I'm trying to create an exposed filter that would search within the range of 2 cck fields (both are set as decimal; one is called "minimum size" and other is "maximum size") user types in a SINGLE value which would show the results of any node that is in the range of the "minimum size" and "maximum size".
Basically, I'm doing a compatibility search.
I need to search within the compatible size range.
So the range is as follows: "minimum size" and "maximum size"
("minimum size" is it's own CCK field (decimal), and so is "Maximum size")
The user would input a SINGLE value of whatever size they have and it will search within the above range.
i.e. has to be equal or greater than the min size and equal or less than the max size
Example:
Product Alpha has Compatible Range of 1.2in(min) - 1.5in(max)
Product Delta has Compatible Range of 1.6in(min) - 1.7(max)
User types in a single value: 1.4
Product Alpha should be displayed.
Other info:
I'm using 3 CCK fields that work in this calculation:
- the exact dimension (type: decimal)
- the lowest compatible dimension (computed field that adds -5% to the exact dimension; type: decimal)
- the highest compatible dimension (computed field that adds +5% to the exact dimension; type: decimal)
Comments
Comment #2
sorensong commented+1 I'm also very interested in a solution to this problem.
Comment #3
kars-t commentedDear fellow Drupal enthusiasts,
this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not pose the problem comprehensible.
But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.
Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.
Help can also be found for it on IRC and in the user groups.
In order this issue no longer remains, I put this issue to "fixed".
If there is new information, please re-open the issue.
Comment #4.0
(not verified) commentedadded more relevant data.