Is there a limit of properties a certain doc type can have?
I have a multilanguage website with language properties on a single doc type for parameters.
For example, I have a property called name as pt_name(Portuguese), en_name(English) and es_name(Spanish) and they are all under a doc type Parameters.
I was wondering if there's any limits for the number of priorities a single doc type can handle. This doc type has over 300 properties and some of them were missing from our live database. I compared the database that we have on our testing environment (which was push live 2 weeks ago) and there were lots of properties that weren't on the live database (over 50).
Is there anything that could have made these priorities go missing? We did not delete any.
I don't think I have ever seen a maximum of properties that can be added...however just because I've never seen any numbers it does not mean that there is a maximum.
But I do think that 300 properties are way too many. Not sure if it can cause data loss but I think you should re-consider your solution and see if you could build it in another way perhaps.
Which version are you using and what database are you using?
We are using Umbraco v.6.1.6 and SQL Server 2008 R2.
Yes, I'm already reconsidering changing the structure that we used, there'll be a lot of impact on the code, but it is better this than properties vanishing.
Usually it's more beneficial to create a tree for each language so you have
Home (english)
- Page
- Page
- Page
- Etc.
Home (portugeese)
- Page
- Page
- Page
- Etc.
But of course it depends of your needs etc. but in most cases (In my experience) this is a good approach. It also makes it farily easy to render the content. However sometimes you have shared content from a shared content repository, which you may not want to structure the same way...then you can use the properties approach...well that was untill Matt "Karmanator" Brailsford made the Vorto package...unfortunately it's only supported on v7 though.
We usually work with separate websites and dictionary, but as this site is kind of a "social network" and content is created by the users, it would be something difficult to do, especially 'cause our client wanted all of the languages to be centralized in the templates.
Number of properties per doc type
Hi guys,
Is there a limit of properties a certain doc type can have?
I have a multilanguage website with language properties on a single doc type for parameters.
For example, I have a property called name as pt_name(Portuguese), en_name(English) and es_name(Spanish) and they are all under a doc type Parameters.
I was wondering if there's any limits for the number of priorities a single doc type can handle. This doc type has over 300 properties and some of them were missing from our live database. I compared the database that we have on our testing environment (which was push live 2 weeks ago) and there were lots of properties that weren't on the live database (over 50).
Is there anything that could have made these priorities go missing? We did not delete any.
Thanks!
Hi Francielle
I don't think I have ever seen a maximum of properties that can be added...however just because I've never seen any numbers it does not mean that there is a maximum.
But I do think that 300 properties are way too many. Not sure if it can cause data loss but I think you should re-consider your solution and see if you could build it in another way perhaps.
Which version are you using and what database are you using?
/Jan
Hi Jan,
Thanks for your reply.
We are using Umbraco v.6.1.6 and SQL Server 2008 R2.
Yes, I'm already reconsidering changing the structure that we used, there'll be a lot of impact on the code, but it is better this than properties vanishing.
Usually it's more beneficial to create a tree for each language so you have
Home (english) - Page - Page - Page - Etc.
Home (portugeese) - Page - Page - Page - Etc.
But of course it depends of your needs etc. but in most cases (In my experience) this is a good approach. It also makes it farily easy to render the content. However sometimes you have shared content from a shared content repository, which you may not want to structure the same way...then you can use the properties approach...well that was untill Matt "Karmanator" Brailsford made the Vorto package...unfortunately it's only supported on v7 though.
Hope these input help.
/Jan
Hi Jan,
We usually work with separate websites and dictionary, but as this site is kind of a "social network" and content is created by the users, it would be something difficult to do, especially 'cause our client wanted all of the languages to be centralized in the templates.
Anyways, thanks a lot for your help and tip!
is working on a reply...