Problem: If you're experiencing issues with custom CSS in Elementor not displaying correctly after translating your site using WPML, where the CSS attribute content remains unchanged across translations. Solution: 1. We recommend setting up a minimal installation of WordPress, WPML, and all necessary WPML add-ons, and themes to replicate the issue. This helps in identifying and solving the problem more efficiently. 2. If the issue persists, you can manually edit the translated page and adjust the CSS directly. Access the second language page from Pages > All and click 'edit with Elementor', or go to the page in the frontend and click 'Edit with Elementor' in the top bar. 3. Alternatively, remove your custom CSS from Elementor and add it to your theme via Appearance > Customize > Additional CSS. 4. Follow the errata and workarounds provided by WPML for known issues with Elementor and custom CSS at https://wpml.org/errata/elementor-custom-page-css-not-copied-correctly-in-translations/.
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 our support forum.
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: The client is experiencing a 'Download failed. (Forbidden)' error when attempting to update or download WPML plugins, even after deregistering and registering the sitekey. Solution: 1. Revalidate your domain with your sitekey by navigating to https://wpml.org/account/sites/ and copying the sitekey created for your domain. Then, go to WP > Plugins > Add new > Commercial Tab > Deregister and register the sitekey again. 2. If the issue persists, manually install the plugin. Download WPML manually by visiting https://wpml.org/account/downloads/, scroll down, and click on 'Download WPML manually'. Then, in your WP dashboard, navigate to WP > Plugins > Add new and upload the downloaded zip file directly.
If these steps do not resolve your issue, or if the solution becomes 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 you still encounter problems, please open a new support ticket at WPML support forum.
