diff --git a/dev.gwtd3.sql b/dev.gwtd3.sql index 8950293..4c68044 100644 --- a/dev.gwtd3.sql +++ b/dev.gwtd3.sql @@ -3,7 +3,7 @@ -- https://www.phpmyadmin.net/ -- -- Host: db40.grserver.gr:3306 --- Generation Time: Jul 26, 2017 at 12:49 AM +-- Generation Time: Jul 26, 2017 at 12:37 PM -- Server version: 10.0.31-MariaDB -- PHP Version: 5.6.27 @@ -182,7 +182,7 @@ INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload` (76, 'comment_order', 'asc', 'yes'), (77, 'sticky_posts', 'a:0:{}', 'yes'), (78, 'widget_categories', 'a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}', 'yes'), -(79, 'widget_text', 'a:3:{i:1;a:0:{}i:2;a:3:{s:5:\"title\";s:0:\"\";s:4:\"text\";s:519:\"\";s:6:\"filter\";s:7:\"content\";}s:12:\"_multiwidget\";i:1;}', 'yes'), +(79, 'widget_text', 'a:3:{i:1;a:0:{}i:2;a:3:{s:5:\"title\";s:0:\"\";s:4:\"text\";s:421:\"\";s:6:\"filter\";s:7:\"content\";}s:12:\"_multiwidget\";i:1;}', 'yes'), (80, 'widget_rss', 'a:2:{i:1;a:0:{}s:12:\"_multiwidget\";i:1;}', 'yes'), (81, 'uninstall_plugins', 'a:0:{}', 'no'), (82, 'timezone_string', '', 'yes'), @@ -210,10 +210,10 @@ INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload` (104, 'widget_media_video', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), (105, 'widget_tag_cloud', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), (106, 'widget_nav_menu', 'a:1:{s:12:\"_multiwidget\";i:1;}', 'yes'), -(107, 'cron', 'a:4:{i:1501050292;a:3:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1501050522;a:1:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1501051818;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}s:7:\"version\";i:2;}', 'yes'), +(107, 'cron', 'a:4:{i:1501093492;a:3:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1501136922;a:1:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1501138218;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}s:7:\"version\";i:2;}', 'yes'), (108, 'theme_mods_twentyseventeen', 'a:3:{s:18:\"custom_css_post_id\";i:-1;s:18:\"nav_menu_locations\";a:4:{s:6:\"menu-1\";i:2;s:18:\"footer-menu-social\";i:0;s:12:\"primary-menu\";i:2;s:9:\"gwtd-menu\";i:4;}s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1501012026;s:4:\"data\";a:4:{s:19:\"wp_inactive_widgets\";a:1:{i:0;s:6:\"text-2\";}s:18:\"orphaned_widgets_1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:18:\"orphaned_widgets_2\";a:0:{}s:18:\"orphaned_widgets_3\";a:0:{}}}}', 'yes'), -(112, '_site_transient_update_core', 'O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:57:\"https://downloads.wordpress.org/release/wordpress-4.8.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:57:\"https://downloads.wordpress.org/release/wordpress-4.8.zip\";s:10:\"no_content\";s:68:\"https://downloads.wordpress.org/release/wordpress-4.8-no-content.zip\";s:11:\"new_bundled\";s:69:\"https://downloads.wordpress.org/release/wordpress-4.8-new-bundled.zip\";s:7:\"partial\";b:0;s:8:\"rollback\";b:0;}s:7:\"current\";s:3:\"4.8\";s:7:\"version\";s:3:\"4.8\";s:11:\"php_version\";s:5:\"5.2.4\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"4.7\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1501011036;s:15:\"version_checked\";s:3:\"4.8\";s:12:\"translations\";a:0:{}}', 'no'), -(117, '_site_transient_update_themes', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1501012023;s:7:\"checked\";a:1:{s:5:\"gwtd3\";s:5:\"1.0.1\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}}', 'no'), +(112, '_site_transient_update_core', 'O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:57:\"https://downloads.wordpress.org/release/wordpress-4.8.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:57:\"https://downloads.wordpress.org/release/wordpress-4.8.zip\";s:10:\"no_content\";s:68:\"https://downloads.wordpress.org/release/wordpress-4.8-no-content.zip\";s:11:\"new_bundled\";s:69:\"https://downloads.wordpress.org/release/wordpress-4.8-new-bundled.zip\";s:7:\"partial\";b:0;s:8:\"rollback\";b:0;}s:7:\"current\";s:3:\"4.8\";s:7:\"version\";s:3:\"4.8\";s:11:\"php_version\";s:5:\"5.2.4\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"4.7\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1501050474;s:15:\"version_checked\";s:3:\"4.8\";s:12:\"translations\";a:0:{}}', 'no'), +(117, '_site_transient_update_themes', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1501050480;s:7:\"checked\";a:1:{s:5:\"gwtd3\";s:5:\"1.0.3\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}}', 'no'), (119, '_site_transient_timeout_browser_8ce1bea2f653ca2ce71bdf6183bef333', '1501568923', 'no'), (120, '_site_transient_browser_8ce1bea2f653ca2ce71bdf6183bef333', 'a:9:{s:8:\"platform\";s:7:\"Windows\";s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:13:\"59.0.3071.115\";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;}', 'no'), (122, 'can_compress_scripts', '1', 'no'), @@ -230,25 +230,27 @@ INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload` (165, '_site_transient_timeout_available_translations', '1501011868', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (166, '_site_transient_available_translations', 'a:108:{s:2:\"af\";a:8:{s:8:\"language\";s:2:\"af\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-23 21:35:47\";s:12:\"english_name\";s:9:\"Afrikaans\";s:11:\"native_name\";s:9:\"Afrikaans\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/af.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"af\";i:2;s:3:\"afr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Gaan voort\";}}s:2:\"ar\";a:8:{s:8:\"language\";s:2:\"ar\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-09 03:55:46\";s:12:\"english_name\";s:6:\"Arabic\";s:11:\"native_name\";s:14:\"العربية\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/ar.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:2;s:3:\"ara\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:3:\"ary\";a:8:{s:8:\"language\";s:3:\"ary\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-01-26 15:42:35\";s:12:\"english_name\";s:15:\"Moroccan Arabic\";s:11:\"native_name\";s:31:\"العربية المغربية\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.5/ary.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:3;s:3:\"ary\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:2:\"as\";a:8:{s:8:\"language\";s:2:\"as\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-22 18:59:07\";s:12:\"english_name\";s:8:\"Assamese\";s:11:\"native_name\";s:21:\"অসমীয়া\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/as.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"as\";i:2;s:3:\"asm\";i:3;s:3:\"asm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:0:\"\";}}s:2:\"az\";a:8:{s:8:\"language\";s:2:\"az\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-06 00:09:27\";s:12:\"english_name\";s:11:\"Azerbaijani\";s:11:\"native_name\";s:16:\"Azərbaycan dili\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/az.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:2;s:3:\"aze\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Davam\";}}s:3:\"azb\";a:8:{s:8:\"language\";s:3:\"azb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-12 20:34:31\";s:12:\"english_name\";s:17:\"South Azerbaijani\";s:11:\"native_name\";s:29:\"گؤنئی آذربایجان\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/azb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:3;s:3:\"azb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:3:\"bel\";a:8:{s:8:\"language\";s:3:\"bel\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-17 20:31:44\";s:12:\"english_name\";s:10:\"Belarusian\";s:11:\"native_name\";s:29:\"Беларуская мова\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/translation/core/4.8/bel.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"be\";i:2;s:3:\"bel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Працягнуць\";}}s:5:\"bg_BG\";a:8:{s:8:\"language\";s:5:\"bg_BG\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-18 19:16:01\";s:12:\"english_name\";s:9:\"Bulgarian\";s:11:\"native_name\";s:18:\"Български\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/bg_BG.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bg\";i:2;s:3:\"bul\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Напред\";}}s:5:\"bn_BD\";a:8:{s:8:\"language\";s:5:\"bn_BD\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-04 16:58:43\";s:12:\"english_name\";s:7:\"Bengali\";s:11:\"native_name\";s:15:\"বাংলা\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/bn_BD.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"bn\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:23:\"এগিয়ে চল.\";}}s:2:\"bo\";a:8:{s:8:\"language\";s:2:\"bo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-05 09:44:12\";s:12:\"english_name\";s:7:\"Tibetan\";s:11:\"native_name\";s:21:\"བོད་ཡིག\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/bo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bo\";i:2;s:3:\"tib\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"མུ་མཐུད།\";}}s:5:\"bs_BA\";a:8:{s:8:\"language\";s:5:\"bs_BA\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-04 20:20:28\";s:12:\"english_name\";s:7:\"Bosnian\";s:11:\"native_name\";s:8:\"Bosanski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/bs_BA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bs\";i:2;s:3:\"bos\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:2:\"ca\";a:8:{s:8:\"language\";s:2:\"ca\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-16 11:47:56\";s:12:\"english_name\";s:7:\"Catalan\";s:11:\"native_name\";s:7:\"Català\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/ca.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ca\";i:2;s:3:\"cat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:3:\"ceb\";a:8:{s:8:\"language\";s:3:\"ceb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-02 17:25:51\";s:12:\"english_name\";s:7:\"Cebuano\";s:11:\"native_name\";s:7:\"Cebuano\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/ceb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"ceb\";i:3;s:3:\"ceb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Padayun\";}}s:5:\"cs_CZ\";a:8:{s:8:\"language\";s:5:\"cs_CZ\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-12 08:46:26\";s:12:\"english_name\";s:5:\"Czech\";s:11:\"native_name\";s:12:\"Čeština‎\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/cs_CZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cs\";i:2;s:3:\"ces\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:11:\"Pokračovat\";}}s:2:\"cy\";a:8:{s:8:\"language\";s:2:\"cy\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-14 13:21:24\";s:12:\"english_name\";s:5:\"Welsh\";s:11:\"native_name\";s:7:\"Cymraeg\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/cy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cy\";i:2;s:3:\"cym\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Parhau\";}}s:5:\"da_DK\";a:8:{s:8:\"language\";s:5:\"da_DK\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-14 23:24:44\";s:12:\"english_name\";s:6:\"Danish\";s:11:\"native_name\";s:5:\"Dansk\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/da_DK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"da\";i:2;s:3:\"dan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Fortsæt\";}}s:5:\"de_CH\";a:8:{s:8:\"language\";s:5:\"de_CH\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 21:25:12\";s:12:\"english_name\";s:20:\"German (Switzerland)\";s:11:\"native_name\";s:17:\"Deutsch (Schweiz)\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/de_CH.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:14:\"de_CH_informal\";a:8:{s:8:\"language\";s:14:\"de_CH_informal\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 08:50:23\";s:12:\"english_name\";s:30:\"German (Switzerland, Informal)\";s:11:\"native_name\";s:21:\"Deutsch (Schweiz, Du)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/4.8/de_CH_informal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:5:\"de_DE\";a:8:{s:8:\"language\";s:5:\"de_DE\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-08 16:08:42\";s:12:\"english_name\";s:6:\"German\";s:11:\"native_name\";s:7:\"Deutsch\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/de_DE.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:12:\"de_DE_formal\";a:8:{s:8:\"language\";s:12:\"de_DE_formal\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-15 19:58:49\";s:12:\"english_name\";s:15:\"German (Formal)\";s:11:\"native_name\";s:13:\"Deutsch (Sie)\";s:7:\"package\";s:69:\"https://downloads.wordpress.org/translation/core/4.8/de_DE_formal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:3:\"dzo\";a:8:{s:8:\"language\";s:3:\"dzo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-06-29 08:59:03\";s:12:\"english_name\";s:8:\"Dzongkha\";s:11:\"native_name\";s:18:\"རྫོང་ཁ\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/dzo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"dz\";i:2;s:3:\"dzo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:0:\"\";}}s:2:\"el\";a:8:{s:8:\"language\";s:2:\"el\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-21 18:05:57\";s:12:\"english_name\";s:5:\"Greek\";s:11:\"native_name\";s:16:\"Ελληνικά\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/el.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"el\";i:2;s:3:\"ell\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Συνέχεια\";}}s:5:\"en_NZ\";a:8:{s:8:\"language\";s:5:\"en_NZ\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-17 08:09:19\";s:12:\"english_name\";s:21:\"English (New Zealand)\";s:11:\"native_name\";s:21:\"English (New Zealand)\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/en_NZ.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_CA\";a:8:{s:8:\"language\";s:5:\"en_CA\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-23 16:48:27\";s:12:\"english_name\";s:16:\"English (Canada)\";s:11:\"native_name\";s:16:\"English (Canada)\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/en_CA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_ZA\";a:8:{s:8:\"language\";s:5:\"en_ZA\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-01-26 15:53:43\";s:12:\"english_name\";s:22:\"English (South Africa)\";s:11:\"native_name\";s:22:\"English (South Africa)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/en_ZA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_GB\";a:8:{s:8:\"language\";s:5:\"en_GB\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 07:18:00\";s:12:\"english_name\";s:12:\"English (UK)\";s:11:\"native_name\";s:12:\"English (UK)\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/en_GB.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_AU\";a:8:{s:8:\"language\";s:5:\"en_AU\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 05:14:35\";s:12:\"english_name\";s:19:\"English (Australia)\";s:11:\"native_name\";s:19:\"English (Australia)\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/en_AU.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"eo\";a:8:{s:8:\"language\";s:2:\"eo\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-27 10:36:23\";s:12:\"english_name\";s:9:\"Esperanto\";s:11:\"native_name\";s:9:\"Esperanto\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/eo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eo\";i:2;s:3:\"epo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Daŭrigi\";}}s:5:\"es_MX\";a:8:{s:8:\"language\";s:5:\"es_MX\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-16 17:22:41\";s:12:\"english_name\";s:16:\"Spanish (Mexico)\";s:11:\"native_name\";s:19:\"Español de México\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/es_MX.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"es\";i:2;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_VE\";a:8:{s:8:\"language\";s:5:\"es_VE\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-07 00:53:01\";s:12:\"english_name\";s:19:\"Spanish (Venezuela)\";s:11:\"native_name\";s:21:\"Español de Venezuela\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/es_VE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"es\";i:2;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_GT\";a:8:{s:8:\"language\";s:5:\"es_GT\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-01-26 15:54:37\";s:12:\"english_name\";s:19:\"Spanish (Guatemala)\";s:11:\"native_name\";s:21:\"Español de Guatemala\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/es_GT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"es\";i:2;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CO\";a:8:{s:8:\"language\";s:5:\"es_CO\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-01-26 15:54:37\";s:12:\"english_name\";s:18:\"Spanish (Colombia)\";s:11:\"native_name\";s:20:\"Español de Colombia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/es_CO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"es\";i:2;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_PE\";a:8:{s:8:\"language\";s:5:\"es_PE\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-09 09:36:22\";s:12:\"english_name\";s:14:\"Spanish (Peru)\";s:11:\"native_name\";s:17:\"Español de Perú\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/es_PE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"es\";i:2;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CL\";a:8:{s:8:\"language\";s:5:\"es_CL\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-28 20:09:49\";s:12:\"english_name\";s:15:\"Spanish (Chile)\";s:11:\"native_name\";s:17:\"Español de Chile\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/es_CL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"es\";i:2;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_AR\";a:8:{s:8:\"language\";s:5:\"es_AR\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-20 00:55:30\";s:12:\"english_name\";s:19:\"Spanish (Argentina)\";s:11:\"native_name\";s:21:\"Español de Argentina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/es_AR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"es\";i:2;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_ES\";a:8:{s:8:\"language\";s:5:\"es_ES\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-18 10:53:33\";s:12:\"english_name\";s:15:\"Spanish (Spain)\";s:11:\"native_name\";s:8:\"Español\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/es_ES.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"es\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"et\";a:8:{s:8:\"language\";s:2:\"et\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 16:37:11\";s:12:\"english_name\";s:8:\"Estonian\";s:11:\"native_name\";s:5:\"Eesti\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/et.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"et\";i:2;s:3:\"est\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Jätka\";}}s:2:\"eu\";a:8:{s:8:\"language\";s:2:\"eu\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-21 08:00:44\";s:12:\"english_name\";s:6:\"Basque\";s:11:\"native_name\";s:7:\"Euskara\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/eu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eu\";i:2;s:3:\"eus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Jarraitu\";}}s:5:\"fa_IR\";a:8:{s:8:\"language\";s:5:\"fa_IR\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-09 15:50:45\";s:12:\"english_name\";s:7:\"Persian\";s:11:\"native_name\";s:10:\"فارسی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/fa_IR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fa\";i:2;s:3:\"fas\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:2:\"fi\";a:8:{s:8:\"language\";s:2:\"fi\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-08 18:25:22\";s:12:\"english_name\";s:7:\"Finnish\";s:11:\"native_name\";s:5:\"Suomi\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/fi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fi\";i:2;s:3:\"fin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Jatka\";}}s:5:\"fr_BE\";a:8:{s:8:\"language\";s:5:\"fr_BE\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-23 06:47:57\";s:12:\"english_name\";s:16:\"French (Belgium)\";s:11:\"native_name\";s:21:\"Français de Belgique\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/fr_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_FR\";a:8:{s:8:\"language\";s:5:\"fr_FR\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-07 13:48:37\";s:12:\"english_name\";s:15:\"French (France)\";s:11:\"native_name\";s:9:\"Français\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/fr_FR.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"fr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_CA\";a:8:{s:8:\"language\";s:5:\"fr_CA\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-05 17:58:06\";s:12:\"english_name\";s:15:\"French (Canada)\";s:11:\"native_name\";s:19:\"Français du Canada\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/fr_CA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:2:\"gd\";a:8:{s:8:\"language\";s:2:\"gd\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-08-23 17:41:37\";s:12:\"english_name\";s:15:\"Scottish Gaelic\";s:11:\"native_name\";s:9:\"Gàidhlig\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/gd.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"gd\";i:2;s:3:\"gla\";i:3;s:3:\"gla\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"Lean air adhart\";}}s:5:\"gl_ES\";a:8:{s:8:\"language\";s:5:\"gl_ES\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-17 20:40:15\";s:12:\"english_name\";s:8:\"Galician\";s:11:\"native_name\";s:6:\"Galego\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/gl_ES.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gl\";i:2;s:3:\"glg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"gu\";a:8:{s:8:\"language\";s:2:\"gu\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-07 12:07:46\";s:12:\"english_name\";s:8:\"Gujarati\";s:11:\"native_name\";s:21:\"ગુજરાતી\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/gu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gu\";i:2;s:3:\"guj\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:31:\"ચાલુ રાખવું\";}}s:3:\"haz\";a:8:{s:8:\"language\";s:3:\"haz\";s:7:\"version\";s:5:\"4.4.2\";s:7:\"updated\";s:19:\"2015-12-05 00:59:09\";s:12:\"english_name\";s:8:\"Hazaragi\";s:11:\"native_name\";s:15:\"هزاره گی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.4.2/haz.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"haz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:5:\"he_IL\";a:8:{s:8:\"language\";s:5:\"he_IL\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 13:33:29\";s:12:\"english_name\";s:6:\"Hebrew\";s:11:\"native_name\";s:16:\"עִבְרִית\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/he_IL.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"he\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"המשך\";}}s:5:\"hi_IN\";a:8:{s:8:\"language\";s:5:\"hi_IN\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-16 17:29:16\";s:12:\"english_name\";s:5:\"Hindi\";s:11:\"native_name\";s:18:\"हिन्दी\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/hi_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hi\";i:2;s:3:\"hin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"जारी\";}}s:2:\"hr\";a:8:{s:8:\"language\";s:2:\"hr\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-19 08:19:39\";s:12:\"english_name\";s:8:\"Croatian\";s:11:\"native_name\";s:8:\"Hrvatski\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/hr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hr\";i:2;s:3:\"hrv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:5:\"hu_HU\";a:8:{s:8:\"language\";s:5:\"hu_HU\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-26 15:48:39\";s:12:\"english_name\";s:9:\"Hungarian\";s:11:\"native_name\";s:6:\"Magyar\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/hu_HU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hu\";i:2;s:3:\"hun\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Folytatás\";}}s:2:\"hy\";a:8:{s:8:\"language\";s:2:\"hy\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-03 16:21:10\";s:12:\"english_name\";s:8:\"Armenian\";s:11:\"native_name\";s:14:\"Հայերեն\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/hy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hy\";i:2;s:3:\"hye\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Շարունակել\";}}s:5:\"id_ID\";a:8:{s:8:\"language\";s:5:\"id_ID\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-12 12:20:50\";s:12:\"english_name\";s:10:\"Indonesian\";s:11:\"native_name\";s:16:\"Bahasa Indonesia\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/id_ID.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"id\";i:2;s:3:\"ind\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Lanjutkan\";}}s:5:\"is_IS\";a:8:{s:8:\"language\";s:5:\"is_IS\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-04-13 13:55:54\";s:12:\"english_name\";s:9:\"Icelandic\";s:11:\"native_name\";s:9:\"Íslenska\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/is_IS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"is\";i:2;s:3:\"isl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Áfram\";}}s:5:\"it_IT\";a:8:{s:8:\"language\";s:5:\"it_IT\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-04 13:01:37\";s:12:\"english_name\";s:7:\"Italian\";s:11:\"native_name\";s:8:\"Italiano\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/it_IT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"it\";i:2;s:3:\"ita\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:2:\"ja\";a:8:{s:8:\"language\";s:2:\"ja\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-25 11:16:15\";s:12:\"english_name\";s:8:\"Japanese\";s:11:\"native_name\";s:9:\"日本語\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/ja.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"ja\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"続ける\";}}s:5:\"ka_GE\";a:8:{s:8:\"language\";s:5:\"ka_GE\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-12 09:20:11\";s:12:\"english_name\";s:8:\"Georgian\";s:11:\"native_name\";s:21:\"ქართული\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/ka_GE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ka\";i:2;s:3:\"kat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"გაგრძელება\";}}s:3:\"kab\";a:8:{s:8:\"language\";s:3:\"kab\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-16 18:44:50\";s:12:\"english_name\";s:6:\"Kabyle\";s:11:\"native_name\";s:9:\"Taqbaylit\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/translation/core/4.8/kab.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"kab\";i:3;s:3:\"kab\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Kemmel\";}}s:2:\"km\";a:8:{s:8:\"language\";s:2:\"km\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-07 02:07:59\";s:12:\"english_name\";s:5:\"Khmer\";s:11:\"native_name\";s:27:\"ភាសាខ្មែរ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/km.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"km\";i:2;s:3:\"khm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"បន្ត\";}}s:5:\"ko_KR\";a:8:{s:8:\"language\";s:5:\"ko_KR\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-19 07:08:35\";s:12:\"english_name\";s:6:\"Korean\";s:11:\"native_name\";s:9:\"한국어\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/ko_KR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ko\";i:2;s:3:\"kor\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"계속\";}}s:3:\"ckb\";a:8:{s:8:\"language\";s:3:\"ckb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-26 15:48:25\";s:12:\"english_name\";s:16:\"Kurdish (Sorani)\";s:11:\"native_name\";s:13:\"كوردی‎\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/ckb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ku\";i:3;s:3:\"ckb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"به‌رده‌وام به‌\";}}s:2:\"lo\";a:8:{s:8:\"language\";s:2:\"lo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 09:59:23\";s:12:\"english_name\";s:3:\"Lao\";s:11:\"native_name\";s:21:\"ພາສາລາວ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/lo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lo\";i:2;s:3:\"lao\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"ຕໍ່​ໄປ\";}}s:5:\"lt_LT\";a:8:{s:8:\"language\";s:5:\"lt_LT\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-05 11:43:04\";s:12:\"english_name\";s:10:\"Lithuanian\";s:11:\"native_name\";s:15:\"Lietuvių kalba\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/lt_LT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lt\";i:2;s:3:\"lit\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Tęsti\";}}s:2:\"lv\";a:8:{s:8:\"language\";s:2:\"lv\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-03-17 20:40:40\";s:12:\"english_name\";s:7:\"Latvian\";s:11:\"native_name\";s:16:\"Latviešu valoda\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.5/lv.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lv\";i:2;s:3:\"lav\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Turpināt\";}}s:5:\"mk_MK\";a:8:{s:8:\"language\";s:5:\"mk_MK\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-01-26 15:54:41\";s:12:\"english_name\";s:10:\"Macedonian\";s:11:\"native_name\";s:31:\"Македонски јазик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/mk_MK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mk\";i:2;s:3:\"mkd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Продолжи\";}}s:5:\"ml_IN\";a:8:{s:8:\"language\";s:5:\"ml_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:43:32\";s:12:\"english_name\";s:9:\"Malayalam\";s:11:\"native_name\";s:18:\"മലയാളം\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ml_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ml\";i:2;s:3:\"mal\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"തുടരുക\";}}s:2:\"mn\";a:8:{s:8:\"language\";s:2:\"mn\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-12 07:29:35\";s:12:\"english_name\";s:9:\"Mongolian\";s:11:\"native_name\";s:12:\"Монгол\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/mn.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mn\";i:2;s:3:\"mon\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"Үргэлжлүүлэх\";}}s:2:\"mr\";a:8:{s:8:\"language\";s:2:\"mr\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-05 19:40:47\";s:12:\"english_name\";s:7:\"Marathi\";s:11:\"native_name\";s:15:\"मराठी\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/mr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mr\";i:2;s:3:\"mar\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"सुरु ठेवा\";}}s:5:\"ms_MY\";a:8:{s:8:\"language\";s:5:\"ms_MY\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-03-05 09:45:10\";s:12:\"english_name\";s:5:\"Malay\";s:11:\"native_name\";s:13:\"Bahasa Melayu\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/ms_MY.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ms\";i:2;s:3:\"msa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Teruskan\";}}s:5:\"my_MM\";a:8:{s:8:\"language\";s:5:\"my_MM\";s:7:\"version\";s:6:\"4.1.18\";s:7:\"updated\";s:19:\"2015-03-26 15:57:42\";s:12:\"english_name\";s:17:\"Myanmar (Burmese)\";s:11:\"native_name\";s:15:\"ဗမာစာ\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.1.18/my_MM.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"my\";i:2;s:3:\"mya\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:54:\"ဆက်လက်လုပ်ဆောင်ပါ။\";}}s:5:\"nb_NO\";a:8:{s:8:\"language\";s:5:\"nb_NO\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-26 11:11:30\";s:12:\"english_name\";s:19:\"Norwegian (Bokmål)\";s:11:\"native_name\";s:13:\"Norsk bokmål\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/nb_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nb\";i:2;s:3:\"nob\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Fortsett\";}}s:5:\"ne_NP\";a:8:{s:8:\"language\";s:5:\"ne_NP\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-23 11:30:58\";s:12:\"english_name\";s:6:\"Nepali\";s:11:\"native_name\";s:18:\"नेपाली\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/ne_NP.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ne\";i:2;s:3:\"nep\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:43:\"जारी राख्नुहोस्\";}}s:5:\"nl_BE\";a:8:{s:8:\"language\";s:5:\"nl_BE\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-20 17:04:00\";s:12:\"english_name\";s:15:\"Dutch (Belgium)\";s:11:\"native_name\";s:20:\"Nederlands (België)\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/nl_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:12:\"nl_NL_formal\";a:8:{s:8:\"language\";s:12:\"nl_NL_formal\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-02-16 13:24:21\";s:12:\"english_name\";s:14:\"Dutch (Formal)\";s:11:\"native_name\";s:20:\"Nederlands (Formeel)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/4.7.5/nl_NL_formal.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nl_NL\";a:8:{s:8:\"language\";s:5:\"nl_NL\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-18 18:26:58\";s:12:\"english_name\";s:5:\"Dutch\";s:11:\"native_name\";s:10:\"Nederlands\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/nl_NL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nn_NO\";a:8:{s:8:\"language\";s:5:\"nn_NO\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-08 13:05:53\";s:12:\"english_name\";s:19:\"Norwegian (Nynorsk)\";s:11:\"native_name\";s:13:\"Norsk nynorsk\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/nn_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nn\";i:2;s:3:\"nno\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Hald fram\";}}s:3:\"oci\";a:8:{s:8:\"language\";s:3:\"oci\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-02 13:47:38\";s:12:\"english_name\";s:7:\"Occitan\";s:11:\"native_name\";s:7:\"Occitan\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/oci.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"oc\";i:2;s:3:\"oci\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Contunhar\";}}s:5:\"pa_IN\";a:8:{s:8:\"language\";s:5:\"pa_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-16 05:19:43\";s:12:\"english_name\";s:7:\"Punjabi\";s:11:\"native_name\";s:18:\"ਪੰਜਾਬੀ\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/pa_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pa\";i:2;s:3:\"pan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"ਜਾਰੀ ਰੱਖੋ\";}}s:5:\"pl_PL\";a:8:{s:8:\"language\";s:5:\"pl_PL\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-19 13:38:04\";s:12:\"english_name\";s:6:\"Polish\";s:11:\"native_name\";s:6:\"Polski\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/pl_PL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pl\";i:2;s:3:\"pol\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Kontynuuj\";}}s:2:\"ps\";a:8:{s:8:\"language\";s:2:\"ps\";s:7:\"version\";s:6:\"4.1.18\";s:7:\"updated\";s:19:\"2015-03-29 22:19:48\";s:12:\"english_name\";s:6:\"Pashto\";s:11:\"native_name\";s:8:\"پښتو\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.1.18/ps.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ps\";i:2;s:3:\"pus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:19:\"دوام ورکړه\";}}s:5:\"pt_PT\";a:8:{s:8:\"language\";s:5:\"pt_PT\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-23 10:24:37\";s:12:\"english_name\";s:21:\"Portuguese (Portugal)\";s:11:\"native_name\";s:10:\"Português\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/pt_PT.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"pt_BR\";a:8:{s:8:\"language\";s:5:\"pt_BR\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-13 23:57:05\";s:12:\"english_name\";s:19:\"Portuguese (Brazil)\";s:11:\"native_name\";s:20:\"Português do Brasil\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/pt_BR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pt\";i:2;s:3:\"por\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:3:\"rhg\";a:8:{s:8:\"language\";s:3:\"rhg\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-16 13:03:18\";s:12:\"english_name\";s:8:\"Rohingya\";s:11:\"native_name\";s:8:\"Ruáinga\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/rhg.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"rhg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:0:\"\";}}s:5:\"ro_RO\";a:8:{s:8:\"language\";s:5:\"ro_RO\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-15 10:32:19\";s:12:\"english_name\";s:8:\"Romanian\";s:11:\"native_name\";s:8:\"Română\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/ro_RO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ro\";i:2;s:3:\"ron\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuă\";}}s:5:\"ru_RU\";a:8:{s:8:\"language\";s:5:\"ru_RU\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 13:54:09\";s:12:\"english_name\";s:7:\"Russian\";s:11:\"native_name\";s:14:\"Русский\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/ru_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ru\";i:2;s:3:\"rus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продолжить\";}}s:3:\"sah\";a:8:{s:8:\"language\";s:3:\"sah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-21 02:06:41\";s:12:\"english_name\";s:5:\"Sakha\";s:11:\"native_name\";s:14:\"Сахалыы\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/sah.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"sah\";i:3;s:3:\"sah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Салҕаа\";}}s:5:\"si_LK\";a:8:{s:8:\"language\";s:5:\"si_LK\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 06:00:52\";s:12:\"english_name\";s:7:\"Sinhala\";s:11:\"native_name\";s:15:\"සිංහල\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/si_LK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"si\";i:2;s:3:\"sin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:44:\"දිගටම කරගෙන යන්න\";}}s:5:\"sk_SK\";a:8:{s:8:\"language\";s:5:\"sk_SK\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 09:02:13\";s:12:\"english_name\";s:6:\"Slovak\";s:11:\"native_name\";s:11:\"Slovenčina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/sk_SK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sk\";i:2;s:3:\"slk\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Pokračovať\";}}s:5:\"sl_SI\";a:8:{s:8:\"language\";s:5:\"sl_SI\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-08 15:29:14\";s:12:\"english_name\";s:9:\"Slovenian\";s:11:\"native_name\";s:13:\"Slovenščina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/sl_SI.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sl\";i:2;s:3:\"slv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Nadaljuj\";}}s:2:\"sq\";a:8:{s:8:\"language\";s:2:\"sq\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-04-24 08:35:30\";s:12:\"english_name\";s:8:\"Albanian\";s:11:\"native_name\";s:5:\"Shqip\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.5/sq.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sq\";i:2;s:3:\"sqi\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Vazhdo\";}}s:5:\"sr_RS\";a:8:{s:8:\"language\";s:5:\"sr_RS\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-08 11:06:53\";s:12:\"english_name\";s:7:\"Serbian\";s:11:\"native_name\";s:23:\"Српски језик\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/sr_RS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sr\";i:2;s:3:\"srp\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:14:\"Настави\";}}s:5:\"sv_SE\";a:8:{s:8:\"language\";s:5:\"sv_SE\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-18 17:49:44\";s:12:\"english_name\";s:7:\"Swedish\";s:11:\"native_name\";s:7:\"Svenska\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/sv_SE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sv\";i:2;s:3:\"swe\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Fortsätt\";}}s:3:\"szl\";a:8:{s:8:\"language\";s:3:\"szl\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-24 19:58:14\";s:12:\"english_name\";s:8:\"Silesian\";s:11:\"native_name\";s:17:\"Ślōnskŏ gŏdka\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/szl.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"szl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:13:\"Kōntynuować\";}}s:5:\"ta_IN\";a:8:{s:8:\"language\";s:5:\"ta_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:22:47\";s:12:\"english_name\";s:5:\"Tamil\";s:11:\"native_name\";s:15:\"தமிழ்\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ta_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ta\";i:2;s:3:\"tam\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"தொடரவும்\";}}s:2:\"te\";a:8:{s:8:\"language\";s:2:\"te\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-26 15:47:39\";s:12:\"english_name\";s:6:\"Telugu\";s:11:\"native_name\";s:18:\"తెలుగు\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/te.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"te\";i:2;s:3:\"tel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"కొనసాగించు\";}}s:2:\"th\";a:8:{s:8:\"language\";s:2:\"th\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-26 15:48:43\";s:12:\"english_name\";s:4:\"Thai\";s:11:\"native_name\";s:9:\"ไทย\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/th.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"th\";i:2;s:3:\"tha\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"ต่อไป\";}}s:2:\"tl\";a:8:{s:8:\"language\";s:2:\"tl\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-30 02:38:08\";s:12:\"english_name\";s:7:\"Tagalog\";s:11:\"native_name\";s:7:\"Tagalog\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/tl.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tl\";i:2;s:3:\"tgl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Magpatuloy\";}}s:5:\"tr_TR\";a:8:{s:8:\"language\";s:5:\"tr_TR\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-19 13:54:12\";s:12:\"english_name\";s:7:\"Turkish\";s:11:\"native_name\";s:8:\"Türkçe\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/tr_TR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tr\";i:2;s:3:\"tur\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Devam\";}}s:5:\"tt_RU\";a:8:{s:8:\"language\";s:5:\"tt_RU\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-20 20:20:50\";s:12:\"english_name\";s:5:\"Tatar\";s:11:\"native_name\";s:19:\"Татар теле\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/tt_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tt\";i:2;s:3:\"tat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:17:\"дәвам итү\";}}s:3:\"tah\";a:8:{s:8:\"language\";s:3:\"tah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-06 18:39:39\";s:12:\"english_name\";s:8:\"Tahitian\";s:11:\"native_name\";s:10:\"Reo Tahiti\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/tah.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"ty\";i:2;s:3:\"tah\";i:3;s:3:\"tah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:0:\"\";}}s:5:\"ug_CN\";a:8:{s:8:\"language\";s:5:\"ug_CN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-05 09:23:39\";s:12:\"english_name\";s:6:\"Uighur\";s:11:\"native_name\";s:9:\"Uyƣurqə\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ug_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ug\";i:2;s:3:\"uig\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:26:\"داۋاملاشتۇرۇش\";}}s:2:\"uk\";a:8:{s:8:\"language\";s:2:\"uk\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-01 22:52:09\";s:12:\"english_name\";s:9:\"Ukrainian\";s:11:\"native_name\";s:20:\"Українська\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/uk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uk\";i:2;s:3:\"ukr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продовжити\";}}s:2:\"ur\";a:8:{s:8:\"language\";s:2:\"ur\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-02 09:17:00\";s:12:\"english_name\";s:4:\"Urdu\";s:11:\"native_name\";s:8:\"اردو\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/ur.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ur\";i:2;s:3:\"urd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:19:\"جاری رکھیں\";}}s:5:\"uz_UZ\";a:8:{s:8:\"language\";s:5:\"uz_UZ\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-05-13 09:55:38\";s:12:\"english_name\";s:5:\"Uzbek\";s:11:\"native_name\";s:11:\"O‘zbekcha\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/uz_UZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uz\";i:2;s:3:\"uzb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:11:\"Davom etish\";}}s:2:\"vi\";a:8:{s:8:\"language\";s:2:\"vi\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-06-15 11:24:18\";s:12:\"english_name\";s:10:\"Vietnamese\";s:11:\"native_name\";s:14:\"Tiếng Việt\";s:7:\"package\";s:59:\"https://downloads.wordpress.org/translation/core/4.8/vi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"vi\";i:2;s:3:\"vie\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Tiếp tục\";}}s:5:\"zh_HK\";a:8:{s:8:\"language\";s:5:\"zh_HK\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-16 05:48:05\";s:12:\"english_name\";s:19:\"Chinese (Hong Kong)\";s:11:\"native_name\";s:16:\"香港中文版 \";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/zh_HK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}s:5:\"zh_TW\";a:8:{s:8:\"language\";s:5:\"zh_TW\";s:7:\"version\";s:3:\"4.8\";s:7:\"updated\";s:19:\"2017-07-05 10:14:12\";s:12:\"english_name\";s:16:\"Chinese (Taiwan)\";s:11:\"native_name\";s:12:\"繁體中文\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8/zh_TW.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}s:5:\"zh_CN\";a:8:{s:8:\"language\";s:5:\"zh_CN\";s:7:\"version\";s:5:\"4.7.5\";s:7:\"updated\";s:19:\"2017-01-26 15:54:45\";s:12:\"english_name\";s:15:\"Chinese (China)\";s:11:\"native_name\";s:12:\"简体中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.5/zh_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"继续\";}}}', 'no'), -(173, '_site_transient_update_plugins', 'O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1501011218;s:7:\"checked\";a:2:{s:19:\"akismet/akismet.php\";s:5:\"3.3.2\";s:9:\"hello.php\";s:3:\"1.6\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:1:{s:9:\"hello.php\";O:8:\"stdClass\":6:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:3:\"1.6\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/plugin/hello-dolly.1.6.zip\";}}}', 'no'), +(173, '_site_transient_update_plugins', 'O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1501050478;s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:0:{}}', 'no'), (174, '_site_transient_timeout_community-events-3822290fe898b4d66e08f381a43eeeb3', '1501054258', 'no'), (175, '_site_transient_community-events-3822290fe898b4d66e08f381a43eeeb3', 'a:2:{s:8:\"location\";a:1:{s:2:\"ip\";s:11:\"85.73.218.0\";}s:6:\"events\";a:1:{i:0;a:7:{s:4:\"type\";s:8:\"wordcamp\";s:5:\"title\";s:15:\"WordCamp Athens\";s:3:\"url\";s:32:\"https://2017.athens.wordcamp.org\";s:6:\"meetup\";N;s:10:\"meetup_url\";N;s:4:\"date\";s:19:\"2017-12-09 00:00:00\";s:8:\"location\";a:4:{s:8:\"location\";s:14:\"Athens, Greece\";s:7:\"country\";s:2:\"GR\";s:8:\"latitude\";d:37.980518699999998;s:9:\"longitude\";d:23.7540722;}}}}', 'no'), -(176, '_transient_timeout_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1501054259', 'no'); +(196, '_site_transient_timeout_theme_roots', '1501052276', 'no'), +(197, '_site_transient_theme_roots', 'a:1:{s:5:\"gwtd3\";s:7:\"/themes\";}', 'no'), +(200, '_site_transient_timeout_community-events-015d358de3e6df34dc7a72657a4971df', '1501104960', 'no'), +(201, '_site_transient_community-events-015d358de3e6df34dc7a72657a4971df', 'a:2:{s:8:\"location\";a:1:{s:2:\"ip\";s:10:\"77.69.15.0\";}s:6:\"events\";a:1:{i:0;a:7:{s:4:\"type\";s:8:\"wordcamp\";s:5:\"title\";s:15:\"WordCamp Athens\";s:3:\"url\";s:32:\"https://2017.athens.wordcamp.org\";s:6:\"meetup\";N;s:10:\"meetup_url\";N;s:4:\"date\";s:19:\"2017-12-09 00:00:00\";s:8:\"location\";a:4:{s:8:\"location\";s:14:\"Athens, Greece\";s:7:\"country\";s:2:\"GR\";s:8:\"latitude\";d:37.980518699999998;s:9:\"longitude\";d:23.7540722;}}}}', 'no'), +(202, '_transient_timeout_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1501104962', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES -(177, '_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:4:{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:\"Wed, 19 Jul 2017 19:50:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"en-US\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=4.9-alpha-41150\";s:7:\"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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"The Month in WordPress: June 2017\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2017/07/the-month-in-wordpress-june-2017/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Jul 2017 11:42: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in 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:34:\"https://wordpress.org/news/?p=4865\";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:342:\"We’re starting a new regular feature on this blog today. We’d like to keep everyone up-to-date about the happenings all across the WordPress open source project and highlight how you can get involved, so we’ll be posting a roundup of all the major WordPress news at the end of every month. Aside from other general […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:9225:\"

We’re starting a new regular feature on this blog today. We’d like to keep everyone up-to-date about the happenings all across the WordPress open source project and highlight how you can get involved, so we’ll be posting a roundup of all the major WordPress news at the end of every month.

\n

Aside from other general news, the three big events in June were the release of WordPress 4.8, WordCamp Europe 2017, and the WordPress Community Summit. Read on to hear more about these as well as other interesting stories from around the WordPress world.

\n
\n

WordPress 4.8

\n

On June 8, a week before the Community Summit and WordCamp Europe, WordPress 4.8 was released.You can read the Field Guide for a comprehensive overview of all the features of this release (the News and Events widget in the dashboard is one of the major highlights).

\n

Most people would either have their version auto-updated, or their hosts would have updated it for them. For the rest, the updates have gone smoothly with no major issues reported so far.

\n

This WordPress release saw contributions from 346 individuals; you can find their names in the announcement post. To get involved in building WordPress core, jump into the #core channel in the Making WordPress Slack group, and follow the Core team blog.

\n

WordCamp Europe 2017

\n

WordCamp Europe 2017 was held in Paris between June 15-17. The event began with a Contributor Day, followed by two days of talks and community goodness. The talks were live-streamed, but you can still catch all the recordings on WordPress.tv. The organisers also published a handy wrap-up of the event.

\n

WordCamp Europe exists to bring together the WordPress community from all over the continent, as well as to inspire local communities everywhere to get their own events going — to that end, the event was a great success, as a host of new meetup groups have popped up in the weeks following WordCamp Europe.

\n

The work that Contributor Day participants accomplished was both varied and valuable, covering all aspects of the WordPress project — have a look through the Make blogs for updates from each team.

\n

Finally, we also learned during the event that WordCamp Europe 2018 will be held in Belgrade, Serbia, continuing the tradition of exploring locations and communities across the continent.

\n

WordPress Community Summit

\n

The fourth WordPress Community Summit took place during the two days leading up to WordCamp Europe 2017. This event is an invite-only unconference where people from all over the WordPress community come together to discuss some of the more difficult issues in the community, as well as to make plans for the year ahead in each of the contribution teams.

\n

As the Summit is designed to be a safe space for all attendees, the notes from each discussion are in the process of being anonymized before we publish them on the Summit blog (so stay tuned – they’ll show up there over the next few weeks).

\n

You can already see the final list of topics that were proposed for the event here (although a few more were added during the course of the two day Summit).

\n

WordPress marketing push continues apace

\n

As part of the push to be more intentional in marketing WordPress (as per Matt Mullenweg’s 2016 State of the Word), the Marketing team has launched two significant drives to obtain more information about who uses WordPress and how that information can shape their outreach and messaging efforts.

\n

The team is looking for WordPress case studies and is asking users, agencies, and freelancers to take a WordPress usage survey. This will go a long way towards establishing a marketing base for WordPress as a platform and as a community — and many people in the community are looking forward to seeing this area develop further.

\n

To get involved in the WordPress Marketing team, you can visit their team blog.

\n

New Gutenberg editor available for testing

\n

For some time now, the Core team has been hard at work on a brand-new text editor for WordPress — this project has been dubbed “Gutenberg.” The project’s ultimate goal is to replace the existing TinyMCE editor, but for now it is in beta and available for public testing — you can download it here as a plugin and install it on any WordPress site.

\n

This feature is still in beta, so we don’t recommend using it on a production site. If you test it out, though, you’ll find that it is a wholly different experience to what you are used to in WordPress. It’s a more streamlined, altogether cleaner approach to the text-editing experience than we’ve had before, and something that many people are understandably excited about. Matt Mullenweg discussed the purpose of Gutenberg in more detail during his Q&A at WordCamp Europe.

\n

There are already a few reviews out from Brian Jackson at Kinsta, Aaron Jorbin, and Matt Cromwell (among many others). Keep in mind that the project is in constant evolution at this stage; when it eventually lands in WordPress core (probably in v5.0), it could look very different from its current iteration — that’s what makes this beta stage and user testing so important.

\n

To get involved with shaping the future of Gutenberg, please test it out, and join the #core-editor channel in the Making WordPress Slack group. You can also visit the project’s GitHub repository to report issues and contribute to the codebase.

\n
\n

Further reading:

\n\n

If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4865\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"WordPress 4.8 “Evans”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://wordpress.org/news/2017/06/evans/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 08 Jun 2017 14:49: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4770\";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:373:\"An Update with You in Mind Gear up for a more intuitive WordPress! Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard. New features in 4.8 add more ways for you to express yourself and represent your brand. Though some […]\";s: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:34144:\"

An Update with You in Mind

\n

\"\"

\n

Gear up for a more intuitive WordPress!

\n

Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard. New features in 4.8 add more ways for you to express yourself and represent your brand.

\n

Though some updates seem minor, they’ve been built by hundreds of contributors with you in mind. Get ready for new features you’ll welcome like an old friend: link improvements, three new media widgets covering images, audio, and video, an updated text widget that supports visual editing, and an upgraded news section in your dashboard which brings in nearby and upcoming WordPress events.

\n
\n

Exciting Widget Updates

\n

\"\"

\n

Image Widget

\n

Adding an image to a widget is now a simple task that is achievable for any WordPress user without needing to know code. Simply insert your image right within the widget settings. Try adding something like a headshot or a photo of your latest weekend adventure — and see it appear automatically.

\n

Video Widget

\n

A welcome video is a great way to humanize the branding of your website. You can now add any video from the Media Library to a sidebar on your site with the new Video widget. Use this to showcase a welcome video to introduce visitors to your site or promote your latest and greatest content.

\n

Audio Widget

\n

Are you a podcaster, musician, or avid blogger? Adding a widget with your audio file has never been easier. Upload your audio file to the Media Library, go to the widget settings, select your file, and you’re ready for listeners. This would be a easy way to add a more personal welcome message, too!

\n

Rich Text Widget

\n

This feature deserves a parade down the center of town! Rich-text editing capabilities are now native for Text widgets. Add a widget anywhere and format away. Create lists, add emphasis, and quickly and easily insert links. Have fun with your newfound formatting powers, and watch what you can accomplish in a short amount of time.

\n
\n

Link Boundaries

\n
\n

Have you ever tried updating a link, or the text around a link, and found you can’t seem to edit it correctly? When you edit the text after the link, your new text also ends up linked. Or you edit the text in the link, but your text ends up outside of it. This can be frustrating! With link boundaries, a great new feature, the process is streamlined and your links will work well. You’ll be happier. We promise.

\n
\n

Nearby WordPress Events

\n

\"\"

\n

Did you know that WordPress has a thriving offline community with groups meeting regularly in more than 400 cities around the world? WordPress now draws your attention to the events that help you continue improving your WordPress skills, meet friends, and, of course, publish!

\n

This is quickly becoming one of our favorite features. While you are in the dashboard (because you’re running updates and writing posts, right?) all upcoming WordCamps and official WordPress Meetups — local to you — will be displayed.

\n

Being part of the community can help you improve your WordPress skills and network with people you wouldn’t otherwise meet. Now you can easily find your local events just by logging in to your dashboard and looking at the new Events and News dashboard widget.

\n
\n

Even More Developer Happiness \"?\"

\n

More Accessible Admin Panel Headings

\n

New CSS rules mean extraneous content (like “Add New” links) no longer need to be included in admin-area headings. These panel headings improve the experience for people using assistive technologies.

\n

Removal of Core Support for WMV and WMA Files

\n

As fewer and fewer browsers support Silverlight, file formats which require the presence of the Silverlight plugin are being removed from core support. Files will still display as a download link, but will no longer be embedded automatically.

\n

Multisite Updates

\n

New capabilities have been introduced to 4.8 with an eye towards removing calls to
\nis_super_admin(). Additionally, new hooks and tweaks to more granularly control site and user counts per network have been added.

\n

Text-Editor JavaScript API

\n

With the addition of TinyMCE to the text widget in 4.8 comes a new JavaScript API for instantiating the editor after page load. This can be used to add an editor instance to any text area, and customize it with buttons and functions. Great for plugin authors!

\n

Media Widgets API

\n

The introduction of a new base media widget REST API schema to 4.8 opens up possibilities for even more media widgets (like galleries or playlists) in the future. The three new media widgets are powered by a shared base class that covers most of the interactions with the media modal. That class also makes it easier to create new media widgets and paves the way for more to come.

\n

Customizer Width Variable

\n

Rejoice! New responsive breakpoints have been added to the customizer sidebar to make it wider on high-resolution screens. Customizer controls should use percentage-based widths instead of pixels.

\n
\n

The Squad

\n

This release was led by Matt and Jeff Paul, with the help of the following fabulous folks. There are 346 contributors with props in this release, with 106 of them contributing for the first time. Pull up some Bill Evans on your music service of choice, and check out some of their profiles:

\n1naveengiri, 4nickpick, Aaron D. Campbell, Aaron Jorbin, abhishek, Abhishek Kumar, abrain, Adam Harley (Kawauso), Adam Silverstein, Adam Soucie, Afzal Multani, Ahmad Awais, ajoah, Alex Concha, Alex Floyd Marshall, Alex King, Alex Shiels, Andrea Fercia, Andrea Middleton, Andrew Nacin, Andrew Ozz, Andrew Rockwell, Andy Mercer, Ankit K Gupta, arena94, Arshid, Arun, asalce, ashokkumar24, Barry Ceelen, bcworkz, Bharat Kambariya, Blobfolio, bonger, Boone B. Gorges, Boro Sitnikovski, Brad Touesnard, Brady Vercher, Brandon Kraft, Brandon Lavigne, Bridget Willard, Bunty, Cami Kaos, Carl Alberto, Casey Driscoll, cazm, ccprog, Chandra Patel, chesio, chetansatasiya, Chirag Patel, Chouby, Chris Klosowski, Chris Mok, chriseverson, Christian Chung, Corey McKrill, Courtney P.K., Cristiano Zanca, csloisel, Curdin Krummenacher, Cyrus Collier, Daniel Bachhuber , Daniel Llewellyn, Daniele Scasciafratte, Darren Ethier (nerrad), Darshan_dj, darthaud, Daryl L. L. Houston (dllh), David A. Kennedy, David Anderson, David Binovec, David Herrera, David Shanske, davidbenton, designsimply, Dhanendran, Dharmesh Patel, Dhaval Parekh, dingo-d, Dion Hulse, Dominik Schilling, Dotan Cohen, DoubleH, DreamOn11, Drew Jaynes, Drivingralle, dspilka, Edwin Cromley, Ejner Galaz, Ella Iseulde Van Dorpe, emirpprime, Eric Andrew Lewis, Erick Hitter, Ethan Allen, Fabien Quatravaux, Felix Arntz, fibonaccina, Florian TIAR, Francesca Marano, Frank Neumann-Staude, Franz Josef Kaiser, Gabriel Maldonado, Garth Mortensen, Gary Cao, Gary Pendergast, Gennady Kovshenin, George Stephanis, Gustave F. Gerhardt, hedgefield, Helen Hou-Sandí, helgatheviking, Hristo Pandjarov, Ian Dunn, ig_communitysites, Igor Zinovyev, imath, Ipstenu (Mika Epstein), Irene Strikkers, Ivan Stefanov, ivantedja, J.D. Grimes, Jack Reichert, Jake Spurlock, James Nylen, Jaydeep Rami, jazbek, Jeff Bowen, Jeff Farthing, Jeff Paul, Jeffrey de Wit, Jen Miller, Jeremy Felt, Jeremy Pry, jesseenterprises, Jignesh Nakrani, Jip Moors, jjcomack, Joe Dolson, Joe Hoyle, Joe McGill, John Blackbourn, John James Jacoby, John Regan, Jonathan Desrosiers, Jonny Harris, Joost de Valk, Josepha, Josh Pollock, Juhi Saxena, Justin Kopepasah, Justin McGuire, Justin Tucker, K.Adam White, kafleg, Kailey (trepmal), karinedo, Kathryn, kaushik, Keanan Koppenhaver, keesiemeijer, Kelly Dwan, Kite, kjellr, Konstantin Kovshenin, Konstantin Obenland, kostasx, kubik-rubik, KUCKLU, Lance Willett, Laurel Fulford, Lee Willis, leemon, LewisCowles, LiamMcArthur, Lucas Stark, lukasbesch, Luke Cavanagh, Maedah Batool, Mahesh Prajapati, mantismamita, Marin Atanasov, Mario Aguiar, Mark Jaquith, Mark Root-Wiley, Mark Uraine, Marko Heijnen, Matheus Martins, MatheusGimenez, mathieuhays, matias, Matt Wiebe, Matthew Boynes, Matthew Haines-Young, mattyrob, Maxime Culea, Mayo Moriyama, Mayur Keshwani, Mel Choyce, Menaka S., Michael Arestad, michalzuber, michelleweber, Miina Sikk, Mike Crantea, Mike Hansen, Mike Jolley, Mike Little, Mike Nelson, Mike Schroder, Milan Dinić, Milind More, Mithun Raval, MMDeveloper, Mohammad Jangda, mohanjith, monikarao, Morgan Estes, moto hachi ( mt8.biz ), MrGregWaugh, mschadegg, Muhammet Arslan, MULTIDOTS, Naoko Takano, Naomi C. Bush, Nate Reist, Ned Zimmerman, Nick Halsey , Nicklas Sundberg, Nikhil Chavan, Nitin Kevadiya, Nitish Kaila, nobremarcos, NoseGraze, nullvariable, odyssey, page-carbajal, Pascal Birchler, Paul Bearne, Paul Biron, Paul de Wouters, Paul Ryan, pavelevap, Payton Swick, pdufour, Perdaan, Peter Wilson, Philip John, Piotr Delawski, Piotr Soluch, postpostmodern, Pranali Patel, Pratik Shrestha, Presskopp, printsachen1, Priyanka Behera, prosti, ptbello, Rachel Baker, Rafael Ehlers, raggedrobins, raisonon, Rami Yushuvaev, ramiabraham, ranh, RC Lations, redrambles, reidbusi, reldev, rellect, RENAUT, rensw90, reportermike, Rian Rietveld, Riddhi Mehta, Robbie Cahill, Robert O\'Rourke, Robin Cornett, runciters, Ryan Boren, Ryan McCue, Ryan Welcher, Sagar Bhatt, Sagar Jadhav, Sagar Prajapati, Sal Ferrarello, Samantha Miller, Sami Keijonen, Samuel Sidler, Sanket Parmar, sathyapulse, sboisvert, Scott Reilly, Scott Taylor, Sean Hayes, Sebastian Pisula, Sergey Biryukov, sfpt, sgolemon, Shady Sharaf, shanee, Shashwat Mittal, shazahm1, shulard, slbmeh, Soren Wrede, Stanimir Stoyanov, Stephane Daury (stephdau), Stephen Edgar, Stephen Harris, Steven Word, Storm Rockwell, Sudar Muthu, Supercoder, Sybre Waaijer, szaqal21, taggon, Takayuki Miyauchi, Takayuki Miyoshi, Tammie Lister, technopolitica, teinertb, tejas5989, terwdan, tharsheblows, theMikeD, thepelkus, Thorsten Frommen, Timmy Crawford, Timothy Jacobs, timph, tmatsuur, tomdxw, Topher, Travis Smith, triplejumper12, truongwp, tymvie, Ulrich, Utkarsh, vaishu.agola27, vortfu, Weston Ruter, wpfo, xrmx, ze3kr, and Zeljko Ascic.\n

 

\n

Finally, thanks to all the community translators who worked on WordPress 4.8. Their efforts bring WordPress 4.8 fully translated to 38 languages at release time with more on the way.

\n

Do you want to report on WordPress 4.8? We’ve compiled a press kit featuring information about the release features, and some media assets to help you along.

\n

If you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress — we hope you enjoy!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4770\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 4.8 Release Candidate 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:69:\"https://wordpress.org/news/2017/06/wordpress-4-8-release-candidate-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 01 Jun 2017 22:13: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4765\";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:336:\"The second release candidate for WordPress 4.8 is now available. To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip). We’ve made a handful of changes since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Mel Choyce\";s: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:1173:\"

The second release candidate for WordPress 4.8 is now available.

\n

To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

\n

We’ve made a handful of changes since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the Beta 1, Beta 2, and RC1 blog posts.

\n

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

\n

Happy testing!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4765\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"WordPress 4.8 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/2017/05/wordpress-4-8-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 25 May 2017 23:04: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:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4758\";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:325:\"The release candidate for WordPress 4.8 is now available. 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.8 on Thursday, June 8, but we need your help to get there. If you haven’t tested 4.8 yet, […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Mel Choyce\";s: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:2365:\"

The release candidate for WordPress 4.8 is now available.

\n

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.8 on Thursday, June 8, but we need your help to get there. If you haven’t tested 4.8 yet, now is the time!

\n

To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

\n

We’ve made a handful of changes since releasing Beta 2 earlier this week. For more details about what’s new in version 4.8, check out the Beta 1 and Beta 2 blog posts.

\n

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

\n

Developers, please test your plugins and themes against WordPress 4.8 and update your plugin’s Tested up to version in the readme to 4.8. If you find compatibility problems please be sure to post to the support forums so we can figure those out before the final release – we work hard to avoid breaking things. An in-depth field guide to developer-focused changes is coming soon on the core development blog.

\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

\n

This release’s haiku is courtesy of @matveb:

\n

Érrese uno
\nCien veces y más
\nErre ce dos

\n

Thanks for your continued help testing out the latest versions of WordPress.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4758\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 4.8 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/2017/05/wordpress-4-8-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 23 May 2017 00:02: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4749\";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.8 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.8, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Mel Choyce\";s: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:1621:\"

WordPress 4.8 Beta 2 is now available!

\n

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.8, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

\n

For more information on what’s new in 4.8, check out the Beta 1 blog post. Since then, we’ve made over 50 changes in Beta 2.

\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

\n

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

\n

WordPress four point eight
\nOne step closer to release
\nPlease test Beta 2!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4749\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:39:\"\n \n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 4.7.5 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/2017/05/wordpress-4-7-5/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 16 May 2017 22:39:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4734\";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:373:\"WordPress 4.7.5 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7.4 and earlier are affected by six security issues: Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing. Improper handling of post meta data values in the XML-RPC […]\";s: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:\"Pascal Birchler\";s: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:2349:\"

WordPress 4.7.5 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

WordPress versions 4.7.4 and earlier are affected by six security issues:

\n
    \n
  1. Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing.
  2. \n
  3. Improper handling of post meta data values in the XML-RPC API. Reported by Sam Thomas.
  4. \n
  5. Lack of capability checks for post meta data in the XML-RPC API. Reported by Ben Bidner of the WordPress Security Team.
  6. \n
  7. A Cross Site Request Forgery (CSRF)  vulnerability was discovered in the filesystem credentials dialog. Reported by Yorick Koster.
  8. \n
  9. A cross-site scripting (XSS) vulnerability was discovered when attempting to upload very large files. Reported by Ronni Skansing.
  10. \n
  11. A cross-site scripting (XSS) vulnerability was discovered related to the Customizer. Reported by Weston Ruter of the WordPress Security Team.
  12. \n
\n

Thank you to the reporters of these issues for practicing responsible disclosure.

\n

In addition to the security issues above, WordPress 4.7.5 contains 3 maintenance fixes to the 4.7 release series. For more information, see the release notes or consult the list of changes.

\n

Download WordPress 4.7.5 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.7.5.

\n

Thanks to everyone who contributed to 4.7.5.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4734\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"WordPress Now on HackerOne\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://wordpress.org/news/2017/05/wordpress-now-on-hackerone/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 15 May 2017 16:02: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:8:\"category\";a:1:{i:0;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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4730\";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:322:\"WordPress has grown a lot over the last thirteen years – it now powers more than 28% of the top ten million sites on the web. During this growth, each team has worked hard to continually improve their tools and processes. Today, the WordPress Security Team is happy to announce that WordPress is now officially […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Aaron D. Campbell\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:1715:\"

WordPress has grown a lot over the last thirteen years – it now powers more than 28% of the top ten million sites on the web. During this growth, each team has worked hard to continually improve their tools and processes. Today, the WordPress Security Team is happy to announce that WordPress is now officially on HackerOne!

\n

HackerOne is a platform for security researchers to securely and responsibly report vulnerabilities to our team. It provides tools that improve the quality and consistency of communication with reporters, and will reduce the time spent on responding to commonly reported issues. This frees our team to spend more time working on improving the security of WordPress.

\n

The security team has been working on this project for quite some time. Nikolay Bachiyski started the team working on it just over a year ago. We ran it as a private program while we worked out our procedures and processes, and are excited to finally make it public.

\n

With the announcement of the WordPress HackerOne program we are also introducing bug bounties. Bug bounties let us reward reporters for disclosing issues to us and helping us secure our products and infrastructure. We’ve already awarded more than $3,700 in bounties to seven different reporters! We are thankful to Automattic for paying the bounties on behalf of the WordPress project.

\n

The program and bounties cover all our projects including WordPress, BuddyPress, bbPress, GlotPress, and WP-CLI as well as all of our sites including WordPress.org, bbPress.org, WordCamp.org, BuddyPress.org, and GlotPress.org.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4730\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 4.8 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/2017/05/wordpress-4-8-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 13 May 2017 00:15: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4727\";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:342:\"We’re planning a smaller WP release early next month, bringing in three major enhancements: An improved visual editor experience, with a new TinyMCE that allows you to navigate more intuitively in and out of inline elements like links. (Try it out to see, it’s hard to describe.) A revamp of the dashboard news widget to […]\";s: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:1148:\"

We’re planning a smaller WP release early next month, bringing in three major enhancements:

\n\n

The first beta of 4.8 is now available for testing. You can use the beta tester plugin (or just run trunk) to try the latest and greatest, and each of these areas could use a ton of testing. Our goals are to make editing posts with links more intuitive, make widgets easier for new users and more convenient for existing ones, and get many more people aware of and attending our community events.

\n

Four point eight is here
\nSmall changes with a big punch
\nBig ones come later

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4727\";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:36:\"\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:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 4.7.4 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/2017/04/wordpress-4-7-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 20 Apr 2017 17:54:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4710\";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:376:\"After almost sixty million downloads of WordPress 4.7, we are pleased to announce the immediate availability of WordPress 4.7.4, a maintenance release. This release contains 47 bug fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Pascal Birchler\";s: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:4518:\"

After almost sixty million downloads of WordPress 4.7, we are pleased to announce the immediate availability of WordPress 4.7.4, a maintenance release.

\n

This release contains 47 maintenance fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST API. For a full list of changes, consult the release notes and the list of changes.

\n

Download WordPress 4.7.4 or visit Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.7.4.

\n

Thanks to everyone who contributed to 4.7.4:
\nAaron Jorbin, Adam Silverstein, Andrea Fercia, Andrew Ozz, aussieguy123, Blobfolio, boldwater, Boone Gorges, Boro Sitnikovski, chesio, Curdin Krummenacher, Daniel Bachhuber, Darren Ethier (nerrad), David A. Kennedy, davidbenton, David Herrera, Dion Hulse, Dominik Schilling (ocean90), eclev91, Ella Van Dorpe, Gustave F. Gerhardt, ig_communitysites, James Nylen, Joe Dolson, John Blackbourn, karinedo, lukasbesch, maguiar, MatheusGimenez, Matthew Boynes, Matt Wiebe, Mayur Keshwani, Mel Choyce, Nick Halsey, Pascal Birchler, Peter Wilson, Piotr Delawski, Pratik Shrestha, programmin, Rachel Baker, sagarkbhatt, Sagar Prajapati, sboisvert, Scott Taylor, Sergey Biryukov, Stephen Edgar, Sybre Waaijer, Timmy Crawford, vortfu, and Weston Ruter.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4710\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:39:\"\n \n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 4.7.3 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2017/03/wordpress-4-7-3-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 06 Mar 2017 17:53: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: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.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4696\";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:396:\"WordPress 4.7.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7.2 and earlier are affected by six security issues: Cross-site scripting (XSS) via media file metadata.  Reported by Chris Andrè Dale, Yorick Koster, and Simon P. Briggs. Control characters can trick redirect […]\";s: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:\"James Nylen\";s: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:6191:\"

WordPress 4.7.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

WordPress versions 4.7.2 and earlier are affected by six security issues:

\n
    \n
  1. Cross-site scripting (XSS) via media file metadata.  Reported by Chris Andrè Dale, Yorick Koster, and Simon P. Briggs.
  2. \n
  3. Control characters can trick redirect URL validation.  Reported by Daniel Chatfield.
  4. \n
  5. Unintended files can be deleted by administrators using the plugin deletion functionality.  Reported by TrigInc and xuliang.
  6. \n
  7. Cross-site scripting (XSS) via video URL in YouTube embeds.  Reported by Marc Montpas.
  8. \n
  9. Cross-site scripting (XSS) via taxonomy term names.  Reported by Delta.
  10. \n
  11. Cross-site request forgery (CSRF) in Press This leading to excessive use of server resources.  Reported by Sipke Mellema.
  12. \n
\n

Thank you to the reporters for practicing responsible disclosure.

\n

In addition to the security issues above, WordPress 4.7.3 contains 39 maintenance fixes to the 4.7 release series. For more information, see the release notes or consult the list of changes.

\n

Download WordPress 4.7.3 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.7.3.

\n

Thanks to everyone who contributed to 4.7.3: Aaron D. Campbell, Adam Silverstein, Alex Concha, Andrea Fercia, Andrew Ozz, asalce, blobfolio, bonger, Boone Gorges, Boro Sitnikovski, Brady Vercher, Brandon Lavigne, Bunty, ccprog, chetansatasiya, David A. Kennedy, David Herrera, Dhanendran, Dion Hulse, Dominik Schilling (ocean90), Drivingralle, Ella Van Dorpe, Gary Pendergast, Ian Dunn, Ipstenu (Mika Epstein), James Nylen, jazbek, Jeremy Felt, Jeremy Pry, Joe Hoyle, Joe McGill, John Blackbourn, John James Jacoby, Jonathan Desrosiers, Kelly Dwan, Marko Heijnen, MatheusGimenez, Mike Nelson, Mike Schroder, Muhammet Arslan, Nick Halsey, Pascal Birchler, Paul Bearne, pavelevap, Peter Wilson, Rachel Baker, reldev, Robert O’Rourke, Ryan Welcher, Sanket Parmar, Sean Hayes, Sergey Biryukov, Stephen Edgar, triplejumper12, Weston Ruter, and wpfo.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4696\";s: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:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Tue, 25 Jul 2017 19:31:04 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:25:\"strict-transport-security\";s:11:\"max-age=360\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 19 Jul 2017 19:50:31 GMT\";s:4:\"link\";s:63:\"; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:11:\"HIT lax 249\";}}s:5:\"build\";s:14:\"20130911040210\";}', 'no'); +(203, '_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:4:{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:\"Wed, 19 Jul 2017 19:50:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"en-US\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=4.9-alpha-41153\";s:7:\"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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"The Month in WordPress: June 2017\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2017/07/the-month-in-wordpress-june-2017/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Jul 2017 11:42: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in 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:34:\"https://wordpress.org/news/?p=4865\";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:342:\"We’re starting a new regular feature on this blog today. We’d like to keep everyone up-to-date about the happenings all across the WordPress open source project and highlight how you can get involved, so we’ll be posting a roundup of all the major WordPress news at the end of every month. Aside from other general […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:9225:\"

We’re starting a new regular feature on this blog today. We’d like to keep everyone up-to-date about the happenings all across the WordPress open source project and highlight how you can get involved, so we’ll be posting a roundup of all the major WordPress news at the end of every month.

\n

Aside from other general news, the three big events in June were the release of WordPress 4.8, WordCamp Europe 2017, and the WordPress Community Summit. Read on to hear more about these as well as other interesting stories from around the WordPress world.

\n
\n

WordPress 4.8

\n

On June 8, a week before the Community Summit and WordCamp Europe, WordPress 4.8 was released.You can read the Field Guide for a comprehensive overview of all the features of this release (the News and Events widget in the dashboard is one of the major highlights).

\n

Most people would either have their version auto-updated, or their hosts would have updated it for them. For the rest, the updates have gone smoothly with no major issues reported so far.

\n

This WordPress release saw contributions from 346 individuals; you can find their names in the announcement post. To get involved in building WordPress core, jump into the #core channel in the Making WordPress Slack group, and follow the Core team blog.

\n

WordCamp Europe 2017

\n

WordCamp Europe 2017 was held in Paris between June 15-17. The event began with a Contributor Day, followed by two days of talks and community goodness. The talks were live-streamed, but you can still catch all the recordings on WordPress.tv. The organisers also published a handy wrap-up of the event.

\n

WordCamp Europe exists to bring together the WordPress community from all over the continent, as well as to inspire local communities everywhere to get their own events going — to that end, the event was a great success, as a host of new meetup groups have popped up in the weeks following WordCamp Europe.

\n

The work that Contributor Day participants accomplished was both varied and valuable, covering all aspects of the WordPress project — have a look through the Make blogs for updates from each team.

\n

Finally, we also learned during the event that WordCamp Europe 2018 will be held in Belgrade, Serbia, continuing the tradition of exploring locations and communities across the continent.

\n

WordPress Community Summit

\n

The fourth WordPress Community Summit took place during the two days leading up to WordCamp Europe 2017. This event is an invite-only unconference where people from all over the WordPress community come together to discuss some of the more difficult issues in the community, as well as to make plans for the year ahead in each of the contribution teams.

\n

As the Summit is designed to be a safe space for all attendees, the notes from each discussion are in the process of being anonymized before we publish them on the Summit blog (so stay tuned – they’ll show up there over the next few weeks).

\n

You can already see the final list of topics that were proposed for the event here (although a few more were added during the course of the two day Summit).

\n

WordPress marketing push continues apace

\n

As part of the push to be more intentional in marketing WordPress (as per Matt Mullenweg’s 2016 State of the Word), the Marketing team has launched two significant drives to obtain more information about who uses WordPress and how that information can shape their outreach and messaging efforts.

\n

The team is looking for WordPress case studies and is asking users, agencies, and freelancers to take a WordPress usage survey. This will go a long way towards establishing a marketing base for WordPress as a platform and as a community — and many people in the community are looking forward to seeing this area develop further.

\n

To get involved in the WordPress Marketing team, you can visit their team blog.

\n

New Gutenberg editor available for testing

\n

For some time now, the Core team has been hard at work on a brand-new text editor for WordPress — this project has been dubbed “Gutenberg.” The project’s ultimate goal is to replace the existing TinyMCE editor, but for now it is in beta and available for public testing — you can download it here as a plugin and install it on any WordPress site.

\n

This feature is still in beta, so we don’t recommend using it on a production site. If you test it out, though, you’ll find that it is a wholly different experience to what you are used to in WordPress. It’s a more streamlined, altogether cleaner approach to the text-editing experience than we’ve had before, and something that many people are understandably excited about. Matt Mullenweg discussed the purpose of Gutenberg in more detail during his Q&A at WordCamp Europe.

\n

There are already a few reviews out from Brian Jackson at Kinsta, Aaron Jorbin, and Matt Cromwell (among many others). Keep in mind that the project is in constant evolution at this stage; when it eventually lands in WordPress core (probably in v5.0), it could look very different from its current iteration — that’s what makes this beta stage and user testing so important.

\n

To get involved with shaping the future of Gutenberg, please test it out, and join the #core-editor channel in the Making WordPress Slack group. You can also visit the project’s GitHub repository to report issues and contribute to the codebase.

\n
\n

Further reading:

\n\n

If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4865\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"WordPress 4.8 “Evans”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:41:\"https://wordpress.org/news/2017/06/evans/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 08 Jun 2017 14:49: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4770\";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:373:\"An Update with You in Mind Gear up for a more intuitive WordPress! Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard. New features in 4.8 add more ways for you to express yourself and represent your brand. Though some […]\";s: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:43005:\"

An Update with You in Mind

\n

\"\"

\n

Gear up for a more intuitive WordPress!

\n

Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard. New features in 4.8 add more ways for you to express yourself and represent your brand.

\n

Though some updates seem minor, they’ve been built by hundreds of contributors with you in mind. Get ready for new features you’ll welcome like an old friend: link improvements, three new media widgets covering images, audio, and video, an updated text widget that supports visual editing, and an upgraded news section in your dashboard which brings in nearby and upcoming WordPress events.

\n
\n

Exciting Widget Updates

\n

\"\"

\n

Image Widget

\n

Adding an image to a widget is now a simple task that is achievable for any WordPress user without needing to know code. Simply insert your image right within the widget settings. Try adding something like a headshot or a photo of your latest weekend adventure — and see it appear automatically.

\n

Video Widget

\n

A welcome video is a great way to humanize the branding of your website. You can now add any video from the Media Library to a sidebar on your site with the new Video widget. Use this to showcase a welcome video to introduce visitors to your site or promote your latest and greatest content.

\n

Audio Widget

\n

Are you a podcaster, musician, or avid blogger? Adding a widget with your audio file has never been easier. Upload your audio file to the Media Library, go to the widget settings, select your file, and you’re ready for listeners. This would be a easy way to add a more personal welcome message, too!

\n

Rich Text Widget

\n

This feature deserves a parade down the center of town! Rich-text editing capabilities are now native for Text widgets. Add a widget anywhere and format away. Create lists, add emphasis, and quickly and easily insert links. Have fun with your newfound formatting powers, and watch what you can accomplish in a short amount of time.

\n
\n

Link Boundaries

\n
\n

Have you ever tried updating a link, or the text around a link, and found you can’t seem to edit it correctly? When you edit the text after the link, your new text also ends up linked. Or you edit the text in the link, but your text ends up outside of it. This can be frustrating! With link boundaries, a great new feature, the process is streamlined and your links will work well. You’ll be happier. We promise.

\n
\n

Nearby WordPress Events

\n

\"\"

\n

Did you know that WordPress has a thriving offline community with groups meeting regularly in more than 400 cities around the world? WordPress now draws your attention to the events that help you continue improving your WordPress skills, meet friends, and, of course, publish!

\n

This is quickly becoming one of our favorite features. While you are in the dashboard (because you’re running updates and writing posts, right?) all upcoming WordCamps and official WordPress Meetups — local to you — will be displayed.

\n

Being part of the community can help you improve your WordPress skills and network with people you wouldn’t otherwise meet. Now you can easily find your local events just by logging in to your dashboard and looking at the new Events and News dashboard widget.

\n
\n

Even More Developer Happiness \"?\"

\n

More Accessible Admin Panel Headings

\n

New CSS rules mean extraneous content (like “Add New” links) no longer need to be included in admin-area headings. These panel headings improve the experience for people using assistive technologies.

\n

Removal of Core Support for WMV and WMA Files

\n

As fewer and fewer browsers support Silverlight, file formats which require the presence of the Silverlight plugin are being removed from core support. Files will still display as a download link, but will no longer be embedded automatically.

\n

Multisite Updates

\n

New capabilities have been introduced to 4.8 with an eye towards removing calls to
\nis_super_admin(). Additionally, new hooks and tweaks to more granularly control site and user counts per network have been added.

\n

Text-Editor JavaScript API

\n

With the addition of TinyMCE to the text widget in 4.8 comes a new JavaScript API for instantiating the editor after page load. This can be used to add an editor instance to any text area, and customize it with buttons and functions. Great for plugin authors!

\n

Media Widgets API

\n

The introduction of a new base media widget REST API schema to 4.8 opens up possibilities for even more media widgets (like galleries or playlists) in the future. The three new media widgets are powered by a shared base class that covers most of the interactions with the media modal. That class also makes it easier to create new media widgets and paves the way for more to come.

\n

Customizer Width Variable

\n

Rejoice! New responsive breakpoints have been added to the customizer sidebar to make it wider on high-resolution screens. Customizer controls should use percentage-based widths instead of pixels.

\n
\n

The Squad

\n

This release was led by Matt and Jeff Paul, with the help of the following fabulous folks. There are 346 contributors with props in this release, with 106 of them contributing for the first time. Pull up some Bill Evans on your music service of choice, and check out some of their profiles:

\nAaron D. Campbell, Aaron Jorbin, abrightclearweb, Achal Jain, achbed, Acme Themes, Adam Silverstein, adammacias, Ahmad Awais, ahmadawais, airesvsg, ajoah, Aki Björklund, akshayvinchurkar, Alain Schlesser, Alex Concha, Alex Dimitrov, Alex Hon, alex27, allancole, Amanda Rush, Andrea Fercia, Andreas Panag, Andrew Nacin, Andrew Ozz, Andrey \"Rarst\" Savchenko, Andy Meerwaldt, Andy Mercer, Andy Skelton, Aniket Pant, Anil Basnet, Ankit K Gupta, Anthony Hortin, antisilent, Anton Timmermans, Antti Kuosmanen, apokalyptik, artoliukkonen, Arunas Liuiza, attitude, backermann, Bappi, Ben Cole, Bernhard Gronau, Bernhard Kau, binarymoon, Birgir Erlendsson (birgire), BjornW, bobbingwide, boblinthorst, boboudreau, bonger, Boone B. Gorges, Brady Vercher, Brainstorm Force, Brandon Kraft, Brian Hogg, Brian Krogsgard, Bronson Quick, Caroline Moore, Casey Driscoll, Caspie, Chandra Patel, Chaos Engine, cheeserolls, chesio, chetansatasiya, choong, Chouby, chredd, Chris Jean, Chris Marslender, Chris Smith, Chris Van Patten, Chris Wiegman, chriscct7, chriseverson, Christian Chung, Christian Nolen, Christian Wach, Christoph Herr, Clarion Technologies, Claudio Sanches, Claudio Sanches, ClaudioLaBarbera, codemovement.pk, coderkevin, codfish, coreymcollins, Curdin Krummenacher, Curtiss Grymala, Cătălin Dogaru, danhgilmore, Daniel Bachhuber , Daniel Kanchev, Daniel Pietrasik, Daniele Scasciafratte, Daryl L. L. Houston (dllh), Dave Pullig, Dave Romsey (goto10), David A. Kennedy, David Chandra Purnama, David Herrera, David Lingren, David Mosterd, David Shanske, davidbhayes, Davide \'Folletto\' Casali, deeptiboddapati, delphinus, deltafactory, Denis de Bernardy, Derek Herman, Derrick Hammer, Derrick Koo, dimchik, Dinesh Chouhan, Dion Hulse, Dipesh Kakadiya, dmsnell, Dominik Schilling, Dotan Cohen, Doug Wollison, doughamlin, DreamOn11, Drew Jaynes, duncanjbrown, dungengronovius, DylanAuty, Eddie Hurtig, Eduardo Reveles, Edwin Cromley, ElectricFeet, Elio Rivero, Ella Iseulde Van Dorpe, elyobo, enodekciw, enshrined, Eric Andrew Lewis, Eric Lanehart, Evan Herman, Felix Arntz, Fencer04, Florian Brinkmann, Florian TIAR, FolioVision, fomenkoandrey, Francesco Taurino, Frank Klein, Frankie Jarrett, Fred, Fredrik Forsmo, fuscata, Gabriel Maldonado, Garth Mortensen, Gary Jones, Gary Pendergast, Geeky Software, George Stephanis, Goran Šerić, Graham Armfield, Grant Derepas, Gregory Karpinsky (@tivnet), Hardeep Asrani, Helen Hou-Sandí, Henry Wright, hiddenpearls, Hinaloe, Hristo Pandjarov, Hugo Baeta, Iain Poulson, Ian Dunn, Ian Edington, idealien, Ignacio Cruz Moreno, imath, implenton, Ionut Stanciu, Ipstenu (Mika Epstein), ivdimova, J.D. Grimes, Jacob Peattie, Jake Spurlock, James Nylen, jamesacero, Japh, Jared Cobb, jayarjo, jdolan, jdoubleu, Jeff Bowen, Jeff Paul, Jeffrey de Wit, Jeremy Felt, Jeremy Pry, jimt, Jip Moors, jmusal, Joe Dolson, Joe Hoyle, Joe McGill, Joel James, johanmynhardt, John Blackbourn, John Dittmar, John James Jacoby, John P. Bloch, John Regan, johnpgreen, Jon (Kenshino), Jonathan Bardo, Jonathan Brinley, Jonathan Daggerhart, Jonathan Desrosiers, Jonny Harris, jonnyauk, jordesign, JorritSchippers, Joseph Fusco, Josh Eaton, Josh Pollock, joshcummingsdesign, joshkadis, Joy, jrf, JRGould, Juanfra Aldasoro, Juhi Saxena, Junko Nukaga, Justin Busa, Justin Sainton, Justin Shreve, Justin Sternberg, K.Adam White, kacperszurek, Kailey (trepmal), KalenJohnson, Kat Hagan, Keanan Koppenhaver, keesiemeijer, kellbot, Kelly Dwan, Kevin Hagerty, Kirk Wight, kitchin, Kite, kjbenk, Knut Sparhell, koenschipper, kokarn, Konstantin Kovshenin, Konstantin Obenland, Konstantinos Kouratoras, kuchenundkakao, kuldipem, Laurel Fulford, Lee Willis, Leo Baiano, LittleBigThings (Csaba), Lucas Stark, Luke Cavanagh, Luke Gedeon, Luke Pettway, lyubomir_popov, mageshp, Mahesh Waghmare, Mangesh Parte, Manish Songirkar, mantismamita, Marcel Bootsman, Marin Atanasov, Mario Valney, Marius L. J., Mariyan Belchev, Mark Jaquith, Mark Root-Wiley, Mark Uraine, Marko Heijnen, markshep, matrixik, Matt Banks, Matt Jaworski, Matt King, Matt van Andel, Matt Wiebe, Matthew Haines-Young, mattyrob, Max Cutler, Maxime Culea, Mayo Moriyama, mckernanin, Mel Choyce, mhowell, Michael Arestad, Michael Arestad, michalzuber, Miina Sikk, Mike Auteri, Mike Crantea, Mike Glendinning, Mike Hansen, Mike Little, Mike Schroder, Mike Viele, Milan Dinić, modemlooper, Mohammad Jangda, Mohan Dere, monikarao, morettigeorgiev, Morgan Estes, Morten Rand-Hendriksen, moto hachi ( mt8.biz ), mrbobbybryant, Naim Naimov, Nate Reist, NateWr, nathanrice, Nazgul, Ned Zimmerman, net, Nick Halsey , Nicolas GUILLAUME, Nikhil Chavan, Nikhil Vimal, Nikolay Bachiyski, Nilambar Sharma, noplanman, nullvariable, odie2, odyssey, Okamoto Hidetaka, orvils, oskosk, Otto Kekäläinen, ovann86, Pantip Treerattanapitak (Nok), Pascal Birchler, patilvikasj, Paul Bearne, Paul Wilde, Payton Swick, pdufour, Perdaan, Peter Wilson, phh, php, Piotr Delawski, pippinsplugins, pjgalbraith, pkevan, Pratik, Pressionate, Presskopp, procodewp, Rachel Baker, Rahul Prajapati, Ramanan, Rami Yushuvaev, ramiabraham, ranh, Red Sand Media Group, Riad Benguella, Rian Rietveld, Richard Tape, Robert D Payne, Robert Jolly, Robert Noakes, Rocco Aliberti, Rodrigo Primo, Rommel Castro, Ronald Araújo, Ross Wintle, Roy Sivan, Ryan Kienstra, Ryan McCue, Ryan Plas, Ryan Welcher, Sal Ferrarello, Sami Keijonen, Samir Shah, Samuel Sidler, Sandesh, Sang-Min Yoon, Sanket Parmar, Sarah Gooding, Sayed Taqui, schrapel, Scott Reilly, Scott Taylor, scrappy@hub.org, scribu, seancjones, Sebastian Pisula, Sergey Biryukov, Sergio De Falco, sfpt, shayanys, shazahm1, shprink, simonlampen, skippy, smerriman, snacking, solal, Soren Wrede, Stanimir Stoyanov, Stanko Metodiev, Steph, Steph Wells, Stephanie Leary, Stephen Edgar, Stephen Harris, Steven Word, stevenlinx, Sudar Muthu, Swapnil V. Patil, swapnild, szaqal21, Takahashi Fumiki, Takayuki Miyauchi, Tammie Lister, tapsboy, Taylor Lovett, team, tg29359, tharsheblows, the, themeshaper, thenbrent, thomaswm, Thorsten Frommen, tierra, Tim Nash, Timmy Crawford, Timothy Jacobs, timph, Tkama, tnegri, Tom Auger, Tom J Nowell, tomdxw, Toro_Unit (Hiroshi Urabe), Torsten Landsiedel, transl8or, traversal, Travis Smith, Triet Minh, Trisha Salas, tristangemus, truongwp, tsl143, Ty Carlson, Ulrich, Utkarsh, Valeriu Tihai, Vishal Kakadiya, vortfu, Vrunda Kansara, webbgaraget, WebMan Design | Oliver Juhas, websupporter, Weston Ruter, William Earnhardt, williampatton, Wolly aka Paolo Valenti, WraithKenny, yale01, Yoav Farhi, Yoga Sukma, Zach Wills, Zack Tollman, Ze Fontainhas, zhildzik, and zsusag.\n

 

\n

Finally, thanks to all the community translators who worked on WordPress 4.8. Their efforts bring WordPress 4.8 fully translated to 38 languages at release time with more on the way.

\n

Do you want to report on WordPress 4.8? We’ve compiled a press kit featuring information about the release features, and some media assets to help you along.

\n

If you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress — we hope you enjoy!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4770\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 4.8 Release Candidate 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:69:\"https://wordpress.org/news/2017/06/wordpress-4-8-release-candidate-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 01 Jun 2017 22:13: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4765\";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:336:\"The second release candidate for WordPress 4.8 is now available. To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip). We’ve made a handful of changes since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Mel Choyce\";s: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:1173:\"

The second release candidate for WordPress 4.8 is now available.

\n

To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

\n

We’ve made a handful of changes since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the Beta 1, Beta 2, and RC1 blog posts.

\n

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

\n

Happy testing!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4765\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"WordPress 4.8 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/2017/05/wordpress-4-8-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 25 May 2017 23:04: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:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4758\";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:325:\"The release candidate for WordPress 4.8 is now available. 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.8 on Thursday, June 8, but we need your help to get there. If you haven’t tested 4.8 yet, […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Mel Choyce\";s: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:2365:\"

The release candidate for WordPress 4.8 is now available.

\n

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.8 on Thursday, June 8, but we need your help to get there. If you haven’t tested 4.8 yet, now is the time!

\n

To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

\n

We’ve made a handful of changes since releasing Beta 2 earlier this week. For more details about what’s new in version 4.8, check out the Beta 1 and Beta 2 blog posts.

\n

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

\n

Developers, please test your plugins and themes against WordPress 4.8 and update your plugin’s Tested up to version in the readme to 4.8. If you find compatibility problems please be sure to post to the support forums so we can figure those out before the final release – we work hard to avoid breaking things. An in-depth field guide to developer-focused changes is coming soon on the core development blog.

\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

\n

This release’s haiku is courtesy of @matveb:

\n

Érrese uno
\nCien veces y más
\nErre ce dos

\n

Thanks for your continued help testing out the latest versions of WordPress.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4758\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 4.8 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/2017/05/wordpress-4-8-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 23 May 2017 00:02: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4749\";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.8 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.8, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Mel Choyce\";s: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:1621:\"

WordPress 4.8 Beta 2 is now available!

\n

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.8, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

\n

For more information on what’s new in 4.8, check out the Beta 1 blog post. Since then, we’ve made over 50 changes in Beta 2.

\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages!

\n

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

\n

WordPress four point eight
\nOne step closer to release
\nPlease test Beta 2!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4749\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:39:\"\n \n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 4.7.5 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/2017/05/wordpress-4-7-5/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 16 May 2017 22:39:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4734\";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:373:\"WordPress 4.7.5 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7.4 and earlier are affected by six security issues: Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing. Improper handling of post meta data values in the XML-RPC […]\";s: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:\"Pascal Birchler\";s: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:2349:\"

WordPress 4.7.5 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

WordPress versions 4.7.4 and earlier are affected by six security issues:

\n
    \n
  1. Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing.
  2. \n
  3. Improper handling of post meta data values in the XML-RPC API. Reported by Sam Thomas.
  4. \n
  5. Lack of capability checks for post meta data in the XML-RPC API. Reported by Ben Bidner of the WordPress Security Team.
  6. \n
  7. A Cross Site Request Forgery (CSRF)  vulnerability was discovered in the filesystem credentials dialog. Reported by Yorick Koster.
  8. \n
  9. A cross-site scripting (XSS) vulnerability was discovered when attempting to upload very large files. Reported by Ronni Skansing.
  10. \n
  11. A cross-site scripting (XSS) vulnerability was discovered related to the Customizer. Reported by Weston Ruter of the WordPress Security Team.
  12. \n
\n

Thank you to the reporters of these issues for practicing responsible disclosure.

\n

In addition to the security issues above, WordPress 4.7.5 contains 3 maintenance fixes to the 4.7 release series. For more information, see the release notes or consult the list of changes.

\n

Download WordPress 4.7.5 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.7.5.

\n

Thanks to everyone who contributed to 4.7.5.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4734\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"WordPress Now on HackerOne\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://wordpress.org/news/2017/05/wordpress-now-on-hackerone/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 15 May 2017 16:02: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:8:\"category\";a:1:{i:0;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:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4730\";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:322:\"WordPress has grown a lot over the last thirteen years – it now powers more than 28% of the top ten million sites on the web. During this growth, each team has worked hard to continually improve their tools and processes. Today, the WordPress Security Team is happy to announce that WordPress is now officially […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Aaron D. Campbell\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:1715:\"

WordPress has grown a lot over the last thirteen years – it now powers more than 28% of the top ten million sites on the web. During this growth, each team has worked hard to continually improve their tools and processes. Today, the WordPress Security Team is happy to announce that WordPress is now officially on HackerOne!

\n

HackerOne is a platform for security researchers to securely and responsibly report vulnerabilities to our team. It provides tools that improve the quality and consistency of communication with reporters, and will reduce the time spent on responding to commonly reported issues. This frees our team to spend more time working on improving the security of WordPress.

\n

The security team has been working on this project for quite some time. Nikolay Bachiyski started the team working on it just over a year ago. We ran it as a private program while we worked out our procedures and processes, and are excited to finally make it public.

\n

With the announcement of the WordPress HackerOne program we are also introducing bug bounties. Bug bounties let us reward reporters for disclosing issues to us and helping us secure our products and infrastructure. We’ve already awarded more than $3,700 in bounties to seven different reporters! We are thankful to Automattic for paying the bounties on behalf of the WordPress project.

\n

The program and bounties cover all our projects including WordPress, BuddyPress, bbPress, GlotPress, and WP-CLI as well as all of our sites including WordPress.org, bbPress.org, WordCamp.org, BuddyPress.org, and GlotPress.org.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4730\";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:33:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 4.8 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/2017/05/wordpress-4-8-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 13 May 2017 00:15: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4727\";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:342:\"We’re planning a smaller WP release early next month, bringing in three major enhancements: An improved visual editor experience, with a new TinyMCE that allows you to navigate more intuitively in and out of inline elements like links. (Try it out to see, it’s hard to describe.) A revamp of the dashboard news widget to […]\";s: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:1148:\"

We’re planning a smaller WP release early next month, bringing in three major enhancements:

\n\n

The first beta of 4.8 is now available for testing. You can use the beta tester plugin (or just run trunk) to try the latest and greatest, and each of these areas could use a ton of testing. Our goals are to make editing posts with links more intuitive, make widgets easier for new users and more convenient for existing ones, and get many more people aware of and attending our community events.

\n

Four point eight is here
\nSmall changes with a big punch
\nBig ones come later

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4727\";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:36:\"\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:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 4.7.4 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/2017/04/wordpress-4-7-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 20 Apr 2017 17:54:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4710\";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:376:\"After almost sixty million downloads of WordPress 4.7, we are pleased to announce the immediate availability of WordPress 4.7.4, a maintenance release. This release contains 47 bug fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Pascal Birchler\";s: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:4518:\"

After almost sixty million downloads of WordPress 4.7, we are pleased to announce the immediate availability of WordPress 4.7.4, a maintenance release.

\n

This release contains 47 maintenance fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST API. For a full list of changes, consult the release notes and the list of changes.

\n

Download WordPress 4.7.4 or visit Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.7.4.

\n

Thanks to everyone who contributed to 4.7.4:
\nAaron Jorbin, Adam Silverstein, Andrea Fercia, Andrew Ozz, aussieguy123, Blobfolio, boldwater, Boone Gorges, Boro Sitnikovski, chesio, Curdin Krummenacher, Daniel Bachhuber, Darren Ethier (nerrad), David A. Kennedy, davidbenton, David Herrera, Dion Hulse, Dominik Schilling (ocean90), eclev91, Ella Van Dorpe, Gustave F. Gerhardt, ig_communitysites, James Nylen, Joe Dolson, John Blackbourn, karinedo, lukasbesch, maguiar, MatheusGimenez, Matthew Boynes, Matt Wiebe, Mayur Keshwani, Mel Choyce, Nick Halsey, Pascal Birchler, Peter Wilson, Piotr Delawski, Pratik Shrestha, programmin, Rachel Baker, sagarkbhatt, Sagar Prajapati, sboisvert, Scott Taylor, Sergey Biryukov, Stephen Edgar, Sybre Waaijer, Timmy Crawford, vortfu, and Weston Ruter.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4710\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:9;a:6:{s:4:\"data\";s:39:\"\n \n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 4.7.3 Security and Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wordpress.org/news/2017/03/wordpress-4-7-3-security-and-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 06 Mar 2017 17:53: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: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.7\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4696\";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:396:\"WordPress 4.7.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7.2 and earlier are affected by six security issues: Cross-site scripting (XSS) via media file metadata.  Reported by Chris Andrè Dale, Yorick Koster, and Simon P. Briggs. Control characters can trick redirect […]\";s: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:\"James Nylen\";s: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:6191:\"

WordPress 4.7.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

WordPress versions 4.7.2 and earlier are affected by six security issues:

\n
    \n
  1. Cross-site scripting (XSS) via media file metadata.  Reported by Chris Andrè Dale, Yorick Koster, and Simon P. Briggs.
  2. \n
  3. Control characters can trick redirect URL validation.  Reported by Daniel Chatfield.
  4. \n
  5. Unintended files can be deleted by administrators using the plugin deletion functionality.  Reported by TrigInc and xuliang.
  6. \n
  7. Cross-site scripting (XSS) via video URL in YouTube embeds.  Reported by Marc Montpas.
  8. \n
  9. Cross-site scripting (XSS) via taxonomy term names.  Reported by Delta.
  10. \n
  11. Cross-site request forgery (CSRF) in Press This leading to excessive use of server resources.  Reported by Sipke Mellema.
  12. \n
\n

Thank you to the reporters for practicing responsible disclosure.

\n

In addition to the security issues above, WordPress 4.7.3 contains 39 maintenance fixes to the 4.7 release series. For more information, see the release notes or consult the list of changes.

\n

Download WordPress 4.7.3 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.7.3.

\n

Thanks to everyone who contributed to 4.7.3: Aaron D. Campbell, Adam Silverstein, Alex Concha, Andrea Fercia, Andrew Ozz, asalce, blobfolio, bonger, Boone Gorges, Boro Sitnikovski, Brady Vercher, Brandon Lavigne, Bunty, ccprog, chetansatasiya, David A. Kennedy, David Herrera, Dhanendran, Dion Hulse, Dominik Schilling (ocean90), Drivingralle, Ella Van Dorpe, Gary Pendergast, Ian Dunn, Ipstenu (Mika Epstein), James Nylen, jazbek, Jeremy Felt, Jeremy Pry, Joe Hoyle, Joe McGill, John Blackbourn, John James Jacoby, Jonathan Desrosiers, Kelly Dwan, Marko Heijnen, MatheusGimenez, Mike Nelson, Mike Schroder, Muhammet Arslan, Nick Halsey, Pascal Birchler, Paul Bearne, pavelevap, Peter Wilson, Rachel Baker, reldev, Robert O’Rourke, Ryan Welcher, Sanket Parmar, Sean Hayes, Sergey Biryukov, Stephen Edgar, triplejumper12, Weston Ruter, and wpfo.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"4696\";s: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:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Wed, 26 Jul 2017 09:36:07 GMT\";s:12:\"content-type\";s:34:\"application/rss+xml; charset=UTF-8\";s:25:\"strict-transport-security\";s:11:\"max-age=360\";s:6:\"x-olaf\";s:3:\"⛄\";s:13:\"last-modified\";s:29:\"Wed, 19 Jul 2017 19:50:31 GMT\";s:4:\"link\";s:63:\"; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:11:\"HIT lax 249\";}}s:5:\"build\";s:14:\"20130911040210\";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES -(178, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1501054259', 'no'), -(179, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1501011059', 'no'), -(180, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1501054260', 'no'); +(204, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1501104962', 'no'), +(205, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1501061762', 'no'), +(206, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1501104963', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES -(181, '_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:133:\"WPTavern: SiteLock Acquires Patchman’s Malware and Vulnerability Detection Technology, Expands WordPress Customer Base to 4 Million\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73626\";s:7:\"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:140:\"https://wptavern.com/sitelock-acquires-patchmans-malware-and-vulnerability-detection-technology-expands-wordpress-customer-base-to-4-million\";s: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:4517:\"

\n

SiteLock, a website security company, has acquired Patchman, a Dutch security startup that offers automated vulnerability patching and malware removal for hosting providers. Prior to the acquisition SiteLock protected 6 million sites, with 2.2 million of them running on WordPress. The addition of Patchman extends SiteLock’s customer base to 12 million sites and more than 4 million of those are powered by WordPress.

\n

Patchman detects vulnerabilities in a wide range of popular applications and quarantines and patches threats automatically. The quarantine feature neutralizes malicious files by removing them from public access. Patchman supports detection and patching for WordPress 3.x and later.

\n

Historically, the service has not included patches for plugins but it has applied them on a case-by-case basis for high impact vulnerabilities, including a few found in WP Super Cache, MailPoet, and the open source Genericons font project. The Patchman dashboard allows users to easily track files where vulnerabilities have been detected, view status, and revert patches if necessary.

\n

\n

Patchman’s single focus on hosting providers gives SiteLock the opportunity to offer more options to its hosting partners. With the acquisition, the company is now partering with more than 500 hosting providers, including BlueHost, 1&1, Web.com, InMotion, Melbourne IT, GMO (NTT), and many others.

\n

“During our early talks, Patchman was not looking to be acquired and SiteLock wasn’t looking to acquire,” SiteLock President Neill Feather said. After meeting at the WorldHostingDays show in Rust, Germany in late March this year and at another show in Los Angeles, the companies found they shared similar goals and would be in a better position working together.

\n

“It truly was a matter of 1+1=3,” Feather said. “Traditionally, SiteLock is very strong in detecting and removing malware for end users. Patchman offers a service tailored specifically to hosting providers and aimed at fixing the security vulnerabilities that hackers exploit to infect websites with malware. By working together we are able to address a wider market and offer a broader solution to the problems that we solve for our customers. We can now attack the problem from multiple angles.”

\n

Patchman’s technology will compliment SiteLock’s existing security features but the company has not yet decided how it will be incorporated into its security plans for customers. Feather said the team is still jointly building out its future roadmap to give hosts and end customers access to a wider range of products. They are also considering making Patchman’s detection technology compatible with more products in the WordPress ecosystem.

\n

Feather could not disclose any specifics on revenue generated by SiteLock’s WordPress security products but approximately 30% of its newly expanded customer base is running on WordPress.

\n

“What we can say is that we’re heavily invested in the WordPress community and plan on continuing to do so,” Feather said.

\n

“I’m excited that the increased number of sites we now protect across multiple platforms means we’ll be able to identify malware and malicious trends more efficiently than we’ve been able to already, and that’s good for every end user,” SiteLock’s WordPress Evangelist Adam Warner said. “Secondly, although we already have solutions for our partners, Patchman allows web hosts to offer increased security options for advanced users of their platforms. Being a WordPress guy, I’m excited about the possibility we now have to extend the capabilities of Patchman to plugins and other WordPress-specific software.”

\n
\";s: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, 25 Jul 2017 18:46:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:63:\"WPTavern: Watch WordCamp Varna Wapuus Get Designed in Real Time\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73617\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/watch-wordcamp-varna-wapuus-get-designed-in-real-time\";s: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:1427:\"

\n

The very first WordCamp Varna will be held September 2-3 at the University of Economics. Varna is a beautiful city in Bulgaria on the Black Sea and a popular spot for summer holidays. It is the first Bulgarian WordCamp to be held outside of Sofia.

\n

Tickets are on sale for EUR 10 (BGN 20) and include all the sessions, lunch, a #WCVAR 2017 T-shirt, and a few drinks at the after party. There are 102 remaining for the conference and 14 remaining tickets for the kids’ workshop (ages 7-14).

\n

The location naturally inspired a maritime sticker pack collection for attendees, featuring four new wapuu designs. The collection was designed by the vector graphic illustrators at GraphicMama, a design partner for the WordCamp. Ever wonder how much effort goes into designing all the individualized creations in the world of wapuus? Check out the video below to see how WordCamp Varna’s wapuu designs were brought to life.

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 25 Jul 2017 04:14:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:64:\"WPTavern: New Aztec Editor for WordPress Mobile Apps Now in Beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73587\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/new-aztec-editor-for-wordpress-mobile-apps-now-in-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3390:\"

WordPress’ iOS and Android apps will soon be getting a new editor. The appearance of the new editor, codenamed “Aztec,” is very similar to the old one but is light years ahead of its predecessor in both speed and reliability. Aaron Douglas, iOS engineer at Automattic, announced the open beta for Aztec today with a side-by-side comparison video of the old and new editors. A copy and paste test with 500 paragraphs on iPhone 6s demonstrates Aztec’s instantaneous response while the old editor takes two-minutes to render the text.

\n

\n

In addition to better speed and performance, Aztec’s use of OS-provided text controls makes it possible to offer full support for accessibility technologies like iOS’ VoiceOver and Android’s TalkBack. It also adds the ability to draft using dictation.

\n

Aztec introduces a new undo/redo tool at the top of the screen as a quick option for fixing mistakes. It also provides a simpler, more reliable experience using spell check.

\n

\n

The Aztec beta is available to all users in the latest updates of the app (8.0 for iOS, 7.8 for Android). After opening the app you will see a popup for enabling the new editor. It can also be toggled on/off by going to Me > App Settings and selecting “Set the Editor Type.”

\n

The mobile team has made it easy to test and give feedback without leaving the app. Tapping the “beta” button at the top of the editor will open a “What’s New in the Beta” page with a bug button at the top that you can use to report bugs and send feedback. At the moment, the beta does not support shortcodes or video and WordPress gallery features. Keep in mind that it’s not 100% ready for use and heavy users of the mobile apps are likely to discover glitches.

\n

Aztec is open source (GPL 2.0) and packaged as a rich-text editor component in its own GitHub repository (iOS | Android) so that developers can use it in their own applications and contribute code back to the project.

\n

“Quite literally, there is nothing like this out there – every editor we could find uses a web view or has very limited support for any HTML,” Douglas said. “Our hope is the Aztec editor is seen as a component that can be used by many iOS and Android apps to provide a rich HTML editing experience. We feel that we could garner a bigger contributor base to the mobile apps simply because this component exists, is free and open, and is super awesome.”

\n

The project is a few months behind the schedule published in April, which had open beta targeted for May and the full release for the end of this month. Depending on how well the beta testing period goes, users could see the new Aztec editor included in the mobile apps within the next few months.

\n
\";s: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, 24 Jul 2017 22:59:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"WPTavern: Hamilton: A Free WordPress Portfolio Theme for Photographers, Illustrators, and Designers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72881\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"https://wptavern.com/hamilton-a-free-wordpress-portfolio-theme-for-photographers-illustrators-and-designers\";s: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:3779:\"

Hamilton is a new portfolio theme released by Swedish designer and developer Anders Norén during his summer vacation. It was created for photographers, illustrators, designers, and image-heavy blogs. The theme displays portfolio items in a minimal, masonry-style grid with an optional tagline on the front page.

\n

\n

“Hamilton has a pretty simple design at its core, so when it was more or less finished, I decided to add a couple of fun theme options to make it more customizable,” Norén said. “The main one is the Dark Mode. With a click of the mouse in the WordPress Customizer, you can change Hamilton from dark text on a white background to white text on a dark background.”

\n

The Customizer also includes a few other helpful options for portfolio sites:

\n\n

The theme is beautifully responsive to various devices and screen sizes. Norén’s typography choices are clean and readable on mobile.

\n

\n

Hamilton includes styles for the default WordPress image gallery with more interesting options available to create complex galleries stacked with different numbers of columns. It also supports Jetpack’s Infinite Scroll module and has styles for blockquotes, pullquotes, and left/right/center aligned media.

\n

\n

One of the most unique features of the theme is the Resume template. It gives users the option to add a simple resume to their portfolios, without having to add a plugin. The template uses basic HTML for formatting with h1 header tags, horizontal rules, and unordered lists. The template could use a bit more documentation, since not all users are familiar with HTML, but it’s a useful addition for simple portfolio sites.

\n

\n

Check out a live demo along with the style guide to see the theme in action.

\n

Hamilton is Anders Norén’s 15th theme approved for the WordPress Theme Directory. When he submitted it to the Theme Review Team, he anticipated that it would take a month or two for it to get through the review process. His previously submitted theme, Davis, took approximately nine months to make it through the queue. He was surprised to find that Hamilton went through the process in under a month. After less than a week on WordPress.org, the theme has already been downloaded more than 200 times.

\n
\";s: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, 24 Jul 2017 19:27: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:\"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:101:\"WPTavern: Members 2.0 Adds Capability Registration System, Introduces New Settings Screen for Add-Ons\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73446\";s:7:\"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:111:\"https://wptavern.com/members-2-0-adds-capability-registration-system-introduces-new-settings-screen-for-add-ons\";s: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:6254:\"

\n

Eight years ago, Justin Tadlock moved back home to Alabama and was living in the spare bedroom of his grandparents’ house with nothing more than a laptop and a suitcase. Over the course of a few months he started going deeper into learning about writing WordPress plugins and produced Members, a role management plugin for WordPress. The first major overhaul of the plugin came in 2015 with version 1.0’s expansion of features and a new UI for editing roles.

\n

Members has built up a user base of more than 100,000 active installs since it first launched in 2009. Tadlock estimates that over the last couple years, 40% of Theme Hybrid customers are primarily there for support and small tweaks to the Members plugin. He decided it was time to begin investing more in the plugin and its community.

\n

Tadlock released Members 2.0 this week. The plugin manages core WordPress capabilities but 2.0 adds the ability for plugins to register custom capabilities. The labels for the capabilities can be internationalized so users can manage the plugin in their own languages in human-readable form.

\n

\n

This release also adds the ability to use the WordPress editor for writing custom post error messages, making it easy to direct visitors to registration or other important information regarding access to the content.

\n

Members 2.0 lets users add multiple roles when creating a new user from the Add User screen. It also introduces the ability to bulk add or remove roles from users, even when multiple roles have been enabled.

\n

\n

This version of the plugin serves some of its data using the WP REST API and a new setting was added to authenticate users who are accessing the REST API endpoints. This protects content from being exposed on sites that have the “private site” setting enabled. Tadlock plans to write a tutorial about what he has learned in integrating the REST API with the plugin.

\n

Tadlock Aims to Monetize Members with Add-Ons, Renews Efforts to Develop a Community of Add-On Developers

\n

Members 2.0 introduces a new Settings screen that ties in with Tadlock’s future plans to monetize the plugin. The new screen includes a view for add-ons. Tadlock has two add-ons available currently and has written an API for third-party developers to register their own add-ons to be visible on this screen.

\n

\n

“The plan is to create some small add-on plugins,” Tadlock said. “There’s already two: Members – Role Levels, which is paid, and Members – Role Hierarchy, which I was hired to build and was allowed to release to the community for free. I’ve got a few small plugins like those in mind that’ll be in a lower price range.”

\n

Tadlock also plans to release a more robust version of the “Content Permissions” feature as another add-on. He has received numerous feature requests from users over the years about what they would like to see in this plugin. The add-on will offer a variety of different ways to show/hide content.

\n

I asked Tadlock if he has considered building payment gateway add-ons so users can charge for memberships. He said the idea is on the table.

\n

“I’m not sure if I’m going to build those or someone else,” Tadlock said. “I’ve mentioned it to some other developers. It would be a good place to start building add-ons.” His current setup uses Easy Digital Downloads with a couple of plugins to bridge it with Members and ThemeHybrid.com.

\n

A plugin like Members has the potential to have a large, third-party ecosystem of plugins for payments and additional features, but Tadlock was focused on other projects during the first few years after it launched.

\n

“I haven’t actively pursued the add-on angle,” Tadlock said. “Instead, I focused more on themes during most of that time. Now, I’m focusing more on plugin development. It’s my fault for not nurturing a community of add-on developers, which is something I’m trying to do more of now.”

\n

Tadlock said many of the developers he knows are working with Members because they like that it gives them a solid foundation to build on for client work. He hopes to persuade some of them to release some of that code back as commercial add-ons or free plugins in the WordPress plugin directory.

\n

Since launching the plugin eight years ago, Tadlock has aimed to make it behave as if it were a natural part of WordPress. At its core, Members is a role and capability management plugin and not a one-size-fits all membership plugin.

\n

“It’s more or less a UI over what you could do with code already,” Tadlock said. “Most of all, it tries not to get in your way. Every membership site has its own unique needs. It’s tough building something that suits everyone. That’s why I’d rather have that foundation of Members just exposing the roles/caps system with third-party add-ons that suit various users’ needs.

\n

“Other membership plugins often try to please everyone or pigeon-hole everything into their custom system. I like more to have a bit more flexibility without the bloat.”

\n
\";s: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, 21 Jul 2017 21:37:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:61:\"WPTavern: WordPress 4.8.1 Adds a Dedicated Custom HTML Widget\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73470\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wptavern.com/wordpress-4-8-1-adds-a-dedicated-custom-html-widget\";s: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:2681:\"

When WordPress 4.8 was released last month, it introduced TinyMCE functionality to the Text widget. Unfortunately, this caused issues for those who use Custom HTML as the Visual editor often strips out portions of the code.

\n

WordPress 4.8.1 Beta 1 is available for testing and addresses this problem by including a dedicated Custom HTML widget.

\n

“For advanced users or any user who needs to paste in HTML snippets, there is now a dedicated ‘Custom HTML’ widget that is specifically for adding arbitrary HTML to your sidebar,” Weston Ruter, said.

\n

“This widget will retain the application of the widget_text filters, in addition to having a new dedicated widget_custom_html_content filter.

\n

“For use cases that involve adding content to your sidebar, the Text widget will continue to feature the same Visual editing interface that the post editor has (TinyMCE).”

\n

Users who access Text widgets that have Custom HTML in WordPress 4.8.1, will see a note at the top of the widget that suggests using the Custom HTML widget.

\n

\n

If a user pastes or types HTML into a text widget with the Visual editor active, WordPress displays an Admin Pointer suggesting that they use the Text tab instead or use the Custom HTML widget.

\nText Widget Admin Pointer\n

The Custom HTML widget works similar to the Text widget in WordPress 4.7 and below.

\nCustom HTML Widget\n

Sites that have existing Text widgets containing custom HTML that may be modified by the Visual editor, are opened in a legacy mode.

\n

Legacy mode retains the old Text widget interface, including the checkbox on whether or not to automatically add paragraphs. This change prevents the Visual editor from altering code.

\n

Ruter says the ideal way to test these improvements is to install it on a staging site that has Text widgets containing HTML and are known to be problematic in WordPress 4.8. After upgrading, check to see if the widgets open in legacy mode.

\n

WordPress 4.8.1 is scheduled to be released on August 1st. Please report any bugs or errors you encounter in as much detail as possible to the WordPress Alpha/Beta section of the support forums.

\n
\";s: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, 21 Jul 2017 18:31:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"WPTavern: Petition to Re-License React has been Escalated to Facebook’s Engineering Directors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73454\";s:7:\"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:\"https://wptavern.com/petition-to-re-license-react-has-been-escalated-to-facebooks-engineering-directors\";s: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:7983:\"photo credit: manu schwendener\n

React users are petitioning Facebook to re-license React.js after the Apache Software Foundation announced its decision to ban Apache PMC members from using any technology licensed with Facebook’s BSD+Patents License. So far the GitHub issue has received 627 “thumbs up” emoji and 66 comments from concerned React users who are hoping for a change in licensing.

\n

Many respondents on the thread said that ASF’s decision affects their organizations’ ability to continue using React in projects.

\n

“Apache CouchDB and others will switch away from React if we have to,” CouchDB committer Robert Newson said. “We’d rather not, it’s a lot of work for no real gain, but we don’t have a choice. Changing license can be simple (RocksDB completed that change in a day).”

\n

“My team, at LinkedIn, is also having legal troubles using React for our internal projects,” LinkedIn software Denis Ivanov said. “We would love to see a change on this front.”

\n

Software developer Clark Evans commented on how React’s current licensing might affect medical research institutes, and suggested that Facebook consider an Apache 2.0 license because it includes equitable patent grants.

\n

Since U.S. based universities rely upon patent licensing as part of their legislatively mandated technology transfer initiatives, they are growing far more cautious in their due diligence. For this reason, at some universities, software written with React may be shunned. Existing projects using React software may be asked to remove the React software software dependency. Please strongly consider this proposal, since our RexDB work is used at major universities, we do not wish to rework to use a React alternative.

\n

Several participants in the discussion commented that they would like to use React but the licensing makes it impossible for their companies.

\n

“Other large companies such as mine (Adobe) can’t use React, Pop, etc. for the very same reason,” Corey Lucier said. “We’d love to participate in the project, contribute to each, etc. but Facebook’s heavy-handed PATENTS clause is a showstopper.”

\n

“Even mid-size companies like mine (ViaSat) are starting to disallow the use of Facebook’s ‘open-source’ projects for this reason,” software developer Aaron Yoshitake said. “We’d like to build React web and native apps, but it seems that any sensible legal department will recommend against agreeing to Facebook’s asymmetric patent grant.”

\n

Internal Discussions Continue at Facebook, Re-Licensing Issue has been Escalated to Engineering Directors

\n

Dan Abramov, co-author of Redux, Create React App, and React Hot Loader, shared with participants that Facebook is having internal discussions about the re-licensing issue but cautioned them to temper their optimism. He returned to throw some ice on the conversation, which has grown more heated over the past few days, when he said it could only remain an open discussion if everyone involved remains civil. Many participants are concerned about the future of the React-based software that they have already invested thousands of hours of work into.

\n

“I understand that everyone is frustrated about this issue,” Abramov said. “Personally I am just as frustrated to spend time, energy, and emotional wellbeing on legal mumbo jumbo that is preventing people from using React. I would much prefer to spend this time on working together to make it better.

\n

“But the reality of this situation is that the maintainers of React (people like me that you’re interacting on the issue tracker) are not the ones making these decisions. Each of us is doing what we can to show different perspectives on this issue to the people who can make those decisions, and we appreciate your feedback too. But we can only keep discussion open if everyone stays civil and respectful.”

\n

Abramov also pointed out in a follow-up update that a bug tracker isn’t the best avenue for a legal discussion, especially since most participants are software developers and not lawyers. Many have mistaken the thread as a way to communicate with Facebook but there are just a handful of software developers who are representing the React community’s concerns.

\n

“We have heard you very well, and we have passed on your concerns,” Abramov said. “But repeating the same points over and over in different threads does not help move this forward, and creates a lot of noise and stress for the maintainers who are already empathetic to your cause.”

\n

Several participants expressed frustration that the React community cannot participate in the discussions more directly. However, as React is both an open source project and a product of Facebook, the company’s leadership has the last word on licensing issues.

\n

“I understand that software developers like us are not the best people to discuss legal details,” software consultant Erik Doernenburg said. “However, wouldn’t the logical consequence be that the Facebook Legal team, who make such decisions, become active in this forum? Shouldn’t it be possible that all relevant details pertaining to a piece of open source software are discussed in the open? It is incredibly frustrating to have such an important aspect of open software discussed behind closed doors.”

\n

It’s not known whether Facebook is considering another change to its Patents grant or a complete re-licensing. Participants in the discussion are also concerned about other Facebook open source projects like GraphQL, Relay, React Native, and Flow, which share the same BSD+Patents License and are widely used by the open source community.

\n

Dan Abramov left an update today to let the community know that no resolution is available this week. However, the update seemed more positive than the first one, which discouraged participants from being optimistic about a change.

\n

“I want to point out that there is a real momentum behind this discussion internally,” Abramov said. “There are going to be more meetings next week escalating this up to the engineering directors. As you imagine they are quite busy, so this is taking more time than we thought.

\n

“Again, I can’t promise you any specific conclusion, and there is no clarity on where this will land. But please know there are people working on getting your voice heard.”

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 20 Jul 2017 22:37: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:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"WPTavern: WPWeekly Episode 282 – Talking WooCommerce with Cody Landefeld\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=73448&preview=true&preview_id=73448\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/wpweekly-episode-282-talking-woocommerce-with-cody-landefield\";s: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:3381:\"

In this episode, John James Jacoby and I are joined by Cody Landefeld, Senior web strategist and founder of Mode Effect. Landefeld describes some of the challenges that shop owners face and provides insight into a couple of WooCommerce projects Mode Effect has recently built.

\n

We discussed the future of WooCommerce and the odds of it turning into a SaaS product. Landefeld shares his thoughts on WooCommerce dropping its 50% renewal discount on subscriptions. Even though the discount is gone, he believes it’s still an affordable option for most users. To close out the show, Jacoby and I discuss the news of the week.

\n

Stories Discussed:

\n

AJ Morris Acquires iThemes Exchange
\nJetpack Professional Plan Introduces Unlimited Access to 200+ Commercial Themes
\nbbPress 2.5.13 Readds Sanitization to Anonymous User Data
\nWP Rollback Adds Multisite Compatibility and Changelog Preview
\nGutenberg 0.5.0 Adds New Verse Block for Poetry and a New Display for Recent Blocks

\n

Picks of the Week:

\n

Gutenberg Boilerplate For Third-Party Custom Blocks by Ahmad Awais. The boilerplate is a great way to learn the basics on creating custom blocks for Gutenberg. It comes with four example blocks.

\n\n

Awais also shared his thoughts on the Gutenberg project.

\n

Add Admin CSS – Using this plugin you’ll easily be able to define additional CSS (inline and/or files by URL) to be added to all administration pages. You can define CSS to appear inline in the admin head (within style tags), or reference CSS files to be linked.

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, August 2nd 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #282:
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 20 Jul 2017 01:19:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WPTavern: The State of JavaScript 2017 Survey is Now Open\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73377\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wptavern.com/the-state-of-javascript-2017-survey-is-now-open\";s: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:2708:\"

\n

The State of JavaScript 2017 Survey is now open to web professionals of all backgrounds. The intent of the survey is to provide an overview of the rapidly changing landscape of JavaScript frameworks and tools by gauging which technologies are growing in popularity and which ones people are liking and using less.

\n

The survey, created by Sacha Greif and Michael Rambeau, should take approximately 10 minutes to complete. Topics include JavaScript frontend and backend tools and frameworks, state management solutions, testing tools, CSS, build tools, mobile and desktop technologies, package managers, text editors, salaries, and more.

\n

Last year’s 89-question survey received more than 9,300 responses. Results showed that React ranked higher than other front-end frameworks in terms of developer satisfaction at 92%, followed closely by Vue.js at 89%.

\n

It will be interesting to see if and how these results change with many open source project and companies growing wary of using React after the Apache Software Foundation’s recent decision to ban Apache PMC members from using any technology licensed with Facebook’s BSD+Patents License. A licensing issue that jeopardizes more companies’ ability to use Facebook’s popular open source technologies could precipitate a decline in React’s preeminence among frontend frameworks.

\n

Sacha Greif reports that the survey has received more than 3,500 responses in less than 24 hours, a remarkable number compared to 9,300 over the course of three weeks last year. This response affirms the value that last year’s results provided to web professionals who are attempting to navigate the ever-expanding JavaScript ecosystem.

\n
\";s: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, 19 Jul 2017 20:16:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:67:\"WPTavern: bbPress 2.5.13 Readds Sanitization to Anonymous User Data\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73397\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://wptavern.com/bbpress-2-5-13-readds-sanitization-to-anonymous-user-data\";s: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:1328:\"

The bbPress development team has released bbPress 2.5.13. This release fixes a few bugs, most notably, it readds sanitization to anonymous user data that was accidentally removed in previous versions.

\n

Those who allow anonymous users to create topics and replies on their forums are encouraged to update immediately.

\n

“This feature is not widely used on public forums because spammers aggressively target these kinds of sites, but for communities that rely on this feature, please know you can safely upgrade to 2.5.13 without any issues,” John James Jacoby, lead developer of bbPress and BuddyPress, said.

\n

As a reminder, beginning with bbPress 2.5.12, the minimum version of WordPress supported is 4.7. If you’re using an older version of WordPress, Jacoby recommends using or staying with bbPress 2.5.11.

\n

bbPress 2.6 is still in the release candidate phase as developers iron out a few issues discovered on WordPress.org.

\n

Users can download the latest version of bbPress from WordPress.org or browse to Dashboard > Updates, and upgrade from within WordPress.

\n
\";s: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, 19 Jul 2017 18:22:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:63:\"WPTavern: Zagreb to Host 3rd WordCamp in Croatia, September 1-3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72737\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wptavern.com/zagreb-to-host-3rd-wordcamp-in-croatia-september-1-3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4747:\"photo credit: Archives of Zagreb Tourist Board – Author: Marko Vrdoljak\n

WordCamp Zagreb will be held September 1-3 and organizers are anticipating 300 attendees. This is the third WordCamp to be held in Croatia, following WordCamp Rijeka (2015) and WordCamp Split (2016). Although it changes cities every year, the camp is known as Croatia’s annual WordCamp.

\n

“Having WordCamp change cities each year is quite normal for us,” WordCamp Croatia co-organizer and Zagreb meetup organizer Emanuel Blagonic said. “A lot of people from other cities travel to meetups too. Our largest meetup in Zagreb, which usually has 80+ people present and 100+ live stream viewers, usually has people attending from a 300km circle around Zagreb. People also travel to Split when there are meetups there.”

\n

A renewed discussion on regional WordCamps is firing up on the WordPress Community team P2 blog, as the topic was discussed at the Community Summit and with recent developments in WordCamp Netherlands being reinstated and WordCamp Asia a possibility for 2019. Croatia is another example of a country where a national WordCamp might benefit the community.

\n

“When we started with organizing a WordCamp in Croatia, as a community we hoped that WordCamp will help us boost local communities, thus not having everything centralized in Zagreb (where most other meetups happen, i.e. PHP, Design, UX, JavaScript, Python, etc.),” Blagonic said. “As a community we strongly believe that every region is different and it should be viewed like that. So far we are organizing WordCamps ‘no matter what,’ but having a ‘national WordCamp would mean more Croatian sponsors and better coverage from national media.”

\n

WordCamp Zagreb will be a three-day event, beginning with workshops on the first day as the event has done in previous years. Organizers are planning for 12 workshops in four tracks that will be open to public registration. The main conference will be held Saturday with two tracks. Contributor Day will close out the event on Sunday, followed by a walking tour of the city.

\n

Friday’s workshops will be held mostly in Croatian, except a few, such as WordPress Basics and Public Speaking, which will be conducted in English. All of the conference talks this year will be in English.

\n

“Croatia is a tourist country and most of the people here speak good English, which is often used at large tech events,” Blagonic said. “With that in mind, every WordCamp so far was (mostly) in English, which means it’s quite welcoming for people outside Croatia, too (Slovenia, Austria, Italy, Germany) – and our community likes to meet new people. Unlike WordCamps, we see Meetups as strong local events so we usually have talks in Croatian there.”

\n

Blagonic said every year so far the WordCamp has had approximately 20% of its attendees traveling from outside Croatia, as the country is relatively small with a population of 4 million. Most attendees travel to the WordCamp from other parts of Croatia.

\n

Croatia currently has five local meetups, but only the two in Zagreb and Split have enough members to meet regularly. Blagonic said he sees the meetups as a way to help local communities grow and views the WordCamp as “a celebration of the country community.” However, he believes centralizing the larger events too much would be detrimental to growing the fledgling WordPress communities in the smaller cities.

\n

“I’d say that in Croatia (and in the region) we have a young democracy and we still haven’t found the best way to connect with people,” Blagonic said. “For example, there are four big cities in Croatia where most of the things happen, and the tech scene is quite strong in them. If you go outside of these four hubs, a lot fewer things happen, which is a problem for people living outside. We believe that having a centralized country is bad for growing local communities (outside these areas) so with changing cities each year and with traveling to other Meetups/WordCamps we hope that we will change how people feel about it. “

\n
\";s: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, 19 Jul 2017 18:11: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: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:29:\"Donncha: WP Super Cache 1.5.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:\"https://odd.blog/?p=89500337\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"https://odd.blog/2017/07/19/wp-super-cache-1-5-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:5935:\"

WP Super Cache is a fast full-page caching plugin for WordPress. Download it from your dashboard or get it here.

\n

Version 1.5.0 has been in development for some time. It has a ton of bug fixes and new features.

\n

REST API

\n

The headline new feature is REST API access to the settings. This will allow developers to create their own interface to the settings of the plugin. Unfortunately it isn’t yet documented but you can see the code in the rest directory. Start with load.php where you’ll find the code that registers all the endpoints. Users who access the API must be logged in as admin users. If you want to test the API, see the end of this post.

\n

Settings Page

\n

We have also simplified the settings page to make it easier to choose which caching method is used.

\n

\n

Instead of maybe confusing the user with technical words like PHP, mod_rewrite and WP-Cache we have split them up into “Simple” and “Expert” delivery methods, and done away with mentioning WP-Cache completely. Simple delivery uses PHP, expert uses mod_rewrite and well, WP-Cache got the boot because it’s always active anyway.

\n

WP-Cache caching is always active, but it can be disabled in different ways.

\n\n

Headers

\n

We expanded the number of headers cached by the plugin. The list of headers was borrowed from Comet Cache. However, anonymous users will still only see the bare minimum like content-length or content-type. If you need to use security headers like “X-Frame-Options” or “Content-Security-Policy” you should enable caching of HTTP headers. This unfortunately disables super caching so only WP-Caching is used but it’s still very fast (and faster in this release than before which I will get to below). You can also use the “wpsc_known_headers” filter to modify the list of recognised headers.

\n

WP-Cache Reorganisation

\n

WP-Cache cache files are split into two files – one holds the page content, the other (meta file) holds information about the page such as cookies, headers and url. In the past these files were stored in two directories which could become a problem if there were many thousands of those files. Even with only a few hundred files, maintenance could be an issue as deleting related files (like page archives, or copies of the front page) needed every meta file to be inspected.
\nNow the files are stored in the supercache directory structure that mirrors your permalink structure. Deleting related files is is simpler and serving files will be faster as the operating system won’t need to open a directory of thousands of files.
\nIf you currently rely on WP-Cache files, the plugin will still look for them where they are, but new WP-Cache files will be created in cache/supercache/example.com/ (where example.com is your hostname).

\n

Sitemaps

\n

We added support for caching sitemaps, but your sitemap plugin will need to cooperate to get it to work. The sitemap plugin needs to identify the sitemap request as a feed. Jetpack 5.1 now supports this since #7397. You can disable the caching by excluding feeds from caching.

\n

Debugging Improved

\n

The debug log is now protected by a username/password. For convenience, the username and password are the same but they are a long md5 string:

\n

\n

Deleting the log file clears it and resets it ready for more logging. Before, toggling debugging would create a new debug log and the old one would be kept around, but not linked, until deleted by garbage collection, and of course they were text files anyone could access.

\n

This release includes lots of other small bug fixes and changes. Take a look at the number of closed PRs for an exhaustive list of those changes!

\n

Testing the REST API

\n

There are a number of ways to send POST requests to a web server but one I like is using curl in a shell script. You’ll need two bits of information from the website:

\n
    \n
  1. The “wordpress_logged_in” cookie from your browser.
  2. \n
  3. The wp_rest nonce which you can get by adding `echo wp_create_nonce( ‘wp_rest’ );` somewhere on your site where you’re logged in. It’s good for 24 hours.
  4. \n
\n

My test script looks something like this:
\nexport NONCE=\'1234567890\'
\nexport COOKIE=\'wordpress_logged_in_xxxxxxxxxxxxxxxxxxxx=1234567890\'
\ncurl -v -X \"GET\" -H \"Content-Type: application/json\" -H \"X-WP-Nonce: $NONCE\" -H \"Cache-Control: no-cache\" -H \"Cookie: wordpress_test_cookie=WP+Cookie+check; $COOKIE\" \\
\n-d \'{}\' \"https://example.com/wp-json/wp-super-cache/v1/settings/\"

\n\n

Related Posts

\n

Source

\";s: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, 19 Jul 2017 12:25:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:32:\"HeroPress: Becoming Myself Again\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=1978\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://heropress.com/essays/becoming-myself-again/?utm_source=rss&utm_medium=rss&utm_campaign=becoming-myself-again\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6018:\"\"Pull

It’s so easy to become secluded and sit at home, in your own bubble, but it wasn’t until a group of people literally pulled me in with their welcoming atmosphere and demeanor, that I realised that I could function amongst other people as well (even if it was somewhat limited).

\n

In The Beginning

\n

To understand my bubble, you need to also know a little about me, or rather, about my childhood. I had a less than ideal childhood. I have a great family, lived in a great house, even in the “best country in the world” as they say. And despite this, I say I wasn’t happy with my childhood. My school years were the reason, they were rough. At times I think back and feel like events that unfolded were parts of ridiculous scenes from an over the top movie.

\n

All in all, the days seemed generic enough, except my school days were a thing of dread. I would suffer physical and verbal abuse throughout my schooldays, even going to and from school, I had no real friends (victim by association is understandably not something a child would want to intentionally walk into. I understand this as an adult, but as a child it’s not that easy).

\n

Because of my treatment over the years, I developed trust issues, I got a fear for everyone around me, and it was growing stronger and stronger over the years.

\n

I suppressed it, I lied about it, and I got terrifyingly good at the lying part.

\n

This is why I was drawn to the internet: I didn’t have to interact with people, I didn’t need to go outside where the others were, I could just do my thing and move on. I could live in my own bubble.

\n

Finding WordPress

\n

But then the darndest thing happened. I’d been stuck on a project, I needed help, and I turned to a support room for an open source project, for WordPress. If you’ve ever tried to get help in a chat before, you’ll know what kind of an experience it can be, the snarky reactions to your code, the nitpicking of using the wrong terminology, it’s not fun. This place though, they didn’t care that I was not only using the wrong terms, but my entire code was a horrible mess.

\n

Where I would usually get the help I needed and move on, popping back in my bubble of solitude, I instead wanted to be like these people, I wanted to use what I learnt to let others get helped.

\n

Over the years, I all but devote myself to that place. Nobody knew me, I liked staying under the radar, but eventually I got pushed into a team meeting. I was intrigued, so I would watch, I’d say hi, and progressively make my opinions heard. Yet, I would stick to my bubble, once the meeting was over I was back on my own.

\n

And Then I Went To WordCamp

\n

Until I got to attend my first big WordCamp, the last one held in San Francisco, I was ecstatic! I’d never been to a big conference before, as I didn’t like crowds, but I knew some of the people who would be there. They were people who had been friendly and inviting in the most genuine way imaginable. It’s not easy being worried whenever you’re out amongst people, but this group of people, this community, I didn’t have that fear around them.

\n

I somehow made WordCamps my safe space.

\n

They are where I can, if only for a short while, leave that bubble, leave the need to be alone, and be a part of something great! I use them as fuel to get through the hard times, I can look forward to meeting people, people who value my opinions and my experience. People who genuinely want to listen and most of all, care about you! The WordPress community is, slowly but surely, helping me get rid of my ingrown fear of the unknown, of others.

\n

The community is helping me become myself again.

\n

The post Becoming Myself Again appeared first on HeroPress.

\";s: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, 19 Jul 2017 12:00: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:\"Marius Jensen\";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:104:\"WPTavern: New WordPress Contributors Meeting Provides Opportunities to Ask Questions and Learn the Ropes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73007\";s:7:\"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:115:\"https://wptavern.com/new-wordpress-contributors-meeting-provides-opportunities-to-ask-questions-and-learn-the-ropes\";s: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:2270:\"

Contributing to WordPress or other open source projects can be intimidating for first-time contributors. Sometimes, all you need is a helping hand to overcome fear, intimidation, or other barriers.

\n

In 2013, with the help of Konstantin Obenland, a WordPress core developer, I overcame my fear and contributed my first patch to WordPress.

\n

This is one of the principles behind a new weekly meeting that is geared towards new contributors.

\n

“The new contributors meeting is the perfect place to come if you are new to contributing to WordPress core and have questions,Adam Silverstein, WordPress core contributor, said.

\n

Every Wednesday at 3PM Eastern Daylight Time, users can visit the #core WordPress Slack channel and ask questions related to patches, tickets, and review the good-first-bugs report on Trac.

\n

The first meeting was held on July 5th where participants asked questions about working with Git in WordPress core, applying patches, and unit testing. In the second meeting, participants discussed whether or not new contributors are allowed to make changes to tickets.

\n

Other topics mentioned include, which repositories to use, clarification on contributing to core versus updating the WordPress Developer’s site, and which tickets to select for review.

\n

The next meeting is on Wednesday, July 19th at 3PM Eastern. If you have any questions on how to contribute to WordPress, be sure to join the WordPress #core Slack channel at that time and ask away.

\n

Meeting notes with links to discussions, tickets mentioned, and other resources are published on the Make WordPress Core blog under the #new-contributors tag

\n
\";s: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, 19 Jul 2017 05:09:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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: WP Rollback Adds Multisite Compatibility and Changelog Preview\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73315\";s:7:\"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:\"https://wptavern.com/wp-rollback-adds-multisite-compatibility-and-changelog-preview\";s: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:4021:\"

\n

In the two years since WP Rollback launched on WordPress.org, the plugin has racked up more than 30,000 active installations with nearly all 5-star reviews. It allows users to roll back any WordPress.org plugin or theme to a previous version with just a few clicks and also supports beta versions of plugins.

\n

It’s easy to see why the plugin is so popular. Navigating buggy updates is a natural part of life when maintaining a self-hosted website and not all users have a separate testing environment for their websites. This tool gives them a basic diagnostic tool and the confidence to apply updates knowing they can easily roll it back in case of a problem. Many reviewers cite the plugin as having been “a lifesaver” when applying WooCommerce or Yoast SEO updates that had unexpected results.

\n

The lone one-star review of WP Rollback was given because the user anticipated multisite compatibility and was unable to get it to work. That issue has been solved in the latest update.

\n

WP Rollback 1.5 is fully compatible with multisite networks, giving super admins the ability to roll back extensions from the network plugin/themes screen or from the the plugins/themes screen of the primary site in the network. Sub-sites do not have the ability to roll back plugins and themes for the entire network. The UI for rolling back themes on the network admin screen is identical to the plugin screens, as multisite doesn’t have the fancy theme preview screen that single site installs have.

\n

Version 1.5 also adds the ability for users to preview the changelog for previous versions of a plugin. This makes it convenient for users to quickly view the changes for each version without leaving the admin.

\n

\n

WordImpress, the folks behind WP Rollback, have considered adding core rollbacks and database savepoints, but both features have serious potential drawbacks that could turn it into a high support-demanding plugin. In its current state, the plugin is virtually support-free.

\n

Matt Cromwell, Head of Support and Community Outreach at WordImpress, said the team thought about monetizing the plugin in the beginning, but is not pursing any plans to do so at this time.

\n

“We think of it as just one of the many ways we are giving back to the WP community,” Cromwell said. “Our preference would be for the core team to consider it as a potential feature plugin for eventual core inclusion.”

\n

Cromwell said WordImpress hasn’t made any intentional steps to see if core folks are interested in WP Rollback becoming a feature plugin, but the team has purposely built it to be as close to core standards as possible. He believes it would be relatively easy to implement in WordPress.

\n

Suggestions for new features, general feedback, and bug reports are welcome on WP Rollback’s GitHub repository. The plugin’s authors recommend backing up your site before using it to rollback plugins and themes or testing rollbacks on a staging site first. WP Rollback is not capable of rolling back changes a plugin update has made to the database, so a backup can come in handy if the database changes are incompatible with previous versions.

\n
\";s: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, 18 Jul 2017 22:24: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: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:136:\"WPTavern: React Users Petition Facebook to Re-license React.js after Apache Software Foundation Bans BSD+Patents License in Dependencies\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73216\";s:7:\"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:146:\"https://wptavern.com/react-users-petition-facebook-to-re-license-react-js-after-apache-software-foundation-bans-bsdpatents-license-in-dependencies\";s: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:9983:\"

\n

The Apache Software Foundation issued a notice over the weekend, indicating that it has added Facebook’s BSD+Patents license to its Category X list of disallowed licenses for Apache PMC members. This is the license that Facebook uses for most of its open source projects.

\n

A representative from Facebook’s RocksDB team commented on the Apache Foundation’s post to advise that the project will meet the August 31st deadline for relicensing in order to be in compliance with Apache PMC member requirements, and that change has been committed today:

\n

The RocksDB team is adjusting the licensing such that it will be dual-licensed under the Apache 2 and GPL 2 (for MySQL compatibility) licenses. This should happen shortly and well ahead of August 31st. I’ll leave the history and philosophy around licensing alone since it’s generally a complex discussion to have and I’m not sure that it has actually been fully captured in this thread especially vis a vis Facebook’s intent.

\n

Hopefully this morning’s guidance to PMCs can be adjusted since I don’t think any of us see a bunch of extra engineering effort as a desirable thing across the ASF projects which are already making use of RocksDB

\n

In light of the ASF Legal Affairs Committee’s decision to disallow the BSD+Patents License in Apache projects, ASF member Joan Touzet opened an issue on the React repository urging Facebook to consider re-licensing React.js under Apache License v2.0 and GPL 2:

\n

\nThis has led to a lot of upset and frustration in the Apache community, especially from projects requiring similarly-licensed code as direct dependencies – the chief of these being RocksDB.

\n

We (the Apache Software Foundation) have just received word that RocksDB will be re-licensing their code under the dual Apache License v2.0 and GPL 2 licenses.

\n

As a user of React.JS in an ASF top-level project (Apache CouchDB), please consider re-licensing React.JS under similar terms. Otherwise, many ASF projects such as our own will have to stop relying on and building with React.

\n

Although the re-licensing of RocksDB solves that particular project’s problem, ASF’s ban of Facebook’s BSD+Patents license means other widely used technologies from Facebook, including React.js, are still banned. This is likely to cause problems for many open source projects.

\n

Harshavardhana, from the Minio team, commented in support of the petition to Facebook for re-licensing React.

\n

“Our object storage browser UI is based on React and we are Apache 2.0 licensed,” he said. “It would be unfortunate and time consuming to migrate but we will have to do that in lieu of new information regarding Apache incompatibility. Please consider re-licensing React.”

\n

Contributors to Om, a ClojureScript interface for React, are also discussing whether or not the ASF’s new requirements will affect their project. Greg Stein, commenting on behalf of ASF, clarified the reasons behind the organization’s decision to ban Facebook’s BSD+Patents license:

\n

Please note that the ASF chose this path for policy reasons, rather than “license incompatibility”. We don’t want downstream users of Apache code to be surprised by the PATENTS grant that (was) in RocksDB and (is) in React. Users should only need to follow the ALv2, with no further constraints.

\n

These license can work together (IMO) and simply provide two sets of restrictions upon users.

\n

Stein said it was not ASF’s lawyers who made the decision but rather the organization’s policy decision to “disallow FB/BSD+Patent license to be mixed into the software the Foundation releases to users.”

\n

Facebook is Internally Discussing the Re-Licensing Matter

\n

Dan Abramov, co-author of Redux, Create React App, and React Hot Loader, joined the discussion on GitHub regarding re-licensing with a brief and ambiguous summary about how Facebook is handling the petition to re-license.

\n

“To give you a small update, there are going to be more internal discussions about this for about a week,” Abramov said. “This is about as much as I can say. I wouldn’t be too optimistic about this changing for React but we’ll see. @daveman692 has kindly agreed to provide an update when these discussions are over.”

\n

Dropping the patent grant entirely, which would be the most convenient way of solving this issue for open source projects, isn’t likely to happen. React has already gone through re-licensing twice during its short history. It was originally licensed under Apache 2.0 but this was changed in October 2014 to the BSD License plus the patent grant, which included a highly controversial termination provision. In April 2015, the patent grant was changed slightly to allow licensees to continue to use the software in the event that a patent lawsuit did not include a counterclaim against Facebook or its affiliates in a matter unrelated to React.js.

\n

The termination provision in Facebook’s BSD+Patents License continues to be unpopular and is regarded suspiciously by many open source project maintainers. When the Drupal project began considering a client-side framework to supersede Backbone.js, Dries Buytaert passed on React based on what he said was “a potentially unacceptable patent clause,” citing pushback from WordPress.com’s Calypso and React contributors.

\n

The WordPress open source project has not formally announced its decision on which JavaScript framework will be included in core, but all signs point to React. WordPress’ upcoming Gutenberg editor is built on React and its chief contributors are Automattic employees who work on React-based products for WordPress.com. Gutenberg continues to plough forward at a breakneck pace with no indication of a rewrite, and WordPress co-creator Matt Mullenweg has been outspoken about his preference for using React.

\n

Although Automattic’s legal counsel has said the company is comfortable using React for its product under the project’s current license , others in the WordPress community are not as amenable to including the framework in core.

\n

The Open Source Initiative (OSI) includes a generic BSD+Patent license listed among its approved licenses, but Facebook’s particular BSD+Patent license has not been submitted. Robert Pierce, a partner at El Camino Legal, contends that the license termination provision ought to be impermissible in an open source license because it exists to protect Facebook from patent litigation that is completely unrelated to React code:

\n

Facebook touts React.js as open source software. But in my mind the license termination provision of the Additional Grant of Patent Rights takes the offering outside the realm of open source software.

\n

The patent license offered in the Additional Grant of Patent Rights (v.2) is conditioned upon the licensee not bringing a patent infringement lawsuit against Facebook or its affiliates. Thus, the licensee pays a price to use the library. It is not a price paid with money. The price demanded by Facebook for use of the library is that the licensee refrain from exercising any of its patent rights against Facebook or its affiliates.

\n

Pierce views Facebook’s publication of React source code as leverage to win some protection against patent lawsuits, which he deems to be “too greedy an approach for Facebook to claim open source status.”

\n

The open source community has widely speculated about the implications of including Facebook’s BSD+Patent license as a dependency, but the license has not yet been tested in court. The Apache Software Foundation is the first major organization to take a hard line stance on the controversial license and this has caught Facebook’s attention. Facebook representatives have promised an update on the petition for re-licensing after its internal discussions have concluded.

\n
\";s: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, 18 Jul 2017 03:25:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:76:\"WPTavern: Stylishly Display Weather Conditions with the Weather Atlas Widget\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73229\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/stylishly-display-weather-conditions-with-the-weather-atlas-widget\";s: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:2207:\"

If you’re looking for an easy way to display weather conditions on your site, check out the new Weather Atlas Widget by Yu Media Group d.o.o. Once activated, browse to Appearance > Widgets, and add the Weather Atlas widget to a sidebar. 

\nWeather Atlas Settings\n

As you begin typing, a drop-down list of cities is displayed. This helps choose the correct city. From here, users can configure the following settings:

\n\n

Users can display sunrise and sunset times, heat index, wind chills, UV index, wind speeds, humidity, and pressure. You can also hide or display hourly forecasts.

\nForecast for Cleveland, Ohio\n

It’s recommended that for three-hour forecasts, you use the vertical layout and for five-hour forecasts, the horizontal layout. The same recommendations apply for daily forecasts.

\n

The widget not only looks nice but it also changes color based on temperature. Shades of blue represent cooler temperatures while shades of red represent warmer temperatures.

\nTemperatures Represented by Colors\n

By default, the bottom of the widget displays the text, “Weather from Weather Atlas”. However, if you choose to display the detailed forecast, the text is replaced with a Detailed Forecast link. This link takes visitors to a page on Weather-Atlas.com that displays detailed weather conditions for the selected city.

\n

I tested the Weather Atlas Widget on WordPress 4.8 and didn’t encounter any issues. It’s available for free on the WordPress plugin directory.

\n
\";s: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, 18 Jul 2017 01:55:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WPTavern: Gutenberg Boilerplate Demonstrates How to Build Custom Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73202\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/gutenberg-boilerplate-demonstrates-how-to-build-custom-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4716:\"

\n

Gutenberg is still in beta but developers are already getting ready for creating their own custom blocks. Over the weekend Ahmad Awais released a new project called Gutenberg Boilerplate For Third-Party Custom Blocks. Awais’ introductory post includes a rundown of his thoughts on the current pros and cons of developing for the Gutenberg project. Although he appreciates the technology behind Gutenberg and the improvements over shortcodes, he is not fully sold on the concept of putting everything into blocks. To learn more, he decided to jump into the code.

\n

“I am still making up my mind with how Gutenberg will fit in the WordPress core,” Awais said. “There are so many things which are both good and bad about it. So, instead of ranting about it, I wanted to do something more productive. I went ahead, studied the source code and received a lot of help from Gutenberg contributors (Matias Ventura, James Nylen, Riad Benguella, Andrew Duthie, Joen, etc.) to finally build a Gutenberg Boilerplate project.”

\n

Awais’ Gutenberg Boilerplate is a good starting place for learning more of the basics about developing for the editor. It comes in the form of a plugin that offers four examples of how to build different kinds of custom Gutenberg blocks, with and without a build process:

\n\n

For example, the tweet block, which is something that might previously been handled with a shortcode, is an example that includes four files: block.js to register the custom Gutenberg block, editor.css, style.css, and index.php.

\n

\n

Awais noticed that many developers were wanting to try building third-party blocks, but Gutenberg’s documentation for this was outdated and/or non-existent. He got involved in contributing to the project’s documentation after discovering the docs describing how to enqueue block and block editor assets were not available. This gave him the inspiration to create a boilerplate.

\n

“Both as a theme/plugin developer, I think there’s going to be a steep learning curve here for just about everyone – users as well as developers,” Awais said. “WordPress development just became very complicated with the Gutenberg project. I’m also not sure how devs will start writing extensions. Some users might expect them to keep the shortcodes for the old editor. Some might ask for blocks in the new one. Is there an API or back-compat? In short everything is changing and this change has both pros and cons.”

\n

These concerns also tie into the larger discussion around how Gutenberg can support legacy metaboxes that use the old PHP framework, instead of updating to the new JS.

\n

“New metaboxes should be written in JS, and will appear in the Post Settings sidebar alongside the stock ones,” Gutenberg contributor Joen Asmussen said. “Metaboxes written in PHP should ideally be upgraded to be JS, but should continue to work in their PHP form also.” Asmussen has proposed an “Extended Settings” panel to house legacy metaboxes in a section below the editor. It would appear only when legacy plugins and metaboxes are enabled, as shown in the mockup below.

\n

\n

Discussion regarding how to support metaboxes is still ongoing. With so many important issues like this up in the air, it’s too early to know what the future of extending Gutenberg will look like. At the moment, the project is undergoing rapid development and changes, so extending Gutenberg may evolve drastically over a short period of time. If the editor is to preserve the same flexibility and customization opportunities of its predecessor, the project will need to ensure that it is easy to create custom blocks and extensions while continuing to support older PHP metabox infrastructure that is currently widely used.

\n
\";s: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, 17 Jul 2017 20:28: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: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:93:\"WPTavern: Gutenberg 0.5.0 Adds New Verse Block for Poetry and a New Display for Recent Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72830\";s:7:\"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:\"https://wptavern.com/gutenberg-0-5-0-adds-new-verse-block-for-poetry-and-a-new-display-for-recent-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5718:\"

Another round of Gutenberg updates was released today. Last weekend brought version 0.4.0, which didn’t have too many noteworthy visible changes on the frontend but introduced an API for handling pasted content. Gutenberg developers are aiming to have specific handling for converting pasted content from applications like Word, Markdown, and Google Docs to native WordPress blocks. Version 0.4.0 also added navigation between blocks using arrow keys and included a new approach for rendering embed frames.

\n

Gutenberg 0.5.0 hit dashboards today. One major improvement to the writing flow is that the editor will now avoid showing block UI while the user is typing and/or starting a new paragraph in a text block. You can test this by typing and pressing enter twice to begin a new text block. No UI should be visible during this process. Small improvements like this one are gradually bringing a bit more zen to the editor, which is still full of confusing and surprising experiences.

\n

Version 0.5.0 adds the ability to upload images via drag-and-drop onto image block placeholders. The example below shows one of my tests. While the image is uploading, it fades in and out. This experience is a bit disconcerting, especially if the upload never resolves. I’m not certain this UI provides the best communication for the status of the image upload.

\n

\n

This version also introduces a new Verse block, which is intended for poetry. It has a slight indent, as compared to a plain text block, but it doesn’t yet work well with copy and paste. Unless you are a poet composing in WordPress, it’s far more likely that you will be pasting in poetry content from somewhere else on the web. Other than the initial bugs, it’s a useful block for those who often post verse.

\n

\n

With the growing number of block types, it can be cumbersome to sort through all of them when adding a new block. Gutenberg 0.5.0 implements a new display for recent blocks. A maximum of eight are shown and the most recently used ones are displayed at the top. It does not yet persist between editor sessions, but Gutenberg contributors plan to add that in the future.

\n

\n

Other notable improvements in this release include the following:

\n\n

Writing Long-Form Content with Gutenberg is Still a Frustrating Experience

\n

Gutenberg in its current state is a long way away from being an editor that users would embrace for long-form writing. It still contains many unnerving bugs that steal user confidence. For example, when pasting in multiple paragraphs from a lorem ipsum generator, the editor gave me a white screen and I lost all of the content in my post. After a bit of testing I found that pasting in paragraphs one at a time worked.

\n

This kind of frustrating and unexpected behavior has caused many testers to wonder why it isn’t being referred to as alpha software instead of beta. WordPress contributor Jon Brown summed up this common sentiment in a comment on the 0.4.0 release post.

\n

“It’s getting better, but it honestly still feels more like a 0.0.4 alpha than a 0.4.0 beta,” Brown said. “I’ve tried writing long form content several times with each version since 0.1.0 and each time I’m quickly frustrated by the lack of flow between blocks. It’s more frustrating than TinyMCE.”

\n

Gutenberg needs to make significant progress before it can be suitable for writing anything more than a few short paragraphs. It’s nearly impossible to get into the flow of creating long-form content with the prominence of the block UI. Right now, the editor just gets in the way. The current UI is skewed heavily towards frequent block creation. It is clutter-some and distracting for pure writing tasks. Following the evolution of the editor, with its fast-paced development cycle, is exhilarating after years of stagnation. But the project is sorely in need of a breakthrough where the Gutenberg UI finally gets out of the way of writing.

\n
\";s: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, 15 Jul 2017 05:14:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:89:\"WPTavern: Jetpack Professional Plan Introduces Unlimited Access to 200+ Commercial 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:29:\"https://wptavern.com/?p=73055\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wptavern.com/jetpack-professional-plan-introduces-unlimited-access-to-200-commercial-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:3407:\"

Automattic has been teasing its plan to add commercial themes to Jetpack for several months after introducing theme installation for self-hosted users from WordPress.com. In March, the plugin opened up access to all of WordPress.com’s free themes via the Jetpack Manage interface. All signs pointed to Automattic developing the infrastructure to offer commercial themes via Jetpack upgrades. At that time, however, Jetpack team member Richard Muscat said that Automattic had “no immediate plans to sell themes at this time.”

\n

\n

Yesterday those subscribed to the Jetpack Announcements email were notified that commercial themes have landed in the Jetpack Professional plan, which is regularly priced at $24.92/month or $299/year. Customers will have unlimited access to more than 200 commercial themes that are already available on WordPress.com. Jetpack users on the free plan will see all the themes available in the WordPress.com theme browser with a prompt to upgrade for the ones that are commercial.

\n

\n

The announcement also noted that any themes users elect to use will be automatically backed up and regularly scanned for malware as part of the security services included in the package. For those who are running a multisite network, each site will need its own Jetpack Professional subscription to have access to the commercial themes.

\n

For years the WordPress community has speculated about what Automattic’s long game was for Jetpack, and many believed it was only a matter of time before the plugin started offering commercial upgrades. It was introduced to the WordPress world in 2011 as a way to provide feature parity between WordPress.com and self-hosted sites. The first version included just eight modules, but fellow plugin developer and entrepreneurs in the community were immediately aware of its commercial potential.

\n

In 2016, Automattic CEO Matt Mullenweg identified both Jetpack and WooCommerce as “multi-billion dollar opportunities” that could each individually be larger than WordPress.com. The plugin is now active on more than 3 million WordPress sites. Automattic’s aggressive commercialization of Jetpack in the past two years is the fulfillment of initial predictions about where the plugin was headed.

\n

The new commercial themes offering significantly raises the value of the Jetpack Professional plan, which was previously targeted at business users who require unlimited storage, Google Analytics, and additional SEO features. With the addition of unlimited use of 200+ themes, Automattic has expanded the Professional plan to be more compelling for non-business users who are simply interested in gaining access to a collection of professionally-supported themes.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 21:46:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"BuddyPress: BuddyPress 2.9.0 Release Candidate 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:32:\"https://buddypress.org/?p=267012\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://buddypress.org/2017/07/buddypress-2-9-0-release-candidate-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2980:\"

Today sees BP 2.9.0 move to The final testing phase Release Candidate 1.

\n

This is the last chance to test out this release and report back any issues found before final release in approximately two weeks time.

\n

Any issues found can be reported to our trac ticket home , or raised on the support forum.

\n

Amongst other improvements and fixes to look out for are:

\n\n

For a full list of commits see 2.9 tickets A full changelog will be available when we release the final version.

\n

You can download the plugin to test from the WP repo BP 2.9.0-RC1 or grab a copy from our SVN repo.

\n

A reminder to all theme developers that there are changes to template markup that could effect layouts and ask that they check their themes carefully, the changes are listed below along with changelog links; again any issues or problems please report as soon as possible to the BP trac or slack channel.

\n

Template changes

\n

In this release there are a number of improvements to templates that add a level of improved a11y performance and markup changes for better semantics & Standards.

\n

Theme authors may want to pay particular attention to changes to profile field visibility links and the profile field descriptions where significant markup changes are made that effect positioning of these elements – changesets for these are r11617 & r11618

\n

Nouveau – new template pack

\n

If you’re looking for Nouveau as we mentioned in the beta2 announcement we have delayed the release of this new template pack to ensure it receives as much code checking & refinement as possible and we’ll be looking to probably package this as it’s own release shortly after 2.9 is released.

\n

We thank you in advance for all testing and reports and it need not be mentioned but please don’t run Beta or RC releases in a production environment only on test installs.

\n

Regards,
\nThe BuddyPress team.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 12:57:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Hugo Ashmore\";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:102:\"WPTavern: CoKinetic Systems Pursues $100 Million GPL License Violation Case Against Panasonic Avionics\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72923\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"https://wptavern.com/cokinetic-systems-pursues-100-million-gpl-license-violation-case-against-panasonic-avionics\";s: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:7082:\"photo credit: Paper Plane(license)\n

Open source software has made its way into nearly every industry, but a recent open source security and risk analysis shows widespread license compliance risks, with 75% of the audited applications including GPL license conflicts. Although most violations are unintentional, there are some cases where companies do not comply with the license in order to block competitors from developing similar software.

\n

GPL enforcement doesn’t often lead to litigation. When it does, most other avenues of resolving the complaint have already been exhausted. A lawsuit in the air transport industry is currently bringing more attention to the gravity of not complying with open source software licensing requirements.

\n

CoKinetic Systems, a developer and manufacturer of in-flight entertainment (IFE) software, has filed a case against Panasonic Avionics that includes allegations of a fairly egregious breach of the GPL. The complaint alleges that Panasonic Avionics has monopolized the Panasonic IFE Software and Media Services Market by deliberately refusing to distribute the source code for its open-source Linux-based operating system:

\n

More specifically, Panasonic has built the Linux-Based Panasonic Core Software using the open-source Linux kernel, which is clearly governed by the GPL, together with Panasonic’s own modified Linux modules, which are likewise governed by the GPL.

\n

Indeed, Panasonic has itself affirmatively identified its own modified modules as being subject to the GPL, because the original Linux modules were specifically designed to generate warning messages if other code is linked with or otherwise combined with the Linux modules that are not licensed under the GPL. To suppress these warnings, Panasonic willfully acted to insert code into its own modules to indicate that they were licensed under the GPL.

\n

Panasonic has incorporated a massive amount of open source modules, programs, and libraries into the Linux-Based Panasonic Core Software, without distributing notices or source code to the Linux-Based Panasonic Core Software, or even to any part of it…By deliberately refusing to distribute the source code to the Linux-Based Panasonic Core Software in accordance with its GPL obligations, Panasonic intentionally deprives competitors in the market from having the ability to develop software that can access the basic features and capabilities of Panasonic IFE Hardware.

\n

CoKinetic Systems contends that Panasonic’s refusal to distribute its source code voids its GPL license and “potentially exposes Panasonic to billions of dollars in statutory damages for hundreds of thousands of hardware installations that willfully infringe copyrights belonging to hundreds or even thousands of software developers that freely contributed source code to Linux.”

\n

Furthermore, the complaint details how competitors have to rely on Panasonic’s APIs in order to offer software services to airlines using Panasonic’s IFE hardware, because they do not have access to the source code for the Linux-based core software. CoKinetic claims that Panasonic also deliberately blocks competitor products by its selective distribution of its APIs, resulting in stifled industry innovation and monopoly control over the Panasonic IFE Software and Media Services Market.

\n

Perhaps the worst and most grave allegation in the complaint is that, in addition to locking up the source code and doling out access to the APIs, Panasonic also maliciously sabotaged its own APIs in order to give the appearance that it is the only reliable software service provider for its hardware, which CoKinetic claims is inferior and sold at monopolistic prices.

\n

Panasonic also is able to use its control over the Linux-Based Panasonic Core Software in order to make ongoing, undisclosed, and often malicious modifications to its source code, deliberately “breaking” Panasonic’s own APIs in order to purposely and maliciously sabotage the performance of third-party software products that Panasonic deems a competitive threat — particularly CoKinetic software.

\n

In the introduction to the case, CoKinetic cites a litany of anti-competitive conduct the company has engaged in over the past decade before detailing the current allegations. The case is not purely an open source license dispute, as the plaintiff also alleges that Panasonic abused regulatory processes, engaged in acts of corporate espionage, defamed CoKinetic, paid commercial bribes, and employed unlawful means to monopolize the Panasonic IFE Software and Media Services Market.

\n

CoKinetic is seeking compensatory damages for Panasonic’s GPL ongoing GPL breaches. The specific amount would be determined at the trial but the company believes it to be in excess of $100 million. The company also wants the court to compel Panasonic to publicly disclose and distribute the source code.

\n

This isn’t a case where distributing the source code is just a small sticking point or just a matter of principle. It has the potential to open up the IFE industry for faster progress and greater innovation. Many reading this article have undoubtedly used Panasonic’s IFE products when flying with the company’s customers, which include Emirates Airlines, Delta Air Lines, Virgin America, and United Airlines. With the source code available, airline customers could remove Panasonic’s software from their IFE hardware and replace it with their own software solutions.

\n

The complaint, which was filed in the Southern District of New York in March, demands a jury trial. An initial pre-trial conference was held in May, but the case has been slow moving. The Court gave a deadline for the Defendant to file its motion to dismiss, but deadlines have since been extended. The Court also strongly recommended that the two parties retain a private mediator but it’s not clear how outside mediation could solve such a far-reaching matter that impacts so many vendors. Additional documents are due over the next few months, so it will be some time before there are updates on the progress of the case.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 04:39: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:\"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:45:\"WPTavern: AJ Morris Acquires iThemes Exchange\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73071\";s:7:\"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://wptavern.com/aj-morris-acquires-ithemes-exchange\";s: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:3545:\"

In 2013, iThemes released Exchange, an e-commerce platform that aimed to make selling online as simple as possible. Today, the company announced that AJ Morris, Product Manager at Liquid Web, has taken over the project.

\n

“When approached about taking over iThemes Exchange early this year, we wanted to be sure the project and our customers went into very competent hands, someone who will love and care for them as much as we do,” Cory Miller, founder of iThemes, said.

\n

“Having spent four and a half years investing in the project and in you and your success, we did not take this lightly.

\n

“After numerous conversations over the past several months, we believe the best home for Exchange is with ExchangeWP LLC led by AJ Morris.”

\n

Everything iThemes Exchange related will transition to ExchangeWP.com. Toolkit, Plugin Suite, Exchange Pro Pack, and iThemes Exchange Add-on customers will be given accounts for free support and upgrades through August 2018 at ExchangeWP.com.

\n

Beginning today, customers will no longer be able to purchase Exchange or its add-ons through iThemes as the company transfers licenses and products to ExchangeWP. However, iThemes will continue to provide customer support until the transition is completed, expected to happen in early August.

\n

Morris says he’ll continue to focus on making e-commerce simple and will provide regular updates to customers to provide insight into what goes into transition a product from one company to another and where the product is heading.

\n

“These days, it’s very easy to get WordPress up and running so you can start blogging,” Morris said. “But when you want to add e-commerce to the mix, it’s a bit different.”

\n

“With big players like WooCommerce out there, it becomes too much too quickly for the average content producer to get their store up and running.

\n

“Exchange is going to continue focusing on the independent publishers that want to keep the revenue they can, while providing a simplistic experience in an easy-to-use e-commerce plugin that will help get their stores online quickly.”

\n

Allowing Morris to take over the project frees up resources for iThemes to focus on three of its flagship products; BackupBuddy, iThemes Security, and iThemes Sync. In addition to their core products, the company says it will soon release a new project.

\n

“My job as CEO is to be a steward of the time and resources we have at iThemes in order to serve you best,” Miller said.

\n

“We’ve realized for a while that it was past time for us to refocus our finite resources on the projects that have the most growth and potential for our company and you.

\n

“That meant we either needed to find a new home for Exchange or sunset the project. I’m thankful we didn’t have to do the latter.”

\n

Morris is a long-time member of the WordPress community and has spoken at several WordCamps. With Morris taking over the reigns, existing customers won’t have to worry about finding a replacement.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 01:00:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:23;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"Akismet: Akismet WordPress Plugin 3.3.3 Now Available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"http://blog.akismet.com/?p=1953\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://blog.akismet.com/2017/07/13/akismet-wordpress-plugin-3-3-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1413:\"

Version 3.3.3 of the Akismet plugin for WordPress is now available.

\n

For a full list of the changes in this release, see the revision log, but here are some notable fixes:

\n\n

To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory.


\"\" \"\"\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jul 2017 22:00: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:17:\"Christopher Finke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:68:\"WPTavern: WordPress.com Introduces Scheduling for Social Media Posts\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73026\";s:7:\"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:\"https://wptavern.com/wordpress-com-introduces-scheduling-for-social-media-posts\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2916:\"

WordPress.com is venturing into the realm of social media management applications with its latest feature that allows users to schedule Facebook, Twitter, and LinkedIn updates for individual posts. This goes beyond the basic Publicize functionality that automatically shares posts to connected accounts as soon as they are published, giving users the ability to automate their content marketing to social networks for the most optimal time for sharing.

\n

\n

It’s difficult to know how a post will appear on social networks once it has automatically been shared, which is one reason why many people choose to manually share a post for the best presentation. You want to ensure that the right thumbnail will show up with a message customized for each network’s particular audience. The new social scheduling feature on WordPress.com includes a built-in preview screen so users can see what the post will look like once it is shared to the network and then make any necessary tweaks.

\n

\n

Scheduling social media posts is available on WordPress.com for Premium and Business plan users and for Jetpack Professional and Premium users. On the Premium plan level, which comes in at ~$9/month, users pay less than they would for scheduling apps like Buffer, Hootsuite, or Sprout Social while also getting access to more commercial WordPress features.

\n

To truly become a realistic replacement for these types of social media marketing apps, WordPress.com would need to offer better analytics tied into the new sharing feature to show how posts are performing at different times and networks. Although WordPress.com allows for unlimited scheduling and users, it would also need to allow sharing to more networks to be more competitive against these apps. For users who don’t need all of that data but just want the scheduling feature, a paid Jetpack or WordPress.com plan is a more affordable option.

\n

Several other self-hosted WordPress plugins already offer scheduling social media posts for free and some even integrate the social accounts with Google Analytics. The addition of this feature to Jetpack commercial plans may not be as compelling for self-hosted users who can already find this for free, but it adds value for existing Jetpack customers who may now be able to replace a plugin or third-party service.

\n
\";s: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, 13 Jul 2017 19:59:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:62:\"WPTavern: WPWeekly Episode 281 – In Memory of Jesse Petersen\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=73045&preview=true&preview_id=73045\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wptavern.com/wpweekly-episode-281-in-memory-of-jesse-petersen\";s: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:2501:\"

In this episode, John James Jacoby and I are joined by Ben Meredith. Over the past few years, Ben has established a friendly and professional relationship with Jesse Petersen, who passed away due to complications from Cystic Fibrosis.

\n

Ben shares his unique perspective on who Petersen was as a person and describes the challenges of taking over his business. We emphasized how important it is to create a file with passwords and other login information to help appointed people access a person’s digital presence. We also discuss if saying a person lost their battle with an illness is a negative thing to say.

\n

To close out the show, we talk about net neutrality, 10up acquiring Lift UX, and Let’s Encrypt offering wildcard certificates in 2018.

\n

Stories Discussed:

\n

Automattic Releases Net Neutrality WordPress Plugin Ahead of July 12 Protest
\n10up Acquires Lift UX
\nLet’s Encrypt Passes 100 Million Certificates Issued, Will Offer Wildcard Certificates in January 2018

\n

Picks of the Week:

\n

Newlungsfor.me is a place to read about Jesse’s battle with Cystic Fibrosis along with CFfatboy.com.

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, July 19th 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #281:
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jul 2017 22:00:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:97:\"WPTavern: Sustain Event Draws 100 Attendees to Discuss the Sustainability of Open Source Software\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73014\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/sustain-event-draws-100-attendees-to-discuss-the-sustainability-of-open-source-software\";s: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:5136:\"

\n

More than 100 open source project maintainers and industry leaders gathered at the GitHub headquarters in San Francisco last month to discuss the long-term sustainability of open source software. The Sustain event, put on by a relatively new organization called SustainOSS, did not follow a traditional conference format with talks and keynotes but was intentionally left unstructured to foster open discussion.

\n

Organizers expected 50 attendees but ended up with double their estimates. The $50 ticket price covered day care, travel assistance, food, and other miscellaneous event costs. Attendees shared insights from their diverse backgrounds and participated in collaborative working sessions and various discussions facilitated by organizers.

\n
\n

Defining a common unified theory of open source sustainability is super hard! #sustainoss pic.twitter.com/2PznN2oZGM

\n

— Lou Huang (@saikofish) June 19, 2017

\n

\n

Co-organizer Alanna Irving shared in her wrap-up post how the team used Open Collective to make the event’s finances transparent and offer payment options for participants and sponsors. The service has recently added a new feature that allows collectives to communicate event info and sell tickets.

\n

Representatives from large tech companies attended the event, as well as contributors from various open source projects and foundations, including Google, Amazon, Paypal, Airbnb, Red Hat, JS Foundation, Linux Foundation, Apache Foundation, npm, FontAwesome, GulpJS, and more. Irving published a few insights from the discucssions that she and her colleagues are applying to their work at Open Collective:

\n\n

On the day following the event, SustainOSS organizers tweeted out a link to a new forum on GitHub for discussing open source sustainability. Proposed topics include fundraising, governance, contributor retention, productivity, and managing corporate relationships. It was created to offer a safe place for open source sustainers to collaborate with each other in the open and contributors have already submitted some practical ideas for discussion, such as adding a standardized FUNDING or SUSTAINABILITY file to repositories.

\n
\n

Busy day, got a lot done. Stay tuned. #sustainoss #sustain17 pic.twitter.com/CtWs82FXAn

\n

— SustainOSS (@SustainOSS) June 20, 2017

\n

\n

Sustain was inspired by inspired by the Maintainerati event held in London in May 2017. The similarly unstructured event brought together open source maintainers who share similar challenges. GitHub also hosted the Wontfix Cabal event at its San Francisco headquarters in February, which highlighted some of the difficulties related to maintaining OSS projects. Events focused on maintaining and funding OSS have been popping up in the past two years, as more people become aware that open source infrastructure has a critical sustainability problem.

\n

The SustainOSS organizers will be releasing a more detailed article on the event soon. They are also open to considering hosting other Sustain events in different locations. Follow @SustainOSS on Twitter for the latest updates.

\n
\";s: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, 12 Jul 2017 20:38: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: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:89:\"HeroPress: How I found myself in WordPress – Как я нашел себя в 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:56:\"https://heropress.com/?post_type=heropress-essays&p=1962\";s:7:\"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:128:\"https://heropress.com/essays/i-found-myself-in-wordpress/?utm_source=rss&utm_medium=rss&utm_campaign=i-found-myself-in-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:22562:\"\"Pull

Это эссе также доступно на русском языке.

\n

About Russia and familiarity with technologies

\n

Russia is a very large and very different country. The basic population, as well as technological development, is concentrated in the central part of the country, in “city-states”: Moscow and St. Petersburg. Other regions are much less developed: lower wages, worse and more expensive infrastructure, fewer IT-vacancies and activities.

\n

I was born and grew up in a remote part of Russia – in the Far East, in one of the industrial cities, which is located in 7 time zones and 9000 kilometers from Moscow. The Internet, like other technologies, reached there with a significant delay and for a lot of money (unlimited Internet at a speed of 64 kb/s appeared only in 2007), Therefore, at first, the basics of site building had to be learned in snatches with the help of dial-up.

\n

The first site I did in school. It was built using simple HTML and CSS. But even in this form, it was very impressive and exciting. Then such sites were popular and periodically on the Internet I met guys of my age who like me comprehended the science of site building.
\nI was lucky to find a like-minded person, with whom we were able to develop together for some time and even launch a joint website.
\n\"\"

\n

University and start of work

\n

Admission to the computer faculty of the university allowed to more specifically address the issues of web development: to learn PHP and MySQL, to get acquainted with a couple of CMS and to make my first blog on WordPress :). As far as I remember, the blog worked on some WordPress assembly using version 2.9. If you count from that moment, it turns out that I somehow have been working with WordPress for almost 8 years.

\n

In those days, ru.wordpress.org was just born and there was no main site on the Russian-language Internet. It was a time of amateur assemblies, amateur translations and even alternatives of WordPress, aimed to the Russian segment of the Internet.

\n

By the will of fate, my first place of work related to website development was the web studio that used Joomla and Drupal. Then there were a few more places of work, during which time WordPress then turned into the main working tool, then returned to the category of extra work and hobbies.

\n

The turning point was the decision to move to Moscow and a full transition to WordPress in freelance format.

\n

Moving to Moscow

\n

The scenario of moving to Moscow or St. Petersburg is quite popular among IT specialists of my native region. This is a great chance to find interesting and highly paid job, get acquainted with a lot of IT specialists, including narrow ones, and develop in the area of interest.

\n

In Moscow, I moved with remote work and I do not have personal experience of employment in this city, but my wife and most of the acquaintances were satisfied with the options found.

\n

After about six months of living in Moscow, I was even more thirsty for adventure — to become a freelancer and completely concentrate on WordPress. The ability to plan time independently gives additional space for maneuvers and time for reflection. In my case, this led to an increase in activity in the WordPress community.

\n

Participate in the WordPress community

\n

Actively participate in the life of the community, I started about 1.5 years ago. Initially, these were the replies at the support forum, then the development of my plugins, after which I decided to try myself in translating the extensions into Russian and recording training videos for Russian-speaking users.

\n

Over time, it turned into a kind of hobby or even a way of life. Every day I read a lot of posts from users on the support forums and try to help resolve their issues, check and correct the added translation lines, periodically record and post training videos.

\n

Communication with users is very helpful. You are one of the first to learn about the problems and ways to solve them, you can quickly correct some incorrect or incorrect translation. Also, over time, a list of popular questions accumulates, which can be turned into training articles and videos. In turn, the creation of articles and videos helps to structure knowledge and understand the details.

\n

On ru.wordpress.org a great team of moderators and translation editors has gathered. We regularly communicate in Slack, some I meet on WordCamp.

\n

\"Denis

\n

In November 2016 I took part in the Global Day of Translation 2. It was an unusual experience: broadcasting from around the world, feeling the scale of what was happening and the excitement of the translation. At that time we took 6th place as the most active locale and attracted 7 new translators.

\n

Meetups and WordCamp

\n

In Russia there are not so many cities where WordPress-meetups are held, and WordCamp is held only in Moscow. But despite all this, these events are a great opportunity to be among WordPress lovers, to see live people with whom I have only spoken on the network before, and just feel the spirit of WordPress :).

\n

\"Three

\n

This year I plan to visit WordCamp Moscow for the third time. I visit WordCamp as a participant, but I hope someday I will find a topic close to me and I will decide to apply for a presentation :). I think it will be interesting.

\n

Conclusion

\n

At the moment I’m a full-time freelancer. This allows me to quite well combine work and activities in the community. I like to share knowledge and make WordPress more accessible for Russian users.

\n

Many resources of WordPress are dominated by English, and some, for example, as developer.wordpress.org or “Handbook” are not available for localization. I hope, in the future this will change and we will be able to expand our activities.

\n

In any case, WordPress remains the place where you can find yourself and help make life a little better for yourself and the rest of the participants.

\n
\n

Как я нашел себя в WordPress

\n

Про Россию и знакомство с технологиями

\n

Россия очень большая и очень разная страна. Основное население, как и технологическое развитие, сосредоточено в центральной части страны, в “городах-государствах”: Москве и Санкт-Петербурге. Остальные регионы развиты значительно слабее: ниже зарплаты, хуже и дороже инфраструктура, меньшее количество IT-вакансий и мероприятий.

\n

Я родился и вырос в отдаленной части России — на Дальнем Востоке, в одном из промышленных городов, который расположен в 7 часовых поясах и 9000 километров от Москвы. Интернет, как и другие технологии, доходили туда с существенным опозданием и за большие деньги (безлимитный интернет на скорости 64 кб/сек появился только в 2007 году), поэтому, по началу, азы сайтостроения приходилось познавать урывками с помощью dial-up.

\n

Первый сайт я сделал ещё в школе. Он был построен на простейшем HTML и CSS. Но даже в таком виде, это было очень впечатляюще и захватывающе. Тогда такие сайты были популярны и, периодически на просторах интернета, я встречал ребят моего возраста, которые, как и я, постигали науку сайтостроения.

\n

Мне повезло найти единомышленника, с которым мы смогли некоторое время вместе развиваться и даже запустить совместный сайт.

\n

\"Very

\n

Университет и начало работы

\n

Поступление на компьютерный факультет университета позволило более предметно заняться вопросами веб-разработки: изучить PHP и MySQL, познакомиться с парой CMS и завести свой первый блог на WordPress :). Насколько я помню, блог работал на какой-то сборке WordPress, использующей версию 2.9. Если вести отсчет с того момента, то получается, что я так или иначе работаю с WordPress уже почти 8 лет.

\n

В те времена ru.wordpress.org только зарождался и в русскоязычном интернете не было какой-то основной площадки. Это было время любительских сборок, любительских переводов и даже альтернатив WordPress, ориентированных на русский сегмент интернета.

\n

Волею судеб, моим первым местом работы, связанным с разработкой сайтов, стала веб-студия, использовавшая Joomla и Drupal. Затем было ещё несколько мест работы, в течение которых WordPress то превращалась в основной рабочий инструмент, то возвращалась в разряд дополнительной работы и хобби.

\n

Переломным моментом стало решение о переезде в Москву и полный переход на WordPress в фриланс-формате.

\n

Переезд в Москву

\n

Сценарий переезда в Москву или Санкт-Петербург достаточно популярен среди IT-специалистов моего родного региона. Это отличный шанс найти интересную и высокооплачиваемую работу, познакомится со множеством IT-специалистов, в том числе узких, и развиться в интересующей области.

\n

В Москву я переезжал вместе с удаленной работой и у меня нет личного опыта трудоустройства в этом городе, но моя жена и большинство знакомых остались довольны найденными вариантами.

\n

Примерно через полгода проживания в Москве, меня обуздала ещё большая жажда приключений — стать фрилансером и полностью сосредоточиться на WordPress. Возможность самостоятельно планировать время дает дополнительное пространство для маневров и время на размышления. В моем случае, это привело к увеличению активности в сообществе WordPress.

\n

Участие в сообществе WordPress

\n

Активно участвовать в жизни сообщества я начал примерно 1.5 года назад. Вначале это были ответы на форуме поддержки, затем разработка своих плагинов, после чего я решил попробовать себя в переводе расширений на русский язык и записи обучающих видео для русскоязычных пользователей.

\n

Со временем это превратилось в некое хобби или даже образ жизни. Каждый день я читаю множество сообщений от пользователей на форумах поддержки и пытаюсь помочь решить их вопросы, проверяю и корректирую добавленные строки перевода, периодически записываю и выкладываю обучающие ролики.

\n

Общение с пользователями очень помогает. Ты одним из первых узнаешь о проблемах и способах их решения, можешь оперативно исправить какой-то неверный или некорректный перевод. Также, со временем накапливается список популярных вопросов, которые можно превращать в обучающие статьи и ролики. В свою очередь, создание статей и видео помогает структурировать знания и разобраться в деталях.

\n

На ru.wordpress.org собралась отличная команда модераторов и редакторов переводов. Мы регулярно общаемся в Slack, некоторых я встречаю на WordCamp.

\n

\"Denis

\n

В ноябре 2016 я принимал участвовали в Глобальном дне перевода 2. Это был необычный опыт: трансляции со всего света, ощущение масштабности происходящего и азарта перевода. В тот раз мы заняли 6 место как самый активный язык и привлекли 7 новых переводчиков.

\n

Митапы и WordCamp

\n

В России не так много городов, где проводятся WordPress-митапы, а WordCamp проводится только в Москве. Но не смотря на всё это, данные мероприятия — отличная возможность побыть среди любителей WordPress, увидеть в живую людей, с которыми до этого общался только по сети, и просто почувствовать дух WordPress :).

\n

\"\"

\n

В этом году я планирую посетить WordCamp Moscow в третий раз. Я посещаю WordCamp как участник, но надеюсь когда-нибудь найду близкую мне тему и решусь подать заявку на выступление :). Я думаю, это будет интересно.

\n

Заключение

\n

На данный момент я — фул-тайм фрилансер. Это позволяет мне достаточно неплохо совмещать работу и деятельность в сообществе. Мне нравится делиться знаниями и делать WordPress доступнее для русскоязычных пользователей

\n

На многих ресурсах WordPress преобладает английский язык, а некоторые, например, как developer.wordpress.org/ или “Handbook” вовсе недоступны для локализации. Надеюсь, в будущем это изменится и мы сможем расширить свою деятельность.

\n

В любом случае, WordPress остается тем местом, где можно найти себя и помочь сделать его чуточку лучше для себя и остальных участников.

\n

участник

\n

\"Denis

\n

 

\n

 

\n

 

\n

 

\n

 

\n

 

\n

 

\n

 

\n

Денис Янчевский

\n\n

The post How I found myself in WordPress – Как я нашел себя в WordPress appeared first on HeroPress.

\";s: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, 12 Jul 2017 12:00:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Denis Yanchevskiy\";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:86:\"WPTavern: Automattic Releases Net Neutrality WordPress Plugin Ahead of July 12 Protest\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72930\";s:7:\"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:97:\"https://wptavern.com/automattic-releases-net-neutrality-wordpress-plugin-ahead-of-july-12-protest\";s: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:2074:\"

Automattic announced its intent to protest the FCC’s attack on net neutrality today by making a way for the millions of WordPress.com users to join in. The company’s logo has been listed on the Save Net Neutrality event website for some time but it had yet to announce how it would be participating. WordPress.com users are encouraged to send a message to the FCC and also enable the Fight for Net Neutrality Plugin via the dashboard Settings screen.

\n

The plugin is open source and available to self-hosted users on WordPress.org. Unlike the existing plugins that support the event on July 12 by presenting visitors with a banner to raise awareness, Automattic’s plugin simulates what life might be like in the “slow lane” if the FCC abandons the principle of net neutrality. It replaces a few of the posts on your site with a “Still Loading” spinner. This plugin doesn’t seem to offer a way to test it ahead of the event, but it essentially displays a message at the bottom of your website and slows down some of your posts.

\n

\n

The plugin will automatically be disabled after the event has concluded, so both WordPress.com and self-hosted users do not have to worry about turning it off and can remove it later. If you are uneasy about slowing down some of your posts as part of the protest and feel more comfortable displaying a modal or a widget, check out the Internet Defense League Cat Signal or the Fight for the Future Alerts plugins as alternatives.

\n
\";s: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, 12 Jul 2017 05:07: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:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:29;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: VersionPress 4.0 Beta Adds User-Editable Location for Plugin Definitions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72939\";s:7:\"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:\"https://wptavern.com/versionpress-4-0-beta-adds-user-editable-location-for-plugin-definitions\";s: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:2944:\"

VersionPress 4.0 beta is available for testing. It includes a number of improvements, most notably, the ability to load plugin definitions from a user-defined location within the wp-content directory.

\n

Plugin definitions are files used to understand data, actions, shortcodes, and other things plugins do in order to automatically provide version control for them.

\n

According to Borek Bernard, co-founder of VersionPress:

\n

If you create a folder WP_CONTENT_DIR/.versionpress/plugins/woocommerce and put definition files like schema.yml or actions.yml there, VersionPress will use and actually prefer it over the bundled definitions if they exist.

\nUser Defined Location of Plugin Definition File\n

Support for WooCommerce and Jetpack are included in 4.0 Beta 1. VersionPress will automatically detect the definition file as long as each plugin has a .versionpress folder in it.

\n

With the release of 4.0 Beta, Bernard says a repository containing plugin definitions is next on the list and is encouraging plugin authors to contribute to the project.

\n

“The final step is to have an online repository of the definitions,” Bernard said. “It will be open to anyone to contribute, not just plugin authors, and used by VersionPress transparently.”

\n

For insight on how to create definitions, developers can look at WordPress core and WooCommerce for real-world examples.

\n

Other major changes include full support for WordPress 4.7 and 4.8, adoption of GitHub projects to help manage the development process, and a number of bugs fixed.

\n

Developers and users can download 4.0 Beta from GitHub. Users are encouraged to test the plugin in a staging environment as it’s not ready to be used on live sites. If you encounter an error, you can report it by creating a new Issue request on the project’s GitHub page.

\n
\";s: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, 12 Jul 2017 04:26:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:\"WPTavern: 10up Acquires Lift UX\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72917\";s:7:\"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://wptavern.com/10up-acquires-lift-ux\";s: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:4294:\"

\n

10up, a leading WordPress design and development agency, has acquired Lift UX, a smaller user experience design-driven agency that will bolster the company’s existing Experience design team. Lift founders Chris Wallace and Brad Miller will join 10up’s 120+ person distributed team, along with Lift’s director of technology, Christian Chung, and front-end developer Anthony Garand.

\n

10up is acquiring the Lift UX brand, hiring four team members, and will also take possession of RemoteJobs.com, which will continue operating independently as a remote job board. The Lift UX brand will be dissolved and clients and projects are in the process of transitioning over to 10up.

\n

“We were always looking for agencies to partner with and when I reached out to 10up I was looking to build a relationship to help work on UX design projects,” Miller said. “10up has a strong engineering background and I felt like having them as a partner would be huge for our agency. Jake and I quickly realized that Lift UX and 10up had so many similar processes that it sounded like our two companies were the same but just different in size.”

\n

With similar expertise serving large clients in the WordPress space, the two companies were bound to end up competing on different projects, which happened during the course of their conversations spanning a year leading up to the deal. Miller said 10up founder Jake Goldman proposed a merger/acquisition type of approach.

\n

“I ended up speaking to them off and on for the next couple of weeks and things got pretty serious when we were competing for some projects,” Miller said. “I was of course flattered by the offer. Jake and John were awesome. We enjoyed our conversations and decided to do an onsite to discuss things in more detail. They made an offer after our onsite and Chris and I decided to accept it.”

\n

In 10up’s announcement, Goldman said it “takes a special kind of chemistry and alignment for a deal like this to work.” The company’s acquisition of Lift is one of the biggest design-driven acquisitions in the WordPress ecosystem in awhile.

\n

“Adding more experience design expertise to our company DNA enhances our empathy and ability to collaborate with design partners in an era of interactive, responsive design where divisions between ‘design’ and ‘engineering’ have eroded,” Goldman said.

\n

Miller, who has worked with Wallace to build Lift into a top-notch design and user experience agency, said that securing design talent is a challenge in the industry. 10up adding a fellow competitor to its team is a stretegic move when design talent is in short supply.

\n

“I think it’s certainly hard to find quality talent that’s interested in a full time position,” Miller said. “There are some amazing designers out there but a lot of them are contractors/freelancers. 10up wanted to find a team that had a big focus on quality design and UX. It didn’t hurt that we were big on WordPress either.”

\n

Miller and Wallace founded Lift UX in 2009 and will be closing out a chapter of their entrepreneurial lives as the brand dissolves into 10up.

\n

“Basically we’ll fade into the 10up brand bringing along our team, portfolio, accolades, and ultimately our personality,” Miller said.

\n

Wallace said closing out this chapter is “definitely bittersweet,” but the team is excited to transition into 10up.

\n

“As a 6-7 person agency, we were all constantly being pulled in a million different directions,” Wallace said. “Joining 10up allows us to focus on our individual areas of specialization and excel in each. I love many aspects of entrepreneurship and small agency ownership but the idea of focusing on the success of the experience design team at 10up is something I am looking forward to.”

\n
\";s: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, 11 Jul 2017 22:02: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: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:31:\"Donncha: Thank you Translators!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://odd.blog/?p=89500320\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"https://odd.blog/2017/07/11/thank-you-translators/\";s: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:1384:\"

Well, well. WP Super Cache translations are coming along well. 100% of strings in the development version are translated into Canadian English and Romanian! (That might change over the next few days as I have a couple of UI changes in mind, sorry!)

\n

Other languages like Persian, Japanese, Spanish, Russian and Italian are roaring along and sometimes only need a handful of words or sentences translated to hit that magic 100% too. The next version of the plugin will grab translations from WordPress.org if they’re available which is awesome for users around the world. We’re still shipping translation files but I think the release after that may ship without and rely entirely on the up-to-date online translations.

\n

So, thank you so much to the translators. Code is nigh on useless if the user and developer don’t speak the same language and the interface is incomprehensible. WP Super Cache has lots of technical language which must be a pain to translate. Your work is invaluable!

\n

Mulțumesc! متشکرم! ありがとうございました!¡Gracias! Спасибо! Grazie! Hvala ti! 谢谢!Vielen Dank!

\n\n

Related Posts

\n

Source

\";s: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, 11 Jul 2017 10:44:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:90:\"WPTavern: Interview with WordCamp US 2017 Organizers Dustin Meza and Laura Byrne-Cristiano\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=72903&preview=true&preview_id=72903\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://wptavern.com/interview-with-wordcamp-us-2017-organizers-dustin-meza-and-laura-byrne-cristiano\";s: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:2252:\"

While at WordCamp Europe I had the opportunity to interview Dustin Meza, lead organizer of WordCamp US 2017, and Laura Byrne-Cristiano, who is part of the marketing team for the event. The two are members of a 20-person team of organizers who will welcome an estimated 2,500 attendees to Nashville in December.

\n

Although the maximum capacity of the Music City Center venue is much higher than what is required by WordCamp US, the organizers want to make judicious use of the event's resources to put on the best possible event for those who make the effort to attend.

\n

\"At the end of the day, it's going to be the right size for the event,\" Byrne-Cristiano said. \"You could say, 'Hey, we want 10,000 people, but that's not the right size for the event. The right size is probably somewhere between 2,000 and 2,500. The venue can do more than that, but I don't know that that's the main goal. Bigger isn't always better. Your main goal is the best event and quality for the people who are already there.\"

\n

Meza said he considers WordCamp US to be the premier event for North America and that it is there to represent the communities located in this area. He couldn't share the full details of the unique things they are working on, but organizers plan to display and exhibit more information about the the various WordPress communities throughout North America.

\n

In the interview below, Meza and Byrne-Cristiano share a little bit about why they believe Nashville was selected and how welcoming the city is for people from different cultures. 

\n

\"No matter where in the world you are coming from, there's a place for you at WordCamp US,\" Byrne-Cristiano said.

\n

\"This is, by far, the best technology community I have ever been apart of, seeing how much everyone involved embraces new people – to me that is the big reason why I got involved,\" Meza said. \"I want to give this community the best event that we possibly can.\"

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jul 2017 02: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:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:33;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"WPTavern: WPCampus 2017 Will Be Streamed Live for Free\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72896\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://wptavern.com/wpcampus-2017-will-be-streamed-live-for-free\";s: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:1020:\"

WPCampus, a conference focused on using WordPress in higher education, takes place this Friday and Saturday in Buffalo, NY. If you’re unable to attend the event, WPCampus will be live streaming the sessions for free.

\n

Visit the streaming page on July 14th and 15th where viewers can choose between three tracks of sessions to watch. Viewers can also hang out in the #discuss-wpc17 Slack channel to discuss sessions with other people.

\n

Organizers are encouraging viewers to have watch parties at WordPress meetups and campuses. Sessions will be recorded and made available online at the end of the event. The stream starts on Friday, July 14th at 9 AM Eastern.

\n
\";s: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, 10 Jul 2017 21:49: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:\"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: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:64:\"WPTavern: Episodes 271-280 of WordPress Weekly are Now Available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72884\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/episodes-271-280-of-wordpress-weekly-are-now-available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1011:\"

In the past two weeks, listeners have reported that recent episodes of WordPress Weekly are not available for download through Apple’s Podcasting app, Stitcher, and other applications.

\nPodcast Download Error\n

I use Vid2MP3 to convert YouTube videos into MP3 files. Starting with episode 271, there was an error in the conversion process. It was difficult to diagnose since the MP3 played fine in some browsers and applications but not in others.

\n

I have reconverted the affected episodes using a different service and uploaded the new files to the site. I confirmed that the episodes are accessible in Apple’s Podcasting application. If you still encounter a problem downloading these episodes, please leave a note in the comments along with which podcasting app you’re using. Thanks to all who reported the error and for listening to the show.

\n
\";s: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, 10 Jul 2017 20:19: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: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:131:\"WPTavern: Automattic Joins Amazon, GitHub, Mozilla, reddit, and Twitter in July 12 Protest Against FCC’s Attack on Net Neutrality\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72799\";s:7:\"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:135:\"https://wptavern.com/automattic-joins-amazon-github-mozilla-reddit-and-twitter-in-july-12-protest-against-fccs-attack-on-net-neutrality\";s: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:3713:\"

\n

Major internet websites, companies, and organizations are banding together on Wednesday, July 12, to protest the FCC’s attack on net neutrality. These include Amazon, GitHub, Kickstarter, Vimeo, reddit, Mozilla, Twitter, Etsy, Spotify, Netflix, and many others. Automattic is joining these tech companies in the protest, as it has several times in the past, including the Internet Slowdown event in September 2014. The company also reaffirmed its commitment to net neutrality in 2015 by filing an amicus brief with the Court of Appeals for the DC Circuit in the case of United States Telecom Assn. v. FCC, joined by Medium, Reddit, Squarespace, Twitter, and Yelp.

\n

Net neutrality is the principle that ensures people can communicate freely online by prohibiting Internet Service Providers (ISPs) and government entities from favoring, blocking, or throttling certain websites, or charging fees for premium content delivery. It guarantees individuals have free to access all content and applications, and forbids ISPs from discriminating against or prioritizing certain users, equipment, or types of content. Vimeo created a handy video to illustrate the importance of defending net neutrality:

\n
\n

Net neutrality is once again under attack as the FCC is planning to remove the Title II (common carrier) protections established during the Obama administration.

\n

How to Join the Protest

\n

Self-hosted WordPress site owners who want to participate in the Internet-Wide Day of Action to Save Net Neutrality on July 12 can do so by installing the Internet Defense League Cat Signal plugin or the Fight for the Future Alerts plugin. Both support the upcoming Save Net Neutrality event and are based on the official Fight for the Future widget for the campaign.

\n

The widget will not display until July 12, so you can add a plugin ahead of time. If you want to test it to see what it will look like on the day of action, you can append #ALWAYS_SHOW_BFTN_WIDGET to your site URL after installing one of the plugins. See an example here: https://wptavern.com/#ALWAYS_SHOW_BFTN_WIDGET

\n

\n

The alert urges visitors to contact Congress and the FCC through the provided form. It can be displayed as a banner at the top of the page or as a modal (see example above).

\n

Automattic may also be planning a way for WordPress.com users to opt-in to participate. We’ll update the post if that information becomes available.

\n

Update: Automattic has since created a Net Neutrality plugin for WordPress.com and self-hosted users who want to join the protest.

\n
\";s: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, 10 Jul 2017 18:12:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:114:\"WPTavern: Let’s Encrypt Passes 100 Million Certificates Issued, Will Offer Wildcard Certificates in January 2018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72805\";s:7:\"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:\"https://wptavern.com/lets-encrypt-passes-100-million-certificates-issued-will-offer-wildcard-certificates-in-january-2018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2660:\"photo credit: Chris Anderson\n

Let’s Encrypt, the free and open certificate authority that launched in 2016, has issued more than 100 million certificates as of June 2017 and is currently securing 47 million domains. Earlier this year, the web passed a major milestone of getting more than 50% of traffic encrypted. Let’s Encrypt has been a major contributor to that percentage growing to nearly 58%.

\n

“When Let’s Encrypt’s service first became available, less than 40% of page loads on the Web used HTTPS,” ISRG Executive Director Josh Aas said. “It took the Web 20 years to get to that point. In the 19 months since we launched, encrypted page loads have gone up by 18%, to nearly 58%. That’s an incredible rate of change for the Web.”

\n

Aas also announced that wildcard certificates are coming to Let’s Encrypt in 2018. Wildcard certificates allow a site to secure an unlimited number of subdomains with the same certificate.

\n

Currently, the process to get Let’s Encrypt working on a WordPress multisite installation is much more complicated than adding a certificate for a single domain. The WP Encrypt plugin claims multisite and multi-network compatibility but super admins have often run into failure on networks with higher numbers of sites. Wildcard support for Let’s Encrypt will provide a better way to secure multisite networks.

\n

Let’s Encrypt will offer the wildcard certificates via the new ACME v2 API endpoint and will start by supporting base domain validation via DNS with the possibility of adding other validation options in the future. ACME is the protocol that Let’s Encrypt developed to allow subscribers to acquire and manage certificates. Those using the v1 endpoint are encouraged to move to v2 as soon as it’s available in January 2018. The v2 protocol was developed to be an IETF (Internet Engineering Task Force) standard so that ACME can work with more certificate authorities in the future.

\n
\";s: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, 07 Jul 2017 18:32: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:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:37;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"WPTavern: WangGuard Plugin Author Shuts Down Splog Hunting Service Due to Trauma and Death Threats\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72733\";s:7:\"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:\"https://wptavern.com/wangguard-plugin-author-shuts-down-splog-hunting-service-due-to-trauma-and-death-threats\";s: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:6853:\"

\n

After seven years of developing and supporting the WangGuard/SplogHunter service, José Conti has shut down the server permanently due to the stress and trauma associated with maintaining it. Conti is a WordPress plugin developer and consultant, and a member of the WordPress España translation team. His WangGuard plugin identifies and blocks sploggers, unwanted users, and untrusted users on WordPress, Multisite, BuddyPress, bbPress, and WooCommerce sites. It is currently active on more than 10,000 sites.

\n

Speculation about why the service shut down was running rampant after Conti had collected donations via an Indiegogo campaign in October 2016 to fund support and server costs. Since that time SiteGround stepped in to sponsor WangGuard, eliminating the server costs. The only costs that remained were Conti’s time and effort that he put into supporting the plugin.

\n

“My purpose with WangGuard was never money,” Conti said in his post explaining the reason for the shut-down. “I could have made WangGuard a paid plugin at anytime, and actually had a plan for that for years. But I didn’t do it because there is something inside me that would never let that happen. It was never, I repeat, never my plan to get rich with WangGuard, and I assure you that I could have done it easily: simply charging each of my users 24€/year, would have meant an income of more than 2 million euros per year. I just had to distribute a version of WangGuard I had collecting dust, with a checkbox on WangGuard’s server administration options but I never got it done. No matter the other reasons, which only people very close to me know: I simply didn’t want to, nor did I want to be a millionaire.”

\n

Mafia Death Threats and Trauma from Exposure to the Dark Web: The High Cost of WangGuard’s 99.9% Accurate Detection of Splogs

\n

WangGuard has long been known for its nearly perfect detection of registration spam. Not only did it completely block unwanted users, it also removed them from the database. The plugin was unrivaled in both accuracy and price – all users got everything the service offered for free. In order for WangGuard to provide its 99.90% accuracy, Conti bolstered the algorithm with manual curation and reviews.

\n

“WangGuard worked in two different ways: as an algorithm that I had been refining for seven years, and which was getting better as the sploggers evolved, so that it was always one step ahead of them, and also as human curation, in which I reviewed many factors, among them sites of sploggers to see if their content could improve the algorithm and make sure that it worked correctly both when it was blocking or not blocking a site,” Conti said. “The great secret of WangGuard was this second part. Without it WangGuard would not ever have become what it was.”

\n

Because of how effective WangGuard was at stopping unwanted users, Conti said for four years he received “almost daily death threats from mafias for making them lose millions of dollars.”

\n

Through the process of manually curating splogger sites, Conti caught a glimpse of the some of the darkest places on the web, which he said had a damaging psychological impact on him.

\n

“For seven years, I have visited places where I saw pederasty, pictures, and videos of murders (by razor blades, by gutting live people, by beheadings, dismemberments, to name a few), real videos of rape of all kinds (children, women, boys), photos of accidents in which people were totally disfigured, bizarre actions that I did not even know existed, and a very long ‘and so on,’ which I do not want to expand on,” Conti said.

\n

The effects of viewing these types of websites every day took their toll and Conti decided to close the splog hunter service.

\n

“Finally, a few months ago, I broke down,” Conti said. “I disappeared from everywhere and fell into a depression. The seven years of working at WangGuard finally took a toll on me. I had nightmares because of all the macabre deaths I had seen, an obsession with protecting my children from pederasty, OCD, depression, and many other symptoms. It took me about 6 months to recover (and honestly, I may be deceiving myself, since I do not think I completely recovered my life).”

\n

I asked Conti if clicking through to the websites was necessary for maintaining the service. He explained that while WangGuard blocked emails, domains, IPs, and ISPs, without his manual curation of visiting the domains and clicking the links, users could get a lot of “sleepers” – registered and active accounts that remain silent until one day with a 0day vulnerability or a bug fix, they attack thousands of websites. The sleepers also wait to perform actions like create millions of sites on thousands of WordPress multisite installations in order to create a lot of bad content/links.

\n

“Visiting many domains, I was able to minimize this problem,” Conti said. “The way I worked not only fixed the current spam / splog problem, but the wizard and database also fixed any future problems with sleepers.”

\n

Another reason he visited the domains was to figure out what he needed to block, whether it was an email or a domain. The domain could be a spam domain or possibly a free email service.

\n

“By visiting a website, I could detect whether it was a phishing website or a site camouflaged as an email service in order to try to cheat WangGuard,” he said. “I saw a lot of ‘techniques’ for trying to cheat WangGuard at Black Hat specialized forums. I had been subscribed to many spam/sploggers forums for investigation. Every time that a user described a real technique for cheating WangGuard, it was fixed immediately.”

\n

If you’re still using the WangGuard plugin, it may continue to work but not nearly as well as in the past. Conti said that some parts of the code work without the API, but the most important parts require the WangGuard/SplogHunter server. The plugin is open source, so anyone can fork it. An English translation of his original post is available on the WordPress.org plugin forums.

\n
\";s: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, 07 Jul 2017 00:36:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"WPTavern: WordSesh Asia Now in Planning for 2018, WordCamp Asia Targeted for 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72742\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"https://wptavern.com/wordsesh-asia-now-in-planning-for-2018-wordcamp-asia-targeted-for-2019\";s: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:4161:\"photo credit: Sakin Shrestha\n

Yesterday Sakin Shrestha announced that WordCamp Asia is now in the preliminary planning stages. Shrestha is a key reviewer on the Theme Review Team, translates WordPress to Nepali, and organizes meetups and WordCamps in Nepal. He and other members of the WordPress community in Asia, including representatives from India, Japan, Indonesia, Thailand, Sri Lanka, Singapore, and Nepal, had the opportunity to meet at WordCamp Europe.

\n

“We have been talking about WordCamp Asia informally when some of us attended WordCamp US for the first time,” Shrestha said. “That’s was in 2015, where I met Naoko Takano. She is the one with the main idea as the Japanese WordPress community was already doing well. Then we started meeting more people from Asia at WordCamp Europe 2016 and had an informal meeting there.”

\n

After this meeting, Rahul Bansal created a Facebook group for WordPress Community Organizers in Asia to support each other in a more coordinated effort. The first formal meeting happened at WordCamp Europe 2017 where the team decided that trying for WordCamp Asia in 2018 would be too soon. Instead, they are planning to host a WordSesh Asia event in 2018 to work on their coordination and teamwork. The team is working towards hosting WordCamp Asia in 2019.

\n

Organizers Consider Bangkok as a Possible Location for WordCamp Asia in 2019

\n

Shrestha’s post identifies several challenges that are unique to hosting a large scale WordCamp in Asia, including the need for visas even for travel within Asia, political instability, and numerous currencies and languages in use.

\n

“WordCamp Asia is really important for the WordPress community in Asia,” Shrestha said. “I am fortunate enough to attend WCUS and WCEU, which are some of the biggest WordCamps where we get to meet lot of WordPressers, share and exchange ideas, contribute to WordPress, start a new business, and think outside of the box. But for most of Asians, it’s really difficult to go that far and also it’s expensive to attain those. So, we are limited to WordCamps in our own country and neighboring ones. That is why we are thinking about WordCamp Asia in Bangkok, which will be really inclusive as it’s in the center part of Asia and it’s cheaper to go there and less time consuming for all.”

\n

Shrestha also feels strongly about providing travel assistance for those with financial hardships, as the most expensive aspect of attending a WordCamp is usually the travel and accommodation.

\n

“WordCamps are not just for the rich,” Shrestha said. “The primary motive of WordCamps is to grow the local community. So, WordCamp Asia’s mission will be to influence the community of WordPress Asia and help it to grow. That is why, instead of planning for a grand and pompous event, we need to make sure it is affordable and reachable to people of all financial backgrounds.”

\n

Shrestha said he has seen major changes in working with the WordPress community in Nepal from 2012 – 2017, which he attributes to having a stronger local presence with the WordCamp. India has also benefited from hosting WordCamps and has approximately nine happening in various cities. They are working towards hosting a WordCamp India in the future. There are also emerging communities in Singapore, Thailand, Indonesia, Sri Lanka, Cambodia, and Vietnam.

\n

“It’s time for pursuing WordCamp Asia,” Shrestha said. “We really have good talents here in Asia but we lack exposure. WordCamp Asia can create buzz and make more people aware, inspire, and provide opportunity.”

\n
\";s: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, 06 Jul 2017 18:10:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:63:\"WPTavern: Jesse Petersen, Founder of Genesis The.me Passes Away\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72772\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wptavern.com/jesse-petersen-founder-of-genesis-the-me-passes-away\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8085:\"Petersen Family\n

Jesse Petersen, founder of Genesis The.me and Petersen Media Group, has passed away at the age of 38. Petersen had been battling Cystic Fibrosis for the past several years and suffered a massive lung bleed earlier today. He passed out before paramedics could reach him and could not be revived at the emergency room.

\n

Petersen was on a double-lung transplant list with a lung allocation score of 38.859. The LAS is a score used to prioritize waiting list candidates based on a combination of wait list urgency and post-transplant survival. Last month, Petersen received the phone call he had been waiting for.

\n
\n

I got the call! Getting ready to leave to go to the hospital for testing and waiting.#NewLungsForJesse pic.twitter.com/hCCJik05MY

\n

— Jesse Ⓦ Petersen (@jpetersen) June 9, 2017

\n

\n

Unfortunately, the lungs were determined not to be in a suitable condition for transplant.

\n
\n

No go. He didn\'t like the look of the lungs. \"?\" No new lungs for Jesse today. Maybe tonight the phone will ring again.

\n

— Jesse Ⓦ Petersen (@jpetersen) June 9, 2017

\n

\n

He shared his experience in a raw, emotional post that describes the highs and lows he felt that day. “While the day was an emotional roller coaster, with the highs being WAY up there, the lows were surprisingly mild,” Petersen said. “They just weren’t the right lungs, and this protected me from years of issues, so it’s all good. The call for the perfect lungs for me will come in God’s timing. I am content to wait.”

\n

On July 2nd, a patient with a higher LAS score than Petersen’s was taken into surgery to receive a double-lung transplant. This made Petersen the highest priority pending a match was found but a match wasn’t found in time.

\n
\n

She was taken into surgery at noon, Tampa time. Surgery is 6-12 hours. I\'m very happy for her because her need was more than twice mine.

\n

— Jesse Ⓦ Petersen (@jpetersen) July 2, 2017

\n

\n

I did not have the opportunity to meet him in person. From those who knew him personally, Petersen was a great husband, father, and a caring individual who despite his medical situation, would help out the best way he could. There are two stories that highlight the kind of person he was. The first is a Twitter thread he published two days ago.

\n

When you meet a 5 year-old who needs a heart and double-lung transplant but has been turned down everywhere, your situation doesn’t seem so bad. That family doesn’t care about politics, social class, keeping up with the Joneses, or whether their clothes match. They are enjoying life.

\n

Because when it comes down to it, all we really need is to know our worth and love everyone else because they have equal worth. That doesn’t mean you have to agree with everyone, but you don’t have to seek out opposition or turmoil. Random acts of kindness rock.

\n

Can you look over your life and say you’d be leaving those connected to you better off having known you? If not, start today.

\n

The second is from his Facebook account about an encounter he had with a mother pushing her small boy in a wheelchair with a surgical mask on.

\n

I finally got out of the house to go do a God & Country service followed by fireworks. While waiting to go outside, a mom I’d seen pushing a small boy in a wheelchair with a surgical mask and oxygen on him came over to me.

\n

‘I just wanted to say how cool I think your double tank cart is. I’m going to call my supplier tomorrow to get one for our wheelchair.’

\n

We started talking (most unlike me) and she said her son needed a heart and a double lung transplant… but they’ve been turned down everywhere, starting with the very forgiving Pittsburgh center.

\n

‘I’m so sorry.’

\n

[nodded her head with a pained look] ‘We’re just making the most of our time now.’

\n

My heart broke. I’ve already lived 7 of his lifetimes. I’ve played sports, graduated from college, stood on the equator, married my best friend, and have two healthy boys.

\n

So kick me the next time I complain about my wait, OK?

\n

Members of the WordPress community are using social media to share memories, grieve, and pass along condolences to his family.

\n
\n

I first met @jpetersen at #wcorl and was honored to have him at #wcmia 2015. Hope it’s ok to share his “speaker card” from @wordcampmiami. pic.twitter.com/R7czM5AV1h

\n

— David Bisset (@dimensionmedia) July 5, 2017

\n

\n
\n

RIP @jpetersen, you were a great friend, and co-host. Gonna miss the great convos we had.

\n

— The WP Crowd (@thewpcrowd) July 5, 2017

\n

\n
\n

Met @jpetersen on multiple occasions. Family man and proud dad. Always respected the hell outta that. See you on the flip side, buddy.

\n

— Jared Atchison (@jaredatch) July 5, 2017

\n

\n
\n

Terrible news, @jpetersen will be missed. CF takes too many, too soon. Rest in peace, buddy.

\n

— Brian Krogsgard (@Krogsgard) July 5, 2017

\n

\n

Petersen’s family has created a crowd-funding campaign to help offset funeral and medical expenses. Since its creation, the community has donated more than $12K of $20K. If you are able, please consider donating as Petersen was the sole provider of income for his family.

\n

My deepest condolences go out to his friends and family. Petersen is survived by his wife and two sons.

\n

Related Reading:

\n

The Loss of One of Our Own

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jul 2017 02:09: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:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:40;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"WPTavern: WPWeekly Episode 280 – Behind the Scenes of Tuniversity\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=72768&preview=true&preview_id=72768\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/wpweekly-episode-280-behind-the-scenes-of-tuniversity\";s: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:2595:\"

In this episode, John James Jacoby and I are joined by Kiko Doran and Travis Totz, Senior Web Strategist at Modern Tribe. Doran helped create Tuniversity, a revolutionary new way of learning music through a highly interactive iBook.

\n

The project was so large, Doran outsourced some of the work to Modern Tribe, a web design and development firm. During the show, we learn the benefits of working with an agency you trust. Doran also explained what it was like to be a client as he’s normally fulfilling the agency role.

\n

Two major takeaways from the Tuniversity project include:

\n
    \n
  1. Work on things you’re passionate about with people who share the same passion.
  2. \n
  3. Approach problems with a positive mindset.
  4. \n
\n

Near the end of the show, we discussed the news that WangGuard is officially closed.

\n

Picks of the Week:

\n

WPHierarchy.com is a WordPress resource created by Rami Abraham in 2013. The site is an interactive version of Michelle Schulp’s colorful diagram of WordPress’ template hierarchy. Each template is linked to documentation that explains its function

\n

Dr. Russell A. Barkley (30 essential ideas everyone should know about ADHD)

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, July 12th 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #280:
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jul 2017 23:58:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:105:\"WPTavern: Nadia Eghbal and Mikeal Rogers Join a16z Podcast to Discuss the Changing Culture of Open Source\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72702\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://wptavern.com/nadia-eghbal-and-mikeal-rogers-join-a16z-podcast-to-discuss-the-changing-culture-of-open-source\";s: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:6242:\"photo credit: 16th st(license)\n

Nadia Eghbal and Mikeal Rogers recently joined Sonal Chokshi for an episode of the a16z Podcast to discuss the changing culture of open source. Eghbal works in community programs at GitHub to better support people doing open source work. Rogers is the community manager at the Node.js Foundation. The episode focuses on the human aspect of the world of open source software and what inspires people to work together to give software away for free.

\n

Through Eghbal’s research on sustaining open source communities, she found, as Rogers succinctly summarized on the show: “There’s no connection between the number of users and the number of people maintaining a project.” The Heartbleed Bug, which arrested public attention when it was disclosed in 2014, is perhaps one of the most critical examples of an open source project with a global user base and a grossly disproportionate number of maintainers.

\n

As part of her research at GitHub, Eghbal is working on creating a vocabulary to explain things that are happening with open source projects. One example is the distinction between “popular” versus “healthy” when describing projects in terms of the communities behind them, governance, quality of maintainership, and other factors that influence a project’s condition.

\n

“Because the dialogue tends to be set by popular projects, and those developers and their problems tend to dominate the story about this, you have these words and vocabulary like ‘drive-by-contributions,\'” Rogers said. This often implies that maintainers are too busy to look at the code. Rogers advocated for changing this perception of “drive-by-contributors” to view them as casual contributors, people who show up and have value to add. If maintainers can seize these contributions as an opportunity, they will have a better chance of leveling up contributors to be a more active part of their organization.

\n

The group also discussed how technology has caused a cultural shift among open source communities from the old world versus the new world of open source.

\n

“In older open source, part of the barrier to entry that people went through before they were ever identifiable to any contributor was an acclimation to the culture and an acclimation to the tool chain and all this stuff,” Rogers said. “One of the things that GitHub has done is completely remove all of that cultural acclimation. There is one tool chain that you use to contribute to any project and when you show up you don’t have all of this cultural knowledge. You haven’t bought into any of these ideals about open source necessarily. You’re just there to contribute. We actually need to work with that.”

\n

In the past, contributors informally acclimated to the culture through the onboarding process, and most software projects were more self-contained.

\n

“Where that becomes awkward today is that so many different pieces of software depend on other open source projects, which wasn’t actually true 10 or 20 year ago,” Eghbal said. With so many projects fitting into others as dependencies, it becomes more difficult to actually remove a project from the public domain. Open source licensing ensures that these projects have a life of their own. This has democratized entrepreneurship, making it easy for people to piece together technology to build applications and businesses. It also requires a higher level of skills for people working together across various open source projects and cultures.

\n

Eghbal and Rogers discussed the qualities of a healthy open source community, such as how welcoming the project is and how contributors speak to each other and resolve conflict. The ability to successfully resolve conflict can make the difference between a healthy growth of contributors or attrition on a project. Rogers mentioned a related conversation they had with Karl Fogel on their Request for Commits podcast concerning conflict within projects.

\n

“When we were talking to Karl, he has this view that ‘As long as a it has an open source license, it doesn’t matter how dysfunctional the project is, because we as a community always have this ability to fork it,\'” Rogers said. “I didn’t agree with him on this, because the practical reality of forking a project is such a huge overhaul and you don’t necessarily have the right people to do it in your particular time. What you actually want are the healthy communities with healthy practices, what you want is to keep them going.”

\n

Another open source predicament they discussed, which is fairly common in the WordPress ecosystem, is when a company releases a project as open source or “gifts it to the community.” Eghbal likened this to “sending your dog away to a farm upstate.”

\n

“We’re really excited to announce this is now open source, meaning we don’t want to take care of it anymore,” she said. “‘We’ll give it to the community,’ (except they haven’t actually identified anyone in the community who wants to take care of it.)” This type of situation shows how “giving back to the community” isn’t always what it appears to be for those who end up using these projects that have been released into the wild.

\n

The group also discussed how the incentives for people to contribute to open source have changed over the years and why “the GitHub generation” has more readily adopted the MIT license. Check out the full podcast episode below:

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jul 2017 19:26: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: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:84:\"HeroPress: How I tried, applied, got involved. Realizing one of my childhood dreams.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=1950\";s:7:\"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:188:\"https://heropress.com/essays/tried-applied-got-involved-realizing-one-childhood-dreams/?utm_source=rss&utm_medium=rss&utm_campaign=tried-applied-got-involved-realizing-one-childhood-dreams\";s: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:15809:\"\"Pull

When you’re born in an island, you usually grow up thinking about all the marvelous things awaiting for you on the other side of the sea. I was born in Sardinia, an island in the middle of the Mediterranean Sea, and as a child I dreamt about becoming an air hostess.

\n

I wanted to travel the world and speak tons of foreign languages, to be able to communicate with local people everywhere I’d go.

\n

But people kept telling me that I wasn’t going to become tall enough for that job (genetics don’t lie!), and I eventually listened to them. I ended up choosing a different path in life, following the Italian mantra: “You have to study something that will guarantee a stable and secure job for life”.

\n

Even if I wasn’t that much convinced about the perspective of having the same job for all my life, as my parents did, at the same time I didn’t want to get stuck in the island forever: the unemployment rate in Sardinia is unfortunately really high and I didn’t want to risk to be part of that percentage.

\n

Crossing the borders of the island

\n

So I chose the Faculty of Economics and did my best to cross the borders of my island as soon as I had the chance: this happened when I was 22 and I moved to Siena, Tuscany, to finish my studies. That is also the time when I opened my first personal blog on an Italian platform named Tiscali, which I later migrated to WordPress.com.

\n

I’ve always loved writing, and since I was a little girl I used to spend hours in my room writing stories and poems. I was doing the same with the blog but with the advantage of reaching a much larger public, virtually meeting many people and getting inspired by their stories.

\n

After 2 years in Tuscany I moved to Strasbourg, France. There I learnt French and did several little jobs, but I found my first important one in Milan, the big city shining with job opportunities for everyone —as Italians love to say.

\n

There I was, fulfilling the dream of many young people of my age (and their families): I was 25, with an average-paid 40 hours/week office job in the marketing department of a big international company, and I was surrounded by ambitious colleagues and a boss constantly asking for extra —and free— working hours per day.

\n

I was feeling like a parrot inside a golden cage.

\n

It seemed to me I wasn’t going anywhere. I also gave up blogging because I wasn’t feeling inspired enough to write. People constantly repeated to me that I was super lucky to have a permanent contract and work in a marketing department; in their eyes I was all set for life, so —using some strange equation — I also had to be happy!

\n

Of course I was luckier than many of my peers, but I kept asking myself if I really wanted to do that life forever.
\nDid I really want to keep on working 10 hours per day under the neon lights of an office, annihilate my dreams and live waiting for the free time of the weekend?

\n

The most vivid memory I have of that period is the overwhelming feeling clenching my throat on Sunday afternoons, when I started to dread the moment of coming back to the office the day after.

\n

Facing new challenges

\n

So I left and faced the change. At the beginning I gave myself the opportunity to test different office jobs. But the results were always the same: I kept feeling unsatisfied with my life, and I understood I had to respect my little girl’s dream and fly away from my golden cage.

\n

I opted for emigration and moved alone to Barcelona, Spain, in 2012.

\n

My first move was plunging myself into a few months of intense Spanish learning at the University, then I found a job in an international Assisted Reproduction Clinic.

\n

My job title was “Patient Coordinator” and I was assisting international patients coming to Barcelona for their treatments: I was their translator, interpreter and administrative consultant. Patients were from Italy, France, England, Morocco, Senegal…it was a Babylon of people with so many different backgrounds that I felt really inspired by some of their stories.
\nThis inspiration led me to start writing again: I dusted off my WordPress blog and filled it up with stories about my new life in Barcelona and some of the women I was meeting at the Clinic. I was feeling stronger and more independent than ever.

\n

The job at the Clinic lasted for 3 years. Even if it was really inspiring, it was also very stressful. Imagine being a 30-something woman speaking all day long about fertility problems with women struggling to have a baby.

\n

I realized I was getting too involved and decided to look around to see what I could do next.

\n

How can I find a job like this?

\n

It was summer 2015 and I was at my desk, in my little tiny apartment in front of Barcelona’s beach. I was writing in my blog and I got stuck in a technical problem. While I was searching through the WordPress.com documentation, I saw a pop-up in the bottom right corner of my screen: an Automattician wrote me to ask if I needed help. I gladly accepted her offer, we chatted for a few minutes, the problem was solved and I could go back to my writing. But I also left the chat with one question: how could that person on chat find a support job with WordPress?

\n

Curious as I am, I started looking for an answer and I stumbled upon the official WordPress job page: jobs.wordpress.net

\n

There I found a job offer that caught my attention: WP Media, a French startup, was looking for a polyglot and remote customer service teammate for one of their plugins, WP Rocket. I read their requirements: fluency in English, French and possibly another language, great experience with WordPress, some coding skills.

\n

That offer was calling me, I felt it.

\n

I knew I didn’t have all the requirements, but hey, I could speak 4 languages, and I had a WordPress blog…right? Of course, I didn’t know anything about PHP, I had always been a WordPress.com user until that moment and I didn’t really know how to manage a self-hosted website or use a cache plugin…but I felt I was ready to learn all that. And moreover, what did I have to lose?

\n

I wrote my most inspired cover letter and sent my CV.

\n

With my total surprise, they answered me the day after and we set up an interview by Skype. My main strengths were the fluency in 4 languages and my previous experience in customer service, so I was really confident about those skills; yet I wanted to be totally honest with them: yes, I had been using WordPress for a long time, and yes, I was digital savvy enough, but I knew very little on the technical side. I had always worked on the front end of websites, writing, blogging, learning by myself; I didn’t know anything about the backend of WordPress sites.

\n

Even so, they had faith in me and in a few days I had the confirmation: I was in! During the first days I felt so happy about this new major turning point in my life: not only had I found a job thanks to my primordial passion, speaking foreign languages, but for the first time in my life I could do that job from home or anywhere else I liked, instead of being caged in a formal office!

\n

I got introduced to my remote teammates and I instantly felt welcomed.

\n

Learning by doing

\n

But, very soon, that initial enthusiasm started to struggle with another intense feeling: the fear of exposing my inexperience.

\n

There were too many things I didn’t know!

\n

Working in a WordPress backend was so new to me that I started studying like crazy and reading everything I could about WordPress for beginners. I went through some really intense months of learning by doing, supported by my teammates. Like a baby who start crawling and then taking little steps, I was initially answering the easiest tickets from our customers. 
At the same my teammates were sending me useful material to read, setting up video-calls for 1to1 training, encouraging me every time they could.

\n

After a few days I received the first happy comments by the customers I was helping in their mother tongue: until that moment the plugin’s support had been offered only in English and French, so it was the first time Spanish and Italian customers were being answered in their own language…and they appreciated that!

\n

Even so, I can’t deny it, I was scared.

\n

It was so scary admitting my ignorance, exposing it in a remote environment where I couldn’t see my teammates reactions live.

\n

My first instinct was imagining the worst scenarios where they were secretly hating me for interrupting their work on Slack with my doubts.

\n

But I had no other choice than to keep asking questions and learn from their answers. Not doing so would have been much worse: silencing my voice would have slowed down my learning process.

\n

Why don’t you try to contribute to WordPress?

\n

We were at WordCamp Paris 2016 when one of my teammates showed me how the WordPress community worked together and kept in contact through Slack.

\n

“You speak multiple languages, why don’t you try to contribute to the polyglots team?” —he asked.

\n

That thought never crossed my mind before, I knew very little about contributing to WordPress. I had been working for WP Media for 6 months and, while I was enjoying my new job a lot, I was just slowly starting to abandon that overwhelming feeling of insecurity I mentioned above.

\n

I didn’t feel ready to dive into a new challenge and start also contributing to WordPress, I thought I didn’t have the ability to do that. I was wrong, obviously.

\n

Curiosity won on me another time and I joined the two Slack channels Making WordPress (where all the WP global community meets) and Italia WP Community. I lurked the channels for a few months, until I went to WordCamp Milan and met some members of the Italian Polyglots team.

\n

It was love at first string: Laura, one of the General Translation Editors (GTE) for Italy, taught me how to start contributing and translating following the polyglots guidelines. She also told me about the big effort the Italian community has been doing to work together, consistently, to boost WordPress related events in Italy and to grow up.

\n

I wanted to be an active part of it and I started contributing.

\n

Now I’m a Project Translator Editor for the Italian polyglots team and I mentor new contributors: I love it!

\n

Since the beginning of my journey into the WordPress world I traveled a lot, and also attended WordCamps in Paris, Vienna, Milan, Barcelona, Torino and Bilbao.

\n

Following my teammates encouragement, I also started applying to WordCamps as a speaker, because I felt my story could be important for other people looking for new inspiration for their working and personal life. I gave my first talk in my adoptive city, Barcelona, in December 2016, then in Torino in April 2017 and I recently had the honor to tell my story also from the stage of WordCamp Europe 2017.

\n

In a short glimpse of time I engaged in many activities related to WordPress which allowed me to meet very interesting and inspiring people from all over the world.

\n

I’m (not) lucky.

\n

People keep telling me that I’m lucky, and it’s true, I really am. But if I’m here, now, sharing my story (and thanks Topher for inviting me to write it!) is not because I live under a lucky star: I just used my previous skills and passions and adapted them to a new career and life path.

\n

We all have some skills; and if we don’t know which they are exactly, we should take some time to make a list of the things we’re really good at. With that in mind, just try. Apply. Get involved. Don’t get stuck in the feeling of “I can’t do it because I don’t know enough”.

\n

That is what I did: without even realizing it, I started putting into reality the dream of the little girl who was born in an island and wanted to travel and speak different languages.

\n

WordPress made this possible: I’m part of a big community, and I am proud of it.

\n

The post How I tried, applied, got involved. Realizing one of my childhood dreams. appeared first on HeroPress.

\";s: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, 05 Jul 2017 12:00:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Alice Orru\";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:102:\"WPTavern: WordCamp Europe 2017 Posts 24% No-Show Rate, Cites Early Ticket Sales and Expensive Location\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72644\";s:7:\"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:111:\"https://wptavern.com/wordcamp-europe-2017-posts-24-no-show-rate-cites-early-ticket-sales-and-expensive-location\";s: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:3872:\"photo credit: WP Tavern\n

WordCamp Europe 2017 organizers have posted attendance and budget data compiled after the conclusion of the event. Despite being promoted as “the largest WordPress event to this day” with more than 3,000 expected attendees, WCEU 2017 fell short with 1,900 people on the ground. Attendees were 5% fewer than last year’s 2,000 in Vienna. Expectations ran high but organizers could not predict the 24% no-show rate once the event got started. This is more than double the 10% no-show rate for the previous four years.

\n

The camp’s organizers do not have a simple explanation for the high no-show rate, but cite several factors, including a few dozen participants being denied visas, higher local sales, an expensive location, and putting tickets on sale too early. Approximately 60% of attendees were from nearby countries, such as France, Great Britain, Germany, Belgium, and the Netherlands.

\n

Ticket sales for 2017 were open immediately at the conclusion of the 2016 event in Vienna. Organizers found that tickets sold in the first six months had a 34% no-show rate as compared to 20% for those sold in 2017. As the event has often sold out in the past, prospective attendees may have felt pressure to purchase a ticket in advance without confirming the ability to attend.

\n

Posting increasingly higher attendance numbers isn’t one of the goals of the WordCamp, but planning accurately for the number of people who will attend is crucial for resource and budget planning. When one in four attendees is a no-show, the plans for food, swag, venue accommodations, and other aspects of the event are askew.

\n

Organizers did not mention Contributor Day attendance in the wrap-up report, but this may have been one of the most successful aspects of the event. It was held prior to the main conference days, which may explain the event’s unusually high attendance numbers. Organizers hosted 473 attendees for the 500 available contributors slots.

\n

WordCamp Europe 2017 Cost 300€ per Attendee, Sponsors Covered 80%

\n

WordCamp Europe’s wrap-up report also includes a transparent breakdown of the event’s 700k€ budget. Catering costs for lunches, snacks and drinks, made up 50% of the budget. However, organizers were limited to the venue’s catering partners, which blurs the line between actual food versus venue costs.

\n

The team was unable to sell all of the sponsorship packages and was forced to reduce the budget by 149k€ along the way. WordCamp Central subsidized 10€/ticket and covered the final deficit of 28k€. The cost breakdown per attendee was 300€ with sponsors covering 80%, WordCamp Central 7%, and tickets sales 13%. These numbers show that the 40€ ticket price is a small fraction of the total costs required for an event of this size.

\n

Organizers said they felt it was important to share the data for educational purposes but also to “demonstrate to everyone who might have a doubt, that maintaining the ticket fee very low is meant to make our events accessible to all, but that the fee is not an indicator of the value of the conference.”

\n
\";s: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, 03 Jul 2017 19:06:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:43:\"Dev Blog: The Month in WordPress: June 2017\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4865\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2017/07/the-month-in-wordpress-june-2017/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9049:\"

We’re starting a new regular feature on this blog today. We’d like to keep everyone up-to-date about the happenings all across the WordPress open source project and highlight how you can get involved, so we’ll be posting a roundup of all the major WordPress news at the end of every month.

\n

Aside from other general news, the three big events in June were the release of WordPress 4.8, WordCamp Europe 2017, and the WordPress Community Summit. Read on to hear more about these as well as other interesting stories from around the WordPress world.

\n
\n

WordPress 4.8

\n

On June 8, a week before the Community Summit and WordCamp Europe, WordPress 4.8 was released.You can read the Field Guide for a comprehensive overview of all the features of this release (the News and Events widget in the dashboard is one of the major highlights).

\n

Most people would either have their version auto-updated, or their hosts would have updated it for them. For the rest, the updates have gone smoothly with no major issues reported so far.

\n

This WordPress release saw contributions from 346 individuals; you can find their names in the announcement post. To get involved in building WordPress core, jump into the #core channel in the Making WordPress Slack group, and follow the Core team blog.

\n

WordCamp Europe 2017

\n

WordCamp Europe 2017 was held in Paris between June 15-17. The event began with a Contributor Day, followed by two days of talks and community goodness. The talks were live-streamed, but you can still catch all the recordings on WordPress.tv. The organisers also published a handy wrap-up of the event.

\n

WordCamp Europe exists to bring together the WordPress community from all over the continent, as well as to inspire local communities everywhere to get their own events going — to that end, the event was a great success, as a host of new meetup groups have popped up in the weeks following WordCamp Europe.

\n

The work that Contributor Day participants accomplished was both varied and valuable, covering all aspects of the WordPress project — have a look through the Make blogs for updates from each team.

\n

Finally, we also learned during the event that WordCamp Europe 2018 will be held in Belgrade, Serbia, continuing the tradition of exploring locations and communities across the continent.

\n

WordPress Community Summit

\n

The fourth WordPress Community Summit took place during the two days leading up to WordCamp Europe 2017. This event is an invite-only unconference where people from all over the WordPress community come together to discuss some of the more difficult issues in the community, as well as to make plans for the year ahead in each of the contribution teams.

\n

As the Summit is designed to be a safe space for all attendees, the notes from each discussion are in the process of being anonymized before we publish them on the Summit blog (so stay tuned – they’ll show up there over the next few weeks).

\n

You can already see the final list of topics that were proposed for the event here (although a few more were added during the course of the two day Summit).

\n

WordPress marketing push continues apace

\n

As part of the push to be more intentional in marketing WordPress (as per Matt Mullenweg’s 2016 State of the Word), the Marketing team has launched two significant drives to obtain more information about who uses WordPress and how that information can shape their outreach and messaging efforts.

\n

The team is looking for WordPress case studies and is asking users, agencies, and freelancers to take a WordPress usage survey. This will go a long way towards establishing a marketing base for WordPress as a platform and as a community — and many people in the community are looking forward to seeing this area develop further.

\n

To get involved in the WordPress Marketing team, you can visit their team blog.

\n

New Gutenberg editor available for testing

\n

For some time now, the Core team has been hard at work on a brand-new text editor for WordPress — this project has been dubbed “Gutenberg.” The project’s ultimate goal is to replace the existing TinyMCE editor, but for now it is in beta and available for public testing — you can download it here as a plugin and install it on any WordPress site.

\n

This feature is still in beta, so we don’t recommend using it on a production site. If you test it out, though, you’ll find that it is a wholly different experience to what you are used to in WordPress. It’s a more streamlined, altogether cleaner approach to the text-editing experience than we’ve had before, and something that many people are understandably excited about. Matt Mullenweg discussed the purpose of Gutenberg in more detail during his Q&A at WordCamp Europe.

\n

There are already a few reviews out from Brian Jackson at Kinsta, Aaron Jorbin, and Matt Cromwell (among many others). Keep in mind that the project is in constant evolution at this stage; when it eventually lands in WordPress core (probably in v5.0), it could look very different from its current iteration — that’s what makes this beta stage and user testing so important.

\n

To get involved with shaping the future of Gutenberg, please test it out, and join the #core-editor channel in the Making WordPress Slack group. You can also visit the project’s GitHub repository to report issues and contribute to the codebase.

\n
\n

Further reading:

\n\n

If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

\";s: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, 03 Jul 2017 11:42: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:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:97:\"WPTavern: Gutenberg Contributors Explore Adding Drag-and-Drop and Multi-Column Support for Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72638\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/gutenberg-contributors-explore-adding-drag-and-drop-and-multi-column-support-for-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6817:\"photo credit: ruudgreven DSC_0012(license)\n

The new Gutenberg editor has an open ticket for allowing users to sort blocks via drag and drop. Blocks can currently be sorted with up and down arrows located to the left of the content but the beta only allows for single-column stacking.

\n

One of the goals for Gutenberg is to provide “a page building experience that makes it easy to create rich post layouts.” As far as layout building goes, the first planned versions of the new editor are very primitive as compared to Wix and Weebly’s drag and drop website builders where nearly every element on the page can be easily moved to a different position.

\n

Contributors have been discussing the intricacies of adding this feature to Gutenberg since February. James Nylen summarized some of the challenges that make drag and drop more complicated to implement:

\n

Dragging and dropping a block is not really a one-step operation. It is more like 3:

\n
    \n
  1. Press and hold mouse button or screen
  2. \n
  3. Move to desired location
  4. \n
  5. Release
  6. \n
\n

Step 2 is incredibly difficult to get right, and requires a lot of complicated behaviors like duplicating an item (or at least its general shape and size), scroll handling, and determining the intended new location, especially at the beginning and end of the content. We have all used bad drag-and-drop experiences, and I would argue they are worse than not having it at all.

\n

That said, for two-dimensional movement with columns, I agree that arrows alone are probably not a good solution. Though mobile support for that is going to be very tricky no matter how it works.

\n

Several commenters on the ticket agree that repeatedly clicking arrows to move blocks is cumbersome and will become untenable in the future when multi-column support is added. This would require up, down, right, and left arrows to rearrange content. Users have come to expect a drag-and-drop interface, because nearly every page builder application offers it.

\n

“We are thinking of drag and drop as a progressive enhancement for desktops,” Joen Asmussen said. “One that would be great to have, but we should build it after we have explicit button actions in place for doing the same, including splitting into columns in the future. This decision is based on a desire to ensure accessibility as well as mobile devices can play the same game.”

\n

Asmussen marked the ticket priority as low in May and removed it from the beta milestone. At this point, users are not likely to see drag and drop in the first release that ships with WordPress core.

\n

Multi-Column Layouts Planned for Gutenberg V2

\n

The discussion surrounding adding drag-and-drop to the editor naturally leads into adding multi-column support. Limiting users to a single column is a one-dimensional approach to designing pages, but contributors don’t plan to leave Gutenberg without multi-column support for long.

\n

Geoarge Olaru, a designer at PixelGrade, shared a prototype for adding a simple two or three-grid column layout to Gutenberg.

\n

“Extending WordPress further from the default Blog Posts automatically implies the need of multi-column layouts for presentation pages,” Olaru said. “I would prefer to tackle this feature upfront, rather than letting every developer do it on his own (see the multitude of page builders plugins).”

\n

\n

“For the V1 editor, I’m afraid columns like this is out of scope,” Asmussen said in reply to a Olaru’s ticket with mockups and a prototype for multi-column support. “That’s not a ‘no’ — rather, we need some technical foundations to be solid first, before we commit to the really interesting stuff. But it might be a V1.1, or at the very least something for the customization folks later on in the year. Even before that, it would be good to keep this UI in mind, so that perhaps a plugin can add this even earlier.”

\n

Other commenters on the ticket feel more urgency about getting multi-column support into the first version of the editor. One of the concerns is that plugin developers will rush to add columns immediately based on demands from users, who will then have to migrate once core adds support.

\n

“Multi column layouts are a must-have,” Anthony Hortin commented on the ticket. “At the moment, Gutenberg isn’t solving any issue. You still end up with one long column of content. The whole reason page builders are so popular, and why hundreds of thousands of people are using them, is because they provide the ability to easily make multi-column layouts. Without this functionality, you’re not providing any reason to use Gutenberg over a page builder plugin.”

\n

One of the main challenges of adding multi-column support is figuring out what type of grid system to use and making sure that it scales from mobile to desktop. Weston Ruter joined the discussion to say that the foundational work for nested block support is being done now in version 1, but the UI for displaying them hasn’t been implemented yet.

\n

“I appreciate the excitement and urgency to wanting columns,” Asmussen said. “We feel the same urgency. It’s not about not wanting columns, it’s purely about managing resources at this point.”

\n

The good news is if you’ve been testing Gutenberg and wondering where some of these features are on the roadmap, they will be coming in later versions. While there may be disagreements about how much of a priority drag-and-drop and multi-column support should have for version 1, contributors agree that laying a solid technical foundation for these features is crucial for future extensibility.

\n
\";s: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, 01 Jul 2017 19:06:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:116:\"WPTavern: Gutenberg 0.3.0 Adds Front-End Styles for Core Blocks, Notices Framework, and Text and Image Quick Inserts\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72646\";s:7:\"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:125:\"https://wptavern.com/gutenberg-0-3-0-adds-front-end-styles-for-core-blocks-notices-framework-and-text-and-image-quick-inserts\";s: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:4557:\"

Gutenberg development is marching ahead with version 0.3.0 released today. New releases are shipping out on a weekly basis, so testers will get to discover another round of new additions after updating to the latest. The changelog has a full list of the 50 additions and improvements included in this release, but here’s a quick visual tour of a few of the most interesting user-facing features added this week.

\n

Gutenberg developers have added front-end styles for core blocks, which means that content like cover images will now appear the same as they look in the admin in the editor. The demo content in the plugin has also been updated to display a full-width cover image. Below is an example of a standard width cover image on the front-end.

\n

\n

Version 0.3.0 also includes new text and image quick inserts, which appear when hovering over the blank space beneath the post content. This makes it faster to add the types of content that are used most frequently.

\n

\n

This release adds a framework for notices, which provides developers with reusable notices components, showing how to trigger notices and where they will show up. Gutenberg now displays notices on post save, schedule, and update.

\n

\n

Version 0.3.0 adds a new block descriptions component to blocks with inspector controls. Several of the core blocks now display descriptions. These will be especially useful when plugin developers begin adding their own custom blocks, offering users a quick way to see the purpose of the block.

\n

\n

This release adds more placeholder text to various blocks, as “placeholders are key,” according to the newly added design blueprints and principles included in Gutenberg’s documentation:

\n

If your block can have a neutral placeholder state, it should. An image placeholder block shows a button to open the media library, a text placeholder block shows a writing prompt. By embracing placeholders we can predefine editable layouts, so all you have to do is fill out the blanks.

\n

Version 0.3.0 also adds several enhancements that make it easier to edit and customize the image-oriented blocks with more options and settings:

\n\n

Active installs for the Gutenberg plugin have nearly doubled since last week and are at more than 900 sites. This is roughly 1% of the goal Matt Mullenweg set for testing on 100,000 sites before replacing the edit screen. The plugin may also be advertised in the dashboard in a future release, possibly 4.8.1, which is slated for the end of July.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 30 Jun 2017 22:07:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:76:\"WPTavern: Popular WordPress Plugins Slow to Add Meta Box Support for Calypso\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=71527\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/popular-wordpress-plugins-slow-to-add-meta-box-support-for-calypso\";s: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:3361:\"

During the State of the Word at WordCamp US 2016, Matt Mullenweg announced that Calypso was plugin aware. Calypso is a REST API and React powered application for the desktop created by Automattic in 2015.

\n

Developers with plugins active on 1M sites or more received an email invitation from Andy Peatling to begin building support for Calypso.

\n

“Calypso is now plugin-aware,” Mullenweg said. “This pull request was merged today, and as a way to bootstrap this, we’re opening up for what I just described for plugins to create Calypso interfaces for what they’re doing.

\n

“Basically saying, if you’re using Calypso on a site that has one of these plugins, let’s say WooCommerce, all of a sudden in the interface, there will be all the WooCommerce stuff. It’ll talk to the API, it will run on the desktop just like the rest of Calypso, and it will only be loaded if the plugin is active.”

\n

One of the major differences between Calypso and WP-Admin is that custom meta boxes added by plugins are not accessible in Calypso.

\n

Nearly seven months since the announcement, popular WordPress plugins have struggled to add meta box support, including those maintained by Automattic. WordPress SEO, active on more than 3M sites, is among the plugins that were selected to take part in the experiment.

\n

When asked about the progress of making WordPress SEO Calypso aware, Joost de Valk, founder of Yoast.com, declined to comment.

\n

Automattic has seen little progress on the initiative, “No news to report at this time, but hope to have some soon,” Automattic representative Mark Armstrong said. WooCommerce has yet to add meta box support and settings pages in Calypso.

\n

Gutenberg, WordPress’ new editor, is also built using React. One of the chief concerns expressed by users and developers is how it will support custom meta boxes built using the current PHP framework.

\n

“I miss a lot of the meta boxes I’m used to seeing on the screen,” Aaron Jorbin said. “Things like Yoast SEO (on some sites) and custom taxonomies are just not shown. If every meta box ever made for WordPress needs to be remade, it sure is going to make developers lives a living hell.”

\n

I want to use Calypso as a replacement for WP-Admin because it’s fast and I like the interface. However, I can’t do that until it supports meta boxes for the plugins I rely on, such as Edit Flow. Is the lack of custom meta box support for Calypso a sign of what’s to come with Gutenberg?

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 30 Jun 2017 20:05: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: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:50:\"WPTavern: WordCamp Netherlands Reinstated for 2018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72624\";s:7:\"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:\"https://wptavern.com/wordcamp-netherlands-reinstated-for-2018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1924:\"

At WordCamp Europe I had the opportunity to speak with WordCamp Netherlands organizers Marcel Bootsman and Luc Princen, along with WordPress Global Community Team members Josepha Haden and Andrea Middleton. The group has had several conversations about the future of WordCamp Netherlands, which was shut down earlier this year in favor of city-based WordCamps, and have decided to reinstate the camp with a few conditions.

\n

WordCamp Netherlands organizers are now allowed to begin planning the event again based on the requirement that the country host three city-based WordCamps first. There are currently two local camps on the schedule and a few others in the pre-planning stage. Lead organizer Marcel Bootsman is aiming to have 500 attendees for the next WordCamp Netherlands in 2018.

\n

In a recent interview with Torque, Matt Mullenweg indicated that the outlook is good for future regional WordCamps.

\n

“I think we got to the point where we were too rules-based and now we’re starting to open up the process and be more agile in the approach to WordCamps,” Mullenweg said. “We can start to think about regional WordCamps and topic-focused WordCamp…we want to think about which WordCamps make sense to move the community forward.”

\n

In our interview below, WordPress Global Community Team members said they plan to take similar country-based WordCamp proposals on a case-by-case basis. WordCamp Netherlands is pioneering the way for other countries with active local communities to continue to push the boundaries of the previously “one-size-fits-all” approach to WordPress events.

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 29 Jun 2017 19:18: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: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:82:\"WPTavern: WPWeekly Episode 279 – The Future of Underscores with David A. Kennedy\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=72616&preview=true&preview_id=72616\";s:7:\"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:\"https://wptavern.com/wpweekly-episode-279-the-future-of-underscores-with-david-a-kennedy\";s: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:2442:\"

In this episode, John James Jacoby and I are joined by David A. Kennedy. Kennedy is a Theminator at Automattic and an accessibility advocate. Kennedy joined us to talk about the future of Underscores, a starter theme created by Automattic in 2012.

\n

We discussed how Gutenberg may impact theme development in general and some of the lessons learned from their Components project. Kennedy tells us what trends he’s noticing with WordPress themes today and what the state of accessibility looks like for the theme landscape.

\n

After the interview, Jacoby and I have a candid conversation about Gutenberg, what it means for WordPress, our experience with it thus far, and how it’s being developed.

\n

Stories Discussed:

\n

WordPress 4.9 to Focus on Managing Plugins and Themes, Gutenberg Targeted for 5.0

\n

Links Mentioned:

\n

Accessibility Weekly – Kennedy’s hand-curated newsletter about web-accessibility delivered weekly.
\nWordPress Theme Review Team
\nGutenberg
\nUnderscores

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, July 5th 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #279:
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 29 Jun 2017 01:07:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Tue, 25 Jul 2017 19:31:05 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Tue, 25 Jul 2017 19:15:08 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:11:\"HIT lax 249\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20130911040210\";}', 'no'); +(207, '_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:64:\"WPTavern: Adobe to Discontinue Flash Support and Updates in 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73654\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/adobe-to-discontinue-flash-support-and-updates-in-2020\";s: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:3567:\"

\n

Adobe announced today that it will discontinue Flash support and updates at the end of 2020. Flash played an important part in the history of the web, inspiring many of the open standards and formats that the web has moved on to embrace.

\n

Given this progress, and in collaboration with several of our technology partners – including Apple, Facebook, Google, Microsoft and Mozilla – Adobe is planning to end-of-life Flash. Specifically, we will stop updating and distributing the Flash Player at the end of 2020 and encourage content creators to migrate any existing Flash content to these new open formats.

\n

Last year most major browsers moved to block Flash, requiring users to enable it manually for sites where they wish to view Flash content. Microsoft, Google, and Mozilla were on deck today with announcements of their own regarding future Flash support. Firefox is the most aggressive with its plan to disable Flash for most users in 2019. Only those running an Extended Support Release will be able to continue using it through the end of 2020 and no version of Firefox will load the plugin after Adobe discontinues security patches.

\n

Chrome is also phasing out support for Flash and plans to remove it completely from the browser toward the end of 2020.

\n

“Three years ago, 80 percent of desktop Chrome users visited a site with Flash each day,” Google Chrome Product Manager Anthony Laforge said. “Today usage is only 17 percent and continues to decline.

\n

“This trend reveals that sites are migrating to open web technologies, which are faster and more power-efficient than Flash. They’re also more secure, so you can be safer while shopping, banking, or reading sensitive documents.”

\n

The Microsoft Edge team also announced its plans to phase out Flash from both Microsoft Edge and Internet Explorer with complete removal from all supported versions of Microsoft Windows by the end of 2020.

\n

Although HTML5 adoption is growing among game developers, Adobe’s announcement means major changes for segments of the the gaming, education, and video industries that have not yet migrated to newer, open formats. This news will also make obsolete dozens of WordPress plugins that were created to upload and display Flash content.

\n

Adobe’s announcement was met with thanks and “good riddance,” with many calling for an even speedier timeline. Many are also concerned about all the orphaned content and .swf games on the web that Flash’s disappearance will create. Adobe has received many requests on Twitter for the company to consider open sourcing the old Flash Player codebase for the sake of compatibility and archiving content. Adobe has not officially replied to any of these requests.

\n
\";s: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, 26 Jul 2017 04:01:41 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:32:\"HeroPress: Random Diary Chapters\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=1992\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://heropress.com/essays/random-diary-chapters/?utm_source=rss&utm_medium=rss&utm_campaign=random-diary-chapters\";s: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:7701:\"\"Pull

There goes my hero
\nWatch him as he goes
\nThere goes my hero
\nHe’s ordinary

\n
\n

I have no idea what I’m going to write about. How about people? Ordinary people are heroes to me. People who are willing to help one another. People just like you and me.

\n

Well, at least like you \"?\" – if you’re for some reason reading my diary.

\n

Who’s teaching who

\n

I still remember when I build my first website with table layouts while studying math in the University of Jyväskylä. Those were the days! But it doesn’t feel like yesterday anymore. More like day before.

\n

Nevertheless being a math teacher has been the perfect choice for me. It’s been fun, challenging, and rewarding. I’ve probably learnt lot more from students than they have from me.

\n

Heck, they even got me into WordPress when I was taking my ex-students short film course. Was it 2008? Something like that. We needed a website for our short film and had only 1-2 days. Students gave me link to WordPress.com and I was sold. Getting site up and running was easy and fast.

\n

“Well come here and do it yourself!!” – drama class student shouted.

\n

That’s another good lesson I’ve learnt.

\n

It’s so easy to give negative feedback (don’t do it like that) without doing anything yourself or giving constructive feedback.

\n

Oh boy I still feel ashamed when I judged a book by it’s cover. This time the book cover was a blonde girl asking weird questions with high voice. I was a prison of my prejudice and instantly assumed she must be bad at math. How wrong was I. She was brilliant.

\n

At least the prison gate is now open if I just understand to walk out.

\n

Who am I

\n

Sometimes I wonder what other people think of me? Do they think I’m open minded teacher, or front-developer who cares about accessibility. But does any of that matter? Job title really doesn’t tell anything who I am. Or anybody else.

\n

But who am I? I’m not sure how to define me. I’m no dad or husband. I do have several good traits but there are also demons inside me. Lack of empathy is one of them. And that comes down to this:

\n

In the end I’m a selfish asshole.

\n

It’s okay to be selfish from time to time but it’s not okay to let people down big time when they need me most. Being an ordinary human being is not one of my strengths but I’ll promise to work on it.

\n

Friends will be friends

\n

I consider myself lucky. I have lovely parents and two crazy big brothers. And over the years I have made friendships that last forever.

\n

I hope everybody have a friend who is like a bridge between other friends. Someone who is always organizing something fun: bowling, music gigs, dinners, sports. Someone who is always nice to others and would never hurt a fly.

\n

I had a friend like that.

\n

But as a return I couldn’t help him enough. Shadows of life had taken over him. He could not see the light anymore. He died by suicide before christmas 2015.

\n

Now he can’t fall anymore. He will always be our beloved one and we’ll miss him more than words can express. So many songs reflects to memories we have. For example this Finnish song that I heard exactly one year after his death. (Lyrics in english).

\n
\n

Why is it so much easier to talk about other problems but not your own. Why is it so hard to ask help when you really need it.

\n

Life goes on

\n

Do I need to say anything. No I don’t.

\n\"ViewSummer 2017. Peaceful state of mind after a sauna.\n

 

\n\"SamiMy dear friends rock!\n

 

\n\"SamiFriends will be friends forever.\n

WordPress is not important

\n

WordPress is not important. People behind it are, they have feelings. I wish more people would remember that when commenting on blog posts, Slack, or other online tools with shitty attitudes.

\n

Being nice and constructive goes a long way.

\n

At the same time it’s amazing to notice how WordPress combines people together from all over the world. In WordCamps and meetups I have found new friends that really matter. That feels good.

\n

Maybe WordPress is important after all.

\n

The post Random Diary Chapters appeared first on HeroPress.

\";s: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, 26 Jul 2017 00:00: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:\"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: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:133:\"WPTavern: SiteLock Acquires Patchman’s Malware and Vulnerability Detection Technology, Expands WordPress Customer Base to 4 Million\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73626\";s:7:\"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:140:\"https://wptavern.com/sitelock-acquires-patchmans-malware-and-vulnerability-detection-technology-expands-wordpress-customer-base-to-4-million\";s: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:4517:\"

\n

SiteLock, a website security company, has acquired Patchman, a Dutch security startup that offers automated vulnerability patching and malware removal for hosting providers. Prior to the acquisition SiteLock protected 6 million sites, with 2.2 million of them running on WordPress. The addition of Patchman extends SiteLock’s customer base to 12 million sites and more than 4 million of those are powered by WordPress.

\n

Patchman detects vulnerabilities in a wide range of popular applications and quarantines and patches threats automatically. The quarantine feature neutralizes malicious files by removing them from public access. Patchman supports detection and patching for WordPress 3.x and later.

\n

Historically, the service has not included patches for plugins but it has applied them on a case-by-case basis for high impact vulnerabilities, including a few found in WP Super Cache, MailPoet, and the open source Genericons font project. The Patchman dashboard allows users to easily track files where vulnerabilities have been detected, view status, and revert patches if necessary.

\n

\n

Patchman’s single focus on hosting providers gives SiteLock the opportunity to offer more options to its hosting partners. With the acquisition, the company is now partering with more than 500 hosting providers, including BlueHost, 1&1, Web.com, InMotion, Melbourne IT, GMO (NTT), and many others.

\n

“During our early talks, Patchman was not looking to be acquired and SiteLock wasn’t looking to acquire,” SiteLock President Neill Feather said. After meeting at the WorldHostingDays show in Rust, Germany in late March this year and at another show in Los Angeles, the companies found they shared similar goals and would be in a better position working together.

\n

“It truly was a matter of 1+1=3,” Feather said. “Traditionally, SiteLock is very strong in detecting and removing malware for end users. Patchman offers a service tailored specifically to hosting providers and aimed at fixing the security vulnerabilities that hackers exploit to infect websites with malware. By working together we are able to address a wider market and offer a broader solution to the problems that we solve for our customers. We can now attack the problem from multiple angles.”

\n

Patchman’s technology will compliment SiteLock’s existing security features but the company has not yet decided how it will be incorporated into its security plans for customers. Feather said the team is still jointly building out its future roadmap to give hosts and end customers access to a wider range of products. They are also considering making Patchman’s detection technology compatible with more products in the WordPress ecosystem.

\n

Feather could not disclose any specifics on revenue generated by SiteLock’s WordPress security products but approximately 30% of its newly expanded customer base is running on WordPress.

\n

“What we can say is that we’re heavily invested in the WordPress community and plan on continuing to do so,” Feather said.

\n

“I’m excited that the increased number of sites we now protect across multiple platforms means we’ll be able to identify malware and malicious trends more efficiently than we’ve been able to already, and that’s good for every end user,” SiteLock’s WordPress Evangelist Adam Warner said. “Secondly, although we already have solutions for our partners, Patchman allows web hosts to offer increased security options for advanced users of their platforms. Being a WordPress guy, I’m excited about the possibility we now have to extend the capabilities of Patchman to plugins and other WordPress-specific software.”

\n
\";s: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, 25 Jul 2017 18:46:32 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:3;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"WPTavern: Watch WordCamp Varna Wapuus Get Designed in Real Time\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73617\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/watch-wordcamp-varna-wapuus-get-designed-in-real-time\";s: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:1427:\"

\n

The very first WordCamp Varna will be held September 2-3 at the University of Economics. Varna is a beautiful city in Bulgaria on the Black Sea and a popular spot for summer holidays. It is the first Bulgarian WordCamp to be held outside of Sofia.

\n

Tickets are on sale for EUR 10 (BGN 20) and include all the sessions, lunch, a #WCVAR 2017 T-shirt, and a few drinks at the after party. There are 102 remaining for the conference and 14 remaining tickets for the kids’ workshop (ages 7-14).

\n

The location naturally inspired a maritime sticker pack collection for attendees, featuring four new wapuu designs. The collection was designed by the vector graphic illustrators at GraphicMama, a design partner for the WordCamp. Ever wonder how much effort goes into designing all the individualized creations in the world of wapuus? Check out the video below to see how WordCamp Varna’s wapuu designs were brought to life.

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 25 Jul 2017 04:14:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:64:\"WPTavern: New Aztec Editor for WordPress Mobile Apps Now in Beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73587\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/new-aztec-editor-for-wordpress-mobile-apps-now-in-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3390:\"

WordPress’ iOS and Android apps will soon be getting a new editor. The appearance of the new editor, codenamed “Aztec,” is very similar to the old one but is light years ahead of its predecessor in both speed and reliability. Aaron Douglas, iOS engineer at Automattic, announced the open beta for Aztec today with a side-by-side comparison video of the old and new editors. A copy and paste test with 500 paragraphs on iPhone 6s demonstrates Aztec’s instantaneous response while the old editor takes two-minutes to render the text.

\n

\n

In addition to better speed and performance, Aztec’s use of OS-provided text controls makes it possible to offer full support for accessibility technologies like iOS’ VoiceOver and Android’s TalkBack. It also adds the ability to draft using dictation.

\n

Aztec introduces a new undo/redo tool at the top of the screen as a quick option for fixing mistakes. It also provides a simpler, more reliable experience using spell check.

\n

\n

The Aztec beta is available to all users in the latest updates of the app (8.0 for iOS, 7.8 for Android). After opening the app you will see a popup for enabling the new editor. It can also be toggled on/off by going to Me > App Settings and selecting “Set the Editor Type.”

\n

The mobile team has made it easy to test and give feedback without leaving the app. Tapping the “beta” button at the top of the editor will open a “What’s New in the Beta” page with a bug button at the top that you can use to report bugs and send feedback. At the moment, the beta does not support shortcodes or video and WordPress gallery features. Keep in mind that it’s not 100% ready for use and heavy users of the mobile apps are likely to discover glitches.

\n

Aztec is open source (GPL 2.0) and packaged as a rich-text editor component in its own GitHub repository (iOS | Android) so that developers can use it in their own applications and contribute code back to the project.

\n

“Quite literally, there is nothing like this out there – every editor we could find uses a web view or has very limited support for any HTML,” Douglas said. “Our hope is the Aztec editor is seen as a component that can be used by many iOS and Android apps to provide a rich HTML editing experience. We feel that we could garner a bigger contributor base to the mobile apps simply because this component exists, is free and open, and is super awesome.”

\n

The project is a few months behind the schedule published in April, which had open beta targeted for May and the full release for the end of this month. Depending on how well the beta testing period goes, users could see the new Aztec editor included in the mobile apps within the next few months.

\n
\";s: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, 24 Jul 2017 22:59:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:99:\"WPTavern: Hamilton: A Free WordPress Portfolio Theme for Photographers, Illustrators, and Designers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72881\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"https://wptavern.com/hamilton-a-free-wordpress-portfolio-theme-for-photographers-illustrators-and-designers\";s: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:3779:\"

Hamilton is a new portfolio theme released by Swedish designer and developer Anders Norén during his summer vacation. It was created for photographers, illustrators, designers, and image-heavy blogs. The theme displays portfolio items in a minimal, masonry-style grid with an optional tagline on the front page.

\n

\n

“Hamilton has a pretty simple design at its core, so when it was more or less finished, I decided to add a couple of fun theme options to make it more customizable,” Norén said. “The main one is the Dark Mode. With a click of the mouse in the WordPress Customizer, you can change Hamilton from dark text on a white background to white text on a dark background.”

\n

The Customizer also includes a few other helpful options for portfolio sites:

\n\n

The theme is beautifully responsive to various devices and screen sizes. Norén’s typography choices are clean and readable on mobile.

\n

\n

Hamilton includes styles for the default WordPress image gallery with more interesting options available to create complex galleries stacked with different numbers of columns. It also supports Jetpack’s Infinite Scroll module and has styles for blockquotes, pullquotes, and left/right/center aligned media.

\n

\n

One of the most unique features of the theme is the Resume template. It gives users the option to add a simple resume to their portfolios, without having to add a plugin. The template uses basic HTML for formatting with h1 header tags, horizontal rules, and unordered lists. The template could use a bit more documentation, since not all users are familiar with HTML, but it’s a useful addition for simple portfolio sites.

\n

\n

Check out a live demo along with the style guide to see the theme in action.

\n

Hamilton is Anders Norén’s 15th theme approved for the WordPress Theme Directory. When he submitted it to the Theme Review Team, he anticipated that it would take a month or two for it to get through the review process. His previously submitted theme, Davis, took approximately nine months to make it through the queue. He was surprised to find that Hamilton went through the process in under a month. After less than a week on WordPress.org, the theme has already been downloaded more than 200 times.

\n
\";s: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, 24 Jul 2017 19:27: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:\"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:101:\"WPTavern: Members 2.0 Adds Capability Registration System, Introduces New Settings Screen for Add-Ons\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73446\";s:7:\"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:111:\"https://wptavern.com/members-2-0-adds-capability-registration-system-introduces-new-settings-screen-for-add-ons\";s: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:6254:\"

\n

Eight years ago, Justin Tadlock moved back home to Alabama and was living in the spare bedroom of his grandparents’ house with nothing more than a laptop and a suitcase. Over the course of a few months he started going deeper into learning about writing WordPress plugins and produced Members, a role management plugin for WordPress. The first major overhaul of the plugin came in 2015 with version 1.0’s expansion of features and a new UI for editing roles.

\n

Members has built up a user base of more than 100,000 active installs since it first launched in 2009. Tadlock estimates that over the last couple years, 40% of Theme Hybrid customers are primarily there for support and small tweaks to the Members plugin. He decided it was time to begin investing more in the plugin and its community.

\n

Tadlock released Members 2.0 this week. The plugin manages core WordPress capabilities but 2.0 adds the ability for plugins to register custom capabilities. The labels for the capabilities can be internationalized so users can manage the plugin in their own languages in human-readable form.

\n

\n

This release also adds the ability to use the WordPress editor for writing custom post error messages, making it easy to direct visitors to registration or other important information regarding access to the content.

\n

Members 2.0 lets users add multiple roles when creating a new user from the Add User screen. It also introduces the ability to bulk add or remove roles from users, even when multiple roles have been enabled.

\n

\n

This version of the plugin serves some of its data using the WP REST API and a new setting was added to authenticate users who are accessing the REST API endpoints. This protects content from being exposed on sites that have the “private site” setting enabled. Tadlock plans to write a tutorial about what he has learned in integrating the REST API with the plugin.

\n

Tadlock Aims to Monetize Members with Add-Ons, Renews Efforts to Develop a Community of Add-On Developers

\n

Members 2.0 introduces a new Settings screen that ties in with Tadlock’s future plans to monetize the plugin. The new screen includes a view for add-ons. Tadlock has two add-ons available currently and has written an API for third-party developers to register their own add-ons to be visible on this screen.

\n

\n

“The plan is to create some small add-on plugins,” Tadlock said. “There’s already two: Members – Role Levels, which is paid, and Members – Role Hierarchy, which I was hired to build and was allowed to release to the community for free. I’ve got a few small plugins like those in mind that’ll be in a lower price range.”

\n

Tadlock also plans to release a more robust version of the “Content Permissions” feature as another add-on. He has received numerous feature requests from users over the years about what they would like to see in this plugin. The add-on will offer a variety of different ways to show/hide content.

\n

I asked Tadlock if he has considered building payment gateway add-ons so users can charge for memberships. He said the idea is on the table.

\n

“I’m not sure if I’m going to build those or someone else,” Tadlock said. “I’ve mentioned it to some other developers. It would be a good place to start building add-ons.” His current setup uses Easy Digital Downloads with a couple of plugins to bridge it with Members and ThemeHybrid.com.

\n

A plugin like Members has the potential to have a large, third-party ecosystem of plugins for payments and additional features, but Tadlock was focused on other projects during the first few years after it launched.

\n

“I haven’t actively pursued the add-on angle,” Tadlock said. “Instead, I focused more on themes during most of that time. Now, I’m focusing more on plugin development. It’s my fault for not nurturing a community of add-on developers, which is something I’m trying to do more of now.”

\n

Tadlock said many of the developers he knows are working with Members because they like that it gives them a solid foundation to build on for client work. He hopes to persuade some of them to release some of that code back as commercial add-ons or free plugins in the WordPress plugin directory.

\n

Since launching the plugin eight years ago, Tadlock has aimed to make it behave as if it were a natural part of WordPress. At its core, Members is a role and capability management plugin and not a one-size-fits all membership plugin.

\n

“It’s more or less a UI over what you could do with code already,” Tadlock said. “Most of all, it tries not to get in your way. Every membership site has its own unique needs. It’s tough building something that suits everyone. That’s why I’d rather have that foundation of Members just exposing the roles/caps system with third-party add-ons that suit various users’ needs.

\n

“Other membership plugins often try to please everyone or pigeon-hole everything into their custom system. I like more to have a bit more flexibility without the bloat.”

\n
\";s: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, 21 Jul 2017 21:37:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:61:\"WPTavern: WordPress 4.8.1 Adds a Dedicated Custom HTML Widget\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73470\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wptavern.com/wordpress-4-8-1-adds-a-dedicated-custom-html-widget\";s: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:2681:\"

When WordPress 4.8 was released last month, it introduced TinyMCE functionality to the Text widget. Unfortunately, this caused issues for those who use Custom HTML as the Visual editor often strips out portions of the code.

\n

WordPress 4.8.1 Beta 1 is available for testing and addresses this problem by including a dedicated Custom HTML widget.

\n

“For advanced users or any user who needs to paste in HTML snippets, there is now a dedicated ‘Custom HTML’ widget that is specifically for adding arbitrary HTML to your sidebar,” Weston Ruter, said.

\n

“This widget will retain the application of the widget_text filters, in addition to having a new dedicated widget_custom_html_content filter.

\n

“For use cases that involve adding content to your sidebar, the Text widget will continue to feature the same Visual editing interface that the post editor has (TinyMCE).”

\n

Users who access Text widgets that have Custom HTML in WordPress 4.8.1, will see a note at the top of the widget that suggests using the Custom HTML widget.

\n

\n

If a user pastes or types HTML into a text widget with the Visual editor active, WordPress displays an Admin Pointer suggesting that they use the Text tab instead or use the Custom HTML widget.

\nText Widget Admin Pointer\n

The Custom HTML widget works similar to the Text widget in WordPress 4.7 and below.

\nCustom HTML Widget\n

Sites that have existing Text widgets containing custom HTML that may be modified by the Visual editor, are opened in a legacy mode.

\n

Legacy mode retains the old Text widget interface, including the checkbox on whether or not to automatically add paragraphs. This change prevents the Visual editor from altering code.

\n

Ruter says the ideal way to test these improvements is to install it on a staging site that has Text widgets containing HTML and are known to be problematic in WordPress 4.8. After upgrading, check to see if the widgets open in legacy mode.

\n

WordPress 4.8.1 is scheduled to be released on August 1st. Please report any bugs or errors you encounter in as much detail as possible to the WordPress Alpha/Beta section of the support forums.

\n
\";s: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, 21 Jul 2017 18:31:28 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"WPTavern: Petition to Re-License React has been Escalated to Facebook’s Engineering Directors\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73454\";s:7:\"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:\"https://wptavern.com/petition-to-re-license-react-has-been-escalated-to-facebooks-engineering-directors\";s: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:7983:\"photo credit: manu schwendener\n

React users are petitioning Facebook to re-license React.js after the Apache Software Foundation announced its decision to ban Apache PMC members from using any technology licensed with Facebook’s BSD+Patents License. So far the GitHub issue has received 627 “thumbs up” emoji and 66 comments from concerned React users who are hoping for a change in licensing.

\n

Many respondents on the thread said that ASF’s decision affects their organizations’ ability to continue using React in projects.

\n

“Apache CouchDB and others will switch away from React if we have to,” CouchDB committer Robert Newson said. “We’d rather not, it’s a lot of work for no real gain, but we don’t have a choice. Changing license can be simple (RocksDB completed that change in a day).”

\n

“My team, at LinkedIn, is also having legal troubles using React for our internal projects,” LinkedIn software Denis Ivanov said. “We would love to see a change on this front.”

\n

Software developer Clark Evans commented on how React’s current licensing might affect medical research institutes, and suggested that Facebook consider an Apache 2.0 license because it includes equitable patent grants.

\n

Since U.S. based universities rely upon patent licensing as part of their legislatively mandated technology transfer initiatives, they are growing far more cautious in their due diligence. For this reason, at some universities, software written with React may be shunned. Existing projects using React software may be asked to remove the React software software dependency. Please strongly consider this proposal, since our RexDB work is used at major universities, we do not wish to rework to use a React alternative.

\n

Several participants in the discussion commented that they would like to use React but the licensing makes it impossible for their companies.

\n

“Other large companies such as mine (Adobe) can’t use React, Pop, etc. for the very same reason,” Corey Lucier said. “We’d love to participate in the project, contribute to each, etc. but Facebook’s heavy-handed PATENTS clause is a showstopper.”

\n

“Even mid-size companies like mine (ViaSat) are starting to disallow the use of Facebook’s ‘open-source’ projects for this reason,” software developer Aaron Yoshitake said. “We’d like to build React web and native apps, but it seems that any sensible legal department will recommend against agreeing to Facebook’s asymmetric patent grant.”

\n

Internal Discussions Continue at Facebook, Re-Licensing Issue has been Escalated to Engineering Directors

\n

Dan Abramov, co-author of Redux, Create React App, and React Hot Loader, shared with participants that Facebook is having internal discussions about the re-licensing issue but cautioned them to temper their optimism. He returned to throw some ice on the conversation, which has grown more heated over the past few days, when he said it could only remain an open discussion if everyone involved remains civil. Many participants are concerned about the future of the React-based software that they have already invested thousands of hours of work into.

\n

“I understand that everyone is frustrated about this issue,” Abramov said. “Personally I am just as frustrated to spend time, energy, and emotional wellbeing on legal mumbo jumbo that is preventing people from using React. I would much prefer to spend this time on working together to make it better.

\n

“But the reality of this situation is that the maintainers of React (people like me that you’re interacting on the issue tracker) are not the ones making these decisions. Each of us is doing what we can to show different perspectives on this issue to the people who can make those decisions, and we appreciate your feedback too. But we can only keep discussion open if everyone stays civil and respectful.”

\n

Abramov also pointed out in a follow-up update that a bug tracker isn’t the best avenue for a legal discussion, especially since most participants are software developers and not lawyers. Many have mistaken the thread as a way to communicate with Facebook but there are just a handful of software developers who are representing the React community’s concerns.

\n

“We have heard you very well, and we have passed on your concerns,” Abramov said. “But repeating the same points over and over in different threads does not help move this forward, and creates a lot of noise and stress for the maintainers who are already empathetic to your cause.”

\n

Several participants expressed frustration that the React community cannot participate in the discussions more directly. However, as React is both an open source project and a product of Facebook, the company’s leadership has the last word on licensing issues.

\n

“I understand that software developers like us are not the best people to discuss legal details,” software consultant Erik Doernenburg said. “However, wouldn’t the logical consequence be that the Facebook Legal team, who make such decisions, become active in this forum? Shouldn’t it be possible that all relevant details pertaining to a piece of open source software are discussed in the open? It is incredibly frustrating to have such an important aspect of open software discussed behind closed doors.”

\n

It’s not known whether Facebook is considering another change to its Patents grant or a complete re-licensing. Participants in the discussion are also concerned about other Facebook open source projects like GraphQL, Relay, React Native, and Flow, which share the same BSD+Patents License and are widely used by the open source community.

\n

Dan Abramov left an update today to let the community know that no resolution is available this week. However, the update seemed more positive than the first one, which discouraged participants from being optimistic about a change.

\n

“I want to point out that there is a real momentum behind this discussion internally,” Abramov said. “There are going to be more meetings next week escalating this up to the engineering directors. As you imagine they are quite busy, so this is taking more time than we thought.

\n

“Again, I can’t promise you any specific conclusion, and there is no clarity on where this will land. But please know there are people working on getting your voice heard.”

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 20 Jul 2017 22:37: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:\"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: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:74:\"WPTavern: WPWeekly Episode 282 – Talking WooCommerce with Cody Landefeld\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=73448&preview=true&preview_id=73448\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/wpweekly-episode-282-talking-woocommerce-with-cody-landefield\";s: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:3381:\"

In this episode, John James Jacoby and I are joined by Cody Landefeld, Senior web strategist and founder of Mode Effect. Landefeld describes some of the challenges that shop owners face and provides insight into a couple of WooCommerce projects Mode Effect has recently built.

\n

We discussed the future of WooCommerce and the odds of it turning into a SaaS product. Landefeld shares his thoughts on WooCommerce dropping its 50% renewal discount on subscriptions. Even though the discount is gone, he believes it’s still an affordable option for most users. To close out the show, Jacoby and I discuss the news of the week.

\n

Stories Discussed:

\n

AJ Morris Acquires iThemes Exchange
\nJetpack Professional Plan Introduces Unlimited Access to 200+ Commercial Themes
\nbbPress 2.5.13 Readds Sanitization to Anonymous User Data
\nWP Rollback Adds Multisite Compatibility and Changelog Preview
\nGutenberg 0.5.0 Adds New Verse Block for Poetry and a New Display for Recent Blocks

\n

Picks of the Week:

\n

Gutenberg Boilerplate For Third-Party Custom Blocks by Ahmad Awais. The boilerplate is a great way to learn the basics on creating custom blocks for Gutenberg. It comes with four example blocks.

\n\n

Awais also shared his thoughts on the Gutenberg project.

\n

Add Admin CSS – Using this plugin you’ll easily be able to define additional CSS (inline and/or files by URL) to be added to all administration pages. You can define CSS to appear inline in the admin head (within style tags), or reference CSS files to be linked.

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, August 2nd 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #282:
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 20 Jul 2017 01:19:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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: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:57:\"WPTavern: The State of JavaScript 2017 Survey is Now Open\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73377\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wptavern.com/the-state-of-javascript-2017-survey-is-now-open\";s: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:2708:\"

\n

The State of JavaScript 2017 Survey is now open to web professionals of all backgrounds. The intent of the survey is to provide an overview of the rapidly changing landscape of JavaScript frameworks and tools by gauging which technologies are growing in popularity and which ones people are liking and using less.

\n

The survey, created by Sacha Greif and Michael Rambeau, should take approximately 10 minutes to complete. Topics include JavaScript frontend and backend tools and frameworks, state management solutions, testing tools, CSS, build tools, mobile and desktop technologies, package managers, text editors, salaries, and more.

\n

Last year’s 89-question survey received more than 9,300 responses. Results showed that React ranked higher than other front-end frameworks in terms of developer satisfaction at 92%, followed closely by Vue.js at 89%.

\n

It will be interesting to see if and how these results change with many open source project and companies growing wary of using React after the Apache Software Foundation’s recent decision to ban Apache PMC members from using any technology licensed with Facebook’s BSD+Patents License. A licensing issue that jeopardizes more companies’ ability to use Facebook’s popular open source technologies could precipitate a decline in React’s preeminence among frontend frameworks.

\n

Sacha Greif reports that the survey has received more than 3,500 responses in less than 24 hours, a remarkable number compared to 9,300 over the course of three weeks last year. This response affirms the value that last year’s results provided to web professionals who are attempting to navigate the ever-expanding JavaScript ecosystem.

\n
\";s: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, 19 Jul 2017 20:16:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:67:\"WPTavern: bbPress 2.5.13 Readds Sanitization to Anonymous User Data\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73397\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:78:\"https://wptavern.com/bbpress-2-5-13-readds-sanitization-to-anonymous-user-data\";s: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:1328:\"

The bbPress development team has released bbPress 2.5.13. This release fixes a few bugs, most notably, it readds sanitization to anonymous user data that was accidentally removed in previous versions.

\n

Those who allow anonymous users to create topics and replies on their forums are encouraged to update immediately.

\n

“This feature is not widely used on public forums because spammers aggressively target these kinds of sites, but for communities that rely on this feature, please know you can safely upgrade to 2.5.13 without any issues,” John James Jacoby, lead developer of bbPress and BuddyPress, said.

\n

As a reminder, beginning with bbPress 2.5.12, the minimum version of WordPress supported is 4.7. If you’re using an older version of WordPress, Jacoby recommends using or staying with bbPress 2.5.11.

\n

bbPress 2.6 is still in the release candidate phase as developers iron out a few issues discovered on WordPress.org.

\n

Users can download the latest version of bbPress from WordPress.org or browse to Dashboard > Updates, and upgrade from within WordPress.

\n
\";s: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, 19 Jul 2017 18:22:29 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:63:\"WPTavern: Zagreb to Host 3rd WordCamp in Croatia, September 1-3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72737\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wptavern.com/zagreb-to-host-3rd-wordcamp-in-croatia-september-1-3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4747:\"photo credit: Archives of Zagreb Tourist Board – Author: Marko Vrdoljak\n

WordCamp Zagreb will be held September 1-3 and organizers are anticipating 300 attendees. This is the third WordCamp to be held in Croatia, following WordCamp Rijeka (2015) and WordCamp Split (2016). Although it changes cities every year, the camp is known as Croatia’s annual WordCamp.

\n

“Having WordCamp change cities each year is quite normal for us,” WordCamp Croatia co-organizer and Zagreb meetup organizer Emanuel Blagonic said. “A lot of people from other cities travel to meetups too. Our largest meetup in Zagreb, which usually has 80+ people present and 100+ live stream viewers, usually has people attending from a 300km circle around Zagreb. People also travel to Split when there are meetups there.”

\n

A renewed discussion on regional WordCamps is firing up on the WordPress Community team P2 blog, as the topic was discussed at the Community Summit and with recent developments in WordCamp Netherlands being reinstated and WordCamp Asia a possibility for 2019. Croatia is another example of a country where a national WordCamp might benefit the community.

\n

“When we started with organizing a WordCamp in Croatia, as a community we hoped that WordCamp will help us boost local communities, thus not having everything centralized in Zagreb (where most other meetups happen, i.e. PHP, Design, UX, JavaScript, Python, etc.),” Blagonic said. “As a community we strongly believe that every region is different and it should be viewed like that. So far we are organizing WordCamps ‘no matter what,’ but having a ‘national WordCamp would mean more Croatian sponsors and better coverage from national media.”

\n

WordCamp Zagreb will be a three-day event, beginning with workshops on the first day as the event has done in previous years. Organizers are planning for 12 workshops in four tracks that will be open to public registration. The main conference will be held Saturday with two tracks. Contributor Day will close out the event on Sunday, followed by a walking tour of the city.

\n

Friday’s workshops will be held mostly in Croatian, except a few, such as WordPress Basics and Public Speaking, which will be conducted in English. All of the conference talks this year will be in English.

\n

“Croatia is a tourist country and most of the people here speak good English, which is often used at large tech events,” Blagonic said. “With that in mind, every WordCamp so far was (mostly) in English, which means it’s quite welcoming for people outside Croatia, too (Slovenia, Austria, Italy, Germany) – and our community likes to meet new people. Unlike WordCamps, we see Meetups as strong local events so we usually have talks in Croatian there.”

\n

Blagonic said every year so far the WordCamp has had approximately 20% of its attendees traveling from outside Croatia, as the country is relatively small with a population of 4 million. Most attendees travel to the WordCamp from other parts of Croatia.

\n

Croatia currently has five local meetups, but only the two in Zagreb and Split have enough members to meet regularly. Blagonic said he sees the meetups as a way to help local communities grow and views the WordCamp as “a celebration of the country community.” However, he believes centralizing the larger events too much would be detrimental to growing the fledgling WordPress communities in the smaller cities.

\n

“I’d say that in Croatia (and in the region) we have a young democracy and we still haven’t found the best way to connect with people,” Blagonic said. “For example, there are four big cities in Croatia where most of the things happen, and the tech scene is quite strong in them. If you go outside of these four hubs, a lot fewer things happen, which is a problem for people living outside. We believe that having a centralized country is bad for growing local communities (outside these areas) so with changing cities each year and with traveling to other Meetups/WordCamps we hope that we will change how people feel about it. “

\n
\";s: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, 19 Jul 2017 18:11: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: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:29:\"Donncha: WP Super Cache 1.5.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:\"https://odd.blog/?p=89500337\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:49:\"https://odd.blog/2017/07/19/wp-super-cache-1-5-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:5935:\"

WP Super Cache is a fast full-page caching plugin for WordPress. Download it from your dashboard or get it here.

\n

Version 1.5.0 has been in development for some time. It has a ton of bug fixes and new features.

\n

REST API

\n

The headline new feature is REST API access to the settings. This will allow developers to create their own interface to the settings of the plugin. Unfortunately it isn’t yet documented but you can see the code in the rest directory. Start with load.php where you’ll find the code that registers all the endpoints. Users who access the API must be logged in as admin users. If you want to test the API, see the end of this post.

\n

Settings Page

\n

We have also simplified the settings page to make it easier to choose which caching method is used.

\n

\n

Instead of maybe confusing the user with technical words like PHP, mod_rewrite and WP-Cache we have split them up into “Simple” and “Expert” delivery methods, and done away with mentioning WP-Cache completely. Simple delivery uses PHP, expert uses mod_rewrite and well, WP-Cache got the boot because it’s always active anyway.

\n

WP-Cache caching is always active, but it can be disabled in different ways.

\n\n

Headers

\n

We expanded the number of headers cached by the plugin. The list of headers was borrowed from Comet Cache. However, anonymous users will still only see the bare minimum like content-length or content-type. If you need to use security headers like “X-Frame-Options” or “Content-Security-Policy” you should enable caching of HTTP headers. This unfortunately disables super caching so only WP-Caching is used but it’s still very fast (and faster in this release than before which I will get to below). You can also use the “wpsc_known_headers” filter to modify the list of recognised headers.

\n

WP-Cache Reorganisation

\n

WP-Cache cache files are split into two files – one holds the page content, the other (meta file) holds information about the page such as cookies, headers and url. In the past these files were stored in two directories which could become a problem if there were many thousands of those files. Even with only a few hundred files, maintenance could be an issue as deleting related files (like page archives, or copies of the front page) needed every meta file to be inspected.
\nNow the files are stored in the supercache directory structure that mirrors your permalink structure. Deleting related files is is simpler and serving files will be faster as the operating system won’t need to open a directory of thousands of files.
\nIf you currently rely on WP-Cache files, the plugin will still look for them where they are, but new WP-Cache files will be created in cache/supercache/example.com/ (where example.com is your hostname).

\n

Sitemaps

\n

We added support for caching sitemaps, but your sitemap plugin will need to cooperate to get it to work. The sitemap plugin needs to identify the sitemap request as a feed. Jetpack 5.1 now supports this since #7397. You can disable the caching by excluding feeds from caching.

\n

Debugging Improved

\n

The debug log is now protected by a username/password. For convenience, the username and password are the same but they are a long md5 string:

\n

\n

Deleting the log file clears it and resets it ready for more logging. Before, toggling debugging would create a new debug log and the old one would be kept around, but not linked, until deleted by garbage collection, and of course they were text files anyone could access.

\n

This release includes lots of other small bug fixes and changes. Take a look at the number of closed PRs for an exhaustive list of those changes!

\n

Testing the REST API

\n

There are a number of ways to send POST requests to a web server but one I like is using curl in a shell script. You’ll need two bits of information from the website:

\n
    \n
  1. The “wordpress_logged_in” cookie from your browser.
  2. \n
  3. The wp_rest nonce which you can get by adding `echo wp_create_nonce( ‘wp_rest’ );` somewhere on your site where you’re logged in. It’s good for 24 hours.
  4. \n
\n

My test script looks something like this:
\nexport NONCE=\'1234567890\'
\nexport COOKIE=\'wordpress_logged_in_xxxxxxxxxxxxxxxxxxxx=1234567890\'
\ncurl -v -X \"GET\" -H \"Content-Type: application/json\" -H \"X-WP-Nonce: $NONCE\" -H \"Cache-Control: no-cache\" -H \"Cookie: wordpress_test_cookie=WP+Cookie+check; $COOKIE\" \\
\n-d \'{}\' \"https://example.com/wp-json/wp-super-cache/v1/settings/\"

\n\n

Related Posts

\n

Source

\";s: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, 19 Jul 2017 12:25:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:32:\"HeroPress: Becoming Myself Again\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=1978\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://heropress.com/essays/becoming-myself-again/?utm_source=rss&utm_medium=rss&utm_campaign=becoming-myself-again\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6018:\"\"Pull

It’s so easy to become secluded and sit at home, in your own bubble, but it wasn’t until a group of people literally pulled me in with their welcoming atmosphere and demeanor, that I realised that I could function amongst other people as well (even if it was somewhat limited).

\n

In The Beginning

\n

To understand my bubble, you need to also know a little about me, or rather, about my childhood. I had a less than ideal childhood. I have a great family, lived in a great house, even in the “best country in the world” as they say. And despite this, I say I wasn’t happy with my childhood. My school years were the reason, they were rough. At times I think back and feel like events that unfolded were parts of ridiculous scenes from an over the top movie.

\n

All in all, the days seemed generic enough, except my school days were a thing of dread. I would suffer physical and verbal abuse throughout my schooldays, even going to and from school, I had no real friends (victim by association is understandably not something a child would want to intentionally walk into. I understand this as an adult, but as a child it’s not that easy).

\n

Because of my treatment over the years, I developed trust issues, I got a fear for everyone around me, and it was growing stronger and stronger over the years.

\n

I suppressed it, I lied about it, and I got terrifyingly good at the lying part.

\n

This is why I was drawn to the internet: I didn’t have to interact with people, I didn’t need to go outside where the others were, I could just do my thing and move on. I could live in my own bubble.

\n

Finding WordPress

\n

But then the darndest thing happened. I’d been stuck on a project, I needed help, and I turned to a support room for an open source project, for WordPress. If you’ve ever tried to get help in a chat before, you’ll know what kind of an experience it can be, the snarky reactions to your code, the nitpicking of using the wrong terminology, it’s not fun. This place though, they didn’t care that I was not only using the wrong terms, but my entire code was a horrible mess.

\n

Where I would usually get the help I needed and move on, popping back in my bubble of solitude, I instead wanted to be like these people, I wanted to use what I learnt to let others get helped.

\n

Over the years, I all but devote myself to that place. Nobody knew me, I liked staying under the radar, but eventually I got pushed into a team meeting. I was intrigued, so I would watch, I’d say hi, and progressively make my opinions heard. Yet, I would stick to my bubble, once the meeting was over I was back on my own.

\n

And Then I Went To WordCamp

\n

Until I got to attend my first big WordCamp, the last one held in San Francisco, I was ecstatic! I’d never been to a big conference before, as I didn’t like crowds, but I knew some of the people who would be there. They were people who had been friendly and inviting in the most genuine way imaginable. It’s not easy being worried whenever you’re out amongst people, but this group of people, this community, I didn’t have that fear around them.

\n

I somehow made WordCamps my safe space.

\n

They are where I can, if only for a short while, leave that bubble, leave the need to be alone, and be a part of something great! I use them as fuel to get through the hard times, I can look forward to meeting people, people who value my opinions and my experience. People who genuinely want to listen and most of all, care about you! The WordPress community is, slowly but surely, helping me get rid of my ingrown fear of the unknown, of others.

\n

The community is helping me become myself again.

\n

The post Becoming Myself Again appeared first on HeroPress.

\";s: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, 19 Jul 2017 12:00: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:\"Marius Jensen\";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:104:\"WPTavern: New WordPress Contributors Meeting Provides Opportunities to Ask Questions and Learn the Ropes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73007\";s:7:\"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:115:\"https://wptavern.com/new-wordpress-contributors-meeting-provides-opportunities-to-ask-questions-and-learn-the-ropes\";s: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:2270:\"

Contributing to WordPress or other open source projects can be intimidating for first-time contributors. Sometimes, all you need is a helping hand to overcome fear, intimidation, or other barriers.

\n

In 2013, with the help of Konstantin Obenland, a WordPress core developer, I overcame my fear and contributed my first patch to WordPress.

\n

This is one of the principles behind a new weekly meeting that is geared towards new contributors.

\n

“The new contributors meeting is the perfect place to come if you are new to contributing to WordPress core and have questions,Adam Silverstein, WordPress core contributor, said.

\n

Every Wednesday at 3PM Eastern Daylight Time, users can visit the #core WordPress Slack channel and ask questions related to patches, tickets, and review the good-first-bugs report on Trac.

\n

The first meeting was held on July 5th where participants asked questions about working with Git in WordPress core, applying patches, and unit testing. In the second meeting, participants discussed whether or not new contributors are allowed to make changes to tickets.

\n

Other topics mentioned include, which repositories to use, clarification on contributing to core versus updating the WordPress Developer’s site, and which tickets to select for review.

\n

The next meeting is on Wednesday, July 19th at 3PM Eastern. If you have any questions on how to contribute to WordPress, be sure to join the WordPress #core Slack channel at that time and ask away.

\n

Meeting notes with links to discussions, tickets mentioned, and other resources are published on the Make WordPress Core blog under the #new-contributors tag

\n
\";s: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, 19 Jul 2017 05:09:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:72:\"WPTavern: WP Rollback Adds Multisite Compatibility and Changelog Preview\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73315\";s:7:\"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:\"https://wptavern.com/wp-rollback-adds-multisite-compatibility-and-changelog-preview\";s: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:4021:\"

\n

In the two years since WP Rollback launched on WordPress.org, the plugin has racked up more than 30,000 active installations with nearly all 5-star reviews. It allows users to roll back any WordPress.org plugin or theme to a previous version with just a few clicks and also supports beta versions of plugins.

\n

It’s easy to see why the plugin is so popular. Navigating buggy updates is a natural part of life when maintaining a self-hosted website and not all users have a separate testing environment for their websites. This tool gives them a basic diagnostic tool and the confidence to apply updates knowing they can easily roll it back in case of a problem. Many reviewers cite the plugin as having been “a lifesaver” when applying WooCommerce or Yoast SEO updates that had unexpected results.

\n

The lone one-star review of WP Rollback was given because the user anticipated multisite compatibility and was unable to get it to work. That issue has been solved in the latest update.

\n

WP Rollback 1.5 is fully compatible with multisite networks, giving super admins the ability to roll back extensions from the network plugin/themes screen or from the the plugins/themes screen of the primary site in the network. Sub-sites do not have the ability to roll back plugins and themes for the entire network. The UI for rolling back themes on the network admin screen is identical to the plugin screens, as multisite doesn’t have the fancy theme preview screen that single site installs have.

\n

Version 1.5 also adds the ability for users to preview the changelog for previous versions of a plugin. This makes it convenient for users to quickly view the changes for each version without leaving the admin.

\n

\n

WordImpress, the folks behind WP Rollback, have considered adding core rollbacks and database savepoints, but both features have serious potential drawbacks that could turn it into a high support-demanding plugin. In its current state, the plugin is virtually support-free.

\n

Matt Cromwell, Head of Support and Community Outreach at WordImpress, said the team thought about monetizing the plugin in the beginning, but is not pursing any plans to do so at this time.

\n

“We think of it as just one of the many ways we are giving back to the WP community,” Cromwell said. “Our preference would be for the core team to consider it as a potential feature plugin for eventual core inclusion.”

\n

Cromwell said WordImpress hasn’t made any intentional steps to see if core folks are interested in WP Rollback becoming a feature plugin, but the team has purposely built it to be as close to core standards as possible. He believes it would be relatively easy to implement in WordPress.

\n

Suggestions for new features, general feedback, and bug reports are welcome on WP Rollback’s GitHub repository. The plugin’s authors recommend backing up your site before using it to rollback plugins and themes or testing rollbacks on a staging site first. WP Rollback is not capable of rolling back changes a plugin update has made to the database, so a backup can come in handy if the database changes are incompatible with previous versions.

\n
\";s: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, 18 Jul 2017 22:24: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: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:136:\"WPTavern: React Users Petition Facebook to Re-license React.js after Apache Software Foundation Bans BSD+Patents License in Dependencies\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73216\";s:7:\"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:146:\"https://wptavern.com/react-users-petition-facebook-to-re-license-react-js-after-apache-software-foundation-bans-bsdpatents-license-in-dependencies\";s: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:9983:\"

\n

The Apache Software Foundation issued a notice over the weekend, indicating that it has added Facebook’s BSD+Patents license to its Category X list of disallowed licenses for Apache PMC members. This is the license that Facebook uses for most of its open source projects.

\n

A representative from Facebook’s RocksDB team commented on the Apache Foundation’s post to advise that the project will meet the August 31st deadline for relicensing in order to be in compliance with Apache PMC member requirements, and that change has been committed today:

\n

The RocksDB team is adjusting the licensing such that it will be dual-licensed under the Apache 2 and GPL 2 (for MySQL compatibility) licenses. This should happen shortly and well ahead of August 31st. I’ll leave the history and philosophy around licensing alone since it’s generally a complex discussion to have and I’m not sure that it has actually been fully captured in this thread especially vis a vis Facebook’s intent.

\n

Hopefully this morning’s guidance to PMCs can be adjusted since I don’t think any of us see a bunch of extra engineering effort as a desirable thing across the ASF projects which are already making use of RocksDB

\n

In light of the ASF Legal Affairs Committee’s decision to disallow the BSD+Patents License in Apache projects, ASF member Joan Touzet opened an issue on the React repository urging Facebook to consider re-licensing React.js under Apache License v2.0 and GPL 2:

\n

\nThis has led to a lot of upset and frustration in the Apache community, especially from projects requiring similarly-licensed code as direct dependencies – the chief of these being RocksDB.

\n

We (the Apache Software Foundation) have just received word that RocksDB will be re-licensing their code under the dual Apache License v2.0 and GPL 2 licenses.

\n

As a user of React.JS in an ASF top-level project (Apache CouchDB), please consider re-licensing React.JS under similar terms. Otherwise, many ASF projects such as our own will have to stop relying on and building with React.

\n

Although the re-licensing of RocksDB solves that particular project’s problem, ASF’s ban of Facebook’s BSD+Patents license means other widely used technologies from Facebook, including React.js, are still banned. This is likely to cause problems for many open source projects.

\n

Harshavardhana, from the Minio team, commented in support of the petition to Facebook for re-licensing React.

\n

“Our object storage browser UI is based on React and we are Apache 2.0 licensed,” he said. “It would be unfortunate and time consuming to migrate but we will have to do that in lieu of new information regarding Apache incompatibility. Please consider re-licensing React.”

\n

Contributors to Om, a ClojureScript interface for React, are also discussing whether or not the ASF’s new requirements will affect their project. Greg Stein, commenting on behalf of ASF, clarified the reasons behind the organization’s decision to ban Facebook’s BSD+Patents license:

\n

Please note that the ASF chose this path for policy reasons, rather than “license incompatibility”. We don’t want downstream users of Apache code to be surprised by the PATENTS grant that (was) in RocksDB and (is) in React. Users should only need to follow the ALv2, with no further constraints.

\n

These license can work together (IMO) and simply provide two sets of restrictions upon users.

\n

Stein said it was not ASF’s lawyers who made the decision but rather the organization’s policy decision to “disallow FB/BSD+Patent license to be mixed into the software the Foundation releases to users.”

\n

Facebook is Internally Discussing the Re-Licensing Matter

\n

Dan Abramov, co-author of Redux, Create React App, and React Hot Loader, joined the discussion on GitHub regarding re-licensing with a brief and ambiguous summary about how Facebook is handling the petition to re-license.

\n

“To give you a small update, there are going to be more internal discussions about this for about a week,” Abramov said. “This is about as much as I can say. I wouldn’t be too optimistic about this changing for React but we’ll see. @daveman692 has kindly agreed to provide an update when these discussions are over.”

\n

Dropping the patent grant entirely, which would be the most convenient way of solving this issue for open source projects, isn’t likely to happen. React has already gone through re-licensing twice during its short history. It was originally licensed under Apache 2.0 but this was changed in October 2014 to the BSD License plus the patent grant, which included a highly controversial termination provision. In April 2015, the patent grant was changed slightly to allow licensees to continue to use the software in the event that a patent lawsuit did not include a counterclaim against Facebook or its affiliates in a matter unrelated to React.js.

\n

The termination provision in Facebook’s BSD+Patents License continues to be unpopular and is regarded suspiciously by many open source project maintainers. When the Drupal project began considering a client-side framework to supersede Backbone.js, Dries Buytaert passed on React based on what he said was “a potentially unacceptable patent clause,” citing pushback from WordPress.com’s Calypso and React contributors.

\n

The WordPress open source project has not formally announced its decision on which JavaScript framework will be included in core, but all signs point to React. WordPress’ upcoming Gutenberg editor is built on React and its chief contributors are Automattic employees who work on React-based products for WordPress.com. Gutenberg continues to plough forward at a breakneck pace with no indication of a rewrite, and WordPress co-creator Matt Mullenweg has been outspoken about his preference for using React.

\n

Although Automattic’s legal counsel has said the company is comfortable using React for its product under the project’s current license , others in the WordPress community are not as amenable to including the framework in core.

\n

The Open Source Initiative (OSI) includes a generic BSD+Patent license listed among its approved licenses, but Facebook’s particular BSD+Patent license has not been submitted. Robert Pierce, a partner at El Camino Legal, contends that the license termination provision ought to be impermissible in an open source license because it exists to protect Facebook from patent litigation that is completely unrelated to React code:

\n

Facebook touts React.js as open source software. But in my mind the license termination provision of the Additional Grant of Patent Rights takes the offering outside the realm of open source software.

\n

The patent license offered in the Additional Grant of Patent Rights (v.2) is conditioned upon the licensee not bringing a patent infringement lawsuit against Facebook or its affiliates. Thus, the licensee pays a price to use the library. It is not a price paid with money. The price demanded by Facebook for use of the library is that the licensee refrain from exercising any of its patent rights against Facebook or its affiliates.

\n

Pierce views Facebook’s publication of React source code as leverage to win some protection against patent lawsuits, which he deems to be “too greedy an approach for Facebook to claim open source status.”

\n

The open source community has widely speculated about the implications of including Facebook’s BSD+Patent license as a dependency, but the license has not yet been tested in court. The Apache Software Foundation is the first major organization to take a hard line stance on the controversial license and this has caught Facebook’s attention. Facebook representatives have promised an update on the petition for re-licensing after its internal discussions have concluded.

\n
\";s: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, 18 Jul 2017 03:25:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:76:\"WPTavern: Stylishly Display Weather Conditions with the Weather Atlas Widget\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73229\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/stylishly-display-weather-conditions-with-the-weather-atlas-widget\";s: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:2207:\"

If you’re looking for an easy way to display weather conditions on your site, check out the new Weather Atlas Widget by Yu Media Group d.o.o. Once activated, browse to Appearance > Widgets, and add the Weather Atlas widget to a sidebar. 

\nWeather Atlas Settings\n

As you begin typing, a drop-down list of cities is displayed. This helps choose the correct city. From here, users can configure the following settings:

\n\n

Users can display sunrise and sunset times, heat index, wind chills, UV index, wind speeds, humidity, and pressure. You can also hide or display hourly forecasts.

\nForecast for Cleveland, Ohio\n

It’s recommended that for three-hour forecasts, you use the vertical layout and for five-hour forecasts, the horizontal layout. The same recommendations apply for daily forecasts.

\n

The widget not only looks nice but it also changes color based on temperature. Shades of blue represent cooler temperatures while shades of red represent warmer temperatures.

\nTemperatures Represented by Colors\n

By default, the bottom of the widget displays the text, “Weather from Weather Atlas”. However, if you choose to display the detailed forecast, the text is replaced with a Detailed Forecast link. This link takes visitors to a page on Weather-Atlas.com that displays detailed weather conditions for the selected city.

\n

I tested the Weather Atlas Widget on WordPress 4.8 and didn’t encounter any issues. It’s available for free on the WordPress plugin directory.

\n
\";s: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, 18 Jul 2017 01:55:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:71:\"WPTavern: Gutenberg Boilerplate Demonstrates How to Build Custom Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73202\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"https://wptavern.com/gutenberg-boilerplate-demonstrates-how-to-build-custom-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4716:\"

\n

Gutenberg is still in beta but developers are already getting ready for creating their own custom blocks. Over the weekend Ahmad Awais released a new project called Gutenberg Boilerplate For Third-Party Custom Blocks. Awais’ introductory post includes a rundown of his thoughts on the current pros and cons of developing for the Gutenberg project. Although he appreciates the technology behind Gutenberg and the improvements over shortcodes, he is not fully sold on the concept of putting everything into blocks. To learn more, he decided to jump into the code.

\n

“I am still making up my mind with how Gutenberg will fit in the WordPress core,” Awais said. “There are so many things which are both good and bad about it. So, instead of ranting about it, I wanted to do something more productive. I went ahead, studied the source code and received a lot of help from Gutenberg contributors (Matias Ventura, James Nylen, Riad Benguella, Andrew Duthie, Joen, etc.) to finally build a Gutenberg Boilerplate project.”

\n

Awais’ Gutenberg Boilerplate is a good starting place for learning more of the basics about developing for the editor. It comes in the form of a plugin that offers four examples of how to build different kinds of custom Gutenberg blocks, with and without a build process:

\n\n

For example, the tweet block, which is something that might previously been handled with a shortcode, is an example that includes four files: block.js to register the custom Gutenberg block, editor.css, style.css, and index.php.

\n

\n

Awais noticed that many developers were wanting to try building third-party blocks, but Gutenberg’s documentation for this was outdated and/or non-existent. He got involved in contributing to the project’s documentation after discovering the docs describing how to enqueue block and block editor assets were not available. This gave him the inspiration to create a boilerplate.

\n

“Both as a theme/plugin developer, I think there’s going to be a steep learning curve here for just about everyone – users as well as developers,” Awais said. “WordPress development just became very complicated with the Gutenberg project. I’m also not sure how devs will start writing extensions. Some users might expect them to keep the shortcodes for the old editor. Some might ask for blocks in the new one. Is there an API or back-compat? In short everything is changing and this change has both pros and cons.”

\n

These concerns also tie into the larger discussion around how Gutenberg can support legacy metaboxes that use the old PHP framework, instead of updating to the new JS.

\n

“New metaboxes should be written in JS, and will appear in the Post Settings sidebar alongside the stock ones,” Gutenberg contributor Joen Asmussen said. “Metaboxes written in PHP should ideally be upgraded to be JS, but should continue to work in their PHP form also.” Asmussen has proposed an “Extended Settings” panel to house legacy metaboxes in a section below the editor. It would appear only when legacy plugins and metaboxes are enabled, as shown in the mockup below.

\n

\n

Discussion regarding how to support metaboxes is still ongoing. With so many important issues like this up in the air, it’s too early to know what the future of extending Gutenberg will look like. At the moment, the project is undergoing rapid development and changes, so extending Gutenberg may evolve drastically over a short period of time. If the editor is to preserve the same flexibility and customization opportunities of its predecessor, the project will need to ensure that it is easy to create custom blocks and extensions while continuing to support older PHP metabox infrastructure that is currently widely used.

\n
\";s: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, 17 Jul 2017 20:28: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: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:93:\"WPTavern: Gutenberg 0.5.0 Adds New Verse Block for Poetry and a New Display for Recent Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72830\";s:7:\"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:\"https://wptavern.com/gutenberg-0-5-0-adds-new-verse-block-for-poetry-and-a-new-display-for-recent-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5718:\"

Another round of Gutenberg updates was released today. Last weekend brought version 0.4.0, which didn’t have too many noteworthy visible changes on the frontend but introduced an API for handling pasted content. Gutenberg developers are aiming to have specific handling for converting pasted content from applications like Word, Markdown, and Google Docs to native WordPress blocks. Version 0.4.0 also added navigation between blocks using arrow keys and included a new approach for rendering embed frames.

\n

Gutenberg 0.5.0 hit dashboards today. One major improvement to the writing flow is that the editor will now avoid showing block UI while the user is typing and/or starting a new paragraph in a text block. You can test this by typing and pressing enter twice to begin a new text block. No UI should be visible during this process. Small improvements like this one are gradually bringing a bit more zen to the editor, which is still full of confusing and surprising experiences.

\n

Version 0.5.0 adds the ability to upload images via drag-and-drop onto image block placeholders. The example below shows one of my tests. While the image is uploading, it fades in and out. This experience is a bit disconcerting, especially if the upload never resolves. I’m not certain this UI provides the best communication for the status of the image upload.

\n

\n

This version also introduces a new Verse block, which is intended for poetry. It has a slight indent, as compared to a plain text block, but it doesn’t yet work well with copy and paste. Unless you are a poet composing in WordPress, it’s far more likely that you will be pasting in poetry content from somewhere else on the web. Other than the initial bugs, it’s a useful block for those who often post verse.

\n

\n

With the growing number of block types, it can be cumbersome to sort through all of them when adding a new block. Gutenberg 0.5.0 implements a new display for recent blocks. A maximum of eight are shown and the most recently used ones are displayed at the top. It does not yet persist between editor sessions, but Gutenberg contributors plan to add that in the future.

\n

\n

Other notable improvements in this release include the following:

\n\n

Writing Long-Form Content with Gutenberg is Still a Frustrating Experience

\n

Gutenberg in its current state is a long way away from being an editor that users would embrace for long-form writing. It still contains many unnerving bugs that steal user confidence. For example, when pasting in multiple paragraphs from a lorem ipsum generator, the editor gave me a white screen and I lost all of the content in my post. After a bit of testing I found that pasting in paragraphs one at a time worked.

\n

This kind of frustrating and unexpected behavior has caused many testers to wonder why it isn’t being referred to as alpha software instead of beta. WordPress contributor Jon Brown summed up this common sentiment in a comment on the 0.4.0 release post.

\n

“It’s getting better, but it honestly still feels more like a 0.0.4 alpha than a 0.4.0 beta,” Brown said. “I’ve tried writing long form content several times with each version since 0.1.0 and each time I’m quickly frustrated by the lack of flow between blocks. It’s more frustrating than TinyMCE.”

\n

Gutenberg needs to make significant progress before it can be suitable for writing anything more than a few short paragraphs. It’s nearly impossible to get into the flow of creating long-form content with the prominence of the block UI. Right now, the editor just gets in the way. The current UI is skewed heavily towards frequent block creation. It is clutter-some and distracting for pure writing tasks. Following the evolution of the editor, with its fast-paced development cycle, is exhilarating after years of stagnation. But the project is sorely in need of a breakthrough where the Gutenberg UI finally gets out of the way of writing.

\n
\";s: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, 15 Jul 2017 05:14:44 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:89:\"WPTavern: Jetpack Professional Plan Introduces Unlimited Access to 200+ Commercial 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:29:\"https://wptavern.com/?p=73055\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wptavern.com/jetpack-professional-plan-introduces-unlimited-access-to-200-commercial-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:3407:\"

Automattic has been teasing its plan to add commercial themes to Jetpack for several months after introducing theme installation for self-hosted users from WordPress.com. In March, the plugin opened up access to all of WordPress.com’s free themes via the Jetpack Manage interface. All signs pointed to Automattic developing the infrastructure to offer commercial themes via Jetpack upgrades. At that time, however, Jetpack team member Richard Muscat said that Automattic had “no immediate plans to sell themes at this time.”

\n

\n

Yesterday those subscribed to the Jetpack Announcements email were notified that commercial themes have landed in the Jetpack Professional plan, which is regularly priced at $24.92/month or $299/year. Customers will have unlimited access to more than 200 commercial themes that are already available on WordPress.com. Jetpack users on the free plan will see all the themes available in the WordPress.com theme browser with a prompt to upgrade for the ones that are commercial.

\n

\n

The announcement also noted that any themes users elect to use will be automatically backed up and regularly scanned for malware as part of the security services included in the package. For those who are running a multisite network, each site will need its own Jetpack Professional subscription to have access to the commercial themes.

\n

For years the WordPress community has speculated about what Automattic’s long game was for Jetpack, and many believed it was only a matter of time before the plugin started offering commercial upgrades. It was introduced to the WordPress world in 2011 as a way to provide feature parity between WordPress.com and self-hosted sites. The first version included just eight modules, but fellow plugin developer and entrepreneurs in the community were immediately aware of its commercial potential.

\n

In 2016, Automattic CEO Matt Mullenweg identified both Jetpack and WooCommerce as “multi-billion dollar opportunities” that could each individually be larger than WordPress.com. The plugin is now active on more than 3 million WordPress sites. Automattic’s aggressive commercialization of Jetpack in the past two years is the fulfillment of initial predictions about where the plugin was headed.

\n

The new commercial themes offering significantly raises the value of the Jetpack Professional plan, which was previously targeted at business users who require unlimited storage, Google Analytics, and additional SEO features. With the addition of unlimited use of 200+ themes, Automattic has expanded the Professional plan to be more compelling for non-business users who are simply interested in gaining access to a collection of professionally-supported themes.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 21:46:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:48:\"BuddyPress: BuddyPress 2.9.0 Release Candidate 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:32:\"https://buddypress.org/?p=267012\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://buddypress.org/2017/07/buddypress-2-9-0-release-candidate-1/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2980:\"

Today sees BP 2.9.0 move to The final testing phase Release Candidate 1.

\n

This is the last chance to test out this release and report back any issues found before final release in approximately two weeks time.

\n

Any issues found can be reported to our trac ticket home , or raised on the support forum.

\n

Amongst other improvements and fixes to look out for are:

\n\n

For a full list of commits see 2.9 tickets A full changelog will be available when we release the final version.

\n

You can download the plugin to test from the WP repo BP 2.9.0-RC1 or grab a copy from our SVN repo.

\n

A reminder to all theme developers that there are changes to template markup that could effect layouts and ask that they check their themes carefully, the changes are listed below along with changelog links; again any issues or problems please report as soon as possible to the BP trac or slack channel.

\n

Template changes

\n

In this release there are a number of improvements to templates that add a level of improved a11y performance and markup changes for better semantics & Standards.

\n

Theme authors may want to pay particular attention to changes to profile field visibility links and the profile field descriptions where significant markup changes are made that effect positioning of these elements – changesets for these are r11617 & r11618

\n

Nouveau – new template pack

\n

If you’re looking for Nouveau as we mentioned in the beta2 announcement we have delayed the release of this new template pack to ensure it receives as much code checking & refinement as possible and we’ll be looking to probably package this as it’s own release shortly after 2.9 is released.

\n

We thank you in advance for all testing and reports and it need not be mentioned but please don’t run Beta or RC releases in a production environment only on test installs.

\n

Regards,
\nThe BuddyPress team.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 12:57:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Hugo Ashmore\";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:102:\"WPTavern: CoKinetic Systems Pursues $100 Million GPL License Violation Case Against Panasonic Avionics\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72923\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:112:\"https://wptavern.com/cokinetic-systems-pursues-100-million-gpl-license-violation-case-against-panasonic-avionics\";s: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:7082:\"photo credit: Paper Plane(license)\n

Open source software has made its way into nearly every industry, but a recent open source security and risk analysis shows widespread license compliance risks, with 75% of the audited applications including GPL license conflicts. Although most violations are unintentional, there are some cases where companies do not comply with the license in order to block competitors from developing similar software.

\n

GPL enforcement doesn’t often lead to litigation. When it does, most other avenues of resolving the complaint have already been exhausted. A lawsuit in the air transport industry is currently bringing more attention to the gravity of not complying with open source software licensing requirements.

\n

CoKinetic Systems, a developer and manufacturer of in-flight entertainment (IFE) software, has filed a case against Panasonic Avionics that includes allegations of a fairly egregious breach of the GPL. The complaint alleges that Panasonic Avionics has monopolized the Panasonic IFE Software and Media Services Market by deliberately refusing to distribute the source code for its open-source Linux-based operating system:

\n

More specifically, Panasonic has built the Linux-Based Panasonic Core Software using the open-source Linux kernel, which is clearly governed by the GPL, together with Panasonic’s own modified Linux modules, which are likewise governed by the GPL.

\n

Indeed, Panasonic has itself affirmatively identified its own modified modules as being subject to the GPL, because the original Linux modules were specifically designed to generate warning messages if other code is linked with or otherwise combined with the Linux modules that are not licensed under the GPL. To suppress these warnings, Panasonic willfully acted to insert code into its own modules to indicate that they were licensed under the GPL.

\n

Panasonic has incorporated a massive amount of open source modules, programs, and libraries into the Linux-Based Panasonic Core Software, without distributing notices or source code to the Linux-Based Panasonic Core Software, or even to any part of it…By deliberately refusing to distribute the source code to the Linux-Based Panasonic Core Software in accordance with its GPL obligations, Panasonic intentionally deprives competitors in the market from having the ability to develop software that can access the basic features and capabilities of Panasonic IFE Hardware.

\n

CoKinetic Systems contends that Panasonic’s refusal to distribute its source code voids its GPL license and “potentially exposes Panasonic to billions of dollars in statutory damages for hundreds of thousands of hardware installations that willfully infringe copyrights belonging to hundreds or even thousands of software developers that freely contributed source code to Linux.”

\n

Furthermore, the complaint details how competitors have to rely on Panasonic’s APIs in order to offer software services to airlines using Panasonic’s IFE hardware, because they do not have access to the source code for the Linux-based core software. CoKinetic claims that Panasonic also deliberately blocks competitor products by its selective distribution of its APIs, resulting in stifled industry innovation and monopoly control over the Panasonic IFE Software and Media Services Market.

\n

Perhaps the worst and most grave allegation in the complaint is that, in addition to locking up the source code and doling out access to the APIs, Panasonic also maliciously sabotaged its own APIs in order to give the appearance that it is the only reliable software service provider for its hardware, which CoKinetic claims is inferior and sold at monopolistic prices.

\n

Panasonic also is able to use its control over the Linux-Based Panasonic Core Software in order to make ongoing, undisclosed, and often malicious modifications to its source code, deliberately “breaking” Panasonic’s own APIs in order to purposely and maliciously sabotage the performance of third-party software products that Panasonic deems a competitive threat — particularly CoKinetic software.

\n

In the introduction to the case, CoKinetic cites a litany of anti-competitive conduct the company has engaged in over the past decade before detailing the current allegations. The case is not purely an open source license dispute, as the plaintiff also alleges that Panasonic abused regulatory processes, engaged in acts of corporate espionage, defamed CoKinetic, paid commercial bribes, and employed unlawful means to monopolize the Panasonic IFE Software and Media Services Market.

\n

CoKinetic is seeking compensatory damages for Panasonic’s GPL ongoing GPL breaches. The specific amount would be determined at the trial but the company believes it to be in excess of $100 million. The company also wants the court to compel Panasonic to publicly disclose and distribute the source code.

\n

This isn’t a case where distributing the source code is just a small sticking point or just a matter of principle. It has the potential to open up the IFE industry for faster progress and greater innovation. Many reading this article have undoubtedly used Panasonic’s IFE products when flying with the company’s customers, which include Emirates Airlines, Delta Air Lines, Virgin America, and United Airlines. With the source code available, airline customers could remove Panasonic’s software from their IFE hardware and replace it with their own software solutions.

\n

The complaint, which was filed in the Southern District of New York in March, demands a jury trial. An initial pre-trial conference was held in May, but the case has been slow moving. The Court gave a deadline for the Defendant to file its motion to dismiss, but deadlines have since been extended. The Court also strongly recommended that the two parties retain a private mediator but it’s not clear how outside mediation could solve such a far-reaching matter that impacts so many vendors. Additional documents are due over the next few months, so it will be some time before there are updates on the progress of the case.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 04:39: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:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:45:\"WPTavern: AJ Morris Acquires iThemes Exchange\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73071\";s:7:\"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://wptavern.com/aj-morris-acquires-ithemes-exchange\";s: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:3545:\"

In 2013, iThemes released Exchange, an e-commerce platform that aimed to make selling online as simple as possible. Today, the company announced that AJ Morris, Product Manager at Liquid Web, has taken over the project.

\n

“When approached about taking over iThemes Exchange early this year, we wanted to be sure the project and our customers went into very competent hands, someone who will love and care for them as much as we do,” Cory Miller, founder of iThemes, said.

\n

“Having spent four and a half years investing in the project and in you and your success, we did not take this lightly.

\n

“After numerous conversations over the past several months, we believe the best home for Exchange is with ExchangeWP LLC led by AJ Morris.”

\n

Everything iThemes Exchange related will transition to ExchangeWP.com. Toolkit, Plugin Suite, Exchange Pro Pack, and iThemes Exchange Add-on customers will be given accounts for free support and upgrades through August 2018 at ExchangeWP.com.

\n

Beginning today, customers will no longer be able to purchase Exchange or its add-ons through iThemes as the company transfers licenses and products to ExchangeWP. However, iThemes will continue to provide customer support until the transition is completed, expected to happen in early August.

\n

Morris says he’ll continue to focus on making e-commerce simple and will provide regular updates to customers to provide insight into what goes into transition a product from one company to another and where the product is heading.

\n

“These days, it’s very easy to get WordPress up and running so you can start blogging,” Morris said. “But when you want to add e-commerce to the mix, it’s a bit different.”

\n

“With big players like WooCommerce out there, it becomes too much too quickly for the average content producer to get their store up and running.

\n

“Exchange is going to continue focusing on the independent publishers that want to keep the revenue they can, while providing a simplistic experience in an easy-to-use e-commerce plugin that will help get their stores online quickly.”

\n

Allowing Morris to take over the project frees up resources for iThemes to focus on three of its flagship products; BackupBuddy, iThemes Security, and iThemes Sync. In addition to their core products, the company says it will soon release a new project.

\n

“My job as CEO is to be a steward of the time and resources we have at iThemes in order to serve you best,” Miller said.

\n

“We’ve realized for a while that it was past time for us to refocus our finite resources on the projects that have the most growth and potential for our company and you.

\n

“That meant we either needed to find a new home for Exchange or sunset the project. I’m thankful we didn’t have to do the latter.”

\n

Morris is a long-time member of the WordPress community and has spoken at several WordCamps. With Morris taking over the reigns, existing customers won’t have to worry about finding a replacement.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jul 2017 01:00:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:25;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"Akismet: Akismet WordPress Plugin 3.3.3 Now Available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"http://blog.akismet.com/?p=1953\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://blog.akismet.com/2017/07/13/akismet-wordpress-plugin-3-3-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1413:\"

Version 3.3.3 of the Akismet plugin for WordPress is now available.

\n

For a full list of the changes in this release, see the revision log, but here are some notable fixes:

\n\n

To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins directory.


\"\" \"\"\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jul 2017 22:00: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:17:\"Christopher Finke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:68:\"WPTavern: WordPress.com Introduces Scheduling for Social Media Posts\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73026\";s:7:\"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:\"https://wptavern.com/wordpress-com-introduces-scheduling-for-social-media-posts\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2916:\"

WordPress.com is venturing into the realm of social media management applications with its latest feature that allows users to schedule Facebook, Twitter, and LinkedIn updates for individual posts. This goes beyond the basic Publicize functionality that automatically shares posts to connected accounts as soon as they are published, giving users the ability to automate their content marketing to social networks for the most optimal time for sharing.

\n

\n

It’s difficult to know how a post will appear on social networks once it has automatically been shared, which is one reason why many people choose to manually share a post for the best presentation. You want to ensure that the right thumbnail will show up with a message customized for each network’s particular audience. The new social scheduling feature on WordPress.com includes a built-in preview screen so users can see what the post will look like once it is shared to the network and then make any necessary tweaks.

\n

\n

Scheduling social media posts is available on WordPress.com for Premium and Business plan users and for Jetpack Professional and Premium users. On the Premium plan level, which comes in at ~$9/month, users pay less than they would for scheduling apps like Buffer, Hootsuite, or Sprout Social while also getting access to more commercial WordPress features.

\n

To truly become a realistic replacement for these types of social media marketing apps, WordPress.com would need to offer better analytics tied into the new sharing feature to show how posts are performing at different times and networks. Although WordPress.com allows for unlimited scheduling and users, it would also need to allow sharing to more networks to be more competitive against these apps. For users who don’t need all of that data but just want the scheduling feature, a paid Jetpack or WordPress.com plan is a more affordable option.

\n

Several other self-hosted WordPress plugins already offer scheduling social media posts for free and some even integrate the social accounts with Google Analytics. The addition of this feature to Jetpack commercial plans may not be as compelling for self-hosted users who can already find this for free, but it adds value for existing Jetpack customers who may now be able to replace a plugin or third-party service.

\n
\";s: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, 13 Jul 2017 19:59:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:62:\"WPTavern: WPWeekly Episode 281 – In Memory of Jesse Petersen\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=73045&preview=true&preview_id=73045\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wptavern.com/wpweekly-episode-281-in-memory-of-jesse-petersen\";s: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:2501:\"

In this episode, John James Jacoby and I are joined by Ben Meredith. Over the past few years, Ben has established a friendly and professional relationship with Jesse Petersen, who passed away due to complications from Cystic Fibrosis.

\n

Ben shares his unique perspective on who Petersen was as a person and describes the challenges of taking over his business. We emphasized how important it is to create a file with passwords and other login information to help appointed people access a person’s digital presence. We also discuss if saying a person lost their battle with an illness is a negative thing to say.

\n

To close out the show, we talk about net neutrality, 10up acquiring Lift UX, and Let’s Encrypt offering wildcard certificates in 2018.

\n

Stories Discussed:

\n

Automattic Releases Net Neutrality WordPress Plugin Ahead of July 12 Protest
\n10up Acquires Lift UX
\nLet’s Encrypt Passes 100 Million Certificates Issued, Will Offer Wildcard Certificates in January 2018

\n

Picks of the Week:

\n

Newlungsfor.me is a place to read about Jesse’s battle with Cystic Fibrosis along with CFfatboy.com.

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, July 19th 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #281:
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jul 2017 22:00:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:28;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: Sustain Event Draws 100 Attendees to Discuss the Sustainability of Open Source Software\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=73014\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/sustain-event-draws-100-attendees-to-discuss-the-sustainability-of-open-source-software\";s: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:5136:\"

\n

More than 100 open source project maintainers and industry leaders gathered at the GitHub headquarters in San Francisco last month to discuss the long-term sustainability of open source software. The Sustain event, put on by a relatively new organization called SustainOSS, did not follow a traditional conference format with talks and keynotes but was intentionally left unstructured to foster open discussion.

\n

Organizers expected 50 attendees but ended up with double their estimates. The $50 ticket price covered day care, travel assistance, food, and other miscellaneous event costs. Attendees shared insights from their diverse backgrounds and participated in collaborative working sessions and various discussions facilitated by organizers.

\n
\n

Defining a common unified theory of open source sustainability is super hard! #sustainoss pic.twitter.com/2PznN2oZGM

\n

— Lou Huang (@saikofish) June 19, 2017

\n

\n

Co-organizer Alanna Irving shared in her wrap-up post how the team used Open Collective to make the event’s finances transparent and offer payment options for participants and sponsors. The service has recently added a new feature that allows collectives to communicate event info and sell tickets.

\n

Representatives from large tech companies attended the event, as well as contributors from various open source projects and foundations, including Google, Amazon, Paypal, Airbnb, Red Hat, JS Foundation, Linux Foundation, Apache Foundation, npm, FontAwesome, GulpJS, and more. Irving published a few insights from the discucssions that she and her colleagues are applying to their work at Open Collective:

\n\n

On the day following the event, SustainOSS organizers tweeted out a link to a new forum on GitHub for discussing open source sustainability. Proposed topics include fundraising, governance, contributor retention, productivity, and managing corporate relationships. It was created to offer a safe place for open source sustainers to collaborate with each other in the open and contributors have already submitted some practical ideas for discussion, such as adding a standardized FUNDING or SUSTAINABILITY file to repositories.

\n
\n

Busy day, got a lot done. Stay tuned. #sustainoss #sustain17 pic.twitter.com/CtWs82FXAn

\n

— SustainOSS (@SustainOSS) June 20, 2017

\n

\n

Sustain was inspired by inspired by the Maintainerati event held in London in May 2017. The similarly unstructured event brought together open source maintainers who share similar challenges. GitHub also hosted the Wontfix Cabal event at its San Francisco headquarters in February, which highlighted some of the difficulties related to maintaining OSS projects. Events focused on maintaining and funding OSS have been popping up in the past two years, as more people become aware that open source infrastructure has a critical sustainability problem.

\n

The SustainOSS organizers will be releasing a more detailed article on the event soon. They are also open to considering hosting other Sustain events in different locations. Follow @SustainOSS on Twitter for the latest updates.

\n
\";s: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, 12 Jul 2017 20:38: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: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:89:\"HeroPress: How I found myself in WordPress – Как я нашел себя в 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:56:\"https://heropress.com/?post_type=heropress-essays&p=1962\";s:7:\"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:128:\"https://heropress.com/essays/i-found-myself-in-wordpress/?utm_source=rss&utm_medium=rss&utm_campaign=i-found-myself-in-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:22562:\"\"Pull

Это эссе также доступно на русском языке.

\n

About Russia and familiarity with technologies

\n

Russia is a very large and very different country. The basic population, as well as technological development, is concentrated in the central part of the country, in “city-states”: Moscow and St. Petersburg. Other regions are much less developed: lower wages, worse and more expensive infrastructure, fewer IT-vacancies and activities.

\n

I was born and grew up in a remote part of Russia – in the Far East, in one of the industrial cities, which is located in 7 time zones and 9000 kilometers from Moscow. The Internet, like other technologies, reached there with a significant delay and for a lot of money (unlimited Internet at a speed of 64 kb/s appeared only in 2007), Therefore, at first, the basics of site building had to be learned in snatches with the help of dial-up.

\n

The first site I did in school. It was built using simple HTML and CSS. But even in this form, it was very impressive and exciting. Then such sites were popular and periodically on the Internet I met guys of my age who like me comprehended the science of site building.
\nI was lucky to find a like-minded person, with whom we were able to develop together for some time and even launch a joint website.
\n\"\"

\n

University and start of work

\n

Admission to the computer faculty of the university allowed to more specifically address the issues of web development: to learn PHP and MySQL, to get acquainted with a couple of CMS and to make my first blog on WordPress :). As far as I remember, the blog worked on some WordPress assembly using version 2.9. If you count from that moment, it turns out that I somehow have been working with WordPress for almost 8 years.

\n

In those days, ru.wordpress.org was just born and there was no main site on the Russian-language Internet. It was a time of amateur assemblies, amateur translations and even alternatives of WordPress, aimed to the Russian segment of the Internet.

\n

By the will of fate, my first place of work related to website development was the web studio that used Joomla and Drupal. Then there were a few more places of work, during which time WordPress then turned into the main working tool, then returned to the category of extra work and hobbies.

\n

The turning point was the decision to move to Moscow and a full transition to WordPress in freelance format.

\n

Moving to Moscow

\n

The scenario of moving to Moscow or St. Petersburg is quite popular among IT specialists of my native region. This is a great chance to find interesting and highly paid job, get acquainted with a lot of IT specialists, including narrow ones, and develop in the area of interest.

\n

In Moscow, I moved with remote work and I do not have personal experience of employment in this city, but my wife and most of the acquaintances were satisfied with the options found.

\n

After about six months of living in Moscow, I was even more thirsty for adventure — to become a freelancer and completely concentrate on WordPress. The ability to plan time independently gives additional space for maneuvers and time for reflection. In my case, this led to an increase in activity in the WordPress community.

\n

Participate in the WordPress community

\n

Actively participate in the life of the community, I started about 1.5 years ago. Initially, these were the replies at the support forum, then the development of my plugins, after which I decided to try myself in translating the extensions into Russian and recording training videos for Russian-speaking users.

\n

Over time, it turned into a kind of hobby or even a way of life. Every day I read a lot of posts from users on the support forums and try to help resolve their issues, check and correct the added translation lines, periodically record and post training videos.

\n

Communication with users is very helpful. You are one of the first to learn about the problems and ways to solve them, you can quickly correct some incorrect or incorrect translation. Also, over time, a list of popular questions accumulates, which can be turned into training articles and videos. In turn, the creation of articles and videos helps to structure knowledge and understand the details.

\n

On ru.wordpress.org a great team of moderators and translation editors has gathered. We regularly communicate in Slack, some I meet on WordCamp.

\n

\"Denis

\n

In November 2016 I took part in the Global Day of Translation 2. It was an unusual experience: broadcasting from around the world, feeling the scale of what was happening and the excitement of the translation. At that time we took 6th place as the most active locale and attracted 7 new translators.

\n

Meetups and WordCamp

\n

In Russia there are not so many cities where WordPress-meetups are held, and WordCamp is held only in Moscow. But despite all this, these events are a great opportunity to be among WordPress lovers, to see live people with whom I have only spoken on the network before, and just feel the spirit of WordPress :).

\n

\"Three

\n

This year I plan to visit WordCamp Moscow for the third time. I visit WordCamp as a participant, but I hope someday I will find a topic close to me and I will decide to apply for a presentation :). I think it will be interesting.

\n

Conclusion

\n

At the moment I’m a full-time freelancer. This allows me to quite well combine work and activities in the community. I like to share knowledge and make WordPress more accessible for Russian users.

\n

Many resources of WordPress are dominated by English, and some, for example, as developer.wordpress.org or “Handbook” are not available for localization. I hope, in the future this will change and we will be able to expand our activities.

\n

In any case, WordPress remains the place where you can find yourself and help make life a little better for yourself and the rest of the participants.

\n
\n

Как я нашел себя в WordPress

\n

Про Россию и знакомство с технологиями

\n

Россия очень большая и очень разная страна. Основное население, как и технологическое развитие, сосредоточено в центральной части страны, в “городах-государствах”: Москве и Санкт-Петербурге. Остальные регионы развиты значительно слабее: ниже зарплаты, хуже и дороже инфраструктура, меньшее количество IT-вакансий и мероприятий.

\n

Я родился и вырос в отдаленной части России — на Дальнем Востоке, в одном из промышленных городов, который расположен в 7 часовых поясах и 9000 километров от Москвы. Интернет, как и другие технологии, доходили туда с существенным опозданием и за большие деньги (безлимитный интернет на скорости 64 кб/сек появился только в 2007 году), поэтому, по началу, азы сайтостроения приходилось познавать урывками с помощью dial-up.

\n

Первый сайт я сделал ещё в школе. Он был построен на простейшем HTML и CSS. Но даже в таком виде, это было очень впечатляюще и захватывающе. Тогда такие сайты были популярны и, периодически на просторах интернета, я встречал ребят моего возраста, которые, как и я, постигали науку сайтостроения.

\n

Мне повезло найти единомышленника, с которым мы смогли некоторое время вместе развиваться и даже запустить совместный сайт.

\n

\"Very

\n

Университет и начало работы

\n

Поступление на компьютерный факультет университета позволило более предметно заняться вопросами веб-разработки: изучить PHP и MySQL, познакомиться с парой CMS и завести свой первый блог на WordPress :). Насколько я помню, блог работал на какой-то сборке WordPress, использующей версию 2.9. Если вести отсчет с того момента, то получается, что я так или иначе работаю с WordPress уже почти 8 лет.

\n

В те времена ru.wordpress.org только зарождался и в русскоязычном интернете не было какой-то основной площадки. Это было время любительских сборок, любительских переводов и даже альтернатив WordPress, ориентированных на русский сегмент интернета.

\n

Волею судеб, моим первым местом работы, связанным с разработкой сайтов, стала веб-студия, использовавшая Joomla и Drupal. Затем было ещё несколько мест работы, в течение которых WordPress то превращалась в основной рабочий инструмент, то возвращалась в разряд дополнительной работы и хобби.

\n

Переломным моментом стало решение о переезде в Москву и полный переход на WordPress в фриланс-формате.

\n

Переезд в Москву

\n

Сценарий переезда в Москву или Санкт-Петербург достаточно популярен среди IT-специалистов моего родного региона. Это отличный шанс найти интересную и высокооплачиваемую работу, познакомится со множеством IT-специалистов, в том числе узких, и развиться в интересующей области.

\n

В Москву я переезжал вместе с удаленной работой и у меня нет личного опыта трудоустройства в этом городе, но моя жена и большинство знакомых остались довольны найденными вариантами.

\n

Примерно через полгода проживания в Москве, меня обуздала ещё большая жажда приключений — стать фрилансером и полностью сосредоточиться на WordPress. Возможность самостоятельно планировать время дает дополнительное пространство для маневров и время на размышления. В моем случае, это привело к увеличению активности в сообществе WordPress.

\n

Участие в сообществе WordPress

\n

Активно участвовать в жизни сообщества я начал примерно 1.5 года назад. Вначале это были ответы на форуме поддержки, затем разработка своих плагинов, после чего я решил попробовать себя в переводе расширений на русский язык и записи обучающих видео для русскоязычных пользователей.

\n

Со временем это превратилось в некое хобби или даже образ жизни. Каждый день я читаю множество сообщений от пользователей на форумах поддержки и пытаюсь помочь решить их вопросы, проверяю и корректирую добавленные строки перевода, периодически записываю и выкладываю обучающие ролики.

\n

Общение с пользователями очень помогает. Ты одним из первых узнаешь о проблемах и способах их решения, можешь оперативно исправить какой-то неверный или некорректный перевод. Также, со временем накапливается список популярных вопросов, которые можно превращать в обучающие статьи и ролики. В свою очередь, создание статей и видео помогает структурировать знания и разобраться в деталях.

\n

На ru.wordpress.org собралась отличная команда модераторов и редакторов переводов. Мы регулярно общаемся в Slack, некоторых я встречаю на WordCamp.

\n

\"Denis

\n

В ноябре 2016 я принимал участвовали в Глобальном дне перевода 2. Это был необычный опыт: трансляции со всего света, ощущение масштабности происходящего и азарта перевода. В тот раз мы заняли 6 место как самый активный язык и привлекли 7 новых переводчиков.

\n

Митапы и WordCamp

\n

В России не так много городов, где проводятся WordPress-митапы, а WordCamp проводится только в Москве. Но не смотря на всё это, данные мероприятия — отличная возможность побыть среди любителей WordPress, увидеть в живую людей, с которыми до этого общался только по сети, и просто почувствовать дух WordPress :).

\n

\"\"

\n

В этом году я планирую посетить WordCamp Moscow в третий раз. Я посещаю WordCamp как участник, но надеюсь когда-нибудь найду близкую мне тему и решусь подать заявку на выступление :). Я думаю, это будет интересно.

\n

Заключение

\n

На данный момент я — фул-тайм фрилансер. Это позволяет мне достаточно неплохо совмещать работу и деятельность в сообществе. Мне нравится делиться знаниями и делать WordPress доступнее для русскоязычных пользователей

\n

На многих ресурсах WordPress преобладает английский язык, а некоторые, например, как developer.wordpress.org/ или “Handbook” вовсе недоступны для локализации. Надеюсь, в будущем это изменится и мы сможем расширить свою деятельность.

\n

В любом случае, WordPress остается тем местом, где можно найти себя и помочь сделать его чуточку лучше для себя и остальных участников.

\n

участник

\n

\"Denis

\n

 

\n

 

\n

 

\n

 

\n

 

\n

 

\n

 

\n

 

\n

Денис Янчевский

\n\n

The post How I found myself in WordPress – Как я нашел себя в WordPress appeared first on HeroPress.

\";s: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, 12 Jul 2017 12:00:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"Denis Yanchevskiy\";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:86:\"WPTavern: Automattic Releases Net Neutrality WordPress Plugin Ahead of July 12 Protest\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72930\";s:7:\"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:97:\"https://wptavern.com/automattic-releases-net-neutrality-wordpress-plugin-ahead-of-july-12-protest\";s: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:2074:\"

Automattic announced its intent to protest the FCC’s attack on net neutrality today by making a way for the millions of WordPress.com users to join in. The company’s logo has been listed on the Save Net Neutrality event website for some time but it had yet to announce how it would be participating. WordPress.com users are encouraged to send a message to the FCC and also enable the Fight for Net Neutrality Plugin via the dashboard Settings screen.

\n

The plugin is open source and available to self-hosted users on WordPress.org. Unlike the existing plugins that support the event on July 12 by presenting visitors with a banner to raise awareness, Automattic’s plugin simulates what life might be like in the “slow lane” if the FCC abandons the principle of net neutrality. It replaces a few of the posts on your site with a “Still Loading” spinner. This plugin doesn’t seem to offer a way to test it ahead of the event, but it essentially displays a message at the bottom of your website and slows down some of your posts.

\n

\n

The plugin will automatically be disabled after the event has concluded, so both WordPress.com and self-hosted users do not have to worry about turning it off and can remove it later. If you are uneasy about slowing down some of your posts as part of the protest and feel more comfortable displaying a modal or a widget, check out the Internet Defense League Cat Signal or the Fight for the Future Alerts plugins as alternatives.

\n
\";s: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, 12 Jul 2017 05:07: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:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:31;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: VersionPress 4.0 Beta Adds User-Editable Location for Plugin Definitions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72939\";s:7:\"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:\"https://wptavern.com/versionpress-4-0-beta-adds-user-editable-location-for-plugin-definitions\";s: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:2944:\"

VersionPress 4.0 beta is available for testing. It includes a number of improvements, most notably, the ability to load plugin definitions from a user-defined location within the wp-content directory.

\n

Plugin definitions are files used to understand data, actions, shortcodes, and other things plugins do in order to automatically provide version control for them.

\n

According to Borek Bernard, co-founder of VersionPress:

\n

If you create a folder WP_CONTENT_DIR/.versionpress/plugins/woocommerce and put definition files like schema.yml or actions.yml there, VersionPress will use and actually prefer it over the bundled definitions if they exist.

\nUser Defined Location of Plugin Definition File\n

Support for WooCommerce and Jetpack are included in 4.0 Beta 1. VersionPress will automatically detect the definition file as long as each plugin has a .versionpress folder in it.

\n

With the release of 4.0 Beta, Bernard says a repository containing plugin definitions is next on the list and is encouraging plugin authors to contribute to the project.

\n

“The final step is to have an online repository of the definitions,” Bernard said. “It will be open to anyone to contribute, not just plugin authors, and used by VersionPress transparently.”

\n

For insight on how to create definitions, developers can look at WordPress core and WooCommerce for real-world examples.

\n

Other major changes include full support for WordPress 4.7 and 4.8, adoption of GitHub projects to help manage the development process, and a number of bugs fixed.

\n

Developers and users can download 4.0 Beta from GitHub. Users are encouraged to test the plugin in a staging environment as it’s not ready to be used on live sites. If you encounter an error, you can report it by creating a new Issue request on the project’s GitHub page.

\n
\";s: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, 12 Jul 2017 04:26:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:31:\"WPTavern: 10up Acquires Lift UX\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72917\";s:7:\"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://wptavern.com/10up-acquires-lift-ux\";s: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:4294:\"

\n

10up, a leading WordPress design and development agency, has acquired Lift UX, a smaller user experience design-driven agency that will bolster the company’s existing Experience design team. Lift founders Chris Wallace and Brad Miller will join 10up’s 120+ person distributed team, along with Lift’s director of technology, Christian Chung, and front-end developer Anthony Garand.

\n

10up is acquiring the Lift UX brand, hiring four team members, and will also take possession of RemoteJobs.com, which will continue operating independently as a remote job board. The Lift UX brand will be dissolved and clients and projects are in the process of transitioning over to 10up.

\n

“We were always looking for agencies to partner with and when I reached out to 10up I was looking to build a relationship to help work on UX design projects,” Miller said. “10up has a strong engineering background and I felt like having them as a partner would be huge for our agency. Jake and I quickly realized that Lift UX and 10up had so many similar processes that it sounded like our two companies were the same but just different in size.”

\n

With similar expertise serving large clients in the WordPress space, the two companies were bound to end up competing on different projects, which happened during the course of their conversations spanning a year leading up to the deal. Miller said 10up founder Jake Goldman proposed a merger/acquisition type of approach.

\n

“I ended up speaking to them off and on for the next couple of weeks and things got pretty serious when we were competing for some projects,” Miller said. “I was of course flattered by the offer. Jake and John were awesome. We enjoyed our conversations and decided to do an onsite to discuss things in more detail. They made an offer after our onsite and Chris and I decided to accept it.”

\n

In 10up’s announcement, Goldman said it “takes a special kind of chemistry and alignment for a deal like this to work.” The company’s acquisition of Lift is one of the biggest design-driven acquisitions in the WordPress ecosystem in awhile.

\n

“Adding more experience design expertise to our company DNA enhances our empathy and ability to collaborate with design partners in an era of interactive, responsive design where divisions between ‘design’ and ‘engineering’ have eroded,” Goldman said.

\n

Miller, who has worked with Wallace to build Lift into a top-notch design and user experience agency, said that securing design talent is a challenge in the industry. 10up adding a fellow competitor to its team is a stretegic move when design talent is in short supply.

\n

“I think it’s certainly hard to find quality talent that’s interested in a full time position,” Miller said. “There are some amazing designers out there but a lot of them are contractors/freelancers. 10up wanted to find a team that had a big focus on quality design and UX. It didn’t hurt that we were big on WordPress either.”

\n

Miller and Wallace founded Lift UX in 2009 and will be closing out a chapter of their entrepreneurial lives as the brand dissolves into 10up.

\n

“Basically we’ll fade into the 10up brand bringing along our team, portfolio, accolades, and ultimately our personality,” Miller said.

\n

Wallace said closing out this chapter is “definitely bittersweet,” but the team is excited to transition into 10up.

\n

“As a 6-7 person agency, we were all constantly being pulled in a million different directions,” Wallace said. “Joining 10up allows us to focus on our individual areas of specialization and excel in each. I love many aspects of entrepreneurship and small agency ownership but the idea of focusing on the success of the experience design team at 10up is something I am looking forward to.”

\n
\";s: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, 11 Jul 2017 22:02: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: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:31:\"Donncha: Thank you Translators!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:28:\"https://odd.blog/?p=89500320\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:50:\"https://odd.blog/2017/07/11/thank-you-translators/\";s: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:1384:\"

Well, well. WP Super Cache translations are coming along well. 100% of strings in the development version are translated into Canadian English and Romanian! (That might change over the next few days as I have a couple of UI changes in mind, sorry!)

\n

Other languages like Persian, Japanese, Spanish, Russian and Italian are roaring along and sometimes only need a handful of words or sentences translated to hit that magic 100% too. The next version of the plugin will grab translations from WordPress.org if they’re available which is awesome for users around the world. We’re still shipping translation files but I think the release after that may ship without and rely entirely on the up-to-date online translations.

\n

So, thank you so much to the translators. Code is nigh on useless if the user and developer don’t speak the same language and the interface is incomprehensible. WP Super Cache has lots of technical language which must be a pain to translate. Your work is invaluable!

\n

Mulțumesc! متشکرم! ありがとうございました!¡Gracias! Спасибо! Grazie! Hvala ti! 谢谢!Vielen Dank!

\n\n

Related Posts

\n

Source

\";s: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, 11 Jul 2017 10:44:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:90:\"WPTavern: Interview with WordCamp US 2017 Organizers Dustin Meza and Laura Byrne-Cristiano\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=72903&preview=true&preview_id=72903\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://wptavern.com/interview-with-wordcamp-us-2017-organizers-dustin-meza-and-laura-byrne-cristiano\";s: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:2252:\"

While at WordCamp Europe I had the opportunity to interview Dustin Meza, lead organizer of WordCamp US 2017, and Laura Byrne-Cristiano, who is part of the marketing team for the event. The two are members of a 20-person team of organizers who will welcome an estimated 2,500 attendees to Nashville in December.

\n

Although the maximum capacity of the Music City Center venue is much higher than what is required by WordCamp US, the organizers want to make judicious use of the event's resources to put on the best possible event for those who make the effort to attend.

\n

\"At the end of the day, it's going to be the right size for the event,\" Byrne-Cristiano said. \"You could say, 'Hey, we want 10,000 people, but that's not the right size for the event. The right size is probably somewhere between 2,000 and 2,500. The venue can do more than that, but I don't know that that's the main goal. Bigger isn't always better. Your main goal is the best event and quality for the people who are already there.\"

\n

Meza said he considers WordCamp US to be the premier event for North America and that it is there to represent the communities located in this area. He couldn't share the full details of the unique things they are working on, but organizers plan to display and exhibit more information about the the various WordPress communities throughout North America.

\n

In the interview below, Meza and Byrne-Cristiano share a little bit about why they believe Nashville was selected and how welcoming the city is for people from different cultures. 

\n

\"No matter where in the world you are coming from, there's a place for you at WordCamp US,\" Byrne-Cristiano said.

\n

\"This is, by far, the best technology community I have ever been apart of, seeing how much everyone involved embraces new people – to me that is the big reason why I got involved,\" Meza said. \"I want to give this community the best event that we possibly can.\"

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jul 2017 02: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:\"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: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:54:\"WPTavern: WPCampus 2017 Will Be Streamed Live for Free\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72896\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:65:\"https://wptavern.com/wpcampus-2017-will-be-streamed-live-for-free\";s: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:1020:\"

WPCampus, a conference focused on using WordPress in higher education, takes place this Friday and Saturday in Buffalo, NY. If you’re unable to attend the event, WPCampus will be live streaming the sessions for free.

\n

Visit the streaming page on July 14th and 15th where viewers can choose between three tracks of sessions to watch. Viewers can also hang out in the #discuss-wpc17 Slack channel to discuss sessions with other people.

\n

Organizers are encouraging viewers to have watch parties at WordPress meetups and campuses. Sessions will be recorded and made available online at the end of the event. The stream starts on Friday, July 14th at 9 AM Eastern.

\n
\";s: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, 10 Jul 2017 21:49: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:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:36;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:64:\"WPTavern: Episodes 271-280 of WordPress Weekly are Now Available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72884\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/episodes-271-280-of-wordpress-weekly-are-now-available\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1011:\"

In the past two weeks, listeners have reported that recent episodes of WordPress Weekly are not available for download through Apple’s Podcasting app, Stitcher, and other applications.

\nPodcast Download Error\n

I use Vid2MP3 to convert YouTube videos into MP3 files. Starting with episode 271, there was an error in the conversion process. It was difficult to diagnose since the MP3 played fine in some browsers and applications but not in others.

\n

I have reconverted the affected episodes using a different service and uploaded the new files to the site. I confirmed that the episodes are accessible in Apple’s Podcasting application. If you still encounter a problem downloading these episodes, please leave a note in the comments along with which podcasting app you’re using. Thanks to all who reported the error and for listening to the show.

\n
\";s: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, 10 Jul 2017 20:19: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: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:131:\"WPTavern: Automattic Joins Amazon, GitHub, Mozilla, reddit, and Twitter in July 12 Protest Against FCC’s Attack on Net Neutrality\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72799\";s:7:\"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:135:\"https://wptavern.com/automattic-joins-amazon-github-mozilla-reddit-and-twitter-in-july-12-protest-against-fccs-attack-on-net-neutrality\";s: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:3713:\"

\n

Major internet websites, companies, and organizations are banding together on Wednesday, July 12, to protest the FCC’s attack on net neutrality. These include Amazon, GitHub, Kickstarter, Vimeo, reddit, Mozilla, Twitter, Etsy, Spotify, Netflix, and many others. Automattic is joining these tech companies in the protest, as it has several times in the past, including the Internet Slowdown event in September 2014. The company also reaffirmed its commitment to net neutrality in 2015 by filing an amicus brief with the Court of Appeals for the DC Circuit in the case of United States Telecom Assn. v. FCC, joined by Medium, Reddit, Squarespace, Twitter, and Yelp.

\n

Net neutrality is the principle that ensures people can communicate freely online by prohibiting Internet Service Providers (ISPs) and government entities from favoring, blocking, or throttling certain websites, or charging fees for premium content delivery. It guarantees individuals have free to access all content and applications, and forbids ISPs from discriminating against or prioritizing certain users, equipment, or types of content. Vimeo created a handy video to illustrate the importance of defending net neutrality:

\n
\n

Net neutrality is once again under attack as the FCC is planning to remove the Title II (common carrier) protections established during the Obama administration.

\n

How to Join the Protest

\n

Self-hosted WordPress site owners who want to participate in the Internet-Wide Day of Action to Save Net Neutrality on July 12 can do so by installing the Internet Defense League Cat Signal plugin or the Fight for the Future Alerts plugin. Both support the upcoming Save Net Neutrality event and are based on the official Fight for the Future widget for the campaign.

\n

The widget will not display until July 12, so you can add a plugin ahead of time. If you want to test it to see what it will look like on the day of action, you can append #ALWAYS_SHOW_BFTN_WIDGET to your site URL after installing one of the plugins. See an example here: https://wptavern.com/#ALWAYS_SHOW_BFTN_WIDGET

\n

\n

The alert urges visitors to contact Congress and the FCC through the provided form. It can be displayed as a banner at the top of the page or as a modal (see example above).

\n

Automattic may also be planning a way for WordPress.com users to opt-in to participate. We’ll update the post if that information becomes available.

\n

Update: Automattic has since created a Net Neutrality plugin for WordPress.com and self-hosted users who want to join the protest.

\n
\";s: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, 10 Jul 2017 18:12:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"WPTavern: Let’s Encrypt Passes 100 Million Certificates Issued, Will Offer Wildcard Certificates in January 2018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72805\";s:7:\"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:\"https://wptavern.com/lets-encrypt-passes-100-million-certificates-issued-will-offer-wildcard-certificates-in-january-2018\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2660:\"photo credit: Chris Anderson\n

Let’s Encrypt, the free and open certificate authority that launched in 2016, has issued more than 100 million certificates as of June 2017 and is currently securing 47 million domains. Earlier this year, the web passed a major milestone of getting more than 50% of traffic encrypted. Let’s Encrypt has been a major contributor to that percentage growing to nearly 58%.

\n

“When Let’s Encrypt’s service first became available, less than 40% of page loads on the Web used HTTPS,” ISRG Executive Director Josh Aas said. “It took the Web 20 years to get to that point. In the 19 months since we launched, encrypted page loads have gone up by 18%, to nearly 58%. That’s an incredible rate of change for the Web.”

\n

Aas also announced that wildcard certificates are coming to Let’s Encrypt in 2018. Wildcard certificates allow a site to secure an unlimited number of subdomains with the same certificate.

\n

Currently, the process to get Let’s Encrypt working on a WordPress multisite installation is much more complicated than adding a certificate for a single domain. The WP Encrypt plugin claims multisite and multi-network compatibility but super admins have often run into failure on networks with higher numbers of sites. Wildcard support for Let’s Encrypt will provide a better way to secure multisite networks.

\n

Let’s Encrypt will offer the wildcard certificates via the new ACME v2 API endpoint and will start by supporting base domain validation via DNS with the possibility of adding other validation options in the future. ACME is the protocol that Let’s Encrypt developed to allow subscribers to acquire and manage certificates. Those using the v1 endpoint are encouraged to move to v2 as soon as it’s available in January 2018. The v2 protocol was developed to be an IETF (Internet Engineering Task Force) standard so that ACME can work with more certificate authorities in the future.

\n
\";s: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, 07 Jul 2017 18:32: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: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:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:98:\"WPTavern: WangGuard Plugin Author Shuts Down Splog Hunting Service Due to Trauma and Death Threats\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72733\";s:7:\"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:\"https://wptavern.com/wangguard-plugin-author-shuts-down-splog-hunting-service-due-to-trauma-and-death-threats\";s: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:6853:\"

\n

After seven years of developing and supporting the WangGuard/SplogHunter service, José Conti has shut down the server permanently due to the stress and trauma associated with maintaining it. Conti is a WordPress plugin developer and consultant, and a member of the WordPress España translation team. His WangGuard plugin identifies and blocks sploggers, unwanted users, and untrusted users on WordPress, Multisite, BuddyPress, bbPress, and WooCommerce sites. It is currently active on more than 10,000 sites.

\n

Speculation about why the service shut down was running rampant after Conti had collected donations via an Indiegogo campaign in October 2016 to fund support and server costs. Since that time SiteGround stepped in to sponsor WangGuard, eliminating the server costs. The only costs that remained were Conti’s time and effort that he put into supporting the plugin.

\n

“My purpose with WangGuard was never money,” Conti said in his post explaining the reason for the shut-down. “I could have made WangGuard a paid plugin at anytime, and actually had a plan for that for years. But I didn’t do it because there is something inside me that would never let that happen. It was never, I repeat, never my plan to get rich with WangGuard, and I assure you that I could have done it easily: simply charging each of my users 24€/year, would have meant an income of more than 2 million euros per year. I just had to distribute a version of WangGuard I had collecting dust, with a checkbox on WangGuard’s server administration options but I never got it done. No matter the other reasons, which only people very close to me know: I simply didn’t want to, nor did I want to be a millionaire.”

\n

Mafia Death Threats and Trauma from Exposure to the Dark Web: The High Cost of WangGuard’s 99.9% Accurate Detection of Splogs

\n

WangGuard has long been known for its nearly perfect detection of registration spam. Not only did it completely block unwanted users, it also removed them from the database. The plugin was unrivaled in both accuracy and price – all users got everything the service offered for free. In order for WangGuard to provide its 99.90% accuracy, Conti bolstered the algorithm with manual curation and reviews.

\n

“WangGuard worked in two different ways: as an algorithm that I had been refining for seven years, and which was getting better as the sploggers evolved, so that it was always one step ahead of them, and also as human curation, in which I reviewed many factors, among them sites of sploggers to see if their content could improve the algorithm and make sure that it worked correctly both when it was blocking or not blocking a site,” Conti said. “The great secret of WangGuard was this second part. Without it WangGuard would not ever have become what it was.”

\n

Because of how effective WangGuard was at stopping unwanted users, Conti said for four years he received “almost daily death threats from mafias for making them lose millions of dollars.”

\n

Through the process of manually curating splogger sites, Conti caught a glimpse of the some of the darkest places on the web, which he said had a damaging psychological impact on him.

\n

“For seven years, I have visited places where I saw pederasty, pictures, and videos of murders (by razor blades, by gutting live people, by beheadings, dismemberments, to name a few), real videos of rape of all kinds (children, women, boys), photos of accidents in which people were totally disfigured, bizarre actions that I did not even know existed, and a very long ‘and so on,’ which I do not want to expand on,” Conti said.

\n

The effects of viewing these types of websites every day took their toll and Conti decided to close the splog hunter service.

\n

“Finally, a few months ago, I broke down,” Conti said. “I disappeared from everywhere and fell into a depression. The seven years of working at WangGuard finally took a toll on me. I had nightmares because of all the macabre deaths I had seen, an obsession with protecting my children from pederasty, OCD, depression, and many other symptoms. It took me about 6 months to recover (and honestly, I may be deceiving myself, since I do not think I completely recovered my life).”

\n

I asked Conti if clicking through to the websites was necessary for maintaining the service. He explained that while WangGuard blocked emails, domains, IPs, and ISPs, without his manual curation of visiting the domains and clicking the links, users could get a lot of “sleepers” – registered and active accounts that remain silent until one day with a 0day vulnerability or a bug fix, they attack thousands of websites. The sleepers also wait to perform actions like create millions of sites on thousands of WordPress multisite installations in order to create a lot of bad content/links.

\n

“Visiting many domains, I was able to minimize this problem,” Conti said. “The way I worked not only fixed the current spam / splog problem, but the wizard and database also fixed any future problems with sleepers.”

\n

Another reason he visited the domains was to figure out what he needed to block, whether it was an email or a domain. The domain could be a spam domain or possibly a free email service.

\n

“By visiting a website, I could detect whether it was a phishing website or a site camouflaged as an email service in order to try to cheat WangGuard,” he said. “I saw a lot of ‘techniques’ for trying to cheat WangGuard at Black Hat specialized forums. I had been subscribed to many spam/sploggers forums for investigation. Every time that a user described a real technique for cheating WangGuard, it was fixed immediately.”

\n

If you’re still using the WangGuard plugin, it may continue to work but not nearly as well as in the past. Conti said that some parts of the code work without the API, but the most important parts require the WangGuard/SplogHunter server. The plugin is open source, so anyone can fork it. An English translation of his original post is available on the WordPress.org plugin forums.

\n
\";s: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, 07 Jul 2017 00:36:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:81:\"WPTavern: WordSesh Asia Now in Planning for 2018, WordCamp Asia Targeted for 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72742\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:91:\"https://wptavern.com/wordsesh-asia-now-in-planning-for-2018-wordcamp-asia-targeted-for-2019\";s: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:4161:\"photo credit: Sakin Shrestha\n

Yesterday Sakin Shrestha announced that WordCamp Asia is now in the preliminary planning stages. Shrestha is a key reviewer on the Theme Review Team, translates WordPress to Nepali, and organizes meetups and WordCamps in Nepal. He and other members of the WordPress community in Asia, including representatives from India, Japan, Indonesia, Thailand, Sri Lanka, Singapore, and Nepal, had the opportunity to meet at WordCamp Europe.

\n

“We have been talking about WordCamp Asia informally when some of us attended WordCamp US for the first time,” Shrestha said. “That’s was in 2015, where I met Naoko Takano. She is the one with the main idea as the Japanese WordPress community was already doing well. Then we started meeting more people from Asia at WordCamp Europe 2016 and had an informal meeting there.”

\n

After this meeting, Rahul Bansal created a Facebook group for WordPress Community Organizers in Asia to support each other in a more coordinated effort. The first formal meeting happened at WordCamp Europe 2017 where the team decided that trying for WordCamp Asia in 2018 would be too soon. Instead, they are planning to host a WordSesh Asia event in 2018 to work on their coordination and teamwork. The team is working towards hosting WordCamp Asia in 2019.

\n

Organizers Consider Bangkok as a Possible Location for WordCamp Asia in 2019

\n

Shrestha’s post identifies several challenges that are unique to hosting a large scale WordCamp in Asia, including the need for visas even for travel within Asia, political instability, and numerous currencies and languages in use.

\n

“WordCamp Asia is really important for the WordPress community in Asia,” Shrestha said. “I am fortunate enough to attend WCUS and WCEU, which are some of the biggest WordCamps where we get to meet lot of WordPressers, share and exchange ideas, contribute to WordPress, start a new business, and think outside of the box. But for most of Asians, it’s really difficult to go that far and also it’s expensive to attain those. So, we are limited to WordCamps in our own country and neighboring ones. That is why we are thinking about WordCamp Asia in Bangkok, which will be really inclusive as it’s in the center part of Asia and it’s cheaper to go there and less time consuming for all.”

\n

Shrestha also feels strongly about providing travel assistance for those with financial hardships, as the most expensive aspect of attending a WordCamp is usually the travel and accommodation.

\n

“WordCamps are not just for the rich,” Shrestha said. “The primary motive of WordCamps is to grow the local community. So, WordCamp Asia’s mission will be to influence the community of WordPress Asia and help it to grow. That is why, instead of planning for a grand and pompous event, we need to make sure it is affordable and reachable to people of all financial backgrounds.”

\n

Shrestha said he has seen major changes in working with the WordPress community in Nepal from 2012 – 2017, which he attributes to having a stronger local presence with the WordCamp. India has also benefited from hosting WordCamps and has approximately nine happening in various cities. They are working towards hosting a WordCamp India in the future. There are also emerging communities in Singapore, Thailand, Indonesia, Sri Lanka, Cambodia, and Vietnam.

\n

“It’s time for pursuing WordCamp Asia,” Shrestha said. “We really have good talents here in Asia but we lack exposure. WordCamp Asia can create buzz and make more people aware, inspire, and provide opportunity.”

\n
\";s: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, 06 Jul 2017 18:10:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:63:\"WPTavern: Jesse Petersen, Founder of Genesis The.me Passes Away\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72772\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wptavern.com/jesse-petersen-founder-of-genesis-the-me-passes-away\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8085:\"Petersen Family\n

Jesse Petersen, founder of Genesis The.me and Petersen Media Group, has passed away at the age of 38. Petersen had been battling Cystic Fibrosis for the past several years and suffered a massive lung bleed earlier today. He passed out before paramedics could reach him and could not be revived at the emergency room.

\n

Petersen was on a double-lung transplant list with a lung allocation score of 38.859. The LAS is a score used to prioritize waiting list candidates based on a combination of wait list urgency and post-transplant survival. Last month, Petersen received the phone call he had been waiting for.

\n
\n

I got the call! Getting ready to leave to go to the hospital for testing and waiting.#NewLungsForJesse pic.twitter.com/hCCJik05MY

\n

— Jesse Ⓦ Petersen (@jpetersen) June 9, 2017

\n

\n

Unfortunately, the lungs were determined not to be in a suitable condition for transplant.

\n
\n

No go. He didn\'t like the look of the lungs. \"?\" No new lungs for Jesse today. Maybe tonight the phone will ring again.

\n

— Jesse Ⓦ Petersen (@jpetersen) June 9, 2017

\n

\n

He shared his experience in a raw, emotional post that describes the highs and lows he felt that day. “While the day was an emotional roller coaster, with the highs being WAY up there, the lows were surprisingly mild,” Petersen said. “They just weren’t the right lungs, and this protected me from years of issues, so it’s all good. The call for the perfect lungs for me will come in God’s timing. I am content to wait.”

\n

On July 2nd, a patient with a higher LAS score than Petersen’s was taken into surgery to receive a double-lung transplant. This made Petersen the highest priority pending a match was found but a match wasn’t found in time.

\n
\n

She was taken into surgery at noon, Tampa time. Surgery is 6-12 hours. I\'m very happy for her because her need was more than twice mine.

\n

— Jesse Ⓦ Petersen (@jpetersen) July 2, 2017

\n

\n

I did not have the opportunity to meet him in person. From those who knew him personally, Petersen was a great husband, father, and a caring individual who despite his medical situation, would help out the best way he could. There are two stories that highlight the kind of person he was. The first is a Twitter thread he published two days ago.

\n

When you meet a 5 year-old who needs a heart and double-lung transplant but has been turned down everywhere, your situation doesn’t seem so bad. That family doesn’t care about politics, social class, keeping up with the Joneses, or whether their clothes match. They are enjoying life.

\n

Because when it comes down to it, all we really need is to know our worth and love everyone else because they have equal worth. That doesn’t mean you have to agree with everyone, but you don’t have to seek out opposition or turmoil. Random acts of kindness rock.

\n

Can you look over your life and say you’d be leaving those connected to you better off having known you? If not, start today.

\n

The second is from his Facebook account about an encounter he had with a mother pushing her small boy in a wheelchair with a surgical mask on.

\n

I finally got out of the house to go do a God & Country service followed by fireworks. While waiting to go outside, a mom I’d seen pushing a small boy in a wheelchair with a surgical mask and oxygen on him came over to me.

\n

‘I just wanted to say how cool I think your double tank cart is. I’m going to call my supplier tomorrow to get one for our wheelchair.’

\n

We started talking (most unlike me) and she said her son needed a heart and a double lung transplant… but they’ve been turned down everywhere, starting with the very forgiving Pittsburgh center.

\n

‘I’m so sorry.’

\n

[nodded her head with a pained look] ‘We’re just making the most of our time now.’

\n

My heart broke. I’ve already lived 7 of his lifetimes. I’ve played sports, graduated from college, stood on the equator, married my best friend, and have two healthy boys.

\n

So kick me the next time I complain about my wait, OK?

\n

Members of the WordPress community are using social media to share memories, grieve, and pass along condolences to his family.

\n
\n

I first met @jpetersen at #wcorl and was honored to have him at #wcmia 2015. Hope it’s ok to share his “speaker card” from @wordcampmiami. pic.twitter.com/R7czM5AV1h

\n

— David Bisset (@dimensionmedia) July 5, 2017

\n

\n
\n

RIP @jpetersen, you were a great friend, and co-host. Gonna miss the great convos we had.

\n

— The WP Crowd (@thewpcrowd) July 5, 2017

\n

\n
\n

Met @jpetersen on multiple occasions. Family man and proud dad. Always respected the hell outta that. See you on the flip side, buddy.

\n

— Jared Atchison (@jaredatch) July 5, 2017

\n

\n
\n

Terrible news, @jpetersen will be missed. CF takes too many, too soon. Rest in peace, buddy.

\n

— Brian Krogsgard (@Krogsgard) July 5, 2017

\n

\n

Petersen’s family has created a crowd-funding campaign to help offset funeral and medical expenses. Since its creation, the community has donated more than $12K of $20K. If you are able, please consider donating as Petersen was the sole provider of income for his family.

\n

My deepest condolences go out to his friends and family. Petersen is survived by his wife and two sons.

\n

Related Reading:

\n

The Loss of One of Our Own

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jul 2017 02:09: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:\"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:67:\"WPTavern: WPWeekly Episode 280 – Behind the Scenes of Tuniversity\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wptavern.com?p=72768&preview=true&preview_id=72768\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:74:\"https://wptavern.com/wpweekly-episode-280-behind-the-scenes-of-tuniversity\";s: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:2595:\"

In this episode, John James Jacoby and I are joined by Kiko Doran and Travis Totz, Senior Web Strategist at Modern Tribe. Doran helped create Tuniversity, a revolutionary new way of learning music through a highly interactive iBook.

\n

The project was so large, Doran outsourced some of the work to Modern Tribe, a web design and development firm. During the show, we learn the benefits of working with an agency you trust. Doran also explained what it was like to be a client as he’s normally fulfilling the agency role.

\n

Two major takeaways from the Tuniversity project include:

\n
    \n
  1. Work on things you’re passionate about with people who share the same passion.
  2. \n
  3. Approach problems with a positive mindset.
  4. \n
\n

Near the end of the show, we discussed the news that WangGuard is officially closed.

\n

Picks of the Week:

\n

WPHierarchy.com is a WordPress resource created by Rami Abraham in 2013. The site is an interactive version of Michelle Schulp’s colorful diagram of WordPress’ template hierarchy. Each template is linked to documentation that explains its function

\n

Dr. Russell A. Barkley (30 essential ideas everyone should know about ADHD)

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, July 12th 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #280:
\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jul 2017 23:58:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:105:\"WPTavern: Nadia Eghbal and Mikeal Rogers Join a16z Podcast to Discuss the Changing Culture of Open Source\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72702\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://wptavern.com/nadia-eghbal-and-mikeal-rogers-join-a16z-podcast-to-discuss-the-changing-culture-of-open-source\";s: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:6242:\"photo credit: 16th st(license)\n

Nadia Eghbal and Mikeal Rogers recently joined Sonal Chokshi for an episode of the a16z Podcast to discuss the changing culture of open source. Eghbal works in community programs at GitHub to better support people doing open source work. Rogers is the community manager at the Node.js Foundation. The episode focuses on the human aspect of the world of open source software and what inspires people to work together to give software away for free.

\n

Through Eghbal’s research on sustaining open source communities, she found, as Rogers succinctly summarized on the show: “There’s no connection between the number of users and the number of people maintaining a project.” The Heartbleed Bug, which arrested public attention when it was disclosed in 2014, is perhaps one of the most critical examples of an open source project with a global user base and a grossly disproportionate number of maintainers.

\n

As part of her research at GitHub, Eghbal is working on creating a vocabulary to explain things that are happening with open source projects. One example is the distinction between “popular” versus “healthy” when describing projects in terms of the communities behind them, governance, quality of maintainership, and other factors that influence a project’s condition.

\n

“Because the dialogue tends to be set by popular projects, and those developers and their problems tend to dominate the story about this, you have these words and vocabulary like ‘drive-by-contributions,\'” Rogers said. This often implies that maintainers are too busy to look at the code. Rogers advocated for changing this perception of “drive-by-contributors” to view them as casual contributors, people who show up and have value to add. If maintainers can seize these contributions as an opportunity, they will have a better chance of leveling up contributors to be a more active part of their organization.

\n

The group also discussed how technology has caused a cultural shift among open source communities from the old world versus the new world of open source.

\n

“In older open source, part of the barrier to entry that people went through before they were ever identifiable to any contributor was an acclimation to the culture and an acclimation to the tool chain and all this stuff,” Rogers said. “One of the things that GitHub has done is completely remove all of that cultural acclimation. There is one tool chain that you use to contribute to any project and when you show up you don’t have all of this cultural knowledge. You haven’t bought into any of these ideals about open source necessarily. You’re just there to contribute. We actually need to work with that.”

\n

In the past, contributors informally acclimated to the culture through the onboarding process, and most software projects were more self-contained.

\n

“Where that becomes awkward today is that so many different pieces of software depend on other open source projects, which wasn’t actually true 10 or 20 year ago,” Eghbal said. With so many projects fitting into others as dependencies, it becomes more difficult to actually remove a project from the public domain. Open source licensing ensures that these projects have a life of their own. This has democratized entrepreneurship, making it easy for people to piece together technology to build applications and businesses. It also requires a higher level of skills for people working together across various open source projects and cultures.

\n

Eghbal and Rogers discussed the qualities of a healthy open source community, such as how welcoming the project is and how contributors speak to each other and resolve conflict. The ability to successfully resolve conflict can make the difference between a healthy growth of contributors or attrition on a project. Rogers mentioned a related conversation they had with Karl Fogel on their Request for Commits podcast concerning conflict within projects.

\n

“When we were talking to Karl, he has this view that ‘As long as a it has an open source license, it doesn’t matter how dysfunctional the project is, because we as a community always have this ability to fork it,\'” Rogers said. “I didn’t agree with him on this, because the practical reality of forking a project is such a huge overhaul and you don’t necessarily have the right people to do it in your particular time. What you actually want are the healthy communities with healthy practices, what you want is to keep them going.”

\n

Another open source predicament they discussed, which is fairly common in the WordPress ecosystem, is when a company releases a project as open source or “gifts it to the community.” Eghbal likened this to “sending your dog away to a farm upstate.”

\n

“We’re really excited to announce this is now open source, meaning we don’t want to take care of it anymore,” she said. “‘We’ll give it to the community,’ (except they haven’t actually identified anyone in the community who wants to take care of it.)” This type of situation shows how “giving back to the community” isn’t always what it appears to be for those who end up using these projects that have been released into the wild.

\n

The group also discussed how the incentives for people to contribute to open source have changed over the years and why “the GitHub generation” has more readily adopted the MIT license. Check out the full podcast episode below:

\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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jul 2017 19:26: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: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:84:\"HeroPress: How I tried, applied, got involved. Realizing one of my childhood dreams.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=1950\";s:7:\"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:188:\"https://heropress.com/essays/tried-applied-got-involved-realizing-one-childhood-dreams/?utm_source=rss&utm_medium=rss&utm_campaign=tried-applied-got-involved-realizing-one-childhood-dreams\";s: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:15809:\"\"Pull

When you’re born in an island, you usually grow up thinking about all the marvelous things awaiting for you on the other side of the sea. I was born in Sardinia, an island in the middle of the Mediterranean Sea, and as a child I dreamt about becoming an air hostess.

\n

I wanted to travel the world and speak tons of foreign languages, to be able to communicate with local people everywhere I’d go.

\n

But people kept telling me that I wasn’t going to become tall enough for that job (genetics don’t lie!), and I eventually listened to them. I ended up choosing a different path in life, following the Italian mantra: “You have to study something that will guarantee a stable and secure job for life”.

\n

Even if I wasn’t that much convinced about the perspective of having the same job for all my life, as my parents did, at the same time I didn’t want to get stuck in the island forever: the unemployment rate in Sardinia is unfortunately really high and I didn’t want to risk to be part of that percentage.

\n

Crossing the borders of the island

\n

So I chose the Faculty of Economics and did my best to cross the borders of my island as soon as I had the chance: this happened when I was 22 and I moved to Siena, Tuscany, to finish my studies. That is also the time when I opened my first personal blog on an Italian platform named Tiscali, which I later migrated to WordPress.com.

\n

I’ve always loved writing, and since I was a little girl I used to spend hours in my room writing stories and poems. I was doing the same with the blog but with the advantage of reaching a much larger public, virtually meeting many people and getting inspired by their stories.

\n

After 2 years in Tuscany I moved to Strasbourg, France. There I learnt French and did several little jobs, but I found my first important one in Milan, the big city shining with job opportunities for everyone —as Italians love to say.

\n

There I was, fulfilling the dream of many young people of my age (and their families): I was 25, with an average-paid 40 hours/week office job in the marketing department of a big international company, and I was surrounded by ambitious colleagues and a boss constantly asking for extra —and free— working hours per day.

\n

I was feeling like a parrot inside a golden cage.

\n

It seemed to me I wasn’t going anywhere. I also gave up blogging because I wasn’t feeling inspired enough to write. People constantly repeated to me that I was super lucky to have a permanent contract and work in a marketing department; in their eyes I was all set for life, so —using some strange equation — I also had to be happy!

\n

Of course I was luckier than many of my peers, but I kept asking myself if I really wanted to do that life forever.
\nDid I really want to keep on working 10 hours per day under the neon lights of an office, annihilate my dreams and live waiting for the free time of the weekend?

\n

The most vivid memory I have of that period is the overwhelming feeling clenching my throat on Sunday afternoons, when I started to dread the moment of coming back to the office the day after.

\n

Facing new challenges

\n

So I left and faced the change. At the beginning I gave myself the opportunity to test different office jobs. But the results were always the same: I kept feeling unsatisfied with my life, and I understood I had to respect my little girl’s dream and fly away from my golden cage.

\n

I opted for emigration and moved alone to Barcelona, Spain, in 2012.

\n

My first move was plunging myself into a few months of intense Spanish learning at the University, then I found a job in an international Assisted Reproduction Clinic.

\n

My job title was “Patient Coordinator” and I was assisting international patients coming to Barcelona for their treatments: I was their translator, interpreter and administrative consultant. Patients were from Italy, France, England, Morocco, Senegal…it was a Babylon of people with so many different backgrounds that I felt really inspired by some of their stories.
\nThis inspiration led me to start writing again: I dusted off my WordPress blog and filled it up with stories about my new life in Barcelona and some of the women I was meeting at the Clinic. I was feeling stronger and more independent than ever.

\n

The job at the Clinic lasted for 3 years. Even if it was really inspiring, it was also very stressful. Imagine being a 30-something woman speaking all day long about fertility problems with women struggling to have a baby.

\n

I realized I was getting too involved and decided to look around to see what I could do next.

\n

How can I find a job like this?

\n

It was summer 2015 and I was at my desk, in my little tiny apartment in front of Barcelona’s beach. I was writing in my blog and I got stuck in a technical problem. While I was searching through the WordPress.com documentation, I saw a pop-up in the bottom right corner of my screen: an Automattician wrote me to ask if I needed help. I gladly accepted her offer, we chatted for a few minutes, the problem was solved and I could go back to my writing. But I also left the chat with one question: how could that person on chat find a support job with WordPress?

\n

Curious as I am, I started looking for an answer and I stumbled upon the official WordPress job page: jobs.wordpress.net

\n

There I found a job offer that caught my attention: WP Media, a French startup, was looking for a polyglot and remote customer service teammate for one of their plugins, WP Rocket. I read their requirements: fluency in English, French and possibly another language, great experience with WordPress, some coding skills.

\n

That offer was calling me, I felt it.

\n

I knew I didn’t have all the requirements, but hey, I could speak 4 languages, and I had a WordPress blog…right? Of course, I didn’t know anything about PHP, I had always been a WordPress.com user until that moment and I didn’t really know how to manage a self-hosted website or use a cache plugin…but I felt I was ready to learn all that. And moreover, what did I have to lose?

\n

I wrote my most inspired cover letter and sent my CV.

\n

With my total surprise, they answered me the day after and we set up an interview by Skype. My main strengths were the fluency in 4 languages and my previous experience in customer service, so I was really confident about those skills; yet I wanted to be totally honest with them: yes, I had been using WordPress for a long time, and yes, I was digital savvy enough, but I knew very little on the technical side. I had always worked on the front end of websites, writing, blogging, learning by myself; I didn’t know anything about the backend of WordPress sites.

\n

Even so, they had faith in me and in a few days I had the confirmation: I was in! During the first days I felt so happy about this new major turning point in my life: not only had I found a job thanks to my primordial passion, speaking foreign languages, but for the first time in my life I could do that job from home or anywhere else I liked, instead of being caged in a formal office!

\n

I got introduced to my remote teammates and I instantly felt welcomed.

\n

Learning by doing

\n

But, very soon, that initial enthusiasm started to struggle with another intense feeling: the fear of exposing my inexperience.

\n

There were too many things I didn’t know!

\n

Working in a WordPress backend was so new to me that I started studying like crazy and reading everything I could about WordPress for beginners. I went through some really intense months of learning by doing, supported by my teammates. Like a baby who start crawling and then taking little steps, I was initially answering the easiest tickets from our customers. 
At the same my teammates were sending me useful material to read, setting up video-calls for 1to1 training, encouraging me every time they could.

\n

After a few days I received the first happy comments by the customers I was helping in their mother tongue: until that moment the plugin’s support had been offered only in English and French, so it was the first time Spanish and Italian customers were being answered in their own language…and they appreciated that!

\n

Even so, I can’t deny it, I was scared.

\n

It was so scary admitting my ignorance, exposing it in a remote environment where I couldn’t see my teammates reactions live.

\n

My first instinct was imagining the worst scenarios where they were secretly hating me for interrupting their work on Slack with my doubts.

\n

But I had no other choice than to keep asking questions and learn from their answers. Not doing so would have been much worse: silencing my voice would have slowed down my learning process.

\n

Why don’t you try to contribute to WordPress?

\n

We were at WordCamp Paris 2016 when one of my teammates showed me how the WordPress community worked together and kept in contact through Slack.

\n

“You speak multiple languages, why don’t you try to contribute to the polyglots team?” —he asked.

\n

That thought never crossed my mind before, I knew very little about contributing to WordPress. I had been working for WP Media for 6 months and, while I was enjoying my new job a lot, I was just slowly starting to abandon that overwhelming feeling of insecurity I mentioned above.

\n

I didn’t feel ready to dive into a new challenge and start also contributing to WordPress, I thought I didn’t have the ability to do that. I was wrong, obviously.

\n

Curiosity won on me another time and I joined the two Slack channels Making WordPress (where all the WP global community meets) and Italia WP Community. I lurked the channels for a few months, until I went to WordCamp Milan and met some members of the Italian Polyglots team.

\n

It was love at first string: Laura, one of the General Translation Editors (GTE) for Italy, taught me how to start contributing and translating following the polyglots guidelines. She also told me about the big effort the Italian community has been doing to work together, consistently, to boost WordPress related events in Italy and to grow up.

\n

I wanted to be an active part of it and I started contributing.

\n

Now I’m a Project Translator Editor for the Italian polyglots team and I mentor new contributors: I love it!

\n

Since the beginning of my journey into the WordPress world I traveled a lot, and also attended WordCamps in Paris, Vienna, Milan, Barcelona, Torino and Bilbao.

\n

Following my teammates encouragement, I also started applying to WordCamps as a speaker, because I felt my story could be important for other people looking for new inspiration for their working and personal life. I gave my first talk in my adoptive city, Barcelona, in December 2016, then in Torino in April 2017 and I recently had the honor to tell my story also from the stage of WordCamp Europe 2017.

\n

In a short glimpse of time I engaged in many activities related to WordPress which allowed me to meet very interesting and inspiring people from all over the world.

\n

I’m (not) lucky.

\n

People keep telling me that I’m lucky, and it’s true, I really am. But if I’m here, now, sharing my story (and thanks Topher for inviting me to write it!) is not because I live under a lucky star: I just used my previous skills and passions and adapted them to a new career and life path.

\n

We all have some skills; and if we don’t know which they are exactly, we should take some time to make a list of the things we’re really good at. With that in mind, just try. Apply. Get involved. Don’t get stuck in the feeling of “I can’t do it because I don’t know enough”.

\n

That is what I did: without even realizing it, I started putting into reality the dream of the little girl who was born in an island and wanted to travel and speak different languages.

\n

WordPress made this possible: I’m part of a big community, and I am proud of it.

\n

The post How I tried, applied, got involved. Realizing one of my childhood dreams. appeared first on HeroPress.

\";s: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, 05 Jul 2017 12:00:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"Alice Orru\";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:102:\"WPTavern: WordCamp Europe 2017 Posts 24% No-Show Rate, Cites Early Ticket Sales and Expensive Location\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72644\";s:7:\"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:111:\"https://wptavern.com/wordcamp-europe-2017-posts-24-no-show-rate-cites-early-ticket-sales-and-expensive-location\";s: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:3872:\"photo credit: WP Tavern\n

WordCamp Europe 2017 organizers have posted attendance and budget data compiled after the conclusion of the event. Despite being promoted as “the largest WordPress event to this day” with more than 3,000 expected attendees, WCEU 2017 fell short with 1,900 people on the ground. Attendees were 5% fewer than last year’s 2,000 in Vienna. Expectations ran high but organizers could not predict the 24% no-show rate once the event got started. This is more than double the 10% no-show rate for the previous four years.

\n

The camp’s organizers do not have a simple explanation for the high no-show rate, but cite several factors, including a few dozen participants being denied visas, higher local sales, an expensive location, and putting tickets on sale too early. Approximately 60% of attendees were from nearby countries, such as France, Great Britain, Germany, Belgium, and the Netherlands.

\n

Ticket sales for 2017 were open immediately at the conclusion of the 2016 event in Vienna. Organizers found that tickets sold in the first six months had a 34% no-show rate as compared to 20% for those sold in 2017. As the event has often sold out in the past, prospective attendees may have felt pressure to purchase a ticket in advance without confirming the ability to attend.

\n

Posting increasingly higher attendance numbers isn’t one of the goals of the WordCamp, but planning accurately for the number of people who will attend is crucial for resource and budget planning. When one in four attendees is a no-show, the plans for food, swag, venue accommodations, and other aspects of the event are askew.

\n

Organizers did not mention Contributor Day attendance in the wrap-up report, but this may have been one of the most successful aspects of the event. It was held prior to the main conference days, which may explain the event’s unusually high attendance numbers. Organizers hosted 473 attendees for the 500 available contributors slots.

\n

WordCamp Europe 2017 Cost 300€ per Attendee, Sponsors Covered 80%

\n

WordCamp Europe’s wrap-up report also includes a transparent breakdown of the event’s 700k€ budget. Catering costs for lunches, snacks and drinks, made up 50% of the budget. However, organizers were limited to the venue’s catering partners, which blurs the line between actual food versus venue costs.

\n

The team was unable to sell all of the sponsorship packages and was forced to reduce the budget by 149k€ along the way. WordCamp Central subsidized 10€/ticket and covered the final deficit of 28k€. The cost breakdown per attendee was 300€ with sponsors covering 80%, WordCamp Central 7%, and tickets sales 13%. These numbers show that the 40€ ticket price is a small fraction of the total costs required for an event of this size.

\n

Organizers said they felt it was important to share the data for educational purposes but also to “demonstrate to everyone who might have a doubt, that maintaining the ticket fee very low is meant to make our events accessible to all, but that the fee is not an indicator of the value of the conference.”

\n
\";s: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, 03 Jul 2017 19:06:00 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:43:\"Dev Blog: The Month in WordPress: June 2017\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=4865\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2017/07/the-month-in-wordpress-june-2017/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9049:\"

We’re starting a new regular feature on this blog today. We’d like to keep everyone up-to-date about the happenings all across the WordPress open source project and highlight how you can get involved, so we’ll be posting a roundup of all the major WordPress news at the end of every month.

\n

Aside from other general news, the three big events in June were the release of WordPress 4.8, WordCamp Europe 2017, and the WordPress Community Summit. Read on to hear more about these as well as other interesting stories from around the WordPress world.

\n
\n

WordPress 4.8

\n

On June 8, a week before the Community Summit and WordCamp Europe, WordPress 4.8 was released.You can read the Field Guide for a comprehensive overview of all the features of this release (the News and Events widget in the dashboard is one of the major highlights).

\n

Most people would either have their version auto-updated, or their hosts would have updated it for them. For the rest, the updates have gone smoothly with no major issues reported so far.

\n

This WordPress release saw contributions from 346 individuals; you can find their names in the announcement post. To get involved in building WordPress core, jump into the #core channel in the Making WordPress Slack group, and follow the Core team blog.

\n

WordCamp Europe 2017

\n

WordCamp Europe 2017 was held in Paris between June 15-17. The event began with a Contributor Day, followed by two days of talks and community goodness. The talks were live-streamed, but you can still catch all the recordings on WordPress.tv. The organisers also published a handy wrap-up of the event.

\n

WordCamp Europe exists to bring together the WordPress community from all over the continent, as well as to inspire local communities everywhere to get their own events going — to that end, the event was a great success, as a host of new meetup groups have popped up in the weeks following WordCamp Europe.

\n

The work that Contributor Day participants accomplished was both varied and valuable, covering all aspects of the WordPress project — have a look through the Make blogs for updates from each team.

\n

Finally, we also learned during the event that WordCamp Europe 2018 will be held in Belgrade, Serbia, continuing the tradition of exploring locations and communities across the continent.

\n

WordPress Community Summit

\n

The fourth WordPress Community Summit took place during the two days leading up to WordCamp Europe 2017. This event is an invite-only unconference where people from all over the WordPress community come together to discuss some of the more difficult issues in the community, as well as to make plans for the year ahead in each of the contribution teams.

\n

As the Summit is designed to be a safe space for all attendees, the notes from each discussion are in the process of being anonymized before we publish them on the Summit blog (so stay tuned – they’ll show up there over the next few weeks).

\n

You can already see the final list of topics that were proposed for the event here (although a few more were added during the course of the two day Summit).

\n

WordPress marketing push continues apace

\n

As part of the push to be more intentional in marketing WordPress (as per Matt Mullenweg’s 2016 State of the Word), the Marketing team has launched two significant drives to obtain more information about who uses WordPress and how that information can shape their outreach and messaging efforts.

\n

The team is looking for WordPress case studies and is asking users, agencies, and freelancers to take a WordPress usage survey. This will go a long way towards establishing a marketing base for WordPress as a platform and as a community — and many people in the community are looking forward to seeing this area develop further.

\n

To get involved in the WordPress Marketing team, you can visit their team blog.

\n

New Gutenberg editor available for testing

\n

For some time now, the Core team has been hard at work on a brand-new text editor for WordPress — this project has been dubbed “Gutenberg.” The project’s ultimate goal is to replace the existing TinyMCE editor, but for now it is in beta and available for public testing — you can download it here as a plugin and install it on any WordPress site.

\n

This feature is still in beta, so we don’t recommend using it on a production site. If you test it out, though, you’ll find that it is a wholly different experience to what you are used to in WordPress. It’s a more streamlined, altogether cleaner approach to the text-editing experience than we’ve had before, and something that many people are understandably excited about. Matt Mullenweg discussed the purpose of Gutenberg in more detail during his Q&A at WordCamp Europe.

\n

There are already a few reviews out from Brian Jackson at Kinsta, Aaron Jorbin, and Matt Cromwell (among many others). Keep in mind that the project is in constant evolution at this stage; when it eventually lands in WordPress core (probably in v5.0), it could look very different from its current iteration — that’s what makes this beta stage and user testing so important.

\n

To get involved with shaping the future of Gutenberg, please test it out, and join the #core-editor channel in the Making WordPress Slack group. You can also visit the project’s GitHub repository to report issues and contribute to the codebase.

\n
\n

Further reading:

\n\n

If you have a story we should consider including in the next “Month in WordPress” post, please submit it here.

\";s: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, 03 Jul 2017 11:42: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:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:97:\"WPTavern: Gutenberg Contributors Explore Adding Drag-and-Drop and Multi-Column Support for Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72638\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:108:\"https://wptavern.com/gutenberg-contributors-explore-adding-drag-and-drop-and-multi-column-support-for-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6817:\"photo credit: ruudgreven DSC_0012(license)\n

The new Gutenberg editor has an open ticket for allowing users to sort blocks via drag and drop. Blocks can currently be sorted with up and down arrows located to the left of the content but the beta only allows for single-column stacking.

\n

One of the goals for Gutenberg is to provide “a page building experience that makes it easy to create rich post layouts.” As far as layout building goes, the first planned versions of the new editor are very primitive as compared to Wix and Weebly’s drag and drop website builders where nearly every element on the page can be easily moved to a different position.

\n

Contributors have been discussing the intricacies of adding this feature to Gutenberg since February. James Nylen summarized some of the challenges that make drag and drop more complicated to implement:

\n

Dragging and dropping a block is not really a one-step operation. It is more like 3:

\n
    \n
  1. Press and hold mouse button or screen
  2. \n
  3. Move to desired location
  4. \n
  5. Release
  6. \n
\n

Step 2 is incredibly difficult to get right, and requires a lot of complicated behaviors like duplicating an item (or at least its general shape and size), scroll handling, and determining the intended new location, especially at the beginning and end of the content. We have all used bad drag-and-drop experiences, and I would argue they are worse than not having it at all.

\n

That said, for two-dimensional movement with columns, I agree that arrows alone are probably not a good solution. Though mobile support for that is going to be very tricky no matter how it works.

\n

Several commenters on the ticket agree that repeatedly clicking arrows to move blocks is cumbersome and will become untenable in the future when multi-column support is added. This would require up, down, right, and left arrows to rearrange content. Users have come to expect a drag-and-drop interface, because nearly every page builder application offers it.

\n

“We are thinking of drag and drop as a progressive enhancement for desktops,” Joen Asmussen said. “One that would be great to have, but we should build it after we have explicit button actions in place for doing the same, including splitting into columns in the future. This decision is based on a desire to ensure accessibility as well as mobile devices can play the same game.”

\n

Asmussen marked the ticket priority as low in May and removed it from the beta milestone. At this point, users are not likely to see drag and drop in the first release that ships with WordPress core.

\n

Multi-Column Layouts Planned for Gutenberg V2

\n

The discussion surrounding adding drag-and-drop to the editor naturally leads into adding multi-column support. Limiting users to a single column is a one-dimensional approach to designing pages, but contributors don’t plan to leave Gutenberg without multi-column support for long.

\n

Geoarge Olaru, a designer at PixelGrade, shared a prototype for adding a simple two or three-grid column layout to Gutenberg.

\n

“Extending WordPress further from the default Blog Posts automatically implies the need of multi-column layouts for presentation pages,” Olaru said. “I would prefer to tackle this feature upfront, rather than letting every developer do it on his own (see the multitude of page builders plugins).”

\n

\n

“For the V1 editor, I’m afraid columns like this is out of scope,” Asmussen said in reply to a Olaru’s ticket with mockups and a prototype for multi-column support. “That’s not a ‘no’ — rather, we need some technical foundations to be solid first, before we commit to the really interesting stuff. But it might be a V1.1, or at the very least something for the customization folks later on in the year. Even before that, it would be good to keep this UI in mind, so that perhaps a plugin can add this even earlier.”

\n

Other commenters on the ticket feel more urgency about getting multi-column support into the first version of the editor. One of the concerns is that plugin developers will rush to add columns immediately based on demands from users, who will then have to migrate once core adds support.

\n

“Multi column layouts are a must-have,” Anthony Hortin commented on the ticket. “At the moment, Gutenberg isn’t solving any issue. You still end up with one long column of content. The whole reason page builders are so popular, and why hundreds of thousands of people are using them, is because they provide the ability to easily make multi-column layouts. Without this functionality, you’re not providing any reason to use Gutenberg over a page builder plugin.”

\n

One of the main challenges of adding multi-column support is figuring out what type of grid system to use and making sure that it scales from mobile to desktop. Weston Ruter joined the discussion to say that the foundational work for nested block support is being done now in version 1, but the UI for displaying them hasn’t been implemented yet.

\n

“I appreciate the excitement and urgency to wanting columns,” Asmussen said. “We feel the same urgency. It’s not about not wanting columns, it’s purely about managing resources at this point.”

\n

The good news is if you’ve been testing Gutenberg and wondering where some of these features are on the roadmap, they will be coming in later versions. While there may be disagreements about how much of a priority drag-and-drop and multi-column support should have for version 1, contributors agree that laying a solid technical foundation for these features is crucial for future extensibility.

\n
\";s: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, 01 Jul 2017 19:06:17 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:116:\"WPTavern: Gutenberg 0.3.0 Adds Front-End Styles for Core Blocks, Notices Framework, and Text and Image Quick Inserts\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=72646\";s:7:\"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:125:\"https://wptavern.com/gutenberg-0-3-0-adds-front-end-styles-for-core-blocks-notices-framework-and-text-and-image-quick-inserts\";s: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:4557:\"

Gutenberg development is marching ahead with version 0.3.0 released today. New releases are shipping out on a weekly basis, so testers will get to discover another round of new additions after updating to the latest. The changelog has a full list of the 50 additions and improvements included in this release, but here’s a quick visual tour of a few of the most interesting user-facing features added this week.

\n

Gutenberg developers have added front-end styles for core blocks, which means that content like cover images will now appear the same as they look in the admin in the editor. The demo content in the plugin has also been updated to display a full-width cover image. Below is an example of a standard width cover image on the front-end.

\n

\n

Version 0.3.0 also includes new text and image quick inserts, which appear when hovering over the blank space beneath the post content. This makes it faster to add the types of content that are used most frequently.

\n

\n

This release adds a framework for notices, which provides developers with reusable notices components, showing how to trigger notices and where they will show up. Gutenberg now displays notices on post save, schedule, and update.

\n

\n

Version 0.3.0 adds a new block descriptions component to blocks with inspector controls. Several of the core blocks now display descriptions. These will be especially useful when plugin developers begin adding their own custom blocks, offering users a quick way to see the purpose of the block.

\n

\n

This release adds more placeholder text to various blocks, as “placeholders are key,” according to the newly added design blueprints and principles included in Gutenberg’s documentation:

\n

If your block can have a neutral placeholder state, it should. An image placeholder block shows a button to open the media library, a text placeholder block shows a writing prompt. By embracing placeholders we can predefine editable layouts, so all you have to do is fill out the blanks.

\n

Version 0.3.0 also adds several enhancements that make it easier to edit and customize the image-oriented blocks with more options and settings:

\n\n

Active installs for the Gutenberg plugin have nearly doubled since last week and are at more than 900 sites. This is roughly 1% of the goal Matt Mullenweg set for testing on 100,000 sites before replacing the edit screen. The plugin may also be advertised in the dashboard in a future release, possibly 4.8.1, which is slated for the end of July.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 30 Jun 2017 22:07:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: Popular WordPress Plugins Slow to Add Meta Box Support for Calypso\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=71527\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/popular-wordpress-plugins-slow-to-add-meta-box-support-for-calypso\";s: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:3361:\"

During the State of the Word at WordCamp US 2016, Matt Mullenweg announced that Calypso was plugin aware. Calypso is a REST API and React powered application for the desktop created by Automattic in 2015.

\n

Developers with plugins active on 1M sites or more received an email invitation from Andy Peatling to begin building support for Calypso.

\n

“Calypso is now plugin-aware,” Mullenweg said. “This pull request was merged today, and as a way to bootstrap this, we’re opening up for what I just described for plugins to create Calypso interfaces for what they’re doing.

\n

“Basically saying, if you’re using Calypso on a site that has one of these plugins, let’s say WooCommerce, all of a sudden in the interface, there will be all the WooCommerce stuff. It’ll talk to the API, it will run on the desktop just like the rest of Calypso, and it will only be loaded if the plugin is active.”

\n

One of the major differences between Calypso and WP-Admin is that custom meta boxes added by plugins are not accessible in Calypso.

\n

Nearly seven months since the announcement, popular WordPress plugins have struggled to add meta box support, including those maintained by Automattic. WordPress SEO, active on more than 3M sites, is among the plugins that were selected to take part in the experiment.

\n

When asked about the progress of making WordPress SEO Calypso aware, Joost de Valk, founder of Yoast.com, declined to comment.

\n

Automattic has seen little progress on the initiative, “No news to report at this time, but hope to have some soon,” Automattic representative Mark Armstrong said. WooCommerce has yet to add meta box support and settings pages in Calypso.

\n

Gutenberg, WordPress’ new editor, is also built using React. One of the chief concerns expressed by users and developers is how it will support custom meta boxes built using the current PHP framework.

\n

“I miss a lot of the meta boxes I’m used to seeing on the screen,” Aaron Jorbin said. “Things like Yoast SEO (on some sites) and custom taxonomies are just not shown. If every meta box ever made for WordPress needs to be remade, it sure is going to make developers lives a living hell.”

\n

I want to use Calypso as a replacement for WP-Admin because it’s fast and I like the interface. However, I can’t do that until it supports meta boxes for the plugins I rely on, such as Edit Flow. Is the lack of custom meta box support for Calypso a sign of what’s to come with Gutenberg?

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 30 Jun 2017 20:05: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Wed, 26 Jul 2017 09:36:08 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Wed, 26 Jul 2017 09:15:08 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:11:\"HIT lax 249\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20130911040210\";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES -(182, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1501054260', 'no'), -(183, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1501011060', 'no'), -(184, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1501054260', 'no'), -(185, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '', 'no'), -(190, '_site_transient_timeout_theme_roots', '1501019413', 'no'), -(191, '_site_transient_theme_roots', 'a:1:{s:5:\"gwtd3\";s:7:\"/themes\";}', 'no'); +(208, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1501104963', 'no'), +(209, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1501061763', 'no'), +(210, '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1501104963', 'no'), +(211, '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '', 'no'); -- -------------------------------------------------------- @@ -596,9 +598,9 @@ INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALU (12, 1, 'wp_user_level', '10'), (13, 1, 'dismissed_wp_pointers', ''), (14, 1, 'show_welcome_panel', '0'), -(15, 1, 'session_tokens', 'a:6:{s:64:\"a32d56b116af50eeb6538cde07a8284f69b4fb6197a442a0eb8beff4b2075329\";a:4:{s:10:\"expiration\";i:1501136922;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1500964122;}s:64:\"f4a4585963403d3b2d34e39eca5626f08599bc1318c3b13a3b31a3ec478253a0\";a:4:{s:10:\"expiration\";i:1501148098;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1500975298;}s:64:\"02967d86f3a5e41ff4add825cfb194a18819927c08de65bf269968c70003976f\";a:4:{s:10:\"expiration\";i:1501153321;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1500980521;}s:64:\"f0db826049809931b1f4529b74402ef518caaed6ba9d5cd747f752d85cb7e2b4\";a:4:{s:10:\"expiration\";i:1501173848;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1501001048;}s:64:\"d0ee8ca310e36eb01b61d5603da04a3f5f49901e5e0abecfa438a7aab4eb7b42\";a:4:{s:10:\"expiration\";i:1501183856;s:2:\"ip\";s:13:\"85.73.218.110\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1501011056;}s:64:\"575df9ca3add9aaf2be8016f2e94d3d58379c6f0121a83f64253a6bc7d55b268\";a:4:{s:10:\"expiration\";i:1501184013;s:2:\"ip\";s:13:\"85.73.218.110\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1501011213;}}'), +(15, 1, 'session_tokens', 'a:7:{s:64:\"a32d56b116af50eeb6538cde07a8284f69b4fb6197a442a0eb8beff4b2075329\";a:4:{s:10:\"expiration\";i:1501136922;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1500964122;}s:64:\"f4a4585963403d3b2d34e39eca5626f08599bc1318c3b13a3b31a3ec478253a0\";a:4:{s:10:\"expiration\";i:1501148098;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1500975298;}s:64:\"02967d86f3a5e41ff4add825cfb194a18819927c08de65bf269968c70003976f\";a:4:{s:10:\"expiration\";i:1501153321;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1500980521;}s:64:\"f0db826049809931b1f4529b74402ef518caaed6ba9d5cd747f752d85cb7e2b4\";a:4:{s:10:\"expiration\";i:1501173848;s:2:\"ip\";s:3:\"::1\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1501001048;}s:64:\"d0ee8ca310e36eb01b61d5603da04a3f5f49901e5e0abecfa438a7aab4eb7b42\";a:4:{s:10:\"expiration\";i:1501183856;s:2:\"ip\";s:13:\"85.73.218.110\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1501011056;}s:64:\"575df9ca3add9aaf2be8016f2e94d3d58379c6f0121a83f64253a6bc7d55b268\";a:4:{s:10:\"expiration\";i:1501184013;s:2:\"ip\";s:13:\"85.73.218.110\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1501011213;}s:64:\"dd96122f6d105e3cf383949a1592c9fd48083e9381cef96d28da8b70c8b46de6\";a:4:{s:10:\"expiration\";i:1501234557;s:2:\"ip\";s:11:\"77.69.15.30\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36\";s:5:\"login\";i:1501061757;}}'), (16, 1, 'wp_dashboard_quick_press_last_post_id', '3'), -(17, 1, 'community-events-location', 'a:1:{s:2:\"ip\";s:11:\"85.73.218.0\";}'), +(17, 1, 'community-events-location', 'a:1:{s:2:\"ip\";s:10:\"77.69.15.0\";}'), (18, 1, 'meta-box-order_dashboard', 'a:4:{s:6:\"normal\";s:19:\"dashboard_right_now\";s:4:\"side\";s:21:\"dashboard_quick_press\";s:7:\"column3\";s:18:\"dashboard_activity\";s:7:\"column4\";s:17:\"dashboard_primary\";}'), (19, 1, 'wp_user-settings', 'libraryContent=browse&editor=html&post_dfw=off'), (20, 1, 'wp_user-settings-time', '1501011051'), @@ -758,7 +760,7 @@ ALTER TABLE `wp_links` -- AUTO_INCREMENT for table `wp_options` -- ALTER TABLE `wp_options` - MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=192; + MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=212; -- -- AUTO_INCREMENT for table `wp_postmeta` -- diff --git a/wp-content/themes/gwtd3/functions.php b/wp-content/themes/gwtd3/functions.php index a122465..2ae1d11 100644 --- a/wp-content/themes/gwtd3/functions.php +++ b/wp-content/themes/gwtd3/functions.php @@ -134,7 +134,7 @@ function gwtd3_scripts() { wp_enqueue_style( 'dashicons' ); - wp_enqueue_style( 'gwtd3-fonts', 'https://fonts.googleapis.com/css?family=Changa:400,700|Open+Sans:400,400i,600,700' ); + wp_enqueue_style( 'gwtd3-fonts', 'https://fonts.googleapis.com/css?family=Changa:400,600,700|Open+Sans:400,400i,600,700' ); wp_enqueue_script( 'gwtd3-navigation', get_template_directory_uri() . '/js/navigation.js', array(), '20170725', true ); diff --git a/wp-content/themes/gwtd3/img/questionmark.png b/wp-content/themes/gwtd3/img/questionmark.png index 03fea4a..65851e1 100644 Binary files a/wp-content/themes/gwtd3/img/questionmark.png and b/wp-content/themes/gwtd3/img/questionmark.png differ diff --git a/wp-content/themes/gwtd3/img/questionmark.svg b/wp-content/themes/gwtd3/img/questionmark.svg index 31f540a..5cadf2f 100644 --- a/wp-content/themes/gwtd3/img/questionmark.svg +++ b/wp-content/themes/gwtd3/img/questionmark.svg @@ -1 +1 @@ -gwtd3Asset 2 \ No newline at end of file +gwtd3Asset 18 \ No newline at end of file diff --git a/wp-content/themes/gwtd3/js/scripts.js b/wp-content/themes/gwtd3/js/scripts.js index d4b7840..a1e8ec7 100644 --- a/wp-content/themes/gwtd3/js/scripts.js +++ b/wp-content/themes/gwtd3/js/scripts.js @@ -8,12 +8,15 @@ function toggleNav() { if ( $( '#site-wrapper' ).hasClass( 'show-nav' ) ) { $( '#site-wrapper' ).removeClass( 'show-nav' ); + $( '#mobile-menu-trigger .dashicons' ).removeClass( 'dashicons-no' ); + $( '#mobile-menu-trigger .dashicons' ).addClass( 'dashicons-menu' ); } else { $( '#site-wrapper' ).addClass( 'show-nav' ); + $( '#mobile-menu-trigger .dashicons' ).removeClass( 'dashicons-menu' ); + $( '#mobile-menu-trigger .dashicons' ).addClass( 'dashicons-no' ); } } - $( window ).scroll( function() { if ( $( this ).scrollTop() < 400 ) { $( '#to-top' ).fadeOut(); @@ -22,6 +25,14 @@ } } ); + $( window ).resize(function() { + if ( $( '#site-wrapper' ).hasClass( 'show-nav' ) ) { + $( '#site-wrapper' ).removeClass( 'show-nav' ); + $( '#mobile-menu-trigger .dashicons' ).removeClass( 'dashicons-no' ); + $( '#mobile-menu-trigger .dashicons' ).addClass( 'dashicons-menu' ); + } + }); + $( 'a[href*=\\#]' ).on( 'click', function( event ) { if ( $( this ).attr( 'id' ) === 'smoothup' ) { $( 'html, body' ).animate( { diff --git a/wp-content/themes/gwtd3/landing-page.php b/wp-content/themes/gwtd3/landing-page.php index 3b7ca0b..31254a7 100644 --- a/wp-content/themes/gwtd3/landing-page.php +++ b/wp-content/themes/gwtd3/landing-page.php @@ -10,9 +10,6 @@
-
- -
post_title; @@ -32,9 +29,6 @@
-
- -
post_title; @@ -54,9 +48,6 @@
-
- -
post_title; diff --git a/wp-content/themes/gwtd3/style.css b/wp-content/themes/gwtd3/style.css index ccdc50b..6429d27 100644 --- a/wp-content/themes/gwtd3/style.css +++ b/wp-content/themes/gwtd3/style.css @@ -4,7 +4,7 @@ Theme URI: http://underscores.me/ Author: TBD... Author URI: https://multiple_wordpress_awesome.contributors Description: The most awesome theme for gwtd3! -Version: 1.0.3 +Version: 1.0.4 License: GNU General Public License v2 or later License URI: LICENSE Text Domain: gwtd3 @@ -52,6 +52,10 @@ h1, h2, h3, h4, h5 { font-weight: 600; } +strong { + font-weight: 600; +} + /* Colors -------------------------------------------------- */ @@ -229,22 +233,6 @@ h1, h2, h3, h4, h5 { /* LP sections –––––––––––––––––––––––––––––––––––––––––––––––––– */ -.questionmark, -.globe, -.rocket { - display: none; - width: 100%; - text-align:center; - clear: both; - margin-bottom: 4rem; -} - -.questionmark img, -.globe img, -.rocket img { - width: 150px; -} - .section.lp-what-it-is { background: #D5AFBB; color: #471530; @@ -253,13 +241,13 @@ h1, h2, h3, h4, h5 { background-repeat: no-repeat; background-attachment: local; background-position: 8% center; - background-size: 280px; + background-size: 350px; background-origin: content-box; } .section.lp-where-it-is { - background: #5A90AA; - color: #9AD9E1; + background: #54879B; + color: #CFEDF9; background-image: url(img/globe.png); background-image: url(img/globe.svg), linear-gradient(transparent, transparent); background-repeat: no-repeat; @@ -270,12 +258,12 @@ h1, h2, h3, h4, h5 { } .section.lp-where-it-is h2 { - color: #14455B; + color: #17506A; } .section.lp-how-to-get-involved { - background: #21627E; - color: #D5AFBB; + background: #17506A; + color: #E5CFD7; background-image: url(img/rocket.png); background-image: url(img/rocket.svg), linear-gradient(transparent, transparent); background-repeat: no-repeat; @@ -289,6 +277,7 @@ h1, h2, h3, h4, h5 { .section.lp-where-it-is h2, .section.lp-how-to-get-involved h2 { font-size: 8.0rem; + z-index: 10; } /* Header @@ -349,22 +338,32 @@ h1, h2, h3, h4, h5 { } #site-menu { - width: 300px; + width: 200px; height: 100%; position: absolute; top: 0; - left: -300px; + left: -200px; background: #5A90AA; padding: 15px; } #site-wrapper.show-nav #site-canvas { - -webkit-transform: translateX(300px); - transform: translateX(300px); + -webkit-transform: translateX(200px); + transform: translateX(200px); } #site-menu ul { list-style: none; + padding: 0; + margin: 0; +} + +#site-menu ul li { + text-align: center; +} + +#site-menu #gwtd-menu { + margin-top: 5rem; } #mobile-menu-trigger { @@ -438,7 +437,7 @@ h1, h2, h3, h4, h5 { .section.lp-what-it-is h2, .section.lp-where-it-is h2, .section.lp-how-to-get-involved h2 { - font-size: 6.0rem; + font-size: 5.0rem; } .footer h2 { @@ -462,19 +461,15 @@ h1, h2, h3, h4, h5 { .section.lp-what-it-is h2, .section.lp-where-it-is h2, .section.lp-how-to-get-involved h2 { - font-size: 3.5rem; - } - - .questionmark, - .globe, - .rocket { - display: block; + margin: 5rem 0; } .section.lp-what-it-is, .section.lp-where-it-is, .section.lp-how-to-get-involved { - background-image: none; + background-position: 20px 20px; + background-size: 200px; + background-origin: padding-box; } .section.primary-menus .columns { display: none;