Hi,
500 errors are server side errors, in this case the Google API. Apart from clearing the error and retrying a bit latter is not much you can do about it.
same here. Problem appeared as soon as I updated to the latest version of this plugin. I agree, 500 error is from Google, but I feel it must be something this plugin is doing differently with the most recent update… previous version continues working fine on another site that I have.
-
This reply was modified 8 years, 3 months ago by
cconstantine.
In the Admin Widget, I’m getting data without issue, but in the front-end widget, I get only (-30).
Errors and Logs had zero in it.
My Chrome console displays “Test” for the reports5.js file for the front-end widget.
I have the front end widget loaded in a Beaver Builder module.
The (-30) is obviously coming from Google, but no idea why. the site is registered and authorized and collecting data in WP-Admin.
Ayn idea what is causing the (-30) to display) in the front-end widget?
Hi,
For security reasons, the only place where you can use the widget is the sidebar.
Thanks!
That did the trick. I used a sidebar in the Page builder and it looks great.
Question: Is there a premium version of the plugin that lets multiple users show their data?
I know it is a very unusual (and weird) question and also requires every user authenticate in their google Analytics account – but this – very special – project justifies this type of dynamism in the plugin.
Everything is free :).
While this particular feature isn’t available the design of the plugin allows further customization with addons.
I was lazy and I’ve just updated from “5.1.2.5” to “5.3.1.1” recently, and I experienced the same problem as OP and two other posters above.
What happened exactly is:
- when I have updated the plugin (with composer), the Analytics account configuration was dropped.
- now, around 24 hours after the update I see no stats in the dashboard nor in the post lists with the same looking errors as OP posted.
However, this does not affect every deployment that I have. Maybe it’s really a partial internal Google error, but then it’s a strange coincidence indeed. I’ve never seen similar errors. So I’m posting because maybe something is still going on.
-
This reply was modified 8 years, 2 months ago by
karex.
-
This reply was modified 8 years, 2 months ago by
karex.