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:
Hiding HTML and breaking the page (1997)
Programmer Needed (1998)
Date Formats (1997)
using showpage and showcart commands (1996)
Generating unique SKU from [cart] (1997)
v5.x and Apache 2.x (2003)
Saving Text Areas with Orders (1997)
using showpage and showcart commands (1996)
Adding Fields To Db from DB Helper (1999)
Locking up with WebCatalog... (1997)
Advice on MacOS & TCP Connects (2000)
Searching multiple criteria (2000)
Sort Order on a page search (1997)
Change in Host? (1999)
What is WebDNA (1997)
Error:Too many nested [xxx] contexts (1997)
Can webcat 3.0/4.0 handle 1,000,000 hits a day? (2000)
Moving files from one server to another... (2001)
F3 crashing server (1997)
RE: type 2 errors with ssl server (1997)