Ok, I tried the “rename the plugins directory method” and now I’m getting 500 for all pages, even when I renamed the plugins directory back!
Hi @laurin1
If you are able to access the file system, are there any error_log files in the admin directory?
Thanks,
Kevin
Thank you
Thank you
Thank you
Thank you
Thank you
Thank you
Thank you
Thank you
Thank you
Thank you
My wp-config.php file was all jacked up (had serious syntax errors). How could a plugin do that???
Glad to hear that you were able to resolve it. It’s possible that there were some writes to the file that may have re-ordered it?
What did you see that was changed?
Our plugin does the following:
1. If the WP_CACHE define is already set, do not change anything.
2. If the wp-config file is not writable, return an error.
3. If there is a define WP_CACHE false, set it to true.
4. If (3) does not exist, Look for table_prefix and add a define before that.
5. If (4) does not exist, try to add to the start of the file after <?php
6. if (5) fails, return error
Do you know what case you had? So we could see if something happened because of the cache plugin.
Here is what was broken, this is lines 1-4 of wp-config.php:
<?php
global define('WP_CACHE', true);
$table_prefix;
For some reason, it stuck “define(‘WP_CACHE’, true);” between global and $table_prefix. I added the global $table_prefix (because PHPStorm throws a warning if I don’t have that and it’s just a good reminder).
Thanks for that!
That explains everything actually. We specifically add it before $table_prefix, and did not search for the beginning of the line. We’ll work on a fix for this situation, so it doesn’t happen again.
Thanks again!
Kevin
