We have started receiving PHP Notice's from the Asset Metadata Screen since earlier this month when assets have been created but have not had their create date and modified dates automatically generated as configured to do so in the Metadata Schema interface. e.g.
Undefined index: asset_created_Y-m-dTH:i:sO_
Our [i]Display Format[/i] is: Y-m-d\TH:i:sO and our Metadata Date Field Screen reports the [i]Editing Style[/i] as "2007-07-17T11:18:28+1000" which is the correct format and would indicate that the date mask is being parsed properly. I have checked that metadata is applied to the assets automatically and can confirm that the information for other metadata values is being generated. In other words at this point it is just the create and modified dates that are failing to generate leaving blank entires for these metadata fields as well as generating PHP Notices when accessing the asset's metadata screen.
At this stage I have taken the step of locking everyone out from the edit/admin interfaces until I can sort out what's happening. Does anyone have any ideas what may be causing this?
[quote]We have started receiving PHP Notice's from the Asset Metadata Screen since earlier this month when assets have been created but have not had their create date and modified dates automatically generated as configured to do so in the Metadata Schema interface. e.g.
Undefined index: asset_created_Y-m-dTH:i:sO_
Our Display Format is: Y-m-d\TH:i:sO and our Metadata Date Field Screen reports the Editing Style as "2007-07-17T11:18:28+1000" which is the correct format and would indicate that the date mask is being parsed properly. I have checked that metadata is applied to the assets automatically and can confirm that the information for other metadata values is being generated. In other words at this point it is just the create and modified dates that are failing to generate leaving blank entires for these metadata fields as well as generating PHP Notices when accessing the asset's metadata screen.
At this stage I have taken the step of locking everyone out from the edit/admin interfaces until I can sort out what's happening. Does anyone have any ideas what may be causing this?
Thanks for your help.
Just updated our config below.[/quote]
Hi John,
This request is now in our support queue and a developer will have a look as soon as they are available.