FYI: Knowledge Base Custom Domains

[JLX89]

Just putting this out there, pushed some info over to the FreeScout team and they implemented the ability to use custom domains for the Knowledge Base Module (Premium).

Link: https://freescout.net/module/knowledge-base/#custom-domain

Module Changelog: https://freescout.net/module/knowledge-base/?changelog=1

Working to try and test this out today.

[JLX89]

@girish Would it be possible to add Alias to this app now to this app since this was implemented?

[nebulon]

I've published a new app package with multiDomain support. This should fix it.

[JLX89]

@nebulon Perfect, thank you so much for the fast response on this! I've enabled this and tested, looks like there is just an issue with CORS settings allowing assets to be served from support.domain.tld to docs.domain.tld.

Is this as simple as dropping something into the env file or more involved?

LiberationSans-Bold-webfont.woff	blocked		Access-Control-Allow-Origin	Missing Header	
 glyphicons-halflings-regular.woff2	blocked		Access-Control-Allow-Origin	Missing Header	
 LiberationSans-Regular-webfont.woff	blocked		Access-Control-Allow-Origin	Missing Header	
 glyphicons-halflings-regular.woff	blocked		Access-Control-Allow-Origin	Missing Header	
 glyphicons-halflings-regular.ttf	blocked		Access-Control-Allow-Origin	Missing Header	
 LiberationSans-Regular-webfont.ttf	blocked		Access-Control-Allow-Origin	Missing Header	
 LiberationSans-Bold-webfont.ttf	blocked		Access-Control-Allow-Origin	Missing Header	

Thank you!

[nebulon]

@JLX89 this should normally be set by the app itself.

[girish]

@JLX89 Since web fonts are subject to CORS, can you let upstream know that they need to set the CORS headers in the app for the resources they expect to be accessed across origin?

[JLX89]

Thanks @girish and @nebulon — looks like an app restart fixed this.

[nebulon]

@JLX89 we purchased the module now as well and were trying to get it to work, however at least in our instance we didn't manage to get the app send the CORS headers. Can you double check if things are working for you and also do you remember which exact steps you have done?

[JLX89]

@nebulon This was working initially, but I ended up clearing my cache for some other reason and it seems like it's not working now.

Based on what I've been looking at, it seems like the Laravel CORS API isn't enabled / installed in FreeScout -- so this might be a bug that needs fixed from FreeScout.

[nebulon]

@JLX89 alright, so I guess we have to report this upstream then. Usually they are quite fast to fix things.

[nebulon]

I have opened an upstream issue now at https://github.com/freescout-helpdesk/freescout/issues/2287

[nebulon]

This was fixed upstream and it now works for us. https://github.com/freescout-helpdesk/freescout/issues/2287

[JLX89]

@nebulon Thank you so much, fixed on my side also!