Re: File not found error message

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 20090
interpreted = N
texte = On 9/24/98 2:32 AM, Wayne Morishige so noted...>I'm having a problem with my search codes. The following search codes >keeps returning a file not found message. > >href=products.tpl?Command=Search&db=../../100_dbase/storefront.db&eqCOMPA >NYdatarq=IslandCovers>SEARCH ITEMSThis may not be the most practical of solutions, but...Could you try doing the search with contexts instead of commands? That way, the browser or anything the request passes though wouldn't have a chance to mangle the URL. Last June someone sent me a note stating they were having the same problem with a page on one of my sites. Turns out that the client was using SurfDoubler, and when that was switched off, the problem went away. While I don't think the problem was necessarily limited to SurfDoubler (dunno, Connectix never returned my letter : ) it *may* be a proxy issue. In any case, writing the search as a context would take that variable out of the picture. FYI, I resolved that particular problem by making an alias of the folder containing the database I was referring and placing it in the directory with the .tmpl file that called it. That way, I could call aliasfolder/list.db instead of ../../originalfolder/list.dbOn a side note, I think I've used commands once (other than $quit, $flushdatabases and the like). Puts me at a disadvantage when trying to decipher some of the code questions on this list (one part of the search request in a hidden form field here, another part tucked into a URL there... : ) and I wish that the tutorial could go into more depth using contexts instead of commands. IMHO they're a lot easier to follow, structure-wise. Add in the fact that it keeps elements of your work out of browser-viewable source code and URLs, contexts seem a better way to assemble a site.Rant off, we now return you to your regular Q & A ; )Rob Marquardt Designer/Resident Wirehead Toast Design300 First Avenue North, Suite 150 Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com Associated Messages, from the most recent to the oldest:

    
  1. Re: File not found error message (Wayne Morishige 1998)
  2. Re: File not found error message (PCS Technical Support 1998)
  3. Re: File not found error message (Rob Marquardt 1998)
  4. Re: File not found error message (Wayne Morishige 1998)
  5. Re: File not found error message (Kenneth Grome 1998)
  6. Re: File not found error message (Wayne Morishige 1998)
  7. Re: File not found error message (Wayne Morishige 1998)
  8. Re: File not found error message (PCS Technical Support 1998)
  9. File not found error message (Wayne Morishige 1998)
On 9/24/98 2:32 AM, Wayne Morishige so noted...>I'm having a problem with my search codes. The following search codes >keeps returning a file not found message. > >href=products.tpl?Command=Search&db=../../100_dbase/storefront.db&eqCOMPA >NYdatarq=IslandCovers>SEARCH ITEMSThis may not be the most practical of solutions, but...Could you try doing the search with contexts instead of commands? That way, the browser or anything the request passes though wouldn't have a chance to mangle the URL. Last June someone sent me a note stating they were having the same problem with a page on one of my sites. Turns out that the client was using SurfDoubler, and when that was switched off, the problem went away. While I don't think the problem was necessarily limited to SurfDoubler (dunno, Connectix never returned my letter : ) it *may* be a proxy issue. In any case, writing the search as a context would take that variable out of the picture. FYI, I resolved that particular problem by making an alias of the folder containing the database I was referring and placing it in the directory with the .tmpl file that called it. That way, I could call aliasfolder/list.db instead of ../../originalfolder/list.dbOn a side note, I think I've used commands once (other than $quit, $flushdatabases and the like). Puts me at a disadvantage when trying to decipher some of the code questions on this list (one part of the search request in a hidden form field here, another part tucked into a URL there... : ) and I wish that the tutorial could go into more depth using contexts instead of commands. IMHO they're a lot easier to follow, structure-wise. Add in the fact that it keeps elements of your work out of browser-viewable source code and URLs, contexts seem a better way to assemble a site.Rant off, we now return you to your regular Q & A ; )Rob Marquardt Designer/Resident Wirehead Toast Design300 First Avenue North, Suite 150 Minneapolis MN 55401 612.330.9863 v 612.321.9424 f www.toastdesign.com Rob Marquardt

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:

[shell] (2002) [founditems] & radiobuttons - CONCLUSION (2002) Follow-Up to: Removing [showif] makes a big difference in speed (1997) Header info in content (1998) Is there an alternative to emailer? (1999) checking for [ and ] in form fields ... (1997) WCS Newbie question (1997) How to implement 'email to a friend' feature? (2002) (1997) emailer (1997) Hidden or Forbidden? (1998) Conditional searching & displaying (1997) Re[2]: POSTing to a secure server ... (2000) problems with 2 tags shakur (1997) How flexible is Shipping? (1997) instant cookies? (1999) shopcost, unitshipcost (2002) 'RequiredField' Question (1998) Cancel Subscription (1996) webcat and OS 8 (1997)