I have several custom fonts entered into ‘Font View’ with an absolute path to the .css file to use in a Paragraph encoded text box like so:
Font name: Sample Font
Alternative Fonts: Arial
Font Type: Sans-serif
URL: https://developer/mysite.com/sample-font-store/csample.css
I found that once entered with this absolute URL, I cannot change the URL entry to just ‘http’ or a relative path: /mysite.com/sample-font-store/csample.css or http://mysite.com/sample-font-store/csample.css as it does not then recognise the .css file as before:
So I created a new font with a new Font Name as a test and right away gave it the ‘http’ public access url and it worked just fine. So the issue seems to be the persistence of the original.
Anyone had experience of this, as any clue would be helpful?
Thanks, Adrian
Hi Adrian,
I can’t reproduce your report that the original URL is persisting despite being changed. You can easily test whether this is happening by switching to Xway’s HTML view and checking to see if it outputs the original URL or the changed URL (it outputs the changed URL for me).
Changing a URL from https to http will normally prevent it from working if you use it from a page that has https access: browsers don’t allow you to access an insecure (http) URL from a secure (https) page.
Protocol-relative URLs (which use the same protocol as the page they’re linked from) should begin with a double slash (//).
Hi Jeremy,
Your explanation has helped me understand that when creating a New URL in Font View, Xway will only accept an ‘absolute’ path to the css file. Anything less produces “This is not a valid URL”.
When styling paragraph text with a custom font I guess it makes sense. I was hoping to use ‘relative’ paths in my development subdomain, /sample-font-store/csample.css, but I’ll just have to update the paths when uploading the final files by removing ‘development’ from the path beforehand:
https://development/mysite.com/sample-font-store/csample.css
to
https://mysite.com/sample-font-store/csample.css
Many thanks,
Adrian
Is there a reason you can’t use https://mysite.com/sample-font-store/csample.css while you’re developing your site?
I can log a feature request for Xway to support relative (and protocol-relative) font paths in future, but this might not work well for local previews.