CREATE TABLE IF NOT EXISTS `wp_links` (
  `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_image` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_target` varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_description` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_visible` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'Y',
  `link_owner` bigint(20) unsigned 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) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `link_notes` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL,
  `link_rss` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  PRIMARY KEY (`link_id`),
  KEY `link_visible` (`link_visible`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci AUTO_INCREMENT=1 ;

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

--
-- بنية الجدول `wp_maillist`
--

CREATE TABLE IF NOT EXISTS `wp_maillist` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) CHARACTER SET utf8 NOT NULL,
  `date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `email` varchar(255) CHARACTER SET utf8 NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci AUTO_INCREMENT=3 ;

--
-- إرجاع أو استيراد بيانات الجدول `wp_maillist`
--

INSERT INTO `wp_maillist` (`id`, `name`, `date`, `email`) VALUES
(1, '', '2015-05-13 02:04:52', 'mohf_1992@hotmail.com'),
(2, '', '2015-05-24 16:08:05', 'ENG.SAMEH@SAMACO.SA');

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

--
-- بنية الجدول `wp_options`
--

CREATE TABLE IF NOT EXISTS `wp_options` (
  `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
  `option_name` varchar(64) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '',
  `option_value` longtext COLLATE utf8mb4_unicode_ci NOT NULL,
  `autoload` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'yes',
  PRIMARY KEY (`option_id`),
  UNIQUE KEY `option_name` (`option_name`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci AUTO_INCREMENT=782 ;


INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(438, '_icl_cache', 'a:3:{s:17:"flags_cache_class";a:2:{s:2:"en";O:8:"stdClass":2:{s:4:"flag";s:6:"en.png";s:13:"from_template";s:1:"0";}s:2:"ar";O:8:"stdClass":2:{s:4:"flag";s:6:"ar.png";s:13:"from_template";s:1:"0";}}s:25:"language_name_cache_class";a:196:{s:14:"in_language_ar";a:2:{i:0;a:8:{s:2:"id";s:1:"1";s:4:"code";s:2:"en";s:12:"english_name";s:7:"English";s:6:"active";s:1:"1";s:12:"display_name";s:20:"الإنجليزية";s:10:"encode_url";s:1:"0";s:14:"default_locale";s:5:"en_US";s:3:"tag";s:5:"en-US";}i:1;a:8:{s:2:"id";s:1:"5";s:4:"code";s:2:"ar";s:12:"english_name";s:6:"Arabic";s:6:"active";s:1:"1";s:12:"display_name";s:14:"العربية";s:10:"encode_url";s:1:"0";s:14:"default_locale";s:2:"ar";s:3:"tag";s:2:"ar";}}s:9:"languages";a:2:{i:0;O:8:"stdClass":2:{s:13:"language_code";s:2:"ar";s:4:"name";s:14:"العربية";}i:1;O:8:"stdClass":2:{s:13:"language_code";s:2:"en";s:4:"name";s:7:"English";}}s:21:"language_details_arar";a:5:{s:4:"code";s:2:"ar";s:12:"english_name";s:6:"Arabic";s:5:"major";s:1:"0";s:6:"active";s:1:"1";s:12:"display_name";s:14:"العربية";}s:4:"arar";s:14:"العربية";s:4:"enen";s:7:"English";s:4:"enar";s:20:"الإنجليزية";s:21:"language_details_enar";a:5:{s:4:"code";s:2:"en";s:12:"english_name";s:7:"English";s:5:"major";s:1:"1";s:6:"active";s:1:"1";s:12:"display_name";s:20:"الإنجليزية";}s:4:"aren";s:6:"Arabic";s:21:"language_details_enen";a:5:{s:4:"code";s:2:"en";s:12:"english_name";s:7:"English";s:5:"major";s:1:"1";s:6:"active";s:1:"1";s:12:"display_name";s:7:"English";}s:19:"language_details_ar";N;s:29:"language_details_enfeedenfeed";N;s:8:"enenfeed";N;s:8:"arenfeed";N;s:37:"language_details_enfeedfeedenfeedfeed";N;s:12:"arenfeedfeed";N;s:45:"language_details_enfeedfeedfeedenfeedfeedfeed";N;s:16:"arenfeedfeedfeed";N;s:53:"language_details_enfeedfeedfeedfeedenfeedfeedfeedfeed";N;s:20:"arenfeedfeedfeedfeed";N;s:61:"language_details_enfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeed";N;s:24:"arenfeedfeedfeedfeedfeed";N;s:69:"language_details_enfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeed";N;s:28:"arenfeedfeedfeedfeedfeedfeed";N;s:77:"language_details_enfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeed";N;s:32:"arenfeedfeedfeedfeedfeedfeedfeed";N;s:85:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeed";N;s:36:"arenfeedfeedfeedfeedfeedfeedfeedfeed";N;s:93:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:40:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:101:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:44:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:109:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:48:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:117:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:52:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:125:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:56:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:133:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:60:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:141:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:64:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:149:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:68:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:157:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:72:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:165:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:76:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:173:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:80:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:181:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:84:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:189:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:88:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:197:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:92:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:205:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:96:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:213:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:100:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:221:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:104:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:229:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:108:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:237:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:112:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:245:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:116:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:253:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:120:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:261:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:124:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:269:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:128:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:12:"enenfeedfeed";N;s:16:"enenfeedfeedfeed";N;s:20:"enenfeedfeedfeedfeed";N;s:24:"enenfeedfeedfeedfeedfeed";N;s:28:"enenfeedfeedfeedfeedfeedfeed";N;s:32:"enenfeedfeedfeedfeedfeedfeedfeed";N;s:36:"enenfeedfeedfeedfeedfeedfeedfeedfeed";N;s:40:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:44:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:48:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:52:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:56:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:60:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:64:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:68:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:72:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:76:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:80:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:84:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:88:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:92:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:96:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:100:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:104:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:108:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:112:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:116:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:120:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:124:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:128:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:277:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:132:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:132:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:285:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:136:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:136:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:293:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:140:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:140:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:301:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:144:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:144:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:309:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:148:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:148:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:317:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:152:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:152:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:325:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:156:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:156:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:333:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:160:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:160:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:341:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:164:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:164:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:349:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:168:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:168:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:357:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:172:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:172:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:365:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:176:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:176:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:373:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:180:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:180:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:381:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:184:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:184:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:389:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:188:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:188:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:397:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:192:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:192:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:405:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:196:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:196:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:413:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:200:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:200:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:421:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:204:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:204:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:429:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:208:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:208:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:437:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:212:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:212:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:445:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:216:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:216:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:453:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:220:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:220:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:461:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:224:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:224:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:469:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:228:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:228:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:477:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:232:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:232:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:485:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:236:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:236:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:493:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:240:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:240:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:501:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:244:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:244:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:509:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:248:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:248:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:517:"language_details_enfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:252:"enenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;s:252:"arenfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeedfeed";N;}s:21:"sliderss_per_language";a:3:{s:3:"all";i:4;s:2:"ar";s:1:"2";s:2:"en";s:1:"2";}}', 'yes');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(440, 'wp_installer_settings', '[encoded data, 25916 characters]', 'yes'),
(441, 'wpml_config_index', 'O:8:"stdClass":2:{s:7:"plugins";a:18:{i:0;O:8:"stdClass":5:{s:4:"name";s:38:"WooCommerce Catalog Visibility Options";s:14:"override_local";b:1;s:7:"updated";i:1408625614;s:4:"path";s:66:"wpml-config/woocommerce-catalog-visibility-options/wpml-config.xml";s:4:"hash";s:32:"d10bd6388a88521e488f7e4ba295c94c";}i:1;O:8:"stdClass":5:{s:4:"name";s:27:"WooCommerce Paymill Gateway";s:14:"override_local";b:1;s:7:"updated";i:1408626572;s:4:"path";s:55:"wpml-config/woocommerce-paymill-gateway/wpml-config.xml";s:4:"hash";s:32:"46409842584ff8df43a2aa922ad1d388";}i:2;O:8:"stdClass":5:{s:4:"name";s:26:"WooCommerce Stripe Gateway";s:14:"override_local";b:1;s:7:"updated";i:1409061503;s:4:"path";s:54:"wpml-config/woocommerce-stripe-gateway/wpml-config.xml";s:4:"hash";s:32:"4139e23bcdd0bb3e78cb079fa851ce85";}i:3;O:8:"stdClass":5:{s:4:"name";s:27:"WooCommerce Product Add-ons";s:14:"override_local";b:1;s:7:"updated";i:1409062371;s:4:"path";s:55:"wpml-config/woocommerce-product-add-ons/wpml-config.xml";s:4:"hash";s:32:"75320b24a703c55370175379c2faf22d";}i:4;O:8:"stdClass":5:{s:4:"name";s:20:"WooCommerce PostePay";s:14:"override_local";b:1;s:7:"updated";i:1409063136;s:4:"path";s:48:"wpml-config/woocommerce-postepay/wpml-config.xml";s:4:"hash";s:32:"b08722979a25b15ba4a02a16fb555ccc";}i:5;O:8:"stdClass":5:{s:4:"name";s:6:"Sensei";s:14:"override_local";b:1;s:7:"updated";i:1409063311;s:4:"path";s:34:"wpml-config/sensei/wpml-config.xml";s:4:"hash";s:32:"21fda51a99579915e92c6b22ae073a81";}i:6;O:8:"stdClass":5:{s:4:"name";s:25:"NW ADCart for WooCommerce";s:14:"override_local";b:1;s:7:"updated";i:1409734281;s:4:"path";s:53:"wpml-config/nw-adcart-for-woocommerce/wpml-config.xml";s:4:"hash";s:32:"91d62df0659fc7b561a3932a7a52de6a";}i:7;O:8:"stdClass":5:{s:4:"name";s:35:"Product Enquiry Pro for WooCommerce";s:14:"override_local";b:1;s:7:"updated";i:1409734531;s:4:"path";s:63:"wpml-config/product-enquiry-pro-for-woocommerce/wpml-config.xml";s:4:"hash";s:32:"305232f06370d52a29c346d6b711f50a";}i:8;O:8:"stdClass":5:{s:4:"name";s:17:"WooCommerce Plivo";s:14:"override_local";b:1;s:7:"updated";i:1409734705;s:4:"path";s:45:"wpml-config/woocommerce-plivo/wpml-config.xml";s:4:"hash";s:32:"539d172825c4714d69b8a42ad1826c5d";}i:9;O:8:"stdClass":5:{s:4:"name";s:24:"WooCommerce Embed Slides";s:14:"override_local";b:1;s:7:"updated";i:1409813892;s:4:"path";s:52:"wpml-config/woocommerce-embed-slides/wpml-config.xml";s:4:"hash";s:32:"f92b0578c4950e1d7ced60bbdba7ed5b";}i:10;O:8:"stdClass":5:{s:4:"name";s:22:"PayPal for WooCommerce";s:14:"override_local";b:1;s:7:"updated";i:1412841483;s:4:"path";s:54:"wpml-config/paypal-for-woocommerce/wpml-config (1).xml";s:4:"hash";s:32:"4ec8cff3c1bd61950873206196a29348";}i:11;O:8:"stdClass":5:{s:4:"name";s:27:"WooCommerce Product Bundles";s:14:"override_local";b:1;s:7:"updated";i:1414747440;s:4:"path";s:55:"wpml-config/woocommerce-product-bundles/wpml-config.xml";s:4:"hash";s:32:"81eae0e4985a54c08a2486cbc0cba690";}i:12;O:8:"stdClass":5:{s:4:"name";s:28:"WooCommerce Price by Country";s:14:"override_local";b:1;s:7:"updated";i:1415282919;s:4:"path";s:56:"wpml-config/woocommerce-price-by-country/wpml-config.xml";s:4:"hash";s:32:"9b296d64ba8afee80cb1ff4fac80144b";}i:13;O:8:"stdClass":5:{s:4:"name";s:21:"WooCommerce Video Tab";s:14:"override_local";b:1;s:7:"updated";i:1415284344;s:4:"path";s:49:"wpml-config/woocommerce-video-tab/wpml-config.xml";s:4:"hash";s:32:"7f9769bc2769e07ae730f3b4cd307741";}i:14;O:8:"stdClass":5:{s:4:"name";s:24:"WooCommerce Multilingual";s:14:"override_local";b:1;s:7:"updated";i:1426674188;s:4:"path";s:52:"wpml-config/woocommerce-multilingual/wpml-config.xml";s:4:"hash";s:32:"03dd5a10ac5d2ff7b7c576c4449cf7dc";}i:15;O:8:"stdClass":7:{s:4:"name";s:16:"WPML Test Config";s:14:"override_local";b:1;s:7:"updated";i:1429773131;s:4:"path";s:44:"wpml-config/wpml-test-config/wpml-config.xml";s:4:"hash";s:32:"9c3bb313d5a4f028bebfa8fc8af990a3";s:4:"user";s:5:"admin";s:7:"details";s:3:"222";}i:16;O:8:"stdClass":5:{s:4:"name";s:29:"WooCommerce Product Gift Wrap";s:14:"override_local";b:1;s:7:"updated";i:1429640013;s:4:"path";s:57:"wpml-config/woocommerce-product-gift-wrap/wpml-config.xml";s:4:"hash";s:32:"dd3371d64d2ee01e6e42fd7e0bd134cf";}i:17;O:8:"stdClass":5:{s:4:"name";s:13:"WordPress SEO";s:14:"override_local";b:1;s:7:"updated";i:1431680052;s:4:"path";s:41:"wpml-config/wordpress-seo/wpml-config.xml";s:4:"hash";s:32:"1c88f7e261a6926f86ba6c8065891cf4";}}s:6:"themes";a:6:{i:0;O:8:"stdClass":5:{s:4:"name";s:6:"Canvas";s:14:"override_local";b:1;s:7:"updated";i:1425652093;s:4:"path";s:34:"wpml-config/canvas/wpml-config.xml";s:4:"hash";s:32:"9e8668255d8dd56105b67540358bae56";}i:1;O:8:"stdClass":5:{s:4:"name";s:4:"Kleo";s:14:"override_local";b:0;s:7:"updated";i:1425651882;s:4:"path";s:32:"wpml-config/kleo/wpml-config.xml";s:4:"hash";s:32:"442023138b716c2f410690eabeeab185";}i:2;O:8:"stdClass":5:{s:4:"name";s:4:"Port";s:14:"override_local";b:1;s:7:"updated";i:1426496203;s:4:"path";s:32:"wpml-config/port/wpml-config.xml";s:4:"hash";s:32:"788cce209545b94cfede660d543d7013";}i:3;O:8:"stdClass":5:{s:4:"name";s:36:"IDStore - Responsive WordPress Theme";s:14:"override_local";b:1;s:7:"updated";i:1427452920;s:4:"path";s:62:"wpml-config/idstore-responsive-wordpress-theme/wpml-config.xml";s:4:"hash";s:32:"c4ab5787cebb38c0358286626710ab37";}i:4;O:8:"stdClass":5:{s:4:"name";s:4:"Divi";s:14:"override_local";b:1;s:7:"updated";i:1430146146;s:4:"path";s:32:"wpml-config/divi/wpml-config.xml";s:4:"hash";s:32:"df3ab45b0372192108394aad7af044b4";}i:5;O:8:"stdClass":5:{s:4:"name";s:5:"Avada";s:14:"override_local";b:1;s:7:"updated";i:1430299590;s:4:"path";s:33:"wpml-config/avada/wpml-config.xml";s:4:"hash";s:32:"0dfb750d08596266d9dfda556c1bb1e1";}}}', 'yes'),
(442, 'wpml_config_index_updated', '1432510708', 'yes'),
(443, 'wpml_config_files_arr', 'O:8:"stdClass":2:{s:6:"themes";a:0:{}s:7:"plugins";a:0:{}}', 'yes'),
(444, 'icl_admin_messages', 'a:2:{s:8:"messages";a:0:{}s:16:"instant_messages";a:0:{}}', 'yes'),
(446, '_transient_90ab5827af4164115fe869d777800bc0', 'en', 'yes'),
(451, '_wpml_media', 'a:3:{s:7:"version";s:5:"2.1.8";s:13:"starting_help";i:1;s:20:"new_content_settings";a:3:{s:22:"always_translate_media";b:1;s:15:"duplicate_media";b:1;s:18:"duplicate_featured";b:1;}}', 'yes'),
(489, '_site_transient_timeout_browser_a344c581ee2eff9c9c4fcdf9997f17a9', '1432150584', 'yes'),
(490, '_site_transient_browser_a344c581ee2eff9c9c4fcdf9997f17a9', 'a:9:{s:8:"platform";s:7:"Windows";s:4:"name";s:6:"Chrome";s:7:"version";s:13:"42.0.2311.135";s:10:"update_url";s:28:"http://www.google.com/chrome";s:7:"img_src";s:49:"http://s.wordpress.org/images/browsers/chrome.png";s:11:"img_src_ssl";s:48:"https://wordpress.org/images/browsers/chrome.png";s:15:"current_version";s:2:"18";s:7:"upgrade";b:0;s:8:"insecure";b:0;}', 'yes'),
(493, 'nav_menu_options', 'a:2:{i:0;b:0;s:8:"auto_add";a:0:{}}', 'yes'),
(512, 'wp_icl_translators_cached', 'a:1:{i:0;O:8:"stdClass":1:{s:2:"ID";s:1:"1";}}', 'yes'),
(517, '_transient_timeout_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1431627313', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(518, '_transient_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:26:"https://wordpress.org/news";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 08 May 2015 10:20:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"en-US";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:39:"http://wordpress.org/?v=4.3-alpha-32500";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:10:{i:0;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:48:"WordPress 4.2.2 Security and Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/news/2015/05/wordpress-4-2-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:60:"https://wordpress.org/news/2015/05/wordpress-4-2-2/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 May 2015 02:24:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3718";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:355:"WordPress 4.2.2 is now available. This is a critical security release for all previous versions and we strongly encourage you to update your sites immediately. Version 4.2.2 addresses two security issues: The Genericons icon font package, which is used in a number of popular themes and plugins, contained an HTML file vulnerable to a cross-site [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Samuel Sidler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3194:"<p>WordPress 4.2.2 is now available. This is a <strong>critical security release</strong> for all previous versions and we strongly encourage you to update your sites immediately.</p>\n<p>Version 4.2.2 addresses two security issues:</p>\n<ul>\n<li>The Genericons icon font package, which is used in a number of popular themes and plugins, contained an HTML file vulnerable to a cross-site scripting attack. All affected themes and plugins hosted on <a href="https://wordpress.org/">WordPress.org</a> (including the Twenty Fifteen default theme) have been updated today by the WordPress security team to address this issue by removing this nonessential file. To help protect other Genericons usage, WordPress 4.2.2 proactively scans the wp-content directory for this HTML file and removes it. Reported by Robert Abela of <a href="http://netsparker.com">Netsparker</a>.</li>\n<li>WordPress versions 4.2 and earlier are affected by a <a href="https://wordpress.org/news/2015/04/wordpress-4-2-1/">critical cross-site scripting vulnerability</a>, which could enable anonymous users to compromise a site. WordPress 4.2.2 includes a comprehensive fix for this issue. Reported separately by Rice Adu and Tong Shi.</li>\n</ul>\n<p>The release also includes hardening for a potential cross-site scripting vulnerability when using the visual editor. This issue was reported by Mahadev Subedi.</p>\n<p>Our thanks to those who have practiced <a href="https://make.wordpress.org/core/handbook/reporting-security-vulnerabilities/">responsible disclosure</a> of security issues.</p>\n<p>WordPress 4.2.2 also contains fixes for 13 bugs from 4.2. For more information, see the <a href="https://codex.wordpress.org/Version_4.2.2">release notes</a> or consult the <a href="https://core.trac.wordpress.org/log/branches/4.2?rev=32418&amp;stop_rev=32324">list of changes</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.2.2</a> or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.2.2.</p>\n<p>Thanks to everyone who contributed to 4.2.2:</p>\n<p><a href="https://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="https://profiles.wordpress.org/boonebgorges">Boone Gorges</a>, <a href="https://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="https://profiles.wordpress.org/iseulde">Ella Iseulde Van Dorpe</a>, <a href="https://profiles.wordpress.org/pento">Gary Pendergast</a>, <a href="https://profiles.wordpress.org/hnle">Hinaloe</a>, <a href="https://profiles.wordpress.org/jeremyfelt">Jeremy Felt</a>, <a href="https://profiles.wordpress.org/johnjamesjacoby">John James Jacoby</a>, <a href="https://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="https://profiles.wordpress.org/mdawaffe">Mike Adams</a>, <a href="https://profiles.wordpress.org/nbachiyski">Nikolay Bachiyski</a>, <a href="https://profiles.wordpress.org/taka2">taka2</a>, and <a href="https://profiles.wordpress.org/willstedt">willstedt</a>.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2015/05/wordpress-4-2-2/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:32:"WordPress 4.2.1 Security Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/news/2015/04/wordpress-4-2-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:60:"https://wordpress.org/news/2015/04/wordpress-4-2-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 27 Apr 2015 18:34:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3706";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:366:"WordPress 4.2.1 is now available. This is a critical security release for all previous versions and we strongly encourage you to update your sites immediately. A few hours ago, the WordPress team was made aware of a cross-site scripting vulnerability, which could enable commenters to compromise a site. The vulnerability was discovered by Jouko Pynnönen. [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Gary Pendergast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1010:"<p>WordPress 4.2.1 is now available. This is a <strong>critical security release</strong> for all previous versions and we strongly encourage you to update your sites immediately.</p>\n<p>A few hours ago, the WordPress team was made aware of a cross-site scripting vulnerability, which could enable commenters to compromise a site. The vulnerability was discovered by <a href="http://klikki.fi/">Jouko Pynnönen</a>.</p>\n<p>WordPress 4.2.1 has begun to roll out as an automatic background update, for sites that <a href="https://wordpress.org/plugins/background-update-tester/">support</a> those.</p>\n<p>For more information, see the <a href="https://codex.wordpress.org/Version_4.2.1">release notes</a> or consult the <a href="https://core.trac.wordpress.org/log/branches/4.2?rev=32311&amp;stop_rev=32300">list of changes</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.2.1</a> or venture over to <strong>Dashboard → Updates</strong> and simply click &#8220;Update Now&#8221;.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2015/04/wordpress-4-2-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:45:"\n		\n		\n		\n		\n		\n				\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:26:"WordPress 4.2 “Powell”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"https://wordpress.org/news/2015/04/powell/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/news/2015/04/powell/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 23 Apr 2015 18:35:29 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3642";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:343:"Version 4.2 of WordPress, named &#8220;Powell&#8221; in honor of jazz pianist Bud Powell, is available for download or update in your WordPress dashboard. New features in 4.2 help you communicate and share, globally. An easier way to share content Clip it, edit it, publish it. Get familiar with the new and improved Press This. From [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:29434:"<p>Version 4.2 of WordPress, named &#8220;Powell&#8221; in honor of jazz pianist <a href="https://en.wikipedia.org/wiki/Bud_Powell">Bud Powell</a>, is available for <a href="https://wordpress.org/download/">download</a> or update in your WordPress dashboard. New features in 4.2 help you communicate and share, globally.</p>\n<div id="v-e9kH4FzP-1" class="video-player"><embed id="v-e9kH4FzP-1-video" src="https://v0.wordpress.com/player.swf?v=1.04&amp;guid=e9kH4FzP&amp;isDynamicSeeking=true" type="application/x-shockwave-flash" width="692" height="388" title="Introducing WordPress 4.2 &quot;Powell&quot;" wmode="direct" seamlesstabbing="true" allowfullscreen="true" allowscriptaccess="always" overstretch="true"></embed></div>\n<hr />\n<h2 style="text-align: center">An easier way to share content</h2>\n<p><img class="alignnone size-full wp-image-3677" src="https://wordpress.org/news/files/2015/04/4.2-press-this-2.jpg" alt="Press This" width="1000" height="832" />Clip it, edit it, publish it. Get familiar with the new and improved Press This. From the Tools menu, add Press This to your browser bookmark bar or your mobile device home screen. Once installed you can share your content with lightning speed. Sharing your favorite videos, images, and content has never been this fast or this easy.</p>\n<hr />\n<h2 style="text-align: center">Extended character support</h2>\n<p><img class="alignnone size-full wp-image-3676" src="https://wordpress.org/news/files/2015/04/4.2-characters.png" alt="Character support for emoji, special characters" width="1000" height="832" />Writing in WordPress, whatever your language, just got better. WordPress 4.2 supports a host of new characters out-of-the-box, including native Chinese, Japanese, and Korean characters, musical and mathematical symbols, and hieroglyphs.</p>\n<p>Don’t use any of those characters? You can still have fun — emoji are now available in WordPress! Get creative and decorate your content with <img src="https://s.w.org/images/core/emoji/72x72/1f499.png" alt="????" class="wp-smiley" style="height: 1em; max-height: 1em;" />, <img src="https://s.w.org/images/core/emoji/72x72/1f438.png" alt="????" class="wp-smiley" style="height: 1em; max-height: 1em;" />, <img src="https://s.w.org/images/core/emoji/72x72/1f412.png" alt="????" class="wp-smiley" style="height: 1em; max-height: 1em;" />, <img src="https://s.w.org/images/core/emoji/72x72/1f355.png" alt="????" class="wp-smiley" style="height: 1em; max-height: 1em;" />, and all the many other <a href="https://codex.wordpress.org/Emoji">emoji</a>.</p>\n<hr />\n<div><img class="alignright size-medium wp-image-3656" src="https://wordpress.org/news/files/2015/04/4.2-theme-switcher-300x230.png" alt="Customizer theme switcher" width="288" height="221" /></p>\n<h3>Switch themes in the Customizer</h3>\n<p>Browse and preview your installed themes from the Customizer. Make sure the theme looks great with your content, before it debuts on your site.</p>\n</div>\n<div style="clear: both"></div>\n<div><img class="alignright size-medium wp-image-3653" src="https://wordpress.org/news/files/2015/04/4.2-embeds-300x230.png" alt="Tumbr.com oEmbed example" width="288" height="221" /></p>\n<h3>Even more embeds</h3>\n<p>Paste links from Tumblr.com and Kickstarter and watch them magically appear right in the editor. With every release, your publishing and editing experience get closer together.</p>\n</div>\n<div style="clear: both"></div>\n<div>\n<p><img class="alignright size-medium wp-image-3654" src="https://wordpress.org/news/files/2015/04/4.2-plugins-300x230.png" alt="Inline plugin updates" width="288" height="221" /></p>\n<h3>Streamlined plugin updates</h3>\n<p>Goodbye boring loading screen, hello smooth and simple plugin updates. Click <em>Update Now</em> and watch the magic happen.</p>\n</div>\n<div style="clear: both"></div>\n<hr />\n<h2 style="text-align: center">Under the Hood</h2>\n<h5>utf8mb4 support</h5>\n<p>Database character encoding has changed from utf8 to utf8mb4, which adds support for a whole range of new 4-byte characters.</p>\n<h5>JavaScript accessibility</h5>\n<p>You can now send audible notifications to screen readers in JavaScript with <code>wp.a11y.speak()</code>. Pass it a string, and an update will be sent to a dedicated ARIA live notifications area.</p>\n<h5>Shared term splitting</h5>\n<p>Terms shared across multiple taxonomies will be split when one of them is updated. Find out more in the <a href="https://developer.wordpress.org/plugins/taxonomy/working-with-split-terms-in-wp-4-2/">Plugin Developer Handbook</a>.</p>\n<h5>Complex query ordering</h5>\n<p><code>WP_Query</code>, <code>WP_Comment_Query</code>, and <code>WP_User_Query</code> now support complex ordering with named meta query clauses.</p>\n<hr />\n<h2 style="text-align: center">The Team</h2>\n<p><a class="alignleft" href="https://profiles.wordpress.org/drewapicture"><img src="https://www.gravatar.com/avatar/95c934fa2c3362794bf62ff8c59ada08?d=mm&amp;s=150&amp;r=G" alt="Drew Jaynes" width="90" height="90" /></a>This release was led by <a href="http://werdswords.com">Drew Jaynes</a>, with the help of these fine individuals. There are 283 contributors with props in this release, a new high. Pull up some Bud Powell on your music service of choice, and check out some of their profiles:</p>\n<a href="https://profiles.wordpress.org/mercime">@mercime</a>, <a href="https://profiles.wordpress.org/a5hleyrich">A5hleyRich</a>, <a href="https://profiles.wordpress.org/aaroncampbell">Aaron D. Campbell</a>, <a href="https://profiles.wordpress.org/jorbin">Aaron Jorbin</a>, <a href="https://profiles.wordpress.org/abhishekfdd">abhishekfdd</a>, <a href="https://profiles.wordpress.org/adamsilverstein">Adam Silverstein</a>, <a href="https://profiles.wordpress.org/mrahmadawais">Ahmad Awais</a>, <a href="https://profiles.wordpress.org/alexkingorg">Alex King</a>, <a href="https://profiles.wordpress.org/viper007bond">Alex Mills (Viper007Bond)</a>, <a href="https://profiles.wordpress.org/deconf">Alin Marcu</a>, <a href="https://profiles.wordpress.org/collinsinternet">Allan Collins</a>, <a href="https://profiles.wordpress.org/afercia">Andrea Fercia</a>, <a href="https://profiles.wordpress.org/awbauer">Andrew Bauer</a>, <a href="https://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="https://profiles.wordpress.org/norcross">Andrew Norcross</a>, <a href="https://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/ankitgadertcampcom">Ankit Gade</a>, <a href="https://profiles.wordpress.org/ankit-k-gupta">Ankit K Gupta</a>, <a href="https://profiles.wordpress.org/atimmer">Anton Timmermans</a>, <a href="https://profiles.wordpress.org/aramzs">Aram Zucker-Scharff</a>, <a href="https://profiles.wordpress.org/arminbraun">ArminBraun</a>, <a href="https://profiles.wordpress.org/ashfame">Ashfame</a>, <a href="https://profiles.wordpress.org/filosofo">Austin Matzko</a>, <a href="https://profiles.wordpress.org/avryl">avryl</a>, <a href="https://profiles.wordpress.org/barrykooij">Barry Kooij</a>, <a href="https://profiles.wordpress.org/beaulebens">Beau Lebens</a>, <a href="https://profiles.wordpress.org/bendoh">Ben Doherty (Oomph, Inc)</a>, <a href="https://profiles.wordpress.org/bananastalktome">Billy Schneider</a>, <a href="https://profiles.wordpress.org/boonebgorges">Boone B. Gorges</a>, <a href="https://profiles.wordpress.org/kraftbj">Brandon Kraft</a>, <a href="https://profiles.wordpress.org/krogsgard">Brian Krogsgard</a>, <a href="https://profiles.wordpress.org/bswatson">Brian Watson</a>, <a href="https://profiles.wordpress.org/calevans">CalEvans</a>, <a href="https://profiles.wordpress.org/carolinegeven">carolinegeven</a>, <a href="https://profiles.wordpress.org/caseypatrickdriscoll">Casey Driscoll</a>, <a href="https://profiles.wordpress.org/caspie">Caspie</a>, <a href="https://profiles.wordpress.org/cdog">Catalin Dogaru</a>, <a href="https://profiles.wordpress.org/chipbennett">Chip Bennett</a>, <a href="https://profiles.wordpress.org/chipx86">chipx86</a>, <a href="https://profiles.wordpress.org/chrico">ChriCo</a>, <a href="https://profiles.wordpress.org/cbaldelomar">Chris Baldelomar</a>, <a href="https://profiles.wordpress.org/c3mdigital">Chris Olbekson</a>, <a href="https://profiles.wordpress.org/cfoellmann">Christian Foellmann</a>, <a href="https://profiles.wordpress.org/cfinke">Christopher Finke</a>, <a href="https://profiles.wordpress.org/clifgriffin">Clifton Griffin</a>, <a href="https://profiles.wordpress.org/codix">Code Master</a>, <a href="https://profiles.wordpress.org/corphi">Corphi</a>, <a href="https://profiles.wordpress.org/couturefreak">Courtney Ivey</a>, <a href="https://profiles.wordpress.org/craig-ralston">Craig Ralston</a>, <a href="https://profiles.wordpress.org/cweiske">cweiske</a>, <a href="https://profiles.wordpress.org/extendwings">Daisuke Takahashi</a>, <a href="https://profiles.wordpress.org/timersys">Damian</a>, <a href="https://profiles.wordpress.org/danielbachhuber">Daniel Bachhuber</a>, <a href="https://profiles.wordpress.org/redsweater">Daniel Jalkut (Red Sweater)</a>, <a href="https://profiles.wordpress.org/dkotter">Darin Kotter</a>, <a href="https://profiles.wordpress.org/nerrad">Darren Ethier (nerrad)</a>, <a href="https://profiles.wordpress.org/dllh">Daryl L. L. Houston (dllh)</a>, <a href="https://profiles.wordpress.org/dmchale">Dave McHale</a>, <a href="https://profiles.wordpress.org/davidakennedy">David A. Kennedy</a>, <a href="https://profiles.wordpress.org/davidanderson">David Anderson</a>, <a href="https://profiles.wordpress.org/dlh">David Herrera</a>, <a href="https://profiles.wordpress.org/folletto">Davide ''Folletto'' Casali</a>, <a href="https://profiles.wordpress.org/davideugenepratt">davideugenepratt</a>, <a href="https://profiles.wordpress.org/davidhamiltron">davidhamiltron</a>, <a href="https://profiles.wordpress.org/denis-de-bernardy">Denis de Bernardy</a>, <a href="https://profiles.wordpress.org/valendesigns">Derek Herman</a>, <a href="https://profiles.wordpress.org/dsmart">Derek Smart</a>, <a href="https://profiles.wordpress.org/designsimply">designsimply</a>, <a href="https://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="https://profiles.wordpress.org/dipeshkakadiya">dipesh.kakadiya</a>, <a href="https://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="https://profiles.wordpress.org/doublesharp">doublesharp</a>, <a href="https://profiles.wordpress.org/dzerycz">DzeryCZ</a>, <a href="https://profiles.wordpress.org/kucrut">Dzikri Aziz</a>, <a href="https://profiles.wordpress.org/emazovetskiy">e.mazovetskiy</a>, <a href="https://profiles.wordpress.org/oso96_2000">Eduardo Reveles</a>, <a href="https://profiles.wordpress.org/cais">Edward Caissie</a>, <a href="https://profiles.wordpress.org/eliorivero">Elio Rivero</a>, <a href="https://profiles.wordpress.org/iseulde">Ella Iseulde Van Dorpe</a>, <a href="https://profiles.wordpress.org/elliottcarlson">elliottcarlson</a>, <a href="https://profiles.wordpress.org/enej">enej</a>, <a href="https://profiles.wordpress.org/ericlewis">Eric Andrew Lewis</a>, <a href="https://profiles.wordpress.org/ebinnion">Eric Binnion</a>, <a href="https://profiles.wordpress.org/ethitter">Erick Hitter</a>, <a href="https://profiles.wordpress.org/evansolomon">Evan Solomon</a>, <a href="https://profiles.wordpress.org/fab1en">Fabien Quatravaux</a>, <a href="https://profiles.wordpress.org/fhwebcs">fhwebcs</a>, <a href="https://profiles.wordpress.org/floriansimeth">Florian Simeth</a>, <a href="https://profiles.wordpress.org/bueltge">Frank Bueltge</a>, <a href="https://profiles.wordpress.org/frankpw">Frank P. Walentynowicz</a>, <a href="https://profiles.wordpress.org/f-j-kaiser">Franz Josef Kaiser</a>, <a href="https://profiles.wordpress.org/garyc40">Gary Cao</a>, <a href="https://profiles.wordpress.org/garyj">Gary Jones</a>, <a href="https://profiles.wordpress.org/pento">Gary Pendergast</a>, <a href="https://profiles.wordpress.org/geertdd">Geert De Deckere</a>, <a href="https://profiles.wordpress.org/genkisan">genkisan</a>, <a href="https://profiles.wordpress.org/georgestephanis">George Stephanis</a>, <a href="https://profiles.wordpress.org/grahamarmfield">Graham Armfield</a>, <a href="https://profiles.wordpress.org/webord">Gustavo Bordoni</a>, <a href="https://profiles.wordpress.org/hakre">hakre</a>, <a href="https://profiles.wordpress.org/harishchaudhari">Harish Chaudhari</a>, <a href="https://profiles.wordpress.org/hauvong">hauvong</a>, <a href="https://profiles.wordpress.org/helen">Helen Hou-Sandí</a>, <a href="https://profiles.wordpress.org/herbmillerjr">herbmillerjr</a>, <a href="https://profiles.wordpress.org/hew">Hew</a>, <a href="https://profiles.wordpress.org/hnle">Hinaloe</a>, <a href="https://profiles.wordpress.org/horike">horike</a>, <a href="https://profiles.wordpress.org/hlashbrooke">Hugh Lashbrooke</a>, <a href="https://profiles.wordpress.org/hugobaeta">Hugo Baeta</a>, <a href="https://profiles.wordpress.org/iandunn">Ian Dunn</a>, <a href="https://profiles.wordpress.org/ianmjones">ianmjones</a>, <a href="https://profiles.wordpress.org/idealien">idealien</a>, <a href="https://profiles.wordpress.org/imath">imath</a>, <a href="https://profiles.wordpress.org/ipstenu">Ipstenu (Mika Epstein)</a>, <a href="https://profiles.wordpress.org/jdgrimes">J.D. Grimes</a>, <a href="https://profiles.wordpress.org/jacklenox">Jack Lenox</a>, <a href="https://profiles.wordpress.org/jamescollins">James Collins</a>, <a href="https://profiles.wordpress.org/janhenckens">janhenckens</a>, <a href="https://profiles.wordpress.org/jfarthing84">Jeff Farthing</a>, <a href="https://profiles.wordpress.org/cheffheid">Jeffrey de Wit</a>, <a href="https://profiles.wordpress.org/jeremyfelt">Jeremy Felt</a>, <a href="https://profiles.wordpress.org/jesin">Jesin A</a>, <a href="https://profiles.wordpress.org/jipmoors">jipmoors</a>, <a href="https://profiles.wordpress.org/jartes">Joan Artes</a>, <a href="https://profiles.wordpress.org/joedolson">Joe Dolson</a>, <a href="https://profiles.wordpress.org/joemcgill">Joe McGill</a>, <a href="https://profiles.wordpress.org/yo-l1982">Joel Bernerman</a>, <a href="https://profiles.wordpress.org/joen">Joen Asmussen</a>, <a href="https://profiles.wordpress.org/johnbillion">John Blackbourn</a>, <a href="https://profiles.wordpress.org/johneckman">John Eckman</a>, <a href="https://profiles.wordpress.org/johnjamesjacoby">John James Jacoby</a>, <a href="https://profiles.wordpress.org/jlevandowski">John Levandowski</a>, <a href="https://profiles.wordpress.org/desrosj">Jonathan Desrosiers</a>, <a href="https://profiles.wordpress.org/joostdekeijzer">joost de keijzer</a>, <a href="https://profiles.wordpress.org/joostdevalk">Joost de Valk</a>, <a href="https://profiles.wordpress.org/jcastaneda">Jose Castaneda</a>, <a href="https://profiles.wordpress.org/joshlevinson">Josh Levinson</a>, <a href="https://profiles.wordpress.org/jphase">jphase</a>, <a href="https://profiles.wordpress.org/juliobox">Julio Potier</a>, <a href="https://profiles.wordpress.org/kopepasah">Justin Kopepasah</a>, <a href="https://profiles.wordpress.org/jtsternberg">Justin Sternberg</a>, <a href="https://profiles.wordpress.org/justincwatt">Justin Watt</a>, <a href="https://profiles.wordpress.org/kadamwhite">K.Adam White</a>, <a href="https://profiles.wordpress.org/trepmal">Kailey (trepmal)</a>, <a href="https://profiles.wordpress.org/ryelle">Kelly Dwan</a>, <a href="https://profiles.wordpress.org/kevdotbadger">Kevin Ruscoe</a>, <a href="https://profiles.wordpress.org/kpdesign">Kim Parsell</a>, <a href="https://profiles.wordpress.org/ixkaito">Kite</a>, <a href="https://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="https://profiles.wordpress.org/obenland">Konstantin Obenland</a>, <a href="https://profiles.wordpress.org/lancewillett">Lance Willett</a>, <a href="https://profiles.wordpress.org/mindrun">Leonard</a>, <a href="https://profiles.wordpress.org/leopeo">Leonardo Giacone</a>, <a href="https://profiles.wordpress.org/lgladdy">Liam Gladdy</a>, <a href="https://profiles.wordpress.org/maimairel">maimairel</a>, <a href="https://profiles.wordpress.org/mako09">Mako</a>, <a href="https://profiles.wordpress.org/funkatronic">Manny Fleurmond</a>, <a href="https://profiles.wordpress.org/marcelomazza">marcelomazza</a>, <a href="https://profiles.wordpress.org/marcochiesi">Marco Chiesi</a>, <a href="https://profiles.wordpress.org/mkaz">Marcus Kazmierczak</a>, <a href="https://profiles.wordpress.org/tyxla">Marin Atanasov</a>, <a href="https://profiles.wordpress.org/nofearinc">Mario Peshev</a>, <a href="https://profiles.wordpress.org/clorith">Marius (Clorith)</a>, <a href="https://profiles.wordpress.org/markjaquith">Mark Jaquith</a>, <a href="https://profiles.wordpress.org/senff">Mark Senff</a>, <a href="https://profiles.wordpress.org/markoheijnen">Marko Heijnen</a>, <a href="https://profiles.wordpress.org/mgibbs189">Matt Gibbs</a>, <a href="https://profiles.wordpress.org/sivel">Matt Martz</a>, <a href="https://profiles.wordpress.org/matt">Matt Mullenweg</a>, <a href="https://profiles.wordpress.org/mattwiebe">Matt Wiebe</a>, <a href="https://profiles.wordpress.org/mzak">Matt Zak</a>, <a href="https://profiles.wordpress.org/mboynes">Matthew Boynes</a>, <a href="https://profiles.wordpress.org/mattheweppelsheimer">Matthew Eppelsheimer</a>, <a href="https://profiles.wordpress.org/mattheu">Matthew Haines-Young</a>, <a href="https://profiles.wordpress.org/mattyrob">mattyrob</a>, <a href="https://profiles.wordpress.org/maxcutler">Max Cutler</a>, <a href="https://profiles.wordpress.org/mehulkaklotar">mehulkaklotar</a>, <a href="https://profiles.wordpress.org/melchoyce">Mel Choyce</a>, <a href="https://profiles.wordpress.org/meloniq">meloniq</a>, <a href="https://profiles.wordpress.org/mdawaffe">Michael Adams (mdawaffe)</a>, <a href="https://profiles.wordpress.org/michael-arestad">Michael Arestad</a>, <a href="https://profiles.wordpress.org/tw2113">Michael Beckwith</a>, <a href="https://profiles.wordpress.org/michalzuber">michalzuber</a>, <a href="https://profiles.wordpress.org/mdgl">Mike Glendinning</a>, <a href="https://profiles.wordpress.org/mikehansenme">Mike Hansen</a>, <a href="https://profiles.wordpress.org/thaicloud">Mike Jordan</a>, <a href="https://profiles.wordpress.org/mikeschinkel">Mike Schinkel</a>, <a href="https://profiles.wordpress.org/mikengarrett">MikeNGarrett</a>, <a href="https://profiles.wordpress.org/dimadin">Milan Dinic</a>, <a href="https://profiles.wordpress.org/mmn-o">mmn-o</a>, <a href="https://profiles.wordpress.org/batmoo">Mohammad Jangda</a>, <a href="https://profiles.wordpress.org/momdad">MomDad</a>, <a href="https://profiles.wordpress.org/morganestes">Morgan Estes</a>, <a href="https://profiles.wordpress.org/morpheu5">Morpheu5</a>, <a href="https://profiles.wordpress.org/Nao">Naoko Takano</a>, <a href="https://profiles.wordpress.org/nathan_dawson">nathan_dawson</a>, <a href="https://profiles.wordpress.org/neil_pie">Neil Pie</a>, <a href="https://profiles.wordpress.org/celloexpressions">Nick Halsey</a>, <a href="https://profiles.wordpress.org/nicnicnicdevos">nicnicnicdevos</a>, <a href="https://profiles.wordpress.org/nikv">Nikhil Vimal</a>, <a href="https://profiles.wordpress.org/ninnypants">ninnypants</a>, <a href="https://profiles.wordpress.org/nitkr">nitkr</a>, <a href="https://profiles.wordpress.org/nunomorgadinho">Nuno Morgadinho</a>, <a href="https://profiles.wordpress.org/originalexe">OriginalEXE</a>, <a href="https://profiles.wordpress.org/pareshradadiya-1">Paresh Radadiya</a>, <a href="https://profiles.wordpress.org/pathawks">Pat Hawks</a>, <a href="https://profiles.wordpress.org/pbearne">Paul Bearne</a>, <a href="https://profiles.wordpress.org/paulschreiber">Paul Schreiber</a>, <a href="https://profiles.wordpress.org/paulwilde">Paul Wilde</a>, <a href="https://profiles.wordpress.org/pavelevap">pavelevap</a>, <a href="https://profiles.wordpress.org/sirbrillig">Payton Swick</a>, <a href="https://profiles.wordpress.org/petemall">Pete Mall</a>, <a href="https://profiles.wordpress.org/gungeekatx">Pete Nelson</a>, <a href="https://profiles.wordpress.org/peterwilsoncc">Peter Wilson</a>, <a href="https://profiles.wordpress.org/mordauk">Pippin Williamson</a>, <a href="https://profiles.wordpress.org/podpirate">podpirate</a>, <a href="https://profiles.wordpress.org/postpostmodern">postpostmodern</a>, <a href="https://profiles.wordpress.org/nprasath002">Prasath Nadarajah</a>, <a href="https://profiles.wordpress.org/prasoon2211">prasoon2211</a>, <a href="https://profiles.wordpress.org/cyman">Primoz Cigler</a>, <a href="https://profiles.wordpress.org/r-a-y">r-a-y</a>, <a href="https://profiles.wordpress.org/rachelbaker">Rachel Baker</a>, <a href="https://profiles.wordpress.org/rahulbhangale">rahulbhangale</a>, <a href="https://profiles.wordpress.org/ramiy">Rami Yushuvaev</a>, <a href="https://profiles.wordpress.org/lamosty">Rastislav Lamos</a>, <a href="https://profiles.wordpress.org/ravindra-pal-singh">Ravindra Pal Singh</a>, <a href="https://profiles.wordpress.org/rianrietveld">Rian Rietveld</a>, <a href="https://profiles.wordpress.org/ritteshpatel">Ritesh Patel</a>, <a href="https://profiles.wordpress.org/miqrogroove">Robert Chapin</a>, <a href="https://profiles.wordpress.org/rodrigosprimo">Rodrigo Primo</a>, <a href="https://profiles.wordpress.org/magicroundabout">Ross Wintle</a>, <a href="https://profiles.wordpress.org/ryan">Ryan Boren</a>, <a href="https://profiles.wordpress.org/rmarks">Ryan Marks</a>, <a href="https://profiles.wordpress.org/sagarjadhav">sagarjadhav</a>, <a href="https://profiles.wordpress.org/solarissmoke">Samir Shah</a>, <a href="https://profiles.wordpress.org/samo9789">samo9789</a>, <a href="https://profiles.wordpress.org/samuelsidler">Samuel Sidler</a>, <a href="https://profiles.wordpress.org/sgrant">Scott Grant</a>, <a href="https://profiles.wordpress.org/coffee2code">Scott Reilly</a>, <a href="https://profiles.wordpress.org/wonderboymusic">Scott Taylor</a>, <a href="https://profiles.wordpress.org/scottgonzalez">scott.gonzalez</a>, <a href="https://profiles.wordpress.org/greglone">ScreenfeedFr</a>, <a href="https://profiles.wordpress.org/scribu">scribu</a>, <a href="https://profiles.wordpress.org/seanchayes">Sean Hayes</a>, <a href="https://profiles.wordpress.org/sergejmueller">Sergej Muller</a>, <a href="https://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/sevenspark">sevenspark</a>, <a href="https://profiles.wordpress.org/simonwheatley">Simon Wheatley</a>, <a href="https://profiles.wordpress.org/siobhan">Siobhan</a>, <a href="https://profiles.wordpress.org/sippis">sippis</a>, <a href="https://profiles.wordpress.org/slobodanmanic">Slobodan Manic</a>, <a href="https://profiles.wordpress.org/stephdau">Stephane Daury</a>, <a href="https://profiles.wordpress.org/sillybean">Stephanie Leary</a>, <a href="https://profiles.wordpress.org/netweb">Stephen Edgar</a>, <a href="https://profiles.wordpress.org/stevegrunwell">Steve Grunwell</a>, <a href="https://profiles.wordpress.org/stevehickeydesign">stevehickeydesign</a>, <a href="https://profiles.wordpress.org/stevenkword">Steven Word</a>, <a href="https://profiles.wordpress.org/taka2">taka2</a>, <a href="https://profiles.wordpress.org/iamtakashi">Takashi Irie</a>, <a href="https://profiles.wordpress.org/hissy">Takuro Hishikawa</a>, <a href="https://profiles.wordpress.org/themiked">theMikeD</a>, <a href="https://profiles.wordpress.org/thomaswm">thomaswm</a>, <a href="https://profiles.wordpress.org/ipm-frommen">Thorsten Frommen</a>, <a href="https://profiles.wordpress.org/tillkruess">Till</a>, <a href="https://profiles.wordpress.org/timothyblynjacobs">Timothy Jacobs</a>, <a href="https://profiles.wordpress.org/tiqbiz">tiqbiz</a>, <a href="https://profiles.wordpress.org/tmatsuur">tmatsuur</a>, <a href="https://profiles.wordpress.org/tmeister">tmeister</a>, <a href="https://profiles.wordpress.org/tschutter">Tobias Schutter</a>, <a href="https://profiles.wordpress.org/tobiasbg">TobiasBg</a>, <a href="https://profiles.wordpress.org/tomdxw">tomdxw</a>, <a href="https://profiles.wordpress.org/travisnorthcutt">Travis Northcutt</a>, <a href="https://profiles.wordpress.org/trishasalas">trishasalas</a>, <a href="https://profiles.wordpress.org/tywayne">Ty Carlson</a>, <a href="https://profiles.wordpress.org/uamv">UaMV</a>, <a href="https://profiles.wordpress.org/desaiuditd">Udit Desai</a>, <a href="https://profiles.wordpress.org/sorich87">Ulrich Sossou</a>, <a href="https://profiles.wordpress.org/veritaserum">Veritaserum</a>, <a href="https://profiles.wordpress.org/voldemortensen">voldemortensen</a>, <a href="https://profiles.wordpress.org/volodymyrc">VolodymyrC</a>, <a href="https://profiles.wordpress.org/vortfu">vortfu</a>, <a href="https://profiles.wordpress.org/welcher">welcher</a>, <a href="https://profiles.wordpress.org/westonruter">Weston Ruter</a>, <a href="https://profiles.wordpress.org/earnjam">William Earnhardt</a>, <a href="https://profiles.wordpress.org/willstedt">willstedt</a>, and <a href="https://profiles.wordpress.org/wordpressorru">WordPressor</a>.\n<p style="margin-top: 22px">Special thanks go to <a href="http://siobhanmckeown.com/">Siobhan McKeown</a> for producing the release video and <a href="http://camikaos.com/">Cami Kaos</a> for the voice-over.</p>\n<p>Finally, thanks to all of the contributors who provided subtitles for the release video, which at last count had been translated into 30 languages!</p>\n<p><a href="https://profiles.wordpress.org/adrianpop">Adrian Pop</a>, <a href="https://profiles.wordpress.org/deconf">Alin Marcu</a>, <a href="https://profiles.wordpress.org/bagerathan">Bagerathan Sivarajah</a>, <a href="https://profiles.wordpress.org/besnik">Besnik</a>, <a href="https://profiles.wordpress.org/bjornjohansen">Bjørn Johansen</a>, Chantal Coolsma, <a href="https://profiles.wordpress.org/cubells">cubells</a>, Daisuke Takahashi, <a href="https://profiles.wordpress.org/dianakc">Diana K. Cury</a>, <a href="https://profiles.wordpress.org/djzone">DjZoNe</a>, <a href="https://profiles.wordpress.org/dyrer">dyrer</a>, <a href="https://profiles.wordpress.org/semblance">Elzette Roelofse</a>, <a href="https://profiles.wordpress.org/wordpress-tr">Emre Erkan</a>, <a href="https://profiles.wordpress.org/fxbenard">fxbenard</a>, <a href="https://profiles.wordpress.org/tacoverdo">TacoVerdo</a>, <a href="https://profiles.wordpress.org/gabriel-reguly">Gabriel Reguly</a>, <a href="https://profiles.wordpress.org/miss_jwo">Jenny Wong</a>, <a href="https://profiles.wordpress.org/garyj">Gary Jones</a>, <a href="https://profiles.wordpress.org/hgmb">Håvard Grimelid</a>, <a href="https://profiles.wordpress.org/intoxstudio">Joachim Jensen</a>, <a href="https://profiles.wordpress.org/jimmyxu">Jimmy Xu</a>, <a href="https://profiles.wordpress.org/nukaga">Junko Nukaga</a>, <a href="https://profiles.wordpress.org/pokeraitis">Justina</a>, <a href="https://profiles.wordpress.org/kenan3008/">Kenan Dervisevic</a>, <a href="https://profiles.wordpress.org/kosvrouvas">Kostas Vrouvas</a>, <a href="https://profiles.wordpress.org/eclare">Krzysztof Trynkiewicz</a>, <a href="https://profiles.wordpress.org/goblindegook">Luís Rodrigues</a>, <a href="https://profiles.wordpress.org/luisrull">Luis Rull</a>, <a href="https://profiles.wordpress.org/culturemark">Mark Thomas Gazel </a>, <a href="https://profiles.wordpress.org/clorith">Marius Jensen</a>, <a href="https://profiles.wordpress.org/matthee">matthee</a>, <a href="https://profiles.wordpress.org/damst">Mattias Tengblad</a>, Matúš Záhradník, Mayuko Moriyama, <a href="https://profiles.wordpress.org/michalvittek">Michal Vittek</a>, <a href="https://profiles.wordpress.org/dimadin">Milan Dinić</a>, <a href="https://profiles.wordpress.org/mrshemek">MrShemek</a>, <a href="https://profiles.wordpress.org/Nao">Naoko Takano</a>, <a href="https://profiles.wordpress.org/pavelevap">pavelevap</a>, <a href="https://profiles.wordpress.org/peterhoob">Peter Holme Obrestad</a>, <a href="https://profiles.wordpress.org/petya">Petya Raykovska</a>, Przemysław Mirota, <a href="https://profiles.wordpress.org/qraczek">qraczek</a>, <a href="https://profiles.wordpress.org/bi0xid">Rafa Poveda</a>, <a href="https://profiles.wordpress.org/ramiy">Rami Yushuvaev</a>, <a href="https://profiles.wordpress.org/rasheed">Rasheed Bydousi</a>, <a href="https://profiles.wordpress.org/gwgan">Rhoslyn Prys</a>, <a href="https://profiles.wordpress.org/robee">Robert Axelsen</a>, <a href="https://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="https://profiles.wordpress.org/siobhyb">Siobhan Bamber</a>, <a href="https://profiles.wordpress.org/netweb">Stephen Edgar</a>, <a href="https://profiles.wordpress.org/tohave">ک To Have داشتن</a>, <a href="https://profiles.wordpress.org/zodiac1978">Torsten Landsiedel</a>, <a href="https://profiles.wordpress.org/egalego">Victor J. Quesada</a>, <a href="https://profiles.wordpress.org/wolly">Wolly</a>, <a href="https://profiles.wordpress.org/xavivars">Xavi Ivars</a>, <a href="https://profiles.wordpress.org/xibe">Xavier Borderie</a></p>\n<p>If you want to follow along or help out, check out <a href="https://make.wordpress.org/">Make WordPress</a> and our <a href="https://make.wordpress.org/core/">core development blog</a>. Thanks for choosing WordPress. See you soon for version 4.3!</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/news/2015/04/powell/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:32:"WordPress 4.1.2 Security Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/news/2015/04/wordpress-4-1-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:60:"https://wordpress.org/news/2015/04/wordpress-4-1-2/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 21 Apr 2015 13:44:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3628";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:383:"WordPress 4.1.2 is now available. This is a critical security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.1.1 and earlier are affected by a critical cross-site scripting vulnerability, which could enable anonymous users to compromise a site. This was reported by Cedric Van Bockhaven and fixed by [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Gary Pendergast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:3913:"<p>WordPress 4.1.2 is now available. This is a <strong>critical security release</strong> for all previous versions and we strongly encourage you to update your sites immediately.</p>\n<p>WordPress versions 4.1.1 and earlier are affected by a critical cross-site scripting vulnerability, which could enable anonymous users to compromise a site. This was reported by <a href="https://cedricvb.be">Cedric Van Bockhaven</a> and fixed by <a href="http://pento.net/">Gary Pendergast</a>, <a href="http://blogwaffe.com/">Mike Adams</a>, and <a href="http://nacin.com/">Andrew Nacin</a> of the WordPress security team.</p>\n<p>We also fixed three other security issues:</p>\n<ul>\n<li>In WordPress 4.1 and higher, files with invalid or unsafe names could be uploaded. Discovered by <a href="http://HSASec.de">Michael Kapfer and Sebastian Kraemer of HSASec</a>.</li>\n<li>In WordPress 3.9 and higher, a very limited cross-site scripting vulnerability could be used as part of a social engineering attack. Discovered by <a href="http://zoczus.blogspot.com/">Jakub Zoczek</a>.</li>\n<li>Some plugins were vulnerable to an SQL injection vulnerability. Discovered by Ben Bidner of the WordPress security team.</li>\n</ul>\n<p>We also made four hardening changes, discovered by <a href="http://codesymphony.co/">J.D. Grimes</a>, Divyesh Prajapati, <a href="http://www.allancollins.net/">Allan Collins</a>, <a href="https://sucuri.net/">Marc-Alexandre Montpas</a> and <a href="https://profiles.wordpress.org/jblz">Jeff Bowen</a>.</p>\n<p>We appreciated the <a href="https://make.wordpress.org/core/handbook/reporting-security-vulnerabilities/">responsible disclosure</a> of these issues directly to our security team. For more information, see the <a href="https://codex.wordpress.org/Version_4.1.2">release notes</a> or consult the <a href="https://core.trac.wordpress.org/log/branches/4.1?rev=32234&amp;stop_rev=32144">list of changes</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.1.2</a> or venture over to <strong>Dashboard → Updates</strong> and simply click &#8220;Update Now.&#8221; Sites that support automatic background updates are already beginning to update to WordPress 4.1.2.</p>\n<p>Thanks to everyone who contributed to 4.1.2: <a href="https://profiles.wordpress.org/collinsinternet">Allan Collins</a>, <a href="https://profiles.wordpress.org/xknown">Alex Concha</a>, <a href="https://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="https://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="https://profiles.wordpress.org/vortfu">Ben Bidner</a>, <a href="https://profiles.wordpress.org/boonbgorges">Boone Gorges</a>, <a href="https://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="https://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="https://profiles.wordpress.org/DrewAPicture">Drew Jaynes</a>, <a href="https://profiles.wordpress.org/pento">Gary Pendergast</a>, <a href="https://profiles.wordpress.org/helen">Helen Hou-Sandí</a>, <a href="https://profiles.wordpress.org/johnbillion">John Blackbourn</a>, and <a href="https://profiles.wordpress.org/mdawaffe">Mike Adams</a>.</p>\n<p>A number of plugins also released security fixes yesterday. Keep everything updated to stay secure. If you’re a plugin author, please read <a href="https://make.wordpress.org/plugins/2015/04/20/fixing-add_query_arg-and-remove_query_arg-usage/">this post</a> to confirm that your plugin is not affected by the same issue. Thank you to all of the plugin authors who worked closely with our security team to ensure a coordinated response.</p>\n<p><em>Already testing WordPress 4.2? The third release candidate is now available (<a href="https://wordpress.org/wordpress-4.2-RC3.zip">zip</a>) and it contains these fixes. For more on 4.2, see <a href="https://wordpress.org/news/2015/04/wordpress-4-2-release-candidate/">the RC 1 announcement post</a>.</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2015/04/wordpress-4-1-2/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"WordPress 4.2 Release Candidate";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:67:"https://wordpress.org/news/2015/04/wordpress-4-2-release-candidate/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:76:"https://wordpress.org/news/2015/04/wordpress-4-2-release-candidate/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 15 Apr 2015 19:07:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3609";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:334:"The release candidate for WordPress 4.2 is now available. We&#8217;ve made more than 140 changes since releasing Beta 4 a week and a half ago. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.2 on Wednesday, [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Drew Jaynes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2328:"<p>The release candidate for WordPress 4.2 is now available.</p>\n<p>We&#8217;ve made more than <a href="https://core.trac.wordpress.org/log?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=32136&amp;stop_rev=31996&amp;limit=100">140 changes</a> since releasing Beta 4 a week and a half ago. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.2 on <strong>Wednesday, April 22</strong>, but we need your help to get there.</p>\n<p>If you haven’t tested 4.2 yet, now is the time! (Please though, not on your live site unless you’re adventurous.)</p>\n<p><strong>Think you&#8217;ve found a bug?</strong> Please post to the <a href="https://wordpress.org/support/forum/alphabeta/">Alpha/Beta support forum</a>. If any known issues come up, you&#8217;ll be able to <a href="https://core.trac.wordpress.org/report/5">find them here</a>.</p>\n<p>To test WordPress 4.2 RC1, you can use the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin or you can <a href="https://wordpress.org/wordpress-4.2-RC1.zip">download the release candidate here</a> (zip). </p>\n<p>For more information about what’s new in version 4.2, check out the <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-1/">Beta 1</a>, <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-2/">Beta 2</a>, <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-3/">Beta 3</a>, and <a href="https://wordpress.org/news/2015/04/wordpress-4-2-beta-4/">Beta 4</a> blog posts.</p>\n<p><strong>Developers</strong>, please test your plugins and themes against WordPress 4.2 and update your plugin&#8217;s <em>Tested up to</em> version in the readme to 4.2 before next week. If you find compatibility problems, we never want to break things, so please be sure to post to the support forums so we can figure those out before the final release.</p>\n<p>Be sure to <a href="https://make.wordpress.org/core/">follow along the core development blog</a>, where we&#8217;ll continue to post <a href="https://make.wordpress.org/core/tag/4-2-dev-notes/">notes for developers</a> for 4.2.</p>\n<p><em>Im-Press-ive saving</em><br />\n<em>Achievement unlocked: RC</em><br />\n<em>Release here we come</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:72:"https://wordpress.org/news/2015/04/wordpress-4-2-release-candidate/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:42:"\n		\n		\n		\n		\n		\n				\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:29:"Improvements to WordPress.org";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wordpress.org/news/2015/04/improvements-to-wordpress-org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:74:"https://wordpress.org/news/2015/04/improvements-to-wordpress-org/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 04 Apr 2015 20:19:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:4:"Meta";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3494";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:335:"If you visit WordPress.org regularly you might have noticed some changes around the place. If you don’t, now’s the time to check them out! We’ve been working hard to improve the site to make it more useful to everyone, both developers and users, and we hope you like what we’ve done. New Theme and Plugin Directories [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Samuel Sidler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:5551:"<p>If you visit WordPress.org regularly you might have noticed some changes around the place. If you don’t, now’s the time to check them out! We’ve been working hard to improve the site to make it more useful to everyone, both developers and users, and we hope you like what we’ve done.</p>\n<h2>New Theme and Plugin Directories</h2>\n<p>Since WordPress 3.8, you’ve been enjoying improved theme management in your WordPress admin, and in WordPress 4.0 plugin management was refined. We’ve brought these experiences from your admin and re-created them right here on WordPress.org.</p>\n<h3>Theme Directory</h3>\n<p>The <a href="https://wordpress.org/themes/">Theme Directory</a> has a better browsing experience, with handy tabs where you can view featured, popular, and the latest themes. As with the theme experience in your admin, you can use the feature filter to browse for just the right theme for your WordPress website.</p>\n<p><img class="alignnone size-large wp-image-3572" src="https://wordpress.org/news/files/2015/04/theme-directory-1024x768.png" alt="theme-directory" width="692" height="519" /></p>\n<p>Click on a theme to get more information about it, including shiny screenshots, ratings, and statistics.</p>\n<p><img class="alignnone size-large wp-image-3573" src="https://wordpress.org/news/files/2015/04/theme-directory-individual-1024x768.png" alt="theme-directory-individual" width="692" height="519" /></p>\n<p>Konstantin Obenland <a href="https://make.wordpress.org/meta/2015/03/10/new-theme-directory/">posted a good overview</a> of everything involved with the theme directory overhaul and followed up with <a href="https://make.wordpress.org/meta/2015/03/31/theme-directory-stats/">a post on improved statistics</a>.</p>\n<h3>Plugin Directory</h3>\n<p>The <a href="https://wordpress.org/plugins/">Plugin Directory</a> has a brand new theme that mirrors the experience in your WordPress admin, with a more visual experience, and better search and statistics.</p>\n<p><img class="alignnone size-large wp-image-3594" src="https://wordpress.org/news/files/2015/04/plugin-directory-1024x768.png" alt="plugin-directory" width="692" height="519" /></p>\n<p>As well as a facelift, there are some great new features for you to play around with:</p>\n<ul>\n<li>Favorites – when you’re logged in to you WordPress.org account, this page gives you direct access to the plugins that you have favorited.</li>\n<li>Beta Testing – try out plugins where developers are experimenting with new features for WordPress.</li>\n<li>Search by plugin author – you can search for a plugin author using their username.</li>\n<li>Better statistics – listings now display the number of active installs so you can see how many people are actually using a plugin.</li>\n</ul>\n<p>An <a href="https://make.wordpress.org/meta/2015/03/04/new-plugin-directory-theme/">overview of the new theme</a> was posted by Scott Reilly.</p>\n<h2>Better Statistics</h2>\n<p>We’ve made huge improvements to <a href="https://wordpress.org/about/stats/">our statistics</a>. This gives us more useful information about the WordPress versions people are using, their PHP version, and their MySQL version.</p>\n<p>Already these new statistics have provided us with useful insights into WordPress usage.</p>\n<ul>\n<li>More than 43% of all sites are running the latest version of WordPress. Previously, we thought only 10% of sites were up-to-date. By excluding sites that are no longer online we were able to improve these statistics.</li>\n<li>We were able to clear up the data around WordPress 3.0, bringing it more in line with expectations. This anomaly was a by-product of spammers.</li>\n<li>Only 15.9% of sites are using PHP 5.2, which is better than we thought.</li>\n</ul>\n<p>Over the coming months we’ll be able to use these statistics to bring you new tools and improvements, and to make more informed decisions across the board. Read <a href="https://make.wordpress.org/meta/2015/03/01/major-update-to-our-version-stats-for-php-mysql-and-wordpress/">Andrew Nacin&#8217;s post about these changes</a> for more background.</p>\n<h2>Thanks!</h2>\n<p>Thanks to everyone who contributed to the theme directory redesign, the plugin directory refresh, and improved statistics: <a href="https://profiles.wordpress.org/deconf">Alin Marcu</a>, <a href="https://profiles.wordpress.org/colorful-tones/">Damon Cook</a>, <a href="https://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="https://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="https://profiles.wordpress.org/mj12982">Jan Cavan Boulas</a>, <a href="https://profiles.wordpress.org/obenland">Konstantin Obenland</a>, <a href="https://profiles.wordpress.org/BrashRebel">Kyle Maurer</a>, <a href="https://profiles.wordpress.org/matveb">Matías Ventura</a>, <a href="https://profiles.wordpress.org/melchoyce">Mel Choyce</a>, <a href="https://profiles.wordpress.org/nataliemac">Natalie MacLees</a>, <a href="https://profiles.wordpress.org/pauldewouters">Paul de Wouters</a>, <a href="https://profiles.wordpress.org/samuelsidler">Samuel Sidler</a>, <a href="https://profiles.wordpress.org/Otto42">Samuel Wood (Otto)</a>, <a href="https://profiles.wordpress.org/coffee2code">Scott Reilly</a>, <a href="https://profiles.wordpress.org/siobhan">Siobhan McKeown</a>.</p>\n<p>If you want to help out or follow along with future WordPress.org projects, check out <a href="https://make.wordpress.org/">Make WordPress</a> and our <a href="https://make.wordpress.org/meta/">meta development blog</a>.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:70:"https://wordpress.org/news/2015/04/improvements-to-wordpress-org/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.2 Beta 4";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2015/04/wordpress-4-2-beta-4/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wordpress.org/news/2015/04/wordpress-4-2-beta-4/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 03 Apr 2015 13:05:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3566";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:337:"WordPress 4.2 Beta 4 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the WordPress Beta Tester plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Drew Jaynes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2694:"<p>WordPress 4.2 Beta 4 is now available!</p>\n<p><strong>This software is still in development,</strong> so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="https://wordpress.org/wordpress-4.2-beta4.zip">download the beta here</a> (zip).</p>\n<p>For more information about what’s new in version 4.2, check out the <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-1/">Beta 1</a>, <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-2/">Beta 2</a>, and <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-3/">Beta 3</a> blog posts. Some of the changes in Beta 4 include:</p>\n<ul>\n<li>Incrementally improved the experience when <strong>accessing the Customizer on mobile</strong>. Please test on your mobile devices and let us know if anything seems wonky.</li>\n<li>Added the ability to make <strong>admin notices dismissible</strong>. Plugin and theme authors: adding <code>.notice</code> and <code>.is-dismissible</code> as adjacent classes to your notice containers should automatically make them dismissible. Please test.</li>\n<li>Fixed some reported issues with <strong>backward-compatibility issues</strong> caused by the modularization of core JS files.</li>\n<li>Removed the <strong>ability to swipe the admin menu open and closed</strong> on touch devices due to reports of some issues with built-in history navigation on certain platforms.</li>\n<li>Improved <strong>accessibility of the WordPress admin</strong> by adding landmark roles. Screen reader users: please test in any core admin screens.</li>\n<li><strong>Various bug fixes</strong>. We&#8217;ve made <a href="https://core.trac.wordpress.org/log?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=31996&amp;stop_rev=31902&amp;limit=100">more than 90 changes</a> in the last week.</li>\n</ul>\n<p>If you think you’ve found a bug, you can post to the <a href="https://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a bug report, <a href="https://core.trac.wordpress.org/">file one on the WordPress Trac</a>. There, you can also find <a href="https://core.trac.wordpress.org/tickets/major">a list of known bugs</a> and <a href="https://core.trac.wordpress.org/query?status=closed&amp;group=component&amp;milestone=4.2">everything we’ve fixed</a>.</p>\n<p><em>Dismiss notices</em><br />\n<em>Customizer on mobile</em><br />\n<em>RC nearly here</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:61:"https://wordpress.org/news/2015/04/wordpress-4-2-beta-4/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.2 Beta 3";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-3/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-3/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 26 Mar 2015 18:32:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3522";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:337:"WordPress 4.2 Beta 3 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the WordPress Beta Tester plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Drew Jaynes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2986:"<p>WordPress 4.2 Beta 3 is now available!</p>\n<p><strong>This software is still in development,</strong> so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="https://wordpress.org/wordpress-4.2-beta3.zip">download the beta here</a> (zip).</p>\n<p>For more information about what’s new in version 4.2, check out the <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-1/">Beta 1</a> and <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-2/">Beta 2</a> blog posts. Some of the changes in Beta 3 include:</p>\n<ul>\n<li>Removed <strong>Shiny Installs</strong> functionality due to concerns about the activation workflow. Please test the remaining &#8220;Shiny Updates&#8221; functionality from both the Plugins &gt; Add New and Plugins screens to ensure in-line updating still works as well as before.</li>\n<li>Fixed an issue with the <strong>Comments Quick Edit</strong> layout breaking on smaller screens. Please test on your mobile devices.</li>\n<li>Improved <strong>accessibility of login screen errors</strong>. Screen reader users: please let us know if you encounter any issues.</li>\n<li>Refined the <strong>emoji compatibility</strong> script to only load on the front- and back-end if the browser requires it. If you&#8217;re using a legacy web browser, please test.</li>\n<li>Fixed several issues in <strong>Press This</strong> with inserted images being improperly linked to locations other than the source site. Go ahead, &#8220;press&#8221; a site with images on the page and tell us if the image links aren&#8217;t working as you&#8217;d expect.</li>\n<li>Standardized the <strong>time display format</strong> in a variety of admin screens, switching to 24-hour notation where a.m. or p.m. are not specified. Please let us know if you notice you notice anything amiss!</li>\n<li><strong>Various other bug fixes</strong>. We&#8217;ve made <a href="https://core.trac.wordpress.org/log?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=31901&amp;stop_rev=31835&amp;limit=100">more than 65 changes</a> in the last week.</li>\n</ul>\n<p>If you think you’ve found a bug, you can post to the <a href="https://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a bug report, <a href="https://core.trac.wordpress.org/">file one on the WordPress Trac</a>. There, you can also find <a href="https://core.trac.wordpress.org/tickets/major">a list of known bugs</a> and <a href="https://core.trac.wordpress.org/query?status=closed&amp;group=component&amp;milestone=4.2">everything we’ve fixed</a>.</p>\n<p><em>Emoji loader</em><br />\n<em>&#8220;Shiny Updates&#8221; still stand firm</em><br />\n<em>Beta 3, please test!</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:61:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-3/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.2 Beta 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-2/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Mar 2015 19:30:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3498";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:337:"WordPress 4.2 Beta 2 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the WordPress Beta Tester plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Drew Jaynes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:2326:"<p>WordPress 4.2 Beta 2 is now available!</p>\n<p><strong>This software is still in development,</strong> so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="https://wordpress.org/wordpress-4.2-beta2.zip">download the beta here</a> (zip).</p>\n<p>For more information about what’s new in version 4.2, <a href="https://wordpress.org/news/2015/03/wordpress-4-2-beta-1/">check out the Beta 1 blog post</a>. Some of the changes in Beta 2 include:</p>\n<ul>\n<li>Added support for entering FTP and SSH credentials when <strong>updating plugins in-place</strong>. FTP and SSH users, please test!</li>\n<li><strong>Improved cross-browser support for emoji</strong> throughout WordPress. If you&#8217;re using an older web browser, please tell us if you have problems using emoji.</li>\n<li>Further <strong>refined Press This authoring</strong> with auto-embedded media and better content scanning. We&#8217;d love to know how auto-embeds work for you.</li>\n<li>Added a constructor and improved method consistency in <code>WP_Comment_Query</code>. Developers: if you&#8217;re extending <code>WP_Comment_Query</code>, please let us know if you run into any issues.</li>\n<li><strong>Various bug fixes</strong>. We&#8217;ve made <a href="https://core.trac.wordpress.org/log?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=31834&amp;stop_rev=31763&amp;limit=100">more than 70 changes</a> in the last week.</li>\n</ul>\n<p>If you think you’ve found a bug, you can post to the <a href="https://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a bug report, <a href="https://core.trac.wordpress.org/">file one on the WordPress Trac</a>. There, you can also find <a href="https://core.trac.wordpress.org/tickets/major">a list of known bugs</a> and <a href="https://core.trac.wordpress.org/query?status=closed&amp;group=component&amp;milestone=4.2">everything we’ve fixed</a>.</p>\n<p><em>Test some emoji</em><br />\n<em>FTP and SSH</em><br />\n<em>Let&#8217;s &#8220;Press&#8221; some embeds!</em></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:61:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-2/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:48:"\n		\n		\n		\n		\n		\n				\n		\n		\n\n		\n		\n				\n			\n		\n		";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.2 Beta 1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:65:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-1/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 12 Mar 2015 23:22:52 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3446";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:329:"WordPress 4.2 Beta 1 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can [&#8230;]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Drew Jaynes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4275:"<p>WordPress 4.2 Beta 1 is now available!</p>\n<p><strong>This software is still in development,</strong> so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.2, try the <a href="https://wordpress.org/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want “bleeding edge nightlies”). Or you can <a href="https://wordpress.org/wordpress-4.2-beta1.zip">download the beta here</a> (zip).</p>\n<p>4.2 is due out next month, but to get there, we need your help testing what we&#8217;ve been working on:</p>\n<ul>\n<li><strong>Press This</strong> has been completely revamped to make sharing content from around the web easier than ever. The new workflow is mobile friendly, and we&#8217;d love for you to try it out on all of your devices. Navigate to the Tools screen in your WordPress backend to get started (<a href="https://core.trac.wordpress.org/ticket/31373">#31373</a>). </li>\n<li><strong>Browsing and switching installed themes</strong> has been added to the Customizer to make switching faster and more convenient. We&#8217;re especially interested to know if this helps streamline the process of setting up your site (<a href="https://core.trac.wordpress.org/ticket/31303">#31303</a>).</li>\n<li>The workflow for <strong>updating and installing plugins</strong> just got more intuitive with the ability to install or update in-place from the Plugins screens. Try it out and let us know what you think! (<a href="https://core.trac.wordpress.org/ticket/29820">#29820</a>)</li>\n<li>If you felt like <strong>emoji</strong> were starkly missing from your content toolbox, worry no more. We&#8217;ve added emoji support nearly everywhere, even post slugs <img src="https://s.w.org/images/core/emoji/72x72/1f44d.png" alt="????" class="wp-smiley" style="height: 1em; max-height: 1em;" /> (<a href="https://core.trac.wordpress.org/ticket/31242">#31242</a>).</li>\n</ul>\n<p><strong>Developers</strong>: There have been a lot of changes for you to test as well, including:</p>\n<ul>\n<li><strong>Taxonomy Roadmap:</strong> Terms shared across multiple taxonomies will <a href="https://make.wordpress.org/core/2015/02/16/taxonomy-term-splitting-in-4-2-a-developer-guide/">now be split</a> into separate terms when one of them is updated. Please let us know if you hit any snags (<a href="https://core.trac.wordpress.org/ticket/5809/">#5809</a>).</li>\n<li>New <code>wp.a11y.speak()</code> functionality helps your JavaScript talk to screen readers to better inform impaired users what&#8217;s happening on-screen. Try it out in your plugin or theme and let us know if you notice any adverse affects (<a href="https://core.trac.wordpress.org/ticket/31368/">#31368</a>).</li>\n<li>Named clause support has been added to <code>WP_Query</code>, <code>WP_Comment_Query</code>, and <code>WP_User_Query</code>, allowing specific <code>meta_query</code> clauses to be used with <code>orderby</code>. If you have any complex queries, please test them (<a href="https://core.trac.wordpress.org/ticket/31045/">#31045</a>, <a href="https://core.trac.wordpress.org/ticket/31265/">#31265</a>).</li>\n</ul>\n<p>If you want a more in-depth view of what changes have made it into 4.2, <a href="https://make.wordpress.org/core/tag/week-in-core/">check out the weekly review posts</a> on the main development blog.</p>\n<p><strong>If you think you’ve found a bug</strong>, you can post to the <a href="https://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, <a href="https://make.wordpress.org/core/reports/">file one on the WordPress Trac</a>. There, you can also find <a href="https://core.trac.wordpress.org/tickets/major">a list of known bugs</a> and <a href="https://core.trac.wordpress.org/query?status=closed&amp;group=component&amp;milestone=4.2">everything we’ve fixed</a> so far.</p>\n<p>Happy testing!</p>\n<p><em>Press This: switch a theme</em><br />\n<em>Save time installing plugins</em><br />\n<em>Testing makes us</em> <img src="https://s.w.org/images/core/emoji/72x72/1f603.png" alt="????" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:61:"https://wordpress.org/news/2015/03/wordpress-4-2-beta-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:32:"https://wordpress.org/news/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:6:"hourly";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 13 May 2015 20:15:12 GMT";s:12:"content-type";s:34:"application/rss+xml; charset=UTF-8";s:10:"connection";s:5:"close";s:25:"strict-transport-security";s:11:"max-age=360";s:10:"x-pingback";s:37:"https://wordpress.org/news/xmlrpc.php";s:13:"last-modified";s:29:"Fri, 08 May 2015 10:20:09 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 249";}s:5:"build";s:14:"20130911110210";}', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(519, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1431627313', 'no'),
(520, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1431584113', 'no'),
(523, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1431627318', 'no');
INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(524, '_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:61:"\n	\n	\n	\n	\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"WordPress Planet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:28:"http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:2:"en";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:47:"WordPress Planet - http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:50:{i:0;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:84:"WPTavern: WP Rollback Provides Basic Versioning for WordPress.org Plugins and Themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43696";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:94:"http://wptavern.com/wp-rollback-provides-basic-versioning-for-wordpress-org-plugins-and-themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4615:"<a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/undo-button.jpg"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/undo-button.jpg?resize=1025%2C506" alt="The undo key from a computer keyboard" class="size-full wp-image-43721" /></a>The undo key from a computer keyboard\n<p>Despite the recent proliferation of plugins that add git-based version control to WordPress, your average user does not require a full-blown version control system as part of regular site management. Developers can certainly benefit from tools like <a href="http://wptavern.com/free-revisr-plugin-offers-git-management-for-wordpress" target="_blank">Revisr</a> and <a href="http://wptavern.com/gitium-provides-automatic-git-version-control-and-deployment-for-wordpress-plugins-and-themes" target="_blank">Gitium</a> for managing projects with Git, but the vast majority of WordPress users are more likely to benefit from a simple &#8220;undo&#8221; button for mistakes or bad updates.</p>\n<p><a href="https://wordpress.org/plugins/wp-rollback/" target="_blank">WP Rollback</a> is a new plugin that brings the concept of an &#8220;undo&#8221; button to updates for plugins and themes hosted on WordPress.org. It allows users to easily rollback to any previous (or newer) version without the hassle of manually downloading files.</p>\n<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback.jpg"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback.jpg?resize=925%2C228" alt="wp-rollback" class="aligncenter size-full wp-image-43711" /></a></p>\n<p>Clicking the Rollback link will take the user to a screen where he can select from a list of previous versions or update to newer ones.</p>\n<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback-versions-screen.jpg"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback-versions-screen.jpg?resize=576%2C437" alt="wp-rollback-versions-screen" class="aligncenter size-full wp-image-43712" /></a></p>\n<p>WP Rollback uses WordPress&#8217; native plugin updater to revert to previous versions.</p>\n<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback-update.jpg"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wp-rollback-update.jpg?resize=556%2C304" alt="wp-rollback-update" class="aligncenter size-full wp-image-43714" /></a></p>\n<p>While using older versions of themes/plugins is not generally encouraged, there are times when it&#8217;s unavoidable. For example, some plugin authors routinely push out buggy updates, seemingly without having run any tests on them, and then rely on their users to discover and report the problems. It can sometimes be 24 &#8211; 72 hours before the author has the chance to push out a fix to the buggy update. WP Rollback allows users to quickly revert to the previous working version of the plugin.</p>\n<p>As themes hosted on WordPress.org <a href="http://wptavern.com/do-wordpress-org-themes-need-a-changelog" target="_blank">do not yet have change logs</a>, there may be times when a user updates to a new version of a theme where the author has made some major changes to the markup and/or styles. Without a changelog, the user has no idea what is included in the update or how it might impact a child theme or plugin&#8217;s output. WP Rollback gives you the ability to test a theme update and quickly rollback if necessary until you&#8217;ve had the chance to get your site ready.</p>\n<p>Most WordPress users do not have a development environment in place for putting software updates to the test before rolling them out. They simply expect updates to work, but there will always be those rare instances of unforeseen conflicts and bugs. Having WP Rollback in place should help users to be less wary about taking updates, since they know they can easily rollback if something goes wrong.</p>\n<p><a href="https://wordimpress.com/" target="_blank">WordImpress</a>, the folks behind WP Rollback as well as the new <a href="http://wptavern.com/give-a-new-free-donations-plugin-for-wordpress" target="_blank">Give plugin</a>, encourages users to backup their sites before performing plugin/theme updates or reverts. Ideally, you would test any changes in a development environment first to ensure that everything works as planned. <a href="https://wordpress.org/plugins/wp-rollback/" target="_blank">WP Rollback</a> is available for free on WordPress.org and <a href="https://github.com/WordImpress/WP-Rollback/wiki" target="_blank">documentation can be found on GitHub</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 May 2015 19:34:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Matt: Advanced Hindsight";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45039";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:40:"http://ma.tt/2015/05/advanced-hindsight/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:612:"<blockquote><p>Beginning with the 2015 academic year, the Center for Advanced Hindsight (CAH) at Duke University will invite promising startups to join its behavioral lab and leverage academic research in their business models. The Center is housed within the Social Science Research Institute at Duke University and is led by Professor Dan Ariely, Professor of Psychology and Behavioral Economics at Duke University.</p></blockquote>\n<p><a href="http://danariely.com/2015/05/08/announcing-cah-startup-lab/">This is a pretty awesome opportunity for entrepreneurs</a>, I hope a reader of this blog pursues it.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 May 2015 04:19:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:98:"WPTavern: Major Changes to WordPress.org Guidelines Should Have a Request for Comments Time Period";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43595";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:104:"http://wptavern.com/major-wordpress-org-guideline-changes-should-have-a-request-for-comments-time-period";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7603:"<p>For the last three years, the <a href="https://make.wordpress.org/themes/">WordPress Theme Review Team</a> has tried to encourage theme authors to adopt the Theme Customizer. In April, the decision was made by the TRT to no longer encourage, but <a href="https://make.wordpress.org/themes/2015/04/22/details-on-the-new-theme-settings-customizer-guideline/">require</a> all theme options to be in the customizer. Although the decision was three years in the making, the community didn&#8217;t have an opportunity to provide feedback until <strong>after</strong> the requirement was put in place.</p>\n<h2>The Timeline</h2>\n<a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2014/07/EstimatedReadingTimeFeaturedImage.png"><img class="size-full wp-image-25719" src="http://i0.wp.com/wptavern.com/wp-content/uploads/2014/07/EstimatedReadingTimeFeaturedImage.png?resize=639%2C200" alt="Estimated Reading Time Featured Image" /></a>photo credit: <a href="https://www.flickr.com/photos/eyesplash/8467316141/">Eyesplash &#8211; let&#8217;s feel the heat</a> &#8211; <a href="http://creativecommons.org/licenses/by-nc-nd/2.0/">cc</a>\n<p>Those who follow the official <a href="https://make.wordpress.org/themes/">TRT blog</a> likely saw the writing on the wall. With the <a href="https://wordpress.org/news/2012/06/green/">release of WordPress 3.4</a> in 2012, which introduced the theme customizer, the TRT held discussions on <a href="https://make.wordpress.org/themes/2012/05/08/proposed-wordpress-3-4-guidelines-revisions/">proposed changes</a> to the theme review guidelines. One of the proposed changes <strong>recommended</strong> theme options be incorporated into the theme customizer. Of particular interest is <a href="https://make.wordpress.org/themes/2012/05/08/proposed-wordpress-3-4-guidelines-revisions/#comment-19516">a conversation</a> between Justin Tadlock and Chip Bennett on whether or not the customizer should be recommended so early.</p>\n<p>In November of 2014, the team <a href="https://make.wordpress.org/themes/2014/11/04/todays-meeting-agenda-ive-gone-back-all-comments/">held a meeting</a> to discuss modifications to the theme review guidelines. Up until this point, theme authors were allowed to create theme options in one of three ways, Theme Customizer, Settings API, or with custom options pages using the Theme Mods API.</p>\n<p>During the meeting, <a href="https://wordpress.slack.com/archives/themereview/p1415124589001969">Tadlock suggested</a> that the team should <strong>strongly recommend</strong> theme authors to use the customizer. Members in attendance agreed and the theme review guidelines changed to <a href="https://make.wordpress.org/themes/2014/04/03/wordpress-3-9-guidelines-revision-proposal-round-2/">strongly recommend</a> theme options be placed into the customizer.</p>\n<p>A few days after the meeting, Tadlock published a post asking <a href="https://make.wordpress.org/themes/2014/11/11/how-do-we-solve-the-theme-options-problem/">how do we solve the theme options problem</a>? He highlights the lack of educational resources on the customizer as one of the major culprits of its slow adoption.</p>\n<blockquote><p>One of the things I’ve always hoped the TRT would become is more of an educational team. I firmly believe that if we didn’t have to spend so much time dealing with theme options, we could spend more time on educating in other areas of the dev/design.</p>\n<p>I’m writing this post because I believe this to be the biggest hangup with themes today. It’s the hardest part of the review process. It’s also one of the most critical because theme options means potential security issues.</p></blockquote>\n<p>The post opened up a dialogue to discuss ways of dealing with several issues related to getting developers to adopt and use the customizer. Bennett <a href="https://make.wordpress.org/themes/2014/11/24/understanding-the-apis-related-to-theme-options/">published a post a few days later</a> that explained APIs related to theme options. It was later followed up by Tadlock with a post on <a href="https://make.wordpress.org/themes/2014/11/26/customizer-theme-mods-api-or-settings-api/">choosing Theme Mods API or Settings API</a>.</p>\n<h2>The Vote</h2>\n<p>Fast forward to April 2015, the team <a href="https://wordpress.slack.com/archives/themereview/p1429639190005379">held a meeting</a> and unanimously agreed to require theme authors to place theme options into the customizer. A day later, <a href="https://make.wordpress.org/themes/2015/04/22/details-on-the-new-theme-settings-customizer-guideline/">Tadlock explained</a> why the change was made and how the team came to its decision.</p>\n<blockquote><p>First, I want to say that the team did not take this decision lightly nor did we make it quickly. In fact, this has been an ongoing discussion for nearly 3 years (since the customizer was first introduced in core). Many of us had originally hoped that we could take a more organic approach to this and allow theme authors to naturally make the switch on their own given enough time.</p></blockquote>\n<p>The decision created a <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options#comments">passionate, lengthy conversation</a> with several people chiming in <em>after the fact</em> on WP Tavern.</p>\n<h2>A Request for Comments Period</h2>\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/03/FutureOfCommentingFeaturedImage.png"><img class="size-full wp-image-18515" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/03/FutureOfCommentingFeaturedImage.png?resize=638%2C200" alt="Future Of Commenting Featured Image" /></a>photo credit: <a href="http://www.flickr.com/photos/marcwathieu/2945514734/">Marc Wathieu</a> &#8211; <a href="http://creativecommons.org/licenses/by-nc/2.0/">cc</a>\n<p>On the TRT blog, there are several blog posts that encourage feedback, especially on guideline proposals. In this instance however, feedback, concerns, and criticism weren&#8217;t encouraged until after the decision was made.</p>\n<p>The TRT usually <a href="https://make.wordpress.org/themes/2015/04/13/weekly-meeting-agenda-this-week-weve-got-our-2/">publishes an agenda</a> that highlights what topics will be discussed during the meeting. An agenda was published for the April 14th meeting but not for the April 21st meeting. This means only those in attendance were able to voice an opinion and vote on the issue, as there was no advance notice.</p>\n<p>I understand the team has discussed this change for the last three years, but I would like to have seen a request for comments period for at least a month on the TRT blog.</p>\n<p>This way, people could comment on the decision before it was implemented. The team could have controlled the conversation, provided a more accessible way of participating in the discussion versus Slack, and heard legitimate concerns from theme developers.</p>\n<p>I hope major changes like this in the future are addressed in a way where the public can be more involved. The notion that concerned parties should have been in Slack during the meeting to voice concerns before the decision was made is unacceptable. People have things to do and while I think Slack is easier to use than IRC, a blog post with a comment form is accessible to a lot more people.</p>\n<p>An RFC period doesn&#8217;t make sense for a lot of what takes place in the world of WordPress development but a change that affects current, past, and future themes in the directory is a great example of where it does makes sense.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 May 2015 22:10:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:93:"WPTavern: Customizer Theme Resizer Plugin Offers Live Previews of Your Site on Mobile Devices";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43599";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:103:"http://wptavern.com/customizer-theme-resizer-plugin-offers-live-previews-of-your-site-on-mobile-devices";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3729:"<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-theme-resizer.jpg"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-theme-resizer.jpg?resize=650%2C300" alt="customizer-theme-resizer" class="aligncenter size-full wp-image-43646" /></a></p>\n<p>Contributors on the <a href="http://wptavern.com/wordpress-4-3-to-focus-on-mobile-experience-admin-ui-better-passwords-and-customizer-improvements" target="_blank">upcoming WordPress 4.3 release</a> are moving full speed ahead with plans to improve the experience of using the customizer. They&#8217;re also exploring ways to re-architect it to make way for feature plugins that would bring in additional functionality.</p>\n<p>WordPress core contributors have continually demonstrated a commitment to improving the customizer to make it better for everyone, and the Theme Developer Handbook was recently <a href="http://wptavern.com/wordpress-theme-developer-handbook-updated-with-comprehensive-guide-to-the-customizer-api" target="_blank">updated with a comprehensive guide to using the Customizer API</a>. Plugin developers are also finding new ways to <a href="https://wordpress.org/plugins/tags/customizer" target="_blank">extend the customizer</a> to support the increasing number of users who depend on it for live previews.</p>\n<p><a href="https://wordpress.org/plugins/customizer-theme-resizer/" target="_blank">Customizer Theme Resizer</a> is a new plugin that is immensely useful for previewing your site on various mobile devices while adjusting options in the customizer. The plugin was created by Japanese web developer <a href="https://profiles.wordpress.org/webnist/" target="_blank">Tatsuki Ohta</a>, who has 10 other extensions listed in the official directory. It allows you to review your design for responsiveness without having to leave the customizer panel.</p>\n<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-theme-resizer-screenshot.jpg"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-theme-resizer-screenshot.jpg?resize=905%2C561" alt="customizer-theme-resizer-screenshot" class="aligncenter size-full wp-image-43648" /></a></p>\n<p>Customizer Theme Resizer offers nine preset mobile phone/tablet display options, or you can manually add your own screen dimensions. You can also easily switch between portrait or landscape mode.</p>\n<p>The plugin works seamlessly within the customizer, so you can set it to iPhone 6, for example, and live preview any of your design choices on that device. This is especially helpful when uploading a site logo or a header image if you want to see how those images resize down for devices. It keeps you from having to go back and forth while making adjustments and testing responsiveness on your phone or simulator.</p>\n<p>I tested the plugin and found that it works as advertised. You can see a quick overview of how it works in the video below:</p>\n<p><span class="embed-youtube"></span></p>\n<p>As a result of the WordPress.org Theme Review Team&#8217;s decision to <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options" target="_blank">enforce the use of the customizer for theme options</a>, more themes will be moving to support the customizer ahead of the deadline to comply. The Customizer Theme Resizer plugin is a handy tool to use in conjunction with any theme that supports the customizer. Install the <a href="https://wordpress.org/plugins/customizer-theme-resizer/" target="_blank">Customizer Theme Resizer</a> plugin from WordPress.org the next time you want to live preview the mobile-friendliness of your design adjustments.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 May 2015 21:52:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:71:"WPTavern: 3 Big Things that Will Happen to WordPress in the Near Future";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43611";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:81:"http://wptavern.com/3-big-things-that-will-happen-to-wordpress-in-the-near-future";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6711:"<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/petersuhm.jpeg"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/petersuhm.jpeg?resize=150%2C150" alt="petersuhm" class="alignright size-thumbnail wp-image-43613" /></a>This opinion piece was contributed by guest author <a href="https://twitter.com/petersuhm" target="_blank">Peter Suhm</a>. Peter is a web developer from the Land of the Danes. He is the creator of <a href="https://wppusher.com/" target="_blank">WP Pusher</a> and a huge travel addict, bringing his work along with him as he goes.<br />\n&nbsp;</p>\n<hr />\n<h3>Yet another WordPress prophecy</h3>\n<p>Okay, I admit that the title of this post is a bit risky. Honestly, it should probably have been &#8220;3 Big Things That I Wholeheartedly Hope Will Happen To WordPress In The Not Too Distant Future&#8221;. That being said, I am optimistic by nature, and I actually think these three ideas are realistic scenarios. So in all modesty, and without further ado, here is my take on some of the next big things to happen in the WordPress world in the near future.</p>\n<h1>WordPress Will Have Dependency Management</h1>\n<p>There is no question about it. WordPress needs some sort of dependency management mechanism. We have seen all other fragments of the PHP community, and other languages too, adopt the use of dependency managers. Most likely, WordPress will adopt <a href="https://getcomposer.org/" target="_blank">Composer</a> in some form, either out-of-the-box or by configuration.</p>\n<h3>What is a dependency manager?</h3>\n<p>A dependency manager is a software tool that can resolve and manage the dependencies (other libraries) that a given library requires. In PHP we have Composer. Each PHP library that supports Composer will have a defined set of dependencies that it depends on. The role of Composer is to fetch all these dependencies and make sure they are all compatible with each other.</p>\n<h3>… and why does WordPress need one?</h3>\n<p>WordPress needs one so we do not have to reinvent the wheel every time we want to make a new plugin or theme. Every time we write code for WordPress when we could have used one of the existing PHP packages out there, we are essentially wasting our time. Allowing the use of third-party dependencies allows for much more rapid development and better security. So many security issues in WordPress plugins are the same ones showing up again and again.</p>\n<h3>What does this mean for you?</h3>\n<p>In the short run, for plugin developers, WordPress adopting a dependency manager will mean a huge opportunity for making WordPress specific plugins for all the existing PHP libraries out there. When this happens, we will see hundreds, if not thousands, of plugins that will just be WordPress wrappers around existing libraries. Some of these plugins will end up becoming very popular. So be ready if you are an upcoming plugin author!</p>\n<p>WordPress developers will probably also have to deal with some sort of frontend dependency manager, since, with the <a href="http://wp-api.org/" target="_blank">WP REST API</a>, a lot of things will be revolutionized on the frontend side of things. We will touch more on that in the next section.</p>\n<h1>WordPress Will Be “Just” a Backend</h1>\n<p>This is not my idea, but I am certain this is the way we are moving. With the WP REST API in core, WordPress will essentially be a backend, complete with user management and so forth, for your API-based web application. Themes are going to be JavaScript based and will communicate with WordPress through the API. Plugins will stay mainly PHP, with a dash of JavaScript, just as the backend itself will.</p>\n<p>I believe that a main reason for WordPress’ widespread success is the dashboard. It is extremely user friendly and intuitive. Add to that how simple and easy it is to add 3rd party plugins and themes and you have a winner. Extending core is also really trivial because of all the actions and filters that WordPress has built in. There is no way that the WP REST API is going to change this. It is simply adding an extra layer for frontend developers, and most likely, radically changing how we work with theming.</p>\n<p>A few years ago, I worked as a full time Ruby on Rails developer. For one project, we needed some kind of CMS to manage the content of our Rails app. One of the developers (a hardcore Ruby guy) suggested using the WordPress dashboard as a backend and just build a simple API around it. We never ended up doing that, but imagine how easy that would be to implement had the API been around at the time.</p>\n<h3>What does this mean for you?</h3>\n<p>If you are a WordPress theme developer, this means that in the future you will probably not be a WordPress developer any more. You will “just” be a theme developer. You better up those JavaScript skills before this happens.</p>\n<h1>WordPress Will Become More Decoupled</h1>\n<p>As a result of all this, WordPress will become a lot more decoupled. Obviously, the biggest cut will be between the backend (dashboard and plugins) and the front end (themes). It is also easy to imagine, with an adaptation of Composer, that core itself will become a lot more decoupled. Maybe similar to how the Laravel framework is split up into the Illuminate packages (now we will have to define what “near future” means, though).</p>\n<p>As already mentioned, the main component will be the dashboard. Plugins makes sense to keep as a part of the dashboard, but in the future, they might look more like WordPress-specific Composer packages. It makes sense to keep all this in PHP &#8211; of course with a bit of JavaScript here and there.</p>\n<p>Another thing to consider is that if Composer is adopted in the near future, that would naturally mean an upgrade of the minimum required PHP version. That will probably happen very soon, anyways. We might see some sort of frontend plugins as well, but these will be JavaScript and be managed through a frontend dependency management tool.</p>\n<h3>What does this mean for you?</h3>\n<p>This means that if you are a WordPress plugin developer, you can keep writing good old PHP code. No need to jump straight over to NodeJS, yet, but if you are a theme developer, you might want to keep an eye on what those guys are up to.</p>\n<p>It also means that WordPress is going to be much more decoupled and customizable. You will be able to pick the parts you need and skip the rest. If you need something different, you will most likely be able to find an existing PHP package that can do the job. Sounds good, right?</p>\n<p>These are my 5 cents. I am curious to hear what you think. Where is WordPress headed?</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 May 2015 18:15:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:106:"WPTavern: BuddyPress 2015 Survey Shows Increase in English-Speaking Communities and Commercial Theme Usage";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43531";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:116:"http://wptavern.com/buddypress-2015-survey-shows-increase-in-english-speaking-communities-and-commercial-theme-usage";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6558:"<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/2015-bp-survey-results.jpg"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/2015-bp-survey-results.jpg?resize=1025%2C576" alt="2015-bp-survey-results" class="aligncenter size-full wp-image-43580" /></a></p>\n<p>The <a href="https://buddypress.org/2015/05/2015-buddypress-survey-results/" target="_blank">BuddyPress 2015 survey results</a> are now available. This year&#8217;s survey did not have the same community penetration as <a href="http://wptavern.com/7-surprising-results-from-the-2013-buddypress-codex-survey" target="_blank">2013</a> and <a href="https://buddypress.org/2014/03/2014-buddypress-survey-results/" target="_blank">2014</a>, with 37.5% fewer respondents, but the information is still valuable for gauging how and where people are using the plugin. Volunteers collected feedback from 211 participants in 42 different countries.</p>\n<p>Feedback this year shows a few significant shifts from previous years, especially when it comes to languages used on BuddyPress sites. The top three languages in 2015 are English (69.23%), French (10.26%), and German (7.69%). In <a href="http://wptavern.com/7-surprising-results-from-the-2013-buddypress-codex-survey" target="_blank">2013</a>, language usage was fairly evenly divided between English (56%) and non-English sites.</p>\n<p>On the surface, the language results seem to indicate a shrinking international community, but it may be due to the fact that the survey lost participants from 20 countries captured the previous year.</p>\n<h3>Commercial BuddyPress Themes are on the Rise</h3>\n<p>Results indicate that 34% of community managers and developers surveyed are building BuddyPress sites with commercial WordPress themes that offer custom BP CSS and/or template modifications. That number is up from 26% the previous year, likely due to more BuddyPress themes entering the market.</p>\n<p>Accessing BuddyPress sites via mobile is also slowly on the rise with 63% of respondents reporting that they&#8217;ve used a smartphone to access their sites. It&#8217;s no surprise that the survey shows mobile responsiveness is one of the most important factors in theme selection.</p>\n<p>Other preferred BuddyPress theme features include compatibility with the latest BP version and a light/fresh design. This preference may be due to kinds of sites that users are building, which remain fairly unchanged from previous years:</p>\n<ul>\n<li>Generic (26.32%)</li>\n<li>Academic (23.31%)</li>\n<li>Artistic (12.03%)</li>\n<li>Sports (11.65%)</li>\n<li>Gaming (10.53%)</li>\n<li>Scientific (8.27%)</li>\n<li>Religious (6.77%)</li>\n<li>Travel (0.75%)</li>\n<li>Health (0.38%)</li>\n</ul>\n<h3>Extended Profiles and Activity Streams Remain the Most Used BuddyPress Components</h3>\n<p>Results show that the most used BuddyPress components are Extended Profiles (71.13%) and Activity Streams (66.49%), followed by User Groups (57.22%). Although Profiles and Activity remain dominant, they are waning slightly from the previous year while Groups are increasing in popularity.</p>\n<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/bp-components-usage.png"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/bp-components-usage.png?resize=1025%2C881" alt="bp-components-usage" class="aligncenter size-full wp-image-43575" /></a></p>\n<p>Surprisingly, Friend Connections, which are often associated with social networks, rank quite low on the list of components, trailing Messaging, Notifications, and Account Settings. Site Tracking, a feature used most often with multisite, ranks dead last among components that are always activated at just 8.25%.</p>\n<p>If you take a look at the features on track for <a href="http://wptavern.com/buddypress-2-3-beta-1-is-ready-for-testing" target="_blank">BuddyPress 2.3</a>, the direction of development seems to be trending toward improving the components that users are mostly likely to activate. Last year&#8217;s major performance improvements <a href="http://wptavern.com/buddypress-2-0-ramps-up-performance-reduces-footprint-by-up-to-75" target="_blank">reduced BuddyPress&#8217; footprint by up to 75%</a> in many places, especially for sites that rely on activity and member directories.</p>\n<p>The recent additions of the <a href="http://wptavern.com/buddypress-2-2-spumoni-released-featuring-new-member-type-api" target="_blank">Member Types API</a> and upcoming <a href="http://wptavern.com/buddypress-2-3-will-improve-avatar-uploads-with-the-new-bp-attachments-api" target="_blank">Attachments API</a> greatly improve the extensibility of components that BuddyPress site administrators are most frequently using. The survey results confirm that BP core development is being shaped by community feedback and overall the software is improving for those that are actively using it.</p>\n<p>The anonymous comments on the survey provide some critical feedback that indicate it may be time for BuddyPress contributors to reconsider how the software is presented to the world. One respondent feels that the tagline &#8220;social networking in a box&#8221; is inaccurate, given recent developments in other social networking software:</p>\n<blockquote><p>BuddyPress is some distance behind the features people now expect of modern social networks. OK for school, or small intranet purposes, but to call it &#8216;social networking in a box&#8217; is slightly stretching reality.</p></blockquote>\n<p>BuddyPress also continues to be somewhat daunting for beginners. Developers can be sold on its extensibility, but your average user trying to set up a social network will have a sharp learning curve when it comes to adding features beyond what is offered in BP core. That frustration, when it comes to extending the software, seems to make its way into users&#8217; opinions of BuddyPress in general.</p>\n<blockquote><p>I&#8217;ve been trying to learn BuddyPress for about a year. Setup is super easy. Mods are always a pain. I understand this has to do with community support. Everybody wants answers. Few pitch in to help.</p></blockquote>\n<p>This year&#8217;s survey results and user feedback provide BuddyPress core contributors and volunteers with some important ideas to consider for shaping both development and community support in the future. The full results of the survey are <a href="https://mercime.github.io/BuddyPress-2015-survey-results/" target="_blank">available on GitHub</a> with a more detailed breakdown and charts for each question.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 May 2015 19:31:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"Matt: New Yorker on Marc Andreessen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45044";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"http://ma.tt/2015/05/new-yorker-on-marc-andreessen/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:371:"<p>Tad Friend has a <a href="http://www.newyorker.com/magazine/2015/05/18/tomorrows-advance-man">great New Yorker profile of Marc Andreessen</a>, one of my favorite people to debate and talk to (though it happens all too rarely). Check out <a href="http://pmarcasays.golaun.ch/">Pmarca Says</a> if you want to catch up on some of his recent thinking from tweetstorms.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 May 2015 15:56:40 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:66:"WPTavern: Gazette: A Free WordPress Magazine Theme from Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43501";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:75:"http://wptavern.com/gazette-a-free-wordpress-magazine-theme-from-automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3367:"<p><a href="https://theme.wordpress.com/themes/gazette/" target="_blank">Gazette</a> is a new WordPress magazine theme from the folks at Automattic, designed by <a href="http://thomasguillot.com/2015/05/07/new-theme-gazette/" target="_blank">Thomas Guillot</a>. Since the majority of themes produced for WordPress.com are well-suited to single author blogs, Gazette&#8217;s fine-tuned focus on digital publications is a welcome addition to the collection.</p>\n<p>Magazine themes are generally few and far between, because they have to be designed for a constant flow of content with a homepage that allows the reader to quickly scan multiple featured stories. Gazette takes a minimalist approach to the magazine style in that it isn&#8217;t cluttered with skinny columns of varying widths, obtrusive advertising slots, etc. It could easily be used for a personal blog or photography site.</p>\n<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-homepage.jpg"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-homepage.jpg?resize=1025%2C906" alt="gazette-homepage" class="aligncenter size-full wp-image-43507" /></a></p>\n<p>As you scroll down the page, the sticky navigation/search bar pins the menu to the top for easy access. Gazette makes a strong impression with fullscreen featured images that display above post and page titles. The content area has been decluttered for readability with post meta pulled out into a separate column.</p>\n<p>Gazette supports image, gallery, video, and link post formats. The theme includes two optional widget areas (the right sidebar and footer), and two custom menus. With Jetpack active, Gazette adds an option to upload your site logo. The plugin also manages the featured content display, along with the related posts functionality seen in the <a href="https://gazettedemo.wordpress.com/" target="_blank">live demo</a>.</p>\n<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-author-bio.jpg"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-author-bio.jpg?resize=300%2C282" alt="gazette-author-bio" class="alignright size-medium wp-image-43552" /></a>Gazette includes a handful of layout and content options in the customizer:</p>\n<ul>\n<li>Display header image on blog index only</li>\n<li>Show author bio on the sidebar of single posts</li>\n<li>Display content in the footer, i.e. basic HTML, links, et.</li>\n</ul>\n<p>Gazette is responsive and maintains its striking visual appeal and readability on mobile devices. The design is similar to popular mobile news apps that display posts with titles overlayed on featured images.</p>\n<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-responsive.jpg"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/gazette-responsive.jpg?resize=560%2C222" alt="gazette-responsive" class="aligncenter size-full wp-image-43508" /></a></p>\n<p>Check out the <a href="https://gazettedemo.wordpress.com/" target="_blank">live demo</a> on WordPress.com to see Gazette in action. The theme is not yet available on WordPress.org but should be soon. In the meantime, the zip file for self-hosted sites can be downloaded from the sidebar of the <a href="https://theme.wordpress.com/themes/gazette/" target="_blank">Gazette theme page</a> on WordPress.com.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 May 2015 06:30:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:15:"Matt: Undercity";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45042";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:31:"http://ma.tt/2015/05/undercity/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:190:"<p>A great video going underneath the streets of New York, Ninja Turtle Style:</p>\n<p><span class="embed-youtube"></span></p>\n<p>Hat tip: <a href="http://dentedreality.com.au/">Beau</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 10 May 2015 15:47:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Matt: Hint Water Founder";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45037";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:32:"http://ma.tt/2015/05/hint-water/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:585:"<blockquote><p>When Kara Goldin started putting fruit in her water 10 years ago, she had no idea that she had stumbled upon a business idea that would eventually lead to the creation of a new category in the beverage industry, grow to a 40 million dollar company, and help her lose over 25 pounds in the process.</p></blockquote>\n<p>Cool interview with <a href="http://www.huffingtonpost.com/anjali-varma/mompreneur-spotlight-foun_b_7198902.html">Kara Goldin, the founder of Hint Water</a>, which I drink 3-4 of a day and is also an <a href="http://audrey.co/">Audrey</a> company.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 10 May 2015 03:42:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:29:"Post Status: The trojan Emoji";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=12600";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:40:"https://poststatus.com/the-trojan-emoji/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5500:"<p>Andrew Nacin just spoke at <a href="http://loopconf.io">Loopconf</a> about the nature of a critical software bug.</p>\n<p></p>\n<h3>No strict mode on WordPress databases</h3>\n<p>At a base level, the problems originated in that WordPress did not enable strict mode for MySQL. If <code>STRICT_ALL_TABLES</code> has been enabled, the security vulnerability that was addressed in WordPress 4.2 would not exist.</p>\n<p>Without strict mode, MySQL allows more flexible inputs, and doesn&#8217;t require the same level of precision in what it allows. For example, a long username would just truncate to the maximum allowed characters, versus be rejected.</p>\n<p>Since MySQL can do strange things without strict mode enabled, there are obscure but significant ways for hackers to take advantage.</p>\n<h3>Defining the scope of a vulnerability</h3>\n<p>A vulnerability was disclosed to the WordPress security team about two years ago. At its core, the method for forcing MySQL truncation was by using four-byte characters, and then using tricks to store nefarious code in the database.</p>\n<p>Nacin used an example of inserting two comments in the database with single quotes and attached four-byte characters. MySQL would truncate the four-byte characters on databases using UTF8 (and don&#8217;t allow four-byte characters), and a hacker could utilize the truncated comment (or any other field, really) to add a second comment to finish the exploitation.</p>\n<p>The initial vulnerability was fixed in 3.6.1. In 2014, an <a href="https://cedricvb.be/post/wordpress-stored-xss-vulnerability-4-1-2/">new disclosure came in from Cedric Van Bochhaven</a> to note that there was still a vulnerability under particular circumstances.</p>\n<p>After months of work and &#8220;tens of thousands of lines of code&#8221; for rewrites and tests, the team realized that they needed to check inputs to the database at a base level of WordPress.</p>\n<p>In WordPress 4.2, approximately 1,000 lines of code were inserted into wpdb.php under the guise of Emoji support, but were really for fixing this vulnerability.</p>\n<p><img class="aligncenter size-full wp-image-12604" src="https://poststatus.com/wp-content/uploads/2015/05/utf8mb4.png" alt="utf8mb4" width="751" height="520" /></p>\n<p>The original report identified three requirements for the site to be exposed:</p>\n<ol>\n<li>MySQL truncating everything after a four-byte character</li>\n<li>It&#8217;s not exposed when utf8mb4 is enabled</li>\n<li>It&#8217;s theme dependent</li>\n</ol>\n<p>It turned out that really only part of number one needed to be true. They discovered, &#8220;this could affect any two fields that would be rendered anywhere near each other.&#8221;</p>\n<p>Between 11 default database tables and hundreds of fields, basically all parts of WordPress were vulnerable, and core itself also &#8220;extensively&#8221; relied on non-strict mode functionality.</p>\n<p>Furthermore, they realized that even three-byte characters could cause truncation, if they aren&#8217;t valid upon insertion.</p>\n<p>So of the requirements from the original report, most were not actually required.</p>\n<p><img class="aligncenter size-full wp-image-12606" src="https://poststatus.com/wp-content/uploads/2015/05/utf8mb4-notreally.png" alt="utf8mb4-notreally" width="745" height="517" /></p>\n<blockquote><p>&#8220;We&#8217;re deeper and deeper and deeper into this hole, and we have no idea how to get out.&#8221;</p></blockquote>\n<p>The team went back to a discussion from the 3.6.1 vulnerability fix, that does what Nacin calls &#8220;preflight checks&#8221; that checks many layers of WordPress to ensure allowed data is being inserted.</p>\n<p>Checking allowed character sets was not only on the database and table level, but also on columns and fields. Furthermore, the client, the connection, and the server can have their own character sets.</p>\n<p>Nacin defines the method for checking as both using a scalpel and a sledgehammer.</p>\n<blockquote><p>We need this to work two different ways: with a scalpel via <code>update()</code>, <code>replace()</code>, <code>insert()</code>, and <code>delete()</code>, and with a sledgehammer via write queries via <code>query()</code>.</p></blockquote>\n<h3>Trojan Emoji</h3>\n<p>The code has been in trunk since January, months before the release of 4.2. But it was there under the guise of Emoji support, as &#8220;noone had any idea what it did because it was 1,000 lines of the database abstraction layer to just remove invalid characters.&#8221;</p>\n<p>Because of how opaque the vulnerability and the corresponding fix were, the team was able to spend a very long time working on and fixing the issue, all without exposing the vulnerability to the general public.</p>\n<p>When 23.9% of the internet uses WordPress, security becomes an even more enormous challenge than in other software. There was an easy fix for this all along: strict mode on MySQL.</p>\n<p>However, it would&#8217;ve broken &#8220;everything.&#8221; Alternatively, exposing a vulnerability to the public without a fix that doesn&#8217;t break websites makes the vulnerability that much more powerful. It takes a ridiculous effort for the WordPress core team and security team to ensure practical solutions to keep the WordPress software secure and reliable for millions of users.</p>\n<p>By the way, if you ever find a vulnerability in WordPress or you get really excited about problems like these, you can email security@wordpress.org to get involved.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 08 May 2015 20:18:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:27:"Matt: Where Does Weight Go?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45034";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"http://ma.tt/2015/05/where-does-weight-go/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:156:"<p><a href="http://mitchkirby.com/2015/04/21/where-does-weight-go/">When You Lose Weight, Where Does it Go?</a> I&#8217;ll be honest that I had no idea.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 08 May 2015 13:10:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:12;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"Matt: Slot Machine Tech";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45031";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:39:"http://ma.tt/2015/05/slot-machine-tech/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:469:"<p>The Verge: <a href="http://www.theverge.com/2015/5/6/8544303/casino-slot-machine-gambling-addiction-psychology-mobile-games">Slot machines perfected addictive gaming. Now, tech wants their tricks</a>. Includes information from one of my favorite authors <a href="http://www.nirandfar.com/">Nir Eyal</a>, who also <a href="http://wordpress.tv/2012/09/03/nir-eyal-automatic-customers-how-to-design-user-habits/">spoke at WordCamp San Francisco a few years ago</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 08 May 2015 06:55:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:67:"Post Status: How to create better, more accessible WordPress themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=12536";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:65:"https://poststatus.com/how-to-create-accessible-wordpress-themes/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:23972:"<p>This is not the ultimate guide for accessibility. You will not be an accessibility expert after reading this, not even a ninja! But I&#8217;d like to share what I have learned about accessibility in WordPress Themes. Hopefully that&#8217;ll help someone to build more accessible themes, and we can share ideas of how to make the web better place for all of us.</p>\n<p>I&#8217;ve learned most of my knowledge from <a href="https://www.joedolson.com/">Joe Dolson</a> and <a href="http://davidakennedy.com/">David A. Kennedy</a>. They both contribute to the <a href="http://make.wordpress.org/accessibility/">WordPress Accessibility Team</a> and have been kindly answering my questions on Github and Twitter. Our goal is to understand the basics of accessibility and how we can prepare our themes to receive the official <a href="https://wordpress.org/themes/tags/accessibility-ready/">accessibility-ready</a> tag.</p>\n<h3>What is accessibility and why should we care?</h3>\n<p>Web <strong>accessibility means that people can browse the web</strong>, with or without disabilities, using any device they might have. In this article, I mostly concentrate on people with disabilities including visual, auditory, physical, speech, cognitive, and neurological disabilities. We can improve our sites and help such people use, navigate, and interact with them.</p>\n<p><a href="https://twitter.com/viljamis">Viljami Salminen</a> talks about different input methods and performance in his article called <a href="http://viljamis.com/blog/2015/the-many-faces-of-the-web/">The Many Faces of the Web</a>.</p>\n<blockquote><p>On a bigger scale, I mean things like making our websites accessible to everyone. Making them work with different input methods like touch, mouse, keyboard or voice. Making them load and perform fast. Providing everyone access to this vast network of connected things. And if we don’t strive for all of this, what’s the point of working on the web?</p></blockquote>\n<p>If nothing else, you should care about the <a href="https://www.youtube.com/watch?v=cpbbuaIA3Ds">money</a>! <a href="https://twitter.com/brad_frost">Brad Frost</a> nails it in his article about <a href="http://bradfrost.com/blog/post/accessibility-and-low-powered-devices/">accessibility and low-powered devices</a>.</p>\n<blockquote><p>“Do you want to reach more customers?” the answer is always yes. When I ask them “Do you want your experience to load blazingly fast?” the answer is always yes. Both accessibility and performance are invisible aspects of an experience and should be considered even if they aren’t explicit goals of the project.</p>\n<p>There it is. Make efforts to make Web experiences accessible and performant; make money.</p></blockquote>\n<p>Let&#8217;s start with the <a href="https://make.wordpress.org/themes/handbook/review/accessibility/required/">required</a> parts of the puzzle.</p>\n<h3>.screen-reader-text for hiding text</h3>\n<p>Using <code>.screen-reader-text</code> is actually not required but I&#8217;ll use it in several examples. WordPress uses the CSS class <code>.screen-reader-text</code> to handle any HTML output that is <a href="https://make.wordpress.org/accessibility/2015/02/09/hiding-text-for-screen-readers-with-wordpress-core/">targeted at screen readers</a>. The purpose of screen-reader targeted text is to provide <strong>additional context</strong> for links, document structure, or form fields. This is helpful for whoever is using screen readers when browsing the web.</p>\n<p>Since WordPress 4.2, the <code>.screen-reader-text</code> class is used in front-end code also, not just back-end. For example <a href="https://codex.wordpress.org/Function_Reference/comments_popup_link">comments_popup_link()</a> can output something like this by default:</p>\n<p><code>4 Comments&lt;span class="screen-reader-text"&gt; on My article about accessibility&lt;/span&gt;</code></p>\n<p>Did you notice the <code>.screen-reader-text</code> class? The text <em>on My article about accessibility</em> is supposed to be hidden on screen but readable for screen readers. This provides additional information about what <em>4 Comments</em> stands for and which article we&#8217;re talking about.</p>\n<p>If you don&#8217;t have .screen-reader-text in your theme&#8217;s style.css that&#8217;s okay too. Then all users in this scenario would see the entire text (<em>4 Comments on My article about accessibility</em>), but nothing is broken. Naturally there is a plugin for <a href="https://wordpress.org/plugins/screen-reader-text-theme-support/">adding support for .screen-reader-text</a> as well.</p>\n<h4>Add .screen-reader-text in your theme&#8217;s style.css</h4>\n<p>The following snippet is the recommended method for adding a screen-reader class in your theme&#8217;s styles at the moment. You can also follow <a href="https://github.com/Automattic/_s">the Underscores theme</a> for this and other recommended methods.</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>You can style the <code>:focus</code> styles differently but this a solid start.</p>\n<h3>Headings and headings hierarchy structure</h3>\n<p>Headings are important way to navigate your site. They are the first step most screen reader users take when they start to navigate your site. And regular users can also browse the a website more easily when there are structured headings.</p>\n<p>But headings and heading hierarchy structure can be challenging, I certainly have had <a href="https://github.com/samikeijonen/kuorinka/issues/18">issues with headings</a> in my personal experience. Should we use just one H1 element on each page? Can there be more than one H1? What about other headings: H2, H3 and so on?</p>\n<p>With the acceptance of HTML5 standards, there can be more than one H1 on each page, but it&#8217;s important to be consistent with your headings hierarchy. Here is example of my blog page headings structure:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>And again for single posts:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>The problem is that the headings hierarchy breaks if a user enters H1 in the article text or mixes headings in the wrong way. Plugins that output markup may also mess with the hierarchy.</p>\n<p>Read more detail info about <a href="https://www.joedolson.com/2014/11/headings-hierarchy-problem/">heading hierarchy structure</a> and be consistent in your theme. And as a writer, think about the hierarchy structure of your theme and try not to break it. <img src="https://poststatus.com/wp-includes/images/smilies/simple-smile.png" alt=":)" class="wp-smiley" /></p>\n<h3>ARIA landmark roles</h3>\n<p>Aria landmark roles programmatically identify sections of a page. This helps navigate to various sections of a page for assistive technology users.</p>\n<p>These are the most common roles:</p>\n<ul>\n<li>header: <code>role="banner"</code></li>\n<li>main content: <code>role="main"</code></li>\n<li>sidebars: <code>role="complementary"</code></li>\n<li>footer: <code>role="contentinfo"</code></li>\n<li>search form: <code>role="search"</code></li>\n<li>navigation menus: <code>role="navigation"</code></li>\n</ul>\n<p>If the same role appears more than once on a page, you should provide an ARIA label for that role:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>Try not to use too many ARIA landmark roles. Otherwise it wouldn&#8217;t be helpful for screen reader users to navigate your site. Ten to fifteen roles is probably a good rule of thumb as a maximum limit.</p>\n<p>Here is a simple example for how your HTML structure could look with ARIA roles:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>An the screenshot from <a href="http://accessibility.oit.ncsu.edu/tools/aria-landmark-inspector/">Aria landmark inspector</a> website:</p>\n<p><a href="https://poststatus.com/wp-content/uploads/2015/05/aria-landmark.png"><img class="aligncenter size-large wp-image-12538" src="https://poststatus.com/wp-content/uploads/2015/05/aria-landmark-752x526.png" alt="Aria Landmarks" width="752" height="526" /></a></p>\n<h3>Link text</h3>\n<p>Imagine your blog archive using ten <em>Read More&#8230;</em> links. That&#8217;s not very helpful for screen reader users browsing trough your links. In general, avoid repetitive non-contextual text strings.</p>\n<h4>Using the_content() function</h4>\n<p>By default <a href="https://codex.wordpress.org/Function_Reference/the_content"><code>the_content()</code></a> function outputs <em>more&amp;hellip;</em> text when using &lt;!&#8211;more&#8211;&gt; in post content. Fortunately, you can change this output using the function&#8217;s first parameter: <code>$more_link_text</code>. It&#8217;s recommended to use the post title for additional context:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>This will output <code>Read more &lt;span class="screen-reader-text"&gt;My Article Name&lt;/span&gt;</code>, not just the repetitive <em>Read More</em>. Note that we&#8217;re using class <code>screen-reader-text</code> again, which means that the post title can be hidden (if theme supports it), but screen readers will still read it.</p>\n<h4>Using the_excerpt() function</h4>\n<p>By default <a href="https://codex.wordpress.org/Function_Reference/the_excerpt">the_excerpt()</a> function adds <code>[...]</code> to the end of the excerpt. We can replace with something similar to what we used in <code>the_content</code> example, using the <code>excerpt_more</code> filter.</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>That&#8217;s more like it. You can change the HTML structure, but you get the general idea how we added post title after the default text.</p>\n<h4>Descriptive link text</h4>\n<p>Try to be descriptive when using link text, and bare urls should not be used as link anchor text.</p>\n<p>Bad example:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>Good example:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<h3>Controls</h3>\n<p>Let links be links, buttons be buttons, divs be divs, spans be spans to ensure native keyboard accessibility and interaction with a screen reader. Article <a href="http://www.karlgroves.com/2013/05/14/links-are-not-buttons-neither-are-divs-and-spans/">links are not buttons. Neither are divs and spans</a>.</p>\n<p>All controls must also have text to indicate the nature of the control, but it too can be hidden inside the <code>.screen-reader-class</code>.</p>\n<p>For example, when toggling a menu, the control should be a button, not a link, div or span.</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>You can always style the button using CSS. Many theme developers add a font icon indicating the menu, like the commonly named &#8220;hamburger menu.&#8221; This is a bad way of adding the font icon:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>Font icons alone don&#8217;t have any meaning for screen readers. In general <a href="http://thomasbyttebier.be/blog/the-best-icon-is-a-text-label">the best icon is a text label</a>.</p>\n<p>Instead you could do this:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>Then add the icon font using a pseudo element, such as <code>#nav-toggle::before</code>.</p>\n<p>You can also use the icon font and <code>.screen-reader-text</code> together.</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>Sighted users will see only the hamburger icon, and screen reader users will now understand that this control is for the menu.</p>\n<h3>Keyboard navigation</h3>\n<p><a href="http://themeshaper.com/">On ThemeShaper</a>, there is fantastic article about <a href="http://themeshaper.com/2015/03/12/keyboard-accessibility/">keyboard accessibility</a>. In short, <strong>users must be able to navigate your site using only a keyboard</strong>. For example people who are blind or have motor disabilities use the keyboard almost exclusively.</p>\n<p>I&#8217;d like to challenge you to put your mouse away for a while and test your own website. Can you navigate through links, dropdown menu and form controls using the tab and shift + tab keys? Enter can be used to activate links, buttons, or other interactive elements.</p>\n<h4>:focus is important</h4>\n<p>Note that only links, buttons and form fields can be focused on by default. That&#8217;s why I keep noting that we should let links be links and buttons be buttons. Don&#8217;t try to replace them with divs or spans. Users should see and elements should have visual effects to notate their state when they navigate your site using a keyboard. This is where :focus steps in.</p>\n<p>This is a poor implementation:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>That disables outline style for all links! This is much better:</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>Now users have a visual effect &#8212; a dotted line around the link &#8212; on links when focused. You can style the thin dotted to something else, but do not disable it. Remember that you can of course style buttons using CSS also, for example to change the background on :focus.</p>\n<p>Make sure that colors are not your only method of conveying important information. That will help color blind people to see visual effects.</p>\n<h4>Dropdown menus and keyboard accessibility</h4>\n<p>Have you tried accessing your submenus in a dropdown menu using only keyboard? If you can&#8217;t successfully do so, let&#8217;s see what we can do about that, starting with the current <a href="https://make.wordpress.org/themes/handbook/review/accessibility/required/#keyboard-navigation">guidelines for navigation menus</a>.</p>\n<ul>\n<li>Fails: Dropdown navigation menus are hidden using <code>display:none;</code> and brought into view on <code>:hover</code></li>\n<li>Passes: Dropdown navigation menus are hidden using <code>position: absolute;</code> and brought into view on <code>:hover </code>and <code>:focus</code>, and are navigable using the <code>tab</code> key</li>\n<li>Better: Dropdown navigation menus are hidden using position: absolute; and brought into view on <code>:hover</code>, <code>:focus</code>, and are navigable using either the <code>tab</code> key or by using the keyboard arrow keys.</li>\n</ul>\n<p>Once again, the <a href="http://underscores.me/">Underscores</a> theme has a good example of dropdown menu markup which is navigable using the <code>tab</code> key. I&#8217;ll hope there will be support for arrow keys in near future. I personally use <a href="http://responsive-nav.com/">Responsive Nav</a> as a starting point for accessible, responsive menus.</p>\n<p>We need some Javascript magic for enabling keyboard support for dropdown menus. For reference, checkout this <a href="https://github.com/Automattic/_s/blob/master/js/navigation.js">navigation.js file</a>. This is the basic idea:</p>\n<ul>\n<li>Each time a menu link is focused or blurred, set or remove the <code>.focus</code> class on the menu link. This is done with the <code>toggleFocus()</code> function.</li>\n<li>Add class <code>.focus</code> your stylesheet, where you have <code>:hover</code> styles for the menu.</li>\n<li>You can now navigate your menu and submenus using the <code>tab</code> and <code>Shift + tab</code> key!</li>\n</ul>\n<p>There are some other aspects we should consider for more accessible dropdown menus:</p>\n<ul>\n<li>Use ARIA markup like aria-haspopup=&#8221;true&#8221; in menu items that have submenus.</li>\n<li>What about touch devices? Have you tried accessing submenus using iPad when menu is in &#8220;Desktop&#8221; mode? I believe touch support is also coming to the Underscores theme.</li>\n</ul>\n<p>There could be another in-depth article for creating accessible, responsive menus so I&#8217;ll move on.</p>\n<h3>Contrasts</h3>\n<p>Color contrast is something we might have to compromise on in our design. We need to provide enough contrast between text and background colors so that it can be read by people with moderately low vision. There are many beautiful themes out there that use for example light grey colors but might not pass the <a href="https://make.wordpress.org/themes/handbook/review/accessibility/required/#contrasts">guideline for color contrast</a>.</p>\n<blockquote><p>Theme authors MUST ensure that all background/foreground color contrasts for plain content text are within the level AA contrast ratio (4.5:1) specified in the Web Content Accessibility Guidelines (WCAG) 2.0 for color luminosity.</p></blockquote>\n<p>I test color contrast using Joe Dolson&#8217;s <a href="https://www.joedolson.com/tools/color-contrast.php">tester tool</a>. Accessibility doesn&#8217;t make your site ugly or boring, that&#8217;s always you. <img src="https://poststatus.com/wp-includes/images/smilies/simple-smile.png" alt=":)" class="wp-smiley" /> But it does set some preconditions we need to follow. Aaron Jorbin also has a great <a href="https://wordpress.tv/2014/07/01/aaron-jorbin-color-theory-for-web-developers/">talk on color theory and accessibility</a> from WordCamp Chicago 2014.</p>\n<h3>Skip links</h3>\n<p>A website&#8217;s primary content is usually not at the top of the page. There can be dropdown menus, header sidebars, search forms or other information before the main content. For keyboard and screen reader users it&#8217;s annoying to navigate this extra content over and over again before arriving at the main content. That&#8217;s why themes must have skip links, which help to navigate directly to content. The skip link is usually added in the header.php file after the body or first div tag.</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>Make sure the link is one of the first items on the page and visible when keyboard focus moves to the link. We already did that when we added .screen-reader-text class in our stylesheet.</p>\n<p>Also move focus to the main content area of the page when skip link is activated. I believe there is still a bug in WebKit-based browsers that prevents focus being moved, but once again, <a href="https://github.com/Automattic/_s/blob/master/js/skip-link-focus-fix.js">the Underscores theme has you covered</a> offering a good example.</p>\n<h3>Forms</h3>\n<p>WordPress default comment and search forms are accessible-ready, but be careful if you tweak them. I have made mistakes doing so in the past.</p>\n<p>Hiding the search button using <code>.search-submit { display: none; }</code>. <strong>Do not use this CSS if you want the content to be read by a screen reader.</strong></p>\n<p>A better option is the filter <a href="https://codex.wordpress.org/Function_Reference/get_search_form">get_search_form</a>, and add our now familiar <code>.screen-reader-text</code> class to the search form&#8217;s submit button.</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>If you use a custom <code>searchform.php</code> in your theme, remember to keep appropriate field labels and do not use only a font icon as the submit button.</p>\n<a href="https://gist.github.com/bee3e380c614542776de" target="_blank"><em>View this code snippet on GitHub.</em></a>\n<p>In short from <a href="https://make.wordpress.org/themes/handbook/review/accessibility/required/#forms">the guidelines</a>:</p>\n<blockquote>\n<ul>\n<li>Use form controls that have explicitly associated <code>&lt;label&gt;</code> elements.</li>\n<li>Create feedback mechanisms (such as via AJAX) that expose responses to screen readers. Look at techniques with ARIA for further information.</li>\n</ul>\n</blockquote>\n<p>Also keep an eye on a <a href="https://github.com/wpaccessibility/a11ythemepatterns">collection of patterns</a> for creating accessible-ready WordPress themes. Like <a href="https://github.com/wpaccessibility/a11ythemepatterns/tree/master/comment-form-with-js-aria">an accessible comment</a> form powered by JavaScript and ARIA.</p>\n<h3>Images and alternative text</h3>\n<p>As a user I&#8217;ve failed to add alternative (alt attribute) text to my content images, at least good ones. I promise to improve! You see, blind people of course can&#8217;t see your content images. Computers and screen readers can&#8217;t determine what the image presents. That&#8217;s why there is alt attribute and <a href="https://make.wordpress.org/themes/handbook/review/accessibility/required/#images">guidelines for images</a>.</p>\n<ul>\n<li>If there are images in template markup, like features images, they must utilize the alt attribute. Or provide the end user to enter alt text.</li>\n<li>All decorative images should be added via CSS versus inline. Examples of decorative images are  lines for style or background images.</li>\n<li>Note that sometimes an empty alt=&#8221;&#8221; is <a href="http://webaim.org/techniques/alttext/">the best choice</a>.</li>\n</ul>\n<h3>Media</h3>\n<p>Sliders and carousels must not auto start by default. The same goes for videos and audios. This is mostly plugin territory, but it&#8217;s good to mention, especially as the broader web is more and more often auto-playing this content.</p>\n<h3>Not allowed</h3>\n<p>There are couple of things that are <a href="https://make.wordpress.org/themes/handbook/review/accessibility/required/#not-allowed">not allowed</a>.</p>\n<blockquote>\n<ul>\n<li>Any positive tabindex attribute. Negative or zero value tabindex is allowed in specific circumstances (assessed on a case-by-case basis).</li>\n<li>The inclusion of the accesskey attribute.</li>\n<li>Spawning new windows or tabs without warning the user.</li>\n</ul>\n</blockquote>\n<h3>Build accessibility-ready themes</h3>\n<p>We have gone through the <a href="https://make.wordpress.org/themes/handbook/review/accessibility/required/">required guidelines</a> for getting the official <a href="https://wordpress.org/themes/tags/accessibility-ready/">accessibility-ready</a> tag in our themes when we submit them to the WordPress theme repository. It wasn&#8217;t that bad was it!</p>\n<p>I challenge you to build an accessibility-ready theme when you start your next project. Or look into your current site and start with small steps, like adding better support for keyboard users. I hope this article will help you do that. Let me know in the comments if there are mistakes in the article, you have questions, or you have ideas for part two.</p>\n<p>It doesn&#8217;t matter are you building themes for customers, commercial themes for marketplaces or free themes for WordPress.org. We can all improve our skills and create more accessible websites.</p>\n<hr />\n<p><em>About the author: <a href="https://poststatus.com/profiles/sami-keijonen/">Sami Keijonen</a> is a teacher who likes to learn about the web, WordPress, and life. He runs <a href="https://foxland.fi/">Foxland Themes</a>.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 May 2015 18:59:54 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sami Keijonen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:14;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:72:"WPTavern: CampPress: A 2-3 Day Social Experience for Geeks and Creatives";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43466";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:81:"http://wptavern.com/camppress-a-2-3-day-social-experience-for-geeks-and-creatives";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2591:"<p>I attend WordCamps on a regular basis and have often joked with attendees as well as organizers that there should be a WordCamp where people camp out. GoDaddy&#8217;s WordPress evangelist, Mendel Kurland, is taking it upon himself to turn the joke into reality. He&#8217;s in the preliminary stage of <a href="https://mendel.me/articles/news/the-hunt-for-a-camppress-venue-is-officially-on/">planning CampPress</a>.</p>\n<p>CampPress is a 2-3 day social experience for geeks and creatives to disconnect from technology to focus on community and creativity. The event is an adult geek summer camp infused with <a href="http://burningman.org/culture/philosophical-center/10-principles/" target="_blank">burning man values</a> and is not affiliated with GoDaddy. I asked Kurland what his inspiration is to organize such an event.</p>\n<p>&#8220;As creative professionals, sometimes we forget to disconnect. CampPress is inspired by the simpler lives we lived as kids, where social interactions and creativity were the hallmarks of great growth experiences. Traditional conferences are incredible at transferring knowledge and skills and creating personal connections. CampPress is about deepening connections between participants and strengthening bonds that encourage collaboration within the community.&#8221;</p>\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/CabinCampCampbell.jpg"><img class="size-full wp-image-43469" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/CabinCampCampbell.jpg?resize=1024%2C683" alt="Camp Campbell is a Possible Venue" /></a>Camp Campbell is a Possible Venue\n<p>Some items will be provided, including, food staples for breakfast, lunch, and dinner along with a preparation area, space to camp, a cabin or RV hookup depending on the final location, and ice for beer. CampPress will also have a Pit of Creativity. Information on what the pit of creativity is for will be published on the official CampPress site at a later date.</p>\n<p>If you&#8217;re interested in attending, volunteering, or simply want to stay updated on the event&#8217;s progress, <a href="http://eepurl.com/blHmE9">sign up</a> to the updates list. Based on initial reactions in the comments, people are excited to see such an event take place.</p>\n<p>I would love to camp out for a few days with members of the WordPress community and disconnect from technology at the same time. Let us know in the comments if you&#8217;re interested in attending such an event. Also, give us your suggestions for venues you think would be a good fit for CampPress.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 May 2015 16:59:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:15;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"WPTavern: TGM Plugin Activation Library Publishes Roadmap for Version 3.0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43432";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:83:"http://wptavern.com/tgm-plugin-activation-library-publishes-roadmap-for-version-3-0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5704:"<a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/domino.jpg"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/domino.jpg?resize=1020%2C484" alt="photo credit: domino - (license)" class="size-full wp-image-43493" /></a>photo credit: <a href="http://www.flickr.com/photos/31059504@N08/6803420982">domino</a> &#8211; <a href="https://creativecommons.org/licenses/by/2.0/">(license)</a>\n<p>This week contributors on the <a href="http://tgmpluginactivation.com/" target="_blank">TGM Plugin Activation</a> (TGMPA) library published a roadmap for the future of the project. TGMPA is widely used by WordPress developers to require and recommend plugins for themes (and other plugins). The library is recommended by Themeforest, CodeCanyon, and the WordPress.org Theme Review Team as an alternative to bundling everything in one theme/plugin.</p>\n<p><a href="https://gamajo.com/" target="_blank">Gary Jones</a> is leading the upcoming 2.5 release, expected in May, with help from fellow lead developer <a href="http://twitter.com/jrf_nl" target="_blank">Juliette Reinders Folmer</a>, to whom he credits most of the recent activity on the project. This release will add support for installing from a GitHub repo source, separate menu items out from under the Appearance menu, add Travis CI support, improve accessibility, and fix a number of bugs.</p>\n<h3>The Future of the TGM Plugin Activation Library</h3>\n<p>The project&#8217;s contributors are also planning ahead for this summer&#8217;s 3.0 release, which Folmer will lead. This release will be a major turning point for TGMPA and will essentially constitute a complete rewrite.</p>\n<p>The <a href="https://github.com/TGMPA/TGM-Plugin-Activation/issues/394" target="_blank">roadmap for 3.0</a> includes several ambitious items that will likely affect the way developers integrate TGMPA into their projects:</p>\n<ul>\n<li>Multisite compatibility</li>\n<li>Fix conflicting UI messages for usage in themes / plugins</li>\n<li>Improved UI by having the admin page always in the same location</li>\n<li>Updatability of TGMPA independently of the plugin/theme which ships it</li>\n<li>Show dependencies more clearly</li>\n</ul>\n<p>This plan includes an architectural change that would allow for the integration of the <a href="https://wordpress.org/plugins/plugin-dependencies/" target="_blank">Plugin Dependencies</a> (PD) plugin to provide UI for dependency management and cascading deactivation if dependencies are not met.</p>\n<p>According to Jones, the eventual goal is to turn TGMPA into a plugin that can be added to the WordPress.org repository for easier updating:</p>\n<blockquote><p>Some of the logic in the rewrite will be handled by the Plugin Dependencies plugin, and TGMPA itself will be turned into a plugin and added to the WPORG repo so that it can be updated automatically. The TGMPA library will then consist of a bootstrap file, the TGMPA plugin (as a zip) and the PD plugin (as a zip). The bootstrap file will then check if the TGMPA + PD plugins are installed, and if not, install them from the embedded zips.</p></blockquote>\n<p>TGMPA contributors are currently in discussion with representatives from WordPress.org about the possibility of allowing their planned plugin in the official directory. As the plugin has not yet been produced and submitted, it&#8217;s still too early to know the outcome of the decision.</p>\n<p>&#8220;If we can&#8217;t go onto the WordPress.org repo, then we&#8217;ll be looking at simply hosting the plugin version on GitHub, and use some (if needed) of the GitHub Updater plugin (or similar) code within the bootstrap file to pull the latest tag from GitHub instead,&#8221; Jones said.</p>\n<p>One of the main focuses for version 3.0 is to allow different plugins and themes to use TGMPA without the concern of compatibilities resulting from plugin A including 2.4.1, for example, and plugin B including 2.5.0.</p>\n<p>&#8220;The v3 setup should also be able to handle instances of v2 gracefully, and the v2 branch may have a 2.6 release to make the logic for that easier,&#8221; Jones said.</p>\n<p>After version 3.0 is released, the project will contain multiple repositories &#8211; one for the standard plugin, and one that uses Grunt to pull in files from the plugin repository and zips them up next to the bootstrap file. In anticipation of these changes, contributors have moved the current repository into a new GitHub organization at: <a href="https://github.com/TGMPA" target="_blank">https://github.com/TGMPA</a>.</p>\n<p>As TGMPA does not currently track its usage, it&#8217;s difficult to nail down exact numbers for how many theme/plugin developers these changes will impact.</p>\n<p>&#8220;I have no idea what sort of numbers of products this entails,&#8221; Jones said. &#8220;But there is a non-trivial amount of usage that requires us to step up the game in order to provide the exceptional functionality other developers can rely on.&#8221;</p>\n<p>TGMPA is a critical tool that many developers in the WordPress ecosystem depend on for managing plugin requirements and recommendations. As theme development continues to move in the direction of separating theme and plugin functionality, TGMPA will play an important role in serving developers who want to structure their projects according to WordPress best practices.</p>\n<p>Getting the new TGMPA plugin included in the WordPress.org plugin directory would be a big win for the project, as it would allow users to update more easily in the future. You can <a href="https://twitter.com/tgmpa" target="_blank">follow TGMPA on Twitter</a> for all the latest news as the team moves into development for version 3.0.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 May 2015 16:35:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:16;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:52:"WPTavern: BuddyPress 2.3 Beta 1 is Ready for Testing";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43440";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:62:"http://wptavern.com/buddypress-2-3-beta-1-is-ready-for-testing";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2493:"<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2014/03/bp-featured.png"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2014/03/bp-featured.png?resize=800%2C390" alt="bp-featured" class="aligncenter size-full wp-image-18726" /></a></p>\n<p>BuddyPress <a href="https://buddypress.org/2015/05/buddypress-2-3-0-beta-1/" target="_blank">2.3 beta 1</a> is now available. Project lead John James Jacoby encouraged site administrators and BP plugin/theme developers to jump in and test the new features.</p>\n<p>One of the highlights in the upcoming release is the new <a href="http://wptavern.com/buddypress-2-3-will-improve-avatar-uploads-with-the-new-bp-attachments-api" target="_blank">Attachments API</a>, which makes it possible for developers to create components that manage uploads. You can see this API in action alongside the newly improved <a href="https://buddypress.trac.wordpress.org/ticket/6290/" target="_blank">avatar upload UI</a>, revamped to include drag-and-drop upload and support for device cameras.</p>\n<p>This release will also ship with <a href="http://wptavern.com/buddypress-2-3-will-introduce-companion-stylesheets-for-wordpress-default-themes" target="_blank">companion stylesheets for WordPress&#8217; latest default themes</a>, Twenty Fifteen and Twenty Fourteen. These stylesheets provide a broad sweep on BP elements to harmonize the appearance of the plugin with the default themes and could use more testing and feedback from the community.</p>\n<p>Jacoby noted a few other important items to test in 2.3 beta 1, including:</p>\n<ul>\n<li><a href="https://buddypress.trac.wordpress.org/ticket/6177/" target="_blank">Blog Post Activity</a> generates better looking excerpts when posts contain images or other embedded media content</li>\n<li><a href="https://buddypress.trac.wordpress.org/ticket/6331/" target="_blank">Star Private Messages</a> allows for improved marking of important inbox messages</li>\n<li>The Member Types API now supports <a href="https://buddypress.trac.wordpress.org/ticket/6286" target="_blank">member-type-specific directories</a></li>\n<li>Continued object and query cache enhancements</li>\n</ul>\n<p>BuddyPress developers and community managers have plenty of time to test their themes and plugins against the upcoming 2.3 release. A release candidate is scheduled for the week of May 12th. The official release is expected to drop May 26th, shortly before the BuddyCamp that will take place at WordCamp Miami 2015.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 May 2015 15:31:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:17;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"WPTavern: WPWeekly Episode 191 – Proven Guilty by a Washing Machine";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:44:"http://wptavern.com?p=43443&preview_id=43443";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:75:"http://wptavern.com/wpweekly-episode-191-proven-guilty-by-a-washing-machine";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2901:"<p>On this episode of WordPress Weekly, <a href="http://marcuscouch.com/">Marcus Couch</a> and I discuss the news of the week. We inform you of the recent security vulnerability discovered in Jetpack and the Twenty Fifteen theme. We also discuss a new crowdfunding campaign to create a server manager built on top of WordPress called HostPress.</p>\n<p>I shared a personal story of a bad habit I&#8217;ve developed in the last two years that&#8217;s decreased my reading comprehension. Last but not least, Marcus tells a story from a conference he recently attended where the technology inside of a washing machine contained the evidence needed to convict a murderer.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="http://wptavern.com/xss-vulnerability-in-jetpack-and-the-twenty-fifteen-default-theme-affects-millions-of-wordpress-users">XSS Vulnerability in Jetpack and the Twenty Fifteen Default Theme Affects Millions of WordPress Users</a><br />\n<a href="http://wptavern.com/wordpress-com-suspends-theme-submissions-from-new-sellers">WordPress.com Suspends Theme Submissions from New Sellers</a><br />\n<a href="http://wptavern.com/dan-griffiths-launches-175k-crowdfunding-campaign-to-build-hostpress">Dan Griffiths Launches $175K Crowdfunding Campaign to Build HostPress</a><br />\n<a href="http://wptavern.com/new-plugin-reorders-the-wordpress-admin-menu-using-drag-and-drop">New Plugin Reorders the WordPress Admin Menu Using Drag-and-Drop</a><br />\n<a href="https://jeffc.wordpress.com/2015/05/05/why-am-i-in-a-hurry-to-do-everything/">Why am I in a Hurry to do Everything?</a></p>\n<h2>Plugins Picked By Marcus:</h2>\n<p><a href="https://wordpress.org/plugins/hamburger-menu/">Hamburger Menu</a> is a side menu that you can add to your site that will be viewed on mobile devices or you can use it to completely replace the main menu on a site.</p>\n<p><a href="https://wordpress.org/plugins/rest-console-embed/">REST Console embed</a> provides a shortcode to embed a REST API console into a page or post. It&#8217;s based on Automattic&#8217;s WordPress.com console.</p>\n<p><a href="https://wordpress.org/plugins/plugin-auditor/">Plugin Auditor</a> records details of who installed and activated each plugin on your website and why.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, May 6th 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 #191:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 May 2015 14:45:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"Matt: Decades are Short";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45029";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:39:"http://ma.tt/2015/05/decades-are-short/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:352:"<p>Sam Altman of YCombinator wrote a great post on the occasion of his thirtieth birthday, <a href="http://blog.samaltman.com/the-days-are-long-but-the-decades-are-short">The days are long but the decades are short</a>. There&#8217;s a lot of subtlety and nuance in each point, so even if you&#8217;ve read it already it&#8217;s worth another pass.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 May 2015 04:05:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:19;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:111:"WPTavern: XSS Vulnerability in Jetpack and the Twenty Fifteen Default Theme Affects Millions of WordPress Users";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43415";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:121:"http://wptavern.com/xss-vulnerability-in-jetpack-and-the-twenty-fifteen-default-theme-affects-millions-of-wordpress-users";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3045:"<p><a href="https://wordpress.org/plugins/jetpack/changelog/">Jetpack</a> and the <a href="https://wordpress.org/themes/twentyfifteen/">Twenty Fifteen</a> default theme have been updated after a DOM-based Cross-Site Scripting (XSS) vulnerability was discovered. <a href="https://blog.sucuri.net/2015/05/jetpack-and-twentyfifteen-vulnerable-to-dom-based-xss-millions-of-wordpress-websites-affected-millions-of-wordpress-websites-affected.html">According to Sucuri</a>, any plugin or theme that uses <a href="http://genericons.com/">Genericons</a> is vulnerable due to an insecure file included within the package.</p>\n<p>Genericons ships with a file called example.html which is vulnerable to attack from the Document Object Model level or DOM for short. The <a href="https://www.owasp.org/index.php/Main_Page">Open Web Application Security Project</a> defines a DOM based attack as:</p>\n<blockquote><p>DOM Based <a class="mw-redirect" title="XSS" href="https://www.owasp.org/index.php/XSS"> XSS</a> (or as it is called in some texts, &#8216;type-0 XSS&#8217;) is an XSS attack wherein the attack payload is executed as a result of modifying the DOM &#8216;environment&#8217; in the victim’s browser used by the original client side script, so that the client side code runs in an &#8216;unexpected&#8217; manner. That is, the page itself (the HTTP response that is) does not change, but the client side code contained in the page executes differently due to the malicious modifications that have occurred in the DOM environment.</p></blockquote>\n<p>The payload for these types of attacks is executed directly in the browser. Even Sucuri&#8217;s website firewall is unable to block the attack since it never gets the chance to see it. The company however, has virtually patched the vulnerability.</p>\n<p>Sucuri worked with a number of hosting providers to identify and remove the example.html file from their servers. If you use the following webhosts, you should already be patched as of a week ago.</p>\n<ul>\n<li>GoDaddy</li>\n<li>HostPapa</li>\n<li>DreamHost</li>\n<li>ClickHost</li>\n<li>InMotion</li>\n<li>WPEngine</li>\n<li>Pagely</li>\n<li>Pressable</li>\n<li>Websynthesis</li>\n<li>Site5</li>\n<li>SiteGround</li>\n</ul>\n<p>According to Sucuri, the example.html file was used for debugging and testing purposes but was mistakenly left inside the directory after the project was packaged for production environments. This simple oversight has placed millions of sites at risk as Twenty Fifteen is a default theme that ships with WordPress.</p>\n<p>You should update the Twenty Fifteen theme and Jetpack regardless of which webhost you&#8217;re using. You should also remain vigilant and keep an eye out for additional plugin and theme updates. If possible, manually remove example.html from within the Genericons directory.</p>\n<p><em><strong>Update</strong></em></p>\n<p>WordPress 4.2.2 <a href="https://wordpress.org/news/2015/05/wordpress-4-2-2/">is available</a> as a security update that addresses the Genericons issue and contains bug fixes.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 06 May 2015 18:56:17 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:20;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:59:"WPTavern: Andrew Nacin on Challenging WordPress Assumptions";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42281";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"http://wptavern.com/andrew-nacin-on-challenging-wordpress-assumptions";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1162:"<p>WordPress lead developer <a href="http://nacin.com/" target="_blank">Andrew Nacin</a> spoke at the <a href="http://world2014.phparch.com/" target="_blank">php[world] 2014</a> conference on &#8220;Challenging Your WordPress Assumptions from 2009.&#8221; The video was recently published on YouTube and provides an excellent overview of the major ways WordPress has changed over the past six years.</p>\n<p>Nacin explores common assumptions, such as &#8220;WordPress is insecure,&#8221; &#8220;WordPress doesn&#8217;t scale,&#8221; and &#8220;WordPress is not OOP,&#8221; among others. Some of these assumptions are false, some are true, some used to be true and others are partially true. If you&#8217;re a PHP developer who is new to WordPress or curious about how it&#8217;s changed over the years, this presentation will give you a quick 30 minute overview.</p>\n<p>Check out the video embedded below to learn more about WordPress&#8217; philosophy for building user-centered software, its commitment to maintaining backwards compatibility, and how major publishers and companies are using it in innovative ways.</p>\n<p><span class="embed-youtube"></span></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 06 May 2015 18:15:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:21;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:51:"WPTavern: Inside BuddyBoss with Michael Eisenwasser";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43380";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:61:"http://wptavern.com/inside-buddyboss-with-michael-eisenwasser";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8724:"<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/buddyboss.jpg"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/buddyboss.jpg?resize=1025%2C453" alt="buddyboss" class="aligncenter size-full wp-image-43387" /></a></p>\n<p>Over the past couple years, <a href="http://www.buddyboss.com/" target="_blank">BuddyBoss</a> has emerged as a leader in the <a href="https://buddypress.org/" target="_blank">BuddyPress</a> products marketplace. Founder Michael Eisenwasser launched the business in 2010 after discovering BuddyPress while building an international job site to help online workers find employment.</p>\n<p>&#8220;BuddyPress blew me away,&#8221; Eisenwasser said. &#8220;It allowed for a sophisticated and fully customizable membership site while still benefiting from the WordPress ecosystem. We launched our online community almost overnight, and a year later 30,000 people were logging in every day and hiring each other.&#8221;</p>\n<p>BuddyBoss entered the BuddyPress ecosystem while it was still in its infancy. Eisenwasser saw an opportunity to help other entrepreneurs launch communities by creating products that solved common problems. In addition to the products, his team also offers development for custom requests.</p>\n<p>&#8220;I’ve been focusing on BuddyPress for so long now that I sometimes forget you can run WordPress without it,&#8221; he said.</p>\n<h3>Growing a Business in a Small Niche</h3>\n<p>As BuddyBoss products are targeted towards a small niche market, hiring has posed a continual challenge for Eisenwasser.</p>\n<p>&#8220;A company is only as good as its employees, and our biggest challenge has always been finding the right people to hire,&#8221; he said. &#8220;We need talented people who can move the company forward, knowing that we’re in a niche market and skilled developers who understand BuddyPress are harder to find.</p>\n<p>&#8220;It’s taken us many years to put together our current staff, and even now I still spend a considerable amount of time on hiring and training.&#8221;</p>\n<p>The BudddyBoss team is now up to 14 people who collaborate on design, development, support, and marketing. They currently serve several thousand customers, thanks to tremendous growth over the past couple of years.</p>\n<p>&#8220;Our revenue is 12.5 times larger today than it was three years ago, and most of that growth has been in the past year,&#8221; Eisenwasser said.</p>\n<p>&#8220;In the past 6 months, product revenue has grown 5 times larger due to improved product offerings, word of mouth from our customers, and better marketing. When I speak of products, I am combining themes and extensions together.</p>\n<p>&#8220;Currently we have several thousand paying customers, with an average checkout order of $130. Many customers purchase two or three products in one order, as we design our themes and plugins to work together for a unified experience,&#8221; he said.</p>\n<p>Despite the success of BuddyBoss&#8217; themes and plugins, the company&#8217;s time is still divided 50/50 between product support and custom client work.</p>\n<p>&#8220;Custom development generates an important part of our revenue, and our product revenue is quickly catching up,&#8221; Eisenwasser said.</p>\n<p>&#8220;We actually have two teams, each equipped for development, support and maintenance. I personally manage our product team, while my business partner Tom Chedd manages our client team.</p>\n<p>&#8220;Many of our clients start as customers, and so when we develop products we’re always thinking about how our clients might use them. I think this has contributed to better products, because we actually use what we build,&#8221; he said.</p>\n<h3>Focused, Intentional Product Growth</h3>\n<p>In the early days of BuddyBoss, Eisenwasser took a job managing SongLyrics.com. Although he learned some valuable skills from the position, theme development at BuddyBoss was slow for the first few years.</p>\n<p>As product revenue has grown, BuddyBoss is looking to invest in adding more offerings to the store.</p>\n<p>&#8220;We’ve been working hard on assembling a team of talented developers who can help us build more products, however we’d rather spend a couple of months working on a theme than pushing out a bunch of themes fast,&#8221; he said.</p>\n<p>Instead of pumping up the BuddyBoss store with a proliferation of products, Eisenwasser and his team have intentionally kept the number of offerings on the smaller side. For years, their primary product was the original <a href="http://www.buddyboss.com/product/buddyboss-theme/" target="_blank">BuddyBoss</a> theme before adding the new <a href="http://www.buddyboss.com/product/boss-theme/" target="_blank">Boss</a> theme this year. Branching out into BuddyPress <a href="http://www.buddyboss.com/plugins/" target="_blank">plugins</a> was also a more recent development.</p>\n<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/boss-1100x760.jpg"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/boss-1100x760.jpg?resize=500%2C345" alt="boss-1100x760" class="aligncenter size-large wp-image-43398" /></a></p>\n<p>&#8220;Designing for social networks requires a lot of thought, and we take our time considering every aspect,&#8221; Eisenwasser said.</p>\n<p>&#8220;Our customers give us all kinds of feedback about what they want, and there are many more themes coming down the road based on what we’ve learned.&#8221;</p>\n<h3>Current Landscape of the BuddyPress Theme and Plugin Market</h3>\n<p>Despite the fact that BuddyPress is now an eight-year-old plugin with a solid community of contributors supporting it, the marketplace for BP themes and plugins remains relatively small. Eisenwasser does not believe that the market is large enough to sustain a full-time theme business, but his team is working to expand its audience outside of the traditional WordPress/BuddyPress community.</p>\n<blockquote><p>BuddyPress has an active developer community and it’s been growing every year. Even if there are not enough people building on BuddyPress to sustain a larger theme business today, we can help change that. </p>\n<p>By building quality products we can improve the usability and perception of BuddyPress and encourage other people to come and join the community. <strong>There are many people building social networks every day &#8211; the question is whether or not they choose to build them within the BuddyPress ecosystem.</strong></p></blockquote>\n<p>As BuddyPress core cannot encompass all the functionality required by the many varied social networks people want to build, part of making BuddyPress more appealing is providing third-party add-ons that are compelling and reliable. BuddyBoss has started carving out a name for itself with useful plugins that extend the platform to support <a href="http://www.buddyboss.com/product/buddyboss-media/" target="_blank">media uploads</a>, <a href="http://www.buddyboss.com/product/buddypress-edit-activity/" target="_blank">activity editing</a>, <a href="http://www.buddyboss.com/product/buddypress-global-search/" target="_blank">global search</a>, and a Facebook-like <a href="http://www.buddyboss.com/product/buddyboss-wall/" target="_blank">wall</a> functionality.</p>\n<p>&#8220;We always envisioned ourselves building both themes and plugins,&#8221; Eisenwasser said. &#8220;I don’t really see a distinction. To me, we’re building solutions.</p>\n<p>&#8220;Layout issues are best solved within themes, and functionality issues are best solved by plugins. All of our products are designed to work together seamlessly, and work great with other themes and plugins too.&#8221;</p>\n<p>In the future, Eisenwasser said that BuddyBoss may open up its marketplace to third-party developers, but his primary concern is to maintain the same level of quality that customers have come to expect from BuddyBoss products.</p>\n<p>&#8220;For now, we are focusing on the theme market and bringing value / creating solutions for different niches,&#8221; he said. &#8220;We plan on evolving with the market as we grow. This could eventually require integrating with other platforms and putting more focus on other types of devices.&#8221;</p>\n<p>While there are a handful of successful BuddyPress themes on Themeforest, BuddyBoss is arguably the most dominant independent BuddyPress theme development shop at the moment. Eisenwasser&#8217;s experience indicates that the landscape of the BuddyPress product market is not yet wide open. Businesses looking to push into this space will need to produce top quality products while simultaneously tilling the soil to expand the WordPress + BuddyPress market in general.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 06 May 2015 17:30:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:22;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:22:"Matt: Untold Silk Road";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45025";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"http://ma.tt/2015/05/untold-silk-road/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:521:"<p>This <a href="http://www.wired.com/2015/04/silk-road-1/">Untold Story of Silk Road</a> is pretty amazing writing, a gripping story regardless of the genre (non-fiction, in this case). I can&#8217;t wait for the next chapter to come out on May 14. Also when reading about Ross, <a href="http://www.wired.com/2015/02/ross-ulbricht-didnt-create-silk-roads-dread-pirate-roberts-guy/">it&#8217;s interesting to keep in mind Vanity Jones who was in many ways the brains behind the operation</a>, and also undiscovered.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 06 May 2015 06:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:79:"WPTavern: Dan Griffiths Launches $175K Crowdfunding Campaign to Build HostPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43256";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:88:"http://wptavern.com/dan-griffiths-launches-175k-crowdfunding-campaign-to-build-hostpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5350:"<p>When it comes to hosting, there are predominately two choices to manage your account or server; <a href="http://www.odin.com/products/plesk/">Plesk</a> and <a href="http://cpanel.com/">cPanel</a>. Dan Griffiths wants to shake things up by adding a third choice with <a href="https://www.indiegogo.com/projects/hostpress-redefining-web-hosting-control-panels">HostPress</a>. HostPress is an open-source, extensible server control panel built on top of WordPress.</p>\n<a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/HostPressLogo.png"><img class="wp-image-43267 size-large" src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/HostPressLogo.png?resize=500%2C333" alt="HostPress Logo" /></a>HostPress Logo\n<p>Griffiths has started an <a href="https://www.indiegogo.com/projects/hostpress-redefining-web-hosting-control-panels">Indiegogo crowdfunding campaign</a> to generate $175k. The money will be used to cover personal expenses, take care of his son, and cover the server fees and salary of an experienced server administrator for one year. cPanel and Plesk have several shortcomings, including:</p>\n<ul>\n<li>Minimum requirements</li>\n<li>Extensibility</li>\n<li>Ease of branding</li>\n<li>Sustainability</li>\n</ul>\n<p>HostPress will have a smaller footprint on servers and customers will be able to brand it with just a few lines of code. By using WordPress, the platform taps into existing development resources which will help it stay on top of security issues.</p>\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/HostPressConceptImage.png"><img class="size-full wp-image-43376" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/HostPressConceptImage.png?resize=620%2C467" alt="HostPress Concept Image" /></a>HostPress Concept Image\n<p>Server managers will be able to extend the platform through an API as well as plugins. HostPress will have a robust set of plugins available to the public, covering the most popular server software at the time of launch.</p>\n<h2>Market Share</h2>\n<p>According to <a href="http://builtwith.com/">BuiltWith</a>, there are more than 4.1 million individual servers running active, licensed cPanel and Plesk installations. Base on this number, Griffiths calculates more than $82M is spent on control panels assuming a $20 per month price tag. Dedicated servers using cPanel, however, cost $45 per month.</p>\n<h2>Funding Specifics</h2>\n<p>The funds generated through the campaign will go to Griffiths, even if it&#8217;s not fully funded. However, if the project is fully funded, he expects to ship a beta of the product in June of 2016. He also plans to release the following:</p>\n<ul>\n<li>A modern, open-source, extensible server control panel</li>\n<li>An intuitive (and responsive) interface</li>\n<li>A fully-localized platform (HostPress speaks your language!)</li>\n<li>A platform developers can build on, including the ability to simply rebrand the panel without complex template languages.</li>\n</ul>\n<p>If the project doesn&#8217;t reach its funding goal, development will continue but at a slower pace. &#8220;The goal is to provide the Internet with an alternative to the clutter and complexity of server management. Even if we don&#8217;t become a major contender in this space, the support we do get will put pressure on the existing solutions to up their game,&#8221; Griffiths said.</p>\n<h2>Market Demand</h2>\n<p>When asked how much demand he&#8217;s witnessed in the hosting space, he replied, &#8220;There’s constant demand for fresh blood in the control panel space. Just take a look at a few of the cPanel/Plesk discussions online and you’ll see a lot of people complaining about their various flaws, or looking for a good alternative. In fact, there have been a number of other attempts made over the years, but none have gained traction due to one fatal flaw. They’re all written by engineers, so while the underlying functionality is solid, the interface always sucks.&#8221;</p>\n<p>If there is high demand from webhosts and server managers for a solution that&#8217;s better than Plesk or cPanel, Griffiths should have no problem reaching his funding goal. To find out what major webhosting companies think of the campaign and if they&#8217;ll financially contribute, I contacted GoDaddy and InMotion hosting. Both companies did not respond to my inquiries, despite multiple efforts to contact them.</p>\n<h2>Largest WordPress Crowdfunding Campaign on Record</h2>\n<p>Griffiths isn&#8217;t a stranger to the WordPress community&#8217;s generosity. Near the end of 2014, he started a <a href="http://wptavern.com/wordpress-community-pulls-together-to-help-a-member-in-need">crowdfunding campaign</a> to raise $2,500. He ended up with nearly three times that amount. In this case however, it&#8217;s a product and $175k is a lot of money. If successful, it will be the largest WordPress crowdfunding campaign on record, dwarfing <a href="http://wptavern.com/buddypress-bbpress-and-glotpress-development-campaign-is-now-fully-funded">John James Jacoby&#8217;s campaign</a> by $125k.</p>\n<p>HostPress looks like it could be an interesting product but without the financial aid of companies with large pockets, I don&#8217;t see how the campaign will reach its funding goal. Let us know your reactions to the campaign in the comments.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 05 May 2015 22:16:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:24;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:74:"WPTavern: New Plugin Reorders the WordPress Admin Menu Using Drag-and-Drop";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43236";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"http://wptavern.com/new-plugin-reorders-the-wordpress-admin-menu-using-drag-and-drop";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3626:"<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/reorder-admin-menu.png"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/reorder-admin-menu.png?resize=1025%2C482" alt="reorder-admin-menu" class="aligncenter size-full wp-image-43336" /></a></p>\n<p>Every WordPress administrator has different needs when navigating the admin. For example, one may require frequent access to the Posts menu and rarely touch the Appearance menu. Another admininistrator may have a certain custom post type that is accessed more frequently than any other menu item.</p>\n<p>In some cases plugin developers take their liberties placing their menu items at the very top of the admin. Jetpack is a prime example of a plugin that assumes preeminence above Posts, Media, Comments, and other more frequently used publishing items.</p>\n<p><a href="https://wordpress.org/plugins/admin-menu-manager/" target="_blank">Admin Menu Manager</a> is a new plugin that allows you to take control of the admin and order menu items to suit your workflow. The plugin, created by <a href="https://spinpress.com/" target="_blank">Pascal Birchler</a> and the folks at <a href="http://required.ch/" target="_blank">required+</a>, adds a simple drag-and-drop interface for decluttering and reordering menu items.</p>\n<p></p>\n<p>As you can see in the demo, Admin Menu Manager allows you to drag menu items from top level to a sub-menu or pull sub-menus out to top level for easier access. The plugin is unobtrusive and doesn&#8217;t require its own settings page.</p>\n<p>&#8220;I got the idea for this particular plugin when I stumbled upon a similar one that used a drag and drop interface just for reordering menu items,&#8221; Birchler said. After searching for other comparable solutions for the admin, he decided to take it one step further and produce a proof-of-concept. The result was a useful new plugin.</p>\n<p>&#8220;I learned that such side projects are great for adapting new technologies and digging deeper into WordPress,&#8221; he said. &#8220;This is already my third plugin leveraging Backbone.js in my first three months working at required+. Before that I had no idea how to use this library.</p>\n<p>&#8220;Also, I now know that the WordPress admin menu can be quite a mess. I mean, there aren&#8217;t even unit tests for it. I&#8217;ll see how I can change that in core.&#8221;</p>\n<p>Birchler said he counts himself lucky that his employer offers him time to work on open source projects. Before he started at required+, the company had no plugins listed on WordPress.org. Now they are up to five after polishing up a few that were lying dormant on GitHub for awhile.</p>\n<p>Version 1 of Admin Menu Manager is <a href="https://wordpress.org/plugins/admin-menu-manager/" target="_blank">now available on WordPress.org</a> and the team is working on adding the following features to version 2:</p>\n<ul>\n<li>Completely remove (and restore) menu items</li>\n<li>Edit existing menu items and their icons</li>\n<li>Add custom items to the admin menu</li>\n</ul>\n<p>In its current state, the plugin is a good option for re-arranging the admin to suit a client&#8217;s needs or for simply getting Jetpack and other less-frequently used menus out of your way.</p>\n<p>New users often complain about how confusing the WordPress admin can be, especially when many active plugins are adding their own top-level menus. With the features promised in version 2, <a href="https://wordpress.org/plugins/admin-menu-manager/" target="_blank">Admin Menu Manager</a> has the potential to become a solid tool for decluttering the admin.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 05 May 2015 21:11:01 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:25;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:89:"WPTavern: Themekraft’s Difficult Experience Switching to the WordPress Theme Customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43297";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:80:"http://wptavern.com/themekrafts-difficult-experience-switching-to-the-customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7022:"<p>Sven Lehnert, CEO of <a href="http://themekraft.com/">Themekraft</a>, published <a href="http://themekraft.com/what-it-means-for-us-and-others-to-follow-the-theme-review-guidelines/">his company&#8217;s experience</a> migrating from a custom theme options page to the theme customizer. He describes how difficult it was to move between the two and how it caused user frustration.</p>\n<p>&#8220;I’m sorry for the trouble some users are experiencing. We receive positive as well as frustrated feedback and I understand how users feel this way,&#8221; Lehnert said.</p>\n<a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/CustomThemeOptionsPage.png"><img class="size-full wp-image-43339" src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/CustomThemeOptionsPage.png?resize=1025%2C493" alt="Custom Theme Options Page" /></a>Custom Theme Options Page\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/CustomizerThemeOptions.png"><img class="size-full wp-image-43338" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/CustomizerThemeOptions.png?resize=1025%2C515" alt="Using the Customizer" /></a>Using the Customizer\n<p>Themekraft is migrating to the customizer because of <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options">a new requirement</a> that forces themes hosted in the <a href="https://wordpress.org/themes/">WordPress theme directory</a> to use it to build theme options. The requirement has sparked controversy and with 175 comments, is the most discussed article in Tavern history.</p>\n<h2>Consequences of Doing the Right Thing</h2>\n<p>Although Themekraft believes the requirement is the right decision, it&#8217;s come at the price of losing users. Lehnert expressed frustration that doing the right thing has caused users to jump ship, &#8220;I think it&#8217;s really frustrating, that our choice to use the customizer to create better themes has made users switch to a different theme. Our decision to use the customizer has pushed users to Themeforest.</p>\n<p>A lot of users have told us they moved to Themeforest and gave up on themes hosted on WordPress.org. To them, Themeforest does the job of WordPress.org and WordPress.org themes are outdated with limited functionality.&#8221;</p>\n<p>Two to three years ago I would have agreed with the opinion that themes in the WordPress theme directory leave a lot to be desired. I&#8217;ve read enough <a href="http://wptavern.com/tag/free-wordpress-themes">reviews of great looking free themes</a> that I&#8217;ve nearly erased this mindset. I used to discourage users from browsing for themes on the directory, now I encourage them.</p>\n<h2>The Educational Problem</h2>\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/09/ChalkboardLearning.png"><img class="size-full wp-image-30030" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/09/ChalkboardLearning.png?resize=640%2C250" alt="Chalkboard Learning" /></a>photo credit: <a href="https://www.flickr.com/photos/signifying/582602054/">Clint Gardner</a> &#8211; <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/">cc</a>\n<p>For years, the WordPress community has <a href="https://managewp.com/themes-design-plugins-functionality">discussed and educated</a> users on why it&#8217;s important to separate presentation from functionality. Lehnert thinks it&#8217;s something normal users can&#8217;t understand, &#8220;They want to buy solutions and base their purchasing decisions from a graphical point of view. The separation from design and functionality is not understandable for the normal user.&#8221;</p>\n<p>In a <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options#comment-67849">recent comment on the Tavern</a>, Chip Bennett explains his perspective on the educational part of the problem, &#8220;You are absolutely right that the wider (i.e. more than just the developers/insiders/one-percenters) have a very long way to go to educate those users.</p>\n<p>The reality is that, for far too long, commercial Theme developers attempted to add &#8216;value&#8217; to their Themes by creating Theme+Plugin combinations.&#8221;</p>\n<p>There&#8217;s been some movement on this front with some theme authors <a href="http://wptavern.com/why-wordpress-theme-developers-are-moving-functionality-into-plugins">moving theme functionality back into plugins</a>.</p>\n<p>Part of the problem is explaining the difference between themes and plugins. If you ask 10 WordPress developers where the line is drawn, you&#8217;d likely get at least five different answers. Since plugins can do everything a theme can do, it can easily become a never-ending debate between presentation and functionality.</p>\n<h2>The Balancing Act</h2>\n<p>Creating a WordPress product that balances user and developer needs is tricky. The main impetus for requiring the theme customizer is to provide a standardized experience between all the themes hosted in the directory. It will also help the Theme Review Team review themes more efficiently.</p>\n<p>Lehnert trusts the Theme Review Team&#8217;s decision but feels the change is geared towards developers. &#8220;I really believe in the WordPress community and I trust there will be a solution to the problem some day. At the moment however, the theme review guidelines only make sense from a developer&#8217;s perspective.&#8221;</p>\n<p>He suggests that the WordPress theme directory add support for <a href="http://wptavern.com/up-to-the-community-to-improve-theme-demo-data">better theme previews</a> with customizer access. This way, users can see how flexible and customizable a theme is.</p>\n<h2>Food for Thought</h2>\n<p>Based on Lehnert&#8217;s experience, there is a perception problem between WordPress.org hosted themes and those on Themeforest. It will be interesting to see if other theme authors and companies have a similar experience when they make the switch.</p>\n<p>It was disheartening to read this statement by Lehnert, &#8220;In the case of a theme business, staying outside of the community is easier!&#8221; Developers and users have at least one thing in common, they don&#8217;t like change, especially when it comes to requirements or guidelines. Developers have always had two choices:</p>\n<ol>\n<li>Abide by the requirements and guidelines to have a plugin or theme hosted on WordPress.org</li>\n<li>Do things on your own terms through your site and GitHub</li>\n</ol>\n<p>Outside of WordPress.org, it&#8217;s the wild west. You can use whatever custom options page or framework you want without anyone telling you what to do.</p>\n<p>Theme developers and companies are going to experience growing pains meeting the new requirement, but I think users of themes hosted on WordPress.org will be better off in the long run. They&#8217;ll know what to expect thanks to a standardized interface and eventually get used to interacting with the customizer.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 05 May 2015 20:45:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:26;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:90:"WPTavern: BuddyPress 2.3 Will Introduce Companion Stylesheets for WordPress Default Themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43120";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:100:"http://wptavern.com/buddypress-2-3-will-introduce-companion-stylesheets-for-wordpress-default-themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4909:"<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2014/01/wp-bp.jpg"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2014/01/wp-bp.jpg?resize=1025%2C383" alt="wp-bp" class="aligncenter size-full wp-image-14611" /></a></p>\n<p>Two years ago, <a href="http://codex.buddypress.org/developer/releases/version-1-7/" target="_blank">BuddyPress 1.7</a> introduced WordPress theme compatibility, which meant that sites no longer required a BuddyPress-specific theme in order to run the plugin. The vast majority of themes that use <a href="http://codex.wordpress.org/Theme_Development" target="_blank">WordPress&#8217; standard template loading</a> should be compatible with BuddyPress.</p>\n<p>However, some themes still need a little help to make the BuddyPress UI elements more harmonious with the rest of the theme. This is the case with the WordPress default themes, which prompted BuddyPress contributors to look into creating a set of companion stylesheets to address any conflicts arising between the plugin and the themes.</p>\n<p><a href="https://twitter.com/hnla" target="_blank">Hugo Ashmore</a>, who is leading the task of creating supporting styles for BuddyPress when activated on the default WordPress themes, summarized the goal on the <a href="https://bpdevel.wordpress.com/2015/04/01/companion-styles-task-updates/" target="_blank">BP development blog</a>:</p>\n<blockquote><p>We discussed and agreed in essence that it would be nice that BP displayed at its best when activated on these default WP themes as they may well be a user&#8217;s first impression of BP and first impressions last.</p></blockquote>\n<p>As of BuddyPress 2.3, the plugin will check and enqueue an additional set of styles if either <a href="https://buddypress.trac.wordpress.org/ticket/6291" target="_blank">Twenty Fifteen</a> or <a href="https://buddypress.trac.wordpress.org/ticket/6338" target="_blank">Twenty Fourteen</a> are active on the site. The same process will be used moving forward to support new WordPress default themes as they are released.</p>\n<p>Work on the tickets for these two themes has already been committed to <a href="https://buddypress.trac.wordpress.org/browser/trunk" target="_blank">BP trunk</a> and is on track for inclusion in 2.3. Whereas previously you might have seen messy unordered lists and BP component UI elements in various states of disarray, the new companion stylesheets resolve many of these issues with BP in use on the default themes.</p>\n<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/bp-twenty-fifteen.png"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/bp-twenty-fifteen.png?resize=1025%2C468" alt="bp-twenty-fifteen" class="aligncenter size-full wp-image-43320" /></a></p>\n<h3>A New Approach to User Account / Single Group Navigation Menus</h3>\n<p>If you take BuddyPress 2.3-alpha for a spin, you&#8217;ll notice that the companion stylesheets take a new approach to the user account and single groups navigation, with the primary object nav now displayed vertically on the left.</p>\n<p>The traditional horizontal nav often causes problems, as plugin developers can dynamically add to this menu, pushing it out to two or more rows of menu items. The vertical menus in the stylesheet eliminate the crowding that you often see in the horizontal user/group navigation.</p>\n<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/bp-user-account-nav.png"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/bp-user-account-nav.png?resize=1025%2C792" alt="bp-user-account-nav" class="aligncenter size-full wp-image-43323" /></a></p>\n<p>In the most recent <a href="https://bpdevel.wordpress.com/2015/04/29/companion-styles-an-update/" target="_blank">update</a> on the task, Ashmore requests that users bear in mind it&#8217;s &#8220;less about theming every aspect as about ensuring a broad sweep on elements to ensure the majority of critical issues are addressed.&#8221;</p>\n<p>The primary goal is to make BuddyPress render in a more seamless manner in the default themes. Refined styling to tweak specific BP elements is next on the agenda. If you want to test 2.3-alpha and find that the stylesheets aren&#8217;t loading, make sure to add <code>define (''SCRIPT_DEBUG'', true);</code> to your <em>wp-config.php</em> file if you want to run trunk directly.</p>\n<p>Contributors working on the companion stylesheet tickets <a href="https://bpdevel.wordpress.com/2015/04/29/companion-styles-an-update/" target="_blank">welcome feedback</a> from the community regarding the layout refactoring of the parent theme containers for the BP directories and user account screens, as well as the vertical menu approach. Testing these elements ahead of the BuddyPress 2.3 beta, expected out this week, will help contributors ship more polished stylesheets in the official release at the end of May.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 05 May 2015 18:30:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:27;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:85:"WPTavern: WordCamp Miami 2015 to Experiment with New Tracks, Tickets Selling Out Fast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=41567";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:94:"http://wptavern.com/wordcamp-miami-2015-to-experiment-with-new-tracks-tickets-selling-out-fast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4934:"<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/02/wcmia-2015.jpg"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/02/wcmia-2015.jpg?resize=750%2C349" alt="wcmia-2015" class="aligncenter size-full wp-image-39447" /></a></p>\n<p><a href="https://miami.wordcamp.org/2015/" target="_blank">WordCamp Miami</a>, one of the largest and longest running WordPress events in the US, is gearing up to <a href="http://wptavern.com/wordcamp-miami-gears-up-for-6th-year-with-new-tracks-and-workshops-planned" target="_blank">celebrate its 6th year on May 29-31</a>. Last year the event brought together 770 attendees and tickets for 2015 are selling fast.</p>\n<p>&#8220;We have sold over 600 tickets, and we see a sell-out on the horizon,&#8221; organizer David Bisset told the Tavern. &#8220;Our workshops are already almost sold out, and soon the weekend tickets will be as well.&#8221;</p>\n<p>WordCamp Miami has adopted a strong educational focus for the event with an expanded array of workshops. On Friday, May 29, the organizers will host a BuddyCamp and a separate Front-End/Theme workshop. As <a href="http://wptavern.com/wordcamp-miami-kids-workshop-launches-the-next-generation-of-bloggers" target="_blank">last year&#8217;s kids workshop</a> was a success, organizers are exploring the option of adding a more advanced kids workshop that gets into coding.</p>\n<h3>New &#8220;How To&#8221; Tracks and Mini-Workshops for Developers</h3>\n<p>Bisset and his team received feedback from last year&#8217;s event indicating that attendees are interested in having more advanced developer talks. This year organizers are replacing the user track on Saturday with experimental &#8220;How To&#8221; tracks.</p>\n<p>&#8220;To my knowledge, this is the first time a WordCamp has tried something like this,&#8221; Bisset said. &#8220;This track will focus on getting things done – almost like a mini-workshop focused on one or two concepts with step by step instructions &#8211; steps you can go home that night and do hopefully on your own.&#8221; Attendees of these tracks will be able to print out “cheat sheets” of each session and bring them to the conference or refer to them when they get back home.</p>\n<p>The organizers are hand-selecting the speakers and requesting that they format their slides to be a lasting resource for users. Speakers will also move to the Happiness Bar to answer any questions in a non-rushed environment after their sessions are finished.</p>\n<p>For the first time, WordCamp Miami will add an additional developer track on Sunday, which will consist of mini-workshops. In this format, two speakers will be give presentations on a single subject (back-to-back), so attendees will get multiple perspectives on the same subject.</p>\n<p>&#8220;For example, Andrea Rennick and Jesse Petersen will start off that Sunday with a &#8216;Genesis Framework&#8217; mini-workshop,&#8221; Bisset said. &#8220;Andrea will introduce the basics and concepts while Jesse afterwards will dive into more advanced topics on Genesis. There are also mini-workshops on building WordPress plugins, the WP-API, and more.&#8221;</p>\n<p>Organizers are also reaching out to other open source communities to help forge connections across different projects.</p>\n<p>&#8220;For the first time, we have a Joomla developer coming to speak on Sunday and talk about Joomla, WordPress, and open source,&#8221; Bisset said. &#8220;We have been opening our doors to local Joomla and Drupal developers so we are excited about this presentation and hope it’s the start of something bigger for the future.&#8221;</p>\n<p>WordCamp Miami is known for its excellent opportunities for networking and will maintain that aspect of the event in 2015.</p>\n<p>&#8220;Besides knowledge, networking has always been a key reason why people (local or not from the area) attend WordCamps,&#8221; Bisset said. Organizers are tailoring the after-party to be more of a &#8220;networking party&#8221; where attendees can continue their conversations from the event. Networking parties will take place on Thursday evening, Saturday night, Sunday for social breakfast, and a brief ice cream social Sunday afternoon.</p>\n<p>The new venue, Florida International University, is large enough to accommodate the 800+ attendees expected this year. All of the educational and networking opportunities during the 3.5 day event give attendees an incredible value for their tickets, especially for those who are traveling from a distance.</p>\n<p>WordCamp Miami is an event that traditionally sells out every year and Bisset expects the same for 2015. The workshops will be limited to 100-150 people and tickets are going fast. Check out the event <a href="https://miami.wordcamp.org/2015/" target="_blank">website</a> for more details on the schedule and available <a href="https://miami.wordcamp.org/2015/tickets/" target="_blank">tickets</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 04 May 2015 21:27:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:28;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:32:"Matt: Macbook &amp; USB-C Review";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45018";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"http://ma.tt/2015/05/macbook-usb-c-review/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5148:"<p><img class="alignright  wp-image-45019" src="https://ma.tt/files/2015/05/macbook-481x740.jpg" alt="macbook" width="266" height="409" />I&#8217;ll start by saying I&#8217;m writing this on a 12&#8243; Macbook in space grey. The screen, weight, size, and weird keyboard have captured my heart and I&#8217;m enjoying using the machine. It has replaced a 15&#8243; Retina Pro as my primary laptop for about 2 weeks now, with most of that being on the road.</p>\n<p>For better and worse, it&#8217;s a lot like an iPad &#8212; the size and weight feel very natural in your life, and the screen is really gorgeous. It&#8217;s also not worth plugging anything into it besides its charging cable. It feels great to open and pick up right where you left off. The speed feels more than adequate for everything I&#8217;ve thrown at it so far, though I haven&#8217;t tried video editing or photo management outside of the new Apple Photos app. If there was a perfect iPad and keybard combo, it would feel and look like the new Retina Macbook.</p>\n<p>The second thing I&#8217;ll say is I wouldn&#8217;t recommend this laptop for everybody yet. There are some trade-offs, for example I can get 5-6 hours from the battery but it&#8217;s a little shorter than I expected. It&#8217;s refreshing to have a computer that&#8217;s totally silent with no fan, and I&#8217;ve only had a heat warning once when it was sitting in hot direct sunlight for about 20 minutes. I moved into the shade because I was also wilting a bit from the direct LA sun.</p>\n<p>The main reason I&#8217;m not sure if I&#8217;d recommend this Macbook right is hopefully ephemeral: USB-C. One of the very coolest things about the new Macbook is it charges (quickly) with a new standard called USB 3.1 with a Type-C connector, which is open for anyone to use, is reversible, and I think is going to be the future <a href="http://ma.tt/2015/02/usb-history-and-type-c/">as I&#8217;ve written about on this blog before</a>.</p>\n<p><img class="aligncenter size-medium wp-image-45021" src="https://ma.tt/files/2015/05/USB-type-C-840x321.jpg" alt="USB-type-C" width="840" height="321" /></p>\n<p>Today, however, USB-C is bleeding edge. I actually have one other device that uses it, Google&#8217;s new Chrome Pixel laptop, but when you search on Amazon for &#8220;USB-C&#8221; there are almost no results except sketchy or not-in-stock generic things, and Apple doesn&#8217;t have any USB-C stuff in stock, even in their stores. (Perhaps related to the general stock issues <a href="http://ma.tt/2015/04/apple-loyalty/">I ended up writing about last time I tried to pen this Macbook review</a>.) I was able to get a cable that had male old USB and male USB-C on Amazon, that was pretty much it. The promise of USB-C is incredible: standard cables for charging everything super-quickly, a battery pack that could charge your phone or laptop, smaller power bricks, a next-gen Thunderbolt display with one cable for all data, display, and charging. You can see and imagine a really perfect ecosystem around USB-C, but it doesn&#8217;t exist today. <a href="http://9to5mac.com/2015/03/11/belkin-and-google-debut-usb-c-cables-including-low-priced-ethernet-displayport-hdmi-and-micro-usb-adapters/">Some cool stuff has been announced but isn&#8217;t coming until the summer</a>, even <a href="http://www.pcworld.com/article/2903292/usb-typec-peripherals-are-on-the-way-and-storage-devices-are-first-up.html">thumb drives</a>.</p>\n<p>The problem in one sentence: it is impossible to buy a cable, from Apple or otherwise, that let&#8217;s you plug an iPhone 6+ into the Macbook. They&#8217;ve announced but not shipped (to me at least) an adapter for old USB stuff (Type-A), but the last thing I need in my life is another dongle.</p>\n<p>I thought I would miss this but in practice it has been a surmountable problem. Instead of using my laptop as a battery, I&#8217;ve been <a href="http://hellomerch.com/collections/wordpress/products/jetpack-battery-pack">using a battery to recharge miscellaneous electronics on-the-go</a>, and everything else including transferring photos from phone to computer is now happening wirelessly.</p>\n<p><img class="  wp-image-45023 alignright" src="https://ma.tt/files/2015/05/apple-line-up.jpg" alt="apple-line-up" width="333" height="214" />I think the most perfect tech combo in the world right now might be a <a href="http://ma.tt/2014/10/retina-5k-mac/">5k iMac at home</a>, an iPhone 6+ as your phone, and the Macbook as an on-the-go device. (The iPad isn&#8217;t in my must-have list anymore.) The strengths of each of these products complement each other, and as Apple gets better about the cloud with things like photos, tethering, keychain sync, and continuity it&#8217;s really becoming a pleasure to use these products together. I also have an Apple Watch in the mix, but still forming my thoughts on that one.</p>\n<p>The thing I might be most excited about is when some of the new tech in the retina Macbook around the keyboard, screen, trackpad, and battery is applied to their &#8220;Pro&#8221; series, which will probably be a bit more in my wheelhouse.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 04 May 2015 21:25:20 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:29;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:99:"WPTavern: WordPress Theme Developer Handbook Updated with Comprehensive Guide to the Customizer API";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43238";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:109:"http://wptavern.com/wordpress-theme-developer-handbook-updated-with-comprehensive-guide-to-the-customizer-api";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6375:"<a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/02/design-studio.jpg" rel="prettyphoto[43238]"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/02/design-studio.jpg?resize=760%2C374" alt="photo credit: Artist''s Room - (license)" class="size-full wp-image-39730" /></a>photo credit: <a href="http://www.flickr.com/photos/63191453@N00/2650862549">Artist&#8217;s Room</a> &#8211; <a href="https://creativecommons.org/licenses/by/2.0/">(license)</a>\n<p>The Theme Review Team&#8217;s controversial decision to <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options" target="_blank">require the use of the Customizer API for building theme options</a> unearthed a wave of criticism and concern about the capabilities of the customizer.</p>\n<p>In response to more than <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options#comments" target="_blank">150 comments</a> debating on the topic, Nick Halsey, who has worked extensively on the feature in WordPress core, stopped by to offer a few words in support of the Theme Review Team&#8217;s decision:</p>\n<blockquote><p>Many of the comments here are misinformed or unaware of both the full power of and the future importance of the Customizer. I’ve given an <a href="http://celloexpressions.com/blog/the-customizer-is-the-future-for-themes-and-theme-options/" target="_blank">overview of my perspective on my blog</a>, and while those views don’t directly represent the views of the WordPress project, I can say that most people working on the Customizer in core would agree with my points. Like it or not, the Customizer is here to stay, and ignoring that fact will eventually cause users to turn against you.</p></blockquote>\n<p>Halsey&#8217;s post calls for theme developers to re-examine their philosophies when it comes to building complex UI options and stop re-inventing the wheel. He believes the customizer has more creative potential than developers give it credit for.</p>\n<blockquote><p>Complaints about the amount of screen real estate available and the 300px default width show a lack of creativity and resistance for the sake of resistance to change. Start by removing all of the ads, external links, unnecessary branding, unnecessary options, and general clutter. Make your options self-explanatory – if you need a paragraph to describe what it does, it probably shouldn’t be a user-facing option. Do you still have so much UI that the experience is completely unusable? Try an outside-the-box solution, like utilizing the core media modal (header images and core media controls use it), a custom modal (theme details modal in core), or a slide-out panel (widgets in core and eventually menus in core as well).</p></blockquote>\n<p>Prior to the Theme Review Team&#8217;s decision, documentation on theme development with the Customizer API was sparse and claims about its wide range of capabilities were difficult to support.</p>\n<p>Resistance from theme developers has WordPress.org contributors scrambling to produce better documentation for using the customizer in themes. Over the weekend, Halsey created a canonical developer tutorial on the <a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/" target="_blank">Customizer API in the official theme developer handbook</a>.</p>\n<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-api-documentation.png" rel="prettyphoto[43238]"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/customizer-api-documentation.png?resize=1025%2C605" alt="customizer-api-documentation" class="aligncenter size-full wp-image-43252" /></a></p>\n<p>This official comprehensive guide includes the following sections and provides detailed examples for each:</p>\n<ul>\n<li><a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/#contextual-controls-sections-and-panels" target="_blank">Contextual Controls, Sections, and Panels</a></li>\n<li><a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/#using-postmessage-for-improved-setting-previewing" target="_blank">Using PostMessage For Improved Setting Previewing</a></li>\n<li><a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/#custom-controls-sections-and-panels" target="_blank">Custom Controls, Sections, and Panels</a></li>\n<li><a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/#custom-setting-types" target="_blank">Custom Setting Types</a></li>\n<li><a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/#the-customizer-javascript-api" target="_blank">The Customizer JavaScript API</a></li>\n<li><a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/#javascriptunderscore-js-rendered-custom-controls" target="_blank">JavaScript/Underscore.js-Rendered Custom Controls</a></li>\n<li><a href="https://developer.wordpress.org/themes/advanced-topics/customizer-api/#allow-non-administrators-to-access-the-customizer" target="_blank">Allow Non-administrators to Access the Customizer</a></li>\n</ul>\n<p>Theme Review Team admin Justin Tadlock <a href="https://make.wordpress.org/themes/2015/04/22/details-on-the-new-theme-settings-customizer-guideline/" target="_blank">posted</a> more details clarifying the new WordPress.org guideline and included a list of additional resources for learning more about the customizer.</p>\n<p>Over the weekend, Samuel &#8220;Otto&#8221; Wood, who has written several customizer articles over the years, wrote a &#8220;<a href="http://ottopress.com/2015/whats-new-with-the-customizer/" target="_blank">What’s new with the Customizer</a>&#8221; tutorial that explores some of its newer features in depth, including panels, active callbacks, and customizing the customizer.</p>\n<p>With <a href="http://wptavern.com/wordpress-4-3-to-focus-on-mobile-experience-admin-ui-better-passwords-and-customizer-improvements" target="_blank">WordPress 4.3 blazing forward on customizer improvements</a>, now is the time for theme developers to familiarize themselves with the available documentation and tutorials in order to be ready to take full advantage of WordPress&#8217; core-supported method of providing live previews to users.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 04 May 2015 16:46:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:30;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"Matt: James Whitcomb Riley Poem";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45016";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:47:"http://ma.tt/2015/05/james-whitcomb-riley-poem/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:748:"<p><a href="http://om.co/2015/05/02/loss/">Via Om</a>, I wanted to share this poem <em>Away</em> by <a href="http://www.poemhunter.com/james-whitcomb-riley/poems/">James Whitcomb Riley</a>:</p>\n<blockquote><p>I cannot say, and I will not say<br />\nThat he is dead. He is just away.<br />\nWith a cheery smile, and a wave of the hand,<br />\nHe has wandered into an unknown land<br />\nAnd left us dreaming how very fair<br />\nIt needs must be, since he lingers there.<br />\nAnd you—oh you, who the wildest yearn<br />\nFor an old-time step, and the glad return,<br />\nThink of him faring on, as dear<br />\nIn the love of There as the love of Here.<br />\nThink of him still as the same. I say,<br />\nHe is not dead—he is just away.</p></blockquote>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 03 May 2015 16:34:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:38:"Donncha: Matt’s interview in the SBP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:24:"http://z9.io/?p=89499491";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"http://z9.io/2015/05/03/matts-interview-in-the-sbp/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:977:"<p><a href="http://i2.wp.com/z9.io/files/2015/05/wpid-20150503_124454.jpg"><img title="20150503_124454.jpg" class="alignnone size-full" alt="image" src="http://i2.wp.com/z9.io/files/2015/05/wpid-20150503_124454.jpg?w=660" /></a></p>\n<p>Nice to see an interview with Matt in the Sunday Business Post, but they got one thing wrong that Matt is not chilled out about!</p>\n\n<p><strong>Related Posts</strong><ul><li> <a href="http://z9.io/2007/02/16/photomatts-net-interview/" rel="bookmark" title="Permanent Link: Photomatt''s .net interview">Photomatt&#039;s .net interview</a></li><li> <a href="http://z9.io/2003/03/24/an-interview-with-mike-davidson-of-espn-part-1/" rel="bookmark" title="Permanent Link: An Interview With Mike Davidson of ESPN (Part 1)">An Interview With Mike Davidson of ESPN (Part 1)</a></li><li> <a href="http://z9.io/2004/07/02/more-on-bush-interview/" rel="bookmark" title="Permanent Link: More On Bush Interview!">More On Bush Interview!</a></li></ul></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 03 May 2015 11:48:40 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Donncha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:32;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"Matt: RIP Dan, RIP Dave";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45011";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"http://ma.tt/2015/05/rip-dan-rip-dave/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1238:"<p>We&#8217;ve lost two incredible souls this week: <a href="http://recode.net/2015/04/25/google-exec-dan-fredinburg-killed-in-nepal-earthquake/">first Dan Fredinburg in Nepal</a> and now <a href="http://recode.net/2015/05/02/beloved-silicon-valley-entrepreneur-david-goldberg-dies-suddenly/">Dave Goldberg has unexpectedly passed</a>. I encourage you to Google articles about their lives, <a href="http://www.businessinsider.com/the-incredible-life-of-david-goldberg-2015-5">like this one about Dave Goldberg</a> or <a href="http://www.outsideonline.com/1972721/remembering-dan-fredinburg">this on Dan</a>, because both were unique and incredible individuals. In an example of <a href="http://meyerweb.com/eric/thoughts/2014/12/24/inadvertent-algorithmic-cruelty/">how software can have unintended effect on emotions</a>, I just realized I had a pending friend request on Facebook from Dan, probably years old. <img src="http://i1.wp.com/s.ma.tt/blog/wp-includes/images/smilies/frownie.png?w=604" alt=":(" class="wp-smiley" /> Going through a lot of emotions, but a good reminder that life can be fleeting and to make time for friends and those who you love, something both of these men were great at. May they both rest in peace.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 02 May 2015 19:46:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:84:"WPTavern: Belgrade’s First WordCamp Sells Out, Plans to Double Attendees Next Year";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42992";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:90:"http://wptavern.com/belgrades-first-wordcamp-sells-out-plans-to-double-attendees-next-year";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5298:"<a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wcbelgrade.jpg" rel="prettyphoto[42992]"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wcbelgrade.jpg?resize=1025%2C505" alt="photo credit: WordCamp Belgrade" class="size-full wp-image-43216" /></a>photo credit: <a href="http://belgrade.wordcamp.org/2015/wordcamp-belgrade-first-batch-of-photos-wcbg/">WordCamp Belgrade</a>\n<p>Organizers of the very first WordCamp Belgrade are happy to report that the event was a smashing success. <a href="http://wptavern.com/a-glimpse-into-serbias-rapidly-growing-wordpress-community" target="_blank">Serbia&#8217;s rapidly growing WordPress community</a> started just two years ago with local meetups that became larger than some smaller WordCamps.</p>\n<p>&#8220;Our road from the first meetup back in April 2013 to the first WordCamp was brilliant,&#8221; organizer Milan Ivanović said. &#8220;Every WPSerbia meetup had no less than 100 people attending, with at least three speakers each.&#8221; Serbia was ready to host its first WordCamp.</p>\n<p>&#8220;We were completely sold out about 10 days before the actual event, and it was such a shame that we had to turn down around 50 people who were asking for extra tickets,&#8221; Ivanović said. &#8220;We were limited by the venue and we couldn&#8217;t take more than 180.&#8221;</p>\n<p>Attendees represented 13 different countries with the highest numbers from Serbia (73%), Macedonia, Bosnia and Herzegovina, and Croatia. Those who came from other countries were treated to Serbia&#8217;s famous hospitality with tours and local cuisine.</p>\n<p>&#8220;We dedicated some extra time for people who visited Belgrade for the first time to experience Belgrade and all of its beauties,&#8221; Ivanović said.</p>\n<p>&#8220;That is why we organized an unofficial after-after party that included a stroll through Belgrade&#8217;s main pedestrian street Knez Mihailova, a visit to Belgrade Fortress Kalemegdan, and dinner with true Serbian food and music in the most famous boem street Skadarlija.&#8221;</p>\n<a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wordcamp-belgrade-food.jpg" rel="prettyphoto[42992]"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wordcamp-belgrade-food.jpg?resize=1025%2C494" alt="photo credit: WordCamp Belgrade" class="size-full wp-image-43219" /></a>photo credit: <a href="http://belgrade.wordcamp.org/2015/wordcamp-belgrade-first-batch-of-photos-wcbg/">WordCamp Belgrade</a>\n<p>&#8220;The food was so good that I was afraid that this WordCamp wouldn&#8217;t be remembered by its talks and speakers but by the catering that all of us enjoyed,&#8221; he said.</p>\n<p>WordCamp Belgrade 2015 in numbers:</p>\n<ul>\n<li>800+ bottles of refreshment served (on the first day)</li>\n<li>500+ coffees served (on the first day)</li>\n<li>345 Tweets with <a href="https://twitter.com/hashtag/wcbg?src=hash" target="_blank">#wcbg</a></li>\n<li>250 Meals served</li>\n<li>180 Tickets sold</li>\n<li>61 Trello cards</li>\n<li>22 Sponsors</li>\n<li>16 Speaker Applications</li>\n<li>13 Talks / Workshops</li>\n<li>10 Speakers</li>\n<li>9 Volunteers</li>\n<li>8 Days after, all session videos published</li>\n<li>1 Awesome <a href="http://wptavern.com/meet-wapuujlo-official-mascot-of-wordcamp-belgrade" target="_blank">Mascot</a></li>\n</ul>\n<p>Attendees received &#8220;<a href="http://wptavern.com/meet-wapuujlo-official-mascot-of-wordcamp-belgrade" target="_blank">Wapuujlo</a>&#8221; magnets and stickers to commemorate the event.</p>\n<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/wapuujlo-magnets.jpg" rel="prettyphoto[42992]"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/05/wapuujlo-magnets.jpg?resize=1025%2C437" alt="wapuujlo-magnets" class="aligncenter size-full wp-image-43226" /></a></p>\n<p>Videos from the WordCamp are already available on <a href="https://www.youtube.com/channel/UCNn90HubD28a63SJu07vYZg" target="_blank">WordPress Serbia&#8217;s YouTube account</a> and will soon be uploaded to WordPress.tv as well.</p>\n<p>&#8220;As soon as WordCamp Belgrade finished, the first thing I did was start plans for #wcbg2016,&#8221; Ivanović said.</p>\n<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wcbelgrade-organizers.jpg" rel="prettyphoto[42992]"><img src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/05/wcbelgrade-organizers.jpg?resize=300%2C200" alt="wcbelgrade-organizers" class="alignright size-medium wp-image-43223" /></a>&#8220;The biggest outcome from this event was people asking how they can help organize the next WordCamp Belgrade, offering lots of different kinds of help &#8211; from finding new sponsors to offering their organization skills.&#8221;</p>\n<p>Ivanović and the organizing team plan to at least double the size of the event next year. They are aiming for 400 attendees and two tracks of speakers.</p>\n<p>&#8220;If we manage to organize an event that size, I think that would be an awesome test and a great intro for application to organize WordCamp Europe 2017,&#8221; he said.</p>\n<p>Check out more <a href="http://belgrade.wordcamp.org/2015/wordcamp-belgrade-first-batch-of-photos-wcbg/" target="_blank">photos from the event</a> on the WordCamp Belgrade website.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 May 2015 21:04:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"Matt: More on GMOs";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=45008";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:34:"http://ma.tt/2015/05/more-on-gmos/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:606:"<blockquote><p>After writing two books on the science of climate change, I decided I could no longer continue taking a pro-science position on global warming and an anti-science position on G.M.O.s.</p></blockquote>\n<p>Mark Lynas writes <a href="http://www.nytimes.com/2015/04/25/opinion/sunday/how-i-got-converted-to-gmo-food.html">How I Got Converted to G.M.O. Food</a>, particularly how GMOs impact the places where crops are needed the most. If you&#8217;re looking for a catch-up <a href="http://ma.tt/2014/03/whole-foods-and-psuedoscience/">check out this link collection on ma.tt last year</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 May 2015 18:43:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:35;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:67:"WPTavern: WordPress.com Suspends Theme Submissions from New Sellers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42345";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"http://wptavern.com/wordpress-com-suspends-theme-submissions-from-new-sellers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5419:"<p>In March 2014, <a href="http://wptavern.com/wordpress-com-formally-opens-its-marketplace-to-theme-developers" target="_blank">WordPress.com opened its marketplace to new theme authors</a>. Prior to that time, new sellers were added via invitation only. A year ago there were only 300 themes available to WordPress.com users, but after having the marketplace open to new authors that count is up to 345.</p>\n<p>Recently the <a href="https://theme.wordpress.com/join/" target="_blank">submission form disappeared from the site</a> with a message that WordPress.com would be keeping it temporarily closed in order to add new features that make the process easier.</p>\n<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/new-themes-wordpresscom.png" rel="prettyphoto[42345]"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/05/new-themes-wordpresscom.png?resize=1025%2C736" alt="new-themes-wordpresscom" class="aligncenter size-full wp-image-43187" /></a></p>\n<p><a href="https://array.is/" target="_blank">Array</a> founder Mike McAlister recently published an <a href="https://array.is/a-year-in-review/" target="_blank">article</a> that detailed his experience selling on the WordPress.com marketplace. One of the main drawbacks was the lack of efficiency in handling the queue for new theme submissions.</p>\n<blockquote><p>The review process on WordPress.com is long. I’m not talking about weeks long, I’m talking about months long. Each Array theme review has taken at least a month, usually longer. Our latest theme for WP.com, Camera, took four months from the day I submitted it to the day it was released.</p></blockquote>\n<p>In addition to painfully long queues, theme authors have also been disappointed with WordPress.com&#8217;s recent lack of promotion for commercial themes. These factors contributed to McAlister&#8217;s decision to focus on promoting his products through more efficient distribution channels and <a href="http://wptavern.com/array-returns-to-themeforest-after-disappointing-experiences-selling-on-creative-market-and-wordpress-com" target="_blank">return to Themeforest</a>.</p>\n<p>In April, WordPress.com theme author Sami Keijonen <a href="https://foxland.fi/toivo-was-not-approved-in-wordpress-com/" target="_blank">posted about his recent difficulties with the marketplace</a> after noticing that WordPress.com removed the submission form for new authors. He summarized some of the sources of confusion for commercial theme authors:</p>\n<blockquote>\n<ul>\n<li>WordPress.com basically stopped marketing commercial themes. (However, they do tweet about new themes.)</li>\n<li>We have a private blog for themers but other than that, there isn&#8217;t any conversation between developers or WordPress.com staff. They did send a enquiry a while ago so that might help.</li>\n<li>The review process takes months for commercial themes.</li>\n<li>They seem to want really simple themes with simple design decisions. That’s fine by me but isn’t that kind of “forcing” the end user to like certain types of themes if they don’t have any options?</li>\n<li>I would have wanted more accessibility-ready themes in WordPress.com like mine, but it seems that isn&#8217;t priority.</li>\n</ul>\n</blockquote>\n<p>I contacted Automattic to find out why the submission form has been removed and when authors can expect for it to be re-opened. The company&#8217;s official statement indicates that opening up the marketplace was a temporary experiment and that there is no ETA for relaunching it.</p>\n<blockquote><p>It’s important to note that current WordPress.com sellers can submit new themes for possible launch. We’re not closed for new theme submission. We experimented with a public form for themes from new shops last year, and we had a ton of great submissions from theme shops around the world. We took it down last fall while we worked on getting ahead of all the new theme reviews that it created. We’ll put it up again but we don’t have an exact date in mind. We do still reach out to new shops with great themes. We’re always excited to find awesome theme shops.</p></blockquote>\n<p>The company&#8217;s statement regarding the change in marketing clarifies that it is looking for new strategies to promote commercial themes.</p>\n<blockquote><p>We may not do blog posts any more, but we haven’t stopped marketing premium themes. They’re featured prominently on <a href="https://wordpress.com/themes" target="_blank">wordpress.com/themes</a> and as part of our <a href="https://store.wordpress.com/plans/" target="_blank">Business Plan</a>. Plus, we’re exploring more ways to put premium themes in front of users.</p>\n<p>In the future, premium theme shops can expect better feedback around the themes they submit, quicker launches, and more communication in general from the WordPress.com Theme Team. We’re excited about what we can continue to do for the world of themes with our sellers’ help.</p></blockquote>\n<p>Automattic has no set time frame for launching these improvements, but it should be reassuring for commercial theme authors to know that the company is tackling the inefficiency that was bogging down the system. For the time being, new commercial theme authors looking to submit products to the marketplace are out of luck, but Automattic may decide to open it up again to continue the experiment in the future.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 May 2015 18:11:16 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:33:"Akismet: April 2015 Stats Roundup";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"http://blog.akismet.com/?p=1839";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"http://blog.akismet.com/2015/05/01/april-2015-stats-roundup/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2934:"<p>April turned out to be a slow month in Akismetland. The highest number of spam comments we saw come in this month on a given day was about 177 million. The total amount of spam we saw come through this month is 23% less than last month, and 33% less than April of last year.</p>\n<p>Here&#8217;s a chart showing the number of spam and ham comments we saw come through each day this month:</p>\n<p><img class="alignnone size-large wp-image-1840" src="https://akismet.files.wordpress.com/2015/05/akismet-spam-and-ham-stats-april-2015.png?w=700&h=438" alt="graph of akismet spam and ham daily stats April 2015" /></p>\n<div id="attachment_1841" class="wp-caption alignright"><img class="size-medium wp-image-1841" src="https://akismet.files.wordpress.com/2015/05/time_machine.jpg?w=300&h=252" alt="This image, .Time Machine. by Sachin Sandhu, is licensed under CC BY 2.0" width="300" height="252" /><p class="wp-caption-text">This image, <a href="https://www.flickr.com/photos/sachin_sandhu/2711789618">.Time Machine.</a> by <a href="https://www.flickr.com/photos/sachin_sandhu/">Sachin Sandhu</a>, is licensed under <a href="https://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a></p></div>\n<p>The total number of spam comments this month is <strong>4,167,247,500</strong> &#8211; just over four billion, which is still a big number even though it&#8217;s a slow month ????. To help visualize this number, let&#8217;s say it takes a second to count each spam message. In that case, <strong>it would take 132 years and two months to finish counting</strong>.</p>\n<p>As for ham &#8211; we saw a total of <strong>145,308,000 real messages</strong> come through. If we were counting each one of those, it would take only 4 and a half years to finish. As usual, there&#8217;s much more spam going around than real messages &#8211; only 3.4% of all messages sent this month were not spam.</p>\n<p>We missed only about 1 in every 10,443 spams this month. If you are seeing spam in your comments, please mark it as spam &#8211; this will help Akismet learn from your input. Similarly, please mark any real comments that end up in the spam folder as &#8216;not spam&#8217;. If you&#8217;re seeing very many mislabelled comments, please <a href="https://akismet.com/contact/">contact us</a> about it and we&#8217;ll be happy to help dig into the issue.</p>\n<p><em>This post is part of a monthly series summarizing some stats and figures from the Akismet universe. Feel free to browse <a href="http://blog.akismet.com/category/monthly-roundup/">all of the posts in the series</a>.</em></p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/akismet.wordpress.com/1839/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/akismet.wordpress.com/1839/" /></a> <img alt="" border="0" src="http://pixel.wp.com/b.gif?host=blog.akismet.com&blog=116920&post=1839&subd=akismet&ref=&feed=1" width="1" height="1" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 May 2015 15:52:23 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Valerie";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"Matt: Changing America’s Mind";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=44992";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"http://ma.tt/2015/04/changing-americas-mind/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:354:"<p><a href="http://www.bloomberg.com/graphics/2015-pace-of-social-change/"><img class=" size-full aligncenter" src="https://ma.tt/files/2015/04/bottom.png" alt="" /></a></p>\n<p>Bloomberg has a cool look at societal changes, called <a href="http://www.bloomberg.com/graphics/2015-pace-of-social-change/">This Is How Fast America Changes Its Mind</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 May 2015 05:56:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:74:"WPTavern: How to Restore the Link Title Attribute Removed in WordPress 4.2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43134";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"http://wptavern.com/how-to-restore-the-link-title-attribute-removed-in-wordpress-4-2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6310:"<p>WordPress 4.2 is <a href="http://wptavern.com/wordpress-4-2-powell-is-now-available-for-download">a week old</a> and has been <a href="https://wordpress.org/download/counter/">downloaded</a> more than six million times. One of the first things I noticed after updating is the change to the Insert/edit link modal box. Instead of having to apply a title to the URL, the title is replaced with Link Text. The text that is highlighted before adding a link is automatically inserted into the Link Text box.</p>\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/LinkmodalChange.png" rel="prettyphoto[43134]"><img class="wp-image-43135 size-full" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/LinkmodalChange.png?resize=1025%2C301" alt="LinkmodalChange" /></a>WordPress 4.2 Add Link Modal on the Left WordPress 4.1 on the Right\n<p>While I found this behavior to be annoying at first, it has quickly become one of my favorite changes. Adding links is quicker and more efficient. Several other people however, don&#8217;t like the change. WordPress user <a href="https://profiles.wordpress.org/Enticknap">Enticknap</a> created a <a href="https://core.trac.wordpress.org/ticket/32095">ticket on Trac</a> reporting the issue as a bug when in fact, the change was deliberate.</p>\n<p><a href="https://profiles.wordpress.org/DrewAPicture">Drew Jaynes</a>, who led the <a href="http://wptavern.com/drew-jaynes-to-lead-wordpress-4-2">WordPress 4.2 development cycle</a>, explained <a href="https://core.trac.wordpress.org/ticket/32095#comment:5">why the change was made</a>.</p>\n<blockquote><p>The &#8216;Title&#8217; field was intentionally removed from the wpLink modal in <a class="closed ticket" title="task (blessed): Include ''source anchor'' in wpLink quicktags modal for improved ui/ux (closed: fixed)" href="https://core.trac.wordpress.org/ticket/28206">#28206</a> largely because it was often confused with the actual link text itself.</p>\n<p>In recent years, we&#8217;ve begun to actively discourage the use of title attributes in links as they are largely useless outside of providing the &#8220;hover tooltip&#8221; many visual users enjoy, and more importantly, they don&#8217;t promote good accessibility.</p>\n<p>If you&#8217;d like to continue using title attributes in links, you can add them manually using the Text mode in the editor.</p></blockquote>\n<p>Several people took part in the conversation, explaining why the Title box is an important part of their work flow. Andrew Nacin, who helped design the original Link dialog, <a href="https://core.trac.wordpress.org/ticket/32095#comment:22">said,</a> &#8220;I wish this is how it worked from the start.&#8221; Nacin described the Title attribute as an edge case and that its bad for accessibility.</p>\n<p>The discussion was heated at times, but the conclusion is that the Title attribute will not be added back to the dialog box. Instead, users are encouraged to use the <a href="https://wordpress.org/plugins/restore-link-title-field/">Restore Link Title Field</a> plugin developed by <a href="https://profiles.wordpress.org/otto42/">Samuel &#8216;Otto&#8217; Wood</a> and <a href="https://wordpress.org/plugins/restore-link-title-field/">Sergey Biryukov</a>.</p>\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/RestoreLinkTitleAttribute.png" rel="prettyphoto[43134]"><img class="size-full wp-image-43138" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/RestoreLinkTitleAttribute.png?resize=502%2C249" alt="Link Title Attribute Restored" /></a>Link Title Attribute Restored\n<p>With the plugin activated, the Insert/edit link dialog is restored to how it was in WordPress 4.1. According to the <a href="https://wordpress.org/plugins/restore-link-title-field/">WordPress plugin directory</a>, the plugin is activated on 100+ sites. I asked Wood if there are plans to add additional features.</p>\n<p>&#8220;I don&#8217;t think adding new features is in the cards as there&#8217;s not much to add,&#8221; he said. &#8220;We might change it up as we fix some of the <a href="https://core.trac.wordpress.org/ticket/32180">problems in core</a> causing it to be difficult to do properly.&#8221;</p>\n<h2>WordPress is Continuously Evolving Software</h2>\n<p>I sympathize with those who are upset that the Link Title attribute was removed from WordPress 4.2. If a feature you depend on in WordPress is drastically changed or removed, the first instinct is to be upset. It forces you to change your workflow and the change is often unexpected.</p>\n<p>I&#8217;ve traveled this path, but I&#8217;ve realized WordPress is continuously evolving software that tries to cater to the majority. Features removed from WordPress generally never go away as they&#8217;re replaced with plugins. A good example is when the ability to add borders and padding to images <a href="http://wptavern.com/common-issues-and-troubleshooting-wordpress-3-9">was removed in WordPress 3.9</a>.</p>\n<a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/04/AdvancedImageEditingOptions.png" rel="prettyphoto[43134]"><img class="size-full wp-image-21489" src="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/04/AdvancedImageEditingOptions.png?resize=840%2C401" alt="Advanced Image Editing Styles" /></a>Advanced Image Styles\n<p>This change lead to a lengthy discussion both on WordPress.org and <a href="http://en.forums.wordpress.com/topic/image-resize-1?replies=430">WordPress.com support forums</a>. Gregory Cornelius created the <a href="https://wordpress.org/plugins/advanced-image-styles/">Advanced Image Styles</a> plugin which re-adds the ability to adjust an image&#8217;s margins and borders as you could prior to WordPress 3.9. According to the plugin directory, it&#8217;s active on more than 20,000 sites.</p>\n<p>I&#8217;m not saying you shouldn&#8217;t speak up when something you use in WordPress is removed. Rather, it&#8217;s a reminder that there is a way for everyone to get the features they want as WordPress core undergoes changes.</p>\n<p><em><strong>Note</strong></em> Before installing the plugin to restore the Link Title attribute, please <a href="http://silktide.com/i-thought-title-text-improved-accessibility-i-was-wrong/">read this post</a> shared by Peter Wilson in the comments.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 May 2015 04:49:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:39;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:75:"WPTavern: Toivo: A Bold Minimalist WordPress Theme for Blogs and Businesses";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43078";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"http://wptavern.com/toivo-a-bold-minimalist-wordpress-theme-for-blogs-and-businesses";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4786:"<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/tovio.jpg" rel="prettyphoto[43078]"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/tovio.jpg?resize=1025%2C489" alt="tovio" class="aligncenter size-full wp-image-43080" /></a></p>\n<p><a href="https://wordpress.org/themes/toivo-lite/" target="_blank">Toivo Lite</a> is a new theme on WordPress.org that features a bold minimalist design that really shines on mobile. <a href="https://foxland.fi/" target="_blank">Sami Keijonen</a> created the theme to be suitable for both business and blog sites.</p>\n<p>Toivo is Finnish and it means &#8220;hope&#8221; in English. It&#8217;s one of a very small number of WordPress themes listed as <a href="https://wordpress.org/themes/tags/accessibility-ready/" target="_blank">accessibility-ready</a> in the official directory. Toivo meets the necessary <a href="https://make.wordpress.org/themes/handbook/review/accessibility/" target="_blank">guidelines</a> without compromising the overall design.</p>\n<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/tovio-screenshot.png" rel="prettyphoto[43078]"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/tovio-screenshot.png?resize=880%2C660" alt="tovio-screenshot" class="aligncenter size-full wp-image-43081" /></a></p>\n<p>Toivo can be easily personalized via the customizer with the following built-in options:</p>\n<ul>\n<li>Set header text color, background color, header image, and background image</li>\n<li>Support for 3 navigation menus: primary, top, and social navigation</li>\n<li>Select from 3 different layouts: 1 column,  2 Columns: Content / Sidebar, 2 Columns: Sidebar / Content</li>\n<li>Edit the front page callout title, text, and URL</li>\n</ul>\n<p>With Jetpack active, the theme has additional features for custom content support:</p>\n<ul>\n<li>Upload a logo</li>\n<li>Show your testimonials</li>\n<li>Display portfolio items</li>\n<li>Add infinite scroll to your blog</li>\n</ul>\n<p>Toivo is Keijonen&#8217;s sixth theme accepted to WordPress.org. In the past he has often built on top of the <a href="http://themehybrid.com/hybrid-core" target="_blank">Hybrid Core</a> framework, but this theme uses only select parts, including the <a href="https://github.com/justintadlock/hybrid-core/blob/master/classes/hybrid-media-grabber.php" target="_blank">Hybrid Media Grabber</a> (a script for grabbing media related to a post), a stripped down version of Schema.org markup support, and the <a href="http://themehybrid.com/plugins/breadcrumb-trail" target="_blank">Breadcrumb Trail</a>.</p>\n<p>&#8220;I can still use best parts of Hybrid Core and make decisions based on theme I’m building,&#8221; Keijonen said. &#8220;Toivo is slimmer with fewer translating strings, and has less code to handle.&#8221;</p>\n<p>Keijonen said that branching out has helped him to understand every line of code and have more control over the theme.</p>\n<p>&#8220;Don&#8217;t get me wrong, I have learned most of my WordPress theme knowledge from Justin Tadlock,&#8221; he said. &#8220;Theme Hybrid is still the only community I feel I belong. It is the place where you can learn, be yourself, ask help, have opinions, and get feedback. But in a way I have grown out of it; it&#8217;s like a moving-from-home experience.&#8221;</p>\n<p>Toivo was rejected when submitted to WordPress.com, but Keijonen is known for his tenacity and continual experimentation with design and distribution approaches.</p>\n<p>&#8220;I have plans to fork the theme, create church and charity themes out of it, and sell it on Themeforest if they allow it,&#8221; he said.</p>\n<p>A year ago, Keijonen conducted an <a href="http://wptavern.com/the-mina-olen-free-wordpress-theme-experiment" target="_blank">experiment</a> wherein he made his commercial Mina Olen theme available for free on GitHub to see if it would affect its popularity and sales for support. The results were positive overall, and Keijonen now has more commercial products available on GitHub. To date, he has earned $5,304 from the WordPress.com version of Mina Olen and 2,142€ from sales of the self-hosted version.</p>\n<p>Getting Toivo approved on WordPress.org was the next step in his theme development journey and Keijonen reports that the experience was &#8220;fast as a shark&#8221; this time. Toivo has been downloaded more than 1,100 times in less than a week. Check out the <a href="https://foxland.fi/demo/toivo/" target="_blank">live demo</a> to see the theme in action. You can <a href="https://wordpress.org/themes/toivo-lite/" target="_blank">download</a> it for free from WordPress.org or get additional features and support with the <a href="https://foxland.fi/downloads/toivo/" target="_blank">commercial version</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 May 2015 03:31:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:40;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: How Barış Ünver Lives and Works with Censorship in Turkey";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43060";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"http://wptavern.com/how-baris-unver-lives-and-works-with-censorship-in-turkey";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1235:"<p>Doc Pop of Torquemag.io has <a href="http://torquemag.io/a-wordpress-developer-on-censorship-in-turkey/">published a great article</a> featuring WordPress developer, Barış Ünver. Ünver is 27 years old and a <a href="http://tutsplus.com/authors/baris-unver">Tuts+ author</a> living in Ankara, the capital of Turkey. In the article, Ünver describes what it&#8217;s like to live and work in Turkey. When asked whether WordPress being blocked in Turkey is a regular occurrence, he responded:</p>\n<blockquote><p>It’s not extremely common, but we experience downtime on large websites like Facebook, YouTube, and Twitter a couple times each year. WordPress.com is actually one of the first websites that was <a href="http://ma.tt/2007/08/blocked-in-turkey/" target="_blank">blocked back in 2007</a>—you can read the story here.</p></blockquote>\n<p>There are other interesting tidbits within the article as well such as the number of people who know how to use VPN&#8217;s as if it&#8217;s common knowledge. Ünver also provides insight into the tools used to get around censorship. If the country you live in blocked access to WordPress.com or WordPress.org, what tools, services, and systems would you use to get around it?</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 30 Apr 2015 19:07:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:64:"WPTavern: WPWeekly Episode 190 – Women in WordPress Roundtable";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:44:"http://wptavern.com?p=43111&preview_id=43111";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"http://wptavern.com/wpweekly-episode-190-women-in-wordpress-roundtable";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1837:"<p>This week&#8217;s episode of WordPress Weekly features <a href="http://www.web-savvy-marketing.com/">Rebbeca Gill</a>, <a href="http://www.bourncreative.com/">Jennifer Bourn</a>, and <a href="http://www.carriedils.com/">Carrie Dils</a> to casually discuss women in WordPress, women in tech, and a variety of other topics.</p>\n<p>The guests share their personal experiences of being involved in the WordPress community. We discuss how important it is to act responsibly, especially during WordCamp after parties which are business related events. Near the end of the discussion, the guests share tips and advice on how women can get more involved and meet influential members of the WordPress community.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="http://wptavern.com/wordpress-4-2-powell-is-now-available-for-download">WordPress 4.2 “Powell” is Now Available for Download</a><br />\n<a href="http://wptavern.com/wordpress-4-2-1-released-to-patch-comment-exploit-vulnerability">WordPress 4.2.1 Released to Patch Comment Exploit Vulnerability</a><br />\n<a href="http://wptavern.com/managewp-launches-wordpress-events-hub">ManageWP Launches WordPress Events Hub</a></p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, May 6th 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 #190:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 30 Apr 2015 18:41:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:42;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:110:"WPTavern: WordPress 4.3 to Focus on Mobile Experience, Admin UI, Better Passwords, and Customizer Improvements";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43084";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:117:"http://wptavern.com/wordpress-4-3-to-focus-on-mobile-experience-admin-ui-better-passwords-and-customizer-improvements";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4866:"<p><a href="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/04/notes.jpg" rel="prettyphoto[43084]"><img src="http://i0.wp.com/wptavern.com/wp-content/uploads/2015/04/notes.jpg?resize=960%2C456" alt="notes" class="aligncenter size-full wp-image-43107" /></a></p>\n<p>WordPress 4.3 development <a href="https://make.wordpress.org/core/2015/04/28/wordpress-4-3-kickoff/" target="_blank">kicked off</a> this week with release lead <a href="https://make.wordpress.org/core/author/obenland/" target="_blank">Konstantin Obenland</a> at the helm. The main focus of this release will be to improve the experience of using WordPress on touch and small-screen devices. Contributors will also be renewing efforts to improve the Admin UI and the Network Admin UI, particularly as it relates to the experience on narrow screens and responsive list tables.</p>\n<h3>Customizer Design and Architectural Improvements</h3>\n<p>The customizer will also be getting some attention. Weston Ruter <a href="https://weston.ruter.net/2015/04/29/customizer-features-for-wordpress-4-3-kickoff/" target="_blank">published</a> a summary of the three areas he proposes tackling:</p>\n<ul>\n<li><strong>Customizer Partial Refresh:</strong> This <a href="https://wordpress.org/plugins/customize-partial-refresh/" target="_blank">feature plugin</a> aims to refresh parts of a Customizer preview instead of reloading the entire page when a setting changed without transport=postMessage.</li>\n<li><strong>Customizer Transactions:</strong> This proposal is dependent on the Partial Refresh and involves re-architecting the customizer to make way for the possibility of feature plugins like scheduled settings, setting revisions, and drafted/pending settings.</li>\n<li><strong>Customizer Concurrency/Locking:</strong> This <a href="https://core.trac.wordpress.org/ticket/31436" target="_blank">proposal</a> would add concurrency/locking support to prevent multiple users from overwriting each other&#8217;s changes while working in the customizer.</li>\n</ul>\n<p>Nick Halsey also has a few ideas he is proposing for iterating on customizer development that was completed in 4.2.</p>\n<p>&#8220;I would like to aim for adding theme install in 4.3, which would require a shiny install process, and shiny updates could work into that well too,&#8221; he said. Halsey is aiming to have a functional and tested proposal ready before the scheduled time to decide on which features to merge in to 4.3.</p>\n<p>He&#8217;s also hoping to renew work on <a href="https://core.trac.wordpress.org/ticket/31336" target="_blank">Customizer UI design changes</a>, which would separate navigation from the options UI by removing accordion behavior for a better experience. It will be interesting to see how these changes, if selected to merge into 4.3, affect theme developer&#8217;s <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options" target="_blank">adoption of the customizer</a>.</p>\n<h3>Better Passwords Coming to WordPress 4.3</h3>\n<p>Mark Jaquith will be spearheading an effort to improve password creation in WordPress 4.3 and discussion will take place in the <a href="https://wordpress.slack.com/archives/core-passwords" target="_blank">#core-passwords</a> channel on Slack. The first leg of his proposal would make “user chooses own password” non-default so that a user can choose his own password or opt to allow WordPress to generate one.</p>\n<p>Jaquith is also proposing that the <a href="http://wptavern.com/ridiculously-smart-password-meter-coming-to-wordpress-3-7" target="_blank">password strength meter</a>, added in WordPress 3.7, offer feedback on why a user&#8217;s selected password might be measured as weak.</p>\n<p>&#8220;Simple feedback like &#8216;too short — add more characters!&#8217;, &#8216;Try adding some numbers and symbols!&#8217;,&#8221; he suggested. &#8220;Not only that, we could actually make the addition for them, show them their password attempt with some additions that would make it better.&#8221;</p>\n<p>Also, Jaquith proposes adding an option to make the password entry visible, eliminating the need for entering it twice. The fourth and final leg of his password improvement proposal is a major and long-overdue step toward improving the security of WordPress.</p>\n<p>&#8220;Let’s not send passwords via e-mail anymore; it’s insecure,&#8221; he said &#8220;We’re not getting around &#8216;full access to e-mail means you can reset,&#8217; but we can stop passwords from sitting around in e-mail accounts forever.&#8221;</p>\n<p>Contributors are aiming to release WordPress 4.3 on Tuesday, August 18th. Follow the <a href="https://make.wordpress.org/core/version-4-3-project-schedule/" target="_blank">project schedule</a> for approximate dates for feature merge, betas, and release candidate(s).</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 30 Apr 2015 17:19:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:43;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:42:"Matt: Brunello Cucinelli, King of Cashmere";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=44990";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:57:"http://ma.tt/2015/04/brunello-cucinelli-king-of-cashmere/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:685:"<blockquote><p>I want to take a step backward. Who remembers the last email they sent yesterday? No one. Or the last text message. Emperor Hadrian used to say, <i>“</i>The daily business, the daily life, the daily chores, kills the human being.<i>“</i> I’m not interested in daily chores. We have now swapped information for knowledge, which is not the same thing. I do not want to know. I’m not online. I don’t even have a computer.</p></blockquote>\n<p>Om has an incredible <a href="http://pi.co/brunello-cucinelli-2/">interview with Brunello Cucinelli on Pi.co</a>, which I&#8217;d recommend for everyone but especially people interested in design or entrepreneurship.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 30 Apr 2015 06:55:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:44;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:81:"WPTavern: Data Shows 24% of Themes Hosted on WordPress.org Support the Customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=43064";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"http://wptavern.com/only-24-of-themes-hosted-on-wordpress-org-support-the-customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2914:"<p><a href="https://twitter.com/aaronjorbin">Aaron Jorbin</a>, who contributes to WordPress core on a regular basis, has published a script called <a href="https://github.com/aaronjorbin/WordPress-Theme-Directory-Slurper">WordPress Theme Directory Slurper</a>. The PHP based script downloads and updates a copy of the latest stable version of every theme in the <a href="http://wordpress.org/themes/">WordPress.org theme directory</a>. Devin Price put the script to good use and has <a href="http://wptheming.com/2015/04/theme-repository-data/">published a series of data points</a> related to the theme directory.</p>\n<p>It took Price 112 minutes to run the script and download nearly 4GB of theme code. In his report, Price answers the following questions:</p>\n<ul>\n<li>How many themes are based on Underscores?</li>\n<li>How many themes are on WordPress.org?</li>\n<li>How many themes have <em>lite</em> in their name?</li>\n<li>How many themes use the latest WordPress functions?</li>\n<li>How many themes add an options page?</li>\n<li>How many themes use a bundled options framework?</li>\n<li>How many themes use TGM Activation?</li>\n</ul>\n<h2>How Many Themes Support the Customizer?</h2>\n<p>Last week, <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options">we reported on a significant change</a> to the WordPress theme directory guidelines. Beginning on April 22nd, themes submitted to the WordPress.org theme directory will have to use the customizer to build theme options. Themes already hosted in the directory have six months to comply before the Theme Review Team will enforce the new requirement.</p>\n<p>By searching the directory for themes that use <code>$wp_customize-&gt;add_control</code>, Price was able to determine that <strong>761 themes</strong> or <strong>23.8%</strong> currently support the customizer. The low number coincides with Justin Tadlock&#8217;s assessment <a href="https://make.wordpress.org/themes/2015/04/22/details-on-the-new-theme-settings-customizer-guideline/">that adoption has been slow</a>, especially when you consider that it was added three years ago to <a href="https://codex.wordpress.org/Version_3.4">WordPress 3.4</a>.</p>\n<p>One thing to keep in mind is that after the six month cutoff date, themes not using the customizer will still be able to be downloaded from and hosted on the directory. However, the theme code can not be updated unless it follows the new guidelines.</p>\n<p>It will be interesting to see what the data looks like three months from now as it would indicate how many and how fast, themes are adopting the customizer. Price is taking requests for what data you&#8217;d like to see, but if you want to do the research yourself, Jorbin&#8217;s <a href="https://github.com/aaronjorbin/WordPress-Theme-Directory-Slurper">Theme Directory Slurper</a> is available for free on GitHub.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 29 Apr 2015 23:16:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:45;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:70:"WPTavern: Postmatic Launches 100% Email-Based Commenting for WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42986";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:79:"http://wptavern.com/postmatic-launches-100-email-based-commenting-for-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6840:"<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/11/postmatic1.jpg" rel="prettyphoto[42986]"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2014/11/postmatic1.jpg?resize=810%2C378" alt="postmatic" class="aligncenter size-full wp-image-33866" /></a></p>\n<p><a href="https://gopostmatic.com" target="_blank">Postmatic</a> publicly launched its email-based commenting service today and is now officially out of beta. The free <a href="https://wordpress.org/plugins/postmatic/" target="_blank">plugin</a> aims to increase comment engagement by allowing readers to subscribe to new posts/comments via email and leave comments by simply hitting reply.</p>\n<p>Postmatic also launched a <a href="https://gopostmatic.com/premium/" target="_blank">commercial service</a> alongside version 1.0. For $9/month customers can add additional features, including guaranteed mail delivery for thousands of subscribers, fully responsive HTML email for posts and comments, support for oEmbed and shortcodes, and the ability to moderate comments from your inbox.</p>\n<h3>The Challenges of Sending Bulk Email</h3>\n<p>Since Postmatic is critically dependent on email delivery, founder Jason Lemieux and his team didn&#8217;t want to hassle with attempting to send it themselves.</p>\n<p>&#8220;Sending bulk email is really difficult to do correctly so we’ve partnered with folks that have already solved it,&#8221; he said. &#8220;All posts, comments, and otherwise are sent through a combination of both <a href="http://www.mailgun.com/" target="_blank">Mailgun</a> (by Rackspace) and <a href="https://www.mandrill.com/" target="_blank">Mandrill</a> (by Mailchimp).</p>\n<p>&#8220;This takes all of the uncertainty out of the equation and makes sending WordPress content to lists of tens of thousands of subscribers as easy as pie. Users don’t need to sign up for accounts with these services, change their dns or anything &#8211; we handle it all for them.&#8221;</p>\n<p>Lemieux reports that Postmatic had 1,200 sites in its beta program, ~500 of which they considered highly active. The individual installations were the easy part of the beta. Supporting the subscribers, which are more numerous, was the greatest challenge the team encountered.</p>\n<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/direct-reply.png" rel="prettyphoto[42986]"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/direct-reply.png?resize=259%2C500" alt="direct-reply" class="alignright size-large wp-image-43052" /></a><strong>&#8220;During beta we delivered posts and comments to roughly 46,000 unique subscribers and processed nearly 15,000 incoming comments</strong>,&#8221; he said. &#8220;These numbers are pretty small so we’ve built a system that scales and are ready to open the doors to everyone.&#8221;</p>\n<p>Notifications sent from Postmatic are two-way transactions designed to invite further discussion in comments, so the team has to be able to adequately support the myriad of email clients that people are using.</p>\n<p>&#8220;Email is complicated and as old as it is, it still seems like the wild west in a lot of ways,&#8221; Lemieux said. &#8220;We have to make sure that the post being delivered to an old-timer using Pine on his home-built Linux box communicates ideas just as well as the same post when seen in Gmail or on an Apple watch. Then we have to accept comment replies from all of these sources as well, which it turns out you can do. With a watch. Leave a comment. Go figure.&#8221;</p>\n<h3>The Future of Postmatic</h3>\n<p>Postmatic is a micro-startup that is mostly self-funded. Approximately 10 months before starting, the team knew that they wanted to be ready to quit their jobs when the time came.</p>\n<p>&#8220;We were fortunate to be able to squirrel away much of the funding we needed while also building it in tandem with our usual client work,&#8221; Lemieux said. &#8220;When we entered beta last fall and saw the reaction people were having to commenting by email we chose to stop taking on new client work, bring in a small amount of private funding, and go at it full time.&#8221;</p>\n<p>Postmatic&#8217;s tiny four-person team is what made this possible. Two members are full-time and the other two are currently part-time.</p>\n<p>As part of their quest to seamlessly join email and commenting, the team deemed it important to launch with <a href="http://wptavern.com/postmatic-now-supports-1-click-migration-of-subscribers-from-jetpack" target="_blank">importers for Jetpack</a>, Mailpoet, and Mailchimp. This makes the transition easier for site administrators who are already hooked into more traditional comment subscription services. Postmatic also has a few more high priority items on the roadmap.</p>\n<p>&#8220;The first is to support sites with high publishing frequency by enabling digests,&#8221; Lemieux said. &#8220;We have some fantastic ideas about how to do this in the new world of email commenting that will be of huge benefit to publishers and readers both.</p>\n<p>&#8220;As we move into the world of professional publishing we’ll also need a diversity of templates. Rolling in a template library or template builder is the plan there. Both of those things are next on our list.&#8221;</p>\n<p>The team behind Postmatic is investing heavily in 100% email commenting because they believe that innovation in WordPress comments is long overdue.</p>\n<p>&#8220;Every comment system needs email to some degree,&#8221; Lemieux said. &#8220;Livefyre, Disqus, Jetpack &#8211; all send an email notification (if subscribed) that a new comment has been posted. But you still have to jump over to a blog to reply and post a comment. It&#8217;s not always possible to do so, nor is it easy on mobile &#8211; which has become so important.</p>\n<p>&#8220;Postmatic takes that out of the equation &#8211; notification leads to reply, leads to blog comment, in one seamless action. Why wouldn&#8217;t you want email commenting to work like that?&#8221;</p>\n<p>Email commenting and post notifications are available in the <a href="https://wordpress.org/plugins/postmatic/" target="_blank">free plugin</a>, but these features are just the beginning of how Postmatic is aiming to revolutionize WordPress commenting.</p>\n<p>&#8220;The debate about the usefulness of comments in WordPress rages on while email marketing and automation has become a very hot area,&#8221;  Lemieux said. &#8220;But really the WordPress comments system is an email automation platform just waiting to happen.&#8221;</p>\n<p>If you&#8217;re curious about what it&#8217;s like to participate in comments without ever leaving your inbox, Postmatic has a <a href="https://gopostmatic.com/2015/04/try-the-magic-right-now/" target="_blank">live demo</a> available where you can try it out.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 29 Apr 2015 16:33:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:49:"WPTavern: WP REST API Version 2.0 Beta 1 Released";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42955";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wptavern.com/wp-rest-api-version-2-0-beta-1-released";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2217:"<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/wp-rest-api.jpg" rel="prettyphoto[42955]"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/wp-rest-api.jpg?resize=1025%2C469" alt="wp-rest-api" class="aligncenter size-full wp-image-43000" /></a></p>\n<p>Contributors on the <a href="https://github.com/WP-API/WP-API" target="_blank">WP REST API</a> project have released <a href="https://github.com/WP-API/WP-API/releases/tag/2.0-beta1" target="_blank">version 2.0 beta 1</a>, named after Simpsons character <a href="https://www.youtube.com/watch?v=g9MTejMEUJU" target="_blank">Ralph Wiggum</a>. This release is not backwards compatible with version 1, but project lead Ryan McCue  <a href="https://make.wordpress.org/core/2015/04/29/wp-rest-api-version-2-0-beta-1/" target="_blank">assured developers</a> that it is a direct continuation and that the fundamentals of the API haven&#8217;t changed.</p>\n<p><a href="http://v2.wp-api.org" target="_blank">Documentation for version 2</a> is now in progress, starting with basic schema docs, and the site has a section that outlines the <a href="http://v2.wp-api.org/changes-beta-1.html" target="_blank">changes in 2.0 Beta 1</a> internals and externals. It also includes an <a href="http://v2.wp-api.org/changes-beta-1.html#migrating-endpoints-from-v1-to-v2" target="_blank">example</a> for migrating endpoints from version 1 code to version 2.</p>\n<p>Compatibility with future beta releases is not guaranteed and this release comes with a note of caution for testers:</p>\n<blockquote><p>While we believe the API is now stable enough for public testing, we may continue to break the API in the future as we improve it further. Only use the API in development, and do not use version 2 in production environments.</p></blockquote>\n<p>Version 2.0 beta 1 had 23 contributors and many generous companies donated employee time to the project. This is a major milestone for the WP REST API on its journey to being proposed for inclusion in WordPress core. Check out the project&#8217;s <a href="https://github.com/WP-API/WP-API/issues/571" target="_blank">core merge plan</a> to follow the progress and view steps as they are completed.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 29 Apr 2015 05:42:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:47;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:83:"WPTavern: WordPress Plugins Created by JP Bot May Not be Maintained After June 2015";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42901";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:93:"http://wptavern.com/wordpress-plugins-created-by-jp-bot-may-not-be-maintained-after-june-2015";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2225:"<p>In late 2014, we went <a href="http://wptavern.com/jp-bot-the-silent-bot-behind-the-jetpack-module-extraction-plugins">behind the scenes</a> with <a href="http://ahs.pw/" target="_blank">Anas Sulaiman</a> who goes by the WordPress.org username of <a href="https://profiles.wordpress.org/wpjp/">JP Bot.</a> Sulaiman is responsible for creating six WordPress plugins that are alternatives to popular Jetpack modules. We received a tip from a reader that the plugins will soon be retired. When browsing to any of the six plugins on WordPress.org, the following message is displayed:</p>\n<blockquote><p>Retiring on June 2015. JP plugins will not be maintained after the end of June 2015. Thanks for everyone who used these plugins. Special thanks for those who gave good ratings.</p></blockquote>\n<p>I asked Sulaiman why he&#8217;s retiring his plugins at the end of June. &#8220;As I said in the interview in 2014, I make sure my projects stay alive when I can no longer work on them. Now, I can hardly find the time to keep JP plugins up to date; hence, I posted that notice in the hope that someone from the community would step up and take the wheel,&#8221; he responded.</p>\n<p><a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2014/11/jp-bot-plugins.jpg" rel="prettyphoto[42901]"><img class="aligncenter size-full wp-image-33603" src="http://i2.wp.com/wptavern.com/wp-content/uploads/2014/11/jp-bot-plugins.jpg?resize=700%2C222" alt="jp-bot-plugins" /></a>Sulaiman confirmed that someone has taken over his plugins but has not worked on them for over a month. He remains hopeful that the person is still motivated. &#8220;Anyways, if no one would seriously pick up JP plugins, I&#8217;m considering updating them every six months, or perhaps quarterly or so. After all, there are 4000+ users who are counting on them,&#8221; he said.</p>\n<p>I suggested that he add the <a href="http://wptavern.com/adopt-me-plugin-tag-is-now-in-use-on-wordpress-org">adopt-me tag</a> to his plugins to increase the chances an interested party will take them over. If you use any of the plugins developed by JP Bot, I highly encourage you to keep tabs on what happens after June 2015 as you might need to find an alternative.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 29 Apr 2015 03:31:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:48:"WPTavern: ManageWP Launches WordPress Events Hub";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42960";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:58:"http://wptavern.com/managewp-launches-wordpress-events-hub";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3382:"<p>There are a variety of WordPress events that take place around the world where users learn WordPress in person. Some are <a href="http://central.wordcamp.org/schedule/">WordCamps</a>, <a href="http://wordpress.meetup.com/">meetups</a>, and others are WordPress specific but don&#8217;t use the WordCamp branding. Until now, there has not been an easy way to see all WordPress events on one page. <a href="https://managewp.org/">ManageWP.org</a> has <a href="https://managewp.org/articles/9696/launching-wordpress-events-hub">launched</a> a WordPress <a href="https://managewp.org/events/">Events Hub</a> which displays WordCamps, meetups, and non-WordCamps on the same page using a map overlay.</p>\n<a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/04/EventsAcrossTheCountry.png" rel="prettyphoto[42960]"><img class="size-full wp-image-42974" src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/04/EventsAcrossTheCountry.png?resize=982%2C924" alt="Events Across the US" /></a>Events Across the US\n<p>Vladimir Prelovac, Founder and CEO of <a href="https://managewp.com/">ManageWP.com</a>, explains why he created the site:</p>\n<blockquote><p>I was travelling the US last year and wanted to see what WordPress events I could attend along the route and there was no elegant solution to this problem. WordCamp Central lists only WordCamps without a map showing their location. There are also numerous meetups as well as non-WordCamp conferences like LoopConf, CaboPress, ThemeConf that are not listed anywhere. So I decided to build it.</p></blockquote>\n<p>Only registered users to ManageWP.org are able to create new events. On the event creation screen, there are fields to add an event&#8217;s address, name, type, date, URL, Twitter account, and Twitter hashtag. You can also add speakers as well. I found creating a WordPress meetup a little confusing since I had to set a start and end date.</p>\n<a href="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/04/CreateNewEventScreen.png" rel="prettyphoto[42960]"><img class="size-full wp-image-42980" src="http://i2.wp.com/wptavern.com/wp-content/uploads/2015/04/CreateNewEventScreen.png?resize=994%2C838" alt="Event Creation Screen" /></a>Event Creation Screen\n<p>I think the event type should be the second field underneath the event&#8217;s name. I&#8217;d also like to see a set of fields or options added that are specific to the type of event being held. For example, if it&#8217;s a meetup, there&#8217;s no reason to have an end date. Instead, the end date should be replaced with an option to set a time.</p>\n<p>There should also be a way to configure repeating events, similar to how Meetup.com does it. This way, I don&#8217;t have to remember to edit the event&#8217;s details every month. Events are not moderated, allowing submissions to appear immediately on the map.</p>\n<p>As the number of WordPress events across the world increases, it&#8217;s nice to have a resource that unites them on one map. In future iterations, it would be cool if users could create an itinerary. The itinerary would be saved to the user&#8217;s account and would be sharable through a URL. This way, users could get together and plan a road trip together.</p>\n<p>Prelovac is keeping a close eye on the comments of this post, so after you check out the events hub, please leave your feedback in the comments.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 28 Apr 2015 19:33:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:49;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:103:"WPTavern: Redux and Kirki Frameworks Join Forces to Provide Better Support for the WordPress Customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=42937";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:113:"http://wptavern.com/redux-and-kirki-frameworks-join-forces-to-provide-better-support-for-the-wordpress-customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4653:"<p><a href="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/redux-kirki-frameworks.jpg" rel="prettyphoto[42937]"><img src="http://i1.wp.com/wptavern.com/wp-content/uploads/2015/04/redux-kirki-frameworks.jpg?resize=876%2C407" alt="redux-kirki-frameworks" class="aligncenter size-full wp-image-42981" /></a></p>\n<p>In light of the WordPress Theme Review team&#8217;s recent decision to <a href="http://wptavern.com/wordpress-org-now-requires-theme-authors-to-use-the-customizer-to-build-theme-options" target="_blank">enforce the use of the native customizer</a> for themes in the official directory, the folks behind the Redux and Kirki frameworks are joining forces to better support developers for the new requirement.</p>\n<p><a href="http://reduxframework.com/" target="_blank">Redux</a>, which is built on the WordPress Settings API, is one of the most widely used options frameworks for themes and plugins, with WordPress.org reporting 90,000+ active installs. It supports a multitude of field types, custom error handling, and custom field and validation types, but is not currently compatible with the Customizer API.</p>\n<p>That&#8217;s where <a href="http://kirki.org/" target="_blank">Kirki</a> is stepping in to offer a framework for <a href="http://wptavern.com/kirki-a-free-plugin-to-style-the-wordpress-customizer-and-add-advanced-controls" target="_blank">advanced controls using the customizer</a>. Kirki, created by <a href="http://aristeides.com/">Aristeides Stathopoulos</a>, makes it easy to style the customizer to be a more natural extension of your theme and add panels and sections with more than 20 different <a href="http://kirki.org/#field-types" target="_blank">field types</a>.</p>\n<p>Both open source frameworks and their developers will be <a href="http://redux.io/" target="_blank">working together</a> to offer &#8220;the most powerful WordPress frameworks under one roof.&#8221; They are currently working on making the data output the same as well as creating a converter API for Redux developers. The eventual goal is that Redux will cover both custom settings panels as well as the customizer, while Kirki will be focused purely on the customizer.</p>\n<p>Redux lead developer <a href="https://twitter.com/simplerain" target="_blank">Dovy Paukstys</a> was one of the most vocal opponents of the decision to make the customizer a requirement for WordPress.org theme options. His position is that it limits developers and cannot provide a complete replacement for the Settings API.</p>\n<p>&#8220;The announcement of April 22, 2015 regarding the requirements for WP.org theme submission bothered me,&#8221; Paukstys said. &#8220;I had a decision to make; work to make Redux work fully in the customizer, or reduce our community.</p>\n<p>&#8220;I then remembered the Kirki project and decided to ping Ari. We discussed the possibility of bringing Kirki into the Redux organization and progressing from there.&#8221; Kirki is joining Redux as part of the team, but it will be maintained as a separate framework.</p>\n<p>&#8220;Kirki will always be light, with a smaller footprint,&#8221; Paukstys said. &#8220;There are no plans to turn Kirki into the Swiss army knife that Redux is. However, Kirki will be modified slightly.&#8221;</p>\n<p>The Redux and Kirki teams plan to share concepts and development time in order to ensure that they can mirror the data output between the two frameworks.</p>\n<p>&#8220;I am also in the process of creating the Kirki API, which will allow Redux devs to take their current config and use it with Kirki, rather than Redux,&#8221; Paukstys said. This will enable developers who have built themes using Redux to easily port their theme options over to Kirki for compatibility with the customizer.</p>\n<p>Eventually, Redux will support both custom options panels using the Settings API and the customizer. In the meantime, Paukstys took the initiative to partner with Kirki to make sure Redux users won&#8217;t be hung out to dry with the new WordPress.org requirements.</p>\n<p>&#8220;Kirki is a great solution for Customizer only themes,&#8221; Paukstys said. &#8220;There&#8217;s room enough on our team for both frameworks. Both serve a unique audience.&#8221;</p>\n<p>As the WordPress Theme Review team seems firmly set on upholding its controversial decision regarding the customizer, Redux and other frameworks have no other choice but to fall in line.</p>\n<p>&#8220;This community is too divided,&#8221; Paukstys said. &#8220;We prefer working together, rather than working apart. We believe greater things will come in the future moving forward together, as a team.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 28 Apr 2015 17:51:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:10:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 13 May 2015 20:15:16 GMT";s:12:"content-type";s:8:"text/xml";s:14:"content-length";s:6:"233001";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Wed, 13 May 2015 20:00:16 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";s:13:"accept-ranges";s:5:"bytes";}s:5:"build";s:14:"20130911110210";}', 'no');
