We’re very happy to announce a new point release for Pods: 2.6. Some of you may have been following the prominence of REST API coming in WordPress. It was even a rather large announcement at Matt Mullenwegg’s State of the Word address at WordCamp US 2015.
We’re very happy to announce that we’ve integrated REST API support directly into Pods Core, no longer requiring a separate plugin to handle your REST API endpoints. Josh Pollock has written up a very thorough article on the new REST API within Pods. For now, you still need to activate the WP REST API Beta in order to access and create your endpoints but once the REST API makes it officially into Core, you will no longer require this step.
Another big addition as part of WordPress 4.4 was the introduction of Taxonomy Term Meta Support. We’re also very happy to announce that we’ve fully integrated Term Meta into Pods 2.6. If you’re familiar with having to activate Table Storage in order to add additional fields to your Custom or Extended Taxonomies in Pods, you’ll no longer have to take that additional step. You will now be able to add fields to Taxonomies just as easily as adding fields to Custom Post Types. Your existing Table Based extended fields in Custom Taxonomies will still work, but now you’ll have the choice to shift them to Meta fields.
This patch also included several cleanups to our unit tests as well as two refinements to the Auto Templates function added to Pods Core in 2.5.5. The full details on this patch are available in our change log for the 2.6 patch. We’d like to send a special thanks out to Ramoonus, Sven Gilessen, Josh Pollock and Nic Ford as well as a pizza and a beer out to Phil Lewis for tirelessly working through the unit test failures and finding the code that was breaking existing tests.
Coming up next: Pods 2.7 if all goes well, we’ll have a new way to set relationships in forms! And of course, Pods 3.0 is also in progress, we’re in the process of backtracking from the CMB2 integration to where it was before that work started.
