Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After upgrading to the latest version of Context (beta6), I get the following fatal error:
Fatal error: Class 'context_reaction_block' not found in /var/www/djoglobal/docroot/sites/all/modules/contrib/context/context_layouts/plugins/context_layouts_reaction_block.inc on line 3
The context_reaction_block class exists and is defined in the plugins/context_reaction_block.inc file. It appears this file is not getting loaded.
Any ideas what's causing this fatal error? I'm going to have to downgrade to get my site working until there's a fix.
Comments
Comment #1
crbassett CreditAttribution: crbassett commentedI have the same issue, too. Not sure what is causing it. Can't seem to get out of the fatal error either. Context error cascaded into Ctools error which cascaded into Views error wich cascades into Menu error. It's bad.
Comment #2
tekante CreditAttribution: tekante commentedCan you see if removing the line files[] = plugins/context_layouts_reaction_block.inc from the context_layouts.info file resolves the issue for you?
Comment #3
crbassett CreditAttribution: crbassett commentedNo. That did not fix it.
Current PHP error is now:
New error seems to be in Delta?
I've got to move on without this module to finish the site. Thanks for your development efforts.
Comment #4
klaxontm CreditAttribution: klaxontm commentedsame issue as #3. anyone with way out?
Comment #5
klaxontm CreditAttribution: klaxontm commentedComment #6
AlexBorsody CreditAttribution: AlexBorsody as a volunteer commentedsame issue
Comment #7
pramodganore CreditAttribution: pramodganore as a volunteer commentedI usually get this error after i run a drush rr.
Never actually spent time looking at the actual cause,
However i end up running a drush cc all and it usually resolves this issue.
The issue arises at the _registry_check_code() -- register cache issue
I had earlier assumed it was fixed as part of https://www.drupal.org/project/drupal/issues/3028364 but seems like that is still not the case.