Problem: The client is unable to translate the 'Other' option and the box prompt in a radio button question on their form when 'enable other option' is selected. Solution: We recommended checking if the issue matches a known problem related to Fluent Forms where error messages from global settings are not translatable. We provided a link to the workaround: https://wpml.org/errata/fluent-forms-error-messages-from-global-settings-are-not-translatable/. If this workaround does not resolve the issue or if it is a different problem, we suggested that the client provide temporary access to a staging or test site. This would allow us to investigate more effectively.
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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client was unable to add themselves as a translator on their WordPress site using WPML, despite trying to assign the necessary capabilities via custom code. Solution: We resolved the issue by temporarily changing the client's user role to Editor and then updating their profile. After this, we reverted the role back to the original setting and updated the profile again. This process refreshed the necessary capabilities, allowing the client to be added as a translator.
If this solution does not resolve your issue, or if it seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
