Conversation
supportI just updated the plugin to 1.6.1 and it “crashed” my site. I used recover mode to disable the plugin. I am running WP 6.8.2, Server architecture: Linux 6.1.0-38-amd64 x86_64, Web server: Apache/2.4.62 (Debian), PHP version: 8.2.29 (Supports 64bit values). WooCommerce 10.1.2. The page I need help with: [ log in to see the link]
This is the message from the error log (/var/log/apache2/error_log): [Tue Sep 02 12:24:44.772454 2025] [php:error] [pid 625722:tid 625722] [client 108.161.129.198:48784] PHP Fatal error: Declaration of Dhii\Container\ProxyContainer::has($key) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool in /var/www/countryrobot/wordpress/wp-content/plugins/zettle-pos-integration/vendor/dhii/containers/src/ProxyContainer.php on line 50
Hello @robertpheller To proceed, please try the following steps: Download and install this release candidate version: https://drive.google.com/uc?id=1RoOXsE3Qlh4JhYtlGp1fmheRu0aV-8bH Upload and activate it from Plugins > Add New > Upload Plugin . If your site still crashes, disable all plugins except WooCommerce and Zettle , then activate the plugin again. If successful, reactivate your other plugins one by one to check if any specific one is causing the conflict. Let us know which plugin triggers the crash, if any. Also, please follow these steps to share your system status report with us: Navigate to the WooCommerce / Status section in your site’s admin panel. Click on the Get system report button and then click Copy for support . Paste the report into our PrivateBin . After uploading, please share the link here so we can review the details thoroughly. Looking forward to your response. Kind Regards, Krystian
The plugin won’t activate: “Plugin could not be activated because it triggered a fatal error .” OK, it works will all my plugins except BackWPup . This reply was modified 8 months, 4 weeks ago by Robert Heller .
The system report is here: https://privatebin.syde.com/?585896bfba0c7009#A8kNzYxBjFcYDxVnfzKYUPxnqjymYG8uKYPwrppJ2ATD
Hello @robertpheller I have already created an internal issue for this so the development team can review it. Once it is fixed and included in a release, I will let you know right away. In the meantime, the only workaround is to avoid running both plugins together. Kind Regards, Krystian
Has there been any progress on this issue?
Hello @robertpheller Thanks for checking in. We have prepared an updated build that should address the issue. You can download it here: https://drive.google.com/uc?id=1ysP6laP3Fh_oG1KhPvbEtgOMMIB6MRgX Please install this version and let us know if it resolves the problem. Once confirmed, we’ll include the fix in the next public release. Kind Regards, Krystian
It still crashes.
Hello @robertpheller Please share the fatal error details that appear after installing the package. You can upload the error log/stack trace to PrivateBin and share the link with us so we can review it. Once we have the exact error output, we’ll identify where it fails. Kind Regards, Krystian
https://privatebin.syde.com/?9b0aca44d919d24a#dHoRe15tUoUwzbpD87HB7eRucFDBFdaQcax5Ce8rm3G
Hello @robertpheller Thanks for sharing the link. If you installed the file as provided, it will appear as a separate plugin rather than replacing the existing one. To avoid conflicts, you likely need to deactivate the old Zettle plugin first before activating this new build. The file itself is fully scoped, so once activated independently, it should not trigger the same error you experienced earlier. Please try that setup and let me know if the issue persists. Kind Regards, Krystian
OK, things have been working fine with 1.6.1+izet-335-new-build-wf.1724d25 — when will the next scheduled update come out?
Still waiting on the next scheduled update….
Still waiting on the next scheduled update… Is this plugin still being maintained? This reply was modified 3 months, 2 weeks ago by Robert Heller .
Hello @robertpheller Yes, the plugin is still actively maintained. We are not planning any significant feature updates in Q1 2026. The bigger changes and improvements are planned for Q2 and Q3 2026. In the meantime, you are currently running the version that resolved the issue on your site – correct me if I’m wrong? I know it’s not an ideal scenario to run an unofficial package, but it shouldn’t create any problems. Kind Regards, Krystian
Hello Firstly, many many thanks to @robertpheller for raising this issue and for chasing up on it. I encountered the same problem around the same time. I have been following this thread for updates almost daily for the last half year or so. Using the listed replacement file fixed my issue, but the BackWPup plugin incompatibility has now resurfaced with the new file (PayPal Zettle POS (version 1.6.2-izet-523-2)). I only noticed that the POS plugin had deactivated when I realised that my stock counts were entirely out of whack, forcing a full inventory. I specifically created this forum account to echo Robert’s interest in a scheduled update that will allow me to return to the standard plugin with automatic updates that will hopefully prevent unexpected downtime or stock desynchronisation. Thank you both for your work on this.
I recently deleted the BackWPup plugin because it was insisting on backing up the whole site (DB AND files), and would not just backup the DB. (I have a separate process for backing up the files.) This eventually resulted in filling up my disk and causing all sorts of problems. (I eded up writing a bash script to replace the BackWPup plugin.) And I too am awaiting putting the Zettle plugin back on automatic updates…
This is the message from the error log (/var/log/apache2/error_log): [Tue Sep 02 12:24:44.772454 2025] [php:error] [pid 625722:tid 625722] [client 108.161.129.198:48784] PHP Fatal error: Declaration of Dhii\Container\ProxyContainer::has($key) must be compatible with Psr\Container\ContainerInterface::has(string $id): bool in /var/www/countryrobot/wordpress/wp-content/plugins/zettle-pos-integration/vendor/dhii/containers/src/ProxyContainer.php on line 50
Hello @robertpheller To proceed, please try the following steps: Download and install this release candidate version: https://drive.google.com/uc?id=1RoOXsE3Qlh4JhYtlGp1fmheRu0aV-8bH Upload and activate it from Plugins > Add New > Upload Plugin . If your site still crashes, disable all plugins except WooCommerce and Zettle , then activate the plugin again. If successful, reactivate your other plugins one by one to check if any specific one is causing the conflict. Let us know which plugin triggers the crash, if any. Also, please follow these steps to share your system status report with us: Navigate to the WooCommerce / Status section in your site’s admin panel. Click on the Get system report button and then click Copy for support . Paste the report into our PrivateBin . After uploading, please share the link here so we can review the details thoroughly. Looking forward to your response. Kind Regards, Krystian
The plugin won’t activate: “Plugin could not be activated because it triggered a fatal error .” OK, it works will all my plugins except BackWPup . This reply was modified 8 months, 4 weeks ago by Robert Heller .
The system report is here: https://privatebin.syde.com/?585896bfba0c7009#A8kNzYxBjFcYDxVnfzKYUPxnqjymYG8uKYPwrppJ2ATD
Hello @robertpheller I have already created an internal issue for this so the development team can review it. Once it is fixed and included in a release, I will let you know right away. In the meantime, the only workaround is to avoid running both plugins together. Kind Regards, Krystian
Has there been any progress on this issue?
Hello @robertpheller Thanks for checking in. We have prepared an updated build that should address the issue. You can download it here: https://drive.google.com/uc?id=1ysP6laP3Fh_oG1KhPvbEtgOMMIB6MRgX Please install this version and let us know if it resolves the problem. Once confirmed, we’ll include the fix in the next public release. Kind Regards, Krystian
It still crashes.
Hello @robertpheller Please share the fatal error details that appear after installing the package. You can upload the error log/stack trace to PrivateBin and share the link with us so we can review it. Once we have the exact error output, we’ll identify where it fails. Kind Regards, Krystian
https://privatebin.syde.com/?9b0aca44d919d24a#dHoRe15tUoUwzbpD87HB7eRucFDBFdaQcax5Ce8rm3G
Hello @robertpheller Thanks for sharing the link. If you installed the file as provided, it will appear as a separate plugin rather than replacing the existing one. To avoid conflicts, you likely need to deactivate the old Zettle plugin first before activating this new build. The file itself is fully scoped, so once activated independently, it should not trigger the same error you experienced earlier. Please try that setup and let me know if the issue persists. Kind Regards, Krystian
OK, things have been working fine with 1.6.1+izet-335-new-build-wf.1724d25 — when will the next scheduled update come out?
Still waiting on the next scheduled update….
Still waiting on the next scheduled update… Is this plugin still being maintained? This reply was modified 3 months, 2 weeks ago by Robert Heller .
Hello @robertpheller Yes, the plugin is still actively maintained. We are not planning any significant feature updates in Q1 2026. The bigger changes and improvements are planned for Q2 and Q3 2026. In the meantime, you are currently running the version that resolved the issue on your site – correct me if I’m wrong? I know it’s not an ideal scenario to run an unofficial package, but it shouldn’t create any problems. Kind Regards, Krystian
Hello Firstly, many many thanks to @robertpheller for raising this issue and for chasing up on it. I encountered the same problem around the same time. I have been following this thread for updates almost daily for the last half year or so. Using the listed replacement file fixed my issue, but the BackWPup plugin incompatibility has now resurfaced with the new file (PayPal Zettle POS (version 1.6.2-izet-523-2)). I only noticed that the POS plugin had deactivated when I realised that my stock counts were entirely out of whack, forcing a full inventory. I specifically created this forum account to echo Robert’s interest in a scheduled update that will allow me to return to the standard plugin with automatic updates that will hopefully prevent unexpected downtime or stock desynchronisation. Thank you both for your work on this.
I recently deleted the BackWPup plugin because it was insisting on backing up the whole site (DB AND files), and would not just backup the DB. (I have a separate process for backing up the files.) This eventually resulted in filling up my disk and causing all sorts of problems. (I eded up writing a bash script to replace the BackWPup plugin.) And I too am awaiting putting the Zettle plugin back on automatic updates…