0

I'd like to provide a way for anonymous users to submit nodes, but also provide suggested edits to existing nodes. The core node revision system cannot support this.

How would one implement a revisioning system that allow anonymous users to save updates which moderators approve. I'm assuming Workbench might get me halfway there.

Edit: like you find on Foursquare and Yelp, for community suggestions on editing venues.

Improve this question
6
  • Are you trying to reinvent Revision Moderation, only with different wording of description>?
    – Mołot
    Commented Jun 30, 2015 at 20:33
  • I think, it's the ability to create revisions which queue up. Like the edit functionality found on Foursquare or Yelp (will update question with that reference.)
    – Matt Glaman
    Commented Jun 30, 2015 at 20:42
  • So all ou want to do is to allow one role to edit, but don't allow their revisions to be automatically published? Probably module i linked is for you
    – Mołot
    Commented Jun 30, 2015 at 20:44
  • But that's unmaintained and D6, so not quite
    – Matt Glaman
    Commented Jun 30, 2015 at 20:44
  • well... worth it as idea / code source, not as ready made solution, true that. that's why i didn't post an answer.
    – Mołot
    Commented Jun 30, 2015 at 20:47

1 Answer 1

Reset to default
0

I think you may want to check out the Workbench Moderation module. Basically, you'd configure a workflow that allows anonymous users to 'edit' a node, but their edits would trigger the workflow. From an admin experience perspective, you may want to configure it to trigger an email notice whenever updates have been made, or otherwise alert content admins that suggestions have been made.

One potential gotcha is the way that Workbench handles revisions -- it doesn't fork. Meaning that if you publish a node, that becomes revision 1. If someone comes along and edits it, they suggest revision 2. If a third person comes along, they'll see that the node is on revision 1, but when they go to edit the node, they'll see it's on revision 2. Any changes would be saved as revision 3, and so on. You may need to extend the module with your own custom workflow if you're looking for forking behavior (think pull requests on GitHub).

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.