Forums / General / Survey: partial object edit (important!)
Piotrek Karaś
Tuesday 24 June 2008 12:54:44 am
Hello everyone,
I would like to ask you if for any of your eZ Publish implementations you have ever modified object edit forms (templates), so that they do not include <b>all</b> of the object's attributes? Have you ever relied on that as a feature?
For example, you have a content class with special checkbox-like flag attribute that you will make available for administrators in the administration interface, but not for registered users in the public one.
A simple YES/NO answer will be fine. Also, if you have used that feature, how important is it for your installations?
Thanks!Piotrek
-- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Thursday 03 July 2008 10:02:23 pm
No response ;(
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).
André R.
Friday 04 July 2008 3:29:35 am
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 ).
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Hans Melis
Friday 04 July 2008 4:25:32 am
hmmm... I didn't see this before today.
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.
Hans http://blog.hansmelis.be
Friday 04 July 2008 4:56:10 am
<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 ;)
Friday 04 July 2008 5:59:12 am
Well, thanks for the poke ;-)
Maxime Thomas
Tuesday 19 August 2008 11:41:59 pm
Hello Piotrek,
Maybe I've got something for you...
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. :-/
Hope it helps.
Maxime Thomas maxime.thomas@wascou.org | www.wascou.org | http://twitter.com/wascou Company Blog : http://www.wascou.org/eng/Company/Blog Technical Blog : http://share.ez.no/blogs/maxime-thomas
Script start
Module start 'content'
Module end 'content'
Script end
Time used to render debug report: 0.0001 secs