Problem: You are trying to translate the slug of your custom post type (CPT) 'Offer', but despite following the documentation and saving the permalinks again, the slug is not translated, resulting in 404 errors when accessing the links. Solution: If your CPT 'Offer' is created using custom code, you should first edit your code to change the slug. After modifying the slug, navigate to WPML-> Settings in your dashboard and translate the new slug, ensuring it differs from the previous translations. This adjustment should resolve the issue with the untranslated slug and the subsequent 404 errors.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing a blank page when attempting to update a translation on their website. Solution: We identified that the issue was related to a browser extension. If you're experiencing this issue, we recommend disabling the DuckDuckGo Privacy Essentials extension. You can find this extension here: https://addons.mozilla.org/en-US/firefox/addon/duckduckgo-for-firefox/.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. We also 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. For further assistance, you can contact us directly at WPML support forum.
Problem: The client was experiencing an issue where the permalink slug for a custom post type was not translating correctly, leading to a 404 error on the translated version of the page.
Solution: We discovered that the problem was caused by the Redis Object Cache plugin. Once we deactivated this plugin, the permalinks started working correctly. If you're experiencing a similar issue with permalinks not translating on your custom post types, we recommend trying to deactivate the Redis Object Cache plugin to see if that resolves the issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If deactivating the Redis Object Cache plugin does not solve your problem, or if you encounter any other issues, 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 the issue persists, please do not hesitate to open a new support ticket with us.
