mrmad
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Yet another Image optimization problem…Thanks a lot for the detailed reply.
– I disabled vault press (which I have been using together with LSCache plugin without ever getting any problems)
– disabled firewall (which I had set up to whitelist Litespeed Cache IPs and has never interfered). There is actually nothing to edit/alter in vault press settings, so I don’t really know what to do here.However, the situation has not changed and still only 1% of the images have been optimized.
I hope things get fixed in V3…
Forum: Plugins
In reply to: [LiteSpeed Cache] Yet another Image optimization problem…So you are basically saying I should wait and have my fingers crossed you might release within time schedule and that might solve issues?
Even though I understand you re totally busy with V3, as a paying customer this is not the service I was expecting…
So what should I do in the meantime as you advise against using other image optimization plugins?Forum: Plugins
In reply to: [LiteSpeed Cache] Installed Plug-in But TTFB Still “F”Thanks for the fast reply!
Forum: Plugins
In reply to: [LiteSpeed Cache] Installed Plug-in But TTFB Still “F”Sorry to hijack this thread but there is something I need to fully get my head around.
If I follow your wiki for Plesk extension, I should manually add<IfModule LiteSpeed>
CacheLookup public on
</IfModule>And this is what the wordpress plugin extension adds:
<IfModule LiteSpeed>
RewriteEngine on
#CacheLookup on
RewriteRule .* – [E=Cache-Control:no-autoflush]
RewriteRule ^min/\w+\.(css|js) – [E=cache-control:no-vary]Do I need both Cache (public) lookup entries?
Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageHi,
with latest plugin update as of today I can confirm it is working again as expected.
Thanks a lot for pointing me into the right direction!Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageHi,
there was a setting in Plesk server that enabled browser by default. I eliminated it but however I believe the problem with not updating correctly persists.
Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageI don’t really know where this is coming from. I don’t have any optimization plugins other than ls cache plugin. I am using Plesk with ls cache add-on.
When I disable LSCache plugin, I still see :
cache-control: public, max-age=86400Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageCan you tell me how to? I am using default settings. Is it because of the favicon? Can you check my .htaccess?
`# BEGIN LSCACHE
## LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block! ##
<IfModule LiteSpeed>
RewriteEngine on
CacheLookup on
RewriteRule .* – [E=Cache-Control:no-autoflush]
RewriteRule ^min/\w+\.(css|js) – [E=cache-control:no-vary]### marker CACHE RESOURCE start ###
RewriteRule wp-content/.*/[^/]*(responsive|css|js|dynamic|loader|fonts)\.php – [E=cache-control:max-age=3600]
### marker CACHE RESOURCE end ###### marker FAVICON start ###
RewriteRule favicon\.ico$ – [E=cache-control:max-age=86400]
### marker FAVICON end ###### marker WEBP start ###
RewriteCond %{HTTP_ACCEPT} “image/webp” [or]
RewriteCond %{HTTP_USER_AGENT} “Page Speed”
RewriteRule .* – [E=Cache-Control:vary=%{ENV:LSCACHE_VARY_VALUE}+webp]
### marker WEBP end ###</IfModule>
## LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block! ##
# END LSCACHE
# BEGIN NON_LSCACHE
## LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block! ##
### marker MINIFY start ###
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{DOCUMENT_ROOT}%{REQUEST_URI} ^(.*)/min/(\w+)\.(css|js)$
RewriteCond %1/wp-content/cache/$2/$1.$2 -f
RewriteRule min/(\w+)\.(css|js) wp-content/cache/$2/$1.$2 [L]
</IfModule>
### marker MINIFY end ##### LITESPEED WP CACHE PLUGIN – Do not edit the contents of this block! ##
# END NON_LSCACHE
# SetEnv MAGICK_THREAD_LIMIT 1
RewriteRule .* – [E=Cache-Vary:euCookie]
CacheKeyModify -qs:utm_medium
<IfModule Litespeed>
RewriteEngine On
RewriteRule (wp-cron)\.php – [E=noconntimeout:1]
</IfModule>
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule># END WordPress
Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageAn update would be nice…
Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageHere is the log: https://gist.github.com/mrmad/3a729867ddc2a50eb1dce5acb98c95c4
Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageWhen I published the article now I saw: cache miss, cache control: private.
I am unable to download the log file at the moment- I will include it as soon as possible.Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageIt was a hit…
Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageHi,
well that is exactly the problem. Only when I hard refresh the page, I will see the new content. My newly published posts appears if I hard-refresh.
Let’s say I worked in firefox browser and publish the post, logout of WordPress, I will see the new post.
If I now check e.g. in Safari, the new post will NOT appear unless I hard refresh the homepage.
When I use another cache plugin (e.g. wp rocket) returning users used to see the newly published post without hard-refreshing. It seems like Litespeed cache will always serve the homepage from last user’s browser cache unless explicitly refreshing the webpage. How are users supposed to see the new content?- This reply was modified 7 years, 3 months ago by mrmad.
Forum: Plugins
In reply to: [LiteSpeed Cache] Autopurge homepageWhat I mean is that a returning visitor will never see the new articles on the front-page. It will always show the same page with the old articles and not the new ones that have been published since the first visit.
Forum: Plugins
In reply to: [LiteSpeed Cache] Lazy loading images – bug found and resolutionPlease delete my last comment. It looks like the theme was adding its own lazy loading mechaninism. Sticking to one helped of course. My apologies.