Sun Nov 16, 2008
xPattern Groups and Permissions
I feel like I took a few big steps with xPattern. Groups and permissions are now served out of the database instead of from global variables hardcoded in to the core. This sets the groundwork for having a fully configurable security model.
The UI is not complete and I have a request for design help over on the xPattern forums. The basic functionality (add/delete/update) is implemented for both groups and permissions, but I have yet to put a UI in place to modify the permissions associated with a group. If anyone would like to help out an open source project by designing a user friendly UI for this action, please contact me.
Before the 1.0 release (release date not yet posted), I plan on adding more permission checks and plugin callbacks throughout the admin interface. This should give a finer level of control to sites that need it. My vision for the xPattern security model is to provide a simple, yet flexible set of controls to allow a plugin to add the desired business rules for a site.
A few examples that I would like to be able to implement with only plugins.
1. Restrict a set of users so they can only edit articles in specific sections.
2. Image and file quotas.
Comment
Commenting is closed for this article.
