earrame

Never mind. I see in another post that this is not possible. I will find another plugin.

Never mind, I figured it out.

I encountered this same problem again, this time I didn’t make any changes in Defender, the salt was just added automatically to the WP-config which caused it to print on screen. I was able to remove it with no further problems. Here is the content of that file:

/* DEFENDER GENERATED SALTS */
define('AUTH_KEY',         '?%:7I(B*?k!:qJCC;-L2vF-Rza@R5oNY7hjTZq

cM-7+|.%XH]L-)VY!1fsl,kCx’);
define(‘SECURE_AUTH_KEY’, ‘E`RF*RZRW@h_N8S8G-.?R<2ZW<.,t7VTQWeB&FEuJPk6C[A|cnv5$KMlv!<G,9D(‘);
define(‘LOGGED_IN_KEY’, ‘L],QLTX~wWx$;+?x:<!^#b4,0vxcD#?mwS|3Qij/(M-9mM$/c)_G3fY3Q;vfw]&q’);
define(‘NONCE_KEY’, ‘s#Tp#}|D_ar^$VMjAy?1%6}Yh+BD-YS?noZp)8g35()YKd^9$VuJFJX{~pr1|[&@’);
define(‘AUTH_SALT’, ‘$^_*JA7$v>Fsh=dYPI7$Iwz8V9AuY?%#g:)lSOD;HF fCm|vg& /n_mfb#g%}$4+’);
define(‘SECURE_AUTH_SALT’, ‘I7y4,*sMwL=<ubaPMz+~2-lD)XXby0AxA} ?0K&FjeZ2^,o oQ<!5V(C:7.J 5OH’);
define(‘LOGGED_IN_SALT’, ‘8afobMK)G%R~5Jo1C>QyT@V{](oz&9qcZ@upTtyH!fIj-()SQ?F7lEA]?$+nt]‘);
define(‘NONCE_SALT’, ‘&FG=p~=uhbv-ep3KZ:fM]6 . 9; ud9|/<mI[8hXj+ygnYqXP4`nb;./7O;2b|_,’);

<?php
/** Enable W3 Total Cache */
define(‘WP_CACHE’, true); // Added by W3 Total Cache

/** Enable W3 Total Cache Edge Mode */
define(‘W3TC_EDGE_MODE’, true); // Added by W3 Total Cache

/** WordPress’s config file **/
/** http://ww.wp.xz.cn/ **/
// ** MySQL settings ** //
//Added by WP-Cache Manager
define(‘DB_NAME’, “*******”);
// The name of the database
define(‘DB_USER’, “*******”);
// Your MySQL username
define(‘DB_PASSWORD’, “**********”);
// …and password
define(‘DB_HOST’, “mysql.seawingdesigns.com:3306″);
// …and the server MySQL is running on
// Change the prefix if you want to have multiple blogs in a single database.
$table_prefix = ‘wp_2sw142_’;

define( ‘DISALLOW_FILE_EDIT’, true );
// example: ‘wp_’ or ‘b2’ or ‘mylogin_’
// Turning off Post Revisions. Comment this line out if you would like them to be on.
define(‘WP_POST_REVISIONS’, false);
// 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’, ”);
/* Stop editing */
$server = DB_HOST;
$loginsql = DB_USER;
$passsql = DB_PASSWORD;
$base = DB_NAME;
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
// Get everything else
require_once ABSPATH . ‘wp-settings.php’;`

I had to do a full site restore. This experience makes me hesitant to use this plugin at all.

This is the content of the error log:

[Mon Oct 18 00:35:48.770821 2021] [fcgid:warn] [pid 21502:tid 140397019907840] [client 194.34.132.57:58512] mod_fcgid: stderr: PHP Warning: Cannot modify header information – headers already sent by (output started at /home/seawing_vps/seawingdesigns.com/wp-config.php:1) in /home/seawing_vps/seawingdesigns.com/wp-includes/functions.php on line 6712, referer: http://seawingdesigns.com/wp-login.php

Of course this repeats many times but it is the same every time.

I cannot open the login page/ dashboard at all, it is just a white screen.

Now my site seems to be hosed by this. The above code is displaying on the front end of the site and the dashboard is down completely. I tried to restore from a backup from a week ago and the problem persists. Please help soon!

Thank you,

How long until the next update? Should I make a manual automation?