Posted by Itangalo on October 20, 2011 at 8:33am
3 followers
Jump to:
| Project: | Rules |
| Version: | 7.x-2.x-dev |
| Component: | Module Integrations |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
This is a feature request to get some cool and useful example configuration provided when downloading Rules. The point of this is not to have people using it, but to get ideas as to what Rules can be used for – and clone and modify any setup they like. Kind of like the default views shipped with Views (and some other modules).
Example configuration can be:
- Creating path aliases for node/edit and user/edit pages
- Redirecting administrators to the content overview list when logging in
- …
Comments
#1
So how should we ship them? As small feature modules that one can activate?
#2
Some of the cooler Rules configuration requires other modules (such as Views or VBO), but it doesn't make sense to have a Configuration Example module being dependent on those.
What to do? Skip the cooler examples? Create two different modules? Have module_exist checks?
#3
Updated component.