Hi Rick,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

If i understood, this forbidden error happens when you try to disable caching on a table in the back-end of our Plugin settings,

or in the main plugin settings, in the cache option?

The 403 Forbidden Error happens when the web page (or another resource) that you’re trying to open in your web browser is a resource that you’re not allowed to access. It’s called a 403 error because that’s the HTTP status code that the webserver uses to describe that kind of error.

You usually get this error for one of two reasons. The first is that the owners of the webserver have properly set up access permissions and that you’re really not allowed access to the resource. The second reason is that the owners of the webserver have improperly set up permissions and you’re getting denied access when you really shouldn’t be.

You need to contact your hosting provider because you have an issue with your permissions.

Once you do that please let us know if everything is back in order.

Thank you.

Hi Rick,

sorry for this delay between replies.

1. I see what you mean, you are right - that is not the 403 error coming from WordPress,

but it seems it is the response from the Google API,   perhaps there was a misconfiguration or a misstep for setting up the Google API method with our Plugin;

2. But , if you plan to have a lot of tables, we found it is better to not use the Google API method,

because after a while with a large number of tables, you would reach the "Google Quota API limit",

which would cause a new error "Too Many Requests" from the Google API.

So, the best option in your use case is, as you did now, to remove the Google API from our Plugin,

and just go for our 'standard Google Sheet' table connection,

combined with our own Cache and Auto Update Cache function via Cron Job,

and i see that everything seems to work perfect, happy to see that.

We will be here though, let us know if you encounter any issue with this, we will be happy to help.