Failed: Drupal\Component\Plugin\Exception\PluginNotFoundException: The "entity_reference_image" plugin does not exist. i [error] Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() [#2867876]

When updating with drush from 8.2.7 to 8.3.0 I get the following error;

Failed: Drupal\Component\Plugin\Exception\PluginNotFoundException: The &quot;entity_reference_image&quot; plugin does not exist. i                               
Drupal\Core\Plugin\DefaultPluginManager-&gt;doGetDefinition() (line 52 of
/home/<sitename>/public_html/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).

Does any one else get the same error?
I've tried to update it multiple times, but I get the same error all the time.
I updated all the modules from within drupal first, then ran the following:

drush sset system.maintenance_mode 1 drush cr
drush pm-update drupal

and then I get the error stated above. Extremely annoying.

Comment	File	Size	Author
#16	update_test.txt	5.87 KB	b0red
#13	drush_pm-list_core.txt	32.41 KB	b0red
#13	drush_status.txt	1.3 KB	b0red
#7	core.extension.yml	2.38 KB	jiisuominen
#7	drush_debug.txt	47.07 KB	jiisuominen

Comments

Comment #1

7 April 2017 at 20:13

b0red created an issue. See original summary.

Comment #2

xjm

she/her

English

commented 8 April 2017 at 03:22

Hi b0red,

Are you running Drush 8.1.10? Earlier versions of drush have known bugs with updating Drupal 8 to 8.3.0. I'd update drush, restore your backup, and then try the update again.
Other users have also reported that they needed to run database updates more than once.
To help us debug this further, please provide your full list of installed modules by exporting your core.extension cofiguration, and also provide the full backtrace for the error message.

It sounds like something providing the entity_reference_image plugin in a previous release is not being found.

Comment #4

alexpott

he/they

English

🇪🇺🌍

commented 8 April 2017 at 15:20

It looks like the site had an early version of the File Browser module - it had an entity_reference_image plugin but has removed it. See http://cgit.drupalcode.org/file_browser/commit/?id=6e2e140 - Unfortunately it looks like they removed it and didn't provide an update path (as far as I can see).

@b0red - as @xjm points out - if you have a full stack trace of the error so we can see where in the update path you've crashed. Thanks

Comment #5

b0red commented 25 July 2017 at 14:38

Sorry for the long post, U can find it here instead
https://pastebin.com/raw/rAckaHMB

Comment #6

b0red commented 11 April 2017 at 09:42

I can't update drush either.

Comment #7

jiisuominen commented 19 April 2017 at 06:51

Status	File	Size
new	drush_debug.txt	47.07 KB
new	core.extension.yml	2.38 KB

So yeah, I stumbled to this issue while trying to update to 8.3. I updated my drush to 8.1.12 to no avail. I've ran updb quite a few times, but always stuck with this.

I attached my updb -d output and also my core.extension.yml. Hope this helps to sort out this, it's blocking me from doing any updates to our site.

/ Janne

Comment #8

alexpott

he/they

English

🇪🇺🌍

commented 19 April 2017 at 08:10

@5to1 are you actually using stuff from the flie_browser_example module if not uninstall it and it might fix your problem. Alternatively you might be able to get away with deleting the File Browser block content type.

Comment #9

jiisuominen commented 19 April 2017 at 12:05

@alexpott, thanks got this working by removing file_browser_example module AND that block type.

Comment #10

b0red commented 21 April 2017 at 13:50

I reverted to 8.2.7, since any tries to update to 8.3.1 always renders the site unoperable. And that took me 2 days of reinstalling old backups, new crashes and more reinstalls of old backups.

How do I do a stack trace for when I feel brave enough to retry updating to 8.3.1? Since I'm confident it will crash again.
And do I need to remove/uninstall file_browser_example and block or just keep it unactivated?

Comment #11

alexpott

he/they

English

🇪🇺🌍

commented 21 April 2017 at 18:10

@b0red if you're not using file_browser_example and block i'd recommend removing it. You've got a good chance of the update working if you do that.

Comment #12

b0red commented 22 April 2017 at 22:12

Nope, the same result. File_browser not active, and the block is uninstalled. Annoying as hell

Comment #13

b0red commented 26 April 2017 at 12:07

Status	File	Size
new	drush_status.txt	1.3 KB
new	drush_pm-list_core.txt	32.41 KB

So, still trying to update to 8.3.1.
When I do a drush pm-update drupal I get the following;

Rolling back all changes. Run again with --no-core to update modules only.
Cancelled.                                                                                                                                                       [cancel]
The following module is missing from the file system: file_browser bootstrap.inc:236                                                                             [warning]
The following module is missing from the file system: file_browser_example bootstrap.inc:236                                                                     [warning]
The following module is missing from the file system: flysystem bootstrap.inc:236                                                                                [warning]
The following module is missing from the file system: flysystem_dropbox bootstrap.inc:236                                                                        [warning]

I don't dare to continue, because I've spent too much time reinstalling the site to a functioning version. What would You do?

Comment #14

b0red commented 26 April 2017 at 12:28

Aaand the update f*cked it all up again. >:(
this is the the stacktrace when trying to install the file_browser manually with drush.

-bash-4.2$ drush en file_browser -y
The following extensions will be enabled: file_browser
Do you really want to continue? (y/n): y

Drupal\Core\Config\PreExistingConfigException: Configuration objects (embed.button.file_browser, entity_browser.browser.browse_files,                            [error]
entity_browser.browser.browse_files_modal, image.style.file_entity_browser_thumbnail) provided by file_browser already exist in active configuration in
/home/fotosbyp/public_html/core/lib/Drupal/Core/Config/PreExistingConfigException.php:65
Stack trace:
#0 /home/fotosbyp/public_html/core/lib/Drupal/Core/Config/ConfigInstaller.php(480): Drupal\Core\Config\PreExistingConfigException::create('file_browser', Array)
#1 /home/fotosbyp/public_html/core/lib/Drupal/Core/ProxyClass/Config/ConfigInstaller.php(132):
Drupal\Core\Config\ConfigInstaller->checkConfigurationToInstall('module', 'file_browser')
#2 /home/fotosbyp/public_html/core/lib/Drupal/Core/Extension/ModuleInstaller.php(141):
Drupal\Core\ProxyClass\Config\ConfigInstaller->checkConfigurationToInstall('module', 'file_browser')
#3 /home/fotosbyp/public_html/core/lib/Drupal/Core/ProxyClass/Extension/ModuleInstaller.php(83): Drupal\Core\Extension\ModuleInstaller->install(Array, true)
#4 phar:///usr/bin/drush/commands/core/drupal/environment.inc(131): Drupal\Core\ProxyClass\Extension\ModuleInstaller->install(Array, true)
#5 phar:///usr/bin/drush/commands/core/drupal/environment.inc(198): drush_module_install(Array)
#6 phar:///usr/bin/drush/commands/pm/pm.drush.inc(1167): drush_module_enable(Array)
#7 phar:///usr/bin/drush/includes/command.inc(422): drush_pm_enable('file_browser')
#8 phar:///usr/bin/drush/includes/command.inc(231): _drush_invoke_hooks(Array, Array)
#9 phar:///usr/bin/drush/includes/command.inc(199): drush_command('file_browser')
#10 phar:///usr/bin/drush/lib/Drush/Boot/BaseBoot.php(67): drush_dispatch(Array)
#11 phar:///usr/bin/drush/includes/preflight.inc(66): Drush\Boot\BaseBoot->bootstrap_and_dispatch()
#12 phar:///usr/bin/drush/includes/startup.inc(458): drush_main()
#13 phar:///usr/bin/drush/includes/startup.inc(365): drush_run_main(false, '/', 'Phar detected. ...')
#14 phar:///usr/bin/drush/drush(114): drush_startup(Array)
#15 /usr/bin/drush(10): require('phar:///usr/bin...')
#16 {main}

Comment #15

b0red commented 27 April 2017 at 22:18

If I do a drush pm-update -s drupal I get following;

-bash-4.2$ drush pm-update -s drupal
Executing: mysql --defaults-extra-file=/tmp/drush_z2Tnu0 --database=fotosbyp_drup8 --host=localhost --port=3306 --silent  < /tmp/drush_GASPxQ
Executing: wget --version
Simulating backend invoke: env COLUMNS=172 /usr/bin/drush  --backend=2 --root=/home/fotosbyp/public_html --uri=http://www  pm-updatestatus drupal 2>&1
pm-updatestatus failed.

Comment #16

b0red commented 28 April 2017 at 15:02

Status	File	Size
new	update_test.txt	5.87 KB

Did a new drush pm-update -svd drupal and got the following result (se enclosed update_test.txt);
This is from Drupal 8.2.8.

Comment #17

criscom

Graz, Austria

commented 25 July 2017 at 11:19

I ran into the same error. That's how I resolved it.

I was on Drupal 8.2.8.
1. Disable file_browser_example
2. Delete file_browser content type
3. Update to Drupal 8.3
4. Disable layout_plugin
5. Update Panels and Page_manager to 8.4
6. Disable file_browser
7. Run DB updates
8. Re-enable file_browser
9. Update to Drupal 8.3.5

Comment #18

b0red commented 25 July 2017 at 14:36

I'm on 8.3.5 now, still have the same problem. And since it's a production site, I really can't or feel like downgrading to 8.2.x to get this to work.
Any other solution?

Comment #19

criscom

Graz, Austria

commented 26 July 2017 at 06:40

Try disabling the file_browser module. Then run drush dbup -y. After that re-enable the file_browser module again.

Comment #20

26 July 2017 at 06:40

Version:

8.3.x-dev

» 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

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

Comment #21

nmeegama commented 16 January 2018 at 17:26

Had a similar error when I moved my website into production . When I checked /admin/reports/status Found out that PHP-gd library was missing. Installing the missing library solved the issue. So might be worth checking /admin/reports/status (Status report) as well

Comment #22

16 January 2018 at 17:26

Version:

8.4.x-dev

» 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

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

Comment #23

cilefen commented 7 April 2018 at 16:51

Priority:	Critical	» Major
Status:	Postponed (maintainer needs more info)	» Closed (works as designed)

I've read through this issue and it seems complete remove of file_browser (which did not provide an upgrade path) fixes the problem. If anyone cannot remove file_browser, that can be done but it should be discussed elsewhere.

Drupal is properly reporting a missing plugin.

Status:	Active	» Postponed (maintainer needs more info)
Issue tags:	-updating core, -8.2.7 to 8.3.0

Failed: Drupal\Component\Plugin\Exception\PluginNotFoundException: The "entity_reference_image" plugin does not exist. i [error] Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition()

Comments

Comment #1

Comment #2

Comment #3

Comment #4

Comment #5

Comment #6

Comment #7

Comment #8

Comment #9

Comment #10

Comment #11

Comment #12

Comment #13

Comment #14

Comment #15

Comment #16

Comment #17

Comment #18

Comment #19

Comment #20

Comment #21

Comment #22

Comment #23

Referenced by

News items

Our community

Documentation

Drupal code base

Governance of community

Failed: Drupal\Component\Plugin\Exception\PluginNotFoundException: The &quot;entity_reference_image&quot; plugin does not exist. i [error] Drupal\Core\Plugin\DefaultPluginManager-&gt;doGetDefinition()

Comments

Referenced by

Failed: Drupal\Component\Plugin\Exception\PluginNotFoundException: The "entity_reference_image" plugin does not exist. i [error] Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition()