This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues where the translated version of your page does not match the front-end display, showing an old template homepage with outdated themes and texts, despite correct strings in both Italian and English in the editor. Solution: We recommend duplicating the page from the primary language and translating it again. After this, edit the translated version with your page builder and save it. This approach resolved similar issues related to icons and styling. Additionally, ensure that your WordPress memory is sufficient, as insufficient memory can prevent page options from being saved correctly in translations. You can check and address WordPress memory issues here: WordPress Memory Issue.
If this solution does not apply to your case, or if it seems outdated, we 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 issues persist, please open a new support ticket with us for further assistance.
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.
Background of the issue:
Solve the ticket (I don't know why is marked as "solved" without my feedback) on date August12, 2024 a 9:38 am, with your operator Carlos Rojas.
I follow the instruction but the problem persists. If I can't solve it, I have to request the refund.
Symptoms:
when I duplicate a page in english, the pages on the frontend are shown with the old, deleted template
Thanks for reaching us and I apologize for the delay in response.
I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
It's not so.
The original language is italian and I want the same page in english.
On your editor, all the strings are correct, both italian and english, but on the front-end there's no matching and I see the old template homepage (!), with old theme (nowadays deleted from wy WP) and old texts.
Thanks
I see the issue now. It looks like this domain hidden link is using a different WordPress installation. Even after deactivating the WPML plugin here hidden link , the domain hidden link is still loading.
Please check with your hosting provider to see if you have a different WordPress installation.
Thanks, finally my customer show me the website's file manager. Effectively, there was a WordPress setup on the /en folder...no one told me that the old website was built in this way. Thank you.
Now I see the translate page (cbox.cloud/en) but I miss a lot of style, why?
Thanks
I compared both pages hidden link and hidden link and I noticed that both page layouts are the same but the icons show different sizes. Could you try replacing the icons and retranslating the page again?
I duplicated the page from the primary language page and translated it again. Then I edited the translated version with the page builder and saved it again. This resolved the issue with the icons and styling.
It appears that the problem with the translated page options not being saved was due to insufficient WordPress memory, as indicated here: hidden link . Once this issue is addressed, your future translations should function correctly.
