By wmike on

I've been working on my first Drupal site (experienced Joomla user) for the past week - it has just died on me. I had installed the captcha module - I now get get this

"Fatal error: Call to undefined function node_load() in /home/sites/rnmedics.com/public_html/includes/menu.inc on line 410"

Help.

Can anyone help me here, please?

This site now has a lot of content ported from Joomla - taken me a lot of time.

What can I do?

Note. I seem to keep bumping into horrors like this with Drupal - I would like to persevere, however.

Any help much appreciated.

Cheers!

Mike

⋅ Categories: Drupal 6.x

Comments

cog.rusty’s picture

cog.rusty commented

The "undefined function node_load()" should have been defined in the core file "modules/node/node.module". Make sure that:
- the file exists, exactly at that place. Core modules can't be moved (watch out for mouse slips in the FTP window).
- the file is undamaged (check if it contains "function node_load()") and readable by the web server (permissions at least 644).
- there is no second copy (for example an old backup) of the node module anywhere under Drupal.
- the "required" core modules - system, node, user, filter, block - are enabled in the system table in the database (status=1) and their paths are also correct.

wmike’s picture

wmike commented

Hi,

Checked all that - no apparent problem - site still reporting the same error.

Thanks for help - if i can't fix this i shall have to give up on Drupal - can't keep having a site break like this.

Cheers!

Mike

mclinn’s picture

mclinn commented

But the more I use Drupal the more I love it, probably for the same reason so many others do. Adding capabilities to a website in a few minutes that could take weeks (or longer, depending on your learning curve) doing it the "old way" is simply amazing.

So I've decided to back it up regularly, at least for any production sites. There's plenty of information here about this but it boils down to 2 things: having a copy of your entire drupal site AND your database files. This forced me to learn tar for archiving -- which still strikes me as cranky compared to good old pkzip and pkunzip -- but it gets the job done.

This can be accomplished fairly quickly with shell / command line access to your server. I haven't tried it with the various gui type setups but it should be doable. I know you can easily get a backup from mysql using phpmyadmin, for example.

I've gone as far as to restore a backed-up site onto another system to make sure all is well. I have a local Linux box that works well for this, plus a Linode account (linode.com).

I've heard horror stories over the years about people discovering their backups don't work so I make it a point to try them. I realize this may not be practical depending on your setup, but something to think about. Being able to roll back to a "last known good" version of the site is vital if the site is important.

The way I see it, the vulnerability to this kind of problem is the price we pay for the power this kind of system provides. A good backup strategy is the solution, or at least a big step in the right direction.

ps Glad to see you got your site back up. It looks good!