Let me start by saying this is NOT a promotion for my blog (but feel free to enjoy it if you wish). If it were, I wouldn't be posting in this section. I uploaded an article to it earlier today while in Mozilla Firefox, and it appeared totally screwed up afterward. I figured I wrecked it somehow. BUT -- I then accessed it from Microsoft IE, and it came up just fine! Multiple times! So then I reinstalled Firefox, figuring that would fix it. No soap. The blog still comes up exactly as screwed up as before, on Firefox, everytime. So NOW I have no idea whether it's just MY Firefox browser, or if the site somehow got de-optimized for Firefox for **others** who try to access it that way. Please try accessing it with both Firefox & IE, and let me know what happens in each case, for you. If it comes up properly, you should see a green digital clock funtioning near the top on the left side. And just below that, there should be a nice photo of a forest in fall colors. [More...] http://apifar.blogspot.com To "Arm Blah" -- Thanks for doing that! I should have thought to ask folks to try bringing it up in *other* browsers as well. I'm glad it worked on that one. (And I know that Macs have wonderful systems. But Windows works fine for me at least 99.9% of the time, and I'm used to it. Thanks again!) To "lavender_tie" -- Thanks for your help, and your suggestion. Maybe blogger.com can help me get it straightened out. Firefox always rendered the site perfectly -- up until this afternoon. To "timniet" -- Thanks for your help... and for all the excellent suggestions! I'll work on implementing some of those. Right now, I'm writing a "Topical Index" that can have a link to it from the left side, near the top. After clicking on its link (to a page for that purpose within another website that I pay to have hosted), they can choose articles by their topics, and *those* links will return them to their chosen articles within the blog. To "Arm Blah" -- Regarding your two supplemental edits, the clock wouldn't even come up for me on IE for a couple of days, but it seems to be working all right again now. So *that* aspect may simply have been an outage on the part of those who furnish the clock to the blog site. Thanks for telling me this, though. I'm assuming the the site appeared all right *otherwise* on those browsers, or you probably would have mentioned it. So the major foul-up may be restricted ONLY to Firefox.