Whoa, I updated to 7.x-3.3 and tried to create a bulk operation to delete all the archived revisions of my nodes. Thankfully I didn't try clean up all my nodes, but only tested it on one node. Bulk operation apparently went wild and messed with the published node as well. Not sure what the bug is, but in summary I tried to use bulk operations to delete my archived revisions and it went out of bounds and half way deleted a non-archive published node.

My mistake, but I was confidently shooting from the hip and did not test the feature on my staging site. So it took a while to manually delete the published node elements so that I could properly reconstruct my node. I think I'll use this module much more carefully in the future.

Priority as major because this could potentially ruin all the nodes of an enter site!

Comments

webservant316 created an issue.

webservant316’s picture

I would love to get this working properly because it is a better and more standard solution than some of the node revision delete modules.

webservant316’s picture

maybe the problem is that I am using the module 'revisioning' which may do odd things with the archive flag.