Create connections between any of your content to help organize it in logical and useful ways with relationship fields.

Let Pods help you grow your development skills and manage content beyond the standard WordPress Posts & Pages. Check out pods.io for our User Guide, Support Forum, and our Slack Chat to help you develop with Pods.

Introduction

Content types that evolve with your needs

Create any type of content that you want — small or large — we’ve got you covered. Every content type created with Pods gets all the love it needs to grow up big and strong. You’ll get an easy to use interface that lets you manage custom fields and how your content type will function.

We now give you the power you’ve never before had with a single plugin because we’ve re-imagined how to manage content types from the ground up.

Create new content types

With Pods, you can create entirely new content types:

Custom Post Types – Content types that look and function like Posts and Pages, but in their own separate areas

Custom Taxonomies – Content types that look and function like Categories and Tags, but in their own separate areas

Avatars – Upload new media or select from existing ones, automatically integrates with get_avatar calls for Users extended by Pods

Relationships – Relate any item, to any item of any WP object type, another Pod, or a custom user-defined list — with bidirectional relationships

Relationships to rule the world with

Custom defined list

Post Types

Taxonomies

Users

User Roles

User Capabilities

Media

Comments

And many other relationships are also available including:

Image Sizes

Navigation Menus

Post Formats

Post Status

Sidebars

Countries (predefined)

US States (predefined)

Days of Week (predefined)

Months of Year (predefined)

Easily display your content

There are several ways to get Pods data to show up throughout your site, but with any WP object type you create or extend with Pods, you can use all of the functions and methods you’re already used to with the core WordPress API / Loop — out of the box!

Additionally, we have a United Theming API that lets you theme your content types across every type of Pod, regardless if it’s a post type or taxonomy or user, or.. you get the picture.

Contributors

Pods really wouldn’t be where it is without all of the contributions both financially and through code / time. Check out our GitHub for a list of contributors, or search our GitHub issues to see everyone involved in adding features, fixing bugs, or reporting issues/testing.

OR you can just install it with WordPress by going to Plugins >> Add New >> and type this plugin’s name

FAQ

Where do we go for Support on your plugin?

Our primary Support is handled through our Support Forums at https://pods.io/forums/. For the fastest support, you can contact us on our Slack Chat at https://pods.io/chat/ in the #support channel. We do not staff our Slack channel 24 hours, but we do check any questions that come through daily and reply to any unanswered questions.

We do have a community of Pods users and developers that hang out on Slack so you’re sure to get an answer quickly. We answer our Forum questions once a week with follow-up during the week as we’re prioritizing resources towards restructuring and improving our documentation.

I’ve found a Bug or I have a Feature Request

If you’ve uncovered a Bug or have a Feature Request, we kindly request you to create an Issue on our GitHub Repository at https://github.com/pods-framework/pods/issues/new. Please be very specific about what steps you did to create the issue you’re having and include any screenshots or other configuration parameters to help us recreate or isolate the issue.

Will Pods work with my Theme?

We don’t provide any special CSS or display attributes with your custom content so as long as your theme works with WordPress standard functions and the WordPress Template Hierarchy, you should be fine. You may need to create special PHP WordPress Theme Templates for your content, or you can use our Pods Templates and the Auto Template option to display your ‘template’ containing your custom content where your theme normally outputs the_content filter.

Reviews

I had to say it!
I use Pods occasionally. I love this plugin. I subscribed to the support mailing list.
I am telling you: I never ever seen such great support from any plugin around. This is the most supportive plugin around. These guys are THE Best!!! Kudos!!!

Pods continues to be the best plugin for creating and managing Custom Posts Types, Custom Fields, and Custom Taxonomies.
The presentation templating model is strong, and connections with Beaver Builder Themer layouts has provided everything we need to create and deliver highly structured content.
Thanks to all of the developers who continue to keep Pods at the forefront.

This plugin is really the best. It significantly eases data manipulation, can create relations between different entities.
There have been no errors working with it. I utilize it in every my project and can't imagine wordpress site without it.
Thank you, guys!

2.7.12 – December 20th 2018

Fixed: Serial comma display works again for Users, Comments, and Media relationships when used in Pods::display() and magic tag templating without specifying the object field you want to display, #5251 (@sc0ttkclark)

2.7.11 – December 7th 2018

Enhancements

Enhancement: Added: New pods_data_auto_calculate_total_found filter can be set to true to auto-calculate total_found() number right away after a Pods::find() query runs, defaults to false, #5232, (@sc0ttkclark)

Fixed: Simplify how we inject the PHP string into the JS #4787 Fixes #4786 which was creating syntax error in JS for number fields (@pglewis)

Fixed: Tooltips were not working in the Pods Templates or Roles and Capabilities components #4851 (Fixes #4850) (@pglewis)

Fixed: Isolates qtip styles and functionality to pods only which should hopefully resolve any issues with conflicting with other plugins/themes that may use the tooltip functionality [#4834] Fixes #4832 where tooltips were not displaying (@nicdford)

Fixed: Tooltip corrections: Update Pods Add New screen for extended taxonomies as Table Storage is not required since Term Meta was added by WordPress. #4609 (@pglewis)

Fixed: Issue where fields with particularly long post titles would extend past the width of the container #4831( Fixes #4700) (@nicdford)

Fixed: Disable the “Add New” button for relationships when we’re inside a media modal window (#4864). This is just a workaround until we can iron out the CSS and display for a modal from a modal. (@pglewis)

2.7.1 – December 8th 2017

Roll-back minimum version requirement for MySQL from 5.5 to 5.1 #4634 @sc0ttkclark

2.7 – December 4th 2017

New PHP & WP Minimum Version Requirements:

PHP Version Change Requirement 5.3+

WP Version Change Required 4.5+

Major Changes in 2.7 Release: Flexible Relationships:

New Relationship Field Format “List View”: The power of the new flexible relationships is our new modal window that opens within the existing record for relationship fields. This is modeled after the Media Modal from WordPress and provides full functionality to Add New related records or edit existing records all from within the parent record of the relationship. This is provided through our new List View field format for relationship fields. To see a demo of this field in action head on over to our YouTube

Add New with Flexible Relationships: The new flexible relationships will automatically enable Add New on all your existing relationships, but you can disable this from the Additional Options tab for each relationship field. You can switch field formats to the new List View from additional options tab as well.

Dynamic Field Views: The relationship fields and file upload fields have been rewritten to take advantage of “Dynamic Field Views”, driven by JavaScript. More technical details about the directions we went towards these field changes can be read about in our “Pods 2.7: What We Did and Why We Did It”

Significant Improvements and Fixes:

Enhancements for Date, Time & Date/Time Fields to improve class inheritance, use WP Defaults and allow for custom options for saving and display @JoryHOgeveen

Added: Pods Templates & Page Capabilities have been added to the Members Cap Filter and Pods Role Manager from Components, Roles & Capabilities. This corrects an issue where Pods Templates and Pods Pages were not available to Admins, only Network Admins. Admins will still need to have the pods_templates_ and pods_pages_ capabilities added to their role, but now they’ll be able to do this without additional code. Fixes (#4311). (#4342). [@JoryHogeveen]

2.6.9 – May 30th 2017

Added: Auto Template Fix: Add configurations setting to override and allow Auto Templates to run against the_content outside of the WordPress_Loop. By default now, it will only run inside the WP Loop. (#4088). [@jamesgol]

Fixed: When using shortcodes/magic tags with PDF attachments, ._src returns an image since WP 4.7. This will now output the URL of the file. You can still get PDF generated images using ._src.image_size or ._img. Fixes (#4040). (#4111). [@JoryHogeveen]

Fixed: Audio attachments will now work properly with pods_attachment_import. (#4155) [@sc0ttkclark]

Fixed: Update save_post / save_user handling with better fallbacks when nonce not active. Fixes an issue where the $is_new_item was not set as expected on post saves and user saves. Fixes (#3801,#3918). (#3936). [@sc0ttkclark]

Fixed: Update the attachment parent if updating a post type. Only updates if the parent isn’t set but allows file fields/upload fields to now properly show parent post. Fixes (#3808). (#3834). [@JoryHogeveen]

Fixed: Set Start of Week Day from General Settings; fixes issue where Calendar of datetime field in admin UI didn’t follow the first day of week settings from Setting, General. Fixes (#3826). (#3831). [@JoryHogeveen]

Fixed: PHP7 Compatibility issues, a few deprecated constructors and deprecated mysql_ with the use of $wpdb. Fixes (#3828). (#3830). [@JoryHogeveen]

Fixed: Use taxonomy capabilities in custom locations for taxonomy edit pages. Fixes an issue where Taxonomies assigned as Top Level Menu Items are not usable by Editors (only by Administrators). Fixes (#3569). (#3780). [@JoryHogeveen]

Fixed: Pods field() now properly handles user and media when the output type is pod/pods. Original issue resulted in $object being empty as user and media do not have a pick_val (#3694). Fixes (#3693). [@pcfreak30]

Fixed: Allow midnight (00:00) as valid time (#3555). If “Allow empty value” is unchecked and a value is not passed it will default to the current time, but it will still accept 00:00:00 as a valid value. Related to (#3488) [@jamesgol]

Fixed: Pass $strict = false to load_pod (#3554). This will keep the “Pod not found” message from being displayed during register of other post types. Related to (#3416) [@jamesgol]

2.6.4 – April 25th, 2016

2.6.3.1 – April 21st, 2016

Fixed: An Git / SVN deploy bug caused some files to not be properly pushed to WordPress.org SVN, this release is just to ensure everyone who may have updated to 2.6.3 during the period which we were fixing it will be able to still get the proper file updates

2.6.3 – April 21st, 2016

Fixed: Fix forcing underscores when loading Edit Pod Form (#3483). Fixes (#3095) [@sc0ttkclark] Kudos to @lkraav for helping us pin this particular issue down and bring it to resolution.

2.6.2 – March 24th, 2016

Added: Support for object fields when using Pods::field() with a specific $field and $option. This was also used to correct a problem with “fetching” Custom Taxonomy’s Term List when using Pods Feeds in Pods Gravity Forms Plugin. (#3437) [@sc0ttkclark]

Fixed: Correcting CSS used for Dashicon to remove conflict with icon usage in Divi. (#3404,#3406) [@jimtrue]

Fixed: Scheduled post preview message/URL. When a post was scheduled, the status message displayed at the top of the edit post page was malformed where the string placeholders were numbered. (#3234) [@sparkdevelopment]

2.5.5 – September 16th, 2015

Fixed: Changed Content property to fix spacing issues with AutoComplete Field where the formatted selection fields have awkward spacing between the selection box and the selection list. (#3098, #3097, #3099) Kudos to @nicdford

Fixed: Issue where [each] tag traversal did not work with Taxonomy in Pods Templates. Related notes regarding pod->object_fields for taxonomy added for 3.0 notes. (#3106, #3018, #3107, #3111) Major thanks to @pglewis

Fixed: permalink field traversal has only been working for post types, not for related taxonomies. (#2779, #3114, #3115) Kudos to @pglewis

Fixed: Fixes for Drag and Drop Reorder Action not working in ACT’s (#3015, #3016)

Fixed: Fix for pagination handling in shortcodes. Shortcodes currently use ‘pagination’ for two contexts (display and data) but if page or offset is supplied, it’s only meant for one context (display). (#2807, #3004)

Fixed: Updated Taxonomy to get called after cache is flushed (#2264, #2375, #2382)

Fixed: Cleared old unit tests from EDD (#2380)

Fixed: Allow fields to be sorted by orderby; Two separate but connected issues. First if orderby is passed then the $data array is never populated. Then looping through $ids will always give it results sorted by priority in the relationships field (data returned by lookup_related_items) (#2350, #2277)

2.5.2 – May 14th, 2015

Fixed: Issues with default values for number and other types of fields.

2.5 – December 30th, 2014

Major performance enhancements can now make things run up to 400% faster (props to @jamesgol!)

More unit tests — now 1,858 tests with a total of 13,420 assertions covering all content type, storage type, and field variations (props to @sc0ttkclark, @clubduece, and @mordauk! it was a group effort)

Added Travis-CI / Scrutinizer-CI for all pushes and pull requests to unit test and check for other issues

Allowed save_post_meta to delete single meta elements instead of update.

Fixed: An issue preventing fields from being sorted by orderby.

Fixed: Issue where fields, storing one value, returned arrays, instead of strings.

Allowed extending the link category taxonomy, if in use.

Added join as an acceptable tag for Pods shortcodes.

Fixed pods_error(): reversed logic that was emitting an error instead of throwing an exception when $display_errors is false

Fixed issue where user_url was created as a required field when extending users.

Add ability to use pods_group_add() in the ACT editor.

Security Update Reminder: As of Pods 2.4.2, we recommend all Pods 2.x installations be updated to the latest version, or replace your plugin files with the download of your version from https://wordpress.org/plugins/pods/developers/

If you need assistance in upgrading your Pods 2.x site to the latest version of Pods, please don’t hesitate to contact us at https://pods.io/help/

2.4.3 – June 23rd, 2014

Fixed: Pods Templates component now has better handling of the new shortcodes

Fixed: PodsUI data issue with Custom DB Table support

Fixed: Readonly fields and noncing now works properly, Pods 2.4.2 caused all forms with readonly fields to fail submission

Hardened: Further security hardening of the [pods] shortcode, added PODS_DISABLE_SHORTCODE constant to allow sites to disable the Pods shortcode altogether

2.4.2 – June 22nd, 2014

Security Update: We recommend all Pods 2.x installations be updated to the latest version of Pods to fix a noncing issue with form saving, or replace your plugin files with the download of your version from https://wordpress.org/plugins/pods/developers/

2.4.1 – June 19th, 2014

Fixed: Display of of hidden fields in Pods Forms

Fixed: Reordering fields in PodsUI

Fixed: PodsUI Admin Icon Display

Add new filter: ‘pods_pod_form_success_message’ for changing the message when Pods Forms are successfully submitted.