The issue is that when you remove a heading, text block, section from a page that has been build by Bricks, those old, removed, elements still show up in the WPML Advanced Translator tool. This is the case for their old and new version of the translator tool.
The only work-around I found is duplicating a page and afterwards remove the old page. This results in the Advanced Translation tool showing only the strings that are there on the page.
Hi,
thank you for your report. As you already mentioned, we have an internal task for this in our local bug tracker.
Once the issue will be fixed, we will update this topic
Hi Matej, I am on Bricks 1.12.4 and WPML 4.7.4 (+ String Translation 3.3.3) and am running into the same problem. The translation editor shows old headings and texts that do not exist on the page.
It seems to happen for elements that are copied from another page. so for example when I copy a Heading from one page to the other and change the text. In the translation editor I now get the original heading and also the new one as separate fields.
Anyone else experiencing the same problem?
I can make the translations but it’s super confusing to have tons of fields that are not on the page anymore. Also the translation manager can’t save the translation when not all fields are translated so I can’t just leave them empty.
I was unable to replicate the issue locally. Could you please share temporary admin access to the site in question with help@bricksbuilder.io? Please include a link to this forum thread in your email.
Thank you for sharing access. It looks like your page data is corrupted, but we haven’t been able to pinpoint exactly how this happened. If you’re able to replicate this issue from scratch, please share the steps so we can dig into it further.
I’ve added your use-case to our bug tracker because it shares the same underlying issue as the report found here: WIP: Query filter elements count in Emement Manager and Database. Meanwhile, I’ve reverted the status of this thread to “WIP” as we continue our assessment.
The core issue is that some elements still exist in the database, but their parent element is missing. As a result, they aren’t rendered in the builder or the frontend, but their content (like text) still shows up in the WPML ATE because the orphaned data still exists in the database.
The temporary solution is a bit cumbersome, but here’s how you may fix this issue in the meantime:
Manually copy elements (section by section, not “Copy all”) to a temporary dummy page.
Delete the problematic page and remove it from the trash completely.
Create a new page with the same slug as the deleted page.
Paste the elements back from the dummy page (you can use “Copy all” now).
Let me know if that clears things up or if anything’s unclear.
