notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /home/felipere/public_html/leclub.com.co/wp-includes/functions.php on line 3457

my web site is http://leclub.com.co

Thanks for writing in! I’ve passed this to our developers for further investigation.

It’s just a notice and shouldn’t be visible, can you make sure that WP Debug mode is disabled in your website? https://codex.wordpress.org/Debugging_in_WordPress

Thanks!

define(‘WP_DEBUG’, false);

Notice is still present on the page.

The error notice is coming from Soliloquy plugin. That needs to be updated as well. If you are not using this plugin, you can deactivate this plugin. Our developers are already aware of this issue and this will be resolve once we have updated Soliloquy plugin when we roll out our next update release.

Please bear with us. Thank you for your understanding.

Other theme authors have already corrected this problem with a new release of WPBakery Visual Composer. In the X theme, the version remains at 4.6.2., whereas on other sites, it’s been upgraded to Version 4.7.

Many thanks.
—–
Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use

__construct()

instead. in /hermes/bosnaweb14a/b1855/ipg.mrrogersweborhoodcom/mrrogersweborhood/wp-includes/functions.php on line 3457

Thanks for letting us know. I’ll forward it to our developer.

Thanks!

Still no fix for this issue as of today. We are experiencing a number of tech support calls from our customer base (on this and other themes).

I know many, many theme and plugin authors are scrambling to resolve this issue. I can only think it was reckless for WordPress to release 4.3.0 when so many themes and plugins would be affected.

With that being said, is there an estimate on a fix for this?

I really do appreciate your time and assistance on this matter.

Bob

Based on our developer notes, the only plugin that had a problem was Soliloquy, and this was fixed in v2.4.3, which we updated a while back. Here is a screenshot from Soliloquy’s changelog:

If you’re not running v2.4.3 of Soliloquy, you should see an update for it and get that squared away as soon as possible and you’ll be good to go. If you’re still having an error after updating (or simply don’t have Soliloquy installed at all), then it is another third party plugin causing this problem, and you’ll need to look into that to figure out which one it is.

Hopefully this helps!