WordPress

This article is about the web content management system (WordPress, WordPress.org). For the blog host, see WordPress.com.

WordPress (WP or WordPress.org) is a free and open-source content management system (CMS) written in hypertext preprocessor (PHP) language^[4] and paired with a MySQL or MariaDB database with supported HTTPS. Features include a plugin architecture and a template system, referred to within WordPress as "Themes". WordPress was originally created as a blog-publishing system but has evolved to support other web content types including more traditional mailing lists and Internet fora, media galleries, membership sites, learning management systems (LMS) and online stores. WordPress is used by 42.8% of the top 10 million websites as of October 2021^[update].^[5][6]

WordPress

Original author(s)	Mike Little Matt Mullenweg
Developer(s)	Community contributors WordPress Foundation
Initial release	May 27, 2003; 19 years ago (2003-05-27)^[1]
Stable release	6.2^[2]  / 29 March 2023; 38 days ago (29 March 2023)
Repository	core.trac.wordpress.org/browser
Written in	PHP
Operating system	Unix-like, Windows, Linux
Size	23.2 MB (compressed)
Type	Blog software, content management system, content management framework
License	GPLv2 or later^[3]
Website	wordpress.org

WordPress was released on May 27, 2003, by its founders, American developer Matt Mullenweg^[1] and English developer Mike Little,^[7][8] as a fork of b2/cafelog. The software is released under the GPLv2 (or later) license.^[9]

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 to serve as a network host in its own right.^[10] A local computer may be used for single-user testing and learning purposes.

WordPress Foundation owns WordPress, WordPress projects, and other related trademarks.^[11]

Overview

 

A WordPress blog

"WordPress is a factory that makes webpages"^[12] is a core analogy designed to clarify the functions of WordPress: it stores content and enables a user to create and publish webpages, requiring nothing beyond a domain and a hosting service.

WordPress has a web template system using a template processor. Its architecture is a front controller, routing all requests for non-static URIs to a single PHP file that parses the URI and identifies the target page. This allows support for more human-readable permalinks.^[13]

Themes

WordPress users may install and switch among many different themes. Themes allow users to change the look and functionality of a WordPress website without altering the core code or site content. Custom code can be added to the website by using a child theme. Every WordPress website requires at least one theme to be present. 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.^[14] WordPress themes are generally classified into two categories: free and premium. Many free themes are listed in the WordPress theme directory (also known as the repository), and premium themes are available for purchase from marketplaces and individual WordPress developers. WordPress users may also create and develop their own custom themes.^[15]

Plugins

WordPress' plugin architecture allows users to extend or depreciate the features and functionality of a website or blog.^{[16] [17]} As of December 2021^[update], WordPress.org has 59,756 plugins available,^[18] each of which offers custom functions and features enabling users to tailor their sites to their specific needs. However, this does not include the available premium plugins (approximately 1,500+), which may not be listed in the WordPress.org repository. These customizations range from search engine optimization (SEO) to client portals used to display private information to logged-in users, to content management systems, to content displaying features, such as the addition of widgets and navigation bars. 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. If the plugin developer has not tested the plugin with the last two major versions of WordPress, a warning message will be displayed on the plugin directory, informing users that the plugin may not work properly with the latest WordPress version.^[19] 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 2,000 hooks (as of Version 5.7 in 2021)^[20] divided into two categories: action hooks and filter hooks.^[21]

Plugins also represent a development strategy that can transform WordPress into all sorts of software systems and applications, limited only by the imagination and creativity of programmers. These are implemented using custom plugins to create non-website systems, such as headless WordPress applications and Software as a Service (SaaS) products.

Plugins could also be used by hackers targeting sites that use WordPress, as hackers could exploit bugs in WordPress plugins instead of bugs in WordPress itself.^[22]

Mobile applications

Phone apps for WordPress exist for WebOS,^[23] Android,^[24] iOS,^[25][26] Windows Phone, and BlackBerry.^[27] 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.^[25][26]

Accessibility

The WordPress Accessibility Team has worked to improve the accessibility for core WordPress as well as support a clear identification of accessible themes.^[28] The WordPress Accessibility Team provides continuing educational support about web accessibility and inclusive design. The WordPress Accessibility Coding Standards state that "All new or updated code released in WordPress must conform with the Web Content Accessibility Guidelines 2.0 at level AA."^[29]

Other features

WordPress also features integrated link management, a search engine–friendly, clean permalink structure; the ability to assign multiple categories to posts; and support for tagging of posts. Automatic filters are also included, providing standardized formatting and styling of text in posts (for example, converting regular quotes to 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 several plugins that allow for a variety of customized editing features.

Multi-user and multi-blogging

Before 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 can 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 MU adds eight new data tables for each blog.

As of the release of WordPress 3, WordPress MU has merged with WordPress.^[30]

History

b2/cafelog, more commonly known as b2 or catalog, was the precursor to WordPress.^[31] b2/cafelog was estimated to have been installed on approximately 2,000 blogs as of May 2003.^[32] 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.

As the development of b2/cafelog slowed down, Matt Mullenweg began pondering the idea of forking b2/cafelog and new features that he would want in a new CMS, in a blog post written on January 24, 2003.^[33] Mike Little, a professional developer, became the first to comment on the blog post expressing interest to contribute.^[33][34] The two worked together to create the first version of WordPress, version 0.70,^[35] which was released on May 27, 2003.^[36] Christine Selleck Tremoulet, a friend of Mullenweg, suggested the name WordPress.^[37][38]

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.^[39][40] 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 May 2021, WordPress is used by 64.8% of all the websites whose content management system is known, and 41.4% of the top 10 million websites.^[5]

Awards and recognition

• Winner of InfoWorld's "Best of open source software awards: Collaboration", awarded in 2008.^[41]
• Winner of Open Source CMS Awards's "Overall Best Open Source CMS", awarded in 2009.^[42]
• Winner of digital synergy's "Hall of Fame CMS category in the 2010 Open Source", awarded in 2010.^[43]
• Winner of InfoWorld's "Bossie award for Best Open Source Software", awarded in 2011.^[44]
• WordPress has a five star privacy rating from the Electronic Frontier Foundation.^[45]

Release history

Main releases of WordPress are codenamed after well-known jazz musicians, starting from version 1.0.^[46][47]

Although only the current release is officially supported, security updates are backported "as a courtesy" to all versions as far back as 4.0.^[48]

Version	Code name	Release date	Notes
Old version, no longer maintained: 0.7	none	May 27, 2003^[49]	Used the same file structure as its predecessor, b2/cafelog, and continued the numbering from its last release, 0.6.^[50] Only 0.71-gold is available for download in the official WordPress Release Archive page.
Old version, no longer maintained: 1.0	Davis	January 3, 2004^[51]	Added search engine-friendly permalinks, multiple categories, dead-simple installation and upgrade, comment moderation, XFN support, and Atom support.
Old version, no longer maintained: 1.0.2	Blakey	March 11, 2004^[52]	This was only a bugfix release and contained no new features.
Old version, no longer maintained: 1.2	Mingus	May 22, 2004^[53]	Added support of Plugins; in which the same identification headers are used unchanged in WordPress releases as of 2011^[update].
Old version, no longer maintained: 1.5	Strayhorn	February 17, 2005^[54]	Added a range of vital features, such as the ability to manage static pages and a template/Theme system. It was also equipped with a new default template (code named Kubrick).^[55] designed by Michael Heilemann.
Old version, no longer maintained: 2.0	Duke	December 31, 2005^[56]	Added rich editing, better administration tools, image uploading, faster posting, improved import system, fully overhauled the back end, and various improvements to Plugin developers.
Old version, no longer maintained: 2.1	Ella	January 22, 2007^[57]	Corrected security issues, a redesigned interface, enhanced editing tools (including integrated spell check and auto save), and improved content management options.
Old version, no longer maintained: 2.2	Getz	May 16, 2007^[58]	Added widget support for templates, updated Atom feed support, and speed optimizations.
Old version, no longer maintained: 2.3	Dexter	September 24, 2007^[59]	Added native tagging support, new taxonomy system for categories, and easy notification of updates, fully supports Atom 1.0, with the publishing protocol, and some much-needed security fixes.
Old version, no longer maintained: 2.5	Brecker	March 29, 2008^[60]	Major revamp to the dashboard, dashboard widgets, multi-file upload, extended search, improved editor, an improved plugin system, and more.
Old version, no longer maintained: 2.6	Tyner	July 15, 2008^[61]	Added new features that made WordPress a more powerful CMS: it can now track changes to every post and page and allow easy posting from anywhere on the web.
Old version, no longer maintained: 2.7	Coltrane	December 11, 2008^[62]	Administration interface was redesigned fully, added automatic upgrades, and installed plugins, from within the administration interface.
Old version, no longer maintained: 2.8	Baker	June 10, 2009^[63]	Added speed improvements, automatically installing themes from within the administration interface, introducing the CodePress editor for syntax highlighting, and a redesigned widget interface.
Old version, no longer maintained: 2.9	Carmen	December 19, 2009^[64]	Added global undo, built-in image editor, batch plugin updating, and many less visible tweaks.
Old version, no longer maintained: 3.0	Thelonious	June 17, 2010^[65]	Added a new theme APIs, merged WordPress and WordPress MU, creating the new multi-site functionality, new default theme "Twenty Ten" and a refreshed, lighter admin UI.
Old version, no longer maintained: 3.1	Reinhardt	February 23, 2011^[66]	-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.
Old version, no longer maintained: 3.2	Gershwin	July 4, 2011^[67]	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.
Old version, no longer maintained: 3.3	Sonny	December 12, 2011^[68]	Focused on making WordPress friendlier for beginners and tablet computer users.
Old version, no longer maintained: 3.4	Green	June 13, 2012^[69]	Focused on improvements to theme customization, Twitter integration and several minor changes.
Old version, no longer maintained: 3.5	Elvin	December 11, 2012^[70]	Support for the Retina Display, color picker, a new default theme "Twenty Twelve", improved image workflow.
Old version, no longer maintained: 3.6	Oscar	August 1, 2013^[71]	New default theme "Twenty Thirteen", admin enhancements, post formats UI update, menus UI improvements, new revision system, autosave, and post locking.
Old version, no longer maintained: 3.7	Basie	October 24, 2013^[72]	Automatically apply maintenance and security updates in the background, stronger password recommendations, and support for automatically installing the right language files and keeping them up to date.
Old version, no longer maintained: 3.8	Parker	December 12, 2013^[73]	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".
Old version, no longer maintained: 3.9	Smith	April 16, 2014^[74]	Improvements to the editor for media, live widget and header previews, and new theme browser.
Old version, no longer maintained: 4.0	Benny	September 4, 2014^[75]	Improved media management, embeds, writing interface, easy language change, theme customizer, plugin discovery, and compatibility with PHP 5.5 and MySQL 5.6.^[76]
Older version, yet still maintained: 4.1	Dinah	December 18, 2014^[77]	Twenty Fifteen as the new default theme, distraction-free writing, easy language switch, Vine embeds, and plugin recommendations.
Older version, yet still maintained: 4.2	Powell	April 23, 2015^[78]	New "Press This" features, improved characters support, emoji support, improved customizer, new embeds, and updated plugin system.
Older version, yet still maintained: 4.3	Billie	August 18, 2015^[79]	Focus on the mobile experience, better passwords, and improved customizer.
Older version, yet still maintained: 4.4	Clifford	December 8, 2015^[80]	Introduction of "Twenty Sixteen" theme, and improved responsive images and embeds.
Older version, yet still maintained: 4.5	Coleman	April 12, 2016^[81]	Added inline linking, formatting shortcuts, live responsive previews, and other updates under the hood.
Older version, yet still maintained: 4.6	Pepper	August 16, 2016^[82]	Added streamlined updates, native fonts, editor improvements with inline link checker and content recovery, and other updates under the hood.
Older version, yet still maintained: 4.7	Vaughan	December 6, 2016^[83]	Comes with new default theme "Twenty Seventeen", Video Header Support, PDF preview, custom CSS in the live preview, editor Improvements, and other updates under the hood.
Older version, yet still maintained: 4.8	Evans	June 8, 2017^[84]	The next-generation editor. Additional specific goals include the TinyMCE inline element/link boundaries, new media widgets, and WYSIWYG in the text widget. End Support for Internet Explorer Versions 8, 9, and 10.
Older version, yet still maintained: 4.9	Tipton	November 16, 2017^[85]	Improved theme customizer experience, including scheduling, frontend preview links, autosave revisions, theme browsing, improved menu functions, and syntax highlighting. Added a new gallery widget and updated text and video widgets. Theme editor gives warnings and rollbacks when saving files that produce fatal errors.^[86]
Older version, yet still maintained: 5.0	Bebo	December 6, 2018^[87]	New block-based editor Gutenberg^[88] with new default theme "Twenty Nineteen".
Older version, yet still maintained: 5.1	Betty	February 21, 2019^[89]	PHP version upgrade notices and block editor improvements.
Older version, yet still maintained: 5.2	Jaco	May 7, 2019^[90]	Include Site Health Check, PHP error protection, the all-new block directory, and update package signing.
Older version, yet still maintained: 5.3	Kirk	November 12, 2019^[91]	Polish current user interactions and make user interfaces more user-friendly. New default theme "Twenty Twenty", was designed by Anders Norén.
Older version, yet still maintained: 5.4	Adderley	March 31, 2020^[92]	Social Icons and Buttons blocks added, blocks customization and user interface improved, added features for personal data exports, custom fields for menu items, blocks improvements for developers.^[93]
Older version, yet still maintained: 5.5	Eckstine	August 11, 2020^[94]	Added lazy-loading images, XML sitemaps by default, auto-updates to plugins and themes, and improvements to the block editor.^[95]
Older version, yet still maintained: 5.6	Simone	December 8, 2020^[96]	New default theme "Twenty Twenty-One," Gutenberg enhancements, automatic updates for core releases, increased support for PHP 8, application passwords for REST API authentication, improved accessibility.^[97]
Older version, yet still maintained: 5.7	Esperanza	March 9, 2021^[98]	New editor is easier to use, do more without writing custom code, simpler default color palette, from HTTP to HTTPS in a single click, new Robots API, lazy-load your iframes and ongoing cleanup after update to jQuery 3.5.1.^[99]
Older version, yet still maintained: 5.8	Tatum	July 20, 2021^[100]	Block widgets, query loop blocks, block themes, List View, Pattern Transformations, Duotone, new theme.json file, dropped IE11 support, WebP image support, new block support flags.^[101]
Older version, yet still maintained: 5.9	Joséphine	January 25, 2022^[102]	New default theme "Twenty Twenty-Two", new WordPress Admin feature Site Editor, Block Themes manageable through Site Editor, new Navigation block, improved block controls, Pattern Directory, List View, refactored Gallery block, Theme.json child theme support, block-level locking, multiple stylesheets per block.^[103]
Older version, yet still maintained: 6.0	Arturo	May 24, 2022^[104]	Gutenberg writing improvements, multiple style variations and expanded template options for block themes, integrated patterns, additional design tools, multiple block selections from the list view, block locking, and various performance, and accessibility improvements.^[105]
Older version, yet still maintained: 6.1	Misha	November 1, 2022^[106]	Gutenberg writing improvements, design tools for more consistency and control, cleaner layouts and document settings visualization, menu management, fluid typography, improved block placeholders, and spacing presets.^[107]
Current stable version: 6.2	Dolphy	March 29, 2023^[108]	Reimagined Site Editor interface, improved Navigation block, Block Inserter, and organized block settings sidebar with tabs for Settings and Styles. A collection of header and footer patterns for block themes is also available, as well as Openverse media integration and Distraction Free mode for writing. The new Style Book provides a complete overview of how each block in the site's library looks, and users can now copy and paste styles and add custom CSS for more control over their site's appearance. Other features include sticky positioning for top-level group blocks, options to import favorite widgets from Classic themes, and local fonts in default WordPress themes for better privacy with Google Fonts included.^[109]
Legend: Old version, not maintained Older version, still maintained Current stable version Latest preview version Future release

WordPress 5.0 "Bebo"

The December 2018 release of WordPress 5.0, "Bebo", is named in homage to the pioneering Cuban jazz musician Bebo Valdés.^[110]

 

New page editor for WordPress

It included a new default editor "Gutenberg" – a block-based editor; it allows users to modify their displayed content in a much more user-friendly way than prior iterations. Blocks are abstract units of markup that, composed together, form the content or layout of a web page.^[111] Past content that was created on WordPress pages is listed under what is referred to as a Classic Block.^[112] Before Gutenberg, there were several block-based editors available as WordPress plugins, e.g. Elementor. Following the release of Gutenberg, comparisons were made between it and those existing plugins.^[113][114]

Classic Editor plugin

The Classic Editor plugin was created as a result of User preferences and helped website developers maintain past plugins only compatible with WordPress 4.9, giving plugin developers time to get their plugins updated & compatible with the 5.0 release. Having the Classic Editor plugin installed restores the "classic" editing experience that WordPress has had up until the WordPress 5.0 release.^[115] The Classic Editor plugin will be supported at least until 2024.^[116]

As of November 2022, the Classic Editor plugin is active on over 5 million installations of WordPress.^[117]

Vulnerabilities

 

Apache access log showing WordPress vulnerability bots

Many security issues^[118] 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.^[119]

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.^[120] A separate vulnerability on one of the project site's web servers allowed an attacker to introduce exploitable code in the form of a back door to some downloads of WordPress 2.1.1. The 2.1.2 release addressed this issue; an advisory released at the time advised all users to upgrade immediately.^[121]

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.^[122] To help mitigate this problem, WordPress made updating the software a much easier, "one-click" automated process in version 2.7 (released in December 2008).^[123] However, the filesystem security settings required to enable the update process can be an additional risk.^[124]

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.^[125]

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 XSS. A separate inspection of the top 10 e-commerce plugins showed that seven of them were vulnerable.^[126]

To promote better security and to streamline the update experience overall, automatic background updates were introduced in WordPress 3.7.^[127]

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 installations, themes, and plugins updated, using only trusted themes and plugins,^[128] and editing the site's .htaccess configuration file if supported by the webserver 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 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, for example, upload their own files (such as a web shell) that collect sensitive information.

Developers can also use tools to analyze potential vulnerabilities, including Jetpack Protect, WPScan, WordPress Auditor, and WordPress Sploit Framework developed by 0pc0deFR. These types of tools research known vulnerabilities, such as CSRF, LFI, RFI, 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 that the Yoast SEO plugin was vulnerable to SQL injection, allowing attackers to potentially execute arbitrary SQL commands.^[129][130] The issue was fixed in version 1.7.4 of the plugin.^[131]

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.^[132][133]

 

The canvas fingerprinting warning is typically given by Tor Browser for WordPress-based websites.

As of WordPress 6.0, the minimum PHP version requirement is PHP 5.6,^[134] which was released on August 28, 2014,^[135] and which has been unsupported by the PHP Group and not received any security patches since December 31, 2018.^[135] Thus, WordPress recommends using PHP version 7.4 or greater.^[134]

In the absence of specific alterations to their default formatting code, WordPress-based websites use the canvas element to detect whether the browser can correctly render emoji. Because Tor Browser does not currently discriminate between this legitimate use of the 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.^[136]

Development and support

Key developers

Matt Mullenweg and Mike Little were co-founders of the project. The core lead developers include Helen Hou-Sandí, Dion Hulse, Mark Jaquith, Matt Mullenweg, Andrew Ozz, and Andrew Nacin.^[137][138]

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

Though largely developed by the community surrounding it, WordPress is closely associated with Automattic, the company founded by Matt Mullenweg.^[139]

WordPress Foundation

WordPress Foundation is a non-profit organization that was set up to support the WordPress project.^{[140][141][142]} The purpose of the organization is to guarantee open access to WordPress's software projects forever.^[140][141] As part of this, the organization owns and manages WordPress, WordCamp, and related trademarks.^{[140][143][144]} In January 2010, Matt Mullenweg formed the organization^[140] to own and manage the trademarks of WordPress project.^[145][144] Previously – from 2006 onwards – Automattic acted as a short-term owner of the WordPress trademarks. From the beginning, he intended later to place the WordPress trademarks with the WordPress Foundation, which did not yet exist in 2006 and which eventually took longer to set up than expected.^[145][146]

WordPress Photo Directory

On December 14, 2021, Matt Mullenweg announced the WordPress Photo Directory at the State of the Word 2021 event.^[147] It is an open-source image directory for open images maintained by the WordPress project.^[147] The image directory aims to provide an open alternative to closed image banks, such as Unsplash, Pixbaby, and Adobe Stock, whose licensing terms have become restrictive in recent years. Use in WordPress themes, for example, is restricted.^[147][148] In January 2022, the project began to gather volunteers, and in February, its own developer website was launched, where team representatives were next selected.^[149]

WordCamp developer and user conferences

 

A WordCamp in Sofia, Bulgaria (2011)

WordCamps are casual, locally organized conferences covering everything related to WordPress.^[150] The first such event was WordCamp 2006 in August 2006 in San Francisco, which lasted one day and had over 500 attendees.^[151][152] The first WordCamp outside San Francisco was held in Beijing in September 2007.^[153] Since then, there have been over 1,022 WordCamps in over 75 cities in 65 countries around the world.^[150] 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.^[154] First ran in 2013 as WordCamp Europe, regional WordCamps in other geographical regions are held to connect people who are not already active in their local communities and inspire attendees to start user communities in their hometowns.^[155] In 2019, the Nordic region had its own WordCamp Nordic.^[156][157] The first WordCamp Asia was to be held in 2020,^[158] but cancelled due to the COVID-19 pandemic.^[159]

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,^[160] and WordPress Forums, an active online community of WordPress users.^[161]

See also

• Weblog software
• NextGEN Gallery
• List of content management systems
• WordPress.com

References

1. Mullenweg, Matt (May 27, 2003). "WordPress Now Available". wordpress.org. WordPress. from the original on July 19, 2010. Retrieved July 22, 2010.
2. "WordPress 6.2 "Dolphy"". March 29, 2023. Retrieved March 29, 2023.
3. "WordPress: About: GPL". WordPress.org. from the original on July 21, 2010. Retrieved June 15, 2010.
4. "Requirements". wordpress.org. WordPress. from the original on January 20, 2020. Retrieved January 29, 2020.
5. "Usage Statistics and Market Share of Content Management Systems for Websites". w3techs.com. W3Techs. May 7, 2021. Retrieved May 7, 2021.{{cite web}}: CS1 maint: url-status (link)
6. "CMS Usage Statistics". builtwith.com. BuiltWith. from the original on August 6, 2013. Retrieved August 1, 2013.
7. mikelittle (April 21, 2003). "Commit number 8". from the original on February 20, 2016. Retrieved February 3, 2016.
8. Patterson, Dan (February 6, 2017). "WordPress "quietly" powers 27% of the web". www.techrepublic.com. from the original on February 5, 2018. Retrieved December 16, 2017.
9. "WordPress › About" License". wordpress.org. WordPress.org. from the original on June 25, 2014. Retrieved June 30, 2014.
10. "Support disaggregating WordPress.com and WordPress.org". wordpress.com. WordPress.com. from the original on December 30, 2015. Retrieved January 7, 2016.
11. "Trademark Policy". WordPress Foundation. September 9, 2010. Retrieved March 28, 2022.{{cite web}}: CS1 maint: url-status (link)
12. Meyer, Fred (February 13, 2018). "WordPress is a Factory: A Technical Introduction". WPShout. from the original on February 4, 2019. Retrieved December 12, 2018.
13. Hayes, David (February 11, 2014). "WordPress and the Front Controller Design Pattern | WPShout". WPShout. from the original on May 17, 2016. Retrieved February 15, 2017.
14. "Theme Installation". wordpress.org. Codex.wordpress.org. April 9, 2013. from the original on April 26, 2013. Retrieved April 26, 2013.
15. Chandler, Jeff (April 3, 2014). "Introduction To Underscores: A WordPress Starter Theme With Konstantin Obenland". wptavern.com. from the original on August 19, 2016. Retrieved July 31, 2016.
16. Paudel, Bimal Raj (July 30, 2022). "How to install a WordPress plugin". wptracer.com. Retrieved March 28, 2023.
17. "WordPress Plugins". WordPress.org. Retrieved March 28, 2023.
18. "WordPress Plugins". WordPress.org. Retrieved May 7, 2021.{{cite web}}: CS1 maint: url-status (link)
19. "Plugin Developer FAQ". WordPress.org. Retrieved October 29, 2022.{{cite web}}: CS1 maint: url-status (link)
20. "WordPress Hooks Database". adambrown.info. Retrieved October 8, 2021.{{cite web}}: CS1 maint: url-status (link)
21. "Plugin Developer Handbook". WordPress Developer Resources. Retrieved March 28, 2023.
22. Cimpanu, Catalin (March 1, 2020). "Hackers are actively exploiting zero-days in several WordPress plugins". ZDNet. Retrieved July 7, 2021.
23. . WordPress. Archived from the original on July 2, 2011. Retrieved March 6, 2012.
24. "WordPress publishes native Android application". wirefly.com. Android and Me. February 2, 2010. from the original on July 21, 2011. Retrieved June 15, 2010.
25. . WordPress iPhone & iPod Touch. July 12, 2008. Archived from the original on March 14, 2016. Retrieved February 9, 2016.
26. melanson, mike (March 24, 2011). "18 Million WordPress Blogs Land on the iPad". ReadWriteWeb. from the original on November 23, 2018. Retrieved June 27, 2015.
27. "WordPress for BlackBerry". WordPress. Archived from the original on November 6, 2013. Retrieved December 27, 2009.
28. "Make WordPress Accessible". WordPress. June 22, 2022. Retrieved June 24, 2022.{{cite web}}: CS1 maint: url-status (link)
29. "Accessibility Coding Standards". WordPress.
30. "WordPress 3.0 "Thelonious"". WordPress.org. June 17, 2010. from the original on June 30, 2010. Retrieved December 18, 2011.
31. Andrew Warner, Matt Mullenweg (September 10, 2009). The Biography Of WordPress – With Matt Mullenweg (MPEG-4 Part 14) (Podcast). Mixergy. Event occurs at 10:57. from the original on September 14, 2009. Retrieved September 28, 2009. b2 had actually, through a series of circumstances, essentially become abandoned.
32. Valdrighi, Michel. "b2 test weblog – post dated 23.05.03". from the original on May 22, 2013. Retrieved May 9, 2013.
33. Matt Mullenweg (January 24, 2003). . Archived from the original on February 8, 2023.
34. @photomatt (January 25, 2023). (Tweet). Archived from the original on March 10, 2023 – via Twitter.
35. . WordPress.org. May 19, 2019. Archived from the original on February 1, 2023.
36. Matt Mullenweg (May 7, 2003). . WordPress.org. Archived from the original on February 1, 2023.
37. Silverman, Dwight (January 24, 2008). "The importance of being Matt". Houston Chronicle. from the original on May 25, 2014. Retrieved August 14, 2014.
38. Tremoulet, Christine Selleck (January 24, 2008). . Christine Selleck Tremoulet. Archived from the original on May 4, 2009. Retrieved March 29, 2012.
39. Manjoo, Farhad (August 9, 2004). "Blogging grows up". Salon. from the original on November 2, 2012. Retrieved March 29, 2012.
40. Pilgrim, Mark (May 14, 2004). . Mark Pilgrim. Archived from the original on April 10, 2006. Retrieved March 29, 2012.
41. "Best of open source software awards: Collaboration". infoworld.com. August 5, 2008. from the original on December 17, 2017. Retrieved December 16, 2017.
42. "WordPress wins top prize in 2009 Open Source CMS Awards". cmscritic.com. November 14, 2009. from the original on December 17, 2017. Retrieved December 16, 2017.
43. "Hall of Fame CMS". digitalsynergy.ca. from the original on October 10, 2018. Retrieved December 16, 2017.
44. "WordPress wins Bossie Awards 2011: The best open source applications". wprockers.com. from the original on December 17, 2017. Retrieved December 16, 2017.
45. "Who Has Your Back? Government Data Requests 2017". July 10, 2017. from the original on September 15, 2018. Retrieved October 19, 2018.
46. hollander, Roel. "Fun Fact: Wordpress Jazz Tributes". roelhollander.eu. from the original on July 14, 2017. Retrieved December 16, 2017.
47. "Roadmap". Blog. WordPress.org. from the original on June 14, 2010. Retrieved June 15, 2010.
48. "Dev Chat summary: Wednesday, November 30, 2022". Make WordPress Core. November 30, 2022. Retrieved December 1, 2022.
49. "WordPress Blog: WordPress 0.7". WordPress.org. May 27, 2003. from the original on July 14, 2010. Retrieved May 27, 2003.
50. "Cafelog". from the original on September 2, 2011. Retrieved May 15, 2011.
51. "WordPress Blog: WordPress 1.0". WordPress.org. January 3, 2004. from the original on July 12, 2010. Retrieved January 3, 2004.
52. "In case you haven't heard…". WordPress.org. March 11, 2004. from the original on May 24, 2022. Retrieved March 11, 2004.
53. "WordPress Blog: WordPress 1.2". WordPress.org. May 22, 2004. from the original on July 14, 2010. Retrieved May 22, 2004.
54. "WordPress Blog: WordPress 1.5". WordPress.org. February 17, 2005. from the original on July 14, 2010. Retrieved February 17, 2005.
55. . Binarybonsai.com. Archived from the original on March 11, 2012. Retrieved June 15, 2010.
56. "WordPress Blog: WordPress 2.0". WordPress.org. December 31, 2005. from the original on July 13, 2010. Retrieved December 31, 2005.
57. "WordPress Blog: WordPress 2.1". WordPress.org. January 22, 2007. from the original on July 12, 2010. Retrieved January 22, 2007.
58. "WordPress Blog: WordPress 2.2". WordPress.org. May 16, 2007. from the original on July 14, 2010. Retrieved May 16, 2007.
59. "WordPress Blog: WordPress 2.3". WordPress.org. from the original on July 12, 2010. Retrieved September 24, 2007.
60. "WordPress Blog: WordPress 2.5". WordPress.org. March 29, 2008. from the original on July 12, 2010. Retrieved March 29, 2008.
61. "WordPress Blog: WordPress 2.6". WordPress.org. from the original on July 13, 2010. Retrieved June 15, 2008.
62. "WordPress Blog: WordPress 2.7". WordPress.org. December 11, 2008. from the original on July 14, 2010. Retrieved December 11, 2008.
63. "WordPress Blog: WordPress 2.8". WordPress.org. from the original on July 14, 2010. Retrieved June 10, 2009.
64. "WordPress Blog: WordPress 2.9". WordPress.org. December 19, 2009. from the original on July 13, 2010. Retrieved December 19, 2009.
65. "WordPress Blog: WordPress 3.0". WordPress.org. June 17, 2010. from the original on July 12, 2010. Retrieved June 17, 2010.
66. "WordPress Blog: WordPress 3.1". WordPress.org. February 23, 2011. from the original on February 24, 2011. Retrieved February 25, 2011.
67. "WordPress Blog: WordPress 3.2". WordPress.org. from the original on July 5, 2011. Retrieved June 4, 2011.
68. "WordPress Blog: WordPress 3.3". WordPress.org. December 12, 2011. from the original on December 13, 2011. Retrieved December 12, 2011.
69. "WordPress Blog: WordPress 3.4". WordPress.org. June 13, 2012. from the original on June 13, 2012. Retrieved June 13, 2012.
70. "WordPress Blog: WordPress 3.5". WordPress.org. December 11, 2012. from the original on December 11, 2012. Retrieved December 11, 2012.
71. "WordPress Blog: WordPress 3.6". WordPress.org. August 2013. from the original on August 2, 2013. Retrieved August 1, 2013.
72. "WordPress Blog: WordPress 3.7". WordPress.org. October 24, 2013. from the original on October 25, 2013. Retrieved October 24, 2013.
73. "WordPress Blog: WordPress 3.8". WordPress.org. December 12, 2013. from the original on December 12, 2013. Retrieved December 12, 2013.
74. "WordPress Blog: WordPress 3.9". WordPress.org. April 16, 2014. from the original on April 16, 2014. Retrieved April 16, 2014.
75. "WordPress Blog: WordPress 4.0". WordPress.org. September 4, 2014. from the original on September 4, 2014. Retrieved September 4, 2014.
76. "Learn What's New in WordPress v4.0". from the original on March 7, 2016. Retrieved March 14, 2016.
77. "WordPress Blog: WordPress 4.1". WordPress.org. December 18, 2014. from the original on December 18, 2014. Retrieved December 18, 2014.
78. "WordPress Blog: WordPress 4.2". WordPress.org. April 23, 2015. from the original on April 24, 2015. Retrieved April 23, 2015.
79. "WordPress Blog: WordPress 4.3". WordPress.org. August 18, 2015. from the original on August 19, 2015. Retrieved August 18, 2015.
80. "WordPress Blog: WordPress 4.4". WordPress.org. December 8, 2015. from the original on December 9, 2015. Retrieved December 8, 2015.
81. "WordPress Blog: WordPress 4.5". WordPress.org. April 12, 2016. from the original on April 26, 2016. Retrieved April 26, 2016.
82. "WordPress Blog: WordPress 4.6". Wordpress News. WordPress.org. August 16, 2016. from the original on August 17, 2016. Retrieved August 16, 2016.
83. "WordPress Blog: WordPress 4.7 "Vaughan"". WordPress.org. December 6, 2016. from the original on December 7, 2016. Retrieved December 7, 2016.
84. "Version 4.8 – Make WordPress Core". WordPress.org. May 3, 2017. from the original on August 2, 2017. Retrieved August 1, 2017.
85. "Version 4.9 – Make WordPress Core". WordPress.org. August 2, 2017. from the original on August 6, 2017. Retrieved August 6, 2017.
86. "WordPress Blog: WordPress 4.9 Beta 1". WordPress.org. October 5, 2017. from the original on October 25, 2017. Retrieved October 25, 2017.
87. "WordPress 5.0 Development Cycle". November 15, 2017. from the original on November 17, 2018. Retrieved November 17, 2018.
88. "The new Gutenberg editing experience". The new Gutenberg editing experience. from the original on December 7, 2018. Retrieved December 7, 2018.
89. "WordPress 5.1 Development Cycle". December 19, 2018. from the original on February 22, 2019. Retrieved February 22, 2019.
90. "WordPress 5.2 Development Cycle". May 20, 2019. from the original on April 12, 2019. Retrieved May 20, 2019.
91. "WordPress 5.3 Development Cycle". Make WordPress Core. November 13, 2019. Retrieved November 14, 2019.
92. "WordPress 5.4 Development Cycle". March 31, 2020. Retrieved March 31, 2020.
93. "WordPress 5.4 "Adderley"". March 31, 2020. Retrieved April 1, 2020.
94. "WordPress 5.5 Development Cycle". August 11, 2020. Retrieved August 12, 2020.
95. "WordPress 5.5 "Eckstine"". August 11, 2020. Retrieved August 12, 2020.
96. "WordPress 5.6 Development Cycle". Wordpress. December 9, 2020. Retrieved December 9, 2020.
97. "WordPress 5.6 "Simone"". Wordpress. December 6, 2020. Retrieved March 9, 2021.
98. "WordPress 5.7 Development Cycle". WordPress. March 9, 2021. Retrieved March 9, 2021.
99. "WordPress 5.7 "Esperanza"". Wordpress. March 9, 2021. Retrieved March 9, 2021.
100. "WordPress 5.8 Development Cycle". WordPress. March 9, 2021. Retrieved August 9, 2021.
101. "WordPress 5.8 Tatum". WordPress. July 20, 2021. Retrieved August 9, 2021.
102. "WordPress 5.9 Development Cycle". WordPress. July 15, 2021. Retrieved February 22, 2022.
103. "WordPress 5.9 Josephine". WordPress. January 25, 2022. Retrieved February 22, 2022.
104. "WordPress 6.0 Development Cycle". WordPress. January 25, 2022. Retrieved May 25, 2022.
105. "WordPress 6.0 Arturo". WordPress. May 24, 2022. Retrieved May 25, 2022.
106. "WordPress 6.1 Development Cycle". WordPress. November 1, 2022. Retrieved November 13, 2022.
107. "WordPress 6.1 Misha". WordPress. November 1, 2022. Retrieved November 13, 2022.
108. "WordPress 6.2 Development Cycle". Make WordPress Core. November 2, 2022. Retrieved April 10, 2023.
109. "Version 6.2". WordPress.org Documentation. March 29, 2023. Retrieved April 10, 2023.
110. "WordPress 5.0 "Bebo"". WordPress News. December 6, 2018. from the original on December 12, 2018. Retrieved December 12, 2018.
111. "Gutenberg « WordPress Codex". codex.wordpress.org. from the original on September 3, 2018. Retrieved December 12, 2018.
112. "The Complete Guide to Gutenberg's Classic Block". go gutenberg. from the original on December 15, 2018. Retrieved December 12, 2018.
113. Gutenberg vs Elementor: Comparing The New WordPress Block Editor To Elementor, CREATE & CODE, December 5, 2018
114. Gutenberg vs. Elementor: ThemeIsle Actually Attempted to Build Their New Site With Both — Here’s What Happened, Elementor.com, February 6, 2020
115. "A tip for the WordPress 5.0 release – Gutenberg and the Classic Editor". Garage. December 6, 2018. from the original on December 13, 2018. Retrieved December 12, 2018.
116. "Classic Editor". WordPress.org. from the original on December 12, 2018. Retrieved December 12, 2018.
117. "Classic Editor". WordPress.org. Retrieved November 25, 2022. Active installations: 5+ million
118. . Blogsecurity.net. June 28, 2007. Archived from the original on March 9, 2012. Retrieved February 17, 2016.
119. "Secunia WordPress Vulnerability Report". Secunia.com. from the original on July 23, 2017. Retrieved September 13, 2013.
120. "WordPress Exploit Nails Big Name Seo Bloggers". Threadwatch.org. from the original on October 6, 2018. Retrieved December 18, 2011.
121. "WordPress 2.1.1 dangerous, Upgrade to 2.1.2". WordPress.org. March 2, 2007. from the original on March 4, 2007. Retrieved March 4, 2007.
122. . Blog Security. May 23, 2007. Archived from the original on March 15, 2012. Retrieved June 15, 2010.
123. "Updating WordPress". WordPress Codex. from the original on October 11, 2012. Retrieved September 25, 2012.
124. "Yet another WordPress release". August 13, 2009. from the original on October 30, 2012. Retrieved September 24, 2012.
125. . BlogSecurity. June 28, 2007. Archived from the original on October 13, 2012. Retrieved June 15, 2010.
126. Westervelt, Robert (June 18, 2013). "Popular WordPress E-Commerce Plugins Riddled With Security Flaws – Page: 1". CRN. from the original on March 20, 2015. Retrieved March 11, 2015.
127. "Configuring Automatic Background Updates « WordPress Codex". Codex.wordpress.org. from the original on June 28, 2014. Retrieved June 30, 2014.
128. Ward, Simon (July 9, 2012). "Original Free WordPress Security Infographic by Pingable". Pingable. from the original on October 25, 2012. Retrieved October 28, 2012.
129. CVE-2015-2292 . Archived from the original on June 14, 2017. Retrieved July 7, 2017.{{cite web}}: CS1 maint: bot: original URL status unknown (link), Retrieved on July 7, 2017
130. Common Vulnerabilities and Exposures CVE-2015-2293. Archived from the original on June 15, 2017. Retrieved July 7, 2017.{{cite web}}: CS1 maint: bot: original URL status unknown (link), Retrieved on July 7, 2017
131. Barry Schwartz "Yoast WordPress SEO Plugin Vulnerable To Hackers" February 11, 2016, at the Wayback Machine, Retrieved on February 13, 2016.
132. "Disclosure of Additional Security Fix in WordPress 4.7.2". Make WordPress Core. February 1, 2017. from the original on February 16, 2017. Retrieved February 16, 2017.
133. "Content Injection Vulnerability in WordPress 4.7 and 4.7.1". Sucuri Blog. February 1, 2017. from the original on February 16, 2017. Retrieved February 16, 2017.
134. "WordPress › About » Requirements". wordpress.org. October 28, 2022. from the original on October 28, 2022. Retrieved October 28, 2022.
135. "Unsupported Branches". php.net. from the original on May 15, 2019. Retrieved May 21, 2019.
136. "Bug report #42428: wp-emoji pops up privacy hanger in Firefox with privacy.resist fingerprinting turned on". Make WordPress Core. Retrieved February 4, 2020.
137. "About WordPress". wordpress.org. from the original on March 21, 2015. Retrieved March 18, 2015.
138. "Core Team". codex.wordpress.org. December 13, 2011. from the original on September 1, 2015. Retrieved August 27, 2015.
139. Leibowitz, Glenn (December 17, 2017). "The Billion-Dollar Tech Company With No Offices or Email". LinkedIn. from the original on September 27, 2018. Retrieved December 17, 2017. 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.
140. "WordPress Foundation". WordPress Foundation. Retrieved March 28, 2022.
141. Vasan, Anjana (February 4, 2022). "What is the WordPress Foundation and Why Does it Exist?". WordPress Foundation. Retrieved March 28, 2022.
142. Patel, Nilay (March 15, 2022). "How WordPress and Tumblr are keeping the internet weird". The Verge. Retrieved April 4, 2022.
143. "Trademark Policy". WordPress Foundation. September 9, 2010. Retrieved March 28, 2022.
144. . opensource.org. Archived from the original on May 31, 2022. Retrieved April 4, 2022.
145. "The WordPress Foundation". Milestones. November 25, 2015. Retrieved March 28, 2022.
146. "For-Profit Automattic Gives WordPress Trademark To Non-Profit Foundation". TechCrunch. September 10, 2010. Retrieved April 4, 2022.
147. "The WordPress Photo Directory Is the Open-Source Image Project We Have Long Needed". WP Tavern. December 21, 2021. Retrieved April 4, 2022.
148. "An Early Look at the WordPress Photo Directory". Speckyboy Design Magazine. February 7, 2022. Retrieved April 4, 2022.
149. "WordPress Photo Directory Gets Its Own Make Team". WP Tavern. February 12, 2022. Retrieved April 4, 2022.
150. "WordCamp Central > About". Central.wordcamp.org. May 11, 2010. from the original on July 24, 2019. Retrieved August 18, 2019.
151. "WordCamp 2006". 2006.wordcamp.org. from the original on November 26, 2011. Retrieved December 18, 2011.
152. "WordCamp 2011". 2011.sf.wordcamp.org. from the original on December 9, 2011. Retrieved December 18, 2011.
153. "WordCamp Central > Schedule". Central.wordcamp.org. September 27, 2010. from the original on December 16, 2011. Retrieved December 18, 2011.
154. "WordCamp SF Announced (not WordCon) | WordCamp Central". Central.wordcamp.org. January 24, 2011. from the original on March 16, 2015. Retrieved March 11, 2015.
155. "Regional WordCamps". Make WordPress Communities. August 21, 2017. from the original on September 28, 2018. Retrieved August 18, 2019.
156. "New conferences, Gutenberg news and more! • Yoast". Yoast. October 12, 2018. from the original on October 18, 2018. Retrieved August 18, 2019.
157. "WordCamp Nordic 2019 to be Held in Helsinki, March 7-8". WordPress Tavern. October 12, 2018. from the original on July 14, 2019. Retrieved August 18, 2019.
158. "WordCamp Asia Set for February 21-23, 2020, in Bangkok, Thailand". WordPress Tavern. July 24, 2019. from the original on July 25, 2019. Retrieved August 18, 2019.
159. Takano, Naoko (February 12, 2020). "WordCamp Asia 2020 Cancellation: Event Ticket and Travel Refunds". WordCamp Asia 2020. Retrieved February 20, 2020.
160. "WordPress Codex". WordPress.org. from the original on March 12, 2014. Retrieved March 13, 2014.
161. "WordPress Forums". WordPress.org. from the original on March 13, 2014. Retrieved March 13, 2014.

External links

• Official website