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.
Tagged: Performance
This topic contains 25 replies, has 1 voice.
Last updated by elenaP-6 2 weeks, 1 day ago.
Assisted by: Bobby.
| Author | Posts |
|---|---|
| April 17, 2026 at 7:49 am #17976145 | |
|
Bobby WPML Supporter since 04/2015
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
Thank you, I received it and was able to access the site using it OK. I have updated our team with the findings and I will be updating you as soon as there are news. |
| April 21, 2026 at 7:02 am #17982661 | |
|
Bobby WPML Supporter since 04/2015
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
We are still working on this and will update you as soon as there is feedback, thank you! |
| April 21, 2026 at 11:12 am #17983802 | |
|
elenaP-6 |
Thank you very much Bobby! Looking forward to receiving news from you |
| April 22, 2026 at 9:49 pm #17988775 | |
|
Bobby WPML Supporter since 04/2015
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
We have made progress and identified 3 possible cases. - Users are missing key capabilities (we have a script to reset this) - Solid security plugin possible - Theres a custom code we located that could also be causing issues that is blocking full access to the REST API to further test it would be great if we had full access (without temporary plugin use ) on the staging site. At the moment we have it for the live site but as you can imagine tinkering on the live site is dangerous 🙂 |
| April 23, 2026 at 7:52 am #17989389 | |
|
elenaP-6 |
Hi Bobby, sure you can "play" on the development site. I will send you in a private mail (to your private email address) FTP access to the development server and create a standard adminstrator profile for you. I will send everything via private mail to your personal address Thanks |
| April 24, 2026 at 10:10 pm #17993963 | |
|
Bobby WPML Supporter since 04/2015
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
Received. Thank you! |
| April 28, 2026 at 4:40 am #17998326 | |
|
Bobby WPML Supporter since 04/2015
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
Thank you for your patience. I have resolved those 403 notices from the console, can you please verify if you are still seeing them ? Curious to know if this is profile specific or if the solution was applied globally. We also detected what is causing this and will be resolving it in upcoming versions. |
| April 28, 2026 at 7:46 am #17998745 | |
|
elenaP-6 |
Hi Bobby, I actually can still see the console 403 error message both in the development site and in the live site. I am not sure I did understand what you did. The development site looks to have at the moment all the plugins deactivated except for WPML CMS. I also did not understand when you say "Curious to know if this is profile specific or if the solution was applied globally". I am uploading the screenshot of both consoles |
| April 28, 2026 at 6:49 pm #18000939 | |
|
Bobby WPML Supporter since 04/2015
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
Thank you, that gave me the answer I needed 🙂 So we found what is causing this 403 errors and will be including a fix but in the meantime the workaround has a few steps. 1. In the backend, open Console and paste the following then hit enter:
console.table({
core: window.wpApiSettings?.nonce,
contentStats: window.wpmlContentStats?.nonce,
endpoints: window.wpmlEndpoints?.nonce,
updates: window.wpmlUpdates?.nonce,
posthog: window.checkPostHogShouldRecord?.nonce,
});
2. next you will get a table, now add the following code in the console and hit enter window.wpmlEndpoints.nonce = window.wpmlContentStats.nonce; This should resolve the 403 errors. Afterwards you can refresh and test again and it should be gone. The reason this is happening is because core and contentStats nonces are identical, so it should work fine. But endpoints are different, shown in the table generated after running the first code. |
| April 28, 2026 at 9:01 pm #18001082 | |
|
elenaP-6 |
Thanks. I did what you say but it doesn't resolve the error. See my screenshot attached. I refreshed the page and the error is still there. |
| April 29, 2026 at 7:23 pm #18003940 | |
|
Bobby WPML Supporter since 04/2015
Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00) |
Thank you for updating me! please go to your theme's functions.php and add the following code.
add_action( 'admin_enqueue_scripts', function () {
if ( ! function_exists( 'wp_add_inline_script' ) ) {
return;
}
wp_add_inline_script(
'wpml-content-stats',
'window.wpmlEndpoints = window.wpmlEndpoints || {}; window.wpmlEndpoints.nonce = "' . esc_js( wp_create_nonce( 'wp_rest' ) ) . '";',
'before'
);
}, 1000 );
With this script you will not need to perform the steps I provided above. Our team has also included a fix for this in the upcoming version of WPML. |
| April 29, 2026 at 7:48 pm #18004012 | |
|
elenaP-6 |
Fantastic Bobby. Thank you so much. The code solved the problem! I imagine I can delete the code from functions.php once the new WPML version will be issued. |



