• Resolved WhistlerDev

    (@prd689)


    Your plugin was very easy to setup, and map fields. Unfortunately, I receive this error on an entry and it does not send to the Infusionsoft CRM. It sends to my admin email address just fine, just not as a Contact within InfusionSoft. Help would be much appreciated.

    Systasis Gravity Forms Infusionsoft Feed Add-On Feed 1: Could not create contact: CURL error: easy handle already used in multi handle

Viewing 15 replies - 1 through 15 (of 19 total)
  • Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    It looks like a plugin conflict. It’s possible there’s a bug in our code that isn’t handling this condition. At this point, I think you want to use the www.ads-software.com community official Health Check & Troubleshooting plugin.

    Please see https://docs.gravityforms.com/conflict-testing-using-health-check-plugin/
    for more information.

    I’d also like to see a system status report.
    https://YOUR WORDPRESS DOMAIN NAME HERE/wp-admin/admin.php?page=gf_system_status

    Thread Starter WhistlerDev

    (@prd689)

    See the status report below. I installed that plugin you suggested and reactivated each one, one by one, including the theme. The error is still presenting itself. We have this site build on kind of a sandbox since it’s not live. Not sure if that’s causing issues.

    ### Gravity Forms ###

    Version: 2.4.20.5 ?
    Upload folder: /home/whistlerworks/public_html/clients/fixthewifi/wp-content/uploads/gravity_forms/
    Upload folder permissions: Writable ?
    Output CSS: Yes
    Output HTML5: No
    No-Conflict Mode: No
    Currency: USD
    Background updates: Yes
    Locale: en_US
    Registration: Site registered ( I removed this license key ) ?

    ### Add-Ons ###

    Systasis GF Infusionsoft Feed: by Systasis Computer Systems, Inc. – 2.3.5 ?

    ### Database ###

    Database Version: 2.4.20.5 ? Your database is up-to-date.
    wp_gf_form_view: ?
    wp_gf_form_meta: ?
    wp_gf_form: ?
    wp_gf_form_revisions: ?
    wp_gf_entry: ?
    wp_gf_entry_meta: ?
    wp_gf_entry_notes: ?
    wp_gf_draft_submissions: ?
    wp_gf_addon_feed: ?

    ### WordPress ###

    Home URL: https://whistleradvantage.com/clients/fixthewifi
    Site URL: https://whistleradvantage.com/clients/fixthewifi
    WordPress Version: 5.5.1 ?
    WordPress Multisite: No
    WordPress Memory Limit: 40M
    WordPress Debug Mode: No
    WordPress Debug Log: No
    WordPress Script Debug Mode: No
    WordPress Cron: Yes
    WordPress Alternate Cron: No
    Background tasks: Yes ?

    ### Active Theme ###

    Pro – Child Theme: by Themeco (https://theme.co/) – 1.0.0 ?
    Pro (Parent): by Themeco (https://theme.co/) – 3.2.3 ?

    ### Active Plugins ###

    Debug Info: by Scott DeLuzio – 1.3.9 ?
    Duplicate Page: by mndpsingh287 – 4.3 ?
    Infusionsoft SDK: by Novak Solutions – 1.0.13 ?
    Schema & Structured Data for WP & AMP: by Magazine3 – 1.9.50 ?
    Slider Revolution: by ThemePunch – 6.2.23 ?
    WPBakery Page Builder: by Michael M – WPBakery.com – 6.4.0 ?
    Yoast SEO: by Team Yoast – 15.0 ?

    ### Web Server ###

    Software: Apache/2.4.46 (cPanel) OpenSSL/1.1.1h mod_bwlimited/1.4
    Port: 443
    Document Root: /home/whistlerworks/public_html

    ### PHP ###

    Version: 7.1.33 ? Recommended: PHP 7.3 or higher.
    Memory Limit: 3000M
    Maximum Execution Time: 600
    Maximum File Upload Size: 1000M
    Maximum File Uploads: 20
    Maximum Post Size: 2000M
    Maximum Input Variables: 1000
    cURL Enabled: Yes (version 7.69.1)
    OpenSSL: OpenSSL 1.1.1h 22 Sep 2020 (269488271)
    Mcrypt Enabled: Yes
    Mbstring Enabled: Yes
    Loaded Extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, pcntl, Reflection, SPL, session, standard, cgi-fcgi, bcmath, calendar, ctype, curl, dom, ftp, gd, iconv, imap, json, mbstring, mcrypt, mysqlnd, PDO, Phar, posix, SimpleXML, sockets, sqlite3, tokenizer, xml, xmlwriter, xsl, zip, mysqli, pdo_mysql, pdo_sqlite, wddx, xmlreader, Zend OPcache

    ### MySQL ###

    Version: 5.5.5 ?
    Database Character Set: latin1
    Database Collation: latin1_swedish_ci

    ### Date and Time ###

    WordPress (Local) Timezone: America/Chicago
    MySQL (UTC): 2020-10-13 16:41:32
    MySQL (Local): October 13, 2020 at 11:41 am
    PHP (UTC): 2020-10-13 16:41:32
    PHP (Local): October 13, 2020 at 11:41 am

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Please see this link and let me know if you can implement any of the remediations. It’s interesting it also mentions Infusionsoft.

    https://www.ads-software.com/support/topic/curl-error-2-easy-handle-already-used-in-multi-handle/

    I’ll keep researching.

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Please set the following settings TRUE in wp-config.php
    WordPress Debug Mode & WordPress Debug Log
    I’m assuming the GF Feed Addon was disabled at the time you ran the system settings log?

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    This is looking like the issue:

    cURL Enabled: Yes (version 7.69.1)

    I haven’t tested with this version. You should be able to downgrade. Please let me know if that’s an option.

    See
    https://www.ads-software.com/support/topic/form-suddenly-not-working-after-20-april-2020/

    [EDIT]
    My development machine uses curl 7.69
    curl 7.69.1 (x86_64-apple-darwin19.3.0) libcurl/7.69.1 OpenSSL/1.1.1e zlib/1.2.11 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0)
    Release-Date: 2020-03-11
    Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
    Features: AsynchDNS HTTPS-proxy IDN IPv6 Largefile libz NTLM NTLM_WB PSL SSL TLS-SRP UnixSockets

    So that might not be it.

    Thread Starter WhistlerDev

    (@prd689)

    If I downgrade the version of cURL, is that a server-wide change? If so, I may ask for our host’s assistance in doing it just to be safe. I’ll let you know.

    Thanks for your help so far in trying to debug this issue.

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Yeah, it’s server wide. I’m not even sure it’ll fix the issue. You mentioned you’re working in a sandbox, so you can try it before deploying it to production.
    I’d still like to see a debug log if you can get one.
    Sorry about the problem. It’s not something I’ve seen before.

    [EDIT]
    There’s also this for more background.
    https://github.com/guzzle/guzzle/issues/2617

    XMLRPC.INC which implements the curl interface does not use guzzle

    [EDIT]
    Sorry, I just realized that you mean a sandbox WordPress site. If this is a managed service site, you might not be able to downgrade.

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    If downgrading isn’t possible, there is also the possibility of disabling HTTP keepalive service. It involves a code change to XMLRPC.INC It’s very easy to do:

    Look for line 944 in /wp-content/plugins/infusionsoft-sdk/Infusionsoft/xmlrpc.inc

    If it looks like
    $this->keepalive = true;

    change it to
    $this->keepalive = false;

    This change will resolve the issue, but it won’t hurt anything.

    Thread Starter WhistlerDev

    (@prd689)

    Thank you for your help. You’ll have to pardon my ignorance, but I’m not exactly sure what to follow in that thread you linked to.

    Thread Starter WhistlerDev

    (@prd689)

    Ok, I’ll give that a shot and let you know. Thanks!

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    Yeah, that guzzle thread was a bit thick. It was further evidence that libcurl has changed in some way.

    BTW: the keepalive change MIGHT fix the issue.

    Thread Starter WhistlerDev

    (@prd689)

    It appears to have fixed it. I just received a new Contact within Infusionsoft. You have been a massive help and your customer support is kick ass. Thank you so so much.

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

    I think I’ve confused the versions.

    From
    https://www.ads-software.com/support/topic/curl-error-2-easy-handle-already-used-in-multi-handle/

    I turned the keep-alive back on, and the site continues to work. This may have coincided with our web host rolling back the cPanel cURL version. Turns out the cURL error began after a cPanel update where cURL went from version 7.69.1 to 7.79.1.

    So rolling back in your case is NOT recommended

    Thread Starter WhistlerDev

    (@prd689)

    Yeah, I didn’t rollback. Your reply to a possible fix caught my eye before anything was done. Again, huge thank you!

    Plugin Author Systasis Computer Systems

    (@systasiscomputersystems)

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Appears to be correctly connected, but nothing being sent’ is closed to new replies.