It looks like you've hit a classic "URL mismatch" issue that often occurs during WordPress migrations. When you move from a staging URL to a live domain, the internal paths for your fonts (especially when using a plugin like "Use Any Font") often remain hardcoded to the old staging address. Because browsers block "Cross-Origin" font requests for security, your live site is likely being prevented from loading the fonts hosted on your staging server.
1. Update Your Font Paths
Since you are using the "Use Any Font" plugin for your headlines, the most direct fix is to refresh its internal settings on the live site:
Go to Use Any Font in your WordPress sidebar.
Delete the current font assignment for Gloock and re-upload/re-assign it. This forces the plugin to generate new CSS paths using your profitwisehq.com domain instead of the staging one.
2. The Salient Typography Sync
For your body copy (Manrope), Salient's internal CSS compiler needs to be "reminded" of the new domain to generate the correct @font-face rules:
Navigate to Salient > Typography > General Typography.
Simply click the "Save Changes" button at the bottom of the page (even if you don't change any settings). This triggers Salient to re-write the dynamic CSS file with the correct live URLs.
3. Clear the Salient Internal Cache
This is the most critical step after any migration. Salient stores a "compiled" version of your CSS to improve speed, and it is likely still holding onto staging references.
Good afternoon,
I'm having issues where the font used on our staging server is not translating to the live site?:
Staging:
https://staging.schiavocreative.com/profitwise/
Live:
https://profitwisehq.com/
Headlines: Gloock (Had to add plugin "Use Any Font")
Body copy: Manrope
Hello Eddie!
Thanks for writing in!
It looks like you've hit a classic "URL mismatch" issue that often occurs during WordPress migrations. When you move from a staging URL to a live domain, the internal paths for your fonts (especially when using a plugin like "Use Any Font") often remain hardcoded to the old staging address. Because browsers block "Cross-Origin" font requests for security, your live site is likely being prevented from loading the fonts hosted on your staging server.
1. Update Your Font PathsSince you are using the "Use Any Font" plugin for your headlines, the most direct fix is to refresh its internal settings on the live site:
-
-
2. The Salient Typography SyncGo to Use Any Font in your WordPress sidebar.
Delete the current font assignment for Gloock and re-upload/re-assign it. This forces the plugin to generate new CSS paths using your profitwisehq.com domain instead of the staging one.
For your body copy (Manrope), Salient's internal CSS compiler needs to be "reminded" of the new domain to generate the correct @font-face rules:
-
-
3. Clear the Salient Internal CacheNavigate to Salient > Typography > General Typography.
Simply click the "Save Changes" button at the bottom of the page (even if you don't change any settings). This triggers Salient to re-write the dynamic CSS file with the correct live URLs.
This is the most critical step after any migration. Salient stores a "compiled" version of your CSS to improve speed, and it is likely still holding onto staging references.
Clearing cache: https://themenectar.ticksy.com/article/6226/
Hope this helps!
Best,