Problem: The client is seeking to renew their WPML Multilingual Agency package and is uncertain about where to renew in the dashboard. They are also interested in any available discounts or promotions for their account. Solution: If you're looking to renew your WPML package and are unsure about the process or available discounts, we recommend the following steps: 1. Log into your WPML account at wpml.org. 2. If you cannot find the renewal options or have questions about discounts, please contact our accounts team directly. You can reach them through this form: Contact Us.
Please note that the solution provided 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 these steps do not resolve your issue, we encourage you to open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with the WP Bakery Media Grid Widget not working on translated pages in second languages, and this occurs on every page that has a media grid, the issue might be related to how the media grid is translated. Solution: We recommend using the WPML Translation Editor to translate your pages as it handles the translation of media grids more effectively. However, if you prefer using the WordPress Editor, follow these steps: 1. Navigate to WPML > Settings > Custom Field Translation and click on "Show system fields". 2. Search for the field
_vc_post_settings
and change its setting to "Not translate". 3. Save your changes and re-translate the pages using the WordPress Editor. This adjustment is necessary because the field
_vc_post_settings
, which includes image IDs, needs specific handling to ensure images display correctly across different languages when not using the WPML Translation Editor.
Please note that this solution might become outdated or may not apply to your specific case. If the issue persists, 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, do not hesitate to open a new support ticket for personalized assistance at WPML support forum.
Problem: You are experiencing issues with parts of your website changing unexpectedly and the logo altering after installing WPML for translating a page from Albanian to English and Italian. Solution: If you're noticing changes in your website's widgets or logo after installing WPML, we recommend checking the "Display as Language" option in your widget settings. You have two choices: create separate widgets for each language and assign them accordingly, or use WPML’s String Translation to manage the translations. The latter option will prevent the need to maintain multiple widgets. If these steps do not resolve your issue, 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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing layout issues on their multilingual WordPress site, where the English version of pages did not match the design of the Albanian version. Additionally, the client was unsure how to translate the footer, header, and use the Slider Revolution plugin in multiple languages. Solution: We identified that the layout discrepancy was due to some custom fields being set as non-translatable. We adjusted the settings to make these fields translatable by following the steps in our guide on Translating Custom Fields. For the issues related to translating widgets and using Slider Revolution, we provided documentation links and advised the client to open separate support tickets for each issue to ensure detailed assistance. The relevant guides can be found here:
If the provided solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should further assistance be needed, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client was unable to manually translate pages using WPML, encountering a permission error that prevented access to the 'Pages' section. Solution: We recommended the following troubleshooting steps: 1. Ensure the website is backed up. 2. Test the issue on a minimal installation or a staging site to avoid affecting the live site. This involves: - Switching to a default theme like 'TwentyTwenty'. - Deactivating all plugins except WPML and its add-ons. - Checking if the issue persists. If not, reactivate plugins one by one to identify the problematic plugin. 3. Enable WordPress debug mode by adding the following code to the 'wp-config.php' file:
Place this code above the line: /* That's all, stop editing! Happy blogging. */ For more information on debugging WPML, visit https://wpml.org/documentation/support/debugging-wpml/ If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client was facing an issue where only the first footer column was displayed on their website, despite the theme supporting six footer columns. The client had added all HTML and CSS to the first column, which was not following WordPress best practices. Solution: 1. We advised the client to save CSS in the Customizer > Additional CSS, in the style.css file, or in a Child Theme instead of embedding it directly in the widget area. 2. We recommended using all available footer widget columns and avoiding manipulating the layout with additional CSS. 3. We suggested placing the FontAwesome link inside the
section of the HTML document using a plugin, which can be found here: https://wordpress.org/plugins/insert-headers-and-footers/ 4. Upon further investigation, disabling the "Droplet Framework" plugin resolved the issue, indicating a conflict between the theme and the plugin. 5. We recommended reinstalling the theme after taking a backup to ensure no theme code alterations were causing the issue. If these steps do not resolve your issue, 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. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
