Conditions:
Contrib modules enabled:

- ctools;
- bean;
- entity;
- panelizer;
- panels;
- entity;

Version php8.0.

Steps to reproduce:
Run drush rr command.
We see warnings- in console:
[warning]
Attempt to read property "language" on null common.inc:7950
[warning]
Attempt to read property "language" on null node.module:707
Please see screenshot console.png.
During investigation I found, that problem was on php7.4 ( hidden notice), but on php8.0 we have Warnings(see above). It arises after call registry_rebuild() in drush_registry_rebuild() on the DRUSH_BOOTSTRAP_DRUPAL_DATABASE level after bootstrap_invoke_all('registry_rebuild'). Then call function drupal_alter('registry_files', $files, $modules) . There is global variable $language is empty. Please see screenshot with call stack on this level (please see screenshot DRUSH_BOOTSTRAP_DRUPAL_DATABASE.png).
But after drush_bootstrap_to_phase(DRUSH_BOOTSTRAP_DRUPAL_FULL) on DRUSH_BOOTSTRAP_DRUPAL_FULL and call registry_rebuild() global variable $language is object of stdClass(please see screenshot DRUSH_BOOTSTRAP_DRUPAL_FULL.png).
So I suggest to add check in ctools_registry_files_alter():

  if (drupal_get_bootstrap_phase() < DRUPAL_BOOTSTRAP_FULL) {
    return;
  }

Issue fork ctools-3284043

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

alena_stanul created an issue. See original summary.

alena_stanul’s picture

Issue summary: View changes
StatusFileSize
new123.94 KB
alena_stanul’s picture

StatusFileSize
new456 bytes
alena_stanul’s picture

Issue summary: View changes

immaculatexavier made their first commit to this issue’s fork.

lesleyfernandes’s picture

The #3 worked for me.

lesleyfernandes’s picture

Status: Active » Needs review
joelpittet’s picture

fenstrat’s picture

Confirming #3 also fixed the issue for me, with PHP 8.2.

japerry’s picture

Status: Needs review » Closed (outdated)

Drupal 7 is no longer supported, closing.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.