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.
Dieses Thema enthält 1 reply, hat 1 voice.
Zuletzt aktualisiert von vor 1 days, 16 hours.
Assistiert von: Christopher Amirian.
Hi Support
We have two Views find-a-native-nanny-search-and-results-view and find-a-job-search-and-results-view.
Lately on our dev site, when only ONE results is retrieved, the results View (which is split apart from the search controls) for Find a Job is getting squeezed. We don't see the same on our production site, and this used to work fine before. I have not made any changes to the view recently, other than a JavaScript addition for AJAX while searching for Location, kindly provided in ticket https://toolset.com/forums/topic/search-by-location-using-toolset-maps-no-longer-working-correctly/?paged=3.
Regarding the "squeezed" results page when only 1 result is being shown, it works correctly on our production site, so it appears that something was changed on the dev site (I'm not aware of any other changes made by me in recent months to that page/view). Normally both sites are configured identically and we have never noticed this problem before in the 5 or 6 years we have the site.
You can search for "Aschaffenburg, Germany" on production (URL below) to see that it CAN work. So we'd just like to understand why it is buggy on the dev site. It's curious, that it only happens with 1 result and not all result sets with 2+ records! - perhaps there's a clue there for the resolution?
PRODUCTION (working fine):
versteckter Link
Not sure how this can be since they should be identically configured, or if it is relevant, but the production URL has the extra arguments:
&wpv_orderby=modified
&wpv_order=desc
DEV (not working, results page is getting "squeezed" when only 1 result)
versteckter Link
(please note when the URL from dev is opened at first, it may show correctly. However if you click into the location field and search for "Aschaffenburg" again, the weird behaviour is observed. I cannot reproduce the weird behaviour on production, doing the same)
Location is our most important search criteria for our users, so this has to work correctly every time!
Kind regards
Simon
