• I get this in my error log after upgrading to 3.5:

    [18-Dec-2012 18:25:06] PHP Warning: Favicon handling has been removed, please use your own handling in /pathtomysite/wp-includes/class-simplepie.php on line 3006

    Repeated over and over, growing the error log to 1 Mb in a day or two.

Viewing 15 replies - 1 through 15 (of 16 total)
  • Sounds like a theme glitch. Does the theme have a favicon option? Switch to twentyeleven for a few minutes, load the site a bunch of times and see if the errors get logged.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    I have my own custom theme and can’t switch to the useless twentyeleven. I don’t do anything special with favicon. This has something to do with RSS feeds.

    What does ‘Favicon handling has been removed, please use your own handling’ mean?

    Re: this thread and your other threads: relax.

    I said switch to twentyeleven for a few minutes and load the site a bunch of times and see if the same warning is logged. php warnings sometimes point to files that aren’t perfectly relevant.

    Besides, it’s a php warning, which means a warning, not an error or a fatal error. Worst case for right now, change the level of warning handling in php.ini to not log all warnings, like this one.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    “… switch to twentyeleven for a few minutes and load the site a bunch of times and see if the same warning is logged.”

    And then what? What does that solve?

    Hiding warnings is not exactly a solution either.

    WordPress/Automattic’s attitude seems to be that whatever breaks after upgrade, it is not your fault. The assumption is we should all use twentyeleven or commercial themes. The known issues list has some real obnoxious, patronizing bits, like this:

    Don’t worry, if that was greek to you, do the usual turning off plugins and switching themes to figure out which one it is, and then tell the dev ‘Hey, you’re doing_it_wrong() and breaking things!’

    Instead of complaining to my imaginary dev, I’m just throwing it back to ‘WP’.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    And then what? What does that solve?

    Hiding warnings is not exactly a solution either.

    It helps identify where the source your the problem lies. It’s basic troubleshooting. You do want to solve your problem, right? ??

    WordPress/Automattic’s attitude seems to be that whatever breaks after upgrade, it is not your fault.

    Not even remotely true. BTW Automattic is not www.ads-software.com. That’s not semantics; they do contribute huge resources to the www.ads-software.com, but they’re still not www.ads-software.com.

    Instead of complaining to my imaginary dev, I’m just throwing it back to ‘WP’.

    I don’t even know what that means. The 3.5 Master List was written and updated to help you the user.

    https://www.ads-software.com/support/topic/troubleshooting-wordpress-35-master-list?replies=4

    If you want to solve your problem then you need to identify where your problem is. That process includes switching to the Twenty Eleven theme and deactivating all of your plugins.

    Once you’ve temporarily done that then see if that log message comes back. From what you’ve described it shouldn’t take long.

    If you’ve confirmed that does fix it then turn on 1 plugin, check the log, another plugin, check the log, etc. Switch back to your custom theme last.

    That should identify where your problem is. Then you can work to get that fixed.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    class-simplepie.php on line 3006 is in the middle of a bit about sorting multifeed items:

    // If we want to order it by date, check if all items have a date, and then sort it
    if ($this->order_by_date && empty($this->multifeed_objects))
    	{
    	if (!isset($this->data['ordered_items']))
    	{
    		$do_sort = true;
    		foreach ($this->data['items'] as $item)
    		{
    			if (!$item->get_date('U'))
    			{
    				$do_sort = false;
    				break;
    			}
    		}
    		$item = null;
    		$this->data['ordered_items'] = $this->data['items'];
    		if ($do_sort)
    		{
    			usort($this->data['ordered_items'], array(get_class($this), 'sort_items'));
    		}
    	}
    	$items = $this->data['ordered_items'];

    I don’t see the connection with favicon. Probably a clash with the SimplePie Core and SimplePie Plugin for WordPress plugins? Are they deprecated or will they be updated?

    Hello there! Happy New Year!!
    I’m having the same issue.
    I use Dot-B theme. Changed to Twenty eleven and the warning remained.
    I don’t understand a bit of php programming, what can I do?

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    Thanks CynthiaSantos. Now we can move on from the pointless ‘theme glitch’ avenue.

    Do you use the ‘SimplePie Plugin for WordPress‘? Or other SimplePie-related plugins that could cause conflicts?

    I know I should remove those plugins anyway, but I’ll probably have to replace/rewrite a lot of stuff in my custom themes.

    EDIT:

    SimplePie Plugin for WordPress depends one a SimplePie Core plugin that just loads SimplePie. Deactivating and deleting SimplePie Core doesn’t break my theme, so that is something.

    Not sure yet if that fixes the problem. Will report back in a few days…

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    I still get the same ‘PHP Warning: Favicon handling has been removed…’ error after removing the old SimplePie Core plugin.

    What is favicon handling? What should I look for that could cause this? There is nothing about favicon in error line 3006 of class-simplepie.php (see above).

    the warning comes from /wp-includes/class-simplepie.php line 3006

    possibly caused by something in your site – either your theme or a plugin – which is calling the deprecated ‘get_favicon()’ in one or more locations.

    to find out where exactly, you need to go through the troubleshooting process of:
    – temporarily switching to one of the default themes;
    – temporarily deactivating all plugins.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    Have you read the preceding posts? Are you pulling my leg?

    yes – they don’t say anywhere that you have done those basic steps to locate the problem.

    Thread Starter Modifiedcontent

    (@modifiedcontent)

    CynthiaSantos reported the same problem with a standard theme. Switching to TwentyTwelve did not fix it. I had already narrowed it down to line 3006 and the favicon issue, but what does it mean? What is favicon handling?

    Please WP moderators, stop interfering with my threads. You are not helpful at all. I post these issues here hoping to get responses from others who have seen the same issues and then hopefully together find the solution.

    Thank’s, alchymyth!!
    It was the SBS Blogroll plugin that was crashing my blog. fortunatelly, I ONLY had 27 plugins installed…ahahaha I deactivated SBS and everything is working fine, now.

    Modifiedcontent, I don’t use SimplePie Plugin. Thank’s!

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘SimplePie problem after upgrade – 'Favicon handling has been removed'’ is closed to new replies.