If you're using WPML with WooCommerce and WooCommerce Bookings and are experiencing issues with duplicate booking entries in your event calendar whenever a customer places an order, despite having disabled translation of Bookings (wc_booking) in WPML Settings -> Post Types Translation.
Solution:
We recommend following these steps: 1) Create a simple Booking Product for testing. 2) Duplicate it into a secondary language. 3) Make a booking and check if the issue still occurs.
A WooCommerce Booking product must have a translation to avoid duplicate booking entries when using WPML.
This solution might be 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 for further assistance.
Problem: The client was trying to install and configure the WPML plugin but encountered an error stating that the table
1
...wp_icl_strings
does not exist. Additionally, the 'Support' option was missing from the WPML side menu, preventing a reset. Solution: We recommended that if the client has just activated WPML and has no translations yet, they should reset WPML and reconfigure it. Here are the steps: 1. Navigate to WPML → Support and click the Troubleshooting link. 2. On the Troubleshooting page, in the Reset section, select the 'I am about to reset all translation and language data' checkbox. Then, click the 'Reset and deactivate WPML' button. For detailed guidance, visit WPML reset documentation.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate a specific string on their website, which is added using the Elementor page builder, but is unsure how to do so. Solution: 1. Open the default language page in Edit mode. 2. Make a small change, such as adding a space or a + sign in the page title. 3. Save the page. 4. Remove the small change made in step 2. 5. Update the page again. 6. Try to open the translated page in WPML Translation Editor to see if the title is now available for translation. If the title is still not available in WPML Translation Editor, the client may need to register the element by following this documentation: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/
If this solution does not resolve the issue or if it seems outdated or irrelevant, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are concerned about whether your site uses custom Twig templates for the language switcher, especially with the upcoming WPML 4.8 update which removes support for Twig templates. Solution: If you have configured your language switcher through WPML → Languages or your theme settings, you should not encounter any issues with the WPML 4.8 update. However, if you are unsure or need further clarification, we recommend checking the 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 solution does not apply to your case, or if it seems outdated, please do not hesitate to open a new support ticket. We highly recommend visiting the WPML support forum for further assistance.
Problem: The client's Turkish designs disappear when WPML is active on their website designed with Elementor and Royal Addon. The designs reappear when WPML is deactivated. Solution: We recommend removing the
1
wpr_single_conditions
key from the
1
wp_options
table in your WordPress database. Before making this change, ensure you create a backup of your database to prevent any potential data loss.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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: The client is using the GreenShift Builder with WPML to build and translate their website. While translating the homepage using WPML’s Advanced Translation Editor, the translated version displays the default language content instead of the translated content. Additionally, an error in the backend indicates that the block contains unexpected or invalid content, prompting a block recovery message. Solution: We resolved the issue by updating the GreenShift plugin and its add-ons to the latest version. It is crucial to follow the correct WPML translation process and avoid editing the translated content directly in the Gutenberg editor. After these updates and following the proper procedures, we tested the system thoroughly and confirmed that everything is now working as expected.
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 the problem persists, please open a new support ticket.
Problem: You are unable to re-add existing users as translators in WPML after an update, and you are concerned about losing translations when updating translated job pages. Solution: To resolve the issue of re-adding existing users as translators, you need to edit the
1
wp_capabilities
key in the
1
wp_usermeta
table. Remove the "translate" value for the affected users. This adjustment will allow you to add them back as translators. After making this change, please ensure to add the correct language pairs for each translator as needed. If you are unsure what to do, don't proceed with the above. Take a backup of the DB of your site before proceeding! If you're experiencing similar issues or if this solution does not apply due to different circumstances or 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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Solution:
The blank page means (or “500 error”) that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code.
First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.
To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:
1
define('WP_DEBUG', true);
To enable the error logging to a file on the server, you need to add yet one more similar line:
1
define( 'WP_DEBUG_LOG', true );
The errors will be saved to a debug.log file inside the /wp-content/directory.
Problem: You are experiencing issues with custom button URLs not consistently appearing in the Advanced Translation Editor (ATE). Sometimes these URLs are visible, and other times they are not, although they can still be accessed by searching.
Solution: We have identified that links within text are typically visible, whereas links in separate fields might not show up by default but can be searched for. This behavior was previously adjusted for some page builder elements to make separate links visible by default for usability purposes. If you are noticing discrepancies between your production and development sites, it might be due to the types of links used (internal vs external). To help us investigate further and provide a more tailored solution, we recommend replicating the issue in a test site. This will allow us to examine the problem in detail.
Please note that this solution might be 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 for further assistance.
Solution:
The blank page means (or “500 error”) that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code.
First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.
To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:
1
define('WP_DEBUG', true);
To enable the error logging to a file on the server, you need to add yet one more similar line:
1
define( 'WP_DEBUG_LOG', true );
The errors will be saved to a debug.log file inside the /wp-content/directory.
Problem: You are trying to get the widget title translated into every language on your website, but the widget title remains in Italian, the default language, instead of being translated. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML >> String Translation page. 2. Open the 'Not seeing strings that you are looking for?' section and click on the Admin texts translation link. 3. Search for the 'Prenota la Tua Barca Ora' string and enable its translation. 4. Return to the WPML >> String Translation page and add its translation.
If the issue still persists after following these steps, please provide temporary access (WP-Admin and FTP Login info) to your site (preferably a staging site), so that we can look into your setup and debug the issue. Ensure you back up your database and website before making changes or providing access.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Solution:
The blank page means (or “500 error”) that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code.
First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.
To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:
1
define('WP_DEBUG', true);
To enable the error logging to a file on the server, you need to add yet one more similar line:
1
define( 'WP_DEBUG_LOG', true );
The errors will be saved to a debug.log file inside the /wp-content/directory.
Problem: You are experiencing issues with your logo not displaying correctly in the translated version of your site. Specifically, the logo appears black instead of transparent in German, and the translation pen loads indefinitely when changes are made. Solution: We applied custom CSS to address the logo display issue. Please add the following CSS code to your site by navigating to WP > Appearance > Customize > Additional CSS:
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.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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 contact us through the WPML support forum.
Problem: The client noticed that the categories are scattered and not in chronological order in the English language. Solution: If you're experiencing scattered categories in a non-chronological order, we recommend you try synchronizing your categories. Here are the steps: 1. Go to WPML → Taxonomy Translation 2. Select the categories 3. And Sync
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.