This may constitute a feature request... either that or it's a rookie question :/
I recently accidentally dragged a fragment from one page to another while attempting to simply scroll up the content tree pane.
The result is that now I have a fragment that was given to me by my client that I have manually dragged back to its original PAGE, but I seem to have no way of discerning it's original position ON ITS ORIGINAL PAGE.
Perhaps if there was a limited history of content tree alterations, enough to provide a basic "undo" function for such errors, this kind of mistake will be less costly.
Of course I am only raising this issue because of one very minor occurance. Truth be told in this scenario I don't think it matters one bit if the fragments are slightly rearranged, but one day it could be a problem to someone...
I recently accidentally dragged a fragment from one page to another while attempting to simply scroll up the content tree pane.
The result is that now I have a fragment that was given to me by my client that I have manually dragged back to its original PAGE, but I seem to have no way of discerning it's original position ON ITS ORIGINAL PAGE.
Perhaps if there was a limited history of content tree alterations, enough to provide a basic "undo" function for such errors, this kind of mistake will be less costly.
Of course I am only raising this issue because of one very minor occurance. Truth be told in this scenario I don't think it matters one bit if the fragments are slightly rearranged, but one day it could be a problem to someone...
Comment