Closed (cannot reproduce)
Project:
Drupal core
Version:
8.9.x-dev
Component:
other
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
23 May 2017 at 16:00 UTC
Updated:
26 Jun 2022 at 23:10 UTC
Jump to comment: Most recent
Comments
Comment #2
Syntapse commentedComment #3
cilefen commentedHi! This doesn't qualify as critical until you look at the site logs to determine the real problem. Take a look and let us know.
Comment #4
Syntapse commentedlog immediately after enabling core modules....
then this one...
Comment #5
Syntapse commented...that first one is not the most user friendly log message I have seen.
Comment #6
cilefen commentedWhich modules? Are there any non-core modules installed?
Comment #8
sic commentedi have the same issue now. could be a problem with localization maybe? views preview isnt working anymore.
Comment #13
lendudeCleaning up old bugs.
Is this still an issue after 8.3.2? Obviously this doesn't happen to all Drupal installs whenever a module in enabled, so we need some steps to reproduce this if it is still an issue.
Comment #14
longwaveThe OP looks to possibly be an issue with nodejs_watchdog; it looks like an exception occurred in the router rebuild and then the logger tried to render something which required routing, causing the recursion.
As nobody has replied in 5 months and there have only been two cases of this in 4 years, closing as cannot reproduce.
Comment #15
adriancotter commentedThis is happening to me today.
I can browser the site anonymously, but when Iog in, I get these errors on the same page:
TypeError: Failed to create closure from callable: function '_field_views_data' not found or invalid function name in Closure::fromCallable() (line 416 of .../web/core/lib/Drupal/Core/Extension/ModuleHandler.php).
Closure::fromCallable('_field_views_data') (Line: 416)
LogicException: A stray renderRoot() invocation is causing bubbling of attached assets to break. in Drupal\Core\Render\Renderer->renderRoot() (line 139 of .../web/core/lib/Drupal/Core/Render/Renderer.php).
The site was edited earlier in the day, so I am really confused why this started to happen.
Comment #16
adriancotter commentedI think the likely issue is that I copied a database that was in with 9.4 Drupal into whatever the last 9.3.x was
I'm still confused as to why it slowly undid itself.
The sequence of errors in the log:
[Fri Jun 24 12:48:14.331658 2022] Uncaught PHP Exception Drupal\\Core\\Extension\\Exception\\UnknownExtensionException: "The module mysql does not exist." at .../web/core/lib/Drupal/Core/Extension/ExtensionList.php line 522,
[Fri Jun 24 14:14:44.240820 2022] Failed to log error: Drupal\\Component\\Plugin\\Exception\\PluginNotFoundException: Unable to determine class for field type 'webform' found in the 'field.field.node.webform_demo_event.webform' configuration in Drupal\\Core\\Field\\FieldConfigStorageBase->mapFromStorageRecords()
[Fri Jun 24 15:11:20.860996 2022] Failed to log error: TypeError: Failed to create closure from callable: function '_field_views_data' not found or invalid function name in Closure::fromCallable()
[Fri Jun 24 15:11:20.861031 2022] TypeError: Failed to create closure from callable: function '_field_views_data' not found or invalid function name in .../web/core/lib/Drupal/Core/Extension/ModuleHandler.php on line 416 #0 .../web/core/lib/Drupal/Core/Extension/ModuleHandler.php(416):
The latter two happen now on login -- and the pages gets redirected to
https://www.sierraclubindependentaction.org/core/install.php
This is on a multi-site -- the other two sites present don't show any issues. I'd moved the database the day prior
The code is now 9.4 and it has not changed the last two errors.
Comment #17
adriancotter commentedI resolved my own issue -- although I'm not exactly sure how.
I thought it might have been related to our internet firewall, but I was able to replicate the issue locally.
Locally, it seemed to point to the fact there was stray configuration for non-enabled modules that were still in the DB in various places mainly in cache. But try as I might I could not get rid of it.
Then I ended up thinking of checking to login (on the live site) with a different machine and a different browser, and I was able to -- and then the issue in the original browser resolved. This points to some cache issue on the browser side. Sadly, I really don't understand why the error occurred or why it resolved.
I imagine the mixed code base and configuration was part of it -- although the stray configuration I was finding locally was also very puzzling (not modules that were ever enabled).