The scripts don't create anything in the images folder, it is just picking up the images created by WC
Thanks, for the info. I was not intending to imply that your scripts would do any harm to my currently live, non-weather site. I'll stop bugging you... for a while, anyway!
have you ever thought about putting all your weather-related uploads into a separate folder "weather" or something similar onto your web server?
That's what I've done. The folder is named "steel", quite original, no?
And the directory structure on the site is the same as on my drive.
Part of the problem is that I first tried to use a 'sub domain' on my web space. That appeared to be option 2 in the Wiki. That plan never seemed to work, even though my .htaccess file seemed to allow it; it probably didn't, but I wasn't sure how to change it, so I fell back to option 1.
At that point, I became concerned about the edits to the "imgPathURL". However, I have reviewed the path/relative path details and I think the edit is correct (it would certainly have been discussed by now, if not!
).
The edit in gauges.js is simply setting a variable that is used by other scripts, to build the actual path to the images. The script with that 'call' for the image is not in gauges.js itself, or even the directory it resides in. I'm sure if I took the time to trace those 'calls', I would end up in the "steel" directory. Javascript is mostly Greek translated into Latin and converted by Babel.com!
My ignorance of what does what (WC and/or the Steel Gauges scripts) helps confuse me. I may need to change my 'location' to show that 'state', BTW.