Currently, Views does not upport this kind of filtering GUIs for ranges. As you might know, we do have a filter mode that lets you select a maximum and a minimum pair of values, and then apply the filter within the range. But we do not offer the option to display such controls as a range slider, at least yet.
We do have an internal ticket to add support for this in the future, but I can not offer an ETA on this right now.
Regarding the option to "select all" or "select none", I am not sure I follow the first case. Can you elaborate on what you want to select when you select all? For the case of selecting none, our frontend search forms can include a Reset button that basically does that: unselects any selected option. I think it should work for you.
Let's assume that you have a custom field that you want to filter by, and offer to filter by minimum/maximum value for that field. You should do the following:
- Head to the Search and Pagination editor of the View, and click on the Add new filter button. Select the field that you want to filter by.
- Select the kind of frontend selector that you want to use. I strongly recommend to use select dropdowns or radio buttons for ths.
- Select to use a between comparison. This will make sure that two different controls are created for you, one for the minimum value and another for the maximum value. Set the comparison mode to numeric, since thts is what a between comparison will expect.
- Now, the controls will be generated with steps that will cover the existing field values, which might not be what you want. Because of that, I also recommend selecting the option to use manually entered values, and include as many step values as you want. Using an empty value will set no value at all. In the minimum value selectr, that means to not apply any minimum at all. The same for the maximum value: an empty value means "do not apply a maximum limit".
That should be all. After inserting the filter, everything shoudl work as expected.
Well, in theory you can use a text input as frontend control, and this was visitors will be able to set their own minimum and maximum values to filter by. However, this might not be very intuitive since they have no reference on what values might look like. But in theory this shoudl also work.
Custom controls inside Views forms are not something that can be done easily, even less explained in a support ticket. The Views filtering mechanism is a complex ngine that combines markup with events listeners with AJAX calls back to the server, and complex operations being managed to run the right query.
In other words, we do not have an API to add custom controls. If you need a specific new filter, please share it here and we can take it as a feature request. As I already mentioned, the ability to use a slider to set maximum and minimum values for a given field is already in our roadmap, without release time estimation.
Please let me know if I can help you with anythign else.
It is highly discouraged to modify core files form plugins to add or remove functionality, as it will get lost when applying an update. In any case, providing code support for manipulating the plugin codebase is far beyond the purpose of this support forum.
I could point you to our Toolset Contractors for some personal and dedicated code work, but as I said there is no API for adding custom controls to our search forms, and I am sure our contractors will not suggest nor provide custom hacking of core codebase for the plugins.
Please let me know if I can help you with something else.
Dear juna,
i know code will get loss and ill do preventive measures while updating it. Theis plugin is solve my requirement without these modifications.
i would really appreciate if u you please guide me how to add button or link or any other price band option so that i can be able to continue development .
JUAN
i am still waiting to hear on this its 7 hours + past
the plugin is not much of a requirement if i am not able to implement these . and i might have to cancel license.
and credit will go to you for making be put a refund clame.
Unfortunately, as I stated above, support does not cover custom code guidelines nor plugin codebase hacking. Even if it did, the things that you are requesting are way too complex for a suppor forum explanation and would require probably a number of days to accomplish along with another number of days for testing.
I will be really sorry if our plugins do not meet your requirements in their current status and with the features they pack.
Please let me know if I can help you with anything else.
I am sorry that you feel this way. As I stated above, the request that you are making would demand several days of work for coding and other amount of days for testing, and it would span for a large number of files to modify. In addition, the whole system is being reviewed and will continue to get modifications soon both in files, code and assets, so any change would get broken in our next major release for sure, starting a circle of requests for code guidance, which is not covered by the policy of this support forum.
The frontend search mechanism in Views is a delicate feature and modifying it is not simple at all.
We offer an API to extend Toolset when it does not cover someone's needs. We take feature requests and we extend our APIs on demand. But when our API is not enough, we will never recommend or give assistance on how to modify core plugin files. I am sorry, but that is a fact that is not going to change.
