#34029 closed defect (bug) (fixed)
When installing a plugin/theme load also available language packs
Reported by: | ocean90 | Owned by: | ocean90 |
---|---|---|---|
Milestone: | 4.4 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Upgrade/Install | Keywords: | has-patch |
Focuses: | Cc: |
Description (last modified by )
Currently when installing a plugin or a theme which has a language packs available for yor locale you have to switch to wp-admin/update-core.php first to get the translations. That's unpleasant.
Attachments (1)
Change History (14)
#4
@
9 years ago
- Keywords has-patch 2nd-opinion added
34029.patch clears the plugin/theme cache so the update function can fetch the new plugin/theme.
@dd32: Could you verify this for me please?
This ticket was mentioned in Slack in #meta-i18n by ocean90. View the logs.
9 years ago
#7
@
9 years ago
- Description modified (diff)
- Keywords 2nd-opinion removed
- Summary changed from When installing a plugin/theme load also avaiable language packs to When installing a plugin/theme load also available language packs
#9
@
9 years ago
- Keywords fixed-major dev-feedback added; has-patch removed
- Milestone changed from 4.4 to 4.3.2
- Resolution fixed deleted
- Status changed from closed to reopened
I think this warrants back-porting to the point releases.
A plugin that previously bundled its own translations cannot remove them in order to exclusively use language packs, because WordPress installations prior to 4.4 won't download its language pack during installation of the plugin.
If this fix gets back-ported then plugins can begin to remove their bundled language files and use language packs instead, without the concern that users on (for example) 4.2 or 4.3 won't immediately receive the language pack during installation.
This looks like a caching issue.
wp_clean_plugins_cache()
gets called afterwp_update_plugins()
andasync_upgrade()
.Log from installing WordPress Importer: