• Resolved Nazrinn

    (@nazrinn)


    And my site becomes completely unusable. I had to restore from server backup. Otherwise the whole site would show nothing; it’s like the pages didn’t even try to load, both on the front-end and back office.

    Since this happened on two of my sites and the site started working again when I disabled LiteSpeed Cache (that site still had some dashboard parts accessible, but CPT were hard to access with the same symptoms), I’m thinking an interaction between the CPT UI plugin and the LiteSpeed Cache plugin is the cause.

    Current version of Litespeed Cache: Version 5.2.1.

    I don’t feel comfortable updating CPT UI unless this is fixed, as every time I needed to go in my server, not site backups, to issue a fix.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Hmm, the only way I can think of that we have any direct interaction with litespeed cache is from some CSS/JS assets that we only load in our areas of the backend. Part of this release had some directory changes with where we store those files.

    Do you know how and where to check for error logs? Any information from those could prove useful. If you have any sort of staging copy of the website, I’m wondering if cache clearing would somehow work, though we don’t load anything frontend.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    I just pushed up a 1.13.1 release with a fix for some other peoples’ issues with 1.13.0.

    When you have a chance, please re-try the upgrade and let us know if the issues go away or if they persist. If they remain, we’ll keep looking into it for your situation.

    Thanks.

    Thread Starter Nazrinn

    (@nazrinn)

    I updated it now. All went well! =)

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Awesome, thanks for the followup.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Database connection fails when updating plugin to 1.13’ is closed to new replies.