Problem: If you're experiencing an issue where opening listings in an incognito window or with an empty cache causes the browser to load the listing page briefly but then redirects to a default /view-listing/ page which is blank, this might be due to the WPML browser redirect script. This occurs because Tracking Prevention in incognito mode blocks cookie storage, leading WPML to incorrectly redirect based on the browser language. Solution: We recommend the following steps to diagnose and potentially resolve the issue: 1. Create a full backup of your site. 2. Temporarily disable all WPML plugins. 3. Test opening a listing in an incognito window again. If the issue persists even with WPML disabled, it is likely not caused by WPML but could be due to another plugin, theme logic, or custom redirect handling on your site.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 continues, please open a new support ticket with us for further assistance.
Problem: You are experiencing an issue where WPML is adding 'amp;' to the '&' symbol in a link within a Gravity Form confirmation, causing the link to break. Solution: This is a known issue with WPML. While our developers are working on a permanent fix, we recommend using the workaround provided in our errata. You can find the detailed steps here: WPML Translated Links with Query Parameters.
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 WPML support forum for further assistance.
Problem: The client has translated a Gravity Form using WPML's Advanced Translation Editor, ensuring that value fields remain in English while translating label fields to maintain conditional logic. However, after modifying the English form, the values in the translated form switched to French, requiring manual correction. Solution: We explained that updating the default language form (adding, deleting, or updating content) necessitates updating the translated versions as well. This behavior is documented here: Updating Forms Translation. To prevent the French translation from being applied to certain fields, we suggested using the Glossary feature to mark specific terms as non-translatable. This ensures they remain unchanged during translation. More information on managing glossary entries can be found here: How to Create and Manage Glossary Entries.
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. Should you need further assistance, please open a new support ticket at WPML Support Forum.
