• Resolved chasky

    (@chasky)


    Done an upgrade to WP from 4.2.4 to 4.3… and I got below error with fruitful….

    reinstalling fruitful theme didn’t help
    working with a different theme my site works ok without any error

    I’d opened a case in fruitful support page.. so I assume this is kind of duplicate… but i just want everyone to see the current issue. I will update the answer here.

    Error that appears in any page of my site:
    `Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in
    httpd.www/wordpress/wp-includes/functions.php on line 3457

    Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at
    httpd.www/wordpress/wp-includes/functions.php:3457) in
    httpd.www/wordpress/wp-content/themes/fruitful/inc/func/comment-inline-error.php on line 9

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter chasky

    (@chasky)

    Just to clarify… error isn’t an error per se but a warning message that makes my website look bad 🙂
    I’d found a wait to disable the warning… so now I don’t get the message.. but the issue is still there… pretty much fort fruitful guys to resolve to be more align to the latest WP 4.3 version

    from @pcenero (with a minor changes in the last sentences)
    I think easiest way would be to make WP_DEBUG false for now, in wp-config file of your site.
    define(‘WP_DEBUG’, false);
    It worked for me to hide the error, hope works for you as well.
    The wp-config.php file is located at the root of your WordPress installation.
    Simply add that line before the “That’s it! Stop editing!” comment.
    If it already exists, change the true value into false

    Theme Author Fruitful Code

    (@fruitfulcode)

    Hi,

    Your version of Fruitful theme is 2.7?

    Thread Starter chasky

    (@chasky)

    HI, yes it is 2.7

    I was contacted by Fruitful code team over email and they defined this as a warning andby simple disabling the debug (as previously described here in another post) the message should disappear.

    You can send me an email if you want any help to recreate issue to have a proper solution.

    thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Error after upgrade to WP 4.3’ is closed to new replies.