![\"cover\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/cover.png\")
Did you know that WordPress users in Japan have meetups dedicated just to eating crab in the Fukui prefecture? WP Tavern has has a fantastic article on Community, Translation, and Wapuu: How Japan is Shaping WordPress History. There is so much that is quotable, just check out the entire thing!
\";s: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, 25 May 2015 22:53: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: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:27:\"Matt: Bosworth says Be Kind\";s:7:\"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=45093\";s:7:\"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/05/bosworth-says-be-kind/\";s: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:361:\"Andrew Bosworth, one of the early engineers and leaders at Facebook tells the story about how he almost got fired in the early days despite being a top engineer. “If I was a good engineer, why would it be hard to work with me? Of course that question was the very foundation of my problem.”
\";s: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, 24 May 2015 23:45: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: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:50:\"Andrew Nacin: Smarter algorithms, smarter defaults\";s:7:\"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:24:\"http://nacin.com/?p=4329\";s:7:\"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:\"http://nacin.com/2015/05/24/smart-algorithms-defaults/\";s: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:961:\"\nInstead of showing the user an alert that something might not work, maybe we can build a smarter algorithm. Instead of asking the user to make a choice up front, maybe we can set a smart default and see if there is high demand after launch for more customization.
— Rebecca Rolfe on the Google Chrome team, interviewed in The Badass Women of Chrome’s Security Team in Refinery29.
\n(More on making decisions, not options.)
\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:\"Sun, 24 May 2015 23:11:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Andrew Nacin\";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:24:\"Matt: Soaring SV Housing\";s:7:\"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=45090\";s:7:\"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:40:\"http://ma.tt/2015/05/soaring-sv-housing/\";s: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:277:\"\nTalent is leaving Silicon Valley because of high real estate costs. Today, the median price for a home just exceeded $1 million.
Why one in four Silicon Valley homebuyers wants to leave. Yep.
\";s: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, 24 May 2015 01:38: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: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:23:\"Matt: TC on Apple Watch\";s:7:\"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=45087\";s:7:\"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/2015/05/tc-on-apple-watch/\";s: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:\"The John Biggs article on Why I’m Still Wearing My Apple Watch almost perfectly describes how I’m feeling about the watch right now. It is a very personal device, I’ve gotten attached to the little fellow, and I should probably start selling all my mechanical watches.
\";s: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, 23 May 2015 00:55:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:100:\"WPTavern: Cover: A Minimalist Blogging Theme for WordPress, Featuring Support for Aesop Story Engine\";s:7:\"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=44165\";s:7:\"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:110:\"http://wptavern.com/cover-a-minimalistic-blogging-theme-for-wordpress-featuring-support-for-aesop-story-engine\";s: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:3410:\"If you’re looking to bring your blog’s design back to the bare bones of pure content without distractions, then the new Cover theme may be a good option. Cover brings blogging minimalism to a new level. After less than a month on WordPress.org, it has already been downloaded more than 2,500 times.
\n
Cover was created by new WordPress.org theme author Paul Eiche and is based on the popular Underscores starter theme maintained by Automattic.
\nThe theme’s simple, single-column design is accented by support for full-width featured images. It was bundled with Font Awesome to allow users to easily add scalable vector icons to any content or social menu. Cover incorporates the lightweight Headroom.js script for hiding your header until it’s needed. It also includes skrollr.js, a stand-alone parallax scrolling library for mobile (Android + iOS) and desktop.
\nCover’s widgets and menus are optional and hidden behind an full-screen overlay triggered by the hamburger icon. This keeps the focus on your content while offering plenty of space for unlimited widgets in the overlay.
\n![\"Cover\'s](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/cover-overlay.jpg\")
Cover’s overlay for widgets and menus\nCover supports one regular navigation menu, one for social media, and an additional social menu in the footer. If you’re using Jetpack’s Infinite Scrolling module, the theme will actually detect whether or not the footer social menu is present and respond accordingly.
\nThe theme was built to make a nice accompaniment to sites using the Aesop Story Engine plugin, although it’s not required. When used with the plugin, content can expand to full-width when using components such as images, galleries, maps, etc.
\nIf you’re a developer wanting to modify the theme, you’ll find that Cover’s stylesheet is compressed. It was built with Sass and the /sass directory includes all the necessary components for compiling the stylesheet.
\nCover is a beautifully responsive theme that presents your website in a bold way on any device. Its minimalist design supports your content instead of upstaging it with the clutter of widgets and navigation. Check out a live demo on the theme’s project page to see it in action. Cover is available for free 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:\"Fri, 22 May 2015 23:15:58 +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: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:94:\"WPTavern: Hello Security Plugin Aims to Educate WordPress Users on Web Security Best Practices\";s:7:\"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=44205\";s:7:\"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/hello-security-plugin-aims-to-educate-wordpress-users-on-web-security-best-practices\";s: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:4532:\"Hello Security is a new plugin developed by Michele Butcher that displays security tips and reminders in the WordPress backend. It’s a fork of Hello Dolly and Butcher’s first plugin submitted to the plugin directory.
\n![\"Hello](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/HelloSecurityTips.png\")
Hello Security Tips\nSecurity best practices include PASSWORD is never a good password, backup all the things, and only give users the access they need. A full list of the tips used is located within the hello-security.php file.
\nFor years, Butcher has avoided learning how to code. Thanks to a WordCamp session and inspirational members of the WordPress community, she now has a plugin of her own. In this short interview, we find out what held her back from developing plugins sooner and who inspired her to go through the process.
\nWhat held you back from writing your first plugin?
\nFor the longest time, I didn’t want to learn how to code. I was a firm believer in that there’s a plugin for everything. Once I was motivated enough to create one, I didn’t know what to create first.
\nI have ideas for the types of plugins I want to make but I always find three plugins with similar functionality. The first WordPress plugin I’ve ever looked at the code for is Better WP Security, developed by Chris Wiegman that eventually turned into iThemes Security.
\nI knew I would have to dig deep into learning code before I could write a plugin that large. I discovered the best way to learn code is to jump in and read actively developed code. Once I became comfortable reading code, I started to get ideas on plugins to create.
\nWhat motivated you enough to go through with creating and releasing your first plugin?
\nI subconsciously kept telling myself to just make something. I eventually decided to get into plugin development and taking the first step was the hardest. I bounced ideas off of friends for a long time before I jumped in and just made one.
\nAt WordCamp North Canton, I attended Topher DeRosia’s session, Introduction to WordPress Plugin Development. After the session was over, I realized I didn’t have to make something that has thousands of lines of code. I brainstormed ideas, thinking how I could use Hello Dolly.
\nWhat inspired you to write Hello Security?
\nThe first idea that came to mind in using Hello Dolly was not security related. I initially thought of doing something fun like Hello Jovi (Bon Jovi lyrics) or Hello Marvel where I use awesome one liners from the various Marvel movies. Iron Man quotes alone would have given me at least 30 lines to work with.
\nI decided against doing something fun and make something that could be useful. Many of the quotes in Hello Security are things I say at all of my talks, tell every client after I clean their site, and mention to everyone who is getting into WordPress.
\nHello Security is there to help those who are either new to WordPress or might not know how or why they should keep their site secure. It is a way to be proactive before something bad happens. Wiegman and DeRosia inspired me the most and I’m glad they did.
\nHello Security is a good plugin that educates users on best practices related to web security without overwhelming them with information. I tested Hello Security on WordPress 4.2.2 and didn’t experience any issues. It’s available for free on WordPress.org and GitHub. Butcher encourages those who want to see a security tip added to submit a pull request on GitHub.
\";s: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 May 2015 21:24: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:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: How WordPress Business Owners are Benefiting from Publicly Sharing Revenue Stats\";s:7:\"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=44207\";s:7:\"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:100:\"http://wptavern.com/how-wordpress-business-owners-are-benefiting-from-publicly-sharing-revenue-stats\";s: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:4890:\"In light of Automattic’s recent acquisition of WooCommerce (and all of WooThemes), estimated to be in the range of $30M, WordPress business owners have been infused with a fresh perspective of the value and potential in creating strong GPL-licensed products.
\nAutomattic’s acquisition of Woo, colloquially referred to as the “WooMattic” deal, is the company’s first major purchase within the WordPress ecosystem since BuddyPress in 2007.
\n\n\nPerhaps most interesting: Woo is Automattic\'s first acquisition of a WP ecosystem product since BuddyPress (2007) http://t.co/AJ1CIPS9Nc
\n— Andrew Nacin (@nacin) May 20, 2015
The business model that brought WooCommerce to success is a free base product with a marketplace of commercial extensions. This revenue model currently drives the success of many of the top products in the WordPress ecosystem and is also proving to be effective for new businesses looking to quickly establish a user base.
\nThis morning, WordPress developer Scott Bolinger published a compilation of 2015 WordPress business revenue statistics based on publicly available transparency reports and figures submitted by business owners. The resource includes each company’s business model, description, and monthly/yearly revenue.
\n![\"wordpress-business-revenue\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/wordpress-business-revenue.png\")
Bolinger is planning to use this information in an upcoming presentation and will be keeping the resource up to date with new submissions and figures as they roll in.
\nTransparency reports from WordPress businesses, ranging from small to large, have been popping up frequently over the past year, as owners are surprisingly eager to share their progress and receive feedback from the community. These kinds of reports are not unique to the WordPress ecosystem, but they do seem to complement the spirit of adventure that is common among open source product developers.
\nZack Katz, co-founder of GravityView, remarked on his motivation to share the company’s revenue publicly.
\n“I think sharing revenue humanizes GravityView: we’re not a nameless corporation where you put in money and somehow good products and customer service come out,” he said. “Our customers are part of an interaction: their purchase of a support license directly allows us to develop the product and help them do great things with their websites.”
\nKatz hopes that the resource will be inspirational for WordPress entrepreneurs who are just getting started.
\n\nThe WordPress community is slowly realizing that businesses don’t have to be cutthroat black boxes to succeed. As more people and businesses share and open up, we’re redefining what it means to be a business in the WordPress ecosystem. I think this leads to lower barriers to entry for others to participate. By sharing GravityView’s numbers and some of the things I’ve learned, I hope others are better informed and inspired to join our community.
Nick Haskins, founder of Aesop Interactive, is currently in the midst of active experimentation with his products and business model and recently published a transparency report for his 15-month old company. He believes that these kinds of reports are important for demonstrating the types of products and pricing models that can be successful.
\n“I think for Aesopinteractive it’s showing that you can still abide by WordPress theme best practices, and be successful at selling WordPress themes as add-ons at $129 each with 3-5 options and no functionality,” Haskins said.
\n“Plus, I really hope it motivates other ‘small timers’ to share numbers as well, and be held accountable for our growth. It’s a lot like sharing your goals publicly, and letting people hold you accountable for it. Sink or swim, the lessons will be valuable either 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 22 May 2015 20:11:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"WPTavern: WPWeekly Episode 193 – WooMattic\";s:7:\"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=44199&preview_id=44199\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"http://wptavern.com/wpweekly-episode-193-woomattic\";s: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:3179:\"In this episode of WordPress Weekly, Marcus Couch and I break down Automattic’s acquisition of WooThemes and discuss the future of WooCommerce. We discuss how the Japanese WordPress community influences WordPress development. Last but not least, we debate the merits of using an honor system for commercial plugins.
\nAutomattic Acquires WooThemes
\nWordPress.org is Testing International Theme and Plugin Directories
\nCommunity, Translation, and Wapuu: How Japan is Shaping WordPress History
\nLasso Frontend Editing Plugin for WordPress Now Available on GitHub
\ncPanel’s Site Software Addon Disables WordPress Auto Updates
\nAll Sessions from LoopConf Now Available on YouTube
Simply Pinterest adds a Pin It button call to action over each image in your post to prompt visitors to Pin your content. You can customize how the plugin is applied to your site with counts, colors and many other settings.
\nI wanted to highlight this plugin because it’s the first from Terry Ann Swallow. Terry has been active in WordPress since 2006 but this is her first plugin, and it’s good. We often forget to recognize first time plugin contributors, and I want to recognize Terry and wish her well with this plugin and many more to follow.
\nNew Facebook Comments makes it simple to add the Facebook comments system to WordPress. You can also insert the comment box as a shortcode into any post, page or theme.
\nSimple Project Manager lets you manage projects, clients, tasks, and create invoices in PDF format. It also gives you the ability to run reports about projects, clients, tasks and invoices.
\nNext Episode: Wednesday, May 27th 4:00 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 #193:
\n
Emily Guendelsberger went undercover as an UberX driver in Philadelphia and wrote about the experience, particularly the economics of it. It’s a pretty fascinating and gripping longread, both in its content and it’s just well-written.
\";s: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 May 2015 05:29: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:10;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:79:\"WPTavern: Hookr Enters Beta with New UI and Support for 800+ Plugins and Themes\";s:7:\"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=44167\";s:7:\"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:88:\"http://wptavern.com/hookr-enters-beta-with-new-ui-and-support-for-800-plugins-and-themes\";s: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:9212:\"![\"hookr-featured\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/hookr-featured.jpg\")
Last April, Christopher Sanford launched Hookr, a WordPress hook/API reference for developers. He initially wrote the parser/indexer for his own use, to improve efficiency in his work, and was inspired to make it a public resource.
\n“I have been professionally working with WordPress since 2.8, but most of which I would describe as ‘superficial development,\'” Sanford said. “It wasn’t until later, roughly WordPress 3.5, that a large-scale WordPress project came along.
\n“I found myself spending an obscene amount of time either digging through code within my IDE, or performing countless Google searches, in order to uncover/understand various hooks, functions, constants etc. So, I wrote a plugin that would index the application/site it was installed within– this was the first iteration of Hookr.”
\nAs a developer whose career is not based in the WordPress ecosystem, Sanford didn’t know what to expect when he tested the waters with his new public resource for developers. After several months in alpha, the traffic and feedback were enough to convince him to invest in performance improvements and an overhaul of the UI.
\n“The alpha version of the site was truly alpha – the UI was a complete afterthought, there were many UI bugs/hiccups, the navigation was not cohesive; it was a hot mess,” Sanford said. “Prior to the beta, I had not updated hookr.io for months, which was purposeful. I wanted to see if the traffic would completely level-off, or if it would remain consistent, with the latter being the determining factor as to whether or not I would continue with the project.”
\nSanford was surprised and encouraged to find that usage of the site was solid and continued to grow. He spent the next three months fixing issues, rewriting core parts of the parser, and refining the UI to focus on features that people actually needed. The site has now entered beta with a slew of noteworthy improvements:
\nIndex screens are infinitely-scrollable and filterable, which cuts down on a lot of clicking through endless pagination. Hook details have been refined to follow a format similar to PHP’s detail pages and include annotated code signatures and descriptions.
\n![\"hookr-annotated-descriptions\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/hookr-annotated-descriptions.png\")
In addition to the basic info about the file and lines where the code/object is defined, Hookr has also been updated to display any related hook callbacks sharing the same tag name or signature.
\n![\"hookr-relations\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/hookr-relations.png\")
Usage examples for every action, filter, function, and constant can now be easily copied. Users can also quickly view source code with Hookr’s new hyperlinked and annotated source code blocks.
\nMany of those in search of a comprehensive hook/API reference find Hookr to be easier to use than the official WordPress.org code reference. Sanford has experienced friction from creating what some perceive to be a competing resource.
\n\nThere were several people that have/had an issue with the resource even existing. For the sake of full-disclosure, my career is outside the WordPress ecosystem; it is simply a platform I use (and love), not a lifestyle.
\nMy experience with the ‘community’ has been mostly positive; many people love the resource, while others are indifferent. I wrote Hookr to aid legit designers/developers/agencies, not hobbyists masquerading as designers/developers who have no skill besides martyrdom and nothing positive to contribute.
The Hookr name has also proven to be controversial, as a few vocal opponents find it to be off-putting and offensive. Sanford said that he is very much torn over rebranding the site but is open to the idea.
\n“The WordPress market is saturated – it is hard to make any sort of impact, hence the name,” he said. “The name is short, controversial, relevant, and memorable – either people love or hate it, of course. It was never the intent to insult, offend, or alienate any demographic.
\n“If people are uncomfortable saying “Hookr” in an open forum, then maybe it’s time to put my personal ethos aside for the betterment of the resource. That being said, I am on the fence in regards to renaming/rebranding Hookr. If I do, it’s only to remove the initial barrier/stigma and promote usage.”
\nAs the site is still in beta, Sanford is still collecting feedback from users but is concentrating on features, fixes, and SEO. If he decides to rebrand, it will likely happen as the site moves out of beta.
\nAfter streamlining the design, removing a few features that no one used, and refining those that worked, Sanford reports that so far users are enjoying the beta version of Hookr.
\n“The feedback I have received has been exceedingly positive,” he said. “The usage has effectively doubled.” User suggestions regarding the search functionality are shaping the roadmap for the next iteration of the resource.
\n“The current search implementation is more or less a filter mechanism, which is effective once you’ve drilled-down to the relevant index,” Sanford said. “However, numerous users have asked for a traditional ‘global’ keyword search that spans core, plugins, and themes. The global search, along with a few other features, will be released within the next month or so.”
\nWhile Sanford is committed to keeping the resource free for anyone to use, he is exploring a few long term options for monetization.
\n“Cluttering the interface with ads is not something I want to do, but never say never,” he said. “However, there is another opportunity for monetization.”
\nIn the future, Sanford is looking at the possibility of establishing the infrastructure to offer Hookr (SaaS) for commercial theme and plugin developers.
\n\nWhen I released Hookr Alpha, a few people inquired about using it to augment the documentation of their premium plugin/theme. I wasn’t confident that it was a true ‘value-add.’ Over the course of a year, I’ve refined the parser and data objects to a point of viability.
\nThe Hookr Parser analyzes source code, which is then reconciled against the inline documentation describing it; often times, the inline documentation is either missing or is erroneous. Jeff Matson and I discussed these issues and decided that Hookr would be invaluable if it could identify these issues, which it now does.
A SaaS model for monetization would allow Sanford to offer developers pre-generated documentation with their themes/plugins. He is also exploring the possibility of offering the raw data in JSON, XML, CSV, etc. to vendors to implement an API microsite.
\nFor the time being, Sanford will continue investing time into improving Hookr as a reference and refining features according to user feedback. If you use Hookr.io regularly, feel free to offer your suggestions in the comments and follow the project on Twitter for all the latest updates.
\";s: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, 21 May 2015 20:05:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:26:\"Matt: William Zinsser Obit\";s:7:\"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=45066\";s:7:\"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/05/william-zinsser-obit/\";s: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:515:\"\nMr. Zinsser was a prolific author, editor and teacher, but it was his role as an arbiter of good writing that resonated widely and deeply.
The New York Times obituary of William Zinsser is touching and fascinating. Clear writing and clear thinking go hand in hand, and Zinnsser’s work On Writing Well did more than any other to help me hone my mind.
\";s: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, 21 May 2015 04:41: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: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: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:103:\"WPTavern: Happy Joe Partners with WebDevStudios, SiteGround and Announces Dates for WordPress BootCamps\";s:7:\"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=44114\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"http://wptavern.com/happy-joe-partners-with-webdevstudios-siteground-and-announces-dates-for-wordpress-bootcamps\";s: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:6025:\"Happy Joe, a 501 c3 non-profit organization that helps U.S. veterans with entrepreneurship and employment opportunities using WordPress, has announced a new round of sponsorships and dates to upcoming boot camps.
\nWhen I talked to James Dalman, founder of Happy Joe in late 2014, he emphasized how important financial assistance is to the organization, “We need people to help fund the training and mentoring of our veterans. We have a lot of people who are sharing the story and mission of Happy Joe and we are VERY appreciative of that. However, we need sponsorships and donations to make a true difference.”
\nWebDevStudios is partnering with Happy Joe as a Hero Partner which is the highest financial contributing level available. Considering the number of military veterans that work at WebDevStudios, the organizations are a perfect match. The agency will also volunteer their time and expertise at upcoming WP BootCamps across the United States.
\nI asked Brad Williams, founder of WebDevStudios and a military veteran, what it means to be able to help veterans through Happy Joe.
\n\nI’m very excited to officially support Happy Joe and their efforts to help Veterans find jobs. As a Veteran myself, I know the struggles trying to find work after leaving the Service, so knowing we are doing something to help ease that process makes me extremely proud.
SiteGround, a webhosting company based in Bulgaria, is also partnering with Happy Joe and will provide business mentoring, career development, training resources, and work opportunities to military veterans and their families.
\nThe company is also providing free hosting for three months to all WP BootCamp attendees. Dalman hints that the partnership may one day lead to the first WP BootCamp in Europe.
\n![\"WordPress](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/11/WPBootCamp.png\")
photo credit: MizGingerSnaps – cc\nWP BootCamps are events tailored to the military community and help veterans of the Armed Forces to set up resume style websites on WordPress so that they can be seen as technology relevant. Veterans are also shown how to launch or build a very successful business or career in the WordPress marketplace.
\nDalman has released a schedule of upcoming camps with the first taking place on July 11th and 12th on GoDaddy’s Sunnyvale, CA campus.
\nPresentations will include, Discovering Opportunities in WordPress, Starting Off Right with WordPress, Finding the Perfect (and Paying) Clients, Winning An Agency Interview, Skills Companies Pay MORE For and more by the following presenters:
\nThere are a limited amount of tickets available but only those who meet the following criteria are able to attend.
\nYou’ll need to show proof of military service via an Active Duty Card, Retirement Card, DD Form 214 from you, your spouse, or family member. Tickets have yet to go on sale but Dalman expects this information to be available in the next few weeks.
\nAs we approach Memorial Day in the US, take some time to remember and thank those who honorably serve or served in the military. Consider supporting an organization like Happy Joe that works year round to give back to 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 21 May 2015 03:52:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:13;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: Learn How to Utilize the WP REST API with Rachel Baker\";s:7:\"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=43136\";s:7:\"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/learn-how-to-utilize-the-wp-rest-api-with-rachel-baker\";s: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:5264:\"![\"photo](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/05/building.jpg\")
photo credit: shenamt – cc\nOne trend at recent WordCamps is that any session on the WP REST API will undoubtedly pack the room with attendees eager to learn more about using it. This was certainly the case at WordCamp London 2015 where more than 200 people crammed into a small room to hear Jack Lenox’s presentation on Building Themes with the WP REST API.
\n![\"rachel-baker\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/rachel-baker.jpeg\")
If you’re a developer who is ready to learn more about getting started with the API, you will not want to miss WPSessions’ upcoming free live event. Rachel Baker, lead engineer at The Wirecutter and formerly a senior engineer at 10up, will be presenting on Utilizing the WP REST API on Tuesday, May 26, 2015.
Baker is one of the lead developers on the WP-API project and is fully in tune with where it’s headed, as well as all the changes in the latest 2.0 beta release. The topics she plans to cover will help developers dive in and start extending 2.0.
\n“The content is driven by wanting to dig deeper with a more technical audience from the overview presentations you see at WordCamps and wanting to show off how easy it is to extend our version 2.0,” Baker said. “This course is only 30-40 minutes, but if it goes well Brian would like to add more.”
\nShe plans to cover the following topics:
\n“It is targeted at developers who are interested in seeing how they can use and customize the API,” Baker said. “Front-end and full-stack developers will see how to add additional fields to the existing endpoint responses. Plugin developers will see a demonstration of how to add their own endpoints. If you are interested in using the WP REST API, or have used version 1.x, you will want to see how version 2.0 works.”
\nBaker’s session will essentially be a crash course in getting started, covering all the basics and more. While there has been a great deal of excitement surrounding the API and what it means for the future of WordPress, many developers are still getting a grasp on how they can incorporate it into real world projects. John James Jacoby made an interesting observation in his recap of LoopConf:
\n\nSo many mentions of the REST API, but not a lot of truly practical usages yet – everyone is building WordPress minus WordPress instead of replacing existing piecemeal AJAX calls or iteratively improving WordPress itself.
Baker is planning to include practical examples in her presentation. One of her main objectives is to help developers get going with the 2.0 beta version so they can offer feedback as they continue to work with it.
\n“I can think of many practical uses, from powering interactions in a plugin like Custom Contact Forms to providing an API for a mobile app like StoryCorps.me,” Baker said.
\n“Our community is hearing that the WP REST API is going to change WordPress and they haven’t seen that happen. I don’t see the WP REST API as changing WordPress. I see the WP REST API as a WordPress feature that makes it easier to interact with your site’s data.”
\nThose who haven’t been able to attend a session on the API in person have an excellent opportunity to see Baker’s WPSessions presentation live for free on Tuesday, May 26th at 3pm EST (UTC-4). It will also be recorded and available after the event for $9.
\";s: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, 20 May 2015 21:43:50 +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: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:110:\"WPTavern: WordPress Trainer Morten Rand-Hendriksen on Common Pain Points, Roadblocks, and Advice for New Users\";s:7:\"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=43952\";s:7:\"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:118:\"http://wptavern.com/wordpress-trainer-morten-rand-hendriksen-on-common-pain-points-roadblocks-and-advice-for-new-users\";s: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:9380:\"The WordPress community is filled with resources to learn about WordPress but finding them can be difficult. WordPress is developed around the clock and locating material that keeps pace can also be a challenge.
\nLynda.com is an online learning center devoted to teaching topics such as, business, technology, design, and photography. For more than five years, Morten Rand-Hendriksen has taught and maintained the WordPress Essential Training course on Lynda.com. The course has been viewed by more than 100,000 individuals and to celebrate, Lynda.com is making it available for free for one month.
\nBy maintaining a WordPress training course, Hendriksen is in a unique position to see trends. He’s also had to keep up with and monitor the vast changes to WordPress that have occurred in the last five years. In the following short interview, Hendriksen describes common pain points users experience with WordPress and shares advice for new users.
\n![\"photo](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/02/wordpress-swag.jpg\")
photo credit: Huasonic – cc\nWhich aspects of WordPress do users have the most trouble with?
\nBased on course feedback and a myriad of emails and questions on Twitter, the hangups people encounter when using WordPress fall into three main categories:
\nMore and more users create local installs to experiment before launching their sites, and they’re creating quite advanced sites on their local computers. When it comes time to migrate these sites, they often get stuck.
\nI think this is partially due to lack of official and understandable documentation about migration, and partially because the general level of technical know-how necessary to build a local install is decreasing. Thanks to tools like MAMP/WAMP, BitNami, and ServerPress, more advanced skills like migration and external hosting become bigger steps up than they were previously.
\nAs WordPress evolves, user interface changes are fairly common but in most cases, they are left unaddressed in release documentation. Recent examples include the removal of Advanced Image Options and Link Title from the editor modals. When changes like these are encountered by existing users, their first response is to assume they are doing something wrong or there is something wrong with their install.
\nIn my opinion, this is justifiable: In other software and in most other situations in the physical world, when a feature is removed or altered in such a way it is not easily found, this change is clearly addressed.
\nIn WordPress, it is usually only the large feature changes that are explained while the smaller ones are left for the user to discover on their own. When these features are part of the user’s workflow, that becomes a problem. This is further exacerbated when meta-conversations in the advanced community go public providing confusing and often contradictory information for new users.
\nThe final grouping is the most obvious one. As the theme and plugin landscape becomes more diversified, users often feel overwhelmed and confused about what solutions to choose and how to use them. A search for membership plugins, business themes, or booking calendars returns hundreds if not thousands of widely different solutions that often have little in common.
\nMeanwhile, you can find blog posts and lists claiming that pretty much every one of them is the best one and the rest are inferior copies. On top of that, more and more themes and plugins are released as freemium offerings or shells that lead the user to a third-party service.
\nAll of this comes together to produce a confusing and frustrating user experience that leaves many users feeling like they are not smart enough to use the application or that they made a wrong choice in going with WordPress.
\nThese are all issues that could be resolved by creating consistent user experiences and by theme and plugin developer communities becoming more mindful of what kind of experiences they provide for the user when they ship freemium solutions or third-party up-sells.
\n![\"WordPress](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/WordPressRoadBlocks.png\")
photo credit: Haven bridge road block – (license)\nAre there more roadblocks to overcome than there were five years ago?
\nThe answer to this question is both yes and no. WordPress has more roadblocks for the beginner, but for the more experienced user there are also more opportunities. I think one of the major challenges we are facing as a community is that WordPress is becoming too advanced for its core user base. The appeal of click-and-publish services like WIX and SquareSpace is that they do not require an in-depth understanding of the underpinnings of the application for it to work.
\nIn striving to become a full-fledged CMS for advanced developers and large publications, WordPress has let itself drift away from its core philosophy of democratizing publishing by adding the very level of complexity it originally aimed to remove. Combined with the theme and plugin issues described above and a lack of modern tools that users expect such as, drag-and-drop design tools and front-end editing, I see new users respond the same way to WordPress today that they did to Drupal five years ago.
\nOn the plus side, these roadblocks are more like speed bumps than fortified walls. With patience and access to well-crafted and easy to understand training materials, I stand by my claim that anyone, regardless of previous experience, can learn to build a great website with WordPress. What has changed is the level of complexity, both in use and in what you can produce.
\n![\"WordPress](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/WordPressAdviceForNewUsers.png\")
photo credit: What You Need To Know About Food Poisoning – (license)\nWhat advice do you have for those new to WordPress?
\nMy number one piece of advice for new and existing WordPress users is to always remember that WordPress is just a tool that makes it easy for you to put content in a database and your visitors to retrieve that content. When learning a new tool as technically advanced as WordPress, it is easy to get so caught up in the tool itself, that you forget what you wanted to do in the first place. Whatever your goals and intentions were when you picked up WordPress for the first time, make sure you remember them and keep working toward them.
\nWhen learning WordPress, whether you are teaching yourself, learning from books or videos, or going to class, remember that every person in the community, even Andrew Nacin, was at some point in time where you are now: Just trying to figure it all out. While every person’s path to learning is different, they all have one thing in common: They all learn from each other.
\nSo reach out online, in person, through Twitter, Facebook groups, Meetups, WordCamps, and beyond, and find like-minded people who want to learn with you or help you on your way. When you meet someone who is just starting out, help them get their footing and invite them into the community.
\nFinally, remember that WordPress is not an island. The web community is a rich ecosystem with many differing solutions based on the same core technology. Learning how the web works gives you the power to use WordPress to move beyond its borders and it’s beyond those borders where true magic is found.
\";s: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, 20 May 2015 19:21:46 +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: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:77:\"WPTavern: WordPress.org is Testing International Theme and Plugin Directories\";s:7:\"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=44068\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"http://wptavern.com/wordpress-org-is-testing-international-theme-and-plugin-directories\";s: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:3751:\"![\"flags\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/02/flags.jpg\")
WordPress.org is making strides towards fully localizing the project’s official theme and plugin directories. Dion Hulse posted this morning that he has enabled localized theme directories for all Rosetta sites. For example, the Romanian themes directory is available at: ro.wordpress.org/themes/.
\nTheme filters, directory sub-navigation, info and download buttons, and other aspects of the details page are all translated. Description and titles are not yet translated, but Hulse says the plan is to add those in the near future.
\n![\"romanian-themes\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/romanian-themes.png\")
Those who are interested in helping translate the interface for the localized theme directories are encouraged to visit the meta translation project page. The process for contributing is the same that is used with WordPress’ other Rosetta translations.
\nLocalized plugin directories are being actively tested at /plugins/ and the sites are also available for contributions from translators. Check out ro.wordpress.org/plugins/ to see the Romanian plugin directory as an example.
\n![\"romanian-plugins\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/romanian-plugins.png\")
As the localized theme and plugin directories are new, there are still a few missing pieces and likely a good number of bugs that will need to be resolved. You can help by reporting them on Hulse’s announcement on the make.wordperss.org/polyglots blog or by opening a ticket on meta.trac.
\nIn Matt Mullenweg’s 2014 State of the Word address, he highlighted the importance of internationalization improvements for connecting and growing the global WordPress community. Localized directories for plugins and themes on WordPress.org are part of this larger effort and make the project’s website easier to navigate for non-English speaking users.
\nIn the future, translation of WordPress’ development handbooks, the codex, and other documentation could also play a large part towards inspiring international developers to make more extensions, products for the marketplace, and contributions back to the project. Growing WordPress’ market share outside of English-speaking countries will be facilitated by having all basic WordPress resources available in other languages.
\";s: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, 20 May 2015 18:37:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:69:\"Post Status: Automattic has acquired WooThemes, makers of WooCommerce\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=12682\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://poststatus.com/automattic-acquired-woocommerce-woothemes/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:21325:\"This acquisition is an important milestone for Automattic, validation for the bootstrapped WooThemes, and will be hugely impactful on the WordPress economy as a whole.
\nWooThemes was started in 2008 as one of the first commercial WordPress theme shops. It quickly became popular and paved the way for hundreds of shops to follow in their footsteps.
\nWith the leadership of Adii Pienaar and co-founders Mark Forrester and Magnus Jepson, WooThemes did a ton of interesting things over the years, and dominated the market with a handful of other shops. They launched WooCommerce in September 2011, in the middle of the commercial theme heyday.
\nWooCommerce’s origins are a hot mess and a long story. WooThemes worked for a long time to develop, with partners, their own eCommerce solution. After numerous failed attempts and false starts, they hired Mike Jolley and Jay Koster full time, and forked JigoShop after acquisition negotiations broke down. Jigoshop is a product that Mike and Jay built as freelancers for JigoWatt, but has since been sold off to another consulting company.
\nMike and Jay were, and are, the heart of that eCommerce plugin — the one we know today as WooCommerce. Under their stewardship, and dozens of other full time and part time contributors — mixed in with outstanding marketing, perfect timing, and a lack of modern competition — WooCommerce took the WordPress world by storm.
\nThey pioneered the extension model for paid add-ons. They put all doubters to rest over and over again. They made mistakes. But they kept at it, kept working, kept making it better. And soon enough, they took the eCommerce world by storm too.
\nIn a short period of four years, WooCommerce has gone from a struggling concept, to a fork, to a remarkable open source commercial software success story.
\nI’ve had the privilege of following WooThemes since around the time they started, and have gotten to know the project and their team even more closely since the very early days of WooCommerce’s launch. In this post, I bring my analysis of the company based on those years of my watching them grow and interacting with them, and hope to share what the acquisition by Automattic may mean for the future.
\nOn the surface, it may seem to many that Automattic was the obvious choice to acquire WooCommerce.
\nAfter all, they need eCommerce support for WordPress.com. As Matt Mullenweg shared with me, they, “have a ton of demand,” for eCommerce from WordPress.com users. Acquiring WooCommerce gives Automattic access to the largest single group of eCommerce stores in the world.
\nBut Mark Forrester and Magnus Jepson — co-founders and owners of WooThemes — could have gone many other routes.
\nWooCommerce is big enough, and has enough brand power, to have attracted significant venture capital investments, as well as suitors from well outside the WordPress space — suitors like MasterCard, eBay/Paypal, Amazon, or Yahoo.
\nThere are 1.2+ million active installs of WooCommerce. They have a nearly 20% eCommerce marketshare of the top one million websites, and over 24% eCommerce marketshare of all websites.
\n![\"woocommerce-builtwith-top-million\"](\"https://poststatus.com/wp-content/uploads/2015/05/woocommerce-builtwith-top-million.png\")
The plugin has had rapid growth over its short four year existence, making it a ripe target for the right buyer.
\nWooCommerce’s popularity has largely been due to the fact that it’s available on WordPress. WordPress makes WooCommerce an attractive choice for websites that need bolt-on eCommerce.
\nOne of WooCommerce’s greatest opportunities for growth is for customers that are eCommerce first, other-parts-of-the-website second. It’s gaining ground quickly as both WooCommerce and WordPress gain further respect for usage on websites of all sizes and scopes.
\nAll of these factors make WooCommerce an attractive choice for Automattic. Automattic’s team knows, understands, and contributes greatly to the WordPress project. A shared reliance on WordPress core makes a WooCommerce and WordPress.com integration simpler. And 55 talented, eCommerce focused employees makes for an inviting addition to Automattic’s relatively small workforce.
\nBringing 55 new people on at once swells Automattic’s ranks by around 18%, bringing them to over 360 people. Recruiting is not easy. This gain of talented people, in a single fell swoop, should not be underestimated.
\nBut there may be some challenges integrating the two teams. This is, by far, the most people brought under the Automattic umbrella in a single acquisition.
\nWooThemes’ theme division and team members will join Automattic’s theme team, and it’s my understanding that WooThemes support will join the Happiness team at Automattic as well.
\nWooThemes has long battled a significant support burden, even before WooCommerce came along. With the demands of supporting eCommerce software that can conflict with nearly infinite plugins, themes, and hosting environments makes support expensive. As long as WooCommerce offers paid self-hosted products, this support will need to be managed.
\nWooCommerce will certainly benefit from the developer resources at Automattic. Matt told me, “lots of folks at Automattic [are] interested in working on eCommerce.” From code audits, to fresh eyes, to more seasoned developers, Automattic’s team will be able to have an immediate impact on the WooCommerce product line.
\nOne aspect I don’t know much about yet is in regard to WooThemes’ middle management. Mark and Magnus own the company, but there is a four person leadership team beyond them:
\nFurthermore, there are product leads for WooCommerce, Sensei, themes, and other elements of WooThemes’ business. As a company, WooThemes is probably as hierarchical as Automattic with six times fewer people.
\nI anticipate some managers may merge into other Automattic teams under new roles, or play a part in sub-teams of sorts, which is (I believe) how Jetpack works now that it’s such a big team.
\nWooThemes is already distributed across five continents and perfectly accustomed to remote work. While they have an office (WooHQ) in Cape Town, South Africa, it’s a “come as you please” environment, similar to Automattic’s San Francisco space.
\nJoining Automattic will be a much cleaner culture fit than other potential buyers would have been. Some team members will naturally leave or integrate to other roles, but the overall gain is a huge win for both organizations.
\nWooThemes is a staple brand of the WordPress ecosystem. They’ve been around since 2008 and probably have the biggest single brand presence after WordPress itself; I’d argue the name is more well-known than Automattic, or even perhaps ThemeForest.
\nFor all practical purposes, I believe the name WooThemes will be retired.
\nWooThemes has previously considered a name change to reflect the change in their business focus, but have not done it. Under the umbrella of Automattic and WordPress.com, there is really no need to carry on the WooThemes brand.
\nI’m told the decision to change the name of the website hasn’t been officially made yet, but it makes no sense to me to keep WooThemes. I’d expect the website we see at WooThemes.com to before long be simply WooCommerce.com.
\nThey better keep Hiro, the Woo Ninja though. I love that little guy.
\nThe WooCommerce business model is built largely on paid extensions that offer additional eCommerce functionality, updates, and support.
\nWooThemes lists a whopping 346 paid and free extensions on their website, about 150 of which link to third party sites. The remaining 200 or so extensions are either developed in house or in partnership with third party developers, but sold on WooThemes’ website. There are also dozens, if not hundreds more, distributed plugins by other vendors that are not listed.
\nCompanies like SkyVerge and Prospress have built their businesses on WooCommerce extension development. If the model were to change drastically, it could have a great deal of impact on them and similar companies or solo developers.
\nThird party developers have been told that life will be business as usual. In an email to strategic partners, Joel Bronkowski said, “There are no plans to mess with the magic sauce strategy that has brought us this far.”
\nHowever, the model of paid plugins is also counter to Matt Mullenweg’s often stated beliefs for what commercialization in the WordPress plugin space should look like.
\nI asked him to explain how his mindset has changed in regard to paid plugins that charge for support and updates. Paid Automattic plugins, like Akismet and VaultPress, are based on SaaS models.
\nHe says that his view has not changed. He told me that one goal with WooCommerce will be to determine, “what services provide the most value to people over a long period of time.” He also noted that such a question is due to the fact that many WordPress product sales are one-time.
\nI found his sentiment curious. He didn’t directly answer the question about paid plugins, which isn’t too surprising. It’s impossible to imagine Automattic doing away with paid extensions in the short term, but there are serious threats to third party developers in the longer term, I believe.
\nWooCommerce has spent a lot of time doing business development over the last couple of years. Last summer, their leadership team went to Chicago for a big eCommerce conference and had a whole new world opened up to them.
\nJoel told me they, “still have a lot to figure out in terms of the road ahead, but [we are] incredibly excited about what this means for us in terms of product development, partner opportunities and for WordPress powered eCommerce.”
\nUnder the wing of Automattic and in the future WordPress.com, I think WooCommerce will be able to further leverage their position in the eCommerce market with big payment companies and other potential corporate entities.
\nI would guess that a gradual change in business model will occur over the next several years, especially in regard to extensions. WooCommerce has a dismal 17% renewal rate for extension purchases. This is a number that needs to improve, or something should change.
\nIt may make sense — and I’m shocked I’m saying it — to make WooCommerce more like Jetpack.
\nIf I were at Automattic, I would encourage the two teams to brainstorm and evolve together. I think a model where a credit card is connected to WordPress.com, and extensions (free and paid) can be easily activated from within the admin makes sense. It would require a lot of change to existing UIs and development infrastructure, but it could also drastically improve what is often a convoluted method for site management with so many add-ons being independently managed.
\nIf we take the potential even further: imagine the VaultPress model of instant syncing, data tracking, and backups being heavily integrated into eCommerce stores. Such a system could be part of a monthly fee.
\nExtensions also don’t have to be piecemeal, or the “nickel and dime” method. Automattic could make WooCommerce a tiered payment plan, where certain levels unlock particular functionality. Or they could buyout all third party paid extensions they care about and make the entire product free or part of a single package.
\nThe point is that Automattic purchasing WooCommerce gives them an incredible amount of flexibility in terms of how to move forward. WooCommerce store owners should be prepared for a lot of potential change.
\nAs a bootstrapped company, WooThemes had to turn a profit. Automattic has to make the company more valuable, but does not need to care about cash day to day. Their stated goal is to make products people want to use. A very small number of people at Automattic really consider profits and losses regularly. That mindset, when applied to WooCommerce, could bring about significant change indeed.
\nAn important concern over the next year or two will be how to bring WooCommerce to WordPress.com. There is little question that it will happen.
\nMatt Mullenweg highlighted the demand from the general WordPress.com userbase, and hosted WooCommerce would be a great answer to Squarespace’s eCommerce add-on, and the likes of Shopify and BigCartel.
\nFurthermore, I’m sure a number of WordPress.com VIP customers will be clamoring for WooCommerce. Automattic’s Vice President of Platform Services, Paul Maiorana, said, “VIP tends to follow the same trends as the broader WP community. Initially blogs, then CMS, now everything.” He is excited about being able to offer a more catered eCommerce experience “in house to better service those customers.”
\nA hosted version of WooCommerce will be a very compelling upsell for WordPress.com if they are able to pull it off well. This too, will not be easy. But they are starting with a heck of a head start, given the WooCommerce brand name, team, and existing plugin infrastructure.
\nWooThemes makes more than WooCommerce, however nearly all of their products today at least integrate with WooCommerce.
\nWooThemes’ themes will be integrated into WordPress.com’s theme offering. Eleven themes are already listed there from an existing partnership that goes back to early 2011.
\nThe Sensei courseware plugin will also continue to be developed and maintained. Regarding Sensei, Matt Mullenweg said, “their team is passionate about it, which is kind of the criteria for what Automattic works on.”
\nThere is a lot of potential in the course space, and I actually think this could be a nice win for Automattic in this acquisition, especially if Sensei gets additional resources and attention.
\nWooThemes has other active free plugins that I doubt will change much. WooSlider is their only other paid plugin, but I don’t think it makes up a considerable amount of revenue.
\nI wouldn’t be surprised if both WooSlider and Sensei core become free plugins.
\nEveryone wants to know: how much was WooThemes making, and how much was the acquisition for?
\nRe/code’s Peter Kafka has sources that say the acquisition was for, “more than $30 million in cash and stock.” I believe this to be a reasonable amount and I don’t think he’d make the claim without some confidence.
\nI don’t know what the terms of the deal were. I’ve tried all day to find out. The best I can do is tell you what I know, what I think I know, and guess right along with everyone else. Sounds fun, right?
\nI’m quite confident that WooThemes’ revenues were around $9-$10 million in 2013. I also know that they have had positive trajectory month over month growth for some time, and I have reason to believe one of their more recent record months well exceeded $1 million in revenue.
\nIf we extrapolate the 2013 numbers with 10-20% growth, we can presume that their gross revenues are somewhere in the neighborhood of $15 million annually.
\nBased on some feedback from people I trust, a 2x multiple of expected 2015 revenues isn’t out of the question. In typical proprietary software and product situations, that would be a low multiplier.
\nBut in this case, WooThemes’ sends a lot of money directly to third party developers, and spends a great deal of money on development and support. Furthermore, WooCommerce isn’t proprietary, it’s open source; which while I love and advocate for it, it simply would be difficult to valuate the same as proprietary software.
\nAdditionally, I could be naive, but in the case of Automattic I’d rather more stock than cash. They are destined for an IPO (someday) that will likely put them well beyond their latest $1.16 billion valuation, and today’s stock could be worth many times what it is now in the years to come.
\nLastly, I don’t think Re/code would run a number they pulled out of thin air. I think they got that from somewhere — perhaps a VC source.
\nI firmly believe WooThemes could’ve continued to grow WooCommerce to be worth $100 million or more. But it would’ve likely been a long and challenging road.
\nUnder the Automattic umbrella, they have a great shot to continue making an awesome eCommerce product without some of their current burdens and with some outstanding new resources.
\nMeanwhile, especially if the $30-$35 million price is correct, I think Automattic got a steal. It’s a brilliant way into a huge market with a major player.
\nThere are potential downsides to this purchase. For one, it makes Automattic further feel like a vacuum that inevitably sucks up the best talent, agencies, and products once they showcase their potential for success.
\nWooThemes was the bastion all other bootstrapped WordPress products stood behind. Knowing it’s possible to do something as big as WooThemes was doing, without funding and starting from nothing, is awesome.
\nSeeing them snatched up by Automattic around the time they’ve become nearly ubiquitous with the term “WordPress eCommerce” is kind of a bummer. It’s like we now have to start over again to see what WordPress centric product company can grow big enough to stand beside Automattic, not under it.
\nI also have some fear that if Automattic rocks the boat too much with WooCommerce it will cause some big inroads WordPress has made in self-hosted eCommerce to be lost.
\nMy concerns are relatively minor. Would I have loved to see WooThemes continue to grow and dominate eCommerce alone? Yes. Am I excited by what this deal makes possible? Yes. Am I a little concerned what it will do to the WordPress economy? Yes.
\nWe must all weigh the pros and cons of any decision. For Mark, Magnus, and the WooThemes team, this is a move that is good for them during this time, and will likely be good for the company they started seven years ago.
\nFor Automattic, this is a heck of a way to round out their first decade in business. It’ll be really interesting to see what the next decade holds in store, but I bet Automattic will look a lot different then, like they do now compared to 2005.
\nCongratulations to both teams. You can read the announcements on Matt’s blog and WooThemes’ blog.
\nPhoto credit: 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 20 May 2015 07:15:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:41:\"WPTavern: Automattic Acquires WooCommerce\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://wptavern.com/?p=44023\";s:7:\"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:\"http://wptavern.com/automattic-acquires-woocommerce\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6368:\"![\"photo](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/woomattic.jpg\")
photo credit: Ma.tt – “A Celebratory Toast\nAutomattic CEO Matt Mullenweg announced today that the company has acquired WooCommerce, WordPress’ most popular e-commerce platform. The plugin recently passed seven million downloads and stats from BuiltWith show that WooCommerce is dominating global e-commerce platforms, powering roughly 30% of all online stores.
\nThis is Automattic’s largest acquisition to date, bringing 55 new employees into the company from 16 countries for a total of 370 Automatticians. Mullenweg confirmed that the acquisition includes Woo, Sensei, and all of the other plugins and themes.
\nGiven WooCommerce’s extensive adoption on the web, Automattic will not be re-branding the newly acquired products. WooThemes and WooCommerce will continue to be sold via their dedicated websites.
\n“We’re planning on retaining (and growing) the WooCommerce brand,” Mullenweg told the Tavern. “The plan is to keep what has been working going.”
\nMullenweg has spoken frequently over the years about growing Automattic’s reach into global commerce, but few could have predicted that the company would acquire Woo as opposed to building its own in-house commerce platform.
\n“They have a full team that goes to bed every night and wakes up in the morning thinking about commerce; it’s core to their DNA,” Mullenweg said. “That’s better than starting it in-house. Also they have a ton of adoption already.”
\nIn April, WooThemes co-founder Magnus Jepson told the Tavern that WooCommerce accounts for over 85% of overall sales and processes “several million dollars per year.” Jepson also confirmed that WooCommerce’s revenue “has been climbing steadily over the past few years, and we are regularly breaking monthly revenue records.”
\nAutomattic is not releasing the financial details of the acquisition, but Re/code speculates that it was in the range of $30 million:
\n\nSources say Automattic will spend more than $30 million in cash and stock to buy the 55-person company. Automattic CEO Matt Mullenweg wouldn’t comment on the price but said the acquisition was the largest his company had made, ‘by about 6x.’
In addition to growing the current WooCommerce customer base, Automattic is looking to use the platform to add more selling options for WordPress.com customers, while retaining its existing e-commerce partnerships.
\n“Partnerships will remain in place on WP.com, but long-term we’d like to offer Woo as an option there as well,” Mullenweg said.
\nWhen asked about plans to integrate WooCommerce into Jetpack, he said, “Jetpack could definitely complement WooCommerce (and WooThemes), but not the other way around.”
\nWooThemes founders never imagined that WooCommerce would rise to the level of popularity that it has, ultimately bringing them into the Automattic family. Co-founder Mark Forrester writes:
\n\nIn 2008, as three strangers in three countries, we set out on a quest to pioneer WordPress commercial theming, never dreaming of the rocket-propelled voyage into the self-hosted eCommerce unknown that lay ahead. It’s been an incredible ride, backed by a unique community, and here we find ourselves powering over 24% of online stores with our flagship product, WooCommerce.
The acquisition affects a whole fleet of third-party designers and developers who create products for WooCommerce. They will likely have more opportunities and sales ahead of them with the power of Automattic behind the core plugin. Mullenweg confirmed that the next WooConf, scheduled to take place in Austin in November, will continue on as planned. Those who are heavily involved in the WooCommerce ecosystem will still be able to connect and build for the platform as they have done previously.
\nWith Automattic now at the helm of the most dominant e-commerce platform on the web, it will be interesting to see if the company can make selling online just as simple as it has made publishing online. WordPress.com’s tremendous success can be partially attributed to the company’s commitment to democratizing publishing.
\n“I do believe that the web needs an open, independent and easy-to-use commerce platform that you can run yourself on your own website,” Mullenweg said in his video announcement, the first video ever to be published to Automattic’s YouTube account.
\nPublishing products and selling them on the web is arguably a more complex endeavor than simple publishing, especially when you factor in location, tax, payment gateways, and everything needed to process transactions. The average non-developer has no concept of what it takes to set up a blog, let alone an online store. But if Automattic can play a part in democratizing the ability for regular folks to sell products online, it has the potential to globally transform e-commerce.
\";s: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, 19 May 2015 21:15: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: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:26:\"Matt: Woo & Automattic\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:21:\"http://ma.tt/?p=45068\";s:7:\"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:31:\"http://ma.tt/2015/05/woomattic/\";s: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:4529:\"For years, we’ve been working on democratizing publishing, and today more people have independent sites built on open source software than ever before in the history of the web. Now, we want to make it easy for anyone to sell online independently, without being locked into closed, centralized services — to enable freedom of livelihood along with freedom of expression.
\nIt’s not a new idea: at a WordCamp a few years ago, someone stood up and asked me when we were going to make it as easy to create an online store as we’d made it to create a blog. Everyone applauded; there’s long been demand for better ecommerce functionality, but it’s been outside the scope of what Automattic could do well.
\nThat changes today — drum roll — as WooCommerce joins the Automattic team to make it easier for people to sell online. Along with Woo’s announcement, here’s a short video explaining more:
\n\n
In the past few years, WooCommerce really distinguished itself in its field. Just like WordPress as a whole, it developed a robust community around its software, and its products meet the needs of hundreds of thousands of people around the world.
\nWoo is also a team after Automattic’s own distributed heart: WooCommerce is created and supported by 55 people in 16 countries. Added to Automattic’s 325 people in 37 countries, that’s a combined 380-person company across 42 countries — the sun never sets.* I can’t wait to meet all my new colleagues.
\nJust like us, the vast majority of WooCommerce’s work is also open source and 100% GPL. And just like WordPress, you’ll find WooCommerce meetups popping up everywhere, from Los Angeles to London, and its global and community-focused work together to make the users’ experiences the best they can be.
\n![\"ecomm-trends\"](\"http://i0.wp.com/ma.tt/files/2015/05/ecomm-trends.png?resize=447%2C294\")
The stats are impressive: the WooCommerce plugin has over 7.5 million downloads and a million+ active installs; BuiltWith’s survey of ecommerce platforms shows Woo passing up Magento in the top million, with about triple the number of total sites. Even a conservative estimate that WooCommerce powers 650,000 storefronts means they’re enabling a huge number of independent sellers. They’ve added a tremendous amount to the WordPress ecosystem (alongside everyone else working in this area).
WordPress currently powers about 23% of the web. As we work our way toward 51%, WooCommerce joining Automattic is a big step opening WordPress up to an entirely new audience. I can’t wait to see how much more we can build together.
\nAutomattic turns ten next month: another amazing milestone I couldn’t have imagined a decade ago. Today’s news is just the first of a number of announcements we have planned for the remainder of the year, so please stay tuned! There’s still so much work to do.
\n* Want to work with us? We’re hiring. Bonus points if you live in Antarctica, the only continent we don’t have covered.
\nAs I said in the video, please drop any questions you might have in the comments and I’ll answer them as soon as I can. Also check out the posts from Mark and Magnus.
\nRead more: Mashable, Recode, Techcrunch, Venturebeat.
\";s: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, 19 May 2015 18:59:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:74:\"WPTavern: WordPress Cape Town to Host 2nd Annual Charity Hackathon in June\";s:7:\"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=43986\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"http://wptavern.com/wordpress-cape-town-to-host-2nd-annual-charity-hackathon-in-june\";s: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:3696:\"![\"wordpress-cape-town-charity-hackathon-2015\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wordpress-cape-town-charity-hackathon-2015.jpg\")
Last August, the WordPress Cape Town meetup group experimented with hosting its first charity hackathon to benefit local charities. The do_action( ‘wordpress-charity-hackathon’ ); event was so successful in 2014 that organizers were inspired to make it an annual event. The 2015 hackathon is scheduled for June 20th from 9:00 AM – 5:00 PM.
\n“With a team of nearly 50 volunteers from the community, we built brand new websites for nine different charitable organizations and we will be doing the same again this year,” said Hugh Lashbrooke, an organizer for the event.
\nThe concept will be the same as the previous year – volunteers will build sites for nine Capetown-based charities, giving each their own unique online presence by the end of the day.
\nA few examples of websites built by the volunteers last year include:
\n“The charities this year are equally as deserving and spread across the whole spectrum of society again,” Lashbrooke said. The 2015 charities list includes organizations such as the Academy for Adults with Autism, FoodBank South Africa, and the Down Syndrome Inclusive Education Foundation NPC.
\nSponsors this year include Hetzner, Obox, and WooThemes. Their generous contributions will help to provide snacks, lunch, dinner, and a prize for the team that builds the best site of the day. All attendees will also receive a ticket to WordCamp Cape Town 2015.
\n“We are still looking for volunteers (there are about 20 spots left at the time of writing this) and it’s important to note that we are not just looking for developers here,” he said. “This is open to Project Managers, Designers, Developers, Content Creators, and Social Media Managers, as all of those individuals are needed to bring a complete website together (especially when it is all being done in one day.)”
\nIf you’re in the Cape Town area and you’d like to be part of this event, you can select a charity team to work on and specify your role when filling out the volunteer application form. Check out the recap video below for a closer look at attendees’ experiences from last year’s event.
\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:\"Tue, 19 May 2015 18:49:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:73:\"WPTavern: Short Survey on Which WordCamp Organizer Tools to Improve First\";s:7:\"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=43992\";s:7:\"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:83:\"http://wptavern.com/short-survey-on-which-wordcamp-organizer-tools-to-improve-first\";s: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:1978:\"
In the past several months, the Make WordPress Community team has engaged in numerous discussions with WordCamp organizers on how they can improve the tools that are available. Those discussions include:
\nThe team has created a six question survey to gather data to determine what tools should be worked on or improved first. If you’ve worked with any of the tools available on WordCamp.org within the last 18 months, you’re strongly encouraged to take the survey.
\n![\"WordCamp](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/WordCampOrganizerToolSurveyQuestion.png\")
WordCamp Tools Survey Question\nThe last section has two questions that are open-ended to allow for feedback that extends beyond the tools in question. This is an excellent opportunity for WordCamp organizers to voice their opinion on what direction the team should take on creating and improving the tools available to them. It’s also a way to tell the team which tools you want to see created that don’t already exist.
\";s: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, 19 May 2015 18:36:50 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:21;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"Matt: How to Get Yourself to Do Things\";s:7:\"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=45054\";s:7:\"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:\"http://ma.tt/2015/05/how-to-get-yourself-to-do-things/\";s: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:227:\"How to Get Yourself to Do Things. Hat tip: 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:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 May 2015 05:16: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: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:54:\"WPTavern: A WordPress Veteran’s Take on DrupalCon LA\";s:7:\"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=43963\";s:7:\"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:61:\"http://wptavern.com/a-wordpress-veterans-take-on-drupalcon-la\";s: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:5746:\"![\"Mendel](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/MendelKurland.jpg\")
This post was contributed by guest author Mendel Kurland. Kurland is GoDaddy’s evangelist who travels to WordCamps and is the interface between various open source communities and GoDaddy.
In the following post, Kurland shares his experience attending DrupalCon Los Angeles, a large conference devoted to Drupal.
\nAs I flew from DrupalCon Los Angeles, CA to WordCamp Maine, I thought a lot about what the Drupal and WordPress communities could learn from each other. WordPress and Drupal are two community-built platforms and each community is powerful. We stand to learn a lot from each other, because all open source projects matter.
\nWith an eye toward looking for the similarities, rather than the differences, both WordPress and Drupal are working to overcome similar obstacles including, brand recognition, threat mitigation, adoption, onboarding, contribution, the list goes on. So why did I go to DrupalCon LA? To learn and give back to another community that’s steeped in collaborative culture.
\nThousands of people attended DrupalCon in Los Angeles this year. It’s massive and the layout is similar to a large developer conference. There are sessions centered on technical, as well as business topics, and usually lively question and answer opportunities after each session. There’s a coder lounge, a contribution room, and a huge emphasis on contributing to coding sprints for the next release of Drupal, Drupal 8.
\n![\"DrupalCon](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/DrupalConLA.png\")
Photo via Mendel\nPrior to the conference, DrupalCon had summits to help gather community members around a particular vertical or topic such as, higher education, community, business, and training sessions to help level-up skills based on experience.
\nThe theme of organizing around common interests is strong throughout the entire conference with birds of a feather sessions and topical social gatherings with topics like, women in Drupal and first time attendees. When it comes to mobilizing around interest groups, Drupal does a brilliant job.
\nI’ve met a higher proportion of people who work on enterprise sites at DrupalCons and a higher proportion of people who work on small business sites at DrupalCamps, local conferences similar to WordCamps. There are some important lessons, however, that I took away from the Drupal community.
\nIf you’re reading this article on the Tavern, you’re likely a WordPress loyalist. I love WordPress, and it’s also ok to love Drupal. They are both tools in an open source toolbox that we all share. The beauty of our opportunity as developers, designers, and creative professionals is our ability to create awesome things in a million different ways.
\nIn going to DrupalCon, it was refreshing for me to take a second to see the web development industry from another perspective. I’d love to hear your perspective in the comments and on Twitter.
\";s: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, 19 May 2015 01:53:43 +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: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:83:\"WPTavern: Community, Translation, and Wapuu: How Japan is Shaping WordPress History\";s:7:\"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=43605\";s:7:\"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:90:\"http://wptavern.com/community-translation-and-wapuu-how-japan-is-shaping-wordpress-history\";s: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:16719:\"![\"Japanese](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wcsf-2014-japanese-community.jpg\")
Japanese WordPress community representatives at WordCamp San Francisco 2014\nJapanese WordPress users were some of the earliest to see the project’s potential and help bring the software to the non-English speaking world. At the end of 2003, just six months after Matt Mullenweg and Mike Little decided to fork b2, a Japanese version of WordPress was available.
\n![\"WordPress-ME\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/WordPress-ME.jpg\")
The version was originally called “WordPress ME” and was maintained by a user called Otsukare, whose translation notes indicate that he believed WordPress would become “convenient and increasingly easy to use in the future.” This Japanese version corresponded with WordPress 0.72, as WordPress wouldn’t have internationalization support until version 1.2.
\nOtsukare was instrumental in demonstrating the demand for translation for all languages with the popularity of his multilingual fork of WordPress, which allowed easy modification via the use of a language file. It is rumored that this multilingual edition, along with discussions on the WordPress ME fourms, was influential in bringing gettext into WordPress.
\nOver the past 11 years, local Japanese WordPress communities have grown steadily. Naoko Takano, who has been involved with the local community since 2003, attributes that growth to consistent translation and a reliable release workflow, managed by a dedicated Japanese package team.
\n![\"japanese-package-team\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/japanese-package-team.jpg\")
An organized system around translation and documentation were two key ingredients that helped germinate the early Japanese WordPress community, but local meetups were ultimately the catalyst for its massive growth.
\nThe first WordCamp Tokyo was held in 2008 with 60 attendees. WordCamp Tokyo today now pulls in 1200 – 1400 people, according to co-organizer Shinichi Nishikawa. This event is larger than past editions of WordCamps Europe and San Francisco.
\nNishikawa reports that over the past seven years, Japan has hosted 15 WordCamps in Tokyo, Kyoto, Fukuoka, Yokohama Nagoyo, Kobe, and Osaka. WordCamp Kansai, held in the Western part of the country, was organized by WordBench members of that area, including Shiga, Kyoto, Osaka, Hyogo, Nara and Wakayama.
\nRegional WordPress groups in Japan are organized on WordBench.org, a site that allows users to find, join, and create a meetup. The site was created in 2009 by Takayuki Miyoshi, the author of Contact Form 7, one of WordPress’ most popular plugins. WordBench has been running on BuddyPress for the past six years and was originally built on RC1 of the plugin.
\n![\"wordbench\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/wordbench.png\")
The site currently lists 48 local groups throughout Japan, named for their cities, i.e. WordBench Tokyo, WordBench Osaka, WordBench Kawasaki. Members and organizers use the site to post about upcoming events and recaps of meetups recently held in various locations. The site serves to keep Japan’s local communities connected and inspired.
\nIn addition to the regional WordBench groups, interest-based meetups are also common in the Japanese WordPress community. In this format, members meet around different interests outside of WordPress, such as cooking or photography. For example, the WordPhotoclub meetup gathers together to go on walks and take photos. Members’ photos were printed and displayed at WordCamp Tokyo 2012.
\nWordCrab is another example of one of Japan’s unique WordPress meetups. Members from all over from Japan gather in the Fukui prefecture, where they combine WordPress sessions with a giant crab party where everyone feasts upon the region’s renowned crabs.
\n![\"photo](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/wordcrab.jpg\")
photo credit: WordCrab meetup\nThe Word温泉 (WordOnsen) meetup is centered around the enjoyment of hot springs. Members gather in Fukushima and stay at a hotel where they have WordPress sessions and a party night.
\n“In meetups we started doing more things than just learning WordPress,” community organizer Shinichi Nishikawa said. “We get friends together and go for a walk and eat lunch/dinner together.
\n“I think this a really good way to make the community stronger. People are talented in different things and by doing something together, other than WordPress, people can show their talents. And of course, it’s fun.”
\nJapan’s holistic approach to meetups incorporates various aspects of life and relationships, as opposed to simply centering around improving WordPress technical skill. As a result, members become more connected and meetups are highly personalized. That’s where Wapuu enters the picture to bring special meaning to each group.
\nWapuu, the official mascot character of WordPress, was designed by Kazuko Kaneuchi in 2011. It’s distributed under the GPLv2 or later and can be modified by anyone to add more personality to the character.
\n“Thanks to the freedom of the GPL, there have been many forked versions of Wapuu,” Nishikawa said. “All local Wapuus are created by someone who belongs to each local community and they hold something that represents where they are from.”
\n![\"photo](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/local-wapuu.jpg\")
photo credit:Wapuu is so well-loved that the creature ends up making its way onto swag, cakes, and nail and coffee art at Japanese WordPress events.
\n![\"photo](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wapuu-everywhere.jpg\")
photo credit:The name “Wapuu” was given to the mascot by a users’ poll. “Japanese people pronounce WordPress as ‘WAADOPURESU,\'” Nishikawa said. “Wapuu sounds like an abbreviation of WAADOPURESU, taking ‘Wa’ and ‘Pu’ from it.”
\nModifications of the mascot have recently started popping up at WordCamps outside of Japan. WordCamp London’s wapuunk was so popular that it inspired WordCamp Philly and WordCamp Belgrade to create their own unique modifications to the character.
\nFor whatever reason, Wapuu seems to have a special power to bring people together, regardless of culture or location. WordPress has the Japanese community to thank for its unique open source contribution to meetup branding.
\nDespite having a large WordPress community thriving in Japan, with many of the top websites built on the software, Japanese developers have a difficult time contributing back to core.
\n“Language is the biggest barrier,” Nishikawa told the Tavern. “There are many good developers in Japan (and in other countries) who don’t speak English. Most of them can read documentation but joining in the conversation in tickets and on Slack is a different thing.
\n“In my opinion, there is English for native speakers and English for international people, and they are different,” he explained.
\n“It’s difficult to say how different they are, but for us who are not native, ambiguous words, abbreviations like ‘FWIW,’ jokes, and slang are difficult,” Nishikawa said. “Sometimes nesting a long sentence in another long sentence by using ‘that,’ ‘which,’ and ‘including’ is difficult.”
\nHe explained that overcoming the language barrier is more than simply learning English; it also includes the hurdle of trying to understand the abbreviations and expressions that are infused by the culture around native English speakers.
\n“People would say that you can understand because it’s code, but if we look at the conversations in tickets, the surrounding discussion often concerns more than just the code,” he said.
\n“Non-English speaking developers are trying to learn English, but it would be good if people in the ticket / Slack would keep in mind that there are people who don’t share the context or culture behind the words they write,” Nishikawa suggested.
\n“If we make the words and expressions easier to understand, someone who understands 80% will have the opportunity to understand nearly 100%.”
\nHowever, Nishikawa is unsure of whether or not it is productive to request these kinds of changes, given that communication can never really be separated from culture.
\n“Maybe a more welcoming atmosphere needed?” he said. “On the other hand, I know that the discussions include a great deal of context and many cultural things. It’s a place for communication, too. So, I don’t know if it’s right to say that something needs to change.
\n“Additionally, there are many talented developers who don’t understand English at all and I have no idea what can be done for them,” he said.
\nNishikawa said that he felt much more connected to the community after attending WordCamp San Francisco and the following summit and contributor day.
\n“Even for developers who didn’t speak English, we had translators and discussed things, looked at the code and shared the WordPress projects they are working on,” he said. “After these face-to-face conversations, developers are more relaxed and motivated to work in the core Make project. Inviting developers to meetups/camps in the English world or inviting core contributors travel and join local contribution days will be a big trigger to involve more people.”
\nNishikawa believes that WordPress has a bright future in Japan, thanks to the efforts of Otsukare, Naoko Takano, Takayuki Miyoshi and all the plugin developers, Tenpura (the author of WP Multibyte Patch plugin), bloggers, community organizers, an army of dedicated translators and more.
\nHe is hopeful that positive experiences for developers at global meetups like WCSF will help the Japanese WordPress community find ways to contribute back to core and other projects.
\n“There have been a few people who had contributed separately, but now I feel there is a small groove of people who are more interested in contribution,” he said.
\n“For the community, we hope that the activeness of the Japanese community will be exported to other Asian (and global) communities, especially with Wapuu or the unique “more-than-learning” style of meetups.”
\nHe also believes the future of WordPress in Japan will be brighter with the internationalization improvements that are continually being added to core.
\n“For the users, when everything is translatable, people are happier. If WordPress can become more mobile friendly, it will be used more by young people. When the WP-API is in core, there will be more diverse apps available.”
\nNishikawa has had such a positive experience organizing WordPress community events in Japan that he is now active in growing the community in Thailand.
\n“We now have meetups twice per month in Bangkok for developers/users/designers. We don’t have ‘session-oriented meetups’ anymore but we try to have casual talks every time, where everyone can speak in their own languages. Translation is more than welcome but we don’t want to rely on someone.”
\nAs Japan’s community-oriented approach to learning has paid off with highly active meetup groups and some of the largest WordCamps on the globe, Nishikawa is hoping to bring his experience to Thailand and help organize a WordCamp Bangkok in the near future.
\n“Community has made my life/job much more exciting and fun,” he said. “Many things will differ culture by culture but the core value of community should be the same everywhere.”
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 May 2015 21:26: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: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:30:\"Matt: 2 Chocolate Chip Cookies\";s:7:\"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=45056\";s:7:\"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:\"http://ma.tt/2015/05/2-chocolate-chip-cookies/\";s: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:494:\"\nSometimes, you just want 2 chocolate chip cookies. This happens to me all of the time. I want a super indulgent, rich and buttery chocolate chip cookie, but don’t want to make the whole 36 of them which I’d inevitably inhale over about the same amount of hours.
Ever wondered a good recipe to make just 2 chocolate chip cookies? Now you know.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 18 May 2015 06:35: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: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:23:\"Matt: Silk Road, Part 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:21:\"http://ma.tt/?p=45063\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"http://ma.tt/2015/05/silk-road-part-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:435:\"As promised a few weeks ago, a new installment of the Wired Silk Road story is out and I wanted to share it, The Untold Story of Silk Road, Part 2: The Fall. This one is actually a lot more normal, with some surprisingly simple breaks leading to the downfall of Ross, but there’s an interesting twist at the end.
\";s: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, 16 May 2015 17:14: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: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: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:27:\"Matt: Memorable Musk Quotes\";s:7:\"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=45046\";s:7:\"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/05/memorable-musk-quotes/\";s: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:224:\"The 22 most memorable quotes from the new Elon Musk book, ranked. Hilarious.
\";s: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, 16 May 2015 06:14: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: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:82:\"WPTavern: Display Your Contributions to WordPress With the WP Contributions Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://wptavern.com/?p=43823\";s:7:\"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:92:\"http://wptavern.com/display-your-contributions-to-wordpress-with-the-wp-contributions-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:4327:\"![\"WPContributionsFeaturedImage\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/WPContributionsFeaturedImage.png\")
WP Contributions is a new plugin by Dustin Filippini, Damon Cook, and WebDevStudios that displays WordPress contributions via widgets. Widgets included are:
Once activated, browse to Appearance > Widgets to access the new widgets. You’ll need to know your username for WordPress trac and the Codex to display your contributions. Keep in mind that the core contributions widget only list tickets that are closed and you received props for.
\n![\"WP](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/WPContributionsCoreWidget.png\")
WP Core Contributions Widget\nThe Codex contributions widget displays the most recent articles you’ve edited along with a link to see more.
\n![\"Codex](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/WPContributionsCodexWidget.png\")
Codex Contributions Widget\nThe theme and plugin widgets use the slug of the theme and plugin you want to feature. You can only feature one theme or plugin at a time unless you use multiple widgets. The featured plugin widget displays a thumbnail of the plugin’s header image, author name, version, description, average rating, total downloads, and when it was last updated.
\n![\"WP](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/WPContributionPluginWidget.png\")
WP Contribution Plugin Widget\nThe featured theme widget displays a small preview of the theme, a short description, average rating, author, current version, total downloads, and when it was last updated.
\n![\"Featured](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/WPContribThemeWidget.png\")
Featured Theme Widget\nEven though the plugin and theme widgets are meant to be used to showcase your own work, they’re great for featuring any plugin or theme you’d like people to know about. WP Contributions comes with a series of template tags for those who want more control over how the information is displayed.
\nOne thing I’d like to see in a future version is short code support. This way, users could create a WP Contributions page on their site with easy to use short codes. It’s not supported now, but Filippini informs me that a future version will include the ability to display badges attached to a WordPress.org user profile.
\nAs WordPress continues to increase in marketshare, the ability to show how much you’ve contributed to the project is a huge resume booster, especially if you can say your code runs on millions of sites. In early 2014, WordPress made substantial improvements to user profiles but there’s no easy way to display those contributions to a wider audience.
\nWP Contributions does a decent job filling the void and is available for free on the WordPress.org plugin directory. I tested WP Contributions on WordPress 4.2.2 and it works without any problems.
\";s: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, 15 May 2015 23:28: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: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:77:\"WPTavern: Lasso Frontend Editing Plugin for WordPress Now Available on GitHub\";s:7:\"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=43852\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"http://wptavern.com/lasso-frontend-editing-plugin-for-wordpress-now-available-on-github\";s: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:4698:\"WordPress developer Nick Haskins is hoping to revolutionize the way users publish content with Lasso, his commercial front-end editing plugin. Lasso is sold through his storefront and is also in use on Story.am, the hosted platform for Aesop Story Engine. Haskins recently made accounts on Story.am available for free in hopes of garnering more feedback on the Lasso editing experience.
\n![\"building-with-lasso\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/building-with-lasso.gif\")
As of today, Lasso is now available on GitHub for developers and users to test and offer feedback/contribution.
\n“This decision was several months in the making,” Haskins told the Tavern. “It included conversations with developers who have their commercially sold code publicly available, as well as A/B testing our presence to verify that the move would be both beneficial to the plugin, as well as the user base that it’s attracting.”
\nMaking the code public is a calculated risk, which he hopes will not damage sales of the plugin but rather increase its visibility. Haskins recently published a financial transparency report on his 15 month old company, which indicates that Aesop Interactive is on track to double its revenue in 2015 based on numbers from January – April. Sales of the Lasso product totaled $4,408.36.
\nAs the plugin is open source, you are free to use it anywhere, but Haskins notes that support will only be offered to customers:
\n\nIf you have a suggestion, a bug report, or a patch for an issue, feel free to submit it here. We do ask, however, that if you are using the plugin on a live site that you please purchase a valid license from the website. We cannot provide support to anyone who does not hold a valid license key.
“I decided to make it public today after I was invited in to collaborate on another publicly available commercially sold plugin,” he said. “I just needed a final excuse, and that was it.”
\nHaskins is not the first developer to make a commercial WordPress product available on GitHub for contribution. Earlier this year, the folks behind GravityView decided to make their plugin public on GitHub after being inspired by a discussion between Matt Medeiros and Matt Mullenweg on ubiquity vs. scarcity as it relates to WordPress product businesses:
\n\nThe one pattern I see most right now that I think is not sustainable is, and it’s because it’s the easiest thing to do, is businesses that are built on a scarcity – the thing not being widely available. If you think about some of the coolest successes so far in WordPress, the Gravity Forms, some of the theme businesses, they are inherently predicated on the fact that you have to pay to access them.
\nI’ve always been a fan of businesses that grow with ubiquity, that become more powerful the more ubiquitous they are, more valuable. WordPress itself is one of these. Akismet is one of these. Jetpack is certainly one of those.
This approach brings up the question of whether or not a commercial plugin developer can run a successful business while giving the code away for free on GitHub. A select few are finding that the benefits of community contribution and feedback outweigh the risk.
\nHaskin’s frontend editing plugin is a prime candidate to explore this approach, as this type of plugin was created for users of all technical skill levels. Customers interested in this functionality are less likely to be comfortable installing and updating plugins from GitHub. If you’ve been eager to try Lasso but couldn’t get past the $129 price tag, now is your opportunity to download the plugin and put it through the paces.
\";s: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, 15 May 2015 20:22:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:68:\"WPTavern: SiteGround is Organizing Bulgaria’s First PHP Conference\";s:7:\"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=43825\";s:7:\"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/siteground-is-organizing-bulgarias-first-php-conference\";s: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:2868:\"![\"bulgaria-php-conference\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/bulgaria-php-conference.jpg\")
SiteGround is organizing the first ever Bulgaria PHP conference to be held in Sofia, September 25-27, 2015. The company is headquartered in Sofia and its Head of Development, Mihail Irintchev, has been working hard to develop the local PHP community with the eventual goal of hosting a global PHP event.
\nIrintchev was one of the founders of the Bulgaria PHP user group two years ago, which meets regularly in the SiteGround offices in Sofia. The meetups have grown steadily, inspiring him to approach the SiteGround management team about working together to host a PHP conference.
\n“We see value in making it possible for developers from Bulgaria and the region to meet and learn from some of the most prominent minds in the global PHP community,” SiteGround representative Reneta Tsankova said. “It is also an opportunity for our region to once again be recognized as a place with strong IT potential and lots of development talent.”
\nThe speaker lineup for the event has been finalized and includes leaders in PHP community (Michelangelo van Dam, Sebastian Bergmann, Cal Evans, Adam Culp, and more), as well as some influencers from both the WordPress and Drupal communities, including Mario Peshev and Larry Garfield.
\nBulgaria PHP Conference will be a three day event that includes one training day and two conference days. All of the sessions will be conducted in English, as the event is pulling in speakers and attendees from Bulgaria, the Balkans, and other parts of the world.
\nAutomattic is now a confirmed sponsor, along with Mandrill, Shopware, SiteGround, and others. The sponsors make it possible for organizers to keep the event accessible to as many attendees as possible with lower ticket prices. The earlybird price for the conference pass is just 65 euro.
\nSofia hosted WordCamp Europe 2014 and the city is home to a vibrant IT community. If you’re looking to expand your PHP skills and connect with other passionate developers, the Bulgaria PHP Conference is one you’ll want to consider adding to your calendar for September.
\";s: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, 15 May 2015 18:15: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: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:18:\"Matt: Trojan Emoji\";s:7:\"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=45050\";s:7:\"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/05/trojan-emoji/\";s: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:588:\"\nAndrew Nacin, lead developer of WordPress, just finished a talk at Loopconf, where he talked about a series of related WordPress security fixes that spanned two years, with the final fix included into WordPress core under the guise of Emoji support.
Post Status has a good look at some of the really deep security work that has been going on in WordPress lately. There will always be more problems, but we’re getting to the point where the problems (and the fixes) are often quite subtle.
\";s: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, 15 May 2015 06:06: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: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:77:\"WPTavern: Beer Directory: A WordPress Plugin for Brewers and Beer Aficionados\";s:7:\"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=43140\";s:7:\"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/beer-directory-a-wordpress-plugin-for-brewers-and-beer-aficionados\";s: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:4464:\"![\"beer\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/beer.jpg\")
Craft beer and WordPress are a magical combination. Both cultures are built on some of the same values, like sharing knowledge and open sourcing happiness. With the explosion of the craft beer scene over the past few years, many new breweries are opting to build their websites on top of WordPress. When you’re bootstrapping a new brewery, the last thing you need to spend money on is proprietary software.
\nThe WordPress community has many free and open source tools that developers can use to build a beer-centered website. Beer Directory is a new plugin released this year by Jami Gibbs, founder of Rescue Themes. She created it to support beer listings on her commercial Brewery theme.
\nBeer Directory gives you an easy way to enter beers and their details in the admin. It allows you to categorize and group beers, enter details, and display listings via a configurable shortcode. The post type includes fields for ABV, IBU, OG, FG, SRM/Color, Malts, Hops, and Yeast.
\n![\"beer-profile\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/beer-profile.jpg\")
I tested the plugin by adding the details from a blueberry sour beer recipe. The output for an individual listing on the frontend will look something like this, depending on your active theme:
\n![\"beer-listing\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/beer-listing.jpg\")
The plugin includes a shortcode for listing an individual beer: [beer id=\"17\"] and one for displaying all listings: [beer]. The shortcodes can be configured by count, category, id, and any of the WordPress Order & Orderby Parameters. Beer posts also include support for a featured image.
Be advised that this is not a beer recipe plugin, so there’s no easy way to enter your hop schedule, amounts for fermentables, temperatures, etc. Beer Directory was created purely for listing beers on the frontend with a few key details. If you need to enter beer recipes, the BeerXML Shortcode plugin, created by Derek Springer, is a more suitable option.
\nThe Beer Directory plugin is perfect for home brewers, professional breweries, or even beer enthusiasts who want to maintain a personal library of beers they enjoy. With this data saved in a custom post type, it will be transferable no matter how many times you change your WordPress theme. In addition to keeping track of your beers, the admin listing allows you to easily search and sort your library.
\n![\"beer-in-the-admin\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/beer-in-the-admin.jpg\")
After testing the plugin, I can confirm that it works as advertised. Beer Directory is fully translatable and available for free on WordPress.org. If you want to contribute to development, the plugin can also be found on GitHub.
\";s: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, 15 May 2015 01:31: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:\"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: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:72:\"WPTavern: cPanel’s Site Software Addon Disables WordPress Auto Updates\";s:7:\"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=43609\";s:7:\"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/cpanels-site-software-addon-disables-wordpress-auto-updates\";s: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:8988:\"A little more than two months ago, Derek Munson, who goes by the username Drumology2001 published a thread in the WordPress.org support forums. While performing maintenance on several WordPress sites on his virtual private server, Munson discovered a number of them running outdated versions. Versions ranged from 3.9 to 4.1 with at least one site using WordPress 3.9.2.
\n\nI’m used to seeing the ‘nag’ at the top of the screen that lets me know there’s a newer version available. I am not seeing that on any of these sites which aren’t on the newest version (4.1.1). When I go to Dashboard > Updates and click ‘Check Again’ to force a manual check, it’s still acting as though everything is up to date when it’s clearly not.
Initially, Munson thought All in One WP Security and Firewall was blocking update notifications. Mbrsolution, the plugin’s main developer, confirmed that it doesn’t block update notifications. After completing a number of troubleshooting techniques suggested by volunteers on the WordPress support forum, Munson installed Wordfence Security, a WordPress security plugin.
\nOne of Wordfence’s noteworthy features is its scanner. It compares clean WordPress core files to those on the server and notifies the user if it detects a difference. Results of the scan shows three files had been changed.
\nwp-admin/includes/update.php
\nwp-admin/update-core.php
\nwp-admin/includes/class-wp-upgrader.php
These files were only changed on WordPress sites that were installed using cPanel’s Site Software addon.
\nWordPress’ update.php file.
\nfunction get_core_updates( $options = array() ) { $options = array_merge( array( \'available\' => true, \'dismissed\' => false ), $options ); $dismissed = get_site_option( \'dismissed_update_core\' );
cPanel’s update.php file.
\nfunction get_core_updates( $options = array() ) { # cPanel override: Disable all core updates to prevent conflict with cPAddons. return false; $options = array_merge( array( \'available\' => true, \'dismissed\' => false ), $options );
WordPress’ update-core.php file.
\nfunction core_upgrade_preamble() { global $wp_version, $required_php_version, $required_mysql_version; $updates = get_core_updates();
cPanel’s update-core.php file.
\nfunction core_upgrade_preamble() { # cPanel override: Do not display the current or the latest version, because we\'ve disabled updates. return; global $wp_version, $required_php_version, $required_mysql_version; $updates = get_core_updates();
WordPress’ class-wp-upgrader.php file.
\npublic function is_disabled() { // Background updates are disabled if you don\'t want file changes. if ( defined( \'DISALLOW_FILE_MODS\' ) && DISALLOW_FILE_MODS ) return true;
cPanel’s class-wp-upgrader.php file.
\npublic function is_disabled() { return true; // Force this functionality to disabled because it is incompatible with cPAddons. // Background updates are disabled if you don\'t want file changes. if ( defined( \'DISALLOW_FILE_MODS\' ) && DISALLOW_FILE_MODS ) return true;
The code added by cPanel disables core WordPress updates, update notifications, and automatic background updates to point releases. Once Munson restored these files to their original version, automatic updates and notifications worked properly.
\nThose who manage dedicated servers or virtual private servers with cPanel have the ability to use cPAddons. According to cPanel documentation, “Addons are applications that work with cPanel to perform functions for your users’ websites. Examples of these applications include bulletin boards, online shopping carts, and blogs.”
\nGeorge Stephanis, a WordPress core contributor and lead developer of Jetpack publicly called out cPanel’s actions as a bad practice.
\n\n\nWait, seriously? @cPanel is hacking WordPress core to prevent updates? I\'m kinda dumbfounded by how bad of an idea this is. #donthackcore
\n— George Stephanis (@daljo628) May 11, 2015
A representative of cPanel saw the tweet and responded that they’d like to receive more information.
\n\n\n@daljo628 re: @cPanel w/ @WordPress we would like to get more info from you can you provide a email? Or email into sales @ cpanel dot net^MR
\n— cPanel Cares (@cpanelcares) May 11, 2015
Stephanis engaged in a lengthy conversation with cPanel representatives explaining why it’s a bad idea to disable core updates. cPanel disables WordPress’ native update system because it could cause conflicts with cPanel’s Site Software version of WordPress.
\n\nWe generally release the latest version of WordPress within 1 to 5 days of the latest WordPress update. At a minimum, server administrators are informed each night of all Site Software applications that need updated. It is up to users to configure their notifications within cPanel to receive such updates.
\nThe way our cPAddons tool tracks software is not compatible with the way WordPress updates, hence why we disable the auto-updates so we can track it through cPAddons.
cPanel goes on to explain how updates are handled for software installed using its Site Software cPAddon.
\nBy default, software installed by cPanel is configured to update automatically but some of Munson’s sites didn’t update. He also didn’t receive update notifications for those sites. cPanel believes there is something wrong with Munson’s server configuration and pledged to contact him to find out more information.
\n\nBased upon what Drumology2001 reported on the forum, it appears something is amiss on that server. We’d love to examine that server to determine why WordPress updates were not available to the user.
\nBased upon the fuzzy dates used on the forum and compared with our internal records, the 4.1.1 update was available to the Site Software system prior to the initial post. We’ll reach out to him to determine whether there is anything we can do there.
The good news is that cPanel is responsive and willing to make any necessary changes to improve the update process. Considering how many webhosting companies offer customers the ability to install WordPress with a one-click installer, it’s important that sites receive updates as soon as possible.
\nIf you installed WordPress through cPanel’s one-click installer, check to make sure your site is running WordPress 4.2.2 which is the latest stable version.
\";s: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, 14 May 2015 19:45: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: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: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:61:\"WPTavern: All Sessions from LoopConf Now Available on YouTube\";s:7:\"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=43528\";s:7:\"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:\"http://wptavern.com/all-sessions-from-loopconf-now-available-on-youtube\";s: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:4590:\"![\"photo](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/loopconf-2015.jpg\")
photo credit: LoopConf\nLoopConf, a new WordPress conference created for developers, was held in Las Vegas last week with a world-class lineup of speakers. The event was such a success that the organization team is already planning for 2016.
\n\n\n#loopconf 2016?! We’ve committed to year 2 and are already making plans! Get on the super early interest list here: http://t.co/23y5pL4qWv
\n— LoopConf (@loopconf) May 13, 2015
Attendees were impressed with the professional planning of the event, speaker selection, and the quality of the venue.
\n“I’m going to say, with emphasis, what I think everyone is probably thinking: LoopConf is what you wish most WordCamps were,” Speaker and attendee John James Jacoby said in his writeup.
\n“I like that WordCamps are casual and inviting, and I like that conferences like LoopConf and the WordPress.com VIP Workshop strive to achieve something more professional. I think there will be some WordCamps that try to upgrade themselves to compete, and others that will purposely stay intimate and niche,” Jacoby predicted.
\nThe entire WooCommerce development team was also in attendance at LoopConf and Patrick Rauland found interacting with other developers from the community to be the highlight.
\n“The biggest takeaway that I got from Loop was that conferences are about people,” he said. “Not that cheesy networking where you try to meet as many people as possible. It’s about meeting people and really getting to know them.”
\n![\"LoopConf](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/loopconf-party.jpg\")
LoopConf attendees at the SiteGround party – credit: LoopConf\nThose who could not attend may have missed out on the networking, but videos for all of the sessions are now available on YouTube. One favorite session among attendees was Andrew Nacin’s presentation on The Anatomy of a Critical Security Bug, during which he revealed that the Emoji support added in WordPress 4.2 was also part of a larger plan to fix a two-year old security vulnerability.
\nAttendees also enjoyed Ghost founder John O’Nolan’s session on The Economics of Open Source, Ryan McCue’s “How to Build a REST API for 23 Percent of the Web,” and Google engineer Ilya Grigorik’s Performance Guide RAIL keynote presentation. If you have some free time to devote to improving your development knowledge, the LoopConf videos make up a small library of advanced learning on a variety technical topics.
\nLoopConf attracted 210 attendees as a brand new WordPress event this year. Glowing accounts of its professional handling are likely to increase attendees next year. LoopConf 2016 is already in the planning stages, but the location is yet to be decided.
\";s: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, 14 May 2015 19:05: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: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:76:\"WPTavern: WPWeekly Episode 192 – Infinite Possibilities With Dan Griffiths\";s:7:\"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=43747&preview_id=43747\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"http://wptavern.com/wpweekly-episode-192-infinite-possibilities-with-dan-griffiths\";s: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:3306:\"In this episode of WordPress Weekly, Marcus Couch and I are joined by Dan Griffiths, founder of Section214. We spend the first half of the show learning about Griffiths’ interest in technology at a young age.
\nOnce out of the military, Griffiths experienced difficulties finding a job. He discovered Easy Digital Downloads and explains how working on a ticket and creating an API led to getting a job offer from Pippin Williamson. Since accepting the job offer, Griffiths has published 22 plugins to the WordPress plugin directory and has attended several WordCamps.
\nLater in the show, we discuss HostPress, an open-source, extensible server control panel built on top of WordPress. He describes his motivation behind the project and why he thinks webhosts need a better solution. Near the end of the interview, Griffiths shares his thoughts on the WP REST API that will eventually be added to WordPress and what it means for the project’s future.
\nHeroes Are Found In Unexpected Places
\nWordPress 4.3 to Focus on Mobile Experience, Admin UI, Better Passwords, and Customizer Improvements
WP Rollback lets you quickly and easily rollback any theme or plugin from WordPress.org to any previous or newer version. It works just like the plugin updater, except you’re rolling backward or forward to a specific version. Be sure to read our review of WP Rollback on the Tavern.
\nLinkedin_Oauth allows users to login and register into WordPress using their LinkedIn account.
\nStrong Password Generator created by Frankie Jarrett, encourages the use of strong passwords by helping users generate them easily.
\nNext Episode: Wednesday, May 20th 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 #192:
\n
Wearable gadgets portend vast health, research and privacy consequences, the Washington Post takes on the quantified self. I’m in the medium end of this, I track pretty much everything that’s easy, but no blood / hormone tests yet.
\";s: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, 14 May 2015 05:04: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:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"WPTavern: WP Engine Rolls Out WP-CLI Support to Select Partners for Beta Testing\";s:7:\"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=43693\";s:7:\"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:90:\"http://wptavern.com/wp-engine-rolls-out-wp-cli-support-to-select-partners-for-beta-testing\";s: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:3885:\"![\"wp-engine\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/11/wp-engine.jpg\")
WP Engine is currently beta testing WP-CLI support with approximately 200 select partners. Those who serve clients that host with the company are eager to see it rolled out to more customers, as WP-CLI has become an indispensable part of many WordPress developers’ workflow.
\n\n\nWP-CLI on @wpengine! From the entire WordPress Community, THANK YOU!!!!!
\n— Brad Williams (@williamsba) May 13, 2015
“We find that with technical products it’s often better to roll out to development partners who we have a prior working relationship with, to get candid feedback from highly technical folks, and thus build a better product before rolling to a wider audience,” founder Jason Cohen told the Tavern.
\nThere is no set timeframe for beta, but Cohen said that the plan is to offer WP-CLI support to all customers on all plans.
\n“Our timeframe for exiting beta is like one of the rules of Fight Club: ‘The beta goes on for as long as it has to,\'” he said. “If everything is smooth and few issues arise, we can roll faster, but if we find things we want to fix, it will take longer. The main thing is to release high quality product, not to release it as quickly as possible.”
\nMany other hosting companies that cater to WordPress customers, such as Bluehost, SiteGround, and Site5, have had WP-CLI pre-installed for years, which makes it curious that WP Engine has taken so long to add support for it. Cohen says that it’s trickier when you plan to offer it to all customers.
\n\nSome of our competitors offer WP-CLI only on dedicated plans, not on shared plans, whereas we offer it on all plans. An example of why it’s tricker: there are security implications (e.g. when running system commands outside of the PHP sandbox, which many WP-CLI commands do) in a multi-tenant system that are less of a concern in a dedicated system. We wanted to take the time to get all that right.
Cohen said that it wasn’t hard to come to the decision to support WP-CLI but WP Engine has been concurrently working on launching other technical tools. Most recently, the company has been focusing on polishing Mercury, its enterprise HHVM hosting platform, which launched last year.
\n“We’ve been building and releasing features that no one else has,” Cohen said. “So, sometimes we’re first-out with a feature, and sometimes not. That seems natural in a market with a dozen good competitors, all innovating in the space.”
\nDevelopment partners who have been granted access to WP-CLI during the beta period can find a list of known issues in the WP Engine documentation, which includes a list of commands that are currently not supported. Documentation will be updated throughout the beta period to reflect progress on issues reported by testers.
\";s: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, 13 May 2015 23:51: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: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:84:\"WPTavern: WP Rollback Provides Basic Versioning for WordPress.org Plugins and Themes\";s:7:\"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=43696\";s:7:\"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/wp-rollback-provides-basic-versioning-for-wordpress-org-plugins-and-themes\";s: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:\"![\"The](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/undo-button.jpg\")
The undo key from a computer keyboard\nDespite the recent proliferation of plugins that add git-based version control to WordPress, your average user does not require a full-blown version control system as part of regular site management. Developers can certainly benefit from tools like Revisr and Gitium for managing projects with Git, but the vast majority of WordPress users are more likely to benefit from a simple “undo” button for mistakes or bad updates.
\nWP Rollback is a new plugin that brings the concept of an “undo” button to updates for plugins and themes hosted on WordPress.org. It allows users to easily rollback to any previous (or newer) version without the hassle of manually downloading files.
\n![\"wp-rollback\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback.jpg\")
Clicking the Rollback link will take the user to a screen where he can select from a list of previous versions or update to newer ones.
\n![\"wp-rollback-versions-screen\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback-versions-screen.jpg\")
WP Rollback uses WordPress’ native plugin updater to revert to previous versions.
\n![\"wp-rollback-update\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback-update.jpg\")
While using older versions of themes/plugins is not generally encouraged, there are times when it’s unavoidable. For example, some plugin authors routinely push out buggy updates, seemingly without having run any tests on them, and then rely on their users to discover and report the problems. It can sometimes be 24 – 72 hours before the author has the chance to push out a fix to the buggy update. WP Rollback allows users to quickly revert to the previous working version of the plugin.
\nAs themes hosted on WordPress.org do not yet have change logs, there may be times when a user updates to a new version of a theme where the author has made some major changes to the markup and/or styles. Without a changelog, the user has no idea what is included in the update or how it might impact a child theme or plugin’s output. WP Rollback gives you the ability to test a theme update and quickly rollback if necessary until you’ve had the chance to get your site ready.
\nMost WordPress users do not have a development environment in place for putting software updates to the test before rolling them out. They simply expect updates to work, but there will always be those rare instances of unforeseen conflicts and bugs. Having WP Rollback in place should help users to be less wary about taking updates, since they know they can easily rollback if something goes wrong.
\nWordImpress, the folks behind WP Rollback as well as the new Give plugin, encourages users to backup their sites before performing plugin/theme updates or reverts. Ideally, you would test any changes in a development environment first to ensure that everything works as planned. WP Rollback is available for free on WordPress.org and documentation can be found on GitHub.
\";s: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, 13 May 2015 19:34:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:24:\"Matt: Advanced Hindsight\";s:7:\"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=45039\";s:7:\"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:40:\"http://ma.tt/2015/05/advanced-hindsight/\";s: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:612:\"\nBeginning with the 2015 academic year, the Center for Advanced Hindsight (CAH) at Duke University will invite promising startups to join its behavioral lab and leverage academic research in their business models. The Center is housed within the Social Science Research Institute at Duke University and is led by Professor Dan Ariely, Professor of Psychology and Behavioral Economics at Duke University.
This is a pretty awesome opportunity for entrepreneurs, I hope a reader of this blog pursues it.
\";s: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, 13 May 2015 04:19: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: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:98:\"WPTavern: Major Changes to WordPress.org Guidelines Should Have a Request for Comments Time Period\";s:7:\"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=43595\";s:7:\"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/major-wordpress-org-guideline-changes-should-have-a-request-for-comments-time-period\";s: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:7603:\"For the last three years, the WordPress Theme Review Team has tried to encourage theme authors to adopt the Theme Customizer. In April, the decision was made by the TRT to no longer encourage, but require all theme options to be in the customizer. Although the decision was three years in the making, the community didn’t have an opportunity to provide feedback until after the requirement was put in place.
\n![\"Estimated](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2014/07/EstimatedReadingTimeFeaturedImage.png\")
photo credit: Eyesplash – let’s feel the heat – cc\nThose who follow the official TRT blog likely saw the writing on the wall. With the release of WordPress 3.4 in 2012, which introduced the theme customizer, the TRT held discussions on proposed changes to the theme review guidelines. One of the proposed changes recommended theme options be incorporated into the theme customizer. Of particular interest is a conversation between Justin Tadlock and Chip Bennett on whether or not the customizer should be recommended so early.
\nIn November of 2014, the team held a meeting to discuss modifications to the theme review guidelines. Up until this point, theme authors were allowed to create theme options in one of three ways, Theme Customizer, Settings API, or with custom options pages using the Theme Mods API.
\nDuring the meeting, Tadlock suggested that the team should strongly recommend theme authors to use the customizer. Members in attendance agreed and the theme review guidelines changed to strongly recommend theme options be placed into the customizer.
\nA few days after the meeting, Tadlock published a post asking how do we solve the theme options problem? He highlights the lack of educational resources on the customizer as one of the major culprits of its slow adoption.
\n\nOne of the things I’ve always hoped the TRT would become is more of an educational team. I firmly believe that if we didn’t have to spend so much time dealing with theme options, we could spend more time on educating in other areas of the dev/design.
\nI’m writing this post because I believe this to be the biggest hangup with themes today. It’s the hardest part of the review process. It’s also one of the most critical because theme options means potential security issues.
The post opened up a dialogue to discuss ways of dealing with several issues related to getting developers to adopt and use the customizer. Bennett published a post a few days later that explained APIs related to theme options. It was later followed up by Tadlock with a post on choosing Theme Mods API or Settings API.
\nFast forward to April 2015, the team held a meeting and unanimously agreed to require theme authors to place theme options into the customizer. A day later, Tadlock explained why the change was made and how the team came to its decision.
\n\nFirst, I want to say that the team did not take this decision lightly nor did we make it quickly. In fact, this has been an ongoing discussion for nearly 3 years (since the customizer was first introduced in core). Many of us had originally hoped that we could take a more organic approach to this and allow theme authors to naturally make the switch on their own given enough time.
The decision created a passionate, lengthy conversation with several people chiming in after the fact on WP Tavern.
\n![\"Future](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/03/FutureOfCommentingFeaturedImage.png\")
photo credit: Marc Wathieu – cc\nOn the TRT blog, there are several blog posts that encourage feedback, especially on guideline proposals. In this instance however, feedback, concerns, and criticism weren’t encouraged until after the decision was made.
\nThe TRT usually publishes an agenda that highlights what topics will be discussed during the meeting. An agenda was published for the April 14th meeting but not for the April 21st meeting. This means only those in attendance were able to voice an opinion and vote on the issue, as there was no advance notice.
\nI understand the team has discussed this change for the last three years, but I would like to have seen a request for comments period for at least a month on the TRT blog.
\nThis way, people could comment on the decision before it was implemented. The team could have controlled the conversation, provided a more accessible way of participating in the discussion versus Slack, and heard legitimate concerns from theme developers.
\nI hope major changes like this in the future are addressed in a way where the public can be more involved. The notion that concerned parties should have been in Slack during the meeting to voice concerns before the decision was made is unacceptable. People have things to do and while I think Slack is easier to use than IRC, a blog post with a comment form is accessible to a lot more people.
\nAn RFC period doesn’t make sense for a lot of what takes place in the world of WordPress development but a change that affects current, past, and future themes in the directory is a great example of where it does makes sense.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 May 2015 22:10:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:93:\"WPTavern: Customizer Theme Resizer Plugin Offers Live Previews of Your Site on Mobile Devices\";s:7:\"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=43599\";s:7:\"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:103:\"http://wptavern.com/customizer-theme-resizer-plugin-offers-live-previews-of-your-site-on-mobile-devices\";s: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:3729:\"![\"customizer-theme-resizer\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-theme-resizer.jpg\")
Contributors on the upcoming WordPress 4.3 release are moving full speed ahead with plans to improve the experience of using the customizer. They’re also exploring ways to re-architect it to make way for feature plugins that would bring in additional functionality.
\nWordPress core contributors have continually demonstrated a commitment to improving the customizer to make it better for everyone, and the Theme Developer Handbook was recently updated with a comprehensive guide to using the Customizer API. Plugin developers are also finding new ways to extend the customizer to support the increasing number of users who depend on it for live previews.
\nCustomizer Theme Resizer is a new plugin that is immensely useful for previewing your site on various mobile devices while adjusting options in the customizer. The plugin was created by Japanese web developer Tatsuki Ohta, who has 10 other extensions listed in the official directory. It allows you to review your design for responsiveness without having to leave the customizer panel.
\n![\"customizer-theme-resizer-screenshot\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-theme-resizer-screenshot.jpg\")
Customizer Theme Resizer offers nine preset mobile phone/tablet display options, or you can manually add your own screen dimensions. You can also easily switch between portrait or landscape mode.
\nThe plugin works seamlessly within the customizer, so you can set it to iPhone 6, for example, and live preview any of your design choices on that device. This is especially helpful when uploading a site logo or a header image if you want to see how those images resize down for devices. It keeps you from having to go back and forth while making adjustments and testing responsiveness on your phone or simulator.
\nI tested the plugin and found that it works as advertised. You can see a quick overview of how it works in the video below:
\n\n
As a result of the WordPress.org Theme Review Team’s decision to enforce the use of the customizer for theme options, more themes will be moving to support the customizer ahead of the deadline to comply. The Customizer Theme Resizer plugin is a handy tool to use in conjunction with any theme that supports the customizer. Install the Customizer Theme Resizer plugin from WordPress.org the next time you want to live preview the mobile-friendliness of your design adjustments.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 May 2015 21:52:25 +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: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:71:\"WPTavern: 3 Big Things that Will Happen to WordPress in the Near Future\";s:7:\"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=43611\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"http://wptavern.com/3-big-things-that-will-happen-to-wordpress-in-the-near-future\";s: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:6711:\"![\"petersuhm\"](\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/petersuhm.jpeg\")
This opinion piece was contributed by guest author Peter Suhm. Peter is a web developer from the Land of the Danes. He is the creator of WP Pusher and a huge travel addict, bringing his work along with him as he goes.
\n
Okay, I admit that the title of this post is a bit risky. Honestly, it should probably have been “3 Big Things That I Wholeheartedly Hope Will Happen To WordPress In The Not Too Distant Future”. That being said, I am optimistic by nature, and I actually think these three ideas are realistic scenarios. So in all modesty, and without further ado, here is my take on some of the next big things to happen in the WordPress world in the near future.
\nThere is no question about it. WordPress needs some sort of dependency management mechanism. We have seen all other fragments of the PHP community, and other languages too, adopt the use of dependency managers. Most likely, WordPress will adopt Composer in some form, either out-of-the-box or by configuration.
\nA dependency manager is a software tool that can resolve and manage the dependencies (other libraries) that a given library requires. In PHP we have Composer. Each PHP library that supports Composer will have a defined set of dependencies that it depends on. The role of Composer is to fetch all these dependencies and make sure they are all compatible with each other.
\nWordPress needs one so we do not have to reinvent the wheel every time we want to make a new plugin or theme. Every time we write code for WordPress when we could have used one of the existing PHP packages out there, we are essentially wasting our time. Allowing the use of third-party dependencies allows for much more rapid development and better security. So many security issues in WordPress plugins are the same ones showing up again and again.
\nIn the short run, for plugin developers, WordPress adopting a dependency manager will mean a huge opportunity for making WordPress specific plugins for all the existing PHP libraries out there. When this happens, we will see hundreds, if not thousands, of plugins that will just be WordPress wrappers around existing libraries. Some of these plugins will end up becoming very popular. So be ready if you are an upcoming plugin author!
\nWordPress developers will probably also have to deal with some sort of frontend dependency manager, since, with the WP REST API, a lot of things will be revolutionized on the frontend side of things. We will touch more on that in the next section.
\nThis is not my idea, but I am certain this is the way we are moving. With the WP REST API in core, WordPress will essentially be a backend, complete with user management and so forth, for your API-based web application. Themes are going to be JavaScript based and will communicate with WordPress through the API. Plugins will stay mainly PHP, with a dash of JavaScript, just as the backend itself will.
\nI believe that a main reason for WordPress’ widespread success is the dashboard. It is extremely user friendly and intuitive. Add to that how simple and easy it is to add 3rd party plugins and themes and you have a winner. Extending core is also really trivial because of all the actions and filters that WordPress has built in. There is no way that the WP REST API is going to change this. It is simply adding an extra layer for frontend developers, and most likely, radically changing how we work with theming.
\nA few years ago, I worked as a full time Ruby on Rails developer. For one project, we needed some kind of CMS to manage the content of our Rails app. One of the developers (a hardcore Ruby guy) suggested using the WordPress dashboard as a backend and just build a simple API around it. We never ended up doing that, but imagine how easy that would be to implement had the API been around at the time.
\nIf you are a WordPress theme developer, this means that in the future you will probably not be a WordPress developer any more. You will “just” be a theme developer. You better up those JavaScript skills before this happens.
\nAs a result of all this, WordPress will become a lot more decoupled. Obviously, the biggest cut will be between the backend (dashboard and plugins) and the front end (themes). It is also easy to imagine, with an adaptation of Composer, that core itself will become a lot more decoupled. Maybe similar to how the Laravel framework is split up into the Illuminate packages (now we will have to define what “near future” means, though).
\nAs already mentioned, the main component will be the dashboard. Plugins makes sense to keep as a part of the dashboard, but in the future, they might look more like WordPress-specific Composer packages. It makes sense to keep all this in PHP – of course with a bit of JavaScript here and there.
\nAnother thing to consider is that if Composer is adopted in the near future, that would naturally mean an upgrade of the minimum required PHP version. That will probably happen very soon, anyways. We might see some sort of frontend plugins as well, but these will be JavaScript and be managed through a frontend dependency management tool.
\nThis means that if you are a WordPress plugin developer, you can keep writing good old PHP code. No need to jump straight over to NodeJS, yet, but if you are a theme developer, you might want to keep an eye on what those guys are up to.
\nIt also means that WordPress is going to be much more decoupled and customizable. You will be able to pick the parts you need and skip the rest. If you need something different, you will most likely be able to find an existing PHP package that can do the job. Sounds good, right?
\nThese are my 5 cents. I am curious to hear what you think. Where is WordPress headed?
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 12 May 2015 18:15:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:106:\"WPTavern: BuddyPress 2015 Survey Shows Increase in English-Speaking Communities and Commercial Theme Usage\";s:7:\"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=43531\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"http://wptavern.com/buddypress-2015-survey-shows-increase-in-english-speaking-communities-and-commercial-theme-usage\";s: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:6558:\"![\"2015-bp-survey-results\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/2015-bp-survey-results.jpg\")
The BuddyPress 2015 survey results are now available. This year’s survey did not have the same community penetration as 2013 and 2014, with 37.5% fewer respondents, but the information is still valuable for gauging how and where people are using the plugin. Volunteers collected feedback from 211 participants in 42 different countries.
\nFeedback this year shows a few significant shifts from previous years, especially when it comes to languages used on BuddyPress sites. The top three languages in 2015 are English (69.23%), French (10.26%), and German (7.69%). In 2013, language usage was fairly evenly divided between English (56%) and non-English sites.
\nOn the surface, the language results seem to indicate a shrinking international community, but it may be due to the fact that the survey lost participants from 20 countries captured the previous year.
\nResults indicate that 34% of community managers and developers surveyed are building BuddyPress sites with commercial WordPress themes that offer custom BP CSS and/or template modifications. That number is up from 26% the previous year, likely due to more BuddyPress themes entering the market.
\nAccessing BuddyPress sites via mobile is also slowly on the rise with 63% of respondents reporting that they’ve used a smartphone to access their sites. It’s no surprise that the survey shows mobile responsiveness is one of the most important factors in theme selection.
\nOther preferred BuddyPress theme features include compatibility with the latest BP version and a light/fresh design. This preference may be due to kinds of sites that users are building, which remain fairly unchanged from previous years:
\nResults show that the most used BuddyPress components are Extended Profiles (71.13%) and Activity Streams (66.49%), followed by User Groups (57.22%). Although Profiles and Activity remain dominant, they are waning slightly from the previous year while Groups are increasing in popularity.
\n![\"bp-components-usage\"](\"http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/bp-components-usage.png\")
Surprisingly, Friend Connections, which are often associated with social networks, rank quite low on the list of components, trailing Messaging, Notifications, and Account Settings. Site Tracking, a feature used most often with multisite, ranks dead last among components that are always activated at just 8.25%.
\nIf you take a look at the features on track for BuddyPress 2.3, the direction of development seems to be trending toward improving the components that users are mostly likely to activate. Last year’s major performance improvements reduced BuddyPress’ footprint by up to 75% in many places, especially for sites that rely on activity and member directories.
\nThe recent additions of the Member Types API and upcoming Attachments API greatly improve the extensibility of components that BuddyPress site administrators are most frequently using. The survey results confirm that BP core development is being shaped by community feedback and overall the software is improving for those that are actively using it.
\nThe anonymous comments on the survey provide some critical feedback that indicate it may be time for BuddyPress contributors to reconsider how the software is presented to the world. One respondent feels that the tagline “social networking in a box” is inaccurate, given recent developments in other social networking software:
\n\nBuddyPress is some distance behind the features people now expect of modern social networks. OK for school, or small intranet purposes, but to call it ‘social networking in a box’ is slightly stretching reality.
BuddyPress also continues to be somewhat daunting for beginners. Developers can be sold on its extensibility, but your average user trying to set up a social network will have a sharp learning curve when it comes to adding features beyond what is offered in BP core. That frustration, when it comes to extending the software, seems to make its way into users’ opinions of BuddyPress in general.
\n\nI’ve been trying to learn BuddyPress for about a year. Setup is super easy. Mods are always a pain. I understand this has to do with community support. Everybody wants answers. Few pitch in to help.
This year’s survey results and user feedback provide BuddyPress core contributors and volunteers with some important ideas to consider for shaping both development and community support in the future. The full results of the survey are available on GitHub with a more detailed breakdown and charts for each question.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 11 May 2015 19:31:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:35:\"Matt: New Yorker on Marc Andreessen\";s:7:\"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=45044\";s:7:\"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:\"http://ma.tt/2015/05/new-yorker-on-marc-andreessen/\";s: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:371:\"Tad Friend has a great New Yorker profile of Marc Andreessen, one of my favorite people to debate and talk to (though it happens all too rarely). Check out Pmarca Says if you want to catch up on some of his recent thinking from tweetstorms.
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 11 May 2015 15:56:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:66:\"WPTavern: Gazette: A Free WordPress Magazine Theme from Automattic\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"http://wptavern.com/?p=43501\";s:7:\"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/gazette-a-free-wordpress-magazine-theme-from-automattic\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3367:\"Gazette is a new WordPress magazine theme from the folks at Automattic, designed by Thomas Guillot. Since the majority of themes produced for WordPress.com are well-suited to single author blogs, Gazette’s fine-tuned focus on digital publications is a welcome addition to the collection.
\nMagazine themes are generally few and far between, because they have to be designed for a constant flow of content with a homepage that allows the reader to quickly scan multiple featured stories. Gazette takes a minimalist approach to the magazine style in that it isn’t cluttered with skinny columns of varying widths, obtrusive advertising slots, etc. It could easily be used for a personal blog or photography site.
\n![\"gazette-homepage\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-homepage.jpg\")
As you scroll down the page, the sticky navigation/search bar pins the menu to the top for easy access. Gazette makes a strong impression with fullscreen featured images that display above post and page titles. The content area has been decluttered for readability with post meta pulled out into a separate column.
\nGazette supports image, gallery, video, and link post formats. The theme includes two optional widget areas (the right sidebar and footer), and two custom menus. With Jetpack active, Gazette adds an option to upload your site logo. The plugin also manages the featured content display, along with the related posts functionality seen in the live demo.
\n![\"gazette-author-bio\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-author-bio.jpg\")
Gazette includes a handful of layout and content options in the customizer:
Gazette is responsive and maintains its striking visual appeal and readability on mobile devices. The design is similar to popular mobile news apps that display posts with titles overlayed on featured images.
\n![\"gazette-responsive\"](\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-responsive.jpg\")
Check out the live demo on WordPress.com to see Gazette in action. The theme is not yet available on WordPress.org but should be soon. In the meantime, the zip file for self-hosted sites can be downloaded from the sidebar of the Gazette theme page on 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 11 May 2015 06:30: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:\"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:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Matt: Undercity\";s:7:\"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=45042\";s:7:\"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:31:\"http://ma.tt/2015/05/undercity/\";s: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:190:\"A great video going underneath the streets of New York, Ninja Turtle Style:
\n\n
Hat tip: Beau.
\";s: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 May 2015 15:47:46 +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: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:24:\"Matt: Hint Water Founder\";s:7:\"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=45037\";s:7:\"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:\"http://ma.tt/2015/05/hint-water/\";s: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:585:\"\nWhen Kara Goldin started putting fruit in her water 10 years ago, she had no idea that she had stumbled upon a business idea that would eventually lead to the creation of a new category in the beverage industry, grow to a 40 million dollar company, and help her lose over 25 pounds in the process.
Cool interview with Kara Goldin, the founder of Hint Water, which I drink 3-4 of a day and is also an Audrey company.
\";s: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 May 2015 03:42: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: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: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:29:\"Post Status: The trojan Emoji\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=12600\";s:7:\"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:40:\"https://poststatus.com/the-trojan-emoji/\";s: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:5500:\"Andrew Nacin just spoke at Loopconf about the nature of a critical software bug.
\n\nAt a base level, the problems originated in that WordPress did not enable strict mode for MySQL. If STRICT_ALL_TABLES has been enabled, the security vulnerability that was addressed in WordPress 4.2 would not exist.
Without strict mode, MySQL allows more flexible inputs, and doesn’t require the same level of precision in what it allows. For example, a long username would just truncate to the maximum allowed characters, versus be rejected.
\nSince MySQL can do strange things without strict mode enabled, there are obscure but significant ways for hackers to take advantage.
\nA vulnerability was disclosed to the WordPress security team about two years ago. At its core, the method for forcing MySQL truncation was by using four-byte characters, and then using tricks to store nefarious code in the database.
\nNacin used an example of inserting two comments in the database with single quotes and attached four-byte characters. MySQL would truncate the four-byte characters on databases using UTF8 (and don’t allow four-byte characters), and a hacker could utilize the truncated comment (or any other field, really) to add a second comment to finish the exploitation.
\nThe initial vulnerability was fixed in 3.6.1. In 2014, an new disclosure came in from Cedric Van Bochhaven to note that there was still a vulnerability under particular circumstances.
\nAfter months of work and “tens of thousands of lines of code” for rewrites and tests, the team realized that they needed to check inputs to the database at a base level of WordPress.
\nIn WordPress 4.2, approximately 1,000 lines of code were inserted into wpdb.php under the guise of Emoji support, but were really for fixing this vulnerability.
\n![\"utf8mb4\"](\"https://poststatus.com/wp-content/uploads/2015/05/utf8mb4.png\")
The original report identified three requirements for the site to be exposed:
\nIt turned out that really only part of number one needed to be true. They discovered, “this could affect any two fields that would be rendered anywhere near each other.”
\nBetween 11 default database tables and hundreds of fields, basically all parts of WordPress were vulnerable, and core itself also “extensively” relied on non-strict mode functionality.
\nFurthermore, they realized that even three-byte characters could cause truncation, if they aren’t valid upon insertion.
\nSo of the requirements from the original report, most were not actually required.
\n![\"utf8mb4-notreally\"](\"https://poststatus.com/wp-content/uploads/2015/05/utf8mb4-notreally.png\")
\n“We’re deeper and deeper and deeper into this hole, and we have no idea how to get out.”
The team went back to a discussion from the 3.6.1 vulnerability fix, that does what Nacin calls “preflight checks” that checks many layers of WordPress to ensure allowed data is being inserted.
\nChecking allowed character sets was not only on the database and table level, but also on columns and fields. Furthermore, the client, the connection, and the server can have their own character sets.
\nNacin defines the method for checking as both using a scalpel and a sledgehammer.
\n\nWe need this to work two different ways: with a scalpel via
update(),replace(),insert(), anddelete(), and with a sledgehammer via write queries viaquery().
The code has been in trunk since January, months before the release of 4.2. But it was there under the guise of Emoji support, as “noone had any idea what it did because it was 1,000 lines of the database abstraction layer to just remove invalid characters.”
\nBecause of how opaque the vulnerability and the corresponding fix were, the team was able to spend a very long time working on and fixing the issue, all without exposing the vulnerability to the general public.
\nWhen 23.9% of the internet uses WordPress, security becomes an even more enormous challenge than in other software. There was an easy fix for this all along: strict mode on MySQL.
\nHowever, it would’ve broken “everything.” Alternatively, exposing a vulnerability to the public without a fix that doesn’t break websites makes the vulnerability that much more powerful. It takes a ridiculous effort for the WordPress core team and security team to ensure practical solutions to keep the WordPress software secure and reliable for millions of users.
\nBy the way, if you ever find a vulnerability in WordPress or you get really excited about problems like these, you can email security@wordpress.org to get involved.
\";s: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, 08 May 2015 20:18:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:27:\"Matt: Where Does Weight Go?\";s:7:\"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=45034\";s:7:\"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/05/where-does-weight-go/\";s: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:156:\"When You Lose Weight, Where Does it Go? I’ll be honest that I had no idea.
\";s: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, 08 May 2015 13:10:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:23:\"Matt: Slot Machine Tech\";s:7:\"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=45031\";s:7:\"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/2015/05/slot-machine-tech/\";s: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:469:\"The Verge: Slot machines perfected addictive gaming. Now, tech wants their tricks. Includes information from one of my favorite authors Nir Eyal, who also spoke at WordCamp San Francisco a few years ago.
\";s: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, 08 May 2015 06:55:58 +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:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";a:10:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Tue, 26 May 2015 04:40:59 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:14:\"content-length\";s:6:\"236727\";s:10:\"connection\";s:5:\"close\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Tue, 26 May 2015 04: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:\"20130911090210\";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (191, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1432658460', 'no'), (192, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1432615260', 'no'), (193, '_transient_timeout_dash_4077549d03da2e451c8b5f002294ff51', '1432658460', 'no'), (194, '_transient_dash_4077549d03da2e451c8b5f002294ff51', '', 'no'), (195, '_transient_is_multi_author', '0', 'yes'); -- -------------------------------------------------------- -- -- Table structure for table `wp_postmeta` -- CREATE TABLE `wp_postmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `post_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- 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/05/header.jpg'), (3, 4, '_wp_attachment_metadata', 'a:5:{s:5:\"width\";i:960;s:6:\"height\";i:250;s:4:\"file\";s:18:\"2015/05/header.jpg\";s:5:\"sizes\";a:3:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:18:\"header-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:17:\"header-300x78.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:78;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:14:\"post-thumbnail\";a:4:{s:4:\"file\";s:18:\"header-624x163.jpg\";s:5:\"width\";i:624;s:6:\"height\";i:163;s:9:\"mime-type\";s:10:\"image/jpeg\";}}s:10:\"image_meta\";a:11:{s:8:\"aperture\";i:0;s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";i:0;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;}}'), (4, 5, '_wp_attached_file', '2015/05/cropped-header.jpg'), (5, 5, '_wp_attachment_context', 'custom-header'), (6, 5, '_wp_attachment_metadata', 'a:5:{s:5:\"width\";i:960;s:6:\"height\";i:250;s:4:\"file\";s:26:\"2015/05/cropped-header.jpg\";s:5:\"sizes\";a:3:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:26:\"cropped-header-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:25:\"cropped-header-300x78.jpg\";s:5:\"width\";i:300;s:6:\"height\";i:78;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:14:\"post-thumbnail\";a:4:{s:4:\"file\";s:26:\"cropped-header-624x163.jpg\";s:5:\"width\";i:624;s:6:\"height\";i:163;s:9:\"mime-type\";s:10:\"image/jpeg\";}}s:10:\"image_meta\";a:11:{s:8:\"aperture\";i:0;s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";i:0;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;}}'), (7, 5, '_wp_attachment_custom_header_last_used_twentytwelve', '1432576189'), (8, 5, '_wp_attachment_is_custom_header', 'twentytwelve'), (9, 2, '_edit_lock', '1432578530:1'), (10, 2, '_edit_last', '1'), (11, 8, '_edit_lock', '1432578539:1'), (12, 8, '_edit_last', '1'), (13, 8, '_wp_page_template', 'default'), (14, 10, '_edit_lock', '1432578561:1'), (15, 10, '_edit_last', '1'), (16, 10, '_wp_page_template', 'default'), (17, 12, '_edit_last', '1'), (18, 12, '_wp_page_template', 'default'), (19, 12, '_edit_lock', '1432578570:1'), (20, 15, '_edit_lock', '1432576391:1'), (21, 15, '_edit_last', '1'), (22, 15, '_wp_page_template', 'default'), (23, 17, '_edit_lock', '1432576445:1'), (24, 17, '_edit_last', '1'), (25, 17, '_wp_page_template', 'default'), (26, 19, '_edit_lock', '1432576479:1'), (27, 19, '_edit_last', '1'), (28, 19, '_wp_page_template', 'default'), (29, 22, '_edit_lock', '1432576526:1'), (30, 22, '_edit_last', '1'), (31, 22, '_wp_page_template', 'default'); -- -------------------------------------------------------- -- -- Table structure for table `wp_posts` -- CREATE TABLE `wp_posts` ( `ID` bigint(20) UNSIGNED NOT NULL, `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' ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- 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, '2015-01-22 13:23:43', '2015-01-22 13:23:43', 'Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2015-01-22 13:23:43', '2015-01-22 13:23:43', '', 0, 'http://www.himanshu-joshi.com/mynewsite/?p=1', 0, 'post', '', 1), (2, 1, '2015-01-22 13:23:43', '2015-01-22 13:23:43', '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:\r\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.)\r\n...or something like this:\r\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.\r\nAs a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!', 'About Me', '', 'publish', 'open', 'closed', '', 'sample-page', '', '', '2015-05-25 18:28:50', '2015-05-25 18:28:50', '', 0, 'http://www.himanshu-joshi.com/mynewsite/?page_id=2', 2, 'page', '', 0), (4, 1, '2015-05-25 17:49:20', '2015-05-25 17:49:20', '', 'header', '', 'inherit', 'open', 'open', '', 'header', '', '', '2015-05-25 17:49:20', '2015-05-25 17:49:20', '', 0, 'http://www.himanshu-joshi.com/mynewsite/wp-content/uploads/2015/05/header.jpg', 0, 'attachment', 'image/jpeg', 0), (5, 1, '2015-05-25 17:49:29', '2015-05-25 17:49:29', 'http://www.himanshu-joshi.com/mynewsite/wp-content/uploads/2015/05/cropped-header.jpg', 'cropped-header.jpg', '', 'inherit', 'open', 'open', '', 'cropped-header-jpg', '', '', '2015-05-25 17:49:29', '2015-05-25 17:49:29', '', 0, 'http://www.himanshu-joshi.com/mynewsite/wp-content/uploads/2015/05/cropped-header.jpg', 0, 'attachment', 'image/jpeg', 0), (6, 1, '2015-05-25 17:52:35', '2015-05-25 17:52:35', '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:\r\n
Hi 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.)\r\n...or something like this:\r\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.\r\nAs a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!', 'About Us', '', 'inherit', 'open', 'open', '', '2-revision-v1', '', '', '2015-05-25 17:52:35', '2015-05-25 17:52:35', '', 2, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/2-revision-v1/', 0, 'revision', '', 0), (7, 1, '2015-05-25 17:52:52', '2015-05-25 17:52:52', '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:\r\n
Hi 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.)\r\n...or something like this:\r\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.\r\nAs a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!', 'About Me', '', 'inherit', 'open', 'open', '', '2-revision-v1', '', '', '2015-05-25 17:52:52', '2015-05-25 17:52:52', '', 2, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/2-revision-v1/', 0, 'revision', '', 0), (8, 1, '2015-05-25 17:53:49', '2015-05-25 17:53:49', 'Hello', 'Portfolio', '', 'publish', 'open', 'closed', '', 'portfolio', '', '', '2015-05-25 18:28:59', '2015-05-25 18:28:59', '', 0, 'http://www.himanshu-joshi.com/mynewsite/?page_id=8', 3, 'page', '', 0), (9, 1, '2015-05-25 17:53:49', '2015-05-25 17:53:49', 'Hello', 'Portfolio', '', 'inherit', 'open', 'open', '', '8-revision-v1', '', '', '2015-05-25 17:53:49', '2015-05-25 17:53:49', '', 8, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/8-revision-v1/', 0, 'revision', '', 0), (10, 1, '2015-05-25 17:54:16', '2015-05-25 17:54:16', 'Welcome', 'Blog', '', 'publish', 'open', 'closed', '', 'blog', '', '', '2015-05-25 18:29:21', '2015-05-25 18:29:21', '', 0, 'http://www.himanshu-joshi.com/mynewsite/?page_id=10', 4, 'page', '', 0), (11, 1, '2015-05-25 17:54:16', '2015-05-25 17:54:16', 'Welcome', 'Blog', '', 'inherit', 'open', 'open', '', '10-revision-v1', '', '', '2015-05-25 17:54:16', '2015-05-25 17:54:16', '', 10, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/10-revision-v1/', 0, 'revision', '', 0), (12, 1, '2015-05-25 17:54:51', '2015-05-25 17:54:51', '', 'Contact Me', '', 'publish', 'open', 'closed', '', 'contact-me', '', '', '2015-05-25 18:29:30', '2015-05-25 18:29:30', '', 0, 'http://www.himanshu-joshi.com/mynewsite/?page_id=12', 5, 'page', '', 0), (13, 1, '2015-05-25 17:54:51', '2015-05-25 17:54:51', '', 'Contact Me', '', 'inherit', 'open', 'open', '', '12-revision-v1', '', '', '2015-05-25 17:54:51', '2015-05-25 17:54:51', '', 12, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/12-revision-v1/', 0, 'revision', '', 0), (15, 1, '2015-05-25 17:55:26', '2015-05-25 17:55:26', '', 'User Experience Design', '', 'publish', 'open', 'open', '', 'user-experience-design', '', '', '2015-05-25 17:55:26', '2015-05-25 17:55:26', '', 8, 'http://www.himanshu-joshi.com/mynewsite/?page_id=15', 0, 'page', '', 0), (16, 1, '2015-05-25 17:55:26', '2015-05-25 17:55:26', '', 'User Experience Design', '', 'inherit', 'open', 'open', '', '15-revision-v1', '', '', '2015-05-25 17:55:26', '2015-05-25 17:55:26', '', 15, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/15-revision-v1/', 0, 'revision', '', 0), (17, 1, '2015-05-25 17:55:46', '2015-05-25 17:55:46', '', 'Sketches', '', 'publish', 'open', 'open', '', 'sketches', '', '', '2015-05-25 17:55:46', '2015-05-25 17:55:46', '', 8, 'http://www.himanshu-joshi.com/mynewsite/?page_id=17', 0, 'page', '', 0), (18, 1, '2015-05-25 17:55:46', '2015-05-25 17:55:46', '', 'Sketches', '', 'inherit', 'open', 'open', '', '17-revision-v1', '', '', '2015-05-25 17:55:46', '2015-05-25 17:55:46', '', 17, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/17-revision-v1/', 0, 'revision', '', 0), (19, 1, '2015-05-25 17:56:54', '2015-05-25 17:56:54', '', 'Graphic Design', '', 'publish', 'open', 'open', '', 'graphic-design', '', '', '2015-05-25 17:56:54', '2015-05-25 17:56:54', '', 8, 'http://www.himanshu-joshi.com/mynewsite/?page_id=19', 0, 'page', '', 0), (20, 1, '2015-05-25 17:56:54', '2015-05-25 17:56:54', '', 'Graphic Design', '', 'inherit', 'open', 'open', '', '19-revision-v1', '', '', '2015-05-25 17:56:54', '2015-05-25 17:56:54', '', 19, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/19-revision-v1/', 0, 'revision', '', 0), (22, 1, '2015-05-25 17:57:40', '2015-05-25 17:57:40', '', 'Development Work', '', 'publish', 'open', 'open', '', 'development-work', '', '', '2015-05-25 17:57:40', '2015-05-25 17:57:40', '', 8, 'http://www.himanshu-joshi.com/mynewsite/?page_id=22', 0, 'page', '', 0), (23, 1, '2015-05-25 17:57:40', '2015-05-25 17:57:40', '', 'Development Work', '', 'inherit', 'open', 'open', '', '22-revision-v1', '', '', '2015-05-25 17:57:40', '2015-05-25 17:57:40', '', 22, 'http://www.himanshu-joshi.com/mynewsite/blog/2015/05/25/22-revision-v1/', 0, 'revision', '', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_registration_log` -- CREATE TABLE `wp_registration_log` ( `ID` bigint(20) NOT NULL, `email` varchar(255) NOT NULL DEFAULT '', `IP` varchar(30) NOT NULL DEFAULT '', `blog_id` bigint(20) NOT NULL DEFAULT '0', `date_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `wp_signups` -- CREATE TABLE `wp_signups` ( `signup_id` bigint(20) NOT NULL, `domain` varchar(200) NOT NULL DEFAULT '', `path` varchar(100) NOT NULL DEFAULT '', `title` longtext NOT NULL, `user_login` varchar(60) NOT NULL DEFAULT '', `user_email` varchar(100) NOT NULL DEFAULT '', `registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `activated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `active` tinyint(1) NOT NULL DEFAULT '0', `activation_key` varchar(50) NOT NULL DEFAULT '', `meta` longtext ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `wp_site` -- CREATE TABLE `wp_site` ( `id` bigint(20) NOT NULL, `domain` varchar(200) NOT NULL DEFAULT '', `path` varchar(100) NOT NULL DEFAULT '' ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Dumping data for table `wp_site` -- INSERT INTO `wp_site` (`id`, `domain`, `path`) VALUES (1, 'www.himanshu-joshi.com', '/mynewsite/'); -- -------------------------------------------------------- -- -- Table structure for table `wp_sitemeta` -- CREATE TABLE `wp_sitemeta` ( `meta_id` bigint(20) NOT NULL, `site_id` bigint(20) NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Dumping data for table `wp_sitemeta` -- INSERT INTO `wp_sitemeta` (`meta_id`, `site_id`, `meta_key`, `meta_value`) VALUES (1, 1, 'site_name', 'New Website Design'), (2, 1, 'admin_email', 'rohit12346@gmail.com'), (3, 1, 'admin_user_id', '1'), (4, 1, 'registration', 'none'), (5, 1, 'upload_filetypes', 'jpg jpeg png gif mov avi mpg 3gp 3g2 midi mid pdf doc ppt odt pptx docx pps ppsx xls xlsx key mp3 ogg wma m4a wav mp4 m4v webm ogv wmv flv'), (6, 1, 'blog_upload_space', '100'), (7, 1, 'fileupload_maxk', '1500'), (8, 1, 'site_admins', 'a:1:{i:0;s:17:\"himanshujoshi2015\";}'), (9, 1, 'allowedthemes', 'a:0:{}'), (10, 1, 'illegal_names', 'a:9:{i:0;s:3:\"www\";i:1;s:3:\"web\";i:2;s:4:\"root\";i:3;s:5:\"admin\";i:4;s:4:\"main\";i:5;s:6:\"invite\";i:6;s:13:\"administrator\";i:7;s:5:\"files\";i:8;s:4:\"blog\";}'), (11, 1, 'wpmu_upgrade_site', '30133'), (12, 1, 'welcome_email', 'Dear User,\n\nYour new SITE_NAME site has been successfully set up at:\nBLOG_URL\n\nYou can log in to the administrator account with the following information:\n\nUsername: USERNAME\nPassword: PASSWORD\nLog in here: BLOG_URLwp-login.php\n\nWe hope you enjoy your new site. Thanks!\n\n--The Team @ SITE_NAME'), (13, 1, 'first_post', 'Welcome to SITE_NAME. This is your first post. Edit or delete it, then start blogging!'), (14, 1, 'siteurl', 'http://www.himanshu-joshi.com/mynewsite/'), (15, 1, 'add_new_users', '0'), (16, 1, 'upload_space_check_disabled', '1'), (17, 1, 'subdomain_install', '0'), (18, 1, 'global_terms_enabled', '0'), (19, 1, 'ms_files_rewriting', '0'), (20, 1, 'initial_db_version', '30133'), (21, 1, 'active_sitewide_plugins', 'a:0:{}'), (22, 1, 'WPLANG', 'en_US'), (30, 1, 'user_count', '1'), (31, 1, 'blog_count', '1'), (32, 1, 'can_compress_scripts', '1'), (49, 1, 'auto_core_update_notified', 'a:4:{s:4:\"type\";s:7:\"success\";s:5:\"email\";s:20:\"rohit12346@gmail.com\";s:7:\"version\";s:5:\"4.1.5\";s:9:\"timestamp\";i:1432485401;}'), (55, 1, '_site_transient_timeout_browser_88efaf4b2dd5ab22adecd83c1cb50387', '1433090389'), (56, 1, '_site_transient_browser_88efaf4b2dd5ab22adecd83c1cb50387', 'a:9:{s:8:\"platform\";s:7:\"Windows\";s:4:\"name\";s:7:\"Firefox\";s:7:\"version\";s:4:\"38.0\";s:10:\"update_url\";s:23:\"http://www.firefox.com/\";s:7:\"img_src\";s:50:\"http://s.wordpress.org/images/browsers/firefox.png\";s:11:\"img_src_ssl\";s:49:\"https://wordpress.org/images/browsers/firefox.png\";s:15:\"current_version\";s:2:\"16\";s:7:\"upgrade\";b:0;s:8:\"insecure\";b:0;}'), (58, 1, '_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:59:\"https://downloads.wordpress.org/release/wordpress-4.2.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-4.2.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-4.2.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-4.2.2-new-bundled.zip\";s:7:\"partial\";b:0;s:8:\"rollback\";b:0;}s:7:\"current\";s:5:\"4.2.2\";s:7:\"version\";s:5:\"4.2.2\";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:1433577756;s:15:\"version_checked\";s:5:\"4.2.2\";s:12:\"translations\";a:0:{}}'), (76, 1, 'registrationnotification', 'yes'), (77, 1, 'welcome_user_email', 'Howdy USERNAME,\n\nYour new account is set up.\n\nYou can log in with the following information:\nUsername: USERNAME\nPassword: PASSWORD\nLOGINLINK\n\nThanks!\n\n--The Team @ SITE_NAME'), (78, 1, '_site_transient_timeout_available_translations', '1432585132'), (79, 1, '_site_transient_available_translations', 'a:56:{s:2:\"ar\";a:8:{s:8:\"language\";s:2:\"ar\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 23:59:50\";s:12:\"english_name\";s:6:\"Arabic\";s:11:\"native_name\";s:14:\"العربية\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-02 03:57:09\";s:12:\"english_name\";s:11:\"Azerbaijani\";s:11:\"native_name\";s:16:\"Azərbaycan dili\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:9:\"Bulgarian\";s:11:\"native_name\";s:18:\"Български\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-25 18:55:51\";s:12:\"english_name\";s:7:\"Bosnian\";s:11:\"native_name\";s:8:\"Bosanski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-24 05:23:15\";s:12:\"english_name\";s:7:\"Catalan\";s:11:\"native_name\";s:7:\"Català\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:5:\"Welsh\";s:11:\"native_name\";s:7:\"Cymraeg\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:09\";s:12:\"english_name\";s:6:\"Danish\";s:11:\"native_name\";s:5:\"Dansk\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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_CH\";a:8:{s:8:\"language\";s:5:\"de_CH\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:20:\"German (Switzerland)\";s:11:\"native_name\";s:17:\"Deutsch (Schweiz)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/de_CH.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Fortfahren\";}}s:5:\"de_DE\";a:8:{s:8:\"language\";s:5:\"de_DE\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-17 18:19:04\";s:12:\"english_name\";s:6:\"German\";s:11:\"native_name\";s:7:\"Deutsch\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-10 21:13:03\";s:12:\"english_name\";s:5:\"Greek\";s:11:\"native_name\";s:16:\"Ελληνικά\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:16:\"English (Canada)\";s:11:\"native_name\";s:16:\"English (Canada)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:09\";s:12:\"english_name\";s:19:\"English (Australia)\";s:11:\"native_name\";s:19:\"English (Australia)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:09\";s:12:\"english_name\";s:12:\"English (UK)\";s:11:\"native_name\";s:12:\"English (UK)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:09\";s:12:\"english_name\";s:9:\"Esperanto\";s:11:\"native_name\";s:9:\"Esperanto\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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_MX\";a:8:{s:8:\"language\";s:5:\"es_MX\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-24 16:03:38\";s:12:\"english_name\";s:16:\"Spanish (Mexico)\";s:11:\"native_name\";s:19:\"Español de México\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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_PE\";a:8:{s:8:\"language\";s:5:\"es_PE\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-25 13:39:01\";s:12:\"english_name\";s:14:\"Spanish (Peru)\";s:11:\"native_name\";s:17:\"Español de Perú\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-18 10:50:06\";s:12:\"english_name\";s:15:\"Spanish (Spain)\";s:11:\"native_name\";s:8:\"Español\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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_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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:09\";s:12:\"english_name\";s:6:\"Basque\";s:11:\"native_name\";s:7:\"Euskara\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-16 10:01:41\";s:12:\"english_name\";s:7:\"Persian\";s:11:\"native_name\";s:10:\"فارسی\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-15 10:49:37\";s:12:\"english_name\";s:7:\"Finnish\";s:11:\"native_name\";s:5:\"Suomi\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-29 17:08:38\";s:12:\"english_name\";s:15:\"French (France)\";s:11:\"native_name\";s:9:\"Français\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:8:\"Galician\";s:11:\"native_name\";s:6:\"Galego\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:3:\"haz\";a:8:{s:8:\"language\";s:3:\"haz\";s:7:\"version\";s:5:\"4.1.5\";s:7:\"updated\";s:19:\"2015-03-26 15:20:27\";s:12:\"english_name\";s:8:\"Hazaragi\";s:11:\"native_name\";s:15:\"هزاره گی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.1.5/haz.zip\";s:3:\"iso\";a:1:{i:2;s:3:\"haz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:5:\"he_IL\";a:8:{s:8:\"language\";s:5:\"he_IL\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-23 10:52:35\";s:12:\"english_name\";s:6:\"Hebrew\";s:11:\"native_name\";s:16:\"עִבְרִית\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-21 12:07:28\";s:12:\"english_name\";s:8:\"Croatian\";s:11:\"native_name\";s:8:\"Hrvatski\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-07 06:15:06\";s:12:\"english_name\";s:9:\"Hungarian\";s:11:\"native_name\";s:6:\"Magyar\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:10:\"Indonesian\";s:11:\"native_name\";s:16:\"Bahasa Indonesia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:\"is_IS\";a:8:{s:8:\"language\";s:5:\"is_IS\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-18 23:48:51\";s:12:\"english_name\";s:9:\"Icelandic\";s:11:\"native_name\";s:9:\"Íslenska\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/is_IS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"is\";i:2;s:3:\"isl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Áfram\";}}s:5:\"it_IT\";a:8:{s:8:\"language\";s:5:\"it_IT\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-23 17:17:36\";s:12:\"english_name\";s:7:\"Italian\";s:11:\"native_name\";s:8:\"Italiano\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-15 08:57:03\";s:12:\"english_name\";s:8:\"Japanese\";s:11:\"native_name\";s:9:\"日本語\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 22:23:52\";s:12:\"english_name\";s:6:\"Korean\";s:11:\"native_name\";s:9:\"한국어\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:\"lt_LT\";a:8:{s:8:\"language\";s:5:\"lt_LT\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:10:\"Lithuanian\";s:11:\"native_name\";s:15:\"Lietuvių kalba\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/lt_LT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lt\";i:2;s:3:\"lit\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Tęsti\";}}s:5:\"my_MM\";a:8:{s:8:\"language\";s:5:\"my_MM\";s:7:\"version\";s:5:\"4.1.5\";s:7:\"updated\";s:19:\"2015-03-26 15:57:42\";s:12:\"english_name\";s:17:\"Myanmar (Burmese)\";s:11:\"native_name\";s:15:\"ဗမာစာ\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.1.5/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-04 08:01:04\";s:12:\"english_name\";s:19:\"Norwegian (Bokmål)\";s:11:\"native_name\";s:13:\"Norsk bokmål\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-18 08:22:28\";s:12:\"english_name\";s:5:\"Dutch\";s:11:\"native_name\";s:10:\"Nederlands\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:\"nn_NO\";a:8:{s:8:\"language\";s:5:\"nn_NO\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:09\";s:12:\"english_name\";s:19:\"Norwegian (Nynorsk)\";s:11:\"native_name\";s:13:\"Norsk nynorsk\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/nn_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nn\";i:2;s:3:\"nno\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Hald fram\";}}s:3:\"oci\";a:8:{s:8:\"language\";s:3:\"oci\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-09 10:19:58\";s:12:\"english_name\";s:7:\"Occitan\";s:11:\"native_name\";s:7:\"Occitan\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.2.2/oci.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"oc\";i:2;s:3:\"oci\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Contunhar\";}}s:5:\"pl_PL\";a:8:{s:8:\"language\";s:5:\"pl_PL\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-09 10:15:05\";s:12:\"english_name\";s:6:\"Polish\";s:11:\"native_name\";s:6:\"Polski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:2:\"ps\";a:8:{s:8:\"language\";s:2:\"ps\";s:7:\"version\";s:5:\"4.1.5\";s:7:\"updated\";s:19:\"2015-03-29 22:19:48\";s:12:\"english_name\";s:6:\"Pashto\";s:11:\"native_name\";s:8:\"پښتو\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.1.5/ps.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"ps\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"دوام\";}}s:5:\"pt_PT\";a:8:{s:8:\"language\";s:5:\"pt_PT\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-27 09:25:14\";s:12:\"english_name\";s:21:\"Portuguese (Portugal)\";s:11:\"native_name\";s:10:\"Português\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-27 14:23:25\";s:12:\"english_name\";s:19:\"Portuguese (Brazil)\";s:11:\"native_name\";s:20:\"Português do Brasil\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-21 15:14:01\";s:12:\"english_name\";s:8:\"Romanian\";s:11:\"native_name\";s:8:\"Română\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:7:\"Russian\";s:11:\"native_name\";s:14:\"Русский\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-08 10:26:50\";s:12:\"english_name\";s:6:\"Slovak\";s:11:\"native_name\";s:11:\"Slovenčina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.1.5\";s:7:\"updated\";s:19:\"2015-03-26 16:25:46\";s:12:\"english_name\";s:9:\"Slovenian\";s:11:\"native_name\";s:13:\"Slovenščina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.1.5/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:2:\"sq\";a:8:{s:8:\"language\";s:2:\"sq\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-05 22:47:02\";s:12:\"english_name\";s:8:\"Albanian\";s:11:\"native_name\";s:5:\"Shqip\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/sq.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sq\";i:2;s:3:\"sqi\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Vazhdo\";}}s:5:\"sr_RS\";a:8:{s:8:\"language\";s:5:\"sr_RS\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 16:55:54\";s:12:\"english_name\";s:7:\"Serbian\";s:11:\"native_name\";s:23:\"Српски језик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-17 21:59:15\";s:12:\"english_name\";s:7:\"Swedish\";s:11:\"native_name\";s:7:\"Svenska\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-29 07:03:07\";s:12:\"english_name\";s:4:\"Thai\";s:11:\"native_name\";s:9:\"ไทย\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:7:\"Turkish\";s:11:\"native_name\";s:8:\"Türkçe\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:\"ug_CN\";a:8:{s:8:\"language\";s:5:\"ug_CN\";s:7:\"version\";s:5:\"4.1.5\";s:7:\"updated\";s:19:\"2015-03-26 16:45:38\";s:12:\"english_name\";s:6:\"Uighur\";s:11:\"native_name\";s:9:\"Uyƣurqə\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.1.5/ug_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ug\";i:2;s:3:\"uig\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:26:\"داۋاملاشتۇرۇش\";}}s:2:\"uk\";a:8:{s:8:\"language\";s:2:\"uk\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-05-24 15:09:07\";s:12:\"english_name\";s:9:\"Ukrainian\";s:11:\"native_name\";s:20:\"Українська\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.2.2/uk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uk\";i:2;s:3:\"ukr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продовжити\";}}s:5:\"zh_CN\";a:8:{s:8:\"language\";s:5:\"zh_CN\";s:7:\"version\";s:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-23 15:23:08\";s:12:\"english_name\";s:15:\"Chinese (China)\";s:11:\"native_name\";s:12:\"简体中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:5:\"4.2.2\";s:7:\"updated\";s:19:\"2015-04-29 06:37:03\";s:12:\"english_name\";s:16:\"Chinese (Taiwan)\";s:11:\"native_name\";s:12:\"繁體中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.2.2/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:\"繼續\";}}}'), (86, 1, '_site_transient_timeout_wporg_theme_feature_list', '1432627417'), (87, 1, '_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\";}}'), (88, 1, '_site_transient_update_themes', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1433577757;s:7:\"checked\";a:4:{s:6:\"seller\";s:7:\"1.0.2.0\";s:9:\"stargazer\";s:5:\"1.2.1\";s:12:\"twentytwelve\";s:3:\"1.7\";s:6:\"twiggy\";s:5:\"1.0.0\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}}'), (89, 1, '_site_transient_timeout_theme_roots', '1433579555'), (90, 1, '_site_transient_theme_roots', 'a:4:{s:6:\"seller\";s:7:\"/themes\";s:9:\"stargazer\";s:7:\"/themes\";s:12:\"twentytwelve\";s:7:\"/themes\";s:6:\"twiggy\";s:7:\"/themes\";}'), (91, 1, '_site_transient_update_plugins', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1433577756;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.1.1\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.3.1.1.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\";}}}'); -- -------------------------------------------------------- -- -- Table structure for table `wp_terms` -- CREATE TABLE `wp_terms` ( `term_id` bigint(20) UNSIGNED NOT NULL, `name` varchar(200) NOT NULL DEFAULT '', `slug` varchar(200) NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0' ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Dumping data for table `wp_terms` -- INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES (1, 'Uncategorized', 'uncategorized', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_term_relationships` -- CREATE TABLE `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' ) ENGINE=InnoDB 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 `wp_term_taxonomy` ( `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL, `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' ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- 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); -- -------------------------------------------------------- -- -- Table structure for table `wp_usermeta` -- CREATE TABLE `wp_usermeta` ( `umeta_id` bigint(20) UNSIGNED NOT NULL, `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- Dumping data for table `wp_usermeta` -- INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (1, 1, 'nickname', 'himanshujoshi2015'), (2, 1, 'first_name', ''), (3, 1, 'last_name', ''), (4, 1, 'description', ''), (5, 1, 'rich_editing', 'true'), (6, 1, 'comment_shortcuts', 'false'), (7, 1, 'admin_color', 'fresh'), (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', 'wp360_locks,wp390_widgets,wp410_dfw'), (13, 1, 'show_welcome_panel', '1'), (15, 1, 'wp_dashboard_quick_press_last_post_id', '24'), (16, 1, 'source_domain', 'www.himanshu-joshi.com'), (17, 1, 'primary_blog', '1'), (18, 1, 'session_tokens', 'a:3:{s:64:\"689cfc1e9ca48fce8d98111108c4c754683b72a49c832e9372ab2d7a7045690b\";a:4:{s:10:\"expiration\";i:1432658388;s:2:\"ip\";s:13:\"106.66.215.72\";s:2:\"ua\";s:65:\"Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0\";s:5:\"login\";i:1432485588;}s:64:\"0f1ccbef7328083bb383ad3495d870840d87559298f00b553b403e473ff36c44\";a:4:{s:10:\"expiration\";i:1432743239;s:2:\"ip\";s:13:\"106.66.206.40\";s:2:\"ua\";s:65:\"Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0\";s:5:\"login\";i:1432570439;}s:64:\"27f67dc29e4e9d22e5f33a5f4748afec474d1c731295b51f536afa176901f850\";a:4:{s:10:\"expiration\";i:1432788055;s:2:\"ip\";s:11:\"106.77.28.4\";s:2:\"ua\";s:65:\"Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Firefox/38.0\";s:5:\"login\";i:1432615255;}}'), (19, 1, 'wp_user-settings', 'libraryContent=browse'), (20, 1, 'wp_user-settings-time', '1432576312'); -- -------------------------------------------------------- -- -- Table structure for table `wp_users` -- CREATE TABLE `wp_users` ( `ID` bigint(20) UNSIGNED NOT NULL, `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 '', `spam` tinyint(2) NOT NULL DEFAULT '0', `deleted` tinyint(2) NOT NULL DEFAULT '0' ) ENGINE=InnoDB DEFAULT CHARSET=utf8; -- -- 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`, `spam`, `deleted`) VALUES (1, 'himanshujoshi2015', '$P$B1wv4UyLzHNkViQUOcXPquWwv/wTMK0', 'himanshujoshi2015', 'rohit12346@gmail.com', '', '2015-01-22 13:23:43', '', 0, 'himanshujoshi2015', 0, 0); -- -- Indexes for dumped tables -- -- -- Indexes for table `wp_blogs` -- ALTER TABLE `wp_blogs` ADD PRIMARY KEY (`blog_id`), ADD KEY `domain` (`domain`(50),`path`(5)), ADD KEY `lang_id` (`lang_id`); -- -- Indexes for table `wp_blog_versions` -- ALTER TABLE `wp_blog_versions` ADD PRIMARY KEY (`blog_id`), ADD KEY `db_version` (`db_version`); -- -- Indexes for table `wp_commentmeta` -- ALTER TABLE `wp_commentmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `comment_id` (`comment_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_comments` -- ALTER TABLE `wp_comments` ADD PRIMARY KEY (`comment_ID`), ADD KEY `comment_post_ID` (`comment_post_ID`), ADD KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), ADD KEY `comment_date_gmt` (`comment_date_gmt`), ADD KEY `comment_parent` (`comment_parent`), ADD KEY `comment_author_email` (`comment_author_email`(10)); -- -- Indexes for table `wp_links` -- ALTER TABLE `wp_links` ADD PRIMARY KEY (`link_id`), ADD KEY `link_visible` (`link_visible`); -- -- Indexes for table `wp_options` -- ALTER TABLE `wp_options` ADD PRIMARY KEY (`option_id`), ADD UNIQUE KEY `option_name` (`option_name`); -- -- Indexes for table `wp_postmeta` -- ALTER TABLE `wp_postmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `post_id` (`post_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_posts` -- ALTER TABLE `wp_posts` ADD PRIMARY KEY (`ID`), ADD KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), ADD KEY `post_parent` (`post_parent`), ADD KEY `post_author` (`post_author`), ADD KEY `post_name` (`post_name`(191)); -- -- Indexes for table `wp_registration_log` -- ALTER TABLE `wp_registration_log` ADD PRIMARY KEY (`ID`), ADD KEY `IP` (`IP`); -- -- Indexes for table `wp_signups` -- ALTER TABLE `wp_signups` ADD PRIMARY KEY (`signup_id`), ADD KEY `activation_key` (`activation_key`), ADD KEY `user_email` (`user_email`), ADD KEY `user_login_email` (`user_login`,`user_email`), ADD KEY `domain_path` (`domain`,`path`); -- -- Indexes for table `wp_site` -- ALTER TABLE `wp_site` ADD PRIMARY KEY (`id`), ADD KEY `domain` (`domain`,`path`); -- -- Indexes for table `wp_sitemeta` -- ALTER TABLE `wp_sitemeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `meta_key` (`meta_key`), ADD KEY `site_id` (`site_id`); -- -- Indexes for table `wp_terms` -- ALTER TABLE `wp_terms` ADD PRIMARY KEY (`term_id`), ADD KEY `slug` (`slug`(191)), ADD KEY `name` (`name`(191)); -- -- Indexes for table `wp_term_relationships` -- ALTER TABLE `wp_term_relationships` ADD PRIMARY KEY (`object_id`,`term_taxonomy_id`), ADD KEY `term_taxonomy_id` (`term_taxonomy_id`); -- -- Indexes for table `wp_term_taxonomy` -- ALTER TABLE `wp_term_taxonomy` ADD PRIMARY KEY (`term_taxonomy_id`), ADD UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), ADD KEY `taxonomy` (`taxonomy`); -- -- Indexes for table `wp_usermeta` -- ALTER TABLE `wp_usermeta` ADD PRIMARY KEY (`umeta_id`), ADD KEY `user_id` (`user_id`), ADD KEY `meta_key` (`meta_key`); -- -- Indexes for table `wp_users` -- ALTER TABLE `wp_users` ADD PRIMARY KEY (`ID`), ADD KEY `user_login_key` (`user_login`), ADD KEY `user_nicename` (`user_nicename`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `wp_blogs` -- ALTER TABLE `wp_blogs` MODIFY `blog_id` bigint(20) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT for table `wp_commentmeta` -- ALTER TABLE `wp_commentmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_comments` -- ALTER TABLE `wp_comments` MODIFY `comment_ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT for table `wp_links` -- ALTER TABLE `wp_links` MODIFY `link_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_options` -- ALTER TABLE `wp_options` MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=196; -- -- AUTO_INCREMENT for table `wp_postmeta` -- ALTER TABLE `wp_postmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=32; -- -- AUTO_INCREMENT for table `wp_posts` -- ALTER TABLE `wp_posts` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=24; -- -- AUTO_INCREMENT for table `wp_registration_log` -- ALTER TABLE `wp_registration_log` MODIFY `ID` bigint(20) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_signups` -- ALTER TABLE `wp_signups` MODIFY `signup_id` bigint(20) NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_site` -- ALTER TABLE `wp_site` MODIFY `id` bigint(20) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT for table `wp_sitemeta` -- ALTER TABLE `wp_sitemeta` MODIFY `meta_id` bigint(20) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=92; -- -- AUTO_INCREMENT for table `wp_terms` -- ALTER TABLE `wp_terms` MODIFY `term_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT for table `wp_term_taxonomy` -- ALTER TABLE `wp_term_taxonomy` MODIFY `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; -- -- AUTO_INCREMENT for table `wp_usermeta` -- ALTER TABLE `wp_usermeta` MODIFY `umeta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=21; -- -- AUTO_INCREMENT for table `wp_users` -- ALTER TABLE `wp_users` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2; COMMIT; /*!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 */;