milan.durovic → created an issue.
Would it be possible to integrate the patch into a new module release? I know that there are other outstanding bugs, but this particular change is stalling the upgrade to Drupal 11.
I've tried the patch and Upgrade Status then reported the module as ready for Drupal 11. However, when I tried the upgrade, I think the composer was still grabbing information from the juicebox site and concluding that Drupal 11 upgrade cannot proceed because of the problems.
If you don't intend to integrate this patch into a release soon, is there a way to move to Drupal 11 after applying the patch, without losing data (ie. galleries) that are already on the site?
Thanks,
Milan
I'm experiencing exactly the same problem with Drupal 10.3.0. In my case, it happened when I uninstalled "Forum" module. I tried clearing all caches, I tried clearing views cache, nothing helped. If I reinstall "Forum" module, the problem goes away. Uninstall again, it's back.
Is there a way to manually change the site's state so that this problem goes away? I haven't tried uninstalling "Views" module as it would be too drastic and would require a lot of recovery work, but I'm hoping there's something else that can be done?
I checked all the blocks on the site and none of them has any references to forum or forum content. Very weird.
I ran *drush* as suggested by larowlan and after that, I could install the module. Thank you guys!
PS. maybe uninstall operation should include this filter removal?
milan.durovic → created an issue.
Hi Anybody,
Ok, I tried your suggestion. First, I did *updb* and *cr* BEFORE the upgrade, then performed the upgrade. This caused the crash exactly as before. Then I ran *updb* and *cr* AFTER the upgrade and the site got back to normal and is showing that CAPTCHA is upgraded.
Thanks for the tip. I'm not sure if these steps can be automated, ie. included in the upgrade. Perhaps it would be good to at least include them in release notes if it's not possible to automate it.
Thanks again for your prompt answers and help.
Regards,
Milan
No, I'm using PHP 8.0.28 and running Drupal 9.5.10
I have the same problem, which happened in the upgrades to .11 and .12. I have Drupal 9.5.10 and running PHP 8.0.28. So, it doesn't look like upgrading from PHP 7 -> 8 would make it go away. I tried the upgrade both via Drupal admin UI and composer, both failed.