usabe
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Litespeed + Facebook Pixel problemHi to all involved in this topic,
Due to inactivity of this topic, I will mark this topic as “resolved”. If you still have such issues (it looks so), please feel free to open a ticket with further information by emailing to support@litespeedtech.com and ask to assign your ticket to Abe. I will check into this further from there.
Forum: Plugins
In reply to: [LiteSpeed Cache] Cache is not clearing when a post is publishedHi to all involved in this topic,
Due to inactivity of this topic, I will mark this topic as “resolved”. If you still have such issues (it looks so), please feel free to open a ticket with further information by emailing to support@litespeedtech.com and ask to assign your ticket to Abe. We will check into this further from there.
Forum: Plugins
In reply to: [LiteSpeed Cache] LS Cache Guest Mode + Elementor Cart Icon not updatingHi to all involved in this topic,
Due to inactivity of this topic, I will mark this topic as “resolved”. If you still have such issues (it looks so), please feel free to open a ticket with further information by emailing to support@litespeedtech.com. We will check into this further from there.
Btw, please ask to assign your ticket to Abe in your ticket if you do so.
- This reply was modified 3 years, 3 months ago by usabe.
Hi @naomiyaki
Due to inactivity of this topic and many updates on lscwp in the past 5 months, I will mark this topic as “resolved”. If you still have such issues, please feel free to open a new ticket and reference this one.
Forum: Plugins
In reply to: [LiteSpeed Cache] problem with litepeedHi @hatembadran
Due to inactivity of this topic and many updates on lscwp in the past 5 months, I will mark this topic as “resolved”. If you still have such issues, please feel free to open a new ticket and reference this one.
Forum: Plugins
In reply to: [LiteSpeed Cache] Crawler no longer works on 5.0.1Hi, @szmigieldesign
Due to inactivity in the past 5 months I will mark this topic as “resolved”. If you still have the issue please consider opening a new ticket referencing this topic. I will check into that.
Forum: Plugins
In reply to: [LiteSpeed Cache] Issues after WordPress 5.9 updateHi, @samkitpalecha,
Is your issue still existing? Indeed there has been many updates in the past four months.
I am checking through all those “unresolved” topics. Due to inactivity I will mark this topic as “resolved”. But welcome to open a new ticket with your updates on this. If needed then we’ll check into that.
Forum: Plugins
In reply to: [LiteSpeed Cache] Empty CSS file on random pagesHi @robb3rt
From what you described, it seems to be the situation that the crawler was trying to access the page to fetch html page source for ucss generation. But for some reason (like your server configuration) it didn’t get the real page but an error page (e.g., 404 error page) and then send it for ucss generation. This generates an empty result for ucss and causes the missing style problem.
So please try to curl the page from the server locally (localhost) to see what’s the result and what’s the problem.
Best regards,
AbeForum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation takes more than 90 secondsHi @mmwbadmin
Thanks for the reporting. Yes, we found node9 had such issue recently. Now should be resolved.
If you still meet any issue with it please do not hesitate to let us know.
Best regards,
AbeForum: Plugins
In reply to: [LiteSpeed Cache] css file is 404Hello @chaoskitten
Thanks for the reporting. LSCWP used to have some css 404 errors reported after v4.0, but those have been fixed in the later versions. For the latest versions, the reported css 404 we investigated into showed those were caused by unexpected file deletions from the server level or some mechanism outside of LSCWP.
So please confirm with your hosting company to make sure those combined css files in the dir /wp-content/litespeed/css are not deleted by the server.
If you verified that and it still has problem, please open a ticket here and we need further investigation: https://store.litespeedtech.com/store/submitticket.php
Forum: Plugins
In reply to: [LiteSpeed Cache] First time visit webSites Loads Unstyled MannerHi @rcverma
You can add your IP to the Guest Mode IPs to troubleshoot this issue, to see if it is caused by ccss or ucss. Please refer to this: https://docs.litespeedtech.com/lscache/lscwp/general/#guest-mode-ips
Forum: Plugins
In reply to: [LiteSpeed Cache] Error in redirect when a relevanssi search is performedHi, Alex,
If that’s the way please open a ticket here and we can further investigate: https://store.litespeedtech.com/store/submitticket.php
Best regards,
AbeForum: Plugins
In reply to: [LiteSpeed Cache] Duplicate entry with query INSERT INTO `wp_litespeed_url`Normally this means that you need to clean up (drop) some indexing table for the table wp_litespeed_url. Please give it a try and see if it works.
Forum: Plugins
In reply to: [LiteSpeed Cache] Load JS Deferred (Delayed) and broken scripts like CF7Hi @pepe80
Thank you for the referring info.
Since lscwp and nitropack had different focus and strategies, and lscwp has already provided the exclusion mechanism as solution for such issue, I don’t think we will put this in a higher priority in short term. But we’ll keep it in mind and check into this to see what we may do better in future.
Best regards,
AbeForum: Plugins
In reply to: [LiteSpeed Cache] Error in redirect when a relevanssi search is performedHi, Alex,
Thanks for reaching out. I just checked the site and confirmed the issue.
It looks like the root cause of this problem is coming from the search engine logic. For this specific string the redirect process generates WP_ERROR as $location which is passed to the line 499 and caused the error.
I suggest you to check the search engine related site settings, to see why it gives such WP_ERROR. From your pages, the string “DIPTYQUE” is the first word of the names of your first products(or you may know more about the special part of that string). You may change it to some other strings and then test to see if the problematic string changes correspondingly. This could verify the root cause of the issue.
Since this is a very corner case, if you still could not figure it out on your own, you can create a ticket with us and we may give you a hand with further access.
Best regards,
Abe