• All our websites using Contact Form 7 are down now with the following error :

    Got error 'PHP message: PHP Fatal error:  Uncaught Error: Class \"RockLobsterInc\\\\Swv\\\\CompositeRule\" not found in ******/wp-content/plugins/contact-form-7/includes/swv/swv.php

    If I remove the plugin completely and reinstall it, it seems ok. The problem is that we have alot of websites using it. Is there something we can do ?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    Where can we see the website in question? And where did you get the error message?

    I’m having the same error on multiple websites and have downgraded to 6.1.7 for now.

    Got error 'PHP message: PHP Fatal error: Uncaught Error: Class "RockLobsterInc\Swv\CompositeRule" not found wp-content/plugins/contact-form-7/includes/swv/swv.php:129

    Quick fix (temp solution):
    Edit the …/plugins/contact-form-7/load.php file
    Old line:
    require 'vendor/autoload.php';
    New line:
    require WPCF7_PLUGIN_DIR . '/vendor/autoload.php';

    I had the same problem with a ‘vendor’ folder at the root of the WordPress site and WordPress in a ‘wp’ directory.

    Thread Starter ubeo

    (@ubeo)

    @takayukister it is happening on many sites, and it breaks the entire site, frontend and backend. Even if I give you the URL, all you will see is the default WordPress error page. You have the complete error above. It seems to be related to sites using composer.

    Hi @takayukister,

    Same error with 6.2 on a Bedrock install. It also happens when activating via WP-CLI from the project root, which has its own vendor/autoload.php.

    Cause: In load.php, the relative require 'vendor/autoload.php'; loads the project’s root Composer autoloader instead of the plugin’s.

    Confirmed fix:

    php

    require WPCF7_PLUGIN_DIR . '/vendor/autoload.php';

    Please include this in the next release and test with Bedrock setups. Thanks!

    Getting the same error due to auto update of the plugin. Thank you for the fix above, it worked. Bad form on the developers part for such a basic error. Makes me want to disabled auto-updates, to prevent issues like this in the future.

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

You must be logged in to reply to this topic.