Howdy,
Thanks for your continued support and development of this rather excellent module :)
I've encountered a strange issue today and I can't quite work out what's going on. I've added an exposed filter using search_api_location, but when I try to place the exposed filter in a MEFIB block, the query string it generates is invalid.
Putting the filter back into the 'default' block works normally.
Here is an example of the two strings:
Default (Works)
?search_api_views_fulltext=&field_geo_locator_latlon_op=5&field_geo_locator_latlon=london&items_per_page=10
MEFIB (Fails)
?mefibs-form-location-search_api_views_fulltext=&mefibs-form-location-field_geo_locator_latlon_op=5&mefibs-form-location-field_geo_locator_latlon=london&mefibs-form-location-items_per_page=10&mefibs-form-location-mefibs_block_id=location
I'm completely baffled as to what is going on here. The MEFIB one does include the 'field_geo_locator_latlon=london' parameter, and the search box has the value set, but the 'field_geo_locator_latlon_op=5' is unset.
Comments
Comment #2
dinis commentedComment #3
hmdnawaz commentedI have the same issue. Does any one solved this problem?
Comment #4
hmdnawaz commentedComment #5
Sylense commentedI just encountered the same problem. No clue what is causing the issue.
Comment #6
Manmohan commentedCommenting out mefibs_set_form_id_recursive($form, mefibs_get_element_name_prefix($block_id)); amd mefibs_set_element_name_recursive($form, mefibs_get_element_name_prefix($block_id)); function on line 718 and 719 fixed the problem for me . It was creating the different form elemet ids for search and sort . and both option were not working together.