Reply To: Constant ABSPATH already defined in wp-config.php

I corrected the PHP Line 52 error and that php error is not coming up anymore. and the wp-config.php is not being quarantined.

I increased the BPS @ini_set(‘memory_limit’,’64M’);  to  @ini_set(‘memory_limit’,’512M’);

I turned off the cURL scan and Pre Installation ran but it did not find any Plugin Firewall paths to whitelist and the few that was in there disappeared so the Plugins Whitelist emptied out when I ran the Pre Installation with cURL scan off.

I turned cULR scan back on and it came up with the same database error but if found paths to whitelist and a little more than it was finding before when the error came up.  So still not working right. I need all the paths to be whitelisted so my sight functions properly.

What now?