Hi @jhunter93
Better Search Replace Support Team here, Thanks for reaching out with your query we would be happy to assist!
Based on your diagnostic info, it seems your WP_DEBUG is still disabled:
WP_DEBUG: Disabled
Can you please verify on your wp-config.php if the WP_DEBUG lines you’ve added is above this line:
/* That's all, stop editing! Happy blogging. */
From my DBA-
This is from the debug section of the file “/etc/wordpress/wp-config.php” on wpprdlx.
Russell
/**
* 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 documentation.
* @link https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/
*/
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', true );
define( 'SAVEQUERIES', true );
// Write to a custom file path:
define('WP_DEBUG_LOG', '/tmp/wp-debug.log');
/
Below is the content of the whole file.
<?php
/**
* The base configuration for WordPress
*
* The wp-config.php creation script uses this file during the installation.
* You don't have to use the website, you can copy this file to "wp-config.php"
* and fill in the values.
*
* This file contains the following configurations:
*
* * Database settings
* * Secret keys
* * Database table prefix
* * ABSPATH
*
* @link https://developer.ww.wp.xz.cn/advanced-administration/wordpress/wp-config/
*
* @package WordPress
*/
// ** Database settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define( 'DB_NAME', 'wordpress' );
/** Database username */
define( 'DB_USER', 'wpadmin' );
/** Database password */
define( 'DB_PASSWORD', '**********************' );
/** Database hostname */
define( 'DB_HOST', '192.168.100.61' );
/** 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.ww.wp.xz.cn/secret-key/1.1/salt/ ww.wp.xz.cn 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!
*
* At the installation time, database tables are created with the specified prefix.
* Changing this value after WordPress is installed will make your site think
* it has not been installed.
*
* @link https://developer.ww.wp.xz.cn/advanced-administration/wordpress/wp-config/#table-prefix
*/
$table_prefix = 'wp_';
/**
* See http://make.ww.wp.xz.cn/core/2013/10/25/the-definitive-guide-to-disabling-auto-updates-in-wordpress-3-7
*/
/* Disable all file change, as RPM base installation are read-only */
define('DISALLOW_FILE_MODS', false);
/* Please ensure that this is either 'direct', 'ssh2', 'ftpext', 'ftpsockets' or false */
define('FS_METHOD', 'direct');
/* Disable automatic updater, in case you want to allow
above FILE_MODS for plugins, themes, ... */
define('AUTOMATIC_UPDATER_DISABLED', true);
/* Core update is always disabled, WP_AUTO_UPDATE_CORE value is ignore */
/**
* 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 documentation.
*
* @link https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/
*/
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', true );
define( 'SAVEQUERIES', true );
// Write to a custom file path:
define('WP_DEBUG_LOG', '/tmp/wp-debug.log');
/* Add any custom values between this line and the "stop editing" line. */
define( 'WP_MEMORY_LIMIT', '1024M' );
define( 'WP_MAX_MEMORY_LIMIT', '2048M' );
define( 'WP_ALLOW_MULTISITE', true );
/* That's all, stop editing! Happy publishing. */
/** Absolute path to the WordPress directory. */
if ( ! defined( 'ABSPATH' ) ) {
define('ABSPATH', '/usr/share/wordpress');
}
/** Sets up WordPress vars and included files. */
require_once ABSPATH . 'wp-settings.php';
Good afternoon,
We have resolved the problem. It was happening on our production server after we had a redirect for a SSL. I now have a solution that allows me to run the Better Search Replace without error.
Thank you,
Jennifer
