>From my point of view that's quite the same case, doesn't matter on what
>events your listener listens to, you can always check the current content at
>the target webapp and trigger the activation only if it's not in sync with the
>source webapp.
Alternatively, let your account registration/update templates write to the only
one and same repository and set up the listener only at the webapp assigned to
it.
Good luck.
On Wed, 2012-02-29 at 15:44 +0100, Magnolia Forums (on behalf of Vineet
Mehta) wrote:
> Hi,
>
> Thanks for your suggestion.
>
> Ideally writing a custom listener class or the custom syndicator (that I was
> trying) I suppose would be a good solution for our use case.
>
> Regarding the listener class suggestion, I think there is a limitation, since
> we would also want to sync any changes made to user, say name,password,etc.
>
> Please let me know your thoughts.
>
> Thanks.
>
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
