Font colour/size problem 
Author: Alf W.
Visited 1698,
Followers 1,
Shared 0
The font type/size/and colour in my text boxs are fine, and the preview is as I want it. When I update to the web they have been changed. I am using Evolution 11 and have never had this problem before in 3 web sites I manage.
This problem is on the http://www.chatterismusicsociety.org.uk/ web site on the Program for 2020 page - the lines of text which have been changed concern the Coronavirus cancellations.
Posted on the
Hello Alf,
This is what I see when I visit the page in question:
How does this differ from what you expect to see?
Can you provide details of the font type, size and colour that you are trying to use?
Kind regards,
Paul
Search the WebSite X5 Help Center
Author
Hello Paul,
Thanks for responding so quickly.
When I access the web site I see the 'Unfortunately' phrase in Times New Roman, Red, font size 9. It should be font size 16 (as it is when I preview before uploading).
On the following text box underneath I see the 'We regret' phrase in Times New Roman, Black, font size 9. It should be in red and font size 16 (as it is when I preview before uploading).
What's going on??
Those fonts and colours are exactly the ones I see on the live website, which proves that the copy on the server is correct.
So this is a straightforward (and common) browser caching issue. Your browser has stored a copy of a previous version of the page in its cache.
To clear the cache you can follow the instructions provided by the manufacturer of whichever browser you are using.
For example:
How to clear the cache in Chrome
How to clear the cache in Firefox
This is a browser issue as opposed to anything to do with WebSite X5.
Author
Hello Paul,
Many thanks, you are absolutely right. I am using Edge as a browser on my PC. When I found the web site was correct in Internet Explorer, and Chrome on my PC, and was correct in Internet Explorer, Chrome, and Edge on my laptop it was becoming clear that this was certainly not a WebSite X5 problem. I cleared the Edge cache and the 'problem' disappeared.
Many thanks for your swift help.
You're welcome, Alf... glad it's resolved.