-- https://www.phpmyadmin.net/
--

START TRANSACTION;



--
-- Database: `jjaggerd_wrdp1`
--
CREATE DATABASE IF NOT EXISTS `jjaggerd_wrdp1` DEFAULT CHARACTER SET latin1 COLLATE latin1_swedish_ci;
USE `jjaggerd_wrdp1`;

-- --------------------------------------------------------

--
-- Table structure for table `wp_comments`
--
-- Creation: Jul 01, 2013 at 12:26 AM
-- Last update: Dec 05, 2020 at 03:07 PM
-- Last check: Dec 05, 2020 at 03:07 PM
--

CREATE TABLE `wp_comments` (
  `comment_ID` bigint(20) UNSIGNED NOT NULL,
  `comment_post_ID` int(11) NOT NULL DEFAULT 0,
  `comment_author` tinytext NOT NULL,
  `comment_author_email` varchar(100) NOT NULL DEFAULT '',
  `comment_author_url` varchar(200) NOT NULL DEFAULT '',
  `comment_author_IP` varchar(100) NOT NULL DEFAULT '',
  `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `comment_content` text NOT NULL,
  `comment_karma` int(11) NOT NULL DEFAULT 0,
  `comment_approved` enum('0','1','spam') NOT NULL DEFAULT '1',
  `comment_agent` varchar(255) NOT NULL DEFAULT '',
  `comment_type` varchar(20) NOT NULL DEFAULT '',
  `comment_parent` bigint(20) NOT NULL DEFAULT 0,
  `user_id` bigint(20) NOT NULL DEFAULT 0
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

--
-- Dumping data for table `wp_comments`
--

INSERT INTO `wp_comments` (`comment_ID`, `comment_post_ID`, `comment_author`, `comment_author_email`, `comment_author_url`, `comment_author_IP`, `comment_date`, `comment_date_gmt`, `comment_content`, `comment_karma`, `comment_approved`, `comment_agent`, `comment_type`, `comment_parent`, `user_id`) VALUES
(2, 27, 'Juliohaumn', 'jmlkcjmlkc@gmail.com', 'https://bysws.ru', '109.173.125.248', '2017-03-13 22:26:06', '2017-03-13 22:26:06', '???????? ?????? ???? ? ???? \r\n<a href=\"https://bysws.ru\" rel=\"nofollow\">Mods by SwS</a>', 0, '0', 'Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36', '', 0, 0);

-- --------------------------------------------------------

--
-- Table structure for table `wp_links`
--
-- Creation: Jul 01, 2013 at 12:26 AM
-- Last update: Dec 05, 2020 at 03:07 PM
-- Last check: Dec 05, 2020 at 03:07 PM
--

CREATE TABLE `wp_links` (
  `link_id` bigint(20) NOT NULL,
  `link_url` varchar(255) NOT NULL DEFAULT '',
  `link_name` varchar(255) NOT NULL DEFAULT '',
  `link_image` varchar(255) NOT NULL DEFAULT '',
  `link_target` varchar(25) NOT NULL DEFAULT '',
  `link_category` bigint(20) NOT NULL DEFAULT 0,
  `link_description` varchar(255) NOT NULL DEFAULT '',
  `link_visible` enum('Y','N') NOT NULL DEFAULT 'Y',
  `link_owner` int(11) NOT NULL DEFAULT 1,
  `link_rating` int(11) NOT NULL DEFAULT 0,
  `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `link_rel` varchar(255) NOT NULL DEFAULT '',
  `link_notes` mediumtext NOT NULL,
  `link_rss` varchar(255) NOT NULL DEFAULT ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

--
-- Dumping data for table `wp_links`
--

INSERT INTO `wp_links` (`link_id`, `link_url`, `link_name`, `link_image`, `link_target`, `link_category`, `link_description`, `link_visible`, `link_owner`, `link_rating`, `link_updated`, `link_rel`, `link_notes`, `link_rss`) VALUES
(1, 'http://codex.wordpress.org/', 'Documentation', '', '', 0, '', 'Y', 1, 0, '0000-00-00 00:00:00', '', '', ''),
(2, 'http://wordpress.org/development/', 'Development Blog', '', '', 0, '', 'Y', 1, 0, '0000-00-00 00:00:00', '', '', 'http://wordpress.org/development/feed/'),
(3, 'http://wordpress.org/extend/ideas/', 'Suggest Ideas', '', '', 0, '', 'Y', 1, 0, '0000-00-00 00:00:00', '', '', ''),
(4, 'http://wordpress.org/support/', 'Support Forum', '', '', 0, '', 'Y', 1, 0, '0000-00-00 00:00:00', '', '', ''),
(5, 'http://wordpress.org/extend/plugins/', 'Plugins', '', '', 0, '', 'Y', 1, 0, '0000-00-00 00:00:00', '', '', ''),
(6, 'http://wordpress.org/extend/themes/', 'Themes', '', '', 0, '', 'Y', 1, 0, '0000-00-00 00:00:00', '', '', ''),
(7, 'http://planet.wordpress.org/', 'WordPress Planet', '', '', 0, '', 'Y', 1, 0, '0000-00-00 00:00:00', '', '', '');

-- --------------------------------------------------------

--
-- Table structure for table `wp_options`
--
-- Creation: Jul 01, 2013 at 12:26 AM
-- Last update: Dec 05, 2020 at 03:07 PM
-- Last check: Dec 05, 2020 at 03:07 PM
--

CREATE TABLE `wp_options` (
  `option_id` bigint(20) NOT NULL,
  `blog_id` int(11) NOT NULL DEFAULT 0,
  `option_name` varchar(64) NOT NULL DEFAULT '',
  `option_value` longtext NOT NULL,
  `autoload` enum('yes','no') NOT NULL DEFAULT 'yes'
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

--
-- Dumping data for table `wp_options`
--

INSERT INTO `wp_options` (`option_id`, `blog_id`, `option_name`, `option_value`, `autoload`) VALUES
(1, 0, 'siteurl', 'http://jaggerdog.com/jaggerblog', 'yes'),
(2, 0, 'blogname', 'Welcome to Jaggerdog.com', 'yes'),
(3, 0, 'blogdescription', '', 'yes'),
(4, 0, 'users_can_register', '', 'yes'),
(5, 0, 'admin_email', 'jjaggerd@jaggerdog.com', 'yes'),
(6, 0, 'start_of_week', '1', 'yes'),
(7, 0, 'use_balanceTags', '0', 'yes'),
(8, 0, 'use_smilies', '1', 'yes'),
(9, 0, 'require_name_email', '1', 'yes'),
(10, 0, 'comments_notify', '1', 'yes'),
(11, 0, 'posts_per_rss', '10', 'yes'),
(12, 0, 'rss_excerpt_length', '50', 'yes'),
(13, 0, 'rss_use_excerpt', '0', 'yes'),
(14, 0, 'mailserver_url', 'pop.gmail.com', 'yes'),
(15, 0, 'mailserver_login', 'nischan', 'yes'),
(16, 0, 'mailserver_pass', 'k2106t', 'yes'),
(17, 0, 'mailserver_port', '110', 'yes'),
(18, 0, 'default_category', '1', 'yes'),
(19, 0, 'default_comment_status', 'open', 'yes'),
(20, 0, 'default_ping_status', 'open', 'yes'),
(21, 0, 'default_pingback_flag', '1', 'yes'),
(22, 0, 'default_post_edit_rows', '10', 'yes'),
(23, 0, 'posts_per_page', '50', 'yes'),
(24, 0, 'what_to_show', 'posts', 'yes'),
(25, 0, 'date_format', 'F j, Y', 'yes'),
(26, 0, 'time_format', 'g:i a', 'yes'),
(27, 0, 'links_updated_date_format', 'F j, Y g:i a', 'yes'),
(28, 0, 'links_recently_updated_prepend', '<em>', 'yes'),
(29, 0, 'links_recently_updated_append', '</em>', 'yes'),
(30, 0, 'links_recently_updated_time', '120', 'yes'),
(31, 0, 'comment_moderation', '0', 'yes'),
(32, 0, 'moderation_notify', '1', 'yes'),
(33, 0, 'permalink_structure', '', 'yes'),
(34, 0, 'gzipcompression', '', 'yes'),
(35, 0, 'hack_file', '0', 'yes'),
(36, 0, 'blog_charset', 'UTF-8', 'yes'),
(37, 0, 'moderation_keys', '', 'no'),
(38, 0, 'active_plugins', 'a:2:{i:0;s:35:\"exploit-scanner/exploit-scanner.php\";i:1;s:43:\"wysiwyg-text-widget/wysiwyg-text-widget.php\";}', 'yes'),
(39, 0, 'home', 'http://jaggerdog.com/jaggerblog', 'yes'),
(40, 0, 'category_base', '', 'yes'),
(41, 0, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'),
(42, 0, 'advanced_edit', '0', 'yes'),
(43, 0, 'comment_max_links', '2', 'yes'),
(44, 0, 'gmt_offset', '0', 'yes'),
(45, 0, 'default_email_category', '1', 'yes'),
(46, 0, 'recently_edited', 'a:5:{i:0;s:41:\"wp-content/themes/Dog-Lover/functions.php\";i:2;s:37:\"wp-content/themes/Dog-Lover/style.css\";i:3;s:37:\"wp-content/themes/Dog-Lover/index.php\";i:4;s:36:\"wp-content/themes/Dog-Lover/page.php\";i:5;s:60:\"wp-content/plugins/flash-video-player/flash-video-player.php\";}', 'no'),
(47, 0, 'use_linksupdate', '0', 'yes'),
(48, 0, 'template', 'Dog-Lover', 'yes'),
(49, 0, 'stylesheet', 'Dog-Lover', 'yes'),
(50, 0, 'comment_whitelist', '1', 'yes'),
(52, 0, 'blacklist_keys', '', 'no'),
(53, 0, 'comment_registration', '', 'yes'),
(54, 0, 'rss_language', 'en', 'yes'),
(55, 0, 'html_type', 'text/html', 'yes'),
(56, 0, 'use_trackback', '0', 'yes'),
(57, 0, 'default_role', 'subscriber', 'yes'),
(58, 0, 'db_version', '6124', 'yes'),
(59, 0, 'uploads_use_yearmonth_folders', '1', 'yes'),
(60, 0, 'upload_path', 'wp-content/uploads', 'yes'),
(61, 0, 'secret', 'f90a3e64cd5947b830ffcb7fe1126ea7', 'yes'),
(62, 0, 'blog_public', '0', 'yes'),
(63, 0, 'default_link_category', '2', 'yes'),
(64, 0, 'show_on_front', 'posts', 'yes'),
(65, 0, 'tag_base', '', 'yes'),
(66, 0, 'wp_user_roles', 'a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:48:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:34:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:10:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:5:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}', 'yes'),
(68, 0, 'widget_categories', 'a:2:{s:6:\"number\";i:1;i:1;a:4:{s:5:\"count\";b:0;s:12:\"hierarchical\";b:0;s:8:\"dropdown\";b:0;s:5:\"title\";s:0:\"\";}}', 'yes'),
(92, 0, 'cron', 'a:1:{s:7:\"version\";i:2;}', 'yes'),
(79, 0, 'update_core', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1504636252;s:15:\"version_checked\";s:5:\"2.3.2\";s:8:\"response\";s:7:\"upgrade\";s:3:\"url\";s:30:\"http://wordpress.org/download/\";}', 'yes'),
(80, 0, 'rss_65b518ff39262941bd5a283defe26c3e', 'O:9:\"magpierss\":17:{s:6:\"parser\";i:0;s:12:\"current_item\";a:0:{}s:5:\"items\";a:0:{}s:7:\"channel\";a:4:{s:5:\"title\";s:56:\"Google Blog Search: link:http://jaggerdog.com/wordpress/\";s:4:\"link\";s:115:\"http://blogsearch.google.com/blogsearch?hl=en&scoring=d&ie=ISO-8859-1&num=10&q=link:http://jaggerdog.com/wordpress/\";s:11:\"description\";s:91:\"Your search - <b>link:http://jaggerdog.com/wordpress/</b> - did not match any documents.   \";s:7:\"tagline\";s:91:\"Your search - <b>link:http://jaggerdog.com/wordpress/</b> - did not match any documents.   \";}s:9:\"textinput\";a:0:{}s:5:\"image\";a:0:{}s:9:\"feed_type\";s:3:\"RSS\";s:12:\"feed_version\";s:3:\"2.0\";s:5:\"stack\";a:0:{}s:9:\"inchannel\";b:0;s:6:\"initem\";b:0;s:9:\"incontent\";b:0;s:11:\"intextinput\";b:0;s:7:\"inimage\";b:0;s:13:\"current_field\";s:0:\"\";s:17:\"current_namespace\";b:0;s:19:\"_CONTENT_CONSTRUCTS\";a:6:{i:0;s:7:\"content\";i:1;s:7:\"summary\";i:2;s:4:\"info\";i:3;s:5:\"title\";i:4;s:7:\"tagline\";i:5;s:9:\"copyright\";}}', 'no'),
(81, 0, 'rss_65b518ff39262941bd5a283defe26c3e_ts', '1210880485', 'no');
INSERT INTO `wp_options` (`option_id`, `blog_id`, `option_name`, `option_value`, `autoload`) VALUES
(82, 0, 'rss_0ff4b43bd116a9d8720d689c80e7dfd4', 'O:9:\"MagpieRSS\":18:{s:6:\"parser\";i:0;s:12:\"current_item\";a:0:{}s:5:\"items\";a:10:{i:0;a:13:{s:5:\"title\";s:23:\"Event Organizers Unite!\";s:4:\"link\";s:57:\"http://wordpress.org/news/2012/07/event-organizers-unite/\";s:8:\"comments\";s:66:\"http://wordpress.org/news/2012/07/event-organizers-unite/#comments\";s:7:\"pubdate\";s:31:\"Fri, 13 Jul 2012 08:18:15 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jane Wells\";}s:8:\"category\";s:60:\"CommunityEventsclassescontributorshackathonsmeetupsWordCamps\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2412\";s:11:\"description\";s:388:\"I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:3709:\"<p>I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a central hub of activity for these folks. Despite the many informal connections between community organizers, we weren&#8217;t taking advantage of the huge existing knowledge base as new organizers stepped up to the plate.</p>\n<p>With the creation of <a href=\"http://make.wordpress.org/events/\">this new contributor group</a>, we finally have a way to organize and recognize these kinds of contributions, a clear avenue for feedback and input when it comes to policies around official events, and the opportunity to create even more connections between community organizers through mentorship programs and group projects. I&#8217;m especially excited about the creation of this group because until now the role of community organizer, while one of the most important, has not gotten the same recognition as higher-profile contribution methods such as forum support or core code contribution. That is something I hope this group will change, and the local organizers can be recognized for the community leaders they are.*</p>\n<p>If you are the organizer of a local WordCamp, WordPress meetup, etc., head over to <a href=\"http://make.wordpress.org/events/\">http://make.wordpress.org/events/</a> and introduce yourself so we can include you in the fun!</p>\n<p>Speaking of meetups, an update on <a href=\"http://wordpress.org/news/2012/01/year-of-the-meetup/\">my last post about meetups</a> is long overdue. With around 500 meetup organizers (and/or potential organizers) responding to my last survey, it took much longer than anticipated to review all the responses. We&#8217;re working now with meetup.com to issue invitations to join a centralized WordPress Meetup account, so if you filled out the form earlier this year, you should be hearing from them soon. The first wave of existing meetup account transfers (for those who opted in) should happen in the next two weeks, with additional waves every 3 months thereafter (and new groups will be able to be created along the way).</p>\n<p>The <a href=\"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/\">contributor summit</a> that is being planned for the end of October also generated hundreds of responses/nominations, so that review process is still happening, but we should be announcing some basic plans and issuing invitations soon.</p>\n<p>And finally, it would be impossible to talk about in-person WordPress events without mentioning the upcoming annual <a href=\"http://2012.sf.wordcamp.org\">WordCamp in San Francisco</a>. As the event that represents the worldwide project as a whole, it&#8217;s the perfect time to evaluate where we stand as a project and as a community, to help determine where we go next. If you&#8217;re a WordPress user, developer, or in any way a part of our vast and interconnected ecosystem, please take a moment to fill in the <a href=\"http://wpsurvey.polldaddy.com/s/wp-2012\">2nd annual WordPress survey</a>. It&#8217;s just a couple of questions, and your input would be greatly appreciated. The results of the survey will be announced at <a href=\"http://2012.sf.wordcamp.org\">WSCF</a>, and a report issued shortly thereafter.</p>\n<p>Thanks!</p>\n<p>*<em> I am also of the firm belief that academic and arts activities should earn varsity letters just like sports teams do &#8212; go mathletes! </em></p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:62:\"http://wordpress.org/news/2012/07/event-organizers-unite/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:388:\"I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a [...]\";s:12:\"atom_content\";s:3709:\"<p>I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a central hub of activity for these folks. Despite the many informal connections between community organizers, we weren&#8217;t taking advantage of the huge existing knowledge base as new organizers stepped up to the plate.</p>\n<p>With the creation of <a href=\"http://make.wordpress.org/events/\">this new contributor group</a>, we finally have a way to organize and recognize these kinds of contributions, a clear avenue for feedback and input when it comes to policies around official events, and the opportunity to create even more connections between community organizers through mentorship programs and group projects. I&#8217;m especially excited about the creation of this group because until now the role of community organizer, while one of the most important, has not gotten the same recognition as higher-profile contribution methods such as forum support or core code contribution. That is something I hope this group will change, and the local organizers can be recognized for the community leaders they are.*</p>\n<p>If you are the organizer of a local WordCamp, WordPress meetup, etc., head over to <a href=\"http://make.wordpress.org/events/\">http://make.wordpress.org/events/</a> and introduce yourself so we can include you in the fun!</p>\n<p>Speaking of meetups, an update on <a href=\"http://wordpress.org/news/2012/01/year-of-the-meetup/\">my last post about meetups</a> is long overdue. With around 500 meetup organizers (and/or potential organizers) responding to my last survey, it took much longer than anticipated to review all the responses. We&#8217;re working now with meetup.com to issue invitations to join a centralized WordPress Meetup account, so if you filled out the form earlier this year, you should be hearing from them soon. The first wave of existing meetup account transfers (for those who opted in) should happen in the next two weeks, with additional waves every 3 months thereafter (and new groups will be able to be created along the way).</p>\n<p>The <a href=\"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/\">contributor summit</a> that is being planned for the end of October also generated hundreds of responses/nominations, so that review process is still happening, but we should be announcing some basic plans and issuing invitations soon.</p>\n<p>And finally, it would be impossible to talk about in-person WordPress events without mentioning the upcoming annual <a href=\"http://2012.sf.wordcamp.org\">WordCamp in San Francisco</a>. As the event that represents the worldwide project as a whole, it&#8217;s the perfect time to evaluate where we stand as a project and as a community, to help determine where we go next. If you&#8217;re a WordPress user, developer, or in any way a part of our vast and interconnected ecosystem, please take a moment to fill in the <a href=\"http://wpsurvey.polldaddy.com/s/wp-2012\">2nd annual WordPress survey</a>. It&#8217;s just a couple of questions, and your input would be greatly appreciated. The results of the survey will be announced at <a href=\"http://2012.sf.wordcamp.org\">WSCF</a>, and a report issued shortly thereafter.</p>\n<p>Thanks!</p>\n<p>*<em> I am also of the firm belief that academic and arts activities should earn varsity letters just like sports teams do &#8212; go mathletes! </em></p>\n\";}i:1;a:13:{s:5:\"title\";s:48:\"WordPress 3.4.1 Maintenance and Security Release\";s:4:\"link\";s:50:\"http://wordpress.org/news/2012/06/wordpress-3-4-1/\";s:8:\"comments\";s:59:\"http://wordpress.org/news/2012/06/wordpress-3-4-1/#comments\";s:7:\"pubdate\";s:31:\"Wed, 27 Jun 2012 19:57:46 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:12:\"Andrew Nacin\";}s:8:\"category\";s:16:\"ReleasesSecurity\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2383\";s:11:\"description\";s:379:\"WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses 18 bugs with version 3.4, including: Fixes an issue where a theme&#8217;s page templates were sometimes not detected. Addresses problems with some category permalink [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:1585:\"<p>WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses <a href=\"http://core.trac.wordpress.org/query?status=closed&amp;resolution=fixed&amp;milestone=3.4.1&amp;group=resolution&amp;order=severity&amp;desc=1\">18 bugs</a> with version 3.4, including:</p>\n<ul>\n<li>Fixes an issue where a theme&#8217;s page templates were sometimes not detected.</li>\n<li>Addresses problems with some category permalink structures.</li>\n<li>Better handling for plugins or themes loading JavaScript incorrectly.</li>\n<li>Adds early support for uploading images on iOS 6 devices.</li>\n<li>Allows for a technique commonly used by plugins to detect a network-wide activation.</li>\n<li>Better compatibility with servers running certain versions of PHP (5.2.4, 5.4) or with uncommon setups (safe mode, open_basedir), which had caused warnings or in some cases prevented emails from being sent.</li>\n</ul>\n<p>Version 3.4.1 also fixes a few security issues and contains some security hardening. The vulnerabilities included potential information disclosure as well as an bug that affects multisite installs with untrusted users. These issues were discovered and fixed by the WordPress security team.</p>\n<p><strong><a href=\"http://wordpress.org/download/\">Download 3.4.1</a> now or visit Dashboard ? Updates in your site admin to update now.</strong></p>\n<p><em>Green was a bit green<br />\nWe have hardened it up some<br />\nUpdate WordPress now</em></p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:55:\"http://wordpress.org/news/2012/06/wordpress-3-4-1/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:379:\"WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses 18 bugs with version 3.4, including: Fixes an issue where a theme&#8217;s page templates were sometimes not detected. Addresses problems with some category permalink [...]\";s:12:\"atom_content\";s:1585:\"<p>WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses <a href=\"http://core.trac.wordpress.org/query?status=closed&amp;resolution=fixed&amp;milestone=3.4.1&amp;group=resolution&amp;order=severity&amp;desc=1\">18 bugs</a> with version 3.4, including:</p>\n<ul>\n<li>Fixes an issue where a theme&#8217;s page templates were sometimes not detected.</li>\n<li>Addresses problems with some category permalink structures.</li>\n<li>Better handling for plugins or themes loading JavaScript incorrectly.</li>\n<li>Adds early support for uploading images on iOS 6 devices.</li>\n<li>Allows for a technique commonly used by plugins to detect a network-wide activation.</li>\n<li>Better compatibility with servers running certain versions of PHP (5.2.4, 5.4) or with uncommon setups (safe mode, open_basedir), which had caused warnings or in some cases prevented emails from being sent.</li>\n</ul>\n<p>Version 3.4.1 also fixes a few security issues and contains some security hardening. The vulnerabilities included potential information disclosure as well as an bug that affects multisite installs with untrusted users. These issues were discovered and fixed by the WordPress security team.</p>\n<p><strong><a href=\"http://wordpress.org/download/\">Download 3.4.1</a> now or visit Dashboard ? Updates in your site admin to update now.</strong></p>\n<p><em>Green was a bit green<br />\nWe have hardened it up some<br />\nUpdate WordPress now</em></p>\n\";}i:2;a:13:{s:5:\"title\";s:25:\"WordPress 3.4 “Green”\";s:4:\"link\";s:40:\"http://wordpress.org/news/2012/06/green/\";s:8:\"comments\";s:49:\"http://wordpress.org/news/2012/06/green/#comments\";s:7:\"pubdate\";s:31:\"Wed, 13 Jun 2012 18:42:40 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Matt Mullenweg\";}s:8:\"category\";s:8:\"Releases\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2334\";s:11:\"description\";s:386:\"WordPress 3.4 is here and out the door. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist Grant Green whose soulful simplicity has kept many of us company during this release. This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights: For [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:15280:\"<p>WordPress 3.4 is <a href=\"http://wordpress.org/download/\">here and out the door</a>. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist <a href=\"http://en.wikipedia.org/wiki/Grant_Green\">Grant Green</a> whose soulful simplicity has kept many of us company during this release.</p>\n<p>This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights:</p>\n<div id=\"v-Gg0EFixV-1\" class=\"video-player\"><embed id=\"v-Gg0EFixV-1-video\" src=\"http://s0.videopress.com/player.swf?v=1.03&amp;guid=Gg0EFixV&amp;isDynamicSeeking=true\" type=\"application/x-shockwave-flash\" width=\"692\" height=\"388\" title=\"Introducing WordPress 3.4 &quot;Green&quot;\" wmode=\"direct\" seamlesstabbing=\"true\" allowfullscreen=\"true\" allowscriptaccess=\"always\" overstretch=\"true\"></embed></div>\n<h3>For Users</h3>\n<p>The biggest change in 3.4 is the <strong>theme customizer</strong> which allows you to play around with various looks and settings for your current theme or one you&#8217;re thinking about switching to without publishing those changes to the whole world. For themes that support it, you can change colors, backgrounds, and of course custom image headers. We have more planned for the customizer down the road.</p>\n<p>Throughout the rest of the admin you&#8217;ll notice tweaks to make your everyday life easier. For example, if you have lots of themes we&#8217;ve made it quicker to browse them all at once without paging. We&#8217;ve made it possible to use images from your media library to populate custom headers, and for you to choose the height and width of your header images.</p>\n<p>We&#8217;ve expanded our embed support to include tweets: just put a Twitter permalink on its own line in the post editor and we&#8217;ll turn it into a beautiful embedded Tweet. And finally, image captions have been improved to allow HTML, like links, in them.</p>\n<h3>For Developers</h3>\n<p>There are hundreds of under-the-hood improvements in this release, notably in the XML-RPC, themes, and custom header APIs, and significant performance improvements in WP_Query and the translation system. <a href=\"http://codex.wordpress.org/Version_3.4\">The Codex has a pretty good summary of the developer features</a>, and you can always <a href=\"http://core.trac.wordpress.org/milestone/3.4\">dive into Trac directly</a>.</p>\n<p>We&#8217;ve also <a href=\"http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/\">put together a busy developer&#8217;s field guide to the new APIs in 3.4</a>.</p>\n<h3>It takes a village</h3>\n<p>Here are some of the fine folks who were involved in bringing 3.4 to the world:</p>\n<p><a href=\"http://profiles.wordpress.org/082net\">082net</a>, <a href=\"http://profiles.wordpress.org/aaroncampbell\">Aaron D. Campbell</a>, <a href=\"http://profiles.wordpress.org/kawauso\">Adam Harley</a>, <a href=\"http://profiles.wordpress.org/ajacommerce\">AJ Acevedo</a>, <a href=\"http://profiles.wordpress.org/akshayagarwal\">akshayagarwal</a>, <a href=\"http://profiles.wordpress.org/xknown\">Alex Concha</a>, <a href=\"http://profiles.wordpress.org/alexkingorg\">Alex King</a>, <a href=\"http://profiles.wordpress.org/viper007bond\">Alex Mills (Viper007Bond)</a>, <a href=\"http://profiles.wordpress.org/ampt\">ampt</a>, <a href=\"http://profiles.wordpress.org/sabreuse\">Amy Hendrix</a>, <a href=\"http://profiles.wordpress.org/andrea_r\">Andrea Rennick</a>, <a href=\"http://profiles.wordpress.org/nacin\">Andrew Nacin</a>, <a href=\"http://profiles.wordpress.org/azaozz\">Andrew Ozz</a>, <a href=\"http://profiles.wordpress.org/andrewryno\">Andrew Ryno</a>, <a href=\"http://profiles.wordpress.org/andy\">Andy Skelton</a>, <a href=\"http://profiles.wordpress.org/arieputranto\">Arie Putranto</a>, <a href=\"http://profiles.wordpress.org/filosofo\">Austin Matzko</a>, <a href=\"http://profiles.wordpress.org/barry\">Barry</a>, <a href=\"http://profiles.wordpress.org/benchapman\">BenChapman</a>, <a href=\"http://profiles.wordpress.org/husobj\">Ben Huson</a>, <a href=\"http://profiles.wordpress.org/benbalter\">Benjamin J. Balter</a>, <a href=\"http://profiles.wordpress.org/billerickson\">Bill Erickson</a>, <a href=\"http://profiles.wordpress.org/bananastalktome\">Billy (bananastalktome)</a>, <a href=\"http://profiles.wordpress.org/boonebgorges\">Boone Gorges</a>, <a href=\"http://profiles.wordpress.org/camiloclc\">camiloclc</a>, <a href=\"http://profiles.wordpress.org/casben79\">casben79</a>, <a href=\"http://profiles.wordpress.org/caspie\">Caspie</a>, <a href=\"http://profiles.wordpress.org/ceefour\">ceefour</a>, <a href=\"http://profiles.wordpress.org/cheald\">cheald</a>, <a href=\"http://profiles.wordpress.org/chellycat\">chellycat</a>, <a href=\"http://profiles.wordpress.org/chexee\">Chelsea Otakan</a>, <a href=\"http://profiles.wordpress.org/chipbennett\">Chip Bennett</a>, <a href=\"http://profiles.wordpress.org/c3mdigital\">Chris Olbekson</a>, <a href=\"http://profiles.wordpress.org/coenjacobs\">Coen Jacobs</a>, <a href=\"http://profiles.wordpress.org/scribu\">Cristi Burc&#259;</a>, <a href=\"http://profiles.wordpress.org/cyapow\">Cyapow</a>, <a href=\"http://profiles.wordpress.org/djcp\">Dan Collis-Puro</a>, <a href=\"http://profiles.wordpress.org/danielbachhuber\">Daniel Bachhuber</a>, <a href=\"http://profiles.wordpress.org/convissor\">Daniel Convissor</a>, <a href=\"http://profiles.wordpress.org/redsweater\">Daniel Jalkut (Red Sweater)</a>, <a href=\"http://profiles.wordpress.org/daniloercoli\">daniloercoli</a>, <a href=\"http://profiles.wordpress.org/koopersmith\">Daryl Koopersmith</a>, <a href=\"http://profiles.wordpress.org/dgwyer\">David Gwyer</a>, <a href=\"http://profiles.wordpress.org/deltafactory\">deltafactory</a>, <a href=\"http://profiles.wordpress.org/demetris\">demetris</a>, <a href=\"http://profiles.wordpress.org/dd32\">Dion Hulse</a>, <a href=\"http://profiles.wordpress.org/dllh\">dllh</a>, <a href=\"http://profiles.wordpress.org/ocean90\">Dominik Schilling</a>, <a href=\"http://profiles.wordpress.org/dougwrites\">Doug Provencio</a>, <a href=\"http://profiles.wordpress.org/drewapicture\">Drew Jaynes (DrewAPicture)</a>, <a href=\"http://profiles.wordpress.org/ebababi\">ebababi</a>, <a href=\"http://profiles.wordpress.org/edward-mindreantre\">edward-mindreantre</a>, <a href=\"http://profiles.wordpress.org/emhr\">emhr</a>, <a href=\"http://profiles.wordpress.org/empireoflight\">Empireoflight</a>, <a href=\"http://profiles.wordpress.org/ericlewis\">Eric Andrew Lewis</a>, <a href=\"http://profiles.wordpress.org/ericmann\">Eric Mann</a>, <a href=\"http://profiles.wordpress.org/ejdanderson\">Evan Anderson</a>, <a href=\"http://profiles.wordpress.org/evansolomon\">Evan Solomon</a>, <a href=\"http://profiles.wordpress.org/fredwu\">Fred Wu</a>, <a href=\"http://profiles.wordpress.org/ounziw\">Fumito Mizuno</a>, <a href=\"http://profiles.wordpress.org/garyc40\">Gary Cao</a>, <a href=\"http://profiles.wordpress.org/garyj\">Gary Jones</a>, <a href=\"http://profiles.wordpress.org/gautamgupta\">Gautam</a>, <a href=\"http://profiles.wordpress.org/soulseekah\">Gennady Kovshenin</a>, <a href=\"http://profiles.wordpress.org/mamaduka\">George Mamadashvili</a>, <a href=\"http://profiles.wordpress.org/georgestephanis\">George Stephanis</a>, <a href=\"http://profiles.wordpress.org/webord\">Gustavo Bordoni</a>, <a href=\"http://profiles.wordpress.org/hearvox\">hearvox</a>, <a href=\"http://profiles.wordpress.org/helenyhou\">Helen Hou-Sandi</a>, <a href=\"http://profiles.wordpress.org/hugobaeta\">Hugo Baeta</a>, <a href=\"http://profiles.wordpress.org/iandstewart\">Ian Stewart</a>, <a href=\"http://profiles.wordpress.org/insertvisionhere\">insertvisionhere</a>, <a href=\"http://profiles.wordpress.org/ipstenu\">Ipstenu</a>, <a href=\"http://profiles.wordpress.org/master-jake\">Jacob Chappell</a>, <a href=\"http://profiles.wordpress.org/jane\">Jane Wells</a>, <a href=\"http://profiles.wordpress.org/japh\">Japh</a>, <a href=\"http://profiles.wordpress.org/jaquers\">jaquers</a>, <a href=\"http://profiles.wordpress.org/jarretc\">JarretC</a>, <a href=\"http://profiles.wordpress.org/jeremyclarke\">jeremyclarke</a>, <a href=\"http://profiles.wordpress.org/jeremyfelt\">Jeremy Felt</a>, <a href=\"http://profiles.wordpress.org/jayjdk\">Jesper Johansen (Jayjdk)</a>, <a href=\"http://profiles.wordpress.org/jiehanzheng\">Jiehan Zheng</a>, <a href=\"http://profiles.wordpress.org/intoxstudio\">Joachim Jensen (Intox Studio)</a>, <a href=\"http://profiles.wordpress.org/jkudish\">Joachim Kudish (jkudish)</a>, <a href=\"http://profiles.wordpress.org/johnbillion\">John Blackbourn (johnbillion)</a>, <a href=\"http://profiles.wordpress.org/aldenta\">John Ford</a>, <a href=\"http://profiles.wordpress.org/johnjamesjacoby\">John James Jacoby</a>, <a href=\"http://profiles.wordpress.org/duck_\">Jon Cave</a>, <a href=\"http://profiles.wordpress.org/joostdevalk\">Joost de Valk</a>, <a href=\"http://profiles.wordpress.org/koke\">Jorge Bernal</a>, <a href=\"http://profiles.wordpress.org/josephscott\">Joseph Scott</a>, <a href=\"http://profiles.wordpress.org/devesine\">Justin</a>, <a href=\"http://profiles.wordpress.org/justindgivens\">Justin Givens</a>, <a href=\"http://profiles.wordpress.org/trepmal\">Kailey Lampert (trepmal)</a>, <a href=\"http://profiles.wordpress.org/kenan3008\">Kenan Dervisevic</a>, <a href=\"http://profiles.wordpress.org/kovshenin\">Konstantin Kovshenin</a>, <a href=\"http://profiles.wordpress.org/kobenland\">Konstantin Obenland</a>, <a href=\"http://profiles.wordpress.org/klagraff\">Kristopher Lagraff</a>, <a href=\"http://profiles.wordpress.org/kurtpayne\">Kurt Payne</a>, <a href=\"http://profiles.wordpress.org/lancewillett\">Lance Willett</a>, <a href=\"http://profiles.wordpress.org/lardjo\">Lardjo</a>, <a href=\"http://profiles.wordpress.org/leewillis77\">Lee Willis (leewillis77)</a>, <a href=\"http://profiles.wordpress.org/linuxologos\">linuxologos</a>, <a href=\"http://profiles.wordpress.org/latz\">Lutz Schroer</a>, <a href=\"http://profiles.wordpress.org/settle\">Mantas Malcius</a>, <a href=\"http://profiles.wordpress.org/netweblogic\">Marcus</a>, <a href=\"http://profiles.wordpress.org/markjaquith\">Mark Jaquith</a>, <a href=\"http://profiles.wordpress.org/markoheijnen\">Marko Heijnen</a>, <a href=\"http://profiles.wordpress.org/markauk\">Mark Rowatt Anderson</a>, <a href=\"http://profiles.wordpress.org/matveb\">Matias Ventura</a>, <a href=\"http://profiles.wordpress.org/sivel\">Matt Martz</a>, <a href=\"http://profiles.wordpress.org/mattonomics\">mattonomics</a>, <a href=\"http://profiles.wordpress.org/iammattthomas\">Matt Thomas</a>, <a href=\"http://profiles.wordpress.org/mattwiebe\">Matt Wiebe</a>, <a href=\"http://profiles.wordpress.org/mattyrob\">MattyRob</a>, <a href=\"http://profiles.wordpress.org/maxcutler\">Max Cutler</a>, <a href=\"http://profiles.wordpress.org/merty\">Mert Yazicioglu</a>, <a href=\"http://profiles.wordpress.org/mgolawala\">mgolawala</a>, <a href=\"http://profiles.wordpress.org/mdawaffe\">Michael Adams (mdawaffe)</a>, <a href=\"http://profiles.wordpress.org/tw2113\">Michael Beckwith</a>, <a href=\"http://profiles.wordpress.org/mfields\">Michael Fields</a>, <a href=\"http://profiles.wordpress.org/mikeschinkel\">Mike Schinkel</a>, <a href=\"http://profiles.wordpress.org/dh-shredder\">Mike Schroder</a>, <a href=\"http://profiles.wordpress.org/toppa\">Mike Toppa</a>, <a href=\"http://profiles.wordpress.org/dimadin\">Milan Dinic</a>, <a href=\"http://profiles.wordpress.org/mitchoyoshitaka\">mitcho (Michael Yoshitaka Erlewine)</a>, <a href=\"http://profiles.wordpress.org/batmoo\">Mohammad Jangda</a>, <a href=\"http://profiles.wordpress.org/mrtorrent\">mrtorrent</a>, <a href=\"http://profiles.wordpress.org/namely\">Name.ly</a>, <a href=\"http://profiles.wordpress.org/Nao\">Naoko McCracken</a>, <a href=\"http://profiles.wordpress.org/alex-ye\">Nashwan Doaqan</a>, <a href=\"http://profiles.wordpress.org/niallkennedy\">Niall Kennedy</a>, <a href=\"http://profiles.wordpress.org/nikolayyordanov\">Nikolay Yordanov</a>, <a href=\"http://profiles.wordpress.org/norocketsurgeon\">norocketsurgeon</a>, <a href=\"http://profiles.wordpress.org/npetetin\">npetetin</a>, <a href=\"http://profiles.wordpress.org/nunomorgadinho\">Nuno Morgadinho</a>, <a href=\"http://profiles.wordpress.org/ocollet\">Olivier Collet</a>, <a href=\"http://profiles.wordpress.org/pbiron\">Paul Biron</a>, <a href=\"http://profiles.wordpress.org/pavelevap\">pavelevap</a>, <a href=\"http://profiles.wordpress.org/petemall\">Pete Mall</a>, <a href=\"http://profiles.wordpress.org/westi\">Peter Westwood</a>, <a href=\"http://profiles.wordpress.org/pishmishy\">pishmishy</a>, <a href=\"http://profiles.wordpress.org/nprasath002\">Prasath Nadarajah</a>, <a href=\"http://profiles.wordpress.org/prettyboymp\">prettyboymp</a>, <a href=\"http://profiles.wordpress.org/ptahdunbar\">Ptah Dunbar</a>, <a href=\"http://profiles.wordpress.org/pw201\">pw201</a>, <a href=\"http://profiles.wordpress.org/ramiy\">Rami Yushuvaev</a>, <a href=\"http://profiles.wordpress.org/rarst\">Rarst</a>, <a href=\"http://profiles.wordpress.org/arena\">RENAUT</a>, <a href=\"http://profiles.wordpress.org/greuben\">Reuben Gunday</a>, <a href=\"http://profiles.wordpress.org/roscius\">Roscius</a>, <a href=\"http://profiles.wordpress.org/rosshanney\">Ross Hanney</a>, <a href=\"http://profiles.wordpress.org/russellwwest\">russellwwest</a>, <a href=\"http://profiles.wordpress.org/ryan\">Ryan Boren</a>, <a href=\"http://profiles.wordpress.org/ryanduff\">Ryan Duff</a>, <a href=\"http://profiles.wordpress.org/rmccue\">Ryan McCue</a>, <a href=\"http://profiles.wordpress.org/zeo\">Safirul Alredha</a>, <a href=\"http://profiles.wordpress.org/solarissmoke\">Samir Shah</a>, <a href=\"http://profiles.wordpress.org/otto42\">Samuel &#8220;Otto&#8221; Wood</a>, <a href=\"http://profiles.wordpress.org/tenpura\">Seisuke Kuraishi</a>, <a href=\"http://profiles.wordpress.org/sergeybiryukov\">Sergey Biryukov</a>, <a href=\"http://profiles.wordpress.org/simonwheatley\">Simon Wheatley</a>, <a href=\"http://profiles.wordpress.org/sirzooro\">sirzooro</a>, <a href=\"http://profiles.wordpress.org/sksmatt\">sksmatt</a>, <a href=\"http://profiles.wordpress.org/sushkov\">Stas Su&#537;kov</a>, <a href=\"http://profiles.wordpress.org/stephdau\">Stephane Daury (stephdau)</a>, <a href=\"http://profiles.wordpress.org/tamlyn\">tamlyn</a>, <a href=\"http://profiles.wordpress.org/griffinjt\">Thomas Griffin</a>, <a href=\"http://profiles.wordpress.org/tott\">Thorsten Ott</a>, <a href=\"http://profiles.wordpress.org/tobiasbg\">TobiasBg</a>, <a href=\"http://profiles.wordpress.org/tomauger\">Tom Auger</a>, <a href=\"http://profiles.wordpress.org/skithund\">Toni Viemero</a>, <a href=\"http://profiles.wordpress.org/transom\">transom</a>, <a href=\"http://profiles.wordpress.org/sorich87\">Ulrich Sossou</a>, <a href=\"http://profiles.wordpress.org/utkarsh\">Utkarsh Kukreti</a>, <a href=\"http://profiles.wordpress.org/wojtekszkutnik\">Wojtek Szkutnik</a>, <a href=\"http://profiles.wordpress.org/wonderslug\">wonderslug</a>, <a href=\"http://profiles.wordpress.org/xibe\">Xavier Borderie</a>, <a href=\"http://profiles.wordpress.org/yoavf\">Yoav Farhi</a>, <a href=\"http://profiles.wordpress.org/thezman84\">Zach &#8220;The Z Man&#8221; Abernathy</a>, <a href=\"http://profiles.wordpress.org/tollmanz\">Zack Tollman</a>, <a href=\"http://profiles.wordpress.org/vanillalounge\">Ze Fontainhas</a>, and <a href=\"http://profiles.wordpress.org/zx2c4\">zx2c4</a>.</p>\n<p>See you next time!</p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:45:\"http://wordpress.org/news/2012/06/green/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:386:\"WordPress 3.4 is here and out the door. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist Grant Green whose soulful simplicity has kept many of us company during this release. This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights: For [...]\";s:12:\"atom_content\";s:15280:\"<p>WordPress 3.4 is <a href=\"http://wordpress.org/download/\">here and out the door</a>. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist <a href=\"http://en.wikipedia.org/wiki/Grant_Green\">Grant Green</a> whose soulful simplicity has kept many of us company during this release.</p>\n<p>This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights:</p>\n<div id=\"v-Gg0EFixV-1\" class=\"video-player\"><embed id=\"v-Gg0EFixV-1-video\" src=\"http://s0.videopress.com/player.swf?v=1.03&amp;guid=Gg0EFixV&amp;isDynamicSeeking=true\" type=\"application/x-shockwave-flash\" width=\"692\" height=\"388\" title=\"Introducing WordPress 3.4 &quot;Green&quot;\" wmode=\"direct\" seamlesstabbing=\"true\" allowfullscreen=\"true\" allowscriptaccess=\"always\" overstretch=\"true\"></embed></div>\n<h3>For Users</h3>\n<p>The biggest change in 3.4 is the <strong>theme customizer</strong> which allows you to play around with various looks and settings for your current theme or one you&#8217;re thinking about switching to without publishing those changes to the whole world. For themes that support it, you can change colors, backgrounds, and of course custom image headers. We have more planned for the customizer down the road.</p>\n<p>Throughout the rest of the admin you&#8217;ll notice tweaks to make your everyday life easier. For example, if you have lots of themes we&#8217;ve made it quicker to browse them all at once without paging. We&#8217;ve made it possible to use images from your media library to populate custom headers, and for you to choose the height and width of your header images.</p>\n<p>We&#8217;ve expanded our embed support to include tweets: just put a Twitter permalink on its own line in the post editor and we&#8217;ll turn it into a beautiful embedded Tweet. And finally, image captions have been improved to allow HTML, like links, in them.</p>\n<h3>For Developers</h3>\n<p>There are hundreds of under-the-hood improvements in this release, notably in the XML-RPC, themes, and custom header APIs, and significant performance improvements in WP_Query and the translation system. <a href=\"http://codex.wordpress.org/Version_3.4\">The Codex has a pretty good summary of the developer features</a>, and you can always <a href=\"http://core.trac.wordpress.org/milestone/3.4\">dive into Trac directly</a>.</p>\n<p>We&#8217;ve also <a href=\"http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/\">put together a busy developer&#8217;s field guide to the new APIs in 3.4</a>.</p>\n<h3>It takes a village</h3>\n<p>Here are some of the fine folks who were involved in bringing 3.4 to the world:</p>\n<p><a href=\"http://profiles.wordpress.org/082net\">082net</a>, <a href=\"http://profiles.wordpress.org/aaroncampbell\">Aaron D. Campbell</a>, <a href=\"http://profiles.wordpress.org/kawauso\">Adam Harley</a>, <a href=\"http://profiles.wordpress.org/ajacommerce\">AJ Acevedo</a>, <a href=\"http://profiles.wordpress.org/akshayagarwal\">akshayagarwal</a>, <a href=\"http://profiles.wordpress.org/xknown\">Alex Concha</a>, <a href=\"http://profiles.wordpress.org/alexkingorg\">Alex King</a>, <a href=\"http://profiles.wordpress.org/viper007bond\">Alex Mills (Viper007Bond)</a>, <a href=\"http://profiles.wordpress.org/ampt\">ampt</a>, <a href=\"http://profiles.wordpress.org/sabreuse\">Amy Hendrix</a>, <a href=\"http://profiles.wordpress.org/andrea_r\">Andrea Rennick</a>, <a href=\"http://profiles.wordpress.org/nacin\">Andrew Nacin</a>, <a href=\"http://profiles.wordpress.org/azaozz\">Andrew Ozz</a>, <a href=\"http://profiles.wordpress.org/andrewryno\">Andrew Ryno</a>, <a href=\"http://profiles.wordpress.org/andy\">Andy Skelton</a>, <a href=\"http://profiles.wordpress.org/arieputranto\">Arie Putranto</a>, <a href=\"http://profiles.wordpress.org/filosofo\">Austin Matzko</a>, <a href=\"http://profiles.wordpress.org/barry\">Barry</a>, <a href=\"http://profiles.wordpress.org/benchapman\">BenChapman</a>, <a href=\"http://profiles.wordpress.org/husobj\">Ben Huson</a>, <a href=\"http://profiles.wordpress.org/benbalter\">Benjamin J. Balter</a>, <a href=\"http://profiles.wordpress.org/billerickson\">Bill Erickson</a>, <a href=\"http://profiles.wordpress.org/bananastalktome\">Billy (bananastalktome)</a>, <a href=\"http://profiles.wordpress.org/boonebgorges\">Boone Gorges</a>, <a href=\"http://profiles.wordpress.org/camiloclc\">camiloclc</a>, <a href=\"http://profiles.wordpress.org/casben79\">casben79</a>, <a href=\"http://profiles.wordpress.org/caspie\">Caspie</a>, <a href=\"http://profiles.wordpress.org/ceefour\">ceefour</a>, <a href=\"http://profiles.wordpress.org/cheald\">cheald</a>, <a href=\"http://profiles.wordpress.org/chellycat\">chellycat</a>, <a href=\"http://profiles.wordpress.org/chexee\">Chelsea Otakan</a>, <a href=\"http://profiles.wordpress.org/chipbennett\">Chip Bennett</a>, <a href=\"http://profiles.wordpress.org/c3mdigital\">Chris Olbekson</a>, <a href=\"http://profiles.wordpress.org/coenjacobs\">Coen Jacobs</a>, <a href=\"http://profiles.wordpress.org/scribu\">Cristi Burc&#259;</a>, <a href=\"http://profiles.wordpress.org/cyapow\">Cyapow</a>, <a href=\"http://profiles.wordpress.org/djcp\">Dan Collis-Puro</a>, <a href=\"http://profiles.wordpress.org/danielbachhuber\">Daniel Bachhuber</a>, <a href=\"http://profiles.wordpress.org/convissor\">Daniel Convissor</a>, <a href=\"http://profiles.wordpress.org/redsweater\">Daniel Jalkut (Red Sweater)</a>, <a href=\"http://profiles.wordpress.org/daniloercoli\">daniloercoli</a>, <a href=\"http://profiles.wordpress.org/koopersmith\">Daryl Koopersmith</a>, <a href=\"http://profiles.wordpress.org/dgwyer\">David Gwyer</a>, <a href=\"http://profiles.wordpress.org/deltafactory\">deltafactory</a>, <a href=\"http://profiles.wordpress.org/demetris\">demetris</a>, <a href=\"http://profiles.wordpress.org/dd32\">Dion Hulse</a>, <a href=\"http://profiles.wordpress.org/dllh\">dllh</a>, <a href=\"http://profiles.wordpress.org/ocean90\">Dominik Schilling</a>, <a href=\"http://profiles.wordpress.org/dougwrites\">Doug Provencio</a>, <a href=\"http://profiles.wordpress.org/drewapicture\">Drew Jaynes (DrewAPicture)</a>, <a href=\"http://profiles.wordpress.org/ebababi\">ebababi</a>, <a href=\"http://profiles.wordpress.org/edward-mindreantre\">edward-mindreantre</a>, <a href=\"http://profiles.wordpress.org/emhr\">emhr</a>, <a href=\"http://profiles.wordpress.org/empireoflight\">Empireoflight</a>, <a href=\"http://profiles.wordpress.org/ericlewis\">Eric Andrew Lewis</a>, <a href=\"http://profiles.wordpress.org/ericmann\">Eric Mann</a>, <a href=\"http://profiles.wordpress.org/ejdanderson\">Evan Anderson</a>, <a href=\"http://profiles.wordpress.org/evansolomon\">Evan Solomon</a>, <a href=\"http://profiles.wordpress.org/fredwu\">Fred Wu</a>, <a href=\"http://profiles.wordpress.org/ounziw\">Fumito Mizuno</a>, <a href=\"http://profiles.wordpress.org/garyc40\">Gary Cao</a>, <a href=\"http://profiles.wordpress.org/garyj\">Gary Jones</a>, <a href=\"http://profiles.wordpress.org/gautamgupta\">Gautam</a>, <a href=\"http://profiles.wordpress.org/soulseekah\">Gennady Kovshenin</a>, <a href=\"http://profiles.wordpress.org/mamaduka\">George Mamadashvili</a>, <a href=\"http://profiles.wordpress.org/georgestephanis\">George Stephanis</a>, <a href=\"http://profiles.wordpress.org/webord\">Gustavo Bordoni</a>, <a href=\"http://profiles.wordpress.org/hearvox\">hearvox</a>, <a href=\"http://profiles.wordpress.org/helenyhou\">Helen Hou-Sandi</a>, <a href=\"http://profiles.wordpress.org/hugobaeta\">Hugo Baeta</a>, <a href=\"http://profiles.wordpress.org/iandstewart\">Ian Stewart</a>, <a href=\"http://profiles.wordpress.org/insertvisionhere\">insertvisionhere</a>, <a href=\"http://profiles.wordpress.org/ipstenu\">Ipstenu</a>, <a href=\"http://profiles.wordpress.org/master-jake\">Jacob Chappell</a>, <a href=\"http://profiles.wordpress.org/jane\">Jane Wells</a>, <a href=\"http://profiles.wordpress.org/japh\">Japh</a>, <a href=\"http://profiles.wordpress.org/jaquers\">jaquers</a>, <a href=\"http://profiles.wordpress.org/jarretc\">JarretC</a>, <a href=\"http://profiles.wordpress.org/jeremyclarke\">jeremyclarke</a>, <a href=\"http://profiles.wordpress.org/jeremyfelt\">Jeremy Felt</a>, <a href=\"http://profiles.wordpress.org/jayjdk\">Jesper Johansen (Jayjdk)</a>, <a href=\"http://profiles.wordpress.org/jiehanzheng\">Jiehan Zheng</a>, <a href=\"http://profiles.wordpress.org/intoxstudio\">Joachim Jensen (Intox Studio)</a>, <a href=\"http://profiles.wordpress.org/jkudish\">Joachim Kudish (jkudish)</a>, <a href=\"http://profiles.wordpress.org/johnbillion\">John Blackbourn (johnbillion)</a>, <a href=\"http://profiles.wordpress.org/aldenta\">John Ford</a>, <a href=\"http://profiles.wordpress.org/johnjamesjacoby\">John James Jacoby</a>, <a href=\"http://profiles.wordpress.org/duck_\">Jon Cave</a>, <a href=\"http://profiles.wordpress.org/joostdevalk\">Joost de Valk</a>, <a href=\"http://profiles.wordpress.org/koke\">Jorge Bernal</a>, <a href=\"http://profiles.wordpress.org/josephscott\">Joseph Scott</a>, <a href=\"http://profiles.wordpress.org/devesine\">Justin</a>, <a href=\"http://profiles.wordpress.org/justindgivens\">Justin Givens</a>, <a href=\"http://profiles.wordpress.org/trepmal\">Kailey Lampert (trepmal)</a>, <a href=\"http://profiles.wordpress.org/kenan3008\">Kenan Dervisevic</a>, <a href=\"http://profiles.wordpress.org/kovshenin\">Konstantin Kovshenin</a>, <a href=\"http://profiles.wordpress.org/kobenland\">Konstantin Obenland</a>, <a href=\"http://profiles.wordpress.org/klagraff\">Kristopher Lagraff</a>, <a href=\"http://profiles.wordpress.org/kurtpayne\">Kurt Payne</a>, <a href=\"http://profiles.wordpress.org/lancewillett\">Lance Willett</a>, <a href=\"http://profiles.wordpress.org/lardjo\">Lardjo</a>, <a href=\"http://profiles.wordpress.org/leewillis77\">Lee Willis (leewillis77)</a>, <a href=\"http://profiles.wordpress.org/linuxologos\">linuxologos</a>, <a href=\"http://profiles.wordpress.org/latz\">Lutz Schroer</a>, <a href=\"http://profiles.wordpress.org/settle\">Mantas Malcius</a>, <a href=\"http://profiles.wordpress.org/netweblogic\">Marcus</a>, <a href=\"http://profiles.wordpress.org/markjaquith\">Mark Jaquith</a>, <a href=\"http://profiles.wordpress.org/markoheijnen\">Marko Heijnen</a>, <a href=\"http://profiles.wordpress.org/markauk\">Mark Rowatt Anderson</a>, <a href=\"http://profiles.wordpress.org/matveb\">Matias Ventura</a>, <a href=\"http://profiles.wordpress.org/sivel\">Matt Martz</a>, <a href=\"http://profiles.wordpress.org/mattonomics\">mattonomics</a>, <a href=\"http://profiles.wordpress.org/iammattthomas\">Matt Thomas</a>, <a href=\"http://profiles.wordpress.org/mattwiebe\">Matt Wiebe</a>, <a href=\"http://profiles.wordpress.org/mattyrob\">MattyRob</a>, <a href=\"http://profiles.wordpress.org/maxcutler\">Max Cutler</a>, <a href=\"http://profiles.wordpress.org/merty\">Mert Yazicioglu</a>, <a href=\"http://profiles.wordpress.org/mgolawala\">mgolawala</a>, <a href=\"http://profiles.wordpress.org/mdawaffe\">Michael Adams (mdawaffe)</a>, <a href=\"http://profiles.wordpress.org/tw2113\">Michael Beckwith</a>, <a href=\"http://profiles.wordpress.org/mfields\">Michael Fields</a>, <a href=\"http://profiles.wordpress.org/mikeschinkel\">Mike Schinkel</a>, <a href=\"http://profiles.wordpress.org/dh-shredder\">Mike Schroder</a>, <a href=\"http://profiles.wordpress.org/toppa\">Mike Toppa</a>, <a href=\"http://profiles.wordpress.org/dimadin\">Milan Dinic</a>, <a href=\"http://profiles.wordpress.org/mitchoyoshitaka\">mitcho (Michael Yoshitaka Erlewine)</a>, <a href=\"http://profiles.wordpress.org/batmoo\">Mohammad Jangda</a>, <a href=\"http://profiles.wordpress.org/mrtorrent\">mrtorrent</a>, <a href=\"http://profiles.wordpress.org/namely\">Name.ly</a>, <a href=\"http://profiles.wordpress.org/Nao\">Naoko McCracken</a>, <a href=\"http://profiles.wordpress.org/alex-ye\">Nashwan Doaqan</a>, <a href=\"http://profiles.wordpress.org/niallkennedy\">Niall Kennedy</a>, <a href=\"http://profiles.wordpress.org/nikolayyordanov\">Nikolay Yordanov</a>, <a href=\"http://profiles.wordpress.org/norocketsurgeon\">norocketsurgeon</a>, <a href=\"http://profiles.wordpress.org/npetetin\">npetetin</a>, <a href=\"http://profiles.wordpress.org/nunomorgadinho\">Nuno Morgadinho</a>, <a href=\"http://profiles.wordpress.org/ocollet\">Olivier Collet</a>, <a href=\"http://profiles.wordpress.org/pbiron\">Paul Biron</a>, <a href=\"http://profiles.wordpress.org/pavelevap\">pavelevap</a>, <a href=\"http://profiles.wordpress.org/petemall\">Pete Mall</a>, <a href=\"http://profiles.wordpress.org/westi\">Peter Westwood</a>, <a href=\"http://profiles.wordpress.org/pishmishy\">pishmishy</a>, <a href=\"http://profiles.wordpress.org/nprasath002\">Prasath Nadarajah</a>, <a href=\"http://profiles.wordpress.org/prettyboymp\">prettyboymp</a>, <a href=\"http://profiles.wordpress.org/ptahdunbar\">Ptah Dunbar</a>, <a href=\"http://profiles.wordpress.org/pw201\">pw201</a>, <a href=\"http://profiles.wordpress.org/ramiy\">Rami Yushuvaev</a>, <a href=\"http://profiles.wordpress.org/rarst\">Rarst</a>, <a href=\"http://profiles.wordpress.org/arena\">RENAUT</a>, <a href=\"http://profiles.wordpress.org/greuben\">Reuben Gunday</a>, <a href=\"http://profiles.wordpress.org/roscius\">Roscius</a>, <a href=\"http://profiles.wordpress.org/rosshanney\">Ross Hanney</a>, <a href=\"http://profiles.wordpress.org/russellwwest\">russellwwest</a>, <a href=\"http://profiles.wordpress.org/ryan\">Ryan Boren</a>, <a href=\"http://profiles.wordpress.org/ryanduff\">Ryan Duff</a>, <a href=\"http://profiles.wordpress.org/rmccue\">Ryan McCue</a>, <a href=\"http://profiles.wordpress.org/zeo\">Safirul Alredha</a>, <a href=\"http://profiles.wordpress.org/solarissmoke\">Samir Shah</a>, <a href=\"http://profiles.wordpress.org/otto42\">Samuel &#8220;Otto&#8221; Wood</a>, <a href=\"http://profiles.wordpress.org/tenpura\">Seisuke Kuraishi</a>, <a href=\"http://profiles.wordpress.org/sergeybiryukov\">Sergey Biryukov</a>, <a href=\"http://profiles.wordpress.org/simonwheatley\">Simon Wheatley</a>, <a href=\"http://profiles.wordpress.org/sirzooro\">sirzooro</a>, <a href=\"http://profiles.wordpress.org/sksmatt\">sksmatt</a>, <a href=\"http://profiles.wordpress.org/sushkov\">Stas Su&#537;kov</a>, <a href=\"http://profiles.wordpress.org/stephdau\">Stephane Daury (stephdau)</a>, <a href=\"http://profiles.wordpress.org/tamlyn\">tamlyn</a>, <a href=\"http://profiles.wordpress.org/griffinjt\">Thomas Griffin</a>, <a href=\"http://profiles.wordpress.org/tott\">Thorsten Ott</a>, <a href=\"http://profiles.wordpress.org/tobiasbg\">TobiasBg</a>, <a href=\"http://profiles.wordpress.org/tomauger\">Tom Auger</a>, <a href=\"http://profiles.wordpress.org/skithund\">Toni Viemero</a>, <a href=\"http://profiles.wordpress.org/transom\">transom</a>, <a href=\"http://profiles.wordpress.org/sorich87\">Ulrich Sossou</a>, <a href=\"http://profiles.wordpress.org/utkarsh\">Utkarsh Kukreti</a>, <a href=\"http://profiles.wordpress.org/wojtekszkutnik\">Wojtek Szkutnik</a>, <a href=\"http://profiles.wordpress.org/wonderslug\">wonderslug</a>, <a href=\"http://profiles.wordpress.org/xibe\">Xavier Borderie</a>, <a href=\"http://profiles.wordpress.org/yoavf\">Yoav Farhi</a>, <a href=\"http://profiles.wordpress.org/thezman84\">Zach &#8220;The Z Man&#8221; Abernathy</a>, <a href=\"http://profiles.wordpress.org/tollmanz\">Zack Tollman</a>, <a href=\"http://profiles.wordpress.org/vanillalounge\">Ze Fontainhas</a>, and <a href=\"http://profiles.wordpress.org/zx2c4\">zx2c4</a>.</p>\n<p>See you next time!</p>\n\";}i:3;a:13:{s:5:\"title\";s:33:\"WordPress 3.4 Release Candidate 3\";s:4:\"link\";s:68:\"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-3/\";s:8:\"comments\";s:77:\"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-3/#comments\";s:7:\"pubdate\";s:31:\"Tue, 12 Jun 2012 00:30:14 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:12:\"Andrew Nacin\";}s:8:\"category\";s:18:\"DevelopmentTesting\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2326\";s:11:\"description\";s:325:\"The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds. There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:1376:\"<p>The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds.</p>\n<p>There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, you can post to the <a href=\"http://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a> in the support forums, or file a bug report on <a href=\"http://core.trac.wordpress.org/\">WordPress Trac</a>.</p>\n<p>To test WordPress 3.4, try the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href=\"http://wordpress.org/wordpress-3.4-RC3.zip\">download the release candidate here</a> (zip). Be sure to visit <strong><img style=\"vertical-align: text-top\" src=\"http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png\" alt=\"\" /> ? About</strong> for an updated list of features and under-the-hood changes. As a reminder: We’ve published some resources on the <a href=\"http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/\">development blog</a> to help plugin and theme developers prepare.</p>\n<p><em>The new live preview<br />\nNearing perfection, and yet?<br />\nNot yet. RC3</em></p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:73:\"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-3/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:325:\"The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds. There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, [...]\";s:12:\"atom_content\";s:1376:\"<p>The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds.</p>\n<p>There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, you can post to the <a href=\"http://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a> in the support forums, or file a bug report on <a href=\"http://core.trac.wordpress.org/\">WordPress Trac</a>.</p>\n<p>To test WordPress 3.4, try the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href=\"http://wordpress.org/wordpress-3.4-RC3.zip\">download the release candidate here</a> (zip). Be sure to visit <strong><img style=\"vertical-align: text-top\" src=\"http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png\" alt=\"\" /> ? About</strong> for an updated list of features and under-the-hood changes. As a reminder: We’ve published some resources on the <a href=\"http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/\">development blog</a> to help plugin and theme developers prepare.</p>\n<p><em>The new live preview<br />\nNearing perfection, and yet?<br />\nNot yet. RC3</em></p>\n\";}i:4;a:13:{s:5:\"title\";s:33:\"WordPress 3.4 Release Candidate 2\";s:4:\"link\";s:68:\"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-2/\";s:8:\"comments\";s:77:\"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-2/#comments\";s:7:\"pubdate\";s:31:\"Thu, 07 Jun 2012 02:48:58 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:12:\"Andrew Nacin\";}s:8:\"category\";s:26:\"DevelopmentReleasesTesting\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2318\";s:11:\"description\";s:331:\"The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a few dozen final changes. Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely your last chance to test your plugins and themes to find any compatibility issues before the final release. [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:1713:\"<p>The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a <a href=\"http://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=21018&amp;stop_rev=20949&amp;limit=500\">few dozen final changes</a>.</p>\n<p>Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely <strong>your last chance to test your plugins and themes to find any compatibility issues before the final release</strong>. We&#8217;ve published some resources on the <a href=\"http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/\">development blog</a> to help you prepare.</p>\n<p>If you think you’ve found a bug, you can post to the <a href=\"http://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a reproducible bug report, <a href=\"http://core.trac.wordpress.org/\">file one on WordPress Trac</a>. Known issues that crop up will be listed <a href=\"http://core.trac.wordpress.org/report/6\">here</a>, but we&#8217;re hoping for a quiet few days so we can get some great features into your hands next week!</p>\n<p>To test WordPress 3.4, try the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href=\"http://wordpress.org/wordpress-3.4-RC2.zip\">download the release candidate here</a> (zip). Be sure to visit <strong><img src=\"http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png\" alt=\"\" style=\"vertical-align:text-top\" /> &rarr; About</strong> for an updated list of features and under-the-hood changes.</p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:73:\"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-2/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:331:\"The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a few dozen final changes. Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely your last chance to test your plugins and themes to find any compatibility issues before the final release. [...]\";s:12:\"atom_content\";s:1713:\"<p>The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a <a href=\"http://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=21018&amp;stop_rev=20949&amp;limit=500\">few dozen final changes</a>.</p>\n<p>Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely <strong>your last chance to test your plugins and themes to find any compatibility issues before the final release</strong>. We&#8217;ve published some resources on the <a href=\"http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/\">development blog</a> to help you prepare.</p>\n<p>If you think you’ve found a bug, you can post to the <a href=\"http://wordpress.org/support/forum/alphabeta\">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a reproducible bug report, <a href=\"http://core.trac.wordpress.org/\">file one on WordPress Trac</a>. Known issues that crop up will be listed <a href=\"http://core.trac.wordpress.org/report/6\">here</a>, but we&#8217;re hoping for a quiet few days so we can get some great features into your hands next week!</p>\n<p>To test WordPress 3.4, try the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href=\"http://wordpress.org/wordpress-3.4-RC2.zip\">download the release candidate here</a> (zip). Be sure to visit <strong><img src=\"http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png\" alt=\"\" style=\"vertical-align:text-top\" /> &rarr; About</strong> for an updated list of features and under-the-hood changes.</p>\n\";}i:5;a:13:{s:5:\"title\";s:31:\"WordPress 3.4 Release Candidate\";s:4:\"link\";s:66:\"http://wordpress.org/news/2012/05/wordpress-3-4-release-candidate/\";s:8:\"comments\";s:75:\"http://wordpress.org/news/2012/05/wordpress-3-4-release-candidate/#comments\";s:7:\"pubdate\";s:31:\"Sun, 27 May 2012 17:18:30 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:12:\"Andrew Nacin\";}s:8:\"category\";s:26:\"DevelopmentReleasesTesting\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2303\";s:11:\"description\";s:130:\"The first release candidate (RC1) for WordPress 3.4 is now available. If you haven’t tested WordPress 3.4 yet, now is the time! \";s:7:\"content\";a:1:{s:7:\"encoded\";s:1871:\"<p>The first release candidate (RC1) for WordPress 3.4 is now available.</p>\n<p>An RC comes after the beta period and before final release. We think we&#8217;re done, but with millions of users and thousands of plugins and themes, it&#8217;s possible we&#8217;ve missed something. So if you haven’t tested WordPress 3.4 yet, now is the time! Please though, not on your live site unless you’re adventurous.</p>\n<p>With more than <a href=\"http://core.trac.wordpress.org/milestone/3.4\">500 tickets closed</a>, there are quite a few changes. <strong>Plugin and theme authors,</strong> please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.</p>\n<p>If you are testing the release candidate and think you&#8217;ve found a bug, please post to the <a href=\"http://wordpress.org/support/forum/alphabeta/\">Alpha/Beta area in the support forums</a>. If any known issues crop up, you’ll be able to <a href=\"http://core.trac.wordpress.org/report/5\">find them here</a>.</p>\n<p>To test WordPress 3.4, try the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (you&#8217;ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href=\"http://wordpress.org/wordpress-3.4-RC1.zip\">download the release candidate here (zip)</a>.</p>\n<p>If you&#8217;d like to know which levers to pull in your testing, visit the About page (<strong><img src=\"http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png\" alt=\"\" style=\"vertical-align:text-top\" /> &rarr; About</strong> in the toolbar) and check out the list of features! You&#8217;ll definitely want to try the live theme previews.</p>\n<p><strong>Bonus:</strong> Happy birthday WordPress &#8212; <a href=\"http://wordpress.org/news/2003/05/wordpress-now-available/\">nine years old</a> today.</p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:71:\"http://wordpress.org/news/2012/05/wordpress-3-4-release-candidate/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:130:\"The first release candidate (RC1) for WordPress 3.4 is now available. If you haven’t tested WordPress 3.4 yet, now is the time! \";s:12:\"atom_content\";s:1871:\"<p>The first release candidate (RC1) for WordPress 3.4 is now available.</p>\n<p>An RC comes after the beta period and before final release. We think we&#8217;re done, but with millions of users and thousands of plugins and themes, it&#8217;s possible we&#8217;ve missed something. So if you haven’t tested WordPress 3.4 yet, now is the time! Please though, not on your live site unless you’re adventurous.</p>\n<p>With more than <a href=\"http://core.trac.wordpress.org/milestone/3.4\">500 tickets closed</a>, there are quite a few changes. <strong>Plugin and theme authors,</strong> please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.</p>\n<p>If you are testing the release candidate and think you&#8217;ve found a bug, please post to the <a href=\"http://wordpress.org/support/forum/alphabeta/\">Alpha/Beta area in the support forums</a>. If any known issues crop up, you’ll be able to <a href=\"http://core.trac.wordpress.org/report/5\">find them here</a>.</p>\n<p>To test WordPress 3.4, try the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin (you&#8217;ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href=\"http://wordpress.org/wordpress-3.4-RC1.zip\">download the release candidate here (zip)</a>.</p>\n<p>If you&#8217;d like to know which levers to pull in your testing, visit the About page (<strong><img src=\"http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png\" alt=\"\" style=\"vertical-align:text-top\" /> &rarr; About</strong> in the toolbar) and check out the list of features! You&#8217;ll definitely want to try the live theme previews.</p>\n<p><strong>Bonus:</strong> Happy birthday WordPress &#8212; <a href=\"http://wordpress.org/news/2003/05/wordpress-now-available/\">nine years old</a> today.</p>\n\";}i:6;a:13:{s:5:\"title\";s:26:\"Plugin Directory Refreshed\";s:4:\"link\";s:52:\"http://wordpress.org/news/2012/05/plugins-refreshed/\";s:8:\"comments\";s:61:\"http://wordpress.org/news/2012/05/plugins-refreshed/#comments\";s:7:\"pubdate\";s:31:\"Sat, 19 May 2012 18:56:27 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Matt Mullenweg\";}s:8:\"category\";s:4:\"Meta\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2291\";s:11:\"description\";s:333:\"Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over 19,000 plugins listed and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:3324:\"<p>Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over <a href=\"http://wordpress.org/extend/plugins/\">19,000 plugins listed</a> and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. Here&#8217;s a quick before and after snapshot you can zoom in on to see a visual overview of some of the changes:</p>\n<p><a href=\"http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png\"><img src=\"http://s2.wp.com/imgpress?resize=690,350&amp;url=http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png&amp;unsharpmask=80,0.5,3\" alt=\"\" /></a></p>\n<p>Our first focus was around improving the discussion and support around plugins.</p>\n<p>You&#8217;ll now notice that threads about a plugin are pulled directly into a &#8220;support&#8221; tab on the plugin page &#8212; each plugin has its own forum. We&#8217;ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you&#8217;re using. And finally to show how active and well-supported a plugin is, you can see  &#8221;16 of 75 support threads in the last two weeks have been resolved.&#8221; Finally, if you&#8217;re logged in you get access to the new &#8220;favorites&#8221; feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!</p>\n<p>If you&#8217;re a plugin author, we&#8217;ve started with a short threshold (2 weeks) for the resolved stats so it&#8217;s easy to catch up and stay on top of it. (It&#8217;ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.</p>\n<p>We&#8217;ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:</p>\n<ul>\n<li>&#8220;Plugin headers&#8221; or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.</li>\n<li>You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn&#8217;t yours. There is no better way to follow the development of your favorite plugins. There&#8217;s nothing like the smell of fresh changesets in the morning.</li>\n<li>Behind the scenes, we&#8217;ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.</li>\n</ul>\n<p>All of this will continue to evolve as we get feedback and see usage, but we&#8217;re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ &#8212; it imparts magical coding powers.)</p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:57:\"http://wordpress.org/news/2012/05/plugins-refreshed/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:333:\"Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over 19,000 plugins listed and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. [...]\";s:12:\"atom_content\";s:3324:\"<p>Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over <a href=\"http://wordpress.org/extend/plugins/\">19,000 plugins listed</a> and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. Here&#8217;s a quick before and after snapshot you can zoom in on to see a visual overview of some of the changes:</p>\n<p><a href=\"http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png\"><img src=\"http://s2.wp.com/imgpress?resize=690,350&amp;url=http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png&amp;unsharpmask=80,0.5,3\" alt=\"\" /></a></p>\n<p>Our first focus was around improving the discussion and support around plugins.</p>\n<p>You&#8217;ll now notice that threads about a plugin are pulled directly into a &#8220;support&#8221; tab on the plugin page &#8212; each plugin has its own forum. We&#8217;ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you&#8217;re using. And finally to show how active and well-supported a plugin is, you can see  &#8221;16 of 75 support threads in the last two weeks have been resolved.&#8221; Finally, if you&#8217;re logged in you get access to the new &#8220;favorites&#8221; feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!</p>\n<p>If you&#8217;re a plugin author, we&#8217;ve started with a short threshold (2 weeks) for the resolved stats so it&#8217;s easy to catch up and stay on top of it. (It&#8217;ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.</p>\n<p>We&#8217;ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:</p>\n<ul>\n<li>&#8220;Plugin headers&#8221; or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.</li>\n<li>You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn&#8217;t yours. There is no better way to follow the development of your favorite plugins. There&#8217;s nothing like the smell of fresh changesets in the morning.</li>\n<li>Behind the scenes, we&#8217;ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.</li>\n</ul>\n<p>All of this will continue to evolve as we get feedback and see usage, but we&#8217;re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ &#8212; it imparts magical coding powers.)</p>\n\";}i:7;a:13:{s:5:\"title\";s:47:\"Calling All Contributors: Community Summit 2012\";s:4:\"link\";s:81:\"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/\";s:8:\"comments\";s:90:\"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/#comments\";s:7:\"pubdate\";s:31:\"Tue, 15 May 2012 22:36:46 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jane Wells\";}s:8:\"category\";s:15:\"CommunityEvents\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2278\";s:11:\"description\";s:334:\"Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending WordCamps and local WordPress meetups (which are awesome and you should try to attend [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:5345:\"<p>Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending <a title=\"WordCamp Central\" href=\"http://wordcamp.org\">WordCamps</a> and local <a title=\"WordPress on Meetup.com\" href=\"http://wordpress.meetup.com/\">WordPress meetups</a> (which are awesome and you should try to attend if you are able), but at the core team meetup, the focus on working together and getting things done is unique, as is the experience of every person in the room being so highly qualified. This year, instead of just planning a core team meetup, I&#8217;m aiming a little higher and shooting for a full-on contributor/community summit.</p>\n<p>Core code isn&#8217;t the only way to contribute to the WordPress project. We have an active <a title=\"Theme Review Team blog\" href=\"http://make.wordpress.org/themes/\">theme review team</a>, <a href=\"http://wordpress.org/support/\">support forum</a> volunteers, people writing <a href=\"http://codex.wordpress.org/Main_Page\">documentation</a>, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we&#8217;ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.</p>\n<p>In addition to bringing together the active contributor team reps to work together, I think it&#8217;s important to include community members who don&#8217;t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!</p>\n<p>Taking a cue from events with limited availability like <a title=\"AdaCamp\" href=\"http://dc.adacamp.org/\">AdaCamp</a> (attendance) and the <a title=\"jQuery Conference\" href=\"http://events.jquery.org/2012/sf/\">jQuery conference</a> (speaker roster), I want you to <a title=\"Nomination survey\" href=\"http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations\">nominate people and/or WordPress-based businesses to participate in the summit</a>. Yes, you can nominate yourself.* You can nominate up to 10 additional people &#8212; be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there&#8217;s a theme or hosting company (for example) that you think should be there, you don&#8217;t need to go looking for employee names. This nomination process will hopefully ensure that we don&#8217;t overlook someone who is making a difference in our community when it comes time to issue invitations.</p>\n<p>Nominations will be open for a week, after which <a href=\"http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations\">the survey</a> will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at <a href=\"http://wordpress.tv\">WordPress.tv</a>. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you&#8217;re thinking to yourself that maybe now&#8217;s the perfect time to start <a href=\"http://codex.wordpress.org/Contributing_to_WordPress\">contributing time to the WordPress project</a>, good thinking! In the meantime, if you want to weigh in, <a href=\"http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations\">fill in the community summit nomination form</a>. Thanks, and wish us luck!</p>\n<p><em>* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.</em></p>\n<p><em>** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.</em></p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:86:\"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:334:\"Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending WordCamps and local WordPress meetups (which are awesome and you should try to attend [...]\";s:12:\"atom_content\";s:5345:\"<p>Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending <a title=\"WordCamp Central\" href=\"http://wordcamp.org\">WordCamps</a> and local <a title=\"WordPress on Meetup.com\" href=\"http://wordpress.meetup.com/\">WordPress meetups</a> (which are awesome and you should try to attend if you are able), but at the core team meetup, the focus on working together and getting things done is unique, as is the experience of every person in the room being so highly qualified. This year, instead of just planning a core team meetup, I&#8217;m aiming a little higher and shooting for a full-on contributor/community summit.</p>\n<p>Core code isn&#8217;t the only way to contribute to the WordPress project. We have an active <a title=\"Theme Review Team blog\" href=\"http://make.wordpress.org/themes/\">theme review team</a>, <a href=\"http://wordpress.org/support/\">support forum</a> volunteers, people writing <a href=\"http://codex.wordpress.org/Main_Page\">documentation</a>, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we&#8217;ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.</p>\n<p>In addition to bringing together the active contributor team reps to work together, I think it&#8217;s important to include community members who don&#8217;t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!</p>\n<p>Taking a cue from events with limited availability like <a title=\"AdaCamp\" href=\"http://dc.adacamp.org/\">AdaCamp</a> (attendance) and the <a title=\"jQuery Conference\" href=\"http://events.jquery.org/2012/sf/\">jQuery conference</a> (speaker roster), I want you to <a title=\"Nomination survey\" href=\"http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations\">nominate people and/or WordPress-based businesses to participate in the summit</a>. Yes, you can nominate yourself.* You can nominate up to 10 additional people &#8212; be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there&#8217;s a theme or hosting company (for example) that you think should be there, you don&#8217;t need to go looking for employee names. This nomination process will hopefully ensure that we don&#8217;t overlook someone who is making a difference in our community when it comes time to issue invitations.</p>\n<p>Nominations will be open for a week, after which <a href=\"http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations\">the survey</a> will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at <a href=\"http://wordpress.tv\">WordPress.tv</a>. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you&#8217;re thinking to yourself that maybe now&#8217;s the perfect time to start <a href=\"http://codex.wordpress.org/Contributing_to_WordPress\">contributing time to the WordPress project</a>, good thinking! In the meantime, if you want to weigh in, <a href=\"http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations\">fill in the community summit nomination form</a>. Thanks, and wish us luck!</p>\n<p><em>* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.</em></p>\n<p><em>** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.</em></p>\n\";}i:8;a:13:{s:5:\"title\";s:20:\"WordPress 3.4 Beta 4\";s:4:\"link\";s:55:\"http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/\";s:8:\"comments\";s:64:\"http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/#comments\";s:7:\"pubdate\";s:31:\"Thu, 03 May 2012 02:52:28 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Ryan Boren\";}s:8:\"category\";s:8:\"Releases\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2273\";s:11:\"description\";s:123:\"Less bugs, more polish, the same beta disclaimers. Download, test, report bugs. Thanks much. /ryan #thewholebrevitything\";s:7:\"content\";a:1:{s:7:\"encoded\";s:190:\"<p>Less bugs, more polish, the same beta disclaimers. <a href=\"http://wordpress.org/wordpress-3.4-beta4.zip\">Download</a>, test, report bugs. Thanks much. /ryan #thewholebrevitything</p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:60:\"http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:123:\"Less bugs, more polish, the same beta disclaimers. Download, test, report bugs. Thanks much. /ryan #thewholebrevitything\";s:12:\"atom_content\";s:190:\"<p>Less bugs, more polish, the same beta disclaimers. <a href=\"http://wordpress.org/wordpress-3.4-beta4.zip\">Download</a>, test, report bugs. Thanks much. /ryan #thewholebrevitything</p>\n\";}i:9;a:13:{s:5:\"title\";s:42:\"WordPress 3.3.2 (and WordPress 3.4 Beta 3)\";s:4:\"link\";s:50:\"http://wordpress.org/news/2012/04/wordpress-3-3-2/\";s:8:\"comments\";s:59:\"http://wordpress.org/news/2012/04/wordpress-3-3-2/#comments\";s:7:\"pubdate\";s:31:\"Fri, 20 Apr 2012 15:10:37 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:12:\"Andrew Nacin\";}s:8:\"category\";s:27:\"DevelopmentReleasesSecurity\";s:4:\"guid\";s:33:\"http://wordpress.org/news/?p=2262\";s:11:\"description\";s:384:\"WordPress 3.3.2 is available now and is a security update for all previous versions. Three external libraries included in WordPress received security updates: Plupload (version 1.5.4), which WordPress uses for uploading media. SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins. SWFObject, which WordPress previously used to embed [...]\";s:7:\"content\";a:1:{s:7:\"encoded\";s:3345:\"<p><a href=\"http://wordpress.org/download/\">WordPress 3.3.2</a> is available now and is a security update for all previous versions.</p>\n<p>Three external libraries included in WordPress received security updates:</p>\n<ul>\n<li>Plupload (version 1.5.4), which WordPress uses for uploading media.</li>\n<li>SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins.</li>\n<li>SWFObject, which WordPress previously used to embed Flash content, and may still be in use by plugins and themes.</li>\n</ul>\n<p>Thanks to <a href=\"https://nealpoole.com/blog/\">Neal Poole</a> and <a href=\"http://greywhind.wordpress.com/\">Nathan Partlan</a> for <a href=\"http://codex.wordpress.org/FAQ_Security\">responsibly disclosing</a> the bugs in Plupload and SWFUpload, and <a href=\"http://mars.iti.pk.edu.pl/~grucha/\">Szymon Gruszecki</a> for a separate bug in SWFUpload.</p>\n<p>WordPress 3.3.2 also addresses:</p>\n<ul>\n<li>Limited privilege escalation where a site administrator could deactivate network-wide plugins when running a WordPress network under particular circumstances, disclosed by <a href=\"http://joncave.co.uk/\">Jon Cave</a> of our WordPress core security team, and <a href=\"http://sixohthree.com/\">Adam Backstrom</a>.</li>\n<li>Cross-site scripting vulnerability when making URLs clickable, by Jon Cave.</li>\n<li>Cross-site scripting vulnerabilities in redirects after posting comments in older browsers, and when filtering URLs. Thanks to <a href=\"http://www.sneaked.net/\">Mauro Gentile</a> for responsibly disclosing these issues to the security team.</li>\n</ul>\n<p>These issues were fixed by the WordPress core security team. Five other bugs were also fixed in version 3.3.2. Consult the <a href=\"http://core.trac.wordpress.org/log/branches/3.3?rev=20552&amp;stop_rev=20087\">change log</a> for more details.</p>\n<p><a href=\"http://wordpress.org/download/\">Download WordPress 3.3.2</a> or update now from the Dashboard ? Updates menu in your site&#8217;s admin area.</p>\n<hr />\n<h3>WordPress 3.4 Beta 3 also available</h3>\n<p>Our development of WordPress 3.4 development continues. Today we are proud to release Beta 3 for testing. <a href=\"http://core.trac.wordpress.org/log/trunk?rev=20552&amp;stop_rev=20450\">Nearly 90 changes</a> have been made since Beta 2, released 9 days ago. (We are aiming for a beta every week.)</p>\n<p>This is still beta software, so <strong>we don&#8217;t recommend that you use it on production sites</strong>. But if you&#8217;re a plugin developer, a theme developer, or a site administrator, <strong>you should be running this on your test environments</strong> and <a href=\"http://codex.wordpress.org/Reporting_Bugs\">reporting any bugs</a> you find. (See the <a href=\"http://core.trac.wordpress.org/report/5\">known issues here</a>.) If you&#8217;re a WordPress user who wants to open your presents early, take advantage of WordPress&#8217;s famous 5-minute install and spin up a secondary test site. <a href=\"http://wordpress.org/support/forum/alphabeta\">Let us know what you think</a>!</p>\n<p>Version 3.4 Beta 3 includes all of the fixes included in version 3.3.2. <a href=\"http://wordpress.org/wordpress-3.4-beta3.zip\">Download WordPress 3.4 Beta 3</a> or use the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin.</p>\n\";}s:3:\"wfw\";a:1:{s:10:\"commentrss\";s:55:\"http://wordpress.org/news/2012/04/wordpress-3-3-2/feed/\";}s:5:\"slash\";a:1:{s:8:\"comments\";s:1:\"0\";}s:7:\"summary\";s:384:\"WordPress 3.3.2 is available now and is a security update for all previous versions. Three external libraries included in WordPress received security updates: Plupload (version 1.5.4), which WordPress uses for uploading media. SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins. SWFObject, which WordPress previously used to embed [...]\";s:12:\"atom_content\";s:3345:\"<p><a href=\"http://wordpress.org/download/\">WordPress 3.3.2</a> is available now and is a security update for all previous versions.</p>\n<p>Three external libraries included in WordPress received security updates:</p>\n<ul>\n<li>Plupload (version 1.5.4), which WordPress uses for uploading media.</li>\n<li>SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins.</li>\n<li>SWFObject, which WordPress previously used to embed Flash content, and may still be in use by plugins and themes.</li>\n</ul>\n<p>Thanks to <a href=\"https://nealpoole.com/blog/\">Neal Poole</a> and <a href=\"http://greywhind.wordpress.com/\">Nathan Partlan</a> for <a href=\"http://codex.wordpress.org/FAQ_Security\">responsibly disclosing</a> the bugs in Plupload and SWFUpload, and <a href=\"http://mars.iti.pk.edu.pl/~grucha/\">Szymon Gruszecki</a> for a separate bug in SWFUpload.</p>\n<p>WordPress 3.3.2 also addresses:</p>\n<ul>\n<li>Limited privilege escalation where a site administrator could deactivate network-wide plugins when running a WordPress network under particular circumstances, disclosed by <a href=\"http://joncave.co.uk/\">Jon Cave</a> of our WordPress core security team, and <a href=\"http://sixohthree.com/\">Adam Backstrom</a>.</li>\n<li>Cross-site scripting vulnerability when making URLs clickable, by Jon Cave.</li>\n<li>Cross-site scripting vulnerabilities in redirects after posting comments in older browsers, and when filtering URLs. Thanks to <a href=\"http://www.sneaked.net/\">Mauro Gentile</a> for responsibly disclosing these issues to the security team.</li>\n</ul>\n<p>These issues were fixed by the WordPress core security team. Five other bugs were also fixed in version 3.3.2. Consult the <a href=\"http://core.trac.wordpress.org/log/branches/3.3?rev=20552&amp;stop_rev=20087\">change log</a> for more details.</p>\n<p><a href=\"http://wordpress.org/download/\">Download WordPress 3.3.2</a> or update now from the Dashboard ? Updates menu in your site&#8217;s admin area.</p>\n<hr />\n<h3>WordPress 3.4 Beta 3 also available</h3>\n<p>Our development of WordPress 3.4 development continues. Today we are proud to release Beta 3 for testing. <a href=\"http://core.trac.wordpress.org/log/trunk?rev=20552&amp;stop_rev=20450\">Nearly 90 changes</a> have been made since Beta 2, released 9 days ago. (We are aiming for a beta every week.)</p>\n<p>This is still beta software, so <strong>we don&#8217;t recommend that you use it on production sites</strong>. But if you&#8217;re a plugin developer, a theme developer, or a site administrator, <strong>you should be running this on your test environments</strong> and <a href=\"http://codex.wordpress.org/Reporting_Bugs\">reporting any bugs</a> you find. (See the <a href=\"http://core.trac.wordpress.org/report/5\">known issues here</a>.) If you&#8217;re a WordPress user who wants to open your presents early, take advantage of WordPress&#8217;s famous 5-minute install and spin up a secondary test site. <a href=\"http://wordpress.org/support/forum/alphabeta\">Let us know what you think</a>!</p>\n<p>Version 3.4 Beta 3 includes all of the fixes included in version 3.3.2. <a href=\"http://wordpress.org/wordpress-3.4-beta3.zip\">Download WordPress 3.4 Beta 3</a> or use the <a href=\"http://wordpress.org/extend/plugins/wordpress-beta-tester/\">WordPress Beta Tester</a> plugin.</p>\n\";}}s:7:\"channel\";a:8:{s:5:\"title\";s:14:\"WordPress News\";s:4:\"link\";s:25:\"http://wordpress.org/news\";s:11:\"description\";s:14:\"WordPress News\";s:13:\"lastbuilddate\";s:31:\"Fri, 13 Jul 2012 08:18:15 +0000\";s:8:\"language\";s:5:\"en-US\";s:2:\"sy\";a:2:{s:12:\"updateperiod\";s:6:\"hourly\";s:15:\"updatefrequency\";s:1:\"1\";}s:9:\"generator\";s:39:\"http://wordpress.org/?v=3.5-alpha-21360\";s:7:\"tagline\";s:14:\"WordPress News\";}s:9:\"textinput\";a:0:{}s:5:\"image\";a:0:{}s:9:\"feed_type\";s:3:\"RSS\";s:12:\"feed_version\";s:3:\"2.0\";s:5:\"stack\";a:0:{}s:9:\"inchannel\";b:0;s:6:\"initem\";b:0;s:9:\"incontent\";b:0;s:11:\"intextinput\";b:0;s:7:\"inimage\";b:0;s:13:\"current_field\";s:0:\"\";s:17:\"current_namespace\";b:0;s:19:\"_CONTENT_CONSTRUCTS\";a:6:{i:0;s:7:\"content\";i:1;s:7:\"summary\";i:2;s:4:\"info\";i:3;s:5:\"title\";i:4;s:7:\"tagline\";i:5;s:9:\"copyright\";}s:13:\"last_modified\";s:31:\"Fri, 13 Jul 2012 08:18:15 GMT\r\n\";}', 'no');
INSERT INTO `wp_options` (`option_id`, `blog_id`, `option_name`, `option_value`, `autoload`) VALUES
(83, 0, 'rss_0ff4b43bd116a9d8720d689c80e7dfd4_ts', '1343676616', 'no');
INSERT INTO `wp_options` (`option_id`, `blog_id`, `option_name`, `option_value`, `autoload`) VALUES
(84, 0, 'rss_867bd5c64f85878d03a060509cd2f92c', 'O:9:\"MagpieRSS\":18:{s:6:\"parser\";i:0;s:12:\"current_item\";a:0:{}s:5:\"items\";a:50:{i:0;a:7:{s:5:\"title\";s:98:\"WordPress.tv Blog: How to create child themes and multi-lingual blogs – Featured on WordPress.tv\";s:4:\"guid\";s:31:\"http://blog.wordpress.tv/?p=414\";s:4:\"link\";s:112:\"http://blog.wordpress.tv/2016/06/08/how-to-create-child-themes-and-multi-lingual-blogs-featured-on-wordpress-tv/\";s:11:\"description\";s:2153:\"<h2 class=\"video-title\">Corinne Welsh: My First Child Theme</h2>\n<p>Corrine Welsh explains how to get started with themes in WordPress, starting with a case study: why, why then, and why not sooner. From there she looks at the structure of a theme and walks through the steps of building a child theme. You may leave inspired to roll up your sleeves and get your hands dirty in theming after this great talk.</p>\n<div id=\"v-6oXMxwGi-1\" class=\"video-player\">\n</div>\n<p>From <a href=\"http://wordpress.tv/event/wordcamp-london-2016/\">WordCamp London 2016</a></p>\n<h2 class=\"video-title\">Maciej Pilarski: How To Make Your WordPress Website Multilingual</h2>\n<p>In this presentation Maciej Pilarski goes into detail on how  to easily and quickly create a traditional multilingual website or eCommerce store.  He also compares most popular multilingual plugins and also shows how this can be done without using any plugins, as well as discusses the benefits to your business of going global and how this can be done in minutes.</p>\n<div id=\"v-K21BXW6Y-1\" class=\"video-player\">\n</div>\n<p>From <a href=\"http://wordpress.tv/event/wordcamp-london-2016/\">WordCamp London 2016</a></p><br />  <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/wptvblog.wordpress.com/414/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/wptvblog.wordpress.com/414/\" /></a> <img alt=\"\" border=\"0\" src=\"http://pixel.wp.com/b.gif?host=blog.wordpress.tv&blog=5310177&post=414&subd=wptvblog&ref=&feed=1\" width=\"1\" height=\"1\" /><div><a href=\"http://blog.wordpress.tv/2016/06/08/how-to-create-child-themes-and-multi-lingual-blogs-featured-on-wordpress-tv/\"><img alt=\"Corinne Welsh: My First Child Theme\" src=\"http://videos.videopress.com/6oXMxwGi/video-b0595a6e44_std.original.jpg\" width=\"160\" height=\"120\" /></a></div><div><a href=\"http://blog.wordpress.tv/2016/06/08/how-to-create-child-themes-and-multi-lingual-blogs-featured-on-wordpress-tv/\"><img alt=\"Maciej Pilarski: How to Make your WordPress Website Multilingual\" src=\"http://videos.videopress.com/K21BXW6Y/video-c5c8665f72_scruberthumbnail_0.jpg\" width=\"160\" height=\"120\" /></a></div>\";s:7:\"pubdate\";s:31:\"Wed, 08 Jun 2016 01:46:32 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:11:\"Jerry Bates\";}s:7:\"summary\";s:2153:\"<h2 class=\"video-title\">Corinne Welsh: My First Child Theme</h2>\n<p>Corrine Welsh explains how to get started with themes in WordPress, starting with a case study: why, why then, and why not sooner. From there she looks at the structure of a theme and walks through the steps of building a child theme. You may leave inspired to roll up your sleeves and get your hands dirty in theming after this great talk.</p>\n<div id=\"v-6oXMxwGi-1\" class=\"video-player\">\n</div>\n<p>From <a href=\"http://wordpress.tv/event/wordcamp-london-2016/\">WordCamp London 2016</a></p>\n<h2 class=\"video-title\">Maciej Pilarski: How To Make Your WordPress Website Multilingual</h2>\n<p>In this presentation Maciej Pilarski goes into detail on how  to easily and quickly create a traditional multilingual website or eCommerce store.  He also compares most popular multilingual plugins and also shows how this can be done without using any plugins, as well as discusses the benefits to your business of going global and how this can be done in minutes.</p>\n<div id=\"v-K21BXW6Y-1\" class=\"video-player\">\n</div>\n<p>From <a href=\"http://wordpress.tv/event/wordcamp-london-2016/\">WordCamp London 2016</a></p><br />  <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/wptvblog.wordpress.com/414/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/wptvblog.wordpress.com/414/\" /></a> <img alt=\"\" border=\"0\" src=\"http://pixel.wp.com/b.gif?host=blog.wordpress.tv&blog=5310177&post=414&subd=wptvblog&ref=&feed=1\" width=\"1\" height=\"1\" /><div><a href=\"http://blog.wordpress.tv/2016/06/08/how-to-create-child-themes-and-multi-lingual-blogs-featured-on-wordpress-tv/\"><img alt=\"Corinne Welsh: My First Child Theme\" src=\"http://videos.videopress.com/6oXMxwGi/video-b0595a6e44_std.original.jpg\" width=\"160\" height=\"120\" /></a></div><div><a href=\"http://blog.wordpress.tv/2016/06/08/how-to-create-child-themes-and-multi-lingual-blogs-featured-on-wordpress-tv/\"><img alt=\"Maciej Pilarski: How to Make your WordPress Website Multilingual\" src=\"http://videos.videopress.com/K21BXW6Y/video-c5c8665f72_scruberthumbnail_0.jpg\" width=\"160\" height=\"120\" /></a></div>\";}i:1;a:7:{s:5:\"title\";s:50:\"WP Mobile Apps: WordPress for Android: Version 5.4\";s:4:\"guid\";s:33:\"http://apps.wordpress.com/?p=3403\";s:4:\"link\";s:72:\"https://apps.wordpress.com/2016/06/01/wordpress-for-android-version-5-4/\";s:11:\"description\";s:3183:\"<p>Hello WordPress users! <a href=\"https://play.google.com/store/apps/details?id=org.wordpress.android\" target=\"_blank\">Version 5.4 of the WordPress for Android app</a> is now available in the Google Play Store.</p>\n<h1>Gravatar update</h1>\n<p>Did you just take a great selfie? You can update your Gravatar from the app on the <em>Me</em> screen. Tap your profile picture, and follow the prompts to take a new photo or pick an image from your device&#8217;s photo library.</p>\n<div id=\"v-a5lLmHSc-1\" class=\"video-player\">\n</div>\n<h1>Smart Lock for Passwords integration</h1>\n<p>Signing in with a WordPress.com account is easier than ever with Smart Lock for Passwords, the Google password manager. If you signed in to your account on your computer using Google&#8217;s Chrome browser, the username and password fields will be automatically pre-filled when you open the app &#8212; you can even manage several identities.</p>\n<p><img class=\"alignnone wp-image-3404 size-large\" src=\"https://apps.files.wordpress.com/2016/05/screenshot-2016-05-04_12-08-06-614.png?w=614&h=1024\" alt=\"screenshot-2016-05-04_12.08.06.614\" width=\"614\" height=\"1024\" /></p>\n<h1>Other Changes</h1>\n<p>Version 5.4 also comes with a few other fixes:</p>\n<ul>\n<li>Fixed comment previews with images in the Comment List screen.</li>\n<li>Fixed an issue with tag display in the Reader.</li>\n<li>Fixed a problem sometimes removed the <em>Themes</em> option after sign-in.</li>\n</ul>\n<p>You can track our development progress for the next release by visiting <a href=\"https://github.com/wordpress-mobile/WordPress-Android/milestones/5.5\">our 5.5 milestone on GitHub</a>.</p>\n<h1>Beta</h1>\n<p>Do you like keeping up with what’s new in the app? Do you enjoy testing new stuff before anyone else? Our testers have access to beta versions with updates shipped directly through Google Play. The beta versions may have new features, new fixes — and possibly new bugs! Testers make it possible for us to improve the overall app experience, and offer us invaluable development feedback.</p>\n<p>Want to become a tester? <a href=\"https://play.google.com/apps/testing/org.wordpress.android\">Opt-in</a>!</p>\n<h1>Thank you</h1>\n<p>Thanks to our GitHub contributors: <a href=\"https://github.com/aerych\">@aerych</a>, <a href=\"https://github.com/aforcier\">@aforcier</a>, <a href=\"https://github.com/daniloercoli\">@daniloercoli</a>, <a href=\"https://github.com/hypest\">@hypest</a>, <a href=\"https://github.com/kwonye\">@kwonye</a>, <a href=\"https://github.com/maxme\">@maxme</a>, <a href=\"https://github.com/mzorz\">@mzorz</a>, <a href=\"https://github.com/nbradbury\">@nbradbury</a>, <a href=\"https://github.com/oguzkocer\">@oguzkocer</a>, <a href=\"https://github.com/roundhill\">@roundhill</a>, and <a href=\"https://github.com/tonyr59h\">@tonyr59h</a>.</p><img alt=\"\" border=\"0\" src=\"https://pixel.wp.com/b.gif?host=apps.wordpress.com&blog=108068616&post=3403&subd=apps&ref=&feed=1\" width=\"1\" height=\"1\" /><div><a href=\"https://apps.wordpress.com/2016/06/01/wordpress-for-android-version-5-4/\"><img alt=\"gravatar\" src=\"https://videos.files.wordpress.com/a5lLmHSc/gravatar_std.original.jpg\" width=\"160\" height=\"120\" /></a></div>\";s:7:\"pubdate\";s:31:\"Wed, 01 Jun 2016 11:53:19 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:6:\"Maxime\";}s:7:\"summary\";s:3183:\"<p>Hello WordPress users! <a href=\"https://play.google.com/store/apps/details?id=org.wordpress.android\" target=\"_blank\">Version 5.4 of the WordPress for Android app</a> is now available in the Google Play Store.</p>\n<h1>Gravatar update</h1>\n<p>Did you just take a great selfie? You can update your Gravatar from the app on the <em>Me</em> screen. Tap your profile picture, and follow the prompts to take a new photo or pick an image from your device&#8217;s photo library.</p>\n<div id=\"v-a5lLmHSc-1\" class=\"video-player\">\n</div>\n<h1>Smart Lock for Passwords integration</h1>\n<p>Signing in with a WordPress.com account is easier than ever with Smart Lock for Passwords, the Google password manager. If you signed in to your account on your computer using Google&#8217;s Chrome browser, the username and password fields will be automatically pre-filled when you open the app &#8212; you can even manage several identities.</p>\n<p><img class=\"alignnone wp-image-3404 size-large\" src=\"https://apps.files.wordpress.com/2016/05/screenshot-2016-05-04_12-08-06-614.png?w=614&h=1024\" alt=\"screenshot-2016-05-04_12.08.06.614\" width=\"614\" height=\"1024\" /></p>\n<h1>Other Changes</h1>\n<p>Version 5.4 also comes with a few other fixes:</p>\n<ul>\n<li>Fixed comment previews with images in the Comment List screen.</li>\n<li>Fixed an issue with tag display in the Reader.</li>\n<li>Fixed a problem sometimes removed the <em>Themes</em> option after sign-in.</li>\n</ul>\n<p>You can track our development progress for the next release by visiting <a href=\"https://github.com/wordpress-mobile/WordPress-Android/milestones/5.5\">our 5.5 milestone on GitHub</a>.</p>\n<h1>Beta</h1>\n<p>Do you like keeping up with what’s new in the app? Do you enjoy testing new stuff before anyone else? Our testers have access to beta versions with updates shipped directly through Google Play. The beta versions may have new features, new fixes — and possibly new bugs! Testers make it possible for us to improve the overall app experience, and offer us invaluable development feedback.</p>\n<p>Want to become a tester? <a href=\"https://play.google.com/apps/testing/org.wordpress.android\">Opt-in</a>!</p>\n<h1>Thank you</h1>\n<p>Thanks to our GitHub contributors: <a href=\"https://github.com/aerych\">@aerych</a>, <a href=\"https://github.com/aforcier\">@aforcier</a>, <a href=\"https://github.com/daniloercoli\">@daniloercoli</a>, <a href=\"https://github.com/hypest\">@hypest</a>, <a href=\"https://github.com/kwonye\">@kwonye</a>, <a href=\"https://github.com/maxme\">@maxme</a>, <a href=\"https://github.com/mzorz\">@mzorz</a>, <a href=\"https://github.com/nbradbury\">@nbradbury</a>, <a href=\"https://github.com/oguzkocer\">@oguzkocer</a>, <a href=\"https://github.com/roundhill\">@roundhill</a>, and <a href=\"https://github.com/tonyr59h\">@tonyr59h</a>.</p><img alt=\"\" border=\"0\" src=\"https://pixel.wp.com/b.gif?host=apps.wordpress.com&blog=108068616&post=3403&subd=apps&ref=&feed=1\" width=\"1\" height=\"1\" /><div><a href=\"https://apps.wordpress.com/2016/06/01/wordpress-for-android-version-5-4/\"><img alt=\"gravatar\" src=\"https://videos.files.wordpress.com/a5lLmHSc/gravatar_std.original.jpg\" width=\"160\" height=\"120\" /></a></div>\";}i:2;a:7:{s:5:\"title\";s:83:\"WPTavern: WordCamp Incubator Program to Launch in Indonesia, Zimbabwe, and Colombia\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=55034\";s:4:\"link\";s:91:\"http://wptavern.com/wordcamp-incubator-program-to-launch-in-indonesia-zimbabwe-and-columbia\";s:11:\"description\";s:2932:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/02/flags.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/02/flags.jpg?resize=1020%2C500\" alt=\"flags\" class=\"aligncenter size-full wp-image-16697\" /></a></p>\n<p>After receiving <a href=\"http://wptavern.com/wordcamp-incubator-program-receives-182-applications-narrows-candidates-to-16-communities\" target=\"_blank\">182 applications from cities all over the world</a>, the WordPress Community Team has selected three locations for the WordCamp Incubator program:</p>\n<ul>\n<li>Denpasar, Indonesia</li>\n<li>Harare, Zimbabwe</li>\n<li>Medellín, Colombia</li>\n</ul>\n<p>Representatives from the thirteen other short-listed locations are encouraged to organize a local WordPress meetup and will have the help of Community Team mentors as needed.</p>\n<p>Thanks to the addition of a new volunteer deputy from the Community Team, the program will move forward with three locations, instead of having to scale back to two, as previously anticipated. Each event has been assigned a deputy who will meet bi-weekly with the local team to mentor the new WordCamp organizers.</p>\n<p>Andrea Middleton outlined in the <a href=\"https://make.wordpress.org/community/2016/05/25/wordcamp-incubator-locations-announcement/\" target=\"_blank\">announcement</a> how the team plans to proceed with getting these events off the ground.</p>\n<p>&#8220;Denpasar, Harare, and Medellín will work with their respective deputies to start a monthly WordPress meetup group or add their existing meetup group to the chapter account program,&#8221; Middleton said. &#8220;Once the local WordPress user group is meeting regularly, each team will work on finding a venue, setting a date, recruiting speakers, and spreading the word about the upcoming WordCamp.&#8221;</p>\n<p>In order to take the pressure off the new organizers, the Community team will assist them in scheduling and finding speakers. The events will be 100% funded by the global sponsorship grant so organizers can focus on community building without the pressure of fundraising. Middleton said they are aiming for no more than three non-local speakers at each event, which she anticipates will happen in the last quarter of 2016.</p>\n<p>The challenge with the Incubator program is to ensure these events are a launching point and not just a flash in the pan. Middleton and the community team deputies are working to establish these emerging communities so that they continue to grow organically after the events conclude.</p>\n<p>&#8220;The goal for these events is to organize an easily reproducible, one-day, one-track event with about 50-75 attendees,&#8221; Middleton said. &#8220;Hopefully by the end of the organizing/incubating experience, members of the local community will feel confident that they can organize an annual WordCamp independently in the years to come.&#8221;</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Tue, 31 May 2016 05:12:14 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2932:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/02/flags.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/02/flags.jpg?resize=1020%2C500\" alt=\"flags\" class=\"aligncenter size-full wp-image-16697\" /></a></p>\n<p>After receiving <a href=\"http://wptavern.com/wordcamp-incubator-program-receives-182-applications-narrows-candidates-to-16-communities\" target=\"_blank\">182 applications from cities all over the world</a>, the WordPress Community Team has selected three locations for the WordCamp Incubator program:</p>\n<ul>\n<li>Denpasar, Indonesia</li>\n<li>Harare, Zimbabwe</li>\n<li>Medellín, Colombia</li>\n</ul>\n<p>Representatives from the thirteen other short-listed locations are encouraged to organize a local WordPress meetup and will have the help of Community Team mentors as needed.</p>\n<p>Thanks to the addition of a new volunteer deputy from the Community Team, the program will move forward with three locations, instead of having to scale back to two, as previously anticipated. Each event has been assigned a deputy who will meet bi-weekly with the local team to mentor the new WordCamp organizers.</p>\n<p>Andrea Middleton outlined in the <a href=\"https://make.wordpress.org/community/2016/05/25/wordcamp-incubator-locations-announcement/\" target=\"_blank\">announcement</a> how the team plans to proceed with getting these events off the ground.</p>\n<p>&#8220;Denpasar, Harare, and Medellín will work with their respective deputies to start a monthly WordPress meetup group or add their existing meetup group to the chapter account program,&#8221; Middleton said. &#8220;Once the local WordPress user group is meeting regularly, each team will work on finding a venue, setting a date, recruiting speakers, and spreading the word about the upcoming WordCamp.&#8221;</p>\n<p>In order to take the pressure off the new organizers, the Community team will assist them in scheduling and finding speakers. The events will be 100% funded by the global sponsorship grant so organizers can focus on community building without the pressure of fundraising. Middleton said they are aiming for no more than three non-local speakers at each event, which she anticipates will happen in the last quarter of 2016.</p>\n<p>The challenge with the Incubator program is to ensure these events are a launching point and not just a flash in the pan. Middleton and the community team deputies are working to establish these emerging communities so that they continue to grow organically after the events conclude.</p>\n<p>&#8220;The goal for these events is to organize an easily reproducible, one-day, one-track event with about 50-75 attendees,&#8221; Middleton said. &#8220;Hopefully by the end of the organizing/incubating experience, members of the local community will feel confident that they can organize an annual WordCamp independently in the years to come.&#8221;</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:3;a:7:{s:5:\"title\";s:31:\"Donncha: WordPress is thirteen!\";s:4:\"guid\";s:24:\"http://z9.io/?p=89499890\";s:4:\"link\";s:46:\"http://z9.io/2016/05/27/wordpress-is-thirteen/\";s:11:\"description\";s:1231:\"<p>You could have knocked me over with a feather today when I read <a href=\"https://ma.tt/2016/05/wordpress-is-a-teenager/\">Matt&#8217;s post</a> announcing that WordPress was celebrating a birthday!</p>\n<p>It didn&#8217;t seem so long ago that we were working on b2++, hacking the multiuser bits in and doing all sorts of crazy things with it.</p>\n<p>Now I&#8217;m &#8220;typing&#8221; this on a mobile phone by swiping my finger across a virtual keyboard. Back then the closest to this that I could imagine would be some sort of SMS integration!</p>\n<p>WordPress today is unrecognisable from what it was back then, especially if you use the slick Calypso interface.</p>\n<p>I&#8217;m looking forward to seeing what the next few years bring.</p>\n\n<p><strong>Related Posts</strong><ul><li> <a href=\"http://z9.io/2013/08/02/like-a-dog-and-his-ball/\" rel=\"bookmark\" title=\"Permanent Link: Like a dog and his ball\">Like a dog and his ball</a></li><li> <a href=\"http://z9.io/2009/01/28/wordpress-mu-27/\" rel=\"bookmark\" title=\"Permanent Link: WordPress MU 2.7\">WordPress MU 2.7</a></li><li> <a href=\"http://z9.io/2008/09/02/wordpress-mu-261/\" rel=\"bookmark\" title=\"Permanent Link: WordPress MU 2.6.1\">WordPress MU 2.6.1</a></li></ul></p>\";s:7:\"pubdate\";s:31:\"Fri, 27 May 2016 22:57:38 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:7:\"Donncha\";}s:7:\"summary\";s:1231:\"<p>You could have knocked me over with a feather today when I read <a href=\"https://ma.tt/2016/05/wordpress-is-a-teenager/\">Matt&#8217;s post</a> announcing that WordPress was celebrating a birthday!</p>\n<p>It didn&#8217;t seem so long ago that we were working on b2++, hacking the multiuser bits in and doing all sorts of crazy things with it.</p>\n<p>Now I&#8217;m &#8220;typing&#8221; this on a mobile phone by swiping my finger across a virtual keyboard. Back then the closest to this that I could imagine would be some sort of SMS integration!</p>\n<p>WordPress today is unrecognisable from what it was back then, especially if you use the slick Calypso interface.</p>\n<p>I&#8217;m looking forward to seeing what the next few years bring.</p>\n\n<p><strong>Related Posts</strong><ul><li> <a href=\"http://z9.io/2013/08/02/like-a-dog-and-his-ball/\" rel=\"bookmark\" title=\"Permanent Link: Like a dog and his ball\">Like a dog and his ball</a></li><li> <a href=\"http://z9.io/2009/01/28/wordpress-mu-27/\" rel=\"bookmark\" title=\"Permanent Link: WordPress MU 2.7\">WordPress MU 2.7</a></li><li> <a href=\"http://z9.io/2008/09/02/wordpress-mu-261/\" rel=\"bookmark\" title=\"Permanent Link: WordPress MU 2.6.1\">WordPress MU 2.6.1</a></li></ul></p>\";}i:4;a:7:{s:5:\"title\";s:44:\"Post Status: WordPress.org — Draft podcast\";s:4:\"guid\";s:31:\"https://poststatus.com/?p=24730\";s:4:\"link\";s:51:\"https://poststatus.com/wordpress-org-draft-podcast/\";s:11:\"description\";s:3592:\"<p>Welcome to the Post Status <a href=\"https://poststatus.com/category/draft\">Draft podcast</a>, which you can find <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">on iTunes</a>, <a href=\"https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast\">Google Play</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, and <a href=\"http://simplecast.fm/podcasts/1061/rss\">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle &#8212; the CTO of Human Made &#8212; and Brian Krogsgard.</p>\n<p><span>In this episode, Joe and Brian discuss the structure and function of the WordPress.org website, which is the hub of the WordPress project. From the actual software distribution, to discussions about the project, to support, and buying swag: it all happens from WordPress.org. We break down what’s what and what we think you should know.</span></p>\n<p><!--[if lt IE 9]><script>document.createElement(\'audio\');</script><![endif]-->\n<a href=\"https://audio.simplecast.com/38479.mp3\">https://audio.simplecast.com/38479.mp3</a><br />\n<a href=\"http://audio.simplecast.com/38479.mp3\">Direct Download</a></p>\n<h3>Notes</h3>\n<p>Who owns WordPress.org?<br />\nWho works on WordPress.org<br />\nHow WordPress.org distributes software updates</p>\n<h3>Different Sections of WordPress.org Navigation</h3>\n<ul>\n<li>Showcase</li>\n<li>WordPress theme directory &#8212; and reviews &#8212; and commercial themes</li>\n<li>WordPress plugin directory &#8212; and reviews</li>\n<li>Mobile &#8212; Redirects to .com</li>\n<li>Support Forums / Codex &#8220;documentation&#8221;</li>\n<li>Make WordPress (Get Involved)</li>\n<li>About (many sub pages and also project structure)</li>\n<li>Blog</li>\n<li>Hosting</li>\n<li>Download (button &#8212; in future to be <a href=\"https://make.wordpress.org/meta/2016/02/29/get-wordpress-improving-the-path-to-wordpress/\">Get WordPress</a>)</li>\n</ul>\n<h3>Other Sections</h3>\n<ul>\n<li><a href=\"https://core.trac.wordpress.org/\">core.trac.wordpress.org</a></li>\n<li><a href=\"https://developer.wordpress.org/\">developer.wordpress.org</a></li>\n<li><a href=\"https://mercantile.wordpress.org/\">mercantile.wordpress.org</a></li>\n<li><a href=\"http://jobs.wordpress.net/\">jobs.wordpress.net</a></li>\n<li><a href=\"https://learn.wordpress.org/\">learn.wordpress.org</a></li>\n<li><a href=\"https://wordpress.org/ideas/\">Ideas</a></li>\n</ul>\n<h3>Other Linked Sites</h3>\n<ul>\n<li><a href=\"https://central.wordcamp.org/\">WordCamp</a></li>\n<li><a href=\"http://wordpress.tv/\">WordPress.tv</a></li>\n<li><a href=\"https://buddypress.org/\">BuddyPress</a></li>\n<li><a href=\"https://bbpress.org/\">bbPress</a></li>\n<li><a href=\"https://wordpress.com/\">WordPress.com</a></li>\n<li><a href=\"https://ma.tt/\">ma.tt</a></li>\n</ul>\n<h3>Active Projects for Improving</h3>\n<ul>\n<li><a href=\"https://make.wordpress.org/meta/tag/helphub/\">Helphub</a></li>\n<li>Handbooks (theme), plugin published</li>\n<li>Plugin directory</li>\n</ul>\n<h3>Links</h3>\n<ul>\n<li><a href=\"https://make.wordpress.org/meta/\">Blog for WordPress.org projects</a></li>\n</ul>\n<h3>Sponsor</h3>\n<p><span>This episode is sponsored by Gravity Forms. <a href=\"http://www.gravityforms.com/\">Gravity Forms</a>  makes the best web forms on the planet. Over a million WordPress sites are already using Gravity Forms. Is yours? For more information, check out their <a href=\"http://www.gravityforms.com/\">website</a> and thank you to Gravity Forms for being a Post Status partner. </span><b> </b></p>\";s:7:\"pubdate\";s:31:\"Fri, 27 May 2016 19:18:04 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Katie Richards\";}s:7:\"summary\";s:3592:\"<p>Welcome to the Post Status <a href=\"https://poststatus.com/category/draft\">Draft podcast</a>, which you can find <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">on iTunes</a>, <a href=\"https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast\">Google Play</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, and <a href=\"http://simplecast.fm/podcasts/1061/rss\">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle &#8212; the CTO of Human Made &#8212; and Brian Krogsgard.</p>\n<p><span>In this episode, Joe and Brian discuss the structure and function of the WordPress.org website, which is the hub of the WordPress project. From the actual software distribution, to discussions about the project, to support, and buying swag: it all happens from WordPress.org. We break down what’s what and what we think you should know.</span></p>\n<p><!--[if lt IE 9]><script>document.createElement(\'audio\');</script><![endif]-->\n<a href=\"https://audio.simplecast.com/38479.mp3\">https://audio.simplecast.com/38479.mp3</a><br />\n<a href=\"http://audio.simplecast.com/38479.mp3\">Direct Download</a></p>\n<h3>Notes</h3>\n<p>Who owns WordPress.org?<br />\nWho works on WordPress.org<br />\nHow WordPress.org distributes software updates</p>\n<h3>Different Sections of WordPress.org Navigation</h3>\n<ul>\n<li>Showcase</li>\n<li>WordPress theme directory &#8212; and reviews &#8212; and commercial themes</li>\n<li>WordPress plugin directory &#8212; and reviews</li>\n<li>Mobile &#8212; Redirects to .com</li>\n<li>Support Forums / Codex &#8220;documentation&#8221;</li>\n<li>Make WordPress (Get Involved)</li>\n<li>About (many sub pages and also project structure)</li>\n<li>Blog</li>\n<li>Hosting</li>\n<li>Download (button &#8212; in future to be <a href=\"https://make.wordpress.org/meta/2016/02/29/get-wordpress-improving-the-path-to-wordpress/\">Get WordPress</a>)</li>\n</ul>\n<h3>Other Sections</h3>\n<ul>\n<li><a href=\"https://core.trac.wordpress.org/\">core.trac.wordpress.org</a></li>\n<li><a href=\"https://developer.wordpress.org/\">developer.wordpress.org</a></li>\n<li><a href=\"https://mercantile.wordpress.org/\">mercantile.wordpress.org</a></li>\n<li><a href=\"http://jobs.wordpress.net/\">jobs.wordpress.net</a></li>\n<li><a href=\"https://learn.wordpress.org/\">learn.wordpress.org</a></li>\n<li><a href=\"https://wordpress.org/ideas/\">Ideas</a></li>\n</ul>\n<h3>Other Linked Sites</h3>\n<ul>\n<li><a href=\"https://central.wordcamp.org/\">WordCamp</a></li>\n<li><a href=\"http://wordpress.tv/\">WordPress.tv</a></li>\n<li><a href=\"https://buddypress.org/\">BuddyPress</a></li>\n<li><a href=\"https://bbpress.org/\">bbPress</a></li>\n<li><a href=\"https://wordpress.com/\">WordPress.com</a></li>\n<li><a href=\"https://ma.tt/\">ma.tt</a></li>\n</ul>\n<h3>Active Projects for Improving</h3>\n<ul>\n<li><a href=\"https://make.wordpress.org/meta/tag/helphub/\">Helphub</a></li>\n<li>Handbooks (theme), plugin published</li>\n<li>Plugin directory</li>\n</ul>\n<h3>Links</h3>\n<ul>\n<li><a href=\"https://make.wordpress.org/meta/\">Blog for WordPress.org projects</a></li>\n</ul>\n<h3>Sponsor</h3>\n<p><span>This episode is sponsored by Gravity Forms. <a href=\"http://www.gravityforms.com/\">Gravity Forms</a>  makes the best web forms on the planet. Over a million WordPress sites are already using Gravity Forms. Is yours? For more information, check out their <a href=\"http://www.gravityforms.com/\">website</a> and thank you to Gravity Forms for being a Post Status partner. </span><b> </b></p>\";}i:5;a:7:{s:5:\"title\";s:60:\"WPTavern: Jetpack 4.0.3 Patches a Critical XSS Vulnerability\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=55036\";s:4:\"link\";s:70:\"http://wptavern.com/jetpack-4-0-3-patches-a-critical-xss-vulnerability\";s:11:\"description\";s:2266:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/07/jetpack-logo.gif\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/07/jetpack-logo.gif?resize=700%2C276\" alt=\"jetpack-logo\" class=\"aligncenter size-full wp-image-27470\" /></a></p>\n<p><a href=\"https://jetpack.com/2016/05/27/jetpack-4-0-3-critical-security-update/\" target=\"_blank\">Jetpack 4.0.3 is a security release</a> that contains an important fix for a critical vulnerability that has been present in the plugin since version 2.0, released in 2012. According to Jetpack team member Sam Hotchkiss, a stored XSS vulnerability was found in the way that some Jetpack shortcodes are processed, which allows an attacker to insert JavaScript into comments to hijack a visitor&#8217;s browser.</p>\n<p>This particular bug is similar to one <a href=\"https://blog.sucuri.net/2016/05/security-advisory-stored-xss-bbpress-2.html\" target=\"_blank\">recently found and patched in bbPress</a>.</p>\n<p>&#8220;Similar issues may exist in other plugins, and it’s a good reminder about the power of regular expressions to create issues when parsing data,&#8221; Hotchkiss said.</p>\n<p>The Jetpack team has been working with the WordPress security team to push out point releases for all vulnerable branches of the plugin&#8217;s codebase, which includes all versions following 2.0. They are using WordPress&#8217; core automatic update system, so all sites that have not explicitly opted out will receive the security update.</p>\n<p>&#8220;Fortunately, we have no evidence of this being used in the wild,&#8221; Hotchkiss said. &#8220;However, now that this update is public, it’s just a matter of time before someone attempts to exploit it.&#8221; The Jetpack team is advising users to update as soon as possible, as the update also fixes any potential exploits that may have already been put in place.</p>\n<p>The team credits Marc-Alexandre Montpas from <a href=\"https://sucuri.net/\" target=\"_blank\">Sucuri</a> for finding the bug and disclosing it responsibly. Users will be notified about the security release via email, but those who have Akismet and/or VaultPress installed have already been protected since the first reporting of the vulnerability.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 27 May 2016 01:05:10 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2266:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/07/jetpack-logo.gif\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/07/jetpack-logo.gif?resize=700%2C276\" alt=\"jetpack-logo\" class=\"aligncenter size-full wp-image-27470\" /></a></p>\n<p><a href=\"https://jetpack.com/2016/05/27/jetpack-4-0-3-critical-security-update/\" target=\"_blank\">Jetpack 4.0.3 is a security release</a> that contains an important fix for a critical vulnerability that has been present in the plugin since version 2.0, released in 2012. According to Jetpack team member Sam Hotchkiss, a stored XSS vulnerability was found in the way that some Jetpack shortcodes are processed, which allows an attacker to insert JavaScript into comments to hijack a visitor&#8217;s browser.</p>\n<p>This particular bug is similar to one <a href=\"https://blog.sucuri.net/2016/05/security-advisory-stored-xss-bbpress-2.html\" target=\"_blank\">recently found and patched in bbPress</a>.</p>\n<p>&#8220;Similar issues may exist in other plugins, and it’s a good reminder about the power of regular expressions to create issues when parsing data,&#8221; Hotchkiss said.</p>\n<p>The Jetpack team has been working with the WordPress security team to push out point releases for all vulnerable branches of the plugin&#8217;s codebase, which includes all versions following 2.0. They are using WordPress&#8217; core automatic update system, so all sites that have not explicitly opted out will receive the security update.</p>\n<p>&#8220;Fortunately, we have no evidence of this being used in the wild,&#8221; Hotchkiss said. &#8220;However, now that this update is public, it’s just a matter of time before someone attempts to exploit it.&#8221; The Jetpack team is advising users to update as soon as possible, as the update also fixes any potential exploits that may have already been put in place.</p>\n<p>The team credits Marc-Alexandre Montpas from <a href=\"https://sucuri.net/\" target=\"_blank\">Sucuri</a> for finding the bug and disclosing it responsibly. Users will be notified about the security release via email, but those who have Akismet and/or VaultPress installed have already been protected since the first reporting of the vulnerability.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:6;a:7:{s:5:\"title\";s:70:\"Post Status: Growing a lifestyle business without losing the lifestyle\";s:4:\"guid\";s:31:\"https://poststatus.com/?p=24644\";s:4:\"link\";s:50:\"https://poststatus.com/growing-lifestyle-business/\";s:11:\"description\";s:8760:\"<p><em><strong>Editor&#8217;s Note</strong>: This is a guest post by Nate Wright. Nate is a WordPress developer and solopreneur. He runs <a href=\"http://themeofthecrop.com\">Theme of The Crop</a>, a niche WordPress theme company geared toward restaurant websites. You can learn more about Nate on his <a href=\"https://poststatus.com/profiles/nate-wright/\">Post Status profile</a> and follow him on <a href=\"https://twitter.com/natewr\">Twitter</a>.</em></p>\n<hr />\n<p>Here&#8217;s a scenario you&#8217;re probably familiar with: a friend or family member, not terribly tech-savvy, approaches you with an idea. Why don&#8217;t you build Facebook for clowns? What about Uber for sandwiches?</p>\n<p>Their ideas are often a little better than these. Sometimes they&#8217;re worse. But in my case the conversation always gets to the same point in the end.</p>\n<p>You can build stuff on the internet. Why aren&#8217;t you shooting for the stars? Don&#8217;t you want to be rich like Zuckerberg?</p>\n<p>Right now some of you may be thinking: yes I do! This post isn&#8217;t for you.</p>\n<p>This is for those of you who cringe at the thought of your days filling up with hiring and training staff, conducting meetings, or filling out paperwork. Those of you who don&#8217;t want to live the big siloed life of a CEO. Who dove into the WordPress market because you wanted to build things yourself. For yourself.</p>\n<h3>The rockstars and the rest of us</h3>\n<p>It’s hard to find someone more widely admired among WordPress developers &#8212; and more deserving of that admiration &#8212; than <a href=\"https://pippinsplugins.com/about/\">Pippin Williamson</a>. So when he <a href=\"https://pippinsplugins.com/control-give-grow/\">described his evolution</a> from staunch go-it-aloner to team leader, many of us sat up and listened.</p>\n<p>The <a href=\"https://pippinsplugins.com/control-give-grow/#comments\">comments</a> in response to that post exhibit a common mix of anxiety, frustration and hope for us go-it-aloners, who have carved out small (and not so small) niches in the WordPress world.</p>\n<p>We’re overstretched and under resourced. We lack good marketing strategies. And we can see that growth will come from transforming our businesses into larger enterprises.</p>\n<p>But then we start thinking about what that means. The hiring. The firing. The training. The meetings. The paperwork. <i>The liability</i>.</p>\n<p>&#8216;I don’t want to be the next Zuckerberg,&#8217; you may think. Then, hopefully, you’ll laugh at the absurdity. But really, you may think, &#8216;I don’t even want to be the next <a href=\"http://carlhancock.com/\">Carl Hancock</a> or <a href=\"https://yoast.com/author/joost/\">Joost de Valk</a>.&#8217;</p>\n<p>Let me be honest with you. I’ll stop putting words in your mouth and put them in mine.</p>\n<p>I have a lifestyle business. No, I don’t sell lifestyle products. I have a business <em>tailored to my lifestyle</em>.</p>\n<p>I have a business that allows to me to take lunch when I want, finish the day when I want, go on holiday when I want, write the code that I want. That’s my job perk. That’s my killer bonus. No, that’s my Shangri-La.</p>\n<p>When people tell you to hire early or scale quickly, they’re right that giving up control can be liberating. But it can also be encumbering. It brings new responsibilities at the same time that it releases you from old ones.</p>\n<p>Whether or not growing your team is right for you will depend on your temperament, your appetite and the kind of lifestyle you want.</p>\n<h3>Being a little fish in a big pond</h3>\n<p>But let’s be honest. You took a chance on the WordPress market because you saw a window of opportunity. That window may be closing.</p>\n<p>In the last few years we’ve seen a lot of consolidation. The theme market exploded, <a href=\"http://inside.envato.com/envato-stories-muhammad-haris-themefusion-2/\">made millions for a few</a>, and then caused a gold rush which <a href=\"http://scottbolinger.com/wordpress-theme-business/\">saturated the market and pushed out small operators</a>.</p>\n<p>At the same time, two big traditional distribution channels dried up: the official <a href=\"https://wordpress.org/themes/\">WordPress.org theme repository</a>, which has a huge backlog of themes awaiting approval, and <a href=\"https://theme.wordpress.com/\">Automattic’s marketplace</a>, which is closed to new entrants.</p>\n<p>We’re also seeing more traditional investment in WordPress properties. The big one is the <a href=\"http://recode.net/2014/05/05/wordpress-parent-automattic-has-raised-160-million-now-valued-at-1-16-billion-post-money/\">$160 million raised by Automattic</a> and Automattic&#8217;s subsequent <a href=\"https://poststatus.com/automattic-acquired-woocommerce-woothemes/\">acquisition of WooThemes</a>. Many actors are moving more aggressively to leverage or retain their market position. Syed Balkhi is on a buying and building spree (<a href=\"http://enviragallery.com/about-us/\">1</a>, <a href=\"http://optinmonster.com/about/\">2</a>, <a href=\"https://wpforms.com/say-hello-to-wpforms/\">3</a>, <a href=\"http://wptavern.com/syed-balkhi-acquires-google-analytics-by-yoast-renames-to-monsterinsights\">4</a>). Ninja Forms did a <a href=\"https://ninjaforms.com/releasing-three/\">ground-up rebuild</a>. Pippin’s shedding non-essential products (<a href=\"https://pippinsplugins.com/easy-content-types-acquired/\">1</a>, <a href=\"https://pippinsplugins.com/nikhil-vimal-adopts-front-end-registration-and-login-forms-plugin/\">2</a>) and <a href=\"https://pippinsplugins.com/selfish/\">purging some third-party addons</a>.</p>\n<p>The ecosystem looks increasingly unfriendly to us go-it-aloners. Automattic was the first to go big. Given exclusive commercial access to the WordPress trademark, it carved out its own space and split WordPress down the middle. Now the other half &#8212; the WordPress for the rest of us &#8212; is going big too.</p>\n<p>The nice thing about being a small operator is that you only need a tiny sliver of the pie. But as the size of the market has grown, it’s become more difficult to attract attention. Showing up with a good product isn’t enough.</p>\n<h3>Going it alone, together</h3>\n<p>My lifestyle business is working well for me. Revenue keeps inching up. Slowly.</p>\n<p>But it might not make it in a different kind of WordPress space. I’ve been thinking a lot about that lately. And I bet you have too.</p>\n<p>Where’s the market going? What am I willing to trade to survive? Which headaches are <a href=\"http://www.codeinwp.com/blog/transparency-report-14/\">worth changing direction for</a> and which headaches aren’t?</p>\n<p>Here are some of the ideas I’ve been tossing around:</p>\n<h3>Contractors</h3>\n<p>Hiring out. I could scale up or down easily, depending on how well it goes. But it’s tough to manage quality when juggling vendors.</p>\n<p>And what would I contract? I’d like to shed my bumbling efforts in marketing and traffic generation. But that seems like precisely the kind of job full of jackals who don’t know what they’re doing.</p>\n<p>Ok, that’s harsh. I’ll just say: I worry it’d be a headache to manage it well.</p>\n<p>Theme development seems the most plausible, since there’s a large body of talented, hungry themers washing up from the stormy seas of ThemeForest. But it may be the least valuable since the market is being swallowed up by a few big themes.</p>\n<h3>Commissions</h3>\n<p>Affiliate marketing is already working for me. A little. I could go further and recruit theme or plugin developers to sell from my site on commission.</p>\n<p>Then I’m saddled with support for products I didn’t build. Can I maintain quality? Can I drive enough traffic to be an attractive outlet for them? Will I end up with all of the headaches I wanted to avoid?</p>\n<h3>Partnerships</h3>\n<p>Maybe I’ll trade in my king-of-the-hill cap and bring on partners. Not employees. Genuine partners with overlapping skill sets. Instead of being a go-it-aloner we can be two or three go-it-aloners going it alone together!</p>\n<p>Or maybe that’s just a terrible way to run a business.</p>\n<h3>Alliances</h3>\n<p>There are a lot of us out there. Independent themers looking to expand beyond ThemeForest or give up on the old freemium approach of the official repository. Plugin developers looking for a new home or seeking out themes that will integrate with their plugins.</p>\n<p>We could probably do something special if we made stronger alliances. Combined to build to stronger platforms for our products.</p>\n<p>But that sounds like a lot of project management. Isn’t that what we were hoping to avoid?</p>\n<p>I don’t know. I’m going to go write some code.</p>\";s:7:\"pubdate\";s:31:\"Thu, 26 May 2016 18:10:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:11:\"Nate Wright\";}s:7:\"summary\";s:8760:\"<p><em><strong>Editor&#8217;s Note</strong>: This is a guest post by Nate Wright. Nate is a WordPress developer and solopreneur. He runs <a href=\"http://themeofthecrop.com\">Theme of The Crop</a>, a niche WordPress theme company geared toward restaurant websites. You can learn more about Nate on his <a href=\"https://poststatus.com/profiles/nate-wright/\">Post Status profile</a> and follow him on <a href=\"https://twitter.com/natewr\">Twitter</a>.</em></p>\n<hr />\n<p>Here&#8217;s a scenario you&#8217;re probably familiar with: a friend or family member, not terribly tech-savvy, approaches you with an idea. Why don&#8217;t you build Facebook for clowns? What about Uber for sandwiches?</p>\n<p>Their ideas are often a little better than these. Sometimes they&#8217;re worse. But in my case the conversation always gets to the same point in the end.</p>\n<p>You can build stuff on the internet. Why aren&#8217;t you shooting for the stars? Don&#8217;t you want to be rich like Zuckerberg?</p>\n<p>Right now some of you may be thinking: yes I do! This post isn&#8217;t for you.</p>\n<p>This is for those of you who cringe at the thought of your days filling up with hiring and training staff, conducting meetings, or filling out paperwork. Those of you who don&#8217;t want to live the big siloed life of a CEO. Who dove into the WordPress market because you wanted to build things yourself. For yourself.</p>\n<h3>The rockstars and the rest of us</h3>\n<p>It’s hard to find someone more widely admired among WordPress developers &#8212; and more deserving of that admiration &#8212; than <a href=\"https://pippinsplugins.com/about/\">Pippin Williamson</a>. So when he <a href=\"https://pippinsplugins.com/control-give-grow/\">described his evolution</a> from staunch go-it-aloner to team leader, many of us sat up and listened.</p>\n<p>The <a href=\"https://pippinsplugins.com/control-give-grow/#comments\">comments</a> in response to that post exhibit a common mix of anxiety, frustration and hope for us go-it-aloners, who have carved out small (and not so small) niches in the WordPress world.</p>\n<p>We’re overstretched and under resourced. We lack good marketing strategies. And we can see that growth will come from transforming our businesses into larger enterprises.</p>\n<p>But then we start thinking about what that means. The hiring. The firing. The training. The meetings. The paperwork. <i>The liability</i>.</p>\n<p>&#8216;I don’t want to be the next Zuckerberg,&#8217; you may think. Then, hopefully, you’ll laugh at the absurdity. But really, you may think, &#8216;I don’t even want to be the next <a href=\"http://carlhancock.com/\">Carl Hancock</a> or <a href=\"https://yoast.com/author/joost/\">Joost de Valk</a>.&#8217;</p>\n<p>Let me be honest with you. I’ll stop putting words in your mouth and put them in mine.</p>\n<p>I have a lifestyle business. No, I don’t sell lifestyle products. I have a business <em>tailored to my lifestyle</em>.</p>\n<p>I have a business that allows to me to take lunch when I want, finish the day when I want, go on holiday when I want, write the code that I want. That’s my job perk. That’s my killer bonus. No, that’s my Shangri-La.</p>\n<p>When people tell you to hire early or scale quickly, they’re right that giving up control can be liberating. But it can also be encumbering. It brings new responsibilities at the same time that it releases you from old ones.</p>\n<p>Whether or not growing your team is right for you will depend on your temperament, your appetite and the kind of lifestyle you want.</p>\n<h3>Being a little fish in a big pond</h3>\n<p>But let’s be honest. You took a chance on the WordPress market because you saw a window of opportunity. That window may be closing.</p>\n<p>In the last few years we’ve seen a lot of consolidation. The theme market exploded, <a href=\"http://inside.envato.com/envato-stories-muhammad-haris-themefusion-2/\">made millions for a few</a>, and then caused a gold rush which <a href=\"http://scottbolinger.com/wordpress-theme-business/\">saturated the market and pushed out small operators</a>.</p>\n<p>At the same time, two big traditional distribution channels dried up: the official <a href=\"https://wordpress.org/themes/\">WordPress.org theme repository</a>, which has a huge backlog of themes awaiting approval, and <a href=\"https://theme.wordpress.com/\">Automattic’s marketplace</a>, which is closed to new entrants.</p>\n<p>We’re also seeing more traditional investment in WordPress properties. The big one is the <a href=\"http://recode.net/2014/05/05/wordpress-parent-automattic-has-raised-160-million-now-valued-at-1-16-billion-post-money/\">$160 million raised by Automattic</a> and Automattic&#8217;s subsequent <a href=\"https://poststatus.com/automattic-acquired-woocommerce-woothemes/\">acquisition of WooThemes</a>. Many actors are moving more aggressively to leverage or retain their market position. Syed Balkhi is on a buying and building spree (<a href=\"http://enviragallery.com/about-us/\">1</a>, <a href=\"http://optinmonster.com/about/\">2</a>, <a href=\"https://wpforms.com/say-hello-to-wpforms/\">3</a>, <a href=\"http://wptavern.com/syed-balkhi-acquires-google-analytics-by-yoast-renames-to-monsterinsights\">4</a>). Ninja Forms did a <a href=\"https://ninjaforms.com/releasing-three/\">ground-up rebuild</a>. Pippin’s shedding non-essential products (<a href=\"https://pippinsplugins.com/easy-content-types-acquired/\">1</a>, <a href=\"https://pippinsplugins.com/nikhil-vimal-adopts-front-end-registration-and-login-forms-plugin/\">2</a>) and <a href=\"https://pippinsplugins.com/selfish/\">purging some third-party addons</a>.</p>\n<p>The ecosystem looks increasingly unfriendly to us go-it-aloners. Automattic was the first to go big. Given exclusive commercial access to the WordPress trademark, it carved out its own space and split WordPress down the middle. Now the other half &#8212; the WordPress for the rest of us &#8212; is going big too.</p>\n<p>The nice thing about being a small operator is that you only need a tiny sliver of the pie. But as the size of the market has grown, it’s become more difficult to attract attention. Showing up with a good product isn’t enough.</p>\n<h3>Going it alone, together</h3>\n<p>My lifestyle business is working well for me. Revenue keeps inching up. Slowly.</p>\n<p>But it might not make it in a different kind of WordPress space. I’ve been thinking a lot about that lately. And I bet you have too.</p>\n<p>Where’s the market going? What am I willing to trade to survive? Which headaches are <a href=\"http://www.codeinwp.com/blog/transparency-report-14/\">worth changing direction for</a> and which headaches aren’t?</p>\n<p>Here are some of the ideas I’ve been tossing around:</p>\n<h3>Contractors</h3>\n<p>Hiring out. I could scale up or down easily, depending on how well it goes. But it’s tough to manage quality when juggling vendors.</p>\n<p>And what would I contract? I’d like to shed my bumbling efforts in marketing and traffic generation. But that seems like precisely the kind of job full of jackals who don’t know what they’re doing.</p>\n<p>Ok, that’s harsh. I’ll just say: I worry it’d be a headache to manage it well.</p>\n<p>Theme development seems the most plausible, since there’s a large body of talented, hungry themers washing up from the stormy seas of ThemeForest. But it may be the least valuable since the market is being swallowed up by a few big themes.</p>\n<h3>Commissions</h3>\n<p>Affiliate marketing is already working for me. A little. I could go further and recruit theme or plugin developers to sell from my site on commission.</p>\n<p>Then I’m saddled with support for products I didn’t build. Can I maintain quality? Can I drive enough traffic to be an attractive outlet for them? Will I end up with all of the headaches I wanted to avoid?</p>\n<h3>Partnerships</h3>\n<p>Maybe I’ll trade in my king-of-the-hill cap and bring on partners. Not employees. Genuine partners with overlapping skill sets. Instead of being a go-it-aloner we can be two or three go-it-aloners going it alone together!</p>\n<p>Or maybe that’s just a terrible way to run a business.</p>\n<h3>Alliances</h3>\n<p>There are a lot of us out there. Independent themers looking to expand beyond ThemeForest or give up on the old freemium approach of the official repository. Plugin developers looking for a new home or seeking out themes that will integrate with their plugins.</p>\n<p>We could probably do something special if we made stronger alliances. Combined to build to stronger platforms for our products.</p>\n<p>But that sounds like a lot of project management. Isn’t that what we were hoping to avoid?</p>\n<p>I don’t know. I’m going to go write some code.</p>\";}i:7;a:7:{s:5:\"title\";s:46:\"WP Mobile Apps: WordPress for iOS: Version 6.2\";s:4:\"guid\";s:33:\"http://apps.wordpress.com/?p=3416\";s:4:\"link\";s:68:\"https://apps.wordpress.com/2016/05/25/wordpress-for-ios-version-6-2/\";s:11:\"description\";s:3021:\"<p>Hi there, WordPress users! <a href=\"https://itunes.apple.com/us/app/wordpress/id335703880?mt=8&uo=6&at=&ct=\">Version 6.2 of the WordPress for iOS app</a> is now available in the App Store.</p>\n<h1>What&#8217;s New:</h1>\n<p><strong>Sharing just got easier!</strong> Post content from apps to your WordPress.com site with a new Share extension. Also, share a post right from your editor’s preview screen.</p>\n\n<a href=\"https://apps.wordpress.com/img_2229_2/\"><img width=\"169\" height=\"300\" src=\"https://apps.files.wordpress.com/2016/05/img_2229_2.png?w=169&h=300\" class=\"attachment-medium size-medium\" alt=\"IMG_2229_2\" /></a>\n<a href=\"https://apps.wordpress.com/img_2230/\"><img width=\"169\" height=\"300\" src=\"https://apps.files.wordpress.com/2016/05/img_2230.png?w=169&h=300\" class=\"attachment-medium size-medium\" alt=\"IMG_2230\" /></a>\n\n<p><strong>Improved clipboard support: </strong>Working with images? You can now copy and paste single images in your editor.</p>\n<p><strong>Login with ease:</strong> We improved error messages for self-hosted users.</p>\n<p><strong>Enhancements:</strong> Because &#8220;good&#8221; is not enough! Here&#8217;s the full <a href=\"https://github.com/wordpress-mobile/WordPress-iOS/issues?q=is%3Aclosed+is%3Aissue+milestone%3A6.2+label%3A%22%5BType%5D+Enhancement%22\">list of enhancements</a>.</p>\n<p><strong>Bugs, be gone!</strong> We zapped bugs that prevented images from rendering properly and caused backspaces to misbehave.  You can see the full list of bug fixes <a href=\"https://github.com/wordpress-mobile/WordPress-iOS/issues?q=is%3Aclosed+is%3Aissue+milestone%3A6.1+label%3A%22%5BType%5D+Bug%22\">here</a>!</p>\n<h1>Thank You</h1>\n<p>Thanks to all of the contributors who worked on this release:<br />\n<a href=\"https://github.com/aerych\">@aerych</a>, <a href=\"https://github.com/akirk\">@akirk</a>, <a href=\"https://github.com/alexcurylo\">@alexcurylo</a>, <a href=\"https://github.com/astralbodies\">@astralbodies</a>, <a href=\"https://github.com/diegoreymendez\">@diegoreymendez</a>, <a href=\"https://github.com/frosty\">@frosty</a>, <a href=\"https://github.com/jleandroperez\">@jleandroperez</a>, <a href=\"https://github.com/koke\">@koke</a>, <a href=\"https://github.com/kurzee\">@kurzee</a>, <a href=\"https://github.com/kwonye\">@kwonye</a>, <a href=\"https://github.com/maxme\">@maxme</a>, <a href=\"https://github.com/nheagy\">@nheagy</a>, <a href=\"https://github.com/rachelmcr\">@rachelmcr</a>, <a href=\"https://github.com/sendhil\">@sendhil</a>, <a href=\"https://github.com/mattmiklic\">@mattmiklic</a> and <a href=\"https://github.com/SergioEstevao\">@SergioEstevao</a>.</p>\n<p>You can track the development progress for the next update by visiting <a href=\"https://github.com/wordpress-mobile/WordPress-iOS/issues?utf8=?&q=is%3Aissue+milestone%3A6.3+\" target=\"_blank\">our 6.3 milestone on GitHub</a>. Until next time!</p><img alt=\"\" border=\"0\" src=\"https://pixel.wp.com/b.gif?host=apps.wordpress.com&blog=108068616&post=3416&subd=apps&ref=&feed=1\" width=\"1\" height=\"1\" />\";s:7:\"pubdate\";s:31:\"Wed, 25 May 2016 06:05:48 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"diegoreymendez\";}s:7:\"summary\";s:3021:\"<p>Hi there, WordPress users! <a href=\"https://itunes.apple.com/us/app/wordpress/id335703880?mt=8&uo=6&at=&ct=\">Version 6.2 of the WordPress for iOS app</a> is now available in the App Store.</p>\n<h1>What&#8217;s New:</h1>\n<p><strong>Sharing just got easier!</strong> Post content from apps to your WordPress.com site with a new Share extension. Also, share a post right from your editor’s preview screen.</p>\n\n<a href=\"https://apps.wordpress.com/img_2229_2/\"><img width=\"169\" height=\"300\" src=\"https://apps.files.wordpress.com/2016/05/img_2229_2.png?w=169&h=300\" class=\"attachment-medium size-medium\" alt=\"IMG_2229_2\" /></a>\n<a href=\"https://apps.wordpress.com/img_2230/\"><img width=\"169\" height=\"300\" src=\"https://apps.files.wordpress.com/2016/05/img_2230.png?w=169&h=300\" class=\"attachment-medium size-medium\" alt=\"IMG_2230\" /></a>\n\n<p><strong>Improved clipboard support: </strong>Working with images? You can now copy and paste single images in your editor.</p>\n<p><strong>Login with ease:</strong> We improved error messages for self-hosted users.</p>\n<p><strong>Enhancements:</strong> Because &#8220;good&#8221; is not enough! Here&#8217;s the full <a href=\"https://github.com/wordpress-mobile/WordPress-iOS/issues?q=is%3Aclosed+is%3Aissue+milestone%3A6.2+label%3A%22%5BType%5D+Enhancement%22\">list of enhancements</a>.</p>\n<p><strong>Bugs, be gone!</strong> We zapped bugs that prevented images from rendering properly and caused backspaces to misbehave.  You can see the full list of bug fixes <a href=\"https://github.com/wordpress-mobile/WordPress-iOS/issues?q=is%3Aclosed+is%3Aissue+milestone%3A6.1+label%3A%22%5BType%5D+Bug%22\">here</a>!</p>\n<h1>Thank You</h1>\n<p>Thanks to all of the contributors who worked on this release:<br />\n<a href=\"https://github.com/aerych\">@aerych</a>, <a href=\"https://github.com/akirk\">@akirk</a>, <a href=\"https://github.com/alexcurylo\">@alexcurylo</a>, <a href=\"https://github.com/astralbodies\">@astralbodies</a>, <a href=\"https://github.com/diegoreymendez\">@diegoreymendez</a>, <a href=\"https://github.com/frosty\">@frosty</a>, <a href=\"https://github.com/jleandroperez\">@jleandroperez</a>, <a href=\"https://github.com/koke\">@koke</a>, <a href=\"https://github.com/kurzee\">@kurzee</a>, <a href=\"https://github.com/kwonye\">@kwonye</a>, <a href=\"https://github.com/maxme\">@maxme</a>, <a href=\"https://github.com/nheagy\">@nheagy</a>, <a href=\"https://github.com/rachelmcr\">@rachelmcr</a>, <a href=\"https://github.com/sendhil\">@sendhil</a>, <a href=\"https://github.com/mattmiklic\">@mattmiklic</a> and <a href=\"https://github.com/SergioEstevao\">@SergioEstevao</a>.</p>\n<p>You can track the development progress for the next update by visiting <a href=\"https://github.com/wordpress-mobile/WordPress-iOS/issues?utf8=?&q=is%3Aissue+milestone%3A6.3+\" target=\"_blank\">our 6.3 milestone on GitHub</a>. Until next time!</p><img alt=\"\" border=\"0\" src=\"https://pixel.wp.com/b.gif?host=apps.wordpress.com&blog=108068616&post=3416&subd=apps&ref=&feed=1\" width=\"1\" height=\"1\" />\";}i:8;a:7:{s:5:\"title\";s:43:\"WPTavern: In Case You Missed It – Issue 9\";s:4:\"guid\";s:44:\"http://wptavern.com?p=55015&preview_id=55015\";s:4:\"link\";s:49:\"http://wptavern.com/in-case-you-missed-it-issue-9\";s:11:\"description\";s:8011:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/ICYMIFeaturedImage.png\" rel=\"attachment wp-att-50955\"><img class=\"size-full wp-image-50955\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/ICYMIFeaturedImage.png?resize=676%2C292\" alt=\"In Case You Missed It Featured Image\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/112901923@N07/16153818039\">Night Moves</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nc/2.0/\">(license)</a>\n<p>There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.</p>\n<h2>Chris Lema Launches Beyond Good</h2>\n<p>Chris Lema has launched a new site called <a href=\"http://beyondgood.com/\">Beyond Good </a>that provides insight, tips, and methodologies for leading employees to become better than good. If it&#8217;s anything like his other sites, it&#8217;s sure to be a hit in the WordPress community.</p>\n<h2>Remote Jobs, a Remote Worker Specific Jobs Board</h2>\n<p>Chris Wallace and the team at Lift have launched <a href=\"https://remotejobs.com/\">Remote Jobs</a>, a jobs board specifically catered to remote workers. According to Wallace, &#8220;The site exists to help others find remote jobs that connect them with their passions in life.&#8221; Check out the site as there&#8217;s already a decent listing of opportunities available for remote workers.</p>\n<h2>Why .Blog is Worth $19M</h2>\n<p>Matt Mullenweg participated in a <a href=\"http://venturebeat.com/2016/05/12/the-creator-of-wordpress-on-why-blog-was-worth-19-million/\">phone interview with VentureBeat</a>. The first question in the interview asks why the .blog domain is worth $19M.</p>\n<blockquote><p>Well, the domain business is actually a really good business because you can sell a domain and people use it and keep it forever. So, if you look at like a Verisign, or people who have TLDs, it’s actually an incredible business.</p>\n<p>We really wanted .blog to be open, and some of the other applications for .blog were closed, including Google — so, let’s say for example, only Blogger could have a .blog domain. And we thought that .blog should be open to everyone, even if they’re not using WordPress.</p>\n<p>I gotta be honest though, it was a stressful auction.</p></blockquote>\n<p>There are other tidbits of information included in the interview that I highly encourage you to read. If I were Google, I&#8217;d be upset as .blog is the perfect complimentary domain for Blogger.</p>\n<h2>Drupal Association Gives Community Member a Lifetime Ban</h2>\n<p>DrupalCon New Orleans took place last week and during the event, several speakers <a href=\"https://www.drupal.org/node/2729687\">experienced online harassment</a> in the form of derogatory racist, homophobic, and misogynistic comments and images from an anonymous Twitter account. Upon further investigation by community members and the Drupal Association technical and event staff, the harassment was tracked to an attendee at the event.</p>\n<blockquote><p>This person was then confronted by members of the Drupal Association staff and the Community Working Group. They were asked to leave the event and informed that they have been banned from attending any future DrupalCons as well as any events produced by the Drupal Association, in accordance with the <a href=\"https://events.drupal.org/neworleans2016/code-conduct\" rel=\"nofollow\">DrupalCon Code of Conduct</a>, which states, &#8216;We do not tolerate harassment of conference participants in any form.&#8217; Shortly after the person left the conference, the account from which the harassing tweets were made was deleted.</p></blockquote>\n<p>This is an excellent example of why Codes of Conduct exist for events. By the way, check out the <a href=\"https://plan.wordcamp.org/code-of-conduct/\">Code of Conduct</a> that&#8217;s in place for every WordCamp. If you experience harassment of any kind at a WordCamp, please tell event staff.</p>\n<h2>Plans Published to Upgrade WordPress Support Forums</h2>\n<p>Jennifer Dodd published a <a href=\"https://make.wordpress.org/meta/2016/05/19/wordpress-org-forums-upgrade/\">detailed plan</a> for migrating the WordPress.org support forums from bbPress 1.x to 2.x. The project is a huge undertaking and involves moving massive amounts of data. If all goes according to plan, the support forums will be on bbPress 2.x by the end of the year. I&#8217;m sure a lot of support forum volunteers are stoked to hear this news.</p>\n<h2>What NOT to Name a WordPress Theme</h2>\n<p>This tweet by Ryan Sullivan gave me a good laugh.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">I\'d strongly consider rebranding. <a href=\"https://t.co/9MeevJTlPq\">pic.twitter.com/9MeevJTlPq</a></p>\n<p>&mdash; Ryan D. Sullivan (@ryandonsullivan) <a href=\"https://twitter.com/ryandonsullivan/status/733120690816065536\">May 19, 2016</a></p></blockquote>\n<p></p>\n<h2>Tom McFarlin on Improving the WordPress Plugin UX</h2>\n<p>Tom McFarlin published a <a href=\"https://tommcfarlin.com/wordpress-plugin-user-experience-2/\">great article</a> that offers ideas on how plugin developers can improve the WordPress plugin user experience. His first suggestion is a key reason I think GravityForms became successful.</p>\n<blockquote><p>Try to make sure that your project tightly integrates with the core WordPress user interface.</p></blockquote>\n<p>When I witnessed GravityForms for the first time in 2009, I loved how it integrated into the WordPress backend as if it were a part of the core software. Fast forward to 2016 and plugins that tie into a service are experimenting with overlay interfaces that replace WordPress&#8217;. The most recent example I recall is WP Forms <a href=\"http://wptavern.com/wpforms-aims-to-be-the-most-beginner-friendly-forms-plugin-for-wordpress\">that I reviewed</a> earlier this year.</p>\n<p>In my review, I specifically noted that the interface the developers used allowed me to focus on creating forms. It doesn&#8217;t seem like it&#8217;s a WordPress core feature and it didn&#8217;t have too. While the advice McFarlin gives is likely accurate for most cases, there are plugins that benefit from having a unique user interface different from WordPress&#8217;.</p>\n<h2>Don&#8217;t Edit Core</h2>\n<p>This comic <a href=\"http://www.commitstrip.com/en/2016/05/17/coder-dilemma-9-the-upgrade/\">created by CommitStrip</a> made me smile.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Coder Dilemma #9 &#8211; The Upgrade<br /> <a href=\"https://t.co/2Tu2l1tgYX\">https://t.co/2Tu2l1tgYX</a> <a href=\"https://t.co/xnMr2VdYWv\">pic.twitter.com/xnMr2VdYWv</a></p>\n<p>&mdash; CommitStrip (@CommitStrip) <a href=\"https://twitter.com/CommitStrip/status/732505464768843776\">May 17, 2016</a></p></blockquote>\n<p></p>\n<h2>Wapuu Tattoo!</h2>\n<p>In what is a traditional part of this series, I end each issue by featuring a Wapuu design. For those who don&#8217;t know, Wapuu is the <a href=\"http://wapuu.jp/2015/12/12/wapuu-origins/\">unofficial mascot</a> of the WordPress project. WordCamp St. Louis 2016, took place last weekend and one of the attendees had a Wapuu tattoo! Wapuu looks good everywhere, including human skin!</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Wapuu has been sighted at <a href=\"https://twitter.com/hashtag/wcstl?src=hash\">#wcstl</a> <a href=\"https://twitter.com/hashtag/wordpress?src=hash\">#wordpress</a> <a href=\"https://twitter.com/hashtag/wapuu?src=hash\">#wapuu</a> <a href=\"https://t.co/4HYlp6GI0S\">pic.twitter.com/4HYlp6GI0S</a></p>\n<p>&mdash; Nile Flores (@blondishnet) <a href=\"https://twitter.com/blondishnet/status/731504592668758017\">May 14, 2016</a></p></blockquote>\n<p></p>\n<p>That&#8217;s it for issue nine. If you recently discovered a cool resource or post related to WordPress, please share it with us in the comments.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 20 May 2016 22:30:11 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:8011:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/ICYMIFeaturedImage.png\" rel=\"attachment wp-att-50955\"><img class=\"size-full wp-image-50955\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/ICYMIFeaturedImage.png?resize=676%2C292\" alt=\"In Case You Missed It Featured Image\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/112901923@N07/16153818039\">Night Moves</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nc/2.0/\">(license)</a>\n<p>There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.</p>\n<h2>Chris Lema Launches Beyond Good</h2>\n<p>Chris Lema has launched a new site called <a href=\"http://beyondgood.com/\">Beyond Good </a>that provides insight, tips, and methodologies for leading employees to become better than good. If it&#8217;s anything like his other sites, it&#8217;s sure to be a hit in the WordPress community.</p>\n<h2>Remote Jobs, a Remote Worker Specific Jobs Board</h2>\n<p>Chris Wallace and the team at Lift have launched <a href=\"https://remotejobs.com/\">Remote Jobs</a>, a jobs board specifically catered to remote workers. According to Wallace, &#8220;The site exists to help others find remote jobs that connect them with their passions in life.&#8221; Check out the site as there&#8217;s already a decent listing of opportunities available for remote workers.</p>\n<h2>Why .Blog is Worth $19M</h2>\n<p>Matt Mullenweg participated in a <a href=\"http://venturebeat.com/2016/05/12/the-creator-of-wordpress-on-why-blog-was-worth-19-million/\">phone interview with VentureBeat</a>. The first question in the interview asks why the .blog domain is worth $19M.</p>\n<blockquote><p>Well, the domain business is actually a really good business because you can sell a domain and people use it and keep it forever. So, if you look at like a Verisign, or people who have TLDs, it’s actually an incredible business.</p>\n<p>We really wanted .blog to be open, and some of the other applications for .blog were closed, including Google — so, let’s say for example, only Blogger could have a .blog domain. And we thought that .blog should be open to everyone, even if they’re not using WordPress.</p>\n<p>I gotta be honest though, it was a stressful auction.</p></blockquote>\n<p>There are other tidbits of information included in the interview that I highly encourage you to read. If I were Google, I&#8217;d be upset as .blog is the perfect complimentary domain for Blogger.</p>\n<h2>Drupal Association Gives Community Member a Lifetime Ban</h2>\n<p>DrupalCon New Orleans took place last week and during the event, several speakers <a href=\"https://www.drupal.org/node/2729687\">experienced online harassment</a> in the form of derogatory racist, homophobic, and misogynistic comments and images from an anonymous Twitter account. Upon further investigation by community members and the Drupal Association technical and event staff, the harassment was tracked to an attendee at the event.</p>\n<blockquote><p>This person was then confronted by members of the Drupal Association staff and the Community Working Group. They were asked to leave the event and informed that they have been banned from attending any future DrupalCons as well as any events produced by the Drupal Association, in accordance with the <a href=\"https://events.drupal.org/neworleans2016/code-conduct\" rel=\"nofollow\">DrupalCon Code of Conduct</a>, which states, &#8216;We do not tolerate harassment of conference participants in any form.&#8217; Shortly after the person left the conference, the account from which the harassing tweets were made was deleted.</p></blockquote>\n<p>This is an excellent example of why Codes of Conduct exist for events. By the way, check out the <a href=\"https://plan.wordcamp.org/code-of-conduct/\">Code of Conduct</a> that&#8217;s in place for every WordCamp. If you experience harassment of any kind at a WordCamp, please tell event staff.</p>\n<h2>Plans Published to Upgrade WordPress Support Forums</h2>\n<p>Jennifer Dodd published a <a href=\"https://make.wordpress.org/meta/2016/05/19/wordpress-org-forums-upgrade/\">detailed plan</a> for migrating the WordPress.org support forums from bbPress 1.x to 2.x. The project is a huge undertaking and involves moving massive amounts of data. If all goes according to plan, the support forums will be on bbPress 2.x by the end of the year. I&#8217;m sure a lot of support forum volunteers are stoked to hear this news.</p>\n<h2>What NOT to Name a WordPress Theme</h2>\n<p>This tweet by Ryan Sullivan gave me a good laugh.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">I\'d strongly consider rebranding. <a href=\"https://t.co/9MeevJTlPq\">pic.twitter.com/9MeevJTlPq</a></p>\n<p>&mdash; Ryan D. Sullivan (@ryandonsullivan) <a href=\"https://twitter.com/ryandonsullivan/status/733120690816065536\">May 19, 2016</a></p></blockquote>\n<p></p>\n<h2>Tom McFarlin on Improving the WordPress Plugin UX</h2>\n<p>Tom McFarlin published a <a href=\"https://tommcfarlin.com/wordpress-plugin-user-experience-2/\">great article</a> that offers ideas on how plugin developers can improve the WordPress plugin user experience. His first suggestion is a key reason I think GravityForms became successful.</p>\n<blockquote><p>Try to make sure that your project tightly integrates with the core WordPress user interface.</p></blockquote>\n<p>When I witnessed GravityForms for the first time in 2009, I loved how it integrated into the WordPress backend as if it were a part of the core software. Fast forward to 2016 and plugins that tie into a service are experimenting with overlay interfaces that replace WordPress&#8217;. The most recent example I recall is WP Forms <a href=\"http://wptavern.com/wpforms-aims-to-be-the-most-beginner-friendly-forms-plugin-for-wordpress\">that I reviewed</a> earlier this year.</p>\n<p>In my review, I specifically noted that the interface the developers used allowed me to focus on creating forms. It doesn&#8217;t seem like it&#8217;s a WordPress core feature and it didn&#8217;t have too. While the advice McFarlin gives is likely accurate for most cases, there are plugins that benefit from having a unique user interface different from WordPress&#8217;.</p>\n<h2>Don&#8217;t Edit Core</h2>\n<p>This comic <a href=\"http://www.commitstrip.com/en/2016/05/17/coder-dilemma-9-the-upgrade/\">created by CommitStrip</a> made me smile.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Coder Dilemma #9 &#8211; The Upgrade<br /> <a href=\"https://t.co/2Tu2l1tgYX\">https://t.co/2Tu2l1tgYX</a> <a href=\"https://t.co/xnMr2VdYWv\">pic.twitter.com/xnMr2VdYWv</a></p>\n<p>&mdash; CommitStrip (@CommitStrip) <a href=\"https://twitter.com/CommitStrip/status/732505464768843776\">May 17, 2016</a></p></blockquote>\n<p></p>\n<h2>Wapuu Tattoo!</h2>\n<p>In what is a traditional part of this series, I end each issue by featuring a Wapuu design. For those who don&#8217;t know, Wapuu is the <a href=\"http://wapuu.jp/2015/12/12/wapuu-origins/\">unofficial mascot</a> of the WordPress project. WordCamp St. Louis 2016, took place last weekend and one of the attendees had a Wapuu tattoo! Wapuu looks good everywhere, including human skin!</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Wapuu has been sighted at <a href=\"https://twitter.com/hashtag/wcstl?src=hash\">#wcstl</a> <a href=\"https://twitter.com/hashtag/wordpress?src=hash\">#wordpress</a> <a href=\"https://twitter.com/hashtag/wapuu?src=hash\">#wapuu</a> <a href=\"https://t.co/4HYlp6GI0S\">pic.twitter.com/4HYlp6GI0S</a></p>\n<p>&mdash; Nile Flores (@blondishnet) <a href=\"https://twitter.com/blondishnet/status/731504592668758017\">May 14, 2016</a></p></blockquote>\n<p></p>\n<p>That&#8217;s it for issue nine. If you recently discovered a cool resource or post related to WordPress, please share it with us in the comments.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:9;a:7:{s:5:\"title\";s:83:\"WPTavern: WordPress Meta Team Publishes Prototypes of The Plugin Directory Redesign\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=55006\";s:4:\"link\";s:93:\"http://wptavern.com/wordpress-meta-team-publishes-prototypes-of-the-plugin-directory-redesign\";s:11:\"description\";s:3713:\"<p>In early 2015, the WordPress.org Meta team <a href=\"http://wptavern.com/wordpress-plugin-directory-launches-new-design\">redesigned</a> the <a href=\"https://wordpress.org/plugins/\">WordPress plugin directory</a> and added a number of new features. In an effort to iterate on the page&#8217;s layout, the Meta Team has <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/\">published prototypes</a> of a new design for the <a href=\"http://codepen.io/mapk/full/jqxqbo/\">plugin directory&#8217;s home</a> and <a href=\"http://codepen.io/mapk/full/KzGQKv/\">search results pages</a>.</p>\n<p>The prototypes are inspired by <a href=\"https://get.wp.com/\">Get WordPress</a>, a landing page that provides key information about the WordPress project at a glance.</p>\n<p>There are a few things to keep in mind while looking at these prototypes. The first is that plugin information displayed on the page is inaccurate. Second, the Pro and Light classifications are for design purposes only. Third, links at the bottom will point to their corresponding pages.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PluginDirectoryMockup1.png\"><img class=\"size-full wp-image-55007\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PluginDirectoryMockup1.png?resize=1025%2C2753\" alt=\"WordPress Plugin Directory Homepage Protoype\" /></a>WordPress Plugin Directory Homepage Protoype\n<p>Unlike the current design, the prototype displays far less information. Authors, Last Updated, Compatibility, and Active Installs are absent from the homepage view. Initial feedback <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/#comment-8151\">highlights the concern</a> that too much information has been stripped away.</p>\n<p>In response to a comment on the announcement post, Samuel Sidler, <span class=\"st\">Apollo Team Lead at Automattic and contributor to the Meta team</span>, <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/#comment-8154\">explains</a> why he doesn&#8217;t think the information is useful to users.</p>\n<blockquote><p>Author, as you said, is only really useful for insiders. The latter two, meanwhile, are already taken into account in the search results. If a plugin doesn’t have a recent compatible version, it will move down the list. If it’s too old, it won’t get shown at all (which is the case today).</p>\n<p>Active installs is more interesting, but we account for it weighting search results as-is. I actually find it refreshing to <em>not</em> show the active installs as it allows for less-popular plugins to get more downloads. Users will be less likely to click the popular plugins (outside of familiar names) and more likely to find the plugin they actually need.</p></blockquote>\n<p>Another commenter suggests <a href=\"https://profiles.wordpress.org/awakensolutions/\">creating a simple/advanced view. </a>By default, the page could display a simplistic design while giving power users an option for more details.</p>\n<p>&#8220;Just like <a href=\"https://wordpress.org/about/philosophy/\" rel=\"nofollow\">WordPress core</a>, we strive to design for the majority and build features for the 80%,&#8221; Sidler said in response to the comment. &#8220;An &#8216;advanced&#8217; view doesn’t meet that requirement, in my eyes.&#8221;</p>\n<p>The Meta team is iterating quickly and will soon publish a prototype of the plugin details page. If you have feedback on the plugin homepage and search result prototypes, please leave a comment on <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/\">the announcement post</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 20 May 2016 20:19:32 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:3713:\"<p>In early 2015, the WordPress.org Meta team <a href=\"http://wptavern.com/wordpress-plugin-directory-launches-new-design\">redesigned</a> the <a href=\"https://wordpress.org/plugins/\">WordPress plugin directory</a> and added a number of new features. In an effort to iterate on the page&#8217;s layout, the Meta Team has <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/\">published prototypes</a> of a new design for the <a href=\"http://codepen.io/mapk/full/jqxqbo/\">plugin directory&#8217;s home</a> and <a href=\"http://codepen.io/mapk/full/KzGQKv/\">search results pages</a>.</p>\n<p>The prototypes are inspired by <a href=\"https://get.wp.com/\">Get WordPress</a>, a landing page that provides key information about the WordPress project at a glance.</p>\n<p>There are a few things to keep in mind while looking at these prototypes. The first is that plugin information displayed on the page is inaccurate. Second, the Pro and Light classifications are for design purposes only. Third, links at the bottom will point to their corresponding pages.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PluginDirectoryMockup1.png\"><img class=\"size-full wp-image-55007\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PluginDirectoryMockup1.png?resize=1025%2C2753\" alt=\"WordPress Plugin Directory Homepage Protoype\" /></a>WordPress Plugin Directory Homepage Protoype\n<p>Unlike the current design, the prototype displays far less information. Authors, Last Updated, Compatibility, and Active Installs are absent from the homepage view. Initial feedback <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/#comment-8151\">highlights the concern</a> that too much information has been stripped away.</p>\n<p>In response to a comment on the announcement post, Samuel Sidler, <span class=\"st\">Apollo Team Lead at Automattic and contributor to the Meta team</span>, <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/#comment-8154\">explains</a> why he doesn&#8217;t think the information is useful to users.</p>\n<blockquote><p>Author, as you said, is only really useful for insiders. The latter two, meanwhile, are already taken into account in the search results. If a plugin doesn’t have a recent compatible version, it will move down the list. If it’s too old, it won’t get shown at all (which is the case today).</p>\n<p>Active installs is more interesting, but we account for it weighting search results as-is. I actually find it refreshing to <em>not</em> show the active installs as it allows for less-popular plugins to get more downloads. Users will be less likely to click the popular plugins (outside of familiar names) and more likely to find the plugin they actually need.</p></blockquote>\n<p>Another commenter suggests <a href=\"https://profiles.wordpress.org/awakensolutions/\">creating a simple/advanced view. </a>By default, the page could display a simplistic design while giving power users an option for more details.</p>\n<p>&#8220;Just like <a href=\"https://wordpress.org/about/philosophy/\" rel=\"nofollow\">WordPress core</a>, we strive to design for the majority and build features for the 80%,&#8221; Sidler said in response to the comment. &#8220;An &#8216;advanced&#8217; view doesn’t meet that requirement, in my eyes.&#8221;</p>\n<p>The Meta team is iterating quickly and will soon publish a prototype of the plugin details page. If you have feedback on the plugin homepage and search result prototypes, please leave a comment on <a href=\"https://make.wordpress.org/meta/2016/05/19/plugin-directory-prototypes/\">the announcement post</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:10;a:7:{s:5:\"title\";s:94:\"WPTavern: WPWeekly Episode 235 – Interview with James Giroux Envato’s WordPress Evangelist\";s:4:\"guid\";s:44:\"http://wptavern.com?p=55000&preview_id=55000\";s:4:\"link\";s:97:\"http://wptavern.com/wpweekly-episode-235-interview-with-james-giroux-envatos-wordpress-evangelist\";s:11:\"description\";s:1298:\"<p>In this episode, <a href=\"http://marcuscouch.com/\">Marcus Couch</a> and I are joined by <a href=\"https://jamesgiroux.ca/\">James Giroux</a>, Envato&#8217;s WordPress evangelist. We discuss a number of topics including what he&#8217;s accomplished since taking over the position in January, the item support policy change, and author driven pricing.</p>\n<p>We also find out what his favorite part of the job is and what he enjoys most about his role at Envato. Last but not least, we discover what the company is doing to shorten the length of time it takes to get through the review queue.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, June 1st 9:30 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href=\"https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href=\"http://www.wptavern.com/feed/podcast\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href=\"http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #235:</strong><br />\n</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 19 May 2016 19:18:56 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:1298:\"<p>In this episode, <a href=\"http://marcuscouch.com/\">Marcus Couch</a> and I are joined by <a href=\"https://jamesgiroux.ca/\">James Giroux</a>, Envato&#8217;s WordPress evangelist. We discuss a number of topics including what he&#8217;s accomplished since taking over the position in January, the item support policy change, and author driven pricing.</p>\n<p>We also find out what his favorite part of the job is and what he enjoys most about his role at Envato. Last but not least, we discover what the company is doing to shorten the length of time it takes to get through the review queue.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, June 1st 9:30 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href=\"https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href=\"http://www.wptavern.com/feed/podcast\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href=\"http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #235:</strong><br />\n</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:11;a:7:{s:5:\"title\";s:60:\"WPTavern: BuddyPress Launches Style Modules Trial Initiative\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54954\";s:4:\"link\";s:70:\"http://wptavern.com/buddypress-launches-style-modules-trial-initiative\";s:11:\"description\";s:3960:\"<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/customize-posts.jpg\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/customize-posts.jpg?resize=1024%2C583\" alt=\"photo credit: Paintbrush - (license)\" class=\"size-full wp-image-54351\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/93249705@N03/13067171403\">Paintbrush</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nd/2.0/\">(license)</a>\n<p>BuddyPress core developer <a href=\"https://twitter.com/hnla\" target=\"_blank\">Hugo Ashmore</a> announced a new trial initiative this week that aims to create a library of CSS and JavaScript snippets to help users customize their communities. The <a href=\"https://bpdevel.wordpress.com/2016/05/11/buddypress-style-modules/\" target=\"_blank\">Style Modules</a> project will aggregate community-submitted code that enhances BuddyPress components in a plug-and-play manner.</p>\n<p>Developers who want to contribute to the project can submit their modules by creating a ticket on <a href=\"https://buddypress.trac.wordpress.org/newticket\" target=\"_blank\">BP trac</a> and attaching a zip file that includes the CSS/JS files, a readme.md, and a screenshot.</p>\n<p>Users who want to add a module will need to create a /style-modules/ directory and then unzip the module inside it. The next step requires the user to copy functions from the module&#8217;s readme file to their theme&#8217;s functions.php file, a step which provides a significant hurdle for a non-technical BuddyPress community manager.</p>\n<p>&#8220;Initially this is a trial to see whether we get sufficient interest in the concept to continue and develop further, perhaps enhancing the loading process with enqueueing of files based on directory scanning and loading of files as an array but run from the core theme compat class, removing the need for users to copy the loading functions to their functions file,&#8221; Ashmore said.</p>\n<p>The project&#8217;s GitHub repository includes <a href=\"https://github.com/buddypress/style-modules/wiki/Style-Modules-Listings\">an example module</a> that re-styles the members list into a grid layout. Other example ideas Ashmore suggested include a new look for profile entries, a different presentation for the activity posting form, or something as simple as changing the font size for the activity stream.</p>\n<p>The experimental initiative will test the waters to see if the BuddyPress community will chip in to provide enough modules to make this a real library. The support policy stated in the proposal doesn&#8217;t offer much incentive for module authors to submit their work:</p>\n<blockquote><p>Provision of modules and use of them is entirely the discretion of the authors and users, while BP will run some basic checks on the module BP does not guarantee that the modules will work in all given situations or installs, or accept any liability in their use. Support for a module remains the responsibility of the author to ensure the continued effectiveness of the module with updates to themes, WP or BP.</p></blockquote>\n<p>Historically, BuddyPress has struggled to present itself as an easily customizable solution for communities. <a href=\"http://codex.buddypress.org/themes/theme-compatibility-1-7/a-quick-look-at-1-7-theme-compatibility/\" target=\"_blank\">Theme compatibility</a>, introduced in April 2013, made it easier to use BP with any theme, but unless you purchase a theme specifically designed for the plugin, its default output is rather generic and in need of heavy styling.</p>\n<p>The <a href=\"https://bpdevel.wordpress.com/2016/05/11/buddypress-style-modules/\" target=\"_blank\">BuddyPress Style Modules</a> concept is an attempt to make it easier for community managers to enhance BP components with different looks, but the project will need to provide a compelling reason for developers to contribute modules and continue to maintain them.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 19 May 2016 02:34:32 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:3960:\"<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/customize-posts.jpg\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/customize-posts.jpg?resize=1024%2C583\" alt=\"photo credit: Paintbrush - (license)\" class=\"size-full wp-image-54351\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/93249705@N03/13067171403\">Paintbrush</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nd/2.0/\">(license)</a>\n<p>BuddyPress core developer <a href=\"https://twitter.com/hnla\" target=\"_blank\">Hugo Ashmore</a> announced a new trial initiative this week that aims to create a library of CSS and JavaScript snippets to help users customize their communities. The <a href=\"https://bpdevel.wordpress.com/2016/05/11/buddypress-style-modules/\" target=\"_blank\">Style Modules</a> project will aggregate community-submitted code that enhances BuddyPress components in a plug-and-play manner.</p>\n<p>Developers who want to contribute to the project can submit their modules by creating a ticket on <a href=\"https://buddypress.trac.wordpress.org/newticket\" target=\"_blank\">BP trac</a> and attaching a zip file that includes the CSS/JS files, a readme.md, and a screenshot.</p>\n<p>Users who want to add a module will need to create a /style-modules/ directory and then unzip the module inside it. The next step requires the user to copy functions from the module&#8217;s readme file to their theme&#8217;s functions.php file, a step which provides a significant hurdle for a non-technical BuddyPress community manager.</p>\n<p>&#8220;Initially this is a trial to see whether we get sufficient interest in the concept to continue and develop further, perhaps enhancing the loading process with enqueueing of files based on directory scanning and loading of files as an array but run from the core theme compat class, removing the need for users to copy the loading functions to their functions file,&#8221; Ashmore said.</p>\n<p>The project&#8217;s GitHub repository includes <a href=\"https://github.com/buddypress/style-modules/wiki/Style-Modules-Listings\">an example module</a> that re-styles the members list into a grid layout. Other example ideas Ashmore suggested include a new look for profile entries, a different presentation for the activity posting form, or something as simple as changing the font size for the activity stream.</p>\n<p>The experimental initiative will test the waters to see if the BuddyPress community will chip in to provide enough modules to make this a real library. The support policy stated in the proposal doesn&#8217;t offer much incentive for module authors to submit their work:</p>\n<blockquote><p>Provision of modules and use of them is entirely the discretion of the authors and users, while BP will run some basic checks on the module BP does not guarantee that the modules will work in all given situations or installs, or accept any liability in their use. Support for a module remains the responsibility of the author to ensure the continued effectiveness of the module with updates to themes, WP or BP.</p></blockquote>\n<p>Historically, BuddyPress has struggled to present itself as an easily customizable solution for communities. <a href=\"http://codex.buddypress.org/themes/theme-compatibility-1-7/a-quick-look-at-1-7-theme-compatibility/\" target=\"_blank\">Theme compatibility</a>, introduced in April 2013, made it easier to use BP with any theme, but unless you purchase a theme specifically designed for the plugin, its default output is rather generic and in need of heavy styling.</p>\n<p>The <a href=\"https://bpdevel.wordpress.com/2016/05/11/buddypress-style-modules/\" target=\"_blank\">BuddyPress Style Modules</a> concept is an attempt to make it easier for community managers to enhance BP components with different looks, but the project will need to provide a compelling reason for developers to contribute modules and continue to maintain them.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:12;a:7:{s:5:\"title\";s:62:\"WPTavern: The .blog Domain Extension Is Now Open to Registrars\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54971\";s:4:\"link\";s:71:\"http://wptavern.com/the-blog-domain-extension-is-now-open-to-registrars\";s:11:\"description\";s:2083:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg?resize=960%2C521\" alt=\"photo credit: Luis Llerena\" class=\"size-full wp-image-54799\" /></a>photo credit: <a href=\"https://stocksnap.io/photo/3ZHG0XOIT6\">Luis Llerena</a>\n<p>Today marks a moment in internet history, as the very first .blog domain is now operational on WordPress.com. Knock Knock, WHOIS There, a subsidiary of Automattic, launched <a href=\"https://nic.blog/\" target=\"_blank\">Nic.blog</a> today to begin getting registrars to sign up to sell the new TLD.</p>\n<p>Automattic <a href=\"http://wptavern.com/automattic-to-oversee-the-sale-and-registration-of-top-level-blog-domains\" target=\"_blank\">won the rights to oversee the sale and registration of the .blog domain</a> in 2015 via a bidding process that is estimated to have closed around $20 million. The domain extension is so new that Twitter doesn&#8217;t yet support it as a valid link, but Automattic expects to activate 250,000 new names in 2016.</p>\n<p>According to the new nic.blog information site, registrars that sign up to sell .blog domains will be able to participate in an incentive partnership model that rewards a higher volume of sales:</p>\n<blockquote><p>Pricing will be in the standard range for new gTLDs, with premium names available in several tiers. High margins for registrars will be guaranteed by an incentive model, rewarding sales above a certain baseline. Final terms will be published in the coming weeks.</p></blockquote>\n<p>Automattic is opening up the .blog TLD to registrars around the world and companies can sign up on nic.blog to learn more about the requirements. Individuals who are interested in purchasing a .blog domain should review the tentative <a href=\"https://nic.blog/launch-plan/\" target=\"_blank\">launch plan</a> published today. Registration will be open to trademark owners during the Sunrise period starting in August 2016, followed by a Landrush period in October.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 18 May 2016 23:26:09 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2083:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg?resize=960%2C521\" alt=\"photo credit: Luis Llerena\" class=\"size-full wp-image-54799\" /></a>photo credit: <a href=\"https://stocksnap.io/photo/3ZHG0XOIT6\">Luis Llerena</a>\n<p>Today marks a moment in internet history, as the very first .blog domain is now operational on WordPress.com. Knock Knock, WHOIS There, a subsidiary of Automattic, launched <a href=\"https://nic.blog/\" target=\"_blank\">Nic.blog</a> today to begin getting registrars to sign up to sell the new TLD.</p>\n<p>Automattic <a href=\"http://wptavern.com/automattic-to-oversee-the-sale-and-registration-of-top-level-blog-domains\" target=\"_blank\">won the rights to oversee the sale and registration of the .blog domain</a> in 2015 via a bidding process that is estimated to have closed around $20 million. The domain extension is so new that Twitter doesn&#8217;t yet support it as a valid link, but Automattic expects to activate 250,000 new names in 2016.</p>\n<p>According to the new nic.blog information site, registrars that sign up to sell .blog domains will be able to participate in an incentive partnership model that rewards a higher volume of sales:</p>\n<blockquote><p>Pricing will be in the standard range for new gTLDs, with premium names available in several tiers. High margins for registrars will be guaranteed by an incentive model, rewarding sales above a certain baseline. Final terms will be published in the coming weeks.</p></blockquote>\n<p>Automattic is opening up the .blog TLD to registrars around the world and companies can sign up on nic.blog to learn more about the requirements. Individuals who are interested in purchasing a .blog domain should review the tentative <a href=\"https://nic.blog/launch-plan/\" target=\"_blank\">launch plan</a> published today. Registration will be open to trademark owners during the Sunrise period starting in August 2016, followed by a Landrush period in October.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:13;a:7:{s:5:\"title\";s:87:\"WPTavern: After Eight Years, Thematic Theme’s Lead Developers Discontinue the Project\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54967\";s:4:\"link\";s:93:\"http://wptavern.com/after-eight-years-thematic-themes-lead-developers-discontinue-the-project\";s:11:\"description\";s:3812:\"<p>Gene Robinson, lead developer of the Thematic WordPress theme, has <a href=\"http://thematictheme.com/2016/05/15/thematic-retrospective/\">announced</a> that the project will no longer be developed. Thematic <a href=\"https://wordpress.org/themes/thematic/\">was last updated</a> in 2013 and is actively installed on more than 4K sites. Users are advised to migrate to a different theme as updates will no longer be released. As WordPress core evolves, sites using Thematic may develop incompatibilities.</p>\n<h2>Continuing The Legacy with a Different Name</h2>\n<p>Although development on Thematic is discontinuing, Robinson has forked the project and renamed it to <a href=\"http://d.eciduo.us\">Deciduous. </a>The project picks up where Thematic leaves off. Those interested in continuing development can <a href=\"https://github.com/emhr/Deciduous\">follow it on GitHub</a> where pull requests are welcomed. Robinson is also seeking links to other projects that are derivative of Thematic.</p>\n<h2>Where to Get Support for Thematic</h2>\n<p>Users who need support are advised to post on the <a href=\"https://wordpress.org/support/theme/thematic\">WordPress.org support forums</a> for the Thematic theme, &#8220;The support forums on the Thematic website are shutting down due to the lack of community involvement, moderation, and developer feedback,&#8221; Robinson said. &#8220;Hopefully the greater WordPress support community will be able to help you find a resolution.&#8221;</p>\n<h2>A Look Back</h2>\n<p>The years 2008-2009 is an interesting time frame in WordPress&#8217; history. A number of commercial theme and plugin companies, WordPress-centric sites, and projects were launched. Among these was the <a href=\"https://web.archive.org/web/20080611165821/http://themeshaper.com/thematic-for-wordpress/\">Thematic theme</a> by Ian Stewart, theme Wrangler for Automattic. Thematic was more than just a theme, it was an opportunity for Stewart to learn how WordPress&#8217; theme system works.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/ThematicThemePreview.png\"><img class=\"size-full wp-image-54981\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/ThematicThemePreview.png?resize=951%2C740\" alt=\"Thematic Theme Preview from WordPress.org\" /></a>Preview of Thematic from WordPress.org\n<p>He regularly shared his knowledge with the community through <a href=\"https://themeshaper.com/\">ThemeShaper.com</a>, a site now owned by Automattic that features contributions from other members of the theme team. It was the wild west of theme development in 2008 and any person who regularly shared theme development techniques became an influential member of the community.</p>\n<p>Two years after launching Thematic, Stewart <a href=\"https://themeshaper.com/2010/03/04/ian-stewart-joined-automattic/\">joined Automattic</a> as a theme wrangler.</p>\n<blockquote><p>What can I say besides awesome, awesome, awesome? The enormous opportunity for learning and improvement; all the super-talented, friendly people; the chance to work on so many really, really cool projects—it’s almost unbelievable. This is a dream job for me.</p></blockquote>\n<p>The hiring allowed him to make available all of his commercial child themes built on the Thematic framework available free of charge to the community.</p>\n<h2>Did You Learn From Thematic?</h2>\n<p>It&#8217;s bittersweet and slightly nostalgic to see the theme come to an end. When I launched the Tavern in 2009, I regularly linked to tutorials and articles published by Stewart. I&#8217;m almost certain Thematic and its creator helped out a number of budding theme developers between 2008-2011. Let us know in the comments if you used Thematic for any projects or what you learned from its code.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 18 May 2016 20:45:48 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:3812:\"<p>Gene Robinson, lead developer of the Thematic WordPress theme, has <a href=\"http://thematictheme.com/2016/05/15/thematic-retrospective/\">announced</a> that the project will no longer be developed. Thematic <a href=\"https://wordpress.org/themes/thematic/\">was last updated</a> in 2013 and is actively installed on more than 4K sites. Users are advised to migrate to a different theme as updates will no longer be released. As WordPress core evolves, sites using Thematic may develop incompatibilities.</p>\n<h2>Continuing The Legacy with a Different Name</h2>\n<p>Although development on Thematic is discontinuing, Robinson has forked the project and renamed it to <a href=\"http://d.eciduo.us\">Deciduous. </a>The project picks up where Thematic leaves off. Those interested in continuing development can <a href=\"https://github.com/emhr/Deciduous\">follow it on GitHub</a> where pull requests are welcomed. Robinson is also seeking links to other projects that are derivative of Thematic.</p>\n<h2>Where to Get Support for Thematic</h2>\n<p>Users who need support are advised to post on the <a href=\"https://wordpress.org/support/theme/thematic\">WordPress.org support forums</a> for the Thematic theme, &#8220;The support forums on the Thematic website are shutting down due to the lack of community involvement, moderation, and developer feedback,&#8221; Robinson said. &#8220;Hopefully the greater WordPress support community will be able to help you find a resolution.&#8221;</p>\n<h2>A Look Back</h2>\n<p>The years 2008-2009 is an interesting time frame in WordPress&#8217; history. A number of commercial theme and plugin companies, WordPress-centric sites, and projects were launched. Among these was the <a href=\"https://web.archive.org/web/20080611165821/http://themeshaper.com/thematic-for-wordpress/\">Thematic theme</a> by Ian Stewart, theme Wrangler for Automattic. Thematic was more than just a theme, it was an opportunity for Stewart to learn how WordPress&#8217; theme system works.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/ThematicThemePreview.png\"><img class=\"size-full wp-image-54981\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/ThematicThemePreview.png?resize=951%2C740\" alt=\"Thematic Theme Preview from WordPress.org\" /></a>Preview of Thematic from WordPress.org\n<p>He regularly shared his knowledge with the community through <a href=\"https://themeshaper.com/\">ThemeShaper.com</a>, a site now owned by Automattic that features contributions from other members of the theme team. It was the wild west of theme development in 2008 and any person who regularly shared theme development techniques became an influential member of the community.</p>\n<p>Two years after launching Thematic, Stewart <a href=\"https://themeshaper.com/2010/03/04/ian-stewart-joined-automattic/\">joined Automattic</a> as a theme wrangler.</p>\n<blockquote><p>What can I say besides awesome, awesome, awesome? The enormous opportunity for learning and improvement; all the super-talented, friendly people; the chance to work on so many really, really cool projects—it’s almost unbelievable. This is a dream job for me.</p></blockquote>\n<p>The hiring allowed him to make available all of his commercial child themes built on the Thematic framework available free of charge to the community.</p>\n<h2>Did You Learn From Thematic?</h2>\n<p>It&#8217;s bittersweet and slightly nostalgic to see the theme come to an end. When I launched the Tavern in 2009, I regularly linked to tutorials and articles published by Stewart. I&#8217;m almost certain Thematic and its creator helped out a number of budding theme developers between 2008-2011. Let us know in the comments if you used Thematic for any projects or what you learned from its code.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:14;a:7:{s:5:\"title\";s:58:\"Post Status: WordPress as a Headless CMS — Draft podcast\";s:4:\"guid\";s:31:\"https://poststatus.com/?p=24518\";s:4:\"link\";s:60:\"https://poststatus.com/wordpress-headless-cms-draft-podcast/\";s:11:\"description\";s:2870:\"<p>Welcome to the Post Status <a href=\"https://poststatus.com/category/draft\">Draft podcast</a>, which you can find <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">on iTunes</a>, <a href=\"https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast\">Google Play</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, and <a href=\"http://simplecast.fm/podcasts/1061/rss\">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle &#8212; the CTO of Human Made &#8212; and Brian Krogsgard.</p>\n<p><span>Joe and Brian discuss WordPress as a Headless CMS. They talk about what a Headless CMS is, WordPress’s strengths and weaknesses as a Headless CMS, popular frameworks to utilize, and offer up example websites to check out.</span></p>\n<p><a href=\"https://audio.simplecast.com/37861.mp3\">https://audio.simplecast.com/37861.mp3</a><br />\n<a href=\"http://audio.simplecast.com/37861.mp3\">Direct Download</a></p>\n<h3>Examples</h3>\n<ul>\n<li><a href=\"https://www.guggenheim.org/\">The Guggenheim</a></li>\n<li><a href=\"https://adayofrest.hm/boston-2016/\">A Day of Rest Boston</a></li>\n<li><a href=\"https://ustwo.com/\">ustwo</a></li>\n<li><a href=\"http://skaled.com/\">Skaled</a></li>\n<li><a href=\"http://tri.be/\">Modern Tribe</a></li>\n</ul>\n<h3>Links</h3>\n<ul>\n<li><a href=\"https://angularjs.org/\">Angular</a></li>\n<li><a href=\"https://facebook.github.io/react/\">React</a></li>\n<li><a href=\"http://blog.scalac.io/2016/02/16/react-vs-angular-2.html\">React vs Angular 2</a></li>\n<li><a href=\"https://getmoxied.net/lean/\">Lean, an Agular for WordPress framework</a></li>\n<li><a href=\"https://pantheon.io/decoupled-cms\">Decoupled CMS</a></li>\n<li><a href=\"https://css-tricks.com/what-is-a-headless-cms/\">What is a Headless CMS?</a></li>\n<li><a href=\"http://petya.in/we-need-to-talk-about-the-rest-api-the-non-developer-guide-to-the-future-of-wordpress/\">We Need to Talk about the REST API</a></li>\n<li><a href=\"https://make.wordpress.org/core/2016/05/16/rest-api-authentication-broker/\">Introducing the REST API Authentication Broker</a></li>\n<li><a href=\"https://hmn.md/2016/01/14/introducing-our-wordpress-rest-api-white-paper/\">Human Made&#8217;s REST API White Paper</a></li>\n</ul>\n<h3>Sponsor</h3>\n<p><span>Today’s show is sponsored by </span><a href=\"http://optinmonster.com\"><span>OptinMonster</span></a><span>. OptinMonster allows you to convert visitors into subscribers. You can easily create &amp; A/B test beautiful lead capture forms without a developer. They recently released </span><a href=\"http://optinmonster.com/introducing-optinmonster-3-0-taking-your-conversion-optimization-to-the-next-level/\"><span>OptinMonster 3.0</span></a><span>, with an all new builder interface and other great features.</span></p>\";s:7:\"pubdate\";s:31:\"Wed, 18 May 2016 17:47:56 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Katie Richards\";}s:7:\"summary\";s:2870:\"<p>Welcome to the Post Status <a href=\"https://poststatus.com/category/draft\">Draft podcast</a>, which you can find <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">on iTunes</a>, <a href=\"https://play.google.com/music/m/Ih5egfxskgcec4qadr3f4zfpzzm?t=Post_Status__Draft_WordPress_Podcast\">Google Play</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, and <a href=\"http://simplecast.fm/podcasts/1061/rss\">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle &#8212; the CTO of Human Made &#8212; and Brian Krogsgard.</p>\n<p><span>Joe and Brian discuss WordPress as a Headless CMS. They talk about what a Headless CMS is, WordPress’s strengths and weaknesses as a Headless CMS, popular frameworks to utilize, and offer up example websites to check out.</span></p>\n<p><a href=\"https://audio.simplecast.com/37861.mp3\">https://audio.simplecast.com/37861.mp3</a><br />\n<a href=\"http://audio.simplecast.com/37861.mp3\">Direct Download</a></p>\n<h3>Examples</h3>\n<ul>\n<li><a href=\"https://www.guggenheim.org/\">The Guggenheim</a></li>\n<li><a href=\"https://adayofrest.hm/boston-2016/\">A Day of Rest Boston</a></li>\n<li><a href=\"https://ustwo.com/\">ustwo</a></li>\n<li><a href=\"http://skaled.com/\">Skaled</a></li>\n<li><a href=\"http://tri.be/\">Modern Tribe</a></li>\n</ul>\n<h3>Links</h3>\n<ul>\n<li><a href=\"https://angularjs.org/\">Angular</a></li>\n<li><a href=\"https://facebook.github.io/react/\">React</a></li>\n<li><a href=\"http://blog.scalac.io/2016/02/16/react-vs-angular-2.html\">React vs Angular 2</a></li>\n<li><a href=\"https://getmoxied.net/lean/\">Lean, an Agular for WordPress framework</a></li>\n<li><a href=\"https://pantheon.io/decoupled-cms\">Decoupled CMS</a></li>\n<li><a href=\"https://css-tricks.com/what-is-a-headless-cms/\">What is a Headless CMS?</a></li>\n<li><a href=\"http://petya.in/we-need-to-talk-about-the-rest-api-the-non-developer-guide-to-the-future-of-wordpress/\">We Need to Talk about the REST API</a></li>\n<li><a href=\"https://make.wordpress.org/core/2016/05/16/rest-api-authentication-broker/\">Introducing the REST API Authentication Broker</a></li>\n<li><a href=\"https://hmn.md/2016/01/14/introducing-our-wordpress-rest-api-white-paper/\">Human Made&#8217;s REST API White Paper</a></li>\n</ul>\n<h3>Sponsor</h3>\n<p><span>Today’s show is sponsored by </span><a href=\"http://optinmonster.com\"><span>OptinMonster</span></a><span>. OptinMonster allows you to convert visitors into subscribers. You can easily create &amp; A/B test beautiful lead capture forms without a developer. They recently released </span><a href=\"http://optinmonster.com/introducing-optinmonster-3-0-taking-your-conversion-optimization-to-the-next-level/\"><span>OptinMonster 3.0</span></a><span>, with an all new builder interface and other great features.</span></p>\";}i:15;a:7:{s:5:\"title\";s:87:\"WPTavern: Take Granular Control of WordPress’ Update System with Easy Updates Manager\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54952\";s:4:\"link\";s:94:\"http://wptavern.com/take-granular-control-of-wordpress-update-system-with-easy-updates-manager\";s:11:\"description\";s:3933:\"<p>When <a href=\"https://wordpress.org/news/2013/10/basie/\">WordPress 3.7 &#8220;Basie&#8221;</a> was released in 2013, it brought automatic updates to the masses. By default, WordPress automatically updates to point releases. Using <a href=\"https://codex.wordpress.org/Configuring_Automatic_Background_Updates\">additional constants</a> within wp-config.php, you can configure WordPress to automatically update themes, plugins, and major releases.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerFeaturedImage.png\"><img class=\"aligncenter size-full wp-image-54958\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerFeaturedImage.png?resize=650%2C207\" alt=\"Easy Update Manager Featured Image\" /></a></p>\n<p>If you want granular control over the WordPress update system without touching code, check out <a href=\"https://wordpress.org/plugins/stops-core-theme-and-plugin-updates/\">Easy Updates Manager</a>. Easy Updates Manager is a free plugin that&#8217;s active on more than 70k sites. It&#8217;s maintained by <a href=\"https://profiles.wordpress.org/kidsguide/\">Matthew</a>, <a href=\"https://profiles.wordpress.org/ronalfy/\">Ronald Huereca</a>, <a href=\"https://profiles.wordpress.org/roary86/\">Roary Tubbs</a>, and <a href=\"https://profiles.wordpress.org/bigwing/\">BigWing Interactive</a>.</p>\n<h2>Countless Number of Configurations Available</h2>\n<p>Once activated, you&#8217;ll find the options page by browsing to Dashboard &gt; Update Options. There are two different interfaces for configuring updates. The first includes a number of toggle switches that disable/enable updates. The second is a traditional screen with radial buttons.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerDashboard.png\"><img class=\"size-full wp-image-54959\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerDashboard.png?resize=1025%2C432\" alt=\"Easy Update Manager Dashboard\" /></a>Easy Updates Manager Dashboard\n<p>Traditional settings page for Easy Updates Manager.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerGeneralSettings.png\"><img class=\"size-full wp-image-54960\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerGeneralSettings.png?resize=566%2C480\" alt=\"Easy Update Manager General Settings\" /></a>Easy Updates Manager General Settings\n<p>One of the highlights of Easy Updates Manager is the ability to enable automatic updates for individual themes and plugins. It&#8217;s a convenient way to update themes and plugins that rarely cause issues. There&#8217;s also a built-in logging feature that when enabled creates a new table in the database. It logs the username, update type, version, action, status, and date.</p>\n<p>Logging is listed as a beta feature and should be used at your own risk. It also may not work with all commercial themes and plugins. Here&#8217;s what the log looks like after I updated three plugins.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerLogs.png\"><img class=\"size-full wp-image-54961\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerLogs.png?resize=1025%2C350\" alt=\"Easy Update Management Log\" /></a>Easy Updates Management Log\n<p>Easy Updates Manager also includes the ability to exclude users from manipulating the plugin&#8217;s settings. The plugin contains additional features that I encourage you to explore by using it on a test site.</p>\n<p>Thanks to the number of options available, users have a countless number of update configurations to choose from. I tested the plugin on WordPress 4.6 alpha and it works as expected. You can <a href=\"https://wordpress.org/plugins/stops-core-theme-and-plugin-updates/\">download it for free</a> from the WordPress plugin directory.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 18 May 2016 07:17:01 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:3933:\"<p>When <a href=\"https://wordpress.org/news/2013/10/basie/\">WordPress 3.7 &#8220;Basie&#8221;</a> was released in 2013, it brought automatic updates to the masses. By default, WordPress automatically updates to point releases. Using <a href=\"https://codex.wordpress.org/Configuring_Automatic_Background_Updates\">additional constants</a> within wp-config.php, you can configure WordPress to automatically update themes, plugins, and major releases.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerFeaturedImage.png\"><img class=\"aligncenter size-full wp-image-54958\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerFeaturedImage.png?resize=650%2C207\" alt=\"Easy Update Manager Featured Image\" /></a></p>\n<p>If you want granular control over the WordPress update system without touching code, check out <a href=\"https://wordpress.org/plugins/stops-core-theme-and-plugin-updates/\">Easy Updates Manager</a>. Easy Updates Manager is a free plugin that&#8217;s active on more than 70k sites. It&#8217;s maintained by <a href=\"https://profiles.wordpress.org/kidsguide/\">Matthew</a>, <a href=\"https://profiles.wordpress.org/ronalfy/\">Ronald Huereca</a>, <a href=\"https://profiles.wordpress.org/roary86/\">Roary Tubbs</a>, and <a href=\"https://profiles.wordpress.org/bigwing/\">BigWing Interactive</a>.</p>\n<h2>Countless Number of Configurations Available</h2>\n<p>Once activated, you&#8217;ll find the options page by browsing to Dashboard &gt; Update Options. There are two different interfaces for configuring updates. The first includes a number of toggle switches that disable/enable updates. The second is a traditional screen with radial buttons.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerDashboard.png\"><img class=\"size-full wp-image-54959\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerDashboard.png?resize=1025%2C432\" alt=\"Easy Update Manager Dashboard\" /></a>Easy Updates Manager Dashboard\n<p>Traditional settings page for Easy Updates Manager.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerGeneralSettings.png\"><img class=\"size-full wp-image-54960\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerGeneralSettings.png?resize=566%2C480\" alt=\"Easy Update Manager General Settings\" /></a>Easy Updates Manager General Settings\n<p>One of the highlights of Easy Updates Manager is the ability to enable automatic updates for individual themes and plugins. It&#8217;s a convenient way to update themes and plugins that rarely cause issues. There&#8217;s also a built-in logging feature that when enabled creates a new table in the database. It logs the username, update type, version, action, status, and date.</p>\n<p>Logging is listed as a beta feature and should be used at your own risk. It also may not work with all commercial themes and plugins. Here&#8217;s what the log looks like after I updated three plugins.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerLogs.png\"><img class=\"size-full wp-image-54961\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/EasyUpdateManagerLogs.png?resize=1025%2C350\" alt=\"Easy Update Management Log\" /></a>Easy Updates Management Log\n<p>Easy Updates Manager also includes the ability to exclude users from manipulating the plugin&#8217;s settings. The plugin contains additional features that I encourage you to explore by using it on a test site.</p>\n<p>Thanks to the number of options available, users have a countless number of update configurations to choose from. I tested the plugin on WordPress 4.6 alpha and it works as expected. You can <a href=\"https://wordpress.org/plugins/stops-core-theme-and-plugin-updates/\">download it for free</a> from the WordPress plugin directory.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:16;a:7:{s:5:\"title\";s:91:\"WPTavern: WordPress 4.6 Improves the Accessibility of the Tag and Category Management Pages\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54910\";s:4:\"link\";s:101:\"http://wptavern.com/wordpress-4-6-improves-the-accessibility-of-the-tag-and-category-management-pages\";s:11:\"description\";s:2775:\"<p>Among the improvements coming in WordPress 4.6 are <a href=\"https://make.wordpress.org/core/2016/05/16/categories-and-tags-screens-changes/\">accessibility enhancements</a> to the Category and Tag management pages. The flow of each page has been changed so that the visual order of elements match the tab order. This allows those who navigate with keyboards to access the Add New Tag or Add New Category area first.</p>\n<p>Andrea Fercia, WordPress core committer and a member of the accessibility team, explains why the changes matter, &#8220;For accessibility, the visual order should always match the tab order. The main functionality in a page should just be the first thing in the source markup and other parts of the user interface should never be &#8216;skipped&#8217;.&#8221;</p>\n<p>The following image shows the tab order of elements on the Tag management screen in WordPress 4.5. In order to reach the Add New Tag section, you need to tab through a number of checkboxes, each tag in the tag cloud, and various quick edit links. This is a time-consuming and frustrating process.</p>\n<a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress45TagManagementPage.png\"><img class=\"size-full wp-image-54944\" src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress45TagManagementPage.png?resize=1025%2C806\" alt=\"WordPress 4.5 Tag Management Element Order\" /></a>WordPress 4.5 Tag Management Element Order\n<p>In WordPress 4.6, the Add New Tag section is the first visual element as well as the first section accessed when pressing the tab key.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress46TagManagementScreen.png\"><img class=\"size-full wp-image-54945\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress46TagManagementScreen.png?resize=1025%2C792\" alt=\"WordPress 4.6 Tag Management Screen\" /></a>WordPress 4.6 Tag Management Screen\n<p>The new flow is more logical and provides consistency between the tag and category management screens, &#8220;From an accessibility point of view, the content structure and organization will be easier to understand and navigate,&#8221; Fercia said.</p>\n<p>WordPress theme and plugin authors who have added custom functionality to these screens are advised to double-check their code against the bleeding edge version of WordPress 4.6. There&#8217;s also an <a href=\"https://core.trac.wordpress.org/ticket/35664\">in-depth ticket</a> where developers and users can see how the team reached a consensus to implement the changes. If you have any questions or concerns please leave a comment on the <a href=\"https://make.wordpress.org/core/2016/05/16/categories-and-tags-screens-changes/\">announcement post</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Tue, 17 May 2016 19:30:29 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:2775:\"<p>Among the improvements coming in WordPress 4.6 are <a href=\"https://make.wordpress.org/core/2016/05/16/categories-and-tags-screens-changes/\">accessibility enhancements</a> to the Category and Tag management pages. The flow of each page has been changed so that the visual order of elements match the tab order. This allows those who navigate with keyboards to access the Add New Tag or Add New Category area first.</p>\n<p>Andrea Fercia, WordPress core committer and a member of the accessibility team, explains why the changes matter, &#8220;For accessibility, the visual order should always match the tab order. The main functionality in a page should just be the first thing in the source markup and other parts of the user interface should never be &#8216;skipped&#8217;.&#8221;</p>\n<p>The following image shows the tab order of elements on the Tag management screen in WordPress 4.5. In order to reach the Add New Tag section, you need to tab through a number of checkboxes, each tag in the tag cloud, and various quick edit links. This is a time-consuming and frustrating process.</p>\n<a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress45TagManagementPage.png\"><img class=\"size-full wp-image-54944\" src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress45TagManagementPage.png?resize=1025%2C806\" alt=\"WordPress 4.5 Tag Management Element Order\" /></a>WordPress 4.5 Tag Management Element Order\n<p>In WordPress 4.6, the Add New Tag section is the first visual element as well as the first section accessed when pressing the tab key.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress46TagManagementScreen.png\"><img class=\"size-full wp-image-54945\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WordPress46TagManagementScreen.png?resize=1025%2C792\" alt=\"WordPress 4.6 Tag Management Screen\" /></a>WordPress 4.6 Tag Management Screen\n<p>The new flow is more logical and provides consistency between the tag and category management screens, &#8220;From an accessibility point of view, the content structure and organization will be easier to understand and navigate,&#8221; Fercia said.</p>\n<p>WordPress theme and plugin authors who have added custom functionality to these screens are advised to double-check their code against the bleeding edge version of WordPress 4.6. There&#8217;s also an <a href=\"https://core.trac.wordpress.org/ticket/35664\">in-depth ticket</a> where developers and users can see how the team reached a consensus to implement the changes. If you have any questions or concerns please leave a comment on the <a href=\"https://make.wordpress.org/core/2016/05/16/categories-and-tags-screens-changes/\">announcement post</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:17;a:7:{s:5:\"title\";s:75:\"WPTavern: New Plugin Uses BuddyPress Email API to Send bbPress Forum Emails\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54863\";s:4:\"link\";s:85:\"http://wptavern.com/new-plugin-uses-buddypress-email-api-to-send-bbpress-forum-emails\";s:11:\"description\";s:3011:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-bbpress.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-bbpress.jpg?resize=1025%2C493\" alt=\"buddypress-bbpress\" class=\"aligncenter size-full wp-image-30982\" /></a></p>\n<p><a href=\"http://wptavern.com/buddypress-2-5-0-released-features-customizable-emails-and-support-for-emoji\" target=\"_blank\">BuddyPress 2.5</a>, released in March, introduced customizable emails via a new <a href=\"http://wptavern.com/buddypress-2-5-will-add-customizable-emails-via-a-new-bp-email-api\" target=\"_blank\">BP Email API</a>. This new feature allows community managers to easily edit BuddyPress-generated emails in the admin and make design changes in the customizer.</p>\n<p>It didn&#8217;t take long for developers to think of bringing this same customizability to bbPress emails. <a href=\"https://profiles.wordpress.org/thebrandonallen/\" target=\"_blank\">Brandon Allen</a> has just released <a href=\"https://wordpress.org/plugins/bp-emails-for-bbp/\" target=\"_blank\">BP Emails for BBP</a>, a plugin that sends forum and topic subscription emails using the new BP Email API.</p>\n<p>Once installed, administrators will find templates for new forum topics and topic replies under the same Emails menu item with the 16 customizable BuddyPress core emails.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/buddypress-bbpress-emails.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/buddypress-bbpress-emails.png?resize=1025%2C305\" alt=\"buddypress-bbpress-emails\" class=\"aligncenter size-full wp-image-54878\" /></a></p>\n<p>Allen noted that the plugin sends emails differently than bbPress, which puts every subscriber email in the BCC field and sends one email. Instead, it sends a separate email to each subscriber, which Allen said may improve deliverability given that some email providers look unfavorably on emails with large BCC fields.</p>\n<p>I tested the plugin and found that it works as advertised for customizing and sending bbPress emails. There are no settings to configure. It simply adds the same functionality that users now expect from BuddyPress core emails with all the same customization options.</p>\n<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/bbpress-subscription-email.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/bbpress-subscription-email.png?resize=1025%2C500\" alt=\"bbpress-subscription-email\" class=\"aligncenter size-full wp-image-54929\" /></a></p>\n<p><a href=\"https://wordpress.org/plugins/bp-emails-for-bbp/\" target=\"_blank\">BP Emails for BBP</a> is available on WordPress.org. It does not work with bbPress alone but requires both bbPress 2.5+ and BuddyPress 2.5+ to be active. With the help of this plugin, a community manager can brand all the email communications generated by the site so that the design and wording is consistent across both plugins.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Tue, 17 May 2016 05:32:44 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:3011:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-bbpress.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-bbpress.jpg?resize=1025%2C493\" alt=\"buddypress-bbpress\" class=\"aligncenter size-full wp-image-30982\" /></a></p>\n<p><a href=\"http://wptavern.com/buddypress-2-5-0-released-features-customizable-emails-and-support-for-emoji\" target=\"_blank\">BuddyPress 2.5</a>, released in March, introduced customizable emails via a new <a href=\"http://wptavern.com/buddypress-2-5-will-add-customizable-emails-via-a-new-bp-email-api\" target=\"_blank\">BP Email API</a>. This new feature allows community managers to easily edit BuddyPress-generated emails in the admin and make design changes in the customizer.</p>\n<p>It didn&#8217;t take long for developers to think of bringing this same customizability to bbPress emails. <a href=\"https://profiles.wordpress.org/thebrandonallen/\" target=\"_blank\">Brandon Allen</a> has just released <a href=\"https://wordpress.org/plugins/bp-emails-for-bbp/\" target=\"_blank\">BP Emails for BBP</a>, a plugin that sends forum and topic subscription emails using the new BP Email API.</p>\n<p>Once installed, administrators will find templates for new forum topics and topic replies under the same Emails menu item with the 16 customizable BuddyPress core emails.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/buddypress-bbpress-emails.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/buddypress-bbpress-emails.png?resize=1025%2C305\" alt=\"buddypress-bbpress-emails\" class=\"aligncenter size-full wp-image-54878\" /></a></p>\n<p>Allen noted that the plugin sends emails differently than bbPress, which puts every subscriber email in the BCC field and sends one email. Instead, it sends a separate email to each subscriber, which Allen said may improve deliverability given that some email providers look unfavorably on emails with large BCC fields.</p>\n<p>I tested the plugin and found that it works as advertised for customizing and sending bbPress emails. There are no settings to configure. It simply adds the same functionality that users now expect from BuddyPress core emails with all the same customization options.</p>\n<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/bbpress-subscription-email.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/bbpress-subscription-email.png?resize=1025%2C500\" alt=\"bbpress-subscription-email\" class=\"aligncenter size-full wp-image-54929\" /></a></p>\n<p><a href=\"https://wordpress.org/plugins/bp-emails-for-bbp/\" target=\"_blank\">BP Emails for BBP</a> is available on WordPress.org. It does not work with bbPress alone but requires both bbPress 2.5+ and BuddyPress 2.5+ to be active. With the help of this plugin, a community manager can brand all the email communications generated by the site so that the design and wording is consistent across both plugins.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:18;a:7:{s:5:\"title\";s:60:\"WPTavern: BuddyPress 2.6 to Introduce New API for Navigation\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54803\";s:4:\"link\";s:70:\"http://wptavern.com/buddypress-2-6-to-introduce-new-api-for-navigation\";s:11:\"description\";s:2401:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-logo-blue.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-logo-blue.png?resize=839%2C398\" alt=\"buddypress-logo-blue\" class=\"aligncenter size-full wp-image-30655\" /></a></p>\n<p>In an exceptionally well-documented <a href=\"https://buddypress.trac.wordpress.org/changeset/10745/\" target=\"_blank\">commit message</a>, BuddyPress lead developer Boone Gorges introduced a new API to manage single item navigation, thanks to contributions from core developers Mathieu Viet and Raymond Hoh. Gorges summarized the changes to how BuddyPress will handle navigation in the upcoming 2.6 release:</p>\n<blockquote><p>The new BP_Core_Nav overhauls the way that BuddyPress registers, stores, and renders navigation items. Navigations are now component-specific, eliminating the potential for confusion and conflict between navigation items with similar names in different components, and opening the possibility of generating navs for separate objects of the same type on a single pageload.</p></blockquote>\n<p>The previous navigation system used bp_nav and bp_options_nav, global properties that managed nav and subnav across all of BuddyPress&#8217; components. Developers had a difficult time extending navigation and sometimes ended up stepping on each other&#8217;s toes when adding similar navigation items.</p>\n<p>&#8220;The new system eliminates most of these problems, by removing direct access to the underlying navigation data, while providing a full-fledged API for accessing and modifying that data,&#8221; Gorges said.</p>\n<p>Although the new API ensures backward compatibility with the legacy bp_nav and bp_options_nav, plugin developers whose extensions depend on these methods will want to update their code. With the exception of certain configurations running PHP 5.2.x, most plugins should work the same as before.</p>\n<p>However, Gorges&#8217; <a href=\"https://buddypress.trac.wordpress.org/changeset/10745/\" target=\"_blank\">commit message</a> details a handful of small ways that the new API may break backward compatibility in a few rare instances. BuddyPress plugin developers will want to review these ahead of the upcoming 2.6 release. Beta 1 is just one week away from release on May 25 and the official release is targeted for June 15.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Tue, 17 May 2016 05:06:43 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2401:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-logo-blue.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2014/09/buddypress-logo-blue.png?resize=839%2C398\" alt=\"buddypress-logo-blue\" class=\"aligncenter size-full wp-image-30655\" /></a></p>\n<p>In an exceptionally well-documented <a href=\"https://buddypress.trac.wordpress.org/changeset/10745/\" target=\"_blank\">commit message</a>, BuddyPress lead developer Boone Gorges introduced a new API to manage single item navigation, thanks to contributions from core developers Mathieu Viet and Raymond Hoh. Gorges summarized the changes to how BuddyPress will handle navigation in the upcoming 2.6 release:</p>\n<blockquote><p>The new BP_Core_Nav overhauls the way that BuddyPress registers, stores, and renders navigation items. Navigations are now component-specific, eliminating the potential for confusion and conflict between navigation items with similar names in different components, and opening the possibility of generating navs for separate objects of the same type on a single pageload.</p></blockquote>\n<p>The previous navigation system used bp_nav and bp_options_nav, global properties that managed nav and subnav across all of BuddyPress&#8217; components. Developers had a difficult time extending navigation and sometimes ended up stepping on each other&#8217;s toes when adding similar navigation items.</p>\n<p>&#8220;The new system eliminates most of these problems, by removing direct access to the underlying navigation data, while providing a full-fledged API for accessing and modifying that data,&#8221; Gorges said.</p>\n<p>Although the new API ensures backward compatibility with the legacy bp_nav and bp_options_nav, plugin developers whose extensions depend on these methods will want to update their code. With the exception of certain configurations running PHP 5.2.x, most plugins should work the same as before.</p>\n<p>However, Gorges&#8217; <a href=\"https://buddypress.trac.wordpress.org/changeset/10745/\" target=\"_blank\">commit message</a> details a handful of small ways that the new API may break backward compatibility in a few rare instances. BuddyPress plugin developers will want to review these ahead of the upcoming 2.6 release. Beta 1 is just one week away from release on May 25 and the official release is targeted for June 15.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:19;a:7:{s:5:\"title\";s:62:\"WPTavern: Wes Bos Launches Free React.js + Redux Online Course\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54903\";s:4:\"link\";s:70:\"http://wptavern.com/wes-bos-launches-free-react-js-redux-online-course\";s:11:\"description\";s:3193:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/react-redux-course.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/react-redux-course.png?resize=1025%2C465\" alt=\"react-redux-course\" class=\"aligncenter size-full wp-image-54916\" /></a></p>\n<p><a href=\"http://wesbos.com/\" target=\"_blank\">Wes Bos</a>, a developer and educator known for his high quality video tutorials, has just launched a free online course for building JavaScript apps with <a href=\"https://facebook.github.io/react/\" target=\"_blank\">React.js</a> and <a href=\"http://redux.js.org/\" target=\"_blank\">Redux</a>. The 2.5 hour <a href=\"https://learnredux.com/\" target=\"_blank\">Learn Redux</a> course includes 20 videos that guide developers through building an example &#8216;Reduxstagram&#8217; app to present the core ideas behind Redux.</p>\n<p>To get the most out of Learn Redux, students should have a decent foundation of React and ES6. Bos recommends those who are not comfortable with React to start with his <a href=\"https://reactforbeginners.com/\" target=\"_blank\">React for Beginners</a> course.</p>\n<p>After you sign up, you&#8217;ll receive an email with a link to the starter files and access to the videos. The example app uses Webpack to bundle ES6 modules into a single JavaScript file, so the course begins with a video on using NPM and Webpack to set up a local development environment. Learn Redux includes:</p>\n<ul>\n<li>Access to all 20 videos</li>\n<li>All starter files</li>\n<li>Webpack Build Templates</li>\n<li>Stepped and finished solutions</li>\n</ul>\n<p>Bos spent more than 100 hours producing this series in partnership with <a href=\"https://getsentry.com/welcome/\" target=\"_blank\">Sentry</a> as a sponsor. Anyone who signs up receives a $50 Sentry credit.</p>\n<p>After Calypso was announced, Bos, who describes himself as &#8220;a huge WordPress fan,&#8221; wrote a <a href=\"http://wesbos.com/wordpress-calypso-react/\" target=\"_blank\">post</a> dispelling rumors that WordPress was ditching PHP and being rewritten in Node.js. He also urged WordPress developers to learn JavaScript.</p>\n<p>&#8220;This is thunder in the distance as to what is to come in WordPress,&#8221; Bos said. &#8220;Much of the theme writing I do is already in JavaScript – I often use WordPress as just an API to get data out of, and then use frameworks like Angular, React, Google Maps or jQuery to display that data. I’m not building an entire website in a JavaScript framework, but much of the interactive view layer of these sites is moving into JavaScript frameworks.&#8221;</p>\n<p>If you want to be ready to dive into the next generation of WordPress site and application development with knowledge of one of the most popular JS frameworks, the free <a href=\"https://learnredux.com/\" target=\"_blank\">Learn Redux</a> course offers all the tools necessary for getting started with React.js, Redux, and React Router.</p>\n<p>&#8220;Our trusty PHP template files aren’t going anywhere anytime soon, but I’ll bet you dollars to donuts you’ll be writing a lot more JavaScript in your WordPress sites in the years to come,&#8221; Bos said.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Mon, 16 May 2016 21:50:34 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:3193:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/react-redux-course.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/react-redux-course.png?resize=1025%2C465\" alt=\"react-redux-course\" class=\"aligncenter size-full wp-image-54916\" /></a></p>\n<p><a href=\"http://wesbos.com/\" target=\"_blank\">Wes Bos</a>, a developer and educator known for his high quality video tutorials, has just launched a free online course for building JavaScript apps with <a href=\"https://facebook.github.io/react/\" target=\"_blank\">React.js</a> and <a href=\"http://redux.js.org/\" target=\"_blank\">Redux</a>. The 2.5 hour <a href=\"https://learnredux.com/\" target=\"_blank\">Learn Redux</a> course includes 20 videos that guide developers through building an example &#8216;Reduxstagram&#8217; app to present the core ideas behind Redux.</p>\n<p>To get the most out of Learn Redux, students should have a decent foundation of React and ES6. Bos recommends those who are not comfortable with React to start with his <a href=\"https://reactforbeginners.com/\" target=\"_blank\">React for Beginners</a> course.</p>\n<p>After you sign up, you&#8217;ll receive an email with a link to the starter files and access to the videos. The example app uses Webpack to bundle ES6 modules into a single JavaScript file, so the course begins with a video on using NPM and Webpack to set up a local development environment. Learn Redux includes:</p>\n<ul>\n<li>Access to all 20 videos</li>\n<li>All starter files</li>\n<li>Webpack Build Templates</li>\n<li>Stepped and finished solutions</li>\n</ul>\n<p>Bos spent more than 100 hours producing this series in partnership with <a href=\"https://getsentry.com/welcome/\" target=\"_blank\">Sentry</a> as a sponsor. Anyone who signs up receives a $50 Sentry credit.</p>\n<p>After Calypso was announced, Bos, who describes himself as &#8220;a huge WordPress fan,&#8221; wrote a <a href=\"http://wesbos.com/wordpress-calypso-react/\" target=\"_blank\">post</a> dispelling rumors that WordPress was ditching PHP and being rewritten in Node.js. He also urged WordPress developers to learn JavaScript.</p>\n<p>&#8220;This is thunder in the distance as to what is to come in WordPress,&#8221; Bos said. &#8220;Much of the theme writing I do is already in JavaScript – I often use WordPress as just an API to get data out of, and then use frameworks like Angular, React, Google Maps or jQuery to display that data. I’m not building an entire website in a JavaScript framework, but much of the interactive view layer of these sites is moving into JavaScript frameworks.&#8221;</p>\n<p>If you want to be ready to dive into the next generation of WordPress site and application development with knowledge of one of the most popular JS frameworks, the free <a href=\"https://learnredux.com/\" target=\"_blank\">Learn Redux</a> course offers all the tools necessary for getting started with React.js, Redux, and React Router.</p>\n<p>&#8220;Our trusty PHP template files aren’t going anywhere anytime soon, but I’ll bet you dollars to donuts you’ll be writing a lot more JavaScript in your WordPress sites in the years to come,&#8221; Bos said.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:20;a:7:{s:5:\"title\";s:134:\"WPTavern: Daniel Bachhuber Discusses WP-CLI, the WP REST API, and the Challenges of Contributing to Open Source on Roots Radio Podcast\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54738\";s:4:\"link\";s:142:\"http://wptavern.com/daniel-bachhuber-discusses-wp-cli-the-wp-rest-api-and-the-challenges-of-contributing-to-open-source-on-roots-radio-podcast\";s:11:\"description\";s:7828:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/daniel-bachhuber.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/daniel-bachhuber.jpg?resize=300%2C300\" alt=\"daniel-bachhuber\" class=\"alignright size-medium wp-image-54898\" /></a><a href=\"https://danielbachhuber.com/\" target=\"_blank\">Daniel Bachhuber</a>, maintainer of the <a href=\"http://wp-cli.org/\" target=\"_blank\">WP-CLI</a> project and a contributing developer to the <a href=\"http://v2.wp-api.org/\" target=\"_blank\">WP REST API</a>, joined Chris Carr and Austin Pray on a recent episode of the <a href=\"https://roots.io/podcast/ep13/\" target=\"_blank\">Roots Radio podcast</a>. Bachhuber discussed his recent experience crowdfunding his work on &#8220;<a href=\"https://wp-cli.org/restful/\" target=\"_blank\">A More RESTful WP-CLI</a>&#8221; as well as the challenges he&#8217;s encountered as a contributor to various open source projects over the years.</p>\n<p>In the first part of the episode, Bachhuber shared how he spent the 283 hours of time that the WordPress community funded to advance the WP-CLI and WP REST API projects. The funding gave him the opportunity to dedicate time split between the two projects. Bachhuber put in approximately 95 hours towards the REST API in January and February but the bulk of the hours went towards making WP-CLI more friendly for developers who work with the REST API.</p>\n<p>&#8220;WordPress developers are going to be putting a lot of time now towards writing REST endpoints that expose their functionality to the world, and it would be really nice if WP-CLI interoperated nicely with that and allowed you to use that functionality at the command line without having to separately write your own WP-CLI commands,&#8221; Bachhuber said.</p>\n<p>He discussed the challenge of scoping out this broad goal and what he learned about crowdfunding during the process.</p>\n<p>&#8220;The RESTful WP-CLI kickstarter project was intentionally ambitious, because I&#8217;m a guy who has big ideas and likes to do big things,&#8221; Bachhuber said. &#8220;There are some things I feel really happy that I&#8217;ve been able to ship and produce so far, and there are other features that, for one reason or another, I haven&#8217;t quite been able to execute  yet and that&#8217;s a bit frustrating.</p>\n<p>&#8220;It&#8217;s a whole different ball game trying to manage the expectations of your Kickstarter backers than it is a single client. I&#8217;ve got 107 clients that I have to make happy,&#8221; he said.</p>\n<p>Nevertheless, Bachhuber said he was able to get the issue backlog for WP-CLI down to less than 60 issues and the dedicated time has allowed him to resolve old issues that have &#8220;languished since the dawn of time.&#8221;</p>\n<p>As part of the rewards offered for contributors to the crowdfunding campaign, Bachhuber offered his time consulting with individuals and organizations, which he found to be easier than traditional physical swag rewards.</p>\n<p>&#8220;I&#8217;m really glad that I chose [consulting] over having to give out physical swag, because it&#8217;s very difficult to procure and ship to everyone, particularly when you have international backers,&#8221; he said. &#8220;Even though I&#8217;ve spent a lot of my time fulfilling the rewards and talking with people and having calls with them and meeting up with them in person, it&#8217;s a much easier effort to manage than sending 100 coffee mugs across the world.&#8221;</p>\n<p>When asked if he&#8217;d do it again, Bachhuber said yes but emphasized that spending this much time on an open source project only works if you keep a healthy balance with other aspects of life.</p>\n<p>&#8220;I think it&#8217;s really important that if you&#8217;re contributing to open source projects on a regular basis or even maintaining them, that you balance your time between that and other things,&#8221; he said. &#8220;It&#8217;s really easy to get burned out on said open source project if you spend 100% of your time on it for a whole month or six months.</p>\n<p>&#8220;I was pretty intentional to say that the money I was raising was going to cover my involvement with the project for six months, a certain number of hours, and that it was going to be a part-time thing. That was a really healthy way to approach it. I think I would have gotten burned out if I had just tried to dive into it, crank it out, and move on to the next thing,&#8221; Bachhuber said.</p>\n<h3>The Emotional Challenges of Working on Open Source Projects</h3>\n<p>During the course of the interview Bachhuber was asked to share his feelings on what he referred to as &#8220;the kerfuffle with the REST API&#8221; that happened in February. The REST API team had written a merge proposal in September 2015 that recommended merging the API in two parts &#8211; the infrastructure in 4.4 and the posts, comments, terms, and users endpoints in 4.5 or 4.6. After partially executing on that proposal, the team held a status chat to discuss the plan moving forward.</p>\n<p>Bachhuber said that the discussion became &#8220;a very emotionally fraught event&#8221; after Matt Mullenweg said the project needed feature parity with the WordPress admin before any of the endpoints could be considered for merge. After putting hundreds of hours into the project alongside a handful of dedicated contributors who were already spread thin, he found this new requirement was a difficult pill to swallow.</p>\n<p>&#8220;For better or for worse, as a maintainer or even a participant of an open source project, you have to have a thick skin and realize that all the time the decisions that are made are not about you &#8211; they are about the project,&#8221; Bachhuber said. &#8220;Even if you are personally offended by the decision, it doesn&#8217;t matter because it isn&#8217;t about you. It&#8217;s really difficult to deal with emotionally.&#8221;</p>\n<p>Bachhuber&#8217;s years of contributing to and maintaing open source projects has taught him a few things about managing stress and conflict that <a href=\"https://2016.europe.wordcamp.org/session/my-condolences-youre-now-the-maintainer-of-a-popular-open-source-project/\" target=\"_blank\">he plans to share at WordCamp Europe</a> in a talk titled, &#8220;My condolences, You&#8217;re now the maintainer of a popular OS project.&#8221;</p>\n<p>&#8220;I find a lot of joy in maintaining open source projects,&#8221; Bachhuber said. &#8220;I also have to actively work to address the emotional side of the equation to make sure I&#8217;m in a healthy space to continue maintaining the project and the project is not affecting me personally. It&#8217;s taken me years to come to a point where I&#8217;m comfortable with that.&#8221;</p>\n<p>In the case of the WP REST API, Bachhuber has come to a place where he can compartmentalize his emotional reactions and responses to the differing opinions.</p>\n<p>&#8220;I&#8217;ve come to a point now where I care but I don&#8217;t care,&#8221; he said. &#8220;I care in the sense that I&#8217;d still love to see those endpoints go into core and see the fruits of our labors realized. I don&#8217;t care because I&#8217;m not emotionally attached to that happening on any particular time frame. I honestly would rather it happen when it&#8217;s ready to happen over prematurely, and I realize I might not be the best qualified person to make that decision.&#8221;</p>\n<p>In the remainder of the episode, Bachhuber and Carr discuss React, Redux, Karma, Enzyme, and other tools for testing and developing with the REST API. Check out the recording of the episode on <a href=\"https://roots.io/podcast/ep13/\" target=\"_blank\">Roots Radio</a> for more details about Bachhuber&#8217;s work on WP-CLI and his crowdfunding experience.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Mon, 16 May 2016 06:03:31 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:7828:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/daniel-bachhuber.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/daniel-bachhuber.jpg?resize=300%2C300\" alt=\"daniel-bachhuber\" class=\"alignright size-medium wp-image-54898\" /></a><a href=\"https://danielbachhuber.com/\" target=\"_blank\">Daniel Bachhuber</a>, maintainer of the <a href=\"http://wp-cli.org/\" target=\"_blank\">WP-CLI</a> project and a contributing developer to the <a href=\"http://v2.wp-api.org/\" target=\"_blank\">WP REST API</a>, joined Chris Carr and Austin Pray on a recent episode of the <a href=\"https://roots.io/podcast/ep13/\" target=\"_blank\">Roots Radio podcast</a>. Bachhuber discussed his recent experience crowdfunding his work on &#8220;<a href=\"https://wp-cli.org/restful/\" target=\"_blank\">A More RESTful WP-CLI</a>&#8221; as well as the challenges he&#8217;s encountered as a contributor to various open source projects over the years.</p>\n<p>In the first part of the episode, Bachhuber shared how he spent the 283 hours of time that the WordPress community funded to advance the WP-CLI and WP REST API projects. The funding gave him the opportunity to dedicate time split between the two projects. Bachhuber put in approximately 95 hours towards the REST API in January and February but the bulk of the hours went towards making WP-CLI more friendly for developers who work with the REST API.</p>\n<p>&#8220;WordPress developers are going to be putting a lot of time now towards writing REST endpoints that expose their functionality to the world, and it would be really nice if WP-CLI interoperated nicely with that and allowed you to use that functionality at the command line without having to separately write your own WP-CLI commands,&#8221; Bachhuber said.</p>\n<p>He discussed the challenge of scoping out this broad goal and what he learned about crowdfunding during the process.</p>\n<p>&#8220;The RESTful WP-CLI kickstarter project was intentionally ambitious, because I&#8217;m a guy who has big ideas and likes to do big things,&#8221; Bachhuber said. &#8220;There are some things I feel really happy that I&#8217;ve been able to ship and produce so far, and there are other features that, for one reason or another, I haven&#8217;t quite been able to execute  yet and that&#8217;s a bit frustrating.</p>\n<p>&#8220;It&#8217;s a whole different ball game trying to manage the expectations of your Kickstarter backers than it is a single client. I&#8217;ve got 107 clients that I have to make happy,&#8221; he said.</p>\n<p>Nevertheless, Bachhuber said he was able to get the issue backlog for WP-CLI down to less than 60 issues and the dedicated time has allowed him to resolve old issues that have &#8220;languished since the dawn of time.&#8221;</p>\n<p>As part of the rewards offered for contributors to the crowdfunding campaign, Bachhuber offered his time consulting with individuals and organizations, which he found to be easier than traditional physical swag rewards.</p>\n<p>&#8220;I&#8217;m really glad that I chose [consulting] over having to give out physical swag, because it&#8217;s very difficult to procure and ship to everyone, particularly when you have international backers,&#8221; he said. &#8220;Even though I&#8217;ve spent a lot of my time fulfilling the rewards and talking with people and having calls with them and meeting up with them in person, it&#8217;s a much easier effort to manage than sending 100 coffee mugs across the world.&#8221;</p>\n<p>When asked if he&#8217;d do it again, Bachhuber said yes but emphasized that spending this much time on an open source project only works if you keep a healthy balance with other aspects of life.</p>\n<p>&#8220;I think it&#8217;s really important that if you&#8217;re contributing to open source projects on a regular basis or even maintaining them, that you balance your time between that and other things,&#8221; he said. &#8220;It&#8217;s really easy to get burned out on said open source project if you spend 100% of your time on it for a whole month or six months.</p>\n<p>&#8220;I was pretty intentional to say that the money I was raising was going to cover my involvement with the project for six months, a certain number of hours, and that it was going to be a part-time thing. That was a really healthy way to approach it. I think I would have gotten burned out if I had just tried to dive into it, crank it out, and move on to the next thing,&#8221; Bachhuber said.</p>\n<h3>The Emotional Challenges of Working on Open Source Projects</h3>\n<p>During the course of the interview Bachhuber was asked to share his feelings on what he referred to as &#8220;the kerfuffle with the REST API&#8221; that happened in February. The REST API team had written a merge proposal in September 2015 that recommended merging the API in two parts &#8211; the infrastructure in 4.4 and the posts, comments, terms, and users endpoints in 4.5 or 4.6. After partially executing on that proposal, the team held a status chat to discuss the plan moving forward.</p>\n<p>Bachhuber said that the discussion became &#8220;a very emotionally fraught event&#8221; after Matt Mullenweg said the project needed feature parity with the WordPress admin before any of the endpoints could be considered for merge. After putting hundreds of hours into the project alongside a handful of dedicated contributors who were already spread thin, he found this new requirement was a difficult pill to swallow.</p>\n<p>&#8220;For better or for worse, as a maintainer or even a participant of an open source project, you have to have a thick skin and realize that all the time the decisions that are made are not about you &#8211; they are about the project,&#8221; Bachhuber said. &#8220;Even if you are personally offended by the decision, it doesn&#8217;t matter because it isn&#8217;t about you. It&#8217;s really difficult to deal with emotionally.&#8221;</p>\n<p>Bachhuber&#8217;s years of contributing to and maintaing open source projects has taught him a few things about managing stress and conflict that <a href=\"https://2016.europe.wordcamp.org/session/my-condolences-youre-now-the-maintainer-of-a-popular-open-source-project/\" target=\"_blank\">he plans to share at WordCamp Europe</a> in a talk titled, &#8220;My condolences, You&#8217;re now the maintainer of a popular OS project.&#8221;</p>\n<p>&#8220;I find a lot of joy in maintaining open source projects,&#8221; Bachhuber said. &#8220;I also have to actively work to address the emotional side of the equation to make sure I&#8217;m in a healthy space to continue maintaining the project and the project is not affecting me personally. It&#8217;s taken me years to come to a point where I&#8217;m comfortable with that.&#8221;</p>\n<p>In the case of the WP REST API, Bachhuber has come to a place where he can compartmentalize his emotional reactions and responses to the differing opinions.</p>\n<p>&#8220;I&#8217;ve come to a point now where I care but I don&#8217;t care,&#8221; he said. &#8220;I care in the sense that I&#8217;d still love to see those endpoints go into core and see the fruits of our labors realized. I don&#8217;t care because I&#8217;m not emotionally attached to that happening on any particular time frame. I honestly would rather it happen when it&#8217;s ready to happen over prematurely, and I realize I might not be the best qualified person to make that decision.&#8221;</p>\n<p>In the remainder of the episode, Bachhuber and Carr discuss React, Redux, Karma, Enzyme, and other tools for testing and developing with the REST API. Check out the recording of the episode on <a href=\"https://roots.io/podcast/ep13/\" target=\"_blank\">Roots Radio</a> for more details about Bachhuber&#8217;s work on WP-CLI and his crowdfunding experience.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:21;a:7:{s:5:\"title\";s:102:\"WPTavern: The WordPress.org Recommended Hosting Page is Revamped, Features Flywheel for the First Time\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54822\";s:4:\"link\";s:111:\"http://wptavern.com/the-wordpress-org-recommended-hosting-page-is-revamped-features-flywheel-for-the-first-time\";s:11:\"description\";s:8235:\"<p>DreamHost, Flywheel, and SiteGround have joined Bluehost on WordPress.org&#8217;s new <a href=\"https://wordpress.org/hosting/\">recommended hosting</a> page. In mid 2015, Matt Mullenweg, co-founder of the open source WordPress project, <a href=\"http://wptavern.com/the-recommended-hosting-page-on-wordpress-org-starts-over-from-scratch\">announced</a> the page would be revamped. To have a chance at being listed webhosting companies needed to fill out a 40-question survey.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/RecommendedHostsPage.png\"><img class=\"size-full wp-image-54844\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/RecommendedHostsPage.png?resize=790%2C642\" alt=\"2016 Recommended Hosts Page\" /></a>2016 Recommended Hosts Page\n<p>This is Flywheel&#8217;s first time on the page. <a href=\"https://getflywheel.com/\">Flywheel</a>, launched in 2013, is a managed WordPress hosting company with an emphasis towards designers and agencies. I asked Dusty Davidson, c<span class=\"team__role\">o-Founder and CEO of Flywheel</span>, what it means to be included on the page. &#8220;We&#8217;re obviously excited to be included, and think it really reflects on the work we&#8217;ve done to create a great experience for WordPress users,&#8221; he<span class=\"team__role\"> said. </span></p>\n<p>The recommended webhosting page on WordPress.org is incredibly lucrative. Based on conversations I&#8217;ve had with employees of hosts listed, it can generate millions of dollars in revenue. I asked Davidson what impact this will have on his company, &#8220;<span class=\"team__role\">I&#8217;m sure it will undoubtedly send a good deal of traffic, but honestly we&#8217;re just humbled and excited to be recognized,&#8221; he said. </span></p>\n<h2>A New Round of Controversy</h2>\n<p>Over the years, companies have come and gone from the recommended hosting page. However, Bluehost in particular has consistently appeared on the list, including the most recent iteration. Bluehost is owned by <a href=\"http://www.endurance.com/\">Endurance International Group</a> who <a href=\"http://www.prweb.com/releases/2014/05/prweb11874425.htm\">invested in Automattic</a> in 2014. Because Mullenweg is the CEO of Automattic and controls who is listed on the page, it&#8217;s easy to see why it regularly generates controversy.</p>\n<p>Kevin Ohashi of ReviewSignal.com, <a href=\"http://reviewsignal.com/blog/2016/05/12/wordpress-org-updates-hosting-recommendations-nobody-knows-selection-criteria/\">criticized the lack of transparency</a> regarding the process for how hosts.</p>\n<blockquote><p>Who is responsible for this revamp? What were the selection criteria? How often will it be updated? Will existing companies be continuously re-evaluated?</p></blockquote>\n<p>These are important questions to ask and there are no publicly documented answers. In a follow up post, <a href=\"http://reviewsignal.com/blog/2016/05/13/wordpress-org-hosting-recommendations-listing-criteria/\">Ohashi investigated</a> what criteria needs to be met for being listed on the page. The post contains a number of screenshots of his private conversation with <a href=\"https://profiles.wordpress.org/macmanx\">James Huff</a>, who has volunteered for the WordPress project for 12 years and has worked at Automattic for five years.</p>\n<p>Huff was directly related to the project and influenced who was chosen thanks to his involvement on the WordPress Support Team. Within the conversation, he shares details of the process and mentions that no money exchanged hands. Early in the conversation, Ohashi tells Huff that he wants to learn and publish how the process works. However, Huff had no idea that everything he said would be made public.</p>\n<p>&#8220;I was invited to what sounded like a friendly chat over direct message from a concerned community member, after he was referred to me by a friend,&#8221; Huff said. &#8220;At no point was it clarified or even implied that anything discussed would be made public.&#8221;</p>\n<p><del>Conversations held in a private matter should remain private unless given permission to publish them, something I discovered the hard way.</del> Unfortunately, the post comes across as a public interrogation of Huff. I asked Huff, who was shaken by the experience, how it has affected him moving forward as it relates to the WordPress project.</p>\n<p>&#8220;I&#8217;d be lying if I said my feelings weren&#8217;t at least shaken by the experience, especially considering how polite he was to my friend and how hostile he was towards me apparently just because I work for Automattic, but this isn&#8217;t the first time that has happened to me and I don&#8217;t expect it to be the last,&#8221; he said.</p>\n<p>&#8220;There&#8217;s an usually prevalent negative bias against Automatticians who contribute to WordPress.&#8221;</p>\n<h2>Mullenweg Provides Clarification</h2>\n<p>Mullenweg <a href=\"http://reviewsignal.com/blog/2016/05/13/wordpress-org-hosting-recommendations-listing-criteria/#comment-1011\">commented on the post</a> where he not only sticks up for Huff, but answers some of the controversial questions raised by Ohashi. Mullenweg explains how the applicants were chosen, how the criteria is weighted, who makes the final decisions, and how much money is involved. Here is his comment in full.</p>\n<blockquote><p>&#8216;I would like to see some transparency in the process&#8217;</p>\n<p>As stated on the page, the listing is completely arbitrary. The process was: There was a survey, four applicants were chosen, and the page was updated. That might repeat later in the year, or the process might change.</p>\n<p>&#8216;how criteria are weighted&#8217;</p>\n<p>There is no criteria or weighting. It ultimately is one person’s opinion. Information that is important is reflected in the questions asked in the survey, but that is not everything that is taken into account. (I have looked at this site in the past, for example.)</p>\n<p>&#8216;who is making the decisions&#8217;</p>\n<p>I am. James helped in sorting through the many submissions that came in, doing additional research, and digging on finalists, but ultimately the decision was mine. You can and should blame me fully for any issues you have with it. I appreciate James’ help in this go-round, but he will not be involved at all with any future updates. (So, please leave him alone.)</p>\n<p>&#8216;how much money is involved&#8217;</p>\n<p>There was no money involved. Obviously being listed on the page is hugely valuable and impacts the listed (or unlisted) businesses a great deal. This is why I take full responsibility for the listing, now and in the future — I have been fortunate to be extraordinarily successful and no financial or business consideration any of the applicants could offer matters to me. A host could offer $100,000,000 to be listed on the page for 1 day, and I would say no.</p></blockquote>\n<p>It&#8217;s unfortunate that the information in Mullenweg&#8217;s comment is not published in an official post announcing the changes to the recommended hosting page. If an official post was published that included the same information in his comment, it&#8217;s possible it would have eliminated most of the confusion, uncertainty, and doubt surrounding it.</p>\n<h2>Should WordPress.org Have a Recommended Hosting Page?</h2>\n<p>Due to the investments EIG has made in Automattic, Mullenweg&#8217;s role at the company, and him making the final decisions, there will always be a potential conflict of interest despite taking full responsibility of the page and the processes associated with it.</p>\n<p>Should WordPress.org have a recommended hosting page? What if the page was replaced with information people could use to make informed decisions on choosing a host? It would eliminate potential conflicts of interest and if there was a host Mullenweg felt strongly about, he could label it as a partner of the project. This would make it clear that any financial connection with the company is a business relationship.</p>\n<p>Are you hosting with any of the companies listed on the recommended hosting page? If so, tell us about your experience in the comments.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Sat, 14 May 2016 16:39:29 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:8235:\"<p>DreamHost, Flywheel, and SiteGround have joined Bluehost on WordPress.org&#8217;s new <a href=\"https://wordpress.org/hosting/\">recommended hosting</a> page. In mid 2015, Matt Mullenweg, co-founder of the open source WordPress project, <a href=\"http://wptavern.com/the-recommended-hosting-page-on-wordpress-org-starts-over-from-scratch\">announced</a> the page would be revamped. To have a chance at being listed webhosting companies needed to fill out a 40-question survey.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/RecommendedHostsPage.png\"><img class=\"size-full wp-image-54844\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/RecommendedHostsPage.png?resize=790%2C642\" alt=\"2016 Recommended Hosts Page\" /></a>2016 Recommended Hosts Page\n<p>This is Flywheel&#8217;s first time on the page. <a href=\"https://getflywheel.com/\">Flywheel</a>, launched in 2013, is a managed WordPress hosting company with an emphasis towards designers and agencies. I asked Dusty Davidson, c<span class=\"team__role\">o-Founder and CEO of Flywheel</span>, what it means to be included on the page. &#8220;We&#8217;re obviously excited to be included, and think it really reflects on the work we&#8217;ve done to create a great experience for WordPress users,&#8221; he<span class=\"team__role\"> said. </span></p>\n<p>The recommended webhosting page on WordPress.org is incredibly lucrative. Based on conversations I&#8217;ve had with employees of hosts listed, it can generate millions of dollars in revenue. I asked Davidson what impact this will have on his company, &#8220;<span class=\"team__role\">I&#8217;m sure it will undoubtedly send a good deal of traffic, but honestly we&#8217;re just humbled and excited to be recognized,&#8221; he said. </span></p>\n<h2>A New Round of Controversy</h2>\n<p>Over the years, companies have come and gone from the recommended hosting page. However, Bluehost in particular has consistently appeared on the list, including the most recent iteration. Bluehost is owned by <a href=\"http://www.endurance.com/\">Endurance International Group</a> who <a href=\"http://www.prweb.com/releases/2014/05/prweb11874425.htm\">invested in Automattic</a> in 2014. Because Mullenweg is the CEO of Automattic and controls who is listed on the page, it&#8217;s easy to see why it regularly generates controversy.</p>\n<p>Kevin Ohashi of ReviewSignal.com, <a href=\"http://reviewsignal.com/blog/2016/05/12/wordpress-org-updates-hosting-recommendations-nobody-knows-selection-criteria/\">criticized the lack of transparency</a> regarding the process for how hosts.</p>\n<blockquote><p>Who is responsible for this revamp? What were the selection criteria? How often will it be updated? Will existing companies be continuously re-evaluated?</p></blockquote>\n<p>These are important questions to ask and there are no publicly documented answers. In a follow up post, <a href=\"http://reviewsignal.com/blog/2016/05/13/wordpress-org-hosting-recommendations-listing-criteria/\">Ohashi investigated</a> what criteria needs to be met for being listed on the page. The post contains a number of screenshots of his private conversation with <a href=\"https://profiles.wordpress.org/macmanx\">James Huff</a>, who has volunteered for the WordPress project for 12 years and has worked at Automattic for five years.</p>\n<p>Huff was directly related to the project and influenced who was chosen thanks to his involvement on the WordPress Support Team. Within the conversation, he shares details of the process and mentions that no money exchanged hands. Early in the conversation, Ohashi tells Huff that he wants to learn and publish how the process works. However, Huff had no idea that everything he said would be made public.</p>\n<p>&#8220;I was invited to what sounded like a friendly chat over direct message from a concerned community member, after he was referred to me by a friend,&#8221; Huff said. &#8220;At no point was it clarified or even implied that anything discussed would be made public.&#8221;</p>\n<p><del>Conversations held in a private matter should remain private unless given permission to publish them, something I discovered the hard way.</del> Unfortunately, the post comes across as a public interrogation of Huff. I asked Huff, who was shaken by the experience, how it has affected him moving forward as it relates to the WordPress project.</p>\n<p>&#8220;I&#8217;d be lying if I said my feelings weren&#8217;t at least shaken by the experience, especially considering how polite he was to my friend and how hostile he was towards me apparently just because I work for Automattic, but this isn&#8217;t the first time that has happened to me and I don&#8217;t expect it to be the last,&#8221; he said.</p>\n<p>&#8220;There&#8217;s an usually prevalent negative bias against Automatticians who contribute to WordPress.&#8221;</p>\n<h2>Mullenweg Provides Clarification</h2>\n<p>Mullenweg <a href=\"http://reviewsignal.com/blog/2016/05/13/wordpress-org-hosting-recommendations-listing-criteria/#comment-1011\">commented on the post</a> where he not only sticks up for Huff, but answers some of the controversial questions raised by Ohashi. Mullenweg explains how the applicants were chosen, how the criteria is weighted, who makes the final decisions, and how much money is involved. Here is his comment in full.</p>\n<blockquote><p>&#8216;I would like to see some transparency in the process&#8217;</p>\n<p>As stated on the page, the listing is completely arbitrary. The process was: There was a survey, four applicants were chosen, and the page was updated. That might repeat later in the year, or the process might change.</p>\n<p>&#8216;how criteria are weighted&#8217;</p>\n<p>There is no criteria or weighting. It ultimately is one person’s opinion. Information that is important is reflected in the questions asked in the survey, but that is not everything that is taken into account. (I have looked at this site in the past, for example.)</p>\n<p>&#8216;who is making the decisions&#8217;</p>\n<p>I am. James helped in sorting through the many submissions that came in, doing additional research, and digging on finalists, but ultimately the decision was mine. You can and should blame me fully for any issues you have with it. I appreciate James’ help in this go-round, but he will not be involved at all with any future updates. (So, please leave him alone.)</p>\n<p>&#8216;how much money is involved&#8217;</p>\n<p>There was no money involved. Obviously being listed on the page is hugely valuable and impacts the listed (or unlisted) businesses a great deal. This is why I take full responsibility for the listing, now and in the future — I have been fortunate to be extraordinarily successful and no financial or business consideration any of the applicants could offer matters to me. A host could offer $100,000,000 to be listed on the page for 1 day, and I would say no.</p></blockquote>\n<p>It&#8217;s unfortunate that the information in Mullenweg&#8217;s comment is not published in an official post announcing the changes to the recommended hosting page. If an official post was published that included the same information in his comment, it&#8217;s possible it would have eliminated most of the confusion, uncertainty, and doubt surrounding it.</p>\n<h2>Should WordPress.org Have a Recommended Hosting Page?</h2>\n<p>Due to the investments EIG has made in Automattic, Mullenweg&#8217;s role at the company, and him making the final decisions, there will always be a potential conflict of interest despite taking full responsibility of the page and the processes associated with it.</p>\n<p>Should WordPress.org have a recommended hosting page? What if the page was replaced with information people could use to make informed decisions on choosing a host? It would eliminate potential conflicts of interest and if there was a host Mullenweg felt strongly about, he could label it as a partner of the project. This would make it clear that any financial connection with the company is a business relationship.</p>\n<p>Are you hosting with any of the companies listed on the recommended hosting page? If so, tell us about your experience in the comments.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:22;a:7:{s:5:\"title\";s:88:\"WPTavern: WordPress Accessibility Team Seeks Testers Using Speech Recognition Technology\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54829\";s:4:\"link\";s:98:\"http://wptavern.com/wordpress-accessibility-team-seeks-testers-using-speech-recognition-technology\";s:11:\"description\";s:2791:\"<a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/glasses.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/glasses.jpg?resize=1024%2C562\" alt=\"photo credit: Let\'s Read - (license)\" class=\"size-full wp-image-54851\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/42788859@N00/320216939\">Let&#8217;s Read</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nc-sa/2.0/\">(license)</a>\n<p>The World Health Organization estimates that <a href=\"http://www.who.int/mediacentre/factsheets/fs282/en/\" target=\"_blank\">285 million people</a> worldwide are living with some form of visual impairment and 39 million of those are estimated to be blind. Many people with low vision depend on speech recognition technology to navigate the web and communicate their thoughts. This type of software also assists people who have carpal tunnel, RSI (Repetitive Stress Injuries) and/or limited mobility in their hands and arms.</p>\n<p>Rian Rietveld and the Accessibility team are working to improve the experience of using WordPress with speech recognition software, such as <a href=\"http://www.nuance.com/dragon/index.htm\" target=\"_blank\">Dragon Naturally Speaking</a> (widely considered as one of the best for desktop use.) In particular, <a href=\"https://core.trac.wordpress.org/ticket/23562\" target=\"_blank\">the task of adding media to a post has a number of obstacles</a> that make it nearly impossible for those using speech recognition software.</p>\n<p>Rietveld <a href=\"https://make.wordpress.org/accessibility/2016/05/13/20th-wordpress-accessibility-test-add-media-with-speech-recognition-software/\" target=\"_blank\">posted three tests</a> to the Accessibility team&#8217;s blog today, inviting those who use <a href=\"http://www.nuance.com/dragon/index.htm\" target=\"_blank\">Dragon Naturally Speaking</a> or other assistive technology to help the contributors determine the roadblocks that need to be removed for adding media. These tests include actions like adding media, editing attachment details, and creating a gallery.</p>\n<p>If you use WordPress with assistive technology for speech recognition, completing these tests and offering your feedback is one way to get involved as a contributor. You don&#8217;t necessarily have to use Dragon Naturally Speaking, as there are many newer alternatives such as Windows Speech Recognition (Cortana) and Chrome&#8217;s speech recognition powered by Google Speech to Text. Testers can report their experiences, along with the assistive technology/browser/OS, in the comments on Rietveld&#8217;s <a href=\"https://make.wordpress.org/accessibility/2016/05/13/20th-wordpress-accessibility-test-add-media-with-speech-recognition-software/\" target=\"_blank\">post</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 13 May 2016 22:40:35 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2791:\"<a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/glasses.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/glasses.jpg?resize=1024%2C562\" alt=\"photo credit: Let\'s Read - (license)\" class=\"size-full wp-image-54851\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/42788859@N00/320216939\">Let&#8217;s Read</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nc-sa/2.0/\">(license)</a>\n<p>The World Health Organization estimates that <a href=\"http://www.who.int/mediacentre/factsheets/fs282/en/\" target=\"_blank\">285 million people</a> worldwide are living with some form of visual impairment and 39 million of those are estimated to be blind. Many people with low vision depend on speech recognition technology to navigate the web and communicate their thoughts. This type of software also assists people who have carpal tunnel, RSI (Repetitive Stress Injuries) and/or limited mobility in their hands and arms.</p>\n<p>Rian Rietveld and the Accessibility team are working to improve the experience of using WordPress with speech recognition software, such as <a href=\"http://www.nuance.com/dragon/index.htm\" target=\"_blank\">Dragon Naturally Speaking</a> (widely considered as one of the best for desktop use.) In particular, <a href=\"https://core.trac.wordpress.org/ticket/23562\" target=\"_blank\">the task of adding media to a post has a number of obstacles</a> that make it nearly impossible for those using speech recognition software.</p>\n<p>Rietveld <a href=\"https://make.wordpress.org/accessibility/2016/05/13/20th-wordpress-accessibility-test-add-media-with-speech-recognition-software/\" target=\"_blank\">posted three tests</a> to the Accessibility team&#8217;s blog today, inviting those who use <a href=\"http://www.nuance.com/dragon/index.htm\" target=\"_blank\">Dragon Naturally Speaking</a> or other assistive technology to help the contributors determine the roadblocks that need to be removed for adding media. These tests include actions like adding media, editing attachment details, and creating a gallery.</p>\n<p>If you use WordPress with assistive technology for speech recognition, completing these tests and offering your feedback is one way to get involved as a contributor. You don&#8217;t necessarily have to use Dragon Naturally Speaking, as there are many newer alternatives such as Windows Speech Recognition (Cortana) and Chrome&#8217;s speech recognition powered by Google Speech to Text. Testers can report their experiences, along with the assistive technology/browser/OS, in the comments on Rietveld&#8217;s <a href=\"https://make.wordpress.org/accessibility/2016/05/13/20th-wordpress-accessibility-test-add-media-with-speech-recognition-software/\" target=\"_blank\">post</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:23;a:7:{s:5:\"title\";s:73:\"WPTavern: Happytables Pivots to Provide Restaurant Analytics and Insights\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=41046\";s:4:\"link\";s:83:\"http://wptavern.com/happytables-pivots-to-provide-restaurant-analytics-and-insights\";s:11:\"description\";s:5302:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/happy-tables.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/happy-tables.jpg?resize=1000%2C608\" alt=\"happy-tables\" class=\"aligncenter size-full wp-image-54835\" /></a></p>\n<p><a href=\"http://www.happytables.com/\" target=\"_blank\">Happytables</a> is changing from being a platform that hosts restaurant websites to one that provides analytics and insights by tapping into apps that restaurants are already using to promote their businesses. The company uses WordPress as a command center for the application that communicates with various restaurant-tech APIs to deliver information to the dashboard in realtime.</p>\n<p>&#8220;We started with the website builder a while back,&#8221; Founder and CEO Noel Tock said. &#8220;It’s been a great ride, but we realized two things: 1) Website builders have become a race to the bottom with regards to revenue as well as extremely competitive, and 2) From our many conversations with restaurants, their challenges have become much larger; consolidating data and insights from all the products they now use.&#8221;</p>\n<p>One of the Happytables beta restaurants in London uses 14 different applications to manage its sales, operations, and marketing, and Tock says this trend is only growing.</p>\n<p>&#8220;The centre of gravity is shifting from the Point of Sale to a very fragmented collection of siloed products (reservations, online ordering, staff scheduling/wages, loyalty, waitlist, social, etc.),&#8221; Tock said. &#8220;Becoming that 30,000 foot view whilst generating actionable insights across the portfolio of applications is the challenge we’ve taken on with the new Happytables.&#8221;</p>\n<p>The first installation of the new Happytables was set up for <a href=\"http://whyteandbrown.com/\" target=\"_blank\">Whyte &amp; Brown</a> in London where the team is focusing their beta testing. The application currently aggregates data from POS (Point of Sale) and Social, but Tock says this will rapidly evolve to providing various insights from POS and Labor, such as revenue forecasting, employee performance, and breakfast/lunch/dinner performance.</p>\n<p>&#8220;It’s been very exciting working towards actionable insights, whereby we can tell a waiter that he/she was underselling a certain product or category compared to their colleagues, or that a particular employee performs a lot better on lunch then on dinner,&#8221; Tock said.</p>\n<p>Below you can see an example of Happytables&#8217; latest kitchen dashboard, using the team view as opposed to the individual employee recommendations/suggestions view.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/Happytables_kitchen_dashboard.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/Happytables_kitchen_dashboard.png?resize=1025%2C731\" alt=\"Happytables_kitchen_dashboard\" class=\"aligncenter size-full wp-image-54833\" /></a></p>\n<p>The new Happytables uses WordPress as a backend and the WP REST API and ReactJS on the frontend.  Although the development team still uses WordPress as one of its core technologies, the infrastructure is a bit more complicated.</p>\n<p>&#8220;It’s not pure WordPress for the data storage,&#8221; CTO Aaron Jorbin said. &#8220;In fact, very little of it is actually stored inside WordPress. It is used to store some information about the restaurant and manage requests to third parties where we fetch the data and then store it in DynamoDB.&#8221;</p>\n<p>The screenshots in this post show the WordPress theme in full screen mode, but Jorbin said the restaurant staff never interact with wp-admin. Restaurant operators use the app to view all the realtime information coming in so that they can make better decisions about how they run their businesses.</p>\n<p>Happytables is still hosting its customers from its first iteration as a website builder, but Tock said most are not good candidates for the beta.</p>\n<p>&#8220;The infrastructure is quite different now as we’re capturing different types of data (previously web content, now largely transactional data),&#8221; he said. &#8220;Our customers on the website builder platform came from all walks of life, so there’s not many who fit the ideal beta candidate (using Micros/Aloha as POS, based in London, run a multiunit restaurant, etc.).</p>\n<p>&#8220;We&#8217;re just looking to see how we can fit this into the larger Happytables model downstream,&#8221; Tock said. &#8220;If we’re going to implement so many API’s, there’s also value in tying those back to the website.&#8221;</p>\n<p>Not many aspects of the new infrastructure have been open sourced yet, as the team has been moving fast. Tock said they hope to make some of their code public further down the road after it&#8217;s been tested.</p>\n<p>&#8220;Once we’re past testing/beta, I’m sure a number of features will become more mature tools and move into their own public repo if they are of that sort of benefit,&#8221; he said. The new infrastructure is one of the many exciting ways that the WP REST API is being used to bring a host of information into WordPress from various third party applications and tie it all together in a useful way.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 13 May 2016 19:45:25 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:5302:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/happy-tables.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/happy-tables.jpg?resize=1000%2C608\" alt=\"happy-tables\" class=\"aligncenter size-full wp-image-54835\" /></a></p>\n<p><a href=\"http://www.happytables.com/\" target=\"_blank\">Happytables</a> is changing from being a platform that hosts restaurant websites to one that provides analytics and insights by tapping into apps that restaurants are already using to promote their businesses. The company uses WordPress as a command center for the application that communicates with various restaurant-tech APIs to deliver information to the dashboard in realtime.</p>\n<p>&#8220;We started with the website builder a while back,&#8221; Founder and CEO Noel Tock said. &#8220;It’s been a great ride, but we realized two things: 1) Website builders have become a race to the bottom with regards to revenue as well as extremely competitive, and 2) From our many conversations with restaurants, their challenges have become much larger; consolidating data and insights from all the products they now use.&#8221;</p>\n<p>One of the Happytables beta restaurants in London uses 14 different applications to manage its sales, operations, and marketing, and Tock says this trend is only growing.</p>\n<p>&#8220;The centre of gravity is shifting from the Point of Sale to a very fragmented collection of siloed products (reservations, online ordering, staff scheduling/wages, loyalty, waitlist, social, etc.),&#8221; Tock said. &#8220;Becoming that 30,000 foot view whilst generating actionable insights across the portfolio of applications is the challenge we’ve taken on with the new Happytables.&#8221;</p>\n<p>The first installation of the new Happytables was set up for <a href=\"http://whyteandbrown.com/\" target=\"_blank\">Whyte &amp; Brown</a> in London where the team is focusing their beta testing. The application currently aggregates data from POS (Point of Sale) and Social, but Tock says this will rapidly evolve to providing various insights from POS and Labor, such as revenue forecasting, employee performance, and breakfast/lunch/dinner performance.</p>\n<p>&#8220;It’s been very exciting working towards actionable insights, whereby we can tell a waiter that he/she was underselling a certain product or category compared to their colleagues, or that a particular employee performs a lot better on lunch then on dinner,&#8221; Tock said.</p>\n<p>Below you can see an example of Happytables&#8217; latest kitchen dashboard, using the team view as opposed to the individual employee recommendations/suggestions view.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/Happytables_kitchen_dashboard.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/Happytables_kitchen_dashboard.png?resize=1025%2C731\" alt=\"Happytables_kitchen_dashboard\" class=\"aligncenter size-full wp-image-54833\" /></a></p>\n<p>The new Happytables uses WordPress as a backend and the WP REST API and ReactJS on the frontend.  Although the development team still uses WordPress as one of its core technologies, the infrastructure is a bit more complicated.</p>\n<p>&#8220;It’s not pure WordPress for the data storage,&#8221; CTO Aaron Jorbin said. &#8220;In fact, very little of it is actually stored inside WordPress. It is used to store some information about the restaurant and manage requests to third parties where we fetch the data and then store it in DynamoDB.&#8221;</p>\n<p>The screenshots in this post show the WordPress theme in full screen mode, but Jorbin said the restaurant staff never interact with wp-admin. Restaurant operators use the app to view all the realtime information coming in so that they can make better decisions about how they run their businesses.</p>\n<p>Happytables is still hosting its customers from its first iteration as a website builder, but Tock said most are not good candidates for the beta.</p>\n<p>&#8220;The infrastructure is quite different now as we’re capturing different types of data (previously web content, now largely transactional data),&#8221; he said. &#8220;Our customers on the website builder platform came from all walks of life, so there’s not many who fit the ideal beta candidate (using Micros/Aloha as POS, based in London, run a multiunit restaurant, etc.).</p>\n<p>&#8220;We&#8217;re just looking to see how we can fit this into the larger Happytables model downstream,&#8221; Tock said. &#8220;If we’re going to implement so many API’s, there’s also value in tying those back to the website.&#8221;</p>\n<p>Not many aspects of the new infrastructure have been open sourced yet, as the team has been moving fast. Tock said they hope to make some of their code public further down the road after it&#8217;s been tested.</p>\n<p>&#8220;Once we’re past testing/beta, I’m sure a number of features will become more mature tools and move into their own public repo if they are of that sort of benefit,&#8221; he said. The new infrastructure is one of the many exciting ways that the WP REST API is being used to bring a host of information into WordPress from various third party applications and tie it all together in a useful way.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:24;a:7:{s:5:\"title\";s:19:\"Matt: Mom on Tinder\";s:4:\"guid\";s:22:\"https://ma.tt/?p=46572\";s:4:\"link\";s:36:\"https://ma.tt/2016/05/mom-on-tinder/\";s:11:\"description\";s:227:\"<p>If you&#8217;re looking for a fun Friday read, <a href=\"http://www.gq.com/story/my-mom-ran-my-tinder\">check out this story of a young GQ writer who gave control of his Tinder account to his Mom</a>. It&#8217;s adorkable.</p>\";s:7:\"pubdate\";s:31:\"Fri, 13 May 2016 16:35:45 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:227:\"<p>If you&#8217;re looking for a fun Friday read, <a href=\"http://www.gq.com/story/my-mom-ran-my-tinder\">check out this story of a young GQ writer who gave control of his Tinder account to his Mom</a>. It&#8217;s adorkable.</p>\";}i:25;a:7:{s:5:\"title\";s:89:\"WPTavern: GitLab Courts Disgruntled GitHub Customers with Response to Recent Pricing Hike\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54780\";s:4:\"link\";s:99:\"http://wptavern.com/gitlab-courts-disgruntled-github-customers-with-response-to-recent-pricing-hike\";s:11:\"description\";s:5016:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/gitlab.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/gitlab.png?resize=1025%2C371\" alt=\"gitlab\" class=\"aligncenter size-full wp-image-50741\" /></a></p>\n<p>Yesterday GitHub <a href=\"http://wptavern.com/github-introduces-unlimited-private-repositories-hikes-prices-for-organizations\" target=\"_blank\">announced</a> pricing changes that give all paid plans unlimited repositories and change plans to a pricing-per-user model. Individual developers are the most likely customers to benefit from the changes, but many organizations will see an exponential increase in pricing.</p>\n<p>GitLab, a competitor in the Git repository hosting space, immediately addressed disgruntled GitHub customers with a <a href=\"https://about.gitlab.com/2016/05/11/git-repository-pricing/\" target=\"_blank\">pricing comparison</a> on the company&#8217;s blog. Co-founder and CEO <a href=\"https://twitter.com/sytses\" target=\"_blank\">Sid Sijbrandij</a> noted that the three main players in this space, GitHub, Bitbucket, and GitLab, all offer unlimited private repositories but that it doesn&#8217;t cost companies more to host additional repositories for a given user.</p>\n<p>Sijbrandij attributes the change to the increase in the <a href=\"https://www.sequoiacap.com/article/build-us-microservices/\" target=\"_blank\">microservices model</a>, a development approach that breaks software down into smaller, related pieces that communicate with one another via APIs.</p>\n<p>&#8220;As more and more developers, teams, and organizations seek out the advantages of microservices, they’ll need more repositories to support this new code structure,&#8221; Sijbrandij said. &#8220;Basically, the more microservices you have the more repositories you’ll need. That is why it is not surprising that GitHub has announced free private repositories.&#8221;</p>\n<p>Sijbrandij referenced several examples where GitHub&#8217;s pricing changes hit open source organizations hard, including <a href=\"https://github.com/edx/\" target=\"_blank\">Open edX</a>, a non-profit with a large number of contributors, which <a href=\"https://news.ycombinator.com/item?id=11674530\" target=\"_blank\">posted</a> the following on Hacker News:</p>\n<blockquote><p>I work for a non-profit open source organization that <a href=\"https://github.com/edx/\" target=\"_blank\">collaborates on github</a>. We have lots of people who aren&#8217;t employees, but have signed a contributor agreement with our organization and contribute changes to our software. Our bill will go up from $200/month to over $2000/month with this new pricing. We can afford it (it&#8217;s still a small fraction of our AWS bill) but it will force us to look at other alternatives. Github&#8217;s code review tools are already pretty mediocre compared to other tools like gerrit, and we&#8217;ve long since moved off of GitHub issue tracking due to lack of features compared to JIRA.</p></blockquote>\n<p>Sijbrandij emphasized that the team at GitLab believes “everyone can contribute,” a mission which drives GitLab.com&#8217;s pricing structure to offer unlimited private repositories, unlimited contributors, and unlimited CI runners for free. The on-premises solution, which includes enterprise features and support, is what keeps the lights on at the company. GitLab.com, the free, hosted version, runs the same enterprise edition software but is, by Sijbrandij&#8217;s own admission, still <a href=\"https://gitlab.com/gitlab-com/operations/issues/42\" target=\"_blank\">struggling with sluggish performance</a>.</p>\n<p>Earlier this year when open source project maintainers <a href=\"http://wptavern.com/open-source-project-maintainers-confront-github-with-open-letter-on-issue-management\" target=\"_blank\">confronted GitHub with an open letter on issue management</a>, GitLab differentiated itself by <a href=\"http://wptavern.com/gitlab-courts-open-source-project-maintainers-with-response-to-dear-github-letter\" target=\"_blank\">responding</a> to the situation with a new initiative focused on “making GitLab the best place for big open source projects.”</p>\n<p>Nearly a month later, <a href=\"http://wptavern.com/github-responds-to-letter-from-open-source-project-maintainers\" target=\"_blank\">GitHub finally responded</a> with an apology to open source project maintainers and a promise to address their concerns with a steady string of changes.</p>\n<p>GitHub has not given any indication of reversing its recent decision to change its pricing structure. However, with competitors like GitLab putting on the heat, GitHub may be forced to make some changes to its paid plans. At the very least, it could inspire the company to address concerns about organizations having to pay for inactive users and perhaps spur GitHub to offer customers the ability to distinguish between collaborators on open source projects and users who simply need access to private repositories.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 13 May 2016 02:33:33 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:5016:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/gitlab.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/01/gitlab.png?resize=1025%2C371\" alt=\"gitlab\" class=\"aligncenter size-full wp-image-50741\" /></a></p>\n<p>Yesterday GitHub <a href=\"http://wptavern.com/github-introduces-unlimited-private-repositories-hikes-prices-for-organizations\" target=\"_blank\">announced</a> pricing changes that give all paid plans unlimited repositories and change plans to a pricing-per-user model. Individual developers are the most likely customers to benefit from the changes, but many organizations will see an exponential increase in pricing.</p>\n<p>GitLab, a competitor in the Git repository hosting space, immediately addressed disgruntled GitHub customers with a <a href=\"https://about.gitlab.com/2016/05/11/git-repository-pricing/\" target=\"_blank\">pricing comparison</a> on the company&#8217;s blog. Co-founder and CEO <a href=\"https://twitter.com/sytses\" target=\"_blank\">Sid Sijbrandij</a> noted that the three main players in this space, GitHub, Bitbucket, and GitLab, all offer unlimited private repositories but that it doesn&#8217;t cost companies more to host additional repositories for a given user.</p>\n<p>Sijbrandij attributes the change to the increase in the <a href=\"https://www.sequoiacap.com/article/build-us-microservices/\" target=\"_blank\">microservices model</a>, a development approach that breaks software down into smaller, related pieces that communicate with one another via APIs.</p>\n<p>&#8220;As more and more developers, teams, and organizations seek out the advantages of microservices, they’ll need more repositories to support this new code structure,&#8221; Sijbrandij said. &#8220;Basically, the more microservices you have the more repositories you’ll need. That is why it is not surprising that GitHub has announced free private repositories.&#8221;</p>\n<p>Sijbrandij referenced several examples where GitHub&#8217;s pricing changes hit open source organizations hard, including <a href=\"https://github.com/edx/\" target=\"_blank\">Open edX</a>, a non-profit with a large number of contributors, which <a href=\"https://news.ycombinator.com/item?id=11674530\" target=\"_blank\">posted</a> the following on Hacker News:</p>\n<blockquote><p>I work for a non-profit open source organization that <a href=\"https://github.com/edx/\" target=\"_blank\">collaborates on github</a>. We have lots of people who aren&#8217;t employees, but have signed a contributor agreement with our organization and contribute changes to our software. Our bill will go up from $200/month to over $2000/month with this new pricing. We can afford it (it&#8217;s still a small fraction of our AWS bill) but it will force us to look at other alternatives. Github&#8217;s code review tools are already pretty mediocre compared to other tools like gerrit, and we&#8217;ve long since moved off of GitHub issue tracking due to lack of features compared to JIRA.</p></blockquote>\n<p>Sijbrandij emphasized that the team at GitLab believes “everyone can contribute,” a mission which drives GitLab.com&#8217;s pricing structure to offer unlimited private repositories, unlimited contributors, and unlimited CI runners for free. The on-premises solution, which includes enterprise features and support, is what keeps the lights on at the company. GitLab.com, the free, hosted version, runs the same enterprise edition software but is, by Sijbrandij&#8217;s own admission, still <a href=\"https://gitlab.com/gitlab-com/operations/issues/42\" target=\"_blank\">struggling with sluggish performance</a>.</p>\n<p>Earlier this year when open source project maintainers <a href=\"http://wptavern.com/open-source-project-maintainers-confront-github-with-open-letter-on-issue-management\" target=\"_blank\">confronted GitHub with an open letter on issue management</a>, GitLab differentiated itself by <a href=\"http://wptavern.com/gitlab-courts-open-source-project-maintainers-with-response-to-dear-github-letter\" target=\"_blank\">responding</a> to the situation with a new initiative focused on “making GitLab the best place for big open source projects.”</p>\n<p>Nearly a month later, <a href=\"http://wptavern.com/github-responds-to-letter-from-open-source-project-maintainers\" target=\"_blank\">GitHub finally responded</a> with an apology to open source project maintainers and a promise to address their concerns with a steady string of changes.</p>\n<p>GitHub has not given any indication of reversing its recent decision to change its pricing structure. However, with competitors like GitLab putting on the heat, GitHub may be forced to make some changes to its paid plans. At the very least, it could inspire the company to address concerns about organizations having to pay for inactive users and perhaps spur GitHub to offer customers the ability to distinguish between collaborators on open source projects and users who simply need access to private repositories.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:26;a:7:{s:5:\"title\";s:106:\"WPTavern: How Authors With Plugins in the Official Directory Can Use Tags to Get a Moderator’s Attention\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54441\";s:4:\"link\";s:113:\"http://wptavern.com/how-authors-with-plugins-in-the-official-directory-can-use-tags-to-get-a-moderators-attention\";s:11:\"description\";s:2627:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/WordPressAdviceForNewUsers.png\"><img class=\"size-full wp-image-44085\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/WordPressAdviceForNewUsers.png?resize=612%2C237\" alt=\"WordPress Advice For New Users\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/99329675@N02/11064947983\">What You Need To Know About Food Poisoning</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-sa/2.0/\">(license)</a>\n<p>It&#8217;s almost inevitable that as a WordPress plugin gains popularity, it will receive a bad review. How plugin authors handle and respond to bad reviews is crucial, especially in a public forum. Mika Epstein, who helps review plugins before they&#8217;re added to the directory and is a dedicated support forum volunteer, <a href=\"https://make.wordpress.org/plugins/2016/05/03/handling-bad-reviews/\">gives advice </a>on how to handle and respond to bad reviews.</p>\n<p>Bad reviews are classified as those written as spam, trolling, emotional blackmail for support, and those that should have been a support post. Since the plugin review system is powered by bbPress, plugin authors can add tags to reviews in order to draw a moderator&#8217;s attention. The tags include:</p>\n<ul>\n<li><strong>Modlook</strong> &#8211; This tag notifies moderators that a particular thread needs their attention. If you think a review is spam, don&#8217;t respond to it. Instead, add the Modlook and Spam tags and let a moderator decide if the review should be deleted.</li>\n<li><strong>Sockpuppet</strong> &#8211; If you suspect a review is part of a spamming campaign where a group of people are marking a plugin as one or five stars, apply the sockpuppet and modlook tags to the review.</li>\n<li><strong>Wrongplugin</strong> &#8211; Add the wrongplugin tag to the review if you believe it&#8217;s for a different plugin. The team can move the review to the appropriate place.</li>\n<li><strong>Pluginmod</strong> &#8211; Add this tag to a review if you need an administrator&#8217;s attention. This usually results in the team performing a full review of your plugin. If it&#8217;s determined that it breaks any of <a href=\"https://wordpress.org/plugins/about/guidelines/\">the guidelines</a>, it will be removed until they&#8217;re fixed.</li>\n</ul>\n<p>Developers who host plugins in the official directory should make note of these tags and use them when necessary. The tag system is generally unknown to the public but it&#8217;s a great way for moderators to keep on top of the forums and reviews.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 13 May 2016 01:06:02 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:2627:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/WordPressAdviceForNewUsers.png\"><img class=\"size-full wp-image-44085\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/WordPressAdviceForNewUsers.png?resize=612%2C237\" alt=\"WordPress Advice For New Users\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/99329675@N02/11064947983\">What You Need To Know About Food Poisoning</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-sa/2.0/\">(license)</a>\n<p>It&#8217;s almost inevitable that as a WordPress plugin gains popularity, it will receive a bad review. How plugin authors handle and respond to bad reviews is crucial, especially in a public forum. Mika Epstein, who helps review plugins before they&#8217;re added to the directory and is a dedicated support forum volunteer, <a href=\"https://make.wordpress.org/plugins/2016/05/03/handling-bad-reviews/\">gives advice </a>on how to handle and respond to bad reviews.</p>\n<p>Bad reviews are classified as those written as spam, trolling, emotional blackmail for support, and those that should have been a support post. Since the plugin review system is powered by bbPress, plugin authors can add tags to reviews in order to draw a moderator&#8217;s attention. The tags include:</p>\n<ul>\n<li><strong>Modlook</strong> &#8211; This tag notifies moderators that a particular thread needs their attention. If you think a review is spam, don&#8217;t respond to it. Instead, add the Modlook and Spam tags and let a moderator decide if the review should be deleted.</li>\n<li><strong>Sockpuppet</strong> &#8211; If you suspect a review is part of a spamming campaign where a group of people are marking a plugin as one or five stars, apply the sockpuppet and modlook tags to the review.</li>\n<li><strong>Wrongplugin</strong> &#8211; Add the wrongplugin tag to the review if you believe it&#8217;s for a different plugin. The team can move the review to the appropriate place.</li>\n<li><strong>Pluginmod</strong> &#8211; Add this tag to a review if you need an administrator&#8217;s attention. This usually results in the team performing a full review of your plugin. If it&#8217;s determined that it breaks any of <a href=\"https://wordpress.org/plugins/about/guidelines/\">the guidelines</a>, it will be removed until they&#8217;re fixed.</li>\n</ul>\n<p>Developers who host plugins in the official directory should make note of these tags and use them when necessary. The tag system is generally unknown to the public but it&#8217;s a great way for moderators to keep on top of the forums and reviews.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:27;a:7:{s:5:\"title\";s:76:\"WPTavern: WPWeekly Episode 234 – All Things WordCamp with Andrea Middleton\";s:4:\"guid\";s:44:\"http://wptavern.com?p=54807&preview_id=54807\";s:4:\"link\";s:82:\"http://wptavern.com/wpweekly-episode-234-all-things-wordcamp-with-andrea-middleton\";s:11:\"description\";s:2896:\"<p>In this episode of WordPress Weekly, Marcus Couch and I are joined by <a href=\"https://thethingwiththestuff.wordpress.com/\">Andrea Middleton</a>, who works at Automattic as a Community Organizer for the WordPress open source project. We discuss a number of topics including, updates to the WordCamp Central website, the <a href=\"https://make.wordpress.org/community/2016/03/02/transitioning-to-wordpress-community-support/\">for-profit subsidiary</a>, and the experimental <a href=\"http://wptavern.com/wordpress-to-launch-experimental-wordcamp-incubator-program\">WordCamp incubator program</a>.</p>\n<p>At the conclusion of our interview with Middleton, Mendel Kurland, GoDaddy&#8217;s Evangelist, joined us to describe his experiences attending DrupalCons. DrupalCons are events similar to WordCamps but on a larger scale. He tells us what the similarities and differences are and the unique things they do that he&#8217;d like to see WordCamps adopt. We close out the show with Marcus&#8217; plugin picks of the week.</p>\n<h2>Stories Discussed:</h2>\n<p><a href=\"http://wptavern.com/wordpress-4-5-2-patches-two-security-vulnerabilities\">WordPress 4.5.2 Patches Two Security Vulnerabilities</a><br />\n<a href=\"http://wptavern.com/automattic-is-protecting-its-woo-woothemes-and-woocommerce-trademarks\">Automattic is Protecting its Woo, WooThemes, and WooCommerce Trademarks</a></p>\n<h2>Plugins Picked By Marcus:</h2>\n<p><a href=\"https://wordpress.org/plugins/disable-core-update-email/\">Disable WordPress Core Update Email</a> allows used to disable the default notification email sent by WordPress after an automatic core update is applied.</p>\n<p><a href=\"https://wordpress.org/plugins/downgrade/\">Downgrade </a>enables users to easily downgrade WordPress to an earlier version. It&#8217;s a handy diagnostics tool that helps determine if a new WordPress release is the cause of errors.</p>\n<p><a href=\"https://wordpress.org/plugins/woo-customer-insight\">Woo Customer Insight </a>provides greater insight into what visitors are doing on your sites. It allows you to see the pages your customers are visiting, where they&#8217;re clicking, the time spent on the different pages, and more.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, May 18th 9:30 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href=\"https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href=\"http://www.wptavern.com/feed/podcast\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href=\"http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #234:</strong><br />\n</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 12 May 2016 23:23:19 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:2896:\"<p>In this episode of WordPress Weekly, Marcus Couch and I are joined by <a href=\"https://thethingwiththestuff.wordpress.com/\">Andrea Middleton</a>, who works at Automattic as a Community Organizer for the WordPress open source project. We discuss a number of topics including, updates to the WordCamp Central website, the <a href=\"https://make.wordpress.org/community/2016/03/02/transitioning-to-wordpress-community-support/\">for-profit subsidiary</a>, and the experimental <a href=\"http://wptavern.com/wordpress-to-launch-experimental-wordcamp-incubator-program\">WordCamp incubator program</a>.</p>\n<p>At the conclusion of our interview with Middleton, Mendel Kurland, GoDaddy&#8217;s Evangelist, joined us to describe his experiences attending DrupalCons. DrupalCons are events similar to WordCamps but on a larger scale. He tells us what the similarities and differences are and the unique things they do that he&#8217;d like to see WordCamps adopt. We close out the show with Marcus&#8217; plugin picks of the week.</p>\n<h2>Stories Discussed:</h2>\n<p><a href=\"http://wptavern.com/wordpress-4-5-2-patches-two-security-vulnerabilities\">WordPress 4.5.2 Patches Two Security Vulnerabilities</a><br />\n<a href=\"http://wptavern.com/automattic-is-protecting-its-woo-woothemes-and-woocommerce-trademarks\">Automattic is Protecting its Woo, WooThemes, and WooCommerce Trademarks</a></p>\n<h2>Plugins Picked By Marcus:</h2>\n<p><a href=\"https://wordpress.org/plugins/disable-core-update-email/\">Disable WordPress Core Update Email</a> allows used to disable the default notification email sent by WordPress after an automatic core update is applied.</p>\n<p><a href=\"https://wordpress.org/plugins/downgrade/\">Downgrade </a>enables users to easily downgrade WordPress to an earlier version. It&#8217;s a handy diagnostics tool that helps determine if a new WordPress release is the cause of errors.</p>\n<p><a href=\"https://wordpress.org/plugins/woo-customer-insight\">Woo Customer Insight </a>provides greater insight into what visitors are doing on your sites. It allows you to see the pages your customers are visiting, where they&#8217;re clicking, the time spent on the different pages, and more.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, May 18th 9:30 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href=\"https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href=\"http://www.wptavern.com/feed/podcast\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href=\"http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #234:</strong><br />\n</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:28;a:7:{s:5:\"title\";s:11:\"Matt: .Blog\";s:4:\"guid\";s:22:\"https://ma.tt/?p=46554\";s:4:\"link\";s:27:\"https://ma.tt/2016/05/blog/\";s:11:\"description\";s:858:\"<p>It&#8217;s now public that Automattic is the company behind Knock Knock Whois There LLC, the registry for the new .blog TLD. (And a great pun.) We wanted to stay stealth while in the bidding process and afterward in order not to draw too much attention, but nonetheless the cost of the .blog auction got up there (people are <a href=\"http://www.theregister.co.uk/2015/02/13/who_just_bought_dotblog_for_30m/\">estimating around $20M</a>). I&#8217;m excited we won and think that it will be both an amazing business going forward and give lots of folks an opportunity to have a fantastic domain name in a new namespace and with an easy-to-say TLD. <a href=\"https://dotblog.wordpress.com/\">You can sign up to be first in line to reserve a domain here</a>. If you have a trademark you can get in August, and then October for the &#8220;land rush.&#8221;</p>\";s:7:\"pubdate\";s:31:\"Thu, 12 May 2016 19:23:11 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:858:\"<p>It&#8217;s now public that Automattic is the company behind Knock Knock Whois There LLC, the registry for the new .blog TLD. (And a great pun.) We wanted to stay stealth while in the bidding process and afterward in order not to draw too much attention, but nonetheless the cost of the .blog auction got up there (people are <a href=\"http://www.theregister.co.uk/2015/02/13/who_just_bought_dotblog_for_30m/\">estimating around $20M</a>). I&#8217;m excited we won and think that it will be both an amazing business going forward and give lots of folks an opportunity to have a fantastic domain name in a new namespace and with an easy-to-say TLD. <a href=\"https://dotblog.wordpress.com/\">You can sign up to be first in line to reserve a domain here</a>. If you have a trademark you can get in August, and then October for the &#8220;land rush.&#8221;</p>\";}i:29;a:7:{s:5:\"title\";s:84:\"WPTavern: Automattic to Oversee the Sale and Registration of Top-Level .Blog Domains\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54788\";s:4:\"link\";s:93:\"http://wptavern.com/automattic-to-oversee-the-sale-and-registration-of-top-level-blog-domains\";s:11:\"description\";s:2974:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg?resize=960%2C521\" alt=\"photo credit: Luis Llerena\" class=\"size-full wp-image-54799\" /></a>photo credit: <a href=\"https://stocksnap.io/photo/3ZHG0XOIT6\">Luis Llerena</a>\n<p>Automattic <a href=\"https://en.blog.wordpress.com/2016/05/12/coming-soon-new-blog-domains-for-websites/\" target=\"_blank\">announced</a> today that it will begin offering top-level .blog domain registration starting in August 2016. The .blog domain extension will be available to both WordPress and non-WordPress sites.</p>\n<p>According to <a href=\"https://twitter.com/markarms\" target=\"_blank\">Mark Armstrong</a>, an Automattic subsidiary is exclusively managing the registration of .blog domains and will be offering it for purchase through WordPress.com and other domain registrars.</p>\n<p>&#8220;Automattic subsidiary Knock Knock Whois There LLC, in partnership with the domain company Primer Nivel, won the rights to the .blog domain in 2015 through an auction process overseen by the Internet Corporation for Assigned Names and Numbers (ICANN), the non profit organization that oversees namespaces of the internet,&#8221; Armstrong said.</p>\n<p>In an <a href=\"https://ma.tt/2016/05/blog/\" target=\"_blank\">announcement</a> on his blog, Automattic CEO Matt Mullenweg said they used the Knock Knock Whois There LLC company name to &#8220;stay stealth while in the bidding process,&#8221; which closed around $19 million.</p>\n<p>Although WordPress.com is currently providing the registration information site at <a href=\"https://dotblog.wordpress.com/\" target=\"_blank\">dotblog.wordpress.com</a>, Armstrong said that the company is using <a href=\"http://www.nominet.uk/\" target=\"_blank\">Nominet</a> (the backend registry provider for .UK) to provide the technical infrastructure for managing the domain extension.</p>\n<p>Registration for .blog domains will be offered in a phased approach during the second half of 2016, according to the following estimated timeframe:</p>\n<ul>\n<li><strong>Sunrise (August):</strong> Trademark owners will be able to register .blog domains associated with their brands</li>\n<li><strong>Landrush (October):</strong> Before .blog becomes available to the public, domains may be registered during the landrush period on an application basis.</li>\n<li><strong>General Availability (November):</strong> Automattic plans to begin offering .blog domains to the general public before the end of the year.</li>\n</ul>\n<p>With the exclusive rights to manage the sale of millions of .blog domains, Automattic has the opportunity to promote WordPress.com as a potential host for new registrants. The company hasn&#8217;t finalized the price but Armstrong said it will be &#8220;in the standard range for new top-level domains with some premium pricing for higher-value names.&#8221;</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 12 May 2016 18:19:44 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2974:\"<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/blogging.jpg?resize=960%2C521\" alt=\"photo credit: Luis Llerena\" class=\"size-full wp-image-54799\" /></a>photo credit: <a href=\"https://stocksnap.io/photo/3ZHG0XOIT6\">Luis Llerena</a>\n<p>Automattic <a href=\"https://en.blog.wordpress.com/2016/05/12/coming-soon-new-blog-domains-for-websites/\" target=\"_blank\">announced</a> today that it will begin offering top-level .blog domain registration starting in August 2016. The .blog domain extension will be available to both WordPress and non-WordPress sites.</p>\n<p>According to <a href=\"https://twitter.com/markarms\" target=\"_blank\">Mark Armstrong</a>, an Automattic subsidiary is exclusively managing the registration of .blog domains and will be offering it for purchase through WordPress.com and other domain registrars.</p>\n<p>&#8220;Automattic subsidiary Knock Knock Whois There LLC, in partnership with the domain company Primer Nivel, won the rights to the .blog domain in 2015 through an auction process overseen by the Internet Corporation for Assigned Names and Numbers (ICANN), the non profit organization that oversees namespaces of the internet,&#8221; Armstrong said.</p>\n<p>In an <a href=\"https://ma.tt/2016/05/blog/\" target=\"_blank\">announcement</a> on his blog, Automattic CEO Matt Mullenweg said they used the Knock Knock Whois There LLC company name to &#8220;stay stealth while in the bidding process,&#8221; which closed around $19 million.</p>\n<p>Although WordPress.com is currently providing the registration information site at <a href=\"https://dotblog.wordpress.com/\" target=\"_blank\">dotblog.wordpress.com</a>, Armstrong said that the company is using <a href=\"http://www.nominet.uk/\" target=\"_blank\">Nominet</a> (the backend registry provider for .UK) to provide the technical infrastructure for managing the domain extension.</p>\n<p>Registration for .blog domains will be offered in a phased approach during the second half of 2016, according to the following estimated timeframe:</p>\n<ul>\n<li><strong>Sunrise (August):</strong> Trademark owners will be able to register .blog domains associated with their brands</li>\n<li><strong>Landrush (October):</strong> Before .blog becomes available to the public, domains may be registered during the landrush period on an application basis.</li>\n<li><strong>General Availability (November):</strong> Automattic plans to begin offering .blog domains to the general public before the end of the year.</li>\n</ul>\n<p>With the exclusive rights to manage the sale of millions of .blog domains, Automattic has the opportunity to promote WordPress.com as a potential host for new registrants. The company hasn&#8217;t finalized the price but Armstrong said it will be &#8220;in the standard range for new top-level domains with some premium pricing for higher-value names.&#8221;</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:30;a:7:{s:5:\"title\";s:78:\"WPTavern: Critical Vulnerabilities Found in PhpStorm, Immediate Update Advised\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54770\";s:4:\"link\";s:87:\"http://wptavern.com/critical-vulnerabilities-found-in-phpstorm-immediate-update-advised\";s:11:\"description\";s:2128:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/09/phpstorm-wp-feature.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/09/phpstorm-wp-feature.jpg?resize=1025%2C471\" alt=\"phpstorm-wp-feature\" class=\"aligncenter size-full wp-image-30739\" /></a></p>\n<p>JetBrains <a href=\"http://blog.jetbrains.com/blog/2016/05/11/security-update-for-intellij-based-ides-v2016-1-and-older-versions/\" target=\"_blank\">announced</a> today that it has released a security update for PhpStorm and all of its other IntelliJ-based IDEs due to a set of critical vulnerabilities:</p>\n<blockquote><p>The cross-site request forgery (CSRF) flaw in the IDE’s built-in webserver allowed an attacker to access local file system from a malicious web page without user consent.</p>\n<p>Over-permissive CORS settings allowed attackers to use a malicious website in order to access various internal API endpoints, gain access to data saved by the IDE, and gather various meta-information like IDE version or open a project.</p></blockquote>\n<p>PhpStorm is by far <a href=\"http://www.sitepoint.com/best-php-ide-2014-survey-results/\" target=\"_blank\">the most favored IDE for PHP developers</a>. It&#8217;s also widely used among WordPress developers, especially since <a href=\"http://wptavern.com/phpstorm-8-released-with-full-wordpress-support\" target=\"_blank\">version 8 added official support for WordPress</a>.</p>\n<p>The update issued today patches the critical vulnerabilities inside the underlying IntelliJ platform that powers nearly a dozen popular IDEs. Installing the update is as easy as selecting &#8216;Check for Updates&#8217; inside the IDE. Alternatively, customers can download the most recent version from JetBrains.com and the <a href=\"http://blog.jetbrains.com/blog/2016/05/11/security-update-for-intellij-based-ides-v2016-1-and-older-versions/\" target=\"_blank\">security announcement</a> includes links to download older versions.</p>\n<p>Although the JetBrains security team is not aware of these vulnerabilities having been exploited, immediate update is recommended.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 11 May 2016 22:26:43 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2128:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/09/phpstorm-wp-feature.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2014/09/phpstorm-wp-feature.jpg?resize=1025%2C471\" alt=\"phpstorm-wp-feature\" class=\"aligncenter size-full wp-image-30739\" /></a></p>\n<p>JetBrains <a href=\"http://blog.jetbrains.com/blog/2016/05/11/security-update-for-intellij-based-ides-v2016-1-and-older-versions/\" target=\"_blank\">announced</a> today that it has released a security update for PhpStorm and all of its other IntelliJ-based IDEs due to a set of critical vulnerabilities:</p>\n<blockquote><p>The cross-site request forgery (CSRF) flaw in the IDE’s built-in webserver allowed an attacker to access local file system from a malicious web page without user consent.</p>\n<p>Over-permissive CORS settings allowed attackers to use a malicious website in order to access various internal API endpoints, gain access to data saved by the IDE, and gather various meta-information like IDE version or open a project.</p></blockquote>\n<p>PhpStorm is by far <a href=\"http://www.sitepoint.com/best-php-ide-2014-survey-results/\" target=\"_blank\">the most favored IDE for PHP developers</a>. It&#8217;s also widely used among WordPress developers, especially since <a href=\"http://wptavern.com/phpstorm-8-released-with-full-wordpress-support\" target=\"_blank\">version 8 added official support for WordPress</a>.</p>\n<p>The update issued today patches the critical vulnerabilities inside the underlying IntelliJ platform that powers nearly a dozen popular IDEs. Installing the update is as easy as selecting &#8216;Check for Updates&#8217; inside the IDE. Alternatively, customers can download the most recent version from JetBrains.com and the <a href=\"http://blog.jetbrains.com/blog/2016/05/11/security-update-for-intellij-based-ides-v2016-1-and-older-versions/\" target=\"_blank\">security announcement</a> includes links to download older versions.</p>\n<p>Although the JetBrains security team is not aware of these vulnerabilities having been exploited, immediate update is recommended.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:31;a:7:{s:5:\"title\";s:90:\"WPTavern: GitHub Introduces Unlimited Private Repositories, Hikes Prices for Organizations\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54746\";s:4:\"link\";s:99:\"http://wptavern.com/github-introduces-unlimited-private-repositories-hikes-prices-for-organizations\";s:11:\"description\";s:7590:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/04/github-octocat.jpg\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/04/github-octocat.jpg?resize=857%2C400\" alt=\"github-octocat\" class=\"aligncenter size-full wp-image-42456\" /></a></p>\n<p>GitHub has been inundated with negative feedback after <a href=\"https://github.com/blog/2164-introducing-unlimited-private-repositories\" target=\"_blank\">announcing a major change to its pricing</a> today. All paid plans now include unlimited private repositories, but there&#8217;s a catch. The new pricing structure requires GitHub.com organizations to purchase a seat for each user. At $9 per user/month, collaborating on private repositories is now far more costly than the legacy plans which started at $25/month for 10 repositories and unlimited members.</p>\n<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/github-pricing.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/github-pricing.png?resize=1025%2C392\" alt=\"github-pricing\" class=\"aligncenter size-full wp-image-54756\" /></a></p>\n<p>The change is good news for individual developers with paid accounts, as they are no longer charged on a per-repository basis. However, many owners of organizations are finding the new pricing to be untenable and are actively considering alternatives. For comparison, Bitbucket offers unlimited private repositories and <a href=\"https://bitbucket.org/product/pricing\" target=\"_blank\">charges $1/user/month</a>. Unlimited users caps out at $200/month.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/Krogsgard\">@Krogsgard</a> EDD org alone will go from $25 per month to $592 per month <a href=\"https://twitter.com/github\">@github</a></p>\n<p>&mdash; Pippinsplugins (@pippinsplugins) <a href=\"https://twitter.com/pippinsplugins/status/730396802638176257\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p>While unlimited private repositories is an exciting benefit that enables developers to make their code more modular, it isn&#8217;t a benefit that every organization needs.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/github\">@github</a> Terrible news. I work on an open-source organization &gt;100 devs. We have 2 private repos for internal projects. $900+ vs $25 really!?</p>\n<p>&mdash; João Ventura (@jcnventura) <a href=\"https://twitter.com/jcnventura/status/730319187667759104\">May 11, 2016</a></p></blockquote>\n<p></p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/williamsba\">@williamsba</a> ours jumped to $1,204 :-( <a href=\"https://twitter.com/github\">@github</a></p>\n<p>&mdash; Tom Willmot (@tomwillmot) <a href=\"https://twitter.com/tomwillmot/status/730391291691995136\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p><a href=\"https://easydigitaldownloads.com/\" target=\"_blank\">Easy Digital Downloads</a> creator Pippin Williamson <a href=\"http://www.twitlonger.com/show/n_1solvjd\" target=\"_blank\">explained</a> why he is frustrated with what amounts to a 2,276% increase in costs for his organization:</p>\n<blockquote><p>I actually have no problems with the pricing for new organizations. It&#8217;s their space and they provide a huge number of valuable tools. It is absolutely worth it.</p>\n<p>The problem I have is the drastic increase for existing customers. It&#8217;s largely the principal of increasing a customer&#8217;s cost by 2,276% without giving them any additional value.</p>\n<p>The value that Github provides me and my team does not change at all with the new pricing, only what I pay per month.</p></blockquote>\n<p>Samuel &#8220;Otto&#8221; Wood <a href=\"http://www.twitlonger.com/show/n_1solviv\" target=\"_blank\">contends</a> that GitHub&#8217;s $9/user/month is a reasonable price to pay for having all the functionality of GitHub hosted for an organization but that the alternative of building your own is far more economical.</p>\n<blockquote><p>A &#8220;private&#8221; repo is, you know, private. On your own server. Git is, after all, decentralized. You could plop a normal git repo on any private VPS you like in a matter of under an hour. If you&#8217;re collaborating with a small group of like 5 people, then coordination is not really a big deal that I&#8217;d pay $45 a month to use GitHub for it. You can use any tooling you like, make any website you like. You could probably reproduce the important parts of GitHub that you need for your private setup using WordPress in like a day or two. </p>\n<p>It just seems to me that any advantages of using GitHub at all seem largely nullified by using private repos. Yes, collaboration and using the same toolset you are used to, I get that. But here you&#8217;re falling prey to vendor lock-in once again. You&#8217;re used to it, you like it, you&#8217;re afraid of change, pay up. Simple. </p>\n<p>The advantage of open source software is the freedom to say &#8220;up yours&#8221; and build your own version instead. Git is open source. Think about it. A $15 a month VPS could easily fit your needs for both privacy and collaboration.</p></blockquote>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/github\">@github</a> found a way to be more expensive than the datacenter that runs my app. Seriously, what\'s happening at <a href=\"https://twitter.com/github\">@github</a> ???</p>\n<p>&mdash; Adilson Carvalho (@lcadilson) <a href=\"https://twitter.com/lcadilson/status/730405070819471361\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p>GitHub has established itself as the de facto code collaboration site by offering free hosting for public, open source repositories. However, the emphasis on &#8220;social coding&#8221; no longer extends to private repositories as organization owners will have little incentive to add more collaborators under the new pricing structure. It discourages organizations from adding users to be bug reporters or third-party collaborators. Teams and agencies hit hardest by the changes are now examining competitors like Bitbucket and self-hosted GitLab.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Today is for <a href=\"https://twitter.com/gitlab\">@gitlab</a> what 2007 was for <a href=\"https://twitter.com/WordPress\">@WordPress</a>. If code is poetry, Gitlab is your library. Own your code like you own your content. ??</p>\n<p>&mdash; John James Jacoby (@JJJ) <a href=\"https://twitter.com/JJJ/status/730417868047790080\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p>Organization owners will not be forced onto the new pricing plans immediately and GitHub promises to give a year&#8217;s notice before mandating a switch to the new plans:</p>\n<blockquote><p>We want everyone to have a plan with unlimited private repositories, but don’t worry—you are welcome to stay on your current plan while you evaluate the new cost structure and understand how to best manage your organization members and their private repository access. And while we&#8217;re currently not enforcing a timeline to move, rest assured that you&#8217;ll have at least 12 months notice before any mandated change to your plan.</p></blockquote>\n<p>While many individual developers will see lower monthly prices and even prorated credits on their accounts, the exponential cost increase for GitHub&#8217;s largest customers may cause a mass exodus to the company&#8217;s more affordable competitors. Are you moving your organization off of GitHub? Let us know in the comments.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 11 May 2016 19:27:29 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:7590:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/04/github-octocat.jpg\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/04/github-octocat.jpg?resize=857%2C400\" alt=\"github-octocat\" class=\"aligncenter size-full wp-image-42456\" /></a></p>\n<p>GitHub has been inundated with negative feedback after <a href=\"https://github.com/blog/2164-introducing-unlimited-private-repositories\" target=\"_blank\">announcing a major change to its pricing</a> today. All paid plans now include unlimited private repositories, but there&#8217;s a catch. The new pricing structure requires GitHub.com organizations to purchase a seat for each user. At $9 per user/month, collaborating on private repositories is now far more costly than the legacy plans which started at $25/month for 10 repositories and unlimited members.</p>\n<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/github-pricing.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/github-pricing.png?resize=1025%2C392\" alt=\"github-pricing\" class=\"aligncenter size-full wp-image-54756\" /></a></p>\n<p>The change is good news for individual developers with paid accounts, as they are no longer charged on a per-repository basis. However, many owners of organizations are finding the new pricing to be untenable and are actively considering alternatives. For comparison, Bitbucket offers unlimited private repositories and <a href=\"https://bitbucket.org/product/pricing\" target=\"_blank\">charges $1/user/month</a>. Unlimited users caps out at $200/month.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/Krogsgard\">@Krogsgard</a> EDD org alone will go from $25 per month to $592 per month <a href=\"https://twitter.com/github\">@github</a></p>\n<p>&mdash; Pippinsplugins (@pippinsplugins) <a href=\"https://twitter.com/pippinsplugins/status/730396802638176257\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p>While unlimited private repositories is an exciting benefit that enables developers to make their code more modular, it isn&#8217;t a benefit that every organization needs.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/github\">@github</a> Terrible news. I work on an open-source organization &gt;100 devs. We have 2 private repos for internal projects. $900+ vs $25 really!?</p>\n<p>&mdash; João Ventura (@jcnventura) <a href=\"https://twitter.com/jcnventura/status/730319187667759104\">May 11, 2016</a></p></blockquote>\n<p></p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/williamsba\">@williamsba</a> ours jumped to $1,204 :-( <a href=\"https://twitter.com/github\">@github</a></p>\n<p>&mdash; Tom Willmot (@tomwillmot) <a href=\"https://twitter.com/tomwillmot/status/730391291691995136\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p><a href=\"https://easydigitaldownloads.com/\" target=\"_blank\">Easy Digital Downloads</a> creator Pippin Williamson <a href=\"http://www.twitlonger.com/show/n_1solvjd\" target=\"_blank\">explained</a> why he is frustrated with what amounts to a 2,276% increase in costs for his organization:</p>\n<blockquote><p>I actually have no problems with the pricing for new organizations. It&#8217;s their space and they provide a huge number of valuable tools. It is absolutely worth it.</p>\n<p>The problem I have is the drastic increase for existing customers. It&#8217;s largely the principal of increasing a customer&#8217;s cost by 2,276% without giving them any additional value.</p>\n<p>The value that Github provides me and my team does not change at all with the new pricing, only what I pay per month.</p></blockquote>\n<p>Samuel &#8220;Otto&#8221; Wood <a href=\"http://www.twitlonger.com/show/n_1solviv\" target=\"_blank\">contends</a> that GitHub&#8217;s $9/user/month is a reasonable price to pay for having all the functionality of GitHub hosted for an organization but that the alternative of building your own is far more economical.</p>\n<blockquote><p>A &#8220;private&#8221; repo is, you know, private. On your own server. Git is, after all, decentralized. You could plop a normal git repo on any private VPS you like in a matter of under an hour. If you&#8217;re collaborating with a small group of like 5 people, then coordination is not really a big deal that I&#8217;d pay $45 a month to use GitHub for it. You can use any tooling you like, make any website you like. You could probably reproduce the important parts of GitHub that you need for your private setup using WordPress in like a day or two. </p>\n<p>It just seems to me that any advantages of using GitHub at all seem largely nullified by using private repos. Yes, collaboration and using the same toolset you are used to, I get that. But here you&#8217;re falling prey to vendor lock-in once again. You&#8217;re used to it, you like it, you&#8217;re afraid of change, pay up. Simple. </p>\n<p>The advantage of open source software is the freedom to say &#8220;up yours&#8221; and build your own version instead. Git is open source. Think about it. A $15 a month VPS could easily fit your needs for both privacy and collaboration.</p></blockquote>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/github\">@github</a> found a way to be more expensive than the datacenter that runs my app. Seriously, what\'s happening at <a href=\"https://twitter.com/github\">@github</a> ???</p>\n<p>&mdash; Adilson Carvalho (@lcadilson) <a href=\"https://twitter.com/lcadilson/status/730405070819471361\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p>GitHub has established itself as the de facto code collaboration site by offering free hosting for public, open source repositories. However, the emphasis on &#8220;social coding&#8221; no longer extends to private repositories as organization owners will have little incentive to add more collaborators under the new pricing structure. It discourages organizations from adding users to be bug reporters or third-party collaborators. Teams and agencies hit hardest by the changes are now examining competitors like Bitbucket and self-hosted GitLab.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">Today is for <a href=\"https://twitter.com/gitlab\">@gitlab</a> what 2007 was for <a href=\"https://twitter.com/WordPress\">@WordPress</a>. If code is poetry, Gitlab is your library. Own your code like you own your content. ??</p>\n<p>&mdash; John James Jacoby (@JJJ) <a href=\"https://twitter.com/JJJ/status/730417868047790080\">May 11, 2016</a></p></blockquote>\n<p></p>\n<p>Organization owners will not be forced onto the new pricing plans immediately and GitHub promises to give a year&#8217;s notice before mandating a switch to the new plans:</p>\n<blockquote><p>We want everyone to have a plan with unlimited private repositories, but don’t worry—you are welcome to stay on your current plan while you evaluate the new cost structure and understand how to best manage your organization members and their private repository access. And while we&#8217;re currently not enforcing a timeline to move, rest assured that you&#8217;ll have at least 12 months notice before any mandated change to your plan.</p></blockquote>\n<p>While many individual developers will see lower monthly prices and even prorated credits on their accounts, the exponential cost increase for GitHub&#8217;s largest customers may cause a mass exodus to the company&#8217;s more affordable competitors. Are you moving your organization off of GitHub? Let us know in the comments.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:32;a:7:{s:5:\"title\";s:66:\"WPTavern: Affinity: A Free WordPress Wedding Theme from Automattic\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54688\";s:4:\"link\";s:75:\"http://wptavern.com/affinity-a-free-wordpress-wedding-theme-from-automattic\";s:11:\"description\";s:3832:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity.png?resize=800%2C471\" alt=\"affinity\" class=\"aligncenter size-full wp-image-54691\" /></a></p>\n<p>Affinity is the latest addition to WordPress.com&#8217;s small collection of <a href=\"https://wordpress.com/themes/search/wedding/\" target=\"_blank\">themes created specifically for weddings</a>. This highly customizable, elegant theme was designed by <a href=\"http://carolinemoore.net/\" target=\"_blank\">Caroline Moore</a> with weddings and family announcements in mind.</p>\n<p>Affinity is a one-page theme with support for five different panels. Each panel&#8217;s content can be assigned in the customizer under Theme Options by selecting a page from a drop-down.</p>\n<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/panel.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/panel.png?resize=660%2C231\" alt=\"panel\" class=\"aligncenter size-full wp-image-54717\" /></a></p>\n<p>With the customizable panel approach users are not locked into providing content for sections they don&#8217;t need. Single posts and pages support full screen featured images that, if used as a panel, become the background of that section. Affinity offers the option to set the header image opacity to create better contrast with header text. Users can also enable or disable scrolling on the header and front-page featured images.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-home-page.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-home-page.png?resize=200%2C474\" alt=\"affinity-home-page\" class=\"alignright size-full wp-image-54693\" /></a></p>\n<p>Affinity includes support for a sidebar widget area and three optional widget areas in the footer. If widgets are added to the sidebar, the one-column layout becomes a two-column layout. It also has a fullwidth page template for removing the sidebar on select pages.</p>\n<p>The different panels give users ample space for adding photos, links to registries, personal stories, info about the bridal party, and anything else related to the event. Affinity includes a Guestbook page template with a special format for displaying visitors&#8217; comments. Turning the Guestbook on is as easy as setting the page template and making sure that comments are enabled.</p>\n<p>Another unique feature of the theme is its post intro area that displays beneath the headline before the first paragraph. It pulls content from the excerpt field and post authors can use it to capture readers&#8217; attention with a quick summary or highlight.</p>\n<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-post-intro.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-post-intro.png?resize=660%2C328\" alt=\"affinity-post-intro\" class=\"aligncenter size-full wp-image-54729\" /></a></p>\n<p>Check out the <a href=\"https://affinitydemo.wordpress.com/\" target=\"_blank\">live demo</a> to see the theme in action. It shows an example of panels that display quotes, an RSVP form, event details, and an engagement story.</p>\n<p>Since no wedding or family announcement is the same, Affinity&#8217;s multi-panel approach offers flexibility for many different types of uses. If you&#8217;re creating a wedding website and are not finding enough customization options with a hosted service, this theme makes it quick and easy to set it up with WordPress. It&#8217;s not yet available on WordPress.org, but you can download a copy for your self-hosted site for free from the sidebar of its <a href=\"https://wordpress.com/themes/affinity\" target=\"_blank\">homepage on WordPress.com</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 11 May 2016 06:52:35 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:3832:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity.png?resize=800%2C471\" alt=\"affinity\" class=\"aligncenter size-full wp-image-54691\" /></a></p>\n<p>Affinity is the latest addition to WordPress.com&#8217;s small collection of <a href=\"https://wordpress.com/themes/search/wedding/\" target=\"_blank\">themes created specifically for weddings</a>. This highly customizable, elegant theme was designed by <a href=\"http://carolinemoore.net/\" target=\"_blank\">Caroline Moore</a> with weddings and family announcements in mind.</p>\n<p>Affinity is a one-page theme with support for five different panels. Each panel&#8217;s content can be assigned in the customizer under Theme Options by selecting a page from a drop-down.</p>\n<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/panel.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/panel.png?resize=660%2C231\" alt=\"panel\" class=\"aligncenter size-full wp-image-54717\" /></a></p>\n<p>With the customizable panel approach users are not locked into providing content for sections they don&#8217;t need. Single posts and pages support full screen featured images that, if used as a panel, become the background of that section. Affinity offers the option to set the header image opacity to create better contrast with header text. Users can also enable or disable scrolling on the header and front-page featured images.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-home-page.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-home-page.png?resize=200%2C474\" alt=\"affinity-home-page\" class=\"alignright size-full wp-image-54693\" /></a></p>\n<p>Affinity includes support for a sidebar widget area and three optional widget areas in the footer. If widgets are added to the sidebar, the one-column layout becomes a two-column layout. It also has a fullwidth page template for removing the sidebar on select pages.</p>\n<p>The different panels give users ample space for adding photos, links to registries, personal stories, info about the bridal party, and anything else related to the event. Affinity includes a Guestbook page template with a special format for displaying visitors&#8217; comments. Turning the Guestbook on is as easy as setting the page template and making sure that comments are enabled.</p>\n<p>Another unique feature of the theme is its post intro area that displays beneath the headline before the first paragraph. It pulls content from the excerpt field and post authors can use it to capture readers&#8217; attention with a quick summary or highlight.</p>\n<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-post-intro.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/affinity-post-intro.png?resize=660%2C328\" alt=\"affinity-post-intro\" class=\"aligncenter size-full wp-image-54729\" /></a></p>\n<p>Check out the <a href=\"https://affinitydemo.wordpress.com/\" target=\"_blank\">live demo</a> to see the theme in action. It shows an example of panels that display quotes, an RSVP form, event details, and an engagement story.</p>\n<p>Since no wedding or family announcement is the same, Affinity&#8217;s multi-panel approach offers flexibility for many different types of uses. If you&#8217;re creating a wedding website and are not finding enough customization options with a hosted service, this theme makes it quick and easy to set it up with WordPress. It&#8217;s not yet available on WordPress.org, but you can download a copy for your self-hosted site for free from the sidebar of its <a href=\"https://wordpress.com/themes/affinity\" target=\"_blank\">homepage on WordPress.com</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:33;a:7:{s:5:\"title\";s:77:\"WPTavern: Help WPCampus Gather Data on How Schools and Campuses Use WordPress\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54650\";s:4:\"link\";s:87:\"http://wptavern.com/help-wpcampus-gather-data-on-how-schools-and-campuses-use-wordpress\";s:11:\"description\";s:1247:\"<p>The organizers of <a href=\"https://2016.wpcampus.org/\">WPCampus</a> are <a href=\"https://www.surveymonkey.com/r/wpcampus05-2016\">seeking feedback</a> via a survey on how schools and campuses utilize WordPress in their environments. The survey consists of five sections:</p>\n<ul>\n<li>How Do You Use WordPress on Campus</li>\n<li>Site Demographics, Traffic, and Data</li>\n<li>Plugins, Themes, and Features</li>\n<li>Security, Performance, and Hosting</li>\n<li>Your Team Structure &amp; Workflows</li>\n</ul>\n<p>There are a couple of perks for those who fill out the survey. Respondents will receive an anonymized version of the complete data set. Those who complete four or more sections will be entered into a drawing to win a free ticket to the conference and will receive a $5 Starbucks or Amazon Gift card.</p>\n<p>Answer the questions that you know and skip the ones you don&#8217;t. The team needs as much data as possible to provide a clearer picture of WordPress&#8217; use in higher education. If you know someone or an organization that uses WordPress in higher education, please <a href=\"https://www.surveymonkey.com/r/wpcampus05-2016\">share the survey</a> with them. The survey closes on May 27th.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 11 May 2016 03:21:06 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:1247:\"<p>The organizers of <a href=\"https://2016.wpcampus.org/\">WPCampus</a> are <a href=\"https://www.surveymonkey.com/r/wpcampus05-2016\">seeking feedback</a> via a survey on how schools and campuses utilize WordPress in their environments. The survey consists of five sections:</p>\n<ul>\n<li>How Do You Use WordPress on Campus</li>\n<li>Site Demographics, Traffic, and Data</li>\n<li>Plugins, Themes, and Features</li>\n<li>Security, Performance, and Hosting</li>\n<li>Your Team Structure &amp; Workflows</li>\n</ul>\n<p>There are a couple of perks for those who fill out the survey. Respondents will receive an anonymized version of the complete data set. Those who complete four or more sections will be entered into a drawing to win a free ticket to the conference and will receive a $5 Starbucks or Amazon Gift card.</p>\n<p>Answer the questions that you know and skip the ones you don&#8217;t. The team needs as much data as possible to provide a clearer picture of WordPress&#8217; use in higher education. If you know someone or an organization that uses WordPress in higher education, please <a href=\"https://www.surveymonkey.com/r/wpcampus05-2016\">share the survey</a> with them. The survey closes on May 27th.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:34;a:7:{s:5:\"title\";s:73:\"WPTavern: What Do You Think of the Recommended Plugins Page in WordPress?\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54437\";s:4:\"link\";s:82:\"http://wptavern.com/what-do-you-think-of-the-recommended-plugins-page-in-wordpress\";s:11:\"description\";s:3913:\"<p>In late 2014, <a href=\"http://wptavern.com/wordpress-4-1-to-introduce-plugin-recommendations\">WordPress 4.1 added</a> a Recommended Plugins tab that takes into account the plugins you have installed and suggests plugins based on which ones are commonly used together. After nearly a year and a half since it was added, I asked the <a href=\"https://twitter.com/wptavern/status/727578470415532032\">Tavern&#8217;s Twitter followers</a> if they have ever installed plugins recommended by WordPress.</p>\n<p>I was surprised to discover that some people don&#8217;t know the tab exists.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> There\'s a \"Recommended\" tab?!?</p>\n<p>&mdash; Joe Taiabjee (@joetek) <a href=\"https://twitter.com/joetek/status/727581218414407681\">May 3, 2016</a></p></blockquote>\n<p></p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> I\'ve just noticed the Recommended tab. It seems to show those plugins with most Active Installs. Interesting, but a bit \'hidden\'</p>\n<p>&mdash; Alejandro Vargas S. (@Alejandro_V_S) <a href=\"https://twitter.com/Alejandro_V_S/status/727836820159930369\">May 4, 2016</a></p></blockquote>\n<p></p>\n<p>Steve Brown says the recommendations are useful.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> yep :) very useful feature indeed</p>\n<p>&mdash; Steve Brown (@stevna) <a href=\"https://twitter.com/stevna/status/727681984504287232\">May 4, 2016</a></p></blockquote>\n<p></p>\n<p>Some people view the page as an opportunity for Automattic to advertise its plugins while others don&#8217;t trust the recommendations.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> I have no needs for the Automattic plugins that are almost only being recommended there</p>\n<p>&mdash; Marko Heijnen (@markoheijnen) <a href=\"https://twitter.com/markoheijnen/status/727624592399998976\">May 3, 2016</a></p></blockquote>\n<p></p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> Once. However 10 of the plugins recommended on page 1 are untested with my version of WP. So wouldnt rely on the recommendations</p>\n<p>&mdash; WPin.me (@wp_in) <a href=\"https://twitter.com/wp_in/status/727725233843671040\">May 4, 2016</a></p></blockquote>\n<p></p>\n<p>When I viewed the recommended plugins page in 2014, the results displayed plugins that weren&#8217;t updated in years.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/12/RecommendedPluginsTab.png\"><img class=\"size-full wp-image-35318\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/12/RecommendedPluginsTab.png?resize=1025%2C527\" alt=\"Plugins Recommended To Me Based on Data of Sites with Similar Plugins Installed\" /></a>Plugins Recommended To Me Based on Data of Sites with Similar Plugins Installed\n<p>Today, the page displays more relevant results with recently updated plugins. On the first page of results for WP Tavern, only one plugin from Automattic is recommended. The second page of results doesn&#8217;t list any plugins authored by Automattic.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/2016RecommendedPlugins.png\"><img class=\"size-full wp-image-54616\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/2016RecommendedPlugins.png?resize=1025%2C514\" alt=\"Recommended Plugins in 2016\" /></a>Recommended Plugin Results in 2016\n<p>To help determine how useful the recommended plugins page is, I&#8217;d like you to take this short survey. Results will be displayed on Tuesday, May 17th. In addition to the survey, you can leave your feedback in the comments.</p>\n<div class=\"pd-embed\" type=\"type\"></div>\n<p></p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Wed, 11 May 2016 03:19:37 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:3913:\"<p>In late 2014, <a href=\"http://wptavern.com/wordpress-4-1-to-introduce-plugin-recommendations\">WordPress 4.1 added</a> a Recommended Plugins tab that takes into account the plugins you have installed and suggests plugins based on which ones are commonly used together. After nearly a year and a half since it was added, I asked the <a href=\"https://twitter.com/wptavern/status/727578470415532032\">Tavern&#8217;s Twitter followers</a> if they have ever installed plugins recommended by WordPress.</p>\n<p>I was surprised to discover that some people don&#8217;t know the tab exists.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> There\'s a \"Recommended\" tab?!?</p>\n<p>&mdash; Joe Taiabjee (@joetek) <a href=\"https://twitter.com/joetek/status/727581218414407681\">May 3, 2016</a></p></blockquote>\n<p></p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> I\'ve just noticed the Recommended tab. It seems to show those plugins with most Active Installs. Interesting, but a bit \'hidden\'</p>\n<p>&mdash; Alejandro Vargas S. (@Alejandro_V_S) <a href=\"https://twitter.com/Alejandro_V_S/status/727836820159930369\">May 4, 2016</a></p></blockquote>\n<p></p>\n<p>Steve Brown says the recommendations are useful.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> yep :) very useful feature indeed</p>\n<p>&mdash; Steve Brown (@stevna) <a href=\"https://twitter.com/stevna/status/727681984504287232\">May 4, 2016</a></p></blockquote>\n<p></p>\n<p>Some people view the page as an opportunity for Automattic to advertise its plugins while others don&#8217;t trust the recommendations.</p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> I have no needs for the Automattic plugins that are almost only being recommended there</p>\n<p>&mdash; Marko Heijnen (@markoheijnen) <a href=\"https://twitter.com/markoheijnen/status/727624592399998976\">May 3, 2016</a></p></blockquote>\n<p></p>\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\"><a href=\"https://twitter.com/wptavern\">@wptavern</a> Once. However 10 of the plugins recommended on page 1 are untested with my version of WP. So wouldnt rely on the recommendations</p>\n<p>&mdash; WPin.me (@wp_in) <a href=\"https://twitter.com/wp_in/status/727725233843671040\">May 4, 2016</a></p></blockquote>\n<p></p>\n<p>When I viewed the recommended plugins page in 2014, the results displayed plugins that weren&#8217;t updated in years.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/12/RecommendedPluginsTab.png\"><img class=\"size-full wp-image-35318\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2014/12/RecommendedPluginsTab.png?resize=1025%2C527\" alt=\"Plugins Recommended To Me Based on Data of Sites with Similar Plugins Installed\" /></a>Plugins Recommended To Me Based on Data of Sites with Similar Plugins Installed\n<p>Today, the page displays more relevant results with recently updated plugins. On the first page of results for WP Tavern, only one plugin from Automattic is recommended. The second page of results doesn&#8217;t list any plugins authored by Automattic.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/2016RecommendedPlugins.png\"><img class=\"size-full wp-image-54616\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/2016RecommendedPlugins.png?resize=1025%2C514\" alt=\"Recommended Plugins in 2016\" /></a>Recommended Plugin Results in 2016\n<p>To help determine how useful the recommended plugins page is, I&#8217;d like you to take this short survey. Results will be displayed on Tuesday, May 17th. In addition to the survey, you can leave your feedback in the comments.</p>\n<div class=\"pd-embed\" type=\"type\"></div>\n<p></p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:35;a:7:{s:5:\"title\";s:81:\"WPTavern: Automattic is Protecting its Woo, WooThemes, and WooCommerce Trademarks\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54645\";s:4:\"link\";s:89:\"http://wptavern.com/automattic-is-protecting-its-woo-woothemes-and-woocommerce-trademarks\";s:11:\"description\";s:6735:\"<p>When <a href=\"http://wptavern.com/automattic-acquires-woocommerce\">Automattic acquired WooThemes in 2015</a>, it gained employees, plugins, themes, and the company&#8217;s trademarks. These trademarks include, standard character marks, logos, and specific graphics such as the Verified WooExpert badges. One of the responsibilities of a trademark owner is to protect it from infringement.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/VerifiedWooExpertServicemark.png\"><img class=\"size-full wp-image-54702\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/VerifiedWooExpertServicemark.png?resize=1025%2C621\" alt=\"Verified WooExpert Service Mark\" /></a>Verified WooExpert Service Mark\n<p>WooGPL is a service that provides customers with commercial themes, plugins, and extensions for WooCommerce at a discounted rate. In March, Automattic <a href=\"https://woogpl.com/woogpl-is-closing/\">sent Billy Ablett</a>, owner of <a href=\"https://woogpl.com\">WooGPL</a>, the following notice that informs him that his domain infringes the Woo and WooCommerce trademarks.</p>\n<blockquote><p>I’m writing to you on behalf of Automattic Inc. regarding your use of the Woo and WooCommerce trademarks.</p>\n<p>As you may know, Automattic owns the Woo, WooCommerce, and WooThemes brands, as well as the associated trademarks. We recently learned of https://woogpl.com, which actively makes use of our registered trademarks in both its name and promotion. We are very concerned that your use of Woo and WooCommerce will create confusion by communicating that your WooCommerce products are endorsed by or associated with Automattic, when in fact it is not.</p>\n<p>While Automattic appreciates that you are providing products that build on WooCommerce open source software, that fact does not authorize you to use Woo, WooThemes or WooCommerce trademarks.</p>\n<p>To minimize user confusion and to protect our own intellectual property, we unfortunately must insist that you take prompt steps to change your domain name to something that doesn’t include &#8216;Woo&#8217; in the prefix, and change your product descriptions to avoid confusion and potentially misleading consumers to believe they are purchasing our products. An example of this would be: WooCommerce Email Customiser Pro would need to be changed to Email Customiser Pro for WooCommerce.</p>\n<p>For more information, please see our <a href=\"https://www.woothemes.com/style-guide/#sg-trademarks\">Trademark Guidelines</a>.</p>\n<p>While we are appreciative that you have included a disclaimer on your site, unfortunately this would not be sufficient and we would still insist that the domain name and product names be changed.</p></blockquote>\n<p>While it&#8217;s not the sole reason <a href=\"https://woogpl.com/woogpl-is-closing/\">WooGPL is shutting down</a>, the notice provides a convenient opportunity to rebrand to <a href=\"https://www.gplkit.com/\">GPL Kit</a>, something the company was already planning to do.</p>\n<p>&#8220;We would have eventually closed down WooGPL due to GPL Kit however, it would have been great to close it down on our terms when the time was right,&#8221; Daniel, who is part of the GPL Kit team told the Tavern.</p>\n<p>Daniel says that when he started WooGPL there wasn&#8217;t a trademark registered with the Woo character mark until October of 2015.</p>\n<p>A search of the United States Patent and Trademark Office for Woo contains over 1K results. However, this is the only character mark for Woo that I found. The filing date is October 22nd, 2015 and is in the approval process.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WooCharacterMark.png\"><img class=\"size-full wp-image-54703\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WooCharacterMark.png?resize=1003%2C557\" alt=\"Woo Character Mark\" /></a>Woo Character Mark\n<h2>When You Should Ask For Permission</h2>\n<p>WooThemes has a <a href=\"https://www.woothemes.com/style-guide/#sg-trademarks\">style guide</a> on its site that explains how the brand is used and has details on when Woo™, WooCommerce®, and WooThemes® names, logos, and related icons collectively known as Woo Marks can be used without permission. The following chart provides some examples.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PermissionChartForWooTrademarks.png\"><img class=\"size-full wp-image-54704\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PermissionChartForWooTrademarks.png?resize=1010%2C814\" alt=\"Examples of When You Do and Don\'t Need Permission\" /></a>Examples of When You Do and Don&#8217;t Need Permission\n<p>If you&#8217;re in doubt, you can email Automattic&#8217;s trademark team  <a href=\"mailto:trademarks@automattic.com\">trademarks @ automattic.com</a> to receive clarification.</p>\n<h2>Woo&#8217;s at Risk?</h2>\n<p>There are quite a few businesses in the WordPress ecosystem that use Woo in their name and domain. <a href=\"http://www.woorockets.com/\">WooRockets</a> is a WooCommerce theme shop while <a href=\"http://wooassist.com/\">WooAssist</a> provides support and maintenance for store owners.</p>\n<p>I reached out to both companies to determine if Automattic sent them the same notice it sent to WooGPL. While I didn&#8217;t receive a response from WooRockets, John Gamour of WooAssist provided the Tavern with the following statement:</p>\n<blockquote><p>No, we haven&#8217;t been contacted by Automattic about that. It would be dissapointing if we were asked to change our name as our founder Nicholas Jones reached out to WooThemes before starting Wooassist and they gave the OK. We have also worked with Matt Cohen and James Koster on a project and nothing was ever mentioned about our name.</p></blockquote>\n<p>I tried to get in touch with Paul Sieminski, legal counsel for Automattic, to learn what the criteria is for violating the trademarks, who&#8217;s at risk, and how long they have enforced the marks but he could not be reached for comment.</p>\n<h2>Better to be Safe Than Sorry</h2>\n<p>As WooGPL discovered, adding a disclaimer to the bottom of your sites may not be enough. Considering the cost and potential impacts of re branding a company or product, it&#8217;s important to know as soon as possible if you&#8217;re infringing a company&#8217;s trademarks.</p>\n<p>Business owners in the WooCommerce and WooThemes ecosystem should double-check the <a href=\"https://www.woothemes.com/style-guide/#sg-trademarks\">style guide</a> to make sure you&#8217;re not violating any guidelines. Owners can also take a proactive step and contact Automattic&#8217;s trademark team to determine if your business meets the requirements.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Tue, 10 May 2016 20:21:06 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:6735:\"<p>When <a href=\"http://wptavern.com/automattic-acquires-woocommerce\">Automattic acquired WooThemes in 2015</a>, it gained employees, plugins, themes, and the company&#8217;s trademarks. These trademarks include, standard character marks, logos, and specific graphics such as the Verified WooExpert badges. One of the responsibilities of a trademark owner is to protect it from infringement.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/VerifiedWooExpertServicemark.png\"><img class=\"size-full wp-image-54702\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/VerifiedWooExpertServicemark.png?resize=1025%2C621\" alt=\"Verified WooExpert Service Mark\" /></a>Verified WooExpert Service Mark\n<p>WooGPL is a service that provides customers with commercial themes, plugins, and extensions for WooCommerce at a discounted rate. In March, Automattic <a href=\"https://woogpl.com/woogpl-is-closing/\">sent Billy Ablett</a>, owner of <a href=\"https://woogpl.com\">WooGPL</a>, the following notice that informs him that his domain infringes the Woo and WooCommerce trademarks.</p>\n<blockquote><p>I’m writing to you on behalf of Automattic Inc. regarding your use of the Woo and WooCommerce trademarks.</p>\n<p>As you may know, Automattic owns the Woo, WooCommerce, and WooThemes brands, as well as the associated trademarks. We recently learned of https://woogpl.com, which actively makes use of our registered trademarks in both its name and promotion. We are very concerned that your use of Woo and WooCommerce will create confusion by communicating that your WooCommerce products are endorsed by or associated with Automattic, when in fact it is not.</p>\n<p>While Automattic appreciates that you are providing products that build on WooCommerce open source software, that fact does not authorize you to use Woo, WooThemes or WooCommerce trademarks.</p>\n<p>To minimize user confusion and to protect our own intellectual property, we unfortunately must insist that you take prompt steps to change your domain name to something that doesn’t include &#8216;Woo&#8217; in the prefix, and change your product descriptions to avoid confusion and potentially misleading consumers to believe they are purchasing our products. An example of this would be: WooCommerce Email Customiser Pro would need to be changed to Email Customiser Pro for WooCommerce.</p>\n<p>For more information, please see our <a href=\"https://www.woothemes.com/style-guide/#sg-trademarks\">Trademark Guidelines</a>.</p>\n<p>While we are appreciative that you have included a disclaimer on your site, unfortunately this would not be sufficient and we would still insist that the domain name and product names be changed.</p></blockquote>\n<p>While it&#8217;s not the sole reason <a href=\"https://woogpl.com/woogpl-is-closing/\">WooGPL is shutting down</a>, the notice provides a convenient opportunity to rebrand to <a href=\"https://www.gplkit.com/\">GPL Kit</a>, something the company was already planning to do.</p>\n<p>&#8220;We would have eventually closed down WooGPL due to GPL Kit however, it would have been great to close it down on our terms when the time was right,&#8221; Daniel, who is part of the GPL Kit team told the Tavern.</p>\n<p>Daniel says that when he started WooGPL there wasn&#8217;t a trademark registered with the Woo character mark until October of 2015.</p>\n<p>A search of the United States Patent and Trademark Office for Woo contains over 1K results. However, this is the only character mark for Woo that I found. The filing date is October 22nd, 2015 and is in the approval process.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WooCharacterMark.png\"><img class=\"size-full wp-image-54703\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WooCharacterMark.png?resize=1003%2C557\" alt=\"Woo Character Mark\" /></a>Woo Character Mark\n<h2>When You Should Ask For Permission</h2>\n<p>WooThemes has a <a href=\"https://www.woothemes.com/style-guide/#sg-trademarks\">style guide</a> on its site that explains how the brand is used and has details on when Woo™, WooCommerce®, and WooThemes® names, logos, and related icons collectively known as Woo Marks can be used without permission. The following chart provides some examples.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PermissionChartForWooTrademarks.png\"><img class=\"size-full wp-image-54704\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/PermissionChartForWooTrademarks.png?resize=1010%2C814\" alt=\"Examples of When You Do and Don\'t Need Permission\" /></a>Examples of When You Do and Don&#8217;t Need Permission\n<p>If you&#8217;re in doubt, you can email Automattic&#8217;s trademark team  <a href=\"mailto:trademarks@automattic.com\">trademarks @ automattic.com</a> to receive clarification.</p>\n<h2>Woo&#8217;s at Risk?</h2>\n<p>There are quite a few businesses in the WordPress ecosystem that use Woo in their name and domain. <a href=\"http://www.woorockets.com/\">WooRockets</a> is a WooCommerce theme shop while <a href=\"http://wooassist.com/\">WooAssist</a> provides support and maintenance for store owners.</p>\n<p>I reached out to both companies to determine if Automattic sent them the same notice it sent to WooGPL. While I didn&#8217;t receive a response from WooRockets, John Gamour of WooAssist provided the Tavern with the following statement:</p>\n<blockquote><p>No, we haven&#8217;t been contacted by Automattic about that. It would be dissapointing if we were asked to change our name as our founder Nicholas Jones reached out to WooThemes before starting Wooassist and they gave the OK. We have also worked with Matt Cohen and James Koster on a project and nothing was ever mentioned about our name.</p></blockquote>\n<p>I tried to get in touch with Paul Sieminski, legal counsel for Automattic, to learn what the criteria is for violating the trademarks, who&#8217;s at risk, and how long they have enforced the marks but he could not be reached for comment.</p>\n<h2>Better to be Safe Than Sorry</h2>\n<p>As WooGPL discovered, adding a disclaimer to the bottom of your sites may not be enough. Considering the cost and potential impacts of re branding a company or product, it&#8217;s important to know as soon as possible if you&#8217;re infringing a company&#8217;s trademarks.</p>\n<p>Business owners in the WooCommerce and WooThemes ecosystem should double-check the <a href=\"https://www.woothemes.com/style-guide/#sg-trademarks\">style guide</a> to make sure you&#8217;re not violating any guidelines. Owners can also take a proactive step and contact Automattic&#8217;s trademark team to determine if your business meets the requirements.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:36;a:7:{s:5:\"title\";s:86:\"WPTavern: WooCommerce Releases Storefront 2.0 with Major Improvements to Mobile Design\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54641\";s:4:\"link\";s:96:\"http://wptavern.com/woocommerce-releases-storefront-2-0-with-major-improvements-to-mobile-design\";s:11:\"description\";s:3509:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-update.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-update.png?resize=1025%2C451\" alt=\"storefront-update\" class=\"aligncenter size-full wp-image-54669\" /></a></p>\n<p><a href=\"https://wordpress.org/themes/storefront/\" target=\"_blank\">Storefront</a>, the official WooCommerce theme built to work seamlessly with the plugin, has just passed the <a href=\"https://www.woothemes.com/2016/05/storefront-2-0-release/\" target=\"_blank\">2.0 milestone</a>. This release introduces a new &#8220;best sellers&#8221; section to the homepage and adds compatibility with the upcoming WooCommerce 2.6’s tabbed “My Account” section and the average rating widget.</p>\n<p>The most important update in Storefront 2.0 is the redesigned mobile experience. According to <a href=\"http://resources.mobify.com/50-mobile-commerce-stats.html\" target=\"_blank\">Mobify</a>, 30% of mobile shoppers will abandon a transaction if the experience is not optimized for mobile. <a href=\"http://www.themobileplaybook.com/\" target=\"_blank\">Google&#8217;s Mobile Playbook</a> says that not having a mobile optimized website is like closing your store one day each week. To keep pace with the expectations of mobile buyers, WooCommerce has drastically reduced Storefront&#8217;s mobile header height by 60% and has added the search, shopping cart, and account links to a sticky bottom menu for easy access.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-mobile-home.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-mobile-home.png?resize=799%2C697\" alt=\"storefront-mobile-home\" class=\"aligncenter size-full wp-image-54671\" /></a></p>\n<p>Storefront 2.0 includes many design improvements that make the theme cleaner and more flexible. This update removes Helvetica in favor of Source Sans, which WooCommerce says gives them access to a wider variety of weights they can use to &#8220;provide greater depth and cohesion.&#8221; Other notable design changes include:</p>\n<ul>\n<li>Borders have been largely removed so that pages don’t feel quite so broken up.</li>\n<li>The breadcrumb and the main navigation are now wrapped in their own content regions, cementing them as unique components.</li>\n<li>Product reviews and comments tweaked to make them cleaner and more scannable.</li>\n<li>Blog post meta has been redesigned to include the author Gravatar.</li>\n<li>Softer design treatment for tables with colors based on the main background color.</li>\n<li>oEmbeds have been styled to match the rest of Storefront (including typography, padding, colors).</li>\n<li>Integrated WordPress 4.5’s custom logo feature so users can add a logo without using a plugin.</li>\n</ul>\n<p><a href=\"https://wordpress.org/themes/storefront/\" target=\"_blank\">Storefront</a> is active on more than 50,000 websites. There are nearly a dozen free themes on WordPress.org that use it as a parent theme and another dozen commercial themes on WooThemes.com. If you use a heavily customized Storefront child theme, you may want to test its compatibility with the 2.0 update on a development site to ensure that there are no visual surprises. If you have any ideas or recommendations for updates to Storefront, you can leave feedback on the theme&#8217;s <a href=\"http://ideas.woothemes.com/forums/275029-storefront\" target=\"_blank\">idea board</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Mon, 09 May 2016 22:23:17 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:3509:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-update.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-update.png?resize=1025%2C451\" alt=\"storefront-update\" class=\"aligncenter size-full wp-image-54669\" /></a></p>\n<p><a href=\"https://wordpress.org/themes/storefront/\" target=\"_blank\">Storefront</a>, the official WooCommerce theme built to work seamlessly with the plugin, has just passed the <a href=\"https://www.woothemes.com/2016/05/storefront-2-0-release/\" target=\"_blank\">2.0 milestone</a>. This release introduces a new &#8220;best sellers&#8221; section to the homepage and adds compatibility with the upcoming WooCommerce 2.6’s tabbed “My Account” section and the average rating widget.</p>\n<p>The most important update in Storefront 2.0 is the redesigned mobile experience. According to <a href=\"http://resources.mobify.com/50-mobile-commerce-stats.html\" target=\"_blank\">Mobify</a>, 30% of mobile shoppers will abandon a transaction if the experience is not optimized for mobile. <a href=\"http://www.themobileplaybook.com/\" target=\"_blank\">Google&#8217;s Mobile Playbook</a> says that not having a mobile optimized website is like closing your store one day each week. To keep pace with the expectations of mobile buyers, WooCommerce has drastically reduced Storefront&#8217;s mobile header height by 60% and has added the search, shopping cart, and account links to a sticky bottom menu for easy access.</p>\n<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-mobile-home.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/storefront-mobile-home.png?resize=799%2C697\" alt=\"storefront-mobile-home\" class=\"aligncenter size-full wp-image-54671\" /></a></p>\n<p>Storefront 2.0 includes many design improvements that make the theme cleaner and more flexible. This update removes Helvetica in favor of Source Sans, which WooCommerce says gives them access to a wider variety of weights they can use to &#8220;provide greater depth and cohesion.&#8221; Other notable design changes include:</p>\n<ul>\n<li>Borders have been largely removed so that pages don’t feel quite so broken up.</li>\n<li>The breadcrumb and the main navigation are now wrapped in their own content regions, cementing them as unique components.</li>\n<li>Product reviews and comments tweaked to make them cleaner and more scannable.</li>\n<li>Blog post meta has been redesigned to include the author Gravatar.</li>\n<li>Softer design treatment for tables with colors based on the main background color.</li>\n<li>oEmbeds have been styled to match the rest of Storefront (including typography, padding, colors).</li>\n<li>Integrated WordPress 4.5’s custom logo feature so users can add a logo without using a plugin.</li>\n</ul>\n<p><a href=\"https://wordpress.org/themes/storefront/\" target=\"_blank\">Storefront</a> is active on more than 50,000 websites. There are nearly a dozen free themes on WordPress.org that use it as a parent theme and another dozen commercial themes on WooThemes.com. If you use a heavily customized Storefront child theme, you may want to test its compatibility with the 2.0 update on a development site to ensure that there are no visual surprises. If you have any ideas or recommendations for updates to Storefront, you can leave feedback on the theme&#8217;s <a href=\"http://ideas.woothemes.com/forums/275029-storefront\" target=\"_blank\">idea board</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:37;a:7:{s:5:\"title\";s:54:\"WPTavern: Timber 1.0 Is Now Available on WordPress.org\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54396\";s:4:\"link\";s:64:\"http://wptavern.com/timber-1-0-is-now-available-on-wordpress-org\";s:11:\"description\";s:5932:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/timber.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/timber.png?resize=1025%2C405\" alt=\"timber\" class=\"aligncenter size-full wp-image-54630\" /></a></p>\n<p>Last week the creators of <a href=\"https://wordpress.org/plugins/timber-library/\" target=\"_blank\">Timber</a>, the plugin that enables WordPress theme developers to write HTML using the <a href=\"http://twig.sensiolabs.org/\" target=\"_blank\">Twig Template Engine</a>, released version 1.0 on WordPress.org. The plugin is active on more than 10,000 websites where theme authors have elected to keep PHP files separate from HTML. Timber is built on DRY and MVC principles to solve the problem stated in its unofficial tagline: <em>&#8220;Because WordPress is awesome, but the_loop isn&#8217;t.&#8221;</em></p>\n<p>Over the past four years, the open source project has evolved from being a starter theme to a plugin that can be added to existing themes. It is now used on <a href=\"http://upstatement.com/timber/#showcase\" target=\"_blank\">thousands of websites</a> and has 83 <a href=\"https://github.com/timber/timber/graphs/contributors\" target=\"_blank\">contributors</a> listed on GitHub.</p>\n<p>&#8220;In 2012 I was getting more into WordPress after doing lots of JS development with <a href=\"http://handlebarsjs.com/\" target=\"_blank\">Handlebars</a> (a JS templating language),&#8221; Timber creator Jared Novack said. &#8220;I went to WordCamp Providence to learn more about state-of-the-art WordPress ways. I remember thinking: &#8216;This is great, but I really miss the cleanliness of Handlebars &#8212; I wish someone would make something like that for WordPress.&#8217; That&#8217;s when I realized, I was that someone.&#8221;</p>\n<p>Novack was playing around with <a href=\"http://www.smarty.net/\" target=\"_blank\">Smarty</a> and <a href=\"https://mustache.github.io/\" target=\"_blank\">Mustache</a> before he finally discovered Fabien Potencier&#8217;s <a href=\"http://twig.sensiolabs.org/\" target=\"_blank\">Twig project</a>.</p>\n<p>&#8220;The syntax felt so natural I almost didn&#8217;t need to read the docs (don&#8217;t worry, I did),&#8221; he said. &#8220;I realized what I needed was a way to marry Twig and WordPress, and thus: Timber was born.&#8221;</p>\n<p>At that time Novack&#8217;s company, <a href=\"https://upstatement.com/\" target=\"_blank\">Upstatement</a>, was beginning development on a big new project for Random House to enable their marketers to generate unique sites from a library of templates. This client project became Timber&#8217;s first test case.</p>\n<p>&#8220;Originally, Timber was a parent theme, like _s. But after we completed the Random House project, I realized I wanted to apply Timber functionality to existing sites,&#8221; Novack said. &#8220;I converted it into a plugin that could be employed on existing themes which is the form it takes today.&#8221;</p>\n<p>The plugin allows designers skilled with HTML and CSS to create themes without having extensive knowledge of PHP and WordPress functions. Timber successfully powers sites like Michael Bloomberg&#8217;s <a href=\"https://www.thetrace.org/\" target=\"_blank\">The Trace</a>, <a href=\"http://everytown.org/\" target=\"_blank\">Everytown for Gun Safety</a>, <a href=\"https://www.hoteltonight.com/\" target=\"_blank\">Hotel Tonight</a>, and the <a href=\"http://harvardlawreview.org/\" target=\"_blank\">Harvard Law Review</a>.</p>\n<h3>Timber 1.0 Puts the Project on the Path of Stability</h3>\n<p>As of Timber 1.0, developers can now include the project as a plugin or require it as a <a href=\"https://packagist.org/packages/timber/timber\" target=\"_blank\">Composer dependency</a>.</p>\n<p>&#8220;The big news is that 1.0 represents a maturing of the platform — developers can use Timber and Twig with confidence that they’re building on top of a stable and universal platform,&#8221; Novack said.</p>\n<p>This release sheds years of deprecated functions and methods dating back to the project&#8217;s early days in 2013. Novack said that technical and documentation debt were the biggest hurdles in getting to 1.0.</p>\n<p>&#8220;In hindsight it’s so easy to build stuff, but so hard to build a complete system,&#8221; he said. &#8220;When Timber started it was just for me and the documentation could just live in my head. I’d add and improve stuff and then live with some of the quirks.&#8221;</p>\n<p>As the project and its contributors grew, Novack found it difficult to keep up with the growing codebase while running his company. Bringing it to a place of maturity with up-to-date automated testing and documentation took nearly a year.</p>\n<p>&#8220;Backwards compatibility was also a major challenge,&#8221; Novack said. &#8220;As ideas and new code got submitted, development slowed as every decision might have implications for existing users. We would deprecate features, but I was hesitant to remove things that I knew were mistakes, but that people were using.&#8221;</p>\n<p>Developers are encouraged to read the <a href=\"https://github.com/timber/timber/wiki/1.0-Upgrade-Guide\" target=\"_blank\">1.0 Upgrade Guide</a>, as there may be additional steps required depending on how Timber is being used. This release adds a few new features but the most important change is the bulk removal of older sections of the codebase. The upgrade guide outlines all of the object properties and static methods that will need to be updated so that nothing breaks. In the future, Timber-powered themes will be easier to maintain, with fewer quirks and better-documented features.</p>\n<p>&#8220;The key learning for me is that the ultimate &#8216;killer feature&#8217; is stability and predictability,&#8221; Novack said. &#8220;When everything is organized cleanly and developers can use the things that they would intuitively expect — that’s success.&#8221;</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Mon, 09 May 2016 17:52:38 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:5932:\"<p><a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/timber.png\"><img src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/timber.png?resize=1025%2C405\" alt=\"timber\" class=\"aligncenter size-full wp-image-54630\" /></a></p>\n<p>Last week the creators of <a href=\"https://wordpress.org/plugins/timber-library/\" target=\"_blank\">Timber</a>, the plugin that enables WordPress theme developers to write HTML using the <a href=\"http://twig.sensiolabs.org/\" target=\"_blank\">Twig Template Engine</a>, released version 1.0 on WordPress.org. The plugin is active on more than 10,000 websites where theme authors have elected to keep PHP files separate from HTML. Timber is built on DRY and MVC principles to solve the problem stated in its unofficial tagline: <em>&#8220;Because WordPress is awesome, but the_loop isn&#8217;t.&#8221;</em></p>\n<p>Over the past four years, the open source project has evolved from being a starter theme to a plugin that can be added to existing themes. It is now used on <a href=\"http://upstatement.com/timber/#showcase\" target=\"_blank\">thousands of websites</a> and has 83 <a href=\"https://github.com/timber/timber/graphs/contributors\" target=\"_blank\">contributors</a> listed on GitHub.</p>\n<p>&#8220;In 2012 I was getting more into WordPress after doing lots of JS development with <a href=\"http://handlebarsjs.com/\" target=\"_blank\">Handlebars</a> (a JS templating language),&#8221; Timber creator Jared Novack said. &#8220;I went to WordCamp Providence to learn more about state-of-the-art WordPress ways. I remember thinking: &#8216;This is great, but I really miss the cleanliness of Handlebars &#8212; I wish someone would make something like that for WordPress.&#8217; That&#8217;s when I realized, I was that someone.&#8221;</p>\n<p>Novack was playing around with <a href=\"http://www.smarty.net/\" target=\"_blank\">Smarty</a> and <a href=\"https://mustache.github.io/\" target=\"_blank\">Mustache</a> before he finally discovered Fabien Potencier&#8217;s <a href=\"http://twig.sensiolabs.org/\" target=\"_blank\">Twig project</a>.</p>\n<p>&#8220;The syntax felt so natural I almost didn&#8217;t need to read the docs (don&#8217;t worry, I did),&#8221; he said. &#8220;I realized what I needed was a way to marry Twig and WordPress, and thus: Timber was born.&#8221;</p>\n<p>At that time Novack&#8217;s company, <a href=\"https://upstatement.com/\" target=\"_blank\">Upstatement</a>, was beginning development on a big new project for Random House to enable their marketers to generate unique sites from a library of templates. This client project became Timber&#8217;s first test case.</p>\n<p>&#8220;Originally, Timber was a parent theme, like _s. But after we completed the Random House project, I realized I wanted to apply Timber functionality to existing sites,&#8221; Novack said. &#8220;I converted it into a plugin that could be employed on existing themes which is the form it takes today.&#8221;</p>\n<p>The plugin allows designers skilled with HTML and CSS to create themes without having extensive knowledge of PHP and WordPress functions. Timber successfully powers sites like Michael Bloomberg&#8217;s <a href=\"https://www.thetrace.org/\" target=\"_blank\">The Trace</a>, <a href=\"http://everytown.org/\" target=\"_blank\">Everytown for Gun Safety</a>, <a href=\"https://www.hoteltonight.com/\" target=\"_blank\">Hotel Tonight</a>, and the <a href=\"http://harvardlawreview.org/\" target=\"_blank\">Harvard Law Review</a>.</p>\n<h3>Timber 1.0 Puts the Project on the Path of Stability</h3>\n<p>As of Timber 1.0, developers can now include the project as a plugin or require it as a <a href=\"https://packagist.org/packages/timber/timber\" target=\"_blank\">Composer dependency</a>.</p>\n<p>&#8220;The big news is that 1.0 represents a maturing of the platform — developers can use Timber and Twig with confidence that they’re building on top of a stable and universal platform,&#8221; Novack said.</p>\n<p>This release sheds years of deprecated functions and methods dating back to the project&#8217;s early days in 2013. Novack said that technical and documentation debt were the biggest hurdles in getting to 1.0.</p>\n<p>&#8220;In hindsight it’s so easy to build stuff, but so hard to build a complete system,&#8221; he said. &#8220;When Timber started it was just for me and the documentation could just live in my head. I’d add and improve stuff and then live with some of the quirks.&#8221;</p>\n<p>As the project and its contributors grew, Novack found it difficult to keep up with the growing codebase while running his company. Bringing it to a place of maturity with up-to-date automated testing and documentation took nearly a year.</p>\n<p>&#8220;Backwards compatibility was also a major challenge,&#8221; Novack said. &#8220;As ideas and new code got submitted, development slowed as every decision might have implications for existing users. We would deprecate features, but I was hesitant to remove things that I knew were mistakes, but that people were using.&#8221;</p>\n<p>Developers are encouraged to read the <a href=\"https://github.com/timber/timber/wiki/1.0-Upgrade-Guide\" target=\"_blank\">1.0 Upgrade Guide</a>, as there may be additional steps required depending on how Timber is being used. This release adds a few new features but the most important change is the bulk removal of older sections of the codebase. The upgrade guide outlines all of the object properties and static methods that will need to be updated so that nothing breaks. In the future, Timber-powered themes will be easier to maintain, with fewer quirks and better-documented features.</p>\n<p>&#8220;The key learning for me is that the ultimate &#8216;killer feature&#8217; is stability and predictability,&#8221; Novack said. &#8220;When everything is organized cleanly and developers can use the things that they would intuitively expect — that’s success.&#8221;</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:38;a:7:{s:5:\"title\";s:49:\"Post Status: WordPress Security — Draft podcast\";s:4:\"guid\";s:31:\"https://poststatus.com/?p=24378\";s:4:\"link\";s:56:\"https://poststatus.com/wordpress-security-draft-podcast/\";s:11:\"description\";s:2296:\"<p>Welcome to the Post Status <a href=\"https://poststatus.com/category/draft\">Draft podcast</a>, which you can find <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">on iTunes</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, and <a href=\"http://simplecast.fm/podcasts/1061/rss\">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle &#8212; the CTO of Human Made &#8212; and Brian Krogsgard.</p>\n<p><span>Security &#8212; in WordPress core, distributed plugins and themes, and in our custom code &#8212; is a constant battle. It’s important to be vigilant with our security practices, from the perspective of managing our websites and when writing code. In this episode, Joe and Brian discuss the nature of WordPress security, best practices for writing secure code, and dig into various situations WordPress developers and site owners may run into.</span></p>\n<a href=\"https://audio.simplecast.com/37301.mp3\">https://audio.simplecast.com/37301.mp3</a>\n<p><a href=\"http://audio.simplecast.com/37301.mp3\">Direct Download</a></p>\n<h3>Links</h3>\n<ul>\n<li><a href=\"http://codex.wordpress.org/Hardening_WordPress\">Hardening WordPress</a></li>\n<li><a href=\"https://wordpress.org/about/security/\">About WordPress Security</a></li>\n<li><a href=\"https://make.wordpress.org/themes/2015/05/19/a-guide-to-writing-secure-themes-part-1-introduction/\">A Guide to Writing Secure Themes</a></li>\n<li><a href=\"http://ben.lobaugh.net/uploads/writing-secure-plugins-and-themes/#/\">Writing Secure Plugins &amp; Themes</a> by Ben Lobaugh</li>\n<li><a href=\"https://codex.wordpress.org/Class_Reference/wpdb\">$wpdb</a></li>\n<li><a href=\"https://wpvulndb.com/\">WP Scan</a></li>\n<li><a href=\"https://blog.sucuri.net/2015/03/understanding-wordpress-plugin-vulnerabilities.html\">Understanding Vulnerabilities</a></li>\n</ul>\n<h3>Sponsor: Pagely</h3>\n<p><a href=\"https://pagely.com\"><span>Pagely</span></a><span> offers best in class managed WordPress hosting, powered by the Amazon Cloud, the Internet’s most reliable infrastructure. Post Status is proudly hosted by Pagely. Thank you to </span><a href=\"https://pagely.com\"><span>Pagely</span></a><span> for being a Post Status partner.</span></p>\";s:7:\"pubdate\";s:31:\"Mon, 09 May 2016 01:01:31 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Katie Richards\";}s:7:\"summary\";s:2296:\"<p>Welcome to the Post Status <a href=\"https://poststatus.com/category/draft\">Draft podcast</a>, which you can find <a href=\"https://itunes.apple.com/us/podcast/post-status-draft-wordpress/id976403008\">on iTunes</a>, <a href=\"http://www.stitcher.com/podcast/krogsgard/post-status-draft-wordpress-podcast\">Stitcher</a>, and <a href=\"http://simplecast.fm/podcasts/1061/rss\">via RSS</a> for your favorite podcatcher. Post Status Draft is hosted by Joe Hoyle &#8212; the CTO of Human Made &#8212; and Brian Krogsgard.</p>\n<p><span>Security &#8212; in WordPress core, distributed plugins and themes, and in our custom code &#8212; is a constant battle. It’s important to be vigilant with our security practices, from the perspective of managing our websites and when writing code. In this episode, Joe and Brian discuss the nature of WordPress security, best practices for writing secure code, and dig into various situations WordPress developers and site owners may run into.</span></p>\n<a href=\"https://audio.simplecast.com/37301.mp3\">https://audio.simplecast.com/37301.mp3</a>\n<p><a href=\"http://audio.simplecast.com/37301.mp3\">Direct Download</a></p>\n<h3>Links</h3>\n<ul>\n<li><a href=\"http://codex.wordpress.org/Hardening_WordPress\">Hardening WordPress</a></li>\n<li><a href=\"https://wordpress.org/about/security/\">About WordPress Security</a></li>\n<li><a href=\"https://make.wordpress.org/themes/2015/05/19/a-guide-to-writing-secure-themes-part-1-introduction/\">A Guide to Writing Secure Themes</a></li>\n<li><a href=\"http://ben.lobaugh.net/uploads/writing-secure-plugins-and-themes/#/\">Writing Secure Plugins &amp; Themes</a> by Ben Lobaugh</li>\n<li><a href=\"https://codex.wordpress.org/Class_Reference/wpdb\">$wpdb</a></li>\n<li><a href=\"https://wpvulndb.com/\">WP Scan</a></li>\n<li><a href=\"https://blog.sucuri.net/2015/03/understanding-wordpress-plugin-vulnerabilities.html\">Understanding Vulnerabilities</a></li>\n</ul>\n<h3>Sponsor: Pagely</h3>\n<p><a href=\"https://pagely.com\"><span>Pagely</span></a><span> offers best in class managed WordPress hosting, powered by the Amazon Cloud, the Internet’s most reliable infrastructure. Post Status is proudly hosted by Pagely. Thank you to </span><a href=\"https://pagely.com\"><span>Pagely</span></a><span> for being a Post Status partner.</span></p>\";}i:39;a:7:{s:5:\"title\";s:26:\"Matt: Apple and Podcasting\";s:4:\"guid\";s:22:\"https://ma.tt/?p=46548\";s:4:\"link\";s:43:\"https://ma.tt/2016/05/apple-and-podcasting/\";s:11:\"description\";s:557:\"<p><a href=\"https://marco.org/2016/05/07/apple-role-in-podcasting\">Marco Arment has a great take on how the decentralized nature of podcasting is a feature</a>, not a bug, and Apple being more proactive there would be harmful to the ecosystem. As an aside, since I&#8217;ve been in Houston more recently, which means driving a lot, I&#8217;ve been really loving his app <a href=\"https://overcast.fm/\">Overcast</a> and I opted in to the optional paid subscription for it. I just need to get in more of a habit of listening to podcasts outside of Houston.</p>\";s:7:\"pubdate\";s:31:\"Sun, 08 May 2016 14:17:25 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:557:\"<p><a href=\"https://marco.org/2016/05/07/apple-role-in-podcasting\">Marco Arment has a great take on how the decentralized nature of podcasting is a feature</a>, not a bug, and Apple being more proactive there would be harmful to the ecosystem. As an aside, since I&#8217;ve been in Houston more recently, which means driving a lot, I&#8217;ve been really loving his app <a href=\"https://overcast.fm/\">Overcast</a> and I opted in to the optional paid subscription for it. I just need to get in more of a habit of listening to podcasts outside of Houston.</p>\";}i:40;a:7:{s:5:\"title\";s:98:\"WPTavern: VersionPress 3.0 Adds New Search Feature, Bulk Undo, and Commit Tracking per Environment\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54530\";s:4:\"link\";s:106:\"http://wptavern.com/versionpress-3-0-adds-new-search-feature-bulk-undo-and-commit-tracking-per-environment\";s:11:\"description\";s:3843:\"<p><a href=\"https://blog.versionpress.net/2016/04/versionpress-3-0-released/\" target=\"_blank\">VersionPress 3.0</a>, released this week, is the first version since the plugin <a href=\"http://wptavern.com/versionpress-transitions-into-a-free-open-source-project\" target=\"_blank\">became a free, open source project</a>. Creators Borek Bernard and Jan Vorá?ek, who originally attempted to crowdfund the project and then <a href=\"http://wptavern.com/versionpress-raises-400k-in-seed-funding\" target=\"_blank\">raised $400,000 in seed funding</a>, <a href=\"http://wptavern.com/versionpress-transitions-into-a-free-open-source-project\" target=\"_blank\">announced</a> last month that they are transitioning to a public development model.</p>\n<p>The team&#8217;s goal with this release was to polish up the experience of using VersionPress in the default WordPress installation while adding more useful features. However, it is not yet ready for use in production, according to Bernard.</p>\n<p>&#8220;We’re still keeping VersionPress in the <a href=\"http://docs.versionpress.net/en/getting-started/about-eap\" target=\"_blank\">“early access” period</a>, because of the third party plugins integration story but on simpler sites, VersionPress already shines,&#8221; he said.</p>\n<p>One of the most notable new features in VersionPress 3.0 is the plugin&#8217;s ability to track commits with the environment where they were created. Users can view changes in the admin and easily see if they were pushed to the staging or production environment.</p>\n<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/commit-tracking-in-environment.gif\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/commit-tracking-in-environment.gif?resize=725%2C347\" alt=\"commit-tracking-in-environment\" class=\"aligncenter size-full wp-image-54599\" /></a></p>\n<p>Version 3.0 also adds searching capabilities for filtering commits by author, date, commit message, and WordPress action. This release also includes a new bulk undo feature for commits and many improvements to the core versioning engine.</p>\n<h3>VersionPress 4.0 to Focus on Support for 3rd Party Plugins</h3>\n<p>One of the reasons the VersionPress team decided to go with a public development model was to mitigate the plugin&#8217;s conflicts with third-party themes and plugins. This was only possible if the opened up the codebase for contribution from other developers.</p>\n<p>&#8220;While we had most of the WordPress core covered pretty well, there was still this huge ecosystem of WordPress plugins and themes that could cause trouble to VersionPress in million different ways,&#8221; Borek said. &#8220;In the long run, the project had to turn into OSS should it be successful, and, fortunately, we met investors who understood this and supported our vision.&#8221;</p>\n<p>Borek and the team plan to focus on adding support for complex third party plugins in version 4.0, tentatively scheduled for mid-2016. One commenter on the post mentioned that a lack of WooCommerce support is a major thing holding him back from using VersionPress on projects. Borek confirmed that WooCommerce is high on their list of plugins they want to support.</p>\n<p>&#8220;Our goal remains the same: to take all the incredibly powerful functionality of Git and package it so that every WordPress user can use it,&#8221; Borek said.</p>\n<p>Since most site owners interested in this plugin are not running vanilla installations of WordPress, support for third party plugins will be a major leap forward for the project with the potential to greatly expand its user base. Check out VersionPress&#8217; <a href=\"http://docs.versionpress.net/en/release-notes/roadmap\" target=\"_blank\">roadmap</a> to follow along with its progress and see what&#8217;s next.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 06 May 2016 22:04:53 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:3843:\"<p><a href=\"https://blog.versionpress.net/2016/04/versionpress-3-0-released/\" target=\"_blank\">VersionPress 3.0</a>, released this week, is the first version since the plugin <a href=\"http://wptavern.com/versionpress-transitions-into-a-free-open-source-project\" target=\"_blank\">became a free, open source project</a>. Creators Borek Bernard and Jan Vorá?ek, who originally attempted to crowdfund the project and then <a href=\"http://wptavern.com/versionpress-raises-400k-in-seed-funding\" target=\"_blank\">raised $400,000 in seed funding</a>, <a href=\"http://wptavern.com/versionpress-transitions-into-a-free-open-source-project\" target=\"_blank\">announced</a> last month that they are transitioning to a public development model.</p>\n<p>The team&#8217;s goal with this release was to polish up the experience of using VersionPress in the default WordPress installation while adding more useful features. However, it is not yet ready for use in production, according to Bernard.</p>\n<p>&#8220;We’re still keeping VersionPress in the <a href=\"http://docs.versionpress.net/en/getting-started/about-eap\" target=\"_blank\">“early access” period</a>, because of the third party plugins integration story but on simpler sites, VersionPress already shines,&#8221; he said.</p>\n<p>One of the most notable new features in VersionPress 3.0 is the plugin&#8217;s ability to track commits with the environment where they were created. Users can view changes in the admin and easily see if they were pushed to the staging or production environment.</p>\n<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/commit-tracking-in-environment.gif\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/commit-tracking-in-environment.gif?resize=725%2C347\" alt=\"commit-tracking-in-environment\" class=\"aligncenter size-full wp-image-54599\" /></a></p>\n<p>Version 3.0 also adds searching capabilities for filtering commits by author, date, commit message, and WordPress action. This release also includes a new bulk undo feature for commits and many improvements to the core versioning engine.</p>\n<h3>VersionPress 4.0 to Focus on Support for 3rd Party Plugins</h3>\n<p>One of the reasons the VersionPress team decided to go with a public development model was to mitigate the plugin&#8217;s conflicts with third-party themes and plugins. This was only possible if the opened up the codebase for contribution from other developers.</p>\n<p>&#8220;While we had most of the WordPress core covered pretty well, there was still this huge ecosystem of WordPress plugins and themes that could cause trouble to VersionPress in million different ways,&#8221; Borek said. &#8220;In the long run, the project had to turn into OSS should it be successful, and, fortunately, we met investors who understood this and supported our vision.&#8221;</p>\n<p>Borek and the team plan to focus on adding support for complex third party plugins in version 4.0, tentatively scheduled for mid-2016. One commenter on the post mentioned that a lack of WooCommerce support is a major thing holding him back from using VersionPress on projects. Borek confirmed that WooCommerce is high on their list of plugins they want to support.</p>\n<p>&#8220;Our goal remains the same: to take all the incredibly powerful functionality of Git and package it so that every WordPress user can use it,&#8221; Borek said.</p>\n<p>Since most site owners interested in this plugin are not running vanilla installations of WordPress, support for third party plugins will be a major leap forward for the project with the potential to greatly expand its user base. Check out VersionPress&#8217; <a href=\"http://docs.versionpress.net/en/release-notes/roadmap\" target=\"_blank\">roadmap</a> to follow along with its progress and see what&#8217;s next.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:41;a:7:{s:5:\"title\";s:62:\"WPTavern: WordPress 4.5.2 Patches Two Security Vulnerabilities\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54594\";s:4:\"link\";s:72:\"http://wptavern.com/wordpress-4-5-2-patches-two-security-vulnerabilities\";s:11:\"description\";s:1441:\"<p>The WordPress core team has <a href=\"https://wordpress.org/news/2016/05/wordpress-4-5-2/\">released WordPress 4.5.2</a> which patches two security vulnerabilities in WordPress versions 4.5.1 and below. The first is a <a href=\"http://www.benhayak.com/2015/06/same-origin-method-execution-some.html\">SOME vulnerability</a> (Same-Origin Method Execution) in Plupload, the third-party library WordPress uses for uploading files. The second is a reflected cross-site-scripting vulnerability in MediaElement.js, the third-party library used for media players.</p>\n<p>Auto updates are rolling out to sites but if you don&#8217;t want to wait, browse to Dashboard &gt; Updates and click the Update Now button. Mario Heiderich, Masato Kinugawa, and Filedescriptor of <a href=\"https://cure53.de/\">Cure53</a> are credited with <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">responsibly disclosing</a> the vulnerabilities.</p>\n<p>In addition to the release, the core team has <a href=\"https://make.wordpress.org/core/2016/05/06/imagemagick-vulnerability-information/\">published a post</a> concerning the <a href=\"https://imagetragick.com/\">multiple vulnerabilities</a> discovered in ImageMagick, a popular image processing script used on thousands of webhosting servers. The post describes how WordPress is affected and what the team is doing to mitigate issues.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 06 May 2016 20:01:26 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:1441:\"<p>The WordPress core team has <a href=\"https://wordpress.org/news/2016/05/wordpress-4-5-2/\">released WordPress 4.5.2</a> which patches two security vulnerabilities in WordPress versions 4.5.1 and below. The first is a <a href=\"http://www.benhayak.com/2015/06/same-origin-method-execution-some.html\">SOME vulnerability</a> (Same-Origin Method Execution) in Plupload, the third-party library WordPress uses for uploading files. The second is a reflected cross-site-scripting vulnerability in MediaElement.js, the third-party library used for media players.</p>\n<p>Auto updates are rolling out to sites but if you don&#8217;t want to wait, browse to Dashboard &gt; Updates and click the Update Now button. Mario Heiderich, Masato Kinugawa, and Filedescriptor of <a href=\"https://cure53.de/\">Cure53</a> are credited with <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">responsibly disclosing</a> the vulnerabilities.</p>\n<p>In addition to the release, the core team has <a href=\"https://make.wordpress.org/core/2016/05/06/imagemagick-vulnerability-information/\">published a post</a> concerning the <a href=\"https://imagetragick.com/\">multiple vulnerabilities</a> discovered in ImageMagick, a popular image processing script used on thousands of webhosting servers. The post describes how WordPress is affected and what the team is doing to mitigate issues.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:42;a:7:{s:5:\"title\";s:97:\"WPTavern: Laravel Releases Valet, a Minimalist Development Environment with Support for WordPress\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54580\";s:4:\"link\";s:106:\"http://wptavern.com/laravel-releases-valet-a-minimalist-development-environment-with-support-for-wordpress\";s:11:\"description\";s:3404:\"<a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/valet-parking.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/valet-parking.jpg?resize=900%2C520\" alt=\"photo credit: Valet Parking, Las Vegas, NV - (license)\" class=\"size-full wp-image-54589\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/55151301@N00/175606346\">Valet Parking, Las Vegas, NV</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nd/2.0/\">(license)</a>\n<p><a href=\"https://laravel.com/\" target=\"_blank\">Laravel</a>, the open source MVC PHP framework created for application development, has just released <a href=\"https://laravel.com/docs/5.2/valet\" target=\"_blank\">Valet</a>, a minimalist development environment for Mac. It uses just 7mb of RAM, because it doesn&#8217;t include Vagrant, Apache, Nginx, or a /etc/hosts file. Here&#8217;s how it works:</p>\n<blockquote><p>Laravel Valet configures your Mac to always run PHP&#8217;s built-in web server in the background when your machine starts. Then, using DnsMasq, Valet proxies all requests on the *.dev domain to point to sites installed on your local machine.\n</p></blockquote>\n<p>Valet supports Laravel, Lumen, Statamic, Craft, Jigsaw, and even has a driver for WordPress. It&#8217;s handy if you just need a simple, fast development environment without virtualization. Developers can also share sites publicly via local tunnels. It&#8217;s as easy as navigating to the site&#8217;s directory in the terminal and running the <code>valet share</code> command, which generates a publicly accessible URL.</p>\n<p><a href=\"https://wppusher.com/\" target=\"_blank\">WP Pusher</a> founder Peter Suhm, who is active in both the Laravel and WordPress communities, wrote a <a href=\"http://blog.wppusher.com/a-minimalist-development-environment-for-wordpress-with-laravel-valet/\" target=\"_blank\">tutorial</a> for setting up Valet for WordPress development.</p>\n<p>&#8220;For larger apps, I generally prefer my development environment to be very similar to production,&#8221; Suhm said. &#8220;Vagrant and Docker are great for that. Valet is great for all those quick and dirty WordPress installations you need, just to test something or quickly work on an idea. If you don’t need anything else besides PHP 7 and a database, Valet is a great setup.&#8221;</p>\n<p>Since it doesn&#8217;t require a ton of dependencies, Valet is quick to set up and doesn&#8217;t require any configuration. Developers don&#8217;t even need to make Valet aware that their app is WordPress &#8211; you can simply drop WordPress core files into a folder on your machine and then access the site in your browser.</p>\n<p>If you&#8217;re looking for a new lightweight development environment or just a quick way to do some PHP 7 testing for WordPress plugins, Valet may fit nicely into your workflow. You can install it using <a href=\"http://brew.sh/\" target=\"_blank\">Homebrew</a>. View the <a href=\"https://laravel.com/docs/5.2/valet#installation\" target=\"_blank\">docs</a> for installation and site setup or follow along with Suhm&#8217;s <a href=\"http://blog.wppusher.com/a-minimalist-development-environment-for-wordpress-with-laravel-valet/\" target=\"_blank\">tutorial</a>.</p>\n<p>To see a quick demo of Valet in action, check out the two-minute introduction video created by Adam Wathan:</p>\n<div class=\"embed-wrap\"></div>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Fri, 06 May 2016 18:44:40 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:3404:\"<a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/valet-parking.jpg\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/valet-parking.jpg?resize=900%2C520\" alt=\"photo credit: Valet Parking, Las Vegas, NV - (license)\" class=\"size-full wp-image-54589\" /></a>photo credit: <a href=\"http://www.flickr.com/photos/55151301@N00/175606346\">Valet Parking, Las Vegas, NV</a> &#8211; <a href=\"https://creativecommons.org/licenses/by-nd/2.0/\">(license)</a>\n<p><a href=\"https://laravel.com/\" target=\"_blank\">Laravel</a>, the open source MVC PHP framework created for application development, has just released <a href=\"https://laravel.com/docs/5.2/valet\" target=\"_blank\">Valet</a>, a minimalist development environment for Mac. It uses just 7mb of RAM, because it doesn&#8217;t include Vagrant, Apache, Nginx, or a /etc/hosts file. Here&#8217;s how it works:</p>\n<blockquote><p>Laravel Valet configures your Mac to always run PHP&#8217;s built-in web server in the background when your machine starts. Then, using DnsMasq, Valet proxies all requests on the *.dev domain to point to sites installed on your local machine.\n</p></blockquote>\n<p>Valet supports Laravel, Lumen, Statamic, Craft, Jigsaw, and even has a driver for WordPress. It&#8217;s handy if you just need a simple, fast development environment without virtualization. Developers can also share sites publicly via local tunnels. It&#8217;s as easy as navigating to the site&#8217;s directory in the terminal and running the <code>valet share</code> command, which generates a publicly accessible URL.</p>\n<p><a href=\"https://wppusher.com/\" target=\"_blank\">WP Pusher</a> founder Peter Suhm, who is active in both the Laravel and WordPress communities, wrote a <a href=\"http://blog.wppusher.com/a-minimalist-development-environment-for-wordpress-with-laravel-valet/\" target=\"_blank\">tutorial</a> for setting up Valet for WordPress development.</p>\n<p>&#8220;For larger apps, I generally prefer my development environment to be very similar to production,&#8221; Suhm said. &#8220;Vagrant and Docker are great for that. Valet is great for all those quick and dirty WordPress installations you need, just to test something or quickly work on an idea. If you don’t need anything else besides PHP 7 and a database, Valet is a great setup.&#8221;</p>\n<p>Since it doesn&#8217;t require a ton of dependencies, Valet is quick to set up and doesn&#8217;t require any configuration. Developers don&#8217;t even need to make Valet aware that their app is WordPress &#8211; you can simply drop WordPress core files into a folder on your machine and then access the site in your browser.</p>\n<p>If you&#8217;re looking for a new lightweight development environment or just a quick way to do some PHP 7 testing for WordPress plugins, Valet may fit nicely into your workflow. You can install it using <a href=\"http://brew.sh/\" target=\"_blank\">Homebrew</a>. View the <a href=\"https://laravel.com/docs/5.2/valet#installation\" target=\"_blank\">docs</a> for installation and site setup or follow along with Suhm&#8217;s <a href=\"http://blog.wppusher.com/a-minimalist-development-environment-for-wordpress-with-laravel-valet/\" target=\"_blank\">tutorial</a>.</p>\n<p>To see a quick demo of Valet in action, check out the two-minute introduction video created by Adam Wathan:</p>\n<div class=\"embed-wrap\"></div>\n<div id=\"epoch-width-sniffer\"></div>\";}i:43;a:7:{s:5:\"title\";s:79:\"WPTavern: WordPress 4.6 to Drop Open Sans in the Admin in Favor of System Fonts\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54507\";s:4:\"link\";s:89:\"http://wptavern.com/wordpress-4-6-to-drop-open-sans-in-the-admin-in-favor-of-system-fonts\";s:11:\"description\";s:2130:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/system-fonts-firefox-osx.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/system-fonts-firefox-osx.png?resize=1025%2C450\" alt=\"system-fonts-firefox-osx\" class=\"aligncenter size-full wp-image-54575\" /></a></p>\n<p>WordPress 4.6 will bid farewell to Open Sans in the admin in favor of using system fonts. Open Sans, which loads from Google Fonts as an external resource, has been in use in the admin since 2013.</p>\n<p>&#8220;At the time of introduction in 3.8, there were not good system fonts common to all platforms at the time,&#8221; WordPress lead developer <a href=\"http://helenhousandi.com/\" target=\"_blank\">Helen Hou-Sandí</a> said in her <a href=\"https://core.trac.wordpress.org/changeset/37361\" target=\"_blank\">commit</a> message. &#8220;In the years since, Windows, Android, OS X, iOS, Firefox OS, and various flavors of Linux have all gotten their own (good) system UI fonts.&#8221;</p>\n<p>Now that the admin doesn&#8217;t have to load fonts from Google, it should feel faster and will provide a better experience for developers who are working offline.</p>\n<p>Dropping Open Sans originated as part of the <a href=\"https://make.wordpress.org/core/features/font-natively/\" target=\"_blank\">Font Natively</a> feature project led by WordPress designer <a href=\"https://mattmiklic.com/\" target=\"_blank\">Matt Miklic</a>, Mark Uraine, and Helen Hou-Sandí. The project page provides screenshots for the WP admin with Open Sans in Firefox on OSX vs the admin with system fonts, but the team noted that they are in need of more screenshots from different environments.</p>\n<p>Anytime that WordPress can shed a third-party dependency while improving the experience in the admin is a win for everyone. The commit comes early in the release cycle in order to get more people testing for misalignments and any other issues. Feel free to report any bugs you experience with the change, as work is still ongoing on the <a href=\"https://core.trac.wordpress.org/ticket/36753\" target=\"_blank\">ticket</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 05 May 2016 20:50:27 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2130:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/system-fonts-firefox-osx.png\"><img src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/system-fonts-firefox-osx.png?resize=1025%2C450\" alt=\"system-fonts-firefox-osx\" class=\"aligncenter size-full wp-image-54575\" /></a></p>\n<p>WordPress 4.6 will bid farewell to Open Sans in the admin in favor of using system fonts. Open Sans, which loads from Google Fonts as an external resource, has been in use in the admin since 2013.</p>\n<p>&#8220;At the time of introduction in 3.8, there were not good system fonts common to all platforms at the time,&#8221; WordPress lead developer <a href=\"http://helenhousandi.com/\" target=\"_blank\">Helen Hou-Sandí</a> said in her <a href=\"https://core.trac.wordpress.org/changeset/37361\" target=\"_blank\">commit</a> message. &#8220;In the years since, Windows, Android, OS X, iOS, Firefox OS, and various flavors of Linux have all gotten their own (good) system UI fonts.&#8221;</p>\n<p>Now that the admin doesn&#8217;t have to load fonts from Google, it should feel faster and will provide a better experience for developers who are working offline.</p>\n<p>Dropping Open Sans originated as part of the <a href=\"https://make.wordpress.org/core/features/font-natively/\" target=\"_blank\">Font Natively</a> feature project led by WordPress designer <a href=\"https://mattmiklic.com/\" target=\"_blank\">Matt Miklic</a>, Mark Uraine, and Helen Hou-Sandí. The project page provides screenshots for the WP admin with Open Sans in Firefox on OSX vs the admin with system fonts, but the team noted that they are in need of more screenshots from different environments.</p>\n<p>Anytime that WordPress can shed a third-party dependency while improving the experience in the admin is a win for everyone. The commit comes early in the release cycle in order to get more people testing for misalignments and any other issues. Feel free to report any bugs you experience with the change, as work is still ongoing on the <a href=\"https://core.trac.wordpress.org/ticket/36753\" target=\"_blank\">ticket</a>.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:44;a:7:{s:5:\"title\";s:68:\"WPTavern: Ninja Forms Update Patches Critical Security Vulnerability\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54556\";s:4:\"link\";s:78:\"http://wptavern.com/ninja-forms-update-patches-critical-security-vulnerability\";s:11:\"description\";s:4325:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/03/NinjaFormsFeaturedImage.png\"><img class=\"aligncenter size-full wp-image-40019\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/03/NinjaFormsFeaturedImage.png?resize=840%2C273\" alt=\"Ninja Forms Featured Image\" /></a><a href=\"https://wordpress.org/plugins/ninja-forms/\">Ninja Forms</a>, a popular plugin active on more than 500K websites, released an update 48 hours ago that addresses a critical security vulnerability. Wordfence <a href=\"https://www.wordfence.com/blog/2016/05/ninja-forms-shell-upload-vulnerability-high-risk/\">is reporting</a> that Ninja Forms versions 2.9.36 to 2.9.42 contain multiple security vulnerabilities.</p>\n<p>One of the vulnerabilities allows an attacker to upload and execute code remotely on WordPress sites. The only information needed to exploit the vulnerability is the URL of the target site that&#8217;s using a form powered by an affected version of Ninja Forms.</p>\n<p>Kevin Stover, CTO of Ninja Forms, explains to the Tavern how they discovered the vulnerabilities:</p>\n<blockquote><p>About two weeks ago, we were contacted by a security researcher, James Golovich, regarding a file upload issue within Ninja Forms. He demonstrated that it was possible to upload an arbitrary file using some test code that hadn’t been removed during our build process.</p>\n<p>We realised that the test code had accidentally been utilised in other areas of the plugin, and we immediately began working on a fix. While the issue was being patched, we reached out to the devs at the <a href=\"http://wordpress.org/\" target=\"_blank\" rel=\"noreferrer\">WordPress.org</a> repo and began the processes of preparing for auto updating users of the affected versions.</p>\n<p>Once the patch had been tested, we pushed version 2.9.43 and .1 versions of 2.9.36 &#8211; 2.9.42. Shortly after, <a href=\"http://wordpress.org/\" target=\"_blank\" rel=\"noreferrer\">WordPress.org</a> began pushing out automatic updates.</p></blockquote>\n<p>As to why there wasn&#8217;t a post published immediately on the official <a href=\"https://ninjaforms.com/blog/\">Ninja Forms blog</a> announcing the update, &#8220;We didn’t want to go public with the vulnerability until our users had time to update, both to the newest version and the .1 versions,&#8221; Stover said.</p>\n<p>&#8220;James Golovich&#8217;s responsible disclosure gave us time to fix the issue and for our users to update to safe versions before disclosing the vulnerability on his site,&#8221; he said. The company has since <a href=\"https://ninjaforms.com/important-security-update-always-hurt-ones-love/\">published a blog post </a>concerning the update.</p>\n<p>Working with the WordPress security team, automatic updates started rolling out on Tuesday, May 3rd. If automatic plugin updates are disabled, you&#8217;re highly encouraged to update manually to 2.9.45 as soon as possible. The Ninja Forms team is also working with a number of large webhosts to ensure as many sites as possible are updated.</p>\n<p>Wordfence is not detecting wide-spread exploitation but this could change in the next few days as details of the exploit emerge.</p>\n<p>When it comes to security vulnerabilities, the ability to upload and execute code remotely is about as severe as it gets. Golovich is credited with <a href=\"http://www.pritect.net/blog/ninja-forms-2-9-42-critical-security-vulnerabilities\">responsibly disclosing</a> the vulnerability to the Ninja Forms team. He also provides technical details of each vulnerability, most of which are in the Ninja Forms 3.0 code base.</p>\n<p>According to Golovich, the most vulnerable code is a proof of concept:</p>\n<blockquote><p>The following vulnerable code was, according to Kyle Johnson of the WP Ninjas team &#8216;not a live feature of Ninja Forms, but was more of a proof of concept for a future free feature.&#8217; Unfortunately, even proof of concept code that is accessible is still vulnerable to attack. This is the most critical vulnerability here because it potentially allows an attacker to execute arbitrary php code on a site.</p></blockquote>\n<p>Users should update as soon as possible as it&#8217;s only a matter of time before tools are created that can easily take advantage of the exploit.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 05 May 2016 20:46:19 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:4325:\"<p><a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/03/NinjaFormsFeaturedImage.png\"><img class=\"aligncenter size-full wp-image-40019\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2015/03/NinjaFormsFeaturedImage.png?resize=840%2C273\" alt=\"Ninja Forms Featured Image\" /></a><a href=\"https://wordpress.org/plugins/ninja-forms/\">Ninja Forms</a>, a popular plugin active on more than 500K websites, released an update 48 hours ago that addresses a critical security vulnerability. Wordfence <a href=\"https://www.wordfence.com/blog/2016/05/ninja-forms-shell-upload-vulnerability-high-risk/\">is reporting</a> that Ninja Forms versions 2.9.36 to 2.9.42 contain multiple security vulnerabilities.</p>\n<p>One of the vulnerabilities allows an attacker to upload and execute code remotely on WordPress sites. The only information needed to exploit the vulnerability is the URL of the target site that&#8217;s using a form powered by an affected version of Ninja Forms.</p>\n<p>Kevin Stover, CTO of Ninja Forms, explains to the Tavern how they discovered the vulnerabilities:</p>\n<blockquote><p>About two weeks ago, we were contacted by a security researcher, James Golovich, regarding a file upload issue within Ninja Forms. He demonstrated that it was possible to upload an arbitrary file using some test code that hadn’t been removed during our build process.</p>\n<p>We realised that the test code had accidentally been utilised in other areas of the plugin, and we immediately began working on a fix. While the issue was being patched, we reached out to the devs at the <a href=\"http://wordpress.org/\" target=\"_blank\" rel=\"noreferrer\">WordPress.org</a> repo and began the processes of preparing for auto updating users of the affected versions.</p>\n<p>Once the patch had been tested, we pushed version 2.9.43 and .1 versions of 2.9.36 &#8211; 2.9.42. Shortly after, <a href=\"http://wordpress.org/\" target=\"_blank\" rel=\"noreferrer\">WordPress.org</a> began pushing out automatic updates.</p></blockquote>\n<p>As to why there wasn&#8217;t a post published immediately on the official <a href=\"https://ninjaforms.com/blog/\">Ninja Forms blog</a> announcing the update, &#8220;We didn’t want to go public with the vulnerability until our users had time to update, both to the newest version and the .1 versions,&#8221; Stover said.</p>\n<p>&#8220;James Golovich&#8217;s responsible disclosure gave us time to fix the issue and for our users to update to safe versions before disclosing the vulnerability on his site,&#8221; he said. The company has since <a href=\"https://ninjaforms.com/important-security-update-always-hurt-ones-love/\">published a blog post </a>concerning the update.</p>\n<p>Working with the WordPress security team, automatic updates started rolling out on Tuesday, May 3rd. If automatic plugin updates are disabled, you&#8217;re highly encouraged to update manually to 2.9.45 as soon as possible. The Ninja Forms team is also working with a number of large webhosts to ensure as many sites as possible are updated.</p>\n<p>Wordfence is not detecting wide-spread exploitation but this could change in the next few days as details of the exploit emerge.</p>\n<p>When it comes to security vulnerabilities, the ability to upload and execute code remotely is about as severe as it gets. Golovich is credited with <a href=\"http://www.pritect.net/blog/ninja-forms-2-9-42-critical-security-vulnerabilities\">responsibly disclosing</a> the vulnerability to the Ninja Forms team. He also provides technical details of each vulnerability, most of which are in the Ninja Forms 3.0 code base.</p>\n<p>According to Golovich, the most vulnerable code is a proof of concept:</p>\n<blockquote><p>The following vulnerable code was, according to Kyle Johnson of the WP Ninjas team &#8216;not a live feature of Ninja Forms, but was more of a proof of concept for a future free feature.&#8217; Unfortunately, even proof of concept code that is accessible is still vulnerable to attack. This is the most critical vulnerability here because it potentially allows an attacker to execute arbitrary php code on a site.</p></blockquote>\n<p>Users should update as soon as possible as it&#8217;s only a matter of time before tools are created that can easily take advantage of the exploit.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:45;a:7:{s:5:\"title\";s:65:\"WPTavern: WordPress.org Support Forums Adds Accessibility Section\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54472\";s:4:\"link\";s:75:\"http://wptavern.com/wordpress-org-support-forums-adds-accessibility-section\";s:11:\"description\";s:3619:\"<p>Earlier this year, the WordPress project made a huge move by <a href=\"http://wptavern.com/wordpress-adopts-accessibility-coding-standards-for-all-new-and-updated-code\">adopting accessibility coding standards</a> for new and updated code. If you&#8217;re struggling to meet <a href=\"https://www.w3.org/WAI/intro/wcag\">WCAG 2.0 guidelines</a> in your WordPress projects and need help, check out the new <a href=\"https://wordpress.org/support/forum/accessibility\">Accessibility section</a> in the WordPress.org support forums.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WPAccessibilitySupport.png\"><img class=\"size-full wp-image-54551\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WPAccessibilitySupport.png?resize=1025%2C487\" alt=\"WordPress Accessibility Support\" /></a>WordPress Accessibility Support\n<p>Amanda Rush, who helps WordPress developers make their themes and plugins accessible, says the forum is the result of a conversation with a support team member at WordCamp Atlanta.</p>\n<p>&#8220;I <span class=\"message_body\">mentioned that part of what makes the job difficult when it comes to making WordPress accessible is stopping during our work to answer occasional questions.<br />\n</span></p>\n<p>&#8220;Most of the time the answer is not a quick one, because in the case of screen reader users, you have to first find out how well they can use their tech, how familiar they are with WordPress itself, and if neither of those chances are high, you spend time giving them a crash course in either one or both, and then answer their question,&#8221; <span class=\"message_body\">Rush said. </span></p>\n<p>Most of the people on the <a href=\"https://make.wordpress.org/accessibility/\">WordPress Accessibility team</a> are volunteers with full-time jobs which limits their ability to provide one-on-one support. Many of the support queries come through email or direct messages to individuals on the team. The forum enables everyone to participate in the support process.</p>\n<p>&#8220;If people ask their questions publicly, I or others not necessarily on the Accessibility Team can answer, and the answers are then public,&#8221; Rush said.</p>\n<p>&#8220;We have a pattern library on GitHub, which we all contribute to when we have time. But there are all kinds of solutions being passed around on Twitter and spread across other people&#8217;s GitHub accounts. So if someone asks a question like that, we can either point to something in specific cases, which is most of them, there&#8217;s probably already a specific solution that someone&#8217;s built, and we can link to that,&#8221; Rush told the Tavern.</p>\n<p>The accessibility support forum also comes with a side benefit, &#8220;W<span class=\"message_body\">e don&#8217;t have to say no all the time when people ask for support, or what looks like all the time to some people. Everyone can help each other </span><span class=\"message_body\">out and Google has a public resource,&#8221; Rush said.<br />\n</span></p>\n<p>The support forum comes at a time where accessibility is an increasingly important part of web development. For example, the European Union <a href=\"http://europa.eu/rapid/press-release_IP-16-1654_en.htm\">recently agreed to new rules</a> that will make public sector websites and apps more accessible.</p>\n<p>If you have any questions related to accessibility, you can post them on the forum. If you have experience and knowledge in the accessibility field, consider answering questions as it&#8217;s a great way to contribute to the WordPress project.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 05 May 2016 20:13:11 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:3619:\"<p>Earlier this year, the WordPress project made a huge move by <a href=\"http://wptavern.com/wordpress-adopts-accessibility-coding-standards-for-all-new-and-updated-code\">adopting accessibility coding standards</a> for new and updated code. If you&#8217;re struggling to meet <a href=\"https://www.w3.org/WAI/intro/wcag\">WCAG 2.0 guidelines</a> in your WordPress projects and need help, check out the new <a href=\"https://wordpress.org/support/forum/accessibility\">Accessibility section</a> in the WordPress.org support forums.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WPAccessibilitySupport.png\"><img class=\"size-full wp-image-54551\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WPAccessibilitySupport.png?resize=1025%2C487\" alt=\"WordPress Accessibility Support\" /></a>WordPress Accessibility Support\n<p>Amanda Rush, who helps WordPress developers make their themes and plugins accessible, says the forum is the result of a conversation with a support team member at WordCamp Atlanta.</p>\n<p>&#8220;I <span class=\"message_body\">mentioned that part of what makes the job difficult when it comes to making WordPress accessible is stopping during our work to answer occasional questions.<br />\n</span></p>\n<p>&#8220;Most of the time the answer is not a quick one, because in the case of screen reader users, you have to first find out how well they can use their tech, how familiar they are with WordPress itself, and if neither of those chances are high, you spend time giving them a crash course in either one or both, and then answer their question,&#8221; <span class=\"message_body\">Rush said. </span></p>\n<p>Most of the people on the <a href=\"https://make.wordpress.org/accessibility/\">WordPress Accessibility team</a> are volunteers with full-time jobs which limits their ability to provide one-on-one support. Many of the support queries come through email or direct messages to individuals on the team. The forum enables everyone to participate in the support process.</p>\n<p>&#8220;If people ask their questions publicly, I or others not necessarily on the Accessibility Team can answer, and the answers are then public,&#8221; Rush said.</p>\n<p>&#8220;We have a pattern library on GitHub, which we all contribute to when we have time. But there are all kinds of solutions being passed around on Twitter and spread across other people&#8217;s GitHub accounts. So if someone asks a question like that, we can either point to something in specific cases, which is most of them, there&#8217;s probably already a specific solution that someone&#8217;s built, and we can link to that,&#8221; Rush told the Tavern.</p>\n<p>The accessibility support forum also comes with a side benefit, &#8220;W<span class=\"message_body\">e don&#8217;t have to say no all the time when people ask for support, or what looks like all the time to some people. Everyone can help each other </span><span class=\"message_body\">out and Google has a public resource,&#8221; Rush said.<br />\n</span></p>\n<p>The support forum comes at a time where accessibility is an increasingly important part of web development. For example, the European Union <a href=\"http://europa.eu/rapid/press-release_IP-16-1654_en.htm\">recently agreed to new rules</a> that will make public sector websites and apps more accessible.</p>\n<p>If you have any questions related to accessibility, you can post them on the forum. If you have experience and knowledge in the accessibility field, consider answering questions as it&#8217;s a great way to contribute to the WordPress project.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:46;a:7:{s:5:\"title\";s:110:\"WPTavern: Font Awesome CDN Now in Beta, Loads Icons Asynchronously with Automatic Accessibility Best Practices\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54509\";s:4:\"link\";s:119:\"http://wptavern.com/font-awesome-cdn-now-in-beta-loads-icons-asynchronously-with-automatic-accessibility-best-practices\";s:11:\"description\";s:2903:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome.png?resize=1025%2C326\" alt=\"font-awesome\" class=\"aligncenter size-full wp-image-54532\" /></a></p>\n<p><a href=\"https://fortawesome.github.io/Font-Awesome/\" target=\"_blank\">Font Awesome</a>, the open source vector icon collection used by more than 300 plugins on WordPress.org and many free and commercial themes, <a href=\"https://articles.fortawesome.com/announcing-font-awesome-cdn-81773e0b301f#.egol888o7\" target=\"_blank\">announced the beta release of its new CDN</a>. Developers can now add a single line of code to bring the icons and CSS toolkit into their projects.</p>\n<p>The icon files and CSS are hosted by <a href=\"https://www.maxcdn.com/\" target=\"_blank\">MaxCDN</a>, which serves a cached version that loads quickly on websites that use Font Awesome. The CDN uses <a href=\"https://github.com/typekit/webfontloader\" target=\"_blank\">Web Font Loader</a>, which was co-developed by Google and Typekit, to load the icons asynchronously. This also gives developers <a href=\"https://github.com/typekit/webfontloader#events\" target=\"_blank\">CSS and JavaScript events</a> to hook into on loading.</p>\n<p><a href=\"http://wptavern.com/font-awesome-4-6-0-adds-new-accessibility-icons-category\" target=\"_blank\">FontAwesome 4.6 added a new accessibility icon category</a> and the new CDN helps to automate outputting the correct markup. If the icon you&#8217;re using has semantic meaning, including an accurate title attribute with the inline icon will trigger Font Awesome&#8217;s JS to do the rest.</p>\n<p>Font Awesome requires an email address from those want to use the CDN so it can issue a unique embed code for each. Developers also have the option to register a Font Awesome CDN account to keep track of sites and apps where they are using the icons, and manage multiple embed codes. Once logged in, you can enable or disable auto-accessibility, asynchronous icon loading, easy updates to newer Font Awesome versions, and CSS or JS embed.</p>\n<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome-account.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome-account.png?resize=1025%2C865\" alt=\"font-awesome-account\" class=\"aligncenter size-full wp-image-54543\" /></a></p>\n<p>One of the most convenient reasons to use the CDN is to simplify updates. WordPress plugin and theme developers do not have to bump versions or push any code to use the latest version. Font Awesome version changes can be triggered on an individual basis for each embed code in a developer&#8217;s account dashboard. Check out the instructions at <a href=\"https://cdn.fontawesome.com/\" target=\"_blank\">cdn.fontawesome.com</a> to get your project hooked up.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 05 May 2016 18:09:31 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Sarah Gooding\";}s:7:\"summary\";s:2903:\"<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome.png?resize=1025%2C326\" alt=\"font-awesome\" class=\"aligncenter size-full wp-image-54532\" /></a></p>\n<p><a href=\"https://fortawesome.github.io/Font-Awesome/\" target=\"_blank\">Font Awesome</a>, the open source vector icon collection used by more than 300 plugins on WordPress.org and many free and commercial themes, <a href=\"https://articles.fortawesome.com/announcing-font-awesome-cdn-81773e0b301f#.egol888o7\" target=\"_blank\">announced the beta release of its new CDN</a>. Developers can now add a single line of code to bring the icons and CSS toolkit into their projects.</p>\n<p>The icon files and CSS are hosted by <a href=\"https://www.maxcdn.com/\" target=\"_blank\">MaxCDN</a>, which serves a cached version that loads quickly on websites that use Font Awesome. The CDN uses <a href=\"https://github.com/typekit/webfontloader\" target=\"_blank\">Web Font Loader</a>, which was co-developed by Google and Typekit, to load the icons asynchronously. This also gives developers <a href=\"https://github.com/typekit/webfontloader#events\" target=\"_blank\">CSS and JavaScript events</a> to hook into on loading.</p>\n<p><a href=\"http://wptavern.com/font-awesome-4-6-0-adds-new-accessibility-icons-category\" target=\"_blank\">FontAwesome 4.6 added a new accessibility icon category</a> and the new CDN helps to automate outputting the correct markup. If the icon you&#8217;re using has semantic meaning, including an accurate title attribute with the inline icon will trigger Font Awesome&#8217;s JS to do the rest.</p>\n<p>Font Awesome requires an email address from those want to use the CDN so it can issue a unique embed code for each. Developers also have the option to register a Font Awesome CDN account to keep track of sites and apps where they are using the icons, and manage multiple embed codes. Once logged in, you can enable or disable auto-accessibility, asynchronous icon loading, easy updates to newer Font Awesome versions, and CSS or JS embed.</p>\n<p><a href=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome-account.png\"><img src=\"http://i1.wp.com/wptavern.com/wp-content/uploads/2016/05/font-awesome-account.png?resize=1025%2C865\" alt=\"font-awesome-account\" class=\"aligncenter size-full wp-image-54543\" /></a></p>\n<p>One of the most convenient reasons to use the CDN is to simplify updates. WordPress plugin and theme developers do not have to bump versions or push any code to use the latest version. Font Awesome version changes can be triggered on an individual basis for each embed code in a developer&#8217;s account dashboard. Check out the instructions at <a href=\"https://cdn.fontawesome.com/\" target=\"_blank\">cdn.fontawesome.com</a> to get your project hooked up.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:47;a:7:{s:5:\"title\";s:50:\"WP Mobile Apps: WordPress for Android: Version 5.3\";s:4:\"guid\";s:33:\"http://apps.wordpress.com/?p=3352\";s:4:\"link\";s:72:\"https://apps.wordpress.com/2016/05/05/wordpress-for-android-version-5-3/\";s:11:\"description\";s:3203:\"<p>Hello WordPress users! <a href=\"https://play.google.com/store/apps/details?id=org.wordpress.android\" target=\"_blank\">Version 5.3 of the WordPress for Android app</a> is now available in the Google Play Store.</p>\n<h1>Account Settings and App Settings</h1>\n<p>We split the old Account Settings into two distinct screens: Account Settings for everything related to your account, and App Settings for everything specific to the App, like the interface language, PIN lock, and Analytics opt-out.</p>\n<p><img class=\"alignnone size-full wp-image-3354\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_15-43-50-172.png?w=640\" alt=\"screenshot-2016-04-04_15.43.50.172\" /></p>\n<h1>Delete WordPress.com site</h1>\n<p>With 5.3, you can now export your content (posts, pages, and settings) by email and delete your WordPress.com site from the app.</p>\n<p><img class=\"alignnone size-full wp-image-3356\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_15-45-34-504.png?w=640\" alt=\"screenshot-2016-04-04_15.45.34.504\" /></p>\n<h1>Other Changes</h1>\n<p>Version 5.3 also comes with a few other enhancements:</p>\n<ul>\n<li>New styling of the action bar in the Reader.</li>\n<li>If you made changes to a post, you&#8217;ll see a confirmation blink on <strong>Blog Posts</strong> when returning to the <strong>My site</strong> screen.</li>\n<li>Better styling of the Post and Page Preview screen.</li>\n<li>An updated support tool reduces crashes.</li>\n</ul>\n\n<a href=\"https://apps.wordpress.com/2016/05/05/wordpress-for-android-version-5-3/screenshot-2016-04-04_15-59-35-639/\"><img width=\"84\" height=\"150\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_15-59-35-639.png?w=84&h=150\" class=\"attachment-thumbnail size-thumbnail\" alt=\"screenshot-2016-04-04_15.59.35.639\" /></a>\n<a href=\"https://apps.wordpress.com/2016/05/05/wordpress-for-android-version-5-3/screenshot-2016-04-04_16-01-41-971/\"><img width=\"84\" height=\"150\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_16-01-41-971.png?w=84&h=150\" class=\"attachment-thumbnail size-thumbnail\" alt=\"screenshot-2016-04-04_16.01.41.971\" /></a>\n\n<p>We&#8217;re working hard on new features for the next version &#8212; you can track our development progress for the next release by visiting <a href=\"https://github.com/wordpress-mobile/WordPress-Android/milestones/5.4\">our 5.4 milestone on GitHub</a>.</p>\n<h1>Thank you</h1>\n<p>Thanks to our contributors: <a href=\"https://github.com/aforcier\">@aforcier</a>, <a href=\"https://github.com/daniloercoli\">@daniloercoli</a>, <a href=\"https://github.com/hypest\">@hypest</a>, <a href=\"https://github.com/kwonye\">@kwonye</a>, <a href=\"https://github.com/maxme\">@maxme</a>, <a href=\"https://github.com/mzorz\">@mzorz</a>, <a href=\"https://github.com/nbradbury\">@nbradbury</a>, <a href=\"https://github.com/oguzkocer\">@oguzkocer</a>, <a href=\"https://github.com/rishabh7m\">@rishabh7m</a>, <a href=\"https://github.com/roundhill\">@roundhill</a>, and <a href=\"https://github.com/tonyr59h\">@tonyr59h</a>.</p><img alt=\"\" border=\"0\" src=\"https://pixel.wp.com/b.gif?host=apps.wordpress.com&blog=108068616&post=3352&subd=apps&ref=&feed=1\" width=\"1\" height=\"1\" />\";s:7:\"pubdate\";s:31:\"Thu, 05 May 2016 08:57:23 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:6:\"Maxime\";}s:7:\"summary\";s:3203:\"<p>Hello WordPress users! <a href=\"https://play.google.com/store/apps/details?id=org.wordpress.android\" target=\"_blank\">Version 5.3 of the WordPress for Android app</a> is now available in the Google Play Store.</p>\n<h1>Account Settings and App Settings</h1>\n<p>We split the old Account Settings into two distinct screens: Account Settings for everything related to your account, and App Settings for everything specific to the App, like the interface language, PIN lock, and Analytics opt-out.</p>\n<p><img class=\"alignnone size-full wp-image-3354\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_15-43-50-172.png?w=640\" alt=\"screenshot-2016-04-04_15.43.50.172\" /></p>\n<h1>Delete WordPress.com site</h1>\n<p>With 5.3, you can now export your content (posts, pages, and settings) by email and delete your WordPress.com site from the app.</p>\n<p><img class=\"alignnone size-full wp-image-3356\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_15-45-34-504.png?w=640\" alt=\"screenshot-2016-04-04_15.45.34.504\" /></p>\n<h1>Other Changes</h1>\n<p>Version 5.3 also comes with a few other enhancements:</p>\n<ul>\n<li>New styling of the action bar in the Reader.</li>\n<li>If you made changes to a post, you&#8217;ll see a confirmation blink on <strong>Blog Posts</strong> when returning to the <strong>My site</strong> screen.</li>\n<li>Better styling of the Post and Page Preview screen.</li>\n<li>An updated support tool reduces crashes.</li>\n</ul>\n\n<a href=\"https://apps.wordpress.com/2016/05/05/wordpress-for-android-version-5-3/screenshot-2016-04-04_15-59-35-639/\"><img width=\"84\" height=\"150\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_15-59-35-639.png?w=84&h=150\" class=\"attachment-thumbnail size-thumbnail\" alt=\"screenshot-2016-04-04_15.59.35.639\" /></a>\n<a href=\"https://apps.wordpress.com/2016/05/05/wordpress-for-android-version-5-3/screenshot-2016-04-04_16-01-41-971/\"><img width=\"84\" height=\"150\" src=\"https://apps.files.wordpress.com/2016/04/screenshot-2016-04-04_16-01-41-971.png?w=84&h=150\" class=\"attachment-thumbnail size-thumbnail\" alt=\"screenshot-2016-04-04_16.01.41.971\" /></a>\n\n<p>We&#8217;re working hard on new features for the next version &#8212; you can track our development progress for the next release by visiting <a href=\"https://github.com/wordpress-mobile/WordPress-Android/milestones/5.4\">our 5.4 milestone on GitHub</a>.</p>\n<h1>Thank you</h1>\n<p>Thanks to our contributors: <a href=\"https://github.com/aforcier\">@aforcier</a>, <a href=\"https://github.com/daniloercoli\">@daniloercoli</a>, <a href=\"https://github.com/hypest\">@hypest</a>, <a href=\"https://github.com/kwonye\">@kwonye</a>, <a href=\"https://github.com/maxme\">@maxme</a>, <a href=\"https://github.com/mzorz\">@mzorz</a>, <a href=\"https://github.com/nbradbury\">@nbradbury</a>, <a href=\"https://github.com/oguzkocer\">@oguzkocer</a>, <a href=\"https://github.com/rishabh7m\">@rishabh7m</a>, <a href=\"https://github.com/roundhill\">@roundhill</a>, and <a href=\"https://github.com/tonyr59h\">@tonyr59h</a>.</p><img alt=\"\" border=\"0\" src=\"https://pixel.wp.com/b.gif?host=apps.wordpress.com&blog=108068616&post=3352&subd=apps&ref=&feed=1\" width=\"1\" height=\"1\" />\";}i:48;a:7:{s:5:\"title\";s:65:\"WPTavern: WPWeekly Episode 233 – Recap of WordCamp Chicago 2016\";s:4:\"guid\";s:44:\"http://wptavern.com?p=54518&preview_id=54518\";s:4:\"link\";s:71:\"http://wptavern.com/wpweekly-episode-233-recap-of-wordcamp-chicago-2016\";s:11:\"description\";s:2903:\"<p>On this episode of WordPress Weekly, I describe my experience attending WordCamp Chicago 2016 this past weekend. Marcus Couch and I then discuss the news of the week including a new tool that helps WordCamp organizers create customized name badges.</p>\n<p>We also have a lengthy discussion on the freemium business model and how it&#8217;s affecting users of themes and plugins downloaded from the official directories. Last but not least, we talk about WooCommerce Connect, a new SaaS tool from Automattic that has a tight relationship with Jetpack.</p>\n<h2>Stories Discussed:</h2>\n<p><a href=\"http://wptavern.com/wordcamp-organizers-get-new-tool-for-creating-personalized-wordcamp-badges\">WordCamp Organizers Get New Tool for Creating Personalized WordCamp Badges</a><br />\n<a href=\"http://wptavern.com/wordpress-is-now-100-translated-into-marathi\">WordPress is Now 100% Translated Into Marathi</a><br />\n<a href=\"http://wptavern.com/templatic-hacked-files-and-databases-compromised\">Templatic Hacked, Files and Databases Compromised</a><br />\n<a href=\"http://wptavern.com/wordpress-theme-review-team-votes-on-new-guidelines-to-ban-obtrusive-upselling\">WordPress Theme Review Team Votes on New Guidelines to Ban Obtrusive Upselling</a><br />\n<a href=\"http://wptavern.com/automattic-introduces-woocommerce-connect-hosted-components-for-e-commerce\">Automattic Introduces WooCommerce Connect, Hosted Components for E-Commerce</a></p>\n<h2>Plugins Picked By Marcus:</h2>\n<p><a href=\"https://wordpress.org/plugins/rss-feed-canceller/\">RSS Feed Canceller </a>provides more control over your RSS feed. You can turn it on or off per post and control whether or not a post is excluded from the feed.</p>\n<p><a href=\"https://wordpress.org/plugins/tld-woocommerce-downloadable-product-update-emails/\">TLD WooCommerce Downloadable Product Update Emails</a> is a simple plugin that notifies customers who purchased a downloadable product via email that there&#8217;s an update available.</p>\n<p><a href=\"https://wordpress.org/plugins/inline-click-to-tweet/\">Inline Click To Tweet</a> allows authors to highlight text from within the visual editor and make it tweetable by clicking within the post or page.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, May 11th 9:30 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href=\"https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href=\"http://www.wptavern.com/feed/podcast\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href=\"http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #233:</strong><br />\n</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 05 May 2016 08:46:25 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:2903:\"<p>On this episode of WordPress Weekly, I describe my experience attending WordCamp Chicago 2016 this past weekend. Marcus Couch and I then discuss the news of the week including a new tool that helps WordCamp organizers create customized name badges.</p>\n<p>We also have a lengthy discussion on the freemium business model and how it&#8217;s affecting users of themes and plugins downloaded from the official directories. Last but not least, we talk about WooCommerce Connect, a new SaaS tool from Automattic that has a tight relationship with Jetpack.</p>\n<h2>Stories Discussed:</h2>\n<p><a href=\"http://wptavern.com/wordcamp-organizers-get-new-tool-for-creating-personalized-wordcamp-badges\">WordCamp Organizers Get New Tool for Creating Personalized WordCamp Badges</a><br />\n<a href=\"http://wptavern.com/wordpress-is-now-100-translated-into-marathi\">WordPress is Now 100% Translated Into Marathi</a><br />\n<a href=\"http://wptavern.com/templatic-hacked-files-and-databases-compromised\">Templatic Hacked, Files and Databases Compromised</a><br />\n<a href=\"http://wptavern.com/wordpress-theme-review-team-votes-on-new-guidelines-to-ban-obtrusive-upselling\">WordPress Theme Review Team Votes on New Guidelines to Ban Obtrusive Upselling</a><br />\n<a href=\"http://wptavern.com/automattic-introduces-woocommerce-connect-hosted-components-for-e-commerce\">Automattic Introduces WooCommerce Connect, Hosted Components for E-Commerce</a></p>\n<h2>Plugins Picked By Marcus:</h2>\n<p><a href=\"https://wordpress.org/plugins/rss-feed-canceller/\">RSS Feed Canceller </a>provides more control over your RSS feed. You can turn it on or off per post and control whether or not a post is excluded from the feed.</p>\n<p><a href=\"https://wordpress.org/plugins/tld-woocommerce-downloadable-product-update-emails/\">TLD WooCommerce Downloadable Product Update Emails</a> is a simple plugin that notifies customers who purchased a downloadable product via email that there&#8217;s an update available.</p>\n<p><a href=\"https://wordpress.org/plugins/inline-click-to-tweet/\">Inline Click To Tweet</a> allows authors to highlight text from within the visual editor and make it tweetable by clicking within the post or page.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, May 11th 9:30 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href=\"https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href=\"http://www.wptavern.com/feed/podcast\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href=\"http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr\" target=\"_blank\">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #233:</strong><br />\n</p>\n<div id=\"epoch-width-sniffer\"></div>\";}i:49;a:7:{s:5:\"title\";s:54:\"WPTavern: WordCamp Chicago 2016 Was a Deep Dish of Fun\";s:4:\"guid\";s:28:\"http://wptavern.com/?p=54453\";s:4:\"link\";s:64:\"http://wptavern.com/wordcamp-chicago-2016-was-a-deep-dish-of-fun\";s:11:\"description\";s:5547:\"<p><a href=\"https://2016.chicago.wordcamp.org/\">WordCamp Chicago 2016</a> was held at University Center in the heart of Chicago, IL, where more than 300 attendees spent the weekend learning about WordPress. The event was organized by Ryan Erwin and a <a href=\"https://2016.chicago.wordcamp.org/organizers/\">team of volunteers. </a></p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/JJJWCChicago2016.jpg\"><img class=\"size-full wp-image-54500\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/JJJWCChicago2016.jpg?resize=1024%2C768\" alt=\"John James Jacoby talking about bbPress and BuddyPress\" /></a>John James Jacoby talking about bbPress and BuddyPress\n<p>Tracks were split up into three separate rooms limiting the amount of background noise during sessions. Giving attendees a schedule is handled differently at most camps. Some provide a paper schedule while others put it on the back of the name badge.</p>\n<p>At WordCamp Chicago, schedule boards were displayed outside each room that corresponded with a track number. This made it easier for attendees to determine if they wanted to stay in the room for the next session.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016Schedule.jpg\"><img class=\"size-full wp-image-54501\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016Schedule.jpg?resize=1024%2C1365\" alt=\"Schedule Board Outside The Room Hosting Track 1\" /></a>Schedule Board Outside The Room Hosting Track 1\n<p>WordCamps are a great way to stress test a venue&#8217;s network but the WiFi at WordCamp Chicago was flawless. I didn&#8217;t experience any issues and it remained fast throughout the event. I didn&#8217;t stick around for lunch as there are plenty of lunch options available within walking distance of the venue.</p>\n<h2>The After Party</h2>\n<p>Most WordCamps host an after party at a restaurant, bar, or other establishment away from the venue. WordCamp Chicago&#8217;s after party was held at the venue. It included, non-alcoholic and alcoholic drinks, food, and card games on each table. It was fun mingling and networking with people without having to compete with blaring music or a loud atmosphere.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016AfterParty.jpg\"><img class=\"size-full wp-image-54503\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016AfterParty.jpg?resize=1024%2C768\" alt=\"WordCamp Chicago 2016 After Party\" /></a>WordCamp Chicago 2016 After Party\n<p>Out of all the sessions I attended, my favorite is <a href=\"https://2016.chicago.wordcamp.org/session/disastrous-deals-to-profitable-projects-comparing-my-best-and-worst-client-experiences/\">by Kyle Maurer,</a> who shared experiences and advice from <a href=\"http://realbigmarketing.com/\">building client websites</a> over the years.</p>\n<p>One of the biggest pieces of advice he shared is to build direct relationships with clients. No one is going to fight your battles as much as you and third-parties are unlikely to stick their neck out. Managing direct relationships leads to trust, referrals, and being rehired to do additional work.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/KyleMaurerSlideWCChicago2016.jpg\"><img class=\"size-full wp-image-54504\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/KyleMaurerSlideWCChicago2016.jpg?resize=1024%2C768\" alt=\"A Slide from Kyle Maurer\'s Presentation\" /></a>A Slide from Kyle Maurer&#8217;s Presentation\n<p>His session contains a lot of great information and I highly encourage you to watch it when it&#8217;s published on WordPress.tv.</p>\n<h2>WordCamps Offer a Lot of Value For The Price</h2>\n<p>Throughout the event, I spoke to a number of people and noted the following. Many attendees said they received more value than expected paying $40 a ticket. Some have spent hundreds of dollars on conference tickets and didn&#8217;t enjoy themselves or come away with nearly as much information.</p>\n<p>I discovered a number of attendees are part of one or more WordPress meetup groups. According to Meetup.com, there are at least <a href=\"http://www.meetup.com/find/?allMeetups=false&keywords=Chicago+WordPress&radius=25&userFreeform=chicago+I&mcId=c60601&change=yes&sort=recommended&eventFilter=mysugg\">four WordPress groups </a>with hundreds of members spread throughout the Chicago area. It&#8217;s a strong indication that the WordPress community in Chicago is thriving and supportive of each other.</p>\n<h2>WordCamp Chicago in 2017</h2>\n<p>It was a pleasure attending WordCamp Chicago and making new friends. I especially enjoyed speaking to WordPress Weekly listeners and getting their feedback. Also for those wondering, I satisfied my craving for deep-dish pizza via <a href=\"http://www.loumalnatis.com/arizona-phoenix\">Lou Malnati&#8217;s</a>. The pizza tastes better than I remembered. If you&#8217;re ever in the Chicago area, you have to try Lou Malnati&#8217;s pizza.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/TheLou.jpg\"><img class=\"size-full wp-image-54505\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/TheLou.jpg?resize=1024%2C768\" alt=\"The Lou!\" /></a>The Lou!\n<p>Everyone involved with WordCamp Chicago 2016 did a great job. If you didn&#8217;t get a chance to attend this year, don&#8217;t worry. After taking a break for a few weeks, the organizing team plans to begin organizing WordCamp Chicago 2017.</p>\n<div id=\"epoch-width-sniffer\"></div>\";s:7:\"pubdate\";s:31:\"Thu, 05 May 2016 03:00:06 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:13:\"Jeff Chandler\";}s:7:\"summary\";s:5547:\"<p><a href=\"https://2016.chicago.wordcamp.org/\">WordCamp Chicago 2016</a> was held at University Center in the heart of Chicago, IL, where more than 300 attendees spent the weekend learning about WordPress. The event was organized by Ryan Erwin and a <a href=\"https://2016.chicago.wordcamp.org/organizers/\">team of volunteers. </a></p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/JJJWCChicago2016.jpg\"><img class=\"size-full wp-image-54500\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/JJJWCChicago2016.jpg?resize=1024%2C768\" alt=\"John James Jacoby talking about bbPress and BuddyPress\" /></a>John James Jacoby talking about bbPress and BuddyPress\n<p>Tracks were split up into three separate rooms limiting the amount of background noise during sessions. Giving attendees a schedule is handled differently at most camps. Some provide a paper schedule while others put it on the back of the name badge.</p>\n<p>At WordCamp Chicago, schedule boards were displayed outside each room that corresponded with a track number. This made it easier for attendees to determine if they wanted to stay in the room for the next session.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016Schedule.jpg\"><img class=\"size-full wp-image-54501\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016Schedule.jpg?resize=1024%2C1365\" alt=\"Schedule Board Outside The Room Hosting Track 1\" /></a>Schedule Board Outside The Room Hosting Track 1\n<p>WordCamps are a great way to stress test a venue&#8217;s network but the WiFi at WordCamp Chicago was flawless. I didn&#8217;t experience any issues and it remained fast throughout the event. I didn&#8217;t stick around for lunch as there are plenty of lunch options available within walking distance of the venue.</p>\n<h2>The After Party</h2>\n<p>Most WordCamps host an after party at a restaurant, bar, or other establishment away from the venue. WordCamp Chicago&#8217;s after party was held at the venue. It included, non-alcoholic and alcoholic drinks, food, and card games on each table. It was fun mingling and networking with people without having to compete with blaring music or a loud atmosphere.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016AfterParty.jpg\"><img class=\"size-full wp-image-54503\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/WCChicago2016AfterParty.jpg?resize=1024%2C768\" alt=\"WordCamp Chicago 2016 After Party\" /></a>WordCamp Chicago 2016 After Party\n<p>Out of all the sessions I attended, my favorite is <a href=\"https://2016.chicago.wordcamp.org/session/disastrous-deals-to-profitable-projects-comparing-my-best-and-worst-client-experiences/\">by Kyle Maurer,</a> who shared experiences and advice from <a href=\"http://realbigmarketing.com/\">building client websites</a> over the years.</p>\n<p>One of the biggest pieces of advice he shared is to build direct relationships with clients. No one is going to fight your battles as much as you and third-parties are unlikely to stick their neck out. Managing direct relationships leads to trust, referrals, and being rehired to do additional work.</p>\n<a href=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/KyleMaurerSlideWCChicago2016.jpg\"><img class=\"size-full wp-image-54504\" src=\"http://i0.wp.com/wptavern.com/wp-content/uploads/2016/05/KyleMaurerSlideWCChicago2016.jpg?resize=1024%2C768\" alt=\"A Slide from Kyle Maurer\'s Presentation\" /></a>A Slide from Kyle Maurer&#8217;s Presentation\n<p>His session contains a lot of great information and I highly encourage you to watch it when it&#8217;s published on WordPress.tv.</p>\n<h2>WordCamps Offer a Lot of Value For The Price</h2>\n<p>Throughout the event, I spoke to a number of people and noted the following. Many attendees said they received more value than expected paying $40 a ticket. Some have spent hundreds of dollars on conference tickets and didn&#8217;t enjoy themselves or come away with nearly as much information.</p>\n<p>I discovered a number of attendees are part of one or more WordPress meetup groups. According to Meetup.com, there are at least <a href=\"http://www.meetup.com/find/?allMeetups=false&keywords=Chicago+WordPress&radius=25&userFreeform=chicago+I&mcId=c60601&change=yes&sort=recommended&eventFilter=mysugg\">four WordPress groups </a>with hundreds of members spread throughout the Chicago area. It&#8217;s a strong indication that the WordPress community in Chicago is thriving and supportive of each other.</p>\n<h2>WordCamp Chicago in 2017</h2>\n<p>It was a pleasure attending WordCamp Chicago and making new friends. I especially enjoyed speaking to WordPress Weekly listeners and getting their feedback. Also for those wondering, I satisfied my craving for deep-dish pizza via <a href=\"http://www.loumalnatis.com/arizona-phoenix\">Lou Malnati&#8217;s</a>. The pizza tastes better than I remembered. If you&#8217;re ever in the Chicago area, you have to try Lou Malnati&#8217;s pizza.</p>\n<a href=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/TheLou.jpg\"><img class=\"size-full wp-image-54505\" src=\"http://i2.wp.com/wptavern.com/wp-content/uploads/2016/05/TheLou.jpg?resize=1024%2C768\" alt=\"The Lou!\" /></a>The Lou!\n<p>Everyone involved with WordCamp Chicago 2016 did a great job. If you didn&#8217;t get a chance to attend this year, don&#8217;t worry. After taking a break for a few weeks, the organizing team plans to begin organizing WordCamp Chicago 2017.</p>\n<div id=\"epoch-width-sniffer\"></div>\";}}s:7:\"channel\";a:5:{s:5:\"title\";s:16:\"WordPress Planet\";s:4:\"link\";s:28:\"http://planet.wordpress.org/\";s:8:\"language\";s:2:\"en\";s:11:\"description\";s:47:\"WordPress Planet - http://planet.wordpress.org/\";s:7:\"tagline\";s:47:\"WordPress Planet - http://planet.wordpress.org/\";}s:9:\"textinput\";a:0:{}s:5:\"image\";a:0:{}s:9:\"feed_type\";s:3:\"RSS\";s:12:\"feed_version\";s:3:\"2.0\";s:5:\"stack\";a:0:{}s:9:\"inchannel\";b:0;s:6:\"initem\";b:0;s:9:\"incontent\";b:0;s:11:\"intextinput\";b:0;s:7:\"inimage\";b:0;s:13:\"current_field\";s:0:\"\";s:17:\"current_namespace\";b:0;s:19:\"_CONTENT_CONSTRUCTS\";a:6:{i:0;s:7:\"content\";i:1;s:7:\"summary\";i:2;s:4:\"info\";i:3;s:5:\"title\";i:4;s:7:\"tagline\";i:5;s:9:\"copyright\";}s:13:\"last_modified\";s:31:\"Sun, 12 Jun 2016 01:30:18 GMT\r\n\";}', 'no');
