ahojdane
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation still not working in version 7.5.0.1@litetim I wrote an e-mail to the support right now, thank you very much!
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation still not working in version 7.5.0.1@litetim Yes, when I upgrade from 6.5 to 7 all the cache is cleared after upgrade automatically (unfortunatelly). When I’m downgrading, I clear all the cache manually.
I have enough credit for “Run UCSS Queue Manually”. If I push the button, then a white page with a black text appears with the number of pages in the queue (right now my daily quota is zero, so I can send a video). This page is automatically reloading. But, in my case, no UCSS are generated (only the pages from the queue are deleted, but the daily credit is not lowered by one (or more), no 5 minute interval between reloading). Once again, this problem is in my version 6.5.4, which I’m using (because of the problem above). But this problem is less problematic for me than the first one (wrong UCSS generation in version 7).
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation still not working in version 7.5.0.1No. The only difference in the WordPress configuration between the generated UCSS files is the version of the Litespeed Cache plugin.
I reported this error two times in the past, see:
https://ww.wp.xz.cn/support/topic/litespeed-cache-ucss-generation-still-not-working-in-version-7-2/
https://ww.wp.xz.cn/support/topic/ucss-generation-not-working-in-version-7-0-1/
I also noticed another error. Because after upgrade Purge all UCSS is made, as I reported, after I downgraded to 6.5.4 I tried to do “Force cron UCSS” to generate UCSS faster. But the cloud returned this message:Cloud Error: Please try after 4m 38s for service ucss.
Failed to communicate with QUIC.cloud server: Unknown error: fetch failed [server] https://node17.quic.cloud [service] ucssI have enough free “credits” in my daily quota. The pages in this case are deleted from the queue, even the UCSS generation failed. The UCSS generation made slower way (via cron?) works fine. This happens from time, when also highest version of Litespeed Cache plugin is available (since version 7). Maybe is this connected with the software version on the cloud server?
Thank you very much!
I really like this plugin and I want to use the newest version. But with this error I can’t.
Forum: Plugins
In reply to: [Image Regenerate & Select Crop] Collision with Litespeed Cache pluginThank you very much, Iulia!
I downgraded the Litespeed Cache plugin again (because of another error), but if I notice the error again (when I again upgrade) I will let you know. But I believe, you fixed it well 😊
Thank you very much once again for your superb plugin!
(And if you add watermarking maybe in one of next versions, I would be very happy! 😊)
Exactly the same like here:
https://ww.wp.xz.cn/support/topic/ucss-generation-not-working-in-version-7-0-1/Some crucial CSS is not included to UCSS (exactly the same). In v6.5.4 is everything fine.
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation not working in version 7.0.1@litetim Hello, fixed in v 7.1? Should I upgrade? Thank you
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation not working in version 7.0.1@litetim Thank you!
Because i really like the UCSS feature, I returned to 6.5.4 several days ago.
Litespeed cache is a great plugin, I hope, you will make the 7x version trouble-free soon. Thank you!
Forum: Plugins
In reply to: [LiteSpeed Cache] Purge All cache – Product publish/createI experienced the similar kind of error several months ago (I tried to solve it with @qtwrk – thank you very much once again!). In my case it was something with polylang plugin (we were unable to solve it, unfortunately).
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation not working in version 7.0.1Hello @litetim
- No, it is OFF. I turned it temporarily ON just because of your question.
– Yes, it already contained TOC. But there are more differences between the 6.5.4 and 7.0.0.1 UCSS versions (see images).
– No, this filter wasn’t used. - OK. From some reason aftery my update from 6.5.4 to 7.0.0.0 purge UCSS was done automatically (this was the reason why I noticed the bad UCSS generation on new pages).
- Yes. Version 7.0.0.1. No, it is not fixed. Right now there is this message:
Cloud server refused the current request due to rate limiting. Please try again later.
Cloud Error: Please try after 4m 58s for service ucss.
(I was NOT using the QUIC service for more than 5 hours (when I noticed, that the UCSS are still generated badly i turned it off and I turned it temporarily on just because of your question right now).
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation not working in version 7.0.1Here it is:
One example:
6.5.4:
https://ibb.co/qwdqg5C
7.0.0.1:
https://ibb.co/nNcmDwvC
Another one:
6.5.4:
https://ibb.co/gbrzSM1d
7.0.0.1:
https://ibb.co/tMtKBtPb
I don’t see any pattern in this. Some of the missing code is included in the main CSS file. Some is included in another WP plugin (Easy TOC).Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation not working in version 7.0.1Sure! But it will take some time. If I try to “Run UCSS Queue Manually”, it always ends with:
Cloud Error: Please try after 4m 3s for service ucss.So I will let to do that job to cron.
7.0.0.1
Forum: Plugins
In reply to: [LiteSpeed Cache] UCSS generation not working in version 7.0.1@litetim
Last Report Number:Â FNNXTUOL
Last Report Date:Â 03/27/2025 16:43:47Automatic update from WP admin to version 7 (previous version was 6.5.4).
I also tried to generate UCSS via QUIC from todays version 7.0.0.1, but same problem as in 7 (some CSS parts were missing). Then I temporarily downgrade to 6.5.4 (UCSS generation worked fine).
FYI: Last working version without this bug was x.69 (this bug appeared new in x.70 version).
Sure. Here it is:
See backend and frontend (tag settings):
https://ibb.co/tBVrtCH
https://ibb.co/khV3B71It possibly happens only when FIRST article in a TAG or CATEGORY is using also TOC menu. Then it is used the header_menu value from this first article.
See first article in this category:
https://ibb.co/2j15hYk
And menu in this article:
https://ibb.co/hdFj6m5
is used as a main menu in the whole category. - No, it is OFF. I turned it temporarily ON just because of your question.