ljmac

Ah, I found I could authorise the plugin if I clicked on Advanced when Google showed me a warning screen, then agreed to “accept the risks”. It might be a good idea to add this to the instructions – I was stuck in testing mode because I thought I had to verify.

In your documentation it says “You don’t need to verify it further since only a handful of users will access it.” But when I publish the app it says it needs verification – is this actually necessary, or did I get something wrong in the setup process? In order to do verify it, I have to submit a YouTube video with the following info:

Your YouTube video should demonstrate the OAuth grant process by users and explain, in detail, how you’ll use sensitive and restricted scopes within the app’s functionality for each OAuth client belonging to the project. Learn more
The video should clearly show the app’s details such as the app name, OAuth client ID, and so on.

AFAIK I have to use my own Google Cloud Console Project in developer mode, right?

Also, what do you mean exactly by ”?Publish the app without necessarily verifying it”?

Could this be related to why I had to use the developer mode to set up the plugin?

I assume you will set this up so that only older WordPress versions use the deprecated function? It would obviously be better for the future of your plugin to stick with the new function for newer WordPress versions, especially as it doesn’t appear to cause any actual problems apart from the errors in the logs.

I already did after your last help ??

https://www.ads-software.com/support/topic/absolutely-stellar-support-2/

Wow, you really are fast! No errors now, and I like that it is no longer necessary to manually enable real time reporting.

Oh my goodness, stupid me: I forgot the save changes button!

It might be a good idea to get rid of the out of date reference to the Real-Time Reporting API though.

Thank you so much for your very prompt and thorough help!

I looked up the Real-Time Reporting API, and it said the following:

This API is deprecated and does not support Google Analytics 4 (GA4) properties. Use the Data API to access the reporting features for GA4 properties.

Yet I already have the data API. Perhaps your plugin needs to be updated for the new API.

• This reply was modified 1 year, 2 months ago by ljmac.

I tried switching that on but it switched itself back off as soon as I left the screen, yet there was no error message or report.

I already had those two enabled – I found I had to also enable the ‘Google Analytics API’ – now it’s finally working!

So your plug in doesn’t have the real time view any more?

• This reply was modified 1 year, 2 months ago by ljmac.

I am on a VPS, which I set up myself, although it is with a hosting company. The Cloudflare cert is officially signed, not self signed.

I did mange to get the plugin fully authorised with the right redirect uri, but a soon as I went to the Dashboard I got a 403 error, then when I went back to your plugin I found it had become de-authorised with the following error:

API Error Reason: Google Analytics Data API has not been used in project [number] before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/analyticsdata.googleapis.com/overview?project=%5Bnumber%5D then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.API Error Details: Array ( [0] => PERMISSION_DENIED [1] => trying to refresh token )

Thank you so much for the fast response! Do you have any idea what might be causing the SSL error when trying to authorise in the normal way?

Some further info: I have tried earlier versions of this plug in, and I have found that 2.0 and earlier do not have this problem.

I have found it produces the following error while optimising as well:

[25-Aug-2022 19:00:03 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘WHERE term_id NOT IN (SELECT term_id FROM as_terms)’ at line 1 for query DELETE FROM WHERE term_id NOT IN (SELECT term_id FROM as_terms) made by do_action_ref_array, call_user_func_array, aDBc_clean_scheduled_elements, aDBc_clean_elements_type

I hope it doesn’t cause any harm – your plugin certainly does appear to be the very best of its type.

Okay great! Happy to be of help. ??

Lee