Support » Plugin: Pardot » Fatal Error PHP7.2 ,WordPress 4.9.4, Pardot 1.4.5, IIS10.0

  • Resolved jimcin

    (@jimcin)


    Hi,

    I am currently migrating our websites from PHP5.6.3 to PHP7.2

    We are hosting our website on our IIS Servers,

    We are using WordPress 4.9.4, and Pardot 1.4.5.

    I did tried to deactivate all plugins, and put the default WP theme, and issue still occurs.

    I can’t see all options on the settings of the pardot plugin, and I have Fatal error on my logs:

    [16-Mar-2018 19:02:27 UTC] PHP Recoverable fatal error: Object of class stdClass could not be converted to string in E:\Web\XXX\wp-includes\formatting.php on line 1045 [16-Mar-2018 19:02:36 UTC] PHP Recoverable fatal error: Object of class stdClass could not be converted to string in E:\Web\XXX\wp-content\plugins\pardot\includes\pardot-plugin-class.php on line 656 [16-Mar-2018 19:03:28 UTC] PHP Recoverable fatal error: Object of class stdClass could not be converted to string in E:\Web\XXX\wp-includes\formatting.php on line 1045

    Thank you for your help.

Viewing 8 replies - 16 through 23 (of 23 total)
  • Plugin Author Barry

    (@barryhughes-1)

    Unfortunately, we’re no further forward with this.

    In our own testing the update solved this problem and there was no further issue like the one you noted above (additionally, a different user who had hit the same original problem re PHP 7.2-compatibility has also confirmed that the update was successful and didn’t note any subsequent issues).

    If you continue to experience the same problem do let me know and if there is any other information you can provide it would be appreciated. Some further avenues you could explore:

    • Using a suitable tool (WP CLI or a transient manager plugin) to clear out all transients, then try again
    • If your staging site does not contain any sensitive data, we’d be open to taking a look at a database dump if you can share one

    Thanks!

    Thank you,

    I will investigate this further and double check.

    Thanks

    I did some more test and still get this fatal in my log:

    [10-Apr-2018 18:40:30 UTC] PHP Recoverable fatal error: Object of class stdClass could not be converted to string in E:\Web\xxx\wp-content\plugins\pardot\includes\pardot-template-tags.php on line 97

    I deactivated all plugins, and put the default theme twentyseventeen.

    I found this on the pardot/salesforce help, is this something that can be related?

    Summary
    If a Pardot account has IP Security enabled and has not whitelisted their WordPress server, some pages of WordPress may be inaccessible or show internal server errors if using the Pardot WordPress plugin.

    Repro
    1) Enable IP Security
    2) Install Pardot WordPress Plugin v 1.4.3 or higher
    3) Navigate to Pardot plugin settings page
    4) Page will likely not completely load

    Workaround
    Add your WordPress server’s IP address(es) to your Pardot security whitelist page.

    (you need to have a salesforce account) URL is: https://success.salesforce.com/issues_view?id=a1p3A000000EAHVQA4

    Thank you

    I just checked and we don’t use IP Security from pardot, so I don’t think issue comes from there.

    One thing I noticed though is that the script tag added by the pardot plugin looks different on our website compared to other websites from this forums.

    I don’t know if this makes a big difference but the order is different.

    We got :
    piCId = ‘xxxx’
    piAId = ‘xxxxx’

    piHostname = ‘pi.pardot.com’

    and other sites looks to have piAId in first position, followed by piCId.

    I am wondering how this could happen, and if this could be part of my issue?

    thanks

    Plugin Author Barry

    (@barryhughes-1)

    Interesting.

    I’m not sure which other sites you were looking at (perhaps they were running older versions of the plugin) but the definition for piCId should come first, followed by piAId — so this sounds correct.

    A couple of other possibilities I shared earlier:

    • Using a suitable tool (WP CLI or a transient manager plugin) to clear out all transients
    • If your staging site does not contain any sensitive data, we’d be open to taking a look at a database dump if you can share one

    Have you had a chance to explore the first of those especially?

    THank you,

    I checked on the website from jarvizu (the other thread who had same issue).
    After double checking, it looks like he has 2 pardot script, one with piCId then piAId, the second one the other way around.

    Well, thanks a lot, your transient solution seems to work. I never heard about transient before, so thank you. I cleared the transient, and error seems to be gone.

    Great job, thanks for your help.

    I will continue monitoring to check, but I think this should solve my issue.

    Regards

    Plugin Author Barry

    (@barryhughes-1)

    Great to hear – and of course don’t hesitate to let us know if anything else crops up.

    thank you

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Fatal Error PHP7.2 ,WordPress 4.9.4, Pardot 1.4.5, IIS10.0’ is closed to new replies.