Custom font not saving to font manager

Beta
#1

custom fonts
custom fonts256×872 16.6 KB

So I can load a custom font file and save the custom font. But when you assign that font in the font manager it comes up in the select box you can select but if you save it doesn’t save. Also another thing is I notice I can’t select the bold option 800 to align with the custom font that has been loaded.

The other font is custom as well but uses 400 and 700 and has the same issue of not saving selecting those two so not just due to not being able to select 800 font weight which may be an extra reason this one isn’t saving after assigning it.

Hopefully it makes sense let me know if need any other info.

1 Like
#2

Hi @quentosity,

Thanks for sharing this. Once we get the next beta out, could you let me know if this is still an issue? We fixed some issues in the font uploader that might be what you’re referring to here.

1 Like
#3

Ok checked and this issue is still occurring on beta4 changed to standard woff rather than woff2 since it is supported and know have had issues with woff2 on normal theme and checked the woff font as custom working fine on stable version correctly so not issue with the font.

Let me know if you need any more info for testing. And looking forward to testing more things in beta4 archive mode got me pretty excited.

#4

Thanks! I really appreciate it. I’ll check it out again and report back here.

#5

Sorry about this, there was an issue where the whole font config wasn’t getting saved. We fixed that for the next patch we’re getting ready to push out.

1 Like
#6

unable to select custom fonts
unable to select custom fonts563×595 33.4 KB

Ok updated to beta5 I noticed it seemed to have error saving at first so I deleted the custom fonts and saved as normal one then tried re-adding in screenshot you can see the option for custom font ‘Graphik’ but it doesn’t seem to allow me to select the font for saving.

1 Like
#7

Hello @quentosity, I ran into exactly the same error a few days ago. The uploaded custom font is showing but I’m not able to select it or save it.

Similar things happened when trying to install a footer from the design cloud, it prompts that it is installed, but when going to the footer templates the newly installed footer doesn’t show anywhere.

Cheers

1 Like
#8

Just noting still not working in beta6.

2 Likes
#9

Thanks Jay! Will confirm here once I’ve checked into it again. There might be an issue with fonts added in an earlier beta :confused: We will make sure it works with fonts added in the previous official version and new updates moving forward. Thanks for your patience with us as we get these things sorted out.

#10

I think we finally got this sorted out for beta 7 (will be out shortly).

3 Likes
#11

This is now working on my end! Thanks @alexander :+1:t3:

#12

Great! Glad to hear that.

#13

I still cant use custom fonts :frowning:

#14

Ok so it is now saving and loading in the font manager. But not outputting as style sheet on the frontend so not working. I checked this comparing stable theme and pro and that seems to be the only thing wrong e.g. screenshot highlighting the style that wasn’t included on beta version. When I manually add this styling with correct url to CSS it works so that seems to be the only issue now.

image
image1443×141 13.2 KB

1 Like
#15

@ERES I checked and maybe the domain is down? (or typo) Couldn’t get the link to open.

@quentosity I was looking into this again and think I found the pattern. Puzzling because it’s all been working on my end. I noticed from your screenshots you uploaded both WOFF2 and WOFF files so I did some more testing with combinations like that. I’m not sure when this happened, but I think at some point in a WordPress update then changed the detected MIME type of .woff to the standard of font/woff instead of font-woff. This is why you could have uploaded both file types and one is missing. I’ve adjusted our MIME type setup to account for both variations.

What I suspect is happening is that after you save the configuration on the latest version is it stripping out the woff file and considering it invalid. Sorry that this issue keeps dragging out! Please let me know if the next patch works for you. If you don’t mind sharing login credentials I could install a development build for you and test it directly on your site.

#16

No Typo and the website is up and running… I only uploaded the woff2-files.

#17

My fault, I’ve been working in Brave and apparently when they see a 503 (error code from under construction) they show a browser error page similar to the whole site being down.

Looks like @font-face styles are missing as well. Would you mind sharing admin credentials in a new thread? I’ve not been able to reproduce any other font related errors so I’m at a loss at the moment for why this is still happening. Thanks!

#18

@alexander I have now added a secure note to eariler reply with admin details and cpanel details if you need to theme there. Forgot to mention currently the style code for this is in the theme css as I was testing that is works just adding it manually.

#19

@alexander I think I also ran into a bug (but not sure, maybe I just did something wrong).

I uploaded a custom font and I managed to save and use it. Now the problem is that the custom font is showing up on all my Windows and Android devices, but on none of the Apple devices that I tested it on.

#20

@quentosity thank you! I will login (hopefully tomorrow) and check into that.

@SchoonhovenOntwerpStudio if you wouldn’t mind sharing login credentials as well on a seperate thread, I could check out what’s going on there too. Thanks!