WPML

Elementor – Custom Fonts Cause CORS Policy Issue with Different Domains per Language

Published Updated

Overview of the Issue

When using Custom Fonts with Elementor and Different domains per language, a Cross-Origin Resource Sharing (CORS) Policy issue arises. The custom fonts are always loaded from the original domain, leading to CORS policy errors.

Workaround

This issue is fixed in WPML Multilingual CMS 4.7.4. Updating solves it on your site, so you only need this workaround if you can’t update yet.

  • Go to WPMLSettingsPost Types Translation
  • Set the post type Custom Fonts (elementor_font) to translate.
  • In the same page but in the Custom Fields Translation section, set the custom field elementor_font_files to translate.
  • Open your translation in ATE.
  • Search for '.ttf’ file.
  • Once you find it, translate the domain URL for the right one.
  • Go to ElementorTools.
  • Press the to Regenerate Files & Data button.
  • Clear browser cache.

Still Seeing This Issue?

If updating doesn’t fix it, ask a support question and we’ll look into it with you.

Ask a support question

All known issues