G'Day,
I am trying to set a trigger to set the future status of an asset based on a metadata date field (see attachment). This consistently fails. If I use either of the first two options (immediately when this trigger is fired OR at exactly XXXXX) the trigger succeeds. There is nothing in the error or system logs beyond "the trigger failed". Can anyone provide any guidance on this? Thanks.
[quote]
I am trying to set a trigger to set the future status of an asset based on a metadata date field (see attachment). This consistently fails. If I use either of the first two options (immediately when this trigger is fired OR at exactly XXXXX) the trigger succeeds. There is nothing in the error or system logs beyond "the trigger failed". Can anyone provide any guidance on this? Thanks.
[/quote]
The contents of the Metadata Date Field must be in ISO 8601 format. ie; 2009-11-20 13:30:00
[quote]
The contents of the Metadata Date Field must be in ISO 8601 format. ie; 2009-11-20 13:30:00
[/quote]
Thanks Mark but that doesn't seem to be the (only) answer. I have changed the format of the date field to ISO 8601, regenerated the metadata and created a new trigger. I continue to receive the same errors -
MySource Notice
Trigger Action: trigger_action_set_future_status Failed [CORE0135]
MySource Warning
FAILURE: Trigger "Press Release Manager" (Trigger# 14), Event "trigger_event_attributes_changed" broadcast by "Second test item " (Id# 25822) [CORE0127]
[quote]
Thanks Mark but that doesn't seem to be the (only) answer. I have changed the format of the date field to ISO 8601, regenerated the metadata and created a new trigger. I continue to receive the same errors -
MySource Notice
Trigger Action: trigger_action_set_future_status Failed [CORE0135]
MySource Warning
FAILURE: Trigger "Press Release Manager" (Trigger# 14), Event "trigger_event_attributes_changed" broadcast by "Second test item " (Id# 25822) [CORE0127]
[/quote]
If the date supplied is being sourced from a Parameter Map, please verify that the associated GET/POST/SESSION variable contains a correctly-formatted date.
If this appears to be in order, please lodge a Support Ticket and we will investigate this on your system.
[quote]
If the date supplied is being sourced from a Parameter Map, please verify that the associated GET/POST/SESSION variable contains a correctly-formatted date.
If this appears to be in order, please lodge a Support Ticket and we will investigate this on your system.
[/quote]
It turns out I needed to use 'c' as the formatting keyword in the metadata schema to format the datetime correctly. Using Y-m-d H:i:s didn't work. c is not listed in the pop up of formating options in Matrix.
Thanks for your help.
[quote]
c is not listed in the pop up of formating options in Matrix.
[/quote]
You should always rely on the date keywords from php.net rather than that pop-up, not sure when the pop-up was updated.
[quote]
You should always rely on the date keywords from php.net rather than that pop-up, not sure when the pop-up was updated.
[/quote]
Nic, it is good to know that now but there is no indication of that anywhere within the Squiz documentation universe. Out of date/incorrect information is worse than no information. If the list cannot be maintained it should be removed and replaced with a link to the relevant page on php.net (which is where I found the details). Further, documentation needs to contain information to be useful. There is a triggers manual. A single sentence in there that says "The Set Future Status Trigger requires datetimes to be formatted in ISO 8601 format." would have saved hours of time, both on my part and that of Mark.
HTML versions of the manuals where users could leave comments - much like the documentation for PHP - would be amazingly useful. Users/developers could then fill in the holes, all those little bits of knowledge, single sentences and snippets that are locked up in people's heads. Somehow I doubt that would happen though.