By femrich on

I am running a multi-site and recently enabled some of the views bonus pack modules on my subordinate sites. They had been running fine on my main site. The process of enabling the modules went without a hitch on all but one of the subordinate sites, but one site suddenly began returning the following error:

Fatal error: Call to undefined function content_fields() in /home/public_html/sites/all/modules/content_taxonomy/content_taxonomy_views.module on line 23

Visiting that site now returns only a white page with this error message at the top, so there appears to be no access through the admin window. All the other sites are working fine.

I suspect I may have enabled the content taxonomy module on this one site without first enabling the content module. Oops! Now I am looking for suggestions on how to correct this, perhaps through cpanel or PHPMyAdmin? Or suggestions on a backdoor entry to Drupal admin that might get around the error.

Thanks for any suggestions.

⋅ Categories: Drupal 5.x

Comments

chadchandler’s picture

chadchandler commented

Go into phpmyadmin, open up your drupal database.. go into the system table.

Then, find the module needed (in this case content tax), then set the status from 1 to 0. This is documented in plenty of forum topics and also in the handbook. Please do a better job of searching before posting.

All you had to do was go into google and search for " turn off drupal modules phpmyadmin" .

femrich’s picture

femrich commented

Thanks very much. That did the trick.

As for the searching, the problem was not lack of searching, but not knowing what to search for. I first ran a search on drupal.org using various elements of the error message I received. I got lots of results and pored through them for about an hour--but the fixes offered were all specific to other modules and involved patching code. None of them had anything close to the solution you offered.

After the search engine seemed not to turn up a reasonable solution, I browsed the issues for Content Taxonomy for about 30 minutes, but again did not come up with a solution.

The problem here is not lack of searching, but not knowing what to search for. Your suggested search, "turn off drupal modules phpmyadmin," presumes I would know the solution was to turn off that module. I suppose it's obvious to many users, but I'm a self-trained newbie with pretty much no knowledge of php or the database system. Before you wrote, I didn't know I should be trying to turn of the module.

So I'm sorry for being a newbie, at least as far as the back end of drupal goes. But that's what I am. Your solution helped me, and now I have some more knowledge that (hopefully) will reduce the number of questions I have to ask on the forum and make it possible for me to help others in the future. So thanks.

mckoss’s picture

mckoss commented

I hit a similar problem - and searched for the error message and found this response - exactly what I needed. Thanks for posting with the appropriate keywords so other can follow in your footsteps!

sonden’s picture

sonden commented

After upgrading my mysql database from 4.0 to 5.0 i ran into the same problem. i can access the system table but the module is not showing up there...

Any hint how to solve this would be much appreciated!