I updated core from 8.3.1 to 8.3.2 and could only access the front page after that. Drush watchdog-show returned:

505 05/May 15:56 php error Drupal\Component\Plugin\Exception\InvalidDeriverException: Plugin
(system.theme_settings_theme) deriver
"Drupal\system\Plugin\Derivative\ThemeLocalTask" does not exist. in
Drupal\Component

I can't figure this one out and am now in the process of reverting to 8.3.1, which itself was a bear to get going due to the layout / bootstrap_layouts / DS installations I had set up. I see a few similar issues while searching, but I don't know if they're caused by the same base problem.

PHP: 7.0.18
Memory limit: 128M
MySQL, MariaDB, Percona Server, or equilivant
Apache Web server

Contrib Modules:
Admin Toolbar
Admin Toolbar Extra Tools
Bootstrap Lib
(Core Layout Discovery module is enabled)
Bootstrap Layouts
Display Suite
Display Suite Extras
Display Suite View Mode
Layout Plugin is still there, but not installed
dropzonejs
Colorbox
Entity Browser
Juicebox
Paragraphs
Backup & Migrate
Pathauto
Block Class
Token
Libraries
Search API
Database Search
Metatag
Views in use
Views Reference Field
Datetime
Entity Reference Revisions
Chaos tools enabled
Chaos tools blocks enabled
Chaos tools Views enabled

Comments

muranod created an issue. See original summary.

cilefen’s picture

Title: Error updating from 8.3.1 to 8.3.2 Website encountered an unexpected error » InvalidDeriverException updating from 8.3.1 to 8.3.2
Component: bootstrap system » plugin system
Category: Support request » Bug report
Priority: Normal » Major
cilefen’s picture

Some of the exception message is cut off in the issue summary. Can you obtain the entire message please?

muranod’s picture

Fortunately, it was still in the logs after reverting to 3.2.1:

Drupal\Component\Plugin\Exception\InvalidDeriverException: Plugin (system.theme_settings_theme) deriver "Drupal\system\Plugin\Derivative\ThemeLocalTask" does not exist. in Drupal\Component\Plugin\Discovery\DerivativeDiscoveryDecorator->getDeriverClass() (line 218 of /home/directoryname/public_html/d8/core/lib/Drupal/Component/Plugin/Discovery/DerivativeDiscoveryDecorator.php).

Sorry for miscategorizing the items when I posted.

cilefen’s picture

The error is in reference to a local task link. It is defined in core/modules/system/system.links.task.yml:

system.theme_settings_theme:
  route_name: system.theme_settings_theme
  title: 'Theme name'
  parent_id: system.theme_settings
  deriver: Drupal\system\Plugin\Derivative\ThemeLocalTask

DerivativeDiscoveryDecorator calls class_exists() on 'Drupal\system\Plugin\Derivative\ThemeLocalTask' on about line 218 and it is not found.

That is just a study of the symptoms. Did you have any trouble upgrading? And if you don't mind me asking—what upgrade procedure did you follow?

muranod’s picture

It was a manual upgrade using FTP. (same way I upgraded from 2.2.8 or .9 to 3.2.1. didn't see any issues with the FTP operation, other than it took a long time due to the number of files.

I thought it odd that I could access the homepage (front), which was created by views, but not the sections (also created by views) or even via direct links to the content without the "website encountered an unexpected error" message.

I could try the update again using drush, but since I don't know if that would work, I thought I'd search for the cause before committing that much time again.

cilefen’s picture

Could you get into a little more detail about what you did to upgrade. Did you delete core/ and vendor/ before adding files?

muranod’s picture

@cilefen Yes, I deleted Core and Vendor directories and all the root files except .htaccess, robots.txt and composer.json

cilefen’s picture

Was core/modules/system/src/Plugin/Derivative/ThemeLocalTask.php missing from the files you uploaded?

muranod’s picture

It's in my local hd folder that I uploaded w/ FileZilla, but there is no log file I can check.

I will wait a bit and try it on my local installation this week and see if I get the same result. Also, time to see if others are having the same issue. Can't help but wondering if it's related to the new vs old layout module w/ DS, but only wondering that because of the issues I had with the prior upgrade.

muranod’s picture

Don't know if this is relevant, but I looked through the text file of the last backup I made of the working 8.3.1 site before upgrading and there are repeated references to the layout_plugin module "not found"

example: /d8/modules/layout_plugin/layout_plugin.module): failed to open stream: No such file or directory";}

That module is still there, but was uninstalled by Display Suite.

I don't know if that's at all related to the issue. I don't see any other errors in the saved database, nor in the logs.

Version: 8.3.2 » 8.3.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.3.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +Bug Smash Initiative

Doing triage for the Bug Smash Initiative.

@muranod, did you resolve this? From the last comment it seems that a module was not installed? If you are no longer having this issue, please close this issue and if possible, leave a comment describing how you fixed it, as it may help others with the same issue.

Thanks!

muranod’s picture

I don't remember how I got around this. I quit updating that site and and redeveloping it locally with Composer and Drupal v9. I apologize for not coming back and closing this issue, which was persistent at the time.

cilefen’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)