Dependency problem

I’ve heard of other plugins namespacing their entire set of composer dependencies to avoid any conflicts with other plugins…we’ll look into whether this is feasible for this project.

We do have it planned for the next minor version to bump minimum PHP to 7.2 (since the latest phpCAS version requires it), but you know how it goes…there’s always someone out there running an ancient version that will complain about it breaking!

I see…When the next version will be ready?

We are targeting the end of August for the next release.

In the meantime, if you have access to a test environment, you can change the config/platform/php version in composer.json to 7.2.5 and then run composer update. This won’t namespace the dependencies, but it may get you up to the same version of guzzlehttp used by the other conflicting plugin.

One other option to try is to request the other plugin be namespaced as well…they may be faster than us getting an update out!

FYI this is the fix we expect to use, php-scoper:
https://github.com/sureswiftcapital/Simple-Calendar/issues/341

Aloha, we reached out to the dPlugin folks and they provided us with a testing copy of the Collaboration plugin. However, we had no problems activating both Authorizer and Collaboration plugins at the same time.

Can you provide more details on the specific error message(s) related to the guzzlehttp/guzzle library, and what specific actions trigger the error?

This is the system error email when enabled Authorizer and Collaboration. Thank you.

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

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.8
Current theme: Twenty Twenty-One (version 1.4) Current plugin: Aether – dPlugins Framework (version 1.1.17) PHP version 7.4.3

Error Details
=============
An error of type E_ERROR was caused in line 61 of the file /var/www/emhk/wp-content/plugins/aether/vendor/guzzlehttp/guzzle/src/functions.php. Error message: Uncaught Error: Call to undefined method GuzzleHttp\Utils::chooseHandler() in /var/www/emhk/wp-content/plugins/aether/vendor/guzzlehttp/guzzle/src/functions.php:61
Stack trace:
#0 /var/www/emhk/wp-content/plugins/authorizer/vendor/guzzlehttp/guzzle/src/HandlerStack.php(42): GuzzleHttp\choose_handler()
#1 /var/www/emhk/wp-content/plugins/authorizer/vendor/guzzlehttp/guzzle/src/Client.php(65): GuzzleHttp\HandlerStack::create()
#2 /var/www/emhk/wp-content/plugins/oxyrealm-collaboration/vendor/pusher/pusher-php-server/src/Pusher.php(69): GuzzleHttp\Client->__construct()
#3 /var/www/emhk/wp-content/plugins/oxyrealm-collaboration/oxyrealm-collaboration.php(142): Pusher\Pusher->__construct()
#4 /var/www/emhk/wp-includes/class-wp-hook.php(303): Oxyrealm\Modules\Collaboration\Collaboration->boot()
#5 /var/www/emhk/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters()
#6 /var/www/emhk/wp-includes/plugin.php(470): WP_Hook->do_action()
#7 /var/www/emhk/wp-settings.php(578): do_action()
#8 /var/www/emhk/w`

Here is the screen of the plugin error page.

View post on imgur.com

Aloha, thanks for the details; we’ve reproduced the issue and are working on a fix scoping/namespacing the composer dependencies.

We’re running into problems with some of the oauth2 libraries, so it’s taking longer than expected. You may want to reach out to the Collaborator developers as well and ask them to scope their dependencies; they may have more luck getting a fix out sooner than us.

We’ll keep you updated on progress here!

Aloha, we weren’t able to get php-scoper to work for our specific dependencies so we have just updated our minimum PHP version to 7.2.5 which should force guzzlehttp/guzzle to the same version used by your other plugin, aether.
https://github.com/uhm-coe/authorizer/commit/97d969c2394941792a194ca64c9ddf7cdac89a57

This will be included in the next version 3.2.0 due out on Monday, we are doing final tests now.

Aloha, version 3.2.0 has been released. Please test and let us know if you see any issues.

I can enable both Authorizer and Collaboration plugin now. Many thanks! ??

Great, thanks for verifying!