Support » Plugin: Cache Enabler » fatal error with the 1.8.2 update

  • Resolved SoulSearcher

    (@alios24)


    i`m having the same kinda issue with the last 2 updates…

    after the 1.8.2 update, it roars the hosting resources, CPU to 100%… the website is non responsive

    i disabled the plugin via FTP, and the the hosting starts to recover, but my WP site is now HTTP500 error…

    so after digging the error log in the hosting

    PHP Fatal error: Uncaught Error: Call to undefined function wp() in /home/trust/public_html/wp-blog-header.php:16

    and some friendly google searching this error, i found out my wp-config.php was empty :))))

    so i replaced it from the backup and everything started to work..

    today when i updated again this plugin to 1.8.3 version.. the same thing happened again.. site unresponsive, disabled the plugin via FTP, found out the wp-config.php was empty again.. replaced it, and not it works

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter SoulSearcher

    (@alios24)

    whats wrong ? i haven`t added any other plugin and nothing has been modified with my Divi theme

    i`m thinking about searching for another cache plugin

    HarriL

    (@harril)

    This same thing also happened to me. Empty wp-config.php

    agenciesFirst

    (@agenciesfirst)

    Hi @alios24 I use also Divi theme on NGINX server and it works perfect for me. I would say, try deactivating and deleting the Cache Enabler complete from WordPress. Make sure that Database has no rest data from Cache Enaber and no directories and files from CE exitst in upload folder. Than installing fresh and new again. If the problem further exsisting, than you have maybe the wrong hosting? Thanks

    Thread Starter SoulSearcher

    (@alios24)

    the plugin works..

    updating the plugin crashes the whole hosting, and empties (not removes) the wp-config.php file

    happened twice with the 1.8.2 and 1.8.3 updates

    currently my website is running the latest 1.8.3 version and its fine
    just that i don`t think i can debug and recover files everytime i update this plugin :DD

    Corey

    (@coreyk)

    @alios24 and @harril, we’re looking into the issue related to the wp-config.php file that appears to be occurring for a couple users (#286). Do either of you happen to be using any hooks related to Cache Enabler, such as the pre_option_cache_enabler hook?

    HarriL

    (@harril)

    I don’t know what that hook is so I’m probably not using it.

    Corey

    (@coreyk)

    @harril, thanks for the additional information. Would it be possible to receive your Site Health Info? This can be obtained by going to the WordPress dashboard > Tools > Site Health > Info > Copy site info to clipboard. (It can be provided privately through our contact form while referencing this thread if you’d prefer.)

    Thread Starter SoulSearcher

    (@alios24)

    same thing.. i`m not using hooks, just a standard cache enabler plugin install

    other plugins i have don`t have anything to do with cacheing,

    the last 2 updates to 1.8.2 and 1.8.3 made my hosting services go to 100% resources, then it went to HTTP500, and i found the wp-config.php file empty

    now i just saw the 1.8.4 update.. and i`m not even gonna try, cause its going to crash my hosting again, and i have to recover the wp-config.php again…

    i`ll also send you my site info via ur contact form

    HarriL

    (@harril)

    @coreyk Just sent you site health info via your contact form.

    Corey

    (@coreyk)

    Thank you @harril and @alios24 for sending that over. This is so odd. With the information you’ve shared I’ve attempted to replicate this issue in every way that I can to no avail. That is going through all of the plugins (can only do the free ones) and then various site configurations matching what you both have set.

    Each time the install or update process is completed successfully without any issues. That is going from any old version, including branches 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, and 1.8, to the latest version as of writing this (1.8.4). That means unfortunately at this point with the information at hand I’m still unsure why it’s occurring for you two.

    To troubleshoot this further, can you please first ensure nothing related to Cache Enabler is in your functions.php file or any code inserting plugins (e.g. Code Snippets)? I’m of course assuming nothing is in there as you two have mentioned, but it’d be good to double check if possible. If nothing is found can you please try increasing your server memory limit and try again (e.g. something like 1024M with a max of 2048M)? I’d recommend deactivating and uninstalling what you have and then installing 1.8.4 fresh when attempting this.

    Please don’t feel obligated to do this, but it will help me debug it further. If needed, one way to back up the wp-config.php file is by temporarily duplicating it (e.g. wp-config-backup.php). I understand this is far from ideal, but trying to work with what I have. Thanks for your understanding.

    Thread Starter SoulSearcher

    (@alios24)

    hello,

    i don`t have any modification to the functions.php or any other file, i tried to keep my WP clean, so i would never have to deal with errors like these 🙂

    i will try to remove the plugin and make a fresh instal, especially since i don`t have any setting for the plugin so nothing would be lost 🙂

    also im increasing the memory sizes, as you suggested, ill return with some feedback, if it crashes again and empties my config.php file 🙂

    Thread Starter SoulSearcher

    (@alios24)

    okey so i did that and everything is good so far 🙂

    1. increased memory to 1024M and server to 2048M
    2. updated WP to 5.8.1
    3. updated Divi to latest 4.10.6
    4. disabled cache enabler, then removed it
    5. checked with FTP to see if there are any remains in the plugins folders.
    6. installed fresh new cache enabler 1.8.4
    7. crossed fingers and watched the server resources in cPanel not go to 100% 😀
    8. everything runs smooth

    will see with the next updates if the error returns..

    thanks for your support

    Corey

    (@coreyk)

    @alios24, great! I’m happy to hear that. 🙂 Also, thank you for sharing the steps you’ve taken. That is always helpful! I’ll be available at any time if you’re in need of my assistance again.

    @harril, I’m still here to help until the issue is resolved for you as well.

    Thread Starter SoulSearcher

    (@alios24)

    thanks for the replies, i`m using this plugin for some time now, and it would have been ashamed to remove it..

    anyways i`ll be having my fingers crossed on the next update 😛

    cheers.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘fatal error with the 1.8.2 update’ is closed to new replies.