How to fix irreversible module damage in Drupal

Question

It was very unpleasant. I installed the Finder module in a Drupal installation. I configured some settings in it, and then after changing some settings, it started to show some Ajax errors, and then a white screen appeared displaying this error:

Fatal error: calling the undefined views_include () function in /var/www/drupal/sites/all/modules/views/includes/plugins.inc on line 9

Using Drush, I disabled the Finder module and cleared the cache. But nothing happened. Then I turned off the Views module. The white screen has disappeared.

And now I'm stuck. I had a good job on this site, and when I turn on Views again, a white screen appears again. It seems to me that the Finder module made some irreversible changes somewhere in Views. I mean, why are my views not working when I cleared the cache and Finder is disabled?

Has anyone ever come across such a thing in Drupal? How did you solve it?

UPDATE I just discovered that the developer of the Finder module claims to be a bug in Views. See here: http://drupal.org/node/1611106 . As suggested, commenting that a specific line 9 in the plugins.inc module of Views works. However, I am still skeptical of admitting errors in perceptions.

Answer 1

I also got this error. It's pretty funny that he also played with the settings in the search module. Play with ajax settings to be precise.

In any case, to return your site when you receive an error and a white screen, close the browser and open it on a page other than your site and clear the entire browser cache. Then you can see your site again.

It happened to me after setting "Ajax" to "yes" under the form heading on the edit search page. After you open the browser again and clear the browser cache, go directly to the edit page of the crawler, which is the culprit, and set "ajax" to "no."

Answer 2

This is not the Seeker; this is either a Drush botching update, or perhaps you are moving a module, making the registry obsolete. Make sure that views.module actually exists, the views are included in the system table, and then rebuild the registry , as nmc suggested.

This should fix it, but in the worst case, you can comment on the views_include('base'); call views_include('base'); at the top of the .inc plugins as a quick hack to restore your site.

Answer 3

Perhaps the Registry Rebuild module can help you.

When will you need Registry Rebuild?

You can get something like:

PHP Fatal error: Class 'EntityAPIControllerExportable' not found in ...sites/all/modules/rules/includes/rules.core.inc on line 11

If this happens when you try to run update.php, and happens when you try to clear your cache, well, you have problems. This is why you need to restore the registry.

I never used it myself, so I recommend you look into the code before running it, but I hope it helps you.

See http://randyfay.com/node/105 and http://drupal.org/project/registry_rebuild

Answer 4

For me, restoring the registry using drush rr did not help. It was also not possible to disconnect the module, removing the reinstallation. The only thing that worked was to clear the sessions table.