Support

Dear Help Desk Team,

I’m experiencing several issues with the filter functionality on our site, and I’d appreciate your help in resolving them. We’ve integrated the filter on both the rental and purchase object pages (http://www.gww.freshfiles.de/kaufobjekte,http://www.gww.freshfiles.de/immobiliensuche), but errors are occurring on both. Below are some specific examples:

For instance, on the rental object page: http://www.gww.freshfiles.de/immobiliensuche

• When using the "Kaltmiete" filter, if I enter a price range (e.g., between 0 and 40), I’m required to input both a minimum and maximum value. Is there an option to allow input for just one value (either minimum or maximum) instead of both?
• After submitting the filter, the Kaltmiete value resets to 0, and the input I’ve entered for Kaltmiete appears in the Wohnfläche input field. I’m not sure what caused this issue, as the filter was working fine before. Could this be related to a setting within the filter configuration?
• Additionally, some Filter disappear after i entered a value in a input field. 

When the filter button is clicked and the overview of all available filters is displayed:

• Is it possible to have an option where users can fill out all their filter criteria and then submit them with one general submit button? It would also be helpful to have a general reset button for all input fields at once.

Lastly, somethimes there is a random error message, that the input has to be lower than 15. Do you know what causes this error message?

Thank you in advance for your support. I look forward to hearing from you.

Best regards,

Alisha

Hi,

let me add my debugging result for the following issue: > After submitting the filter, the Kaltmiete value resets to 0, and the input I've entered for Kaltmiete appears in the Wohnfläche input field

Both mentioned filters, Kaltmiete and Wohnfäche are range inputs. In media/mod_jfilters_filters/js/range_inputs.js, you are performing the following logic in the „boot" method:

* Iterate over each filter ("filterParams.forEach(fltr => {"

* Build filter config

* Get all filter wrappers ("const filterWrappers = [].slice.call(moduleElement.querySelectorAll('.jfilters-filter-range_inputs'));"

* Iterate over all wrappers and bind an event handler to the submit button, using the current filter config ("JFilters.range_inputs.update(config, values);!")

So, instead of binding the current filter config to the current submit button, you are binding the config of ALL filters to ALL submit buttons, which creates the unexpected result that my colleague describes.

We fixed it by limiting the querySelectorAll call for the wrappers to the wrapper of the current range input:

const filterWrappers = [].slice.call(moduleElement.querySelectorAll('#jfilters-filter-range_inputs-' + fltr.moduleId + '-' + fltr.id));

Looking forward to your feedback and a patched release!