WordPress.org

Forums

Fatal error: require_once() [function.require]: (4 posts)

  1. trondert
    Member
    Posted 9 years ago #

    I got WP running on one user on my server, and now i want to add another. But when i follow the instructions, and try to point my browser to: install.php i get this error:

    Warning: require_once(/home/hula/public_html/wp-includes/wp-db.php) [function.require-once]: failed to open stream: No such file or directory in /home/hula/public_html/wp-settings.php on line 73

    Fatal error: require_once() [function.require]: Failed opening required '/home/hula/public_html/wp-includes/wp-db.php' (include_path='.:/usr/share/php5:/usr/share/php') in /home/hula/public_html/wp-settings.php on line 73

    Mysql user is added, cant see whats wrong...

    my conf:

    <?php
    // ** MySQL settings ** //
    define('DB_NAME', 'hula'); // The name of the database
    define('DB_USER', '-correct-'); // Your MySQL username
    define('DB_PASSWORD', '-correct-'); // ...and password
    define('DB_HOST', 'localhost'); // 99% chance you won't need to change this value

    // You can have multiple installations in one database if you give each a unique prefix
    $table_prefix = 'wp_'; // Only numbers, letters, and underscores please!

    // Change this to localize WordPress. A corresponding MO file for the
    // chosen language must be installed to wp-includes/languages.
    // For example, install de.mo to wp-includes/languages and set WPLANG to 'de'
    // to enable German language support.
    define ('WPLANG', '');

    /* That's all, stop editing! Happy blogging. */

    define('ABSPATH', dirname(__FILE__).'/');
    require_once(ABSPATH.'wp-settings.php');
    ?>

  2. moshu
    Member
    Posted 9 years ago #

    I'd check if every file has been uploaded into the wp-includes folder. Try a fresh upload.

  3. rivestfr
    Member
    Posted 9 years ago #

    I have a very similar problem. At first it was the install.php who could not run require_once of admin-functions.php (deep in the the required tree). Even using an include statement cause an HALT. I kind of pass that successfully by commenting it out (did not need it to install, just for upgrade).

    But, when login in, I got that same problem with wp-login, that could not require_once wp-db.php (exactly as describe by trondert). Again, I got an HALT, but I can directly call wp-db.php with my browser, and it parses fine (except that it misses variables lower in the require tree).

    Hope we will find a solution!

  4. neville
    Member
    Posted 8 years ago #

    I just had something very similar:

    Warning: require_once(/home/.filou/ehobsonc/www.nevillehobson.com/wp-content/themes/k2/) [function.require-once]: failed to open stream: Success in /home/.filou/ehobsonc/www.nevillehobson.com/wp-includes/functions.php on line 2172

    Fatal error: require_once() [function.require]: Failed opening required '/home/.filou/ehobsonc/www.nevillehobson.com/wp-content/themes/k2/' (include_path='.:/usr/local/php5/lib/php') in /home/.filou/ehobsonc/www.nevillehobson.com/wp-includes/functions.php on line 2172

    Lots of head scratching. My blog runs WP 2.0.6 and, before this error, I'd been able to see the blog perfectly fine. I had changed nothing in the WP files nor the K2 theme.

    What I had done, though, was update a couple of plugins and install a new one.

    Updated plugins: PodPress 7.0, Live 0.4, Diagnosis 1.2.
    New plugin: View All Comments 0.1.

    First, though, I switched themes back to the Kubrick default to see if this was theme specific, given the ref to K2 in the error message.

    Same error resulted, referencing 'default' in place of k2. So, not theme specific.

    Next, a process of elimination with the plugins.

    First I deleted PodPress 7 and reverted back (re-uploaded) to version 6.8. Prime reason was 7 produced other errors in the saved PodPress config settings relating to the iTunes configuration. Reverting to 6.8, those errors disappeared.

    Once I'd done that, I viewed the blog and the same warning/fatal error mentioned above error existed. So PodPress doesn't seem to be the culprit.

    Next, deactivate View All Comments. And that's where the error stopped.

    With VAC deactivated, the error disappears entirely and the blog works fine.

    Now for a note to the plugin developer...

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.