Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.After updating to the latest dev version of revisioning today, my nodes are getting automatically published after initial save. This was not happening before the update. Seems to be a bug with the new way nodes are tested for auto publishing possibly?
Comments
Comment #1
rdeboerOops, we'll have to look into this asap.
Comment #2
rdeboerI have just tried this but cannot reproduce it, unless the "Published" box is ticked on the content type.
Are you sure the Published box is UNTICKED at Structure >> Content Types >> edit >> Publishing options ?
Can you please mention steps to reproduce this error?
Comment #3
acbramley commentedNo the published tickbox is unticked.
To reproduce I simply updated to the latest dev version of revisioning, and attempted to create a new page in draft. When I hit save, my content was published.
Comment #4
rdeboerSo I downloaded the tar ball from the project page (17 Jan, the one from 24 Dec is no more for reasons we won't advertise) and verified through the diff command that all files are the same to what's in Git. The only difference is the .info file, which the packaging script curiously sets to 7.x-1.2+28-dev (?).
I enabled Revisioning and the Revisioning Scheduler (optional).
In my case I was logged in as uid=1, but naturally all of this should work for any role with the right permissions.
I went to the Structure >> Content types >> edit (Article) and under "Publishing options" UNticked "Published", then ticked "Create new revision" and "New revision in draft, pending moderation".
Also pressed "Every time article content is updated" and UNticked "Auto-publish drafts of type article".
"Save content type".
Content >> Add content >> Article. Enter title, body, attachment, etc.
I make sure to erase the publication date, which by default is set to "now" (naturally when you don't have Revisioning Scheduler installed this field does not appear).
Press Save.
New revision is created. NOT published, yet. All good....
Can you please confirm that when you follow the above steps the new content created incorrectly appears published on your system?
Also when you visit admin/config/content/revisioning, what content access modules are reported for your system?
Comment #5
rdeboerI've also changed the inline scheduled publication date/time default, so that the node won't be published if you don't edit the date/time.