Here's something else interesting. When I go to the drop-down menu in the area at the bottom of the page where the finds are supposed to appear, and I select a brand, the finds associated with that particular brand do indeed appear. But I have to have a brand selected, a store selected, etc. I can't get them to display all at once.

Greg, all I can say as far as pinpointing the time was that it started happening a few days ago, possibly in the range of 2-4 days ago. This is when I started not being able to access finds.

My font problem started immediately with the launch of the finds function, so that has been going on for a while. The font problem is annoying but not that big a deal. In fact, I rarely have it happen anymore.

Gigi, being able to see Finds when you select a brand is an important clue. Thanks for that.

I found something that has an outside chance of being responsible for what you're both seeing. Let me know if you can now see the finds (like the ones below this post!).

Well, we're getting there. The finds did not load under your post initially, and I didn't see my own finds at the bottom of the page, but when I hit "reload" on my finds, *your* finds appeared in your post.

However, my own finds still do not appear, even after "reload." And when I select the brand, what happens now is nothing appears at all. But when I afterward select a different brand, a find loads—but it is the find for the first search, not the second. And the find disappears instantly (it just flicks on the screen for a second). When I search for a third brand, the find from the second search loads and disappears.

And here's the fun part. I just noticed that after I mouse over *your* finds (I don't click on them but just mouse over), *my* finds appear at the bottom of the page. But for some reason I have to mouse over your finds first. And after I do a new search in my finds, my own finds disappear again—but I can get them to reappear after I mouse over your finds again.

Clear as mud?

On first read this all sounds very strange, but all the detail will be super helpful. Back to the drawing board!

I will also mention that my finds area doesn't even say "loading" anymore. The area is just blank (although the header appears with "select finds to add them to your post," etc.).

I have made further refinements. Not confident they will make any difference because I can't reproduce the problem myself at the moment. Hope to remedy that tomorrow though.

Forever hopeful, I added two more of my finds to this post.

Unfortunately, the finds are still acting as they were previously—I can't see either yours or mine, but when I click on various buttons for *my* finds, I can then see *yours* (not mine!); after I mouse over your finds, I can then see my own. Pretty crazy!

I did see that today there is a little icon where the finds are, showing that the finds are loading (it is a little moving circle thingie). However, the finds do not ever load. The page is still not hung up, however, as the little icon in the URL bar shows that the page itself does indeed finish loading.

Thanks Gigi. The good news is that I finally have an old version of the Safari browser and I can see the same problem that you do. AND I have a fix. I just need to test a bit more and then I will deploy it on the website. So hopefully tomorrow you will be seeing finds again.

Thanks, Greg!

Greg, everything seems to be OK now. Thanks for being persistent!

Phew! Thanks for your patience Gigi. Let me know if there are any other problems. Even if they are smaller ones.

BTW: The reason for this problem was that the older version of the Safari browser doesn't conform to the standards for the way websites are built. This definitely makes it a stronger argument for upgrading your system and moving to a more modern browser.

Thanks for the info, Greg. So it looks like I can probably start to expect similar problems on other websites.

Instead of upgrading my OS, would I be able to just switch to a different browser (Chrome or—God forbid—Firefox)?

Gigi, absolutely. I would suggest Chrome. The internal engine is actually very similar to the one used in Safari.