Problem: The client is experiencing an issue with WPML registration despite using the correct 10-character alphanumeric site key. The error message indicates an invalid site key defined as the constant OTGS_INSTALLER_SITE_KEY_WPML, likely in wp-config.php. Solution: 1. Verify the site key for case sensitivity and ensure it matches exactly what is provided in the WPML account. Use the following code snippet to check:
2. Refresh the repository information from the WordPress Dashboard > Updates page. 3. If the issue persists, follow these steps: - Ensure a complete backup of the site, files, and database. - Access the site's database via PHPMyAdmin. - Navigate to the wp_options table and delete the wp_installer_settings key. 4. Check for any warning messages in WPML>>Support>>Installer Support. For more details on checking the installer support log for errors, visit WPML support documentation. 5. Consider potential conflicts with caching mechanisms or specific architectures like Bedrock that might affect key validation.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also 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. For further assistance, please contact us through the WPML support forum.
Problem: The client reported an issue where translations were visible in the WPML String Translation system but did not appear on the site unless 'Auto register strings for translation' was enabled. When this option was disabled, the translations reverted to English. Solution: We provided a step-by-step solution to address the issue: 1) Navigate to WPML>>String Translation. 2) Search for and delete the problematic string from the 'pinegrow' text domain. 3) Go to WPML>>Themes and Plugins localization. 4) Scan the theme strings for translation. 5) Translate the newly added string again in WPML>>String Translation. Additionally, we suggested that the issue might be related to .mo files not matching the .po files used on the live site. We recommended: - Regenerate the .mo files from WPML>>Support>>Troubleshooting by using the 'Show Custom MO Files Pre-generation' dialog box and clicking 'Generate .Mo files'. - Clear all types of caches and check if the issue persists.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our support forum to open a new ticket. We also 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.
