Support » Plugin: WP RSS Aggregator » NOt WP4.7 Ready yet

  • Resolved Sébastien SERRE


    I’ve just upgraded and got an error on activation “headers already sent” and a notice:
    class-feed.php is <strong>deprecated</strong> since version 4.7.0! Use fetch_feed() instead. in <b>/var/www/html/wp-includes/functions.php</b> on line <b>3911</b><br />

    Could you please update?

    Many thx for your job

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Xedin Unknown


    Hi Sebastien,

    And thank you for your report. This is a known issue, and we are working on a fix, which will be getting released not later than next week, along with a huge amount of other fixes and improvements. Please update frequently to receive all the latest features and fixes.

    Meanwhile, you are seeing this error because your error reporting settings include E_NOTICE – possibly because you have WP_DEBUG and DISPLAY_ERRORS enabled. The notice is causing the “headers already sent” message, because a redirect is attempted during activation. Just a reminder that in production environments, notices should be turned off. With the notice gone, so would the “headers already sent” message.

    Please let us know if you have any further questions or suggestions.

    I know, i’m currently developping a website integrating your plugins, that’s why i’m with debug on true 😉

    I will update as soon as the fix will be available.

    Thx for your job


    Do you have news about the fix ?

    Hi Sebastien,

    Thanks for getting back to us.

    As we have mentioned before, the fix for this will be included in the next update. We’ll let you know once it’s released. Thank you for your patience.

    Hi, I have display_errors off, and error_reporting includes ~E_NOTICE & ~E_DEPRECATED, and WP_DEBUG is defined to false in wp-config.php, and I’m still seeing the error (!!).

    Any suggestions while we await an update would be sincerely appreciated. I even tried messing with line 3911 of functions.php, and that didn’t improve anything (in fact, odd characters I inserted did not display, leading me to believe that it’s not actually line 3911 causing the error). I emptied page cache, I even changed line 3906 to read if ( FALSE && WP_DEBUG…. so that nothing would trigger, and it still did.

    What have I missed?


    Hi Ken (@menken) and Sebastien (@sebastienthivinfocom),

    We have just released our latest update for the core WP RSS Aggregator plugin, version 4.10. This version supports WordPress 4.7 and includes the fix for this.

    Please give it a try and let us know if the problem still persists.

    We’d also like to remind you to backup your site before updating, just in case you might need it later.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘NOt WP4.7 Ready yet’ is closed to new replies.