Pods Dynamic Content Not Taking Brizy Editor Styling

Phill Healey

• February 12, 2020 14:31

I've created a custom post type using pods. I've created a post within that custom post type and begun building a page within the brizy editor which then displays the info.

Within the page I am adding content from the pods fields to populate content on the page. Most thing work as expected (eg images and plain text fields). However if I add dynamic content from a field which is a paragraph field (WYSIWYG or Plain Paragraph Text) the brizy styling is not applied.

If I go back to Pods and make this field a standard text field, then the styling is applied. However, on reverting the field back to any paragraph field type this results in the styling not being applied again.

At present it means that the only way to style Pods Dynamic Paragraph fields is to manually apply styling to the Brizy container, which is a bad idea and hard to maintain.

0

• 

  Alex

  • February 13, 2020 10:42

  Hi Phill,

  From what I see you are already discussing this with my colleague Sandra on ticket 5833. More details and explanations are needed to understand exactly what you did and how to reproduce it. Let's keep the discussion in one place.

  0
• 

  Don Schaffer

  • February 22, 2020 23:26
  • Edited

  I've encountered this with Pods with custom post types, as well, where non-standard text will mirror the CSS of whatever WordPress theme you are using (disregarding the formatting that is created in Brizy), forcing colors and styling to what would be assigned to the Gutenberg blocks - H1, H2, p, etc. vs the Brizy formatting.

  Therefore, in cases of the text formatting, you are correct, WYSIWYG formatting is pretty much controlled while you create your paragraph structure in the post's field on the backend.

  Additionally, guessing you may encounter this, too, when you find issues with taxonomies/categories or other elements displaying odd colors when implementing dynamic content (mirroring the theme, not the Brizy plugin), you can locate and troubleshoot them via the Developer Tools (Inspect Elements) in a web browser and then copy/paste the adjusted CSS into the Theme Editor. Not a perfect world yet, but it works!

  0
• 

  Alex

  • February 24, 2020 19:39
  • Edited

  Thank you for sharing!

   

  0

Please sign in to leave a comment.