By Geekzilla on

I am trying to find a way to allow certain members to Promote to Front Page and/or Sticky a post. I don't want these people to be able to edit the main pages of the site, so Node Administrator it seems is out. I'd appreciate any ideas you guys have, as I've lost at least 3% of my hair trying to find a working solution. Thanks.

⋅ Categories: Drupal 5.x

Comments

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

which implements separate permissions for these and works via AJAX.

http://drupal.org/project/fasttoggle

Geekzilla’s picture

Geekzilla commented

Fasttoggle would be perfect if it would respect content type permissions. For example, user1 has permission to create and edit only 'Custom Content Category A'. With fasttoggle user1 is able to sticky and promote any content (even front page stuff). I am wanting to restrict user1 to promoting and/or stickying only 'Custom Content Category A' content. Thanks for the suggestions nedjo.

blowski’s picture

blowski commented

Each fasttoggle menu item has a class, so you can edit your template files.

1. Make sure that node.tpl.php has a line like <div class="node-<?php print $node->type; ?>"> wrapped around the whole node.
2. Then in your CSS you can combine node types with fasttoggle options to hide them.

This will hide the status option on the node type 'page'.
.node-page .fasttoggle_status { display:none; }

This will hide the sticky option on the node type 'blog'.
.node-blog .fasttoggle_sticky { display:none; }

This will hide the promote option everywhere by default, and then turn it back on for the 'blog' type.
.node .fasttoggle_promote { display:none; } .node-blog .fasttoggle_promote { display:block; }

Although the options will still be in the HTML, they will at least be hidden on the screen. Not ideal, but it has worked as a hack for me until the module itself implements this functionality.

====
Dan Blows
Drupal Theme Developer
daniel@blowski.com

lucio.ferrari’s picture

lucio.ferrari commented

Am I too late?
I found another way, using Rules and CCK.

  • I inserted in my content types three CCK integer fields as on/off widgets, namely 'publish', 'promote' and 'sticky'.
  • Then I added a set of rules and a triggered rule
  • The latter is triggered when saving a node and as an action it runs the ruleset
  • In the ruleset 6 rules will publish/unpublish, promote/demote, stick/unstick according to what's in the fields