Error after update

@rogerpz81 so it sounds like you are able to log in to the backend of the site if you are able to see the Mail Integration settings menu option. Is that the case?

The error should be logged in the WordPress error log on the site, which might provide further clues. If you are able to, disable all plugins and then just the mail integration one and see if you get any issues. If you don’t, keep enabling a single plugin and checking if the error presents itself, and if not, enable another plugin until you hit the one that causes the error to appear.

Ed

Thanks for your response Ed.

It looks like the problem is related with the Ninja Forms plugin.

We really need Ninja Forms so, can we do something to keep both plugins working together?

Kind regards,

Roger

Hi Roger, when I get a chance I’ll download Ninja Forms, but I’ve got quite a bit on at the moment I’m afraid (I’ve got a bit of a DIY project going on at the moment). I may have a spare moment this weekend to take a look.

We are having the same error after updating: There has been a critical error on this website
Detailed error:

Uncaught Error: Call to undefined method GuzzleHttp\Utils::chooseHandler() in
 public_html/wp-content/plugins/mail-integration-365/libs/vendor/guzzlehttp/guzzle/src/functions.php:61
 Stack trace: #0
 public_html/wp-content/plugins/woocommerce-bookings/vendor/guzzlehttp/guzzle/src/HandlerStack.php(42):
 GuzzleHttp\choose_handler() #1
 public_html/wp-content/plugins/woocommerce-bookings/vendor/guzzlehttp/guzzle/src/Client.php(65):
 GuzzleHttp\HandlerStack::create() #2
 public_html/wp-content/plugins/mail-integration-365/libs/vendor/league/oauth2-client/src/Provider/
 AbstractProvider.php(132): GuzzleHttp\Client->__construct(Array) #3
 public_html/wp-content/plugins/mail-integration-365/libs/vendor/thenetworg/oauth2-azure/src/Provider/Azure
 .php(45): League\OAuth2\Client\Provider\AbstractProvider->__construct(Array, Array) #4
 public_html/wp-content/plugins/mail-integration-365/classes/mail_integration_365/admin.php(424):
 TheNetworg\OAuth2\Client\ in
 public_html/wp-content/plugins/mail-integration-365/libs/vendor/guzzlehttp/guzzle/src/functions.php on
 line 61

I regress back to an older version of the plugin 1.71 and the errors go away but will not send any emails even though it activates fine. 1.71 is the last version available of older versions. Wou;d it be possible to get a version closer to 1.82?

@blondeone @rogerpz81 hi both, so I have had a look at this and I’m pretty sure this is down to limitations with dependency handling within WordPress and the use of Composer, as this article explains: https://wordpress.stackexchange.com/questions/175392/how-to-prevent-composer-dependency-conflicts-amongst-wp-plugins

Unfortunately, there isn’t an easy fix to this problem, and indeed no potential solution could resolve the issue if a plugin can’t use the more recent version of the library causing the conflict (as explained in the above article).

It may be a case of choosing which plugin is most important to you site I’m afraid, or finding a combination that doesn’t cause dependency issues.

Of course, if any of you have any ideas/PHP experience, I’m more than happy for you to contribute to development of a solution!

@blondeone @rogerpz81 so I have been investigating a bit more, and this article might hold the solution: https://deliciousbrains.com/php-scoper-namespace-composer-depencies/

I’ll look to test when I get a spare moment!

Hey, can you let us know if your close to a fix? We were going to go live and then Woocommerce Bookings plugin has made this plugin stop working ??

Thanks for your hard work. Your doing great job man

Hi @rogerpz81 @blondeone @hassgt , sorry for the considerable delay in getting to look at this. I develop on a Synology NAS and I was trying to figure out how to install the PHP extensions required to run PHP Scoper. However, I’ve managed to get it working and I believe the composer dependencies are now all uniquely namespaced so they shouldn’t conflict with other plugins utilising the same libraries. I believe this issue has now been resolved but it could do with some testing.

NOTE! You will need to re-authorise the plugin with your 365 Account on the settings page.

• This reply was modified 3 years, 3 months ago by edwardcross.

It works!

Thank you very much for your help and for this plugin! It is very useful!