WPML using older PSR standards

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	8:00 – 13:00	9:00 – 13:00	9:00 – 13:00	8:00 – 12:00	8:00 – 12:00	-
-	14:00 – 17:00	14:00 – 18:00	14:00 – 18:00	13:00 – 17:00	13:00 – 17:00	-

Supporter timezone: Europe/Zagreb (GMT+02:00)

Tagged: Bug

This topic contains 1 replies, has 2 voices.

Assisted by: Bruno Kos.

Author	Posts
April 16, 2024 at 7:43 am #15522979
Arty	Hello, I have a bug in my code when working in the development environment. Fatal error: Declaration of MonologLogger::emergency(Stringable\|string $message, array $context = []): void must be compatible with PsrLogLoggerInterface::emergency($message, array $context = []) in .... I have debugged this and found that removing psr from the WPML static autoload resolves this. Probably due to WPML using older PSR standards, I was wondering if there was any future of updating these? Or if I have to resort to some wrapper to ignore logging within WPML during runtime? It appears that the Logger within WPML conflicts with Laravel's Illuminate/Log package I am using Bedrock/Sage/Acorn. I had this bug when upgrading Acorn to v4. And after the community helped me we pinpointed it to WPML
April 16, 2024 at 1:17 pm #15525637
Bruno Kos WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) French (Français ) Timezone: Europe/Zagreb (GMT+02:00)	Hi, Thank you for contacting WPML support! Ok, to confirm, your issue is the same as this one? https://wpml.org/forums/topic/fatal-error-declaration-of-monolog/#post-15258791 There is an internal ticket where it is mentioned that the fix for this may end up in WPML 4.7, but this may change so I can't be certain when exactly. I will keep this thread updated. Regards, Bruno Kos