Observation DMS recursion woes

[Thomas Martin-8]

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: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Jan Haderka-2]

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: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

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

[Thomas Martin-8]

Hi Jan

Thanks for your quick answer. I could unfortunately not find said  
discussion in the archives.
But based upon your explanation (I somewhat assumed it had to do with  
the change in the MetaData) I figured that you need to specify a  
nodeType not only for the listener.

Now with restricting the event (PROPERTY_CHANGED) to nodeType  
mgnl:contentNode everything seems to work nicely.

Great stuff, will save me a couple of phone calls in the future :)
Thanks & cheers
Thomas



On 05.10.2009, at 17:25, Jan Haderka wrote:

>
> 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: <user-list-unsubscribe@...>
>> ----------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>

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

[Jan Haderka-2]

On Tue, 2009-10-06 at 09:44 +0200, Thomas Martin wrote:
> Hi Jan
>
> Thanks for your quick answer. I could unfortunately not find said  
> discussion in the archives.

http://www.mail-archive.com/user-list@.../msg01144.html

;)

> But based upon your explanation (I somewhat assumed it had to do with  
> the change in the MetaData) I figured that you need to specify a  
> nodeType not only for the listener.
>
> Now with restricting the event (PROPERTY_CHANGED) to nodeType  
> mgnl:contentNode everything seems to work nicely.
>
> Great stuff, will save me a couple of phone calls in the future :)
> Thanks & cheers

You're welcome.

Jan


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