Too bad. My question/survey is related to one of the bug fixes that will be introduced soon, securing most of the built-in datatypes: http://issues.ez.no/10655
I expect that sites using the feature described above will have problems with their edit forms, meaning - the forms will never validate, hence it will not be possible to publish using those forms.
Now, it may be just our problem, but I suspect that we were not the only ones to use that, as there was no good alternative for partial object editing for a long time (and I don't think there is one now).
I use it. But I guess you can just hide the attributes with css instead so they will get their default value ( so you need to set a default value in the class on required attributes, that you for some reason decides to hide ).
We use that feature in a couple of places and on a couple of sites. There are a few places where it's used in the core business of a site, so I'd label it as critical there.
But isn't the change of behaviour a BC break? I thought that was only allowed for major releases.
<i>...There are a few places where it's used in the core business of a site, so I'd label it as critical there... but isn't the change of behaviour a BC break? I thought that was only allowed for major releases...</i> This is exactly why I am trying to have more than just one or two people discuss this issue ;)
In fact, a colleague and I were trying to only update one attribute by one attribute (or chunks of content by chunks, like in a wizard) and we found the great extension of Sir Kristof Coomans, eZLord :
http://projects.ez.no/index.php/powercontent
The only problem is that you version the content at each update, logical. :-/