[wp-meta] [Making WordPress.org] #6188: Language Pack generation: trigger on plugin update

Making WordPress.org noreply at wordpress.org
Mon Mar 14 18:13:14 UTC 2022

#6188: Language Pack generation: trigger on plugin update
 Reporter:  adamsilverstein           |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
 Feature request: always generate language packs on plugin update (or
 enable a way to trigger that behavior).

 For the Site Kit plugin, we have been receiving support requests stating
 (JavaScript) strings were not translated. As far as we can tell, this
 happens because these users aren't getting updated translation packs when
 we update the plugin. I imagine other plugins using JavaScript
 translations could also run into similar issues.

 * Site Kit uses hashed names for our JavaScript files, we found that
 without this users would get JavaScript errors after upgrades due to
 cached JS in their browsers (despite versioning the script tag).
 * Because WordPress i18n keys on the script file names, users need a new
 language pack for each Site Kit release, regardless of whether new
 translations were added (since our JavaScript file names change with each

 As I understand it currently language packs are only regenerated when
 someone updates a translation string. Is that correct? Would it be
 possible to have translations packs also regenerated for each plugin
 version update?

 If this would consume excessive resources as a default, maybe it could be
 an opt-in behavior, with a header option for "auto-regeneration", or
 perhaps a "translation version" string that when changed would trigger an

 cc: @ocean90 @swissspidy

Ticket URL: <https://meta.trac.wordpress.org/ticket/6188>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list