WPML cannot connect properly and shows file name mismatch error

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

Problem:
You are using WPML on your website and encountering a file name mismatch error that prevents proper connection to wpml.org for updates, despite having registered the plugin and confirmed outgoing connections with your hosting provider. You are concerned about losing existing translations.
Solution:
We recommend enabling WordPress debugging to better understand the issue. Here are the steps you should follow:
1. Edit your wp-config.php file and add the following lines before the comment /* That's all, stop editing! Happy publishing. */:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

2. Replicate the error.
3. Check the debug.log file located in the /wp-content/debug.log for any WPML-related errors.
4. Share the full error message with us.
Additionally, a similar issue has been documented and resolved in the past. You can review the details here: https://wpml.org/errata/file-naming-conflict-in-yoast-whip-vendor-library-on-case-sensitive-servers/

If this solution does not apply to your case, or if it seems 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 issues persist, 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: Exception

This topic contains 1 reply, has 0 voices.

Last updated by Andrey 5 months, 1 week ago.

Assisted by: Andrey.

Author	Posts
August 26, 2025 at 11:33 am #17348032
taniaB-3	Background of the issue: I am using WPML on my website vitalsenior.es, hosted on Hostinger. The plugin is registered, but I cannot connect properly to wpml.org for updates. I have already registered WPML successfully and confirmed with Hostinger that outgoing connections to necessary domains are allowed. I forced updates from Dashboard → Updates → Check again, but the problem persists. I am concerned about losing existing translations. Symptoms: WPML cannot connect properly and shows a file name mismatch error. The issue noted in the Commercial tab is: 'Fixed a fatal error caused by file name mismatches on servers using case-sensitive file systems.' Questions: How can I safely resolve the case-sensitive file mismatch error? How can I ensure WPML connects properly without losing existing translations?
August 26, 2025 at 12:42 pm #17348393
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+02:00)	Thank you for contacting WPML support. We had a similar case in the past, and it has already been resolved: https://wpml.org/errata/file-naming-conflict-in-yoast-whip-vendor-library-on-case-sensitive-servers/ To better understand your situation, could you please enable debugging, replicate the issue, and share the full error message from your debug.log file? Here are the steps: 1. Enable WordPress debugging by editing your wp-config.php file. Add (or modify, if these lines already exist) the following lines before the comment /* That's all, stop editing! Happy publishing. */: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', false ); 2. Replicate the error. 3. Check the debug.log file (located in the /wp-content/debug.log) for any WPML-related errors. 4. Copy and paste the full error message here.