Ross Patterson wrote:
SimO <[email protected]> writes:
Ross Patterson wrote:
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.
If 'default installation' means to put 'collective.formcriteria' in the
buildout -
as I think :) - then, yes, I did so and I got this problem.
But what happens to the criteria type pulldown *after* you've selected
the field?
Ok, its content change based on what you have set in
plone_control_panel/collection. Indeed, right there you can set the type
of criteria you want to show in the pulldown list so you can discard
"double items".
In the previous post you said 'appending "(form)" or some such might be
just as misleading.' but IMHO it will be *less* misleading than two
items with the same name. 'If someone has a suggestion that can resolve
this, I'm all ears. :) ' ... for instance, instead of append "(form)" or
"(search)" or whatever, you could append an "(*)" - only in the panel
widget, not in the pulldown list - and add a line to the description of
the panel such as:
"Configure which indices will be displayed while creating criteria for
Collections, and how they will be displayed.
Criteria type marked with (*) allows you to show the field in the
formcriteria's search portlet."
What do you think?
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
