Pods Development Blog

Tagged: releases RSS Toggle Comment Threads | Keyboard Shortcuts

  • sc0ttkclark 7:17 am on October 4, 2012 Permalink
    Tags: , , releases   

    Pods 2.0 has arrived! 

    Background

    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!

    Bug Reports / Feature Requests

    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.

    Big Thanks to our Sponsors!

    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!

    What’s new?

    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.

    • Slick new interface, fully revamped to make managing your Pods easy and stress-free
    • Large performance enhancements using transients and object caching (reducing queries per page load in both dashboard and site to the lowest possible number, sometimes that’s ZERO)
    • New Upgrade wizard screens designed by RD2 will help you upgrade from previous versions and report any potential known issues beforeit actually upgrades your site
      • We’ve partnered with Automattic to offer 1 free month of VaultPress service to users upgrading from Pods 1.x, you will see the offer in the upgrade screens.
      • We’ve also partnered with iThemes to offer 25% off of a BackupBuddy license to users upgrading from Pods 1.x, you will see the offer in the upgrade screens.
    • Add New Pod wizard guides you through creating or extending content types with custom fields
      • Create New Content Types
        • Custom Post Types
        • Custom Taxonomies
        • Advanced Content Types (each type lives in it’s own table, outside of the WP object architecture)
      • Extend Existing Content Types
        • Post Types (Posts, Pages, Existing Custom Post Types)
        • Taxonomies (Categories, Tags, Existing Custom Taxonomies)
        • Media
        • Users
        • Comments
    • Choose to store your data using meta-based storage (default) or custom table-based storage
    • New Field Editor and Field Types
      • New Field Type options built in (no more input helpers for most common input types!)
        • Date / Time – Date, Time, or both
        • Number – Plain Number or Currency
        • Text – Plain Text, Website, Phone, E-mail, or Password
        • Paragraph Text – Plain Paragraph, WYSIWYG (TinyMCE or CLEditor, or add your own), or Code (Syntax Highlighting)
        • Color Picker – Choose colors, because colors are great (Using the default WP color picker, Farbtastic in 3.4)
        • Yes / No – You can’t really go wrong with a checkbox, but we’ve added a few charms to make it stand out
        • File / Image / Video – Upload new media or select from existing ones with our Media Library integration, or use a simple uploader, your choice
        • Relationships – Relate any item, to any item of any WP object type or another Pod, now with improved Bidirectional relationship support
    • New grouping fields API on the Add/Edit forms for Post Types, Taxonomies, Media, Users, and Comments (We’re adding a management UI for this coming in 2.1)
    • New Shortcode popup integration with TinyMCE editor (now provide one-off templates within the shortcode itself)
    • New Widgets (and provide one-off templates within the widget itself)
    • New Form UI front and back
    • New Attachments option available for File Uploads allows you to click “Attach” and select media items from the normal built-in WP Media Library pop-up
    • New Componentsallow additional functionality to be enabled but not loaded if you don’t want/need them
      • Pod Templates
      • Pod Pages
      • Pod Helpers
      • Roles and Capabilities
        • Add / Edit Roles (Administrator, Editor, etc..)
        • Add / Edit Capabilities for each Role
      • Markdown Syntax for Paragraph Text fields
      • Migrate: Import from Custom Post Type UI
        • Import Custom Post Types and Taxonomies created by the Custom Post Type UI plugin
        • Import them all, or choose a few
        • Optionally cleanup the Custom Post Type UI options when done, removing the imported objects from it’s control
    • Basic WPML Integration and confirmed Polylang compatibility
    • Fully Localized interface and error messages! All of our text strings in the plugin now run through the i18n functions. We don’t have any translations yet, but we’re looking at getting GlotPress setup for translators to start getting in.
    • Requires at least WordPress 3.4 and is tested against WordPress 3.4 and 3.5 releases

    Not sure about Pods 2.0 yet? Screenshot time!

     

    • hsatterwhite 2:43 pm on October 6, 2012 Permalink | Log in to Reply

      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.

      • sc0ttkclark 2:34 pm on October 8, 2012 Permalink | Log in to Reply

        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!

  • sc0ttkclark 3:23 pm on August 9, 2012 Permalink
    Tags: , cost, ohloh   

    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!

    https://www.ohloh.net/p/pods-framework/estimated_cost

     

    • 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.

  • sc0ttkclark 6:33 pm on December 7, 2012 Permalink
    Tags: releases   

    Pods 2.1 is out! 

    Pods 2.1 is now out, go check out all the goodies and see the change log at http://wordpress.org/extend/plugins/pods/changelog/

     

  • sc0ttkclark 3:29 am on September 17, 2012 Permalink
    Tags: , , releases   

    Pods 1.14.4: Bug fixes and tweaks 

    Release Notes

    • 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
     

  • sc0ttkclark 6:35 pm on September 6, 2012 Permalink
    Tags: , , releases   

    Pods 1.14.3: Bug fixes and tweaks 

    Release Notes

    • Added: Reordering a Pod (using pods_ui_manage) now has a new capability check for pods_reorder_pod_podname (Custom WP capability you can add to the user’s role if they don’t have pod_podname access already)
    • Added: New pods_page_precode_X action, where X is the Pod Page URI
    • Fixed: get_field from returning values if an id is not set (no data found)
    • Fixed: Moved wp_editor support into an if/else statement to avoid potential overlaps
    • Fixed: Pods UI pagination and search parameter naming for ‘num’ usage
     

  • sc0ttkclark 7:37 pm on June 8, 2012 Permalink
    Tags: , releases,   

    Pods 1.14.2: Bug fix and Security Reminder 

    Release Notes

    • Security Update Reminder (from 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)
    • Changed: More strictness to the above security update, also setting tighter defaults for security access w/ uploader
     

    • term25 4:27 pm on June 9, 2012 Permalink | Log in to Reply

      I mean is possible in 1.14.2 version to use wp_redirect function call (in post save helper) to redirect user after submitting the public form to another, e.g. thank you page? I mean will this code now work in post save helper for a pod e.g. this code

      • term25 4:29 pm on June 9, 2012 Permalink | Log in to Reply

        the php code is not showing, so I will try once more wp_redirect(‘../thanks’); PLease, merge these 3 replies into one if possible, I wasn’t able to edit my post. There is not such a function available. Just permalink and reply. Thanks.

  • sc0ttkclark 1:55 am on May 31, 2012 Permalink
    Tags: releases,   

    Pods 1.14.1: Bug fixes 

    Release Notes

    • Changed: Uploaded files now uses data-post-id attribute in file row div to avoid issues with IDs, backwards compatibility maintained for old input helpers using IDs
    • Fixed: Uploaded files not showing in form in the order of upload on subsequent edits
    • Fixed: Fixed an issue with adding / editing fields where “Related to” dropdown would not show
     

  • sc0ttkclark 4:17 am on May 21, 2012 Permalink
    Tags: releases,   

    Pods 1.14: New Uploader (plupload) and Bug fixes 

    Release Notes

    • Important Change / Addition: For installations using WordPress 3.3+, we have switched the default uploader to Plupload from SWFUpload due to incompatibilities introduced in WP 3.3.2 that effect all plugins and themes using the styled button. Be sure to update your file upload helpers using our examples at http://podscms.org/packages/file-uploader-input-helpers/
    • Added: edit_where_any option in Pods UI now lets you set (true/false) whether for edit_where to be an ANY or ALL match (default false = ALL)
    • Fixed: Date Input field was throwing a JS error if you used YYYY-mm-dd format without the time included
    • Fixed: parse_url fixes for when path isn’t set (localhost or custom ports usually causes this)
    • Fixed: When there was extra output above or below JSON strings like errors from other plugins, whitespace, or anything else – we now explicitly match the JSON {…} string before using it in JS to avoid confusing errors for the user
    • Fixed: .pods_form style tweaks to help cover themes which display the form incorrectly
    • Fixed: Forcing (int) on getRecordById when is_numeric( $id )
    • Fixed: Resolved incompatibility issues with certain MySQL configurations which were throwing errors when saving a Pod
     

  • sc0ttkclark 10:14 pm on April 5, 2012 Permalink
    Tags: , , releases   

    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
     

  • sc0ttkclark 8:11 pm on February 19, 2012 Permalink
    Tags: , , releases   

    Pods 1.12.3: Bug fix release 

    Release Notes

    • Added: Pods UI findRecords parameters array now goes through a new filter called “pods_ui_findrecords”
    • Fixed: Forcing boolean check if true in bypass_helpers in PodAPI
    • Fixed: Pod Page automatic title generation now removed WP home path (for WP sites in sub-directories); Props @chrisbliss18
    • Fixed: nicEdit JS “A.createRange()||document.createRange()” fix for JS errors on certain browsers / uses
    • Fixed: Pagination page_var usage (was forcing ‘pg’ var name no matter what), and fixed query array handling; Props to @thangaswamyarun for finding this one so we could fix it!
    • Fixed: Pods UI search settings set correctly now (had to flip a true/false check and not have search_across take the bool value of search)
    • Fixed: Pods UI filtering sets emptied values now, wasn’t setting right if you had emptied a filter value when submitting (unselected drop-down)
     

  • sc0ttkclark 1:01 am on December 12, 2011 Permalink
    Tags: , , releases,   

    Pods 1.12: Security Update, Features, Changes, and Bug Fixes 

    Release Notes

    • Important: As with all upgrades, we take them seriously. If you experience any major issues when upgrading to this version from a previous version, immediately contact uhoh@podsframework.org and we’ll help get your upgrade issue figured out (critical bugs only please)
    • Security Update: 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)
    • Added: Multi-level references in field names when referenced in Pod :: findRecords $params (`select, where, groupby, having, orderby`) – ex. `’where’ => ‘pick_field.another_pick_field.another_pick.field = “Example”‘` (donation-funded by @chriscarvache)
    • Added: Multi-level references in search filters when referenced in Pod :: findRecords $params (`select, where, groupby, having, orderby`) or Pod :: traverse variable (when not mentioned in params but you want it filterable) (donation-funded by @chriscarvache)
    • Added: Lightweight Relationship (PICK) field support in Pod :: findRecords (2.0 full support in UI) (donation-funded by @chriscarvache)
    • Added: Fully revamped JOINs based on field names when referenced in Pod :: findRecords $params (`select, where, groupby, having, orderby`) (donation-funded by @chriscarvache)
    • Added: RegEx auto-sanitizing of field names when referenced in Pod :: findRecords $params (`select, where, groupby, having, orderby`) (donation-funded by @chriscarvache)
    • Added: PodAPI :: duplicate_pod_item with $params as `’datatype’ => ‘podname’, ‘tbl_row_id’ => $item_id_to_duplicate` (returns new id) (donation-funded by @gr0b1)
    • Added: PodAPI :: export_pod_item with $params as `’datatype’ => ‘podname’, ‘tbl_row_id’ => $item_id_to_export` (returns array of data – pick/file columns are arrays of their data) (donation-funded by @gr0b1)
    • Added: PODS_STRICT_MODE constant to enable many features at once which are common settings for advanced developers including – Pagination defaults to off; Search defaults to off; PodAPI $params are auto-sanitized (stripslashes_deep if you already sanitized or are dealing with sanitized values in your $params)
    • Added: Pod(‘pod_name’, $params) ability to run findRecords straight away with one single line that also sets up the Pod object, $params must be an array
    • Added: Option to use SQL_CALC_FOUND_ROWS or COUNT(*) for getting the total rows available (for use with pagination / Pod :: getTotalRows) setting ‘calc_found_rows’ or ‘count_found_rows’ to true in Pod :: findRecords $params (useful for complex queries on data)
    • Added: Option to disable pagination altogether (separate from setting page to 1, but also forces page to be 1) in findRecords $params `’pagination’ => false`
    • Added: PODS_GLOBAL_POD_PAGINATION constant to globally disable pagination by setting the constant to false (can be renabled as needed in findRecords $params `’pagination’ => true`)
    • Added: PODS_GLOBAL_POD_SEARCH constant to globally disable search by setting the constant to false (can be renabled as needed in findRecords $params `’search’ => true`)
    • Added: PODS_GLOBAL_POD_SEARCH_MODE constant to globally set the search_mode to ‘text’, ‘int’, or ‘text_like’ (default ‘int’ which references field IDs) – can be overrided as needed in findRecords $params `’search_mode’ => ‘text’`)
    • Added: PODS_DISABLE_EVAL constant to globally disable PHP eval() on PHP-enabled areas of Pods (Templates, Helpers, Pod Pages)
    • Added: PODS_WP_VERSION_MINIMUM constant to disable WP minimum version requirement
    • Added: PODS_PHP_VERSION_MINIMUM constant to disable PHP minimum version requirement
    • Added: PODS_MYSQL_VERSION_MINIMUM constant to disable MySQL minimum version requirement
    • Added: Pod :: getRowNumber() to get current row number and Pod :: row_number variable to internally be used to keep track of which row_number you’re on in findRecords loop (incremented in fetchRecord)
    • Added: Pod :: raw_sql contains SQL without @ table references replaced and Pod :: sql now should reflect the same query as hits the DB (@ table references replaced)
    • Added: Pod :: getZebra() which uses a switch (Pod :: zebra) that goes from false to true during fetchRecord loops (initial value is false, first fetch switches it to true and reverses each additional fetch)
    • Added: PodAPI :: save_template / save_page / save_helper now allow ‘name’ / ‘uri’ to be renamed on save (only in API, not UI)
    • Added: PodAPI :: save_pod_item now accepts an array for $params->tbl_row_id which will let you save multiple items at a time using the rest of the $params
    • Added: PodAPI :: delete_pod_item now accepts an array for $params->tbl_row_id which will let you delete multiple items at a time
    • Added: Having trouble updating Pods but you know things should be OK (advanced users)? Try adding ?pods_bypass_update=1 to the page URL you’re on to bypass the update
    • Added: Pagination / Filters to pods_shortcode (ex. `

      Please provide either a template or field name

      `)
    • Added: pods_page_templates filter to get $page_templates for use in Pod Page editor, which allows support for Pods built into iThemes Builder coming soon (to select layouts)
    • Added: When using pods_query and setting $error to false, will bypass die on MySQL error
    • Added: When using Pods UI as an admin (manage_options capability), add ‘debug=1′ to the URL to see the currently used SQL query for a manage screen
    • Added: pods_manage now returns $object
    • Added: Sort classes now used to show current sort direction
    • Added: PodAPI :: load_column now accepts ‘name’ and ‘datatype’ (id) parameters for lookup instead of only just ‘id’ of field
    • Added: PodAPI :: load_helper now accepts ‘type’ parameter for lookup instead of only just ‘id’ and ‘name’ of helper
    • Added: New function ‘pods_function_or_file’ that checks if a function or file exists based on a number of locations, used for Helpers / Templates / Pod Pages, filter available called ‘pods_function_or_file’ if you want to customize further
    • Changed: Pod Page Precode now runs on ‘after_setup_theme’ action instead of ‘plugins_loaded’
    • Changed: pods_generate_key / pods_validate_key revamped to work off of wpnonce, though $_SESSION is still used for holding the columns from that form usage
    • Changed: pods_sanitize now sanitizes keys (previously only values)
    • Changed: Now using wp_hash instead of md5 to get the hash of a value
    • Changed: PODS_VERSION_FULL removed and PODS_VERSION now set as real point version (ex. `1.12`), updated all checks for version to use PHP version_compare
    • Changed: input_helper in column options returns only value instead of the actual ‘phpcode’ now during publicForm, which then enables file-based / function-based checks during input_field.php loop
    • Changed: pods_unique_slug to work more efficiently
    • Removed: $this->wpdb from Pod class (just a vestige of the past, now using global $wpdb)
    • Removed: PodAPI / UI References to old Pods Menu functionality
    • Fixed: jQuery Sortable include fix
    • Fixed: WP 3.3 errors fixed in regards to new WP Editor API for TinyMCE (via @azzozz)
    • Fixed: Tightened up uninstall.php and when it can be run to avoid accidental uninstalls (Reminder: When you delete Pods (and other plugins) within WP, you’ll delete the files AND your data as we follow the WP Plugin data standard for uninstalling)
    • Fixed: Pods >> Setup UI updated with lots of fixes when editing Pods / Columns, and Helpers (no more refreshes needed where they may have been needed before)
    • Fixed: PodAPI setting of defaults for $params to avoid isset checks
    • Fixed: PodAPI :: save_column now sets pick-related extra data to empty if not a pick column
    • Fixed: Pod :: getRecordById() now gets all of the same data as findRecords pulls in (pod_id, created, modified)
    • Fixed: pods_url_variable references updated to pods_var
    • Fixed: SQL cleaned up (extra line breaks removed so it’s not as ugly) and standardized to escape field names in SQL references
     

    • vingogly 10:37 pm on August 24, 2011 Permalink | Log in to Reply

      Is it possible to install the Beta to try it without clobbering the Pods I’ve already created? If yes, will I be able to update to the final version from the dashboard?

      • sc0ttkclark 9:41 am on August 25, 2011 Permalink | Log in to Reply

        Pods 1.12 makes no database changes, so you would be fine. And yes, WP is sophisticated in it’s version handling and knows that 1.12-beta-4 is less than 1.12 final.

    • vingogly 10:31 am on August 25, 2011 Permalink | Log in to Reply

      Awesome; thanks!

      • sc0ttkclark 10:54 am on August 25, 2011 Permalink | Log in to Reply

        No problem, enjoy Pods 1.12 and let us know if you have any issues. We wouldn’t want you to have to downgrade ;)

    • vingogly 6:46 pm on August 27, 2011 Permalink | Log in to Reply

      OK, I’m running WordPress 3.21, Pods CMS Framework 1.12-beta-6, and had installed 2.0.2 of the Pod Ratings package last week. Unfortunately, the Pod Ratings package doesn’t seem to be working; the stars don’t show up at all. The location of the stars image file has been edited, and require_wp_user is set to true in both helpers (I’ve also tried it with both set to false). The page with the embedded list of Pods is here:
      http://no-consent.org/book-reviews/
      and here’s the detail page for the Pod:
      http://no-consent.org/bookreview/the-federalist-papers/
      This was working BTW to a point with the old version of Pods/Pod Ratings; the stars would display, but the values weren’t being saved.

    • WallabyKid 10:25 am on September 6, 2011 Permalink | Log in to Reply

      Bug in PodAPI.php — can’t “Add new pod”

      replace if (in_array($column, array(‘id’, ‘order’)))
      WITH if (in_array($column, array(‘id’, ‘order’, ‘return_pod’)))

      replace $set = implode(“‘, ‘”, $set);
      WITH $set = implode(‘, ‘, $set);

      replace $pod_id = pod_query(“INSERT INTO @wp_pod_types ({$columns}) VALUES (‘{$set}’)”, ‘Cannot add new pod’);
      WITH $pod_id = pod_query(“INSERT INTO @wp_pod_types ({$columns}) VALUES ({$set})”, ‘Cannot add new pod’);

    • WallabyKid 10:32 pm on September 6, 2011 Permalink | Log in to Reply

      Thank Scott! I found this while digging into another bug with wp_page pick columns I discovered in Pods1.11 (which persists in RC). Detailed Here
      http://podscms.org/qna/questions/2118/bug-with-wp-page-pick-columns-in-pods1.11

    • eduu 12:25 pm on September 30, 2011 Permalink | Log in to Reply

      I am working on my first Pods project and I had the following problems with Pods 1.12-rc-5

      1. I could not create a new fresh activation of the Pods CMS using 1.12-rc-5. I got a fatal error. I proceeded to activate Pods in 1.11, then I was able to switch to Pods 1.12-rc-5 and imported previous code that worked fine in 1.11.

      2. The following errors occurred in 1.12 that did not in 1.11:

      a. I got a syntax error in findRecords when the first parameter was ‘name ASC ‘. It worked fine if the first parameter is changed to ‘name ASC’. It did not like the extra space at the end.

      b. I got an unknown column error in findRecords when the first parameter was ‘modified ASC’, where ‘modified’ is the predefined modified date.

      Thanks

      • sc0ttkclark 2:20 pm on October 2, 2011 Permalink | Log in to Reply

        Good finds, I knew of the #1, it had to do with line endings and is fixed already for RC 6, as for #2 I’ll look into it and fix them. Thanks for reporting!

      • sc0ttkclark 2:26 pm on October 2, 2011 Permalink | Log in to Reply

        #2b: When referencing modified, you need to prefix it with a p., so you end up with ‘p.modified ASC’

        Also, just MySQL shorthand – you don’t have to include ASC specifically as that’s what sorting MySQL defaults to.

      • sc0ttkclark 2:54 pm on October 2, 2011 Permalink | Log in to Reply

        Do you have the exact syntax error you were getting for #2a? Trying to reproduce but am having problems getting the error.

        • eduu 8:19 pm on October 2, 2011 Permalink | Log in to Reply

          If I change in RC 5 the first parameter to ‘p.modified ASC’ or plain ‘modified’ as you suggested and it works fine.

          If I use ‘modified ASC’ the MySQL generated tries to attach a t in front of modified getting the error: … ORDER BY `t`.`modified` ASC; Response: Unknown column ‘t.modified’ in ‘order clause.

          Thanks.

          • sc0ttkclark 11:20 pm on October 2, 2011 Permalink | Log in to Reply

            Oh now I see, I just now patched it in Pods 1.12 RC 6, but you’ll want to wait about an hour until the ZIP on wp.org refreshes. That should #2a..

            but for #2b, that’s part of the functionality, if you don’t put in p. it will assume it’s a reference to the current column and prefix it with t. to avoid other potential database errors in other cases.

    • eduu 1:24 pm on October 3, 2011 Permalink | Log in to Reply

      There seem to be a conflict between sort and filters in Pods UI in RC6. If I add ‘filters’=> array(‘state’,'region’), where ‘state’ and ‘region’ are pick columns, to the definition, it works fine.

      But if then I add ‘sort’ => ‘region.name’, it will filter fine the region but the state filtering gets ignored completely.

    • hexdump 8:09 am on October 4, 2011 Permalink | Log in to Reply

      Sorry if this is not the place to ask this, but I’m a bit messed up with version numbres. I see people talking about 1.9X in the forums, and now I see a release with 1.12 RC7 numbering, but 2.0 is due to october :S. Am I missing something?

      • hexdump 5:09 am on October 5, 2011 Permalink | Log in to Reply

        Ok, I missed the subversion in the version numbers. It was 1.9.X so, 1.12 is a newer one :D . Just sleepy.
        Just another question, I have seen there’s a release date for 2.0 for sept/oct. Is this still valid? Or the release date is not set?. I’m just asking because we’re starting a new project this week and we’re thinking on using pods 2.0 (Posts integration is a must for us) but don’t know if we could wait for the release or use another CMS.

        • sc0ttkclark 2:20 pm on October 12, 2011 Permalink | Log in to Reply

          We’re working really hard on releasing Pods 2.0 alpha in October, so yes that’s still the plan.

          • hexdump 3:20 am on October 13, 2011 Permalink | Log in to Reply

            This are really good news. I really apreciate all your hard work (all the team) and I’m really forward to having it in my hands :D .

    • seafae 6:55 pm on November 2, 2011 Permalink | Log in to Reply

      Hi, I’m using Pods 1.12 RC 6 with WP 3.3 beta 2.
      With a paragraph input text field I get “Fatal error: Call to a member function editor() on a non-object in /var/www/vhosts/gicare.com/httpdocs/wp-content/plugins/pods/ui/input_fields.php on line 156″

    • philm 11:08 am on November 3, 2011 Permalink | Log in to Reply

      Hi there,
      Is it hard to split edit and add in roles?
      I think it might be really helpful to assign some users the right to add only and not to edit pods.

    • magi182 2:25 am on December 13, 2011 Permalink | Log in to Reply

      Looked through RC7: checked basic functionality, the public form stuff, but didn’t have time to go through the API improvements yet. One thing I noticed when adding or editing pods, if a Paragraph Text (desc) field is left on the HTML tab when clicking “Save Changes”, the field contents are not saved. However, if you switch to the “Visual” tab before hitting the save button, the contents are saved correctly.

    • mobragauk 9:27 am on December 13, 2011 Permalink | Log in to Reply

      Hi guys,
      I’ve updated PODS CMS plugin to 1.12.1. Automatic installation succeeded without errors. I went to PODS Setup to create a new pod and got the following error:
      Cannot add new pod; SQL: INSERT INTO wp_pod_types(`name`,`label`,`is_toplevel`,`detail_page`, `pre_save_helpers`,`pre_drop_helpsers`,`post_save_helpers`,’post_drop_helpers`,`_REPEATED`) VALUES (‘speakers,”,”,”,”,”,”,”,’1′); Response: Unknown column ‘_REPEATED’ in ‘field list’
      Could you please help me fix the problem?
      Thanks.
      Mo

      • mobragauk 9:32 am on December 13, 2011 Permalink | Log in to Reply

        Don’t worry about the typos in the SQL command above (helpsers instead of helpers, missing closing quote after speakers, and what else). I had to re-type since the dialog box wasn’t editable. The actual crux of the issue is the _REPEATED column that is missing.

      • mobragauk 11:50 am on December 13, 2011 Permalink | Log in to Reply

        Gotcha! That’s being caused by the Dagon Designer Form Mailer plugin. Once that plugin is deactivated, pod creation (and update) works OK.

        • sc0ttkclark 11:43 pm on December 14, 2011 Permalink | Log in to Reply

          Yeah, looks like Dagon Designer is polluting $_POST with their extra field. You should try contacting the dev and have them try to clean up it’s use.

    • hacksey 5:49 pm on December 16, 2011 Permalink | Log in to Reply

      Hi, i have updated to 1.12.2 / 3.3. The auto_set_current_user input helper stopped working and all my get_field (‘author.display_name’) outputs disappeared. Maybe it helps.

    • hacksey 8:21 am on December 19, 2011 Permalink | Log in to Reply

      I’m on localhost only, but i also tested this with a clean WP 3.3 Installation. After WP i added Pods 1.12.2, imported the “Auto Set Current User” helper from the pods website, created a test pod with an ‘editor’ column (pick wp_user) and added the input_helper. Than i tried to add an item to my test pod , but even in backend the helper did not work.

← Older posts

Wordpress Cloud Hosting