Scanning for strings in a mu-plugin

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.

WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/

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

Supporter timezone: Europe/Bucharest (GMT+03:00)

This topic contains 18 replies, has 8 voices.

Last updated by mikeD-5 9 months ago.

Assisted by: Radu.

Author	Posts
March 10, 2023 at 9:03 am #13214993
jeroenM-12	+1 for getting this fixed. We run into the same issue. The setup described, using a proxy PHP loader + actual plugin within a subdirectory, actually ironically seems to be "the WordPress way", as can be read on the link posted earlier in this thread (here again: https://wordpress.org/documentation/article/must-use-plugins/#caveats) Just to summarize: - We have two plugins (that have to run) in the mu-plugins folder. Both in in their own subdirectory. - Both plugins are being loaded with the proxy PHP loader file, which loads the mentioned plugins using require_once. - WPML only finds the loader file (which doesn't have a text domain) and doesn't find the actual plugins (which do have a text domain). - The strings in the plugins can not be translated, even though they are being called using the proper __() functions, which gets passed the textdomain at any time. Expected behaviour: the plugins within the subdirectories within the /mu-plugins directory should show up in WPML, with the correct text domains. They should be "scanable" for string, so the strings become translatable.
September 27, 2023 at 9:54 am #14472577
ondrejd-2	This thread was started back in 2020. 3 freaking years and your so called team did nothing about it. Can you please move your lazy asses and do something already? I am sick of trying to find hacks to get WPML to behave as expected. Every single time I come here for advice I find unresolved tickets. Every single time I contact you your answers are vague and not helpful at all. Bunch of unprofessional morons if you ask me. This plugin caused more headaches than all other plugins combined together.
October 31, 2023 at 11:11 am #14698891
martinA-36	This should be fixed asap, it can't be more than 4-5hours of work to read out the php files of the mu-plugins folder.
March 4, 2024 at 2:54 pm #15370279
mikeD-5	Has there been any movement on this? It would seem that you know what the issue is given https://wpml.org/errata/must-use-plugin-not-available-for-string-scanning-in-theme-and-plugins-localization/ so I don't really understand why this is still a thing.