Closed (duplicate)
Project:
Workbench Moderation
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Jul 2011 at 08:06 UTC
Updated:
15 May 2013 at 19:21 UTC
Workbench Moderation looks really helpful.
Unfortunately, all workflows are currently purely node centric.
Other entities, like commerce_product, should become integrated into the workflows as well.
Comments
Comment #1
stevectorAny other entity type would have to be revisionable and have an analog to the published/unpublished concept to integrate with Workbench Moderation.
Comment #2
robeano commentedI agree with #1215974-1: provide workflow for non-node entities as well, and I would love to see revisions on user entities. Will it happen? Not sure at this time. Leaving open and lowering priority.
Are there any other entities which provide revisions and a published/unpublished state? If so, it would be worth investigating to see what it takes to offer wb_moderation to other entities in a generic way.
Comment #3
stevectorThere is a module for user_revisions at least. http://drupal.org/project/user_revision The blocked status is somewhat analogous to node's published status.
I don't think that'd be a common use case. I think a site would more likely need to moderate a user toward a higher role, or organic group maybe.
Comment #4
stevectorI no longer think the "published" endpoint is a requirement here. We've thought about having different workflows for nodes like a one that leads to an already published node getting promoted to the frontpage. If have this "workflow" concept for nodes, I think we could have it for any entity.
Comment #5
k_zoltan commentedThis feature would be great for User Profiles (http://drupal.org/project/profile2) for Organizations that like to control the presentation of there Sales Persones. In this way every time a person changes its profile the Marketing and Communication section could overview it and moderate it, but until then to still have the latest version online ("published").
Also for Private messages (http://drupal.org/project/profile2) an Organization sometimes likes to communicate with there clients using this features. There may be some internal communication rules, that the supperiors would like to filter, suggest correction for there employe.
I got these two requests from a client and would be really happy if there would be some easy way to implement this.
Comment #6
stevectorWe should keep this in mind with the work in #1316314: Workflow Architecture for Workbench Moderation
Comment #7
Brian MacKinney commentedI also have a client requesting moderation for private messages, which are entities. All I can offer him is a rule that notifies an elevated role of the existence of the message, and the permission for that role to delete it. To be effective, recipients are not notified of new messages by email, and the elevated user has to review the message before the recipient logs in to the site.
Comment #8
stevectorComment #9
stevectorThis functionality will come from State Machine under the current working plan for 2.x discussed at http://groups.drupal.org/node/198188
I've made a ticket in State Machine to cover this: #1294880: Convert Workbench Moderation records to entities
Comment #10
lonehorseend commentedTaxonomy terms! Desperately need this for that.