INSERT INTO `wp_fovr_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(42247, '_transient_timeout_external_ip_address_39.36.242.255', '1497705490', 'no'),
(42248, '_transient_external_ip_address_39.36.242.255', '192.185.2.88', 'no'),
(42250, '_transient_timeout_external_ip_address_39.36.60.249', '1497848770', 'no'),
(42251, '_transient_external_ip_address_39.36.60.249', '192.185.2.88', 'no'),
(42431, '_transient_timeout_external_ip_address_182.186.184.94', '1497934380', 'no'),
(42432, '_transient_external_ip_address_182.186.184.94', '192.185.2.88', 'no'),
(42433, '_transient_timeout_external_ip_address_182.186.144.44', '1497934954', 'no'),
(42434, '_transient_external_ip_address_182.186.144.44', '192.185.2.88', 'no'),
(42437, '_transient_timeout_external_ip_address_39.36.56.52', '1497935556', 'no'),
(42438, '_transient_external_ip_address_39.36.56.52', '192.185.2.88', 'no'),
(43333, 'megamenu_themes_last_updated', 'default', 'no'),
(43334, 'megamenu_toggle_blocks', 'a:1:{s:7:"default";a:1:{i:1;a:9:{s:4:"type";s:11:"menu_toggle";s:5:"align";s:5:"right";s:11:"closed_text";s:4:"MENU";s:9:"open_text";s:4:"MENU";s:11:"closed_icon";s:9:"dash-f333";s:9:"open_icon";s:9:"dash-f153";s:10:"text_color";s:7:"#ffffff";s:10:"icon_color";s:7:"#ffffff";s:13:"icon_position";s:5:"after";}}}', 'no'),
(43344, 'woocommerce_permalinks', 'a:4:{s:13:"category_base";s:0:"";s:8:"tag_base";s:0:"";s:14:"attribute_base";s:0:"";s:12:"product_base";s:19:"/shop/%product_cat%";}', 'yes'),
(43365, 'yith_wcmg_slider_direction', 'left', 'yes'),
(43443, '_transient_wc_related_1584', 'a:4:{i:0;s:4:"1895";i:1;s:4:"1893";i:2;s:4:"1892";i:3;s:4:"1894";}', 'no'),
(43359, '_transient_timeout_wc_related_1900', '1499759398', 'no'),
(43360, '_transient_wc_related_1900', 'a:4:{i:0;s:4:"1902";i:1;s:4:"1901";i:2;s:4:"1588";i:3;s:4:"1903";}', 'no'),
(43366, 'yith_wcas_general_videobox', 'a:7:{s:11:"plugin_name";s:31:"YITH WooCommerce Zoom Magnifier";s:18:"title_first_column";s:30:"Discover The Advanced Features";s:24:"description_first_column";s:95:"Upgrade to the PREMIUM VERSION of YITH WOOCOMMERCE ZOOM MAGNIFIER to benefit from all features!";s:5:"video";a:3:{s:8:"video_id";s:9:"122436840";s:15:"video_image_url";s:138:"http://wisedezine.com/abexports/wp-content/plugins/yith-woocommerce-zoom-magnifier/assets/images/yith-woocommerce-zoom-magnifier-video.jpg";s:17:"video_description";s:79:"See YITH WooCommerce Zoom Magnifier plugin with full premium features in action";}s:19:"title_second_column";s:28:"Get Support and Pro Features";s:25:"description_second_column";s:206:"By purchasing the premium version of the plugin, you will take advantage of the advanced features of the product, and you will get one year of free updates and support through our platform available 24h/24.";s:6:"button";a:2:{s:4:"href";s:84:"http://yithemes.com/themes/plugins/yith-woocommerce-zoom-magnifier/?refer_id=1030585";s:5:"title";s:28:"Get Support and Pro Features";}}', 'yes'),
(43400, 'widget_nextendaccordionmenuwidget', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'),
(43367, 'yith_wcmg_enable_plugin', 'yes', 'yes'),
(43368, 'yith_wcmg_enable_mobile', 'yes', 'yes'),
(43369, 'yith_wcmg_force_sizes', 'yes', 'yes'),
(43370, 'yith_wcmg_zoom_width', '300', 'yes'),
(43371, 'yith_wcmg_zoom_height', '300', 'yes'),
(43372, 'woocommerce_magnifier_image', 'a:3:{s:5:"width";s:3:"600";s:6:"height";s:3:"600";s:4:"crop";s:2:"on";}', 'yes'),
(43373, 'yith_wcmg_zoom_position', 'inside', 'yes'),
(43374, 'yith_wcmg_zoom_mobile_position', 'inside', 'yes'),
(43375, 'yith_wcmg_loading_label', 'Loading...', 'yes'),
(43376, 'yith_wcmg_lens_opacity', '0.5', 'yes'),
(43377, 'yith_wcmg_softfocus', 'no', 'yes'),
(43378, 'yith_wcmg_enableslider', 'yes', 'yes'),
(43379, 'yith_wcmg_slider_responsive', 'yes', 'yes'),
(43380, 'yith_wcmg_slider_items', '3', 'yes'),
(43381, 'yith_wcmg_slider_circular', 'yes', 'yes'),
(43382, 'yith_wcmg_slider_infinite', 'yes', 'yes'),
(43496, 'zoooom_activation_time', '1499837574', 'yes'),
(43497, 'zoooom_version', '1.13', 'yes'),
(43498, 'zoooom_settings', 'a:43:{s:9:"lensShape";s:11:"zoom_window";s:10:"cursorType";s:7:"default";s:8:"zwEasing";i:12;s:8:"lensSize";i:200;s:15:"borderThickness";i:1;s:11:"borderColor";s:7:"#ffffff";s:8:"lensFade";d:1;s:4:"tint";b:0;s:9:"tintColor";s:7:"#ffffff";s:11:"tintOpacity";d:0.5;s:7:"zwWidth";i:400;s:8:"zwHeight";i:360;s:9:"zwPadding";i:10;s:17:"zwBorderThickness";i:4;s:8:"zwShadow";i:4;s:13:"zwBorderColor";s:7:"#888888";s:14:"zwBorderRadius";i:0;s:6:"zwFade";d:0;s:18:"enable_woocommerce";b:1;s:19:"exchange_thumbnails";b:1;s:13:"enable_mobile";b:0;s:7:"woo_cat";b:0;s:17:"force_woocommerce";b:1;s:26:"remove_lightbox_thumbnails";b:0;s:15:"remove_lightbox";b:0;s:14:"woo_variations";b:0;s:17:"force_attachments";b:0;s:10:"flexslider";s:0:"";s:15:"enable_fancybox";b:0;s:23:"enable_jetpack_carousel";b:0;s:15:"huge_it_gallery";s:0:"";s:7:"onClick";s:5:"false";s:5:"ratio";s:7:"default";s:10:"lensColour";s:7:"#ffffff";s:11:"lensOverlay";b:0;s:12:"zwResponsive";b:0;s:21:"zwResponsiveThreshold";s:0:"";s:13:"zwPositioning";s:0:"";s:14:"mousewheelZoom";s:0:"";s:10:"customText";s:0:"";s:14:"customTextSize";s:0:"";s:15:"customTextColor";s:7:"#000000";s:15:"customTextAlign";s:0:"";}', 'yes'),
(43411, 'widget_bqw-accordion-slider-lite-widget', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'),
(43404, '_site_transient_timeout_browser_cc75d7392f9d8bd819fbfacf05f70081', '1500294021', 'no'),
(43405, '_site_transient_browser_cc75d7392f9d8bd819fbfacf05f70081', 'a:9:{s:8:"platform";s:7:"Windows";s:4:"name";s:7:"Firefox";s:7:"version";s:4:"54.0";s:10:"update_url";s:23:"http://www.firefox.com/";s:7:"img_src";s:50:"http://s.wordpress.org/images/browsers/firefox.png";s:11:"img_src_ssl";s:49:"https://wordpress.org/images/browsers/firefox.png";s:15:"current_version";s:2:"16";s:7:"upgrade";b:0;s:8:"insecure";b:0;}', 'no'),
(42741, 'megamenu_version', '2.3.7.1', 'yes'),
(42742, 'megamenu_settings', 'a:3:{s:6:"prefix";s:8:"disabled";s:12:"descriptions";s:7:"enabled";s:7:"primary";a:4:{s:5:"event";s:5:"hover";s:6:"effect";s:7:"fade_up";s:12:"effect_speed";s:3:"200";s:5:"theme";s:7:"default";}}', 'yes'),
(42829, '_site_transient_timeout_browser_e7f3f4c74154f498c364b3de62d0ebab', '1498715015', 'no'),
(42830, '_site_transient_browser_e7f3f4c74154f498c364b3de62d0ebab', 'a:9:{s:8:"platform";s:7:"Windows";s:4:"name";s:6:"Chrome";s:7:"version";s:12:"59.0.3071.86";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'),
(43032, '_transient_external_ip_address_182.186.179.114', '192.185.2.88', 'no'),
(43043, '_transient_timeout_external_ip_address_39.36.17.132', '1499577316', 'no'),
(43044, '_transient_external_ip_address_39.36.17.132', '192.185.2.88', 'no'),
(43276, '_transient_timeout_wc_related_1612', '1499599088', 'no'),
(43277, '_transient_wc_related_1612', 'a:4:{i:0;s:4:"2112";i:1;s:4:"2113";i:2;s:4:"2114";i:3;s:4:"2115";}', 'no'),
(42566, '_transient_external_ip_address_182.186.140.105', '192.185.2.88', 'no'),
(42570, '_transient_timeout_external_ip_address_43.245.8.189', '1498056861', 'no'),
(42600, '_transient_timeout_external_ip_address_64.233.172.175', '1498108749', 'no'),
(42601, '_transient_external_ip_address_64.233.172.175', '503 Over Quota Error &nbsp; Over Quota This application is temporarily over its serving quota. Please try again later.', 'no'),
(42714, '_transient_timeout_external_ip_address_39.36.8.53', '1498542539', 'no'),
(43085, '_transient_external_ip_address_104.45.18.178', '192.185.2.88', 'no'),
(42776, 'widget_rommeled_image', 'a:2:{i:2;a:15:{s:4:"sort";s:0:"";s:5:"image";s:75:"http://wisedezine.com/abexports/wp-content/uploads/2017/06/CC-2.jpg?id=2272";s:5:"title";s:13:"HOME TEXTILES";s:11:"inner-title";s:0:"";s:4:"text";s:0:"";s:6:"button";s:0:"";s:3:"url";s:21:"http/:wisedezine.com/";s:10:"url_target";s:0:"";s:4:"size";s:14:"shop_thumbnail";s:5:"style";s:9:"img-round";s:16:"title-visibility";s:2:"on";s:12:"class_custom";s:0:"";s:17:"mega_menu_columns";i:2;s:15:"mega_menu_order";a:1:{i:2734;i:5;}s:24:"mega_menu_parent_menu_id";i:2734;}s:12:"_multiwidget";i:1;}', 'yes'),
(42562, '_transient_timeout_external_ip_address_39.36.181.202', '1498048311', 'no'),
(42563, '_transient_external_ip_address_39.36.181.202', '503 Over Quota Error &nbsp; Over Quota This application is temporarily over its serving quota. Please try again later.', 'no'),
(42565, '_transient_timeout_external_ip_address_182.186.140.105', '1498048593', 'no'),
(42718, '_transient_external_ip_address_39.36.20.241', '192.185.2.88', 'no'),
(42571, '_transient_external_ip_address_43.245.8.189', '192.185.2.88', 'no'),
(42573, '_transient_timeout_external_ip_address_39.36.135.148', '1498105927', 'no'),
(42574, '_transient_external_ip_address_39.36.135.148', '192.185.2.88', 'no'),
(42740, 'widget_maxmegamenu', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'),
(43083, '_transient_external_ip_address_178.152.111.203', '192.185.2.88', 'no'),
(43084, '_transient_timeout_external_ip_address_104.45.18.178', '1499704638', 'no'),
(42797, '_transient_timeout_external_ip_address_182.186.231.215', '1498562907', 'no'),
(42798, '_transient_external_ip_address_182.186.231.215', '192.185.2.88', 'no'),
(42807, '_transient_timeout_external_ip_address_182.186.243.62', '1498563809', 'no'),
(42808, '_transient_external_ip_address_182.186.243.62', '503 Over Quota Error &nbsp; Over Quota This application is temporarily over its serving quota. Please try again later.', 'no'),
(42809, '_transient_timeout_external_ip_address_103.255.4.11', '1498563836', 'no'),
(42612, 'cgmp_settings_builder_location', 'false', 'yes'),
(42613, 'cgmp_settings_custom_post_types', '', 'yes'),
(42614, 'cgmp_settings_tinymce_button', 'true', 'yes'),
(42615, 'cgmp_settings_plugin_admin_bar_menu', 'true', 'yes'),
(42616, 'cgmp_settings_map_should_fill_viewport', 'false', 'yes'),
(42679, '_transient_external_ip_address_31.13.110.118', '192.185.2.88', 'no'),
(42680, '_transient_timeout_external_ip_address_162.156.182.25', '1498370239', 'no'),
(42681, '_transient_external_ip_address_162.156.182.25', '192.185.2.88', 'no'),
(42682, '_transient_timeout_external_ip_address_39.36.146.184', '1498373722', 'no'),
(42683, '_transient_external_ip_address_39.36.146.184', '192.185.2.88', 'no'),
(43073, '_transient_timeout_external_ip_address_66.102.6.15', '1499669523', 'no'),
(42699, '_transient_timeout_external_ip_address_39.36.40.142', '1498468977', 'no'),
(42700, '_transient_external_ip_address_39.36.40.142', '192.185.2.88', 'no'),
(43090, '_transient_wc_products_will_display_61_1498112960', '', 'no'),
(43444, '_transient_timeout_wc_related_2454', '1499858160', 'no'),
(43445, '_transient_wc_related_2454', 'a:4:{i:0;s:4:"2460";i:1;s:4:"2463";i:2;s:4:"2462";i:3;s:4:"2461";}', 'no'),
(43093, '_transient_timeout_external_ip_address_66.102.6.19', '1499745679', 'no'),
(43094, '_transient_external_ip_address_66.102.6.19', '192.185.2.88', 'no'),
(42671, '_transient_timeout_external_ip_address_182.186.144.164', '1498370127', 'no'),
(42672, '_transient_external_ip_address_182.186.144.164', '192.185.2.88', 'no'),
(42678, '_transient_timeout_external_ip_address_31.13.110.118', '1498370161', 'no'),
(42749, '_transient_timeout_external_ip_address_182.186.142.232', '1498556343', 'no'),
(42750, '_transient_external_ip_address_182.186.142.232', '192.185.2.88', 'no'),
(43018, '_transient_timeout_external_ip_address_182.186.194.243', '1498890134', 'no'),
(43019, '_transient_external_ip_address_182.186.194.243', '503 Over Quota Error &nbsp; Over Quota This application is temporarily over its serving quota. Please try again later.', 'no'),
(43025, '_transient_timeout_external_ip_address_182.186.176.98', '1498890723', 'no'),
(42746, '_transient_megamenu_css_version', '2.3.7.1', 'yes'),
(43255, '_transient_timeout_wc_shipping_method_count_0_1496640205', '1502085183', 'no'),
(43256, '_transient_wc_shipping_method_count_0_1496640205', '0', 'no'),
(43258, '_transient_timeout_wc_products_will_display_24_1498112960', '1510036877', 'no'),
(43259, '_transient_wc_products_will_display_24_1498112960', '', 'no'),
(43158, '_transient_timeout_wc_related_2462', '1499324237', 'no'),
(43159, '_transient_wc_related_2462', 'a:4:{i:0;s:4:"2460";i:1;s:4:"2463";i:2;s:4:"2454";i:3;s:4:"2461";}', 'no'),
(43160, '_transient_timeout_wc_products_will_display_27_1498112960', '1509634710', 'no'),
(43161, '_transient_wc_products_will_display_27_1498112960', '', 'no'),
(43162, '_transient_timeout_wc_related_2174', '1499325001', 'no'),
(43163, '_transient_wc_related_2174', 'a:4:{i:0;s:4:"1625";i:1;s:4:"2171";i:2;s:4:"2173";i:3;s:4:"2175";}', 'no'),
(43298, 'ls-share-displayed', '2', 'yes'),
(45997, '_site_transient_timeout_browser_a8fa04da005937516d8bdfff00fdbe54', '1507630076', 'no'),
(45998, '_site_transient_browser_a8fa04da005937516d8bdfff00fdbe54', 'a:10:{s:4:"name";s:6:"Chrome";s:7:"version";s:13:"61.0.3163.100";s:8:"platform";s:7:"Windows";s:10:"update_url";s:29:"https://www.google.com/chrome";s:7:"img_src";s:43:"http://s.w.org/images/browsers/chrome.png?1";s:11:"img_src_ssl";s:44:"https://s.w.org/images/browsers/chrome.png?1";s:15:"current_version";s:2:"18";s:7:"upgrade";b:0;s:8:"insecure";b:0;s:6:"mobile";b:0;}', 'no'),
(43548, 'squelch_taas_jquery_ui_theme', 'smoothness', 'yes'),
(43549, 'squelch_taas_v', '0.3.9', 'yes'),
(43570, 'widget_rich_web_photo_slider', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'),
(43251, '_transient_timeout_wc_addons_sections', '1500097945', 'no'),
(43252, '_transient_wc_addons_sections', 'O:8:"stdClass":10:{s:8:"featured";O:8:"stdClass":2:{s:5:"title";s:8:"Featured";s:8:"endpoint";s:59:"https://d3t0oesq8995hv.cloudfront.net/section/featured.json";}s:7:"popular";O:8:"stdClass":2:{s:5:"title";s:7:"Popular";s:8:"endpoint";s:58:"https://d3t0oesq8995hv.cloudfront.net/section/popular.json";}s:16:"payment_gateways";O:8:"stdClass":2:{s:5:"title";s:16:"Payment Gateways";s:8:"endpoint";s:67:"https://d3t0oesq8995hv.cloudfront.net/section/payment_gateways.json";}s:16:"shipping_methods";O:8:"stdClass":2:{s:5:"title";s:16:"Shipping Methods";s:8:"endpoint";s:67:"https://d3t0oesq8995hv.cloudfront.net/section/shipping_methods.json";}s:13:"import_export";O:8:"stdClass":2:{s:5:"title";s:13:"Import/Export";s:8:"endpoint";s:64:"https://d3t0oesq8995hv.cloudfront.net/section/import_export.json";}s:10:"accounting";O:8:"stdClass":2:{s:5:"title";s:10:"Accounting";s:8:"endpoint";s:61:"https://d3t0oesq8995hv.cloudfront.net/section/accounting.json";}s:9:"marketing";O:8:"stdClass":2:{s:5:"title";s:9:"Marketing";s:8:"endpoint";s:60:"https://d3t0oesq8995hv.cloudfront.net/section/marketing.json";}s:7:"product";O:8:"stdClass":2:{s:5:"title";s:8:"Products";s:8:"endpoint";s:58:"https://d3t0oesq8995hv.cloudfront.net/section/product.json";}s:4:"free";O:8:"stdClass":2:{s:5:"title";s:4:"Free";s:8:"endpoint";s:55:"https://d3t0oesq8995hv.cloudfront.net/section/free.json";}s:11:"third_party";O:8:"stdClass":2:{s:5:"title";s:11:"Third-party";s:8:"endpoint";s:62:"https://d3t0oesq8995hv.cloudfront.net/section/third_party.json";}}', 'no'),
(43253, '_transient_timeout_wc_addons_featured', '1500097945', 'no'),
(43254, '_transient_wc_addons_featured', 'O:8:"stdClass":1:{s:8:"sections";a:11:{i:0;O:8:"stdClass":4:{s:6:"module";s:12:"banner_block";s:5:"title";s:50:"Take your store beyond the typical - sell anything";s:11:"description";s:83:"From services to content, there’s no limit to what you can sell with WooCommerce.";s:5:"items";a:3:{i:0;O:8:"stdClass":6:{s:4:"href";s:118:"https://woocommerce.com/products/woocommerce-subscriptions/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:13:"Subscriptions";s:5:"image";s:71:"https://d3t0oesq8995hv.cloudfront.net/add-ons/subscriptions-icon@2x.png";s:11:"description";s:98:"Let customers subscribe to your products or services and pay on a weekly, monthly or annual basis.";s:6:"button";s:10:"From: $199";s:6:"plugin";s:55:"woocommerce-subscriptions/woocommerce-subscriptions.php";}i:1;O:8:"stdClass":6:{s:4:"href";s:113:"https://woocommerce.com/products/woocommerce-bookings/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:8:"Bookings";s:5:"image";s:66:"https://d3t0oesq8995hv.cloudfront.net/add-ons/bookings-icon@2x.png";s:11:"description";s:76:"Allow customers to book appointments for services without leaving your site.";s:6:"button";s:10:"From: $249";s:6:"plugin";s:45:"woocommerce-bookings/woocommerce-bookings.php";}i:2;O:8:"stdClass":6:{s:4:"href";s:116:"https://woocommerce.com/products/woocommerce-memberships/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:11:"Memberships";s:5:"image";s:69:"https://d3t0oesq8995hv.cloudfront.net/add-ons/memberships-icon@2x.png";s:11:"description";s:76:"Give members access to restricted content or products, for a fee or for free";s:6:"button";s:10:"From: $149";s:6:"plugin";s:51:"woocommerce-memberships/woocommerce-memberships.php";}}}i:1;O:8:"stdClass":1:{s:6:"module";s:16:"wcs_banner_block";}i:2;O:8:"stdClass":2:{s:6:"module";s:12:"column_start";s:9:"container";s:22:"column_container_start";}i:3;O:8:"stdClass":4:{s:6:"module";s:12:"column_block";s:5:"title";s:46:"Improve the main features of your online store";s:11:"description";s:71:"Sell more by helping customers find the products and options they want.";s:5:"items";a:3:{i:0;O:8:"stdClass":6:{s:4:"href";s:108:"https://woocommerce.com/products/product-add-ons/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:15:"Product Add-ons";s:5:"image";s:73:"https://d3t0oesq8995hv.cloudfront.net/add-ons/product-add-ons-icon@2x.png";s:11:"description";s:82:"Give your customers the option to customize their purchase or add personalization.";s:6:"button";s:9:"From: $49";s:6:"plugin";s:57:"woocommerce-product-addons/woocommerce-product-addons.php";}i:1;O:8:"stdClass":6:{s:4:"href";s:119:"https://woocommerce.com/products/woocommerce-product-search/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:14:"Product Search";s:5:"image";s:72:"https://d3t0oesq8995hv.cloudfront.net/add-ons/product-search-icon@2x.png";s:11:"description";s:67:"Make sure customers find what they want when they search your site.";s:6:"button";s:9:"From: $49";s:6:"plugin";s:57:"woocommerce-product-search/woocommerce-product-search.php";}i:2;O:8:"stdClass":6:{s:4:"href";s:121:"https://woocommerce.com/products/woocommerce-checkout-add-ons/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:16:"Checkout Add-ons";s:5:"image";s:74:"https://d3t0oesq8995hv.cloudfront.net/add-ons/checkout-add-ons-icon@2x.png";s:11:"description";s:89:"Highlight relevant products, offers like free shipping and other upsells during checkout.";s:6:"button";s:9:"From: $49";s:6:"plugin";s:61:"woocommerce-checkout-add-ons/woocommerce-checkout-add-ons.php";}}}i:4;O:8:"stdClass":5:{s:6:"module";s:17:"small_light_block";s:5:"title";s:34:"Get the official WooCommerce theme";s:11:"description";s:128:"Storefront is the lean, flexible, and free theme, built by the people who make WooCommerce - everything you need to get started.";s:5:"image";s:70:"https://d3t0oesq8995hv.cloudfront.net/add-ons/storefront-screen@2x.png";s:7:"buttons";a:2:{i:0;O:8:"stdClass":2:{s:4:"href";s:44:"/wp-admin/theme-install.php?theme=storefront";s:4:"text";s:7:"Install";}i:1;O:8:"stdClass":2:{s:4:"href";s:94:"https://woocommerce.com/storefront/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:4:"text";s:9:"Read More";}}}i:5;O:8:"stdClass":1:{s:6:"module";s:10:"column_end";}i:6;O:8:"stdClass":1:{s:6:"module";s:12:"column_start";}i:7;O:8:"stdClass":4:{s:6:"module";s:16:"small_dark_block";s:5:"title";s:20:"Square + WooCommerce";s:11:"description";s:176:"Keep your WooCommerce and brick-and-mortar stores in sync. Use Square to take payments both online and offline, keep inventory updated between the two and sync product changes.";s:5:"items";a:1:{i:0;O:8:"stdClass":2:{s:4:"href";s:99:"https://woocommerce.com/products/square/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:6:"button";s:9:"From: $79";}}}i:8;O:8:"stdClass":4:{s:6:"module";s:12:"column_block";s:5:"title";s:19:"Get deeper insights";s:11:"description";s:58:"Learn how your store is performing with enhanced reporting";s:5:"items";a:3:{i:0;O:8:"stdClass":6:{s:4:"href";s:121:"https://woocommerce.com/products/woocommerce-google-analytics/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:16:"Google Analytics";s:5:"image";s:60:"https://d3t0oesq8995hv.cloudfront.net/add-ons/ga-icon@2x.png";s:11:"description";s:93:"Understand your customers and increase revenue with the world’s leading analytics platform.";s:6:"button";s:4:"Free";s:6:"plugin";s:85:"woocommerce-google-analytics-integration/woocommerce-google-analytics-integration.php";}i:1;O:8:"stdClass":6:{s:4:"href";s:117:"https://woocommerce.com/products/woocommerce-cart-reports/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:12:"Cart reports";s:5:"image";s:70:"https://d3t0oesq8995hv.cloudfront.net/add-ons/cart-reports-icon@2x.png";s:11:"description";s:66:"Get real-time reports on what customers are leaving in their cart.";s:6:"button";s:9:"From: $79";s:6:"plugin";s:53:"woocommerce-cart-reports/woocommerce-cart-reports.php";}i:2;O:8:"stdClass":6:{s:4:"href";s:118:"https://woocommerce.com/products/woocommerce-cost-of-goods/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:13:"Cost of Goods";s:5:"image";s:71:"https://d3t0oesq8995hv.cloudfront.net/add-ons/cost-of-goods-icon@2x.png";s:11:"description";s:64:"Easily track profit by including  cost of goods in your reports.";s:6:"button";s:9:"From: $79";s:6:"plugin";s:55:"woocommerce-cost-of-goods/woocommerce-cost-of-goods.php";}}}i:9;O:8:"stdClass":2:{s:6:"module";s:10:"column_end";s:9:"container";s:20:"column_container_end";}i:10;O:8:"stdClass":4:{s:6:"module";s:12:"banner_block";s:5:"title";s:40:"Promote your products and increase sales";s:11:"description";s:77:"From coupons to emails, these extensions can power up your marketing efforts.";s:5:"items";a:3:{i:0;O:8:"stdClass":6:{s:4:"href";s:106:"https://woocommerce.com/products/smart-coupons/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:13:"Smart Coupons";s:5:"image";s:71:"https://d3t0oesq8995hv.cloudfront.net/add-ons/smart-coupons-icon@2x.png";s:11:"description";s:106:"Enhance your coupon options - create gift certificates, store credit, coupons based on purchases and more.";s:6:"button";s:9:"From: $99";s:6:"plugin";s:55:"woocommerce-smart-coupons/woocommerce-smart-coupons.php";}i:1;O:8:"stdClass":6:{s:4:"href";s:109:"https://woocommerce.com/products/follow-up-emails/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:16:"Follow Up Emails";s:5:"image";s:74:"https://d3t0oesq8995hv.cloudfront.net/add-ons/follow-up-emails-icon@2x.png";s:11:"description";s:140:"Automatically contact customers after purchase - be it everyone, your most loyal or your biggest spenders - and keep your store top-of-mind.";s:6:"button";s:9:"From: $99";s:6:"plugin";s:61:"woocommerce-follow-up-emails/woocommerce-follow-up-emails.php";}i:2;O:8:"stdClass":6:{s:4:"href";s:112:"https://woocommerce.com/products/google-product-feed/?utm_source=product&utm_medium=upsell&utm_campaign=wcaddons";s:5:"title";s:19:"Google Product Feed";s:5:"image";s:77:"https://d3t0oesq8995hv.cloudfront.net/add-ons/google-product-feed-icon@2x.png";s:11:"description";s:61:"Let customers find you when shopping for products via Google.";s:6:"button";s:9:"From: $79";s:6:"plugin";s:45:"woocommerce-product-feeds/woocommerce-gpf.php";}}}}}', 'no'),
(43442, '_transient_timeout_wc_related_1584', '1499858099', 'no'),
(46035, '_transient_timeout_feed_b9388c83948825c1edaef0d856b7b109', '1507089383', 'no'),
(44250, '_transient_timeout_wc_related_2002', '1501928675', 'no'),
(44251, '_transient_wc_related_2002', 'a:4:{i:0;s:4:"2003";i:1;s:4:"2005";i:2;s:4:"2004";i:3;s:4:"1997";}', 'no'),
(44253, '_transient_timeout_wc_related_1603', '1501929533', 'no'),
(44254, '_transient_wc_related_1603', 'a:4:{i:0;s:4:"1941";i:1;s:4:"1942";i:2;s:4:"1943";i:3;s:4:"1945";}', 'no'),
(46210, '_transient_timeout_wc_related_1624', '1507581948', 'no'),
(46211, '_transient_wc_related_1624', 'a:14:{i:0;s:4:"1629";i:1;s:4:"1628";i:2;s:4:"1627";i:3;s:4:"1625";i:4;s:4:"1623";i:5;s:4:"1622";i:6;s:4:"1621";i:7;s:4:"1620";i:8;s:4:"1619";i:9;s:4:"1626";i:10;s:4:"2186";i:11;s:4:"2188";i:12;s:4:"2190";i:13;s:4:"2191";}', 'no'),
(44331, '_transient_timeout_wc_related_2186', '1502395118', 'no'),
(44332, '_transient_wc_related_2186', 'a:4:{i:0;s:4:"1624";i:1;s:4:"2188";i:2;s:4:"2190";i:3;s:4:"2191";}', 'no'),
(44326, '_transient_timeout_wc_related_2191', '1502395115', 'no'),
(44327, '_transient_wc_related_2191', 'a:4:{i:0;s:4:"1624";i:1;s:4:"2186";i:2;s:4:"2188";i:3;s:4:"2190";}', 'no'),
(46031, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1507089382', 'no');
INSERT INTO `wp_fovr_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(46032, '_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:87:"WPTavern: Regenerate Thumbnails Plugin Passes 5 Million Downloads, Rewrite in the Works";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74186";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/regenerate-thumbnails-plugin-passes-5-million-downloads-rewrite-in-the-works";s: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:4603:"<p><a href="https://wordpress.org/plugins/regenerate-thumbnails/" rel="noopener" target="_blank">Regenerate Thumbnails</a>, written by prolific plugin developer <a href="https://alex.blog/" rel="noopener" target="_blank">Alex Mills</a>, has passed 5 million downloads. The plugin was first released nearly a decade ago in August 2008 during the days of WordPress 2.6. Regenerate Thumbnails is used to retroactively generate new thumbnail sizes for past uploads. It has become an indispensable utility over the years, helping millions of users successfully transition between WordPress themes that have different featured image sizes.</p>\n<a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/08/regenerate-thumbnails-v-1.png?ssl=1"><img /></a>Regenerate Thumbnails version 1.0.0\n<p>&#8220;I was freelancing at the time and according to an ancient post on my blog, I apparently wrote it as a client needed the functionality,&#8221; Mills said. &#8220;I don&#8217;t remember that though and I certainly never figured it&#8217;d be installed and activated on over a million sites like it is today!&#8221;</p>\n<p>Regenerate Thumbnails is downloaded thousands of times every day, and, fortunately, it is the type of plugin that doesn&#8217;t generate too many support issues. Mills said he is thankful for the many volunteers on the WordPress.org support forums who have also helped manage the load. Despite the continued and widespread use of the plugin, Mills has never considered cashing in on it.</p>\n<p>&#8220;I&#8217;d never monetize any of my plugins,&#8221; he said. &#8220;I write them for fun not profit. It would be a conflict of interest anyway due to my employment at Automattic.&#8221;</p>\n<p>Regenerate Thumbnails is a fairly straightforward plugin that rarely requires updating, but this year Mills said he has tried to give it a lot more love and will soon be releasing a complete rewrite.</p>\n<p>&#8220;The rewrite is currently taking place on <a href="https://github.com/Viper007Bond/regenerate-thumbnails" rel="noopener" target="_blank">GitHub</a> and is a complete rethink of the plugin, both in terms of the interface and underlying technologies,&#8221; Mills said. &#8220;The interface is powered by Vue.js, which I&#8217;m learning and using for the first time, and the WordPress REST API. I also have a full suite of unit tests for PHPUnit to verify that the plugin code is working as intended, both now and into the future. Those have been incredibly useful while writing the plugin and I highly recommend other plugin authors make use of them too. <a href="https://make.wordpress.org/cli/handbook/plugin-unit-tests/" rel="noopener" target="_blank">WP-CLI makes it very easy to set up</a>.&#8221;</p>\n<p>After nine years of supporting Regenerate Thumbnails, and many other plugins, Mills said he doesn&#8217;t consider himself the best example when it comes to maintaining plugins. His advice to other developers is &#8220;try to make sure to write your plugins to be future-proof.&#8221;</p>\n<p>&#8220;Outside of some updates last month, the last real changes to the plugin were made in 2012!&#8221; Mills said. &#8220;I wrote the plugin well the first time around and it&#8217;s just worked mostly fine ever since because it uses built-in WordPress code to do the work.&#8221;</p>\n<p>This is the reason why Regenerate Thumbnails has already blazed past its major milestone at 5,762,713 downloads and is well on its way to 6 million before the end of the year. Users still find the plugin to work as reliably as it did in 2008.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Have loved this plugin for years, just used it to relaunch a website with 50000 images and 30 image sizes.</p>\n<p>&mdash; Scott Fennell (@scottfennell123) <a href="https://twitter.com/scottfennell123/status/896933624657756160?ref_src=twsrc%5Etfw">August 14, 2017</a></p></blockquote>\n<p></p>\n<p>Mills said that making a plugin future proof is key if you write code all day for a living and then find it difficult to write more in the evenings and weekends for WordPress.org plugins. However, due to his current illness, he hasn&#8217;t worked in nearly a year since October 2016.</p>\n<p>&#8220;While I&#8217;m still battling the leukemia, I&#8217;m at least feeling better than I was at the beginning of the year so I&#8217;ve gotten the itch to code again,&#8221; Mills said. &#8220;Working on personal projects such as Regenerate Thumbnails has been a good way to brush off my coding skills in anticipation of returning to work. Plus it&#8217;s just fun to code again!&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 02 Oct 2017 21:53: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: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:87:"WPTavern: New WP-CLI Project Aims to Extend Checksum Verification to Plugins and Themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=75100";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:98:"https://wptavern.com/new-wp-cli-project-aims-to-extend-checksum-verification-to-plugins-and-themes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3908:"<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/05/wp-cli-logo.png?ssl=1"><img /></a></p>\n<p>The WP-CLI team is initiating a new project that <a href="https://make.wordpress.org/cli/2017/09/26/wordpress-plugin-and-theme-checksums-project-announcement/" rel="noopener" target="_blank">aims to bring checksum verification to plugins and themes</a>. Checksums are a method of verifying the integrity of files. Three years ago, WP-CLI added the capability of verifying WordPress core checksums using the MD5 algorithm. This is a useful security feature that allows developers to easily see if any files have been modified or compromised.</p>\n<p>The core checksums are handled via WordPress&#8217; official API (https://api.wordpress.org/core/checksums/) and WP-CLI contributors are planning to extend this infrastructure to plugins and themes hosted on WordPress.org.</p>\n<p>&#8220;Having this kind of functionality for plugins and themes as well would be a huge security benefit,&#8221; WP-CLI co-maintainer Alain Schlesser said. &#8220;It would allow you to check the file integrity of an entire site, possibly in an automated fashion. However, there is no centralized way of retrieving the file checksums for plugins or themes yet, and the alternative of downloading the plugins and themes from the official servers first just to check against them is wasteful in terms of resources and bandwidth.&#8221;</p>\n<p>Contributors are currently exploring different options for implementation in a <a href="https://github.com/wp-cli/ideas/issues/6" rel="noopener" target="_blank">discussion on GitHub</a>, inspired by an existing <a href="https://github.com/eriktorsner/wp-checksum" rel="noopener" target="_blank">wp-checksum project</a> by Erik Torsner.</p>\n<p>&#8220;The simplest possible infrastructure to go with would be flat files (no database),&#8221; WP-CLI maintainer Daniel Bachhuber said. &#8220;I&#8217;ve chatted with the corresponding WordPress.org folks about hosting. If our middleware application can generate flat files served by some API, then it will be fine to sync those flat files to a WordPress.org server (with rsync or similar).&#8221;</p>\n<p>The team is considering building the API under a separate URL for testing and iteration and then incorporating it back into WordPress.org&#8217;s infrastructure once it is ready. However, the sheer size of the SVN checkouts and the CPU required to sync the files makes it an interesting challenge. DreamHost has volunteered a server for the team to run its checksum generator on while the infrastructure is being developed.</p>\n<p>Torsner&#8217;s WP-CLI subcommand to verify checksums for themes and plugins currently only works with those hosted on WordPress.org, but he is also experimenting with mechanisms for getting checksums from some commercial vendors, including Gravity Forms and Easy Digital Downloads. He said he hopes the project would be capable of keeping these capabilities for commercial plugins after it is incorporated back into WordPress.org.</p>\n<p>The Plugin and Themes Checksums project is currently in the initiation stage and will have an official kickofff during the next WP-CLI meeting on <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=20171003T1600" rel="noopener" target="_blank">Tuesday, October 3, 2017, at 11:00 AM CDT</a>. Anyone who would like to volunteer is encouraged to attend, especially those with an interest in security, systems administration, and the technology required to get this project off the ground.</p>\n<p>&#8220;This project will have a huge impact on the perceived and effective security of WordPress installations,&#8221; Schlesser said. &#8220;It can greatly reduce the amount of malware-infested sites plaguing the internet, and through the substantial market share of WordPress, improve the general browsing experience for all net citizens.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 02 Oct 2017 18:37:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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:48:"Dev Blog: The Month in WordPress: September 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=4920";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://wordpress.org/news/2017/10/the-month-in-wordpress-september-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:5633:"<p>This has been an interesting month for WordPress, as a bold move on the JavaScript front brought the WordPress project to the forefront of many discussions across the development world. There have also been some intriguing changes in the WordCamp program, so read on to learn more about the WordPress community during the month of September.</p>\n<hr />\n<h2>JavaScript Frameworks in WordPress</h2>\n<p>Early in the month, <a href="https://ma.tt/2017/09/on-react-and-wordpress/">Matt Mullenweg announced</a> that WordPress will be switching away from React as the JavaScript library WordPress Core might use — this was in response to Facebook’s decision to keep a controversial patent clause in the library’s license, making many WordPress users uncomfortable.</p>\n<p>A few days later, <a href="https://ma.tt/2017/09/facebook-dropping-patent-clause/">Facebook reverted the decision</a>, making React a viable option for WordPress once more. Still, the WordPress Core team is exploring a move <a href="https://github.com/WordPress/gutenberg/pull/2463">to make WordPress framework-agnostic</a>, so that the framework being used could be replaced by any other framework without affecting the rest of the project.</p>\n<p>This is a bold move that will ultimately make WordPress core a lot more flexible, and will also protect it from potential license changes in the future.</p>\n<p>You can get involved in the JavaScript discussion by joining the #core-js channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a> and following the <a href="https://make.wordpress.org/core/">WordPress Core development blog</a>.</p>\n<h2>Community Initiative to Make WordCamps More Accessible</h2>\n<p>A WordPress community member, Ines van Essen, started a new nonprofit initiative to offer financial assistance to community members to attend WordCamps. <a href="https://donatewc.org/">DonateWC</a> launched with a crowdsourced funding campaign to cover the costs of getting things up and running.</p>\n<p>Now that she’s raised the initial funds, Ines plans to set up a nonprofit organization and use donations from sponsors to help people all over the world attend and speak at WordCamps.</p>\n<p>If you would like to support the initiative, you can do so by <a href="https://donatewc.org/make-a-donation/">donating through their website</a>.</p>\n<h2>The WordCamp Incubator Program Returns</h2>\n<p>Following the success of <a href="https://make.wordpress.org/community/2017/06/30/wordcamp-incubator-report/">the first WordCamp Incubator Program</a>, the Community Team is <a href="https://make.wordpress.org/community/2017/09/27/wordcamp-incubator-program-v2-new-role-name/">bringing the program back</a> to assist more underserved cities in kick-starting their WordPress communities.</p>\n<p>The program’s first phase aims to find community members who will volunteer to mentor, assist, and work alongside local leaders in the incubator communities — this is a time-intensive volunteer role that would need to be filled by experienced WordCamp organizers.</p>\n<p>If you would like to be a part of this valuable initiative, join the #community-team channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a> and follow the <a href="https://make.wordpress.org/community/">Community Team blog</a> for updates.</p>\n<h2>WordPress 4.8.2 Security Release</h2>\n<p>On September 19, <a href="https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/">WordPress 4.8.2 was released to the world</a> — this was a security release that fixed nine issues in WordPress Core, making the platform more stable and secure for everyone.</p>\n<p>To get involved in building WordPress Core, jump into the #core channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a>, and follow <a href="https://make.wordpress.org/core/">the Core team blog</a>.</p>\n<hr />\n<h2>Further Reading:</h2>\n<ul>\n<li>The WordPress Meetup program hit a significant milestone this month — there are now 500 meetup groups in <a href="https://www.meetup.com/pro/wordpress/">the official chapter program</a>.</li>\n<li>The SWFUpload library <a href="https://make.wordpress.org/core/2017/09/07/removing-swfupload/">will be removed from WordPress Core</a> in version 4.9, scheduled for release in mid-November.</li>\n<li>Matías Ventura put together some useful videos on <a href="https://make.wordpress.org/core/2017/08/31/gutenberg-themes/">how theme developers can integrate Gutenberg into their work</a>.</li>\n<li><a href="http://applyfilters.fm/"><i>Apply Filters</i></a>, the popular WordPress development podcast, will go on hiatus after the upcoming 83rd episode.</li>\n<li>The WordPress Plugin Directory <a href="https://make.wordpress.org/plugins/2017/09/04/plugin-support-reps/">has added the ability</a> for plugin owners to assign plugin support representatives.</li>\n<li>After a couple of slower development weeks, <a href="https://make.wordpress.org/core/2017/09/27/whats-new-in-gutenberg-1-2-1/">Gutenberg v1.2 is out</a> and it’s looking better than ever.</li>\n<li>The third <a href="https://wordpress.org/news/2017/09/global-wordpress-translation-day-3/">Global WordPress Translation Day</a> took place this past weekend — keep an eye on <a href="https://make.wordpress.org/polyglots/">the Polyglots team blog</a> for updates.</li>\n</ul>\n<p><em>If you have a story we should consider including in the next “Month in WordPress” post, please <a href="https://make.wordpress.org/community/month-in-wordpress-submissions/">submit it here</a>.</em></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 02 Oct 2017 08:00:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:79:"WPTavern: Gutenberg 1.2 Adds Postmeta Support and Extended Settings Placeholder";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75199";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:90:"https://wptavern.com/gutenberg-1-2-adds-postmeta-support-and-extended-settings-placeholder";s: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:5590:"<p>WordPress contributors have not yet made a final decision on the JavaScript framework to adopt for core, but Gutenberg development continues on with <a href="https://make.wordpress.org/core/2017/09/27/whats-new-in-gutenberg-1-2-1/" rel="noopener" target="_blank">version 1.2</a> released this week.</p>\n<p>The update provides a better experience <a href="https://github.com/WordPress/gutenberg/pull/2708" rel="noopener" target="_blank">resolving block conflicts</a> when switching between the &#8220;classic editor&#8221; and Gutenberg. Previously, if a user had created some paragraph blocks in Gutenberg but switched to the classic editor, the tags would get stripped out, making those blocks invalid when moving back to Gutenberg. Version 1.2 merges a pull request that detects whether the post contains blocks and then disables the wpautop behavior in the classic editor to prevent it from stripping the tags.</p>\n<p>This release also offers initial <a href="https://github.com/WordPress/gutenberg/pull/2740" rel="noopener" target="_blank">support for postmeta</a> in block attributes. Gutenberg contributor Gary Pendergast tweeted <a href="https://gist.github.com/pento/19b35d621709042fc899e394a9387a54" rel="noopener" target="_blank">an example plugin</a> for those who want to experiment with it.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Just between us, the new Gutenberg 1.2 release includes the first version of postmeta support! If you want to start experimenting with it, here''s a sample plugin to get you going. <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="🙂" class="wp-smiley" /><a href="https://t.co/O1GbKZ3xzt">https://t.co/O1GbKZ3xzt</a></p>\n<p>&mdash; Gary (@GaryPendergast) <a href="https://twitter.com/GaryPendergast/status/913623415549976577?ref_src=twsrc%5Etfw">September 29, 2017</a></p></blockquote>\n<p></p>\n<p>Another new item you&#8217;ll notice in version 1.2 is the addition of word and block counts to the table of contents. The value of knowing how many blocks are in play on the page or how many headings have been used is not immediately evident. It strikes me as a rather large and obtrusive display of non-essential information, which for some reason has been given priority placement at the top of the editor.</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-29-at-10.36.02-PM.png?ssl=1"><img /></a></p>\n<p>Gutenberg is getting ready to support metaboxes and this release adds a placeholder for the proposed Extended Settings panel. The <a href="https://github.com/WordPress/gutenberg/pull/2800" rel="noopener" target="_blank">metabox placeholder shell</a> currently sits beneath the content with a &#8220;coming soon&#8221; message.</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-29-at-10.56.48-PM.png?ssl=1"><img /></a></p>\n<p>Developer Ross Wintle <a href="https://github.com/WordPress/gutenberg/pull/2800#issuecomment-332573684" rel="noopener" target="_blank">commented</a> on the pull request with a few concerns about the naming and placement of this panel with notes on how it might impact interfaces that have required meta fields:</p>\n<blockquote><p>\na) Meta boxes currently have several places that they can live: in the sidebar, below post content with different priorities and contexts<br />\nb) I also have cases where I&#8217;ve improved the editing experience for my users by having meta boxes above or below the title because this fits with their content editing flow.<br />\nc) I really don&#8217;t like the &#8220;Extended settings&#8221; title. For some editing workflows the information in meta boxes is actually critical, core content/settings, not something optional/added-on/extended. Is this editable? Can developers add additional sections of their own like this?</p></blockquote>\n<p>Gutenberg engineer Riad Benguella acknowledged these concerns as legitimate and said the team is still exploring different options for the panel.</p>\n<p>&#8220;For the first iteration, we&#8217;ll probably keep the collapsed state but have multiple areas,&#8221; Benguella said. &#8220;There are some good design proposals dropping the expanding area (for the content area) and replacing them with &#8220;separators,&#8221; which might be <a href="https://github.com/WordPress/gutenberg/issues/952#issuecomment-312804592" rel="noopener" target="_blank">good as a v2</a>.&#8221;</p>\n<p>It may have seemed like Gutenberg development has been on hold due to the delayed JavaScript framework decision, but development is still ongoing. It slowed over the past couple weeks while most of the project&#8217;s chief contributors were attending the Automattic GM.</p>\n<p>&#8220;The framework decision doesn’t affect most Gutenberg development work &#8211; because the framework is hidden behind a compatibility layer, the majority of development work (at least, the work that touches the UI) can talk to the compatibility layer,&#8221; contributor Gary Pendergast said.</p>\n<p>&#8220;There are also large areas of code that don’t need the framework at all. For example, adding <a href="https://github.com/WordPress/gutenberg/pull/2740" rel="noopener" target="_blank">postmeta support</a> was just about writing the glue between the Block API and the REST API.&#8221;</p>\n<p>Pendergast said that even once a JavaScript framework decision is made, Gutenberg will only require one or two developers to work on the necessary changes, but all other contributors will be able to continue on without any issues.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 30 Sep 2017 04:21: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: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:111:"WPTavern: DigitalOcean Partners with GitHub to Support Open Source Projects during Hacktoberfest October 1–31";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75163";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:120:"https://wptavern.com/digitalocean-partners-with-github-to-support-open-source-projects-during-hacktoberfest-october-1-31";s: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:2705:"<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-29-at-12.29.22-PM.png?ssl=1"><img /></a></p>\n<p>DigitalOcean is organizing its fourth annual <a href="https://hacktoberfest.digitalocean.com" rel="noopener" target="_blank">Hacktoberfest</a> in partnership with GitHub. The event was created to support open source projects and participants can earn a free t-shirt by contributing four pull requests during the month of October.</p>\n<p>More than 29,000 people signed up for <a href="https://blog.digitalocean.com/open-source-at-its-hacktoberbest/" rel="noopener" target="_blank">Hacktoberfest 2016</a> from 114 countries and 10,227 people completed the challenge. The event tracked a record-breaking 92,569 total PRs opened, up from 49,000 the previous year. Participants contributed to more than 29,000 repositories, spurring progress on thousands of open source projects and making maintainers very busing during the month of October.</p>\n<p>In preparation for the event, maintainers can add the &#8220;Hacktoberfest&#8221; label to issues in their GitHub projects that would be suitable for new contributors to work on. Participants can <a href="https://github.com/search?q=label:hacktoberfest+state:open+type:issue" rel="noopener" target="_blank">browse all the &#8220;Hacktoberfest&#8221; issues</a> if they need some inspiration to get started.</p>\n<p>Both <a href="https://github.com/woocommerce/woocommerce/issues?q=is%3Aissue%20is%3Aopen%20label%3AHacktoberfest" rel="noopener" target="_blank">WooCommerce</a> and <a href="https://github.com/WordPress/gutenberg/labels/Hacktoberfest" rel="noopener" target="_blank">Gutenberg</a> plugin maintainers have already started applying the &#8220;Hacktoberfest&#8221; label to  issues to help WordPress developers find a good entry point for contributing.</p>\n<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-29-at-12.19.21-PM.png?ssl=1"><img /></a></p>\n<p><a href="https://hacktoberfest.digitalocean.com/" rel="noopener" target="_blank">Hacktoberfest</a> begins Sunday, October 1, but participants can sign up anytime between October 1 and October 31. All participants will receive limited-edition Hactoberfest stickers, even if you don&#8217;t complete the four pull requests. Those who complete the challenge before October 31st will be eligible to receive a shirt. Pull requests can be made in any public GitHub-hosted repository and are not limited to those with the Hacktoberfest label.</p>\n<p>Please leave a comment on this post if you have a WordPress-related plugin, theme, or project that has a few designated Hacktoberfest issues for new contributors.</p>\n<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 29 Sep 2017 18:16:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:62:"WPTavern: A Very Brief Introduction to Version Control and Git";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75177";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/a-very-brief-introduction-to-version-control-and-git";s: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:3819:"<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2015/03/petersuhm.jpeg?ssl=1"><img /></a>This post was contributed by guest author <a href="http://petersuhm.com/" target="_blank">Peter Suhm</a>. Peter is a web developer from the Land of the Danes. He is the creator of <a href="https://wptavern.com/wp-pusher-aims-to-provide-pain-free-deployment-of-wordpress-themes-and-plugins-from-github" target="_blank">WP Pusher</a> and a huge travel addict, bringing his work along with him as he goes.<br />\n&nbsp;</p>\n<hr />\n<p>Have you ever done this?</p>\n<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/file-versions.png?ssl=1"><img /></a></p>\n<p>Most of us have.</p>\n<p>Do you know what the technical term for it is? <em>Version control</em>. Your own, homemade, delicious implementation of version control!</p>\n<p>Okay, how about this?</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/commented-code.png?ssl=1"><img /></a></p>\n<p>Version control right there!</p>\n<p>What I’m trying to show with these two examples is that all developers use some sort of version control. Some use Ctrl-z to roll back to a previous version, some use a zipped backup in a Dropbox folder and some use a dedicated version control system (VCS), such as Git. All the things we are trying to accomplish by backing up our files, commenting out old code and stashing it away in another “final-FINAL” zipball has been taken care of already. All we need to do is to embrace these VCS tools that we have available in our tool belt.</p>\n<p>Git is not complicated to use. It might seem difficult and overwhelming but in your day to day life you will probably use a maximum of 3-4 different commands. Learning how to use 3-4 commands to properly have version control of every single change ever made to your code base is a great deal compared to the “final-FINAL” approach.</p>\n<p>Here’s what version control looks like:</p>\n<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/version-control-intro.png?ssl=1"><img /></a></p>\n<p>This is a screenshot of the <a href="https://github.com/WordPress/WordPress" rel="noopener" target="_blank">WordPress Git mirror on GitHub</a>. Every time a change is made to the code base, it is recorded with Git and there is no need to copy the whole code base, throwing it into another folder, zipping it and naming it “final-FINAL-F-I-N-A-L”. If you dive into the WordPress code base on GitHub, you can find <a href="https://github.com/WordPress/WordPress/commit/23f1a9d2a4e9b484290f130e6c80e38e7fdcd453" rel="noopener" target="_blank">commits dating back to 2003</a>, made by “someone” named saxmatt!</p>\n<p>Let’s dive into one of these commits, as they are called in Git:</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/commit.png?ssl=1"><img /></a></p>\n<p>This is the diff (Git jargon for difference between 2 commits) for the “class-wp-widget-text.php” file. The red line is being replaced with the green line below it. No need to comment it out to save it for eternity, like in that other example. Git will do that for us and we can forever and always refer back to this commit to see what was replaced and with what.</p>\n<p>Of course, the full WordPress code base is a large project with many collaborators. However, no project is too small to benefit from Git. Once you master those 3-4 commands, using Git in your day-to-day developer life becomes second nature, just like hitting Ctrl-s. It might not be obvious right now, but when you pull out an old project months or years later, having version control helps you catch up and gives you the confidence to change things without fearing disaster.</p>\n<p>So I challenge you to learn Git! Not necessarily deeply, just a little bit.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 28 Sep 2017 22:31:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:57:"WPTavern: WordCamp Incubator Program Gears Up for Round 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=75159";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordcamp-incubator-program-gears-up-for-round-2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2791:"<p>Last year the WordPress Community Team launched an experimental <a href="https://wptavern.com/wordpress-to-launch-experimental-wordcamp-incubator-program" rel="noopener" target="_blank">WordCamp Incubator program</a> to bring WordCamps to new cities where meetups had not been very well established. After receiving 182 applications, organizers narrowed the selections to three cities with the most potential to foster an emerging WordPress community. Successful WordCamps were held in Denpasar, Harare, and Medellín. Six additional communities that applied to the program ended up organizing WordCamps as well with the help of community mentors.</p>\n<p>This week Andrea Middleton announced that the Community Team will be pursuing <a href="https://make.wordpress.org/community/2017/09/27/wordcamp-incubator-program-v2-new-role-name/" rel="noopener" target="_blank">round two of the WordCamp Incubator program</a>. Given the rapid growth of the global WordPress community, Middleton said the greatest challenge to getting the program running again is finding people who can oversee the new WordCamps. The full-time sponsored volunteer staff from the previous year is already fully committed for 2018.</p>\n<p>&#8220;This is a time-intensive volunteer role,&#8221; Middleton said. &#8220;We estimate that lead organizers spend about 170 hours on a WordCamp, and I figure that the folks working to support the growth of an Incubator event need to dedicate about 200-250 hours over the planning cycle. The job is that of co-organizer, mentor, and ambassador — since it’s probable that no one you’re working with has ever actually attended a WordCamp.&#8221;</p>\n<p>Experience having organized WordCamps is a prerequisite for taking on the community advisor role. Middleton also emphasized the importance of sensitivity and experience collaborating with people from other cultures. She estimates the volunteer role is likely to require 25 hours per month. As this is almost a part-time job, the Community Team is looking at the possibility of having interested volunteers pitch their companies to sponsor some of their hours to work on the incubator program. They are also considering creating a team of incubator advisors to work together assisting multiple communities.</p>\n<p>The team is aiming to decide on a name for the advisor role and come up with a plan for recruiting volunteers by October 6. This will be followed by a call for communities that would like to be considered for the program and host their first WordCamp in 2018. Anyone interested in volunteering can jump in on the discussion on the <a href="https://make.wordpress.org/community/2017/09/27/wordcamp-incubator-program-v2-new-role-name/" rel="noopener" target="_blank">make.wordpress.org/community</a> blog.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 28 Sep 2017 21:26: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: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:73:"WPTavern: WPWeekly Episode 289 – Where Did WordPress’ Ease of Use Go?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=75134&preview=true&preview_id=75134";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://wptavern.com/wpweekly-episode-289-where-did-wordpress-ease-of-use-go";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3091:"<p>In this episode, <a href="https://jjj.blog/">John James Jacoby</a> and I are joined by <a href="http://scottbolinger.com/">Scott Bolinger</a>. Bolinger recently attended a Content and Commerce Summit where WordPress and WooCommerce were not mentioned. Bolinger <a href="http://scottbolinger.com/perspective-on-wordpress/">shared the perspective</a> he gained from an attending the event and speaking with a friend who uses Shopify.</p>\n<p>We discuss what happened to WordPress&#8217; ease of use, which user segment the project is developed for, and how can it provide an end-to-end user experience that&#8217;s on par with SaaS offerings like SquareSpace or Wix. We also talk about the challenges associated with setting up a WordPress site after the installation process. Last but not least, we discuss why some people are not recommending WordPress to friends or family anymore.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://wptavern.com/donatewc-reaches-fundraising-goal">DonateWC Reaches Fundraising Goal</a><br />\n<a href="https://wptavern.com/wordcamp-for-publishers-videos-now-available-on-youtube">WordCamp for Publishers Videos Now Available on YouTube</a><br />\n<a href="https://wptavern.com/apply-filters-podcast-to-be-retired-after-83-episodes">Apply Filters Podcast to be Retired after 83 Episodes</a><br />\n<a href="https://wptavern.com/facebook-to-re-license-react-after-backlash-from-open-source-community">Facebook to Re-license React after Backlash from Open Source Community</a><br />\n<a href="https://wptavern.com/wordpress-explores-a-javascript-framework-agnostic-approach-to-building-gutenberg-blocks">WordPress Explores a JavaScript Framework-Agnostic Approach to Building Gutenberg Blocks</a><br />\n<a href="https://wptavern.com/si-captcha-anti-spam-plugin-permanently-removed-from-wordpress-og-due-to-spam-code">SI CAPTCHA Anti-Spam Plugin Permanently Removed from WordPress.org Due to Spam Code</a></p>\n<h2>Picks of the Week:</h2>\n<p><a href="https://make.wordpress.org/plugins/2016/02/12/on-the-topic-of-selling-your-plugins/">Otto shares tips and advice on selling plugins</a>.</p>\n<p><a href="https://en.wikipedia.org/wiki/Metroid:_Samus_Returns">Metroid: Samus Returns</a> and Nintendo 3DS.</p>\n<p><a href="http://amyciavolino.com/assets/MindfulCommunicationInCodeReviews.pdf">Mindful Communication in Code Reviews by Amy Ciavolino</a>.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, October 4th 3:00 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href="https://wptavern.com/feed/podcast" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #289:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 27 Sep 2017 22:37:17 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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: WordPress.com Adds Google Photos Integration, Available Now for Jetpack-Enabled Sites";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75084";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:105:"https://wptavern.com/wordpress-com-adds-google-photos-integration-available-now-for-jetpack-enabled-sites";s: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:3566:"<p>WordPress.com now supports <a href="https://en.blog.wordpress.com/2017/09/26/upload-once-blog-anywhere-photos-from-google/" rel="noopener" target="_blank">seamless integration between Google Photos and the WordPress media library</a>. Users can connect their Google accounts to have access to their photos when inserting an image.</p>\n<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-27-at-3.39.22-PM.png?ssl=1"><img /></a></p>\n<p><a href="https://www.google.com/photos/" rel="noopener" target="_blank">Google Photos</a> has gained popularity due to its automatic tagless organization and free, unlimited backup for photos and videos up to 16MP and 1080p HD. In May 2017, the service reported <a href="https://www.blog.google/products/photos/google-photos-500-million-new-sharing/" rel="noopener" target="_blank">500 million monthly users</a> backing up more than 1.2 billion photos and videos per day.</p>\n<p>When inserting pictures on WordPress.com, users can also take advantage of Google&#8217;s smart image searching capabilities. The service is fairly good at recognizing what is in your images and where they were taken, even if you haven&#8217;t specifically categorized them or added descriptions.</p>\n<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-27-at-3.46.51-PM.png?ssl=1"><img /></a></p>\n<p>The new Google Photos integration is also available for Jetpack-enabled sites when posting via the WordPress.com interface. (It is not available in wp-admin of self-hosted sites.) Unfortunately, this experience is still rather buggy. After adding photos, WordPress.com didn&#8217;t seem to be able to save drafts and it was also unable to display the most recent photos from the past week.</p>\n<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-27-at-1.44.52-PM-e1506544898526.png?ssl=1"><img /></a></p>\n<p>Users should also note that when you authenticate with Google Photos, it will open access to the photos from every single site that you have connected to that particular WordPress.com account. This access is, however, is limited to the specific user who connected. Multiple users on a site will each need to authenticate separately and can connect their own Google accounts. The users do not have access to each other&#8217;s photos. It&#8217;s also easy to revoke access at <a href="https://wordpress.com/sharing/" rel="noopener" target="_blank">wordpress.com/sharing</a>.</p>\n<p>The new Google Photos feature has been very well received by WordPress.com users, as it saves them the trouble of downloading images from the service and then uploading to their media libraries. It&#8217;s not quite as convenient for Jetpack-enabled sites, because it adds additional steps to the publishing process.</p>\n<p>&#8220;Excellent feature, but will it be available directly from self-hosted sites without using WordPress.com?&#8221; one user asked. &#8220;This cuts out so many steps in our publishing workflow, but then adds several more if we then need to login to WordPress.com to do this. Our admin setup is complex, so switching to editing here isn’t an option. I have multiple contributors who write directly and this would be a game changer if they could directly upload their images from their account.&#8221;</p>\n<p>A WordPress.com representative confirmed that there are currently no plans to support a standalone version in Jetpack. They are, however, looking at supporting other services, such as Flickr, in the future.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 27 Sep 2017 22:17: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:"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:50:"WPTavern: Camp Press – A Detox from Digital Life";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75139";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:57:"https://wptavern.com/camp-press-a-detox-from-digital-life";s: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:"<p>The following is a guest post by Brad Williams who shares his experience at <a href="https://camp.press/">Camp Press</a> this past weekend. Brad is the Co-Founder and CEO of the website design and development agency <a href="https://webdevstudios.com">WebDevStudios</a>.</p>\n<p>He is also a co-author of the Professional WordPress book series. Brad is a US Marine Corps veteran and has been developing websites for over 20 years, including the last 10 where he has focused on open-source technologies like WordPress.</p>\n<hr />\n<img />Brad Williams at Camp Press\n<p>I’ve been to a number of WordCamps and tech-related events over the years. They all follow a similar pattern of speakers, panels, sponsors, after-parties, etc. We’ve all been to these types of events and generally know what to expect; so when <a href="https://twitter.com/ifyouwillit?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Mendel Kurland</a> pitched the idea of <a href="https://camp.press/">Camp Press</a> to me as &#8216;geeks camping,&#8217; I was intrigued.</p>\n<p>I went to Camp Press with no idea of what to expect. I honestly have never felt less prepared for an event as I did for this one. I like to plan. So, going to an event where I wasn’t 100% sure how it would work had me feeling nervous. What I soon realized is that I liked being pushed out of my &#8216;safety bubble.&#8217;</p>\n<p>The Camp Press location was absolutely amazing and truly helped make the event special. We stayed at a large summer camp style setup, about an hour outside of Oklahoma City called Fry Lake. If you aren’t familiar with Oklahoma, just imagine driving an hour from a large city to the middle of nowhere. Perfect.</p>\n<p>Fry Lake had cabins, shower and bathroom facilities, an amazing swimming lake with diving boards, and a full cafeteria kitchen. We were literally back at the type of summer camp we experienced as kids, and we immediately knew it.</p>\n<img />Camp Press Fire\n<p>As we learned more about each other, we quickly became more comfortable as a group. We shared stories, laughed, cooked, and debated topics from tech to TV shows. We discussed very personal struggles and experiences, some of which I would guess haven’t been shared outside of close family. We sang songs around the campfire, performed late-night improv, made s’mores, and enjoyed each other’s company.</p>\n<p>Even more amazing is that nothing was scripted. There was no agenda, set activities, presentations. It was just natural interaction. Over the course of a few days, we all grew closer to each other. There was an unspoken bond forming between everyone at Camp Press.</p>\n<p>I didn’t know what to expect going to <a href="https://camp.press/">Camp Press</a>. What I promptly learned is that was the entire point of the event—doing the unexpected, pushing yourself outside of your comfort zone, making new friends, having fun and serious conversations, and doing all of this without the normal technology that is always around us.</p>\n<p>When is the last time you had a detox from digital life? My detox was last weekend, and I can’t wait to do it again!</p>\n<img />Camp Press Attendees\n<p>For more insight into Camp Press and to get Mendel&#8217;s perspective, check out the event&#8217;s <a href="https://camp.press/general/inaugural-camp-press-2017-huge-success/">official blog post</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 27 Sep 2017 22:12: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:"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:44:"Dev Blog: Global WordPress Translation Day 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:34:"https://wordpress.org/news/?p=4915";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://wordpress.org/news/2017/09/global-wordpress-translation-day-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:3298:"<p><span>On September 30 2017, the WordPress Polyglots Team &#8211; whose mission is to translate WordPress into as many languages as possible &#8211; will hold its third <a href="https://wptranslationday.org/">Global WordPress Translation Day</a>, a 24-hour, round-the-clock, digital and physical global marathon dedicated to the localisation and internationalisation of the WordPress platform and ecosystem, a structure that powers, today, over 28% of all existing websites.</span></p>\n<p><span>The localisation process allows for WordPress and for all WordPress-related products (themes and plugins) to be available in local languages, so to improve their accessibility and usage and to allow as many people as possible to take advantage of the free platform and services available.</span></p>\n<p><span>In a (not completely) serendipitous coincidence, September 30 has also been declared by the United Nations “International Translation Day”, to pay homage to the great services of translators everywhere, one that allows communication and exchange.</span></p>\n<p><span>The event will feature a series of multi-language live speeches (training sessions, tutorials, case histories, etc.) that will be screen-casted in streaming, starting from Australia and the Far East and ending in the Western parts of the United States.</span></p>\n<p><span>In that same 24-hour time frame, Polyglots worldwide will gather physically in local events, for dedicated training and translations sprints (and for some fun and socializing as well), while those unable to physically join their teams will do so remotely.</span></p>\n<p><span>A big, fun, useful and enlightening party and a lovely mix of growing, giving, learning and teaching, to empower, and cultivate, and shine.</span></p>\n<p><span>Here are some stats about the first two events:</span></p>\n<p><b>Global WordPress Translation Day 1</b></p>\n<ul>\n<li><span>   </span><span>448 translators worldwide</span></li>\n<li><span>   </span><span>50 local events worldwide</span></li>\n<li><span>   </span><span>54 locales involved</span></li>\n<li><span>   </span><span>40350 strings translated, in</span></li>\n<li><span>   </span><span>597 projects</span></li>\n</ul>\n<p><b>Global WordPress Translation Day 2</b></p>\n<ul>\n<li><span>   </span><span>780 translators worldwide</span></li>\n<li><span>   </span><span>67 local events worldwide</span></li>\n<li><span>   </span><span>133 locales involved</span></li>\n<li><span>   </span><span>60426 strings translated, in</span></li>\n<li><span>   </span><span>590 projects</span></li>\n</ul>\n<p><span>We would like your help in spreading this news and in reaching out to all four corners of the world to make the third #WPTranslationDay a truly amazing one and to help celebrate the unique and fundamental role that translators have in the Community but also in all aspects of life.</span></p>\n<p><span>A full press release is available, along with more information and visual assets at </span><a href="https://wptranslationday.org/press/"><span>wptranslationday.org/press</span></a>.</p>\n<p><span>For any additional information please don’t hesitate to contact the event team on </span><a href="mailto:press@wptranslationday.org"><span>press@wptranslationday.org</span></a><span>.</span></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 27 Sep 2017 11:56: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: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: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:36:"HeroPress: Challenge Gladly Accepted";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=2129";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:124:"https://heropress.com/essays/challenge-gladly-accepted/#utm_source=rss&utm_medium=rss&utm_campaign=challenge-gladly-accepted";s: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:8986:"<img width="960" height="480" src="http://20094-presscdn.pagely.netdna-cdn.com/wp-content/uploads/2017/09/092717-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: I could never have imagined that WordPress would become an important part of my life." /><p>I grew up in a suburb to Stockholm, where me and my brothers would wrestle over who was allowed to use our first PC. I think it was a pre-owned old beaten Compaq Deskpro 386. We only stopped arguing once we could sit down together and play Civ; one of us at the controls, the others giving advice on what moves to make.</p>\n<h3>Dipping Into The Web</h3>\n<p>I learnt HTML and built my first pages on Geocities and out of necessity: I needed a place to publish my angsty teenage poetry. But people didn’t come to my website for the bad poetry, instead they filled my guestbook with webdesign and HTML questions.</p>\n<p>I have built websites for myself and others since the mid 90’s and kept a few clients on the side while studying. At this time, there was not a lot of computer or programming classes available for high school students. It had been easy enough to learn HTML online by reading guides, message boards and similar. During one of my final semesters, my school announced a new class called “Computers for girls”. I signed up hoping to learn enough to assemble or upgrade my own PC. The class was a joke. Instead of teaching us about motherboards, memory or networks, our teacher showed us where to put the cords…</p>\n<p>He didn’t realise that most of us already spent every recess in the computer halls, chatting over IRC. In order to learn the basics of actual programming (not just HTML), I had to take adult education evening- and summer classes since my school didn’t offer any.</p>\n<h3>Derailed</h3>\n<p>After high school I did like many others of my generation: I fell in love with someone I had only met online, who lived on the other side of the world. All to the soundtrack of Savage Garden&#8217;s “I Knew I Loved You”.</p>\n<div class="jetpack-video-wrapper"></div>\n<p>It took all my savings and courage to travel back and forward between Sweden and the US, while studying from a distance.</p>\n<blockquote><p>When my boyfriend suddenly passed away in 2001 I had to make drastic changes in my life.</p></blockquote>\n<p>I was in the middle of moving, I couldn’t keep up with deadlines or deal with clients, and I was barely able to finish my project managing and programming classes. I had to forget all our plans, start over, and take a desk job instead.</p>\n<h3>Coming Back To The Web</h3>\n<p>Many years later one of my former clients asked if I had tried WordPress. It took me a few months to decide if I liked it or not, partially because I didn’t know PHP, and because I didn’t have great experiences from trying Joomla and Drupal.</p>\n<p>I did some customization work and eventually I submitted my first theme to WordPress.org. Of course my theme was a mess and did not even work as expected.</p>\n<blockquote><p>But I appreciated that someone took the time to look at my code and explain what I needed to do to fix it and where I could read more. It was very rare to receive such feedback.</p></blockquote>\n<p>I joined the Theme Review Team&#8217;s mailing list, listening in and learning. I started reviewing themes to learn more and to improve my own themes.</p>\n<p>For those who do not know what the Theme Review Team does, we test and review the code (every single file) of themes that are submitted to be included in the WordPress.org theme directory.</p>\n<h3>My Secret Power</h3>\n<p>Because I am on the autism spectrum, the structure and patterns of coding languages suits me well. I need both structure and a creative outlet in my life, and coding is therapy, much like a puzzle or a coloring book. I love my once dreaded desk job, because it gives me the opportunity to help people on a different scale than I ever could as a freelancer. Being a volunteer on WordPress.org lets me combine both worlds.</p>\n<p>I could never have imagined that WordPress would become an important part of my life, that I would spend this much time on it (sometimes up to 20 hours per week), or that I would be asked to be one of the team leads for the Theme Review Team in 2017.</p>\n<p>Today I honestly don’t know what I would do if I could no longer contribute to WordPress the way I know and am familiar with. It is an essential part of my everyday life.</p>\n<p>WordPress is also challenging because you can only do so much without interacting with others… And even though I find that difficult, I have had to learn that it is something I need as well.</p>\n<blockquote><p>I have to remind myself from time to time that here, I am allowed to be myself, with all my flaws, to contribute as much or as little as I choose, at my own pace.</p></blockquote>\n<p>And to be able to contribute and to help others, I also have to remind myself that people are not scary.</p>\n<h3>And Then WordCamp</h3>\n<p>I was a volunteer online for 6 years before I had the courage to go to my first WordCamp, which took place in my own home town. When I was finally there, I only spoke to 3 or 4 people. My second WordCamp went better, but the experience was still overwhelming.</p>\n<p>During my third WordCamp, which was WCEU 2017, I helped lead the Theme Review section of the contributor day, having to speak in front of 500 people.</p>\n<blockquote><p>The thing is, even when it overwhelms you, this community and its energy is addicting.</p></blockquote>\n<p>Everything changes once you go to your first meetup or WordCamp, meeting people who share your interest and passion. The community at large is open and welcoming, passionate, curious and caring. And it is trying to be a safe place for us all.</p>\n<h3>The Theme Review Team</h3>\n<p>There always seem to be a lot of opinions and even controversy surrounding the Theme Review Team. It is not always easy to handle the pressure and the amount of responsibility that is placed on you because so many people have a financial interest in WordPress themes. As a team lead or moderator, you often have to try to find the least bad solution to many different kind of situations.</p>\n<p>By the end of September, it is time for the current team leads to step back and welcome our next leads. I am looking forward to the break, but also to see what new ideas they will bring.<br />\nIt takes time to change a system that has been in place for this many years, and truthfully, sometimes it is painfully slow. It has proven difficult to find a system where themes without errors can be added to the directory quickly, and where reviewers can support authors who need extra help.</p>\n<p>This amazing team of volunteers has managed to reduce the queue time from 7 months down to 8-10 weeks. We still hope to be able to reduce it further, possibly by automating parts of the code review.</p>\n<p>Finally, the Theme Review Team is open to everyone and always looking for new volunteers.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: Challenge Gladly Accepted" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Challenge%20Gladly%20Accepted&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fchallenge-gladly-accepted%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Challenge Gladly Accepted" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fchallenge-gladly-accepted%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fchallenge-gladly-accepted%2F&title=Challenge+Gladly+Accepted" rel="nofollow" target="_blank" title="Share: Challenge Gladly Accepted"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/challenge-gladly-accepted/&media=https://heropress.com/wp-content/uploads/2017/09/092717-150x150.jpg&description=Challenge Gladly Accepted" rel="nofollow" target="_blank" title="Pin: Challenge Gladly Accepted"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/challenge-gladly-accepted/" title="Challenge Gladly Accepted"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/challenge-gladly-accepted/">Challenge Gladly Accepted</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 27 Sep 2017 00:00: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:15:"Carolina Nymark";s: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:122:"WPTavern: WordPress Core JavaScript Framework Selection Discussion Continues with Input from Open Source Community Leaders";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75086";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:133:"https://wptavern.com/wordpress-core-javascript-framework-selection-discussion-continues-with-input-from-open-source-community-leaders";s: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:10632:"<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/javascript.jpg?ssl=1"><img /></a></p>\n<p>WordPress&#8217; #core-js Slack channel hosted a lively and productive meeting this morning led by Andrew Duthie. The discussion focused less on specific framework comparisons and more on the role a framework will play in building JavaScript-powered interfaces for WordPress. Contributors were joined by core developers and leaders from the React and Vue communities, Chrome engineers, and other interested parties from outside the WordPress community.</p>\n<p>&#8220;This chat will focus largely on identifying requirements in building core features, overlap with plugin and theme authors, and patterns to reducing framework lock-in,&#8221; Duthie said. &#8220;Ideally this is higher-level than simply debating the merits of specific frameworks in a vacuum, and should be seen as an opportunity to collaborate between projects to set a path forward for WordPress which will provide flexibility and resiliency to future churn.&#8221;</p>\n<p>Duthie began by asking what role a framework should play in a WordPress developer&#8217;s workflow and also asked framework contributors to offer their perspectives on recommendations for extendable interfaces. This question provided attendees with the opportunity to weigh in on topics such as <a href="https://github.com/WordPress/gutenberg/pull/2791" rel="noopener" target="_blank">support for web components</a>, <a href="https://github.com/WordPress/gutenberg/pull/2463" rel="noopener" target="_blank">framework-agnostic block interoperability</a> for Gutenberg, and how this might affect WordPress&#8217; plugin ecosystem.</p>\n<p>&#8220;I disagree a bit with the idea that whatever core (in this case Gutenberg) uses to power some of the intricacies of building a stateful app is going to be the de facto standard for plugin development,&#8221; Gutenberg engineer Matías Ventura said. &#8220;The actual framework here, in general terms, is going to be what WordPress exposes and the APIs.&#8221;</p>\n<p>With a framework-agnostic approach to building Gutenblocks, the library that core decides to build on doesn&#8217;t have to become the de facto standard for plugin developers but many outside the Gutenberg team believe that it will inevitably end up that way in practice. There are entire teams of engineers waiting on this decision that are committed to adopt whichever framework WordPress bets on.</p>\n<p>&#8220;To provide some perspective on how WP’s decision on a framework impacts developers downstream, I’m a developer at Boston University and our plan is to focus on whichever framework WP decides upon, even if Gutenberg has a completely agnostic API,&#8221; Adam Pieniazek said. &#8220;We’re primarily a WP shop (~ 1,000 site WP install powers most/a lot of our public web presence) and end up creating huge customizations on top of WP that often require diving into core to see what is actually happening in the background. I like Vue more than React personally, but if WP decides upon React, BU will focus on building expertise in React for when we need to peek/debug beyond the API. It doesn’t mean we won’t also use Vue but it won’t be our primary focus.&#8221;</p>\n<p>Pieniazek feedback echoes that of Gravity Forms co-founder Carl Hancock, who said his team is ready to adopt whatever library WordPress selects.</p>\n<p>“People are going to end up adopting whatever core uses for the most part despite the rainbows and butterflies some are claiming as it relates to creating an abstraction layer so plugin/theme developers can use whatever they want,” Hancock said in the #core-js channel earlier this week.</p>\n<p>Many participants from outside the WordPress community seemed to be in agreement with a framework-agnostic approach and none were eager to force a single framework on all developers working with WordPress. The remaining concern is how this works out practically and whether it puts developers in the confusing position of using a framework on top of a framework.</p>\n<p>&#8220;Since Gutenberg itself is going to become a platform to build for, the best level of separation is if the framework is used to build the core, but isn’t exposed as API to block builders,&#8221; AMP engineer Paul Bakaus said. &#8220;This gives one the choice to replace the underlying foundation whenever necessary.&#8221;</p>\n<p>Gutenberg engineer Riad Benguella summarized the approach the team has been discussing:</p>\n<blockquote><p>I think what we try to communicate is something like:</p>\n<p>&#8211; WordPress Core is going to use this X framework internally<br />\n &#8211; If you want to use it, we think it’s good<br />\n &#8211; If you want to use something else, you can just as easily as you’d use the Core’s chosen framework</p></blockquote>\n<p>Benguella also said that one of the goals for Gutenberg is &#8220;to set the basis for how we extend WordPress&#8217; UI in the future.&#8221; Once it ships, the team will likely set its sights on other parts of the wp-admin and build them in the same way.</p>\n<p>&#8220;If all parts of WP’s UI can be extended via a standard interface, whether it be a simple &#8216;data down, events up&#8217; API, or expecting a WC, I think this would cleanly separate the concerns of &#8216;what framework to use for core&#8217; vs. &#8216;what framework to use for extension development,''&#8221; Vue.js creator Evan You said.</p>\n<p>When asked for his thoughts on on React becoming a primary framework for WordPress, React maintainer Dan Abromov was hesitant to advocate for WordPress adopting the library. His response underscored the necessity of having a framework-agnostic approach for extending Gutenberg and future WP interface overhauls.</p>\n<p>&#8220;I don&#8217;t really know WordPress well, so it&#8217;s hard for me to say whether it&#8217;s a great fit for the use case or not,&#8221; Abramov said. &#8220;Generally we use React for highly interactive UIs and find that it scales well with the app size. I&#8217;m also happy to answer technical questions about it. But I think in general people have strong opinions about, for example, templating vs expressiveness, and I don&#8217;t feel like forcing React upon everyone is the best way.&#8221;</p>\n<p>&#8220;I also feel the same way,&#8221; Evan You said. &#8220;Forcing a single framework on everyone, regardless of which one, is IMO not a good idea because it is bound to alienate the group of devs who are not into that framework, and imposes a bigger long term stability risk.&#8221;</p>\n<p>Abramov also said that people are already &#8220;very bitter and divisive&#8221; about the subject of selecting a framework. He also tweeted a similar sentiment prior to the meeting.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">When I read discussion threads (e.g. about WordPress) there’s a sense that people perceive every team as hostile to others. That’s false.</p>\n<p>&mdash; Dan Abramov (@dan_abramov) <a href="https://twitter.com/dan_abramov/status/912645022344007682">September 26, 2017</a></p></blockquote>\n<p></p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Think of it like tending a garden. You’re welcome to hang out at ours. Other gardens are great too <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="🙂" class="wp-smiley" /></p>\n<p>&mdash; Dan Abramov (@dan_abramov) <a href="https://twitter.com/dan_abramov/status/912653828977254401">September 26, 2017</a></p></blockquote>\n<p></p>\n<p>&#8220;I believe it’s important (and technically feasible) to separate &#8216;which framework to use for core&#8217; and &#8216;which framework community devs use for extensions,''&#8221; Evan You said.</p>\n<p>&#8220;Yes, I think there’s a goal here to be unopinionated for what we’re exposing to plugin authors, so long as the APIs/interfaces we do expose are sufficiently flexible (and easy) to build the UIs and interactions they need to implement,&#8221; Andrew Duthie said.</p>\n<p>The topic of <a href="https://github.com/WordPress/gutenberg/pull/2791" rel="noopener" target="_blank">supporting web components interoperability for Gutenblocks</a> was also part of the discussion during the meeting.</p>\n<p>&#8220;While less powerful than most of the actual frameworks at this point, they are likely to become a W3C standard, ensuring that they will stick around and evolve,&#8221; Felix Arntz said. &#8220;Plus once browser support is fully there, there&#8217;s less functionality to implement by an actual framework built on top.&#8221;</p>\n<p>Polymer.js representative Justin Fagnani said he disagreed that they are &#8220;less powerful&#8221; and noted that web components already are a W3C standard.</p>\n<p>&#8220;I think WP is also uniquely positioned to help drive forward support for web components natively everywhere,&#8221; EventEspresso core dev Darren Ethier said. &#8220;Pretty much all the frameworks have the ability to work with the web component spec now. It’s just a matter of proper implementation.&#8221;</p>\n<p>Several participants referenced <a href="https://custom-elements-everywhere.com/" rel="noopener" target="_blank">custom-elements-everywhere.com</a>, a site that displays popular JS frameworks&#8217; progress on communicating Custom Elements in a way that promotes interoperability. Matías Ventura asked React and Vue core devs how web components (and their future) fit into each framework at the moment.</p>\n<p>&#8220;In React, we have some web component support but haven&#8217;t made it a large priority since use cases have seemed slim in the past, especially since adding Web Components hasn&#8217;t made a lot of sense in a first-party application where you control the whole stack – but we do have some support for them nonetheless and I&#8217;m happy to entertain adding more, either now or in the future,&#8221; Sophie Alpert said.</p>\n<p>&#8220;On the high level I think frameworks like React/Vue provide what is not really addressed in web components: efficient and declarative DOM updates reacting to state changes,&#8221; Evan You said. &#8220;This is also why Polymer exists on top of WC. I have always acknowledged the value of WC as an interop interface.&#8221;</p>\n<p>Overall, attendees at the meeting were respectful, collaborative, and eager to contribute their expertise to help WordPress contributors find the best way forward in the framework selection process. The discussion will continue at next week&#8217;s meeting and likely in the comments of a forthcoming Make/Core post summarizing the meeting.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 26 Sep 2017 22:16:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:93:"WPTavern: SI CAPTCHA Anti-Spam Plugin Permanently Removed from WordPress.org Due to Spam Code";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75059";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/si-captcha-anti-spam-plugin-permanently-removed-from-wordpress-og-due-to-spam-code";s: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:4092:"<p>The <a href="https://wordpress.org/plugins/si-captcha-for-wordpress/" rel="noopener" target="_blank">SI CAPTCHA Anti-Spam</a> plugin has been removed from the WordPress Directory due to its author including spam code. The plugin added a CAPTCHA image test to WordPress forms to prevent spam and was compatible with forms generated by bbPress, BuddyPress, Jetpack, and WooCommerce. It had more than 300,000 active installs at the time of removal.</p>\n<p><a href="https://profiles.wordpress.org/mikechallis" rel="noopener" target="_blank">Mike Challis</a>, the original author of the plugin, said that a WordPress.org user named &#8220;<a href="https://profiles.wordpress.org/fastsecure" rel="noopener" target="_blank">fastsecure</a>&#8221; became the new owner of SI CAPTCHA Anti-Spam in June 2017. Challis was not aware of the new owner&#8217;s plans for the plugin but <a href="https://wordpress.org/support/topic/where-did-the-plugin-go-2/" rel="noopener" target="_blank">posted a notice</a> on the WordPress.org support forums to inform users about why it was removed.</p>\n<p>&#8220;The new owner attempted to put code in several of his newly acquired WordPress plugins that would connect to a 3rd party server he also owned and place spam ads for payday loans and such in the WP posts,&#8221; Challis said. He also linked the incident to a ring of WordPress plugins that researchers at Wordfence say were part of a <a href="https://www.wordfence.com/blog/2017/09/coordinated-plugin-spam/" rel="noopener" target="_blank">coordinated spam campaign</a>. Display Widgets, one of the most notable plugins in this group, was recently <a href="https://wptavern.com/display-widgets-plugin-permanently-removed-from-wordpress-org-due-to-malicious-code" rel="noopener" target="_blank">permanently removed from WordPress.org</a> for a series of violations wherein the author had injected malicious code.</p>\n<p>Challis said the new owner failed to display any spam on sites due to how the code was implemented, but the code could have been activated at a later time:</p>\n<blockquote><p>The new owner put spam code in versions 3.0.1 and 3.0.2 but it failed to display any spam because he put the code in the secureimage.php file. The malicious code required WordPress libraries to also be loaded to execute. The reason the spam code did not do anything at all is because the secureimage.php file is not included in the WordPress run time environment. The secureimage.php file is included from another file securimage_show.php that loads the captcha image directly from html img src outside of the WordPress run time. The spam code in this plugin was never activated, it would not have corrupted your posts or changed anything in the WordPress database.</p></blockquote>\n<p>SI CAPTCHA Anti-Spam users who still have the plugin installed may see an update available in the WordPress admin. Plugin team member Samuel (Otto) Wood removed the malicious code and <a href="https://wordpress.org/support/topic/where-did-the-plugin-go-2/" rel="noopener" target="_blank">released 3.0.3</a> as a clean version that is a safe update for users who still rely on the plugin. Wood recommends users find an alternative, because SI CAPTCHA Anti-Spam will not be re-listed in the directory or receive any future updates.</p>\n<p>The incident is another reminder for users to be on alert when WordPress.org plugins change hands, as the buyers do not always disclose their actual intentions for the plugin. Users in search of an alternative to SI CAPTCHA Anti-Spam will find many alternative options on WordPress.org. <a href="https://wordpress.org/plugins/cleantalk-spam-protect/" rel="noopener" target="_blank">AntiSpam by CleanTalk</a>, <a href="https://wordpress.org/plugins/simple-google-recaptcha/" rel="noopener" target="_blank">Simple Google reCAPTCHA</a>, and <a href="https://wordpress.org/plugins/captcha-code-authentication/" rel="noopener" target="_blank">CAPTCHA Code</a> are a few examples that may work as replacements, depending on what other plugins you need the anti-spam capabilities to support.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 25 Sep 2017 21:50:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:14;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:80:"WPTavern: Facebook to Re-license React after Backlash from Open Source Community";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75021";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/facebook-to-re-license-react-after-backlash-from-open-source-community";s: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:4566:"<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2015/12/react.png?ssl=1"><img /></a></p>\n<p>Facebook has <a href="https://code.facebook.com/posts/300798627056246/relicensing-react-jest-flow-and-immutable-js/" rel="noopener" target="_blank">announced</a> its intentions to re-license React, Jest, Flow, and Immutable.js under the MIT license. React community members began rallying around a <a href="https://wptavern.com/react-users-petition-facebook-to-re-license-react-js-after-apache-software-foundation-bans-bsdpatents-license-in-dependencies" rel="noopener" target="_blank">petition to re-license React</a> after the Apache Software Foundation (ASF) added Facebook’s BSD+Patents license to its Category X list of disallowed licenses for Apache PMC members. Facebook’s engineering directors officially denied the request in mid-August, citing the burden of meritless patent litigation as the reason for keeping the patents clause.</p>\n<p>Facebook moved forward on this decision in full recognition that it might lose some React community members as a consequence. Many open source project maintainers began to look for alternatives. In a surprising move, Matt Mullenweg announced that <a href="https://wptavern.com/wordpress-abandons-react-due-to-patents-clause-gutenberg-to-be-rewritten-with-a-different-library" rel="noopener" target="_blank">WordPress would also be parting ways with React</a> and planned to remove it from the upcoming Gutenberg editor.</p>\n<p>Mullenweg&#8217;s decision to drop React from consideration for WordPress was likely an influential factor in Facebook&#8217;s eventual about-face on the topic of re-licensing the project. Facebook&#8217;s announcement on Friday acknowledges that the company failed to convince the open source community of the benefits of its BSD + Patents license:</p>\n<blockquote><p>We&#8217;re relicensing these projects because React is the foundation of a broad ecosystem of open source software for the web, and we don&#8217;t want to hold back forward progress for nontechnical reasons. </p>\n<p>This decision comes after several weeks of disappointment and uncertainty for our community. Although we still believe our BSD + Patents license provides some benefits to users of our projects, we acknowledge that we failed to decisively convince this community.</p></blockquote>\n<p>The React 16 release, slated for this week, will ship with the updated MIT license. Facebook declined to respond to our request for further comment and said their post is the only public statement they will be providing.</p>\n<p>It&#8217;s not yet clear whether WordPress will continue on with React, picking up where the team left off on Gutenberg, or  shift to another library. Core contributors had originally <a href="https://twitter.com/nacin/status/911356481936740352" rel="noopener" target="_blank">decided on React</a> while attending WordPress&#8217; community summit in Paris last June, although this decision had not yet been made public when the greater open source community started petitioning Facebook to re-license React.</p>\n<p>&#8220;I’m just so tired of this drama,&#8221; Gutenberg engineer Riad Benguella said. &#8220;We spent days and days thinking about the best framework for WP, and this change will just add more thinking, complexity, and uncertainty to our decision. I’m just tired of all this&#8230;we all have to rethink everything.&#8221;</p>\n<p>Mullenweg, who had previously penned a several-thousand word unpublished announcement about how WordPress would be adopting React, did not confirm whether WordPress is still examining other libraries.</p>\n<p>&#8220;Our decision to move away from React, based on their previous stance, has sparked a lot of interesting discussions in the WordPress world,&#8221; Mullenweg said in a <a href="https://ma.tt/2017/09/facebook-dropping-patent-clause/" rel="noopener" target="_blank">post</a> published to his blog this weekend. &#8220;Particularly with Gutenberg there may be an approach that allows developers to write Gutenberg blocks (Gutenblocks) in the library of their choice including Preact, Polymer, or Vue, and now React could be an officially-supported option as well.&#8221;</p>\n<p>The regularly scheduled core JavaScript meeting is set for Tuesday, September 26 at 15:00 GMT and contributors plan to discuss the role a JS framework will play in current and future core focuses. The time has been changed to be two hours later than originally planned in an effort to accommodate more contributors across various timezones.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 25 Sep 2017 16:53: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: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:37:"Matt: Facebook Dropping Patent Clause";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=47574";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:54:"https://ma.tt/2017/09/facebook-dropping-patent-clause/";s: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:1326:"<p>I am surprised and excited to see the news that Facebook is going to drop the <a href="https://ma.tt/2017/09/on-react-and-wordpress/">patent clause that I wrote about last week</a>. They’ve announced that with React 16 the license will just be <a href="https://code.facebook.com/posts/300798627056246/relicensing-react-jest-flow-and-immutable-js/">regular MIT with no patent addition</a>. I applaud Facebook for making this move, and I hope that patent clause use is re-examined across all their open source projects.</p>\n<p>Our decision to move away from React, based on their previous stance, has sparked a lot of interesting discussions in the WordPress world. Particularly with <a href="https://github.com/WordPress/gutenberg">Gutenberg</a> there may be an approach that allows developers to write Gutenberg blocks (Gutenblocks) in the library of their choice including Preact, Polymer, or Vue, and now React could be an officially-supported option as well.</p>\n<p>I want to say thank you to everyone who participated in the discussion thus far, I really appreciate it. The vigorous debate and discussion in the comments here and on Hacker News and Reddit was great for the passion people brought and the opportunity to learn about so many different points of view; it was even better that Facebook was listening.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 24 Sep 2017 16:20:20 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:87:"WPTavern: Scott Bolinger Shares Unique Perspective of WordPress From Outside the Bubble";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75015";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:98:"https://wptavern.com/scott-bolinger-shares-unique-perspective-of-wordpress-from-outside-the-bubble";s: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:5058:"<p>Scott Bolinger, a product developer focused on the WordPress space who has created several products, including <a title="Make native iOS and Android Apps with WordPress" href="https://apppresser.com" target="_blank" rel="noopener">AppPresser </a>and <a href="https://hollerwp.com/">Holler Box</a>, recently attended <a href="http://contentandcommercesummit.com/">Content and Commerce Summit 2017</a>.</p>\n<p>This conference focuses on what’s working in eCommerce, digital media, information publishing, and subscription commerce. <a href="http://scottbolinger.com/perspective-on-wordpress/">According to Bolinger</a>, WordPress and WooCommerce were not topics of discussion.</p>\n<p>&#8220;It really opened my eyes going to an event where no one even said the word WordPress once,&#8221; Bolinger said. &#8220;The audience at this conference was non-technical, mostly marketers selling stuff online. I watched a presentation where the presenter had slides with 20+ different recommended tools on them, and not a single mention of WordPress.</p>\n<p>&#8220;This is an eCommerce conference, WooCommerce is 41% of all eCommerce stores, and not a single person said the word WooCommerce. All I heard about was Shopify and Amazon.&#8221;</p>\n<p>According to <a href="https://www.similartech.com/">SimilarTech</a>, WooCommerce is leading in the top 100K sites, top 1M sites, and the entire web while Shopify is leading in the top 10K sites. While Shopify has a lot less market share, it&#8217;s used on substantially higher trafficked sites.</p>\n<p>Bolinger shared the perspective of a friend who uses Shopify to sell clothing and will gross more than $1M in revenue this year. According to his friend, Shopify is easy to use, from setting up a theme, to the plugin/app ecosystem to add functionality.</p>\n<p>&#8220;When my friend said Shopify is easy to use, this is a whole different category of great user experience,&#8221; Bolinger said. &#8220;This is building a site from scratch for a completely non-technical user, and them loving the end result and the experience.&#8221;</p>\n<p>Bolinger raised an interesting point in that, Wix, Shopify, and SquareSpace are closed, SaaS offerings where they can control the user experience from end-to-end. This is impossible to do with WordPress because there are too many moving parts and core can not control how plugins and themes take part in that experience.</p>\n<p>While WordPress core can&#8217;t necessarily solve the problem, it hasn&#8217;t stopped webhosts from trying. <a href="https://wptavern.com/godaddy-launches-new-onboarding-experience-for-wordpress-customers">GoDaddy</a>,  <a href="https://www.bluehost.com/blog/bluehost-news/welcome-to-the-new-bluehost-8973/">Bluehost</a>, and others have created onboarding solutions that try to control the end-to-end user experience.</p>\n<p>Bolinger shared a sentiment that many in the WordPress community have advocated in recent years. &#8220;If we’re honest, the strength of WordPress is not that it’s easy to use for non-technical people. It’s an open-source platform that is easy for developers to extend and customize for clients.&#8221;</p>\n<ul>\n<li><a href="https://mattreport.com/wordpress-is-not-easy/">WordPress is Not Easy</a></li>\n<li><a href="https://mor10.com/wordpress-easy-thats-ok/">WordPress is not easy – and that’s OK</a></li>\n<li><a href="https://neliosoftware.com/blog/is-wordpress-as-easy-as-we-think/">Is WordPress As Easy As We Think?</a></li>\n</ul>\n<p>There was a time, somewhere between WordPress 2.3 and WordPress 3.5, where one of the main reasons people used WordPress was because it was easy. Between then and now, what caused WordPress to lose its ease-of-use factor?</p>\n<p>SquareSpace, Wix, and Shopify didn&#8217;t exist in the early days of WordPress, they were late to market. This gave them the advantage of implementing all the lessons learned through WordPress&#8217; lifespan and since it&#8217;s a closed system, they can iterate rapidly.</p>\n<p>The biggest reality check that Bolinger shares is that there are a lot of people WordPress simply doesn&#8217;t cater too.</p>\n<p>&#8220;There is a large contingent of people who just want to get stuff done, they don’t want to fuss with the tech&#8221;, He said. &#8220;They don’t care about open source or owning their data. They don’t want to install a theme and setup their widgets, or search thousands of results to find the best SEO plugin.</p>\n<p>&#8220;They don’t want to set up &#8216;managed hosting&#8217;, an SSL certificate, or a payment gateway. They just want to sell their products and make money as fast and easily as possible.&#8221;</p>\n<p>I encourage you to <a href="http://scottbolinger.com/perspective-on-wordpress/">read the full post</a> as it provides a perspective of WordPress not often shared within the WordPress bubble. <a href="http://scottbolinger.com/perspective-on-wordpress/"></a>How does WordPress become a platform that delivers the kind of experience from end-to-end that Bolinger&#8217;s friend describes?</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 23 Sep 2017 00:43:40 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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:98:"WPTavern: WordPress Explores a JavaScript Framework-Agnostic Approach to Building Gutenberg 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=74900";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordpress-explores-a-javascript-framework-agnostic-approach-to-building-gutenberg-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:9072:"<a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/blocks.jpg?ssl=1"><img /></a>photo credit: found_drama <a href="http://www.flickr.com/photos/28555778@N00/30725752376">E.&#8217;s pirate town</a> &#8211; <a href="https://creativecommons.org/licenses/by-nc-sa/2.0/">(license)</a>\n<p>The discussion regarding WordPress&#8217; JavaScript framework selection continues in the #core-js Slack channel ahead of next week&#8217;s meeting. One of the more recent topics is the possibility of <a href="https://github.com/WordPress/gutenberg/pull/2463" rel="noopener" target="_blank">framework-agnostic block rendering</a> for Gutenberg, which would allow developers to extend the new editor using any JS library they prefer. This means that Gutenberg blocks, which are colloquially referred to as &#8220;Gutenblocks,&#8221; could be built with Vue, React, Preact, Angular, or whatever the developer feels comfortable using.</p>\n<p>Proponents of this idea contend that pursuing a more flexible approach makes WordPress&#8217; core JS framework decision <a href="https://github.com/WordPress/gutenberg/pull/2463#issuecomment-330637007" rel="noopener" target="_blank">less critical</a>. While answering questions on the #core-js channel, Gary Pendergast explained how Gutenberg could be built to maintain the separation.</p>\n<p>&#8220;I&#8217;m really not joking when I say that this decision doesn&#8217;t matter, even for people contributing to Gutenberg,&#8221; Pendergast said. &#8220;In <a href="https://github.com/WordPress/gutenberg/pull/2463" rel="noopener" target="_blank">#2463</a>, the library is treated entirely as a utility library, much like we use lodash, for example. It performs a handful of tasks, and it can be relatively easily pulled out and replaced with something entirely different, with no disruption to the rest of the codebase. For people contributing to Gutenberg, they&#8217;re contributing in the Gutenberg coding style, not the style of whatever library we happen to import.&#8221;</p>\n<p>When asked about a timeline for when the decision will be made and what factors are being considered, Pendergast replied that there is no timeline and that those interested in participating should blog about their experiences and write examples of things they can build with the JS frameworks they are familiar with.</p>\n<p>&#8220;There is neither roadmap, nor timeline, nor does there need to be,&#8221; Pendergast said. &#8220;As Matt mentioned, it&#8217;s really just a technical decision &#8211; the important decision for the wider community was choosing &#8216;not React.&#8217; Unfortunately, this decision has been blown way out of proportion, and heavily conflated with &#8216;what JS library will I be able to build my plugins with?&#8217; and sometimes &#8216;what JS library&#8217;s practices will Gutenberg blocks resemble?,&#8217; neither of which are related. Tweets and posts that treat it like a horse race are not helpful in this way.&#8221;</p>\n<p>Pendergast said whatever library is selected will &#8220;continue to be wrapped by the WordPress element, the underlying library won&#8217;t be exposed.&#8221; The Gutenberg team is working to remove all library dependencies from its components so that plugin developers can use any library they choose.</p>\n<p>However, other community members are not so eager to relegate the JS library selected for core to a simple technical decision or utility library.</p>\n<p>&#8220;Most developers understand that their plugins are not bound by the framework chosen for core/Gutenberg,&#8221; Kevin Hoffman said. &#8220;But that doesn&#8217;t diminish the significance of the decision. If we want to encourage more contributors, we&#8217;d be well served to choose a framework in which a significant majority feel capable and confident. If this majority is out there developing plugins with one framework and has to learn another in order to contribute to core, then we&#8217;re limiting the number of potential contributors.&#8221;</p>\n<p>Peter Booker contends that no matter how elegant Gutenberg&#8217;s separation is, having a decent understanding of the library chosen for core affects a developers&#8217; ability to deeply troubleshoot certain issues.</p>\n<p>&#8220;I do not think we should be so dismissive of the choice as a minor technical decision,&#8221; Booker said. &#8220;Understanding how PHP, JavaScript, and Backbone (among other things) work is essential to be able to properly debug problems with WordPress. The JS framework chosen for Gutenberg is going to impact a great many people, even if we are not core contributors. It will be essential knowledge to be able to fully troubleshoot issues. This is a decision which will impact far more people than just the Gutenberg team.&#8221;</p>\n<h3>What are the implications of providing a flexible, framework-agnostic approach to building Gutenblocks?</h3>\n<p>Jason Bahl asked if anyone has tried mixing React, Preact, Vue, and Angular in a single app to see if it is &#8220;a recipe for a performance nightmare.&#8221; He posed an example scenario wherein Gravity Forms builds Vue-based Gutenblocks, Yoast has React-based blocks, WooCommerce builds blocks with Preact, and another plugin uses Ember.</p>\n<p>&#8220;It sounds kind of nice to be flexible and allow folks to use whatever but also like it could lead to a lot of division on best practices, and potentially performance issues,&#8221; Bahl said. &#8220;We&#8217;ll see tutorials pop up for how to build Gutenblocks in Vue, React, Preact, Ember, Vanilla JS, etc., which would be cool to see, but also confusing and potentially cause further divide in the community and accepted best practices. Flexibility is nice to a degree, but a strong opinion at some level is also good.&#8221;</p>\n<p>Carl Hancock, co-founder of Gravity Forms, contends that offering a framework-agnostic approach to building Gutenblocks will have little influence on developers who are extending the project. The decision cannot be made less critical by offering more flexibility, because developers will inevitably adopt whatever WordPress core uses.</p>\n<p>&#8220;People are going to end up adopting whatever core uses for the most part despite the rainbows and butterflies some are claiming as it relates to creating an abstraction layer so plugin/theme developers can use whatever they want,&#8221; Hancock said. &#8220;Which means however complex that core framework ends up being will have a direct impact on the barrier to entry for plugin and theme developers. That barrier to entry has been historically low to date and a direct contributor to the growth of WordPress as a self-hosted CMS. Dramatically raising that barrier to entry isn’t necessarily a bad thing. For example, Gravity Forms will use Preact, Vue, whatever, because we have the manpower and skillset to do so when we can finally decide to do so once core makes it’s decision.&#8221;</p>\n<h3>WordPress&#8217; Opportunity to Advance the Web</h3>\n<p>WordPress currently powers 28% of all websites, according to <a href="https://w3techs.com/technologies/details/cm-wordpress/all/all" rel="noopener" target="_blank">W3 Techs</a>, and whatever framework it chooses will make a major impact on which library many developers decide to learn in order to extend the software and advance their careers.</p>\n<p>Matías Ventura, one of the technical leads on the Gutenberg project, encouraged participants in the discussion to look at the bigger picture and embrace the opportunity to work together and collaborate on a solution for WordPress that will advance the web. The team&#8217;s efforts to collaborate with representatives from competing frameworks stands apart in an ecosystem that is generally fragmented and fractious.</p>\n<p>&#8220;I’m excited about the opportunity we have to advance web development in terms of JavaScript UI representation, in a similar way to how WordPress was a driving force for web standards during the past decade,&#8221; Ventura said. &#8220;That’s also where I see us having a responsibility as a project, as people will continue to learn web development through WP. Many people have been introduced to PHP through WordPress, originally just interacting with WP functions and APIs, eventually diving a bit more deeply into the language as needed. I do see our core remaining close to JS the language, as that gives the most meaningful tool to learn, spanning across all frameworks and libraries.&#8221;</p>\n<p>Ventura assured participants in the ongoing discussion that the Gutenberg team is listening and working towards a solution that will push the web forward.</p>\n<p>&#8220;We are absolutely aware that how we build and what we offer through Gutenberg is going to affect the dev community and we are not taking this lightly—quite the opposite,&#8221; Ventura said. &#8220;I’ve been talking with Evan (Vue) and Jason (Preact) because rather than having a &#8216;choose your framework&#8217; contest, this seems an opportunity to collaborate and push the web forwards.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 22 Sep 2017 22:26:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:43:"WPTavern: DonateWC Reaches Fundraising Goal";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=75001";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:54:"https://wptavern.com/donatewc-reaches-fundraising-goal";s: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:1702:"<p><a href="https://donatewc.org/">DonateWC</a>, <a href="https://wptavern.com/donatewc-aims-to-provide-travel-sponsorships-to-attend-large-wordcamps">an initiative</a> focused on providing less fortunate people an opportunity to attend large WordCamps has <a href="https://donatewc.org/news/surprise-our-goal-is-fully-funded/">reached its fundraising goal</a> of 1,000€. Ines van Essen expressed gratitude and appreciation for the donations. &#8220;The responses and feedback that have come in during the past week have been overwhelming,&#8221; She said.</p>\n<p>&#8220;I can’t believe we can already move to legalizing things and actually getting things done. Lesson learned: do not spend two years thinking about something you could maybe do at some point in the future. The time is now, and it’s time to change some lives.&#8221;</p>\n<img />DonateWC Reaches Fundraising Goal\n<p>Essen confirmed that Automattic is not affiliated with the initiative although quite a few of her colleagues are supportive of the idea.  &#8220;Everyone can do something to help another community member,&#8221; She said. &#8220;Whether that&#8217;s buying someone a meal, sharing a ride, or even sharing a room. DonateWC is a big picture thing, but there&#8217;s so many other things you can do to help under privileged groups.&#8221;</p>\n<p>Essen hopes to have the non-profit and other legal aspects of the project taken care of in time to sponsor at least one person to WordCamp US. Part of the funds will be used to pay someone to design a logo and for social media marketing. If you&#8217;re interested in helping out with the project, please <a href="https://donatewc.org/get-in-touch/">get in touch.</a></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 22 Sep 2017 00:13: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: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:65:"WPTavern: WordCamp for Publishers Videos Now Available on YouTube";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=74871";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:76:"https://wptavern.com/wordcamp-for-publishers-videos-now-available-on-youtube";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2772:"<p><a href="https://2017-denver.journalist.wordcamp.org" rel="noopener" target="_blank">WordCamp for Publishers</a>, held last month at The Denver Post building, was the first niche WordCamp to be focused around a specific industry. The event was designed for people who use WordPress to manage publications and also to encourage collaboration among project maintainers who build open source tools for publishers.</p>\n<p>In addition to hands-on technical workshops, the <a href="https://2017-denver.journalist.wordcamp.org/schedule/" rel="noopener" target="_blank">schedule</a> included a variety of publishing-related topics, such as monetization, content distribution, newsletter tools, and print and digital workflows.</p>\n<p>&#8220;The schedule prompted a great deal of learning and discussion that extended well beyond the content typically found at a regional WordCamp,&#8221; attendee Maura Teal <a href="https://mlteal.com/2017/08/wordcamp-publishers-denver/" rel="noopener" target="_blank">said</a>. &#8220;One of the best aspects of this conference was chatting with other developers and leaders involved in media on the web. There were multiple sessions and hallway discussions that brought intriguing solutions to the table. My primary takeaway was that there certainly needs to be more WordCamps of this kind &#8211; that is, focused on a niche but still rooted in community.&#8221;</p>\n<p>The unique format of the event offered more small group opportunities than a traditional WordCamp does for learning, asking questions, and collaborating around tools and strategies that directly relate to publishers.</p>\n<p>&#8220;WordCamp for Publishers was not your average or typical WordCamp,&#8221; attendee Dwayne McDaniel <a href="https://www.mcdwayne.com/2017/08/21/wordcamp-for-publishers/" rel="noopener" target="_blank">said</a>. &#8220;It felt a lot more like WPCampus insofar as the general mood and feeling I got from the participants. Getting to see folks from competing media companies openly discussing how to solve their common challenges, I learned a whole lot and I am grateful to have had the chance to learn about the publishing space.&#8221;</p>\n<p>Videos for all of the sessions held in the auditorium are now available in a <a href="https://www.youtube.com/playlist?list=PLp4P7UHKK-kC1CGF3LDtfPDwtLEzDKiP9" rel="noopener" target="_blank">YouTube playlist</a>. They will also be uploaded to WordPress.tv in the near future. Organizer Steph Yiu said the event was so successful that they are already planning next year&#8217;s conference. Anyone interested in volunteering or donating a venue can <a href="https://vip.wordpress.com/2017/09/01/wordcamp-for-publishers/" rel="noopener" target="_blank">get in touch</a> with the organizing team.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 21 Sep 2017 18:53: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: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:63:"WPTavern: Apply Filters Podcast to be Retired after 83 Episodes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74948";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/apply-filters-podcast-to-be-retired-after-83-episodes";s: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:2025:"<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/apply-filters.png?ssl=1"><img /></a></p>\n<p><a href="http://bradt.ca/" rel="noopener" target="_blank">Brad Touesnard</a> and <a href="http://pippinsplugins.com/" rel="noopener" target="_blank">Pippin Williamson</a> are retiring from podcasting. Their bi-weekly show <a href="http://applyfilters.fm/" rel="noopener" target="_blank">Apply Filters</a>, a favorite podcast among WordPress developers, will go off the air after publishing its 83rd episode. The hosts have not yet revealed why they are retiring but plan to share more details in the final episode.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">We’ll answer that next week during the episode! :)</p>\n<p>&mdash; Apply Filters (@applyfilters) <a href="https://twitter.com/applyfilters/status/910593317179555840">September 20, 2017</a></p></blockquote>\n<p></p>\n<p>Apply Filters focused primarily on development and technical topics but also provided a wealth of information on business models, pricing, and marketing in the WordPress product ecosystem. The first episode aired August 15, 2013, just after the Heartbeat API was introduced in WordPress 3.6.</p>\n<p>The show&#8217;s imminent retirement was announced on Twitter today to the disappointment of its many loyal fans. According to the information available on the sponsors page, each episode was receiving more than 2,000 downloads in the first three months after publishing. Roughly 54% of the audience identified as developers.</p>\n<p>During the past six months, the frequency of the episodes had slowed to once per month. I wouldn&#8217;t be surprised if the hosts became too busy to keep up with the show, as they both lead successful WordPress product businesses. Touesnard and Williamson plan to record one final mailbag episode before retiring the show indefinitely and are inviting listeners to <a href="http://applyfilters.fm/submit-topic-idea/" rel="noopener" target="_blank">send in any last questions</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 21 Sep 2017 03:54: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: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:60:"WPTavern: New Core Gallery Widget Targeted for WordPress 4.9";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=74896";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wptavern.com/new-core-gallery-widget-targeted-for-wordpress-4-9";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3816:"<p>The <a href="https://wordpress.org/plugins/wp-core-media-widgets/" rel="noopener" target="_blank">Core Media Widgets</a> feature plugin introduced a gallery widget in the 0.2.0 release this week. WordPress 4.8 added the new audio, image, and video widgets from this feature plugin. The gallery widget is targeted for merge into the upcoming WordPress 4.9 release.</p>\n<p>In testing the new feature I found it to be a simple, straightforward implementation of a gallery widget that could easily replace many plugins that are currently filling this need for users. The option to edit or replace a gallery is immediately available and users can easily rearrange or randomize the images included.</p>\n<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/core-gallery-widget.png?ssl=1"><img /></a></p>\n<p>On the frontend the gallery displays neatly in a thumbnail grid. I was able to change the number of columns while editing the gallery, but the preview in the admin did not match the the way the gallery looks on the frontend. The number of columns is correct on the frontend but not in the admin preview. This might cause some confusion for users if it isn&#8217;t fixed before landing in core. Contributors to the plugin are looking at this <a href="https://github.com/xwp/wp-core-media-widgets/issues/190#issuecomment-331011895" rel="noopener" target="_blank">issue</a>.</p>\n<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-20-at-3.16.22-PM-e1505938641908.png?ssl=1"><img /></a></p>\n<p>Overall, the implementation is user-friendly and similar to adding galleries in posts and pages. However, the widget could still use some testing, especially with different plugins installed. For example, with Jetpack enabled, users can choose between a thumbnail and a slideshow gallery, but the slideshow option doesn&#8217;t seem to work correctly in the widget. WordPress.org has <a href="https://wordpress.org/plugins/search/gallery+widget/" rel="noopener" target="_blank">several hundred plugins</a> that implement some sort of gallery widget and these plugin authors will want to test the new core widget.</p>\n<p>Theme authors will also need to test how the core gallery widget interacts with their themes. After testing the gallery widget with several popular WordPress.org themes, I found that many display the thumbnails with unsightly outlines and unpredictable spacing between images.</p>\n<p>Weston Ruter, who authored the <a href="https://make.wordpress.org/core/2017/05/26/media-widgets-for-images-video-and-audio/" rel="noopener" target="_blank">dev note post</a> when the previous media widgets were introduced in 4.8, said that the paragraph regarding default theme updates is still applicable:</p>\n<blockquote><p>Themes that add custom styles to the MediaElement.js player (namely Twenty Thirteen and Twenty Fourteen) were updated from just styling it within syndicated content, to also include instances within widgets. Most themes don’t restrict styles for captioned images or media players to just post content, that is, limit CSS selectors to classes output by post_class(). If your theme does, make sure to either remove that constraint or include a .widget selector.</p></blockquote>\n<p>Ruter said another dev note will be coming with common theme changes that are required to add the right styling for galleries. Users and theme/plugin developers can test the gallery widget right now on 4.8.2 or 4.9-alpha using the <a href="https://wordpress.org/plugins/wp-core-media-widgets/" rel="noopener" target="_blank">Core Media Widgets</a> plugin. Once the widget is added to WordPress, it will be deactivated in the feature plugin for future releases. Contributors plan to merge the new widget into core next week, provided testing goes well.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 21 Sep 2017 00:35: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: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:70:"WPTavern: WPWeekly Episode 288 – No React.js Framework for Gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74933&preview=true&preview_id=74933";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"https://wptavern.com/wpweekly-episode-288-no-react-js-framework-for-gutenberg";s: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:3046:"<p>While I was supposed to be on vacation last week, I instead had surgery for a broken ankle. Tune in to hear the hilarious explanation on how I broke it. The lesson I learned is to not chase animals out of the yard.</p>\n<p><a href="https://jjj.blog/">John James Jacoby</a> and I discuss the news of the week, including a major decision where Gutenberg will not be written in React due to a patent clause in its license. Other topics include, blind speaker selection for WordCamp US, <a href="https://jjj.blog/2017/09/turbo-boost-for-bbpress-2-6/">bbPress performance improvements</a>, and our picks of the week.</p>\n<h2>Stories Discussed:</h2>\n<p><a href="https://wptavern.com/equifax-launches-wordpress-powered-site-for-consumers-affected-by-security-breach">Equifax Launches WordPress-Powered Site for Consumers Affected by Security Breach</a><br />\n<a href="https://wptavern.com/swfupload-will-officially-be-removed-from-wordpress">SWFUpload Will Officially Be Removed From WordPress</a><br />\n<a href="https://wptavern.com/wordpress-org-adds-new-support-rep-role-for-plugin-pages">WordPress.org Adds New Support Rep Role for Plugin Pages</a><br />\n<a href="https://wptavern.com/display-widgets-plugin-permanently-removed-from-wordpress-org-due-to-malicious-code">Display Widgets Plugin Permanently Removed from WordPress.org Due to Malicious Code</a><br />\n<a href="https://wptavern.com/wordpress-abandons-react-due-to-patents-clause-gutenberg-to-be-rewritten-with-a-different-library">WordPress Abandons React due to Patents Clause, Gutenberg to be Rewritten with a Different Library</a><br />\n<a href="https://wptavern.com/donatewc-aims-to-provide-travel-sponsorships-to-attend-large-wordcamps">DonateWC Aims to Provide Travel Sponsorships to Attend Large WordCamps</a></p>\n<h2>Picks of the Week:</h2>\n<p><a href="https://wptranslationday.org/">WordPress Global Translation day</a> is next Saturday, September 30th. Twenty-four hours dedicated to translating the WordPress ecosystem through sessions, training marathons, and local events.</p>\n<p><a href="https://local.getflywheel.com">Local by Flywheel</a> is software that easily creates a local environment for WordPress development.</p>\n<p>From the folks behind GiveWP, <a href="https://givewp.com/give-live/">Give Live</a> is a series of webinars for the community.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, September 27th 3:00 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href="https://wptavern.com/feed/podcast" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #288:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Sep 2017 22:13:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:45:"HeroPress: What I Do Does Not Define Who I Am";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=2109";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:142:"https://heropress.com/essays/what-i-do-does-not-define-who-i-am/#utm_source=rss&utm_medium=rss&utm_campaign=what-i-do-does-not-define-who-i-am";s: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:13146:"<img width="960" height="480" src="http://20094-presscdn.pagely.netdna-cdn.com/wp-content/uploads/2018/09/092017-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: I became completely inspired by the mission of WordPress. I had become a part of something bigger than myself." /><p>The first time I ever made a WordPress site, I got 180,000 views in 2 days, 253 comments, and (give or take) 7 death threats.</p>\n<p>It was 2014 and I was working on an MBA at Florida State University during the peak of the Jameis Winston controversy, where a football quarterback was accused of rape and protected from prosecution by the university and local police. I had used WordPress before, but not a lot. But, in true democratizing publishing, giving a voice to the voiceless fashion, when I had something I wanted to say, I knew just the thing to get it out there with minimal know-how: a free, single page WordPress.com site.</p>\n<p>I had just returned to Florida from a summer in New York City. To my amazement, I got the life-changing opportunity, paid for by the university’s College of Social Sciences paid, to go up there for a summer of exploration in the social entrepreneurship and technology circles after pitching Florida State on a concept for financial education.</p>\n<h3>Beginning the Journey</h3>\n<p>I had become interested in financial education around the age of 16, when my family became homeless for a month. My mom hadn’t been able to make the rent, so we got kicked out, and then couldn’t find an apartment easily due to my mom’s lack of credit. Later, I started working at a major commercial bank and met hundreds, if not thousands, of people in similar situations (and saw the ways in which major commercial banks don’t help these people, but that’s a different conversation).</p>\n<p>Imagine having been homeless at 16. Then, 6 years later, you’re attending graduate school, funded by the university, and that same university also paid for you to live in the country’s most expensive place for 3 months so that you could learn about executing your ideas on how to make a positive difference through technology entrepreneurship.</p>\n<p>You would probably be overcome with gratefulness. But you would also likely be extremely protective of the people making such a thing possible.</p>\n<p>Now imagine, that while Florida State University’s programs making such an impact on you, a football player’s actions are driving the narrative of this place you want to be proud of.</p>\n<blockquote><p>Imagine me, telling the story I just told you, and watching people connect the dots between what institution was making all of this possible for me, and what they had heard of it. “Oh, my God, with the quarterback that raped that girl?” they would say.</p></blockquote>\n<p>I would link you to the page I created, but quite honestly, it wasn’t a lot more than a profanity-laden rant (of admittedly epic proportions). But, it got a reaction: she needs to shut the f**k up. She’s completely right. She’s an “attention-seeking whore!”. She’s the story we should be focusing on. She’s just upset her Kickstarter campaign failed.</p>\n<p>There it was: WordPress had amplified my voice, and everyone else’s, too.</p>\n<h3>Finding WordPress Business</h3>\n<p>Today, I’m the lesser-known half of Caldera Labs, makers of Caldera Forms, a top drag-and-drop form building plugin for WordPress. A few weeks ago, we got a one-star review on WordPress.org that called me out by name: “their team is useless, especially Christie Chirinos.” I received caring notes from several seasoned WordPress product developers, reassuring me that these things happen and I ought to not take it personally. “It’s not the first time someone’s been mean to me on the internet, and it probably won’t be the last,” I wrote in a Slack DM to my incredible business partner, the part of Caldera Labs you probably know, Josh Pollock. Josh laughed.</p>\n<p>My road from single-page rants on WordPress.com to WordPress product leadership was actually pretty straightforward, although certainly wrapped in incredible fortune. I kept up that blog for a few months at the request of some of those 253 people (and the dismay of some others). Eventually it was forgotten for my financial education project’s website, which went from Wix to self-hosted WordPress.</p>\n<p>Some months of working on that site made me acutely aware that if I wanted to execute more of my ideas, I should learn more code. I started learning JavaScript and PHP. I met Josh somewhere around that time. He liked my WordPress.com story, and encouraged me to keep learning, while picking my brain on what my almost-finished MBA thought about Caldera Forms.</p>\n<p>A professor asked me if I would work on his academic WordPress website for a fee. I was a broke graduate student, so I said yes. Suddenly I had clients. When I graduated, Josh approached me with a proposal to join him in business. I said yes, but my only condition is that I’m moving back to New York City. Josh said, remote work is the norm.</p>\n<p><img class="aligncenter size-large wp-image-2118" src="http://20094-presscdn.pagely.netdna-cdn.com/wp-content/uploads/2017/09/screen_shot_2017-09-19_at_8.26.20_pm-1024x374.png" alt="Screen shot of Caldera website" width="960" height="351" /></p>\n<p>&nbsp;</p>\n<p>Despite the quote-unquote “formal business education,” I was flabbergasted when the full weight of what a WordPress product business entailed hit me. I didn’t understand the community. I didn’t understand the niche’s culture. Much of what I learned were business norms, were completely non-existent in WordPress. I communicated all of this to Josh.</p>\n<blockquote><p>“I have no idea what I’m doing.”</p>\n<p>“Of course you don’t, you’ve never done this before.”</p>\n<p>He introduced me to the extensive library of talks on WordPress TV on imposter syndrome.</p></blockquote>\n<h3>Diving Into WordCamp</h3>\n<p>For me, it clicked at the inaugural WordCamp US. I showed up to the event looking like a deer caught in the headlights and was welcomed with open arms. I got to put faces to all of the names I had learned in the last half-year, and surprise: they were nice. They were welcoming. They were understanding.</p>\n<p>I scoffed at the idea that I would have anything to contribute on Contributor Day, and then found out that the polyglots team could totally use an immigrant that speaks 4 languages. More importantly, I became completely inspired by the mission of WordPress. I realized that, by total accident (or perhaps completely on purpose), I had become a part of something bigger than myself. I had to stick with it, no matter how hard it was.</p>\n<p>In the year after that, I also began to find a small niche for myself. I became “the girl with the MBA,” smart, young, and clearly lucky. “There’s not a lot of people in the space with your background,” said the host interviewing me on a WordPress podcast. Meanwhile, I’m thinking to myself, “oh my god. I don’t even understand why you invited me. I’m very grateful, but I also really don’t know that much about business. Didn’t you notice? Didn’t anyone tell you?”</p>\n<p>Move forward a year, and results started rolling in. I spoke at 4 WordCamps and many other shows. Josh published his 2016 Year In Review, where he outlined the explosive growth that Caldera Forms experienced at the end of the year and acknowledged the benefit of having partnered with me. He doesn’t know this, but I cried when I read that (now he knows).</p>\n<blockquote><p>It was surreal: the unlikely thing that we set out to do was working.</p></blockquote>\n<p>This year, 2017, has consisted of taking on the next step in that process: teaching myself how to turn all of those thoughts on their heads. I have had to unlearn “why me?” and internalize “why not me?”, and most importantly, practice differentiating the story that I tell myself about myself versus the evidence-based reality.</p>\n<h3>Self Discovery</h3>\n<p>A crucial part of this stage has been learning that what I do does not define who I am. That’s a tired joke where I live. The joke goes that you can go to any bar, and participate in the same script: what’s your name? What do you do? “I’m Christie, and I’m a partner and the business manager at a commercial WordPress plugin shop, Caldera Labs” is a story, and it immediately sparks self-doubt. That isn’t an answer that describes an evidence-based reality, it is an answer that describes a story, and stories by definition require effort to be believed.</p>\n<blockquote><p>Who I am, I am learning, is the collection of my experiences, which then drive my priorities in how I do what I do, which is business.</p></blockquote>\n<p>In that podcast interview, I wasn’t told “there aren’t many business managers in the space.” I was told that there weren’t a lot of people with my background in the space. It’s the collection of my stories &#8211; of immigration, difficult childhoods, arguments in business school classrooms and accidentally viral WordPress websites, that perfectly positioned me to do what I’m doing right now.</p>\n<p>The main reason I wanted to write for HeroPress when Topher offered was to take these thoughts out of my story. The more I grow into this role, the more I’m learning that this is especially common with people like me.</p>\n<p>Research is being conducted more and more every day seeking to discover why we don’t become entrepreneurs who fearlessly pursue happiness and high-risk, high-reward situations (the common trope being that privilege is being told to strive to be anything one wants to be, while others are told to strive for an escape from instability).</p>\n<blockquote><p>Most of it boils down to the idea that many minorities, women, immigrants, people from low-income households &#8211; take your pick &#8211; have convinced themselves of a story that does not, in fact, reflect the reality of their possibilities.</p></blockquote>\n<p>It’s a shame, because there’s almost as much research that demonstrates that businesses with diverse leadership teams outperform homogeneous teams almost every single time.</p>\n<p>Let’s start talking about this, even if this isn’t something that directly relates to you. Because, if that is the case, chances are that this is a topic that relates to someone you know. Diversity of thought is an important part of our WordPress community narrative. If you are not the person who must assess replacing a story with an evidence-based reality, you may be someone who is positioned to engage in powerful actions to promote diversity of thought, like encouraging someone else to challenge the stories they tell themselves and the stories they tell others about themselves. “I’m Christie, and I lead all of the business development and marketing for a commercial WordPress plugin shop, Caldera Labs” sounds a lot better.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: What I Do Does Not Define Who I Am" class="rtsocial-twitter-button" href="https://twitter.com/share?text=What%20I%20Do%20Does%20Not%20Define%20Who%20I%20Am&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fwhat-i-do-does-not-define-who-i-am%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: What I Do Does Not Define Who I Am" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fwhat-i-do-does-not-define-who-i-am%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fwhat-i-do-does-not-define-who-i-am%2F&title=What+I+Do+Does+Not+Define+Who+I+Am" rel="nofollow" target="_blank" title="Share: What I Do Does Not Define Who I Am"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/what-i-do-does-not-define-who-i-am/&media=https://heropress.com/wp-content/uploads/2018/09/092017-150x150.jpg&description=What I Do Does Not Define Who I Am" rel="nofollow" target="_blank" title="Pin: What I Do Does Not Define Who I Am"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/what-i-do-does-not-define-who-i-am/" title="What I Do Does Not Define Who I Am"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/what-i-do-does-not-define-who-i-am/">What I Do Does Not Define Who I Am</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Sep 2017 12:00: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:17:"Christie Chirinos";s: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:64:"WPTavern: WordPress 4.8.2 Patches Eight Security Vulnerabilities";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74914";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordpress-4-8-2-patches-eight-security-vulnerabilities";s: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:840:"<p>WordPress 4.8.2 <a href="https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/">is available for download</a> and users are encouraged to update as soon as possible. This release patches eight security vulnerabilities and has six maintenance related fixes. Hardening was also added to WordPress core to prevent plugins and themes from accidentally causing a vulnerability through <code>$wpdb-&gt;prepare()</code> which can create unexpected and unsafe queries leading to potential SQL injection (SQLi).</p>\n<p>To see a full list of changes, check out the <a href="https://codex.wordpress.org/Version_4.8.2">release notes</a>. Auto updates are rolling out to sites that support them but if you&#8217;d like to update manually, you can browse to Dashboard &#8211; Updates and click the Update Now button.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Sep 2017 01:22: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: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:58:"Dev Blog: WordPress 4.8.2 Security and Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4909";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/09/wordpress-4-8-2-security-and-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2799:"<p>WordPress 4.8.2 is now available. This is a <strong>security release</strong> for all previous versions and we strongly encourage you to update your sites immediately.</p>\n<p>WordPress versions 4.8.1 and earlier are affected by these security issues:</p>\n<ol>\n<li><code>$wpdb-&gt;prepare()</code> can create unexpected and unsafe queries leading to potential SQL injection (SQLi). WordPress core is not directly vulnerable to this issue, but we&#8217;ve added hardening to prevent plugins and themes from accidentally causing a vulnerability. Reported by <a href="https://hackerone.com/slavco">Slavco</a></li>\n<li>A cross-site scripting (XSS) vulnerability was discovered in the oEmbed discovery. Reported by xknown of the WordPress Security Team.</li>\n<li>A cross-site scripting (XSS) vulnerability was discovered in the visual editor. Reported by <a href="https://twitter.com/brutelogic">Rodolfo Assis (@brutelogic)</a> of Sucuri Security.</li>\n<li>A path traversal vulnerability was discovered in the file unzipping code. Reported by <a href="https://hackerone.com/noxrnet">Alex Chapman (noxrnet)</a>.</li>\n<li>A cross-site scripting (XSS) vulnerability was discovered in the plugin editor. Reported by 陈瑞琦 (Chen Ruiqi).</li>\n<li>An open redirect was discovered on the user and term edit screens. Reported by <a href="https://hackerone.com/ysx">Yasin Soliman (ysx)</a>.</li>\n<li>A path traversal vulnerability was discovered in the customizer. Reported by Weston Ruter of the WordPress Security Team.</li>\n<li>A cross-site scripting (XSS) vulnerability was discovered in template names. Reported by <a href="https://hackerone.com/sikic">Luka (sikic)</a>.</li>\n<li>A cross-site scripting (XSS) vulnerability was discovered in the link modal. Reported by <a href="https://hackerone.com/qasuar">Anas Roubi (qasuar)</a>.</li>\n</ol>\n<p>Thank you to the reporters of these issues for practicing <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/">responsible disclosure</a>.</p>\n<p>In addition to the security issues above, WordPress 4.8.2 contains 6 maintenance fixes to the 4.8 release series. For more information, see the <a href="https://codex.wordpress.org/Version_4.8.2">release notes</a> or consult the <a href="https://core.trac.wordpress.org/query?status=closed&milestone=4.8.2&group=component&col=id&col=summary&col=component&col=status&col=owner&col=type&col=priority&col=keywords&order=priority">list of changes</a>.</p>\n<p><a href="https://wordpress.org/download/">Download WordPress 4.8.2</a> or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.8.2.</p>\n<p>Thanks to everyone who contributed to 4.8.2.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Sep 2017 22:17:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:"";}}}}}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:114:"WPTavern: WooCommerce 3.2 to Introduce Pre-Update Extension Version Checks, Release Date Pushed Back to October 11";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74908";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:124:"https://wptavern.com/woocommerce-3-2-to-introduce-pre-update-extension-version-checks-release-date-pushed-back-to-october-11";s: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:4251:"<p>WooCommerce 3.2 RC1 is coming next week ahead of the plugin&#8217;s second major release this year. <a href="https://wptavern.com/woocommerce-3-1-adds-new-csv-product-importerexporter-improves-extension-management" target="_blank">Version 3.1</a> introduced a new built-in product importer/exporter that supports CSV files and brought significant improvements to extension management. Version 3.2 is on track to make the process of updating stores a smoother experience with a long-awaited new feature that displays version compatibility checks to users prior to updating their extensions.</p>\n<p>Many WooCommerce store owners experienced considerable difficulties in updating to version 3.0 due to incompatibilities with extensions that were not fully compatible. The widespread problems with updating caused a direct hit to the plugin&#8217;s reputation, even though the main issue was with third-party extensions not being ready to go for 3.0. WooCommerce 3.2&#8217;s new pre-update extension version checks will help users to be more informed about the status of extension compatibility before updating.</p>\n<p>WooCommerce plugin developers can now add two new headers to their extensions to specify a minimum required version and a &#8220;tested up to&#8221; version.<br />\n<code><br />\n/*<br />\n * Plugin Name: WooCommerce Barter Gateway<br />\n * Plugin URI: https://wordpress.org/plugins/woocommerce-gateway-barter/<br />\n * Description: Take payments by bartering crops and livestock.<br />\n * Author: WooCommerce<br />\n * Author URI: https://woocommerce.com/<br />\n * Version: 3.0.7<br />\n * Text Domain: woocommerce-gateway-barter<br />\n * Domain Path: /languages<br />\n * WC requires at least: 3.0.0<br />\n * WC tested up to: 3.2.0<br />\n */</code></p>\n<p>Plugin authors are recommended to update these headers after each major and minor WooCommerce release. (Patch releases do not require headers to be updated.)</p>\n<p>The core WooCommerce plugin will check through the extension headers and display a warning to users when updates are available, detailing which plugins have or haven&#8217;t been tested with the latest major version.</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/pre-update-extension-version-checks.png?ssl=1"><img /></a></p>\n<p>WooCommerce developer Claudiu Lodromanean cited several important benefits for extension developers in a <a href="https://woocommerce.wordpress.com/2017/08/28/new-version-check-in-woocommerce-3-2/" target="_blank">post</a> announcing the new feature:</p>\n<ul>\n<li>You will have to field fewer complaints from users that the new WooCommerce version broke your plugin. They will have clear warnings about the dangers of upgrading when the plugin is incompatible. This should reduce your support load when new versions of WooCommerce are released.</li>\n<li>You will not have to rush updates to your plugin. If a user upgrades WooCommerce and your plugin breaks you are under a lot of pressure to release an update fast. If the user waits until a compatible version of the plugin is released before updating WooCommerce you do not have this problem.</li>\n<li>Users will trust your plugin more. By adding the header you are letting the user know that the plugin has been tested, works with their version of WooCommerce, and is actively maintained to be compatible with WooCommerce.</li>\n</ul>\n<p>The pre-update version checks for extensions is an exciting improvement for store owners and the greater WooCommerce developer community. Updates will be much easier when users can see at a glance which of their extensions are ready to go. Developers are also <a href="https://woocommerce.wordpress.com/2017/08/28/new-version-check-in-woocommerce-3-2/#comment-3635" target="_blank">interested in seeing this feature applied for themes</a> and the WooCommerce team confirmed they will look into the possibility.</p>\n<p><a href="https://woocommerce.wordpress.com/2017/09/19/important-update-woocommerce-3-2-will-now-be-released-october-11th/" target="_blank">WooCommerce 3.2&#8217;s release date</a> has been pushed back one week to October 11 to give store owners and extension developers enough time to test. The first release candidate is slated for September 27.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Sep 2017 21:06: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: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:80:"WPTavern: DonateWC Aims to Provide Travel Sponsorships to Attend Large WordCamps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74891";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/donatewc-aims-to-provide-travel-sponsorships-to-attend-large-wordcamps";s: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:1919:"<p><a href="https://donatewc.org/">DonateWC</a> is a new initiative by <a href="https://twitter.com/themotherofcode?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Ines van Essen</a>, Happiness Engineer at Automattic, that aims to provide an opportunity for less fortunate people to attend large WordCamps. Essen was inspired to create the non-profit organization after realizing how expensive it was to attend WordCamp US 2015. &#8220;As I did not work for a company that could send me there, I had to pay for travel, accommodation, and food/drinks myself,&#8221; She said. &#8220;All in all, I spent a full month’s worth of income to attend.&#8221;</p>\n<p>While many WordPress focused businesses purchase and give away WordCamp tickets, DonateWC sponsorships include the following:</p>\n<ul>\n<li>A WordCamp ticket</li>\n<li>Door to door transportation</li>\n<li>Accommodation</li>\n<li>Food and drink money</li>\n<li>Internet access</li>\n</ul>\n<p>To be eligible for a sponsorship, you can not work for a company that is involved in WordPress or known to sponsor employees to WordCamps. You must be active in the community and either a speaker or volunteer at the WordCamp you&#8217;re attending.</p>\n<p>Essen has a <a href="https://www.gofundme.com/startup-cost-for-donatewc">crowdfunding campaign</a> through GoFundme and is asking for 1,000€. The initial 1,000€ will be used to design a logo, register the non-profit in the Netherlands, customize the theme for the site, and commercial plugins. However, if you <a href="https://donatewc.org/get-in-touch/">can help out </a>with providing any of the above, the savings will go towards sponsoring more people. Once DonateWC officially becomes a non-profit organization, a call for sponsors will go out.</p>\n<p>If DonateWC is an initiative you believe in, consider <a href="https://www.gofundme.com/startup-cost-for-donatewc">donating to the campaign</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Sep 2017 19:01: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: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:51:"Akismet: Akismet WordPress Plugin 4.0 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=1964";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://blog.akismet.com/2017/09/19/akismet-wordpress-plugin-4-0-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:1574:"<p>Version 4.0 of <a href="http://wordpress.org/plugins/akismet/">the Akismet plugin for WordPress</a> is available.</p>\n<p>This update, a.k.a, &#8220;Akismet for the REST of Us,&#8221; adds endpoints to the WordPress REST API for configuring Akismet and retrieving Akismet stats. Documentation is available <a href="https://blog.akismet.com/akismet-wordpress-plugin-rest-api-endpoints/">here</a>, or you can read the code that adds the endpoints in the <a href="https://plugins.trac.wordpress.org/browser/akismet/trunk/class.akismet-rest-api.php">`class.akismet-rest-api.php` file</a>.</p>\n<p>The progress indicator on the &#8220;Check for Spam&#8221; button has been improved as well and now shows the percentage of comments that have been rechecked rather than just a loading indicator.</p>\n<p>This release also removes support for versions of WordPress before 4.0. If you&#8217;re running anything older than that, you should upgrade.</p>\n<p>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 <a href="http://wordpress.org/plugins/akismet/">the WordPress plugins directory</a>.</p><br />  <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/akismet.wordpress.com/1964/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/akismet.wordpress.com/1964/" /></a> <img alt="" border="0" src="https://pixel.wp.com/b.gif?host=blog.akismet.com&blog=116920&post=1964&subd=akismet&ref=&feed=1" width="1" height="1" />";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Sep 2017 18:12: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: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: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: Why Vue.js Creator Evan You Thinks Vue Could Be a Good Fit for WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=74884";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/why-vue-js-creator-evan-you-thinks-vue-could-be-a-good-fit-for-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6230:"<a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/06/evan-you.png?ssl=1"><img /></a>photo credit: <a href="https://www.youtube.com/watch?v=EiTORdpGqns">JSConf China</a>\n<p>After last week&#8217;s news that <a href="https://wptavern.com/wordpress-abandons-react-due-to-patents-clause-gutenberg-to-be-rewritten-with-a-different-library" target="_blank">WordPress is abandoning React due to its unfavorable patents clause</a>, the discussion regarding the selection of a new framework is heating up again. As Vue is once again among the leading contenders, I reached out to Vue.js creator Evan You to get his perspective on the possibility of WordPress adopting the framework.</p>\n<p>&#8220;Yes, I had a conversation with the WordPress team mostly answering questions they had about Vue,&#8221; You said. &#8220;The discussion happened before Matt&#8217;s announcement of moving away from React. It was mostly intended for filling the team in with the state of Vue and there was no particular conclusion made from it.</p>\n<p>&#8220;To be honest, I got the feeling that the team had already decided to go with React and simply wanted to explore other options before they make the final call. I was a bit surprised by Matt&#8217;s post, but also understand the concerns behind that decision. I think React is a technically sound choice, and the whole patent issue is unfortunate.&#8221;</p>\n<p>Vue is back in the mix alongside Preact.js and other libraries WordPress core contributors are considering adopting. You has been active in the <a href="https://make.wordpress.org/core/2017/05/31/javascript-chat-summary-for-may-30th/#comment-32642" target="_blank">comments</a> on the WordPress core development blog during the previous discussion, as well as more recently in the <a href="https://github.com/WordPress/gutenberg/issues/2733#issuecomment-330124938" target="_blank">discussion</a> in Gutenberg&#8217;s GitHub repo, clarifying misconceptions about the financial stability of the project.</p>\n<p>You has been careful to disclose his bias when participating in conversations about which framework WordPress should adopt. During my interview with him, he offered the community three reasons why he sees Vue as a good fit for the project:</p>\n<p>&#8220;Now that WP has decided to pick a different framework, as the creator of Vue, I surely hope that the WordPress team can adopt Vue,&#8221; You said. &#8220;Below is why I believe Vue would be a good fit for the choice:</p>\n<ul>\n<li>&#8220;As an independent open source project (not born from within a major corporate), Vue provides a good alignment in terms of OSS values with the WordPress project. It&#8217;s fully MIT licensed, and its development is sustained by open financial contribution channels (via Patreon and OpenCollective). This means WordPress can easily ensure Vue&#8217;s sustainability by becoming a major sponsor.</li>\n<li>&#8220;Vue is one of the most approachable frameworks out there, with an established and active community, and ever-growing amount of learning resources. Adopting Vue would provide a low entry barrier and smooth learning curve for devs just getting into WordPress development. This also aligns with what made WordPress successful.</li>\n<li>&#8220;As an incrementally adoptable framework, Vue&#8217;s flexibility means it can be adapted in different use cases ranging from embedded widgets, plugin development to full single-page applications. It can be used without any compilation step in simple use cases, while being mature and powerful enough for more complex use cases such as Calypso and Gutenberg. It offers the complete stack from vdom + ability to use raw render functions, server-side rendering, routing, state management, build tooling, browser devtool extensions, to editor tooling support.&#8221;</li>\n</ul>\n<p>Evan You and six others from the Vue.js core team will be participating in an <a href="https://hashnode.com/ama/with-vuejs-team-cj7itlrki03ae62wuv2r2005s" target="_blank">AMA on Hashnode at 12PM on September 20</a>, inviting general questions about the project, how to use it and contribute, and general programming advice. The questions are already rolling in and their answers should provide more information about the future of Vue and its place in the wider JavaScript ecosystem.</p>\n<p>WP Tavern has also reached out to <a href="https://twitter.com/_developit" target="_blank">Jason Miller</a>, creator of Preact.js to get his perspective on the possibility of WordPress selecting Preact and what it would mean for both projects. The React-alternative is another strong contender among JS libraries WordPress is looking at for use in core.</p>\n<p>The Gutenberg team has been working to ensure that WordPress developers will be able to create &#8220;Gutenblocks&#8221; using any JS library they prefer with different explorations of <a href="https://github.com/WordPress/gutenberg/pull/2463" target="_blank">framework-agnostic block rendering</a>. Ultimately, this would make creating plugins and themes less dependent on the library that is chosen for use in core. Other community members involved in the discussion, however, are keen to emphasize that the framework selected will have an impact on the greater WordPress product ecosystem, far beyond its use in Gutenberg, and are not eager to down play it as a simple technical decision. We&#8217;ll have a more detailed look on that in a separate post.</p>\n<p>In addition to the discussions on independent blogs, the Gutenberg GitHub issues queue and the #core-js channel on WordPress Slack are both hosting active conversations on the upcoming decision. This week&#8217;s core JavaScript chat has been <a href="https://make.wordpress.org/core/2017/09/18/javascript-chat-canceled-for-september-19/" target="_blank">cancelled</a> due to many of those involved traveling or unable to attend. The agenda for the next meeting is to discuss the role a JavaScript framework will play in current and future core focuses (including but not limited to the Gutenberg editor). This meeting is scheduled for <a href="http://www.timeanddate.com/worldclock/fixedtime.html?iso=20170926T1300" target="_blank">Tuesday, September 26, 2017, 8:00 AM CDT</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Sep 2017 17:42:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:30;a:6:{s:4:"data";s:11:"\n	\n	\n	\n	\n	\n";s:7:"attribs";a: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:47:"HeroPress: DonateWC: Getting People to WordCamp";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://heropress.com/?p=2113";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:131:"https://heropress.com/donatewc-getting-people-wordcamp/#utm_source=rss&utm_medium=rss&utm_campaign=donatewc-getting-people-wordcamp";s: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:4050:"<img width="800" height="533" src="http://20094-presscdn.pagely.netdna-cdn.com/wp-content/uploads/2017/09/23950564_1505660479.8301.png" class="attachment-large size-large wp-post-image" alt="Image of a plane wing with the sunset on the horizon" /><p>One of the first addons for HeroPress I ever thought of was sending people to WordCamp who might have a hard time getting there. HeroPress started out to be a voice for people on the fringe of WordPress, and being outside the ability to go to WordCamp practically defines the fringe.</p>\n<p>I never could figure out the logistics of how to make it work. How is money handled? International law? So the idea languished.</p>\n<p>On the other side of the world, <a href="https://heropress.com/essays/getting-a-life/">Ines van Essen</a> had the same idea. She&#8217;s far more clever than I though, and she&#8217;s making it happen. She&#8217;s starting a new organization called DonateWC, specifically to help people get to WordCamp.  Not just local WordCamps, but the large ones like WordCamp Europe and WordCamp US. Trips that can cost multiple months, or even a years salary.</p>\n<p>I am so so so excited that this is happening, Ines is my hero.</p>\n<h2>How You Can Help</h2>\n<p>To get things really rolling Ines needs some funds.  I mentioned logistics earlier; if this isn&#8217;t handled properly a tax agent somewhere is going to come investigating. A non-profit org needs to be created, a logo needs to be created, a site needs to be built, a board needs to be formed, etc. Getting started costs money.</p>\n<p>So <a href="https://www.gofundme.com/startup-cost-for-donatewc">there&#8217;s a GoFundMe page for DonateWC</a>. All things considered she&#8217;s not looking for very much money right now, we can DO THIS.</p>\n<p>If we can make this thing work it&#8217;s going to really change lives. Please help out if you can, and keep an eye on the project. The first person to get sent to WordCamp is going to make history.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: DonateWC: Getting People to WordCamp" class="rtsocial-twitter-button" href="https://twitter.com/share?text=DonateWC%3A%20Getting%20People%20to%20WordCamp&via=heropress&url=https%3A%2F%2Fheropress.com%2Fdonatewc-getting-people-wordcamp%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: DonateWC: Getting People to WordCamp" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fdonatewc-getting-people-wordcamp%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fdonatewc-getting-people-wordcamp%2F&title=DonateWC%3A+Getting+People+to+WordCamp" rel="nofollow" target="_blank" title="Share: DonateWC: Getting People to WordCamp"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/donatewc-getting-people-wordcamp/&media=https://heropress.com/wp-content/uploads/2017/09/23950564_1505660479.8301-150x150.png&description=DonateWC: Getting People to WordCamp" rel="nofollow" target="_blank" title="Pin: DonateWC: Getting People to WordCamp"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/donatewc-getting-people-wordcamp/" title="DonateWC: Getting People to WordCamp"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/donatewc-getting-people-wordcamp/">DonateWC: Getting People to WordCamp</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 17 Sep 2017 20:42: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:"";}}}}}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:67:"WPTavern: Vue Project Launches Community Campaign on OpenCollective";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74756";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/vue-project-launches-community-campaign-on-opencollective";s: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:4392:"<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/Screen-Shot-2017-09-15-at-2.13.34-PM-e1505502876371.png?ssl=1"><img /></a></p>\n<p>With the recent news that <a href="https://wptavern.com/wordpress-abandons-react-due-to-patents-clause-gutenberg-to-be-rewritten-with-a-different-library" target="_blank">WordPress is abandoning React</a> due to its BSD + Patents license, core contributors are now revisiting the discussion of the merits of other frameworks. Gutenberg development is currently on hold until a new library is chosen to replace React, and selection is likely to be imminent to prevent further delay.</p>\n<p><a href="https://vuejs.org/" target="_blank">Vue</a> is once again a strong contender with a recent surge in enthusiastic support in <a href="https://github.com/WordPress/gutenberg/issues/2733" target="_blank">discussions on GitHub</a>, Mullenweg&#8217;s <a href="https://ma.tt/2017/09/on-react-and-wordpress/" target="_blank">announcement</a>, and <a href="https://www.facebook.com/groups/advancedwp/permalink/1624213760974165/" target="_blank">social</a> <a href="https://www.facebook.com/groups/advancedwp/permalink/1624383604290514/" target="_blank">media</a> posts. One of the chief concerns WordPress core contributors had regarding Vue in previous discussions was the longevity of the project and its dependence on creator <a href="https://wptavern.com/vue-js-creator-evan-you-weighs-in-on-wordpress-javascript-framework-discussion" target="_blank">Evan You</a>, who has historically done most of the development.</p>\n<p>The Vue project has recently been taking steps to mitigate this drawback. Earlier this week You announced that <a href="https://medium.com/the-vue-point/vue-is-now-on-opencollective-1ef89ca1334b" target="_blank">Vue is now accepting financial support on OpenCollective</a>, a platform for funding open source projects in a transparent way. You already has a successful <a href="https://www.patreon.com/evanyou" target="_blank">Patreon campaign</a> where contributors are paying $8,815 per month to support his work on Vue, but the new <a href="https://opencollective.com/vuejs" target="_blank">OpenCollective account</a> will support the work of core contributors and community events.</p>\n<p>&#8220;When I started the Patreon campaign, the primary goal was providing myself with enough income so that I can work on Vue full-time,&#8221; You said. &#8220;Today, as the Vue community grows, there are more and more contributions from the community, and OpenCollective’s transparent expense model could help us scale the financial contributions beyond a single developer.&#8221;</p>\n<p>Just four days after launching, Vue already has an estimated annual budget of $9,895 on its OpenCollective account. You is still independently accepting contributions on Patreon to fund his full-time work on the project.</p>\n<p><a href="https://preactjs.com/" target="_blank">Preact</a>, the other leading contender WordPress core contributors are considering, has had an <a href="https://opencollective.com/preact" target="_blank">account on OpenCollective</a> since late 2016. Backers and sponsors have contributed to a $16,091 estimated annual budget for the project.</p>\n<p>Both Vue and Preact have growing networks of financial supporters and are not heavily influenced by a single corporation&#8217;s interests. WordPress core contributors continue to discuss the merits and drawbacks of the two frameworks on various places around the web, but the discussion is somewhat scattered and it&#8217;s difficult for participants to know where their feedback will receive consideration.</p>\n<p>&#8220;The main options are actually all pretty good, and we&#8217;d probably be fine going with any of them, which is makes it a tough decision — objectively and technically there isn&#8217;t one clear without-a-doubt winner,&#8221; Matt Mullenweg said today in WordPress&#8217; #core-js Slack channel.</p>\n<p>An updated post detailing the frameworks and technical considerations that contributors are now examining has yet to be published to the make/wordpress.org development blog. Having communication throughout the process of selecting the framework, instead of announcing it after the decision, would go a long way towards keeping the community informed and involved. We&#8217;ll be following the public discussion as it develops.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Sep 2017 19:54:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:108:"WPTavern: WordPress Abandons React due to Patents Clause, Gutenberg to be Rewritten with a Different Library";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74834";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:118:"https://wptavern.com/wordpress-abandons-react-due-to-patents-clause-gutenberg-to-be-rewritten-with-a-different-library";s: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:7411:"<a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/wrinkled-paper.jpg?ssl=1"><img /></a>photo credit: <a href="https://stocksnap.io/photo/6XVYR9HYNT">	Lalesh Aldarwish</a>\n<p>This evening Matt Mullenweg <a href="https://ma.tt/2017/09/on-react-and-wordpress/" target="_blank">announced</a> on his blog that WordPress has decided to move away from React due to its BSD + Patents clause licensing. Gutenberg engineers will be rewriting the new editor to use another JavaScript framework and Automattic plans to rewrite Calypso as well:</p>\n<blockquote><p>We had a many-thousand word announcement talking about how great React is and how we&#8217;re officially adopting it for WordPress, and encouraging plugins to do the same. I’ve been sitting on that post, hoping that the patent issue would be resolved in a way we were comfortable passing down to our users.</p>\n<p>That post won&#8217;t be published, and instead I&#8217;m here to say that the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library. It will likely delay Gutenberg at least a few weeks, and may push the release into next year.</p></blockquote>\n<p>Mullenweg clarified that Automattic has been happy with React and that the company&#8217;s general counsel <a href="https://github.com/Automattic/wp-calypso/issues/650#issuecomment-235086367" target="_blank">didn&#8217;t think they would ever run into the patent issue</a>. He also commended Facebook on being &#8220;one of the better open source contributors out there&#8221; and for making their intentions clear. Ultimately, Mullenweg decided that he wasn&#8217;t comfortable with the larger WordPress community inheriting the patents clause:</p>\n<blockquote><p>Automattic will also use whatever we choose for Gutenberg to rewrite Calypso — that will take a lot longer, and Automattic still has no issue with the patents clause, but the long-term consistency with core is worth more than a short-term hit to Automattic’s business from a rewrite. Core WordPress updates go out to over a quarter of all websites, having them all inherit the patents clause isn’t something I’m comfortable with.</p></blockquote>\n<p>After the Apache Software Foundation added Facebook&#8217;s BSD+Patents license to its Category X list of disallowed licenses, many open source project leaders and developers <a href="https://wptavern.com/react-users-petition-facebook-to-re-license-react-js-after-apache-software-foundation-bans-bsdpatents-license-in-dependencies" target="_blank">petitioned Facebook to consider re-licensing React</a>, as many React-based projects are now having to be rewritten. <a href="https://wptavern.com/facebook-isnt-budging-on-reacts-bsd-patents-license" target="_blank">Facebook decided it wasn&#8217;t budging on the patents clause</a> and opted to continue protecting its own interests, fully recognizing that it may lose some React community members.</p>\n<p>In the past Mullenweg has been outspoken about how Automattic was betting on React. Many in the community considered WordPress adopting React to be a foregone conclusion, given that both Calypso and Jetpack&#8217;s new admin interface were built on it, as well as WordPress&#8217; new Gutenberg editor. In making the costly decision to rewrite Gutenberg and Automattic&#8217;s products in another library, Mullenweg has demonstrated he is willing to lead the WordPress project in a direction where the community can feel confident about continuing to use and extend the software.</p>\n<p>&#8220;The decision on which library to use going forward will be another post; it’ll be primarily a technical decision,&#8221; Mullenweg said. &#8220;We’ll look for something with most of the benefits of React, but without the baggage of a patents clause that’s confusing and threatening to many people. Thank you to everyone who took time to share their thoughts and give feedback on these issues thus far — we&#8217;re always listening.&#8221;</p>\n<p>Gutenberg could certainly use the extra time and may gain a new crop of contributors, given that the learning curve for the new library isn&#8217;t likely to be as steep as learning React.</p>\n<p>At the end of May, WordPress core contributors had <a href="https://wptavern.com/wordpress-core-javascript-framework-debate-heats-up-contributors-narrow-discussion-to-react-vs-vue" target="_blank">narrowed their considerations for a new JavaScript framework to React and Vue</a>. It appears that <a href="https://vuejs.org/" target="_blank">Vue</a> is still a strong contender. After a commenter on Mullenweg&#8217;s post suggested switching to Vue, he replied that it has been frequently suggested and that the team has met with Evan You, Vue&#8217;s lead developer.</p>\n<p>When I <a href="https://wptavern.com/vue-js-creator-evan-you-weighs-in-on-wordpress-javascript-framework-discussion" target="_blank">interviewed Evan You in June</a>, he said he didn&#8217;t have enough perspective on WordPress core to make an unbiased recommendation but offered feedback on some technical issues being discussed at the time. He also clarified some common misconceptions about Vue, which WordPress&#8217; React proponents had been using as leverage in their arguments against adopting it.</p>\n<p>Mullenweg also confirmed in the comments of his post that <a href="https://preactjs.com/" target="_blank">Preact</a> is another library under consideration. Preact.js is a lightweight 3kB alternative to React that uses the same API but is MIT-licensed. Some are already speculating about Preact being the front-runner for the replacement, as Gutenberg already has a branch devoted to trying it.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">There is a Preact “try” Gutenberg branch. But there is no Vue.js “try” Gutenberg branch. <a href="https://t.co/mFRYTLIV3b">https://t.co/mFRYTLIV3b</a></p>\n<p>&mdash; Carl Hancock <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f680.png" alt="🚀" class="wp-smiley" /> (@carlhancock) <a href="https://twitter.com/carlhancock/status/908510738066657281">September 15, 2017</a></p></blockquote>\n<p></p>\n<p>Also, Mullenweg&#8217;s comment that the decision &#8220;will likely delay Gutenberg at least a few weeks, and may push the release into next year,&#8221; seems to only be feasible if the team rewrites the project using Preact.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">For Gutenberg, not Calypso. I’d take a friendly bet like some booze. <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f600.png" alt="😀" class="wp-smiley" /></p>\n<p>&mdash; Matt Mullenweg (@photomatt) <a href="https://twitter.com/photomatt/status/908539602645827584">September 15, 2017</a></p></blockquote>\n<p></p>\n<p>Public reactions to the news that WordPress is shifting away from React have so far been overwhelmingly positive. Many are thankful and relieved that Mullenweg made the tough decision to change course and select another library after investing so heavily in React.</p>\n<p>The discussion regarding the new framework continues behind closed doors and is not open to the public, although a <a href="https://github.com/WordPress/gutenberg/pull/2732" target="_blank">pull request for using Preact in Gutenberg</a> is open on the project&#8217;s GitHub repo and some community discussion regarding the library selection is happening there.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Sep 2017 05:39: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:28:"Matt: On React and 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:22:"https://ma.tt/?p=47558";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"https://ma.tt/2017/09/on-react-and-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:3758:"<p>Big companies like to bury unpleasant news on Fridays: A few weeks ago, <a href="https://code.facebook.com/posts/112130496157735/explaining-react-s-license/">Facebook announced</a> they have decided to dig in on their patent clause addition to the React license, even after Apache had said <a href="https://issues.apache.org/jira/browse/LEGAL-303">it’s no longer allowed for Apache.org projects</a>. In their words, removing the patent clause would "increase the amount of time and money we have to spend fighting meritless lawsuits."</p>\n<p>I&#x27;m not judging Facebook or saying they&#x27;re wrong, it&#x27;s not my place. They have decided it&#x27;s right for them — it&#x27;s their work and they can decide to license it however they wish. I appreciate that they&#x27;ve made their intentions going forward clear.</p>\n<p>A few years ago, Automattic used React as the basis for the <a href="https://developer.wordpress.com/calypso/">ground-up rewrite of WordPress.com we called Calypso</a>, I believe it&#x27;s one of the larger React-based open source projects. As our general counsel wrote, <a href="https://github.com/Automattic/wp-calypso/issues/650#issuecomment-235086367">we made the decision that we&#x27;d never run into the patent issue</a>. That is still true today as it was then, and overall, we’ve been really happy with React. More recently, the WordPress community started to use React for <a href="https://make.wordpress.org/core/2017/02/17/dev-chat-summary-february-15th-4-7-3-week-3/">Gutenberg</a>, <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/">the largest core project we&#x27;ve taken on in many years</a>. People&#x27;s experience with React and the size of the React community &#8212;  including Calypso &#8212; was a factor in trying out React for Gutenberg, and that made React the new de facto standard for WordPress and the tens of thousands of plugins written for WordPress.</p>\n<p>We had a many-thousand word announcement talking about how great React is and how we&#x27;re officially adopting it for WordPress, and encouraging plugins to do the same. I’ve been sitting on that post, hoping that the patent issue would be resolved in a way we were comfortable passing down to our users.</p>\n<p>That post won&#x27;t be published, and instead I&#x27;m here to say that <strong>the Gutenberg team is going to take a step back and rewrite Gutenberg using a different library</strong>. It will likely delay Gutenberg at least a few weeks, and may push the release into next year.</p>\n<p>Automattic will also use whatever we choose for Gutenberg to rewrite Calypso — that will take a lot longer, and Automattic still has no issue with the patents clause, but the <em>long-term consistency</em> with core is worth more than a <em>short-term hit</em> to Automattic’s business from a rewrite. Core WordPress updates go out to over a quarter of all websites, having them all inherit the patents clause isn’t something I’m comfortable with.</p>\n<p>I think Facebook’s clause is actually clearer than many other approaches companies could take, and Facebook has been one of the better open source contributors out there. But we have a lot of problems to tackle, and convincing the world that Facebook’s patent clause is fine isn’t ours to take on. It’s their fight. </p>\n<p>The decision on which library to use going forward will be another post; it’ll be primarily a technical decision. We’ll look for something with most of the benefits of React, but without the baggage of a patents clause that’s confusing and threatening to many people. Thank you to everyone who took time to share their thoughts and give feedback on these issues thus far — we&#x27;re always listening.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Sep 2017 00:59:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:53:"WPTavern: First WordCamp Dublin Set for October 14-15";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=74595";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:64:"https://wptavern.com/first-wordcamp-dublin-set-for-october-14-15";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4577:"<a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/dublin.jpg?ssl=1"><img /></a>photo credit: <a href="http://www.ireland.com/en-us/what-is-available/sightseeing/destinations/republic-of-ireland/dublin/dublin-city/">Ireland.com</a>\n<p>Following up on the success of WordCamp Belfast last October, the WordPress community in <a href="https://2017.dublin.wordcamp.org/" target="_blank">Dublin will be hosting its first WordCamp October 14-15</a>. Both camps <a href="https://wptavern.com/wordpress-meetup-groups-in-belfast-and-dublin-are-planning-wordcamps-for-2016-and-2017" target="_blank">began the early stages of planning last year</a> and the two communities have shared some of the same organizers across their teams to help get these new camps off the ground in Ireland.</p>\n<p>WordCamp Dublin will be held at <a href="http://business.dcu.ie/" target="_blank">DCU Business School</a> and ticket sales will be capped at 250. In truly affordable WordCamp tradition, tickets are only €35 and include access to two tracks of speakers on both camp days, catered lunch, and an after party on Saturday night in Dublin City Centre.</p>\n<p>&#8220;Given it’s our first WordCamp Dublin it’s difficult to select a venue when we’ve no idea about how many people would like to attend,&#8221; co-organizer Colm Troy said. &#8220;But demand so far has been great so if you want a ticket I’d recommend getting one sooner rather than later.&#8221;</p>\n<p>Most of the camp&#8217;s five organizers are also part of the Dublin WordPress meetup, which is fairly active with 25-30 people attending regularly. They meet the first Thursday of every month and host a local speaker to teach attendees something new. WordPress developers generally gravitate towards the more technical talks, while WordPress users are more interested in talks about improving and promoting their websites.</p>\n<p>WordCamp Dublin will feature one track with advanced WordPress, coding, and development topics and a second track that covers aspects of running a business, growing website traffic, podcasting, and other related topics.</p>\n<p>&#8220;​The Dublin WordPress community, based on what I’ve seen and experienced elsewhere (Buenos Aires, Paris, Vienna, UK, Italy), is pretty unusual,&#8221; co-organizer Rodolfo Melogli said. In addition to co-organizing the local WordPress meetup, Melogli also organizes the Dublin E-commerce and WooCommerce Meetups.</p>\n<p>&#8220;We have complete beginners, who after years of using other CMSs have finally decided to start using WordPress,&#8221; Melogli said. &#8220;We have passionate bloggers, who have been exploiting the SEO and content management features of WordPress since the very beginning. Then, we&#8217;ve got successful themers, popular plugin developers and experienced WordPress freelancers. Making sure everyone is catered for at each WordPress meetup and at the upcoming WordCamp is our biggest challenge and main priority.</p>\n<p>&#8220;The beautiful thing about the WordPress community, and especially in Dublin, is that you can have a successful theme seller sitting beside a complete beginner. And they both have things to share.&#8221;</p>\n<p>Organizers have just announced the <a href="https://2017.dublin.wordcamp.org/speakers-2017/" target="_blank">full lineup of speakers</a> for the WordCamp and co-organizer Colm Troy said the team was &#8220;blown away by the quality and quantity of excellent speaking applications&#8221; they received.</p>\n<p>The camp&#8217;s designers have created a new &#8220;blocky&#8221; style wapuu for the occasion to accompany the event&#8217;s modular design theme. They were aiming for a Lego-like wapuu while incorporating the cosmopolitan landmark &#8220;<a href="https://en.wikipedia.org/wiki/Spire_of_Dublin" target="_blank">Spire of Dublin</a>.&#8221;</p>\n<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/wordcamp-dublin-2017.png?ssl=1"><img /></a></p>\n<p>&#8220;​We have a couple of ideas floating around that will definitely add a unique Irish aspect to WordCamp Dublin but it’s too early to let the cat out of the bag on those yet,&#8221; Troy said. &#8220;In terms of what people can expect, Dublin and Ireland in general has a well earned reputation as one of the most welcoming places in the world. In many ways, our welcoming spirit is closely aligned with the ethos of the WordPress community and I think it’s going to be a really special weekend for attendees regardless of whether they’re new to WordPress or WordCamp veterans.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 14 Sep 2017 21:15: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: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:59:"WPTavern: GitHub Partners with Facebook to Release Atom-IDE";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74752";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://wptavern.com/github-partners-with-facebook-to-release-atom-ide";s: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:3269:"<p>GitHub <a href="http://blog.atom.io/2017/09/12/announcing-atom-ide.html" target="_blank">announced</a> the launch of Atom-IDE this week, a new set of packages that extend its open source JavaScript-powered code editor to include IDE-like functionality. This first release includes packages that support TypeScript, Flow, JavaScript, Java, C#, and PHP.</p>\n<p>&#8220;The start of this journey includes smarter context-aware auto-completion as well as a host of code navigation features such as an outline view, go to definition, find all references as well as other useful functions such as hover-to-reveal information, errors and warnings (diagnostics) and document formatting,&#8221; Atom engineer Damien Guard said.</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/atom-ide.png?ssl=1"><img /></a></p>\n<p>Atom, which was open sourced in 2014, is relatively new to the world of text editors, but its directory lists more than 6,700 packages to extend its functionality. WordPress developers have created <a href="https://atom.io/packages/search?q=WordPress" target="_blank">more than a dozen packages</a> that support actions and filters, WP-CLI commands, documentation, and snippets for third-party plugins.</p>\n<p>Those who have adopted Atom appreciate its extendability, but the most common complaint from the Atom community is that the code editor is noticeably <a href="https://discuss.atom.io/t/why-is-atom-so-slow/11376/193" target="_blank">slower than many others</a>. This has been a frequent <a href="https://discuss.atom.io/t/atom-is-painfully-slow/36298" target="_blank">topic</a> of <a href="https://news.ycombinator.com/item?id=8989606" target="_blank">discussion</a> for several years and its creators admit that <a href="https://discuss.atom.io/t/atom-feels-slow-or-is-consuming-too-much-cpu-or-memory/32662?source_topic_id=36298" target="_blank">performance isn&#8217;t one of its strongest features</a>. However, sometimes extreme performance issues can be caused by a package that a user has installed.</p>\n<p>Atom partnered with Facebook&#8217;s <a href="https://nuclide.io/" target="_blank">Nuclide</a> project developers to develop the new <a href="https://atom.io/packages/atom-ide-ui" target="_blank">Atom IDE UI</a> package that uses Atom’s <a href="https://github.com/atom/atom-languageclient" target="_blank">atom-languageclient</a> library in displaying features supported by the <a href="http://langserver.org/" target="_blank">language server protocol</a>. Users who want to get started with Atom-IDE will need to install the Atom IDE UI package as well as an IDE language support package (i.e. <a href="https://atom.io/packages/ide-php" target="_blank">ide-php</a>).</p>\n<p>Using Atom-IDE currently requires Atom Beta 1.21+. In the future the team plans to add support for more languages, which will most likely happen through outside package contributions.</p>\n<p>&#8220;With the help of our community, we plan to expand the number of languages that Atom-IDE can support and make it possible for you to run and edit applications, making Atom-IDE a true IDE,&#8221; Damien Guard said. &#8220;We hope to see future language support for the great languages out there including Rust, Go, Python, etc.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 14 Sep 2017 02:12: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:"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:93:"WPTavern: Display Widgets Plugin Permanently Removed from WordPress.org Due to Malicious Code";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74768";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/display-widgets-plugin-permanently-removed-from-wordpress-org-due-to-malicious-code";s: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:6033:"<p><a href="https://wordpress.org/plugins/display-widgets/" target="_blank">Display Widgets</a>, a plugin with more than 200,000 active installs, has been removed from WordPress.org due to its authors inserting malicious code. SEO consultant <a href="https://www.linkedin.com/in/david-law-9444b637/" target="_blank">David Law</a> was the first to bring this issue to the attention of the plugin team after discovering that Display Widgets was inserting content into sites from external servers and also collecting visitor data without permission. He posted to the WordPress.org forums <a href="https://wordpress.org/support/topic/display-widgets-plugin-v2-6-1-deleted-from-the-plugin-repository/" target="_blank">several</a> <a href="https://wordpress.org/support/topic/display-widgets-plugin-v2-6-3-1-includes-hacking-code/" target="_blank">times</a> to warn other users.</p>\n<p>Wordfence has been warning its customers about the plugin during the past several months and published a <a href="https://www.wordfence.com/blog/2017/09/display-widgets-malware/" target="_blank">timeline</a> tracking how Display Widgets was removed from WordPress.org on four separate occasions. According to their independent investigation, the plugin included a backdoor that allowed the plugin author to publish spam content to the sites where Display Widgets is installed. It also prevented logged-in users from being able to see the content.</p>\n<p><a href="https://pagely.com/blog/2017/09/malicious-code-display-widgets/" target="_blank">Pagely banned the Display Widgets plugin</a> from its hosting platform this week:</p>\n<blockquote><p>For our customer’s safety, we have banned the plugin from our customer sites&#8230;The plugin will remained banned on our network until a time that we see someone has taken responsibility for the plugin and the future of patching its code.</p></blockquote>\n<p>Display Widgets had recently changed hands, as it was acquired from the team that created Formidable Forms. The previous owners have issued a warning about the plugin on Twitter, advising users to remove it from their sites.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">We don''t have a way of contacting users of our old Display Widgets plugin. But if you are using it you should uninstall immediately.</p>\n<p>&mdash; Formidable Forms (@FormidableForms) <a href="https://twitter.com/FormidableForms/status/907654976708726787">September 12, 2017</a></p></blockquote>\n<p></p>\n<p>It is not yet confirmed whether the plugin was acquired solely for the purpose of distributing malware, but its new owners have been fairly persistent about getting it added back to WordPress.org after each of its violations.</p>\n<h3>Display Widgets Users Advised to Update to Version 2.7 or Remove the Plugin</h3>\n<p>Users have no way of finding out that they are running malicious code unless they hear about from their host, security company, or some other third party. They do not receive a notice in the WordPress admin about the plugin having been removed from the directory. Since Display Widgets was a fairly popular plugin, there are likely many sites that still have it active and those website owners are probably unaware of the spam content they are publishing.</p>\n<p>Yesterday the plugin team issued a notice that <a href="https://wordpress.org/support/topic/display-widgets-2-7-is-safe/" target="_blank">Display Widgets 2.7 is a clean version</a> that restores the plugin to version 2.0.5 before the malicious code was added:</p>\n<blockquote><p>We will be leaving this version deploying updates, however at this time we will NOT be allowing for its adoption. The second owner has effectively destroyed any trust a person might have in the plugin.</p>\n<p>Note: You CANNOT visit the page or download it as a new plugin for a reason. This plugin is done. It’s not supported, it’s not worked on, nothing. So if you have it, upgrade. Otherwise, find something else to use.</p></blockquote>\n<p>Display Widgets is now likely to end up in the graveyard of abandoned plugins, but there are many other options for adding conditional widget display to WordPress sites. Jetpack&#8217;s <a href="https://jetpack.com/support/widget-visibility/" target="_blank">widget visibility module</a>, <a href="https://wordpress.org/plugins/widget-options/" target="_blank">Widget Options</a> by Phpbits Creative Studio, <a href="https://wordpress.org/plugins/custom-sidebars/" target="_blank">Custom Sidebars</a> by WPMU Dev, and <a href="https://wordpress.org/plugins/content-aware-sidebars/" target="_blank">Content Aware Sidebars</a> are a few popular alternatives on WordPress.org.</p>\n<p>The plugin team does not currently disclose why certain plugins have been closed or removed from WordPress.org, but they are working on providing better communication for users. One meta trac <a href="https://meta.trac.wordpress.org/ticket/2627" target="_blank">ticket</a> requests that closed plugins have a public page instead of disappearing completely. In another related <a href="https://meta.trac.wordpress.org/ticket/2860" target="_blank">ticket</a>, plugin team member Mika Epstein has proposed that when plugins are closed or disabled, there should be a dropdown for WordPress.org admins to select a reason why. She suggested the following as available options:</p>\n<ul>\n<li>Security Issue</li>\n<li>Author Request</li>\n<li>Guideline Violation</li>\n<li>Licensing/Trademark violations</li>\n<li>Merged into Core</li>\n</ul>\n<p>The issue with Display Widgets was fairly public as users posted about their investigations on the WordPress.org support forums and various companies issued warnings about it. However, many plugins are disabled without the public knowing why. Even a short explanation like the proposed examples above would be a major improvement over leaving WordPress.org plugin users in the dark. It would assist site owners in knowing whether they need to prioritize looking for an alternative or simply wait until the situation is resolved.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Sep 2017 20:08: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:"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:31:"HeroPress: Making My Own Normal";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=2098";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:114:"https://heropress.com/essays/making-my-own-normal/#utm_source=rss&utm_medium=rss&utm_campaign=making-my-own-normal";s: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:8262:"<img width="960" height="480" src="http://20094-presscdn.pagely.netdna-cdn.com/wp-content/uploads/2017/09/091317-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: There are more sorts of normal than I could ever imagine." /><p>As long as I can remember being normal was my only goal in life. If only I could be normal, then everything would be alright. There was not a lot wrong in my life when I was a kid, growing up in a small dutch town. I had a normal family with 2 parents (a mum and a dad) and a younger sister. My life was pretty normal. The problem was: It didn’t feel normal; I didn’t feel normal. You see, everybody was going through life living by certain rules and I lived my life not knowing those rules. Nobody told me, but apparently they told everybody else.</p>\n<h3>Understanding</h3>\n<p>When I was 35 I got diagnosed with Asperger syndrome. I cannot tell you how relieved I was after receiving such a clear diagnoses. All those years working so hard to fit in there was an explanation why I didn’t. Why I couldn’t. That was a big deal. It was not that I wouldn&#8217;t that I didn’t try hard enough or was to lazy. There was something different about me why I couldn’t. Not understanding the rules of life? Being clumsy and inappropriate in social situation? Being obsessed about some things and totally not interested in others? It was all part of the package.</p>\n<blockquote><p>Getting the right diagnosis changed everything and at the same time it didn’t change anything.</p></blockquote>\n<p>The problems I had to face were still the same. The way to handle them just got more clear. And there was help. I started reading books, I started therapy and I started working with a coach to find a way to integrate this new knowledge into my life. I started looking at what I needed (what??) and finding ways to take care of myself. I really thought this was it. I found the keys, I could learn the rules and finally be a normal person.</p>\n<p>And then I got fired.</p>\n<p>Having a job was a big part of being normal in my head. Getting fired ruined my chances of ever getting there. I was working as an assistant manager in the local library. I liked my job, and the people I worked with and they liked me. I loved going to work. But the library had to cut their expenses and I was one of the people that got fired. It happens but I was completely shocked.</p>\n<p>My experiences with jobs were not good (to put it mildly). There wasn’t one I kept longer than 2 years. You can do the math; I had a lot of jobs since I started working. Some were fun most were not. I got fired many of times. Getting fired was not a new thing. Liking a job and not wanting to get fired and getting fired anyway was what upset me the most. So I decided to start my own company.</p>\n<h3>Taking Control</h3>\n<p>Looking back it was a ridiculous plan but strangely enough, it worked out. I started helping people with their Social Media and building website with WordPress.</p>\n<p>I learned WordPress for fun. I wasn’t interested in computers or tech stuff. I was just a little obsessed with making a website for the domain name my boyfriend gave me for my birthday a few years earlier. I had nothing to say but was totally fascinated by what you can do with a website. It was like magic to me. Some written code turned into a beautiful page, or an ugly one. I wanted to know all about that. Building things with HTML and CSS was easy. Code is logic (and poetry of course;-)). It does what you tell it to do. If it doesn’t you did something wrong. Never a discussion about it.</p>\n<p>I shied away from people. It was too confusing for me now that I found something that was so easy and logical.</p>\n<blockquote><p>I could make money without seeing other people, it felt like heaven.</p></blockquote>\n<p>For a while. This is really what makes this whole thing so disturbing. I want to be alone, but also want to be around other people. I appear to be good with people. A lot of people like me (who knew?!). They have no idea how confusing it is not knowing what the underlying rule set is others are acting by. It’s like interacting with someone from a totally different culture speaking a different language but both of you don’t know that. I got really good at guessing things through the years, but that didn’t make it any less uncomfortable. I also got really scared. Because not all people are understanding and friendly when you try to explain.</p>\n<h3>And Then WordCamp</h3>\n<p>In 2011 I went to my first WordPress meetup. I was shocked! These people did what I did and actually knew what they were doing and talked about it. I was blown away with all this new knowledge and information. I needed to know more and learn more. So I went back into my WordPress cave and studied, practiced and learned more.</p>\n<p>WordCamp Europe happened for the first time in 2013 in The Netherlands. I signed up as a volunteer. I visited WordCamp NL the year before. As a visitor I didn’t know how to meet new people. That was a lonely experience. I loved the knowledge that was shared but I knew I had to find a way to talk to those people. I figured being a volunteer would give me something to do and a reason to talk to people. And it did.</p>\n<p>I met new people, I was shy, I was scared, I acted totally inappropriate and I was exhausted for a week after the event but I did it. The people were nice. Some seem to like me and I had fun. This was a totally new experience. If only this could normal.</p>\n<blockquote><p>I attended more WordCamps, always as a volunteer, that was my safe place.</p></blockquote>\n<p>My confidence grew. The number of people I knew grew. The amount of fun I had grew. And never ever did I feel not normal. As my confidence grew I got more visible and things got even better. It’s an upward spiral. This year I held my first talk, at WordCamp London. I was MC at WordCamp EU in Paris en I am on the organising team for WordCamp EU 2018 (BIG things!).</p>\n<p>Did these experiences end my quest to becoming “normal”?</p>\n<p>When I turned 40 I decided to quit the quest. I was done trying to be normal. Not because I became normal but I broadened my worldview. There are more sorts of normal than I could ever imagine. It took me a while ( and a lot of redirections) to find the one that fits me best.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: Making My Own Normal" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Making%20My%20Own%20Normal&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fmaking-my-own-normal%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Making My Own Normal" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fmaking-my-own-normal%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fmaking-my-own-normal%2F&title=Making+My+Own+Normal" rel="nofollow" target="_blank" title="Share: Making My Own Normal"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/making-my-own-normal/&media=https://heropress.com/wp-content/uploads/2017/09/091317-150x150.jpg&description=Making My Own Normal" rel="nofollow" target="_blank" title="Pin: Making My Own Normal"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/making-my-own-normal/" title="Making My Own Normal"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/making-my-own-normal/">Making My Own Normal</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Sep 2017 12:00: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:24:"Wendie Huis in ‘t Veld";s: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:66:"WPTavern: WordPress.org Adds New Support Rep Role for Plugin Pages";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=74726";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"https://wptavern.com/wordpress-org-adds-new-support-rep-role-for-plugin-pages";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1424:"<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/collaboration.jpg?ssl=1"><img /></a></p>\n<p>WordPress.org introduced a new feature for plugin pages this week that highlights official support representatives. Plugin authors can now find the UI for adding support reps under the Advanced View on the plugin page. Unlike the contributors and developers role, individual support reps do not have commit access and do not appear on the plugin details page.</p>\n<p>The new <a href="https://make.wordpress.org/plugins/2017/09/04/plugin-support-reps/" target="_blank">&#8220;support rep&#8221; role</a> is especially useful for larger plugins that have a support team managing the forum. It includes the ability to mark forum topics as resolved or sticky. Previously, only plugin authors were able to do this, which made it difficult for support teams to fully manage forum topics. Support reps will now have their interactions highlighted in the forum:</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/support-rep-reply.png?ssl=1"><img /></a></p>\n<p>Adding these official indicators to support reps&#8217; replies puts them in context within the thread and lends more authority to their answers. It is a small addition that will allow plugin shops to provide better support to their users. The feature is already active on WordPress.org and available for any plugin author to use.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Sep 2017 21:38:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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:125:"WPTavern: Gutenberg to Offer New Approach to TinyMCE in WordPress 5.0, a Plugin to Bring Back Old Interface Will be 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=74639";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/gutenberg-to-offer-new-approach-to-tinymce-in-wordpress-5-0-a-plugin-to-bring-back-old-interface-will-be-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:9397:"<a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2016/08/typewriter.jpg?ssl=1"><img /></a>photo credit: <a href="https://stocksnap.io/photo/4OURRGDU7Z">Sergey Zolkin</a>\n<p>The WordPress community is currently knee-deep in Gutenberg takes, as the new editor is poised to impact nearly every corner of the ecosystem when it <a href="https://wptavern.com/matt-mullenweg-addresses-concerns-about-gutenberg-confirms-new-editor-to-ship-with-wordpress-5-0" target="_blank">ships in WordPress 5.0</a>. With billions of dollars flowing through the WordPress economy, tensions are high, as many people support themselves and their families with the revenue earned from products and services that have been built on the existing editor.</p>\n<p>First impressions range from outright rejection of the new editor to those who embrace it and are hopeful for what it will bring to WordPress. For the past several years, most major new features added to WordPress have come through the feature plugin/feature project process where release leads and other contributors decide whether a proposed feature is ready for merge. The Gutenberg project is taking a somewhat different path to core in that Matt Mullenweg has already confirmed that <a href="https://wptavern.com/matt-mullenweg-addresses-concerns-about-gutenberg-confirms-new-editor-to-ship-with-wordpress-5-0" target="_blank">Gutenberg will ship with WordPress 5.0</a>, but the release will come out when Gutenberg is ready. This approach is part of Mullenweg&#8217;s new strategy for core development that makes releases more project-based instead of time-based.</p>\n<p>One of the most common concerns that developers and agency owners have about the plan to include Gutenberg in 5.0 is that they may need to hold back some of their sites from updating. The most vocal opponents have called for a way to &#8220;opt out&#8221; of Gutenberg so that it isn&#8217;t forced on their users.</p>\n<p>In a post titled &#8220;<a href="http://valiantchickendigital.com/blog/wordpress-new-coke-moment/" target="_blank">WordPress is about to have its New Coke moment</a>,&#8221; Nate Hoffelder shared his first impressions of the new edidtor after taking it for a test run. He said he appreciates the changes it promises but was unable to figure out how to create the blocks in the demo and worries about the &#8220;average non-techie&#8221; trying to use the interface.</p>\n<p>Hoffelder referenced Coca-Cola&#8217;s attempt to introduce New Coke in April 1985, which quickly ended in consumers calling for a return of the original flavor.</p>\n<p>&#8220;My gut feeling is that if users share my frustrations with Gutenberg, they will demand the return of the old interface,&#8221; Hoffelder said. &#8220;But the official release is months and months away, so it is entirely possible that a UX (user experience) expert will force the Gutenberg developers to make Gutenberg easier to use before it is inflicted upon an unsuspecting public.&#8221;</p>\n<h3>WordPress Users Will be Able to Restore the Old Editor with a Plugin after Gutenberg Lands in Core</h3>\n<p>WordPress will move forward with the Gutenberg editor as the default experience in the 5.0 release, but Matt Mullenweg confirmed in a <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/#comment-587616" target="_blank">comment</a> on his blog that a plugin will be available for users who want to restore the old editor.</p>\n<p>&#8220;Gutenberg uses TinyMCE, so a better way to think of it is that Gutenberg is a new version of our approach to TinyMCE,&#8221; Mullenweg said. &#8220;It will be the default experience of WP, for people that want to use something more like what’s currently there we’ll have a plugin they can use.&#8221;</p>\n<p>This should bring some relief to developers who will not yet have updated their extensions to work with Gutenberg, as well as agency owners who are not ready to give their clients access to the new editor.</p>\n<p>In his post, titled <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason" target="_blank">We Called it Gutenberg for a Reason</a>, Mullenweg shared his vision for how the new editor will will re-imagine TinyMCE and the advantages it will bring for plugin editors:</p>\n<blockquote><p>Plugin developers will be able to completely integrate into every part of WordPress, including posts, pages, custom post types, and sidebars without having to hack TinyMCE or squeeze their entire feature behind a toolbar button. Today, every plugin that extends WordPress does it in a different way; Gutenberg’s blocks provide a single, easy-to-learn entry point for an incredible variety of extensions. Some folks have already begun to port their plugins over, and are finding that they’re easier to build and have a much improved UI.</p></blockquote>\n<p>For developers who are worried about the compatibility of their metaboxes, Mullenweg said <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/#comment-587620" target="_blank">a plugin will be available for providing the legacy edit page for metaboxes</a>. One commenter, whose sites are heavily dependent on Advanced Custom Fields (ACF), asked if there is going to be a version of WordPress that will get long-term support for sites that can&#8217;t be upgraded to 5.0 without breaking.</p>\n<p>&#8220;There won’t be a version of WP like that, but there will definitely be a plugin that gives you the legacy / old edit page. Make sure to let ACF know that Gutenberg compatibility is a top priority,&#8221; Mullenweg said.</p>\n<p>Scott Kingsley Clark, lead developer of the Pods plugin, said this support for legacy PHP meta boxes is welcome news for the project but that Pods is also looking to get on board with Gutenberg once the project&#8217;s engineers have a solution for metaboxes.</p>\n<p>&#8220;I’m very excited to start using the new meta boxes from Gutenberg once the API supports it and gives us more to utilize,&#8221; Clark said. &#8220;As soon as that’s available, count us in for immediate adoption.&#8221;</p>\n<p>Despite assurances that a plugin will be available to restore the old interface, some are still concerned about how Gutenberg will impact the WordPress ecosystem. The average WordPress user has never heard of Gutenberg and its inclusion in 5.0 will be a major change.</p>\n<p>In a recent article on WPShout Fred Meyer contends that <a href="https://wpshout.com/stop-presses-gutenberg-wordpress-needs-doesnt-go-nearly-far-enough/" target="_blank">Gutenberg doesn’t go nearly far enough</a> towards giving users what they really want, which he identifies as front-end editing and the ability to create layouts within post content.</p>\n<p>&#8220;Gutenberg doesn’t go nearly far enough,&#8221; Meyer said. &#8220;It won’t make WordPress’ core content editor competitive with hosted builder solutions, or even with WordPress’ own themes and plugins (including badly built, bad-for-the-community solutions like Visual Composer.)&#8221;</p>\n<p>Meyer believes Gutenberg has the opportunity to defragment WordPress&#8217; ecosystem of page building tools, but only if it moves towards providing &#8220;a feature-rich, developer-friendly, front-end page builder and content editor.&#8221;</p>\n<p>In responding to feedback from the community, Gutenberg design lead Tammie Lister has said that the project is currently focusing on editing before tackling the page building experience. The team has also been <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/#comment-587693" target="_blank">working with the authors of page builder plugins</a> ahead of the next focus on customization.</p>\n<p>&#8220;It is still a little early to say what will happen to plugins and builders,&#8221; Lister <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/#comment-587692" target="_blank">said</a>. &#8220;Initially, Gutenberg is focusing on the editor. The next stage is for the Customization focus (the building of pages). One thing that will need to happen is a lot of testing of existing plugins with Gutenberg. That’s how we can ensure things do work and limit issues. Ultimately, more and more plugins won’t be needed – or at least not so many together to achieve simple things. This benefits users and creates a better, more unified experience for all.&#8221;</p>\n<p>If users&#8217; first impression of Gutenberg is that it is unable to deliver on all of the lofty promises of the project, they may return to the old interface en masse. WordPress will then have a battle to convince users to give it a another chance as the experience improves to include customization.</p>\n<p>Multi-column layouts, which are the gateway to page building, are <a href="https://wptavern.com/gutenberg-contributors-explore-adding-drag-and-drop-and-multi-column-support-for-blocks" target="_blank">not currently within the scope of the first official version coming to core</a>. Gutenberg&#8217;s one-dimensional, vertically stacking approach to designing pages isn&#8217;t very inspiring. This may frustrate average users whose expectations have not been tempered with the understanding that a future version will include an expanded page building experience. A plugin that allows users to opt out until it is an improvement over their current tools is going to be crucial for keeping the community happy.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Sep 2017 04:22: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: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:100:"WPTavern: “The Final Word” Plugin Extends O2 to Pin a Highlighted Comment to the Top of a Thread";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74707";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:105:"https://wptavern.com/the-final-word-plugin-extends-o2-to-pin-a-highlighted-comment-to-the-top-of-a-thread";s: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:3311:"<p>&#8220;<a href="https://wordpress.org/plugins/the-final-word/" target="_blank">The Final Word</a>&#8221; is a new plugin that extends O2 to highlight a comment at the top of a thread. <a href="https://github.com/Automattic/o2" target="_blank">O2</a> is the plugin successor to <a href="https://wordpress.org/themes/p2/" target="_blank">P2</a>, Automattic&#8217;s group blogging theme that introduced quick posting from the front page with real-time comment updates. The code was <a href="https://wptavern.com/o2-is-now-available-on-github" target="_blank">released on GitHub in 2015</a> and it powers the <a href="http://make.wordpress.org" target="_blank">make.wordpress.org</a> blogs.</p>\n<p>If you use O2 as a WordPress contributor or within another organization, then you have likely been a part of lengthy conversations that require a decent chunk of time to read and comprehend. Hugh Lashbrooke <a href="https://make.wordpress.org/meta/2017/08/24/o2-plugin-request-the-final-word/" target="_blank">created The Final Word for use on the WordPress Community Team blog</a> so that long discussion threads could be summed up in a single comment. He likened the new feature as something similar to the &#8220;accepted answer&#8221; function on Stack Exchange or other support forums where the best answer floats to the top. Discussions in the Community P2 often involve decision making, and the plugin is useful for highlighting the team&#8217;s conclusion on a matter.</p>\n<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/top-comment.png?ssl=1"><img /></a></p>\n<p>The Final Word gives users who are able to edit the post the ability to mark a specific comment as the &#8220;top comment.&#8221; Other features include the following:</p>\n<ul>\n<li>The top comment is displayed at the top of the comment list with a ‘view in context’ anchor link</li>\n<li>The top comment is also highlighted in context in the thread</li>\n<li>Only one comment can be selected as the top comment</li>\n<li>The top comment flag can be removed</li>\n<li>Includes basic styling for top comments</li>\n<li>‘Top comment’ label can be translated and/or filtered</li>\n</ul>\n<p>The plugin currently will not work without 02 enabled because of its specific way of handling comments, but Lashbrooke said it may be updated in the future to work without O2. (While O2 is not theme-dependent, the plugin is also not guaranteed to work with every theme and is recommended to be used in combination with the <a href="https://wpcom-themes.svn.automattic.com/p2-breathe" target="_blank">p2-breathe theme</a>.)</p>\n<p>The Final Word is now active on the <a href="http://make.wordpress.org/community" target="_blank">WordPress Community team&#8217;s blog</a> and is available for other teams to activate as well. With the number of O2 blogs that many contributors are subscribed to, there is a massive amount of information and discussion to keep up with. This plugin gives thread authors and team leaders the ability to summarize conversations and keep them more manageable for readers and participants. The Final Word is available on both <a href="https://wordpress.org/plugins/the-final-word/" target="_blank">WordPress.org</a> and <a href="https://github.com/hlashbrooke/The-Final-Word" target="_blank">GitHub</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Sep 2017 04:10:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:91:"WPTavern: Equifax Launches WordPress-Powered Site for Consumers Affected by Security Breach";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74677";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://wptavern.com/equifax-launches-wordpress-powered-site-for-consumers-affected-by-security-breach";s: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:7328:"<a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2015/03/security.jpg?ssl=1"><img /></a>photo credit: <a href="http://www.flickr.com/photos/58441544@N00/2660230441">Lock</a> &#8211; <a href="https://creativecommons.org/licenses/by/2.0/">(license)</a>\n<p>Equifax has launched <a href="https://www.equifaxsecurity2017.com/" target="_blank">a WordPress-powered website</a> to connect with consumers affected by its recent security breach, which compromised 143 million customers&#8217; personal data. The exposed data includes names, birth dates, social security numbers, addresses, credit card numbers, driver&#8217;s license numbers, and other sensitive financial information.</p>\n<p>The <a href="https://www.equifaxsecurity2017.com/" target="_blank">equifaxsecurity2017.com</a> site was launched shortly after disclosure to give consumers information about the security incident. Equifax reports that the company has found no evidence of unauthorized activity on its core consumer or commercial credit reporting databases but is offering free identity theft protection and credit file monitoring services to U.S. consumers who enter their last names and last six digits of their social security number into its form.</p>\n<p>Consumers are rightfully wary of the website, as the company is asking for more personal information in order to sign people up for another one of its products. Various <a href="https://www.theregister.co.uk/2017/09/08/equifax_breach_notification/" target="_blank">news</a> <a href="https://arstechnica.com/information-technology/2017/09/why-the-equifax-breach-is-very-possibly-the-worst-leak-of-personal-info-ever/" target="_blank">outlets</a> are decrying the fact that the site is built on WordPress.</p>\n<p>&#8220;What&#8217;s more, the website which Equifax created to notify people of the breach, is highly problematic for a variety of reasons,&#8221; Ars Technica Security Editor Dan Goodin said. &#8220;It runs on a stock installation WordPress, a content management system that doesn&#8217;t provide the enterprise-grade security required for a site that asks people to provide their last name and all but three digits of their Social Security number.&#8221;</p>\n<p>Goodin also referenced the output of <a href="https://www.equifaxsecurity2017.com/wp-json/wp/v2/users/" target="_blank">https://www.equifaxsecurity2017.com/wp-json/wp/v2/users/</a> which earlier in the day exposed the username for the site&#8217;s administrator before the page was protected.</p>\n<p><a href="https://i2.wp.com/wptavern.com/wp-content/uploads/2017/09/equifax-site-users-endpoint.png?ssl=1"><img /></a></p>\n<p>WordPress&#8217; handbook has a section on reporting security vulnerabilities that explains <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/#why-are-disclosures-of-usernames-or-user-ids-not-a-security-issue" target="_blank">why disclosures of usernames or user IDs is not a security issue</a>:</p>\n<blockquote><p>The WordPress project doesn’t consider usernames or user ids to be private or secure information. A username is part of your online identity. It is meant to identify, not verify, who you are saying you are. Verification is the job of the password.</p>\n<p>Generally speaking, people do not consider usernames to be secret, often sharing them openly. Additionally, many major online establishments — such as Google and Facebook — have done away with usernames in favor of email addresses, which are shared around constantly and freely. WordPress has also moved this way, allowing users to log in with an email address or username since version 4.5.</p></blockquote>\n<p>WordPress Core Security Team Lead Aaron Campbell clarified this section of the handbook to confirm that the users endpoint is intended to be an open API endpoint that serves public data.</p>\n<p>&#8220;It does in fact include usernames and user IDs (among other things) for users that have published posts in a post type that is set up to use the API, but all the data is considered public,&#8221; Campbell said.</p>\n<p>Campbell also said he is wary of entering personal data into the equifaxsecurity2017.com website, but not because it is using WordPress.</p>\n<p>&#8220;I don&#8217;t think the fact that it runs on WordPress is a concern from a security standpoint, with the caveat that I don&#8217;t know what ELSE it&#8217;s using,&#8221; Campbell said. &#8220;&#8216;Equifax&#8217; is a trusted brand, but it&#8217;s not the official Equifax domain and the SSL certificate doesn&#8217;t verify ownership. So you know your data is encrypted, but not necessarily who it&#8217;s being sent to since you don&#8217;t know who owns the site.&#8221;</p>\n<p>It&#8217;s not clear why Equifax simply didn&#8217;t build out the information site on its own domain. According to security investigator <a href="https://krebsonsecurity.com/2017/09/equifax-breach-response-turns-dumpster-fire/" target="_blank">Brian Krebs</a>, the company appears to have hired Edelman PR, a global PR firm, to handle its public response to the data breach, citing the username publicly displayed by WordPress&#8217; API. Edelman PR opted to use a free Cloudflare certificate to secure the site.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">Not only did <a href="https://twitter.com/Equifax">@Equifax</a> suffer a massive data breach, but their site about the breach is using a free shared CloudFlare SSL cert. ಠ_ಠ <a href="https://t.co/r4bvPpde1i">pic.twitter.com/r4bvPpde1i</a></p>\n<p>&mdash; Daniel Lo Nigro (@Daniel15) <a href="https://twitter.com/Daniel15/status/905953979934187520">September 8, 2017</a></p></blockquote>\n<p></p>\n<p>Consumers were also off put by the verbiage of the arbitration clause included in the terms and services of the free credit monitoring, which appears to force those who sign up to waive their rights to participate in class action lawsuits against the company.</p>\n<p>&#8220;I cannot recall a previous data breach in which the breached company’s public outreach and response has been so haphazard and ill-conceived,&#8221; Krebs said.</p>\n<p>Kenneth White, a security researcher and director of the Open Crypto Audit Project, said on Twitter that he was amazed the site was running stock WordPress but that his comments specifically referenced the sloppy implementation of the site.</p>\n<blockquote class="twitter-tweet">\n<p lang="en" dir="ltr">intent wasn''t to blast WP, this is just sloppy—default admin pages, default nginx errors, wonky certs, phish flagged…</p>\n<p>&mdash; Kenn White (@kennwhite) <a href="https://twitter.com/kennwhite/status/906152286908551168">September 8, 2017</a></p></blockquote>\n<p></p>\n<p>Due to how the site was set up, it appeared to many consumers and researchers as Equifax&#8217;s way of stalling or perhaps even scamming those who may have been affected by the breach. Various browsers flagged it as a phishing threat, and some consumers found they were given different answers from the form based on whether they checked with desktop or mobile devices. In responding to the incident with a website that appears to have been hastily implemented for its own convenience and corporate interests, Equifax has missed an opportunity to reclaim any remaining consumer confidence from the public.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 08 Sep 2017 20:04: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: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:61:"WPTavern: SWFUpload Will Officially Be Removed From 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:29:"https://wptavern.com/?p=74660";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/swfupload-will-officially-be-removed-from-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:2000:"<p>SWFUpload is an open-source library that was used by WordPress in 2011 and earlier that allowed users to upload files. The library was abandoned and replaced with <a href="http://www.plupload.com/">Plupload</a> in WordPress 3.3, released in 2011. Despite being replaced, WordPress continued to bundle the library for plugins that didn&#8217;t migrate to Plupload. In 2013, the core team <a href="http://github.com/wordpress/secure-swfupload">forked SWFUpload</a> and maintained the project, applying security fixes submitted by contributors.</p>\n<p>After six years of deprecation, the core team <a href="https://make.wordpress.org/core/2017/09/07/removing-swfupload/">has announced</a> that SWFUpload will officially be removed from WordPress core. The team searched the WordPress plugin directory and <a href="https://core.trac.wordpress.org/ticket/41752">compiled a list</a> of plugins that contain references to swfupload in their code. <a href="https://core.trac.wordpress.org/ticket/41752#comment:4">According to Weston Ruter</a>, the list includes 128 themes and plugins.</p>\n<p>Some of the most popular plugins include:</p>\n<ul>\n<li><a href="https://wordpress.org/plugins/wysija-newsletters/">MailPoet 2</a></li>\n<li><a href="https://wordpress.org/plugins/wp-all-import/">WP All Import</a></li>\n<li><a href="https://wordpress.org/plugins/profile-builder/">Profile Builder</a></li>\n<li><a href="https://wordpress.org/plugins/flash-album-gallery/">Gallery Grand Flagallery</a></li>\n</ul>\n<p>The team is working on a way to provide enough backwards compatibility to ensure there are no JavaScript errors and an upload form is displayed instead of embedded Flash. Andrew Ozz also apologized to plugin authors noting that the list likely contains some false positives. If you use one or more of the plugins mentioned above, please get in touch with the author and ask if it will function <a href="https://make.wordpress.org/core/2017/09/07/removing-swfupload/">without SWFUpload in core</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 08 Sep 2017 08:06:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:59:"WPTavern: WordCamp Ann Arbor to Host Second WordCamp WarmUp";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74654";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://wptavern.com/wordcamp-ann-arbor-to-host-second-wordcamp-warmup";s: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:2080:"<p><a href="https://2017.annarbor.wordcamp.org/">WordCamp Ann Arbor, MI</a>, is set to take place October 13-14 and for the second year in a row, organizers will host a secondary event called <a href="https://wptavern.com/wordcamp-warmup-an-experimental-event-aimed-at-breaking-the-ice-for-new-wordcamp-attendees">WordCamp WarmUp</a>. WordCamp WarmUp provides an environment for attendees to break the ice and meet new people before the main event.</p>\n<p>Janelle Reichman is co-organizing WordCamp WarmUp. &#8220;I&#8217;ve been running my own WordPress business for about eight years,&#8221; Reichman said. &#8220;However, I attended my first WordCamp just last fall. I&#8217;ll never forget it &#8211; I was pretty much terrified.</p>\n<p>&#8220;But then, I got an invitation to a WordCamp WarmUp. I couldn&#8217;t believe my luck. I couldn&#8217;t believe there was an event made exactly for people like me, who were shaking in their boots at the prospect of showing up at a conference and not knowing anybody.</p>\n<p>&#8220;I attended the WarmUp, made friends, saw them all the next day at WordCamp, and ended up having an amazing and unforgettable time&#8221;</p>\n<p>Unlike last year&#8217;s WarmUp, details for this years event will only be announced to WordCamp Ann Arbor <a href="https://2017.annarbor.wordcamp.org/tickets/">ticket holders</a>. The event is maxed out to fifty people and is available on a first come, first serve basis. Appetizers and beverages will be provided.</p>\n<p>Rebecca Gill, founder of <a href="https://www.web-savvy-marketing.com/">Web-Savvy-Marketing</a>, organized <a href="https://wptavern.com/wordcamp-warmup-is-a-success">the event last year</a> and <a href="https://www.web-savvy-marketing.com/2016/10/recap-of-wordcamp-ann-arbors-wordcamp-warmup/">considered it a success</a>. &#8220;Not only did most WarmUp guests arrive right on time, we had a full room of WarmUp attendees and even had a few unexpected friends show up,” Gill said.</p>\n<p>Ticket holders can expect to see an email with event details within the next few weeks.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 08 Sep 2017 03:14:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:44;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:116:"WPTavern: Gutenberg 1.1.0 Adds Autocomplete for Blocks, Developers Elaborate on How New Editor Will Work with 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=74545";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:126:"https://wptavern.com/gutenberg-1-1-0-adds-autocomplete-for-blocks-developers-elaborate-on-how-new-editor-will-work-with-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:4082:"<p>Gutenberg contributors continue marching forward this week on their relentless drive to improve the usability of the controversial new editor that will <a href="https://wptavern.com/matt-mullenweg-addresses-concerns-about-gutenberg-confirms-new-editor-to-ship-with-wordpress-5-0" target="_blank">ship with WordPress 5.0</a>. Meanwhile, discussions about Gutenberg&#8217;s timing, implications, UI, architecture, and other aspects of the project continue across the web, as the community grapples with what this new editor will mean for the future of WordPress.</p>\n<p><a href="https://make.wordpress.org/core/2017/09/05/whats-new-in-gutenberg-september-5/" target="_blank">Version 1.1.0</a> was released this week with a new autocomplete-shortcut for adding new blocks without leaving the keyboard.</p>\n<p>Many testers have been frustrated with the amount of pointing and clicking required to create new blocks. Autocomplete for blocks is a new feature that partially answers this problem, but it relies on the user knowing that typing a slash <code>/</code> in a new default paragraph block will trigger autocomplete. It may also be added to other blocks in the future.</p>\n<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/autocomplete.gif?ssl=1"><img /></a></p>\n<p>&#8220;We still need to get the point-click/tap interactions right since most people won’t discover, remember, nor use keyboard shortcuts,&#8221; Gutenberg engineer Matías Ventura <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/#comment-587704" target="_blank">said</a> in response to user feedback on the plugin.</p>\n<p>This release of the plugin adds the ability to remove images from the gallery block inline. It works smoothly and resizes the thumbnail previews to fit the available space after an image is removed.</p>\n<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/gutenberg-gallery-delete-image.png?ssl=1"><img /></a></p>\n<p>Version 1.1.0 also includes small updates like the ability to set links to <a href="https://github.com/WordPress/gutenberg/pull/2628" target="_blank">open in a new window</a>, accessibility improvements to the add-new-category form, caption styling for video blocks, adjustments to column width calculation in the gallery block, and many other tweaks and improvements. The <a href="http://gutenberg-devdoc.surge.sh/" target="_blank">Gutenberg docs</a> also received <a href="https://github.com/WordPress/gutenberg/pull/2638" target="_blank">an updated design</a> and improvements to the content.</p>\n<h3>A Preview of How Gutenberg Will Interact with Themes to Build Websites</h3>\n<p>Gutenberg engineers elaborated on how they expect the new editor will work with themes in a <a href="https://make.wordpress.org/core/2017/08/31/gutenberg-themes/" target="_blank">post</a> on the make.wordpress./core blog. Matías Ventura published two video examples to demonstrate where they see Gutenberg headed on its journey towards becoming a full-fledged website building tool. Ventura said this is the long-term goal after the project completes the post and page editing milestone.</p>\n<p>The first video shows how Gutenberg can be used for page building, starting with a blank slate and a theme that defines specific styles for blocks. The second one shows how a theme might include templates with blocks already in place that provide users with a guided page-building experience.</p>\n<p></p>\n<p></p>\n<p>These examples clarify some of the benefits the team is aiming for with Gutenberg and how WordPress theme authors will be able to build more user-friendly experiences on top of the new editor.</p>\n<p>&#8220;These are quickly put together, but I hope it shows how things can progress even with very straightforward theme integration,&#8221; Ventura said. &#8220;As soon as we expand the scope and include more blocks (site title, site header, menus, more widgets, etc), and describe a way to store page templates as a «list of blocks», Gutenberg would be fundamentally capable of building an entire website.&#8221;</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 Sep 2017 20:02:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:45;a:6:{s:4:"data";s:13:"\n	\n	\n	\n	\n	\n	\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:97:"WPTavern: WPWeekly Episode 287 – WordPress Meetups, Events, and WordCamps with Andrea Middleton";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74614&preview=true&preview_id=74614";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://wptavern.com/wpweekly-episode-287-wordpress-meetups-events-and-wordcamps-with-andrea-middleton";s: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:1776:"<p>In this episode, <a href="https://jjj.blog/">John James Jacoby</a> and I are joined by <a href="https://andreamiddleton.blog/">Andrea Middleton</a>, Dot org Wrangler at Automattic. Middleton supports WordPress community organizers by helping them <a href="https://make.wordpress.org/community/">plan community events</a> that inspire people to do more with WordPress, connect the community, and contribute to the WordPress project.</p>\n<p>We discussed a variety of topics including, whether or not speakers should be compensated, regional WordCamps, and improvements that have been made to WordCamp.org. By the way, if you can lend a hand with <a href="https://meta.trac.wordpress.org/ticket/2992">this trac ticket</a>, it would be appreciated.</p>\n<p>We also discussed the possibilities of expanding WordCamps to be more subject focused events. Last but not least, we talked about the successful <a href="https://wptavern.com/wordpress-to-launch-experimental-wordcamp-incubator-program">WordCamp Incubator program</a> and whether or not it will continue.</p>\n<h2>WPWeekly Meta:</h2>\n<p><strong>Next Episode:</strong> Wednesday, September 13th 3:00 P.M. Eastern</p>\n<p><strong>Subscribe To WPWeekly Via Itunes: </strong><a href="https://itunes.apple.com/us/podcast/wordpress-weekly/id694849738" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via RSS: </strong><a href="https://wptavern.com/feed/podcast" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Subscribe To WPWeekly Via Stitcher Radio: </strong><a href="http://www.stitcher.com/podcast/wordpress-weekly-podcast?refid=stpr" target="_blank" rel="noopener">Click here to subscribe</a></p>\n<p><strong>Listen To Episode #287:</strong><br />\n</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 07 Sep 2017 01:59:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:37:"HeroPress: Crafting the Life You Want";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=2086";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:110:"https://heropress.com/essays/crafting-life-want/#utm_source=rss&utm_medium=rss&utm_campaign=crafting-life-want";s: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:9042:"<img width="960" height="480" src="http://20094-presscdn.pagely.netdna-cdn.com/wp-content/uploads/2017/09/090617-1024x512.jpg" class="attachment-large size-large wp-post-image" alt="Pull Quote: WordPress turned out to be a tool that led me to meeting a fantastic community of interesting and friendly people." /><p>I grew up in a small country town in Poland, where life was pretty simple. People would know all the neighbors, they would pay each other visits every week to talk about what’s been going on in the community and to have a beer or two. It all seemed great until the moment when I got a bit older and went to Junior High School. My hair, unlike all other boys’, was long and I enjoyed listening to rock / metal music, the genre that was considered weird, unknown, maybe even evil.</p>\n<blockquote><p>Suddenly this friendly community started treating me like an alien, someone they refused to treat as one of their own or spend time with.</p></blockquote>\n<p>Almost every day I would get some beatings from school bullies, they would pull my hair, call me names, in short &#8211; my life became miserable. I had to find a way to survive, something to focus on.</p>\n<p>That’s when I started spending even more time with my computer, playing Diablo (I even set up a Diablo fan club which became quite popular in Poland) and other multiplayer games that connected me with new people. All these interesting personalities living there, somewhere far away, (and the unforgettable sound of a dial-up modem) made me believe there was something good out there waiting for me.</p>\n<p>Next, natural step was the analysis of how a game could be created. I spent months looking at the code and analyzing its components. There weren’t many tutorials back then, so sometimes it took a while to figure things out. But it all led to building my first website, which was full of tables and hundreds of colorful elements, everything was there! I was so proud of myself! <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="🙂" class="wp-smiley" /></p>\n<p>When I went to High School, I already knew a thing or two about coding and I wasn’t afraid to use it! I moved to a big city, got my first job as a graphic designer and started renting my own apartment.</p>\n<blockquote><p>I was very young, full of energy and determination to change my life.</p></blockquote>\n<p>After a while I got another job and another, and suddenly I realized that coding became an essential part of my life. Instead of learning chemistry and biology, I spent my nights learning new ways of improving my skills and finally was offered a pretty sweet job in a huge company, where I led a team of front-end developers. Yes, I was about 19, but I felt so mature. It’s so funny now, when I recall that feeling of accomplishing “everything”, but hey, I knew CSS ‘hacks’ on IE 6, I knew it all!</p>\n<blockquote><p>Of course, I had heard of WordPress, but none of the ‘true’ coders would use it, so why would I want to dig into that?</p></blockquote>\n<p>Well, I’m glad someone helped me change my mind. In 2010 my colleague invited me to join him on WordCamp. In Poland WordPress was still considered a cute little tool for creating internet blogs, so I thought going there would be a waste of time, but it turned out to be a life-changing experience. The opportunity to meet people from different countries, hear them talk about the growing possibilities of WordPress made me realize I was in the right place. The fact that a few people I met there are still my friends today only stresses the importance of that event.</p>\n<blockquote><p>It simply dawned on me that it’s not really about the CMS or other technical elements.</p></blockquote>\n<p>WordPress turned out to be a tool that led me to meeting a fantastic community of interesting and friendly people. And this was one of the reasons I wanted to delve further into WordPress.</p>\n<p>Two years later I started cooperating with a company based in the United States. Their main tool to build sites on was WordPress, obviously. By the way, I’ve been with this company for over 5 years now and to be honest, I can’t imagine my life without those guys now, but I don’t want to keep you here too long, so let’s move on. I quit my safe, ‘nine to five’ job to the dismay of my parents and started working remotely. Everything was so new, so exciting, but at the same time physically and mentally exhausting. I was doing my master’s degree in e-business and I rarely slept through the night, mostly because my clients were from different time zones.</p>\n<p>To make things more exciting, I applied for a grant from the European Union and registered my own little company in Poland. But hey, I still felt unsated. It took me around a year to decide to move my company to the United States and go there to manage it. Actually, part of this time was spent on convincing my wife to quit the job she didn’t like anyway, but again, no subplots.</p>\n<blockquote><p>To say that moving to the States was easy would be a monstrous lie.</p></blockquote>\n<p>Dealing with visas and all types of immigration documents is very time-consuming and caused us way too many sleepless nights, but eventually we got to California! I registered my company (again!), opened a bank account (you wouldn’t believe how difficult it was, so thank you, dear Russian lady for fighting with the system for over 2 hours!), and looked for a place to stay.</p>\n<p>Almost 3 years have passed, I’ve been given a chance to work with amazing people whom I truly admire, and I work for and with a few startups that, I admit, are close to my heart. One of the projects my wife and I are working on is a platform (based on WordPress, of course) that will help freelancers find good, well paid projects. Again, right time, right place, no doubt about it.</p>\n<blockquote><p>“I know you&#8217;ve heard it a thousand times before. But it&#8217;s true &#8211; hard work pays off. If you want to be good, you have to practice, practice, practice. If you don&#8217;t love something, then don&#8217;t do it.“ (Ray Bradbury)</p></blockquote>\n<p>Very often people ask me if it’s all worth it, if I’m a masochist and enjoy burning the midnight oil, but I don’t see it that way. If I have a goal, whether it’s one to create a new website, or learn how to prepare real pierogi (dumplings) for my wife, I’m ready to spend as much time as needed to accomplish it. Sure, if it’s not something I truly ‘feel’, I might not be able to devote 100 percent of my energy to make it happen, but I like to think it’s a matter of making the right choices.</p>\n<p>I’m not saying it’s all rainbows and butterflies right now, I’m not a guy who spends his days surfing or drinking cocktails. To be honest I don’t think I’ll ever be that guy. I’m still working very hard and I rarely take days off, but at least when I go to bed I have a feeling that I’ve done all I could to help others and improve my skills as a front-ender, project manager and most of all, a human being.</p>\n<div class="rtsocial-container rtsocial-container-align-right rtsocial-horizontal"><div class="rtsocial-twitter-horizontal"><div class="rtsocial-twitter-horizontal-button"><a title="Tweet: Crafting the Life You Want" class="rtsocial-twitter-button" href="https://twitter.com/share?text=Crafting%20the%20Life%20You%20Want&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fcrafting-life-want%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-fb-horizontal fb-light"><div class="rtsocial-fb-horizontal-button"><a title="Like: Crafting the Life You Want" class="rtsocial-fb-button rtsocial-fb-like-light" href="https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fcrafting-life-want%2F" rel="nofollow" target="_blank"></a></div></div><div class="rtsocial-linkedin-horizontal"><div class="rtsocial-linkedin-horizontal-button"><a class="rtsocial-linkedin-button" href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fcrafting-life-want%2F&title=Crafting+the+Life+You+Want" rel="nofollow" target="_blank" title="Share: Crafting the Life You Want"></a></div></div><div class="rtsocial-pinterest-horizontal"><div class="rtsocial-pinterest-horizontal-button"><a class="rtsocial-pinterest-button" href="https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/crafting-life-want/&media=https://heropress.com/wp-content/uploads/2017/09/090617-150x150.jpg&description=Crafting the Life You Want" rel="nofollow" target="_blank" title="Pin: Crafting the Life You Want"></a></div></div><a rel="nofollow" class="perma-link" href="https://heropress.com/essays/crafting-life-want/" title="Crafting the Life You Want"></a></div><p>The post <a rel="nofollow" href="https://heropress.com/essays/crafting-life-want/">Crafting the Life You Want</a> appeared first on <a rel="nofollow" href="https://heropress.com">HeroPress</a>.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 06 Sep 2017 12:00: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:14:"Damian Samolej";s: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:86:"WPTavern: Jetpack 5.3 Adds PHP 7.1 Compatibility, Better Control for WordAds Placement";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74547";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:96:"https://wptavern.com/jetpack-5-3-adds-php-7-1-compatibility-better-control-for-wordads-placement";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2636:"<p><a href="https://jetpack.com/2017/09/05/jetpack-5-3-php-7-1-compatibility/" target="_blank">Jetpack 5.3</a> was released with compatibility for PHP 7.1, a task the Jetpack team has been working on <a href="https://github.com/Automattic/jetpack/issues/6106" target="_blank">since January 2017</a> after they received multiple reports of <a href="https://github.com/Automattic/jetpack/issues/6629" target="_blank">failures with PHP 7.1 when opcache was enabled</a>. This interfered with XML-RPC requests and some users reported issues managing their sites from WordPress.com and connecting to third-party apps. Downgrading to PHP 7.0 or disabling opcache in PHP 7.1 provided temporary workarounds for many users but this is no longer required as of Jetpack 5.3.</p>\n<p>In January 2017, <a href="https://wptavern.com/jetpack-4-5-expands-monetization-with-wordads-integration" target="_blank">Jetpack added integration with WordAds</a>, WordPress.com’s advertising program. Over the past few years the program has evolved to get better at distinguishing sites with higher quality traffic and allocating earnings accordingly. This correction, along with industry-wide declining ad rates, has given publishers more modest earnings expectations after the first few years of unpredictable payouts. Jetpack 5.3 offers customers on the Premium and Professional plans more control over how ads are displayed.</p>\n<p>This release adds the ability for publishers to display multiple ads and introduces more control options for where they can be placed. Since WordAds pays based on the number of impressions (combined with many other factors) and not the number of clicks, selecting the right combination of placement options is important for success.</p>\n<p><a href="https://i0.wp.com/wptavern.com/wp-content/uploads/2017/09/wordads-jetpack5-3.png?ssl=1"><img /></a></p>\n<p>Other notable changes and improvements include the following:</p>\n<ul>\n<li>Users can preview their sites without leaving WordPress.com</li>\n<li>WordPress.com Toolbar updated to include link to comments</li>\n<li>Omnisearch feature was removed</li>\n<li>Improved performance in the admin by cutting back on unnecessary requests</li>\n<li>VideoPress shortcode includes option to stop video from looping during autoplay</li>\n<li>Fixed compatibility issues with plugins using TinyMCE</li>\n<li>Re-added a filter for Widget Visibility that was accidentally removed</li>\n</ul>\n<p>For a full list of all the changes included in Jetpack 5.3, check out the plugin&#8217;s <a href="https://wordpress.org/plugins/jetpack/#developers" target="_blank">changelog</a> on WordPress.org.</p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 06 Sep 2017 05:46:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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:78:"WPTavern: WordCamp Grand Rapids Attendees Share First Impressions of Gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=74538";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:89:"https://wptavern.com/wordcamp-grand-rapids-attendees-share-first-impressions-of-gutenberg";s: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:2688:"<p><a href="https://i1.wp.com/wptavern.com/wp-content/uploads/2017/09/wordcamp-grand-rapids.png?ssl=1"><img /></a></p>\n<p>While attending <a href="https://wptavern.com/wordcamp-grand-rapids-2017-sells-out-organizers-on-board-for-2018-event" target="_blank">WordCamp Grand Rapids</a> I had the opportunity to interview developers and business owners about their first impressions of the new Gutenberg editor. Many attendees I spoke to had not yet heard of the project but were intrigued and decided to install the plugin on a test site. A few attendees were developers who have already contributed to Gutenberg and are experimenting with extending the editor.</p>\n<p>Those who have tested the beta have varied concerns, depending on how they use WordPress in their professions. Some are waiting to begin testing until the plugin provides a more consistent experience. One of the most common concerns for developers is how the editor will handle meta boxes. Freelancers and agency owners are waiting to see how the new editor will affect their businesses.</p>\n<p>&#8220;How much am I going to have to change what my company does as a business to build websites with this new tool?&#8221; Topher DeRosia asked.</p>\n<p>Agency owner Sara Dunn said she is excited about what Gutenberg will bring to WordPress and undaunted by the prospect of getting clients acquainted to a new interface. She believes the project has a lot of potential to solve some of the most common client frustrations.</p>\n<p>&#8220;I&#8217;m excited about it, because I have a lot of clients who say they can&#8217;t stand WordPress because when they look at the backend and update their pages and posts, it doesn&#8217;t look how it looks on the frontend,&#8221; Dunn said. &#8220;I really think WordPress needs this move to compete in the future, and I&#8217;m excited about where it&#8217;s going.&#8221;</p>\n<p>John James Jacoby, one of the developers who has contributed to Gutenberg and experimented with extending it, said he considers it to be a very ambitious project.</p>\n<p>&#8220;It is probably one of the most important projects that anyone has worked on with WordPress in a number of years, in my opinion,&#8221; Jacoby said. &#8220;My take on it is that everyone has the responsibility to try to influence the direction that it&#8217;s going to take. If we care about the open web and the freedom of how people publish to it, then we should all try to join in and help with its ongoing development and make it as good as it can be if it&#8217;s going to end up as part of WordPress in the coming months.&#8221;</p>\n<p>Check out the interviews below to see how attendees weighed in on Gutenberg.</p>\n<p></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 05 Sep 2017 23:31: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: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:45:"Dev Blog: The Month in WordPress: August 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=4899";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://wordpress.org/news/2017/09/the-month-in-wordpress-august-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:6420:"<p>While there haven’t been any major events or big new developments in the WordPress world this past month, a lot of work has gone into developing a sustainable future for the project. Read on to find out more about this and other interesting news from around the WordPress world in August.</p>\n<hr />\n<h2>The Global WordPress Translation Day Returns</h2>\n<p>On September 30, the WordPress Polyglots team will be holding <a href="https://wptranslationday.org/">the third Global WordPress Translation Day</a>. This is a 24-hour global event dedicated to the translation of the WordPress ecosystem (core, themes, plugins), and is a mix of physical, in-person translation work with online streaming of talks from WordPress translators all over the world.</p>\n<p>Meetup groups will be holding events where community members will come together to translate WordPress. To get involved in this worldwide event, <a href="https://www.meetup.com/pro/wordpress/">join your local meetup group</a> or, if one is not already taking place in your area, organize one for your community.</p>\n<p>You can find out more information <a href="https://wptranslationday.org/global-wordpress-translation-day-3/">on the Translation Day blog</a> and in the #polyglots-events channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a>.</p>\n<h2>WordPress Foundation to Run Open Source Training Worldwide</h2>\n<p>The WordPress Foundation is a non-profit organization that exists to provide educational events and resources for hackathons, support of the open web, and promotion of diversity in the global open source community.</p>\n<p>In an effort to push these goals forward, <a href="http://wordpressfoundation.org/2017/call-for-organizers-introduction-to-open-source/">the Foundation is going to be offering assistance</a> to communities who would like to run local open source training workshops. A number of organizers have applied to be a part of this initiative, and the Foundation will be selecting two communities in the coming weeks.</p>\n<p>Follow <a href="http://wordpressfoundation.org/news/">the WordPress Foundation blog</a> for updates.</p>\n<h2>Next Steps in WordPress Core’s PHP Focus</h2>\n<p>After <a href="https://wordpress.org/news/2017/08/the-month-in-wordpress-july-2017/">last month’s</a> push to focus on WordPress core’s PHP development, a number of new initiatives have been proposed and implemented. The first of these initiatives is a page on WordPress.org that will educate users on the benefits of upgrading PHP. The page and its implementation are still in development, so <a href="https://github.com/WordPress/servehappy">you can follow and contribute on GitHub</a>.</p>\n<p>Along with this, <a href="https://make.wordpress.org/plugins/2017/08/29/minimum-php-version-requirement/">plugin developers are now able to specify</a> the minimum required PHP version for their plugins. This version will then be displayed on the Plugin Directory page, but it will not (yet) prevent users from installing it.</p>\n<p>The next evolution of this is for the minimum PHP requirement to be enforced so that plugins will only work if that requirement is met. You can assist with this implementation by contributing your input or a patch on <a href="https://core.trac.wordpress.org/ticket/40934">the open ticket</a>.</p>\n<p>As always, discussions around the implementation of PHP in WordPress core are done in the #core-php channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a>.</p>\n<h2>New Editor Development Continues</h2>\n<p>For a few months now, the core team has been steadily working on Gutenberg, the new editor for WordPress core. While Gutenberg is still in development and is some time away from being ready, a huge amount of progress has already been made. In fact, <a href="https://make.wordpress.org/core/2017/08/29/whats-new-in-gutenberg-august-29/">v1.0.0 of Gutenberg</a> was released this week.</p>\n<p>The new editor is available as a plugin <a href="https://make.wordpress.org/test/handbook/call-for-testing/gutenberg-testing/">for testing</a> and <a href="https://make.wordpress.org/core/2017/08/11/revised-suggested-roadmap-for-gutenberg-and-customization/">the proposed roadmap</a> is for it to be merged into core in early 2018. You can get involved in the development of Gutenberg by joining the #core-editor channel in the <a href="https://make.wordpress.org/chat/">Making WordPress Slack group</a> and following the <a href="https://make.wordpress.org/core/">WordPress Core development blog</a>.</p>\n<hr />\n<h2>Further reading:</h2>\n<ul>\n<li>On the topic of Gutenberg, <a href="https://ma.tt/2017/08/we-called-it-gutenberg-for-a-reason/">Matt Mullenweg wrote a post</a> to address some of the concerns that the community has expressed about the new editor.</li>\n<li><a href="http://hookrefineandtinker.com/2017/08/jaiwp-an-alternative-project-to-wordcamp-india/">A new movement has started</a> in the Indian WordPress community named JaiWP — the organizers are seeking to unite and motivate the country’s many local communities.</li>\n<li><a href="https://richtabor.com/merlin-wp/">Merlin WP</a> is a new plugin offering theme developers an easy way to onboard their users.</li>\n<li>Ryan McCue posted <a href="https://make.wordpress.org/core/2017/08/23/rest-api-roadmap/">an ambitious roadmap</a> for the future of the WordPress REST API — many contributions from the community will be needed in order to reach these goals.</li>\n<li>Want to know what you can expect in the next major release of WordPress? <a href="https://make.wordpress.org/core/2017/08/11/wordpress-4-9-goals/">Here’s a look</a> at what the core team is planning for v4.9.</li>\n<li>To help combat the difficulties that Trac presents to WordPress Core contributors, Ryan McCue built an alternative platform dubbed <a href="https://github.com/rmccue/not-trac">Not Trac</a>.</li>\n<li><a href="https://make.wordpress.org/cli/2017/08/08/version-1-3-0-released/">v1.3.0 of WP-CLI was released</a> earlier in the month, adding a whole lot of great new features to the useful tool.</li>\n</ul>\n<p><i><span>If you have a story we should consider including in the next &#8220;Month in WordPress&#8221; post, please </span></i><a href="https://make.wordpress.org/community/month-in-wordpress-submissions/"><i><span>submit it here</span></i></a><i><span>.</span></i></p>";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 01 Sep 2017 10:02:16 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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, 03 Oct 2017 15:56:22 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Tue, 03 Oct 2017 15:45:09 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20150108085034";}', 'no');
INSERT INTO `wp_fovr_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(46158, '_transient_themeisle_sdk_feed_items', 'a:5:{i:0;a:3:{s:5:"title";s:74:"10 For-Beginners WordPress Hacks That Will Change the Way You Blog Forever";s:4:"date";i:1507210843;s:4:"link";s:43:"https://themeisle.com/blog/wordpress-hacks/";}i:1;a:3:{s:5:"title";s:51:"3 Ways to Sell Your Services Online Using WordPress";s:4:"date";i:1507112290;s:4:"link";s:63:"https://themeisle.com/blog/sell-your-services-online-wordpress/";}i:2;a:3:{s:5:"title";s:98:"We’ve Researched Popular Fiverr WordPress Customizations and Gigs … See if Fiverr’s Worth It";s:4:"date";i:1506952527;s:4:"link";s:66:"https://themeisle.com/blog/fiverr-wordpress-customizations-how-to/";}i:3;a:3:{s:5:"title";s:50:"How to Make Sure You Pick a Secure WordPress Theme";s:4:"date";i:1506679422;s:4:"link";s:50:"https://themeisle.com/blog/secure-wordpress-theme/";}i:4;a:3:{s:5:"title";s:58:"3 Steps to Take Before and After Changing WordPress Themes";s:4:"date";i:1506527647;s:4:"link";s:53:"https://themeisle.com/blog/changing-wordpress-themes/";}}', 'no');
INSERT INTO `wp_fovr_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES
(46036, '_transient_feed_b9388c83948825c1edaef0d856b7b109', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"\n	\n	\n	\n	\n	\n	\n	\n	\n	\n	\n		\n		\n		\n		\n		\n		\n		\n		\n		\n	";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:29:"Popular — WordPress Plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wordpress.org/plugins";s: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:57:"Plugins extend and expand the functionality of WordPress.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 03 Oct 2017 15:41: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: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-41683";s:7:"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: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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"Contact Form 7";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"https://wordpress.org/plugins/contact-form-7/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/plugins/contact-form-7/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2007 12:43: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wordpress.org/plugins-wp/contact-form-7/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:54:"Just another contact form plugin. Simple but flexible.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Takayuki Miyoshi";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:5872:"<p><!--section=description--></p>\n<p>Contact Form 7 can manage multiple contact forms, plus you can customize the form and the mail contents flexibly with simple markup. The form supports Ajax-powered submitting, CAPTCHA, Akismet spam filtering and so on.</p>\n<h4>Docs &amp; Support</h4>\n<p>You can find <a href="https://contactform7.com/docs/" rel="nofollow">docs</a>, <a href="https://contactform7.com/faq/" rel="nofollow">FAQ</a> and more detailed information about Contact Form 7 on <a href="https://contactform7.com/" rel="nofollow">contactform7.com</a>. If you were unable to find the answer to your question on the FAQ or in any of the documentation, you should check the <a href="https://wordpress.org/support/plugin/contact-form-7/" rel="nofollow">support forum</a> on WordPress.org. If you can&#8217;t locate any topics that pertain to your particular issue, post a new topic for it.</p>\n<h4>Contact Form 7 Needs Your Support</h4>\n<p>It is hard to continue development and support for this free plugin without contributions from users like you. If you enjoy using Contact Form 7 and find it useful, please consider <a href="https://contactform7.com/donate/" rel="nofollow"><strong>making a donation</strong></a>. Your donation will help encourage and support the plugin&#8217;s continued development and better user support.</p>\n<h4>Recommended Plugins</h4>\n<p>The following plugins are recommended for Contact Form 7 users:</p>\n<ul>\n<li><a href="https://wordpress.org/plugins/flamingo/">Flamingo</a> by Takayuki Miyoshi &#8211; With Flamingo, you can save submitted messages via contact forms in the database.</li>\n<li><a href="https://wordpress.org/plugins/postman-smtp/">Postman</a> by<br />\nJason Hendriks &#8211; Postman is a next-generation SMTP Mailer, software that assists in the delivery of email generated by your WordPress site.</li>\n<li><a href="https://wordpress.org/plugins/bogo/">Bogo</a> by Takayuki Miyoshi &#8211; Bogo is a straight-forward multilingual plugin that doesn&#8217;t cause headaches.</li>\n</ul>\n<h4>Translations</h4>\n<p>You can <a href="https://contactform7.com/translating-contact-form-7/" rel="nofollow">translate Contact Form 7</a> on <a href="https://translate.wordpress.org/projects/wp-plugins/contact-form-7" rel="nofollow"><strong>translate.wordpress.org</strong></a>.</p>\n<p><!--section=installation--></p>\n<ol>\n<li>Upload the entire <code>contact-form-7</code> folder to the <code>/wp-content/plugins/</code> directory.</li>\n<li>Activate the plugin through the &#8216;Plugins&#8217; menu in WordPress.</li>\n</ol>\n<p>You will find &#8216;Contact&#8217; menu in your WordPress admin panel.</p>\n<p>For basic usage, you can also have a look at the <a href="https://contactform7.com/" rel="nofollow">plugin web site</a>.</p>\n<p><!--section=faq--></p>\n<p>Do you have questions or issues with Contact Form 7? Use these support channels appropriately.</p>\n<ol>\n<li><a href="https://contactform7.com/docs/" rel="nofollow">Docs</a></li>\n<li><a href="https://contactform7.com/faq/" rel="nofollow">FAQ</a></li>\n<li><a href="https://wordpress.org/support/plugin/contact-form-7/" rel="nofollow">Support Forum</a></li>\n</ol>\n<p><a href="https://contactform7.com/support/" rel="nofollow">Support</a></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<ol>\n<li>Upload the entire <code>contact-form-7</code> folder to the <code>/wp-content/plugins/</code> directory.</li>\n<li>Activate the plugin through the &#8216;Plugins&#8217; menu in WordPress.</li>\n</ol>\n<p>You will find &#8216;Contact&#8217; menu in your WordPress admin panel.</p>\n<p>For basic usage, you can also have a look at the <a href="https://contactform7.com/" rel="nofollow">plugin web site</a>.</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<p>For more information, see <a href="https://contactform7.com/category/releases/" rel="nofollow">Releases</a>.</p>\n<h4>4.9</h4>\n<ul>\n<li>Supports subscribers_only setting</li>\n<li>Changes the default value of WPCF7_VERIFY_NONCE to false</li>\n<li>WPCF7_FormTagsManager::collect_tag_types() supports invert option</li>\n<li>New filter hooks: wpcf7_verify_nonce, wpcf7_subscribers_only_notice, wpcf7_remote_ip_addr, and wpcf7_submission_is_blacklisted</li>\n<li>Fixed: Form-tag&#8217;s tabindex option did not accept 0 or negative integer values</li>\n<li>Shows a validation error when no option in a radio buttons group is checked</li>\n<li>Config validator: Adds a validation rule against the use of deprecated settings (on_sent_ok and on_submit)</li>\n<li>Allows to pass the skip_mail option through the WPCF7_ContactForm::submit() and WPCF7_Submission::get_instance() function parameters.</li>\n<li>Triggers wpcf7beforesubmit custom DOM event. You can manipulate the formData object through an event handler.</li>\n</ul>\n<h4>4.8.1</h4>\n<ul>\n<li>wpcf7.initForm JavaScript function added to isolate form initialization process.</li>\n<li>Fix response message duplication caused by repeated click on submit button.</li>\n<li>Clear $phpmailer-&gt;AltBody to avoid unintended inheritance from previous wp_mail() calls.</li>\n<li>Fix incorrect character count of textarea input.</li>\n<li>Akismet: Exclude the comment_author, comment_author_email, and comment_author_url values from the comment_content value.</li>\n<li>REST API: More reliable approach to build route URLs.</li>\n<li>Include free_text inputs into event.detail.inputs.</li>\n</ul>\n<h4>4.8</h4>\n<ul>\n<li>Stopped using jquery.form.js.</li>\n<li>Added custom REST API endpoints for Ajax form submissions.</li>\n<li>WPCF7_FormTag class implements ArrayAccess interface.</li>\n<li>WPCF7_FormTagsManager::filter() filters form-tags based on features they support.</li>\n<li>New form-tag features: do-not-store, display-block, and display-hidden</li>\n<li>Removed inappropriate content from h1 headings.</li>\n<li>Added the support of size:invisible option to the reCAPTCHA form-tag.</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/contact-form-7/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:30:"\n		\n		\n		\n		\n		\n		\n		\n				\n			";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:9:"Yoast SEO";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"https://wordpress.org/plugins/wordpress-seo/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Oct 2010 20:55: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins-wp/wordpress-seo/";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:103:"Improve your WordPress SEO: Write better content and have a fully optimized WordPress site using&#8230;";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Joost de Valk";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:16721:"<p><!--section=description--></p>\n<p>WordPress out of the box is already technically quite a good platform for SEO. This was true when Joost wrote his original <a href="https://yoast.com/articles/wordpress-seo/" rel="nofollow">WordPress SEO</a> article in 2008 (updated every few months) and it&#8217;s still true today, but that doesn&#8217;t mean you can&#8217;t improve it further! This plugin is written from the ground up by Joost de Valk and his team at <a href="https://yoast.com/" rel="nofollow">Yoast</a> to improve your site&#8217;s SEO on <em>all</em> needed aspects. While this <a href="https://yoast.com/wordpress/plugins/seo/" rel="nofollow">Yoast SEO plugin</a> goes the extra mile to take care of all the technical optimization, more on that below, it first and foremost helps you write better content.  Yoast SEO forces you to choose a focus keyword when you&#8217;re writing your articles, and then makes sure you use that focus keyword everywhere.</p>\n<blockquote>\n<p><strong>Premium Support</strong><br />\n  The Yoast team does not always provide active support for the Yoast SEO plugin on the WordPress.org forums. One-on-one email support is available to people who bought the <a href="https://yoast.com/wordpress/plugins/seo-premium/" rel="nofollow">Premium Yoast SEO plugin</a> only.<br />\n  Note that the Premium SEO plugin has several extra features too, including the option to have multiple focus keywords and a redirect manager, so it might be well worth your investment!</p>\n<p>You should also check out the <a href="https://yoast.com/wordpress/plugins/local-seo/" rel="nofollow">Yoast Local SEO</a>, <a href="https://yoast.com/wordpress/plugins/news-seo/" rel="nofollow">Yoast News SEO</a> and <a href="https://yoast.com/wordpress/plugins/video-seo/" rel="nofollow">Yoast Video SEO</a> extensions to Yoast SEO. These of course come with support too.</p>\n<p><strong>Bug Reports</strong><br />\n  Bug reports for Yoast SEO are <a href="https://github.com/Yoast/wordpress-seo" rel="nofollow">welcomed on GitHub</a>. Please note GitHub is <em>not</em> a support forum, and issues that aren&#8217;t properly qualified as bugs will be closed.</p>\n</blockquote>\n<h4>Write better content with Yoast SEO</h4>\n<p>Using the snippet preview, you can see a rendering of what your post or page will look like in the search results, whether your title is too long or too short, and whether your meta description makes sense in the context of a search result. This way the plugin will help you not only increase rankings but also increase the click through rate for organic search results.</p>\n<h4>Page Analysis</h4>\n<p>The Yoast SEO plugins <a href="https://yoast.com/content-seo-wordpress-linkdex/" rel="nofollow">Page Analysis</a> functionality checks simple things you&#8217;re bound to forget. It checks, for instance, if you have images in your post and whether they have an alt tag containing the focus keyword for that post. It also checks whether your posts are long enough, whether you&#8217;ve written a meta description and if that meta description contains your focus keyword, if you&#8217;ve used any subheadings within your post, etc. etc.</p>\n<p>The plugin also allows you to write meta titles and descriptions for all your category, tag and custom taxonomy archives, giving you the option to further optimize those pages.</p>\n<p>Combined, this plugin makes sure that your content is the type of content search engines will love!</p>\n<h4>Technical WordPress Search Engine Optimization</h4>\n<p>While out of the box WordPress is pretty good for SEO, it needs some tweaks here and there. This Yoast SEO plugin guides you through some of the settings needed, for instance by reminding you to enable pretty permalinks. But it also goes beyond that, by automatically optimizing and inserting the meta tags and link elements that Google and other search engines like so much:</p>\n<h4>Meta &amp; Link Elements</h4>\n<p>With the Yoast SEO plugin you can control which pages Google shows in its search results and which pages it doesn&#8217;t show. By default, it will tell search engines to index all of your pages, including category and tag archives, but to only show the first pages in the search results. It&#8217;s not very useful for a user to end up on the third page of your &#8220;personal&#8221; category, right?</p>\n<p>WordPress itself only shows canonical link elements on single pages, but Yoast SEO makes it output canonical link elements everywhere. Google has recently announced they would also use <code>rel="next"</code> and <code>rel="prev"</code> link elements in the <code>head</code> section of your paginated archives. This plugin adds those automatically. See <a href="https://yoast.com/rel-next-prev-paginated-archives/" rel="nofollow">this post</a> for more info.</p>\n<h4>XML Sitemaps</h4>\n<p>The Yoast SEO plugin has the most advanced XML Sitemaps functionality in any WordPress plugin. Once you check the box, it automatically creates XML sitemaps and notifies Google &amp; Bing of the sitemaps&#8217; existence. These XML sitemaps include the images in your posts &amp; pages too, so that your images may be found better in the search engines too.</p>\n<p>These XML Sitemaps will even work on large sites, because of how they&#8217;re created, using one index sitemap that links to sub-sitemaps for each 1,000 posts. They will also work with custom post types and custom taxonomies automatically, while giving you the option to remove those from the XML sitemap should you wish to.</p>\n<p>Because of using <a href="https://yoast.com/xsl-stylesheet-xml-sitemap/" rel="nofollow">XSL stylesheets for these XML Sitemaps</a>, the XML sitemaps are easily readable for the human eye too, so you can spot things that shouldn&#8217;t be in there.</p>\n<h4>RSS Optimization</h4>\n<p>Are you being outranked by scrapers? Instead of cursing at them, use them to your advantage! By automatically adding a link to your RSS feed pointing back to the original article, you&#8217;re telling the search engine where they should be looking for the original. This way, the Yoast SEO plugin increases your own chance of ranking for your chosen keywords and gets rid of scrapers in one go!</p>\n<h4>Breadcrumbs</h4>\n<p>If your theme is compatible, and themes based on for instance Genesis or by WooThemes often are, you can use the built-in Breadcrumbs functionality. This allows you to create an easy navigation that is great for both users and search engines, and will support the search engines in understanding the structure of your site.</p>\n<p>Making your theme compatible isn&#8217;t hard either, check <a href="https://kb.yoast.com/kb/implement-wordpress-seo-breadcrumbs/" rel="nofollow">these instructions</a>.</p>\n<h4>Edit your .htaccess and robots.txt file</h4>\n<p>Using the built-in file editor, you can edit your WordPress blog&#8217;s <code>.htaccess</code> and <code>robots.txt</code> file, giving you direct access to the two most powerful files, from an SEO perspective, in your WordPress install.</p>\n<h4>Social Integration</h4>\n<p>SEO and Social Media are heavily intertwined. That&#8217;s why this plugin also comes with a Facebook OpenGraph implementation and will soon also support Google+ sharing tags.</p>\n<h4>Multi-Site Compatible</h4>\n<p>The Yoast SEO plugin, unlike some others, is fully Multi-Site compatible. The XML Sitemaps work fine in all setups and you even have the option, in the Network settings, to copy the settings from one blog to another, or make blogs default to the settings for a specific blog.</p>\n<h4>Import &amp; Export functionality</h4>\n<p>If you have multiple blogs, setting up plugins like this one on all of them might seem like a daunting task. Except that it&#8217;s not, because what you can do is simple: you set up the plugin once. You then export your settings and simply import them on all your other sites. It&#8217;s that simple!</p>\n<h4>Import functionality for other WordPress SEO plugins</h4>\n<p>If you&#8217;ve used All In One SEO Pack or HeadSpace2 before using this plugin, you might want to import all your old titles and descriptions. You can do that easily using the built-in import functionality. There&#8217;s also import functionality for some of the older Yoast plugins, like Robots Meta and RSS footer.</p>\n<p>Should you have a need to import from another SEO plugin to Yoast SEO, or from a theme like Genesis or Thesis, you can use the <a href="https://wordpress.org/extend/plugins/seo-data-transporter/" rel="nofollow">SEO Data Transporter</a> plugin, which will easily convert your SEO meta data from and to a whole set of plugins like Platinum SEO, SEO Ultimate, Greg&#8217;s High Performance SEO, and themes like Headway, Hybrid, WooFramework, Catalyst etc.</p>\n<p>Read <a href="https://yoast.com/all-in-one-seo-pack-migration/" rel="nofollow">this migration guide</a> if you still have questions about migrating from another SEO plugin to Yoast SEO.</p>\n<h4>Yoast SEO Plugin in your Language!</h4>\n<p>Currently a huge translation project is underway, translating Yoast SEO in as much as 24 languages. So far, the translations for French and Dutch are complete, but we still need help on a lot of other languages, so if you&#8217;re good at translating, please join us at <a href="http://translate.yoast.com" rel="nofollow">translate.yoast.com</a>.</p>\n<h4>News SEO</h4>\n<p>Be sure to also check out the premium <a href="https://yoast.com/wordpress/plugins/news-seo/" rel="nofollow">News SEO module</a> if you need Google News Sitemaps. It tightly integrates with Yoast SEO to give you the combined power of News Sitemaps and full Search Engine Optimization.</p>\n<h4>Further Reading</h4>\n<p>For more info, check out the following articles:</p>\n<ul>\n<li>The <a href="https://kb.yoast.com/kb/category/yoast-seo/" rel="nofollow">Yoast SEO Knowledgebase</a>.</li>\n<li><a href="https://yoast.com/articles/wordpress-seo/" rel="nofollow">WordPress SEO &#8211; The definitive Guide by Yoast</a>.</li>\n<li>Once you have great SEO, you&#8217;ll need the <a href="https://yoast.com/articles/wordpress-hosting/" rel="nofollow">best WordPress Hosting</a>.</li>\n<li>The <a href="https://yoast.com/wordpress/plugins/seo/" rel="nofollow">Yoast SEO Plugin</a> official homepage.</li>\n<li>Other <a href="https://yoast.com/wordpress/plugins/" rel="nofollow">WordPress Plugins</a> by the same team.</li>\n<li>Follow Yoast on <a href="https://facebook.com/yoast" rel="nofollow">Facebook</a> &amp; <a href="http://twitter.com/yoast" rel="nofollow">Twitter</a>.</li>\n</ul>\n<h3>From within WordPress</h3>\n<ol>\n<li>Visit &#8216;Plugins &gt; Add New&#8217;</li>\n<li>Search for &#8216;Yoast SEO&#8217;</li>\n<li>Activate Yoast SEO from your Plugins page.</li>\n<li>Go to &#8220;after activation&#8221; below.</li>\n</ol>\n<h3>Manually</h3>\n<ol>\n<li>Upload the <code>wordpress-seo</code> folder to the <code>/wp-content/plugins/</code> directory</li>\n<li>Activate the Yoast SEO plugin through the &#8216;Plugins&#8217; menu in WordPress</li>\n<li>Go to &#8220;after activation&#8221; below.</li>\n</ol>\n<h3>After activation</h3>\n<ol>\n<li>You should see (a notice to start) the Yoast SEO configuration wizard.</li>\n<li>Go through the configuration wizard and set up the plugin for your site.</li>\n<li>You&#8217;re done!</li>\n</ol>\n<p><!--section=faq--></p>\n<p>You&#8217;ll find answers to many of your questions on <a href="https://kb.yoast.com/kb/category/yoast-seo/" rel="nofollow">kb.yoast.com</a>.</p>\n<p><!--section=changelog--></p>\n<h4>5.5.1</h4>\n<p>Release Date: September 28th, 2017</p>\n<ul>\n<li>\n<p>Bugfixes</p>\n<ul>\n<li>Fixes Snippet preview error when Yoast metabox has been removed.</li>\n</ul>\n</li>\n<li>\n<p>Changes</p>\n<ul>\n<li>Change Yoast Blog feed to new endpoint.</li>\n</ul>\n</li>\n</ul>\n<h4>5.5.0</h4>\n<p>Release Date: September 26th, 2017</p>\n<ul>\n<li>\n<p>Enhancements</p>\n<ul>\n<li>Updated the Dashboard Widget with a new design.</li>\n<li>Added additional explanations to the Configuration wizard.</li>\n<li>Added <code>contentinfo</code> landmark for assistive technologies to the Configuration wizard page.</li>\n<li>Introduces <code>wpseo_manager</code> and <code>wpseo_editor</code> roles.</li>\n<li>Introduces <code>wpseo_manage_options</code> capability to control which users have access to all SEO settings.</li>\n<li>Introduces <code>wpseo_edit_advanced_metadata</code> capability to control which users have access to the advanced SEO settings.</li>\n</ul>\n</li>\n<li>\n<p>Bugfixes</p>\n<ul>\n<li>Fixed a bug where certain options (<code>site_type</code>, <code>environment_type</code> and <code>has_multiple_authors</code>) would be reset to their default value whenever one of the feature toggles were changed.</li>\n<li>Ensured that <code>has_multiple_authors</code> gets validated.</li>\n</ul>\n</li>\n</ul>\n<p>= 5.4.2</p>\n<p>Release Date: September 21st, 2017</p>\n<ul>\n<li>Bugfixes\n<ul>\n<li>Replace unsupported query <code>prepare</code> placeholder <code>%1$d</code> with <code>%d</code> to fix broken queries. Fixes compatibility issue with WordPress 4.8.2.</li>\n</ul>\n</li>\n</ul>\n<p>= 5.4.1</p>\n<p>Release Date: September 20th, 2017</p>\n<ul>\n<li>Bugfixes\n<ul>\n<li>Replace unsupported query <code>prepare</code> placeholder <code>%1$s</code> with <code>%d</code> to fix broken queries. Fixes compatibility issue with WordPress 4.8.2.</li>\n</ul>\n</li>\n</ul>\n<h4>5.4.0</h4>\n<p>Release Date: September 6th, 2017</p>\n<ul>\n<li>\n<p>Enhancements</p>\n<ul>\n<li>Added a hook to disabled the twitter card. (Props: @petenelson)</li>\n</ul>\n</li>\n<li>\n<p>Performance</p>\n<ul>\n<li>Replaced the use of <code>get_posts</code> and <code>get_children</code> by <code>WP_Query</code>.</li>\n</ul>\n</li>\n<li>\n<p>Bugfixes</p>\n<ul>\n<li>Archive pages are excluded from the sitemap based on the noindex setting. (Props: @stodorovic)</li>\n<li>Prevent the throwing of an error when <code>wpseoPostScraperL10n</code> is not defined.</li>\n<li>Escapes all input when generating links for the RSS feed.</li>\n<li>Apply the <code>wp_get_attachment_url</code> filter to Sitemap images.</li>\n</ul>\n</li>\n</ul>\n<h4>5.3.3</h4>\n<p>Release Date: August 28th, 2017</p>\n<ul>\n<li>Bugfixes\n<ul>\n<li>Fixes a bug where table listings were not giving expected content, props <a href="https://github.com/kjohnson" rel="nofollow">Kyle B. Johnson</a>.</li>\n</ul>\n</li>\n</ul>\n<h4>5.3.2</h4>\n<p>Release Date: August 23rd, 2017</p>\n<ul>\n<li>Bugfixes\n<ul>\n<li>Fixes a bug where an invalid license notification could be shown in certain situations.</li>\n</ul>\n</li>\n</ul>\n<h4>5.3.1</h4>\n<p>Release Date: August 22nd, 2017</p>\n<ul>\n<li>Bugfixes\n<ul>\n<li>Fixes a bug where &#8220;mark as fixed&#8221; on the search console page didn&#8217;t work.</li>\n<li>Fixes a bug where the configuration wizard JavaScript file was too large.</li>\n</ul>\n</li>\n</ul>\n<h4>5.3.0</h4>\n<p>Release Date: August 22nd, 2017</p>\n<ul>\n<li>\n<p>Enhancements</p>\n<ul>\n<li>Adds missing I18n function call to make a string translatable</li>\n<li>Adds XML schema for image sitemap, props: <a href="https://github.com/stodorovic" rel="nofollow">stodorovic</a></li>\n<li>Adds schema.org meta-data on every page, instead of only on the homepage</li>\n<li>Adds the possibility to filter posts by readability score.</li>\n<li>Exposes tinyMCEHelper as window.YoastSEO.wp._tinyMCEHelper in JavaScript</li>\n<li>Exposes the ReplaceVar class in YoastReplaceVarPlugin as window.YoastReplaceVarPlugin.ReplaceVar in JavaScript</li>\n</ul>\n</li>\n<li>\n<p>Bugfixes</p>\n<ul>\n<li>Adds sanitization for the Twitter Image meta field</li>\n<li>Fixes use of <code>register_meta</code> for usage in WordPress 4.6 and higher</li>\n<li>Initialize the providers on hook <code>after_theme_setup</code> to make sure custom providers are added properly, props: <a href="https://github.com/stodorovic" rel="nofollow">stodorovic</a></li>\n<li>Changes the label of the &#8220;Bad&#8221; score to &#8220;Needs improvement&#8221; while filtering on SEO or readability scores.</li>\n</ul>\n</li>\n</ul>\n<h4>5.2.0</h4>\n<p>Release Date: August 8th, 2017</p>\n<ul>\n<li>\n<p>Enhancements</p>\n<ul>\n<li>Added wpseo_pre_adjacent_rel_links filter to bypass built-in rel prev/next functionality.</li>\n<li>Introduces classes to allow collecting data in the Premium plugin.</li>\n<li>Renamed OnPage.org to Ryte.</li>\n<li>Allow WordPress WHIP messages to be dismissed for a period of 4 weeks.</li>\n<li>Adds a filter for word combinations that consist of a single one-character word.</li>\n<li>Adds aria-current to the onboarding wizard active step.</li>\n</ul>\n</li>\n<li>\n<p>Bugfixes</p>\n<ul>\n<li>Removes JQMIGRATE JavaScript warnings.</li>\n</ul>\n</li>\n</ul>\n<h4>Earlier versions</h4>\n<p>For the changelog of earlier versions, please refer to the separate changelog.txt file.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:7:"Akismet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"https://wordpress.org/plugins/akismet/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/akismet/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Oct 2005 08:57: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/plugins-wp/akismet/";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:103:"Akismet checks your comments and contact form submissions against our global database of spam to&#8230;";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:19828:"<p><!--section=description--></p>\n<p>Akismet checks your comments and contact form submissions against our global database of spam to prevent your site from publishing malicious content. You can review the comment spam it catches on your blog&#8217;s &#8220;Comments&#8221; admin screen.</p>\n<p>Major features in Akismet include:</p>\n<ul>\n<li>Automatically checks all comments and filters out the ones that look like spam.</li>\n<li>Each comment has a status history, so you can easily see which comments were caught or cleared by Akismet and which were spammed or unspammed by a moderator.</li>\n<li>URLs are shown in the comment body to reveal hidden or misleading links.</li>\n<li>Moderators can see the number of approved comments for each user.</li>\n<li>A discard feature that outright blocks the worst spam, saving you disk space and speeding up your site.</li>\n</ul>\n<p>PS: You&#8217;ll need an <a href="https://akismet.com/get/" rel="nofollow">Akismet.com API key</a> to use it.  Keys are free for personal blogs; paid subscriptions are available for businesses and commercial sites.</p>\n<p><!--section=installation--></p>\n<p>Upload the Akismet plugin to your blog, Activate it, then enter your <a href="https://akismet.com/get/" rel="nofollow">Akismet.com API key</a>.</p>\n<p>1, 2, 3: You&#8217;re done!</p>\n<p><!--section=changelog--></p>\n<h4>4.0</h4>\n<p><em>Release Date &#8211; 19 September 2017</em></p>\n<ul>\n<li>Added REST API endpoints for configuring Akismet and retrieving stats.</li>\n<li>Increased the minimum supported WordPress version to 4.0.</li>\n<li>Added compatibility with comments submitted via the REST API.</li>\n<li>Improved the progress indicator on the &#8220;Check for Spam&#8221; button.</li>\n</ul>\n<h4>3.3.4</h4>\n<p><em>Release Date &#8211; 3 August 2017</em></p>\n<ul>\n<li>Disabled Akismet&#8217;s debug log output by default unless AKISMET_DEBUG is defined.</li>\n<li>URL previews now begin preloading when the mouse moves near them in the comments section of wp-admin.</li>\n<li>When a comment is caught by the Comment Blacklist, Akismet will always allow it to stay in the trash even if it is spam as well.</li>\n<li>Fixed a bug that was preventing an error from being shown when a site can&#8217;t reach Akismet&#8217;s servers.</li>\n</ul>\n<h4>3.3.3</h4>\n<p><em>Release Date &#8211; 13 July 2017</em></p>\n<ul>\n<li>Reduced amount of bandwidth used by the URL Preview feature.</li>\n<li>Improved the admin UI when the API key is manually pre-defined for the site.</li>\n<li>Removed a workaround for WordPress installations older than 3.3 that will improve Akismet&#8217;s compatibility with other plugins.</li>\n<li>The number of spam blocked that is displayed on the WordPress dashboard will now be more accurate and updated more frequently.</li>\n<li>Fixed a bug in the Akismet widget that could cause PHP warnings.</li>\n</ul>\n<h4>3.3.2</h4>\n<p><em>Release Date &#8211; 10 May 2017</em></p>\n<ul>\n<li>Fixed a bug causing JavaScript errors in some browsers.</li>\n</ul>\n<h4>3.3.1</h4>\n<p><em>Release Date &#8211; 2 May 2017</em></p>\n<ul>\n<li>Improve performance by only requesting the akismet_comment_nonce option when absolutely necessary.</li>\n<li>Fixed two bugs that could cause PHP warnings.</li>\n<li>Fixed a bug that was preventing the &#8220;Remove author URL&#8221; feature from working after a comment was edited using &#8220;Quick Edit.&#8221;</li>\n<li>Fixed a bug that was preventing the URL preview feature from working after a comment was edited using &#8220;Quick Edit.&#8221;</li>\n</ul>\n<h4>3.3</h4>\n<p><em>Release Date &#8211; 23 February 2017</em></p>\n<ul>\n<li>Updated the Akismet admin pages with a new clean design.</li>\n<li>Fixed bugs preventing the <code>akismet_add_comment_nonce</code> and <code>akismet_update_alert</code> wrapper functions from working properly.</li>\n<li>Fixed bug preventing the loading indicator from appearing when re-checking all comments for spam.</li>\n<li>Added a progress indicator to the &#8220;Check for Spam&#8221; button.</li>\n<li>Added a success message after manually rechecking the Pending queue for spam.</li>\n</ul>\n<h4>3.2</h4>\n<p><em>Release Date &#8211; 6 September 2016</em></p>\n<ul>\n<li>Added a WP-CLI module. You can now check comments and recheck the moderation queue from the command line.</li>\n<li>Stopped using the deprecated jQuery function <code>.live()</code>.</li>\n<li>Fixed a bug in <code>remove_comment_author_url()</code> and <code>add_comment_author_url()</code> that could generate PHP notices.</li>\n<li>Fixed a bug that could cause an infinite loop for sites with very very very large comment IDs.</li>\n<li>Fixed a bug that could cause the Akismet widget title to be blank.</li>\n</ul>\n<h4>3.1.11</h4>\n<p><em>Release Date &#8211; 12 May 2016</em></p>\n<ul>\n<li>Fixed a bug that could cause the &#8220;Check for Spam&#8221; button to skip some comments.</li>\n<li>Fixed a bug that could prevent some spam submissions from being sent to Akismet.</li>\n<li>Updated all links to use https:// when possible.</li>\n<li>Disabled Akismet debug logging unless WP_DEBUG and WP_DEBUG_LOG are both enabled.</li>\n</ul>\n<h4>3.1.10</h4>\n<p><em>Release Date &#8211; 1 April 2016</em></p>\n<ul>\n<li>Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.</li>\n<li>Fixed a bug that could have resulted in comments that were caught by the core WordPress comment blacklist not to have a corresponding History entry.</li>\n<li>Fixed a bug that could have caused avoidable PHP warnings in the error log.</li>\n</ul>\n<h4>3.1.9</h4>\n<p><em>Release Date &#8211; 28 March 2016</em></p>\n<ul>\n<li>Add compatibility with Jetpack so that Jetpack can automatically configure Akismet settings when appropriate.</li>\n<li>Fixed a bug preventing some comment data from being sent to Akismet.</li>\n</ul>\n<h4>3.1.8</h4>\n<p><em>Release Date &#8211; 4 March 2016</em></p>\n<ul>\n<li>Fixed a bug preventing Akismet from being used with some plugins that rewrite admin URLs.</li>\n<li>Reduced the amount of bandwidth used on Akismet API calls</li>\n<li>Reduced the amount of space Akismet uses in the database</li>\n<li>Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.</li>\n</ul>\n<h4>3.1.7</h4>\n<p><em>Release Date &#8211; 4 January 2016</em></p>\n<ul>\n<li>Added documentation for the &#8216;akismet_comment_nonce&#8217; filter.</li>\n<li>The post-install activation button is now accessible to screen readers and keyboard-only users.</li>\n<li>Fixed a bug that was preventing the &#8220;Remove author URL&#8221; feature from working in WordPress 4.4</li>\n</ul>\n<h4>3.1.6</h4>\n<p><em>Release Date &#8211; 14 December 2015</em></p>\n<ul>\n<li>Improve the notices shown after activating Akismet.</li>\n<li>Update some strings to allow for the proper plural forms in all languages.</li>\n</ul>\n<h4>3.1.5</h4>\n<p><em>Release Date &#8211; 13 October 2015</em></p>\n<ul>\n<li>Closes a potential XSS vulnerability.</li>\n</ul>\n<h4>3.1.4</h4>\n<p><em>Release Date &#8211; 24 September 2015</em></p>\n<ul>\n<li>Fixed a bug that was preventing some users from automatically connecting using Jetpack if they didn&#8217;t have a current Akismet subscription.</li>\n<li>Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.</li>\n<li>Error messages and instructions have been simplified to be more understandable.</li>\n<li>Link previews are enabled for all links inside comments, not just the author&#8217;s website link.</li>\n</ul>\n<h4>3.1.3</h4>\n<p><em>Release Date &#8211; 6 July 2015</em></p>\n<ul>\n<li>Notify users when their account status changes after previously being successfully set up. This should help any users who are seeing blank Akismet settings screens.</li>\n</ul>\n<h4>3.1.2</h4>\n<p><em>Release Date &#8211; 7 June 2015</em></p>\n<ul>\n<li>Reduced the amount of space Akismet uses in the commentmeta table.</li>\n<li>Fixed a bug where some comments with quotes in the author name weren&#8217;t getting history entries</li>\n<li>Pre-emptive security improvements to ensure that the Akismet plugin can&#8217;t be used by attackers to compromise a WordPress installation.</li>\n<li>Better UI for the key entry field: allow whitespace to be included at the beginning or end of the key and strip it out automatically when the form is submitted.</li>\n<li>When deactivating the plugin, notify the Akismet API so the site can be marked as inactive.</li>\n<li>Clearer error messages.</li>\n</ul>\n<h4>3.1.1</h4>\n<p><em>Release Date &#8211; 17th March, 2015</em></p>\n<ul>\n<li>Improvements to the &#8220;Remove comment author URL&#8221; JavaScript</li>\n<li>Include the pingback pre-check from the 2.6 branch.</li>\n</ul>\n<h4>3.1</h4>\n<p><em>Release Date &#8211; 11th March, 2015</em></p>\n<ul>\n<li>Use HTTPS by default for all requests to Akismet.</li>\n<li>Fix for a situation where Akismet might strip HTML from a comment.</li>\n</ul>\n<h4>3.0.4</h4>\n<p><em>Release Date &#8211; 11th December, 2014</em></p>\n<ul>\n<li>Fix to make .htaccess compatible with Apache 2.4.</li>\n<li>Fix to allow removal of https author URLs.</li>\n<li>Fix to avoid stripping part of the author URL when removing and re-adding.</li>\n<li>Removed the &#8220;Check for Spam&#8221; button from the &#8220;Trash&#8221; and &#8220;Approved&#8221; queues, where it would have no effect.</li>\n<li>Allow automatic API key configuration when Jetpack is installed and connected to a WordPress.com account</li>\n</ul>\n<h4>3.0.3</h4>\n<p><em>Release Date &#8211; 3rd November, 2014</em></p>\n<ul>\n<li>Fix for sending the wrong data to delete_comment action that could have prevented old spam comments from being deleted.</li>\n<li>Added a filter to disable logging of Akismet debugging information.</li>\n<li>Added a filter for the maximum comment age when deleting old spam comments.</li>\n<li>Added a filter for the number per batch when deleting old spam comments.</li>\n<li>Removed the &#8220;Check for Spam&#8221; button from the Spam folder.</li>\n</ul>\n<h4>3.0.2</h4>\n<p><em>Release Date &#8211; 18th August, 2014</em></p>\n<ul>\n<li>Performance improvements.</li>\n<li>Fixed a bug that could truncate the comment data being sent to Akismet for checking.</li>\n</ul>\n<h4>3.0.1</h4>\n<p><em>Release Date &#8211; 9th July, 2014</em></p>\n<ul>\n<li>Removed dependency on PHP&#8217;s fsockopen function</li>\n<li>Fix spam/ham reports to work when reported outside of the WP dashboard, e.g., from Notifications or the WP app</li>\n<li>Remove jQuery dependency for comment form JavaScript</li>\n<li>Remove unnecessary data from some Akismet comment meta</li>\n<li>Suspended keys will now result in all comments being put in moderation, not spam.</li>\n</ul>\n<h4>3.0.0</h4>\n<p><em>Release Date &#8211; 15th April, 2014</em></p>\n<ul>\n<li>Move Akismet to Settings menu</li>\n<li>Drop Akismet Stats menu</li>\n<li>Add stats snapshot to Akismet settings</li>\n<li>Add Akismet subscription details and status to Akismet settings</li>\n<li>Add contextual help for each page</li>\n<li>Improve Akismet setup to use Jetpack to automate plugin setup</li>\n<li>Fix &#8220;Check for Spam&#8221; to use AJAX to avoid page timing out</li>\n<li>Fix Akismet settings page to be responsive</li>\n<li>Drop legacy code</li>\n<li>Tidy up CSS and Javascript</li>\n<li>Replace the old discard setting with a new &#8220;discard pervasive spam&#8221; feature.</li>\n</ul>\n<h4>2.6.0</h4>\n<p><em>Release Date &#8211; 18th March, 2014</em></p>\n<ul>\n<li>Add ajax paging to the check for spam button to handle large volumes of comments</li>\n<li>Optimize javascript and add localization support </li>\n<li>Fix bug in link to spam comments from right now dashboard widget</li>\n<li>Fix bug with deleting old comments to avoid timeouts dealing with large volumes of comments</li>\n<li>Include X-Pingback-Forwarded-For header in outbound WordPress pingback verifications</li>\n<li>Add pre-check for pingbacks, to stop spam before an outbound verification request is made</li>\n</ul>\n<h4>2.5.9</h4>\n<p><em>Release Date &#8211; 1st August, 2013</em></p>\n<ul>\n<li>Update &#8216;Already have a key&#8217; link to redirect page rather than depend on javascript</li>\n<li>Fix some non-translatable strings to be translatable</li>\n<li>Update Activation banner in plugins page to redirect user to Akismet config page</li>\n</ul>\n<h4>2.5.8</h4>\n<p><em>Release Date &#8211; 20th January, 2013</em></p>\n<ul>\n<li>Simplify the activation process for new users</li>\n<li>Remove the reporter_ip parameter</li>\n<li>Minor preventative security improvements</li>\n</ul>\n<h4>2.5.7</h4>\n<p><em>Release Date &#8211; 13th December, 2012</em></p>\n<ul>\n<li>FireFox Stats iframe preview bug</li>\n<li>Fix mshots preview when using https</li>\n<li>Add .htaccess to block direct access to files</li>\n<li>Prevent some PHP notices</li>\n<li>Fix Check For Spam return location when referrer is empty</li>\n<li>Fix Settings links for network admins</li>\n<li>Fix prepare() warnings in WP 3.5</li>\n</ul>\n<h4>2.5.6</h4>\n<p><em>Release Date &#8211; 26th April, 2012</em></p>\n<ul>\n<li>Prevent retry scheduling problems on sites where wp_cron is misbehaving</li>\n<li>Preload mshot previews</li>\n<li>Modernize the widget code</li>\n<li>Fix a bug where comments were not held for moderation during an error condition</li>\n<li>Improve the UX and display when comments are temporarily held due to an error</li>\n<li>Make the Check For Spam button force a retry when comments are held due to an error</li>\n<li>Handle errors caused by an invalid key</li>\n<li>Don&#8217;t retry comments that are too old</li>\n<li>Improve error messages when verifying an API key</li>\n</ul>\n<h4>2.5.5</h4>\n<p><em>Release Date &#8211; 11th January, 2012</em></p>\n<ul>\n<li>Add nonce check for comment author URL remove action</li>\n<li>Fix the settings link</li>\n</ul>\n<h4>2.5.4</h4>\n<p><em>Release Date &#8211; 5th January, 2012</em></p>\n<ul>\n<li>Limit Akismet CSS and Javascript loading in wp-admin to just the pages that need it</li>\n<li>Added author URL quick removal functionality</li>\n<li>Added mShot preview on Author URL hover</li>\n<li>Added empty index.php to prevent directory listing</li>\n<li>Move wp-admin menu items under Jetpack, if it is installed</li>\n<li>Purge old Akismet comment meta data, default of 15 days</li>\n</ul>\n<h4>2.5.3</h4>\n<p><em>Release Date &#8211; 8th Febuary, 2011</em></p>\n<ul>\n<li>Specify the license is GPL v2 or later</li>\n<li>Fix a bug that could result in orphaned commentmeta entries</li>\n<li>Include hotfix for WordPress 3.0.5 filter issue</li>\n</ul>\n<h4>2.5.2</h4>\n<p><em>Release Date &#8211; 14th January, 2011</em></p>\n<ul>\n<li>Properly format the comment count for author counts</li>\n<li>Look for super admins on multisite installs when looking up user roles</li>\n<li>Increase the HTTP request timeout</li>\n<li>Removed padding for author approved count</li>\n<li>Fix typo in function name</li>\n<li>Set Akismet stats iframe height to fixed 2500px.  Better to have one tall scroll bar than two side by side.</li>\n</ul>\n<h4>2.5.1</h4>\n<p><em>Release Date &#8211; 17th December, 2010</em></p>\n<ul>\n<li>Fix a bug that caused the &#8220;Auto delete&#8221; option to fail to discard comments correctly</li>\n<li>Remove the comment nonce form field from the &#8216;Akismet Configuration&#8217; page in favor of using a filter, akismet_comment_nonce</li>\n<li>Fixed padding bug in &#8220;author&#8221; column of posts screen</li>\n<li>Added margin-top to &#8220;cleared by &#8230;&#8221; badges on dashboard</li>\n<li>Fix possible error when calling akismet_cron_recheck()</li>\n<li>Fix more PHP warnings</li>\n<li>Clean up XHTML warnings for comment nonce</li>\n<li>Fix for possible condition where scheduled comment re-checks could get stuck</li>\n<li>Clean up the comment meta details after deleting a comment</li>\n<li>Only show the status badge if the comment status has been changed by someone/something other than Akismet</li>\n<li>Show a &#8216;History&#8217; link in the row-actions</li>\n<li>Translation fixes</li>\n<li>Reduced font-size on author name</li>\n<li>Moved &#8220;flagged by&#8230;&#8221; notification to top right corner of comment container and removed heavy styling</li>\n<li>Hid &#8220;flagged by&#8230;&#8221; notification while on dashboard</li>\n</ul>\n<h4>2.5.0</h4>\n<p><em>Release Date &#8211; 7th December, 2010</em></p>\n<ul>\n<li>Track comment actions under &#8216;Akismet Status&#8217; on the edit comment screen</li>\n<li>Fix a few remaining deprecated function calls ( props Mike Glendinning ) </li>\n<li>Use HTTPS for the stats IFRAME when wp-admin is using HTTPS</li>\n<li>Use the WordPress HTTP class if available</li>\n<li>Move the admin UI code to a separate file, only loaded when needed</li>\n<li>Add cron retry feature, to replace the old connectivity check</li>\n<li>Display Akismet status badge beside each comment</li>\n<li>Record history for each comment, and display it on the edit page</li>\n<li>Record the complete comment as originally submitted in comment_meta, to use when reporting spam and ham</li>\n<li>Highlight links in comment content</li>\n<li>New option, &#8220;Show the number of comments you&#8217;ve approved beside each comment author.&#8221;</li>\n<li>New option, &#8220;Use a nonce on the comment form.&#8221;</li>\n</ul>\n<h4>2.4.0</h4>\n<p><em>Release Date &#8211; 23rd August, 2010</em></p>\n<ul>\n<li>Spell out that the license is GPLv2</li>\n<li>Fix PHP warnings</li>\n<li>Fix WordPress deprecated function calls</li>\n<li>Fire the delete_comment action when deleting comments</li>\n<li>Move code specific for older WP versions to legacy.php</li>\n<li>General code clean up</li>\n</ul>\n<h4>2.3.0</h4>\n<p><em>Release Date &#8211; 5th June, 2010</em></p>\n<ul>\n<li>Fix &#8220;Are you sure&#8221; nonce message on config screen in WPMU</li>\n<li>Fix XHTML compliance issue in sidebar widget</li>\n<li>Change author link; remove some old references to WordPress.com accounts</li>\n<li>Localize the widget title (core ticket #13879)</li>\n</ul>\n<h4>2.2.9</h4>\n<p><em>Release Date &#8211; 2nd June, 2010</em></p>\n<ul>\n<li>Eliminate a potential conflict with some plugins that may cause spurious reports</li>\n</ul>\n<h4>2.2.8</h4>\n<p><em>Release Date &#8211; 27th May, 2010</em></p>\n<ul>\n<li>Fix bug in initial comment check for ipv6 addresses</li>\n<li>Report comments as ham when they are moved from spam to moderation</li>\n<li>Report comments as ham when clicking undo after spam</li>\n<li>Use transition_comment_status action when available instead of older actions for spam/ham submissions</li>\n<li>Better diagnostic messages when PHP network functions are unavailable</li>\n<li>Better handling of comments by logged-in users</li>\n</ul>\n<h4>2.2.7</h4>\n<p><em>Release Date &#8211; 17th December, 2009</em></p>\n<ul>\n<li>Add a new AKISMET_VERSION constant</li>\n<li>Reduce the possibility of over-counting spam when another spam filter plugin is in use</li>\n<li>Disable the connectivity check when the API key is hard-coded for WPMU</li>\n</ul>\n<h4>2.2.6</h4>\n<p><em>Release Date &#8211; 20th July, 2009</em></p>\n<ul>\n<li>Fix a global warning introduced in 2.2.5</li>\n<li>Add changelog and additional readme.txt tags</li>\n<li>Fix an array conversion warning in some versions of PHP</li>\n<li>Support a new WPCOM_API_KEY constant for easier use with WordPress MU</li>\n</ul>\n<h4>2.2.5</h4>\n<p><em>Release Date &#8211; 13th July, 2009</em></p>\n<ul>\n<li>Include a new Server Connectivity diagnostic check, to detect problems caused by firewalls</li>\n</ul>\n<h4>2.2.4</h4>\n<p><em>Release Date &#8211; 3rd June, 2009</em></p>\n<ul>\n<li>Fixed a key problem affecting the stats feature in WordPress MU</li>\n<li>Provide additional blog information in Akismet API calls</li>\n</ul>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<p>Upload the Akismet plugin to your blog, Activate it, then enter your <a href="https://akismet.com/get/" rel="nofollow">Akismet.com API key</a>.</p>\n<p>1, 2, 3: You&#8217;re done!</p>\n</dd>\n</dl>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:43:"https://wordpress.org/plugins/akismet/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"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:"";}}}}}i:3;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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Jetpack by WordPress.com";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"https://wordpress.org/plugins/jetpack/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/jetpack/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Jan 2011 02:21:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/plugins-wp/jetpack/";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:87:"Jetpack gives you tools to design, secure, and grow your site in one convenient bundle.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:11762:"<p><!--section=description--></p>\n<p>Keep any WordPress site secure, increase traffic, and engage your readers.</p>\n<h4>Traffic and SEO Tools</h4>\n<p>Traffic is the lifeblood of any website. Jetpack includes:</p>\n<ul>\n<li>[free] Site stats and analytics</li>\n<li>[free] Automatic sharing on Facebook, Twitter, LinkedIn, Tumblr, Reddit, and WhatsApp</li>\n<li>[free] Related posts</li>\n<li>[paid] Search engine optimization tools for Google, Bing, Twitter, Facebook, and WordPress.com</li>\n<li>[paid] Advertising program that includes the best of AdSense, Facebook Ads, AOL, Amazon, Google AdX, and Yahoo</li>\n</ul>\n<h4>Security and Backup Services</h4>\n<p>Stop worrying about data loss, downtime, and hacking. Jetpack provides:</p>\n<ul>\n<li>[free] Brute force attack protection</li>\n<li>[free] Downtime and uptime monitoring</li>\n<li>[free] Secured logins and two-factor authentication</li>\n<li>[paid] Malware scanning, code scanning, and threat resolution</li>\n<li>[paid] Site backups, restores, and migrations</li>\n</ul>\n<h4>Content Creation</h4>\n<p>Add rich, beautifully-presented media &#8212; no graphic design expertise necessary:</p>\n<ul>\n<li>[free] A high-speed CDN for your images</li>\n<li>[free] Carousels, slideshows, and tiled galleries</li>\n<li>[free] Simple embeds from YouTube, Google Documents, Spotify and more</li>\n<li>[free] Sidebar customization including Facebook, Twitter, and RSS feeds</li>\n<li>[free] Extra sidebar widgets including blog stats, calendar, and author widgets</li>\n<li>[paid] High-speed, ad-free, and high-definition video hosting</li>\n</ul>\n<h4>Discussion and Community</h4>\n<p>Create a connection with your readers and keep them coming back to your site with:</p>\n<ul>\n<li>[free] Email subscriptions</li>\n<li>[free] Comment login with Facebook, Twitter, and Google</li>\n<li>[free] Fully-customizable contact forms</li>\n<li>[free] Infinite scroll for your posts</li>\n</ul>\n<h4>Expert Support</h4>\n<p>We have an entire team of Happiness Engineers ready to help you. Ask your questions in the support forum, or <a href="https://jetpack.com/contact-support" rel="nofollow">contact us directly</a>.</p>\n<h4>Paid Services</h4>\n<p>Most of Jetpack&#8217;s features and services are free. Jetpack also provides advanced security and backup services, video hosting, site monetization, priority support, and more SEO tools in three <a href="https://jetpack.com/pricing?from=wporg" rel="nofollow">simple and affordable plans</a>.</p>\n<h4>Get Started</h4>\n<p>Installation is free, quick, and easy. Set up <a href="https://jetpack.com/install?from=wporg" rel="nofollow">the free plan</a> in minutes.</p>\n<p><!--section=installation--></p>\n<h4>Automated Installation</h4>\n<p>Installation is free, quick, and easy. <a href="https://jetpack.com/install?from=wporg" rel="nofollow">Install Jetpack from our site</a> in minutes.</p>\n<h4>Manual Alternatives</h4>\n<p>Alternatively, install Jetpack via the plugin directory, or upload the files manually to your server and follow the on-screen instructions. If you need additional help <a href="https://jetpack.com/support/installing-jetpack/" rel="nofollow">read our detailed instructions</a>.</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<h4>Automated Installation</h4>\n<p>Installation is free, quick, and easy. <a href="https://jetpack.com/install?from=wporg" rel="nofollow">Install Jetpack from our site</a> in minutes.</p>\n<h4>Manual Alternatives</h4>\n<p>Alternatively, install Jetpack via the plugin directory, or upload the files manually to your server and follow the on-screen instructions. If you need additional help <a href="https://jetpack.com/support/installing-jetpack/" rel="nofollow">read our detailed instructions</a>.</p>\n</dd>\n<dt>Is Jetpack Free?</dt>\n<dd>\n<p>Yes! Jetpack&#8217;s core features are and always will be free.</p>\n<p>These include: <a href="https://jetpack.com/features/traffic/site-stats" rel="nofollow">site stats</a>, a <a href="https://jetpack.com/features/writing/content-delivery-network/" rel="nofollow">high-speed CDN</a> for images, <a href="https://jetpack.com/features/traffic/related-posts" rel="nofollow">related posts</a>, <a href="https://jetpack.com/features/security/downtime-monitoring" rel="nofollow">downtime monitoring</a>, brute force <a href="https://jetpack.com/features/security/brute-force-attack-protection" rel="nofollow">attack protection</a>, <a href="https://jetpack.com/features/traffic/automatic-publishing/" rel="nofollow">automated sharing</a> to social networks, <a href="https://jetpack.com/features/writing/sidebar-customization/" rel="nofollow">sidebar customization</a>, and many more.</p>\n</dd>\n<dt>Should I purchase a paid plan?</dt>\n<dd>\n<p>Jetpack&#8217;s paid services include automated backups, security scanning, spam filtering, video hosting, site monetization, SEO tools, and priority support.</p>\n<p>If you&#8217;re interested in learning more about the extra layers of protection and advanced tools available, learn more about our <a href="https://jetpack.com/pricing?from=wporg" rel="nofollow">paid plans</a>.</p>\n</dd>\n<dt>Why do I need a WordPress.com account?</dt>\n<dd>\n<p>Since Jetpack and its services are provided and hosted by WordPress.com, a WordPress.com account is required for Jetpack to function.</p>\n</dd>\n<dt>I already have a WordPress account, but Jetpack isn&#8217;t working. What&#8217;s going on?</dt>\n<dd>\n<p>A WordPress.com account is different from the account you use to log into your self-hosted WordPress. If you can log into <a href="https://wordpress.com" rel="nofollow">WordPress.com</a>, then you already have a WordPress.com account. If you can&#8217;t, you can easily create one <a href="https://jetpack.com/install?from=wporg" rel="nofollow">during installation</a>.</p>\n</dd>\n<dt>How do I view my stats?</dt>\n<dd>\n<p>Once you&#8217;ve installed Jetpack your stats will be available on <a href="https://wordpress.com/stats" rel="nofollow">WordPress.com/Stats</a>, on the official <a href="https://apps.wordpress.com/mobile/" rel="nofollow">WordPress mobile apps</a>, and on your Jetpack dashboard.</p>\n</dd>\n<dt>How do I contribute to Jetpack?</dt>\n<dd>\n<p>There are opportunities for developers at all levels to contribute. <a href="https://jetpack.com/contribute" rel="nofollow">Learn more about contributing to Jetpack</a> or consider <a href="https://jetpack.com/beta" rel="nofollow">joining our beta program</a>.</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>5.3</h4>\n<ul>\n<li>Release date: September 5, 2017</li>\n<li>Release post: http://wp.me/p1moTy-5Xv</li>\n</ul>\n<p><strong>Major Enhancements</strong><br />\n* Full PHP 7.1 compatibility.<br />\n* It&#8217;s now possible to preview your site within WordPress.com.</p>\n<p><strong>Enhancements</strong><br />\n* The Ads feature now gives you more options and control over the ads displayed on your site.<br />\n* Increased performance in the admin by cutting back on unnecessary requests.<br />\n* Loading comment avatars from Facebook and Twitter through a more secure https.<br />\n* Admin UI is much friendlier on initial activation when there are no stats to display.<br />\n* You&#8217;re now able to stop VideoPress from looping a video during autoplay through the shortcode.<br />\n* Made some optimizations to the Jetpack connection process which means connecting your site more is more reliable.<br />\n* The EU Cookie Law widget got some styling improvements and looks better in any theme.<br />\n* There&#8217;s a new Jetpack CLI command to allow testing of the Jetpack connection.<br />\n* Added the Likes and Monitor features to our recommended features list, making it easier to activate for new sites.<br />\n* Improvements made that makes sure we have the most up-to-date version of your site when managing from WordPress.com.<br />\n* Added a link to view your Comments in the WordPress.com toolbar.<br />\n* Lots of minor design improvements to the Jetpack admin area.<br />\n* We&#8217;ve found a few places where we were able to optimize the loading of css files.<br />\n* Removed the Omnisearch feature.</p>\n<p><strong>Bug fixes</strong><br />\n* Fixed compatibility issues with plugins using TinyMCE.<br />\n* Contact Form submission emails have been fixed for sites hosted on SiteGround.<br />\n* Updating WordPress.com themes will no longer have any problems.<br />\n* The Sitemaps feature will no longer error with posts/images with special characters in the title.<br />\n* There are no more conflicts with the ACF plugin when adding a new custom field.<br />\n* Fixed a bug that would cause some plugins to throw warnings with the Shortcode feature.<br />\n* We&#8217;re no longer loading a font on the front-end for the Likes feature, which will also have some performance benefits.<br />\n* The Jetpack admin UI had some bugs that were causing some features to not display the correct active status, which are squashed now.<br />\n* Cleaned up our markup to avoid XHTML validation errors.<br />\n* Brought back a filter for the Widget Visibility feature that was accidentally removed.<br />\n* Managing your comments and comment authors more reliable from WordPress.com.</p>\n<h4>5.2.1</h4>\n<ul>\n<li>Release date: August 2, 2017</li>\n<li>Release post: https://jetpack.com/?p=22686</li>\n</ul>\n<p><strong>Bug fixes</strong><br />\n* Solves an issue that caused widgets to lose their content when saved in WP Admin or Customizer.</p>\n<h4>5.2</h4>\n<ul>\n<li>Release date: August 1, 2017</li>\n<li>Release post: https://jetpack.com/?p=22509</li>\n</ul>\n<p><strong>Major Enhancements</strong><br />\n* Contact Forms now sports a fancy new interface that allows you to visually compose your form in the editor.<br />\n* We have a new and slick way to showcase and explain the features we recommend to activate to new users.</p>\n<p><strong>Enhancements</strong><br />\n* Reduced 500kb from plugin zip file, which means faster updates.<br />\n* Refactored and reduced code for Comment Likes so it&#8217;s faster and lighter.</p>\n<p><strong>Bug fixes</strong><br />\n* An inconsistency experienced in WordPress.com dashboard when Related Posts settings were set in the local site&#8217;s WP Admin is now fixed.<br />\n* Fixed a 404 when loading Open Sans font from a stylesheet plus now it&#8217;s only enqueued if it will be used.<br />\n* Solve PHP warnings when Image widget wasn&#8217;t migrated.</p>\n<h4>5.1</h4>\n<ul>\n<li>Release date: July 5th, 2017</li>\n<li>Release post: https://jetpack.com/?p=20888</li>\n</ul>\n<p><strong>Major Enhancements</strong><br />\n* You and your readers can now show appreciation to particularly clever comments with the new Comment Likes feature.</p>\n<p><strong>Enhancements</strong><br />\n* Quickly visit your current site&#8217;s front-end directly from the Masterbar&#8217;s new &#8220;View Site&#8221; item.<br />\n* Site data fetch from /me/sites REST API endpoint now includes <code>blog_public</code> in the list of returned options.<br />\n* The Flickr widget now automatically displays images in a grid if there&#8217;s enough room.<br />\n* E-mail sharing is now disabled by default unless it&#8217;s explicitly enabled by a filter or Akismet is active.</p>\n<p><strong>Compatibility Improvements</strong></p>\n<ul>\n<li>Updated instructions in Flickr widget to reflect recent changes to the Flickr UI.</li>\n</ul>\n<p><strong>Bug fixes</strong></p>\n<ul>\n<li>EU Cookie Law Banner cookie no longer cached.</li>\n<li>WP Admin menu can now be accessed in mobile when Masterbar is displayed.</li>\n<li>We now sync the <code>order_id</code> for <code>order_items</code> in older WooCommerce versions.</li>\n<li>UI now handles VaultPress connection or registration problems gracefully.</li>\n<li>Photon now works correctly with images uploaded before WordPress 2.7.</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:43:"https://wordpress.org/plugins/jetpack/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"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:"";}}}}}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:3:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"WordPress Importer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:49:"https://wordpress.org/plugins/wordpress-importer/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 May 2010 18:48: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:8:"category";a:1:{i:0;a:5:{s:4:"data";s:13:"Uncategorized";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:52:"https://wordpress.org/plugins-wp/wordpress-importer/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:101:"Import posts, pages, comments, custom fields, categories, tags and more from a WordPress export file.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Brian Colinger";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:4618:"<p><!--section=description--></p>\n<p>The WordPress Importer will import the following content from a WordPress export file:</p>\n<ul>\n<li>Posts, pages and other custom post types</li>\n<li>Comments</li>\n<li>Custom fields and post meta</li>\n<li>Categories, tags and terms from custom taxonomies</li>\n<li>Authors</li>\n</ul>\n<p>For further information and instructions please see the <a href="https://codex.wordpress.org/Importing_Content#WordPress" rel="nofollow">Codex page on Importing Content</a></p>\n<h3>Filters</h3>\n<p>The importer has a couple of filters to allow you to completely enable/block certain features:</p>\n<ul>\n<li><code>import_allow_create_users</code>: return false if you only want to allow mapping to existing users</li>\n<li><code>import_allow_fetch_attachments</code>: return false if you do not wish to allow importing and downloading of attachments</li>\n<li><code>import_attachment_size_limit</code>: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited)</li>\n</ul>\n<p>There are also a few actions available to hook into:</p>\n<ul>\n<li><code>import_start</code>: occurs after the export file has been uploaded and author import settings have been chosen</li>\n<li><code>import_end</code>: called after the last output from the importer</li>\n</ul>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<p>The quickest method for installing the importer is:</p>\n<ol>\n<li>Visit Tools -&gt; Import in the WordPress dashboard</li>\n<li>Click on the WordPress link in the list of importers</li>\n<li>Click &#8220;Install Now&#8221;</li>\n<li>Finally click &#8220;Activate Plugin &amp; Run Importer&#8221;</li>\n</ol>\n<p>If you would prefer to do things manually then follow these instructions:</p>\n<ol>\n<li>Upload the <code>wordpress-importer</code> folder to the <code>/wp-content/plugins/</code> directory</li>\n<li>Activate the plugin through the &#8216;Plugins&#8217; menu in WordPress</li>\n<li>Go to the Tools -&gt; Import screen, click on WordPress</li>\n</ol>\n</dd>\n<dt>Help! I&#8217;m getting out of memory errors or a blank screen.</dt>\n<dd>\n<p>If your exported file is very large, the import script may run into your host&#8217;s configured memory limit for PHP.</p>\n<p>A message like &#8220;Fatal error: Allowed memory size of 8388608 bytes exhausted&#8221; indicates that the script can&#8217;t successfully import your XML file under the current PHP memory limit. If you have access to the php.ini file, you can manually increase the limit; if you do not (your WordPress installation is hosted on a shared server, for instance), you might have to break your exported XML file into several smaller pieces and run the import script one at a time.</p>\n<p>For those with shared hosting, the best alternative may be to consult hosting support to determine the safest approach for running the import. A host may be willing to temporarily lift the memory limit and/or run the process directly from their end.</p>\n<p>&#8212; <a href="https://codex.wordpress.org/Importing_Content#Before_Importing" rel="nofollow">WordPress Codex: Importing Content</a></p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>0.6.3</h4>\n<ul>\n<li>Add support for import term metadata.</li>\n<li>Fix bug that caused slashes to be stripped from imported content.</li>\n<li>Fix bug that caused characters to be stripped inside of CDATA in some cases.</li>\n<li>Fix PHP notices.</li>\n</ul>\n<h4>0.6.2</h4>\n<ul>\n<li>Add wp_import_existing_post filter. See: https://core.trac.wordpress.org/ticket/33721</li>\n</ul>\n<h4>0.6</h4>\n<ul>\n<li>Support for WXR 1.2 and multiple CDATA sections</li>\n<li>Post aren&#8217;t duplicates if their post_type&#8217;s are different</li>\n</ul>\n<h4>0.5.2</h4>\n<ul>\n<li>Double check that the uploaded export file exists before processing it. This prevents incorrect error messages when<br />\nan export file is uploaded to a server with bad permissions and WordPress 3.3 or 3.3.1 is being used.</li>\n</ul>\n<h4>0.5</h4>\n<ul>\n<li>Import comment meta (requires export from WordPress 3.2)</li>\n<li>Minor bugfixes and enhancements</li>\n</ul>\n<h4>0.4</h4>\n<ul>\n<li>Map comment user_id where possible</li>\n<li>Import attachments from <code>wp:attachment_url</code></li>\n<li>Upload attachments to correct directory</li>\n<li>Remap resized image URLs correctly</li>\n</ul>\n<h4>0.3</h4>\n<ul>\n<li>Use an XML Parser if possible</li>\n<li>Proper import support for nav menus</li>\n<li>&#8230; and much more, see <a href="https://core.trac.wordpress.org/ticket/15197" rel="nofollow">Trac ticket #15197</a></li>\n</ul>\n<h4>0.1</h4>\n<ul>\n<li>Initial release</li>\n</ul>\n";s: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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:11:"WooCommerce";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"https://wordpress.org/plugins/woocommerce/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/woocommerce/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 27 Sep 2011 15:32:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:45:"https://wordpress.org/plugins-wp/woocommerce/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:97:"WooCommerce is a powerful, extendable eCommerce plugin that helps you sell anything. Beautifully.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"WooThemes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:23662:"<p><!--section=description--></p>\n<p>WooCommerce is a free eCommerce plugin that allows you to sell anything, beautifully. Built to integrate seamlessly with WordPress, WooCommerce is the world’s favorite eCommerce solution that gives both store owners and developers complete control.</p>\n<p>With endless flexibility and access to hundreds of free and premium WordPress extensions, WooCommerce now powers 30% of all online stores &#8212; more than any other platform.</p>\n<iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/1KahlicghaE?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe>\n<h4>Sell anything, anywhere</h4>\n<p>With WooCommerce, you can sell both physical and digital goods in all shapes and sizes, offer product variations, multiple configurations, and instant downloads to shoppers, and even sell affiliate goods from online marketplaces.</p>\n<p>With premium extensions, you can offer bookings, memberships, and recurring subscriptions. Perhaps you’d like to sell monthly subscriptions for physical goods, or offer your members a discount on digital downloads? It’s all possible.</p>\n<h4>Ship wherever you like</h4>\n<p>Offer free shipping, flat rate shipping, or make real-time calculations. Limit your shipments to specific countries, or open your store up to the world. Shipping is highly configurable, and WooCommerce even supports drop shipping.</p>\n<h4>Extensive payment options</h4>\n<p>WooCommerce comes bundled with the ability to accept major credit cards, PayPal, BACS (bank transfers), and cash on delivery. Need additional options? More than 140 region-specific gateways integrate with WooCommerce, including popular choices like Stripe, Authorize.Net, and Amazon Payments.</p>\n<h4>You control it all &#8212; forever</h4>\n<p>WooCommerce gives you complete control of your store, from taxes to stock levels to customer accounts. Add and remove extensions, change your design, and switch settings as you please. It’s all under your control.</p>\n<p>One of the biggest risks of using a hosted eCommerce platform is what happens to your store if the provider closes up shop. With WooCommerce, you have complete control, so there’s never any reason to worry. Your data belongs to you &#8212; and it’s kept secure, thanks to regular audits by industry leaders.</p>\n<h4>Define your style with Storefront</h4>\n<p><a href="https://wordpress.org/themes/storefront/" rel="nofollow">Storefront</a> is a free WordPress theme available to any WooCommerce store. Along with deep WooCommerce integration, Storefront prioritizes speed and uptime while eliminating theme and plugin conflicts during major updates.</p>\n<p>Define your style even further by customizing Storefront to your liking or choosing from one of our several <a href="https://woocommerce.com/product-category/themes/storefront-child-theme-themes/" rel="nofollow">Storefront child themes</a>. It’s all up to you, and all open source.</p>\n<h4>Built with developers in mind</h4>\n<p>Extendable, adaptable, and open source &#8212; WooCommerce was created with developers in mind. With its strong, robust framework, you can scale your client’s store all the way from basic to high-end (infinity and beyond).</p>\n<p>Built with a REST API, WooCommerce can integrate with virtually any service. Your store’s data can be accessed anywhere, anytime, 100% securely. WooCommerce allows developers to easily create, modify, and grow a store that meets their specifications.</p>\n<p>No matter the size of the store you want to build, WooCommerce will scale to meet your requirements. With a growing collection of more than 300 extensions, you can enhance each store’s features to meet your client’s unique needs &#8212; or even create your own solution.</p>\n<p>If security is a concern, rest easy. WooCommerce is audited by a dedicated team of developers working around the clock to identify and patch any and all discovered bugs.</p>\n<p>We also support WooCommerce and all its extensions with comprehensive, easily-accessible documentation. With our docs, you’ll learn how to create the exact site your client needs.</p>\n<h4>Extensions galore</h4>\n<p>WordPress.org is home to some amazing extensions for WooCommerce, including:</p>\n<ul>\n<li><a href="https://wordpress.org/plugins/woocommerce-google-analytics-integration/">Google Analytics</a></li>\n<li><a href="https://wordpress.org/plugins/woocommerce-delivery-notes/">Delivery Notes</a></li>\n<li><a href="https://wordpress.org/plugins/woocommerce-pdf-invoices-packing-slips/">PDF Invoices and Packing Slips</a></li>\n<li><a href="https://wordpress.org/plugins/affiliates-woocommerce-light/">Affiliates Integration Light</a></li>\n<li><a href="https://wordpress.org/plugins/woocommerce-new-product-badge/">New Product Badges</a></li>\n</ul>\n<p>Keen to see them all? Search WordPress.org for ‘WooCommerce’ to dive in.</p>\n<p>If you’re looking for something endorsed and maintained by the developers who built WooCommerce, there are a plethora of premium eCommerce extensions, the most popular of which include:</p>\n<ul>\n<li><a href="https://woocommerce.com/products/woocommerce-subscriptions/" rel="nofollow">WooCommerce Subscriptions</a></li>\n<li><a href="https://woocommerce.com/products/woocommerce-memberships/" rel="nofollow">WooCommerce Memberships</a></li>\n<li><a href="https://woocommerce.com/products/woocommerce-bookings/" rel="nofollow">WooCommerce Bookings</a></li>\n<li><a href="https://woocommerce.com/products/dynamic-pricing/" rel="nofollow">Dynamic Pricing</a></li>\n<li><a href="https://woocommerce.com/products/table-rate-shipping/" rel="nofollow">Table Rate Shipping</a></li>\n<li><a href="https://woocommerce.com/products/product-csv-import-suite/" rel="nofollow">Product CSV Import Suite</a></li>\n</ul>\n<p>And there’s plenty more where they came from. Visit our <a href="https://woocommerce.com/product-category/woocommerce-extensions/" rel="nofollow">extensions page</a> to find out everything you’re capable of and all that&#8217;s possible with premium WooCommerce extensions.</p>\n<h4>Join our growing community</h4>\n<p>When you download WooCommerce, you join a community of more than a million store owners, developers, and WordPress enthusiasts. We’re one of the fastest-growing open source communities online, and whether you’re a n00b or a Ninja, we’d love to have you!</p>\n<p>If you’re interested in contributing to WooCommerce we’ve got more than 350 contributors, and there’s always room for more. Head over to the <a href="https://github.com/woocommerce/woocommerce" rel="nofollow">WooCommerce GitHub Repository</a> to find out how you can pitch in.</p>\n<p>Want to add a new language to WooCommerce? Swell! You can contribute via <a href="https://translate.wordpress.org/projects/wp-plugins/woocommerce" rel="nofollow">translate.wordpress.org</a>.</p>\n<p>And, finally, consider joining or spearheading a WooCommerce Meetup locally, more about those <a href="https://woocommerce.com/woocommerce/meetups/" rel="nofollow">here</a>.</p>\n<p><!--section=installation--></p>\n<h4>Minimum Requirements</h4>\n<ul>\n<li>PHP version 5.2.4 or greater (PHP 5.6 or greater is recommended)</li>\n<li>MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)</li>\n<li>Some payment gateways require fsockopen support (for IPN access)</li>\n<li>WooCommerce 2.5 requires WordPress 4.1+</li>\n<li>WooCommerce 2.6 requires WordPress 4.4+</li>\n</ul>\n<p>Visit the <a href="https://docs.woocommerce.com/document/server-requirements/" rel="nofollow">WooCommerce server requirements documentation</a> for a detailed list of server requirements.</p>\n<h4>Automatic installation</h4>\n<p>Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.</p>\n<p>In the search field type “WooCommerce” and click Search Plugins. Once you’ve found our eCommerce plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”.</p>\n<h4>Manual installation</h4>\n<p>The manual installation method involves downloading our eCommerce plugin and uploading it to your webserver via your favourite FTP application. The WordPress codex contains <a href="https://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation" rel="nofollow">instructions on how to do this here</a>.</p>\n<h4>Updating</h4>\n<p>Automatic updates should work like a charm; as always though, ensure you backup your site just in case.</p>\n<p>If on the off-chance you do encounter issues with the shop/category pages after an update you simply need to flush the permalinks by going to WordPress &gt; Settings &gt; Permalinks and hitting &#8216;save&#8217;. That should return things to normal.</p>\n<h4>Dummy data</h4>\n<p>WooCommerce comes with some dummy data you can use to see how products look; either import dummy_data.xml via the <a href="https://wordpress.org/plugins/wordpress-importer/">WordPress importer</a> or use our <a href="https://woocommerce.com/products/product-csv-import-suite/" rel="nofollow">CSV Import Suite plugin</a> to import dummy_data.csv and dummy_data_variations.csv.</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<h4>Minimum Requirements</h4>\n<ul>\n<li>PHP version 5.2.4 or greater (PHP 5.6 or greater is recommended)</li>\n<li>MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)</li>\n<li>Some payment gateways require fsockopen support (for IPN access)</li>\n<li>WooCommerce 2.5 requires WordPress 4.1+</li>\n<li>WooCommerce 2.6 requires WordPress 4.4+</li>\n</ul>\n<p>Visit the <a href="https://docs.woocommerce.com/document/server-requirements/" rel="nofollow">WooCommerce server requirements documentation</a> for a detailed list of server requirements.</p>\n<h4>Automatic installation</h4>\n<p>Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.</p>\n<p>In the search field type “WooCommerce” and click Search Plugins. Once you’ve found our eCommerce plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”.</p>\n<h4>Manual installation</h4>\n<p>The manual installation method involves downloading our eCommerce plugin and uploading it to your webserver via your favourite FTP application. The WordPress codex contains <a href="https://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation" rel="nofollow">instructions on how to do this here</a>.</p>\n<h4>Updating</h4>\n<p>Automatic updates should work like a charm; as always though, ensure you backup your site just in case.</p>\n<p>If on the off-chance you do encounter issues with the shop/category pages after an update you simply need to flush the permalinks by going to WordPress &gt; Settings &gt; Permalinks and hitting &#8216;save&#8217;. That should return things to normal.</p>\n<h4>Dummy data</h4>\n<p>WooCommerce comes with some dummy data you can use to see how products look; either import dummy_data.xml via the <a href="https://wordpress.org/plugins/wordpress-importer/">WordPress importer</a> or use our <a href="https://woocommerce.com/products/product-csv-import-suite/" rel="nofollow">CSV Import Suite plugin</a> to import dummy_data.csv and dummy_data_variations.csv.</p>\n</dd>\n<dt>Where can I find WooCommerce documentation and user guides?</dt>\n<dd>\n<p>For help setting up and configuring WooCommerce please refer to our <a href="https://docs.woocommerce.com/documentation/plugins/woocommerce/getting-started/" rel="nofollow">user guide</a></p>\n<p>For extending or theming WooCommerce, see our <a href="https://docs.woocommerce.com/documentation/plugins/woocommerce/woocommerce-codex/" rel="nofollow">codex</a>.</p>\n</dd>\n<dt>Where can I get support or talk to other users?</dt>\n<dd>\n<p>If you get stuck, you can ask for help in the <a href="https://wordpress.org/support/plugin/woocommerce" rel="nofollow">WooCommerce Plugin Forum</a>.</p>\n<p>For help with premium extensions from WooThemes, use <a href="https://support.woothemes.com/" rel="nofollow">our helpdesk</a>.</p>\n</dd>\n<dt>Will WooCommerce work with my theme?</dt>\n<dd>\n<p>Yes; WooCommerce will work with any theme, but may require some styling to make it match nicely. Please see our <a href="https://docs.woocommerce.com/documentation/plugins/woocommerce/woocommerce-codex/" rel="nofollow">codex</a> for help. If you&#8217;re looking for a theme with built in WooCommerce integration we recommend <a href="https://woocommerce.com/storefront/" rel="nofollow">Storefront</a>.</p>\n</dd>\n<dt>Where can I request new features, eCommerce themes and extensions?</dt>\n<dd>\n<p>You can vote on and request new features and extensions in our <a href="http://ideas.woothemes.com/forums/133476-woocommerce" rel="nofollow">WooIdeas board</a></p>\n</dd>\n<dt>Where can I report bugs or contribute to the project?</dt>\n<dd>\n<p>Bugs can be reported either in our support forum or preferably on the <a href="https://github.com/woocommerce/woocommerce/issues" rel="nofollow">WooCommerce GitHub repository</a>.</p>\n</dd>\n<dt>Where can I find the REST API documentation?</dt>\n<dd>\n<p>You can find the documentation of our REST API on the <a href="https://woocommerce.github.io/woocommerce-rest-api-docs/" rel="nofollow">WooCommerce REST API Docs</a>.</p>\n</dd>\n<dt>WooCommerce is awesome! Can I contribute?</dt>\n<dd>\n<p>Yes you can! Join in on our <a href="http://github.com/woocommerce/woocommerce/" rel="nofollow">GitHub repository</a> <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>3.1.2 &#8211; 2017-08-15</h4>\n<ul>\n<li>Fix &#8211; Importer: Prevent multiple placeholders being created when mixing IDs and SKUs.</li>\n<li>Fix &#8211; Importer: correctly set stock management props.</li>\n<li>Fix &#8211; Importer: Allow &#8220;unfiltered_html&#8221; for name, description and short description fields.</li>\n<li>Fix &#8211; Fix filename image handling.</li>\n<li>Fix &#8211; Rest API: Allow OPTIONS requests.</li>\n<li>Fix &#8211; Fixed missing reviews in product_page shortcode when querying by SKU.</li>\n<li>Fix &#8211; Don&#8217;t subtract negative taxes in net sales report.</li>\n<li>Fix &#8211; Sort by order + zone ID as a fallback in shipping zones so the zones always match in the same order.</li>\n<li>Fix &#8211; Corrected subject and heading in customer refunded email.</li>\n<li>Fix &#8211; Corrected handling of custom checkbox fields in checkout get_posted_data method.</li>\n<li>Fix &#8211; Fix admin help videos async property.</li>\n<li>Fix &#8211; Fixed price filters by introducing precision.</li>\n<li>Fix &#8211; Improved customer IP address detection.</li>\n<li>Fix &#8211; Fix dark theme readability.</li>\n<li>Fix &#8211; CLI tools command.</li>\n<li>Fix &#8211; Adjusted shop manager role to prevent unfiltered HTML being used.</li>\n<li>Fix &#8211; Various notices/warnings.</li>\n<li>Dev &#8211; Correctly invalidate cache after saving order items.</li>\n<li>Dev &#8211; Added <code>woocommerce_data_store_wp_{$this-&gt;meta_type}_read_meta</code> filter.</li>\n</ul>\n<h4>3.1.1 &#8211; 2017-07-11</h4>\n<ul>\n<li>Fix &#8211; Product importer: fixed handling of non UTF8 characters in descriptions.</li>\n<li>Fix &#8211; Product importer: Allow times in date fields.</li>\n<li>Fix &#8211; Product exporter: fixed meta data checkbox option.</li>\n<li>Fix &#8211; Helper: Styling and connect button in non-english languages.</li>\n<li>Fix &#8211; Tweak terms and conditions template to check for disallowed shortcodes.</li>\n<li>Fix &#8211; Fixed order helper queries when before_date and after_date args are both, corrected use of &#8220;paged&#8221;, and corrected use of filters.</li>\n<li>Fix &#8211; Gallery; Trigger resize after main image loads to ensure correct gallery size.</li>\n<li>Fix &#8211; Prevent extra slashes being added to meta values when using the CRUD.</li>\n<li>Fix &#8211; Appends &#8220;where&#8221; clauses in the comment feed to prevent a notice.</li>\n<li>Fix &#8211; Fixed structured data output for variable product prices.</li>\n<li>Fix &#8211; 3.x issue: Changed state validation logic to work for MX states.</li>\n<li>Fix &#8211; 3.x issue: 7day reports should start from midnight, not the current time.</li>\n<li>Fix &#8211; 3.x issue: Status changes made by admin should be marked as a manual in the order notes.</li>\n<li>Fix &#8211; 3.x issue: Allow unsetting product shipping class in REST API.</li>\n<li>Fix &#8211; 3.x issue: Corrected error handling in zones shippingMethodView.</li>\n<li>Tweak &#8211; Avoid CloudFlare email obfuscation in admin.</li>\n<li>Tweak &#8211; Improved detection of DOING_AUTOSAVE in admin meta box code.</li>\n<li>Tweak &#8211; Improved my-account redirects and fallbacks.</li>\n<li>Tweak &#8211; Add <code>cart_subtotal</code> to the shipping package so prices are recalculated when needed.</li>\n<li>Dev &#8211; Add search_customers() filter in customer data store.</li>\n<li>Dev &#8211; Product exporter: woocommerce_product_export_skip_meta_keys filter to control what gets exported.</li>\n<li>Dev &#8211; Pass correct value to woocommerce_shipping_classes_save_class when inserting a new term</li>\n</ul>\n<h4>3.1.0 &#8211; 2017-06-28</h4>\n<ul>\n<li>Feature &#8211; Built-in product CSV importer and exporter for products.</li>\n<li>Feature &#8211; Display (toggle-able) terms inline on the checkout rather than showing a link.</li>\n<li>Feature &#8211; On the &#8220;pay for order&#8221; page, if logged out show a login form rather than an error message.</li>\n<li>Feature &#8211; Enabled oembed support for product short descriptions.</li>\n<li>Feature &#8211; Added bulk variation update for stock status.</li>\n<li>Feature &#8211; On customer profiles: added a button to copy billing address to shipping address.</li>\n<li>Feature &#8211; Setup Wizard &#8211; Automatic Shipping Zone Creation In Setup Wizard for the base location.</li>\n<li>Feature &#8211; Setup Wizard &#8211; Added a new optional Storefront Theme step if you&#8217;re using a non-WooCommerce compatible theme.</li>\n<li>Feature &#8211; Made it possible to manage extension licenses purchased from WooCommerce.com on the extensions screen.</li>\n<li>Tweak &#8211; Gallery &#8211; Added a data-caption for captions to support both captions and titles for SEO.</li>\n<li>Tweak &#8211; Gallery &#8211; Used smoothHeight setting to better support images of different heights.</li>\n<li>Tweak &#8211; UI &#8211; Added blank states for API keys &amp; webhooks.</li>\n<li>Tweak &#8211; UI &#8211; Made Product submenu labels consistent in admin.</li>\n<li>Tweak &#8211; UI &#8211; Changed street address field label and placeholder to minimize user error on checkout.</li>\n<li>Tweak &#8211; UI &#8211; Added a confirmation before deleting log files.</li>\n<li>Tweak &#8211; If prices are the same for all variations, use price not priceSpecification in structured data.</li>\n<li>Tweak &#8211; Added variable so shipping calculator is shown on first row only when showing multiple shipping packages.</li>\n<li>Tweak &#8211; Updated mini-cart HTML to use a list.</li>\n<li>Tweak &#8211; Allow linking to single product additional_information tab from url hash.</li>\n<li>Tweak &#8211; Re-included WooCommerce endpoints on the appearance &gt; menus screens.</li>\n<li>Tweak &#8211; Always sync incorrect titles on variation read regardless of version.</li>\n<li>Tweak &#8211; Standardize rating HTML in all templates.</li>\n<li>Tweak &#8211; When searching, disable WC sort order so results are sorted by relevance.</li>\n<li>Tweak &#8211; Update price sorting code to use min or max for variable products depending on sorting direction.</li>\n<li>Tweak &#8211; Utilize $product method to get thumbnail in loops.</li>\n<li>Tweak &#8211; Check for an existing display name before updating a user on checkout. Adds display_name prop to the CRUD.</li>\n<li>Tweak &#8211; Adapt variable product price used in sorting based on direction of sort.</li>\n<li>Tweak &#8211; Made state validation less strict for keys.</li>\n<li>Tweak &#8211; For COD orders, force payment complete status to be completed.</li>\n<li>Fix &#8211; Use get_max_purchase_quantity in cart template and fix logic when stock management is off.</li>\n<li>Fix &#8211; Added log_id as the secondary sorting column to log list so log entries sort correctly.</li>\n<li>Fix &#8211; Fix shop page when using shop base and UTF8 shop page slug.</li>\n<li>Fix &#8211; Added handles so drag and drop does not break edit on mobile when sorting categories.</li>\n<li>Fix &#8211; Added ABSPATH checks to all files.</li>\n<li>Fix &#8211; Fixed how to flush rewrite rules after saving the shop main page.</li>\n<li>Fix &#8211; Emails sent via admin should switch to global locale.</li>\n<li>Fix &#8211; Set and restore wp_query so product page functions think it&#8217;s a real product page.</li>\n<li>Fix &#8211; Variation default value of &#8216;0&#8217; fails to save on product.</li>\n<li>Fix &#8211; Prevent locations being added to the &#8220;Rest Of The World&#8221; shipping zone via the API.</li>\n<li>Dev &#8211; Allow date created to be set in wc_create_refund.</li>\n<li>Dev &#8211; Introduced a <a href="https://github.com/woocommerce/woocommerce/wiki/wc_get_orders-and-WC_Order_Query" rel="nofollow">WC_Order_Query class</a> for finding/searching orders.</li>\n<li>Dev &#8211; Added &#8220;restored&#8221; webhook.</li>\n<li>Dev &#8211; Support floats for the custom attribute name sorting function.</li>\n<li>Dev &#8211; Updated Emogrifier to version 1.2.</li>\n<li>Dev &#8211; Sort product data tabs by priority in admin screen.</li>\n<li>Dev &#8211; Added new hooks for: dashboard reviews widget, product and category sorting events, woocommerce_add_to_cart_sold_individually_found_in_cart, cart empty messages.</li>\n<li>Dev &#8211; Added filters for zoom / flexslider / photoswipe enabling.</li>\n<li>Dev &#8211; Added filter for cookie name.</li>\n<li>Dev &#8211; Added ability to filter Photoswipe lightbox options.</li>\n<li>Dev &#8211; Added new filter for product thumbnail size.</li>\n<li>Dev &#8211; Added action for displaying custom data for fees in admin.</li>\n<li>Dev &#8211; Changed build_payload from private to public in webhook system.</li>\n<li>Dev &#8211; Added deprecated notice to WC_Order_Item_Meta (deprecated in 3.0).</li>\n<li>Dev &#8211; Added namespace to jQuery events that are removed in VariationForm.</li>\n<li>Dev &#8211; Made WC_Checkout::get_posted_data() public.</li>\n<li>Dev &#8211; Add custom message for custom system status tools.</li>\n<li>Dev &#8211; Added filters to change which order items are created and loaded to support custom item types.</li>\n<li>Dev &#8211; Updated jQuery payment and serializejson libraries.</li>\n<li>Localization &#8211; Added Bolivian states.</li>\n<li>Localization &#8211; Use VAT for Norway instead of Tax.</li>\n</ul>\n<p><a href="https://raw.githubusercontent.com/woocommerce/woocommerce/master/CHANGELOG.txt" rel="nofollow">See changelog for all versions</a>.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/woocommerce/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s: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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"All in One SEO Pack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/all-in-one-seo-pack/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/plugins/all-in-one-seo-pack/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 30 Mar 2007 19:30:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/plugins-wp/all-in-one-seo-pack/";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:83:"The original SEO plugin for WordPress, downloaded over 30,000,000 times since 2007.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"uberdose";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:5016:"<p><!--section=description--></p>\n<p>Use <strong>All in One SEO Pack</strong> to optimize your WordPress site for SEO. It&#8217;s easy and works out of the box for beginners, and has advanced features and an API for developers.</p>\n<p><strong><a href="http://semperplugins.com/plugins/all-in-one-seo-pack-pro-version/?loc=readme_utpv" rel="nofollow">Upgrade to Pro Version</a></strong></p>\n<p><a href="http://semperplugins.com/support/?loc=readme_ps" rel="nofollow">Premium Support</a></p>\n<p>First created in 2007, see why AIOSEO is one of the all time most downloaded plugins for WordPress.</p>\n<ul>\n<li>XML Sitemap support &#8211; submit your sitemap to Google and Bing and improve your SEO</li>\n<li>Image XML Sitemap submitted to Google and Bing to improve your Image SEO</li>\n<li>Google AMP support (Accelerated Mobile Pages)</li>\n<li>Google Analytics support</li>\n<li>Support for SEO on Custom Post Types</li>\n<li>Advanced Canonical URLs</li>\n<li>Redirect attachment pages to parent post</li>\n<li>Automatically notifies search engines like Google and Bing about changes to your site</li>\n<li>Built-in API so other plugins/themes can access and extend functionality</li>\n<li>ONLY free plugin to provide SEO Integration for e-Commerce sites, including WooCommerce</li>\n<li>Nonce Security built into All in One SEO Pack</li>\n<li>Automatically optimizes your <strong>titles</strong> for Google and other search engines</li>\n<li>Generates <strong>META tags automatically</strong></li>\n<li>Avoids the typical duplicate content found on WordPress blogs</li>\n<li>For beginners, you don&#8217;t even have to look at the options, it works out-of-the-box. Just install.</li>\n<li>For advanced users, you can fine-tune everything to optimize your SEO</li>\n<li>You can override any title and set any META description and any META keywords you want.</li>\n<li>Compatibility with many other plugins</li>\n<li>Translated into 57 languages</li>\n<li>PHP 7 100% Compatible</li>\n</ul>\n<p>Follow me on Twitter to keep up with the latest updates <a href="http://twitter.com/michaeltorbert/" rel="nofollow">Michael<br />\nTorbert</a></p>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/46MR4FboMaA?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n<h4>Tags</h4>\n<p>seo, SEO, All in One, google, meta, meta description, search engine optimization, xml sitemap, xml sitemaps, google sitemap, sitemap, sitemaps, robots meta, rss, rss footer, yahoo, bing, widget, Post, plugin, admin, posts, shortcode, sidebar, twitter, page, images, comments, image, news sitemaps, XML News Sitemaps, WordPress SEO, multisite, canonical, nofollow, noindex, keywords, meta keywords, description, webmaster tools, google webmaster tools, seo pack, schema.org, search engines, custom post types, custom taxonomies, canonical</p>\n<p><!--section=faq--></p>\n<p>Please visit our complete <strong><a href="http://semperplugins.com/documentation/" rel="nofollow">Documentation</a></strong> before requesting support for SEO from the<br />\n<strong><a href="http://semperplugins.com/support/" rel="nofollow">All in One SEO Pack Support Forum</a></strong></p>\n<p><a href="http://semperfiwebdesign.com/documentation/all-in-one-seo-pack/translations-for-all-in-one-seo-pack/" rel="nofollow">Translations</a></p>\n<dl>\n<dt>General Settings</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/uGt6CVbA5bI?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n<dt>XML Sitemaps</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/zvNU92Low8A?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n<dt>Social Meta</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/Dfe49FiiAog?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n<dt>Performance</dt>\n<dd>\n<p><iframe class=''youtube-player'' type=''text/html'' width=''640'' height=''390'' src=''https://www.youtube.com/embed/A0VKinM5s00?version=3&#038;rel=1&#038;fs=1&#038;autohide=2&#038;showsearch=0&#038;showinfo=1&#038;iv_load_policy=1&#038;wmode=transparent'' allowfullscreen=''true'' style=''border:0;''></iframe></p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<p>All in One SEO Pack <a href="http://semperfiwebdesign.com/documentation/all-in-one-seo-pack/all-in-one-seo-pack-release-history/" rel="nofollow">Changelog</a></p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/all-in-one-seo-pack/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s: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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"Google XML Sitemaps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/google-sitemap-generator/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:63:"https://wordpress.org/plugins/google-sitemap-generator/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 16 Jun 2005 09:33: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/plugins-wp/google-sitemap-generator/";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:94:"This plugin will improve SEO by helping search enginess better index your site using sitemaps.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Arne Brachhold";s: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:27964:"<p><!--section=description--></p>\n<p>Use this plugin to greatly improve SEO to create special XML sitemaps which will help search engines like Google, Bing, Yahoo and Ask.com to better index your site.</p>\n<p>With such a sitemap, it&#8217;s much easier for the crawlers to see the complete structure of your site and retrieve it more efficiently. The plugin supports all kinds of WordPress generated pages as well as custom URLs. Additionally it notifies all major search engines every time you create a post about the new content.</p>\n<p>Supported since <em>over 9 years</em> and rated as the <a href="https://wordpress.org/plugins/browse/top-rated/">best WordPress plugin</a>, it will do exactly what it&#8217;s supposed to do &#8211; providing a complete XML sitemap for search engines. It will not break your site, slow it down or annoy you. Guaranteed!</p>\n<blockquote>\n<p>If you like the plugin, feel free to rate it (on the right side of this page)! <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n</blockquote>\n<p>Related Links:</p>\n<ul>\n<li><a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/" title="Google XML Sitemaps Plugin for WordPress" rel="nofollow">Plugin Homepage</a></li>\n<li><a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/changelog/" title="Changelog of the Google XML Sitemaps Plugin for WordPress" rel="nofollow">Changelog</a></li>\n<li><a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/help/" title="Google Sitemaps FAQ" rel="nofollow">Plugin help and sitemaps FAQ</a></li>\n<li><a href="https://wordpress.org/support/topic/read-before-opening-a-new-support-topic" rel="nofollow">Support Forum</a></li>\n</ul>\n<h3>License</h3>\n<p>Good news, this plugin is free for everyone! Since it&#8217;s released under the GPL, you can use it free of charge on your personal or commercial site.</p>\n<h3>Translations</h3>\n<p>The plugin comes with various translations, please refer to the <a href="https://codex.wordpress.org/Installing_WordPress_in_Your_Language" title="Installing WordPress in Your Language" rel="nofollow">WordPress Codex</a> for more information about activating the translation. If you want to help to translate the plugin to your language, please have a look at the sitemap.pot file which contains all definitions and may be used with a <a href="http://www.gnu.org/software/gettext/" rel="nofollow">gettext</a> editor like <a href="http://www.poedit.net/" rel="nofollow">Poedit</a> (Windows).</p>\n<p><!--section=installation--></p>\n<ol>\n<li>Install the plugin like you always install plugins, either by uploading it via FTP or by using the &#8220;Add Plugin&#8221; function of WordPress.</li>\n<li>Activate the plugin at the plugin administration page</li>\n<li>If you want: Open the plugin configuration page, which is located under Settings -&gt; XML-Sitemap and customize settings like priorities and change frequencies.</li>\n<li>The plugin will automatically update your sitemap of you publish a post, so there is nothing more to do <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></li>\n</ol>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<ol>\n<li>Install the plugin like you always install plugins, either by uploading it via FTP or by using the &#8220;Add Plugin&#8221; function of WordPress.</li>\n<li>Activate the plugin at the plugin administration page</li>\n<li>If you want: Open the plugin configuration page, which is located under Settings -&gt; XML-Sitemap and customize settings like priorities and change frequencies.</li>\n<li>The plugin will automatically update your sitemap of you publish a post, so there is nothing more to do <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f642.png" alt="🙂" class="wp-smiley" style="height: 1em; max-height: 1em;" /></li>\n</ol>\n</dd>\n<dt>Where can I find the options page of the plugin?</dt>\n<dd>\n<p>It is under Settings &gt; XML Sitemap. I know nowadays many plugins add top-level menu items, but in most of the cases it is just not necessary. I&#8217;ve seen WP installations which looked like an Internet Explorer ten years ago with 20 toolbars installed. <img src="https://s.w.org/images/core/emoji/2.3/72x72/1f609.png" alt="😉" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>\n</dd>\n<dt>Do I have to create a sitemap.xml and sitemap.xml.gz by myself?</dt>\n<dd>\n<p>Not anymore. Since version 4, these files are dynamically generated. <em>There must be no sitemap.xml or sitemap.xml.gz in your site directory anymore!</em> The plugin will try to rename them to sitemap.xml.bak if they still exists.</p>\n</dd>\n<dt>Does this plugin use static files or &#8220;I can&#8217;t find the sitemap.xml file!&#8221;</dt>\n<dd>\n<p>Not anymore. Since version 4, these files are dynamically generated just like any other WordPress content.</p>\n</dd>\n<dt>There are no comments yet (or I&#8217;ve disabled them) and all my postings have a priority of zero!</dt>\n<dd>\n<p>Please disable automatic priority calculation and define a static priority for posts.</p>\n</dd>\n<dt>So many configuration options&#8230; Do I need to change them?</dt>\n<dd>\n<p>No, only if you want to. Default values are ok for most sites.</p>\n</dd>\n<dt>Does this plugin work with all WordPress versions?</dt>\n<dd>\n<p>This version works with WordPress 3.3 and better. If you&#8217;re using an older version, please check the <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/" title="Google (XML) Sitemap Generator Plugin Homepage" rel="nofollow">Google Sitemaps Plugin Homepage</a> for the legacy releases. There is a working release for every WordPress version since 1.5, but you really should consider updating your WordPress installation!</p>\n</dd>\n<dt>My question isn&#8217;t answered here</dt>\n<dd>\n<p>Most of the plugin options are described at the <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/" rel="nofollow">plugin homepage</a> as well as the dedicated <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/help/" title="List of common questions / problems regarding Google (XML) Sitemaps" rel="nofollow">Google Sitemaps FAQ</a>.</p>\n</dd>\n<dt>My question isn&#8217;t even answered there</dt>\n<dd>\n<p>Please post your question at the <a href="https://wordpress.org/support/topic/read-before-opening-a-new-support-topic" rel="nofollow">WordPress support forum</a> and tag your post with &#8220;google-sitemap-generator&#8221;.</p>\n</dd>\n<dt>What&#8217;s new in the latest version?</dt>\n<dd>\n<p>The changelog is maintained <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/changelog/" title="Google (XML) Sitemap Generator Plugin Changelog" rel="nofollow">here</a></p>\n</dd>\n<dt>Why is the changelog on a separate page and not here?</dt>\n<dd>\n<p>The WordPress.org repository is just another place to download this plugin. I don&#8217;t want to maintain too many pages with the same content. Thank you for your understanding!</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>4.0.9 (2017-07-24)</h4>\n<ul>\n<li>Fixed security issue related to donation functionality.</li>\n</ul>\n<h4>4.0.8 (2014-11-15)</h4>\n<ul>\n<li>Fixed bug regarding the exclude categories feature, thanks to Claus Schöffel!</li>\n</ul>\n<h4>4.0.7.1 (2014-09-02)</h4>\n<ul>\n<li>Sorry, no new features this time… This release only updates the Compatibility-Tag to WordPress 4.0. Unfortunately there is no way to do this anymore without a new version</li>\n</ul>\n<h4>4.0.7 (2014-06-23)</h4>\n<ul>\n<li>Better compatibility with GoDaddy managed WP hosting</li>\n<li>Better compatibility with QuickCache</li>\n<li>Removed WordPress version from the sitemap</li>\n<li>Corrected link to WordPress privacy settings (if search engines are blocked)</li>\n<li>Changed hook which is being used for sitemap pings to avoid pings on draft edit</li>\n</ul>\n<h4>4.0.6 (2014-06-03)</h4>\n<ul>\n<li>Added option to disable automatic gzipping</li>\n<li>Fixed bug with duplicated external sitemap entries</li>\n<li>Don’t gzip if behind Varnish since Varnish can do that</li>\n</ul>\n<h4>4.0.5 (2014-05-18)</h4>\n<ul>\n<li>Added function to manually start ping for main-sitemap or all sub-sitemaps</li>\n<li>Added support for changing the base of the sitemap URL to another URL (for WP installations in sub-folders)</li>\n<li>Fixed issue with empty post sitemaps (related to GMT/local time offset)</li>\n<li>Fixed some timing issues in archives</li>\n<li>Improved check for possible problems before gzipping</li>\n<li>Fixed empty archives and author sitemaps in case there were no posts</li>\n<li>Fixed bug which caused the Priority Provider to disappear in recent PHP versions</li>\n<li>Plugin will also ping with the corresponding sub-sitemap in case a post was modified</li>\n<li>Better checking for empty external urls</li>\n<li>Changed text in XSL template to be more clear about sitemap-index and sub-sitemaps</li>\n<li>Changed content type to text/xml to improve compatibility with caching plugins</li>\n<li>Changed query parameters to is_feed=true to improve compatibility with caching plugins</li>\n<li>Switched from using WP_Query to load posts to a custom SQL statement to avoid problems with other plugin filters</li>\n<li>Added caching of some SQL statements</li>\n<li>Added support feed for more help topics</li>\n<li>Added link to new help page</li>\n<li>Cleaned up code and renamed variables to be more readable</li>\n<li>Updated Japanese Translation, thanks to Daisuke Takahashi</li>\n</ul>\n<h4>4.0.4 (2014-04-19)</h4>\n<ul>\n<li>Removed deprecated get_page call</li>\n<li>Changed last modification time of sub-sitemaps to the last modification date of the posts instead of the publish date</li>\n<li>Removed information window if the statistic option has not been activated</li>\n<li>Added link regarding new sitemap format</li>\n<li>Updated Portuguese translation, thanks to Pedro Martinho</li>\n<li>Updated German translation</li>\n</ul>\n<h4>4.0.3 (2014-04-13)</h4>\n<ul>\n<li>Fixed compression if an gzlib handler was already active</li>\n<li>Help regarding permalinks for Nginx users</li>\n<li>Fix with gzip compression in case there was other output before already</li>\n<li>Return 404 for HTML sitemaps if the option has been disabled</li>\n<li>Updated translations</li>\n</ul>\n<h4>4.0.2 (2014-04-01)</h4>\n<ul>\n<li>Fixed warning if an gzip handler is already active</li>\n</ul>\n<h4>4.0.1 (2014-03-31)</h4>\n<ul>\n<li>Fixed bug with custom post types including a &#8220;-&#8220;</li>\n<li>Fixed some 404 Not Found Errors</li>\n</ul>\n<h4>4.0 (2014-03-30)</h4>\n<ul>\n<li>No static files anymore, sitemap is created on the fly!</li>\n<li>Sitemap is split-up into sub-sitemaps by month, allowing up to 50.000 posts per month! <a href="http://www.arnebrachhold.de/projects/wordpress-plugins/google-xml-sitemaps-generator/google-xml-sitemap-generator-new-sitemap-format/" rel="nofollow">More information</a></li>\n<li>Support for custom post types and custom taxonomis!</li>\n<li>100% Multisite compatible, including by-blog and network activation.</li>\n<li>Reduced server resource usage due to less content per request.</li>\n<li>New API allows other plugins to add their own, separate sitemaps.</li>\n<li>Note: PHP 5.1 and WordPress 3.3 is required! The plugin will not work with lower versions!</li>\n<li>Note: This version will try to rename your old sitemap files to *-old.xml. If that doesn’t work, please delete them manually since no static files are needed anymore!</li>\n</ul>\n<h4>3.4.1 (2014-04-10)</h4>\n<ul>\n<li>Compatibility with mysqli</li>\n</ul>\n<h4>Version 3.4 (2013-11-24)</h4>\n<ul>\n<li>Fixed deprecation warnings in PHP 5.4, thanks to Dion Hulse!</li>\n</ul>\n<h4>3.3 (2013-09-28)</h4>\n<ul>\n<li>Fixed problem with file permission checking</li>\n<li>Filter out hashs (#) in URLs</li>\n</ul>\n<h4>3.2.9 (2013-01-11)</h4>\n<ul>\n<li>Fixed security issue with change frequencies and filename of sitemap file. Exploit was only possible with admin account.</li>\n</ul>\n<h4>3.2.8 (2012-08-08)</h4>\n<ul>\n<li>Fixed wrong custom taxonomy URLs, thanks to ramon fincken of the wordpress.org forum!</li>\n<li>Removed ASK ping since they shut down their service.</li>\n<li>Exclude post_format taxonomy from custom taxonomy list</li>\n</ul>\n<h4>3.2.7 (2012-04-24)</h4>\n<ul>\n<li>Fixed custom post types, thanks to clearsite of the wordpress.org forum!</li>\n<li>Fixed broken admin layout on WP 3.4</li>\n</ul>\n<h4>3.2.6 (2011-09-19)</h4>\n<ul>\n<li>Removed YAHOO ping since YAHOO uses bing now</li>\n<li>Removed deprecated function call</li>\n</ul>\n<h4>3.2.5 (2011-07-11)</h4>\n<ul>\n<li>Backported Bing ping success fix from beta</li>\n<li>Added friendly hint to try out the new beta</li>\n</ul>\n<h4>3.2.4 (2010-05-29)</h4>\n<ul>\n<li>Added (GMT) to date column in sitemap xslt template to avoid confusion with different time zones</li>\n<li>Fixed wrong SQL statement for author pages, thanks to twoenoug</li>\n<li>Fixed several deprecated function calls</li>\n<li>Note: This release does not support the new multisite feature of WordPress yet and will not be active when multisite is enabled.</li>\n</ul>\n<h4>3.2.3 (2010-04-02)</h4>\n<ul>\n<li>Fixed that all pages were missing in the sitemap if the “Uncategorized” category was excluded</li>\n</ul>\n<h4>3.2.2 (2009-12-19)</h4>\n<ul>\n<li>Updated compatibility tag to WordPress 2.9</li>\n<li>Fixed PHP4 problems</li>\n</ul>\n<h4>3.2.1 (2009-12-16)</h4>\n<ul>\n<li>Notes and update messages at the top of the admin page could interfere with the manual build function</li>\n<li>Help links in the WP contextual help were not shown anymore since the last update</li>\n<li>IE 7 sometimes displayed a cached admin page</li>\n<li>Removed invalid link to config page from the plugin description (The link lead to a &#8220;Not enough permission error&#8221;)</li>\n<li>Improved performance of getting the current plugin version by caching</li>\n<li>Updated Spanish language files</li>\n</ul>\n<h4>3.2 (2009-11-23)</h4>\n<ul>\n<li>Added function to show the actual results of a ping instead of only linking to the url</li>\n<li>Added new hook (sm_rebuild) for third party plugins to start building the sitemap</li>\n<li>Fixed bug which showed the wrong URL for the latest Google ping result</li>\n<li>Added some missing documentation</li>\n<li>Removed hardcoded php name for sitemap file in admin urls</li>\n<li>Uses KSES for showing ping test results</li>\n<li>Ping test fixed for WP &lt; 2.3</li>\n</ul>\n<h4>3.1.9 (2009-11-13)</h4>\n<ul>\n<li>Fixed MySQL Error if author pages were included</li>\n</ul>\n<h4>3.1.8 (2009-11-07)</h4>\n<ul>\n<li>Improved custom taxonomy handling and fixed wrong last modification date</li>\n<li>Fixed fatal error in WordPress versions lower than 2.3</li>\n<li>Fixed Update Notice for WordPress 2.8 and higher</li>\n<li>Added warning if blog privacy is activated</li>\n<li>Fixed priorities of additional pages were shown as 0 instead of 1</li>\n</ul>\n<h4>3.1.7 (2009-10-21)</h4>\n<ul>\n<li>Added support for custom taxonomies. Thanks to Lee!</li>\n</ul>\n<h4>3.1.6 (2009-08-31)</h4>\n<ul>\n<li>Fixed PHP error “Only variables can be passed by reference”</li>\n<li>Fixed wrong URLS of multi-page posts (Thanks artstorm!)</li>\n<li>Updated many language files</li>\n</ul>\n<h4>3.1.5 (2009-08-24)</h4>\n<ul>\n<li>Added option to completely disable the last modification time</li>\n<li>Fixed problem with HTTPS url for the XSL stylesheet if the sitemap was build via the admin panel</li>\n<li>Improved handling of homepage entry if a single page was set for it</li>\n<li>Fixed mktime warning which appeared sometimes</li>\n<li>Fixed bug which caused inf. reloads after rebuilding the sitemap via the admin panel</li>\n<li>Improved handling of missing sitemaps files if WP was moved to another location</li>\n</ul>\n<h4>3.1.4 (2009-06-22)</h4>\n<ul>\n<li>Fixed bug which broke all pings in WP older than 2.7</li>\n<li>Added more output in debug mode if pings fail</li>\n<li>Moved global post variable so other plugins can use it in get_permalink()</li>\n<li>Added small icon for ozh admin menu</li>\n<li>Added more help links in UI</li>\n</ul>\n<h4>3.1.3 (2009-06-07)</h4>\n<ul>\n<li>Changed MSN Live Search to Bing</li>\n<li>Exclude categories also now exludes the category itself and not only the posts</li>\n<li>Pings now use the new WordPress HTTP API instead of Snoopy</li>\n<li>Fixed bug that in localized WP installations priorities could not be saved</li>\n<li>The sitemap cron job is now cleared after a manual rebuild or after changing the config</li>\n<li>Adjusted style of admin area for WP 2.8 and refreshed icons</li>\n<li>Disabled the “Exclude categories” feature for WP 2.5.1, since it doesn’t have the required functions yet</li>\n</ul>\n<h4>3.1.2 (2008-12-26)</h4>\n<ul>\n<li>Changed the way the stylesheet is saved (default / custom stylesheet)</li>\n<li>Sitemap is now rebuild when a page is published</li>\n<li>Removed support for static robots.txt files, this is now handled via WordPress functions</li>\n<li>Added compat. exceptions for WP 2.0 and WP 2.1</li>\n</ul>\n<h4>3.1.1 (2008-12-21)</h4>\n<ul>\n<li>Fixed redirect issue if wp-admin is rewritten via mod_rewrite, thanks to macjoost</li>\n<li>Fixed wrong path to assets, thanks PozHonks</li>\n<li>Fixed wrong plugin URL if wp-content was renamed / redirected, thanks to wnorris</li>\n<li>Updated WP User Interface for 2.7</li>\n<li>Various other small things</li>\n</ul>\n<h4>3.1.0.1 (2008-05-27)</h4>\n<ul>\n<li>Extracted UI JS to external file</li>\n<li>Enabled the option to include following pages of multi-page posts</li>\n<li>Script tries to raise memory and time limit if active</li>\n</ul>\n<h4>3.1 (2008-05-22)</h4>\n<ul>\n<li>Marked as stable</li>\n</ul>\n<h4>3.1b3 (2008-05-19)</h4>\n<ul>\n<li>Cleaned up plugin directory and moved img files to subfolders</li>\n<li>Fixed background building bug in WP 2.1</li>\n<li>Removed auto-update plugin link for WP &lt; 2.5</li>\n</ul>\n<h4>3.1b2 (2008-05-18)</h4>\n<ul>\n<li>Fixed critical bug with the build in background option</li>\n<li>Added notification if a build is scheduled</li>\n</ul>\n<h4>3.1b1 (2008-05-08)</h4>\n<ul>\n<li>Splitted plugin in loader, generator and user interface to save memory</li>\n<li>Generator and UI will only be loaded when needed</li>\n<li>Secured all admin actions with nonces</li>\n<li>Improved WP 2.5 handling</li>\n<li>New &#8220;Suggest a Feature&#8221; link</li>\n</ul>\n<h4>3.0.3.3 (2008-04-29)</h4>\n<ul>\n<li>Fixed author pages</li>\n<li>Enhanced background building and increased delay to 15 seconds</li>\n<li>Enabled background building by default</li>\n</ul>\n<h4>3.0.3.2 (2008-04-28)</h4>\n<ul>\n<li>Improved WP 2.5 handling (fixes blank screens and timeouts)</li>\n</ul>\n<h4>3.0.3.1 (2008-03-30)</h4>\n<ul>\n<li>Added compatibility CSS for WP 2.5</li>\n</ul>\n<h4>3.0.3 (2007-12-30)</h4>\n<ul>\n<li>Added option to ping MSN Live Search</li>\n<li>Removed some WordPress hooks (the sitemap isn’t updates with every comment anymore)</li>\n</ul>\n<h4>3.0.2.1 (2007-11-28)</h4>\n<ul>\n<li>Fixed wrong XML Schema Location (Thanks to Emanuele Tessore)</li>\n<li>Added Russian Language files by Sergey http://ryvkin.ru</li>\n</ul>\n<h4>3.0.2 (2007-11-25)</h4>\n<ul>\n<li>Fixed bug which caused that some settings were not saved correctly</li>\n<li>Added option to exclude pages or post by ID</li>\n<li>Restored YAHOO ping service with API key since the other one is to unreliable</li>\n</ul>\n<h4>3.0.1 (2007-11-03)</h4>\n<ul>\n<li>Changed HTTP client for ping requests to Snoopy</li>\n<li>Added &#8220;safemode&#8221; for SQL which doesn’t use unbuffered results</li>\n<li>Added option to run the building process in background using wp-cron</li>\n<li>Added links to test the ping if it failed</li>\n</ul>\n<h4>3.0 final (2007-09-24)</h4>\n<ul>\n<li>Marked as stable</li>\n<li>Removed useless functions</li>\n</ul>\n<h4>3.0b11 (2007-09-23)</h4>\n<ul>\n<li>Changed mysql queries to unbuffered queries</li>\n<li>Uses MUCH less memory</li>\n<li>Option to limit the number of posts</li>\n</ul>\n<h4>3.0b10 (2007-09-04)</h4>\n<ul>\n<li>Added category support for WordPress 2.3</li>\n<li>Fixed bug with empty URLs in sitemap</li>\n<li>Repaired GET building</li>\n</ul>\n<h4>3.0b9 (2007-09-02)</h4>\n<ul>\n<li>Added tag support for WordPress 2.3</li>\n<li>Fixed archive bug with static pages (Thanks to Peter Claus Lamprecht)</li>\n<li>Fixed some missing translation strings, thanks to Kirin Lin</li>\n</ul>\n<h4>3.0b8 (2007-07-22)</h4>\n<ul>\n<li>Fixed bug with empty categories</li>\n<li>Fixed bug with translation plugins</li>\n<li>Added support for robots.txt</li>\n<li>Switched YAHOO ping API from YAHOO Web Services to the “normal” ping service</li>\n<li>Search engines will only be pinged if the sitemap file has changed</li>\n</ul>\n<h4>3.0b7 (2007-05-17)</h4>\n<ul>\n<li>Added Ask.com notification</li>\n<li>Added option to include the author pages like /author/john</li>\n<li>Fixed WP 2.1 / Pre 2.1 post / pages database changes</li>\n<li>Added check to not build the sitemap if importing posts</li>\n<li>Fixed wrong XSLT location (Thanks froosh)</li>\n<li>Small enhancements and bug fixes</li>\n</ul>\n<h4>3.0b6 (2007-01-23)</h4>\n<ul>\n<li>sitemap.xml.gz was not compressed</li>\n<li>YAHOO update-notification was PHP5 only (Thanks to Joseph Abboud!)</li>\n<li>More WP 2.1 optimizations</li>\n<li>Reduced memory usage with PHP5</li>\n</ul>\n<h4>3.0b5 (2007-01-19)</h4>\n<ul>\n<li>WordPress 2 Design</li>\n<li>YAHOO update notification</li>\n<li>New status report, removed ugly logfiles</li>\n<li>Added option to define a XSLT stylesheet and added a default one</li>\n<li>Fixed bug with sub-pages, thanks to <a href="http://baptiste.us/" rel="nofollow">Mike</a>, <a href="http://fastagent.de/" rel="nofollow">Peter</a> and <a href="http://publicityship.com.au/" rel="nofollow">Glenn</a></li>\n<li>Improved file handling, thanks to <a href="http://www.vjtd3.com/" rel="nofollow">VJTD3</a></li>\n<li>WP 2.1 improvements</li>\n</ul>\n<h4>3.0b4 (2006-11-16)</h4>\n<ul>\n<li>Fixed some smaller bugs</li>\n<li>Decreased memory usage which should solve timeout and memory problems</li>\n<li>Updated namespace to support YAHOO and MSN</li>\n</ul>\n<h4>3.0b2 (2006-01-14)</h4>\n<ul>\n<li>Fixed several bugs reported by users</li>\n</ul>\n<h4>3.0b (2005-11-25)</h4>\n<ul>\n<li>WordPress 2.0 (Beta, RC1) compatible</li>\n<li>Added different priority calculation modes and introduced an API to create custom ones (Some people didn’t like the way to calculate the post priority based on the count of user comments. This will give you the possibility to develop custom priority providers which fit your needs.)</li>\n<li>Added support to use the <a href="http://www.alexking.org/blog/2005/07/27/popularity-contest-11/" rel="nofollow">Popularity Contest</a> plugin by <a href="http://www.alexking.org/" rel="nofollow">Alex King</a> to calculate post priority (If you are already using the Popularity Contest plugin, this will be the best way to determine the priority of the posts. Uses to new priority API noted above.)</li>\n<li>Added option to exclude password protected posts (This was one of the most requested features.)</li>\n<li>Posts and pages marked for publish with a date in the future won’t be included</li>\n<li>Added function to start sitemap creation via GET and a secret key (If you are using external software which directly writes into the database without using the WordPress API, you can rebuild the sitemap with a simple HTTP Request. This can be made with a cron job for example.)</li>\n<li>Improved compatibility with other plugins (There should no longer be problems with other plugins now which checked for existence of a specified function to determine if you are in the control panel or not.)</li>\n<li>Recoded plugin architecture which is now fully OOP (The code is now cleaner and better to understand which makes it easier to modify. This should also avoid namespace problems.)</li>\n<li>Improved speed and optimized settings handling (Settings and pages are only loaded if the sitemap generation process starts and not every time a page loads. This saves one MySQL Query on every request.)</li>\n<li>Added Button to restore default configuration (Messed up the config? You’ll need just one click to restore all settings.)</li>\n<li>Added log file to check everything is running (In the new log window you can see when your sitemap was rebuilt or if there was any error.)</li>\n<li>Improved user-interface</li>\n<li>Added several links to homepage and support (This includes the Notify List about new releases and the WordPress support forum.)</li>\n</ul>\n<h4>2.7 (2005-11-25)</h4>\n<ul>\n<li>Added Polish Translation by <a href="http://kubazwolinski.com/" rel="nofollow">kuba</a></li>\n</ul>\n<h4>2.7 (2005-11-01)</h4>\n<ul>\n<li>Added French Translation by <a href="http://www.chezthierry.info/" rel="nofollow">Thierry Lanfranchi</a></li>\n</ul>\n<h4>2.7 (2005-07-21)</h4>\n<ul>\n<li>Fixed bug with incorrect date in additional pages (wrong format)</li>\n<li>Added Swedish Translation by <a href="http://tobiasbergius.se/" rel="nofollow">Tobias Bergius</a></li>\n</ul>\n<h4>2.6 (2005-07-16)</h4>\n<ul>\n<li>Included Chinese (Simplified) language files by <a href="http://www.june6.cn/" rel="nofollow">june6</a></li>\n</ul>\n<h4>2.6 (2005-07-04)</h4>\n<ul>\n<li>Added support to store the files at a custom location</li>\n<li>Changed the home URL to have a slash at the end</li>\n<li>Fixed errors with wp-mail</li>\n<li>Added support for other plugins to add content to the sitemap</li>\n</ul>\n<h4>2.5 (2005-06-15)</h4>\n<ul>\n<li>You can include now external pages which aren’t generated by WordPress or are not recognized by this plugin</li>\n<li>You can define a minimum post priority, which will overrride the calculated value if it’s too low</li>\n<li>The plugin will automatically ping Google whenever the sitemap gets regenerated</li>\n<li>Update 1: Included Spanish translations by <a href="http://www.cesargomez.org/" rel="nofollow">Cesar Gomez Martin</a></li>\n<li>Update 2: Included Italian translations by <a href="http://wordpress-it.it/" rel="nofollow">Stefano Aglietti</a></li>\n<li>Update 3: Included Traditional Chinese translations by <a href="http://kirin-lin.idv.tw/" rel="nofollow">Kirin Lin</a></li>\n</ul>\n<h4>2.2 (2005-06-08)</h4>\n<ul>\n<li>Language file support: <a href="http://hiromasa.zone.ne.jp/" rel="nofollow">Hiromasa</a> from <a href="http://hiromasa.zone.ne.jp/" rel="nofollow">http://hiromasa.zone.ne.jp</a> sent me a japanese version of the user interface and modified the script to support it! Thanks for this! Check <a href="https://codex.wordpress.org/WordPress_Localization" rel="nofollow">the WordPress Codex</a> how to set the language in WordPress.</li>\n<li>Added Japanese user interface by <a href="http://hiromasa.zone.ne.jp/" rel="nofollow">Hiromasa</a></li>\n<li>Added German user interface by me</li>\n</ul>\n<h4>2.12 (2005-06-07)</h4>\n<ul>\n<li>Changed SQL Statement for categories that it also works on MySQL 3</li>\n</ul>\n<h4>2.11 (2005-06-07)</h4>\n<ul>\n<li>Fixed a hardcoded tablename which made a SQL error</li>\n</ul>\n<h4>2.1 (2005-06-07)</h4>\n<ul>\n<li>Can also generate a gzipped version of the xml file (sitemap.xml.gz)</li>\n<li>Uses correct last modification dates for categories and archives. (Thanks to thx <a href="http://www.shupe.ca/" rel="nofollow">Rodney Shupe</a> for the SQL)</li>\n<li>Supports now different WordPress / Blog directories</li>\n<li>Fixed bug which ignored different post/page priorities (Reported by <a href="http://h3h.net/" rel="nofollow">Brad</a>)</li>\n</ul>\n<h4>2.01 (2005-06-07)</h4>\n<ul>\n<li>Fixed compatibility for PHP installations which are not configured to use short open tags</li>\n<li>Changed Line 147 from _e($i); to _e(strval($i));</li>\n<li>Thanks to <a href="http://publicvoidblog.de/" rel="nofollow">Christian Aust</a> for reporting this!</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"https://wordpress.org/plugins/google-sitemap-generator/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s: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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"Limit Login Attempts";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/plugins/limit-login-attempts/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wordpress.org/plugins/limit-login-attempts/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 15 Jan 2009 14:20:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:54:"https://wordpress.org/plugins-wp/limit-login-attempts/";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:91:"Limit rate of login attempts, including by way of cookies, for each IP. Fully customizable.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:11518:"<p><!--section=description--></p>\n<p>Limit the number of login attempts possible both through normal login as well as using auth cookies.</p>\n<p>By default WordPress allows unlimited login attempts either through the login page or by sending special cookies. This allows passwords (or hashes) to be brute-force cracked with relative ease.</p>\n<p>Limit Login Attempts blocks an Internet address from making further attempts after a specified limit on retries is reached, making a brute-force attack difficult or impossible.</p>\n<p>Features</p>\n<ul>\n<li>Limit the number of retry attempts when logging in (for each IP). Fully customizable</li>\n<li>Limit the number of attempts to log in using auth cookies in same way</li>\n<li>Informs user about remaining retries or lockout time on login page</li>\n<li>Optional logging, optional email notification</li>\n<li>Handles server behind reverse proxy</li>\n<li>It is possible to whitelist IPs using a filter. But you probably shouldn&#8217;t. 🙂</li>\n</ul>\n<p>Translations: Bulgarian, Brazilian Portuguese, Catalan, Chinese (Traditional), Czech, Dutch, Finnish, French, German, Hungarian, Norwegian, Persian, Romanian, Russian, Spanish, Swedish, Turkish</p>\n<p>Plugin uses standard actions and filters only.</p>\n<p><!--section=installation--></p>\n<ol>\n<li>Download and extract plugin files to a wp-content/plugin directory.</li>\n<li>Activate the plugin through the WordPress admin interface.</li>\n<li>Customize the settings on the options page, if desired. If your server is located behind a reverse proxy make sure to change this setting.</li>\n</ol>\n<p>If you have any questions or problems please make a post here: https://wordpress.org/tags/limit-login-attempts</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Why not reset failed attempts on a successful login?</dt>\n<dd>\n<p>This is very much by design. Otherwise you could brute force the &#8220;admin&#8221; password by logging in as your own user every 4th attempt.</p>\n</dd>\n<dt>What is this option about site connection and reverse proxy?</dt>\n<dd>\n<p>A reverse proxy is a server in between the site and the Internet (perhaps handling caching or load-balancing). This makes getting the correct client IP to block slightly more complicated.</p>\n<p>The option default to NOT being behind a proxy &#8212; which should be by far the common case.</p>\n</dd>\n<dt>How do I know if my site is behind a reverse proxy?</dt>\n<dd>\n<p>You probably are not or you would know. We show a pretty good guess on the option page. Set the option using this unless you are sure you know better.</p>\n</dd>\n<dt>Can I whitelist my IP so I don&#8217;t get locked out?</dt>\n<dd>\n<p>First please consider if you really need this. Generally speaking it is not a good idea to have exceptions to your security policies.</p>\n<p>That said, there is now a filter which allows you to do it: &#8220;limit_login_whitelist_ip&#8221;.</p>\n<p>Example:<br />\nfunction my_ip_whitelist($allow, $ip) {<br />\n     return ($ip == &#8216;my-ip&#8217;) ? true : $allow;<br />\n}<br />\nadd_filter(&#8216;limit_login_whitelist_ip&#8217;, &#8216;my_ip_whitelist&#8217;, 10, 2);</p>\n<p>Note that we still do notification and logging as usual. This is meant to allow you to be aware of any suspicious activity from whitelisted IPs.</p>\n</dd>\n<dt>I locked myself out testing this thing, what do I do?</dt>\n<dd>\n<p>Either wait, or:</p>\n<p>If you know how to edit / add to PHP files you can use the IP whitelist functionality described above. You should then use the &#8220;Restore Lockouts&#8221; button on the plugin settings page and remove the whitelist function again.</p>\n<p>If you have ftp / ssh access to the site rename the file &#8220;wp-content/plugins/limit-login-attempts/limit-login-attempts.php&#8221; to deactivate the plugin.</p>\n<p>If you have access to the database (for example through phpMyAdmin) you can clear the limit_login_lockouts option in the wordpress options table. In a default setup this would work: &#8220;UPDATE wp_options SET option_value = &#8221; WHERE option_name = &#8216;limit_login_lockouts''&#8221;</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>1.7.1</h4>\n<p>This version fixes a security bug in version 1.6.2 and 1.7.0. Please upgrade immediately.</p>\n<p>&#8220;Auth cookies&#8221; are special cookies set at login that authenticating you to the system. It is how WordPress &#8220;remembers&#8221; that you are logged in between page loads.</p>\n<p>During lockout these are supposed to be cleared, but a change in 1.6.2 broke this. It allowed an attacker to keep trying to break these cookies during a lockout.</p>\n<p>Lockout of normal password login attempts still worked as it should, and it appears that all &#8220;auth cookie&#8221; attempts would keep getting logged.</p>\n<p>In theory the &#8220;auth cookie&#8221; is quite resistant to brute force attack. It contains a cryptographic hash of the user password, and the difficulty to break it is not based on the password strength but instead on the cryptographic operations used and the length of the hash value. In theory it should take many many years to break this hash. As theory and practice does not always agree it is still a good idea to have working lockouts of any such attempts.</p>\n<h4>1.7.0</h4>\n<ul>\n<li>Added filter that allows whitelisting IP. Please use with care!!</li>\n<li>Update to Spanish translation, thanks to Marcelo Pedra</li>\n<li>Updated Swedish translation</li>\n<li>Tested against WordPress 3.3.2</li>\n</ul>\n<h4>1.6.2</h4>\n<ul>\n<li>Fix bug where log would not get updated after it had been cleared</li>\n<li>Do plugin setup in &#8216;init&#8217; action</li>\n<li>Small update to Spanish translation file, thanks to Marcelo Pedra</li>\n<li>Tested against WordPress 3.2.1</li>\n</ul>\n<h4>1.6.1</h4>\n<ul>\n<li>(WordPress 3.0+) An invalid cookie can sometimes get sent multiple times before it gets cleared, resulting in multiple failed attempts or even a lockout from a single invalid cookie. Store the latest failed cookie to make sure we only count it as one failed attempt</li>\n<li>Define &#8220;Text Domain&#8221; correctly</li>\n<li>Include correct Dutch tranlation file. Thanks to Martin1 for noticing. Thanks again to Bjorn Wijers for the translation</li>\n<li>Updated POT file for this version</li>\n<li>Tested against WordPress 3.1-RC4</li>\n</ul>\n<h4>1.6.0</h4>\n<ul>\n<li>Happy New Year</li>\n<li>Tested against WordPress 3.1-RC1</li>\n<li>Plugin now requires WordPress version 2.8+. Of course you should never ever use anything but the latest version</li>\n<li>Fixed deprecation warnings that had been piling up with the old version requirement. Thanks to Johannes Ruthenberg for the report that prompted this</li>\n<li>Removed auth cookie admin check for version 2.7.</li>\n<li>Make sure relevant values in $_COOKIE get cleared right away on auth cookie validation failure. There are still some problems with cookie auth handling. The lockout can trigger prematurely in rare cases, but fixing it is plugin version 2 stuff unfortunately.</li>\n<li>Changed default time for retries to reset from 24 hours to 12 hours. The security impact is very minor and it means the warning will disappear &#8220;overnight&#8221;</li>\n<li>Added question to FAQ (&#8220;Why not reset failed attempts on a successful login?&#8221;)</li>\n<li>Updated screenshots</li>\n</ul>\n<h4>1.5.2</h4>\n<ul>\n<li>Reverted minor cookie-handling cleanup which might somehow be responsible for recently reported cookie related lockouts</li>\n<li>Added version 1.x Brazilian Portuguese translation, thanks to Luciano Passuello</li>\n<li>Added Finnish translation, thanks to Ari Kontiainen</li>\n</ul>\n<h4>1.5.1</h4>\n<ul>\n<li>Further multisite &amp; WPMU support (again thanks to <a href="mailto:&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;" rel="nofollow">&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;</a>)</li>\n<li>Better error handling if option variables are damaged</li>\n<li>Added Traditional Chinese translation, thanks to Denny Huang <a href="mailto:&#x62;&#105;&#x67;&#101;&#x78;&#112;&#x6c;&#111;&#114;&#x61;&#116;&#x69;&#111;&#x6e;&#115;&#064;&#x62;&#105;&#x67;&#101;&#x78;&#112;&#108;&#x6f;&#114;&#x61;&#116;&#x69;&#111;n&#x73;&#046;&#x63;&#111;&#x6d;&#046;t&#x77;" rel="nofollow">&#x62;&#105;&#x67;&#101;&#x78;&#112;&#x6c;&#111;&#114;&#x61;&#116;&#x69;&#111;&#x6e;&#115;&#064;&#x62;&#105;&#x67;&#101;&#x78;&#112;&#108;&#x6f;&#114;&#x61;&#116;&#x69;&#111;n&#x73;&#046;&#x63;&#111;&#x6d;&#046;t&#x77;</a></li>\n</ul>\n<h4>1.5</h4>\n<ul>\n<li>Tested against WordPress 3.0</li>\n<li>Handle 3.0 login page failure &#8220;shake&#8221;</li>\n<li>Basic multisite support (parts thanks to <a href="mailto:&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;" rel="nofollow">&#101;&#114;&#105;&#x6b;&#x40;&#101;&#114;&#105;&#x6b;&#x73;&#x68;&#111;&#115;t&#x69;&#x6e;&#103;&#046;c&#x6f;&#x6d;</a>)</li>\n<li>Added Dutch translation, thanks to Bjorn Wijers <a href="mailto:b&#117;&#x72;&#111;&#x62;&#x6a;&#111;&#x72;n&#064;&#x62;&#117;&#x72;&#x6f;&#098;&#x6a;&#111;&#114;&#x6e;&#046;&#x6e;l" rel="nofollow">b&#117;&#x72;&#111;&#x62;&#x6a;&#111;&#x72;n&#064;&#x62;&#117;&#x72;&#x6f;&#098;&#x6a;&#111;&#114;&#x6e;&#046;&#x6e;l</a></li>\n<li><a href="mailto:&#098;&#097;&#x6c;&#x69;&#110;&#116;&#x40;v&#101;&#x72;&#x65;&#115;&#107;&#x75;&#x74;&#105;&#046;&#x69;n&#102;&#x6f;" rel="nofollow">&#098;&#097;&#x6c;&#x69;&#110;&#116;&#x40;v&#101;&#x72;&#x65;&#115;&#107;&#x75;&#x74;&#105;&#046;&#x69;n&#102;&#x6f;</a></li>\n<li>Added French translation, thanks to oVa <a href="mailto:&#111;&#118;&#x61;&#x31;&#x33;l&#097;&#115;&#x74;&#x61;&#x72;&#064;&#103;&#109;&#097;&#x69;&#x6c;&#x2e;&#099;&#111;&#109;" rel="nofollow">&#111;&#118;&#x61;&#x31;&#x33;l&#097;&#115;&#x74;&#x61;&#x72;&#064;&#103;&#109;&#097;&#x69;&#x6c;&#x2e;&#099;&#111;&#109;</a></li>\n</ul>\n<h4>1.4.1</h4>\n<ul>\n<li>Added Turkish translation, thanks to Yazan Canarkadas</li>\n</ul>\n<h4>1.4</h4>\n<ul>\n<li>Protect admin page update using wp_nonce</li>\n<li>Added Czech translation, thanks to Jakub Jedelsky</li>\n</ul>\n<h4>1.3.2</h4>\n<ul>\n<li>Added Bulgarian translation, thanks to Hristo Chakarov</li>\n<li></li>\n<li>Added Spanish translation, thanks to Marcelo Pedra</li>\n<li>Added Persian translation, thanks to Mostafa Soufi</li>\n<li>Added Russian translation, thanks to Jack Leonid (http://studio-xl.com)</li>\n</ul>\n<h4>1.3.1</h4>\n<ul>\n<li>Added Catalan translation, thanks to Robert Buj</li>\n<li>Added Romanian translation, thanks to Robert Tudor</li>\n</ul>\n<h4>1.3</h4>\n<ul>\n<li>Support for getting the correct IP for clients while server is behind reverse proxy, thanks to Michael Skerwiderski</li>\n<li>Added German translation, thanks to Michael Skerwiderski</li>\n</ul>\n<h4>1.2</h4>\n<ul>\n<li>No longer replaces pluggable function when cookie handling active. Re-implemented using available actions and filters</li>\n<li>Filter error messages during login to avoid information leak regarding available usernames</li>\n<li>Do not show retries or lockout messages except for login (registration, lost password pages). No change in actual enforcement</li>\n<li>Slightly more aggressive in trimming old retries data</li>\n</ul>\n<h4>1.1</h4>\n<ul>\n<li>Added translation support</li>\n<li>Added Swedish translation</li>\n<li>During lockout, filter out all other login errors</li>\n<li>Minor cleanups</li>\n</ul>\n<h4>1.0</h4>\n<ul>\n<li>Initial version</li>\n</ul>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/plugins/limit-login-attempts/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s: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:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"TinyMCE Advanced";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/tinymce-advanced/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/tinymce-advanced/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 22 Jun 2007 06:02:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins-wp/tinymce-advanced/";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:58:"Extends and enhances TinyMCE, the WordPress Visual Editor.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Andrew Ozz";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:10701:"<p><!--section=description--></p>\n<p>This plugin will let you add, remove and arrange the buttons that are shown on the Visual Editor toolbar. You can configure up to four rows of buttons including Font Sizes, Font Family, text and background colors, tables, etc. It will also let you enable the editor menu, see the <a href="screenshots" rel="nofollow">screenshots</a>.</p>\n<p>It includes 15 plugins for <a href="http://tinymce.com/" rel="nofollow">TinyMCE</a> that are automatically enabled or disabled depending on the buttons you have chosen. In addition this plugin adds some commonly used options as keeping the paragraph tags in the Text editor and importing the CSS classes from the theme&#8217;s editor-style.css.</p>\n<h4>Some of the features added by this plugin</h4>\n<ul>\n<li>Support for creating and editing tables.</li>\n<li>More options when inserting lists.</li>\n<li>Search and Replace in the editor.</li>\n<li>Ability to set Font Family and Font Sizes.</li>\n<li>And many others.</li>\n</ul>\n<p>With this plugin you can also enable the TinyMCE menu above the toolbars. This will make the editor even more powerful and convenient.</p>\n<p><!--section=installation--></p>\n<p>Best is to install directly from WordPress. If manual installation is required, please make sure that the plugin files are in a folder named &#8220;tinymce-advanced&#8221; (not two nested folders) in the WordPress plugins folder, usually &#8220;wp-content/plugins&#8221;.</p>\n<p><!--section=faq--></p>\n<dl>\n<dt>Installation Instructions</dt>\n<dd>\n<p>Best is to install directly from WordPress. If manual installation is required, please make sure that the plugin files are in a folder named &#8220;tinymce-advanced&#8221; (not two nested folders) in the WordPress plugins folder, usually &#8220;wp-content/plugins&#8221;.</p>\n</dd>\n<dt>No styles are imported in the Formats sub-menu.</dt>\n<dd>\n<p>These styles are imported from your current theme editor-style.css file. However some themes do not have this functionality. For these themes TinyMCE Advanced has the option to let you add a customized editor-style.css and import it into the editor.</p>\n</dd>\n<dt>I have just installed this plugin, but it does not do anything.</dt>\n<dd>\n<p>Change some buttons on one of the toolbars, save your changes, clear your browser cache, and try again. If that does not work try reloding the Edit page several times while holding down Shift or Ctrl. There may also be a network cache somewhere between you and your host. You may need to wait for a few hours until this cache expires.</p>\n</dd>\n<dt>When I add &#8220;Smilies&#8221;, they do not show in the editor.</dt>\n<dd>\n<p>The &#8220;Emoticons&#8221; button in TinyMCE adds the codes for the smilies. The actual images are added by WordPress when viewing the Post. Make sure the checkbox &#8220;Convert emoticons to graphics on display&#8221; in &#8220;Options &#8211; Writing&#8221; is checked.</p>\n</dd>\n<dt>The plugin does not add any buttons.</dt>\n<dd>\n<p>Make sure the &#8220;Disable the visual editor when writing&#8221; checkbox under &#8220;Users &#8211; Your Profile&#8221; is <strong>not</strong> checked.</p>\n</dd>\n<dt>I still see the &#8220;old&#8221; buttons in the editor</dt>\n<dd>\n<p>Click the &#8220;Restore Default Settings&#8221; button on the plugin settings page and then set the buttons again and save.</p>\n</dd>\n<dt>Other questions? More screenshots?</dt>\n<dd>\n<p>Please post on the support forum or visit the homepage for <a href="http://www.laptoptips.ca/projects/tinymce-advanced/" rel="nofollow">TinyMCE Advanced</a>.</p>\n</dd>\n</dl>\n<p><!--section=changelog--></p>\n<h4>4.6.3</h4>\n<ul>\n<li>Updated for WordPress 4.8 and TinyMCE 4.6.3.</li>\n</ul>\n<h4>4.5.6</h4>\n<ul>\n<li>Updated for WordPress 4.7.4 and TinyMCE 4.5.6.</li>\n<li>Fixed PHP notice after importing settings.</li>\n</ul>\n<h4>4.4.3</h4>\n<ul>\n<li>Updated for WordPress 4.7 and TinyMCE 4.4.3.</li>\n<li>Fixed missing &#8220;Source code&#8221; button bug.</li>\n</ul>\n<h4>4.4.1</h4>\n<ul>\n<li>Updated for WordPress 4.6 and TinyMCE 4.4.1.</li>\n<li>Fixed multisite saving bug.</li>\n<li>Added new button in the Text editor to add or reset the line breaks. Adds line breaks only between tags. Works only when it detects that line breaks are missing so it doesn&#8217;t reformat posts with removed paragraphs.</li>\n</ul>\n<h4>4.3.10.1</h4>\n<ul>\n<li>Fixed adding paragraph tags when loading posts that were saved before turning autop off.</li>\n<li>Disabled the (new) inline toolbar for tables as it was overlapping the table in some cases.</li>\n</ul>\n<h4>4.3.10</h4>\n<ul>\n<li>Updated for WordPress 4.5.1 and TinyMCE 4.3.10.</li>\n<li>Fixed support for adding editor-style.css to themes that don&#8217;t have it.</li>\n</ul>\n<h4>4.3.8</h4>\n<ul>\n<li>Updated for WordPress 4.5 and TinyMCE 4.3.8.</li>\n<li>Separated standard options and admin options.</li>\n<li>Added settings that can disable the plugin for the main editor, other editors in wp-admin or editors on the front-end.</li>\n<li>Korean translation by Josh Kim and Greek translation by Stathis Mellios.</li>\n</ul>\n<h4>4.2.8</h4>\n<ul>\n<li>Updated for WordPress 4.4 and TinyMCE 4.2.8.</li>\n<li>Japanese translation by Manabu Miwa.</li>\n</ul>\n<h4>4.2.5</h4>\n<ul>\n<li>Updated for WordPress 4.3.1 and TinyMCE 4.2.5.</li>\n<li>Fixed text domain and plugin headers.</li>\n</ul>\n<h4>4.2.3.1</h4>\n<ul>\n<li>Fix error with removing the &#8216;textpattern&#8217; plugin.</li>\n</ul>\n<h4>4.2.3</h4>\n<ul>\n<li>Updated for WordPress 4.3 and TinyMCE 4.2.3.</li>\n<li>Removed the &#8216;textpattern&#8217; plugin as WordPress 4.3 includes similar functionality by default.</li>\n<li>French translation by Nicolas Schneider.</li>\n</ul>\n<h4>4.1.9</h4>\n<ul>\n<li>Updated for WordPress 4.2 and TinyMCE 4.1.9.</li>\n<li>Fixed bugs with showing oEmbed previews when pasting an URL.</li>\n<li>Fixed bugs with getting the content from TinyMCE with line breaks.</li>\n</ul>\n<h4>4.1.7</h4>\n<ul>\n<li>Updated for WordPress 4.1 and TinyMCE 4.1.7.</li>\n<li>Fixed bug where consecutive caption shortcodes may be split with an empty paragraph tag.</li>\n</ul>\n<h4>4.1.1</h4>\n<ul>\n<li>Fix bug with image captions when wpautop is disabled.</li>\n<li>Add translation support to the settings page. Button names/descriptions are translated from JS using the existing WordPress translation, so this part of the settings page will be translated by default. The other text still needs separate translation.</li>\n</ul>\n<h4>4.1</h4>\n<ul>\n<li>Updated for WordPress 4.0 and TinyMCE 4.1.</li>\n<li>Add the &#8216;textpattern&#8217; plugin that supports some of the markdown syntax while typing, <a href="http://www.tinymce.com/wiki.php/Configuration:textpattern_patterns" rel="nofollow">(more info)</a>.</li>\n<li>Add the updated &#8216;table&#8217; plugin that supports background and border color.</li>\n</ul>\n<h4>4.0.2</h4>\n<ul>\n<li>Fix showing of the second, third and forth button rows when the Toolbar Toggle button is not used.</li>\n<li>Fix adding the &#8221;directionality&#8221; plugin when RTL or LTR button is selected.</li>\n<li>Show the &#8221;Advanced Options&#8221; to super admins on multisite installs.</li>\n<li>Add the &#8221;link&#8221; plugin including link rel setting. Replaces the Insert/Edit Link dialog when enabled.</li>\n<li>Include updated &#8221;table&#8221; plugin that has support for vertical align for cells.</li>\n</ul>\n<h4>4.0.1</h4>\n<p>Fix warnings on pages other than Edit Post. Update the description.</p>\n<h4>4.0</h4>\n<p>Updated for WordPress 3.9 and TinyMCE 4.0. Refreshed the settings screen. Added support for exporting and importing of the settings.</p>\n<h4>3.5.9.1</h4>\n<p>Updated for WordPress 3.8, fixed auto-embedding of single line URLs when not removing paragraph tags.</p>\n<h4>3.5.9</h4>\n<p>Updated for WordPress 3.7 and TinyMCE 3.5.9.</p>\n<h4>3.5.8</h4>\n<p>Updated for WordPress 3.5 and TinyMCE 3.5.8.</p>\n<h4>3.4.9</h4>\n<p>Updated for WordPress 3.4 and TinyMCE 3.4.9.</p>\n<h4>3.4.5.1</h4>\n<p>Fixed a bug preventing TinyMCE from importing CSS classes from editor-style.css.</p>\n<h4>3.4.5</h4>\n<p>Updated for WordPress 3.3 or later and TinyMCE 3.4.5.</p>\n<h4>3.4.2.1</h4>\n<p>Fix the removal of the <em>media</em> plugin so it does not require re-saving the settings.</p>\n<h4>3.4.2</h4>\n<p>Compatibility with WordPress 3.2 and TinyMCE 3.4.2, removed the options for support for iframe and HTML 5.0 elements as they are supported by default in WordPress 3.2, removed the <em>media</em> plugin as it is included by default.</p>\n<h4>3.3.9.1</h4>\n<p>Added advanced options: stop removing iframes, stop removing HTML 5.0 elements, moved the support for custom editor styles to editor-style.css in the current theme.</p>\n<p>Attention: if you have a customized tadv-mce.css file and your theme doesn&#8217;t have editor-style.css, please download tadv-mce.css, rename it to editor-style.css and upload it to your current theme directory. Alternatively you can add there the editor-style.css from the Twenty Ten theme. If your theme has editor-style.css you can add any custom styles there.</p>\n<h4>3.3.9</h4>\n<p>Compatibility with WordPress 3.1 and TinyMCE 3.3.9, improved P and BR tags option.</p>\n<h4>3.2.7</h4>\n<p>Compatibility with WordPress 2.9 and TinyMCE 3.2.7, several minor bug fixes.</p>\n<h4>3.2.4</h4>\n<p>Compatibility with WordPress 2.8 and TinyMCE 3.2.4, minor bug fixes.</p>\n<h4>3.2</h4>\n<p>Compatibility with WordPress 2.7 and TinyMCE 3.2, minor bug fixes.</p>\n<h4>3.1</h4>\n<p>Compatibility with WordPress 2.6 and TinyMCE 3.1, keeps empty paragraphs when disabling the removal of P and BR tags, the buttons for MCImageManager and MCFileManager can be arranged (if installed).</p>\n<h4>3.0.1</h4>\n<p>Compatibility with WordPress 2.5.1 and TinyMCE 3.0.7, added option to disable the removal of P and BR tags when saving and in the HTML editor (autop), added two more buttons to the HTML editor: autop and undo, fixed the removal of non-default TinyMCE buttons.</p>\n<h4>3.0</h4>\n<p>Support for WordPress 2.5 and TinyMCE 3.0.</p>\n<h4>2.2</h4>\n<p>Deactivate/Uninstall option page, font size drop-down menu and other small changes.</p>\n<h4>2.1</h4>\n<p>Improved language selection, improved compatibility with WordPress 2.3 and TinyMCE 2.1.1.1, option to override some of the imported css classes and other small improvements and bugfixes.</p>\n<h4>2.0</h4>\n<p>Includes an admin page for arranging the TinyMCE toolbar buttons, easy installation, a lot of bugfixes, customized &#8220;Smilies&#8221; plugin that uses the built-in WordPress smilies, etc. The admin page uses jQuery and jQuery UI that lets you &#8220;drag and drop&#8221; the TinyMCE buttons to arrange your own toolbars and enables/disables the corresponding plugins depending on the used buttons.</p>\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:52:"https://wordpress.org/plugins/tinymce-advanced/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:50:"https://wordpress.org/plugins/browse/popular/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:6:"hourly";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Tue, 03 Oct 2017 15:56:23 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:"Tue, 03 Oct 2017 15:41:23 GMT";s:4:"link";s:66:"<https://wordpress.org/plugins/wp-json/>; 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:"20150108085034";}', 'no');
