Undefined variable: metadata_run_level_changed

Squiz Matrix Support
1

Hello


We upgraded to 3.12.1 and that has stopped the closest_parent error we had been seeing when creating assets.



Now when we try to create an asset in Simple Edit with a customised Asset Builder form to allow metadata entry on asset creation for a data record, standard page etc with a metadata schema attached, we get this error and the asset is not created:



Undefined variable: metadata_run_level_changed



Our error log shows this:



(/packages/cms/page_templates/page_asset_builder/page_asset_builder.inc:488) - Undefined variable: metadata_run_level_changed



What can we do about this?



Thanks

Davo

2

How are you configuring your custom layout on the asset builder? You need to customise that layout and reference the metadata field entry as %metadata-F_XXX% where XXX is the asset ID of the metadata field.

3

[quote]How are you configuring your custom layout on the asset builder? You need to customise that layout and reference the metadata field entry as %metadata-F_XXX% where XXX is the asset ID of the metadata field.
[right][post=“14631”]<{POST_SNAPBACK}>[/post][/right][/quote]



Thats exactly what we have been doing i.e %metadata-F_757%. This was working before the upgrade to 3.12.1.

4

[quote]Thats exactly what we have been doing i.e %metadata-F_757%. This was working before the upgrade to 3.12.1.
[right][post=“14633”]<{POST_SNAPBACK}>[/post][/right][/quote]



Can you log this as a bug so that a developer can investigate?

5

[quote]Can you log this as a bug so that a developer can investigate?
[right][post=“14636”]<{POST_SNAPBACK}>[/post][/right][/quote]



Thanks for looking at this Avi. I have logged it as bug #2138

6

Hi Davo


I can see the cause of this problem and it will be fixed in forthcoming releases.



In the meantime, a workaround you can use is to turn OFF the "disable permissions" setting on the details screen of the asset builder page. Turning this off may require that you grant some extra permissions so that users of the page have write access to the create locations.



Tom

7

[quote]Hi Davo


I can see the cause of this problem and it will be fixed in forthcoming releases.



In the meantime, a workaround you can use is to turn OFF the “disable permissions” setting on the details screen of the asset builder page.  Turning this off may require that you grant some extra permissions so that users of the page have write access to the create locations.



Tom

[right][post=“14644”]<{POST_SNAPBACK}>[/post][/right][/quote]



Thanks Tom, We actually intend on checking the permissions in the create locations when user is creating an asset. Therefore we can live with this workaround.