Kyle Phillips

1) There is currently only one input available… you can label it however you’d like, but I’d recommend keeping it “Location”. There are logical issues with distance/radius search, Geocoding locations, and results that I plan on writing about on the plugin site when I get a chance.

2) Maps can’t be turned off. This would violate Google’s API terms (the maps API is used to geocode locations entered, and based on their API terms, a Google map must be displayed if you’re using their data). You could hide them via CSS, but again, you’re technically breaking Google’s Map API terms at that point. See the Google API FAQs for more information.

3) The results are listed in order of distance from the location entered in the search. Currently, there’s no way to reorder that list. If you’re just looking for an alpha list of all locations, you could setup your own loop and query the location post type (or if you’ve changed the post type to your own, query that).

When importing, if you have your fields split into address_one and address_two, it’ll combine those when geocoding and save them separately as WP meta fields.

The full_address is for when you might have a large CSV file with a single column that contains the full address.

If possible, it’s better to use the split fields (address_one, address_two, city, etc…).

Marking this reaolved, since Nested pages now includes its own cloning feature.

Calls to admin-ajax are only made after the initial page load is complete.

There is one call after page load, which updates all the button statuses and lists.

This is to get around issues inherent to cached pages. If page cache is enabled (whether through a plugin like w3 total cache or through a managed host like WP Engine), and this call isn’t made, the favorites displayed are going to be incorrect. The AJAX call fetches the correct favorites/lists and replaces the cached version, which fixes this issue.

The only other call is when a user actually favorites an item.

I know it’s been a while, but believe I have this issue fixed.

If either of you (or anyone else) is willing to test this fix before I release it here, shoot me a message with your email using the contact form on the plugin site, and I’ll send you a patched version:

https://nestedpages.com/

This will be included in the next release.

The confirmation will appear for link items since those are permanently deleted (not trashed).

It will not appear for normal pages/posts, since that’s the normal WP behavior for trashing posts.

If you have page caching enabled, make sure to clear that. The update adds a data attribute to the HTML that is required by the AJAX call.

Is the CSV something you could share?

You can contact me via email on the plugin website (form at the bottom of the page).

https://locatewp.com/