dd32

6 ms·

1.
by dd32 15y ago
and a lot of other aspects I'm sure, given the article is over 2 years old..
2.
by dd32 15y ago
Just because a Linux Distribution releases a release with an old version of PHP, it doesnt make it a current-generation PHP release. Yes, It might have extra security patches applied to it[PHP], but Security is not the reason behind applica
3.
by dd32 15y ago
Luckely, the number is much lower than 15%, and is at about 6.5% based on the usage stats: http://wordpress.org/about/stats/ of those, about half are on PHP4, which you cant expect any major application to support for much longer, the res
4.
by dd32 15y ago
Please contact your host and get them to upgrade to something released in the last... 5 years or so? However, 3.1.x is not going to be "officially supported" as a legacy branch AFAIK, If any security issues arrise in the coming months and t
5.
by dd32 15y ago
The idea was to bump the requirements at the same time, to reduce the number of times a host would need to update their older systems. The decision not to change any queries was made early on, 3.3 will bring a few query changes, There are q
6.
by dd32 15y ago
WordPress.com != WordPress.org Project.
7.
by dd32 15y ago
I can't comment on how the accounts were compromised (As I'm not part of those investigating) however I'm pretty sure I can say it's the accounts that were compromised (As the commits came from the plugin owners accounts) and not the svn se
8.
by dd32 15y ago
As the developer who wrote the Upgrading classes; I'd just like to say that PHP4 is, and always was, supported. The upgrade code hasn't been really affected by the switch to PHP5.2.4 All the known issues with PHP4 and upgrading have been do