Sorry if this seems basic but I am very new to Umbraco (less than 2 days old).
Anyway I've been looking at the datatypes and there doesn't seem to be support for lists or array types.
So for instance if I was to create a 'contact list' which will display on my page as a table of name, email address, phone number, job title. Now, I realise I could just do this in a text block and have the content editors maintain it as such, or I could have a contact document type and have multiple child nodes then roll them up on the parent page but that's not an idea way for the editors to maintain the data either.
Any insightful wisdom on how this should be done would be most welcome.
I've been struggling with the same issue. Repeatable Custom Content is great, but doesn't work with all datatypes (namely, I haven't been able to make it work with any Media Picker that allows upload).
Lately I have been using child nodes for list data. The only thing I am worried about, is Umbraco treating the node as a Page, when it's really just a "list item". I'm worried the Search may pick these up as pages and show links, which will of course goto a blank page since they don't have associated templates. Another example, if you use notifications/approvals, the email has a Preview link which will also goto a blank page. Though I guess one could create a template that simply lists the data so reviewers can at least see. I'm sure there are ways around these, just haven't looked into it yet.
If you are worried about the pages being picked up by search, etc. You could have a property on the parent node called which if true meant that the children nodes are hidden in sitemaps, navigation, etc. To do this you just need to add a true/false data type and then on your Macros test is the parameter is equal to 0 or 1.
This is how we normally apporach this and in addition we might also add a IIS redirect on the child pages to point them back at the parent. (this could be done using a template if you wished).
How do you enter list data?
Sorry if this seems basic but I am very new to Umbraco (less than 2 days old).
Anyway I've been looking at the datatypes and there doesn't seem to be support for lists or array types.
So for instance if I was to create a 'contact list' which will display on my page as a table of name, email address, phone number, job title. Now, I realise I could just do this in a text block and have the content editors maintain it as such, or I could have a contact document type and have multiple child nodes then roll them up on the parent page but that's not an idea way for the editors to maintain the data either.
Any insightful wisdom on how this should be done would be most welcome.
Thanks in advance.
Jim
We would probably normally do this with child nodes and then bring them to the parent page using XSLT.
But you could also look at this Umbraco Project as it may fit your needs;
http://our.umbraco.org/projects/repeatable-custom-content
- Lau
I've been struggling with the same issue. Repeatable Custom Content is great, but doesn't work with all datatypes (namely, I haven't been able to make it work with any Media Picker that allows upload).
Lately I have been using child nodes for list data. The only thing I am worried about, is Umbraco treating the node as a Page, when it's really just a "list item". I'm worried the Search may pick these up as pages and show links, which will of course goto a blank page since they don't have associated templates. Another example, if you use notifications/approvals, the email has a Preview link which will also goto a blank page. Though I guess one could create a template that simply lists the data so reviewers can at least see. I'm sure there are ways around these, just haven't looked into it yet.
Just my thoughts
-Tom
Hi Tom,
If you are worried about the pages being picked up by search, etc. You could have a property on the parent node called which if true meant that the children nodes are hidden in sitemaps, navigation, etc. To do this you just need to add a true/false data type and then on your Macros test is the parameter is equal to 0 or 1.
This is how we normally apporach this and in addition we might also add a IIS redirect on the child pages to point them back at the parent. (this could be done using a template if you wished).
Lau
is working on a reply...