Skip Navigation

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

Problem:
The client is unable to see URL slugs in the page translation UI when trying to translate a new page URL slug, despite following the guide on translating page slugs. This issue is inconsistent across different environments and accounts.
Solution:
1. Make a minor edit to the page in the default language and update it. Then, check if the translation shows the URL slug correctly.
2. If the issue persists, create a new test page or post, add a translation, and see if the slug appears in the editor.
3. Clear your site's cache as it might be a caching issue affecting the visibility of translated slugs.
4. If none of the above steps resolve the issue, it could be helpful to test using a different user account to see if the problem persists.
5. For further troubleshooting, especially if the problem occurs only in specific environments, provide temporary access to your site for detailed investigation by the WPML support team.

Please note that the solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.

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.

This topic contains 2 replies, has 0 voices.

Last updated by rannooo 3 weeks, 2 days ago.

Assisted by: Bobby.

Author Posts
November 29, 2024 at 4:11 pm #16460577

rannooo

Background of the issue:
I am trying to translate a new page URL slug following the guide at https://wpml.org/documentation/getting-started-guide/translating-page-slugs/. This process worked well before.

Symptoms:
URL slugs are not shown in the page translation UI.

Questions:

November 29, 2024 at 7:04 pm #16460954

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

Please try the following:

1. Edit the page in the default language and make a small edit then update, once finished click on the translation, is it showing OK now?

2. If step #1 does not work, please add a new test page/post and then add a translation, does it pull the slug in the editor?

Let me know your results, please.

November 30, 2024 at 6:47 pm #16462235

rannooo

No and no :/

December 2, 2024 at 6:47 pm #16468151

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)

**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **

I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.

NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.

Thank you,
Bobby

December 5, 2024 at 8:19 am #16479751

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Thank you for the access details!

I am currently reviewing this issue and will update you shortly.

December 6, 2024 at 12:10 am #16484173

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

Please try this:

1. Edit the translation in the ATE
2. Use the search field and search for the slug for example 'About Us'
3. You will notice that it's 100% translated automatically and also you can adjust it in the editor.

Also, I was able to find it at the bottom of the ATE editor without searching. (see screenshot )

Is there a specific page/post that we can test where the issue is currently present?

Screen Shot 2024-12-05 at 3.50.19 PM.png
Screen Shot 2024-12-05 at 3.48.59 PM.png
Screen Shot 2024-12-05 at 3.47.03 PM.png
December 6, 2024 at 6:08 pm #16487188

rannooo

Yes, I can confirm it works with About us page. But it doesn't work on the "Download Mobile App" page :/

December 7, 2024 at 1:04 am #16487829

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

Hi there,

When I click on the translation I can see the URL now.

Possibly a caching issue?

Try and let me know your results, please.

Screen Shot 2024-12-06 at 5.03.32 PM.png
December 9, 2024 at 7:59 pm #16494953

rannooo

Yeah, I can now see that it works on Staging env. But it doesn't still work on my Production env. How could I make it work there as well?

December 10, 2024 at 7:26 pm #16500211

Bobby
Supporter

Languages: English (English )

Timezone: America/Los_Angeles (GMT-08:00)

I did not make any changes or take any other steps from the ones here:
https://wpml.org/forums/topic/url-slugs-are-not-shown-in-the-page-translation-ui/#post-16484173

Please verify that the settings are correct on the live environment and try the steps above then let me know your results.

Also, before testing clear your site's cache.

Another test is to sign in with another user account and see if the issues persist that way.

If it does, I'd like to take a closer look. (you can update the previous private reply with access to the live site if needed)

December 11, 2024 at 1:44 pm #16503886

rannooo

Very weird. I created myself another account and there I could translate the URL slug. Though, it wasn't auto translated. I hope this is the last time I have to create another account to do translations correctly 😀 Thank you for the help!