Plugin Version 7.2 Errors

  • Resolved jstubbs034

    (@jstubbs034)


    11 months ago

    After updating the LSCache plugin to version 7.2 every time I open a page in Elementor when I exit I am seeing this error at the top of the screen “setting Disable All Features is currently enabled. Click here to change” and when I check the debug settings everything is disabled so this is a false positive trigger.

    Version 7.2 also is disconnectinng the site from QUIC.cloud, spitting out REST API errors at random, saying that it cannot communicate to QUIC.cloud when trying to access tools to revert the plugin back to an older working version.

    I have tested this by creating an exact clone of our website, disabling all plugins except for Elementor, changed the theme to a default theme and the issue still exists. If I restore the plugin to any other version 7.1, 7.0.1, 6.5.4 no issues.

    This is not only happening on our website it is happening on multiple client websites that have been updated to version 7.2 so it’s not an isolated issue with just our website it is happening across dozens of websites that were upgraded to version 7.2. These issues don’t happen when these sites are rolled back to version 7.1 or older.

    I even setup a brand new install of WordPress with a default theme and zero plugins outside of Elementor and LScache and tested it by opening up a new page in Elementor and then exiting the page and it does the exact same thing displays this error “setting Disable All Features is currently enabled. Click here to change” and also has this error with trying to rollback the plugin Failed to communicate with QUIC.cloud server: Unknown error: unknown commit [server] https://wpapi.quic.cloud [service] beta_test

    I then deleted that site and did another fresh install and this time used Divi page builder and opened a page and then exited and no errors where displayed concerning “setting Disable All Features is currently enabled. Click here to change” but going to the tools section of LSCache and trying to rollback the plugin to 7.1 yielded this error Failed to communicate with QUIC.cloud server: Unknown error: unknown commit [server] https://wpapi.quic.cloud [service] beta_test and since Divi handles it’s exiting the page builder differently than Elementor does I imagine the same error concerning the debug settings still exists I just can’t see the error in the WordPress dashboard because Divi exits the page builder differently than Elementor does when returning you to the WordPress dashboard.

    So there is a serious issue with the LSCache plugin version 7.2 and it seems to be happening no matter what is running on the website using a default theme Twenty Twenty-Five and two plugins installed those being a page builder in my test Elementor and LSCache. There are still errors using other page builders like Divi which too was installed on a brand new WordPress installation using no plugins at all except for LSCache.

    • This topic was modified 11 months ago by jstubbs034.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support qtwrk

    (@qtwrk)

    11 months ago

    apologize for the inconvenience , yes, the elementor part is a message you can ignore ,

    by design , it will enable “disable all features” when you enter the elemntor builder page , and exit again once you leave the elemnetor page , it will be address in next version.

    the beta_test error , as far as I remember , this action should only be trigger when you try to upgrade/downgrade in the beta test page , did you do anything from there ? or you were downgrading from there ?

    Thread Starter jstubbs034

    (@jstubbs034)

    11 months ago

    I get the Elementor error however that still doesn’t explain the disconnect from QUIC.cloud just from upgrading the plugin from 7.1 to 7.2 it also doesn’t explain the pagespeed drop which is actually pretty harsh or the random REST API errors that pop up in the WordPress dashboard saying that the plugin cannot connect to QUIC.cloud. None of those issues exist when the plugin is set back to 7.1, 7.0.1, or even 6.5.4. 7.2 Has given so many problems after udating it that I’m forced to run my site on an outdated version just to keep the connection to QUIC.cloud. On another clients website that was updated to 7.2 their pagespeed score for desktop fell from a 99 to an 83 and it too disconnected from QUIC.cloud on updating the plugin and had to be reconnected and after reconnecting it the pagespeed dropped as mentioned. If I restore it back to 7.1 the pagespeed score goes back upp to 99 on desktop. So something is off with that plugin.

    Thread Starter jstubbs034

    (@jstubbs034)

    11 months ago

    Also if it is normal for it to be displaying that error when coming out of the Elementor page builder how come it doesn’t do it when 7.1, 7.0.1 or 6.5.4 is installed? Also how come 7.2 is the only version having REST API issues with QUIC.cloud and disconnecting the CDN none of the other versions do that.

    Plugin Support qtwrk

    (@qtwrk)

    11 months ago

    it’s not exactly an error but more like a message or notification.

    from code, it is designed to work that way , that when engage the elementor builder , it will enable itself into “disable all feature” mode to avoid conflict , and then exit “disable all feature” mode after exit the elementor builder , it’s been this way all the time , except there wasn’t a notification before

    I did a quick look over that particular section of code but don’t see anything obvious related for instance , I will check up further and get back to you.

    Plugin Support litetim

    (@litetim)

    11 months ago

    @jstubbs034 please share a report ID.
    Reports can be created and shared from LSC => Toolbox => Report and click on “Send to Litespeed”
    Thank you

    Thread Starter jstubbs034

    (@jstubbs034)

    11 months ago

    Right now we are using 7.0.1 and I don’tplan on updating it because our site is live and everytime I update the plugin it ruins our website pagespeed. I may reclone the site later today and update the plugin but that is the best I can offer to you for a report.

    Plugin Support litetim

    (@litetim)

    10 months, 4 weeks ago

    @jstubbs034
    Are you not able to create a report and share that ID? No other info is needed.

    Thank you

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

The topic ‘Plugin Version 7.2 Errors’ is closed to new replies.