Changes
Undid revision 867111439 by 178.168.204.140 (talk) that's not general data
{{about|the blogging software|the blog host|WordPress.com}}
{{pp-move-indef}}
{{Use mdy dates|date=March 2016}}
{{Infobox software
| name = WordPress
| logo = [[File:WordPress logo.svg|240px]]
| screenshot = WordPress MP6 dashboard.png
| caption = WordPress Dashboard
| developer = WordPress Foundation
| released = {{start date and age|2003|05|27}}<ref name=release />
| latest release version = <!-- If you update [[Template:Wordpress version]], it will automatically update this page and [[List of content management systems]]--> {{Wordpress version}}
| latest release date = {{Wordpress version|releasedate}}
<!-- To edit the Stable release and/or Preview release fields you click on the [±] at the end of each field -->| programming language = [[PHP]]
| operating system = [[Unix-like]], [[Windows]]
| genre = [[Blog software]], [[Content Management System]], [[Content Management Framework]]
| license = [[GNU General Public License Version 2|GNU GPLv2]]+<ref>{{cite web |url=https://wordpress.org/about/license/ |title=WordPress: About: GPL |publisher=WordPress.org |accessdate=June 15, 2010}}</ref>
| website = {{URL|https://wordpress.org}}
}}
'''WordPress''' is a [[free and open-source software|free and open-source]] [[content management system]] (CMS) based on [[PHP]] and [[MySQL]].<ref>{{cite web |publisher=WordPress |title=WordPress Web Hosting |url=https://wordpress.org/hosting/ |accessdate=May 21, 2013}}</ref> Features include a [[Plug-in (computing)|plugin architecture]] and a [[Web template system|template system]]. It is most associated with [[blog]]ging, but supports other types of web content including more traditional [[Electronic mailing list|mailing lists]] and [[Internet forum|forums]], media galleries, and online stores. Used by more than 60 million websites,<ref>{{cite web |url=https://www.forbes.com/sites/jjcolao/2012/09/05/the-internets-mother-tongue/ |title=With 60 Million Websites, WordPress Rules The Web. So Where's The Money? |last=Coalo |first=J.J |date=September 5, 2012 |work=[[Forbes]] |accessdate=February 3, 2016}}</ref> including 30.6% of the top 10 million websites {{as of|2018|04|lc=y}},<ref name="Usage of content management systems for websites">{{cite web |url=http://w3techs.com/technologies/overview/content_management/all/ |title=Usage Statistics and Market Share of Content Management Systems for Websites |date=April 23, 2018 |publisher=W3Techs | accessdate=April 23, 2018}}</ref><ref>{{cite web |url= https://www.linkedin.com/pulse/billion-dollar-tech-company-offices-email-glenn-leibowitz |title= The Billion-Dollar Tech Company With No Offices or Email |access-date = 17 December 2017 |last= Leibowitz |first= Glenn |date= 17 December 2017 |quote= Right now we power about 24% of all websites as of this recording: that is the largest of any of the content management systems. The number two has around 3%. But we are not happy that we have just 24%, and we see a lot of work to get the remaining 76%. |website= [[Linkedin]]}}</ref> WordPress is the most popular [[website]] management system in use.<ref>{{cite web |accessdate=August 1, 2013 |url=http://trends.builtwith.com/cms |title=CMS Usage Statistics |publisher=BuiltWith}}</ref> WordPress has also been used for other application domains such as [[Digital signage|pervasive display systems]] (PDS).<ref>Amir E. Sarabadani Tafreshi and Moira C. Norrie. 2017. ScreenPress: a powerful and flexible platform for networked pervasive display systems. In Proceedings of the 6th ACM International Symposium on Pervasive Displays (PerDis '17). ACM, New York, NY, USA, Article 13, 8 pages. DOI: https://doi.org/10.1145/3078810.3078813</ref>
WordPress was released on May 27, 2003, by its founders, [[Matt Mullenweg]]<ref name=release>{{cite web |url=https://wordpress.org/news/2003/05/wordpress-now-available/ |title=WordPress Now Available |publisher=WordPress |last=Mullenweg |first=Matt |accessdate=July 22, 2010}}</ref> and [[Mike Little]],<ref name=release_commit>{{cite web |url=https://core.trac.wordpress.org/changeset/8 |title=Commit number 8 |accessdate=February 3, 2016}}</ref><ref>{{cite web|last1=Patterson|first1=Dan|title=WordPress "quietly" powers 27% of the web|url=https://www.techrepublic.com/article/wordpress-quietly-powers-27-percent-of-the-web/|website=www.techrepublic.com|accessdate=16 December 2017}}</ref> as a [[Fork (software development)|fork]] of ''b2/cafelog''. The software is released under the [[GNU General Public License#Version_2|GPLv2]] (or later) license.<ref>{{cite web |url=https://wordpress.org/about/license/ |title=WordPress › About » License |publisher=WordPress.org |accessdate=June 30, 2014}}</ref>
To function, WordPress has to be installed on a [[web server]], either part of an [[Internet hosting service]] like [[WordPress.com]] or a computer running the software package WordPress.org in order to serve as a [[Host (network)|network host]] in its own right.<ref>{{cite web |url=https://en.support.wordpress.com/com-vs-org/ |title=Support disaggregating WordPress.com and WordPress.org |publisher=WordPress.com |accessdate=January 7, 2016}}</ref> A local computer may be used for single-user testing and learning purposes.
==Overview==
WordPress has a [[web template system]] using a [[template processor]]. Its architecture is a [[front controller]], routing all requests for non-static [[Uniform Resource Identifier|URI]]<nowiki/>s to a single PHP file which parses the URI and identifies the target page. This allows support for more human-readable [[permalink]]s.<ref>{{Cite news|url=https://wpshout.com/wordpress-front-controller/|title=WordPress and the Front Controller Design Pattern {{!}} WPShout|date=2014-02-11|newspaper=WPShout|access-date=2017-02-15|language=en-US}}</ref>
===Themes===
WordPress users may install and switch among different [[Theme (computing)|themes]]. Themes allow users to change the look and functionality of a WordPress website without altering the core code or site content. Every WordPress website requires at least one theme to be present and every theme should be designed using WordPress standards with structured [[PHP]], valid [[HTML]] (HyperText Markup Language), and [[Cascading Style Sheets]] (CSS). Themes may be directly installed using the WordPress "Appearance" administration tool in the dashboard, or theme folders may be copied directly into the themes directory, for example via [[File Transfer Protocol|FTP]].<ref>{{cite web |url=https://codex.wordpress.org |title=Theme Installation |publisher=Codex.wordpress.org |date=April 9, 2013 |accessdate=April 26, 2013}}</ref> The [[PHP]], [[HTML]] and [[Cascading Style Sheets|CSS]] found in themes can be directly modified to alter theme behavior, or a theme can be a "child" theme which inherits settings from another theme and selectively overrides features.<ref>{{Cite web|url=https://codex.wordpress.org/Child_Themes|title=Child Themes « WordPress Codex|website=codex.wordpress.org|language=en|access-date=2017-02-15}}</ref> WordPress themes are generally classified into two categories: free and premium. Many free themes are listed in the WordPress theme directory, and premium themes are available for purchase from marketplaces and individual WordPress developers. WordPress users may also create and develop their own custom themes. The free theme Underscores created by the WordPress developers has become a popular basis for new themes.<ref>{{cite web |url=https://wptavern.com/introduction-to-underscores-a-wordpress-starter-theme-with-konstantin-obenland |title=Introduction To Underscores: A WordPress Starter Theme With Konstantin Obenland |author=Jeff Chandler |date=April 3, 2014 |accessdate=July 31, 2016}}</ref>
===Plugins===
WordPress' [[plugin (computing)|plugin]] architecture allows users to extend the features and functionality of a website or blog. As of March 2017, WordPress has over 55,286 plugins available,<ref>{{cite web |url=https://wordpress.org/plugins/ |title=WordPress > WordPress Plugins |publisher=WordPress.org |accessdate=March 2, 2017}}</ref> each of which offers custom functions and features enabling users to tailor their sites to their specific needs. These customizations range from [[search engine optimization]], to [[client portal]]s used to display private information to logged in users, to content management systems, to content displaying features, such as the addition of [[GUI widget|widgets]] and [[navigation bar]]s. Not all available plugins are always abreast with the upgrades and as a result they may not function properly or may not function at all. Most plugins are available through WordPress themselves, either via downloading them and installing the files manually via FTP or through the WordPress dashboard. However, many third parties offer plugins through their own websites, many of which are paid packages.
Web developers who wish to develop plugins need to learn WordPress' hook system which consists of over 300 hooks divided into two categories: action hooks and filter hooks.
===Mobiles===
Native applications exist for [[WebOS]],<ref>{{cite web |url=https://webos.wordpress.org/ |title=WordPress for WebOS |work=WordPress |accessdate=March 6, 2012}}</ref> [[Android (operating system)|Android]],<ref>{{cite web |url=http://androidandme.com/2010/02/news/wordpress-publishes-native-android-application/ |title=WordPress publishes native Android application |publisher=Android and Me |date=February 2, 2010 |accessdate=June 15, 2010}}</ref> [[iOS]] (iPhone, iPod Touch, iPad),<ref name="altafsayani">{{cite web |url=http://www.altafsayani.com/2008/07/12/wordpress-app-for-iphone-and-ipod-touch/ |title=Idea: WordPress App For iPhone and iPod Touch |work=WordPress iPhone & iPod Touch |date=July 12, 2008 |accessdate=February 9, 2016}}</ref><ref name="post">{{cite news|url=https://readwrite.com/2011/03/23/18_million_wordpress_blogs_land_on_the_ipad/|title=18 Million WordPress Blogs Land on the iPad|last=|first=|date=March 24, 2011|work=ReadWriteWeb|access-date=|archive-url=|archive-date=|dead-url=}}</ref> [[Windows Phone]], and [[BlackBerry]].<ref>{{cite web |url=https://blackberry.wordpress.org/ |title=WordPress for BlackBerry |work=WordPress |accessdate=December 27, 2009 |deadurl=yes |archiveurl=http://arquivo.pt/wayback/20131106094925/http://blackberry.wordpress.org/ |archivedate=November 6, 2013 |df=mdy-all }}</ref> These applications, designed by [[Automattic]], have options such as adding new blog posts and pages, commenting, moderating comments, replying to comments in addition to the ability to view the stats.<ref name="altafsayani" /><ref name="post" />
===Other features===
WordPress also features integrated link management; a [[Web search engine|search engine]]–friendly, clean [[permalink]] structure; the ability to assign multiple categories to posts; and support for [[Tag (metadata)|tagging]] of posts. Automatic filters are also included, providing standardized formatting and styling of text in posts (for example, converting regular quotes to [[Quotation marks in English#Smart quotes|smart quotes]]). WordPress also supports the [[Trackback]] and [[Pingback]] standards for displaying links to other sites that have themselves linked to a post or an article. WordPress posts can be edited in HTML, using the visual editor, or using one of a number of plugins that allow for a variety of customized editing features.
==Multi-user and multi-blogging==
Prior to version 3, WordPress supported one blog per installation, although multiple concurrent copies may be run from different directories if configured to use separate database tables. WordPress Multisites (previously referred to as WordPress Multi-User, WordPress MU, or WPMU) was a fork of WordPress created to allow multiple blogs to exist within one installation but is able to be administered by a centralized maintainer. WordPress MU makes it possible for those with websites to host their own blogging communities, as well as control and moderate all the blogs from a single dashboard. WordPress MS adds eight new data tables for each blog.
As of the release of WordPress 3, WordPress MU has merged with WordPress.<ref>{{cite web |url=https://wordpress.org/development/2010/06/thelonious/ |title=WordPress 3.0 "Thelonious" |publisher=WordPress.org |date=June 17, 2010 |accessdate=December 18, 2011}}</ref>
==History==
''b2/cafelog'', more commonly known as ''b2'' or ''cafelog'', was the precursor to WordPress.<ref>{{cite video |people=Andrew Warner, [[Matt Mullenweg]] |date=September 10, 2009 |title=The Biography Of WordPress – With Matt Mullenweg |url=http://mixergy.com/the-biography-of-wordpress-with-matt-mullenweg/ |format=[[MPEG-4 Part 14]] |medium=Podcast |publisher=Mixergy |accessdate=September 28, 2009 |time=10:57 |quote=b2 had actually, through a series of circumstances, essentially become abandoned.}}</ref>
b2/cafelog was estimated to have been installed on approximately 2,000 blogs as of May 2003.<ref>{{cite web |last=Valdrighi |first=Michel |title=b2 test weblog - post dated 23.05.03 |url=http://cafelog.com/index.php?p=500 |accessdate=May 9, 2013}}</ref> 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 (software development)|fork]] of b2.<ref>{{cite web |url=https://codex.wordpress.org/History |title=History - WordPress Codex |accessdate=March 29, 2012 |publisher=WordPress.org}}</ref> Christine Selleck Tremoulet, a friend of Mullenweg, suggested the name ''WordPress''.<ref>{{cite web |url=http://blog.chron.com//techblog/2008/01/the-importance-of-being-matt/ |title=The importance of being Matt |author=Silverman, Dwight |publisher=Houston Chronicle |date=January 24, 2008 |accessdate=August 14, 2014}}</ref><ref>{{cite web |url=http://www.bigpinkcookie.com/2008/01/24/the-importance-of-being-matt/ |title=The Importance of Being Matt… |author=Tremoulet, Christine Selleck |publisher=Christine Selleck Tremoulet |date=January 24, 2008 |accessdate=March 29, 2012}}</ref>
In 2004 the licensing terms for the competing [[Movable Type]] package were changed by [[Six Apart]], resulting in many of its most influential users migrating to WordPress.<ref>{{cite web |url=http://www.salon.com/2004/08/09/six_apart/ |title=Blogging grows up |author=Manjoo, Farhad |publisher=Salon |date=August 9, 2004 |accessdate=March 29, 2012}}</ref><ref>{{cite web |archiveurl=https://web.archive.org/web/20060410125402/http://diveintomark.org/archives/2004/05/14/freedom-0 |url=http://diveintomark.org/archives/2004/05/14/freedom-0 |title=Freedom 0 |author=Pilgrim, Mark |publisher=Mark Pilgrim |archivedate=April 10, 2006 |date=May 14, 2004 |accessdate=March 29, 2012 |deadurl=yes |df=mdy-all }}</ref>
By October 2009 the Open Source CMS MarketShare Report concluded that WordPress enjoyed the greatest brand strength of any open-source content management system.
As of February 2017, WordPress is used by 58.7% of all the websites whose content management system is known. This is 27.5% of the top 10 million websites.<ref name="Usage of content management systems for websites" /><ref>{{Cite news|url=https://www.theregister.co.uk/2018/03/05/wordpress_is_now_30_per_cent_of_the_web/|title=WordPress is now 30 per cent of the web, daylight second|access-date=2018-03-20|language=en}}</ref>
===Awards and recognition===
*Winner of [[Infoworld]]'s "Best of open source software awards: Collaboration", awarded in 2008.<ref name="award 2008">{{cite web | title = Best of open source software awards: Collaboration | publisher = infoworld.com | url = https://www.infoworld.com/article/2638571/techology-business/best-of-open-source-software-awards--collaboration.html | accessdate = 2017-12-16 }}</ref>
*Winner of Open Source CMS Awards's "Overall Best Open Source CMS", awarded in 2009.<ref name="Open Source CMS 2009">{{cite web | title = WordPress wins top prize in 2009 Open Source CMS Awards | publisher = cmscritic.com | url = https://www.cmscritic.com/wordpress-wins-top-prize-in-2009-open-source-cms-awards/ | accessdate = 2017-12-16 }}</ref>
*Winner of digitalsynergy's "Hall of Fame CMS category in the 2010 Open Source", awarded in 2010.<ref name="bossie 2010">{{cite web | title = Hall of Fame CMS | publisher = digitalsynergy.ca | url = http://www.digitalsynergy.ca/library/wordpress-wins-hall-of-fame-cms-award/ | accessdate = 2017-12-16 }}</ref>
*Winner of [[Infoworld]]'s "Bossie award for Best Open Source Software", awarded in 2011.<ref name="bossie 2011">{{cite web | title = WordPress wins Bossie Awards 2011: The best open source applications | publisher = wprockers.com | url = http://wprockers.com/wordpress-wins-bossie-awards-2011-the-best-open-source-applications-1610.html | accessdate = 2017-12-16 }}</ref>
*Winner of CMS Critic Award's "Best CMS for Personal Websites", awarded in 2015.<ref name="CMS 2015">{{cite web | title = CMS Critic Awards Home 2015 Winners | publisher = cmscritic.com | url = https://www.cmscritic.com/awards/2015-winners/ | accessdate = 2017-12-16 }}</ref>
*Wordpress has a five star [[privacy]] rating from the [[Electronic Frontier Foundation]].<ref>{{cite web|url=https://www.eff.org/who-has-your-back-2017|title=Who Has Your Back? Government Data Requests 2017}}</ref>
===Release history===
Main releases of WordPress are codenamed after well-known [[jazz]] musicians, starting from version 1.0.<ref>{{cite web|last1=hollander|first1=Roel|title=Fun Fact: Wordpress Jazz Tributes|url=https://roelhollander.eu/en/blog-other-articles/wordpress-jazz-tributes/|website=roelhollander.eu|accessdate=16 December 2017}}</ref><ref>{{cite web |url=https://wordpress.org/about/roadmap/ |title=Roadmap |work=Blog |publisher=WordPress.org |accessdate=June 15, 2010}}</ref>
<!--Template:Version - for version & release history. Documentation & examples: -->
{{Version |t |show=11111}}
{| class="wikitable"
! Version
! Code name
! Release date
! Notes
|-
! {{Version |o |0.7}}
| none
| May 27, 2003<ref>{{cite web |url=https://wordpress.org/news/2003/05/wordpress-now-available/ |title=WordPress Blog: WordPress 0.7 |publisher=WordPress.org |accessdate=May 27, 2003}}</ref>
| Used the same file structure as its predecessor, ''b2/cafelog'', and continued the numbering from its last release, 0.6.<ref>{{cite web |url=http://cafelog.com/ |title=Cafelog |accessdate=May 15, 2011}}</ref> Only 0.71-gold is available for download in the official WordPress Release Archive page.
|-
! {{Version |o |1.0}}
| ''[[Miles Davis|Davis]]''
| January 3, 2004<ref>{{cite web |url=https://wordpress.org/news/2004/01/wordpress-10/ |title=WordPress Blog: WordPress 1.0 |publisher=WordPress.org |accessdate=January 3, 2004}}</ref>
| Added search engine friendly permalinks, multiple categories, dead simple installation and upgrade, comment moderation, XFN support, Atom support.
|-
! {{Version |o |1.2}}
| ''[[Charles Mingus|Mingus]]''
| May 22, 2004<ref>{{cite web |url=https://wordpress.org/news/2004/05/heres-the-beef/ |title=WordPress Blog: WordPress 1.2 |publisher=WordPress.org |accessdate=May 22, 2004}}</ref>
| Added support of Plugins; which same identification headers are used unchanged in WordPress releases {{as of|2011|lc=y}}.
|-
! {{Version |o |1.5}}
|''[[Billy Strayhorn|Strayhorn]]''
| February 17, 2005<ref>{{cite web |url=https://wordpress.org/news/2005/02/strayhorn/ |title=WordPress Blog: WordPress 1.5 |publisher=WordPress.org |accessdate=February 17, 2005}}</ref>
| Added a range of vital features, such as ability to manage static pages and a template/Theme system. It was also equipped with a new default template (code named ''[[Stanley Kubrick|Kubrick]]'').<ref>{{cite web |url=http://binarybonsai.com/kubrick |title=Kubrick at Binary Bonsai |publisher=Binarybonsai.com |accessdate=June 15, 2010}}</ref> designed by Michael Heilemann.
|-
| colspan="4" |
|-
! {{Version |o |2.0}}
| ''[[Duke Ellington|Duke]]''
| December 31, 2005<ref>{{cite web |url=https://wordpress.org/news/2005/12/wp2/ |title=WordPress Blog: WordPress 2.0 |publisher=WordPress.org |accessdate=December 31, 2005}}</ref>
| Added rich editing, better administration tools, image uploading, faster posting, improved import system, fully overhauled the back end, and various improvements to Plugin developers.
|-
! {{Version |o |2.1}}
| ''[[Ella Fitzgerald|Ella]]''
| January 22, 2007<ref>{{cite web |url=https://wordpress.org/news/2007/01/ella-21/ |title=WordPress Blog: WordPress 2.1 |publisher=WordPress.org |accessdate=January 22, 2007}}</ref>
| Corrected security issues, redesigned interface, enhanced editing tools (including integrated spell check and auto save), and improved content management options.
|-
! {{Version |o |2.2}}
| ''[[Stan Getz|Getz]]''
| May 16, 2007<ref>{{cite web |url=https://wordpress.org/news/2007/05/wordpress-22/ |title=WordPress Blog: WordPress 2.2 |publisher=WordPress.org |accessdate=May 16, 2007}}</ref>
| Added widget support for templates, updated [[Atom (standard)|Atom]] feed support, and speed optimizations.
|-
! {{Version |o |2.3}}
| ''[[Dexter Gordon|Dexter]]''
| style="white-space: nowrap;"| September 24, 2007<ref>{{cite web |url=https://wordpress.org/news/2007/09/wordpress-23/ |title=WordPress Blog: WordPress 2.3 |publisher=WordPress.org |accessdate=September 24, 2007}}</ref>
| Added native tagging support, new [[Taxonomy (general)|taxonomy]] system for categories, and easy notification of updates, fully supports Atom 1.0, with the publishing protocol, and some much needed security fixes.
|-
! {{Version |o |2.5}}
| ''[[Michael Brecker|Brecker]]''
| March 29, 2008<ref>{{cite web |url=https://wordpress.org/news/2008/03/wordpress-25-brecker/ |title=WordPress Blog: WordPress 2.5 |publisher=WordPress.org |accessdate=March 29, 2008}}</ref>
| Major revamp to the dashboard, dashboard widgets, multi-file upload, extended search, improved editor, improved plugin system and more.
|-
! {{Version |o |2.6}}
| ''[[McCoy Tyner|Tyner]]''
| July 15, 2008<ref>{{cite web |url=https://wordpress.org/news/2008/07/wordpress-26-tyner/ |title=WordPress Blog: WordPress 2.6 |publisher=WordPress.org |accessdate=June 15, 2008}}</ref>
| Added new features that made WordPress a more powerful CMS: it can now [[revision control|track changes]] to every post and page and allow easy posting from anywhere on the web.
|-
! {{Version |o |2.7}}
| ''[[John Coltrane|Coltrane]]''
| December 11, 2008<ref>{{cite web |url=https://wordpress.org/news/2008/12/coltrane/ |title=WordPress Blog: WordPress 2.7 |publisher=WordPress.org |accessdate=December 11, 2008}}</ref>
| Administration interface redesigned fully, added automatic upgrades and installing plugins, from within the administration interface.
|-
! {{Version |o |2.8}}
| ''[[Chet Baker|Baker]]''
| June 10, 2009<ref>{{cite web |url=https://wordpress.org/news/2009/06/wordpress-28/ |title=WordPress Blog: WordPress 2.8 |publisher=WordPress.org |accessdate=June 10, 2009}}</ref>
| Added improvements in speed, automatic installing of themes from within administration interface, introduces the CodePress editor for [[syntax highlighting]] and a redesigned widget interface.
|-
! {{Version |o |2.9}}
| ''[[Carmen McRae|Carmen]]''
| December 19, 2009<ref>{{cite web |url=https://wordpress.org/news/2009/12/wordpress-2-9/ |title=WordPress Blog: WordPress 2.9 |publisher=WordPress.org |accessdate=December 19, 2009}}</ref>
| Added global undo, built-in image editor, batch plugin updating, and many less visible tweaks.
|-
| colspan="4" |
|-
! {{Version |o |3.0}}
| ''[[Thelonious Monk|Thelonious]]''
| June 17, 2010<ref>{{cite web |url=https://wordpress.org/news/2010/06/thelonious/ |title=WordPress Blog: WordPress 3.0 |publisher=WordPress.org |accessdate=June 17, 2010}}</ref>
| Added a new theme [[application programming interface|API]]s, merge WordPress and WordPress MU, creating the new multi-site functionality, new default theme "Twenty Ten" and a refreshed, lighter admin UI.
|-
! {{Version |o |3.1}}
| ''[[Django Reinhardt|Reinhardt]]''
| February 23, 2011<ref>{{cite web |url=https://wordpress.org/news/2011/02/threeone/ |title=WordPress Blog: WordPress 3.1 |publisher=WordPress.org |accessdate=February 25, 2011}}</ref>
| Added the Admin Bar, which is displayed on all blog pages when an admin is logged in, and Post Format, best explained as a Tumblr like micro-blogging feature. It provides easy access to many critical functions, such as comments and updates. Includes internal linking abilities, a newly streamlined writing interface, and many other changes.
|-
! {{Version |o |3.2}}
| ''[[George Gershwin|Gershwin]]''
| July 4, 2011<ref>{{cite web |url=https://wordpress.org/news/2011/07/gershwin/ |title=WordPress Blog: WordPress 3.2 |publisher=WordPress.org |accessdate=June 4, 2011}}</ref>
| Focused on making WordPress faster and lighter. Released only four months after version 3.1, reflecting the growing speed of development in the WordPress community.
|-
! {{Version |o |3.3}}
| ''[[Sonny Stitt|Sonny]]''
| December 12, 2011<ref>{{cite web |url=https://wordpress.org/news/2011/12/sonny/ |title=WordPress Blog: WordPress 3.3 |publisher=WordPress.org |accessdate=December 12, 2011}}</ref>
| Focused on making WordPress friendlier for beginners and [[tablet computer]] users.
|-
! {{Version |o |3.4}}
| ''[[Grant Green|Green]]''
| June 13, 2012<ref>{{cite web |url=https://wordpress.org/news/2012/06/green/ |title=WordPress Blog: WordPress 3.4 |publisher=WordPress.org |accessdate=June 13, 2012}}</ref>
| Focused on improvements to theme customization, [[Twitter]] integration and several minor changes.
|-
! {{Version |o |3.5}}
| ''[[Elvin Jones|Elvin]]''
| December 11, 2012<ref>{{cite web |url=https://wordpress.org/news/2012/12/elvin/ |title=WordPress Blog: WordPress 3.5 |publisher=WordPress.org |accessdate=December 11, 2012}}</ref>
| Support for the [[Retina Display]], color picker, new default theme "Twenty Twelve", improved image workflow.
|-
! {{Version |o |3.6}}
| ''[[Oscar Peterson|Oscar]]''
| August 1, 2013<ref>{{cite web |url=https://wordpress.org/news/2013/08/oscar/ |title=WordPress Blog: WordPress 3.6 |publisher=WordPress.org |accessdate=August 1, 2013}}</ref>
| New default theme "Twenty Thirteen", admin enhancements, post formats UI update, menus UI improvements, new revision system, autosave and post locking.
|-
! {{Version |co |3.7}}
| ''[[Count Basie|Basie]]''
| October 24, 2013<ref>{{cite web |url=https://wordpress.org/news/2013/10/basie/ |title=WordPress Blog: WordPress 3.7 |publisher=WordPress.org |accessdate=October 24, 2013}}</ref>
| Automatically apply maintenance and security updates in the background, stronger password recommendations, support for automatically installing the right language files and keeping them up to date.
|-
! {{Version |co |3.8}}
| ''[[Charlie Parker|Parker]]''
| December 12, 2013<ref>{{cite web |url=https://wordpress.org/news/2013/12/parker/ |title=WordPress Blog: WordPress 3.8 |publisher=WordPress.org |accessdate=December 12, 2013}}</ref>
| Improved admin interface, responsive design for mobile devices, new typography using [[Open Sans]], admin color schemes, redesigned theme management interface, simplified main dashboard, "Twenty Fourteen" magazine style default theme, second release using "Plugin-first development process".
|-
! {{Version |co |3.9}}
| ''[[Jimmy Smith (musician)|Smith]]''
| April 16, 2014<ref>{{cite web |url=https://wordpress.org/news/2014/04/smith/ |title=WordPress Blog: WordPress 3.9 |publisher=WordPress.org |accessdate=April 16, 2014}}</ref>
| Improvements to editor for media, live widget and header previews, new theme browser.
|-
| colspan="4" |
|-
! {{Version |co |4.0}}
| ''[[Benny Goodman|Benny]]''
| September 4, 2014<ref>{{cite web |url=https://wordpress.org/news/2014/09/benny/ |title=WordPress Blog: WordPress 4.0 |publisher=WordPress.org |accessdate=September 4, 2014}}</ref>
| Improved media management, embeds, writing interface, easy language change, theme customizer, plugin discovery and compatibility with [[PHP]] 5.5 and [[MySQL]] 5.6.<ref>{{cite web |url=http://www.suntecoss.com/blog/learn-whats-new-in-wordpress-v4-0 |title=Learn What’s New in WordPress v4.0 |accessdate=March 14, 2016}}</ref>
|-
! {{Version |co|4.1}}
| ''[[Dinah Washington|Dinah]]''
| December 18, 2014<ref name="wordpress1">{{cite web |url=https://wordpress.org/news/2014/12/dinah/ |title=WordPress Blog: WordPress 4.1 |publisher=WordPress.org |accessdate=December 18, 2014}}</ref>
| Twenty Fifteen as the new default theme, distraction-free writing, easy language switch, Vine embeds and plugin recommendations.
|-
! {{Version |co |4.2}}
| ''[[Bud Powell|Powell]]''
| April 23, 2015<ref>{{cite web |url=https://wordpress.org/news/2015/04/powell/ |title=WordPress Blog: WordPress 4.2 |publisher=WordPress.org |accessdate=April 23, 2015}}</ref>
| New "Press This" features, improved characters support, emoji support, improved customizer, new embeds and updated plugin system.
|-
! {{Version |co |4.3}}
| ''[[Billie Holiday|Billie]]''
| August 18, 2015<ref>{{cite web |url=https://wordpress.org/news/2015/08/billie/ |title=WordPress Blog: WordPress 4.3 |publisher=WordPress.org |accessdate=August 18, 2015}}</ref>
| Focus on mobile experience, better passwords and improved customizer.
|-
! {{Version |co |4.4}}
| ''[[Clifford Brown|Clifford]]''
| December 8, 2015<ref>{{cite web |url=https://wordpress.org/news/2015/12/clifford |title=WordPress Blog: WordPress 4.4 |publisher=WordPress.org |accessdate=December 8, 2015}}</ref>
| Introduction of "Twenty Sixteen" theme, and improved responsive images and embeds.
|-
! {{Version |co |4.5}}
| ''[[Ornette Coleman|Coleman]]''
| April 12, 2016<ref>{{cite web |url=https://wordpress.org/news/2016/04/coleman/ |title=WordPress Blog: WordPress 4.5|publisher=WordPress.org|accessdate=April 26, 2016}}</ref>
| Added inline linking, formatting shortcuts, live responsive previews, and other updates under the hood.
|-
|-
! {{Version |co |4.6}}
| ''[[Pepper Adams|Pepper]]''
| August 16, 2016<ref>{{cite web |url=https://wordpress.org/news/2016/08/pepper/ |title=WordPress Blog: WordPress 4.6 |publisher=WordPress.org|accessdate=August 16, 2016}}</ref>
| Added streamlined updates, native fonts, editor improvements with inline link checker and content recovery, and other updates under the hood.
|-
|-
! {{Version |co |4.7}}
| ''[[Sarah Vaughan|Vaughan]]''
| December 6, 2016<ref>{{cite web |url=https://wordpress.org/news/2016/12/vaughan/ |title=WordPress Blog: WordPress 4.7 "Vaughan" |publisher=WordPress.org|accessdate=December 7, 2016}}</ref>
| Comes with new default theme "Twenty Seventeen", Video Header Support, PDF preview, custom CSS in live preview, editor Improvements, and other updates under the hood.
|-
|-
! {{Version |co |4.8}}
| ''[[Bill Evans|Evans]]''
| June 8, 2017<ref>{{cite web |url=https://make.wordpress.org/core/4-8/ |title=Version 4.8 – Make WordPress Core |publisher=WordPress.org |accessdate=August 1, 2017}}</ref>
| The next-generation editor. Additional specific goals include the TinyMCE inline element / link boundaries, new media widgets, WYSIWYG in text widget. End Support for Internet Explorer Versions 8, 9, and 10.
|-
|-
! {{Version |c |4.9}}
| ''[[Billy Tipton|Tipton]]''
| November 16, 2017<ref>{{cite web |url=https://make.wordpress.org/core/4-9/ |title=Version 4.9 – Make WordPress Core |publisher=WordPress.org |accessdate=August 6, 2017}}</ref>
| Improved theme customizer experience, including scheduling, frontend preview links, autosave revisions, theme browsing, improved menu functions, and syntax highlighting. Added new gallery widget and updated text and video widgets. Theme editor gives warnings and rollbacks when saving files that produce fatal errors.<ref>{{cite web |url=https://wordpress.org/news/2017/10/wordpress-4-9-beta-1/ |title=WordPress Blog: WordPress 4.9 Beta 1|publisher=WordPress.org|accessdate=October 25, 2017}}</ref>
|-
| colspan="4" |
|-
! {{Version |p |5.0}}
|[[Johannes Gutenberg|''Gutenberg'']]
| November 19, 2018
| WordPress 5.0 will be the first "major" release of 2018, including the new editor, code-named "Gutenberg".
|-
|}
==Future==
Matt Mullenweg has stated that the future of WordPress is in social, mobile, and as an application platform.<ref>{{cite web |url=http://ma.tt/2012/05/simpler/ |title=Radically Simplified WordPress |publisher=Ma.tt |accessdate=March 11, 2015}}</ref><ref>{{cite web |url=http://wordpress.tv/2013/07/29/matt-mullenweg-state-of-the-word-2013/ |title=Matt Mullenweg: State of the Word 2013 |publisher=WordPress.tv |accessdate=March 11, 2015}}</ref>
==Vulnerabilities==
Many security issues<ref>{{cite web |date=June 28, 2007 |title=David Kierznowski |url=http://blogsecurity.net/wordpress/interview-280607/ |publisher=Blogsecurity.net |archiveurl=https://web.archive.org/web/20120309013608/http://blogsecurity.net/wordpress/interview-280607 |archivedate=March 9, 2012 |accessdate=February 17, 2016}}</ref> have been uncovered in the software, particularly in 2007, 2008, and 2015. According to [[Secunia]], WordPress in April 2009 had seven unpatched security advisories (out of 32 total), with a maximum rating of "Less Critical". Secunia maintains an up-to-date list of WordPress vulnerabilities.<ref>{{cite web |url=https://secuniaresearch.flexerasoftware.com/community/advisories/54803 |title=Secunia WordPress Vulnerability Report |publisher=Secunia.com |accessdate=September 13, 2013}}</ref>
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.<ref>{{cite web |url=http://www.threadwatch.org/node/11333 |title=WordPress Exploit Nails Big Name Seo Bloggers |publisher=Threadwatch.org |accessdate=December 18, 2011}}</ref> A separate vulnerability on one of the project site's [[web server]]s allowed an attacker to introduce exploitable code in the form of a [[Backdoor (computing)|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.<ref>{{cite web |url=https://wordpress.org/development/2007/03/upgrade-212/ |title=WordPress 2.1.1 dangerous, Upgrade to 2.1.2 |publisher=WordPress.org |accessdate=March 4, 2007 |date=March 2, 2007}}</ref>
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.<ref>{{cite web |archiveurl=https://web.archive.org/web/20120315201030/http://blogsecurity.net/wordpress/articles/article-230507 |url=http://blogsecurity.net/wordpress/articles/article-230507/ |title=Survey Finds Most WordPress Blogs Vulnerable |publisher=Blog Security |archivedate=March 15, 2012 |date=May 23, 2007 |accessdate=June 15, 2010 |deadurl=yes |df=mdy-all }}</ref> In part to mitigate this problem, WordPress made updating the software a much easier, "one click" automated process in version 2.7 (released in December 2008).<ref>{{cite web |url=https://codex.wordpress.org/Updating_WordPress |title=Updating WordPress |publisher=WordPress Codex |deadurl=no |accessdate=September 25, 2012}}</ref> However, the filesystem security settings required to enable the update process can be an additional risk.<ref>{{cite web |url=http://www.realstorygroup.com/Blog/1663-Yet-another-WordPress-release |title=Yet another WordPress release |date=August 13, 2009 |accessdate=September 24, 2012}}</ref>
In a June 2007 interview, Stefan Esser, the founder of the PHP Security Response Team, spoke critically of WordPress' 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.<ref>{{cite web |archiveurl=https://web.archive.org/web/20121013080700/http://blogsecurity.net/wordpress/interview-280607 |url=http://blogsecurity.net/wordpress/interview-280607/ |title=Interview with Stefan Esser |publisher=BlogSecurity |archivedate=October 13, 2012 |date=June 28, 2007 |accessdate=June 15, 2010}}</ref>
In June 2013, it was found that some of the 50 most downloaded WordPress plugins were vulnerable to common Web attacks such as SQL injection and [[Cross-site scripting|XSS]]. A separate inspection of the top-10 e-commerce plugins showed that seven of them were vulnerable.<ref>{{cite web |author=Robert Westervelt |url=http://www.crn.com/news/security/240156883/popular-wordpress-e-commerce-plugins-riddled-with-security-flaws.htm |title=Popular WordPress E-Commerce Plugins Riddled With Security Flaws - Page: 1 |publisher=CRN |date=June 18, 2013 |accessdate=March 11, 2015}}</ref>
In an effort to promote better security, and to streamline the update experience overall, automatic background updates were introduced in WordPress 3.7.<ref>{{cite web |url=https://codex.wordpress.org/Configuring_Automatic_Background_Updates |title=Configuring Automatic Background Updates « WordPress Codex |publisher=Codex.wordpress.org |accessdate=June 30, 2014}}</ref>
Individual installations of WordPress can be protected with security plugins that prevent user enumeration, hide resources and thwart probes. Users can also protect their WordPress installations by taking steps such as keeping all WordPress installation, themes, and plugins updated, using only trusted themes and plugins,<ref>{{cite web |url=http://www.pingable.org/original-free-wordpress-security-infographic-by-pingable/ |title=Original Free WordPress Security Infographic by Pingable |last=Ward |first=Simon |date=July 9, 2012 |publisher=Pingable |accessdate=October 28, 2012}}</ref> editing the site's .htaccess file to prevent many types of SQL injection attacks and block unauthorized access to sensitive files. It is especially important to keep WordPress plugins updated because would-be [[hacker (computer security)|hackers]] can easily list all the plugins a site uses, and then run scans searching for any vulnerabilities against those plugins. If vulnerabilities are found, they may be exploited to allow hackers to upload their own files (such as a PHP Shell script) that collect sensitive information.<ref>{{cite web |url=http://www.rackaid.com/blog/scan-wordpress/ |title=How To Scan WordPress Like A Hacker}}</ref><ref>{{cite web |url=http://pluginforage.com/how-to-quickly-safely-manually-update-wordpress-plugins/ |title=How To Manually Update WordPress Plugins}}</ref><ref>{{cite web |url=http://www.esecurityplanet.com/open-source-security/top-5-wordpress-vulnerabilities-and-how-to-fix-them.html |title=Top 5 WordPress Vulnerabilities and How to Fix Them |date=April 20, 2012 |publisher=eSecurityPlanet.com |accessdate=April 20, 2012}}</ref>
Developers can also use tools to analyze potential vulnerabilities, including WPScan, WordPress Auditor and WordPress Sploit Framework developed by 0pc0deFR. These types of tools research known vulnerabilities, such as a [[Cross-site request forgery|CSRF]], [[Local File Inclusion|LFI]], [[File inclusion vulnerability|RFI]], [[Cross-site scripting|XSS]], SQL injection and user enumeration. However, not all vulnerabilities can be detected by tools, so it is advisable to check the code of plugins, themes and other add-ins from other developers.
In March 2015, it was reported by many security experts and SEOs including Search Engine Land that a [[SEO]] plugin for WordPress called [[Yoast]] which is used by more than 14 million users worldwide has a vulnerability which can lead to an exploit where hackers can do a Blind SQL injection.<ref>Common Vulnerabilities and Exposures [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2292 "CVE-2015-2292"], Retrieved on July 7, 2017</ref><ref>Common Vulnerabilities and Exposures [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2293 "CVE-2015-2293"], Retrieved on July 7, 2017</ref> To fix that issue they immediately introduced a newer version 1.7.4 of the same plugin to avoid any disturbance on web because of the security lapse that the plugin had.<ref>Barry Schwartz [http://searchengineland.com/yoast-wordpress-seo-plugin-vulnerable-to-hackers-216656 "Yoast WordPress SEO Plugin Vulnerable To Hackers"], Retrieved on February 13, 2016.</ref>
In January 2017, security auditors at Sucuri identified a vulnerability in the WordPress [[REST API]] that would allow any unauthenticated user to modify any post or page within a site running WordPress 4.7 or greater. The auditors quietly notified WordPress developers, and within six days WordPress released a high priority patch to version 4.7.2 which addressed the problem.<ref>{{Cite news|url=https://make.wordpress.org/core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/|title=Disclosure of Additional Security Fix in WordPress 4.7.2|date=2017-02-01|newspaper=Make WordPress Core|access-date=2017-02-16|language=en-US}}</ref><ref>{{Cite news|url=https://blog.sucuri.net/2017/02/content-injection-vulnerability-wordpress-rest-api.html|title=Content Injection Vulnerability in WordPress 4.7 and 4.7.1|date=2017-02-01|newspaper=Sucuri Blog|access-date=2017-02-16|language=en-US}}</ref>
[[File:Typical Tor Browser notification of a canvas read attempt.png|thumb|280x280px|The [[canvas fingerprinting]] warning that is typically given by [[Tor Browser]] for WordPress-based websites.]]
WordPress' minimum PHP version requirement is PHP 5.2,<ref>{{cite web |url=https://wordpress.org/about/requirements/ |title=WordPress › About » Requirements |accessdate=December 30, 2015 |website=wordpress.org}}</ref> which was released on January 6, 2006,<ref name="eol">{{cite web |url=http://php.net/eol.php |title=Unsupported Branches |website=php.net |accessdate=November 14, 2015}}</ref> and which has been unsupported by the PHP Group and not received any security patches since January 6, 2011.<ref name="eol" />
In the absence of specific alterations to their default formatting code, WordPress-based websites use the [[canvas element]] to detect whether the browser is able to correctly render [[emoji]]. Because [[Tor (anonymity network)|Tor Browser]] does not currently discriminate between this legitimate use of the [[Canvas (GUI)|Canvas]] [[API]] and an effort to perform [[canvas fingerprinting]], it warns that the website is attempting to 'extract HTML5 canvas image data'. Ongoing efforts seek workarounds to reassure privacy advocates while retaining the ability to check for proper emoji rendering capability. {{Citation needed|reason=Claim needs source for such ongoing efforts|date=October 2018}}
==Development and support==
===Key developers===
[[Matt Mullenweg]] and [[Mike Little]] were cofounders of the project. The core lead developers include Helen Hou-Sandí, Dion Hulse, Mark Jaquith, Matt Mullenweg, Andrew Ozz, and Andrew Nacin.<ref>{{cite web |url=https://wordpress.org/about/ |title=About WordPress |accessdate=March 18, 2015 |publisher=wordpress.org}}</ref><ref>{{cite web |url=https://codex.wordpress.org/Core_Team |title=Core Team |publisher=codex.wordpress.org |accessdate=August 27, 2015}}</ref>
WordPress is also developed by its community, including ''WP testers'', a group of volunteers who test each release.<ref>{{cite web |url= http://simplifyingit.com.au/support/index.php/installing-wordpress/ |title=Installing WordPress |date=August 2014}}</ref> They have early access to [[Neutral build|nightly builds]], beta versions and release candidates. Errors are documented in a special [[mailing list]], or the project's [[Trac]] tool.
Though largely developed by the community surrounding it, WordPress is closely associated with [[Automattic]], the company founded by Matt Mullenweg.<ref>{{cite web |url= https://www.linkedin.com/pulse/billion-dollar-tech-company-offices-email-glenn-leibowitz |title= The Billion-Dollar Tech Company With No Offices or Email |access-date = 17 December 2017 |last= Leibowitz |first= Glenn |date= 17 December 2017 |quote= I recently met with Matt Mullenweg, the creator of WordPress and CEO of Automattic, the company that develops WordPress and offers a range of products and services for WordPress users both large and small. Automattic is valued today at over $1 billion. |website= [[Linkedin]]}}</ref> On September 9, 2010, Automattic handed the WordPress trademark to the newly created WordPress Foundation, which is an umbrella organization supporting WordPress.org (including the software and archives for plugins and themes), [[bbPress]] and [[BuddyPress]].
===WordCamp developer and user conferences===
[[File:WordCamp 2011 Bulgaria.jpg|thumb|right|A WordCamp in [[Sofia]], [[Bulgaria]] (2011)]]
WordCamps are casual, locally organized conferences covering everything related to WordPress.<ref name="WordCamp Central About">{{cite web |url=https://central.wordcamp.org/about/ |title=WordCamp Central > About |publisher=Central.wordcamp.org |accessdate=October 28, 2015}}</ref> The first such event was WordCamp 2006 in August 2006 in [[San Francisco]], which lasted one day and had over 500 attendees.<ref>{{cite web |url=http://2006.wordcamp.org/ |title=WordCamp 2006 |publisher=2006.wordcamp.org |accessdate=December 18, 2011}}</ref><ref>{{cite web |url=http://2011.sf.wordcamp.org/ |title=WordCamp 2011 |publisher=2011.sf.wordcamp.org |accessdate=December 18, 2011}}</ref> The first WordCamp outside San Francisco was held in [[Beijing]] in September 2007.<ref name="wordcamp schedule">{{cite web |url=http://central.wordcamp.org/schedule/ |title=WordCamp Central > Schedule |publisher=Central.wordcamp.org |accessdate=December 18, 2011}}</ref> Since then, there have been over 507 WordCamps in over 207 cities in 48 different countries around the world.<ref name="WordCamp Central About"/> WordCamp San Francisco 2014 was the last official annual conference of WordPress developers and users taking place in San Francisco, having now been replaced with WordCamp US.<ref>{{cite web |url=http://central.wordcamp.org/news/2011/01/24/wordcampsf-not-wordcon/ |title=WordCamp SF Announced (not WordCon) | WordCamp Central |publisher=Central.wordcamp.org |date=January 24, 2011 |accessdate=March 11, 2015}}</ref>
WordPress users who like public speaking can sign up to speak and lead a session.
===Support===
WordPress' primary support website is WordPress.org. This support website hosts both WordPress Codex, the online manual for WordPress and a living repository for WordPress information and documentation,<ref>{{cite web |url=https://codex.wordpress.org/ |title=WordPress Codex |publisher=WordPress.org |accessdate=March 13, 2014}}</ref>
and WordPress Forums, an active online community of WordPress users.<ref>{{cite web |url=https://wordpress.org/support/ |title=WordPress Forums |publisher=WordPress.org |accessdate=March 13, 2014}}</ref>
==See also==
* [[Weblog software]]
* [[List of content management systems]]
* [[WordPress.com]]
{{Portal bar|Free software|Software|IT|Internet}}
==References==
{{Reflist|colwidth=30em}}
==External links==
{{Sisterlinks|d=Q13166|voy=no|commons=Category:WordPress|wikt=no|m=no|mw=no|species=no|q=no|n=no|s=no}}
*{{Official website|https://wordpress.org}}
*{{DMOZ|Computers/Internet/On_the_Web/Weblogs/Templates/WordPress/}}
{{Application frameworks}}
{{Authority control}}
{{DEFAULTSORT:WordPress}}
[[Category:2003 software]]
[[Category:Blog software]]
[[Category:Content management systems]]
[[Category:Free content management systems]]
[[Category:Free software programmed in PHP]]
[[Category:Software forks]]
[[Category:Software using the GPL license]]
[[Category:Website management]]
[[Category:WordPress| ]]
[[Category:Free and open-source Android software]]
{{pp-move-indef}}
{{Use mdy dates|date=March 2016}}
{{Infobox software
| name = WordPress
| logo = [[File:WordPress logo.svg|240px]]
| screenshot = WordPress MP6 dashboard.png
| caption = WordPress Dashboard
| developer = WordPress Foundation
| released = {{start date and age|2003|05|27}}<ref name=release />
| latest release version = <!-- If you update [[Template:Wordpress version]], it will automatically update this page and [[List of content management systems]]--> {{Wordpress version}}
| latest release date = {{Wordpress version|releasedate}}
<!-- To edit the Stable release and/or Preview release fields you click on the [±] at the end of each field -->| programming language = [[PHP]]
| operating system = [[Unix-like]], [[Windows]]
| genre = [[Blog software]], [[Content Management System]], [[Content Management Framework]]
| license = [[GNU General Public License Version 2|GNU GPLv2]]+<ref>{{cite web |url=https://wordpress.org/about/license/ |title=WordPress: About: GPL |publisher=WordPress.org |accessdate=June 15, 2010}}</ref>
| website = {{URL|https://wordpress.org}}
}}
'''WordPress''' is a [[free and open-source software|free and open-source]] [[content management system]] (CMS) based on [[PHP]] and [[MySQL]].<ref>{{cite web |publisher=WordPress |title=WordPress Web Hosting |url=https://wordpress.org/hosting/ |accessdate=May 21, 2013}}</ref> Features include a [[Plug-in (computing)|plugin architecture]] and a [[Web template system|template system]]. It is most associated with [[blog]]ging, but supports other types of web content including more traditional [[Electronic mailing list|mailing lists]] and [[Internet forum|forums]], media galleries, and online stores. Used by more than 60 million websites,<ref>{{cite web |url=https://www.forbes.com/sites/jjcolao/2012/09/05/the-internets-mother-tongue/ |title=With 60 Million Websites, WordPress Rules The Web. So Where's The Money? |last=Coalo |first=J.J |date=September 5, 2012 |work=[[Forbes]] |accessdate=February 3, 2016}}</ref> including 30.6% of the top 10 million websites {{as of|2018|04|lc=y}},<ref name="Usage of content management systems for websites">{{cite web |url=http://w3techs.com/technologies/overview/content_management/all/ |title=Usage Statistics and Market Share of Content Management Systems for Websites |date=April 23, 2018 |publisher=W3Techs | accessdate=April 23, 2018}}</ref><ref>{{cite web |url= https://www.linkedin.com/pulse/billion-dollar-tech-company-offices-email-glenn-leibowitz |title= The Billion-Dollar Tech Company With No Offices or Email |access-date = 17 December 2017 |last= Leibowitz |first= Glenn |date= 17 December 2017 |quote= Right now we power about 24% of all websites as of this recording: that is the largest of any of the content management systems. The number two has around 3%. But we are not happy that we have just 24%, and we see a lot of work to get the remaining 76%. |website= [[Linkedin]]}}</ref> WordPress is the most popular [[website]] management system in use.<ref>{{cite web |accessdate=August 1, 2013 |url=http://trends.builtwith.com/cms |title=CMS Usage Statistics |publisher=BuiltWith}}</ref> WordPress has also been used for other application domains such as [[Digital signage|pervasive display systems]] (PDS).<ref>Amir E. Sarabadani Tafreshi and Moira C. Norrie. 2017. ScreenPress: a powerful and flexible platform for networked pervasive display systems. In Proceedings of the 6th ACM International Symposium on Pervasive Displays (PerDis '17). ACM, New York, NY, USA, Article 13, 8 pages. DOI: https://doi.org/10.1145/3078810.3078813</ref>
WordPress was released on May 27, 2003, by its founders, [[Matt Mullenweg]]<ref name=release>{{cite web |url=https://wordpress.org/news/2003/05/wordpress-now-available/ |title=WordPress Now Available |publisher=WordPress |last=Mullenweg |first=Matt |accessdate=July 22, 2010}}</ref> and [[Mike Little]],<ref name=release_commit>{{cite web |url=https://core.trac.wordpress.org/changeset/8 |title=Commit number 8 |accessdate=February 3, 2016}}</ref><ref>{{cite web|last1=Patterson|first1=Dan|title=WordPress "quietly" powers 27% of the web|url=https://www.techrepublic.com/article/wordpress-quietly-powers-27-percent-of-the-web/|website=www.techrepublic.com|accessdate=16 December 2017}}</ref> as a [[Fork (software development)|fork]] of ''b2/cafelog''. The software is released under the [[GNU General Public License#Version_2|GPLv2]] (or later) license.<ref>{{cite web |url=https://wordpress.org/about/license/ |title=WordPress › About » License |publisher=WordPress.org |accessdate=June 30, 2014}}</ref>
To function, WordPress has to be installed on a [[web server]], either part of an [[Internet hosting service]] like [[WordPress.com]] or a computer running the software package WordPress.org in order to serve as a [[Host (network)|network host]] in its own right.<ref>{{cite web |url=https://en.support.wordpress.com/com-vs-org/ |title=Support disaggregating WordPress.com and WordPress.org |publisher=WordPress.com |accessdate=January 7, 2016}}</ref> A local computer may be used for single-user testing and learning purposes.
==Overview==
WordPress has a [[web template system]] using a [[template processor]]. Its architecture is a [[front controller]], routing all requests for non-static [[Uniform Resource Identifier|URI]]<nowiki/>s to a single PHP file which parses the URI and identifies the target page. This allows support for more human-readable [[permalink]]s.<ref>{{Cite news|url=https://wpshout.com/wordpress-front-controller/|title=WordPress and the Front Controller Design Pattern {{!}} WPShout|date=2014-02-11|newspaper=WPShout|access-date=2017-02-15|language=en-US}}</ref>
===Themes===
WordPress users may install and switch among different [[Theme (computing)|themes]]. Themes allow users to change the look and functionality of a WordPress website without altering the core code or site content. Every WordPress website requires at least one theme to be present and every theme should be designed using WordPress standards with structured [[PHP]], valid [[HTML]] (HyperText Markup Language), and [[Cascading Style Sheets]] (CSS). Themes may be directly installed using the WordPress "Appearance" administration tool in the dashboard, or theme folders may be copied directly into the themes directory, for example via [[File Transfer Protocol|FTP]].<ref>{{cite web |url=https://codex.wordpress.org |title=Theme Installation |publisher=Codex.wordpress.org |date=April 9, 2013 |accessdate=April 26, 2013}}</ref> The [[PHP]], [[HTML]] and [[Cascading Style Sheets|CSS]] found in themes can be directly modified to alter theme behavior, or a theme can be a "child" theme which inherits settings from another theme and selectively overrides features.<ref>{{Cite web|url=https://codex.wordpress.org/Child_Themes|title=Child Themes « WordPress Codex|website=codex.wordpress.org|language=en|access-date=2017-02-15}}</ref> WordPress themes are generally classified into two categories: free and premium. Many free themes are listed in the WordPress theme directory, and premium themes are available for purchase from marketplaces and individual WordPress developers. WordPress users may also create and develop their own custom themes. The free theme Underscores created by the WordPress developers has become a popular basis for new themes.<ref>{{cite web |url=https://wptavern.com/introduction-to-underscores-a-wordpress-starter-theme-with-konstantin-obenland |title=Introduction To Underscores: A WordPress Starter Theme With Konstantin Obenland |author=Jeff Chandler |date=April 3, 2014 |accessdate=July 31, 2016}}</ref>
===Plugins===
WordPress' [[plugin (computing)|plugin]] architecture allows users to extend the features and functionality of a website or blog. As of March 2017, WordPress has over 55,286 plugins available,<ref>{{cite web |url=https://wordpress.org/plugins/ |title=WordPress > WordPress Plugins |publisher=WordPress.org |accessdate=March 2, 2017}}</ref> each of which offers custom functions and features enabling users to tailor their sites to their specific needs. These customizations range from [[search engine optimization]], to [[client portal]]s used to display private information to logged in users, to content management systems, to content displaying features, such as the addition of [[GUI widget|widgets]] and [[navigation bar]]s. Not all available plugins are always abreast with the upgrades and as a result they may not function properly or may not function at all. Most plugins are available through WordPress themselves, either via downloading them and installing the files manually via FTP or through the WordPress dashboard. However, many third parties offer plugins through their own websites, many of which are paid packages.
Web developers who wish to develop plugins need to learn WordPress' hook system which consists of over 300 hooks divided into two categories: action hooks and filter hooks.
===Mobiles===
Native applications exist for [[WebOS]],<ref>{{cite web |url=https://webos.wordpress.org/ |title=WordPress for WebOS |work=WordPress |accessdate=March 6, 2012}}</ref> [[Android (operating system)|Android]],<ref>{{cite web |url=http://androidandme.com/2010/02/news/wordpress-publishes-native-android-application/ |title=WordPress publishes native Android application |publisher=Android and Me |date=February 2, 2010 |accessdate=June 15, 2010}}</ref> [[iOS]] (iPhone, iPod Touch, iPad),<ref name="altafsayani">{{cite web |url=http://www.altafsayani.com/2008/07/12/wordpress-app-for-iphone-and-ipod-touch/ |title=Idea: WordPress App For iPhone and iPod Touch |work=WordPress iPhone & iPod Touch |date=July 12, 2008 |accessdate=February 9, 2016}}</ref><ref name="post">{{cite news|url=https://readwrite.com/2011/03/23/18_million_wordpress_blogs_land_on_the_ipad/|title=18 Million WordPress Blogs Land on the iPad|last=|first=|date=March 24, 2011|work=ReadWriteWeb|access-date=|archive-url=|archive-date=|dead-url=}}</ref> [[Windows Phone]], and [[BlackBerry]].<ref>{{cite web |url=https://blackberry.wordpress.org/ |title=WordPress for BlackBerry |work=WordPress |accessdate=December 27, 2009 |deadurl=yes |archiveurl=http://arquivo.pt/wayback/20131106094925/http://blackberry.wordpress.org/ |archivedate=November 6, 2013 |df=mdy-all }}</ref> These applications, designed by [[Automattic]], have options such as adding new blog posts and pages, commenting, moderating comments, replying to comments in addition to the ability to view the stats.<ref name="altafsayani" /><ref name="post" />
===Other features===
WordPress also features integrated link management; a [[Web search engine|search engine]]–friendly, clean [[permalink]] structure; the ability to assign multiple categories to posts; and support for [[Tag (metadata)|tagging]] of posts. Automatic filters are also included, providing standardized formatting and styling of text in posts (for example, converting regular quotes to [[Quotation marks in English#Smart quotes|smart quotes]]). WordPress also supports the [[Trackback]] and [[Pingback]] standards for displaying links to other sites that have themselves linked to a post or an article. WordPress posts can be edited in HTML, using the visual editor, or using one of a number of plugins that allow for a variety of customized editing features.
==Multi-user and multi-blogging==
Prior to version 3, WordPress supported one blog per installation, although multiple concurrent copies may be run from different directories if configured to use separate database tables. WordPress Multisites (previously referred to as WordPress Multi-User, WordPress MU, or WPMU) was a fork of WordPress created to allow multiple blogs to exist within one installation but is able to be administered by a centralized maintainer. WordPress MU makes it possible for those with websites to host their own blogging communities, as well as control and moderate all the blogs from a single dashboard. WordPress MS adds eight new data tables for each blog.
As of the release of WordPress 3, WordPress MU has merged with WordPress.<ref>{{cite web |url=https://wordpress.org/development/2010/06/thelonious/ |title=WordPress 3.0 "Thelonious" |publisher=WordPress.org |date=June 17, 2010 |accessdate=December 18, 2011}}</ref>
==History==
''b2/cafelog'', more commonly known as ''b2'' or ''cafelog'', was the precursor to WordPress.<ref>{{cite video |people=Andrew Warner, [[Matt Mullenweg]] |date=September 10, 2009 |title=The Biography Of WordPress – With Matt Mullenweg |url=http://mixergy.com/the-biography-of-wordpress-with-matt-mullenweg/ |format=[[MPEG-4 Part 14]] |medium=Podcast |publisher=Mixergy |accessdate=September 28, 2009 |time=10:57 |quote=b2 had actually, through a series of circumstances, essentially become abandoned.}}</ref>
b2/cafelog was estimated to have been installed on approximately 2,000 blogs as of May 2003.<ref>{{cite web |last=Valdrighi |first=Michel |title=b2 test weblog - post dated 23.05.03 |url=http://cafelog.com/index.php?p=500 |accessdate=May 9, 2013}}</ref> 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 (software development)|fork]] of b2.<ref>{{cite web |url=https://codex.wordpress.org/History |title=History - WordPress Codex |accessdate=March 29, 2012 |publisher=WordPress.org}}</ref> Christine Selleck Tremoulet, a friend of Mullenweg, suggested the name ''WordPress''.<ref>{{cite web |url=http://blog.chron.com//techblog/2008/01/the-importance-of-being-matt/ |title=The importance of being Matt |author=Silverman, Dwight |publisher=Houston Chronicle |date=January 24, 2008 |accessdate=August 14, 2014}}</ref><ref>{{cite web |url=http://www.bigpinkcookie.com/2008/01/24/the-importance-of-being-matt/ |title=The Importance of Being Matt… |author=Tremoulet, Christine Selleck |publisher=Christine Selleck Tremoulet |date=January 24, 2008 |accessdate=March 29, 2012}}</ref>
In 2004 the licensing terms for the competing [[Movable Type]] package were changed by [[Six Apart]], resulting in many of its most influential users migrating to WordPress.<ref>{{cite web |url=http://www.salon.com/2004/08/09/six_apart/ |title=Blogging grows up |author=Manjoo, Farhad |publisher=Salon |date=August 9, 2004 |accessdate=March 29, 2012}}</ref><ref>{{cite web |archiveurl=https://web.archive.org/web/20060410125402/http://diveintomark.org/archives/2004/05/14/freedom-0 |url=http://diveintomark.org/archives/2004/05/14/freedom-0 |title=Freedom 0 |author=Pilgrim, Mark |publisher=Mark Pilgrim |archivedate=April 10, 2006 |date=May 14, 2004 |accessdate=March 29, 2012 |deadurl=yes |df=mdy-all }}</ref>
By October 2009 the Open Source CMS MarketShare Report concluded that WordPress enjoyed the greatest brand strength of any open-source content management system.
As of February 2017, WordPress is used by 58.7% of all the websites whose content management system is known. This is 27.5% of the top 10 million websites.<ref name="Usage of content management systems for websites" /><ref>{{Cite news|url=https://www.theregister.co.uk/2018/03/05/wordpress_is_now_30_per_cent_of_the_web/|title=WordPress is now 30 per cent of the web, daylight second|access-date=2018-03-20|language=en}}</ref>
===Awards and recognition===
*Winner of [[Infoworld]]'s "Best of open source software awards: Collaboration", awarded in 2008.<ref name="award 2008">{{cite web | title = Best of open source software awards: Collaboration | publisher = infoworld.com | url = https://www.infoworld.com/article/2638571/techology-business/best-of-open-source-software-awards--collaboration.html | accessdate = 2017-12-16 }}</ref>
*Winner of Open Source CMS Awards's "Overall Best Open Source CMS", awarded in 2009.<ref name="Open Source CMS 2009">{{cite web | title = WordPress wins top prize in 2009 Open Source CMS Awards | publisher = cmscritic.com | url = https://www.cmscritic.com/wordpress-wins-top-prize-in-2009-open-source-cms-awards/ | accessdate = 2017-12-16 }}</ref>
*Winner of digitalsynergy's "Hall of Fame CMS category in the 2010 Open Source", awarded in 2010.<ref name="bossie 2010">{{cite web | title = Hall of Fame CMS | publisher = digitalsynergy.ca | url = http://www.digitalsynergy.ca/library/wordpress-wins-hall-of-fame-cms-award/ | accessdate = 2017-12-16 }}</ref>
*Winner of [[Infoworld]]'s "Bossie award for Best Open Source Software", awarded in 2011.<ref name="bossie 2011">{{cite web | title = WordPress wins Bossie Awards 2011: The best open source applications | publisher = wprockers.com | url = http://wprockers.com/wordpress-wins-bossie-awards-2011-the-best-open-source-applications-1610.html | accessdate = 2017-12-16 }}</ref>
*Winner of CMS Critic Award's "Best CMS for Personal Websites", awarded in 2015.<ref name="CMS 2015">{{cite web | title = CMS Critic Awards Home 2015 Winners | publisher = cmscritic.com | url = https://www.cmscritic.com/awards/2015-winners/ | accessdate = 2017-12-16 }}</ref>
*Wordpress has a five star [[privacy]] rating from the [[Electronic Frontier Foundation]].<ref>{{cite web|url=https://www.eff.org/who-has-your-back-2017|title=Who Has Your Back? Government Data Requests 2017}}</ref>
===Release history===
Main releases of WordPress are codenamed after well-known [[jazz]] musicians, starting from version 1.0.<ref>{{cite web|last1=hollander|first1=Roel|title=Fun Fact: Wordpress Jazz Tributes|url=https://roelhollander.eu/en/blog-other-articles/wordpress-jazz-tributes/|website=roelhollander.eu|accessdate=16 December 2017}}</ref><ref>{{cite web |url=https://wordpress.org/about/roadmap/ |title=Roadmap |work=Blog |publisher=WordPress.org |accessdate=June 15, 2010}}</ref>
<!--Template:Version - for version & release history. Documentation & examples: -->
{{Version |t |show=11111}}
{| class="wikitable"
! Version
! Code name
! Release date
! Notes
|-
! {{Version |o |0.7}}
| none
| May 27, 2003<ref>{{cite web |url=https://wordpress.org/news/2003/05/wordpress-now-available/ |title=WordPress Blog: WordPress 0.7 |publisher=WordPress.org |accessdate=May 27, 2003}}</ref>
| Used the same file structure as its predecessor, ''b2/cafelog'', and continued the numbering from its last release, 0.6.<ref>{{cite web |url=http://cafelog.com/ |title=Cafelog |accessdate=May 15, 2011}}</ref> Only 0.71-gold is available for download in the official WordPress Release Archive page.
|-
! {{Version |o |1.0}}
| ''[[Miles Davis|Davis]]''
| January 3, 2004<ref>{{cite web |url=https://wordpress.org/news/2004/01/wordpress-10/ |title=WordPress Blog: WordPress 1.0 |publisher=WordPress.org |accessdate=January 3, 2004}}</ref>
| Added search engine friendly permalinks, multiple categories, dead simple installation and upgrade, comment moderation, XFN support, Atom support.
|-
! {{Version |o |1.2}}
| ''[[Charles Mingus|Mingus]]''
| May 22, 2004<ref>{{cite web |url=https://wordpress.org/news/2004/05/heres-the-beef/ |title=WordPress Blog: WordPress 1.2 |publisher=WordPress.org |accessdate=May 22, 2004}}</ref>
| Added support of Plugins; which same identification headers are used unchanged in WordPress releases {{as of|2011|lc=y}}.
|-
! {{Version |o |1.5}}
|''[[Billy Strayhorn|Strayhorn]]''
| February 17, 2005<ref>{{cite web |url=https://wordpress.org/news/2005/02/strayhorn/ |title=WordPress Blog: WordPress 1.5 |publisher=WordPress.org |accessdate=February 17, 2005}}</ref>
| Added a range of vital features, such as ability to manage static pages and a template/Theme system. It was also equipped with a new default template (code named ''[[Stanley Kubrick|Kubrick]]'').<ref>{{cite web |url=http://binarybonsai.com/kubrick |title=Kubrick at Binary Bonsai |publisher=Binarybonsai.com |accessdate=June 15, 2010}}</ref> designed by Michael Heilemann.
|-
| colspan="4" |
|-
! {{Version |o |2.0}}
| ''[[Duke Ellington|Duke]]''
| December 31, 2005<ref>{{cite web |url=https://wordpress.org/news/2005/12/wp2/ |title=WordPress Blog: WordPress 2.0 |publisher=WordPress.org |accessdate=December 31, 2005}}</ref>
| Added rich editing, better administration tools, image uploading, faster posting, improved import system, fully overhauled the back end, and various improvements to Plugin developers.
|-
! {{Version |o |2.1}}
| ''[[Ella Fitzgerald|Ella]]''
| January 22, 2007<ref>{{cite web |url=https://wordpress.org/news/2007/01/ella-21/ |title=WordPress Blog: WordPress 2.1 |publisher=WordPress.org |accessdate=January 22, 2007}}</ref>
| Corrected security issues, redesigned interface, enhanced editing tools (including integrated spell check and auto save), and improved content management options.
|-
! {{Version |o |2.2}}
| ''[[Stan Getz|Getz]]''
| May 16, 2007<ref>{{cite web |url=https://wordpress.org/news/2007/05/wordpress-22/ |title=WordPress Blog: WordPress 2.2 |publisher=WordPress.org |accessdate=May 16, 2007}}</ref>
| Added widget support for templates, updated [[Atom (standard)|Atom]] feed support, and speed optimizations.
|-
! {{Version |o |2.3}}
| ''[[Dexter Gordon|Dexter]]''
| style="white-space: nowrap;"| September 24, 2007<ref>{{cite web |url=https://wordpress.org/news/2007/09/wordpress-23/ |title=WordPress Blog: WordPress 2.3 |publisher=WordPress.org |accessdate=September 24, 2007}}</ref>
| Added native tagging support, new [[Taxonomy (general)|taxonomy]] system for categories, and easy notification of updates, fully supports Atom 1.0, with the publishing protocol, and some much needed security fixes.
|-
! {{Version |o |2.5}}
| ''[[Michael Brecker|Brecker]]''
| March 29, 2008<ref>{{cite web |url=https://wordpress.org/news/2008/03/wordpress-25-brecker/ |title=WordPress Blog: WordPress 2.5 |publisher=WordPress.org |accessdate=March 29, 2008}}</ref>
| Major revamp to the dashboard, dashboard widgets, multi-file upload, extended search, improved editor, improved plugin system and more.
|-
! {{Version |o |2.6}}
| ''[[McCoy Tyner|Tyner]]''
| July 15, 2008<ref>{{cite web |url=https://wordpress.org/news/2008/07/wordpress-26-tyner/ |title=WordPress Blog: WordPress 2.6 |publisher=WordPress.org |accessdate=June 15, 2008}}</ref>
| Added new features that made WordPress a more powerful CMS: it can now [[revision control|track changes]] to every post and page and allow easy posting from anywhere on the web.
|-
! {{Version |o |2.7}}
| ''[[John Coltrane|Coltrane]]''
| December 11, 2008<ref>{{cite web |url=https://wordpress.org/news/2008/12/coltrane/ |title=WordPress Blog: WordPress 2.7 |publisher=WordPress.org |accessdate=December 11, 2008}}</ref>
| Administration interface redesigned fully, added automatic upgrades and installing plugins, from within the administration interface.
|-
! {{Version |o |2.8}}
| ''[[Chet Baker|Baker]]''
| June 10, 2009<ref>{{cite web |url=https://wordpress.org/news/2009/06/wordpress-28/ |title=WordPress Blog: WordPress 2.8 |publisher=WordPress.org |accessdate=June 10, 2009}}</ref>
| Added improvements in speed, automatic installing of themes from within administration interface, introduces the CodePress editor for [[syntax highlighting]] and a redesigned widget interface.
|-
! {{Version |o |2.9}}
| ''[[Carmen McRae|Carmen]]''
| December 19, 2009<ref>{{cite web |url=https://wordpress.org/news/2009/12/wordpress-2-9/ |title=WordPress Blog: WordPress 2.9 |publisher=WordPress.org |accessdate=December 19, 2009}}</ref>
| Added global undo, built-in image editor, batch plugin updating, and many less visible tweaks.
|-
| colspan="4" |
|-
! {{Version |o |3.0}}
| ''[[Thelonious Monk|Thelonious]]''
| June 17, 2010<ref>{{cite web |url=https://wordpress.org/news/2010/06/thelonious/ |title=WordPress Blog: WordPress 3.0 |publisher=WordPress.org |accessdate=June 17, 2010}}</ref>
| Added a new theme [[application programming interface|API]]s, merge WordPress and WordPress MU, creating the new multi-site functionality, new default theme "Twenty Ten" and a refreshed, lighter admin UI.
|-
! {{Version |o |3.1}}
| ''[[Django Reinhardt|Reinhardt]]''
| February 23, 2011<ref>{{cite web |url=https://wordpress.org/news/2011/02/threeone/ |title=WordPress Blog: WordPress 3.1 |publisher=WordPress.org |accessdate=February 25, 2011}}</ref>
| Added the Admin Bar, which is displayed on all blog pages when an admin is logged in, and Post Format, best explained as a Tumblr like micro-blogging feature. It provides easy access to many critical functions, such as comments and updates. Includes internal linking abilities, a newly streamlined writing interface, and many other changes.
|-
! {{Version |o |3.2}}
| ''[[George Gershwin|Gershwin]]''
| July 4, 2011<ref>{{cite web |url=https://wordpress.org/news/2011/07/gershwin/ |title=WordPress Blog: WordPress 3.2 |publisher=WordPress.org |accessdate=June 4, 2011}}</ref>
| Focused on making WordPress faster and lighter. Released only four months after version 3.1, reflecting the growing speed of development in the WordPress community.
|-
! {{Version |o |3.3}}
| ''[[Sonny Stitt|Sonny]]''
| December 12, 2011<ref>{{cite web |url=https://wordpress.org/news/2011/12/sonny/ |title=WordPress Blog: WordPress 3.3 |publisher=WordPress.org |accessdate=December 12, 2011}}</ref>
| Focused on making WordPress friendlier for beginners and [[tablet computer]] users.
|-
! {{Version |o |3.4}}
| ''[[Grant Green|Green]]''
| June 13, 2012<ref>{{cite web |url=https://wordpress.org/news/2012/06/green/ |title=WordPress Blog: WordPress 3.4 |publisher=WordPress.org |accessdate=June 13, 2012}}</ref>
| Focused on improvements to theme customization, [[Twitter]] integration and several minor changes.
|-
! {{Version |o |3.5}}
| ''[[Elvin Jones|Elvin]]''
| December 11, 2012<ref>{{cite web |url=https://wordpress.org/news/2012/12/elvin/ |title=WordPress Blog: WordPress 3.5 |publisher=WordPress.org |accessdate=December 11, 2012}}</ref>
| Support for the [[Retina Display]], color picker, new default theme "Twenty Twelve", improved image workflow.
|-
! {{Version |o |3.6}}
| ''[[Oscar Peterson|Oscar]]''
| August 1, 2013<ref>{{cite web |url=https://wordpress.org/news/2013/08/oscar/ |title=WordPress Blog: WordPress 3.6 |publisher=WordPress.org |accessdate=August 1, 2013}}</ref>
| New default theme "Twenty Thirteen", admin enhancements, post formats UI update, menus UI improvements, new revision system, autosave and post locking.
|-
! {{Version |co |3.7}}
| ''[[Count Basie|Basie]]''
| October 24, 2013<ref>{{cite web |url=https://wordpress.org/news/2013/10/basie/ |title=WordPress Blog: WordPress 3.7 |publisher=WordPress.org |accessdate=October 24, 2013}}</ref>
| Automatically apply maintenance and security updates in the background, stronger password recommendations, support for automatically installing the right language files and keeping them up to date.
|-
! {{Version |co |3.8}}
| ''[[Charlie Parker|Parker]]''
| December 12, 2013<ref>{{cite web |url=https://wordpress.org/news/2013/12/parker/ |title=WordPress Blog: WordPress 3.8 |publisher=WordPress.org |accessdate=December 12, 2013}}</ref>
| Improved admin interface, responsive design for mobile devices, new typography using [[Open Sans]], admin color schemes, redesigned theme management interface, simplified main dashboard, "Twenty Fourteen" magazine style default theme, second release using "Plugin-first development process".
|-
! {{Version |co |3.9}}
| ''[[Jimmy Smith (musician)|Smith]]''
| April 16, 2014<ref>{{cite web |url=https://wordpress.org/news/2014/04/smith/ |title=WordPress Blog: WordPress 3.9 |publisher=WordPress.org |accessdate=April 16, 2014}}</ref>
| Improvements to editor for media, live widget and header previews, new theme browser.
|-
| colspan="4" |
|-
! {{Version |co |4.0}}
| ''[[Benny Goodman|Benny]]''
| September 4, 2014<ref>{{cite web |url=https://wordpress.org/news/2014/09/benny/ |title=WordPress Blog: WordPress 4.0 |publisher=WordPress.org |accessdate=September 4, 2014}}</ref>
| Improved media management, embeds, writing interface, easy language change, theme customizer, plugin discovery and compatibility with [[PHP]] 5.5 and [[MySQL]] 5.6.<ref>{{cite web |url=http://www.suntecoss.com/blog/learn-whats-new-in-wordpress-v4-0 |title=Learn What’s New in WordPress v4.0 |accessdate=March 14, 2016}}</ref>
|-
! {{Version |co|4.1}}
| ''[[Dinah Washington|Dinah]]''
| December 18, 2014<ref name="wordpress1">{{cite web |url=https://wordpress.org/news/2014/12/dinah/ |title=WordPress Blog: WordPress 4.1 |publisher=WordPress.org |accessdate=December 18, 2014}}</ref>
| Twenty Fifteen as the new default theme, distraction-free writing, easy language switch, Vine embeds and plugin recommendations.
|-
! {{Version |co |4.2}}
| ''[[Bud Powell|Powell]]''
| April 23, 2015<ref>{{cite web |url=https://wordpress.org/news/2015/04/powell/ |title=WordPress Blog: WordPress 4.2 |publisher=WordPress.org |accessdate=April 23, 2015}}</ref>
| New "Press This" features, improved characters support, emoji support, improved customizer, new embeds and updated plugin system.
|-
! {{Version |co |4.3}}
| ''[[Billie Holiday|Billie]]''
| August 18, 2015<ref>{{cite web |url=https://wordpress.org/news/2015/08/billie/ |title=WordPress Blog: WordPress 4.3 |publisher=WordPress.org |accessdate=August 18, 2015}}</ref>
| Focus on mobile experience, better passwords and improved customizer.
|-
! {{Version |co |4.4}}
| ''[[Clifford Brown|Clifford]]''
| December 8, 2015<ref>{{cite web |url=https://wordpress.org/news/2015/12/clifford |title=WordPress Blog: WordPress 4.4 |publisher=WordPress.org |accessdate=December 8, 2015}}</ref>
| Introduction of "Twenty Sixteen" theme, and improved responsive images and embeds.
|-
! {{Version |co |4.5}}
| ''[[Ornette Coleman|Coleman]]''
| April 12, 2016<ref>{{cite web |url=https://wordpress.org/news/2016/04/coleman/ |title=WordPress Blog: WordPress 4.5|publisher=WordPress.org|accessdate=April 26, 2016}}</ref>
| Added inline linking, formatting shortcuts, live responsive previews, and other updates under the hood.
|-
|-
! {{Version |co |4.6}}
| ''[[Pepper Adams|Pepper]]''
| August 16, 2016<ref>{{cite web |url=https://wordpress.org/news/2016/08/pepper/ |title=WordPress Blog: WordPress 4.6 |publisher=WordPress.org|accessdate=August 16, 2016}}</ref>
| Added streamlined updates, native fonts, editor improvements with inline link checker and content recovery, and other updates under the hood.
|-
|-
! {{Version |co |4.7}}
| ''[[Sarah Vaughan|Vaughan]]''
| December 6, 2016<ref>{{cite web |url=https://wordpress.org/news/2016/12/vaughan/ |title=WordPress Blog: WordPress 4.7 "Vaughan" |publisher=WordPress.org|accessdate=December 7, 2016}}</ref>
| Comes with new default theme "Twenty Seventeen", Video Header Support, PDF preview, custom CSS in live preview, editor Improvements, and other updates under the hood.
|-
|-
! {{Version |co |4.8}}
| ''[[Bill Evans|Evans]]''
| June 8, 2017<ref>{{cite web |url=https://make.wordpress.org/core/4-8/ |title=Version 4.8 – Make WordPress Core |publisher=WordPress.org |accessdate=August 1, 2017}}</ref>
| The next-generation editor. Additional specific goals include the TinyMCE inline element / link boundaries, new media widgets, WYSIWYG in text widget. End Support for Internet Explorer Versions 8, 9, and 10.
|-
|-
! {{Version |c |4.9}}
| ''[[Billy Tipton|Tipton]]''
| November 16, 2017<ref>{{cite web |url=https://make.wordpress.org/core/4-9/ |title=Version 4.9 – Make WordPress Core |publisher=WordPress.org |accessdate=August 6, 2017}}</ref>
| Improved theme customizer experience, including scheduling, frontend preview links, autosave revisions, theme browsing, improved menu functions, and syntax highlighting. Added new gallery widget and updated text and video widgets. Theme editor gives warnings and rollbacks when saving files that produce fatal errors.<ref>{{cite web |url=https://wordpress.org/news/2017/10/wordpress-4-9-beta-1/ |title=WordPress Blog: WordPress 4.9 Beta 1|publisher=WordPress.org|accessdate=October 25, 2017}}</ref>
|-
| colspan="4" |
|-
! {{Version |p |5.0}}
|[[Johannes Gutenberg|''Gutenberg'']]
| November 19, 2018
| WordPress 5.0 will be the first "major" release of 2018, including the new editor, code-named "Gutenberg".
|-
|}
==Future==
Matt Mullenweg has stated that the future of WordPress is in social, mobile, and as an application platform.<ref>{{cite web |url=http://ma.tt/2012/05/simpler/ |title=Radically Simplified WordPress |publisher=Ma.tt |accessdate=March 11, 2015}}</ref><ref>{{cite web |url=http://wordpress.tv/2013/07/29/matt-mullenweg-state-of-the-word-2013/ |title=Matt Mullenweg: State of the Word 2013 |publisher=WordPress.tv |accessdate=March 11, 2015}}</ref>
==Vulnerabilities==
Many security issues<ref>{{cite web |date=June 28, 2007 |title=David Kierznowski |url=http://blogsecurity.net/wordpress/interview-280607/ |publisher=Blogsecurity.net |archiveurl=https://web.archive.org/web/20120309013608/http://blogsecurity.net/wordpress/interview-280607 |archivedate=March 9, 2012 |accessdate=February 17, 2016}}</ref> have been uncovered in the software, particularly in 2007, 2008, and 2015. According to [[Secunia]], WordPress in April 2009 had seven unpatched security advisories (out of 32 total), with a maximum rating of "Less Critical". Secunia maintains an up-to-date list of WordPress vulnerabilities.<ref>{{cite web |url=https://secuniaresearch.flexerasoftware.com/community/advisories/54803 |title=Secunia WordPress Vulnerability Report |publisher=Secunia.com |accessdate=September 13, 2013}}</ref>
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.<ref>{{cite web |url=http://www.threadwatch.org/node/11333 |title=WordPress Exploit Nails Big Name Seo Bloggers |publisher=Threadwatch.org |accessdate=December 18, 2011}}</ref> A separate vulnerability on one of the project site's [[web server]]s allowed an attacker to introduce exploitable code in the form of a [[Backdoor (computing)|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.<ref>{{cite web |url=https://wordpress.org/development/2007/03/upgrade-212/ |title=WordPress 2.1.1 dangerous, Upgrade to 2.1.2 |publisher=WordPress.org |accessdate=March 4, 2007 |date=March 2, 2007}}</ref>
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.<ref>{{cite web |archiveurl=https://web.archive.org/web/20120315201030/http://blogsecurity.net/wordpress/articles/article-230507 |url=http://blogsecurity.net/wordpress/articles/article-230507/ |title=Survey Finds Most WordPress Blogs Vulnerable |publisher=Blog Security |archivedate=March 15, 2012 |date=May 23, 2007 |accessdate=June 15, 2010 |deadurl=yes |df=mdy-all }}</ref> In part to mitigate this problem, WordPress made updating the software a much easier, "one click" automated process in version 2.7 (released in December 2008).<ref>{{cite web |url=https://codex.wordpress.org/Updating_WordPress |title=Updating WordPress |publisher=WordPress Codex |deadurl=no |accessdate=September 25, 2012}}</ref> However, the filesystem security settings required to enable the update process can be an additional risk.<ref>{{cite web |url=http://www.realstorygroup.com/Blog/1663-Yet-another-WordPress-release |title=Yet another WordPress release |date=August 13, 2009 |accessdate=September 24, 2012}}</ref>
In a June 2007 interview, Stefan Esser, the founder of the PHP Security Response Team, spoke critically of WordPress' 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.<ref>{{cite web |archiveurl=https://web.archive.org/web/20121013080700/http://blogsecurity.net/wordpress/interview-280607 |url=http://blogsecurity.net/wordpress/interview-280607/ |title=Interview with Stefan Esser |publisher=BlogSecurity |archivedate=October 13, 2012 |date=June 28, 2007 |accessdate=June 15, 2010}}</ref>
In June 2013, it was found that some of the 50 most downloaded WordPress plugins were vulnerable to common Web attacks such as SQL injection and [[Cross-site scripting|XSS]]. A separate inspection of the top-10 e-commerce plugins showed that seven of them were vulnerable.<ref>{{cite web |author=Robert Westervelt |url=http://www.crn.com/news/security/240156883/popular-wordpress-e-commerce-plugins-riddled-with-security-flaws.htm |title=Popular WordPress E-Commerce Plugins Riddled With Security Flaws - Page: 1 |publisher=CRN |date=June 18, 2013 |accessdate=March 11, 2015}}</ref>
In an effort to promote better security, and to streamline the update experience overall, automatic background updates were introduced in WordPress 3.7.<ref>{{cite web |url=https://codex.wordpress.org/Configuring_Automatic_Background_Updates |title=Configuring Automatic Background Updates « WordPress Codex |publisher=Codex.wordpress.org |accessdate=June 30, 2014}}</ref>
Individual installations of WordPress can be protected with security plugins that prevent user enumeration, hide resources and thwart probes. Users can also protect their WordPress installations by taking steps such as keeping all WordPress installation, themes, and plugins updated, using only trusted themes and plugins,<ref>{{cite web |url=http://www.pingable.org/original-free-wordpress-security-infographic-by-pingable/ |title=Original Free WordPress Security Infographic by Pingable |last=Ward |first=Simon |date=July 9, 2012 |publisher=Pingable |accessdate=October 28, 2012}}</ref> editing the site's .htaccess file to prevent many types of SQL injection attacks and block unauthorized access to sensitive files. It is especially important to keep WordPress plugins updated because would-be [[hacker (computer security)|hackers]] can easily list all the plugins a site uses, and then run scans searching for any vulnerabilities against those plugins. If vulnerabilities are found, they may be exploited to allow hackers to upload their own files (such as a PHP Shell script) that collect sensitive information.<ref>{{cite web |url=http://www.rackaid.com/blog/scan-wordpress/ |title=How To Scan WordPress Like A Hacker}}</ref><ref>{{cite web |url=http://pluginforage.com/how-to-quickly-safely-manually-update-wordpress-plugins/ |title=How To Manually Update WordPress Plugins}}</ref><ref>{{cite web |url=http://www.esecurityplanet.com/open-source-security/top-5-wordpress-vulnerabilities-and-how-to-fix-them.html |title=Top 5 WordPress Vulnerabilities and How to Fix Them |date=April 20, 2012 |publisher=eSecurityPlanet.com |accessdate=April 20, 2012}}</ref>
Developers can also use tools to analyze potential vulnerabilities, including WPScan, WordPress Auditor and WordPress Sploit Framework developed by 0pc0deFR. These types of tools research known vulnerabilities, such as a [[Cross-site request forgery|CSRF]], [[Local File Inclusion|LFI]], [[File inclusion vulnerability|RFI]], [[Cross-site scripting|XSS]], SQL injection and user enumeration. However, not all vulnerabilities can be detected by tools, so it is advisable to check the code of plugins, themes and other add-ins from other developers.
In March 2015, it was reported by many security experts and SEOs including Search Engine Land that a [[SEO]] plugin for WordPress called [[Yoast]] which is used by more than 14 million users worldwide has a vulnerability which can lead to an exploit where hackers can do a Blind SQL injection.<ref>Common Vulnerabilities and Exposures [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2292 "CVE-2015-2292"], Retrieved on July 7, 2017</ref><ref>Common Vulnerabilities and Exposures [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2293 "CVE-2015-2293"], Retrieved on July 7, 2017</ref> To fix that issue they immediately introduced a newer version 1.7.4 of the same plugin to avoid any disturbance on web because of the security lapse that the plugin had.<ref>Barry Schwartz [http://searchengineland.com/yoast-wordpress-seo-plugin-vulnerable-to-hackers-216656 "Yoast WordPress SEO Plugin Vulnerable To Hackers"], Retrieved on February 13, 2016.</ref>
In January 2017, security auditors at Sucuri identified a vulnerability in the WordPress [[REST API]] that would allow any unauthenticated user to modify any post or page within a site running WordPress 4.7 or greater. The auditors quietly notified WordPress developers, and within six days WordPress released a high priority patch to version 4.7.2 which addressed the problem.<ref>{{Cite news|url=https://make.wordpress.org/core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/|title=Disclosure of Additional Security Fix in WordPress 4.7.2|date=2017-02-01|newspaper=Make WordPress Core|access-date=2017-02-16|language=en-US}}</ref><ref>{{Cite news|url=https://blog.sucuri.net/2017/02/content-injection-vulnerability-wordpress-rest-api.html|title=Content Injection Vulnerability in WordPress 4.7 and 4.7.1|date=2017-02-01|newspaper=Sucuri Blog|access-date=2017-02-16|language=en-US}}</ref>
[[File:Typical Tor Browser notification of a canvas read attempt.png|thumb|280x280px|The [[canvas fingerprinting]] warning that is typically given by [[Tor Browser]] for WordPress-based websites.]]
WordPress' minimum PHP version requirement is PHP 5.2,<ref>{{cite web |url=https://wordpress.org/about/requirements/ |title=WordPress › About » Requirements |accessdate=December 30, 2015 |website=wordpress.org}}</ref> which was released on January 6, 2006,<ref name="eol">{{cite web |url=http://php.net/eol.php |title=Unsupported Branches |website=php.net |accessdate=November 14, 2015}}</ref> and which has been unsupported by the PHP Group and not received any security patches since January 6, 2011.<ref name="eol" />
In the absence of specific alterations to their default formatting code, WordPress-based websites use the [[canvas element]] to detect whether the browser is able to correctly render [[emoji]]. Because [[Tor (anonymity network)|Tor Browser]] does not currently discriminate between this legitimate use of the [[Canvas (GUI)|Canvas]] [[API]] and an effort to perform [[canvas fingerprinting]], it warns that the website is attempting to 'extract HTML5 canvas image data'. Ongoing efforts seek workarounds to reassure privacy advocates while retaining the ability to check for proper emoji rendering capability. {{Citation needed|reason=Claim needs source for such ongoing efforts|date=October 2018}}
==Development and support==
===Key developers===
[[Matt Mullenweg]] and [[Mike Little]] were cofounders of the project. The core lead developers include Helen Hou-Sandí, Dion Hulse, Mark Jaquith, Matt Mullenweg, Andrew Ozz, and Andrew Nacin.<ref>{{cite web |url=https://wordpress.org/about/ |title=About WordPress |accessdate=March 18, 2015 |publisher=wordpress.org}}</ref><ref>{{cite web |url=https://codex.wordpress.org/Core_Team |title=Core Team |publisher=codex.wordpress.org |accessdate=August 27, 2015}}</ref>
WordPress is also developed by its community, including ''WP testers'', a group of volunteers who test each release.<ref>{{cite web |url= http://simplifyingit.com.au/support/index.php/installing-wordpress/ |title=Installing WordPress |date=August 2014}}</ref> They have early access to [[Neutral build|nightly builds]], beta versions and release candidates. Errors are documented in a special [[mailing list]], or the project's [[Trac]] tool.
Though largely developed by the community surrounding it, WordPress is closely associated with [[Automattic]], the company founded by Matt Mullenweg.<ref>{{cite web |url= https://www.linkedin.com/pulse/billion-dollar-tech-company-offices-email-glenn-leibowitz |title= The Billion-Dollar Tech Company With No Offices or Email |access-date = 17 December 2017 |last= Leibowitz |first= Glenn |date= 17 December 2017 |quote= I recently met with Matt Mullenweg, the creator of WordPress and CEO of Automattic, the company that develops WordPress and offers a range of products and services for WordPress users both large and small. Automattic is valued today at over $1 billion. |website= [[Linkedin]]}}</ref> On September 9, 2010, Automattic handed the WordPress trademark to the newly created WordPress Foundation, which is an umbrella organization supporting WordPress.org (including the software and archives for plugins and themes), [[bbPress]] and [[BuddyPress]].
===WordCamp developer and user conferences===
[[File:WordCamp 2011 Bulgaria.jpg|thumb|right|A WordCamp in [[Sofia]], [[Bulgaria]] (2011)]]
WordCamps are casual, locally organized conferences covering everything related to WordPress.<ref name="WordCamp Central About">{{cite web |url=https://central.wordcamp.org/about/ |title=WordCamp Central > About |publisher=Central.wordcamp.org |accessdate=October 28, 2015}}</ref> The first such event was WordCamp 2006 in August 2006 in [[San Francisco]], which lasted one day and had over 500 attendees.<ref>{{cite web |url=http://2006.wordcamp.org/ |title=WordCamp 2006 |publisher=2006.wordcamp.org |accessdate=December 18, 2011}}</ref><ref>{{cite web |url=http://2011.sf.wordcamp.org/ |title=WordCamp 2011 |publisher=2011.sf.wordcamp.org |accessdate=December 18, 2011}}</ref> The first WordCamp outside San Francisco was held in [[Beijing]] in September 2007.<ref name="wordcamp schedule">{{cite web |url=http://central.wordcamp.org/schedule/ |title=WordCamp Central > Schedule |publisher=Central.wordcamp.org |accessdate=December 18, 2011}}</ref> Since then, there have been over 507 WordCamps in over 207 cities in 48 different countries around the world.<ref name="WordCamp Central About"/> WordCamp San Francisco 2014 was the last official annual conference of WordPress developers and users taking place in San Francisco, having now been replaced with WordCamp US.<ref>{{cite web |url=http://central.wordcamp.org/news/2011/01/24/wordcampsf-not-wordcon/ |title=WordCamp SF Announced (not WordCon) | WordCamp Central |publisher=Central.wordcamp.org |date=January 24, 2011 |accessdate=March 11, 2015}}</ref>
WordPress users who like public speaking can sign up to speak and lead a session.
===Support===
WordPress' primary support website is WordPress.org. This support website hosts both WordPress Codex, the online manual for WordPress and a living repository for WordPress information and documentation,<ref>{{cite web |url=https://codex.wordpress.org/ |title=WordPress Codex |publisher=WordPress.org |accessdate=March 13, 2014}}</ref>
and WordPress Forums, an active online community of WordPress users.<ref>{{cite web |url=https://wordpress.org/support/ |title=WordPress Forums |publisher=WordPress.org |accessdate=March 13, 2014}}</ref>
==See also==
* [[Weblog software]]
* [[List of content management systems]]
* [[WordPress.com]]
{{Portal bar|Free software|Software|IT|Internet}}
==References==
{{Reflist|colwidth=30em}}
==External links==
{{Sisterlinks|d=Q13166|voy=no|commons=Category:WordPress|wikt=no|m=no|mw=no|species=no|q=no|n=no|s=no}}
*{{Official website|https://wordpress.org}}
*{{DMOZ|Computers/Internet/On_the_Web/Weblogs/Templates/WordPress/}}
{{Application frameworks}}
{{Authority control}}
{{DEFAULTSORT:WordPress}}
[[Category:2003 software]]
[[Category:Blog software]]
[[Category:Content management systems]]
[[Category:Free content management systems]]
[[Category:Free software programmed in PHP]]
[[Category:Software forks]]
[[Category:Software using the GPL license]]
[[Category:Website management]]
[[Category:WordPress| ]]
[[Category:Free and open-source Android software]]
