Support » Plugin: Pods - Custom Content Types and Fields » This field is required.

  • Resolved mrtvy.kenny


    After save this comes up even though all required fields are filled. I think it might be some problem with date-time format?

    Anyway even re-saving old posts doesn’t work.

    How do I debug what is wrong? There is nothing in debug.log..

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Jory Hogeveen


    Hi @mrtvykenny
    This might be a bug.
    Please file a bug report at:
    Include any relevant screenshots, your process of how you got the error/problem and any relevant code.
    This will help us in reproducing the issue and find the solution.
    Marking this topic as resolved in favor of GitHub.
    Thanks! Jory

    Plugin Author Jory Hogeveen


    In addition to the above:
    Could you test if this issue still occurs with only Pods enabled on a default theme?
    You can test this using Site Health Troubleshooting:

    Let me know!

    same thing happens here.
    Ho do we solve it?

    Plugin Author Jory Hogeveen


    Assuming you are working with Gutenberg this is an issue that is still pending a fix. The Gutenberg developers didn’t provide any means for metaboxes to properly validate required fields before saving.

    In any case, please file a proper bug report at GitHub (see link above) and provide all info so we can try to reproduce your issue.

    In my case:
    it doesn’t matter if Gutenberg or Classic editor, I have this issue with custom post type.
    also it doesn’t matter if my template or twentytwenty.

    The strange thing is that even older items cannot be re-saved now..

    Site health is good.

    If I add Query monitor plugin, the only hint i’m getting after the unsuccessful save is this:
    Main error message is “This field is required.”

    and Query monitor addition:

    The message above was triggered by Core.
    Call stack:

    also one more observation: the post gets saved, but none of the pods fields does, only the default (title, content)

    I found it out, filed issue

    Problem is with YES/NO field which is set to be required, when set to “NO” value, it doesn’t save. It used to work before though…

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.