Re: Linux Beta4 problems with multirecord returns

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 32235
interpreted = N
texte = It appears that the construct [max] is evil. As soon as it appears in any page, bad things happen, except within [FormVariables]. I added the following to the top of my page:max [max]
startat [startat]
numfound [numfound]
and nothing displayed after max 0 at all. If I change the order of execution (i.e. put max [max] last), I see the other items, so it is definitely at the root of my problems. I am using a search command in a form, with the optional parameter max. In [formvariables], I can see the Max = 10, like it should. I added [max] to a formerly working page (where it was not even used) and the page ended just there.John PeacockJohn Peacock wrote: > > Beta4 seems to be suprisingly wonky on multiple record pages (i.e. with > [shownext]). The same page works fine under 3.04NT (with a few simple > modifications, like HTTP_HOST -> Host). I am trying to simplify the > page to see where the problem is happening, but it appears to be in the > [founditems] loop itself. Single record page works fine, so it doesn't > seem to be the database itself. > > A lot of times, I am getting only the following: > > Missing Post reply data >

Data Missing

> This document resulted from a POST operation and has expired from the > cache. If you wish you can repost the form data to recreate the > document by pressing the reload button. > > Pressing reload does nothing, so it looks like the POST code is not > working. Sometimes I get [startat] - 24 of 24 Hits which is the > correct number of records, but what is up with [startat]? > > More details to come... > > John Peacock > > ############################################################# > 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 > To switch to the INDEX mode, E-mail to > Send administrative queries to ############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to Associated Messages, from the most recent to the oldest:

    
  1. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  2. Re: Linux Beta4 problems with multirecord returns (GHulbert@smithmicro.com 2000)
  3. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  4. Re: Linux Beta4 problems with multirecord returns (GHulbert@smithmicro.com 2000)
  5. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  6. Re: Linux Beta4 problems with multirecord returns (GHulbert@smithmicro.com 2000)
  7. Re: Linux Beta4 problems with multirecord returns (John Peacock 2000)
  8. Linux Beta4 problems with multirecord returns (John Peacock 2000)
It appears that the construct [max] is evil. As soon as it appears in any page, bad things happen, except within [formvariables]. I added the following to the top of my page:max [max]
startat [startat]
numfound [numfound]
and nothing displayed after max 0 at all. If I change the order of execution (i.e. put max [max] last), I see the other items, so it is definitely at the root of my problems. I am using a search command in a form, with the optional parameter max. In [formvariables], I can see the Max = 10, like it should. I added [max] to a formerly working page (where it was not even used) and the page ended just there.John PeacockJohn Peacock wrote: > > Beta4 seems to be suprisingly wonky on multiple record pages (i.e. with > [shownext]). The same page works fine under 3.04NT (with a few simple > modifications, like HTTP_HOST -> Host). I am trying to simplify the > page to see where the problem is happening, but it appears to be in the > [founditems] loop itself. Single record page works fine, so it doesn't > seem to be the database itself. > > A lot of times, I am getting only the following: > > Missing Post reply data >

Data Missing

> This document resulted from a POST operation and has expired from the > cache. If you wish you can repost the form data to recreate the > document by pressing the reload button. > > Pressing reload does nothing, so it looks like the POST code is not > working. Sometimes I get [startat] - 24 of 24 Hits which is the > correct number of records, but what is up with [startat]? > > More details to come... > > John Peacock > > ############################################################# > 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 > To switch to the INDEX mode, E-mail to > Send administrative queries to ############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to 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:

WebCat2: multiple currency support (1997) Help name our technology! (1997) Database Options (1997) OT: zipcodes (2002) A matter of time (1997) Filemaker Pro & Webcatalog (1999) WebCat2 beta 11 - new prefs ... (1997) Updated ClipText for Edit Plus 2 (2003) practicing safe queries.. (2000) Forcing a NEWCART (1997) Multiple Passwords (1997) Cookie Question (1999) WebCatalog Features (1997) Re1000001: Setting up shop (1997) Problem displaying search result (1997) New WebDNA Solutions ... (1997) WebCat and PIXO (2000) WebCat 5 (2003) Help formatting search results w/ table (1997) Images (2003)