rainer ha scritto:
I wouldnt do that because:
If you do so, your author and publish instance will have stored different
data. And the general magnolia concept is to:
1. upload on author instance
2. activate the uploaded stuff to public
And what do you think about this scenario:
1. user upload a file into public instance without storing into the
local repository.
2. a custom filter / control do the staff to send the file back to
author instance AND start a workflow.
3. At this point a custom authentication should be provided, to avoid
permission issues.
4. a "superuser" approve or reject the document answering to the
workflow engine
5. workflow end with short-circuit the route back to public instance,
with "publication" (if approved) or deleting the document (if rejected).
can this be a solution?
this can also be useful if you have several public instances...
Matteo
----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------
