Trigger hipcup

:ph34r: Hi all


I had a topic previously listed in the general discussion forum section in regards to scheduled future status changes.



Well I decided to try out the new functionality in relations to deleting old- up for review for pages automatically, but no success.





I get the following errors which I have attached for illustration .



Currently we have the following triggers which already exists,




  1. Clear cache - UOM (files)
  2. Clear Cache - UOM (pages)
  3. Set Review Date (6Months) (files)
  4. Set Review Date (6Months) (pages)





    The one I created was yogitrigger which I have attached also


  5. yogitrigger (pages)



    What have I missed here to make this error appear? Thank you :wink:
    triggercreated.JPG (61.6 KB)
    triggererror.JPG (11.2 KB)

I'm not sure what you are trying to achieve with this trigger. It reads as "If a page's status is changed to Up For Review and the attributes where changed, remove all Up For Review future status jobs." That doesn't make sense to me.


The error you have posted is also unrelated as your trigger doesn't include any action to clear the Squid cache. That must be caused by another trigger firing.



Edited to say: Your trigger is already configured to fail because of that Attribute Changed trigger condition. It says on the screen that this will cause the trigger to fail if the event is not Attributes Changed, but your trigger fires on the Status Changed event.

[quote]I’m not sure what you are trying to achieve with this trigger. It reads as “If a page’s status is changed to Up For Review and the attributes where changed, remove all Up For Review future status jobs.” That doesn’t make sense to me.


The error you have posted is also unrelated as your trigger doesn’t include any action to clear the Squid cache. That must be caused by another trigger firing.



Edited to say: Your trigger is already configured to fail because of that Attribute Changed trigger condition. It says on the screen that this will cause the trigger to fail if the event is not Attributes Changed, but your trigger fires on the Status Changed event.

[right][post=“14859”]<{POST_SNAPBACK}>[/post][/right][/quote]





I have removed the Attribute Changed tirgger condition. Basically now I have only got "Asset has the current status of: Live



Action





Delete Future Status



Source string for trigger_delete_future_status not found for locale en_A Up for review. But this totally removes everything, instead of keeping the latest one. Thank you :rolleyes:

What you need is to change the existing trigger action that adds the Future Status. What you currently have setup is one trigger to add a new one and another trigger to delete all of them (including the new one). These need to be combined.


Just edit the existing triggers and make sure you add a new action to remove existing future status jobs BEFORE the action that adds the new job.

[quote]What you need is to change the existing trigger action that adds the Future Status. What you currently have setup is one trigger to add a new one and another trigger to delete all of them (including the new one). These need to be combined.


Just edit the existing triggers and make sure you add a new action to remove existing future status jobs BEFORE the action that adds the new job.

[right][post=“14864”]<{POST_SNAPBACK}>[/post][/right][/quote]



Thank you very much Greg? :slight_smile:



That part is now working well. But I still get that Trigger message error on the top of the detail screen. It happen onces of when I make it live??? :frowning:

[quote]That part is now working well. But I still get that Trigger message error on the top of the detail screen. It happen onces of when I make it live??? :frowning:
[right][post=“14869”]<{POST_SNAPBACK}>[/post][/right][/quote]



Your Squid Cache settings may be wrong. You have custom development for clearing Squid cache and you should not be using the generic trigger actions.

[quote]Your Squid Cache settings may be wrong. You have custom development for clearing Squid cache and you should not be using the generic trigger actions.
[right][post=“14873”]<{POST_SNAPBACK}>[/post][/right][/quote]





Thank you very much Avi in clearing this up for me. B)