After the successful activation, the activation info is updated in the content, which is picked up by your observer and leads to another activation. You should not trigger activation on MetaData updates or at least not on activation related props updates (activation date, activation status, activator id). It has been discussed on the list before.
HTH, Jan On Mon, 2009-10-05 at 16:56 +0200, Thomas Martin wrote: > Hi List > > One of the most user-errors we get is people forgetting to activate > DMS content and therefore downloads on the public instance are either > out of date or not existing. > > So I thought, let me try this fine observation module and just > activate every new / changed file in the DMS automatically. > Basically this seems to work very well - until I bumped in to > following combination: > > When setting > > eventTypes: PROPERTY_CHANGED > and > includeSubNodes: true > > whenever I change something that does not reside on the root (/) > magnolia entered a _endless_ loop of firing events and activating nodes. > > So my question is has anyone had this issue and is there a solution to > it? > > magnolia CE 3.6.8 > observation 1.0 > > Any pointers very welcome. > Brgds, Thomas > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
