Version 4.1 of WordPress, named “Dinah” in honor of jazz singer Dinah Washington, is available for download or update in your WordPress dashboard. New features in WordPress 4.1 help you focus on your writing, and the new default theme lets you show it off in style.
\n
Twenty Fifteen has flawless language support, with help from Google’s Noto font family.
The straightforward typography is readable on any screen size.
\nYour content always takes center stage, whether viewed on a phone, tablet, laptop, or desktop computer.
\n
Sometimes, you just need to concentrate on putting your thoughts into words. Try turning on distraction-free writing mode. When you start typing, all the distractions will fade away, letting you focus solely on your writing. All your editing tools instantly return when you need them.
\n
Choose a languageRight now, WordPress 4.1 is already translated into over forty languages, with more always in progress. You can switch to any translation on the General Settings screen.
\n
Log out everywhereIf you’ve ever worried you forgot to sign out from a shared computer, you can now go to your profile and log out everywhere.
\n
Vine embedsEmbedding videos from Vine is as simple as pasting a URL onto its own line in a post. See the full list of supported embeds.
\n
Plugin recommendationsThe plugin installer suggests plugins for you to try. Recommendations are based on the plugins you and other users have installed.
\nMetadata, date, and term queries now support advanced conditional logic, like nested clauses and multiple operators — A AND ( B OR C ).
The customizer now supports conditionally showing panels and sections based on the page being previewed.
\n<title> tags in themesadd_theme_support( ''title-tag'' ) tells WordPress to handle the complexities of document titles.
Continued improvements to inline code documentation have made the developer reference more complete than ever.
\nThis release was led by John Blackbourn, with the help of these awesome folks. Check out some of their profiles while listening to Dinah Washington on the music service of your choice:
\nAaron D. Campbell, Aaron Jorbin, Adam Harley (Kawauso), Adam Silverstein, adelval, Ajay, Akeda Bagus, Alex Concha, Alex Shiels, Alison Barrett, Allan Collins, Amy Hendrix (sabreuse), Andrea Fercia, Andrew Nacin, Andrew Norcross, Andrew Ozz, Andrey "Rarst" Savchenko, Andy Keith, Andy Skelton, Anton Timmermans, Aubrey Portwood, Barry, Bartosz Romanowski, bassgang, bcworkz, Ben Dunkle, Bernhard Riedl, bigdawggi, Bob Gregor, bobbingwide, Brad Touesnard, bradparbs, Bram Duvigneau, Brandon Kraft, brasofilo, bravokeyl, Bryan Petty, cgaffga, Chirag Swadia, Chouby, Chris Blower, Chris Marslender, Chris Olbekson, Chris Scott, chriseverson, chrisguitarguy, Christopher Finke, ciantic, Comparativa de Bancos, Connor Jennings, Cor van Noorloos, Corphi, cramdesign, Daniel Bachhuber, Daniel Jalkut (Red Sweater), Danny de Haan, Daryl Koopersmith, Dave Kellam, DaveE, David A. Kennedy, David Anderson, David Marichal, Denis de Bernardy, Dion Hulse, Dominik Schilling, Doug Wollison, Drew Jaynes, DrProtocols, Dustin Filippini, eatingrules, edik, Eduardo Reveles, Elio Rivero, enej, Eric Lewis, Eric Mann, Erica Varlese, Erick Hitter, Evan Anderson, Fahmi Adib, fboender, Frank Klein, Fumito MIZUNO, Gary Cao, Gary Jones, Gary Pendergast, genkisan, Gennady Kovshenin, George Stephanis, Graham Armfield, Grant Mangham, Gregory Cornelius, Gregory Karpinsky (@tivnet), hakre, hanni, Helen Hou-Sandí, ippetkov, Ipstenu (Mika Epstein), J.D. Grimes, Jack Reichert, jameslee, Janneke Van Dorpe, janrenn, JayCC, Jeff Sebring, Jen, Jeremy Felt, Jesin A, Jesper Johansen (jayjdk), jnielsendotnet, Joan Artes, Joe Dolson, Joe Hoyle, John James Jacoby, John P. Bloch, John Regan, Jon Cave, Jonas Bolinder (jond3r), Joost de Valk, Josh Pollock, Joshua Abenazer, jstraitiff, Julio Potier, Justin Kopepasah, Justin Sainton, K.Adam White, Kailey (trepmal), Kaspars, Kelly Dwan, kerikae, Kevin Worthington, Kim Parsell, Kirk Wight, kitchin, klihelp, Knut Sparhell, Konstantin Kovshenin, Konstantin Obenland, Krzysiek Drozdz, Lance Willett, ldebrouwer, Lee Willis, lpointet, Lucas Karpiuk, Luke Woodward, Mario Peshev, Mark Barnes, Mark Jaquith, Marko Heijnen, Marventus, Matt (Thomas) Miklic, Matt Banks, Matt Mullenweg, Matthew Boynes, Matthew Denton, Matthew Haines-Young, mattonomics, mattyrob, Matías Ventura, Max Cutler, mcadwell, Mel Choyce, meloniq, Michael Arestad, Michael Pick, Michel - xiligroup dev, Miguel Fonseca, Mike Burns, Mike Hansen, Mike Manger, Mike Schinkel, Mike Schroder, mikecorkum, mitcho (Michael Yoshitaka Erlewine), Mohammad Jangda, Morgan Estes, Morten Rand-Hendriksen, Naoko Takano, Nashwan Doaqan, nendeb55, Nick Halsey, Nicole Arnold, Nikhil Vimal (NikV), Nivi Jah, Nuno Morgadinho, olivM, Omer Korner, OriginalEXE, patricknami, Paul Bearne, Paul Gibbs, Paul Wilde, pavelevap, Peter Westwood, Philip Arthur Moore, Pippin Williamson, Prasath Nadarajah, prettyboymp, Raam Dev, Rachel Baker, Ram Ratan Maurya, ramonchiara, Rhys Wynne, Ricardo Correia, Richard, Richard Sweeney, Richard Tape, Ricky Lee Whittemore, Robert Chapin, robmiller, Rodrigo Primo, romaimperator, roothorick, Ruud Laan, Ryan Boren, Ryan McCue, Sal Ferrarello, Samuel Wood (Otto), Sandeep, Scott Lee, Scott Reilly, Scott Taylor, ScreenfeedFr, scribu, sdasse, Sean Butze, Sean Hayes, Sean Nessworthy, Sergey Biryukov, shahpranaf, Shaun Andrews, ShinichiN, Simon Prosser, Simon Wheatley, Siobhan, Siobhan Bamber (siobhyb), sirzooro, solarissmoke, sonjanyc, Spencer Finnell, Spencer Piontkowski, stephcook22, Stephen Edgar, Stephen Harris, Steve Bruner, Steven Word, Takayuki Miyauchi, Tanner Moushey, Taylor Lovett, tbrams, TobiasBg, Tom Auger, Tom Willmot, Topher, topquarky, Torsten Landsiedel, Toru Miki, Travis Smith, Umesh Kumar, undergroundnetwork, VarunAgw, wawco, Weston Ruter, wokamoto, xsonic, Yoav Farhi, Yuri Victor, Zach Tirrell, and Ze Fontainhas.\nThere were 283 contributors to this release, again a new high.
\nIf you want to help out or follow along, check out Make WordPress and our core development blog.
\nThanks for choosing WordPress. Happy holidays and see you next year for version 4.2!
\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:46:"https://wordpress.org/news/2014/12/dinah/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:45:"\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:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:33:"WordPress 4.1 Release Candidate 3";s: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://wordpress.org/news/2014/12/wordpress-4-1-release-candidate-3/";s: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:78:"https://wordpress.org/news/2014/12/wordpress-4-1-release-candidate-3/#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, 18 Dec 2014 02:22: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:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";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:5:{s:4:"data";s:8:"Releases";s: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:33:"http://wordpress.org/news/?p=3411";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:429:"The next release candidate for WordPress 4.1 is now available for testing. Seventy changes have gone in since the first release candidate. With no known issues left, we plan to release 4.1 tomorrow, December 18. To test, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). If you’d like to learn more about […]";s: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:"";}}}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:1465:"The next release candidate for WordPress 4.1 is now available for testing.
\nSeventy changes have gone in since the first release candidate. With no known issues left, we plan to release 4.1 tomorrow, December 18.
\nTo test, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). If you’d like to learn more about what’s new in WordPress 4.1, visit the updated About screen in your dashboard (
→ About in the toolbar) and also check out the Beta 1 post.
Plugin authors: Remember to test your plugins against 4.1, and if they’re compatible, make sure they are marked as tested up to 4.1. Be sure to follow along the core development blog; we’ve been posting notes for developers for 4.1 as always.
\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:74:"https://wordpress.org/news/2014/12/wordpress-4-1-release-candidate-3/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:2;a:6:{s:4:"data";s:45:"\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:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"WordPress 4.1 Release Candidate";s: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://wordpress.org/news/2014/12/wordpress-4-1-release-candidate/";s: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:76:"https://wordpress.org/news/2014/12/wordpress-4-1-release-candidate/#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, 11 Dec 2014 11:52:16 +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:2:{i:0;a:5:{s:4:"data";s:8:"Releases";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:5:{s:4:"data";s:3:"4.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:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3375";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:341:"The release candidate for WordPress 4.1 is now available. We’ve made a lot of refinements over the last few weeks. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.1 on Tuesday, December 16, but we need your […]";s: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:"";}}}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:2301:"The release candidate for WordPress 4.1 is now available.
\nWe’ve made a lot of refinements over the last few weeks. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.1 on Tuesday, December 16, but we need your help to get there. If you haven’t tested 4.1 yet, now is the time! (Please though, not on your live site unless you’re adventurous.)
\nThink you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.
\nTo test WordPress 4.1 RC1, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip). If you’d like to learn more about what’s new in WordPress 4.1, visit the About screen in your dashboard ( → About in the toolbar) or check out the beta announcement.
Developers, please test your plugins and themes against WordPress 4.1 and update your plugin’s Tested up to version in the readme to 4.1 before next week. If you find compatibility problems, we never want to break things, so please be sure to post to the support forums so we can figure those out before the final release.
\nBe sure to follow along the core development blog, where we’ll continue to post notes for developers for 4.1. (For example: if you’ve written a child theme for Twenty Fifteen, some of the new pagination functions have been renamed for clarity.)
\nTesting four point one
\nWhy are we up at this hour?
\nCode is poetry
WordPress 4.0.1 is now available. This is a critical security release for all previous versions and we strongly encourage you to update your sites immediately.
\nSites that support automatic background updates will be updated to WordPress 4.0.1 within the next few hours. If you are still on WordPress 3.9.2, 3.8.4, or 3.7.4, you will be updated to 3.9.3, 3.8.5, or 3.7.5 to keep everything secure. (We don’t support older versions, so please update to 4.0.1 for the latest and greatest.)
\nWordPress versions 3.9.2 and earlier are affected by a critical cross-site scripting vulnerability, which could enable anonymous users to compromise a site. This was reported by Jouko Pynnonen. This issue does not affect version 4.0, but version 4.0.1 does address these eight security issues:
\nVersion 4.0.1 also fixes 23 bugs with 4.0, and we’ve made two hardening changes, including better validation of EXIF data we are extracting from uploaded photos. Reported by Chris Andrè Dale.
\nWe appreciated the responsible disclosure of these issues directly to our security team. For more information, see the release notes or consult the list of changes.
\nDownload WordPress 4.0.1 or venture over to Dashboard → Updates and simply click “Update Now”.
\nAlready testing WordPress 4.1? The second beta is now available (zip) and it contains these security fixes. For more on 4.1, see the beta 1 announcement post.
\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/news/2014/11/wordpress-4-0-1/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:4;a:6:{s:4:"data";s:48:"\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:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.1 Beta 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:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2014/11/wordpress-4-1-beta-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wordpress.org/news/2014/11/wordpress-4-1-beta-1/#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, 14 Nov 2014 22:35: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:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";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:5:{s:4:"data";s:8:"Releases";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:5:{s:4:"data";s:4:"beta";s: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:33:"http://wordpress.org/news/?p=3352";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:346:"Welcome, everyone, to WordPress 4.1 Beta 1! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.1, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can […]";s: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:"";}}}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:3409:"Welcome, everyone, to WordPress 4.1 Beta 1!
\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.1, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).
\nWordPress 4.1 is due for release next month, so we need your help with testing. Here are some highlights of what to test:
\nThere have been a lot of changes for developers to test as well:
\nIf you want a more in-depth view of what changes have made it into 4.1, check out the weekly review posts on the main development blog.
\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on the WordPress Trac. There, you can also find a list of known bugs and everything we’ve fixed so far.
\nHappy testing!
\nTwenty Fifteen theme
\n The beautiful face which hides
\n Many improvements
WordCamp San Francisco is the official annual WordPress conference, gathering the community every year since 2006. This is the time when Matt Mullenweg addresses the community in his annual State of the Word presentation – a recap of the year in WordPress and giving us a glimpse into its future.
\nThis year the speaker lineup is stellar. There will be talks by three of the lead WordPress developers: Andrew Nacin, Helen Hou-Sandí, and Mark Jaquith. We’re also looking forward to speakers like Jenny Lawson, also known as The Bloggess, and Chris Lema. If you’re at all interested in the web, you will appreciate the appearance of Jeff Veen – one of the creators of Google Analytics and co-founder of Typekit.
\nEven though San Francisco is far far away for most of you, you can still be part of the fun and watch all presentations in real-time via livestream:
\nGet a livestream ticket and watch all talks from WordCamp San Francisco live
\nIf you hurry, you can get one of the special livestream tickets, including a WordCamp San Francisco 2104 t-shirt. You can find all the technical details and start times at the WordCamp San Francisco website.
\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/news/2014/10/wcsf-livestream/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:42:"\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:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:25:"WordPress 4.0 “Benny”";s: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:41:"https://wordpress.org/news/2014/09/benny/";s: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/news/2014/09/benny/#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, 04 Sep 2014 17:05: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:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s: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:33:"http://wordpress.org/news/?p=3296";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:370:"Version 4.0 of WordPress, named “Benny” in honor of jazz clarinetist and bandleader Benny Goodman, is available for download or update in your WordPress dashboard. While 4.0 is just another number for us after 3.9 and before 4.1, we feel we’ve put a little extra polish into it. This release brings you a smoother writing and management experience […]";s: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:"Matt 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:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:23070:"Version 4.0 of WordPress, named “Benny” in honor of jazz clarinetist and bandleader Benny Goodman, is available for download or update in your WordPress dashboard. While 4.0 is just another number for us after 3.9 and before 4.1, we feel we’ve put a little extra polish into it. This release brings you a smoother writing and management experience we think you’ll enjoy.
\n\n
Explore your uploads in a beautiful, endless grid. A new details preview makes viewing and editing any amount of media in sequence a snap.
Paste in a YouTube URL on a new line, and watch it magically become an embedded video. Now try it with a tweet. Oh yeah — embedding has become a visual experience. The editor shows a true preview of your embedded content, saving you time and giving you confidence.
\nWe’ve expanded the services supported by default, too — you can embed videos from CollegeHumor, playlists from YouTube, and talks from TED. Check out all of the embeds that WordPress supports.
\nWriting and editing is smoother and more immersive with an editor that expands to fit your content as you write, and keeps the formatting tools available at all times.
\n
There are more than 30,000 free and open source plugins in the WordPress plugin directory. WordPress 4.0 makes it easier to find the right one for your needs, with new metrics, improved search, and a more visual browsing experience.
\nThis release was led by Helen Hou-Sandí, with the help of these fine individuals. There are 275 contributors with props in this release, a new high. Pull up some Benny Goodman on your music service of choice, as a bandleader or in one of his turns as a classical clarinetist, and check out some of their profiles:
\nAaron D. Campbell, Aaron Jorbin, Adam Harley (Kawauso), Adam Silverstein, adelval, Ajay, Akeda Bagus, Alex Concha, Alex Shiels, Alison Barrett, Allan Collins, Amy Hendrix (sabreuse), Andrea Fercia, Andrew Nacin, Andrew Norcross, Andrew Ozz, Andrey "Rarst" Savchenko, Andy Keith, Andy Skelton, Anton Timmermans, Aubrey Portwood, Barry, Bartosz Romanowski, bassgang, bcworkz, Ben Dunkle, Bernhard Riedl, bigdawggi, Bob Gregor, bobbingwide, Brad Touesnard, bradparbs, Bram Duvigneau, Brandon Kraft, brasofilo, bravokeyl, Bryan Petty, cgaffga, Chirag Swadia, Chouby, Chris Blower, Chris Marslender, Chris Olbekson, Chris Scott, chriseverson, chrisguitarguy, Christopher Finke, ciantic, Comparativa de Bancos, Connor Jennings, Cor van Noorloos, Corphi, cramdesign, Daniel Bachhuber, Daniel Jalkut (Red Sweater), Danny de Haan, Daryl Koopersmith, Dave Kellam, DaveE, David A. Kennedy, David Anderson, David Marichal, Denis de Bernardy, Dion Hulse, Dominik Schilling, Doug Wollison, Drew Jaynes, DrProtocols, Dustin Filippini, eatingrules, edik, Eduardo Reveles, Elio Rivero, enej, Eric Lewis, Eric Mann, Erica Varlese, Erick Hitter, Evan Anderson, Fahmi Adib, fboender, Frank Klein, Fumito MIZUNO, Gary Cao, Gary Jones, Gary Pendergast, genkisan, Gennady Kovshenin, George Stephanis, Graham Armfield, Grant Mangham, Gregory Cornelius, Gregory Karpinsky (@tivnet), hakre, hanni, ippetkov, Ipstenu (Mika Epstein), J.D. Grimes, Jack Reichert, jameslee, Janneke Van Dorpe, janrenn, JayCC, Jeff Sebring, Jen, Jeremy Felt, Jesin A, Jesper Johansen (jayjdk), jnielsendotnet, Joan Artes, Joe Dolson, Joe Hoyle, John Blackbourn, John James Jacoby, John P. Bloch, John Regan, Jon Cave, Jonas Bolinder (jond3r), Joost de Valk, Josh Pollock, Joshua Abenazer, jstraitiff, Julio Potier, Justin Kopepasah, Justin Sainton, K.Adam White, Kailey (trepmal), Kaspars, Kelly Dwan, kerikae, Kevin Worthington, Kim Parsell, Kirk Wight, kitchin, klihelp, Knut Sparhell, Konstantin Kovshenin, Konstantin Obenland, Krzysiek Drozdz, Lance Willett, ldebrouwer, Lee Willis, lpointet, Lucas Karpiuk, Luke Woodward, Mario Peshev, Mark Barnes, Mark Jaquith, Marko Heijnen, Marventus, Matt (Thomas) Miklic, Matt Banks, Matt Mullenweg, Matthew Boynes, Matthew Denton, Matthew Haines-Young, mattonomics, mattyrob, Matías Ventura, Max Cutler, mcadwell, Mel Choyce, meloniq, Michael Arestad, Michel - xiligroup dev, Miguel Fonseca, Mike Burns, Mike Hansen, Mike Manger, Mike Schinkel, Mike Schroder, mikecorkum, mitcho (Michael Yoshitaka Erlewine), Mohammad Jangda, Morgan Estes, Morten Rand-Hendriksen, Naoko Takano, Nashwan Doaqan, nendeb55, Nick Halsey, Nicole Arnold, Nikhil Vimal (NikV), Nivi Jah, Nuno Morgadinho, olivM, Omer Korner, OriginalEXE, patricknami, Paul Bearne, Paul Gibbs, Paul Wilde, pavelevap, Peter Westwood, Philip Arthur Moore, Pippin Williamson, Prasath Nadarajah, prettyboymp, Raam Dev, Rachel Baker, Ram Ratan Maurya, ramonchiara, Rhys Wynne, Ricardo Correia, Richard, Richard Sweeney, Richard Tape, Ricky Lee Whittemore, Robert Chapin, robmiller, Rodrigo Primo, romaimperator, roothorick, Ruud Laan, Ryan Boren, Ryan McCue, Sal Ferrarello, Samuel Wood (Otto), Sandeep, Scott Lee, Scott Reilly, Scott Taylor, ScreenfeedFr, scribu, sdasse, Sean Butze, Sean Hayes, Sean Nessworthy, Sergey Biryukov, shahpranaf, Shaun Andrews, ShinichiN, Simon Prosser, Simon Wheatley, Siobhan, Siobhan Bamber (siobhyb), sirzooro, solarissmoke, sonjanyc, Spencer Finnell, Spencer Piontkowski, stephcook22, Stephen Edgar, Stephen Harris, Steve Bruner, Steven Word, Takayuki Miyauchi, Tanner Moushey, Taylor Lovett, tbrams, TobiasBg, Tom Auger, Tom Willmot, Topher, topquarky, Torsten Landsiedel, Toru Miki, Travis Smith, Umesh Kumar, undergroundnetwork, VarunAgw, wawco, Weston Ruter, wokamoto, xsonic, Yoav Farhi, Yuri Victor, Zach Tirrell, and Ze Fontainhas. Also thanks to Michael Pick for producing the release video, and Helen with Adrián Sandí for the music.
\nIf you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress. See you soon for version 4.1!
\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:46:"https://wordpress.org/news/2014/09/benny/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:7;a:6:{s:4:"data";s:45:"\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:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"WordPress 4.0 Release Candidate";s: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://wordpress.org/news/2014/08/wordpress-4-0-release-candidate/";s: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:76:"https://wordpress.org/news/2014/08/wordpress-4-0-release-candidate/#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:"Wed, 27 Aug 2014 12:20: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:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";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:5:{s:4:"data";s:8:"Releases";s: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:33:"http://wordpress.org/news/?p=3287";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:321:"The first release candidate for WordPress 4.0 is now available! In RC 1, we’ve made refinements to what we’ve been working on for this release. Check out the Beta 1 announcement post for more details on those features. We hope to ship WordPress 4.0 next week, but we need your help to get there. If you […]";s: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:"Helen Hou-Sandi";s: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:2134:"The first release candidate for WordPress 4.0 is now available!
\nIn RC 1, we’ve made refinements to what we’ve been working on for this release. Check out the Beta 1 announcement post for more details on those features. We hope to ship WordPress 4.0 next week, but we need your help to get there. If you haven’t tested 4.0 yet, there’s no time like the present. (Please, not on a production site, unless you’re adventurous.)
\nThink you’ve found a bug? Please post to the Alpha/Beta area in the support forums. If any known issues come up, you’ll be able to find them here.
\nTo test WordPress 4.0 RC1, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). If you’d like to learn more about what’s new in WordPress 4.0, visit the awesome About screen in your dashboard (
→ About in the toolbar).
Developers, please test your plugins and themes against WordPress 4.0 and update your plugin’s Tested up to version in the readme to 4.0 before next week. If you find compatibility problems, please be sure to post any issues to the support forums so we can figure those out before the final release. You also may want to give your plugin an icon, which we launched last week and will appear in the dashboard along with banners.
\nIt is almost time
\n For the 4.0 release
\n And its awesomeness
The fourth and likely final beta for WordPress 4.0 is now available. We’ve made more than 250 changes in the past month, including:
\nWe need your help. We’re still aiming for a release this month, which means the next week will be critical for identifying and squashing bugs. If you’re just joining us, please see the Beta 1 announcement post for what to look out for.
\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums, where friendly moderators are standing by. Plugin developers, if you haven’t tested WordPress 4.0 yet, now is the time — and be sure to update the “tested up to” version for your plugins so they’re listed as compatible with 4.0.
\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.0, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).
\nWe are working hard
\nTo finish up 4.0
\nWill you help us too?
WordPress 3.9.2 is now available as a security release for all previous versions. We strongly encourage you to update your sites immediately.
\nThis release fixes a possible denial of service issue in PHP’s XML processing, reported by Nir Goldshlager of the Salesforce.com Product Security Team. It was fixed by Michael Adams and Andrew Nacin of the WordPress security team and David Rothstein of the Drupal security team. This is the first time our two projects have coordinated joint security releases.
\nWordPress 3.9.2 also contains other security changes:
\nWe appreciated responsible disclosure of these issues directly to our security team. For more information, see the release notes or consult the list of changes.
\nDownload WordPress 3.9.2 or venture over to Dashboard → Updates and simply click “Update Now”.
\nSites that support automatic background updates will be updated to WordPress 3.9.2 within 12 hours. (If you are still on WordPress 3.8.3 or 3.7.3, you will also be updated to 3.8.4 or 3.7.4. We don’t support older versions, so please update to 3.9.2 for the latest and greatest.)
\nAlready testing WordPress 4.0? The third beta is now available (zip) and it contains these security fixes.
\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/news/2014/08/wordpress-3-9-2/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:32:"https://wordpress.org/news/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:6:"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: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:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Sun, 11 Jan 2015 14:20:29 GMT";s:12:"content-type";s:23:"text/xml; charset=UTF-8";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:10:"x-pingback";s:37:"https://wordpress.org/news/xmlrpc.php";s:13:"last-modified";s:29:"Thu, 18 Dec 2014 18:57:51 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";}s:5:"build";s:14:"20130911080210";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (7575, '_site_transient_update_plugins', 'O:8:"stdClass":5:{s:12:"last_checked";i:1420986181;s:7:"checked";a:2:{s:19:"akismet/akismet.php";s:5:"3.0.0";s:9:"hello.php";s:3:"1.6";}s:8:"response";a:1:{s:19:"akismet/akismet.php";O:8:"stdClass":6:{s:2:"id";s:2:"15";s:4:"slug";s:7:"akismet";s:6:"plugin";s:19:"akismet/akismet.php";s:11:"new_version";s:5:"3.0.4";s:3:"url";s:38:"https://wordpress.org/plugins/akismet/";s:7:"package";s:56:"https://downloads.wordpress.org/plugin/akismet.3.0.4.zip";}}s:12:"translations";a:0:{}s:9:"no_update";a:1:{s:9:"hello.php";O:8:"stdClass":6:{s:2:"id";s:4:"3564";s:4:"slug";s:11:"hello-dolly";s:6:"plugin";s:9:"hello.php";s:11:"new_version";s:3:"1.6";s:3:"url";s:42:"https://wordpress.org/plugins/hello-dolly/";s:7:"package";s:58:"https://downloads.wordpress.org/plugin/hello-dolly.1.6.zip";}}}', 'yes'), (1878, 'auto_core_update_notified', 'a:4:{s:4:"type";s:7:"success";s:5:"email";s:38:"admin@delawarecountypublicadjuster.com";s:7:"version";s:5:"4.0.1";s:9:"timestamp";i:1416509336;}', 'yes'), (141, 'db_upgraded', '', 'yes'), (7574, '_site_transient_update_themes', 'O:8:"stdClass":4:{s:12:"last_checked";i:1420985983;s:7:"checked";a:4:{s:13:"twentyfifteen";s:3:"1.0";s:14:"twentyfourteen";s:3:"1.1";s:14:"twentythirteen";s:3:"1.2";s:12:"twentytwelve";s:3:"1.4";}s:8:"response";a:3:{s:14:"twentyfourteen";a:4:{s:5:"theme";s:14:"twentyfourteen";s:11:"new_version";s:3:"1.3";s:3:"url";s:43:"https://wordpress.org/themes/twentyfourteen";s:7:"package";s:60:"https://downloads.wordpress.org/theme/twentyfourteen.1.3.zip";}s:14:"twentythirteen";a:4:{s:5:"theme";s:14:"twentythirteen";s:11:"new_version";s:3:"1.4";s:3:"url";s:43:"https://wordpress.org/themes/twentythirteen";s:7:"package";s:60:"https://downloads.wordpress.org/theme/twentythirteen.1.4.zip";}s:12:"twentytwelve";a:4:{s:5:"theme";s:12:"twentytwelve";s:11:"new_version";s:3:"1.6";s:3:"url";s:41:"https://wordpress.org/themes/twentytwelve";s:7:"package";s:58:"https://downloads.wordpress.org/theme/twentytwelve.1.6.zip";}}s:12:"translations";a:0:{}}', 'yes'), (7567, '_site_transient_update_core', 'O:8:"stdClass":4:{s:7:"updates";a:1:{i:0;O:8:"stdClass":10:{s:8:"response";s:6:"latest";s:8:"download";s:57:"https://downloads.wordpress.org/release/wordpress-4.1.zip";s:6:"locale";s:5:"en_US";s:8:"packages";O:8:"stdClass":5:{s:4:"full";s:57:"https://downloads.wordpress.org/release/wordpress-4.1.zip";s:10:"no_content";s:68:"https://downloads.wordpress.org/release/wordpress-4.1-no-content.zip";s:11:"new_bundled";s:69:"https://downloads.wordpress.org/release/wordpress-4.1-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:3:"4.1";s:7:"version";s:3:"4.1";s:11:"php_version";s:5:"5.2.4";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"4.1";s:15:"partial_version";s:0:"";}}s:12:"last_checked";i:1420985982;s:15:"version_checked";s:3:"4.1";s:12:"translations";a:0:{}}', 'yes'), (1606, 'dashboard_widget_options', 'a:4:{s:25:"dashboard_recent_comments";a:1:{s:5:"items";i:5;}s:24:"dashboard_incoming_links";a:5:{s:4:"home";s:39:"http://delawarecountypublicadjuster.com";s:4:"link";s:115:"http://blogsearch.google.com/blogsearch?scoring=d&partner=wordpress&q=link:http://delawarecountypublicadjuster.com/";s:3:"url";s:148:"http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:http://delawarecountypublicadjuster.com/";s:5:"items";i:10;s:9:"show_date";b:0;}s:17:"dashboard_primary";a:7:{s:4:"link";s:26:"http://wordpress.org/news/";s:3:"url";s:31:"http://wordpress.org/news/feed/";s:5:"title";s:14:"WordPress Blog";s:5:"items";i:2;s:12:"show_summary";i:1;s:11:"show_author";i:0;s:9:"show_date";i:1;}s:19:"dashboard_secondary";a:7:{s:4:"link";s:28:"http://planet.wordpress.org/";s:3:"url";s:33:"http://planet.wordpress.org/feed/";s:5:"title";s:20:"Other WordPress News";s:5:"items";i:5;s:12:"show_summary";i:0;s:11:"show_author";i:0;s:9:"show_date";i:0;}}', 'yes'), (7551, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1421028817', 'no'), (7552, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1420985617', 'no'), (7553, '_transient_timeout_feed_867bd5c64f85878d03a060509cd2f92c', '1421028818', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (7554, '_transient_feed_867bd5c64f85878d03a060509cd2f92c', '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:25:"Matt: NFL is a Non-Profit";s: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:21:"http://ma.tt/?p=44285";s: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:41:"http://ma.tt/2015/01/nfl-is-a-non-profit/";s: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:283:"Did you know the NFL is a non-profit? Slate says the NFL should lose its tax-exempt status: The league is not a “nonprofit.”.
";s: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, 10 Jan 2015 18:12:00 +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: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:18:"Matt: PGP Tutorial";s: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:21:"http://ma.tt/?p=44579";s: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:"http://ma.tt/2015/01/pgp-tutorial/";s: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:373:"Speaking of PGP and security, this self-describedbest PGP tutorial for Mac OS X, ever actually lives up to the promise. Check it out, makes encrypting and decrypting things on the fly super easy.
";s: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, 10 Jan 2015 00:26:00 +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: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:84:"WPTavern: Duplicate and Merge Posts: A New Editorial Plugin for WordPress Publishers";s: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:"http://wptavern.com/?p=37018";s: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:93:"http://wptavern.com/duplicate-and-merge-posts-a-new-editorial-plugin-for-wordpress-publishers";s: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:4489:"
WordPress sites with multiple users often run into challenges when attempting to work on the same content. Larger publications require more robust editorial tools for efficient collaboration between administrators, editors, contributors, and authors, who often need to jump in on the same post.
\nDuplicate and Merge Posts is a plugin that offers a new take on WordPress drafts. This editorial tool makes it possible to clone a live post, edit it, and then merge back the updated copy into the original post. It’s a essentially a far more simplified version of the Post Forking plugin in that it offers fewer capabilities. Duplicate and Merge Posts is intended for the following workflow:
\nOriginal Post -> Clone -> Edit -> Merge back to Original Post
\nThe plugin was created by WordPress developer David Wells as part of a client project with Exygy. “We built it for a ‘Fortune 10′ company for them to manage an internal documentation platform they have running on WordPress and figured the rest of the WordPress community would benefit from the plugin as well,” he said.
\nDuplicate and Merge Posts works with both posts and pages. When activated, you’ll find a new “Duplicate and Edit” button at the top of the post on the front end, as well as in the post edit screen.
\nThe plugin’s settings screen allows you to set different editorial capabilities based on user role. For example, you might only allow administrators and editors to merge changes back into posts. The buttons shown in the post editor are limited to the user’s capabilities and allow for the following:
\n
Users with merge capabilities will receive an email notification when a post has edits ready for review. The plugin allows you to see all of the changes side-by-side for quick comparison.
\n
The primary use case for the Duplicate and Merge plugin is likely to be multi-author publications. However, it’s flexible enough to enable more creative uses, such as turning your site into a wiki or allowing visitors to submit fixes for typos. The basic ability to clone posts can also be useful for sites using WordPress as a CMS with many pages that are similar in content.
\nAfter testing Duplicate and Merge, I found that it works as advertised. This tool has the potential to improve your editorial workflow without creating additional confusion for contributors. It has a natural workflow that allows a publication team to get more eyes on the content before pushing edits live.
\nYou can download Duplicate and Merge from WordPress.org. It’s also available for contributions on GitHub. If you want to see the plugin in action before installing it, check out the video below to tour its features.
\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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 09 Jan 2015 20:02:17 +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:"Sarah Gooding";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:39:"WPTavern: AcademiaThemes One Year Later";s: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:"http://wptavern.com/?p=37011";s: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:"http://wptavern.com/academiathemes-one-year-later";s: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:2636:"
When Dumitru Brinzan launched AcademiaThemes in early 2014, he did so with the goal of providing high quality themes for the education sector. With one year under his belt, I reached out to Brinzan to find out how the business is doing. The first year was rough, thanks in large part to algorithm changes implemented by Google to its search engine in early 2014.
\n
The updates negatively impacted a majority of AcademiaThemes affiliates, “Many of our affiliates simply lost all of their traffic, so we lost basically all sales generated by them, which is an important source of revenue for new shops.” With affiliates having a hard time getting search engine traffic, Brinzan is finding it difficult to get new traffic to his site, “Now with almost all of the main affiliates out of the picture, it’s become incredibly hard to get traffic to our shop.”
\nDespite a significant loss in traffic and affiliate revenue, Brinzan will continue to operate the site. In fact, he’s opened a new theme shop called EnergyThemes aimed at the fitness market. EnergyThemes is the third theme company he owns that’s aimed at a specific niche. In addition to AcademiaThemes, he operates HermesThemes which offers themes for hotels.
\nI’ve never owned a WordPress theme shop, but I understand how important affiliate programs are. They provide free advertising while helping to generate sales. I never realized updates to Google’s search engine could drastically reduce affiliate revenue and traffic if sites perform poorly based on those updates. This is an important thing to consider if you’re thinking about utilizing an affiliate program.
";s: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, 09 Jan 2015 11:50:08 +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: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:67:"WPTavern: 5 WordPress Initiatives That Didn’t Make it Out of 2014";s: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:"http://wptavern.com/?p=36477";s: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:74:"http://wptavern.com/5-wordpress-initiatives-that-didnt-make-it-out-of-2014";s: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:7788:"Throughout the course of a year, several new ideas, products, and businesses are launched in the WordPress ecosystem. However, not all of them are destined for success. Here are five WordPress initiatives launched in 2014 that didn’t make the cut.
\n
Launched in early 2014 and created by Ryan Bell, WPKindness shared acts of kindness that have taken place throughout the WordPress community. The site used a combination of Headway, Gravity Forms, Toolset and WordPress, allowing visitors to submit reports. At the time, I was concerned with a section within the site’s terms of service that explained affiliate links might be used in reports where companies are mentioned, “You understand wpkindness.com might use an affiliate link to the company you are submitting about.“ The concern is a moot point as the site is offline.
\nFresh out of WordCamp Norway, Slobodan Manic created a WordPress collaboration group with the idea that working together creates more opportunities to learn. The first task for the group was to create a WordPress plugin and submit it to the directory. Their first plugin, Hello Emoji, successfully made it to the directory and was created by five people from four different continents in a two week time period.
\nWhile WPCollab showed promise, the lack of focus and the inability to manage several contributors from across the world caused the project to lose momentum.
\nWhen Editorially closed its doors in May of 2014, it took all of its cool writing collaboration tools with it. A new project called Feuilles picked up where Editorially left off with an app that provided some of the features Editorially users loved most.
\n
Feuilles allowed users to publish to Github, WordPress.com, and Dropbox at the same time. Alex Duloz, one of the project’s creators, aimed to make Feuilles a language/device agnostic CMS with in-house publishing. Unfortunately, the project never made it that far and the website devoted to the project fails to redirect properly.
\n
Created by Pooria Asteraky, WP School launched with the goal of bringing WordPress education to the masses. Classified as a (MOOC) or massive open online course, the site was dedicated to offering WordPress education and online courses in a variety of languages for people to use across the world. In order to get off the ground, Asteraky created a crowdfunding campaign asking for $25K. The campaign ended with only $1,087 pledged. With a severe lack of funding, WP School never made it out of the gate.
\n
Netropolitan also known as the “Facebook for Rich People” launched in late 2014. The site used WordPress and BuddyPress to provide a social network for those who had nothing better to do with $9K. After paying a $9K entrance fee, it cost $3K a year to continue membership. Netropolitan was featured on CNN and other major news outlets across the globe.
\nWhen Vice asked the site’s creator James Touchi-Peters, why he created the site, he responded, “This whole thing started because when I was traveling in my work, I wanted to get in on a social event where basically I could meet people like myself.” There must not be a lot of people like him because the service recently closed. Touch-Peters left the site online with the following message:
\n\nIt is with a sad heart that I report that the Netropolitan Club has been closed. In the end, there was not sufficient interest in our service among the targeted demographic to operate it as a going concern. (That said, I am happy to report that all paid members received full refunds.)
\nI personally would like to thank all those involved in this enterprise – employees, contractors, publicists, et.al. – as well as the paying members who took a chance on an unprecedented business model. I also would like to thank both the public and the worldwide media for their relatively intense interest, whether positive or negative. (It’s not often that Jimmy Fallon tells jokes about your business on ‘The Tonight Show’.)
\nThanks again, one and all. I’ll see you at the concert hall
There are likely several more products, ideas, and businesses outside of what we covered on the Tavern, that launched in 2014, but shut down before 2015 arrived. Keep an eye on the Tavern as there are several things that launched that are doing well and in the next few weeks, we’ll update you on how they’re doing.
";s: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, 09 Jan 2015 10:09: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: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:42:"WPTavern: The Geeky Tech Behind WordSesh 3";s: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:"http://wptavern.com/?p=37001";s: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:52:"http://wptavern.com/the-geeky-tech-behind-wordsesh-3";s: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:"
WordSesh 3 attracted more than 3,000 unique viewers from 89 countries. This equates to nearly three times the amount of people who attended WordCamp Europe 2014. With so many people interacting with the WordSesh site and 24 hours of live video sessions, it’s imperative that a webhost be able to deliver great performance. For the third annual event, Scott Basgaard partnered with SiteGround.
\nIn a post published on the company blog, SiteGround employee Hristo Pandjarov explains how they were able to hand the traffic load and keep the site online. The post is filled with geeky terminology and provides a glimpse into what it takes to host a mission critical site. The company used Linux Containers, built redundant infrastructure from the start, utilized dynamic caching, and more.
\n\nSince we didn’t want to risk any downtime with WordSesh, we opted for a hosting technology that we love for its almost unlimited ability to scale on the fly without downtime – the Linux containers. Using containers gave us the peace of mind that no matter what happens we will be able to add more resources both vertically and horizontally to each part of the infrastructure we built for WordSesh. At any moment, we had people on duty ready to add more resources or face any other potential issues.
Although I don’t understand many of the technologies involved, the end result is that the WordSesh 3 site stayed online throughout the entire event. I didn’t encounter any errors or experience problems watching sessions live. If you experienced problems accessing the WordSesh site during the event, let us know in the 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, 09 Jan 2015 09:50:10 +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:97:"WPTavern: WordPress 4.2 Will Automatically Enable Pretty Permalinks for New Sites on Installation";s: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:"http://wptavern.com/?p=36867";s: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:"http://wptavern.com/wordpress-4-2-will-automatically-enable-pretty-permalinks-for-new-sites-on-installation";s: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:2506:"
photo credit: gordon2208 – cc\nWordPress 1.0 introduced search engine friendly permalinks using mod_rewrite. Setting your site to use pretty permalinks is usually one of the first things that administrators do after installation.
\nWordPress 4.2 will add a new function that will automatically enable pretty permalinks, if the server supports it, at the time of installation. This means that in most cases you’ll never be greeted with ugly permalinks again.
\nThe new function is the result of a ticket that was originally opened seven years ago. In the upcoming release, pretty permalinks will be enabled if WordPress can verify that they work. It will cycle through the various permalink formats, and if they all fail to work, WordPress will fall back to ugly permalinks.
\nBy default, WordPress will set the following permalink structure for a new site, if possible, using mod_rewrite or nginx rewriting: /%year%/%monthnum%/%day%/%postname%/
Under configurations without rewrites enabled, it will set /index.php/%year%/%monthnum%/%day%/%postname%/ for PATHINFO (“Almost Pretty”) permalinks.
Eric Lewis, a contributor on the ticket, commented on the upcoming change, “Delivering pretty permalinks by default seems in line with a bunch of core philosophies – great out-of-the-box, design for the majority, simplicity, clean, lean and mean.”
\nIf you frequently create new WordPress sites or development sites, the automatically enabled pretty permalinks in 4.2 should save you a step in the setup process.
";s: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, 09 Jan 2015 06:11: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:13:"Sarah Gooding";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:117:"WPTavern: Plugin Authors: How to Avoid Download Prompts Associated with Screenshots on the WordPress Plugin Directory";s: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:"http://wptavern.com/?p=36949";s: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:126:"http://wptavern.com/plugin-authors-how-to-avoid-download-prompts-associated-with-screenshots-on-the-wordpress-plugin-directory";s: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:2599:"If you’ve ever clicked on a screenshot in the WordPress plugin directory and received a download prompt, you’re not the only one. In fact, it’s a widespread issue that affects a number of plugins. Screenshots are important as they help with troubleshooting, previewing features, and give users a sense of what to expect when it’s activated. But if you can’t see important details, they’re a moot point.
\n
Plugin Screenshot Download Prompt\nMika Epstein, who reviews plugins before they’re added to the directory, wrote about the issue in early 2014. The prompt appears for images that use the incorrect MIME Type. Otto explains how to set the correct MIME Type using TortiseSVN on Windows or where to look if you use a different SVN client.
\n\nOn Windows, using TortoiseSVN, you can right click the screenshot file, and select the TortoiseSVN->Properties menu. There you will find the svn:mime-type property, probably incorrectly set to “application/octet-stream”. Change that to the proper mime type of “image/png” or “image/jpg” accordingly. Afterwards, commit the change.
\nIf you prefer command line SVN:
\nsvn propset svn:mime-type image/png screenshot-1.png
\nsvn commit
\n
\nOr similar. If somebody uses a different SVN client, look for “properties” and then the svn:mime-type property.
Once the changes are made, upload them to the plugin directory. They’ll take effect once the directory is synchronized. It’s a simple change that vastly improves the effectiveness and user experience of viewing screenshots.
";s: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, 09 Jan 2015 01:19: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: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:25:"Matt: Easy Security Guide";s: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:21:"http://ma.tt/?p=44577";s: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:41:"http://ma.tt/2015/01/easy-security-guide/";s: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:422:"There’s a simple, unattributed site called Decent Security which has very nice common-sense but effective advice on security. I believe it’s from the same person as behind the Infosec Taylor Swift account. It’s refreshing like reading Bruce Schnier’s blog.
";s: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, 09 Jan 2015 00:40:00 +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: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:47:"WPTavern: WPWeekly Episode 176 – Farewell Kim";s: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:44:"http://wptavern.com?p=36934&preview_id=36934";s: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:53:"http://wptavern.com/wpweekly-episode-176-farewell-kim";s: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:1643:"This special episode of WordPress Weekly doesn’t have any news or plugin picks of the week. Instead, it’s dedicated to the late Kim Parsell.
\nI describe the experience of January 2nd where Brian Layman and I drive to Kim Parsell’s house to check on her. After telling the story, I share a couple of funny memories I have of Kim, like the time I called her #wpgrandma. Near the end of the show, we discuss the outpouring of support from the WordPress community and a special memorial page created by Suzette Franck.
\nNext Episode: Wednesday, January 14th 9:30 P.M. Eastern
\nSubscribe To WPWeekly Via Itunes: Click here to subscribe
\nSubscribe To WPWeekly Via RSS: Click here to subscribe
\nSubscribe To WPWeekly Via Stitcher Radio: Click here to subscribe
\nListen To Episode #176:
\n
Web accessibility guideline are constantly in flux, making it difficult for site administrators to keep pace. Even if you have a decent grasp on the basics, changes to your theme, plugins, and content can introduce new accessibility issues that you didn’t anticipate. Legal requirements may soon put publishers under the gun for accessibility compliance.
\nPlugin developer and WordPress Accessibility team member Joe Dolson has just released a tool that will help the average WordPress site administrator to identify and tackle accessibility issues with the help of automated testing. Access Monitor, now available on WordPress.org, is a plugin that runs accessibility tests on both the front and back ends of your site, powered by the new Tenon.io API.
\nTenon is an automated accessibility testing service developed by Karl Groves. It’s designed to make accessibility testing less painful for developers. Groves has taken the “API first” route in order to create flexibility for developers interested in building tools for content management systems, browser extensions, IDE plugins, etc.
\nAccess Monitor is the first plugin to use the Tenon API for testing WordPress sites in the admin. It generates a report that identifies each issue, where it’s found, and who is affected by it. With that knowledge you can work on improving your site’s overall accessibility. Here is an example of results for a single page:
\n
Accessibility reports generated by the plugin are configurable and can return results for multiple pages at once.
\n
Access Monitor includes the following features in its automated testing:
\nIt’s important to note that a perfect score from Access Monitor doesn’t necessarily mean that the theme you’re using meets WordPress accessibility guidelines or that your site is perfectly accessible. Dolson notes that the plugin only tests issues that are machine-testable, which means that it cannot detect keyboard issues, color contrast, etc.
\nAccess monitor incorporates the current 72 tests outlined by the WCAG criterion for accessibility best practices. This includes items such non-text content, focus order, images of text, and the ability to resize text. Tenon plans to add 43 new tests in the first quarter of 2015.
\nTo get an idea of how the testing works without installing the plugin, you can run your site through the Tenon.io testing tool. Having the Access Monitor plugin on hand is useful for when you want to test multiple pages, schedule tests, and keep records in order to monitor your site’s accessibility performance.
\nThe WordPress Accessibility Team, of which Dolson is a member, is mobilizing in 2015 to carry out a plan of action that would make accessibility required for all themes hosted on WordPress.org. The team has a number of hurdles that it will have to overcome in order to get this approved by the Theme Review team, including further education for theme developers.
\nAutomated accessibility testing for WordPress is an important first step towards making users and developers more aware of accessibility best practices. With high quality automated tests like these, there’s no excuse for being completely in the dark about your site’s accessibility issues. Dolson’s new tool puts the knowledge of accessibility experts into the hands of the average WordPress user, who is capable of implementing many of the text content-related recommendations.
\nIf you want to see how your site measures up with current web accessibility guidelines, download Access Monitor from WordPress.org. The Tenon.io API key is free to anyone who signs up.
";s: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, 08 Jan 2015 22:26: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:13:"Sarah Gooding";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:84:"WPTavern: Show Support for Free Speech with the Je Suis Charlie Plugin for 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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=36865";s: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:"http://wptavern.com/show-support-for-free-speech-with-the-je-suis-charlie-plugin-for-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3767:"
This week the world mourns with Parisians following yesterday’s terrorist attack at the headquarters of satirical newspaper Charlie Hebdo. Masked gunmen, claiming to be Yemeni al-Qaida, killed 12 people, including eight journalists and two police officers. The attackers targeted Charlie Hebdo’s daily editorial meeting, in protest of the publication’s controversial satirical depictions of religious figures.
\nIn light of the tragedy, French WordPress developer Julio Potier released a new plugin in support of the #jesuischarlie hashtag created to show solidarity with victims of the attack. The Je Suis Charlie plugin adds a black ribbon to the top right or left of your site.
\n
The banner links to the #jesuischarlie Twitter hashtag, which supporters are using to advocate for freedom of expression.
\n\n\nYou can kill journalists, cartoonists. You can''t kill the freedom of the press. You have only made their message stronger. #JeSuisCharlie
\n— Emily Koch (@EmilyKoch22) January 7, 2015
\n\n#Freedomofthepress cannot be killed. #FreedomOfSpeech cannot be suppressed. We are journalists, we will not be silenced. #JeSuisCharlie
\n— Marika Kataja-Lian (@katajalian) January 7, 2015
You can see a live demo of the plugin on Potier’s website. In just one day, the plugin has already been downloaded more than 700 times.
\nSince WordPress is one of the most powerful vehicles for free speech on the web, Potier decided to use his plugin development skills to create a way for WordPress users to show their support. “I did it to show my support for Charlie Hebdo, for all the families of the casualties, for all people involved in this tragedy,” he said.
\nPotier believes that the banner means more than simply showing support for victims but is also a rallying cry in support of freedom of speech. “Saying ‘I am Charlie’ means that nobody can shut the mouth of the freedom of expression,” he said.
\n“I am also Charlie; we are all Charlie. Terrorists, you killed 12 people, but you can’t kill all of us, you can’t even try. You thought you could kill this freedom by taking down this newspaper? Instead, you raise a country with its beloved friends, all over the world.”
";s: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, 08 Jan 2015 19:55: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:13:"Sarah Gooding";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:106:"Post Status: Yoast Google Analytics plugin introduces stats dashboards, with lessons learned along the way";s: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:30:"https://poststatus.com/?p=7305";s: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/yoasts-google-analytics-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:6046:"I look at my website stats a lot, but I typically just want a really brief snapshot to give me an idea of what’s happening right now on my website. I run both Jetpack’s WordPress.com Stats module and Google Analytics on this site, but I actually view the WordPress.com Stats many times more than Google Analytics, because they are right there in my dashboard.
\nWith the update to Yoast’s Google Analytics plugin, I can now get a similarly quick glance with either plugin.
\n
The new dashboards in Yoast’s plugin are nice, but definitely are what I’d consider a first iteration. It’s not a replacement dashboard for WordPress.com’s stats, yet.
\nFor one, the dashboard is only pulling in stats once per day, so it’s not exactly a right now sort of thing. When I look at stats, it’s often to see how a recently published article is “trending” and I usually care most about the current day’s numbers. Additionally, the basic stats only show Sessions and Bounce Rate. I rely heavily on seeing referrals and clicks out of my site.
\nBut that’s what early versions of new features are about. And the Yoast team has definitely learned a lot while rolling out these new dashboards.
\nI have had a notice on my site’s admin for a few weeks now, telling me that Google Analytics by Yoast can’t authenticate. I’ve re-authenticated a dozen times, but the notice has persisted. Thankfully, my stats were being tracked still, but I had no idea where that error was coming from.
\nThis morning, I finally decided it was time to investigate, and I learned that this problem persists across many sites where this plugin is installed. I also had a pending update for the plugin in my dashboard, and the update message claimed to fix the issue. For me and others, it seems to have done so; at least so that the notice only appears on the actual analytics pages and not site-wide (which was incredibly annoying).
\nSo, what went wrong? Well, I talked to Joost de Valk, Founder of Yoast, and he filled me in on the backstory.
\nGoogle Analytics are fetched via a WordPress cron job, and Yoast tells me that the lack of reliability (a common sentiment amongst plugin developers) of WordPress cron jobs can cause the plugin to think it needs re-authentication. Though he tells me there were a few other issues involved as well.
\nNow that the feature is a few weeks old, the plugin is only fetching data from Google once per day. That’s after they received a message from Google though. At first, they were grabbing the data live, and in a matter of hours they were far beyond the APIs limits.
\nJoost said to me, “We learned a lot in that week.” They had a number of releases in quick succession attempting to squash the issues pinging Google’s API. This included an update to using the newer OAuth 2.0 instead of 1.0 — which they had successfully used until the update.
\nI have no idea what it’s like to release code at a scale that Yoast is doing. They have increased their development team from one person (Joost) to five people in a pretty short amount of time; and that team is learning.
\nThat may not be a great excuse for causing issues with millions; but in my opinion it’s understandable, and it’s obvious to me their team is working hard to ship better products (which are basically all free for most people). I think as the team matures and lessons are learned, we’ll see better and better releases from Yoast — not that their current slate isn’t already the best on the market, proven by the fact that it seems everyone uses them.
\nAutomattic (with Jetpack) may be the only team in the WordPress ecosystem that knows what it’s like to create a plugin to scale like Yoast’s. And Automattic just surpassed 300 people. Yoast’s team, in total, is fifteen people. I’ve heard a decent amount of grumbling from the WordPress community about Yoast’s frequent — and sometimes seemingly flippant — update procedures. These grumbles may be warranted. At the same time, I think we can all extend a little grace in times like these. Scaling is hard, and many large or growing WordPress companies can attest to. I think Joost de Valk cares about his products and the role he plays in the WordPress ecosystem as much as just about anyone, and I’m pretty pleased with the direction they are taking their plugins.
\nThe updates to Google Analytics don’t seem like a whole lot right now — with a couple of new charts — but I think it has potential to be a great way to get a snapshot of site activity in the future.
\nOne thing is for sure: this plugin may have started as a simple way to embed Google Analytics code, but it’s evolving to be much more than that. Not everyone will care to keep using it as it evolves — and will opt for a simpler solution — but I think most users will welcome the changes and the new features. I certainly like the potential.
";s: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, 08 Jan 2015 17:04: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:"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: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:62:"WPTavern: Advanced WordPress Facebook Group Milestones in 2014";s: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:"http://wptavern.com/?p=36846";s: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:"http://wptavern.com/advanced-wordpress-facebook-group-milestones-in-2014";s: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:6519:"For the Advanced WordPress group on Facebook, 2014 was a great year. The group added key admins Joost de Valk and Danny van Kooten to cover the European time zone. It took two and a half years to reach 7,500 members, but after highlighting the group on the Tavern, membership skyrocketed from 7,500 members to more than 10,000.
\n
Advanced WordPress Facebook Group 11K Members Strong\nMatt Cromwell, who administers the group, highlights notable threads throughout the year. My favorite item from the list is when Matt Mullenweg joined the group and participated in an unscheduled Q&A session. In the thread, Mullenweg answered every question, including my own; Do you ever eat food that doesn’t look like it belongs in an art gallery? Like a Big Mac or something. His response:
\n\nI had McDonald’s as recently as Sunday, just a few days ago. I just don’t usually post it to my blog. McDonald’s I’m a chicken McNugget guy, though I’m curious about their new jalapeño burger. Burger King it’s always a Whopper. Growing up in Texas I have a soft spot for Whataburger and Sonic, I think In-n-Out is overrated but usually tasty, and I’ve been really enjoying Five Guys when I come across one.
\nI will always be happy with fried chicken from Popeyes or KFC, though the former has better biscuits and I grew up just a few blocks away from one. When Automattic had an office in the Mission in SF there was a KFC on the opposite corner and I’d often sneak over there for lunch or a late snack when I was in the office till odd hours.
The group is an excellent place to have discussions, but the things that bothered me in 2014 still exist. It’s hard to find posts using Facebook’s search feature because it sucks. There are a lot of threads where people ask for general tech support either with a theme or plugin. Although the group’s title says it’s about Advanced WordPress, it really doesn’t have a central identity and according to Cromwell, it may never have one.
\n\nThe name itself seems to cause confusion or lack clarity. Some are attracted to the group expecting seriously “Advanced” material. Others come to the group because they are learning and wanting to become advanced. Others see “Advanced” and think: “Perfect, I’ll go ask the experts how to fix all my problems.” With 11k+ members now, it’s hard to conceive of this group as having any kind of central identity.
With over 11K members, Advanced WordPress has splintered into several smaller groups. Doing a search for WordPress groups on Facebook shows the following results:
\nEach group on Facebook is like a silo with its own members and conversations. I can’t help but wonder how awesome it would be if a centralized discussion platform such as a forum, played host to all of these discussions. However, a Facebook group does have a few key benefits, such as focusing the topic of discussion and eliminating distractions from other groups. It’s also easy to pull people into a conversation by adding their name to a response.
\nI still don’t think Facebook is a great platform for conversations surrounding WordPress. It lacks the ability to style posts, browse archives, and easily browse topics. It’s also a walled garden and if Facebook decides to remove the feature or shuts down, a lot of great knowledge will be lost forever. However, with so many people on Facebook and the convenience of quickly participating in a conversation, I can see why a lot of people are happy to use it.
\nHow many of you would like to see an open discussion platform dedicated to WordPress topics that everyone can participate in? Is there a WordPress sub-community or watering hole that doesn’t exist that you’d like to see created?
";s: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, 08 Jan 2015 00:04: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:"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: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:94:"WPTavern: WordPress For Android Version 3.5 Embraces Google’s New Material Design Principles";s: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:"http://wptavern.com/?p=36774";s: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:101:"http://wptavern.com/wordpress-for-android-version-3-5-embraces-googles-new-material-design-principles";s: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:4010:"WordPress for Android is starting 2015 with a big update. Version 3.5 was released today, introducing major changes to the app’s overall design. This release follows Google’s new Material design principles, which was created to unify the experience of apps across platforms and devices. The design spec includes basic tenets for the various aspects of app design, including animation, layouts, patterns, and usability.
\n
Google’s goal with Material design is to “create a visual language that synthesizes classic principles of good design with the innovation and possibility of technology and science.” To that end, Material design incorporates three guiding principles:
\nThe WordPress for Android app interface now embraces these principles with new Lollipop components and styling. With the exception of a few features, such as ripple animations, these enhancements should also work for pre-Lollipop devices. You can see the changes most clearly when checking out the designs of the individual posts, the app menu, notifications, and post editor screens.
\n\n
\n
\n
\n\nAnother major change in version 3.5 is the addition of auto completion for mentions in comments. If you use the “@” symbol while typing, the app can now match blog member usernames, displayed via a popover.
\n
Auto completion is also integrated into the reader and notifications. It makes it easy for blog authors to interact more directly with readers in the comments. Participants in blog conversations can stay in the loop via the app’s notifications. Auto completion for mentions is a major update that should deepen the level of interaction on blogs and help keep users better connected.
The design changes in this version may come as a surprise to many users, but they make the app feel like a native part of the device. The additions make the app feel cleaner and more intuitive for mobile publishing. WordPress for Android version 3.5 is now available in the Google Play store. Update your app today to take advantage of all the new features and fixes.
";s: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, 07 Jan 2015 22:57: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:"Sarah Gooding";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:95:"WPTavern: Better Search Replace: A New Plugin for Updating URLs and Text in WordPress Databases";s: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:"http://wptavern.com/?p=36741";s: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:104:"http://wptavern.com/better-search-replace-a-new-plugin-for-updating-urls-and-text-in-wordpress-databases";s: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:4372:"
photo credit: Bunches and Bits {Karina} – cc\nWhen migrating a WordPress site to a new domain, you’ll have to update every instance of the site’s URL in the database. Some developers prefer to use tools like WP-CLI or WP Migrate DB to handle this, while others opt for a general database search and replace plugin with a UI in the WordPress admin.
\nSearch and Replace is an old plugin, with nearly a million downloads, that can be used to update URLs and text in the database. I used this plugin successfully for a number of years, but it went without any updates for long time. It has since come under new ownership, although the screenshots demonstrate just how long ago the plugin was released.
\nBetter Search Replace is a new take on database search and replace plugins. It was heavily based on Interconnect/It’s open source Search Replace DB script that performs replacement actions without damaging PHP serialized strings or objects. I’ve used this script a number of times with success, although it’s not as convenient as a plugin. The Better Search Replace plugin packages it up using native WordPress database functions and adds a friendly UI.
\n
The plugin merges the best features from older plugins and the Interconnect/It script to support the following capabilities:
\nSince searching and replacing in the database is a sensitive action to perform, the “dry run” feature gives you a good idea of what you can expect before pulling the trigger. Even with the option of performing a dry run, you will undoubtedly want to have a backup of your database created before touching it.
\n
Migrations aren’t the only reason for this type of plugin. Perhaps you’ve renamed your company or product line and need to replace all instances throughout your website. This plugin makes it safe and easy to perform the replacements directly within the WordPress admin. I tested it on a development site and found that it is fast and works exactly as advertised.
\nBetter Search Replace was created by Matt Shaw, author of the Revisr plugin that allows developers to synchronize WordPress with a remote Git repository. If you’re a long-time fan of the Interconnect/It script, you’ll find that this plugin is even easier to use. You can find Better Search Replace on 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 07 Jan 2015 21:19:54 +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:"Sarah Gooding";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:96:"WPTavern: Happy Joe to Host WP Boot Camp January 23: A Free Training Event for Military Veterans";s: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:"http://wptavern.com/?p=36751";s: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:"http://wptavern.com/happy-joe-to-host-wp-boot-camp-january-23-a-free-training-event-for-military-veterans";s: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:1827:"
Happy Joe is launching its first planned WP Boot Camp in San Antonio, TX on January 23, 2015. The non-profit organization helps US military veterans re-enter the workforce through training in WordPress and the web technology industry in general. Happy Joe was started by former service member James Dalman, who will be presenting at the first WP Boot Camp, along with other WordPress professionals.
\nThe three hour event will give military veterans and their spouses an opportunity to learn, network, and gain access to free resources and online training. Dahlman plans to assist attendees in setting up an online resume website using WordPress as a first step towards entering the web technology industry.
\nWP Boot Camp is free of charge to anyone with a valid military ID, thanks to event sponsors iThemes, Automattic, WP Site Care, and WebTegrity. The event will be held at Geekdom San Antonio, the largest collaborative co-working space in Texas. However, it is limited to 30 attendees, so those planning to attend must RSVP.
";s: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, 07 Jan 2015 19:00: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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";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:27:"Matt: WP.com Year in Review";s: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:21:"http://ma.tt/?p=44587";s: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:43:"http://ma.tt/2015/01/wp-com-year-in-review/";s: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:192:"There’s a great write-up of the human side of WordPress.com’s 2014 as well as some impressive numbers.
";s: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, 07 Jan 2015 18:53:00 +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: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:32:"Post Status: The ABCs of the web";s: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:30:"https://poststatus.com/?p=7300";s: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:32:"https://poststatus.com/web-abcs/";s: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:3244:"I wanted to change my primary URL, and also setup HTTPS on my new VPS.
\nSo, I bought an SSL cert that required I add a TXT record to get a verification email. The domain was new so I needed Google MX records added to receive the new email. Ah, but I also changed the DNS provider where I put those records. Thankfully, the TTL for new records was short and I got squared away so I could submit a CSR and get the SSL. I had to make sure to choose a CDN provider to support SSL too, and it happened to be the same place that handles my DNS now. This service also GZIP compresses as much as it can.
\nThe domain is square now so I SSH’d into my new VPS to set a few things straight. For one, I needed to edit the MySQL DB with WP-CLI to search and replace the new URL. But I accidentally forgot to exclude the GUIDs so my RSS went haywire.
\nMy VC is kinda jacked for deployment purposes, though I’m learning to handle dependencies and repo management with a JSON file via Composer. But I’ll still need to deploy my Git repo with something like Dploy.io. For now I had to cowboy up and SCP some new stuff to the server, since it doesn’t have (bad practice) FTP. Then I noticed I screwed something up, so I used Vi to edit it live, like a madman.
\nMy new CDN provider not only delivers but also caches HTML, CSS, and JS. That’s on top of what JS-based Grunt does on the theme side, where my front-end JS is concatenated and minified, and my Sass is pre-processed to CSS. Grunt is also managed with a JSON config file, where I can do these things and more: like linting, combing, .pot generation, and auto-prefixing my Sass. I can even generate RTL-specific CSS if I need to. I’m told that hardly scratches the surface still.
\nIn order to do these things, I work locally with VVV, so these scripts can run. That lets met setup custom LEMP stacks to my heart’s content, stored in a www folder. I can even do auto-site generation with one of many custom shell scripts, though you have to watch out if the project structure isn’t the same as yours. VVV supports WP-CLI too, so that’s nice.
\nNow the live site is HTTPS instead of HTTP, and because of new tools and modern browsers (that support stuff like SPDY and SVG) my website has fewer HTTP requests, and weighs less than a single MB.
\nAlso, I better not forget to 301 the old URLs to the new URLs with the domain change; that’s easy with nginx and will help me keep my SEO.
\nOf course, these things are happening while building my site with my CMS of choice, which is also the one largely considered the easiest to work with: WP. And I’m not even close to done. I have so much to learn, APIs to explore, and mistakes to make.
\nThe moral of this silly story, is that building and maintaining websites is still pretty complicated. In fact, I think it may be more complicated than ever. I always feel like a kid learning his ABCs, but that shouldn’t stop us. Don’t get intimidated. Dig in. Eventually we learn to string a few sentences together, or even a story.
";s: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, 07 Jan 2015 18:16: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: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: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:40:"Post Status: A new look and a new domain";s: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:30:"https://poststatus.com/?p=7287";s: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:43:"https://poststatus.com/new-look-new-domain/";s: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:12091:"Last night I launched version 3 of Post Status. The site design was about a year and a half old and in the first two iterations I never put too much thought into it as much as just trying to get something out the door as soon as possible. This time, I tried to build something that could be a foundation for a while.
\nI’m going to try and walk you through much of my thought processes. Hopefully it gives you insight to what I’ve been up to, as well as perhaps point you to a new resource or two. And if you have advice for me, I’ll take it.
\nI never really expected Post Status to be my business, but now it is. I realized that some early decisions were mistakes — like not having the .com for the domain. Poststat.us was a fun domain hack and the .com wasn’t available, but it was also a branding issue. The site’s name is Post Status, not PostStat.us or poststat.us or whatever else. That’s always been hard to shake.
\nA few days ago Greg Wallace pointed me to a Flippa auction for the poststatus.com domain. I was both pleased and annoyed. I tried — in the past year or so — to contact the owner privately multiple times and never got a response, even with a direct offer of cash. Nevertheless, I bid on the domain and even got the seller to give me a buy it now option so I could guarantee the domain. It was $800, but I think I got plenty of value in the transaction. All of that happened just yesterday.
\nAnother important thing to me was making the entire site utilize HTTPS. I’ll need it for the eCommerce memberships anyway, and it’s a good practice and even has speed benefits. Post Status is now on a custom VPS product that I’m working on with SiteGround.
\nThe site is on a LEMP stack, and utilizes a variation of their GetClouder product. DNS, CDN, and additional caching elements are provided through Cloudflare Pro, which took me a while to settle on. The SSL certification is from DigiCert, which had great reviews.
\nI’m really excited about using nginx as well as being able to take advantage of SPDY. My site is now more secure, faster, more customizable, and ready for the future. Meanwhile, I was able to knock out two redirects (for the new domain and from HTTP to HTTPS) in one go.
\nThe logo featured above is probably not finalized, but it’s about where I want it to be. I sketched out logo drafts for months and Sara Cannon helped me put the first version into Illustrator. The one shown in the featured image is a bit thicker than the original, since the thinner one is tough to scale at small sizes.
\nI’ll probably be tweaking this with the help of someone less like a bull in a china shop within Illustrator as I am, to get it cleaned up and swag-ready (oh yeah!). Either way, I’m happy to finally have a logo for this project, and I think it represents both the brand and the nature of the site pretty well.
\nThe part of the site I’m most excited about is the new theme design. I’ve had this concept in mind for months, but didn’t really execute the latter half (aka 90% of it) until the last couple of weeks.
\nIn general, finding things based on topic and search should be a lot better, and the reading experience is more focused than ever. I went one column on article pages — something I’ve wanted to do for a while. And I went to a two-column format for archives, minus the latest article that sits in a featured spot on the home page.
\nThe development is based off of Underscores, which I’ve grown to love. I’m using Sass for the preprocessor, though with a different structure than base Underscores. Though I’m no longer using Hybrid Core (I still love it), I am using Get The Image from it to wrangle some default featured images on legacy archives.
\nOne thing you may notice is the icons. Everything is SVG, using Iconic. Iconic makes using SVG super simple. I just insert the SVG of choice with an image tag and the Iconic JS (that’s minified in my primary JS via Grunt) actually changes the image tag to inline SVG. Iconic also has small, medium, and large versions of each icon, which will be pretty cool for some of the larger ones I intend to use for other landing and member page templates. One thing I don’t like is the FOUI (flash of unstyled icon — I just made that up) when I load the page. Hopefully that gets cached and doesn’t happen often, but I sometimes see it working locally.
\nThe call to action for memberships on the homepage is also something I debated a lot. I’m excited about how it came together, mostly because that section will also be the member dashboard for folks once they’re logged in; so the CTAs shouldn’t be too obnoxious for those that follow them.
\nThis design is super alpha and I’m very willing to receive feedback of what you like and hate. I have a lot of known issues too. The bottom half of article pages have a ton of work to do. The footer doesn’t exist yet. And I have to build out templates for new sections of the website.
\nPart of the new theme is new typography. I have stayed with Typography.com‘s delivery service — mostly because I am just too in love with Gotham Rounded for my titles.
\nI do have some performance concerns, as Zack Tollman outlines, but I have reduced the font’s package size considerably — from 9 fonts to 6, and they are smaller sets as well.
\nI’m still using Gotham Rounded for the logo, buttons, and for main headers and titles. It’s just so pretty. But I’m only using a single weight, since the use is quite controlled.
\nI’m also using a single weight (light italic) of Sentinel, an incredible slab serif, for archive titles, taglines, and pullquotes. Sentinel is replacing four weights of Archer. I thought about not using any serif, but I think Sentinel is worth it.
\nThe body font is the biggest change. I’ve gone from Gotham Rounded to Gotham Narrow. It’s a more traditional sans-serif, and I think it’s both slightly more serious and slightly more readable. I toyed with the idea of listing (but not hosting) a series of sans-serifs for body, to gain speed improvements by downloading the best available local fonts from the reader; but I discovered I’m too picky for that. That said, the four weights I’m using of Gotham Narrow are lighter than Gotham Rounded was.
\nPerformance has been a primary concern throughout the redesign. I’m trying really hard to consider whether I need things.
\n
\nOne takeaway is that performance is a multi-faceted, challenging endeavor that spans design, development, and infrastructure. All in all, Post Status is way faster now.
Some of that is hardware, with nginx on a VPS and SPDY support with HTTPS. But the theme is faster too. I’m using no images unless they are in a post. I’m not using an icon font, but instead using SVG. I’m using Grunt to concatenate and minify various theme scripts. Fonts are still a burden, but one I decided was worth it.
\nAnd then there are plugins. Oh, plugins.
\nWrangling Jetpack has been tough. I’m probably screwing up some features on the site, but I’m basically dequeuing everything Jetpack spits out. However, I’m confident I’ll be able to wrangle Jetpack okay, as I’m really only going to use Related Posts and Sharing as front-facing features; and though neither is shown here today, both are manageable without Jetpack’s styles and scripts.
\nGravity Forms is another one I still have to wrangle. A simple newsletter signup form (a single email field) is causing four stylesheets and two Javascript files to be loaded on every page. That can’t happen, so I have some work to do there.
\nGenerally, finding, dequeuing, and enqueuing styles and scripts from plugins is just annoying. I totally understand why folks tend to just not bother. I would love to see product makers start offering guides on how users can responsibly enqueue such things on their own.
\nEspecially with something like forms, I don’t want to remove a script that prevents the form from working properly. But I do want to remove pointless stylesheets that don’t matter at all to my simple forms. I don’t mean to pick on Gravity Forms, as I freaking love Gravity Forms. I just want to figure out how to make complex plugins more performant. Every http request matters, you know?
\nAll in all, every page load is under pretty well under 1MB uncached, and making between 25-50 requests. I’d like to keep it that way, and really I’d like to make sure full page loads are under 1 second always, and usually under 500ms. I have a lot of work to do!
\nToday is an early Alpha of the new site. I’ll walk you through some of what’s left or still in progress:
\nDeployments. My deployment method for this site is terrible. I spent a lot of time learning about Composer (will have posts on that) and I may use it, but either way I’ve got work to do on proper repo management and deployments. This is especially the case since I’m trying to both manage the site’s private repo as well as share the theme and functionality plugin as their own repos for others to use, see, and contribute to.
\nMemberships and membership functionality still have a long way to go. I’m using WooCommerce, Subscriptions by Prospress and (most likely) a product that’s in Alpha/Beta from SkyVerge for content restriction and other member features. I’m using the Mailchimp API to create a custom email to send to members with new private content; that’s been fun to learn.
\nI’ve created two new content types (Notes and Resources) that are going to be members only. Notes are like the old links, but now a members only blog and newsletter. Resources will be mostly members only with some free stuff, and will be evergreen informational content. Then I’m creating a Profiles content type to create static pages for people and companies (think Crunchbase for WordPress), as well as a cross-relational tool for posts about those folks.
\nThe goal with the new Post Status is to provide useful and informative free content for everyone, but go above and beyond for members. I’m working hard to make that content accessible, digestible, high quality, and trim enough for busy WordPress professionals.
\nOkay, this is way more than you needed to know. If you read all that, you are my ideal customer.
\nI can’t wait until I can show you guys the rest of the site! I’m having a blast spending all of my working time on my own project. It’s a professional euphoria I’ve never known until now.
";s: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, 07 Jan 2015 16:11:01 +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: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:76:"Post Status: Website micro services provider, Elto, is shutting down for now";s: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:30:"https://poststatus.com/?p=7258";s: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/elto-shutting-down-temporarily/";s: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:4615:"Elto, formerly Tweaky, is a micro services provider, for lack of a better term. They started with $25 tweaks, which until they shut down services today, worked it’s way to a $199 minimum.
\nWordPress is a high focus vertical for Elto’s, and I presume it’s their largest as well. Elto is one of several such providers of micro services like this; others still running are Codeable and Envato Studio (formerly Microlancer). These are besides the longstanding generic types (with rather poor reputations, in my opinion) such as oDesk and Elance.
\nI have always kept track of Elto, as I started referring folks to them from my own contact form for small projects, in order to narrow the leads I was getting. When I got the email today from Ned Dwyer, Elto’s founder, I went to my dashboard to see how many folks had used my referral and what those services were:
\n
In the time I was referring folks to Elto, I sent them nearly $2,000 in business and got a 25% referral fee. That’s not a lot; more interesting is that of these referrals, there was an 8.5 / 10 satisfaction rate. I wouldn’t say that’s outstanding, but it’s not bad either. It’s probably better or close to the satisfaction of more traditional web services providers.
\nI emailed Ned to see if he could offer any more insight into this decision. He responded with the following:
\n\n\nIt was something we thought long and hard about before making this change.
\nThe challenge is that the current model was working well – customers rate us on average 8.7 out of 10, thousands of new customers every month etc – but it wasn’t delivering the kinds of results we wanted. This will become clearer when we launch the new version.
\nWhile we could have kept going with this model while working on the next version in the background, the current model has significant customer support challenges. This puts a burden on our team to maintain the current app and customer base which draws resources away from us working on what’s important.
\nWe have the full support of our team and investors in making these changes and we’re excited about what’s next.
So it appears that this is a temporary stop for Elto. I’m sure — with investors to answer to — rising support challenges makes change inevitable.
\nI’ve always liked the idea of companies like Elto from a developer standpoint. As long as the company values the developers they are mediating for, it can be a nice way for junior developers or just folks that don’t want to interact with clients much to be able to get work. It can also be a way to fill in the gaps in someone’s own freelance work.
\nI’m not sure what the next version of Elto will look like, but it seems they’re aiming to be more in the product business and less in the service business.
\nFrom what I can gather, they raised at least a seed round in 2012, reported at $460,000, and perhaps another round in 2013 from Blackbird Ventures.
\nI guess my primary takeaway from a change like this is that even when companies are productizing services, doing work for cheap isn’t easy. Support struggles, maintaining customer expectations, managing developers — it’s all tough. I am curious if Codeable and other what I’d call “progressive” members of this style market can relate to Elto’s struggles, or if they have somehow managed to get past those.
\nFor some additional reading on Elto’s journey, Ned’s post about what they learned in their first two years was insightful. He also hints they considered a pause even then; so I guess today shouldn’t be too much of a surprise.
";s: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, 06 Jan 2015 23:30: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: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: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:39:"Post Status: WordPress 4.1, “Dinah”";s: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:30:"https://poststatus.com/?p=7245";s: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:43:"https://poststatus.com/wordpress-4-1-dinah/";s: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:7094:"
\nWordPress 4.1, “Dinah”, has just been released. WordPress 4.1 is the result of months of work and includes a number of excellent new features.
WordPress 4.1 was led by John Blackbourn, who did an outstanding job. Two hundred and eighty three contributors were part of WordPress 4.1, which Matt Mullenweg states is a new high.
\nHere are some of the new features.
\nI must begin with the new persistent Distraction-free Writing feature, as I’m using it to write this very post. We’ve had Distraction-free Writing since 2011, with the release of WordPress 3.2. However, it’s always been a single-experience decision. You hit the button to enter distraction free mode, and you utilize it for a single writing session.
\nNow, the button itself is persistent, and the experience of writing distraction free doesn’t enter a new screen, but rather fade away the distractions of the default editor.
\nhttps://cloudup.com/cqbFU6CSqm2
\nThe left admin seamlessly floats away, as do the metaboxes to the right of and below the editor. The editor itself remains, versus using a modified editor like before.
\nWhen you update to WordPress 4.1, you are triggered with a note about Distraction-free Writing, and now that it’s a decision you only have to make once, I think this feature will finally get the broad use it deserves. It really is much more pleasant to write without everything else around you, to be lost in your thoughts as they make their way to the editor.
\nhttps://cloudup.com/cgjoFpPJvYk
\nThe Twenty Fifteen theme is the finest work I’ve seen yet of the default theme team. A blogging, and personal, theme — Twenty Fifteen is simple, with beautiful typography, and capable of showcasing blog posts of any format with poise.
\nTwenty Fifteen comes in six base color schemes: default (light), dark, yellow, ping, purple, and blue. It also supports WordPress’ background and header image features, and allows you to customize colors from your base selection; Twenty Fifteen can be as quirky as you are.
\nhttps://cloudup.com/cFEI4yyaDmU
\nHere’s a link to the default theme demo, as well as it’s new page on WordPress.org.
\nhttps://cloudup.com/ckbOnTY71Gq
\nWordPress has made tremendous progress for non-English speaking users in the past few releases. With WordPress 4.0, you could choose a language on installation, whereas before it required many more steps. Now the team has gone a step further, so that language can be changed at any time, right from WordPress’ general settings page.
\nGiven that a third of WordPress installs are non-English (and if I recall correctly half of new downloads are non-English now), this change further reduces the barrier of language in publishing software, and is an excellent move for the progression of the platform across the world.
\nhttps://cloudup.com/cQi9LX744H8
\nI believe recommended plugins is probably the most controversial feature in WordPress 4.1, though it is not without precedent. “Featured” themes have been in the WordPress dashboard for a while now. But with a tab for recommended plugins, now users can see plugin recommendations based on plugins already installed and plugins other sites have installed.
\nRecommended plugins are replacing the former popular plugins tab, and is mostly a change in the underlying API for showing the plugins themselves. Since it’s not a manual recommendation, I think this is a good change, and will more accurately help folks find relevant plugins than just listing the most popular plugins in the directory.
\nI’m really looking forward to using some of the new template tags introduced in WordPress 4.1.
\nMy favorite is get_the_archive_title(). Themers out there all know about the big blob of conditionals in most theme archive templates to spit out the right string based on which archive template it is. Now, there’s a function for that, and it’s fully filterable to boot.
Descriptions of the new title functions, some new pagination functions, and some particularly nice body class assignment enhancements are well described on this Make WordPress post by Konstantin Obenland. There’s also a post about adding theme support to let WordPress handle title tags, which is a handy thing.
\nA relatively small but nice security feature is the new ability to log out of all installs from a single location. WordPress uses cookies to keep you logged into your install for a period of time. Well, if you ever leave yourself logged in on a computer you don’t trust, you can now log out of all instances easily, from your profile page on an install.
\nThere is a new button that says “Log Out of All Other Sessions,” and also tells you if you are logged in at more than one location.
\nI love how much progress has been made on the WordPress query tools in the last couple of years. WordPress 4.1 introduces the ability for a nested query syntax, which makes more complex queries possible for WP_Tax_Query, WP_Date_Query, and WP_Meta_Query. I don’t often call out single individual’s work on something, but Boone Georges really slayed it with the nested queries work. He wrote about it on his blog in detail.
WordPress 4.1 includes many other under the hood features you should check out on the Codex page about the release.
\nWordPress is better than ever, and hundreds (or thousands) of people make it so. Great job everyone. Now, go download WordPress 4.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:"Tue, 06 Jan 2015 23:30: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: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: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:38:"Post Status: Let’s WordSesh together";s: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:30:"https://poststatus.com/?p=7232";s: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://poststatus.com/lets-wordsesh-together/";s: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:1513:"
This weekend, WordSesh 3 will begin. WordSesh is 24 straight hours of live streamed presentations and discussions from a variety of intelligent folks in the WordPress world.
\nIt starts at 0:00 UTC Saturday, which really means 7:00 p.m. Eastern time on Friday for those of us in America. It’ll run through Saturday evening.
\nThe lineup for WordSesh is as good as any WordCamp, and the chat around the past events has been fantastic. Scott Basgaard and his team of volunteers do a great job.
\nI’ll be on a WordPress news roundtable at the tail end of WordSesh. On Friday, I’m going to have some news that will help explain my radio silence of late, and will probably spice up the conversation I’m to have with Jeff Chandler (of WP Tavern), Dre Armeda and Brad Williams (of DradCast) and Doc Pop (of Torquemag). I hope you’ll watch.
\nCheck out all the information on the WordSesh website, follow @WordSesh on Twitter, and RSVP if you’d like to attend. There are already over 600 people signed up. It’s completely free and community supported. I love this event and I’m glad to see it happen again.
";s: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, 06 Jan 2015 23:30: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: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: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:54:"Post Status: Matt Mullenweg’s 2014 State of the Word";s: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:30:"https://poststatus.com/?p=7213";s: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://poststatus.com/matt-mullenwegs-2014-state-word/";s: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:11832:"
\n“Oh, my name is Matt Mullenweg by the way. Nice to meet you.”
After the WordPress co-founder welcomed the largest WordCamp San Francisco audience ever, he introduced himself and began this year’s State of the Word — the annual talk where he provides insight of the last year of WordPress and inspiration for the future.
\nedit: The video is now available:
\n\n\nWordCamp San Francisco has been here in Mission Bay for 7 years, and it’s the last year here. Next year, things are going to change. There will be a WordCamp US (Matt notes it’s a working title) that will be modeled similarly to WordCamp Europe. The name, location and date are yet to be determined.
\nThis year there were over 33,000 responses to the annual WordPress survey.
\nOnly 23% of the survey respondents were from the United States — a 6% increase of international respondents. And for the first time ever, non-English downloads surpassed English downloads. This change is much due to the new internationalization tools in WordPress core itself.
\nA quarter of the respondents now make their living fully off of WordPress — 7,539 people from the survey pool. Matt estimates those people alone make up for more than a billion dollars of economic impact.
\nOf those people surveyed, they have between half a million and a million currently active websites they own or have developed. And 91% of those sites took less than 200 hours to make.
\n
Since last summer and the last WCSF, we’ve had five major releases of WordPress. Matt spent some time going over some of the features we’ve gained.
\nFrom WordPress 3.6 to WordPress 4.0, WordPress has evolved an enormous amount in a short amount of time. It’s better on mobile; has a better user experience; is more performant; is easier to use for both developers and end users; and is the best publishing tool in the world.
\nThere have been seven release leads in that time:
\nAdditionally, Matt highlighted another 8 significant contributors and five new committers to the WordPress project.
\nIn these five releases, there have been 785 contributors to the project. And Matt also highlights John Blackbourn — the WordPress 4.1 release lead, which will soon enter beta.
\nSince last summer, WordPress has grown “two Drupal marketshares.”
\nThere have been 684 theme additions to the repository this year — a 36% increase year over year. There are now 2,781 themes in the repo.
\nThere have been two updates for Android, five for iOS, and we abandoned older platforms to focus on a better user experience. “Sorry, both of the Windows phone users,” he joked.
\nMatt notes that there are now more mobile phones than humans on earth, and that this will continue to be a huge priority.
\nNoted in the last WCSF State of the Word, developer.wordpress.org is now live. A little later that hoped, he noted, but it’s a huge achievement and improvement for WordPress documentation.
\nThere are over 100 meetup and WordCamp organizers here at WordCamp San Francisco. Matt asked them all to stand, with a personal thanks to their commitment to a difficult, but rewarding task.
\nWe have a long way to go with Internationalization, but Matt highlights some of the progress and promise for the future, including the advancement of language packs that plugin and theme developers will be able to take advantage of.
\nSoon — with the release of WordPress 4.1 — Matt announced that the WordPress plugin and theme directories will be fully localized, making it more accessible and fully translated for non-English speakers.
\n“The discovery process [of themes and plugins] is prohibitive” unless we make it a priority to offer the same discovery features that are in English to other languages.
\n\n“We have the potential — thanks to the web — for WordPress to be a truly global experience.”
Matt is promising a better offering of statistics for WordPress theme and plugin providers — a task that’s being worked on right now by the .org team.
\nThese are numbers people have long wanted and are very difficult to get. This is a very welcome change.
\nMatt says only 25% of users are on the latest install, WordPress 4.0. While he notes that it’s far better than it was in the past, we still have a lot of improvement we can make.
\nAnd he goes into the importance of removing versions from the conversation in software. Users should not know or care the version of their software. They should only know that it works.
\n“Our vision is that we’re like Chrome. … And the hosts have helped pioneer this.” But WordPress itself will eventually move to such a model; this is a thing that is controversial, but I believe it is an essential and inevitable evolution.
\nMatt asked how many people had been hacked — and even in a room full of professionals — it was a lot of people. This is why updates are important, as updated WordPress installs are much safer.
\nMatt spent some time talking about WordPress support for more modern versions of PHP.
\nWordPress is notorious for being a poor supporter of modern PHP. But that’s ready to change.
\n\n“We’re going to start working with hosts to get everyone on PHP 5.5 or above.”
Matt is excited about Twenty Fifteen, this coming year’s default theme. He notes this is our fifth year with a new default theme, and it’s the same number of years that Kubrick was the only default theme. A massive success.
\nMatt Mullenweg says that starting this year, you can submit a pull request to WordPress on Github, “and that will not go into a black hole.”
\nHe asked how many people are using Github, and nearly everyone raised their hand. This removes a barrier to contributing to WordPress, and is a huge improvement.
\nHe also says that all development of the WordPress mobile apps is now on Github. It’s also worth noting that much of Automattic’s internal projects, like Jetpack, are run on Github.
\nFor the first time in 11 years, WordPress is leaving IRC for primary organization communication. We’re going to try a tool called Slack, built by a company in San Francisco started by the former founder of Flickr. Slack has taken over communication in remote teams, from my experience, and will be excellent.
\nSlack will also help us make use of integrations and notifications. Right after the talk, chat.wordpress.org will lead any WordPress.org user to a method for using Slack for communication.
\nThis is a huge partnership, and as someone that uses Slack daily, I’m incredibly excited. I’m sure there could be pushback for using a paid tool for this, but it’s certainly and interesting experiment and I’m excited to see what happens.
\nIt appears clear to me that contributing to WordPress will now be easier than ever.
\nMatt talked about his controversial blog post about the concept of Five for the future, something I also opined about.
\nMatt highlighted three companies: Gravity Forms, WPMUDev, and Automattic are all now contributing 5%. Of course he notes others are doing it as well, but wanted to highlight those that have committed to doing it publicly.
\nMatt discussed a number of ways people can contribute, and that folks can attend sessions to learn how to contribute both here at WCSF and at most other WordCamp events.
\n\n“A contributor, by the way, is a title that no one can give you except yourself.”
He called it an altruistic mentality of contribution.
\n\n“Who’s excited about the REST API?”
Nearly everyone responded with enthusiasm. Matt talks about how WordPress.com has had a similar API for years now, and what they’ve learned, and how much potential there will be for the core version, and the importance for marrying the .com API and the .org API as they each approach 2.0.
\nMatt wants us to re-think “the WordPress engine” as a kernel that can a hub for building all sorts of things that are more capable to be fit into a proper architecture for the case at hand versus “shoehorning” existing WordPress features to areas that aren’t really meant for it.
\n\n“Maybe what we need isn’t a way for theming the WP admin; maybe what we need is a way for 1,000 WP admins to be built.”
And for those admins to be able to fork each other, learn from one another, and create better and catered publishing experiences catered to specific use cases.
\nWe can expect the core WordPress JSON API in 2015.
\nMatt discussed how important mobile is to the future of the web, and therefore WordPress. “They are winning,” he says about the phones, and says how phones are more available and evolving every year. “They’re getting bigger and bigger,” and the interfaces and methods for interacting with our phones are evolving as well.
\nMatt believes that WordPress can play a central role in the further evolution of mobile applications and the mobile web. As the power of mobile devices gets better, Matt believes that the web will become a bigger part of the mobile experience than it is now — when the conversation seems to be completely centered around apps.
\n\n“This is one of the ways that we can be truly global.”
To democratize publishing, is the mission of WordPress.
\nWordPress is a community, Matt states, and accessibility from a language, device, and any other point of view is critical to the mission 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 06 Jan 2015 23:30: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: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: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:87:"Post Status: Postmatic wants to revitalize your WordPress email, starting with 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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"https://poststatus.com/?p=7197";s: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://poststatus.com/postmatic-wordpress-email/";s: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:4912:"
Postmatic is a new WordPress plugin that I think is quite promising. It’s aim is to eventually change the way you utilize WordPress email in many ways, but its comment functionality is what intrigued me immediately.
\nPostmatic currently allows users to subscribe to comments and posts by email; but what sets it apart is that it enables reply by email functionality as well. That’s something that has been high on my list of wants for a WordPress plugin for a long time, and I wanted it without switching to a third party system like Disqus.
\nAll in all — aside from enabling replies by email — the current feature set is quite similar to Jetpack’s Subscriptions module. Postmatic has widgets for post subscriptions and will send subscribers new posts and allow them to get emailed comment notifications as well.
\n\nI asked Jason Lemieux, a co-founder of Postmatic, if they were considering a way to import from Jetpack or otherwise integrate with it, and they are. They’re working now to make it so that your old posts using Jetpack’s subscription module for comment notifications will still work, and your new posts will use Postmatic.
\nI had a pretty thorough conversation with Jason and got to see Postmatic in action. For a free plugin especially, the functionality is quite impressive. I tested subscribing to comments, replying by email, and opting into subscriptions, and it is all very smooth. Here’s a sample reply notification to my email.
\n
Sample Postmatic notification email
Postmatic is already in beta with their API as well. With a little legwork, you can utilize Postmatic for a variety of custom use cases. I know I’d love to play with it to see if I could create email campaigns for custom post types or multiple lists. They also intend to monetize the plugin via a few avenues — including ensuring mail delivery and functionality add-ons.
\nPostmatic — available for download on WordPress.org — is and will remain completely free. At some point they’ll exit beta and they will offer paid delivery of outgoing mail for larger sites. They understand the limitations of sending email through your own server and are using Mailgun to ensure delivery. They also have an extensive — and for now private — list of features they aim to introduce to Postmatic.
\nThe product is definitely version 1.0. Advanced list management, and more advanced campaign delivery is still not ready. But I was impressed by how good of a 1.0 Postmatic is, and how much effort Jason and his business parter, Dylan Kuhn, have clearly invested heavily into the product. For instance, subscriber importing is already possible, so you could move to Postmatic for post delivery right away. They have videos show how to do that and more already available.
\nThey tell me as well that Postmatic is in very early stages. Right now they are working on more advanced template building and other features to help tame your WordPress emails. I think they definitely have other services like Jetpack’s Subscriptions and MailPoet in their sights.
\nI think WordPress email is ripe for disruption. Imagine, currently, all the ways users can get emails from a website, with little continuity: WordPress itself, Mailchimp or other newsletter provider, Jetpack / WordPress.com, eCommerce solutions, form solutions. Each of these sends email and each has their own quirks, look and feel, and otherwise.
\nI’d love to see a service like Postmatic help tame WordPress email as a whole, and offer a more seamless experience for my website visitors that receive email from me.
\nIn the short term, I doubt any service will be able to do this perfectly. But I think as WordPress sites send more and more mail, continuity in this arena will be very important. I know, for me, as I prepare to enable club memberships on Post Status, it’s top of my mind to provide a quality email experience to my members.
";s: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, 06 Jan 2015 23:30: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: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: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:78:"Post Status: LoopConf: A new WordPress conference that’s only for developers";s: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:30:"https://poststatus.com/?p=7188";s: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:74:"https://poststatus.com/loopconf-new-wordpress-conference-thats-developers/";s: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:3300:"\n
Early May 2015 will be the first ever LoopConf, a WordPress conference that’s geared solely toward developers. Ryan Sullivan, the owner of WP Site Care, is hosting the conference that is to be held in Las Vegas.
\nLoopConf describes itself like this:
\n\nLoopConf is the greatest conference ever created for WordPress developers. LoopConf came about as we heard technically-minded folks talk about wanting to get together and dive deep into advanced engineering and development topics. We’ve assembled an amazing group of speakers to get this inaugural event started off on the right foot, and we’re excited to share our excitement and passion for WordPress with all of you in an exciting two-day event. We hope that you join us to celebrate the software we love, enjoy each other’s company, and learn from one another.
There are already six speakers confirmed:
\nThe initial speaker line-up is pretty fantastic. I’d love to learn more from each one of them.
\nLoopConf is not a WordCamp or associated with the WordPress foundation. It’s an independent WordPress conference, and Ryan says it’s the first in-person developer only WordPress conference he knows of. Most WordCamps are very catered to a diverse audience.
\nThis could be a good way for people to have more developer centric conversations. I’m certainly interested to see how it goes, and would like to make it myself. They are seeking sponsors and speaker submissions now. I don’t know how much the tickets will be exactly, but Ryan tells me he hopes for LoopConf to have a prestige and quality similar to An Event Apart events, but for WordPress — so I imagine the tickets won’t be cheap.
\nAs the WordPress conference ecosystem continues to blossom, I’m sure this isn’t the only one we’ll see like this. Non-WordCamp, niche events like PressNomics helped lead the way for those that are happening now, and I think generally it’s been good to have a diverse array of options for people to attend and learn from one another.
\nYou can keep up with @LoopConf on Twitter or via the website.
";s: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, 06 Jan 2015 23:30: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: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: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:70:"Post Status: 5 years into business, Pagely is growing faster than ever";s: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:30:"https://poststatus.com/?p=7174";s: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://poststatus.com/pagely-growth-wordpress-hosting/";s: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:9862:"
Pagely is celebrating their fifth year of business right now. They have just launched their newly designed website (note to early readers: it’s in process of launching at this moment, so some links may not work until later today) to reflect some of the ways they’ve changed over the years. They are also growing, rapidly.
\nThe new website is a complete rebrand. They’ve tweaked their logo many times over the years, but they’ve completely changed it now. It’s much more modern and can be used in a variety of ways.
\nThe new website is flat, geometric, modern, and as sassy as ever (like with their Investors page they are quite proud of). In all, the redesign attempts to showcase happy customers and what makes them different.
\n
They are introducing brand ambassadors — a kind of super testimonial — that includes names you’ll surely recognize from the WordPress community.
\nAdditionally, they are giving other managed hosts a bit of a sting with what they call #turnthepage, a dedicated page to highlight that they don’t charge for pageviews, something that most managed WordPress hosting companies do.
\nPagely has implemented the new branding and design elements across most of their platform, including their Support sub-site.
\n
In addition to branding and a web redesign, Pagely is attempting to showcase that they were first to market with managed WordPress hosting, but also that they are best in class. The strategy — and particularly their recent all-in move to being an AWS-based service — appear to be working.
\nI discussed the Pagely redesign and their recent growth with Joshua Strebel, Pagely co-founder and CEO. He told me that they’ve seen an enormous amount of growth this year.
\nRevenue is up 28% in the last month alone and between 40-45% quarter over quarter. This means that Pagely is on pace to more than double in size between this summer and next.
\nTo some this may seem a surprise, but it’s part of some slow and steady investments Pagely has made in recent years.
\nThey certainly did not scale at the pace of other players in the market — most notably WP Engine. They also (as noted above with the Investors page) have bootstrapped their company from the beginning.
\nNoone knows exactly how big Pagely is today, and that’s part of what you get with their owners. Though I’m told they are “more than 10 people but fewer than 50.”
\n
The Strebel’s (on the left of the picture above) own the company — only sharing equity with some key employees — and they are proud of their independence.
\nIt’s nearly impossible to be a Pagely customer without feeling the presence of Josh and Sally Strebel’s own personalities. And while Josh is an opinionated figure in the WordPress community, Pagely customers seem quite happy with that.
\nSteven Gliebe started a new project recently called HostingReviews.io, a website that attempts to collect non-biased reviews from social media about various hosting solutions. Pagely has a 94% happiness rating according to HostingReviews.io — matched only by Flywheel’s 95% rating.
\nI like Steven’s project because he is not using affiliates at all with this project, an aspect that spoils most hosting review websites. Here’s a breakdown of some others:
\n
\n
It’s been an interesting time to analyze the managed WordPress hosting market. For one, the term “managed WordPress hosting” is here to stay. Nearly every large player — including the likes of GoDaddy, Bluehost, Dreamhost, and more — offer a managed WordPress hosting product.
\nThe differences between these large company products and the original smaller players — players like Pagely, WP Engine, Pressable, and later entrants like Flywheel, Siteground, and Pantheon — are beyond the name of the product. You really have to dig into each service and business model to get a full grasp of how they are unique.
\nAnd this is really hard.
\nFor one, you can find positive and negative things about every host in the world. But also, these companies are often targeting different audiences. For instance, GoDaddy and the other large hosts pretty clearly want the smaller website audience, but to upsell them with a more WordPress-specific package. And that’s fine; they can offer some great functionality for that.
\nBut Pagely, Pantheon, and some others are going after bigger fish; and they are marketing themselves appropriately.
\nWordPress.com VIP is the king of the big-WordPress mountain. They have the promise of infinite scale and excellent reliability. It’s Automattic’s own product and an excellent business model for them.
\nThey are able to charge big companies big dollars (relative to other WordPress hosting, not compared to some enterprise software these companies are used to) to get the assurance that their website is hosted safely and reliably.
\nWordPress.com serves billions of pageviews every month. It’s simply a massive platform and a comfortable place for companies to take their WordPress hosting needs.
\nPagely wants to be an alternative to WordPress.com VIP. They see themselves as a viable and attractive alternative. For one, they’ll tell you that you can run anything on Pagely; whereas WordPress VIP has a restricted ecosystem that involves approved-only plugins and stringent code reviews for any custom code, that often requires one of their VIP service partners to perform the work.
\n\nVIP is a great service. However it is no longer the only service capable of serving clients at scale. We are winning more of those high-caliber clients that need the extra flexibility our stack offers.
\n– Joshua Strebel, Pagely CEO
Pagely and others seeking the high end market are still relatively early on in their efforts; WordPress.com VIP is a behemoth in that market.
\nI’ve noticed — and I’m sure some of you have too — a change in tide of WordPress managed hosting. This year has no doubt been a very tough one for some managed hosts.
\nIt’s been painful to see customers that were once happy with their service — to the point of being huge brand ambassadors themselves — to quietly leaving and moving on to something else, now with warranted skepticism.
\nPersonally, I try to stay pretty host-agnostic. It is a very difficult market to say anything about, due to its incredibly competitive nature. However, I think it’s obvious that Pagely — accompanied by the likes of SiteGround and Pantheon — is on the rise while some of the other early entrants to WordPress managed hosting are struggling to consistently deliver on their promises.
\nHowever, with new-found popularity and fast growth, Pagely too can be susceptible to some of the same growing pains of their competition. But they say they’re ready for it.
\nThey’ve invested heavily in AWS and put all their technology chips in Amazon’s basket. And they assure me that they have been hiring some of the best support techs and engineers in the business. Additionally, they tell me that because they aren’t investing a ton of money into marketing, their customer influx is more natural and less likely to strain more linear growth levels.
\nTime will tell if Pagely is ready to scale with players that have more money and resources than they do, but they’re definitely excited about the recent growth, the new brand and website, their brand ambassadors, and the challenges ahead.
";s: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, 06 Jan 2015 23:30: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: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: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:46:"Post Status: Is WordPress right for eCommerce?";s: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:30:"https://poststatus.com/?p=7165";s: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://poststatus.com/wordpress-right-ecommerce/";s: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:11014:"
I’m going to take a leaf out of Chris Lema’s book right now to answer whether WordPress should be used for eCommerce: It depends.
\nThere are camps of thought that think WordPress isn’t right for eCommerce, and there are people that think it’s the only way to go. Having worked with and used several different eCommerce platforms (both hosted and self-hosted), I’ve definitely developed the mindset that there are use cases for each. WordPress can be the right choice in a lot of circumstances, but not all.
\nIf you’re not sure about the major differences between hosted vs self hosted platforms, I recommend reading Patrick Rauland’s overview of the major differences. WordPress eCommerce usually falls under self-hosted eCommerce (I don’t count WordPress.com since it uses external eCommerce solutions). Forbes also recently wrote about this, though I don’t necessarily agree with their conclusions.
\nThe typical viewpoint is that WordPress plugins like WooCommerce or Easy Digital Downloads are great for small stores or people that just want to quickly and easily sell a few items, while hosted platforms like Shopify and Bigcommerce are for “serious” stores.
\nThis viewpoint is actually pretty backwards, not to mention the fact that the number of items is a poor way of determining which platform you should use.
\nIs WordPress the best platform on which to build apps? I don’t always think so, but it could be. Is it always a good choice for eCommerce? Nope. However, it’s the right one for lots of stores, and it’s the wrong one for lots of stores.
\nThere are a few major strengths and weaknesses of both WordPress and hosted solutions. I’ve worked most with WooCommerce, Easy Digital Downloads, and Shopify, but have tried lots of other eCommerce solutions for comparison. Some of the knocks against WordPress aren’t valid, but we should note that some are.
\nEveryone loves to talk about how easy certain WordPress plugins are to use. When you compare WordPress plugins to something like Shopify, this just isn’t true. They may be easy to use for people that are familiar with WordPress, but not for the average user who wants to start selling online with no experience.
\nWordPress requires a domain name purchase, hosting setup, installation, plugin installation and setup, theme installation and setup, blah blah blah, you get the drift. With hosted solutions, you don’t worry about this (though solutions like Evermore — which was covered by Post Status when it launched — make this interesting). You pay your monthly bill, and you’re handed a store website – you just pick the name and get rolling. You can start adding products right away, and then you might get into changing your theme or other setup.
\n\nSome of the site tweaks or setup with hosted solutions aren’t easy, but the learning curve for a solution like Shopify is far gentler than the learning curve for something like WooCommerce.
\nThere are also WP Cron issues for some sites, as it’s not a perfect system for scheduling actions, like recurring payments. It can work pretty well, but other platforms can make this far easier to implement and more reliable than Cron.
\nWordPress store owners are also responsible for their own hosting, software updates, and security. For many site owners, these are huge responsibilities. Hosted solutions roll all of this into their package so that users don’t have to know how their website is powered. They just have to use it.
\nBoth WordPress and hosted solutions will scale, but there are considerations with WordPress that users need to be aware of. Database issues (like backups or memory with massive amounts of customers and orders) should be addressed, hosting has to be optimized, and plugins need to scale with the site. With a hosted solution, none of this is your problem as a user.
\nBearing these weaknesses in mind, it’s a bit crazy to me that WordPress is sometimes referred to as the “easy solution” or the right tool for “small stores”. It’s not. In many cases, it’s like bringing a tank to the eCommerce playground.
\nSo what does WordPress do well?
\nFirst, WordPress offers the most all-in-one website solution available. WordPress can offer the eCommerce aspects of the website, in addition to its many other CMS features. The ability to create a single, seamless CMS experience for a multi-purpose website makes it quite compelling and more budget-friendly than more “eCommerce first” platforms.
\nSecond, it’s optimized for SEO. Your content is crucial here, and WordPress is built for content. More importantly, if you’ve tried to blog on another platform, you know how painful it can be (don’t start with me Squarespace fans, that thing is difficult to use). WordPress doesn’t encourage you to avoid blogging to avoid headache: it’s built for complete websites, and is not simply focused on eCommerce.
\nWordPress also contains functionality that you can’t always get with different platforms. There’s a massive selection of plugins, themes, and all sorts of solutions for WordPress that are readily available. Since it’s open source, it’s far easier to find ways to customize it when compared to closed platforms like Bigcommerce.
\nSpeaking of customizations, your ability to customize WordPress or plugins is far easier than with hosted solutions. There’s lots of functionality that can be achieved with WordPress that’s not even possible in hosted solutions. For example, developers have no control over the Shopify checkout process, but this can be entirely customized with WordPress.
\nYou can also usually find a plugin that will provide a “starting point” for a customization project. Even if you find a Shopify or Bigcommerce app that gets close to what you need, but not quite, you’ll need to create a completely custom solution anyway – there’s no “extending” there.
\nAlong with customization is the control over your environment. You can spin up your eCommerce site on something like Digital Ocean, and you’ve got control over the entire site, from server to theme.
\nThe biggest difference for me between hosted solutions and self-hosted actually isn’t usability or scalability – it’s product type. Can almost every eCommerce platform sell tee shirts? Yes. Even EDD can do that, and it’s made for digital products.
\nHowever, selling complex products becomes infinitely more difficult on hosted platforms, as you’re restricted to what the API offers for product changes, which isn’t always a lot. For example, if you’ve ever tried to add pricing changes for customization options in Shopify, you know that it literally takes some wizardry, black magic, and possibly bubble gum used as tape to do so.
\nWordPress plugins make this far easier, because the entire platform is open, not just an API. Most eCommerce plugins have more than enough actions or filters to change products, product pages, checkout forms, or any other part of your site.
\nHosted eCommerce solutions are typically easy to use, and can provide some customization options via apps or other add-on services. However, it’s like renting a house versus owning. With a rented house, you can’t go knocking down walls or completely remodeling – you’ve got to work inside of a framework you’re given. This is exactly how a hosted solution works.
\nThe benefit to this is that you absolve yourself of a lot of responsibility and worry. The entire experience is managed and supported, and is typically very easy to work with.
\nHowever, WordPress eCommerce is like buying the house. You can do whatever you want – add-on, rebuild sections of the house, change layouts around, add tunnels to other houses, you name it. However, when the water heater blows up, it’s your responsibility.
\nWordPress also affords the opportunity to sell complex products, such as measurement based products like corks by the pound, that simply can’t be sold on other platforms. The same ability to customize WordPress so thoroughly lets you customize the eCommerce plugin you’re using.
\nYou gain the flexibility that comes with the platform, as well as the benefits like tons of plugins, themes, a great content structure, and a consistently maintained and updated core solution. However, the Frankenstein site that you build is your baby, and yours alone – you need to host it, maintain it, and care for it.
\nWordPress lets you create advanced functionality via plugins and customizations, but isn’t right for users looking for an easy, basic shop setup. If you want a move-in ready house or a beautiful rental, you should look at hosted solutions. If you’re willing to make your dream house from great bones and foundation, or you need to sell fairly complex products, then WordPress might be it for you. It’s not the “easy” solution, but it can be a great one.
";s: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, 06 Jan 2015 23:30: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:9:"Beka Rice";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:36:"Post Status: Contribution as culture";s: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:30:"https://poststatus.com/?p=7153";s: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/contribution-culture/";s: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:12488:"
This post spends a lot of time analyzing and referencing two other blog posts. Excuse me for that, but also be sure to read both, as they are relevant for this post and also interesting in their own right.
\nMatt Mullenweg wrote a blog post called Five for the Future yesterday that advocates his belief that WordPress-centric companies should aim to utilize 5% of their company resources toward contributing back to the project.
\nHe noted in the post that Automattic isn’t quite to this point, but that they are working on it, and describes why he believes it’s important. He closes with this:
\n\nIt’s a big commitment, but I can’t think of a better long-term investment in the health of WordPress overall. I think it will look incredibly modest in hindsight. This ratio is probably the bare minimum for a sustainable ecosystem, avoiding the tragedy of the commons. I think the 5% rule is one that all open source projects and companies should follow, at least if they want to be vibrant a decade from now.
This was followed up by one of the co-founders of one of the very hosting companies Matt partially referenced in his post — WP Engine’s Ben Metcalfe — who responded with a blog post of his own: WordPress: What exactly do they get for their 5%?
\nI think I was immediately thrown off by Ben’s post title, but so many times throughout reading it I was shocked at how he made assumptions of Matt’s intentions or missed what I would call “the point”.
\nObviously, Matt is not speaking from the mountaintop with a proclamation of law. This is his recommendation — one that he believes will reward the firms that strive for it.
\nI believe that the community has already shown us that those that invest into WordPress are rewarded from it. We improve our understanding of a foundational software of our careers, improve our skills, are more marketable, more attractive to employers, and create natural opportunities for developing industry relationships.
\nHow should 5% of “people” be defined? I’m pretty sure Matt would agree that 5% of people or 5% of revenue toward people doesn’t really matter to him; yet Ben makes a continuous sticking point about the cost of — and need for — engineers.
\nAdditionally, while Matt utilizes full-time employees, the same (or better) effect could be had with shared time from more employees.
\nI’m not big into absolutes, so it’s important to remember that while I’m advocating that Matt’s recommendation of 5% time, I think it’s simply a good recommendation. This is a free economy and companies can do what they want. But I think in the current and long term, contribution will be key to greater corporate success for those that choose to do so.
\n\n
\nWhile Matt was careful to include numerous non-engineering roles companies could help with, ultimately what drives the open source project is source code contribution by software engineers. …
\nA reasonable engineer in the US costs $100k/y, and if you factor in benefits (tax funded health-care, anyone?) and overheads you could easily be looking at $130k or more per person, per year. …
\nA 200+ person web hosting company would need to hire 10 engineers to meet a 5% goal, requiring a budget of anything between $1MM-1.3MM+ per year. Those engineers probably need a manager – to mentor them, provide career development etc. Those 11 people also put pressure on human resources, finance, legal, facilities etc – probably equating to another person again. Now we’re talking probably more like $1.25-$1.5m annually.
First, I believe Ben has spent too much time in the world’s largest cities if he believes engineers cost $100,000 per year on average. In my experience (yes, I interview people myself), that’s not the case, and based on my decent view of the ecosystem it’s not an appropriate going rate — especially if the offer on the table is a particularly desirable position.
\nMore importantly, the project needs far more non-technical contributors. Ben’s assertion that “ultimately” software engineers drive the project is not true. Users drive the project. A technically savvy user-minded contributor can be a beacon of light to a group of software developers. And given the user-facing nature of WordPress itself, non-engineer contributors could drastically improve the less code-sexy parts of the WordPress ecosystem: project management, docs, training, testing, support, translation, etc.
\nAdditional to “core” contributions, WordCamps, plugins, themes, communities, and many other venues are outstanding places where contributors — yes, they’re still contributors! — can impact the overall project.
\nFinally, as I noted above, I think companies could quite effectively contribute parts of employees’ time versus dedicated 100% time, which would also prevent the need to have dedicated managers for open source contributors.
\nBen spends a chunk of time saying that big companies like GoDaddy get a “get out of jail free card” and that obviously Matt wouldn’t expect they dedicate 5% of their thousands of employees.
\nGoDaddy definitely benefits from WordPress and they also contribute to it; and no, they don’t contribute 5% I’m sure. But WordPress is not foundational to GoDaddy’s business. They have a dedicated sub-product for it, and they also have many contributors to it.
\nWP Engine, and many others (including mine), are almost completely or completely reliant on WordPress as a platform. WordPress and its underlying technologies are foundational to our careers and businesses.
\nIt is simply a different story to compare a company that would continue on pretty much fine without WordPress and one that would have to seriously reconsider their entire business model.
\nFor example, let’s compare the scenario to a publisher. Re/code is built on WordPress. They have a staff of 20+. Do they completely rely on WordPress for their website? Yes. For their business model? No. In their scenario, it makes sense for them — and could benefit them pretty directly — to allocate some time of some employees to WordPress, but if WordPress disappears they can and will migrate to a different platform.
\nIt was questioned to me on Twitter, after my initial reaction to Ben’s post, whether I contribute 5% of my time to open source projects like PHP, MySQL, and other tools that WordPress relies on.
\nThis is a good question and point, but it does not cause me to stumble in my opinions. I believe open source contributions in general benefit the entire software stack.
\nIn my scenario, I can be more impactful on the WordPress project than others. But I believe contributions can take many shapes, in both directions.
\nSome folks, like Daniel Bachhuber, greatly contribute to the project as a whole by supporting upstream projects like WP CLI.
\nAutomattic is a fantastic example of a company that has both upstream and downstream contributions. They are active contributors to, employers of contributors or founders, or monetary sponsors to a huge number of downstream projects: WordPress, PHP, Nginx, jQuery, Elastic Search, Node, Socket.io, and probably a bunch I can’t think of or don’t know about. Additionally, they are a driving force behind dozens of upstream, open source themes and plugins.
\nEdit: Matt says in a Tweet where Andrey Savchenko asked for clarification about PHP contributions that Automattic doesn’t actively contribute to PHP. Though I think I define contribution a bit more loosely than Matt does.
\nWhether a company is contributing to their foundational piece of software, a downstream or upstream application, or on an adjacent aspect that leads to the betterment of the platform that is foundational to their business objectives, then I believe it will in turn be beneficial to their bottom line.
\nContribution should not be considered an isolated cost, but an enabling investment.
\nIf I run a business that relies on a foundational piece of software like WordPress, then it benefits me greatly for my employees — no matter what role they play within the company — to be intimately familiar with that software.
\nIn my last job, I was tasked with guiding a transition of my company from developing mostly on a proprietary CMS to WordPress. I consistently preached the importance for everyone in the company to understand some fundamentals of WordPress itself. During my time there and since I’ve moved on, I’ve seen other members of that company learn the software, get involved in our local community, and even contribute back to WordPress itself; and both they and the company are better off for it.
\nWhether an employee is in sales, customer service, design, development, management, or wherever else — every employee knowing your product is important. I firmly believe this. I would want anyone in an organization I’m part of to be able to discuss our product in detail and with confidence to anyone.
\nWhen your company relies on a foundational piece of software — such as those we’re discussing in this post — that’s in effect part of your product. We are building products and services around and for WordPress. How important should it be that our company’s employees understand it?
\nAnd how can they understand it better? By contributing of course!
\nHave a new support rep? Show them the WordPress.org forums to get their feet wet. New designer or front-end developer? Have them sit in on default theme conversations or read through the Make UI blog. New sales person? Get them involved at your local meetup and WordCamp. This list can go on.
\nAvenues for contribution are an incredible gateway for learning WordPress. Blogging about WordPress (another avenue of contribution) has greatly enabled me to be better at my job, and therefore made me significantly more valuable to the companies I’ve worked with.
\nMatt called his post Five for the Future, and talked specifically about how a 5% investment by a company will ensure a greater future for WordPress and therefore said company. I disagree.
\nContributing now will benefit the company and its employees right now. And while both Matt and Ben focused on individuals within the company being targeted contributors, I think it’s much more beneficial to have a much larger percentage of a company contributing a portion of their time (even if small). I’d rather see 2 of 200 employees be full time contributors and then have 80 10% contributors than have 10 full time contributors.
\nI think we’ve seen many, many examples of contributors (people and companies) reaping tangible and intangible benefits from when they contribute — whether that contribution is to the codebase or the community. Contributors in this ecosystem come out on top.
\nContributions are not an isolated cost or burden. Nor should their effects be limited to good faith investments to the sustainability of the ecosystem.
\nContributions benefit the bottom line, and they benefit the bottom line right now.
";s: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, 06 Jan 2015 23:30: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: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: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:84:"Post Status: The anatomy of a security breach, and how to do good in a bad situation";s: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:30:"https://poststatus.com/?p=7134";s: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://poststatus.com/ithemes-security-breach-and-disclosure/";s: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:12133:"
On Tuesday, iThemes posted an announcement that they had suffered from a security breach of their website and servers. The attackers had reached the servers which stored customer information, including email addresses, IP addresses, full names, and yes, passwords.
\niThemes was quick to notify customers via their blog, social media, and their full customer email list about the breach. Approximately 60,000 users were affected. They warned that passwords were vulnerable. In the second update, posted today, they gave more information about passwords, in response to many questions from users.
\nIt turns out that passwords were stored in plaintext on iThemes’ server. That is, obviously, very bad practice.
\n\n\nWhy Would You Store Passwords in Plain Text?
\nThis is how the membership software we started using in 2009 did it. There are a number of factors for this, none that will make much of a difference at this point or make anyone feel any better about it, myself included.
\nKnow that it’s not because we did not value your data. As an organization, we have been working on a very large migration process that has required us to interlink legacy systems with the latest technologies. Anyone that has ever gone through that process understands the complexities and challenges.
\nFrankly put, it’s been something we identified as a potential risk and are working rapidly now to rectify this issue as fast as humanly possible.
It’s also worth noting that their customer database and iThemes.com users were affected, but customers that use their Sync product to manage their own websites were not. So if you use iThemes Sync, and utilized your site passwords to connect, those accounts and passwords were not part of this breach.
\nThe membership platform that Cory highlights in the update is aMember, a membership management system that’s been around for many years. aMember only introduced encrypted passwords in version 4, which was released in November of 2011.
\nI discussed aMember and plaintext passwords with some other folks that have a significant history with the membership platform, and there are some significant problems that anyone using aMember have experienced.
\nFirst, most folks heavily using aMember aren’t using it out of the box. At the time, most membership sites were doing significant customizations to aMember to achieve desired functionality. So when the v.4 update came out, it was a very difficult update procedure for people to take advantage of the features.
\niThemes would even tell you that their current version of membership software doesn’t look much like aMember at all.
\niThemes is also not the first to be hacked and their aMember passwords leaked. Tuts+ Premium had the same issue in 2012.
\nI discussed aMember at length with Pippin Williamson. He has done a lot of work on his brother’s membership site, CGCookie, which also used aMember until 2012, when he did a huge migration of tens of thousands of members to a new platform.
\nAt the time, Pippin notes that aMember did not disclose passwords were stored in plaintext, so CGCookie had no idea that their users were vulnerable until they learned of the Tuts+ hack, wherein they put a planned migration “into hyperdrive.”
\nThe problem with iThemes’ situation is that they knew of the plaintext passwords and didn’t address the obvious security vulnerability.
\nAll in all, the migration for CGCookie took months to perfect and significant juggling of priorities by their team.
\nSpeaking with Pippin, migrating from aMember was not an easy task. Paypal’s IPN handlers (a payment notification system) were tightly linked to aMember and preventing customer accounts from being disconnected from the membership site took weeks of engineering. Additionally, simply upgrading to the newer versions was also terrible.
\nMany other WordPress companies have used aMember in the past as well, storing plaintext passwords just like iThemes today.
\nSo, aMember has definitely been a problem before now, but iThemes has absolutely slacked in their prioritization of the issue. Simply put, it’s inexcusable to put users into long term risk if you know their passwords are stored in plaintext.
\nThat said, we should consider the potential consequences — though it doesn’t make it excusable. Because iThemes doesn’t store credit card details, emails and names and passwords are about the worst things at risk. Still, a tiny percentage of the general population uses responsible passwords, so getting a list of names and emails and passwords is a treasure trove of information for third party (as in other websites like banks and email providers) to steal identities and break directly into user accounts.
\nThis should also be a significant lesson for any user to always use different passwords for every website where you keep an account. Tools like LastPass and 1Password make account password management easy. Additionally, learn about 2-factor authentication and use it whenever the service enables it.
\nThis is clearly a horrible situation for iThemes to be in. Users have a right to be mad. In 2014 we should be able to expect that our passwords are encrypted, and that even if a server where our information is stored is hacked, that certain valuable details like credit cards or passwords are not exposed. Thankfully, iThemes doesn’t store credit card details, but those passwords should now be assumed stolen, and users have to pay that price.
\nBut where I have enormous respect for iThemes is how they have owned it. Especially in the update post, Cory Miller — iThemes’ founder and CEO — took ownership of the issue and told the full story of the breach.
\n\nI realize this will generate a lot of concern. Again, I am deeply sorry for this mistake and how it has affected you.
\nLet me say: we have made mistakes in the past at iThemes … and as humans will make mistakes in the future. To make a promise otherwise would be absurd and misleading.
\nBut my promise to you, our customers, is this … and it’s the same promise that I’ve held to since January 2008 when I started iThemes in my home:
\n\n
\n- We will identify mistakes as best we can. You have helped us with this and appreciate that accountability.
\n- We will own up to our mistakes. Again, we’ve done this in the past, we did this yesterday and this post is another example of us living this value.
\n- We will fix the mistake as fast as humanly possible. A number of priority issues have been unearthed, shone a hard light on, but we are working to resolve them.
\n- We will learn and grow from it and be better for it and for you.
\nAdditionally, as the founder and CEO, the leader of this company, I want you to know: the buck stops with me and me alone.
\nAt the end of the day, I am responsible for our company, iThemes, and the work we do. I’ve often tried to defer credit for the great work we’ve done to our team, but as for the mistakes we make, that credit belongs solely to me.
Not every company that’s been breached can say the same. Even huge organizations (I’m thinking of Home Depot as the latest) have done a horrible job at responsible and honest disclosure to their customers.
\niThemes could have made this much more quiet and kept it from being a priority to their users or a big deal in WordPress news-land. But they didn’t. They owned it, they apologized, and they’ve been rewarded for that.
\nIn the comments of the security update post, users were appalled by the lack of responsibility on the security priorities, but the honesty paid off in the sense that users were verbally thankful for it so that they could accept the problem and deal with it, when the alternative was to be in the dark.
\nWhile this breach has cost iThemes some credibility, and some trust, I believe those things are recoverable. Had they obfuscated the hack itself, my post and users reactions (had they found out) would be very different.
\niThemes has learned a hard lesson this week, as many other companies have before them. Now they must react, and react strongly. In a situation like this, nothing should take priority over getting this issue fixed.
\nUntil they get their password storage issue fixed, they still are storing passwords in plaintext, even the new ones. Thankfully they’ve already updated password restrictions — which previously limited passwords to 20 characters — to now accept up to 255 characters. But storing them in plaintext means that they are still as vulnerable today as they were last week if someone gets into the server again. So they must be absolutely vigilant to protect their servers through this migration.
\nSecurity is not a sexy industry. Too often we don’t consider it until it’s a problem. “Going on offense” should be our default when we consider security actions, but more often — even with some of the best companies and people in the tech space — we react to issues and aren’t appropriately proactive.
\nThat said, our job is not done either. All of us should consider our own security situation and how we can improve it. Especially if you have users of your own (and many of my readers do), consider that state of your own security, and make sure it’s a priority in your business.
\nWhen we think about what pays the bills, it’s not security awareness and proactive security investments. But we should consider security breaches and vulnerabilities as risks that must be managed; meaning investment into security priorities should be a significant part of any business.
\niThemes, Envato, and WooThemes are all “big” businesses from a WordPress business perspective. Each of them has fought a website security battle. Envato and WooThemes before iThemes have recovered and maintained their users and the community’s trust. I think iThemes will too. But before you, or me, decide “it won’t happen to us”, consider that it can happen to anyone, and our investments into security measures and best practices are not only worthwhile, but the only responsible thing to do.
\nAnd for users, use different passwords on every site. Use LastPass or 1Password. Enable 2-factor authentication. Be vigilant. Do not use the excuse that it’s too hard or a burden. What’s much more of a burden is dealing with a hacked email or bank account. Protect yourself and learn how to protect your accounts. It’s easy to adjust to and modern tools make it a much simpler task to manage.
\nLet’s all — web professionals and users — learn with iThemes here, and do better.
";s: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, 06 Jan 2015 23:30: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: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: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:98:"WPTavern: WordPress StackExchange Thrives in 2014 with 17 Million Page Views and 14K New Questions";s: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:"http://wptavern.com/?p=36695";s: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:"http://wptavern.com/wordpress-stackexchange-thrives-in-2014-with-17-million-page-views-and-14k-new-questions";s: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:10679:"
Last week, moderators from the WordPress Development StackExchange (WPSE) posted a short summary of stats from 2014, which demonstrate the remarkable growth and success of the community surrounding the site. This past year WPSE pulled in approximately 15,000 new users, bringing the total to 45,000.
\nThe site received a total of 17 million page views during 2014. Users submitted 14,000 new questions, and the site received 13,000 new answers.
\nThe question and answer model employed at the WordPress StackExchange may not be a perfect forumula, but it works. If you’re a developer looking for help, you’re far more likely to receive high quality answers on WPSE than on the official WordPress.org forums. On average, the two forums cater to different types of users.
\nThe StackExchange question and answer communities are expert communities by design. Right answers float to the top, based on votes from experts in the community, making it an efficient way to locate the most helpful answers.
\nIn more traditional forums, you’ll spend quite a bit of time weeding through useless, poor quality information to find what you’re looking for. Those who share their knowledge on StackExchange communities earn reputation points, which also helps users discern the quality of answers provided. Overall, it’s a tidy formula for engaging and rewarding expert advice.
\n
Each new StackExchange community passes through a beta period where it is required to demonstrate sustained activity around the topic. I spoke with Andrey Savchenko, better known online as @Rarst, a moderator who has witnessed the evolution of WPSE from its early beta days to today. Browsing through questions on the site, there seem to be very few beginner inquiries, as compared to WordPress.org support. I asked Savchenko if the site purposely attracts a different crowd or if the questions are heavily moderated.
“At 45,000+ registered users it would be hard for me to paint an average user in few strokes,” he said. “Out of more obvious quirks I would say is that WPSE seems more heavily European than WordPress’ usual.
\n“It’s also a clearly for–developer resource in a primarily user–centric WordPress world, which doesn’t mean beginner development questions are unwelcome — they often make some of the best ones. But beginner user questions aren’t something we historically selected for.”
\nWhile moderation is one of the key features in place in every StackExchange network, Rarst believes it’s not as heavy as one might imagine. “I think SE moderation is efficient rather than heavy. It is strict when it needs to be and intelligently flexible when not,” he said.
\nWhy do many WordPress users prefer getting help at WPSE as opposed to WordPress.org? Apart from the general difference in the user base, the WPSE community has a different mission and approach to answering questions.
\n“WPSE is a unique case of a high profile WordPress site outside of the WordPress ethos. In a way, we are the other side of the coin — a corner for people who don’t click with mainline WordPress resources too well,” Rarst explained.
\n“For StackExchange, the cultivation of knowledge is the primary mission, as the WordPress.org documentation and forums often feel like a neglected afterthought.” WPSE offers an alternative way to explore WordPress development questions, outside of the culture that exists on WordPress.org.
\nWPSE manages to maintain a cohesive community without instituting an overly strict governing body. All WPSE moderators are organically grown within the community. “People tend to choose their own level of social involvement; the system isn’t really opinionated about it,” Rarst said. “There are some chatty types, who are around on our meta site and in ‘The Loop’ chat room a lot. There are also plenty of high ranked people who keep to themselves and stay a complete mystery, apart from avatar and nickname.”
\nWhen it comes to housekeeping, WPSE has a natural structure, which lends moderation capabilities to members with the most influence and participation. “The moderators tend to have a lot of pull in organizational issues, but they tend to be elected moderators because they already have that influence,” Rarst explained. “Position comes to those who have established themselves, not the other way around.”
\nThe overarching StackExchange mission has been key to the community’s success. The purpose of the 133 StackExchange communities is to enable users to ask questions and get answers without distraction. Unlike a traditional discussion forum, replies are heavily geared towards answers without a lot of chit-chat. “I think the focus with which Stack Exchange pursues their goals and their dedication to empowering people to contribute is what captures users on any topic,” Rarst said.
\nUsers are encouraged to follow a simple set of guidelines when asking questions. They are encouraged to keep questions tightly focused on the topic at hand and to avoid opinion-based questions that would generate a lengthy discussion.
\n
In the early days, the site was more exploratory, and moderators were open to trying new things to see where it went. “These days we are more reserved — we learned what works well for us, what is our main identity,” Rarst said. “We had finally pushed through name change to ‘WordPress Development’ from ‘WordPress Answers’, which had temporarily and accidentally stuck.”
\nThey also learned what kind of content to turn away in order to keep the site working well. “The most prominent example is probably a much more stronger enforcement of questions specific to plugins and themes being out of scope for our general WordPress development focus,” Rarst said. This helps to keep the site more focused on how WordPress itself works, as opposed to getting overrun with support questions regarding third-party extensions.
\nOver the years, moderators and participants have actively sought to elicit feedback in order to improve the experience at WPSE, on both the meta site and on Reddit. Discussion from these exchanges has helped shape the direction of the site to filter out questions that detract from the main mission.
\nWPSE stats show that the most voted new question in 2014 was, “What is your best practice to execute one-time scripts?” The most viewed new question was “Allow HTML in Excerpt” with 8,300+ views.
\nWith a predominantly developer-oriented community, Rarst believes that the WPSE model is working because it attracts competent WordPress experts to participate. Like-minded users and moderators have cultivated a fertile soil for answers. “I consider answering questions an immense personal learning opportunity, but also I think as a resource it is important for WordPress knowledge infrastructure, which is starved for quality information,” Rarst said.
\nThe points-based reputation system also helps in motivating users to submit answers, although Rarst doesn’t attribute it to having played a large role in the site’s success. “I wouldn’t try to guess if points made Stack Exchange popular or was it other way around,” he said. “They definitely add a playful component to the experience, but the additional nature of ‘play’ is the key here — hardly anyone would participate for points alone in my opinion.”
\n
The success is more likely attributed to the combination of dedicated and proven moderators, a focused mission, and a foundational question-and-answer format that simply works. Spend a few minutes sifting through questions on the site and you’ll undoubtedly have the opportunity to explore the inner workings of WordPress with knowledgeable, experienced respondents on hand.
\nThe growth of the site over the past year shows that WPSE is quickly becoming a popular, high quality resource for finding answers to WordPress-related questions. If you’re stuck, and you’ve already done your homework of googling and browsing other forums, WPSE is a solid option for getting real answers without all the extra fluff.
";s: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, 06 Jan 2015 22:00: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:13:"Sarah Gooding";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:19:"Matt: Rise of Bacon";s: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:21:"http://ma.tt/?p=44575";s: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:35:"http://ma.tt/2015/01/rise-of-bacon/";s: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:217:"This article on the amazing rise of bacon was one of my favorite articles I read last year. About bacon.
";s: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, 06 Jan 2015 13:34:59 +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:76:"WPTavern: Control the Visibility of WordPress Widgets Based on Time and Date";s: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:"http://wptavern.com/?p=35102";s: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:86:"http://wptavern.com/control-the-visibility-of-wordpress-widgets-based-on-time-and-date";s: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:3203:"
photo credit: Βethan – cc\nThe traditional use of widgets in WordPress is to set it and forget it. After placing and configuring a widget, it stays in the widgetized area until manually removed. Many plugins have extended widgets to add visibility settings that are based on the page or post where the widget appears. But what if you could also control widgets based on time and date?
\nThe new Widget Visibility Time Scheduler plugin actually allows you to schedule the display of widgets down to the minute. The plugin, created by WordPress developer Martin Stehle, adds time-based visibility settings to each widget’s configuration options.
\n
Widget Visibility Time Scheduler was designed to work seamlessly with Jetpack’s Widget Visibility module, which allows you to limit widget display to certain pages. There is no conflict if your site is Jetpack-enabled and you can even use the two visibility options in combination with one another.
\nThe plugin is perfect for seasonal widgets, temporary sales/promotions, events, live chat buttons, and any other time/date-dependent content. One feature that might be useful to add is an indefinite option for the end time of the widget display. That would enable users to schedule future widgets and leave them in place indefinitely. Additionally, an option to set the widget display based on the day of the week could offer more flexibility.
\nAfter testing the plugin, I can confirm that it works as advertised. If you try the plugin and you want to remove it at a later point in time, you’ll need to uncheck the widget visibility time scheduler box in each widget before you remove that plugin. This will ensure that none of its data remains in the database after you remove the plugin.
\nWidget Visibility Time Scheduler is a handy addition to any site using WordPress as a CMS, an e-commerce platform, or even a blog. In combination with the Jetpack module, it offers full control over when and where your widgets are displayed. This is one you may want to favorite for the next time you need to use it. The plugin is available for download from 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 05 Jan 2015 22:13:49 +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:"Sarah Gooding";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:65:"WPTavern: Emil Uzelac Launches New WordPress Theme Review Service";s: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:"http://wptavern.com/?p=36615";s: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:75:"http://wptavern.com/emil-uzelac-launches-new-wordpress-theme-review-service";s: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:4358:"
Emil Uzelac’s new WordPress Theme Review service is the first of its kind. As a four-year veteran of the WordPress.org Theme Review Team, he is uniquely qualified to operate a service that focuses on theme standards and quality control.
Uzelac plans to assist developers with theme reviews for client projects, commercial themes, and free themes submitted to WordPress.org. The reviews are aimed not only at helping developers meet the latest WordPress theme guidelines but also at catching bugs before the product gains distribution. The service will also aim to give customers detailed feedback on performance and security.
\nA preliminary review starts at $90 for the first hour. “You would be surprised how much one can find within an hour,” Uzelac told the Tavern.
\n“The service will cover things like efficiency, performance, sanity, and the overall code quality,” he said. “It will also include UX improvements for both desktop and mobile devices. My goal is also to educate as well,” he said. Customers who use the service will receive suggestions for improvement, along with examples and support from Uzelac.
\n“Look, no one wants to ship a theme with issues,” Uzelac said. “Everyone knows time constraints and the pressure to finish can introduce mistakes even the most seasoned developers miss. That’s completely normal. But frustrated end users quickly abandon themes they don’t understand or can’t fix.” As the original author of Responsive, one of most popular themes of all time on WordPress.org, Uzelac knows the kind of quality and support required to build a strong user base.
\nIn the past, getting a theme through the rigorous review process for WordPress.org could take weeks. If you have errors that need to be fixed, your theme goes back into the queue to be reviewed again. Being able to make it through the first time with no issues is advantageous to developers who are hoping to release their themes to the public as soon as possible.
\nMario Peshev recently touched on this topic when we interviewed him regarding his partnership with Uzelac to launch a theme for his company. “There is no clear way to hire any of them for theme reviews or building a theme following the WordPress.org guidelines,” Peshev said, commenting on the lack of visibility of the WordPress Theme Review Team. “I assume that small and medium agencies would be willing to pay for professional reviews or getting themes built for any reason, which would support both parties,” he said.
\nWordPress users are losing confidence in large commercial theme marketplaces that continue to sell products riddled with bad practices and security vulnerabilities. The community has a need for a service that can authoritatively address problems with WordPress themes and educate developers on best practices.
\nDespite launching his theme review service, Uzelac plans to continue volunteering on the WordPress.org Theme Review Team for many years to come. “This is something I enjoy doing, even more than creating themes,” he said. If the service takes off, he plans to do it full-time and hopes to take on additional reviewers to grow the business.
";s: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 Jan 2015 18:34: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:13:"Sarah Gooding";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:30:"Matt: What’s in My Bag, 2014";s: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:21:"http://ma.tt/?p=44570";s: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:"http://ma.tt/2015/01/whats-in-my-bag-2014/";s: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:6355:"As the start of a new year’s tradition, I’d like to take inventory of what I carry around in my backpack, which I have with me almost everywhere I go. I’m constantly iterating and changing what I carry around, so I hope it’s interesting to see this vignette of what I’ve found to be the best or most effective items to have with me all the time. With the things in this backpack I can be productive pretty much any place on the planet with a wifi or LTE connection.
\n
So if you add it all up, there are about 53 unique items I’m carrying around all the time. I’m curious how this total number changes over time as well. If you have any recommendations for a better, lighter, or more functional item than what I’m carrying please leave it in the 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:"Mon, 05 Jan 2015 17:07: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: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: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:65:"WPTavern: Kim Parsell, Affectionately Known as #wpmom 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:28:"http://wptavern.com/?p=36618";s: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:"http://wptavern.com/kim-parsell-affectionately-known-as-wpmom-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:9532:"
WordCamp San Francisco 2014 By Sheri Bigelow\nIn the eight years I’ve covered the WordPress scene, only once have I written about someone passing away. It’s with a heavy heart and great sadness to inform you that Kim Parsell passed away last week at her home in Southern, Ohio. The cause of death is unknown and a small service is tentatively scheduled for this Saturday. There’s also a memorial type of event being planned for WordCamp Columbus, OH.
\nBefore getting actively involved in the WordPress project, she was an avid photographer. Almost all of the photos she published were taken on her property in Southern, Ohio. She had an eye for nature’s beauty and showed the world through photography how beautiful Ohio is. Her photos are so good that I think she could have made a living selling them as prints.
\n
Springtime Sky by Kim Parsell\n
Kim Parsell’s WordPress.org Profile\nIn the past few years, Kim has worked on improving documentation in WordPress as a member of the docs team. She substantially contributed to the effort of adding inline documentation to every hook in WordPress. Her contributions got her mentioned by Matt Mullenweg (11:00 minute mark) during his State of the Word presentation at WordCamp San Francisco 2014. She’s contributed to every release of WordPress from 3.7 to 4.1.
\nBeing mentioned in the State of the Word is one of Kim’s best moments and it meant a lot to her. Sarah Pressler accurately describes the jubilation felt by Kim, “Can you believe it? Me!!! In Matt’s talk! Me!? I…just …. I can’t believe it. Little ol’ me. An old lady up there on the screen with all the kids. It’s official, I really am #WPMom now.”
\n
Kim Parsell With the Docs Team Meetup in Cincinnati 2013\nKim became known throughout the WordPress community as #wpmom, a title she fully embraced. She had a way of giving people purpose, taking them under her wing, and showing compassion when it was needed most. As Carrie Dils explains, “Folks jokingly call her #wpmom, but there’s a lot of truth there. She was very much like a mother figure, but never EVER in a condescending way.”
\nIn a comment on the same post, Amanda describes exactly the type of person Kim was, “The greatest thing about Kim is that whether you’re standing at the back of the line or the front she would have walked her way down that line to let everyone know they were equally as important and that the only reason there’s a line is because everyone can’t be in the same place at once.”
\nAs Jayvie Canono found out, Kim didn’t put up with bull crap from anyone and had no problem letting you know about it. It’s how she told people which made her unique, “She brought people together and had the salty, country-gal personality who would not put up with your bull crap and yet would never break one rule of etiquette in the process of letting you know.”
\n
Sunset as Seen From Kim Parsell’s Property\nKim referred to herself as “The little ol’ crazy lady at the top of a hill in Ohio.” She wasn’t crazy but rather, an independent, strong-willed woman who at times was stubborn. A hard worker, she spent a lot of time in rural Ohio alone, “Chillin’ on a dirt road.” She routinely drove an hour and a half north to attend our WordPress meetup because there wasn’t a person within 30 miles of her house who knows what WordPress is.
\nWhen I started WordPress Weekly in 2009, she would often join me on each episode to provide the countdown before I hit the record button. She was occasionally a guest on the show as on episode 87. After the show, she would stick around for a half hour to an hour to talk about whatever was on her mind. In many ways, the show offered her an opportunity to connect and speak to WordPress people every week. The show was the closest thing to a meetup she could regularly attend.
\nhttp://recordings.talkshoe.com/TC-34224/TS-317335.mp3\nShe lived in a rural area where her internet was capped at 1.5MB, but it didn’t stop her from contributing to WordPress. Despite living on top of a hill in Southern Ohio, often alone, she left a lasting impact on people across the world. She wasn’t much of a speaker but at WordCamp San Francisco 2014, she gave a presentation on WordPress documentation.
\n\nKim, you’re missed by a lot of people, some of whom you’ve never met. That’s the kind of impact and legacy you’ve left us with. You’re an inspiration to become a better person and be more kind to those in the WordPress community. You opened your heart and soul to whoever needed help and ended every exchange with a smile. I will miss you friend, colleague, and fellow buckeye. My deepest condolences are with the Parsell family.
\nIf you have a lasting memory of Kim, please share it in the comments.
\nRelated Reading:
\nDeveloping an API is hard. Here’s Automattician Demitrious Kelly On API Correctness.
";s: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:"Sun, 04 Jan 2015 19:42: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: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:37;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:32:"Matt: Case for Distributed Teams";s: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:21:"http://ma.tt/?p=44564";s: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://ma.tt/2015/01/case-for-distributed-teams/";s: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:209:"Avleen Vig wrote a great case for distributed teams that covers many of the high-level highlights I’d agree with.
";s: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:"Sun, 04 Jan 2015 16:00: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: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: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:19:"Matt: Jetpack Speed";s: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:21:"http://ma.tt/?p=44562";s: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:35:"http://ma.tt/2015/01/jetpack-speed/";s: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:1422:"Over on the BruteProtect blog they have a look at the Jetpack Bloat Myth, and find that counter-intuitively even though Jetpack has more comprehensive functionality it’s faster than using individual plugins to do the same things. There are economies of scale to Jetpack’s approach, and it doesn’t even include the impact of doing things more advanced and complex like Related Posts. There’s a reason why some web hosts like WP Engine ban most related post plugins but encourage the use of Jetpack.
\nThe performance of the plugin code, though still faster, is still a small difference when compared to the benefit of offloading certain tasks like image resizing, related posts, stats, video transcoding, and more in the future to the WordPress.com cloud (which is now across 11 datacenters worldwide).
\nOf course if you don’t need the functionality at all it’s always faster to have nothing, but that’s a shrinking minority. There are still more optimizations to be had, and in line with a performance focus in 2015 look for more improvements to come in the future. In the meantime, check out the Jetpack benchmarks.
";s: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 Jan 2015 16:03: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: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: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:37:"Matt: Software Engineers Should Write";s: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:21:"http://ma.tt/?p=44560";s: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:53:"http://ma.tt/2015/01/software-engineers-should-write/";s: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:151:"Shubhro Saha on why software engineers should write. Hear hear.
";s: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 Jan 2015 18:00:00 +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: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:47:"Akismet: December and all of 2014 Stats Roundup";s: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=1753";s: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:74:"http://blog.akismet.com/2015/01/01/december-and-all-of-2014-stats-roundup/";s: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:5184:"Gone with the Wind is the highest-grossing movie of all time – making over 3 billion dollars1. The next highest-grossing film is Avatar, with just over 2.7 billion dollars to its name.
\n
\n
In December, Akismet caught 10,136,855,000 spam comments – that’s just over 10 billion. If each spam comment were one dollar, that amount would be about equal to 3 times the total sales of Gone with the Wind. Not too shabby.
\nOn the other hand, Akismet saw just 156,497,000 real comments go through in December. If each one of those were one dollar, they’d make up about 4% of the total sales of Gone with the Wind. As is usual, we see much less real comments than spam comments – at a ratio of about 1 to 65 this month.
\nHere’s the day-to-day breakdown:
\n
The busiest day of the month was the 5th with just over 409 million spam comments, and the slowest day was the 10th with just under 267 spam comments.
\n
For the first time since June, Akismet saw a drop in the number of spam comments month-to-month – we dropped 16% compared to November. However, we still saw a rise of 52% since last year in December.
\nNow… what about 2014 as a whole? Here’s what that looked like in plot form:
\n
\n
How do the numbers fare against the highest grossing movies of all time? In January 2014, Akismet saw about 6 billion comments go through in total. If each comment were one dollar, that’s like the total sales of Gone with the Wind and Avatar combined.
\nThings were moving along at about the same rate until August, when we started noticing much more spam coming through. In September we hit the 300 million spam caught per day mark. In total, there were 8 billion comments caught.
\nNovember was our highest-traffic month with over 12 billion spam comments caught. Continuing with our movie example, that would be like adding up the totals for the top 4 highest grossing films and then a little more: Gone with the Wind and Avatar and Star Wars and Titanic.
\nWhat about the total amount of spam for 2014? That’s 90,326,951,500 – like adding up the total sales of the top 10 movies… and quadrupling that number.
\nOver the year, you may have seen similar trends in the amount of spam comments that you see come through on your own blog or website. As always, if you’re having any issues please do contact us, we’re happy to help!
\nWe’re looking forward to an even more fruitful 2015, with Akismet continuing to save you from your spam. All of us from Akismet wish you a thrilling, successful, and happy new year!
\nThis post is part of a monthly series summarizing some stats and figures from the Akismet universe. Feel free to browse all of the posts in the series.
\nFootnote
\n1when adjusted for inflation in 2011 dollars, which is what really counts ;)
";s: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 Jan 2015 17:30: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:7:"Valerie";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:21:"Matt: Donate to GnuPG";s: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:21:"http://ma.tt/?p=44552";s: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:37:"http://ma.tt/2014/12/donate-to-gnupg/";s: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:185:"With the news that PGP is one of the things that is still tough for the NSA, now is a great time to donate to GnuPG, which I just did.
";s: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 Dec 2014 21:56:00 +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: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:91:"WPTavern: How to Preview Posts in Distraction-free Writing Mode Without Seeing a Transition";s: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:"http://wptavern.com/?p=36595";s: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:101:"http://wptavern.com/how-to-preview-posts-in-distraction-free-writing-mode-without-seeing-a-transition";s: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:1905:"In order to see the post meta boxes using Distraction-free Writing Mode in WordPress 4.1, you have to move the cursor away from the post editor. During the editing process, you may need to preview a post several times. Since the preview button is only available when the publish meta box is shown, you have to go in and out of DFW mode multiple times before publishing a post.
\nThis can not only be annoying, but discourage you from using DFW mode altogether. Thankfully, there’s a handy plugin by Alex King that solves the problem by adding a preview button inside the post editor.
\n
Preview Button is Always Visible\nThe preview button inside the editor significantly reduces the amount of times the DFW transition occurs. What’s nice about this plugin is that when you disable DFW mode, the preview button disappears in favor of the publish meta box.
\nI tested the plugin using WordPress 4.1 and didn’t encounter any issues. The plugin is available in the plugin directory and Github where pull requests are welcomed.
";s: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 Dec 2014 20:02:01 +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: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:"WPTavern: Benchmarks Indicate Jetpack Doesn’t Negatively Impact Site Loading Times";s: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:"http://wptavern.com/?p=36539";s: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:91:"http://wptavern.com/benchmarks-indicate-jetpack-doesnt-negatively-impact-site-loading-times";s: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:3777:"
photo credit: the JoshMeister – cc\nJetpack is a WordPress plugin maintained by Automattic and has more than 30 different modules. The modules provide a variety of features including, contact forms, stats, and related posts.
\nPart of Jetpack’s reputation in the WordPress community is that it’s bloated and slows down websites. Sam Hotchkiss, who is part of the Jetpack team, has published benchmark results showing the performance impact of Jetpack is not as bad as you might think.
\nThe benchmarks run on two different setups. The first is a website where the user is only running Jetpack with 19 modules activated. (After The Deadline, Contact Form, Custom Content Types, Custom CSS, Gravatar Hovercards, Latex, Notes, Omnisearch, Post By Email, Publicize, Sharedaddy, Shortcodes, Shortlinks, Stats, Subscriptions, Vaultpress, Verification Tools, Widget Visibility, Widgets).
\nThe second environment involves a user running five plugins that replicate similar functionality of popular modules. (Contact Form 7, Google Analytics Dashboard for WP, Simple Custom CSS, Share Buttons by AddToAny, NextScripts: Social Networks Auto-Poster). The plugins were chosen because they have the most downloads in the directory providing similar functionality.
\nJetpack, First load, TTFB: 773ms
\nJetpack, First load, Complete page load: 1876ms
\nJetpack, Repeat view, TTFB: 143ms
\nJetpack, Repeat view, Complete page load: 322ms
Other Plugins, First load, TTFB: 797ms
\nOther Plugins, First load, Complete page load: 2609ms
\nOther Plugins, Repeat view, TTFB: 460ms
\nOther Plugins, Repeat view, Complete page load: 529ms
As you can see, the performance impact from using Jetpack is negligible at best. Jetpack also has fewer HTTP requests overall than the custom plugins installed.
\n
Number of HTTP Requests\nAccording to Hotchkiss, there’s a series of 35 tests that run against Jetpack every time a change is committed to the master branch. The tests are designed to detect whether or not a change negatively impacts site performance. Hotchkiss says the test results will be released in the near future, “We’ll be releasing all the results of these tests to the public in the near future. Every member of the Jetpack team is committed to making sure that performance is a high priority for the project.”
\nThe results indicate Jetpack doesn’t hinder website performance as much as you might think. It’s only one set of results, but I’m curious to see how it performs in a variety of situations and environments. Do you think the results accurately represent Jetpack and what other benchmark tests would you like to see performed?
";s: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 Dec 2014 17:56: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: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:60:"WPTavern: A Look Back at WordPress News in 2014, Part 2 of 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:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=36578";s: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:"http://wptavern.com/a-look-back-at-wordpress-news-in-2014-part-2-of-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:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:37876:"
photo credit: Merlin1487 – cc\nThis is part two of a two part series looking back at WordPress news in 2014. There was plenty of action to write about with over 900 posts published in 2014. Browse through the list and if a particular story had an impact on you, let us know in the comments.
\nThe stories included here are handpicked based on their newsworthiness, importance, and whether they generated a healthy discussion in the comments. The posts are in chronological order starting with July.
\n
When the distraction-free writing mode was overhauled in WordPress 4.1 my little Preview Button plugin was rendered non-functional. Never fear, it’s now been updated and works a treat.
\nThis post is part of the project: Fullscreen Preview Button. View the project timeline for more context on this post.
";s: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 Dec 2014 23:14: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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Alex";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:65:"WPTavern: Dear WordPress Plugin Developer, Please Add Screenshots";s: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:"http://wptavern.com/?p=30748";s: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:74:"http://wptavern.com/dear-wordpress-plugin-developer-please-add-screenshots";s: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:6263:"
photo credit: when i was a bird – cc\nThis year the WordPress plugin directory crossed 35,000 plugin listings and is rapidly approaching one billion total downloads. WordPress 4.0 added custom icons to the plugin installer in the admin, which helps developers to differentiate their plugins in this massive sea of extensions. Plugin branding is useful for standing out in the initial results of a search, but beyond that there is one tab that gives plugins a distinct advantage over others.
\nHow important is the Screenshots tab for plugins hosted on WordPress.org? Feedback from our readers indicates that screenshots are a critical part of a understanding what a plugin does:
\n\n\n@pollyplummer screenshots is the first tab I click on for any plugin. How a plugin integrates with WP can say a great deal about it.
\n— Scott Evans (@scottsweb) September 17, 2014
There’s nothing more infuriating than an incomplete plugin description with no screenshots. When you’re on the hunt for a specific functionality, it can be time-consuming to install a plugin, only to find out that it doesn’t do what you need it to do. For the plugin developer, there’s always the risk that someone will install your plugin, find out that it doesn’t do what they want, and give it a poor review because of the inconvenience.
\nMany users now hunt for plugins in the admin, as opposed to directly on WordPress.org. If you’re a plugin developer, it’s a good idea to remember that the plugin details page is still available to users searching in the admin via a modal window.
\nWith the exception of plugins that have no visible output, every plugin listed in the directory could benefit from a set of basic screenshots. Some plugins, such as BuddyPress or Jetpack, have their own websites full of images. Even with a separate website, the plugins still include screenshots for users who don’t wish to navigate away from the admin or WordPress.org.
\nIf your plugin does something visual on the frontend, users appreciate a screenshot of an example, even if the output varies depending on the active theme. Frontend and backend screenshots are equally important.
\n\n\n@pollyplummer SO many plugin just show the backend settings. I want to see how it outputs!!
\n— Phil Hoyt (@philhoyt) September 17, 2014
\n\n@pollyplummer @bobWP And even if it does something not so visual, screenshots are very much needed, wanted and appreciated!
\n— David Bell (@Cape_Dave) September 17, 2014
For a simple plugin, with no dedicated website, having screenshots could be the difference between gaining a strong user base or having your plugin stuck at just a handful of downloads.
\nI’m borderline obsessive when it comes to the WordPress plugin directory. I have scanned through every single plugin that has come through the directory for the past several years, always on the hunt for the cream of the crop. Even with a solid description, if the plugin has no screenshots, it’s tough to find the motivation to take it on a test run. There are many gems hiding in the directory that have been overlooked and undervalued, simply because users cannot visualize how the plugin works.
\nIf you are hosting a plugin on WordPress.org, there are three solid advantages to adding screenshots to your details page:
\nA plugin developer’s decision to omit screenshots is not necessarily indicative of the plugin’s future, but screenshots can go a long way towards building a solid user base that can make your plugin worth all the hard work you’ve put into it.
\nIf you’re going through the trouble of putting your plugin up on WordPress.org, you might as well spend a couple extra minutes adding a few basic screenshots. Who knows? That plugin could be the key to your next paid gig and a valuable example of your work as an open source developer. Your plugin may even be the next most widely recommended tool for WordPress users, but the world may never know if you don’t bother to add any screenshots.
";s: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 Dec 2014 22:09:08 +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:"Sarah Gooding";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:"Matt: Best of 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:21:"http://ma.tt/?p=44548";s: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:39:"http://ma.tt/2014/12/best-of-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:178:"Longreads has just published their best of 2014 list which has plenty to keep you entertained and read for hours.
";s: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 Dec 2014 18:39:00 +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: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:58:"WPTavern: Add an Expiration Date to WordPress Sticky Posts";s: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:"http://wptavern.com/?p=36164";s: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:"http://wptavern.com/add-an-expiration-date-to-wordpress-sticky-posts";s: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:2901:"
photo credit: This Year’s Love – cc\nWordPress’ sticky posts feature was introduced six years ago in the 2.7 release. It was added to enable users to stick important posts to the front page so that they won’t disappear in a blog’s steady stream of chronologically ordered content.
\nBy default, a sticky post is sticky indefinitely and requires you to manually uncheck the box under the post’s visibility settings in order to remove its stickiness. Expire Sticky Posts is a new ultra-simple plugin that allows you to set an expiration date on your sticky selections.
\n
The plugin, created by Andy von Dohren, is a fork of the Simple Post Expiration plugin by Pippin Williamson. Expire Sticky Posts adds a date entry box to the publish panel for setting an expiration date if the post has been checked as sticky.
The plugin is perfect for automating the management of seasonal sticky posts and important time-sensitive notices. Also, some themes rely on sticky posts for setting the featured content on the homepage, requiring you to manually change them out. This plugin allows you to set up future dates for expiring sticky posts at the time that you publish them, so you don’t have to log in and change it later.
\nI tested the plugin and found that it works as advertised. The only thing I would add is the ability to set a specific time in addition to the date, as this may be important in some instances. If you find the Expire Sticky Posts plugin to be useful and have any further feedback, feel free to leave a note in the issues queue of the project’s GitHub repository.
";s: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 Dec 2014 06:07: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:"Sarah Gooding";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:69:"WPTavern: WordPress Community Pulls Together to Help a Member in Need";s: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:"http://wptavern.com/?p=36487";s: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:79:"http://wptavern.com/wordpress-community-pulls-together-to-help-a-member-in-need";s: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:3787:"
photo credit: Stewardship – Transforming Generosity – cc\nDan Griffiths, who is known on Twitter as Ghost1227 and one of the creators of WP Tally, recently found himself in an emergency situation. Due to personal reasons, details of the situation have been withheld but it required Griffiths to come up with $2,500 within a 24 hour time span. Griffiths is a military Veteran who served in the Marines and received an honorable discharge.
\nHe reached out to Happy Joe, an organization that helps veterans in need. Happy Joe founder, James Dalman, published an all points bulletin on Twitter asking for help from the WordPress community.
\n\n\nPLEASE help @ghost1227 raise $2500 in the next 24 hours. It''s an emergency and he is a #marine #veteran. http://t.co/6SDlA41IkP
\n— jamesdalman (@jamesdalman) December 30, 2014
At least 22 people retweeted the call for help with several members of the WordPress community sending out custom tweets. I donated $20 to the campaign not only to thank Griffiths for his service, but to help him out in a dire time of need. Within two hours of the initial call for help, Griffiths reached his goal and added the following message to his personal donation page.
\n\nI can’t believe the response my call for help has received… For lack of a better word, I’m in shock. My sincerest thanks go out to the whole community for your unbelievable support. In a matter of an hour or two I received more than I ever thought possible… much from people whom I wasn’t even aware I had made an impression on. I am beyond humbled at the awesomeness of our community and can’t begin to express how much you all mean to me. Thanks again, and I hope we can continue to make WordPress, our community, and the Internet as a whole even better this coming year than the last!
This isn’t the first time the community has been generous to those in need. Near the end of 2013, the community rallied together to donate over $7,300 ($2,000 over the requested amount) to help Justin Tadlock buy a house.
\nI can’t imagine the overwhelming sense of happiness Griffiths must be feeling. The fact that several of the donations came from people he doesn’t know is another indication of just how awesome and generous the WordPress community is to those who need it most.
";s: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 Dec 2014 05:09: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: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:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:10:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Sun, 11 Jan 2015 14:20:29 GMT";s:12:"content-type";s:8:"text/xml";s:14:"content-length";s:6:"304485";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Sun, 11 Jan 2015 14:15:13 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";s:13:"accept-ranges";s:5:"bytes";}s:5:"build";s:14:"20130911080210";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (7548, '_site_transient_browser_fcf8cc3594f4801f9ee0936c74c111ac', 'a:9:{s:8:"platform";s:7:"Windows";s:4:"name";s:6:"Chrome";s:7:"version";s:12:"39.0.2171.95";s:10:"update_url";s:28:"http://www.google.com/chrome";s:7:"img_src";s:49:"http://s.wordpress.org/images/browsers/chrome.png";s:11:"img_src_ssl";s:48:"https://wordpress.org/images/browsers/chrome.png";s:15:"current_version";s:2:"18";s:7:"upgrade";b:0;s:8:"insecure";b:0;}', 'yes'), (4407, 'WPLANG', '', 'yes'), (7570, '_site_transient_timeout_wporg_theme_feature_list', '1420998267', 'yes'), (7571, '_site_transient_wporg_theme_feature_list', 'a:4:{s:6:"Colors";a:15:{i:0;s:5:"black";i:1;s:4:"blue";i:2;s:5:"brown";i:3;s:4:"gray";i:4;s:5:"green";i:5;s:6:"orange";i:6;s:4:"pink";i:7;s:6:"purple";i:8;s:3:"red";i:9;s:6:"silver";i:10;s:3:"tan";i:11;s:5:"white";i:12;s:6:"yellow";i:13;s:4:"dark";i:14;s:5:"light";}s:6:"Layout";a:9:{i:0;s:12:"fixed-layout";i:1;s:12:"fluid-layout";i:2;s:17:"responsive-layout";i:3;s:10:"one-column";i:4;s:11:"two-columns";i:5;s:13:"three-columns";i:6;s:12:"four-columns";i:7;s:12:"left-sidebar";i:8;s:13:"right-sidebar";}s:8:"Features";a:20:{i:0;s:19:"accessibility-ready";i:1;s:8:"blavatar";i:2;s:10:"buddypress";i:3;s:17:"custom-background";i:4;s:13:"custom-colors";i:5;s:13:"custom-header";i:6;s:11:"custom-menu";i:7;s:12:"editor-style";i:8;s:21:"featured-image-header";i:9;s:15:"featured-images";i:10;s:15:"flexible-header";i:11;s:20:"front-page-post-form";i:12;s:19:"full-width-template";i:13;s:12:"microformats";i:14;s:12:"post-formats";i:15;s:20:"rtl-language-support";i:16;s:11:"sticky-post";i:17;s:13:"theme-options";i:18;s:17:"threaded-comments";i:19;s:17:"translation-ready";}s:7:"Subject";a:3:{i:0;s:7:"holiday";i:1;s:13:"photoblogging";i:2;s:8:"seasonal";}}', 'yes'), (7584, '_site_transient_timeout_theme_roots', '1420989594', 'yes'), (7585, '_site_transient_theme_roots', 'a:4:{s:13:"twentyfifteen";s:7:"/themes";s:14:"twentyfourteen";s:7:"/themes";s:14:"twentythirteen";s:7:"/themes";s:12:"twentytwelve";s:7:"/themes";}', 'yes'), (4410, '_transient_random_seed', '325f9d80e39d9413912a86303459d874', 'yes'), (7547, '_site_transient_timeout_browser_fcf8cc3594f4801f9ee0936c74c111ac', '1421590414', 'yes'), (7568, 'recently_activated', 'a:0:{}', 'yes'), (7569, 'can_compress_scripts', '1', 'yes'), (7555, '_transient_timeout_feed_mod_867bd5c64f85878d03a060509cd2f92c', '1421028818', 'no'), (7556, '_transient_feed_mod_867bd5c64f85878d03a060509cd2f92c', '1420985618', 'no'), (7557, '_transient_timeout_feed_b9388c83948825c1edaef0d856b7b109', '1421028818', 'no'), (7558, '_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";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:72:"\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:2:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:39:"WordPress Plugins » View: Most Popular";s: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/browse/popular/";s: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:39:"WordPress Plugins » View: Most Popular";s: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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 11 Jan 2015 14:05: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:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:25:"http://bbpress.org/?v=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:"";}}s:4:"item";a:15:{i:0;a:6:{s:4:"data";s:30:"\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:7:"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:4:"link";a:1:{i:0;a:5:{s:4:"data";s:46:"https://wordpress.org/plugins/akismet/#post-15";s: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, 09 Mar 2007 22: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"15@https://wordpress.org/plugins/";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:98:"Akismet checks your comments against the Akismet Web service to see if they look like spam or not.";s: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:"Matt 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:"";}}}}}i:1;a:6:{s:4:"data";s:30:"\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: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:59:"https://wordpress.org/plugins/all-in-one-seo-pack/#post-753";s: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 20:08: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"753@https://wordpress.org/plugins/";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:126:"All in One SEO Pack is a WordPress SEO plugin to automatically optimize your WordPress blog for Search Engines such as Google.";s: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:"uberdose";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:30:"\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: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:55:"https://wordpress.org/plugins/contact-form-7/#post-2141";s: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:45: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:35:"2141@https://wordpress.org/plugins/";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:"";}}}}}i:3;a:6:{s:4:"data";s:30:"\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:25:"Google Analytics by Yoast";s: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/plugins/google-analytics-for-wordpress/#post-2316";s: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, 14 Sep 2007 12:15: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"2316@https://wordpress.org/plugins/";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:124:"Track your WordPress site easily with the latest tracking codes and lots added data for search result pages and error pages.";s: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:"";}}}}}i:4;a:6:{s:4:"data";s:30:"\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: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:49:"https://wordpress.org/plugins/jetpack/#post-23862";s: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:36:"23862@https://wordpress.org/plugins/";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:28:"Your WordPress, Streamlined.";s: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:"Tim Moore";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:30:"\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:22:"WordPress SEO by Yoast";s: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://wordpress.org/plugins/wordpress-seo/#post-8321";s: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 Jan 2009 20:34: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"8321@https://wordpress.org/plugins/";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:131:"Improve your WordPress SEO: Write better content and have a fully optimized WordPress site using Yoast's WordPress SEO 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: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:"";}}}}}i:6;a:6:{s:4:"data";s:30:"\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:33:"WooCommerce - excelling eCommerce";s: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:53:"https://wordpress.org/plugins/woocommerce/#post-29860";s: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 Sep 2011 08:13: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:36:"29860@https://wordpress.org/plugins/";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:"";}}}}}i:7;a:6:{s:4:"data";s:30:"\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:"iThemes Security (formerly Better WP Security)";s: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:60:"https://wordpress.org/plugins/better-wp-security/#post-21738";s: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 Oct 2010 22:06: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:36:"21738@https://wordpress.org/plugins/";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:63:"The easiest, most effective way to secure WordPress in seconds.";s: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:"Chris Wiegman";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:30:"\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: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:60:"https://wordpress.org/plugins/wordpress-importer/#post-18101";s: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 17:42: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:36:"18101@https://wordpress.org/plugins/";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:"";}}}}}i:9;a:6:{s:4:"data";s:30:"\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: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:64:"https://wordpress.org/plugins/google-sitemap-generator/#post-132";s: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, 09 Mar 2007 22:31:32 +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:34:"132@https://wordpress.org/plugins/";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:105:"This plugin will generate a special XML sitemap which will help search engines to better index your blog.";s: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:5:"arnee";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:30:"\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:33:"Google Analytics Dashboard for WP";s: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:75:"https://wordpress.org/plugins/google-analytics-dashboard-for-wp/#post-50539";s: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:"Sun, 10 Mar 2013 17:07: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:36:"50539@https://wordpress.org/plugins/";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:148:"Displays Google Analytics reports and real-time statistics in your WordPress Dashboard. Inserts the latest tracking code in every page of your 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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Alin Marcu";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:30:"\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:18:"Wordfence Security";s: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/wordfence/#post-29832";s: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:"Sun, 04 Sep 2011 03:13:51 +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:36:"29832@https://wordpress.org/plugins/";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:137:"Wordfence Security is a free enterprise class security and performance plugin that makes your site up to 50 times faster and more secure.";s: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:"Wordfence";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:30:"\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:"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:57:"https://wordpress.org/plugins/tinymce-advanced/#post-2082";s: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, 27 Jun 2007 15:00:26 +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:35:"2082@https://wordpress.org/plugins/";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:71:"Enables the advanced features of TinyMCE, the WordPress WYSIWYG 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:"";}}}}}i:13;a:6:{s:4:"data";s:30:"\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:15:"NextGEN Gallery";s: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:56:"https://wordpress.org/plugins/nextgen-gallery/#post-1169";s: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, 23 Apr 2007 20:08: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"1169@https://wordpress.org/plugins/";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:121:"The most popular WordPress gallery plugin and one of the most popular plugins of all time with over 10 million downloads.";s: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:"Alex Rabe";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:30:"\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:"WPtouch Mobile 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:"link";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wordpress.org/plugins/wptouch/#post-5468";s: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 May 2008 04:58: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"5468@https://wordpress.org/plugins/";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:63:"Create a slick mobile WordPress website with just a few clicks.";s: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:"BraveNewCode Inc.";s: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:46:"https://wordpress.org/plugins/rss/view/popular";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:4:"type";i:128;s:7:"headers";a:11:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Sun, 11 Jan 2015 14:20:30 GMT";s:12:"content-type";s:23:"text/xml; charset=UTF-8";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:7:"expires";s:29:"Sun, 11 Jan 2015 14:40:18 GMT";s:13:"cache-control";s:0:"";s:6:"pragma";s:0:"";s:13:"last-modified";s:31:"Sun, 11 Jan 2015 14:05:18 +0000";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";}s:5:"build";s:14:"20130911080210";}', 'no'), (7559, '_transient_timeout_feed_mod_b9388c83948825c1edaef0d856b7b109', '1421028818', 'no'), (7560, '_transient_feed_mod_b9388c83948825c1edaef0d856b7b109', '1420985618', 'no'), (7561, '_transient_timeout_plugin_slugs', '1421072158', 'no'), (7562, '_transient_plugin_slugs', 'a:2:{i:0;s:19:"akismet/akismet.php";i:1;s:9:"hello.php";}', 'no'), (7563, '_transient_timeout_dash_4077549d03da2e451c8b5f002294ff51', '1421028818', 'no'), (7564, '_transient_dash_4077549d03da2e451c8b5f002294ff51', '', 'no'), (7576, 'theme_mods_twentythirteen', 'a:1:{s:16:"sidebars_widgets";a:2:{s:4:"time";i:1420986959;s:4:"data";a:3:{s:19:"wp_inactive_widgets";a:0:{}s:9:"sidebar-1";a:6:{i:0;s:8:"search-2";i:1;s:14:"recent-posts-2";i:2;s:17:"recent-comments-2";i:3;s:10:"archives-2";i:4;s:12:"categories-2";i:5;s:6:"meta-2";}s:9:"sidebar-2";a:0:{}}}}', 'yes'), (7577, 'current_theme', 'Twenty Fourteen', 'yes'), (7578, 'theme_mods_twentyfourteen', 'a:1:{i:0;b:0;}', 'yes'), (7579, 'theme_switched', '', 'yes'), (7582, 'rewrite_rules', 'a:68:{s:47:"category/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$";s:52:"index.php?category_name=$matches[1]&feed=$matches[2]";s:42:"category/(.+?)/(feed|rdf|rss|rss2|atom)/?$";s:52:"index.php?category_name=$matches[1]&feed=$matches[2]";s:35:"category/(.+?)/page/?([0-9]{1,})/?$";s:53:"index.php?category_name=$matches[1]&paged=$matches[2]";s:17:"category/(.+?)/?$";s:35:"index.php?category_name=$matches[1]";s:44:"tag/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?tag=$matches[1]&feed=$matches[2]";s:39:"tag/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?tag=$matches[1]&feed=$matches[2]";s:32:"tag/([^/]+)/page/?([0-9]{1,})/?$";s:43:"index.php?tag=$matches[1]&paged=$matches[2]";s:14:"tag/([^/]+)/?$";s:25:"index.php?tag=$matches[1]";s:45:"type/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?post_format=$matches[1]&feed=$matches[2]";s:40:"type/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?post_format=$matches[1]&feed=$matches[2]";s:33:"type/([^/]+)/page/?([0-9]{1,})/?$";s:51:"index.php?post_format=$matches[1]&paged=$matches[2]";s:15:"type/([^/]+)/?$";s:33:"index.php?post_format=$matches[1]";s:12:"robots\\.txt$";s:18:"index.php?robots=1";s:48:".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$";s:18:"index.php?feed=old";s:20:".*wp-app\\.php(/.*)?$";s:19:"index.php?error=403";s:18:".*wp-register.php$";s:23:"index.php?register=true";s:32:"feed/(feed|rdf|rss|rss2|atom)/?$";s:27:"index.php?&feed=$matches[1]";s:27:"(feed|rdf|rss|rss2|atom)/?$";s:27:"index.php?&feed=$matches[1]";s:20:"page/?([0-9]{1,})/?$";s:28:"index.php?&paged=$matches[1]";s:41:"comments/feed/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?&feed=$matches[1]&withcomments=1";s:36:"comments/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?&feed=$matches[1]&withcomments=1";s:44:"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:40:"index.php?s=$matches[1]&feed=$matches[2]";s:39:"search/(.+)/(feed|rdf|rss|rss2|atom)/?$";s:40:"index.php?s=$matches[1]&feed=$matches[2]";s:32:"search/(.+)/page/?([0-9]{1,})/?$";s:41:"index.php?s=$matches[1]&paged=$matches[2]";s:14:"search/(.+)/?$";s:23:"index.php?s=$matches[1]";s:47:"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?author_name=$matches[1]&feed=$matches[2]";s:42:"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?author_name=$matches[1]&feed=$matches[2]";s:35:"author/([^/]+)/page/?([0-9]{1,})/?$";s:51:"index.php?author_name=$matches[1]&paged=$matches[2]";s:17:"author/([^/]+)/?$";s:33:"index.php?author_name=$matches[1]";s:69:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$";s:80:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]";s:64:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$";s:80:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]";s:57:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$";s:81:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]";s:39:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$";s:63:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]";s:56:"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$";s:64:"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]";s:51:"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$";s:64:"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]";s:44:"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$";s:65:"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]";s:26:"([0-9]{4})/([0-9]{1,2})/?$";s:47:"index.php?year=$matches[1]&monthnum=$matches[2]";s:43:"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$";s:43:"index.php?year=$matches[1]&feed=$matches[2]";s:38:"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$";s:43:"index.php?year=$matches[1]&feed=$matches[2]";s:31:"([0-9]{4})/page/?([0-9]{1,})/?$";s:44:"index.php?year=$matches[1]&paged=$matches[2]";s:13:"([0-9]{4})/?$";s:26:"index.php?year=$matches[1]";s:27:".?.+?/attachment/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:37:".?.+?/attachment/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:57:".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:52:".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:52:".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:20:"(.?.+?)/trackback/?$";s:35:"index.php?pagename=$matches[1]&tb=1";s:40:"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$";s:47:"index.php?pagename=$matches[1]&feed=$matches[2]";s:35:"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$";s:47:"index.php?pagename=$matches[1]&feed=$matches[2]";s:28:"(.?.+?)/page/?([0-9]{1,})/?$";s:48:"index.php?pagename=$matches[1]&paged=$matches[2]";s:35:"(.?.+?)/comment-page-([0-9]{1,})/?$";s:48:"index.php?pagename=$matches[1]&cpage=$matches[2]";s:20:"(.?.+?)(/[0-9]+)?/?$";s:47:"index.php?pagename=$matches[1]&page=$matches[2]";s:27:"[^/]+/attachment/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:37:"[^/]+/attachment/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:57:"[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:52:"[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:52:"[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:20:"([^/]+)/trackback/?$";s:31:"index.php?name=$matches[1]&tb=1";s:40:"([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:43:"index.php?name=$matches[1]&feed=$matches[2]";s:35:"([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:43:"index.php?name=$matches[1]&feed=$matches[2]";s:28:"([^/]+)/page/?([0-9]{1,})/?$";s:44:"index.php?name=$matches[1]&paged=$matches[2]";s:35:"([^/]+)/comment-page-([0-9]{1,})/?$";s:44:"index.php?name=$matches[1]&cpage=$matches[2]";s:20:"([^/]+)(/[0-9]+)?/?$";s:43:"index.php?name=$matches[1]&page=$matches[2]";s:16:"[^/]+/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:26:"[^/]+/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:46:"[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:41:"[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:41:"[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";}', 'yes'), (7593, '_site_transient_timeout_available_translations', '1420999271', 'yes'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (7594, '_site_transient_available_translations', 'a:46:{s:2:"ar";a:8:{s:8:"language";s:2:"ar";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-18 13:48:58";s:12:"english_name";s:6:"Arabic";s:11:"native_name";s:14:"العربية";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/ar.zip";s:3:"iso";a:2:{i:1;s:2:"ar";i:2;s:3:"ara";}s:7:"strings";a:1:{s:8:"continue";s:16:"المتابعة";}}s:2:"az";a:8:{s:8:"language";s:2:"az";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-09 18:52:27";s:12:"english_name";s:11:"Azerbaijani";s:11:"native_name";s:16:"Azərbaycan dili";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/az.zip";s:3:"iso";a:2:{i:1;s:2:"az";i:2;s:3:"aze";}s:7:"strings";a:1:{s:8:"continue";s:5:"Davam";}}s:5:"bg_BG";a:8:{s:8:"language";s:5:"bg_BG";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-04 21:03:27";s:12:"english_name";s:9:"Bulgarian";s:11:"native_name";s:18:"Български";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/bg_BG.zip";s:3:"iso";a:2:{i:1;s:2:"bg";i:2;s:3:"bul";}s:7:"strings";a:1:{s:8:"continue";s:22:"Продължение";}}s:5:"bs_BA";a:8:{s:8:"language";s:5:"bs_BA";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 17:39:56";s:12:"english_name";s:7:"Bosnian";s:11:"native_name";s:8:"Bosanski";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/bs_BA.zip";s:3:"iso";a:2:{i:1;s:2:"bs";i:2;s:3:"bos";}s:7:"strings";a:1:{s:8:"continue";s:7:"Nastavi";}}s:2:"ca";a:8:{s:8:"language";s:2:"ca";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-09 04:10:35";s:12:"english_name";s:7:"Catalan";s:11:"native_name";s:7:"Català";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/ca.zip";s:3:"iso";a:2:{i:1;s:2:"ca";i:2;s:3:"cat";}s:7:"strings";a:1:{s:8:"continue";s:8:"Continua";}}s:2:"cy";a:8:{s:8:"language";s:2:"cy";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-09 11:12:57";s:12:"english_name";s:5:"Welsh";s:11:"native_name";s:7:"Cymraeg";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/cy.zip";s:3:"iso";a:2:{i:1;s:2:"cy";i:2;s:3:"cym";}s:7:"strings";a:1:{s:8:"continue";s:6:"Parhau";}}s:5:"da_DK";a:8:{s:8:"language";s:5:"da_DK";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-06 18:51:09";s:12:"english_name";s:6:"Danish";s:11:"native_name";s:5:"Dansk";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/da_DK.zip";s:3:"iso";a:2:{i:1;s:2:"da";i:2;s:3:"dan";}s:7:"strings";a:1:{s:8:"continue";s:12:"Fortsæt";}}s:5:"de_DE";a:8:{s:8:"language";s:5:"de_DE";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-04 15:21:32";s:12:"english_name";s:6:"German";s:11:"native_name";s:7:"Deutsch";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/de_DE.zip";s:3:"iso";a:1:{i:1;s:2:"de";}s:7:"strings";a:1:{s:8:"continue";s:10:"Fortfahren";}}s:2:"el";a:8:{s:8:"language";s:2:"el";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 21:47:46";s:12:"english_name";s:5:"Greek";s:11:"native_name";s:16:"Ελληνικά";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/el.zip";s:3:"iso";a:2:{i:1;s:2:"el";i:2;s:3:"ell";}s:7:"strings";a:1:{s:8:"continue";s:16:"Συνέχεια";}}s:5:"en_CA";a:8:{s:8:"language";s:5:"en_CA";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-18 00:30:12";s:12:"english_name";s:16:"English (Canada)";s:11:"native_name";s:16:"English (Canada)";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/en_CA.zip";s:3:"iso";a:3:{i:1;s:2:"en";i:2;s:3:"eng";i:3;s:3:"eng";}s:7:"strings";a:1:{s:8:"continue";s:8:"Continue";}}s:5:"en_AU";a:8:{s:8:"language";s:5:"en_AU";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-16 23:14:33";s:12:"english_name";s:19:"English (Australia)";s:11:"native_name";s:19:"English (Australia)";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/en_AU.zip";s:3:"iso";a:3:{i:1;s:2:"en";i:2;s:3:"eng";i:3;s:3:"eng";}s:7:"strings";a:1:{s:8:"continue";s:8:"Continue";}}s:5:"en_GB";a:8:{s:8:"language";s:5:"en_GB";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-06 08:18:42";s:12:"english_name";s:12:"English (UK)";s:11:"native_name";s:12:"English (UK)";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/en_GB.zip";s:3:"iso";a:3:{i:1;s:2:"en";i:2;s:3:"eng";i:3;s:3:"eng";}s:7:"strings";a:1:{s:8:"continue";s:8:"Continue";}}s:2:"eo";a:8:{s:8:"language";s:2:"eo";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 22:46:58";s:12:"english_name";s:9:"Esperanto";s:11:"native_name";s:9:"Esperanto";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/eo.zip";s:3:"iso";a:2:{i:1;s:2:"eo";i:2;s:3:"epo";}s:7:"strings";a:1:{s:8:"continue";s:8:"Daŭrigi";}}s:5:"es_PE";a:8:{s:8:"language";s:5:"es_PE";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-19 08:14:32";s:12:"english_name";s:14:"Spanish (Peru)";s:11:"native_name";s:17:"Español de Perú";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/es_PE.zip";s:3:"iso";a:2:{i:1;s:2:"es";i:2;s:3:"spa";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuar";}}s:5:"es_ES";a:8:{s:8:"language";s:5:"es_ES";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-09 09:37:59";s:12:"english_name";s:15:"Spanish (Spain)";s:11:"native_name";s:8:"Español";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/es_ES.zip";s:3:"iso";a:1:{i:1;s:2:"es";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuar";}}s:5:"es_MX";a:8:{s:8:"language";s:5:"es_MX";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 23:41:34";s:12:"english_name";s:16:"Spanish (Mexico)";s:11:"native_name";s:19:"Español de México";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/es_MX.zip";s:3:"iso";a:2:{i:1;s:2:"es";i:2;s:3:"spa";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuar";}}s:5:"es_CL";a:8:{s:8:"language";s:5:"es_CL";s:7:"version";s:3:"4.0";s:7:"updated";s:19:"2014-09-04 19:47:01";s:12:"english_name";s:15:"Spanish (Chile)";s:11:"native_name";s:17:"Español de Chile";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.0/es_CL.zip";s:3:"iso";a:2:{i:1;s:2:"es";i:2;s:3:"spa";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuar";}}s:2:"eu";a:8:{s:8:"language";s:2:"eu";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-09 12:20:08";s:12:"english_name";s:6:"Basque";s:11:"native_name";s:7:"Euskara";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/eu.zip";s:3:"iso";a:2:{i:1;s:2:"eu";i:2;s:3:"eus";}s:7:"strings";a:1:{s:8:"continue";s:8:"Jarraitu";}}s:5:"fa_IR";a:8:{s:8:"language";s:5:"fa_IR";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-18 23:18:50";s:12:"english_name";s:7:"Persian";s:11:"native_name";s:10:"فارسی";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/fa_IR.zip";s:3:"iso";a:2:{i:1;s:2:"fa";i:2;s:3:"fas";}s:7:"strings";a:1:{s:8:"continue";s:10:"ادامه";}}s:2:"fi";a:8:{s:8:"language";s:2:"fi";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-17 07:01:16";s:12:"english_name";s:7:"Finnish";s:11:"native_name";s:5:"Suomi";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/fi.zip";s:3:"iso";a:2:{i:1;s:2:"fi";i:2;s:3:"fin";}s:7:"strings";a:1:{s:8:"continue";s:5:"Jatka";}}s:5:"fr_FR";a:8:{s:8:"language";s:5:"fr_FR";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-05 09:12:27";s:12:"english_name";s:15:"French (France)";s:11:"native_name";s:9:"Français";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/fr_FR.zip";s:3:"iso";a:1:{i:1;s:2:"fr";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuer";}}s:2:"gd";a:8:{s:8:"language";s:2:"gd";s:7:"version";s:3:"4.0";s:7:"updated";s:19:"2014-09-05 17:37:43";s:12:"english_name";s:15:"Scottish Gaelic";s:11:"native_name";s:9:"Gàidhlig";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.0/gd.zip";s:3:"iso";a:3:{i:1;s:2:"gd";i:2;s:3:"gla";i:3;s:3:"gla";}s:7:"strings";a:1:{s:8:"continue";s:15:"Lean air adhart";}}s:5:"gl_ES";a:8:{s:8:"language";s:5:"gl_ES";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-17 18:21:32";s:12:"english_name";s:8:"Galician";s:11:"native_name";s:6:"Galego";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/gl_ES.zip";s:3:"iso";a:2:{i:1;s:2:"gl";i:2;s:3:"glg";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuar";}}s:5:"he_IL";a:8:{s:8:"language";s:5:"he_IL";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-18 06:09:08";s:12:"english_name";s:6:"Hebrew";s:11:"native_name";s:16:"עִבְרִית";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/he_IL.zip";s:3:"iso";a:1:{i:1;s:2:"he";}s:7:"strings";a:1:{s:8:"continue";s:12:"להמשיך";}}s:2:"hr";a:8:{s:8:"language";s:2:"hr";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-19 14:39:57";s:12:"english_name";s:8:"Croatian";s:11:"native_name";s:8:"Hrvatski";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/hr.zip";s:3:"iso";a:2:{i:1;s:2:"hr";i:2;s:3:"hrv";}s:7:"strings";a:1:{s:8:"continue";s:7:"Nastavi";}}s:5:"hu_HU";a:8:{s:8:"language";s:5:"hu_HU";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-07 11:10:15";s:12:"english_name";s:9:"Hungarian";s:11:"native_name";s:6:"Magyar";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/hu_HU.zip";s:3:"iso";a:2:{i:1;s:2:"hu";i:2;s:3:"hun";}s:7:"strings";a:1:{s:8:"continue";s:7:"Tovább";}}s:5:"id_ID";a:8:{s:8:"language";s:5:"id_ID";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-17 05:06:14";s:12:"english_name";s:10:"Indonesian";s:11:"native_name";s:16:"Bahasa Indonesia";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/id_ID.zip";s:3:"iso";a:2:{i:1;s:2:"id";i:2;s:3:"ind";}s:7:"strings";a:1:{s:8:"continue";s:9:"Lanjutkan";}}s:5:"it_IT";a:8:{s:8:"language";s:5:"it_IT";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 09:00:58";s:12:"english_name";s:7:"Italian";s:11:"native_name";s:8:"Italiano";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/it_IT.zip";s:3:"iso";a:2:{i:1;s:2:"it";i:2;s:3:"ita";}s:7:"strings";a:1:{s:8:"continue";s:8:"Continua";}}s:2:"ja";a:8:{s:8:"language";s:2:"ja";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-05 01:40:32";s:12:"english_name";s:8:"Japanese";s:11:"native_name";s:9:"日本語";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/ja.zip";s:3:"iso";a:1:{i:1;s:2:"ja";}s:7:"strings";a:1:{s:8:"continue";s:9:"続ける";}}s:5:"ko_KR";a:8:{s:8:"language";s:5:"ko_KR";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-04 02:56:59";s:12:"english_name";s:6:"Korean";s:11:"native_name";s:9:"한국어";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/ko_KR.zip";s:3:"iso";a:2:{i:1;s:2:"ko";i:2;s:3:"kor";}s:7:"strings";a:1:{s:8:"continue";s:6:"계속";}}s:5:"my_MM";a:8:{s:8:"language";s:5:"my_MM";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-21 19:07:31";s:12:"english_name";s:7:"Burmese";s:11:"native_name";s:15:"ဗမာစာ";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/my_MM.zip";s:3:"iso";a:2:{i:1;s:2:"my";i:2;s:3:"mya";}s:7:"strings";a:1:{s:8:"continue";s:54:"ဆက်လက်လုပ်ေဆာင်ပါ။";}}s:5:"nb_NO";a:8:{s:8:"language";s:5:"nb_NO";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-10 16:35:13";s:12:"english_name";s:19:"Norwegian (Bokmål)";s:11:"native_name";s:13:"Norsk bokmål";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/nb_NO.zip";s:3:"iso";a:2:{i:1;s:2:"nb";i:2;s:3:"nob";}s:7:"strings";a:1:{s:8:"continue";s:8:"Fortsett";}}s:5:"nl_NL";a:8:{s:8:"language";s:5:"nl_NL";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-09 07:20:46";s:12:"english_name";s:5:"Dutch";s:11:"native_name";s:10:"Nederlands";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/nl_NL.zip";s:3:"iso";a:2:{i:1;s:2:"nl";i:2;s:3:"nld";}s:7:"strings";a:1:{s:8:"continue";s:8:"Doorgaan";}}s:5:"pl_PL";a:8:{s:8:"language";s:5:"pl_PL";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-09 15:11:56";s:12:"english_name";s:6:"Polish";s:11:"native_name";s:6:"Polski";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/pl_PL.zip";s:3:"iso";a:2:{i:1;s:2:"pl";i:2;s:3:"pol";}s:7:"strings";a:1:{s:8:"continue";s:9:"Kontynuuj";}}s:5:"pt_PT";a:8:{s:8:"language";s:5:"pt_PT";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-02 18:49:32";s:12:"english_name";s:21:"Portuguese (Portugal)";s:11:"native_name";s:10:"Português";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/pt_PT.zip";s:3:"iso";a:1:{i:1;s:2:"pt";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuar";}}s:5:"pt_BR";a:8:{s:8:"language";s:5:"pt_BR";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-06 15:59:30";s:12:"english_name";s:19:"Portuguese (Brazil)";s:11:"native_name";s:20:"Português do Brasil";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/pt_BR.zip";s:3:"iso";a:2:{i:1;s:2:"pt";i:2;s:3:"por";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuar";}}s:5:"ro_RO";a:8:{s:8:"language";s:5:"ro_RO";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 08:06:17";s:12:"english_name";s:8:"Romanian";s:11:"native_name";s:8:"Română";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/ro_RO.zip";s:3:"iso";a:2:{i:1;s:2:"ro";i:2;s:3:"ron";}s:7:"strings";a:1:{s:8:"continue";s:9:"Continuă";}}s:5:"ru_RU";a:8:{s:8:"language";s:5:"ru_RU";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-04 23:12:49";s:12:"english_name";s:7:"Russian";s:11:"native_name";s:14:"Русский";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/ru_RU.zip";s:3:"iso";a:2:{i:1;s:2:"ru";i:2;s:3:"rus";}s:7:"strings";a:1:{s:8:"continue";s:20:"Продолжить";}}s:5:"sk_SK";a:8:{s:8:"language";s:5:"sk_SK";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-19 09:33:53";s:12:"english_name";s:6:"Slovak";s:11:"native_name";s:11:"Slovenčina";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/sk_SK.zip";s:3:"iso";a:2:{i:1;s:2:"sk";i:2;s:3:"slk";}s:7:"strings";a:1:{s:8:"continue";s:12:"Pokračovať";}}s:5:"sl_SI";a:8:{s:8:"language";s:5:"sl_SI";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 07:31:14";s:12:"english_name";s:9:"Slovenian";s:11:"native_name";s:13:"Slovenščina";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/sl_SI.zip";s:3:"iso";a:2:{i:1;s:2:"sl";i:2;s:3:"slv";}s:7:"strings";a:1:{s:8:"continue";s:10:"Nadaljujte";}}s:5:"sr_RS";a:8:{s:8:"language";s:5:"sr_RS";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-18 19:08:01";s:12:"english_name";s:7:"Serbian";s:11:"native_name";s:23:"Српски језик";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/sr_RS.zip";s:3:"iso";a:2:{i:1;s:2:"sr";i:2;s:3:"srp";}s:7:"strings";a:1:{s:8:"continue";s:14:"Настави";}}s:5:"sv_SE";a:8:{s:8:"language";s:5:"sv_SE";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-18 13:39:48";s:12:"english_name";s:7:"Swedish";s:11:"native_name";s:7:"Svenska";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/sv_SE.zip";s:3:"iso";a:2:{i:1;s:2:"sv";i:2;s:3:"swe";}s:7:"strings";a:1:{s:8:"continue";s:9:"Fortsätt";}}s:2:"th";a:8:{s:8:"language";s:2:"th";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-18 16:15:24";s:12:"english_name";s:4:"Thai";s:11:"native_name";s:9:"ไทย";s:7:"package";s:59:"https://downloads.wordpress.org/translation/core/4.1/th.zip";s:3:"iso";a:2:{i:1;s:2:"th";i:2;s:3:"tha";}s:7:"strings";a:1:{s:8:"continue";s:15:"ต่อไป";}}s:5:"tr_TR";a:8:{s:8:"language";s:5:"tr_TR";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-10 11:11:55";s:12:"english_name";s:7:"Turkish";s:11:"native_name";s:8:"Türkçe";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/tr_TR.zip";s:3:"iso";a:2:{i:1;s:2:"tr";i:2;s:3:"tur";}s:7:"strings";a:1:{s:8:"continue";s:5:"Devam";}}s:5:"zh_CN";a:8:{s:8:"language";s:5:"zh_CN";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2014-12-26 02:21:02";s:12:"english_name";s:15:"Chinese (China)";s:11:"native_name";s:12:"简体中文";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/zh_CN.zip";s:3:"iso";a:2:{i:1;s:2:"zh";i:2;s:3:"zho";}s:7:"strings";a:1:{s:8:"continue";s:6:"继续";}}s:5:"zh_TW";a:8:{s:8:"language";s:5:"zh_TW";s:7:"version";s:3:"4.1";s:7:"updated";s:19:"2015-01-08 03:46:32";s:12:"english_name";s:16:"Chinese (Taiwan)";s:11:"native_name";s:12:"繁體中文";s:7:"package";s:62:"https://downloads.wordpress.org/translation/core/4.1/zh_TW.zip";s:3:"iso";a:2:{i:1;s:2:"zh";i:2;s:3:"zho";}s:7:"strings";a:1:{s:8:"continue";s:6:"繼續";}}}', 'yes'); -- -------------------------------------------------------- -- -- Table structure for table `wp_postmeta` -- CREATE TABLE IF NOT EXISTS `wp_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=14 ; -- -- Dumping data for table `wp_postmeta` -- INSERT INTO `wp_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES (1, 2, '_wp_page_template', 'default'), (2, 4, '_wp_attached_file', '2015/01/d5-corporate-extend.zip'), (3, 4, '_wp_attachment_context', 'upgrader'), (4, 5, '_wp_attached_file', '2015/01/Shovel-Roof-Snow.jpg'), (5, 5, '_wp_attachment_metadata', 'a:5:{s:5:"width";i:1164;s:6:"height";i:651;s:4:"file";s:28:"2015/01/Shovel-Roof-Snow.jpg";s:5:"sizes";a:5:{s:9:"thumbnail";a:4:{s:4:"file";s:28:"Shovel-Roof-Snow-150x150.jpg";s:5:"width";i:150;s:6:"height";i:150;s:9:"mime-type";s:10:"image/jpeg";}s:6:"medium";a:4:{s:4:"file";s:28:"Shovel-Roof-Snow-300x168.jpg";s:5:"width";i:300;s:6:"height";i:168;s:9:"mime-type";s:10:"image/jpeg";}s:5:"large";a:4:{s:4:"file";s:29:"Shovel-Roof-Snow-1024x573.jpg";s:5:"width";i:1024;s:6:"height";i:573;s:9:"mime-type";s:10:"image/jpeg";}s:14:"post-thumbnail";a:4:{s:4:"file";s:28:"Shovel-Roof-Snow-672x372.jpg";s:5:"width";i:672;s:6:"height";i:372;s:9:"mime-type";s:10:"image/jpeg";}s:25:"twentyfourteen-full-width";a:4:{s:4:"file";s:29:"Shovel-Roof-Snow-1038x576.jpg";s:5:"width";i:1038;s:6:"height";i:576;s:9:"mime-type";s:10:"image/jpeg";}}s:10:"image_meta";a:11:{s:8:"aperture";i:0;s:6:"credit";s:4:"Main";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";i:1419582143;s:9:"copyright";s:0:"";s:12:"focal_length";i:0;s:3:"iso";i:0;s:13:"shutter_speed";i:0;s:5:"title";s:0:"";s:11:"orientation";i:0;}}'), (6, 5, '_edit_lock', '1420986999:1'), (7, 5, '_edit_last', '1'), (8, 6, '_edit_last', '1'), (9, 6, '_edit_lock', '1420987822:1'), (10, 6, '_wp_page_template', 'page-templates/contributors.php'), (11, 8, '_edit_last', '1'), (12, 8, '_edit_lock', '1420988304:1'), (13, 8, '_wp_page_template', 'default'); -- -------------------------------------------------------- -- -- Table structure for table `wp_posts` -- CREATE TABLE IF NOT EXISTS `wp_posts` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_author` bigint(20) unsigned NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext NOT NULL, `post_title` text NOT NULL, `post_excerpt` text NOT NULL, `post_status` varchar(20) NOT NULL DEFAULT 'publish', `comment_status` varchar(20) NOT NULL DEFAULT 'open', `ping_status` varchar(20) NOT NULL DEFAULT 'open', `post_password` varchar(20) NOT NULL DEFAULT '', `post_name` varchar(200) NOT NULL DEFAULT '', `to_ping` text NOT NULL, `pinged` text NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `guid` varchar(255) NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`ID`), KEY `post_name` (`post_name`), KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), KEY `post_parent` (`post_parent`), KEY `post_author` (`post_author`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=10 ; -- -- Dumping data for table `wp_posts` -- INSERT INTO `wp_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES (1, 1, '2013-10-25 02:18:59', '2013-10-25 02:18:59', 'Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2013-10-25 02:18:59', '2013-10-25 02:18:59', '', 0, 'http://delawarecountypublicadjuster.com/?p=1', 0, 'post', '', 1), (2, 1, '2013-10-25 02:18:59', '2013-10-25 02:18:59', 'This is an example page. It''s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:\n\nHi there! I''m a bike messenger by day, aspiring actor by night, and this is my blog. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin'' caught in the rain.)\n\n...or something like this:\n\n
The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.\n\nAs a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!', 'Sample Page', '', 'publish', 'open', 'open', '', 'sample-page', '', '', '2013-10-25 02:18:59', '2013-10-25 02:18:59', '', 0, 'http://delawarecountypublicadjuster.com/?page_id=2', 0, 'page', '', 0), (7, 1, '2015-01-11 14:41:37', '2015-01-11 14:41:37', 'Water Damage\r\n\r\nWater Damage\r\n\r\nWater Damage\r\n\r\nWater Damage\r\n\r\nWater Damage', 'Water Damage', '', 'inherit', 'open', 'open', '', '6-revision-v1', '', '', '2015-01-11 14:41:37', '2015-01-11 14:41:37', '', 6, 'http://delawarecountypublicadjuster.com/?p=7', 0, 'revision', '', 0), (4, 1, '2015-01-11 14:23:01', '2015-01-11 14:23:01', 'http://delawarecountypublicadjuster.com/wp-content/uploads/2015/01/d5-corporate-extend.zip', 'd5-corporate-extend.zip', '', 'private', 'open', 'open', '', 'd5-corporate-extend-zip', '', '', '2015-01-11 14:23:01', '2015-01-11 14:23:01', '', 0, 'http://delawarecountypublicadjuster.com/wp-content/uploads/2015/01/d5-corporate-extend.zip', 0, 'attachment', '', 0), (5, 1, '2015-01-11 14:37:43', '2015-01-11 14:37:43', '', 'Shovel Roof Snow', '', 'inherit', 'open', 'open', '', 'shovel-roof-snow', '', '', '2015-01-11 14:38:35', '2015-01-11 14:38:35', '', 0, 'http://delawarecountypublicadjuster.com/wp-content/uploads/2015/01/Shovel-Roof-Snow.jpg', 0, 'attachment', 'image/jpeg', 1), (6, 1, '2015-01-11 14:41:37', '2015-01-11 14:41:37', 'Water Damage\r\n\r\nWater Damage\r\n\r\nWater Damage\r\n\r\nWater Damage\r\n\r\nWater Damage', 'Water Damage', '', 'publish', 'open', 'open', '', 'water-damage', '', '', '2015-01-11 14:52:42', '2015-01-11 14:52:42', '', 0, 'http://delawarecountypublicadjuster.com/?page_id=6', 0, 'page', '', 0), (8, 1, '2015-01-11 15:00:07', '2015-01-11 15:00:07', 'Wind Damage\r\n\r\nWind Damage\r\n\r\nWind Damage\r\n\r\nWind Damage\r\n\r\nWind Damage', 'Wind Damage', '', 'publish', 'open', 'open', '', 'wind-damage', '', '', '2015-01-11 15:00:07', '2015-01-11 15:00:07', '', 0, 'http://delawarecountypublicadjuster.com/?page_id=8', 0, 'page', '', 0), (9, 1, '2015-01-11 15:00:07', '2015-01-11 15:00:07', 'Wind Damage\r\n\r\nWind Damage\r\n\r\nWind Damage\r\n\r\nWind Damage\r\n\r\nWind Damage', 'Wind Damage', '', 'inherit', 'open', 'open', '', '8-revision-v1', '', '', '2015-01-11 15:00:07', '2015-01-11 15:00:07', '', 8, 'http://delawarecountypublicadjuster.com/8-revision-v1/', 0, 'revision', '', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_terms` -- CREATE TABLE IF NOT EXISTS `wp_terms` ( `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(200) NOT NULL DEFAULT '', `slug` varchar(200) NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0', PRIMARY KEY (`term_id`), KEY `name` (`name`), KEY `slug` (`slug`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=6 ; -- -- Dumping data for table `wp_terms` -- INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES (1, 'Uncategorized', 'uncategorized', 0), (2, 'Public Adjuster Water Damage Delaware County', 'public-adjuster-water-damage-delaware-county', 0), (3, 'Public Adjuster Wind Damage Delaware County', 'public-adjuster-wind-damage-delaware-county', 0), (4, 'Public Adjuster Hail Damage Delaware County', 'public-adjuster-hail-damage-delaware-county', 0), (5, 'Public Adjuster Fire Damage Delaware County', 'public-adjuster-fire-damage-delaware-county', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_term_relationships` -- CREATE TABLE IF NOT EXISTS `wp_term_relationships` ( `object_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`object_id`,`term_taxonomy_id`), KEY `term_taxonomy_id` (`term_taxonomy_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `wp_term_relationships` -- INSERT INTO `wp_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES (1, 1, 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_term_taxonomy` -- CREATE TABLE IF NOT EXISTS `wp_term_taxonomy` ( `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `taxonomy` varchar(32) NOT NULL DEFAULT '', `description` longtext NOT NULL, `parent` bigint(20) unsigned NOT NULL DEFAULT '0', `count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`term_taxonomy_id`), UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), KEY `taxonomy` (`taxonomy`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=6 ; -- -- Dumping data for table `wp_term_taxonomy` -- INSERT INTO `wp_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES (1, 1, 'category', '', 0, 1), (2, 2, 'category', 'If you are a Delaware County resident or business owner and have sustained water damage, then we are your Delaware County Public Adjuster. Competitive Fees 5-20%. CALL (215) 364-4546', 0, 0), (3, 3, 'category', 'If you are a Delaware County resident or business owner and have sustained wind damage, then we are your Delaware County Public Adjuster. Competitive Fees 5-20%. CALL (215) 364-4546', 0, 0), (4, 4, 'category', 'If you are a Delaware County resident or business owner and have sustained hail damage, then we are your Delaware County Public Adjuster. Competitive Fees 5-20%. CALL (215) 364-4546', 0, 0), (5, 5, 'category', 'If you are a Delaware County resident or business owner and have sustained fire damage, then we are your Delaware County Public Adjuster. Competitive Fees 5-10%. CALL (215) 364-4546', 0, 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_usermeta` -- CREATE TABLE IF NOT EXISTS `wp_usermeta` ( `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext, PRIMARY KEY (`umeta_id`), KEY `user_id` (`user_id`), KEY `meta_key` (`meta_key`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=18 ; -- -- Dumping data for table `wp_usermeta` -- INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (1, 1, 'first_name', 'Rick'), (2, 1, 'last_name', 'Kinney'), (3, 1, 'nickname', 'admin'), (4, 1, 'description', ''), (5, 1, 'rich_editing', 'true'), (6, 1, 'comment_shortcuts', 'false'), (7, 1, 'admin_color', 'light'), (8, 1, 'use_ssl', '0'), (9, 1, 'show_admin_bar_front', 'true'), (10, 1, 'wp_capabilities', 'a:1:{s:13:"administrator";b:1;}'), (11, 1, 'wp_user_level', '10'), (12, 1, 'dismissed_wp_pointers', 'wp330_toolbar,wp330_saving_widgets,wp340_choose_image_from_library,wp340_customize_current_theme_link,wp350_media,wp360_revisions,wp360_locks,wp390_widgets,wp410_dfw'), (13, 1, 'show_welcome_panel', '1'), (14, 1, 'wp_dashboard_quick_press_last_post_id', '3'), (15, 1, 'session_tokens', 'a:2:{s:64:"0e10285c9964f72cecb0e63ff877c3765717f5e98e4e21af43ece53680376ca5";a:1:{s:10:"expiration";i:1421158413;}s:64:"08736fbd433126a8d3025b4f2e0aa1c2dfd0e04a11c441cb10cc5c93295ad159";a:4:{s:10:"expiration";i:1421160697;s:2:"ip";s:12:"71.123.44.27";s:2:"ua";s:101:"Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36";s:5:"login";i:1420987897;}}'), (16, 1, 'wp_user-settings', 'libraryContent=browse'), (17, 1, 'wp_user-settings-time', '1420987073'); -- -------------------------------------------------------- -- -- Table structure for table `wp_users` -- CREATE TABLE IF NOT EXISTS `wp_users` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_login` varchar(60) NOT NULL DEFAULT '', `user_pass` varchar(64) NOT NULL DEFAULT '', `user_nicename` varchar(50) NOT NULL DEFAULT '', `user_email` varchar(100) NOT NULL DEFAULT '', `user_url` varchar(100) NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(60) NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT '0', `display_name` varchar(250) NOT NULL DEFAULT '', PRIMARY KEY (`ID`), KEY `user_login_key` (`user_login`), KEY `user_nicename` (`user_nicename`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=2 ; -- -- Dumping data for table `wp_users` -- INSERT INTO `wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES (1, 'admin', '$P$B3MLmo0x1tVngBqhT54aGtkLf5Q9ZE0', 'admin', 'admin@delawarecountypublicadjuster.com', 'http://www.delawarecountypublicadjuster.com', '2013-10-25 02:18:59', '', 0, 'admin'); /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
