CORE BUG; The "metatag_display_extender" plugin does not exist

I am facing the above this issue when using blt and running a blt setup command, while blt tries to reinstall the site from scratch and importing the existing config I get the same error as below:

  The "metatag_display_extender" plugin does not exist. Valid plugin IDs for   
  Drupal\views\Plugin\ViewsPluginManager are: default    

I tried adding the dependencies of metatag_views module in views.settings.ymlfile as, mentioned in #21 but it didnt resolve the issue for me.

I think adding the dependency on the View definition that uses Metatag would be better than modifying views.settings.yml?

Same as #22: I can't do a site install from config (used for automated tests, drush si --existing-config -y), this error makes it crash.

metatag_views module is enabled on config.

@DamienMcKenna tried adding the dependency to the view definition that uses the metatag_views but even this didnt work, secondly I obsered that it fails when scheduler module is getting installed, and hence little confused how and why installation of scheduler module is is looking for

The "metatag_display_extender" plugin does not exist. Valid plugin IDs for   
  Drupal\views\Plugin\ViewsPluginManager are: default 

plugin and causing this to fail.

Looking for directions to debug this further and how this can be resolved ? Any help?

I wonder if this was the problem?

If anyone has reliable instructions for triggering this problem please let me know, I'd love to solve it, thank you.

Tested the above patch, its not resolving this Issue.
The steps to reproduce are as below:

Step 1. Create a normal Drupal Install
Step 2. Add and enable metatag module
Step 3. Add and enable metatag_views module
Step 4. Ensure under admin/structure/views/settings/advanced metatag_display_extender
Step 5. Run drush cex and export all the configs.
Step 6. Then try re running drush si and this should cause the error.

None of the above solutions worked for me.
I tried

composer require drupal/metatag_views

and it worked.

"metatag_views" isn't a separate package available on Packagist, so "composer require drupal/metatag_views" shouldn't have changed your composer files. It does suggest part of the problem might be the class autoloading, and possibly one priority over another.

I wonder if the priority for metatag_views was higher than the views priority, would that fix the problem?

@zakariabdc I tired adding the composer dependency to the project as mentioned by you, and that does not fix the issue on drush si .

yeah I agree with @DamienMcKenna on adding the module as a composer dependency, it do not make any difference.

@DamienMcKenna I tried changing the priority of the metatag_views in mycore.extension file, but no even that do not help.

I feel this has something to do with plugin dependencies not getting calculated properly and hence the metatag_views module is not getting added, not 100% sure on this though.

How's about this?

The last submitted patch, 33: metatag-n2927551-33.patch, failed testing. View results →

That suggests the dependencies can't be modified on a config object using the get()/set() methods. So what's the best approach?

The patch in #33 is also not helping to solve the drush si issue.

Hi All,
Still struggling to resolve this, requesting direction towards the resolution or even a work around would help for now ?
Thanks in advance..

I think the first step would be to add a new install profile that adds Metatag Views to the install profile, then we can have something to debug.

Going to try creating an install profile..

WIP.

We first need to make the tests fail.

+1 for this to be solved, I face exactly the same issue with simple_sitemap also, looks like the problem is general and more likely related to core as multiple modules struggling with it

Attaching the issue in case it will be solved earlier

As far as I can tell, at least part of the issue is that the metatag_views module lists views as a dependency (which makes sense), but that means when installing from a profile, Drupal will try to install Views before installing Metatag Views, and with the `metatag_display_extender` plugin is listed in the `views.settings` config, at the point where Drupal tries to install Views, it sees that but because Metatag Views isn't installed at this point, as far as Drupal is concerned the metatag_display_extender plugin does not exist, so it fails.

Off the top of my head I can't think of a clean way around this.

So maybe Views shouldn't cache its list of display extenders as a config object? Maybe this is ultimately a core issue?

I opened a core issue for this: 🐛 views.settings config object should not be used to cache list of available plugins Active

I get this error as soon as I do anything in composer like uninstall a completely different module. How can I workaround this issue breaking my site as soon as I want to do basically anything?

Hete's my scenario: https://imgur.com/a/frC5mEA

@Castor-designs If you have an export of your site's config, go into the views.settings.yml, look for the line metatag_display_extender, remove that line and try doing a config import, that might fix the issue for you.