#5737 closed defect (bug) (fixed)
block.json strings not being extracted
Reported by: | swissspidy | Owned by: | ocean90 |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Translate Site & Plugins | Keywords: | |
Cc: |
Description
Apparently the latest Gutenberg release (10.6.0) relies solely on block.json for translatable strings like block title and description.
While the WP-CLI i18n command does support extracting strings from that file, it appears that this is not the case yet for translate.wordpress.org.
Change History (12)
This ticket was mentioned in Slack in #core-editor by swissspidy. View the logs.
3 years ago
#3
@
3 years ago
WP-CLI 2.5.0 or nightly (2.5 will be out this week), or simply the latest version of the i18n command package.
Sounds like we'd need to prioritize fixing those bugs first?
This ticket was mentioned in Slack in #core-editor by carlosgprim. View the logs.
3 years ago
This ticket was mentioned in Slack in #core-editor by hypest. View the logs.
3 years ago
#6
@
3 years ago
Do you think this will affect WordPress 5.8 as well when it lands, since it includes all changes in Gutenberg 10.6?
This ticket was mentioned in Slack in #core by jeffpaul. View the logs.
3 years ago
#10
@
3 years ago
- Resolution set to fixed
- Status changed from assigned to closed
In dotorg17458:
Bin: Update WP-CLI to 2.5.0-dotorg
This is a custom WP-CLI build based on 2.5.0. The only difference is using a patched version of the i18n-command package which reverts an upstream change to restore the previous include/exclude behaviour.
See #meta5737.
What WP-CLI version is required for this? On wp.org we're still using 2.2.0 because issue #185 and #186 are preventing an update.