• Fatal error: Uncaught Error: Failed opening required 'includes/blocks/wc-satispay-blocks.php' (include_path='.:/usr/share/php') in /var/www/sito/wp-content/plugins/woo-satispay/woo-satispay.php:40 Stack trace: #0 /var/www/sito/wp-includes/class-wp-hook.php(324): woocommerce_gateway_satispay_woocommerce_block_support() #1 /var/www/sito/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /var/www/sito/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /var/www/sito/wp-content/plugins/woocommerce/src/Blocks/Domain/Bootstrap.php(94): do_action() #4 /var/www/sito/wp-content/plugins/woocommerce/src/Blocks/Package.php(124): Automattic\WooCommerce\Blocks\Domain\Bootstrap->__construct() #5 /var/www/sito/wp-content/plugins/woocommerce/src/Blocks/Registry/AbstractDependencyType.php(42): Automattic\WooCommerce\Blocks\Package::Automattic\WooCommerce\Blocks\{closure}() #6 /var/www/sito/wp-content/plugins/woocommerce/src/Blocks/Registry/SharedType.php(28): Automattic\WooCommerce\Blocks\Registry\AbstractDependencyType->resolve_value() #7 /var/www/sito/wp-content/plugins/woocommerce/src/Blocks/Registry/Container.php(96): Automattic\WooCommerce\Blocks\Registry\SharedType->get() #8 /var/www/sito/wp-content/plugins/woocommerce/src/Blocks/Package.php(44): Automattic\WooCommerce\Blocks\Registry\Container->get() #9 [internal function]: Automattic\WooCommerce\Blocks\Package::init() #10 /var/www/sito/wp-content/plugins/woocommerce/src/Packages.php(128): call_user_func() #11 /var/www/sito/wp-content/plugins/woocommerce/src/Packages.php(64): Automattic\WooCommerce\Packages::initialize_packages() #12 /var/www/sito/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Packages::on_init() #13 /var/www/sito/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #14 /var/www/sito/wp-includes/plugin.php(517): WP_Hook->do_action() #15 /var/www/sito/wp-settings.php(506): do_action() #16 /var/www/sito/wp-config.php(84): require_once('...') #17 /var/www/sito/wp-load.php(50): require_once('...') #18 /var/www/sito/wp-admin/admin.php(34): require_once('...') #19 /var/www/sito/wp-admin/index.php(10): require_once('...') #20 {main} thrown in /var/www/sito/wp-content/plugins/woo-satispay/woo-satispay.php on line 40
Viewing 3 replies - 1 through 3 (of 3 total)
  • Same situation

    For anyone encountering the same issue with the WooCommerce Satispay plugin causing errors on your WordPress site, here’s a concise temporary fix that can be applied via cPanel or FTP. This solution involves commenting out a specific section of code in the plugin file to bypass the error until an official update is released by the developers.Temporary Fix via cPanel or FTP

    Step 1: Access your site’s files through your hosting account’s cPanel or via an FTP client like FileZilla.

    Step 2: Navigate to the WooCommerce Satispay plugin directory located at /wp-content/plugins/woo-satispay/.

    Step 3: Open the woo-satispay.php file for editing. In cPanel, use the File Manager to locate and edit the file. If using FTP, download the file, open it in a text editor, make your changes, and then upload it back to the server.

    Step 4: Comment out lines 38 to 48 by adding // at the beginning of each line to prevent the plugin from attempting to load a missing file. It should look something like this:

    // function woocommerce_gateway_satispay_woocommerce_block_support() {
    //     if ( class_exists( 'Automattic\WooCommerce\Blocks\Payments\Integrations\AbstractPaymentMethodType') ) {
    //         // require_once 'includes/blocks/wc-satispay-blocks.php';
    //         add_action(
    //             'woocommerce_blocks_payment_method_type_registration',
    //             function( Automattic\WooCommerce\Blocks\Payments\PaymentMethodRegistry $payment_method_registry ) {
    //                 $payment_method_registry->register( new WC_Satispay_Blocks );
    //             }
    //         );
    //     }
    // }
    

    Save your changes. If using cPanel, save directly in the File Manager editor. If using FTP, ensure you upload the modified file back to its original location.

    Plugin Author Satispay

    (@satispay)

    Hello,

    New update available to fix this issue.
    We’re sorry for what happened, please proceed with an update or delete /wp-content/plugins/woo-satispay and proceed to download again the Plugin.

    Best Regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this review.