Problem: When using the WPML language switcher to switch to a secondary language, no shipping methods are displayed for that language. However, when selecting 'All languages', the shipping methods for the secondary language become visible. Solution: First, ensure you have a full backup of your site. Then, in your WPML dashboard under WPML → Support → Troubleshooting, run the following steps: 1. Remove ghost entries from the translation tables 2. Fix element_type collation 3. Fix WPML tables collation 4. Set language information 5. Fix terms count 6. Fix post type assignment for translations If these steps do not resolve the issue, it may be necessary to reset the shipping methods. This involves exporting the shipping methods using the Advanced Shipping plugin's export function, deleting all existing shipping methods, and then re-importing them. This process was tested and resolved the issue on a staging site before applying it to the live site.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML support forum.
Problem: The client is unable to translate strings from a PHP file on their website because the strings are not wrapped in the necessary WordPress functions (__() or _e()). Solution: We recommend wrapping the hard-coded strings in the PHP file with GetText functions to make them translatable. You can find detailed instructions on how to find strings that don't appear on the String Translation page and how to wrap texts in GetText calls here:
The _e() function retrieves and displays a translated string immediately, useful for simple outputs:
_e('Hello, world!', 'text-domain');
If these functions are missing, it indicates that the theme may not have been developed with translation in mind. For automated assistance in adding these functions, you might consider using tools like PHP Code Beautifier and Fixer (PHPCBF) alongside PHP CodeSniffer (PHPCS), though manual adjustments might still be necessary for complex cases.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if you need further assistance: WPML Support Forum.
Problem: The client reported that the language switcher on their website only displayed English and did not show Japanese as an option, despite setting up automatic translations in WPML. The client also noted that many pages were marked as 'Needs translation' and manual translation options appeared instead of automatic translations. Solution: We advised the client to check if the content was already translated and published, as the language switcher only displays languages for which translations are available and published. We identified that the Classic Translation Editor (CTE), which does not support automatic translations, was active. We recommended switching to the Advanced Translation Editor (ATE) for automatic translation capabilities. The client was guided to change the settings in WPML to 'Translate what you choose' and to send a page for automatic translation as a test. We provided a link to the documentation on how to review automatic translations: https://wpml.org/documentation/automatic-translation/how-to-review-automatic-translations-on-your-site/
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 https://wpml.org/forums/forum/english-support/.
