Metadata Default not actually applied to assets

(Nic Hubbard) #1

I have a strange problem. I am using a select metadata field with two options. The first has been set as the default.

 

The metadata schema is applied to a root, and when creating Standard Page assets under that root they correctly get the schema applied. But, when listing those assets with an Asset Listing, and trying to print out that metadata field, it doesn't print anything, when I would expect it to print the default value.

 

Instead it prints nothing, and I have to go to the metadata screen for those assets, and uncheck "Use Default" and then commit that page, only then does the metadata show up in my asset listing.

 

Am I missing something here? It doesn't seem like I should have to do that last step, it seems to me that default metadata values should be automatically applied to an asset.

 

3.14.3

(Ashish Karelia) #2

I think you meant 4.14.3.

Anyways does your problem sound anything similar to #6382 Problem with metadata default value or #6484 creating new Context and Metadata value?

 

Ash

(Nic Hubbard) #3

I think you meant 4.14.3.

Anyways does your problem sound anything similar to #6382 Problem with metadata default value or #6484 creating new Context and Metadata value?

 

Ash

 

Sorry, yes I meant 4.14.3.

 

The bug does seem like #6382.

 

But, isn't the point of having a default metadata value so that it will automatically be the default value for an asset that the schema is applied to? This isn't the case here as it is printing nothing.

 

I have a 4.14.2 install that we are doing the same thing. We have a default metadata value from a select menu, and it correctly gets printed.

 

In the case of the 4.14.3 install, I have a paint layout applied to an asset listing which is using %asset_contents% in the type format. So in the paint layout is where I am trying to print the metadata field.

(Steve Linford) #4

Hi Nic,

 

Was this confirmed as a bug, and if so fixed?

 

I'm having the same problem with V5.1.8 - i.e. nothing printed for a default value, so requiring user intervention to uncheck 'Use default'.

 

Similarly for custom forms, if I set a default value for a question to a value entered for a previous question (e.g. %response_assetID_q1%) the default is blank. Possibly not the same as the metadata issue but I would have expected this to work.

 

Steve

(Nic Hubbard) #5

This was so long ago I don't even remember. Sorry about that!

(Bart Banda) #6

If you change the default metadata value on an already existing field, it won't take affect on all assets until either the metadata schema is regenerated over all those assets, or if you commit the asset's metadata screen manually again. 

 

Is your issue easy to replicate? 

(Nic Hubbard) #7

If you change the default metadata value on an already existing field, it won't take affect on all assets until either the metadata schema is regenerated over all those assets, or if you commit the asset's metadata screen manually again. 

 

Is your issue easy to replicate? 

 

That was probably my issue, but it was confusing because if I remember right it did show the default value on the metadata screen, but you couldn't print it using a keyword. Which from a user standpoint is confusing.

(Bart Banda) #8

Yep, agreed, added roadmap idea for it. https://squizmap.squiz.net/matrix/9190