Problem: The client is migrating a user database from Ultimate Memberships Pro to WordPress User Management and needs to ensure that custom field value strings are correctly assigned to the new domain in WPML for proper translation in both English and French. Solution: 1. Correct a typo in the plugin code:
Then, go to "Users > Custom fields" and edit at least one option from the multiselect field. Afterward, translate all options in "WPML > String Translation". 2. Modify the code to handle comma-separated string outputs for multiselect fields:
Edit \wp-content\plugins\wp-user-manager\includes\fields\types\class-wpum-field-multiselect.php<br />Replace the entire get_formatted_output() function with the provided code snippet that includes WPML translation filters.
We have contacted the plugin authors to update their code accordingly. If the solution provided does not resolve your issue or seems outdated, please check related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at WPML support forum.
Problem: If you're trying to switch languages on a profile page using the WPML language switcher, but instead of being redirected to the corresponding profile page in the other language, you are redirected to a generic profile page or a warning page. Solution: We recommend backing up your site before making any changes. Then, edit your theme's functions.php file and add the following code at the end:
// WPML Workaround for compsupp-8195<br />// Preserve WPUM profile sub-path when switching languages with WPML.<br />add_filter( 'icl_ls_languages', function( $languages ) {<br /> // Only run if WPUM<br /> if ( ! function_exists( 'wpum_get_core_page_id' ) ) {<br /> return $languages;<br /> }<br /><br /> // Get profile info from query vars<br /> $queried_profile = get_query_var( 'profile', false );<br /> if ( ! $queried_profile ) {<br /> return $languages;<br /> }<br /><br /> // Build the trailing path from query vars<br /> $trailing = '/' . rawurlencode( $queried_profile );<br /><br /> // Add tab and pagination if present<br /> $tab = get_query_var( 'tab' );<br /> if ( $tab ) {<br /> $trailing .= '/' . rawurlencode( $tab );<br /> }<br /> $paged = get_query_var( 'paged' );<br /> if ( $paged ) {<br /> $trailing .= '/page/' . rawurlencode( $paged );<br /> }<br /><br /> // Append to each language URL<br /> foreach ( $languages as $key => $lang ) {<br /> if ( empty( $lang['url'] ) ) {<br /> continue;<br /> }<br /> $languages[$key]['url'] = rtrim( $lang['url'], '/' ) + $trailing;<br /> }<br /><br /> return $languages;<br />} );
This solution might be 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.
Problem: The client was experiencing an issue where the Gravity Form confirmation message was appearing twice in French, but only once in English on their 'Auditions' page.
Solution: We discovered that the 'Auditions' page had the same form added twice. We removed the second occurrence of the form, saved the changes, and updated the translation. This resolved the issue, and now the confirmation message appears only once in both languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening 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, please visit our support forum at WPML Support Forum.
Problem: The client is building a bilingual website using WPML, The Events Calendar Pro, and Event Tickets. They encountered an issue where the RSVP form does not appear on the event page, and the RSVP block is not saved when WPML is activated. Disabling WPML resolves the issue. Solution: We created a sandbox environment for the client to replicate the issue. It was suggested that the client should try creating a basic RSVP block in the sandbox to see if the problem persists. This step is crucial to determine if the issue is specific to the client's current setup or a general problem with the plugins and theme used. Additionally, we noted that there are known issues with The Events Calendar, but this particular problem with RSVP forms is not currently recognized as one.
If this solution does not resolve your issue or seems 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. If the problem persists, please open a new support ticket.
Problem: The client is using WPML and WP All Import to manage a bilingual contact directory. After importing translated contacts, they are not linked to their original versions in the other language. The WPML Export and Import admin page only shows instructions without providing an interface to apply languages and connect translations.
Solution: We recommend using only the WPML Import/Export addon for both exporting and importing content to ensure translations are automatically connected. Here are the steps: 1. Export your content using WPML Import/Export. 2. Import your content using the same addon. 3. Ensure that during the import process, you assign the correct language to each content piece and use the unique identifier
{wpmltranslationid[1]}
to link translations. For detailed guidance, refer to our documentation on WPML Export and Import.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and consider opening a new support ticket for further assistance at WPML support forum.
Problem: The client is trying to translate a block pattern with two buttons using Kadence Blocks in WPML. While the text strings are translatable, the URLs for the buttons in the translated version do not appear editable, leading to incorrect URL encoding and a 500 error on the target page. Solution: We recommend the following steps to resolve the issue: 1) Ensure you have a full site backup before making changes. 2) Navigate to WPML>>Settings>>Custom XML Configuration and update the WPML language configuration as follows:
3) Go to *****/wp-admin/edit.php?post_type=wp_block&lang=en 4) Edit the *Registration Block* post, make a minor change to refresh the translation settings, and update it. 5) Open the French translation for editing and adjust the URLs as needed.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
