I stumbled across a page field "contents" which is all present in the list of available fields when inserting page fields into a template. Can anyone tell something about its meaning/function?
Aaah, it's a "Folder Browser" field of the default "Folder" media type. I wonder why the media properties appear in the umbraco page field list, as obviously they are no page but media properties and I think they cannot be used, since templates and macros can only be used with documents.
Actually all of the available properties/aliases that's created in the installation, will be vissible in the page field list when creating templates through the back office. You could argue that properties on media items shouldn't be in that list, but sometimes we actually need those properties in the tempaltes, so it would be kind'a hard to determine which properties should be shown and which ones shouldn't.
What does the page field 'contents' do?
Hi,
I stumbled across a page field "contents" which is all present in the list of available fields when inserting page fields into a template. Can anyone tell something about its meaning/function?
Atze
Aaah, it's a "Folder Browser" field of the default "Folder" media type. I wonder why the media properties appear in the umbraco page field list, as obviously they are no page but media properties and I think they cannot be used, since templates and macros can only be used with documents.
Actually all of the available properties/aliases that's created in the installation, will be vissible in the page field list when creating templates through the back office. You could argue that properties on media items shouldn't be in that list, but sometimes we actually need those properties in the tempaltes, so it would be kind'a hard to determine which properties should be shown and which ones shouldn't.
Just my five cents :)
/Kim A
is working on a reply...