Problem: The client wanted to place the WPML menu language switcher in the second last position of their menu, but the WPML settings only allow placement at the first or last position. Solution: We informed the client that WPML does not offer an option to insert the language switcher in the middle of the menu. However, we suggested using a shortcode for more flexibility or adding the switcher at the end of the menu and then re-adding the last item manually or with another menu (Menu 1 - Switcher - Menu 2). We also provided a link to a resource that explains how to enable the use of shortcodes in header menu items: https://support.buddyboss.com/support/solutions/articles/72000599576-enable-the-use-of-shortcodes-in-header-menu-items Additionally, we mentioned that if the client is comfortable with coding, they could use the wp_nav_menu_items hook to insert their last link after the switcher, as referenced here: https://developer.wordpress.org/reference/hooks/wp_nav_menu_items/
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 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 you need further assistance, please contact us in the WPML support forum.
Problem: The client was unable to translate certain fields from ACF blocks in the Advanced Translation Editor, such as link text and URLs. Additionally, most ACF blocks were not appearing in the Custom Fields Translation settings.
Solution: 1) We recommended increasing the WP Memory limit to 256M by adding the following code to the wp-config.php file:
define('WP_MEMORY_LIMIT', '256M');
2) We advised ensuring that "ACF Field Groups" are set to "Not translate" in WPML > Settings > Post Type Translation. 3) We suggested verifying that the ACF Field Group uses the translation preference setting "Same fields across languages". Guide 4) We instructed the client to edit the fields on the original content and then open the WPML Translation Editor again. 5) We identified that field groups with the same field names were causing issues and recommended making each field name unique. Source 6) We changed the translation preference for the Link field to "translate" and explained that external links usually need to be searched using the text search input in ATE. Default setting for Links 7) We provided instructions on creating a custom XML config and placing it in the root folder of the theme or plugin responsible for the block, or adding it at WPML > Settings > Custom XML Config. Guide 8) We provided an example of a custom XML config for translating a button's text and link:
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 you still need assistance, please open a new support ticket at our support forum.
