Conversation
supportHave downgraded to 4.0.3 which resolves the problem. Waited to see if an update to 4.0.4 would appear but nothing so far. Possibly an interaction with some other plugin, the usual advice is to disable all plugins. But hoping we don’t have to do this. [31-May-2026 02:21:11 UTC] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function WooCommerce\PayPalCommerce\Settings\Service\ScriptDataHandler::__construct(), 9 passed in /home/lamp/wordpress/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-settings/services.php on line 246 and exactly 10 expected in /home/lamp/wordpress/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-settings/src/Service/ScriptDataHandler.php:31 Stack trace: 0 /home/lamp/wordpress/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-settings/services.php(246): WooCommerce\PayPalCommerce\Settings\Service\ScriptDataHandler->__construct(Object(WooCommerce\PayPalCommerce\Assets\AssetGetter), true, ‘AU’, ‘KxxxxxxxxxxxJ’, Array, Object(WooCommerce\PayPalCommerce\ApiClient\Helper\PartnerAttribution), Object(WooCommerce\PayPalCommerce\Settings\Data\SettingsProvider), Object(WooCommerce\PayPalCommerce\ApiClient\Helper\PaymentLevelEligibility), true) 1 /home/lamp/wordpress/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Container/ReadOnlyContainer.php(46): WooCommerce\PayPalCommerce\Settings\SettingsModule::WooCommerce\PayPalCommerce\Settings{closure}(Object(WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer)) 2 /home/lamp/wordpress/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-settings/src/SettingsModule.php(229): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Container\ReadOnlyContainer->get(‘settings.servic…’) 3 /home/lamp/wordpress/core/wp7.0/wp-includes/class-wp-hook.php(341): WooCommerce\PayPalCommerce\Settings\SettingsModule->WooCommerce\PayPalCommerce\Settings{closure}(‘plugins.php’) 4 /home/lamp/wordpress/core/wp7.0/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array) 5 /home/lamp/wordpress/core/wp7.0/wp-includes/plugin.php(522): WP_Hook->do_action(Array) 6 /home/lamp/wordpress/core/wp7.0/wp-admin/admin-header.php(123): do_action(‘admin_enqueue_s…’, ‘plugins.php’) 7 /home/lamp/wordpress/core/wp7.0/wp-admin/plugins.php(637): require_once(‘/home/lamp/word…’) 8 {main} thrown in /home/lamp/wordpress/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-settings/src/Service/ScriptDataHandler.php on line 31 The page I need help with: [ log in to see the link]
Here is system status report: https://privatebin.syde.com/?e73bb70478402e9d#HgDVdASP8pvhDmsDTcLzoEZTWZ7qb2tgG13eV8QbPTh6
Hello @nikdow Looking at the stack trace, I’m not convinced this is necessarily caused by a plugin conflict. However, without further testing on your side, I won’t be able to confirm that with certainty. This error looks more like an installation or update issue than a plugin conflict. Since downgrading resolved it, it’s possible that some files were not updated correctly, resulting in a mismatch between plugin components. If this occurs again during a future update, I would greatly appreciate it if you could try to identify whether a specific plugin is involved, if any. Without being able to reproduce the issue ourselves, it becomes very difficult for us to investigate and fix it. This particular error is not something I’ve seen reported elsewhere for this release, so at the moment I don’t have another environment where I can reliably retest it. In the meantime, if you have a staging site available, I would recommend testing the update to 4.0.4 there first. That would help confirm whether the issue is related to the update process itself or whether another factor in the environment is contributing to it. Kind Regards Krystian
deactivated all plugins except for WooCommerce and WooCommerce PayPal Payments. Enabled theme twentytwentytwo. Error persists! We use https://repo.wp-packages.org to load free plugins, including the two plugins above. Switching from 4.0.3 to 4.0.4 is done by editing composer.json and running composer update. Apache has only read permission to the plugin files. All files are owned by user composer with permissions 744 or 755.
Upgraded server from php8.3 to php8.4 and tried v4.0.4 and no error now! Hard to believe we were the only webserver in the world running php8.3 though.
Here is system status report: https://privatebin.syde.com/?e73bb70478402e9d#HgDVdASP8pvhDmsDTcLzoEZTWZ7qb2tgG13eV8QbPTh6
Hello @nikdow Looking at the stack trace, I’m not convinced this is necessarily caused by a plugin conflict. However, without further testing on your side, I won’t be able to confirm that with certainty. This error looks more like an installation or update issue than a plugin conflict. Since downgrading resolved it, it’s possible that some files were not updated correctly, resulting in a mismatch between plugin components. If this occurs again during a future update, I would greatly appreciate it if you could try to identify whether a specific plugin is involved, if any. Without being able to reproduce the issue ourselves, it becomes very difficult for us to investigate and fix it. This particular error is not something I’ve seen reported elsewhere for this release, so at the moment I don’t have another environment where I can reliably retest it. In the meantime, if you have a staging site available, I would recommend testing the update to 4.0.4 there first. That would help confirm whether the issue is related to the update process itself or whether another factor in the environment is contributing to it. Kind Regards Krystian
deactivated all plugins except for WooCommerce and WooCommerce PayPal Payments. Enabled theme twentytwentytwo. Error persists! We use https://repo.wp-packages.org to load free plugins, including the two plugins above. Switching from 4.0.3 to 4.0.4 is done by editing composer.json and running composer update. Apache has only read permission to the plugin files. All files are owned by user composer with permissions 744 or 755.
Upgraded server from php8.3 to php8.4 and tried v4.0.4 and no error now! Hard to believe we were the only webserver in the world running php8.3 though.