By boonies on

Hello,

I've tried starting from scratch a couple of times but continue running into the same problem trying to install version 5.6:

Fatal error: Call to undefined function: node_get_types() in /var/hsphere/local/home/freecms/drupal.mysite.com/includes/theme.inc on line 271

This happens right after the installation script is run; I enter the database details and proceed, then when it goes to the index page I get the error. No additional configuration or additions have been made to the base install, no additional modules activated.

It's the same page I'm aware, but also happens when trying to pull up the index page directly after the fact.

Some CSS styles get printed out before the error if that means anything; I'm not sure why but I'm assuming that means there's some other errors happening before the 'Fatal' one, since there's no header tags, etc..

Here's the output of the index page in full with the error (page source looks the same, there's no additional markup tags in there)

/* $Id: node.css,v 1.2.2.1 2007/07/24 18:38:58 drumm Exp $ */ .node-unpublished { background-color: #fff4f4; } .preview .node { background-color: #ffffea; } #node-admin-filter ul { list-style-type: none; padding: 0; margin: 0; width: 100%; } #node-admin-buttons { float: left; margin-left: 0.5em; clear: right; } td.revision-current { background: #ffc; } .node-form .form-text { display: block; width: 95%; } .node-form .container-inline .form-text { display: inline; width: auto; } .node-form .standard { clear: both; } .node-form textarea { display: block; width: 95%; } .node-form .attachments fieldset { float: none; display: block; } Fatal error: Call to undefined function: node_get_types() in /var/hsphere/local/home/freecms/drupal.freecmstemplates.com/includes/theme.inc on line 271

If anyone's got any ideas on what to try I'd sincerely appreciate it! :) Anything I've searched up on the particular error in the forums doesn't seem to relate.

⋅ Categories: Drupal 5.x

Comments

gpk’s picture

gpk commented

Very odd. http://api.drupal.org/api/function/node_get_types/5 is in modules/node/node.module. Is the file there and readable by the web server (PHP) process?

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

boonies’s picture

boonies commented

Thank you kindly for the response gpk;

- Yes, the file is present and looks to be in order.

- I'm not quite sure how to determine whether the server/php has any issues with reading the .module file; is there a way to independently verify whether or not that might be an issue with the web server or it's PHP configuration? (excuse my technical ignorance).

Thanks again.

gpk’s picture

gpk commented

1. What are the permissions on node.module?
2. Does PHP run as an Apache module, or via CGI...?

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

boonies’s picture

boonies commented

1. node.module is a 644 (I gave it a CHMOD 777 for a second just in case - didn't change the error, switched it back)

2. PHP is running as an apache module.

gpk’s picture

gpk commented

Very odd. The server should be able to read that just fine.

I wonder if there is an obscure PHP setting that restricts the file type/extensions that it will read to .php and .inc, or something.

What is your Apache/PHP configuration? Hoping someone else will also chip in as I'm fast running out of ideas.

[update: May be worth talking to your server admin about why Drupal might not work. Do you know if PHP safe mode is on?]

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

boonies’s picture

boonies commented

Apache Version :
Apache/1.3.39 (Unix) PHP/4.4.7 mod_throttle/3.1.2 FrontPage/5.0.2.2635 mod_psoft_traffic/0.2 mod_ssl/2.8.29 OpenSSL/0.9.7a

PHP Version
4.4.7, safe mode is off.

I'll keep trying with the hosting provider, but they're not being terribly helpful unfortunately.

Thanks again for the suggestions.

Corny’s picture

Corny commented

I ran in same Fatal error: Call to undefined function: node_get_types() in /var/.../includes/theme.inc on line 271 after I installed airplane_reservation module. I started update.php which ran one time ok after module installation but wont display anything on a second try.
The function node_get_types() is there in the node.moule.

I had to roll back a database backup and tweak line 15 in resi.module like this:

// require_once('includes/sunriseset.php');
require_once('sunriseset.php');

Drupal 5.5,
GD library 2.0 or higher
MySQL database 5.0.24a
PHP 5.1.6
Web server Apache/2.0.55 (Ubuntu) PHP/5.1.6 mod_ssl/2.0.55 OpenSSL/0.9.8b

gpk’s picture

gpk commented

Hmmm I wonder if these problems are caused by the {system} table in the database being damaged or not installed correctly.

The following modules are "required" and so must have a 1 in the status field:
block
filter
node
system
user
watchdog

gpk
----
www.alexoria.co.uk

gpk
----
www.alexoria.co.uk

TravieMo9’s picture

TravieMo9 commented

I had the same problem with this fatal error. It happened under my first installation of Drupal on my Hosting Account and again when I uninstalled it and put on 5.5 as re-installation. After poking around a few pages into the site I got this fatal error, lost the theme and the navigation. I looked at the Database as recommended by gpk but am a little bit confused: where is the (1) supposed to be. "Status" has "data type" "attributes" "null" and "default". Some of those mudules have (1) under "default". Excuse me I am newbie.

This is getting quite frustrating. I have a working site on my localhost but no way to get it up on the web.

TravieMo9’s picture

TravieMo9 commented

I solved my problem. I looked at the Drupal Database and I noticed the repeated use of vti_cnf in the paths to files. I knew I had seen that someplace before. They are the folders that are placed in each directory by FrontPage. I had had a couple of FrontPage websites on my hosting and had FrontPage Server Extensions turned on. I replaced all sites with ones that didn't depend on FrontPage Extensions and I turned them off. But for some reason the vti_cnf got placed in the Drupal Installation and then into the database. I cleaned all of these out of my folders wherever they were, uninstalled Drupal and reinstalled it. Now things work fine. Gotta love Microsoft.

boonies’s picture

boonies commented

I realize this probably isn't particularly helpful since 5.6 is outdated now, but for whatever reason 5.7 in the same environment didn't give me the same issues.