• Hi –

    There appears to be a bug in the latest version of the plugin. When saving settings, the following text is inserted into my wp-cache-config.php.

    ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$

    Obviously, this is not valid syntax, which causes the server to throw 500 errors. I am using SuperCache Version 1.5.4 and WordPress 4.8.1.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Which setting or form in the settings page did you submit that caused this?

    Hey there,

    it happened twice (friday and today) on my website too.

    The first time was when I ran a plugin called Postie, PHP was printing an error on wp-cache-config.php and today it happened again when I updated a comment.

    I just checked now php log and there are a lot of super cache errors:

    [28-Aug-2017 14:30:16 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/…/public_html/wp-content/wp-cache-config.php:90) in /home/…/public_html/wp-includes/pluggable.php on line 1210

    @joseleonardo – edit your wp-cache-config.php and remove the extra characters. That’s what is causing the warnings you’re seeing.

    I don’t know why that text was added to the config file however. ??

    Donncha, thank you for replying!

    I did it on friday, but it happened today too, I have uninstalled and reinstalled Super Cache again and I am monitoring the file log.

    For now, everything looks good…

    Donncha,

    I also have noticed that my plugin page is loading a bit more slowly than before and when I down the page quickly (pressing END button on keyboard) it is stoping for few milliseconds on WP Super Cache item.

    Hi all, we have noticed the exact same problem!

    We noticed that in the days after updating WP Super Cache to 1.5.5, many sites seem to regenerate their wp-cache-config.php. In most cases this has gone well, but we too had one file where NUL bytes were intermixed in the file. This caused the site to barf the contents at the top of the theme and the admin panel, likely as PHP could not parse the file anymore.

    What didn’t resolve it: deactivating and re-activating WP Super Cache

    What did resolve it: deactivating, deinstalling, re-installing, re-activating WP Super Cache.

    Example hexdump (hope this is formatted right..)

    
    # hexdump -C wp-cache-config-broken.php
    00000000  24 77 70 5f 63 61 63 68  65 5f 63 72 6f 6e 5f 63  |$wp_cache_cron_c|
    00000010  68 65 63 6b 20 3d 20 31  3b 20 2f 2f 41 64 64 65  |heck = 1; //Adde|
    00000020  64 20 62 79 20 57 50 2d  43 61 63 68 65 20 4d 61  |d by WP-Cache Ma|
    00000030  6e 61 67 65 72 0a 24 77  70 73 63 5f 6c 61 73 74  |nager.$wpsc_last|
    00000040  5f 70 6f 73 74 5f 75 70  64 61 74 65 20 3d 20 31  |_post_update = 1|
    00000050  35 30 34 31 38 39 30 33  31 3b 20 2f 2f 41 64 64  |504189031; //Add|
    00000060  65 64 20 62 79 20 57 50  2d 43 61 63 68 65 20 4d  |ed by WP-Cache M|
    00000070  61 6e 61 67 65 72 0a 00  00 00 00 00 00 00 00 00  |anager..........|
    00000080  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    00000090  00 00 00 00 00 00 00 00  00 00 00 00 00 24 77 70  |.............$wp|
    000000a0  73 63 5f 6c 61 73 74 5f  70 6f 73 74 5f 75 70 64  |sc_last_post_upd|
    000000b0  61 74 65 20 3d 20 31 35  30 34 31 38 39 30 33 30  |ate = 1504189030|
    000000c0  3b 20 2f 2f 41 64 64 65  64 20 62 79 20 57 50 2d  |; //Added by WP-|
    000000d0  43 61 63 68 65 20 4d 61  6e 61 67 65 72 0a 00 00  |Cache Manager...|
    000000e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
    *
    00000170  00 00 00 00 00 00 00 00  00 00 00 00 24 63 61 63  |............$cac|
    00000180  68 65 5f 74 69 6d 65 5f  69 6e 74 65 72 76 61 6c  |he_time_interval|
    00000190  20 3d 20 27 33 36 30 30  27 3b 20 2f 2f 41 64 64  | = '3600'; //Add|
    000001a0  65 64 20 62 79 20 57 50  2d 43 61 63 68 65 20 4d  |ed by WP-Cache M|
    000001b0  61 6e 61 67 65 72 0a 24  63 61 63 68 65 5f 73 63  |anager.$cache_sc|
    

    Here’s an example of what the admin panel looked like: https://i.imgur.com/F5MRx4Q.png

    Using PHP 5.6.31

    • This reply was modified 7 years, 2 months ago by Slik.

    It happened again today with me too.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Saving Cache Settings Corrupts wp-cache-config.php’ is closed to new replies.