WordPress

WordPress

Screenshot  WordPress's default configuration
Developer(s)	Matt Mullenweg, Ryan Boren, Donncha O Caoimh
Initial release	May 27, 2003[1]
Stable release	3.0.1 / July 29, 2010; 6 months ago (2010-07-29)
Development status	Active
Operating system	Cross-platform
Platform	PHP
Type	Weblog software
License	GPLv2[2]
Website	http://wordpress.org/

WordPress is an open source CMS, often used as a blog publishing application powered by PHP and MySQL. It has many features including a plugin architecture and a templating system. Used by over 12% of the 1,000,000 biggest websites, WordPress is the most popular CMS in use today.^[3]

It was first released on May 27, 2003, by Matt Mullenweg^[1] as a fork of b2/cafelog. As of August 2010, version 3.0 had been downloaded over 12.5 million times.^[4]

Contents 1 Features 2 Deployment 3 History 3.1 Awards 3.2 Removal of sponsored themes 3.3 Releases 4 Future 5 Vulnerabilities 6 Multi-blogging 7 Key developers 8 See also 9 References 10 External links

Features

WordPress has a templating system, which includes widgets that can be rearranged without editing PHP or HTML code, as well as themes that can be installed and switched between. The PHP and HTML code in themes can also be edited for more advanced customizations. WordPress also features integrated link management; a search engine-friendly, clean permalink structure; the ability to assign nested, multiple categories to articles; and support for tagging of posts and articles. Automatic filters that provide for proper formatting and styling of text in articles (for example, converting regular quotes to smart quotes) are also included. WordPress also supports the Trackback and Pingback standards for displaying links to other sites that have themselves linked to a post or article. Finally, WordPress has a rich plugin architecture which allows users and developers to extend its functionality beyond the features that come as part of the base install.

Native applications exist for Android,^[5] iPhone/iPod Touch,^[6] and BlackBerry^[7] which provide access to some of the features in the WordPress Admin panel and work with WordPress.com and many WordPress.org blogs.

Deployment

WordPress can be deployed using various methods on a hosting environment. Users have the option to download the current version of WordPress from WordPress.org. From there, they can upload the source code and its dependencies to their hosting environment.

WordPress can also be installed via package management system or deploying a ready-to-use TurnKey WordPress appliance, which does not require any manual setup or configuration.^[8]

WordPress can also be installed via the Microsoft Web Platform Installer which installs WordPress on Windows and IIS. The Web PI will automatically detect any missing dependencies such as PHP or MySQL then install and configure them^[9] before installing WordPress.

Advanced users have the option to have WordPress downloaded to their server and consistently updated using SVN. This will allow users to remain updated easily.^[10]

Free hosting services such as WordPress.com offer users an easy way to deploy a WordPress blog on-line without having to install WordPress on your own web server. Many shared web hosting services also offer automated WordPress installation through their control panel.

History

b2/cafelog, more commonly known as simply b2 or cafelog, was the precursor to WordPress.^[11] b2/cafelog was estimated to have been employed on approximately 2,000 blogs as of May 2003. It was written in PHP for use with MySQL by Michel Valdrighi, who is now a contributing developer to WordPress. Although WordPress is the official successor, another project, b2evolution, is also in active development.

WordPress first appeared in 2003 as a joint effort between Matt Mullenweg and Mike Little to create a fork of b2.^[12] The name WordPress was suggested by Christine Selleck, a friend of Mullenweg.^[13]

In 2004 the licensing terms for the competing Movable Type package were changed by Six Apart and many of its users migrated to WordPress, causing a marked and continuing growth in WordPress's popularity. By October, 2009, the 2009 Open Source CMS Market Share Report reached the conclusion that WordPress enjoys the greatest brand strength of any open source content management systems. That conclusion was based on an extensive analysis of rate of adoption patterns and brand strength and was backed by a survey of users.^[14]

Awards

In 2007 WordPress won a Packt Open Source CMS Award.^[15]

In 2009 WordPress won the best Open Source CMS Award.^[16]

Removal of sponsored themes

On July 10, 2007, following a discussion on the WordPress ideas forum^[17] and a post by Mark Ghosh in his blog Weblog Tools Collection,^[18] Matt Mullenweg announced that the official WordPress theme directory at http://themes.wordpress.net would no longer host themes containing sponsored links.^[19][20] Although this move was criticized by designers and users of sponsored themes, it was applauded by WordPress users who consider such themes to be spam. The official WordPress theme directory ceased to accept any new themes, including those without sponsored links, shortly after the announcement was made.^[21] Sponsored themes are still available elsewhere, as well as free themes with additional sponsored links added by third parties.^[22][23]

On July 18, 2008, a new theme directory opened at http://wordpress.org/extend/themes/. It was styled along the same lines as the plug-ins directory,^[24] Any theme that is uploaded to it will be vetted, first by an automated program and then by a human.

On December 12, 2008, over 200 themes were removed from the WordPress theme directory as they did not comply with GPL License requirements.^[25][26] Today, author mentions are permitted in each theme but the official policy does not allow for sponsorships or links to sites distributing non-GPL compatible themes. Non-GPL compliant themes are now hosted on other theme directories.

Releases

Most WordPress releases are code named after well-known jazz musicians starting after version 1.0.^[27]

Version	Code Name	Release Date	Notes
0.70		27 May 2003	contained the same file structure as its predecessor, b2/cafelog. Only 0.71-gold is available for download in the official WordPress Release Archive page.
1.2	Mingus	22 May 2004	It's notable for containing the support of Plugins. The same Plugin identification headers are still used unchanged in the latest WordPress releases.
1.5	Strayhorn	17 February 2005	Strayhorn added a range of vital features, such as the ability to manage static pages and a template/theme system. It was also equipped with a new default template (code named Kubrick[28]) designed by Michael Heilemann.
2.0	Duke	31 December 2005	This version added rich editing, better administration tools, image uploading, faster posting, an improved import system, and completely overhauled the back end. WordPress 2.0 also offered various improvements to plugin developers.[29]
2.1	Ella	22 January 2007	In addition to correcting security issues, version 2.1 featured a redesigned interface, enhanced editing tools (including integrated spell check and auto save), and improved content management options.[30]
2.2	Getz	16 May 2007	Version 2.2 featured widget support for templates, updated Atom feed support, and speed optimizations.[31]
2.3	Dexter	24 September 2007	Version 2.3 featured native tagging support, new taxonomy system for categories, and easy notification of updates. 2.3 also fully supports Atom 1.0 along with the publishing protocol, and included some much needed security fixes.[32]
2.5	Brecker	29 March 2008	Developers skipped the release of version 2.4 so version 2.5 contained two releases worth of new code. WordPress 2.5 saw a complete overhaul of the administration interface and the WordPress website was also redesigned to match the new style.[33]
2.6	Tyner	15 July 2008	Tyner contained new features that made WordPress a more powerful CMS: you can now track changes to every post and page and easily post from wherever you are on the web.[34]
2.7	Coltrane	11 December 2008	It once again saw the administration interface completely redesigned. It also introduces an automated upgrade feature, and automatic installation of plugins from within the administration interface.[35]
2.8	Baker	10 June 2009	Baker offered improvements in speed, and automatic installation of themes from within the administration interface. It also introduces the CodePress editor for syntax highlighting and a redesigned widget interface.[36]
2.9	Carmen	19 December 2009	Carmen offers a global undo feature, a built-in image editor, batch plugin updating, and numerous under-the-hood tweaks.[37]
3.0	Thelonious	17 June 2010	Thelonious offers a new default theme called "Twenty Ten" along with new theme APIs; the merge of WordPress and WordPress MU, creating the new multi-site functionality; and numerous under-the-hood tweaks.[38]

Future

After the release of WordPress 3.0, Matt Mullenweg updated the WordPress blog letting the community know that his team will be taking a release cycle off from the WordPress software to focus on expanding and improving the WordPress community.^[39][40]

Vulnerabilities

Many security issues^[41][42] were uncovered in the software, particularly in 2007 and 2008. According to Secunia, WordPress in April 2009 had 7 unpatched security advisories (out of 32 total), with a maximum rating of "Less Critical".^[43] Secunia maintains an up-to-date list of WordPress vulnerabilities.^[44]

In January 2007, many high-profile Search engine optimization (SEO) blogs, as well as many low-profile commercial blogs featuring AdSense, were targeted and attacked with a WordPress exploit.^[45] A separate vulnerability on one of the project site's web servers allowed an attacker to introduce exploitable code in the form of a back door to some downloads of WordPress 2.1.1. The 2.1.2 release addressed this issue; an advisory released at the time advised all users to upgrade immediately.^[46]

In May 2007, a study revealed that 98% of WordPress blogs being run were exploitable because they were running outdated and unsupported versions of the software.^[47]

In a June 2007 interview, Stefen Esser, the founder of the PHP Security Response Team, spoke critically of WordPress's security track record, citing problems with the application's architecture that made it unnecessarily difficult to write code that is secure from SQL injection vulnerabilities, as well as some other problems.^[48]

Multi-blogging

Prior to WordPress 3.0, WordPress supported one blog per installation, although multiple concurrent copies may be run from different directories if configured to use separate database tables. WordPress Multi-User (WordPress MU, or just WPMU) was a fork of WordPress created to allow multiple blogs to exist within one installation that is able to be administered by a centralized maintainer. WordPress MU makes it possible for those with a website to host their own blogging community, as well as control and moderate all the blogs from a single dashboard. WordPress MU adds eight new data tables for each blog.

WordPress MU merged with WordPress as part of the 3.0 release.^[49]

Key developers

WordPress development is led by Ryan Boren and Matt Mullenweg. Mullenweg and Mike Little were co-founders of the project.

The core contributing developers include Dougal Campbell, Mark Jaquith, Donncha Ó Caoimh, Andy Skelton, Michel Valdrighi and Peter Westwood.

Though largely developed by the community surrounding it, WordPress is closely associated with Automattic, where 50% of WordPress's core commiters are employees.^[50]

WordPress is also developed by its community, including WP testers, a group of volunteers who test each release. They have early access to nightly builds, beta versions and release candidates. Errors are documented in a special mailing list, or the project's Trac tool.

See also

• Comparison of content management systems
• BuddyPress

References

External links

• Official website
• WordPress at the Open Directory Project