WordPress

From Wikipedia, the free encyclopedia
Jump to: navigation, search
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; 13 years ago (2003-05-27)[1]
Stable release 4.5.3 (June 21, 2016; 32 days ago (2016-06-21)) [±][2]
Preview release 4.6 Beta 1 (June 30, 2016; 23 days ago (2016-06-30)) [±][3]
Development status Active
Operating system Cross-platform
Platform PHP
Type Blog software, Content Management System, Content Management Framework
License GNU GPLv2+[4]
Proprietary (for web hosting)
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; 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. Features include a plugin architecture and a template system. WordPress was used by more than 26.4% of the top 10 million websites as of April 2016.[7] WordPress is the most popular blogging system in use on the Web,[8] at more than 60 million websites.[9]

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

Overview[edit]

WordPress has a web template system using a template processor. Once downloaded, WordPress installation files have a size of 19.9MB

Themes[edit]

WordPress users may install and switch between different 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.[12] 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[edit]

WordPress's plugin architecture allows users to extend the features and functionality of a website or blog. WordPress has over 40,501 plugins available,[13] 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,[14] 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.[15]

Mobiles[edit]

Native applications exist for WebOS,[16] Android,[17] iOS (iPhone, iPod Touch, iPad),[18][19] Windows Phone, and BlackBerry.[20] 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.[18][19]

Other features[edit]

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[edit]

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[21] (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.[22]

Migration/wp-config.php[edit]

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

  • 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[edit]

b2/cafelog, more commonly known as b2 or cafelog, was the precursor to WordPress.[25] b2/cafelog was estimated to have been installed on approximately 2,000 blogs as of May 2003.[26] 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.[27] Christine Selleck Tremoulet, a friend of Mullenweg, suggested the name WordPress.[28][29]

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.[30][31] 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 January 2015, more than 23.3% of the top 10 million websites now use WordPress.[32]

As of February 2016, WordPress is used by 59.1% of all the websites whose content management system we know. This is 25.8% of all websites.[33]

Release history[edit]

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

Legend: Old version Older version, still supported Current stable version Latest preview version Future release
Version Code name Release date Notes
Old version, no longer supported: 0.7 none May 27, 2003[35] Used the same file structure as its predecessor, b2/cafelog, and continued the numbering from its last release, 0.6.[36] Only 0.71-gold is available for download in the official WordPress Release Archive page.
Old version, no longer supported: 1.0 Davis January 3, 2004[37] 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 May 22, 2004[38] 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 February 17, 2005[39] 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).[40] designed by Michael Heilemann.
Old version, no longer supported: 2.0 Duke December 31, 2005[41] 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 January 22, 2007[42] 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 May 16, 2007[43] Added widget support for templates, updated Atom feed support, and speed optimizations.
Old version, no longer supported: 2.3 Dexter September 24, 2007[44] 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 March 29, 2008[45] 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 July 15, 2008[46] 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 December 11, 2008[47] Administration interface redesigned fully, added automatic upgrades and installing plugins, from within the administration interface.
Old version, no longer supported: 2.8 Baker June 10, 2009[48] 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 December 19, 2009[49] Added global undo, built-in image editor, batch plugin updating, and many less visible tweaks.
Old version, no longer supported: 3.0 Thelonious June 17, 2010[50] 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 February 23, 2011[51] 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 July 4, 2011[52] 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 December 12, 2011[53] Focused on making WordPress friendlier for beginners and tablet computer users.
Old version, no longer supported: 3.4 Green June 13, 2012[54] Focused on improvements to Theme customization, Twitter integration and several minor changes.
Old version, no longer supported: 3.5 Elvin December 11, 2012[55] Support for the Retina Display, color picker, new default theme "Twenty Twelve", improved image workflow.
Old version, no longer supported: 3.6 Oscar August 1, 2013[56] 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 supported: 3.7 Basie October 24, 2013[57] 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.
Old version, no longer supported: 3.8 Parker December 12, 2013[58] 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 supported: 3.9 Smith April 16, 2014[59] Improvements to editor for media, live widget and header previews, new theme browser.
Old version, no longer supported: 4.0 Benny September 4, 2014[60] Improved media management, embeds, writing interface, easy language change, theme customizer, plugin discovery and compatibility with PHP 5.5 and MySQL 5.6.[61]
Old version, no longer supported: 4.1 Dinah December 18, 2014[62] Twenty Fifteen as the new default theme, distraction-free writing, easy language switch, Vine embeds and plugin recommendations.
Old version, no longer supported: 4.2 Powell April 23, 2015[63] New "Press This" features, improved characters support, emoji support, improved customizer, new embeds and updated plugin system.
Old version, no longer supported: 4.3 Billie August 18, 2015[64] Focus on mobile experience, better passwords and improved customizer.
Old version, no longer supported: 4.4 Clifford December 8, 2015[65] Introduction of Twenty Sixteen theme, and improved responsive images and embeds.
Current stable version: 4.5 Coleman April 12, 2016[66] Added inline linking, formatting shortcuts, live responsive previews, and other updates under the hood.

Future[edit]

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

Vulnerabilities[edit]

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

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.[73] 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.[74]

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

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.[78]

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.[79]

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

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,[81] 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.[82][83][84]

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.

In March 2015, it was reported by many security experts and SEOs including Search Engine Land that a SEO plugin for WordPress called WordPress SEO by 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.

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.[85]

WordPress's minimum PHP version requirement is PHP 5.2,[86] which was released on January 6, 2006,[87] 10 years ago, and which has been unsupported by the PHP Group and not received any security patches since January 6, 2011, 5 years ago.[87]

Development and support[edit]

Key developers[edit]

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.[88][89]

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

A WordCamp in Sofia, Bulgaria (2011)

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

Support[edit]

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,[96] and WordPress Forums, an active online community of WordPress users.[97][98]

See also[edit]

References[edit]

  1. ^ a b Mullenweg, Matt. "WordPress Now Available". WordPress. Retrieved July 22, 2010. 
  2. ^ Silverstein, Adam (2016-04-26). "WordPress 4.5.3 Maintenance and Security Release". WordPress. Retrieved 2016-04-26. 
  3. ^ Schilling, Dominik (2016-06-30). "WordPress 4.6 Beta 1". WordPress. Retrieved 2016-07-06. 
  4. ^ "WordPress: About: GPL". WordPress.org. Retrieved June 15, 2010. 
  5. ^ "WordPress Web Hosting". WordPress. Retrieved May 21, 2013. 
  6. ^ "Support disaggregating WordPress.com and WordPress.org". WordPress.com. Retrieved January 2016. 
  7. ^ "Usage Statistics and Market Share of Content Management Systems for Websites". W3Techs. January 2015. Retrieved January 2015. 
  8. ^ "CMS Usage Statistics". BuiltWith. Retrieved August 1, 2013. 
  9. ^ Coalo, J.J (September 5, 2012). "With 60 Million Websites, WordPress Rules The Web. So Where's The Money?". Forbes. Retrieved February 3, 2016. 
  10. ^ "Commit number 8". Retrieved February 3, 2016. 
  11. ^ "WordPress › About » License". WordPress.org. Retrieved June 30, 2014. 
  12. ^ "Theme Installation". Codex.wordpress.org. April 9, 2013. Retrieved April 26, 2013. 
  13. ^ "WordPress > WordPress Plugins". WordPress.org. Retrieved October 5, 2015. 
  14. ^ "WordPress custom meta boxes and custom fields plugin". March 1, 2014. Retrieved March 1, 2014. 
  15. ^ "Pros and Cons of WordPress". September 14, 2014. Retrieved October 21, 2014. 
  16. ^ "WordPress for WebOS". WordPress. Retrieved March 6, 2012. 
  17. ^ "WordPress publishes native Android application". Android and Me. February 2, 2010. Retrieved June 15, 2010. 
  18. ^ a b "Idea: WordPress App For iPhone and iPod Touch". WordPress iPhone & iPod Touch. July 12, 2008. Retrieved February 9, 2016. 
  19. ^ a b "18 Million WordPress Blogs Land on the iPad". ReadWriteWeb. March 24, 2011. 
  20. ^ "WordPress for BlackBerry". WordPress. Retrieved December 27, 2009. 
  21. ^ "MultiSite In WordPress 3.0". Deluxe Blog Tips. May 3, 2010. 
  22. ^ "WordPress 3.0 "Thelonious"". WordPress.org. June 17, 2010. Retrieved December 18, 2011. 
  23. ^ "Editing wp-config.php". WordPress.org. Retrieved January 12, 2016. 
  24. ^ "Moving WordPress to a new server". SquirrelHosting.co.uk. March 17, 2014. Retrieved January 12, 2016. 
  25. ^ 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. Retrieved September 28, 2009. b2 had actually, through a series of circumstances, essentially become abandoned. 
  26. ^ Valdrighi, Michel. "b2 test weblog - post dated 23.05.03". Retrieved May 9, 2013. 
  27. ^ "History - WordPress Codex". WordPress.org. Retrieved March 29, 2012. 
  28. ^ Silverman, Dwight (January 24, 2008). "The importance of being Matt". Houston Chronicle. Retrieved August 14, 2014. 
  29. ^ Tremoulet, Christine Selleck (January 24, 2008). "The Importance of Being Matt…". Christine Selleck Tremoulet. Retrieved March 29, 2012. 
  30. ^ Manjoo, Farhad (August 9, 2004). "Blogging grows up". Salon. Retrieved March 29, 2012. 
  31. ^ Pilgrim, Mark (May 14, 2004). "Freedom 0". Mark Pilgrim. Archived from the original on April 10, 2006. Retrieved March 29, 2012. 
  32. ^ "Beginner’s Guide to Starting a WordPress Blog". Retrieved November 15, 2015. 
  33. ^ "Usage statistics and market share of WordPress for websites". Retrieved February 7, 2016. 
  34. ^ "Roadmap". Blog. WordPress.org. Retrieved June 15, 2010. 
  35. ^ "WordPress Blog: WordPress 0.7". WordPress.org. Retrieved May 27, 2003. 
  36. ^ "Cafelog". Retrieved May 15, 2011. 
  37. ^ "WordPress Blog: WordPress 1.0". WordPress.org. Retrieved January 3, 2004. 
  38. ^ "WordPress Blog: WordPress 1.2". WordPress.org. Retrieved May 22, 2004. 
  39. ^ "WordPress Blog: WordPress 1.5". WordPress.org. Retrieved February 17, 2005. 
  40. ^ "Kubrick at Binary Bonsai". Binarybonsai.com. Retrieved June 15, 2010. 
  41. ^ "WordPress Blog: WordPress 2.0". WordPress.org. Retrieved December 31, 2005. 
  42. ^ "WordPress Blog: WordPress 2.1". WordPress.org. Retrieved January 22, 2007. 
  43. ^ "WordPress Blog: WordPress 2.2". WordPress.org. Retrieved May 16, 2007. 
  44. ^ "WordPress Blog: WordPress 2.3". WordPress.org. Retrieved September 24, 2007. 
  45. ^ "WordPress Blog: WordPress 2.5". WordPress.org. Retrieved March 29, 2008. 
  46. ^ "WordPress Blog: WordPress 2.6". WordPress.org. Retrieved June 15, 2008. 
  47. ^ "WordPress Blog: WordPress 2.7". WordPress.org. Retrieved December 11, 2008. 
  48. ^ "WordPress Blog: WordPress 2.8". WordPress.org. Retrieved June 10, 2009. 
  49. ^ "WordPress Blog: WordPress 2.9". WordPress.org. Retrieved December 19, 2009. 
  50. ^ "WordPress Blog: WordPress 3.0". WordPress.org. Retrieved June 17, 2010. 
  51. ^ "WordPress Blog: WordPress 3.1". WordPress.org. Retrieved February 25, 2011. 
  52. ^ "WordPress Blog: WordPress 3.2". WordPress.org. Retrieved June 4, 2011. 
  53. ^ "WordPress Blog: WordPress 3.3". WordPress.org. Retrieved December 12, 2011. 
  54. ^ "WordPress Blog: WordPress 3.4". WordPress.org. Retrieved June 13, 2012. 
  55. ^ "WordPress Blog: WordPress 3.5". WordPress.org. Retrieved December 11, 2012. 
  56. ^ "WordPress Blog: WordPress 3.6". WordPress.org. Retrieved August 1, 2013. 
  57. ^ "WordPress Blog: WordPress 3.7". WordPress.org. Retrieved October 24, 2013. 
  58. ^ "WordPress Blog: WordPress 3.8". WordPress.org. Retrieved December 12, 2013. 
  59. ^ "WordPress Blog: WordPress 3.9". WordPress.org. Retrieved April 16, 2014. 
  60. ^ "WordPress Blog: WordPress 4.0". WordPress.org. Retrieved September 4, 2014. 
  61. ^ "Learn What’s New in WordPress v4.0". Retrieved March 14, 2016. 
  62. ^ "WordPress Blog: WordPress 4.1". WordPress.org. Retrieved December 18, 2014. 
  63. ^ "WordPress Blog: WordPress 4.2". WordPress.org. Retrieved April 23, 2015. 
  64. ^ "WordPress Blog: WordPress 4.3". WordPress.org. Retrieved August 18, 2015. 
  65. ^ "WordPress Blog: WordPress 4.4". WordPress.org. Retrieved December 8, 2015. 
  66. ^ "WordPress Blog: WordPress 4.5". WordPress.org. Retrieved April 26, 2016. 
  67. ^ "Radically Simplified WordPress". Ma.tt. Retrieved March 11, 2015. 
  68. ^ "Matt Mullenweg: State of the Word 2013". WordPress.tv. Retrieved March 11, 2015. 
  69. ^ "David Kierznowski". Blogsecurity.net. June 28, 2007. Archived from the original on March 9, 2012. Retrieved February 17, 2016. 
  70. ^ "Secunia Advisories for WordPress 2.x". Secunia.com. April 7, 2009. Retrieved March 11, 2015. 
  71. ^ "Secunia WordPress 2.x Vulnerability Report". Secunia.com. Retrieved June 15, 2010. 
  72. ^ "Secunia WordPress 3.x Vulnerability Report". Secunia.com. Retrieved December 27, 2010. 
  73. ^ "WordPress Exploit Nails Big Name Seo Bloggers". Threadwatch.org. Retrieved December 18, 2011. 
  74. ^ "WordPress 2.1.1 dangerous, Upgrade to 2.1.2". WordPress.org. March 2, 2007. Retrieved March 4, 2007. 
  75. ^ "Survey Finds Most WordPress Blogs Vulnerable". Blog Security. May 23, 2007. Archived from the original on October 18, 2012. Retrieved June 15, 2010. 
  76. ^ "Updating WordPress". WordPress Codex. Retrieved September 25, 2012. 
  77. ^ "Yet another WordPress release". August 13, 2009. Retrieved September 24, 2012. 
  78. ^ "Interview with Stefan Esser". BlogSecurity. June 28, 2007. Archived from the original on October 30, 2012. Retrieved June 15, 2010. 
  79. ^ Robert Westervelt (June 18, 2013). "Popular WordPress E-Commerce Plugins Riddled With Security Flaws - Page: 1". CRN. Retrieved March 11, 2015. 
  80. ^ "Configuring Automatic Background Updates « WordPress Codex". Codex.wordpress.org. Retrieved June 30, 2014. 
  81. ^ Ward, Simon (July 9, 2012). "Original Free WordPress Security Infographic by Pingable". Pingable. Retrieved October 28, 2012. 
  82. ^ "How To Scan WordPress Like A Hacker". 
  83. ^ "How To Manually Update WordPress Plugins". 
  84. ^ "Top 5 WordPress Vulnerabilities and How to Fix Them". eSecurityPlanet.com. April 20, 2012. Retrieved April 20, 2012. 
  85. ^ Barry Schwartz "Yoast WordPress SEO Plugin Vulnerable To Hackers", Retrieved on February 13, 2016.
  86. ^ "WordPress › About » Requirements". wordpress.org. Retrieved December 30, 2015. 
  87. ^ a b "Unsupported Branches". php.net. Retrieved November 14, 2015. 
  88. ^ "About WordPress". wordpress.org. Retrieved March 18, 2015. 
  89. ^ "Core Team". codex.wordpress.org. Retrieved August 27, 2015. 
  90. ^ "Installing WordPress". August 2014. 
  91. ^ a b "WordCamp Central > About". Central.wordcamp.org. Retrieved October 28, 2015. 
  92. ^ "WordCamp 2006". 2006.wordcamp.org. Retrieved December 18, 2011. 
  93. ^ "WordCamp 2011". 2011.sf.wordcamp.org. Retrieved December 18, 2011. 
  94. ^ "WordCamp Central > Schedule". Central.wordcamp.org. Retrieved December 18, 2011. 
  95. ^ "WordCamp SF Announced (not WordCon) | WordCamp Central". Central.wordcamp.org. January 24, 2011. Retrieved March 11, 2015. 
  96. ^ "WordPress Codex". WordPress.org. Retrieved March 13, 2014. 
  97. ^ "WordPress Forums". WordPress.org. Retrieved March 13, 2014. 
  98. ^ "WordPress Performance". yourescapefrom9to5.com. Retrieved May 13, 2015. 

External links[edit]