Hi,
We have recently upgraded to 3.22.6 and I have been viewing the logs and have found two new entries:
error log:
(/core/include/metadata_manager.inc:1705) - Undefined index: event date
cron_errors:
(/packages/cms/cron_jobs/cron_job_manage_incomplete_submissions/cron_job_manage_incomplete_submissions.inc:205) - Only variables should be passed by reference
I understand the cron error is an open bug at the moment, however the metadata manager error seems to be specific to pages we've created using the Date field option of a metadata schema. These are the details:
Details
Field Name event_date
Friendly Name
Friendly Name will be used as the caption for metadata fields in the edit interface. If it is left empty, Field Name will be used instead.
Description
Default Value 01 Jan 2009
Choose the default value for this field. If 'show keyword selector' (below) is enabled, an asset keyword may be chosen as the default value.
Offset
Type, in plain text, an offset for this field (if any). For example, "+1 year" or "-1 day"
Display Format d M Y
Click Here to see the formatting keywords that can be used in this field. Note that you cannot use a tilde (~) to separate date fields.
Scheme
Language
Options
Editable Yes
If this field is not editable, the user will always see the default value
Editing Style 01 Jan 2003
Note that this setup table only affects how the field looks to the metadata editor, NOT how it is displayed in META tags on the frontend.
Show keyword selector No
Choose whether metadata editors should be able to choose asset keywords for this field's value, as an alternative to a specific date.
Required No
If this field is Required, then either the value or any one of the value components must be set for an asset to be approved
Show On Frontend Always
Always: this metadata field will always be printed on the frontend.
Only If Filled: this metadata field will only be printed on the frontend if data is entered in that field for that asset.
Never: this metadata field will not be printed on the frontend.
Is there something wrong with these details that could explain the above error we're getting?
Thanks
Hi,
All sorted.
Tracked it down to a an asset listing page that was sorting on a metadata tag that didn't exist.
[quote]
Hi,
We have recently upgraded to 3.22.6 and I have been viewing the logs and have found two new entries:
error log:
(/core/include/metadata_manager.inc:1705) - Undefined index: event date
cron_errors:
(/packages/cms/cron_jobs/cron_job_manage_incomplete_submissions/cron_job_manage_incomplete_submissions.inc:205) - Only variables should be passed by reference
I understand the cron error is an open bug at the moment, however the metadata manager error seems to be specific to pages we've created using the Date field option of a metadata schema. These are the details:
Details
Field Name event_date
Friendly Name
Friendly Name will be used as the caption for metadata fields in the edit interface. If it is left empty, Field Name will be used instead.
Description
Default Value 01 Jan 2009
Choose the default value for this field. If 'show keyword selector' (below) is enabled, an asset keyword may be chosen as the default value.
Offset
Type, in plain text, an offset for this field (if any). For example, "+1 year" or "-1 day"
Display Format d M Y
Click Here to see the formatting keywords that can be used in this field. Note that you cannot use a tilde (~) to separate date fields.
Scheme
Language
Options
Editable Yes
If this field is not editable, the user will always see the default value
Editing Style 01 Jan 2003
Note that this setup table only affects how the field looks to the metadata editor, NOT how it is displayed in META tags on the frontend.
Show keyword selector No
Choose whether metadata editors should be able to choose asset keywords for this field's value, as an alternative to a specific date.
Required No
If this field is Required, then either the value or any one of the value components must be set for an asset to be approved
Show On Frontend Always
Always: this metadata field will always be printed on the frontend.
Only If Filled: this metadata field will only be printed on the frontend if data is entered in that field for that asset.
Never: this metadata field will not be printed on the frontend.
Is there something wrong with these details that could explain the above error we're getting?
Thanks
[/quote]