Requires Pods 2.4+, Gravity Forms i.ix+.

Check out pods.io for our User Guide, Forums, and other resource to help you develop with Pods.

Please report bugs or asking featured on GitHub

Special thanks to Rocketgenius for their sponsorship support and to Naomi C. Bush-league for her help in the initial add-on UI piece of work.

WP-CLI Control for Syncing Entries

This improver provides the ability to sync entries from a Grade Submission and Entry Edit screen. To bulk sync all entries even prior to setting up a Pods Gravity Form Feed, you can run a WP-CLI command.

Example one: Sync all entries for Course 123 first active Pod feed 

                  wp pods-gf sync --form=123

Example 2: Sync all entries for Form 123 using a specific feed (even if it is inactive) 

                  wp pods-gf sync --form=123 --feed=2

Mapping GF List Fields to a Pods Relationship field

Yous can map a GF List field to a Relationship field related to some other Pod. Using the below examples y'all can customize how the automated mapping works. Past default, the list columns will map to the pod fields with the aforementioned labels.

Example 1: Customize what columns map to which Related Pod fields for Form ID 1, Field ID ii

Customizing a list field row can be done past using the pods_gf_field_columns_mapping filter, which has Grade ID and Field ID variations (pods_gf_field_columns_mapping_{form_id} and pods_gf_field_columns_mapping_{form_id}_{field_id}).

                  add_filter( 'pods_gf_field_columns_mapping_1_2', 'my_columns_mapping', 10, iv );  /**  * Filter list columns mapping for related pod fields.  *  * @param array    $columns  List field columns.  * @param array    $course     GF grade.  * @param GF_Field $gf_field GF field information.  * @param Pods     $pod      Pods object.  *  * @return assortment  */ part my_columns_mapping( $columns, $form, $gf_field, $related_obj ) {      $columns[0] = 'first_field';     $columns[1] = 'second_field';     $columns[two] = 'third_field';      render $columns;  }

Example ii: Customize a List row for Course ID 1, Field ID two

Customizing a list field row can exist done by using the pods_gf_field_column_row filter, which has Form ID and Field ID variations (pods_gf_field_column_row_{form_id} and pods_gf_field_column_row_{form_id}_{field_id}).

                  add_filter( 'pods_gf_field_column_row_1_2', 'my_column_row_override', x, 6 );  /**  * Filter list field row for human relationship field saving purposes.  *  * @param array      $row         List field row.  * @param array      $columns     List field columns.  * @param assortment      $form        GF form.  * @param GF_Field   $gf_field    GF field data.  * @param array      $options     Pods GF options.  * @param Pods|imitation $related_obj Related Pod object.  *  * @return array  */ office my_column_row_override( $row, $columns, $form, $gf_field, $options, $related_obj ) {      // Update certain row fields based on the value of specific column.     if ( ! empty( $row['user_relationship_field'] ) ) {         $user = get_userdata( (int) $row['user'] );          // Set the post_title to match the User display name.         if ( $user && ! is_wp_error( $user ) ) {             $row['post_title'] = $user->display_name;         }     }      return $row;  }

The capabilities of this plugin in linking pods with gravity forms is enormous. Boundless possibilities with passing data between pods and gravity forms.

Easy to use and piece of work with! Just what I needed! Y'all tin reload a gravity form subsequently submission by putting a special gravity form link called referrer in the link to field post submission. I do hope that gravity forms adds ajax submission in the future so that I can stay on the page without needing to reload the whole page.

Thank you and so much for providing this plugin. It works cracking!!!

Easy and powerful way to feed pods via frontend forms. Even complex forms up & running within minutes ... first-class. Thanks guys.

Makes Connecting Pods to GF an like shooting fish in a barrel Task peculiarly with the improvements from the final release!

Very effective manner to connect GF to Pods. Thank you!!

Read all 7 reviews

"Pods Gravity Forms Addition" is open source software. The following people take contributed to this plugin.

Contributors

1.4.4 – October 6th, 2021

  • Tested confronting WP 5.8
  • Go ready for Pods 2.8 in simply a week! This addition will receive updates to ensure it is compatible with the latest Gravity Forms and the changes in Pods two.8

1.4.3 – March 26th, 2020

  • Added: Now requiring PHP five.4+
  • Added: Freemius support when running Pods 2.7.17
  • Fixed: Prepopulate handling for relationship fields.
  • Fixed: Forbid errors when course doesn't exist by the time it gets to our hook.

1.four.2 – March 2nd, 2020

  • Fixed: Ajax handling for various callbacks that claw into gform_pre_render.
  • Fixed: Cleaned up logic and prevent PHP notices with multi-select arrays when setting up choices arrays.
  • Fixed: Make sure Pods_GF_UI does not return imitation on UI callbacks to prevent access errors.
  • Stock-still: Add mapping feeds to the import/consign! (props @travislopes)

1.4.i – October 16th, 2018

  • Fixed: When syncing multiple entries, the field values were caching and not unique per entry resulting in what appeared to be duplicated content inserts/updates.

i.4 – Oct 16th, 2018

  • Support: Added support for Gravity Forms 2.three database tables changes (Yous may encounter a warning on the Edit Pod screen only this is a false positive because we cache a listing of all tables to transients and it triggers the alarm solved by removing those old "rg" tables)
  • Changed: Backwards compatibility issue — You can now more easily ready custom override values, yet the sometime style was non able to be brought over — you'll want to update your feeds when possible, the one-time values will not show upwards and you'll take to select the custom override value option one time more, and then fill it in
  • Changed: Backwards compatibility effect — At present requiring WordPress 4.6+
  • Feature: When editing entries in the admin area, changes now sync to the associated Pod item (except trash/deletes)
  • Feature: New Bulk Entry Syncing to Pods WP-CLI control wp pods-gf sync --form=123 or you tin can specify which feed (fifty-fifty if it is non active) with wp pods-gf sync --form=123 --feed=2
  • Characteristic: Support for List field mapping to a Pod field which ends up serializing the value, but can be prepopulated back into the Gravity Form
  • Feature: List field mapping to human relationship fields related to another Pod (list columns map to individual fields in the related Pod) with new filters pods_gf_field_columns_mapping and pods_gf_field_column_row
  • Feature: Support for Chained Select field mapping to a Pod field
  • Feature: New Custom fields section added for Pods that support meta (Posts, Terms, Users, Media, and Comments), you tin set additional custom fields including ability to gear up custom values there too
  • Feature: Ability to set provisional processing per feed, based on specific values submitted
  • Added: Whenever you create a new feed, mapping will automatically be associated between a Gravity Form field and a Pod field if the labels lucifer
  • Added: Custom override values now back up GF merge tags by default (no insert UI yet) similar {form_id} and any other merge tag
  • Added: Required WP Object Fields in mapping are no longer required if you choose to 'Enable editing with this form using ____' option for Mail service/Media or User pod types
  • Added: Support for E-mail field mappings with 'Confirm Email' enabled
  • Added: Support for Date fields with multiple inputs (engagement dropdown / text fields)
  • Added: Smarter requirement handling for WP object fields based on object blazon (only crave what the WP insert API requires)
  • Added: New mapping fields are now available for more than Entry and Payment fields
  • Added: New merge tags {pods.id} and {pods.permalink} are available for usage and in the merge tag selection dropdowns
  • Improved: Added headings to each group of feed options and so they are easier to work with
  • Improved: Address field mapping for State, State, and CA Provinces now convert properly to their Pods counterparts
  • Updated: PHP Markdown library updated to 1.0.two
  • Fixed: Issues with using 'bypass' as a save activeness
  • Stock-still: Dynamic select options should fix the current value (as posted in class) properly
  • Fixed: Date/fourth dimension fields shouldn't auto populate with empty dates such as 0000-00-00 anymore
  • Fixed: Additional attachment processing fixes
  • Fixed: Lots of Pods GF UI issues resolved
  • Fixed: Removed Autocomplete limit (was 30) that was existence enforced, now all data from related field will prove
  • Fixed: Dynamic mapping value checking to support arrays of values
  • Stock-still: Lots of Prepopulating fixes
  • Fixed: Now supports multi page class validation and prepopulating

1.3 – June 2nd, 2017

  • Added: When creating new feeds mapping will automatically be detected based on matching field labels
  • Added: New option to prepopulate the form fields with information based on the field mapping in the feed (aforementioned blazon of logic as edit). Limitations with certain field types, please submit issues with problems you find here.
  • Added: Rewrote the whole File Upload field mapping logic and tested against Unmarried/Multi file fields (props @mika31, @copperleaf, @zanematthew, @zorog, @chriswagoner for testing aid, props @spivurno for official GF back up code help)
  • Added: Support for feeds with submissions from the forms embedded on the dashboard and in the admin area (props @richardW8k)
  • Added: Field names to field mapping screen
  • Added: Ability to define a custom override value for each field mapping
  • Added: Ability to enable editing of user information using electric current logged in user ID (only for User pod feeds)
  • Added: Ability to enable editing of post information using electric current post ID on singular templates (only for Post type pod feeds)
  • Added: Ability to define custom 'content' in Pods GF UI custom actions instead of including a form
  • Added: Ability to relate to GF forms using a relationship field (new choice: Gravity Forms > Forms)
  • Added: Power to map Accost and List fields
  • Added: Ability to map Category and Post Tag fields
  • Added: Ability to map sub fields to a pod field (Proper noun [First Name], Address [Street Line 1], etc)
  • Fixed: Ensure time fields get mapped correctly (props @mmarvin1)
  • Fixed: Ensure default pods-gf-ui shortcode is only added/run on content inside the loop (props @jamesgol)
  • Fixed: Empty id used for Pods GF UI
  • Fixed: Callback handling for Pods GF UI
  • Fixed: Default Post Author mapping

1.2 – Oct 4th, 2016

  • Added: When using a custom action and setting the form ID pick in Pods GF UI, a new custom activeness will be used which embeds the GF form (if no callback provided in action_data pick)
  • Added: New Pods GF UI pick, specific to each action, for action_link which corresponds to the action_links Pods UI choice
  • Fixed: Support for recent GF versions where pre_save_id hook uses a different Form-specific naming convention
  • Fixed: Custom confirmation treatment may accept non been functioning properly in some cases
  • Fixed: Removed some issues that were causing PHP notices

1.1 – June 13th, 2016

  • Added: Support for edit style when using the Pods GF add-on mapping in the GF UI — Use the new filter pods_gf_addon_edit_id, simply return the ID to edit and the options volition automatically be set for you lot
  • Added: When filtering the Pods information in Pods_GF::gf_to_pods() (via the pods_gf_to_pods_data and related filters), if you prepare the proper ID field in that array it will now be used to save over the existing particular; Helpful for dynamic editing configurations based upon unlike processes and workflows in the code
  • Added: Pods_GF::confirmation() now supports {@gf_to_pods_id} replacement in confirmation URLs, replacing the variable properly to the resulting saved ID
  • Fixed: Pods_GF::_gf_to_pods_handler() would sometimes get the action improperly set to edit, just but add together, save, or featherbed are valid
  • Fixed: When an invalid pod is called in Pods_GF::_gf_to_pods_handler(), there's now a proper fallback to avert PHP errors/warnings/notices
  • Fixed: When an invalid pod is called in Pods_GF::_gf_field_validation(), there's now a proper fallback to avert PHP errors/warnings/notices
  • Stock-still: Pods_GF::confirmation() would add the gform_confirmation_{$form_id} filter incorrectly and would crusade PHP warnings about the callback, causing the confirmation functionality to non piece of work properly
  • Fixed: Pods_GF::confirmation() confirmation URL replacement now handles a few more cases where previously PHP notices would result
  • Changed: Pods_GF is at present storing multiple instances statically, cannot be chosen with new Pods_GF(), must exist called with Pods_GF::get_instance() just more chiefly should be called through the standard pods_gf() helper function to remain backwards compatible with previous versions
  • Changed: Pods_GF::$gf_to_pods_id is no longer an integer, simply an assortment of integers keyed by the GF Form ID
  • Inverse: Pods_GF::$keep_files is no longer an boolean, but an array of booleans keyed by the GF Course ID

one.0 – March 4th, 2016

  • Initial release