ekaterir
Forum Replies Created
-
Forum: Plugins
In reply to: [Cache Sniper for Nginx] HTTP ERROR 500 while Deleting MediaHi @yosbeda,
Thank you for catching and reporting that. It should be fixed now. Let me know if it worked for you.
ekaterir
Forum: Plugins
In reply to: [Cache Sniper for Nginx] Engintron flushing?Hi @openedge1,
We haven’t tested with Engintron (actually, we haven’t even heard of it, but it looks really cool). If you’d like to test and let us know, that’d great.
Thank you,
ekaterirForum: Plugins
In reply to: [Cache Sniper for Nginx] PHP Error after UpdateHello @myar,
Thank you for the feedback. I just pushed a fix. Let me know if it worked and I’ll resolve this support issue.
Thanks again,
ekaterirForum: Plugins
In reply to: [Cache Sniper for Nginx] How to trigger clear post cache on commentHello @myar,
You can call a function called
csnx_delete_current_page_cache_on_comments( $comment )
it’s located in
snipe-nginx-cache/includes/cache-sniper-nginx-comments.php
$comment
can be an object or an id, the function will figure that out.
So it can look something like this:require_once plugin_dir_path( __FILE__ ) . '../snipe-nginx-cache/includes/cache-sniper-nginx-comments.php'; // get your comment object or id $commentSniper = new Cache_Sniper_Nginx_Comments(); $commentSniper->csnx_delete_current_page_cache_on_comments( $comment );
However, this will introduce a dependency in your plugin.
I think there is a hook I can use to trigger cache clear on wp_insert_comment.You can try the approach described above for now and I will let you know when we implement the wp_insert_comment action hook.
Thank you for raising the issue.
Forum: Plugins
In reply to: [Cache Sniper for Nginx] Clear index page cache on publish postHello @myar,
Thanks for using Cache Sniper and bringing up this issue. We are going to work on this feature next and let you know when it’s available.
Forum: Plugins
In reply to: [Cache Sniper for Nginx] Custom DevelopmentHey, We’d be glad to help. Contact us at [email protected].
Thank you for the feedback! I just pushed a version that addressed the issue you brought up. I hope other aspects of this plugin are working as expected.