Was this working earlier?
Recently another user from Poland said that he too was getting the same error, and his site was working earlier. I don’t know if this is a specific problem with some hosting providers in Poland, but can you check with your hosts if they are blocking outgoing HTTPS calls?
Who is your hosting provider?
That’s right, everything was fine before. I have been glad to use the plugin since July 2019.
Home.pl is my hosting provider.
I have succeeded now, but I don’t know how long. I uninstalled the application and reinstalled. I have cleared the Autoptimize plugin data. I have re-established the Google API connection.
Tell me, can the number of requests (or their exact limitations) affect the plug-in? Because I use the Photonic plugin to create photo galleries for articles from the life of a small town. Several hundred people visit the website daily and display photos. Should I fear this limited number of requests?
I have succeeded now, but I don’t know how long. I uninstalled the application and reinstalled. I have cleared the Autoptimize plugin data. I have re-established the Google API connection.
Considering that everything was working fine for the past 9 months, I will say that this isn’t really a Photonic problem. Basically the Google Photos API has not changed, and Photonic’s code to use the Google Photos API has not changed, so there should be no reason why this will suddenly stop working.
I am not sure if there is a setting in Autoptimize (or something else in your installation) that either causes caching of requests made from your site, or strips out some URL parameters. But from Photonic’s side, you shouldn’t even need to uninstall or reinstall the application (unless you have changed some plugin files this won’t make a difference). Redoing the authentication might help, but the probability is low.
Tell me, can the number of requests (or their exact limitations) affect the plug-in? Because I use the Photonic plugin to create photo galleries for articles from the life of a small town. Several hundred people visit the website daily and display photos. Should I fear this limited number of requests?
Every API key is given its own limit, and the limits are reasonably high. I think it used to be 10,000 API calls and 75,000 base URL calls per key per day, so unless you have very high traffic and lots of galleries, you shouldn’t see a problem. But, if you hit your limit, the error you get says something like “API quota exceeded”, not that the token is missing.
I am not sure if there is a setting in Autoptimize (or something else in your installation) that either causes caching of requests made from your site, or strips out some URL parameters.
No, AO only optimizes JS, CSS, HTML, Google Fonts & Images and all of that only on the front-end, not under /wp-admin/.
No, AO only optimizes JS, CSS, HTML, Google Fonts & Images and all of that only on the front-end, not under /wp-admin/.
Thanks. Here the impact is to the front-end, though, not wp-admin. Both, the front-end and the back-end calls add the access token to the Google Photos API URL. When viewed from the back-end there is no issue with calling Google Photos’ API, however, the front-end seems to complain that a parameter has been stripped out.
I understand, though, that this might not be happening from Autoptimize – my comment was simply in response to the point above, about clearing Autoptimize data.
