Problem: The client was experiencing issues with non-translatable links in their multilingual site. Solution: We corrected the custom XML configuration to ensure that the links became translatable. We then resaved the primary language page to apply these changes. We recommend checking the updated page to confirm that the links are now correctly functioning in different languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Please 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, you can contact us directly at WPML support forum.
Problem: The client needed to identify the domain associated with a payment failure notification for WPML's automatic translation service. The notification email did not specify which of the multiple client sites was affected, making it difficult to address the issue. Solution: We advised the client to check the domain with the payment issue by navigating to WPML -> Translation Management -> Tools tab. Meanwhile, we escalated the issue to our second tier of support for further investigation and to ensure future notifications include the domain information. Additionally, we identified the specific site with the payment issue as https://tech-automation.dk/. We also discovered a problem with the payment method and advised the client to contact their bank as retries would not succeed.
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 further assistance is needed, please open a new support ticket.
Problem: You are working on a site under development and trying to translate pages using WPML. You encounter a white blank page when attempting to translate pages, and the update process gets stuck. Additionally, an AMS Server Communication error "Active record not found" appears in the support logs. Solution: If you're experiencing this issue, we recommend ensuring that all admin users and translators (all users with access to ATE) have a valid firstname, lastname, and e-mail address in their profiles. This usually should solve the error.
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 persists, please open a new support ticket at WPML support forum for further assistance.
