Ajax Search Lite Placeholder translation problem

This thread is resolved. Here is a description of the problem and solution.

Problem:
The customer translated the placeholder 'Search here..' from the 'Ajax Search Lite' plugin into French, English, and traditional Chinese. The default language of the site is French. Despite translating the placeholder into multiple languages, the French translation ('Chercher') appears in all languages instead of the respective translations. This issue corrects itself when the 'Auto-register strings' option is activated but reverts back to displaying the French translation when the option is deactivated.
Solution:
If you're experiencing this issue, we recommend you try the following steps:
- Go to WPML > Theme and plugin localization
- Check the "Automatically load the theme's .mo file using 'load_textdomain'" box
- Add the textdomain (probably "ajax-search-lite and/or ajax-search-pro") to the "Enter textdomain" field then save
- Scroll down and scan the theme/plugin
- Go to WPML > Support > Troubleshooting
- Click on "Show custom MO Files Pre-generation dialog box"
- Refresh the page (It should display the MO files dialog box)
- Regenerate the MO Files

If this solution does not resolve the issue, it 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 for further assistance.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Bug

This topic contains 1 reply, has 2 voices.

Last updated by Mateus Getulio 11 months, 3 weeks ago.

Assisted by: Mateus Getulio.

Author	Posts
May 20, 2024 at 11:01 am #15645152
elyesZ	Background of the issue: I translated the placeholder 'Search here..' from the 'Ajax Search Lite' plugin into French and English, which worked fine initially. I then added a traditional Chinese translation for the same placeholder. The default language of the site is French. Symptoms: Despite translating the placeholder into multiple languages, the French translation ('Chercher') appears in all languages instead of the respective translations. This issue corrects itself when the 'Auto-register strings' option is activated but reverts back to displaying the French translation when the option is deactivated. Questions: Why does the French translation appear in all languages despite having translations for each? How can I fix the issue so that each language displays its respective translation without having to keep the 'Auto-register strings' option activated?
May 20, 2024 at 7:26 pm #15647283
Mateus Getulio Supporter Languages: English (English ) Portuguese (Brazil) (Português ) Timezone: America/Sao_Paulo (GMT-03:00)	Hello, welcome to the WPML support Forum! Please try the following procedure to try to fix this issue: - Go to WPML > Theme and plugin localization - Check the "Automatically load the theme's .mo file using 'load_textdomain'" box - Add the textdomain (probably "ajax-search-lite and/or ajax-search-pro") of the string to "Enter textdomain" field then save - Scroll down and scan the theme/plugin - Go to WPML >Support > Troubleshooting - Click on "Show custom MO Files Pre-generation dialog box" - Refresh the page (It should display the MO files dialog box) - Regenerate the MO Files If it doesn't work, I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it. Our Debugging Procedures I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site. Privacy and Security Policy We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ IMPORTANT - Please make a backup of site files and database before providing us access. - If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link Please, let me know if you need any additional details. Have a nice day.