<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[6653] sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main: Main: Make use of child page template struture.</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta" style="font-size: 105%">
<dt style="float: left; width: 6em; font-weight: bold">Revision</dt> <dd><a style="font-weight: bold" href="http://meta.trac.wordpress.org/changeset/6653">6653</a><script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","description":"Review this Commit","action":{"@type":"ViewAction","url":"http://meta.trac.wordpress.org/changeset/6653","name":"Review Commit"}}</script></dd>
<dt style="float: left; width: 6em; font-weight: bold">Author</dt> <dd>obenland</dd>
<dt style="float: left; width: 6em; font-weight: bold">Date</dt> <dd>2018-02-16 05:03:05 +0000 (Fri, 16 Feb 2018)</dd>
</dl>
<pre style='padding-left: 1em; margin: 2em 0; border-left: 2px solid #ccc; line-height: 1.25; font-size: 105%; font-family: sans-serif'>Main: Make use of child page template struture.
Lessens the footprint about page templates have on Rosetta sites.
See <a href="http://meta.trac.wordpress.org/changeset/6652">[6652]</a>, <a href="http://meta.trac.wordpress.org/ticket/3046">#3046</a>.</pre>
<h3>Added Paths</h3>
<ul>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutdomainsphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-domains.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutetiquettephp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-etiquette.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutfeaturesphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-features.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutgplphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-gpl.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageabouthistoryphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-history.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutlicensephp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-license.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutphilosophyphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-philosophy.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutprivacyphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-privacy.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutrequirementsphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-requirements.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutroadmapphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-roadmap.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutsecurityphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutstatsphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-stats.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutswagphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-swag.php</a></li>
</ul>
<h3>Removed Paths</h3>
<ul>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagedomainsphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-domains.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageetiquettephp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-etiquette.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagefeaturesphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-features.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagegplphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-gpl.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagehistoryphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-history.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagelicensephp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-license.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagephilosophyphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-philosophy.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageprivacyphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-privacy.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagerequirementsphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-requirements.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageroadmapphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-roadmap.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagesecurityphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-security.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagestatsphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-stats.php</a></li>
<li><a href="#sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageswagphp">sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-swag.php</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutdomainsphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagedomainsphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-domains.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-domains.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-domains.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-domains.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,62 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Domains
+ *
+ * Page template for displaying the Domains page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'WordPress Domains', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p><?php echo wp_kses_post( ___( 'For various reasons related to our WordPress trademark, we ask if you’re going to start a site about WordPress or related to it that you <strong>not</strong> use “WordPress” in the domain name. Try using “wp” instead, or another variation. We’re not lawyers, but very good ones tell us we have to do this to preserve our trademark. Also, many users have told us they find it confusing.', 'wporg' ) ); ?></p>
+
+ <p><?php _esc_html_e( 'If you already have a domain with “WordPress” in it, redirecting it to the “wp” equivalent is fine, just as long as the main one users see and you promote doesn’t contain “WordPress” and in the long term you should consider transferring the old one to the Foundation.', 'wporg' ); ?></p>
+
+ <p>
+ <?php
+ echo wp_kses_post( ___( '“WordPress” in sub-domains is fine, like <code>wordpress.example.com</code>, we’re just concerned about top-level domains.', 'wporg' ) ); // phpcs:ignore WordPress.WP.CapitalPDangit.Misspelled
+ ?>
+ </p>
+
+ <p><?php _esc_html_e( 'We’ve told this to anyone who has ever asked us, we just wanted to make it public so more people could be aware of this policy.', 'wporg' ); ?></p>
+
+ <p><strong><?php _esc_html_e( '<whine>Other domains are using WordPress in them!</whine>', 'wporg' ); ?></strong></p>
+ <p><?php _esc_html_e( 'If they’re not WordPress.com, WordPress.net, WordPress.org, WordPress.tv, or WordPressFoundation.org, they’re not allowed, and you should contact the owner with a pointer to this page. We see this most frequently with spammy sites distributing plugins and themes with malware in them, which you probably don’t want to be associated with.', 'wporg' ); ?></p>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutetiquettephpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageetiquettephp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-etiquette.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-etiquette.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-etiquette.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-etiquette.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,76 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Etiquette
+ *
+ * Page template for displaying the Etiquette page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Etiquette', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p>
+ <?php
+ /* translators: Link to blog post */
+ printf( wp_kses_post( ___( 'In the WordPress open source project, we realize that our biggest asset is the community that we foster. The project, as a whole, follows these basic philosophical principles from <a href="%s">The Cathedral and The Bazaar</a>.', 'wporg' ) ), esc_url( 'http://www.catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/index.html' ) );
+ ?>
+ </p>
+
+ <ul>
+ <li><?php _esc_html_e( 'Contributions to the WordPress open source project are for the benefit of the WordPress community as a whole, not specific businesses or individuals. All actions taken as a contributor should be made with the best interests of the community in mind.', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'Participation in the WordPress open source project is open to all who wish to join, regardless of ability, skill, financial status, or any other criteria.', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'The WordPress open source project is a volunteer-run community. Even in cases where contributors are sponsored by companies, that time is donated for the benefit of the entire open source community.', 'wporg' ); ?></li>
+ <li>
+ <?php
+ /* translators: Link to make.wordpress.org */
+ printf( wp_kses_post( ___( 'Any member of the community can donate their time and contribute to the project in any form including design, code, documentation, community building, etc. For more information, go to <a href="%s">make.wordpress.org</a>.', 'wporg' ) ), esc_url( 'https://make.wordpress.org/' ) );
+ ?>
+ </li>
+ <li><?php _esc_html_e( 'The WordPress open source community cares about diversity. We strive to maintain a welcoming environment where everyone can feel included, by keeping communication free of discrimination, incitement to violence, promotion of hate, and unwelcoming behavior.', 'wporg' ); ?></li>
+ </ul>
+
+ <p><?php _esc_html_e( 'There is a project currently underway to create a project-wide code of conduct so that we can ensure the safety of our contributors.', 'wporg' ); ?></p>
+
+ <p>
+ <?php
+ /* translators: 1: Link to community team slack channel; 2: Link to tag archive on make/community */
+ printf( wp_kses_post( ___( 'Meetings are conducted in the <a href="%1$s">#community-team Slack channel</a>, and minutes published on the <a href="%2$s">Make Community blog</a>.', 'wporg' ) ), esc_url( 'https://wordpress.slack.com/messages/community-team' ), esc_url( 'https://make.wordpress.org/community/tag/ccoc/' ) );
+ ?>
+ </p>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutfeaturesphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagefeaturesphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-features.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-features.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-features.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-features.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,155 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Features
+ *
+ * Page template for displaying the Features page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Features', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p class="intro">
+ <?php
+ /* translators: WordPress market share: 29%; */
+ printf( _esc_html__( 'WordPress powers more than %s of the web — a figure that rises every day. Everything from simple websites, to blogs, to complex portals and enterprise websites, and even applications, are built with WordPress.', 'wporg' ), esc_html( WP_MARKET_SHARE . '%' ) );
+ ?>
+ </p>
+
+ <p><?php _esc_html_e( 'WordPress combines simplicity for users and publishers with under-the-hood complexity for developers. This makes it flexible while still being easy-to-use.', 'wporg' ); ?></p>
+
+ <p><?php _esc_html_e( 'The following is a list of some of the features that come as standard with WordPress; however, there are literally thousands of plugins that extend what WordPress does, so the actual functionality is nearly limitless. You are also free to do whatever you like with the WordPress code, extend it or modify in any way or use it for commercial projects without any licensing fees. That is the beauty of free software, free refers not only to price but also the freedom to have complete control over it.', 'wporg' ); ?></p>
+
+ <p><?php _esc_html_e( 'Here are some of the features that we think that you’ll love.', 'wporg' ); ?></p>
+
+ <ul>
+ <li><strong><?php _esc_html_e( 'Simplicity', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'Simplicity makes it possible for you to get online and get publishing, quickly. Nothing should get in the way of you getting your website up and your content out there. WordPress is built to make that happen.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Flexibility', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'With WordPress, you can create any type of website you want: a personal blog or website, a photoblog, a business website, a professional portfolio, a government website, a magazine or news website, an online community, even a network of websites. You can make your website beautiful with themes, and extend it with plugins. You can even build your very own application.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Publish with Ease', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'If you’ve ever created a document, you’re already a whizz at creating content with WordPress. You can create Posts and Pages, format them easily, insert media, and with the click of a button your content is live and on the web.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Publishing Tools', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'WordPress makes it easy for you to manage your content. Create drafts, schedule publication, and look at your post revisions. Make your content public or private, and secure posts and pages with a password.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'User Management', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'Not everyone requires the same access to your website. Administrators manage the site, editors work with content, authors and contributors write that content, and subscribers have a profile that they can manage. This lets you have a variety of contributors to your website, and let others simply be part of your community.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Media Management', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'They say a picture says a thousand words, which is why it’s important for you to be able to quickly and easily upload images and media to WordPress. Drag and drop your media into the uploader to add it to your website. Add alt text, captions, and titles, and insert images and galleries into your content. We’ve even added a few image editing tools you can have fun with.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Full Standards Compliance', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'Every piece of WordPress generated code is in full compliance with the standards set by the W3C. This means that your website will work in today’s browser, while maintaining forward compatibility with the next generation of browser. Your website is a beautiful thing, now and in the future.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Easy Theme System', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'WordPress comes bundled with two default themes, but if they aren’t for you there’s a theme directory with thousands of themes for you to create a beautiful website. None of those to your taste? Upload your own theme with the click of a button. It only takes a few seconds for you to give your website a complete makeover.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Extend with Plugins', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'WordPress comes packed full of features for every user, for every other feature there’s a plugin directory with thousands of plugins. Add complex galleries, social networking, forums, social media widgets, spam protection, calendars, fine-tune controls for search engine optimization, and forms.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Built-in Comments', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'Your blog is your home, and comments provide a space for your friends and followers to engage with your content. WordPress’s comment tools give you everything you need to be a forum for discussion and to moderate that discussion.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Search Engine Optimized', 'wporg' ); ?></strong>
+ <?php
+ /* translators: Link to Plugin Directory search for SEO */
+ printf( wp_kses_post( ___( 'WordPress is optimized for search engines right out of the box. For more fine-grained SEO control, there are plenty of <a href="%s">SEO plugins</a> to take care of that for you.', 'wporg' ) ), esc_url( 'https://wordpress.org/plugins/search/SEO/' ) );
+ ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Multilingual', 'wporg' ); ?></strong>
+ <?php
+ /* translators: Link to polyglots teams */
+ printf( wp_kses_post( ___( 'WordPress is available in more than 70 languages. If you or the person you’re building the website for would prefer to use WordPress in a language other than English, <a href="%s">that’s easy to do</a>.', 'wporg' ) ), esc_url( 'https://make.wordpress.org/polyglots/teams/' ) );
+ ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Easy Installation and Upgrades', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'WordPress has always been easy to install and upgrade. If you’re happy using an FTP program, you can create a database, upload WordPress using FTP, and run the installer. Not familiar with FTP? Plenty of web hosts offer one-click WordPress installers that let you install WordPress with, well, just one click!', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Importers', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'Using blog or website software that you aren’t happy with? Running your blog on a hosted service that’s about to shut down? WordPress comes with importers for blogger, LiveJournal, Movable Type, TypePad, Tumblr, and WordPress. If you’re ready to make the move, we’ve made it easy for you.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Own Your Data', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'Hosted services come and go. If you’ve ever used a service that disappeared, you know how traumatic that can be. If you’ve ever seen adverts appear on your website, you’ve probably been pretty annoyed. Using WordPress means no one has access to your content. Own your data, all of it — your website, your content, your data.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Freedom', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'WordPress is licensed under the GPL which was created to protect your freedoms. You are free to use WordPress in any way you choose: install it, use it, modify it, distribute it. Software freedom is the foundation that WordPress is built on.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Community', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'As the most popular open source CMS on the web, WordPress has a vibrant and supportive community. Ask a question on the support forums and get help from a volunteer, attend a WordCamp or Meetup to learn more about WordPress, read blogs posts and tutorials about WordPress. Community is at the heart of WordPress, making it what it is today.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Contribute', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'You can be WordPress too! Help to build WordPress, answer questions on the support forums, write documentation, translate WordPress into your language, speak at a WordCamp, write about WordPress on your blog. Whatever your skill, we’d love to have you!', 'wporg' ); ?>
+ </li>
+ </ul>
+ <h3><?php _esc_html_e( 'Developer Features', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'For developers, we’ve got lots of goodies packed under the hood that you can use to extend WordPress in whatever direction takes your fancy.', 'wporg' ); ?></p>
+
+ <ul>
+ <li><strong><?php _esc_html_e( 'Plugin System', 'wporg' ); ?></strong>
+ <?php
+ /* translators: 1: Link to Codex page about APIs; 2: Link to Plugin Directory */
+ printf( wp_kses_post( ___( 'The <a href="%1$s">WordPress APIs</a> make it possible for you to create plugins to extend WordPress. WordPress’s extensibility lies in the thousands of hooks at your disposal. Once you’ve created your plugin, we’ve even got a <a href="%2$s">plugin repository</a> for you to host it on.', 'wporg' ) ), esc_url( 'https://codex.wordpress.org/WordPress_APIs' ), esc_url( home_url( '/plugins/' ) ) );
+ ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Theme System', 'wporg' ); ?></strong>
+ <?php
+ /* translators: 1: Link to Codex page about APIs; 2: Link to Theme Directory */
+ printf( wp_kses_post( ___( 'Create WordPress themes for clients, customers, and for WordPress users. The <a href="%1$s">WordPress API</a> provides the extensibility to create themes as simple or as complex as you wish. If you want to give your theme away for free you can give it to users in the <a href="%2$s">Theme Repository</a>', 'wporg' ) ), esc_url( 'https://codex.wordpress.org/WordPress_APIs' ), esc_url( home_url( '/themes/' ) ) );
+ ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Application Framework', 'wporg' ); ?></strong>
+ <?php _esc_html_e( 'If you want to build an application, WordPress can help with that too. Under the hood WordPress provides a lot of the features that your app will need, things like translations, user management, HTTP requests, databases, URL routing and much, much more.', 'wporg' ); ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'Custom Content Types', 'wporg' ); ?></strong>
+ <?php
+ /* translators: 1: Link to Codex page about Custom Post Types; 2: Link to Codex page about Custom Taxonomies; 3: Link to Codex page about Custom Fields */
+ printf( wp_kses_post( ___( 'WordPress comes with default content types, but for more flexibility you can add a few lines of code to create your own <a href="%1$s">custom post types</a>, <a href="%2$s">taxonomies</a>, and <a href="%3$s">metadata</a>. Take WordPress in whatever direction you wish.', 'wporg' ) ), esc_url( 'https://codex.wordpress.org/Post_Types#Custom_Post_Types' ), esc_url( 'https://codex.wordpress.org/Taxonomies#Custom_Taxonomies' ), esc_url( 'https://codex.wordpress.org/Custom_Fields' ) );
+ ?>
+ </li>
+ <li><strong><?php _esc_html_e( 'The Latest Libraries', 'wporg' ); ?></strong>
+ <?php
+ /* translators: 1: Link to Developer Handbook page about default scripts */
+ printf( wp_kses_post( ___( 'WordPress comes with the <a href="%s">latest script libraries</a> for you to make use of. These include jQuery, Plupload, Underscore.js and Backbone.js. We’re always on the lookout for new tools that developers can use to make a better experience for our users.', 'wporg' ) ), esc_url( 'https://developer.wordpress.org/reference/functions/wp_enqueue_script/#default-scripts-included-and-registered-by-wordpress' ) );
+ ?>
+ </li>
+ </ul>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutgplphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagegplphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-gpl.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-gpl.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-gpl.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-gpl.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,103 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: GPL
+ *
+ * Page template for displaying the GPL page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'GNU General Public License', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p>The GPLv2 (or later) from the <a href="http://www.fsf.org/">Free Software Foundation</a> is the license that the WordPress software is under. Its text follows.</p>
+
+ <p>Version 2, June 1991</p>
+
+ <p>Copyright (C) 1989, 1991 Free Software Foundation, Inc.<br /> 51 Franklin St, Fifth Floor, Boston, MA 02110, USA</p>
+ <p>Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.</p>
+
+ <h3>Preamble</h3>
+
+ <p>The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software — to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation’s software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.</p>
+
+ <p>When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.</p>
+
+ <p>To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.</p>
+
+ <p>For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.</p>
+
+ <p>We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.</p>
+
+ <p>Also, for each author’s protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.</p>
+
+ <p>Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use or not licensed at all.</p>
+
+ <p>The precise terms and conditions for copying, distribution and modification follow.</p>
+
+ <h3>GNU General Public License Terms and Conditions for Copying, Distribution, and Modification</h3>
+
+ <ol start="0">
+
+ <li>This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having
been made by running the Program). Whether that is true depends on what the Program does.</li>
+ <li>You may copy and distribute verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.</li>
+ <li>You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
+ <ol type="a">
+ <li>You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.</li>
+ <li>You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.</li>
+ <li>If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)</li>
+ </ol>
+ These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volum
e of a storage or distribution medium does not bring the other work under the scope of this License.</li>
+ <li>You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
+ <ol type="a">
+ <li>Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,</li>
+ <li>Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,</li>
+ <li>Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object c
ode is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.</li>
+ </ol>
+ </li>
+ <li>You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.</li>
+ <li>You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.</li>
+ <li>Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.</li>
+ <li>If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is int
ended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.</li>
+ <li>If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.</li>
+ <li>The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.</li>
+ <li>If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.</li>
+ <li>BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.</li>
+ <li>IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</li>
+ </ol>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageabouthistoryphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagehistoryphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-history.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-history.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-history.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-history.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,55 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: History
+ *
+ * Page template for displaying the History page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'History', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p class="intro">We’ve been working on a new book about the history of WordPress drawing on dozens of interviews with the original folks involved and extensive research. It’s not ready yet, but for the tenth anniversary of WordPress we’d like to make a chapter available, <em>On forking WordPress, forks in general, early WordPress, and the community</em>, which you can download below in the following formats:</p>
+
+ <ul>
+ <li><a href="chapter3.epub">Chapter 3 - EPUB</a></li>
+ <li><a href="chapter3.mobi">Chapter 3 - MOBI</a></li>
+ <li><a href="chapter3.pdf">Chapter 3 - PDF</a></li>
+ </ul>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutlicensephpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagelicensephp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-license.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-license.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-license.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-license.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,68 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: License
+ *
+ * Page template for displaying the License page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'GNU Public License', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p>
+ <?php
+ /* translators: 1: Link to Free Software Foundation; 2: Link to GPL text */
+ printf( wp_kses_post( ___( 'The license under which the WordPress software is released is the GPLv2 (or later) from the <a href="%1$s">Free Software Foundation</a>. A copy of the license is included with every copy of WordPress, but you can also read <a href="%2$s">the text of the license</a> here.', 'wporg' ) ), esc_url( 'https://www.fsf.org/' ), esc_url( home_url( '/about/gpl/' ) ) );
+ ?>
+ </p>
+
+ <p>
+ <?php
+ /* translators: 1: Link to Drupal; 2: Link to Drupal's licensing faq */
+ printf( wp_kses_post( ___( 'Part of this license outlines requirements for derivative works, such as plugins or themes. Derivatives of WordPress code inherit the GPL license. <a href="%1$s">Drupal</a>, which has the same GPL license as WordPress, has an excellent page on <a href="%2$s">licensing as it applies to themes and modules</a> (their word for plugins).', 'wporg' ) ), esc_url( 'https://drupal.org/' ), esc_url( 'https://drupal.org/licensing/faq/' ) );
+ ?>
+ </p>
+
+ <p>
+ <?php
+ /* translators: 1: Link to Serendipity; 2: Link to Habari */
+ printf( wp_kses_post( ___( 'There is some legal grey area regarding what is considered a derivative work, but we feel strongly that plugins and themes are derivative work and thus inherit the GPL license. If you disagree, you might want to consider a non-GPL platform such as <a href="%1$s">Serendipity</a> (BSD license) or <a href="%2$s">Habari</a> (Apache license) instead.', 'wporg' ) ), esc_url( 'https://www.s9y.org/' ), esc_url( 'http://habariproject.org/en/' ) );
+ ?>
+ </p>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutphilosophyphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagephilosophyphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-philosophy.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-philosophy.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-philosophy.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-philosophy.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,88 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Philosophy
+ *
+ * Page template for displaying the Philosophy page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Philosophy', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <h3 id="box"><?php _esc_html_e( 'Out of the Box', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'Great software should work with little configuration and setup. WordPress is designed to get you up and running and fully functional in no longer than five minutes. You shouldn’t have to battle to use the standard functionality of WordPress.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'We work hard to make sure that every release is in keeping with this philosophy. We ask for as few technical details as possible during the setup process as well as providing full explanations of anything we do ask.', 'wporg' ); ?></p>
+
+ <h3 id="majority"><?php _esc_html_e( 'Design for the Majority', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'Many end users of WordPress are non-technically minded. They don’t know what AJAX is, nor do they care about which version of PHP they are using. The average WordPress user simply wants to be able to write without problems or interruption. These are the users that we design the software for as they are ultimately the ones who are going to spend the most time using it for what it was built for.', 'wporg' ); ?></p>
+
+ <h3 id="decisions"><?php _esc_html_e( 'Decisions, not Options', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'When making decisions these are the users we consider first. A great example of this consideration is software options. Every time you give a user an option, you are asking them to make a decision. When a user doesn’t care or understand the option this ultimately leads to frustration. As developers we sometimes feel that providing options for everything is a good thing, you can never have too many choices, right? Ultimately these choices end up being technical ones, choices that the average end user has no interest in. It’s our duty as developers to make smart design decisions and avoid putting the weight of technical choices on our end users.', 'wporg' ); ?></p>
+
+ <h3 id="clean"><?php _esc_html_e( 'Clean, Lean, and Mean', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'The core of WordPress will always provide a solid array of basic features. It’s designed to be lean and fast and will always stay that way. We are constantly asked "when will X feature be built" or "why isn’t X plugin integrated into the core". The rule of thumb is that the core should provide features that 80% or more of end users will actually appreciate and use. If the next version of WordPress comes with a feature that the majority of users immediately want to turn off, or think they’ll never use, then we’ve blown it. If we stick to the 80% principle then this should never happen.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'We are able to do this because we have a very capable theme and plugin system and a fantastic developer community. Different people have different needs, and having the sheer number of quality WordPress plugins and themes allows users to customize their installations to their taste. That should allow all users to find the remaining 20% and make all WordPress features those they appreciate and use.', 'wporg' ); ?></p>
+
+ <h3 id="simplicity"><?php _esc_html_e( 'Striving for Simplicity', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'We’re never done with simplicity. We want to make WordPress easier to use with every single release. We’ve got a good track record of this, if you don’t believe us then just take a look back at some older versions of WordPress!', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'In past releases we’ve taken major steps to improve ease of use and ultimately make things simpler to understand. One great example of this is core software updates. Updating used to be a painful manual task that was too tricky for a lot of our users. We decided to focus on this and simplified it down to a single click. Now anyone with a WordPress install can perform one click upgrades on both the core of WordPress and plugins and themes.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'We love to challenge ourselves and simplify tasks in ways that are positive for the overall WordPress user experience. Every version of WordPress should be easier and more enjoyable to use than the last.', 'wporg' ); ?></p>
+
+ <h3 id="deadlines"><?php _esc_html_e( 'Deadlines Are Not Arbitrary', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'Deadlines are not arbitrary, they’re a promise we make to ourselves and our users that helps us rein in the endless possibilities of things that could be a part of every release. We aspire to release three major versions a year because through trial and error we’ve found that to be a good balance between getting cool stuff in each release and not so much that we end up breaking more than we add.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'Good deadlines almost always make you trim something from a release. This is not a bad thing, it’s what they’re supposed to do.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'The route of delaying a release for that one-more-feature is a rabbit hole. We did that for over a year once, and it wasn’t pleasant for anybody.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'The more frequent and regular releases are, the less important it is for any particular feature to be in this release. If it doesn’t make it for this one, it’ll just be a few months before the next one. When releases become unpredictable or few and far between, there’s more pressure to try and squeeze in that one more thing because it’s going to be so long before the next one. Delay begets delay.', 'wporg' ); ?></p>
+
+ <h3 id="minority"><?php _esc_html_e( 'The Vocal Minority', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'There’s a good rule of thumb within internet culture called the 1% rule. It states that "the number of people who create content on the internet represents approximately 1% (or less) of the people actually viewing that content".', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'So while we consider it really important to listen and respond to those who post feedback and voice their opinions on forums, they only represent a tiny fraction of our end users. When making decisions on how to move forward with future versions of WordPress, we look to engage more of those users who are not so vocal online. We do this by meeting and talking to users at WordCamps across the globe, this gives us a better balance of understanding and ultimately allows us to make better decisions for everyone moving forward.', 'wporg' ); ?></p>
+
+ <h3 id="gpl"><?php _esc_html_e( 'Our Bill of Rights', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'WordPress is licensed under the General Public License (GPLv2 or later) which provides four core freedoms, consider this as the WordPress "bill of rights":', 'wporg' ); ?></p>
+ <ul>
+ <li><?php _esc_html_e( 'The freedom to run the program, for any purpose.', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'The freedom to study how the program works, and change it to make it do what you wish.', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'The freedom to redistribute.', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'The freedom to distribute copies of your modified versions to others.', 'wporg' ); ?></li>
+ </ul>
+ <p><?php _esc_html_e( 'Part of those licensing requirements include licensing derivative works or things that link core WordPress functions (like themes, plugins, etc.) under the GPL as well, thereby passing on the freedom of use for these works as well.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'Obviously there are those who will try to get around these ideals and restrict the freedom of their users by trying to find loopholes or somehow circumvent the intention of the WordPress licensing, which is to ensure freedom of use. We believe that the community as a whole will reward those who focus on supporting these licensing freedoms instead of trying to avoid them.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'The most responsible use of WordPress community resources would therefore be put to best use by emphasizing high quality contributions that embrace the freedoms provided by the GPL.', 'wporg' ); ?></p>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutprivacyphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageprivacyphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-privacy.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-privacy.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-privacy.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-privacy.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,71 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Privacy
+ *
+ * Page template for displaying the Privacy page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Privacy', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p><?php _esc_html_e( 'WordPress.org websites (collectively “WordPress.org” in this document) refer to sites hosted on the WordPress.org, WordPress.net, WordCamp.org, BuddyPress.org, bbPress.org, and other related domains and subdomains thereof.', 'wporg' ); ?></p>
+
+ <h3><?php _esc_html_e( 'Website Visitors', 'wporg' ); ?></h3>
+ <p>L<?php _esc_html_e( 'ike most website operators, WordPress.org collects non-personally-identifying information of the sort that web browsers and servers typically make available, such as the browser type, language preference, referring site, and the date and time of each visitor request. WordPress.org’s purpose in collecting non-personally identifying information is to better understand how WordPress.org’s visitors use its website. From time to time, WordPress.org may release non-personally-identifying information in the aggregate, e.g., by publishing a report on trends in the usage of its website.', 'wporg' ); ?></p>
+
+ <p><?php _esc_html_e( 'WordPress.org also collects potentially personally-identifying information like Internet Protocol (IP) addresses. WordPress.org does not use such information to identify its visitors, however, and does not disclose such information, other than under the same circumstances that it uses and discloses personally-identifying information, as described below.', 'wporg' ); ?></p>
+
+ <h3><?php _esc_html_e( 'Gathering of Personally-Identifying Information', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'Certain visitors to WordPress.org choose to interact with WordPress.org in ways that require WordPress.org to gather personally-identifying information. The amount and type of information that WordPress.org gathers depends on the nature of the interaction. For example, we ask visitors who use our forums to provide a username and email address. In each case, WordPress.org collects such information only insofar as is necessary or appropriate to fulfill the purpose of the visitor’s interaction with WordPress.org. WordPress.org does not disclose personally-identifying information other than as described below. And visitors can always refuse to supply personally-identifying information, with the caveat that it may prevent them from engaging in certain website-related activities.', 'wporg' ); ?></p>
+
+ <h3><?php _esc_html_e( 'Aggregated Statistics', 'wporg' ); ?></h3>
+ <p><?php echo wp_kses_post( ___( 'WordPress.org may collect statistics about the behavior of visitors to its websites. For instance, WordPress.org may reveal how many downloads a particular version got, or say which plugins are most popular based on checks from <code>api.wordpress.org</code>, a web service used by WordPress installations to check for new versions of WordPress and plugins. However, WordPress.org does not disclose personally-identifying information other than as described below.', 'wporg' ) ); ?></p>
+
+ <h3><?php _esc_html_e( 'Protection of Certain Personally-Identifying Information', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'WordPress.org discloses potentially personally-identifying and personally-identifying information only to those of its employees, contractors, and affiliated organizations that (i) need to know that information in order to process it on WordPress.org’s behalf or to provide services available at WordPress.org, and (ii) that have agreed not to disclose it to others. Some of those employees, contractors and affiliated organizations may be located outside of your home country; by using WordPress.org, you consent to the transfer of such information to them. WordPress.org will not rent or sell potentially personally-identifying and personally-identifying information to anyone. Other than to its employees, contractors, and affiliated organizations, as described above, WordPress.org discloses potentially personally-identifying and personally-identifying information only when required to do so by law, or when WordPress.org believes in good faith
that disclosure is reasonably necessary to protect the property or rights of WordPress.org, third parties, or the public at large. If you are a registered user of a WordPress.org website and have supplied your email address, WordPress.org may occasionally send you an email to tell you about new features, solicit your feedback, or just keep you up to date with what’s going on with WordPress.org and our products. We primarily use our blog to communicate this type of information, so we expect to keep this type of email to a minimum. If you send us a request (for example via a support email or via one of our feedback mechanisms), we reserve the right to publish it in order to help us clarify or respond to your request or to help us support other users. WordPress.org takes all measures reasonably necessary to protect against the unauthorized access, use, alteration, or destruction of potentially personally-identifying and personally-identifying information.', 'wporg' ); ?>&
lt;/p>
+
+ <h3><?php _esc_html_e( 'Cookies', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'A cookie is a string of information that a website stores on a visitor’s computer, and that the visitor’s browser provides to the website each time the visitor returns. WordPress.org uses cookies to help WordPress.org identify and track visitors, their usage of WordPress.org, and their website access preferences. WordPress.org visitors who do not wish to have cookies placed on their computers should set their browsers to refuse cookies before using WordPress.org’s websites, with the drawback that certain features of WordPress.org’s websites may not function properly without the aid of cookies.', 'wporg' ); ?></p>
+
+ <h3><?php _esc_html_e( 'Privacy Policy Changes', 'wporg' ); ?></h3>
+ <p><?php _esc_html_e( 'Although most changes are likely to be minor, WordPress.org may change its Privacy Policy from time to time, and in WordPress.org’s sole discretion. WordPress.org encourages visitors to frequently check this page for any changes to its Privacy Policy. Your continued use of this site after any change in this Privacy Policy will constitute your acceptance of such change.', 'wporg' ); ?></p>
+
+ <p><a rel="license" href="https://creativecommons.org/licenses/by-sa/2.5/"><img alt="Creative Commons License" src="https://creativecommons.org/images/public/somerights20.png"></a></p>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutrequirementsphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagerequirementsphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-requirements.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-requirements.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-requirements.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-requirements.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,100 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Requirements
+ *
+ * Page template for displaying the Requirements page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Requirements', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <h3><?php _esc_html_e( 'To run WordPress we recommend your host supports:', 'wporg' ); ?></h3>
+
+ <ul>
+ <li>
+ <?php
+ /* translators: URL to PHP */
+ printf( wp_kses_post( ___( '<a href="%s">PHP</a> version 7.2 or greater.', 'wporg' ) ), esc_url( 'http://www.php.net/' ) );
+ ?>
+ </li>
+ <li>
+ <?php
+ /* translators: 1: URL to MySQL; 2: URL to MariaDB */
+ printf( wp_kses_post( ___( '<a href="%1$s">MySQL</a> version 5.6 or greater <em>OR</em> <a href="%2$s">MariaDB</a> version 10.0 or greater.', 'wporg' ) ), esc_url( 'https://www.mysql.com/' ), esc_url( 'https://mariadb.org/' ) );
+ ?>
+ </li>
+ <li>
+ <?php
+ /* translators: URL to news post */
+ printf( wp_kses_post( ___( '<a href="%s">HTTPS</a> support', 'wporg' ) ), esc_url( 'https://wordpress.org/news/2016/12/moving-toward-ssl/' ) );
+ ?>
+ </li>
+ </ul>
+
+ <p>
+ <?php
+ /* translators: 1: URL to Apache; 2: URL to Nginx; 3: URL to hosting page */
+ printf( wp_kses_post( ___( 'That’s really it. We recommend <a href="%1$s">Apache</a> or <a href="%2$s">Nginx</a> as the most robust and featureful server for running WordPress, but any server that supports PHP and MySQL will do. That said, we can’t test every possible environment and <a href="%3$s">each of the hosts on our hosting page</a> supports the above and more with no problems.', 'wporg' ) ), esc_url( 'https://httpd.apache.org/' ), esc_url( 'https://nginx.org/' ), esc_url( home_url( '/hosting/' ) ) );
+ ?>
+ </p>
+
+ <p><?php echo wp_kses_post( ___( 'Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.2.4+ and MySQL 5.0+, but these versions have reached official End Of Life and as such <strong>may expose your site to security vulnerabilities</strong>.', 'wporg' ) ); ?></p>
+
+ <h3><?php _esc_html_e( 'Ask for it', 'wporg' ); ?></h3>
+
+ <p><?php _esc_html_e( 'Here’s a letter you can send to your host; copy and paste!', 'wporg' ); ?></p>
+
+ <blockquote>
+ <p><?php _esc_html_e( 'I’m interested in running the open-source WordPress <https://wordpress.org/> web software and I was wondering if my account supported the following:', 'wporg' ); ?></p>
+
+ <ul>
+ <li><?php _esc_html_e( 'PHP 7.2 or greater', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'MySQL 5.6 or greater OR MariaDB 10.0 or greater', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'Nginx or Apache with mod_rewrite module', 'wporg' ); ?></li>
+ <li><?php _esc_html_e( 'HTTPS support', 'wporg' ); ?></li>
+ </ul>
+
+ <p><?php _esc_html_e( 'Thanks!', 'wporg' ); ?></p>
+ </blockquote>
+
+ <h3><?php _esc_html_e( 'Not required, but recommended for better security', 'wporg' ); ?></h3>
+
+ <p><?php _esc_html_e( 'Hosting is more secure when PHP applications, like WordPress, are run using your account’s username instead of the server’s default shared username. Ask your potential host what steps they take to ensure the security of your account.', 'wporg' ); ?></p>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutroadmapphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageroadmapphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-roadmap.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-roadmap.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-roadmap.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-roadmap.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,251 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Roadmap
+ *
+ * Page template for displaying the Roadmap page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+
+$date_format = get_option( 'date_format' );
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Roadmap', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p>
+ <?php
+ /* translators: 1: Link to Ideas forum; 2: Link to Core Trac */
+ printf( wp_kses_post( ___( 'After the 2.1 release, we decided to adopt a regular release schedule every 3-4 months with the features primarily driven by <a href="%1$s">ideas voted on by our users</a>. Here are the current planned releases, and links to their respective milestones in our <a href="%2$s">issue tracker</a>.', 'wporg' ) ), esc_url( 'https://wordpress.org/ideas/' ), esc_url( 'https://core.trac.wordpress.org/' ) );
+ ?>
+ </p>
+ <p><?php _esc_html_e( 'Any projected dates are for discussion and planning purposes, and will be firmed up as we get closer to release.', 'wporg' ); ?></p>
+ <table>
+ <thead><tr><th><?php _esc_html_e( 'Version', 'wporg' ); ?></th><th><?php _esc_html_e( 'Planned', 'wporg' ); ?></th></tr></thead>
+ <tbody>
+ <tr><th><a href="https://make.wordpress.org/core/5-0/">5.0</a></th><td>2018</td></tr>
+ </tbody>
+ </table>
+
+ <p><?php _esc_html_e( 'The month prior to a release new features are frozen and the focus is entirely on ensuring the quality of the release by eliminating bugs and profiling the code for any performance issues.', 'wporg' ); ?></p>
+
+ <h3><?php _esc_html_e( 'Jazzers and Release Dates', 'wporg' ); ?></h3>
+
+ <p>
+ <?php
+ /* translators: 1: Link to playlist */
+ printf( wp_kses_post( ___( 'WordPress core developers share a love of jazz music, and all our major releases are named in honor of jazz musicians we personally admire. Here’s a list of releases and the musicians they were named for. <a href="%s">You can listen to a Last.fm station of all the musicians we named a release for</a>.', 'wporg' ) ), esc_url( 'http://www.last.fm/tag/wordpress-release-jazz' ) );
+ ?>
+ </p>
+
+ <table>
+ <thead>
+ <tr>
+ <th><?php _esc_html_e( 'Version', 'wporg' ); ?></th>
+ <th><?php _esc_html_e( 'Musician', 'wporg' ); ?></th>
+ <th><?php _esc_html_e( 'Date', 'wporg' ); ?></th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <th><a href="https://wordpress.org/news/2003/05/wordpress-now-available/">.70</a></th>
+ <td><?php _esc_html_e( 'No musician chosen.', 'wporg' ); ?></td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'May 27, 2003' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2004/01/wordpress-10/">1.0</a></th>
+ <td>Miles Davis</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'January 3, 2004' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2004/05/heres-the-beef/">1.2</a></th>
+ <td>Charles Mingus</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'May 22, 2004' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2005/02/strayhorn/">1.5</a></th>
+ <td>Billy Strayhorn</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'February 17, 2005' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2005/12/wp2/">2.0</a></th>
+ <td>Duke Ellington</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 31, 2005' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2007/01/ella-21/">2.1</a></th>
+ <td>Ella Fitzgerald</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'January 22, 2007' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2007/05/wordpress-22/">2.2</a></th>
+ <td>Stan Getz</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'May 16, 2007' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2007/09/wordpress-23/">2.3</a></th>
+ <td>Dexter Gordon</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'September 24, 2007' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2008/03/wordpress-25-brecker/">2.5</a></th>
+ <td>Michael Brecker</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'March 29, 2008' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2008/07/wordpress-26-tyner/">2.6</a></th>
+ <td>McCoy Tyner</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'July 15, 2008' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2008/12/coltrane/">2.7</a></th>
+ <td>John Coltrane</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 10, 2008' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2009/06/wordpress-28/">2.8</a></th>
+ <td>Chet Baker</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 11, 2009' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2009/12/wordpress-2-9/">2.9</a></th>
+ <td>Carmen McRae</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 18, 2009' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2010/06/thelonious/">3.0</a></th>
+ <td>Thelonious Monk</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 17, 2010' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2011/02/threeone/">3.1</a></th>
+ <td>Django Reinhardt</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'February 23, 2011' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2011/07/gershwin/">3.2</a></th>
+ <td>George Gershwin</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'July 4, 2011' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2011/12/sonny/">3.3</a></th>
+ <td>Sonny Stitt</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 12, 2011' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2012/06/green/">3.4</a></th>
+ <td>Grant Green</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 13, 2012' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2012/12/elvin/">3.5</a></th>
+ <td>Elvin Jones</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 11, 2012' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2013/08/oscar/">3.6</a></th>
+ <td>Oscar Peterson</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'August 1, 2013' ) ) ); ?></td>
+ </tr>
+ <tr class="alt">
+ <th><a href="https://wordpress.org/news/2013/10/basie/">3.7</a></th>
+ <td>Count Basie</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'October 24, 2013' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2013/12/parker/">3.8</a></th>
+ <td>Charlie Parker</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 12, 2013' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2014/04/smith/">3.9</a></th>
+ <td>Jimmy Smith</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'April 16, 2014' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2014/09/benny/">4.0</a></th>
+ <td>Benny Goodman</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'September 4, 2014' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2014/12/dinah/">4.1</a></th>
+ <td>Dinah Washington</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 18, 2014' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2015/04/powell/">4.2</a></th>
+ <td>Bud Powell</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'April 23, 2015' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2015/08/billie/">4.3</a></th>
+ <td>Billie Holiday</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'August 18, 2015' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2015/12/clifford/">4.4</a></th>
+ <td>Clifford Brown</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 8, 2015' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2016/04/coleman/">4.5</a></th>
+ <td>Coleman Hawkins</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'April 12, 2016' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2016/08/pepper/">4.6</a></th>
+ <td>Pepper Adams</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'August 16, 2016' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2016/12/vaughan/">4.7</a></th>
+ <td>Sarah Vaughan</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 6, 2016' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2017/06/evans/">4.8</a></th>
+ <td>Bill Evans</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 8, 2017' ) ) ); ?></td>
+ </tr>
+ <tr>
+ <th><a href="https://wordpress.org/news/2017/11/tipton/">4.9</a></th>
+ <td>Billy Tipton</td>
+ <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'November 15, 2017' ) ) ); ?></td>
+ </tr>
+ </tbody>
+ </table>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutsecurityphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagesecurityphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-security.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-security.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,253 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Security
+ *
+ * Page template for displaying the Security page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Security', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p class="intro">Learn more about WordPress core software security in this free white paper. You can also download it in <a href="https://github.com/WordPress/Security-White-Paper/blob/master/WordPressSecurityWhitePaper.pdf?raw=true">PDF format</a>.</p>
+
+ <img src="//s.w.org/about/images/logos/wordpress-logo-stacked-rgb.png" class="aligncenter" />
+
+ <h2>Overview</h2>
+
+ <p>This document is an analysis and explanation of the WordPress core software development and its related security processes, as well as an examination of the inherent security built directly into the software. Decision makers evaluating WordPress as a content management system or web application framework should use this document in their analysis and decision-making, and for developers to refer to it to familiarize themselves with the security components and best practices of the software.</p>
+
+ <p>The information in this document is up-to-date for the latest stable release of the software, WordPress 4.7 at time of publication, but should be considered relevant also to the most recent versions of the software as backwards compatibility is a strong focus for the WordPress development team. Specific security measures and changes will be noted as they have been added to the core software in specific releases. It is strongly encouraged to always be running the latest stable version of WordPress to ensure the most secure experience possible.</p>
+ <h2>Executive Summary</h2>
+ <p>WordPress is a dynamic open-source content management system which is used to power millions of websites, web applications, and blogs. It currently powers more than 27% of the top 10 million websites on the Internet. WordPress' usability, extensibility, and mature development community make it a popular and secure choice for websites of all sizes.</p>
+
+ <p>Since its inception in 2003, WordPress has undergone continual hardening so its core software can address and mitigate common security threats, including the Top 10 list identified by The Open Web Application Security Project (OWASP) as common security vulnerabilities, which are discussed in this document.</p>
+
+ <p>The WordPress Security Team, in collaboration with the WordPress Core Leadership Team and backed by the WordPress global community, works to identify and resolve security issues in the core software available for distribution and installation at WordPress.org, as well as recommending and documenting security best practices for third-party plugin and theme authors.</p>
+
+ <p>Site developers and administrators should pay particular attention to the correct use of core APIs and underlying server configuration which have been the source of common vulnerabilities, as well as ensuring all users employ strong passwords to access WordPress.</p>
+ <h2>An Overview of WordPress</h2>
+ <p>WordPress is a free and open source content management system (CMS). It is the most widely-used CMS software in the world and it powers more than 27% of the top 10 million websites<sup id="ref1"><a href="#footnote1">1</a></a></sup>, giving it an estimated 58% market share of all sites using a CMS.</p>
+
+ <p>WordPress is licensed under the General Public License (GPLv2 or later) which provides four core freedoms, and can be considered as the WordPress "bill of rights":</p>
+ <ol>
+ <li>The freedom to run the program, for any purpose.</li>
+ <li>The freedom to study how the program works, and change it to make it do what you wish.</li>
+ <li>The freedom to redistribute.</li>
+ <li>The freedom to distribute copies of your modified versions to others.</li>
+ </ol>
+ <h3>The WordPress Core Leadership Team</h3>
+ <p>The WordPress project is a meritocracy, run by a core leadership team, and led by its co-creator and lead developer, Matt Mullenweg. The team governs all aspects of the project, including core development, WordPress.org, and community initiatives.</p>
+
+ <p>The Core Leadership Team consists of Matt Mullenweg, five lead developers, and more than a dozen core developers with permanent commit access. These developers have final authority on technical decisions, and lead architecture discussions and implementation efforts.</p>
+
+ <p>WordPress has a number of contributing developers. Some of these are former or current committers, and some are likely future committers. These contributing developers are trusted and veteran contributors to WordPress who have earned a great deal of respect among their peers. As needed, WordPress also has guest committers, individuals who are granted commit access, sometimes for a specific component, on a temporary or trial basis.</p>
+
+ <p>The core and contributing developers primarily guide WordPress development. Every version, hundreds of developers contribute code to WordPress. These core contributors are volunteers who contribute to the core codebase in some way.</p>
+ <h3>The WordPress Release Cycle</h3>
+ <p>Each WordPress release cycle is led by one or more of the core WordPress developers. A release cycle usually lasts around 4 months from the initial scoping meeting to launch of the version.</p>
+
+ <p>A release cycle follows the following pattern<sup id="ref2"><a href="#footnote2">2</a></sup>:</p>
+ <ul>
+ <li>Phase 1: Planning and securing team leads. This is done in the #core chat room on Slack. The release lead discusses features for the next release of WordPress. WordPress contributors get involved with that discussion. The release lead will identify team leads for each of the features.</li>
+ <li>Phase 2: Development work begins. Team leads assemble teams and work on their assigned features. Regular chats are scheduled to ensure the development keeps moving forward.</li>
+ <li>Phase 3: Beta. Betas are released, and beta-testers are asked to start reporting bugs. No more commits for new enhancements or feature requests are carried out from this phase on. Third-party plugin and theme authors are encouraged to test their code against the upcoming changes.</li>
+ <li>Phase 4: Release Candidate. There is a string freeze for translatable strings from this point on. Work is targeted on regressions and blockers only.</li>
+ <li>Phase 5: Launch. WordPress version is launched and made available in the WordPress Admin for updates.</li>
+ </ul>
+ <h3>Version Numbering and Security Releases</h3>
+ <p>A major WordPress version is dictated by the first two sequences. For example, 3.5 is a major release, as is 3.6, 3.7, or 4.0. There isn't a "WordPress 3" or "WordPress 4" and each major release is referred to by its numbering, e.g., "WordPress 3.9."</p>
+
+ <p>Major releases may add new user features and developer APIs. Though typically in the software world, a "major" version means you can break backwards compatibility, WordPress strives to never break backwards compatibility. Backwards compatibility is one of the project's most important philosophies, with the aim of making updates much easier on users and developers alike.</p>
+
+ <p>A minor WordPress version is dictated by the third sequence. Version 3.5.1 is a minor release, as is 3.4.2<sup id="ref3"><a href="#footnote3">3</a></sup>. A minor release is reserved for fixing security vulnerabilities and addressing critical bugs only. Since new versions of WordPress are released so frequently — the aim is every 4-5 months for a major release, and minor releases happen as needed — there is only a need for major and minor releases.</p>
+
+ <h3>Version Backwards Compatibility</h3>
+ <p>The WordPress project has a strong commitment to backwards compatibility. This commitment means that themes, plugins, and custom code continues to function when WordPress core software is updated, encouraging site owners to keep their WordPress version updated to the latest secure release.</p>
+ <h2>WordPress and Security</h2>
+ <h3>The WordPress Security Team</h3>
+ <p>The WordPress Security Team is made up of approximately 50 experts including lead developers and security researchers — about half are employees of Automattic (makers of WordPress.com, the earliest and largest WordPress hosting platform on the web), and a number work in the web security field. The team consults with well-known and trusted security researchers and hosting companies<sup><a href="#footnote3">3</a></sup>.</p>
+
+ <p>The WordPress Security Team often collaborates with other security teams to address issues in common dependencies, such as resolving the vulnerability in the PHP XML parser, used by the XML-RPC API that ships with WordPress, in WordPress 3.9.2<sup id="ref4"><a href="#footnote4">4</a></sup>. This vulnerability resolution was a result of a joint effort by both WordPress and Drupal security teams.</p>
+ <h3>WordPress Security Risks, Process, and History</h3>
+ <p>The WordPress Security Team believes in Responsible Disclosure by alerting the security team immediately of any potential vulnerabilities. Potential security vulnerabilities can be signaled to the Security Team via the <a href="https://hackerone.com/wordpress">WordPress HackerOne</a><sup id="ref5"><a href="#footnote5">5</a></sup>. The Security Team communicates amongst itself via a private Slack channel, and works on a walled-off, private Trac for tracking, testing, and fixing bugs and security problems.</p>
+
+ <p>Each security report is acknowledged upon receipt, and the team works to verify the vulnerability and determine its severity. If confirmed, the security team then plans for a patch to fix the problem which can be committed to an upcoming release of the WordPress software or it can be pushed as an immediate security release, depending on the severity of the issue.</p>
+
+ <p>For an immediate security release, an advisory is published by the Security Team to the WordPress.org News site<sup id="ref6"><a href="#footnote6">6</a></sup> announcing the release and detailing the changes. Credit for the responsible disclosure of a vulnerability is given in the advisory to encourage and reinforce continued responsible reporting in the future.</p>
+
+ <p>Administrators of the WordPress software see a notification on their site dashboard to upgrade when a new release is available, and following the manual upgrade users are redirected to the About WordPress screen which details the changes. If administrators have automatic background updates enabled, they will receive an email after an upgrade has been completed.</p>
+ <h3>Automatic Background Updates for Security Releases</h3>
+ <p>Starting with version 3.7, WordPress introduced automated background updates for all minor releases<sup id="ref7"><a href="#footnote7">7</a></sup>, such as 3.7.1 and 3.7.2. The WordPress Security Team can identify, fix, and push out automated security enhancements for WordPress without the site owner needing to do anything on their end, and the security update will install automatically.</p>
+
+ <p>When a security update is pushed for the current stable release of WordPress, the core team will also push security updates for all the releases that are capable of background updates (since WordPress 3.7), so these older but still recent versions of WordPress will receive security enhancements.</p>
+
+ <p>Individual site owners can opt to remove automatic background updates through a simple change in their configuration file, but keeping the functionality is strongly recommended by the core team, as well as running the latest stable release of WordPress.</p>
+ <h3>2013 OWASP Top 10</h3>
+ <p>The Open Web Application Security Project (OWASP) is an online community dedicated to web application security. The OWASP Top 10 list<sup id="ref8"><a href="#footnote8">8</a></sup> focuses on identifying the most serious application security risks for a broad array of organizations. The Top 10 items are selected and prioritized in combination with consensus estimates of exploitability, detectability, and impact estimates.</p>
+
+ <p>The following sections discuss the APIs, resources, and policies that WordPress uses to strengthen the core software and 3rd party plugins and themes against these potential risks.</p>
+ <h4>A1 - Injection</h4>
+ <p>There is a set of functions and APIs available in WordPress to assist developers in making sure unauthorized code cannot be injected, and help them validate and sanitize data. Best practices and documentation are available<sup id="ref9"><a href="#footnote9">9</a></sup> on how to use these APIs to protect, validate, or sanitize input and output data in HTML, URLs, HTTP headers, and when interacting with the database and filesystem. Administrators can also further restrict the types of file which can be uploaded via filters.</p>
+ <h4>A2 - Broken Authentication and Session Management</h4>
+ <p>WordPress core software manages user accounts and authentication and details such as the user ID, name, and password are managed on the server-side, as well as the authentication cookies. Passwords are protected in the database using standard salting and stretching techniques. Existing sessions are destroyed upon logout for versions of WordPress after 4.0.</p>
+ <h4>A3 - Cross Site Scripting (XSS)</h4>
+ <p>WordPress provides a range of functions which can help ensure that user-supplied data is safe<sup id="ref10"><a href="#footnote10">10</a></sup>. Trusted users, that is administrators and editors on a single WordPress installation, and network administrators only in WordPress Multisite, can post unfiltered HTML or JavaScript as they need to, such as inside a post or page. Untrusted users and user-submitted content is filtered by default to remove dangerous entities, using the KSES library through the <code>wp_kses</code> function.</p>
+
+ <p>As an example, the WordPress core team noticed before the release of WordPress 2.3 that the function <code>the_search_query()</code> was being misused by most theme authors, who were not escaping the function's output for use in HTML. In a very rare case of slightly breaking backward compatibility, the function's output was changed in WordPress 2.3 to be pre-escaped.</p>
+ <h4>A4 - Insecure Direct Object Reference</h4>
+ <p>WordPress often provides direct object reference, such as unique numeric identifiers of user accounts or content available in the URL or form fields. While these identifiers disclose direct system information, WordPress' rich permissions and access control system prevent unauthorized requests.</p>
+ <h4>A5 - Security Misconfiguration</h4>
+ <p>The majority of the WordPress security configuration operations are limited to a single authorized administrator. Default settings for WordPress are continually evaluated at the core team level, and the WordPress core team provides documentation and best practices to tighten security for server configuration for running a WordPress site<sup id="ref11"><a href="#footnote11">11</a></sup>.</p>
+ <h4>A6 - Sensitive Data Exposure</h4>
+ <p>WordPress user account passwords are salted and hashed based on the Portable PHP Password Hashing Framework<sup id="ref12"><a href="#footnote12">12</a></sup>. WordPress' permission system is used to control access to private information such an registered users' PII, commenters' email addresses, privately published content, etc. In WordPress 3.7, a password strength meter was included in the core software providing additional information to users setting their passwords and hints on increasing strength. WordPress also has an optional configuration setting for requiring HTTPS.</p>
+ <h4>A7 - Missing Function Level Access Control</h4>
+ <p>WordPress checks for proper authorization and permissions for any function level access requests prior to the action being executed. Access or visualization of administrative URLs, menus, and pages without proper authentication is tightly integrated with the authentication system to prevent access from unauthorized users.</p>
+ <h4>A8 - Cross Site Request Forgery (CSRF)</h4>
+ <p>WordPress uses cryptographic tokens, called nonces<sup id="ref13"><a href="#footnote13">13</a></sup>, to validate intent of action requests from authorized users to protect against potential CSRF threats. WordPress provides an API for the generation of these tokens to create and verify unique and temporary tokens, and the token is limited to a specific user, a specific action, a specific object, and a specific time period, which can be added to forms and URLs as needed. Additionally, all nonces are invalidated upon logout.</p>
+ <h4>A9 - Using Components with Known Vulnerabilities</h4>
+ <p>The WordPress core team closely monitors the few included libraries and frameworks WordPress integrates with for core functionality. In the past the core team has made contributions to several third-party components to make them more secure, such as the update to fix a cross-site vulnerability in TinyMCE in WordPress 3.5.2<sup id="ref14"><a href="#footnote14">14</a></sup>.</p>
+
+ <p>If necessary, the core team may decide to fork or replace critical external components, such as when the SWFUpload library was officially replaced by the Plupload library in 3.5.2, and a secure fork of SWFUpload was made available by the security team<sup id="ref15"><a href="#footnote15">15</a></sup> for those plugins who continued to use SWFUpload in the short-term.</p>
+ <h4>A10 - Unvalidated Redirects and Forwards</h4>
+ <p>WordPress' internal access control and authentication system will protect against attempts to direct users to unwanted destinations or automatic redirects. This functionality is also made available to plugin developers via an API, <code>wp_safe_redirect()</code><sup id="ref16"><a href="#footnote16">16</a></sup>.</p>
+ <h3>Further Security Risks and Concerns</h3>
+ <h4>XXE (XML eXternal Entity) processing attacks</h4>
+ <p>When processing XML, WordPress disables the loading of custom XML entities to prevent both External Entity and Entity Expansion attacks. Beyond PHP's core functionality, WordPress does not provide additional secure XML processing API for plugin authors.</p>
+ <h4>SSRF (Server Side Request Forgery) Attacks</h4>
+ <p>HTTP requests issued by WordPress are filtered to prevent access to loopback and private IP addresses. Additionally, access is only allowed to certain standard HTTP ports.</p>
+ <h2>WordPress Plugin and Theme Security</h2>
+ <h3>The Default Theme</h3>
+ <p>WordPress requires a theme to be enabled to render content visible on the frontend. The default theme which ships with core WordPress (currently "Twenty Fifteen") has been vigorously reviewed and tested for security reasons by both the team of theme developers plus the core development team.</p>
+
+ <p>The default theme can serve as a starting point for custom theme development, and site developers can create a child theme which includes some customization but falls back on the default theme for most functionality and security. The default theme can be easily removed by an administrator if not needed.</p>
+
+ <h3>WordPress.org Theme and Plugin Repositories</h3>
+
+ <p>There are approximately 50,000+ plugins and 4,500+ themes listed on the WordPress.org site. These themes and plugins are submitted for inclusion and are manually reviewed by volunteers before making them available on the repository.</p>
+
+ <p>Inclusion of plugins and themes in the repository is not a guarantee that they are free from security vulnerabilities. Guidelines are provided for plugin authors to consult prior to submission for inclusion in the repository<sup id="ref17"><a href="#footnote17">17</a></sup>, and extensive documentation about how to do WordPress theme development<sup id="ref18"><a href="#footnote18">18</a></sup> is provided on the WordPress.org site.</p>
+
+ <p>Each plugin and theme has the ability to be continually developed by the plugin or theme owner, and any subsequent fixes or feature development can be uploaded to the repository and made available to users with that plugin or theme installed with a description of that change. Site administrators are notified of plugins which need to be updated via their administration dashboard.</p>
+
+ <p>When a plugin vulnerability is discovered by the WordPress Security Team, they contact the plugin author and work together to fix and release a secure version of the plugin. If there is a lack of response from the plugin author or if the vulnerability is severe, the plugin/theme is pulled from the public directory, and in some cases, fixed and updated directly by the Security Team.</p>
+ <h3>The Theme Review Team</h3>
+ <p>The Theme Review Team is a group of volunteers, led by key and established members of the WordPress community, who review and approve themes submitted to be included in the official WordPress Theme directory. The Theme Review Team maintains the official Theme Review Guidelines<sup id="ref19"><a href="#footnote19">19</a></sup>, the Theme Unit Test Data<sup id="ref20"><a href="#footnote20">20</a></sup>, and the Theme Check Plugin<sup id="ref21"><a href="#footnote21">21</a></sup>, and attempts to engage and educate the WordPress Theme developer community regarding development best practices. Inclusion in the group is moderated by core committers of the WordPress development team.</p>
+ <h2>The Role of the Hosting Provider in WordPress Security</h2>
+ <p>WordPress can be installed on a multitude of platforms. Though WordPress core software provides many provisions for operating a secure web application, which were covered in this document, the configuration of the operating system and the underlying web server hosting the software is equally important to keep the WordPress applications secure.</p>
+ <h3>A Note about WordPress.com and WordPress security</h3>
+ <p>WordPress.com is the largest WordPress installation in the world, and is owned and managed by Automattic, Inc., which was founded by Matt Mullenweg, the WordPress project co-creator. WordPress.com runs on the core WordPress software, and has its own security processes, risks, and solutions<sup id="ref22"><a href="#footnote22">22</a></sup>. This document refers to security regarding the self-hosted, downloadable open source WordPress software available from WordPress.org and installable on any server in the world.</p>
+ <h2>Appendix</h2>
+ <h3>Core WordPress APIs</h3>
+ <p>The WordPress Core Application Programming Interface (API) is comprised of several individual APIs<sup id="ref23"><a href="#footnote23">23</a></sup>, each one covering the functions involved in, and use of, a given set of functionality. Together, these form the project interface which allows plugins and themes to interact with, alter, and extend WordPress core functionality safely and securely.</p>
+
+ <p>While each WordPress API provides best practices and standardized ways to interact with and extend WordPress core software, the following WordPress APIs are the most pertinent to enforcing and hardening WordPress security:</p>
+
+ <h3>Database API</h3>
+
+ <p>The Database API<sup id="ref24"><a href="#footnote24">24</a></sup>, added in WordPress 0.71, provides the correct method for accessing data as named values which are stored in the database layer.</p>
+
+ <h3>Filesystem API</h3>
+
+ <p>The Filesystem API<sup id="ref25"><a href="#footnote25">25</a></sup>, added in WordPress 2.6<sup id="ref26"><a href="#footnote26">26</a></sup>, was originally created for WordPress' own automatic updates feature. The Filesystem API abstracts out the functionality needed for reading and writing local files to the filesystem to be done securely, on a variety of host types.</p>
+
+ <p>It does this through the <code>WP_Filesystem_Base</code> class, and several subclasses which implement different ways of connecting to the local filesystem, depending on individual host support. Any theme or plugin that needs to write files locally should do so using the WP_Filesystem family of classes.</p>
+
+ <h3>HTTP API</h3>
+
+ <p>The HTTP API<sup id="ref27"><a href="#footnote27">27</a></sup>, added in WordPress 2.7<sup id="ref28"><a href="#footnote28">28</a></sup> and extended further in WordPress 2.8, standardizes the HTTP requests for WordPress. The API handles cookies, gzip encoding and decoding, chunk decoding (if HTTP 1.1), and various other HTTP protocol implementations. The API standardizes requests, tests each method prior to sending, and, based on your server configuration, uses the appropriate method to make the request.</p>
+
+ <h3>Permissions and current user API</h3>
+
+ <p>The permissions and current user API<sup id="ref29"><a href="#footnote29">29</a></sup> is a set of functions which will help verify the current user's permissions and authority to perform any task or operation being requested, and can protect further against unauthorized users accessing or performing functions beyond their permitted capabilities.</p>
+ <h3>White paper content License</h3>
+ <p>The text in this document (not including the WordPress logo or <a href="http://wordpressfoundation.org/trademark-policy/">trademark</a>) is licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0 1.0 Universal (CC0 1.0) Public Domain Dedication</a>. You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission.</p>
+
+ <p><em>A special thank you to Drupal's </em><a href="http://drupalsecurityreport.org/"><em>security white paper</em></a><em>, which provided some inspiration. </em></p>
+ <h3>Additional Reading</h3>
+ <ul>
+ <li>WordPress News <a href="https://wordpress.org/news/">https://wordpress.org/news/</a></li>
+ <li>WordPress Security releases <a href="https://wordpress.org/news/category/security/">https://wordpress.org/news/category/security/</a></li>
+ <li>WordPress Developer Resources <a href="https://developer.wordpress.org/">https://developer.wordpress.org/</a></li>
+ </ul>
+
+ <hr />
+
+ <p><em>Authored by </em>Sara Rosso </p>
+
+ <p><em>Contributions from</em> Barry Abrahamson, Michael Adams, Jon Cave, Helen Hou-Sandí, Dion Hulse, Mo Jangda, Paul Maiorana</p>
+
+ <p><em>Version 1.0 March 2015</em></p>
+
+ <hr />
+
+ <h3>Footnotes</h3>
+ <ul>
+ <li id='footnote1'><a href="#ref1">[1]</a> <a href="http://w3techs.com/">http://w3techs.com/</a>, as of March 2017</li>
+ <li id='footnote2'><a href="#ref2">[2]</a> <a href="https://make.wordpress.org/core/handbook/about/release-cycle/">https://make.wordpress.org/core/handbook/about/release-cycle/</a></li>
+ <li id='footnote3'><a href="#ref3">[3]</a> Andrew Nacin, WordPress lead developer, <a href="http://vip.wordpress.com/security">http://vip.wordpress.com/security</a></li>
+ <li id='footnote4'><a href="#ref4">[4]</a> <a href="https://wordpress.org/news/2014/08/wordpress-3-9-2/">https://wordpress.org/news/2014/08/wordpress-3-9-2/</a></li>
+ <li id='footnote5'><a href="#ref5">[5]</a> <a href="http://codex.wordpress.org/Security_FAQ">http://codex.wordpress.org/Security_FAQ</a></li>
+ <li id='footnote6'><a href="#ref6">[6]</a> <a href="https://wordpress.org/news/">https://wordpress.org/news/</a></li>
+ <li id='footnote7'><a href="#ref7">[7]</a> <a href="https://wordpress.org/news/2013/10/basie/">https://wordpress.org/news/2013/10/basie/</a></li>
+ <li id='footnote8'><a href="#ref8">[8]</a> <a href="https://www.owasp.org/index.php/Top_10_2013-Top_10">https://www.owasp.org/index.php/Top_10_2013-Top_10</a></li>
+ <li id='footnote9'><a href="#ref9">[9]</a> <a href="https://developer.wordpress.org/plugins/security/">https://developer.wordpress.org/plugins/security/</a></li>
+ <li id='footnote10'><a href="#ref10">[10]</a> <a href="http://codex.wordpress.org/Data_Validation#HTML.2FXML">http://codex.wordpress.org/Data_Validation#HTML.2FXML</a></li>
+ <li id='footnote11'><a href="#ref11">[11]</a> <a href="http://codex.wordpress.org/Hardening_WordPress">http://codex.wordpress.org/Hardening_WordPress</a></li>
+ <li id='footnote12'><a href="#ref12">[12]</a> <a href="http://www.openwall.com/phpass/">http://www.openwall.com/phpass/</a></li>
+ <li id='footnote13'><a href="#ref13">[13]</a> <a href="https://developer.wordpress.org/plugins/security/nonces/">https://developer.wordpress.org/plugins/security/nonces/</a></li>
+ <li id='footnote14'><a href="#ref14">[14]</a> <a href="https://wordpress.org/news/2013/06/wordpress-3-5-2/">https://wordpress.org/news/2013/06/wordpress-3-5-2/</a></li>
+ <li id='footnote15'><a href="#ref15">[15]</a> <a href="https://make.wordpress.org/core/2013/06/21/secure-swfupload/">https://make.wordpress.org/core/2013/06/21/secure-swfupload/</a></li>
+ <li id='footnote16'><a href="#ref16">[16]</a> <a href="https://developer.wordpress.org/reference/functions/wp_safe_redirect/">https://developer.wordpress.org/reference/functions/wp_safe_redirect/</a></li>
+ <li id='footnote17'><a href="#ref17">[17]</a> <a href="https://wordpress.org/plugins/about/guidelines/">https://wordpress.org/plugins/about/guidelines/</a></li>
+ <li id='footnote18'><a href="#ref18">[18]</a> <a href="https://developer.wordpress.org/themes/getting-started/">https://developer.wordpress.org/themes/getting-started/</a></li>
+ <li id='footnote19'><a href="#ref19">[19]</a> <a href="http://codex.wordpress.org/Theme_Review">http://codex.wordpress.org/Theme_Review</a></li>
+ <li id='footnote20'><a href="#ref20">[20]</a> <a href="http://codex.wordpress.org/Theme_Unit_Test">http://codex.wordpress.org/Theme_Unit_Test</a></li>
+ <li id='footnote21'><a href="#ref21">[21]</a> <a href="https://wordpress.org/plugins/theme-check/">https://wordpress.org/plugins/theme-check/</a></li>
+ <li id='footnote22'><a href="#ref22">[22]</a> <a href="http://automattic.com/security/">http://automattic.com/security/</a></li>
+ <li id='footnote23'><a href="#ref23">[23]</a> <a href="https://codex.wordpress.org/WordPress_APIs">https://codex.wordpress.org/WordPress_APIs</a></li>
+ <li id='footnote24'><a href="#ref24">[24]</a> <a href="https://codex.wordpress.org/Database_API">https://codex.wordpress.org/Database_API</a></li>
+ <li id='footnote25'><a href="#ref25">[25]</a> <a href="https://codex.wordpress.org/Filesystem_API">https://codex.wordpress.org/Filesystem_API</a></li>
+ <li id='footnote26'><a href="#ref26">[26]</a> <a href="http://codex.wordpress.org/Version_2.6">http://codex.wordpress.org/Version_2.6</a></li>
+ <li id='footnote27'><a href="#ref27">[27]</a> <a href="https://codex.wordpress.org/HTTP_API">https://codex.wordpress.org/HTTP_API</a></li>
+ <li id='footnote28'><a href="#ref28">[28]</a> <a href="https://codex.wordpress.org/Version_2.7">https://codex.wordpress.org/Version_2.7</a></li>
+ <li id='footnote29'><a href="#ref29">[29]</a> <a href="http://codex.wordpress.org/Function_Reference/current_user_can">http://codex.wordpress.org/Function_Reference/current_user_can</a></li>
+ </ul>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutstatsphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagestatsphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-stats.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-stats.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-stats.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-stats.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,53 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Stats
+ *
+ * Page template for displaying the Stats page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Statistics', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p><?php _esc_html_e( 'Here are some charts showing what sorts of systems people are running WordPress on. (You’ll need JavaScript enabled to see them.)', 'wporg' ); ?></p>
+ <div id="wp_versions" class="wporg-stats-chart loading"></div>
+ <div id="php_versions" class="wporg-stats-chart loading"></div>
+ <div id="mysql_versions" class="wporg-stats-chart loading"></div>
+ <div id="locales" class="wporg-stats-chart loading"></div>
+ </section>
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageaboutswagphpfromrev6652sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageswagphp"></a>
<div class="copfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Copied: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-swag.php (from rev 6652, sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-swag.php)</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-swag.php (rev 0)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-swag.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -0,0 +1,67 @@
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+<?php
+/**
+ * Template Name: Swag
+ *
+ * Page template for displaying the Swag page.
+ *
+ * @package WordPressdotorg\MainTheme
+ */
+
+namespace WordPressdotorg\MainTheme;
+
+if ( false === stristr( home_url(), 'test' ) ) {
+ return get_template_part( 'page' );
+}
+
+get_header();
+the_post();
+?>
+
+ <main id="main" class="site-main col-12" role="main">
+
+ <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
+ <header class="entry-header">
+ <h1 class="entry-title"><?php _esc_html_e( 'Swag', 'wporg' ); ?></h1>
+ </header><!-- .entry-header -->
+
+ <div class="entry-content row">
+ <section class="col-8">
+ <p>
+ <a class="alignright" href="https://mercantile.wordpress.org">
+ <img width="132" height="177" src="https://s.w.org/images/home/swag_col-1.jpg?1" alt="<?php esc_attr_e( 'WordPress Swag', 'wporg' ); ?>" />
+ </a>
+ <?php
+ /* translators: Link to swag store */
+ printf( wp_kses_post( ___( 'Whether you’re a seasoned WordPress fanatic or just getting warmed up, wear your WordPress love with pride. The official <a href="%s">WordPress Swag Store</a> sells shirts and hoodies in a variety of designs and colors, printed on stock from socially responsible companies.', 'wporg' ) ), esc_url( 'https://mercantile.wordpress.org' ) );
+ ?>
+ </p>
+ <p><?php _esc_html_e( 'The swag store also rotates other products through the lineup on a regular basis.', 'wporg' ); ?></p>
+ <p><?php _esc_html_e( 'The proceeds from these sales help offset the cost of providing free swag (buttons, stickers, etc.) to WordCamps and WordPress meetups around the world.', 'wporg' ); ?></p>
+ <p>
+ <?php
+ /* translators: Link to swag store */
+ printf( wp_kses_post( ___( 'So show the love and spread the word — get your <a href="%s">WordPress swag</a> today.', 'wporg' ) ), esc_url( 'https://mercantile.wordpress.org' ) );
+ ?>
+ </p>
+
+ </section>
+
+ </div><!-- .entry-content -->
+
+ <?php
+ edit_post_link(
+ sprintf(
+ /* translators: %s: Name of current post */
+ esc_html__( 'Edit %s', 'wporg' ),
+ the_title( '<span class="screen-reader-text">"', '"</span>', false )
+ ),
+ '<footer class="entry-footer"><span class="edit-link">',
+ '</span></footer><!-- .entry-footer -->'
+ );
+ ?>
+ </article><!-- #post-## -->
+
+ </main><!-- #main -->
+
+<?php
+get_footer();
</ins></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagedomainsphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-domains.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-domains.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-domains.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,62 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Domains
- *
- * Page template for displaying the Domains page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'WordPress Domains', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p><?php echo wp_kses_post( ___( 'For various reasons related to our WordPress trademark, we ask if you’re going to start a site about WordPress or related to it that you <strong>not</strong> use “WordPress” in the domain name. Try using “wp” instead, or another variation. We’re not lawyers, but very good ones tell us we have to do this to preserve our trademark. Also, many users have told us they find it confusing.', 'wporg' ) ); ?></p>
-
- <p><?php _esc_html_e( 'If you already have a domain with “WordPress” in it, redirecting it to the “wp” equivalent is fine, just as long as the main one users see and you promote doesn’t contain “WordPress” and in the long term you should consider transferring the old one to the Foundation.', 'wporg' ); ?></p>
-
- <p>
- <?php
- echo wp_kses_post( ___( '“WordPress” in sub-domains is fine, like <code>wordpress.example.com</code>, we’re just concerned about top-level domains.', 'wporg' ) ); // phpcs:ignore WordPress.WP.CapitalPDangit.Misspelled
- ?>
- </p>
-
- <p><?php _esc_html_e( 'We’ve told this to anyone who has ever asked us, we just wanted to make it public so more people could be aware of this policy.', 'wporg' ); ?></p>
-
- <p><strong><?php _esc_html_e( '<whine>Other domains are using WordPress in them!</whine>', 'wporg' ); ?></strong></p>
- <p><?php _esc_html_e( 'If they’re not WordPress.com, WordPress.net, WordPress.org, WordPress.tv, or WordPressFoundation.org, they’re not allowed, and you should contact the owner with a pointer to this page. We see this most frequently with spammy sites distributing plugins and themes with malware in them, which you probably don’t want to be associated with.', 'wporg' ); ?></p>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageetiquettephp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-etiquette.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-etiquette.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-etiquette.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,76 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Etiquette
- *
- * Page template for displaying the Etiquette page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Etiquette', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p>
- <?php
- /* translators: Link to blog post */
- printf( wp_kses_post( ___( 'In the WordPress open source project, we realize that our biggest asset is the community that we foster. The project, as a whole, follows these basic philosophical principles from <a href="%s">The Cathedral and The Bazaar</a>.', 'wporg' ) ), esc_url( 'http://www.catb.org/esr/writings/cathedral-bazaar/cathedral-bazaar/index.html' ) );
- ?>
- </p>
-
- <ul>
- <li><?php _esc_html_e( 'Contributions to the WordPress open source project are for the benefit of the WordPress community as a whole, not specific businesses or individuals. All actions taken as a contributor should be made with the best interests of the community in mind.', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'Participation in the WordPress open source project is open to all who wish to join, regardless of ability, skill, financial status, or any other criteria.', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'The WordPress open source project is a volunteer-run community. Even in cases where contributors are sponsored by companies, that time is donated for the benefit of the entire open source community.', 'wporg' ); ?></li>
- <li>
- <?php
- /* translators: Link to make.wordpress.org */
- printf( wp_kses_post( ___( 'Any member of the community can donate their time and contribute to the project in any form including design, code, documentation, community building, etc. For more information, go to <a href="%s">make.wordpress.org</a>.', 'wporg' ) ), esc_url( 'https://make.wordpress.org/' ) );
- ?>
- </li>
- <li><?php _esc_html_e( 'The WordPress open source community cares about diversity. We strive to maintain a welcoming environment where everyone can feel included, by keeping communication free of discrimination, incitement to violence, promotion of hate, and unwelcoming behavior.', 'wporg' ); ?></li>
- </ul>
-
- <p><?php _esc_html_e( 'There is a project currently underway to create a project-wide code of conduct so that we can ensure the safety of our contributors.', 'wporg' ); ?></p>
-
- <p>
- <?php
- /* translators: 1: Link to community team slack channel; 2: Link to tag archive on make/community */
- printf( wp_kses_post( ___( 'Meetings are conducted in the <a href="%1$s">#community-team Slack channel</a>, and minutes published on the <a href="%2$s">Make Community blog</a>.', 'wporg' ) ), esc_url( 'https://wordpress.slack.com/messages/community-team' ), esc_url( 'https://make.wordpress.org/community/tag/ccoc/' ) );
- ?>
- </p>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagefeaturesphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-features.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-features.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-features.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,155 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Features
- *
- * Page template for displaying the Features page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Features', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p class="intro">
- <?php
- /* translators: WordPress market share: 29%; */
- printf( _esc_html__( 'WordPress powers more than %s of the web — a figure that rises every day. Everything from simple websites, to blogs, to complex portals and enterprise websites, and even applications, are built with WordPress.', 'wporg' ), esc_html( WP_MARKET_SHARE . '%' ) );
- ?>
- </p>
-
- <p><?php _esc_html_e( 'WordPress combines simplicity for users and publishers with under-the-hood complexity for developers. This makes it flexible while still being easy-to-use.', 'wporg' ); ?></p>
-
- <p><?php _esc_html_e( 'The following is a list of some of the features that come as standard with WordPress; however, there are literally thousands of plugins that extend what WordPress does, so the actual functionality is nearly limitless. You are also free to do whatever you like with the WordPress code, extend it or modify in any way or use it for commercial projects without any licensing fees. That is the beauty of free software, free refers not only to price but also the freedom to have complete control over it.', 'wporg' ); ?></p>
-
- <p><?php _esc_html_e( 'Here are some of the features that we think that you’ll love.', 'wporg' ); ?></p>
-
- <ul>
- <li><strong><?php _esc_html_e( 'Simplicity', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'Simplicity makes it possible for you to get online and get publishing, quickly. Nothing should get in the way of you getting your website up and your content out there. WordPress is built to make that happen.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Flexibility', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'With WordPress, you can create any type of website you want: a personal blog or website, a photoblog, a business website, a professional portfolio, a government website, a magazine or news website, an online community, even a network of websites. You can make your website beautiful with themes, and extend it with plugins. You can even build your very own application.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Publish with Ease', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'If you’ve ever created a document, you’re already a whizz at creating content with WordPress. You can create Posts and Pages, format them easily, insert media, and with the click of a button your content is live and on the web.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Publishing Tools', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'WordPress makes it easy for you to manage your content. Create drafts, schedule publication, and look at your post revisions. Make your content public or private, and secure posts and pages with a password.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'User Management', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'Not everyone requires the same access to your website. Administrators manage the site, editors work with content, authors and contributors write that content, and subscribers have a profile that they can manage. This lets you have a variety of contributors to your website, and let others simply be part of your community.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Media Management', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'They say a picture says a thousand words, which is why it’s important for you to be able to quickly and easily upload images and media to WordPress. Drag and drop your media into the uploader to add it to your website. Add alt text, captions, and titles, and insert images and galleries into your content. We’ve even added a few image editing tools you can have fun with.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Full Standards Compliance', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'Every piece of WordPress generated code is in full compliance with the standards set by the W3C. This means that your website will work in today’s browser, while maintaining forward compatibility with the next generation of browser. Your website is a beautiful thing, now and in the future.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Easy Theme System', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'WordPress comes bundled with two default themes, but if they aren’t for you there’s a theme directory with thousands of themes for you to create a beautiful website. None of those to your taste? Upload your own theme with the click of a button. It only takes a few seconds for you to give your website a complete makeover.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Extend with Plugins', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'WordPress comes packed full of features for every user, for every other feature there’s a plugin directory with thousands of plugins. Add complex galleries, social networking, forums, social media widgets, spam protection, calendars, fine-tune controls for search engine optimization, and forms.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Built-in Comments', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'Your blog is your home, and comments provide a space for your friends and followers to engage with your content. WordPress’s comment tools give you everything you need to be a forum for discussion and to moderate that discussion.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Search Engine Optimized', 'wporg' ); ?></strong>
- <?php
- /* translators: Link to Plugin Directory search for SEO */
- printf( wp_kses_post( ___( 'WordPress is optimized for search engines right out of the box. For more fine-grained SEO control, there are plenty of <a href="%s">SEO plugins</a> to take care of that for you.', 'wporg' ) ), esc_url( 'https://wordpress.org/plugins/search/SEO/' ) );
- ?>
- </li>
- <li><strong><?php _esc_html_e( 'Multilingual', 'wporg' ); ?></strong>
- <?php
- /* translators: Link to polyglots teams */
- printf( wp_kses_post( ___( 'WordPress is available in more than 70 languages. If you or the person you’re building the website for would prefer to use WordPress in a language other than English, <a href="%s">that’s easy to do</a>.', 'wporg' ) ), esc_url( 'https://make.wordpress.org/polyglots/teams/' ) );
- ?>
- </li>
- <li><strong><?php _esc_html_e( 'Easy Installation and Upgrades', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'WordPress has always been easy to install and upgrade. If you’re happy using an FTP program, you can create a database, upload WordPress using FTP, and run the installer. Not familiar with FTP? Plenty of web hosts offer one-click WordPress installers that let you install WordPress with, well, just one click!', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Importers', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'Using blog or website software that you aren’t happy with? Running your blog on a hosted service that’s about to shut down? WordPress comes with importers for blogger, LiveJournal, Movable Type, TypePad, Tumblr, and WordPress. If you’re ready to make the move, we’ve made it easy for you.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Own Your Data', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'Hosted services come and go. If you’ve ever used a service that disappeared, you know how traumatic that can be. If you’ve ever seen adverts appear on your website, you’ve probably been pretty annoyed. Using WordPress means no one has access to your content. Own your data, all of it — your website, your content, your data.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Freedom', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'WordPress is licensed under the GPL which was created to protect your freedoms. You are free to use WordPress in any way you choose: install it, use it, modify it, distribute it. Software freedom is the foundation that WordPress is built on.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Community', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'As the most popular open source CMS on the web, WordPress has a vibrant and supportive community. Ask a question on the support forums and get help from a volunteer, attend a WordCamp or Meetup to learn more about WordPress, read blogs posts and tutorials about WordPress. Community is at the heart of WordPress, making it what it is today.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Contribute', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'You can be WordPress too! Help to build WordPress, answer questions on the support forums, write documentation, translate WordPress into your language, speak at a WordCamp, write about WordPress on your blog. Whatever your skill, we’d love to have you!', 'wporg' ); ?>
- </li>
- </ul>
- <h3><?php _esc_html_e( 'Developer Features', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'For developers, we’ve got lots of goodies packed under the hood that you can use to extend WordPress in whatever direction takes your fancy.', 'wporg' ); ?></p>
-
- <ul>
- <li><strong><?php _esc_html_e( 'Plugin System', 'wporg' ); ?></strong>
- <?php
- /* translators: 1: Link to Codex page about APIs; 2: Link to Plugin Directory */
- printf( wp_kses_post( ___( 'The <a href="%1$s">WordPress APIs</a> make it possible for you to create plugins to extend WordPress. WordPress’s extensibility lies in the thousands of hooks at your disposal. Once you’ve created your plugin, we’ve even got a <a href="%2$s">plugin repository</a> for you to host it on.', 'wporg' ) ), esc_url( 'https://codex.wordpress.org/WordPress_APIs' ), esc_url( home_url( '/plugins/' ) ) );
- ?>
- </li>
- <li><strong><?php _esc_html_e( 'Theme System', 'wporg' ); ?></strong>
- <?php
- /* translators: 1: Link to Codex page about APIs; 2: Link to Theme Directory */
- printf( wp_kses_post( ___( 'Create WordPress themes for clients, customers, and for WordPress users. The <a href="%1$s">WordPress API</a> provides the extensibility to create themes as simple or as complex as you wish. If you want to give your theme away for free you can give it to users in the <a href="%2$s">Theme Repository</a>', 'wporg' ) ), esc_url( 'https://codex.wordpress.org/WordPress_APIs' ), esc_url( home_url( '/themes/' ) ) );
- ?>
- </li>
- <li><strong><?php _esc_html_e( 'Application Framework', 'wporg' ); ?></strong>
- <?php _esc_html_e( 'If you want to build an application, WordPress can help with that too. Under the hood WordPress provides a lot of the features that your app will need, things like translations, user management, HTTP requests, databases, URL routing and much, much more.', 'wporg' ); ?>
- </li>
- <li><strong><?php _esc_html_e( 'Custom Content Types', 'wporg' ); ?></strong>
- <?php
- /* translators: 1: Link to Codex page about Custom Post Types; 2: Link to Codex page about Custom Taxonomies; 3: Link to Codex page about Custom Fields */
- printf( wp_kses_post( ___( 'WordPress comes with default content types, but for more flexibility you can add a few lines of code to create your own <a href="%1$s">custom post types</a>, <a href="%2$s">taxonomies</a>, and <a href="%3$s">metadata</a>. Take WordPress in whatever direction you wish.', 'wporg' ) ), esc_url( 'https://codex.wordpress.org/Post_Types#Custom_Post_Types' ), esc_url( 'https://codex.wordpress.org/Taxonomies#Custom_Taxonomies' ), esc_url( 'https://codex.wordpress.org/Custom_Fields' ) );
- ?>
- </li>
- <li><strong><?php _esc_html_e( 'The Latest Libraries', 'wporg' ); ?></strong>
- <?php
- /* translators: 1: Link to Developer Handbook page about default scripts */
- printf( wp_kses_post( ___( 'WordPress comes with the <a href="%s">latest script libraries</a> for you to make use of. These include jQuery, Plupload, Underscore.js and Backbone.js. We’re always on the lookout for new tools that developers can use to make a better experience for our users.', 'wporg' ) ), esc_url( 'https://developer.wordpress.org/reference/functions/wp_enqueue_script/#default-scripts-included-and-registered-by-wordpress' ) );
- ?>
- </li>
- </ul>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagegplphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-gpl.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-gpl.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-gpl.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,103 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: GPL
- *
- * Page template for displaying the GPL page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'GNU General Public License', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p>The GPLv2 (or later) from the <a href="http://www.fsf.org/">Free Software Foundation</a> is the license that the WordPress software is under. Its text follows.</p>
-
- <p>Version 2, June 1991</p>
-
- <p>Copyright (C) 1989, 1991 Free Software Foundation, Inc.<br /> 51 Franklin St, Fifth Floor, Boston, MA 02110, USA</p>
- <p>Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.</p>
-
- <h3>Preamble</h3>
-
- <p>The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software — to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation’s software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.</p>
-
- <p>When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.</p>
-
- <p>To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.</p>
-
- <p>For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.</p>
-
- <p>We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.</p>
-
- <p>Also, for each author’s protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.</p>
-
- <p>Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use or not licensed at all.</p>
-
- <p>The precise terms and conditions for copying, distribution and modification follow.</p>
-
- <h3>GNU General Public License Terms and Conditions for Copying, Distribution, and Modification</h3>
-
- <ol start="0">
-
- <li>This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having
been made by running the Program). Whether that is true depends on what the Program does.</li>
- <li>You may copy and distribute verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.</li>
- <li>You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
- <ol type="a">
- <li>You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.</li>
- <li>You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.</li>
- <li>If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)</li>
- </ol>
- These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volum
e of a storage or distribution medium does not bring the other work under the scope of this License.</li>
- <li>You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
- <ol type="a">
- <li>Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,</li>
- <li>Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,</li>
- <li>Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object c
ode is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.</li>
- </ol>
- </li>
- <li>You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.</li>
- <li>You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.</li>
- <li>Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.</li>
- <li>If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is int
ended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.</li>
- <li>If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.</li>
- <li>The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.</li>
- <li>If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.</li>
- <li>BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.</li>
- <li>IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</li>
- </ol>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagehistoryphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-history.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-history.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-history.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,55 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: History
- *
- * Page template for displaying the History page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'History', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p class="intro">We’ve been working on a new book about the history of WordPress drawing on dozens of interviews with the original folks involved and extensive research. It’s not ready yet, but for the tenth anniversary of WordPress we’d like to make a chapter available, <em>On forking WordPress, forks in general, early WordPress, and the community</em>, which you can download below in the following formats:</p>
-
- <ul>
- <li><a href="chapter3.epub">Chapter 3 - EPUB</a></li>
- <li><a href="chapter3.mobi">Chapter 3 - MOBI</a></li>
- <li><a href="chapter3.pdf">Chapter 3 - PDF</a></li>
- </ul>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagelicensephp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-license.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-license.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-license.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,68 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: License
- *
- * Page template for displaying the License page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'GNU Public License', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p>
- <?php
- /* translators: 1: Link to Free Software Foundation; 2: Link to GPL text */
- printf( wp_kses_post( ___( 'The license under which the WordPress software is released is the GPLv2 (or later) from the <a href="%1$s">Free Software Foundation</a>. A copy of the license is included with every copy of WordPress, but you can also read <a href="%2$s">the text of the license</a> here.', 'wporg' ) ), esc_url( 'https://www.fsf.org/' ), esc_url( home_url( '/about/gpl/' ) ) );
- ?>
- </p>
-
- <p>
- <?php
- /* translators: 1: Link to Drupal; 2: Link to Drupal's licensing faq */
- printf( wp_kses_post( ___( 'Part of this license outlines requirements for derivative works, such as plugins or themes. Derivatives of WordPress code inherit the GPL license. <a href="%1$s">Drupal</a>, which has the same GPL license as WordPress, has an excellent page on <a href="%2$s">licensing as it applies to themes and modules</a> (their word for plugins).', 'wporg' ) ), esc_url( 'https://drupal.org/' ), esc_url( 'https://drupal.org/licensing/faq/' ) );
- ?>
- </p>
-
- <p>
- <?php
- /* translators: 1: Link to Serendipity; 2: Link to Habari */
- printf( wp_kses_post( ___( 'There is some legal grey area regarding what is considered a derivative work, but we feel strongly that plugins and themes are derivative work and thus inherit the GPL license. If you disagree, you might want to consider a non-GPL platform such as <a href="%1$s">Serendipity</a> (BSD license) or <a href="%2$s">Habari</a> (Apache license) instead.', 'wporg' ) ), esc_url( 'https://www.s9y.org/' ), esc_url( 'http://habariproject.org/en/' ) );
- ?>
- </p>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagephilosophyphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-philosophy.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-philosophy.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-philosophy.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,88 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Philosophy
- *
- * Page template for displaying the Philosophy page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Philosophy', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <h3 id="box"><?php _esc_html_e( 'Out of the Box', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'Great software should work with little configuration and setup. WordPress is designed to get you up and running and fully functional in no longer than five minutes. You shouldn’t have to battle to use the standard functionality of WordPress.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'We work hard to make sure that every release is in keeping with this philosophy. We ask for as few technical details as possible during the setup process as well as providing full explanations of anything we do ask.', 'wporg' ); ?></p>
-
- <h3 id="majority"><?php _esc_html_e( 'Design for the Majority', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'Many end users of WordPress are non-technically minded. They don’t know what AJAX is, nor do they care about which version of PHP they are using. The average WordPress user simply wants to be able to write without problems or interruption. These are the users that we design the software for as they are ultimately the ones who are going to spend the most time using it for what it was built for.', 'wporg' ); ?></p>
-
- <h3 id="decisions"><?php _esc_html_e( 'Decisions, not Options', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'When making decisions these are the users we consider first. A great example of this consideration is software options. Every time you give a user an option, you are asking them to make a decision. When a user doesn’t care or understand the option this ultimately leads to frustration. As developers we sometimes feel that providing options for everything is a good thing, you can never have too many choices, right? Ultimately these choices end up being technical ones, choices that the average end user has no interest in. It’s our duty as developers to make smart design decisions and avoid putting the weight of technical choices on our end users.', 'wporg' ); ?></p>
-
- <h3 id="clean"><?php _esc_html_e( 'Clean, Lean, and Mean', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'The core of WordPress will always provide a solid array of basic features. It’s designed to be lean and fast and will always stay that way. We are constantly asked "when will X feature be built" or "why isn’t X plugin integrated into the core". The rule of thumb is that the core should provide features that 80% or more of end users will actually appreciate and use. If the next version of WordPress comes with a feature that the majority of users immediately want to turn off, or think they’ll never use, then we’ve blown it. If we stick to the 80% principle then this should never happen.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'We are able to do this because we have a very capable theme and plugin system and a fantastic developer community. Different people have different needs, and having the sheer number of quality WordPress plugins and themes allows users to customize their installations to their taste. That should allow all users to find the remaining 20% and make all WordPress features those they appreciate and use.', 'wporg' ); ?></p>
-
- <h3 id="simplicity"><?php _esc_html_e( 'Striving for Simplicity', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'We’re never done with simplicity. We want to make WordPress easier to use with every single release. We’ve got a good track record of this, if you don’t believe us then just take a look back at some older versions of WordPress!', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'In past releases we’ve taken major steps to improve ease of use and ultimately make things simpler to understand. One great example of this is core software updates. Updating used to be a painful manual task that was too tricky for a lot of our users. We decided to focus on this and simplified it down to a single click. Now anyone with a WordPress install can perform one click upgrades on both the core of WordPress and plugins and themes.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'We love to challenge ourselves and simplify tasks in ways that are positive for the overall WordPress user experience. Every version of WordPress should be easier and more enjoyable to use than the last.', 'wporg' ); ?></p>
-
- <h3 id="deadlines"><?php _esc_html_e( 'Deadlines Are Not Arbitrary', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'Deadlines are not arbitrary, they’re a promise we make to ourselves and our users that helps us rein in the endless possibilities of things that could be a part of every release. We aspire to release three major versions a year because through trial and error we’ve found that to be a good balance between getting cool stuff in each release and not so much that we end up breaking more than we add.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'Good deadlines almost always make you trim something from a release. This is not a bad thing, it’s what they’re supposed to do.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'The route of delaying a release for that one-more-feature is a rabbit hole. We did that for over a year once, and it wasn’t pleasant for anybody.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'The more frequent and regular releases are, the less important it is for any particular feature to be in this release. If it doesn’t make it for this one, it’ll just be a few months before the next one. When releases become unpredictable or few and far between, there’s more pressure to try and squeeze in that one more thing because it’s going to be so long before the next one. Delay begets delay.', 'wporg' ); ?></p>
-
- <h3 id="minority"><?php _esc_html_e( 'The Vocal Minority', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'There’s a good rule of thumb within internet culture called the 1% rule. It states that "the number of people who create content on the internet represents approximately 1% (or less) of the people actually viewing that content".', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'So while we consider it really important to listen and respond to those who post feedback and voice their opinions on forums, they only represent a tiny fraction of our end users. When making decisions on how to move forward with future versions of WordPress, we look to engage more of those users who are not so vocal online. We do this by meeting and talking to users at WordCamps across the globe, this gives us a better balance of understanding and ultimately allows us to make better decisions for everyone moving forward.', 'wporg' ); ?></p>
-
- <h3 id="gpl"><?php _esc_html_e( 'Our Bill of Rights', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'WordPress is licensed under the General Public License (GPLv2 or later) which provides four core freedoms, consider this as the WordPress "bill of rights":', 'wporg' ); ?></p>
- <ul>
- <li><?php _esc_html_e( 'The freedom to run the program, for any purpose.', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'The freedom to study how the program works, and change it to make it do what you wish.', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'The freedom to redistribute.', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'The freedom to distribute copies of your modified versions to others.', 'wporg' ); ?></li>
- </ul>
- <p><?php _esc_html_e( 'Part of those licensing requirements include licensing derivative works or things that link core WordPress functions (like themes, plugins, etc.) under the GPL as well, thereby passing on the freedom of use for these works as well.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'Obviously there are those who will try to get around these ideals and restrict the freedom of their users by trying to find loopholes or somehow circumvent the intention of the WordPress licensing, which is to ensure freedom of use. We believe that the community as a whole will reward those who focus on supporting these licensing freedoms instead of trying to avoid them.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'The most responsible use of WordPress community resources would therefore be put to best use by emphasizing high quality contributions that embrace the freedoms provided by the GPL.', 'wporg' ); ?></p>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageprivacyphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-privacy.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-privacy.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-privacy.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,71 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Privacy
- *
- * Page template for displaying the Privacy page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Privacy', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p><?php _esc_html_e( 'WordPress.org websites (collectively “WordPress.org” in this document) refer to sites hosted on the WordPress.org, WordPress.net, WordCamp.org, BuddyPress.org, bbPress.org, and other related domains and subdomains thereof.', 'wporg' ); ?></p>
-
- <h3><?php _esc_html_e( 'Website Visitors', 'wporg' ); ?></h3>
- <p>L<?php _esc_html_e( 'ike most website operators, WordPress.org collects non-personally-identifying information of the sort that web browsers and servers typically make available, such as the browser type, language preference, referring site, and the date and time of each visitor request. WordPress.org’s purpose in collecting non-personally identifying information is to better understand how WordPress.org’s visitors use its website. From time to time, WordPress.org may release non-personally-identifying information in the aggregate, e.g., by publishing a report on trends in the usage of its website.', 'wporg' ); ?></p>
-
- <p><?php _esc_html_e( 'WordPress.org also collects potentially personally-identifying information like Internet Protocol (IP) addresses. WordPress.org does not use such information to identify its visitors, however, and does not disclose such information, other than under the same circumstances that it uses and discloses personally-identifying information, as described below.', 'wporg' ); ?></p>
-
- <h3><?php _esc_html_e( 'Gathering of Personally-Identifying Information', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'Certain visitors to WordPress.org choose to interact with WordPress.org in ways that require WordPress.org to gather personally-identifying information. The amount and type of information that WordPress.org gathers depends on the nature of the interaction. For example, we ask visitors who use our forums to provide a username and email address. In each case, WordPress.org collects such information only insofar as is necessary or appropriate to fulfill the purpose of the visitor’s interaction with WordPress.org. WordPress.org does not disclose personally-identifying information other than as described below. And visitors can always refuse to supply personally-identifying information, with the caveat that it may prevent them from engaging in certain website-related activities.', 'wporg' ); ?></p>
-
- <h3><?php _esc_html_e( 'Aggregated Statistics', 'wporg' ); ?></h3>
- <p><?php echo wp_kses_post( ___( 'WordPress.org may collect statistics about the behavior of visitors to its websites. For instance, WordPress.org may reveal how many downloads a particular version got, or say which plugins are most popular based on checks from <code>api.wordpress.org</code>, a web service used by WordPress installations to check for new versions of WordPress and plugins. However, WordPress.org does not disclose personally-identifying information other than as described below.', 'wporg' ) ); ?></p>
-
- <h3><?php _esc_html_e( 'Protection of Certain Personally-Identifying Information', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'WordPress.org discloses potentially personally-identifying and personally-identifying information only to those of its employees, contractors, and affiliated organizations that (i) need to know that information in order to process it on WordPress.org’s behalf or to provide services available at WordPress.org, and (ii) that have agreed not to disclose it to others. Some of those employees, contractors and affiliated organizations may be located outside of your home country; by using WordPress.org, you consent to the transfer of such information to them. WordPress.org will not rent or sell potentially personally-identifying and personally-identifying information to anyone. Other than to its employees, contractors, and affiliated organizations, as described above, WordPress.org discloses potentially personally-identifying and personally-identifying information only when required to do so by law, or when WordPress.org believes in good faith
that disclosure is reasonably necessary to protect the property or rights of WordPress.org, third parties, or the public at large. If you are a registered user of a WordPress.org website and have supplied your email address, WordPress.org may occasionally send you an email to tell you about new features, solicit your feedback, or just keep you up to date with what’s going on with WordPress.org and our products. We primarily use our blog to communicate this type of information, so we expect to keep this type of email to a minimum. If you send us a request (for example via a support email or via one of our feedback mechanisms), we reserve the right to publish it in order to help us clarify or respond to your request or to help us support other users. WordPress.org takes all measures reasonably necessary to protect against the unauthorized access, use, alteration, or destruction of potentially personally-identifying and personally-identifying information.', 'wporg' ); ?>&
lt;/p>
-
- <h3><?php _esc_html_e( 'Cookies', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'A cookie is a string of information that a website stores on a visitor’s computer, and that the visitor’s browser provides to the website each time the visitor returns. WordPress.org uses cookies to help WordPress.org identify and track visitors, their usage of WordPress.org, and their website access preferences. WordPress.org visitors who do not wish to have cookies placed on their computers should set their browsers to refuse cookies before using WordPress.org’s websites, with the drawback that certain features of WordPress.org’s websites may not function properly without the aid of cookies.', 'wporg' ); ?></p>
-
- <h3><?php _esc_html_e( 'Privacy Policy Changes', 'wporg' ); ?></h3>
- <p><?php _esc_html_e( 'Although most changes are likely to be minor, WordPress.org may change its Privacy Policy from time to time, and in WordPress.org’s sole discretion. WordPress.org encourages visitors to frequently check this page for any changes to its Privacy Policy. Your continued use of this site after any change in this Privacy Policy will constitute your acceptance of such change.', 'wporg' ); ?></p>
-
- <p><a rel="license" href="https://creativecommons.org/licenses/by-sa/2.5/"><img alt="Creative Commons License" src="https://creativecommons.org/images/public/somerights20.png"></a></p>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagerequirementsphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-requirements.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-requirements.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-requirements.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,100 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Requirements
- *
- * Page template for displaying the Requirements page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Requirements', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <h3><?php _esc_html_e( 'To run WordPress we recommend your host supports:', 'wporg' ); ?></h3>
-
- <ul>
- <li>
- <?php
- /* translators: URL to PHP */
- printf( wp_kses_post( ___( '<a href="%s">PHP</a> version 7.2 or greater.', 'wporg' ) ), esc_url( 'http://www.php.net/' ) );
- ?>
- </li>
- <li>
- <?php
- /* translators: 1: URL to MySQL; 2: URL to MariaDB */
- printf( wp_kses_post( ___( '<a href="%1$s">MySQL</a> version 5.6 or greater <em>OR</em> <a href="%2$s">MariaDB</a> version 10.0 or greater.', 'wporg' ) ), esc_url( 'https://www.mysql.com/' ), esc_url( 'https://mariadb.org/' ) );
- ?>
- </li>
- <li>
- <?php
- /* translators: URL to news post */
- printf( wp_kses_post( ___( '<a href="%s">HTTPS</a> support', 'wporg' ) ), esc_url( 'https://wordpress.org/news/2016/12/moving-toward-ssl/' ) );
- ?>
- </li>
- </ul>
-
- <p>
- <?php
- /* translators: 1: URL to Apache; 2: URL to Nginx; 3: URL to hosting page */
- printf( wp_kses_post( ___( 'That’s really it. We recommend <a href="%1$s">Apache</a> or <a href="%2$s">Nginx</a> as the most robust and featureful server for running WordPress, but any server that supports PHP and MySQL will do. That said, we can’t test every possible environment and <a href="%3$s">each of the hosts on our hosting page</a> supports the above and more with no problems.', 'wporg' ) ), esc_url( 'https://httpd.apache.org/' ), esc_url( 'https://nginx.org/' ), esc_url( home_url( '/hosting/' ) ) );
- ?>
- </p>
-
- <p><?php echo wp_kses_post( ___( 'Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.2.4+ and MySQL 5.0+, but these versions have reached official End Of Life and as such <strong>may expose your site to security vulnerabilities</strong>.', 'wporg' ) ); ?></p>
-
- <h3><?php _esc_html_e( 'Ask for it', 'wporg' ); ?></h3>
-
- <p><?php _esc_html_e( 'Here’s a letter you can send to your host; copy and paste!', 'wporg' ); ?></p>
-
- <blockquote>
- <p><?php _esc_html_e( 'I’m interested in running the open-source WordPress <https://wordpress.org/> web software and I was wondering if my account supported the following:', 'wporg' ); ?></p>
-
- <ul>
- <li><?php _esc_html_e( 'PHP 7.2 or greater', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'MySQL 5.6 or greater OR MariaDB 10.0 or greater', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'Nginx or Apache with mod_rewrite module', 'wporg' ); ?></li>
- <li><?php _esc_html_e( 'HTTPS support', 'wporg' ); ?></li>
- </ul>
-
- <p><?php _esc_html_e( 'Thanks!', 'wporg' ); ?></p>
- </blockquote>
-
- <h3><?php _esc_html_e( 'Not required, but recommended for better security', 'wporg' ); ?></h3>
-
- <p><?php _esc_html_e( 'Hosting is more secure when PHP applications, like WordPress, are run using your account’s username instead of the server’s default shared username. Ask your potential host what steps they take to ensure the security of your account.', 'wporg' ); ?></p>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageroadmapphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-roadmap.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-roadmap.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-roadmap.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,251 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Roadmap
- *
- * Page template for displaying the Roadmap page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-
-$date_format = get_option( 'date_format' );
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Roadmap', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p>
- <?php
- /* translators: 1: Link to Ideas forum; 2: Link to Core Trac */
- printf( wp_kses_post( ___( 'After the 2.1 release, we decided to adopt a regular release schedule every 3-4 months with the features primarily driven by <a href="%1$s">ideas voted on by our users</a>. Here are the current planned releases, and links to their respective milestones in our <a href="%2$s">issue tracker</a>.', 'wporg' ) ), esc_url( 'https://wordpress.org/ideas/' ), esc_url( 'https://core.trac.wordpress.org/' ) );
- ?>
- </p>
- <p><?php _esc_html_e( 'Any projected dates are for discussion and planning purposes, and will be firmed up as we get closer to release.', 'wporg' ); ?></p>
- <table>
- <thead><tr><th><?php _esc_html_e( 'Version', 'wporg' ); ?></th><th><?php _esc_html_e( 'Planned', 'wporg' ); ?></th></tr></thead>
- <tbody>
- <tr><th><a href="https://make.wordpress.org/core/5-0/">5.0</a></th><td>2018</td></tr>
- </tbody>
- </table>
-
- <p><?php _esc_html_e( 'The month prior to a release new features are frozen and the focus is entirely on ensuring the quality of the release by eliminating bugs and profiling the code for any performance issues.', 'wporg' ); ?></p>
-
- <h3><?php _esc_html_e( 'Jazzers and Release Dates', 'wporg' ); ?></h3>
-
- <p>
- <?php
- /* translators: 1: Link to playlist */
- printf( wp_kses_post( ___( 'WordPress core developers share a love of jazz music, and all our major releases are named in honor of jazz musicians we personally admire. Here’s a list of releases and the musicians they were named for. <a href="%s">You can listen to a Last.fm station of all the musicians we named a release for</a>.', 'wporg' ) ), esc_url( 'http://www.last.fm/tag/wordpress-release-jazz' ) );
- ?>
- </p>
-
- <table>
- <thead>
- <tr>
- <th><?php _esc_html_e( 'Version', 'wporg' ); ?></th>
- <th><?php _esc_html_e( 'Musician', 'wporg' ); ?></th>
- <th><?php _esc_html_e( 'Date', 'wporg' ); ?></th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <th><a href="https://wordpress.org/news/2003/05/wordpress-now-available/">.70</a></th>
- <td><?php _esc_html_e( 'No musician chosen.', 'wporg' ); ?></td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'May 27, 2003' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2004/01/wordpress-10/">1.0</a></th>
- <td>Miles Davis</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'January 3, 2004' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2004/05/heres-the-beef/">1.2</a></th>
- <td>Charles Mingus</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'May 22, 2004' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2005/02/strayhorn/">1.5</a></th>
- <td>Billy Strayhorn</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'February 17, 2005' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2005/12/wp2/">2.0</a></th>
- <td>Duke Ellington</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 31, 2005' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2007/01/ella-21/">2.1</a></th>
- <td>Ella Fitzgerald</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'January 22, 2007' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2007/05/wordpress-22/">2.2</a></th>
- <td>Stan Getz</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'May 16, 2007' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2007/09/wordpress-23/">2.3</a></th>
- <td>Dexter Gordon</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'September 24, 2007' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2008/03/wordpress-25-brecker/">2.5</a></th>
- <td>Michael Brecker</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'March 29, 2008' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2008/07/wordpress-26-tyner/">2.6</a></th>
- <td>McCoy Tyner</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'July 15, 2008' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2008/12/coltrane/">2.7</a></th>
- <td>John Coltrane</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 10, 2008' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2009/06/wordpress-28/">2.8</a></th>
- <td>Chet Baker</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 11, 2009' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2009/12/wordpress-2-9/">2.9</a></th>
- <td>Carmen McRae</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 18, 2009' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2010/06/thelonious/">3.0</a></th>
- <td>Thelonious Monk</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 17, 2010' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2011/02/threeone/">3.1</a></th>
- <td>Django Reinhardt</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'February 23, 2011' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2011/07/gershwin/">3.2</a></th>
- <td>George Gershwin</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'July 4, 2011' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2011/12/sonny/">3.3</a></th>
- <td>Sonny Stitt</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 12, 2011' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2012/06/green/">3.4</a></th>
- <td>Grant Green</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 13, 2012' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2012/12/elvin/">3.5</a></th>
- <td>Elvin Jones</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 11, 2012' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2013/08/oscar/">3.6</a></th>
- <td>Oscar Peterson</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'August 1, 2013' ) ) ); ?></td>
- </tr>
- <tr class="alt">
- <th><a href="https://wordpress.org/news/2013/10/basie/">3.7</a></th>
- <td>Count Basie</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'October 24, 2013' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2013/12/parker/">3.8</a></th>
- <td>Charlie Parker</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 12, 2013' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2014/04/smith/">3.9</a></th>
- <td>Jimmy Smith</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'April 16, 2014' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2014/09/benny/">4.0</a></th>
- <td>Benny Goodman</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'September 4, 2014' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2014/12/dinah/">4.1</a></th>
- <td>Dinah Washington</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 18, 2014' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2015/04/powell/">4.2</a></th>
- <td>Bud Powell</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'April 23, 2015' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2015/08/billie/">4.3</a></th>
- <td>Billie Holiday</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'August 18, 2015' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2015/12/clifford/">4.4</a></th>
- <td>Clifford Brown</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 8, 2015' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2016/04/coleman/">4.5</a></th>
- <td>Coleman Hawkins</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'April 12, 2016' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2016/08/pepper/">4.6</a></th>
- <td>Pepper Adams</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'August 16, 2016' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2016/12/vaughan/">4.7</a></th>
- <td>Sarah Vaughan</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'December 6, 2016' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2017/06/evans/">4.8</a></th>
- <td>Bill Evans</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'June 8, 2017' ) ) ); ?></td>
- </tr>
- <tr>
- <th><a href="https://wordpress.org/news/2017/11/tipton/">4.9</a></th>
- <td>Billy Tipton</td>
- <td><?php echo esc_html( date_i18n( $date_format, strtotime( 'November 15, 2017' ) ) ); ?></td>
- </tr>
- </tbody>
- </table>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagesecurityphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-security.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-security.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-security.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,253 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Security
- *
- * Page template for displaying the Security page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Security', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p class="intro">Learn more about WordPress core software security in this free white paper. You can also download it in <a href="https://github.com/WordPress/Security-White-Paper/blob/master/WordPressSecurityWhitePaper.pdf?raw=true">PDF format</a>.</p>
-
- <img src="//s.w.org/about/images/logos/wordpress-logo-stacked-rgb.png" class="aligncenter" />
-
- <h2>Overview</h2>
-
- <p>This document is an analysis and explanation of the WordPress core software development and its related security processes, as well as an examination of the inherent security built directly into the software. Decision makers evaluating WordPress as a content management system or web application framework should use this document in their analysis and decision-making, and for developers to refer to it to familiarize themselves with the security components and best practices of the software.</p>
-
- <p>The information in this document is up-to-date for the latest stable release of the software, WordPress 4.7 at time of publication, but should be considered relevant also to the most recent versions of the software as backwards compatibility is a strong focus for the WordPress development team. Specific security measures and changes will be noted as they have been added to the core software in specific releases. It is strongly encouraged to always be running the latest stable version of WordPress to ensure the most secure experience possible.</p>
- <h2>Executive Summary</h2>
- <p>WordPress is a dynamic open-source content management system which is used to power millions of websites, web applications, and blogs. It currently powers more than 27% of the top 10 million websites on the Internet. WordPress' usability, extensibility, and mature development community make it a popular and secure choice for websites of all sizes.</p>
-
- <p>Since its inception in 2003, WordPress has undergone continual hardening so its core software can address and mitigate common security threats, including the Top 10 list identified by The Open Web Application Security Project (OWASP) as common security vulnerabilities, which are discussed in this document.</p>
-
- <p>The WordPress Security Team, in collaboration with the WordPress Core Leadership Team and backed by the WordPress global community, works to identify and resolve security issues in the core software available for distribution and installation at WordPress.org, as well as recommending and documenting security best practices for third-party plugin and theme authors.</p>
-
- <p>Site developers and administrators should pay particular attention to the correct use of core APIs and underlying server configuration which have been the source of common vulnerabilities, as well as ensuring all users employ strong passwords to access WordPress.</p>
- <h2>An Overview of WordPress</h2>
- <p>WordPress is a free and open source content management system (CMS). It is the most widely-used CMS software in the world and it powers more than 27% of the top 10 million websites<sup id="ref1"><a href="#footnote1">1</a></a></sup>, giving it an estimated 58% market share of all sites using a CMS.</p>
-
- <p>WordPress is licensed under the General Public License (GPLv2 or later) which provides four core freedoms, and can be considered as the WordPress "bill of rights":</p>
- <ol>
- <li>The freedom to run the program, for any purpose.</li>
- <li>The freedom to study how the program works, and change it to make it do what you wish.</li>
- <li>The freedom to redistribute.</li>
- <li>The freedom to distribute copies of your modified versions to others.</li>
- </ol>
- <h3>The WordPress Core Leadership Team</h3>
- <p>The WordPress project is a meritocracy, run by a core leadership team, and led by its co-creator and lead developer, Matt Mullenweg. The team governs all aspects of the project, including core development, WordPress.org, and community initiatives.</p>
-
- <p>The Core Leadership Team consists of Matt Mullenweg, five lead developers, and more than a dozen core developers with permanent commit access. These developers have final authority on technical decisions, and lead architecture discussions and implementation efforts.</p>
-
- <p>WordPress has a number of contributing developers. Some of these are former or current committers, and some are likely future committers. These contributing developers are trusted and veteran contributors to WordPress who have earned a great deal of respect among their peers. As needed, WordPress also has guest committers, individuals who are granted commit access, sometimes for a specific component, on a temporary or trial basis.</p>
-
- <p>The core and contributing developers primarily guide WordPress development. Every version, hundreds of developers contribute code to WordPress. These core contributors are volunteers who contribute to the core codebase in some way.</p>
- <h3>The WordPress Release Cycle</h3>
- <p>Each WordPress release cycle is led by one or more of the core WordPress developers. A release cycle usually lasts around 4 months from the initial scoping meeting to launch of the version.</p>
-
- <p>A release cycle follows the following pattern<sup id="ref2"><a href="#footnote2">2</a></sup>:</p>
- <ul>
- <li>Phase 1: Planning and securing team leads. This is done in the #core chat room on Slack. The release lead discusses features for the next release of WordPress. WordPress contributors get involved with that discussion. The release lead will identify team leads for each of the features.</li>
- <li>Phase 2: Development work begins. Team leads assemble teams and work on their assigned features. Regular chats are scheduled to ensure the development keeps moving forward.</li>
- <li>Phase 3: Beta. Betas are released, and beta-testers are asked to start reporting bugs. No more commits for new enhancements or feature requests are carried out from this phase on. Third-party plugin and theme authors are encouraged to test their code against the upcoming changes.</li>
- <li>Phase 4: Release Candidate. There is a string freeze for translatable strings from this point on. Work is targeted on regressions and blockers only.</li>
- <li>Phase 5: Launch. WordPress version is launched and made available in the WordPress Admin for updates.</li>
- </ul>
- <h3>Version Numbering and Security Releases</h3>
- <p>A major WordPress version is dictated by the first two sequences. For example, 3.5 is a major release, as is 3.6, 3.7, or 4.0. There isn't a "WordPress 3" or "WordPress 4" and each major release is referred to by its numbering, e.g., "WordPress 3.9."</p>
-
- <p>Major releases may add new user features and developer APIs. Though typically in the software world, a "major" version means you can break backwards compatibility, WordPress strives to never break backwards compatibility. Backwards compatibility is one of the project's most important philosophies, with the aim of making updates much easier on users and developers alike.</p>
-
- <p>A minor WordPress version is dictated by the third sequence. Version 3.5.1 is a minor release, as is 3.4.2<sup id="ref3"><a href="#footnote3">3</a></sup>. A minor release is reserved for fixing security vulnerabilities and addressing critical bugs only. Since new versions of WordPress are released so frequently — the aim is every 4-5 months for a major release, and minor releases happen as needed — there is only a need for major and minor releases.</p>
-
- <h3>Version Backwards Compatibility</h3>
- <p>The WordPress project has a strong commitment to backwards compatibility. This commitment means that themes, plugins, and custom code continues to function when WordPress core software is updated, encouraging site owners to keep their WordPress version updated to the latest secure release.</p>
- <h2>WordPress and Security</h2>
- <h3>The WordPress Security Team</h3>
- <p>The WordPress Security Team is made up of approximately 50 experts including lead developers and security researchers — about half are employees of Automattic (makers of WordPress.com, the earliest and largest WordPress hosting platform on the web), and a number work in the web security field. The team consults with well-known and trusted security researchers and hosting companies<sup><a href="#footnote3">3</a></sup>.</p>
-
- <p>The WordPress Security Team often collaborates with other security teams to address issues in common dependencies, such as resolving the vulnerability in the PHP XML parser, used by the XML-RPC API that ships with WordPress, in WordPress 3.9.2<sup id="ref4"><a href="#footnote4">4</a></sup>. This vulnerability resolution was a result of a joint effort by both WordPress and Drupal security teams.</p>
- <h3>WordPress Security Risks, Process, and History</h3>
- <p>The WordPress Security Team believes in Responsible Disclosure by alerting the security team immediately of any potential vulnerabilities. Potential security vulnerabilities can be signaled to the Security Team via the <a href="https://hackerone.com/wordpress">WordPress HackerOne</a><sup id="ref5"><a href="#footnote5">5</a></sup>. The Security Team communicates amongst itself via a private Slack channel, and works on a walled-off, private Trac for tracking, testing, and fixing bugs and security problems.</p>
-
- <p>Each security report is acknowledged upon receipt, and the team works to verify the vulnerability and determine its severity. If confirmed, the security team then plans for a patch to fix the problem which can be committed to an upcoming release of the WordPress software or it can be pushed as an immediate security release, depending on the severity of the issue.</p>
-
- <p>For an immediate security release, an advisory is published by the Security Team to the WordPress.org News site<sup id="ref6"><a href="#footnote6">6</a></sup> announcing the release and detailing the changes. Credit for the responsible disclosure of a vulnerability is given in the advisory to encourage and reinforce continued responsible reporting in the future.</p>
-
- <p>Administrators of the WordPress software see a notification on their site dashboard to upgrade when a new release is available, and following the manual upgrade users are redirected to the About WordPress screen which details the changes. If administrators have automatic background updates enabled, they will receive an email after an upgrade has been completed.</p>
- <h3>Automatic Background Updates for Security Releases</h3>
- <p>Starting with version 3.7, WordPress introduced automated background updates for all minor releases<sup id="ref7"><a href="#footnote7">7</a></sup>, such as 3.7.1 and 3.7.2. The WordPress Security Team can identify, fix, and push out automated security enhancements for WordPress without the site owner needing to do anything on their end, and the security update will install automatically.</p>
-
- <p>When a security update is pushed for the current stable release of WordPress, the core team will also push security updates for all the releases that are capable of background updates (since WordPress 3.7), so these older but still recent versions of WordPress will receive security enhancements.</p>
-
- <p>Individual site owners can opt to remove automatic background updates through a simple change in their configuration file, but keeping the functionality is strongly recommended by the core team, as well as running the latest stable release of WordPress.</p>
- <h3>2013 OWASP Top 10</h3>
- <p>The Open Web Application Security Project (OWASP) is an online community dedicated to web application security. The OWASP Top 10 list<sup id="ref8"><a href="#footnote8">8</a></sup> focuses on identifying the most serious application security risks for a broad array of organizations. The Top 10 items are selected and prioritized in combination with consensus estimates of exploitability, detectability, and impact estimates.</p>
-
- <p>The following sections discuss the APIs, resources, and policies that WordPress uses to strengthen the core software and 3rd party plugins and themes against these potential risks.</p>
- <h4>A1 - Injection</h4>
- <p>There is a set of functions and APIs available in WordPress to assist developers in making sure unauthorized code cannot be injected, and help them validate and sanitize data. Best practices and documentation are available<sup id="ref9"><a href="#footnote9">9</a></sup> on how to use these APIs to protect, validate, or sanitize input and output data in HTML, URLs, HTTP headers, and when interacting with the database and filesystem. Administrators can also further restrict the types of file which can be uploaded via filters.</p>
- <h4>A2 - Broken Authentication and Session Management</h4>
- <p>WordPress core software manages user accounts and authentication and details such as the user ID, name, and password are managed on the server-side, as well as the authentication cookies. Passwords are protected in the database using standard salting and stretching techniques. Existing sessions are destroyed upon logout for versions of WordPress after 4.0.</p>
- <h4>A3 - Cross Site Scripting (XSS)</h4>
- <p>WordPress provides a range of functions which can help ensure that user-supplied data is safe<sup id="ref10"><a href="#footnote10">10</a></sup>. Trusted users, that is administrators and editors on a single WordPress installation, and network administrators only in WordPress Multisite, can post unfiltered HTML or JavaScript as they need to, such as inside a post or page. Untrusted users and user-submitted content is filtered by default to remove dangerous entities, using the KSES library through the <code>wp_kses</code> function.</p>
-
- <p>As an example, the WordPress core team noticed before the release of WordPress 2.3 that the function <code>the_search_query()</code> was being misused by most theme authors, who were not escaping the function's output for use in HTML. In a very rare case of slightly breaking backward compatibility, the function's output was changed in WordPress 2.3 to be pre-escaped.</p>
- <h4>A4 - Insecure Direct Object Reference</h4>
- <p>WordPress often provides direct object reference, such as unique numeric identifiers of user accounts or content available in the URL or form fields. While these identifiers disclose direct system information, WordPress' rich permissions and access control system prevent unauthorized requests.</p>
- <h4>A5 - Security Misconfiguration</h4>
- <p>The majority of the WordPress security configuration operations are limited to a single authorized administrator. Default settings for WordPress are continually evaluated at the core team level, and the WordPress core team provides documentation and best practices to tighten security for server configuration for running a WordPress site<sup id="ref11"><a href="#footnote11">11</a></sup>.</p>
- <h4>A6 - Sensitive Data Exposure</h4>
- <p>WordPress user account passwords are salted and hashed based on the Portable PHP Password Hashing Framework<sup id="ref12"><a href="#footnote12">12</a></sup>. WordPress' permission system is used to control access to private information such an registered users' PII, commenters' email addresses, privately published content, etc. In WordPress 3.7, a password strength meter was included in the core software providing additional information to users setting their passwords and hints on increasing strength. WordPress also has an optional configuration setting for requiring HTTPS.</p>
- <h4>A7 - Missing Function Level Access Control</h4>
- <p>WordPress checks for proper authorization and permissions for any function level access requests prior to the action being executed. Access or visualization of administrative URLs, menus, and pages without proper authentication is tightly integrated with the authentication system to prevent access from unauthorized users.</p>
- <h4>A8 - Cross Site Request Forgery (CSRF)</h4>
- <p>WordPress uses cryptographic tokens, called nonces<sup id="ref13"><a href="#footnote13">13</a></sup>, to validate intent of action requests from authorized users to protect against potential CSRF threats. WordPress provides an API for the generation of these tokens to create and verify unique and temporary tokens, and the token is limited to a specific user, a specific action, a specific object, and a specific time period, which can be added to forms and URLs as needed. Additionally, all nonces are invalidated upon logout.</p>
- <h4>A9 - Using Components with Known Vulnerabilities</h4>
- <p>The WordPress core team closely monitors the few included libraries and frameworks WordPress integrates with for core functionality. In the past the core team has made contributions to several third-party components to make them more secure, such as the update to fix a cross-site vulnerability in TinyMCE in WordPress 3.5.2<sup id="ref14"><a href="#footnote14">14</a></sup>.</p>
-
- <p>If necessary, the core team may decide to fork or replace critical external components, such as when the SWFUpload library was officially replaced by the Plupload library in 3.5.2, and a secure fork of SWFUpload was made available by the security team<sup id="ref15"><a href="#footnote15">15</a></sup> for those plugins who continued to use SWFUpload in the short-term.</p>
- <h4>A10 - Unvalidated Redirects and Forwards</h4>
- <p>WordPress' internal access control and authentication system will protect against attempts to direct users to unwanted destinations or automatic redirects. This functionality is also made available to plugin developers via an API, <code>wp_safe_redirect()</code><sup id="ref16"><a href="#footnote16">16</a></sup>.</p>
- <h3>Further Security Risks and Concerns</h3>
- <h4>XXE (XML eXternal Entity) processing attacks</h4>
- <p>When processing XML, WordPress disables the loading of custom XML entities to prevent both External Entity and Entity Expansion attacks. Beyond PHP's core functionality, WordPress does not provide additional secure XML processing API for plugin authors.</p>
- <h4>SSRF (Server Side Request Forgery) Attacks</h4>
- <p>HTTP requests issued by WordPress are filtered to prevent access to loopback and private IP addresses. Additionally, access is only allowed to certain standard HTTP ports.</p>
- <h2>WordPress Plugin and Theme Security</h2>
- <h3>The Default Theme</h3>
- <p>WordPress requires a theme to be enabled to render content visible on the frontend. The default theme which ships with core WordPress (currently "Twenty Fifteen") has been vigorously reviewed and tested for security reasons by both the team of theme developers plus the core development team.</p>
-
- <p>The default theme can serve as a starting point for custom theme development, and site developers can create a child theme which includes some customization but falls back on the default theme for most functionality and security. The default theme can be easily removed by an administrator if not needed.</p>
-
- <h3>WordPress.org Theme and Plugin Repositories</h3>
-
- <p>There are approximately 50,000+ plugins and 4,500+ themes listed on the WordPress.org site. These themes and plugins are submitted for inclusion and are manually reviewed by volunteers before making them available on the repository.</p>
-
- <p>Inclusion of plugins and themes in the repository is not a guarantee that they are free from security vulnerabilities. Guidelines are provided for plugin authors to consult prior to submission for inclusion in the repository<sup id="ref17"><a href="#footnote17">17</a></sup>, and extensive documentation about how to do WordPress theme development<sup id="ref18"><a href="#footnote18">18</a></sup> is provided on the WordPress.org site.</p>
-
- <p>Each plugin and theme has the ability to be continually developed by the plugin or theme owner, and any subsequent fixes or feature development can be uploaded to the repository and made available to users with that plugin or theme installed with a description of that change. Site administrators are notified of plugins which need to be updated via their administration dashboard.</p>
-
- <p>When a plugin vulnerability is discovered by the WordPress Security Team, they contact the plugin author and work together to fix and release a secure version of the plugin. If there is a lack of response from the plugin author or if the vulnerability is severe, the plugin/theme is pulled from the public directory, and in some cases, fixed and updated directly by the Security Team.</p>
- <h3>The Theme Review Team</h3>
- <p>The Theme Review Team is a group of volunteers, led by key and established members of the WordPress community, who review and approve themes submitted to be included in the official WordPress Theme directory. The Theme Review Team maintains the official Theme Review Guidelines<sup id="ref19"><a href="#footnote19">19</a></sup>, the Theme Unit Test Data<sup id="ref20"><a href="#footnote20">20</a></sup>, and the Theme Check Plugin<sup id="ref21"><a href="#footnote21">21</a></sup>, and attempts to engage and educate the WordPress Theme developer community regarding development best practices. Inclusion in the group is moderated by core committers of the WordPress development team.</p>
- <h2>The Role of the Hosting Provider in WordPress Security</h2>
- <p>WordPress can be installed on a multitude of platforms. Though WordPress core software provides many provisions for operating a secure web application, which were covered in this document, the configuration of the operating system and the underlying web server hosting the software is equally important to keep the WordPress applications secure.</p>
- <h3>A Note about WordPress.com and WordPress security</h3>
- <p>WordPress.com is the largest WordPress installation in the world, and is owned and managed by Automattic, Inc., which was founded by Matt Mullenweg, the WordPress project co-creator. WordPress.com runs on the core WordPress software, and has its own security processes, risks, and solutions<sup id="ref22"><a href="#footnote22">22</a></sup>. This document refers to security regarding the self-hosted, downloadable open source WordPress software available from WordPress.org and installable on any server in the world.</p>
- <h2>Appendix</h2>
- <h3>Core WordPress APIs</h3>
- <p>The WordPress Core Application Programming Interface (API) is comprised of several individual APIs<sup id="ref23"><a href="#footnote23">23</a></sup>, each one covering the functions involved in, and use of, a given set of functionality. Together, these form the project interface which allows plugins and themes to interact with, alter, and extend WordPress core functionality safely and securely.</p>
-
- <p>While each WordPress API provides best practices and standardized ways to interact with and extend WordPress core software, the following WordPress APIs are the most pertinent to enforcing and hardening WordPress security:</p>
-
- <h3>Database API</h3>
-
- <p>The Database API<sup id="ref24"><a href="#footnote24">24</a></sup>, added in WordPress 0.71, provides the correct method for accessing data as named values which are stored in the database layer.</p>
-
- <h3>Filesystem API</h3>
-
- <p>The Filesystem API<sup id="ref25"><a href="#footnote25">25</a></sup>, added in WordPress 2.6<sup id="ref26"><a href="#footnote26">26</a></sup>, was originally created for WordPress' own automatic updates feature. The Filesystem API abstracts out the functionality needed for reading and writing local files to the filesystem to be done securely, on a variety of host types.</p>
-
- <p>It does this through the <code>WP_Filesystem_Base</code> class, and several subclasses which implement different ways of connecting to the local filesystem, depending on individual host support. Any theme or plugin that needs to write files locally should do so using the WP_Filesystem family of classes.</p>
-
- <h3>HTTP API</h3>
-
- <p>The HTTP API<sup id="ref27"><a href="#footnote27">27</a></sup>, added in WordPress 2.7<sup id="ref28"><a href="#footnote28">28</a></sup> and extended further in WordPress 2.8, standardizes the HTTP requests for WordPress. The API handles cookies, gzip encoding and decoding, chunk decoding (if HTTP 1.1), and various other HTTP protocol implementations. The API standardizes requests, tests each method prior to sending, and, based on your server configuration, uses the appropriate method to make the request.</p>
-
- <h3>Permissions and current user API</h3>
-
- <p>The permissions and current user API<sup id="ref29"><a href="#footnote29">29</a></sup> is a set of functions which will help verify the current user's permissions and authority to perform any task or operation being requested, and can protect further against unauthorized users accessing or performing functions beyond their permitted capabilities.</p>
- <h3>White paper content License</h3>
- <p>The text in this document (not including the WordPress logo or <a href="http://wordpressfoundation.org/trademark-policy/">trademark</a>) is licensed under <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0 1.0 Universal (CC0 1.0) Public Domain Dedication</a>. You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission.</p>
-
- <p><em>A special thank you to Drupal's </em><a href="http://drupalsecurityreport.org/"><em>security white paper</em></a><em>, which provided some inspiration. </em></p>
- <h3>Additional Reading</h3>
- <ul>
- <li>WordPress News <a href="https://wordpress.org/news/">https://wordpress.org/news/</a></li>
- <li>WordPress Security releases <a href="https://wordpress.org/news/category/security/">https://wordpress.org/news/category/security/</a></li>
- <li>WordPress Developer Resources <a href="https://developer.wordpress.org/">https://developer.wordpress.org/</a></li>
- </ul>
-
- <hr />
-
- <p><em>Authored by </em>Sara Rosso </p>
-
- <p><em>Contributions from</em> Barry Abrahamson, Michael Adams, Jon Cave, Helen Hou-Sandí, Dion Hulse, Mo Jangda, Paul Maiorana</p>
-
- <p><em>Version 1.0 March 2015</em></p>
-
- <hr />
-
- <h3>Footnotes</h3>
- <ul>
- <li id='footnote1'><a href="#ref1">[1]</a> <a href="http://w3techs.com/">http://w3techs.com/</a>, as of March 2017</li>
- <li id='footnote2'><a href="#ref2">[2]</a> <a href="https://make.wordpress.org/core/handbook/about/release-cycle/">https://make.wordpress.org/core/handbook/about/release-cycle/</a></li>
- <li id='footnote3'><a href="#ref3">[3]</a> Andrew Nacin, WordPress lead developer, <a href="http://vip.wordpress.com/security">http://vip.wordpress.com/security</a></li>
- <li id='footnote4'><a href="#ref4">[4]</a> <a href="https://wordpress.org/news/2014/08/wordpress-3-9-2/">https://wordpress.org/news/2014/08/wordpress-3-9-2/</a></li>
- <li id='footnote5'><a href="#ref5">[5]</a> <a href="http://codex.wordpress.org/Security_FAQ">http://codex.wordpress.org/Security_FAQ</a></li>
- <li id='footnote6'><a href="#ref6">[6]</a> <a href="https://wordpress.org/news/">https://wordpress.org/news/</a></li>
- <li id='footnote7'><a href="#ref7">[7]</a> <a href="https://wordpress.org/news/2013/10/basie/">https://wordpress.org/news/2013/10/basie/</a></li>
- <li id='footnote8'><a href="#ref8">[8]</a> <a href="https://www.owasp.org/index.php/Top_10_2013-Top_10">https://www.owasp.org/index.php/Top_10_2013-Top_10</a></li>
- <li id='footnote9'><a href="#ref9">[9]</a> <a href="https://developer.wordpress.org/plugins/security/">https://developer.wordpress.org/plugins/security/</a></li>
- <li id='footnote10'><a href="#ref10">[10]</a> <a href="http://codex.wordpress.org/Data_Validation#HTML.2FXML">http://codex.wordpress.org/Data_Validation#HTML.2FXML</a></li>
- <li id='footnote11'><a href="#ref11">[11]</a> <a href="http://codex.wordpress.org/Hardening_WordPress">http://codex.wordpress.org/Hardening_WordPress</a></li>
- <li id='footnote12'><a href="#ref12">[12]</a> <a href="http://www.openwall.com/phpass/">http://www.openwall.com/phpass/</a></li>
- <li id='footnote13'><a href="#ref13">[13]</a> <a href="https://developer.wordpress.org/plugins/security/nonces/">https://developer.wordpress.org/plugins/security/nonces/</a></li>
- <li id='footnote14'><a href="#ref14">[14]</a> <a href="https://wordpress.org/news/2013/06/wordpress-3-5-2/">https://wordpress.org/news/2013/06/wordpress-3-5-2/</a></li>
- <li id='footnote15'><a href="#ref15">[15]</a> <a href="https://make.wordpress.org/core/2013/06/21/secure-swfupload/">https://make.wordpress.org/core/2013/06/21/secure-swfupload/</a></li>
- <li id='footnote16'><a href="#ref16">[16]</a> <a href="https://developer.wordpress.org/reference/functions/wp_safe_redirect/">https://developer.wordpress.org/reference/functions/wp_safe_redirect/</a></li>
- <li id='footnote17'><a href="#ref17">[17]</a> <a href="https://wordpress.org/plugins/about/guidelines/">https://wordpress.org/plugins/about/guidelines/</a></li>
- <li id='footnote18'><a href="#ref18">[18]</a> <a href="https://developer.wordpress.org/themes/getting-started/">https://developer.wordpress.org/themes/getting-started/</a></li>
- <li id='footnote19'><a href="#ref19">[19]</a> <a href="http://codex.wordpress.org/Theme_Review">http://codex.wordpress.org/Theme_Review</a></li>
- <li id='footnote20'><a href="#ref20">[20]</a> <a href="http://codex.wordpress.org/Theme_Unit_Test">http://codex.wordpress.org/Theme_Unit_Test</a></li>
- <li id='footnote21'><a href="#ref21">[21]</a> <a href="https://wordpress.org/plugins/theme-check/">https://wordpress.org/plugins/theme-check/</a></li>
- <li id='footnote22'><a href="#ref22">[22]</a> <a href="http://automattic.com/security/">http://automattic.com/security/</a></li>
- <li id='footnote23'><a href="#ref23">[23]</a> <a href="https://codex.wordpress.org/WordPress_APIs">https://codex.wordpress.org/WordPress_APIs</a></li>
- <li id='footnote24'><a href="#ref24">[24]</a> <a href="https://codex.wordpress.org/Database_API">https://codex.wordpress.org/Database_API</a></li>
- <li id='footnote25'><a href="#ref25">[25]</a> <a href="https://codex.wordpress.org/Filesystem_API">https://codex.wordpress.org/Filesystem_API</a></li>
- <li id='footnote26'><a href="#ref26">[26]</a> <a href="http://codex.wordpress.org/Version_2.6">http://codex.wordpress.org/Version_2.6</a></li>
- <li id='footnote27'><a href="#ref27">[27]</a> <a href="https://codex.wordpress.org/HTTP_API">https://codex.wordpress.org/HTTP_API</a></li>
- <li id='footnote28'><a href="#ref28">[28]</a> <a href="https://codex.wordpress.org/Version_2.7">https://codex.wordpress.org/Version_2.7</a></li>
- <li id='footnote29'><a href="#ref29">[29]</a> <a href="http://codex.wordpress.org/Function_Reference/current_user_can">http://codex.wordpress.org/Function_Reference/current_user_can</a></li>
- </ul>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpagestatsphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-stats.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-stats.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-stats.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,53 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Stats
- *
- * Page template for displaying the Stats page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Statistics', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p><?php _esc_html_e( 'Here are some charts showing what sorts of systems people are running WordPress on. (You’ll need JavaScript enabled to see them.)', 'wporg' ); ?></p>
- <div id="wp_versions" class="wporg-stats-chart loading"></div>
- <div id="php_versions" class="wporg-stats-chart loading"></div>
- <div id="mysql_versions" class="wporg-stats-chart loading"></div>
- <div id="locales" class="wporg-stats-chart loading"></div>
- </section>
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre></div>
<a id="sitestrunkwordpressorgpublic_htmlwpcontentthemespubwporgmainpageswagphp"></a>
<div class="delfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Deleted: sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-swag.php</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-swag.php 2018-02-16 02:22:58 UTC (rev 6652)
+++ sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-swag.php 2018-02-16 05:03:05 UTC (rev 6653)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -1,67 +0,0 @@
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-<?php
-/**
- * Template Name: Swag
- *
- * Page template for displaying the Swag page.
- *
- * @package WordPressdotorg\MainTheme
- */
-
-namespace WordPressdotorg\MainTheme;
-
-if ( false === stristr( home_url(), 'test' ) ) {
- return get_template_part( 'page' );
-}
-
-get_header();
-the_post();
-?>
-
- <main id="main" class="site-main col-12" role="main">
-
- <article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
- <header class="entry-header">
- <h1 class="entry-title"><?php _esc_html_e( 'Swag', 'wporg' ); ?></h1>
- </header><!-- .entry-header -->
-
- <div class="entry-content row">
- <section class="col-8">
- <p>
- <a class="alignright" href="https://mercantile.wordpress.org">
- <img width="132" height="177" src="https://s.w.org/images/home/swag_col-1.jpg?1" alt="<?php esc_attr_e( 'WordPress Swag', 'wporg' ); ?>" />
- </a>
- <?php
- /* translators: Link to swag store */
- printf( wp_kses_post( ___( 'Whether you’re a seasoned WordPress fanatic or just getting warmed up, wear your WordPress love with pride. The official <a href="%s">WordPress Swag Store</a> sells shirts and hoodies in a variety of designs and colors, printed on stock from socially responsible companies.', 'wporg' ) ), esc_url( 'https://mercantile.wordpress.org' ) );
- ?>
- </p>
- <p><?php _esc_html_e( 'The swag store also rotates other products through the lineup on a regular basis.', 'wporg' ); ?></p>
- <p><?php _esc_html_e( 'The proceeds from these sales help offset the cost of providing free swag (buttons, stickers, etc.) to WordCamps and WordPress meetups around the world.', 'wporg' ); ?></p>
- <p>
- <?php
- /* translators: Link to swag store */
- printf( wp_kses_post( ___( 'So show the love and spread the word — get your <a href="%s">WordPress swag</a> today.', 'wporg' ) ), esc_url( 'https://mercantile.wordpress.org' ) );
- ?>
- </p>
-
- </section>
-
- </div><!-- .entry-content -->
-
- <?php
- edit_post_link(
- sprintf(
- /* translators: %s: Name of current post */
- esc_html__( 'Edit %s', 'wporg' ),
- the_title( '<span class="screen-reader-text">"', '"</span>', false )
- ),
- '<footer class="entry-footer"><span class="edit-link">',
- '</span></footer><!-- .entry-footer -->'
- );
- ?>
- </article><!-- #post-## -->
-
- </main><!-- #main -->
-
-<?php
-get_footer();
</del></span></pre>
</div>
</div>
</body>
</html>