Translation is not automatically linked to the original blog post

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is trying to add a translation to a blog post using the WordPress Editor, but the translated blog post is not automatically connected to the original English post and exists as a separate entity unless manually connected.

Solution:
The problem turned out to be because of NGINX security headers that they added recently to improve the website security. Specifically these two:

add_header Referrer-Policy "strict-origin";
add_header Permissions-Policy "geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self)";

Removing these headers fixed the issue.

If the problem continues, please visit our support forum and open a new ticket for further assistance. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.

If this solution does not apply to your case because it might be outdated or not relevant, please do not hesitate to contact us by opening a new support ticket at our support forum.

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: Exception

This topic contains 16 replies, has 2 voices.

Last updated by Waqas Bin Hasan 4 months ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
August 26, 2024 at 3:13 am
August 26, 2024 at 9:20 am #16103490
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for the new staging site. But unfortunately after submitting login, it takes too much time to load wp-admin and then times out. So I'm not able to check at this moment but 'll circle back later. However, in the meanwhile, our team enabled headers in the sandbox site and confirmed via that security scan (hidden link). So the headers are applied and it works fine in the sandbox site. Can you please remove these headers in your staging site temporarily and recheck for the issue? If issue still persists then it is not related to the said headers and we can look into that direction. Please let me know.
August 29, 2024 at 4:02 am #16117430
federicoB-41	Hello Waqas. Both headers (Referrer-Policy and Permissions-Policy) are not enabled on the staging website I shared with you. How did your team add headers to the sandbox website this time? Via plugin or directly to the NGING config file? Please let me know. I tested it multiple times on live environment and on staging, and the issue happens only when those 2 headers are enabled.
August 29, 2024 at 7:49 am #16118026
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Team added headers using the https://wordpress.org/plugins/http-headers/ plugin. - After activation, go to Settings > HTTP Headers > Advanced Settings > Use PHP to send headers (deprecated). - In the plugin settings, you can add custom headers. You’ll find a form where you can input header names and values. Add Security Headers: For the Referrer-Policy header, set: Header Name: Referrer-Policy Header Value: strict-origin For the Permissions-Policy header, set: Header Name: Permissions-Policy Header Value: geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self)
September 3, 2024 at 7:26 am #16134160
federicoB-41	Hi Waqas. Thanks, that solution worked.