ABSPATH wp-settings.php errors

  • I’ve been trying to figure this out for the past few days. My hosting company (Ionos) blamed it on my PCI Scanner and told me I need to “contact WordPress and let them turn off the debug on their end”. This is happening on every single website I have with Ionos (I only scanned one out of 8) and failed the PCI scan due to wp-settings issues. I also set up a fresh site today to test this, with no plugins and just the default theme installed and still get the error. It happens when going to https://www.example.com/wp-settings.php in any browser replacing example.com with any of my domain names. Some sites are on the current version of WordPress and others are on the previous version.

    For all eight sites, it displays:

    Warning: Use of undefined constant ABSPATH – assumed ‘ABSPATH’ (this will throw an Error in a future version of PHP) in /shows-full-server-file-path-here/wp-settings.php on line 33

    Warning: require(ABSPATHwp-includes/version.php): failed to open stream: No such file or directory in /shows-full-server-file-path-here/wp-settings.php on line 33

    Fatal error: require(): Failed opening required ‘ABSPATHwp-includes/version.php’ (include_path=’.:/usr/lib/php7.4′) in /shows-full-server-file-path-here/wp-settings.php on line 33

    This is the last section of wp-config.php for all sites:

    /* That’s all, stop editing! Happy publishing. */

    /** Absolute path to the WordPress directory. */
    if ( ! defined( ‘ABSPATH’ ) ) {
    define( ‘ABSPATH’, dirname( __FILE__ ) . ‘/’ );
    }

    /** Sets up WordPress vars and included files. */
    require_once ABSPATH . ‘wp-settings.php’;

    Line 33 of wp-settings.php shows:
    require ABSPATH . WPINC . ‘/version.php’;

    I’ve also tried various ways of turning off debugging with no success. I’m not very familiar with the code, so I’m not sure where else to look.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter cyunicorn

    (@cyunicorn)

    This is what shows in wp-includes/version.php

    <?php
    /**
    * WordPress Version
    *
    * Contains version information for the current WordPress release.
    *
    * @package WordPress
    * @since 1.1.0
    */

    /**
    * The WordPress version string.
    *
    * @global string $wp_version
    */
    $wp_version = ‘5.7’;

    /**
    * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.
    *
    * @global int $wp_db_version
    */
    $wp_db_version = 49752;

    /**
    * Holds the TinyMCE version.
    *
    * @global string $tinymce_version
    */
    $tinymce_version = ‘49110-20201110’;

    /**
    * Holds the required PHP version.
    *
    * @global string $required_php_version
    */
    $required_php_version = ‘5.6.20’;

    /**
    * Holds the required MySQL version.
    *
    * @global string $required_mysql_version
    */
    $required_mysql_version = ‘5.0’;

    Thread Starter cyunicorn

    (@cyunicorn)

    After looking at the folders more, I realized that all of the files being referenced in the errors are located in the htdocs folder in the opcache. Is there a way to fix that? The .php files there are .php.bin files.

    All errors are referencing htdocs/appxxxxxxxx/wp-settings.php

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘ABSPATH wp-settings.php errors’ is closed to new replies.