dotzak

Hi Clare12345,

I realize it’s probably too late for you, but for anyone looking for an updated link, click here.

@semaj119 and Preveen:

Please heed the warning I posted if you do alter the code and thoroughly test all functionality of the plugin before putting the changes into effect.

The PHP 4-style constructor is still valid in PHP5, and should still work. The only thing that has changed is that WordPress 4.3+ is now creating warnings in preperation for PHP7.

Most likely you’re only getting a deprecated constructor warning. This warning should only appear if WP_DEBUG is set to true. Simply setting that to false should be enough to silence the error and should have no serious side effects.

If you edit the code you could be introducing bugs to your site unnecessarily.

Hello all,

The PHP4-style constructor has been deprecated, and will pass a warning in WordPress 4.3+.

This is, however, only a warning. The plugin should still work. If it does not work, you may have another problem.

There are two options here: (1) silence the warning, (2) fix the problem yourself by altering the plugin’s code until the plugin developers fix the issue.

1. To silence the warning, simply disable WP_Debug by setting it to false in your wp-config.php file. This is not a fix, just silencing the issue. In my opinion you shouldn’t have this enabled on a live site anyway, it’s really only for development.

NOTE: This will work for most most places the error message will appear, however it’s possible it will still show up in other locations. If that’s the case you cannot silence the error without fixing it.

2. You could update line ~50 of wysija_nl.php from a PHP4-styled constructor:

$this->WP_Widget( $namekey, $title, $params,$sizeWindow );

to a PHP5-styled constructor:

parent::__construct( $namekey, $title, $params,$sizeWindow );

I haven’t tested the fix yet, beyond just getting it to silence the error itself. This will be overwritten the next time this plugin file is updated by the developer and you run updates.

Just for emphasis: I have not tested the code replacement yet. If you’re going to do this you need to thoroughly test before expecting it to work. I know it silences the error, and I know that the plugin still seems to work, but I’ve only done it myself about 10 minutes before writing this.

If you rely on this plugin it may be easier to roll back to WordPress 4.2.4.

Hi,

Is there an update on when this will feature will be released? I have a sidebar form which doesn’t show on my contact page as a result of this.

I really like your plugin, by the way. We’ve used it for a few sites now and it works so nicely! Thanks for your hard work.

Thanks for your reply. I missed it before.

The problem with the CAPTCHA not showing up was a conflict with some code in the ‘head’. I don’t recall what it was now, but removing it fixed the CAPTCHA on the form.

I have the same issue on the form of the homepage at Passion For Language.

I have the form entered into Contact Form 7 using Bootstrap 3 like this:

<div class="row">
<div class="form-group col-sm-4">[text* your-name placeholder class:form-control "Name"]</div>
<div class="form-group col-sm-4">[email* your-email placeholder class:form-control "Email Address"]</div>
<div class="form-group col-sm-4">[text your-phone placeholder class:form-control "Phone Number"]</div>
</div>
<div class="row">
<div class="form-group col-sm-12">[textarea your-message class:form-control]</div>
</div>
<div class="row">
<div class="col-sm-3 col-sm-offset-2">[recaptcha recaptcha-881]</div>
<div class="text-center col-sm-2"><div class="cf7-form-btn">[submit class:btn class:btn-primary class:btn-lg  "Send"]</div></div>
</div>

The code generated on the frontend looks like this:

<div class="col-sm-3 col-sm-offset-2">
<div type="recaptcha" class="wdm-nocapt-recapt wpcf7-form-control wpcf7-recaptcha" id="wdm-nocapt-recapt-id" "=""></div>
<p><span class="wpcf7-form-control-wrap recaptcha-881"></span></p></div>

I’m assuming the problem is something to do with the id="wdm-nocapt-recapt-id" "="" causing jQuery and/or JavaScript not to locate the element?

I’m also having the same issue.