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: Compatibility
This topic contains 3 replies, has 0 voices.
Last updated by Otto 2 weeks, 1 day ago.
Assisted by: Otto.
| Author | Posts |
|---|---|
| December 3, 2025 at 4:31 pm #17631734 | |
|
lencS |
We are experiencing two serious problems related to the WPML integration inside Events Calendar Pro and The Events Calendar. 1. Fatal error triggered by The Events Calendar WPML-integrated code PHP Fatal error: Uncaught ValueError: Unknown format specifier "n" This happens inside a string passed through sprintf(). It appears that a translation string (likely Slovenian) contains an invalid %n placeholder, which immediately breaks PHP 8.2. Because Events Calendar relies on WPML for translations, this issue might be coming from a translated string that WPML loads. 2. Deprecated WPML integration code inside Events Calendar Pro Creation of dynamic property Tribe__Events__Pro__Integrations__WPML__Event_Listener::$wpml is deprecated This means the integration used by Events Calendar Pro is not PHP 8.2 compliant. What we need from WPML: We have valid licenses for both plugins, and this is happening on a live production website. |
| December 3, 2025 at 5:38 pm #17631914 | |
|
Otto WPML Supporter since 09/2015
Languages: English (English ) Spanish (Español ) Timezone: America/Argentina/Buenos_Aires (GMT-03:00) |
Hello, Regarding the fatal error. Please go to WPML > String Translation and search for: Fix the PHP placeholder in the translation there, and this should fix the error. The translation should be something like this: but probably there is a missing number or symbol there. Regarding the deprecation notice, it's on the TEC side. I suggest you let them know about the issue. On my end, I'll mention this to our compatibility team so they reach them too. But, in our experience, clients request are always more effective 🙂 Let me know how it goes with the fatal error, please. Best Regards, |
| December 4, 2025 at 8:42 am #17632983 | |
| lencS |
Hi Otto, thanks for the update. 1. We fixed the problematic strings and the fatal error is gone. 2. Regarding TEC: they are not responding to our tickets at all. If you have a direct line or any internal channel to escalate this, that would help a lot because we’re stuck on their side. 3. There is one more issue we keep seeing on most admin pages: load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,wp-hooks&ver=6.9:5 dashboard.js?ver=485900:2 It throws a 404 on the localization file and keeps repeating in the console. Can you check if this file is missing on your side or if something needs to be updated in the plugin? 4. We are also hitting a new fatal error related to Monolog inside Event Tickets. PHP Fatal error: Uncaught Error: Interface "Monolog\ResettableInterface" not found in The error happens when Logger.php is being loaded and the required interface Monolog\ResettableInterface is not available. From the stack trace it’s clear that multiple autoloaders are involved during the load sequence, so this might be a version mismatch or a missing dependency in the Tickets plugin. Can you check whether this is a known compatibility issue on your side or something that needs to be escalated to TEC? At the moment it results in a hard fatal inside the admin. Let me know how we can proceed. New threads created by Otto and linked to this one are listed below: https://wpml.org/forums/topic/console-error-2/ https://wpml.org/forums/topic/fatal-error-related-to-monolog/ |
| December 4, 2025 at 2:29 pm #17634807 | |
|
Otto WPML Supporter since 09/2015
Languages: English (English ) Spanish (Español ) Timezone: America/Argentina/Buenos_Aires (GMT-03:00) |
Hello, I am happy to hear that the fatal error is gone. We will try to reach TEC too about this and the deprecation notice. Regarding the other issues. In our experience, it is better to handle one problem per ticket. So, I created a new ticket for each problem. I'll follow up here: and here: Best Regards, |
