Problem: The client wants to change the URL slug from 'nieuws' to 'news' in the English version of their site. Solution: If you're experiencing this issue, we recommend you first check if the Slug Translation option is enabled in WPML. You can do this by navigating to WPML > Settings > Slug Translation. For more details, visit Translating URL slugs in WPML.
Next, go to WPML > Settings > Taxonomy Translation to translate the slug for your post categories. If 'nieuws' is used as a category, ensure to translate it at the same location. For a step-by-step guide on translating taxonomy terms, visit Translating Taxonomy Terms.
Please also check your WordPress permalink settings. If you are using a custom structure like '/nieuws/%postname%', note that this format is not translatable with WPML. We suggest switching to the 'Post name' structure instead.
If these steps do not resolve your issue, or if the solution seems outdated or not applicable to your case, we highly recommend opening a new support ticket. Additionally, check related known issues at WPML Known Issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please contact us at WPML Support Forum.
Problem: The client was experiencing a 'Forbidden' error when switching languages on their website. They were concerned that updating plugins might cause the issue to recur.
Solution: We first asked the client to check if the issue still occurred, suggesting it might have been a temporary caching problem. If the problem persisted, we recommended a step-by-step troubleshooting process: 1. Ensure a full backup of the website and database. 2. Deactivate all plugins except for WPML and its addons, then check if the issue still occurs. 3. Reactivate each plugin one by one, checking for the error after each activation to identify any conflicting plugin. 4. If the issue continued, we advised repeating the steps with a default WordPress theme.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
