Carson McDonald

Thanks for the patch. I will integrate it in the next update I make. I wish I would have seen this before I released the 2.0.4 version.

Sorry for the late response. I end up getting answers split between forums here and the Google groups I set up years ago. I hope the latest update fixes this for people. I was aware that the older system was being shut down but I wasn’t aware that they were going to remove the old hosts the plugin used.

I will put it on a todo list but I can’t say how long it will take. I’ve been re-energized to work on the plugin by the recent issues so I may find time soon to make some changes. I really want to try to move to the latest API system and that will take a pretty good bit of rework of the plugin.

This isn’t a simple issue to fix really. First off I haven’t been able to trigger the limit in my testing. Second is that Google doesn’t supply the actual limit they place on unregistered API calls so it is hard to tell just how bad of problem this is. It could be different for everyone.

Getting access to registered API calls is something that can’t be automated and I can’t gauge how easy it will be for people to go through the process. Each person using the plugin would have to go through that process.

Having said that, are any of you guys willing to install a test version of the plugin potentially? I may be able to add a new field into the options that takes an API key and tacks it on to every request. You would have to register for the API key and that is where the difficulty would come in but then I would know just how hard it is going to be.

I wonder if this is potentially caused by using older login information. Can one of you guys try going to the settings for the plugin and doing a auth reset and then logging in again using the OAuth system? You can reset auth by going into the plugin’s settings and checking the “” checkbox then hitting save. You should then see the auth page where you will want to follow the instructions for using the “Login using Google’s OAuth system.” version.

There is some limit to the number of times the data can be loaded in a day. You may have run into that limit. The plugin caches the data for a few minutes and I could increase that time but I haven’t seen anyone else have this type of problem. I could imagine it happening if you went through a lot of pages of past posts. Did it work at all after you installed it?

You should check your php error logs and see if there are any errors being produced.

Do you have access to your PHP error log? Can you tell if there are any errors being reported there?

Maybe try this to see what it says: https://help.godaddy.com/article/3937 If it says PHP 4 then that is probably the issue.

Are you seeing that error after you are loading the posts page or just when you log in to the dashboard? There is a limit on the number of times the requests to Google can be made in a row and that is why the caching is in there as well as delay that I added to try and space requests apart. It may be that the delay isn’t long enough.

What version of PHP are you using?

This should be fixed in the 2.0.3 release.

Can you try the 2.0.3 update and let me know if it looks better?

The new release is out (2.0.3) so I think that should have this fixed. Anyone want to verify that it looks good?

No problem.