Can Actions Permissions be reinstated?

Q1: Short answer: Action attribute class in core doesn't allow any additional parameters anymore like annotations did and the module relied on that.
Q2: Because I chose so. The module has absolutely no funding, it's only my courtesy that it still exists, is actively maintained and supported and I don't have any use cases for the submodule anywhere. No one is forced to upgrade to the latest version and everyone is welcome to rewrite the Actions Permissions module and maintain it as a separate contrib project.

Please update the issue title to something meaningful so maybe someone will work on it.

I can work on this but not as a free work as I'm not using this on any of my projects and have enough work with Drupal LMS that I'm doing for the community currently. If anyone else would like to rewrite the module to work with the current API - I'll also support that work.

I recommend those that need it to stay on 4.2.x before it is recreated this way or the other.

Hello Graber,
Thank you for your work on this module. Do you know which version of Drupal is the last version that the views bulk operations module 4.2 with the actions permissions will work on? I would be interested in getting a crew together to rebuild that functionality if it's helpful, but need to know where this change in the API occurs.

Would be nice, I cannot answer that question without spending time I don't have on additional research though, quite possible that 4.2.x even works with Drupal 11 because I think old annotations way is not removed yet and my goal was to modernize the code as much as possible. Just test it.

Yeah, I'm stuck not being able to run my database updates for module updates because of this. I've tried removing VBO, but that doesn't seem to fix the problem. Anyone happen to know?

The Actions Permissions module was removed from VBO in version 4.3.0 to simplify permissions and improve security. It was deprecated and removed at once to prevent dependency on outdated functionality. To re-implement similar permissions, consider creating custom permissions or setting up role-specific VBO views.

Just a note - if like me you upgraded to 4.3.1 without uninstalling Actions Permissions first...

I got a nasty note on the Status report and when running update.php after upgrading - oops.

I tried to downgrade back to 4.2.7 and that completely broke my site. Super oops.

After many upgrade/downgrade/uninstall/reinstalls... I found a way to re-add the actions_permissions module so I could uninstall it after the fact. I'm surprised it worked... but it did!

I downloaded the 4.2.7 tar file, and from within modules folder I grabbed the actions_permissions module folder and dropped it in to the current install (via sftp) - this allowed it to be displayed under Extend > Uninstall and I was able to use that mechanism to uninstall "Actions Permissions" properly.

And then, hooray! The nasty note went away on Status report and update.php - All is well and good... except of course I have no actions permissions :-/

Boooooo.

ertiepie:

Same. Thankfully, I do run a backup of our account before running updates, so I completely reverted back.

Please test. And if it works well send me a beer because I drank one when rewriting this :P

Seems to work fine on first sight. Thanks @graber!

Updating some meta data. Don't forget to update the project page once this is released.

Thank you for checking it, I should release it today.