You are here

README.txt in Context 6.3

Context UI
----------
Context UI provides an administrative interface for managing and editing
Contexts. It is not necessary for the proper functioning of contexts once they
are built and can be turned off on most production sites.


Requirements
------------
- Context, Context UI modules enabled (`admin/build/modules`)
- [jQuery UI 1.x][1] and [Admin 2.x][2] to use the inline context editor.
  Optional.


Basic usage
-----------
As a site administrator you can manage your site's contexts at
`admin/build/context`. The main page will show you a list of the contexts on the
site and give you some options for managing each context.

When editing or adding a new context, you will be presented with a form to
manage some basic information about the context and then alter its conditions
and reactions.

- `name`: The name of your context. This is the main identifier for your context
  and cannot be changed after you've created it.
- `description`: A description or human-readable name for your context. This is
  displayed in the inline editor if available instead of the name.
- `tag`: A category for organizing contexts in the administrative context
  listing. Optional.

**Conditions**

When certain conditions are true, your context will be made active. You can
customize the conditions that trigger the activation of your context.

- **Condition mode**: you can choose to have your context triggered if **ANY**
  conditions are met or only active when **ALL** conditions are met.
- **Adding/removing conditions**: you can add or remove to the conditions on
  your context using the conditions dropdown.
- **Individual settings**: most conditions provide a simple form for selecting
  individual settings for that condition. For example, the node type condition
  allows you to choose which node types activate the context.

**Reactions**

Whenever a particular context is active, all of its reactions will be run.
Like conditions, reactions can be added or removed and have settings that can
be configured.


Using the inline editor
-----------------------
If you have installed jQuery UI and Admin, you can enable the inline context
editor:

1. As an administrative user go to `admin/settings/admin`.
2. Check the 'Context editor' block and save.
3. When viewing a page with one or more active contexts, you will see the
  `Context editor` in the admin toolbar.
4. You can use the context editor to adjust the conditions under which each
  context is active and alter its reactions.


[1]: http://drupal.org/project/jquery_ui
[2]: http://drupal.org/project/admin

File

context_ui/README.txt
View source
  1. Context UI
  2. ----------
  3. Context UI provides an administrative interface for managing and editing
  4. Contexts. It is not necessary for the proper functioning of contexts once they
  5. are built and can be turned off on most production sites.
  6. Requirements
  7. ------------
  8. - Context, Context UI modules enabled (`admin/build/modules`)
  9. - [jQuery UI 1.x][1] and [Admin 2.x][2] to use the inline context editor.
  10. Optional.
  11. Basic usage
  12. -----------
  13. As a site administrator you can manage your site's contexts at
  14. `admin/build/context`. The main page will show you a list of the contexts on the
  15. site and give you some options for managing each context.
  16. When editing or adding a new context, you will be presented with a form to
  17. manage some basic information about the context and then alter its conditions
  18. and reactions.
  19. - `name`: The name of your context. This is the main identifier for your context
  20. and cannot be changed after you've created it.
  21. - `description`: A description or human-readable name for your context. This is
  22. displayed in the inline editor if available instead of the name.
  23. - `tag`: A category for organizing contexts in the administrative context
  24. listing. Optional.
  25. **Conditions**
  26. When certain conditions are true, your context will be made active. You can
  27. customize the conditions that trigger the activation of your context.
  28. - **Condition mode**: you can choose to have your context triggered if **ANY**
  29. conditions are met or only active when **ALL** conditions are met.
  30. - **Adding/removing conditions**: you can add or remove to the conditions on
  31. your context using the conditions dropdown.
  32. - **Individual settings**: most conditions provide a simple form for selecting
  33. individual settings for that condition. For example, the node type condition
  34. allows you to choose which node types activate the context.
  35. **Reactions**
  36. Whenever a particular context is active, all of its reactions will be run.
  37. Like conditions, reactions can be added or removed and have settings that can
  38. be configured.
  39. Using the inline editor
  40. -----------------------
  41. If you have installed jQuery UI and Admin, you can enable the inline context
  42. editor:
  43. 1. As an administrative user go to `admin/settings/admin`.
  44. 2. Check the 'Context editor' block and save.
  45. 3. When viewing a page with one or more active contexts, you will see the
  46. `Context editor` in the admin toolbar.
  47. 4. You can use the context editor to adjust the conditions under which each
  48. context is active and alter its reactions.
  49. [1]: http://drupal.org/project/jquery_ui
  50. [2]: http://drupal.org/project/admin