Symbols displaying wrong locale when refreshing the previewer

Bugs
,
1

I think i may have found a bug with how the Visual Designer queries Symbols with Default locale regardless of which locale is selected.
This only happens when refreshing the previewer and not when just changing locale only.
This is problematic for us since we have a Dynamic Preview URL script that changes the URL in the previewer and triggering a refresh when changing locale in the Visual Designer.
I inspected the network requests and it seems to be the query for the Symbol wrongfully supplying the Default locale. It correctly supplies the selected locale when not refreshing the previewer.

I also tried using Inherit State toggle under Advanced Options on the Symbol but with no success.

Builder public api key
2ed15156525641798af8def331c7a124

Detailed steps to reproduce the bug

  1. Create a Symbol with a simple Text element and translate it to different locales.
  2. Save it and use it on a Page.
  3. Change locale on the Page and the watch the Symbol translation working correctly.
  4. Now refresh the previewer and watch the Symbol wrongfully go back to the Default locale.

Screenshots or video link
Below we can see that whenever the Refresh Preview is clicked the Symbol is being queried by the Visual Designer with the Default locale regardless of the selected locale. (The Symbol is the “SHOP NOW” button).

image
image1412×494 41.5 KB

Below we can see that on the actual published website the Symbol displays the correct translation. Note that on the actual website the content of the Symbol is part of the Page Content Query response and not a separate query for the Symbol like in the Visual Designer. (This separate query for Symbols in the Designer may be where the bug is).

image
image1052×356 14.9 KB

Code stack you are integrating Builder with
React

Thanks in advance!

2

Just wanted to bump this topic.
I feel like its kind of a critical issue, but on the surface would seem like a pretty easy fix!

3

Hello @panen,

Thank you for providing the detailed steps. I am pleased to confirm that I was able to successfully reproduce the issue you are experiencing.

We are discussing this internally to determine the appropriate next steps. I will keep you informed as soon as I have further updates.

In the meantime, please do not hesitate to reach out if you have any additional questions or further information to share.

Kind regards,

1 Like