kkinfy
Forum Replies Created
-
Thanks a lot
Hi,
I understand that. However, I want to prevent any accidental delete (like aclicking the delete all button on the admin toolbar by mistake) and those invoked by other modules like FVM.
The reason is my site has now over 200,000 pages preloaded. Hence an accidental “delete all” will be devastating.
Kindly help me with the code (line of code/function) responsible for the delete so that I can comment that.
Whenever a need for cache clear arises I am more than happy to do it directly on the filesystem on the server.
Regards,
KKForum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Use of RewriteCond %{HTTPS} !=onThanks, I got the response email. Your support is great as always. Keep up the good work.
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Use of RewriteCond %{HTTPS} !=onHi,
I have shared my URL in email to fastestcache@gmail.com . Kindly have a look and let me know if the functioning is fine. Please note I have commented out the line RewriteCond %{HTTPS} !=on
- This reply was modified 7 years, 7 months ago by kkinfy.
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Use of RewriteCond %{HTTPS} !=onSorry there was a typo in my previous reply. TTFB decreased (improved) as a result of commenting out RewriteCond %{HTTPS} !=on line.
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Use of RewriteCond %{HTTPS} !=onHi, my question is not about the functioning of the cache after https redirection. The cache is working fine. What I fail to understand is how cache works properly for https pages even with the line RewriteCond %{HTTPS} !=on on mod rewrite.
My guess (please see my second reply in this thread) is PHP handles HTTPS pages while Mod_Rewrite handles non-HTTP pages.
Why not force Mod_Rewrite to handle both by removing the RewriteCond %{HTTPS} !=on line. You can take this as a suggestion for the next update. Because doing so has increased the TTFB (First Byte Time) for my site significantly.
- This reply was modified 7 years, 7 months ago by kkinfy.
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Use of RewriteCond %{HTTPS} !=onI have analyzed further on my doubt. Please check if my understanding is correct.
1. WP Fastest Cache uses MOD REWRITE to serve only HTTP pages from cache.
2. For HTTPS pages, the processing is at PHP level and not at MOD REWRITE Level.For curiosity sake I commented out the RewriteCond %{HTTPS} !=on on my htaccess and checked the Time To First Byte or TTFB. TTFB improved by almost 100%. (From about 1200 ms to 700 ms) .
Hence on my websites using WP Fastest Cache I am planning to comment out RewriteCond %{HTTPS} !=on.
Still I don’t understand the need for HTTPS pages to be bypassed at MOD REWRITE and be handled at PHP level. In future, it could be better if you remove RewriteCond %{HTTPS} !=on from htaccess provided there are no adverse effects.
Hi,
As another option, can I try this:
Is there someplace in code where I can bypass caching by wp fastest cache and serve dynamic content.
For example, is the below algo possible?
If Geo Detect Country Belongs To EU
Do Not Serve Cached ContentHi, I am using “Cookie Consent” (by Catapult_Themes) plugin.
But I am ok to switch to any plugin that is compatible with wp fastest cache. Kindly guide me. My website gets most of the traffic from the US and around 20% from Europe. Hence, I want to display the cookie consent message only to EU users and not to other visitors.
Hi, I think I haven’t explained my query well enough.
Suppose I have a page example.com/abcd . WP Fastest Cache will in turn create a folder /public_html/wp-content/cache/all/abcd to store the static html file.
In case, I delete /public_html/wp-content/cache/all/abcd using some FTP manager or through unix commands directly, my understanding is that fastest cache plugin will create a new folder when someone visits the page in browser. Will the direct deletion break the site in any way?