LiteSpeed Technologies
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Conflict with remove query string functionsThe LiteSpeed Cache plugin does not apply any browser caching rules, so it might be an interference with another plugin.
Could you go to your wp-admin, under LiteSpeed Cache -> Environment Report, could you copy and paste it here? It’ll provide us with information that could prove useful to determining why there was a change.
Thanks,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Fixing: Dynamic “wp-content” folderLikely not exactly. WordPress suggests that WP_CONTENT_DIR should not be used by plugins, and we will honor that the best we can.
As you can see in the class-litespeed-cache.php constructor, we got the content dir via get_theme_root() (and dirnaming that). We will likely just re-use this. Since the rule in question relates to themes anyway, this should be a fitting solution.
Let me know what you think! We’re always open to recommendations.
Cheers,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Conflict with remove query string functionsHi @kaiderella
Could you rephrase your question? I don’t quite understand what the issue is.
One thing to note, our plugin does not cache static files (.js, .css) anyway.
Thanks,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Fixing: Dynamic “wp-content” folderThanks for letting us know! This will be resolved for the next release.
Forum: Plugins
In reply to: [LiteSpeed Cache] What is cached and what notTo add on to what @hailite said, if
/destinations/should not be cached, you can add it to the URI list. The plugin code may not recognize the query string portion of the request, so if you are ok with it,/destinations/will not be cached for anyone.Rewrite Rules will probably work better if you prefer requests without arguments to be cached. If you do go this route, remember to add it outside the plugin comment block, else it will be overwritten.
Forum: Plugins
In reply to: [LiteSpeed Cache] What is cached and what notHi @massimod
We will look into adding a new option for query strings.
A temporary fix, you can use rewrite rules conditional on the query string to set no-cache and it will ignore the cache entry.
Another idea is if you are handy at PHP, you can also make a simple PHP script to do this yourself via our third party api.
Let us know what you think!
Cheers,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Purge All on upgradeHi @massimod
We just tested this internally and it worked for us.
Do you remember what plugin you were upgrading? How did you upgrade the plugin?
It is hooked to the
upgrader_process_completeaction, so if you have a way to verify that this action was called, we’ll need to investigate further.Thanks,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Status / Debug informationHi @massimod,
We’ll look into this. We removed some commits because we wanted to get another bug fix release out and may have removed the commit containing this change accidentally.
If we did, we’ll update the repo and reply here.
Cheers,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Known Supported PluginsHi @remo94
Thank you for trying our plugin out!
With regards to the plugins you listed:
1. Cache Enabler – This will directly conflict with our plugin. Normally, we will say that you can use other cache plugins for other features, such as minification, but that isn’t something that Cache Enabler provides.
2. Adaptive Images and Gallery Manager should both be fine. If you notice anything conflicting, just let us know, we’ll gladly look into it!
3. BBQ – I’m not sure how it works, but if it is implementing a firewall within PHP, the cached pages will not trigger BBQ. Otherwise, this should be fine as well.Let us know how it goes! If you run into any problems, just let us know and we’ll try to resolve it as fast as we can.
Cheers,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Shared Hosting QuestionsHi @massimod,
Our cache plugin will not trigger PHP. It is very similar to html page caches, except the benefit of LiteSpeed Cache is the server is aware of how the cached pages are stored.
If you want the fine details, I can explain further in this paragraph. Else you can skip it. The server stores the cache pages as static files and keeps a hash table with extra information about each stored page. The extra information allows us to purge pages more effectively as well as allows us to further improve the cache if needed.
Let me know if you have any more questions about this!
Kevin
Forum: Plugins
In reply to: [LiteSpeed Cache] Automatic cache primingYes! that’s the plan. We may release a bugfix version like 1.0.15.1, but priming is a big feature and that won’t be until 1.0.16.
Forum: Plugins
In reply to: [LiteSpeed Cache] Automatic cache primingHi @hlsg
No, unfortunately not. We were looking to add it for this release, but it required quite a bit of code overhaul, so we decided to release a version fixing various issues that some people encountered.
The primer code is implemented already, we just need to go through the plugin code to make sure that everything is as optimized as possible.
Sorry for any inconvenience that this may have caused.
Cheers,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Message Since UpdatingSure thing! Let us know if you run into any more issues!
Forum: Plugins
In reply to: [LiteSpeed Cache] Message Since UpdatingHi @shellyo
I believe the culprit is the “Cache Enabler” plugin. Please try deactivating that plugin.
I noticed that their description discusses WebP images a lot, so if you were looking for that benefit, try their Optimus plugin. Optimus should work OK with LiteSpeed Cache.
Let me know how it goes,
KevinForum: Plugins
In reply to: [LiteSpeed Cache] Message Since UpdatingHi @shellyo
You have to access the file directly through your host.
If that’s not a viable option, in the wp-admin, could you go to LiteSpeed Cache->Environment Report? This should be available unless you only have subsite access in a multisite install.
Once there, scroll down the text area until you get to “WordPress Specific Extras”. Could you paste the contents here? It’ll tell us the current active plugins.
Thanks,
Kevin