• Resolved jidwictut9

    (@jidwictut9)


    Hello, every time a backup is run—whether manually or as part of a scheduled task—my WP Super Cache cache gets deactivated.

    I am experiencing a conflict between BackWPup and WP Super Cache.

    Every time a BackWPup job starts (even a database-only backup), WP Super Cache is automatically disabled. I observed that the file wp-cache-config.php gets a new timestamp exactly when the backup starts, and the caching state switches to “Off” in the WordPress dashboard.

    I have already tried the following:

    • Excluded the /wp-content/cache/ directory from the backup.
    • Excluded the wp_options table from the database backup.
    • Both steps did not resolve the issue.

    The only workaround that works is setting the file permissions of wp-cache-config.php to 444 (read-only). This prevents the caching from being turned off during the backup process.

    Is there any specific function or hook in BackWPup that triggers a cache flush or a configuration check which might cause this behavior?

    Best regards,

    • This topic was modified 6 days, 16 hours ago by jidwictut9.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter jidwictut9

    (@jidwictut9)

    After playing around a bit, I realized that this error has been occurring since version 5.6.7

    Plugin Support Saransh

    (@saranshwpm)

    Hi,

    Thank you for the detailed report and for the troubleshooting you already did.

    I was able to replicate this behavior on my end as well. I’ve opened an internal report for our developers so they can review why WP Super Cache is being disabled when a BackWPup job starts.

    Your notes about wp-cache-config.php being updated at the exact backup start time are very helpful and have been included in the report.

    I’ll get back to you once I have an update from our team.

    Thank you again for bringing this to our attention.

    Plugin Support Saransh

    (@saranshwpm)

    Hello,
    We appreciate your patience.

    The developers have acknowledged the issue, and it will be addressed in one of the upcoming update.

    Thank you for bringing this to our attention.

    Best regards,

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.