I only have two states on the site I'm working on: Draft and Published. If I use VBO to moderate an existing node's current draft to Published, it appears that both the draft and the old published version are set to Published, but the old one is made Current.
Here's a screenshot:
Revision 1614 is my draft — when I view it it looks how I want it to — but the old revision, 1578, gets a Published --> Published moderation at the same timestamp as the Draft --> Published on 1614.
(There are several other VBO-related issues open, but I think this may be different from all of them. Apologies if it's a dupe.)
Comment | File | Size | Author |
---|---|---|---|
#10 | Screenshot from 2020-07-20 15-25-34.png | 110.4 KB | hmdnawaz |
#8 | vbo-2844723-8.patch | 615 bytes | govind.maloo |
Screenshot 2017-01-18 at 14.41.02.png | 54.88 KB | Lanny Heidbreder |
Comments
Comment #2
Lanny Heidbreder CreditAttribution: Lanny Heidbreder commentedComment #3
vikrama1k1 CreditAttribution: vikrama1k1 as a volunteer and commented+1 having same issue.
Please help @75th Trombone ,if you have solved the issue
Comment #4
vikrama1k1 CreditAttribution: vikrama1k1 as a volunteer and commentedProblem Solved
downgrading module to the older version of (Workbench Moderation 7.x-1.4) solved my problem.
Comment #5
jday CreditAttribution: jday commentedWe see the same issue using VBO 7.x-3.5, Workbench Moderation 7.x-3.0, and Drafy 7.x-1.0-rc1 so far no luck tracking down the odd behavior.
Comment #6
govind.maloo CreditAttribution: govind.maloo at Salsa Digital commentedHi
In Workbench Moderation 7.x-3.0 entity_presave and hook_node_insert/update is calling the same function multiple time and causing misjudgement in state and revision by an external event from other modules.
Comment #8
govind.maloo CreditAttribution: govind.maloo at Salsa Digital commentedCorrect patch
Comment #10
hmdnawaz CreditAttribution: hmdnawaz commented@govind.maloo your patch works. But the problem is it sets the published version into draft and set it as current revision.
Therefore this patch can't be used. Is there any workaround for this?
Comment #11
hmdnawaz CreditAttribution: hmdnawaz commentedThe patch in https://www.drupal.org/project/workbench_moderation/issues/3160301#comme... fixes the issue.
Comment #12
agentrickard