xfoxx
Forum Replies Created
-
Forum: Plugins
In reply to: [Redis Object Cache] v1.6 and v1.61 breaks themeNot sure if you can install this plugin (clicky) to replicate.
I think the update is breaking this plugin, on my dashboard within wp-admin.
https://en-gb.www.ads-software.com/plugins/clicky-analytics/Doesn’t let it load the API key hosted at clicky anymore.
Gives me error with admin dashboard.The clicky plugin works on the front end side. Just not admin dashboards. Since updating.
https://i.imgur.com/MfQxnF0.png – screenshot
I tried on another server, using different Redis Object Cache plugin (lite-speed) and clicky analytics works fine, using same API key. Was working fine before update.
Forum: Plugins
In reply to: [Redis Object Cache] v1.6 and v1.61 breaks themeThanks for looking into this. 1.62 works with the auto load posts.
- This reply was modified 4 years, 6 months ago by xfoxx.
@pushkar-gaikwad this plugin is installed in around 900,000 sites and this plugin is locking people out of their admin pages, giving error 500 so don’t tell me anything.
Just because it’s free, doesn’t give them the right to break everybody’s site.Should have been tested properly, or let people sign up to beta test etc, before mass releasing. Now they had to release two updates in 1 day, and still not fixed.
At least people are reading my message, renaming the wpsmtp plugin folder, and able to get back into their sites.
@mookie4a4 yes it’s the google api client. The devs reckon they don’t owe us anything so can’t fix it yet.
When you are breaking everybody’s site, it’s important to get the message out, so you know what you’ve done. You do owe us, not to break the sites. Everybody can’t be wrong, look at the other threads.
Slava Abakumov (@slaffik)
8 hours, 31 minutes ago
@xfoxx,I see that you are a not a developer, so it would be very complicated for me to explain to you the roots of your issue.
But please, create a SEPARATE thread to discuss your issue if you want to, and do not pollute unrelated threads with your opinions and incorrect observations.
In any case, please be calm and polite, we don’t owe you anything.
I said it was Google API library problem from day 1 and you said it had nothing to do with it, and I should be ignored.
Then I posted the logs, showing your plugin conflicting with others. Now you admit i’m right.
Why not just put back the old Google API library , how it was, from the old version. And then give us an option, in the settings, to use the new version of Google API library .
It is the apiclient , it’s your buggy version of it, and it’s conflicting and spreading with other plugins that use apiclient too. When I delete your plugin it’s fine.
“makeCredentials() must be an instance of Psr\\Http\\Message\\StreamInterface, array given” Is the problem. Haven’t coded it properly.
[Thu Jun 28 22:09:29.145826 2018] [proxy_fcgi:error] [pid 6457:tid x] [client x] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught TypeError: Argument 2 passed to Google\\Auth\\CredentialsLoader::makeCredentials() must be an instance of Psr\\Http\\Message\\StreamInterface, array given, called in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/google/apiclient/src/Google/Client.php on line 1085 and defined in
/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-stateless/lib/Google/vendor/google/auth/src/CredentialsLoader.php:115\nStack trace:\n#0
/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/google/apiclient/src/Google/Client.php(1085): Google\\Auth\\CredentialsLoader::makeCredentials(‘https://www.goo…’, Array)\n#1
/opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/google/apiclient/src/Google/Client.php(364): Google_Client->createApplicationDefaultCredentials()\n#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/google/apiclient/src/Google/Client.php(796): Google_Client->authorize()\n#3 /opt/bitnami…\n’, referer: https://x.com/wp-admin/index.php
- This reply was modified 6 years, 5 months ago by xfoxx.
I’m on php 7 and use other plugins, that use google-api-php-client and they are fine.
Deleted the plugin now anyway, author not listening to anythingIt’s the google-api-php-client in the new update, don’t know what you’ve done, but you’ve broken everyone’s site
This plugin using out of date or wrongly configured google-api-php-client , not listening to the users. Nothing to do with the php version.