Pattern Syntax: Views

Documentation for the Patterns Views syntax is coming soon... for the time being refer to this example view action below.

Valid properties for "view" action

Coming soon...

YAML Example:

tag: view
action: update
name: view_test
description: This is a test view
tag: test
base: node
- name: default
- name: row_plugin
value: node
- name: row_options
teaser: 0
links: 1
comments: 1
- name: use_pager
value: 1
pager_element: 2
- name: items_per_page
value: 25
- name: title
value: Test
- name: empty
value: There are currently no posts to display.
- type: filter
name: node.type
operator: in
page: page
- type: filter
name: node.status
operator: =
value: 1
- type: sort
name: node.created
order: DESC
granularity: minute
- name: page

Pattern Syntax: Content (CCK)

Valid properties for "content" action

  • name (human readable name, unique, required)
  • type (machine-readable name, unique, required)
  • description
  • title_label
  • body_label
  • min_word_count
  • help (submission guidelines)
  • node_options (Workflow settings) - required when workflow settings contain additional options besides 4 Drupal core default ones (status, promote, sticky, revision)
  • status - alias for node_options['status']
  • promote - alias for node_options['promote']
  • sticky - alias for node_options['sticky']
  • revision - alias for node_options['revision']
  • has_body - set to 0 if you want to remove/omit body field from this content type
  • comment
          valid values:
          0 - Disabled,
          1 - Read only,
          2 - Read/Write (default)
  • comment_default_mode
          valid values:
          1 - Flat list - collapsed,
          2 - Flat list - expanded,
          3 - Threaded list - collapsed,
          4 - Threaded list - expanded (default)
  • comment_default_order
          valid values:
          1 - Date - newest first (default),
          2 - Date - oldest first

Pattern Syntax: User

Valid tags for <user>:

add user:

  • name (unique)
  • mail (unique)
  • password (as plain text)
  • roles
  • status (0 - block, 1 - activate)

edit user:

  • timezone (format +hhmm e.g. +0400, -0930)
  • contact (0 - disable, 1 - enable)

In case profile module (or any other module) adds additional fields to user registration form and those fields are required, pattern will fail if value for that field is not provided.


Follow the seven simple steps below to create a basic content publication workflow that will satisfy most of your requirements for revision moderation, using the Revisioning module. Then, if needed, further enhance content security with fine-grained access control through two more tutorials on publication workflow for categorized content with workflow states.

In this first tutorial we'll keep things simple. We'll present a solution to the following common scenario:

Authors write content that prior to being made publicly visible must be reviewed (and possibly edited) by moderators. Once the moderators have published content, authors should be prevented from modifying it while “live”, but they should be able to submit new revisions to their moderators.

Pattern Syntax: System

"theme" action

Set default theme. All other themes will be disabled at the same time.


"form" action

Form action allows you to execute any Drupal form that is not directly supported by patterns module.
This action has certain limitations - it can't support forms that require complex data types as arguments - only scalar values and arrays are supported.

Pattern Syntax: Profile


Drupal forms supported:

  1. Add New Profile Field (/admin/user/profile/add/*)
  2. Edit Profile Field (/admin/user/profile/edit/*)
  3. Delete Profile Field (/admin/user/profile/delete/*)

Available actions:

  1. profile

Depends on the following modules:


Subscribe with RSS Subscribe to RSS - Site administrators