Clik here to view.
WordPress weekly digest 4th February to 10th February 2008
It has been a busy week again for WordPress 2.5, the changes this week were: Addition of extra capabilities checks to the xmlrpc code (#5313). New filters for comments_open() and pings_open() (#5761)....
View ArticleClik here to view.
WordPress weekly digest 11th February to 17th February 2008
It has been a busy week again for WordPress 2.5, the changes this week were: Introduction of the beginnings of a plugin update system (#5586). Changes to allow uploads to be stored outside of the WP...
View ArticleClik here to view.
WordPress weekly digest 25th February to 3rd March 2008
Firstly, apologies again for this digest post being a bit late – the final push for 2.5 has been in full swing and I took a week out to go on holiday. It was a busy week again for WordPress 2.5, the...
View ArticleClik here to view.
WordPress weekly digest 24th March to 29th March 2008
It was a busy week again for WordPress 2.5, this list look short as we have been doing the final polishing on today’s WordPress 2.5 release, the changes were: A fix to ensure that we preserve HTML...
View ArticleClik here to view.
making the default install more secure
WordPress 2.6 will be more secure out-of-the box including better support for running the admin over SSL and changes to disable the remote publishing protocols by default. We have choosen to disable...
View ArticleClik here to view.
WordPresz
It seems there has been an attempt recently to distribute a trojaned version of WordPress via some form of phishing scam. It seems this attack relied on exploiting an old version of WordPress which...
View ArticleClik here to view.
Making your broken Plugin work again with WordPress 2.8.1
WordPress 2.8.1 contains changes to improve the security of plugins by ensuring that only correctly registered plugin pages can be accessed as well as only showing the link to the page to users who...
View ArticleClik here to view.
SSL all the things
Security is important and one of the things I would like to see is if we can enforce a requirement for all requests that core makes back to WordPress.org for updates and information to be https. This...
View Article
