- Issue created by @cameron prince
- 🇮🇳India shiv_yadav
Hello cameron prince,
Add reproduces step. becuase install this module. i've not any issue.
Configuration:- drupal - 9.5.10
Php :-8.1.2 - 🇨🇦Canada aarantes
I had the same issue when updating from 1.0.0-beta1 to 2.0.0-alpha5.
After update (successful), ran "drush updb" and got these messages:> [notice] Update started: rabbit_hole_update_8103
> [notice] Update completed: rabbit_hole_update_8103
> [notice] Update started: rabbit_hole_update_8104
> [notice] Update completed: rabbit_hole_update_8104
> [notice] Update started: rabbit_hole_update_8105
> [notice] Update completed: rabbit_hole_update_8105
> [notice] Update started: rabbit_hole_update_8106
> [error] 'rh_action' not found
> [error] Update failed: rabbit_hole_update_8106
[error] Update aborted by: rabbit_hole_update_8106
[error] Finished performing updates.No problem exporting (drush cex).
As of now, no visible issues on the site.
- 🇺🇸United States mikegodin
Confirming exactly the same issue as observed by aarantes → when updating from 1.0.0-beta1 to 2.0.0-alpha5, with Drupal: 10.1.5 and PHP: 8.1.16, while running
drush updb
:> [notice] Update started: rabbit_hole_update_8103
> [notice] Update completed: rabbit_hole_update_8103
> [notice] Update started: rabbit_hole_update_8104
> [notice] Update completed: rabbit_hole_update_8104
> [notice] Update started: rabbit_hole_update_8105
> [notice] Update completed: rabbit_hole_update_8105
> [notice] Update started: rabbit_hole_update_8106
> [error] 'rh_action' not found
> [error] Update failed: rabbit_hole_update_8106
> [notice] Copied modules/custom/content_type_theme/css/adminimal-custom.css to sites/default/files/adminimal-custom.css.
[error] Update aborted by: rabbit_hole_update_8106
[error] Finished performing updates. - 🇺🇸United States cybercoda
Confirming same problem. Install was on Drupal 9.5.11
[notice] Update started: rabbit_hole_update_8103
> [notice] Update completed: rabbit_hole_update_8103
> [notice] Update started: rabbit_hole_update_8104
> [notice] Update completed: rabbit_hole_update_8104
> [notice] Update started: rabbit_hole_update_8105
> [notice] Update completed: rabbit_hole_update_8105
> [notice] Update started: rabbit_hole_update_8106
> [error] 'rh_action' not found
> [error] Update failed: rabbit_hole_update_8106 - 🇺🇸United States jsweetack
I have the exact same issue. In fact the 'rl_action' issue was breaking the database after trying to cleanup the rabbit hole entities that were showing in the status report. I tried updating in hopes it would fix the problem, but alas it still persists as others have attested to above.
- 🇳🇱Netherlands PROMES
I reported this also in https://www.drupal.org/project/rabbit_hole/issues/3415838 🐛 uninstall of Rabbit Hole nodes not possible Active last januari.
Today, deinstalling a complete non-related module I got this exception:
RuntimeException: Adding non-existent permissions to a role is not allowed. The incorrect permissions are "rabbit hole bypass node". in Drupal\user\Entity\Role->calculateDependencies() (line 207 of /xxx/drupal/web/core/modules/user/src/Entity/Role.php).PLEASE provide us with a solution. Regular database updates allways finish with an error about rabbit hole and do't do all updates!!!!!!!
- 🇿🇦South Africa Gomez_in_the_South
I also encountered this error updating from 1.0.0-beta11 to 2.0.0-alpha5.
I was able to resolve this by going to the Rabbit hole configuration (/admin/config/content/rabbit-hole) and then for each entity, clicking "Configure" and saving it again.
After doing this, and running the updates again, the `rabbit_hole_update_8106` step completed ok.
(I have seen another error further on, with `rabbit_hole_update_8112` - "[error] SQLSTATE[23000]: Integrity constraint violation", but I'll raise a separate issue for this)
- 🇳🇱Netherlands PROMES
@Gomez_in_the_South: thanks for your input.
After enabling and disabling entities in the rabbithole settingspage and runnng update.php all my updates finished correct. Now I can also deinstall old modules. But NOT rabbithole node.
Since the problems exist in production site I cannot use the 'update part'.