I have a map view with search by distance. See screenshot.
1. Padding settings for the block don't seem to move the inputs away from each other, so the enter box for the number of miles is sitting right on top of the mi/km selector.
2. I don't want to give them the option of miles or km. I have Miles selected in the block settings so why is it giving the miles/km selection? I want that hidden/to not display as a choice.
3. I want the control the width of the input box where they put in the number of miles. It's currently 100% of the block width which looks weird. I want to limit to say 5 characters.
Thanks in advance.
And why is it stacking rather than being horizontal?
In your example in documentation here
https://toolset.com/course-lesson/filtering-and-ordering-map-markers-by-distance/
It shows it all being on one line. But on my search page, it stacks the mile number input, miles/km drop down, location entry box and use my location button. How do I get them to all be on one line?
Thanks
Hi,
To troubleshoot and suggest the next steps, I'll need to see how these search fields are currently set up.
Can you please share temporary admin login details, along with the link to the page with this view?
Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.
regards,
Waqar
Thank you for sharing the access details.
Just wanted to let you know that I'm working on this and will share an update with you within the next few hours.
Thank you for waiting, while I performed some testing on my website with a distance search filter in the view.
The screenshot from the documentation that you referred to is from the older legacy version of the views. When using the blocks-based views, the set of distance search fields are shown stacked on top of each other, as they are on your website.
I noticed that the page and the view that you mentioned in the earlier message were deleted, but found the distance search on the page '{removed}'.
Because the fields included in the distance group are added through a single block and not individually, they can be shown inline, only through custom CSS code:
@media (min-width: 769px) {
.wp-block-toolset-views-custom-search-filter span.wpv-custom-search-filter__input .form-group {
display: block !important;
margin: 5px 0px 15px;
}
.wp-block-toolset-views-custom-search-filter span.wpv-custom-search-filter__input .form-group > * {
display: inline-block !important;
width: 20% !important;
margin-right: 5px;
margin-left: 5px;
}
.wp-block-toolset-views-custom-search-filter span.wpv-custom-search-filter__input .form-group > input[name=toolset_maps_distance_radius] {
width: 10% !important;
}
.wp-block-toolset-views-custom-search-filter span.wpv-custom-search-filter__input .form-group > input[name=toolset_maps_distance_center] {
width: 40% !important;
}
}
@media (max-width: 768px) {
.wp-block-toolset-views-custom-search-filter span.wpv-custom-search-filter__input .form-group {
display: block !important;
}
.wp-block-toolset-views-custom-search-filter span.wpv-custom-search-filter__input .form-group > * {
display: block !important;
margin: 5px 0px 15px;
}
}
.wp-block-toolset-views-custom-search-filter span.wpv-custom-search-filter__input .form-group > select[name=toolset_maps_distance_unit] {
display: none !important;
}
I've included this in the '{removed}' view's custom CSS field and the distance fields are now inline and the unit field is also hidden.
( screenshot: hidden link )
Thanks for looking at this.
Why would I be using old views? It's udpated on my site and only just recently installed it. Does it have something to do with that checkbox one of you guys had me check that says something about Legacy editor? Can I uncheck that and get current views?
I definitely don't want to have to use custom code to make search by distance map work. Search by distance is the main reason I got Toolset in the first place, so....let's make sure that I'm using the current version of it.
Why is it using the old one and how do I get it to use the current version please?
Thanks
Please see screenshot. Is this why I'm seeing legacy views? I've changed it back to blocks. I forget why but there was something one of you guys said I needed to check that for but then I think I was supposed to put it back and forgot to. So now "blocks" is checked again.
Thanks for writing back.
There are two ways to work with the views:
1. The classic editor, which uses HTML code and shortcodes to generate the output.
2. The blocks editor, which uses the blocks in the Gutenberg (blocks-based) environment.
Before the Gutenberg editor was introduced by WordPress, the classic editor was the default and only option. But now, users can choose between the two, based on personal preference.
( using the 'Editing Experience' option that you showed in your screenshot )
The custom CSS code from my last message is not needed to make the distance-based search work. It will work just fine, even without it. However, since you'd like to visually design the distance search fields so that they show up in a single line, that will require custom CSS code, as this design can't be accomplished through the available design options in the block's settings.
There are other issues on that page as well.
Please see the private reply.
In this support ticket, we've now discussed two different pages:
1. {removed}
2. {removed}
Also, some of the comments from the private reply, no longer seem relevant as the pages have been remade, since then.
Can you please share the specific details about the page that we need to focus on and about what are the remaining challenges? I'll be in a better position to guide you with the next steps, accordingly.
Hi Waqar,
See private reply please.
As requested I've removed the specific term page names from this support thread.
The admin access details are no longer working and the website is behind a coming soon page, so I understand you've started working on the rebuilding.
Sorry to learn that your experience using maps and distance-based search wasn't pleasant. But, we're here to help and if you have any further questions or challenges, please do let us know.
To avoid any further confusion caused by multiple threads, I recommend starting a new ticket so that we can start a fresh and focused conversation.