How much does Pods cost?
Pods is free and will remain free, but check out how much effort it’s taken to get it to where it is today!
Tagged: changes RSS Toggle Comment Threads | Keyboard Shortcuts
-
sc0ttkclark
-
sc0ttkclark
Pods 2.0 has arrived!
Background
The Pods Framework has been around since late 2008. Planning, design, development, and testing started in 2010 for Pods 2.0 leading to an Alpha release on January 2nd, 2012. Beta was released on August 12th, 2012. Now Pods 2.0 has finally arrived, as of September 21st, 2012!
After our soft launch, we’ve been working on bug fixes for the past few weeks to ensure maximum stability and backwards compatibility before going full force with our 2.0 announcement. That point has been reached and we’re ready for the flood of new users that awaits, including our awesome Pods 1.x users who are anxious to upgrade.
Have at it, and most of all — Enjoy the freedom of developing any type of content with any type of field that you can think of for WordPress!
Bug Reports / Feature Requests
Please report bugs and suggest features in our GitHub Issues area. We’ve got an awesome feature line up for Pods 2.1 that is already in progress, we’ll announce our 2.1 testing program in the next month. Pods 2.1 is scheduled to be released alongside WordPress 3.5 on December 5th, 2012.
Big Thanks to our Sponsors!
We have to really thank Automattic and Matt Mullenweg for all they’ve done to help us, we honestly could not have finished Pods 2.0 and taken it to the next level without their support.
RD2 provided some awesome UI design work for our new 2.0 upgrade screens.
MarkNet Group provided extra help when we needed it to keep the project going over the past two years, major kudos!
What’s new?
Below is a feature list that goes over what 2.0 offers, we hope you enjoy it as much as we have while we’ve used it on our own projects.
- Slick new interface, fully revamped to make managing your Pods easy and stress-free
- Large performance enhancements using transients and object caching (reducing queries per page load in both dashboard and site to the lowest possible number, sometimes that’s ZERO)
- New Upgrade wizard screens designed by RD2 will help you upgrade from previous versions and report any potential known issues beforeit actually upgrades your site
- We’ve partnered with Automattic to offer 1 free month of VaultPress service to users upgrading from Pods 1.x, you will see the offer in the upgrade screens.
- We’ve also partnered with iThemes to offer 25% off of a BackupBuddy license to users upgrading from Pods 1.x, you will see the offer in the upgrade screens.
- Add New Pod wizard guides you through creating or extending content types with custom fields
- Create New Content Types
- Custom Post Types
- Custom Taxonomies
- Advanced Content Types (each type lives in it’s own table, outside of the WP object architecture)
- Extend Existing Content Types
- Post Types (Posts, Pages, Existing Custom Post Types)
- Taxonomies (Categories, Tags, Existing Custom Taxonomies)
- Media
- Users
- Comments
- Create New Content Types
- Choose to store your data using meta-based storage (default) or custom table-based storage
- New Field Editor and Field Types
- New Field Type options built in (no more input helpers for most common input types!)
- Date / Time – Date, Time, or both
- Number – Plain Number or Currency
- Text – Plain Text, Website, Phone, E-mail, or Password
- Paragraph Text – Plain Paragraph, WYSIWYG (TinyMCE or CLEditor, or add your own), or Code (Syntax Highlighting)
- Color Picker – Choose colors, because colors are great (Using the default WP color picker, Farbtastic in 3.4)
- Yes / No – You can’t really go wrong with a checkbox, but we’ve added a few charms to make it stand out
- File / Image / Video – Upload new media or select from existing ones with our Media Library integration, or use a simple uploader, your choice
- Relationships – Relate any item, to any item of any WP object type or another Pod, now with improved Bidirectional relationship support
- New Field Type options built in (no more input helpers for most common input types!)
- New grouping fields API on the Add/Edit forms for Post Types, Taxonomies, Media, Users, and Comments (We’re adding a management UI for this coming in 2.1)
- New Shortcode popup integration with TinyMCE editor (now provide one-off templates within the shortcode itself)
- New Widgets (and provide one-off templates within the widget itself)
- New Form UI front and back
- New Attachments option available for File Uploads allows you to click “Attach” and select media items from the normal built-in WP Media Library pop-up
- New Componentsallow additional functionality to be enabled but not loaded if you don’t want/need them
- Pod Templates
- Pod Pages
- Pod Helpers
- Roles and Capabilities
- Add / Edit Roles (Administrator, Editor, etc..)
- Add / Edit Capabilities for each Role
- Markdown Syntax for Paragraph Text fields
- Migrate: Import from Custom Post Type UI
- Import Custom Post Types and Taxonomies created by the Custom Post Type UI plugin
- Import them all, or choose a few
- Optionally cleanup the Custom Post Type UI options when done, removing the imported objects from it’s control
- Basic WPML Integration and confirmed Polylang compatibility
- Fully Localized interface and error messages! All of our text strings in the plugin now run through the i18n functions. We don’t have any translations yet, but we’re looking at getting GlotPress setup for translators to start getting in.
- Requires at least WordPress 3.4 and is tested against WordPress 3.4 and 3.5 releases
Not sure about Pods 2.0 yet? Screenshot time!
-
hsatterwhite
Holy Cow in a plugin Scott! I’ve been looking at it since Thursday afternoon and it’s absolutely wonderful. The UI is great, intuitive, and very forgiving when you’re making mistakes. Love seeing how far you’ve come with Pods as it is by far one of the most powerful plugins/frameworks/extendomatic-in-a-box things to to ever happen to WordPress.
I’m a big fan of how you re-vamped “Helpers”. Using it as a custom post type with the built-in WordPress revisions feature is spot on smart. This is honestly the first time I’ve ever looked at Pods 2.0 in any of its forms. The really cool thing to me is that you created “Helpers” in a way that provides flexibility and history. Using Code Mirror for syntax highlighting, storing it as a custom post type, and utilizing WordPress’ built-in revisions function takes “Helpers” light years beyond what it was in the 1.x.x releases. As a long time user of Pods I’m completely overjoyed with Pods 2.0!
Again, thanks for all that you’ve contributed to the WordPress community.
-
sc0ttkclark
It’s messages like these that make what I do worth it. That’s exactly what I set out to do for Pods 2.0, so I’m very glad that was successful!
-
-
sc0ttkclark
Looks like there’s a compatibility issue with making Pods WP 3.2 compatible AND the version of jQuery used by WP 3.0.x which has a bug with the .data() function. Looks like it’s time to update readme.txt on Pods 1.9.x to 3.1+ (previously 2.8+)?
-
sc0ttkclark
It’s official, the terminology and usage of Columns will be changed to Fields in Pods 2.0
See http://dev.podscms.org/2011/04/17/terminology-poll-columns-vs-fields-what-makes-more/
-
sc0ttkclark
Dating Pods
No, not that type of dating
Talking about the Pods usage of date(), we should at all times use date_i18n() instead, which has two params just like date() which are $format and $timestamp. This ensures all places where a date is shown is set to the correct timezone that the WP site is set to. Any time we need to do a time() we should use current_time(‘timestamp’) and alternatively we can easily use current_time(‘mysql’) to get the current MySQL Date formated date + time.
A separate issue, I’m not sure if we need to store a GMT version of each date+time too, anyone have any thoughts there? Otherwise I’m leaning towards not storing an additional GMT date+time for every date+time field out in Pods.
-
sc0ttkclark
We should also avoid using MySQL CURRENT_DATE() and functions like it, instead, opting for the PHP usage of current_time(‘mysql’) or date_i18n($format,$timestamp) in it’s place to ensure the timezone is used everywhere and that we assume that the date+times we pull from the DB are actually set in the current timezone.
-
-
sc0ttkclark
WP_INC_URL >> WP_INCLUDES_URL
Renaming for consistency with WP constants. Though it doesn’t exist yet, it may in the future, hence the check to see if it’s defined first.
if (!defined('WP_INCLUDES_URL')) {
define('WP_INCLUDES_URL', includes_url());
} -
sc0ttkclark
pod_query >> pods_query
Renaming for consistency. Added pod_query function mapping to pods_query in deprecated.php
bjornet is discussing. 
bjornet 8:23 pm on September 5, 2012 Permalink | Log in to Reply
I really appreciate you for showing this, this example helps me as developer to set a decent pricetag on my work and of cause understand the tremendous amount of work you guys have put into Pods.