action
Contributors
- Balazs Halasy Updated
- Kristof Coomans Commenter
- Samuel Sauder Commenter
- P. Renaud Commenter
This documentation stores what it needs to work: a session cookie when you sign in or keep a setting such as the help menu shown or hidden, the design you chose (Classic or Modern) and your language. Only if you agree, it also uses Google Analytics (through Google Tag Manager) to count visits; until then nothing is loaded from Google. Your choice is kept in a cookie for 6 months, and you can change it at any time under "Cookie settings" at the foot of every page. Details are in our Cookie Policy.
The session cookie for signing in and for forms, the cookies that keep your design and language, and the cookie that keeps this choice. They stay on because the website needs them; you can delete them in your browser settings at any time.
Google Analytics, loaded through Google Tag Manager (GTM-MPGWKTQV), counts visits and shows us which pages are read: the pages you open, the page you came from, your browser, device and screen size, and your approximate location derived from your IP address. Google processes the data for us and may transfer it to the USA. It sets the cookies _ga and _ga_* for up to 2 years. Off until you turn it on; when you turn it off again, Google is no longer loaded and these cookies are deleted.
Comments (4 historical)
Written by readers of the earlier documentation sites, kept as they were.
HTML form element names
Kristof Coomans ·
A list with the names for the HTML form elements for the different view actions and their meaning would be very useful.
For example, to move a node, you can use these names:
MoveNodeAction, must be present to trigger the action
ContentNodeID, the node id of the node to move
optional:
NewParentNode, the node id of the new parent node, if not present the user will have to browse for the new parent node
ViewMode, the node's view mode to redirect to, if not present 'full'
ContentObjectLanguageCode, the object's language to redirect to, if not present the default language
Re: HTML form element names
Samuel Sauder ·
From my experience....
Edit needs ContentObjectID as a hidden form field like this
<form method="post" action="main/content/action/"> <input type="hidden" name="ContentObjectID" value="{$node.object.id}" /> <input class="button" type="submit" name="EditButton" value="{'Edit'|i18n('design/standard/node/view')}" /> </form>Create needs ClassIdentifier and NodeID
<input type="hidden" name="ClassIdentifier" value="my_custom_class" /> <input type="hidden" name="NodeID" value="{$node.node_id}" />Re: HTML form element names
Samuel Sauder ·
From my experience....
Edit needs ContentObjectID as a hidden form field like this (add your own lt and gt html markers)
form method="post" action="main/content/action/"> input type="hidden" name="ContentObjectID" value="{$node.object.id}" /> input class="button" type="submit" name="EditButton" value="{'Edit'|i18n('design/standard/node/view')}" /> /form>Create needs ClassIdentifier and NodeID
input type="hidden" name="ClassIdentifier" value="my_custom_class" /> input type="hidden" name="NodeID" value="{$node.node_id}" />Re: Re: HTML form element names
P. Renaud ·
I post this here because the information is unfoundable on eZ, and is only available in the "Exponential basics" book... and is wrong.
After editing an object, you can redirect the user to a specific page. To do so, add the following in your template edit form :