WordPress Version 4.9.2 and plugin version 1.4.5

Hey @mayahatt,

Sorry to hear about the trouble there.

1. When you say “that WordPress version”, can you specify which WordPress version you’re referring to?
2. Next, do you know if your site is using any sort of security plugins like WordFence, or just generally has any limitations on sending/receiving requests between your website and third-party websites?

Thanks,
George

As the tile of the thread says, its version 4.9.2 and no there shouldnt be any limitation on access to other sites from our server.

Our server admin says that he sees that error:

Fri Feb 02 12:32:38.387544 2018] [php7:error] [pid 2951] [client] PHP Recoverable fatal error: Object of class stdClass could not be converted to string in /home/preprodmaya/wp-includes/formatting.php on line 1045, referer: https://www.mayahtt.com/wp-admin/options-general.php?page=pardot

I tried setting it up on another wordpress site that I have with version 4.8.1 and it installed and connected just fine. So I guess the problem is related to wordpress version 4.9.2.

@ggwicz Any new about trying it on version 4.9.2 and generating a fix?

Hi there @mayahtt,

Thanks for your patience so far.

This is not a problem we can replicate, which makes me wonder if perhaps there is a conflict with your theme or with another plugin. Here are a few things we can try.

Gather more information by temporarily enabling WP_DEBUG – then try to replicate the problem. My hope is that besides displaying the error you already cited, this will give us a ‘stack trace’ (basically, a bunch of additional information that might help us to track the source of the problem).

Perform some standard troubleshooting steps by temporarily deactivating all other plugins and switching to a standard, default theme such as Twenty Seventeen – then see if you can still replicate the error. If you cannot, it points to there being a conflict with one of the other components you have installed. Try reactivating them one by one and see if you can determine which is causing the conflict.

With regards to that last approach, if you prefer not to do this on a live site you could of course use a staging site, which can be as simple as a fresh WordPress installation contained within a subdirectory.

Let me know how you get on or if you have any questions about this approach!

Hi,

After enabling debug in WP, I got the following: Deprecated: Function mcrypt_get_iv_size() is deprecated

We are using PHP 7.1 and it seems like this function is deprecated. Do you guys support PHP 7.1? If not, when do you plan on updating the plugin to support it?

You could maybe try openssl_encrypt as it seems to be the replacement for mcrypt: https://php.net/manual/en/function.openssl-encrypt.php

We do indeed support PHP 7.1 and are aware of this specific issue ??

You can safely ignore the warning, which is great for troubleshooting and debugging purposes but will not generally cause issues in production (and while this is something of an exception because you are troubleshooting, generally speaking the display of errors will not and should not be enabled).

You could maybe try openssl_encrypt as it seems to be the replacement for mcrypt

This is a certainly a possibility, we’re also exploring the use of libsodium.

Its fixed now downgrading our server to PHP 5.6.33. The Mcrypt is certainly creating and issue with the current plugin version and php 7.1.

That’s great.

Just to clarify, though, so long as the display of errors is deactivated it should be possible to safely ignore the warning about mcrypt. Please note also that it remains possible to install the mcrypt extension in PHP 7.1+, it just doesn’t happen by default.

We are currently working on more complete resolution of this problem, though, so do stay tuned for a further update.