Take the 2-minute tour ×
Drupal Answers is a question and answer site for Drupal developers and administrators. It's 100% free, no registration required.

I am using node clone 7.x-1.0-rc2 module.It is creating clone for a particular node.Now if i published clone.How to override parent node with clone node. Is there any other way or module for doing this?

I am using workbench and my scenario is that i have three types of user contributor,validator and publisher. only contributor can create node and assign it to validator, now here validator can revert to contributor or assign to publisher.Publisher can publish this node or revert to validator.Now i am creating a clone of this node and again send it to contributor and contributor send it to publisher but when publisher wants to publish this clone so old content get update this clone node's content or delete old one and become this node as a parent node.

share|improve this question
    
What do you mean by "override parent node", exactly? –  Mołot Mar 4 at 7:39
    
Just when i published my clone node the parent node content deleted or updated with clone node content. –  Fawwad Mar 4 at 7:44
1  
Ok... so why would you need a clone at all in that case? Why not to simply create a revision for the original node? –  Mołot Mar 4 at 7:45
    
I am using workbench and my scenario is that i have three types of user contributor,validator and publisher. only contributor can create node and assign it to validator, now here validator can revert to contributor or assign to publisher.Publisher can publish this node or revert to validator.Now i am creating a clone of this node and again send it to contributor and contributor send it to publisher but when publisher wants to publish this clone so old content get update this clone node's content or delete old one and become this node as a parent node. –  Fawwad Mar 4 at 7:56
1  
overriding might be too broad too handle, consider if your parent node is assigned to a menu item and you are deleting it, make sure when you say overriding you do not mean two nodes with same nids, as Molot suggested revisioning should be what you are looking for. –  arpitr Mar 4 at 7:58
show 2 more comments

1 Answer 1

It looks that you are trying to implement elaborated workflow using node cloning approach.

I strongly suggest you to use Workflow module instead:

This module allows you to create arbitrary Workflows, and assign them to Entities.

Workflows are made up of workflow states. Transitions between states can be allowed per role. For example, a workflow with the states Draft, Review, and Published could be assigned to the Story node type. Only users with role 'chief editor' can set Stories to the published state. You can set up the Workflow to alter states from form, page, comment and a special workflow tab.

Transitions between workflow states can have actions assigned to them. In our example, we could assign an action so that when the story moves from the Draft state to the Review state an email is sent out. Another action could be assigned to the transition from Review to Published so that the node's status is set to Published (and becomes visible on your website).

It is there, it works, and it seems to cover all your needs in one, integrated solution. Even it's example use case is almost exactly like your use case here.

If you want to configure it at revision level more easily, there is also Revisioning, "a module for the configuration of workflows to create, moderate and publish content revisions".

You use it in scenario's like this:

  • Authors write content that prior to being made publicly visible must be reviewed (and possibly edited) by moderators. Once the moderators have published the content, authors should be prevented from modifying it while “live”, but they should be able to submit new revisions to their moderators.
  • We shouldn't have to grant these roles “god-like” powers (e.g. D6's "administer nodes" permission) to implement this.
share|improve this answer
    
@Fawwad see my updated answer –  Mołot Mar 4 at 8:13
    
You are right Molot even all things works as it is in workbench what ever you explained above.But in my case if publisher want to change in node content and assign it to contributor and then validator it will not affect published node until clone node published.Is there any ways we can update our old published node with this new clone content. –  Fawwad Mar 4 at 8:18
    
@Fawwad right, for that specific scenario Revisioning seems a bit better suited. I heard Workflow can be made to work that way, too, but don't havean access to details, and Revisioning seems simpler. –  Mołot Mar 4 at 8:22
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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