• Resolved David Sahlstr?m

    (@david_sa)


    Hi,

    I’m getting a very strange error on my local install. It’s been working before and is working for other people on my team.
    We have the same exact environment (docker) and exactly the same codebase, still, I’m experiencing the below error.

    Judging from the error message in the “Site is experiencing Technical Issues” email sent by WordPress it looks like it’s having trouble parsing the response from Pardot.

    Any ideas or suggestions as to why this might be happening?

    WordPress version 5.3.2
    Current theme: Aditro (version 2.0)
    Current plugin: Pardot (version 1.4.11)
    PHP version 7.3.11-1+ubuntu18.04.1+deb.sury.org+1

    Error Details
    =============
    An error of type E_ERROR was caused in line 451 of the file /wordpress/wp-content/plugins/pardot/includes/pardot-api-class.php. Error message: Uncaught Exception: String could not be parsed as XML in /wordpress/wp-content/plugins/pardot/includes/pardot-api-class.php:451
    Stack trace:
    #0 /wordpress/wp-content/plugins/pardot/includes/pardot-api-class.php(451): SimpleXMLElement->__construct(”)
    #1 /wordpress/wp-content/plugins/pardot/includes/pardot-api-class.php(162): Pardot_API->get_response(‘campaign’, Array)
    #2 /wordpress/wp-content/plugins/pardot/includes/pardot-plugin-class.php(1056): Pardot_API->get_campaigns(Array)
    #3 /wordpress/wp-content/plugins/pardot/includes/pardot-plugin-class.php(998): Pardot_Plugin::call_api(‘campaigns’, Array)
    #4 /wordpress/wp-content/plugins/pardot/includes/pardot-settings-class.php(757): Pardot_Plugin::get_campaigns()
    #5 [internal function]: Pardot_Settings->campaign_field(Array)
    #6 /wordpress/wp-admin/includes/template.php(1690): call_user_func(Array, Array)
    #7 /wordpress/wp-admin/includes/template.php(1648): do_settings_fields(‘pardot’, ‘pardot_settings’)
    #8 /wordpress/wp-content/plugins/pardot/includes/pardot-setti

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Cliff Seal

    (@cliffseal)

    @david_sa Apologies for the delay.

    That’s interesting—I’m not sure why it would be happening only to you if the environments are the same. Are you connecting to a different account than other folks on your team?

    Plugin Author Cliff Seal

    (@cliffseal)

    @david_sa The latest update addresses this more gracefully, at least.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Strange E_ERROR in version 1.4.11’ is closed to new replies.