I have an asset listing set up to display standard pages that all have the same metadata schema, and while the Price gets successfully output using %asset_metadata_Price%, I cannot get a description or any custom fields to appear.
I have tried %globals_asset_metadata... etc. and %asset_field... etc. but these produce the same result - the output is empty.
Does anyone have any suggestions or ideas? Thanks.
Do any of your metadata fields have spaces in? If so, you'll need to reference them using underscores instead, so "Item Name" would be referenced as %asset_metadata_Item_Name%, not %asset_metadata_Item Name%
If your asset listing is embedded into another page, %globals_asset_metadata... will be referring to the asset your listing is embedded within, not the asset you're intending to reference.
For the description, assuming that this is on the page contents, you'll want %asset_contents%
Thanks for the response :) Unfortunately none of the fields use spaces and the %globals_asset_metadata... was just hopeful testing.
I think I might simply be trying to use metadata in an unintended manner, because I'm not trying to output this information inside the <head> tag, but to actually display it on the page. I had thought it was working because the Price was appearing as 0.00, but since changing some prices and still seeing 0.00 everywhere I'm wondering if Squiz's metadata is restricted to being used as page metadata. It's starting to look like I probably haven't gone about this in the best way... <_<
I'm wondering if Squiz's metadata is restricted to being used as page metadata. It's starting to look like I probably haven't gone about this in the best way... <_<
No no, not at all. Metadata is used everywhere. It can be used just how you are, to add extra data to an asset, and print it out in the body of your site.
Do the assets that you are printing, actually have the metadata schema applied to them, therefore, having those fields?
Do the assets that you are printing, actually have the metadata schema applied to them, therefore, having those fields?
Following up on that, you may also need to regenerate the metadata on those assets if you have changed those fields in the schema since applying. You can do this by going to each individual asset and Acquiring the Locks on the Metadata screen and committing, or selecting Regenerate metadata on the Details screen of the Metadata Schema.
Thanks for the responses. I never managed to resolve this and instead just implemented workarounds. However, now I'm needing the same functionality in a different place and it's still not working.
I've started a brand new Design, and in the parse file of the design I am trying to print (for example) %asset_metadata_Region% and some other custom metadata fields.
I've applied the relevant metadata schema to a page and filled in the fields, but the whole %asset...% tag is replaced with nothing at all.
Any additional ideas are most welcome!
EDIT: When using <MySource_AREA id_name="metadata" design_area="metadata" /> , the resulting output is
If I find the page that uses this design in the asset list and look at it's Metadata, however, the it is correctly shown as
<!-- My Meta Schema //--> <!-- SectionName //--> <meta name="Region" content="Region 1" /> <meta name="Date" content="01/01/1901" />
Obviously there is no problem with the schema or its being applied to the page: all of the fields from the schema get printed into the HTML, but they remain empty even when every field is definitely filled out on the page that's using this design. All of the fields are set to "Always" display on frontend, the schema is set for "Yes" to Show on Frontend, the section has No Restrictions.
After extensive trial and error I seem to have discovered that Metadata fields are very touchy when it comes to the following:
I'm not sure which was the main culprit but hopefully for anyone else frantically googling, this might be of some use.
I tried to submit a bug report but trying to use the bug report interface is like licking a cheese grater.
I tried to submit a bug report but trying to use the bug report interface is like licking a cheese grater.
What issue did you have with reporting this as a bug? The Bug Reporter is extremely straight forward. Just tell is what Matrix version, and then type up the details.
I find that the metadata output is case sensitive, I use it a lot in my page content, failing that it is the underscores that will get you. Also look at the content of the fields and see if it breaks up your HTML in weird and wonderful ways.