PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Form is not connecting to paypal upon submission

Gravity Support Forums » Plugin Support » Gravity Forms

  1. AGLLC
    Member

    I am setting up gravity forms on a website and was previously able to get through to paypal and make a transaction, but am no longer able to and am receiving the following error at the top of the page when I click on submit for a payment. Any help into why this is occurring is greatly appreciated.

    Warning: explode() expects parameter 2 to be string, array given in /nfs/c03/h04/mnt/166451/domains/gosavr.com/html/wp-content/plugins/gravityforms/common.php on line 1929

    Warning: explode() expects parameter 2 to be string, array given in /nfs/c03/h04/mnt/166451/domains/gosavr.com/html/wp-content/plugins/gravityforms/common.php on line 1929

    Posted 11 years ago on Thursday May 2, 2013 | Permalink

  2. AAG
    Member

    Getting similar error when submitting form with salesforce and pay pal standard integration - not going to paypal, get email notifications and salesforce is populated, but get an error page:

    PHP Warning: stripslashes() expects parameter 1 to be string, array given in C:\inetpub\aag_main_wp\wp-content\plugins\gravity-forms-salesforce\salesforce.php on line 515

    What is the problem here? When is the paypal pro add on going to start working - very frustrating! Need solution soon or will have to find new form plugin option.

    Posted 11 years ago on Tuesday June 25, 2013 | Permalink

  3. Rob Harrell
    Member

    We didn't create the salesforce add-on, a 3rd party did. That error is coming from the 3rd party plugin. You'll want to report the error your having to them here:

    http://wordpress.org/support/plugin/gravity-forms-salesforce

    Posted 11 years ago on Tuesday June 25, 2013 | Permalink

This topic has been resolved and has been closed to new replies.