Viewing 10 replies - 1 through 10 (of 10 total)
  • same problem here… after yesterday’s plugin update i keep having error 500 to the website and wp-config seems to go broken everytime even after i reupload it

    updating to 5.0.6 (which rolled out 3 hours ago) did not solve the issue.

    • This reply was modified 2 weeks, 2 days ago by reloaded192.

    Hi, I’m just a WordPress user, I’m not part of the plugin team.
    Have you checked your server error logs? What they have to say?

    It looks strange to me the cache plugin can broke the WordPress wp-config.php , how did you know is that file broken?

    Deactivate the cache plugin resolve the issue you are facing?

    Hi,

    yes checked, and was reporting error in wp-cofing (which is why i immediately checked).

    The wp-config fail to load at different level, sometimes i found it half empty, sometimes i find it with only this line in it:

    define(‘WP_CACHE’, true); // Added by WP Cloudflare Super Page Cache

    but the reason why i report this as a bug is that since i deactivated the plugin by renaming the folder and uploaded a correct wp-config … the website loads correctly.

    Thanks for the answer.
    The wp-config.php is the core php file located in the root folder of your WordPress installation?

    Looks strange to me that a plugin can edit this file.

    but the reason why i report this as a bug is that since i deactivated the plugin by renaming the folder and uploaded a correct wp-config

    I never seen such issue but you said you renamed the plugin folder to deactivate the plugin?
    You uploaded the correct wp-config from where, a backup?

    The wp-config.php is not the core configuration WordPress file with also all database configuration? WordPress cannot work if this file is empty.

    The wp-config fail to load at different level, sometimes i found it half empty, sometimes i find it with only this line in it:

    define(‘WP_CACHE’, true); // Added by WP Cloudflare Super Page Cache

    Maybe I’m confused.
    The reason why you read my reply is because I see this topic has not received yet a reply from the plugin team and this since 2 days from his creation.

    The first post has not many info so maybe for that reason the topic is also missing replies, I don’t know.
    My intent is just to help you to get support ??

    Ok i’ll try to clarify.

    1. i noticed error 500 on my website so i went to take a look at server log file to understand what happend and it was saying “error in wp-config line 41”

    2. so i take a look at my config and find out that it was compromised: just by looking at it i could say that half of it was missing

    3. i tried to reupload a new one from my automatic update, so i checked the website and was loading fine but after 1 maybe 2 minute and still error 500

    4. looked at config file and it was full empy execpt for this line: define(‘WP_CACHE’, true); // Added by WP Cloudflare Super Page Cache

    5. so i started to think about it and i was remembering the night before i did some plugin updates and this was one of them.

    6. i also contacted my server assistance to make sure because in my experience it was the first time that a plugin did compromise my config file this way

    7. they also concluded it could be a plugin failure

    8. so i deactived it by renaming the folder and uploading a new config file (always the same from the backup)

    9. since then the website is online with no problem, i tried to update the plugin to version 5.0.6 but i ended with the same results and i still did not tryed the 5.0.7

    I just hoped some of the plugin creators could make clear what happened, i don’t see in the changelog of the 5.0.7 something that can make me understand they fixed.

    • This reply was modified 2 weeks, 1 day ago by reloaded192.

    I hope as you the plugin team can reply to you.
    The reason of my messages here is to let you explain better as I saw this topic has without any reply since different days.

    Still don’t understand if you talk about the wp-config.php file of WordPress located at the root of WordPress and still not imagine how this file can be erased in his content. I never seen such issue before and also if I’m using the super-cache plugin I’m not facing this.

    I believe that for help you the team should have info on how to reproduce the issue, if not they may be not able to help you. It looks a strange situation the one discussed here.

    Best luck to get this answered and resolved.
    I hope now this topic has more useful info for who read it.

    somersby

    (@somersby)

    Hi. I had a similar problem when updating another plugin 2 months ago. Later there were several other topics from users with the same problem. https://www.ads-software.com/support/topic/update-6-5-0-2-broke-wp-config/

    reloaded192

    (@reloaded192)

    Hi somersby thanks for your message, i’ll take note of it.

    Fortunately i tried to install version 5.0.7 and since yesterday the website is working.

    I’ve had the same problem.

    The latest updates, including version 5.0.8 have left my wp-config.php broken.
    Either by just leaving one row at the top like so:

    <?php
    define('WP_CACHE', true); // Added by WP Cloudflare Super Page Cache

    or by leaving only the upper half of the file intact.

    Super Page Cache is probably the culprit since it’s the only plugin recently updated when this error occurs. Shortly after the plugin update, my advanced-cache.php file is edited at the same timestamp as wp-config.php. And Super Page Cache is the only plugin editing the advanced-cache.php file.

    Unfortunately, after multiple plugin updates, I’ve been able to confirm this error across over 50 sites, without fail.

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.