Re: shownext problems
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 18513
interpreted = N
texte = >>>Okay then. I have a search context on a page using values passed from a >>>form on the preceding page. Inside the search context is a shownext >>>context. It displays the correct text for the links to the next found >>>items, but the links don't find anything (the right page comes up, but >>>there are no found items anymore, and I don't get any kind of error >>>message). > >>When WebCat sees a [search] context it does the search automatically. >>Therefore you can take out the 'command=search&' string and it will work just >>fine. Try this instead: >> >>[shownext position=begin] >>
[start]-[end] >>[/shownext] > >No, that also returns a page with zero found items.Personally I *never* use the [searchstring] tag now that I have adopted the policy of always using [search] contexts ... so you might have to write your own search string instead of using that tag ... :)Please post either the form or the URL you're using to get to this results page, so I can see what values are being sent to this page from the previous page. Then post the search context that appears on this page. I'll take a look at it and let you know what's up.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Associated Messages, from the most recent to the oldest:
>>>Okay then. I have a search context on a page using values passed from a >>>form on the preceding page. Inside the search context is a shownext >>>context. It displays the correct text for the links to the next found >>>items, but the links don't find anything (the right page comes up, but >>>there are no found items anymore, and I don't get any kind of error >>>message). > >>When WebCat sees a
[search] context it does the search automatically. >>Therefore you can take out the 'command=search&' string and it will work just >>fine. Try this instead: >> >>[shownext position=begin] >>
[start]-[end] >>[/shownext] > >No, that also returns a page with zero found items.Personally I *never* use the [searchstring] tag now that I have adopted the policy of always using [search] contexts ... so you might have to write your own search string instead of using that tag ... :)Please post either the form or the URL you're using to get to this results page, so I can see what values are being sent to this page from the previous page. Then post the search context that appears on this page. I'll take a look at it and let you know what's up.Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
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...
Related Readings:
Context and commands (1998)
Just testing (2003)
NT b19 sends extra MIME headers (1997)
Concatenating Form Variables (1998)
Total found of each unique field (2003)
Multiple catalog databases and showcart (1997)
shipcost (1997)
default value from Lookup (was Grant, please help me) (1997)
Q: for those who use Cookies for sessions? (2004)
ListFiles (1998)
Copyright ? (1997)
RE: protect tag on NT (1997)
Sort Order on a page search (1997)
credit card authorization question (1997)
OT: WebDNA and LINUX (2004)
WebSTAR and WebSTAR/SSL with WebCatalog plugins (1998)
More news on 5.0 (2003)
Exclamation point (1997)
PayPal WebMerchant Templates (2006)
rules for .tpl only in certain domains... (2000)