Posted by nektir on March 19, 2009 at 10:35pm
Jump to:
| Project: | Publish Content |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
I'm trying to use this with Revision Moderation module. It seems when my book content type has the setting "New revisions in moderation", the users that have "publish book content" permission from this module are no longer allowed to publish content book content.
Comments
#1
I should note... The book content type is set to "unpublished" by default. It does work when I change my book content type to "published" by default, but I need it to be "unpublished" by default.
#2
This is related to an issue with Revision Moderation that effectively prevents publishing/unpublishing without creating a new revision... or something. Not sure I fully understand, but it's definitely beyond the control of Publish Content.
You might try modr8 and see if it works for you?
If all else fails, you can use the following hack, which will probably never make it into this module:
--- publishcontent.module (saved version)+++ publishcontent.module (current document)
@@ -97,7 +97,7 @@
*/
function publishcontent_toggle_status($node) {
$node->status = !$node->status;
- node_save($node);
+ db_query('UPDATE {node} SET status = %d WHERE nid = %d', $node->status, $node->nid);
drupal_set_message(_publishcontent_get_message($node->nid, $node->title, $node->status));
drupal_goto('node/'. $node->nid);
}
#3
P.S. Here are two of the relevant issues in the Revision Mod queue:
#156269: Publishing a previously unpublished node with new revision moderation checked does not get published
#496014: Revision_moderation don't save options (status, promoted, sticky)