[Plugin: Google Analytics Dashboard] User Rate Limit Exceeded – Please help.

Hi Carlson,

2.0.4 doesn’t seem to fix it for me I’m still getting issues, do you have an ETA on the fix for this?? If not I was thinking I could implement api handling into it pretty easily using this gem

https://code.google.com/p/google-api-php-client/

Let me know if your not doing it and I’ll update it for you and email it to you so you can update it, unless of course you want to give me svn access to do it myself.

Kind regards,

Sean.
Static Dream

Hi Carlson

Getting the same issue here too. A fix would be great.

Happy to test a beta version and give feed back if that would help.

Cheers Karl

I also need a fix for this.

Gary

Having the same issue. Any luck finding a fix for this?

Thank you,
Carolyn

And another usageLimitsuserRateLimitExceededUnregUser Rate Limit Exceeded
Any fix yet?

Same problem as stated on your blog. Can I tru the OAuth improvement?

I had this problem for a couple of months now with one of my websites https://www.windowswebwereld.nl

But today I solved it, only I don’t know what exactly the solution was. Anyway, this is what I did:
– Uninstalled the Google Analytics Dashboard plugin
– Deleted everything in the database with “GAD” in it.
– Then installed the Google Analytics Dashboard again.
– After that I installed another plugin, the Google Analytics Dashboard Stats plugin. I configured that plugin, but I didn’t liked this plugin as much as the other one, so I disabled this plugin very quickly.
– Than suddenly the Google Analytics Dashboard worked again. Maybe the other plugin has reset something, but I don’t know that for sure.

Please tell me if this solution worked for you!

foodin65 i solved my problem using this plugin:

https://www.ads-software.com/extend/plugins/google-analytics-dashboard-for-wp/

this plugin allows you to use your own Google API Project. Using your own Google API Project is almost impossible to reach the limit of 50.000 requests/day.

I’m having this issue too:

Error gathering analytics data from Google: usageLimitsuserRateLimitExceededUnregUser Rate Limit Exceeded. Please sign uphttps://code.google.com/apis/console

Then there is a Please Try Again Later message on the settings page, so I can’t un-authorize/re-authorize as some have suggested… those options aren’t even there.

I found the solution to this problem elsewhere:

try dropping

add_action( 'admin_init', 'delete_gad_options' );
function delete_gad_options() {
	delete_option( 'gad_login_pass' );
	delete_option( 'gad_login_email' );
	delete_option( 'gad_auth_token' );
}

in your theme functions.php file, refresh an admin page, then delete the code or comment it out.

I am having the same problem. @supertrooper2 I’d like to try your solution, but I’m not so tech savvy. What do you mean “refresh an admin page” and “‘comment it out”?

I tried uninstalling and reinstalling the wordpress Google Analytics Dashboard plug-in but it didn’t fix it. Also, I turned on the Analytics API but that didn’t do anything either.

Any easy-to-follow help would be greatly appreciated. My site is https://www.neversaydiebeauty.com

Acohen,

Open your theme’s functions.php file in your ftp upload window and copy / paste the above code into it. Then refresh a wordpress admin page.

Finally delete the code from your theme’s functions.php file in your ftp upload window (i.e. revert to the original file).

If you then open the GAD settings page, you should find that this procedure has served to reset the plugin. The settings should again be visible.

Hope this helps.

@supertrooper2 does it matter where in the function.php I place the code?

I placed the code that @supertrooper2 suggested toward the top of the function.php, saved the file, refreshed the page, deleted the code, saved the file, went to the GAD setting, logged in via the process on top, and got the same error message:

Error gathering analytics data from Google: usageLimitsuserRateLimitExceededUnregUser Rate Limit Exceeded. Please sign uphttps://code.google.com/apis/console

Please try again later.

Did I do something wrong? Any other ideas?