Before this ticket gets assigned to my colleagues, I will try to help.
From what I can see, most of the content is already in French at the URL that you shared (although I don't understand why it exists under "/en" instead of the main domain).
In regards to the strings that are still not translated, the proper way to translate strings depends a lot on how they have been implemented inside the theme/plugin.
IMPORTANT: Sometimes, there are even duplicates of the same string and only one of them is the correct one that needs to be translated.
Also, sometimes, simply removing the string (checking the box and removing it) and then re-registering it again by scanning for it (one of the methods below) and re-translating it resolves the issue (sounds like you did this already so let's focus on finding the duplicates that are still NOT translated).
Method 1:
Go to WPML > String Translation and at the bottom of the page you will find a checkbox called "Look for strings while pages are rendered". You can enable (check) that and then go in the front end to a page where you have that string showing up and then go back to WPML > String Translation and search for that string and see if it now shows up.
Method 2: If you can't find them inside the WPML > String Translation, they might be added as admin text.
Sorry, it's been a pretty full queue in the past few days.
I would have been interested in finding out if you were able to follow step 1, too, because that might help us find some extra strings with the same wording that need to be translated, too.
As I said there at point 1, sometimes there are duplicates that need to be translated, too.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of the site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box.
Sorry for the delay, I was already having most of my reply written but I did not sent it because I was still trying a few more things.
This is not the typical scenario where an issue can be resolved in a very short time.
It takes a while to try to understand how things were created and set up, sometimes that can take the most time (it is always easier when you built everything from scratch yourself and you know the site inside out but unfortunately this was not the case here for me). Especially when there are a lot of plugins (many JET plugins which can get pretty complex at some point).
What is also a bit weird in this current site setup is that, even though the default language has been set to "French", the content was initially created in English.
This one is the original page: hidden link
This one is the translated page: hidden link
It should be the opposite if French is set as the default.
The quickest way I initially though this ccould be handled was:
1. Edit the EN page directly in Elementor and change the content and language as you wish
2. Edit the FR page directly in Elementor and change the content and language as you wish
BUT that did not work, because, the "Edit with Elementor" option does not show up on this site for the default page + the translated page. When you try to open the translated page and the default page with Elementor, they will both get us to the same backend edit page, so no matter which one you will edit, the change will show up in both languages (I tried for example to translate the "Booking Inquiry" title, the one at the top of the form on the right area, and when I changed it in French with "Demande de réservation", the same change showed up on the homepage, too).
So, it would definitely help if you can explain a bit more to me how these pages were initially created, from where, and with which tools.
From the code of the page, they seem to be Elementor, but, something has to be custom or handled by (at least one) of the other plugins that are currently active that is causing this behavior: to make the change in both languages.
Can you please explain to me a bit more about how these pages were created?
In the meantime, I am also still trying to find a workaround at least.
Thank you for helping with any extra info that you can share on this matter.
PS: By looking at your last reply and at the current ticket status, I think you might have closed the ticket by mistake but I am opening it back again in case you still need help with this.
Another extra piece of valuable information (after it took me a lot to figure where things are) is that it seems that there is not translation for the booking form (you can see that there's a "+" (plus) icon under the French table column on this page which means there's no existing translation - there should be a "pencil" edit icon if there was an existing translation for this form): hidden link
You can also see that, from the way this URL ends, this form was created from the English backend (the secondary language, NOT the default one) but it was created with French words - "DATE D'ARRIVÉE" etc.
The words used in this form, as long as it was created from the EN backend should be in English, and only after the form is fully created in EN and saved, only then the form can be translated to French where we would use French words.
At the moment what we know is that the content was built IN FRENCH but from the EN backend (instead of the FR backend), which is why things might be confusing.
The topic ‘[Closed] Translation doesn't appears’ is closed to new replies.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
