Closed (fixed)
Project:
Drupal core
Version:
5.x-dev
Component:
node.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Dec 2005 at 17:06 UTC
Updated:
27 Jul 2007 at 14:57 UTC
modulo this thing:
http://drupal.org/node/40555
this patch adds a "toggle nodes sticky" role which is necessary for setting moderators for your forum that don't have full admin access.
See also: http://drupal.org/node/39330
| Comment | File | Size | Author |
|---|---|---|---|
| stickymod.patch | 1.86 KB | Wesley Tanaka |
Comments
Comment #1
drummThis is not critical and 'toggle nodes sticky' doesn't seem like a very understandable permission name.
Comment #2
Wesley Tanaka commentedThe main problem with core code appears to have been fixed with http://drupal.org/cvs?commit=50606
Comment #3
catchThere'd be quite a lot of value to having "sticky" "published" "in moderation" available to certain users for specific node types rather than the all or nothing with administer nodes. The content moderator module works along these lines although the UI is external to the normal edit page for nodes so it feels like a bit of a hack.
Comment #4
RobRoy commentedI've made a small beta release of http://drupal.org/project/override_node_options which will help alleviate this issue for 4.7.x and 5.x. Let's work on this in contrib and get it ready for D6 core. So please post issues/patches to that project.
Currently, there is just one perm but I plan on making them really granular, for each node type and/or each node publishing status. It will be a lot of perms so it's fine for contrib, but we'll have to think of a cleaner solution for core.
Comment #5
Wesley Tanaka commentedIndeed the problem in core was fixed in 5.x. With a combination of hook_form_alter and a hackish hook_nodeapi, it's possible to do this completely in a module in 5.1. An example can be found here
Comment #6
(not verified) commented