It's not very easy for me to see what the issue is based on the above.
Can I take a look at your site to see the set-up directly?
I will mark your next reply as private so that I can get log-in credentials from you—you may want to create a temporary admin user for me to use that you can later delete. And be sure to have a current backup of your site.
Can you confirm the View affected and the page you have added it to?
I just stumbled upon the solution. I would still like your feedback though.
I took one last look at the address field in the post, and for whatever reason, I decided to grab the marker, and move it slightly on the map.
The address field lit up green as though it was save, and then the markers started showing up.
FYI, I am not putting addresses in, I am just putting locations in different Countries (Africa, Guatamala, India, Africa, etc.) ...
Is there something special I have to do to lock the address/location in once I put it in the address field? There is no save button, so I just assumed it would lock itself in when I pushed publish/update on the post.
If I drag and drop the marker in the address field slightly, and press "update" the marker shows up on the map.
If I move the marker slightly, and then press the "use this address" button under the map in the address field, and then press "update", the marker disappears.
It seems that your system doesn't like non-latitude and longitude entries, such as physical address, or a city, state combination.
What is supposed to happen is that you add an address custom field to a post, and when editing that post enter an address in the field. It will auto-fill the address as you start typing and you accept one of the addresses that Google recommends. Then when you save the post the address is stored in the post meta, and the corresponding lat/lon coordinates for that address are stored elsewhere by Views.
The key part is accepting the address Google suggests, which means it will then retrieve the corresponding coordinates. When you type a place, such as a country, are you accepting the auto-fill recommendation from Google?
Yes, I click on the suggestion, and update, but the marker does not show up until I move the marker slightly (and the top address field is filled with exact coordinates) ...
If I try to move the marker, and then click the "use this address" button, it also doesn't work.
The only way the marker stays on the map from my view is if I move the marker, and then press update.
Sorry for the delay getting back to you, yesterday was a public holiday.
I've just been testing the address field in the manner you describe, saving countries such as "India" or "China" using the auto-suggestion, and I didn't experience any problems, the addresses are saved.
You say you already tried switching theme and disabling plugins.
Can I get a copy of your site to test locally?
I'll mark your next reply as private so you can share the URL of a site duplicate (https://toolset.com/faq/provide-supporters-copy-site/) or, if you prefer, let me have site credentials and I will take a copy from your site myself. Be sure to have a current backup first.
I went to look at a Missions post and saw that rather than an address (or country) the address fields were all coordinate pairs (presumably resulting from you manually adjusting the markers).
The adjacent maps were not displaying because of restrictions from your API key, so I replaced that with an unrestricted key.
I then went through the 8 Mission posts and updated the address fields with country names, as shown in one of the attached screenshots.
I then looked at the map page, and all 8 markers displayed correctly.
In short, I couldn't reproduce the problem.
The only material difference between your version of the site and mine is the API key, you might want to try removing the restrictions on your key for testing to see if that is the root of the problem.
I think every maps question I have dealt with has always been resolved by fixing the settings for the API key. I didn't think that was going to be the case from your description, but it looks like it might be.
It seems that the Maps for Views plugin has an issue when you restrict the API key to the domains you are using.
The fact that I wouldn't be able to use the Google API domain restrictions is a bug in my opinion. If someone wanted to use your API key, the domain restriction is the only thing stopping them from sticking you with a pretty nasty bill for all the data they stole.
Basically, with restrictions, the map does not lock in the markers. Without restrictions it does.
You mentioned that you used an unrestricted API key. This might be why you couldn't reproduce the issue.
Can you lock your API key down using your local website url, so you can confirm?
