Ale
Forum Replies Created
-
This was originally your thread. I was wondering if you were able to get in touch with your host. Note that in Photonic 2.45 I put in a small tweak to tell you what the error message is on the front-end. If you too are getting a timeout error (even with a high timeout set), it is certainly due to a configuration issue for your host to resolve.
Yes, I am getting a timeout error even with a long timeout set. The host says the following:
Yes, this is a server issue.
Google changed their SSL settings recently which we know already broke access to the ReCAPTCHA API. I wouldn’t be surprised if you’re running into the same issue now. This issue will be resolved next week with a PHP [and SSL library] upgrade.They didn’t specify any specific ETA about the resolution when asked. I have been waiting since.
If this doesn’t resolve the 401 error on the front-end, you will have to get in touch with your host to see if they have disabled any configuration, because after deleting the plugin from the WP dashboard and replacing it with a fresh install of the older version of the plugin, you are back at a state where you had the plugin working, so a plugin change wouldn’t have triggered the problem.
Unfortunately, the code patch did not work.
…you will have to get in touch with your host to see if they have disabled any configuration…
Can you suggest to me any general or specific queries or requests I should make to my web host, relevant to diagnosing this issue on their end?
For the “Obtain Token” step you will have to follow through the workaround entirely. Once you generate the tokens on Google’s site, you can save the tokens on Photonic’s settings page.
Like I’ve mentioned before (this will be the 3rd time I’m reiterating this), I already did what you’ve been suggesting and so without any result.
My point is, after storing the token you should not be seeing the 401 error on the front end.
I understand your point. However, the problem remains.
Long story short – I discovered a corner case wherein it might be possible to perpetually face this error. If you uninstall the plugin from your WP dashboard (first “Deactivate”, then “Delete” – don’t delete the plugin folder) and subsequently reinstall, this should go away. The downside is that your settings will be gone. Of course, if you don’t want to go through the pain of setting up the authentication again, just copy all the keys, secrets and tokens you currently have elsewhere and copy them back upon reinstallation.
I did a fresh install, as you suggest. And manually entered the google client id, client secret, & the refresh token (generated from ‘oauthplayground’ as shown in your workaround steps). The problem still persists.
And even after the fresh install, with regards to the attempt at regular authentication (Photonic > Authentication > Step1. Authenticate > Step2. Obtain Token), the authentication goes through with the consent, and then as I click the ‘Obtain Token’ button, the loading animation shows indefinitely.
The problem remains as before.
I will put a fix in place for this in the next version…
When will you release the next version?
…but I can give you the code change you may make to fix this, too.
Yes, could you give me the ‘code change’?
What happens if you switch to the last working version in your case, 2.34?…Are you still seeing the error with it?
I downgraded it but the problem still persists.
One other question, before you downgrade the version for checking: what PHP version are you on? Can you get to the a 7.x version if you are on 5.6.x? Does being on newer PHP versions resolve the issue for you?
I am running PHP v7.3