Good morning.
I’m very much a noob (old noob).
I have created a basic website in sitejet builder cpanel (ukhost4u). The only things I have done that are outside site jet builder are install a third party SSL Cert and force SSL by adding “htaccess” script in cpanel file manager.
So my issue is fonts not displaying properly on the published site. On safari Mac I get, I thing sans serif and on iPhone I get Times. Same thing using Chrome on both.
In Safari Inspector I can see a string of “failed to load resource…404 error” for fonts that are called for. Also can’t find any trace of uploaded fonts in cpanel file manager. The link for the fonts location doesn’t exist. The only thing in the “g” folder in file manager is a script.
this might be an issue of cPanel. Are you able to contact their support or your hoster’s? They need to check if the files are properly updated on your server upon publishing.
I’m no coder but those file paths to the fonts don’t exist, at least when I look in cpanel file manager. I’ll drop my host (ukhost4u) a ticket and see what they say.
Yes, no worries. Its not your responsibility to know this. Your hoster and cPanel have to figure out what is going wrong there… or (and) our devs need to assist as well, if we can
Submitted a ticket to ukhost4u. Really fast response. But not resolved. Cutting a long story short. I have tried publishing using a MacBook Pro (Safari & Chrome. Neither worked. The font folder structure is not present in cpanel file manager. Still 404 errors.
Then they tried publishing from their end and behold, the font file nest of folders with fonts appeared in cpanel. But website still not displaying correct fonts on Mac or iPhone (they still use default fonts like Times).
Then I tried publishing again from my end and the folders disappeared again
Finally I dug out a Win10 laptop and tried publishing in Chrome on that. Just in case its an Apple thing. No difference. No font folders and files. Not displaying fonts correctly.
Changes to text and layout behave fairly well but there’s something up and it’s beyond my skill level.
To be fair to ukhost4u there has been a quite an exchange of messages all day.
In cpanel file manager I went into public_html/G/fonts.css
renamed the file fonts.csx
back in Sitejet I re-published.
Now in the “G” folder I had created a new fonts.css file AND the whole nest of folders with fonts in the last one that I couldn’t get before forcing a new “fonts.css” file.
still didn’t work the web but progress. One of the nest of folders had the wrong name and so did the font file names. This is in comparison to Safaris web inspectors errors. Still wires crossed somewhere.
So something definitely corrupted fonts wise. So I decided to delete all the selected fonts, non selected fonts and uploaded font files, taking Sitejet Builder back to only having system fonts from the Mac to play with.
Published again.The “G” folder in cpanel file manager - gone. Mac and iPhone defaulting to “Times” font.
Now back in Sitejet I selected one, no more, Google font (outfit) and ticked the boxes it in the fonts menu. Although text font changed in the Designer I had to manually go through all the Headings and select “outfit” font as still showing uninstalled fonts (bug?). Same in a couple of text blocks
Published again and WHOOPIE! Fonts showing correctly on Mac & iPhone.
A long and uneducated fix. Maybe some error trapping is required to prevent old duffers like me spoiling things.
Ok. I jumped the gun a wee bit. It looks like a definite bug.
After checking the website on other machines Win10, Mac & iOS, yet untried, on multiple browsers, the font loading fault still appears. Still reporting as a fault in developer tools (Chrome) 404 error.
So this is what’s I think is happening.
If public_html/g/fonts.css exists then when you edit then publish in Sitejet Builder no fonts folder nest will be created and if the fonts folder nest exists it will be deleted. So font.css must not exist for a successful upload via Sitejet to occur.
Therefore if you’ve viewed the website successfully previously after a successful upload those font files are cached by the browser. Therefore this error goes unnoticed after subsequent edits. At least until the cache is cleared.
Anyone else viewing on another machine WILL get the error, 404 as fonts being looked for do not exist on server (as viewed in cpanel).
Deleting fonts.css (or renaming fonts.css to fonts.csx, for example) BEFORE publishing vie Sitejet Builder forces both a new fonts.css files AND a new nest of folders containing the fonts to be written.
After that all is good.
It’s worth checking, via cpanel file manager, for public_html/g/fonts… after publishing to check this has worked. Don’t forget to refresh the page first. If fonts.cssis the only thing there then delete it and try publishing the site again.
Hopefully a dev will check it out and find a fix because with those font files being cached by the browser it’s an easy error to miss after an edit and re-publish vie Sitejet Builder.
No I didn’t. To be honest I’m still trying to get my head around the relationship between my provider, cPanel and Sitejet Builder. Like who saves what where and how my website design gets published. etc.
So it’s been a learning curve just figuring out who is responsible for what. But I’m getting there.
posting issues in this community is fine. But sometimes, raising a ticket instead is better. It could also be that raising a ticket after you posted here can be the next steps. It all depends on the issue and what info it involves to be solved. I do like when users post issues here, because this is helpful for other users as well - as you never know who might have a similar issue and can see possible solutions. That is, what these communities are for, right?
Anyway, about the relationship: Your first contact should always be your provider unless you have the Sitejet Studio version (Studio is the standalone version under sitejet.io ) They would then get in touch with cPanel support for troubleshooting.
We do also support but ours is limited to issues inside or from the Sitejet Builder. Since most users do not know where and how an issue is happening, it is of course not possible to know where to post. That is why under some posts here or via tickets to us, you might get a response as “Please contact your provider or cPanel directly” - which basically means it is something they have to fix probably.
But, it is totally okay if you feel like posting everything here. I am here to guide you to the right direction.
Hope this helps clarifying it a bit.
Regarding your issue: In this case, you need to really contact your provider so they get in touch with cPanel. It seems that there is a server issue - if we have to provide assistance, cPanel will come to us.
But sometimes, raising a ticket instead is better. It could also be that raising a ticket after you posted here can be the next steps. It all depends on the issue and what info it involves to be solved. I do like when users post issues here, because this is helpful for other users as well - as you never know who might have a similar issue and can see possible solutions. That is, what these communities are for, right?