Is a metadata loop possible?

Squiz Matrix Support
1

I added a new metadata field to our schema which has two Matrix tags set in the default field.


One tag printed the image source url of any thumbnail attached to the asset the schema was applied to and the other tag printed the contents of an existing metadata field we had created that contains a description of the asset.



When this was applied the server went very very slow (and still is!), our sysadmin noticed that Postgres had lots and lots of processes so many that the frontend and backend are not accessible and are timing out:blink:



Have I created some sort of metadata loop?

2

[quote]I added a new metadata field to our schema which has two Matrix tags set in the default field.


One tag printed the image source url of any thumbnail attached to the asset the schema was applied to and the other tag printed the contents of an existing metadata field we had created that contains a description of the asset.



When this was applied the server went very very slow (and still is!), our sysadmin noticed that Postgres had lots and lots of processes so many that the frontend and backend are not accessible and are timing out:blink:



Have I created some sort of metadata loop?[/quote]



I had the loop before. But the loop only happens when you set a metadata keyword into a metadata fields.



For example, here are two fields in metadata,



field_one

field_two





if you set field_two's default value with the keyword of "%asset_metadata_field_one%", the loop occurs and make the system very slow.



So just avoid doing this.



Robin

3

[quote]I had the loop before. But the loop only happens when you set a metadata keyword into a metadata fields.


For example, here are two fields in metadata,



field_one

field_two





if you set field_two's default value with the keyword of "%asset_metadata_field_one%", the loop occurs and make the system very slow.



So just avoid doing this.



Robin[/quote]



Thanks Robin, looks like we did something similar. The way we managed to stop it was to stop Postgres so it killed all the open connections. Restart Postgres and quickly go in before lots of processes had started and delete the offending asset and purge the trash.



Over night the server had core dumped 70 gigs of data :blink:

4

Just ran into this problem myself too. Did anyone figure out a solution to make this work? I am trying to populate many pages through a paint layout using metadata fields. But since the control of the actual entering of the data is out of my hands, I would like to populate fields that are empty with other fields that are required to be populated in case the user has not yet populated the later metadata field.


Any advice?

5

There should be no looping unless you set field one to be the value of field two and also set field two to be the value of field one. Using the standard keywords to include the content of one field within another should work fine and not cause any performance problems. If it is, please report a bug and the developers will take a look.

6

Just to make sure I am doing it right, how would I correctly set the value of field1 metadata to the value of field2 metadata? Using the keyword %asset_metadata_field1% for the value of metadata field2 is causing a loop for me.

7

Yes this is correct and should work without looping.

As Greg has suggested, please submit details of the issue (including field types and values) to our Bug Tracker at http://bugs.matrix.squiz.ne so we can investigate this in detail.

8

The keyword for using one metadata field in another is just %metadata_field_field1%. I've found that using %asset_metadata_field1% will cause looping errors.
9

A new keyword? :P' /> <img src='http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/tongue.gif' class='bbc_emoticon' alt=':P
10

All hail the mighty Avi! That is what I needed and it works without causing a loop.
11

Sorry to reopen an old topic.


I want the value of one metadata field to be the default value of another metadata field and I want to avoid the looping below.



Is it better to use %globals_asset_metadata_AllPurposeDate% or %metadata_field_AllPurposeDate%? When I try %metadata_field_AllPurposeDate% on the edit contents screen nothing appears which makes me think it won't work… but I do not want to cause a loop as I wouldn't know how to delete it as described below. We are on 3.16.12.

12

Here's a tip; don't make a post, forget about it, then pick the project up a month later and happily stick %asset_metadata_fieldname% in. You'll do so many loops you'll think you're on a rollercoaster. :rolleyes:


%metadata_field_fieldname% seems to work just fine. Thanks everyone.