Background of the issue:
I just started using WPML, and when I tried to translate a language, Korea, I found the URL translated too. For example, when translating the page 'About Us' into Korea, its URL 'hidden link' was translated into: 'hidden link'. I hope the URL is not translated and can be: 'hidden link'.
Symptoms:
The URL slug is being translated when I translate a page using WPML.
Questions:
How to prevent URL slug from being translated?
The URL slug typically gets translated when the Page URL setting in WPML is configured to "Translate" (Screenshot: hidden link). However, if you're using a language with non-Latin characters and the page URL setting is set to "Auto-Generate", the URL slug will be copied directly from the title of the translated post or page.
If you prefer not to translate the URL slug or want to keep it the same as the default language, you have two options:
1) Set the Page URL to "Translate" and manage the slug in the Translation Editor:
- Go to "WPML > Settings" and under the Translated Documents Option, set the Page URL to "Translate."
- After enabling this option, when translating a page or post, the slug will be available in the editor for translation. You can manually input the slug (e.g., keep it in English if you don't want the slug translated) and save the translation. This way, the slug in the translated language won't be changed.
2) Copy the slug from the default language:
- Set the Page URL option to "Copy from original language." Once configured, the slug from the default language will be copied to the translated version after translation.
- Before selecting this option, you'll need to enable the Encode URL option for the language to which the slug will be copied. Here's how:
- Go to "WPML > Languages" and click Edit Languages.
- In the Encode URL column, set the dropdown to "Yes" for the language using non-Latin characters (e.g., Korean).
- Save your changes.
Once this is done, set the Page URL option to "Copy," and when you translate a new post/page into Korean, the slug will remain the same as in the default language.
Please note that changing the Page URL setting will NOT impact posts or pages that have already been translated. For those existing translations, you'll need to manually edit the slug.
You can choose either of the options above based on your specific needs. I hope it will help.
Feel free to let me know if you need further assistance or clarification. I will be happy to help.
Many thanks for your quick reply and great support.
I tried the 2 methods, for the first method, sorry I can not find any url column on editor, so I tried the second method, I found it is successful for new translations, thank you.
But can you help me how to "For those existing translations, you'll need to manually edit the slug."
And I found when I translate a post, it will spend about 2000 credits, is it normally? Is there any mistake with me?
To manually adjust the slug for an existing translation, follow these steps:
1. In your WordPress Dashboard, switch to the secondary language using the language switcher located in the top bar (Screenshot: hidden link).
2. Go to Pages/Posts (or the relevant post type) where the translated post is available.
3. Find the translated post, and under its name, click on "Quick Edit" (Screenshot: hidden link).
4. In the Quick Edit panel, you'll see a field for the slug. Update the slug as needed, then save your changes.
The steps above should help in changing the slug for the existing translated post.
In response to your question about credits: If you have automatic translation credits, the system will automatically initiate the translation process when you open the translation editor. It will attempt to translate the content, and credits will be deducted based on the word count.
If you prefer not to have the content translated automatically, you can easily reverse the translation within the translation editor. Once the editor loads and the content is translated automatically, you’ll see a button at the top of the editor to undo the translation. Please refer to this screenshot: hidden link. Click that button to undo the automatic translation and recover your credits.
Please note that to ensure clarity and organization in each thread, we discuss one issue at a time. If you have additional questions or need further assistance regarding translation credits or automatic translation, please create a new ticket for that topic. We’ll be more than happy to help you with that as well.
I have a similar question to the one I asked before. The question is as follows. I have provided a new ticket, but no one has answered me.
Actually, I asked about pages before, and this time it is about the category of Post.
I tried to use the method you mentioned before, but changed it to Category:
WordPress---Category---Click on the specific category---Click Quick Edit----Replace the original Korean Slug with English, but after this replacement, the format of the corresponding Korean version of the Category has changed, and the sidebar on the left is missing.
Could you please help me solve this problem?
------------------------------
Background of the issue:
I am trying to restore the URL of a category for posts on my website to its original form. The URL has been translated into Korean, and I want to revert it back. We are not using WooCommerce.
Symptoms:
The URL of the category for posts on our website has been translated into Korean.
Questions:
How can I restore the translated category URL back to its original form?
I understand your question, but I noticed that you've created a new ticket for the same inquiry. One of our Supporters is currently handling that ticket. To ensure smooth and efficient communication, we kindly recommend avoiding duplicate tickets and discuss same topic in different tickets.
I’m confident you’ll receive a response to your query in that ticket.
If you need further assistance or have questions regarding the Page slug translation, feel free to let me know. I'll be happy to help.
Best regards,
Prosenjit
The topic ‘[Closed] How to prevent url slug from being translated?’ is closed to new replies.
