[wp-meta] [Making WordPress.org] #7088: Custom block translations are not hit by wp_set_script_translations.
Making WordPress.org
noreply at wordpress.org
Fri Jun 23 03:19:41 UTC 2023
#7088: Custom block translations are not hit by wp_set_script_translations.
--------------------------------------+----------------------
Reporter: shimotomoki | Owner: (none)
Type: defect (bug) | Status: closed
Priority: normal | Milestone:
Component: Translate Site & Plugins | Resolution: invalid
Keywords: |
--------------------------------------+----------------------
Changes (by dd32):
* status: new => closed
* resolution: => invalid
Comment:
https://plugins.trac.wordpress.org/browser/flip-box-
block/trunk/readme.txt?marks=7 still specifies `0.1.21` as the latest
version, so 0.1.31 isn't stable / being built.
The last language pack built for the plugin was `0.1.6`, that contains the
`flip-box-block-ja-fe9085f3d98a08dce07b16c5b89041e9.json` JS translations.
It looks like the textdomain you're passing to `wp.i18n.__()` might be
`flipbox-block` which isn not the slug on WordPress.org, which would be
the textdomain used for the language pack. That's probably a problem, as
WordPress doesn't know that textdomain is the WordPress.org language pack.
I'm not seeing any issues on the WordPress.org side here, so this is
likely an issue with the plugin. Meta trac isn't the appropriate place for
developer support, one of these will likely help:
- https://wordpress.org/support/forum/wp-advanced/
- https://developer.wordpress.org/plugins/internationalization/
- https://developer.wordpress.org/plugins/internationalization/how-to-
internationalize-your-plugin/#handling-javascript-files
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/7088#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list