Problem: The client manually installed a new WPML update because it wasn't showing in the WordPress updates section or in plugins, which resulted in a critical error on the website. Solution: We logged into the site and attempted to update the WPML plugins via the Plugins -> Add New -> Commercial page. However, the site was still pointing to localhost, which we identified from the WPML -> Support page notice indicating the site was detected at localhost. This could interfere with updating plugins from a publicly mapped address.
To resolve this, we deactivated all plugins, switched to the standard WP theme 2025, updated the WPML plugins (WPML, String Translation, and WCML), and then reactivated these along with WooCommerce. After these steps, the fatal error was no longer present.
We recommend the client to try reproducing the issue with the current setup and report the steps if the error reoccurs. Additionally, we advised using PHP 8.2 until newer versions are fully supported, as PHP 8.4 is still in beta support by WordPress. For more details on PHP compatibility, visit WordPress PHP Compatibility.
If this solution does not resolve your issue or seems outdated, please check 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 highly recommend opening a new support ticket at WPML support forum.
Problem: The client is unable to translate the cookies notice on their website after modifying the text, and the provided WPML documentation did not resolve their issue. Solution: We recommend updating the gettext code in your theme or plugin files to ensure proper translation string and text domain usage. Here are the steps: 1. Update your gettext code to include the correct text domain and ensure the URL is wrapped appropriately for translation. For example:
<div class="message"><br /> <?php echo sprintf(<br /> esc_html__( 'We use cookies to improve your user experience. %s', 'your-text-domain' ),<br /> '<u><b><a href="https://mp-performance.ae/privacy-policy">' . esc_html__( 'Learn more', 'your-text-domain' ) . '</a></b></u>' <br /> ); ?><br />
2. Scan the theme or plugins for strings using WPML's String Translation. 3. Translate the strings as needed in WPML.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket.
Problem: The client is facing an issue where a static block does not appear on the Arabic translation of the shop page in the Elessi theme, despite being visible in the English version. The root cause is identified as the missing breadcrumb in the Arabic page, which affects the display of the static block set to appear after the breadcrumb. Solution: First, ensure that the breadcrumb is visible on the page by setting the custom field
_nasa_show_breadcrumb
to "Copy". To do this, navigate to WPML > Settings > Custom Field Translation, click "Show system fields", find the field
_nasa_show_breadcrumb
, and set it to "Copy". After this, retranslate the Shop page. Additionally, when translating the static block, use the Advanced Translation Editor's search bar to find and translate all URLs by typing "http".
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are unable to find the bottom blocks of your theme in the WPML string translation interface, and you are finding the new version of WPML confusing.
Solution: First, ensure you have checked the Admin Strings section as some strings might appear there. Additionally, follow the steps in our guide on Finding Strings that Don't Appear on the String Translation Page to bring those strings into String Translation. If the blocks are part of a widget or an element from a theme or page builder, you might need to make them recognizable by WPML. For detailed instructions, please visit How to Register Page Builder Widgets for Translation.
If this solution does not apply to your case because it might be outdated, or if you are still experiencing issues, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to use their translation credits in WPML despite having a sufficient balance. They encountered an issue where WPML indicated that more credits were needed, although the account showed plenty of credits available. Solution: We identified that the issue was likely due to multiple automatic translation accounts being created after reinstalling or resetting WPML or WordPress. This caused the translation credits to become stuck in one of these accounts. We resolved the problem by transferring the stuck credits (a total of 60094 credits) to the client's current automatic translation account. The client can now view and use these credits by navigating to WPML > Translation Management > Tools page.
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 advise 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 was unable to translate certain strings that were previously translated. They also noticed an issue with a category name appearing in Arabic and a link pointing to an Arabic URL, suggesting a broader issue with WPML. Solution: We recommended enabling the 'Look for strings while pages are rendered' option to identify conflicting language files outside the wp-content/language/wpml directory. The client should back up and then remove each language file outside this directory to see if it resolves the issue. For the specific issue of the 'shop' page title in Arabic, the client needs to translate the page title at https://mp-performance.ae/wp-admin/edit.php?post_type=page&lang=ar. Additionally, we advised duplicating the wp-content/language folder for backup, then removing wp-content/language/plugins and wp-content/language/themes to check if translations appear correctly. We also addressed a separate issue regarding product breadcrumbs in a different ticket. Lastly, we instructed the client to remove the language file at \wp-content\languages\ar.l10n and apply a fix available at https://wpml.org/errata/l10n-php-performant-default-translated-strings-not-displaying-correctly/.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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: The client noticed that the category name on their product page was in Arabic, and the link was pointing to an Arabic version, suggesting a potential issue with WPML. Solution: We first noted that the client's website was experiencing a database connection issue. After resolving that, we recommended changing the Taxonomies Translation settings by navigating to Taxonomies Translation settings. Following this adjustment, we advised the client to clear their browser cache to ensure the changes take effect.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket.
