WAIT: WPML + Bricks: Internal links (Button) not switched to translated pages + missing translated Bricks components

Bugs
1

Browser: Chrome 110
OS: macOS / Windows / Linux / etc.
URL: Link to a page that illustrates this issue
Video: Short screen recording that illustrates this issue (free tool: jam.dev)

Hi Bricks Support,

We’re using Bricks Builder + WPML and we’re facing a translation issue with internal links and components visibility.

1) Buttons internal link not translated

On the default language pages we create Buttons in Bricks and set the link using Bricks’ internal page picker (not a custom URL and not dynamic text).

After translating the pages with WPML, on the translated pages (secondary language) the buttons still link to the default language pages, instead of the corresponding translated pages.

Expected:
Button internal links should point to the translated page automatically (same content ID mapping through WPML).

Actual:
Button links keep pointing to the default language version.

2) Bricks components not showing on translated pages

We also have Bricks components/elements used inside pages (NOT templates, not header/footer).
In the translated language pages, those components are not rendered / not visible (or they appear missing), even though the page translation is completed.

We’re not sure what is the correct workflow to translate these “components inside the page” if they are not templates:

  • Should we translate the page via WPML ATE?

  • Or should we duplicate/translate the page in Bricks per language?

  • Is there a specific setting required for Bricks elements/components to be translatable and rendered correctly?

2

Hi @VASnake,

Welcome to the forum!

1) Button internal link not translated

I couldn’t replicate this issue locally. Can you try re-translating the page that includes the button with the link?

2) Bricks Components

Component instance property values will be bundled with the page strings, so you should find them when translating a page via WPML ATE.

As for component elements & properties, they are translated separately from pages since they’re global. Please refer to this article on how to translate components: How to use WPML with Bricks – Bricks Academy.

Let me know if you have any questions :slight_smile:

3

Hi!

Luckily, I solved the problem.
The problem was a missing setting in WPML called: Make themes multilingual in WPML->Language

For the components instead I followed the new guide and solved it

1 Like
4

Awesome :slight_smile: Thanks for the update!