Hi,
This usually means you made changes to the wp-config.php (DB_NAME, DB_USER, DB_PASSWORD, DB_HOST or $table_prefix) and the firewall cannot parse it.
You can debug it with this PHP script and paste the results here.
Hi,
Thank you for the fast feedback. The result from the script is
cannot read DB_NAME
cannot read DB_USER
cannot read DB_PASSWORD
cannot read DB_HOST
cannot read table_prefix
which is odd, as I have not changed anything except adding these lines right in front of “That’s all, stop editing! Happy blogging.”:
define( 'SD_HIDE_MARKDOWN_BOX', true );
define('FORCE_SSL_ADMIN', true);
define('DISALLOW_FILE_EDIT', true);
What is the next step for debugging/finding the error?
Is the $table_prefix value using single quotes (‘) and not double-quotes(“) ?
$table_prefix = ‘whatever’; < will be okay
$table_prefix = “whatever”; < will not be okay
All values are in single quotes.
Can you mask the DB name, username and password and send me a copy of your wp-config.php to contact-at-nintechnet.com ?
I did not receive it yet.
I received it. But if I run the test script, it works:
DB_NAME: OK
DB_USER: OK
DB_PASSWORD: OK
DB_HOST: OK
table_prefix: OK
Do you have an encoding issue with the original file? I can see, for instance, it is using CR/LF (Windows format) rather than LF.
Hi, here is an update. On a completely different server, I have exactly the same problem except that when running your debug-script, everything is okay. Also, there is no additional variables configured in wp-config.php.
This time, however, it is WordPress 4.0 and 1.2.6/20140810.
Hi,
I just cannot find out what the problem is.
Do you have a wp-config file that works with NinjaFirewall ? You could try to copy it to the server where you have the problem, and simply edit the DB_NAME, DB_USER, DB_PASSWORD, DB_HOST and $table_prefix, then check if that works ?
I am thinking about a possible encoding issue. Or maybe ensure that you uploaded it via FTP using ASCII mode rather than binary ?
