Author 詩語

Common Questions Regarding Notifications

How many notifications can I have?Can I copy a notification to other forms?Can I have one notification for all forms?Why am I not receiving form notification e-mails?

How many notifications can I have?
We don』t have any built-in limitation on the number of notifications you can have. By default, there should be an automatic Admin notification on each form created, and many people will create a User notification to send the data to the people that submit the form as well.
Through the use of conditional logic, you can set-up different notifications to run depending on what a user selects on the form.
Can I copy a notification to other forms?
Not currently, no. You can create the same notification on multiple forms, but you have to do this manually.
Can I have one notification for all forms?
Our notification system works on a per form basis. Currently, you cannot control all of the form notifications from one created notification. You will have to edit the notification on each form.
Why am I not receiving form notification e-mails?
There are many potential reasons you might not receive form notification e-mails. The best way to troubleshoot this issue is to go through the following troubleshooting steps: Troubleshooting Notifications

Pipe Change Log

1.3 | 2020-09-281.2 | 2020-04-271.1 | 2018-04-051.0 | 2017-08-08

1.3 | 2020-09-28

Added support for Gravity Forms 2.5.

1.2 | 2020-04-27

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated Javascript files, stylesheets to use minified versions.
Updated link to Pipe account settings page.

1.1 | 2018-04-05

Add GPL to plugin header.
Add security enhancements.
Add support for audio only embeds.
Fix incorrect URL of recorded videos.
Fix JSON string displaying instead of video URL when using {all_fields}.
Updated Plugin URI and Author URI to use https.

1.0 | 2017-08-08

It's all new!

Paragraph Text Field CSS Selectors

example: standard paragraph field (textarea) – applies to all forms
body .gform_wrapper .gform_body .gform_fields .gfield textarea {border: 1px solid red}

example: standard paragraph field (textarea) – applies just to form ID #1
body #gform_wrapper_1 .gform_body .gform_fields .gfield textarea {border: 1px solid red}

example: standard paragraph field (textarea) – applies just to specific paragraph field (based on the unique parent element ID – replace 「XX_X」 with your actual element ID)
body .gform_wrapper .gform_body .gform_fields #field_XX_X.gfield textarea {border: 1px solid red}

PayPal Service Upgrade

PayPal StandardPayPal Payments Pro & PayPal Pro

This alert relates to a change made by Paypal in 2017
PayPal have announced that in an effort to strengthen security they are upgrading their SSL certificates to SHA-256. They are performing a staged rollout across all their web and API endpoints.
As this is a server/SSL certificate issue, the Gravity Forms PayPal Add-Ons do not require any changes; however, we will be releasing updates which will alert you if your server does not support the newer SHA-256 standard.
PayPal isn』t alone in making this change; many organizations are upgrading their SSL certificates to the newer SHA-256 standard. For this reason most hosts should have already begun upgrading their servers to support this new standard. You may want to contact your hosting provider to check if the server hosting your site supports SHA-256.
If your site has an SSL certificate you should also check if it needs upgrading to SHA-256. You can do this by using the SHAChecker tool.
See more from Paypal regarding security here.
PayPal Standard
The endpoint used by the PayPal IPN service is due to be upgraded anytime between September 9-30, 2015. You may have already received an email from PayPal with the subject 『IMMEDIATE ATTENTION REQUIRED』 notifying you about the certificate upgrade for www.paypal.com to SHA-256.
If the server hosting your site does not currently support SHA-256, your customers will still be able to make payments using the add-on; however, the PayPal IPN will not be able to update the entry payment status or transaction details on your site.
Note: When using the PayPal Standard Add-On you don』t need an SSL certificate.
PayPal Payments Pro & PayPal Pro
The SHA-256 upgrade for the endpoint used by the PayPal Payments Pro Add-On is currently planned for October 7, 2015.
The upgrade of the endpoint used by the PayPal Pro Add-On is currently planned for Q2, 2016.
To use either of these add-ons your site should have an SSL certificate.
If your certificate is not using the newer standard or the server hosting your site is not compatible with SHA-256 then once PayPal has made this change you may find that the credit card field will return a validation error when submitting the form.

Obtaining Prior Versions of Gravity Forms

Warning: We do not recommend downgrading Gravity Forms or a Gravity Forms Add-On to a prior version.

If you are experiencing an issue with a recent update, the recommended solution is to restore to your last good backup. This is the best guarantee to recover your previous state, instead of trying to rollback to a prior version of Gravity Forms which can create interworking issues with already upgraded database tables, third party add-ons etc.

Commonly, issues you may be experiencing after an update can be due to a conflict with a theme or plugin, or may already have been corrected with a hotfix release. For this reason, opening a ticket with the Support Team to check may be a better initial option than starting a downgrade process.

We always recommend running the most up-to-date version of Gravity Forms and it』s add-ons, to guard against security vulnerabilities, known bugs, and ensuring compatibility with WordPress core. Check out this article for more on the importance of staying up to date.

If you do need access to a prior version of Gravity Forms for testing or other purposes, please identify what you need and why in your Support request so we can review your issue. Note that providing access to previous versions is not guaranteed, and will be evaluated by the Support team on a case-by-case basis.

Polls Change Log

3.9 | 2021-09-083.8 | 2021-04-293.7 | 2020-10-153.6 | 2020-09-303.5 | 2020-05-133.4 | 2019-08-073.3 | 2019-06-133.2 | 2019-03-223.1 | 2016-08-313.0 | 2016-04-142.4 | 2015-10-082.3 | 2015-04-202.2 | 2014-10-162.1 | 2014-09-242.0 | 2014-02-281.5 | 2013-06-061.4 | 2013-04-301.3 | 2013-04-231.21.1 | 2012-10-03

3.9 | 2021-09-08

Fixed an issue where the polls blocks enqueue breaks the Gutenberg editor in WordPress 5.8.x and later.
Fixed an issue where the polls shortcode renders the form even when it is not active.
Fixed markup errors when poll choices are randomized in Gravity Forms 2.5.

3.8 | 2021-04-29

Added an icon for the form editor in Gravity Forms 2.5.
Fixed an issue where script tags are being output above the document head element.
Fixed an issue where the polls editor block generates error notices in the browser.
Fixed compatibility issues with PHP 8.

3.7 | 2020-10-15

Added security enhancements.

3.6 | 2020-09-30

Added support for Gravity Forms 2.5.
Fixed an issue where the label tag is corrupt when using Jetsloth image choices and enabling shuffle choices setting.

3.5 | 2020-05-13

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Updated Javascript files, stylesheets to use minified versions.
Fixed PHP notices which occur on the entry detail page with PHP 7.4.
Fixed a PHP notice which can occur when a third-party add-on triggers the gform_entry_field_value filter without passing a field object.
Fixed a compatibility issue with the Poll block and WPGraphQL Gutenberg.

3.4 | 2019-08-07

Added security enhancements.

3.3 | 2019-06-13

Added Poll block.
Added the gform_polls_results_ajax_response filter, including form specific version, enabling the results Ajax response to be overridden.
Fixed PHP notice after Gravity Form 2.4.7 adding tab capabilities check.

3.2 | 2019-03-22

Fixed deprecation notices under Gravity Forms > 2.3.
Fixed strings for translations.
Fixed an issue with the locations the gform_merge_tags hook was being used to include the merge tags.

3.1 | 2016-08-31

Updated field general settings label classes for consistency with GF2.0+.
Fixed an issue with the "other" choice feature on the radio type field when saving the form.
Fixed a layout issue in the form editor when the 'Randomize order of choices' setting is enabled.

3.0 | 2016-04-14

Added support for Gravity Forms 2.0.0.
Added GF_Field_Poll.
Fixed an issue with the AWeber integration.

2.4 | 2015-10-08

Updated minimum Gravity Forms version to 1.9.
Fixed some PHP warnings which could appear when using the polls shortcode action with a form that doesn't have any poll fields.
Fixed an issue with the calculation of results which can lead to inconsistent results being displayed in certain situations on sites with high volume. Props: Antonis Zachopoulos.
Fixed a notice in WP4.3 with Widget constructor deprecation.
Fixed an issue with the placeholder for the select type poll field.
Fixed an issue which caused poll merge tags to be replaced during form render.

2.3 | 2015-04-20

Added Spanish (es_ES) translation.
Added support for rendering polls in admin pages. Requires Gravity Forms 1.9.
Added support for the shortcode builder.
Fixed issue where "Other" choice displayed twice in front-end poll results.
Fixed a low severity security vulnerability.
Fixed defaults for the shortcode builder.
Fixed issue where confirmation text wasn't getting displayed on AJAX forms.

2.2 | 2014-10-16

Added support for Gravity Forms 1.9 form editor drag and drop.
Added function gf_polls to easily get a Poll instance.
Added text domain/path to header.
Updated protected functions to be public.
Updated to have the file class-gf-polls.php and organized code into this file and polls.php.
Updated version to use a variable.
Fixed notices.

2.1 | 2014-09-24

Fixed the field title in the Form Editor.
Fixed a PHP warning when overriding a page redirect with the Poll results.
Fixed an issue with the resending of notifications from the entry detail page where the choice values were being displayed instead of the choice text.
Updated a few text strings so they may be translated.
Updated POT file.
Fixed translation text domain in several instances to be gravityformspolls.

2.0 | 2014-02-28

Added integration with the Campaign Monitor Add-On, MailChimp Add-On, AWeber Add-On, and Zapier Add-On.
Added Add-On Framework integration.
Added support for the poll entries tab in the Contacts Add-On.
Added the gform_polls_percentage_precision hook so the percentages on the front-end results can be rounded to a custom number of decimal digits.
Updated label of some form settings items.
Updated Drop Down Poll field to display the "Select one" option at the top of the list instead of the bottom.
Updated GFPolls::merge_tag_filter() to public static.
Fixed view results link for forms with no entries.
Fixed an issue where poll merge tags would appear in the list of merge tags available during pre-submission.
Fixed Strict notices under PHP 5.4.
Fixed permissions for settings pages.

1.5 | 2013-06-06

Requires Gravity Forms > 1.7.4.2
Added a "Select one" option to the dropdown poll field
Added the gform_polls_cron_schedule filter so the frequency of the cron job can be modified.
Notes: The wp_cron job will take over the calculation of the results if 5 seconds is not long enough at the time of form submission/update.
The default schedule is set to hourly to avoid heavy loads on the server but the frequency can be changed by using the gform_polls_cron_schedule filter.
The format follows the same format required by the WordPress cron_schedules filter
Important: the Polls Add-On must be deactivated and reactivated in order to reschedule the task.
Example usage:
add_filter( 'gform_polls_cron_schedule', 'cron_add_twice_hourly' );
function cron_add_twice_hourly() {
// Adds once weekly to the existing schedules.
$schedule['twicehourly'] = array(
'interval' => 1800, // number of seconds in the interval
'display' => __( 'Twice Hourly' )
);
return $schedule;
}
Changed the calculation of the cookie expiration to take into account the browser's timezone if possible.
Fixed an issue with results not being displayed when double quotes were inside field choices labels.
Fixed an issue with results not being displayed in no conflict mode.
Fixed an issue with poll submissions taking too long or timing out when there are already a large number of entries. When the results calculation takes more than 5 seconds then a cached version of the results will be displayed until the background process has finished calculating the new results.
Fixed issue with repeat voting when the poll shortcode cookie attribute is not used.
Removed some deprecated jQuery calls.

1.4 | 2013-04-30

Added gform_form_pre_results filter so the form object can be manipulated before the results are calculated for the admin results page.
Added gform_polls_form_pre_results so the form object can be manipulated before the results are calculated for the front and and entry detail page.
Fixed poll form settings appearing on the form settings tab.
Fixed poll results not appearing below the confirmation in ajax forms.

1.3 | 2013-04-23

Changed confirmation behavior to ignore a confirmation redirect when "display results" is selected.
Fixed a display issue with confirmation message for multipage and ajax enabled forms.
Fixed display issues in the confirmation when the confirmation is empty.
Fixed issue with boolean form settings in imported forms.
Added form settings tab ready for 1.7.
Added results page.
Updated load_plugin_textdomain() call to be outside the is_admin() block so that front end strings can be translated.
Changed the calculation of the ratio of each choice to use the number of entries for each field rather than the number of entries for the form. This fixes support for conditional logic.
Changed the poll results to display only the submitted poll fields. This fixes support for conditional logic.
Fixed poll results on entry detail.
Removed the "Display Confirmation" form setting. The confirmation will be displayed unless the widget or shortcode overrides.
Fixed css conflict with other add-ons on the preview page.
Added poll settings to the form settings. The widget and shortcode are now only needed for the Results display mode.
Removed poll settings from the widget by default and added gpoll_widget_override filter to display the option to override
Example usage:
add_filter('gpoll_widget_override' , 'gpoll_widget_override');
function gpoll_widget_override($form_ids){
array_push($form_ids, 7, 9);
return $form_ids;
}
Added support for legacy widgets by overriding form settings automatically and providing an option to use the form settings.
Added support for legacy shortcodes by overriding form settings.
Added checksum to shortcodes and widgets to make sure the settings aren't not interfered with.
Changed form selector in the widget to display only the forms with poll fields.
Fixed performance issue in the display_entries_field_value() function.

1.2

Fixed an issue with the display of special characters when random choice order is selected for a field. Fixed randomize choice order support for drop-down input types.
Fixed an issue with the tabindex in the widget.
Changed the way the repeating voting mechanism works to play better with caching plugins. Results are now displayed via ajax if the cookie option is set and the visitor has already voted.
Fixed an issue with multiple instances of the same form on the page.
Fixed an issue displaying checkbox values en entry detail and export.
Fixed an issue in the email notification where Disable Auto-formatting is not selected.

1.1 | 2012-10-03

Fixed an issue where results were being displayed when the cookie is set and display_results=false.
Fixed an issue during the export process.

Mollie Change Log

1.2 | 2021-09-011.1 | 2020-09-161.0 | 2020-05-06

1.2 | 2021-09-01

Fixed an issue that slows down the page load speed when the Mollie add-on is active.
Fixed an issue where payment delayed feeds don't fire correctly if the window is closed before the thank you page renders.
Fixed an issue where a warning appears on the form editor when the add-on fails to communicate with the mollie API.
Fixed an issue when a PHP notice displays if an RTL language is used.

1.1 | 2020-09-16

Added support for Gravity Forms 2.5.
Added accessibility enhancements that announcing the credit card validation error in Mollie Components for screen readers.
Added accessibility enhancements that announcing the supported credit cards.
Fixed an issue that PHP notices were thrown if the Mollie feed didn't have billing fields mapped.

1.0 | 2020-05-06

It's all new!

Managing Forms with WP-CLI

Creating FormsExamplesParametersDeleting FormsExamplesParametersDuplicating FormsExamplesParametersEditing FormsExamplesParametersExporting FormsExamplesParametersListing FormsExamplesParametersGetting FormsExamplesParametersImporting FormsExamplesParametersUpdating FormsExamplesParameters

In this article, we will show you how to do things such as import, export, update, delete, and even create forms using the CLI Add-On for Gravity Forms.
Creating Forms
wp gf form create
Examples

Creates a new form with just a title and description.
wp gf form create 'My Form Title' 'Description Here'

Parameters

Argument
Description