Problem: You are trying to link already translated pages to multiple languages on your site using the 'connect with translations' link, but you can only connect one other language instead of the two additional languages. Solution: Here are the steps to connect each translated page to your default language page: A) Connect "French page" as French (FR) translation of "Dutch page": - Edit your "French page". - Expand the Language section and set the language of your page to French. - Switch to WordPress Editor, and in the popup that appears, leave the selection at This Post. Click Apply. - Click on Connect with translations. A popup will appear. Search for the "Dutch page" and click Ok. - Another dialog will appear. Uncheck the box if you do not want to set the current page as the default language. B) Connect "English page" as English (EN) translation of "Dutch page": - Repeat the steps as above, setting the language to English. C) Connect "German page" as German (DE) translation of "Dutch page": - Repeat the steps as above, setting the language to German. After following these steps, your pages (French, English, German) will be linked as translations of the Dutch page.
If this solution does not resolve your issue or seems outdated, we 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: You are trying to translate the placeholder text in Contact Form 7 using WPML, but the placeholder does not appear on the translation page as expected. Solution: If you're experiencing this issue, we recommend checking the syntax used for your placeholders. Contact Form 7 requires double quotes for placeholder text. For example, if your form code looks like this:
[text* yourname placeholder 'YOUR NAME*']
You should update it to:
[text* yourname placeholder "YOUR NAME*"]
After updating, retranslate the form. This should resolve the issue and the translated placeholder should appear correctly on the frontend.
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing a technical problem with your Language Switcher plugin causing an E_PARSE error in langswitch.php, making your WordPress site unavailable. Solution: First, ensure that your WordPress debugging is enabled to capture detailed error information. Modify your
wp-config.php
file by changing
define('WP_DEBUG', false);
to
define('WP_DEBUG', true);
. Then, add the following lines just before the 'stop editing here' comment in your
file in your site's root directory, which will log all errors. Please review this log to identify and resolve issues.
If this solution does not resolve your issue or seems outdated, we 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 problems persist, please open a new support ticket with us.
Problem: The client was experiencing persistent loading and sporadic 404 errors on translated pages of their website after using WPML. The issues included pages not displaying after translation and random 404 errors when switching languages. Solution: We recommended the following steps to troubleshoot and resolve the issues: 1. Ensure all pages are correctly translated by making a minor edit in the original language, saving it, and then updating the translation. 2. Check and flush cache settings, as stale cache data might lead to pages not loading correctly. 3. Deactivate and reactivate plugins to identify any that might be causing conflicts, particularly focusing on the 'Razorpay for WooCommerce' and 'Categories Images' plugins, which were found to be problematic. 4. Switch the language URL format settings in WPML to see if this affects the 404 errors. 5. Increase the WordPress memory limit to ensure sufficient resources are available for operations. 6. If issues persist, especially with specific plugins like 'WooCommerce PayPal Payments', deactivate them to check if the problem resolves.
If these steps do not resolve the issues, or if the solution seems 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. For further assistance, please open a new support ticket at WPML support forum.
Problem: After updating WPML and all related plugins, the client found that there was no space to paste the code in the 'WPML > Settings > Custom XML configuration' section. Solution: We recommended clearing the browser cache as it might be causing the issue. Specifically, we suggested visiting the WPML settings page and then clearing the browser cache to refresh the page display. If you're experiencing this issue, we recommend you try the same steps: 1. Navigate to your WPML settings page. 2. Clear your browser cache. 3. Reload the page to see if the custom XML configuration space appears.
Please note that this solution might be irrelevant if it's 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 the problem persists, please open a new support ticket.
Problem: You are trying to display the translated single template of a Jet Engine custom post type using the JupiterX theme, but it keeps showing in the original language.
Solution: 1. Backup your site. 2. To translate template strings like BEDS, BATHS, etc., add the following code to your theme's functions.php file:
3. Save the changes and refresh a product page to see the translation. 4. To make the 'features' post meta translatable, add this code to your theme's functions.php or as a Must Use Plugin:
/**
* Translate associative KEYS for JetEngine 'features' post meta via WPML.
* Place in wp-content/mu-plugins/jetengine-features-wpml.php (recommended) or your theme's functions.php.
*/
add_filter( 'jet-engine/listing/data/get-post-meta', 'myproject_translate_features_keys_wpml', 10, 3 );
/**
* @param mixed $value The meta value resolved by JetEngine (array for 'features').
* @param string $key Meta key (we only act on 'features').
* @param int $object_id Post ID.
*
* @return mixed
*/
function myproject_translate_features_keys_wpml( $value, $key, $object_id ) {
// Only handle the 'features' field and only if it's an associative array like ['Pet-Friendly' => 'true', ...].
if ( $key !== 'features' || ! is_array( $value ) ) {
return $value;
}
// Determine current language (WPML). If WPML is missing, calls below no-op and return originals.
$lang = apply_filters( 'wpml_current_language', null );
if ( empty( $lang ) && defined( 'ICL_LANGUAGE_CODE' ) ) {
$lang = ICL_LANGUAGE_CODE;
}
$context = 'Jet Engine Admin Labels';
// Small request-level cache to avoid re-translating the same labels repeatedly.
static $cache = [];
$translated = [];
foreach ( $value as $label => $flag ) {
$label_str = (string) $label;
$name = md5( $label_str ); // stable key as you requested
$ck = $context . '|' . $name . '|' . (string) $lang;
if ( isset( $cache[ $ck ] ) ) {
$new_label = $cache[ $ck ];
} else {
// Register (idempotent) so translators can provide translations in WPML String Translation.
do_action( 'wpml_register_single_string', $context, $name, $label_str );
// Translate. If WPML inactive or no translation yet, this returns the original.
$new_label = apply_filters( 'wpml_translate_single_string', $label_str, $context, $name, $lang );
if ( ! is_string( $new_label ) || $new_label === '' ) {
$new_label = $label_str;
}
$cache[ $ck ] = $new_label;
}
// Keep the same value ('true'/'false') as stored; do NOT coerce unless you want to.
$translated[ $new_label ] = $flag;
}
return $translated;
}
5. Save the changes. 6. Go to WPML -> Strings Translation and translate the strings under the 'Jet Engine Admin Labels' domain.
If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we recommend opening a new support ticket at WPML support forum.
Problem: You are experiencing 404 errors on the English version of your product category pages even after updating the permalink and saving the slug via the 'Taxonomy Translation' option. Solution: We recommend resaving the permalinks to address this issue. You can do this by navigating to Settings → Permalinks in your WordPress dashboard and simply clicking 'Save Changes'. This action often resolves issues with 404 errors following permalink or translation adjustments.
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 problems persist, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: You are managing product gallery translations in your WooCommerce store using WPML. In the original language (FR), products have a complete gallery. However, in the back-end product editor of the translated product, the product gallery field is empty and not dynamic, despite having enabled 'Duplicate featured image from original' and 'Duplicate image galleries from original'. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML → Settings → Custom Fields Translation. 2. Activate the option "Show 'Multilingual Content Setup' meta box on post edit screen." and save your changes. 3. Edit the product in the original language, scroll to the bottom, and click on "Show system fields". 4. Set
_product_image_gallery
to Copy and save your changes. 5. Make a minor change to the original product, update it, and then complete the translation.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with installing new plugins and uploading media files in WordPress with WPML active, where the process would hang indefinitely. Server logs indicated a memory exhaustion error related to WPML. Solution: We first suggested checking if the REST API was enabled, as its disablement could be causing the issue. For more information on REST API dependencies with WPML, visit https://wpml.org/documentation/support/rest-api-dependencies/. After enabling the REST API and the issue persisted, updating WPML and its add-ons to the latest version (4.8) was recommended, which includes new bug fixes and improvements. The client can download the latest versions from "My Account -> Downloads" on the WPML site and should click the "Check for updates" button in Plugins → Add New → Commercial tab if updates are not visible. It is also advised to back up the database before updating.
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 at WPML support forum.
Problem: The client is using WPML on their website and wants to make the background color of the language switcher widget in the header completely transparent. Additionally, they want only the current language to appear transparent while the dropdown menu displays in a chosen color. Solution: We recommended adding specific CSS to the custom CSS section of the theme to achieve this. To make the background color of the language switcher widget transparent, use the following CSS:
You can change '#fff' to any color as per your preference. For more details on customizing the language switcher, visit how to fix styling and CSS issues for the language switchers. If this solution does not fully address 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 further assistance is needed, please open a new support ticket.
Problem: If you're unable to find the dropbar information in the advanced translation dashboard while using WPML. Solution: We recommend adding the following custom XML configuration to WPML > Settings > Custom XML Configuration. This will make the dropbar widget translatable:
Please note that this solution might be irrelevant if it's outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: After adding translation content, it is not displayed in the corresponding language, only in English. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Go to edit the product. 2. Click on 'Show system fields'. 3. Set the necessary fields to 'copy'. 4. Update the product.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check if there's a permanent fix available. Ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket through our support forum.
Problem: The client is unable to assign credits to the URL evess.ch after purchasing new credits. Solution: If you're experiencing issues with assigning credits to a different site URL, we recommend you try the following steps: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key by clicking the little trash icon (if the key exists for that site). 3. Log in to your site and go to the Dashboard >> Plugins >> Add new >> Commercial tab and click the Unregister WPML from this site link if it exists. 4. Then click the Register WPML link. 5. Click the Get a key for this site link. 6. It will generate the Key for your site and you can also assign the credits using that popup. Confirm the assigned credits from WPML >> Translation Management > Translation Tools. 7. Copy the key, and paste it back into the input box, and press the Register button.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing a fatal PHP error with the Sitepress Multilingual CMS plugin on WPEngine, specifically an error related to 'Call to private method WPML_Language_Pair_Records::convert_to_storage_format()' in the file translation-management.class.php on line 192. Solution: We recommend the following steps to resolve this issue: 1. Ensure all WPML components are updated to the same version. If auto-update is not possible, manually update by following these steps: - Deactivate all WPML add-ons. - Deactivate WPML Multilingual CMS. - Reactivate the core plugin first. - Go to Plugins -> Add New -> Commercial tab and activate add-ons one at a time. 2. On WPEngine, clear the object/page cache from the WPE dashboard. 3. In WPML → Support → Troubleshooting, run the following: - Clear the cache in WPML - Remove ghost entries from translation tables - Fix element_type collation - Set language information (only if you’ve seen language-less rows) - Synchronize local job ids with ATE jobs (if you use ATE) If these steps do not resolve the error, it may be due to outdated information or a different issue. 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 at WPML support forum for further assistance.
Problem: You are trying to publish translations on pages using the advanced editor, but the translations are not publishing. Solution: We have confirmed that this issue does not occur in our local tests, even when the String Translation plugin is reactivated. We attempted to review this on your installation via the File Manager, but it appears that debugging is not writing to the debug.log. We recommend that you verify on your side if there have been any recent changes, such as a modified log path.
If this solution does not resolve your issue or seems irrelevant due to being 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
