In our use case we would like node clone to respect the default publishing options for each content type. For example, if we are cloning an already published node of type 'page', but nodes of type 'page' are unpublished by default, we would prefer that the new node is unpublished.
The attached patch changes node_clone to do this. I think this behaviour is preferable to the current behaviour, but perhaps this should be configurable?
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | clone_settings_5_0.diff | 6.18 KB | pwolanin |
| publishing_options_patch.txt | 775 bytes | mleicester |
Comments
Comment #1
mcurry commented+1 on the suggestion
I was going to build my own cloner module, but I found this one. So, I may be doing some tweaks or feature enhancements and submitting a patch or two myself.
Comment #2
pwolanin commentedI would prefer to see this as a configurable option on a settings page, but I think it would be a potentially useful feature.
Actually, the best version might be to be able to configure the behavior on a per-node-type basis and/or based on the "administer nodes" permission.
Comment #3
pwolanin commentedcombining this issue with: http://drupal.org/node/81882
The patch attached addresses both feature requests.
Please give me your feedback on these changes.
Comment #4
pwolanin commentedpatch committed
Comment #5
pwolanin commented