Posted by Neredbojias on 01/09/93 11:28

With neither quill nor qualm, dorayme quothed:

> > From: Neredbojias <neredbojias@neredbojias.com>
> >
> >>> I know it sounds silly but it's usually something small - try clearing your
> >>> browser cache and re-load the page. For example it might invole pressing
> >>> shift-F5 (depending on browser used).
> >>>
> >>
> >> I doubt it. If the OP is getting the source code to appear
> >> "almost right". If it was a browser cache problem it would be
> >> totally unlike the intended.
> >
> > How do you figure that? He could have a pre-version "stuck" in the
> > cache, no?
>
>
> OK, Boji, I might be wrong on this! I now can't recall what
> clear but obviously unobvious reason I said this? Indeed there
> could be an earlier "stuck" version. But did the OP ever have a
> forward slash or is this added by the server somehow because of
> some other small user error input?

It could've been a typo, but I really don't know. Servers can do some
strange things...

(...'Specially if you don't tip 'em! Hah, hah, hah. -Er, okay, I'll go
back in my hole now.)

>
> To the OP: I clear cache in a variety of ways. One way is to go
> to an unrelated page, then clear it in preferences or options
> and then to try the original page again.
>
> Also make a new doc, cut and paste nearly everything from old to
> new but actually retype the bit and around it that is giving
> trouble. Then ftp new html doc up to server...
>
> dorayme
>
>

--
Neredbojias
Contrary to popular belief, it is believable.

[Back to original message]