You are here

function workbench_base_ui::edit_form_context in Workbench Moderation 7.2

File

modules/workbench_workflows/plugins/export_ui/workbench_base_ui.class.php, line 25
A base class meant to be extended by the workbench_workflows_ui, workbench_states_ui, workbench_events_ui.

Class

workbench_base_ui
@file

Code

function edit_form_context(&$form, &$form_state) {

  // Force setting of the node required context.
  // @todo, add a way of setting which entity type this state, event, workflow works with.
  $form_state['item']->requiredcontexts = array(
    0 => array(
      'identifier' => 'Node',
      'keyword' => 'node',
      'name' => 'entity:node',
      'id' => 1,
    ),
  );
  ctools_include('context-admin');
  ctools_context_admin_includes();
  ctools_add_css('ruleset');

  // Set this up and we can use CTools' Export UI's built in wizard caching,
  // which already has callbacks for the context cache under this name.
  $module = 'export_ui::' . $this->plugin['name'];
  $name = $this
    ->edit_cache_get_key($form_state['item'], $form_state['form type']);
  ctools_context_add_relationship_form($module, $form, $form_state, $form['relationships_table'], $form_state['item'], $name);

  // While these modules are in an experimental state, throw this message in
  // for some clarity.
  drupal_set_message(t("This is a screen where the CTools export UI needs customization to fit the needs of States/Events/Workflows.\n    <br /><br />\n    The idea here is that a site builder could start from an article node and bring in related contexts. For instance the relevant Organic\n    Group could be brought it with one of these relationship plugins. One the next screen the site builder can then use the relevant Organic Group\n    as the basis for access control. So the end user's access to this state/event/workflow could be restricted on an arbitrary condition of the Organic\n    Group, like its published status or taxonomy values.\n    <br /><br />\n    If you have an opinion on how to improve this UI please go to\n    <a href='http://drupal.org/node/1376258'>http://drupal.org/node/1376258</a>"), 'warning');
}