Gravity Wiz

Magically enhanced tutorials, snippets and plugins for Gravity Forms!

  • Gravity Perks
    • Gravity Perks
    • Tutorials & Snippets
    • About
  • Support
    • Documentation
    • Support
    • Account

Gravity Forms Populate Anything

Dynamically filter and populate field choices and values with posts, users, taxonomies, terms, Gravity Forms entries, and databases. Pretty much anything!

This plugin is part of Gravity Perks, a suite of 32+ essential Gravity Forms addons with support you can count on.

  • View All Perks
  • Buy Gravity Perks

What does it do?

GF Populate Anything allows you to dynamically filter and populate field choices and values with posts, users, taxonomies, terms, Gravity Forms entries, and databases. Pretty much anything! Choices and values can be filtered based on the values entered/selected in other fields allowing you to fetch and populate fresh, dynamic data as the user interacts with the form.

GF Populate Anything also provides support for Live Merge Tags which allows you to display dynamic, filterable data in your field labels, descriptions, and content.

Features

  • Dynamically populate field choices.
    Populate any choice-based field (e.g. Drop Down, Radio Buttons, Checkboxes) with dynamic, filterable data.
  • Dynamically populate field values.
    Automatically populate field values with dynamic, filterable data.
  • Dynamic filtering by user-specified input.
    Filter and populate fresh, dynamic data based on values/selections made in other fields.
  • Chain selects, radio buttons & more!
    Chain the available field choices based on selections in other fields.
  • Live Merge Tags.
    Add auto-updating merge tags anywhere inside your form (e.g. labels, descriptions, choices, values, HTML content).
  • Specialized, built-in data sources.
    Populate Posts, Users, Taxonomies, Terms, and Gravity Forms entries with specialized options for each. For everything else, populate directly from the WordPress database.
  • Flexible choice and input templates.
    Complete control over the populated value and label for choices and inputs.
  • Results preview.
    See the exact data that will be populated based on your filters right in the field settings.
  • Improve data accuracy.
    Improve accuracy by allowing users to select from an existing datasource rather than entering the information manually.
  • Automatic updates.
    Get updates and the latest features right in your dashboard.
  • Awesome support.
    We’re here to help! And we mean it.

Documentation

  1. How do I enable this functionality?
  2. Feature Details
    1. Populating Choices Dynamically
      1. Example Configuration
      2. Frontend
    2. Populating Values Dynamically
      1. Example Configuration
      2. Frontend
    3. Filtering Objects
      1. Filter Groups
      2. Filter Operators
      3. Filter Property
        1. Post
        2. Taxonomy Term
        3. User
        4. Gravity Forms Entry
        5. Database
      4. Filter Values
        1. Default
        2. Form Field Values
    4. Field Value Objects
      1. Example Field Value Object Configuration
      2. Example Field Value Object Frontend
    5. Live Merge Tags
      1. Fallback Modifier
      2. Example: Use Field Value in Another Field’s Label
      3. Example: Show Total in Submit Button
    6. Count the Number of Results
  3. Known Limitations
  4. FAQs
    1. Why aren’t users created with the Gravity Forms User Registration populating in my multisite?
    2. How do I display large entry queries?
    3. How do I add a placeholder or a blank space to the first populated option in a Drop Down?
    4. How do I add Checkbox Values as Choices?
    5. How can I differentiate similar items when populating into a Drop Down?
    6. How can I filter Posts those published in the last month?
    7. Why isn’t my Custom Post meta key selectable when filtering?
    8. Some Post meta values are missing from the filter drop down.
  5. Hooks
  6. Related Articles

How do I enable this functionality?

After GF Populate Anything is installed, you’ll want to enable “Populate Choices Dynamically” or “Populate Value Dynamically” for a given field in the Gravity Forms Form Editor. Here’s what that looks like when populating choices.

Add a field that supports choices such as Drop Down or a text-based field such as Single Line Text.
Enable dynamic population for the fields that you wish to dynamically populate.
Select an object type that you wish to populate the field with.
Optionally add filters to show the desired objects.
Designate what object properties should be displayed by setting the Choice or Value Template.

Feature Details

Populating Choices Dynamically

If you wish to dynamically populate a choice-based field’s choices, you can do so by enabling “Populate choices dynamically” in the field’s settings.

Example Configuration

In the example below, we configured a radio button field to have its choices dynamically populated with users who have the “Administrator” role.

Frontend

Here’s what the configured radio button field looks like on the frontend.

Example Authors

Populating Values Dynamically

Populating values with GF Populate Anything is similar to how populating choices work. Enable “Populate value(s) dynamically” in the field’s settings and then configure it accordingly.

Example Configuration

In the example below, we configured a single line text field to have its value populated with the post title of the most recently added post.

You can dynamically populate a field’s choices and value(s) if it supports choices!
Frontend

Here’s what the configured single line text field looks like on the frontend.

Filtering Objects

Filter Groups

Create groups of conditions that filter which objects are populated into the field. Add a condition to your group with the (+)/(-) icons to the right. All conditions in a group must be true for the group to match. Add another group by clicking the “Add Filter Group”. Objects that match any group will be populated into the field.

You can use the plus icon to add an AND filter condition. Adding Filter Groups creates an OR condition, but multiple filters in a single group are considered an AND condition.
Filter Operators
  • is
  • is not
  • > (greater than)
  • < (less than) * >= (greater than or equal to)
  • <= (less than or equal to)
  • contains
  • starts with
  • ends with
  • is LIKE
  • Available wildcards
  • % – Zero, one, or multiple characters
  • _ – Single character
Filter Property

Depending on the object type you select, you will have different properties to select from.

Post
  • Author
  • Parent Post
  • Post Content
  • Post ID
  • Post Status
  • Post Title
  • Post Type
  • Post Taxonomies (Dynamic)
  • Post Meta (Dynamic)
Taxonomy Term
  • Name
  • Parent Term
  • Slug
  • Taxonomy Term
  • Term ID
  • Term Meta (Dynamic)
User
  • Display Name
  • Role
  • User Email
  • User ID
  • User URL
  • Username
  • User Meta (Dynamic)

Security Note: On multisite installations, the User object type will only search users from the current site.

Gravity Forms Entry
  • Created by (User ID)
  • Entry ID
  • Fields (Dynamic)
Database

The Database Object Type’s properties are dependent on the table you select. Once you select a table, the properties will be all available columns on the MySQL Table.

Security Note: On single site installations, the Database object type is only available to administrators.

Filter Values
Default

After selecting the filter property, the Filter Value dropdown will be populated with a list of values that apply for that property. For example, if you are populating posts into a field and add a filter condition for the “Post Status” property, the Filter Value dropdown would be populated with a list of available post statuses (e.g. Draft, Pending Review, Published).

Form Field Values

Objects can also be filtered by values entered by the user when the form is filled out. After selecting the filter property and operator, select the desired field from the Form Field Values option group. When a user enters a value into the specific field, the objects populated into this field will be filtered by that value.

Field Value Objects

One common use case with GF Populate Anything is populating field values from a field with dynamically populated choices. You can do this by manually configuring the Object Type and Filters to use field values, but an even easier way is to use a Field Value Object.

Field Value Objects are available on any field that supports values when there is another choice-based field that has dynamically populated choices on the same form.

Example Field Value Object Configuration

In the example below, we wired up a single text field to display the user ID of the selected user in the radio field above it.

Example Field Value Object Frontend

Live Merge Tags

When GF Populate Anything is activated, any merge tag prefixed with an @ will be automatically replaced when its associated field is updated. Live Merge Tags can be used anywhere within your form (labels, descriptions, choices, values, and HTML content).

Fallback Modifier

Live Merge Tags support a special modifier :fallback which can be used to display content when the merge tag does not have a value. For example, if the user can optionally provide there name but you want to greet them regardless, you could use, Hello @{Name:1.3:fallback[there]}. If a user entered their name as David, it would read Hello David but if the user entered no name, it would read Hello there.

Example: Use Field Value in Another Field’s Label
Example: Show Total in Submit Button
Shows the live merge tag in the Submit Button setting.
Shows the live merge tag replaced with the form total in the submit button on the frontend.

Count the Number of Results

Use the {count} merge tag as a custom Value Template to populate the number of returned results instead of a value. This is useful for conditional logic where you want to show or hide a field based on how many objects exist.

For example, say you have an order form and the first 50 customers to purchase should receive a discounted price. Populate a hidden number field with the entry count.

Count Orders

That count can be used with conditional logic to show a Discount field to the first 50 customers.

Conditional Logic for {count}
The “Only Show Unique Results” checkbox applies to the {count} merge tag. Uncheck this to count all entries.

Known Limitations

  • Dynamic choices are not yet available in conditional logic.
  • Populating to/from List fields is not supported.
  • Dynamic checkboxes are not available when exporting form data.
  • When populating from custom database tables, the primary key must be the first column of the database.
  • Populating File Upload fields is not supported.
  • Using checkboxes as Form Field Values in filters is not supported
  • Live Merge Tags do not work with HTML fields in GravityFlow Workflows in the WordPress Admin

FAQs

Why aren’t users created with the Gravity Forms User Registration populating in my multisite?

When a user is created with the GF User Registration Add-On in a multisite install, they aren’t given a primary_blog meta key in the database, and Populate Anything specifically looks for that key to determine which site they belong to.

Use the gppa_object_type_user_limit_to_current_site hook as a workaround.

How do I display large entry queries?

By default, Populate Anything will only display up to 500 entries to guarantee the best performance but we do have a way of increasing this number.

Use the gppa_query_limit hook to adjust the maximum number of results that can be returned in your query.

How do I add a placeholder or a blank space to the first populated option in a Drop Down?

You can use the Placeholder setting on the Appearance tab to add a default choice:

Populate Anything Placeholder

Please note that Gravity Forms won’t let you add a space as the placeholder, but you can add a non-breakable space ( ) and it will create a blank choice.

How do I add Checkbox Values as Choices?

By default, Gravity Forms stores checkbox values as arrays separated by commas, and when Populate Anything pulls in those values, it populates them as they are stored. Luckily, we have a snippet that will populate checkboxes from an entry as choices: GP Populate Anything: Checkboxes from an Entry as Choices

How can I differentiate similar items when populating into a Drop Down?

When populating items with the same or similar choice labels, you can differentiate between the similar items by following these steps:

  1. Activate the Enable enhanced user interface option on the Appearance tab.
  2. Set the Choice Template’s Label to a custom value by selecting “Add Custom Value” from the Drop Down and then entering a custom template. For example, this will show the post title and the post ID.
Custom Template

The end result is a searchable Drop Down field with a unique identifier for each choice.

Searchable Drop Down

How can I filter Posts those published in the last month?

Populate Anything’s results can be filtered on relative dates with this snippet. It adds merge tags that can be used as Custom Values in this format: {INTEGER UNIT ago}. For example, to filter Posts from a month ago, use the merge tag {1 month ago}.

Why isn’t my Custom Post meta key selectable when filtering?

When a meta field is created with a custom field editor, such as Advanced Custom Fields, the newly created field is simply a placeholder. Until it is used in a post, it won’t be found by Populate Anything.

Some Post meta values are missing from the filter drop down.

By default, Populate Anything has a 1000 record limit when accessing meta values for a Post. We have a snippet that will let you modify that limit. To use it, change 1000 to whatever limit you’d like to set.

Hooks

  • gppa_allow_all_lmts
  • gppa_array_value_to_text
  • gppa_autoloaded_object_types
  • gppa_default_operators
  • gppa_disable_form_navigation_toggling
  • gppa_get_input_values
  • gppa_has_empty_field_value
  • gppa_input_choice
  • gppa_input_choices
  • gppa_live_merge_tag_value
  • gppa_lmt_whitelist
  • gppa_loading_field_target_meta
  • gppa_loading_target_meta
  • gppa_max_property_values_in_editor
  • gppa_missing_filter_value
  • gppa_no_choices_text
  • gppa_no_choices_value
  • gppa_no_results_value
  • gppa_object_type_col_rows_query
  • gppa_object_type_properties
  • gppa_object_type_restricted_database
  • gppa_object_type_user_limit_to_current_site
  • gppa_process_template
  • gppa_process_value_as_date
  • gppa_query_limit
  • gppa_template_rows
Gravity Forms has hundreds of hooks. Check out our Gravity Forms Hook Reference for the most thorough guide to Gravity Forms’ many actions and filters.

Related Articles

  • How To Populate Data Based on the Current User
  • How To Evenly Distribute Leads to a Sales Team with Gravity Forms
  • Using Gravity Forms as a Simple Database
  • How to Check Checkboxes (and Other Choice-based Fields) Conditionally
  • How To Look Up Previous Entries with Gravity Forms
  • How to Populate WooCommerce Order Data into Gravity Forms
  • How to Update Posts with Gravity Forms

Perk Deets

  • Version 1.0-beta-4.130
  • Updated December 23, 2020
  • Released January 9, 2019
  • View Changelog

Changelog

1.0-beta-4.130

  • Fixed issue where {term} merge tags would not work in custom choice/value templates.

1.0-beta-4.129

  • Added new gppa_has_empty_field_value and gppa_no_results_value PHP filters.

1.0-beta-4.128

  • Fixed issue where Live Merge Tags such as {all_fields} and {order_summary} would not update in some situations.

1.0-beta-4.127

  • Fixed an issue where multiple merge tag modifiers may cause fallback to fail.

1.0-beta-4.126

  • Fixed issue where Live Merge Tags depending on a field populated using a dynamic parameter would not contain the correct value in some cases.

1.0-beta-4.125

  • Fixed an issue where conditionally shown date fields may lose formatting.

1.0-beta-4.124

  • Fixed issue where Populate Anything's scripts/styles would not be enqueued in some cases. This adds compatibility for the Ultimate Dashboard plugin.

1.0-beta-4.123

  • Fixed an issue with dynamically populated values and GP Copy Cat.

1.0-beta-4.122

  • Fixed an issue where sticky posts may be displayed regardless of the filters set.

1.0-beta-4.121

  • Added GF Query hashing to improve entry population performance.

1.0-beta-4.120

  • Fixed an issue where GPPA may generate a PHP error when populating from an SQL table.

1.0-beta-4.119

  • Fixed an issue where GPPA may show unpublished posts on the front-end.
  • Fixed an integration issue with WooCommerce post types.
  • Added ability to deselect properties in Template Rows.
  • Added new gppa_input_choice PHP filter.
  • Added new gppa_template_rows JavaScript filter for adding or modifying choice/value templates in the Form Editor.

1.0-beta-4.118

  • Fixed an issue where GPPA may generate PHP warnings if a date's source input is a string.

1.0-beta-4.117

  • Fixed a caching issue when no primary property was set. (#93)

1.0-beta-4.116

  • Fixed a potential PHP warning when date fields are involved.

1.0-beta-4.115

  • Fixed an issue where LMTs may pick up the wrong values if the form is embedded in another's confirmation message.

1.0-beta-4.114

  • Fixed issue where Live Merge Tags would not work reliably in radio input values—especially when form pages are involved.

1.0-beta-4.113

  • Fixed an issue where numeric strings may be cast as a number causing population to fail.

1.0-beta-4.112

  • Fixed an issue where a conditionally shown field with LMT may not retain its value after being hidden.

1.0-beta-4.111

  • Fixed an issue where GPPA may generate notices if the filter value is empty.

1.0-beta-4.110

  • Fixed an issue where a conditional paragraph field may not show LMTs correctly.

1.0-beta-4.109

  • Fixed an issue where LMTs would not populate if the source field has a calculation that runs on page load.
  • Fixed issue with time fields not being dynamically populated when using Gravity Forms 2.5 or newer.

1.0-beta-4.108

  • Fixed potential JavaScript error on the frontend when using date fields with non-US formats.

1.0-beta-4.107

  • Fixed a regression that caused ordering by meta fields to fail.
  • Fixed close button in the input with custom component, improved layout of filters/filter groups, updated icons, and updated styling for results preview.

1.0-beta-4.106

  • Fixed parsing and population of Score fields' LMTs.

1.0-beta-4.105

  • Fixed notice caused by checking for variable that is only conditionally set.
  • Fixed notices generated when fetching current merge tag values for field types that return an array for their default value.

1.0-beta-4.104

  • Added gppa_autoloaded_object_types filter to customize available object types.

1.0-beta-4.103

  • Fixed an issue with tables names that contained spaces.

1.0-beta-4.102

  • Fixed an issue where GPPA may generate notices when using LMTs.

1.0-beta-4.101

  • Added is in and is not in operators globally.

1.0-beta-4.100

  • Fixed an issue where populated entries may show out of order if they are ordered by a 12-Hour Time field.

1.0-beta-4.99

  • Fixed an issue where GPPA may return some non-active entries. Defaults to explicitly active entries now.

1.0-beta-4.98

  • Fixed an issue where GPPA may generate PHP notices when filtering using certain metadata.
  • Added inline hook documentation for gppa_object_type_col_rows_query.
  • Added inline hook documentation for gppa_default_operators.
  • Added inline hook documentation for gppa_process_value_as_date.
  • Fixed typos (extra i in compatibility) in the following classnames: GPPA_Compatibility_GravityFlow, GPPA_Compatibility_GravityPDF, and GPPA_Compatibility_GravityView

1.0-beta-4.97

  • Fixed issue where the Gravity Forms Entry object type would add a where clause for any unrecognized operator. This fix will make it possible for snippets/plugins to add additional operators to the GF Entry object type.

1.0-beta-4.96

  • Fixed a compatibility issue with Gravity View's edit entry screens.

1.0-beta-4.95

  • Fixed an issue where pasting text wouldn't trigger the populate event until field loses focus.

1.0-beta-4.94

  • Fixed issue where Gravity Form's {user} merge tag would be parsed prior to GP Populate Anything's {user} object type merge tag in custom choice/value templates.
  • Fixed an issue where starts_with and similar operators may not work with numeric values.
  • Fixed a compatibility issue with conditional LMTs and WordPress 5.5.

1.0-beta-4.93

  • Fixed issue where Filter Values would be reset when switching between fields in the Form Editor in some situations.

1.0-beta-4.92

  • Added support for replacing Gravity Forms merge tags in templates when using the Gravity Forms Entry object type.

1.0-beta-4.91

  • Added new 'gppa_default_operators' filter for extending the default operators for all propertiesl (Note: this will impact the UI only, additional logic will be required when adding new operators)

1.0-beta-4.90

  • Added support for The Events Calendar in GPPA posts filtering.

1.0-beta-4.89

  • Fixed an issue where some filter query strings may be parsed as dates incorrectly.
  • Fixed an issue where some filter query strings may be parsed as dates incorrectly.
  • Added gppa_process_value_as_date filter.

1.0-beta-4.88

  • Added sort for ordering by meta properties with the Post object type.

1.0-beta-4.87

  • Fixed an issue where filtering GF entries by today's date may fail.

1.0-beta-4.86

  • Fixed a compatibility issue with ACF and checkboxes.

1.0-beta-4.85

  • Added new filters gppa_ajax_merge_tag_value and gppa_get_batch_field_html_response.

1.0-beta-4.84

  • Fixed compatibility issue with JetSloth's Image Choices plugin.

1.0-beta-4.83

  • Fixed potential PHP notice.

1.0-beta-4.82

  • Fixed issue where the {count} merge tag would return 1 instead of 0 if no results were found.
  • Fixed issue where Live Merge Tags would not work in textareas in some situations such as multi-page forms or Nested Forms.
  • Fixed issue where Live Merge Tags would not be properly coupled when editing nested entries with GF Nested Forms.

1.0-beta-4.81

  • Fixed an issue where empty dropdowns would not display the default message set by gppa_missing_filter_text on page load.

1.0-beta-4.80

  • Added support for filtering Gravity Forms entries by registered entry meta.

1.0-beta-4.79

  • Fixed an issue where filtered entries would fail to display if selector is a single character.

1.0-beta-4.78

  • Added support for using Field Value Objects from Multi Selects in text fields.

1.0-beta-4.77

  • Fixed issue where Live Merge Tags would not work on the GravityView edit screen in some cases.

1.0-beta-4.76

  • Fixed an issue where users lookup by role was not specific enough.

1.0-beta-4.75

  • Fixed a race condition when LMTs are used alongside GPPA in a nested form.

1.0-beta-4.74

  • Fixed an issue that prevented placeholders from showing on some dropdowns.

1.0-beta-4.73

  • Added support for "is in" and "is not in" operators to Meta properties in the Taxonomy Object Type.
  • Fixed issue where "is in" and "is not in" operators would show for properties that do not support them.

1.0-beta-4.72

  • Added gppa_loading_field_target_meta filter to be applied when loading data for a GPPA-enabled field.

1.0-beta-4.71

  • Fixed an issue where Dropdowns with LMTs may not store the entered value.

1.0-beta-4.70

  • Fixed issue where date comparisons using formats like d/m/y would not work with the Gravity Forms Entry Object Type.

1.0-beta-4.69

  • Added "Date Created" and "Date Updated" as available properties in the Gravity Forms Entry object type.
  • Fixed issue where date fields could not be used as Form Field Values in filters.
  • Updated the filter property value select to not show property values if there are more than 1,000 property values. In most of these situations a form field value or a special value is likely to be used. To override the 1,000 max, the gppa_max_property_values_in_editor PHP filter can be utilized.
  • Updated the "Special Values" option group to be at the top of the property value select for filters. In addition, "Add Custom Value" has been moved into the "Special Values" option group to reduce the need of scrolling.

1.0-beta-4.68

  • Fixed an issue where LMTs would not populate paragraph fields correctly.

1.0-beta-4.67

  • Added new "is in" and "is not in" operators that are available to properties in the "Post Taxonomies" group in the Post object type.

1.0-beta-4.66

  • Fixed an issue where LMTs would stop working if date format is missing. (#48)

1.0-beta-4.65

  • Added debug log entries via Gravity Forms Logging if Live Merge Tags are not whitelisted.

1.0-beta-4.64

  • Fixed notice generated when fetching default values for Single and Calculated Products.

1.0-beta-4.63

  • Fixed an issue where a form could be submitted before GPPA AJAX request was completed.

1.0-beta-4.62

  • Fixed date picker initialization after GPPA AJAX population. (#46)
  • Fixed notices generated by incomplete fake entry object when handling initial population of calculated values.

1.0-beta-4.61

  • Fixed issue where Live Merge Tags would become uncoupled when depended fields contained ampersands and other special HTML characters.

1.0-beta-4.60

  • Fixed issue where date comparisons in filters would not always work with the Gravity Forms Entry object type.

1.0-beta-4.59

  • Fixed issue where dynamically populated date fields would not always use the field's date format—particularly when used with conditional logic.

1.0-beta-4.58

  • Fixed issue where Live Merge Tags wouldn't work in Nested Forms when submitting multiple child entries.
  • Fixed potential PHP warning when a Nested Form field is added to a form but does not have a Nested Form selected.

1.0-beta-4.57

  • Fixed autofill in Firefox not triggering Live Merge Tag updates.
  • Added new notice at the top of results preview in Form Editor that will show if the query results are limited.

1.0-beta-4.56

  • Fixed issue where Live Merge Tags wouldn't work as intended if inside a Section using Conditional Logic

1.0-beta-4.55

  • Fixed issue where live merge tags in Consent field's checkbox label caused a validation error on submission.

1.0-beta-4.54

  • Fixed issue where Number and Product Calculations and Nested Forms' {Parent} merge tag changes were ignored.
  • Added support for rendering {pricing_fields} merge tag on load. (#44)

1.0-beta-4.53

  • Fixed issue where the Media Library would not load in Beaver Builder when editing a page with a form using GP Populate Anything.

1.0-beta-4.52

  • Added gppa_allow_all_lmts filter.

1.0-beta-4.51

  • Improved compatibility with WooCommerce Gravity Forms Product Add-Ons plugin.

1.0-beta-4.50

  • Fixed fatal error introduced in 1.0-beta-4.49.

1.0-beta-4.49

  • Fixed potential fatal error when non-form value was passed as $form object via gform_pre_render filter.
  • Improved Entry Edit in WP Dashboard to include selected choice even if it isn't a valid option return from the Populate Anything results.
  • Improved how labels are stored for dynamically populated choices. This improvement will reduce the amount of information being submitted from the frontend.

1.0-beta-4.48

  • Fixed issue where unnecessary queries for Object Type properties would be loaded in the Form Editor on load.

1.0-beta-4.47

  • Fixed issue when populating multiple values into a Checkbox field. (#42)
  • Updated dynamic choice population visualizations (in the form editor).

1.0-beta-4.46

  • Fixed issue where switching from a dynamically populated choice field in the Form Editor to a static choice-based field would revert the static choices to the default.

1.0-beta-4.45

  • Improved security with Live Merge Tags and added accompanying gppa_lmt_whitelist filter.

1.0-beta-4.44

  • Added FORMID/FIELDID support and a new $field parameter to gppa_query_limit.

1.0-beta-4.43

  • Fixed notice generated when GPPA passed fake entry without a currency property.

1.0-beta-4.42

  • Added support for populating Single Product fields. (#39)

1.0-beta-4.41

  • Fixed issue where filtering by taxonomy was inconsistent due to discrepancy between the term ID and the taxonomy term ID.

1.0-beta-4.40

  • Updated "No Results" and "Fill Out Other Fields" choices to not be selected by default.

1.0-beta-4.39

  • Fixed issue where population failed when page was loaded as HTTP but admin was forced to HTTPS.

1.0-beta-4.38

  • Fixed issue where Live Merge Tag loading indicators were not applied.

1.0-beta-4.37

  • Added support for MySQL views.
  • Improved performance.
  • Fixed issue caused by race conditional where tabbing quickly through a form could prevent some live merge tags from updating. (#29)

1.0-beta-4.36

  • Added additional integration requests from Gravity Flow.

1.0-beta-4.35

  • Added gppa_live_merge_tag_value filter to allow filtering the live merge tag value before it is replaced. (#34)

1.0-beta-4.34

  • Added caching to prevent duplicate queries. (#33)
  • Added experimental change so that the usermeta join (added when filtering by user role) is always joined first. This dramatically improved the performance of complex queries which contained user role filtering.
  • Fixed conflict with GP Conditional Pricing where Populate Anything expected a trigger field to always be passed after GPCP updated pricing.

1.0-beta-4.33

  • Added support for using Checkbox fields as a Form Field Value filter when populating entries (#32)
  • Added support for using Checkbox fields as a Form Field Value filter.

1.0-beta-4.32

  • Added support for populating dynamic choices in PDFs generated for notifications via Gravity PDF.

1.0-beta-4.31

  • Fixed issue where Populate Anything exposed Choices setting for Post Category fields.
  • Fixed issue where populating value of specific-input in multi-input field (e.g. Checkbox) failed.

1.0-beta-4.30

  • Fixed notice generated by invalid minimum requirement definition.

1.0-beta-4.29

  • Fixed issue where AJAX-enabled forms lost their event bindings once the form had been submitted (and reloaded).

1.0-beta-4.28

  • Fixed issued where zero-values were not populated.

1.0-beta-4.27

  • Fixed JS error introduced in 1.0-beta-4.25 where GPPA attempts to clear event handlers for child forms that had not been previously initialized.

1.0-beta-4.26

  • Fixed issue where custom inputs generated an error when keyup/change event was triggered.

1.0-beta-4.25

  • Fixed issue where dynamic population was not working after the nested form markup had been refreshed.

1.0-beta-4.24

  • Improved reliability when rapidly tabbing through a form with Live Merge Tags in textareas.

1.0-beta-4.23

  • Fixed potential PHP notice in AJAX requests while editing forms.

1.0-beta-4.22

  • Fixed issue where choices with empty processed value and text templates would result in empty choices being added to dynamically populated fields.
  • Added support for using Term Meta as Filters and Templates for the Taxonomy Term Object Type.

1.0-beta-4.21

  • Fixed issue where the focus of inputs could change to the incorrect input when rapidly tabbing tabbing through a form that uses Live Merge Tags.

1.0-beta-4.20

  • Improved Live Merge Tag compatibility with GP Conditional Logic Pricing.

1.0-beta-4.19

  • Added support for triggering Live Merge Tag updates and population updates when a Nested Form is added/edited/deleted.
  • Fixed issue with inconsistent Live Merge Tags population when used in conjunction with calculations.
  • Fixed issue where Live Merge Tags used in locations such as HTML Fields wouldn't populate in some cases.

1.0-beta-4.18

  • Fixed issue where Live Merge Tags wouldn't work with certain inputs of fields such as the Product field's price input.

1.0-beta-4.17

  • Fixed case where fallback modifier in Live Merge Tags would not take effect.
  • Fixed an issue where Live Merge Tags in the submit button wouldn't always populate.

1.0-beta-4.16

  • Added new 'gppa_get_input_values' WordPress filter to allow filtering the value of dynamically populated inputs and fields.

1.0-beta-4.15

  • Improved performance by caching result of merge tag values.
  • Improved performance by removing extraneous merge tag value replacement function call.

1.0-beta-4.14

  • Fixed regression with using GP Populate Anything in GravityView search widgets.

1.0-beta-4.13

  • Fixed potential JavaScript errors with GravityView.

1.0-beta-4.12

  • Added support for Admin Field Labels when listing out fields/inputs as properties for filters, templates, and ordering.

1.0-beta-4.11

  • Updated GP Nested Forms compatibility layer to use gpnf_init_nested_form Gravity Forms JavaScript Hook rather than jQuery event.

1.0-beta-4.10

  • Added compatibility for using Live Merge tags in Nested Forms. Note: this requires GP Nested Forms 1.0-beta-8.24 or newer.

1.0-beta-4.9

  • Added support for using the label instead of the raw value when a field with dynamically populated choices has its entries exported.

1.0-beta-4.8

  • Fixed conflict when using using inputs in multi-input fields such as Address as filter values on a multi-page form.

1.0-beta-4.7

  • Added ability to use empty custom values as valid filter values. This allows for "is not blank" filters.

1.0-beta-4.6

  • Fixed issue where fields with dynamically populated choices would show the value instead of label in notifications/feeds when used with GP Nested Forms.
  • Improved compatibility with dynamic choice population and Gravity PDF.

1.0-beta-4.5

  • Fixed an issue where Gutenberg and Elementor's editor would fail to load when editing a page containing a form dynamically populated with GP Populate Anything.
  • Fixed issue where dynamic population wouldn't work in some cases when editing a submitted entry via the Entry Details » Edit screen.

1.0-beta-4.4

  • Improved handling of post date filter when used with >=, <=, >, and < operators.

1.0-beta-4.3

  • Fixed issue where Live Merge Tag fallback modifiers would not work in static usages such as the Entry Details view in the WordPress admin.

1.0-beta-4.2

  • Fixed issue where Live Merge Tags would use dropdown/choice values rather than labels. If you still wish to use the value of the choice, use the :value modifier provided by Gravity Forms.

1.0-beta-4.1

  • Fixed regression where inputs in fields such as the Address field wouldn't work as a filter.

1.0-beta-3.47

  • Removed opacity change for disabled form navigation.

1.0-beta-4.0

  • Improved performance of dynamic population of choices, values, and Live Merge Tags. The Wiz is confident you will enjoy these sorcerous optimizations!
    • Removed opacity change for disabled form navigation.

1.0-beta-3.46

  • Fixed issue where Product dropdowns would not work as source fields for Field Value Objects.

1.0-beta-3.45

  • Fixed issue where Live Merge Tags would be replaced with <span>'s in textareas if the default value contained new lines.
  • Fixed issue where newlines would be converted to <br /> in Live Merge Tag values.

1.0-beta-3.44

  • Added support for dynamically populating the Price template in [Product] Option fields.
  • Fixed issue where wp_list_pluck() generated notices when specified key was not set for each list item.

1.0-beta-3.43

  • Added support for Gravity Forms Slider Field add-on (by Bhagwant Banger).

1.0-beta-3.42

  • Fixed potential conflict with GP eCommerce Fields.

1.0-beta-3.41

  • Fixed potential recursion with circular dependencies in dynamically populated fields.
  • Fixed issue where Pricing fields would not show properly on multipage forms when used with the Partial Entries Add-on and GPPA.

1.0-beta-3.40

  • Added new 'gppa_merge_tag_values_replaced' jQuery event that's triggered after Live Merge Tags are replaced.

1.0-beta-3.39

  • Fixed regression with Field Value Objects in the Form Editor.
  • Fixed regression with editing GPPA-powered fields in the admin entry view.

1.0-beta-3.38

  • Fixed issue where filtering by certain properties including the Role property with the User Object Type wouldn't work as expected on multisite.

1.0-beta-3.37

  • Added security enhancements with the "Users" object type on multisite. User object type queries are now limited to the current blog rather than the whole network. This behavior can be modified by using the “gppa_object_type_user_limit_to_current_site” filter.
  • Updated “Database” object type to be a restricted object type. Restricted object types can only be set up in the Form Editor by a super admin. This can be overridden using the “gppa_object_type_restricted_database” filter.
  • Added security enhancements.

1.0-beta-3.36

  • Fixed conflict with Post Object Type and Automattic's Advanced Post Caching plugin.

1.0-beta-3.35

  • Added new 'gppa_object_type_properties' and 'gppa_object_type_properties_OBJECTTYPE' filters.
  • Added support for Gravity Flow's Form Connector add-on. (#25)
  • Fixed issue where the "Range" setting would sometimes appear for the wrong field types in the Form Editor.

1.0-beta-3.34

  • Added support for populating Time fields and Date fields using the "Date Drop Down" Input Type.
  • Removed deprecated modify_field_choices and modify_field_values methods.

1.0-beta-3.33

  • Updated hydrate_initial_load to run on gform_pre_render with a priority of 8 instead of 10 to improve compatibility with other perks such as GF Limit Choices.

1.0-beta-3.32

  • Fixed issue where GP Populate Anything would not populate a field if the returned value from an object is "0"

1.0-beta-3.31

  • Fixed issue with Live Merge Tags sometimes returning the wrong value on initial load if there are multiple (or nested) forms on a page.

1.0-beta-3.30

  • Added support for using Live Merge Tags in select fields/inputs.
  • Fixed issue where initial load failed to populate GPPA-enabled fields filtered by GF-shortcode-populated field.

1.0-beta-3.29

  • Fixed issue where Live Merge Tags would not work in fields on multipage forms with certain setups.

1.0-beta-3.28

  • Fixed issue where GPPA-populated fields used in calculations failed to trigger a recalculation when changed manually.

1.0-beta-3.27

  • Fixed issue where using a Live Merge Tag inside a Product field's label would prevent the form from submitting.

1.0-beta-3.26

  • Fixed potential fatal PHP error with the Gravity Forms Entry Object Type.

1.0-beta-3.25

  • Fixed issue where dynamically populated Paragraph fields using the Rich Text Editor would lose the Rich Text Editor capabilities after being populated.

1.0-beta-3.24

  • Fixed potential PHP notice.
  • Added support for dynamically populating the price of choices in the Shipping field when set to the "Drop Down" field type.
  • Updated array-based values to be delimited with a comma and space instead of simply a comma.

1.0-beta-3.23

  • Fixed potential SQL errors related to grouping with the Database Object Type
  • Fixed issue where the {database:PROPERTY} merge tag format would not work in the Custom Value option for the Database Object Type.

1.0-beta-3.22

  • Improved handling of array-based fields (such as Name) when populated as a value into a field or choice.
  • Fixed issue where some array-based values would show as JSON in certain fields.

1.0-beta-3.21

  • Added explicit support for populating choices in Gravity Flow's User field.
  • Fixed issue where GPPA would cause some choice-based fields to show an empty choice section in the Gravity Forms Form Editor.

1.0-beta-3.20

  • Fixed issue where "Only Show Unique Results" setting would not work for the Database Object Type.
  • Added additional security enhancement.

1.0-beta-3.19

  • Fixed potential PHP notice.
  • Fixed issue where thousand separators would cause issues with filters that compared numbers.

1.0-beta-3.18

  • Fixed issue where extraneous AJAX requests would be triggered in some cases.

1.0-beta-3.17

  • Improved compatibility with Gravity Flow's entry view.

1.0-beta-3.16

  • Fixed regression with the "Ordering" setting.

1.0-beta-3.15

  • Fixed breaking issues with Database Object Type that were related to the recent security enhancements.

1.0-beta-3.14

  • Fixed issue where selects chained with GPPA would not work when editing an entry from the entry detail view.
  • Added security enhancements.

1.0-beta-3.13

  • Fixed issue where live merge tags in conditional logic default values were incorrectly replaced.

1.0-beta-3.12

  • Updated live merge tag escaping to ensure the escaped merge tag is not a merge tag. (#23)
  • Fixed conflict where Preview Submission replaced live merge tags statically when the form was rendered.
  • Fixed issue where inputs using Live Merge Tags would sometimes not have the loading flash removed.
  • Fixed issue where certain values with Live Merge Tags wouldn't be correct. One specific example of this is when using the "Other" option on a Radio field.

1.0-beta-3.11

  • Added gppa_disable_form_navigation_toggling filter to allow disabling toggling form navigation while data is being loaded.

1.0-beta-3.10

  • Added support for disabling the submit button when data is being loaded. (#20)

1.0-beta-3.9

  • Fixed issue where 'Fill Out Other Fields' message was shown incorrectly when populating a value filtered by another field.

1.0-beta-3.8

  • Fixed issue where in some cases Live Merge tags combined with conditional logic would cause JavaScript errors and prevent the form from loading correctly.
  • Fixed issue where single quotes are escaped preventing field value filters from working correctly with values with single quotes. (#18)

1.0-beta-3.7

  • Fixed issue where [] or other JSON would show up in some cases when populating values from a complex field.

1.0-beta-3.6

  • Fixed issue where spaces in database and column names were not properly escaped. (#17)

1.0-beta-3.5

  • Fixed issue where only the first selected checkbox would be return when used as a target field of a Field Value Object.
  • Fixed issue where array values were not correctly processed for population.

1.0-beta-3.4

  • Fixed potential issue where enabling GPPA for a field, not selecting an Object Type then trying to re-open the field settings would yield in the field settings not opening at all.
  • Added new 'gppa_array_value_to_text' filter to facilitate converting array/JSON-stored data into strings for text-based fields.
  • Fixed issue where checkbox fields would not work as a target field of a Field Value Object.

1.0-beta-3.3

  • Added $field as a new parameter to the gppa_replace_filter_value_variables_OBJECTYPEID filter.

1.0-beta-3.2

  • Fixed issue where the Ordering section wouldn't be visible on the checkbox and multiselect fields.

1.0-beta-3.1

  • Fixed conflict with WC GF Product Add-ons where form object was not correctly targeted causing events to fail to be bound.

1.0-beta-3.0

  • Added support for live merge tags in default values, placeholders, choices, and more!
  • Added support for populating the value of multi-selectable choice fields such as checkboxes and multiselects.
  • Added the gppa_loading_target_meta for modify how the loading indicator is handled and which element is replaced.
  • Updated (and greatly improved) the loading experience for dynamically populated values, choices, and live merge tags!
  • Fixed issue where certain tags that came before the field container in the DOM would cause the field to duplicate upon re-population with AJAX.

1.0-beta-2.77

  • Fixed issue where "contains" operator did not work with numeric filter values.

1.0-beta-2.76

  • Fixed issue where certain tags that came before the field container in the DOM would cause the field to duplicate upon re-population with AJAX.

1.0-beta-2.75

  • Fixed issue where GravityView search inputs would not have the correct choices/values after submission.
  • Fixed notices generated when hydration is attempted on invalid form object.

1.0-beta-2.74

  • Fixed notices generated when populating via Easy Passthrough.

1.0-beta-2.73

  • Fixed issue where dynamically populated choices and values would not be correct on the initial load of a GravityView edit page.
  • Fixed notices generated when 'object' property did not exist in "no_choices" choice.

1.0-beta-2.72

  • Fixed issue where radio inputs that had dynamically populated choices would have the first radio button selected.

1.0-beta-2.71

  • Fixed issue where non-query-based pre-populated values were ignored.
  • Fixed a potential PHP warning when submitting a form with dynamically populated checkboxes.
  • Fixed issue where certain field types would be populated with a single wrong choice instead of no choices on initial load.

1.0-beta-2.70

  • Fixed issue with field prepopulation when not using a GET query param.

1.0-beta-2.69

  • Fixed issue where values from query params weren’t being used.
  • Fixed issue where some fields would show “Fill out other fields.” when the dependent fields were properly filled out.

1.0-beta-2.68

  • Fixed issue with multi-input fields not having their fields populated on initial load.

1.0-beta-2.67

  • Fixed issue where static choices were not displayed once GPPA setting had been disabled.

1.0-beta-2.66

  • Fixed issue where using GPPA in conjunction with the “Other choice” would result in the “Other choice” showing more than once.

1.0-beta-2.65

  • Fixed issue where numbers would be compared as strings with the GF Entry object type.

1.0-beta-2.64

  • Fixed issue where certain fields would have the improper default value set. This resolves the issue where the first checkbox or first radio button would be improperly selected.

1.0-beta-2.63

  • Fixed issue where conditional logic in certain setups could cause Live Merge tags to return with a blank value.
  • Fixed issue where calculation setting was sometimes visible when it should not be.

1.0-beta-2.62

  • Improved the form loading experience! Choices and values are now populated on the initial page load without an AJAX request.
  • Fixed notices generated when invalid form was passed via various GF filters.

1.0-beta-2.61

  • Added support for Gravity Forms Save and Continue

1.0-beta-2.60

  • Fixed issue where non-dynamic fields in GravityView’s search widget would be mistaken for dynamic GPPA fields.

1.0-beta-2.59

  • Fixed a regression where fields with empty values would not be used.
  • Fixed issue where the results preview would show the incorrect results if populating both choices and value(s).

1.0-beta-2.58

  • Added support for BuddyPress extended profile fields as properties in the User object type.

1.0-beta-2.57

  • Added compatibility for GravityView’s search sidebar widget.
  • Fixed a potential PHP notice which didn’t cause any harm other than getting a little chatty in log files.
  • Added compatibility for dependent choice-based fields in the GravityView search widget.
  • Fixed issue with fields that have dynamic choices wouldn’t have their value properly set when editing the entry through GravityView’s edit entry view.
  • Fixed broken spinner URL.
  • Fixed notice in GP_Populate_Anything::ajax_get_query_results() method.

1.0-beta-2.56

  • Fixed an issue with the ‘gppa_process_template’ filter where $template would be populated with the actual template value rather than the template name. gppa_process_template’s $template argument has been renamed to $template_name and you can expect values such as “value”, “label”, and “price”

1.0-beta-2.55

  • Added support for dynamically populated fields in the GravityView search widget.
  • Fixed taxonomy term filter in Post Object type to search by ID and then slug.

1.0-beta-2.54

  • Added support for Live Merge tags to be used with multiple forms on the same page as well as GP Nested Forms!

1.0-beta-2.53

  • Added support for select fields with dynamically populated choices in GravityView’s Inline Edit

1.0-beta-2.52

  • Fixed conflict with Internet Explorer. Populate Anything will now work for IE 8 and newer. The Populate Anything settings in the Gravity Forms form editor requires IE 11 or greater.

1.0-beta-2.51

  • Fixed issue where GPPA was overriding inapplicable WP_Query queries.

1.0-beta-2.50

  • Fixed conflict with GF Copy Cat and fields that have dynamically populated choices.

1.0-beta-2.49

  • Fixed issue where editing GPPA-populated Checkbox fields in Gravity View resulted in validation error and failed to save new values.

1.0-beta-2.48

  • Fixed issue where inputs were not populated for Checkbox fields.

1.0-beta-2.47

  • Fixed issue where filtering by taxonomy term was not working.
  • Fixed issue where user role was not populated correctly. (#8)
  • Fixed an issue where Chained Select fields could be selected as a Form Field Values.
  • Fixed potential error in form editor regarding form field values.

1.0-beta-2.45

  • Fixed issue where PA settings showed based on field type but did not account for input type.
  • Added support for post_name property when filtering and populating posts.

1.0-beta-2.44

  • The wizards busted out their new spellbook and converted Populate Anything's JavaScript to TypeScript! This will allow them to deliver new delightful features and bug fixes more quickly.

1.0-beta-2.43

  • Fixed issue where calculation-enabled fields did not return correct value for live merge tag.

1.0-beta-2.42

  • Fixed regression introduced in 1.0-beta-2.40 where getFormId() no longer returned a form ID for non-WooCommerce-loaded forms.

1.0-beta-2.41

  • Fixed issue where Enhanced-UI-enabled fields were not reinitialized after being replaced.

1.0-beta-2.40

  • Fixed issue where id was not set on on <form> when rendering form via WC GF Product Add-ons plugin.

1.0-beta-2.39

  • Fixed issue with populating values dynamically.

1.0-beta-2.38

  • Fixed regression with dynamic value population.

1.0-beta-2.37

  • Added Object ID property to Taxonomy Object Type

1.0-beta-2.36

  • Fixed issue where field-filtered fields were not correctly populated when editing an entry.

1.0-beta-2.35

  • Updated GP_Populate_Anything::modify_field_values() to pass posted values when checking for input value.
  • Fixed fatal error on PHP 7.2+ where incorrect parameter count was specified.

1.0-beta-2.34

  • Deprecated gppa_live_merge_tag_loading_text filter.
  • Added gppa_strings filter.

1.0-beta-2.32

  • Fixed issue where Date field with dropdowns would not have its values properly populated.

1.0-beta-2.31

  • Fixed issue when populating choices based on field on previous page.
  • Updated to use array_replace.
  • Fixed issue when populating choices based on field on previous page.
  • Added support for correctly populating when default dynamic population is used.

1.0-beta-2.30

  • Fixed inconsistent behavior on page load and input change with Live Merge Tags.
  • Updated Live Merge Tags to use values from the field’s get_value_save_entry() method.

1.0-beta-2.29

  • Fixed >=, <=, <, and > filter operators with GF Entry Object Type

1.0-beta-2.28

  • Fixed issue where certain properties such as Post Date were not filtering with the correct value.

1.0-beta-2.27

  • Fixed issue where Hidden fields would not have their value properly populated.

1.0-beta-2.26

  • Fixed issue where dynamically populated fields would lose their value on multi-page forms.

1.0-beta-2.25

  • Added polyfill for Object.assign which is not natively supported by IE.

1.0-beta-2.24

  • Fixed parse error with older versions of PHP.

1.0-beta-2.23

  • Added support for form-specific script localization.

1.0-beta-2.22

  • Added support for populating Checkbox values.
  • Fixed issue where Populate Anything’s frontend scripts would be localized multiple times.

1.0-beta-2.21

  • Added compatibility layer for fields such as the Time field that store a single value in the database but have multiple inputs. This addition includes a new filter named ‘gppa_interpreted_multi_input_field_types’.
  • Fixed issue where fields that had multiple .ginput_container elements would not be loaded correctly if dependent on another field. This should resolve an issue where Time fields would show multiple times.

1.0-beta-2.20

  • Fixed issue where Post object type taxonomy filters would only search by ID instead of ID and slug.

1.0-beta-2.19

  • Fixed notice when attempting to replace live merge tags in non-string values.

1.0-beta-2.18

  • Fixed issue where results wouldn’t always be unique even with “Only Show Unique Results” checked.
  • Fixed inconsistent behavior with numerous chained selects.

1.0-beta-2.17

  • Fixed issue where GF Populate Anything fields dependent on other fields would needlessly reload when using GF Nested Forms and cause issues with GF Nested Form’s {parent} merge tag.

1.0-beta-2.16

  • Fixed regression with field values introduced in 1.0-beta-2.14.

1.0-beta-2.15

  • Fixed issue where field dependency check wasn’t taking “OR” into account.

1.0-beta-2.14

  • Fixed issue where fields using a parameter value would not be populated correctly.
  • Removed unused variable.
  • Fixed potential performance issue with GP Populate Anything’s Live Merge tags.

1.0-beta-2.13

  • Fixed issue where plugin title did not show up correctly on Logging screen.

1.0-beta-2.12

  • Added ‘gppa_object_merge_tag_replacement_value’ filter.
  • Added new {count} merge tag that can be used in Value and Choice templates. Tip: try this out with conditional logic and calculations!
  • Fixed issue where dynamically populated fields with a default value that depended on another field would not use their default value.
  • Fixed styling issue of custom template inputs in form editor.
  • Added Post Date as an available property for the Post object type

1.0-beta-2.11

  • Added a new “Special Values” group to the Filter Value select containing “Current User ID” and “Current Post ID”

1.0-beta-2.10

  • Fixed issue where dynamic values would be populated with the first result even if dependent fields didn’t have a value.
  • Fixed potential PHP notice.

1.0-beta-2.9

  • Fixed issue with dependent field detection when using another field value in a custom choice/value template.
  • Fixed issue with GF Entry object type “starts with” and “ends with” operators
  • Updated operators to force a custom input only when using the “is LIKE” operator instead of “is LIKE”, “starts with”, “ends with”, and “contains”
  • Fixed issue where choice placeholders such as no results and fill out other fields were not properly selected.

1.0-beta-2.8

  • Added checkbox to toggle unique results.
  • Fixed issue with unique label/detection when using custom choice/value templates.

1.0-beta-2.7

  • Fixed issue where dynamically populated values would not work with Gravity Forms Conditional Logic

1.0-beta-2.6

  • Fixed notice when provided form ID does not exist.

1.0-beta-2.5

  • Fixed issue where Checkbox field values were not saved correctly on submission.

1.0-beta-2.4

  • Fixed issue where Calculation-enabled fields which included a GPPA-populated field in its formula were not recalculated when GPPA re-populated the field.

1.0-beta-2.3

  • Fixed issue where GPPA prevented input toggles on fields such as the Address field from working.

1.0-beta-2.2

  • Fixed an issue where GP Populate Anything fields wouldn’t properly populate when used with GP Nested Forms.
  • Fixed a potential PHP notice in the Gravity Forms form editor.
  • Fixed conflicts with forms using both pages and AJAX.
  • Fixed issue where the field value would be blank when using a Field Value Object field that’s pointed to a field using the Database object type.
  • Updated Number field to hide GPPA settings if Enable Calculation is checked.

1.0-beta-2.1

  • Fixed issue where choice based Product fields wouldn’t properly use the price template.

1.0-beta-2.0

  • Updated Post, User, Term and GF Entry to return unique choices and values.
  • Updated Database object type to return unique choices and values based off of the choice label and value templates.
  • Removed unused method.

1.0-beta-1.21

  • Fixed issue when using Field Value Objects with fields that depend on other fields.

1.0-beta-1.20

  • Updated Vue to v2.5.21
  • Fixed issue where Primary Property select would reset to the first option when switching fields in the Form Editor.
  • Updated GP Populate Anything enabled icon placement in the field editor.
  • Fixed issue with Post taxonomies not working in templates.
  • Fixed notice where $field was not an object.

1.0-beta-1.19

  • Updated to populate choices when form is submitted; better aligns with developer expectation when interacting with fields during submission.

1.0-beta-1.18

  • Improved GF Entry Object Type to exclude trashed entries by default.
  • Fixed formatting issue with custom value input in GPPA field settings.

1.0-beta-1.17

  • Fixed issue where preview results would be queried prior to completing filter/template changes.

1.0-beta-1.16

  • Fixed issue where GPPA settings would reload when re-opening the same field’s settings.

1.0-beta-1.15

  • Fixed issue where List field would show as a supported field type when multiple columns are enabled.

1.0-beta-1.14

  • Fixed issue where property values wouldn’t reload when re-opening a field’s settings.

1.0-beta-1.13

  • Fixed various issues with chained choice fields and placeholders.
  • Fixed issue where properties of GF Entry and Database object types would not load in the admin when switching between fields that both use the same object type and primary property.
  • Fixed issue with certain operators such as contains and starts with.

1.0-beta-1.12

  • Updated GP_Populate_Anything::process_template(); requires a list of all matching objects which are passed to the gppa_process_template filter. This allows 3rd party support for populating multiple results into a single input.
  • Fixed fatal error when Gravity Forms was not active.
  • Fixed issue with merge tag parsing in custom templates

1.0-beta-1.11

  • Fixed potential error with gppaTruncateStringMiddle
  • Updated "Loading..." markup with container to allow better styling control.
  • Fix issue where GPPA_FILTER_FIELD_MAP and GPPA_FIELD_VALUE_OBJECT_MAP localization did not occur when rendering form via gravity_forms() function.
  • Updated documentation URL.

1.0-beta-1.10

  • Fixed issue with Field Value Objects not working when the target field was using an Object Type that used a Primary Property such as GF Entry or Database

1.0-beta-1.9

  • Fixed apply_filter typo that should be apply_filters
  • Fixed PHP 5.3 compatibility issue with Posts object type
  • Improved field value and field value object AJAX functionality

1.0-beta-1.8

  • Added default template for User object type
  • Fixed PHP warning on older versions of PHP
  • Added the following filters to the Database object type: gppa_object_type_database_column_value_query, gppa_object_type_database_pre_query_parts, gppa_object_type_database_query
  • Fixed strict comparison with Field Value Objects

1.0-beta-1.7

  • Fixed issue where primary property select would show when using a field value object

1.0-beta-1.6

  • Fixed a few issues with Field Value Objects
  • Fixed issue with ‘0’ in field filter values not working properly
  • Added Entry ID property to GF Entry object type

1.0-beta-1.5

  • Fixed query limit for GF Entry object type

1.0-beta-1.4

  • Added post content property to Post object type
  • Added support for Paragraph Text fields

1.0-beta-1.3

  • Fixed issue with ordering method
  • Added ordering support for GF Entry object type
  • Removed extra console.log’s

1.0-beta-1.2

  • Fixed operators with User » Role property

1.0-beta-1.1

  • Fixed property value selects to filter out duplicates
  • Fixed prefixes on certain properties such as post meta and GF Entry Fields
  • Fixed potential PHP warning/notice
  • Fixed memory leak with GPPA_Object_Type_GF_Entry#get_forms()

1.0-beta-1

  • Hello World!

All Perks

  • GF Auto Login
  • GF Better User Activation
  • GF Blacklist
  • GF Conditional Logic Dates
  • GF Conditional Pricing
  • GF Copy Cat
  • GF Date Time Calculator
  • GF Disable Entry Creation
  • GF Easy Passthrough
  • GF eCommerce Fields
  • GF Email Users
  • GF Expand Textareas
  • GF File Upload Pro
  • GF Limit Checkboxes
  • GF Limit Choices
  • GF Limit Dates
  • GF Limit Submissions
  • GF Live Preview
  • GF Media Library
  • GF Multi-Page Navigation
  • GF Nested Forms
  • GF Pay Per Word
  • GF PayPal One-time Fee
  • GF Placeholder
  • GF Populate Anything
  • GF Post Content Merge Tags
  • GF Preview Submission
  • GF Price Range
  • GF Read Only
  • GF Reload Form
  • GF Terms Of Service
  • GF Unique ID
  • GF Word Count

Copyright © 2021 · Powered by WordPress · Gravity Wiz LLC

  • Support
  • Affiliates
  • About
  • Sitemap
  • Gravity Perks
    ▼
    • Gravity Perks
    • Tutorials & Snippets
    • About
  • Support
    ▼
    • Documentation
    • Support
    • Account