As in '../dir2' vs 'c:/dir1/dir2', or as in '../dir2' vs 'http://server/dir1/dir2'? I had to clean a bunch of the latter out of web site recently when it moved from one server to another - the number of hard-coded server-name links was obnoxious!
Did he legitimately not have a clue what you were talking about, or did he just not know the proper terminology for them? (I was that latter guy, once)
As in '1337.jpg' vs 'http://example.com/bsns/srs/1337.jpg', when the thing doing it was on a completely separate server. The guy plucked his code out of Dreamweaver's source code for his site and was upset that it didn't work on our server. *smackity*
I do not lie when I say that I learned a whole lot about how to make phone-based tech support work when tutoring learning-disabled and/or ADHD kindergarteners.
no subject
no subject
no subject
no subject
<img src="1337.jpg" alt="zomg description" usemap="#Map">
(where 1337.jpg refers to an image on example.com, and he's on ecommerce.example.com, which is on a completely different server.)
"No, sir, notice how you've got 1337.jpg up there, you need to replace that with the actual absolute address of where it's at."
"Of the image. The physical address where it is stored on the server. Where you already have it uploaded."
"Look. You have it uploaded somewhere, right? OK. Go there. Right-click on the image. Yes. Copy image location."
"Uh-huh. And see where it says 1337.jpg now? Replace that with what you copied."
"Ohhh!" (in a tone of dawn breaking.) "The whole address, yes!"
2.)
http://www.example.com/images/bsns/srs/1337.jpg
"... Yes, that's very much the address, sir, but what about the IMG tag?"
"Your picture. It won't show up unless it's got some of that stuff from before in there to make it display."
(twenty minutes later...)
3.)
"And you were so helpful! You explained how to put that image in there so quickly and easily! ... But I cannot click on it!"
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject