Sorry, Tom, but this is what I've been saying all along.  The apache error
logs show the images as "not existing" in the path where they actually are
- that's the first thing I looked at.
When I view source, img src="/images/qmailadmin/delete.png" which is the
correct path as well.
The initial login images are in the actual HTML files but they are NOT in
the HTML files for the show_users.html and other GUI page files.  This
would explain why they are found whereas the button images are not because
the HTML is being generated by qmailadmin.
I've changed the permsissions and ownership to no avail.
One thing I've tested which only adds to my frustration is the following:

I noticed that the disabled.png button image was the only image showing so
logic follows that the ownership/permissions on that file must somehow be
different.  But it wasn't.  I tried moving the image out of the images
directory and refreshing the page - it didn't display any more.  This
shows me that qmailadmin can find some of the images in the right place
and not the others.  I then tried moving ALL the images out and then back
into place.  Still no dice EXCEPT that disabled.png still displays fine
!!!

ARGH !

Thanks for all your help on this so far...

====================================
OSC Consulting
Affordable Dedicated Email, Ecommerce, and Web servers.
!!! $199 per month 30-day CASH BACK GUARANTEE !!!
Effective Results -- System Administration and Consulting Services.
http://www.1osc.com

> On Monday, March 24, 2003, at 03:29  AM, tonix (Antonio Nati) wrote:
>> Check in your apache logs which paths and images you are looking for.
>
> If you look at the errorlog, you'll find out what image URLs are
> failing.
>
> You could also do a "view HTML source" from your web browser for the
> pages with failing graphics, and search for "IMG" tags to see what
> they're set to.
>
> I'm pretty sure that 1.0.6 had images stored in a hard-coded location
> /images/qmailadmin.  I'm surprised that the graphics on the login and
> main menu pages load, but not the others.  The only difference I can
> think of is that those IMG tags are coded into the HTML templates, and
> all of the other tags are coded in the source code.
>
>>> > check the permisions on the images.
>>> > it should be 600, owned by webserver's user, or at least, readable
>>> by
>>> > webserver's user
>
> Better to make them 644 -- that way they're readable by everyone and
> ownership doesn't matter (and in fact can be "root" so no one can write
> a cgi script on your server to modify the graphics files).
>
> --
> Tom Collins
> [EMAIL PROTECTED]
>
>




Reply via email to