The inline authoring features of Workplace Web Content Management can make creating, modifying, and approving content easy, by providing access to those authoring actions from the context of the Web site.
After an author indicates an action, the display portlet content is replaced with the authoring template for the specified content. The author can make any changes or additions, then select Save and close to see the change. Optionally, the authoring tool can be configured to save changes as a draft, then the normal workflow process for the content is enforced.
To enable inline editing, create an authoring tools component that provides the actions you want to make available. To disable an action, do not provide a design for that action.
Security is not bypassed by inline authoring, as users must still have the appropriate access to the item to perform any actions.
As Inline Authoring requires that end-users have access to both the ‘Item Type’ at the Library level and the individual item (for example to edit the current content, you need ‘edit’ access to the ‘Content’ Item Type within the library where the content resides plus edit access to the actual item), you can easily disable Inline Authoring on production rendering servers but not allowing end-users ‘edit’ access to item types on the rendering servers library.
NOTE: Using Inline Authoring within the Remote Rendering Portlet OR the WCM Servlet will cause the user to the redirected to the local Authoring Page, where as using Inline Authoring within the Local Rendering Portlet, will cause the authoring form to be shown within the Local Rendering Portlet. Forcing the Inline Authoring functionality to redirect to the Authoring Server
If you have a separate authoring and rendering environment and want to use Inline Authoring on your rendering server, then an alternative to setting up two way syndication between the Authoring and Rendering servers (which could cause problems if two users edit the same item on both servers), is to have the Inline Authoring links redirect to the Authoring Server.
Forcing the Inline Authoring functionality to redirect to the Authoring Server, is as simple as providing your own item layout for each action that creates the Inline Authoring link manually. For example, the ‘Edit’ item layout would be set to:
Where [authoring_server] should be replaced with the name of your authoring server (make sure that the authoring server is accessible from the rendering environment)
<a href="http://[authoring_server]/wps/myportal/wcmAuthoring?wcmAuthoringAction=edit&docid=com.aptrix.pluto.content.Content/<Placeholder tag=idnum/>" target="_blank"> Edit </a>
The above link will cause the browser to open a new window for displaying the authoring form. To show the authoring form in the current window (and thus navigate away from the website) remove the text target=’_blank’ from the link.
This concept can also be applied to force Inline Authoring links within the Local Rendering Portlet to go to the local Authoring Page (by making the URL relative, ie remove http:// : from the link), which is useful if your custom theme for the Local Rendering Portlet is incompatible with the authoring form
NOTE: For versions of WCM prior to 18.104.22.168, PK51011 is required for ‘Idnum’ Placeholder tag to work inside an Authoring Tools component
Writing your own custom 'New' Authoring Tools Link
Using a JSP component its possible to build your own custom 'New' authoring tools link that can utilise a specific sitearea and/or authoring-template as well as target a specific server... In WCM 6.1, this link can be further customised to specify values for one or more of the content's fields. See the attached 'customNewAuthoringToolsLink.jsp' for an example that works with WCM 22.214.171.124 and later, instructions for use are within the JSP itself.