data-brz-translate-text
Hi, suddenly the text module add a new div
<div data-brz-translate-text="1">
which contain this css
.brz .brz-rich-text > * {
white-space: pre-wrap;
}
This code adds an unwanted line between paragraphs, as you can see in this screencast.
https://punto-rosso.d.pr/v/ExIWWj
Any idea why?
Thanks. Best
-
Hi,
Thank you for contacting us.
The <div data-brz-translate-text="1"> is added as part of the translation feature, which is causing the line breaks. Please try adding the following CSS to see if it resolves the issue:
.brz .brz-rich-text[data-brz-translate-text="1"] > * {
white-space: normal !important;
}Best regards,
Ariel H.0 -
Thanks for the suggestion. Unfortunately, it doesn’t work properly.
Check here a comparison of the different solutions I have tested:
https://punto-rosso.d.pr/i/zcstLf
As you can see, no one is the same as the original.
By the way, where should this “translation feature” be? I thought it was only available for the Cloud version, not for the WP plugin!
Any other suggestions are welcome.
Best.0 -
Hi,
Thank you for the update.
The translation feature you’re referring to is integrated into the Brizy Page Builder to enable compatibility with translation plugins.
Could you please provide us with temporary access to your WP Admin page so we can take a look. Kindly add us as an Admin user to your WordPress Dashboard and send the following details to communitysupport@brizy.io.
Community Post link: https://support.brizy.io/hc/en-us/community/posts/23047526960530
WordPress Admin URL:
Username:
Password:
URL of the problematic page:As a precaution, we recommend creating a full backup of your site.
Best regards,
Ariel H.0 -
Hi Amadeus,
Thank you for your detailed explanation and for taking the time to set up a staging site for testing.
Upon checking, it appears this issue is coming from incompatibility between Brizy and the Tickera plugin. While we understand the impact this may have on your workflow, resolving such conflicts requires adjustments from the plugin developers’ side.
The CSS solution we provided earlier remains the best workaround we can offer at this time. We recommend sharing these findings with the Tickera support team, as they would be in the best position to address the current issue.
If you have any further questions or need assistance with the CSS workaround, please let us know.
Best regards,
Ariel H.0 -
Hi Ariel,
I understand your point, but have you ever considered that the developers of Tickera might feel the same way about Brizy?
;)
Best
0 -
Hi Amadeus,
Thank you for the update. Please check with them first, perhaps they have already encountered this issue and possibly offer a solution.
Let me know how it goes.
Best regards,
Ariel H.0
Please sign in to leave a comment.
Comments
6 comments