Ok. I've updated everything that I think I needed to....running check-fetch-times tells me that everything is current now.
I'm a paranoid type of person so rather than doing a bulk upload (which would have been fine) I went through and renamed a single file and then uploaded it's update. I figured I'd have a known, easily found replacement if one of the new files didn't work out. I only ran into two hiccups along the way...which apparently has nothing to do with the integrity of the new files.
The first one was with get-USNO-sunmon.php. Once I uploaded it it brought up two error messages on my homepage...errors on certain lines of code. Seems one line was #368 (or in that vicinity), the other line was very close to that line...within 10 or 12 lines of it. I reverted to the saved file and all was well. I then reloaded the new file to replicate the error messages and retrieve the specific line numbers but things seem to be working fine and the errors don't come up now. Was this some type of current data requiring hiccup that straightened itself out?
The second issue doesn't appear to be associated with the new files (I reloaded the old file and I had the same issue). This one is wxquake.php. The problem is that the map comes up for a moment but then is replaced with a Java error message...
"Oops! Something went wrong. This page didn't load Google Maps correctly. See the JavaScript console for technical details." The individual quake data down below shows fine, just not the map. I tried this both in Firefox and in Chrome. Anybody got a (Java?) solution on this one? This was probably already happening before the update and checking it out brought it to my attention. I'll check the forum out for recent discussion of this.
Thanks for all the help, Ken. The current condition issue that started this thread has been corrected. Now to get wxquake figured out.
Ed