How to force rescan of plugin

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

Problem:
You are trying to force a rescan of a plugin using WPML, but WPML indicates that the files are already scanned and you are unable to trigger a rescan.
Solution:
We recommend updating your WPML plugins to the latest version to resolve this issue. Please ensure you have the following versions or later:
- WPML CMS 4.7.3
- String Translation 3.3.2
You can download the latest versions from here.

If this solution does not apply because it is outdated or not relevant 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 our support forum.

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: Exception

This topic contains 7 replies, has 0 voices.

Last updated by Osama Mersal 1 year, 1 month ago.

Assisted by: Osama Mersal.

Author	Posts
April 10, 2025 at 7:20 am #16916835
janneK-3	Background of the issue: I am trying to force a rescan of a plugin using WPML. WPML indicates that files are already scanned, but I need to trigger a rescan for a specific plugin. Symptoms: WPML says 'Files already scanned' and I am unable to force a rescan. Questions: Is there a way to force a rescan of a plugin in WPML? Is there a trigger to initiate a rescan?
April 10, 2025 at 8:30 am #16917221
Osama Mersal	Hi, Thanks for contacting WPML forums support. I'll be glad to help you today. 1) Please go to WPML-> Theme and Plugin Localization, select the plugin, and scan it. 2) Could you please share your Debug information with me? You can read a detailed explanation about it here. (http://wpml.org/faq/provide-debug-information-faster-support) The debug info will give me much information about how your site is configured. Best regards, Osama
April 10, 2025 at 9:03 am #16917336
janneK-3	I submitted debug information. I have tried that, but it says "Files already scanned". Is there a way to bypass that?
April 10, 2025 at 9:28 am #16917512
Osama Mersal	Hi, 1) I tested on a clean installation but didn't get this message. Could you please share a screenshot of the message? 2) It's unrelated to the issue, but according to your Debug.info, the WP memory limit needs to be increased. PHP memory is fine, but WordPress uses 40MB as default. The minimum requirement for WPML is 128 MB. (Kindly check this page https://wpml.org/home/minimum-requirements/) You can increase it by adding the following code in your wp-config.php file right before the */ That's all, stop editing! Happy publishing. /* line: /* Memory Limit */ define('WP_MEMORY_LIMIT', '256M'); define( 'WP_MAX_MEMORY_LIMIT', '256M'); Best regards, Osama
April 10, 2025 at 9:31 am #16917533
janneK-3	Here is the screenshot. The same does not happen in our staging for the same plugin. I have not seen this before in any other site.
April 10, 2025 at 9:33 am #16917557
Osama Mersal	Hi, Please update WPML plugins to the latest version and check the issue. WPML CMS 4.7.3 String Translation 3.3.2 You can find the latest version here. Best regards, Osama
April 10, 2025 at 9:49 am #16917623
janneK-3	Perfect. That fixed it and I was able to rescan plugin. I also had to make a change to certain string translation and then change it back and re-save in order to make one translation appear in frontend. Thank you.
April 10, 2025 at 9:52 am #16917634
Osama Mersal	Hi, It's great to hear that the issue is fixed. 🙂 Please don't hesitate to open a new ticket if you face any other issues. We are always happy to help you. Have a great day! Best regards, Osama