Revived Site, Nimble v2.1.1 upgrade to 3.1.32 kills site

  • Sorry if this is long ago dealt with but my keyword search brings up pages of topics but not the same. Basically my title says it all. I imagine the stages of plugin updates have evolved so much that the pathways of connection of old and new have died.

    Any chance you may be able to give me a ‘1-2-3…’ process to follow please?
    Thanks very much.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter aajaanron

    (@aajaanron)

    Hi, I’ve tried all the usual using Customizr theme

    – deactivate all plugins,
    – WP healthchecker which just gave me 2 block errors until I activated Nimble during troubleshooting, then nothing.
    – I think bluehost is still PHP 7.4
    – everything else is right up to date.
    – Have another site using v 2.1.8 that updated to date with no errors.

    So the problem seems to be somewhere between v 2.1.1 and 2.1.8

    If someone tells me where I can find the old versions I will upgrade one by one.

    My noobness is obvious. Thank you.

    Thread Starter aajaanron

    (@aajaanron)

    WP Debug gives this error where all images are, only plugin is Nimble Builder 2.1.1

    ” Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /xyz/xyz/xyz/heyhoov/wp-includes/functions.php on line 5211 ”

    If I deactivate the plugin – or update it to any of the last couple of updates – it gives no error… because there’s no content, it was all in Nimble

    Thread Starter aajaanron

    (@aajaanron)

    Problem solved – I went ahead and deleted everything and started over.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Revived Site, Nimble v2.1.1 upgrade to 3.1.32 kills site’ is closed to new replies.