Changeset 60728 for trunk/src/wp-includes/l10n.php

Timestamp:

09/11/2025 10:11:40 AM (5 months ago)

Author:

swissspidy

Message:

I18N: Use Domain Path for script translations if available.

This is a follow-up to [59461] from 6.8, which leveraged Domain Path for just-in-time loading of MO/PHP translation files.

Now, the same is done for script translations, which means plugins/themes shipping with their own translation no longer need to manually specify the translation path when calling wp_set_script_translations().

Props tusharbharti, swissspidy, shailu25, jsnajdr.
See #62244, #54797.
Fixes #63944.

File:

• trunk/src/wp-includes/l10n.php (modified) (3 diffs)

trunk/src/wp-includes/l10n.php

@@ -1135 +1135 @@
  * @see WP_Scripts::set_translations()
  *
+ * @global WP_Textdomain_Registry $wp_textdomain_registry WordPress Textdomain Registry.
+ *
  * @param string $handle Name of the script to register a translation domain to.
  * @param string $domain Optional. Text domain. Default 'default'.
@@ -1142 +1144 @@
  */
 function load_script_textdomain( $handle, $domain = 'default', $path = '' ) {
+    /** @var WP_Textdomain_Registry $wp_textdomain_registry */
+    global $wp_textdomain_registry;
+
     $wp_scripts = wp_scripts();
 
@@ -1148 +1153 @@
     }
 
-    $path   = untrailingslashit( $path );
     $locale = determine_locale();
+
+    if ( ! $path ) {
+        $path = $wp_textdomain_registry->get( $domain, $locale );
+    }
+
+    $path = untrailingslashit( $path );
 
     // If a path was given and the handle file exists simply return it.