Asset Recycling Bin

Favorite-off Notification-off
46 Thumb-up Thumb-down
Idea by ross.williams about 1 year ago Favorite-off - In progress

It would be great to have a more robust asset recycling bin to prevent users from accidentally deleting items that can’t be recovered by administrators.

12 comments

  • 0 points Thumb-up Thumb-down Favorite-off by syl.turner about 1 year ago Permalink
    As a workaround, you can utilize deletion workflows to prevent accidental deletes.
    • 0 points Thumb-up Thumb-down Favorite-off by irifkin about 1 year ago Permalink
      It doesn't make sense to utilize deletion workflows for every page.
      • People do want to delete pages and it shouldn't be prevented.
      • If someone approves the deletion workflow we're back in the same situation.
      • Many sites may only have one Web editor, so it really doesn't make sense to use workflow.
      At best, workflow can help prevent issues from occurring. A recycle bin (or something similar) can help recover.
  • 0 points Thumb-up Thumb-down Favorite-off by Autograff about 1 year ago Permalink
    That's a good workaround, but I agree on the recycle bin. Like a temp db to hold the data deleted, so it's still in its original state, with relationships intact.
  • 0 points Thumb-up Thumb-down Favorite-off by dcloutman 11 months ago Permalink
    I posted the following functional requirements to the HiEd listserv:

    ...given that the application has Quartz running to manage scheduled jobs, it seems like it should be possible to create an administrative tool to

    1. Cache deleted items for recovery
    2. Purge deleted items after an user-defined period of time
    3. Manually purge deleted items.

  • 0 points Thumb-up Thumb-down Favorite-off by bradley.wagner 8 months ago Permalink
    Interested to hear ideas on how we might handle deletion of assets that are critical to the integrity of other assets (e.g. Templates essential for Pages and Page Configurations that use them). My thought was that we handle it kind of like we do now where you can't recycle the template until assets that depend on it, no longer depend on it.

    When the Template is restored, the user has the option to re-establish critical relationships like the parent folder. Like in the OS X operating system, you have the ability to restore an asset to any location.
    • 0 points Thumb-up Thumb-down Favorite-off by mike.strauch 8 months ago Permalink
      Yeah, I don't think we would change any of the deletion rules.
      • 0 points Thumb-up Thumb-down Favorite-off by bradley.wagner 8 months ago Permalink
        We would need to think about restoring assets though and what sorts of things we would prompt users for upon restoration.
        • 0 points Thumb-up Thumb-down Favorite-off by mike.strauch 8 months ago Permalink
          I think it  would basically work the same as activating a previous version when required fields are missing.  I believe with activating versions you are presented an edit form which allows you to populate any missing required fields (this may only be for pages currently, I don't recall).
  • 0 points Thumb-up Thumb-down Favorite-off by jraller 7 months ago Permalink
    Can we get a status update on either this feature or the addition of a new security setting that prevents the use of the delete function for a particular role?
    • 0 points Thumb-up Thumb-down Favorite-off by jraller 5 months ago Permalink
      I saw a very nice demonstration of this at the Fall 2009 Users Conference. It got cheers from the audience. We were told that it was still alpha, but to look for it in early 2010.
  • 0 points Thumb-up Thumb-down Favorite-off by cp-michael 6 months ago Permalink
    Without the ability to backup a single site for recovery this first level of recovery would be very much welcomed.
  • 0 points Thumb-up Thumb-down Favorite-off by turnerjd 6 days ago Permalink
    What's the status of this? Any ideas as to when it will be released?

No attachments


* Note - To input code samples, click the pencil icon (this will remove the WYSIWYG) then be sure to start and end code sections with @@@ (three '@' signs).  For more information on textile markup, click here.  

Sign in

Follow us on Twitter

Current Category