Opened 9 years ago
Closed 9 years ago
#36872 closed enhancement (fixed)
No Action For Manually Updated Translations
Reported by: | ronalfy | Owned by: | ocean90 |
---|---|---|---|
Milestone: | 4.6 | Priority: | normal |
Severity: | normal | Version: | 4.5.2 |
Component: | Upgrade/Install | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
Right now, core, theme, and plugin have the do_action
of upgrader_process_complete
applied to them.
I feel this should also be applied for manual updates of translations.
Attachments (8)
Change History (26)
This ticket was mentioned in Slack in #core by ronaldhuereca. View the logs.
9 years ago
#3
@
9 years ago
- Keywords has-patch added
I went ahead with a new action language_updates_complete
since it didn't fall in the scheme of upgrader_process_complete
.
Use-case is for logging translations.
#4
@
9 years ago
Example output.
<?php Marker - May 31, 2016, 5:45:18 PM [31-May-2016 22:45:21 UTC] Array ( [0] => Array ( [language] => de_DE [version] => 4.5.2 [type] => core [slug] => default ) ) [31-May-2016 22:45:40 UTC] Array ( [0] => Array ( [language] => de_DE [version] => 3.1.5 [type] => plugin [slug] => akismet ) [1] => Array ( [language] => de_DE [version] => 2.2.1 [type] => plugin [slug] => cmb2 ) [2] => Array ( [language] => de_DE [version] => 6.0.5 [type] => plugin [slug] => stops-core-theme-and-plugin-updates ) [3] => Array ( [language] => de_DE [version] => 2.2.2 [type] => plugin [slug] => metronet-reorder-posts ) [4] => Array ( [language] => de_DE [version] => 1.4 [type] => theme [slug] => twentyfifteen ) [5] => Array ( [language] => de_DE [version] => 1.6 [type] => theme [slug] => twentyfourteen ) [6] => Array ( [language] => de_DE [version] => 1.7 [type] => theme [slug] => twentythirteen ) )
This ticket was mentioned in Slack in #core by ronaldhuereca. View the logs.
9 years ago
#6
in reply to:
↑ 5
@
9 years ago
Replying to slackbot:
This ticket was mentioned in Slack in #core by ronaldhuereca. View the logs.
See the linked Slack discussion about possible just reusing the upgrader_process_complete
for language pack updates.
#8
@
9 years ago
- Milestone changed from 4.6 to Awaiting Review
I was mistaken, @ronalfy is talking about wanting to log all language packs being updated rather than individually. The reuse of upgrader_process_complete
for language packs, however, wouldn't be a terrible idea for another ticket.
#10
@
9 years ago
Ended up going with upgrader_process_complete
thanks to the help of @DrewAPicture.
#11
@
9 years ago
There are a few version checks hooked into upgrader_process_complete
see trunk/src/wp-admin/includes/admin-filters.php?rev=37570&marks=110-114#L110. I think these should be removed in Language_Pack_Upgrader::bulk_upgrade()
.
#12
@
9 years ago
Thanks for the feedback @ocean90 . Patch updated and I also resolved a PHP warning error when the language is changed from the settings panel.
This ticket was mentioned in Slack in #core by voldemortensen. View the logs.
9 years ago
#16
@
9 years ago
36872.7.patch looks good. In 36872.8.patch I tweaked the docs a bit and restored the version checks after the upgrader_process_complete
hook.
@DrewAPicture Are you happy with the docs?
I'd be willing to go ahead with a patch on this pending the ownership of a core contributor or blessed by the component maintainer.