I clicked the "Disable Config" button, and now all pages give me the error:

Fatal error: Call to undefined function _print_page_match() in /usr/local/share/drupal/sites/all/modules/print/print_mail/print_mail.module on line 479


kjcole’s picture

Title: Fatal error from module print » Fatal errors

Oops. I take it back: The fatal error is really fatal errors:

Fatal error: Call to undefined function taxonomy_vocabulary_load() in /usr/local/share/drupal/modules/forum/forum.module on line 175

is another one that I'm seeing.

babbage’s picture

Firstly, to solve your immediate problem, regardless of its cause—almost certainly you have modules enabled that are dependent on modules that have been disabled. Remove those modules from your modules folder, run update.php, then return to your modules page and click "Save Configuration". (Can't recall if the final step is required, but probably it is.) You should then be able to re-install the modules in question and make sure the modules they depend on are also active—and do so without errors. If this still doesn't fix your problem, post here and we'll try to find a further solution.

In terms of identifying the cause of the bug you're reporting, I'll need more information. Questions soon.

babbage’s picture

OK, things that would assist in troubleshooting this issue:
What version of Drupal were you running when you clicked the "Disable Contrib" button?
What version of Drupal are you running now?
When did you first see an error message?
What were you doing at the time?
What has been changed on your site between clicking the "Disable Contrib" button and now?
Do any of the modules you are running modify the look or operation of the module administration page?
Were you running Devel Themer module at the time you clicked "Disable Contrib"?

Please provide a list of all contrib modules that were installed on your site at the time you clicked the "Disable Contrib" button.

Dave Reid’s picture

I'm pretty sure this is a problem that taxonomy has to be enabled before forum.

babbage’s picture

The reason for the detail is not to figure out what is causing the error per se—but rather to figure out (presuming it was Contrib Toggle that was at fault) which module interfered with the operations of Contrib Toggle that meant that some modules were disabled but not all of the modules that also depended on them. That's much more complex to figure out than merely which modules are now causing the problem...

babbage’s picture

Status: Active » Postponed (maintainer needs more info)
babbage’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

I'm going to presume the poster doesn't intend providing more information here, so not possible to determine what if anything caused this problem. Feel free to re-open this issue if you have any information relevant to add.

jleroi’s picture

I have just had the same experience. I installed Contrib Toggle 6.x-1.3 hoping to use it to upgrade a Drupal 6.10 installation to the current 6.14. I had the module enabled but had not used it yet as I was updating a couple of other modules before the Drupal update. When I hit "Save configuration" on the Modules page after enabling Counter 6.x-2.0 I immediately started getting fatal errors in various modules that had all been running in a stable state for months. I couldn't even get back to the module page. I removed Counter from the modules folder with no effect. Then I removed ctools because the error I was getting was from the delegator. Then the image module started generating fatal errors. Then birthdays and date. With all of those removed from the modules folder I was finally able to load a page. I have some errors still showing but they are not fatal. In looking at the modules I noticed that several I have not touched are disabled and greyed out. Things like Taxonomy, Views, Path, and LDAP Authentication. Their dependent modules are still enabled.