Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Our wait time is higher than usual, please make sure you are meeting the minimum requirement - https://wpml.org/home/minimum-requirements before you report issues, and if you can take a look at current Known Issues - https://wpml.org/known-issues/. Thank you.
Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 7:00 – 15:00 -
- - - - - - -

Supporter timezone: Pacific/Easter (GMT-06:00)

Tagged: 

This topic contains 0 replies, has 1 voice.

Last updated by arnaudh-8 1 day, 1 hour ago.

Assisted by: Ilyes.

Author Posts
March 18, 2025 at 1:15 pm #16830304

arnaudh-8

Background of the issue:
****Please assign this ticket to Ilyes**** I am experiencing issues with my WordPress site after updating the Elementor and Elementor Pro plugins. I want the fonts on the French version of my website to match those on the English version (which was the case prior to the Elementors updates. Additionally, when I create a new property in English and assign an agent, I want the agent to also be assigned to the translated French property. This is important because the new translated properties are not appearing on the 'À propos' page, which is accessible from the French menu.

Symptoms:
Fonts on the French version of the website changed after updates. Agents are not being assigned to translated properties (french properties), causing them not to appear on the 'À propos' page.

Questions:
How can I ensure that the fonts on the French version of my website match those on the English version?
How can an agent (me) be automatically assigned to a translated property in WPML when creating a new property in the default language (english)?

March 20, 2025 at 2:46 pm #16840660

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

Hey Arnaud,

I'm currently working on your site, I will get back to you asap,

Best,

March 20, 2025 at 2:47 pm #16840663

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

Have you changed the password? The old access is not working for me,

You can share it again using the form below.

March 25, 2025 at 8:57 pm #16859940

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

Hello Arnaud, thanks for your patience,

For the font issue, it seems from the backend, the font is applied correctly : hidden link

The issue only occurs on the frontend, resetting the theme solved most of the font issues,

But some parts are not working, so I checked the console and I found the following error :

arnaudhomburger.fr/:1  Access to font at '<em><u>hidden link</u></em>' from origin '<em><u>hidden link</u></em>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
playfairdisplay-nufid-vyszvivyub_rj3ij__anpxdtzyga.woff2:1 
            
            
            Failed to load resource: net::ERR_FAILED
arnaudhomburger.fr/:1  Access to font at '<em><u>hidden link</u></em>' from origin '<em><u>hidden link</u></em>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
dosis-hhyau5sn9vomlzloc_u.woff2:1 
             

Not to complicate things too much for you, but the .fr domain is not able to access to the custom font files, the issue is not WPML related perse, but related to multisites in general : https://wordpress.org/support/topic/cors-policy-errors-2/

We have a possible solution for that but I would need a backup of your site first: https://wpml.org/errata/elementor-custom-fonts-cause-cors-policy-issue-with-different-domains-per-language/

----

For the agent field, I have changed the custom field to "copy", could you test this new configuration?

The field should become grey in French property (in the backend) as it will be copied from the original since it is the same agent.

Could you test and create a new property to test this new setting?

Best,

March 27, 2025 at 11:15 pm #16870594

arnaudh-8

Hi Ilyes,

Thank you for your assistance!

I tried to create a new property as a test, in the default language and assign an agent, but the agent was not assigned on the french translation. I then deleted the test property so it does not show on my site as it is live. So it does not look like it works.

Also, I tried to update the French translation for this property : hidden link , to assign it an agent (me, Arnaud Homburger) but I cannot do that. How can I assign an agent for the french version of this property?

Regarding the font issue, I noticed that I am not encountering the issue when using Safari or my iPhone, it's only when using Chrome. I thought it was relevant to share this with you before moving on with any setting on your end.

Thank you again for your help.

Best Regards,

March 28, 2025 at 7:13 pm #16874432

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

Hi again,

For the font issue, I would need you to backup your site first, I will then download a copy of your site, test the solution locally first then if it worked, I will apply it on your live site,

For the agent issue, I'm escalating this to the compatibility team, I will take care of it for you,

Thank you for your patience,

Best,

March 28, 2025 at 11:58 pm #16874736

arnaudh-8

Hi Ilyes,

1. Font issue

So just to make sure we are on the same page, like I was trying to explain on my previous note, I noticed that I am not encountering the issue when using Safari on my Mac or my iPhone, no issue with Chrome on my iPhone. The issue with the font only occurs when using Chrome on my Mac.

Question: Does the solution you're thinking about will resolve that issue?

Regarding the back up of my site, how do you proceed? My website is hosted with Hostinger and I think they create a back up of my website once per day. Do you still need ti save a back up of my website in this case? (I guess it's probably safer).

2. Agent assignment issue

Ok, it's well noted.

Thank you for your assistance Ilyes!

April 1, 2025 at 4:36 pm #16883953

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

Hi,

In that case, no need for a backup since you do one everyday,

And yes, I still think the issue could be solved by my solution even if the issue is only on chrome (and btw, it happens for me on edge too, and edge is chromium based, interesting behavior)

I'm reading online about this behavior, and it matches what I found previously with the console error.

I will get back to you with more details today,

April 1, 2025 at 4:57 pm #16884058

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

What is interesting is that the font issue doesn't occur locally : hidden link

But I still want to apply the solution, I get back to you soon,

April 1, 2025 at 5:48 pm #16884233

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

Hello again,

If you access your site using a proxy (a remote device, different device), it is working fine, you can test it here : hidden link

Search for your French site, you will see it is working there, this is totally a browser cookies or cache issue, I'm still digging a little more to see if I can do something about it

April 1, 2025 at 6:12 pm #16884264

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

I have many theories, but mostly, it's possible that the CORS headers are being blocked by other server settings, such as server caching (litespeed), a CDN or firewall rules. Here are some additional things you can check:

Check for a caching layer on the server side: since the issue is not occurring on new sessions (using the proxy site like I mentioned on my previous response) nor the issue is happening locally (no CDN nor server connect cause it is local), it could be caching the previous response without the CORS headers. Clear the cache on both the server and any caching service you're using.

With all honestly, I think this kind of issue will solve itself by the time, but it could be helpful to check if your host is using any kind of cache or CDN that could be affecting the CORS headers.

April 1, 2025 at 6:59 pm #16884396

arnaudh-8

Hello Ilyes,

Thank you so much for investigating on this! It seem complexe to me, I think I am going to leave it like that for now, hoping it will improve by itself then.

Again, thank you for your support, and I wish you a great day!

April 1, 2025 at 7:01 pm #16884426

arnaudh-8

Sorry, reopening the ticket for the agent assignment on the french version. Do you have any update on this one? Thank you Ilyes

April 1, 2025 at 7:56 pm #16884640

Ilyes
Supporter

Languages: French (Français )

Timezone: Pacific/Easter (GMT-06:00)

Yes, the agent issue is already escalated to compatibility (just did it), I will let you know once I get an update.

April 5, 2025 at 1:39 pm #16899972

arnaudh-8

Hi Ilyes,

Ok, perfect, thank you. I am responding late because every time I open a new ticket, by default, notifications are turned off. Just realizing I forgot to turn the notification "ON" for this ticket. It would be great if by default, new tickets would be set to "Email notifications only when WPML support posts an answer ".

Thank you for your assistance!