The other thing to try would be linking to an external image, say, the
google logo. If that shows up, it's a good sign and suggests your
problem is with your server configuration or relative/absolute URLs.
You can also try viewing the image properties in the browser and see
what it says the path to the image is... if it is correct (it will be an
absolute path) then you know it's a permissions problem. If it's
incorrect, you can see in what way it's incorrect and modify to suit.
larry price wrote:
On 7/7/06, Matthew Jarvis <[EMAIL PROTECTED]> wrote:
updating a BF dealer page with some new pictures... they just won't
display...
I looked at permissions and out of desperation went 777 on them, but
they still don't show. Originals weren't 777 but the user group
permissions had 'x' in there as well... I guess I just don't know how a
browser interprets a jpg file when it's flagged as executable...
When I view source it has the reference to the filename just like it's
supposed to...
Okay, I'm stumped.... any suggestions?
URL's, relative or Absolute?
if your DocumentRoot is /usr/local/www/bikefriday/
and your images are in images/ relative to that then an
href='images/image.jpg' should work but an
href='bikefriday/images/image.jpg' wont
It can be confusing especially since common apache settings will
canonicalise urls for you changing 'images/image.jpg' to
'http://example.com/images/image.jpg'
Are you getting 404 Not Found?
look at how the URL is being mapped to the filesystem.
Are you getting 403 Not Authorised?
then you have a permissions problem at the apache level.
_______________________________________________
EUGLUG mailing list
euglug@euglug.org
http://www.euglug.org/mailman/listinfo/euglug
_______________________________________________
EUGLUG mailing list
euglug@euglug.org
http://www.euglug.org/mailman/listinfo/euglug
