Problem:
There is a problem with the String Translation table in your site
Solution:
It was a false positive notice and I removed the "wpml_string_table_ok_for_mo_import" key from the *_options database table and the notice is gone.
Problem:
use ATE to translate a post that contains Kadence Blocks "Testimonial" block Solution:
Please go to WPML->Settings->Custom XML Configuration (tab at the top) and add the following
I checked the issue and was able to fix it by the following steps:
1- Go to WPML-> Settings-> Post Types Translation
2- Set the "Footers" post type translatable
3- Translate the "Default" footer template
4- Go to WPML-> String Translation
5- Scroll down and click on the "Translate texts in admin screens »" link
6- Search for the Footer template ID
7- Select the String
8- Click on the "Add to String Translation" button
9- Then click on the "« Return to String Translation" link
10- Translate the template ID to the translated template ID
Modern Events Calendar Weekly View works of in the translated language when logged in, but not working when logged out.
Solution:
- Go to "WordPress Dashboard > WPML > Languages > Language filtering for AJAX operations".
- Make sure that the "Store a language cookie to support language filtering for AJAX" option is checked.
- Click the "Save button".
Problem:
The client was getting an "Update failed: undefined" error on updating the WPML plugins and also seeing the "WPML plugin cannot connect to wpml.org" notice on the site's dashboard.
Solution:
Please delete the existing site key and create a new one by following the below steps:
1. Please login to your WPML account >> Go to the Sites page: https://wpml.org/account/sites/
2. Delete the existing site key.
3. Create a new subscription key for your site as a production.
4. Visit the Site Dashboard and go to Plugins >> Add New >> Commercial tab.
5. Click on the “Unregister WPML from this site” button.
6. Register with the new site key and refresh the page.
7. Click the “Check for updates” button and try to update the WPML plugins. Here is the screenshot for more details: https://wpml.org/wp-content/uploads/2020/04/wpml-force-plugin-update-1.png
8. After registering WPML with a new key please follow the below steps for removing the “the WPML plugin cannot connect to wpml.org” notification:
8.1. Please go to WP Dashboard Menu >> Updates.
8.2. Press the "Check again" link.
8.3. Now please go to the Plugins page and see if that notification still exists or not.
Problem:
The client wants to translate the Elementor footer automatically using ATE which was built using custom post type.
Solution:
I have set the Elementor Header & Footer Builder (elementor-hf) post type as “Translatable only show translated items” from WPML >> Settings > Post Types Translation section and now ATE translated the footer automatically and shows the translated footer in each language.
Problem:
The client wants to translate the dropdown menu items that are built using custom links.
Solution:
I have Sync menus from WPML >> WP Menus Sync page and updated the custom menu items links from WPML >> String Translation page and it solved the issue.
Problem:
The client was seeing a Fatal error after installing the WPML plugins.
Solution:
This issue usually happens when there is something wrong in the database during installation. If it’s a new site with no translated content, you can reset WPML and set it up again.
To do so:
- Please take a backup of your site and go to WPML >> Support >> Troubleshooting (the link is at the bottom of the support page). >> There, click on “Reset and deactivate WPML” >> then Delete the plugin.
- After deleting all WPML data and WPML-related plugins then please install WPML plugins again and I hope now you will not face any issues.
Some themes and plugins let you set the site footer, header, or template via theme options or the WordPress Customizer.
To display the correct footer according to the language of the site, you need to tell your theme which footer or theme option to display in each language.
You can do this by going to WPML > String Translation and searching for the footer's default language ID. You can then add the secondary language ID as the translation of the default language footer. Now, on the front-end, you should see the right footer according to the language of the site.
Using wpml_object_id we get the correct menu id's for each language, however the actual menu and thus, menu items returned, are the same base language (English in our case) for all translations.
This happens in the wp-graphql "graphql_register_types" action.
Solution:
We adjust terms, and the menu is a taxonomy. Disable the option " Adjust IDs for multilingual functionality" from WPML->Languages->Make themes work multilingual.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
