wpmansour

Hi,

Thank you for reaching out with your query about adding a filter to trigger a cache purge for a specific page when there’s a site update on WP Optimize.

Based on your requirements, you can indeed use the WPO_Page_Cache::delete_single_post_cache($post_id); function to purge the cache for a specific page. This method allows you to target the cache of a single page or post efficiently.

Here’s how you can implement this:

function custom_purge_specific_page_cache($post_id) {
 // if ($post_id == 'your_specific_page_id') {
        WPO_Page_Cache::delete_single_post_cache($post_id);
 // }
}
add_action('save_post', 'custom_purge_specific_page_cache');

This function hooks into WordPress’s save_post action, which is triggered whenever a post or page is saved. If you want this to only apply to a specific page, replace 'your_specific_page_id' with the ID of the page you’re targeting and uncomment the if statement.

Add this code to your theme’s functions.php file or a site-specific plugin to ensure it executes correctly.

If you have any further questions or need additional assistance with this setup, please feel free to let me know. I’m here to help!

Best regards,
Mansour M

• This reply was modified 7 months, 1 week ago by wpmansour. Reason: clear display of code

Thank you very much for your suggestion! I’ve already discussed it with the team. Your input is greatly appreciated and helps us continue to improve our service. : )

Hi,

I apologize for any inconvenience, but please note that I can only provide support in English.

It seems you’re encountering the “cURL error 28: Connection timed out” while trying to compress images. This error indicates a problem with your server’s connection setup. Here are some steps you can take to address this:

1. Disable Your Firewall: Security measures on your site might be preventing external connections necessary for operations like image compression. Temporarily disabling any firewalls could help identify if they are causing these timeouts.
2. Increase Server Resource Limits: Limited server resources can also lead to this error. Increasing the PHP memory limit or execution time could provide a solution. These adjustments can often be made through your hosting control panel or by modifying the php.ini file on your server.
3. Contact Your Hosting Provider: If these adjustments don’t resolve the problem, the issue might lie deeper within the server’s configuration or with the hosting environment itself. Contacting your hosting provider can help as they can perform more detailed checks and possibly resolve server-specific issues that could be causing the timeouts.

For additional guidance, you might find this blog post helpful: “How To Fix the ‘cURL Error 28: Connection Timed Out”. It provides a detailed overview and more solutions for dealing with this error.

Best regards,
Mansour M

Hi,

Thank you for reaching out and providing your feedback regarding the caching features of our WP-Optimize plugin. We truly value the insights our users share and are always looking for ways to enhance our plugin’s capabilities.

We understand your concerns about the cache lifespan and the lack of an automatic cache clearing feature upon publishing content. Many of our users have expressed a desire for more granular control over cache settings, and we take these suggestions seriously as we plan our development roadmap.

While we are actively working on including more flexible cache management options in future updates of WP-Optimize, if you’re interested, we can provide a custom code snippet that enables immediate cache clearing whenever new content is published. This can serve as an interim solution until we release an update with built-in functionality.

Thank you once again for your feedback, which is instrumental in helping us improve and better serve our user community.

Best regards,
Mansour M

Hi Chris,

It sounds frustrating to see the database size increase unexpectedly after cleaning up user records and optimizing it. Here’s what might be happening:

1. Index Rebuilding: When you optimize a database, especially using tools like WP-Optimize, it often involves rebuilding indexes. This process can sometimes increase the size of the database temporarily because it rebuilds the index structures in a more optimized manner but uses additional space to do so.
2. Database Overhead: After deleting records, the database might still hold onto some “overhead,” which is space reserved for future data. While you’ve deleted records, the space those records occupied may not be immediately released back to the operating system, depending on how your database manages its storage and optimization settings.
3. Fragmentation: If your database was heavily fragmented before the optimization, the process might rearrange how data is stored, which can paradoxically increase the total size due to how data is aligned in the storage.
4. Log Files and Backup Copies: Sometimes, optimization processes increase log file sizes or create backup copies of data during the process, which contributes to an overall increase in size.

It’s also possible that the settings used during the optimization process weren’t entirely suited for reducing the database size but rather aimed at improving performance or stability. Reviewing the specific settings or consulting documentation on the optimization process you followed might provide more insights.

If the size remains a concern, it may be beneficial to look into the specific types of data that are taking up the most space now compared to before, and whether any temporary or redundant data can be cleaned up further.

Hope that helps clarify why you might be seeing this result!

Best Regards,
Mansour M