This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is unable to find strings using the search or filter options in the WPML String Translation interface, despite having scanned themes and plugins.
Solution:
We recommend the following troubleshooting steps after ensuring a full site backup:
1) Navigate to WPML>>Support page, and click on the Troubleshooting link. 2) On the Troubleshooting page, click on the following options in the Clean up section and wait for confirmation after each: - Clear the cache in WPML - Remove ghost entries from the translation tables - Fix element_type collation - Set language information - Fix WPML tables collation - Assign translation status to duplicated content - Fix terms count - Fix post type assignment - Cleanup and optimize string tables
If these steps do not resolve your issue, or if the solution becomes outdated, 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 with us 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.
Background of the issue:
I am trying to search for strings to translate using the Theme and plugins localization feature. I scanned themes and plugins and see the results in String translation. However, when I use filters or search, I get 'No strings found'. Here is a link to a screencast showing the issue: hidden link
Symptoms:
When using filters or search in String translation, I receive a 'No strings found' message.
Questions:
Why am I getting 'No strings found' when searching for strings to translate?
How can I resolve the issue with string search in WPML?
Welcome to the WPML support forum. I will do my best to help you to resolve the issue.
Does it happen after upgrading to the WPML 4.7 version? A couple of requests for tracking the issue.
1) Please share with us the WordPress debug.log(not WPML debug information) to collect more details on this. Refer to the following pages for instructions
To enable the WordPress Debug log, open your wp-config.php file of site root and look for define('WP_DEBUG', false);. Change it to:
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
In this case, the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check if you are getting any errors or warnings related to WPML in the log file.
If you can paste your debug.log to http://pastebin.com/index.php and provide me with that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion).
2) Please fill the private details fields after a full site backup. I would like to access the admin area of your site for further checking. Refer to the following links for more details about our private information sharing policies.
Thank you for the updates and Debug.log. The Debug log does not show any warning or error related to this.
I can reproduce the issue on your site. But interestingly it is working as expected in WPML>>Translation Management Screen. Please refer to this screencast for more details - hidden link
So please try the following troubleshooting steps after a full site backup{mandatory} and make sure the issue exists or not.
1) Go to WPML>>Support page, click on the Troubleshooting link (blue link in the middle of the page)
2) On the Troubleshooting page, please click on the following options in the *Clean up* section. Wait for confirmation of processing after each one.
- Clear the cache in WPML
- Remove ghost entries from the translation tables
- Fix element_type collation
- Set language information
- Fix WPML tables collation
- Assign translation status to duplicated content
- Fix terms count
- Fix post type assignment
- Cleanup and optimize string tables
Thank you for the updates. You can download the older version of WPML plugins from here - https://wpml.org/account/downloads/ (by clicking the Changelog icon).
Then deactivate and remove the latest version of WPML after a full site backup. After that manually install the older version (WPML 4.6.15 & String Translation 3.2.18).
Thank you for the updates. This requires further testing. So please allow me to make a duplicator copy of your site using the Duplicator plugin (https://wordpress.org/plugins/duplicator/) for debugging the issue on my local server.
This may be related to the following errata. Please try the workaround suggested after a full site backup and ensure you are getting the expected results.
