Patterns fork on GitHub

@ChrisBryant

Hey Chris, yeah I've been in touch with the guys and hopefully we can roll these changes into the mainline trunk soon. Till then I'll keep the github fork updated with my latest changes.

An update on the Github fork (http://github.com/hiddentao/patterns2).

- After loading the specified modules, we now clear all caches before running
the actions, to ensure that certain actions (e.g. setting user permissions on
CCK fields) work as expected.

- Fixed bugs involving the use of inside sub-patterns and in form synchronization code.

Finally, two new patterns:

1) Added a 'menu_trail' tag which allows you to configure the Menu Trails module
(node type <-> menu mappings) using a pattern.

Example:

   <menu_trail>
      <menu>
        <parent>Primary links</parent>
        <item>Home</item>
      </menu>
      <type>Shows</type>
    </menu_trail>

This will ensure that when viewing a node of the 'Shows' type the 'Home' link in
the 'Primary links' menu is set to be the active menu.

Example:

   <menu_trail>
      <menu>
        <parent>primary-links</parent>
        <item>Home</item>
      </menu>
      <type>shows</type>
    </menu_trail>

This does the same thing as example 1 except that we now use the internal
machine names rather than the human-readable names.

2) Added a 'patterns-config' tag which allows you to configure the pattern
processor at runtime by toggling varous flags. At the moment only one flag is
supported:

- ignore-failed-actions: if turned on (default is off) then the pattern will no longer fail if one or more actions fail to execute properly.

How to use this flag:

  <actions>

    <!-- Turn the flag ON -->
    <patterns-config name="ignore-failed-actions" value="1" />

    ...here run some actions which aren't all expected to pass...

    <!-- Turn the flag OFF -->
    <patterns-config name="ignore-failed-actions" value="0" />

  </actions>

@klktrk, the github fork I'm building is definitely production-ready since my team and I are using it in our client work. But like you said, you can just create your own fork if you like (gotta love git!). If the changes look good I'll merge them into mine.

-- http://github.com/hiddentao/patterns2 --

Tags to control how patterns appear in the admin page

Added two new tags (to be placed inside ) for controlling how a pattern
appears in the list on the patterns admin page...

1) subpattern_only - Using this tag tells Patterns module that the pattern is
not to be run on its own, but rather, only as a sub-pattern of another pattern.
It causes the pattern to appear in the admin page list but without a 'Run' link.

Example usage:

  <info>
    <title>Test pattern</title>
    <description>A pattern that cannot be run on its own</description>
    <author>Foo Bar</author>
    <author_email>foo@bar.com</author_email>
    <version>1.0</version>
    <category>Test patterns</category>
    <core>6.x</core>
    <subpattern_only>1</subpattern_only>
  </info>

Note that if if the tag's content is set to 0 or if the tag is
ommitted then the pattern will appear as normal.

2) hidden - Using this tag tells Patterns module that the pattern is not to be
shown on the admin page patterns list.

Example usage:

  <info>
    <title>Test pattern</title>
    <description>A pattern that doesn't get shown on the patterns admin 
    page</description>
    <author>Foo Bar</author>
    <author_email>foo@bar.com</author_email>
    <version>1.0</version>
    <category>Test patterns</category>
    <core>6.x</core>
    <hidden>1</hidden>
  </info>

Note that if if the tag's content is set to 0 or if the tag is ommitted
then the pattern will appear as normal.

Running patterns without using batch API

Added the ability to execute a pattern programmatically without using the batch
API. This allow for patterns to be run from within hook_update()
implementations, which themselves use the batch API.

Example usage:

patterns_execute_pattern_immediate('patter name', 
array('run-subpatterns'=>TRUE));

The following syntax also works:

patterns_execute_pattern('patter name', array('run-subpatterns'=>TRUE), 
'immediate');