Re: ShowNext for method=POST
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 14361
interpreted = N
texte = I am using this in an embedded search because my search page merely collects all the variables in a form and they are cobbled together on the results page. This was Marc Eagle's recommendation, and it works well for the initial search.So I cut and pasted your code out of your email into my document. At first, nothing. Then I removed all of the quotations save the ones on the value of the submit button, and behold, I have show next buttons.I press the button, the result is the returned results.tmpl with 0 item(s) found. I look at the webstar log and find that the request begins with max=%5max%5 so I hard code the value for max as 3, which is not so bad since I have hard coded it into my initial search parameters anyway.Try again, still the results 0 item(s) found. The requested information being passed, as cut out of the webstar log ismax=3&db=aliveBooksv1.db&cart=296144159722&woTitledata=allerg&startAt=4the URL requested ishttp://207.102.129.250/webcatalog/yoursite/v4alivebooksv1Results.tmpl$SearchThe browser is Netscape Gold 3.01. I am running webstar on the same machine that I am browsing on. I have upgraded to the latest version of Webcatalog, and am using the plugin. Help!Grant Hulbert wrote: > > >As far as I can tell, I have followed the latest example to a tee. But > >then again, perhaps I am missing something. > > First, remember that this is for $Search actions, and *NOT* embedded searches. I haven't verified the best way for embedded searches to work yet. > > Why do you keep putting all those hidden variables in there? My examples do no such thing, because [SearchString] does it for you. The problem here is that you're trying to do too much -- just sit back and let WebCatalog do the work. The purpose of [SearchString] is to *AUTOMATICALLY* build up all the hidden form variables *FOR YOU*, because WebCatalog knows exactly what values it needs for each of those ShowNext Links. > > Also, your
> >[/shownext] > > ...and here's what it should be: > > [shownext position=begin&method=POST] >
> [/ShowNext] > > The max=[max] thing is because of a bug in the POST version of ShowNext; you will be able to take that out in the next version of WebCatalog. It is not necessary for method=GET. >
Associated Messages, from the most recent to the oldest:
I am using this in an embedded search because my search page merely collects all the variables in a form and they are cobbled together on the results page. This was Marc Eagle's recommendation, and it works well for the initial search.So I cut and pasted your code out of your email into my document. At first, nothing. Then I removed all of the quotations save the ones on the value of the submit button, and behold, I have show next buttons.I press the button, the result is the returned results.tmpl with 0 item(s) found. I look at the webstar log and find that the request begins with max=%5max%5 so I hard code the value for max as 3, which is not so bad since I have hard coded it into my initial search parameters anyway.Try again, still the results 0 item(s) found. The requested information being passed, as cut out of the webstar log ismax=3&db=aliveBooksv1.db&cart=296144159722&woTitledata=allerg&startAt=4the URL requested ishttp://207.102.129.250/webcatalog/yoursite/v4alivebooksv1Results.tmpl$SearchThe browser is Netscape Gold 3.01. I am running webstar on the same machine that I am browsing on. I have upgraded to the latest version of Webcatalog, and am using the plugin. Help!Grant Hulbert wrote: > > >As far as I can tell, I have followed the latest example to a tee. But > >then again, perhaps I am missing something. > > First, remember that this is for $Search actions, and *NOT* embedded searches. I haven't verified the best way for embedded searches to work yet. > > Why do you keep putting all those hidden variables in there? My examples do no such thing, because [SearchString] does it for you. The problem here is that you're trying to do too much -- just sit back and let WebCatalog do the work. The purpose of [SearchString] is to *AUTOMATICALLY* build up all the hidden form variables *FOR YOU*, because WebCatalog knows exactly what values it needs for each of those ShowNext Links. > > Also, your
> >[/shownext] > > ...and here's what it should be: > > [shownext position=begin&method=POST] >
> [/ShowNext] > > The max=[max] thing is because of a bug in the POST version of ShowNext; you will be able to take that out in the next version of WebCatalog. It is not necessary for method=GET. >
Chris Gursche
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:
RePost: AutoReload? RequireComment? InterpretAll? (1999)
Another question (1997)
This list needs a digest: rant, rave... (1997)
can WC render sites out? (1997)
PIXO (1997)
Sorry WebDNA server not running ????? (2002)
ssl/empty cart problem (2003)
[SearchString] usage (1997)
RE: Major Security Hole IIS NT (1998)
Encrypt and Commit Me (1998)
Re:[ShowIf] and empty fields (1997)
[WebDNA] lighttpd problem with returnraw http header (2018)
Help!!!! (1997)
A quickie question (1997)
Superfilous Characters (1998)
'does not contain' operator needed ... (1997)
Summary Searches (2000)
WebCat2b13MacPlugIn - [include] (1997)
searching for items that begin with a number (2004)
A question about security (1998)