Re: Paths change questions ...
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 56992
interpreted = N
texte = That's funny because I am thinking of coding like this in the future. I have included files that either require passing a path so all the database paths work wherever the include is in relation to the template calling it. The alternative I've used is creating two includes. That's clearly not workable. I'm also thinking that the path relative to site root is easily controlled when moving servers, I just won't use a Windows server. Now I've got to create a shell script command to do this for me or grep all includes and work through my list of them. I'm thinking: $ grep -r include * Bill > Thanks Scott. Now that I know this, I also know that I will *not* > change my coding techniques. I'm certainly not going to expose > myself to this kind of problem every time I move a web site ... > > > >> For all UNIX builds of WebDNA (including OSX), that should always work as >> expected. However, that will not work on the Windows platform, unless.... >> >> You are using WebDNA 5 or greater >> AND >> are running the site in a WebDNA sandbox >> AND >> the sandbox path is set to the website root. >> >> >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of >> Kenneth Grome >> Sent: Wednesday, March 17, 2004 8:03 PM >> To: WebDNA Talk >> Subject: Paths change questions ... >> >> >> I'm considering a change from using relative paths from the current >> template (which I have always used in the past without any problem) >> to relative paths that begin in the web site's root folder (which may >> create new problems). >> >> My question has to do with the portability of sites coded like this. >> >> If I always use paths that begin with a slash, will this technique >> always create a path that begins in the current web site's root >> folder, or does this depend upon the version of webdna, the sandbox >> settings (if available), the platform, the OS, the server software, >> or any other issues like these? >> >> -- >> >> Kenneth Grome >> WebDNA Programmer >> Outsource Service Provider >> Phone: +6332 255-6591 >> ------------------------------------------------------------- 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:
That's funny because I am thinking of coding like this in the future. I have included files that either require passing a path so all the database paths work wherever the include is in relation to the template calling it. The alternative I've used is creating two includes. That's clearly not workable. I'm also thinking that the path relative to site root is easily controlled when moving servers, I just won't use a Windows server. Now I've got to create a shell script command to do this for me or grep all includes and work through my list of them. I'm thinking: $ grep -r include * Bill > Thanks Scott. Now that I know this, I also know that I will *not* > change my coding techniques. I'm certainly not going to expose > myself to this kind of problem every time I move a web site ... > > > >> For all UNIX builds of WebDNA (including OSX), that should always work as >> expected. However, that will not work on the Windows platform, unless.... >> >> You are using WebDNA 5 or greater >> AND >> are running the site in a WebDNA sandbox >> AND >> the sandbox path is set to the website root. >> >> >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of >> Kenneth Grome >> Sent: Wednesday, March 17, 2004 8:03 PM >> To: WebDNA Talk >> Subject: Paths change questions ... >> >> >> I'm considering a change from using relative paths from the current >> template (which I have always used in the past without any problem) >> to relative paths that begin in the web site's root folder (which may >> create new problems). >> >> My question has to do with the portability of sites coded like this. >> >> If I always use paths that begin with a slash, will this technique >> always create a path that begins in the current web site's root >> folder, or does this depend upon the version of webdna, the sandbox >> settings (if available), the platform, the OS, the server software, >> or any other issues like these? >> >> -- >> >> Kenneth Grome >> WebDNA Programmer >> Outsource Service Provider >> Phone: +6332 255-6591 >> ------------------------------------------------------------- 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/
William DeVaul
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:
[WebDNA] group searching not working as expected. (2010)
URGENT! Locked DB's (2001)
New Site Announcement (1998)
WebCat for Unix?? (1997)
WebCatalog stalls (1998)
WebCat editing, SiteGuard WAS:SiteAssociative lookup style? (1997)
WebDNA & Suse Linux (2004)
capitalize each word? (2002)
Bulletin Board (1998)
Bug or syntax error on my part? (1997)
WebCommerce: Folder organization ? (1997)
Payflow Pro on OSX (2003)
WebCat2b12 CGI Mac -- Problems propagating the cart through frames...still (1997)
Passing WebCat data to SSL server (1997)
Sort Order on a page search (1997)
RE: IIS4b2 and WebCatalog b19 (1997)
OK, here goes... (1997)
Need some assistance. (1999)
Thanks Grant (1997)
Just Testing (1997)