Address change issue #454
-
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 13 replies
-
Thank you for having tried disabling other plugins as that is a common source of issues. And I'm not sure yet we can rule that out in this case. The Gutenberg plugin has been known to cause issues with TSML. Is this problem occurring with all address changes (or new meetings)? Or, just this one meeting? I was able to geocode the address you provided on my dev site so I don't think we can point a finger at Google :-) What geocoder configuration are you using? If you're using the Legacy method, try our Beta API Gateway method. If you're using your own Google geocode key, check the settings for that through your Google account. Please open up a dev/debugging console and try geocoding the address again. Please note any errors, and try to address them. Another option is to go into another meeting and changes something other than the address, then click Update. This should rewrite the meeting list cache. That is a long shot imo, but worth trying. |
Beta Was this translation helpful? Give feedback.
-
Disabled all plugins except:12 Step Meeting List
Akismet Anti-Spam (Automatically managed)
Jetpack (Automatically managed)
Very unfamiliar with WordPress (or web building in general). Just another servant!Import is in there somewhere...
On Thursday, July 22, 2021, 09:08:35 PM PDT, Tech2Serve ***@***.***> wrote:
You can select the API Gateway through the Import & Settings page, lower down on the right hand side.
Did you disable the Gutenberg plugin and try again?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Beta Was this translation helpful? Give feedback.
-
Even though I know little about WordPress and/or web design, I know enough to agree about the cache.Note: Address removed and I tabbed out of the field to refresh...
The map remains to the old address. Perplexing.I enter the new address (auto fill with the new address is shown):
The map doesn't change, the publish button is greyed out and the console reads as follows:
If I had any idea how to switch to your API Gateway, I would. I am skilled at desktop publishing, graphic design, 3d cad, 3d animation and play one HELL of a game of Solitaire! I quit advancing my web skills when anything but html was used 30 years ago. Just another railroaded servant. Thanks for what you are doing!As you requested, I changed the address to an existing location (the local Alano Club) and everything worked perfectly. Go figure...
(bad language)......What the heck? I will see if anyone knows who our hosting platform provider is (I think it's GoDaddy) and see if the site cache can be cleared.
On Saturday, July 24, 2021, 08:41:56 AM PDT, Tech2Serve ***@***.***> wrote:
This is perplexing. I don't understand why Google is throwing the geocoding error of "REQUEST DENIED".
I may have missed your reply, but please confirm this is only happening to the one address? Or, are you unable to update any address?
The advantage of you switching to our API Gateway is that I can actually see the request being made to Google and can evaluate their response better.
My gut is still telling me something is interfering with the contents of the request for this address. Since disabling Gutenberg didn't help, I'm left with a potential cache issue.
When you try to update the meeting, make sure to remove the contents of Location before entering the new Address. Also, you can try putting some other address and update the meeting, then try putting in the correct new address and updating? Again, please watch the errors in your console and record them.
Also, please contact your hosting platform (or log into your cPanel/account page) and try to clear the website cache.
Please report back with answers to any questions or suggestions I've made. It really helps me to help you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Beta Was this translation helpful? Give feedback.
-
After discussion with the OP, we discovered his configuration for the geocoder had been changed to Google, but that his API key had not been authorized for geocoding. Changing his configuration to use the API Gateway resolved his geocoding issues. |
Beta Was this translation helpful? Give feedback.
After discussion with the OP, we discovered his configuration for the geocoder had been changed to Google, but that his API key had not been authorized for geocoding.
Changing his configuration to use the API Gateway resolved his geocoding issues.