Empty search results deletes map

This support ticket is created 5 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

Tagged: Toolset Maps, Views plugin

This topic contains 3 replies, has 3 voices.

Last updated by smileBeda 5 years, 1 month ago.

Assisted by: Luo Yang.

Author

Posts

October 7, 2019 at 6:55 am #1356619

maxfieldB

I am trying to: avoid the map disappearing when there are no matching search results

Link to a page where the issue can be seen:
battstaging2.com

I expected to see:
avoid the map disappearing when there are no matching search results

Instead, I got:
The map disappears when there are no search results from a custom search

October 7, 2019 at 8:57 am #1356763

Luo Yang

Hello,

Please edit the post view(ID: 312) you mentioned above.

in section "Loop Editor", try to move the map shortcode [wpv-map-render] outside [wpv-items-found] ... [/wpv-items-found], and test again.

More help:
hidden link
Meta HTML wrapped in [wpv-items-found][/wpv-items-found] will be output if there are any posts | taxonomies | users returned by the View.

October 7, 2019 at 5:52 pm #1357317

maxfieldB

My issue is resolved now. Thank you!

March 17, 2021 at 9:33 am #1990233

smileBeda

This issue is not resolved, while moving the map outside the no items found is a logical resolution for when you put the Map in the loop editor, it is not when you want the search form appear after the map, in which case, the map can only be placed before the search form, and in that case, the issue as described here still happens.

Additionally the core issue only happens when you use AJAX.

Opened a new ticket for this, since the real reason for this is a error in the implementation of the map. The map, when there are no results, should still be instantiated - but without markers.