I've just encountered this issue as well and am thinking in my case at least, that it's relating to a few other unresolved issues I've been trying to piece together.
In my case, I've built an administrative dashboard that contains programmatically generated links to VBO pages that include arguments relating to the site's content. It's not uncommon for a webmaster to to see a list of these links and open many of them in new tabs to take care of an administrative process.
Because of the issue raised here: https://www.drupal.org/project/views_bulk_operations/issues/3083237 → , the same tempstore is attempted to be used (since the user id, view and display id are all the same) and so my guess is that the attempt to utilize this is creating the exception.
This is also then leading to this issue: https://www.drupal.org/project/views_bulk_operations/issues/3199115 → where in my case, opening a second tab of the same view and then checking boxes in one of the earlier opened tabs leads to a state where possible entity ids saved in the final tempstore dont' line up with the acceptable ones from the first tab opened.
Which leads to the most disastrous case of all, particularly if there's no confirmation screen - if I've checked one box on my initial tab and selected to "delete" an entity, but the VBO executes with NO entities selected, it moves forward like I've chosen to delete ALL entities in my display, i.e.: https://www.drupal.org/project/views_bulk_operations/issues/3199534 🐛 On configure form every entity is selected when user didn't select anything Needs work (I'm trying to find the other issue that referenced this problem, but it's a known configuration I believe that going to process with nothing checked implies that ALL are checked).
If others are encountering this on the 2.x branch, there appears to be an issue where there are new fields when editing the content type that isn't saved into config until you go to the edit form for the bundle and click "save". Doing this caused the image style options to show up again for me!
Yep, confirmed here as well. This all has to be CF changes I'd guess? It's a little unclear how often Chrome updates as they happen in background...
matthensley → created an issue.
Will the 7x version of the plugin be affected by this change as well?
matthensley → created an issue.
matthensley → created an issue.