contrib

My D6 module usage stats

I'm reviewing my modules to determine each of their popularity for #D7CX. I also use this window before a major release to decide if any of my modules should just shrivel up and blow away into the dust of history.

The following table is the list of modules where I am the node author, or lead maintainer simpler terms.

Project Users
node privacy byrole 2373
Similar Entries 1889
Countdown 1015
Atom 712
URL List 473
Troll 344
User Read-Only 268
Field Actions 223
Jammer 199
Session Limit 141
Anti Existing Field 77
Workflow Named Transitions 74
.mobi loader 69
.mobi 53
Workflow Private Comments 49
Log Search 41
Bookmarks with login reminders 31
Randomizer 9
State Reference 5
Advogato Import 0

Project Users
Masquerade 2924
DB Maintenance 2892
SaveGuard 1866
Submit Again 723
Redirect 403 to User Login 445
Inactive User 393
Login Security 308
Password policy 295
Frameprevention 111
Google Pagerank 87
Arooga 29


» deekayen's blog · Add new comment Topics: ·

CCK Content Permissions patch feature

The current distribution of CCK 6.x-2 provides a new module from 5.x that sets view and edit permissions at the field level. Certain roles might be only able to see a few fields of all that is available on a content type and edit none while others might be able to edit a few of those.

Content permissions has one glaring flaw IMO, which has to do with the read-only view status of a field. Let's say, for example, you have permission to view all fields on a content type, but only edit a few. The view page will look like normal, and the edit page will only show those fields which you have permission to edit. What's missing in that picture? You can't see the read-only fields on the edit form. In the cases I use content permissions, seeing the values of the read-only fields is valuable context to know what to change in the editable fields.

Luckily, cYu wrote a patch that adds the values of the read-only fields back to the edit form. I think since yched is such a busy person, he would feel better if other people tested the patch to leave their experiences as well.

Workflow Fields is another module that can set fields to be invisible or read-only, but depending on workflow state, however it does not use the new CCK 6.x field permissions hooks. Instead, it tries to search through the form's FAPI array to find various field settings such as #access and #disabled along with changing to a markup field type to change the handling of content. While more powerful than Content Permissions with regards to workflow awareness, the implementation might benefit from some patching to utilize more of the new CCK field access hook since it has a known buggy history trying to support the various features of the Date widget.


» deekayen's blog · 1 comment Topics: · ·
Syndicate content