numero = 50320
interpreted = N
texte = Thanks John, I'll try to get through this. I don't know if you saw the code I posted, but maybe that is a big part of the problem. It's probably not the most elegant way of coding things. On Monday, May 12, 2003, at 02:58 pm, John Peacock wrote:> kmac wrote: >> I guess I'm an idiot, because I can't get this going. > > Without seeing more of your code, we cannot help you. I'll try and > give you a couple of general recommendations and you can see if they > help point you in the right direction: > > 1) [shownext] predates the time when people generally used [search] as > a context, so it operates only as part of a search _command_; > > 2) The target of the [shownext] link will be in an implied search > context, so if you are using an additional [search] context, it will > no work (you'll have to roll your own); > > 3) [ShowNext position=begin&method=post&max=1] will display all of the > parameters actively part of the current search as type=hidden> so it is very useful for debugging (see below); > > 4) most of the arguments about not using commands (preferring > contexts) is needless paranoia (IMNSHO), especially when it comes to > search pages - if you are so concerned about people being able to > rewrite your search queries, take your data off the Internet, > disconnect the PC from all power, and bury it in 300 tons of concrete; > now your data is completely safe! > > My suggestion is to make a simple page the just includes the > [shownext] context and another page that references that page as part > of the search you are trying to perform (this is just for testing and > experimentation). Your _target_ page will look kind of like this (if > it was named ShowFile.tpl): > > >
> > > > Your search page will need to have all of your search terms plus a > couple to enable the [shownext]; as a form, it would look something > like this: > > > > NOTE that the three 'type=hidden' lines are required terms that must > be in any search in order for [shownext] to function. NOTE also that > the max term in the search is not the same as the max term in the > [shownext]; the former is the number of records to return on each page > and the latter is how many instances of the [shownext] loop itself > should display on the page. > > HTH > > John > > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4501 Forbes Boulevard > Suite H > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5748 > > > ------------------------------------------------------------- > 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/ > ------------------------------------------------------------- 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:
Thanks John, I'll try to get through this. I don't know if you saw the code I posted, but maybe that is a big part of the problem. It's probably not the most elegant way of coding things. On Monday, May 12, 2003, at 02:58 pm, John Peacock wrote:> kmac wrote: >> I guess I'm an idiot, because I can't get this going. > > Without seeing more of your code, we cannot help you. I'll try and > give you a couple of general recommendations and you can see if they > help point you in the right direction: > > 1) [shownext] predates the time when people generally used [search] as > a context, so it operates only as part of a search _command_; > > 2) The target of the [shownext] link will be in an implied search > context, so if you are using an additional [search] context, it will > no work (you'll have to roll your own); > > 3) [ShowNext position=begin&method=post&max=1] will display all of the > parameters actively part of the current search as type=hidden> so it is very useful for debugging (see below); > > 4) most of the arguments about not using commands (preferring > contexts) is needless paranoia (IMNSHO), especially when it comes to > search pages - if you are so concerned about people being able to > rewrite your search queries, take your data off the Internet, > disconnect the PC from all power, and bury it in 300 tons of concrete; > now your data is completely safe! > > My suggestion is to make a simple page the just includes the > [shownext] context and another page that references that page as part > of the search you are trying to perform (this is just for testing and > experimentation). Your _target_ page will look kind of like this (if > it was named ShowFile.tpl): > > >
> > > > Your search page will need to have all of your search terms plus a > couple to enable the [shownext]; as a form, it would look something > like this: > > > > NOTE that the three 'type=hidden' lines are required terms that must > be in any search in order for [shownext] to function. NOTE also that > the max term in the search is not the same as the max term in the > [shownext]; the former is the number of records to return on each page > and the latter is how many instances of the [shownext] loop itself > should display on the page. > > HTH > > John > > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4501 Forbes Boulevard > Suite H > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5748 > > > ------------------------------------------------------------- > 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/ > ------------------------------------------------------------- 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/
kmac
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...