Hi. My name is***** you for your question and the opportunity to assist.
I'm in south Florida. Post a link and I'll send a screenshot and you can tell me if it's correct.
Has your friend tried opening the site using a different browser?
It is Carolhowe.com
Yes she downloaded a new browser and everything!
Thanks. Give me a minute to check, please.
Ok. This is what it looks like in Firefox (see attachment below)
I also opened it up in Chrome, Internet Explorer and Edge
and it looks the same in those browsers as well.
Yes - this is the website that I see too
But Carol Howe - the woman in the website - see's her old one!
She said she has cleared her cached, tried multiple devices, downloaded a new browser she has never used before - and is still getting the old one?
Any idea what the issue could be?
If this was only happening on a single device I would probably have an explanation. But three devices...I'm not sure.
Is the new page hosted on the same server as the old one?
This sounds like a DNS error.
If she's using a Windows computer, have her hold down the Windows logo key (just to the left of the spacebar) and press R
The Run box will open. In the text area type: cmd
and click OK.
At the blinking prompt in the black window type: ipconfig /flushdns
and press Enter.
A message should state the DNS resolver cache was successfully flushed
and try the web page again.
That didnt work but it self corrected it self :)
This was an internet cache issue with a server storing the old page. When a change is made on a webpage it takes time for the changes to propagate to all servers. A Web cache sits between one or more Web servers (also known as origin servers) and a client or many clients, and watches requests come by, saving copies of the responses - like HTML pages, images and files (collectively known as representations) - for itself. Then, if there is another request for the same URL, it can use the response that it has, instead of asking the origin server for it again. This saves time and makes the internet look more responsive but until the changes are made system-wide, clients (your friend) can end up looking at the old content. Cached content has what's called a TTL(time-to-live) that is set on the server. Once the TTL expires, cached content is flushed and a request (from your friend) is sent to the origin server and the cache updated.