Errore critico per il nuovo aggiornamento

  • Resolved davidepichler

    (@davidepichler)


    9 months, 2 weeks ago

    Ho disattivato il plugin WooCommerce Satispay (versione 2.2.0) perché dopo il nuovo aggiornamento la pagina va in errore critico con il plugin attivo. 


Dettagli dell'errore:

====================

Un errore di E_ERROR è stato causato nella linea 40 del file /var/www/clients/client0/web14/web/wp-content/plugins/woo-satispay/woo-satispay.php. Messaggio di errore: Uncaught Error: Failed opening required 'includes/blocks/wc-satispay-blocks.php' (include_path='.:/usr/share/php') in /var/www/clients/client0/web14/web/wp-content/plugins/woo-satispay/woo-satispay.php:40

Stack trace:

#0 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(324): woocommerce_gateway_satispay_woocommerce_block_support()

#1 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#2 /var/www/clients/client0/web14/web/wp-includes/plugin.php(517): WP_Hook->do_action()

#3 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Domain/Bootstrap.php(94): do_action()

#4 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Package.php(125): Automattic\WooCommerce\Blocks\Domain\Bootstrap->__construct()

#5 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Registry/AbstractDependencyType.php(42): Automattic\WooCommerce\Blocks\Package::Automattic\WooCommerce\Blocks\{closure}()

#6 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Registry/SharedType.php(28): Automattic\WooCommerce\Blocks\Registry\AbstractDependencyType->resolve_value()

#7 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Registry/Container.php(96): Automattic\WooCommerce\Blocks\Registry\SharedType->get()

#8 /var/www/clients/client0/web14/web/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/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Packages.php(128): call_user_func()

#11 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Packages.php(64): Automattic\WooCommerce\Packages::initialize_packages()

#12 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Packages::on_init()

#13 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#14 /var/www/clients/client0/web14/web/wp-includes/plugin.php(517): WP_Hook->do_action()

#15 /var/www/clients/client0/web14/web/wp-settings.php(506): do_action()

#16 /var/www/clients/client0/web14/web/wp-config.php(99): require_once('...')

#17 /var/www/clients/client0/web14/web/wp-load.php(50): require_once('...')

#18 /var/www/clients/client0/web14/web/wp-login.php(12): require('...')

#19 {main}

thrown

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

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

  • Ho lo stesso problema. Stesso errore, stessa linea di davidepichler
    Nel mio caso manda in crash l’intero sito.
    Il plugin era stato messo in rinnovo automatico.
    Appena è partito l’auto-update, il sito è andato fuori uso.
    Molto grave, anche perché si tratta solo di un plugin per il sistema di pagamento e non di un plugin di sistema Che possa crasher un sito è preoccupante. Ovviamente se il problema si risolve non mentterò più il plugin in auto-update Grazie per l’attenzione
    —-
    I have the same problem. Same error, same line from davidepichler In my case it crashes the entire site. The plugin had been put on automatic renewal. As soon as the auto-update started, the site went down. Very serious, also because it is only a plugin for the payment system and not a system plugin. The fact that it can crash a site is worrying. Obviously if the problem is solved I will no longer auto-update the plugin. Thanks for your attention.

    • This reply was modified 9 months, 2 weeks ago by supergap.
    Plugin Author Satispay

    (@satispay)

    Salve,

    E’ stata rilasciato un nuovo aggiornamento che risolve il problema.
    Qualora non sia possibile aggiornare o usare il sito, cancellate la folder in: /wordpress-folder/wp-content/plugins/woo-satispay/ dopodiché aggiornate scaricate e installate il plugin.

    = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

    Hello,

    a new update has been released and it solves the crash of the latest release.
    If you cannot access your website, please manually delete this folder and try to download our plugin again:
    /wordpress-folder/wp-content/plugins/woo-satispay/ then download and install the newest version.

    • This reply was modified 9 months, 2 weeks ago by Satispay.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Errore critico per il nuovo aggiornamento’ is closed to new replies.