Font problems continue 
Author: John W.Seems every time I upgrade to a new version of the software, I have to go through every web site which, I have created and fix font issues. This is a continuing issue for which, I started an earlier thread at:
https://helpcenter.websitex5.com/en/post/209369
I would have added information there but, the thread is closed.
The last time there was a mojor upgrade, I edited the style.css file and got rid of the mentions of the fonts causing the error and the error went away. After the 2020.3.6 version upgrade, the error came back on all sites but, this time, the font was named fakeFont. fakeFont could not be found in any file that I could open and I never did find it, any where it was listed, within the program.
Project analysis in step five shows nothing and pretty much never has when this operation is tried.
In template settings, I searched through every setting to see if fakeFont was listed anywhere and nothing was found. I changed every font mentioned in headings and other areas of pages, to areal font. Restarted the program and the error still popped up.
I then, opened every page within the web site and closed it and saved it. Then restarted the program and the error disappeared. A lot of work to thousands of pages, across multiple websites, to fix an error message. I worry about errors on pages especially since, search engines are so particular about the content of your pages.
When template settings are changed, there is no global update of all pages in the site and must be done manually to every page so, it appears. Maybe version 2021 will be a better version. Fingers crossed!
Hello. I sent a notification about your message to the company employees, expect an answer from them here in the comments.
Hello John
I'm very sorry to hear this warning message is causing you so many issues. I must confirm that this problem is very particular and it is also particularly difficult to identify correctly.
This problem does not always occur regularly. In fact, every time I tried to reproduce it on a new project or even on the projects sent in the various reports, I could not see this problem.
In this situation, understanding what is causing the problem is extremely complicated
I can confirm that the developers are still investigating the matter, albeit so difficult to reproduce.
If it continues to happen to you, try to check if with a certain IWZIP the problem seems to happen regularly with every import. If so, open a private topic and forward the project to me for further testing
This way, it may be easier to find a situation where the problem is always present
Thanks for your patience and understanding
Stephen