Re: Help getting [shownext] to increment

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 47295
interpreted = N
texte = >> I'm getting groggy trying to get [shownext] to work ...>>Simply put, [shownext] requires the original search to include both >the max and start paramaters ...John's almost right, except for two things:1- The search context requires a startat parameter, not a start parameter.2- The value of the startat parameter must be a variable ... and the value of that variable must be set inside the shownext context.In other words, your search context should look like this:[search db=catalog.db&eqXXXdatarq=[url][XXX][/url]&max=5&startat=[startat]]... and your shownext links should look like this:[shownext]Show items [start]-[end][/shownext]Please pay close attention to the startat=[start] portion of the URL in the shownext context. It does NOT say start=[start] and it does NOT say startat=[startat] -- it says startat=[start]. The reason is because this is where the startat value gets *SET* ... and it gets set to the [start] value.If this confuses anyone, here are some other examples that will work just fine too:Example #2:[search ... &startat=[var99]][shownext][start][/shownext]Example #3:[search ... &startat=[blah]][shownext][start][/shownext]Example #4:[search ... &startat=[zzzzz]][shownext][start][/shownext]In other words, you can NAME the variable anything you want, as long as it gets its value from the [start] tag inside the shownext. Then use the same variable as the startat value in your search context. That's all there is to it.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.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.If you stop using the searchstring tag and adopt a different approach, there is only one simple rule to follow: Every search context variable MUST appear in every shownext URL.Simple rule, right? Except that when you try to do it the 'easy way' by using [searchstring] to put the variables in the shownext URL, you never really see what the [searchstring] tag's value is -- so you never really know what values are being put into the URL. And then you get confused because you don't really understand what's going on inside that searchstring tag ...So ... if you prefer to see and understand EXACTLY what's going on, I would recommend that you never again use the searchstring tag. Instead, just type every variable manually into your shownext links according to the simple rule I wrote above.If you can remember the simple rule above, that is all you will ever need to understand why your shownext links don't work sometimes ... and how to fix them so they WILL work properly from now on.:)Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development Center175 J. Llorente Street +63 (32) 255-6921Cebu City, Cebu 6000 kengrome@webdna.netPhilippines http://www.webdna.net----------------------------------------------------------------------------------------------------------------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:

Re: Help getting [shownext] to increment (Marko Bernyk 2003)
Re: Help getting [shownext] to increment (Marko Bernyk 2003)
Re: Help getting [shownext] to increment (Kenneth Grome 2003)
Re: Help getting [shownext] to increment (Donovan 2003)
Re: Help getting [shownext] to increment (John Peacock 2003)
Re: Help getting [shownext] to increment (Donovan 2003)
Re: Help getting [shownext] to increment (Joe R. Richardson 2003)
Re: Help getting [shownext] to increment (Joe R. Richardson 2003)
Re: Help getting [shownext] to increment (John Peacock 2003)
Re: Help getting [shownext] to increment (Kenneth Grome 2003)
Re: Help getting [shownext] to increment (John Peacock 2003)
Help getting [shownext] to increment (Joe R. Richardson 2003)

>> I'm getting groggy trying to get [shownext] to work ...>>Simply put, [shownext] requires the original search to include both >the max and start paramaters ...John's almost right, except for two things:1- The search context requires a startat parameter, not a start parameter.2- The value of the startat parameter must be a variable ... and the value of that variable must be set inside the shownext context.In other words, your search context should look like this:[search db=catalog.db&eqXXXdatarq=[url][XXX][/url]&max=5&startat=[startat]]... and your shownext links should look like this:[shownext][thisurl]?XXX=[url][XXX][/url]&startat=[start]>Show items [start]-[end][/shownext]Please pay close attention to the startat=[start] portion of the URL in the shownext context. It does NOT say start=[start] and it does NOT say startat=[startat] -- it says startat=[start]. The reason is because this is where the startat value gets *SET* ... and it gets set to the [start] value.If this confuses anyone, here are some other examples that will work just fine too:Example #2:[search ... &startat=[var99]][shownext][start][/shownext]Example #3:[search ... &startat=[blah]][shownext][start][/shownext]Example #4:[search ... &startat=[zzzzz]][shownext][start][/shownext]In other words, you can NAME the variable anything you want, as long as it gets its value from the [start] tag inside the shownext. Then use the same variable as the startat value in your search context. That's all there is to it.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.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.If you stop using the searchstring tag and adopt a different approach, there is only one simple rule to follow: Every search context variable MUST appear in every shownext URL.Simple rule, right? Except that when you try to do it the 'easy way' by using [searchstring] to put the variables in the shownext URL, you never really see what the [searchstring] tag's value is -- so you never really know what values are being put into the URL. And then you get confused because you don't really understand what's going on inside that searchstring tag ...So ... if you prefer to see and understand EXACTLY what's going on, I would recommend that you never again use the searchstring tag. Instead, just type every variable manually into your shownext links according to the simple rule I wrote above.If you can remember the simple rule above, that is all you will ever need to understand why your shownext links don't work sometimes ... and how to fix them so they WILL work properly from now on.:)Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development Center175 J. Llorente Street +63 (32) 255-6921Cebu City, Cebu 6000 kengrome@webdna.netPhilippines http://www.webdna.net----------------------------------------------------------------------------------------------------------------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/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: Help getting [shownext] to increment

2003

Top Articles:

Related Readings: