#4925 - Custom fields seem impossible to reference
| Identifier | #4925 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | Custom fields seem impossible to reference |
| Status | Closed (no changes needed) |
| Handling member | Chris Graham |
| Version | 10.0.43 |
| Addon | catalogues |
| Description | I have set a custom catalogue field on Gallery videos which references a catalogue entry. If I try to use {$CATALOGUE_ENTRY_FIELD_VALUE,53,0} the field is blank (though that is the correct ID). |
| Steps to reproduce | |
| Additional information | {$CATALOGUE_ENTRY_FIELD_VALUE,{$GET,bound_catalogue_entry}} works but this limits me to single custom field. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
CATALOGUE_ENTRY_FIELD_VALUE looks up a specific entry based on entry ID.
You mentioned you have a custom field. Custom fields for a content entry are themselves stored in a catalogue entry.
You mentioned the custom field references another catalogue entry.
It sounds like you are getting confused between having a video referencing a catalogue entry which itself references another catalogue entry.
When you said {$CATALOGUE_ENTRY_FIELD_VALUE,{$GET,bound_catalogue_entry}} works but for a single field -- well, you didn't include a field sequence number. The field sequence number defaults to 0, which is the first. {$CATALOGUE_ENTRY_FIELD_VALUE,{$GET,bound_catalogue_entry},1} Would be the 2nd custom field of the catalogue.
If you want to get the raw value of the 1st custom field and then reference the catalogue entry that field is pointing to to get the title field (1st field) of that entry, I think that would be...
{$CATALOGUE_ENTRY_FIELD_VALUE_PLAIN,{$CATALOGUE_ENTRY_FIELD_VALUE_PLAIN,{$GET,bound_catalogue_entry},0},0}
As for PARAM_INFO, that only returns parameters to a template. The custom fields are not themselves parameters because they have to be looked up individually as described here.