I installed a brand new Umbraco v6.0.0 instance, and added this doc type structure.
Base Page (Create a tab called: "Content").
--- Standard Page (Create a property called BodyText, alias: bodyText into tab Content from Base Page)
--- News Page (Create a property called BodyText, alias: bodyText into tab Content from Base Page)
After that, if you go to Content, and create a new DOC of type Standard Page, fill BodyText with any value, and hit Save and Publish, it does not throws any error, but if you go to another node and come back, the value is not there anymore.
This is indeed a bug - not sure if it ha been reported at the issue tracker but if it has not please feel free to report it here http://issues.umbraco.org/issues/U4
I think that it would also be nice if you provide the stack trace of the error in the bug report.
Making matters worse, you guy are now FORCING lowercase first letters for aliases. In the PAST aliases had uppercase first letters. So now, if a property is changed, it CAN'T be saved without breaking XSLT,. etc. Worse, even if you do change to lowercase and SAVE, the DB does not appear to reflect the changes:
In any case, in instances where multiple pages have the same properttype Name, I am also seeing problems.
I have had to manually change names in the DB, as the properties "Save" appears to work, but records are not updated if multiple document types include the property name.
This is a mess that should be easily reproducble by HQ. Please fix it.
Umbraco v6.0.0: Properties of different doc types with the same name causes a bug.
I installed a brand new Umbraco v6.0.0 instance, and added this doc type structure.
Base Page (Create a tab called: "Content").
--- Standard Page (Create a property called BodyText, alias: bodyText into tab Content from Base Page)
--- News Page (Create a property called BodyText, alias: bodyText into tab Content from Base Page)
After that, if you go to Content, and create a new DOC of type Standard Page, fill BodyText with any value, and hit Save and Publish, it does not throws any error, but if you go to another node and come back, the value is not there anymore.
Hi Francisco
This is indeed a bug - not sure if it ha been reported at the issue tracker but if it has not please feel free to report it here http://issues.umbraco.org/issues/U4
I think that it would also be nice if you provide the stack trace of the error in the bug report.
Cheers,
Jan
Making matters worse, you guy are now FORCING lowercase first letters for aliases. In the PAST aliases had uppercase first letters. So now, if a property is changed, it CAN'T be saved without breaking XSLT,. etc. Worse, even if you do change to lowercase and SAVE, the DB does not appear to reflect the changes:
In any case, in instances where multiple pages have the same properttype Name, I am also seeing problems.
I have had to manually change names in the DB, as the properties "Save" appears to work, but records are not updated if multiple document types include the property name.
This is a mess that should be easily reproducble by HQ. Please fix it.
is working on a reply...