Unable to edit existing extra field or render any public site pages

Same issue here.

Ran into the getName() null error on Drupal 10.2.5 after upgrading to 2.1.0-rc1.

This is a regress from this issue 🐛 Unable to create extra field on user entity Fixed

That changes the ID of the config - but there is no update hook provided to fix existing config.

What is happening is that the the config storage loads all the configs which are keyed by the old id:

    foreach ($this->configFactory->loadMultiple($names) as $config) {
      $id = $config->get($this->idKey);
      $records[$id] = $this->overrideFree ? $config->getOriginal(NULL, FALSE) : $config->get();
      $configs[$id] = $config;
    }
    $entities = $this->mapFromStorageRecords($records);

When it loops through the entities returned, they have the key id, so this thows an exception as $configs[$id] isn't set - configs is keyed by the old id.

    foreach ($entities as $id => $entity) {
      $self_referring_cache_tag = ['config:' . $configs[$id]->getName()];

This module needs an update hook to fix the old configs.

Opened MR to revert the change which I believe is accidental.

This will still need an update hook I believe, as this will cause the same issue for people who have created config from 2.1.0-rc1 or when using the committed diff as a patch (as indicated in the related issue, some people are using the committed change already having updated the config ids themselves).

Setting needs work as I think with or without the id revert this will need an update hook to ensure what is in configuration matches what the entity generates for its id.

Hello,
After installing the module, the two errors are occurring, one is while creating a new extra field and another is when editing the existing extra field.
ERRORS:
1. Error: Typed property Drupal\entity_extra_field\Entity\EntityExtraField::$name must not be accessed before initialization
2. Error: Call to a member function getName() on null

Solution:
To resolve above two errors, created a patch. Please review the attached patch file.
Thank you!

Hi arora.shivani,

There is a different issue reported in 🐛 Unable to add an extra field on a content type/bundle that has no extra fields already Active which is specific to your first issue.

There is already a patch in that issue that is the same as yours so it looks like that is another valid fix that needs to go in but this issue is about existing data not fresh installs.

Please do follow up in that related issue that the patch works for you.

Setting back to needs work based on my previous comment / MR.

@arora.shivani - I took a look and the patch doesn't do anything for the errors reported specifically in this issue - I think my original comment stands that your issue is likely in 🐛 Unable to add an extra field on a content type/bundle that has no extra fields already Active

Added an update hook to correct any broken config.

This I think can be used for either case if the id change is reverted or not.

It will help people who have either created config using the changed id format - or if the id format is not going to change back it will convert old config to the new format.

The new format is I think a mistake, if you have the same bundle name across multiple entity types (rare but possible) this could lead to collision, I believe it was just a mistake that can be reverted.

The MR worked for me, thanks

Marking MR15 as RTBC.

#11 worked for me as well. Could this please be committed to dev at least?