WIP: Fatal error caused by %S in translation string (Bricks 2.0)

Browser: Safari 18.5, Edge 138, Chrome 138
OS: MacOS
URL: https://test.local/?bricks=run
Video: Short screen recording that illustrates this issue (free tool: jam.dev)

[Please describe this bug in as much detail as possible so we can replicate & debug this bug]
After updating to Bricks 2.0, I get a fatal error when editing a page in the builder.
(Error message: Fatal error: Uncaught ValueError: Unknown format specifier “S” in i18n.php on line 939)
I’m using the Korean language setting (ko_KR) in WordPress.

Hello @alpine4root and welcome to the forum :partying_face:

We already received the report about this one, so I’ll just link this topic to the internal task that we have. Once it’s solved, we will update the topic.

As for a workaround, you will have to switch the language.

Thank you,
Matej

1 Like

Do you build a multi-language site? If so, which plugin?
I am building a multi-language site and plan to use WPML

Hi @Newbie,

is this question for me? If yes, I can’t tell you, as my websites are not multilingual. But, we do have

integrations.

Best regards,
Matej

Temporary Workaround: Disable Korean Translation Files

If you’re encountering a Bricks Builder editor error after the 2.0 update, the issue may be caused by outdated or incompatible translation files.

:wrench: 1. Remove or Move the Korean Translation Files

Since the error references i18n.php, try removing or temporarily moving the following files:

  • ko_KR.mo
  • ko_KR.po

Example path:

/wp-content/themes/bricks/languages/ko_KR.mo
/wp-content/themes/bricks/languages/ko_KR.po

2 Likes

Hi @Matej ,

Thanks. I’ve read through the posts.

My site is a woo store. Which multilingual plugin do you recommend, please?

Can I set a different font family for each language in the theme style?

Best Regards,

Newbie

As for plugin recommendations, you will have to try them and pick one that best suits your needs. I sadly can’t give recommendations on this, as I’m personally not using any one.

For this question, it also depends on how translation plugins handle the pages. If there is a HTML markup somewhere that indicates a language, you can use this one for a quick custom CSS.
If you create different pages for different languages, you can then check the pages and so on.
I think it’s best to open new topic in How To once you get to this.

Best regards,
Matej