Caution: This documentation is for eZ Publish legacy, from version 3.x to 6.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

action

Summary

Provides an interface to different actions (AddToBasket, SwapNode, etc.).

Balazs Halasy (21/03/2005 7:54 am)

Balazs Halasy (10/04/2005 12:51 pm)

Comments

  • HTML form element names

    Tuesday 20 December 2005 9:39:22 am

    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

      Friday 21 April 2006 6:11:03 pm

      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

      Friday 21 April 2006 6:17:32 pm

      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}" />