6.0.3 BUG custom font problem

Support
#1

hi there,
added custom fonts does not display correct in builder and frontend. different font will be displayed.
do you need further informations?

greetings
harry

#2

Hey @deranaloge,

Thanks for posting in! The Pro 6.0.3 version is supposedly to resolve the font issue that was assured by @Charlie. Would you mind providing us your WP Access so we can check your installation pertaining to your issue? It could just be some caching issue which usually happens every after doing updates. You can create a secure note in your next reply with the following info:
– Link to your site
– WP login URL
– WP username
– WP password
– WP Administrator Role
– Confirmation that we can access and make changes to your site

To know how to create a secure note, please check this out: How The Forum Works

image

Best Regards.

#3

sure, see secure note

the font i am talking about is the custom font in font manager (cirka medium ?> sub headings)

thanks harald

#4

hey Harald,

I have logged in and investigated your issue. As it turns out, you are having CORS issue.

Mixed Content: The page at 'https://example.com/' was loaded over HTTPS, but requested an insecure font 'http://example.com/wp-content/uploads/PPCirka-Medium.woff2'. This request has been blocked; the content must be served over HTTPS.

This usually happens during the font upload when the SSL (not using https) is not yet set. You can install Search and Replace plugin where you have to search for http://example.com/wp-content/uploads/ and replace it with https://example.com/wp-content/uploads/

Kindly let us know how it goes.

#5

thank you! i dont know if you did anything, but it now works…

cheers

#6

Hi Harald,

Glad to know that it is resolved now. Maybe the CORS problem solved and that is why this problem also solved,

Thanks

#7

I can see the log-in details, you need to remove them and use the private message thing.

#8

Hello @henrybag,

Thanks for reposting it, we have moved the credentials into the secure note.

Thanks

#9

hm thanks for reporting,
but i added it to the secure note? what was the problem?

#10

Hi Harald,

Maybe the CORS problem was fixed and that is why this problem was also solved.

Thanks

#11

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.