Security Update Reminder: As of Pods 1.12+, AJAX API calls all utilize _wpnonce hashes, update your customized publicForm / input helper code AJAX (api.php and misc.php expect `wp_create_nonce(‘pods-‘ . $action)` usage)
Note: Oh hey, Pods 2.0 is coming out September 21st! Please help us continue to test the beta this week: http://dev.podsframework.org/tag/pods2/
Changed: get_current_url was an older function added by Pods a while back, pods_get_current_url is the new function name which is future-proof (get_current_url will point at the new one)
Added: A new check will deactivate the plugin if you happen to have another version of the plugin activated for testing purposes
Added: A quick enhancement for all to enjoy as a final farewell to Pods 1.x, File Browser now has a mouse-over image enlarge function (props @WallabyKid), see: http://podsframework.org/forums/topic/add-thumbnail-preview-to-jqmwindow-file-browser-for-image-files/
Fixed: Some plugins/themes use the wp_title filter incorrectly and do not pass the $sep and $seplocation variables, we now set defaults in those cases
Fixed: Some sites experienced PHP notices from the way we’ve been using parse_url, we now have a fallback for that handling which clears those up
Q & A: What’s going to happen to Pods 1.x when Pods 2.0 comes out? We’re going to release maintenence updates to Pods 1.14.x for a period of time, but there will be no further features added
