Ray
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!A homepage or post is a static resource, especially if I say so. AGAIN, you guys have decided that EVERYTHING is dynamic and therefore you have lost the plot. !!!!!!!!!!!!!!
Once again, users of your plugin have static pages THAT ARE NOT DELIVERING the expires headers they THINK they have selected in your plugin!!!!!!!
Again, I ask the question, what is the point of the Browser Caching tab in the plugin? It COMPLETELY IGNORES user selections!!!!!!!!!
- This reply was modified 2 years, 10 months ago by Ray.
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!AGAIN – What is the point of the Browser Caching section of the plugin? IT DOES NOTHING, as it considers ALL content to be DYNAMIC.
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!Yes I read that reply. But fixed pages should have an efficient expires policy. Every best practice document concurs. Starting from Google and down.
AGAIN – the plugin has decided that fixed pages are not fixed, but are dynamic.
Who the heck gave you guys permission to override my decision on what is fixed and what is dynamic?????
That’s why you have lost the plot. Not in a small way. But in a massive way.
The decision on what is fixed content and what is dynamic content is MINE not YOURS !!!!!!!!!!!!
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!Let’s turn the question around. What is the point of the browser cache section of the plugin when *IT APPLIES THE RULES SET TO PRECISELY NOTHING*
???????????????????
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!There is no point to the browser caching section of your plugin and you are misleading EVERY user of your plugin. Millions of homepages, posts and the like are being delivered with ZERO expires policy. Despite users thinking otherwise.
This used to be a great plugin. But this issue is so massive and I find it beyond comprehension that you guys think otherwise!
OMG and wow!!!!!!
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!I have misunderstood nothing. Fixed content should be cached, for a minimum of one month and preferably one year.
Dynamic content should not be cached.
We are all clear on that.
The problem is that the plugin has decided that *ALL* content is dynamic, not fixed. Therefore it *NEVER* delivers the cache expiry policy selected by the user in the plugin under any circumstances !!!!!!!!
Therefore, the browser cache section of the plugin is useless, as it does not honour user selects!
- This reply was modified 2 years, 10 months ago by Ray.
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!Let’s follow the logic. So the browser cache settings on the plugin are pointless and should not be there in the first place. Why? because the plugin only applies them to static resources. But the plugin has decided that things like homepages etc are dynamic.
What a load of nonsense!!!!!!!!!!
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!The problem is that the plugin has now decided that *EVERY* page is dynamic. So it now *NEVER* delivers the correct expires headers.
When did your users give you permission for *YOU GUYS* to decide that every post on WordPress is now *DYNAMIC* ???????????????????
- This reply was modified 2 years, 10 months ago by Ray.
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!Pages, taxonomies and posts *ARE STATIC RESOURCES* unless we tell the plugin otherwise!
Like I said, the plugin now considers *EVERY PAGE TO BE DYNAMIC*
Thus, the browser cache part of the plugin is now BEYOND USELESS
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!In other words, you guys have decided that every fixed page, post or taxonomy is, in your opinion, now a “dynamic resource” and WILL NOT HAVE A CACHE EXPIRES HEADER.
How the heck did you guys suddenly decide that *EVERY* page for *EVERY USER* is now a dynamic resource?
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!Yep, static resources might be, but in my case, every post, page and taxonomy on my entire website •*S A STATIC RESOURCE*. But you guys have have decided otherwise.
So, once again, you have rendered the browser caching section of your plugin *UNUSABLE* as you now *COMPLETELY IGNORE USER CHOICES*
This means that for every user of your plugin there is now *NO EXPIRES INFORMATION EVER*
- This reply was modified 2 years, 10 months ago by Ray.
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!This used to work fine. Google themselves state that you should deliver an expires policy of a minimum of one month and preferably one year:
https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/
This used to work fine. Basically you are confirming that Google is wrong and you guys are right.
So, every user of your plugin is now being mugged. We all *think* the plugin is honouring our browser cache settings in the plugin.
But you’ve decided to *completely ignore this*
Therefore, the browser cache settings in the plugin are now *USELESS* as you ignore them.
You have lost the plot……
Forum: Plugins
In reply to: [LiteSpeed Cache] Warning All Users – Browser Cache No Longer Works!A temporary workaround is to add this to your .htaccess file:
<IfModule mod_expires.c> FileETag MTime Size AddOutputFilterByType DEFLATE text/plain text/html text/xml text/css application/xml application/xhtml+xml application/rss+xml application/javascript application/x-javascript ExpiresActive On ExpiresByType text/html "access 1 year" </IfModule>- This reply was modified 2 years, 10 months ago by Ray.
Thank you, I’ve now created a new issue over at GitHub as requested.
Hi @priscillamc
Thanks for your prompt reply on this ticket. I will create an account over at GitHub and create a new issue as you suggest.
Many thanks