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!
Pods is free and will remain free, but check out how much effort it’s taken to get it to where it is today!
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!
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.
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!
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.
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.
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!
Pods C-Gen 0.2 Download and test it out!
Nice, we should start thinking about how to classify these types of optional features in Pods – I believe there is merrit in including something like this in Core but only if we can make it hidden by default. Pods 2.0 is going to be full of options, but I know tools like these could be useful (as long as their code isn’t loaded in by default).
Do you think this could be hidden by default as defined by the pods default role permissions? I think right now that might be the simplest way right now.
Not sure yet, would definitely need to discuss with everyone else – it appears this is something we haven’t really addressed before but with the IA restructuring we should be able to figure something out.
Like the updates in this one, would like to see more use of ‘label’ in the template field selection though
agreed – this was just a bug fix update lol…
So I’ve been using PODS for a while and have found the process of creating templates and pages very repetitive. For the most part all of my Pods follow some sort of list page and detail page format. I decided to rectify this and create a plugin that will allow for automatic code generation based on the columns in the selected pod.
Check out the attachment for a prototype of how this will work. There are still a bunch of features that I’d like to add before it’ll be ready for prime time (mainly code refactoring, and code generation options) but, I wanted to share the prototype with the other developers and get some initial reactions from the guys who know the system the best.
Please check out and let me know what you think
Interesting, definitely some usefulness here. A bit more tweaking for formatting / naming conventions I’d say, and then also some custom options to easily define the uri of the page, etc.. and have it update detail_url too. Lots of possibilities..
Agreed… Good suggestion on the detail_url… The next publish for this will more than likely have these option in them. Overall I’d like this to generate code with some sort of predefined layouts. That way generating visual templates for blog articles, product lists and whatever else you might think of will be easier.
Actually, populating all the magic fields for all the fields in a Pod would also be helpful, like listing each field label: field value.
It already does this… There was a bug in the code that prevented the JS from displaying the fields. I’ll upload another version now for ya.
I was also thinking too… Here is what I want to do next for the plugin
1. PODS Templates will not be generated with list or detail views anymore just templates
2. PODS Pages must be generated with a predefined template in mind and user must select template
3. List PODS Alphabetically not by ID
4. Add option to link to detail pages using a select box
5. Add code generation selection (either divs or tables)
6. Add Page header information to generate column information (such as table columns for grid type data)
7. Add option so people can choose what list page is named
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.