Open
Reported for: WPML Multilingual CMS 4.6.9
Overview of the issue
In some cases, when using custom page templates, the selected template is not correctly applied to translated pages.
Workaround
To ensure the custom page template is correctly applied to the translated page, follow these steps:
- Delete the relevant entries from both the
wp_postsandicl_translationstables.
OR
- Switch to the secondary language using the top admin bar, then go to Appearance > Editor, locate the translated template, and delete it.
- In WPML > Settings > Page URL, enable “Translate” for Slug Translation (this ensures the template slug is included in the translation instead of being auto-generated from the title).
- Open the file: wp-content/plugins/sitepress-multilingual-cms/classes/full-site-editing/BlockTemplates.php
- Around line 56, comment out the following line:
1
$postData['post_name'] =$post->post_name; - Resend the template for translation.
- When translating the template, make sure the slug is correct and includes the translated page or taxonomy slug.
Hello
How is it possible that wpml is not compatible with the theme éditor?
I find it hard to believe. Do you confirm?
Hello there,
WPML is compatible with the theme editor. However, there could be some scenarios where you can find the issue reported here.
For those cases, please follow the workaround provided.
We will keep this page updated.
The Problem here is: The german and english pages a using different templates. If I wanna select a other template for the translated page, different templates are visble in oppoite to the german original. Its not possible to find a solution. We lost so much time and money to solf this problem and nothing helps!
For this solution here:
To delete a template from the database – > Do I need to delete with phpmyadmin/MYSQL and where in the datanase is it stored???
Is it possible to delete the tempkate in the admin backend in wordpress???
At last: you write to send a template to a page. What does it mean? To select another template for the page in the pageeditor???
Sad to see, that a chargeable plugin needs so much work and time!!!
Hello Dorothee,
Thank you for your comment, and I’m sorry for the trouble you’re experiencing.
1. If you’re not comfortable using phpMyAdmin, you can delete the template from the backend: Switch to 2nd language from the top bar and go to Appearance > Editor to find your translated template and delete it
2. “Send the template to the translation”. You can do this via WPML > Translation Management. Select the template and send it to translation.
3. I saw that you left several comments, I’ll review them all and do my best to provide answers. If the steps in this erratum aren’t clear, or please open a support ticket so we can assist you directly.
And another thing: I dont wanna delete my templates. I need controll about for pages/posts, what template should be use!
Hi,
Just to clarify, you don’t want to delete your templates in the primary language. You want/need to delete the template in the secondary language. You can do it from the WordPress dashboard, without touching the database. Don’t hesitate to open a ticket if you need further assistance. Our supporters will be happy to help!
We use the twentytwentyfour theme, we cant see a possibility to delete templates! This is the satndatr template for wordpress, we use it because all plugin are most compatible… what about wpml?
We swiched of all plugins (only wpml is acktive) an wordpress and the plugin are in the newest version! Same problem is going on!
Hi,
This errata is still open, which means that the issue is not resolved yet. You will have to follow the steps described above in the workaround section.
in your “forum” i find people with the same problem, but nowhere is a solution for the problems snd the tickets are closed, its not anymore possible to answer…
Hi,
Could you please open a new ticket? Our support team will be happy to assist you personally and help resolve the issue.
Hi,
I am already working with the support team, however, I would like to add that WordPress will not allow deletions as stated in a previous chat here. I have been trying to have this fixed, and I have not been able to publish my site due to this. WordPress support stated there needs to be a different solution. I have to say I am quite disappointed. For the money I paid it should be seamless.
Hi there,
Thanks for reaching out. The priority of this issue was raised recently; however, due to other development priorities, our team wasn’t able to work on it in time for today’s release.
We appreciate your patience and understanding as we continue working toward a resolution.
How Nicolas, I appreciate your reply!
I do hope you understand the frustration that it has now been going to past 10 days, and an answer cannot be figured out. I would kindly ask if you are able to add second tech to my case. I believe, in your site it states there is support 6 days a week, 22 hours a day, and one cannot afford 1 reply every 2 days. I would sincerely appreciate your help in this matter. As I said, if you could please add a second, and I’ll add the as admin if you give me an email address.
Alternatively, perhaps you may be able to provide a specialist as a courtesy. I understand some may be less limited in availability.
Best regards, and looking forward to hearing from you.
Rovena
Hello,
We’re currently experiencing a higher volume of support requests, which is affecting response times. But support tickets and live chat are still the best ways to reach us!
I checked your ticket, and Bobby is actively handling it. Thanks for your patience and comprehension.
How come that this issue is still not solved, 15 months after this Errata was started?!
Hi Pieter,
Thanks for your message. It’s still being worked on. We’ll share updates as soon as possible.
Not a real answer to my question Nicolas. It’s quite obvious that it’s still being worked on, otherwise the issue would be closed. Let me rephrase my question then: with so many people using custom templates and so many people running into trouble with this, why does this issue not get the priority it deserves? How is it that a known issue remains unresolved for more than 15 months?!
Hi,
I hear you. The priority of this issue has been raised, I’ve added your comment to the internal ticket, and asked our dev team if the fix could be expedited and included in one of the upcoming releases. We’ll keep this page updated.