- Issue created by @redseujac
- π§πͺBelgium redseujac
In addition to my initial post: you must take care of uninstalling and deleting the separate module actions_permissions beforehand. If not you will get problems when running "drush updatedb" or something similar. That module was distributed with previous versions of Views Bulk Operations and seems not being removed when upgrading. I had to manually uninstall and remove that module beforehand.
I had the error message:
[error] (Currently using Missing or invalid module The following module is marked as installed in the core.extension configuration, but it is missing: * actions_permissions
I had to execute:
"drush config:delete core.extension module.actions_permissions"
and even:
drush php-eval "\Drupal::keyValue('system.schema')->delete('actions_permissions');"
- πΊπΈUnited States bunthorne
I was also unable to Run Updates after the upgrade. Please add appropriate instructions to the Release Notes page for what to uninstall before upgrade.
- π§πͺBelgium redseujac
Another anomaly: the module Actions Permissions is still mentioned at the home page of the module VBO, while it has been dropped since 4.3.0-beta1.
Nowhere on that homepage it is mentioned that this particulare module Actions Permissions must be uninstalled and removed before installing a new version, because as far as I know that module is not removed automtically when installing a new version of VBO.
- ππΊHungary Grabby
Running D10.3.5 and VBO 4.3.0-beta2 I was getting
Configuration user.role.user depends on the Actions Permissions module that will not be installed after import.
when doing a drush cim, so I downgraded to 4.2.7 and Iβm still getting it. Any guidance?