WP Super Cache plug-in timestamp error solution

We searched for this issue on the WordPress official English forum and found that many users encountered similar problems, most of which were the same, and the solutions were different. According to the plug-in author's discussions with many users, most of them are due to the use of compression-related plug-ins or the inclusion of compression functions in themes or plug-ins.

Earlier versions of WP Super Cache may also cause the entire problem because WordPress is installed in sub-directories. You can check. htaccess under the root directory of the website to solve this problem. However, you can ignore this factor.

We recommend that you follow these steps to check your WordPress plug-ins and themes to solve the timestamp problem:

1. Follow our WP Super Cache Tutorial to install the plugin. After the installation, click "Test Cache" for testing.
If The test is normal, The result is: The timestamps on both pages match! Congratulations! you can skip all the steps below and celebrate them directly.
If The test is not normal, The following message is displayed: The pages do not match! Timestamps differ or were not found! . Continue.
2. Switch the topic you are currently using to the default topic of WordPress.
Note: This refers to the default theme that has not been modified. Some netizens modify the topic themselves, but some added code may be the cause of this problem.
3. Return to the settings of the WP Super Cache plug-in. First, click the "Delete Cache" button below to Delete the original Cache. Then, return to the plug-in settings homepage and click "Test Cache.
If the default theme test is normal, it is basically a problem with the previous theme. Continue to the topic used before the next check; otherwise, skip
4. You have confirmed that the topic is used before. Switch back to the previous topic and carefully check all the files of the topic. Special attention should be paid to files such as functions. php and header. php. Check whether the file contains a function with the compression function, or the PHP ob_start function is incorrectly used.
You can search by keyword such as zip or ob_start. After searching, you can first try to block (or delete, back up the code before deletion), and then re-test the cache function (remember to delete the original cache first ).
If the test is normal, congratulations. You can skip to the last step. Otherwise, proceed to the next step and check all the plug-ins.
5. Close all the plug-ins except WP Super Cache and re-enable them one by one for testing to see which plug-ins conflict with WP Super Cache plug-ins.
Plug-ins related to the compression function or plug-ins that contain the compression code are prone to problems. However, this blog (English) finds that the WordPress plug-in (plug-in versions 3.9.7 and 3.9.8) of the famous blog profitable website Text Link Ads conflicts with this plug-in.
6. After finding the plug-in, you can use other plug-ins with the same function, or modify the code of the plug-in (if you are familiar with WordPress plug-in development), or stop using the plug-in.
7. Return to the homepage of the WordPress Super Cache plug-in again and click Test Cache to Test whether the Cache function is normal (remind me again to delete the original Cache first ). If the problem persists, we recommend that you start from step 1 and re-check.
Things and pen talk about its solution in his blog; Xiao Jie encountered this problem but did not find a solution; some people encountered similar problems in the WordPress Chinese forum, however, there was no effective reply; another related problem encountered by the underwater rivers and lakes could be used as a reference; Z's blog encountered similar problems and solutions when using the D4 topic.

There is not much effective information in the English blog, mainly concentrated in the official WordPress Forum.

Finally, the problem with the netizen is that the webpage compression function is used in the functions. php file in the function template of the topic. If the corresponding code is blocked, the system returns to normal.