Dynamic text elements with minor errors.
Hello
1 I added dynamic text output using # - No styles are applied to the text.


2 I decided to add dynamic text output in a different way. This time, the styles are applied. I noticed that extra space is being added under the text element—the constructor adds an extra <p> element, and this empty element adds empty space.


Please correct these errors in the future.
-
Hi Timur,
Thank you for contacting us.
Could you please check if you’re able to replicate the issue on this new staging site and let us know the results? Brizy and Brizy Pro are already activated there, and you’re welcome to add any other plugins you need in order to reproduce the issue.
[**]
Once you’ve had a chance to test it, please share your findings with us so we can continue investigating.
Best regards,
Ariel H.0 -
Hello
You can visit the site and see where the problems are. I wrote about the issue with extra indents a year or two ago, but it still hasn't been fixed.
I've added two templates to Brizy.
I'm also showing a similar issue with displaying the description for a blog category.




I wrote about the problem with extra indents in the blog category description a year ago, but it still hasn't been fixed.
0 -
Hi Timur,
Thank you for your cooperation.
After checking, the extra space or gap that appears when linking dynamic content inside the Text element is related to Pods compatibility. This behavior does not occur when using Advanced Custom Fields (ACF).
Additionally, applying styles to dynamic content using the # method works as expected with ACF. For this reason, you may want to consider switching from Pods to ACF to avoid these limitations.

Kind regards,
Ariel H.0 -
You claim to support the PODS plugin. I'd like to see Brizy + Pods fix some minor bugs. I chose PODS for creating websites; it's a more convenient solution for my needs.
Similar issues with unnecessary indents and styles also exist when displaying category descriptions.
Please fix these issues in future updates. I think your specialists will resolve this issue quickly.
Thank you!
0 -
Hi Timur,
Thank you for taking the time to share your feedback.
Regarding this behavior, we may gradually phase out the use of the # for consistency moving forward. I’ll also make sure to pass your notes along to the team so they can review the issues you mentioned, including the extra indents and styles when working with PODS and category descriptions.
Best regards,
Ariel H.0
Please sign in to leave a comment.
Comments
5 comments