• Resolved B

    (@blclda)


    Latest 4.0 version gives my frontpage and non cached pages a critical error.

    Since im running a woocommerce site I had it disabled and the site is working but with css bugs, how can I return to the older version or how can I figure this out?

Viewing 10 replies - 1 through 10 (of 10 total)
  • What theme are you using?

    Thread Starter B

    (@blclda)

    Hey David, I’m using the popular Shoptimizer theme at: https://www.commercegurus.com/product/shoptimizer/

    I deactivated Kirki to keep the site online and just sent the team an email.

    I was foolish enough to update the plugin on our live woo site. How can I go back to using the 3.1.9 version without losing anything?

    • This reply was modified 2 years, 3 months ago by B.
    • This reply was modified 2 years, 3 months ago by B.

    Can you try to update to Kirki 4.0.1? The issue should now be fixed.

    Thread Starter B

    (@blclda)

    Hey David, just did so, the error returned.

    I activated kirki, then updated, then cleared all cache and refreshed the site and the error was back.

    Deactivated kirki again and its functional.

    Here are some prints: https://imgur.com/a/K3cGKgB

    same thing after the update in 4.0.1 https://odyssey.photos

    i downgrade to 3.1.9 and waiting 4.0.2:-)

    • This reply was modified 2 years, 3 months ago by odysseyphotos.

    @odysseyphotos, please try 4.0.3 – this should now work.

    @davidvongries Nice its ok for me 🙂 with the 4.0.3

    Phew, awesome! Thank you for testing! 🙂

    Thread Starter B

    (@blclda)

    Ok David, I just gave it a go, updated it, cleaned cache, and our site seems to be up and running with all the cool Kirki features 🙂

    I’m going to test run it for a few minutes to make sure everything is fine.

    May I know what the problem was?

    Also I saw your “Fingers Crossed” Tweet, ahah man, you and the team managed to fix it it seems in less than 15 minutes, that’s a big achievement, congrats man! And thank you!

    It’s a bit of a tricky one to explain how this happened but basically it came down to a lowercase folder name.

    Thank you for your kind words, I really appreciate that! 🙂 It should be relatively smooth sailing from here on. fingers crossed, haha.

    Best,
    David

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘“There has been a critical error on this website.”’ is closed to new replies.