Pods plugin review and common issues

After creating or modifying a Pods custom post type, flush the WordPress rewrite rules: go to Settings → Permalinks and click Save Changes (without changing anything). This triggers the rewrite rule refresh. If the post type still does not appear, verify in Pods → Edit Pod → Advanced that “Show in Menu” (show_in_menu) is set to true and the menu position is not conflicting with another menu item. Also check if a user role restriction is hiding the post type from your current user role.

Relationship fields in Pods require nested template tags to access related content. In a Pods template, use {field_name.related_field_name} syntax for traversal — for example, {author.display_name} to get the display name of a related Author post type. For relationship fields that may have multiple related items, use the Pods repeater syntax: [each field_name]{@related_field_name}[/each]. If the field returns no data, verify the relationship field is populated for the current post in the admin and that the template is associated with the correct Pod.

Pods major version upgrades sometimes require database migration. After upgrading, go to Pods → Settings → Upgrade and run any available upgrade routines. If data appears lost, check the Pods database tables directly: Pods stores data in wp_pods, wp_pods_* tables or in wp_postmeta depending on the storage type configured. Use phpMyAdmin or Adminer to verify the data exists in the database. Also clear all caches — object caches or Pods-specific caches may be serving stale data after the upgrade.

Pods provides Pods Blocks for the Gutenberg block editor. Go to any post editor and search for “Pods” in the block inserter. The Pods Single Item (Field Value) block outputs a single field value for a specified Pod and field name. The Pods Loop block renders a list of items from a Pod with configurable template. For dynamic display of current post’s Pods fields in a block, the Pods Single Item block with “use current post” mode is the simplest approach without custom code.

In Pods → Edit Pod → [your post type], add a Relationship field. In the field settings, set Related Type to the target custom post type. Set the Relationship Storage to “Custom Relationship Table” for a true many-to-many relationship. Set “Pick a Limit” to allow multiple selections (0 = unlimited). Save the field. The relationship is now bidirectional — selecting a related item on one side also creates the reverse relationship, accessible from the related post type via Pods API or template traversal. Pods manages the junction table automatically.

For complex many-to-many content relationships (e.g., authors linked to books, books linked to genres, genres linked to publishers), Pods manages these more naturally through its dedicated relationship table storage. ACF Pro handles relationships via the Relationship field but stores references as serialized post meta, which performs less efficiently on complex relational queries. For straightforward custom fields on standard content, ACF is simpler to set up. For database-heavy relational content architectures, Pods’s custom table storage and relationship system have structural advantages.

No — Pods handles custom post type registration directly within its own interface. You do not need CPT UI when using Pods. The Pods plugin creates, manages, and maintains CPT registrations internally. If you want to use Pods for fields only and register CPTs through code or CPT UI for familiarity, that is also possible — Pods can attach fields to CPTs registered by other means.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.