Alin Marcu

Hi, update to 6.3.2 and let me know if you have further issues.

Hi and thanks for the feedback. A fix will be released, we will let you know when available.

@thanewest version 2.2 which was just released, fixes the above issue among a few more things.

All the best!

Hi and thanks for the feedback!

It looks that there’s a bug on plugin’s cache system. It will be fixed on next release, I will ping you when it’s solved.

Meanwhile, by using Clear Cache button it will automatically clear the entire cache (those rows you mention are actually cached reports).

Thanks again for the heads-up, I really appreciate it!

I’ve just test it and the option saves properly (you must use the Save changes button) and the Real-Time reports works fine, without any additional APIs enabled.

I had a tutorial saved as draft for months (didn’t had time to review it), It’s now reviewed and published, you may have a look at it too. Please make sure you haven’t missed a step.

That’s bug then, I will have a look and fix it on next release. I wonder why the units test haven’t failed, but I’ll double check it

For that there’s a checkbox that needs to be enabled under Backend Settings. If you enable it and don’t have access to Real-time API will throw an error. On GA4 I think that access is implicit, no special access needed. Check it out and let me know.

You need to enable Google Analytics Data API and Google Analytics Admin API.

Hi,

Have you enabled Debugging to check the exact line where the error is thrown?

Also if you’re using a custom CA bundle, you should make sure is loaded by WordPress (wp-includes\certificates), you can find some solutions here.

From your original post I understand that you are running WordPress on your own server (not with a hosting company), right?

Hi,

The redirect_uri is:

https://yourdomain.com/wp-admin/admin.php?page=aiwp_settings

Please replace yourdomain.com with your domain name on the above URI.

Please note that if your API project has the Publishing status set as Testing your refresh token wil expire after 7 days. It must be set to In Production. This option can be found on Oauth2 consent screen, but to set it for production there are a few checks including a manual Google check that you’ll have to comply with.

ps. At the moment it looks like I have to re-authorize less frequent after update. So another thing I am happy about.

About that, one thing on oauth2 non-standard and undocumented by Google was the cause. After months on of testing and always focusing on a possible plugin issue it turned out to be a few lines of code causing the mess, which were inline with Google’s documentation and practice.

My fault for not looking into it and taken it as it is, without questioning the standards nor documentation.

Hi again,

I though about sorting the drop-down webstreams list and the fact that other users will preffer it as it is grouped by account. The best solution I could think of is to have the list searchable, making things easier for everyone. This feature is already available on latest release, check it out!

Hi,

Which is the exact report and time interval you’re having issues with?

Because the data comes directly from Google Analytics through an API, there’s no difference, unless you’re checking different reports on the plugin and analytics website,

Nb. With the last update I had to re-authorize the plugin on 14 out of 15 sites. (just for your information)

From now on, an error on a website won’t invalidate the others. Let’s see how it goes. Keep me updated about it. We fixed a bug on latest release. Actually wasn’t a bug was a lack of documentation on Google API which generated the issues.

Hi,

Please clear your browser cache and cookies for the website, purge WordPress cache and any other cache (eg CDN).

If you still have issues let me know. I’ve tested it on two development websites and a live one and it works fine.