Download Pods
Download v 1.9.1 from WordPress.org | Downloads: 53,904
About Pods
Pods is a CMS framework for managing your own content types.
Create your own content types.
A pod, or content type, is a named group of input fields. The Pods plugin lets you create your own content types. Instead of with custom post types, each content type gets its own table.
Create a variety of different input fields, including text, paragraph text, date, number, file upload, and relationship (called “pick”) fields. Pick fields are extremely useful if you want to create relationships among your data. One example is if you want to relate an “event” item with one or more “speaker” items.
Easily display your content.
There are several ways to get Pods data to show up throughout your site:
- Add Pod Pages from within the admin area. Pod Pages support PHP and Wildcard URLs. For example, the Pod Page “events/*” will be the default handler for all pages beginning with “events/”. This allows you to have a single page to handle a myriad of different items.
- Add PHP code directly into your WP template files, or wherever else PHP is supported.
- Use shortcode to display lists of Pod items within WP Pages or Posts.
- The Pods API allows you to retrieve raw data from the database.
Migrate!
Pods includes a Package Manager, which allows you to import/export your database structure. You can select which features you want to “package up” and export it for easy migration. Pods also includes an easy to use PHP API to manage all types of Pod-related data for complex operations.
Changelog
1.9.1 – August 13, 2010
- Added: Support for Multisite Environment URLs and Super Admin role
- Added: Filters for Manage Tabs (to allow Pods UI to enhance these areas)
- Added: page.php now appears as “Page (WP Default)” in the Page Template list if page.php has no “Template Name” and exists in the theme (previously did not show up)
- Added: $is_new_item to save_pod_item() in PodAPI for use in Pre-save and Post-save Helpers — $is_new_item = true if adding an item, $is_new_item = false if editing an item
- Bugfix: drop_pod() in PodAPI function reference fix
- Bugfix: validate_package() in PodAPI assumed array, now it checks if the $data is an array
1.9.0 – July 29, 2010
- Added: Integration with body_class() – When on a Pod Page, two classes are added: pods, pod-page-URI-GOES-HERE; and if $pods is defined as a Pod another is added: pod-POD-NAME-GOES-HERE
- Added: pods_admin css class to wrap divs in Admin UI
- Added: New Pods Icon set for primary Pods menu and Pods Setup heading
- Added: pods_api_$action filter runs before $action runs in AJAX API operations
- Added: Support for tbl_row_id in save_pod_item, drop_pod_item, and load_pod_item params as alternative to pod_id (to eventually fully replace pod_id support)
- Added: reset_pod() added to PodAPI class to delete all Pod Items from a Pod without deleting the Pod itself
- Added: reorder_pod_item() added to PodAPI class to quickly and easily mass edit a number field for reordering purpose
- Added: Bulk save_pod_item() operations added in PodAPI class with new ‘data’ parameter (‘data’ should contain an array of ‘columns’ arrays)
- Added: Files previously uploaded will now be linked to the location in the file list for a column
- Improved: New $api->snap variable can be set to true in PodAPI class to silence all die() functions and throw them as Exceptions to improve API-based operations in advanced setups
- Improved: pod_query() now trims $sql once instead of three times
- Improved: pod_page_exists() now has a $uri parameter to pull data on a Pod Page at another URI than REQUEST_URI gives
- Improved: pods_access() now supports checking multiple at a time with addition of second parameter $method (AND/OR) and accepting an array for $priv
- Improved: Admin UI / Form Fields now have maxlength attributes on input fields with length restrictions
- Improved: Extended maximum length for Helper names, Template names, and and Field Comments to 255 characters
- Improved: Made Debug Information on Settings tab easier to read
- Improved: drop_pod() in PodAPI class now clears Pod items in a more efficient way
- Changed: DB update trims all Pod Pages of their beginning and trailing slashes “/” which previously were allowed but are now stripped during the saving process (normalization)
- Changed: save_page() in PodAPI class now strips beginning and trailing slashes “/” from URI before save
- Changed: Moved Package operations into PodAPI class
- Changed: Moved jqmWindow in Admin UI into wrap div and the pods_form div in the content form
- Changed: PodAPI class now returns all IDs instead of die(“$id”)
- Changed: import() in PodAPI class now uses save_pod_item() which gives it full support for bi-directional relationships
- Bugfix: load_pod_item() in PodAPI class no longer interferes with input helpers access to the data of a Pod Item as the Pod class is now initiated with an $id
- Bugfix: api.php now requires manage_pods priv to run load_sister_fields action
- Bugfix: Menu now runs after most plugins to avoid conflicts
- Bugfix: Menu no longer shows to any user, checks access via Pod roles
- Bugfix: pod_query() now checks against FOUND_ROWS() instead of FOUND ROWS() to cache or not
- Bugfix: style.css now uses the .pods_admin and .pods_form class selectors for each style defined to avoid overwriting other element styles on a page
- Removed: package.php has been removed from AJAX operations as code has been moved into PodAPI class
1.8.9 – July 7, 2010
- Changed: Minor UI changes
- Changed: author_id now getting stored
- Bugfix: Add / Edit javascript fix
1.8.8 – May 23, 2010
- Bugfix: bi-directional relationships
1.8.7 – Apr 16, 2010
- Bugfix: error when editing a unique field
- Bugfix: API handling for drop_pod_item
1.8.6 – Apr 14, 2010
- Bugfix: saving an empty pick column throws an error
1.8.5 – Apr 13, 2010
- Changed: save_pod_item improvements, see http://bit.ly/d4EWDM
- Changed: proper PHPdoc commenting
- Bugfix: timezone issues
- Added: ability to override pager var ($this->page_var)
- Added: load_helper, load_pod, load_template, drop_helper, drop_pod, drop_template methods support the “name” field as well as the id
- Added: load_page, drop_page methods support the “uri” field as well as the id