Closed (won't fix)
Project:
Drupal core
Version:
4.6.0
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Jul 2005 at 11:37 UTC
Updated:
24 Jul 2005 at 07:55 UTC
I was just taking Drupal on a dry-run. After playing around for a bit, everything just started going haywire.
Fatal error: Call to undefined function: node_title_list() in /home/webadminz/bobberz.com/html/drupal/modules/blog.module on line 280
I keep getting errors like this all over the place now.
Everything was going fine. This all started going crazy after I activated the modules:
event
flexinode
adsense
blogtheme
And switched to the Marvin theme.
As I wasn't expecting the error, I'm not sure which change brought it about.
Any ideas what suddenly brought this on?
Comments
Comment #1
drupalcreed commentedJust wanted to update this. The site is completely down, totally inaccessible.
What may have happened is that I disabled some modules without turning off their blocks, throwing it into a tailspin?
Not being a coder, and obviously having no way of even beginning to understand what caused the error or why it's preventing any access whatsoever to the script - is there a way around stuff like this, if and when it happens?
Just concerned about launching a site using Drupal and having something like this happen? Seems odd that it took the entire site out?
Thanks for any help.
Comment #2
cel4145 commentedSorry. I don't know the solution to your problem. However, you'd have better luck with getting support if you post to the forums; this is the first suggestion on the support page. Bug reports are for reports of bugs, not support. As it is, you've posted a bug report for Drupal core; yet it sounds like from your problem description that you might have a bug in one of the contributed modules. Hard to to tell for now. In fact, for a bug report to be useful, you'd want to localize it more to the point that you were sure it is a bug in Drupal core or a particular module then post in the appropriate spot.
Comment #3
chx commentedThis is not a bug report but a support request. Hence the status change.