nigelrs

Any takers on this? It is either a wordpress conflict or a problem with the config file that is loaded by WP by default

Unless there is another command that mirrors and masks as FS_METHOD, here is the file as I cannot see it twice and it is not in the wp_load.php having looked:

<?php
define(‘WP_AUTO_UPDATE_CORE’, false);// This setting was defined by WordPress Toolkit to prevent WordPress auto-updates. Do not change it to avoid conflicts with the WordPress Toolkit auto-updates feature.
/**
* 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.www.ads-software.com/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’, ‘****’);

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

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

/** MySQL hostname */
define(‘DB_HOST’, ‘localhost:3306’);

/** 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.www.ads-software.com/secret-key/1.1/salt/ www.ads-software.com 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’, ‘*****!u86SKRW226kH)JBQ7p/xV8P6JH|8Y1]x*&BUq-402Td0j!’);
define(‘SECURE_AUTH_KEY’, ‘*****K2UsJ8zqtWc)2|JUy88*3|ZFlU#j[TsyIaGTt0:J9GR3@5w5i6xH4P48’);
define(‘LOGGED_IN_KEY’, ‘****8CDhEdhK~(15sH609+(3K|D****UzK8XRa6dT)jh54y_5%MDpw’);
define(‘NONCE_KEY’, ‘*****UzPw-P&K3qt+|3)4oZ#FVpq]6o8~6Ep;~IPRq794)x2cG0a(+GzYLp’);
define(‘AUTH_SALT’, ‘****6i77#T&fJS2yP*on7+Y!GA9qr45Tp9Mw0XacE1u7bMkYgQ#7p1Yyo55ny/’);
define(‘SECURE_AUTH_SALT’, ‘YzE0g3G******/b4T4ygP-c*/&7NvZx9)c@#q*k[n@skT4v29~5I1:2_F[#~Y’);
define(‘LOGGED_IN_SALT’, ‘F)xfN!b*****6-#*%SAQ!1XA7X!2_zJ0(U5~j0s-(8J||*l7BzI[e_34;/e7h’);
define(‘NONCE_SALT’, ‘y@JN;Ey1370******f+1f~Wc8l2ru5KF_7eI9/C~7K&0u-tS;nYW9l8′);
/**#@-*/

/**
* 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 = ’73***’;

/**
* 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.www.ads-software.com/Debugging_in_WordPress
*/
define(‘WP_DEBUG’, ‘false’);
define(‘WP_MEMORY_LIMIT’, ‘256M’);

/* 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’);

define( ‘WP_ALLOW_MULTISITE’, true );

define (‘FS_METHOD’, ‘direct’);

***********
Is there something masking as FS_METHOD?

Hi,

Thanks, I had looked at that. I have over 20 sites and only 2 show this. I have compared the wp-config.php on 1 site with this error and 1 site without it and they are identical (aside from the usual (table_prefix, key code, database/user names/pw and a define wp_memory_limit line).

Something else has to be triggering this?

It is a line required by WP, so I don’t want to take it out as it could affect the FTP and there is nothing else in the config file. Confused…

I have been getting this error. Started at 250mg memory allowance when scanning, now at 950mg and it still fails. I can run it on other sites with no problem, but just one of the sites seems to trip it up, I have run it on larger sites with much less memory and it has run. Not sure what to do, have tried clearing cache etc. I have uninstalled and reinstalled and it has loaded it back in, even with a site clear it must have had information still retained in the WP database?

Not sure what the next step is.