Problem: The client is experiencing issues with WPML on their site, including data corruption. Specific problems include: 1) MapsMarker Pro translated data not displaying correctly on the frontend, 2) ACF translated search results not showing the translated version, and 3) inability to open the Croatian version of the 'About Us' page. Solution: For the MapsMarker Pro issue, we verified that the translated string appears correctly at the specific URL provided by the client. For the 'About Us' page, we made a minor title change and updated the page, which resolved the access issue. Regarding the ACF fields, we recommended changing the format of the field choices from a simple list to a key-value pair format (e.g., 'red : Red') and setting the return format to 'both'. This adjustment should help display the translated versions correctly. For more details on translating ACF fields with WPML, visit Translating ACF Field Labels with WPML.
If these solutions do not resolve your issues or seem outdated, we recommend opening a new support ticket. We also advise 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 WPML Support Forum.
Problem: You are trying to translate Maps Marker Pro maps and markers, but they are showing partially translated and partially in the original language, despite being fully translated in the backend. Solution: 1. Go to WPML-> String Translation and search for the destination URLs to ensure they are correctly translated. 2. If the issue persists, update the marker URL, clear the WPML and site cache, and then regenerate the MO files from WPML-> Support-> Troubleshooting.
If this solution does not resolve your issue or seems outdated, we 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 still need assistance, please open a new support ticket at our support forum.
Problem: If you're experiencing issues with URL parameters not being passed when switching languages on your site, despite having 'Preserve URL arguments' correctly configured, this might be due to the parameters being populated via JavaScript.
Solution: We recommend modifying your 'Search' button to submit and reload the page. This adjustment should ensure that the parameters are correctly passed to the language switcher. If you prefer to keep your current setup, you will need to implement custom code to modify the language links in the language switcher to include these client-side populated 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 was experiencing issues with ACF Field Groups attached to portfolio items. The fields appeared for translation once and then disappeared from the post translation screen, even though the group was set to "Same fields across the languages" option. Additionally, there were problems with translating a page, custom grid elements not showing in the translated language, and the language switcher not functioning correctly on the portfolio page.
Solution: 1. We explained that when "Same fields across the languages" is selected, the translation settings for most custom fields will default to either "Copy" or "Translate". To see the field data in the translation editor again, the client should make a minor change to the data and update the translation.
2. We advised the client to check the translation settings in "WPML > Settings > Custom Field Translation" and ensure that the fields are set to "Translate" instead of "Copy". After adjusting these settings, the client should retranslate the page.
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 open a new support ticket.
