PHPXRef 0.7 : Drupal 6 (gatewave) : Detail view of page

Functions

Functions that are not part of a class:

page_manager_list_page($js = NULL) X-Ref

Output a list of pages that are managed.

page_manager_get_pages($tasks, &$pages, $task_id = NULL) X-Ref

Sort tasks into buckets based upon whether or not they have subtasks.

page_manager_list_pages_form(&$form_state) X-Ref

Provide a form for sorting and filtering the list of pages.

page_manager_list_pages_form_submit(&$form, &$form_state) X-Ref

Accept submission from the page manager sort/filter form and apply it
to the list of pages.

page_manager_edit_page($page) X-Ref

Render the edit page for a a page, custom or system.

page_manager_edit_page_operation() X-Ref

Entry point to edit a single operation for a page.

param: $js
param: $page
param: ...

page_manager_get_operations($page, $operations = NULL) X-Ref

Take the operations array from a task and expand it.

This allows some of the operations to be dynamic, based upon settings
on the task or the task's handlers. Each operation should have a type. In
addition to all the types allowed in page_manager_render_operations, these
types will be dynamically replaced with something else:
- 'handlers': An automatically created group that contains all the task's
handlers and appropriate links.
- 'function': A callback (which will be placed in the 'function' parameter
that should return an array of operations. This can be used to provide
additional, dynamic links if needed.

page_manager_get_handler_operations(&$page) X-Ref

Collect all the operations related to task handlers (variants) and
build a menu.

page_manager_get_operation($operations, $trail) X-Ref

Get an operation from a trail.

return: array($operation, $active, $args)

page_manager_get_operation_content($js, &$page, $trail, $operations) X-Ref

Fetch the content for an operation.

First, this drills down through the arguments to find the operation, and
turns whatever it finds into the active trail which is then used to
hilite where we are when rendering the operation list.

The arguments are discovered from the URL, and are an exact match for where
the operation is in the hierarchy. For example, handlers/foo/settings will
be the operation to edit the settings for the handler named foo. This comes
in as an array ('handlers', 'foo', 'settings') and is used to find where the
data for that operation is in the array.

_page_manager_get_operation_content($js, &$page, $active, $operation, $titles = array() X-Ref

Fetch the content for an operation, after it's been discovered from arguments.

This system runs through the CTools form wizard. Each operation specifies a form
or set of forms that it may use. Operations may also specify wrappers and can
set their own next/finish handlers so that they can make additional things happen
at the end.

page_manager_operation_wrapper(&$form, &$form_state) X-Ref

No description

page_manager_edit_page_finish(&$form_state) X-Ref

Callback generated when the an operation edit finished.

page_manager_edit_page_next(&$form_state) X-Ref

Callback generated when the 'next' button is clicked.

All we do here is store the cache.

page_manager_edit_page_cancel(&$form_state) X-Ref

Callback generated when the 'cancel' button is clicked.

All we do here is clear the cache.

page_manager_render_operations(&$page, $operations, $active_trail, $attributes, $location, $parents = array() X-Ref

Render an operations array.

This renders an array of operations into a series of nested UL statements,
with ajax automatically on unless specified otherwise. Operations will
automatically have the URLs generated nested.

Each operation should have a 'type', which tells the renderer how to deal
with it:
- 'operation': An AJAX link to render. This is the default and is
assumed if a type is not specified. Other fields for the operation:
- - 'title': The text to display. Can be an image. Must be pre-sanitized.
- - 'description': Text to place in the hover box over the link using the
title attribute.
- - 'arguments': Anything optional to put at the end of the URL.
- - 'path': If set, overrides the default path.
- - 'no operations': If set, the path will not have operations appended.
- - 'no task': If set, the path will not have the task id.
- - 'no link': If set, this item will just be text, not a link.
- - 'ajax': If set to TRUE, ajax will be used. The default is TRUE.
- - 'class': An optional class to specify for the link.
- - 'form': The form to display for this operation, if using a single form.
- - 'forms': An array of forms that must be paired with 'order' of this
operation uses multiple forms. See wizard tool for details.
- - 'order': The form order to use for multiple forms. See wizard tool for
details.
- - 'form info': Form info overrides for the wizard. See the wizard tool
for available settings
- 'group':
- - 'title': The title of the link. May be HTML.
- - 'title class': A class to apply to the title.
- - 'children': An array of more operations that this group represents.
All operations within this group will have this group's ID as part
of the AJAX url to make it easier to find.
- - 'class': A class to apply to the UL of the children.
- - 'collapsible': If TRUE the collapsible tool will be used.

page_manager_save_page_form(&$form_state) X-Ref

Provide a simple form for saving the page manager info out of the cache.

page_manager_save_page_form_submit(&$form, &$form_state) X-Ref

Save the page.

page_manager_save_page_form_cancel(&$form, &$form_state) X-Ref

Discard changes to the page.

page_manager_handler_add(&$form, &$form_state) X-Ref

Add a new task handler.

page_manager_handler_add_submit(&$form, &$form_state) X-Ref

Handler related forms.

page_manager_handler_add_finish(&$form_state) X-Ref

Finish the add process and make the new handler official.

page_manager_handler_add_cancel(&$form_state) X-Ref

Throw away a new handler and return to the add form

page_manager_handler_add_form(&$form, $form_state, $features = array() X-Ref

Provide a consistent UI for adding handlers.

page_manager_handler_import(&$form, &$form_state) X-Ref

Rearrange the order of variants.

page_manager_handler_import_validate($form, &$form_state) X-Ref

Make sure that an import actually provides a handler.

page_manager_handler_import_submit($form, &$form_state) X-Ref

Clone an existing task handler into a new handler.

page_manager_handler_rearrange(&$form, &$form_state) X-Ref

Rearrange the order of variants.

page_manager_handler_rearrange_submit(&$form, &$form_state) X-Ref

No description

_page_manager_handler_sort($a, $b) X-Ref

Used as a callback to uasort to sort the task cache by weight.

The 'name' field is used as a backup when weights are the same, which
can happen when multiple modules put items out there at the same
weight.

page_manager_handler_delete(&$form, &$form_state) X-Ref

Rearrange the order of variants.

page_manager_handler_delete_submit(&$form, &$form_state) X-Ref

Submit handler to delete a view.

page_manager_handler_export(&$form, &$form_state) X-Ref

Entry point to export a page.

page_manager_handler_clone(&$form, &$form_state) X-Ref

Rearrange the order of variants.

page_manager_handler_clone_submit($form, &$form_state) X-Ref

Clone an existing task handler into a new handler.

page_manager_handler_enable(&$form, &$form_state) X-Ref

Form to enable a handler.