Problem: The client was experiencing a warning message 'Illegal offset type in isset or empty' on their website. Solution: We recommended following the instructions provided in the errata page for a temporary fix. The errata related to this issue can be found here: https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/. We also informed the client that our development team is working on a permanent solution that will be released in an upcoming update.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related 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 do not hesitate to open a new support ticket in the WPML support forum.
Problem: If you're experiencing a TypeError with the message 'Illegal offset type in isset or empty' on your site, it might be due to a conflict between WPML and the latest version of the Site Kit by Google plugin. Solution: We recommend downgrading to the previous version of the Site Kit by Google plugin (1.105) after ensuring you have a full site backup. This issue is currently under investigation by our developers. For more details, please check the known issue here: https://wpml.org/errata/site-kit-by-google-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/.
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 you need further assistance, please open a new support ticket.
However those instructions only work if you DON'T register WPML on the development site before pushing the plugin to the live site.
The correct process would be to install WPML on the dev site, then push it to live. After that create WPML keys for both dev and live. Then activate the plugin on both sites, that would allow you to enter the appropriate keys.
If you install and register WPML on the dev site, make your translation then clone to live (just pushing code changes doesn't include the database). You do have to use the define( 'OTGS_INSTALLER_SITE_KEY_WPML', '' ); for the live site in wp-config.
Unfortunately, because of the way Pantheon is setup that means you can only make translations on the live site. If you want to create translations on the dev site then you'd need to modify wp-config again for the dev key.
One other item: Since Pantheon is using alias URLs I had to first go to create a key for the actual site URL (example.pantheon.io) and modify wp-config. Then modify wp-config again with the live URL key (example.com). Then in the error message in the WP dashboard go through the steps confirming that the new URL is example.com. Finally going to example.com and also confirming there that that URL was the correct one.
Again all these steps are only if you don't follow the correct install/register process for Pantheon's environment (which isn't really intuitive and they don't mention possible issues like these).
Hopefully this makes sense and might possibly help others.
Problem: The client's website has duplicate content issues because pages are accessible with and without the '/en/' language directory. Solution: If you're experiencing duplicate content issues on your multilingual site where pages are accessible with and without a language directory, we recommend the following steps: Issue is fixed in WPML 4.6.8. If you have similar issue you can try check the WPML language URL format settings to ensure that you have selected the option to use a different language in directories.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please don't hesitate to open a new support ticket in the WPML support forum.
Problem: If you're experiencing issues with translating text fields within a nested repeater on an ACF options page using ACFML, where the text fields are not translatable. Solution: We recommend setting the field group mode to "Expert" and setting the parent repeater field to "Copy Once". Initially, this will copy the entire structure, but after saving once in the second language, you will need to manually adjust the new rows and fields in both languages. Additionally, if you use the mode 'Same field across languages', the text field becomes translatable. For more details, please read our documentation on recommended custom fields translation preferences for ACF and WPML.
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 for further assistance.
Problem:
When using custom permalink structure with custom code for a CPT UI post type the translated posts are not loading.
Solution:
WPML supports only custom slug translation and not custom permalink structure.
When you use CPT UI plugin for a custom permalink structure you can use Permalink Manager plugin as suggested in the plugin document linked next.
Problem:
I'm working with avada and try to translate a postcard module. On the translated version the filtes are not visible. i translated the categories but it doesnt help. Solution:
The solution was to edit the translation in the WordPress mode. Then I had to choose the categories in English, so they were shown in the filters. Thanks for the help!
Problem:
Some parameters in URL weren't being missed when switching language (or visiting translation).
Solution:
If you are using "Language name added as a parameter" option and want to preserve other query string parameters across translations, make sure to turn on the following setting:
WPML -> Languages -> Language switcher options -> Preserve URL arguments
And add the parameters separated by a comma.
After adding just move out of that box, so it is saved automatically. Then reload the page in frontend and you can see the parameters added to the language switcher or the target URL.
Problem:
The client was unable to edit the default language products.
Solution:
Please follow the below steps:
1. Please take a backup of your site first for safety reasons.
2. Please empty the trash from all languages.
3. Please go to WPML >> Support >> Troubleshooting page and press the below buttons:
- Clear the cache in WPML
- [Products] Synchronize posts taxonomies
- Remove ghost entries from the translation tables
- Synchronize local job ids with ATE jobs
- Synchronize translators and translation managers with ATE
- Assign translation status to duplicated content
- Fix post type assignment for translations
- Set language information
Problem:
Repeater field was not showing in the frontend but only for one language , for other languages it was working fine.
Solution:
- Backup the site for a reference.
- Go to WPML -> Settings page and scroll to "Post Types Translation" section
- Set "Field Groups (acf-field-group)" to not translatable as explained in the next link.
Problem:
WooCommerce My account/registration page layout was broken for translation.
Solution:
Make sure all strings for WooCommerce specially for the strings used in login/signup are translated properly from WPML -> String Translation. Most probably some string like "text %s" is missing the text specifier "%s" for the translation, which was exactly the case in this thread.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
