\CMS_Content_Manager

Manages orders in different states and handles events on orders.

The order manager should manage orders in different states and handle events on orders. Each implementation could define its own states and events for orders. However all implementations should handle the following events:

  • create: to create a new order this event will be occured
  • update: to update an order this event will be occured
  • delete: to delete an order this event will be occured

Note: If 'secureId' is sets in the REQUEST parameters, then access MUST not be checked.

Summary

Methods
Constants
createContentFilter()
apply()
transitions()
No constants found
No protected methods found
N/A
No private methods found
N/A

Methods

createContentFilter()

createContentFilter(\Pluf_HTTP_Request  $request) : \Pluf_SQL

Creates a content filter

This filter is used to list contents based on states and the request. For example, all contents will be displayed to the owner of the system.

Parameters

\Pluf_HTTP_Request $request

Returns

\Pluf_SQL

apply()

apply(  $order, String  $action, Boolean  $save = false) : \CMS_Content

Apply action on content

Each content must follow CRUD actions in life cycle. Here is default action list:

  • create
  • read
  • update
  • delete

Parameters

$order
String $action
Boolean $save

to save or not the content

Returns

\CMS_Content

transitions()

transitions(\CMS_Content  $order) : array

Returns possible transitions for given content

Returns possible transitions respect to currecnt state of given content.

Parameters

\CMS_Content $order

Returns

array —

array of transitions