Problem/Motivation
Wanted to uninstall this plugin, but as I enabled it in views, there is error message :
The website encountered an unexpected error. Please try again later.
Drupal\Component\Plugin\Exception\PluginNotFoundException: The "views_ajax_get" plugin does not exist. Valid plugin IDs for Drupal\views\Plugin\ViewsPluginManager are: default in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).
Unable to restore and enable it back, need to rollback whole site.
Is it possible to create any patch which prevent such case?
Comments
Comment #2
leon kessler commentedThis is actually an issue with core, as it should be handling the dependencies.
Attached reference to issue for Drupal core.
Comment #3
robertoguzman commentedany update regarding this issue ?
Comment #4
arlina commentedThe core referenced issue does not have a working patch (that I could find at least). Until it gets fixed, maybe this module can remove the display extender on the uninstall hook - that's how metatag_views is doing it as well.
Here's a patch that works against 2.0.0.
Comment #5
fabiansierra5191 commentedI had to uninstall this module and I got the same issue.
I tried patch #4 and works for me.
Moved to RTBC.
Comment #6
greg boggsI was able to uninstall the module with this patch, but only partially, my views still generate the config from the module. Is there an upgrade path to 10.1? Can we mark this unsupported by 10.1? It's currently marked as supported and working 10.1 in composer.
Comment #7
greg boggsComment #8
catchYou might be able to manually resave your views to clean up the config.
Comment #9
rcodinaEditing views and saving them doesn't work for me. I just have had to manually editing view's yml files to remove this module's configuration.
Comment #10
greg boggsThat was also what I had to do.
Comment #11
tuwebo commentedNot sure about the implications of this workaround (it might break your site, take it with a grain of salt) , but it seems it is working for me if I run it before uninstalling:
drush cset --input-format=yalm views.settings display_extenders default
You might want to check the views.settings configuration before running it, executing:
drush cget views.settings
and then bring back the configuration that was there before the uninstall, e.g.:
drush cset --input-format=yaml views.settings display_extenders '["metatag_display_extender", "ajax_history"]'
Be aware, this workaround is not tested, I am posting it as I am facing the issue.