On 04.09.2009, at 09:37, Jan Haderka wrote:
a) this would be quite a coincidence, right?
Coincidences happens. I'm willing to bet that should you put that into
the real life you would experience it on moderately used app quite
soon.
Is Facebook run by Magnolia? ;-)
No, I know what you mean.
b) it could be fixed by a custom save handler of the dialog which
compares modification dates. Tricky but feasible I would say.
I'd say this can be completely avoided by design. How? The user
generated content goes into different workspace then the content
made by
the editor. This is for example the case with the commenting. While
the
comments appear on the same page visually, they live in separate space
physically and their adding/editing/deletion is completely independent
from the updates to the article on which comments are made. Similar
solutions can be devised also for other scenarios.
That of course is a very clean way to solve the problem... As others
have stated too: We are very grateful for such state-of-the-art
solution advice.
For comments this would work fine, but what about user accounts for
instance? If you allow your user to change his/her password and for
some reason you also need your editors to be able to work on the user
account (e.g. adding new groups)?
-will
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
