Author 诗语

Where to Put Your Custom CSS

Use the WordPress CustomizerUsing a Third Party PluginModifying style.css

Use the WordPress Customizer
WordPress includes a tool to enable you to tailor the presentation of your theme. Included in that, is a way to add custom CSS code. Do the following:

From your site admin dashboard, click the Appearance option.
Under Appearance, choose Customize.
That will be take you into the theme customizer, where you can find the Additional CSS tool.

Remember, these custom CSS changes are kept with your theme, so will be lost if you change themes.
This external article covers the basics of the customizer, and as always, your can refer to the official WordPress documentation for a detailed list of the options.
Using a Third Party Plugin
There are third party plugins that allow you to add additional styles to your theme without editing the core theme files. They often allow you to target changes to only specific form pages, and it may keep your changes intact, even if you decide to switch themes or your theme provider issues an update.
The Custom CSS & JS Pro plugin by SilkyPress.com is a well established plugin with good supporting documentation. There are also other plugins that do similar things. Try searching our community plugins library or the WordPress plugin directory.
Modifying style.css
If you are comfortable with editing and modifying cascading style sheets (CSS), then you can make custom site wide changes to how your Gravity Forms are displayed by manipulating your theme』s style.css file. We recommended this approach only for users with at least moderate CSS experience, as the interactions and complexity of style sheets can mount up quickly.
The location of the style.css file is not consistent across the many themes available. Often the theme』s style.css file is located in the in the root (or top level) of the theme folder on the web server hosting your site, but theme developers can choose to place them somewhere else within their theme』s folder structure. Check out this article (external site) for some advice on how to locate and access the theme』s CSS file.
Remember: Your first step should always be to back up the CSS file before you modify it!
We cannot really advise where to put your style additions within your style.css file, as their organization varies immensely from theme to theme. If in doubt, or your changes do not seem to be working, review any documentation that accompanies your theme, or contact your theme provider.

Zoho CRM Change Log

2.0 | 2021-10-271.13 | 2021-05-051.12 | 2020-09-231.11 | 2020-07-141.101.9 | 2020-05-141.8 | 2019-08-081.7 | 2019-04-251.6 | 2019-04-151.5 | 2018-03-301.4 | 2017-01-051.3 | 2016-08-311.2 | 2016-02-101.1 | 2015-09-141.0 | 2015-07-30

2.0 | 2021-10-27

Fixed a fatal error that occurs after refreshing authentication tokens with the Zoho API.

1.13 | 2021-05-05

Added a menu icon for Gravity Forms 2.5.
Fixed an issue where the reauthentication notice appears for users who have never authenticated before.
Fixed compatibility issues with PHP 8.
Fixed an issue where authentication may not complete after attempting a connection with Zoho.

1.12 | 2020-09-23

Added support for Gravity Forms 2.5.
Fixed an issue where the add-on would attempt to use deactivated module layouts.

1.11 | 2020-07-14

Added security enhancements.
Fixed an infinite loop which occurred when the record insert error returned by Zoho CRM is missing the api_name.

1.10

Added security enhancements.

1.9 | 2020-05-14

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Added support for the Australia (AU) data center.
Added license key to authorization url.
Added the gform_zohocrm_record filter to modify the record arguments before they are sent to Zoho CRM.
Fixed the width of the Feed Name setting on the feed configuration page.
Fixed an issue where PHP notices thrown after gform_zohocrm_record introduced.
Fixed an issue where PHP notices thrown when the contact or lead has no Email but doesn't allow duplicate in the settings.
Updated a few labels on the settings page related to connecting and disconnecting the add-on with Zoho CRM.

1.8 | 2019-08-08

Added security enhancements.
Added gform_zohocrm_post_create_lead, gform_zohocrm_post_create_contact and gform_zohocrm_post_create_task, to allow custom actions to be performed after creating a lead, contact or task.
Updated Authenticate With options. After switching to OAuth Authentication, remove the other old options.
Updated the feed configuration page to support mapping checkbox (boolean) type Zoho fields.
Fixed an issue when a Zoho account used a non-English language, some module fields couldn't be updated with REST API.
Fixed an issue when Contacts, Leads or Tasks module is missing, REST API couldn't work at all.
Fixed an issue where Blueprints weren't triggered when adding Contacts/Leads in Workflow Mode with v2 API.
Fixed an issue where fields (especially Last Name and Email fields) missing from the feed settings for non-English Zoho accounts users.
Fixed an issue where values mapped to checkbox type Zoho fields would not be passed to the API.
Fixed the "Field cannot be found at Zoho CRM" issue with v2 API.

1.7 | 2019-04-25

Added support for multiple data center when authenticating with v2 API.

1.6 | 2019-04-15

Added supports for Zoho CRM v2 REST API.
Added supports for Approval Process if "Approval Mode" is checked in feed settings, when authenticated with REST API.
Fixed feed settings not saving when selecting a choice containing an ampersand.
Fixed the setting for delaying feed processing until after payment not being added to the PayPal Standard feed configuration page.
Fixed issue when using special characters to create contacts.

1.5 | 2018-03-30

Added security enhancements.
Added logging statements.
Added GPL to plugin header.
Updated Plugin URI and Author URI to use https.
Updated module field map to allow for custom fields to be used.
Updated strings for translations.
Fixed a PHP fatal error which can occur on the feeds page if the Zoho account user does not have permission to access the contacts or leads modules.
Fixed the settings page not showing an error when the maximum number of allowed auth tokens has been exceeded.
Fixed an issue with the response code logging statement.
Fixed an issue with a few strings using the wrong text domain for translations.
Fixed an issue which prevented files being sent to Zoho.
Fixed owner not being set on the created contact/lead.
Fixed an issue retrieving the ID of the created contact from the API response which also caused contact task creation to fail.

1.4 | 2017-01-05

Updated contact, lead and task creation error reporting.
Fixed module fields not importing in certain scenarios.
Fixed strings for translations.

1.3 | 2016-08-31

Added hook to allow API URL to be changed.
Updated not to force standard fields to be required. The required state of the field on the feed will match the required state of the field in the Zoho account.
Fixed issue where checking for duplicate leads did not correctly update duplicate leads.
Fixed an issue where Zoho was unable to parse the XML data if the value contained special characters.
Fixed an issue with the request failed message if a WP_Error occurs.

1.2 | 2016-02-10

Added support for configuring a task description.
Added feed duplication support.
Added support for delaying feed processing until payment by PayPal Standard is successfully completed.
Added some additional logging.
Updated the task due date setting to support merge tags. The merge tag value must be numeric for the due date to be set.
Updated to display an error for the password field on the settings page if Zoho returns a WEB_LOGIN_REQUIRED error.
Fixed an issue with the request failed message if a WP_Error occurs.
Fixed an issue with the text domain for some of the translatable strings.
Fixed an issue with how multiple choices in multi select and checkbox type field values are separated when being sent to Zoho.
Fixed module field choices return "Array" as an option.
Fixed fatal error that occurs during 1.1.5 upgrade routine.
Fixed contacts and leads not being created when Zoho CRM account language is not set to English.
Fixed module field loading to support foreign languages.

1.1 | 2015-09-14

Added authentication option for third party services (Google Apps, Facebook, Yahoo).
Added options to allow for duplicate contacts and feeds.
Added option to manually clear custom fields cache.
Changed custom fields cache from 24 hours to 12 hours.
Fixed an issue where only some of the uploaded files were attached.
Updated available field types for mapping to the contact/lead email.

1.0 | 2015-07-30

It's all new!

What is a Feed?

A feed is like a notification that communicates information to an add-on or to an external service that the add-on integrates with, each time a visitor successfully submits your form.
Whereas a notification will fire an email off to a destination of your choice each time a Gravity Forms submission is completed, a 「feed」 is set-up within an add-on in order to define the way your form will notify the add-on (and potentially an external service) of a submission.
The reason to do this is because you want the external service to do something with it, such as:

send information to a customer management system in order to create a new customer record. E.g. Agile CRM Add-On or ActiveCampaign Add-On.
send information to a payment gateway in order to generate a charge. E.g. Paypal Payments Standard Add-On or 2Checkout Add-On.
send information to a ticketing service to initiate a support request. E.g. Help Scout Add-On.
send information to a communication service to generate a message in that service. E.g. Slack Add-On.
send file information to a storage service. E.g. Dropbox Add-On.

In general when setting up a feed for an external service, you will have to setup the following:

configure an API key or unique identifier that allows the external service to securely identify your submissions as coming from you. This is usually done within the Add-On Settings.
identify the form you want to use to send the information.
map the form fields to the external service fields you want to populate. For example, identifying which phone number field on your form is going to be sent to a CMS service to create a new custom record.
if needed, set any conditional logic you need in order to describe the conditions you want the submission to be sent using your feed. For example, you may only want the customer details to be sent using the 「new customer」 feed when a form field is set to 「new customer」, else you will want to fire the 「update customer」 feed. For information on enabling conditional logic for a feed, please see this article.

For specific instructions on setting up your feeds, refer to the user guide for each add-on.
Note: A feed must be present and active at the time of form submission in order to send information to the external service. Entries created without an active feed will not be sent to the service. Creating a feed afterwards will not process any entries previously submitted.
Tip: If you cannot find an Add-On that supports the specific external service you want to integrate your form with, then try the Zapier Add-On, which is a service expressly designed for providing hundreds of integrations with other services.

WP-CLI Tools

Clearing TransientsExamplesEmptying TrashExamplesParametersVerifying ChecksumsExamplesParametersGetting the System ReportExamplesRunning the database setup

This article includes a few extra commands which are available with the CLI Add-On for Gravity Forms.
Clearing Transients
wp gf tool clear_transients
wp gf tool clear-transients
Clears the Gravity Forms transients.
Examples
123# Successful clearing of the transients.$ wp gf tool clear-transientsSuccess: Gravity Forms transients cleared successfully.
123# Failed clearing of the transients.$ wp gf tool clear_transientsError: There was a problem clearing the Gravity Forms transients.
Emptying Trash
wp gf tool empty_trash
wp gf tool empty-trash
Delete the trashed entries.
Examples
123# Successful deletion of trashed entries for all forms.$ wp gf tool empty-trashSuccess: Trash emptied successfully for all forms.
123# Successful deletion of trashed entries for a specific form.$ wp gf tool empty-trash 2Success: Trash emptied successfully for form ID 2
Parameters

Argument
Description

[]
The ID of the form to delete the entries from. Default: all forms.

Verifying Checksums
wp gf tool verify_checksums
wp gf tool verify-checksums
Verify the Gravity Forms plugin files against the checksums.
Examples
123# Successful verification of the plugin checksums.$ wp gf tool verify-checksumsSuccess: Gravity Forms install verifies against checksums.
1234# Failed checksum verification.$ wp gf tool verify-checksumsWarning: File doesn't exist: css/admin.min.cssError: Gravity Forms install doesn't verify against checksums.
Parameters

Argument
Description

[--version=]
The version number the checksums should be validated against.

Getting the System Report
wp gf tool system_report
wp gf tool system-report
wp gf tool status
Outputs the system report from the Forms > System Status page.
Examples
12345# Successfully using the "system-report" command to output the system report.$ wp gf tool system-reportSuccess:### Gravity Forms ###...
123# Using the "status" alias with an older Gravity Forms version.$ wp gf tool statusError: The system report is only available with Gravity Forms 2.2 or greater.
Running the database setup
See the Managing Gravity Forms and Add-Ons with WP-CLI article.

Where』s that old forum topic?

Gravity Forms Official Help ChannelsAdditional Help ChannelsSome Third Party Gravity Forms ResourcesOther Q&A ChannelsWordPressAdvanced Custom FieldsBuddyPressWooCommerceWPMLCustomizations

In July 2013 we moved from forum based support to a ticket based system, with the forums remaining read-only for reference. Since that time we have released more than dozens updates for Gravity Forms, many new add-ons, and numerous add-on updates.
All these updates do sadly mean that a lot of the information contained in the forums is now extremely dated and, in some cases, can cause more trouble than it』s worth. Also, since the demise of pastie.org many of the code snippets shared in the forums have also been lost.
For these reasons we phased out the forums soon after introducing our customer support ticketing system.
In 2018 though, we did introduce a community hub at the request of our dedicated advocates, our Community Forum. This is not an official support channel, but offers community-to-community conversation with folks who may have solved the problem you are faced with now!
Gravity Forms Official Help Channels

Gravity Forms Support is staffed by our knowledgeable support engineers from around the world, and available to Gravity Forms valid license holders.
Search the Gravity Forms documentation at https://docs.gravityforms.com/
Ask your question on our Community Forum. This is not an official support channel, but offers community-to-community conversation with folks who may have already solved the problem you are faced with now!

Additional Help Channels
These forums and channels are not endorsed or supported by us in any official capacity, but are well established places that may help you on your search.
Some Third Party Gravity Forms Resources

Gravity Wiz for tutorials, code snippets, and add-ons (Gravity Perks)
GravityWP for tutorials, code snippets, add-ons, and add-on reviews
Gravity+ for tutorials and add-ons
Gravity Extend add-on directory and tutorials
The Gravity Forms, GravityView and Gravity Perks Users Facebook Group (unofficial)
The Gravity Forms Development Facebook Group (unofficial)
The Gravity Forms Slack Workspace (unofficial)
Search our library of third party plug-ins, which can be found here

Other Q&A Channels
The following resources are not specific to Gravity Forms but can help with more general topics. Search or ask a question at:

WordPress Development Stack Exchange
Stack Overflow
Quora
WP Help Forum
CSS-Tricks Help Forums

WordPress

Search the WordPress developer documentation at https://developer.wordpress.org/
Search the WordPress support forums or ask a question at https://wordpress.org/support/

Advanced Custom Fields

Search the ACF documentation at https://www.advancedcustomfields.com/resources/
Search the ACF support forums at https://support.advancedcustomfields.com/
The WordPress ACF Users Facebook Group

BuddyPress

Search the BuddyPress documentation at https://codex.buddypress.org/
Search the BuddyPress support forums at https://buddypress.org/support/

WooCommerce

Search the WooCommerce documentation at https://docs.woocommerce.com/
Search the WooCommerce support forums at https://wordpress.org/support/plugin/woocommerce
The Advanced WooCommerce Facebook Group
The WooCommerce Help & Share Facebook Group

WPML

Search the WPML documentation at https://wpml.org/documentation/
Search the WPML forums at https://wpml.org/forums/

Customizations
We are unable to provide customization services as part of our customer support. That is just not what we do. But we have partnered with Codeable to provide Gravity Forms customization services. They can help pair you with a developer based on your needs and budget. You can get started with Codeable here.

Zoho CRM Feed Meta

IntroductionUsagePropertiesContact PropertiesLead PropertiesTask PropertiesCustom Field Properties

Introduction
The Feed Object meta for the Zoho CRM add-on is an associative array containing the properties which determine how the add-on should process the form submission.
12345678$feed['meta'] = array(    'feedName'                                => 'Zoho CRM Feed 1',    'message'                                 => '',    'feed_condition_conditional_logic'        => true,    'feed_condition_conditional_logic_object' => array(        'conditionalLogic' => array(),    ),);
Usage
We recommend accessing the $feed meta using the rgar() or rgars() functions, e.g.:
1$conditional_logic_enabled = rgars( $feed, 'meta/feed_condition_conditional_logic' );

Properties

feedName string
The feed name which appears on the add-ons feeds tab.

action string
The action which will occur when this feed is processed. Possible values: contact or lead.

feed_condition_conditional_logic boolean
Is the feed condition (conditional logic) setting enabled. Default is false.

feed_condition_conditional_logic_object array
An associative array containing the conditional logic rules. See the Conditional Logic Object for more details.

Contact Properties
The following properties are only applicable when the action is set to contact.

contactStandardFields_Email string
The ID of the form field containing the contact』s email.

contactStandardFields_First_Name string
The ID of the form field containing the contact』s first name.

contactStandardFields_Last_Name string
The ID of the form field containing the contact』s last name.

contactCustomFields array
A multidimensional array containing the contact custom fields. See Custom Field Properties.

contactOwner string
The Zoho CRM user ID to be assigned to this contact.

contactLeadSource string
The source from which the contact is created. Default values: Advertisement, Cold Call, Employee Referral, External Referral, OnlineStore, Partner, Public Relations, Sales Mail Alias, Seminar Partner, Seminar-Internal, Trade Show, Web Download, Web Research, and Chat.

contactDescription string
The contact description. Merge tags supported.

contactAttachments array
1234array(    '10' => true,    '11' => false,);
An array of file upload fields. The field ID is the key with a boolean value indicating if the files for that field should be attached.

contactApprovalMode boolean
Is approval mode enabled? Default is false.

contactWorkflowMode boolean
Should workflow rules be triggered when this contact is added? Default is false.

contactEmailOptOut boolean
Remove contact from your mailing list so that they will not receive any emails from your Zoho CRM account. Default is false.

contactUpdate boolean
Update contact if existing? Default is false.

Lead Properties
The following properties are only applicable when the action is set to lead.

leadStandardFields_Company string
The ID of the form field containing the lead』s company.

leadStandardFields_Email string
The ID of the form field containing the lead』s email.

leadStandardFields_First_Name string
The ID of the form field containing the lead』s first name.

leadStandardFields_Last_Name string
The ID of the form field containing the lead』s last name.

leadCustomFields array
A multidimensional array containing the lead custom fields. See Custom Field Properties.

leadOwner string
The Zoho CRM user ID to be assigned to this lead.

leadRating string
The lead rating. Default values: Acquired, Active, Market Failed, Project Cancelled, and ShutDown.

leadSource string
The source from which the lead is generated. Default values: Advertisement, Cold Call, Employee Referral, External Referral, OnlineStore, Partner, Public Relations, Sales Mail Alias, Seminar Partner, Seminar-Internal, Trade Show, Web Download, Web Research, and Chat.

leadStatus string
The lead status. Default values: Attempted to Contact, Contact in Future, Contacted, Junk Lead, Lost Lead, Not Contacted, and Pre Qualified.

leadDescription string
The lead description. Merge tags supported.

leadAttachments array
1234array(    '10' => true,    '11' => false,);
An array of file upload fields. The field ID is the key with a boolean value indicating if the files for that field should be attached.

leadApprovalMode boolean
Is approval mode enabled? Default is false.

leadWorkflowMode boolean
Should workflow rules be triggered when this contact is added? Default is false.

leadEmailOptOut boolean
Remove lead from your mailing list so that they will not receive any emails from your Zoho CRM account. Default is false.

leadUpdate boolean
Update lead if existing? Default is false.

Task Properties

createTask boolean
Should a task be created? Default is false.

taskSubject string
The task subject. Merge tags supported.

taskDueDate integer
The number of days until the task is due.

taskOwner string
The Zoho CRM user ID to be assigned to this contact.

taskStatus string
The task status. Default values: Not Started, Deferred, In Progress, Completed, and Waiting on someone else.

Custom Field Properties
1234array(    'key'   => 'title',    'value' => '3',)
Each custom field is an associative array containing the following properties:

key string
The field name. Possible values: the Zoho field name or gf_custom.

Zoho CRM Contacts Module Fields
Zoho CRM Leads Module Fields
Zoho CRM Tasks Module Fields

value string
The ID of the form field or entry meta item containing the value for this custom field.

custom_key string
The custom key. Only used when the custom field key is set to gf_custom.

What is Gravity Forms?

What It IsWhat It Isn』tWhere To Start

What It Is

Gravity Forms is a WordPress plugin that allows site owners, admins and developers to create simple and complex forms to collect information on their WordPress site, and then decide what to do with that information. Gravity Forms can be used for contact forms, WordPress post creation, calculators, employment applications and more. Check out this library of available templates for just a taste of some of the things you can do.

Additionally, we also offer numerous official add-ons ​that help you integrate your form submissions with numerous external services (such as Stripe, PayPal, Square, Zapier or MailChimp). See a full list of official add-ons here.

On top of that, we offer a robust number of WordPress hooks and a fully featured API to enable developers to modify and extend the functionality we provide, and enable third parties to produce extensive number of additions to the core functionality. Refer to our developer documentation, and our repository of third party add-ons that work with Gravity Forms for a sample of what exists.

Written in PHP, Gravity Forms uses many WordPress built-in functions and features to power its form builder. It also uses the same MySQL database system as WordPress, but stores all forms and entries in its own tables. Gravity Forms is open source and GPL licensed. All of the code included is unencrypted.

What It Isn』t

Gravity Forms is not a SaaS service. We do not host your forms, collect or store your form submissions. All that takes place on your designated WordPress website host where you install Gravity Forms.

Gravity Forms is not a design agency. We cannot contract to design or integrate your forms into your website.

We at Gravity Forms are not available for custom coding. But the fine developers at Codeable are!

Where To Start

If you are new to Gravity Forms, try starting your adventure into wonderful forms with this helpful Getting Started checklist.

Check out our informative blog for a host of getting started articles and the latest news.

Or reach out to our team via our Contact Us form if you have further questions.

WP Config Options

General OptionsGF_THEME_IMPORT_FILEGF_LICENSE_KEYMulti-Site Specific OptionsGF_RECAPTCHA_PRIVATE_KEYGF_RECAPTCHA_PUBLIC_KEYGF_IMPORT_FILECreating a Form Import JSON File

General Options
The following options are available for general use.
GF_THEME_IMPORT_FILE
Setting this option allows you to specify a Form JSON file from which a set of default forms can be pre-generated when a theme containing this option is activated. This option should be specified in your theme』s functions.php file. Follow these steps to create a Form JSON file for use with this option.
1define( 'GF_THEME_IMPORT_FILE', 'path/to/gf_import.json' );
Note: The path is relative to your theme root.
GF_LICENSE_KEY
Setting this option before installing Gravity Forms on a single site WP installation or before creating new sites on a multisite install will automatically pre-populate your Gravity Forms license key for those new installations.
1define( 'GF_LICENSE_KEY', 'YOUR-LICENSE-KEY-HERE' );
Multi-Site Specific Options
The following options are available when using WordPress Multi-Site. All of the options below should be defined in your wp-config.php.
GF_RECAPTCHA_PRIVATE_KEY
GF_RECAPTCHA_PUBLIC_KEY
Setting these options will automatically pre-populate your ReCAPTCHA public and private keys when a new site is created on your Multi-Site install.
12define( 'GF_RECAPTCHA_PUBLIC_KEY', 'YOUR-KEY-HERE' );define( 'GF_RECAPTCHA_PRIVATE_KEY', 'YOUR-KEY-HERE' );
GF_IMPORT_FILE
Setting this option allows you to specify a Form JSON file from which a set of default forms can be pre-generated when a new site is created on your Multi-Site install. Follow these steps to create a Form JSON file for use with this option.
1define( 'GF_IMPORT_FILE', 'http://www.domain.com/path/to/gf_import.json' );
Creating a Form Import JSON File
The following steps explain how to create a Form JSON file from which a set of default forms can be pre-generated when used with the GF_IMPORT_FILE or GF_THEME_IMPORT_FILE option.

Create the initial set of forms you want to replicate.
Navigate to the Import/Export tool and select 「Export Forms」.
Select the forms you want to auto-replicate when a new site is created.
Click 「Export」 to export them to an JSON file.
Place the JSON file somewhere on your web server, such as your wp-content/uploads/ folder, or somewhere easily accessible.
Replace the URL in the example code above with the URL to your Form JSON file.

Which PayPal Add-On should I use?

IntroductionPayPal CheckoutLegacy PayPal Add-OnsUsing More Than OneOne-time paymentsRecurring payments

Notice: The Gravity Forms PayPal Commerce Platform Add-On has been renamed PayPal Checkout as of version 2.0.
Introduction
With multiple APIs evolutions and various service interactions, PayPal add-ons have had to evolve, and fork, over the last 10 years of Gravity Forms. This makes the question of 「which should I use?」 a little trickier than most add-ons. We have put together this guide to try and help you with that question.
PayPal Checkout
In most cases, the PayPal Checkout Add-On is what you should use. It is the most up to date, uses the most current PayPal service API, and is the future home of most new functionality as we roll all previous add-on functions into this add-on.
Eventually, this will be the recommended add-on for all use cases, but at this time, PayPal』s Checkout service (previously known as PayPal Commerce Platform) is not available in all markets, so the legacy add-ons do still have a few specific use-cases, as described below.
Legacy PayPal Add-Ons
We classify our PayPal Standard, PayPal Pro, and PayPal Payments Pro Add-Ons as 「legacy」, meaning they have been retired but are not end of life yet. The API』s they rely on have been deprecated by PayPal, so future operation is not guaranteed, though PayPal have not specified any termination dates for these services yet.
We still support these add-ons for now, but no new functionality is expected. Any future releases will purely be for required security or bug fix updates. We will eventually stop all support and development for all the retired add-ons, but at this time there is no official date for when this retirement process will begin. Keep an our on our blog for announcements.
Using More Than One
Multiple add-ons can be used with the same form as long as the PayPal/Credit Card fields and payment add-on feeds have conditional logic configured on them. See the Setting Up Conditional Payments in Gravity Forms article for an example.
One-time payments
One-time payments include products, services, and donations.

Feature
Recommended Add-On

Credit Card Field1 (PayPal Field)
PayPal Checkout Add-On

Credit Card Field (legacy)
PayPal Payments Pro Add-On

PayPal Checkout (PayPal Field)
PayPal Checkout Add-On

PayPal Checkout (legacy)
PayPal Standard Add-On

Venmo (PayPal Field)
PayPal Checkout Add-On

SEPA-Lastschrift (PayPal Field)
PayPal Checkout Add-On

Bancontact (PayPal Field)
PayPal Checkout Add-On

eps (PayPal Field)
PayPal Checkout Add-On

giropay (PayPal Field)
PayPal Checkout Add-On

iDEAL (PayPal Field)
PayPal Checkout Add-On

MyBank (PayPal Field)
PayPal Checkout Add-On

Przelewy24 (PayPal Field)
PayPal Checkout Add-On

Przelewy24 (PayPal Field)
PayPal Checkout Add-On

Simple PCI Compliance
PayPal Checkout Add-On

Strong Customer Authentication (SCA/PSD2)
PayPal Checkout Add-On

Recurring payments
Recurring payments include subscriptions and donations.

Feature
Recommended Add-On

Credit Card Field (deprecated)
PayPal Payments Pro Add-On

PayPal Checkout (PayPal Field)
PayPal Checkout Add-On

PayPal Checkout (legacy)
PayPal Standard Add-On

Simple PCI Compliance
PayPal Checkout Add-On

Strong Customer Authentication (SCA/PSD2)
PayPal Checkout Add-On

Credit Card Field support is currently in limited release on the PayPal Checkout (aka PayPal Commerce) platform.

Zoho CRM Potential Data Errors

SummaryError NotesData FormatData SizeContact/Lead Already Exists

Summary
When data is sent to Zoho CRM for processing, errors may occur. Some errors are related to the data format or size. If an error does occur, the error message will be saved into a note on the entry. Data format or size errors do not prevent the contact/lead from being created in Zoho CRM. The bad data is simply not saved with the contact/lead. A few errors that may occur are listed below.
Error Notes
Data Format
If the data sent is in the wrong format, such as including the @ with the Twitter handle, a message similar to below will be saved as an entry note.

Data Size
Some fields have set field sizes, and if the data sent exceeds the limit, a message like below is sent. To prevent this issue, a Maximum Characters size limit may be set for the field in the Form Editor.

Contact/Lead Already Exists
When creating a feed, there is the setting Update Contact/Lead if contact/lead already exists for email address. If this setting is not checked, the contact/lead is not updated and a message like below is added as a note on the entry.