This is Interesting: Free Magazines for Graphics designers and webmasters
Home > Archive > Dreamweaver > June 2004 > Definitions, please
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Definitions, please
|
|
| Jenna 2004-06-10, 12:14 pm |
| Can someone define these examples for me:
1) foldername/filename.ext
2) /foldername/filename.ext
I think one is root relational, but don't know which is which.
Also, it seems that sometimes the graphics won't show up when they are
uploaded because the filepath is lacking or has the / at the beginning. HOW
DOES ONE MAKE DREAMWEAVER AUTOMATICALLY FORMAT ALL FILENAMES ONE WAY OR THE
OTHER? I always have to go in and either take out the / or add it to all
filenames.
| |
|
|
> Can someone define these examples for me:
>
> 1) foldername/filename.ext
>
> 2) /foldername/filename.ext
>
>
>
> I think one is root relational, but don't know which is which.
>
> Also, it seems that sometimes the graphics won't show up when they are
> uploaded because the filepath is lacking or has the / at the beginning. HOW
> DOES ONE MAKE DREAMWEAVER AUTOMATICALLY FORMAT ALL FILENAMES ONE WAY OR THE
> OTHER? I always have to go in and either take out the / or add it to all
> filenames.
two older messages below. First one is about fixing the links so they will
work when you view the files locally from your Hard Drive. Second tries to
explain difference between linking methods:
older info:
canned letter #7
it's because you are using Site Root relative paths {they always start with
a leading / slash }, and then either trying to directly view the files from
your hard drive, which is happening when clicking a link on a dreamweaver
"Preview in Browser" page, or you are hosted in a subfolder of a domain like
http://myhost.com/~mysite/
Site Root relative paths won't work in those cases- in the first case
because site root is different than drive root, in the later because the
domain is the site root, not your subfolder.
/image.gif is telling the browser the image is at
http://myhost.com/image.gif
but it's really here:
http://myhost.com/~mysite/image.gif
If that's the reason- change to Document Relative paths.
The point to file and Insert image uses the Last linking method you have
chosen.
******To change this********
select an existing image or link on the page.
in the Property inspector, click the folder icon, to open the "Browse to
File" dialog box. On the lower part of that dialog box is pulldown, to
choose "Site Root Relative" or "Relative to Document"
Put it on "Relative to Document"
Finish picking the correct file, and click okay.
That setting will now stay that way until it's changed.
When you use the point to file tool, it will use that method of linking.
If you want to quickly change links to a different linking method- install
the Relativity Extension.
http://e7x.com/dw/ Relativity ext.
or here
http://www.microwaved.plus.com/dw/
**antique canned message #42
There are three link methods-
Relative to Document
Site Root Relative
Absolute or Full http path
1) RELATIVE TO DOCUMENT
.../folder1/page.html
or
folder1/page.html
or
page.html
can start with a folder name, a filename, or can use ../ which means "go up
one folder" ../../../ would mean go up three folder levels from present
location.
Gives directions on how to get to the other file, based on where you are
now. such as go UP one folder, then find a folder named 'folder1', then in
the 'folder1' folder get a file called page.html
A real world analogy- to get to the Post Office from the high school, leave
the high school parking lot, go west, turn left, go south 2 blocks.
( ***The directions are based on where you are now ***)
With Document Relative paths and links, as long as the relationship between
documents is kept the same and folders aren't juggled around, the links will
work anywhere. The most portable linking method.
Say a page located here:
http://example.com/folder1/folder2/page.html
contains an image tag like this:
<img src="../image.jpg">
That means go up one level from where this page is, and find image.jpg in
that directory.
http://example.com/folder1/image.jpg
2) RELATIVE TO SITE ROOT
/folder1/page.html
or
/page.html
Will ALWAYS start with a leading slash /
The leading slash means "go to root first, and then follow this file path"
Relative to site root gives directions from the root level of the site,
regardless of where you are starting from.
This root is the domain name, when the site is on a server. If your site is
defined to a subfolder of a domain, do NOT use site root relative paths in
dreamweaver. They will come out wrong, because dreamweaver will base them on
what you've told it your site's folder is, not the real "root" of the site,
which is at the root of the domain.
In real world, to get to Post Office, go to the City Hall then go two blocks
east. It doesn't matter where you are now- you have to go the City Hall to
start following the directions.
(***the directions are based on a ROOT or ground zero point ***)
Think of some cities like Anchorage, AK or Salt Lake City- all street
addresses there can be read as co-ordinates from a zero point. By just
looking at the address, you know in what corner of the city it is.
Site Root Relative the way we use it requires that there be a domain to be
relative to-- thus will not work to create a site on CD. And will not work
from a Hard Drive. "Root" on a CD or HD is different. Needs to be on a
server to work correctly. And- should not be used if your remote site is
hosted in a subfolder of a domain, like http://geocities.com/mysite/
The TMP files dreamweaver creates for a "preview in browser" convert these
to document relative so they work during preview- but only the document
that's being previewed. If you click a link on the "Preview in Browser"
page- you will be looking directly at a file from the hard drive- and site
root relative paths on that page won't work.
Say a page located here:
http://example.com/folder1/folder2/page.html
contains an image tag like this:
<img src="/folder1/image.jpg">
That means go to the site's root level on the server, http://example.com/
then find the folder1 directory, and in that directory find image.jpg
http://example.com/folder1/image.jpg
An example of site root links not working-
Your site is at
http://geocities.com/mysite
If you use a site root relative path in dreamweaver, the link will come out
/image.jpg
and the image is at:
http://geocities.com/mysite/image.jpg
But the browser will be looking here
http://geocites.com/image.jpg
and the image isn't there...
3) ABSOLUTE
http://mydomain.com/folder1/page.html
absolute is the full http address of the file
To get to the post office, go to 113 Main Street, Anytown, Your_State, USA.
Don't need to know anything about where you are starting from, it's an exact
address.
Almost all people who use dreamweaver use Document Relative paths, and let
dreamweaver manage the paths. There are exceptions but few of them. Document
Relative is the easiest for a new user to stay out of trouble with.
The other big concept is that site has to be properly defined within
dreamweaver, because dw makes all links based on the information it's been
given in the site defintion. If that info is wrong- then links can be wrong
(especially site root relative paths)
| |
| Jenna 2004-06-10, 12:14 pm |
| Thankyou so much!! :)
"Alan" <dont_mail_me_period@macromedia.com> wrote in message
news:BCEDE4D7.1991E8%dont_mail_me_period@macromedia.com...
>
>
HOW[color=darkred]
THE[color=darkred]
all[color=darkred]
>
> two older messages below. First one is about fixing the links so they will
> work when you view the files locally from your Hard Drive. Second tries to
> explain difference between linking methods:
>
> older info:
> canned letter #7
>
> it's because you are using Site Root relative paths {they always start
with
> a leading / slash }, and then either trying to directly view the files
from
> your hard drive, which is happening when clicking a link on a dreamweaver
> "Preview in Browser" page, or you are hosted in a subfolder of a domain
like
> http://myhost.com/~mysite/
>
> Site Root relative paths won't work in those cases- in the first case
> because site root is different than drive root, in the later because the
> domain is the site root, not your subfolder.
> /image.gif is telling the browser the image is at
> http://myhost.com/image.gif
> but it's really here:
> http://myhost.com/~mysite/image.gif
>
> If that's the reason- change to Document Relative paths.
>
> The point to file and Insert image uses the Last linking method you have
> chosen.
>
> ******To change this********
> select an existing image or link on the page.
> in the Property inspector, click the folder icon, to open the "Browse to
> File" dialog box. On the lower part of that dialog box is pulldown, to
> choose "Site Root Relative" or "Relative to Document"
> Put it on "Relative to Document"
> Finish picking the correct file, and click okay.
>
> That setting will now stay that way until it's changed.
> When you use the point to file tool, it will use that method of linking.
>
> If you want to quickly change links to a different linking method- install
> the Relativity Extension.
> http://e7x.com/dw/ Relativity ext.
> or here
> http://www.microwaved.plus.com/dw/
>
>
>
>
> **antique canned message #42
>
>
> There are three link methods-
> Relative to Document
> Site Root Relative
> Absolute or Full http path
>
>
> 1) RELATIVE TO DOCUMENT
> ../folder1/page.html
> or
> folder1/page.html
> or
> page.html
> can start with a folder name, a filename, or can use ../ which means "go
up
> one folder" ../../../ would mean go up three folder levels from present
> location.
>
> Gives directions on how to get to the other file, based on where you are
> now. such as go UP one folder, then find a folder named 'folder1', then in
> the 'folder1' folder get a file called page.html
> A real world analogy- to get to the Post Office from the high school,
leave
> the high school parking lot, go west, turn left, go south 2 blocks.
> ( ***The directions are based on where you are now ***)
> With Document Relative paths and links, as long as the relationship
between
> documents is kept the same and folders aren't juggled around, the links
will
> work anywhere. The most portable linking method.
>
> Say a page located here:
> http://example.com/folder1/folder2/page.html
> contains an image tag like this:
> <img src="../image.jpg">
> That means go up one level from where this page is, and find image.jpg in
> that directory.
> http://example.com/folder1/image.jpg
>
>
> 2) RELATIVE TO SITE ROOT
> /folder1/page.html
> or
> /page.html
> Will ALWAYS start with a leading slash /
> The leading slash means "go to root first, and then follow this file path"
>
> Relative to site root gives directions from the root level of the site,
> regardless of where you are starting from.
> This root is the domain name, when the site is on a server. If your site
is
> defined to a subfolder of a domain, do NOT use site root relative paths in
> dreamweaver. They will come out wrong, because dreamweaver will base them
on
> what you've told it your site's folder is, not the real "root" of the
site,
> which is at the root of the domain.
>
> In real world, to get to Post Office, go to the City Hall then go two
blocks
> east. It doesn't matter where you are now- you have to go the City Hall
to
> start following the directions.
> (***the directions are based on a ROOT or ground zero point ***)
> Think of some cities like Anchorage, AK or Salt Lake City- all street
> addresses there can be read as co-ordinates from a zero point. By just
> looking at the address, you know in what corner of the city it is.
>
> Site Root Relative the way we use it requires that there be a domain to be
> relative to-- thus will not work to create a site on CD. And will not work
> from a Hard Drive. "Root" on a CD or HD is different. Needs to be on a
> server to work correctly. And- should not be used if your remote site is
> hosted in a subfolder of a domain, like http://geocities.com/mysite/
> The TMP files dreamweaver creates for a "preview in browser" convert these
> to document relative so they work during preview- but only the document
> that's being previewed. If you click a link on the "Preview in Browser"
> page- you will be looking directly at a file from the hard drive- and site
> root relative paths on that page won't work.
>
> Say a page located here:
> http://example.com/folder1/folder2/page.html
> contains an image tag like this:
> <img src="/folder1/image.jpg">
> That means go to the site's root level on the server, http://example.com/
> then find the folder1 directory, and in that directory find image.jpg
> http://example.com/folder1/image.jpg
>
> An example of site root links not working-
> Your site is at
> http://geocities.com/mysite
> If you use a site root relative path in dreamweaver, the link will come
out
> /image.jpg
> and the image is at:
> http://geocities.com/mysite/image.jpg
> But the browser will be looking here
> http://geocites.com/image.jpg
> and the image isn't there...
>
>
> 3) ABSOLUTE
> http://mydomain.com/folder1/page.html
> absolute is the full http address of the file
>
> To get to the post office, go to 113 Main Street, Anytown, Your_State,
USA.
> Don't need to know anything about where you are starting from, it's an
exact
> address.
>
> Almost all people who use dreamweaver use Document Relative paths, and let
> dreamweaver manage the paths. There are exceptions but few of them.
Document
> Relative is the easiest for a new user to stay out of trouble with.
>
> The other big concept is that site has to be properly defined within
> dreamweaver, because dw makes all links based on the information it's been
> given in the site defintion. If that info is wrong- then links can be
wrong
> (especially site root relative paths)
>
>
| |
|
| i've heard that your supposed to have a / at the beginning of all path.
However I have NEVER done it that way and either use
foldername/filename.ext
or
.../foldername/filename.ext
(if in a different folder)
and it's ALWAYS worked.
If you browse to the file, Dreamweaver will ask you if you want him to
write a document relative path or a root relative path.
Since I always keep my folders the same way locally and online, I choose
once and for all document relative paths and never have problems.
Jenna wrote:
> Can someone define these examples for me:
>
> 1) foldername/filename.ext
>
> 2) /foldername/filename.ext
>
>
>
> I think one is root relational, but don't know which is which.
>
> Also, it seems that sometimes the graphics won't show up when they are
> uploaded because the filepath is lacking or has the / at the beginning. HOW
> DOES ONE MAKE DREAMWEAVER AUTOMATICALLY FORMAT ALL FILENAMES ONE WAY OR THE
> OTHER? I always have to go in and either take out the / or add it to all
> filenames.
>
>
| |
| Murray *TMM* 2004-06-10, 12:14 pm |
| seb:
> i've heard that your supposed to have a / at the beginning of all path.
Where do you hear claptrap like that?
> and it's ALWAYS worked.
Don't try this in an include....
--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================
"seb" <sebnewyork@earhlink.netTakeThisOut> wrote in message
news:ca9se4$qlq$1@forums.macromedia.com...[color=darkred]
> i've heard that your supposed to have a / at the beginning of all path.
> However I have NEVER done it that way and either use
> foldername/filename.ext
> or
> ../foldername/filename.ext
> (if in a different folder)
> and it's ALWAYS worked.
>
> If you browse to the file, Dreamweaver will ask you if you want him to
> write a document relative path or a root relative path.
>
> Since I always keep my folders the same way locally and online, I choose
> once and for all document relative paths and never have problems.
>
> Jenna wrote:
>
HOW[color=darkred]
THE[color=darkred]
all[color=darkred]
| |
| Murray *TMM* 2004-06-10, 12:14 pm |
| seb:
I have read these forums for a long time, and have never seen such advice
posted. But maybe I missed it.
Anyhow, it's wrong.
> i said: i never use / at the beginning of my paths
There are times when you will need to do this, seb.
--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================
"seb" <sebnewyork@earhlink.netTakeThisOut> wrote in message
news:ca9sv3$r98$1@forums.macromedia.com...[color=darkred]
> i said: i never use / at the beginning of my paths, Murray.
> I said: I've heard that you're supposed to, i.e. someone in these forums
> recently wrote that you should (which stroke me, since I never did).
> Too lazy to go find the thread, but maybe you should, and tell that
> person the truth.
>
> Murray *TMM* wrote:
>
| |
|
| i said: i never use / at the beginning of my paths, Murray.
I said: I've heard that you're supposed to, i.e. someone in these forums
recently wrote that you should (which stroke me, since I never did).
Too lazy to go find the thread, but maybe you should, and tell that
person the truth.
Murray *TMM* wrote:
> seb:
>
>
>
>
> Where do you hear claptrap like that?
>
>
>
>
> Don't try this in an include....
>
| |
|
| Murray, don't you ever sleep? Actually, thank goodness you don't. :)
What is your bottom-line recommendation on filepaths????
"Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
news:ca9ta0$rp6$1@forums.macromedia.com...
> seb:
>
> I have read these forums for a long time, and have never seen such advice
> posted. But maybe I missed it.
>
> Anyhow, it's wrong.
>
>
> There are times when you will need to do this, seb.
>
> --
> Murray --- ICQ 71997575
> Team Macromedia Volunteer for Dreamweaver MX
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
> news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
> ANSWERS
> ==================
> http://www.dreamweavermx-templates.com - Template Triage!
> http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
> http://www.dwfaq.com - DW FAQs, Tutorials & Resources
> http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
> ==================
>
> "seb" <sebnewyork@earhlink.netTakeThisOut> wrote in message
> news:ca9sv3$r98$1@forums.macromedia.com...
path.[color=darkred]
>
>
| |
|
| some of the exceptions
Main one- if you are using SSI Server Side Includes, or scripted includes,
use Site Root relative paths for links and images that are IN the included
files. That way they will work in any folder level you use the included
files at.
another- many hosts let you set up a custom 404 page. Use full http:// paths
in this, because it's often delivered by an error routine of the server, and
relative paths may be relative to the root of the server and have nothing to
do with your site.
another- if using a form script like "formmail" and passing a url to a
thankyou page using the "redirect" hidden element, use a full http:// or
site root relative path. If you use a document relative path, it's relative
to the location of the formmail script, Not the location of your form page.
> I'd 'a' answered sooner, but I was taking a power nap.
>
> Bottom line?
>
> Use document relative until you need to use root relative. That's the
> truth. When you get there, you'll know.
| |
| Joe Makowiec 2004-06-10, 7:14 pm |
| On Thu 10 Jun 2004 02:22:47p, Jenna wrote in macromedia.dreamweaver:
> Come to the midwest, I'll buy you a beer.
Murray is in the Midwest.[1]
[1] OK, western suburbs of Philadelphia.[2]
[2] Relative to the Hudson River, that's the Midwest.[3]
[3] I think it was a New Yorker cover?
| |
| Murray *TMM* 2004-06-10, 7:14 pm |
| I'd 'a' answered sooner, but I was taking a power nap.
Bottom line?
Use document relative until you need to use root relative. That's the
truth. When you get there, you'll know.
--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================
"Jenna" <jennaw707@NOSPAMhotmail.com> wrote in message
news:caa8ib$c04$1@forums.macromedia.com...
> Murray, don't you ever sleep? Actually, thank goodness you don't. :)
>
> What is your bottom-line recommendation on filepaths????
>
>
>
> "Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
> news:ca9ta0$rp6$1@forums.macromedia.com...
advice[color=darkred]
GET[color=darkred]
forums[color=darkred]
> path.
>
>
| |
|
| LOL! Your sense of humor is surpassed only by 'schmats' when it comes to
this stuff. Thanks again!! Come to the midwest, I'll buy you a beer.
"Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
news:caa8kq$c20$1@forums.macromedia.com...
> I'd 'a' answered sooner, but I was taking a power nap.
>
> Bottom line?
>
> Use document relative until you need to use root relative. That's the
> truth. When you get there, you'll know.
>
> --
> Murray --- ICQ 71997575
> Team Macromedia Volunteer for Dreamweaver MX
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
> news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
> ANSWERS
> ==================
> http://www.dreamweavermx-templates.com - Template Triage!
> http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
> http://www.dwfaq.com - DW FAQs, Tutorials & Resources
> http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
> ==================
>
> "Jenna" <jennaw707@NOSPAMhotmail.com> wrote in message
> news:caa8ib$c04$1@forums.macromedia.com...
> advice
> GET
> forums
>
>
| |
| Michael Fesser 2004-06-10, 7:14 pm |
| .oO(Alan)
>another- many hosts let you set up a custom 404 page. Use full http:// paths
>in this, because it's often delivered by an error routine of the server,
Not a good idea. Using http://... with an error document causes the
server to send back a 302 ("Found") status code instead of the correct
404 ("Not Found"). This becomes an even bigger problem with HTTP
authentication if you use customized 401 ("Unauthorized") documents.
With remote files the browser will never get the correct status code and
therefore never prompt for a login/password.
See also the ErrorDocument directive in the Apache manual.
http://httpd.apache.org/docs/mod/co...l#errordocument
Micha
| |
|
| If you have already started building a site in DW and decide you want to
change the way the files are pathed, is there any way to tell it to do that
and have it update all the links??
"Alan" <dont_mail_me_period@macromedia.com> wrote in message
news:BCEE2098.199323%dont_mail_me_period@macromedia.com...
> some of the exceptions
>
> Main one- if you are using SSI Server Side Includes, or scripted
includes,
> use Site Root relative paths for links and images that are IN the included
> files. That way they will work in any folder level you use the included
> files at.
>
> another- many hosts let you set up a custom 404 page. Use full http://
paths
> in this, because it's often delivered by an error routine of the server,
and
> relative paths may be relative to the root of the server and have nothing
to
> do with your site.
>
> another- if using a form script like "formmail" and passing a url to a
> thankyou page using the "redirect" hidden element, use a full http:// or
> site root relative path. If you use a document relative path, it's
relative
> to the location of the formmail script, Not the location of your form
page.
>
>
>
| |
|
| from first post--
If you want to quickly change links to a different linking method- install
the Relativity Extension.
http://e7x.com/dw/ Relativity ext.
or here
http://www.microwaved.plus.com/dw/
check the readme on what it will change.
> If you have already started building a site in DW and decide you want to
> change the way the files are pathed, is there any way to tell it to do that
> and have it update all the links??
| |
|
| I didn't mean use a http path in .htaccess or the server config file to
point to the document to use, I meant use absolute paths in the source code
of the custom 404 document itself.
<img src="http://mysite.com/logo.gif">
if you want a logo to show in your custom 404 page you can't use relative
links on most servers, because the link will be seen as relative to the
server's root
> Not a good idea. Using http://... with an error document causes the
> server to send back a 302 ("Found") status code instead of the correct
> 404 ("Not Found"). This becomes an even bigger problem with HTTP
> authentication if you use customized 401 ("Unauthorized") documents.
> With remote files the browser will never get the correct status code and
> therefore never prompt for a login/password.
| |
| Murray *TMM* 2004-06-10, 7:14 pm |
| You're on!
--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================
"Jenna" <jennaw707@NOSPAMhotmail.com> wrote in message
news:caa8tg$ce2$1@forums.macromedia.com...
> LOL! Your sense of humor is surpassed only by 'schmats' when it comes to
> this stuff. Thanks again!! Come to the midwest, I'll buy you a beer.
>
>
> "Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
> news:caa8kq$c20$1@forums.macromedia.com...
GET[color=darkred]
TO[color=darkred]
Technotes[color=darkred]
did).[color=darkred]
that[color=darkred]
all[color=darkred]
>
>
| |
| Michael Fesser 2004-06-10, 7:15 pm |
| .oO(Alan)
>I didn't mean use a http path in .htaccess or the server config file to
>point to the document to use, I meant use absolute paths in the source code
>of the custom 404 document itself.
Ok, little misunderstanding.
Micha
|
|
|
| | Copyright 2003 - 2009 forum4designers.com Software forum Computer Hardware reviews |
|