WordPress 2.2.2 and 2.0.11 have been released. Anyone running older versions should upgrade immediately since they include security patches. Plus, they include some minor bug fixes.
I’ve upgraded, have you? If you haven’t, don’t wait or procrastinate, upgrade now, or you might regret it… 😀
The PHP Team has released End of Life information for PHP 4. There will be no more releases of PHP 4 after December 31, 2007 (the end of this year), and critical security issues will no longer be patched after August 8, 2008.
PHP 4 was initially released on May 22, 2000. PHP 4 was a huge step-up from PHP 3, and people started using it soon after it’s release. PHP 5 was initially released on July 13, 2004. Although PHP 5 offered much more better things than PHP 4, PHP 5 adoption was taken very slowly. Mostly because PHP 4 offered everything people needed, and PHP 5 just improved on those features and added some other stuff that people didn’t really need, but they were useful. Even today, in 2007, PHP 5 is still second to PHP 4.
Hopefully the PHP 4 EOL will start to make people use PHP 5. Let’s face it, PHP 4 obsolete. Hosts have plenty of time to get PHP 5 on their servers, and software writers have lots of time to make sure their software works on PHP 5.
PHP 5 adoption by hosts would go a lot quicker if software starting requiring a minimum of PHP 4. GoPHP5.org is trying to get software writers to make PHP 5.2 a minimum requirement.
We’ve had this discussion on the WordPress WP-Hackers mailing list a couple of times. The majority wants to make PHP 5(.2) a minimum requirement. The “lead developers” haven’t really said much on the discussion, though. Although, by the looks of this post that Matt Mullenweg (founder of WordPress) wrote on his Blog, it doesn’t look like it’ll be happening anytime soon…
iTunes 7.3.1 has been released which fixes a Library Saving error. I previously posted the workaround.
I must say, it’s good that Apple patched this. But, why did it take so long? iTunes 7.3 was released on June 29, 2007, and the fix was released July 12, 2007. That’s like 12 days! I doubt it took them more than an hour to fix it, and it’s not like they didn’t know about it, everybody was having the problem.
I’m disappointed in you Apple, even though I don’t really like you anyways… 😛
So, go download the update (Go Start > All Programs, click “Apple Software Update”).
Damn, yesterday was hot (where I live, at least 😛 ). The top temperature was 41 degrees Celsius (105.8 degrees Fahrenheit); and that’s not from the Weather People either, that’s from our own thermometer in the backyard.
We had all the fans on, but those were just moving hot air around. Our deck was so hot in the sun, you could barley stand on it for more than a minute.
Luckily, we have a full, finished basement, so it was nice and cool down there.
Ah, I love summer! 😀
If you’ve ever used WordPress with Internet Explorer, you’ve probably seen that little logo at the bottom of the page. That logo is for BrowseHappy. Another campaign trying to get you to switch browsers. Well, I’ve got some good news for you. In WordPress 2.3, that BrowseHappy logo will no longer be there. Last month I wrote about how I submitted a Ticket and Patch to stop the BrowseHappy logo from showing up in IE7. Well, last night, after a little bit of discussion on the Ticket comments, I submitted a new patch that completely removed the BrowseHappy code from WordPress. Well, today, that patch has been committed into the WordPress Subversion Trunk (which will become 2.3). Changeset 5742 fixes it.
Sweet. 😀
Update [June 21, 2007]: Changeset 5744 now reverts Changeset 5742. Matt Mullenweg (founder of WordPress) wanted it reverted, since BrowseHappy is his site. Which is totally unfair, because these intrusive campaigns had a time, and they had a place. That time is no longer existent, and that place never should have been WordPress.
You are currently browsing the archives for the News category.