[buddypress-trac] [BuddyPress Trac] #9187: Custom BuddyPress translation files are no more loaded since WP 4.6

[buddypress-trac]

#9187: Custom BuddyPress translation files are no more loaded since WP 4.6
--------------------------+---------------------
 Reporter:  imath         |       Owner:  imath
     Type:  defect (bug)  |      Status:  closed
 Priority:  strategic     |   Milestone:  14.0.0
Component:  Core          |     Version:  1.0
 Severity:  major         |  Resolution:  fixed
 Keywords:  has-patch     |
--------------------------+---------------------
Changes (by imath):

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


Comment:

 In [changeset:"13936" 13936]:
 {{{
 #!CommitTicketReference repository="" revision="13936"
 i18n: bring back custom locations for translation files

 Prior to WordPress 4.6, it was possible to completely override the
 translation file with a custom one from one of the
 `'buddypress_locale_locations'` filterable list items.

 With WordPress 6.5 latest improvements about l10n, we are now able to
 bring these back. Making it easier for users to customize every BuddyPress
 strings should help them build match their community needs (e.g.: using
 sport/school/working/any other wording).

 3 functions has been introduced:

 -  `bp_get_custom_translation_file()` is looking for a file name into
 `'buddypress_locale_locations'` filterable list items.
 - `bp_load_custom_translation_file()` is the `'load_translation_file'`
 filter callback for regular translation files.
 - `bp_load_custom_script_translation_file()` is the
 `'load_script_translation_file'` filter callback for JavaScript
 translation files.

 The `bp_core_load_buddypress_textdomain()` function has been deprecated as
 it was pretty useless since WordPress 4.6.

 Props espellcaste

 Fixes #9187
 Closes https://github.com/buddypress/buddypress/pull/316
 }}}

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9187#comment:3>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac