• I am building a template for a single post using the Site Editor in WordPress 6.5.5.

    I have added a custom field to the Posts content type. When I place that custom field on the template using the Pods Field Value block or the Pods Single Item block, it displays with an error — “Pods Embed Error: Pod not found.”

    The good news: When I view the post on the site’s front end, the field displays as expected.

    The bad news: The error message makes it look like Pods isn’t working with full-site editing (FSE).

    Am I doing something wrong? Is this the expected behavior? Or is there a workaround to get it to display something closer to what I get on the front end rather than an error?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Paul Clark

    (@pdclark)

    Does the issue resolve if the specific Pod name to be queried is specified in the Block, rather than allowing it to autodetect?

    In an FSE context, WordPress may be passing the current post object as a site template, rather than the post type being queried within the template, because FSE templates are stored as a post type.

    Thread Starter PatrickRiepe

    (@patrickriepe)

    Nope, same behavior.

    I was going to try to code the block to replace the dynamic content with some default content if the ID isn’t found.

    But with such a popular plugin, it would seem to me that people have used Pods Blocks in the Site Editor before and that I must have set something up wrong.

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