Revisions getting reverted when two translations are pending

@dinaish20,

I don't have a lot of experience with the 3.x branch however in my use cases I'm using the 2.x version and on the /admin/content view we're displaying titles of nodes in the current language without duplicates so the node only gets bulk processed once for all languages. Make sense?

With that said, there could be a bug in the 3.x branch, I will have to run some of my own tests.

You may wish to consider using the 2.x release instead however I don't understand your use case.

The 2.x release was made to publish all languages pending or most recent draft for the same node.

@joseph.olstad

Use case is simple.
Global content and its translations both are being edited at the same time.
And business wanted a way to bulk publish all so this module comes into picture.
So even if English or any other translation is published first, the remaining translations or global should still retain its changes.
It works find when a node without its translation is being edited and bulk publish pushed to live smoothly.

Issue with 2.0 is - it will move translations which are still being edited to live when only the global or English is published. I saw that configuration was introduced in 3.x so opted for that.

Let me know if I didn't explain it right.

Dinaish20, if you edit related translations at the same time like you mentioned you do you might be interested to try https://drupal.org/project/entity_translation_unified_form
This module has a few different configuration options, when publishing the revisions for all translations are marked as related , perhaps your revisions are not in sync this way.

There's also a one on top of the other mode

With that said, we're using the 2x branch of moderated_content_bulk_publish, I haven't actually used 3.x much at all yet.