You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initially reported at https://forum.cloudron.io/topic/7702/fyi-knowledge-base-custom-domains which already has some context.
So when a custom domain is set for the knowledge base, the Access-Control-Allow-Origin headers are not sent from the main domain. This affects at least the fonts.
One solution is to set those headers accordingly or maybe all resources should be fetched using the custom knowledgebase origin.
The text was updated successfully, but these errors were encountered:
We've checked - when Knowledge Base is opened on a custom domain all CSS files are loaded from the custom domain too, including fonts CSS: https://demo.freescout.net/css/fonts.css
And fonts CSS have file relative paths to fonts (../../fonts/liberation-sans/LiberationSans-Bold-webfont.eot), so there should be no problems with fonts being requested from another domain.
Initially reported at https://forum.cloudron.io/topic/7702/fyi-knowledge-base-custom-domains which already has some context.
So when a custom domain is set for the knowledge base, the
Access-Control-Allow-Origin
headers are not sent from the main domain. This affects at least the fonts.One solution is to set those headers accordingly or maybe all resources should be fetched using the custom knowledgebase origin.
The text was updated successfully, but these errors were encountered: