Aims
Forum Replies Created
-
Hi all,
I got mine resolved finally, so I hope this helps you if your problem is the same or similar:
Permission was restricted in the Google API dashboard for my Google Translate API app.
You should be able to edit the API key’s restrictions – access your https://console.cloud.google.com and either change the restrictions None or No Application Restrictions and Don’t Restrict key. Or if you’re concerned about others possibly accessing and using your API key, you can set to restrict by HTTP Referrers (web sites).
I did not want to leave the app unrestricted, so I added my domain to the HTTP referrer list. However, it did not work when I entered only mysite.org/* –– I had to enter https://www.mysite.org/* for it to work (I added both). Yours may be https://yoursite.com without the ‘www’ part (maybe add a few versions and retest).
I also had to set up OAuth for my Google app. I couldn’t use the “Internal” user type, so I set up the External user type, added myself as a test user, and then didn’t submit the app, but this worked in the end.
So hopefully those tips help if you are having the same problem with the Google Translate API key 403 error.
Same. Seems like a newly introduced bug in the TranslatePress plugin. Maybe Google changed something and TranslatePress needs to adjust its integration ?
- This reply was modified 3 years, 5 months ago by Aims.
Thank you.
Here is the link: https://drive.google.com/file/d/1QP5WRMipdUqyqFoDGtxbct8wisOKdSVq/view?usp=sharing
I got it!
It’s because the website is behind password protection at the moment while I’m developing. I lifted that password gate temporarily to test it and the images were displayed in the email (Gmail).
Thanks again for your help!
Thank you for your response!
I looked at the Gmail code and when I enter the Gmail src URL directly in the browser, it gives a 404 error.
I’ll see if I can find anything about this searching online, but might you have any suggestions? None of my other emails are doing this. Just those sent by BNFW on my site.
Thank you so much.
Amy
- This reply was modified 6 years, 2 months ago by Aims.
Ah, that totally makes sense. Thanks for the detail on that, Mikko! Helps for next time.
Thanks again for the fast response time, for the simple solution, and the plugin!
Much appreciated.
Amy
Thank you. That solved the problem. I appreciate your help and fast response.
One question though regarding your comment “When reporting problems like this, please explain how it’s not working. Just “it’s not working” doesn’t really tell me anything.”
I actually thought I did explain it in my support question. I provided a bunch of info I thought might help in knowing where the source of the problem might be and explained things the best I could while not knowing what was causing the issue.
So out of genuine curiosity, what could I have added that would have told you more in terms of explaining “how” it wasn’t working? So I know for next time in a forum.
Thanks again, Mikko.
Thank you.
Since you mentioned it was a memory limit or time out problem, I tried again today and it worked fine.
I’ll check with my hosting companies anyway.
Thanks again.