After upgrading to 7.3+ CSS Combine don’t work, loading a dummy CSS instead

  • Resolved Pyetro

    (@subfighter3)


    9 months ago

    Helllo there, I am experiencing sth similar: from 7.3 on, the CSS Combine function prevent the loading in head of the combined CSS, instead I only see loading the “litespeed-dummy.css” file even if in the FTP /wp-content/litespeed/css I can see a proper (1) combined css file.

    I tried to enable/disable/reset all the settings, and I was able to isolate the problem which is caused by the CSS Combine function.

    Then I tried to exclude all the CSS file in my theme one-by-one, still the combined file is never loaded in HEAD in favor of the dummy one.

    I will send the report from my staging environment where I kept LSC 7.3.0.1 for testing, while I rolled back to 7.2 on production for continuity.

    thanks in advance!

    ps: I can’t send the report from the Toolbox, I get this error: Failed to request via WordPress: [server] https://api.quic.cloud [service] wp/report . Where or how should I send you the report and my notes about it otherwise?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support litetim

    (@litetim)

    9 months ago

    @subfighter3
    please test Master code version from: https://docs.litespeedtech.com/lscache/lscwp/toolbox/#beta-test-tab Version will be 7.3.0.1-rc1

    For request error ensure that LSC servers IPS are not blocked.

    Thread Starter Pyetro

    (@subfighter3)

    9 months ago

    Hello there, thanks for you reply.

    I tried to use the Master commit from the Beta Test tab, but it looks like the plugin version is the same 7.3.0.1 and the CSS Combine issue persist, not sure if it changing LSC version worked.

    Regarding the LSC servers IPs, nobody blocked them, unless there is a section in LSC itself from where to block. I also tried disabling Sucuri Security plugin, but I’m still unable to send the report.

    Can I send the report somewhere else?

    EDIT: I don’t think any LSC IPs is blocked, I was able to send a report from the Production environment (with LSC 7.2) hosted on the same server, report ID: BFKFILLO. Also, I am able to switch versions from Beta Test tab, but master version now is just 7.3.0.1 which correspond to the latest stable available version

    • This reply was modified 9 months ago by Pyetro.
    • This reply was modified 9 months ago by Pyetro.
    Plugin Support Hai Zheng⚡

    (@hailite)

    9 months ago

    Sorry for the inaccurate answer. V7.3.0.1 was released already so there is no need to try master.

    You can send the info to [email protected]

    Thread Starter Pyetro

    (@subfighter3)

    9 months ago

    ok thanks! I just sent an email with all the same info as they appear in the Report tab of the plugin’s Toolbox:

    • System Information
    • Passwordless Link
    • Notes
    • Phpinfo link

    Thanks

    Plugin Support litetim

    (@litetim)

    9 months ago

    @hailite you are right 🙂
    @subfighter3 is the dummy css error fixed? this issue was addressed in 7.3.0.1

    Thread Starter Pyetro

    (@subfighter3)

    9 months ago

    @litetim nope, when I opened the thread I was already testing it in the latest 7.3.0.1. I had to rollback to 7.2 to prevent the dummy css to load and the CSS Combine mess (not being loaded).

    Plugin Support litetim

    (@litetim)

    9 months ago

    @subfighter3 Closing the topic because a ticket was created

    Dennys Dionigi

    (@dennysdionigi)

    6 months, 2 weeks ago

    Hi there,

    coming from: https://ww.wp.xz.cn/support/topic/remove-dummy-css/page/2/#post-18683232

    Either me, I ‘m seeing that useless empty dummy stylesheet “#litespeed-cache-dummy-css”; even if I am using latest 7.6.1 and the beta channel.


    So which is the fix from your side?

    I mean: I can quickly easily handle it using some patch code, but… why do I need to fix something that shouldn’t even be there? 🙂

    Cheers

    Plugin Support litetim

    (@litetim)

    6 months, 2 weeks ago

    @dennysdionigi please stop spamming other topics and create your own topic. we will gladly help you

    Dennys Dionigi

    (@dennysdionigi)

    6 months, 2 weeks ago

    Hi,

    I will be pleased to open new thread, and… sorry if this appear as spamming to your eyes.

    But.. I just feel to reply back: why opening a new thread if the issue is technically and basically the same?

    And neither this topic, neither the second one I’ve seen, have a definite reply and a clear solution.

    So which will be the point to open N* threads to get a simple solution and reply?

    Sorry if this appear as “spamming”, or even “flaming”, but while searching for something in the forum, the steps I’m expecting are: “wow, I found the same issue, great, maybe there’s a solution from the original developer”.

    In the unfortunate event that there are no clear solutions, it seems quite obvious to me to reopen the current topic, since it is the exact same problem, expecting a kind reply.

    One would expect a polite response, not to be scolded for not opening another post (identical to the previous ones, by the way!).

    What would be the utility point of opening yet another thread, other than to further complicate future searches for future users?

    Plugin Support litetim

    (@litetim)

    6 months, 2 weeks ago

    @dennysdionigi
    1) forum guidelines: https://ww.wp.xz.cn/support/guidelines/#we-reserve-the-right-to-manage-the-forums-to-the-best-of-our-ability
    2) if you read 2 topics resolved and your issue is still there, then your problem is not the same
    3) you help us manage the topics and figure out your problem.

    Thank you

    Dennys Dionigi

    (@dennysdionigi)

    6 months, 2 weeks ago

    Hi,

    in this post the issue is not resolved and the user opened a ticket, so I dont know what happened into that ticket.

    “Closing the topic because the users opened a ticket” : doesn’t mean this has been fixed, and it’s hot helpful to other users.

    2) In the post I linked here too, in my initial comment… how to say: no one, literally, has solved this issue, and your global reply is “open a separate thread” and send a report ID.

    But searching for the keys “dummy CSS”, “dummy”, “unwanted CSS” et similar, I found that this issue has a long story, and in old topics you suggested both:

    1) restore previous versioning, flush the cache and turn back to last updated one (we are talking about version 7.3 / 7.4) – so it’s an old temporary “trick”.. if we can call it a trick – and sadly this didnt work too, reading those posts latest reply.

    2) on some topics you said too: “switch to dev/beta channel” of the plugin, and then again: “send the report ID”. That’s all I could see.

    So, from what I could read:

    None of this solution worked, if after a long time, I here reporting the same problem and asking for the reason of a missing clear fix from you.

    Example:

    Francisco Sanchez Llorente 

    (@kurros)

    2 months ago

    I have this resource on my website: neurinomavestibular.es
    https://neurinomavestibular.es/wp-content/plugins/litespeed-cache/assets/css/litespeed-dummy.css
    Is blocking the render and I don’t know how to remove it

    Your reply: “Update to 7.3.0.1” .


    What I mean:

    If the issue is the same, and I am on the latest 7.6.1 – even also “playing” switching between “dev/master/latest” as the tricks said above, means that it has not been solved yet, and that’s useless opening a new thread, I don’t understand the purpose, if the issue in something more general and happened to more users.

    I can understand something that happens a single time, to a single user, who needs a fix for his own onetime issue, but this is not the situation.

    BTW…

    My REPORT ID: IAQUXATD and I also openend, as per request, this topic: https://ww.wp.xz.cn/support/topic/dummy-unused-css/

    And if a builtin solution will be provided, I hope it will help future users.
    Meanwhile for my situation: I solved using the HTML Processor API and removed the unwanted resources.

Viewing 12 replies - 1 through 12 (of 12 total)

The topic ‘After upgrading to 7.3+ CSS Combine don’t work, loading a dummy CSS instead’ is closed to new replies.