Inline Editing (OE?)

Friday 30 April 2010 2:32:01 am

Hello,

I was wondering if there is an inline editor where the user can on-site edit just one single datatype instead of all of them? If you have a class with an xml-block with a header and you only want to edit one or the other, I only want the datatype area to turn into a box or line when pressing an "edit" link above each datatype.

Is that possible, or do I need to use WT to get to the edit page and then scroll down to the datatype that I need to edit and then publish the result? This would be a much more user-friendly way for users to edit a single datatype and on-page with no redirects save the content and see the result.

Best regards,
Håkan

Friday 30 April 2010 3:08:32 am

Hi Jerome,

Thanks for your input.

I watched the webinar for 4.3 upgrade and grouping looked good and promising when editing a full class.

But I was more or less interested in some JS-extension that loaded the datatype as an input, textarea, xml-block area on site and just throw the input update to the database for that specific class datatype. If you miss spell the header for example like tets instead of test, it would be easy enough to click "edit", get an input field instead of the text entered, spell it right, click "save", page reloaded and updated.

The purpose is for Nisses Car Shop owner of age 68 to edit a single input box without getting distracted by other input boxes or fields. The typical user can handle the class updates pretty good, but a few can't and instead of learning they never update the website instead. And overall, everyone would be pleased to use a function like that, even experienced ones, I myself would love that feature.

Are you going to implement this or should I investigate some time to make it work?

Best regards,

Håkan

Friday 30 April 2010 5:52:13 am

This feature has been requested several times, but there are some issues with it.

One: Should it create a new version (probably yes, as you would want to keep revision history, and anything else would be a hack)

Two: Spam, this would need to be for specific user groups only that you trust as it will be 100% inline and without the spam protection edit forms has in them self, and without Captcha for the same reason.

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

Friday 30 April 2010 6:58:53 am

@andré : this feature has, for sure, to be activated when an editor is connected (like website toolbar) so I don't really see a problem with Spam.

There is lot of work behind that but seems doable with the awesome eZ JSCore extension :)

@Håkan : I agree that this feature will be very well welcomed !

--
eZ certified developer: http://ez.no/certification/verify/346216

Friday 30 April 2010 8:03:26 am

I've been wanting to do something like this for a long time.

Would be great if someone else did it instead! :P

I actually made a tiny start a while ago. I created new template functions equivalent to node_view_gui and attribute_view_gui (you could do a search/replace on the default templates or a template designer could just choose specific areas for enabling inline editing).

These functions wrapped their contents with a DIV with classes consisting of object data, node id, object id, class id, parent node id, section etc (everything you need to work out permissions on the client side):

 <div class="node oid-55 nid-2 pnid-1 sid-6... ">...node_view_gui template here.. </div>

A javascript function would check the user's permissions based on these values and highlight appropriate node/attribute templates on mouseover with the relevant edit/remove/hide... buttons shown.

Should be relatively simple to create a custom view that renders the appropriate edit templates which the JS inserts in the page and positions apropriately.

I'm not sure you could avoid a page refresh on publishing though. anything can happen to the page when an object is edited, depending on each individual setup.

I'll dig out my code when i get a chance.

Cheers + g'luck