WordPress

From Infogalactic: the planetary knowledge core
(Redirected from Wordpress)
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

This article is about the blogging software. For the blog host, see WordPress.com.
WordPress
WordPress logo.svg
WordPress MP6 dashboard.png
WordPress Dashboard
Developer(s) WordPress Foundation
Initial release May 27, 2003; 21 years ago (2003-05-27)[1]
Stable release 4.5.2 (May 6, 2016; 8 years ago (2016-05-06)) [±][2]
Preview release 4.5 Beta 2 (March 3, 2016; 8 years ago (2016-03-03)) [±][3]
Development status Active
Operating system Cross-platform
Platform PHP
Type Blog software, Content Management System, Content Management Framework
License GNU GPLv2+[4]
Website wordpress.org

WordPress is a free and open-source content management system (CMS) based on PHP and MySQL.[5] Wordpress is installed on a web server, which either is part of an Internet hosting service or is a network host itself Host_(network); the first case may be on a service like Wordpress.com, for example, and the second case is a computer running the software package Wordpress.org. [6] An example of the second case is a local computer configured to act as its own web server hosting Wordpress for single-user testing or learning purposes.[7][8] Features include a plugin architecture and a template system. WordPress was used by more than 23.3% of the top 10 million websites as of January 2015.[9] WordPress is the most popular blogging system in use on the Web,[10] at more than 60 million websites.[11]

It was released on May 27, 2003, by its founders, Matt Mullenweg[1] and Mike Little,[12] as a fork of b2/cafelog. The license under which WordPress software is released is the GPLv2 (or later) from the Free Software Foundation.[13]

Overview

WordPress has a web template system using a template processor.

Themes

WordPress users may install and switch between themes. Themes allow users to change the look and functionality of a WordPress website and they can be installed without altering the content or health of the site. 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 and Cascading Style Sheets (CSS). Themes may be directly installed using the WordPress "Appearance" administration tool in the dashboard or theme folders may be uploaded via FTP.[14] The PHP, HTML (HyperText Markup Language) and CSS code found in themes can be added to or edited for providing advanced features. WordPress themes are in general classified into two categories, free themes and premium themes. All the free themes are listed in the WordPress theme directory and premium themes should be purchased from marketplaces and individual WordPress developers. WordPress users may also create and develop their own custom themes if they have the knowledge and skill to do so. If WordPress users do not have themes development knowledge then they may download and use free WordPress themes from wordpress.org.

Plugins

WordPress's plugin architecture allows users to extend the features and functionality of a website or blog. WordPress has over 40,501 plugins available,[15] 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 portals used to display private information to logged in users, to content management systems,[16] to content displaying features, such as the addition of widgets and navigation bars. But 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.[17] Plugins transform WordPress into a powerful CMS and can be used for any kind of websites, not only blogs. WordPress encourages developers to submit a plugin, either free or paid, to the depository subject to a manual review.[18]

Mobiles

Native applications exist for WebOS,[19] Android,[20] iOS (iPhone, iPod Touch, iPad),[21][22] Windows Phone, and BlackBerry.[23] These applications, designed by Automattic, allow a limited set of options, which include adding new blog posts and pages, commenting, moderating comments, replying to comments in addition to the ability to view the stats.[21][22]

Other features

WordPress also features integrated link management; a search engine–friendly, clean permalink structure; the ability to assign multiple categories to articles; and support for tagging of posts and articles. Automatic filters are also included, providing standardized formatting and styling of text in articles (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 blog 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[24] (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.[25]

Migration/wp-config.php

WordPress makes migration from one server to another relatively simple due to its use of a configuration file (wp-config.php, usually located in your root). This file controls the base settings for a WordPress website including (but not limited to) your database connection settings. [26] Due to the use of a configuration file, migrating from one server to another can be accomplished by the following basic steps: [27]

  • Download a copy of the WordPress files/folders (e.g. via FTP).
  • Download a copy of the associated database (view the 'DB_NAME' row in the wp-config.php for the associated database to back up).
  • Upload the files/folders to the new server.
  • Create a new database on the new server and import the sql backup.
  • Update the wp-config.php database fields to reflect.

History

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

WordPress first appeared in 2003 as a joint effort between Matt Mullenweg and Mike Little to create a fork of b2.[30] Christine Selleck Tremoulet, a friend of Mullenweg, suggested the name WordPress.[31][32]

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.[33][34] By October 2009 the Open Source CMS MarketShare Report concluded that WordPress enjoyed the greatest brand strength of any open-source content-management system.[35]

As of January 2015, more than 23.3% of the top 10 million websites now use WordPress.[36]

Release history

Main releases of WordPress are codenamed after well-known jazz musicians, starting after version 1.0.[37]

Legend: Old version Older version, still supported Current version Latest preview version Future release
Version Code name Release date Notes
Old version, no longer supported: 0.7 none 27 May 2003 [38] Used the same file structure as its predecessor, b2/cafelog, and continued the numbering from its last release, 0.6.[39] Only 0.71-gold is available for download in the official WordPress Release Archive page.
Old version, no longer supported: 1.0 Davis 3 January 2004 [40] Added search engine friendly permalinks, multiple categories, dead simple installation and upgrade, comment moderation, XFN support, Atom support.
Old version, no longer supported: 1.2 Mingus 22 May 2004 [41] Added support of Plugins; which same identification headers are used unchanged in WordPress releases as of 2011.
Old version, no longer supported: 1.5 Strayhorn 17 February 2005 [42] 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 Kubrick).[43] designed by Michael Heilemann.
Old version, no longer supported: 2.0 Duke 31 December 2005 [44] 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 supported: 2.1 Ella 22 January 2007 [45] Corrected security issues, redesigned interface, enhanced editing tools (including integrated spell check and auto save), and improved content management options.
Old version, no longer supported: 2.2 Getz 16 May 2007 [46] Added widget support for templates, updated Atom feed support, and speed optimizations.
Old version, no longer supported: 2.3 Dexter 24 September 2007 [47] 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 supported: 2.5 Brecker 29 March 2008 [48] Major revamp to the dashboard, dashboard widgets, multi-file upload, extended search, improved editor, improved plugin system and more.
Old version, no longer supported: 2.6 Tyner 15 July 2008 [49] 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 supported: 2.7 Coltrane 11 December 2008 [50] Administration interface redesigned fully, added automatic upgrades and installing plugins, from within the administration interface.
Old version, no longer supported: 2.8 Baker 10 June 2009 [51] Added improvements in speed, automatic installing of themes from within administration interface, introduces the CodePress editor for syntax highlighting and a redesigned widget interface.
Old version, no longer supported: 2.9 Carmen 19 December 2009 [52] Added global undo, built-in image editor, batch plugin updating, and many less visible tweaks.
Old version, no longer supported: 3.0 Thelonious 17 June 2010 [53] Added a new theme APIs, merge 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 supported: 3.1 Reinhardt 23 February 2011 [54] 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 supported: 3.2 Gershwin 4 July 2011 [55] 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 supported: 3.3 Sonny 12 December 2011 [56] Focused on making WordPress friendlier for beginners and tablet computer users.
Old version, no longer supported: 3.4 Green 13 June 2012 [57] Focused on improvements to Theme customization, Twitter integration and several minor changes.
Old version, no longer supported: 3.5 Elvin 11 December 2012 [58] Support for the Retina Display, color picker, new default theme "Twenty Twelve", improved image workflow.
Old version, no longer supported: 3.6 Oscar 1 August 2013 [59] New default theme "Twenty Thirteen", admin enhancements, post formats UI update, menus UI improvements, new revision system, autosave and post locking.
Older version, yet still supported: 3.7 Basie 24 October 2013 [60] 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.
Older version, yet still supported: 3.8 Parker 12 December 2013 [61] 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".
Older version, yet still supported: 3.9 Smith 16 April 2014 [62] Improvements to editor for media, live widget and header previews, new theme browser.
Older version, yet still supported: 4.0 Benny 4 September 2014 [63] Improved media management, embeds, writing interface, and plugin discovery.
Older version, yet still supported: 4.1 Dinah 18 December 2014 [64] Twenty Fifteen as the new default theme, distraction-free writing, easy language switch, Vine embeds and plugin recommendations.
Older version, yet still supported: 4.2 Powell 23 April 2015 [65] New "Press This" features, improved characters support, emoji support, improved customizer, new embeds and updated plugin system.
Older version, yet still supported: 4.3 Billie 18 August 2015 [66] Focus on mobile experience, better passwords and improved customizer.
Current stable version: 4.4 Clifford 8 December 2015 [67] Introduction of Twenty Sixteen theme, and improved responsive images and embeds.
Future release: 4.5 TBA April 2016 [68]

Future

Matt Mullenweg has stated that the future of WordPress is in social, mobile, and as an application platform.[69][70]

Vulnerabilities

Many security issues[71][72] have been uncovered in the software, particularly in 2007 and 2008. According to Secunia, WordPress in April 2009 had 7 unpatched security advisories (out of 32 total), with a maximum rating of "Less Critical."[73] Secunia maintains an up-to-date list of WordPress vulnerabilities.[74][75]

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.[76] 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.[77]

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.[78] 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).[79] However, the filesystem security settings required to enable the update process can be an additional risk.[80]

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

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 7 of them were vulnerable.[82]

In an effort to promote better security, and to streamline the update experience overall, automatic background updates were introduced in WordPress 3.7.[83]

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,[84] 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 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.[85][86][87]

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 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.

WordPress's minimum PHP version requirement is PHP 5.2,[88] which was released in 6 January 2006,[89] Expression error: Unexpected < operator., and which has been unsupported by the PHP Group and not received any security patches since 6 January 2011, Expression error: Unexpected < operator..[89]

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.[90][91]

WordPress is also developed by its community, including WP testers, a group of volunteers who test each release.[92] 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. 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

A WordCamp in Sofia, Bulgaria (2011)

WordCamps are casual, locally-organized conferences covering everything related to WordPress.[93] The first such event was WordCamp 2006 in August 2006 in San Francisco, which lasted one day and had over 500 attendees.[94][95] The first WordCamp outside San Francisco was held in Beijing in September 2007.[96] Since then, there have been over 507 WordCamps in over 207 cities in 48 different countries around the world.[93] 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.[97][98]

Support

WordPress's 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,[99] and WordPress Forums, an active online community of WordPress users.[100][101]

See also

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ 89.0 89.1 Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  91. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  92. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  93. ↑ 93.0 93.1 Lua error in package.lua at line 80: module 'strict' not found.
  94. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  95. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  96. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  97. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  98. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  99. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  100. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  101. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Find out more on Wikipedia's
Sister projects
Commons-logo.svg Media
from Commons
Wikispecies-logo.svg Species directories
from Wikispecies
Wikivoyage-Logo-v3-icon.svg Travel guides
from Wikivoyage
Wikinews-logo.svg News stories
from Wikinews
Wiktionary-logo-en.svg Definitions
from Wiktionary
Wikiquote-logo.svg Quotations
from Wikiquote
Wikisource-logo.svg Source texts
from Wikisource
Retrieved from "https://infogalactic.com/w/index.php?title=WordPress&oldid=726437537"