Home ›
Agaric wants CCK Field Permissions to have smarter defaults (let the world see!)Agaric wants CCK Field Permissions to have smarter defaults (let the world see!)
Submitted by Benjamin Melançon on May 1, 2009 - 5:58pm
Searched words:
content field permissions CCK drupal default
perms
Enabling CCK Field Permissions (cck_field_perms in Drupal 5, part of CCK itself in Drupal 6) can create bugs on your if you aren't paying attention and cleaning up after it.
Some excerpts from IRC among people trying to figure out why an image on a news post simply wasn't showing up (for the user who posted it in this case, the authenticated role had editing but not viewing rights for the imagefield!).
i don't see any thumbnails - including for my test post - on the news page in FF3-linux or IE7
that's strange indeed. I have compared your request to the post with mine and the servers response to your request is much shorter and it does not fire the request for the image.
this smells like a very hard-to-debug bug
log out > clear cache > log in > refresh -- still no images
It would really really help if when you installed the moule, and for each new field, it defaulted to being viewable and editable.
The problem probably is that there's no way to know when something is a new permission. Well not by default. We could keep track ourselves though. Hacky, but it would make CCK Field Permissions much more usable.
Resolution
More like this
- Agaric wants Programmatic CCK field addition
- Permission sets for sensible defaults in module-provided permissions to roles
- Custom nodes module AND CCK: Bdragon serves you cake and lets you have it, too
- RE: Node access module (based on users listed in userreference fields)
- Node Authors module: give multiple people edit rights to specific content based on userreference field
Comments
Post new comment