🇦🇹Austria @reinimax

Hello,

I tried out the update and successfully performed the database updates, but still I get this entity/field definitions error on the status page:

Mismatched entity and/or field definitions
The following changes were detected in the entity type and field definitions.
Wishlist
The Code field needs to be updated.

Update: for me, the culprit was the gin_lb module. Applying the patch from this issue 🐛 \Drupal::$container is not initialized yet Active solved my problem.

@nicxvan I tried both patches #19 and #23 as well as the diff from the merge request. They applied, but I still get the container is not initialized yet error.

If this helps, the site was created with Drupal 11.1.4 and on this version I have no problems. The error occurs when doing a drush cr immediately after the updating to 11.1.5. Since @raveen_thakur51 has the same problem when updating to 11.1.2, maybe the issue has something to do with updating core itself?

Here are my modules:

"require": {
        "composer/installers": "^2.3",
        "drupal/admin_toolbar": "^3.5",
        "drupal/better_exposed_filters": "^7.0",
        "drupal/coffee": "^2.0",
        "drupal/config_split": "^2.0",
        "drupal/core-composer-scaffold": "^11.1",
        "drupal/core-project-message": "^11.1",
        "drupal/core-recommended": "^11.1",
        "drupal/easy_breadcrumb": "^2.0",
        "drupal/field_group": "^3.6",
        "drupal/focal_point": "^2.1",
        "drupal/gin": "^3.0",
        "drupal/gin_lb": "^1.0@RC",
        "drupal/gin_login": "^2.1",
        "drupal/honeypot": "^2.2",
        "drupal/inline_block_title_automatic": "^2.0",
        "drupal/layout_builder_browser": "^1.8",
        "drupal/layout_builder_modal": "^2.0",
        "drupal/layout_builder_operation_link": "^2.2",
        "drupal/metatag": "^2.1",
        "drupal/pathauto": "^1.13",
        "drupal/preprocess": "^2.2",
        "drupal/redirect": "^1.11",
        "drupal/sam": "^1.3",
        "drupal/shield": "^1.8",
        "drupal/simple_sitemap": "^4.2",
        "drupal/twig_tweak": "^3.4",
        "drupal/ultimate_cron": "^2.0@beta",
        "drupal/webform": "^6.3@beta",
        "drush/drush": "^13.3",
        "vlucas/phpdotenv": "^5.6",
        "wikimedia/composer-merge-plugin": "^2.1"
    },
"require-dev": {
        "drupal/coder": "^8.3",
        "drupal/core-dev": "^11",
        "drupal/masquerade": "^2.0",
        "drupal/webprofiler": "^11.1",
        "phpstan/extension-installer": "^1.4"
    }

I ran into this issue when I upgraded from 11.1.4 to 11.1.5. I created a patch from the MR and it applied, but I still get the error.

Thanks for the patch, this is a very useful feature indeed!

However, I'm wondering whether it is a good idea to let any user with the "administer users" permission view the key authentication tab? Sure, they cannot edit the authentication key without the appropriate permission, but they can still see and potentially disclose or abuse this information.

In my opinion, it would be better to remove the "administer users" permission from the access check in UserKeyAuthForm, so that access is only granted if the user has the appropriate permissions from the key_auth module. If a role who manages users needs to view the key authentication tab, they can simply be assigned an additional role.

reinimax → created an issue.

reinimax → created an issue.