Re: PHP and Javascript Problems--lost in TWB

Hi Robert! On Fri, 15 Sep 2000, Robert Lorimor wrote: > Right now I lost in the "TravelsWithBob.com" website. > > I am in the middle of transferring this photo website that was using Cold > Fusion to PHP4. Good decision! :) > First thing problem I ran the images filenames are case senitive on the PHP > server, so the pictures were all broken due to an all-cap folder. To > temporary fix that we added a checkspelling line to the .htaccess file. (I > should say that it almost fix the entire problem, on the thankyou page for > submitting a comment the images are still not loading despite everything I > can think of trying... may also be releted to a cookie header I have on that > page) turn them all to small caps in your images dir w/ something like: for i in $(find /my/images -type f -print); do $dir = $(dirname $i) $fil = $(basename $i) mv $i $dir/$(echo $fil | tr A-Z a-z) done > Next problem I ran into was that the javascript rollovers buttons were slow, > depite being preloaded with javascipt. I have even tried preloading them by > hiding them on the page as single pixel images. The rollover buttons are > still slow. I can also see that each time the mouse rolls over the buttons, > there is a activity going on with my modem. This is strange. I was under the > impression that javascript is cliet side. Haven't the images been precached? > Keep in mind that the roll over were not slow with the cold fusion server > and as far as I can tell, there are no request made to the server. This is because the server doesn't send an E-Tag or Last-Modified or something to enable caching the picture, I guess. See mod_expires in the Apache documentation (I assume you are using it), maybe it can help on that. > Ok, I think... I will rename all the filenames and links to the filenames to > lower case and then remove the checkspelling fix that we used in the first > problem... And what happen?... All the images are broken again... and the > rollovers are still slow. :( well, this is what you get for using drain-bamage wingoz case-insesitive names for files... > > Here is my code for my index page. > > <!-- Travel Asia Photography , including Bangkok, Thailand, Phillippines, > Southeast Asia by award winning photojournalist, Robert Lorimor --> > <HTML> > > <HEAD> > <TITLE>Currently in Thailand -- Travels With Bob - Robert Lorimor's Asia > Photography</TITLE> > <LINK REL="stylesheet" TYPE="text/css" > HREF="portstyle.css"> > <META NAME="Description" CONTENT="Travel Asia Photography , including > Bangkok, Thailand, Phillippines, Southeast Asia."> > <META NAME="Keywords" CONTENT="Asia Travel Photography, Asia > Photojournalism, Asia Photojournalist, Bangkok Thailand"> > <META NAME="Author" CONTENT="Robert Lorimor Asia Travel Photography"> > > > > <SCRIPT LANGUAGE="JavaScript"> > <!-- > <!---------- JavaScript begins... > > if (parent.frames[1]) > parent.location.href = self.location.href; > self.focus(); > window.status="Click the red button to continue." > > // JavaScript ends ----------> > Ah, MM. Generally speaking, I always hated this kind of JS generated code ;) > Any expert opinion out there? What can I try next? first off, verify that your browser gets it's images from the local cache. good luck. -- teodor