Blog

Pods 1.12.4: Tweaks and bug fixes

Release Notes

  • Added: ‘offset’ parameter to Pod::findRecords, allows you to offset what results to start with, which is added to the offset calculated based on current page number and limit
  • Added: ‘page_var’ parameter to Pod::findRecords, allows you to set a custom page_var (default is ‘pg’), setting it will reset the current page number, set during Pod::construct()
  • Added: New ‘pods_rel_lookup_data’ filter to filter the data array itself (not just the MySQL resource given in ‘pods_rel_lookup’ filter above), great for customizing drop-downs for PICK fields
  • Fixed: ‘page’ parameter in Pod::findRecords wasn’t being validated as a number greater than 0, now forces a minimum of 1; Anything less will also reset the current page number, set during Pod::construct()
  • Fixed: Pods UI ‘label_add’ wasn’t being used on button at top of manage table list
  • Fixed: Pagination bug with custom page_var set in Pod object, would add the custom page_var to the URL over and over
  • Fixed: Upgrade script updated to include all upgrades prior to 1.6, which had been left out in a previous release
  • Fixed: More strict matching in Pod::findRecords for field names, instead of just removing ‘(‘ and ‘)’, it now removes ‘function_name(‘ first, so that fields with the same name as function names won’t be pulled