[ben]

2 years, 2 months ago #30233

Hello Team,

I have installed wpsolr plugin on my wordpress website on the test server. After installation, it displayed me a critical error during backend login into wordpress (screenshot attached 1.1). At that time, I just ignored it and start integrating wpsolr. It worked fine as I wanted but when I installed the plugin on my live server I got the same error while login in. Also, the payment process starts giving errors (screenshot 1.2). After checking everything, I found that wordfence is conflicting with wpsolr, so I disabled wordfence which was already working before the wpsolr installation. As soon as the wordfence plugin is deactivated, the error also disappeared.

Now, in summary, the problem is that wpsolr is conflicting with wordfence and I need both plugins.
Can you please guide me on what can I do to solve this issue?
wpsolr version is : 22.2

Thanks

1.1 https://ibb.co/HxXC4XX
1.2 https://ibb.co/xSd7f2B

• This topic was modified 2 years, 2 months ago by wpsolr.

[ben]

2 years, 2 months ago #30234

Please check the screenshots here
1.1 https://ibb.co/HxXC4XX

1.2 https://ibb.co/xSd7f2B

[wpsolr]

2 years, 2 months ago #30236

What are your PHP errors in debug.log?

[ben]

2 years, 2 months ago #30243

PHP Fatal error: Uncaught Error: Undefined class constant ‘MAJOR_VERSION’ in /var/www/html/corporatementorz.com/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/guzzlehttp/guzzle/src/Utils.php:113\nStack trace:\n#0 /var/www/html/corporatementorz.com/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/guzzlehttp/guzzle/src/functions.php(71): GuzzleHttp\\Utils::defaultUserAgent()\n#1 /var/www/html/corporatementorz.com/wp-content/plugins/gmail-smtp/google-api-php-client/vendor/guzzlehttp/guzzle/src/Client.php(194): GuzzleHttp\\default_user_agent()\n#2 /var/www/html/corporatementorz.com/wp-content/plugins/gmail-smtp/google-api-php-client/vendor/guzzlehttp/guzzle/src/Client.php(75): GuzzleHttp\\Client->configureDefaults()\n#3 /var/www/html/corporatementorz.com/wp-content/plugins/gmail-smtp/google-api-php-client/src/Google/Client.php(1058): GuzzleHttp\\Client->__construct()\n#4 /var/www/html/corporatementorz.com/wp-content/plugins/gmail-smtp/google-api-php-client/src/Google/Client.php(1032): Google_Client->createDefaultHttpClient()\n#5 /var/www/ in /var/www/html/corporatementorz.com/wp-content/plugins/wpsolr-pro/wpsolr/core/vendor/guzzlehttp/guzzle/src/Utils.php on line 113

[ben]

2 years, 2 months ago #30245

Hello Team is there any update on my issue?

[wpsolr]

2 years, 2 months ago #30248

It is a conflict with Guzzle: https://www.wpsolr.com/forums/reply/30203/

[ben]

2 years, 2 months ago #30254

I am not sure how to resolve this Guzzle issue can you please guide me?

[wpsolr]

2 years, 2 months ago #30255

Both WPSOLR ad gmail-smtp use the same library, but with different versions (the latest for WPSOLR).

When gmail-smtp calls Guzzle, the one from WPSOLR is called instead, but with a different signature, hence the error.

There is no good solution but to ask gmail-smtp to deliver a release with the latest Guzzle version (not sure it is possible).

(deactivate gmail-smtp to verify that WPSOLR is fine without this conflict)

[wpsolr]

2 years, 2 months ago #30282

I’m closing this topic, as you opened the same question at https://www.wpsolr.com/forums/topic/indexing-is-not-working-for-orders-in-wordpress-back-end/page/4/. I’ll answer from there.