drupal-4.7.3
http://www.shreemaa.org is broke

with this error below.
can someone help me identify what the problem is?
I have /home/shreemaa/public_html/httpdocs/drupal-4.7.3/includes/* all intact.

please help me.
thanks, Susan

===============
alien@www [/etc/init.d]# php /home/shreemaa/public_html/httpdocs/drupal/index.php

Warning: main(./includes/bootstrap.inc): failed to open stream: No such file or directory in /home/shreemaa/public_html/httpdocs/drupal-4.7.3/index.php on line 12

Fatal error: main(): Failed opening required './includes/bootstrap.inc' (include_path='.:/usr/lib/php:/usr/local/lib/php:/php/includes:/home/shreemaa/public_html/httpdocs/drupal/includes') in /home/shreemaa/public_html/httpdocs/drupal-4.7.3/index.php on line 12
===============

Comments

jayjenxi’s picture

I'm not sure what you mean by the files being intact. Do you mean you didn't remove or change any file? You might want to try uploading the files again cos sometimes file transfer might be unsuccessful. It might be a file corrupted by a bad transfer.

mayurikab’s picture

Just do the change in the file name.

use this line in
include('includes/bootstrap.inc');

may be this will help you out.
use this direct path instead of using /home/shreemaa/public_html/httpdocs/drupal-4.7.3/includes/bootstrap.inc

gpk’s picture

Is your Drupal installation in /home/shreemaa/public_html/httpdocs/drupal/ or in /home/shreemaa/public_html/httpdocs/drupal-4.7.3/? PHP seems to be looking for the includes/ folder in the drupal/ folder, not in drupal-4.7.3/.

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

sjames’s picture

drupal is a symlink to drupal-4.7.3

I found what the problem was.
the hosting service updated Apace/Php without telling me, and that broke drupal.
when they reverted back to the previous Apache config, all started working again.
I'm wondering if I should upgrade to drupal-5 to avoid this problem in the future; i.e. if Apache/Php is upgrade, drupal won't break?

Susan

gpk’s picture

drupal is a symlink to drupal-4.7.3

I wondered if something like that was causing the problem. I think Drupal's default .htaccess file has an option to follow symlinks, but maybe that option was disabled after the Apache/PHP upgrade.

Upgrading *may* help protect against this sort of problem, but I'm not certain it would have helped you in this case. More likely to be that the new version of Apache/PHP was configured differently. Also I don't know if PHP behaves identically from the command line as when called via a web page request.

If your site has resistered users other than yourself then you should probably consider upgrading for security reasons; otherwise it's really a question of whether the site is under ongoing development - in which case you may want the more recent facilities available in 5.x e.g. jQuery - or just "sitting there" quite happily as it is.

It's amazing how many hosts seem to think it's OK to upgrade their servers without telling their customers, then get deluged by customers complaining that their sites don't work any more! And have to revert their configuration to fix it!

[edit]
Drupal's .htaccess includes the following:

# Follow symbolic links in this directory.
Options +FollowSymLinks

Possibly you would have needed to put that in a .htaccess in your httpdocs/ folder to get everything to work with the new version of Apache/PHP. It looks to me like the symlink was causing the problem, rather than Drupal itself.
[/edit]

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