Have conflict with others plugins (updraftplus and supersocializer)
1. Updraft Plus
2 SuperSocializer
Just tryin login with Google from frontend, similar error occur
Error Details
=============
An error of type E_ERROR was caused in line 92 of the file /wp-content/plugins/google-site-kit/vendor/google/apiclient/src/Google/Client.php. Error message: Uncaught TypeError: Argument 1 passed to Google_Client::__construct() must be of the type array, object given, called in /wp-content/plugins/updraftplus/methods/googledrive.php on line 825 and defined in /wp-content/plugins/google-site-kit/vendor/google/apiclient/src/Google/Client.php:92
Stack trace:
#0 /wp-content/plugins/updraftplus/methods/googledrive.php(825): Google_Client->__construct(Object(Google_Config))
#1 /wp-content/plugins/updraftplus/methods/googledrive.php(512): UpdraftPlus_BackupModule_googledrive->bootstrap(Array)
#2 /wp-includes/class-wp-hook.php(286): UpdraftPlus_BackupModule_googledrive->show_authed_admin_success('')
#3 /wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#4 /wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#5 /wp-admin/admin-header.php(289): do_action('all_admin_not
_Do not alter or remove anything below. The following sections will be managed by moderators only._
Hi @tunakode
Thanks for your report! We鈥檙e aware of this conflict with UpdraftPlus and are actively investigating it here.
You also mention a conflict with Super Socializer. Could you provide the details of the error message you received for that? We have an open issue with a plugin called LoginPress, so would be good to know if this is something similar.
Thank you!
Sorry for late reply, SuperSocializer conflict might related to Google Library
PHP Fatal error: Cannot declare class Google_Service, because the name is already in use in /wp-content/plugins/super-socializer/library/Google/Service.php on line 18
I;m not found any kind error in my logs except the one above, recording every I;m tryin to login with Google login.
We're now tracking work on this in #612.
Closing as a duplicate of #612.
Most helpful comment
We're now tracking work on this in #612.