Closed Bug 882389 Opened 11 years ago Closed 10 years ago

allow users to delete their pages

Categories

(Webmaker Graveyard :: Thimble, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: michiel, Assigned: michiel)

References

Details

(Whiteboard: p=1 s=2013w27 u=dev)

      No description provided.
The soft-integration between Thimble and the makeAPI means that Thimble needs a route that lets someone delete their project. The most sensible would be a two-step approach:

1. call /delete/:id to get a one-time token JSON response (allowing an 'are you sure?' modal)
2. call /delete/confirm/jf90q2jdfohu3hofuhw3pfu34 route to finalise the deletion.

Open to suggestions if anyone has a better idea of course.
Another option that JP and I were discussing was adding a worker that checked a SQS queue, and deleted projects when they appeared in the SQS queue.
Assignee: nobody → pomax
I will be doing this in phases, since it seems this is a composite task:

1. the app needs an app.delete() route for removing content from the database
2. set up a "delete published URLs from S3" middleware + S3 interface
3. be able to inform the makeAPI that a delete occurred, so that deletions can come from in-app too. This step may not be necessary, if we're committing to only allowing deletes through
the makeAPI (personally, the idea of a delete button next to the publish button for thimble would be lovely, so I can delete a page I just published because in retrospect it was a crappy page, and I'm already /edit'ing it. No need to trawl my makes if I already have the thing I want to delete)
Status: NEW → ASSIGNED
Whiteboard: p=1 s=2013w26
Blocks: 886857
Depends on: 886860
Whiteboard: p=1 s=2013w26 → p=1 s=2013w27 u=dev
unassigning pending reprioritisation
Assignee: pomax → nobody
Status: ASSIGNED → NEW
Assignee: nobody → schranz.m
Assignee: schranz.m → nobody
Assignee: nobody → pomax
Status: NEW → ASSIGNED
invalidating this in favour of a wider discussion on the various levels of private/public/deleting/etc we want in our tools.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.