INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(9001, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1517910618', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(9002, '_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:61:"\n	\n	\n	\n	\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"WordPress Planet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:28:"http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:2:"en";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:47:"WordPress Planet - http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:50:{i:0;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:45:"Dev Blog: WordPress 4.9.3 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5545";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wordpress.org/news/2018/02/wordpress-4-9-3-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3408:"<p>WordPress 4.9.3 is now available.</p>\n<p>This maintenance release fixes 34 bugs in 4.9, including fixes for Customizer changesets, widgets, visual editor, and PHP 7.2 compatibility. For a full list of changes, consult the <a href="https://core.trac.wordpress.org/query?status=closed&milestone=4.9.3&group=component">list of tickets</a> and the <a href="https://core.trac.wordpress.org/log/branches/4.9?rev=42630&stop_rev=42521">changelog</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.9.3</a> or visit Dashboard → Updates and click “Update Now.” Sites that support automatic background updates are already beginning to update automatically.</p>\n<p>Thank you to everyone who contributed to WordPress 4.9.3:</p>\n<p><a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/abdullahramzan/">abdullahramzan</a>, <a href="https://profiles.wordpress.org/adamsilverstein/">Adam Silverstein</a>, <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/andreiglingeanu/">andreiglingeanu</a>, <a href="https://profiles.wordpress.org/azaozz/">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/bpayton/">Brandon Payton</a>, <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a>, <a href="https://profiles.wordpress.org/coleh/">coleh</a>, <a href="https://profiles.wordpress.org/darko-a7/">Darko A7</a>, <a href="https://profiles.wordpress.org/desertsnowman/">David Cramer</a>, <a href="https://profiles.wordpress.org/dlh/">David Herrera</a>, <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a>, <a href="https://profiles.wordpress.org/flixos90/">Felix Arntz</a>, <a href="https://profiles.wordpress.org/frank-klein/">Frank Klein</a>, <a href="https://profiles.wordpress.org/pento/">Gary Pendergast</a>, <a href="https://profiles.wordpress.org/audrasjb/">Jb Audras</a>, <a href="https://profiles.wordpress.org/jbpaul17/">Jeffrey Paul</a>, <a href="https://profiles.wordpress.org/lizkarkoski/">lizkarkoski</a>, <a href="https://profiles.wordpress.org/clorith/">Marius L. J.</a>, <a href="https://profiles.wordpress.org/mattyrob/">mattyrob</a>, <a href="https://profiles.wordpress.org/monikarao/">Monika Rao</a>, <a href="https://profiles.wordpress.org/munyagu/">munyagu</a>, <a href="https://profiles.wordpress.org/ndavison/">ndavison</a>, <a href="https://profiles.wordpress.org/nickmomrik/">Nick Momrik</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a>, <a href="https://profiles.wordpress.org/rishishah/">rishishah</a>, <a href="https://profiles.wordpress.org/othellobloke/">Ryan Paul</a>, <a href="https://profiles.wordpress.org/sasiddiqui/">Sami Ahmed Siddiqui</a>, <a href="https://profiles.wordpress.org/sayedwp/">Sayed Taqui</a>, <a href="https://profiles.wordpress.org/seanchayes/">Sean Hayes</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/shooper/">Shawn Hooper</a>, <a href="https://profiles.wordpress.org/netweb/">Stephen Edgar</a>, <a href="https://profiles.wordpress.org/manikmist09/">Sultan Nasir Uddin</a>, <a href="https://profiles.wordpress.org/tigertech/">tigertech</a>, and <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 05 Feb 2018 19:47:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Sergey Biryukov";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"Mark Jaquith: Tips for configuring WordPress environments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:40:"http://markjaquith.wordpress.com/?p=5476";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:89:"https://markjaquith.wordpress.com/2018/02/05/tips-for-configuring-wordpress-environments/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4626:"<p>Many WordPress hosts will give your site a &#8220;staging&#8221; environment. You can also use tools like <a href="https://local.getflywheel.com/">Local by Flywheel</a>, or <a href="https://www.mamp.info/">MAMP Pro</a> to run a local &#8220;dev&#8221; version of your site. These are great ways of testing code changes, playing with new plugins, or making theme tweaks, without risking breaking your live &#8220;production&#8221; site.</p>\n<p>Here is my advice for working with different WordPress environments.</p>\n<h2>Handling Credentials</h2>\n<p>The live (&#8220;production&#8221;) version of your site should be opt-in. That is, your site&#8217;s Git repo should <strong>not</strong> store production credentials in <strong>wp-config.php</strong>. You don&#8217;t want something to happen like <a href="https://www.reddit.com/r/cscareerquestions/comments/6ez8ag/accidentally_destroyed_production_database_on/">when this developer accidentally connected to the production database</a> and destroyed all the company data on his first day.</p>\n<p>Instead of keeping database credentials in <strong>wp-config.php</strong>, have <strong>wp-config.php</strong> look for a <strong>local-config.php</strong> file. Replace the section that defines the database credentials with something like this:</p>\n<pre class="brush: php; title: ; notranslate">if ( file_exists( __DIR__ . ''/local-config.php'' ) ) {\n    include( __DIR__ . ''/local-config.php'' );\n} else {\n    die( ''local-config.php not found'' );\n}</pre>\n<p>Make sure you add <strong>local-config.php</strong> to your <strong>.gitignore</strong> so that no one commits their local version to the repo.</p>\n<p>On production, you&#8217;ll create a <strong>local-config.php</strong> with production credentials. On staging or development environments, you&#8217;ll create a <strong>local-config.php</strong> with the credentials for those environments.</p>\n<h2>Production is a Choice</h2>\n<p>Right after the section that calls out <strong>local-config.php</strong>, put something like this:</p>\n<pre class="brush: php; title: ; notranslate">if ( ! defined( ''WP_ENVIRONMENT'' ) ) {\n    define( ''WP_ENVIRONMENT'', ''development'' );\n}</pre>\n<p>The idea here is that there will always be a <strong>WP_ENVIRONMENT</strong> constant available to you that tells you what kind of environment your site is being run in. In production, you will put this in <strong>local-config.php</strong> along with the database credentials:</p>\n<pre class="brush: php; title: ; notranslate">define( ''WP_ENVIRONMENT'', ''production'' );</pre>\n<p>Now, in your theme, or your custom plugins, or other code, you can do things like this:</p>\n<pre class="brush: php; title: ; notranslate">if ( ''production'' === WP_ENVIRONMENT ) {\n    add_filter( ''option_gravityformsaddon_gravityformsstripe_settings'', function( $stripe_settings ) {\n        $stripe_settings[''api_mode''] = ''live'';\n        return $stripe_settings;\n    });\n} else {\n    add_filter( ''option_gravityformsaddon_gravityformsstripe_settings'', function( $stripe_settings ) {\n        $stripe_settings[''api_mode''] = ''test'';\n        return $stripe_settings;\n    });\n}</pre>\n<p>This bit of code is for the Easy Digital Downloads Stripe gateway plugin. It makes sure that on the production environment, the payment gateway is always in <strong>live</strong> mode, and the anywhere else, it is always in <strong>test</strong> mode. This protects against two very bad situations: connecting to live services from a test environment (which could result in customers being charged for test transactions) and connecting to test services from a live environment (which could prevent customers from purchasing products on your site).</p>\n<p>You can also use this pattern to do things like hide Google Analytics on your test sites, or make sure debug plugins are only active on development sites (more on that, in a future post!)</p>\n<p>Don&#8217;t rely on complicated procedures (&#8220;step 34: make sure you go into the Stripe settings and switch the site to test mode on your local test site&#8221;) — make these things explicit in code. Make it impossible to screw it up, and working on your sites will become faster and less stressful.</p>\n<hr />\n<p><b>Do you need <a href="https://coveredwebservices.com/">WordPress services?</a></b></p>\n<p>Mark runs <a href="https://coveredwebservices.com/">Covered Web Services</a> which specializes in custom WordPress solutions with focuses on security, speed optimization, plugin development and customization, and complex migrations.</p>\n<p>Please reach out to start a conversation!</p>\n[contact-form]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 05 Feb 2018 14:59:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Mark Jaquith";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:40:"Matt: National Magazine Award Nomination";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=47900";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:57:"https://ma.tt/2018/02/national-magazine-award-nomination/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:761:"<p>Longreads <a href="http://www.magazine.org/asme/about-asme/pressroom/asme-press-releases/ellies-2018-finalists-announced">was nominated today</a> for its first-ever <a href="https://en.wikipedia.org/wiki/National_Magazine_Awards">National Magazine Award</a>, in the category of columns and commentary, alongside ESPN The Magazine, BuzzFeed News, Pitchfork, and New York magazine. Laurie Penny&#x27;s Longreads columns <a href="https://longreads.com/tag/metoo-and-consent/">explore important questions of consent and female desire</a> that have strongly resonated in our current moment. In addition to this nomination, Penny&#x27;s columns have been translated and republished in Italian and German newspapers, and will be collected in a forthcoming book.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Feb 2018 21:37:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:46:"Dev Blog: The Month in WordPress: January 2018";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5541";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wordpress.org/news/2018/02/the-month-in-wordpress-january-2018/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3861:"<p>Things got off to a gradual start in 2018 with momentum starting to pick up over the course of the month. There were some notable developments in January, including a new point release and work being done on other important areas of the WordPress project.</p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<h2>WordPress 4.9.2 Security and Maintenance Release</h2>\n\n\n\n<p>On January 16, <a href="https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/">WordPress 4.9.2 was released</a> to fix an important security issue with the media player, as well as a number of other smaller bugs. This release goes a long way to smoothing out the 4.9 release cycle with the next point release, v4.9.3, <a href="https://make.wordpress.org/core/2018/01/31/wordpress-4-9-3-release-pushed-to-february-5th/">due in early February</a>.</p>\n\n\n\n<p>To get involved in building WordPress Core, jump into the #core channel in the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>, and follow<a href="https://make.wordpress.org/core/"> the Core team blog</a>.</p>\n\n\n\n<h2>Updated Plugin Directory Guidelines</h2>\n\n\n\n<p>At the end of 2017, <a href="https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/">the guidelines for the Plugin Directory</a> received a significant update to make them clearer and expanded to address certain situations. This does not necessarily make these guidelines complete, but rather more user-friendly and practical; they govern how developers build plugins for the Plugin Directory, so they need to evolve with the global community that the Directory serves.</p>\n\n\n\n<p>If you would like to contribute to these guidelines, you can make a pull request to <a href="https://github.com/WordPress/wporg-plugin-guidelines">the GitHub repository</a> or email <a href="mailto:plugins@wordpress.org">plugins@wordpress.org</a>. You can also jump into the #pluginreview channel in the<a href="https://make.wordpress.org/chat/"> Making WordPress Slack group</a>.</p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul>\n    <li>Near the end of last year a lot of work was put into improving the standards in the WordPress core codebase and now <a href="https://make.wordpress.org/core/2017/11/30/wordpress-php-now-mostly-conforms-to-wordpress-coding-standards/">the entire platform is at nearly 100% compliance with the WordPress coding standards</a>.</li>\n    <li>Gutenberg, the new editor coming to WordPress core in the next major release, <a href="https://make.wordpress.org/core/2018/01/25/whats-new-in-gutenberg-25th-january/">was updated to v2.1 this month</a> with some great usability and technical improvements.</li>\n    <li>The Global Community Team is <a href="https://make.wordpress.org/community/2018/01/16/2018-goals-for-the-global-community-team-suggestions-time/">taking suggestions for the goals of the Community program in 2018</a>.</li>\n    <li><a href="https://online.wpcampus.org/">WPCampus Online</a>, a digital conference focused on WordPress in higher education, took place on January 30. The videos of the event sessions will be online soon.</li>\n    <li>A WordPress community member <a href="https://wptavern.com/new-toolkit-simplifies-the-process-of-creating-gutenberg-blocks">has released a toolkit</a> to help developers build blocks for Gutenberg.</li>\n    <li>The community team that works to improve the WordPress hosting experience is relatively young, but <a href="https://make.wordpress.org/hosting/2018/01/25/hosting-meeting-notes-january-10-2018/">they have been making some great progress recently</a>.</li>\n</ul>\n\n\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Feb 2018 08:30:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Hugh Lashbrooke";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:54:"WPTavern: WordPress 4.9.3 Rescheduled for February 5th";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=78058";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wptavern.com/wordpress-4-9-3-rescheduled-for-february-5th";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1336:"<p>WordPress 4.9.3 is a maintenance release and was originally scheduled to be available on January 30th. However, due to ongoing tickets and a short time frame to test the <a href="https://make.wordpress.org/core/2018/02/01/wordpress-4-9-3-rc/">release candidate</a>, it has <a href="https://make.wordpress.org/core/2018/01/31/wordpress-4-9-3-release-pushed-to-february-5th/">been pushed back</a> to February 5th.</p>\n<p><a href="https://make.wordpress.org/core/2018/02/01/wordpress-4-9-3-rc/">WordPress 4.9.3 RC 1</a> is available for testing. This release <a href="https://make.wordpress.org/core/2018/01/24/jshint-removed-from-codemirror-in-4-9-3/">removes JSHint from the code editors</a> due to conflicts with the GPL License. If your code relies on JSHint from Core, <a href="https://core.trac.wordpress.org/ticket/42850">developers encourage</a> you to update it to use a copy of JSHint.</p>\n<p>Other changes in 4.9.3 include, avoiding page scrolling when navigating the media modal, a handful of improvements to the customizer, <a href="https://make.wordpress.org/core/2018/01/26/wordpress-4-9-3-beta/">and more</a>. Please test WordPress 4.9.3 on a staging site and if you encounter any bugs, you can report them on the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta section</a> of the support forums.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Feb 2018 08:09:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:78:"WPTavern: WooCommerce 3.3 Removed From Plugin Directory Due to Theme Conflicts";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77962";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:89:"https://wptavern.com/woocommerce-3-3-removed-from-plugin-directory-due-to-theme-conflicts";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3081:"<p>Earlier this week, WooCommerce 3.3 <a href="https://wptavern.com/woocommerce-3-3-increases-theme-compatibility-auto-regenerates-thumbnails">was released</a> and among the features was increased theme compatibility. However, soon after release, users of third-party themes <a href="https://wordpress.org/support/topic/wc-3-3-issues-with-categories-displaying-in-shop/">reported issues</a> with categories displaying improperly.</p>\n<p>Despite it being a minor release that should be fully backwards compatible with previous releases up to 3.0, WooCommerce has removed 3.3 from the plugin directory and replaced it with 3.2.6.</p>\n<p>According <a href="https://woocommerce.wordpress.com/2018/02/01/woocommerce-3-3-1-status-update/">to a post</a> on the project&#8217;s official blog, WooCommerce 3.3.1 will take the place of 3.3 and will include a fix for the category display issue.</p>\n<blockquote class="wp-block-quote"><p>The issue affected themes with template overrides from 3.2.x which hadn’t been made compatible with 3.3. In general, <a href="https://github.com/woocommerce/woocommerce/wiki/Template-File-Guidelines-for-Devs-and-Theme-Authors#hook-vs-override---when-to-use-what">we recommend that themes use hooks instead of template overrides.</a> Themes such as <a href="https://en-gb.wordpress.org/themes/storefront/">Storefront</a> (which does not use template overrides) were compatible at launch.</p>\n<p><cite>WooCommerce Blog</cite></p></blockquote>\n<p>If you&#8217;ve already updated to WooCommerce 3.3 and your theme is compatible, you don&#8217;t need to make any changes. If your theme is not compatible, WooCommerce recommends checking with your theme&#8217;s author to see if a compatibility fix has been released.</p>\n<p>Users can also wait for the release of 3.3.1, update to the <a href="https://github.com/woocommerce/woocommerce/releases/tag/3.3.1-rc.1">pre-release version</a> of 3.3.1, or use the <a href="https://wordpress.org/plugins/wp-rollback/">WP-Rollback plugin</a> and revert back to 3.2.6. WooCommerce developers suggest only going the WP-Rollback route if you&#8217;re not comfortable installing pre-release software.</p>\n<p>Coen Jacobs, a former member of the WooCommerce development team, commented on Twitter that this was the first time he can remember that a release was reverted.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Fun fact: As far as I recall, there has never been a release of WooCommerce that has been withdrawn before. During my time on the development team we have pushed fix releases on the same day as a big releases, but never was it reverted like this.</p>\n<p>&mdash; Coen Jacobs (@CoenJacobs) <a href="https://twitter.com/CoenJacobs/status/958768816808497152?ref_src=twsrc%5Etfw">January 31, 2018</a></p></blockquote>\n<p></p>\n<p>The development team has tested 3.3.1 with more than 40 different themes and believe it is stable. However, they are exercising caution and thoroughly testing the fixes with more themes. Users can expect to see 3.3.1 officially released the week of February 5th.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Feb 2018 07:06:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:81:"WPTavern: WPWeekly Episode 303 – Interview With Zac Gordon, Technology Educator";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=77901&preview=true&preview_id=77901";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:87:"https://wptavern.com/wpweekly-episode-303-interview-with-zac-gordon-technology-educator";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1902:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> and I are joined by <a href="http://zacgordon.com/">Zac Gordon</a>. We discussed a wide range of topics including, balancing freelance work with educating, an overview of Gutenberg from an educator&#8217;s perspective, and potential brand issues if the Gutenberg name <a href="githubhttps://github.com/WordPress/gutenberg/issues/4681">was deprecated</a>. We also talked about some of the difficulties involved with <a href="https://gutenberg.courses/">creating a course</a> around a feature that&#8217;s not yet part of WordPress core.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://ithemes.com/2018/01/31/ithemes-joining-the-liquid-web-family/">iThemes Acquired by LiquidWeb</a><br />\n<a href="https://woocommerce.com/2018/01/whats-new-woocommerce-3-3/">WooCommerce 3.3 Released</a><br />\n<a href="https://wptavern.com/updraftplus-acquires-easy-updates-manager-plugin">Easy Updates Manager Acquired by UpdraftPlus</a></p>\n<h2>Picks of the Week:</h2>\n<p>John James Jacoby suggested <a href="https://www.beamauthentic.com/">Beam Authentic</a>. Beam Authentic is a wearable, connected, smart button that can be programmed to display different images through an app.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, February 7th 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #303:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Feb 2018 02:12:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:100:"WPTavern: Efrain Rivera, A Longtime Community Member, WordCamp Organizer, and Volunteer, Passes Away";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77893";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:107:"https://wptavern.com/efrain-rivera-a-longtime-community-member-wordcamp-organizer-and-volunteer-passes-away";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2776:"<p>Efrain Rivera, who helped organize and volunteer at numerous WordCamps in Florida has passed away at the age of 47. The news was shared on Facebook by his sister on January 28th.</p>\n<img />Efrain Rivera and his wife at WordCamp Miami. Photo courtesy of David Bisset\n<p>David Bisset, organizer of WordCamp Miami and a well-known figure in the Florida WordPress community, <a href="http://davidbisset.com/efrain-rivera/">shared his thoughts</a> on Rivera&#8217;s passing.</p>\n<blockquote><p>Efrain wasn’t just a fellow organizer, but also a supporter of the local WordPress meetups. There was no ulterior motive in anything that he did. Never once did he ask for anything – he was just happy to be there and help out. He was 100% about giving back to the WordPress community, but even if the community didn’t exist he would find a way to help out folks.</p>\n<p>Efrain wasn’t just a supporter and volunteer. He was a good friend to have – someone you could speak frankly too.</p></blockquote>\n<p>Rivera is being remembered as a kind, compassionate, and happy person by members of the community.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">I’m so sorry, he was a pleasure volunteering with,  <a href="https://twitter.com/EfrainWp?ref_src=twsrc%5Etfw">@EfrainWp</a> was always happy to help and answer questions.</p>\n<p>&mdash; Rian M. Kinney, Esq. (@TheKinneyFirm) <a href="https://twitter.com/TheKinneyFirm/status/958855848784252928?ref_src=twsrc%5Etfw">February 1, 2018</a></p></blockquote>\n<p></p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">I remember his kindness David. What a great person and sad loss.</p>\n<p>&mdash; Diane Kinney (@dkinney) <a href="https://twitter.com/dkinney/status/958858994843611138?ref_src=twsrc%5Etfw">February 1, 2018</a></p></blockquote>\n<p></p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Efrain was one of happiest, smiliest, caring people I’d ever hung out with at any WordPress event. <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f64f.png" alt="?" class="wp-smiley" /> <a href="https://t.co/qW7ChUmjX0">https://t.co/qW7ChUmjX0</a></p>\n<p>&mdash; J ³ (@JJJ) <a href="https://twitter.com/JJJ/status/958448885030182913?ref_src=twsrc%5Etfw">January 30, 2018</a></p></blockquote>\n<p></p>\n<p><a href="https://memorials.serenitymemorialchapels.com/efrain-rivera/3417849/obituary.php">Memorial services are scheduled</a> for Saturday, February 3, 2018 from 4:00 P.M.-9:00 P.M. EST at Serenity Funeral Home and Cremation, 1450 S State Road 7, North Lauderdale, Florida 33068. The service will take place during visitation at 7PM. If you have any memories of meeting or hanging out with Efrain at any of the WordPress events in Florida, please share them in the comments.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Feb 2018 01:13:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:44:"Post Status: Liquid Web has acquired iThemes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=41738";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://poststatus.com/liquid-web-acquired-ithemes/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5096:"<p><a href="https://www.liquidweb.com/">Liquid Web</a> has acquired <a href="https://ithemes.com/">iThemes</a>, in an all cash deal that includes the entire iThemes team moving over to Liquid Web as an independent unit. Cory Miller &#8212; CEO of iThemes &#8212; will be the Business Manager of the new unit, with iThemes COO Matt Danner as the Director of Technology and Operations for iThemes. The entire team of twenty three people is staying on, and will continue to be headquartered in Oklahoma.</p>\n<p>This is not the first or last time we&#8217;ll see longstanding WordPress companies get rolled into large hosting providers. It&#8217;s a trend that is natural in any ecosystem as it matures, and iThemes was a clear and quality candidate for a host to target. Cory said the culture around Liquid Web, including their &#8220;heroic support,&#8221; but also the quality he sees in their management team, was a key motivator for them to go work with Liquid Web.</p>\n<p>As hosting companies evolve more and more to provide broader services for customers with managed WordPress offerings, there is less room for utility product creators to fill that gap.</p>\n<p>Backups are a fine example: customers may see less need for external backups if they have confidence that their hosting is managing backups properly. Security is another. These have been great products for iThemes, and still are &#8212; but their current markets are more for hosts without a managed experience, and that slice of the pie has been narrowing.</p>\n<p>iThemes has had a partnership with Liquid Web for about a year and a half now, which started by licensing iThemes Sync for Liquid Web&#8217;s WordPress hosting offering. They&#8217;ve slowly been integrating more features into the platform, and the acquisition will allow Liquid Web to further integrate iThemes&#8217; offerings, and allow iThemes to improve some of their product offerings with the backing of Liquid&#8217;s Web&#8217;s hosting infrastructure.</p>\n<p>I spoke to Cory Miller about the move, which is occurring not long after iThemes&#8217; ten year anniversary in business. He said he looks back every year and sees them as chapters in the iThemes story, and this feels just the same. He&#8217;s excited about what the backing from Liquid Web will allow them to do, and most importantly for him, the ability to keep supporting the team they have built over the years.</p>\n<p>Cory tells me he&#8217;s amazed that they&#8217;ve been able to build the company they have built, and neither he nor his business partners would have imagined it ten years ago. All equity holders had their shares purchased by Liquid Web, and Cory and the team will be Liquid Web employees.</p>\n<p>iThemes has iterated on the business many times over the years &#8212; as the name implies. Their theme business slowly dwindled in terms of the overall ratio of sales revenue it provided. BackupBuddy has long been a flagship, and they&#8217;ve found great success the past couple of years since they acquired and iterated on the iThemes Security product. He said that it took them experimenting a great deal &#8212; and like Exchange for eCommerce, and others &#8212; it didn&#8217;t always work out the way they hoped. But because they stayed agile and kept working at it, they&#8217;ve consistently been able to grow and diversify their product line.</p>\n<p>One practical component Liquid Web will be able to provide, as an example, is their data centers to power BackupBuddy and iThemes Stash storage and processing. iThemes has historically used Amazon, which Cory said really adds up and has started to eat into their own margins. Liquid Web will help them not only improve the offering but also to be able to perform those functions more affordably.</p>\n<p>For Liquid Web, this acquisition furthers their goal to integrate WordPress-specific functionality into their suite of WordPress hosting tools. They recently launched WooCommerce hosting on their platform, and the iThemes Sales Accelerator product can now be a core component of that offering. Additionally, the technology iThemes has built with BackupBuddy and Sync will further add to their platform.</p>\n<p>Beyond the technology and products, Liquid Web Vice President of Products and Innovation Chris Lema tells me it&#8217;s about the team:</p>\n<blockquote><p>This adds so much to what we’re doing with managed WordPress and managed WooCommerce, that it just made a lot of sense — both from a product perspective, and even more from a team perspective.</p></blockquote>\n<p>Having spent a lot of time with the management teams for each of these companies, I would agree that the culture fit is a really good one. And for Liquid Web, a company continuing to make its big push into the WordPress market, it is a solid strategic acquisition move that offers product dividends but more importantly adds a great and experienced WordPress team to their company.</p>\n<p><a href="https://ithemes.com/2018/01/31/ithemes-joining-the-liquid-web-family/">Cory shares more</a> about the news on the iThemes blog.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 31 Jan 2018 17:12:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:60:"HeroPress: The Journey: Curiosity, Challenge, Transformation";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2431";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:158:"https://heropress.com/essays/journey-curiosity-challenge-transformation/#utm_source=rss&utm_medium=rss&utm_campaign=journey-curiosity-challenge-transformation";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:9293:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/01/013118-2-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: My place in the world has transformed." /><p>When I look back on the past five years I’ve been working with WordPress, I feel the real weight of the journey I’ve had to get where I am. Much of it has been filled with challenge of both of the difficult and welcome variety. I’m an optimist and problem-solver to the core, but I sometimes wonder how I got through these past years. One thing is for certain, my involvement with WordPress, the opportunities and community around it, has been a force for so much good, motivation, and satisfaction in my life.</p>\n<h2>The Beginning</h2>\n<p>When I was introduced to WordPress, I was going through one of the most trying times of my adult life. My dad had suddenly passed away just a few years before. We didn’t have the best relationship, but his quirkiness, interest in esoteric things, and passion for food certainly rubbed off on me.</p>\n<p>I was living with roommates, but moved back home to be with my mom. Not too long after, she developed debilitating osteoarthritis in both of her hips. From a physically healthy yet grieving 52-year-old woman to eventually becoming handicap and walker-bound, needless to say, impacted our lives greatly. I became her caretaker, and I also worked retail part-time for the flexible schedule.</p>\n<blockquote><p>I felt emotionally exhausted, uninspired and quite lost with what my next steps would be.</p></blockquote>\n<p>I grew up using the internet fervently as a youth and in my college years. I met new friends, learned new skills, and traveled to new places thanks the endless source of information it provided for my active mind. So when a friend, now my mentor, John Bolyard, approached me to help him in his web marketing and development consultancy using “WordPress” I just said “yes.” It was mysterious, being unknown to me, and intriguing, which is usually a green light in my book!</p>\n<p>I started doing administrative work on a website he helped develop for a national guild. Like many situations, he had finished their website and they would circle back to him for minor updates. I took on the minor updates, started tinkering on my own, and fell in love in the process.</p>\n<p>The accessibility with which one could make changes and produce content dynamically was just mind blowing to me. It was my gateway to web development and now I could make web content with the ability to work with code, if I so chose. It seemed an endless source of learning and knowledge- it was a great fit.</p>\n<h2>Levelling Up</h2>\n<p>That went well and he brought me on a larger project to help the artist, Dorothy Braudy, create her website archive. I was able to blend my affinity for the technical and handy visual memory to help an all around amazing person (she&#8217;s still one of closest people in my life) tell her story through her art. I was thrilled to have the challenge and the privilege to bring her vibrant and prolific work (hundreds of pieces) to the web.</p>\n<p>I also started assisting John with teaching WordPress classes at SCORE, a government organization that helps people develop and sustain small businesses.</p>\n<blockquote><p>We volunteered our time teaching business owners WordPress to help them build their own websites.</p></blockquote>\n<p>It was challenging yet rewarding to see them feel empowered that they could take a hands-on role in making their web presence.</p>\n<p>Nevertheless, I ended up with several clients and that’s how my freelancing career began :). I also started going to meetups. John brought me to my first one in the San Fernando Valley. I was like wait&#8230;this software is cool and people gather to talk about it? I can also learn stuff too?! Get outta town!</p>\n<p>Well, I started attending fairly frequently. Particularly, the meetup in the West Valley lead by Andrew Behla (then at the Topanga Canyon Library). I soaked up info from presentations given by Roy Sivan, Suzette Franck, and Lucy Beer (who is now my teammate). Just to name a few ;).</p>\n<p>After building a consistent client base, I also started working part-time as a project assistant at a boutique museum exhibit development firm. My first project was for the Huntington Library, Art Collections and Botanical Gardens supporting the development of an educational WordPress website for their Junípero Serra exhibition. What were the chances? My skills in WordPress proved helpful for the project and the firm&#8217;s website.</p>\n<h2>Pivoting</h2>\n<p>At this point, I had seen my mom through her first hip replacement and recovery, and she was moving on to her next one. I thought about where I saw myself and also where I could build a sustainable future given the circumstances. I thought WordPress, and so I did a trial as a Happiness Engineer at WordPress.com.</p>\n<p>While I didn&#8217;t get the position, I met some great people and learned exponentially more in that short time than I had on my own. More so, I learned about the users, WordPress’ strengths and weaknesses, and how to fill that gap in an accessible way. I was sad, but also motivated. I took on more client work and just did the thing.</p>\n<p>After three years, it was time to leave the exhibit development firm. It was fascinating, it provided me a design, development and project management vocabulary I had never encountered before. However, I needed a firmer career path and I still thought WordPress. My mom was recovered, I had also just recovered from some health issues, and I knew it was time for a change.</p>\n<p>While doing client work for several months, I also explored options on how I could &#8220;level up.&#8221; Maybe it was my time to dig into web development: should I learn on my own, go to a school?</p>\n<blockquote><p>In my gut, I knew I had to find work that supported my endeavors, so I started applying in the WordPress and tech ecosystem.</p></blockquote>\n<p>I networked, attended workshops, and met some awesome folks in the local tech and WordPress communities. I was also approached about joining the organizer team for WordCamp Los Angeles (WCLAX). I said “yes” (that magic word) and last year we had a great event.</p>\n<p>When we started planning, I had also heard from WP Media, (the company behind the WP Rocket and Imagify plugins), that I was hired for their Customer Support position. We’re a remote crew spread across 8 countries. However, I’ve been lucky enough to spend time with them at WordCamp Europe, WordCamp US, and our annual retreat last year.</p>\n<h2>Transformation</h2>\n<p>My place in the world has transformed. I&#8217;ve traveled to places once out of reach, work every day with some of the most brilliant and kind people in the WordPress space, and grow day by day with new challenges and opportunities. I&#8217;m happy, mom is healthy, and the journey continues…</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: The Journey: Curiosity, Challenge, Transformation" class="rtsocial-twitter-button" href="https://twitter.com/share?text=The%20Journey%3A%20Curiosity%2C%20Challenge%2C%20Transformation&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fjourney-curiosity-challenge-transformation%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: The Journey: Curiosity, Challenge, Transformation" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fjourney-curiosity-challenge-transformation%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fjourney-curiosity-challenge-transformation%2F&title=The+Journey%3A+Curiosity%2C+Challenge%2C+Transformation" rel="nofollow" target="_blank" title="Share: The Journey: Curiosity, Challenge, Transformation"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/journey-curiosity-challenge-transformation/&media=https://heropress.com/wp-content/uploads/2018/01/013118-2-150x150.jpg&description=The Journey: Curiosity, Challenge, Transformation" rel="nofollow" target="_blank" title="Pin: The Journey: Curiosity, Challenge, Transformation"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/journey-curiosity-challenge-transformation/" title="The Journey: Curiosity, Challenge, Transformation"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/journey-curiosity-challenge-transformation/">The Journey: Curiosity, Challenge, Transformation</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 31 Jan 2018 11:00:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Renee Johnson";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:84:"WPTavern: WooCommerce 3.3 Increases Theme Compatibility, Auto Regenerates Thumbnails";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77795";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:94:"https://wptavern.com/woocommerce-3-3-increases-theme-compatibility-auto-regenerates-thumbnails";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3108:"<p>WooCommerce 3.3 <a href="https://woocommerce.com/2018/01/whats-new-woocommerce-3-3/">is available</a> and is considered a minor release. Based on the project’s <a href="https://github.com/woocommerce/woocommerce/wiki/Roadmap-and-release-process">new release process</a>, it should be fully backwards compatible with previous releases up to 3.0.</p>\n<p>The orders screen has been redesigned with large buttons that indicate an order’s status. You can also view an order’s details from the order screen without having to edit the order.</p>\n<img class="aligncenter" src="https://i2.wp.com/wptavern.com/wp-content/uploads/2018/01/WC33OrdersScreen.png?w=627&ssl=1" alt="" width="627" height="261" />WooCommerce 3.3 Orders Screen\n<p>For products that are on backorder and have stock management enabled, WooCommerce 3.3 will automatically transition from ‘In stock’ to ‘On backorder’ or ‘Out of stock’ as the inventory decreases. Once inventory is added, the status will switch back to ‘In Stock’.</p>\n<img class="aligncenter" src="https://i2.wp.com/wptavern.com/wp-content/uploads/2018/01/WC33OrderStatus.png?w=627&ssl=1" alt="" width="627" height="328" />WooCommerce 3.3 Order Status Screen\n<p>For full compatibility, users generally needed to use a WordPress theme that specifically supported WooCommerce. In 3.3, improvements have been made so that WooCommerce renders on themes that don’t fully support it, making it compatible with nearly every WordPress theme.</p>\n<p>Users can now set the number of columns and rows for shops with the ability to preview the results live via the Customizer. The columns will resize to fill the entire width of the area and is available on all themes.</p>\n<p>In earlier versions of WooCommerce, shop owners needed to use the <a href="https://wordpress.org/plugins/regenerate-thumbnails/">Regenerate Thumbnails</a> after updating a product’s image as WordPress did not automatically resize the image and generate new thumbnails. WooCommerce 3.3 adds on-the-fly thumbnail regeneration and background thumbnail resizing.</p>\n<p>In addition, users can customize the aspect ratios of product images. The choices are classic square images, custom cropped images, or uncropped images</p>\n<img class="aligncenter" src="https://i2.wp.com/wptavern.com/wp-content/uploads/2018/01/WC33ImageAspectRatio.png?w=627&ssl=1" alt="" width="627" height="402" />WooCommerce 3.3 Image Aspect Ratio Options\n<p>Shop owners can now view logs of product downloads with a couple of built-in filters including, by order, by product, by customer, and by file. You can also search for extensions now from the Extensions administration screen.</p>\n<p>WooCommerce 3.3 includes more features and changes than what’s listed here. For a detailed overview of what’s new in 3.3, <a href="https://github.com/woocommerce/woocommerce/blob/release/3.3/readme.txt">check out the changelog</a>. If you think you’ve discovered a bug, please report it on the <a href="https://github.com/woothemes/woocommerce/issues">project’s GitHub page</a>.</p>\n<p><!-- /wp:core/paragraph --></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 30 Jan 2018 22:53:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:48:"Mark Jaquith: Simple WordPress deploys using Git";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:40:"http://markjaquith.wordpress.com/?p=5422";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:80:"https://markjaquith.wordpress.com/2018/01/30/simple-wordpress-deploys-using-git/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3328:"<p>A few weeks back, Clifton Griffin asked me a question about deploying WordPress sites:</p>\n<div class="embed-twitter">\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr"><a href="https://twitter.com/markjaquith?ref_src=twsrc%5Etfw">@markjaquith</a> Hey Mark, quick question: Do you still use and recommend Capistrano?</p>\n<p>&mdash; Clifton Griffin (@clifgriffin) <a href="https://twitter.com/clifgriffin/status/948373150680707073?ref_src=twsrc%5Etfw">January 3, 2018</a></p></blockquote>\n<p></div>\n<p>I <b>do not</b> use Capistrano for deployments anymore, for one simple reason: it was massive overkill for most of the sites I manage, and maintaining it was not worth the benefit.</p>\n<p>My current deployment system for WordPress sites is simple: I use Git.</p>\n<p>I&#8217;m already using Git for version control of the site&#8217;s code, so using Git for deployments is not that much more work. There are a few ways to do this, but the simplest way is to just make your site root a Git checkout of your site files.</p>\n<p>Then, if your server has read-access to your Git remote, you can run some Git commands to sync everything. Here are your options:</p>\n<ol>\n<li><strong>git pull</strong> — Simple, but might fail if someone naughty has made code modifications on the server.</li>\n<li><strong>git fetch &amp;&amp; git reset &#8211;hard origin/master</strong> — The hard reset method will wipe any local modifications that someone has mistakenly made.</li>\n</ol>\n<p>But wait. Before you implement this, it is very important that you ensure that your server&#8217;s <strong>.git</strong> directory is not readable, as it might be able to leak sensitive information about your site&#8217;s code. How you do this will depend on what web server you&#8217;re running. In Nginx, I do the following:</p>\n<pre class="brush: plain; title: ; notranslate">location ~ /\\.(ht[a-z]+|git|svn) {\ndeny all;\n}</pre>\n<p>In Apache, you could put the following in your <strong>.htaccess</strong> file:</p>\n<pre class="brush: plain; title: ; notranslate">RedirectMatch 404 /\\.git</pre>\n<p>SSHing into your server every time is tedious, so let&#8217;s script that:</p>\n<pre class="brush: bash; title: ; notranslate">#!/bin/bash\nssh example.com ''cd /srv/www/example.com &amp;&amp; git pull''</pre>\n<p>Save that to <strong>deploy.sh</strong> in your Git repo, run <strong>chmod +x deploy.sh</strong>, and commit it to the repo. Now when you&#8217;re ready to deploy the site, just type <strong>./deploy.sh</strong> and the public site will pull down the latest changes from your main Git remote.</p>\n<p>Bonus points if you make <strong>deploy.sh</strong> take an optional commit hash, so you can also use this tool to roll back to a previous hash, in case a commit goes wrong.</p>\n<p>This method has served me well, for years, and has required no maintenance.</p>\n<p>What methods are you using for WordPress code deploys?</p>\n<hr />\n<p><b>Do you need <a href="https://coveredwebservices.com/">WordPress services?</a></b></p>\n<p>Mark runs <a href="https://coveredwebservices.com/">Covered Web Services</a> which specializes in custom WordPress solutions with focuses on security, speed optimization, plugin development and customization, and complex migrations.</p>\n<p>Please reach out to start a conversation!</p>\n[contact-form]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 30 Jan 2018 15:31:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Mark Jaquith";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:12;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:58:"WPTavern: UpdraftPlus Acquires Easy Updates Manager Plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77700";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wptavern.com/updraftplus-acquires-easy-updates-manager-plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2048:"<p><a href="https://updraftplus.com/">UpdraftPlus</a>, a popular WordPress backup plugin actively installed on more than 1 million sites has acquired the <a href="https://wordpress.org/plugins/stops-core-theme-and-plugin-updates/">Easy Updates Manager</a> plugin for an undisclosed amount.</p>\n<p>Easy Updates Manager disables core, theme, and plugin updates in WordPress and provides granular control over them. It was created in 2015, is actively installed on more than 100K sites, and is maintained by <a href="https://profiles.wordpress.org/kidsguide/">Matthew Sparrow</a>, <a href="https://profiles.wordpress.org/ronalfy/">Ronald Huereca</a>, <a href="https://profiles.wordpress.org/roary86/">Roary Tubbs</a>, and <a href="https://profiles.wordpress.org/bigwing/">BigWing Interactive</a>.</p>\n<img />Easy Updates manager User Interface\n<p>Burnout was a contributing factor for selling the plugin. &#8220;Matthew Sparrow and I were both burnt out on the project, so the offer to sell was a no-brainer,&#8221; Huereca said. &#8220;It’s bittersweet letting our baby go, but it’s in good hands.&#8221;</p>\n<p>Without proper vetting, selling established plugins to individuals or companies can be harmful to sites and tarnish its reputation. Because UpdraftPlus is a well established company, Huereca didn&#8217;t have to do a lot of research.</p>\n<p>&#8220;We were looking for more backend plugins that we understand and it&#8217;s a great plugin, highly rated and growing,&#8221; A company representative said. &#8220;Updates and backups go hand-in-hand as people should really backup before updating.&#8221;</p>\n<p>UpdraftPlus will focus its marketing efforts towards <a href="https://updraftplus.com/updraftcentral/">UpdraftCentral</a> later this year. UpdraftCentral provides the ability for users to update, backup, and manage their sites from one dashboard. Easy Updates Manager and UpdraftCentral are complimentary products.</p>\n<p>Users can expect to see more updates later this year and continued refinement of the user interface.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 30 Jan 2018 00:30:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:61:"BuddyPress: BuddyPress 2.9.3 Security and Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://buddypress.org/?p=270325";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:81:"https://buddypress.org/2018/01/buddypress-2-9-3-security-and-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1312:"<p>BuddyPress 2.9.3 is now available. This is a security and maintenance release. We strongly encourage all BuddyPress sites to upgrade as soon as possible.</p>\n<p>The 2.9.3 release addresses two security issues:</p>\n<ul>\n<li>A dynamic template loading feature could be used in some cases for unauthorized file execution and directory traversal. Reported by <a href="https://pritect.net">James Golovich</a>.</li>\n<li>Some permissions checks and path validations in the attachment deletion process were hardened. Reported by <a href="https://www.ripstech.com/">RIPSTech</a> and <a href="https://profiles.wordpress.org/slaFFik/">Slava Abakumov</a> of the BuddyPress security team.</li>\n</ul>\n<p>These vulnerabilities were reported privately to the BuddyPress team, in accordance with <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/">WordPress&#8217;s security policies</a>. Our thanks to all reporters for practicing coordinated disclosure.</p>\n<p>In addition, 2.9.3 includes a change that fixes the ability to install legacy bbPress 1.x forums. Please note that legacy forum support will be removed altogether in BuddyPress 3.0; see <a href="https://bpdevel.wordpress.com/2017/12/07/legacy-forums-support-will-be/">the announcement blog post</a> for more details.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 Jan 2018 18:11:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Boone Gorges";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:14;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:61:"Post Status: WordPress Market Opportunities — Draft podcast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=41485";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"https://poststatus.com/wordpress-market-opportunities-draft-podcast/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2459:"<p>Welcome to the Post Status <a href="https://poststatus.com/category/draft">Draft podcast</a>, which you can find <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">on iTunes</a>, <a href="https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast">Google Play</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, and <a href="http://simplecast.fm/podcasts/1061/rss">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.</p>\n<p>In this episode, Brian and Brian discuss market segmentation across the WordPress ecosystem. The focus for this discussion focused entirely on the entry-level segment of site assemblers and their small-business clients as well as the mid-level market of contractors and agencies selling additional levels of service. The duo talked through a few different strategies employed in each segment, including service differentiation, regional focus, building a network of complementary contractors, systemizing processes, delivering quality customer support flow, and selling ongoing service.</p>\n<p>In addition to this look at market segmentation, the Brians shared a few useful resources for both Gutenberg and WP-CLI.</p>\n<p></p>\n<h3>Links</h3>\n<ul>\n<li>Mike McAlister&#8217;s <a href="http://gutenberg.news/">Gutenberg News</a></li>\n<li>Ahmed Awais&#8217;s <a href="https://github.com/ahmadawais/create-guten-block">create-gutenberg-block</a></li>\n<li>Delicious Brain&#8217;s <a href="https://deliciousbrains.com/wordpress-cli-packages-review/">WP-CLI packages reviews</a></li>\n<li>WordPress Website: <a href="https://poststatus.com/wordpress-website-cost/">How much should it cost?</a></li>\n<li><a href="https://wpsessions.com/sessions/selling-ongoing-service/">Selling Ongoing Services with Sara Dunn</a></li>\n</ul>\n<h3>Sponsor: iThemes</h3>\n<p>This episode is sponsored by <a href="https://ithemes.com/?utm_source=post_status&utm_medium=banner&utm_campaign=ps_ads">iThemes</a>. The team at iThemes offers WordPress plugins, themes and training to help take the guesswork out of building, maintaining and securing WordPress websites. For more information, check out their <a href="https://ithemes.com/?utm_source=post_status&utm_medium=banner&utm_campaign=ps_ads">website</a> and thank you to iThemes for being a Post Status partner.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 Jan 2018 16:50:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Katie Richards";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:15;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:72:"WPTavern: WPWeekly Episode 302 – Brian Gardner, Founder of StudioPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=77689&preview=true&preview_id=77689";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:78:"https://wptavern.com/wpweekly-episode-302-brian-gardner-founder-of-studiopress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1338:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> and I are joined by <a href="https://briangardner.com/">Brian Gardner</a>, founder of <a href="https://www.studiopress.com/">StudioPress</a>. We talk about the past, present, and future of the company including various milestones such as the Genesis framework and merger with CopyBlogger Media in 2010. We also discuss the community surrounding StudioPress&#8217; products and the role it plays in the company&#8217;s continued success.</p>\n<h2>Picks of the Week:</h2>\n<p><a href="https://wptavern.com/new-toolkit-simplifies-the-process-of-creating-gutenberg-blocks">Ahmad Awais Create Guten Block toolkit</a>.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, January 31st 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #302:</strong> </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 Jan 2018 04:15:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:16;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:38:"WPTavern: WordPress Turns 15 Years Old";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77652";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:49:"https://wptavern.com/wordpress-turns-15-years-old";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1120:"<p><!-- wp:core/paragraph --><br />\nWordPress, the free open source project, <a href="https://ma.tt/2003/01/the-blogging-software-dilemma/">turns 15 years</a> old today. Here is the comment that started it all.<br />\n<!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/image {"id":51095} --></p>\n<img src="https://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/MikeLittleForkB2Comment.png?w=627&ssl=1" alt="Mike Little&#x27;s Comment" />Mike Little&#x27;s Comment\n<p><!-- /wp:core/image --></p>\n<p><!-- wp:core/paragraph --><br />\nIn addition to celebrating 15 years as a successful software project, it&#x27;s also a good opportunity to reflect on the number of people across the world who are making a great living and <a href="http://heropress.com/">turning dreams into reality</a> thanks to the project.<br />\n<!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --><br />\nThank you Matt Mullenweg and Mike Little for creating WordPress, its contributors for keeping the ball rolling all these years, and providing opportunities for so many people. Happy birthday WordPress!<br />\n<!-- /wp:core/paragraph --></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 Jan 2018 03:41:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:17;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"WPTavern: WordCamp Miami Celebrates Its 10th Consecutive Year March 16-18";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77595";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"https://wptavern.com/wordcamp-miami-celebrates-its-10th-consecutive-year-march-16-18";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3689:"<p><!-- wp:core/paragraph --></p>\n<p><a href="https://2018.miami.wordcamp.org/">WordCamp Miami</a> is celebrating its 10th anniversary on March 16-18th. This year&#x27;s event is organized by twelve people and organizers expect more than 800 people to attend. Speakers will arrive from Italy, Germany, London, Brazil, and other international locations to share their knowledge.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>In addition to a <a href="https://2018.miami.wordcamp.org/kids/">two-day Kids Camp</a> with a Kids Panel, WordCamp Miami will feature two new workshops. The first is developer focused and will prepare developers for <a href="https://2018.miami.wordcamp.org/2017/12/19/developer-workshop-announcement-future-of-wordpress/">the future of WordPress</a>. The second is <a href="https://2018.miami.wordcamp.org/2017/12/21/ecommerce-workshop-coming-to-wcmia/">focused on eCommerce</a>.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Attendees will receive their own site and be able to apply what they&#x27;ve learned to it. The sites will have pre-installed plugins and access to various tools mentioned by the workshop teachers.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>The &#x27;Learn JavaScript Deeply&#x27; track is returning this year, featuring local and international JavaScript developers. This is the third time WordCamp Miami has had this track and according to David Bisset, one of the organizers, the focus will be on JavaScript basics, React, plus using JavaScript to create &#x27;cool and unique&#x27; projects with or without WordPress.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Joshua Strebel, Syed Balkhi, and Christie Chirinos will highlight Saturday&#x27;s business track. </p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>For the first time in recent years, WordCamp Miami will have a closing keynote on Saturday, March 17th by John James Jacoby. Jacoby was one of the founders of WordCamp Miami a decade ago, and his talk will cover both nostalgic moments and what the future of WordPress holds for users.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Finally, WordCamp Miami will be doing a &#x27;game show hour&#x27; before the official after party. "We wanted to do something fun and interactive for everyone &#8211; and we think we found a great way to segue people from the talks to unwinding at the after party," Bisset explained. </p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>"We are even planning on having our sponsors form teams in a trivia contest battle. There will be provisions at the party for those who want to network or just relax in a quiet setting."</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Bisset praised volunteers and organizers for helping make 10 years of WordCamp Miami a reality.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>"Each and every one of our organizers and speakers deserve a huge amount of thanks and praise for their hard work." He said. "We couldn&#x27;t have done ten years without the support of the WordPress community."</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Tickets are <a href="https://2018.miami.wordcamp.org/tickets/">on sale</a> with a number of purchasing options. Workshops cost $15 each and general admission tickets are $40 each. General admission tickets provide access to Saturday and Sunday sessions, lunch, swag, and the after party. </p>\n<p><!-- /wp:core/paragraph --></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 25 Jan 2018 01:56:52 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:30:"HeroPress: Believe In Yourself";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2420";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:112:"https://heropress.com/essays/believe-in-yourself/#utm_source=rss&utm_medium=rss&utm_campaign=believe-in-yourself";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10510:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/01/012418-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: Working in WordPress has allowed my curiosity to run wild." /><p>You ever have a moment where you blink your eyes and you wonder how you’ve gotten to where you are today? I’m having one of those moments right now as I sit here to share my story with you. It’s bizarre to think of how far I’ve come because I truly thought that I was not good enough to be where I am today. Let’s get into it.</p>\n<h3>The Beginning</h3>\n<p>As a child, I was always around technology. My dad was a computer scientist and considered it a great idea to get each of his four children their own computer so they would stay away from his. So as the years went by with system administrative tasks being “one of the hard-knocks of life”, I went off to Drexel University in 2005 to pursue a degree in Computer Science. I remember when I walked into my first class and instantly saw how different I was. Everyone was white. Everyone was male. And I was not. In fact, I couldn’t even check off one of those boxes. I was opposite. I was female and I was black.</p>\n<p>The first year pursuing my degree actually went really well and finished off the year, completing my C++ final project to create a matching cards game using objects and classes. All was swell. I found that I was doing just as well as everyone else. And I found that was struggling in certain areas just like everyone else.</p>\n<h3>Leaning In</h3>\n<p>Next semester came and that’s when the more difficult course load began. There was one class in particular called “Data Algorithms &amp; Theories” that was incredibly and frustratingly difficult. As someone who always wanted to do well and is inclined to beat herself up for not being “perfect”, it was an incredibly stressful time for me. But once again, I was not the only one who was struggling because the class was difficult for all of my classmates. But as the class progressed, I decided to step out of my comfort zone and ask for help. This was the first time I would actually utilize the teaching assistant (TA) that was often present during this class. So our scheduled meeting comes around and it doesn’t go as I’d hoped. It wasn’t at all a welcoming atmosphere.</p>\n<blockquote><p>The demeanor of the TA made it clear that he didn’t want to be there but my happy-go-lucky personality brushed it aside.</p></blockquote>\n<p>To make things worse, I wasn’t understanding the “simple” concepts that he was explaining and was subject to the TA’s dismissive glances of judgement and shame. I remember at one point, my mind shifted into trying to make him like me rather than realize that he was discriminating against me. Then he said to me “You know, maybe this just isn’t for you. I’ve explained this to you multiple times and you’re just not getting.” This was a very upsetting moment in my life because someone who was supposed to be helping me learn was telling me that you’re too stupid to learn. Needless to say, I left that session very upset and I ultimately ended up changing my major to something “easier” because apparently it “wasn’t for me”.</p>\n<h3>Accepting A Career</h3>\n<p>After I graduated in 2010 with my degree in Information Technology, I moved to DC to pursue an unfulfilling Systems Engineering career in government contracting. Don’t get me wrong. I learned a plethora of valuable skills that I will use for the rest of my life. But I wasn’t doing something that was enriching me. Not only that, I was often made to feel ostracized in the work culture because of the lack of diversity.</p>\n<blockquote><p>I’m not sure if anyone’s told you&#8230;but it’s extremely hard being a minority and working with people who don’t look like you and who can’t relate to you.</p></blockquote>\n<p>If someone said something racially insensitive or offensive (and there have been multiple instances), that was always a battle I had to fight on my own. And to be honest, sometimes I didn’t fight because I knew no one would give a damn and the person would get away with it with a slap on the wrist.</p>\n<h3>Remembering Joy</h3>\n<p>So in the mist of all of this, no matter how upset, beaten-up and angry I felt after a work day, I could always come back to my love for the metal music genre. I would spend so much time listening to new metal music after work that co-workers nicknamed me “the DJ”. Which isn’t completely untrue. In college, one of my extracurriculars was to host a weekly metal radio show on the college radio station. But I didn’t have that anymore so I essentially felt a bit lost.</p>\n<p>That’s when I decided to get it back! Not in the form of an actual radio show. But in the form of a metal music blog. Outside of having played around with making marque-filled pages on GeoCities and changing the backgrounds of my MySpace and Xanga profiles to be neon-colored or highly pixelated images, I didn’t have any experience making a website. So I GOOGLED it! And in that research I learned how hosting providers work and the best blogging platform for me to use for my blog. And that platform was WordPress. So in 2015, I launched my first website ever on WordPress: metalandcoffee.com. And this point I didn’t really know anything super WordPress-nerdy outside of being able to select a theme and add/organize content on the navigation bar. But I finally had my own voice live and anyone can see it!</p>\n<h3>Looking Deep</h3>\n<p>Now &#8211; the year was 2017 and words cannot describe how miserable I am in my current work position. I thought transferring to a position within the company that brought me back to Philadelphia would help my pain and suffering but it only numbed it for a couple months. I still didn’t like the environment, I didn’t like what I was doing, and although I was able to look at the occasional code snippet that would give me a spark of confidence when I understood what the code was doing, I wasn’t given an opportunity to be on the other side. This is what lit a fire under me to finally do everything in my power to move towards a developer career. I felt like that was where I was supposed to be. Sure, I was told that I wasn’t smart enough to be anywhere near code but why did it excite me to see it and recognize it? Why was I able to troubleshoot errors even though I wasn’t a developer? Why was I excelling at quality assuring software by being able to understand the code’s logic thus thinking of scenarios that were unaccounted for?</p>\n<h3>Breaking Through</h3>\n<p>So I signed up for a couple online courses focused on web development and eventually found myself having been accepted to <a href="http://www.interactivemechanics.com/fellowship">a front-end developer fellowship program</a> that provided me with an amazing mentor and a final project to work towards. For my final project, I chose to learn how to create a custom WordPress theme for my Metal &amp; Coffee website because the current one that I was using did not fully suite my needs.</p>\n<blockquote><p>And there you have it &#8211; throughout the next 9 months, the doubt and shame instilled in me since college kept coming up and I kept having to find ways to break through it whether it’d be a pep talk from my mentor, talking to developers who look like me (black women) or using meditation to help me through the anxiety.</p></blockquote>\n<p>And by the end of that, not only did I finish my final project (<a href="http://metalandcoffee.github.io">http://metalandcoffee.github.io</a>) and come to really love WordPress theming, I got a job offer from Tracy Levesque and Mia Levesque to work at their WordPress web agency, <a href="https://www.yikesinc.com/">Yikes Inc.</a></p>\n<h3>Finding My Place</h3>\n<p>Now, I’m a full-time WordPress developer and I couldn’t be more satisfied. Working at Yikes has sent my developer skills soaring over mountains and valleys. My curiosity is allowed to run wild and I’ve actually been diving into the plugin world, completely re-coding an internal plugin from the ground up and learning essential web programming practices in the process.</p>\n<p>My next goal in the WordPress community is to see more WordPress developers who look like me. And one step I’ve taken towards that goal is to co-teach a Intro to WordPress workshop at Codeland 2018 which I’m very excited (and nervous) for. And I’ll continue to be as visible and outspoken as possible to encourage diversity in this community.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: Believe In Yourself" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Believe%20In%20Yourself&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fbelieve-in-yourself%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Believe In Yourself" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fbelieve-in-yourself%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fbelieve-in-yourself%2F&title=Believe+In+Yourself" rel="nofollow" target="_blank" title="Share: Believe In Yourself"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/believe-in-yourself/&media=https://heropress.com/wp-content/uploads/2018/01/012418-150x150.jpg&description=Believe In Yourself" rel="nofollow" target="_blank" title="Pin: Believe In Yourself"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/believe-in-yourself/" title="Believe In Yourself"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/believe-in-yourself/">Believe In Yourself</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Jan 2018 13:00:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Ebonie Butler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"WPTavern: New Toolkit Simplifies the Process of Creating Gutenberg Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77521";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"https://wptavern.com/new-toolkit-simplifies-the-process-of-creating-gutenberg-blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5470:"<p><!-- wp:core/paragraph --></p>\n<p><a href="https://ahmadawais.com/">Ahmad Awais</a>, who <a href="https://wptavern.com/gutenberg-boilerplate-demonstrates-how-to-build-custom-blocks">created the Gutenberg Boilerplate</a> last year, has <a href="https://ahmadawais.com/create-guten-block-toolkit/">released</a> a <a href="https://github.com/ahmadawais/create-guten-block">Guten Block Toolkit</a>. The toolkit substantially simplifies the creation of Gutenberg Blocks by providing no configuration, one dependency, and no lock-in.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Awais created the toolkit after receiving feedback that configuring things like Webpack, React, ES 6/7/8/Next, ESLint, Babel and keeping up with their development was too difficult.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>"Developers told me that they built Gutenberg blocks with ES5 because the amount of time required to configure, set up, and learn tools like Babel, Webpack, ESLint, Prettier, etc. wasn’t worth it," Awais said.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>"So, yes! I went ahead and built a solution — a zero-config-js #0CJS WordPress developers’ toolkit called create-guten-block!"</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Creating blocks using the toolkit is a three-step process. </p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Developers begin by installing Node version 8 or higher on a local server. The next step is to run the create-guten-block command and provide a name for the plugin that will be created. This command also creates the folder structure necessary to maintain the project. The last step is to run the NPM start command which runs the plugin in development mode.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Once these steps are completed, the WordPress plugin will be compatible with Gutenberg and have React.js, ES 6/7/8/Next, and Babel, which also has ESLint configurations for code editors to detect and use automatically. </p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>The Guten Block Toolkit comes with the following:</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/list --></p>\n<ul>\n<li>React, JSX, and ES6 syntax support. </li>\n<li>Webpack dev/production build process behind the scene. </li>\n<li>Language extras beyond ES6 like the object spread operator. </li>\n<li>Auto-prefixed CSS, so you don’t need -webkit or other prefixes. </li>\n<li>A build script to bundle JS, CSS, and images for production with source-maps. </li>\n<li>Hassle-free updates for the above tools with a single dependency cgb-scripts.</li>\n</ul>\n<p><!-- /wp:core/list --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>The project has received positive feedback, including from members of Gutenberg&#x27;s development team.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/embed {"url":"https://twitter.com/GaryPendergast/status/954559771910193152"} --></p>\n\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Mad props to <a href="https://twitter.com/MrAhmadAwais?ref_src=twsrc%5Etfw">@MrAhmadAwais</a> for making a super useful Gutenberg tool that I''ve been really looking forward to! ?</p>\n<p>I''m excited about the possibilities for this, and I love how it''s embraced WordPress'' "decisions, not options" philosophy, doing all of the hard work for you. ?? <a href="https://t.co/hUAQVDL7S1">https://t.co/hUAQVDL7S1</a></p>\n<p>&mdash; Gary (@GaryPendergast) <a href="https://twitter.com/GaryPendergast/status/954559771910193152?ref_src=twsrc%5Etfw">January 20, 2018</a></p></blockquote>\n<p><br />\n\n<p><!-- /wp:core/embed --></p>\n<p><!-- wp:core/embed {"url":"https://twitter.com/igorbenic/status/955539392273281025"} --></p>\n\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Tried the <a href="https://t.co/WkvhwSVBh6">https://t.co/WkvhwSVBh6</a> from <a href="https://twitter.com/MrAhmadAwais?ref_src=twsrc%5Etfw">@MrAhmadAwais</a>, had a block within a minute. Now it''s time to finish the <a href="https://twitter.com/hashtag/Gutenberg?src=hash&ref_src=twsrc%5Etfw">#Gutenberg</a> course from <a href="https://twitter.com/zgordon?ref_src=twsrc%5Etfw">@zgordon</a> to actually build something useful :D</p>\n<p>&mdash; Igor Benić (@igorbenic) <a href="https://twitter.com/igorbenic/status/955539392273281025?ref_src=twsrc%5Etfw">January 22, 2018</a></p></blockquote>\n<p><br />\n\n<p><!-- /wp:core/embed --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>With a stable release now available to the public, Awais is working on <a href="https://github.com/ahmadawais/create-guten-block/issues/11">2.0.0</a>. "The next step is to get this toolkit tested and mature the entire app to release version 2.0.0 for that not only do I need your <a href="https://ahmadawais.com/contact/">support</a>, I ask that you hop on board and contribute — that’s the only way forward," he said.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Create Guten Block Toolkit is <a href="https://github.com/ahmadawais/create-guten-block/blob/master/LICENSE">MIT licensed</a> and available for free <a href="https://github.com/ahmadawais/create-guten-block">on GitHub</a>. Contributions are welcomed! </p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p><!-- /wp:core/paragraph --></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Jan 2018 03:30:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:20;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:97:"WPTavern: Free Conference Dedicated to WordPress in Higher Ed Takes Place January 30th at 9AM CST";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77514";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:108:"https://wptavern.com/free-conference-dedicated-to-wordpress-in-higher-ed-takes-place-january-30th-at-9am-cst";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1380:"<p>If you&#8217;re interested in learning how WordPress is used in Higher Ed, tune in to <a href="https://online.wpcampus.org/">WPCampus Online</a>, January 30th at 9AM Central Standard Time. WPCampus Online is a virtual conference that people can watch for free, no traveling necessary. The event uses <a href="https://www.crowdcast.io/">Crowdcast</a> allowing viewers to switch between rooms, interact with each other, and ask questions.</p>\n<p>Some of the topics that <a href="https://online.wpcampus.org/schedule/">will be presented</a> include, <a href="https://online.wpcampus.org/schedule/wordpress-and-real-world-data-with-students/">WordPress and Real-World Data with Students</a>, <a href="https://online.wpcampus.org/schedule/headless-brainless-wordpress/">Headless and Brainless WordPress</a>, and <a href="https://online.wpcampus.org/schedule/using-wordpress-support-run-student-government-elections/">Using WordPress to Support and Run Student Government Elections</a>. If in-person conferences are more your style, keep an eye out for information on WPCampus 2018 tentatively planned for this Summer.</p>\n<p>To learn more about WPCampus and the people behind it, <a href="https://wptavern.com/wpweekly-episode-301-wordpress-in-highered-accessibility-and-more-with-rachel-cherry">listen to our interview</a> with Rachel Cherry on episode 301 of WordPress Weekly.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 22 Jan 2018 22:14:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:21;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"Mark Jaquith: How I fixed Yoast SEO sitemaps on a large WordPress site";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:40:"http://markjaquith.wordpress.com/?p=5392";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://markjaquith.wordpress.com/2018/01/22/how-i-fixed-yoast-seo-sitemaps-on-a-large-wordpress-site/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4852:"<p>One of my Covered Web Services clients recently came to me with a problem: <a href="https://yoast.com/wordpress/plugins/seo/">Yoast SEO</a> sitemaps were broken on their largest, highest-traffic WordPress site. Yoast SEO breaks your sitemap up into chunks. On this site, the individual chunks were loading, but the sitemap index (its &#8220;table of contents&#8221;) would not load, and was giving a timeout error. This prevented search engines from finding the individual sitemap chunks.</p>\n<p>Sitemaps are really helpful for providing information to search engines about the content on your site, so fixing this issue was a high priority to the client! They were frustrated, and confused, because this was working just fine on their other sites.</p>\n<p>Given that this site has over a decade of content, I figured that Yoast SEO&#8217;s dynamic generation of the sitemap was simply taking too long, and the server was giving up.</p>\n<p>So I increased the site&#8217;s various timeout settings to 120 seconds.</p>\n<p><strong>No good.</strong></p>\n<p>I increased the timeout settings to 300 seconds. Five whole minutes!</p>\n<p><strong>Still no good.</strong></p>\n<p>This illustrates one of the problems that WordPress sites can face when they accumulate a lot of content: <strong>dynamic processes start to take longer</strong>. A process that takes a reasonable 5 seconds with 5,000 posts might take 100 seconds with 500,000 posts. I could have eventually made the Yoast SEO sitemap index work if I increased the timeout high enough, but that wouldn&#8217;t have been a good solution.</p>\n<ol>\n<li>It would have meant increasing the timeout settings irresponsibly high, leaving the server potentially open to abuse.</li>\n<li>Even though it is search engines, not people, who are requesting the sitemap, it is unreasonable to expect them to wait over 5 minutes for it to load. They&#8217;re likely to give up. They might even penalize the site in their rankings for being slow.</li>\n</ol>\n<p>I needed the sitemap to be reliably generated without making the search engines wait.</p>\n<p><strong>When something intensive needs to happen reliably on a site, look to the command line.</strong></p>\n<h2>The Solution</h2>\n<p>Yoast SEO doesn&#8217;t have <a href="http://wp-cli.org/">WP-CLI</a> (WordPress command line interface) commands, but that doesn&#8217;t matter — you can just use <a href="https://developer.wordpress.org/cli/commands/eval/"><b>wp eval</b></a> to run arbitrary WordPress PHP code.</p>\n<p>After a little digging through the <a href="https://github.com/Yoast/wordpress-seo/blob/46802dbcf8e7d2ac0d6552f4de0923cd0eba2b07/inc/sitemaps/class-sitemaps.php#L345-L364">Yoast SEO code</a>, I determined that this WP-CLI command would output the index sitemap:</p>\n<pre class="brush: bash; title: ; notranslate">wp eval ''\n$sm = new WPSEO_Sitemaps;\n$sm-&gt;build_root_map();\n$sm-&gt;output();\n''</pre>\n<p>That took a good while to run on the command line, but that doesn&#8217;t matter, because I just set a <a href="https://help.ubuntu.com/community/CronHowto">cron job</a> to run it once a day and save its output to a static file.</p>\n<pre class="brush: plain; title: ; notranslate">0 3 * * * cd /srv/www/example.com &amp;&amp; /usr/local/bin/wp eval ''$sm = new WPSEO_Sitemaps;$sm-&gt;build_root_map();$sm-&gt;output();'' &gt; /srv/www/example.com/wp-content/uploads/sitemap_index.xml</pre>\n<p>The final step that was needed was to modify a rewrite in the site&#8217;s Nginx config that would make the <b>/sitemap_index.xml</b> path point to the cron-created static file, instead of resolving to Yoast SEO&#8217;s dynamic generation URL.</p>\n<pre class="brush: plain; highlight: [4]; title: ; notranslate">location ~ ([^/]*)sitemap(.*).x(m|s)l$ {\n    rewrite ^/sitemap.xml$ /sitemap_index.xml permanent;\n    rewrite ^/([a-z]+)?-?sitemap.xsl$ /index.php?xsl=$1 last;\n    rewrite ^/sitemap_index.xml$ /wp-content/uploads/sitemap_index.xml last;\n    rewrite ^/([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&amp;sitemap_n=$2 last;\n}</pre>\n<p>Now the sitemap index loads instantly (because it&#8217;s a static file), and is kept up-to-date with a reliable background process. The client is happy that they didn&#8217;t have to switch SEO plugins or install a separate sitemap plugin. Everything just works, thanks to a little bit of command line magic.</p>\n<p>What other WordPress processes would benefit from this kind of approach?</p>\n<hr />\n<p><b>Do you need <a href="https://coveredwebservices.com/">WordPress services?</a></b></p>\n<p>Mark runs <a href="https://coveredwebservices.com/">Covered Web Services</a> which specializes in custom WordPress solutions with focuses on security, speed optimization, plugin development and customization, and complex migrations.</p>\n<p>Please reach out to start a conversation!</p>\n[contact-form]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 22 Jan 2018 15:15:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Mark Jaquith";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:22;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:66:"Post Status: Hosted versus self-hosted eCommerce — Draft podcast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=41084";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"https://poststatus.com/hosted-versus-self-hosted-ecommerce-draft-podcast/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2130:"<p>Welcome to the Post Status <a href="https://poststatus.com/category/draft">Draft podcast</a>, which you can find <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">on iTunes</a>, <a href="https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast">Google Play</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, and <a href="http://simplecast.fm/podcasts/1061/rss">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.</p>\n<p>In this episode, Brian and Brian discuss self-hosted vs managed ecommerce and whether or not conferences have outlived their usefulness. Specifically, they look at WooCommerce vs other solutions and explore Shopify and Liquid Web’s Managed WooCommerce hosting as viable done-for-you strategies. On the conference front, they talk about the good and the bad of conferences and ponder how tech conferences of the future may need to change to attract more attendees.</p>\n<p></p>\n<h3>Links</h3>\n<ul>\n<li><a href="https://marco.org/2018/01/17/end-of-conference-era">The End of the Conference Era</a></li>\n<li><a href="https://www.liquidweb.com/blog/liquid-web-announces-the-launch-of-managed-woocommerce-hosting/">Liquid Web introduces Managed WooCommerce</a></li>\n<li><a href="https://github.com/liquidweb/woocommerce-order-tables">Liquid Web&#8217;s WooCommerce Order Tables Plugin</a></li>\n<li><a href="https://metorik.com/">Metorik</a></li>\n<li><a href="https://www.ecommercefuel.com/">eCommerceFuel</a></li>\n</ul>\n<h3>Sponsor: Pippin&#8217;s Plugins</h3>\n<p>This episode is sponsored by Pippin’s Plugins. <a href="http://pippinsplugins.com/">Pippin’s Plugins</a> creates a suite of plugins that work great alone, or together. Whether you need to restrict content, sell downloads, or start an affiliate program, they’ve got you covered. For more information, check out their <a href="http://pippinsplugins.com/">website</a> and thank you to Pippin’s Plugins for being a Post Status partner.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 19 Jan 2018 20:56:40 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Katie Richards";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"Matt: R.I.P Dean";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=47840";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:33:"https://ma.tt/2018/01/r-i-p-dean/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3493:"<p>Dean Allen, a web pioneer and good man, has passed away. I&#x27;ve been processing the news for a few days and still don&#x27;t know where to begin. Dean was a writer, who wrote the software he wrote on. His websites were crafted, designed, and typeset so well you would have visited them even if they were filled with Lorem Ipsum, and paired with his writing you were drawn into an impossibly rich world. His blog was called Textism, and among many other things it introduced me to the art of typography.</p>\n\n\n\n<p>Later, he created Textpattern, without which WordPress wouldn&#x27;t exist. Later, he created Textdrive with Jason Hoffman, without which WordPress wouldn&#x27;t have found an early business model or had a home on the web. He brought a care and craft to everything he touched that inspires me to this day. As <a href="https://daringfireball.net/2018/01/dean_allen">John Gruber said</a>, "Dean strove for perfection and often achieved it." (Aside: Making typography better on the web led John Gruber to release Smarty Pants, Dean a tool called Textile, and myself something called Texturize all within a few months of each other; John continued his work and created Markdown, I put Texturize into WP, and Dean released Textile in Textpattern.)</p>\n\n\n\n<p>Years later, we became friends and shared many trips, walks, drinks, and meals together, often with Hanni and <a href="https://om.co/2018/01/18/dean-allen-rest-in-peace/">Om</a>. (When we overlapped in Vancouver he immediately texted "I&#x27;ll show you some butt-kicking food and drink.") His zest for life was matched with an encyclopedic knowledge of culture and voracious reading (and later podcast listening) habits. I learned so much in our time together, a web inspiration who turned for me into a real-life mensch. He was endlessly generous with his time and counsel in design, prose, and fashion. I learned the impossibly clever sentences he wrote, that you assumed were the product of a small writing crew or at least a few revisions, came annoyingly easily to him, an extension of how he actually thought and wrote and the culmination of a lifetime of telling stories and connecting to the human psyche.</p>\n\n\n\n<p>Dean, who (of course) was also a great photographer, didn&#x27;t love having his own photo taken but would occasionally tolerate me when I pointed a camera at him <a href="https://om.co/2018/01/18/dean-allen-rest-in-peace/">and Om has a number of the photos on his post</a>. There&#x27;s one that haunts me: before getting BBQ we were at his friend&#x27;s apartment in Vancouver, listening to Mingus and enjoying hand-crafted old fashioneds with <a href="https://ma.tt/files/2018/01/IMG_7147.jpg">antique bitters</a>, and despite the rain we went on the roof to see the art that was visible from there. He obliged to a photo this time though and we took photos of each other individually in front of a sign that said "EVERYTHING IS GOING TO BE ALRIGHT." It wasn&#x27;t, but it&#x27;s what I imagine Dean would say right now if he could.</p>\n\n\n\n<div class="wp-block-gallery alignnone columns-2 is-cropped">\n    <img src="https://i2.wp.com/ma.tt/files/2018/01/IMG_7151.jpg?w=604&ssl=1" />\n    <img src="https://i0.wp.com/ma.tt/files/2018/01/IMG_7158.jpg?w=604&ssl=1" />\n</div>\n\n\n\n<img src="https://i1.wp.com/ma.tt/files/2018/01/104050690_ce98a95092_o.jpg?w=604&ssl=1" />\n    When we first met, in 2006, <a href="https://www.flickr.com/photos/textdriveinc/104050690/in/photostream/">from Jason</a>.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 19 Jan 2018 05:21:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:24;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:100:"WPTavern: WPWeekly Episode 301 – WordPress in HigherEd, Accessibility, and More With Rachel Cherry";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=77497&preview=true&preview_id=77497";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:105:"https://wptavern.com/wpweekly-episode-301-wordpress-in-highered-accessibility-and-more-with-rachel-cherry";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2840:"<p>In this episode, <a href="http://jjj.me">John James Jacoby</a> and I are joined by <a href="https://bamadesigner.com/">Rachel Cherry</a>, Senior Software Engineer for <a href="http://www.disneyinteractive.com/">Disney Interactive</a> and Director of <a href="https://wpcampus.org/">WPCampus</a>. Cherry describes how she got involved with WordPress, its use in higher education, the inspiration behind WPCampus, and her thoughts on accessibility both in WordPress and across the web. She also assigned everyone the following homework assignment.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Per my interview on <a href="https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw">#WordPress</a> Weekly, I’ve assigned everyone <a href="https://twitter.com/hashtag/accessibility?src=hash&ref_src=twsrc%5Etfw">#accessibility</a> homework: open your website and navigate using ONLY THE KEYBOARD. Can you access all content and functionality? Can you open AND close popups? Let me know what you learned.</p>\n<p>&mdash; Rachel Cherry (@bamadesigner) <a href="https://twitter.com/bamadesigner/status/953742847831818240?ref_src=twsrc%5Etfw">January 17, 2018</a></p></blockquote>\n<p></p>\n<p>If you want to learn how WordPress is being used in higher education, tune in to<a href="https://online.wpcampus.org/"> WPCampus Online</a> Tuesday, January 30, 2018. Viewers will be able to watch sessions and interact with the speakers for free. Near the end of the show, Jacoby provides a review of the Nintendo Switch he received for Christmas.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://make.wordpress.org/core/2018/01/12/whats-new-in-gutenberg-12th-january/">Gutenberg 2.0 Released</a><br />\n<a href="https://wptavern.com/wordpress-4-9-2-patches-xss-vulnerability">WordPress 4.9.2 Patches XSS Vulnerability</a><br />\n<a href="https://wptavern.com/zac-gordon-launches-gutenberg-development-course-includes-more-than-30-videos">Zac Gordon Launches Gutenberg Development Course, Includes More Than 30 Videos</a></p>\n<h2>Picks of the Week:</h2>\n<p><a href="https://pippinsplugins.com/2017-in-review/">Pippin Williamson&#8217;s 2017 Year in Review</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, January 24th 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #301:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 18 Jan 2018 02:42:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:25;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:62:"WPTavern: DesktopServer 3.8.4 Includes A Gift to the Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77259";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"https://wptavern.com/desktopserver-3-8-4-includes-a-gift-to-the-community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2802:"<p><!-- wp:core/paragraph --></p>\n<p>DesktopServer <a href="https://serverpress.com/announcing-desktopserver-v3-8-4/">has released</a> version 3.8.4 of its local development software. This version includes a lot of refactored code, setting the foundation for faster updates in the future along with design-time plugins.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>One of the major changes in 3.8.4 is the use of the .dev.cc top level domain.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/quote --></p>\n<blockquote class="wp-block-quote">\n<p>Due to the latest changes with the .dev Top Level Domain and the fact that many browsers now force SSL on anything with the .dev extension, DesktopServer will now use .dev.cc as its TLD extension. This is a legitimate top level domain owned by ServerPress, LLC and will ONLY be used for local development purposes.</p>\n<p><cite><a href="https://serverpress.com/announcing-desktopserver-v3-8-4/">Release Announcement Post</a></cite></p></blockquote>\n<p><!-- /wp:core/quote --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Marc Benzakein says the domain will work no matter which local development solution is being used and that it&#x27;s a gift to the community. Other domains such as .test will continue to work as expected. </p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>Other improvements include speed optimizations for Windows installs, a Windows compatibility plugin to fix long filename problems when updating from third-party plugin repositories such as Easy Digital Downloads, and a WordPress 4.9.1 Blueprint.</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>If you use an Apple device with a Retina screen or Hi-DPI in Windows, you&#x27;ll likely appreciate the user-interface changes that are vastly improved on high resolution screens. Josh Eby does!</p>\n<p><!-- /wp:core/paragraph --></p>\n<p><!-- wp:core/embed {"url":"https://twitter.com/josheby/status/953089139439751168"} --></p>\n\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Love the new scaling fix on <a href="https://twitter.com/DesktopServer?ref_src=twsrc%5Etfw">@DesktopServer</a> 3.8.4!  Looks great on my 4K display now. Can''t wait for 3.9 to get released!</p>\n<p>&mdash; Josh Eby (@josheby) <a href="https://twitter.com/josheby/status/953089139439751168?ref_src=twsrc%5Etfw">January 16, 2018</a></p></blockquote>\n<p><br />\n\n<p><!-- /wp:core/embed --></p>\n<p><!-- wp:core/paragraph --></p>\n<p>DesktopServer 3.8.4 also includes a number of enhancements for premium service customers. To view these and other notes related to the release, check out <a href="https://serverpress.com/announcing-desktopserver-v3-8-4/">the announcement post</a>. </p>\n<p><!-- /wp:core/paragraph --></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 17 Jan 2018 19:12:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:26;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:51:"WPTavern: WordPress 4.9.2 Patches XSS Vulnerability";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77438";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:62:"https://wptavern.com/wordpress-4-9-2-patches-xss-vulnerability";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1106:"<p>WordPress 4.9.2 has been released and patches a cross-site scripting vulnerability in the Flash fallback files in the MediaElement library. <a href="https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/">According to Ian Dunn</a>, the Flash files are rarely needed and have been removed from WordPress.</p>\n\n\n\n<p>If you need access to the Flash fallback files, they can be obtained using the <a href="https://wordpress.org/plugins/mediaelement-flash-fallbacks/">MediaElement Flash Fallback</a> plugin. <a href="https://opnsec.com">Enguerran Gillier</a> and <a href="https://widiz.com/">Widiz</a> are credited with responsibly disclosing the vulnerability. ﻿</p>\n\n\n\n<p>In addition to the patch, this releases fixes 21 bugs. JavaScript errors that prevented saving posts in Firefox has been fixed and switching themes will attempt to restore previous widget assignments, even if no sidebars exist.</p>\n\n\n\n<p>You can view detailed information about the changes in 4.9.2 by <a href="https://codex.wordpress.org/Version_4.9.2">reading the following Codex article</a>. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 17 Jan 2018 09:19:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:27;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:37:"HeroPress: Growing WordPress in India";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2406";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:120:"https://heropress.com/essays/growing-wordpress-india/#utm_source=rss&utm_medium=rss&utm_campaign=growing-wordpress-india";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:18306:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/01/011718-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: The world will know you for the path you have chosen." /><h3>Preface</h3>\n<p>I was one of the first batch of participants in the initial version of HeroPress, which was video stories but I backed out due to multiple reasons. But, I’m glad HeroPress has survived in this current avatar, telling some really interesting stories of some real wonderful people. Few of whom I’ve had the pleasure of calling friends.</p>\n<p><a href="https://heropress.com/about/">Topher</a> has umpteen number of times asked me to write my HeroPress story and I have always either given excuses or deadlines that I never planned on meeting. The few times that I did start writing this article I went into too much of a deep dive into my life story (that I never finished it&#8230;) which is quite the rollercoaster from having failed Std.10th (high School) in English or dropping out in College to having guest lectured(teaching WordPress, of course) in one of the biggest B-schools in India OR my work experience which includes Film, TV, dealing cards to even working as an assistant to the Union Minister of India for Youth Affairs and sports… There I go again!! While that does make for a good story I should save it for when you buy me a beer.</p>\n<p>I wanted my HeroPress article to tell a story of how our WordPress Community is truly open source and always open for everyone’s participation. I think this version does the Job. Also would like to thank <a href="https://profiles.wordpress.org/andreamiddleton">Andrea Middleton </a>and <a href="https://twitter.com/adityakane?lang=en">Aditya Kane</a> who have been the most supportive of my efforts all these years. Last but not the least I’d like to thank Topher for this great space he has created and being a true friend with whom I could share some of my troubles.</p>\n<p>I am <a href="https://twitter.com/gounder?lang=en">Alexander Gounder</a>, somewhat of a nobody who become somebody not only because I tried but also because WordPress is open enough to allow it and this is my story!</p>\n<h3>Background</h3>\n<p>I was born in a lower middle class household in Mumbai, India. I am the middle kid among three siblings. My Father works as a tailor in Saudi Arabia and visits every few years. My Mother is a strong willed woman, who would fight the world for her kids which was evident when she refused to listen to doctors that my sister who suffers from Cerebral Palsy be sent to Special school and instead went pillar to post to get her to study in her normal school, even if it meant that she had to wait outside class during school hours (in case my sister had to go to the restroom) or carry my sister (who then was about 8 yrs old) around.</p>\n<blockquote><p>I live where 70%, if not more, of Mumbai’s population lives, the slum or <a href="https://en.wikipedia.org/wiki/Chawl">chawls</a> in the suburbs.</p></blockquote>\n<p>So I’ve lived through the hunger for a day when I lost <u title="15 cents USD">Rs.10</u> on my way to buy bread, this was during the Gulf war when my father couldn’t send us any money for months; I’ve lived through the darkness of when there are frequent power cuts and still the power companies claim that there isn’t any load shedding in this city; I’ve lived through the annual ritual of walking in knee deep water to school, then college and now work as Monsoon water, thanks to clogged drains finds its way to the empty plot between our chawl and the main road.</p>\n<p>In terms of education I was an above average student but somehow managed to fail my Std. 10 board exams (this is a very important milestones in the Indian education system). Failure has been my stepping stone to success. I learnt computers as I had free time because I had to wait six months for joining college. I got a job at a local cyber cafe which was run by a linux enthusiast, this was my introduction to Free and Open Source. Post that I attended college (but didn’t graduate) and had many jobs (I’ve been working since I was 17, almost 50% of my lifetime).</p>\n<p>To conclude, the point I’m trying to make here is, I don’t come from a lot of money or have a lot in terms of education qualifications in spite of which I was able to do everything I did in the WordPress Community here in Mumbai and India at large.</p>\n<h3>My first WordCamp</h3>\n<p>I was an attendee at the first WordCamp in Mumbai in 2012. I was pretty excited about attending it, because only a few days before I saw a video from WordCamp San Francisco. I thought the idea of having a conference about WordPress was super cool. Though the tickets seemed a little expensive, I had just started freelancing and wasn’t attending events yet, so didn’t really have any benchmarks and thought it was worth it as this was an International/official event.</p>\n<p>My excitement was short lived when talks were sponsor pitches or mostly not about WordPress. The arrangements too weren’t as expected. During a session that was delayed by over 45 mins because the speaker and his connectivity problems (which could have been resolved by just using another machine), I lost my cool and walked out, one of the volunteers struck a conversation with me where I began by complaining about the arrangements and wanted to speak with the organizers to complain, but anger turned to sympathy when I realized that these student volunteers were in fact the event organizers, with that fact in mind even putting together this event was a great achievement. I probed further trying to understand where things were going wrong, checked what they paid for the t-shirts, it was about 30-40% higher than market price, asked if everyone paid the sponsor amount listed on the site, they said &#8211; many had bargained for upto 50% less than the published sponsor slab and some agreed with speaker slots thrown in. I asked how many tickets they sold and was informed free tickets were distributed in their colleges and to some of their partners. Partners? These were a few individuals who in the guise of helping these kids organize WordCamp had brokered deals that got sponsors discounts and/or speaker slots, free tickets (over 50) for friends / colleagues / employees, speaker slots for themselves and even their companies or brands as in kind sponsors.</p>\n<p>On the second day, things went to a confrontational stage with many (who paid to attend the event) questioning the Non-WordPress talks and long twitter threads ensued. While it is easy to blame the organizers of the WC Mumbai 2012, I think it was those few selfish individuals who weren’t part of the organizing team but tried to influence them while offering to help.</p>\n<p>This showed there was a need for the Indian WordPress Community to come together so we started a small buddypress website which was inundated with spam registrations hence replaced it with a <a href="https://www.facebook.com/groups/JaiWP/">FB group</a>.</p>\n<p>This WordPress India FB group helped us co-ordinate our first meetup in Jan 2013.</p>\n<h3>Visiting Other WordCamps</h3>\n<p>While talking to others about bringing WordPress enthusiasts from all over India, I got a sense there&#8217;s mostly mistrust among people involved in WordCamps and those attending or speaking at it. That&#8217;s when something I read on plan.wordcamp.org struck me, it said that sponsoring a WordCamp is a great way to contribute and give back. So I sponsored the next WordCamp in India, WC Baroda. When asked what is the sponsoring brand, I named our BuddyPress website. Little did I realise that this helped others see I was genuinely interested in bringing people together than make a quick buck or get publicity for myself.</p>\n<p>While the next few WordCamps were better than my experience at WC Mumbai 2012, but they shared some common threads, in terms of the people who spoke there, or how there was no clarity in terms of how speakers were selected. I had even applied to speak at a WordCamp through FB chat, because that&#8217;s how the organiser was handling it. To my disappointment I sat through a session at that WordCamp with someone from automattic presenting exactly what I had proposed, later to be told by the speaker that he didn&#8217;t intend to speak and this was a topic proposed by the organisers.</p>\n<blockquote><p>I was disgusted by how these WordCamps were filled with shady underhand deals and zero transparency. While WordCamps had some set of guidelines and expectations, these organizers knowingly or unknowingly followed none of them.</p></blockquote>\n<p>At that point of time, the idea of organising a WordCamp in Mumbai came to mind too, but then what if I would end up doing the same as what was already happening was the only thing that stopped me from applying for a WordCamp.</p>\n<h3>Moment of truth</h3>\n<p>WordPress turned 10, and there were meetups organised everywhere and with a little confusion we too managed to organise a meet-up at a coffee shop, here the attendees weren&#8217;t people who we normally meet at WordCamps but regular WordPress users who discovered the meetup through WordPress.org. They had some amazing stories to tell about their association with the software &#8211; I met Manish who 80k downloads for his theme on WordPress.org or Sachin who had been blogging since ‘98 even before WordPress.</p>\n<p>So I realised the Meetups and WordCamps weren&#8217;t really reaching most WordPress users within our own neighborhood, these users were equally passionate about WordPress and they too wanted to have real world meetups to meet others like them.</p>\n<h3>Then how did we do it</h3>\n<h4>We not I</h4>\n<p>While “I” claim to have broken WordCamps in India, I couldn’t have done it alone. Right from the beginning I started asking other to join and help out, because we were at the end of the day trying to build a community and that couldn’t be done alone. At first it was Aditya, then we had other regular members like Sahil and Vachan join in to help us organize regular meetups.</p>\n<p>Getting more stock holders allowed us to bring a different perspective to everything that we were doing. Till then people blocked others from participating as organizers or volunteers because of their own insecurities and used the line that “meetups don’t work in India”. Maybe even peddling that lie to even WordPress Foundation which was then allowing these WordCamps in the hope they would kickstart local. We went the opposite way.</p>\n<h4>Persevere</h4>\n<p>When we started off with meetups we were told “Meetups don’t work in India”, but this wasn’t true because I was already attending Startup Saturday, a monthly Meetup for startups, Quora had a meetup, Many Bloggers had meetups. So we got started. A few meetups had 10-20 people showing up while others had 2-3 but we didn’t give up on meetups because we were meeting new people which was our end goal. Aditya once remarked that even if he met one new person and discussed WordPress that would be a successful, and has resulted in us having a fairly active meetup with so many different people speaking and attending it.</p>\n<h4>Put a little thought</h4>\n<p>I became very close friends with Aditya and we spent a lot of time discussing what we were doing here. We were a good cop / bad cop team many times. From our discussion we set up some guidelines for what we stood for inclusiveness and transparency. This was before we had a WordCamp Handbook which guides you through most of the challenges you would face.</p>\n<p>We were the first WordCamp in India to publish the code of conduct and make sure it was accessible to everyone, we made repeated announcements on the run-up to the WordCamp and during the WordCamp about this Code of Conduct and how serious we were about following it. We even discussed thing amongst ourselves about handling any complaints about violations of the code of conduct, for e.g. as per Indian law you can’t disclose the identity of a person who is victim of Sexual Harassment and therefore we took care and had a system in place to take complaints and maintain the complainants privacy.</p>\n<p>When we did our first WordCamp we tried to have ticket cost as low as possible (<u title="">INR 300</u> or pay more if you’d like) to allow anyone to afford it. ( Fun fact &#8211; WC Mumbai to date has the lowest Avg. ticket price per day among WordCamps in India ).</p>\n<blockquote><p>At the first WordCamp Mumbai (2014) organized by our meetup group, I had someone come to me and tell me that he was glad to have attended and missed the last Mumbai WordCamp because the tickets were too expensive and his parents wouldn’t give him that kind of money.</p></blockquote>\n<p>This reinforced my view of never making WordCamp tickets too expensive, in fact we picked up what WC Pune 2015 did and started offering Student Discounts among other discounts to aid inclusivity.</p>\n<p>During the WordCamp preparation time all vendor information, speaker selection and accounts data was available to all organizers, post WordCamp Mumbai 2014, we published this account on our WordCamp website for everyone to review.</p>\n<h4>Focus on Basics</h4>\n<p>We want to build a community that shared information and talked about WordPress, So we focused on the basics that included having regular meetups. Even our first WordCamp was very low key in terms of the menu or swag at the event or international speakers or host of sponsors… the things that other used to say if they organized a successful WordCamp. We focused instead on getting good speakers, affordable tickets, reaching out and spreading the message about our WordCamp. Putting in a Processes / Guidelines for speakers selection and so on. We wanted to get the WordCamp right rather than find something that we could brag about, we knew if we delivered on the first we could then brag all we want. Some simple ideas helped us cut cost as we didn’t really have many sponsors For e.g. we had packed lunch packets which bought catering cost to <u title="$2.36">INR 150/day</u> from INR 350 &#8211; 450/day if we would have a simple buffet spread. We did mugs instead of tshirts because the quality ones costed us INR 80 instead of INR 150 for decent quality t-shirts.</p>\n<h4>Keeping it open</h4>\n<p>We didn’t discriminate amongst attendees or treat someone as more important than others, everyone from the organizing team was approachable and we wanted to help. The meetups too became a welcoming space, we tried to keep a check on behaviour that could harmful or make the space unwelcoming to other. We didn’t shy away from calling out sexist behaviour. We didn’t discriminate amongst people who wanted to volunteer, we have freelancers and students in our team and they are as important as someone who owns an IT firm employing several people.</p>\n<h4>What the future holds for us</h4>\n<p>Even before WordCamp Central had a rule for allowing a person to be lead organizer only for two consecutive years we had started on planning of grooming the next set of leaders so that, if we decide to become a little inactive meetups and WordCamps would continue as usual.</p>\n<p>WordCamp Mumbai in a gist:</p>\n<p>As a result of the above I can proudly say that WordCamp Mumbai is oldest actively running WordCamp/meetup group in India having had twice as many WordCamps than any other city.</p>\n<p>I would like to leave you with this song which everyone here at our meetup group can Identify with.</p>\n<div class="jetpack-video-wrapper"></div>\n<p>हमारी ही मुठ्ठी में आकाश सारा (Humari hi mutthi mein akash sara)<br />\nजब भी खुलेगी चमकेगा तारा (Jab bhi khulenga chamkenga tara)<br />\nकभी ना ढले जो, वो ही सितारा (Kabhi na dale jo, woh hi sitara)<br />\nदिशा जिस से पहचाने संसार सारा (Disha jis se pehchane sansaar sara)</p>\n<p>These lyrics roughly translate to</p>\n<p>We have the skies in our fist. Whenever it opens, a star will shine.</p>\n<p>One that never sets will be a Superstar and the world will know you for the path you have chosen.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: Growing WordPress in India" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Growing%20WordPress%20in%20India&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fgrowing-wordpress-india%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Growing WordPress in India" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fgrowing-wordpress-india%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fgrowing-wordpress-india%2F&title=Growing+WordPress+in+India" rel="nofollow" target="_blank" title="Share: Growing WordPress in India"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/growing-wordpress-india/&media=https://heropress.com/wp-content/uploads/2018/01/011718-150x150.jpg&description=Growing WordPress in India" rel="nofollow" target="_blank" title="Pin: Growing WordPress in India"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/growing-wordpress-india/" title="Growing WordPress in India"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/growing-wordpress-india/">Growing WordPress in India</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 17 Jan 2018 02:30:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Alexander Gounder";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:28;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:58:"Dev Blog: WordPress 4.9.2 Security and Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5376";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3953:"<p>WordPress 4.9.2 is now available. This is a <strong>security and maintenance release</strong> for all versions since WordPress 3.7﻿. We strongly encourage you to update your sites immediately.</p>\n\n\n\n<p>An XSS vulnerability was discovered in the Flash fallback files in MediaElement, a library that is included with WordPress. Because the Flash files are no longer needed for most use cases, they have been removed from WordPress.</p>\n\n\n\n<p>MediaElement has released a new version that contains a fix for the bug, and <a href="https://wordpress.org/plugins/mediaelement-flash-fallbacks/">a WordPress plugin containing the fixed files</a> is available in the plugin repository.</p>\n\n\n\n<p>Thank you to the reporters of this issue for practicing <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/">responsible security disclosure</a>: <a href="https://opnsec.com">Enguerran Gillier</a> and <a href="https://widiz.com/">Widiz﻿</a>.</p>\n\n\n\n<p>21 other bugs were fixed in WordPress 4.9.2. Particularly of note were:</p>\n\n\n\n<ul>\n    <li>JavaScript errors that prevented saving posts in Firefox have been fixed.</li>\n    <li>The previous taxonomy-agnostic behavior of <code>get_category_link()</code> and <code>category_description()</code> was restored.</li>\n    <li>Switching themes will now attempt to restore previous widget assignments, even when there are no sidebars to map.<br /></li>\n</ul>\n\n\n\n<p>The Codex has <a href="https://codex.wordpress.org/Version_4.9.2">more information about all of the issues fixed in 4.9.2</a>, if you&#x27;d like to learn more.</p>\n\n\n\n<p>﻿<a href="https://wordpress.org/download/"></a><a href="https://wordpress.org/download/">Download WordPress 4.9.2</a> or venture over to Dashboard → Updates and click "Update Now." Sites that support automatic background updates are already beginning to update automatically.</p>\n\n\n\n<p>Thank you to everyone who contributed to WordPress 4.9.2:</p>\n\n\n\n<p><a href="https://profiles.wordpress.org/0x6f0/">0x6f0</a>, <a href="https://profiles.wordpress.org/jorbin/">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/afercia/">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/aduth/">Andrew Duthie</a>, <a href="https://profiles.wordpress.org/azaozz/">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/blobfolio/">Blobfolio</a>, <a href="https://profiles.wordpress.org/boonebgorges/">Boone Gorges</a>, <a href="https://profiles.wordpress.org/icaleb/">Caleb Burks</a>, <a href="https://profiles.wordpress.org/poena/">Carolina Nymark</a>, <a href="https://profiles.wordpress.org/chasewg/">chasewg</a>, <a href="https://profiles.wordpress.org/chetan200891/">Chetan Prajapati</a>, <a href="https://profiles.wordpress.org/dd32/">Dion Hulse</a>, <a href="https://profiles.wordpress.org/hardik-amipara/">Hardik Amipara</a>, <a href="https://profiles.wordpress.org/ionvv/">ionvv</a>, <a href="https://profiles.wordpress.org/jaswrks/">Jason Caldwell</a>, <a href="https://profiles.wordpress.org/jbpaul17/">Jeffrey Paul</a>, <a href="https://profiles.wordpress.org/jeremyfelt/">Jeremy Felt</a>, <a href="https://profiles.wordpress.org/joemcgill/">Joe McGill</a>, <a href="https://profiles.wordpress.org/johnschulz/">johnschulz</a>, <a href="https://profiles.wordpress.org/juiiee8487/">Juhi Patel</a>, <a href="https://profiles.wordpress.org/obenland/">Konstantin Obenland</a>, <a href="https://profiles.wordpress.org/markjaquith/">Mark Jaquith</a>, <a href="https://profiles.wordpress.org/rabmalin/">Nilambar Sharma</a>, <a href="https://profiles.wordpress.org/peterwilsoncc/">Peter Wilson</a>, <a href="https://profiles.wordpress.org/rachelbaker/">Rachel Baker</a>, <a href="https://profiles.wordpress.org/rinkuyadav999/">Rinku Y</a>, <a href="https://profiles.wordpress.org/sergeybiryukov/">Sergey Biryukov</a>, and <a href="https://profiles.wordpress.org/westonruter/">Weston Ruter</a>.﻿<strong></strong><br /></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 16 Jan 2018 23:00:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Ian Dunn";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:29;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:61:"Post Status: Two Brians are better than one — Draft podcast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=41041";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"https://poststatus.com/two-brians-better-one-draft-podcast/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2210:"<p>Welcome to the Post Status <a href="https://poststatus.com/category/draft">Draft podcast</a>, which you can find <a href="https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008">on iTunes</a>, <a href="https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast">Google Play</a>, <a href="http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast">Stitcher</a>, and <a href="http://simplecast.fm/podcasts/1061/rss">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and his new co-host, Brian Richards.</p>\n<p>Brian Richards, the creator of <a href="https://wpsessions.com/">WPSessions.com</a>, has been developing with WordPress since 2007 and training and leading development teams since 2011. In addition to investing his time into training, Brian has had the opportunity to work with many amazing WordPress agencies and experts over these last several years. This has allowed him to help develop sites for Microsoft, Disney, TIME, YMCA, and numerous others.</p>\n<p>Brian has an affinity for self-directed learning and helping others to develop skills and workflows to better solve important and complicated problems. He can’t resist helping good people do great things!</p>\n<p></p>\n<p>&nbsp;</p>\n<h3>Links</h3>\n<ul>\n<li><a href="https://wpsessions.com/">WPSessions.com</a></li>\n<li><a href="https://crowdfavorite.com/">Crowd Favorite</a></li>\n<li><a href="https://webdevstudios.com/">WebDevStudios</a></li>\n<li><a href="http://rzen.net/">Ramblings from a nobody</a></li>\n<li><a href="https://twitter.com/rzen">Brian Richards on Twitter</a></li>\n<li><a href="https://twitter.com/wpsessions">WPSessions on Twitter</a></li>\n</ul>\n<h3>Sponsor: Valet</h3>\n<p>This episode is sponsored by <a href="https://www.valet.io/">Valet</a>. Valet helps keep your clients happy &amp; coming back. They offer expert services and keep the websites they manage functioning flawlessly. They offer preventative care that provides peace of mind around the clock. For more information, check out <a href="https://www.valet.io/">their website</a> and thank you to Valet for being a Post Status partner. </p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 16 Jan 2018 21:26:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Katie Richards";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:30;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:97:"WPTavern: Gutenberg 2.0 Released With Numerous Accessibility and Keyboard Navigation Improvements";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77370";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:108:"https://wptavern.com/gutenberg-2-0-released-with-numerous-accessibility-and-keyboard-navigation-improvements";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1337:"<p><a href="https://wordpress.org/plugins/gutenberg/">Gutenberg 2.0</a> is available for testing and includes a <a href="https://wordpress.org/plugins/gutenberg/#developers">changelog</a> that&#x27;s a mile long. Accessibility, keyboard navigation, and the ability to drag-and-drop multiple images to the Gallery block are among the improvements listed.</p>\n\n\n\n<p>Clicking the Publish button displays options in the sidebar rather than a drop-down menu to add polish to the publishing flow.<br /></p>\n\n\n\n<img src="https://i0.wp.com/wptavern.com/wp-content/uploads/2018/01/PublishButtonSidebarOptions.png?w=627&ssl=1" />\n    Publish Button Options In The Sidebar\n\n\n\n\n<p>The Table of Contents has <a href="https://github.com/WordPress/gutenberg/pull/4288">been redesigned</a> to increase readability and copying and pasting has also significantly improved. </p>\n\n\n\n<p>Gutenberg 2.0 covers a lot of ground and the changes are too numerous to list here. However, Matias Ventura does a great job <a href="https://make.wordpress.org/core/2018/01/12/whats-new-in-gutenberg-12th-january/">listing the changes</a> with links to Pull Requests on GitHub where people can see how they were made.</p>\n\n\n\n<p>If you haven&#x27;t tried or tested <a href="https://wordpress.org/plugins/gutenberg/">Gutenberg</a>, now is a great time to check it out.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 15 Jan 2018 22:48:55 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:17:"Matt: Thirty-Four";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=47801";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:34:"https://ma.tt/2018/01/thirty-four/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2257:"<p>I am very thankful and grateful to have made it through the past year, which was a really special one personally and professionally. I learned to open myself up more to relationships, continued aspiring to be clear and direct with <a href="https://ma.tt/2017/01/rebirth-and-yellow-arrows/">yellow arrows</a>, and worked alongside some incredible people to tackle the biggest and hardest problems, whether it was getting plugin and theme support on WP.com or the start and growth of <a href="https://wordpress.org/plugins/gutenberg/">Gutenberg</a>.</p>\n\n\n\n<p>I read a <a href="https://ma.tt/2017/12/books-in-2017/">lot more books</a>, traveled 337k miles between 91 cities, spent more time in Texas, kept my health in a good balance with weight training, running, and a better diet including several months of 16/8 intermittent fasting, while still getting in some excellent meals with friends and loved ones (up to 58% of top 50 list). As I&#x27;m solidly in my mid-thirties now, and I want to continue to live by: all things in moderation. I consider what I do with WordPress and Automattic my life&#x27;s work, and hope to continue it as long as I&#x27;m useful. Some days I pinch myself.</p>\n\n\n\n<p>Thank you to all of you on this journey with me. I am imperfect but trying my darndest, and I&#x27;m lucky to have friends and colleagues doing the same.</p>\n\n\n\n<img src="https://i1.wp.com/ma.tt/files/2018/01/IMG_1232.jpg?w=604&ssl=1" />\n\n\n\n<p>Previously: <a href="https://ma.tt/2003/01/bday/">19</a>, <a href="https://ma.tt/2004/01/so-im-20/">20</a>, <a href="https://ma.tt/2005/01/hot-barely-legal-matt/">21</a>, <a href="https://ma.tt/2006/01/matt-22/">22</a>, <a href="https://ma.tt/2007/01/twenty-three/">23</a>, <a href="https://ma.tt/2008/01/twenty-four/">24</a>, <a href="https://ma.tt/2009/01/twenty-five/">25</a>, <a href="https://ma.tt/2010/01/twenty-six/">26</a>, <a href="https://ma.tt/2011/01/twenty-seven/">27</a>, <a href="https://ma.tt/2012/01/twenty-eight/">28</a>, <a href="https://ma.tt/2013/01/twenty-nine/">29</a>, <a href="https://ma.tt/2014/01/matt-3-0/">30</a>, <a href="https://ma.tt/2015/01/thirty-one/">31</a>, <a href="https://ma.tt/2016/01/thirty-two/">32</a>, and <a href="https://ma.tt/2017/01/thirty-three/">33</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 12 Jan 2018 01:55:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:32;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:39:"HeroPress: Make It Better, Give It Back";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2396";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:116:"https://heropress.com/essays/make-better-give-back/#utm_source=rss&utm_medium=rss&utm_campaign=make-better-give-back";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:13479:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/01/011017-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: Giving back makes me a better person and allows me to help others become better people." /><p>Recently, technology entrepreneur Anil Dash <a href="https://twitter.com/anildash/status/939137973240696832">tweeted the following question</a>:</p>\n<blockquote><p>Who is a person (not counting family) that opened doors for you in your career when they didn&#8217;t have to? Anytime is a good time to show gratitude!</p></blockquote>\n<p>If you need a pick-me-up, go and read through the replies and threads that start with Anil&#8217;s question. There are replies from many people who are grateful to others for an unending variety of reasons, some large and immediate, some small and indirect, some that were only realised months or years later.</p>\n<p>One commonality between many of the replies is that of selflessness. People who help others without expecting something in return. This prompted me to think about those people who&#8217;ve helped me in my career through their own selflessness, without my prompting, and without their expecting anything in return.</p>\n<p>I&#8217;m lucky that several people have helped me in this way. My WordPress story started in around 1998 when, as a fourteen year old living in a house that was one among just sixteen in a forest in the English countryside, my divorced parents saved up and bought me a Windows 98 PC for Christmas. A personal computer was a big expenditure for my parents. We weren&#8217;t able to afford an Internet connection, and at that time I don&#8217;t recall being particularly aware of the Internet. As a result, I took an interesting route into web development.</p>\n<p>Windows PCs at the time came bundled with Internet Explorer and promotional material from Internet service providers in HTML files. I wanted to find out how these pages were built, and I discovered Frontpage Express could edit the files, although often with many errors (which years later I attributed to the lack of HTML standards in use).</p>\n<blockquote><p>One day my curiosity lead me to the View Source menu in Internet Explorer. <strong>Boom</strong>. What is all this code? What do all these angle brackets do? Is this how web pages are built? Can I change this?</p></blockquote>\n<p>Naturally, everything I changed initially broke pages completely. The Undo command was my version control system. I figured out that text wrapped in <code>&lt;b&gt;</code> produced bold text. I hadn&#8217;t a clue how a <code>&lt;table&gt;</code> worked without breaking it. <code>&lt;marquee&gt;</code> ended up everywhere. Poor support for much of the markup in these files made Frontpage redundant. Looking back, I could say that the View Source menu in Internet Explorer was an important part of the progression of my career. Maybe also that of thousands of other web developers. If the inventor and early adopters of the web hadn&#8217;t been strong proponents of open data and information sharing, it&#8217;s possible that the View Source menu would never have existed and the open web would not have flourished to the extent that it has.</p>\n<p>(The topic of open access to technology, both software and hardware, can be discussed all day. Consider if Adobe Photoshop would have had the same great commercial success that it did without its widespread piracy leading to an abundance of students leaving school with years of Photoshop experience. But I digress.)</p>\n<p>I spent evenings after school hacking on HTML. My older brother Adam gave me a book titled &#8220;How to Create pages for the Web using HTML&#8221; which introduced me to the world of HTML 2.0. I learned about the available tags. I learned about inline CSS, which set me up for learning React twenty years later. And I learned that you can see the source behind any web page, hack on it, and learn from it.</p>\n<h3>Getting Online</h3>\n<p>I don&#8217;t remember the first web page that I put online when we eventually got Internet access. I doubt it was any good, but what the whole experience did do was help my curiosity grow, to which I&#8217;ve attributed much of my success so far. Being curious about a topic helps enormously when learning, self-teaching, and staying motivated.</p>\n<p>I didn&#8217;t attend university, partly due to my excellent high school grades not being followed up by any good college grades (in the UK, there’s two years of sixth form college between high school and university). In hindsight I see that I got bored of state education, and two short years flew by with no time for me to to fix that attitude. Stay in school, kids.</p>\n<p>The years after school saw me working barely above minimum wage in a supermarket by day and hacking on web projects at night. I was first introduced to WordPress by <a href="https://profiles.wordpress.org/lumpysimon/">my brother Simon</a> who built websites for customers of his printing business. After a brief period of building my own CMS (everyone&#8217;s done it, right?), I realised there were many advantages to using a free and community built CMS maintained by a relatively large number of people. I started building simple WordPress sites for myself. Along with Simon and his friend Tom, we played around with the idea of a hosted web service to make it even easier for people to publish online using WordPress. The project never went anywhere (hello wordpress.com), but the ideas we explored helped me learn a lot about WordPress.</p>\n<blockquote><p>Who is a person (not counting family) that opened doors for you in your career when they didn&#8217;t have to? Anytime is a good time to show gratitude!</p></blockquote>\n<p>I can pinpoint the start of my career with WordPress when Tom recommended me to someone who was looking for a WordPress plugin developer. That person, Conor O&#8217;Neill, became one of the people that opened a door for me in my career when they didn&#8217;t have to. Conor was pleased with the plugin work that I did for him, and selflessly passed my name onto several of his friends and acquaintances. He didn&#8217;t need to do that, it didn&#8217;t directly benefit him, but he did it because he knew it would help out his acquaintances and help me to get work.</p>\n<h3>Becoming A WordPress Consultant</h3>\n<p>I started building WordPress themes and plugins for people that Conor gave my name to. I didn&#8217;t have much experience at the time, but I had the advantage of personal recommendations. It&#8217;s difficult to overstate how valuable a personal recommendation is. All the advertising in the world can be useless when competing against a personal recommendation. If you&#8217;re looking to start or change a career, I recommend asking people to pass your name on to friends and colleagues whenever they can.</p>\n<blockquote><p>I&#8217;m one of the lucky ones that got a good start through personal recommendations, and if you can do that too then it&#8217;ll set you up well.</p></blockquote>\n<p>Conor passed my name onto a chap named Damien Mulley who was also instrumental in advancing my career by passing my name on when he didn&#8217;t need to. I owe a lot to the selflessness of Conor and Damien.</p>\n<p>Around this time I started finding bugs in WordPress (a practice that I continue to this day). Another key point in my career came when I reported a bug on the WordPress bug tracking system, and was greeted with a pleasant welcome. One of the contributors, Lloyd Budd, was kind enough to take the time to explain to me that I could fix the bug myself and submit the fix to the WordPress project. He pointed me to resources for learning Subversion and creating patches. That small act of help lead to me becoming a regular WordPress contributor, and ultimately one of the core developers. Lloyd didn&#8217;t have to use his free time to help others out, but he did, and it had long-reaching impact on my career and on the WordPress project.</p>\n<p>After a year of freelancing, I was able to get enough work that I could drop down to part time work at my supermarket job. I worked and self-taught for seventy hours a week for six months. I was afraid of leaving a stable job despite earning three times as much working as a freelance developer, but making that jump felt very scary before I made it. A combination of personal recommendations and working to get a name for myself in the WordPress sphere lead me to leave my supermarket job, freelance for a few years, become the first employee at WordPress agency <a href="https://codeforthepeople.com/">Code for the People</a>, and ultimately to join <a href="https://humanmade.com/">Human Made</a> as a senior WordPress engineer.</p>\n<h3>Giving Back</h3>\n<p>I’m lucky that I’m able to spend some of my time contributing back to WordPress, and I&#8217;ve been thinking a lot about how the principles of open source apply outside of software. I gave <a href="https://wordpress.tv/2016/05/31/john-blackbourn-rachel-mccollin-and-taco-verdonschot-lightning-sessions/">a short talk at WordCamp London in 2016</a> where I coined the phrase &#8220;<em>Make it better, give it back</em>&#8220;, which is how I interpret the fundamental principles of open source. It’s the idea of improving upon an existing process and giving it back to the community in order to embetter everyone, whether it’s through an open data project such as OpenStreetMap, a community initiative in your local area, or shared learning.</p>\n<blockquote><p>Recently I came to realise that the &#8220;<em>it</em>&#8221; in &#8220;<em>Make it better, give it back</em>&#8221; doesn&#8217;t have to refer to the primary aspect of what you&#8217;re contributing to.</p></blockquote>\n<p>Lloyd made WordPress better by writing code and giving it back, but he also made WordPress better by improving the knowledge and skills of its community members, many of whom in turn give back in a variety of ways.</p>\n<p>Giving back allows me to improve many of my own skills. It allows me to challenge myself, not only technically but also in areas such as communication, compassion, critical thinking, and time management. Giving back makes me a better person and allows me to help others become better people.</p>\n<a href="https://heropress.com/wp-content/uploads/2018/01/dsc_3097.jpg"><img class="wp-image-2398" src="https://heropress.com/wp-content/uploads/2018/01/dsc_3097-768x1024.jpg" alt="John and Francesca" width="350" height="467" /></a>John and Francesca\n<p>Giving back has advanced my professional career thanks to the technical and people skills that I learn from it and the recognition gained by my contributions. In turn this has lead to many new friends, a career in a field that I enjoy very much, and it also lead to me finding the love of my life at a WordPress contributor day.</p>\n<p>I hope that in one way or another I&#8217;ve given back to many people in the open source community. I&#8217;ve been involved with WordPress for twelve years now, and over those years I&#8217;ve given advice, pointers, and encouragement to others that might seem small or inconsequential at the time but can be just the sort of encouragement that somebody needs. The difference between not receiving a reply to a query, and receiving one which says &#8220;Thanks! That&#8217;s a good start&#8221; might mean the difference between never contributing again versus becoming a decade long community member.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: Make It Better, Give It Back" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Make%20It%20Better%2C%20Give%20It%20Back&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fmake-better-give-back%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Make It Better, Give It Back" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fmake-better-give-back%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fmake-better-give-back%2F&title=Make+It+Better%2C+Give+It+Back" rel="nofollow" target="_blank" title="Share: Make It Better, Give It Back"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/make-better-give-back/&media=https://heropress.com/wp-content/uploads/2018/01/011017-150x150.jpg&description=Make It Better, Give It Back" rel="nofollow" target="_blank" title="Pin: Make It Better, Give It Back"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/make-better-give-back/" title="Make It Better, Give It Back"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/make-better-give-back/">Make It Better, Give It Back</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 10 Jan 2018 08:00:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"John Blackbourn";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:29:"Matt: Ariel Levy in Longreads";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=47797";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:46:"https://ma.tt/2018/01/ariel-levy-in-longreads/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:769:"<p>I had originally planned last year to write <a href="https://ma.tt/2017/12/books-in-2017/">a review of each book as I read it</a>, but The Rules Do Not Apply threw a spanner in the works. I had no idea how to write about it, much less review it. The author, <a href="https://longreads.com/2017/03/14/ariel-levy-interview/">Ariel Levy, has a great interview in Longreads from when the book came out</a>.</p>\n\n\n\n<p>Speaking of Longreads, <a href="https://longreads.com/2017/12/29/the-25-most-popular-longreads-exclusives-of-2017/">don&#x27;t forget to check out their top 25 exclusives from 2017</a>, and <a href="https://longreads.com/2017/12/11/longreads-best-of-2017-all-of-our-no-1-story-picks/">their number 1 picks overall</a>. Some amazing writing in there.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 08 Jan 2018 00:44:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:67:"Lorelle on WP: Vulnerability in phpMyAdmin Requires Immediate Patch";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:37:"http://lorelle.wordpress.com/?p=14409";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:94:"https://lorelle.wordpress.com/2018/01/06/vulnerability-in-phpmyadmin-requires-immediate-patch/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4273:"<p>A <a href="http://www.itprotoday.com/patch-management/critical-csrf-security-vulnerability-phpmyadmin-database-tool-patched" title="Critical CSRF Vulnerability in phpMyAdmin Database Tool Patched | IT Pro">critical CSRF Vulnerability in phpMyAdmin Database administration tool</a> has been found and a <a href="https://www.phpmyadmin.net/security/PMASA-2017-9/" title="phpMyAdmin - Security - PMASA-2017-9">patch is available</a> for all computers and servers running the MySQL database. </p>\n<p>Does this include you?</p>\n<p>If you are using WordPress, yes it does. </p>\n<p>Contact your web host to ensure phpMyAdmin is updated immediately. </p>\n<p>If you are self-hosted and manage your own server, update phpMyAdmin immediately. </p>\n<p>If you are using WordPress or phpMyAdmin and MySQL on your computer through <a href="http://www.wampserver.com/en/" title="WAMP">WAMP</a>, <a href="http://www.mamp.info/en/index.html" title="MAMP">MAMP</a>, <a href="http://www.apachefriends.org/en/xampp.html" title="XAMPP">XAMPP</a>, <a href="http://www.instantwp.com/" title="Instant WordPress">Instant WordPress</a>, <a href="http://serverpress.com/products/desktopserver/" title="DesktopServer">DesktopServer</a>, <a href="http://bitnami.org/stack/wordpress" title="BitNami">BitNami</a> or any of the other ways you can install WordPress on your computer or a stick (USB), update phpMyAdmin by using the patch or check the install technique&#8217;s site for updates. </p>\n<p><strong>If you are using WordPress.com, don&#8217;t worry.</strong> This does not apply to you or your site. </p>\n<p>The flaw affects phpMyAdmin versions 4.7.x prior to 4.7.7. Hopefully, your server/web host company has been updating phpMyAdmin all along and you don&#8217;t need to worry, but even though this is a medium security vulnerability, it is your responsibility as a site owner and administrator to ensure that your site is safe. Don&#8217;t just rely on GoDaddy, Dreamhost, or whatever hosting service you use to take care of these things for you. Sometimes they are on top of these before an announcement is made public. Other times, they are clueless and require customer intervention and nagging. </p>\n<p>Now, what is phpMyAdmin?</p>\n<p>MySQL is an open source database program, and <a href="https://www.phpmyadmin.net/" title="phpMyAdmin">phpMyAdmin</a> is the free, open source tool that makes the administration and use of MySQL easier to manage. <em>It is not a database. It is a database manager.</em> You can <a href="https://lorelle.wordpress.com/2014/08/10/find-search-replace-and-delete-in-the-wordpress-database/" title="Find, Search, Replace, and Delete in the WordPress Database « Lorelle on WordPress">easily search and replace data</a> in the database, make changes, and do other maintenance and utility tasks in the database.</p>\n<p>Every installation of WordPress requires PHP and MySQL along with a variety of other web-based programming packages and software. Most installations by web hosts and portable versions of WordPress add phpMyAdmin to manage the WordPress site. It is not required for WordPress to work, but don&#8217;t assume that it is or isn&#8217;t installed. CHECK. </p>\n<p>To find out if phpMyAdmin is installed on your site:</p>\n<ol>\n<li>Check with your web host and ask. Don&#8217;t expect their customer service staff to know for sure. Make them check your account and verify whether or not it is installed, and if they&#8217;ve updated. Push them for a specific answer.</li>\n<li>Check the site admin interface (cPanel, Plesk, etc.) to see if it is installed.</li>\n<li>Log into your site through secure FTP into the root (if you have access) and look for the installation at <em>/usr/share/phpmyadmin</code> or <code>localhost/phpmyadmin</code>. Unfortunately, it could be anywhere depending upon the installation as these are virtual folders, not folders found on your computer, so it must be assigned to a location.</li>\n<li>If running a portable installation of MySQL and/or WordPress, follow the instructions for that tool and download and install all patches to ensure phpMyAdmin is updated to the latest secure version.</li>\n</ol>\n<div class="sig">\n<p><img src="https://lorelle.files.wordpress.com/2006/08/sig.gif" alt="" /></p>\n<hr /> </div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 06 Jan 2018 16:55:40 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Lorelle VanFossen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:35;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:88:"WPTavern: Zac Gordon Launches Gutenberg Development Course, Includes More Than 30 Videos";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=77285";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:98:"https://wptavern.com/zac-gordon-launches-gutenberg-development-course-includes-more-than-30-videos";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2756:"<p><a href="https://zacgordon.com/">Zac Gordon</a>, a technology educator, has released his <a href="http://gutenberg.courses/">Gutenberg Development course</a>. The course is $79 but is available for $49 using the coupon code <strong>earlyadopter</strong>.</p>\n\n\n\n<p>Gordon says the course is aimed at developers who want to update their themes, plugins, shortcodes, etc. to work with Gutenberg and take advantage of blocks. <br /></p>\n\n\n\n<p>"There is also some content I am adding geared towards theme developers, but honestly there is not much to that," Gordon said. "I think plugin developers will fill a lot of the needs of theme developers and help prevent them from having to build too many custom blocks. </p>\n\n\n\n<p>"Also, in my opinion, blocks belong in plugins, so maybe some theme developers will migrate into plugin development through working with blocks."</p>\n\n\n\n<p>The course includes more than 30 videos, a dozen example blocks, access to support forums, and the community run Slack channel. It covers how Gutenberg works, how to extend and customize it, and using a modern JavaScript development approach.</p>\n\n\n\n<p>Gordon learned quite a few things about Gutenberg while creating the course. "Specifically, I learned Gutenberg is really just React under the hood, and then the more traditional WordPress PHP under that," he said.</p>\n\n\n\n<p>"Digging deeper into the source attributes system that Gutenberg has to keep track of dynamic data was interesting. Also, there are far more possibilities with server-side code hooking into blocks than I thought ahead of time. I also came to the opinion that I&#x27;m not sure why someone would build a block in anything other than React, so I&#x27;m interested to see what common practices evolve."</p>\n\n\n\n<p>Creating the course has allowed Gordon to dive deep into Gutenberg. So does he think it&#x27;s a suitable replacement for the editor? <br /></p>\n\n\n\n<p>"I think most users will feel Gutenberg is an improvement of the editing experience," he responded. "We are definitely moving in the right direction. Ironically perhaps, I still like site and page builder plugins when editing or creating content in WordPress."</p>\n\n\n\n<p>Gutenberg is still in a high state of flux with rapid development. According to Gordon, if there is one thing developers should know about Gutenberg, it&#x27;s that learning JavaScript deeply will pay off.<br /></p>\n\n\n\n<p>"Matt Mullenweg was right when he said &#x27;<a href="https://www.youtube.com/watch?v=KrZx4IY1IgU">Learn JavaScript Deeply</a>&#x27;," Gordon said. "In terms of Gutenberg, that means a foundation with ES+, JSX/React, and webpack/babel/etc. You can learn as you go, but we are definitely moving from the time of learning to a time of doing."</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 05 Jan 2018 23:32:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:81:"WPTavern: WPWeekly Episode 300 – Interview with Matt ‘Gutenbeard’ Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=77276&preview=true&preview_id=77276";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:82:"https://wptavern.com/wpweekly-episode-300-interview-with-matt-gutenbeard-mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1492:"<p>In this the 300th episode, <a href="http://jjj.me">John James Jacoby</a> and I interview <a href="https://ma.tt/">Matt &#8216;Gutenbeard&#8217; Mullenweg</a>, co-creator of the WordPress project. We discuss a range of topics including, the somewhat controversial poetry reading that included a curse word prior to the State of the Word, the WordPress Foundation increasing its range of funding, and of course, Gutenberg.</p>\n<p>One of the big takeaways from this interview is learning that Gutenberg will not arrive at the flick of a switch. There will be a transition period and a considerable amount of effort to make it as smooth as possible. Unlike episode 296, Mullenweg&#8217;s internet is fantastic and we didn&#8217;t experience any audio issues. A transcription of this interview will be published in a few days.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, January 10th 3:00 P.M. Eastern</p>\n<p>Subscribe to <a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738">WordPress Weekly via Itunes</a></p>\n<p>Subscribe to <a href="https://www.wptavern.com/feed/podcast">WordPress Weekly via RSS</a></p>\n<p>Subscribe to <a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr">WordPress Weekly via Stitcher Radio</a></p>\n<p>Subscribe to <a href="https://play.google.com/music/listen?u=0#/ps/Ir3keivkvwwh24xy7qiymurwpbe">WordPress Weekly via Google Play</a></p>\n<p><strong>Listen To Episode #300:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 04 Jan 2018 03:55:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:11:"\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:40:"HeroPress: A Review Of HeroPress in 2017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://heropress.com/?p=2387";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:119:"https://heropress.com/a-review-of-heropress-2017/#utm_source=rss&utm_medium=rss&utm_campaign=a-review-of-heropress-2017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:9442:"<img width="960" height="480" src="https://heropress.com/wp-content/uploads/2018/01/010318-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: HeroPress is something WordPress people do for themselves. The world simply gets to watch." /><p><strong>FIRST</strong>: please leave a comment if HeroPress has inspired or impacted you this year. I&#8217;ve love for you to be a part of this post.</p>\n<p>With that out of the way, another year of HeroPress has come and gone. HeroPress is still young enough that we can&#8217;t really see multi-year trends, but I still find it interesting to look at them and try to guess things.  In this post we&#8217;ll look at some stats, some things I tried that didn&#8217;t work, some things that did work, and some dreams for the future.</p>\n<h3>Statistics</h3>\n<h4>Diversity</h4>\n<p>Diversity has always been important to me.  In 2015 and 2016 I had more men than women, by a pretty wide margin, and that bothered me.  In 2017 I&#8217;m happy to say we had 32 women and 21 men. I didn&#8217;t work SUPER hard at that, it was just something I kind of kept in my head when I was looking for new folks.</p>\n<p>We also had great geographical diversity in our contributors, representing 26 different countries.</p>\n<table>\n<tbody>\n<tr>\n<th>Country</th>\n<th>No. of Essays</th>\n</tr>\n<tr>\n<td>Bangladesh</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Cameroon</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Croatia</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Finland</td>\n<td>2</td>\n</tr>\n<tr>\n<td>France</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Germany</td>\n<td>2</td>\n</tr>\n<tr>\n<td>India</td>\n<td>7</td>\n</tr>\n<tr>\n<td>Italy</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Jamaica</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Nepal</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Netherlands</td>\n<td>2</td>\n</tr>\n<tr>\n<td>Nigeria</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Norway</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Poland</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Romania</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Russia</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Scotland</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Serbia</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Somalia</td>\n<td>1</td>\n</tr>\n<tr>\n<td>South Africa</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Spain</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Sweden</td>\n<td>1</td>\n</tr>\n<tr>\n<td>Turkey</td>\n<td>1</td>\n</tr>\n<tr>\n<td>United Kingdom</td>\n<td>1</td>\n</tr>\n<tr>\n<td>United States</td>\n<td>13</td>\n</tr>\n<tr>\n<td>Yemen</td>\n<td>1</td>\n</tr>\n</tbody>\n</table>\n<p>The US and India had far more than any other country, which has been the trend since we started, but the US has far fewer in 2017 than 2016.</p>\n<h4>Readers</h4>\n<p>We had traffic from 175 countries this year.</p>\n<p><img class="aligncenter size-full wp-image-2388" src="https://heropress.com/wp-content/uploads/2018/01/country_traffic.png" alt="World map showing HeroPress visitors" width="951" height="547" /></p>\n<p>That said, HeroPress saw less traffic overall in 2017 than in 2016.</p>\n<p><img class="aligncenter size-full wp-image-2389" src="https://heropress.com/wp-content/uploads/2018/01/heropress_stats.png" alt="Bar chart showing HeroPress stats" width="692" height="282" /></p>\n<h4>The Important Stuff</h4>\n<p>As fun as stats are, it&#8217;s been pointed out to me many times that they&#8217;re meaningless. Someone asked me recently how I define success for HeroPress, and the answer was that at least one person is impacted for the better. The interesting twist to that is the hierarchy of people impacted positively by HeroPress.  It goes like this:</p>\n<p><strong>Topher</strong>: Because he gets to see them all, AND behind the scenes. It&#8217;s heady stuff.</p>\n<p><strong>Contributors themselves</strong>: MANY people have told me that writing their story changed their life. The simple act of processing things from the past, and getting them out there, and being vulnerable is powerful.</p>\n<p><strong>Readers</strong>: Lot&#8217;s of people tell me it&#8217;s inspiring.</p>\n<p>What we learn from the above information is that HeroPress would be a success if we had zero readers. HeroPress is something WordPress people do for themselves. The world simply gets to watch.</p>\n<h3>Experiments</h3>\n<h4>The Scholarship</h4>\n<p>Last spring the folks from WPShout approached me about working together to offer a scholarship.  They would offer the actual scholarship, and we would manage getting applicants and deciding who won.</p>\n<p>It was a huge success.  We had tons of traffic, many great applicants, and the winners did great things with their scholarships.  We&#8217;d love to do something like that again, so if you&#8217;re interested, drop us a note.</p>\n<h4>Commercial Support</h4>\n<p>This changed a bit in 2017. Most of the year was sponsored by Gravity Forms, which was great. That ended with only a few weeks left in the year, and I was surprised to find that there were a number of organizations that were interested in sponsoring a single week. That worked quite well, and I&#8217;m interested in looking into that more.</p>\n<p>At WordCamp US I spoke to an organization that was interested in sponsoring an entire quarter, which would be a first.  It hasn&#8217;t happened yet, but I&#8217;m also looking into that some more.</p>\n<h4>Donations</h4>\n<p>This didn&#8217;t really work out. I put up the donation form at the request of a few people that wanted to give. Those people gave, and a few more, but after the third day or so there were no more. There could be many reasons, but I&#8217;m not too concerned. I&#8217;ll probably take the form down, and if I ask for donations again it&#8217;ll be a Public Radio style press-a-thon for a week or something. Lots of flash, and then it&#8217;s gone for a year.</p>\n<h3>Thanks</h3>\n<p>As always happens, I got some great advice this year and lots of donated services and software.</p>\n<p>Many thanks to Tine Haugen from XWP for her ongoing input from a Larger Company perspective.</p>\n<p>Thanks to <a href="https://pagely.com/">Pagely</a> for hosting HeroPress.</p>\n<p>Thanks to these commercial plugin folk that donated licenses:</p>\n<ul>\n<li>Analytify &#8211; Google Analytics Dashboard</li>\n<li>Give &#8211; Donation Plugin</li>\n<li>Make Plus</li>\n<li>Maps Builder Pro</li>\n<li>Ninja Forms</li>\n<li>Postmatic &amp; Postmatic Labs</li>\n</ul>\n<p>Thanks to these wonderful software developers who&#8217;ve released there work to the world for free:</p>\n<ul>\n<li>Akismet Anti-Spam</li>\n<li>Blog Time</li>\n<li>Jetpack by WordPress.com</li>\n<li>Post Type Archive Descriptions</li>\n<li>Public Post Preview</li>\n<li>Really Simple Series</li>\n<li>rtSocial</li>\n<li>Simple 301 Redirects</li>\n<li>Simply Exclude</li>\n<li>Widget Logic</li>\n<li>WP Custom Login Page Logo</li>\n<li>WP Retina 2x</li>\n<li>Yoast SEO</li>\n</ul>\n<p>Thanks to 2017&#8217;s commercial supporters:</p>\n<ul>\n<li><a href="https://eventespresso.com/">Event Espresso</a></li>\n<li><a href="https://www.gowp.com/">GoWP</a></li>\n<li><a href="https://www.gravityforms.com/">Gravity Forms</a></li>\n<li><a href="https://rtcamp.com/">rtCamp</a></li>\n</ul>\n<p><strong>MOST IMPORTANTLY</strong></p>\n<p>Thanks to our contributors.  Without people willing to share of themselves, tell us their stories, make themselves vulnerable, HeroPress would not exist. Thank you SO SO much, all of you who&#8217;ve written.</p>\n<h3>Your Turn</h3>\n<p>As I mentioned at the top of the post, the rest of the post is to be written by you.  How has HeroPress impacted you this year? What value is there besides numbers and charts and graphs?</p>\n<p>Please leave a comment.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: A Review Of HeroPress in 2017" class="rtsocial-twitter-button" href="https://twitter.com/share?text=A%20Review%20Of%20HeroPress%20in%202017&via=heropress&url=https%3A%2F%2Fheropress.com%2Fa-review-of-heropress-2017%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: A Review Of HeroPress in 2017" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fa-review-of-heropress-2017%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fa-review-of-heropress-2017%2F&title=A+Review+Of+HeroPress+in+2017" rel="nofollow" target="_blank" title="Share: A Review Of HeroPress in 2017"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/a-review-of-heropress-2017/&media=https://heropress.com/wp-content/uploads/2018/01/010318-150x150.jpg&description=A Review Of HeroPress in 2017" rel="nofollow" target="_blank" title="Pin: A Review Of HeroPress in 2017"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/a-review-of-heropress-2017/" title="A Review Of HeroPress in 2017"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/a-review-of-heropress-2017/">A Review Of HeroPress in 2017</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 03 Jan 2018 17:49:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:47:"Dev Blog: The Month in WordPress: December 2017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5424";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:72:"https://wordpress.org/news/2018/01/the-month-in-wordpress-december-2017/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4742:"<p>Activity slowed down in December in the WordPress community, particularly in the last two weeks. However, the month started off with a big event and work pushed forward in a number of key areas of the project. Read on to find out more about what transpired in the WordPress community as 2017 came to a close.</p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<h2>WordCamp US 2017 Brings the Community Together</h2>\n\n\n\n<p>The latest edition of <a href="https://2017.us.wordcamp.org/">WordCamp US</a> took place last month in Nashville on December 1-3. The event brought together over 1,400 WordPress enthusiasts from around the world, fostering a deeper, more engaged global community.</p>\n\n\n\n<p>While attending a WordCamp is always a unique experience, you can catch up on <a href="https://wordpress.tv/event/wordcamp-us-2017/">the sessions on WordPress.tv</a> and look through <a href="https://www.facebook.com/pg/WordCampUSA/photos/?tab=albums">the event photos on Facebook</a> to get a feel for how it all happened. Of course, <a href="https://wordpress.tv/2017/12/04/matt-mullenweg-state-of-the-word-2017/">Matt Mullenweg’s State of the Word</a> talk is always one of the highlights at this event.</p>\n\n\n\n<p>The next WordCamp US will be held in Nashville again in 2018, but if you would like to see it hosted in your city in 2019 and 2020, then <a href="https://make.wordpress.org/community/2017/12/19/apply-to-host-wordcamp-us-2019-2020/">you have until February 2 to apply</a>.</p>\n\n\n\n<h2>WordPress User Survey Data Is Published</h2>\n\n\n\n<p>Over the last few years, tens of thousands of WordPress users all over the world have filled out the annual WordPress user survey. The results of that survey are used to improve the WordPress project, but that data has mostly remained private. This has changed now and <a href="https://wordpress.org/news/2017/12/wordpress-user-survey-data-for-2015-2017/">the results from the last three surveys are now publicly available</a> for everyone to analyze.</p>\n\n\n\n<p>The data will be useful to anyone involved in WordPress since it provides a detailed look at who uses WordPress and what they do with it — information that can help inform product development decisions across the board.</p>\n\n\n\n<h2>New WordPress.org Team for the Tide Project</h2>\n\n\n\n<p>As announced at WordCamp US, <a href="https://make.wordpress.org/tide/2017/12/02/new-home/">the Tide project is being brought under the WordPress.org umbrella</a> to be managed and developed by the community.</p>\n\n\n\n<p>Tide is a series of automated tests run against every plugin and theme in the directory to help WordPress users make informed decisions about the plugins and themes that they choose to install.</p>\n\n\n\n<p>To get involved in developing Tide, jump into the #tide channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a>, and follow <a href="https://make.wordpress.org/tide/">the Tide team blog</a>.</p>\n\n\n\n<hr class="wp-block-separator" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul>\n    <li>If you’re following the development of Gutenberg, or if you want a primer on where it’s headed, then <a href="https://wordpress.tv/2017/12/10/morten-rand-hendriksen-gutenberg-and-the-wordpress-of-tomorrow/">Morten Rand-Hendriksen’s talk from WordCamp US</a> is a must watch.</li>\n    <li>The annual surveys for WordPress <a href="https://wordpressdotorg.polldaddy.com/s/2017-annual-meetup-member-survey">meetup members</a> and <a href="https://wordpressdotorg.polldaddy.com/s/2017-annual-meetup-organizer-survey">meetup organizers</a> are available for people to fill out — if you’re involved in or attend your local meetup group then be sure to complete those.</li>\n    <li>10up has <a href="https://distributorplugin.com/">a brand new plugin in beta</a> that will assist with powerful and flexible content publishing and syndication across WordPress sites.</li>\n    <li><a href="https://make.wordpress.org/community/2017/12/07/should-we-change-the-default-wordcamp-theme-to-campsite-2017/">The Community Team is exploring a move</a> to make the recently developed CampSite theme the default theme for all new WordCamp websites. This is the theme that was developed and employed for <a href="https://2017.europe.wordcamp.org">WordCamp Europe 2017</a>.</li>\n    <li>The team working on the multisite features of WordPress Core has recently published <a href="https://make.wordpress.org/core/2017/12/19/multisite-roadmap-published/">their planned roadmap for development</a>.</li>\n</ul>\n\n\n\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 03 Jan 2018 10:00:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Hugh Lashbrooke";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:39;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:50:"Dev Blog: WordPress User Survey Data for 2015-2017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=5310";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://wordpress.org/news/2017/12/wordpress-user-survey-data-for-2015-2017/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:61756:"<p>For many years, we&#8217;ve invited folks to tell us how they use WordPress by filling out an annual survey. In the past, interesting results from this survey have been shared in the annual <a href="https://ma.tt/2017/12/state-of-the-word-2017/">State of the Word</a> address. This year, for the first time, the results of the 2017 survey are being published on WordPress News, along with the results of the 2015 and 2016 survey.</p>\n<p>So that information from the survey doesn&#8217;t reveal anything that respondents might consider private, we do not publish a full export of the raw data. We’d love to make this information as accessible as possible, though, so if you have a suggestion for an OS project or tool we can put the data into that allows people to play with it that still protects individual response privacy, please leave a comment on this post!</p>\n<h4>Major Groups</h4>\n<p>This survey features multiple groups, dividing respondents at the first question:</p>\n<blockquote><p>Which of the following best describes how you use WordPress? (<em>Mandatory</em>)</p></blockquote>\n<p>Those who selected &#8220;I&#8217;m a designer or developer, or I work for a company that designs/develops websites; I use WordPress to build websites and/or blogs for others. (This might include theme development, writing plugins, or other custom work.)&#8221; were served questions from what we&#8217;ll call the &#8220;WordPress Professionals&#8221; group.</p>\n<p>This &#8220;WordPress Professionals&#8221; group is further divided into WordPress Company and WordPress Freelancer/Hobbyist groups, based on how the respondent answered the question, &#8220;Which of the following best describes your involvement with WordPress? (2015) / Do you work for a company, or on your own? (2016-17).&#8221;</p>\n<p>Those who selected &#8220;I own, run, or contribute to a blog or website that is built with WordPress.&#8221; were served questions in what we&#8217;re calling the &#8220;WordPress Users&#8221; group.</p>\n<p>The relevant survey group is noted in each table below. In the case of questions that were served to different groups in 2015 but then served to all respondents in 2016 and 2017, the group responses from 2015 have been consolidated into one set of data for easier comparison between years.</p>\n<h4>Survey results</h4>\n<p><a href="https://wordpress.org/news/feed/#pro">Jump to answers from WordPress Professionals</a></p>\n<p><a href="https://wordpress.org/news/feed/#user">Jump to answers from WordPress Users</a></p>\n<p><a href="https://wordpress.org/news/feed/#all">Jump to answers from All Respondents</a></p>\n<p><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></p>\n<h3>Which of the following best describes how you use WordPress? (Mandatory)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td>Number of responses (since this question was mandatory, the number of responses here is the total number for the survey)</td>\n<td>45,995</td>\n<td></td>\n<td>15,585</td>\n<td></td>\n<td>16,029</td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;m a designer or developer, or I work for a company that designs/develops websites; I use WordPress to build websites and/or blogs for others. (This might include theme development, writing plugins, other custom work.)</td>\n<td>26,662</td>\n<td>58%</td>\n<td>8,838</td>\n<td>57%</td>\n<td>9,099</td>\n<td>57%</td>\n</tr>\n<tr>\n<td>I own, run, or contribute to a blog or website that is built with WordPress.</td>\n<td>16,130</td>\n<td>35%</td>\n<td>5,293</td>\n<td>34%</td>\n<td>5,625</td>\n<td>35%</td>\n</tr>\n<tr>\n<td>Neither of the above.</td>\n<td>3,204</td>\n<td>7%</td>\n<td>1,460</td>\n<td>9%</td>\n<td>1,306</td>\n<td>8%</td>\n</tr>\n</tbody>\n</table>\n<h2 id="pro">WordPress Professionals</h2>\n<h3><strong>Which of the following best describes your involvement with WordPress? (Mandatory, 2015) / Do you work for a company, or on your own? (Mandatory, 2016-17)</strong></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>26,699</td>\n<td></td>\n<td>8,838</td>\n<td></td>\n<td>9,101</td>\n<td></td>\n</tr>\n<tr>\n<td>My primary job is working for a company or organization that uses WordPress.</td>\n<td>9,505</td>\n<td>36%</td>\n<td>3,529</td>\n<td>40%</td>\n<td>3,660</td>\n<td>40%</td>\n</tr>\n<tr>\n<td>My primary job is as a self-employed designer or developer that uses WordPress.</td>\n<td>9,310</td>\n<td>35%</td>\n<td>3,188</td>\n<td>36%</td>\n<td>3,440</td>\n<td>38%</td>\n</tr>\n<tr>\n<td>I earn money from part-time or occasional freelance work involving WordPress.</td>\n<td>5,954</td>\n<td>22%</td>\n<td>1,633</td>\n<td>18%</td>\n<td>1,590</td>\n<td>17%</td>\n</tr>\n<tr>\n<td>Work that I do involving WordPress is just a hobby, I don&#8217;t make money from it.</td>\n<td>1,930</td>\n<td>7%</td>\n<td>491</td>\n<td>6%</td>\n<td>411</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>How does your company or organization work with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,342</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Build/design and/or maintain websites or blogs for other people, companies, or organizations.</td>\n<td>7,772</td>\n<td>27%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Develop or customize themes.</td>\n<td>5,404</td>\n<td>19%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Build/design and/or maintain websites or blogs for my own use.</td>\n<td>4,733</td>\n<td>16%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Host websites for customers.</td>\n<td>4,397</td>\n<td>15%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Develop or distribute plugins.</td>\n<td>3,181</td>\n<td>11%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Provide educational resources to help others to use WordPress.</td>\n<td>1,349</td>\n<td>5%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Sponsor and/or attend WordCamps.</td>\n<td>1,127</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Contribute bug reports and/or patches to WordPress core.</td>\n<td>914</td>\n<td>3%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>182</td>\n<td> 1%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>3,457</td>\n<td></td>\n<td>3,598</td>\n<td></td>\n</tr>\n<tr>\n<td>We make websites for others.</td>\n<td></td>\n<td></td>\n<td>2,695</td>\n<td>24%</td>\n<td>2,722</td>\n<td>23%</td>\n</tr>\n<tr>\n<td>We make websites for ourselves.</td>\n<td></td>\n<td></td>\n<td>2,355</td>\n<td>21%</td>\n<td>2,470</td>\n<td>21%</td>\n</tr>\n<tr>\n<td>We develop or customize themes.</td>\n<td></td>\n<td></td>\n<td>1,866</td>\n<td>16%</td>\n<td>1,910</td>\n<td>16%</td>\n</tr>\n<tr>\n<td>We host websites for others.</td>\n<td></td>\n<td></td>\n<td>1,564</td>\n<td>14%</td>\n<td>1,595</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>We develop or distribute plugins.</td>\n<td></td>\n<td></td>\n<td>1,283</td>\n<td>11%</td>\n<td>1,342</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>We provide educational resources to help others to use WordPress.</td>\n<td></td>\n<td></td>\n<td>581</td>\n<td>5%</td>\n<td>631</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>We sponsor and/or attend WordCamps.</td>\n<td></td>\n<td></td>\n<td>561</td>\n<td>5%</td>\n<td>579</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>We contribute bug reports and/or patches to WordPress core.</td>\n<td></td>\n<td></td>\n<td>444</td>\n<td>4%</td>\n<td>468</td>\n<td>4%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td></td>\n<td></td>\n<td>98</td>\n<td>1%</td>\n<td>96</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<p><strong>How would you describe the business of your typical client(s)? (2015) / How would you describe the business of your typical client/customer? (2016, 2017)</strong></p>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,154</td>\n<td></td>\n<td>3,317</td>\n<td></td>\n<td>3,498</td>\n<td></td>\n</tr>\n<tr>\n<td>Small business</td>\n<td>6,893</td>\n<td>32%</td>\n<td>2,398</td>\n<td>31%</td>\n<td>2,510</td>\n<td>31%</td>\n</tr>\n<tr>\n<td>Large business or Enterprise</td>\n<td>3,635</td>\n<td>17%</td>\n<td>1,361</td>\n<td>18%</td>\n<td>1,447</td>\n<td>18%</td>\n</tr>\n<tr>\n<td>Non-profit</td>\n<td>2,644</td>\n<td>12%</td>\n<td>934</td>\n<td>12%</td>\n<td>992</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>Individual</td>\n<td>2,600</td>\n<td>12%</td>\n<td>888</td>\n<td>12%</td>\n<td>1,022</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>Education</td>\n<td>2,344</td>\n<td>11%</td>\n<td>854</td>\n<td>11%</td>\n<td>966</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>Website development (sub-contracting)</td>\n<td>2,065</td>\n<td>10%</td>\n<td>637</td>\n<td>8%</td>\n<td>677</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>Government</td>\n<td>1,410</td>\n<td>6%</td>\n<td>524</td>\n<td>7%</td>\n<td>552</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>127</td>\n<td>1%</td>\n<td>66</td>\n<td>1%</td>\n<td>64</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<p><strong>How does your company or organization use WordPress when developing websites? (2015) / When making websites, how does your company or organization use WordPress? (2016, 2017)</strong></p>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,078</td>\n<td></td>\n<td>3,369</td>\n<td></td>\n<td>3,552</td>\n<td></td>\n</tr>\n<tr>\n<td>Mostly as a content management system (CMS)</td>\n<td>6,361</td>\n<td>70%</td>\n<td>2,482</td>\n<td>74%</td>\n<td>2,640</td>\n<td>74%</td>\n</tr>\n<tr>\n<td>About half the time as a blogging platform and half the time as a CMS</td>\n<td>1,222</td>\n<td>13%</td>\n<td>370</td>\n<td>11%</td>\n<td>383</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Mostly as a blogging platform</td>\n<td>721</td>\n<td>8%</td>\n<td>137</td>\n<td>4%</td>\n<td>129</td>\n<td>4%</td>\n</tr>\n<tr>\n<td>Mostly as an application framework</td>\n<td>629</td>\n<td>7%</td>\n<td>303</td>\n<td>9%</td>\n<td>303</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>145</td>\n<td>2%</td>\n<td>78</td>\n<td>2%</td>\n<td>97</td>\n<td>3%</td>\n</tr>\n</tbody>\n</table>\n<h3>How much is your average WordPress site customized from the original WordPress installation?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,054</td>\n<td></td>\n<td>3,302</td>\n<td></td>\n<td>3,473</td>\n<td></td>\n</tr>\n<tr>\n<td>A lot of work has been done, the front end is unrecognizable, but the Dashboard still looks like the usual WordPress interface.</td>\n<td>5,651</td>\n<td>62%</td>\n<td>2,025</td>\n<td>61%</td>\n<td>2,105</td>\n<td>61%</td>\n</tr>\n<tr>\n<td>There&#8217;s a different theme and some plugins have been added.</td>\n<td>2,230</td>\n<td>25%</td>\n<td>799</td>\n<td>24%</td>\n<td>905</td>\n<td>26%</td>\n</tr>\n<tr>\n<td>Not at all, it&#8217;s still pretty much the same as the original download.</td>\n<td>756</td>\n<td>8%</td>\n<td>302</td>\n<td>9%</td>\n<td>298</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>You&#8217;d never know this was a WordPress installation, everything (including the admin) has been customized.</td>\n<td>417</td>\n<td>5%</td>\n<td>177</td>\n<td>5%</td>\n<td>165</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>Roughly how many currently active WordPress sites has your company or organization built?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>8,801</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>200 +</td>\n<td>1,074</td>\n<td>12%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>51 &#8211; 200</td>\n<td>1,721</td>\n<td>20%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>21 &#8211; 50</td>\n<td>1,718</td>\n<td>20%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>11 &#8211; 20</td>\n<td>1,284</td>\n<td>15%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>6 &#8211; 10</td>\n<td>1,109</td>\n<td>13%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>2 &#8211; 5</td>\n<td>1,418</td>\n<td>16%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>1</td>\n<td>390</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>0</td>\n<td>87</td>\n<td>1%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>3,358</td>\n<td></td>\n<td>3,540</td>\n<td></td>\n</tr>\n<tr>\n<td>Thousands.</td>\n<td></td>\n<td></td>\n<td>291</td>\n<td>9%</td>\n<td>331</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Hundreds.</td>\n<td></td>\n<td></td>\n<td>770</td>\n<td>23%</td>\n<td>894</td>\n<td>25%</td>\n</tr>\n<tr>\n<td>Fewer than a hundred.</td>\n<td></td>\n<td></td>\n<td>1,144</td>\n<td>34%</td>\n<td>1,177</td>\n<td>33%</td>\n</tr>\n<tr>\n<td>Just a few, but they are really great.</td>\n<td></td>\n<td></td>\n<td>926</td>\n<td>28%</td>\n<td>896</td>\n<td>25%</td>\n</tr>\n<tr>\n<td>Prefer not to answer.</td>\n<td></td>\n<td></td>\n<td>228</td>\n<td>7%</td>\n<td>242</td>\n<td>7%</td>\n</tr>\n</tbody>\n</table>\n<h3>How many person-hours (of your company&#8217;s work) does the typical site take to complete?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>9,091</td>\n<td></td>\n<td>3,353</td>\n<td></td>\n<td>3,522</td>\n<td></td>\n</tr>\n<tr>\n<td>More than 200</td>\n<td>939</td>\n<td>10%</td>\n<td>309</td>\n<td>9%</td>\n<td>325</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>100 &#8211; 200</td>\n<td>1080</td>\n<td>12%</td>\n<td>329</td>\n<td>10%</td>\n<td>367</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>60 &#8211; 100</td>\n<td>1541</td>\n<td>17%</td>\n<td>527</td>\n<td>16%</td>\n<td>513</td>\n<td>15%</td>\n</tr>\n<tr>\n<td>40 &#8211; 60</td>\n<td>1854</td>\n<td>20%</td>\n<td>583</td>\n<td>17%</td>\n<td>620</td>\n<td>18%</td>\n</tr>\n<tr>\n<td>20 &#8211; 40</td>\n<td>2066</td>\n<td>23%</td>\n<td>691</td>\n<td>21%</td>\n<td>685</td>\n<td>19%</td>\n</tr>\n<tr>\n<td>Fewer than 20</td>\n<td>1611</td>\n<td>18%</td>\n<td>479</td>\n<td>14%</td>\n<td>519</td>\n<td>15%</td>\n</tr>\n<tr>\n<td>Prefer not to answer (2016, 2017)</td>\n<td></td>\n<td></td>\n<td>436</td>\n<td>13%</td>\n<td>493</td>\n<td>14%</td>\n</tr>\n</tbody>\n</table>\n<h3>Roughly what percentage of your company or organization&#8217;s output is based around WordPress (as opposed to other platforms or software)?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Company</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>8,950</td>\n<td></td>\n<td>3,345</td>\n<td></td>\n<td>3,503</td>\n<td></td>\n</tr>\n<tr>\n<td>100 %</td>\n<td>1,089</td>\n<td>12%</td>\n<td>438</td>\n<td>13%</td>\n<td>480</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>90 %</td>\n<td>1,043</td>\n<td>12%</td>\n<td>417</td>\n<td>12%</td>\n<td>459</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>80 %</td>\n<td>955</td>\n<td>11%</td>\n<td>367</td>\n<td>11%</td>\n<td>424</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>70 %</td>\n<td>831</td>\n<td>9%</td>\n<td>305</td>\n<td>9%</td>\n<td>344</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>60 %</td>\n<td>534</td>\n<td>6%</td>\n<td>246</td>\n<td>7%</td>\n<td>226</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>50 %</td>\n<td>973</td>\n<td>11%</td>\n<td>335</td>\n<td>10%</td>\n<td>338</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>40 %</td>\n<td>613</td>\n<td>7%</td>\n<td>245</td>\n<td>7%</td>\n<td>202</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>30 %</td>\n<td>877</td>\n<td>10%</td>\n<td>335</td>\n<td>10%</td>\n<td>310</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>20 %</td>\n<td>806</td>\n<td>9%</td>\n<td>242</td>\n<td>7%</td>\n<td>280</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>10 %</td>\n<td>1,039</td>\n<td>12%</td>\n<td>344</td>\n<td>10%</td>\n<td>348</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>0 %</td>\n<td>190</td>\n<td>2%</td>\n<td>72</td>\n<td>2%</td>\n<td>92</td>\n<td>3%</td>\n</tr>\n</tbody>\n</table>\n<h3>In which of the following ways do you work with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>17,009</td>\n<td></td>\n<td>5,221</td>\n<td></td>\n<td>5,425</td>\n<td></td>\n</tr>\n<tr>\n<td>Build/design and/or maintain websites or blogs for other people, companies, or organizations</td>\n<td>15,342</td>\n<td>34%</td>\n<td>4,795</td>\n<td>34%</td>\n<td>5,064</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Develop or customize themes</td>\n<td>10,549</td>\n<td>24%</td>\n<td>2,997</td>\n<td>21%</td>\n<td>3,021</td>\n<td>20%</td>\n</tr>\n<tr>\n<td>Host websites for customers</td>\n<td>8,142</td>\n<td>18%</td>\n<td>2,466</td>\n<td>17%</td>\n<td>2,728</td>\n<td>18%</td>\n</tr>\n<tr>\n<td>Develop or distribute plugins</td>\n<td>4,125</td>\n<td>9%</td>\n<td>1,395</td>\n<td>10%</td>\n<td>1,416</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Provide educational resources to help others to use WordPress</td>\n<td>3,276</td>\n<td>7%</td>\n<td>1,187</td>\n<td>8%</td>\n<td>1,308</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Sponsor and/or attend WordCamps</td>\n<td>1,559</td>\n<td>4%</td>\n<td>648</td>\n<td>5%</td>\n<td>724</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>Contribute bug reports and/or patches to WordPress core</td>\n<td>1,107</td>\n<td>2%</td>\n<td>381</td>\n<td>3%</td>\n<td>393</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>389</td>\n<td>1%</td>\n<td>243</td>\n<td>2%</td>\n<td>299</td>\n<td>2%</td>\n</tr>\n</tbody>\n</table>\n<h3>How would you describe the business of your typical client(s)?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,863</td>\n<td></td>\n<td>5,151</td>\n<td></td>\n<td>5,353</td>\n<td></td>\n</tr>\n<tr>\n<td>Small business</td>\n<td>14,185</td>\n<td>35%</td>\n<td>4,342</td>\n<td>35%</td>\n<td>4,622</td>\n<td>36%</td>\n</tr>\n<tr>\n<td>Individual</td>\n<td>8,513</td>\n<td>21%</td>\n<td>2,581</td>\n<td>21%</td>\n<td>2,583</td>\n<td>20%</td>\n</tr>\n<tr>\n<td>Non-profit</td>\n<td>6,585</td>\n<td>16%</td>\n<td>2,004</td>\n<td>16%</td>\n<td>2,113</td>\n<td>16%</td>\n</tr>\n<tr>\n<td>Website development (sub-contracting)</td>\n<td>4,301</td>\n<td>11%</td>\n<td>1,258</td>\n<td>10%</td>\n<td>1,216</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Education</td>\n<td>3,458</td>\n<td>8%</td>\n<td>1,049</td>\n<td>8%</td>\n<td>1,139</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Large business or Enterprise</td>\n<td>2,391</td>\n<td>6%</td>\n<td>805</td>\n<td>6%</td>\n<td>857</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>Government</td>\n<td>1,150</td>\n<td>3%</td>\n<td>300</td>\n<td>2%</td>\n<td>329</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>173</td>\n<td>0%</td>\n<td>101</td>\n<td>1%</td>\n<td>99</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>How do you use WordPress in your development?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,768</td>\n<td></td>\n<td>5,145</td>\n<td></td>\n<td>5,372</td>\n<td></td>\n</tr>\n<tr>\n<td>Mostly as a content management system (CMS)</td>\n<td>11,754</td>\n<td>70%</td>\n<td>3,641</td>\n<td>71%</td>\n<td>3,959</td>\n<td>74%</td>\n</tr>\n<tr>\n<td>About half the time as a blogging platform and half the time as a CMS</td>\n<td>2,825</td>\n<td>17%</td>\n<td>812</td>\n<td>16%</td>\n<td>721</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>Mostly as an application framework</td>\n<td>1,012</td>\n<td>6%</td>\n<td>343</td>\n<td>7%</td>\n<td>344</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Mostly as a blogging platform</td>\n<td>992</td>\n<td>6%</td>\n<td>246</td>\n<td>5%</td>\n<td>226</td>\n<td>4%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>185</td>\n<td>1%</td>\n<td>105</td>\n<td>2%</td>\n<td>122</td>\n<td>2%</td>\n</tr>\n</tbody>\n</table>\n<h3>How much is your average WordPress site customized from the original WordPress installation?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,699</td>\n<td></td>\n<td>5,131</td>\n<td></td>\n<td>5,317</td>\n<td></td>\n</tr>\n<tr>\n<td>A lot of work has been done, the front end is unrecognizable, but the Dashboard still looks like the usual WordPress interface.</td>\n<td>9,457</td>\n<td>57%</td>\n<td>2,837</td>\n<td>55%</td>\n<td>2,998</td>\n<td>56%</td>\n</tr>\n<tr>\n<td>There&#8217;s a different theme and some plugins have been added.</td>\n<td>5,526</td>\n<td>33%</td>\n<td>1,694</td>\n<td>33%</td>\n<td>1,781</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Not at all, it&#8217;s still pretty much the same as the original download.</td>\n<td>977</td>\n<td>6%</td>\n<td>341</td>\n<td>7%</td>\n<td>310</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>You&#8217;d never know this was a WordPress installation, everything (including the admin) has been customized.</td>\n<td>739</td>\n<td>4%</td>\n<td>261</td>\n<td>5%</td>\n<td>228</td>\n<td>4%</td>\n</tr>\n</tbody>\n</table>\n<h3>How many currently active WordPress sites have you built? (2015) / Roughly how many currently active WordPress sites have you built? (2016, 2017)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,690</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>200 +</td>\n<td>514</td>\n<td>3%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>51 &#8211; 200</td>\n<td>1,728</td>\n<td>10%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>21 &#8211; 50</td>\n<td>3,000</td>\n<td>18%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>11 &#8211; 20</td>\n<td>3,146</td>\n<td>19%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>6 &#8211; 10</td>\n<td>3,405</td>\n<td>20%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>2 &#8211; 5</td>\n<td>3,838</td>\n<td>23%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>1</td>\n<td>698</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>0</td>\n<td>361</td>\n<td>2%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>5,165</td>\n<td></td>\n<td>5367</td>\n<td></td>\n</tr>\n<tr>\n<td>Thousands.</td>\n<td></td>\n<td></td>\n<td>110</td>\n<td>2%</td>\n<td>104</td>\n<td>2%</td>\n</tr>\n<tr>\n<td>Hundreds.</td>\n<td></td>\n<td></td>\n<td>603</td>\n<td>12%</td>\n<td>713</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>Fewer than a hundred.</td>\n<td></td>\n<td></td>\n<td>2,264</td>\n<td>44%</td>\n<td>2,457</td>\n<td>46%</td>\n</tr>\n<tr>\n<td>Just a few, but they are really great.</td>\n<td></td>\n<td></td>\n<td>1,871</td>\n<td>36%</td>\n<td>1,813</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Prefer not to answer.</td>\n<td></td>\n<td></td>\n<td>319</td>\n<td>6%</td>\n<td>280</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>Roughly what percentage of your working time is spent working with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,658</td>\n<td></td>\n<td>5,039</td>\n<td></td>\n<td>5,241</td>\n<td></td>\n</tr>\n<tr>\n<td>100 %</td>\n<td>949</td>\n<td>6%</td>\n<td>459</td>\n<td>9%</td>\n<td>461</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>90 %</td>\n<td>1,300</td>\n<td>8%</td>\n<td>527</td>\n<td>10%</td>\n<td>540</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>80 %</td>\n<td>1,784</td>\n<td>11%</td>\n<td>637</td>\n<td>13%</td>\n<td>711</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>70 %</td>\n<td>1,850</td>\n<td>11%</td>\n<td>608</td>\n<td>12%</td>\n<td>627</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>60 %</td>\n<td>1,313</td>\n<td>8%</td>\n<td>438</td>\n<td>9%</td>\n<td>465</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>50 %</td>\n<td>2,095</td>\n<td>13%</td>\n<td>612</td>\n<td>12%</td>\n<td>639</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>40 %</td>\n<td>1,438</td>\n<td>9%</td>\n<td>391</td>\n<td>8%</td>\n<td>384</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>30 %</td>\n<td>2,076</td>\n<td>12%</td>\n<td>530</td>\n<td>11%</td>\n<td>511</td>\n<td>10%</td>\n</tr>\n<tr>\n<td>20 %</td>\n<td>1,743</td>\n<td>10%</td>\n<td>445</td>\n<td>9%</td>\n<td>429</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>10 %</td>\n<td>1,819</td>\n<td>11%</td>\n<td>342</td>\n<td>7%</td>\n<td>419</td>\n<td>8%</td>\n</tr>\n<tr>\n<td>0 %</td>\n<td>291</td>\n<td>2%</td>\n<td>52</td>\n<td>1%</td>\n<td>55</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>How many hours of your work does the typical site take to complete? (2015) / How many hours of work does your typical WordPress project take to launch? (2016, 2017)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Freelancer/Hobbyist</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>16,670</td>\n<td></td>\n<td>5,164</td>\n<td></td>\n<td>5,378</td>\n<td></td>\n</tr>\n<tr>\n<td>More than 200</td>\n<td>503</td>\n<td>3%</td>\n<td>222</td>\n<td>4%</td>\n<td>245</td>\n<td>5%</td>\n</tr>\n<tr>\n<td>100 &#8211; 200</td>\n<td>973</td>\n<td>6%</td>\n<td>386</td>\n<td>7%</td>\n<td>393</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>60 &#8211; 100</td>\n<td>2,277</td>\n<td>14%</td>\n<td>788</td>\n<td>15%</td>\n<td>815</td>\n<td>15%</td>\n</tr>\n<tr>\n<td>40 &#8211; 60</td>\n<td>3,896</td>\n<td>23%</td>\n<td>1,153</td>\n<td>22%</td>\n<td>1,216</td>\n<td>23%</td>\n</tr>\n<tr>\n<td>20 &#8211; 40</td>\n<td>6,068</td>\n<td>36%</td>\n<td>1,487</td>\n<td>29%</td>\n<td>1,582</td>\n<td>29%</td>\n</tr>\n<tr>\n<td>Fewer than 20</td>\n<td>2,953</td>\n<td>18%</td>\n<td>712</td>\n<td>14%</td>\n<td>751</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>418</td>\n<td>8%</td>\n<td>376</td>\n<td>7%</td>\n</tr>\n</tbody>\n</table>\n<h3>Which of the following have you done with WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" /> </colgroup>\n</table>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional (Company/Freelancer/Hobbyist)</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>20,687</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I’ve written a theme from scratch.</td>\n<td>11,894</td>\n<td>25%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I’ve written a plugin.</td>\n<td>9,719</td>\n<td>21%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve answered a question in the WordPress forum.</td>\n<td>8,805</td>\n<td>19%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve attended a WordPress meetup.</td>\n<td>4,062</td>\n<td>9%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve submitted a WordPress bug report.</td>\n<td>4,062</td>\n<td>9%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve attended a WordCamp.</td>\n<td>3,571</td>\n<td>8%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve contributed to WordPress documentation.</td>\n<td>1,778</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>1,739</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;ve contributed a WordPress core patch.</td>\n<td>1,055</td>\n<td>2%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n<h3>What&#8217;s the best thing about WordPress?<a href="https://wordpress.org/news/feed/#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>22,718</td>\n<td></td>\n<td>7,891</td>\n<td></td>\n<td>8,267</td>\n<td></td>\n</tr>\n<tr>\n<td>Easy/simple/user-friendly</td>\n<td>9,450</td>\n<td>42%</td>\n<td>3,454</td>\n<td>44%</td>\n<td>3,852</td>\n<td>47%</td>\n</tr>\n<tr>\n<td>Customizable/extensible/modular/plugins/themes</td>\n<td>8,601</td>\n<td>38%</td>\n<td>3,116</td>\n<td>39%</td>\n<td>3,555</td>\n<td>43%</td>\n</tr>\n<tr>\n<td>Community/support/documentation/help</td>\n<td>3,806</td>\n<td>17%</td>\n<td>1,211</td>\n<td>15%</td>\n<td>1,340</td>\n<td>16%</td>\n</tr>\n<tr>\n<td>Free/open/open source</td>\n<td>2,291</td>\n<td>10%</td>\n<td>802</td>\n<td>10%</td>\n<td>908</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Popular/ubiquitous</td>\n<td>249</td>\n<td>1%</td>\n<td>86</td>\n<td>1%</td>\n<td>187</td>\n<td>2%</td>\n</tr>\n</tbody>\n</table>\n<h3> What&#8217;s the most frustrating thing about WordPress?<a href="https://wordpress.org/news/feed/#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>21,144</td>\n<td></td>\n<td>7,294</td>\n<td></td>\n<td>7,691</td>\n<td></td>\n</tr>\n<tr>\n<td>Plugins &amp; themes (abandoned/conflicts/coding standards)</td>\n<td>6,122</td>\n<td>29%</td>\n<td>2,194</td>\n<td>30%</td>\n<td>2,187</td>\n<td>28%</td>\n</tr>\n<tr>\n<td>Security/vulnerabilities/hacks</td>\n<td>2,321</td>\n<td>11%</td>\n<td>712</td>\n<td>10%</td>\n<td>829</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Updates</td>\n<td>1,544</td>\n<td>7%</td>\n<td>422</td>\n<td>6%</td>\n<td>508</td>\n<td>7%</td>\n</tr>\n<tr>\n<td>Nothing/I don&#8217;t know/can&#8217;t think of anything</td>\n<td>1,276</td>\n<td>6%</td>\n<td>344</td>\n<td>5%</td>\n<td>476</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Speed/performance/slow/heavy</td>\n<td>1,196</td>\n<td>6%</td>\n<td>644</td>\n<td>9%</td>\n<td>516</td>\n<td>7%</td>\n</tr>\n</tbody>\n</table>\n<h3>WordPress is as good as, or better than, its main competitors.</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress Professional</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (this question was not asked in the 2015 survey)</td>\n<td></td>\n<td></td>\n<td>8,672</td>\n<td></td>\n<td>9,059</td>\n<td></td>\n</tr>\n<tr>\n<td>Agree</td>\n<td></td>\n<td></td>\n<td>7551</td>\n<td>87%</td>\n<td>7836</td>\n<td>87%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>754</td>\n<td>9%</td>\n<td>795</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Disagree</td>\n<td></td>\n<td></td>\n<td>370</td>\n<td>4%</td>\n<td>428</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h2 id="user">WordPress Users</h2>\n<h3>Which of the following describes how you use WordPress?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>15,169</td>\n<td></td>\n<td>5,043</td>\n<td></td>\n<td>5,521</td>\n<td></td>\n</tr>\n<tr>\n<td>My personal blog (or blogs) uses WordPress.</td>\n<td>9,395</td>\n<td>36%</td>\n<td>3,117</td>\n<td>36%</td>\n<td>3,424</td>\n<td>36%</td>\n</tr>\n<tr>\n<td>My company or organization&#8217;s website is built with WordPress software.</td>\n<td>7,480</td>\n<td>29%</td>\n<td>2,519</td>\n<td>29%</td>\n<td>2,841</td>\n<td>30%</td>\n</tr>\n<tr>\n<td>I have a hobby or side project that has a website built with WordPress.</td>\n<td>6,112</td>\n<td>23%</td>\n<td>1,973</td>\n<td>23%</td>\n<td>2,200</td>\n<td>23%</td>\n</tr>\n<tr>\n<td>I write (or otherwise work) for an online publication that uses WordPress.</td>\n<td>2,329</td>\n<td>9%</td>\n<td>806</td>\n<td>9%</td>\n<td>821</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>872</td>\n<td>3%</td>\n<td>234</td>\n<td>3%</td>\n<td>288</td>\n<td>3%</td>\n</tr>\n</tbody>\n</table>\n<h3>Who installed your WordPress website?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>15,055</td>\n<td></td>\n<td>5,020</td>\n<td></td>\n<td>5,523</td>\n<td></td>\n</tr>\n<tr>\n<td>I did.</td>\n<td>11,216</td>\n<td>66%</td>\n<td>3,659</td>\n<td>73%</td>\n<td>4,129</td>\n<td>75%</td>\n</tr>\n<tr>\n<td>My hosting provider</td>\n<td>2,236</td>\n<td>13%</td>\n<td>667</td>\n<td>13%</td>\n<td>767</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>An external company</td>\n<td>909</td>\n<td>5%</td>\n<td>182</td>\n<td>4%</td>\n<td>178</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>An internal web person/team or a colleague</td>\n<td>874</td>\n<td>5%</td>\n<td>178</td>\n<td>4%</td>\n<td>191</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>A friend or family member</td>\n<td>787</td>\n<td>5%</td>\n<td>192</td>\n<td>4%</td>\n<td>172</td>\n<td>3%</td>\n</tr>\n<tr>\n<td>I don&#8217;t know</td>\n<td>502</td>\n<td>3%</td>\n<td>145</td>\n<td>3%</td>\n<td>87</td>\n<td>2%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>345</td>\n<td>2%</td>\n<td>n/a</td>\n<td>n/a</td>\n<td>n/a</td>\n<td>n/a</td>\n</tr>\n</tbody>\n</table>\n<h3>How much has the site been customized from the original WordPress installation?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>14,789</td>\n<td></td>\n<td>4,997</td>\n<td></td>\n<td>5,494</td>\n<td></td>\n</tr>\n<tr>\n<td>There&#8217;s a different theme and some plugins have been added.</td>\n<td>7,465</td>\n<td>50%</td>\n<td>2,337</td>\n<td>47%</td>\n<td>2,660</td>\n<td>48%</td>\n</tr>\n<tr>\n<td>A lot of work has been done, the site itself is unrecognizable from the original theme, but the Dashboard still looks like the usual WordPress interface.</td>\n<td>4,715</td>\n<td>32%</td>\n<td>1,707</td>\n<td>34%</td>\n<td>1,872</td>\n<td>34%</td>\n</tr>\n<tr>\n<td>Not at all, it&#8217;s still pretty much the same as it was when I started out.</td>\n<td>1,841</td>\n<td>12%</td>\n<td>635</td>\n<td>13%</td>\n<td>673</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>You&#8217;d never know this was a WordPress installation, everything has been customized.</td>\n<td>768</td>\n<td>5%</td>\n<td>321</td>\n<td>6%</td>\n<td>290</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h3>What&#8217;s the best thing about WordPress?<a href="https://wordpress.org/news/feed/#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>14,328</td>\n<td></td>\n<td>4,613</td>\n<td></td>\n<td>5,076</td>\n<td></td>\n</tr>\n<tr>\n<td>Easy/simple/user-friendly</td>\n<td>7,391</td>\n<td>52%</td>\n<td>2,276</td>\n<td>49%</td>\n<td>2,511</td>\n<td>49%</td>\n</tr>\n<tr>\n<td>Customizable/extensible/modular/plugins/themes</td>\n<td>4,219</td>\n<td>29%</td>\n<td>1,569</td>\n<td>34%</td>\n<td>1,632</td>\n<td>32%</td>\n</tr>\n<tr>\n<td>Free/open/open source</td>\n<td>1,586</td>\n<td>11%</td>\n<td>493</td>\n<td>11%</td>\n<td>538</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>Community/support/documentation/help</td>\n<td>1,085</td>\n<td>8%</td>\n<td>388</td>\n<td>8%</td>\n<td>458</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Popular/ubiquitous</td>\n<td>223</td>\n<td>2%</td>\n<td>74</td>\n<td>2%</td>\n<td>48</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>What&#8217;s the most frustrating thing about WordPress?<a href="https://wordpress.org/news/feed/#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td>13,681</td>\n<td></td>\n<td>4,287</td>\n<td></td>\n<td>4,758</td>\n<td></td>\n</tr>\n<tr>\n<td>Plugins &amp; themes (abandoned/conflicts/coding standards)</td>\n<td>2,531</td>\n<td>19%</td>\n<td>1,183</td>\n<td>28%</td>\n<td>1,300</td>\n<td>27%</td>\n</tr>\n<tr>\n<td>Customization/design/look/template</td>\n<td>1,273</td>\n<td>9%</td>\n<td>381</td>\n<td>9%</td>\n<td>408</td>\n<td>9%</td>\n</tr>\n<tr>\n<td>Code/coding/PHP</td>\n<td>931</td>\n<td>7%</td>\n<td>306</td>\n<td>7%</td>\n<td>277</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Updates</td>\n<td>926</td>\n<td>7%</td>\n<td>209</td>\n<td>5%</td>\n<td>296</td>\n<td>6%</td>\n</tr>\n<tr>\n<td>Security/vulnerabilites/hacks</td>\n<td>785</td>\n<td>6%</td>\n<td>255</td>\n<td>6%</td>\n<td>292</td>\n<td>6%</td>\n</tr>\n</tbody>\n</table>\n<h3>WordPress is as good as, or better than, its main competitors.</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: WordPress User</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>5,026</td>\n<td></td>\n<td>5,498</td>\n<td></td>\n</tr>\n<tr>\n<td>Agree</td>\n<td></td>\n<td></td>\n<td>4,038</td>\n<td>80%</td>\n<td>4,462</td>\n<td>81%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>737</td>\n<td>15%</td>\n<td>782</td>\n<td>14%</td>\n</tr>\n<tr>\n<td>Disagree</td>\n<td></td>\n<td></td>\n<td>254</td>\n<td>5%</td>\n<td>255</td>\n<td>5%</td>\n</tr>\n</tbody>\n</table>\n<h2 id="all">All Respondents</h2>\n<h3>Can you (truthfully!) say &#8220;I make my living from WordPress&#8221;?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (combination of all three groups from 2015; this question was not broken out by group in 2016-2017)</td>\n<td>42,236</td>\n<td></td>\n<td>14,906</td>\n<td></td>\n<td>15,616</td>\n<td></td>\n</tr>\n<tr>\n<td>Not really, but I do get some or all of my income as a result of working with WordPress.</td>\n<td>16,607</td>\n<td>39%</td>\n<td>5,408</td>\n<td>36%</td>\n<td>5,702</td>\n<td>37%</td>\n</tr>\n<tr>\n<td>Yes.</td>\n<td>9,635</td>\n<td>23%</td>\n<td>4,791</td>\n<td>32%</td>\n<td>5,033</td>\n<td>32%</td>\n</tr>\n<tr>\n<td>No.</td>\n<td>15,995</td>\n<td>38%</td>\n<td>4,713</td>\n<td>32%</td>\n<td>4,882</td>\n<td>31%</td>\n</tr>\n</tbody>\n</table>\n<h3>Which devices do you access WordPress on?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (combination of all three groups from 2015; this question was not broken out by group in 2016-2017)</td>\n<td>42,433</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Web</td>\n<td>40,503</td>\n<td>95%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Android phone</td>\n<td>15,396</td>\n<td>36%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>iPhone</td>\n<td>12,353</td>\n<td>29%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>iPad</td>\n<td>11,748</td>\n<td>28%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Android tablet</td>\n<td>9,223</td>\n<td>22%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Desktop app, like MarsEdit</td>\n<td>6,018</td>\n<td>14%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td>1837</td>\n<td>4%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (this question was not broken out by group in 2016-2017)</td>\n<td></td>\n<td></td>\n<td>14,840</td>\n<td></td>\n<td>15,597</td>\n<td></td>\n</tr>\n<tr>\n<td>Web browser on a desktop or laptop</td>\n<td></td>\n<td></td>\n<td>14,160</td>\n<td>54%</td>\n<td>15,052</td>\n<td>55%</td>\n</tr>\n<tr>\n<td>Web browser on a mobile device (tablet or phone)</td>\n<td></td>\n<td></td>\n<td>7,952</td>\n<td>30%</td>\n<td>8,248</td>\n<td>30%</td>\n</tr>\n<tr>\n<td>An app on a mobile device (table or phone)</td>\n<td></td>\n<td></td>\n<td>3,309</td>\n<td>13%</td>\n<td>3,311</td>\n<td>12%</td>\n</tr>\n<tr>\n<td>A desktop app like MarsEdit</td>\n<td></td>\n<td></td>\n<td>517</td>\n<td>2%</td>\n<td>498</td>\n<td>2%</td>\n</tr>\n<tr>\n<td>Other Option</td>\n<td></td>\n<td></td>\n<td>282</td>\n<td>1%</td>\n<td>240</td>\n<td>1%</td>\n</tr>\n</tbody>\n</table>\n<h3>WordPress now updates minor &amp; security releases automatically for you. Check all that apply: (question not asked in 2016, 2017)</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="36" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (combination of all three groups)</td>\n<td>39,726</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I love auto-updates.</td>\n<td>17,367</td>\n<td>44%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;d like to see auto-updates for plugins.</td>\n<td>12,796</td>\n<td>32%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Initially, I was nervous about auto updates.</td>\n<td>11,868</td>\n<td>30%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Auto updates still make me nervous.</td>\n<td>10,809</td>\n<td>27%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Auto updates don&#8217;t make me nervous now.</td>\n<td>10,708</td>\n<td>27%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;d like to see auto-updates for themes.</td>\n<td>10,449</td>\n<td>26%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I&#8217;d like to see auto updates for major versions of WordPress.</td>\n<td>10,225</td>\n<td>26%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>This is the first I&#8217;ve heard of auto-updates.</td>\n<td>8,660</td>\n<td>22%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>I hate auto-updates.</td>\n<td>3,293</td>\n<td>8%</td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n<h3>What is your gender?<a href="https://wordpress.org/news/feed/#text">*</a></h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All respondents (This question was not asked in the 2015 survey.)</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>13,953</td>\n<td></td>\n<td>14,680</td>\n<td></td>\n</tr>\n<tr>\n<td>Male</td>\n<td></td>\n<td></td>\n<td>10,978</td>\n<td>78.68%</td>\n<td>11,570</td>\n<td>78.81%</td>\n</tr>\n<tr>\n<td>Female</td>\n<td></td>\n<td></td>\n<td>2,340</td>\n<td>16.77%</td>\n<td>2,511</td>\n<td>21.70%</td>\n</tr>\n<tr>\n<td>Prefer not to answer</td>\n<td></td>\n<td></td>\n<td>601</td>\n<td>4.31%</td>\n<td>562</td>\n<td>3.83%</td>\n</tr>\n<tr>\n<td>Transgender</td>\n<td></td>\n<td></td>\n<td>11</td>\n<td>0.08%</td>\n<td>8</td>\n<td>0.05%</td>\n</tr>\n<tr>\n<td>Nonbinary</td>\n<td></td>\n<td></td>\n<td>8</td>\n<td>0.06%</td>\n<td>17</td>\n<td>0.12%</td>\n</tr>\n<tr>\n<td>Genderqueer</td>\n<td></td>\n<td></td>\n<td>4</td>\n<td>0.03%</td>\n<td>3</td>\n<td>0.02%</td>\n</tr>\n<tr>\n<td>Androgynous</td>\n<td></td>\n<td></td>\n<td>6</td>\n<td>0.04%</td>\n<td>5</td>\n<td>0.03%</td>\n</tr>\n<tr>\n<td>Fluid</td>\n<td></td>\n<td></td>\n<td>3</td>\n<td>0.02%</td>\n<td>4</td>\n<td>0.03%</td>\n</tr>\n<tr>\n<td>Demimale</td>\n<td></td>\n<td></td>\n<td>2</td>\n<td>0.01%</td>\n<td>0</td>\n<td>0</td>\n</tr>\n</tbody>\n</table>\n<h3>Where are you located?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All respondents (This question was not asked in the 2015 survey.)</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses</td>\n<td></td>\n<td></td>\n<td>14,562</td>\n<td></td>\n<td>15,343</td>\n<td></td>\n</tr>\n<tr>\n<td>United States</td>\n<td></td>\n<td></td>\n<td>3,770</td>\n<td>25.89%</td>\n<td>4,067</td>\n<td>26.51%</td>\n</tr>\n<tr>\n<td>India</td>\n<td></td>\n<td></td>\n<td>1,456</td>\n<td>10.00%</td>\n<td>1,424</td>\n<td>9.28%</td>\n</tr>\n<tr>\n<td>United Kingdom</td>\n<td></td>\n<td></td>\n<td>810</td>\n<td>5.56%</td>\n<td>900</td>\n<td>5.87%</td>\n</tr>\n<tr>\n<td>Germany</td>\n<td></td>\n<td></td>\n<td>555</td>\n<td>3.81%</td>\n<td>729</td>\n<td>4.75%</td>\n</tr>\n<tr>\n<td>Canada</td>\n<td></td>\n<td></td>\n<td>511</td>\n<td>3.51%</td>\n<td>599</td>\n<td>3.90%</td>\n</tr>\n<tr>\n<td>Australia</td>\n<td></td>\n<td></td>\n<td>389</td>\n<td>2.67%</td>\n<td>460</td>\n<td>3.00%</td>\n</tr>\n<tr>\n<td>Italy</td>\n<td></td>\n<td></td>\n<td>298</td>\n<td>2.05%</td>\n<td>356</td>\n<td>2.32%</td>\n</tr>\n<tr>\n<td>Netherlands</td>\n<td></td>\n<td></td>\n<td>343</td>\n<td>2.36%</td>\n<td>350</td>\n<td>2.28%</td>\n</tr>\n<tr>\n<td>France</td>\n<td></td>\n<td></td>\n<td>232</td>\n<td>1.59%</td>\n<td>283</td>\n<td>1.84%</td>\n</tr>\n<tr>\n<td>Bangladesh</td>\n<td></td>\n<td></td>\n<td>257</td>\n<td>1.76%</td>\n<td>263</td>\n<td>1.71%</td>\n</tr>\n<tr>\n<td>Spain</td>\n<td></td>\n<td></td>\n<td>271</td>\n<td>1.86%</td>\n<td>252</td>\n<td>1.64%</td>\n</tr>\n<tr>\n<td>Brazil</td>\n<td></td>\n<td></td>\n<td>239</td>\n<td>1.64%</td>\n<td>251</td>\n<td>1.64%</td>\n</tr>\n<tr>\n<td>Pakistan</td>\n<td></td>\n<td></td>\n<td>254</td>\n<td>1.74%</td>\n<td>240</td>\n<td>1.56%</td>\n</tr>\n<tr>\n<td>Indonesia</td>\n<td></td>\n<td></td>\n<td>230</td>\n<td>1.58%</td>\n<td>226</td>\n<td>1.47%</td>\n</tr>\n<tr>\n<td>Iran, Islamic Republic of</td>\n<td></td>\n<td></td>\n<td>190</td>\n<td>1.30%</td>\n<td>173</td>\n<td>1.13%</td>\n</tr>\n<tr>\n<td>Sweden</td>\n<td></td>\n<td></td>\n<td>144</td>\n<td>0.99%</td>\n<td>173</td>\n<td>1.13%</td>\n</tr>\n<tr>\n<td>Nigeria</td>\n<td></td>\n<td></td>\n<td>196</td>\n<td>1.35%</td>\n<td>172</td>\n<td>1.12%</td>\n</tr>\n<tr>\n<td>South Africa</td>\n<td></td>\n<td></td>\n<td>193</td>\n<td>1.33%</td>\n<td>172</td>\n<td>1.12%</td>\n</tr>\n<tr>\n<td>Russian Federation</td>\n<td></td>\n<td></td>\n<td>181</td>\n<td>1.24%</td>\n<td>151</td>\n<td>0.98%</td>\n</tr>\n<tr>\n<td>Poland</td>\n<td></td>\n<td></td>\n<td>129</td>\n<td>0.89%</td>\n<td>137</td>\n<td>0.89%</td>\n</tr>\n<tr>\n<td>Romania</td>\n<td></td>\n<td></td>\n<td>144</td>\n<td>0.99%</td>\n<td>132</td>\n<td>0.86%</td>\n</tr>\n<tr>\n<td>Switzerland</td>\n<td></td>\n<td></td>\n<td>122</td>\n<td>0.84%</td>\n<td>130</td>\n<td>0.85%</td>\n</tr>\n<tr>\n<td>Philippines</td>\n<td></td>\n<td></td>\n<td>92</td>\n<td>0.63%</td>\n<td>125</td>\n<td>0.81%</td>\n</tr>\n<tr>\n<td>China</td>\n<td></td>\n<td></td>\n<td>136</td>\n<td>0.93%</td>\n<td>123</td>\n<td>0.80%</td>\n</tr>\n<tr>\n<td>Austria</td>\n<td></td>\n<td></td>\n<td>89</td>\n<td>0.61%</td>\n<td>122</td>\n<td>0.80%</td>\n</tr>\n<tr>\n<td>Ukraine</td>\n<td></td>\n<td></td>\n<td>105</td>\n<td>0.72%</td>\n<td>118</td>\n<td>0.77%</td>\n</tr>\n<tr>\n<td>Denmark</td>\n<td></td>\n<td></td>\n<td>107</td>\n<td>0.73%</td>\n<td>114</td>\n<td>0.74%</td>\n</tr>\n<tr>\n<td>Greece</td>\n<td></td>\n<td></td>\n<td>120</td>\n<td>0.82%</td>\n<td>114</td>\n<td>0.74%</td>\n</tr>\n<tr>\n<td>Portugal</td>\n<td></td>\n<td></td>\n<td>94</td>\n<td>0.65%</td>\n<td>109</td>\n<td>0.71%</td>\n</tr>\n<tr>\n<td>Vietnam</td>\n<td></td>\n<td></td>\n<td>101</td>\n<td>0.69%</td>\n<td>108</td>\n<td>0.70%</td>\n</tr>\n<tr>\n<td>Mexico</td>\n<td></td>\n<td></td>\n<td>94</td>\n<td>0.65%</td>\n<td>105</td>\n<td>0.68%</td>\n</tr>\n<tr>\n<td>Nepal</td>\n<td></td>\n<td></td>\n<td>76</td>\n<td>0.52%</td>\n<td>97</td>\n<td>0.63%</td>\n</tr>\n<tr>\n<td>Ireland</td>\n<td></td>\n<td></td>\n<td>72</td>\n<td>0.49%</td>\n<td>94</td>\n<td>0.61%</td>\n</tr>\n<tr>\n<td>Israel</td>\n<td></td>\n<td></td>\n<td>78</td>\n<td>0.54%</td>\n<td>94</td>\n<td>0.61%</td>\n</tr>\n<tr>\n<td>New Zealand</td>\n<td></td>\n<td></td>\n<td>77</td>\n<td>0.53%</td>\n<td>91</td>\n<td>0.59%</td>\n</tr>\n<tr>\n<td>Finland</td>\n<td></td>\n<td></td>\n<td>63</td>\n<td>0.43%</td>\n<td>90</td>\n<td>0.59%</td>\n</tr>\n<tr>\n<td>Turkey</td>\n<td></td>\n<td></td>\n<td>91</td>\n<td>0.62%</td>\n<td>86</td>\n<td>0.56%</td>\n</tr>\n<tr>\n<td>Malaysia</td>\n<td></td>\n<td></td>\n<td>91</td>\n<td>0.62%</td>\n<td>81</td>\n<td>0.53%</td>\n</tr>\n<tr>\n<td>Belgium</td>\n<td></td>\n<td></td>\n<td>84</td>\n<td>0.58%</td>\n<td>79</td>\n<td>0.51%</td>\n</tr>\n<tr>\n<td>Norway</td>\n<td></td>\n<td></td>\n<td>66</td>\n<td>0.45%</td>\n<td>79</td>\n<td>0.51%</td>\n</tr>\n<tr>\n<td>Argentina</td>\n<td></td>\n<td></td>\n<td>65</td>\n<td>0.45%</td>\n<td>76</td>\n<td>0.50%</td>\n</tr>\n<tr>\n<td>Bulgaria</td>\n<td></td>\n<td></td>\n<td>74</td>\n<td>0.51%</td>\n<td>72</td>\n<td>0.47%</td>\n</tr>\n<tr>\n<td>Japan</td>\n<td></td>\n<td></td>\n<td>61</td>\n<td>0.42%</td>\n<td>68</td>\n<td>0.44%</td>\n</tr>\n<tr>\n<td>Thailand</td>\n<td></td>\n<td></td>\n<td>69</td>\n<td>0.47%</td>\n<td>67</td>\n<td>0.44%</td>\n</tr>\n<tr>\n<td>Czech Republic</td>\n<td></td>\n<td></td>\n<td>76</td>\n<td>0.52%</td>\n<td>66</td>\n<td>0.43%</td>\n</tr>\n<tr>\n<td>Serbia</td>\n<td></td>\n<td></td>\n<td>89</td>\n<td>0.61%</td>\n<td>63</td>\n<td>0.41%</td>\n</tr>\n<tr>\n<td>Kenya</td>\n<td></td>\n<td></td>\n<td>58</td>\n<td>0.40%</td>\n<td>62</td>\n<td>0.40%</td>\n</tr>\n<tr>\n<td>Colombia</td>\n<td></td>\n<td></td>\n<td>39</td>\n<td>0.27%</td>\n<td>59</td>\n<td>0.38%</td>\n</tr>\n<tr>\n<td>Egypt</td>\n<td></td>\n<td></td>\n<td>40</td>\n<td>0.27%</td>\n<td>52</td>\n<td>0.34%</td>\n</tr>\n</tbody>\n</table>\n<h3>What is your age?</h3>\n<table dir="ltr" border="1" cellspacing="0" cellpadding="0">\n<colgroup>\n<col width="554" />\n<col width="47" />\n<col width="36" />\n<col width="47" />\n<col width="51" />\n<col width="47" />\n<col width="51" /></colgroup>\n<tbody>\n<tr>\n<td></td>\n<td colspan="2" rowspan="1"><strong>2015</strong></td>\n<td colspan="2" rowspan="1"><strong>2016</strong></td>\n<td colspan="2" rowspan="1"><strong>2017</strong></td>\n</tr>\n<tr>\n<td><em>Group: All Respondents</em></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>Number of responses (This question was not asked in 2015.)</td>\n<td></td>\n<td></td>\n<td>14,944</td>\n<td></td>\n<td>15,636</td>\n<td></td>\n</tr>\n<tr>\n<td>60 and over</td>\n<td></td>\n<td></td>\n<td>1,139</td>\n<td>8%</td>\n<td>1,641</td>\n<td>11%</td>\n</tr>\n<tr>\n<td>50-59</td>\n<td></td>\n<td></td>\n<td>1,537</td>\n<td>10%</td>\n<td>1,996</td>\n<td>13%</td>\n</tr>\n<tr>\n<td>40-49</td>\n<td></td>\n<td></td>\n<td>2,205</td>\n<td>15%</td>\n<td>2,643</td>\n<td>17%</td>\n</tr>\n<tr>\n<td>30-39</td>\n<td></td>\n<td></td>\n<td>3,914</td>\n<td>26%</td>\n<td>3,972</td>\n<td>25%</td>\n</tr>\n<tr>\n<td>20-29</td>\n<td></td>\n<td></td>\n<td>5,013</td>\n<td>34%</td>\n<td>4,444</td>\n<td>28%</td>\n</tr>\n<tr>\n<td>Under 20</td>\n<td></td>\n<td></td>\n<td>1142</td>\n<td>8%</td>\n<td>941</td>\n<td>6%</td>\n</tr>\n</tbody>\n</table>\n<p>Thank you to everyone who made time to fill out the survey &#8212; we&#8217;re so happy you use WordPress, and we&#8217;re very grateful that you&#8217;re willing to share your experiences with us! Thanks also to everyone who spread the word about this survey, and to those of you who read all the way to the bottom of this post. <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f609.png" alt="?" class="wp-smiley" /></p>\n<p><small><a id="text"></a>*Text Field Questions: Each survey included some questions that could be answered only by filling out a text field. In the case of the questions &#8220;What is the best thing about WordPress?&#8221; and &#8220;What is the most frustrating thing about WordPress?&#8221; we listed the five most common responses, aggregated when applicable. In the case of the question “What is your gender?” in the 2016 and 2017 surveys, we aggregated responses as best we could. Responses meant to obscure respondents’ gender entirely are aggregated in “prefer not to answer.”</small></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 22 Dec 2017 21:40:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Andrea Middleton";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:71:"Akismet: Version 4.0.2 of the Akismet WordPress Plugin Is Now Available";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"http://blog.akismet.com/?p=1982";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:99:"https://blog.akismet.com/2017/12/18/version-4-0-2-of-the-akismet-wordpress-plugin-is-now-available/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1161:"<p>Version 4.0.2 of <a href="http://wordpress.org/plugins/akismet/">the Akismet plugin for WordPress</a> is now available.</p>\n<p>4.0.2 contains a few helpful changes:</p>\n<ul>\n<li class="p1"><span class="s1">Fixed a bug that could cause Akismet to recheck a comment that has already been manually approved or marked as spam.</span></li>\n<li class="p1"><span class="s1">Fixed a bug that could cause Akismet to claim that some comments are still waiting to be checked when no comments are waiting to be checked.</span></li>\n</ul>\n<p>To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in <a href="http://wordpress.org/plugins/akismet/">the WordPress plugins directory</a>.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/akismet.wordpress.com/1982/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/akismet.wordpress.com/1982/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=blog.akismet.com&blog=116920&post=1982&subd=akismet&ref=&feed=1" width="1" height="1" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 18 Dec 2017 16:56:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Stephane Daury";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:51:"Post Status: Matt Mullenweg State of the Word, 2017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=40186";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:54:"https://poststatus.com/matt-mullenweg-state-word-2017/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6903:"<p>Matt Mullenweg has just finished the 2017 State of the Word address, where he offers the lay of the land for all things WordPress.</p>\n<h3>WordCamp in Nashville</h3>\n<p>This is the first WordCamp US in Nashville. The first two WordCamp US events were held in Philadelphia, following a long run of the primary event of the year being WordCamp San Francisco.</p>\n<p><a href="https://amandagiles.com/">Amanda Giles</a> recited her poem, &#8220;Code is Poetry&#8221; to kick off the event. She then introduced Matt, who started off his talk by thanking the top sponsors for WordCamp US: <a href="https://sitelock.com">SiteLock</a>, <a href="https://woocommerce.com">WooCommerce</a>, <a href="https://bluehost.com">Bluehost</a>, and <a href="https://jetpack.com">Jetpack</a>. I second Matt in thanking these sponsors as well as the other 36 sponsors who help make this event happen while keeping ticket prices so low &#8212; only $40.</p>\n<h3>WordCamps and Meetups</h3>\n<p>WordCamp US makes for the 128th WordCamp of the year, and 40,000 tickets were sold across them. There were more than 1,008 organizers, 2,310 speakers, 1,091 unique sponsors.</p>\n<p>Since adding the meetups to the WordPress News widget, meetup attendance is up more than 30%. I can confirm that I met people at my own home WordCamp who discovered it was happening this way.</p>\n<p><img /></p>\n<p>Last year three charities were chosen to donate to, and eachHack the Hood, the Internet Archive, and Black Girls Code received $15,000 &#8212; more than the original goal.</p>\n<h3>WordPress Foundation donations open</h3>\n<p>With the first step I&#8217;ve seen of Matt opening up the WordPress foundation in any way, he&#8217;s enabled direct donations to the foundation. I look forward to seeing how else this may evolve.</p>\n<h3>Hackerone update</h3>\n<p>52 bugs were resolved through Hackerone, with 39 reward to 46 hackers that were thanked.</p>\n<p><img />The top reporter submitted 9 reports. It&#8217;s been an effective way thus far to resolve WordPress security issues.</p>\n<h3>Updates to WordPress.org</h3>\n<p><img /></p>\n<p>One of the big updates in the last year has been to update non-English versions of WordPress.org, that includes new landing pages in 26 languages.</p>\n<p>Language packs are now supported by 1,166 themes and 2,023 plugins, making WordPress even better for people, no matter what language they prefer it in. The top 10 WordPress plugins have between 19 and 56 translations.</p>\n<h3>Tide</h3>\n<p>Matt spent some time talking about the <a href="https://xwp.co/tide-a-path-to-better-code-across-the-wordpress-ecosystem/">Tide</a> project, which originated from XWP, but was adopted by the WordPress project. Tide runs automated tests against every plugin and theme in the WordPress directory.</p>\n<h3>WordPress Growth Council</h3>\n<p>Matt updated on the WordPress Growth Council, which he admitted has been slow, but says that the fist meeting will be next week.</p>\n<p>The goal of the council is to bring together WordPress advocates together from all over, including commercial companies, to share ideas and find new ways to market and grow WordPress.</p>\n<p>There will be two councils &#8212; an enterprise council, and a consumer council &#8212; in order to effectively serve two primary WordPress audiences.</p>\n<h3>Update on WordPress core focus areas</h3>\n<h4></h4>\n<p>We had two major releases in 2017, <a href="https://poststatus.com/notes/wordpress-4-8-evans/">WordPress 4.8</a> and <a href="https://poststatus.com/wordpress-4-9-tipton/">WordPress 4.9</a>. Gutenberg is slated for WordPress 5.0.</p>\n<p>The was a great deal of work in 2017 has been on Gutenberg, but there have been efforts amongst all three core focus areas.</p>\n<h4>The Customizer</h4>\n<p>The Customizer has had a lot of work done in WordPress 4.8 and 4.9 led by Weston Ruter, Mel Choyce, and Jeff Paul. Weston and Mel joined Matt on stage to talk about these releases.</p>\n<div id="attachment_40194" class="wp-caption aligncenter"><img /><p class="wp-caption-text">Weston Ruter</p></div>\n<div id="attachment_40196" class="wp-caption aligncenter"><img /><p class="wp-caption-text">Mel Choyce</p></div>\n<p>The customizer and Gutenberg have several complimentary goals that will align in 2018.</p>\n<h4>The WordPress REST API</h4>\n<p>Ryan McCue gave a <a href="https://journal.rmccue.io/380/state-of-the-rest-api-2017/">State of the REST API</a> in blog format that&#8217;s worth reading, where he highlights the highs and lows of the REST API since its December 2016 release, including some challenges he believes it faces going forward.</p>\n<p>Matt acknowledged that there is a great deal of room to improve with the REST API.</p>\n<h3>The editor, Gutenberg</h3>\n<p><a href="https://wordpress.org/plugins/gutenberg/">Gutenberg</a> has been a huge focus of WordPress development in 2017. Gutenberg has had 4,302 commits from 100+ contributors. There have been weekly releases and 18 major iterations. You can actually use Gutenberg yourself and use it now.</p>\n<div id="attachment_40195" class="wp-caption alignnone"><img /><p class="wp-caption-text">Matias Ventura</p></div>\n<p>Matias Ventura came to the stage to talk about Gutenberg, including a live demo. Matias walked through how blocks work and the progress that has happened since it started. I was really impressed with the accessibility efforts that have gone into the project.</p>\n<p>Matt also noted that there&#8217;s a <a href="https://wordpress.org/plugins/classic-editor/">classic editor</a> plugin now in the directory, just in case some users aren&#8217;t ready for Gutenberg.</p>\n<h3>Other core updates</h3>\n<p>There were a few updates about other core projects and endeavors.</p>\n<h4>WP-CLI an official WordPress project</h4>\n<p>There have been four major releases with 124 contributors to WP-CLI this year. Lead by Daniel Bachhuber, it is a really amazing way to interact with WordPress.</p>\n<p>It became an official WordPress project this year and has a bright future.</p>\n<h4>No default theme for 2018</h4>\n<p>For the first time since it started with TwentyTen, there won&#8217;t be a new default theme for 2018. This will allow more effort to be put into the block concepts with Gutenberg.</p>\n<h3>Looking forward</h3>\n<p>WordPress has grown another 2%+ this year, now 29.1% of the web, and Matt wants to continue to see growth. He says he&#8217;s keeping his &#8220;lead hat&#8221; on for another year, to see the Gutenberg project all the way through.</p>\n<h4>Three focuses for 2018</h4>\n<p>Matt said he&#8217;s excited to announce three big focuses for the next year around Gutenberg and core development.</p>\n<ul>\n<li>Gutenberg editing</li>\n<li>Gutenberg customization</li>\n<li>Gutenberg theme</li>\n</ul>\n<p>And with that, he&#8217;s ready to take questions.</p>\n<p><em>Photos by <a href="https://wpsessions.com">Brian Richards</a>, for Post Status</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 02 Dec 2017 23:43:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:42;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:34:"BuddyPress: BuddyPress 2018 Survey";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://buddypress.org/?p=269296";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:54:"https://buddypress.org/2017/12/buddypress-2018-survey/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:630:"<p>What would you like BuddyPress to focus on in 2018? The core team has ideas of where BuddyPress can expand on and your input is important to harness the time and resources of an all-volunteer crew.</p>\n<p>The survey will take 10-15 minutes to complete. Be assured that we will not publish your name, email address, nor IP address when we post the results of this survey at BuddyPress.org.</p>\n<p>Thank you for your time and cooperation. Your feedback will help us improve BuddyPress for you.</p>\n<p>=&gt;  <strong><a href="https://mercime.polldaddy.com/s/buddypress-2018-survey">Take the 2018 BuddyPress Survey</a></strong></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 Dec 2017 10:26:07 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"@mercime";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:84:"Post Status: WordPress 4.9, “Tipton”, is released with drafts for the customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=39963";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"https://poststatus.com/wordpress-4-9-tipton/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4801:"<p>WordPress 4.9, &#8220;Tipton&#8221;, <a href="https://wordpress.org/news/2017/11/tipton/">has been released</a>, named after jazz musician Billy Tipton. Approximately 443 contributors took part in the development of WordPress 4.9; congratulations to 185 of these contributors for their first ever contribution. 188 new enhancements or features were added in WordPress 4.9. The <a href="https://make.wordpress.org/core/4-9/">release cycle</a> was co-lead by <a href="https://twitter.com/melchoyce">Mel Choyce</a> and <a href="https://twitter.com/westonruter">Weston Ruter</a>. Check out <a href="https://choycedesign.com/2017/10/27/whats-coming-in-wordpress-4-9/">Mel&#8217;s post</a> about 4.9 as well.</p>\n<p>There are several significant features in WordPress 4.9, primarily around improvements to the customizer experience and editing code. In addition to the rundown of items here, listen to the podcast that I published with WordPress project lead and co-founder <a href="https://poststatus.com/interview-matt-mullenweg-wordpress-ecosystem-draft-podcast/">Matt Mullenweg</a>.</p>\n<p>The Gutenberg editor project has been running simultaneously to the WordPress 4.9 process (and the 4.8 one before that), and is one of the things Matt and I talked about yesterday &#8212; in regard to how the projects running simultaneously have gone.</p>\n<p>The team has done a great job doing feature descriptions for WordPress 4.9, thankfully, so there isn&#8217;t a ton you need to hear from me there. But I would like to highlight a couple of my favorite things.</p>\n<h3>Customizer improvements for site editing</h3>\n<p>By far, the most useful component of WordPress 4.9 for me is the customizer improvements for drafting and scheduling changes.</p>\n<p>Most of the features are things we&#8217;ve grown to enjoy in posts themselves: drafting, scheduling, locking (when someone else is actively editing), preview links (not actually in core for posts, maybe this is a step!). These features make collaborative and iterative site editing a much nicer experience.</p>\n<p>I just spent time with a friend who was asking me how to make changes to their site but only in preview mode, and I really believe this will be an impactful feature for every day WordPress users.</p>\n<h3>Gallery widget and text widget enhancements</h3>\n<p>Widgets are one of the first things a new site owner interacts with. The gallery widget makes for an easy to use enhancement to a site, for a common request. It operates much like galleries in regular WordPress, but for sidebars.</p>\n<p>The text widget enhancements allow for a richer text widget experience using the media button, a huge improvement over what has existed for a long time. WordPress 4.8 brought an image widget, but the media button in the text widget gives someone more control over what goes around media, so a full call to action can be created in the text widget. I like this practical step.</p>\n<h3>Code editing</h3>\n<p>Code editing is one of those things I&#8217;d rather not exist in WordPress. I would call it a last resort option for site customization. However, we&#8217;ve always had it in WordPress, and it&#8217;s always been a danger. It&#8217;s made it easy for a user to white screen their site, or enable hackers with the wrong level of access to sneak in malicious code.</p>\n<p>However, now at least the file editor prevents users from doing the worst and bricking their sites. A syntax checking library called CodeMirror, has been added to the file editor so that more sites are protected. While I still wouldn&#8217;t recommend most people go this route, it&#8217;s the right thing to do if the feature is to be kept.</p>\n<h3>A solid stepping stone to Gutenberg</h3>\n<p><a href="https://wordpress.org/news/2017/11/tipton/">WordPress 4.9</a> is the second core release this year, since moving to a feature release cycle after WordPress US last December. I talked more about how that&#8217;s gone in my interview with Matt, as well as progress on the Gutenberg initiative.</p>\n<p>Some of the features in 4.9 will aid in the shift to a block-driven mindset for WordPress content creation. Others were simply ready to go. I think this is a positive release and I&#8217;m impressed by the team that has put WordPress 4.9 together.</p>\n<p>For links to all changes, I highly suggest you check out the <a href="https://make.wordpress.org/core/2017/11/07/wordpress-4-9-field-guide/">field guide</a>, which highlights each 4.9 project, and links to in-depth overviews of those features, including references to specific tickets involved. You can also check out all posts <a href="https://make.wordpress.org/core/tag/4.9+dev-notes/">tagged for WordPress 4.9</a> on the Make Core blog.</p>\n<p>Congratulations to everyone involved, and happy publishing.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Nov 2017 01:17:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:44;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:71:"Akismet: Version 4.0.1 of the Akismet WordPress Plugin Is Now Available";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"http://blog.akismet.com/?p=1978";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:67:"https://blog.akismet.com/2017/11/06/akismet-wordpress-plugin-4-0-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1232:"<p>Version 4.0.1 of <a href="http://wordpress.org/plugins/akismet/">the Akismet plugin for WordPress</a> is now available.</p>\n<p>4.0.1 contains a few helpful changes:</p>\n<ul>\n<li>We fixed a bug that could prevent some sites from connecting Akismet using an existing Jetpack connection.</li>\n<li>We added some code to ensure that any pending Akismet-related events are unscheduled if (heaven forbid) the plugin is deactivated.</li>\n<li>Some of the Akismet JavaScript is now run asynchronously in order to increase the speed with which your pages will appear to load.</li>\n</ul>\n<p>Pretty good, right?  To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in <a href="http://wordpress.org/plugins/akismet/">the WordPress plugins directory</a>.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/akismet.wordpress.com/1978/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/akismet.wordpress.com/1978/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=blog.akismet.com&blog=116920&post=1978&subd=akismet&ref=&feed=1" width="1" height="1" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 06 Nov 2017 20:29:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Christopher Finke";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:45;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:61:"BuddyPress: BuddyPress 2.9.2 Security and Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://buddypress.org/?p=268770";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:81:"https://buddypress.org/2017/11/buddypress-2-9-2-security-and-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1580:"<p>BuddyPress 2.9.2 is now available. This is a security and maintenance release. We strongly encourage all BuddyPress sites to upgrade as soon as possible.</p>\n<p>The 2.9.2 release addresses five security issues:</p>\n<ul>\n<li>A Cross Site Request Forgery (CSRF) vulnerability was fixed in the interface used by admins to perform certain actions related to sitewide notices. Reported by <a href="https://hackerone.com/jdgrimes">J.D. Grimes</a>.</li>\n<li>Some uses of serialized data were judged to need hardening. Reported by <a href="https://profiles.wordpress.org/johnjamesjacoby/">John James Jacoby</a> of the BuddyPress security team.</li>\n<li>An open redirect was fixed on the user edit screens. Reported by <a href="https://hackerone.com/ysx">Yasin Soliman (ysx)</a>.</li>\n<li>An unauthorized information disclosure vulnerability was fixed in an AJAX handler. Reported by <a href="https://hackerone.com/jdgrimes">J.D. Grimes</a>.</li>\n<li>A Cross Site Scripting (XSS) vulnerability was fixed in the avatar upload interface. Reported by <a href="https://dk.linkedin.com/in/skansing">Ronnie Skansing</a>.</li>\n</ul>\n<p>These vulnerabilities were reported privately to the BuddyPress team, in accordance with <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/">WordPress&#8217;s security policies</a>. Our thanks to all reporters for practicing coordinated disclosure.</p>\n<p>In addition, 2.9.2 includes a change that improves compatibility with the upcoming WordPress 4.9 release, by removing the call to a newly deprecated hook.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Nov 2017 16:30:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Boone Gorges";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:39:"Donncha: Writing WP Super Cache Plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"https://odd.blog/?p=89500474";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"https://odd.blog/2017/10/25/writing-wp-super-cache-plugins/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3478:"<p>WP Super Cache is a full page caching plugin for WordPress. When a page is cached almost all of WordPress is skipped and the page is sent to the browser with the minimum amount of code executed. This makes the page load much faster.</p>\n<p>Unfortunately if you want to run code on every page load you&#8217;re out of luck as regular WordPress plugins are not loaded or executed. You&#8217;ll need to write a WP Super Cache plugin. This short introduction will not teach you how to write plugins but the example plugins that ship with WP Super Cache will get you a long way towards understanding how they work.</p>\n<p><img /></p>\n<p>WP Super Cache ships with some example plugins in wp-super-cache/plugins/. Some of them even do useful tasks like help with domain mapping and Jetpack integration. There&#8217;s one called &#8220;awaitingmoderation.php&#8221; which removes the text &#8220;Your comment is awaiting moderation.&#8221; when someone writes a moderated comment.<br />\nThere&#8217;s also dynamic-cache-test.php which is a complicated beast but it&#8217;s heavily commented. It allows you to add template tags to your site that are replaced when the cached page is loaded.</p>\n<p>Before you get started writing a plugin you should be aware that you should <em>not</em> use the wp-super-cache/plugins/ directory. Every time WP Super Cache is updated this directory is deleted. So, edit your wp-config.php and set <code>$wp_cache_plugins_dir</code> to another directory where you&#8217;ll put your plugin.</p>\n<p>These plugins run before most of WordPress has loaded. That means you can&#8217;t rely on some of the nice features of WordPress such as filters and actions. However, WP Super Cache has it&#8217;s own action/filter system that is similar to actions and filters in WordPress:</p>\n<ul>\n<li>add_cacheaction( $action, $func )</li>\n<li>do_cacheaction( $action, $value = &#8221; )</li>\n</ul>\n<p>A cacheaction is also a filter. If you hook on to a cache action that has a parameter, you must return that parameter at the end of the function like you would with a WordPress filter.</p>\n<p><img /></p>\n<p>If you need to hook into a WordPress filter use the imaginatively named cache action &#8220;add_cacheaction&#8221;. That runs on &#8220;init&#8221; so the function that is executed can use <code>add_action()</code> or <code>add_filter()</code>. You can see this in action in the plugins/dynamic-cache-test.php or plugins/awaitingmoderation.php scripts.</p>\n<p>Two very useful filters are the WordPress filter, &#8220;wpsupercache_buffer&#8221; (in wp-cache-phase2.php) that is used to modify the page before it is <em>cached</em> and the cache action &#8220;wpsc_cachedata&#8221; (in wp-cache-phase1.php) is used to modify the cached page just before it&#8217;s <em>served</em>.</p>\n\n<p><strong>Related Posts</strong><ul><li> <a href="https://odd.blog/2008/10/24/wp-super-cache-084-the-garbage-collector/" rel="bookmark" title="Permanent Link: WP Super Cache 0.8.4, the garbage collector">WP Super Cache 0.8.4, the garbage collector</a></li><li> <a href="https://odd.blog/2010/02/08/wp-super-cache-099/" rel="bookmark" title="Permanent Link: WP Super Cache 0.9.9">WP Super Cache 0.9.9</a></li><li> <a href="https://odd.blog/2009/07/17/wp-super-cache-0-9-5/" rel="bookmark" title="Permanent Link: WP Super Cache 0.9.5">WP Super Cache 0.9.5</a></li></ul></p>\n<p><a href="https://odd.blog/2017/10/25/writing-wp-super-cache-plugins/" rel="nofollow">Source</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 25 Oct 2017 16:21:28 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Donncha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:47;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"bbPress: bbPress 2.5.14";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://bbpress.org/?p=186831";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:48:"https://bbpress.org/blog/2017/09/bbpress-2-5-14/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:710:"<p>Today we are releasing bbPress 2.5.14, which fixes a few small bugs we&#8217;ve noticed since 2.5.13 was released, in particular we&#8217;ve fixed some incompatibilities when using PHP 7.1, an unexpected debug notice with the Topics &amp; Replies widgets, and improved validation and sanitization of database properties with the forum converter.</p>\n<p>Also, remember that since bbPress 2.5.12, the minimum WordPress version allowed is 4.7. If you need to use a previous version of WordPress, you will want to continue to use 2.5.11.</p>\n<p>bbPress 2.6 is still in the release candidate phase while we tie up some loose ends across WordPress.org, but I&#8217;ll let you know when it&#8217;s ready to go!</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Sep 2017 19:39:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Stephen Edgar";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:21:"Dougal Campbell: Bugs";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"http://dougal.gunters.org/?p=81413";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:48:"http://dougal.gunters.org/blog/2017/08/29/81413/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:550:"<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">I seem to have a knack for finding obscure edge-case bugs in WordPress. <a href="https://twitter.com/hashtag/wordpress?src=hash">#wordpress</a> <a href="https://twitter.com/hashtag/oembed?src=hash">#oembed</a> <a href="https://t.co/aucCSDb76H">https://t.co/aucCSDb76H</a></p>\n<p>&mdash; Dougal Campbell (@dougal) <a href="https://twitter.com/dougal/status/902299942701674497">August 28, 2017</a></p></blockquote>\n<p></p>\n<p>&nbsp;</p>\n<div class="yarpp-related-rss yarpp-related-none">\n</div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 29 Aug 2017 15:53:05 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Dougal Campbell";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:49;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:43:"Lorelle on WP: WordPress School: Shortcodes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:37:"http://lorelle.wordpress.com/?p=14325";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://lorelle.wordpress.com/2017/08/18/wordpress-school-shortcodes/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:12916:"<p><a href="https://lorelle.wordpress.com/category/wordpress/wordpress-school/" title="WordPress School taught by Lorelle VanFossen."><img /></a></p>\n<p>WordPress shortcodes are abbreviated code placed into the WordPress Visual or Text Editors that expands into a larger code structure. As we continue with <a href="https://lorelle.wordpress.com/classes-and-workshops/wordpress-school/" title="WordPress School « Lorelle on WordPress">Lorelle&#8217;s WordPress School free online course</a>, it&#8217;s time to explore the basics of WordPress shortcodes.</p>\n<p>The following is the embed code for a Google Map, pointing to one of my favorite local museums, <a href="http://ricenorthwestmuseum.com/">The Rice Northwest Rocks and Minerals Museum</a> in Hillsboro, Oregon:</p>\n<p><code>&lt;a href="https&#058;&#047;&#047;www&#046;google.com/maps/embed?pb=!1m18!1m12!1m3!1d2792.809130780463!2d-122.94987648443889!3d45.57427677910247!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x54950456e76e254b%3A0xdfad5d11bde5b6cc!2s26385+NW+Groveland+Dr%2C+Hillsboro%2C+OR+97124!5e0!3m2!1sen!2sus!4v1502560000052"&gt;https&#058;&#047;&#047;www&#046;google.com/maps/embed?pb=!1m18!1m12!1m3!1d2792.809130780463!2d-122.94987648443889!3d45.57427677910247!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x54950456e76e254b%3A0xdfad5d11bde5b6cc!2s26385+NW+Groveland+Dr%2C+Hillsboro%2C+OR+97124!5e0!3m2!1sen!2sus!4v1502560000052&lt;/a&gt;</code></p>\n<p>When the post or Page is saved, WordPress.com automatically converts it to the embed code for Google Maps like this:</p>\n<p><code>&#091;googlemaps https&#058;&#047;&#047;www&#046;google&#046;com/maps/embed?pb=!1m18!1m12!1m3!1d2792.809130780463!2d-122.94987648443889!3d45.57427677910247!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x54950456e76e254b%3A0xdfad5d11bde5b6cc!2s26385+NW+Groveland+Dr%2C+Hillsboro%2C+OR+97124!5e0!3m2!1sen!2sus!4v1502560000052&amp;w=600&amp;h=450]</code></p>\n<p>This is what you see in your Visual or Text/HTML editors. Doesn&#8217;t look like a map, yet, does it? </p>\n<p>When the post is previewed or published, you will see the map like this:</p>\n<div class="googlemaps"></div>\n<p>The map is not a screenshot. It is interactive. Zoom in and out and move around on the map. The <a href="https://en.support.wordpress.com/google-maps/" title="Google Maps — Support — WordPress.com">Google Maps shortcode</a> taps into the Google Maps API allowing a live section of the map to be embedded on your site to help people find locations and directions. </p>\n<p>Google Maps are a great way of providing instructions to the location of a store or company on a Contact web page. They are also fun to embed in a post about a favorite park, hike, fishing hole, vacation spot, or even create a custom map that charts your travels, hikes, or a specific route for shopping or exploring. </p>\n<p><strong>NOTE:</strong> <em>Google Map embeds are tricky. You need to search for the exact address and use that embed code. If you search for a business name, you may get an invalid server request from Google Maps. Also note that WordPress.com has made it easier to use shortcodes by skipping the extra code and converting links and embed codes automatically to shortcodes. This may require saving your post as a draft twice before you can see the results on the front end preview of the post or Page.</em></p>\n<p>Shortcodes allow the user to add content and functionality to a WordPress site without knowing extensive code or digging into the programming of a WordPress Theme or Plugin. With the shortcut of a shortcode, WordPress users may add all sorts of customization features to their site.</p>\n<p>There are a variety of shortcodes in the core of WordPress. WordPress Themes have the ability to enable or disable these, and add more, as do WordPress Plugins.</p>\n<p>Let&#8217;s experiment with the <a title="Archives Shortcode &mdash; Support &mdash; WordPress.com" href="http://en.support.wordpress.com/archives-shortcode/">Archives Shortcode</a>.</p>\n<ol>\n<li>Add a New Page to your site. Title it &#8220;Site Map&#8221; or &#8220;Archives.&#8221;</li>\n<li>Type in <code>&#091;archives]</code>.</li>\n<li>Preview, then publish the post when ready to see a listing of all of the published posts on your site in a list.</li>\n</ol>\n<p>Check out my <a href="https://lorelle.wordpress.com/site-map/" title="Site Map « Lorelle on WordPress">site map</a> as an example of what&#8217;s possible. </p>\n<h3>What You Need to Know About WordPress Shortcodes</h3>\n<p>Shortcodes come with WordPress out of the box, and also with WordPress Themes and Plugins. These snippets of code allow the user to add functionality to their site without touching the code. </p>\n<p>The PHP code that enables the functionality, and adds the ability to use the abbreviated code to generate that functionality on the site, is called a <code>function</code>. </p>\n<p>At its core, this is the function found to generate all WordPress Shortcodes:</p>\n<pre class="brush: xml; title: ; notranslate">//[foobar]\nfunction foobar_func( $atts ){\n	return "foo and bar";\n}\nadd_shortcode( ''foobar'', ''foobar_func'' );</pre>\n<p>The attributes, represented in this abbreviated version by <code>$atts</code>, are the instructions as to what the shortcode is to do.</p>\n<p>In the expanded form with functionality, I&#8217;ve called the shortcode &#8220;elephant&#8221; and set up two attribute values, &#8220;trumpet loudly&#8221; and &#8220;stomp.&#8221; </p>\n<pre class="brush: xml; title: ; notranslate">// [elephant foo="foo-value"]\nfunction elephant_func( $atts ) {\n    $a = shortcode_atts( array(\n        ''foo'' =&gt; ''trumpet loudly'',\n        ''bar'' =&gt; ''stomp'',\n    ), $atts );\n\n    return "foo = {$a[''foo'']}";\n}\nadd_shortcode( ''elephant'', ''elephant_func'' );</pre>\n<p>Depending upon what &#8220;foo&#8221; and &#8220;bar&#8221; represent, the results would be &#8220;trumpet loudly&#8221; and &#8220;stomp.&#8221; What these represent are HTML code, modifications to HTML code, and initiates the programming such as generating a list of all the posts you&#8217;ve published as an archive list.</p>\n<p>Right now, you aren&#8217;t at the stage where you can program shortcodes and add them to WordPress Themes or create WordPress Plugins, so I&#8217;m not going to dive into these much deeper. You need to learn how these work and how to use them on your site, and the more you use them, the better feel you will have for what a shortcode can do on your site. </p>\n<p>WordPress.com offers a <a href="https://en.support.wordpress.com/category/shortcodes/" title="Support — WordPress.com">wide range of shortcodes</a> to add functionality to your site. To learn about how to use these, see <a title="Shortcodes &mdash; Support &mdash; WordPress.com" href="http://en.support.wordpress.com/shortcodes/">Shortcodes &mdash; Support</a>. </p>\n<p>Here are some examples of shortcodes to experiment with on WordPress.com.</p>\n<ul>\n<li><a href="https://en.support.wordpress.com/videos/youtube/" title="YouTube — Support — WordPress.com">YouTube Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/audio/" title="Audio — Support — WordPress.com">Audio Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/soundcloud-audio-player/">SoundCloud Audio Player Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/gallery/" title="Galleries and Slideshows — Support — WordPress.com">Galleries and Slideshows Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/instagram/" title="Instagram — Support — WordPress.com">Instagram Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/archives-shortcode/" title="Create an Archive using the Archives Shortcode — Support — WordPress.com">Archives Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/blog-subscription-shortcode/" title="Blog Subscription Shortcode — Support — WordPress.com">Blog Subscription Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/forms/contact-form/" title="Contact Form — Support — WordPress.com">Contact Form Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/google-maps/" title="Google Maps — Support — WordPress.com">Google Maps Shortcode</a></li>\n<li><a href="https://en.support.wordpress.com/recipes/" title="Recipes — Support — WordPress.com">Recipes Shortcode</a></li>\n</ul>\n<h4>More Information on WordPress Shortcodes</h4>\n<ul>\n<li><a title="Shortcodes &mdash; Support &mdash; WordPress.com" href="http://en.support.wordpress.com/shortcodes/">Shortcodes &#8211; Support &#8211; WordPress.com</a></li>\n<li><a title="Shortcodes &mdash; Support &mdash; WordPress.com" href="http://en.support.wordpress.com/shortcodes/">List of Shortcodes available for WordPress.com sites</a></li>\n<li><a title="Shortcode &laquo; WordPress Codex" href="http://codex.wordpress.org/Shortcode">Shortcode &#8211; WordPress Codex</a></li>\n<li><a title="Support &mdash; WordPress.com" href="http://en.support.wordpress.com/category/shortcodes/">Shortcodes for WordPress.com</a></li>\n<li><a title="Gallery Shortcode &laquo; WordPress Codex" href="http://codex.wordpress.org/Gallery_Shortcode">Gallery Shortcode &#8211; WordPress Codex</a></li>\n<li><a href="https://www.smashingmagazine.com/2012/05/wordpress-shortcodes-complete-guide/" title="WordPress Shortcodes: A Complete Guide – Smashing Magazine">WordPress Shortcodes: A Complete Guide – Smashing Magazine</a></li>\n<li><a href="http://www.wpbeginner.com/wp-tutorials/how-to-add-a-shortcode-in-wordpress/" title="How to Add A Shortcode in WordPress?">How to Add A Shortcode in WordPress? &#8211; WPBeginner</a></li>\n<li><a href="http://www.wpbeginner.com/beginners-guide/7-essential-tips-for-using-shortcodes-in-wordpress/" title="7 Essential Tips for Using Shortcodes in WordPress">7 Essential Tips for Using Shortcodes in WordPress &#8211; WPBeginner</a></li>\n<li><a href="https://code.tutsplus.com/articles/getting-started-with-wordpress-shortcodes--wp-21197" title="Getting Started With WordPress Shortcodes">Getting Started With WordPress Shortcodes &#8211; Envatotuts+</a></li>\n</ul>\n<h3>Assignment</h3>\n<p><img />Your assignment in these WordPress School exercises is to experiment with WordPress shortcodes, specifically the ones available on WordPress.com. </p>\n<p>I&#8217;ve listed some examples of shortcodes on WordPress.com above, and you may find more in the <a href="https://en.support.wordpress.com/category/shortcodes/" title="Support — WordPress.com">WordPress.com list of Shortcodes</a>.</p>\n<p>Your assignment is to use shortcodes to add features to your site. </p>\n<ul>\n<li>Create a Page called &#8220;Site Map&#8221; or &#8220;Archives&#8221; and add an archive list shortcode.</li>\n<li>Add a Google Map to a post or Page using the Google Maps shortcode.</li>\n<li>Add a gallery to a post or Page with the gallery shortcode, testing the various options (parameters) to get the look and feel you like best.</li>\n<li>Add a recipe to a post using the recipe shortcode.</li>\n<li>Find another shortcode with a variety of features to experiment with. See how many ways you can change the look and feel of the content. If you wish, blog about your discoveries with screenshots or examples in the post. Let us know about it in the comments below so we can come inspect your work.</li>\n</ul>\n<p><em>This is a tutorial from <a href="https://lorelle.wordpress.com/classes-and-workshops/wordpress-school/" title="WordPress School « Lorelle on WordPress">Lorelle&#8217;s WordPress School</a>. For more information, and to join this free, year-long, online WordPress School, see:</em></p>\n<ul>\n<li><a href="https://lorelle.wordpress.com/2015/01/24/welcome-to-lorelles-wordpress-school/" title="Welcome to Lorelle’s WordPress School « Lorelle on WordPress">Lorelle&#8217;s WordPress School Introduction</a></li>\n<li><a href="https://lorelle.wordpress.com/classes-and-workshops/wordpress-school/" title="WordPress School « Lorelle on WordPress">Lorelle&#8217;s WordPress School Description</a></li>\n<li><a href="https://lorelle.wordpress.com/classes-and-workshops/wordpress-school/tutorials/" title="Tutorials « Lorelle on WordPress">WordPress School Tutorials List</a></li>\n<li><a href="https://plus.google.com/u/0/communities/115251582756616355670" title="WordPress School Google+ Community">WordPress School Google+ Community</a></li>\n<li><a href="https://lorelle.wordpress.com/2015/01/12/wordpress-publishing-checklist/" title="WordPress Publishing Checklist">WordPress Publishing Checklist</a></li>\n<li><a href="https://lorelle.wordpress.com/classes-and-workshops/wordpress-school/feedback-and-criticism/" title="How to Give Feedback and Criticism - Lorelle''s WordPress School.">How to Give Feedback and Criticism</a></li>\n</ul>\n<div class="sig">\n<p><img src="https://lorelle.files.wordpress.com/2006/08/sig.gif" alt="" /></p>\n<hr /> </div>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Aug 2017 11:02:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Lorelle VanFossen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Mon, 05 Feb 2018 21:50:18 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Mon, 05 Feb 2018 21:30:34 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 2";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20130911040210";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(9005, '_transient_timeout_feed_b9388c83948825c1edaef0d856b7b109', '1517910621', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(9006, '_transient_feed_b9388c83948825c1edaef0d856b7b109', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:29:"Popular — WordPress Plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wordpress.org/plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:57:"Plugins extend and expand the functionality of WordPress.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:34:"\n	Mon, 05 Feb 2018 21:38:20 +0000	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"en-US";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:40:"https://wordpress.org/?v=5.0-alpha-42649";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:10:{i:0;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"Contact Form 7";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"https://wordpress.org/plugins/contact-form-7/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/plugins/contact-form-7/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2007 12:43:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wordpress.org/plugins-wp/contact-form-7/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:54:"Just another contact form plugin. Simple but flexible.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Takayuki Miyoshi";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4993:"<p><!--section=description--></p>\n<p>Contact Form 7 can manage multiple contact forms, plus you can customize the form and the mail contents flexibly with simple markup. The form supports Ajax-powered submitting, CAPTCHA, Akismet spam filtering and so on.</p>\n<h4>Docs &amp; Support</h4>\n<p>You can find <a href="https://contactform7.com/docs/" rel="nofollow">docs</a>, <a href="https://contactform7.com/faq/" rel="nofollow">FAQ</a> and more detailed information about Contact Form 7 on <a href="https://contactform7.com/" rel="nofollow">contactform7.com</a>. If you were unable to find the answer to your question on the FAQ or in any of the documentation, you should check the <a href="https://wordpress.org/support/plugin/contact-form-7/" rel="nofollow">support forum</a> on WordPress.org. If you can&#8217;t locate any topics that pertain to your particular issue, post a new topic for it.</p>\n<h4>Contact Form 7 Needs Your Support</h4>\n<p>It is hard to continue development and support for this free plugin without contributions from users like you. If you enjoy using Contact Form 7 and find it useful, please consider <a href="https://contactform7.com/donate/" rel="nofollow"><strong>making a donation</strong></a>. Your donation will help encourage and support the plugin&#8217;s continued development and better user support.</p>\n<h4>Recommended Plugins</h4>\n<p>The following plugins are recommended for Contact Form 7 users:</p>\n<ul>\n<li><a href="https://wordpress.org/plugins/flamingo/">Flamingo</a> by Takayuki Miyoshi &#8211; With Flamingo, you can save submitted messages via contact forms in the database.</li>\n<li><a href="https://wordpress.org/plugins/bogo/">Bogo</a> by Takayuki Miyoshi &#8211; Bogo is a straight-forward multilingual plugin that doesn&#8217;t cause headaches.</li>\n</ul>\n<h4>Translations</h4>\n<p>You can <a href="https://contactform7.com/translating-contact-form-7/" rel="nofollow">translate Contact Form 7</a> on <a href="https://translate.wordpress.org/projects/wp-plugins/contact-form-7" rel="nofollow"><strong>translate.wordpress.org</strong></a>.</p>\n<p><!--section=installation--></p>\n<ol>\n<li>Upload the entire <code>contact-form-7</code> folder to the <code>/wp-content/plugins/</code> directory.</li>\n<li>Activate the plugin through the &#8216;Plugins&#8217; menu in WordPress.</li>\n</ol>\n<p>You will find &#8216;Contact&#8217; menu in your WordPress admin panel.</p>\n<p>For basic usage, you can also have a look at the <a href="https://contactform7.com/" rel="nofollow">plugin web site</a>.</p>\n<p><!--section=faq--></p>\n<p>Do you have questions or issues with Contact Form 7? Use these support channels appropriately.</p>\n<ol>\n<li><a href="https://contactform7.com/docs/" rel="nofollow">Docs</a></li>\n<li><a href="https://contactform7.com/faq/" rel="nofollow">FAQ</a></li>\n<li><a href="https://wordpress.org/support/plugin/contact-form-7/" rel="nofollow">Support Forum</a></li>\n</ol>\n<p><a href="https://contactform7.com/support/" rel="nofollow">Support</a></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<ol>\n<li>Upload the entire <code>contact-form-7</code> folder to the <code>/wp-content/plugins/</code> directory.</li>\n<li>Activate the plugin through the &#8216;Plugins&#8217; menu in WordPress.</li>\n</ol>\n<p>You will find &#8216;Contact&#8217; menu in your WordPress admin panel.</p>\n<p>For basic usage, you can also have a look at the <a href="https://contactform7.com/" rel="nofollow">plugin web site</a>.</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<p>For more information, see <a href="https://contactform7.com/category/releases/" rel="nofollow">Releases</a>.</p>\n<h4>5.0</h4>\n<ul>\n<li>Additional settings: on_sent_ok and on_submit have been removed.</li>\n<li>New additional setting: skip_mail</li>\n<li>Flamingo: Inbound channel title changes in conjunction with a change in the title of the corresponding contact form.</li>\n<li>DOM events: Make an entire API response object accessible through the event.detail.apiResponse property.</li>\n<li>HTML mail: Adds language-related attributes to the HTML header.</li>\n<li>File upload: Sets the accept attribute to an uploading field.</li>\n<li>Introduces the WPCF7_MailTag class.</li>\n<li>Allows aborting a mail-sending attempt using the wpcf7_before_send_mail action hook. Also, you can set a custom status and a message through the action hook.</li>\n<li>Acceptance checkbox: Allows the specifying of a statement of conditions in the form-tag’s content part.</li>\n<li>Acceptance checkbox: Supports the optional option.</li>\n<li>New special mail tags: [_site_title], [_site_description], [_site_url], [_site_admin_email], [_invalid_fields], [_user_login], [_user_email], [_user_url], [_user_first_name], [_user_last_name], [_user_nickname], and [_user_display_name]</li>\n<li>New filter hooks: wpcf7_upload_file_name, wpcf7_autop_or_not, wpcf7_posted_data_{$type}, and wpcf7_mail_tag_replaced_{$type}</li>\n<li>New form-tag features: zero-controls-container and not-for-mail</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/contact-form-7/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:30:"\n		\n		\n		\n		\n		\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:9:"Yoast SEO";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"https://wordpress.org/plugins/wordpress-seo/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Oct 2010 20:55:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins-wp/wordpress-seo/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:103:"Improve your WordPress SEO: Write better content and have a fully optimized WordPress site using&#8230;";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Joost de Valk";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:8375:"<p><!--section=description--></p>\n<h3>Yoast SEO: the #1 WordPress SEO plugin</h3>\n<p>Need an SEO plugin that helps you reach for the stars? Yoast SEO is the original WordPress SEO plugin since 2008. It is the favorite tool of millions of users, ranging from the bakery around the corner to some of the most popular sites on the planet. With Yoast SEO, you get a solid toolset that helps you aim for that number one spot in the search results. Yoast: SEO for everyone.</p>\n<p>Yoast SEO does everything in its power to please both visitors and search engine spiders. How? Below you’ll find a small sampling of the powers of Yoast SEO:</p>\n<h4>Taking care of your WordPress SEO</h4>\n<ul>\n<li>The most advanced XML Sitemaps functionality at the push of a button.</li>\n<li>Full control over site breadcrumbs: add a piece of code and you’re good to go.</li>\n<li>Set canonical URLs to avoid duplicate content. Never have to worry about Google penalties again.</li>\n<li>Title and meta description templating for better branding and consistent snippets in the search results.</li>\n<li><strong>[Premium]</strong> Expand Yoast SEO with the News SEO, Video SEO, Local SEO and WooCommerce SEO extensions.</li>\n<li><strong>[Premium]</strong> Need help? Yoast SEO Premium users get 1 year free access to our awesome support team.</li>\n</ul>\n<blockquote>\n<p>Note: some features are Premium. Which means you need Yoast SEO Premium to unlock those features. You can <a href="https://yoa.st/1v8" rel="nofollow">get Yoast SEO Premium here</a>!</p>\n</blockquote>\n<h4>Write killer content with Yoast SEO</h4>\n<ul>\n<li>Content &amp; SEO analysis: Invaluable tools to write SEO-friendly texts.</li>\n<li>The snippet preview shows you how your post or page will look in the search results &#8211; even on mobile. Yoast SEO Premium even has social media previews!</li>\n<li><strong>[Premium]</strong> The Insights tool shows you what your text focuses on so you can keep your article in line with your keywords.</li>\n<li><strong>[Premium]</strong> Multiple focus keywords: Optimize your article for synonyms and related keywords.</li>\n<li><strong>[Premium]</strong> Automatic internal linking suggestions: write your article and get automatic suggested posts to link to.</li>\n</ul>\n<h4>Keep your site in perfect shape</h4>\n<ul>\n<li>Yoast SEO tunes the engine of your site so you can work on creating great content.</li>\n<li>Our cornerstone content and internal linking features help you optimize your site structure in a breeze.</li>\n<li>Integrates with Google Search Console: See how your site performs in the search engines and fix crawl errors.</li>\n<li>Manage SEO roles: Give your colleagues access to specific sections of the Yoast SEO plugin.</li>\n<li>Bulk editor: Make large-scale edits to your site.</li>\n<li><strong>[Premium]</strong> Social previews to manage the way your page is shared on social networks like Facebook and Twitter.</li>\n<li><strong>[Premium]</strong> Redirect manager: It keeps your site healthy by easily redirecting errors from Google Search Console, deleted pages and changed URLs.</li>\n</ul>\n<h3>Premium support</h3>\n<p>The Yoast team does not always provide active support for the Yoast SEO plugin on the WordPress.org forums, as we prioritize our email support. One-on-one email support is available to people who <a href="https://yoa.st/1v8" rel="nofollow">bought Yoast SEO Premium</a> only.</p>\n<p>Note that the <a href="https://yoa.st/1v8" rel="nofollow">Yoast SEO Premium</a> also has several extra features too, including the option to have multiple focus keywords, internal linking suggestions, cornerstone content checks and a redirect manager, so it is well worth your investment!</p>\n<p>You should also check out the <a href="https://yoa.st/1uu" rel="nofollow">Yoast Local SEO</a>, <a href="https://yoa.st/1uv" rel="nofollow">Yoast News SEO</a> and <a href="https://yoa.st/1uw" rel="nofollow">Yoast Video SEO</a> extensions to Yoast SEO. They work with the free version of Yoast SEO already, and these premium extensions of course come with support too.</p>\n<h3>Bug reports</h3>\n<p>Bug reports for Yoast SEO are <a href="https://github.com/Yoast/wordpress-seo" rel="nofollow">welcomed on GitHub</a>. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.</p>\n<h3>Further Reading</h3>\n<p>For more info, check out the following articles:</p>\n<ul>\n<li>The <a href="https://yoa.st/1v8" rel="nofollow">Yoast SEO Plugin</a> official homepage.</li>\n<li>The <a href="https://yoa.st/1va" rel="nofollow">Yoast SEO Knowledgebase</a>.</li>\n<li><a href="https://yoa.st/1v6" rel="nofollow">WordPress SEO &#8211; The definitive Guide by Yoast</a>.</li>\n<li>Other <a href="https://yoa.st/1v9" rel="nofollow">WordPress Plugins</a> by the same team.</li>\n<li>Follow Yoast on <a href="https://facebook.com/yoast" rel="nofollow">Facebook</a> &amp; <a href="https://twitter.com/yoast" rel="nofollow">Twitter</a>.</li>\n</ul>\n<h3>From within WordPress</h3>\n<ol>\n<li>Visit &#8216;Plugins &gt; Add New&#8217;</li>\n<li>Search for &#8216;Yoast SEO&#8217;</li>\n<li>Activate Yoast SEO from your Plugins page.</li>\n<li>Go to &#8220;after activation&#8221; below.</li>\n</ol>\n<h3>Manually</h3>\n<ol>\n<li>Upload the <code>wordpress-seo</code> folder to the <code>/wp-content/plugins/</code> directory</li>\n<li>Activate the Yoast SEO plugin through the &#8216;Plugins&#8217; menu in WordPress</li>\n<li>Go to &#8220;after activation&#8221; below.</li>\n</ol>\n<h3>After activation</h3>\n<ol>\n<li>You should see (a notice to start) the Yoast SEO configuration wizard.</li>\n<li>Go through the configuration wizard and set up the plugin for your site.</li>\n<li>You&#8217;re done!</li>\n</ol>\n<p><!--section=faq--></p>\n<p>You&#8217;ll find answers to many of your questions on <a href="https://yoa.st/1va" rel="nofollow">kb.yoast.com</a>.</p>\n<p><!--section=changelog--></p>\n<h4>6.2.0</h4>\n<p>Release Date: January 23rd, 2018</p>\n<p>Enhancements:</p>\n<ul>\n<li>Allows more strings to be translated.</li>\n<li>Adds the passive voice assessment for French.</li>\n<li>Adds the passive voice assessment for Spanish.</li>\n<li>Simplifies the feedback message for the assessment that checks whether subheadings contain the keyword.</li>\n</ul>\n<p>Bugfixes:</p>\n<ul>\n<li>Security hardening through stricter code checks.</li>\n<li>Reduces the number of times the content analysis is refreshed on page load.</li>\n<li>Fixes a bug where relative URLs were not counted as internal links in the internal link assessment.</li>\n<li>Fixes a bug where Premium users would be shown ads when following a certain path through the SEO menu.</li>\n<li>Fixes a bug where the method of setting the title and meta description templates for the WooCommerce shop page would not work anymore.</li>\n</ul>\n<h4>6.1.1</h4>\n<p>Release Date: January 10th, 2018</p>\n<p>Bugfixes:</p>\n<ul>\n<li>Fixes a bug where sitemaps could not be generated when there one or more galleries in the content.</li>\n</ul>\n<h4>6.1.0</h4>\n<p>Release Date: January 9th, 2018</p>\n<p>Enhancements:</p>\n<ul>\n<li>Allows more strings to be translated.</li>\n<li>Replaces any Yoast domain URLs with shortlink alternatives.</li>\n</ul>\n<p>Bugfixes:</p>\n<ul>\n<li>Fixes a bug where the internal links aren&#8217;t recognized when the <code>site_url</code> is not the same as the <code>home_url</code>.</li>\n<li>Fixes a bug where the user locale is not used for the Help Center when it is different from the site locale.</li>\n<li>Removes unsupported PHP 5.2 arguments in an <code>array_unique</code> call in the Term image sitemap.</li>\n<li>Removes unsupported PHP 5.3 arguments in a <code>json_encode</code> call in the notification functionality.</li>\n<li>Added support for locales without territory (examples: et, fi) &#8211; Props <a href="https://github.com/petskratt" rel="nofollow">Peeter Marvet</a>.</li>\n<li>Added support support for 3-letter language codes (example: rhg) &#8211; Props <a href="https://github.com/petskratt" rel="nofollow">Peeter Marvet</a>.</li>\n<li>Fixes a JavaScript compatibility issue by prefixing the webpack jsonP function with <code>yoast</code> &#8211; Props <a href="https://visualcomposer.io/" rel="nofollow">Raitis Sevelis from Visual Composer</a>.</li>\n</ul>\n<h4>Earlier versions</h4>\n<p>For the changelog of earlier versions, please refer to the separate changelog.txt file.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:17:"Akismet Anti-Spam";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"https://wordpress.org/plugins/akismet/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/akismet/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Oct 2005 08:57:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/plugins-wp/akismet/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:103:"Akismet checks your comments and contact form submissions against our global database of spam to&#8230;";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:20566:"<p><!--section=description--></p>\n<p>Akismet checks your comments and contact form submissions against our global database of spam to prevent your site from publishing malicious content. You can review the comment spam it catches on your blog&#8217;s &#8220;Comments&#8221; admin screen.</p>\n<p>Major features in Akismet include:</p>\n<ul>\n<li>Automatically checks all comments and filters out the ones that look like spam.</li>\n<li>Each comment has a status history, so you can easily see which comments were caught or cleared by Akismet and which were spammed or unspammed by a moderator.</li>\n<li>URLs are shown in the comment body to reveal hidden or misleading links.</li>\n<li>Moderators can see the number of approved comments for each user.</li>\n<li>A discard feature that outright blocks the worst spam, saving you disk space and speeding up your site.</li>\n</ul>\n<p>PS: You&#8217;ll need an <a href="https://akismet.com/get/" rel="nofollow">Akismet.com API key</a> to use it.  Keys are free for personal blogs; paid subscriptions are available for businesses and commercial sites.</p>\n<p><!--section=installation--></p>\n<p>Upload the Akismet plugin to your blog, Activate it, then enter your <a href="https://akismet.com/get/" rel="nofollow">Akismet.com API key</a>.</p>\n<p>1, 2, 3: You&#8217;re done!</p>\n<p><!--section=changelog--></p>\n<h4>4.0.2</h4>\n<p><em>Release Date &#8211; 18 December 2017</em></p>\n<ul>\n<li>Fixed a bug that could cause Akismet to recheck a comment that has already been manually approved or marked as spam.</li>\n<li>Fixed a bug that could cause Akismet to claim that some comments are still waiting to be checked when no comments are waiting to be checked.</li>\n</ul>\n<h4>4.0.1</h4>\n<p><em>Release Date &#8211; 6 November 2017</em></p>\n<ul>\n<li>Fixed a bug that could prevent some users from connecting Akismet via their Jetpack connection.</li>\n<li>Ensured that any pending Akismet-related events are unscheduled if the plugin is deactivated.</li>\n<li>Allow some JavaScript to be run asynchronously to avoid affecting page render speeds.</li>\n</ul>\n<h4>4.0</h4>\n<p><em>Release Date &#8211; 19 September 2017</em></p>\n<ul>\n<li>Added REST API endpoints for configuring Akismet and retrieving stats.</li>\n<li>Increased the minimum supported WordPress version to 4.0.</li>\n<li>Added compatibility with comments submitted via the REST API.</li>\n<li>Improved the progress indicator on the &#8220;Check for Spam&#8221; button.</li>\n</ul>\n<h4>3.3.4</h4>\n<p><em>Release Date &#8211; 3 August 2017</em></p>\n<ul>\n<li>Disabled Akismet&#8217;s debug log output by default unless AKISMET_DEBUG is defined.</li>\n<li>URL previews now begin preloading when the mouse moves near them in the comments section of wp-admin.</li>\n<li>When a comment is caught by the Comment Blacklist, Akismet will always allow it to stay in the trash even if it is spam as well.</li>\n<li>Fixed a bug that was preventing an error from being shown when a site can&#8217;t reach Akismet&#8217;s servers.</li>\n</ul>\n<h4>3.3.3</h4>\n<p><em>Release Date &#8211; 13 July 2017</em></p>\n<ul>\n<li>Reduced amount of bandwidth used by the URL Preview feature.</li>\n<li>Improved the admin UI when the API key is manually pre-defined for the site.</li>\n<li>Removed a workaround for WordPress installations older than 3.3 that will improve Akismet&#8217;s compatibility with other plugins.</li>\n<li>The number of spam blocked that is displayed on the WordPress dashboard will now be more accurate and updated more frequently.</li>\n<li>Fixed a bug in the Akismet widget that could cause PHP warnings.</li>\n</ul>\n<h4>3.3.2</h4>\n<p><em>Release Date &#8211; 10 May 2017</em></p>\n<ul>\n<li>Fixed a bug causing JavaScript errors in some browsers.</li>\n</ul>\n<h4>3.3.1</h4>\n<p><em>Release Date &#8211; 2 May 2017</em></p>\n<ul>\n<li>Improve performance by only requesting the akismet_comment_nonce option when absolutely necessary.</li>\n<li>Fixed two bugs that could cause PHP warnings.</li>\n<li>Fixed a bug that was preventing the &#8220;Remove author URL&#8221; feature from working after a comment was edited using &#8220;Quick Edit.&#8221;</li>\n<li>Fixed a bug that was preventing the URL preview feature from working after a comment was edited using &#8220;Quick Edit.&#8221;</li>\n</ul>\n<h4>3.3</h4>\n<p><em>Release Date &#8211; 23 February 2017</em></p>\n<ul>\n<li>Updated the Akismet admin pages with a new clean design.</li>\n<li>Fixed bugs preventing the <code>akismet_add_comment_nonce</code> and <code>akismet_update_alert</code> wrapper functions from working properly.</li>\n<li>Fixed bug preventing the loading indicator from appearing when re-checking all comments for spam.</li>\n<li>Added a progress indicator to the &#8220;Check for Spam&#8221; button.</li>\n<li>Added a success message after manually rechecking the Pending queue for spam.</li>\n</ul>\n<h4>3.2</h4>\n<p><em>Release Date &#8211; 6 September 2016</em></p>\n<ul>\n<li>Added a WP-CLI module. You can now check comments and recheck the moderation queue from the command line.</li>\n<li>Stopped using the deprecated jQuery function <code>.live()</code>.</li>\n<li>Fixed a bug in <code>remove_comment_author_url()</code> and <code>add_comment_author_url()</code> that could generate PHP notices.</li>\n<li>Fixed a bug that could cause an infinite loop for sites with very very very large comment IDs.</li>\n<li>Fixed a bug that could cause the Akismet widget title to be blank.</li>\n</ul>\n<h4>3.1.11</h4>\n<p><em>Release Date &#8211; 12 May 2016</em></p>\n<ul>\n<li>Fixed a bug that could cause the &#8220;Check for Spam&#8221; button to skip some comments.</li>\n<li>Fixed a bug that could prevent some spam submissions from being sent to Akismet.</li>\n<li>Updated all links to use https:// when possible.</li>\n<li>Disabled Akismet debug logging unless WP_DEBUG and WP_DEBUG_LOG are both enabled.</li>\n</ul>\n<h4>3.1.10</h4>\n<p><em>Release Date &#8211; 1 April 2016</em></p>\n<ul>\n<li>Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.</li>\n<li>Fixed a bug that could have resulted in comments that were caught by the core WordPress comment blacklist not to have a corresponding History entry.</li>\n<li>Fixed a bug that could have caused avoidable PHP warnings in the error log.</li>\n</ul>\n<h4>3.1.9</h4>\n<p><em>Release Date &#8211; 28 March 2016</em></p>\n<ul>\n<li>Add compatibility with Jetpack so that Jetpack can automatically configure Akismet settings when appropriate.</li>\n<li>Fixed a bug preventing some comment data from being sent to Akismet.</li>\n</ul>\n<h4>3.1.8</h4>\n<p><em>Release Date &#8211; 4 March 2016</em></p>\n<ul>\n<li>Fixed a bug preventing Akismet from being used with some plugins that rewrite admin URLs.</li>\n<li>Reduced the amount of bandwidth used on Akismet API calls</li>\n<li>Reduced the amount of space Akismet uses in the database</li>\n<li>Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.</li>\n</ul>\n<h4>3.1.7</h4>\n<p><em>Release Date &#8211; 4 January 2016</em></p>\n<ul>\n<li>Added documentation for the &#8216;akismet_comment_nonce&#8217; filter.</li>\n<li>The post-install activation button is now accessible to screen readers and keyboard-only users.</li>\n<li>Fixed a bug that was preventing the &#8220;Remove author URL&#8221; feature from working in WordPress 4.4</li>\n</ul>\n<h4>3.1.6</h4>\n<p><em>Release Date &#8211; 14 December 2015</em></p>\n<ul>\n<li>Improve the notices shown after activating Akismet.</li>\n<li>Update some strings to allow for the proper plural forms in all languages.</li>\n</ul>\n<h4>3.1.5</h4>\n<p><em>Release Date &#8211; 13 October 2015</em></p>\n<ul>\n<li>Closes a potential XSS vulnerability.</li>\n</ul>\n<h4>3.1.4</h4>\n<p><em>Release Date &#8211; 24 September 2015</em></p>\n<ul>\n<li>Fixed a bug that was preventing some users from automatically connecting using Jetpack if they didn&#8217;t have a current Akismet subscription.</li>\n<li>Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.</li>\n<li>Error messages and instructions have been simplified to be more understandable.</li>\n<li>Link previews are enabled for all links inside comments, not just the author&#8217;s website link.</li>\n</ul>\n<h4>3.1.3</h4>\n<p><em>Release Date &#8211; 6 July 2015</em></p>\n<ul>\n<li>Notify users when their account status changes after previously being successfully set up. This should help any users who are seeing blank Akismet settings screens.</li>\n</ul>\n<h4>3.1.2</h4>\n<p><em>Release Date &#8211; 7 June 2015</em></p>\n<ul>\n<li>Reduced the amount of space Akismet uses in the commentmeta table.</li>\n<li>Fixed a bug where some comments with quotes in the author name weren&#8217;t getting history entries</li>\n<li>Pre-emptive security improvements to ensure that the Akismet plugin can&#8217;t be used by attackers to compromise a WordPress installation.</li>\n<li>Better UI for the key entry field: allow whitespace to be included at the beginning or end of the key and strip it out automatically when the form is submitted.</li>\n<li>When deactivating the plugin, notify the Akismet API so the site can be marked as inactive.</li>\n<li>Clearer error messages.</li>\n</ul>\n<h4>3.1.1</h4>\n<p><em>Release Date &#8211; 17th March, 2015</em></p>\n<ul>\n<li>Improvements to the &#8220;Remove comment author URL&#8221; JavaScript</li>\n<li>Include the pingback pre-check from the 2.6 branch.</li>\n</ul>\n<h4>3.1</h4>\n<p><em>Release Date &#8211; 11th March, 2015</em></p>\n<ul>\n<li>Use HTTPS by default for all requests to Akismet.</li>\n<li>Fix for a situation where Akismet might strip HTML from a comment.</li>\n</ul>\n<h4>3.0.4</h4>\n<p><em>Release Date &#8211; 11th December, 2014</em></p>\n<ul>\n<li>Fix to make .htaccess compatible with Apache 2.4.</li>\n<li>Fix to allow removal of https author URLs.</li>\n<li>Fix to avoid stripping part of the author URL when removing and re-adding.</li>\n<li>Removed the &#8220;Check for Spam&#8221; button from the &#8220;Trash&#8221; and &#8220;Approved&#8221; queues, where it would have no effect.</li>\n<li>Allow automatic API key configuration when Jetpack is installed and connected to a WordPress.com account</li>\n</ul>\n<h4>3.0.3</h4>\n<p><em>Release Date &#8211; 3rd November, 2014</em></p>\n<ul>\n<li>Fix for sending the wrong data to delete_comment action that could have prevented old spam comments from being deleted.</li>\n<li>Added a filter to disable logging of Akismet debugging information.</li>\n<li>Added a filter for the maximum comment age when deleting old spam comments.</li>\n<li>Added a filter for the number per batch when deleting old spam comments.</li>\n<li>Removed the &#8220;Check for Spam&#8221; button from the Spam folder.</li>\n</ul>\n<h4>3.0.2</h4>\n<p><em>Release Date &#8211; 18th August, 2014</em></p>\n<ul>\n<li>Performance improvements.</li>\n<li>Fixed a bug that could truncate the comment data being sent to Akismet for checking.</li>\n</ul>\n<h4>3.0.1</h4>\n<p><em>Release Date &#8211; 9th July, 2014</em></p>\n<ul>\n<li>Removed dependency on PHP&#8217;s fsockopen function</li>\n<li>Fix spam/ham reports to work when reported outside of the WP dashboard, e.g., from Notifications or the WP app</li>\n<li>Remove jQuery dependency for comment form JavaScript</li>\n<li>Remove unnecessary data from some Akismet comment meta</li>\n<li>Suspended keys will now result in all comments being put in moderation, not spam.</li>\n</ul>\n<h4>3.0.0</h4>\n<p><em>Release Date &#8211; 15th April, 2014</em></p>\n<ul>\n<li>Move Akismet to Settings menu</li>\n<li>Drop Akismet Stats menu</li>\n<li>Add stats snapshot to Akismet settings</li>\n<li>Add Akismet subscription details and status to Akismet settings</li>\n<li>Add contextual help for each page</li>\n<li>Improve Akismet setup to use Jetpack to automate plugin setup</li>\n<li>Fix &#8220;Check for Spam&#8221; to use AJAX to avoid page timing out</li>\n<li>Fix Akismet settings page to be responsive</li>\n<li>Drop legacy code</li>\n<li>Tidy up CSS and Javascript</li>\n<li>Replace the old discard setting with a new &#8220;discard pervasive spam&#8221; feature.</li>\n</ul>\n<h4>2.6.0</h4>\n<p><em>Release Date &#8211; 18th March, 2014</em></p>\n<ul>\n<li>Add ajax paging to the check for spam button to handle large volumes of comments</li>\n<li>Optimize javascript and add localization support </li>\n<li>Fix bug in link to spam comments from right now dashboard widget</li>\n<li>Fix bug with deleting old comments to avoid timeouts dealing with large volumes of comments</li>\n<li>Include X-Pingback-Forwarded-For header in outbound WordPress pingback verifications</li>\n<li>Add pre-check for pingbacks, to stop spam before an outbound verification request is made</li>\n</ul>\n<h4>2.5.9</h4>\n<p><em>Release Date &#8211; 1st August, 2013</em></p>\n<ul>\n<li>Update &#8216;Already have a key&#8217; link to redirect page rather than depend on javascript</li>\n<li>Fix some non-translatable strings to be translatable</li>\n<li>Update Activation banner in plugins page to redirect user to Akismet config page</li>\n</ul>\n<h4>2.5.8</h4>\n<p><em>Release Date &#8211; 20th January, 2013</em></p>\n<ul>\n<li>Simplify the activation process for new users</li>\n<li>Remove the reporter_ip parameter</li>\n<li>Minor preventative security improvements</li>\n</ul>\n<h4>2.5.7</h4>\n<p><em>Release Date &#8211; 13th December, 2012</em></p>\n<ul>\n<li>FireFox Stats iframe preview bug</li>\n<li>Fix mshots preview when using https</li>\n<li>Add .htaccess to block direct access to files</li>\n<li>Prevent some PHP notices</li>\n<li>Fix Check For Spam return location when referrer is empty</li>\n<li>Fix Settings links for network admins</li>\n<li>Fix prepare() warnings in WP 3.5</li>\n</ul>\n<h4>2.5.6</h4>\n<p><em>Release Date &#8211; 26th April, 2012</em></p>\n<ul>\n<li>Prevent retry scheduling problems on sites where wp_cron is misbehaving</li>\n<li>Preload mshot previews</li>\n<li>Modernize the widget code</li>\n<li>Fix a bug where comments were not held for moderation during an error condition</li>\n<li>Improve the UX and display when comments are temporarily held due to an error</li>\n<li>Make the Check For Spam button force a retry when comments are held due to an error</li>\n<li>Handle errors caused by an invalid key</li>\n<li>Don&#8217;t retry comments that are too old</li>\n<li>Improve error messages when verifying an API key</li>\n</ul>\n<h4>2.5.5</h4>\n<p><em>Release Date &#8211; 11th January, 2012</em></p>\n<ul>\n<li>Add nonce check for comment author URL remove action</li>\n<li>Fix the settings link</li>\n</ul>\n<h4>2.5.4</h4>\n<p><em>Release Date &#8211; 5th January, 2012</em></p>\n<ul>\n<li>Limit Akismet CSS and Javascript loading in wp-admin to just the pages that need it</li>\n<li>Added author URL quick removal functionality</li>\n<li>Added mShot preview on Author URL hover</li>\n<li>Added empty index.php to prevent directory listing</li>\n<li>Move wp-admin menu items under Jetpack, if it is installed</li>\n<li>Purge old Akismet comment meta data, default of 15 days</li>\n</ul>\n<h4>2.5.3</h4>\n<p><em>Release Date &#8211; 8th Febuary, 2011</em></p>\n<ul>\n<li>Specify the license is GPL v2 or later</li>\n<li>Fix a bug that could result in orphaned commentmeta entries</li>\n<li>Include hotfix for WordPress 3.0.5 filter issue</li>\n</ul>\n<h4>2.5.2</h4>\n<p><em>Release Date &#8211; 14th January, 2011</em></p>\n<ul>\n<li>Properly format the comment count for author counts</li>\n<li>Look for super admins on multisite installs when looking up user roles</li>\n<li>Increase the HTTP request timeout</li>\n<li>Removed padding for author approved count</li>\n<li>Fix typo in function name</li>\n<li>Set Akismet stats iframe height to fixed 2500px.  Better to have one tall scroll bar than two side by side.</li>\n</ul>\n<h4>2.5.1</h4>\n<p><em>Release Date &#8211; 17th December, 2010</em></p>\n<ul>\n<li>Fix a bug that caused the &#8220;Auto delete&#8221; option to fail to discard comments correctly</li>\n<li>Remove the comment nonce form field from the &#8216;Akismet Configuration&#8217; page in favor of using a filter, akismet_comment_nonce</li>\n<li>Fixed padding bug in &#8220;author&#8221; column of posts screen</li>\n<li>Added margin-top to &#8220;cleared by &#8230;&#8221; badges on dashboard</li>\n<li>Fix possible error when calling akismet_cron_recheck()</li>\n<li>Fix more PHP warnings</li>\n<li>Clean up XHTML warnings for comment nonce</li>\n<li>Fix for possible condition where scheduled comment re-checks could get stuck</li>\n<li>Clean up the comment meta details after deleting a comment</li>\n<li>Only show the status badge if the comment status has been changed by someone/something other than Akismet</li>\n<li>Show a &#8216;History&#8217; link in the row-actions</li>\n<li>Translation fixes</li>\n<li>Reduced font-size on author name</li>\n<li>Moved &#8220;flagged by&#8230;&#8221; notification to top right corner of comment container and removed heavy styling</li>\n<li>Hid &#8220;flagged by&#8230;&#8221; notification while on dashboard</li>\n</ul>\n<h4>2.5.0</h4>\n<p><em>Release Date &#8211; 7th December, 2010</em></p>\n<ul>\n<li>Track comment actions under &#8216;Akismet Status&#8217; on the edit comment screen</li>\n<li>Fix a few remaining deprecated function calls ( props Mike Glendinning ) </li>\n<li>Use HTTPS for the stats IFRAME when wp-admin is using HTTPS</li>\n<li>Use the WordPress HTTP class if available</li>\n<li>Move the admin UI code to a separate file, only loaded when needed</li>\n<li>Add cron retry feature, to replace the old connectivity check</li>\n<li>Display Akismet status badge beside each comment</li>\n<li>Record history for each comment, and display it on the edit page</li>\n<li>Record the complete comment as originally submitted in comment_meta, to use when reporting spam and ham</li>\n<li>Highlight links in comment content</li>\n<li>New option, &#8220;Show the number of comments you&#8217;ve approved beside each comment author.&#8221;</li>\n<li>New option, &#8220;Use a nonce on the comment form.&#8221;</li>\n</ul>\n<h4>2.4.0</h4>\n<p><em>Release Date &#8211; 23rd August, 2010</em></p>\n<ul>\n<li>Spell out that the license is GPLv2</li>\n<li>Fix PHP warnings</li>\n<li>Fix WordPress deprecated function calls</li>\n<li>Fire the delete_comment action when deleting comments</li>\n<li>Move code specific for older WP versions to legacy.php</li>\n<li>General code clean up</li>\n</ul>\n<h4>2.3.0</h4>\n<p><em>Release Date &#8211; 5th June, 2010</em></p>\n<ul>\n<li>Fix &#8220;Are you sure&#8221; nonce message on config screen in WPMU</li>\n<li>Fix XHTML compliance issue in sidebar widget</li>\n<li>Change author link; remove some old references to WordPress.com accounts</li>\n<li>Localize the widget title (core ticket #13879)</li>\n</ul>\n<h4>2.2.9</h4>\n<p><em>Release Date &#8211; 2nd June, 2010</em></p>\n<ul>\n<li>Eliminate a potential conflict with some plugins that may cause spurious reports</li>\n</ul>\n<h4>2.2.8</h4>\n<p><em>Release Date &#8211; 27th May, 2010</em></p>\n<ul>\n<li>Fix bug in initial comment check for ipv6 addresses</li>\n<li>Report comments as ham when they are moved from spam to moderation</li>\n<li>Report comments as ham when clicking undo after spam</li>\n<li>Use transition_comment_status action when available instead of older actions for spam/ham submissions</li>\n<li>Better diagnostic messages when PHP network functions are unavailable</li>\n<li>Better handling of comments by logged-in users</li>\n</ul>\n<h4>2.2.7</h4>\n<p><em>Release Date &#8211; 17th December, 2009</em></p>\n<ul>\n<li>Add a new AKISMET_VERSION constant</li>\n<li>Reduce the possibility of over-counting spam when another spam filter plugin is in use</li>\n<li>Disable the connectivity check when the API key is hard-coded for WPMU</li>\n</ul>\n<h4>2.2.6</h4>\n<p><em>Release Date &#8211; 20th July, 2009</em></p>\n<ul>\n<li>Fix a global warning introduced in 2.2.5</li>\n<li>Add changelog and additional readme.txt tags</li>\n<li>Fix an array conversion warning in some versions of PHP</li>\n<li>Support a new WPCOM_API_KEY constant for easier use with WordPress MU</li>\n</ul>\n<h4>2.2.5</h4>\n<p><em>Release Date &#8211; 13th July, 2009</em></p>\n<ul>\n<li>Include a new Server Connectivity diagnostic check, to detect problems caused by firewalls</li>\n</ul>\n<h4>2.2.4</h4>\n<p><em>Release Date &#8211; 3rd June, 2009</em></p>\n<ul>\n<li>Fixed a key problem affecting the stats feature in WordPress MU</li>\n<li>Provide additional blog information in Akismet API calls</li>\n</ul>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<p>Upload the Akismet plugin to your blog, Activate it, then enter your <a href="https://akismet.com/get/" rel="nofollow">Akismet.com API key</a>.</p>\n<p>1, 2, 3: You&#8217;re done!</p>\n</dd>\n</dl>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:43:"https://wordpress.org/plugins/akismet/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Jetpack by WordPress.com";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"https://wordpress.org/plugins/jetpack/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/jetpack/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Jan 2011 02:21:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/plugins-wp/jetpack/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:112:"The one plugin you need for stats, related posts, search engine optimization, social sharing, protection,&#8230;";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:24437:"<p><!--section=description--></p>\n<p>Keep any WordPress site secure, increase traffic, and engage your readers.</p>\n<h4>Traffic and SEO Tools</h4>\n<p>Traffic is the lifeblood of any website. Jetpack includes:</p>\n<ul>\n<li>[free] Site stats and analytics</li>\n<li>[free] Automatic sharing on Facebook, Twitter, LinkedIn, Tumblr, Reddit, and WhatsApp</li>\n<li>[free] Related posts</li>\n<li>[paid] Search engine optimization tools for Google, Bing, Twitter, Facebook, and WordPress.com</li>\n<li>[paid] Advertising program that includes the best of AdSense, Facebook Ads, AOL, Amazon, Google AdX, and Yahoo</li>\n</ul>\n<h4>Security and Backup Services</h4>\n<p>Stop worrying about data loss, downtime, and hacking. Jetpack provides:</p>\n<ul>\n<li>[free] Brute force attack protection</li>\n<li>[free] Downtime and uptime monitoring</li>\n<li>[free] Secured logins and two-factor authentication</li>\n<li>[paid] Malware scanning, code scanning, and threat resolution</li>\n<li>[paid] Site backups, restores, and migrations</li>\n</ul>\n<h4>Content Creation</h4>\n<p>Add rich, beautifully-presented media &#8212; no graphic design expertise necessary:</p>\n<ul>\n<li>[free] A high-speed CDN for your images</li>\n<li>[free] Carousels, slideshows, and tiled galleries</li>\n<li>[free] Simple embeds from YouTube, Google Documents, Spotify and more</li>\n<li>[free] Sidebar customization including Facebook, Twitter, and RSS feeds</li>\n<li>[free] Extra sidebar widgets including blog stats, calendar, and author widgets</li>\n<li>[paid] High-speed, ad-free, and high-definition video hosting</li>\n</ul>\n<h4>Discussion and Community</h4>\n<p>Create a connection with your readers and keep them coming back to your site with:</p>\n<ul>\n<li>[free] Email subscriptions</li>\n<li>[free] Comment login with Facebook, Twitter, and Google</li>\n<li>[free] Fully-customizable contact forms</li>\n<li>[free] Infinite scroll for your posts</li>\n</ul>\n<h4>Expert Support</h4>\n<p>We have an entire team of Happiness Engineers ready to help you. Ask your questions in the support forum, or <a href="https://jetpack.com/contact-support" rel="nofollow">contact us directly</a>.</p>\n<h4>Paid Services</h4>\n<p>Most of Jetpack&#8217;s features and services are free. Jetpack also provides advanced security and backup services, video hosting, site monetization, priority support, and more SEO tools in three <a href="https://jetpack.com/pricing?from=wporg" rel="nofollow">simple and affordable plans</a>.</p>\n<h4>Get Started</h4>\n<p>Installation is free, quick, and easy. Set up <a href="https://jetpack.com/install?from=wporg" rel="nofollow">the free plan</a> in minutes.</p>\n<p><!--section=installation--></p>\n<h4>Automated Installation</h4>\n<p>Installation is free, quick, and easy. <a href="https://jetpack.com/install?from=wporg" rel="nofollow">Install Jetpack from our site</a> in minutes.</p>\n<h4>Manual Alternatives</h4>\n<p>Alternatively, install Jetpack via the plugin directory, or upload the files manually to your server and follow the on-screen instructions. If you need additional help <a href="https://jetpack.com/support/installing-jetpack/" rel="nofollow">read our detailed instructions</a>.</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<h4>Automated Installation</h4>\n<p>Installation is free, quick, and easy. <a href="https://jetpack.com/install?from=wporg" rel="nofollow">Install Jetpack from our site</a> in minutes.</p>\n<h4>Manual Alternatives</h4>\n<p>Alternatively, install Jetpack via the plugin directory, or upload the files manually to your server and follow the on-screen instructions. If you need additional help <a href="https://jetpack.com/support/installing-jetpack/" rel="nofollow">read our detailed instructions</a>.</p>\n</dd>\n<dt>Is Jetpack Free?</dt>\n<dd>\n<p>Yes! Jetpack&#8217;s core features are and always will be free.</p>\n<p>These include: <a href="https://jetpack.com/features/traffic/site-stats" rel="nofollow">site stats</a>, a <a href="https://jetpack.com/features/writing/content-delivery-network/" rel="nofollow">high-speed CDN</a> for images, <a href="https://jetpack.com/features/traffic/related-posts" rel="nofollow">related posts</a>, <a href="https://jetpack.com/features/security/downtime-monitoring" rel="nofollow">downtime monitoring</a>, brute force <a href="https://jetpack.com/features/security/brute-force-attack-protection" rel="nofollow">attack protection</a>, <a href="https://jetpack.com/features/traffic/automatic-publishing/" rel="nofollow">automated sharing</a> to social networks, <a href="https://jetpack.com/features/writing/sidebar-customization/" rel="nofollow">sidebar customization</a>, and many more.</p>\n</dd>\n<dt>Should I purchase a paid plan?</dt>\n<dd>\n<p>Jetpack&#8217;s paid services include automated backups, security scanning, spam filtering, video hosting, site monetization, SEO tools, and priority support.</p>\n<p>If you&#8217;re interested in learning more about the extra layers of protection and advanced tools available, learn more about our <a href="https://jetpack.com/pricing?from=wporg" rel="nofollow">paid plans</a>.</p>\n</dd>\n<dt>Why do I need a WordPress.com account?</dt>\n<dd>\n<p>Since Jetpack and its services are provided and hosted by WordPress.com, a WordPress.com account is required for Jetpack to function.</p>\n</dd>\n<dt>I already have a WordPress account, but Jetpack isn&#8217;t working. What&#8217;s going on?</dt>\n<dd>\n<p>A WordPress.com account is different from the account you use to log into your self-hosted WordPress. If you can log into <a href="https://wordpress.com" rel="nofollow">WordPress.com</a>, then you already have a WordPress.com account. If you can&#8217;t, you can easily create one <a href="https://jetpack.com/install?from=wporg" rel="nofollow">during installation</a>.</p>\n</dd>\n<dt>How do I view my stats?</dt>\n<dd>\n<p>Once you&#8217;ve installed Jetpack your stats will be available on <a href="https://wordpress.com/stats" rel="nofollow">WordPress.com/Stats</a>, on the official <a href="https://apps.wordpress.com/mobile/" rel="nofollow">WordPress mobile apps</a>, and on your Jetpack dashboard.</p>\n</dd>\n<dt>How do I contribute to Jetpack?</dt>\n<dd>\n<p>There are opportunities for developers at all levels to contribute. <a href="https://jetpack.com/contribute" rel="nofollow">Learn more about contributing to Jetpack</a> or consider <a href="https://jetpack.com/beta" rel="nofollow">joining our beta program</a>.</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>5.7.1</h4>\n<ul>\n<li>Release date: January 16, 2018</li>\n<li>Release post: https://wp.me/p1moTy-7aS</li>\n</ul>\n<p><strong>Bug Fixes</strong></p>\n<ul>\n<li>Protect: Fixed the math problem fallback for logging into Multisite installations.</li>\n<li>Settings: Made sure that the Security tab is no longer constantly updating the displayed information.</li>\n</ul>\n<h4>5.7</h4>\n<ul>\n<li>Release date: January 2, 2018</li>\n<li>Release post: https://wp.me/p1moTy-6FR</li>\n</ul>\n<p><strong>Enhancements</strong></p>\n<ul>\n<li>Added ability to create revisions of Portfolio Projects.</li>\n<li>Users hosting their sites with our Pressable partner who have Rewind access can now jump from the new Activity card in the Jetpack dashboard to the Activity Log in WordPress.com and restore or download backups for the site.</li>\n<li>Comments: Edit links for comments in the frontend can redirect to calypso if the Jetpack option <code>edit_links_calypso_redirect</code> is enabled.</li>\n<li>Protect: Updated the styling of the Protect page for recovering access to your site when you&#8217;re locked out of it.</li>\n<li>Search: Improved the UI for customizing the Search widget.</li>\n</ul>\n<p><strong>Improved compatibility</strong></p>\n<ul>\n<li>Comments: Updated our filtering behavior for Jetpack comments so other plugins appending html to the comments section are able to do it instead of being filtered out by Jetpack.</li>\n<li>Widgets: We updated Goodreads URLs to support https schema.</li>\n<li>Masterbar: We now hide the Masterbar settings card in Jetpack’s Admin Page for sites that are set to always show the Masterbar.</li>\n<li>Lazy Images: Added a callback for processing image attributes array when attempting to lazy load images are loaded via <code>wp_get_attachment_image</code>.</li>\n<li>Search: Added hooks to the search filters widget so that other plugins/themes can hook in and change its output.</li>\n</ul>\n<p><strong>Bug fixes</strong></p>\n<ul>\n<li>REST API: Added a check for avoiding a fatal error when attempting to include Akismet class files in case the Akismet plugin files are present but the permissions on the files there are set to be not readable</li>\n<li>Markdown: Fixed bug where code inside shortcodes wasn&#8217;t correctly restored from the hash.</li>\n<li>Search: Fixed the link that acts as a month and year filter removal toggle.</li>\n</ul>\n<h4>5.6.1</h4>\n<ul>\n<li>Release date: December 14, 2017</li>\n<li>\n<p>Release post: https://wp.me/p1moTy-6Jk</p>\n</li>\n<li>\n<p>Contact Forms: Hardened security in Contact Form processing.</p>\n</li>\n<li>Sharing: Bumped the character limit to 280 when sharing a post to Twitter.</li>\n<li>Widget Visibility: Fixed a bug that disabled &#8220;saving&#8221; the widget when removing a Widget Visibility rule.</li>\n</ul>\n<h4>5.6</h4>\n<ul>\n<li>Release date: December 5, 2017</li>\n<li>Release post: https://wp.me/p1moTy-6zt</li>\n</ul>\n<p><strong>Major Enhancements</strong><br />\n* Google Analytics: Add support for universal analytics for WooCommerce.<br />\n* Performance: minify all JavaScript files used in the plugin.<br />\n* Performance: add new Lazy Images module.<br />\n* Protect: add new mechanism allowing you to send yourself an email with a link to the form when you are locked out of your site.</p>\n<p><strong>Enhancements</strong><br />\n* Custom CSS: add new set of font properties that can be used in the CSS editor.<br />\n* Photon: do not remove <code>width</code> and <code>height</code> attributes from image tags when known.<br />\n* Sitemaps: add CLI commands to purge and built the sitemaps.<br />\n* Sitemaps: only display the reporter log success messages if <code>JETPACK_DEV_DEBUG</code> is defined.<br />\n* WordPress.com API: add new endpoints to allow for better comment management in third party interfaces like WordPress.com.<br />\n* WordPress.com Toolbar: prevent dns prefetching for logged out users.</p>\n<p><strong>Improved compatibility</strong><br />\n* Stats: remove function deprecated in PHP 7.2.</p>\n<p><strong>Bug fixes</strong><br />\n* Comment Likes: make sure Like text is properly translated.<br />\n* General: only load stats code when necessary.<br />\n* Related Posts: allow site owners to exclude multiple blog posts from the list of Related Posts.<br />\n* Sharing: remove inline JavaScript used in the email sharing form.<br />\n* Search: Maintain ordering of the search filters in the widget.<br />\n* Sync: avoid PHP notices during the synchronization process.<br />\n* WordPress.com Toolbar: avoid broken link when using the sign out button.</p>\n<h4>5.5.1</h4>\n<ul>\n<li>Release date: November 21, 2017</li>\n<li>Release post: https://wp.me/p1moTy-6Bd</li>\n</ul>\n<p><strong>Bug fixes</strong><br />\n* In Jetpack 5.5 we made some changes that created errors if you were using other plugins that added custom links to the Plugins menu. This is now fixed.<br />\n* We have fixed a problem that did not allow to upload plugins using API requests.<br />\n* Open Graph links in post headers are no longer invalid in some special cases.<br />\n* We fixed warnings happening when syncing users with WordPress.com.<br />\n* We updated the way the Google+ button is loaded to match changes made by Google, to ensure the button is always displayed properly.<br />\n* We fixed conflicts between Jetpack&#8217;s Responsive Videos and the updates made to Video players in WordPress 4.9.<br />\n* We updated Publicize&#8217;s message length to match Twitter&#8217;s new 280 character limit.</p>\n<h4>5.5</h4>\n<ul>\n<li>Release date: November 7, 2017</li>\n<li>Release post: https://wp.me/p1moTy-6rk</li>\n</ul>\n<p><strong>Major Enhancements</strong></p>\n<ul>\n<li>Jetpack is now fully compatible with WordPress&#8217;s <a href="https://make.wordpress.org/core/2017/09/25/introducing-the-gallery-widget/" rel="nofollow">new Gallery Widget</a>. Your old Gallery widgets powered by Jetpack will switch to the new Widget when you update to WordPress 4.9.</li>\n</ul>\n<p><strong>Enhancements</strong><br />\n* We have improved the performance when loading the Jetpack Settings in the dashboard by optimizing the number of calls made when loading the page.<br />\n* We have updated the plugin to do a better job of cleaning up after itself whenever you decide to remove Jetpack from your site.<br />\n* We made some changes to reduce the number of connection issues that may happen on a site when switching from HTTP to HTTPs.<br />\n* We made some performance improvements to the Jetpack dashboard interface, to make sure your options and settings are loaded faster there.<br />\n* Error messages are also better in the Jetpack Dashboard; whenever you can&#8217;t update settings, Jetpack will provide you with more information about why.<br />\n* We improved the Jetpack update process to make sure updating Jetpack does not stress your database during it, even on high-traffic sites.<br />\n* The next version of WordPress, 4.9, will be released very soon and will include <a href="https://make.wordpress.org/core/2017/10/22/code-editing-improvements-in-wordpress-4-9/" rel="nofollow">a lot of changes to its code editors</a>. Jetpack&#8217;s Custom CSS will be fully compatible with the new editors and their syntax highlighting feature.<br />\n* We also made changes to make sure Jetpack was fully compatible with the <a href="https://make.wordpress.org/core/2017/10/15/improvements-for-roles-and-capabilities-in-4-9/" rel="nofollow">role and capability changes</a> in WordPress 4.9.<br />\n* We have made some performance improvements to the Carousel feature.<br />\n* Contact Form: do not process shortcodes in widgets when WordPress itself does, starting in 4.9.<br />\n* Contact Form: we have improved the &#8220;website&#8221; field to display better error messages when you don&#8217;t supply a URL. We have also improved the look of the date picker for the date field.<br />\n* Contact Form: avoid duplicate slashes when loading editor style.<br />\n* Masterbar: update the &#8220;Plugins&#8221; menu item to match the updated design on WordPress.com.<br />\n* Open Graph: do not display images smaller than Facebook&#8217;s required size.<br />\n* Sharing: use Google&#8217;s minified libraries to improve performance when loading Google buttons.<br />\n* Sharing: update Open Graph Image tags appearing on the home page to offer better alternatives based on your site settings in Appearance &gt; Customize.<br />\n* We improved the way sitemaps are built so they do not consume too much memory when they are generated.<br />\n* WP.me Shorlinks: those links will now always use HTTPS.<br />\n* Spellchecker: we improved the admin interface to make it more clear when adding ignored phrases and saving them.<br />\n* Subscriptions: we added a filter so third party developers can track comment subscription activations.<br />\n* Sync: synchronize plugin action links to add that information to WordPress.com.<br />\n* Sync: improvements to better track theme and widget changes.<br />\n* VideoPress: we removed Jetpack version locking for directly embedded VideoPress videos to ensure all users receive the newest version of the player.<br />\n* We added a new filter (<code>jetpack_google_translate_widget_layout</code>) to the Google Translate Widget to allow you to change its layout.<br />\n* WordPress.com REST API: improve comment management for all roles, including post authors.<br />\n* WordPress.com REST API: allow site owners to manage comments on attachment pages from WordPress.com.<br />\n* WordPress.com REST API: improve the response from the API when WordPress&#8217; autoupdates are disabled.</p>\n<p><strong>Improved compatibility</strong><br />\n* You can now use Jetpack&#8217;s contact form and Yoast SEO&#8217;s Focus keywords on the same page without any issues in the editor.<br />\n* Top Posts Widget: avoid Fatal Errors when the widget is used on a site using WPML, and when a popular post cannot be found by WPML.<br />\n* Sync: add more Custom Post Types from third-party plugins to the list of things we do not synchronize with WordPress.com, to improve sync performance.<br />\n* Sharing: since <a href="https://make.wordpress.org/core/2017/11/02/press-this-in-4-9/" rel="nofollow">Press This is now a plugin and not part of WordPress itself</a>, we removed the Press This sharing button if you are not using the plugin.</p>\n<p><strong>Bug fixes</strong><br />\n* We now avoid displaying notices to user roles that cannot benefit or act based on the info in the notices.<br />\n* Gravatar Hovercards: avoid PHP Notices when the user info is an object.<br />\n* Infinite Scroll: avoid PHP notices when a site customizes galleries thanks to the <code>post_gallery</code> filter.<br />\n* Mailchimp: make sure subscription forms can still be embedded in posts and pages.<br />\n* Mailchimp: do not require the use of the shortcodes feature to use the Mailchimp widget.<br />\n* Mailchimp: fix issue where Mailchimp form code could not be added to the Mailchimp widget.<br />\n* Masterbar: avoid JavaScript errors by always loading jQuery.<br />\n* Post By Email: do not display any content in the email address field if no email address has ever been set before.<br />\n* Publicize: avoid errors when DOMDocument is not available.<br />\n* Publicize: we now hide the feature activation toggle if you are not allowed to manage Jetpack features.<br />\n* Search: make sure module cannot be activated when the site does not use a Plan.<br />\n* SEO Tools: do not output any custom meta tags if another SEO plugin is already active.<br />\n* Sharing: make sure Twitter Cards can be displayed even when a post does not include a title.<br />\n* Sharing: fix alignment of sharing buttons in the admin preview when using custom sharing buttons.<br />\n* Sitemaps: wait a minute before to generate sitemaps when the feature is activated, to avoid performance issues.<br />\n* Sync: avoid synchronization issues on Multisite networks using custom domains.<br />\n* Top Posts Widget: display the default title when it is set to empty.<br />\n* Milestone Widget: make sure the widget is displayed properly and can easily be translated into other languages.<br />\n* Verification Tools: avoid notices when saving changes on a Multisite network admin page.<br />\n* VideoPress: avoid missing file warning in the editor when using an RTL language.<br />\n* Upcoming events Widget: avoid PHP notices on sites using a custom timezone setting.<br />\n* WordPress.com REST API: avoid errors when installing plugins via the WordPress.com API.</p>\n<h4>5.4</h4>\n<ul>\n<li>Release date: October 3, 2017</li>\n<li>Release post: http://wp.me/p1moTy-67V</li>\n</ul>\n<p><strong>Major Enhancements</strong><br />\n* Multiple improvements to the connection process, to allow more people to use the Jetpack plugin, even on very specific server configurations.<br />\n* Add a new Welcome screen to guide site owners after they have purchased a Jetpack plan.</p>\n<p><strong>Enhancements</strong><br />\n* Add Schema.org markup to the Contact Info Widget.<br />\n* Add a new &#8220;Date&#8221; field to the Contact Form.<br />\n* Do not show any update notices when in <a href="http://jetpack.com/support/development-mode" rel="nofollow">development mode</a>.<br />\n* Improve our documentation to help contributors set up a unit testing environment.<br />\n* Avoid conflicts between Jetpack&#8217;s Infinite Scroll and other Infinite Scroll plugins.<br />\n* Improvements to the WordPress.com REST API to avoid issues when interacting with your site&#8217;s categories and tags on WordPress.com.<br />\n* Allow third party plugin and theme authors to add new menu items to the WordPress.com toolbar.<br />\n* Improve the Content Options panel displayed in the Customizer with certain themes.<br />\n* Add architecture for the Jetpack Search feature, available for Jetpack Professional users.<br />\n* Simple Payments: improve the display of the payment items when used on your site.<br />\n* Ensure a proper display of the Recipe shortcode on sites using an RTL language.<br />\n* Improve the display of the Facebook posts, images, and all other Facebook embeds in your posts.<br />\n* Synchronize the author information for all published posts.<br />\n* Record how Jetpack was discovered and activated to better understand how site owners first discover Jetpack.<br />\n* Improve the display and options offered with the Milestone Widget.</p>\n<p><strong>Bug fixes</strong><br />\n* We fixed layout issues appearing in the admin interface for IE11 users.<br />\n* Comment Form: avoid whitespace sometimes appearing below the form with some themes.<br />\n* Contact Form: avoid errors in the post editor on sites using RTL languages.<br />\n* Toolbar: always display the Toolbar when it&#8217;s active, regardless of other admin bar settings.<br />\n* Widget Visibility: make sure rules are correctly migrated from the old Jetpack image widget to the new WordPress Image Widget.<br />\n* Avoid errors showing that Jetpack is out of date on WordPress.com, when running a Multisite network.<br />\n* WP CLI: avoid warnings when using the <code>wp jetpack protect whitelist list</code> command to list the whitelisted IP addresses in the Protect feature.<br />\n* Avoid displaying raw HTML in the Stats Configuration screen.<br />\n* Comment edits are reflected properly in wordpress.com.</p>\n<h4>5.3</h4>\n<ul>\n<li>Release date: September 5, 2017</li>\n<li>Release post: http://wp.me/p1moTy-5Xv</li>\n</ul>\n<p><strong>Major Enhancements</strong><br />\n* Full PHP 7.1 compatibility.<br />\n* It&#8217;s now possible to preview your site within WordPress.com.</p>\n<p><strong>Enhancements</strong><br />\n* The Ads feature now gives you more options and control over the ads displayed on your site.<br />\n* Increased performance in the admin by cutting back on unnecessary requests.<br />\n* Loading comment avatars from Facebook and Twitter through a more secure https.<br />\n* Admin UI is much friendlier on initial activation when there are no stats to display.<br />\n* You&#8217;re now able to stop VideoPress from looping a video during autoplay through the shortcode.<br />\n* Made some optimizations to the Jetpack connection process which means connecting your site more is more reliable.<br />\n* The EU Cookie Law widget got some styling improvements and looks better in any theme.<br />\n* There&#8217;s a new Jetpack CLI command to allow testing of the Jetpack connection.<br />\n* Added the Likes and Monitor features to our recommended features list, making it easier to activate for new sites.<br />\n* Improvements made that makes sure we have the most up-to-date version of your site when managing from WordPress.com.<br />\n* Added a link to view your Comments in the WordPress.com toolbar.<br />\n* Lots of minor design improvements to the Jetpack admin area.<br />\n* We&#8217;ve found a few places where we were able to optimize the loading of css files.<br />\n* Removed the Omnisearch feature.</p>\n<p><strong>Bug fixes</strong><br />\n* Fixed compatibility issues with plugins using TinyMCE.<br />\n* Contact Form submission emails have been fixed for sites hosted on SiteGround.<br />\n* Updating WordPress.com themes will no longer have any problems.<br />\n* The Sitemaps feature will no longer error with posts/images with special characters in the title.<br />\n* There are no more conflicts with the ACF plugin when adding a new custom field.<br />\n* Fixed a bug that would cause some plugins to throw warnings with the Shortcode feature.<br />\n* We&#8217;re no longer loading a font on the front-end for the Likes feature, which will also have some performance benefits.<br />\n* The Jetpack admin UI had some bugs that were causing some features to not display the correct active status, which are squashed now.<br />\n* Cleaned up our markup to avoid XHTML validation errors.<br />\n* Brought back a filter for the Widget Visibility feature that was accidentally removed.<br />\n* Managing your comments and comment authors more reliable from WordPress.com.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:43:"https://wordpress.org/plugins/jetpack/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:33:"\n		\n		\n		\n		\n				\n\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"WordPress Importer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:49:"https://wordpress.org/plugins/wordpress-importer/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 May 2010 18:48:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:13:"Uncategorized";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:52:"https://wordpress.org/plugins-wp/wordpress-importer/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:101:"Import posts, pages, comments, custom fields, categories, tags and more from a WordPress export file.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Brian Colinger";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:5307:"<p><!--section=description--></p>\n<p>The WordPress Importer will import the following content from a WordPress export file:</p>\n<ul>\n<li>Posts, pages and other custom post types</li>\n<li>Comments</li>\n<li>Custom fields and post meta</li>\n<li>Categories, tags and terms from custom taxonomies</li>\n<li>Authors</li>\n</ul>\n<p>For further information and instructions please see the <a href="https://codex.wordpress.org/Importing_Content#WordPress" rel="nofollow">Codex page on Importing Content</a></p>\n<h3>Filters</h3>\n<p>The importer has a couple of filters to allow you to completely enable/block certain features:</p>\n<ul>\n<li><code>import_allow_create_users</code>: return false if you only want to allow mapping to existing users</li>\n<li><code>import_allow_fetch_attachments</code>: return false if you do not wish to allow importing and downloading of attachments</li>\n<li><code>import_attachment_size_limit</code>: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited)</li>\n</ul>\n<p>There are also a few actions available to hook into:</p>\n<ul>\n<li><code>import_start</code>: occurs after the export file has been uploaded and author import settings have been chosen</li>\n<li><code>import_end</code>: called after the last output from the importer</li>\n</ul>\n<p><!--section=installation--></p>\n<p>The quickest method for installing the importer is:</p>\n<ol>\n<li>Visit Tools -&gt; Import in the WordPress dashboard</li>\n<li>Click on the WordPress link in the list of importers</li>\n<li>Click &#8220;Install Now&#8221;</li>\n<li>Finally click &#8220;Activate Plugin &amp; Run Importer&#8221;</li>\n</ol>\n<p>If you would prefer to do things manually then follow these instructions:</p>\n<ol>\n<li>Upload the <code>wordpress-importer</code> folder to the <code>/wp-content/plugins/</code> directory</li>\n<li>Activate the plugin through the &#8216;Plugins&#8217; menu in WordPress</li>\n<li>Go to the Tools -&gt; Import screen, click on WordPress</li>\n</ol>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<p>The quickest method for installing the importer is:</p>\n<ol>\n<li>Visit Tools -&gt; Import in the WordPress dashboard</li>\n<li>Click on the WordPress link in the list of importers</li>\n<li>Click &#8220;Install Now&#8221;</li>\n<li>Finally click &#8220;Activate Plugin &amp; Run Importer&#8221;</li>\n</ol>\n<p>If you would prefer to do things manually then follow these instructions:</p>\n<ol>\n<li>Upload the <code>wordpress-importer</code> folder to the <code>/wp-content/plugins/</code> directory</li>\n<li>Activate the plugin through the &#8216;Plugins&#8217; menu in WordPress</li>\n<li>Go to the Tools -&gt; Import screen, click on WordPress</li>\n</ol>\n</dd>\n<dt>Help! I&#8217;m getting out of memory errors or a blank screen.</dt>\n<dd>\n<p>If your exported file is very large, the import script may run into your host&#8217;s configured memory limit for PHP.</p>\n<p>A message like &#8220;Fatal error: Allowed memory size of 8388608 bytes exhausted&#8221; indicates that the script can&#8217;t successfully import your XML file under the current PHP memory limit. If you have access to the php.ini file, you can manually increase the limit; if you do not (your WordPress installation is hosted on a shared server, for instance), you might have to break your exported XML file into several smaller pieces and run the import script one at a time.</p>\n<p>For those with shared hosting, the best alternative may be to consult hosting support to determine the safest approach for running the import. A host may be willing to temporarily lift the memory limit and/or run the process directly from their end.</p>\n<p>&#8212; <a href="https://codex.wordpress.org/Importing_Content#Before_Importing" rel="nofollow">WordPress Codex: Importing Content</a></p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>0.6.3</h4>\n<ul>\n<li>Add support for import term metadata.</li>\n<li>Fix bug that caused slashes to be stripped from imported content.</li>\n<li>Fix bug that caused characters to be stripped inside of CDATA in some cases.</li>\n<li>Fix PHP notices.</li>\n</ul>\n<h4>0.6.2</h4>\n<ul>\n<li>Add wp_import_existing_post filter. See: https://core.trac.wordpress.org/ticket/33721</li>\n</ul>\n<h4>0.6</h4>\n<ul>\n<li>Support for WXR 1.2 and multiple CDATA sections</li>\n<li>Post aren&#8217;t duplicates if their post_type&#8217;s are different</li>\n</ul>\n<h4>0.5.2</h4>\n<ul>\n<li>Double check that the uploaded export file exists before processing it. This prevents incorrect error messages when<br />\nan export file is uploaded to a server with bad permissions and WordPress 3.3 or 3.3.1 is being used.</li>\n</ul>\n<h4>0.5</h4>\n<ul>\n<li>Import comment meta (requires export from WordPress 3.2)</li>\n<li>Minor bugfixes and enhancements</li>\n</ul>\n<h4>0.4</h4>\n<ul>\n<li>Map comment user_id where possible</li>\n<li>Import attachments from <code>wp:attachment_url</code></li>\n<li>Upload attachments to correct directory</li>\n<li>Remap resized image URLs correctly</li>\n</ul>\n<h4>0.3</h4>\n<ul>\n<li>Use an XML Parser if possible</li>\n<li>Proper import support for nav menus</li>\n<li>&#8230; and much more, see <a href="https://core.trac.wordpress.org/ticket/15197" rel="nofollow">Trac ticket #15197</a></li>\n</ul>\n<h4>0.1</h4>\n<ul>\n<li>Initial release</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:11:"WooCommerce";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"https://wordpress.org/plugins/woocommerce/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/woocommerce/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 27 Sep 2011 15:32:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:45:"https://wordpress.org/plugins-wp/woocommerce/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:97:"WooCommerce is a powerful, extendable eCommerce plugin that helps you sell anything. Beautifully.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"WooThemes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:31090:"<p><!--section=description--></p>\n<p>WooCommerce is a free eCommerce plugin that allows you to sell anything, beautifully. Built to integrate seamlessly with WordPress, WooCommerce is the world’s favorite eCommerce solution that gives both store owners and developers complete control.</p>\n<p>With endless flexibility and access to hundreds of free and premium WordPress extensions, WooCommerce now powers 30% of all online stores &#8212; more than any other platform.</p>\n<iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/1KahlicghaE?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe>\n<h4>Sell anything, anywhere</h4>\n<p>With WooCommerce, you can sell both physical and digital goods in all shapes and sizes, offer product variations, multiple configurations, and instant downloads to shoppers, and even sell affiliate goods from online marketplaces.</p>\n<p>With premium extensions, you can offer bookings, memberships, and recurring subscriptions. Perhaps you’d like to sell monthly subscriptions for physical goods, or offer your members a discount on digital downloads? It’s all possible.</p>\n<h4>Ship wherever you like</h4>\n<p>Offer free shipping, flat rate shipping, or make real-time calculations. Limit your shipments to specific countries, or open your store up to the world. Shipping is highly configurable, and WooCommerce even supports drop shipping.</p>\n<h4>Extensive payment options</h4>\n<p>WooCommerce comes bundled with the ability to accept major credit cards, PayPal, BACS (bank transfers), and cash on delivery. Need additional options? More than 140 region-specific gateways integrate with WooCommerce, including popular choices like Stripe, Authorize.Net, and Amazon Payments.</p>\n<h4>You control it all &#8212; forever</h4>\n<p>WooCommerce gives you complete control of your store, from taxes to stock levels to customer accounts. Add and remove extensions, change your design, and switch settings as you please. It’s all under your control.</p>\n<p>One of the biggest risks of using a hosted eCommerce platform is what happens to your store if the provider closes up shop. With WooCommerce, you have complete control, so there’s never any reason to worry. Your data belongs to you &#8212; and it’s kept secure, thanks to regular audits by industry leaders.</p>\n<h4>Define your style with Storefront</h4>\n<p><a href="https://wordpress.org/themes/storefront/" rel="nofollow">Storefront</a> is a free WordPress theme available to any WooCommerce store. Along with deep WooCommerce integration, Storefront prioritizes speed and uptime while eliminating theme and plugin conflicts during major updates.</p>\n<p>Define your style even further by customizing Storefront to your liking or choosing from one of our several <a href="https://woocommerce.com/product-category/themes/storefront-child-theme-themes/" rel="nofollow">Storefront child themes</a>. It’s all up to you, and all open source.</p>\n<h4>Built with developers in mind</h4>\n<p>Extendable, adaptable, and open source &#8212; WooCommerce was created with developers in mind. With its strong, robust framework, you can scale your client’s store all the way from basic to high-end (infinity and beyond).</p>\n<p>Built with a REST API, WooCommerce can integrate with virtually any service. Your store’s data can be accessed anywhere, anytime, 100% securely. WooCommerce allows developers to easily create, modify, and grow a store that meets their specifications.</p>\n<p>No matter the size of the store you want to build, WooCommerce will scale to meet your requirements. With a growing collection of more than 300 extensions, you can enhance each store’s features to meet your client’s unique needs &#8212; or even create your own solution.</p>\n<p>If security is a concern, rest easy. WooCommerce is audited by a dedicated team of developers working around the clock to identify and patch any and all discovered bugs.</p>\n<p>We also support WooCommerce and all its extensions with comprehensive, easily-accessible documentation. With our docs, you’ll learn how to create the exact site your client needs.</p>\n<h4>Extensions galore</h4>\n<p>WordPress.org is home to some amazing extensions for WooCommerce, including:</p>\n<ul>\n<li><a href="https://wordpress.org/plugins/woocommerce-google-analytics-integration/">Google Analytics</a></li>\n<li><a href="https://wordpress.org/plugins/woocommerce-delivery-notes/">Delivery Notes</a></li>\n<li><a href="https://wordpress.org/plugins/woocommerce-pdf-invoices-packing-slips/">PDF Invoices and Packing Slips</a></li>\n<li><a href="https://wordpress.org/plugins/affiliates-woocommerce-light/">Affiliates Integration Light</a></li>\n<li><a href="https://wordpress.org/plugins/woocommerce-new-product-badge/">New Product Badges</a></li>\n</ul>\n<p>Keen to see them all? Search WordPress.org for ‘WooCommerce’ to dive in.</p>\n<p>If you’re looking for something endorsed and maintained by the developers who built WooCommerce, there are a plethora of premium eCommerce extensions, the most popular of which include:</p>\n<ul>\n<li><a href="https://woocommerce.com/products/woocommerce-subscriptions/" rel="nofollow">WooCommerce Subscriptions</a></li>\n<li><a href="https://woocommerce.com/products/woocommerce-memberships/" rel="nofollow">WooCommerce Memberships</a></li>\n<li><a href="https://woocommerce.com/products/woocommerce-bookings/" rel="nofollow">WooCommerce Bookings</a></li>\n<li><a href="https://woocommerce.com/products/dynamic-pricing/" rel="nofollow">Dynamic Pricing</a></li>\n<li><a href="https://woocommerce.com/products/table-rate-shipping/" rel="nofollow">Table Rate Shipping</a></li>\n<li><a href="https://woocommerce.com/products/product-csv-import-suite/" rel="nofollow">Product CSV Import Suite</a></li>\n</ul>\n<p>And there’s plenty more where they came from. Visit our <a href="https://woocommerce.com/product-category/woocommerce-extensions/" rel="nofollow">extensions page</a> to find out everything you’re capable of and all that&#8217;s possible with premium WooCommerce extensions.</p>\n<h4>Join our growing community</h4>\n<p>When you download WooCommerce, you join a community of more than a million store owners, developers, and WordPress enthusiasts. We’re one of the fastest-growing open source communities online, and whether you’re a n00b or a Ninja, we’d love to have you!</p>\n<p>If you’re interested in contributing to WooCommerce we’ve got more than 350 contributors, and there’s always room for more. Head over to the <a href="https://github.com/woocommerce/woocommerce" rel="nofollow">WooCommerce GitHub Repository</a> to find out how you can pitch in.</p>\n<p>Want to add a new language to WooCommerce? Swell! You can contribute via <a href="https://translate.wordpress.org/projects/wp-plugins/woocommerce" rel="nofollow">translate.wordpress.org</a>.</p>\n<p>And, finally, consider joining or spearheading a WooCommerce Meetup locally, more about those <a href="https://woocommerce.com/woocommerce/meetups/" rel="nofollow">here</a>.</p>\n<p><!--section=installation--></p>\n<h4>Minimum Requirements</h4>\n<ul>\n<li>PHP version 5.2.4 or greater (PHP 5.6 or greater is recommended)</li>\n<li>MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)</li>\n<li>Some payment gateways require fsockopen support (for IPN access)</li>\n<li>WordPress 4.4+</li>\n</ul>\n<p>Visit the <a href="https://docs.woocommerce.com/document/server-requirements/" rel="nofollow">WooCommerce server requirements documentation</a> for a detailed list of server requirements.</p>\n<h4>Automatic installation</h4>\n<p>Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.</p>\n<p>In the search field type “WooCommerce” and click Search Plugins. Once you’ve found our eCommerce plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”.</p>\n<h4>Manual installation</h4>\n<p>The manual installation method involves downloading our eCommerce plugin and uploading it to your webserver via your favourite FTP application. The WordPress codex contains <a href="https://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation" rel="nofollow">instructions on how to do this here</a>.</p>\n<h4>Updating</h4>\n<p>Automatic updates should work like a charm; as always though, ensure you backup your site just in case.</p>\n<p>If on the off-chance you do encounter issues with the shop/category pages after an update you simply need to flush the permalinks by going to WordPress &gt; Settings &gt; Permalinks and hitting &#8216;save&#8217;. That should return things to normal.</p>\n<h4>Dummy data</h4>\n<p>WooCommerce comes with some dummy data you can use to see how products look; either import dummy_data.xml via the <a href="https://wordpress.org/plugins/wordpress-importer/">WordPress importer</a> or use our <a href="https://woocommerce.com/products/product-csv-import-suite/" rel="nofollow">CSV Import Suite plugin</a> to import dummy_data.csv and dummy_data_variations.csv.</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<h4>Minimum Requirements</h4>\n<ul>\n<li>PHP version 5.2.4 or greater (PHP 5.6 or greater is recommended)</li>\n<li>MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)</li>\n<li>Some payment gateways require fsockopen support (for IPN access)</li>\n<li>WordPress 4.4+</li>\n</ul>\n<p>Visit the <a href="https://docs.woocommerce.com/document/server-requirements/" rel="nofollow">WooCommerce server requirements documentation</a> for a detailed list of server requirements.</p>\n<h4>Automatic installation</h4>\n<p>Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.</p>\n<p>In the search field type “WooCommerce” and click Search Plugins. Once you’ve found our eCommerce plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”.</p>\n<h4>Manual installation</h4>\n<p>The manual installation method involves downloading our eCommerce plugin and uploading it to your webserver via your favourite FTP application. The WordPress codex contains <a href="https://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation" rel="nofollow">instructions on how to do this here</a>.</p>\n<h4>Updating</h4>\n<p>Automatic updates should work like a charm; as always though, ensure you backup your site just in case.</p>\n<p>If on the off-chance you do encounter issues with the shop/category pages after an update you simply need to flush the permalinks by going to WordPress &gt; Settings &gt; Permalinks and hitting &#8216;save&#8217;. That should return things to normal.</p>\n<h4>Dummy data</h4>\n<p>WooCommerce comes with some dummy data you can use to see how products look; either import dummy_data.xml via the <a href="https://wordpress.org/plugins/wordpress-importer/">WordPress importer</a> or use our <a href="https://woocommerce.com/products/product-csv-import-suite/" rel="nofollow">CSV Import Suite plugin</a> to import dummy_data.csv and dummy_data_variations.csv.</p>\n</dd>\n<dt>Where can I find WooCommerce documentation and user guides?</dt>\n<dd>\n<p>For help setting up and configuring WooCommerce please refer to our <a href="https://docs.woocommerce.com/documentation/plugins/woocommerce/getting-started/" rel="nofollow">user guide</a></p>\n<p>For extending or theming WooCommerce, see our <a href="https://docs.woocommerce.com/documentation/plugins/woocommerce/woocommerce-codex/" rel="nofollow">codex</a>.</p>\n</dd>\n<dt>Where can I get support or talk to other users?</dt>\n<dd>\n<p>If you get stuck, you can ask for help in the <a href="https://wordpress.org/support/plugin/woocommerce" rel="nofollow">WooCommerce Plugin Forum</a>.</p>\n<p>For help with premium extensions from WooCommerce.com, use <a href="https://woocommerce.com/my-account/tickets/" rel="nofollow">our helpdesk</a>.</p>\n</dd>\n<dt>Will WooCommerce work with my theme?</dt>\n<dd>\n<p>Yes; WooCommerce will work with any theme, but may require some styling to make it match nicely. Please see our <a href="https://docs.woocommerce.com/documentation/plugins/woocommerce/woocommerce-codex/" rel="nofollow">codex</a> for help. If you&#8217;re looking for a theme with built in WooCommerce integration we recommend <a href="https://woocommerce.com/storefront/" rel="nofollow">Storefront</a>.</p>\n</dd>\n<dt>Where can I request new features, eCommerce themes and extensions?</dt>\n<dd>\n<p>You can vote on and request new features and extensions in our <a href="http://ideas.woothemes.com/forums/133476-woocommerce" rel="nofollow">WooIdeas board</a></p>\n</dd>\n<dt>Where can I report bugs or contribute to the project?</dt>\n<dd>\n<p>Bugs can be reported either in our support forum or preferably on the <a href="https://github.com/woocommerce/woocommerce/issues" rel="nofollow">WooCommerce GitHub repository</a>.</p>\n</dd>\n<dt>Where can I find the REST API documentation?</dt>\n<dd>\n<p>You can find the documentation of our REST API on the <a href="https://woocommerce.github.io/woocommerce-rest-api-docs/" rel="nofollow">WooCommerce REST API Docs</a>.</p>\n</dd>\n<dt>WooCommerce is awesome! Can I contribute?</dt>\n<dd>\n<p>Yes you can! Join in on our <a href="http://github.com/woocommerce/woocommerce/" rel="nofollow">GitHub repository</a> <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f642.png" alt="?" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>3.2.6 &#8211; 2017-12-13</h4>\n<ul>\n<li>Fix &#8211; CSV Importer &#8211; Fix ID mapping to existing IDs.</li>\n<li>Fix &#8211; CSV Importer &#8211; Unslash header fields to avoid extra slashes.</li>\n<li>Fix &#8211; CSV Importer &#8211; Allow import and export of draft products.</li>\n<li>Fix &#8211; CSV Importer &#8211; Get global attribute ID only when is a global attribute.</li>\n<li>Fix &#8211; Remove URL fragment when appending geolocation hash.</li>\n<li>Fix &#8211; Additional cart rounding fixes so rounding before subtotal works again. Added more unit tests.</li>\n<li>Fix &#8211; Add BOM to exported report CSVs.</li>\n<li>Fix &#8211; is_visible should ensure product is is not trashed before returning true.</li>\n<li>Fix &#8211; Return packages with no rates back to the cart so the shipping calculator is displayed even when the current country is not shippable.</li>\n<li>Fix &#8211; Merge session and persistent carts when both exists after login.</li>\n<li>Fix &#8211; Remove &#8220;wc_error&#8221; query string after login. </li>\n<li>Fix &#8211; Allow woocommerce_form_field() have &#8216;custom_attributes&#8217; equal 0.</li>\n<li>Fix &#8211; Bulk actions in status logs table.</li>\n<li>Fix &#8211; Exclude add-to-cart from pagination links.</li>\n<li>Fix &#8211; Updated $GLOBALS[&#8216;post&#8217;] data in products shortcode to prevent theme conflicts.</li>\n<li>Fix &#8211; Only remove base taxes in cart totals class if item is taxable.</li>\n<li>Fix &#8211; REST API &#8211; Fixed date format in reports schema.</li>\n<li>Fix &#8211; REST API &#8211; Updated product categories image schema.</li>\n<li>Fix &#8211; REST API &#8211; UUse KSES for purchase_note like in admin.</li>\n<li>Fix &#8211; REST API &#8211; Filter passed images before processing so they can be unset via querystring.</li>\n<li>Tweak &#8211; Use protected instead of private methods to allow easy override in session handler.</li>\n<li>Tweak &#8211; wc_lostpassword_url should not be used before init &#8211; added warning.</li>\n<li>Localization &#8211; Update Japanese prefectures to include prefecture type.</li>\n</ul>\n<h4>3.2.5 &#8211; 2017-11-22</h4>\n<ul>\n<li>Fix &#8211; WordPress 4.9 &#8211; REST API &#8211; Updated schema, sanitization, and validation callbacks to support correct data types.</li>\n<li>Fix &#8211; WordPress 4.9 &#8211; Fix an issue saving variation attributes on new products and with attributes containing slashes.</li>\n<li>Fix &#8211; Save fee tax lines to new orders on checkout.</li>\n<li>Fix &#8211; Restore the post global after rendering product shortcodes.</li>\n<li>Fix &#8211; Fix product filtering when searching for a string including quote characters.</li>\n<li>Fix &#8211; Fix layered nav drop-downs containing unicode characters.</li>\n<li>Fix &#8211; Fix an edge case rounding bug with shipping taxes, and another with non-integer quantities.</li>\n<li>Fix &#8211; Set correct defaults when adding a new shipping class in admin.</li>\n</ul>\n<h4>3.2.4 &#8211; 2017-11-16</h4>\n<ul>\n<li>Fix &#8211; Cache IDs in shortcodes rather than query objects.</li>\n<li>Fix &#8211; Fix float rounding issues in cart with currencies like Bitcoin.</li>\n<li>Fix &#8211; Prevent slashes appearing in shipping fields and inside meta keys when using quotes.</li>\n<li>Fix &#8211; Check valid data when filtering <code>wp_nav_menu_objects</code> to prevent conflicts.</li>\n<li>Fix &#8211; <code>get_total_ex_tax</code> should exclude fee taxes.</li>\n<li>Fix &#8211; Fix orders count in tax reports.</li>\n<li>Fix &#8211; Allow removing coupons from the cart, even if coupons are disabled.</li>\n<li>Fix &#8211; Prevent calculate_totals totals running too often.</li>\n<li>Fix &#8211; Set attributes during variation creation so all options are correctly displayed in cart forms.</li>\n<li>Fix &#8211; Grab description directly to pass through wc_format_content to prevent double sanitization.</li>\n<li>Fix &#8211; Fix db warnings when using the &#8220;Add Order Indexes&#8221; tool.</li>\n<li>Fix &#8211; Remove unnecessary html formatting in variation dimensions field.</li>\n<li>Fix &#8211; Fix WC_Customer_Download isset method.</li>\n<li>Fix &#8211; Removed class within class in admin meta boxes HTML.</li>\n<li>Fix &#8211; Fixed wrong <code>flex-control-nav</code> selector scope in <code>add-to-cart-variation.js</code></li>\n<li>Fix &#8211; Allow variations to be added to cart from query string.</li>\n<li>Fix &#8211; Use <code>add_filter</code> for <code>comment_feed_where</code> hook. </li>\n<li>Fix &#8211; Change nocache_headers hook firing in the cache helper.</li>\n<li>Fix &#8211; Coupon min/max spend based on displayed subtotal.</li>\n<li>Fix &#8211; Fix event propagation on click in setup wizard and improve validation.</li>\n<li>Fix &#8211; API &#8211; Change how line items are saved in API so calculations are correct.</li>\n<li>Tweak &#8211; Hide downloads from admin emails. </li>\n<li>Tweak &#8211; Set placeholder for variation lxwxh field to that of the parent.</li>\n<li>Tweak &#8211; Improve the Add Payment Methods display so buttons are not shown when no payment methods support the feature.</li>\n<li>Localization &#8211; Update NJ tax rate.</li>\n<li>Localization &#8211; Add Belarusian ruble BYN.</li>\n</ul>\n<h4>3.2.3 &#8211; 2017-11-02</h4>\n<ul>\n<li>Fix &#8211; Fixed a conflict with some slider plugins due to sanitization of archive/term descriptions. </li>\n<li>Fix &#8211; Fixed a flexslider bug when there is only 1 image on the product page (no gallery).</li>\n<li>Fix &#8211; Prevent potential notices when someone extends product tabs wrongly.</li>\n<li>Fix &#8211; Fixed display of shipping calculator under some conditions.</li>\n<li>Fix &#8211; Fix discount calculation when customer is not within the base location and prices include tax.</li>\n</ul>\n<h4>3.2.2 &#8211; 2017-10-31</h4>\n<ul>\n<li>Fix &#8211; Properly escape commas when exporting products to CSV.</li>\n<li>Fix &#8211; Fixed email template padding in Outlook.</li>\n<li>Fix &#8211; Flexslider support for RTL languages and fixes for zoom target in Chrome.</li>\n<li>Fix &#8211; Correctly sync prices for grouped products.</li>\n<li>Fix &#8211; Filter and remove invalid tax classes names.</li>\n<li>Fix &#8211; Stop showing &#8220;major&#8221; update notification for minor or patch releases.</li>\n<li>Fix &#8211; Allow scroll bar in untested plugins list on the bulk plugin updates screen.</li>\n<li>Fix &#8211; Fixed meta data cloning when duplicating products.</li>\n<li>Fix &#8211; Clean &#8220;Filter Products by Attribute&#8221; widget cache when updating attributes.</li>\n<li>Fix &#8211; Fixed warning messages when reseting passwords with an invalid key.</li>\n<li>Fix &#8211; Cart totals: Don&#8217;t add shipping costs unless show_shipping is true.</li>\n<li>Fix &#8211; Cart totals: Calculate shipping after discounts so discount amounts are available.</li>\n<li>Fix &#8211; Cart totals: Fixed issue where VAT exempt users where still being charged VAT on the totals.</li>\n<li>Fix &#8211; Cart totals: Fixed the coupons user limit and calculations.</li>\n<li>Fix &#8211; Fixed &#8220;relevance&#8221; default sorting in search results.</li>\n<li>Fix &#8211; Use item tax class rather than product tax class when recalculating order totals.</li>\n<li>Tweak &#8211; Allow shortcodes and relative URLs for downloads in product CSV importer.</li>\n<li>Tweak &#8211; Save unsaved items first while deleting order items.</li>\n<li>Tweak &#8211; Only change <code>nocacheheaders</code> when on a cart/checkout page.</li>\n<li>Tweak &#8211; Setup locale before generating settings placeholders in email templates.</li>\n<li>Tweak &#8211; On checkout, improved the field locale logic to work without clearing default values.</li>\n<li>Tweak &#8211; Change title of customer invoice email for clarity.</li>\n<li>Tweak &#8211; Use custom event instead of blur to trigger validation.</li>\n<li>Tweak &#8211; Various selectWoo usibility improvements and better support for keyboard controls on AJAX multiselect elements.</li>\n<li>Tweak &#8211; Various setup Wizard improvements.</li>\n<li>Dev &#8211; Fixed orders date query when querying by meta data.</li>\n<li>Dev &#8211; In the CSV exporter, added a filter to process meta values before export.</li>\n</ul>\n<h4>3.2.1 &#8211; 2017-10-13</h4>\n<ul>\n<li>Fix &#8211; Made grouped products display in the saved order, vs the menu order.</li>\n<li>Fix &#8211; Made variations with &#8216;same as parent&#8217; tax class calculate taxes correctly.</li>\n<li>Fix &#8211; Fixed tax rate reverting to 0 when the tax rate itself is not changed and the row is saved.</li>\n<li>Fix &#8211; Made tax rates sort correctly when defining postcodes and cities.</li>\n<li>Fix &#8211; Made guided tour help tab videos lazy-load to prevent performance issues.</li>\n<li>Fix &#8211; Added SelectWoo dependency to admin meta box scripts.</li>\n<li>Fix &#8211; Fixed cart subtotal 1p rounding error.</li>\n<li>Fix &#8211; Fixed discount logic to also look at variation parent categories when validating coupons.</li>\n<li>Fix &#8211; Product import filename based matching, and full URL based matching where the date part would still be present.</li>\n<li>Fix &#8211; Fixed storage of cart discounts when prices include tax.</li>\n<li>Fix &#8211; Added styling for screen-reader-text for themes which do not define it.</li>\n<li>Fix &#8211; Fixed legacy cart <code>prices_include_tax</code> variable.</li>\n<li>Fix &#8211;  Hide cat-parent class when category will show no children due to the new depth setting.</li>\n<li>Fix &#8211; Make sure image zoom is enable for calling initZoomForTarget.</li>\n<li>Fix &#8211; {blogname} email placeholder.</li>\n<li>Fix &#8211; API &#8211; Use edit context when updating prices.</li>\n<li>Tweak &#8211; Clearly describe when a feature is powered by WooCommerce Services in the setup wizard.</li>\n<li>Tweak &#8211; Restored discount total line in order screen when discounts are present.</li>\n<li>Tweak &#8211; Add back option to send admin new order email, and include order number and customer email in order emails.</li>\n<li>Tweak &#8211; Replace settings screenshot on wp.org listing.</li>\n</ul>\n<h4>3.2.0 &#8211; 2017-10-11</h4>\n<ul>\n<li>Feature &#8211; Coupons can now be applied and removed in admin when editing unpaid orders.</li>\n<li>Feature &#8211; Simplified the ability to resend order details to customers with a single &#8220;Resend Order Details&#8221; action.</li>\n<li>Feature &#8211; Added store street address, city and postal code to settings for use by plugins.</li>\n<li>Feature &#8211; Wrapping values in quotes now let&#8217;s you use commas in the product CSV importer.</li>\n<li>Feature &#8211; If a fatal error occurs, WooCommerce will catch and log it to be viewed in WC &gt; Status &gt; Logs.</li>\n<li>Feature &#8211; Drag and drop sorting on the grouped product field to control display order.</li>\n<li>Feature &#8211; Integrated selectWoo; more accessible Select2 (enhanced select boxes) in admin and on the front-end.</li>\n<li>Feature &#8211; Enhanced select boxes in the shipping calculator.</li>\n<li>Feature &#8211; Enhanced select boxes in layered nav &#8220;or&#8221; widget.</li>\n<li>Feature &#8211; Ajaxified the product category filter on the products screen.</li>\n<li>Feature &#8211; <code>[products]</code> shortcode can be used in place of other product shortcodes &#8211; one shortcode to rule them all.</li>\n<li>Feature &#8211; Added option to control maximum depth of product category widget, and cleaned up widget naming.</li>\n<li>Feature &#8211; Show sorting options when viewing search results. This defaults to sorting by relevance.</li>\n<li>Feature &#8211; Support for the <code>WC tested up to</code> plugin header to show which extensions have been tested against updates.</li>\n<li>Feature &#8211; Helper &#8211; Filters on the subscription management screen, update notifications, and support for shared licenses.</li>\n<li>Tweak &#8211; Importer now supports menu_order property, adds filename based titles to imported images, and correctly sets post status of variations.</li>\n<li>Tweak &#8211; Made the buyer phone number clickable in the in the order back-end.</li>\n<li>Tweak &#8211; Clean up user is_paying_customer after deleting an order.</li>\n<li>Tweak &#8211; If stock changes between page load and editing, reject stock changes to avoid incorrect stock changes.</li>\n<li>Tweak &#8211; Disable search engines indexing core, dynamic, cart/checkout pages.</li>\n<li>Tweak &#8211; Added shortcodes to description output in structured data, and improved variable product data.</li>\n<li>Tweak &#8211; Use AJAX when restoring an item in the cart, and removing an item from the mini-cart.</li>\n<li>Tweak &#8211; On-boarding: added &#8220;next&#8221; button to pointers and allowed them to be dismissed.</li>\n<li>Tweak &#8211; Display post states for WC pages e.g. shop, checkout etc.</li>\n<li>Tweak &#8211; Improved order tracking page display and validation.</li>\n<li>Tweak &#8211; Wizard improvements, with store-owner newsletter sign-up.</li>\n<li>Tweak &#8211; Improved tax calculations on negative fees by apportioning to all items.</li>\n<li>Tweak &#8211; Added logic to install the plugins and themes asynchronously without using wp-cron.</li>\n<li>Tweak &#8211; Modify product API returned data by context.</li>\n<li>Tweak &#8211; Move js clipboards off of zeroclipboard script.</li>\n<li>Tweak &#8211; Remove spam trap field from registration form.</li>\n<li>Tweak &#8211; Added screen reader text to quantity input template.</li>\n<li>Fix &#8211; Improved error handling in the CSV importer when invalid files are uploaded.</li>\n<li>Fix &#8211; Handle full refunds in tax report by date.</li>\n<li>Fix &#8211; API &#8211; Return empty result when there is no on_sale products.</li>\n<li>Fix &#8211; Fixed WC_Emails::wrap_message hooks .</li>\n<li>Fix &#8211; Load up gateways on ajax order status transitions so PayPal funds capture when order is completed.</li>\n<li>Fix &#8211; Replace wistia videos with youtube.</li>\n<li>Fix &#8211; Handle sale dates on the fly in case of missed cron schedule.</li>\n<li>Fix &#8211; If sorting by date in the REST API, fallback to ID so searches are consistant.</li>\n<li>Fix &#8211; Do not apply custom sorting to product feeds.</li>\n<li>Fix &#8211; Make importer columns case-insensitive.</li>\n<li>Dev &#8211; Make parse_date_for_wp_query public.</li>\n<li>Dev &#8211; API &#8211; Creating webhooks uses the current API version rather than the latest API version.</li>\n<li>Dev &#8211; Product CRUD search helpers.</li>\n<li>Dev &#8211; Refactor shipping rate to include instance IDs, and pass instance IDs through filters.</li>\n<li>Dev &#8211; New attribute helper functions.</li>\n<li>Dev &#8211; Order note helper functions.</li>\n<li>Dev &#8211; Added the &#8220;Terms and conditions&#8221; page to the api system status report.</li>\n<li>Dev &#8211; Made date inputs reusable.</li>\n<li>Dev &#8211; Added option for merging when using &#8216;Order Again&#8217; via filter <code>woocommerce_empty_cart_when_order_again</code>.</li>\n<li>Dev &#8211; Added system status tool for re-populating order address search indexes.</li>\n<li>Dev &#8211; Added system status tool for clearing webhook logs.</li>\n<li>Dev &#8211; Added woocommerce_get_asset_url filter.</li>\n<li>Dev &#8211; Show notice when internal meta props are accessed directly.</li>\n<li>Dev &#8211; Improve meta data updates so data is only updated when changed.</li>\n<li>Dev &#8211; Improved get_filtered_term_product_counts performance.</li>\n<li>Dev &#8211; Introduced wc_get_account_orders_actions function.</li>\n<li>Dev &#8211; <code>wc_get_account_formatted_address</code> can get address by customer ID.</li>\n<li>Dev &#8211; Added <code>woocommerce_get_product_id_by_sku</code> filter.</li>\n<li>Dev &#8211; Refactored cart to use new WC_Cart_Session/WC_Cart_Totals/WC_Cart_Fees/WC_Discounts classes.</li>\n<li>Dev &#8211; New <code>WC_Shortcode_Products</code> class to handle all product based shortcodes.</li>\n<li>Theming &#8211; Display downloads in their own table, universally, using a new template file.</li>\n<li>Theming &#8211; Streamlined email templates content: using the new downloads table, moved billing email with the billing address, order notes into the order totals table, and removed the need for &#8216;downloadable&#8217; subjects/headings.</li>\n<li>Theming &#8211; Checkout: Order pay template</li>\n<li>Localization &#8211; Added cantons of Switzerland.</li>\n<li>Localization &#8211; Updated XAF and XOF currency codes.</li>\n<li>Localization &#8211; Added rtl support for activation.css.</li>\n<li>Localization &#8211; Updated Mexican states to use correct 2 letter codes.</li>\n<li>Localization &#8211; Improved many strings by excluding HTML.</li>\n<li>Many smaller fixes and improvements &#8211; see GitHub!</li>\n</ul>\n<p><a href="https://raw.githubusercontent.com/woocommerce/woocommerce/master/CHANGELOG.txt" rel="nofollow">See changelog for all versions</a>.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/woocommerce/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"All in One SEO Pack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/all-in-one-seo-pack/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wordpress.org/plugins/all-in-one-seo-pack/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 30 Mar 2007 19:30:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/plugins-wp/all-in-one-seo-pack/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:83:"The original SEO plugin for WordPress, downloaded over 30,000,000 times since 2007.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Michael Torbert";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4457:"<p><!--section=description--></p>\n<p>Use <strong>All in One SEO Pack</strong> to optimize your WordPress site for SEO. It&#8217;s easy and works out of the box for beginners, and has advanced features and an API for developers.</p>\n<p><strong><a href="http://semperplugins.com/plugins/all-in-one-seo-pack-pro-version/?loc=readme_utpv" rel="nofollow">Upgrade to Pro Version</a></strong></p>\n<p><a href="http://semperplugins.com/support/?loc=readme_ps" rel="nofollow">Premium Support</a></p>\n<p>First created in 2007, see why AIOSEO is one of the all time most downloaded plugins for WordPress.</p>\n<ul>\n<li>XML Sitemap support &#8211; submit your sitemap to Google and Bing and improve your SEO</li>\n<li>Image XML Sitemap submitted to Google and Bing to improve your Image SEO</li>\n<li>Google AMP support (Accelerated Mobile Pages)</li>\n<li>Google Analytics support</li>\n<li>Support for SEO on Custom Post Types</li>\n<li>Advanced Canonical URLs</li>\n<li>Redirect attachment pages to parent post</li>\n<li>Automatically notifies search engines like Google and Bing about changes to your site</li>\n<li>Built-in API so other plugins/themes can access and extend functionality</li>\n<li>ONLY free plugin to provide SEO Integration for e-Commerce sites, including WooCommerce</li>\n<li>Nonce Security built into All in One SEO Pack</li>\n<li>Automatically optimizes your <strong>titles</strong> for Google and other search engines</li>\n<li>Generates <strong>META tags automatically</strong></li>\n<li>Avoids the typical duplicate content found on WordPress blogs</li>\n<li>For beginners, you don&#8217;t even have to look at the options, it works out-of-the-box. Just install.</li>\n<li>For advanced users, you can fine-tune everything to optimize your SEO</li>\n<li>You can override any title and set any META description and any META keywords you want.</li>\n<li>Compatibility with many other plugins</li>\n<li>Translated into 57 languages</li>\n<li>PHP 7 100% Compatible</li>\n</ul>\n<p>Follow me on Twitter to keep up with the latest updates <a href="http://twitter.com/michaeltorbert/" rel="nofollow">Michael<br />\nTorbert</a></p>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/46MR4FboMaA?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n<p><!--section=faq--></p>\n<p>Please visit our complete <strong><a href="http://semperplugins.com/documentation/" rel="nofollow">Documentation</a></strong> before requesting support for SEO from the<br />\n<strong><a href="http://semperplugins.com/support/" rel="nofollow">All in One SEO Pack Support Forum</a></strong></p>\n<p><a href="http://semperfiwebdesign.com/documentation/all-in-one-seo-pack/translations-for-all-in-one-seo-pack/" rel="nofollow">Translations</a></p>\n<dl>\n<dt>General Settings</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/uGt6CVbA5bI?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n<dt>XML Sitemaps</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/zvNU92Low8A?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n<dt>Social Meta</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/Dfe49FiiAog?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n<dt>Performance</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/A0VKinM5s00?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<p>All in One SEO Pack <a href="http://semperfiwebdesign.com/documentation/all-in-one-seo-pack/all-in-one-seo-pack-release-history/" rel="nofollow">Changelog</a></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/all-in-one-seo-pack/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"Google XML Sitemaps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/google-sitemap-generator/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:63:"https://wordpress.org/plugins/google-sitemap-generator/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jun 2005 09:33:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/plugins-wp/google-sitemap-generator/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:94:"This plugin will improve SEO by helping search enginess better index your site using sitemaps.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Arne Brachhold";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:27964:"<p><!--section=description--></p>\n<p>Use this plugin to greatly improve SEO to create special XML sitemaps which will help search engines like Google, Bing, Yahoo and Ask.com to better index your site.</p>\n<p>With such a sitemap, it&#8217;s much easier for the crawlers to see the complete structure of your site and retrieve it more efficiently. The plugin supports all kinds of WordPress generated pages as well as custom URLs. Additionally it notifies all major search engines every time you create a post about the new content.</p>\n<p>Supported since <em>over 9 years</em> and rated as the <a href="https://wordpress.org/plugins/browse/top-rated/">best WordPress plugin</a>, it will do exactly what it&#8217;s supposed to do &#8211; providing a complete XML sitemap for search engines. It will not break your site, slow it down or annoy you. Guaranteed!</p>\n<blockquote>\n<p>If you like the plugin, feel free to rate it (on the right side of this page)! <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f642.png" alt="?" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n</blockquote>\n<p>Related Links:</p>\n<ul>\n<li><a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/" title="Google XML Sitemaps Plugin for WordPress" rel="nofollow">Plugin Homepage</a></li>\n<li><a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/changelog/" title="Changelog of the Google XML Sitemaps Plugin for WordPress" rel="nofollow">Changelog</a></li>\n<li><a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/help/" title="Google Sitemaps FAQ" rel="nofollow">Plugin help and sitemaps FAQ</a></li>\n<li><a href="https://wordpress.org/support/topic/read-before-opening-a-new-support-topic" rel="nofollow">Support Forum</a></li>\n</ul>\n<h3>License</h3>\n<p>Good news, this plugin is free for everyone! Since it&#8217;s released under the GPL, you can use it free of charge on your personal or commercial site.</p>\n<h3>Translations</h3>\n<p>The plugin comes with various translations, please refer to the <a href="https://codex.wordpress.org/Installing_WordPress_in_Your_Language" title="Installing WordPress in Your Language" rel="nofollow">WordPress Codex</a> for more information about activating the translation. If you want to help to translate the plugin to your language, please have a look at the sitemap.pot file which contains all definitions and may be used with a <a href="http://www.gnu.org/software/gettext/" rel="nofollow">gettext</a> editor like <a href="http://www.poedit.net/" rel="nofollow">Poedit</a> (Windows).</p>\n<p><!--section=installation--></p>\n<ol>\n<li>Install the plugin like you always install plugins, either by uploading it via FTP or by using the &#8220;Add Plugin&#8221; function of WordPress.</li>\n<li>Activate the plugin at the plugin administration page</li>\n<li>If you want: Open the plugin configuration page, which is located under Settings -&gt; XML-Sitemap and customize settings like priorities and change frequencies.</li>\n<li>The plugin will automatically update your sitemap of you publish a post, so there is nothing more to do <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f642.png" alt="?" class="wp-smiley" style="height: 1em; max-height: 1em;" /></li>\n</ol>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<ol>\n<li>Install the plugin like you always install plugins, either by uploading it via FTP or by using the &#8220;Add Plugin&#8221; function of WordPress.</li>\n<li>Activate the plugin at the plugin administration page</li>\n<li>If you want: Open the plugin configuration page, which is located under Settings -&gt; XML-Sitemap and customize settings like priorities and change frequencies.</li>\n<li>The plugin will automatically update your sitemap of you publish a post, so there is nothing more to do <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f642.png" alt="?" class="wp-smiley" style="height: 1em; max-height: 1em;" /></li>\n</ol>\n</dd>\n<dt>Where can I find the options page of the plugin?</dt>\n<dd>\n<p>It is under Settings &gt; XML Sitemap. I know nowadays many plugins add top-level menu items, but in most of the cases it is just not necessary. I&#8217;ve seen WP installations which looked like an Internet Explorer ten years ago with 20 toolbars installed. <img src="https://s.w.org/images/core/emoji/2.4/72x72/1f609.png" alt="?" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n</dd>\n<dt>Do I have to create a sitemap.xml and sitemap.xml.gz by myself?</dt>\n<dd>\n<p>Not anymore. Since version 4, these files are dynamically generated. <em>There must be no sitemap.xml or sitemap.xml.gz in your site directory anymore!</em> The plugin will try to rename them to sitemap.xml.bak if they still exists.</p>\n</dd>\n<dt>Does this plugin use static files or &#8220;I can&#8217;t find the sitemap.xml file!&#8221;</dt>\n<dd>\n<p>Not anymore. Since version 4, these files are dynamically generated just like any other WordPress content.</p>\n</dd>\n<dt>There are no comments yet (or I&#8217;ve disabled them) and all my postings have a priority of zero!</dt>\n<dd>\n<p>Please disable automatic priority calculation and define a static priority for posts.</p>\n</dd>\n<dt>So many configuration options&#8230; Do I need to change them?</dt>\n<dd>\n<p>No, only if you want to. Default values are ok for most sites.</p>\n</dd>\n<dt>Does this plugin work with all WordPress versions?</dt>\n<dd>\n<p>This version works with WordPress 3.3 and better. If you&#8217;re using an older version, please check the <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/" title="Google (XML) Sitemap Generator Plugin Homepage" rel="nofollow">Google Sitemaps Plugin Homepage</a> for the legacy releases. There is a working release for every WordPress version since 1.5, but you really should consider updating your WordPress installation!</p>\n</dd>\n<dt>My question isn&#8217;t answered here</dt>\n<dd>\n<p>Most of the plugin options are described at the <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/" rel="nofollow">plugin homepage</a> as well as the dedicated <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/help/" title="List of common questions / problems regarding Google (XML) Sitemaps" rel="nofollow">Google Sitemaps FAQ</a>.</p>\n</dd>\n<dt>My question isn&#8217;t even answered there</dt>\n<dd>\n<p>Please post your question at the <a href="https://wordpress.org/support/topic/read-before-opening-a-new-support-topic" rel="nofollow">WordPress support forum</a> and tag your post with &#8220;google-sitemap-generator&#8221;.</p>\n</dd>\n<dt>What&#8217;s new in the latest version?</dt>\n<dd>\n<p>The changelog is maintained <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/changelog/" title="Google (XML) Sitemap Generator Plugin Changelog" rel="nofollow">here</a></p>\n</dd>\n<dt>Why is the changelog on a separate page and not here?</dt>\n<dd>\n<p>The WordPress.org repository is just another place to download this plugin. I don&#8217;t want to maintain too many pages with the same content. Thank you for your understanding!</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>4.0.9 (2017-07-24)</h4>\n<ul>\n<li>Fixed security issue related to donation functionality.</li>\n</ul>\n<h4>4.0.8 (2014-11-15)</h4>\n<ul>\n<li>Fixed bug regarding the exclude categories feature, thanks to Claus Schöffel!</li>\n</ul>\n<h4>4.0.7.1 (2014-09-02)</h4>\n<ul>\n<li>Sorry, no new features this time… This release only updates the Compatibility-Tag to WordPress 4.0. Unfortunately there is no way to do this anymore without a new version</li>\n</ul>\n<h4>4.0.7 (2014-06-23)</h4>\n<ul>\n<li>Better compatibility with GoDaddy managed WP hosting</li>\n<li>Better compatibility with QuickCache</li>\n<li>Removed WordPress version from the sitemap</li>\n<li>Corrected link to WordPress privacy settings (if search engines are blocked)</li>\n<li>Changed hook which is being used for sitemap pings to avoid pings on draft edit</li>\n</ul>\n<h4>4.0.6 (2014-06-03)</h4>\n<ul>\n<li>Added option to disable automatic gzipping</li>\n<li>Fixed bug with duplicated external sitemap entries</li>\n<li>Don’t gzip if behind Varnish since Varnish can do that</li>\n</ul>\n<h4>4.0.5 (2014-05-18)</h4>\n<ul>\n<li>Added function to manually start ping for main-sitemap or all sub-sitemaps</li>\n<li>Added support for changing the base of the sitemap URL to another URL (for WP installations in sub-folders)</li>\n<li>Fixed issue with empty post sitemaps (related to GMT/local time offset)</li>\n<li>Fixed some timing issues in archives</li>\n<li>Improved check for possible problems before gzipping</li>\n<li>Fixed empty archives and author sitemaps in case there were no posts</li>\n<li>Fixed bug which caused the Priority Provider to disappear in recent PHP versions</li>\n<li>Plugin will also ping with the corresponding sub-sitemap in case a post was modified</li>\n<li>Better checking for empty external urls</li>\n<li>Changed text in XSL template to be more clear about sitemap-index and sub-sitemaps</li>\n<li>Changed content type to text/xml to improve compatibility with caching plugins</li>\n<li>Changed query parameters to is_feed=true to improve compatibility with caching plugins</li>\n<li>Switched from using WP_Query to load posts to a custom SQL statement to avoid problems with other plugin filters</li>\n<li>Added caching of some SQL statements</li>\n<li>Added support feed for more help topics</li>\n<li>Added link to new help page</li>\n<li>Cleaned up code and renamed variables to be more readable</li>\n<li>Updated Japanese Translation, thanks to Daisuke Takahashi</li>\n</ul>\n<h4>4.0.4 (2014-04-19)</h4>\n<ul>\n<li>Removed deprecated get_page call</li>\n<li>Changed last modification time of sub-sitemaps to the last modification date of the posts instead of the publish date</li>\n<li>Removed information window if the statistic option has not been activated</li>\n<li>Added link regarding new sitemap format</li>\n<li>Updated Portuguese translation, thanks to Pedro Martinho</li>\n<li>Updated German translation</li>\n</ul>\n<h4>4.0.3 (2014-04-13)</h4>\n<ul>\n<li>Fixed compression if an gzlib handler was already active</li>\n<li>Help regarding permalinks for Nginx users</li>\n<li>Fix with gzip compression in case there was other output before already</li>\n<li>Return 404 for HTML sitemaps if the option has been disabled</li>\n<li>Updated translations</li>\n</ul>\n<h4>4.0.2 (2014-04-01)</h4>\n<ul>\n<li>Fixed warning if an gzip handler is already active</li>\n</ul>\n<h4>4.0.1 (2014-03-31)</h4>\n<ul>\n<li>Fixed bug with custom post types including a &#8220;-&#8220;</li>\n<li>Fixed some 404 Not Found Errors</li>\n</ul>\n<h4>4.0 (2014-03-30)</h4>\n<ul>\n<li>No static files anymore, sitemap is created on the fly!</li>\n<li>Sitemap is split-up into sub-sitemaps by month, allowing up to 50.000 posts per month! <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/google-xml-sitemap-generator-new-sitemap-format/" rel="nofollow">More information</a></li>\n<li>Support for custom post types and custom taxonomis!</li>\n<li>100% Multisite compatible, including by-blog and network activation.</li>\n<li>Reduced server resource usage due to less content per request.</li>\n<li>New API allows other plugins to add their own, separate sitemaps.</li>\n<li>Note: PHP 5.1 and WordPress 3.3 is required! The plugin will not work with lower versions!</li>\n<li>Note: This version will try to rename your old sitemap files to *-old.xml. If that doesn’t work, please delete them manually since no static files are needed anymore!</li>\n</ul>\n<h4>3.4.1 (2014-04-10)</h4>\n<ul>\n<li>Compatibility with mysqli</li>\n</ul>\n<h4>Version 3.4 (2013-11-24)</h4>\n<ul>\n<li>Fixed deprecation warnings in PHP 5.4, thanks to Dion Hulse!</li>\n</ul>\n<h4>3.3 (2013-09-28)</h4>\n<ul>\n<li>Fixed problem with file permission checking</li>\n<li>Filter out hashs (#) in URLs</li>\n</ul>\n<h4>3.2.9 (2013-01-11)</h4>\n<ul>\n<li>Fixed security issue with change frequencies and filename of sitemap file. Exploit was only possible with admin account.</li>\n</ul>\n<h4>3.2.8 (2012-08-08)</h4>\n<ul>\n<li>Fixed wrong custom taxonomy URLs, thanks to ramon fincken of the wordpress.org forum!</li>\n<li>Removed ASK ping since they shut down their service.</li>\n<li>Exclude post_format taxonomy from custom taxonomy list</li>\n</ul>\n<h4>3.2.7 (2012-04-24)</h4>\n<ul>\n<li>Fixed custom post types, thanks to clearsite of the wordpress.org forum!</li>\n<li>Fixed broken admin layout on WP 3.4</li>\n</ul>\n<h4>3.2.6 (2011-09-19)</h4>\n<ul>\n<li>Removed YAHOO ping since YAHOO uses bing now</li>\n<li>Removed deprecated function call</li>\n</ul>\n<h4>3.2.5 (2011-07-11)</h4>\n<ul>\n<li>Backported Bing ping success fix from beta</li>\n<li>Added friendly hint to try out the new beta</li>\n</ul>\n<h4>3.2.4 (2010-05-29)</h4>\n<ul>\n<li>Added (GMT) to date column in sitemap xslt template to avoid confusion with different time zones</li>\n<li>Fixed wrong SQL statement for author pages, thanks to twoenoug</li>\n<li>Fixed several deprecated function calls</li>\n<li>Note: This release does not support the new multisite feature of WordPress yet and will not be active when multisite is enabled.</li>\n</ul>\n<h4>3.2.3 (2010-04-02)</h4>\n<ul>\n<li>Fixed that all pages were missing in the sitemap if the “Uncategorized” category was excluded</li>\n</ul>\n<h4>3.2.2 (2009-12-19)</h4>\n<ul>\n<li>Updated compatibility tag to WordPress 2.9</li>\n<li>Fixed PHP4 problems</li>\n</ul>\n<h4>3.2.1 (2009-12-16)</h4>\n<ul>\n<li>Notes and update messages at the top of the admin page could interfere with the manual build function</li>\n<li>Help links in the WP contextual help were not shown anymore since the last update</li>\n<li>IE 7 sometimes displayed a cached admin page</li>\n<li>Removed invalid link to config page from the plugin description (The link lead to a &#8220;Not enough permission error&#8221;)</li>\n<li>Improved performance of getting the current plugin version by caching</li>\n<li>Updated Spanish language files</li>\n</ul>\n<h4>3.2 (2009-11-23)</h4>\n<ul>\n<li>Added function to show the actual results of a ping instead of only linking to the url</li>\n<li>Added new hook (sm_rebuild) for third party plugins to start building the sitemap</li>\n<li>Fixed bug which showed the wrong URL for the latest Google ping result</li>\n<li>Added some missing documentation</li>\n<li>Removed hardcoded php name for sitemap file in admin urls</li>\n<li>Uses KSES for showing ping test results</li>\n<li>Ping test fixed for WP &lt; 2.3</li>\n</ul>\n<h4>3.1.9 (2009-11-13)</h4>\n<ul>\n<li>Fixed MySQL Error if author pages were included</li>\n</ul>\n<h4>3.1.8 (2009-11-07)</h4>\n<ul>\n<li>Improved custom taxonomy handling and fixed wrong last modification date</li>\n<li>Fixed fatal error in WordPress versions lower than 2.3</li>\n<li>Fixed Update Notice for WordPress 2.8 and higher</li>\n<li>Added warning if blog privacy is activated</li>\n<li>Fixed priorities of additional pages were shown as 0 instead of 1</li>\n</ul>\n<h4>3.1.7 (2009-10-21)</h4>\n<ul>\n<li>Added support for custom taxonomies. Thanks to Lee!</li>\n</ul>\n<h4>3.1.6 (2009-08-31)</h4>\n<ul>\n<li>Fixed PHP error “Only variables can be passed by reference”</li>\n<li>Fixed wrong URLS of multi-page posts (Thanks artstorm!)</li>\n<li>Updated many language files</li>\n</ul>\n<h4>3.1.5 (2009-08-24)</h4>\n<ul>\n<li>Added option to completely disable the last modification time</li>\n<li>Fixed problem with HTTPS url for the XSL stylesheet if the sitemap was build via the admin panel</li>\n<li>Improved handling of homepage entry if a single page was set for it</li>\n<li>Fixed mktime warning which appeared sometimes</li>\n<li>Fixed bug which caused inf. reloads after rebuilding the sitemap via the admin panel</li>\n<li>Improved handling of missing sitemaps files if WP was moved to another location</li>\n</ul>\n<h4>3.1.4 (2009-06-22)</h4>\n<ul>\n<li>Fixed bug which broke all pings in WP older than 2.7</li>\n<li>Added more output in debug mode if pings fail</li>\n<li>Moved global post variable so other plugins can use it in get_permalink()</li>\n<li>Added small icon for ozh admin menu</li>\n<li>Added more help links in UI</li>\n</ul>\n<h4>3.1.3 (2009-06-07)</h4>\n<ul>\n<li>Changed MSN Live Search to Bing</li>\n<li>Exclude categories also now exludes the category itself and not only the posts</li>\n<li>Pings now use the new WordPress HTTP API instead of Snoopy</li>\n<li>Fixed bug that in localized WP installations priorities could not be saved</li>\n<li>The sitemap cron job is now cleared after a manual rebuild or after changing the config</li>\n<li>Adjusted style of admin area for WP 2.8 and refreshed icons</li>\n<li>Disabled the “Exclude categories” feature for WP 2.5.1, since it doesn’t have the required functions yet</li>\n</ul>\n<h4>3.1.2 (2008-12-26)</h4>\n<ul>\n<li>Changed the way the stylesheet is saved (default / custom stylesheet)</li>\n<li>Sitemap is now rebuild when a page is published</li>\n<li>Removed support for static robots.txt files, this is now handled via WordPress functions</li>\n<li>Added compat. exceptions for WP 2.0 and WP 2.1</li>\n</ul>\n<h4>3.1.1 (2008-12-21)</h4>\n<ul>\n<li>Fixed redirect issue if wp-admin is rewritten via mod_rewrite, thanks to macjoost</li>\n<li>Fixed wrong path to assets, thanks PozHonks</li>\n<li>Fixed wrong plugin URL if wp-content was renamed / redirected, thanks to wnorris</li>\n<li>Updated WP User Interface for 2.7</li>\n<li>Various other small things</li>\n</ul>\n<h4>3.1.0.1 (2008-05-27)</h4>\n<ul>\n<li>Extracted UI JS to external file</li>\n<li>Enabled the option to include following pages of multi-page posts</li>\n<li>Script tries to raise memory and time limit if active</li>\n</ul>\n<h4>3.1 (2008-05-22)</h4>\n<ul>\n<li>Marked as stable</li>\n</ul>\n<h4>3.1b3 (2008-05-19)</h4>\n<ul>\n<li>Cleaned up plugin directory and moved img files to subfolders</li>\n<li>Fixed background building bug in WP 2.1</li>\n<li>Removed auto-update plugin link for WP &lt; 2.5</li>\n</ul>\n<h4>3.1b2 (2008-05-18)</h4>\n<ul>\n<li>Fixed critical bug with the build in background option</li>\n<li>Added notification if a build is scheduled</li>\n</ul>\n<h4>3.1b1 (2008-05-08)</h4>\n<ul>\n<li>Splitted plugin in loader, generator and user interface to save memory</li>\n<li>Generator and UI will only be loaded when needed</li>\n<li>Secured all admin actions with nonces</li>\n<li>Improved WP 2.5 handling</li>\n<li>New &#8220;Suggest a Feature&#8221; link</li>\n</ul>\n<h4>3.0.3.3 (2008-04-29)</h4>\n<ul>\n<li>Fixed author pages</li>\n<li>Enhanced background building and increased delay to 15 seconds</li>\n<li>Enabled background building by default</li>\n</ul>\n<h4>3.0.3.2 (2008-04-28)</h4>\n<ul>\n<li>Improved WP 2.5 handling (fixes blank screens and timeouts)</li>\n</ul>\n<h4>3.0.3.1 (2008-03-30)</h4>\n<ul>\n<li>Added compatibility CSS for WP 2.5</li>\n</ul>\n<h4>3.0.3 (2007-12-30)</h4>\n<ul>\n<li>Added option to ping MSN Live Search</li>\n<li>Removed some WordPress hooks (the sitemap isn’t updates with every comment anymore)</li>\n</ul>\n<h4>3.0.2.1 (2007-11-28)</h4>\n<ul>\n<li>Fixed wrong XML Schema Location (Thanks to Emanuele Tessore)</li>\n<li>Added Russian Language files by Sergey http://ryvkin.ru</li>\n</ul>\n<h4>3.0.2 (2007-11-25)</h4>\n<ul>\n<li>Fixed bug which caused that some settings were not saved correctly</li>\n<li>Added option to exclude pages or post by ID</li>\n<li>Restored YAHOO ping service with API key since the other one is to unreliable</li>\n</ul>\n<h4>3.0.1 (2007-11-03)</h4>\n<ul>\n<li>Changed HTTP client for ping requests to Snoopy</li>\n<li>Added &#8220;safemode&#8221; for SQL which doesn’t use unbuffered results</li>\n<li>Added option to run the building process in background using wp-cron</li>\n<li>Added links to test the ping if it failed</li>\n</ul>\n<h4>3.0 final (2007-09-24)</h4>\n<ul>\n<li>Marked as stable</li>\n<li>Removed useless functions</li>\n</ul>\n<h4>3.0b11 (2007-09-23)</h4>\n<ul>\n<li>Changed mysql queries to unbuffered queries</li>\n<li>Uses MUCH less memory</li>\n<li>Option to limit the number of posts</li>\n</ul>\n<h4>3.0b10 (2007-09-04)</h4>\n<ul>\n<li>Added category support for WordPress 2.3</li>\n<li>Fixed bug with empty URLs in sitemap</li>\n<li>Repaired GET building</li>\n</ul>\n<h4>3.0b9 (2007-09-02)</h4>\n<ul>\n<li>Added tag support for WordPress 2.3</li>\n<li>Fixed archive bug with static pages (Thanks to Peter Claus Lamprecht)</li>\n<li>Fixed some missing translation strings, thanks to Kirin Lin</li>\n</ul>\n<h4>3.0b8 (2007-07-22)</h4>\n<ul>\n<li>Fixed bug with empty categories</li>\n<li>Fixed bug with translation plugins</li>\n<li>Added support for robots.txt</li>\n<li>Switched YAHOO ping API from YAHOO Web Services to the “normal” ping service</li>\n<li>Search engines will only be pinged if the sitemap file has changed</li>\n</ul>\n<h4>3.0b7 (2007-05-17)</h4>\n<ul>\n<li>Added Ask.com notification</li>\n<li>Added option to include the author pages like /author/john</li>\n<li>Fixed WP 2.1 / Pre 2.1 post / pages database changes</li>\n<li>Added check to not build the sitemap if importing posts</li>\n<li>Fixed wrong XSLT location (Thanks froosh)</li>\n<li>Small enhancements and bug fixes</li>\n</ul>\n<h4>3.0b6 (2007-01-23)</h4>\n<ul>\n<li>sitemap.xml.gz was not compressed</li>\n<li>YAHOO update-notification was PHP5 only (Thanks to Joseph Abboud!)</li>\n<li>More WP 2.1 optimizations</li>\n<li>Reduced memory usage with PHP5</li>\n</ul>\n<h4>3.0b5 (2007-01-19)</h4>\n<ul>\n<li>WordPress 2 Design</li>\n<li>YAHOO update notification</li>\n<li>New status report, removed ugly logfiles</li>\n<li>Added option to define a XSLT stylesheet and added a default one</li>\n<li>Fixed bug with sub-pages, thanks to <a href="http://baptiste.us/" rel="nofollow">Mike</a>, <a href="http://fastagent.de/" rel="nofollow">Peter</a> and <a href="http://publicityship.com.au/" rel="nofollow">Glenn</a></li>\n<li>Improved file handling, thanks to <a href="http://www.vjtd3.com/" rel="nofollow">VJTD3</a></li>\n<li>WP 2.1 improvements</li>\n</ul>\n<h4>3.0b4 (2006-11-16)</h4>\n<ul>\n<li>Fixed some smaller bugs</li>\n<li>Decreased memory usage which should solve timeout and memory problems</li>\n<li>Updated namespace to support YAHOO and MSN</li>\n</ul>\n<h4>3.0b2 (2006-01-14)</h4>\n<ul>\n<li>Fixed several bugs reported by users</li>\n</ul>\n<h4>3.0b (2005-11-25)</h4>\n<ul>\n<li>WordPress 2.0 (Beta, RC1) compatible</li>\n<li>Added different priority calculation modes and introduced an API to create custom ones (Some people didn’t like the way to calculate the post priority based on the count of user comments. This will give you the possibility to develop custom priority providers which fit your needs.)</li>\n<li>Added support to use the <a href="http://www.alexking.org/blog/2005/07/27/popularity-contest-11/" rel="nofollow">Popularity Contest</a> plugin by <a href="http://www.alexking.org/" rel="nofollow">Alex King</a> to calculate post priority (If you are already using the Popularity Contest plugin, this will be the best way to determine the priority of the posts. Uses to new priority API noted above.)</li>\n<li>Added option to exclude password protected posts (This was one of the most requested features.)</li>\n<li>Posts and pages marked for publish with a date in the future won’t be included</li>\n<li>Added function to start sitemap creation via GET and a secret key (If you are using external software which directly writes into the database without using the WordPress API, you can rebuild the sitemap with a simple HTTP Request. This can be made with a cron job for example.)</li>\n<li>Improved compatibility with other plugins (There should no longer be problems with other plugins now which checked for existence of a specified function to determine if you are in the control panel or not.)</li>\n<li>Recoded plugin architecture which is now fully OOP (The code is now cleaner and better to understand which makes it easier to modify. This should also avoid namespace problems.)</li>\n<li>Improved speed and optimized settings handling (Settings and pages are only loaded if the sitemap generation process starts and not every time a page loads. This saves one MySQL Query on every request.)</li>\n<li>Added Button to restore default configuration (Messed up the config? You’ll need just one click to restore all settings.)</li>\n<li>Added log file to check everything is running (In the new log window you can see when your sitemap was rebuilt or if there was any error.)</li>\n<li>Improved user-interface</li>\n<li>Added several links to homepage and support (This includes the Notify List about new releases and the WordPress support forum.)</li>\n</ul>\n<h4>2.7 (2005-11-25)</h4>\n<ul>\n<li>Added Polish Translation by <a href="http://kubazwolinski.com/" rel="nofollow">kuba</a></li>\n</ul>\n<h4>2.7 (2005-11-01)</h4>\n<ul>\n<li>Added French Translation by <a href="http://www.chezthierry.info/" rel="nofollow">Thierry Lanfranchi</a></li>\n</ul>\n<h4>2.7 (2005-07-21)</h4>\n<ul>\n<li>Fixed bug with incorrect date in additional pages (wrong format)</li>\n<li>Added Swedish Translation by <a href="http://tobiasbergius.se/" rel="nofollow">Tobias Bergius</a></li>\n</ul>\n<h4>2.6 (2005-07-16)</h4>\n<ul>\n<li>Included Chinese (Simplified) language files by <a href="http://www.june6.cn/" rel="nofollow">june6</a></li>\n</ul>\n<h4>2.6 (2005-07-04)</h4>\n<ul>\n<li>Added support to store the files at a custom location</li>\n<li>Changed the home URL to have a slash at the end</li>\n<li>Fixed errors with wp-mail</li>\n<li>Added support for other plugins to add content to the sitemap</li>\n</ul>\n<h4>2.5 (2005-06-15)</h4>\n<ul>\n<li>You can include now external pages which aren’t generated by WordPress or are not recognized by this plugin</li>\n<li>You can define a minimum post priority, which will overrride the calculated value if it’s too low</li>\n<li>The plugin will automatically ping Google whenever the sitemap gets regenerated</li>\n<li>Update 1: Included Spanish translations by <a href="http://www.cesargomez.org/" rel="nofollow">Cesar Gomez Martin</a></li>\n<li>Update 2: Included Italian translations by <a href="http://wordpress-it.it/" rel="nofollow">Stefano Aglietti</a></li>\n<li>Update 3: Included Traditional Chinese translations by <a href="http://kirin-lin.idv.tw/" rel="nofollow">Kirin Lin</a></li>\n</ul>\n<h4>2.2 (2005-06-08)</h4>\n<ul>\n<li>Language file support: <a href="http://hiromasa.zone.ne.jp/" rel="nofollow">Hiromasa</a> from <a href="http://hiromasa.zone.ne.jp/" rel="nofollow">http://hiromasa.zone.ne.jp</a> sent me a japanese version of the user interface and modified the script to support it! Thanks for this! Check <a href="https://codex.wordpress.org/WordPress_Localization" rel="nofollow">the WordPress Codex</a> how to set the language in WordPress.</li>\n<li>Added Japanese user interface by <a href="http://hiromasa.zone.ne.jp/" rel="nofollow">Hiromasa</a></li>\n<li>Added German user interface by me</li>\n</ul>\n<h4>2.12 (2005-06-07)</h4>\n<ul>\n<li>Changed SQL Statement for categories that it also works on MySQL 3</li>\n</ul>\n<h4>2.11 (2005-06-07)</h4>\n<ul>\n<li>Fixed a hardcoded tablename which made a SQL error</li>\n</ul>\n<h4>2.1 (2005-06-07)</h4>\n<ul>\n<li>Can also generate a gzipped version of the xml file (sitemap.xml.gz)</li>\n<li>Uses correct last modification dates for categories and archives. (Thanks to thx <a href="http://www.shupe.ca/" rel="nofollow">Rodney Shupe</a> for the SQL)</li>\n<li>Supports now different WordPress / Blog directories</li>\n<li>Fixed bug which ignored different post/page priorities (Reported by <a href="http://h3h.net/" rel="nofollow">Brad</a>)</li>\n</ul>\n<h4>2.01 (2005-06-07)</h4>\n<ul>\n<li>Fixed compatibility for PHP installations which are not configured to use short open tags</li>\n<li>Changed Line 147 from _e($i); to _e(strval($i));</li>\n<li>Thanks to <a href="http://publicvoidblog.de/" rel="nofollow">Christian Aust</a> for reporting this!</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"https://wordpress.org/plugins/google-sitemap-generator/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"Limit Login Attempts";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/plugins/limit-login-attempts/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wordpress.org/plugins/limit-login-attempts/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 15 Jan 2009 14:20:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:54:"https://wordpress.org/plugins-wp/limit-login-attempts/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:91:"Limit rate of login attempts, including by way of cookies, for each IP. Fully customizable.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"johanee";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:12097:"<p><!--section=description--></p>\n<p>Limit the number of login attempts possible both through normal login as well as using auth cookies.</p>\n<p>By default WordPress allows unlimited login attempts either through the login page or by sending special cookies. This allows passwords (or hashes) to be brute-force cracked with relative ease.</p>\n<p>Limit Login Attempts blocks an Internet address from making further attempts after a specified limit on retries is reached, making a brute-force attack difficult or impossible.</p>\n<p>Features</p>\n<ul>\n<li>Limit the number of retry attempts when logging in (for each IP). Fully customizable</li>\n<li>Limit the number of attempts to log in using auth cookies in same way</li>\n<li>Informs user about remaining retries or lockout time on login page</li>\n<li>Optional logging, optional email notification</li>\n<li>Handles server behind reverse proxy</li>\n<li>It is possible to whitelist IPs using a filter. But you probably shouldn&#8217;t. ?</li>\n</ul>\n<p>Translations: Bulgarian, Brazilian Portuguese, Catalan, Chinese (Traditional), Czech, Dutch, Finnish, French, German, Hungarian, Norwegian, Persian, Romanian, Russian, Spanish, Swedish, Turkish</p>\n<p>Plugin uses standard actions and filters only.</p>\n<p><!--section=installation--></p>\n<ol>\n<li>Download and extract plugin files to a wp-content/plugin directory.</li>\n<li>Activate the plugin through the WordPress admin interface.</li>\n<li>Customize the settings on the options page, if desired. If your server is located behind a reverse proxy make sure to change this setting.</li>\n</ol>\n<p>If you have any questions or problems please make a post here: https://wordpress.org/tags/limit-login-attempts</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<ol>\n<li>Download and extract plugin files to a wp-content/plugin directory.</li>\n<li>Activate the plugin through the WordPress admin interface.</li>\n<li>Customize the settings on the options page, if desired. If your server is located behind a reverse proxy make sure to change this setting.</li>\n</ol>\n<p>If you have any questions or problems please make a post here: https://wordpress.org/tags/limit-login-attempts</p>\n</dd>\n<dt>Why not reset failed attempts on a successful login?</dt>\n<dd>\n<p>This is very much by design. Otherwise you could brute force the &#8220;admin&#8221; password by logging in as your own user every 4th attempt.</p>\n</dd>\n<dt>What is this option about site connection and reverse proxy?</dt>\n<dd>\n<p>A reverse proxy is a server in between the site and the Internet (perhaps handling caching or load-balancing). This makes getting the correct client IP to block slightly more complicated.</p>\n<p>The option default to NOT being behind a proxy &#8212; which should be by far the common case.</p>\n</dd>\n<dt>How do I know if my site is behind a reverse proxy?</dt>\n<dd>\n<p>You probably are not or you would know. We show a pretty good guess on the option page. Set the option using this unless you are sure you know better.</p>\n</dd>\n<dt>Can I whitelist my IP so I don&#8217;t get locked out?</dt>\n<dd>\n<p>First please consider if you really need this. Generally speaking it is not a good idea to have exceptions to your security policies.</p>\n<p>That said, there is now a filter which allows you to do it: &#8220;limit_login_whitelist_ip&#8221;.</p>\n<p>Example:<br />\nfunction my_ip_whitelist($allow, $ip) {<br />\n     return ($ip == &#8216;my-ip&#8217;) ? true : $allow;<br />\n}<br />\nadd_filter(&#8216;limit_login_whitelist_ip&#8217;, &#8216;my_ip_whitelist&#8217;, 10, 2);</p>\n<p>Note that we still do notification and logging as usual. This is meant to allow you to be aware of any suspicious activity from whitelisted IPs.</p>\n</dd>\n<dt>I locked myself out testing this thing, what do I do?</dt>\n<dd>\n<p>Either wait, or:</p>\n<p>If you know how to edit / add to PHP files you can use the IP whitelist functionality described above. You should then use the &#8220;Restore Lockouts&#8221; button on the plugin settings page and remove the whitelist function again.</p>\n<p>If you have ftp / ssh access to the site rename the file &#8220;wp-content/plugins/limit-login-attempts/limit-login-attempts.php&#8221; to deactivate the plugin.</p>\n<p>If you have access to the database (for example through phpMyAdmin) you can clear the limit_login_lockouts option in the wordpress options table. In a default setup this would work: &#8220;UPDATE wp_options SET option_value = &#8221; WHERE option_name = &#8216;limit_login_lockouts''&#8221;</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>1.7.1</h4>\n<p>This version fixes a security bug in version 1.6.2 and 1.7.0. Please upgrade immediately.</p>\n<p>&#8220;Auth cookies&#8221; are special cookies set at login that authenticating you to the system. It is how WordPress &#8220;remembers&#8221; that you are logged in between page loads.</p>\n<p>During lockout these are supposed to be cleared, but a change in 1.6.2 broke this. It allowed an attacker to keep trying to break these cookies during a lockout.</p>\n<p>Lockout of normal password login attempts still worked as it should, and it appears that all &#8220;auth cookie&#8221; attempts would keep getting logged.</p>\n<p>In theory the &#8220;auth cookie&#8221; is quite resistant to brute force attack. It contains a cryptographic hash of the user password, and the difficulty to break it is not based on the password strength but instead on the cryptographic operations used and the length of the hash value. In theory it should take many many years to break this hash. As theory and practice does not always agree it is still a good idea to have working lockouts of any such attempts.</p>\n<h4>1.7.0</h4>\n<ul>\n<li>Added filter that allows whitelisting IP. Please use with care!!</li>\n<li>Update to Spanish translation, thanks to Marcelo Pedra</li>\n<li>Updated Swedish translation</li>\n<li>Tested against WordPress 3.3.2</li>\n</ul>\n<h4>1.6.2</h4>\n<ul>\n<li>Fix bug where log would not get updated after it had been cleared</li>\n<li>Do plugin setup in &#8216;init&#8217; action</li>\n<li>Small update to Spanish translation file, thanks to Marcelo Pedra</li>\n<li>Tested against WordPress 3.2.1</li>\n</ul>\n<h4>1.6.1</h4>\n<ul>\n<li>(WordPress 3.0+) An invalid cookie can sometimes get sent multiple times before it gets cleared, resulting in multiple failed attempts or even a lockout from a single invalid cookie. Store the latest failed cookie to make sure we only count it as one failed attempt</li>\n<li>Define &#8220;Text Domain&#8221; correctly</li>\n<li>Include correct Dutch tranlation file. Thanks to Martin1 for noticing. Thanks again to Bjorn Wijers for the translation</li>\n<li>Updated POT file for this version</li>\n<li>Tested against WordPress 3.1-RC4</li>\n</ul>\n<h4>1.6.0</h4>\n<ul>\n<li>Happy New Year</li>\n<li>Tested against WordPress 3.1-RC1</li>\n<li>Plugin now requires WordPress version 2.8+. Of course you should never ever use anything but the latest version</li>\n<li>Fixed deprecation warnings that had been piling up with the old version requirement. Thanks to Johannes Ruthenberg for the report that prompted this</li>\n<li>Removed auth cookie admin check for version 2.7.</li>\n<li>Make sure relevant values in $_COOKIE get cleared right away on auth cookie validation failure. There are still some problems with cookie auth handling. The lockout can trigger prematurely in rare cases, but fixing it is plugin version 2 stuff unfortunately.</li>\n<li>Changed default time for retries to reset from 24 hours to 12 hours. The security impact is very minor and it means the warning will disappear &#8220;overnight&#8221;</li>\n<li>Added question to FAQ (&#8220;Why not reset failed attempts on a successful login?&#8221;)</li>\n<li>Updated screenshots</li>\n</ul>\n<h4>1.5.2</h4>\n<ul>\n<li>Reverted minor cookie-handling cleanup which might somehow be responsible for recently reported cookie related lockouts</li>\n<li>Added version 1.x Brazilian Portuguese translation, thanks to Luciano Passuello</li>\n<li>Added Finnish translation, thanks to Ari Kontiainen</li>\n</ul>\n<h4>1.5.1</h4>\n<ul>\n<li>Further multisite &amp; WPMU support (again thanks to <a href="mailto:&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;" rel="nofollow">&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;</a>)</li>\n<li>Better error handling if option variables are damaged</li>\n<li>Added Traditional Chinese translation, thanks to Denny Huang <a href="mailto:&#x62;&#105;&#x67;&#101;&#x78;&#112;&#x6c;&#111;&#114;&#x61;&#116;&#x69;&#111;&#x6e;&#115;&#064;&#x62;&#105;&#x67;&#101;&#x78;&#112;&#108;&#x6f;&#114;&#x61;&#116;&#x69;&#111;n&#x73;&#046;&#x63;&#111;&#x6d;&#046;t&#x77;" rel="nofollow">&#x62;&#105;&#x67;&#101;&#x78;&#112;&#x6c;&#111;&#114;&#x61;&#116;&#x69;&#111;&#x6e;&#115;&#064;&#x62;&#105;&#x67;&#101;&#x78;&#112;&#108;&#x6f;&#114;&#x61;&#116;&#x69;&#111;n&#x73;&#046;&#x63;&#111;&#x6d;&#046;t&#x77;</a></li>\n</ul>\n<h4>1.5</h4>\n<ul>\n<li>Tested against WordPress 3.0</li>\n<li>Handle 3.0 login page failure &#8220;shake&#8221;</li>\n<li>Basic multisite support (parts thanks to <a href="mailto:&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;" rel="nofollow">&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;</a>)</li>\n<li>Added Dutch translation, thanks to Bjorn Wijers <a href="mailto:b&#117;&#x72;&#111;&#x62;&#x6a;&#111;&#x72;n&#064;&#x62;&#117;&#x72;&#x6f;&#098;&#x6a;&#111;&#114;&#x6e;&#046;&#x6e;l" rel="nofollow">b&#117;&#x72;&#111;&#x62;&#x6a;&#111;&#x72;n&#064;&#x62;&#117;&#x72;&#x6f;&#098;&#x6a;&#111;&#114;&#x6e;&#046;&#x6e;l</a></li>\n<li>Added Hungarian translation, thanks to B?lint Vereskuti <a href="mailto:&#098;&#097;&#x6c;&#x69;&#110;&#116;&#x40;v&#101;&#x72;&#x65;&#115;&#107;&#x75;&#x74;&#105;&#046;&#x69;n&#102;&#x6f;" rel="nofollow">&#098;&#097;&#x6c;&#x69;&#110;&#116;&#x40;v&#101;&#x72;&#x65;&#115;&#107;&#x75;&#x74;&#105;&#046;&#x69;n&#102;&#x6f;</a></li>\n<li>Added French translation, thanks to oVa <a href="mailto:&#111;&#118;&#x61;&#x31;&#x33;l&#097;&#115;&#x74;&#x61;&#x72;&#064;&#103;&#109;&#097;&#x69;&#x6c;&#x2e;&#099;&#111;&#109;" rel="nofollow">&#111;&#118;&#x61;&#x31;&#x33;l&#097;&#115;&#x74;&#x61;&#x72;&#064;&#103;&#109;&#097;&#x69;&#x6c;&#x2e;&#099;&#111;&#109;</a></li>\n</ul>\n<h4>1.4.1</h4>\n<ul>\n<li>Added Turkish translation, thanks to Yazan Canarkadas</li>\n</ul>\n<h4>1.4</h4>\n<ul>\n<li>Protect admin page update using wp_nonce</li>\n<li>Added Czech translation, thanks to Jakub Jedelsky</li>\n</ul>\n<h4>1.3.2</h4>\n<ul>\n<li>Added Bulgarian translation, thanks to Hristo Chakarov</li>\n<li>Added Norwegian translation, thanks to Rune Gulbrands?y</li>\n<li>Added Spanish translation, thanks to Marcelo Pedra</li>\n<li>Added Persian translation, thanks to Mostafa Soufi</li>\n<li>Added Russian translation, thanks to Jack Leonid (http://studio-xl.com)</li>\n</ul>\n<h4>1.3.1</h4>\n<ul>\n<li>Added Catalan translation, thanks to Robert Buj</li>\n<li>Added Romanian translation, thanks to Robert Tudor</li>\n</ul>\n<h4>1.3</h4>\n<ul>\n<li>Support for getting the correct IP for clients while server is behind reverse proxy, thanks to Michael Skerwiderski</li>\n<li>Added German translation, thanks to Michael Skerwiderski</li>\n</ul>\n<h4>1.2</h4>\n<ul>\n<li>No longer replaces pluggable function when cookie handling active. Re-implemented using available actions and filters</li>\n<li>Filter error messages during login to avoid information leak regarding available usernames</li>\n<li>Do not show retries or lockout messages except for login (registration, lost password pages). No change in actual enforcement</li>\n<li>Slightly more aggressive in trimming old retries data</li>\n</ul>\n<h4>1.1</h4>\n<ul>\n<li>Added translation support</li>\n<li>Added Swedish translation</li>\n<li>During lockout, filter out all other login errors</li>\n<li>Minor cleanups</li>\n</ul>\n<h4>1.0</h4>\n<ul>\n<li>Initial version</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/plugins/limit-login-attempts/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:39:"\n		\n		\n		\n		\n		\n		\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"TinyMCE Advanced";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/tinymce-advanced/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/tinymce-advanced/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 22 Jun 2007 06:02:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins-wp/tinymce-advanced/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:58:"Extends and enhances TinyMCE, the WordPress Visual Editor.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Andrew Ozz";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:10906:"<p><!--section=description--></p>\n<p>This plugin will let you add, remove and arrange the buttons that are shown on the Visual Editor toolbar. You can configure up to four rows of buttons including Font Sizes, Font Family, text and background colors, tables, etc. It will also let you enable the editor menu, see the <a href="screenshots" rel="nofollow">screenshots</a>.</p>\n<p>It includes 15 plugins for <a href="http://tinymce.com/" rel="nofollow">TinyMCE</a> that are automatically enabled or disabled depending on the buttons you have chosen. In addition this plugin adds some commonly used options as keeping the paragraph tags in the Text editor and importing the CSS classes from the theme&#8217;s editor-style.css.</p>\n<h4>Some of the features added by this plugin</h4>\n<ul>\n<li>Support for creating and editing tables.</li>\n<li>More options when inserting lists.</li>\n<li>Search and Replace in the editor.</li>\n<li>Ability to set Font Family and Font Sizes.</li>\n<li>And many others.</li>\n</ul>\n<p>With this plugin you can also enable the TinyMCE menu above the toolbars. This will make the editor even more powerful and convenient.</p>\n<p><!--section=installation--></p>\n<p>Best is to install directly from WordPress. If manual installation is required, please make sure that the plugin files are in a folder named &#8220;tinymce-advanced&#8221; (not two nested folders) in the WordPress plugins folder, usually &#8220;wp-content/plugins&#8221;.</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<p>Best is to install directly from WordPress. If manual installation is required, please make sure that the plugin files are in a folder named &#8220;tinymce-advanced&#8221; (not two nested folders) in the WordPress plugins folder, usually &#8220;wp-content/plugins&#8221;.</p>\n</dd>\n<dt>No styles are imported in the Formats sub-menu.</dt>\n<dd>\n<p>These styles are imported from your current theme editor-style.css file. However some themes do not have this functionality. For these themes TinyMCE Advanced has the option to let you add a customized editor-style.css and import it into the editor.</p>\n</dd>\n<dt>I have just installed this plugin, but it does not do anything.</dt>\n<dd>\n<p>Change some buttons on one of the toolbars, save your changes, clear your browser cache, and try again. If that does not work try reloding the Edit page several times while holding down Shift or Ctrl. There may also be a network cache somewhere between you and your host. You may need to wait for a few hours until this cache expires.</p>\n</dd>\n<dt>When I add &#8220;Smilies&#8221;, they do not show in the editor.</dt>\n<dd>\n<p>The &#8220;Emoticons&#8221; button in TinyMCE adds the codes for the smilies. The actual images are added by WordPress when viewing the Post. Make sure the checkbox &#8220;Convert emoticons to graphics on display&#8221; in &#8220;Options &#8211; Writing&#8221; is checked.</p>\n</dd>\n<dt>The plugin does not add any buttons.</dt>\n<dd>\n<p>Make sure the &#8220;Disable the visual editor when writing&#8221; checkbox under &#8220;Users &#8211; Your Profile&#8221; is <strong>not</strong> checked.</p>\n</dd>\n<dt>I still see the &#8220;old&#8221; buttons in the editor</dt>\n<dd>\n<p>Click the &#8220;Restore Default Settings&#8221; button on the plugin settings page and then set the buttons again and save.</p>\n</dd>\n<dt>Other questions? More screenshots?</dt>\n<dd>\n<p>Please post on the support forum or visit the homepage for <a href="http://www.laptoptips.ca/projects/tinymce-advanced/" rel="nofollow">TinyMCE Advanced</a>.</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>4.6.7</h4>\n<ul>\n<li>Fixed compatibility with Gutenberg freeform block.</li>\n<li>Forced refresh of the TinyMCE plugins after activation.</li>\n<li>Updated for WordPress 4.9 and TinyMCE 4.6.7.</li>\n</ul>\n<h4>4.6.3</h4>\n<ul>\n<li>Updated for WordPress 4.8 and TinyMCE 4.6.3.</li>\n</ul>\n<h4>4.5.6</h4>\n<ul>\n<li>Updated for WordPress 4.7.4 and TinyMCE 4.5.6.</li>\n<li>Fixed PHP notice after importing settings.</li>\n</ul>\n<h4>4.4.3</h4>\n<ul>\n<li>Updated for WordPress 4.7 and TinyMCE 4.4.3.</li>\n<li>Fixed missing &#8220;Source code&#8221; button bug.</li>\n</ul>\n<h4>4.4.1</h4>\n<ul>\n<li>Updated for WordPress 4.6 and TinyMCE 4.4.1.</li>\n<li>Fixed multisite saving bug.</li>\n<li>Added new button in the Text editor to add or reset the line breaks. Adds line breaks only between tags. Works only when it detects that line breaks are missing so it doesn&#8217;t reformat posts with removed paragraphs.</li>\n</ul>\n<h4>4.3.10.1</h4>\n<ul>\n<li>Fixed adding paragraph tags when loading posts that were saved before turning autop off.</li>\n<li>Disabled the (new) inline toolbar for tables as it was overlapping the table in some cases.</li>\n</ul>\n<h4>4.3.10</h4>\n<ul>\n<li>Updated for WordPress 4.5.1 and TinyMCE 4.3.10.</li>\n<li>Fixed support for adding editor-style.css to themes that don&#8217;t have it.</li>\n</ul>\n<h4>4.3.8</h4>\n<ul>\n<li>Updated for WordPress 4.5 and TinyMCE 4.3.8.</li>\n<li>Separated standard options and admin options.</li>\n<li>Added settings that can disable the plugin for the main editor, other editors in wp-admin or editors on the front-end.</li>\n<li>Korean translation by Josh Kim and Greek translation by Stathis Mellios.</li>\n</ul>\n<h4>4.2.8</h4>\n<ul>\n<li>Updated for WordPress 4.4 and TinyMCE 4.2.8.</li>\n<li>Japanese translation by Manabu Miwa.</li>\n</ul>\n<h4>4.2.5</h4>\n<ul>\n<li>Updated for WordPress 4.3.1 and TinyMCE 4.2.5.</li>\n<li>Fixed text domain and plugin headers.</li>\n</ul>\n<h4>4.2.3.1</h4>\n<ul>\n<li>Fix error with removing the &#8216;textpattern&#8217; plugin.</li>\n</ul>\n<h4>4.2.3</h4>\n<ul>\n<li>Updated for WordPress 4.3 and TinyMCE 4.2.3.</li>\n<li>Removed the &#8216;textpattern&#8217; plugin as WordPress 4.3 includes similar functionality by default.</li>\n<li>French translation by Nicolas Schneider.</li>\n</ul>\n<h4>4.1.9</h4>\n<ul>\n<li>Updated for WordPress 4.2 and TinyMCE 4.1.9.</li>\n<li>Fixed bugs with showing oEmbed previews when pasting an URL.</li>\n<li>Fixed bugs with getting the content from TinyMCE with line breaks.</li>\n</ul>\n<h4>4.1.7</h4>\n<ul>\n<li>Updated for WordPress 4.1 and TinyMCE 4.1.7.</li>\n<li>Fixed bug where consecutive caption shortcodes may be split with an empty paragraph tag.</li>\n</ul>\n<h4>4.1.1</h4>\n<ul>\n<li>Fix bug with image captions when wpautop is disabled.</li>\n<li>Add translation support to the settings page. Button names/descriptions are translated from JS using the existing WordPress translation, so this part of the settings page will be translated by default. The other text still needs separate translation.</li>\n</ul>\n<h4>4.1</h4>\n<ul>\n<li>Updated for WordPress 4.0 and TinyMCE 4.1.</li>\n<li>Add the &#8216;textpattern&#8217; plugin that supports some of the markdown syntax while typing, <a href="http://www.tinymce.com/wiki.php/Configuration:textpattern_patterns" rel="nofollow">(more info)</a>.</li>\n<li>Add the updated &#8216;table&#8217; plugin that supports background and border color.</li>\n</ul>\n<h4>4.0.2</h4>\n<ul>\n<li>Fix showing of the second, third and forth button rows when the Toolbar Toggle button is not used.</li>\n<li>Fix adding the &#8221;directionality&#8221; plugin when RTL or LTR button is selected.</li>\n<li>Show the &#8221;Advanced Options&#8221; to super admins on multisite installs.</li>\n<li>Add the &#8221;link&#8221; plugin including link rel setting. Replaces the Insert/Edit Link dialog when enabled.</li>\n<li>Include updated &#8221;table&#8221; plugin that has support for vertical align for cells.</li>\n</ul>\n<h4>4.0.1</h4>\n<p>Fix warnings on pages other than Edit Post. Update the description.</p>\n<h4>4.0</h4>\n<p>Updated for WordPress 3.9 and TinyMCE 4.0. Refreshed the settings screen. Added support for exporting and importing of the settings.</p>\n<h4>3.5.9.1</h4>\n<p>Updated for WordPress 3.8, fixed auto-embedding of single line URLs when not removing paragraph tags.</p>\n<h4>3.5.9</h4>\n<p>Updated for WordPress 3.7 and TinyMCE 3.5.9.</p>\n<h4>3.5.8</h4>\n<p>Updated for WordPress 3.5 and TinyMCE 3.5.8.</p>\n<h4>3.4.9</h4>\n<p>Updated for WordPress 3.4 and TinyMCE 3.4.9.</p>\n<h4>3.4.5.1</h4>\n<p>Fixed a bug preventing TinyMCE from importing CSS classes from editor-style.css.</p>\n<h4>3.4.5</h4>\n<p>Updated for WordPress 3.3 or later and TinyMCE 3.4.5.</p>\n<h4>3.4.2.1</h4>\n<p>Fix the removal of the <em>media</em> plugin so it does not require re-saving the settings.</p>\n<h4>3.4.2</h4>\n<p>Compatibility with WordPress 3.2 and TinyMCE 3.4.2, removed the options for support for iframe and HTML 5.0 elements as they are supported by default in WordPress 3.2, removed the <em>media</em> plugin as it is included by default.</p>\n<h4>3.3.9.1</h4>\n<p>Added advanced options: stop removing iframes, stop removing HTML 5.0 elements, moved the support for custom editor styles to editor-style.css in the current theme.</p>\n<p>Attention: if you have a customized tadv-mce.css file and your theme doesn&#8217;t have editor-style.css, please download tadv-mce.css, rename it to editor-style.css and upload it to your current theme directory. Alternatively you can add there the editor-style.css from the Twenty Ten theme. If your theme has editor-style.css you can add any custom styles there.</p>\n<h4>3.3.9</h4>\n<p>Compatibility with WordPress 3.1 and TinyMCE 3.3.9, improved P and BR tags option.</p>\n<h4>3.2.7</h4>\n<p>Compatibility with WordPress 2.9 and TinyMCE 3.2.7, several minor bug fixes.</p>\n<h4>3.2.4</h4>\n<p>Compatibility with WordPress 2.8 and TinyMCE 3.2.4, minor bug fixes.</p>\n<h4>3.2</h4>\n<p>Compatibility with WordPress 2.7 and TinyMCE 3.2, minor bug fixes.</p>\n<h4>3.1</h4>\n<p>Compatibility with WordPress 2.6 and TinyMCE 3.1, keeps empty paragraphs when disabling the removal of P and BR tags, the buttons for MCImageManager and MCFileManager can be arranged (if installed).</p>\n<h4>3.0.1</h4>\n<p>Compatibility with WordPress 2.5.1 and TinyMCE 3.0.7, added option to disable the removal of P and BR tags when saving and in the HTML editor (autop), added two more buttons to the HTML editor: autop and undo, fixed the removal of non-default TinyMCE buttons.</p>\n<h4>3.0</h4>\n<p>Support for WordPress 2.5 and TinyMCE 3.0.</p>\n<h4>2.2</h4>\n<p>Deactivate/Uninstall option page, font size drop-down menu and other small changes.</p>\n<h4>2.1</h4>\n<p>Improved language selection, improved compatibility with WordPress 2.3 and TinyMCE 2.1.1.1, option to override some of the imported css classes and other small improvements and bugfixes.</p>\n<h4>2.0</h4>\n<p>Includes an admin page for arranging the TinyMCE toolbar buttons, easy installation, a lot of bugfixes, customized &#8220;Smilies&#8221; plugin that uses the built-in WordPress smilies, etc. The admin page uses jQuery and jQuery UI that lets you &#8220;drag and drop&#8221; the TinyMCE buttons to arrange your own toolbars and enables/disables the corresponding plugins depending on the used buttons.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:52:"https://wordpress.org/plugins/tinymce-advanced/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:50:"https://wordpress.org/plugins/browse/popular/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:9:"\n	hourly	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:4:"\n	1	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Mon, 05 Feb 2018 21:50:20 GMT";s:12:"content-type";s:34:"application/rss+xml; charset=UTF-8";s:25:"strict-transport-security";s:11:"max-age=360";s:6:"x-olaf";s:3:"⛄";s:13:"last-modified";s:29:"Mon, 05 Feb 2018 21:38:20 GMT";s:4:"link";s:66:"<https://wordpress.org/plugins/wp-json/>; rel="https://api.w.org/"";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:13:"EXPIRED ord 2";}}s:5:"build";s:14:"20130911040210";}', 'no');
