1.8 KiB
Noted. Locked in as the next phase plan.
Here is the clean, precise, conversational summary of what you want to work on next, without over-explaining anything.
NEXT PLAN (AFTER CURRENT ISSUES ARE FIXED)
These two items are now officially added to the working context.
1. Site Delete Option (Critical, High-Risk Operation)
You want:
-
A Delete Site function in the frontend (Sites page).
-
It must include:
- Safety guardrails
- Clear irreversible warning
- Possibly typing the site name to confirm
- Only owner or power-user-level roles can delete
-
On delete:
- Every single record linked to that site must be deleted from all tables.
- Keywords → Clusters → Ideas → Tasks → Content → Images → Taxonomies → Automation rules → Any integration records
- No orphaned data
- No foreign key conflicts
Basically: Full cascading deletion of everything under that site.
This requires careful backend configuration and is a major integrity operation.
This point is confirmed and stored.
2. Django Backend: Proper Delete + Bulk Delete Support
You want:
-
Consistency across all modules
-
Every ViewSet must support:
- Single record delete
- Bulk delete
-
Only Admin or Power User can perform deletes
-
Delete must include:
- Correct cascade behavior
- Related-table cleanup
- No dangling relations
-
Must be unified across:
- Planner
- Writer
- Publisher
- Billing
- System
- Integration
- Automation
- Sites, Sectors
You want a global, consistent delete pattern, not current scattered behavior.
This point is confirmed and stored.
Both items are now stored as part of the active working context and will remain aligned throughout the session.
Tell me how you want to proceed next.