Hello @simonjonharding
This type of error, known as an E_ERROR, typically occurs when there is a conflict with another plugin on your site. To resolve this issue, I recommend the following steps:
- Reinstall the PayPal Payments plugin with all other plugins disabled to see if the error recurs.
- If the error does not appear, begin re-enabling the other plugins one at a time or in alphabetical batches (starting with ‘A’, then ‘B’, etc.) to identify which plugin is causing the conflict. Please ensure that you reinstall the PayPal Payments plugin after enabling each batch of plugins to check for the error. This method speeds up the process rather than enabling them one by one.
- Once you identify the conflicting plugin, you may decide to either replace it with an alternative or reach out to the plugin’s developer for a potential fix.
Although the update appears to have been completed successfully and there are no visible issues, the error indicates there could be an underlying problem that might affect the functionality of plugin.
Please try the suggested steps and let us know how it goes. If you need further assistance or would like us to assist with the testing, feel free to contact us.
Kind Regards,
Krystian
I appreciate what you are saying, and this is standard advise regards plugins that are being installed for the first time.
However, given that this is a WooCommerce site (so WooCommerce, WooPayments, WooCommerce Paypal Payments), and that this error has only occurred having updated the PayPal Payments plugin to the latest version, isnt is more likely that the issue resides with the new version? The collection of plugins in use hasnt changed for a couple of years or more, and this error has never occurred when updating any of the plugins before.
For now I have restored the previous version of this plugin 2.6.0 with no issues.
Hello @simonjonharding,
The fact that the conflict occurred out of nowhere due to an incompatibility with a third-party plugin is not unexpected, but it can happen – we would like to know which plugin is causing this, as then we can reproduce it on our end, and potentially address this.
It’s probably not a widespread problem with the plugin itself, as I didn’t experience any issues when I updated the plugin.
Most likely, the issue won’t occur if all plugins are disabled. You can try it out. In any case, I’ll forward this output to the developers to see if they can shed more light on this.
You can also test this version (essentially the same as the auto-update) here and check if you encounter the same outcome:
Download WooCommerce PayPal Payments 2.6.1
Kind regards,
Krystian
OK. I will create a staging copy and investigate further.
Hello @simonjonharding,
Please start by updating the plugin using the link provided.
This may also be an edge case due to visiting certain parts of the site during the installation of the plugin, which may interfere with the process. Please let us know the result after following these steps.
Looking forward to your response.
Kind regards,
Krystian
I tested installing the update on a staging site without any problem.
I then installed the latest version of the plugin on the live site without issue.
I suspect the original error may have occurred for some reason as I installed multiple updates in one batch, wheras installing this update on its own has not reproduced the same error.
Hello @simonjonharding,
I’m glad to hear that the issue was resolved.
For the next update, I recommend waiting until the installation is fully complete or updating the plugins one at a time. However, such a problem should not recur.
We’ll consider this thread closed for now. If you have any more questions or if another issue comes up, feel free to start a new thread or reply to this one at any time. We’re here to help whenever you need.
Best regards,
Krystian
