WordPress.org

Forums

The Support Forums will be in read-only mode for a scheduled maintenance window on 01 September 2016 14:00 UTC - 20:00 UTC. More information.

Installation problems (4 posts)

  1. Anders
    Member
    Posted 11 years ago #

    When I tried to install WordPress I got the following error:
    Fatal error: Failed opening required '//wp-settings.php' (include_path='.:/usr/local/lib/php') in //wp-config.php on line 20
    In wp-config.php I found this line:
    define('ABSPATH', dirname(__FILE__).'/');
    I canged it to:
    define('ABSPATH', '<path to wp-dir>');
    I think this is the wrong way to go, but I had to try something
    It now installed WordPress but when I tried to log in, it gave me the same type of error.
    Any suggestions?
    I think that the prerequisites are met since my ISP has PHP 4.1.2, MySQL 3.23.58 and Apache 1.13.19 (no mod_rewrite).
    //Anders.

  2. Anders
    Member
    Posted 11 years ago #

    I tried to install the newest wordpress I could get a hold on (2004-09-19).
    I still needed to change the define ('ABSPATH' .... in the wp-config.php to my wordpress directory for the installation to work.
    But the same problem exists, I get the following message when I log in:
    Fatal error: Failed opening required '//wp-config.php' (include_path='.:/usr/local/lib/php') in //wp-includes/wp-l10n.php on line 4
    Will I need to go through all PHP-code to change out the dirname(__FILE__) within all path definitions, or is there some other solution?
    // Anders.

  3. Mark (podz)
    Support Maven
    Posted 11 years ago #

    An error such as this, which includes a double backslash in a filepath, indicates a fault in the actual PHP installation.
    This sort of error is very occasionally reported here, and even though this PHP fault is relayed to the poster, no-one has yet to come back with any other definitive answer.

  4. Anders
    Member
    Posted 11 years ago #

    Do you think that an upgrade of the PHP installation could solve the problem?
    I have found indications stating that there has been a change in the dirname functions behaviour after version 4.3.0. I will ask my ISP to upgrade the PHP installation (hoping they are willing) to see if this could solve the problem.
    <?php
    //before PHP 4.3.0
    dirname('c:/'); // returned '.'
    //after PHP 4.3.0
    dirname('c:/'); // returns 'c:'
    ?>

    I found this piece of information at: http://se.php.net/.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.