Modifiedcontent

I just found this same problem. Tried to delete line 105, but get another error because line 1221 needs class ‘MyPHP’.

So where is that folder ‘externals’ with the myphp.class.php? Can we download it somewhere?

I have now two down sites.

I have “fixed” the feed by changing ‘Syndication feeds show the most recent’ in wp-admin from 5 to 3.

One post seems to be causing problems, although thrashing that post did not fix the feed. I don’t get it…

Would it be possible to add php code to functions.php that would return some kind of safe ‘null’ in <wfw:commentRss> if ‘no element found’?

I have the same error and never installed that Facebook plugin either.

When this happened before I found out that it can be caused by whitespace at the end of wp-config.php. Removing that whitespace fixed the problem.

But now it is broken again. Apparently whitespace or “other stuff” in any plugins and functions.php code can cause this, so good luck tracking down the cause.

Is there a better way to troubleshoot this or prevent these fatal errors? RSS is becoming unusable for me.

@earthman Web & Media, I am deliberately rude to WordPress insiders, because their responses/solutions are usually useless. I hope to get responses from regular, real-world WP users struggling with the same frustrations. If not, my posts help me keep track of unresolved issues.

I think your solutions also miss the point again – correct me if I’m wrong. In my custom theme Firstname Lastname are already consistently stored, but new blogs and user accounts still sometimes have display name format set to ‘crapusername’.

I am looking for a catch-all solution to make Firstname Lastname the default display name format, across a network, forever and ever. Storing Firstname Lastname from a form is not the problem.

Gravity Forms and various user registration plugins are not solutions to any problem having to do with registration – I even made this point in my original post. As far as I know Gravity Forms is mainly a way to make adding forms to WordPress “easier” for people who don’t know any PHP.

I am especially rude about Firstname Lastname and the entire registration process because WordPress clearly has no intention to fix it, bring it up to current internet standards. I have been asking about these things for years, since at least ’96, initially friendly, by now not so much.

One response I got from an Automattic developer was that WordPress couldn’t do Firstname Lastname, because it was insensitive to certain unnamed cultures that don’t use that name format. WordPress lives in a weird bubble for nerd bloggers that never go anywhere.

I am 100% sure jQuery.popover has no dependencies on jQuery UI.

I guess jQuery UI changes standard behavior of jQuery?

Bedankt + het beste voor 2013!

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.

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

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).

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…

I think I found it…

Another jQuery script in the page had a local jquery-ui.js link. Replacing that with the latest version fixes popover’s positioning problem.

<script src="https://code.jquery.com/ui/jquery-ui-git.js"></script>

So I guess there was a clash between the old local jquery-ui.js and the new version of jQuery that comes with WordPress.

I also tried with jquery-ui completely removed, but that breaks everything. So jquery-ui is required for popover? And it is not already included in WP somewhere?

Thanks for looking into this Davey IJzermans!

I have upgraded a second site with a similar setup to WP 3.5 and get the same problem in the popover. I haven’t changed anything else, so the problem may be specific to my site/theme/host, but something in WP 3.5 causes it.

Unfortunately the new version does not fix the problem. It even introduces new ones; the popups disappear behind some elements of the site – probably z-index issue. Still stuck in the upper left corner anyway.

I had looked for clues in bug consoles of various browsers, but couldn’t find any. I have more experience with html, php and CSS troubleshooting, so I’m probably missing something.

I’ll try a few more other things…

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?

“… 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’.

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?

To the WordPress moderator who closed my other thread, can you please change the title of this thread to this:

‘Does WP 3.5 interfere with jQuery outerWidth() etc? ‘