Uncomprehensible field behaviour

  • Resolved PK

    (@pkwp73)


    1 month, 2 weeks ago

    Hi,

    I just discovered Pods and I don’t understand the behavior of certain fields. I created additional fields for my products of WoCommerce.

    First, I need a subtitle. I created the field. I can add it in my template product. No problem.

    I don’t understand how dealing with it in the product admin. I add a new block at the end of the page, but the field appears strangely. For instance, in the field is in text, then I can modify it and it appears in the custom field. The field runs well in the template (hmmm… except the CSS field: I have to add it with my private CSS file!).

    If I choose a header… and I cutomize it with h3 for instance, the field is not editable! If the field is HTML content, it does not appear! But sometimes, I can force it in the custom field… But only sometimes!

    What did I disagree?

    A double thanks (for the response and for real free plugins)

    WP 6.9.1 with twenty-five and Gutenberg. The most possible full-free plugins!

Viewing 1 replies (of 1 total)
  • Plugin Support pdclark

    (@pdclark)

    1 month, 1 week ago

    There are two fields which are for presentation of the administrative input form: html and header

    When those fields are used, they display information in the form for the user, rather than providing editable input.

    For having editable text which displays as a heading, use a text field, then place the output of the text within a heading tag in the template (<h3>{@text_field_name}</h3> in Pods template syntax).

    For editable raw HTML or other code, use the code field.

    For editable rich text, (formatted text, editable HTML), use the WYSIWYG field.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.