Opened 11 months ago

Closed 11 months ago

Last modified 11 months ago

#7088 closed defect (bug) (invalid)

Custom block translations are not hit by wp_set_script_translations.

Reported by: shimotomoki's profile shimotomoki Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:


The following plugins are hosted on

Plugin Directory
The plugin has been updated in Stable and 0.1.31 can be obtained from the Advanced tab.
Source Code

I am having trouble getting my JavaScript translated text to translate.

Translating WordPress contains the text translated by JavaScript.
(This is an example of Japanese)

However, when I install the plugin and set the language to Japanese, the translation is not done.

Is this a problem with the plugin code?
Or is there a problem with the translation (GlotPress) ?

Change History (3)

This ticket was mentioned in Slack in #glotpress by nekojonez. View the logs.

11 months ago

#2 @dd32
11 months ago

  • Resolution set to invalid
  • Status changed from new to closed 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, which would be the textdomain used for the language pack. That's probably a problem, as WordPress doesn't know that textdomain is the language pack.

I'm not seeing any issues on the 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:

#3 @shimotomoki
11 months ago

Thanks for your comment.

I bumped the version by saying that it wasn't translated in Stable, but it wasn't resolved.

I also posted on Developing with WordPress.

Last edited 11 months ago by shimotomoki (previous) (diff)
Note: See TracTickets for help on using tickets.