Problem: You have created a custom post type (CPT) with the slug 'event' using the ACF Pro plugin and defined a custom archive slug 'events'. You have translated the base default slug 'event' to 'événement' in French via WPML > Settings > Post Types Translation, but you are unable to find where to translate the archive slug. Solution: Currently, WPML does not support the translation of custom slugs set in the
has_archive
option for custom post types. You can read more about this limitation here. We recommend enabling the archive option and leaving the slug field empty for custom post types created with ACF. This approach uses the default slug, and when you switch languages, the translated slug set in "WPML > Settings > Post Type Translation" will display.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with a site built using Kadence and Beaver Builder, where the translation lost text formatting, resulting in a block of text instead of paragraphs. Additionally, the mobile CTA button from Kadence Conversions is displayed on all screen sizes, not just on mobile, and editing the French Conversion version causes a 500 Internal Server error. Solution: For the issue of lost text formatting, we recommend disabling the option "I prefer bigger segments" in the Advanced Translation Editor as it might be causing the line breaks to be ignored. You can find more details and workarounds on this issue at https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. Regarding the mobile CTA button displaying on all screen sizes, please ensure that Kadence Conversions is compatible with WPML and check any specific settings within Kadence Conversions that might be affecting visibility across different devices.
If these solutions do not resolve your issues or if the information provided becomes outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client needed to know if the settings for MailChimp, such as audience name and tags, associated with the translated Gravity Forms remain intact or if it's possible to 'translate' these settings as well.
Solution: We informed the client that when translating a form using the WPML editor, the form in all languages is treated as one form and adds one tag. Therefore, having different tags/settings per language is not possible. We recommended that the client should create two separate forms, one for each language, and add the specific tags in each one as a workaround.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, we encourage you to open a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us in the WPML support forum.
