Plugin conflict after update to 2.3.1

  • Resolved paulaaconway

    (@paulaaconway)


    8 years ago

    This plugin worked fine until I updated to the latest version. The error message produced was:

    Warning: require_once(/home/wfomikko/iam-sheffield.org/wp-content/plugins/uk-cookie-consent/public/class-ctcc-public.php): failed to open stream: No such file or directory in /home/wfomikko/iam-sheffield.org/wp-content/plugins/uk-cookie-consent/uk-cookie-consent.php on line 36

    Fatal error: require_once(): Failed opening required ‘/home/wfomikko/iam-sheffield.org/wp-content/plugins/uk-cookie-consent/public/class-ctcc-public.php’ (include_path=’.:/usr/local/lib/php:/usr/local/php5/lib/pear’) in /home/wfomikko/iam-sheffield.org/wp-content/plugins/uk-cookie-consent/uk-cookie-consent.php on line 36

    The updated plugin completely blocked my access to the wordpress installation. I now have a fully working version on my local server with the cookie consent plugin restored to the last version (2.3.0). All the plugins work fine and the WordPress installation is fully functional on the local server.

    Thanks for your help
    Paul Conway
    Editor, Social Media & Webmaster
    Sheffield Advanced Motorcyclists
    https://iam-sheffield.org

Viewing 3 replies - 1 through 3 (of 3 total)
  • Gareth

    (@catapult_themes)

    Hmm. Possibly a file got corrupted during the update.

    I suggest you deactivate and delete the plugin. Then reinstall from scratch.

    Let me know how you get on.

    Gareth

    Thread Starter paulaaconway

    (@paulaaconway)

    Thanks for the rapid reply Gareth. I’ve been able to reinstall the files from the previous version onto the live site to get it up and running. I’ll test out installing the plugin update on my local server, but this test will have to wait a day or so. I’ll let you know how I get on. At least the biker charity has their website back ??

    Paul

    Gareth

    (@catapult_themes)

    I’m marking this as resolved. Let me know if you have any further problems.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Plugin conflict after update to 2.3.1’ is closed to new replies.