So @logikal16 officially agreed to change my title here at Pods to ‘Lead Developer’! It’s been a bit unofficial for a while now, but I’m glad I can officially say I’m leading Pods to a bright and better future!
We’re ramping up development for Pods 2.0 and have lots planned for our new site. Contribute Code or Join the Conversation Anyone who would like to contribute code or be part of the discussions around 2.0 or the new site, apply to be a contributor at: https://pods.io/contribute/ Donations Welcome Anyone who would like to help …
Note to self, update the Upcoming Features for Pods 2.0 page with updated information: https://pods.io/pods-2-0/
Pods 1.9.5 has now been released.. http://wordpress.org/extend/plugins/pods/ Changelog: Added: Multisite (3.0+) Network Activation support – Now when you click Network Activate, Pods will install itself correctly across all sites (and new sites as they are added) Added: Third option “$thankyou_url” in publicForm($columns, $label, $thankyou_url) which changes what happens when a form is submitted Added: Pod …
Thinking about a simple update_pod function that would handle all the class instantiation, param sanitization etc in cases where you just want to quickly add/update a single pod. Think update_post_meta(). I’m thinking update_pod($datatype,$tbl_row_id,$values) where $values is a key/value array of field and value … i.e. update_pod(‘books’,4,array(‘author_last_name’,’Shakespeare)); Thoughts?
Thought it’d be interesting to put together a good pros / cons list for Pods vs WP CPT for people to reference. http://wrangl.com/pods-vs-custom-post-types Feel free to contribute your two or more cents.
Anyone want to take up the task of creating a simple Poll package for Pods?
If you’re a Author / Contributor on the Pods Dev blog, you should be able to review the Upgrade Notes for Pods 2.0 which are currently set to private until they are somewhat finalized. Please take a look at it when you get a moment and chime in with any questions you might have. Developers …
Repeating fields is going to be awesome – but we need to decide how to store this data. We have a few options: For each ‘repeatable’ field, have a separate table devoted to it that has these fields: id, related_id, and value (stored as the field’s type, like date, number, etc..) For each ‘repeatable’ field’s …
Setup e-mail addresses for the team, updated Google Code logo and configured some Google Apps stuff for future use.