• Type: Technical Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: 6.2.0 CE M2
    • Fix Version/s: 6.2.0 CE M2
    • Component/s: DM
    • Labels:


      There is a problem with subentries that have been trashed prior to the trashing of the folder:
      1. If you restore the folder, the subentry should remain trashed.

      2. If you purge the folder, what happens to the subentry? (OS X, for example, does not allow this since it only allows for empty of trash and does not allow for purging individual entries.)

      • For Liferay, the subentries would be orphaned. Subsequent request to restore the subentry would prompt to move the subentry to a new folder (see LPS-27033).

      3. If you restore the subentry, where does the subentry go? (OS X actually has a bug here where if you try to restore the subentry, nothing happens.)

      • For Liferay, we will not allow the option to restore the subentry but the option would be changed to move the subentry (again, see LPS-27033).

      Considering all the above, for now, we should remove the functionality of multiple purge/restores within the trash. The support of multiple purge/restores causes problems in other use cases. One example is the following scenario:

      1. File A and Folder B used to both be in Folder C, but now all three are independently in the trash.
      2. If all three were selected and restore, do you handle #3 in turn? If you did, you would move File A, Folder B, then come across Folder C and now have everything out of context.
      3. If you didn't, you would have to walk the entire folder/file/shortcut hierarchy to determine the relationships and restore in order.


          Issue Links



              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:
                  Days since last comment:
                  6 years, 38 weeks, 6 days ago


                  Version Package
                  6.2.0 CE M2