Problem: The client needs to translate the text 'LEARN MORE' that is hardcoded in the functions.php file of their theme, but it does not appear in the WPML String Translation after rescanning the theme. Solution: 1. We recommend going to WPML -> String Translation and enabling the option 'Look for strings while pages are rendered'. 2. Visit the front end of the website where the 'LEARN MORE' text appears. 3. Return to the String Translation page, uncheck the 'Look for strings while pages are rendered' option, and reload the page to check if the string appears.
Problem: The client is trying to allow other admin users to view and modify translations of Gravity Forms that were created and translated by their own user. However, each admin user only sees their own translations. Solution: We explained that the behavior the client is experiencing is expected. According to our documentation on setting up local translators and language pairs, once a translator completes a translation job, it cannot be taken by a second translator. If the client wants a different translator to edit and review the same translation, they need to resend the content for translation and assign it to that translator. As a workaround, we suggested that the admin users, who are also Translation Managers, can go to WPML -> Translation Management and resend the forms for translation. This will create new jobs in the system, allowing users to assign and open them. If this solution doesn't look relevant, please open a new support ticket.
