Background of the issue:
We are in the process of changing the site from WP Bakery to Astra/Spectra. Now we need to override existing translations in order to also override the code. However, with this, our existing page slugs get overridden. We have some slugs which are translated and some not, so we cannot choose either copy from base URL or translate.
Symptoms:
Existing page slugs are getting overridden during the translation process.
Questions:
How can we prevent existing page slugs from being overridden during translation?
Is there a way to selectively translate or copy slugs from the base URL?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
According to the provided debug information the setting WPML → Settings → Translated documents options → Page URL is set to "Translate" and this is why the slugs are available inside the WPML Translation Editor.
I suggest you apply the standard setting "Auto-generate from title".
Subject: Follow-up on WPML Translation & Slug Settings
Dear [WPML Support Team],
Thank you for your response and for your help so far. However, I wanted to clarify our situation further, as the suggested solution does not align with what we need.
We have already translated our pages, but they were originally created in WPBakery. Now that we have upgraded our site to Astra with Spectra, we need to re-translate the pages so that the blocks transfer over correctly. In doing so, we do not want to modify the slugs.
Some slugs are directly copied from the English version, while others have been translated, and we want to keep them exactly as they are. We do not want WPML to override or modify any slugs during the re-translation process.
Could you please advise on the correct settings to ensure that:
1. We can re-translate the pages so that the new blocks are properly transferred.
2. The existing slugs remain unchanged.
3. If possible, we can update the translations without overwriting any existing translations while still ensuring the block-based content is properly migrated.
As you can see we use the latest Version of WPMl.
Looking forward to your guidance on the best approach.
Thanks for your reply. Please allow me to answer your questions accordingly.
1. We can re-translate the pages so that the new blocks are properly transferred. As you mentioned, you have already translated the pages, are having issues with this?
2. The existing slugs remain unchanged. We do have an option to prevent the URL slugs to be translated. To do this, navigate to WPML > Settings > Translated documents options > Page URL > Select "Translate (this will include the slug in the translation and not create it automatically from the title)". Then, when you're translating the page content using the Advanced Translation Editor, use the copy feature to copy the primary language URL slug to your secondary language.
3. If possible, we can update the translations without overwriting any existing translations while still ensuring the block-based content is properly migrated. If you've been using the Advanced Translation Editor, the same translated contents will show up automatically without needing to retranslate them.
