numero = 10366
interpreted = N
texte = To leave this talk list send an email to macjordomo@smithmicro.com with BODY unsubscribe WebDNA-Talk ---------------------------------- >> I haven't looked in the code, but I can see how this might be a problem >> (that can be fixed of course). I'm not sure how well our current code >> distiguishes between multiple parameters with the same name. I'll look into >> it and make sure it's fixed in the next beta if this is the problem. > >John, just so you know: Beta12 can't even *do* searches based on >multiple parameters with the same name--it only returns the matching >values from the first checkbox checked. Beta10 does the search >correctly, but creates the problem I described earlier.This is something new in the HTML docs:You may combine many search criteria into a single search command. To create a complex search, simply put all the search criteria into a single URL or HTML form. For example, to find all product Descriptions that contain either of the words Television or Stereo or both:Results.tmpl$search?woDescriptiondata=Television,Stereo&db=Products.db Gil and John, I think the portion of Gil's URL relating to the checkboxes on his form are still being written as individual search args because that portion of the code hasn't been changed yet. Gil's URL had this in it, and I don't think this is the proper format for version b12:cwresult.tmpl$search?db=catalog.txt&wotext1datarq=270&wotext1datarq=270Since WebCat2 creates these URLs itself by using the values from a search form, we probably have to wait for Grant to get back so he can rewrite that portion of the code ... unless Gil wants to try one of two techniques that might solve his problem right now ...Gil, you could try replacing your checkboxes temporarily with a scrolling list. Be sure to make multiple choices selectable in the list. If the code is updated for scrolling lists, that might work.The other solution might even be better, and that's to collect the data on the search form, but don't do the search from the sarch form. Instead, place all the form values into variables, then pass them to the results form. Next, place a [search] context in the results form, and use the variables to assemble the search parameters as shown in the HTML example I quoted from the HTML docs above.This would require minimal changes to your templates and you can keep using version b12 ... and it *should* work because you are actually writing the search string the way you want it, not the way WebCat2 seems to want to write it for you.>Does it have anything to do with the fact that these are text fields, >not number fields? And if so, is there anything I can do about that?WebCat2 assumes that all its fields are text fields unless you manually tell it to deal with certain fields as numbers or dates ... so I don't think that being a text field has anything to do with this problem.Sincerely, Ken
Associated Messages, from the most recent to the oldest:
To leave this Talk List send an email to macjordomo@smithmicro.com with BODY unsubscribe WebDNA-Talk ---------------------------------- >> I haven't looked in the code, but I can see how this might be a problem >> (that can be fixed of course). I'm not sure how well our current code >> distiguishes between multiple parameters with the same name. I'll look into >> it and make sure it's fixed in the next beta if this is the problem. > >John, just so you know: Beta12 can't even *do* searches based on >multiple parameters with the same name--it only returns the matching >values from the first checkbox checked. Beta10 does the search >correctly, but creates the problem I described earlier.This is something new in the HTML docs:You may combine many search criteria into a single search command. To create a complex search, simply put all the search criteria into a single URL or HTML form. For example, to find all product Descriptions that contain either of the words Television or Stereo or both:Results.tmpl$search?woDescriptiondata=Television,Stereo&db=Products.db Gil and John, I think the portion of Gil's URL relating to the checkboxes on his form are still being written as individual search args because that portion of the code hasn't been changed yet. Gil's URL had this in it, and I don't think this is the proper format for version b12:cwresult.tmpl$search?db=catalog.txt&wotext1datarq=270&wotext1datarq=270Since WebCat2 creates these URLs itself by using the values from a search form, we probably have to wait for Grant to get back so he can rewrite that portion of the code ... unless Gil wants to try one of two techniques that might solve his problem right now ...Gil, you could try replacing your checkboxes temporarily with a scrolling list. Be sure to make multiple choices selectable in the list. If the code is updated for scrolling lists, that might work.The other solution might even be better, and that's to collect the data on the search form, but don't do the search from the sarch form. Instead, place all the form values into variables, then pass them to the results form. Next, place a [search] context in the results form, and use the variables to assemble the search parameters as shown in the HTML example I quoted from the HTML docs above.This would require minimal changes to your templates and you can keep using version b12 ... and it *should* work because you are actually writing the search string the way you want it, not the way WebCat2 seems to want to write it for you.>Does it have anything to do with the fact that these are text fields, >not number fields? And if so, is there anything I can do about that?WebCat2 assumes that all its fields are text fields unless you manually tell it to deal with certain fields as numbers or dates ... so I don't think that being a text field has anything to do with this problem.Sincerely, Ken
Kenneth Grome
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...