Re: Help getting [shownext] to increment
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 47297
interpreted = N
texte = Kenneth Grome wrote: > John's almost right, except for two things: > > 1- The search context requires a startat parameter, not a start > parameter. > Yes, sorry, startat, not start.> 2- The value of the startat parameter must be a variable ... and the > value of that variable must be set inside the shownext context.Wrong! I don't know where Ken gets this stuff. The [searchstring] tag includes everything you need to continue your search. The startat parameter must be present in the original search and then it is available as part of the [searchstring] tag. There is no requirement that it be a variable, because _all_ form parameters are variables.> > By the way, if you stop messing around with the searchstring tag and > instead put all the required variables into your shownext URLs manually, > as I have demonstrated above, then you will probably begin to understand > what's going on when you click a shownext link.You'll also spend a lot of time writing non-portable code. [searchstring] does everything for you. With Ken's techniques, you cannot have a page be the target for multiple search variations and have the [searchstring] automatically do the right thing.> > Using the searchstring tag tends to hide important information from you, > which only confuses the issue. And as John said in his previous > message, the searchstring tag has problems -- which is yet another good > reason to avoid using it. > No, the documentation has problems; the [searchstring] works just fine. Ken and I differ, here. He got burned by the error in the docs and never recovered his confidence in the [shownext]/[searchstring] pair. I figured out why the docs were wrong and use [searchstring] every day without fear.If you care to see just how magical [shownext] is, check out this from our web site. The raw WebDNA:[ShowNext position=begin&method=post&max=1]
[/ShowNext]The processed page (for a representative search):
John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Kenneth Grome wrote: > John's almost right, except for two things: > > 1- The search context requires a startat parameter, not a start > parameter. > Yes, sorry, startat, not start.> 2- The value of the startat parameter must be a variable ... and the > value of that variable must be set inside the shownext context.Wrong! I don't know where Ken gets this stuff. The [searchstring] tag includes everything you need to continue your search. The startat parameter must be present in the original search and then it is available as part of the [searchstring] tag. There is no requirement that it be a variable, because _all_ form parameters are variables.> > By the way, if you stop messing around with the searchstring tag and > instead put all the required variables into your shownext URLs manually, > as I have demonstrated above, then you will probably begin to understand > what's going on when you click a shownext link.You'll also spend a lot of time writing non-portable code. [searchstring] does everything for you. With Ken's techniques, you cannot have a page be the target for multiple search variations and have the [searchstring] automatically do the right thing.> > Using the searchstring tag tends to hide important information from you, > which only confuses the issue. And as John said in his previous > message, the searchstring tag has problems -- which is yet another good > reason to avoid using it. > No, the documentation has problems; the [searchstring] works just fine. Ken and I differ, here. He got burned by the error in the docs and never recovered his confidence in the [shownext]/[searchstring] pair. I figured out why the docs were wrong and use [searchstring] every day without fear.If you care to see just how magical [shownext] is, check out this from our web site. The raw WebDNA:[ShowNext position=begin&method=post&max=1] [/ShowNext]The processed page (for a representative search):John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
John Peacock
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:
[shipCost] math formula? (1997)
Math Problem - Format? (1997)
FWD: Autoproxy Bug with WebCatalog and FireSite (1997)
Multiple Ad databases? (1997)
Using Applescript to process WebCatalog functions (1998)
Country & Ship-to address & other fields ? (1997)
Newbie from and old bee (1997)
autocommit problem (1998)
Taxable Shipping (2003)
Version f1 status (1997)
[shownext] support - MacOS (1997)
WebCat2b15MacPlugin - [protect] (1997)
hmmm (2006)
Secure Server (1999)
MacAuthorize order data fields WAS:How To question... (1997)
Calendar Program (2004)
Doing what I can (2004)
Need relative path explanation (1997)
String manipulation in Webcatalog (2001)
Cookies not setting on IE (2002)