Hi @abdulazeem – thanks for replying!
Yes, you’re right, it seems to have fixed itself, or revalidated because the error went away in the Google Search console. If it comes back again in the future, I’ll create a new topic. Thanks again for taking the time to look into it!
All the best,
Patrick Jaszewski
Actually both. They got set initially, I cleared my litespeed and browser cache (CDN set to development mode), and the frontend did not show the fonts. Then, I checked the customize view and the correct fonts were in the dropdown, but not appearing on the page. Clicking the debug checkbox set them in the back-end initially, but they didn’t appear on the frontend or the backend after clearing caches and refreshing.
Thanks for your help @dannycooper.
Solved! I cleared my browser cache. Should have done that first!
