This issue is similar to the one here:
http://drupal.org/node/480618
Revisioning works as expected when creating a new Content Profile node for the user but when editing an existing profile, revisions are being automatically published. I need to have website staff review changes made to these nodes before they can be made public.
Published, is unchecked in the content type's Workflow settings and Create new revision as well as New revision in draft, pending moderation are both checked. I've tried both New revision in draft settings with no luck.
If anyone has a workaround I'd love to hear it as I'm supposed to be launching this site this weekend. Otherwise, my PHP abilities are limited, but if someone can point me in the right direction I can try putting together a patch.
Comments
Comment #1
rdeboerIn its symptoms this appears similar to #611988: Don't automatically publish on revert.
The actual cause may be different though ....
Comment #2
kesmeby commentedI've solved the problem for myself, but the issue is still there. The problem appears to be path related. I had been using the "Show a tab at the user's page" option for users to create and edit their profile. The path to create or edit that node is something like:
example.com/user/user#/profile/content-type
Which works fine with Revisioning for creating the page, but bypasses Revisioning when editing the page.
If I use the "Include an edit link to the display" with the "Show a link to the content profile creation page, if there is no profile." options it then offers create and view links for the node at a more traditional path:
example.com/node/node#/add&destination=user%2Fuser#
example.com/node/node#/edit&destination=user%2Fuser#
This method works fine--although interestingly I don't think anything after the "/edit" or "/add" does anything since deleting it has no effect. Though please correct me if I'm wrong.
I decided to set this entry to bug report because at least it should be easy to remove the string off the end of the second set of URLs. And if it makes sense change the URL of the tab on the user page to link to the same as the other ones--although there may be a good reason not to do that.
Thanks for this module, it has been a life saver.
Comment #3
rdeboerThank you for your analysis and support, Kyle.
When I have some time I will investigate why the method using the tab causes a Revisioning-bypass.
Just so that I don't waste a lot of time reproducing the issue, can you please let us know what version of Content Profile you used?
Also, I'm wondering about the "traditional" links.... these would be generated by the Content Profile module, rather than Revisioning wouldn't they?
Rik
Comment #4
kesmeby commentedSorry I checked out for a while. I was using 6.x-1.0-beta4 of content profile.
And yes you are right those links are most likely generated by Content Profile. Sorry about that, I was pretty sleep deprived at the time.
Comment #5
rdeboerSounds like it's become a non-issue.
If there's still an issue, please reopen after testing with the latest and greatest versions of all modules involved.
Comment #6
rdeboer