I understand.
The issue is, the ShortCodes are as it is visible, broken.
They are not using the correct apostrophes/quotes.
Also the setup is very intricate with conditions, which makes it impossible to be sure what is faulty, and what not.
In such cases one needs to take apart the single items.
So for example, create a View in a very minimal and unconditional state, to see if that works, then proceed to more complex setups, and so forwards until the issue is found.
I understand you have the post type "In Action" (hidden link), and use instead of the provided Toolset Address Field (and others) and ACF provided solution.
If those Fields are simple fields, that should not be a big issue, however remember that only Toolset registered fields work with full features in Searches, for example creating selectable lists with other field types may fail, if they are not registered by Toolset.
It should not affect this particular aspect, however.
I took a look at the addresses you have and there seems to be only one cached right now:
34 Poniu Circle, Wailuku, HI, USA 20.8780099 -156.502369
So that means you need to load one by one the page again (it will cache each time 10 addresses, that is the limit of Google).
Then, all the addresses will appear on any map you use, and not before.
So if you have 300 addresses, you will need to load that page 30 times under circumstances until all addresses are cached.
That is how google works, it's not due to Toolset.
Now, as I mentioned you also have uncached addresses, as it states in the dashboard, and it does not seem to be converted, as it still expects to do that hidden link:
You've got some address data cached. Convert it to a new, more efficient format to gain significant performance benefits.
==> Convert cache
This is for the new way of Toolset to store the addresses, but I fear this will only work with Toolset registered address fields, I am honestly not sure about that, and will need to ask the developer on Tuesday.
To proceed for now, I left that as is and created a View, where I query the Post Type "In Action" and display a map with the markers using the lat and long fields of the "non toolset fields".
The problem is it offers me a "lat " field (with spaces), one "lat", then additionally one "_ lat" and one "_lat".
In ACF however I see only a "lat": hidden link
Same for lng.
So which one it is, that is a problem, that Toolset Views will not be able to solve.
You would need to make sure to have only ONE field of that exact slug and that field must be the one saved for all those posts.
If you created and deleted fields, (at least with Toolset) you should remove them from the database (in Toolset you can do that with a WordPress backend command). With ACF I am not sure.
The case is that there are each more than one such field and Views will not know which to get.
I decided arbitrarily to use [wpv-post-field name='lat'] and [wpv-post-field name='lng']
Initially I thought they seem to work:
hidden link
But do you see the Lat and Long output there?
It is for each post:
47.556446, 47.556446/7.586509, 7.586509
But I only added [wpv-post-field name='lat']/[wpv-post-field name='lng'] to my loop, so I expect only 47.556446/7.586509
The ACF field does something unexpected here, and that can not work with a map - it is not a valid Lat and long value.
When I output the underscores variant (_lat and _lng), I get values like
field_5a0efe883e001, field_5a0efe883e001/field_5a0efe933e002, field_5a0efe933e002
So here we get the Field ID of ACF.
Then, when I output the ones with spaces, I get nothing.
So it seems that the only fields returning a valid return for each the value twice, comma separated:
47.556446, 47.556446 and then 7.586509, 7.586509
And logically that is because there are 2 "lat" and 2 "lng" fields registered, probably in the database only, since they are not visible in ACF's admin, but Views gets them in the Loop Editor GUI.
What am I missing here?
The field indeed seems to simply output a doubled value, which will not work for the purpose you want to use it.
But why would it do that?
Do you have any other method to display those ACF fields? Maybe we can use a Custom Shortcode instead, to see if that works for now?
One could use a get_post_meta() inside a ShortCode, for example.
// [acf-fields field="field-slug"]
function ts_get_fields( $atts ) {
$post_id = do_shortcode("[wpv-post-id]");
$a = shortcode_atts( array(
'field' => '',
), $atts );
$field_value = get_post_meta($post_id,$a['field'], true );
return $field_value ;
}
add_shortcode( 'acf-fields', 'ts_get_fields' );
Something like above could work.
However, first I'd like to hear your opinion on the doubled output, I feel I miss something important.
