Re: HTML encoding in URLs

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 14184
interpreted = N
texte = Okay, send me the page and I'll fix it for you ... :)>Kenneth Grome wrote: > >> WebCat developers can always put their searches into contexts >> instead, then this problem won't be a problem anymore. In other >> words, instead of doing searches directly from URL's, pass the search >> values to the results page, and use a search context on the results >> page to do your search. >> >> >> >> search >> >> >> >> [search db=xxx.db&eqfield1datarq=valueA&nefield2datarq=valueB] >> [founditems] >> [/founditems] >> [/search] > >I've done that, but now I have a problem showing the next results. The >search finds 18 items. The results page shows 3 at a time, and there are >links to the next items, but when I click on the links, the new results >page merely says 0 items found. > >I've tried every concievable method I can think of, and the search data >seems to be formulated correctly when I check the web page log, but >obviously I'm missing something. > >The page html is available if you wish. > >Chris Gursche >EC&T Electronic Colour & Type Corp Sincerely, Ken Grome WebDNA Solutions 808-737-6499 http://www.smithmicro.com/webdnasolutions/. Associated Messages, from the most recent to the oldest:

    
  1. Re: HTML encoding in URLs (Kenneth Grome 1997)
  2. Re: HTML encoding in URLs (Chris Gursche 1997)
  3. Re: HTML encoding in URLs (Grant Hulbert 1997)
  4. Re: HTML encoding in URLs (Thomas Wedderburn-Bisshop 1997)
  5. Re: HTML encoding in URLs (Grant Hulbert 1997)
  6. Re: HTML encoding in URLs (Kenneth Grome 1997)
  7. Fwd: Re: HTML encoding in URLs (Thomas Wedderburn-Bisshop 1997)
  8. HTML encoding in URLs (Thomas Wedderburn-Bisshop 1997)
Okay, send me the page and I'll fix it for you ... :)>Kenneth Grome wrote: > >> WebCat developers can always put their searches into contexts >> instead, then this problem won't be a problem anymore. In other >> words, instead of doing searches directly from URL's, pass the search >> values to the results page, and use a search context on the results >> page to do your search. >> >> >> >> search >> >> >> >> [search db=xxx.db&eqfield1datarq=valueA&nefield2datarq=valueB] >> [founditems] >> [/founditems] >> [/search] > >I've done that, but now I have a problem showing the next results. The >search finds 18 items. The results page shows 3 at a time, and there are >links to the next items, but when I click on the links, the new results >page merely says 0 items found. > >I've tried every concievable method I can think of, and the search data >seems to be formulated correctly when I check the web page log, but >obviously I'm missing something. > >The page html is available if you wish. > >Chris Gursche >EC&T Electronic Colour & Type Corp Sincerely, Ken Grome WebDNA Solutions 808-737-6499 http://www.smithmicro.com/webdnasolutions/. 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:

WCS Newbie question (1997) [WebDNA] WebDNA7 and mod_fcgi (2013) Test (2000) quantity limit (1998) Summing fields (1997) [WebDNA] inputed text getting scrambled up in DB (2012) WebCatalog/Mac 2.1b2 New Features (1997) Credit card processing - UK (1997) Moment of Thanks (1997) Announce: WebMerchant 3.0 for Windows shipping now (1998) Search wbrk (repost) (2001) Not really WebCat (1997) New public beta available (1997) WebCat2: Items xx to xx shown, etc. (1997) [WebDNA] MacOS 10.5 instal/config. I'm drowning. ...just needs to work for LOCAL one person (2008) FAX orders (1996) My web page only... (2003) Building Calendars (1997) WC2f3 (1997) Location of Browser Info.txt file (1997)