SimO <[email protected]> writes: > Ross Patterson wrote: >> SimO <[email protected]> writes: >> >> >>> i.e: I set a range 0:100 and it shows me 5 items. If I put in the >>> portlet a second value of 80, instead of showing me 4 items it shows >>> NO items and worst, even if a re-insert 100 in the second value >>> nothing happens and I have to reload the page to get my items. The >>> weird thing is that if I set 0:80 trough the criteria tab it works >>> fine and it shows me 4 items. >>> >> >> Sounds like there's a bug in the integer range criterion. I've added >> this to the TODO: >> >> http://dev.plone.org/collective/changeset/82270> >> I'll get to fixing it as soon as I can. >> >> Thanks for the bug report! >> Ross > Hi Ross, > > thanks to you for this useful product. BTW I think there's a second bug :) > > When you look at the "Criteria type" list you see TWO items for setting: > > Integer value or range > Integer value or range > List of values > List of values > Select values from list > Select values from list > > I found that for every couple the first is gives you the base setting > without the "Form fields" section, thus not allowing you to show the > field in the search. The second is the right one.
This is because the ATCT non-form criteria exist along side the collective.formcriteria criteria to preserve compatibility for previously existing topics and criteria. In the default installation of collective.formcriteria, however, the JavaScript should narrow the list down to just the collective.formcriteria version of the crtierion when you select the field to use. Can you please check if this works for you? If it does, then I don't think this is a bug. One could argue that collective.formcriteria should use different text for these descriptions but then when you looked at the JS narrowed list, you'd see only options with the different text. And since form criteria don't *have* to appear on the form, appending "(form)" or some such might be just as misleading. If someone has a suggestion that can resolve this, I'm all ears. :) The root of this problem is whether to outright replace the ATCT criteria or preserve compatibility with ATCT topics and criteria. I opted for compatibility. Ross _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
