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: Development Tips 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
Fixing wp_list_pages and wp_nav_menu highlighting plus breadcrumbs on Dynamic Pod Pages
Recently I took it upon myself to begin fixing what wp_list_pages and wp_nav_menu sometimes messes up — highlighting what menu/page item you’re on.
The resulting code is used on the new Pods site, and it’s really only basic (wp_list_pages is basic in itself, while wp_nav_menu I’m only focusing on the ‘menu-’ classes. It covers whenever you’re on a URL that isn’t in WP (dynamic pod pages, 404s, etc) but matches items in the menu / pages list. Why wp_nav_menu doesn’t specifically look at the current URL itself is beyond me, but oh well
Pop this code into your theme functions.php file and you should be all set:
Along the same lines, here’s a handy breadcrumb fixer (example uses yoast_breadcrumb from the WordPress SEO by Yoast plugin):
The code above only goes two levels deep (like cool-stuff/*/*) and in the case of the second level, be sure to supply a field name in your $pods->parent variable to go off of to get the related name that’s called via $pods->get_field(‘parent_field_name.name’) in the breadcrumb fixer.
Thinking about adding this into Pods 2.0 core either as a component you can enable or have it just run with an option to disable it with a hook.
-
sc0ttkclark
Easy to use Code Editor on any Textarea (like used in the Pod Page / Template / Helper editors)
You can use the Bespin Bookmarklet to enable a code editor on any textarea you select. Follow the instructions here to start using it:
-
gr0b1
Does not have php
-
sc0ttkclark
Yeah, that is sad.
-
-
chris.pilko
Try the Ace Bookmarklet:
-
sc0ttkclark
Thx for buzzing in, didn’t realize they had a newer version already.
-
-
chris.pilko
I just saw this one on Lifehacker this morning. Looks intriguing, but I haven’t tried it out yet. http://www.listary.com/text-editor-anywhere.html
-
-
sc0ttkclark
Getting the Current Full URL of any page in Pods 1.9.6
Pods 1.9.6 isn’t out yet, we’re waiting on the fully working TinyMCE API to be ready, but once it is, we’ve added a new function called get_current_url()
You can use get_current_url() to get the full URL including the protocol, current hostname, and URI. This differs from just using $_SERVER['REQUEST_URI'] because it’s absolute. You can use this on your Pod Pages or when needing the real URL of a page. This function works both inside WP and outside WP (if WP is init via an include) and it gets the current HTTP_HOST which could possibly differ from a normal get_bloginfo(‘wpurl’)
function get_current_url () {
$url = 'http';
if (isset($_SERVER['HTTPS']) && 'off' != $_SERVER['HTTPS'] && 0 != $_SERVER['HTTPS'])
$url = 'https';
$url .= '://' . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'];
return apply_filters('get_current_url', $url);
} -
sc0ttkclark
Naming Pod Templates and Pod Helpers with a Slash and why it makes sense
When things first started out with Pods, the naming conventions for Pod Templates and Pod Helpers were pretty much a free-for-all.
Examples of names would be like:
- event_list (template)
- event_detail (template)
- event_save (pre-save helper)
- image_full (display helper)
- image_thumb (display helper)
- subscriber_get_info (display helper – advanced)
- etc…
But, now that your sites are becoming more complex, and you’re using many more Pods — I bet you are starting to see managing all of these becoming quite difficult. This is why I’d like to introduce to you the new standard we’ll be using in our examples, demo videos, tutorials, and our documentation.
Slashing without fear
Don’t worry, you can use slashes to help further distinguish your templates and helpers from each other! To construct a name, follow these simple rules and you’ll find yourself with easier to navigate management as well as perhaps a bit more readability when you implement them.
- If your template or helper is specific to one pod, try prefixing the name with pod_name/ otherwise try general/ or categorize it in a way that makes sense to you so you can keep templates and helpers that are alike together for easy usage
- Two levels may not be enough, you can use as many slashes as you want
- 2.0 will change the way helpers are grouped in management, so don’t worry about mixing up Display / Input / Pre-save / Post-save / etc.. types of helpers based on their names, that’s taken care of in the new UI
So examples of the new naming convention would be as follows:
- event/list (template)
- event/detail (template)
- event/save (pre-save helper)
- image/size/full (display helper)
- image/size/thumb (display helper)
- subscriber/get-info (display helper – advanced)
- etc…
I know that once you start using this new standard, you’ll find navigating like-minded Templates and Helpers much easier.
-
Masino Sinaga
Great news. Thanks, Scott. I have been waiting for this feature.
-
kimantebedan
Nice share Scott. Thank you
-
sc0ttkclark
Disposable and Secure phpinfo using a Pod Page
If you’re a dev and you find yourself uploading a file to run phpinfo(); why not try using a disposable Pod Page that’s access controlled by WordPress?
Create a new pod page and name it ‘phpinfo’, then place the following code in your ‘Precode’ area, then change the Page Template selected to ‘Page’ or ‘Page (WP Default)’ (depending on your theme).
$pods = 404;
if (is_user_logged_in() && (current_user_can('administrator') || (function_exists('is_super_admin') && is_super_admin()))) {
phpinfo();
die();
}
Now try going to yoursite.com/phpinfo/ and you'll see the info for your PHP configuration but someone who's not an admin for your site can't
No extra files.. no access to anyone who might use this information against you.
bjornet is discussing. 
chris.pilko, 
gr0b1 are discussing. 
kimantebedan and 
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.