Problem: You are experiencing issues with the new ATE redesign where the hover-line colors for translation fields are uniform, making it difficult to distinguish between automatically translated fields and those approved for translation. Previously, these were indicated by different colors which matched the progress bar at the bottom of the ATE window. Solution: We have updated the Advanced Translation Editor to address this issue. The color meanings are now as follows: - Blue: Translated fields - Dotted blue: Translated by automatic translation, might need review - Solid blue: Translated either by the translator or from translation memory - Yellow: Draft - Light grey in Gen3 (black in Gen2): Not translated We have removed the purple color, which indicated changes not saved on the ATE server, as we now autosave every time the user changes focus.
If this solution does not resolve your issue, or if it 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 visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client reported an issue with WPML's new address detection when the Object Cache Pro (OCP) plugin is enabled on Pantheon sites. Specifically, the problem occurred when trying to register the site address with WPML. Solution: We suggested that the client try using a different domain name than the one that was causing issues (https://wpml-chainalysis.pantheonsite.io/). There seemed to be some problems with the domain's registered sitekey, and using a different domain could resolve the issue.
If you're experiencing a similar issue with WPML's address detection when using the Object Cache Pro plugin on Pantheon, we recommend trying a different domain name to see if that resolves the problem. It's important to note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, please open a new support ticket. We also highly recommend checking 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 contact us in the WPML support forum.
Problem: The client reported that the support links in email notifications for WPML forum tickets were not directing to the specific comment in the forum thread as they used to.
Solution: We acknowledged the issue and forwarded the details to our systems team for investigation. After the systems team implemented the necessary changes, we asked the client to verify if the email links for forum ticket notifications were now functioning correctly.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client is trying to register WPML on a WordPress site hosted on Pantheon, which blocks access to the standard registration URL (wp-admin/plugin-install.php). The client cannot use the PHP constant method for adding the registration key due to security policies that prevent adding sensitive information to the git code repository.
Solution: We recommend storing the WPML license keys in text files within a private, non-version-controlled directory, such as
wp-content/uploads/private/
on Pantheon. The client should name the text files according to the Pantheon environment name or the local Lando subdomain. For example, the live environment would use 'live.txt'.
The client can then use the following code snippet in the
wp-config.php
file to automatically load the correct license key file based on the environment:
Problem: The client was experiencing an issue with the message "This site has moved to a new location" after migrating their website and using WPML version 4.6.7 on a test copy of the site. The problem was occurring within Lando, used for local development, particularly with the Pantheon recipe.
Solution: If you're experiencing this issue with WPML and Lando for local development, here are the steps to resolve it: 1. Perform a search and replace from your production site URL to your local Lando URL using the following command:
lando wp search-replace '://www.mysite.com' '://my.lndo.site'
2. Flush or rebuild your cache with:
lando wp cache flush
3. Delete specific WPML settings from your database with the command:
lando wp db query "DELETE from pantheon.wp_options WHERE option_name = 'WPML_SITE_ID:ate' OR option_name = 'WPML_TM_AMS' OR option_name = 'otgs_wpml_tm_ate_cloned_site_lock'"
Additionally, we have released a fix in WPML 4.6.7 which includes a new button "Force-enable WPML’s Advanced Translation Editor" on the Troubleshooting page. For more details, you can refer to our documentation:
