It’s a problem of perception, so I suppose that makes it an image problem.

That slide annoyed me, too. I decided that we had been trolled. I am sure that if anyone had complained of its unfairness he’d have countered with something edgy about PHP’s inherent suck and lack of true OO purity.
Python and Ruby will always win purity battles with PHP, but those battles won’t do anything constructive for either party. Maybe the speaker realised this and picked a slide that was unfair and ridiculous to drive home the point that he’s really about solving problems quickly and transparently with something that works and the patterns used by Rails can help a lot with that.
PHP’s homepage isn’t limited to lacking pointers to clever time-saving frameworks. It lacks pointers to any sort of best practice, which is a bigger problem. It’s own manual doesn’t even hint at it, in fact the online manual can’t even decide if PHP is OO, with respect to its examples.
Again, I think this is deliberate. PHP is a very broad church, there are still plenty of PHP developers who won’t use OO, plenty who scatter mysql_query() into some HTML and PHP works for them because it works for their boss. Those people do not want to be reading about exception handlers or extending classes because they know PHP is already meeting their needs. The sad part is that these people are the ones who go all starry-eyed when they see Rails “not repeating itself” and they probably blame PHP for being PHP when they were the problem all along.