Problem: The client has multiple branches with the same page titles (e.g., 'Dining') under different URLs (e.g., /london/dining, /berlin/dining) within their website. In WPML's Translation Management, these pages appear with the same title without showing their full URL or hierarchy, making it difficult to identify and translate the correct page for a specific branch. Solution: 1. If the pages are not set as child pages but follow a hierarchical structure like destination pages (London, Spain, etc.), you can assign a translation priority when editing the page. This allows you to filter pages by priority in WPML's Translation Management. 2. Another method is to hover over the 'Edit' button for the page in the Translation Management dashboard. This action will display the URL in the browser's status bar or tooltip, showing the post ID. You can use this ID to identify the correct 'Dining' page to translate.
If these solutions do not apply to your case, or if they seem outdated, we recommend opening a new support ticket. We also highly advise 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: You are working on a site under development and need to understand the implications of changing the WPML license key if the client changes providers in the future. You are concerned about whether they will need to unregister their WPML and get a new license key, and if they will lose any translations in the process. Solution: If your client has a WPML.org account, they can manage their sitekey directly from their account. Here are the steps we recommend: 1. Create a new sitekey on their WPML.org account. 2. Unregister the site using the old sitekey. 3. Re-register the site with the new sitekey. Changing the sitekey will not affect the translations on the site.
This solution might be irrelevant if it’s outdated or not applicable to your 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
