|
|
Posted by Lars Eighner on 10/09/07 23:35
In our last episode, <xn0fc9m6n1wv8cd006@news.individual.net>, the lovely
and talented Jeff Gaines broadcast on comp.lang.php:
> On 09/10/2007 in message
><slrnfgo1n8.1iiu.usenet@debranded.larseighner.com> Lars Eighner wrote:
>>Well, I'm mystified. However if the browser displays the stuff like html,
>>(hides the tags, underlines the link), I'm pretty sure that it is a .php
>>file is not your problem.
> I have a solution :-)
> You made me think of it so thanks for jogging my brain.
> A link in the form:
> http://localhost/Test/Usenet.htm
> works fine - because I am reading the files on a 'server' not in the file
> system. It doesn't explain why the file link doesn't work but this is
> probably a better way of doing it. It even sorts the spaces out
> automagically!
Well, yes. Given your development environment this makes perfect sense. Of
course, "file:" should work. but if you do not have to crack this nut, there
is no reason not to leave it as one of those odd things to look into at your
leisure. Sometime things put aside --- because you can put them aside ---
solve themselves because you find the solution to some parallel problem or
notice some clause in a manual that you had overlooked.
I do most of my work from the command line, so if it doesn't work without a
server, I tend to think it doesn't work at all. (The upside is that if it
works on the command line, it will work on the server --- at least that is
my experience so far.) I never see anything working on the server that does
not work on the command line because if it didn't work on the command line I
did not put it on the server.
--
Lars Eighner <http://larseighner.com/> <http://myspace.com/larseighner>
Countdown: 468 days to go.
What do you do when you're debranded?
Navigation:
[Reply to this message]
|