[wp-trac] [WordPress Trac] #63944: load_script_textdomain doesn't use plugin's DomainPath for translation lookup

[WordPress Trac]

#63944: load_script_textdomain doesn't use plugin's DomainPath for translation
lookup
--------------------------------------+-------------------------
 Reporter:  jsnajdr                   |       Owner:  swissspidy
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:  6.9
Component:  I18N                      |     Version:  5.0
 Severity:  normal                    |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+-------------------------
Changes (by swissspidy):

 * owner:  (none) => swissspidy
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"60728" 60728]:
 {{{
 #!CommitTicketReference repository="" revision="60728"
 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.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/63944#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform