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

Making WordPress.org noreply at wordpress.org
Tue Mar 15 15:29:46 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  |  Resolution:
 Keywords:                            |

Comment (by adamsilverstein):

 > While this makes zero sense

 Given the scale of our install base, we run into every edge case. We found
 a subset of users regularly missed critical JS updates unless we performed
 this per version naming change.  Unfortunately it looks like this breaks
 translations so we may need to investigate an alternate approach to
 solving this issue.

 I'm curious: why do translations key off of file names instead of the
 script handle?

 > I can confirm that each version gets its own language pack if there were
 string changes or the latest theme/plugin version has no language pack
 yet. But there are indeed some delays:

 Sounds like close to an hour between plugin update and new language packs

 > There's a delay between the language pack being built, and when it's
 installed on the site as well, which could be upwards of 24hrs depending
 on the site, or even delayed until the next time they manually install a
 plugin if the site doesn't have write access to the language files.

 Could we improve this by scheduling a language pack update for ~ 1hr after
 a plugin is updated - when we would expect new language packs to be
 available for the plugin?

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

More information about the wp-meta mailing list