WordPress 3.6.1

WordPress 3.6.1 has been release. This is a maintenance and security release, so please upgrade as soon as you get the chance.

This .1 release fixes 13 bugs and the below security issues:

  • Block unsafe PHP unserialization that could occur in limited situations and setups, which can lead to remote code execution. Reported by Tom Van Goethem.
  • Prevent a user with an Author role, using a specially crafted request, from being able to create a post “written by” another user. Reported by Anakorn Kyavatanakij.
  • Fix insufficient input validation that could result in redirecting or leading a user to another website. Reported by Dave Cummo, a Northrup Grumman subcontractor for the U.S. Centers for Disease Control and Prevention.
  • Additionally, we’ve adjusted security restrictions around file uploads to mitigate the potential for cross-site scripting.

Download: WordPress 3.6.1

1 Star2 Stars3 Stars4 Stars5 Stars (48 votes, average: 3.81 out of 5)

WordPress 3.0 RC1

WordPress 3.0 RC1 has been released just a day after WordPress crosses its 7th birthday!

Happy Birthday WordPress. I have been growing together with you for the past 6 years, unfortunately because of my full time job, I am unable to contribute to you after your 7th birthday! Sorry about that.

As Matt teased earlier, the first release candidate (RC1) for WordPress 3.0 is now available. What’s an RC? An RC comes after beta and before the final launch. It means we think we’ve got everything done: all features finished, all bugs squashed, and all potential issues addressed. But, then, with over 20 million people using WordPress with a wide variety of configurations and hosting setups, it’s entirely possible that we’ve missed something. So! For the brave of heart, please download the RC and test it out (but not on your live site unless you’re extra adventurous). Some things to know:

  • Custom menus are finished! Yay!
  • Multi-site is all set.
  • The look of the WordPress admin has been lightened up a little bit, so you can focus more on your content.
  • There are a ton of changes, so plugin authors, please test your plugins now, so that if there is a compatibility issue, we can figure it out before the final release.
  • Plugin and theme *users* are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.
  • There are a couple of known issues.

Download: WordPress 3.0 RC1

1 Star2 Stars3 Stars4 Stars5 Stars (371 votes, average: 3.80 out of 5)

Widgets

If you look on the right, those items on the sidebar all called widgets. I find them kinda cool and hence I have created widgets for WP-Polls, WP-UserOnline and WP-Stats.

New version of WP-UserOnline and WP-Stats will be coming out on 1st July 2006. Any plugins used on this site are all the latest builds.

1 Star2 Stars3 Stars4 Stars5 Stars (280 votes, average: 3.80 out of 5)

JavaScript In My Plugins

Only 5 of my plugins (WP-Polls, WP-PostRatings, WP-Email, WP-ServerInfo and WP-UserOnline) use JavaScript. The JavaScripts are packed using Dean Edward’s Packer and the only framework use just for AJAX is TW-Sack or Simple AJAX Code-Kit (SACK). TW-Sack is extremely lightweight and easy to use but unfortunately, it can be used only for AJAX purposes. The reason I used TW-Sack instead of jQuery is simple, at the time I created my plugin, jQuery does not exists yet and when jQuery becomes popular the reason why I didn’t upgrade it was because I was lazy. As the saying goes, “If it ain’t broke, don’t fix it”. Recently there is some buzz within the WordPress Development Team regarding WordPress’s JavaScript Usage. Andrew Ozz has written two articles on it in the WordPress Development Updates blog entitled Optimizing script loading, Optimizing script loading part 2 and Optimizing script loading, implementation. With the upcoming WordPress 2.8 will feature some heavy JavaScript changes, I told myself to make use of this chance to totally revamped the JavaScripts in my plugins. Here are the changes that will be made:

  • Minified JavaScript instead of packing them
  • Replaced TW-Sack with jQuery
  • Move JavaScript to the footer
  • Use wp_localize_script() for JavaScript text translation
  • javascript-js.js will now contain the minified code for normal usage
  • javascript-js.dev.js will now contain the unminified code for development purposes

I have already done it for WP-PostRatings and it is now running live on this site. Next, I will be doing WP-UserOnline, followed by WP-Email and lastly WP-Polls as it is more complex.

1 Star2 Stars3 Stars4 Stars5 Stars (122 votes, average: 3.80 out of 5)