Problem/Motivation

I am unable to access the admin menu. The log is showing:
[proxy_fcgi:error] [pid 1431248:tid 1431307] [remote 51.155.122.103:49568] AH01071: Got error 'PHP message: Uncaught PHP Exception Drupal\Component\Plugin\Exception\PluginNotFoundException: "The "resolvable_uri" plugin does not exist. Valid plugin IDs for Drupal\Core\TypedData\TypedDataManager are:

Steps to reproduce

Update core to 11.4.1

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

johnwt created an issue. See original summary.

cilefen’s picture

cilefen commented
Component: typed data system » link.module
Issue tags: +Needs steps to reproduce
Related issues: +#3066751: Add resolvable_uri property to LinkItem for APIs

Would you please provide the steps you took to upgrade the site? The error suggests that the auto loader is malfunctioning, or that cashes were not rebuilt.

johnwt’s picture

johnwt
Location 🇬🇧
commented

I ran:

composer update "drupal/core-*" --with-all-dependencies
johnwt’s picture

johnwt
Location 🇬🇧
commented

I have just run: drush cr and drush updb and most things seem to be working.

cilefen’s picture

cilefen commented
Status: Active » Closed (cannot reproduce)

Those commands are steps in the update documentation, so this isn’t a bug in Drupal.

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.

johnwt’s picture

johnwt
Location 🇬🇧
commented
Status: Closed (cannot reproduce) » Active

I haven't normally had to run these commands from drush, normally I would run them from the admin menu. Is it intended that the admin menu would be disabled without running the commands using drush ?

cilefen’s picture

cilefen commented

By that do you mean that update.php was inoperable?

johnwt’s picture

johnwt
Location 🇬🇧
commented

I don't know, but I couldn't access it from the admin menu as I normally would since it was inaccessible.

dcam’s picture

dcam commented
Component: link.module » base system
Category: Bug report » Support request
Status: Active » Fixed

Is it intended that the admin menu would be disabled without running the commands using drush ?

No. But updating a site's code always carries with it the potential that the site will be put into a non-functional state. It is intended that an administrator should know how to perform database updates without the benefit of a functional user interface. That's why those update instructions say (paraphrased) "Use Drush or visit /update.php." They don't say "Click the Run Updates link in the main menu." If I'm not mistaken, the Run Updates link is provided by the contrib Admin Toolbar module, in which case it definitely wouldn't be a recommendation in Core documentation.

I'm sorry that you had this difficulty with your site. If you haven't already, then please integrate the official means of running database updates into your update workflow to ensure smooth functioning of your site.

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.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.