[Resolved] Issues with translating a specific page, and other elements
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing a 404 error when trying to access the translated version of the /map/ page on their website. Additionally, they are unable to find specific strings for translation on the homepage and member map block. Solution: To address the 404 error, we recommended checking if the page is not in draft status and ensuring that the translation process was followed correctly. For locating and translating the missing strings, we advised the following steps: 1. Navigate to WPML → String Translation. 2. Enable the option 'Look for strings while pages are rendered.' 3. Visit the page where the untranslated strings are displayed. 4. Return to WPML → String Translation and check if the string is registered. 5. If found, proceed to translate the string. For more detailed guidance, visit https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/ If these steps do not resolve the issues, we recommend opening a new support ticket. It's also advisable to check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us through the WPML support forum at https://wpml.org/forums/forum/english-support/.
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:
I'm trying to translate the new /map/ page on my site hidden link to all required languages using WPML.
Symptoms:
When I view the translated /map/ page in another language, I get a 404 error (e.g. hidden link). I also can't find the strings to translate 'Not your closest help centre? Find it on the map' on the homepage or 'Please note: you will need to accept cookies to see and use our map.' on the member map block.
Questions:
How can I resolve the 404 error when accessing the translated /map/ page?
Where can I find the strings to translate the specific phrases on the homepage and member map block?
Could you please provide screenshots showing how you translated the page? Additionally, can you share how you created this page?
Please make sure that the page is not in draft status.
Regarding your other question, have you tried to locate the strings by following these steps?
1. Go to WPML → String Translation.
2. Enable the option "Look for strings while pages are rendered."
3. Visit the page where the untranslated strings are displayed.
4. Return to WPML → String Translation and check if the string is registered.
5. If it is, you can proceed to translate the string.
If you are still unable to find the strings, could you please open a new ticket for this issue? This will also assist other users facing similar problems in finding solutions when they search the forum.
On the first point, the /map/ page is published, and was created in WordPress within Pages in Gutenberg. The page itself doesn't feature any text, but has a block and a summary, which has been translated.
To translate this page, I went to WPML > Translation Management.
In "Select Items for translation", I found and selected the map page only
In "Select translation options" I chose all available languages to translate, then chose "Translate automatically".
I can see the translations are there in the Page menu, and I can edit them, but when I go to the expected page URL, e.g. hidden link, I get page not found.
I will reply separately on the string translation issue.
Unfortunately, when I go to the WPML > Translations page, the translations queue doesn't load (please see screenshot), so I can't approve them that way.
When viewing errors in the console, I see the following two issues:
GET hidden link net::ERR_ABORTED 404 (Not Found)
TypeError: Failed to construct 'URL': Invalid URL
at app.js?ver=4.6.13:601:357476
at K_ (app.js?ver=4.6.13:601:357554)
at Go (app.js?ver=4.6.13:571:57930)
at _s (app.js?ver=4.6.13:571:104169)
at cu (app.js?ver=4.6.13:571:96717)
at su (app.js?ver=4.6.13:571:96642)
at Zs (app.js?ver=4.6.13:571:93672)
at app.js?ver=4.6.13:571:45314
at t.unstable_runWithPriority (app.js?ver=4.6.13:579:3844)
at Wa (app.js?ver=4.6.13:571:45023)
I have made the change to the app.js file but no change to the Translations admin page.
I'm receiving the same error message, would we expect the app version to have increased - is it somehow still using the same cached version? app.js?ver=4.6.13
TypeError: Failed to construct 'URL': Invalid URL
at app.js?ver=4.6.13:601:357476
at K_ (app.js?ver=4.6.13:601:357554)
at Go (app.js?ver=4.6.13:571:57930)
at _s (app.js?ver=4.6.13:571:104169)
at cu (app.js?ver=4.6.13:571:96717)
at su (app.js?ver=4.6.13:571:96642)
at Zs (app.js?ver=4.6.13:571:93672)
at app.js?ver=4.6.13:571:45314
at app.js?ver=4.6.13:579:3844
at Wa (app.js?ver=4.6.13:571:45023)
So, basically, we are returning the original issue that was reported. Is this occurring on a specific page, right? Or will the problem be the same if you create another new test page?
The process for translating pages appears to be correct.
Does the same issue occur if you temporarily turn off all plugins except WPML?
Hi Andrey,
Thanks for your suggestion - I have switched off a number of less important plugins and the issue has resolved.
I will investigate which plugin is causing the issue, but I believe this ticket can now be closed.
Best regards,
Greg