Well, of course you only need to activate UGC back to the author instance if it is actually needed there, that is if the editors should be able to edit or reference this content and activate it back to the public instance. If possible we try to let the editors do this directly on the public instance too, but as you can imagine, often the editors can do more in the Magnolia dialogs than what the user can on the public instance in custom dialogs.

What I did just today: I had my "save" method of the custom dialog in the public instance call the standard "activate" command (and of course have a subscriber to the author instance configured on the public instance). I have not tested it in a real life setup, but it seems to work fine.

-will

On 03.09.2009, at 16:54, Grégory Joseph wrote:



On Sep 3, 2009, at 8:35 AM, Will Scheidegger wrote:

Very good question, Brent! I wanted ask something similar about UGC:

What is The Best Way (TM) to publish UGC back to the author instance?

I think you'll only find out the "best" way if you can explain *why* you want to do that.
There's not always a good reason to do it.


(I tried to use the observation module with mixed results... )

Concerning your first question about the modules: We are using the PUR module in several "real life public sites" and it works just fine. We did tweak it a little tough.

-will

On 03.09.2009, at 04:47, Brent McArthur wrote:

[...]
Also, once we start to get into user generated content we enter the realm of synching clustered repositories. What’s everyone’s opinion on the solution to this? From what I can tell the easiest approach is to move to a MySQL database as the repository (http://wiki.magnolia-cms.com/display/WIKI/MySQL+Persistence ) so that all public instances share the same repository. Does that work?


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to