I had this same exact error when trying to clean up the RH entities in the system. It ended up breaking the database and I had to restore a previous one. This was on 1.0 beta version, and when I tried to upgrade to 2.0.0 to maybe fix the issue, I got the same errors as everyone here in this related issue: https://www.drupal.org/project/rabbit_hole/issues/3385471 🐛 'rh_action' not found Active
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.
@basby - I have drush, you need to install the devel_entity_updates module for that to work on current versions of drush, and as I stated, it appears that's not the right way to go for production servers, hence why I'm not installing that module.
@keshavv - thank you, I will look into that.
I want to depart from this madness completely since I'm on 10.2.2, and there appears to be no patch and also appears it will never be incorporated in core, so I'd rather not deal with the headache of having to keep track of this patch anymore. I have a profile that has the setting of "base profile" set to "standard". How can I go about changing the current custom profile to NOT inherit the base profile? Can I just remove the "base profile" entry and it's good, it will default to inheriting the standard profile modules/themes/etc? Or do I need to go and put those in manually?
This page, https://www.drupal.org/node/1127786#s-details → shows the modules for the standard profile but it looks like it was for Drupal 7 and I can't find any information anywhere else as what dependencies are in the standard profile now.
I have the same issue, however I'm not using 'drush entity-updates' because it doesn't exist on my system. I see you can download and enable the devel_entity_updates module for TEST environments but not production. Many warnings about how you should NOT use it in a production environment, and how "maintainers of the module should fix the entity issue." So, unsure of what to do next, and whether this is breaking anything currently.
Nevermind, is a duplicate of https://www.drupal.org/project/simple_popup_blocks/issues/3367595 🐛 Remove useage of $(...).once, as it is removed in drupal 10 Closed: duplicate
jsweetack → created an issue.