-- MySQL dump 10.13 Distrib 5.7.27, for Linux (x86_64) -- -- Host: localhost Database: groot_wbc -- ------------------------------------------------------ -- Server version 5.7.27 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; -- -- Current Database: `groot_wbc` -- CREATE DATABASE /*!32312 IF NOT EXISTS*/ `groot_wbc` /*!40100 DEFAULT CHARACTER SET latin1 */; USE `groot_wbc`; -- -- Table structure for table `wp_commentmeta` -- DROP TABLE IF EXISTS `wp_commentmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_commentmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`meta_id`), KEY `comment_id` (`comment_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_commentmeta` -- LOCK TABLES `wp_commentmeta` WRITE; /*!40000 ALTER TABLE `wp_commentmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wp_commentmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_comments` -- DROP TABLE IF EXISTS `wp_comments`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_comments` ( `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0', `comment_author` tinytext COLLATE utf8mb4_unicode_520_ci NOT NULL, `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_content` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `comment_karma` int(11) NOT NULL DEFAULT '0', `comment_approved` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '1', `comment_agent` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`comment_ID`), KEY `comment_post_ID` (`comment_post_ID`), KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), KEY `comment_date_gmt` (`comment_date_gmt`), KEY `comment_parent` (`comment_parent`), KEY `comment_author_email` (`comment_author_email`(10)) ) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_comments` -- LOCK TABLES `wp_comments` WRITE; /*!40000 ALTER TABLE `wp_comments` DISABLE KEYS */; INSERT INTO `wp_comments` VALUES (1,1,'A WordPress Commenter','wapuu@wordpress.example','https://wordpress.org/','','2019-06-19 01:12:11','2019-06-19 01:12:11','Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from Gravatar.',0,'1','','',0,0); /*!40000 ALTER TABLE `wp_comments` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_links` -- DROP TABLE IF EXISTS `wp_links`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_links` ( `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `link_url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_image` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_target` varchar(25) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_description` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_visible` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'Y', `link_owner` bigint(20) unsigned NOT NULL DEFAULT '1', `link_rating` int(11) NOT NULL DEFAULT '0', `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `link_rel` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_notes` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `link_rss` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', PRIMARY KEY (`link_id`), KEY `link_visible` (`link_visible`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_links` -- LOCK TABLES `wp_links` WRITE; /*!40000 ALTER TABLE `wp_links` DISABLE KEYS */; /*!40000 ALTER TABLE `wp_links` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_options` -- DROP TABLE IF EXISTS `wp_options`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_options` ( `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `option_name` varchar(191) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `option_value` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `autoload` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'yes', PRIMARY KEY (`option_id`), UNIQUE KEY `option_name` (`option_name`) ) ENGINE=MyISAM AUTO_INCREMENT=149 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_options` -- LOCK TABLES `wp_options` WRITE; /*!40000 ALTER TABLE `wp_options` DISABLE KEYS */; INSERT INTO `wp_options` VALUES (1,'siteurl','https://pastes.vip','yes'),(2,'home','https://pastes.vip','yes'),(3,'blogname','Pastes','yes'),(4,'blogdescription','Just another WordPress site','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','admin@pastes.vip','yes'),(7,'start_of_week','1','yes'),(8,'use_balanceTags','0','yes'),(9,'use_smilies','1','yes'),(10,'require_name_email','1','yes'),(11,'comments_notify','1','yes'),(12,'posts_per_rss','10','yes'),(13,'rss_use_excerpt','0','yes'),(14,'mailserver_url','mail.example.com','yes'),(15,'mailserver_login','login@example.com','yes'),(16,'mailserver_pass','password','yes'),(17,'mailserver_port','110','yes'),(18,'default_category','1','yes'),(19,'default_comment_status','open','yes'),(20,'default_ping_status','open','yes'),(21,'default_pingback_flag','1','yes'),(22,'posts_per_page','10','yes'),(23,'date_format','F j, Y','yes'),(24,'time_format','g:i a','yes'),(25,'links_updated_date_format','F j, Y g:i a','yes'),(26,'comment_moderation','0','yes'),(27,'moderation_notify','1','yes'),(28,'permalink_structure','/%year%/%monthnum%/%day%/%postname%/','yes'),(29,'rewrite_rules','a:75:{s:11:\"^wp-json/?$\";s:22:\"index.php?rest_route=/\";s:14:\"^wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:21:\"^index.php/wp-json/?$\";s:22:\"index.php?rest_route=/\";s:24:\"^index.php/wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:12:\"robots\\.txt$\";s:18:\"index.php?robots=1\";s:48:\".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$\";s:18:\"index.php?feed=old\";s:20:\".*wp-app\\.php(/.*)?$\";s:19:\"index.php?error=403\";s:18:\".*wp-register.php$\";s:23:\"index.php?register=true\";s:32:\"feed/(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:27:\"(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:8:\"embed/?$\";s:21:\"index.php?&embed=true\";s:20:\"page/?([0-9]{1,})/?$\";s:28:\"index.php?&paged=$matches[1]\";s:41:\"comments/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:36:\"comments/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:17:\"comments/embed/?$\";s:21:\"index.php?&embed=true\";s:44:\"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:39:\"search/(.+)/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:20:\"search/(.+)/embed/?$\";s:34:\"index.php?s=$matches[1]&embed=true\";s:32:\"search/(.+)/page/?([0-9]{1,})/?$\";s:41:\"index.php?s=$matches[1]&paged=$matches[2]\";s:14:\"search/(.+)/?$\";s:23:\"index.php?s=$matches[1]\";s:47:\"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:42:\"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:23:\"author/([^/]+)/embed/?$\";s:44:\"index.php?author_name=$matches[1]&embed=true\";s:35:\"author/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?author_name=$matches[1]&paged=$matches[2]\";s:17:\"author/([^/]+)/?$\";s:33:\"index.php?author_name=$matches[1]\";s:69:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:45:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/embed/?$\";s:74:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]\";s:39:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$\";s:63:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]\";s:56:\"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:51:\"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:32:\"([0-9]{4})/([0-9]{1,2})/embed/?$\";s:58:\"index.php?year=$matches[1]&monthnum=$matches[2]&embed=true\";s:44:\"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]\";s:26:\"([0-9]{4})/([0-9]{1,2})/?$\";s:47:\"index.php?year=$matches[1]&monthnum=$matches[2]\";s:43:\"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:38:\"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:19:\"([0-9]{4})/embed/?$\";s:37:\"index.php?year=$matches[1]&embed=true\";s:31:\"([0-9]{4})/page/?([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&paged=$matches[2]\";s:13:\"([0-9]{4})/?$\";s:26:\"index.php?year=$matches[1]\";s:58:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:68:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:88:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:83:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:83:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:64:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:53:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/embed/?$\";s:91:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/trackback/?$\";s:85:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&tb=1\";s:77:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]\";s:72:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]\";s:65:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/page/?([0-9]{1,})/?$\";s:98:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&paged=$matches[5]\";s:72:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/comment-page-([0-9]{1,})/?$\";s:98:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&cpage=$matches[5]\";s:61:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)(?:/([0-9]+))?/?$\";s:97:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&page=$matches[5]\";s:47:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:57:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:77:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:72:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:72:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:53:\"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&cpage=$matches[4]\";s:51:\"([0-9]{4})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&cpage=$matches[3]\";s:38:\"([0-9]{4})/comment-page-([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&cpage=$matches[2]\";s:27:\".?.+?/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\".?.+?/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\".?.+?/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"(.?.+?)/embed/?$\";s:41:\"index.php?pagename=$matches[1]&embed=true\";s:20:\"(.?.+?)/trackback/?$\";s:35:\"index.php?pagename=$matches[1]&tb=1\";s:40:\"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:35:\"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:28:\"(.?.+?)/page/?([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&paged=$matches[2]\";s:35:\"(.?.+?)/comment-page-([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&cpage=$matches[2]\";s:24:\"(.?.+?)(?:/([0-9]+))?/?$\";s:47:\"index.php?pagename=$matches[1]&page=$matches[2]\";}','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(33,'active_plugins','a:0:{}','yes'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','','no'),(40,'template','twentynineteen','yes'),(41,'stylesheet','twentynineteen','yes'),(42,'comment_whitelist','1','yes'),(43,'blacklist_keys','','no'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','44719','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','1','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','posts','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'widget_categories','a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(79,'widget_text','a:0:{}','yes'),(80,'widget_rss','a:0:{}','yes'),(81,'uninstall_plugins','a:0:{}','no'),(82,'timezone_string','','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','0','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'wp_page_for_privacy_policy','3','yes'),(92,'show_comments_cookies_opt_in','1','yes'),(93,'initial_db_version','44719','yes'),(94,'wp_user_roles','a:5:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:61:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:34:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:10:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:5:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}}','yes'),(95,'fresh_site','1','yes'),(96,'widget_search','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(97,'widget_recent-posts','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(98,'widget_recent-comments','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(99,'widget_archives','a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(100,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(101,'sidebars_widgets','a:3:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}','yes'),(102,'cron','a:6:{i:1560910331;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1560949931;a:3:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}}i:1560993131;a:1:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1560993350;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1560993351;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}s:7:\"version\";i:2;}','yes'),(103,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(104,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(105,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(106,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(107,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(108,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(109,'nonce_key',',oK0RLct`Bb(Jh}A*v?%.4F?3u51}(hxnH3d:k|Itb((:SvJ$8s=j3*b{L4v%)-%_{Q7yne.K=.&Ft]`~joS=T.`9m0*3-q~','no'),(115,'recovery_keys','a:0:{}','yes'),(119,'theme_mods_twentynineteen','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(116,'_site_transient_update_core','O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.2.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.2.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.2.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.2.2-new-bundled.zip\";s:7:\"partial\";b:0;s:8:\"rollback\";b:0;}s:7:\"current\";s:5:\"5.2.2\";s:7:\"version\";s:5:\"5.2.2\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.0\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1560906732;s:15:\"version_checked\";s:5:\"5.2.2\";s:12:\"translations\";a:0:{}}','no'),(120,'_site_transient_timeout_theme_roots','1560908532','no'),(121,'_site_transient_theme_roots','a:4:{s:8:\"ribosome\";s:7:\"/themes\";s:14:\"twentynineteen\";s:7:\"/themes\";s:15:\"twentyseventeen\";s:7:\"/themes\";s:13:\"twentysixteen\";s:7:\"/themes\";}','no'),(122,'_site_transient_update_themes','O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1560906733;s:7:\"checked\";a:4:{s:8:\"ribosome\";s:5:\"2.5.0\";s:14:\"twentynineteen\";s:3:\"1.4\";s:15:\"twentyseventeen\";s:3:\"2.2\";s:13:\"twentysixteen\";s:3:\"2.0\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}}','no'),(123,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1560906733;s:7:\"checked\";a:5:{s:19:\"akismet/akismet.php\";s:5:\"4.1.2\";s:33:\"classic-editor/classic-editor.php\";s:3:\"1.5\";s:51:\"featured-image-from-url/featured-image-from-url.php\";s:5:\"2.5.0\";s:9:\"hello.php\";s:5:\"1.7.2\";s:42:\"wordpress-seo-premium-1/wp-seo-premium.php\";s:6:\"10.1.1\";}s:8:\"response\";a:1:{s:51:\"featured-image-from-url/featured-image-from-url.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:37:\"w.org/plugins/featured-image-from-url\";s:4:\"slug\";s:23:\"featured-image-from-url\";s:6:\"plugin\";s:51:\"featured-image-from-url/featured-image-from-url.php\";s:11:\"new_version\";s:5:\"2.5.1\";s:3:\"url\";s:54:\"https://wordpress.org/plugins/featured-image-from-url/\";s:7:\"package\";s:66:\"https://downloads.wordpress.org/plugin/featured-image-from-url.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:76:\"https://ps.w.org/featured-image-from-url/assets/icon-256x256.png?rev=1694895\";s:2:\"1x\";s:76:\"https://ps.w.org/featured-image-from-url/assets/icon-128x128.png?rev=1694895\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:79:\"https://ps.w.org/featured-image-from-url/assets/banner-1544x500.png?rev=1694895\";s:2:\"1x\";s:78:\"https://ps.w.org/featured-image-from-url/assets/banner-772x250.png?rev=1694895\";}s:11:\"banners_rtl\";a:0:{}s:14:\"upgrade_notice\";s:55:\"\";s:6:\"tested\";s:5:\"5.2.2\";s:12:\"requires_php\";b:0;s:13:\"compatibility\";O:8:\"stdClass\":0:{}}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:3:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.1.2\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.1.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}}s:33:\"classic-editor/classic-editor.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:28:\"w.org/plugins/classic-editor\";s:4:\"slug\";s:14:\"classic-editor\";s:6:\"plugin\";s:33:\"classic-editor/classic-editor.php\";s:11:\"new_version\";s:3:\"1.5\";s:3:\"url\";s:45:\"https://wordpress.org/plugins/classic-editor/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/plugin/classic-editor.1.5.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/classic-editor/assets/icon-256x256.png?rev=1998671\";s:2:\"1x\";s:67:\"https://ps.w.org/classic-editor/assets/icon-128x128.png?rev=1998671\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:70:\"https://ps.w.org/classic-editor/assets/banner-1544x500.png?rev=1998671\";s:2:\"1x\";s:69:\"https://ps.w.org/classic-editor/assets/banner-772x250.png?rev=1998676\";}s:11:\"banners_rtl\";a:0:{}}s:9:\"hello.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:5:\"1.7.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855\";s:2:\"1x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:66:\"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855\";}s:11:\"banners_rtl\";a:0:{}}}}','no'),(125,'secure_auth_salt','(/cnYS(~&?KXyUt#|mfnfXKt Kq#~.(*%|T;@^{Yo!{df=PbqXNcCVGhd4ev:T:,','no'),(126,'logged_in_key','0NT=8OP/q 9x/Ml$J^L.6xvEqchrcY;)-c]Lm*rK03[o-ccKD>U8z]teRAd /Mxs','no'),(127,'logged_in_salt','NDx3;(Pj%brjUSg!G{ei&ET!0;qsj+Ppi:)8Pq7hQZJ4 jN8#oNl4@`%,E-zT_1_','no'),(128,'_site_transient_timeout_browser_fd1885f00291b83c2cb49a9bbb9a909a','1561511751','no'),(129,'_site_transient_browser_fd1885f00291b83c2cb49a9bbb9a909a','a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:13:\"74.0.3729.169\";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'),(130,'_site_transient_timeout_php_check_a5907c2ea4d6fbd7e531b3aa7734f0e4','1561511751','no'),(131,'_site_transient_php_check_a5907c2ea4d6fbd7e531b3aa7734f0e4','a:5:{s:19:\"recommended_version\";s:3:\"7.3\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:0;s:9:\"is_secure\";b:0;s:13:\"is_acceptable\";b:1;}','no'),(133,'_site_transient_timeout_community-events-865de90b3b585c7255b6592a2347e913','1560950153','no'),(134,'_site_transient_community-events-865de90b3b585c7255b6592a2347e913','a:2:{s:8:\"location\";a:1:{s:2:\"ip\";s:12:\"31.171.152.0\";}s:6:\"events\";a:2:{i:0;a:7:{s:4:\"type\";s:8:\"wordcamp\";s:5:\"title\";s:15:\"WordCamp Europe\";s:3:\"url\";s:33:\"https://2019.europe.wordcamp.org/\";s:6:\"meetup\";s:0:\"\";s:10:\"meetup_url\";s:0:\"\";s:4:\"date\";s:19:\"2019-06-20 00:00:00\";s:8:\"location\";a:4:{s:8:\"location\";s:15:\"Berlin, Germany\";s:7:\"country\";s:2:\"DE\";s:8:\"latitude\";d:52.50697000000000258523868978954851627349853515625;s:9:\"longitude\";d:13.2843064000000001811940819607116281986236572265625;}}i:1;a:7:{s:4:\"type\";s:8:\"wordcamp\";s:5:\"title\";s:21:\"WordCamp Thessaloniki\";s:3:\"url\";s:38:\"https://2019.thessaloniki.wordcamp.org\";s:6:\"meetup\";N;s:10:\"meetup_url\";N;s:4:\"date\";s:19:\"2019-10-12 00:00:00\";s:8:\"location\";a:4:{s:8:\"location\";s:39:\"Thessaloniki, Central Macedonia, Greece\";s:7:\"country\";s:2:\"GR\";s:8:\"latitude\";d:40.60096630000000317295416607521474361419677734375;s:9:\"longitude\";d:22.959811699999999490273694391362369060516357421875;}}}}','no'),(135,'can_compress_scripts','1','no'),(136,'_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3','1560950153','no'),(137,'_transient_feed_9bbd59226dc36b9b26cd43f15694c5c3','a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:49:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"News – – WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"https://wordpress.org/news\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"WordPress News\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 19:42: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: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=5.3-alpha-45546\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:10:{i:0;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.2.2 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2019/06/wordpress-5-2-2-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 18:14:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6993\";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:348:\"WordPress 5.2.2 is now available! This maintenance release fixes 13 bugs and adds a little bit of polish to the Site Health feature that made its debut in 5.2. For more info, browse the full list of changes on Trac or check out the Version 5.2.2 documentation page. WordPress 5.2.2 is a short-cycle maintenance release. The next […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"marybaum\";s: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:3961:\"\n

WordPress 5.2.2 is now available! This maintenance release fixes 13 bugs and adds a little bit of polish to the Site Health feature that made its debut in 5.2.

\n\n\n\n

For more info, browse the full list of changes on Trac or check out the Version 5.2.2 documentation page.

\n\n\n\n

WordPress 5.2.2 is a short-cycle maintenance release. The next major release will be version 5.3; check make.wordpress.org/core for details as they happen.

\n\n\n\n

You can download WordPress 5.2.2 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

JB Audras, Justin Ahinon and Mary Baum co-led this release, with invaluable guidance from our Executive Director, Josepha Haden Chomphosy, and contributions from 30 other contributors. Thank you to everyone who made this release possible!

\n\n\n\n

Andrea Fercia, Andrew Duthie, Andrew Ozz, Andy Fragen, Birgir Erlendsson (birgire), Chetan Prajapati, David Baumwald, Debabrata Karfa, Garrett Hyder, Janki Moradiya, Jb Audras, jitendrabanjara1991, Jonathan Desrosiers, Jonny Harris, Jorge Costa, Justin Ahinon, Marius L. J., Mary Baum, Meet Makadia, Milan Dinić, Mukesh Panchal, palmiak, Pedro Mendonça, Peter Wilson, Rami Yushuvaev, Riad Benguella, sarah semark, Sergey Biryukov, Shashank Panchal, Tammie Lister, Tim Hengeveld, vaishalipanchal, vrimill, and William Earnhardt

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6993\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"The Month in WordPress: May 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/06/the-month-in-wordpress-may-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Jun 2019 10:21:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6987\";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:319:\"This month saw the 16th anniversary since the launch of the first release of WordPress. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6602:\"\n

This month saw the 16th anniversary since the launch of the first release of WordPress. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a significant global event.

\n\n\n\n
\n\n\n\n

Release of WordPress 5.2

\n\n\n\n

WordPress 5.2 “Jaco” was released on May 7 shipping some useful site management tools, such as the Site Health Check and PHP Error Protection, as well as a number of accessibility, privacy, and developer updates. You can read the field guide for this release for more detailed information about what was included and how it all works.

\n\n\n\n

327 individual volunteers contributed to the release. If you would like to be a part of that number for future releases, follow the Core team blog and join the #core channel in the Making WordPress Slack group.

\n\n\n\n

A Successful WordPress Translation Day 4

\n\n\n\n

WordPress Translation Day is a 24-hour event organised by the Polyglots team where community members from all over the world come together to translate WordPress into their local languages. For the fourth edition held on 11 May, 183 brand new contributors joined the Polyglots team from 77 communities across 35 countries in Africa, Asia, Europe, North America, South America, and Oceania.

\n\n\n\n

While the WP Translation Day is a great time for focussed contributions to localizing WordPress, but these contributions can happen at any time of the year, so if you would like to help make WordPress available in your local language, follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.

\n\n\n\n

Updated Plugin Guidelines Proposal

\n\n\n\n

The Plugins team has proposed some updates to the guidelines for developers on the Plugin Directory. The majority of the proposed changes are intended to address significant issues faced by developers who do not speak English as a first language, making the Plugin DIrectory a more accessible and beneficial place for everyone.

\n\n\n\n

The proposal will be open for comments until late June, so the community is encouraged to get involved with commenting on them and the direction they will take the Plugin Directory. If you would like to be involved in this discussion, comment on the proposal and join the #plugin review team in the Making WordPress Slack group.

\n\n\n\n

Continued Gutenberg Development

\n\n\n\n

Since the block editor was first released as part of WordPress Core in v5.0, development has continued in leaps and bounds with a new release every two weeks. The latest update includes some great incremental improvements that will be merged into the 5.2.2 release of WordPress along with the other recent enhancements.

\n\n\n\n

In addition to the editor enhancements, work has been ongoing in the Gutenberg project to bring the block editing experience to the rest of the WordPress dashboard. This second phase of the project has been going well and the latest update shows how much work has been done so far.

\n\n\n\n

In addition to that, the Block Library project that aims to bring a searchable library of available blocks right into the editor is deep in the planning phase with a recent update showing what direction the team is taking things.

\n\n\n\n

If you would like to get involved in planning and development of Gutenberg and the block editor, follow the Core and Design team blogs and join the #core, #design, and #core-editor channels in the Making WordPress Slack group.

\n\n\n\n
\n\n\n\n

Further Reading:

\n\n\n\n\n\n\n\n

Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6987\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.2.1 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2019/05/wordpress-5-2-1-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 19:04:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:5:\"5.2.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6976\";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:405:\"WordPress 5.2.1 is now available! This maintenance release fixes 33 bugs, including improvements to the block editor, accessibility, internationalization, and the Site Health feature introduced in 5.2. You can browse the full list of changes on Trac. WordPress 5.2.1 is a short-cycle maintenance release. Version 5.2.2 is expected to follow in approximately two weeks. You can download […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s: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:4923:\"\n

WordPress 5.2.1 is now available! This maintenance release fixes 33 bugs, including improvements to the block editor, accessibility, internationalization, and the Site Health feature introduced in 5.2.

\n\n\n\n

You can browse the full list of changes on Trac.

\n\n\n\n

WordPress 5.2.1 is a short-cycle maintenance release. Version 5.2.2 is expected to follow in approximately two weeks.

\n\n\n\n

You can download WordPress 5.2.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

Jonathan Desrosiers and William Earnhardt co-led this release, with contributions from 52 other contributors. Thank you to everyone that made this release possible!

\n\n\n\n

Alex Dimitrov, Alex Shiels, Andrea Fercia, Andrew Duthie, Andrew Ozz, Andrey “Rarst” Savchenko, Andy Fragen, anischarolia, Birgir Erlendsson (birgire), chesio, Chetan Prajapati, daxelrod, Debabrata Karfa, Dima, Dion Hulse, Dominik Schilling, Ella van Durpe, Emil Dotsev, ghoul, Grzegorz (Greg) Ziółkowski, gwwar, Hareesh, Ian Belanger, imath, Jb Audras, Jeremy Felt, Joen Asmussen, Jonathan Desrosiers, Jonny Harris, Josepha, jrf, kjellr, Marius L. J., MikeNGarrett, Milan Dinić, Mukesh Panchal, onlanka, paragoninitiativeenterprises, parkcityj, Peter Wilson, Presskopp, Riad Benguella, Sergey Biryukov, Stephen Edgar, Sébastien SERRE, Thorsten Frommen, Tim Hengeveld, Timothy Jacobs, timph, TobiasBg, tonybogdanov, Tor-Bjorn Fjellner, William Earnhardt, and Yui.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6976\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"Tomorrow is WordPress Translation Day 4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wordpress.org/news/2019/05/tomorrow-is-wordpress-translation-day-4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 May 2019 09:17: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:13:\"Documentation\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=6961\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:342:\"The fourth edition of WordPress translation day is coming up on Saturday 11 May 2019: tomorrow! Get ready for a 24-hour, global marathon dedicated to localizing the WordPress platform and ecosystem. This event takes place both online and in physical locations across the world, so you can join no matter where you are! The 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: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:3747:\"\n

The fourth edition of WordPress translation day is coming up on Saturday 11 May 2019: tomorrow! Get ready for a 24-hour, global marathon dedicated to localizing the WordPress platform and ecosystem. This event takes place both online and in physical locations across the world, so you can join no matter where you are!

\n\n\n\n

The WordPress Polyglots Team has a mission to translate and make available the software’s features into as many languages as possible. As WordPress powers more than 33% of websites, people from across the world use it in their daily life. That means there is a lot that needs translating, and into many different languages.

\n\n\n\n

On 11 May 2019, from 00:00 UTC until 23:59 UTC, WordPress Translation Day aims to celebrate the thousands of volunteers who contribute to translation and internalization. The event is also an opportunity for encouraging more people to get involved and help increase the availability of themes and plugins in different languages.

\n\n\n\n

“At the time of the last event in 2017, WordPress was being translated into 178 languages, we have now reached the 200 mark!”

WPtranslationday.org
\n\n\n\n

What happens on WordPress Translation Day?

\n\n\n\n

There are a number of local meetings all over the world, as well as online talks by people from the WordPress community. More than 700 people from around the world took part in past WordPress Translation Days, and everyone welcome to join in this time around!

\n\n\n\n

Everyone is welcome to join the event to help translate and localize WordPress, no matter their level of experience. A lot is happening on the day, so join in and you will learn how to through online sessions!

\n\n\n\n

What can you expect?

\n\n\n\n\n\n\n\n

A number of experienced WordPress translators and internationalization experts are part of the line-up for the livestream, joined by some first time contributors.

\n\n\n\n

Whether you have or haven’t contributed to the Polyglots before, you can join in for WordPress Translation Day. Learn more about both local and online events and stay updated through the website and social media.

\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6961\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"WordPress 5.2 “Jaco”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/news/2019/05/jaco/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 07 May 2019 21:03:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6925\";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:426:\"Version 5.2 of WordPress is available for download or update in your WordPress dashboard. New features in this update make it easier than ever to fix your site if something goes wrong. There are even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:31720:\"\n

Keeping Sites Safer

\n\n\n\n
\"\"
\n\n\n\n

Version 5.2 of WordPress, named “Jaco” in honor of renowned and revolutionary jazz bassist Jaco Pastorius, is available for download or update in your WordPress dashboard. New features in this update make it easier than ever to fix your site if something goes wrong.

\n\n\n\n

There are even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.

\n\n\n\n
\n\n\n\n

Site Health Check

\n\n\n\n
\"\"
\n\n\n\n

Building on the Site Health features introduced in 5.1, this release adds two new pages to help debug common configuration issues. It also adds space where developers can include debugging information for site maintainers.

\n\n\n\n
\n\n\n\n

PHP Error Protection

\n\n\n\n
\"\"
\n\n\n\n

This administrator-focused update will let you safely fix or manage fatal errors without requiring developer time. It features better handling of the so-called “white screen of death,” and a way to enter recovery mode,  which pauses error-causing plugins or themes.

\n\n\n\n
\n\n\n\n
\n\n\n\n

Improvements for Everyone

\n\n\n\n

Accessibility Updates

\n\n\n\n

A number of changes work together to improve contextual awareness and keyboard navigation flow for those using screen readers and other assistive technologies.

\n\n\n\n

New Dashboard Icons

\n\n\n\n

Thirteen new icons including Instagram, a suite of icons for BuddyPress, and rotated Earth icons for global inclusion. Find them in the Dashboard and have some fun!

\n\n\n\n

Plugin Compatibility Checks

\n\n\n\n

WordPress will now automatically determine if your site’s version of PHP is compatible with installed plugins. If the plugin requires a higher version of PHP than your site currently uses, WordPress will not allow you to activate it, preventing potential compatibility errors.

\n\n\n\n
\n\n\n\n

Developer Happiness

\n\n\n\n
\n
\n

PHP Version Bump

\n\n\n\n

The minimum supported PHP version is now 5.6.20. As of WordPress 5.2*, themes and plugins can safely take advantage of namespaces, anonymous functions, and more!

\n
\n\n\n\n
\n

Privacy Updates

\n\n\n\n

A new theme page template, a conditional function, and two CSS classes make designing and customizing the Privacy Policy page easier.

\n
\n
\n\n\n\n
\n
\n

New Body Hook

\n\n\n\n

5.2 introduces a wp_body_open hook, which lets themes support injecting code right at the beginning of the <body> element.

\n
\n\n\n\n
\n

Building JavaScript

\n\n\n\n

With the addition of webpack and Babel configurations in the wordpress/scripts package, developers won’t have to worry about setting up complex build tools to write modern JavaScript.

\n
\n
\n\n\n\n

*If you are running an old version of PHP (less than 5.6.20), update your PHP before installing 5.2.

\n\n\n\n
\n\n\n\n

The Squad

\n\n\n\n

This release was led by Matt Mullenweg, Josepha Haden Chomphosy, and Gary Pendergast. They were graciously supported by 327 generous volunteer contributors. Load a Jaco Pastorius playlist on your favorite music service and check out some of their profiles:

\n\n\nAaron D. Campbell, Aaron Jorbin, Adam Silverstein, Adam Soucie, Adil Öztaşer, Ajit Bohra, Alain Schlesser, Alda Vigdís, Alex Denning, Alex Dimitrov, Alex Kirk, Alex Mills, Alex Shiels, Alexis, Alexis Lloyd, allancole, Allen Snook, André, andraganescu, Andrea Fercia, Andrea Middleton, Andrei Lupu, Andrew Dixon, Andrew Duthie, Andrew Nacin, Andrew Ozz, Andrey \"Rarst\" Savchenko, Andrés Maneiro, Andy Fragen, Andy Meerwaldt, Aniket Patel, anischarolia, Anton Timmermans, Anton Vanyukov, Antonio Villegas, antonypuckey, Aristeides Stathopoulos, Aslam Shekh, axaak, Bego Mario Garde, Ben Dunkle, Ben Ritner - Kadence Themes, Benjamin Intal, Bill Erickson, Birgir Erlendsson, Bodo (Hugo) Barwich, bonger, Boone Gorges, Bradley Taylor, Brandon Kraft, Brent Swisher, Burhan Nasir, Cathi Bosco, Chetan Prajapati, Chiara Magnani, Chouby, Chris Van Patten, D.S. Webster, Damon Cook, Daniel Bachhuber, Daniel James, Daniel Llewellyn, Daniel Richards, Daniele Scasciafratte, Darren Ethier, Dave Whitley, DaveFX, davetgreen, David Baumwald, David Binovec, David Binovec, David Herrera, David Roddick, David Smith, Davide \'Folletto\' Casali, daxelrod, Debabrata Karfa, dekervit, Denis de Bernardy, Dennis Snell, Derek Herman, Derrick Hammer, designsimply, Dhanukanuwan, Dharmesh Patel, Diane, diegoreymendez, Dilip Bheda, Dima, Dion Hulse, Dixita Dusara, Dmitry Mayorov, Dominik Schilling, Drew Jaynes, dsifford, EcoTechie, Eduardo Toledo, Ella Van Durpe, Emil Dotsev, fabiankaegy, Faisal Alvi, Farhad Sakhaei, Felix Arntz, Franklin Tse, Fuegas, Garrett Hyder, Gary Jones, Gennady Kovshenin, ghoul, Girish Panchal, Grzegorz Ziółkowski, Guido Scialfa, GutenDev \"✍\"\"㊙\", gwwar, Hannah Malcolm, Hardik Amipara, Hardik Thakkar, Hendrik Luehrsen, Henry, Henry Wright, Hoover, Ian Belanger, Ian Dunn, ice9js, Igor Zinovyev, imath, Ixium, J.D. Grimes, jakeparis, James, janak Kaneriya, Janki Moradiya, Jarred Kennedy, Javier Villanueva, Jay Upadhyay, Jaydip Rami, Jaye Simons, Jayman Pandya, jdeeburke, Jean-Baptiste Audras, Jeff Paul, Jeffrey de Wit, Jenny Wong, Jeremy Felt, Jeremy Green, Jeremy Herve, jitendrabanjara1991, JJJ, Joe Dolson, Joe McGill, Joen Asmussen, Johan Falk, Johanna de Vos, John Blackbourn, Jonathan Desrosiers, Jonathandejong, joneiseman, Jonny Harris, jonnybojangles, Joost de Valk, jordesign, Jorge Bernal, Jorge Costa, Jory Hogeveen, Jose Castaneda, josephwa, Josh Feck, JoshuaWold, Joy, jplo, JR Tashjian, jrf, Juhi Patel, juliarrr, justinahinon, K. Adam White, KamataRyo, Karine Do, Katyatina, Kelin Chauhan, Kelly Dwan, Khokan Sardar, killua99, Kite, Kjell Reigstad, Knut Sparhell, Koji Kuno, Konstantin Obenland, Konstantinos Xenos, Kʜᴀɴ (ಠ_ಠ), laurelfulford, lkraav, lovingboth, Luke Carbis, Luke Gedeon, Luke Pettway, Maciej Palmowski, Maedah Batool, Maja Benke, Malae, Manzoor Wani, Marcin, Marcin Pietrzak, Marco Fernandes, Marco Peralta, Marcus Kazmierczak, marekhrabe, Marius Jensen, Mariyan Belchev, Mark Uraine, markcallen, Markus Echterhoff, Marty Helmick, marybaum, mattnyeus, mdwolinski, Meet Makadia, Mel Choyce, mheikkila, Micah Wood, michelleweber, Miguel Fonseca, Miguel Torres, Mikael Korpela, Mike Auteri, Mike Schinkel [WPLib Box project lead], Mike Schroder, Mike Selander, MikeNGarrett, Milan Dinić, mirka, Mobin Ghasempoor, Mohadese Ghasemi, Mohammed Saimon, Morten Rand-Hendriksen, Morteza Geransayeh, Muhammad Muhsin, Mukesh Panchal, Mustafa Uysal, mzorz, Nahid F. Mohit, Naoki Ohashi, Nate Allen, Ned Zimmerman, Neokazis Charalampos, Nick Cernis, Nick Diego, Nick Halsey, Nidhi Jain, Niels, Niels de Blaauw, Nikolay Nikolov, Nilambar Sharma, ninio, notnownikki, Oliver Sadler, onlanka, pandelisz, Pascal Birchler, Paul Bearne, Paul Biron, Pedro Mendonça, Peter Booker, Peter Wilson, pfiled, pilou69, Pranali Patel, Pratik, Pratik K. Yadav, Presskopp, psealock, Punit Patel, Rachel Cherry, Rahmon, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, Riad Benguella, Rinat Khaziev, Robert Anderson, Rudy Susanto, Ryan Boren, Ryan Welcher, Sébastien SERRE, Saeed Fard, Sal Ferrarello, Salar Gholizadeh, Samaneh Mirrajabi, Sami Keijonen, Samuel Elh, Santiago Garza, Sara Cope, saracup, sarah semark, Scott Arciszewski, Scott Reilly, Sebastian Pisula, Sekineh Ebrahimzadeh, Sergey Biryukov, SergioEstevao, sgastard, sharifkiberu, Shashank Panchal, shazdeh, Shital Marakana, sky_76, Soren Wrede, Stephen Edgar, Steven Word, Subrata Sarkar, Sudar Muthu, Sudhir Yadav, szepe.viktor, Takayuki Miyauchi, Tammie Lister, Themonic, thomstark, Thorsten Frommen, Thrijith Thankachan, Tim Hedgefield, Tim Wright, Timothy Jacobs, timph, tmatsuur, tmdesigned, tmdesigned, Tobias Zimpel, TobiasBg, TomHarrigan, tonybogdanov, Tor-Bjorn Fjellner, Toro_Unit (Hiroshi Urabe), torres126, Torsten Landsiedel, Towhidul Islam, Tracy Levesque, Umang Bhanvadia, Vaishali Panchal, vrimill, WebFactory, Weston Ruter, WFMattR, William \'Bahia\' Bay, William Earnhardt, williampatton, Willscrlt, Wolly aka Paolo Valenti, wrwrwr0, Yoav Farhi, Yui, Zebulan Stanphill, and Česlav Przywara.\n\n\n\n
\n\n\n\n

Also, many thanks to all of the community volunteers who contribute in the support forums. They answer questions from people across the world, whether they are using WordPress for the first time or since the first release. These releases are more successful for their efforts!

\n\n\n\n

If you want learn more about volunteering with WordPress, check out Make WordPress or the core development blog.

\n\n\n\n

Thanks for choosing WordPress!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6925\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"WordPress 5.2 RC2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/2019/05/wordpress-5-2-rc2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 May 2019 16:17:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6914\";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:326:\"The second release candidate for WordPress 5.2 is now available! WordPress 5.2 will be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time! There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s: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:2472:\"\n

The second release candidate for WordPress 5.2 is now available!

\n\n\n\n

WordPress 5.2 will be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time!

\n\n\n\n

There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).

\n\n\n\n

For details about what to expect in WordPress 5.2, please see the first release candidate post.

\n\n\n\n

This release includes the final About page design. It also contains fixes for:

\n\n\n\n\n\n\n\n

Plugin and Theme Developers

\n\n\n\n

Please test your plugins and themes against WordPress 5.2 and update the Tested up to version in the readme to 5.2. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.

\n\n\n\n

The WordPress 5.2 Field Guide has also been published, which details the major changes.

\n\n\n\n

How to Help

\n\n\n\n

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

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

It’s the start of May
and the release is coming.
We all give a cheer!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6914\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"The Month in WordPress: April 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2019/05/the-month-in-wordpress-april-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 02 May 2019 09:00:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6918\";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:324:\"This past month has been filled with anticipation as the community builds up towards a big new release, plans some important events, and builds new tools to grow the future of the project. WordPress 5.2 Almost Due for Release WordPress 5.2 is due for release on May 7 with many new features included for developers […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8386:\"\n

This past month has been filled with anticipation as the community builds up towards a big new release, plans some important events, and builds new tools to grow the future of the project.

\n\n\n\n
\n\n\n\n

WordPress 5.2 Almost Due for Release

\n\n\n\n

WordPress 5.2 is due for release on May 7 with many new features included for developers and end-users alike. The Field Guide for the release provides a lot of information about what is in it and what you can expect, including a few key elements:

\n\n\n\n

Site Health Check

\n\n\n\n

One of the most highly anticipated features for v5.2 is the Site Health Check. This feature adds two new pages in the admin interface to help end users maintain a healthy site through common configuration issues and other elements that go along with having a robust online presence. It also provides a standardized location for developers to add debugging information.

\n\n\n\n

Fatal Error Recovery Mode

\n\n\n\n

The Fatal Error Recovery Mode feature was originally planned for the 5.1 release but was delayed to patch up some last-minute issues that arose. This feature will help site-owners recover more quickly from fatal errors that break the display or functionality of their site that would ordinarily require code or database edits to fix.

\n\n\n\n

Privacy and Accessibility Updates

\n\n\n\n

Along with the headlining features mentioned above, there are some important enhancements to the privacy and accessibility features included in Core. These include some important developer-focused changes to how privacy policy pages are displayed and user data is exported, as well as moving to more semantic markup for admin tabs and other improvements such as switching post format icons to drop-down menus on post list tables, improved admin toolbar markup, and contextual improvements to archive widget drop-down menu.

\n\n\n\n

New Dashicons

\n\n\n\n

The Dashicons library was last updated was over 3 years ago. Now, in the upcoming release, a set of 13 new icons will be added to the library along with improvements to the build process and file format of the icons.

\n\n\n\n

Block Editor Upgrades

\n\n\n\n

The Block Editor has seen numerous improvements lately that will all be included in the v5.2 release. Along with the interface upgrades, the underlying Javascript module has been reorganized, improvements have been made to how the block editor is detected on the post edit screen, and the Javascript build process has been enhanced.

\n\n\n\n

WordPress 5.2 is now in the Release Candidate phase and you can test it by installing the Beta Tester plugin on any WordPress site.

\n\n\n\n

Want to get involved in building WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group.

\n\n\n\n

WordPress Translation Day 4 is Almost Here

\n\n\n\n

On 11 May 2019, the fourth WordPress Translation Day will take place. This is a 24-hour global event dedicated to the translation of all things WordPress, from Core to themes, plugins to marketing.

\n\n\n\n

Over the course of 24 hours, WordPress communities will meet to translate WordPress into their local languages and watch talks and sessions broadcast on wptranslationday.org. During the previous WordPress Translation Day, 71 local events took place in 29 countries, and even more communities are expected to take part this time.

\n\n\n\n

Want to get involved in WordPress Translation Day 4? Find out how to organize a local event, follow the updates on the Polyglots team blog, and join the #polyglots channel in the Making WordPress Slack group.

\n\n\n\n

Block Library Project Gets Started

\n\n\n\n

Since the initial proposal for a Block Library that would be made available from inside the block editor, work has been done to put together some designs for how this would look. Since then the project has received a more direct focus with a planned out scope and timeline.

\n\n\n\n

The project is being managed on GitHub and people interested in contributing are encouraged to get involved there. You can also keep up to date by following the Design team blog and joining the #design channel in the Making WordPress Slack group.

\n\n\n\n
\n\n\n\n

Further Reading:

\n\n\n\n\n\n\n\n

Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6918\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"WordPress 5.2 Release Candidate\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/04/wordpress-5-2-release-candidate/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 26 Apr 2019 01:28:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6909\";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:364:\"The first release candidate for WordPress 5.2 is now available! This is an important milestone as we progress toward the WordPress 5.2 release date. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.2 is scheduled to […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s: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:3117:\"\n

The first release candidate for WordPress 5.2 is now available!

\n\n\n\n

This is an important milestone as we progress toward the WordPress 5.2 release date. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.2 is scheduled to be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time!

\n\n\n\n

There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).

\n\n\n\n

What’s in WordPress 5.2?

\n\n\n\n

Continuing with the theme from the last release, WordPress 5.2 gives you even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.

\n\n\n\n

The Site Health Check and PHP Error Protection tools have brand new features, giving you peace of mind if you discover any issues with plugins or themes on your site. There are also updates to the icons available in your dashboard, fresh accessibility considerations for anyone using assistive technologies and more.

\n\n\n\n

Plugin and Theme Developers

\n\n\n\n

Please test your plugins and themes against WordPress 5.2 and update the Tested up to version in the readme to 5.2. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.

\n\n\n\n

The WordPress 5.2 Field Guide has also been published, which goes into the details of the major changes.

\n\n\n\n

How to Help

\n\n\n\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.2 release schedule.

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

Howdy, RC 1!
With tools this interesting,
I can hardly wait.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6909\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.2 Beta 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2019/04/wordpress-5-2-beta-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 12 Apr 2019 21:33:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6885\";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:316:\"WordPress 5.2 Beta 3 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. There are two ways to test the latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s: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:4391:\"\n

WordPress 5.2 Beta 3 is now available!

\n\n\n\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

\n\n\n\n

There are two ways to test the latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

\n\n\n\n

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 2, nearly 40 tickets have been closed since then. Here are the major changes and bug fixes:

\n\n\n\n\n\n\n\n

Minimum PHP Version Update

\n\n\n\n

Important reminder: as of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

\n\n\n\n
\n\n\n\n

Developer Notes

\n\n\n\n

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

\n\n\n\n

How to Help

\n\n\n\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 3 release also marks the soft string freeze point of the 5.2 release schedule.

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

Would you look at that
each day brings release closer
test to be ready
.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6885\";s: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:54:\"\n \n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.2 Beta 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2019/04/wordpress-5-2-beta-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Apr 2019 01:27: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:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.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:34:\"https://wordpress.org/news/?p=6874\";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:312:\"WordPress 5.2 Beta 2 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. There are two ways to test the WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Gary Pendergast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4565:\"\n

WordPress 5.2 Beta 2 is now available!

\n\n\n\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

\n\n\n\n

There are two ways to test the WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

\n\n\n\n

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 1, nearly 100 tickets have been closed since then. Here are the major changes and bug fixes:

\n\n\n\n\n\n\n\n

Minimum PHP Version Update

\n\n\n\n

As of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

\n\n\n\n
\n\n\n\n

Developer Notes

\n\n\n\n

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

\n\n\n\n

How to Help

\n\n\n\n

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

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

The wonderful thing
about betas, is betas
are wonderful things.
\"?\"

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6874\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n 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:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Wed, 19 Jun 2019 01:15:53 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, 18 Jun 2019 19:42:02 GMT\";s:4:\"link\";s:63:\"; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";}}s:5:\"build\";s:14:\"20130911073210\";}','no'),(138,'_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1560950153','no'),(139,'_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1560906953','no'),(140,'_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9','1560950154','no'),(141,'_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:42:\"WPTavern: WordPress 5.2.2 Squashes 13 Bugs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90869\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wptavern.com/wordpress-5-2-2-squashes-13-bugs\";s: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:1305:\"

WordPress 5.2.2 dubbed a short-cycle maintenance release is available for download. This release addresses 13 bugs and improves the Site Heath features introduced in 5.2.

\n\n\n\n

One of the changes in 5.2.2 affects the theme update link in the Customizer of multisite installs. The update link for themes on multisite installs in the Customizer has been removed. This is because updates can not be performed from within the Customizer in this situation.

\n\n\n\n

Other changes include, adding a exit recovery mode button in the responsive view, making the Site Health page access filterable, and updates to the page editor packages.

\n\n\n\n

JB Audras, Justin Ahinon and Mary Baum co-led the release with guidance from Executive Director, Josepha Haden. Thirty people contributed to WordPress 5.2.2.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 21:24:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:55:\"WordPress.org blog: WordPress 5.2.2 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=6993\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpress.org/news/2019/06/wordpress-5-2-2-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:3947:\"

WordPress 5.2.2 is now available! This maintenance release fixes 13 bugs and adds a little bit of polish to the Site Health feature that made its debut in 5.2.

\n\n\n\n

For more info, browse the full list of changes on Trac or check out the Version 5.2.2 documentation page.

\n\n\n\n

WordPress 5.2.2 is a short-cycle maintenance release. The next major release will be version 5.3; check make.wordpress.org/core for details as they happen.

\n\n\n\n

You can download WordPress 5.2.2 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

JB Audras, Justin Ahinon and Mary Baum co-led this release, with invaluable guidance from our Executive Director, Josepha Haden Chomphosy, and contributions from 30 other contributors. Thank you to everyone who made this release possible!

\n\n\n\n

Andrea Fercia, Andrew Duthie, Andrew Ozz, Andy Fragen, Birgir Erlendsson (birgire), Chetan Prajapati, David Baumwald, Debabrata Karfa, Garrett Hyder, Janki Moradiya, Jb Audras, jitendrabanjara1991, Jonathan Desrosiers, Jonny Harris, Jorge Costa, Justin Ahinon, Marius L. J., Mary Baum, Meet Makadia, Milan Dinić, Mukesh Panchal, palmiak, Pedro Mendonça, Peter Wilson, Rami Yushuvaev, Riad Benguella, sarah semark, Sergey Biryukov, Shashank Panchal, Tammie Lister, Tim Hengeveld, vaishalipanchal, vrimill, and William Earnhardt

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 18:14:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"marybaum\";s: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:44:\"WPTavern: In Case You Missed It – Issue 26\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90840&preview=true&preview_id=90840\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/in-case-you-missed-it-issue-26\";s: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:7430:\"

photo credit: Night Moves – (license)

\n

There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.

\n

Birgit Olzem Could Use the Community’s Help

\n

Birgit Olzem has encountered some financial hard times due to multiple illnesses and paying for acupuncture treatments and osteopathic therapy which are not covered by her insurance. Olzem fell ill earlier this year which prevented her from generating income as a self-employed person.

\n
\n

Dear #WordPress community!

\n

Today I turn to you with a request that I find very difficult to make. \"?\"

\n

Over the last 7 years, I\'ve invested a lot of time and money in the contributions for WordPress. Despite five children, part-time jobs and chronic diseases. #Thread

\n

— Birgit Olzem (@CoachBirgit) June 13, 2019

\n

\n
\n

If my contributions to #WordPress have helped in any way over the years, or you just like me as a person, I\'d be happy if you would help me become healthy again.https://t.co/wfmJ3WOXMn

\n

My eternal thanks will come to you. \"?\"

\n

7/7 pic.twitter.com/i98dU1EC1S

\n

— Birgit Olzem (@CoachBirgit) June 13, 2019

\n

\n

Olzem has translated WordPress, compiled release packages for de_DE, organized Meetups, WordCamps, answered support questions and has been part of different make/WordPress teams, some of them as a team-rep. She’s also contributed to WordCamps as a Speaker, Volunteer and Contributor day team-lead.

\n

To learn more about her story and to donate, please read her request to the community.

\n

Liam Dempsey’s Take on Gutenberg

\n

Liam Dempsey describes what he likes and doesn’t like about the new WordPress editor.

\n

Defending the Right to Publish Open Source Software in the UK

\n

The EFF and Open Rights Group have submitted comments to the UK government defending the right to publish open source software.

\n

Moreover, source code is a form of written creative expression, and open source code is a form of public discourse. Regulating its publication under anti-money-laundering provisions fails to honor the free expression rights of software creators in the United Kingdom, and their collaborators and users in the rest of the world.

\n

Why Is It Important to Give Back to Open Source?

\n

JC Mae Palmes on Twitter asked, why is it important to give back to the WordPress community? Here are a few responses. To see all of the responses, check out this Twitter thread. 

\n
\n

WordPress powers 34% of the web, it\'s a career advantage, the community is awesome, the product is used by students and enterprises alike, you can directly talk to incredibly knowledgeable people and learn a ton

\n

— Mario Peshev (@no_fear_inc) June 13, 2019

\n

\n
\n

Open Source projects live and die by the willingness of those who benefit from the project giving back to the project.

\n

— Morten i Danmark \"??\" (@mor10) June 13, 2019

\n

\n
\n

You realize you’re not alone. The mistakes you make are normal, that everyone’s figuring it out as they go. It gives you access to experience at all levels and people to brainstorm with who have unique perspectives.

\n

— Cate DeRosia (@mysweetcate) June 13, 2019

\n

\n

WordCamp US Speaker Selection Process

\n

If you’re wondering how speakers are being selected for WordCamp US this year, check out this post by the Programming Team. The team is using a new process that includes, limiting the number of submissions per speaker to two instead of unlimited, reviewing submissions based on the organizer’s sphere of experience, and using blind reviews. Speakers who are chosen are scheduled to be notified by the end of this month.

\n

An Easy Way to Make an Impact in The WordPress Community

\n

David Bisset shared the following idea on Twitter and while a few companies have started doing this, I think it will catch on with individuals more than businesses.

\n
\n

Are you a company that wants to make an impact in the #WordPress space but doesn’t have alot of $$$?

\n

Buy some tickets for people to attend WordCamps. Especially people (youths, non-profits, not privileged) that wouldn’t normally consider going.

\n

— David Bisset (@dimensionmedia) June 14, 2019

\n

\n

That’s it for issue twenty-six. If you recently discovered a cool resource or post related to WordPress, please share it with us in the comments.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jun 2019 22:06: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: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:67:\"WPTavern: Justin Tadlock Proposes Idea to Solve Common Theme Issues\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90725\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/justin-tadlock-proposes-idea-to-solve-common-theme-issues\";s: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:2119:\"

The Theme Review Team has been discussing ideas in Slack on how to solve the problem of themes in the review queue suffering from common theme issues. Just Tadlock has proposed a idea he calls Theme Feature Repositories.

\n\n\n\n

The idea is to create standardized packages on the Theme Review Team GitHub repo that authors could use in their themes. If enough people bought into the idea and worked together, it would lessen the pain points between reviewers and theme authors. It would also decrease the amount of code written by hundreds of different authors to solve a common problem.

\n\n\n\n

Tadlock used Admin notices and Links to ‘Pro’ versions as two examples that could benefit from this approach. Packages would handle specific use cases and be installed using Composer. For those who don’t use composer, an autoloader would be provided as well as a .zip file that could be dropped into a theme.

\n\n\n\n

Tadlock is asking the theme community what packages do they need or what common problems could be solved together.

\n\n\n\n

“This can literally be any common feature in WordPress themes, not just admin or customizer-related things,” Tadlock said. “Nothing is ‘out of bounds’. Every idea is on the table right now.

\n\n\n\n

“This is an ambitious project. It’d require cooperation between authors and reviewers for the betterment of the theme directory as a whole. It’ll only work if we have buy-in from everyone.”

\n\n\n\n

Tadlock also mentioned that due to his schedule, he will be unable to lead or co-lead the project and is seeking people interested in taking on these roles. Those interested should have knowledge of Git, Composer, and Object-oriented programming.

\n\n\n\n

If you’re interested in this project or want to provide feedback, you can leave a comment on the proposal.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 21:07: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: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:106:\"WPTavern: WordPress Spanish Translation Team Now has Meta Sites, Apps, and Top 200 Plugins 100% Translated\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90804\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/wordpress-spanish-translation-team-now-has-meta-sites-apps-and-top-200-plugins-100-translated\";s: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:5640:\"

The Spanish WordPress community hit a remarkable milestone with translations this week. Polyglots volunteers have now translated the meta sites, WordPress apps, and the top 200 plugins at 100% completion, with no pending translations to review.

\n
\n

La comunidad #WordPress España @wp_es sigue batiendo récords.

\n

No solo no hay traducciones pendientes de revisar, sino que tiene siempre traducido al 100% WordPress, sitios meta, aplicaciones y, ahora, también al 100% el Top 200 Plugins.

\n

Únete al equipo: https://t.co/ymTyKpvt7L pic.twitter.com/6OtoQHwVoA

\n

— WordPress España (@wp_es) June 10, 2019

\n

\n

The size of the team is a major factor in reaching this milestone. According to stats Naoko Takano shared at WordPress Translation Day 4 last month, Spanish is the locale with the most translation contributors (2,863), followed by German (2,399), Italian (2,190), Dutch (1,584), and Russian (1,515). It is also one of the top non-English locales installed, with 5.0% of all WordPress sites using the translation. WordPress.com reports similar numbers, where Spanish is the second most popular language for blogs at 4.7%.

\n

Rocío Valdivia, a Community Wrangler at WordCamp Central who lives in Spain, gave us a look at what is behind the team’s extraordinary growth and momentum. She identified several key factors that have contributed to their success in working efficiently and sharing useful information among team members during the past 2-3 years.

\n

“We created a Slack instance some years ago, but at the beginning it was common for people to join and ask for support questions,” Valdivia said. “Now we have some protocols: the general channel is an only-read channel. If someone ask for support, we send them with a kind predef to the es.wordpress.org forums, where they get answers in a few hours. There are no questions in the forums waiting for longer than six hours ever, as we have a very active support team that coordinates in the #support channel of our Slack.”

\n

Valdivia said that removing the noise of support requests has given the team very productive channels for translations, plugin and theme translations, meetups (where Meetup organizers share tips and resources using a shared Google drive folder), and WordCamps (where WC organizers share info, tips, answer questions in Spanish, and share resources like email templates.)

\n

“Besides all of this, we’ve worked very well passing the philosophy of the project to the new members from the most experienced ones,” Valdivia said. “For example, people do very soft transitions from one lead organizer to the next one.”

\n

Although some WordCamp attendees have complained in the past that not much is accomplished at Contributor Days, the Spanish community has had success using these opportunities to transfer knowledge to new leaders and contributors. The community hosted 10 WordCamps in 2018 and Valdivia estimates they will have 9-10 in 2019. WordCamp Barcelona 2018 and 2019 had 400 attendees and 180 people at their Contributor Days. WC Irun 2019 had 220 attendees and 100 participants at Contributor Day. WordCamp Madrid 2019 sold out with 600 attendees and approximately 200 participated in Contributor Day.

\n

Although the Spanish community has experienced contributors across several WordPress.org teams, such as WPTV, Community, Support, and Polyglots, Valdivia said they are a bit thin on Core contributors.

\n

“We’re lacking people with experience contributing frequently to Core,” Valdivia said. “We have some of them who have contributed several times, but still need more people with more involvement to be able to pass all this info to newcomers.”

\n

Strong local meetups are another factor in the Spanish community’s success at keeping translations up-to-date. In addition to the largest team of translators in the world of WordPress, Spain has the second highest number of meetup groups and events per month. Spain is running 64 local meetups, with a population of 46 million people, compared to 201 groups in the U.S., which has 7x the population size (327 million).

\n

\n

“The language barrier has been an issue for years, as not everyone speaks English and not everyone feels confident following conversations in English,” Valdivia said. “So, being able to train our own teams of contributors in our own language and having our own shared resources and channels, has been very useful.”

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 20:22: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: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:105:\"WPTavern: WPWeekly Episode 356 – Gutenberg, Governance, and Contributing to WordPress with Jonny Harris\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90817&preview=true&preview_id=90817\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/wpweekly-episode-356-gutenberg-governance-and-contributing-to-wordpress-with-jonny-harris\";s: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:1955:\"

In this episode, John James Jacoby and I are joined by Jonny Harris. Jonny describes how he discovered WordPress and some of the core projects he’s been working on including, Site Health Checks, fatal error protection, and Multisite. We discuss WordPress’ focus on users vs developers in recent years, Jonny’s experience contributing to core, and his thoughts on a WordPress governance model.

\n

Stories Discussed:

\n

WordPress Is Borked So Enjoy This Glorious Plant That’s Taking Over the Internet

\n

WP Engine Launches DevKit Open Beta

\n

Drupal Gutenberg 1.0 Released, Now Ready for Production Sites

\n

BuddyPress 5.0 to Update Password Control to Match WordPress

\n

Transcript:

\n

Episode 356 Transcript

\n

WPWeekly Meta:

\n

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

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #356:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 20:08:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"WPTavern: Pika Project Launches New JavaScript CDN to Serve Modern, ESM Packages\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90762\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/pika-project-launches-new-javascript-cdn-to-serve-modern-esm-packages\";s: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:7138:\"

\n

Fred Schott, a software developer and former Google employee on the Polymer team, has launched a new CDN for his Pika project. Schott’s mission with Pika is “to make modern JavaScript more accessible by making it easier to find, publish, install, and use modern packages on npm.” Pika provides a searchable catalog of “module” packages available on npm – packages that use the more compact ES module syntax (ESM), which result in smaller Javascript bundles.

\n

npm currently lists 59,851 ES modules. This makes up approximately 7% of total packages on npm are exporting an ES module, but the number is steadily increasing:

\n

\n

Pika makes it easy to search for these packages and the results will only include those that have a defined “module” entry point in their package.json manifest. Each listing consolidates the relevant information on one page, highlighting the important details.

\n

\n

One of the chief advantages of using ES modules is that they run natively on the web, without the need for a bundler. In a post titled “A Future Without Webpack,” Schott contends that JavaScript developers are “so steeped in the world of bundlers” that they overlook the possibilities of using ESM dependencies that run directly on the web:

\n

Over the last several years, JavaScript bundling has morphed from a production-only optimization into a required build step for most web applications. Whether you love this or hate it, it’s hard to deny that bundlers have added a ton of new complexity to web development – a field of development that has always taken pride in its view-source, easy-to-get-started ethos.

\n

@pika/web is an attempt to free web development from the bundler requirement. In 2019, you should use a bundler because you want to, not because you need to.

\n

Schott created @pika/web to make it easy for developers to use ES modules, even when they don’t have compatible dependencies. It provides an install-time tool that is not exactly a build tool or a bundler but works to output web-native npm dependencies into a single ESM .js file:

\n

@pika/web checks your package.json manifest for any “dependencies” that export a valid ESM “module” entry point, and then installs them to a local web_modules/ directory. @pika/web works on any ESM package, even ones with ESM & Common.js internal dependencies.

\n

Installed packages run in the browser because @pika/web bundles each package into a single, web-ready ESM .js file. For example: The entire “preact” package is installed to web_modules/preact.js. This takes care of anything bad that the package may be doing internally, while preserving the original package interface.

\n

Here’s a demo of how that works:

\n
\n

¡OJO con @pika/web! \"?\"\"⚡\"

\n

\"?\" Instala tus dependencias npm y úsalas directamente en el navegador.
\"✨\" Sin bundlers, ni configuraciones de ningún tipo.
\"⚡\" Nativo, ESM, optimizado para http2… ¡y MUY rápido!

\n

¡Muy pronto, vídeo más completo y artículo en https://t.co/uc7bPEkbXB \"?‍?\"! pic.twitter.com/cdNWqBnrDc

\n

— Miguel Ángel Durán \"?‍?\" (@midudev) March 2, 2019

\n

\n

This week Schott announced the availability of a new Pika CDN for delivering modern ES module packages. It uses the pikapkg/web package builder to work with any ESM package and the CDN will automagically handle any non-ESM dependencies of that package. Pika CDN automatically detects the visitor’s browser and serves JS that is optimized to the environment, eliminating polyfills and transpiler bloat wherever possible.

\n

\n

“Pika CDN leverages your browser’s natural caching abilities to give your pages faster dependency load times, especially on first visit,” Schott said. “0ms first-loads are even possible (for your dependencies at least) if all packages have been seen before.

\n

“With our CDN, package authors can distribute more modern, unminified packages without worrying about how to serve them directly. Instead, our nifty package-builder automatically resolves each package — and any legacy sub-dependencies — into a single, minified, ready-to-import JavaScript file.”

\n

Schott recently left his position at Ripple to work full-time on Pika, a project that he believes will move the JavaScript ecosystem forward.

\n

“Leaving my team was one of the hardest decisions I’ve ever made, but I know that I’m needed here,” he said. “I’m so excited to be a part of the future of the web, whatever it ends up looking like.”

\n

Pika is looking for corporate sponsors. For now, Schott is funding the server costs using Patreon.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 15:54:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:96:\"WPTavern: Gutenberg 5.9 Brings Major Improvements to Block Grouping, Introduces Snackbar Notices\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90747\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"https://wptavern.com/gutenberg-5-9-brings-major-improvements-to-block-grouping-introduces-snackbar-notices\";s: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:2988:\"

Gutenberg 5.9 is now available for those who are running the plugin to get the latest features on their sites. This release brings significant improvements to the grouping capabilities, allowing users to group and ungroup blocks inside a container block. Once placed inside a group, the blocks can be moved up or down within the group using simple up/down controls.

\n

\n

Nested blocks have also been improved so that users can click through to each layer to configure each and navigate to the deepest nested block.

\n

Gutenberg 5.9 introduces “Snackbar” notices to communicate completed actions in the block editor UI that do not require further action.

\n

The term “Snackbar” doesn’t adequately describe the way these notices behave. The concept was inspired by Material design and is traditionally used for providing brief messages about app processes at the bottom of the screen. Gutenberg’s new Snackbars pop up and disappear after a short delay, so the notice doesn’t have to be dismissed.

\n

“For a distraction-free experience, all the notices used in the editor to inform about the post saving/publishing, reusable blocks creation and updates have been updated to use this new type of notice,” Gutenberg Phase 2 lead Riad Benguella said. He posted a gif demonstrating Snackbar notices in action:

\n

\n

This release brings several visual enhancements to blocks and UI components, including a redesign of the Table block placeholder, refactoring and consolidation of dropdown menus, and improvements the output of the Spacer block.

\n

Gutenberg 5.9 contains more than two dozen fixes for bugs found in both desktop and mobile experiences. The editor took a slight dip in performance from the previous version, going from 4.8 to 4.9 seconds in loading time and 62.8ms to 66.3ms for keypress events. More than 40 people contributed to this release and approximately 15% were new contributors.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jun 2019 18:54:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"HeroPress: My “Hero’s Journey” Through the Dark Underworld of WordPress Hosting\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=2862\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:204:\"https://heropress.com/essays/my-heros-journey-through-the-dark-underworld-of-wordpress-hosting/#utm_source=rss&utm_medium=rss&utm_campaign=my-heros-journey-through-the-dark-underworld-of-wordpress-hosting\";s: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:22301:\"\"Pull

The following is an expanded and updated version of my presentation at WordCamp Salt Lake City 2017.

\n

My girls love Moana. Especially when it first came to video and they could watch it every day… or two or three times a day if mom wasn’t feeling good or catching up on sleep from being up with baby brother the night before.

\n

There’s this strange part of that movie where Moana follows Maui to a place under the ocean called “The Realm of Monsters.” It’s where monsters go after being killed. If you have younger kids, you know what I’m talking about. If you don’t have kids, it’s when the giant crab sings the song “Shiny.”

\n

\n

One common theme in myths, legends, and ancient religious writings, is where the hero visits the underworld, aka “afterlife” or “hell.” There they experience a symbolic or actual death for themselves or a loved one. Often through conquering a monster who is the Lord of the Underworld, they then re-emerge with their loved one, new knowledge and power, and/or some object to help them on their quest.

\n

The film Moana clearly plays out this theme. She and Maui emerge triumphant from the realm of monsters, having defeated the giant crab by flipping it on its back and retrieving Maui’s magical hook.

\n

In Return of the Jedi, Luke descends to the underworld of Jabba’s Palace. There, he’s able to bring his friend Han Solo back from a virtual death, defeat the Rancor, kill Jabba the Hut (lord of the criminal underworld), save the princess, and retrieve his lightsaber. All this happens before we see even one single, fuzzy, cute, unblinking Ewok…. Unless you believe in the “special editions,” in which case the Ewoks blink.

\n

\n

There are many movies, books, stories, mythologies, etc that all follow similar patterns.

\n

Like Maui’s hook or Luke’s lightsaber, in these stories the hero often emerges from the underworld with newfound knowledge and/or a powerful object. Briefly, I’d like to take you on my own personal “Hero’s Journey” to the dark underworld of WordPress hosting. Along with it my quest of building a business on WordPress and hosting, with its own mythical monsters to slay, trials to be conquered, riddles to be solved, and ultimately new knowledge and weapons gained.

\n

The Call to Adventure

\n

In the early days of my business, Fiddler Online (now called WordXpress), I envisioned building websites for companies on WordPress, then charging a monthly fee to maintain, support, edit, update, and manage them. I got started with a few clients and wanted to grow.

\n

I’d trusted someone to set me up with a very inexpensive VPS on unmanaged hosting. He was supposed to do the managing and ensure it all ran smoothly. I quickly learned you get what you pay for! Soon our members’ sites started going offline, usually all at once as the VPS crashed from one problem or another. It wasn’t just the server being down that caused problems. It was also corrupting data and other strange and scary things that I’d never encountered before, such as the body content of posts and pages being cut off, starting with the first special character that appeared in the content (a database issue).

\n

\n

These were dark and scary monsters to battle. I knew cPanel pretty well, but the APACHE stack that ran beneath it was mostly a mystery to me. So was database encoding and other advanced technical realms that all have an impact on the server, WordPress, and ultimately our clients’ businesses.

\n

The monsters appeared, seemingly determined to kill my small and struggling business, shortly after the birth of our first child. I was frequently up all night working with “Todd” the server guy (we’ll call him) to try and get the websites back online. We’d vanquish one monster, rest a day or so, and find another had taken some sites down again.

\n

After a few weeks of constant frustration, I said “enough” and signed up for a Hostgator reseller plan. This was back when they were an independent hosting company. On this new plan I could install as many cPanel’s as I needed and manage each separately! I thought it was wonderful and would solve all my problems. Hostgator transferred all our sites from the terrible VPS hosting we’d been on to their servers and I thought perhaps that was it!

\n

I thought my quest was over. I’d fought the monsters and won.

\n

Scary as it was, it had been relatively brief. I’d learned a lot, but felt like I’d been to the underworld and back!

\n

The Illusion of Safety

\n

Unfortunately, the wraiths had cast a spell over me, blinding me to the fact that they were still lurking in the shadows. When transferring our WordPress websites to our new account, Hostgator had copied each entire cPanel over from the VPS. This eliminated the underlying problems in the APACHE stack on that horrible VPS, but brought with it the fiends that had infiltrated cPanel and even our WordPress websites. To be clear: they weren’t infected with any kind of malware, but configuration problems, cruft, and who knows what else, caused some really bad results.

\n

With my new spellbound, but misled confidence, I pushed our business forward. I brought on a business partner, Kurt as the sales guy. Later we acquired another website company. Through all that, we’d learned a lot, and doing okay for that stage, but still struggled financially as we bootstrapped this new business from nothing.

\n

When we acquired this other business, they’d been running all their client’s sites on WordPress Multisite. It seemed like a great idea because of how it allowed us to manage all the websites in one place.

\n

Despite the progress the business made, the monstrosities emerged again and this time with higher stakes since our business had grown and was now managing many more websites. These monsters emerged partly from what had been transferred over with cPanel, and the difficulties of running a large Multisite where each child site had its own theme, plus the weight of adding more and more websites and traffic to hosting that was really just shared hosting with WHM access and more control.

\n

\n

The Plunge Into the Underworld

\n

In each hero’s journey, there’s often a wizard or goddess that helps guide and mentor the hero along his journey. I eventually made friends with a great guy we’ll call Sam. He ran his own hosting company with data centers and a great support staff. Sam was somewhat like Obi-Wan, Merlin, or Maui in these stories: he was my mentor and companion on my adventures into the underworld that followed. He made a great guide, because he’d been there before. Unfortunately, his own journey had never taken him to some of the deepest darkest places we would soon encounter.

\n

So we moved to Sam’s hosting, where he kindly watched things closely and provided a server admin’s perspective and advice at a much lower price than he would have normally charged.

\n

It wasn’t long before the demons, wraiths, monsters, and other ghouls started crawling from the darkness. It started with random downtime. Then followed strange limitations on websites. Next emails were not getting delivered. Then it was slowness. Now we were hacked… or were we? Suddenly all the contents of all pages and posts were cut off (we thought we killed this monster before)! Then email wasn’t being sent. Next our server is sending spam email. Now a hard drive is dying. It just kept going and going. Many of these demons were completely new to Sam and his very experienced team.

\n

It didn’t take long before there were whisperings of “the Fiddler curse.” This curse referred to Fiddler Online the name of our company. The hosting support team joked that we were cursed. All kinds of issues arose that they’d never seen before, and with a frequency they’d never experienced either.

\n

When a car crashed into the data center’s power regulation center during a freak storm, it cut off power from the normal power lines, as well as from their automatic backup power supply! It completely took the data center offline. The “Fiddler curse” was in full force.

\n

Or put better, we were in the deepest, darkest, part of the underworld, locked in an all-out battle with the worst demons and wraiths it had to send against us.

\n

We tried method after method to defeat the monsters. We tried rebuilding the server stacks. We tried various WordPress optimizations. We bought our own server and had it installed in their data center. We even tried a totally different Linux stack and something called Interworx, a cPanel alternative, that came with load balancing and real-time backup. But no matter how much money, time, and knowledge we threw at it, the issues continued. No matter how many monsters we slew, we were still losing the war.

\n

The “Real World” Dragons

\n

When I recently asked my wife Jill about that time of our lives, she said:

\n

“From my perspective, it was hard to know when to throw in the towel and say ‘enough’ because it’s just not working. Getting the hosting sorted out totally changed the entire dynamic and perspective of doing our own business. Before that, it felt like we were building a dream on a crumbling foundation.”

\n

\n

And don’t get the wrong idea from this image. Jill was no damsel in distress. She’s a warrior too. I’d have never completed this quest without her there, fighting alongside me. She may have not fought the technical fiends, but there were plenty other monsters in the form of financial struggles, moves, and difficult situations that arose from my unavailability, our lack of money, and more.

\n

This was all a lot like battling the Hydra of Lerna: we’d cut off one head, and two would grow back in its place. We’d take a breather for a week, and then here came the wraiths!

\n

The stress of it all exacerbated a gallstone problem I had. Because of a misdiagnosis, I thought it was something there was no solution for. So even when I wasn’t up in the middle of the night battling monsters demons of the hosting underworld with Sam, I was often awake at night in massive amounts of pain as my gallbladder tried to pass gigantic gallstones. So even then, I’d be sleeping the next day when I needed to be designing websites or networking.

\n

Throw in a healthy dose of anxiety and some intermittent depression and you get the picture. Instead of growing, our business stagnated. The quest through this dark underworld seemed to have no end in sight. It ruined vacations, stole away family time, punished me physically, hurt our client’s business, and was pushing myself, Jill, and our finances, to our very limits.

\n

Death and Rebirth

\n

It all seemed to come to a head when the pain of my gallstones became so intense I thought I was going to die. After 2 visits to the Emergency Room and 3 days in the hospital, I gave birth to this baby. They actually saw a larger one than this in the ultrasound beforehand, but my body had apparently broken it up before they removed my gallbladder. I returned home with real-world wounds that would turn into scars, and lighter by one gallbladder and several massive gallstones.

\n

\n

I left the hospital with a new lease on life. I felt like I’d been resurrected, fighting my way out of the underworld and back to the land of the living. It helped me open up to a completely different approach to hosting and allowed me to see that tiny speck of light that ended up being the doorway out of this underworld made up of the dark side of WordPress and hosting.

\n

I was able to use my newfound perspective to find some awesome new weapons, and fight my way to that exit. Luckily for you, you can learn from my pain and battles with the underworld.

\n

The Road Back: Simplify

\n

Illumination was mine! Of the knowledge I gained, one key principle stood out among the rest: make things as simple as possible, while avoiding single points of failure on mission-critical systems. Multisite was great for managing all the websites at once, but if one had a problem, they all went down! The same with having a single server to run all our sites: if the server went down, we had the urgency of 30 or 40 clients (back then) all being negatively impacted at once.

\n

We started by killing our Multisites and traditional hosting setups. Instead of a single Multisite with 1 database where a problem could take down all the sites in the Multisite, we moved to individual WordPress installs for each site. As we pulled each site out of the Multisite and migrated it to our new cloud hosting, we also checked the databases and files thoroughly to ensure they were clean, light, and that we eliminated any cruft that had built up in the database. We also stopped running email and DNS through our web servers. This effectively killed the demons that had moved with us in previous hosting migrations.

\n

Here’s my recommended do’s and don’ts for any smaller businesses hosting and maintaining WordPress websites:

\n

Don’t:

\n
    \n
  1. use shared hosting or hosting that uses cPanel
  2. \n
  3. use Multisite (SPoF)
  4. \n
  5. put all your sites on 1 server (SPoF)
  6. \n
  7. use your web server as an email server
  8. \n
  9. send WordPress transactional emails from your webserver
  10. \n
  11. use your web server for DNS
  12. \n
  13. use your hosting company for domain registration
  14. \n
\n

Do:

\n
    \n
  1. use cloud hosting with WordPress-optimized stack and custom control panel
  2. \n
  3. use a bulk-site-management tool
  4. \n
  5. spread your sites across multiple servers
  6. \n
  7. use an email suite (Hover, Zoho, G Suite, Office 365)
  8. \n
  9. use a transactional email service (SendGrid, Postmark, MailGun)
  10. \n
  11. use your registrar for DNS
  12. \n
  13. use a different registrar for registering domains, than your hosting
  14. \n
\n

Following these tips eliminates many single points of failure, simplifies things greatly, and gives you the tools and ability to go right to the source of the problem. Since all your important WordPress functionality isn’t in one place with one point of failure, you can go where the problem is.

\n

For example, if a client isn’t receiving WooCommerce new order emails from their website, we can quickly go to SendGrid to see why that is and what needs to be done to fix it in an easy to use interface. Try that on a traditional APACHE/cPanel setup that sends your client’s company emails, WordPress emails, etc. all from one place.

\n

\n

Cloud Hosting

\n

We eliminated cPanel and the normal Linux hosting stacks by moving to CloudWays, which has a nice WordPress setup that they run on top of a number of cloud hosting services such as Google, Amazon, Digital Ocean, and Vultr. They have their own in-house customized stack and management dashboard. CloudWays removed all the normal bloat and potential for problems that comes with it, and really took away most of the pain, hassle, and responsibility of the hosting part of WordPress and for quite cheap.

\n

On CloudWays, instead of putting all 40+ sites on one server, we split them up, with about 15 – 18 sites on one small Digital Ocean (and later Vultr) server. This meant that if one site had issues, it wouldn’t take down all our other sites. And even if the issue was bad enough to affect the whole server, or the server had its own issues, only a small portion of our clients would be affected at once.

\n

Email Accounts and Transactional Email

\n

Additionally, we stopped running email through our servers. Part of simplifying is outsourcing to people/services who can just do it better than you (or that old hosting you’re clinging to because it’s cheap). I love that good WordPress hosts like CloudWays, Flywheel, and Kinsta have no options for you to do this or include built-in services like SendGrid. I slew a lot of email monsters. Using something like SendGrid or Postmark for WordPress and G Suite or Office 365 for email accounts, eliminates tons of headaches.

\n

We set up WordPress’s emails to go through SendGrid and all our members’ email accounts we migrated to Hover, Google Apps, or Office 365.

\n

Bulk-WordPress Management

\n

In place of Multisite, we found MainWP and chose it over other options like InfiniteWP. It provided us the bulk-control of Multisite, but without the single point of failure issue. The upside is that it’s fairly inexpensive and runs on a WordPress install, so you control it on your hosting.

\n

That’s kinda its downside as well. If something goes wrong, it’s on my team and I to run the problem down and fix it. Or we have to go through the cumbersome process of reporting it to the MainWP support team, then providing them access to both the dashboard site and an affected child site. Eventually we decided to move to ManageWP because it’s a hosted platform. That means when something goes wrong, much of the time, it’s on them to fix, and they have access to fix their own platform, plus the logs, etc from our sites.

\n

MainWP:

\n\n

ManageWP:

\n\n

Master of Two Worlds of WordPress

\n

Fortunately today there are many awesome hosting options and bulk-management tools that simply weren’t available to me years ago when I started on this journey. After this last, final push, my team and I stood back and waited and rested, expecting more monsters. And occasionally one crawled out of it’s hole. But by and large the underworld was defeated and left far behind. Moving to cloud hosting and simplifying were finally the spell that broke the Fiddler curse and freed us from the underworld. Our business’s core service was stable and safe and running like it should be. We could start growing again! It was such a relief!

\n

To reiterate some of the illumination gained on my journey: simplify your WordPress websites and hosting through offloading everything you can to experts who do it better, often for cheaper (if you properly calculate the value of your own time). Focus on your super-power whether it be design or development, or just creating solutions on WP with existing plugins and tools. If your super-power isn’t WordPress at all, you can outsource maintenance, content updates, backups and security, plugin and core updates, and much more to a company like WordXpress. I’ve built this company based on the knowledge and tools I learned on my quest.

\n

The post My “Hero’s Journey” Through the Dark Underworld of WordPress Hosting appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jun 2019 12:00:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Tevya Washburn\";s: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:71:\"WPTavern: Drupal Gutenberg 1.0 Released, Now Ready for Production 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=90376\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/drupal-gutenberg-1-0-released-now-ready-for-production-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:6201:\"

The Gutenberg module for Drupal, created by Frontkom, reached the 1.0 milestone earlier this month. It is the first stable release recommended for use in production with Drupal 8.x.

\n

The 1.0 release removes the Gutenberg-JS dependency and uses Gutenberg core files directly. It is based on Gutenberg version 5.6.1, which was released in early May. The module boasts better handling for media files, adding support for title, caption, and alternative text. It also adds an “Allowed Blocks UI” to the content type admin UI, so administrators can restrict which blocks show up in the block selector.

\n

“We’re now ready for production sites in the sense that we’ll be more careful with structure changes, will try to do update paths when possible, and will create automated tests for crucial functionality,” Frontkom project manager Thor Andre Gretland said. “We’ve solved the blockers for a stable release.”

\n

Upgrading the module from RC-1 may require some extra steps, because it is a big jump, taking the Gutenberg library from 4.8.0 to 5.6.1. Users will need to update the database. It is also necessary to navigate to content types and click save to enable Gutenberg again so that it will begin storing the Allowed blocks in the database. If users get notices about invalid blocks, they are advised to try the Attempt Block Recovery option:

\n

\n

“It’s actually a rather large update,” Gretland said. “We were planning to add a couple of last needed features to release our 1.0 version, but ended up using the latest Gutenberg version with several new great features. We’re also using more of the Gutenberg Core, that we’ve been able to use before.”

\n

The module still has one critical issue that Frontkom is working on. Reusable blocks are not working with the latest release. Users are getting a “this block is unavailable or deleted” message when attempting to insert a reusable block. In the meantime, those who require this feature can roll back to RC1 to get it working again.

\n

So far the Gutenberg module has been well-received. It has been downloaded more than 12,000 times and 494 sites are reported to be using it.

\n
\n

Setup @drupalgutenberg on D8 yesterday (following meeting one of @frontkom at the recent Dutch #CiviCRM sprint) and was pretty blown away. Bringing Medium-style editing to all the CMSs & then some. If #Joomla doesn’t implement a Gutenberg.js integration we/they’ll be left behind. https://t.co/SfieuGfOlf

\n

— Nicol (@netribution) May 28, 2019

\n

\n

Drupal’s Gutenberg module includes access to the Gutenberg Cloud library of free blocks. Although the library has been slow to gain contributors, it does contain several blocks that are helpful for creating page layouts, such as Content in Columns, Hero Section, Section Wrapper, Section Row, and a Feature Box block. Site administrators can also use the Gutenberg module in combination with Drupal’s new Layout Builder, which was introduced as a stable module to Drupal 8.7 core.

\n

“We see a valid use case for mixing Drupal Gutenberg with the Drupal layout builder when you might want to create layout templates with the layout builder, and keep the actual content editing in Gutenberg,” Gretland said. “For example you could use the layout builder to define fixed byline elements for author and create date, but leave the actual content creation experience to Gutenberg.”

\n

There are a few limitations to using the two tools together. The only way to use them on the same project is if they deal with different content types.

\n

“Since Drupal Gutenberg takes over the whole node UI, it can have some unexpected effects when used together with Layout Builder,” Gretland said. “That doesn’t mean that they won’t ever ‘work’ together. One idea could be using the LB data structure to generate Gutenberg fixed layouts/templates and even save Gutenberg data in a structured way handled by Layout Builder.”

\n

Gretland said his team believes Gutenberg delivers a better editing experience than Layout Builder, as it is a more mature project. However, Layout Builder stores its data in a structured way, which has its advantages and disadvantages over Gutenberg.

\n

WebWash has a good video tutorial for Drupal users who want to learn how to configure the Gutenberg module and use it on the Page content type. It includes a walkthrough for common actions like uploading images, creating reusable blocks, and using the Gutenberg Cloud. If you want to see how Gutenberg can improve Drupal’s authoring experience without installing the module, check out the frontend demo of Drupal Gutenberg created by the team at Frontkom.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jun 2019 23:03: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: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: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:45:\"WPTavern: WP Engine Launches DevKit Open Beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90715\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wptavern.com/wp-engine-launches-devkit-open-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2627:\"

Those who host or manage sites on WP Engine now have a new tool at their disposal. It’s called DevKit, developed by Chris Wiegman and Jason Stallings.

\n\n\n\n

DevKit is a WordPress local development environment that includes SSH Gateway access, push and pull deployments to WP Engine, Command Line Interface commands for the Genesis theme framework and other tools.

\n\n\n\n

Although DevKit has tight integration with WP Engine the software can be used independently of the host. With Local by Flywheel, Vagrant, XAMPP, and other tools available, Wiegman explains what motivated him to create a new solution.

\n\n\n\n

“I’ve been working on the perfect WordPress developer environment since I learned about Vagrant in 2013,” he said. “As it was never my full-time job, I could never take it to the next level. DevKit gives me the power to do that.”

\n\n\n\n

Stallings added, “We wanted to build a kick ass set of tools for developers building on WP Engine. That’s been our mission from the start, build something that all developers want to use (including us)!”

\n\n\n\n

As what for what sets DevKit apart from the others, “I think our architecture is very different from both tools,” Stallings said.

\n\n\n\n

“Similar to Docker Engine, DevKit CLI is the interface to DevKit. So when we build the GUI it will 100% complement the CLI, and the two can be used interchangeably. This will enable us to build other interfaces in the future too.”

\n\n\n\n

DevKit provides the following features:

\n\n\n\n\n\n\n\n

Currently, DevKit’s user interface is command line only with plans to add a GUI later this year. It’s available for free and is in open beta for Mac and Linux. Those interested in participating in the open beta can sign up on the DevKit landing page.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jun 2019 20:12:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:83:\"WPTavern: Former npm, Inc. CTO Announces Entropic, a Decentralized Package Registry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90574\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/former-npm-inc-cto-announces-entropic-a-decentralized-package-registry\";s: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:4561:\"

\n

CJ Silverio, former CTO of npm Inc., gave a presentation at JSConf EU 2019 in Berlin earlier this month titled “The Economics of Open Source.” More specifically, she discussed the economics of package management as it applies to open source software, based on her unique perspective and experience gained in working for the company that runs the world’s largest JavaScript package registry.

\n

Silverio tells the story of how npm gained official status and characterizes its success as a catastrophe for a centralized package registry and repository. Although centralization has some advantages for usability and reliability, success can be expensive when a centralized service becomes popular. She described the events leading up to npm’s incorporation in 2013. The registry was down more than it was up in October 2013 and npm needed money.

\n

npm’s owner took seed funding from a VC firm and the Node project continued to give npm special privileges. Developers perpetuated this by continuing to use npm, as over time it had come to define developers’ expectations in serving JavaScript packages. Silverio discusses some of the consequences of npm coming under private control, how developers now have no input into registry policies or how disputes are resolved.

\n

Presumably speaking from her intimate knowledge of the company’s inner workings, Silverio describes how VC-funding turned npm Inc. into a financial instrument.

\n

“Financial instruments are contracts about money,” she said. “npm Inc, the company that owns our language ecosystem, is a thing that might as well be a collection of pork bellies, as far as its owners are concerned. They make contracts with each other and trade bits of it around. npm Inc. is a means for turning money into more money.”

\n

Silverio contends that JavaScript’s package registry should not be privately controlled and that centralization is a burden that will inevitably lead to private control because the servers cost money.

\n

Her sharp criticism of centralized package management leads into her announcement of a federated, decentralized package registry called Entropic that she created with former npm colleague Chris Dickinson and more than a dozen contributors. The project is Apache 2.0 licensed and its creators are working in cooperation with the OpenJS Foundation.

\n
\n

Warming my heart right now: how many former npm-ers are contributing to entropic <3

\n

— Ceej is on vacation (@ceejbot) June 6, 2019

\n

\n

Entropic comes with its own CLI, and offers a new file-centric publication API. All packages published to the registry are public and developers are encouraged to use something like the GitHub Package Registry if they need to control access to packages. The project is just over a month old and is not ready for use.

\n

“I think it’s right that the pendulum is swinging away from centralization and I want to lend my push to the swing,” Silverio said. The last decade has been about consolidation and monolithic services, but the coming decade is going to be federated. Federation spreads out costs. It spreads out control. It spreads out policy-making. It hands control of your slice of our language ecosystem to you. My hope is that by giving Entropic away, I’ll help us take our language commons back.”

\n

Silverio’s Economics of Package Management essay is available on GitHub. Check out the video of the presentation from JSConf EU below. If decentralized package management gains momentum and becomes the standard for the industry, this video captures what may become a turning point in the JavaScript ecosystem and a defining moment for the future of the web.

\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jun 2019 03:41:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:70:\"WPTavern: BuddyPress 5.0 to Update Password Control to Match 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=90023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/buddypress-5-0-to-update-password-control-to-match-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:3462:\"

BuddyPress 5.0 development began in December 2018 after 4.0.0 was released in November. The core BuddyPress team has not published a roadmap for what will be coming in 5.0, but features and fixes added so far can be found on GitHub in the commit log.

\n

One noteworthy addition to the upcoming major release is that the BP Nouveau template pack is being updated to use the same password control as the one used in WordPress core. BuddyPress users will now be able to set their passwords using WordPress’ interface on the registration page and on the user’s general settings page.

\n

Here’s what it will look like in the templates:

\n
\n

Here\'s how it looks \"?\" pic.twitter.com/g8DknNpUKl

\n

— imath (@imath) May 18, 2019

\n

\n

By default, BuddyPress will generate a strong password, but the user can still edit it, if necessary. If the user selects a password that is too weak, the submit button will be disabled until the user confirms they want to proceed by checking the checkbox.

\n

BP Nouveau replaced the bp-legacy template packs in 2018, introducing JavaScript-powered templates, integration with the Customizer, and more layout options for BuddyPress navigation and component directories. As a result of the password control update, the src/bp-templates/bp-nouveau/js/password-verify.js template is scheduled to be deprecated and deleted in BuddyPress 6.0.0, so developers will want to take note if using the bp-nouveau-password-verify script as a dependency for custom password control implementations.

\n

BuddyPress 5.0 also adds BP-specific debug into to the Site Health Info screen that was introduced in WordPress 5.2. This release will require WordPress 4.7 or greater for optimal compatibility and older versions will not be supported. Site owners running on older versions of WordPress have time to prepare.

\n

Although the BuddyPress core team and contributors have put out several security and maintenance releases since version 4.0.0, regular project meetings have been sporadic in 2019. BuddyPress 5.0 was expected at the end of May but a new timeline may be discussed at the next meeting, which is tentatively planned for Wednesday, June 12.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 10 Jun 2019 19:04: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: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:44:\"WPTavern: In Case You Missed It – Issue 25\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90643&preview=true&preview_id=90643\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/in-case-you-missed-it-issue-25\";s: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:7707:\"

photo credit: Night Moves – (license)

\n

There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.

\n

Open Call for People Interested in Being Team Leads

\n

Josepha Haden has published an open call on the Team Updates blog looking for people interested in learning about the Team Lead role. The post includes links to training materials that will be open for two weeks where people can make suggestions.

\n

Once the training materials are complete, interested parties will be sent the team leads training materials and quizzes. Those who pass the quizzes will then be part of a group orientation in which team leads and future leads will be chosen. Even if you’re not interested in becoming a team lead, the training materials in the post contain a lot of useful information about the inner workings of the project.

\n

Marcel Bootsman Continues on After Hospital Visit

\n

Marcel Bootsman who is walking more than 700km to Berlin, Germany for WCEU recently made a hospital visit. “The doctor asked about what I’m doing, and what the problem is, so I explained everything,” Bootsman said. “She examined both legs and found that there was a swelling on my right ankle. She sadly could not diagnose further, since it’s impossible. An expert has to look at it, and an x-ray picture has to be taken.”

\n
\n

YESS! Nothing serious, just an overloaded ankle which is almost healed.
Doctor said I can continue with just one more resting day, so I\'m going by train to my next stop. Just to be of extra help he bandaged my ankle.#WalkToWCEU pic.twitter.com/VdW7C8m71N

\n

— \"??\" Marcel Bootsman (@mbootsman) June 5, 2019

\n

\n

The doctor diagnosed him with having an overloaded right ankle. After wrapping his ankle for extra support, Bootsman continued on. Check out his description and photos from day 19 of his travels.

\n

WooSesh is Coming Back

\n

WooSesh, a global, virtual conference devoted to WooCommerce, is scheduled to take place on October 9-10th. You can follow WooSesh_ on Twitter or sign up to their email list to be notified of when tickets are available.

\n
\n

ANNOUNCEMENT: If you use @WooCommerce to build ecommerce sites, or do any kind of ecommerce development, you\'ll be thrilled to hear that @WooSesh returns on Oct 9 and 10!

\n

Follow @WooSesh_ and join the mailing list at https://t.co/Pyev9v2CPv to stay in the loop pic.twitter.com/hPdv8Yu5LU

\n

— WordSesh (@WordSesh) May 23, 2019

\n

\n

GitHub Repo Templates

\n

Earlier this week, GitHub launched Repository Templates to help developers manage and distribute boilerplate code. Web development agency 10UP has a Theme and Plugin repo template that is available for anyone to use.

\n

WordPress 5.2.2 Release Date Changed

\n

WordPress 5.2.2 was originally scheduled to be released on June 13th, but the release team has decided to push the date back. Tickets that are slated for WordPress 5.3 that meet the requirements to be in a minor release will be merged into 5.2.2. The new release date is Tuesday, June 18th, a few days before WordCamp EU.

\n

WordCamp US After Party Is Now Wordfest

\n

There won’t be a big after party at the conclusion of WordCamp US this year. Instead, organizers are hosting WordFest on Friday, November 1, 2019, at City Museum in St. Louis. According to organizers, the party doesn’t always have to be at the conclusion of the event thus the name change.

\n

How to Use and Create Reusable Block Templates

\n

Justin Tadlock has published a tutorial that explains how to create, use, import, and export reusable block templates in WordPress.

\n

“A lot of this is not intuitive at this point and might take some digging for someone not intimately familiar with all the block editor features. But, this is an extremely powerful feature that I’m sure will become more useful in the future. I can even see things like theme authors sharing reusable blocks to help users build out certain page designs.”

\n

I’m looking forward to seeing other people share their reusable blocks or templates. One of the beautiful things about the new editor is that it doesn’t require a developer to sort blocks into a particular layout and then save it as a reusable block that can be shared.

\n

C02 May Be the Cause of Feeling Drowsy During Conference Sessions

\n

I always thought it had something to do with lunch but I’ve felt drowsy before then. Interesting data shared in a Twitter thread. Hat tip to David Bisset.

\n
\n

Ever wonder why you get so sleepy during conference talks? Turns out lots of conference venues aren\'t well-ventilated, causing CO2 to rise to levels that cause drowsiness (>1000ppm). Data from @keflavich shows this steady rise over the first 50min of a conference session. pic.twitter.com/AjFO2eQDrJ

\n

— Cara Battersby (@battersbot) June 4, 2019

\n

\n

That’s it for issue twenty-five. If you recently discovered a cool resource or post related to WordPress, please share it with us in the comments.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jun 2019 21:33:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"WPTavern: Experimenting With Reusable Blocks to Create Post Templates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90636\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wptavern.com/experimenting-with-reusable-blocks-to-create-post-templates\";s: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:2177:\"

For the past several years, I’ve used the Post Template plugin developed by Vincent Prat to create and manage post templates. For example, some of the information in the WordPress Weekly and In Case You Missed It posts never changes and instead of manually entering it each time, it’s nice to use a template where only a few changes are necessary.

\n\n\n\n

The other day, I was wondering if I could use the reusable block feature in Gutenberg to replace the plugin. Justin Tadlock reached out and provided me a reusable block template JSON file that I imported into Gutenberg. By the way, if you successfully import a block into WordPress, the block won’t appear until you manually refresh the page.

\n\n\n\n

The reusable block template approach works fairly well. However, I noticed that I was unable to add a block inside the reusable block. When I tried, a red line was displayed and any blocks that were inserted were removed.

\n\n\n\n
Red Means No
\n\n\n\n

I understand that reusable blocks are meant to be restricted templates where changes are distributed across a site to wherever the block is displayed. But it’s still a bummer that I can’t add a block inside the template for a singular purpose if a need arises.

\n\n\n\n

One other thing I noticed is that reusable blocks are custom post types. While there is a link to manage them within the reusable block selector, there isn’t a dedicated item within the admin menu. Unless you know the location of the management link, adding and managing them can be a bit more time-consuming.

\n\n\n\n

If you want a quick shortcut to the reusable block management screen, add this to the URL after your domain name. wp-admin/edit.php?post_type=wp_block

\n\n\n\n

I think I’ll experiment with reusable blocks a bit more but as long as they’re not changing often, I believe they’ll make a nice replacement for the Post Templates plugin. What use cases have you encountered where reusable blocks were the solution?

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jun 2019 02:13:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"WPTavern: Branch Continuous Integration Service Selected for TinySeed Startup Accelerator\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90611\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"https://wptavern.com/branch-continuous-integration-service-selected-for-tinyseed-startup-accelerator\";s: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:4298:\"

Branch, a Docker-based continuous integration service for WordPress, has been selected for TinySeed’s startup accelerator. The company was founded by Peter Suhm who is also the creator of WP Pusher, a plugin that lets developers install and update WordPress themes and plugins directly from GitHub, Bitbucket, and GitLab.

\n

TinySeed, founded by Rob Walling and Einar Vollset, is a remote accelerator that focuses on providing enough funding for early-stage SaaS founders to live for a year and focus full-time on their startups. It advertises itself as “the first startup accelerator designed for bootstrappers.” TinySeed is unique in that it does not have a bias against single founders. The website states that the majority of successful $1m-$30m SaaS companies that TinySeed is connected with were started by founders working alone.

\n

Branch fits the bill as a SaaS company with a single founder and no employees. As part of the investment terms, TinySeed invests $120k for the first founder (plus $20k per additional founder) in exchange for 8-15% equity. If founders do not need the money for living expenses they are free to spend it on growing the business. Both Branch and WP Pusher are included in Suhm’s participation in TinySeed.

\n

“WP Pusher was doing just enough to pay my bills living in a fairly cheap city (Glasgow), but not enough to pay a full time developer salary,” Suhm said. “However, I didn’t spend much time on WP Pusher in the past few years and was working part time for other companies – mainly Timekit as a backend developer.”

\n

Suhm said the TinySeed investment will allow him to work full time on Branch and WP Pusher for at least a year or two without having to worry about making a salary.

\n

“I may also decide to make a hire during the program, but I want the product to be a little bit more mature,” he said. “In terms of the roadmap, I’ll be able to focus more on building the best tool and less about making a lot of money in the beginning.”

\n

Branch and WP Pusher are fairly unique products in the WordPress space. Suhm said he sees most of his competition coming from continuous integration services that are not tailored to WordPress.

\n

“However, my biggest competitor at the moment is probably manual labor – WordPress developers testing and deploying everything manually,” Suhm said.

\n

TinySeed received approximately 900 applications from which they will select 10-15 companies for participation in 2019. Co-founder Rob Walling has knowledge of the WordPress ecosystem, as he previously invested in WP Engine’s 2011 round of funding.

\n

“Peter has a distinct advantage with Branch in that he’s building on the audience, customer base, and domain knowledge he’s developed with WP Pusher,” TinySeed co-founder Rob Walling said. “His methodical approach to shipping code and content every week has been a good signal for us that he’s pushing the product forward, as well as a key factor in building Branch’s traction in the space.”

\n

Branch is joining a handful of other SaaS companies that have already been selected for 2019, including ClientSherpa, Gather, SimSaaS, Reimbi, and Castos.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jun 2019 20:31: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: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:49:\"WPTavern: Automattic Adopts Alex Mills’ 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90583\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/automattic-adopts-alex-mills-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:4656:\"

Automattic announced today that a team inside the company will be adopting Alex Mills‘ plugins and continuing their development and support. Mills, also known around the web as @Viper007Bond, was a WordPress core contributor and prolific plugin developer who passed away in February 2019 after a battle with Leukemia.

\n

At one time last year, Mills was the primary author for and contributor to more than 40 plugins hosted on WordPress.org. The current collection seems to have been pared back to 17 of his most popular plugins. According to stats from WP Tally, these 17 plugins have a cumulative download count of 138,665,603 and a cumulative rating of 4.55 out of 5 stars.

\n

“Since all of my plugins are open-source, they are free to be forked by reputable authors in the WordPress community. It would mean a lot to have my legacy go on,” Mills said in his farewell post earlier this year. The plugins are all free without any pro versions or monetization efforts attached to them.

\n

“I’d never monetize any of my plugins,” Mills told the Tavern after his popular Regenerate Thumbnails plugin passed 5 million downloads in 2017. “I write them for fun not profit. It would be a conflict of interest anyway due to my employment at Automattic.”

\n

Regenerate Thumbnails is active on more than a million WordPress sites and passed the 10 million downloads milestone in January 2019. It has already been downloaded more than 7,000 times today and has regularly received 3K-12k downloads per day throughout 2019.

\n

The enduring popularity of Regenerate Thumbnails is a testament to Mills’ commitment to writing future-proof plugins. What started as a small plugin to fix a client’s problem in 2008 quickly became an indispensable utility for millions of WordPress users transitioning between themes with different image sizes. For those users who could never write their own script to generate new thumbnail sizes, Mills’ plugin was a little piece of time-saving magic that exemplifies the significant contributions plugin developers can make when they write and share code that solves a common problem.

\n

Automattic plans to fork each of Mills’ GitHub repositories and will add them to the Automattic Github account. The team behind this effort is also adding the following paragraph to each plugin’s readme file:

\n

In February 2019 Alex Mills, the author of this plugin, passed away. He leaves behind a number of plugins which will be maintained by Automattic and members of the WordPress community. If this plugin is useful to you please consider donating to the Oregon Health and Science University.

\n

Automattic will also be answering support queries on the forums and the team is open to receiving help from other members of the WordPress community in maintaining and supporting Mills’ plugins.

\n

“In times gone by authors left works of music, novels, poetry, and letters on their passing,” Donncha Ó Caoimh said on the Automattic Engineering blog. “They were static works of art frozen in time. Alex leaves behind his code that will continue to evolve and operate in a living world used by thousands (millions?) of people every day as they go about their online lives.”

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jun 2019 16:51:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: WPWeekly Episode 355 – Food Poisoning Is No Joke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90569&preview=true&preview_id=90569\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wptavern.com/wpweekly-episode-355-food-poisoning-is-no-joke\";s: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:1676:\"

In this episode, John James Jacoby and I discuss Joost de Valk’s decision to step down as WordPress’ Marketing Lead. I shared my recent encounter with food poisoning and some of the lifestyle changes I’m making to improve my health. We also talk about a new experimental plugin by Automattic that aims to provide full site editing and FreeCodeCamp’s decision to migrate away from Medium to Ghost.

\n

Stories Discussed:

\n

Joost de Valk Steps Down as WordPress Marketing Lead

\n

FreeCodeCamp Moves Off of Medium after being Pressured to Put Articles Behind Paywalls

\n

Automattic is Testing an Experimental Full Site Editing Plugin

\n

WPWeekly Meta:

\n

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

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #355:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jun 2019 01:10:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:82:\"WPTavern: Google Adds New Desktop/Mobile Selector to the Rich Results Testing Tool\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90532\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/google-adds-new-desktop-mobile-selector-to-the-rich-results-testing-tool\";s: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:3254:\"

Google’s rich results testing tool has been updated to include a selector for desktop or mobile so website owners can check their results on both platforms. This tool shows if pages are properly structured for display in Google’s carousels, images, breadcrumbs, events, books, and other types of rich snippets. A glossary is available with images showing what each type of result looks like with the proper structured data in place.

\n

\n

Last week Google announced that it will begin enabling mobile-first indexing (crawling sites with a mobile user-agent) by default for new domains on July 1, 2019. Site owners can select “Googlebot Smartphone” as the user-agent on the rich results testing tool to see if their sites are prepared for mobile-first indexing. The tool is still in beta, so not all rich results and error types are supported yet.

\n

If your page supports rich results, you will see a confirmation and can click through to view the HTML. Certain rich result types will display a preview of how the result might appear in Google Search. If multiple result layouts are available, the tool will also let you drill down into the different layouts for both desktop and mobile.

\n

\n

If you get a result that says “Page not eligible for rich results known by this test” when you know that you have the structured data in place, it could be because the beta version of this tool only supports a subset of rich result types. These currently include job postings, recipes, courses, TV and movie, events, and Q&A pages.

\n

You can also test your page using this tool by putting in a code snippet, in case your content is not publicly accessible or is restricted behind authorization.

\n

Depending on your specific requirements, there are many different WordPress plugins that properly structure data to improve how your content appears in rich results around the web, such as Schema, All In One Schema Rich Snippets, Schema App Structured Data, Rank Math, and Yoast SEO, to name a handful of popular options.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jun 2019 19:57: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: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:62:\"WPTavern: Joost de Valk Steps Down as WordPress Marketing Lead\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90542\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/joost-de-valk-steps-down-as-wordpress-marketing-lead\";s: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:2397:\"

Joost de Valk has announced that he’s stepped down from the WordPress Marketing and Communications Lead role. The position was created and awarded to de Valk earlier this year. Not only was it a new position, but it also expanded the leadership roles in the WordPress project.

\n\n\n\n

Despite making progress, de Valk didn’t feel as though he was fulfilling the leadership aspect of his role. “My experience over the last few months made me feel that while I was doing things and getting things done, I certainly wasn’t leadership. I don’t want to pretend I have a say in things I don’t have a say in,” he said.

\n\n\n\n

Not having a clear definition of what marketing means and having people within the project on the same page contributed to his decision.

\n\n\n\n

“There’s a stark difference between where I thought I would be in the organization in this role, and where I am actually finding myself now,” de Valk said.

\n\n\n\n

“Even things that every outsider would consider marketing (release posts, about pages) are created without even so much as talking to me or others in the marketing team. Because I felt left out of all these decisions, I feel I can’t be a marketing lead.”

\n\n\n\n

He also cited a lack of clarity surrounding his position, “I’ve been asked dozens of times on Twitter, Facebook and at WordCamps why I now work for Automattic, which of course I don’t but that is the perception for a lot of people,” he said. “On other occasions, I seem to be the token non-Automattician, which I’m also uncomfortable with.”

\n\n\n\n

Due to taking a toll from failing to fulfill the position, de Valk plans to take an extended vacation during the Summer and when he returns, focus 100% of his efforts on Yoast and his Chief Product Officer role.

\n\n\n\n

Matt Mullenweg commented on de Valk’s article thanking him for being willing to try new things and for his passion, impatience, and drive to improve 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jun 2019 17:57:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: Take Back Your Web: Tantek Çelik’s Call to Action to Join the Independent Web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90416\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/take-back-your-web-tantek-celiks-call-to-action-to-join-the-independent-web\";s: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:4246:\"

Tantek Çelik, Web Standards Lead at Mozilla and co-founder of IndieWebCamp, delivered an inspirational talk titled “Take Back Your Web” at the most recent beyond tellerrand conference in Düsseldorf, Germany. He opened the presentation with a litany of Facebook’s wrongdoings, taking the world’s largest social network to task for its role in increasing polarization, amplifying rage, and spreading conspiracy theories.

\n

Çelik challenged the audience to “stop scrolling Facebook,” because its algorithms are designed to manipulate users’ emotions and behaviors. He noted that it is the only social network with a Wikipedia page dedicated to its criticism. This massive document has a dizzying number of references, which Wikipedia says “may be too long to read and navigate comfortably.” As an alternative to scrolling Facebook, Celik encouraged attendees to spend time doing nothing, an activity that can be uncomfortable yet productive.

\n

The “Take Back Your Web” presentation is a call to action to join the independent web by owning your own domain, content, social connections, and reading experience. Celik recommends a number of IndieWeb services and tools to empower users to take control of their experiences on the web.

\n

With a free site hosted on GitHub, he said the costs of owning your own domain are less than owning a phone or having internet service. Suggestions like this are targeted at developers who share Twitter names instead of domains and post articles on Medium. Setting up a site on GitHub is not a simple task for most. That’s why networks like WordPress.com, along with hosts that provide instant WordPress sites, are so important for enabling average internet users to create their own websites.

\n

Celik referenced Matthias Ott’s recent article “Into the Personal-Website-Verse,” highlighting the section about the value of learning new technologies by implementing them on your own website: “A personal website is also a powerful playground to tinker with new technologies and discover your powers.” It’s one of the few places developers can expand their skills and make mistakes without the pressure to have everything working. Ott enumerates the many benefits of people having their own enduring home on the web and encourages developers to use their powers to make this a reality:

\n

As idealistic as this vision of the Web might seem these days, it isn’t that far out of reach. Much of what’s needed, especially the publishing part, is already there. It’s also not as if our sites weren’t already connected in one way or another. Yet much of the discussions and establishment of connections, of that social glue that holds our community together – besides community events in real life, of course –, mostly happens on social media platforms at the moment. But: this is a choice. If we would make the conscious decision to find better ways to connect our personal sites and to enable more social interaction again, and if we would then persistently work on this idea, then we could, bit by bit, influence the development of Web technologies into this direction. What we would end up with is not only a bunch of personal websites but a whole interconnected personal-website-verse.

\n

Check out Çelik’s slides for the presentation and the recording below for a little bit of inspiration to re-evaluate your relationship with social networks, create your own site, or revive one that has been neglected.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 04 Jun 2019 21:50: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: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:93:\"WPTavern: Jetpack 7.4 Adds Business Hours Block and Ability to Share Content Through WhatsApp\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90503\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/jetpack-7-4-adds-business-hours-block-and-ability-to-share-content-through-whatsapp\";s: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:2229:\"

Jetpack 7.4 is now available and includes a new Business Hours block. This block contains a toggle that users can set to show whether they’re open or closed.

\n\n\n\n

There’s also a way to add additional times so restaurants, for example, can display when they’re open for breakfast, lunch, and dinner. However, I couldn’t figure out a way to add text to label what the hours mean. Also, depending on the theme, the alignment displays incorrectly. You can see the block in action below.

\n\n\n
Sunday
Closed
Monday
9:00 AM – 1:00 PM
5:00 PM – 10:00 PM
Tuesday
9:00 AM – 5:00 PM
Wednesday
9:00 AM – 5:00 PM
Thursday
9:00 AM – 5:00 PM
Friday
9:00 AM – 5:00 PM
Saturday
Closed
\n\n\n

The Slideshow, Carousel, and Tiled Galleries blocks have all received enhancements to improve their look and performance on mobile devices. The Carousel block also contains better theme compatibility.

\n\n\n\n

WhatsApp is now included in the Jetpack Sharing module. Users can enable it by browsing to Jetpack > Settings > Sharing > Configure sharing buttons. The button supports sharing content through the stand-alone app and the web interface.

\n\n\n\n

Jetpack 7.4 also makes a number of enhancements to the Recurring Payments block such as improving the display of the renewal frequency in the button list and improving the look of the payment modal on mobile devices. This version also requires users to be on the Premium or Professional plan on WordPress.com in order to access the button.

\n\n\n\n

You can see a full list of changes in 7.4 by viewing the changelog.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 04 Jun 2019 20:19: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: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:52:\"WordPress.org blog: The Month in WordPress: May 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6987\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/06/the-month-in-wordpress-may-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6614:\"

This month saw the 16th anniversary since the launch of the first release of WordPress. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a significant global event.

\n\n\n\n
\n\n\n\n

Release of WordPress 5.2

\n\n\n\n

WordPress 5.2 “Jaco” was released on May 7 shipping some useful site management tools, such as the Site Health Check and PHP Error Protection, as well as a number of accessibility, privacy, and developer updates. You can read the field guide for this release for more detailed information about what was included and how it all works.

\n\n\n\n

327 individual volunteers contributed to the release. If you would like to be a part of that number for future releases, follow the Core team blog and join the #core channel in the Making WordPress Slack group.

\n\n\n\n

A Successful WordPress Translation Day 4

\n\n\n\n

WordPress Translation Day is a 24-hour event organised by the Polyglots team where community members from all over the world come together to translate WordPress into their local languages. For the fourth edition held on 11 May, 183 brand new contributors joined the Polyglots team from 77 communities across 35 countries in Africa, Asia, Europe, North America, South America, and Oceania.

\n\n\n\n

While the WP Translation Day is a great time for focussed contributions to localizing WordPress, but these contributions can happen at any time of the year, so if you would like to help make WordPress available in your local language, follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.

\n\n\n\n

Updated Plugin Guidelines Proposal

\n\n\n\n

The Plugins team has proposed some updates to the guidelines for developers on the Plugin Directory. The majority of the proposed changes are intended to address significant issues faced by developers who do not speak English as a first language, making the Plugin DIrectory a more accessible and beneficial place for everyone.

\n\n\n\n

The proposal will be open for comments until late June, so the community is encouraged to get involved with commenting on them and the direction they will take the Plugin Directory. If you would like to be involved in this discussion, comment on the proposal and join the #plugin review team in the Making WordPress Slack group.

\n\n\n\n

Continued Gutenberg Development

\n\n\n\n

Since the block editor was first released as part of WordPress Core in v5.0, development has continued in leaps and bounds with a new release every two weeks. The latest update includes some great incremental improvements that will be merged into the 5.2.2 release of WordPress along with the other recent enhancements.

\n\n\n\n

In addition to the editor enhancements, work has been ongoing in the Gutenberg project to bring the block editing experience to the rest of the WordPress dashboard. This second phase of the project has been going well and the latest update shows how much work has been done so far.

\n\n\n\n

In addition to that, the Block Library project that aims to bring a searchable library of available blocks right into the editor is deep in the planning phase with a recent update showing what direction the team is taking things.

\n\n\n\n

If you would like to get involved in planning and development of Gutenberg and the block editor, follow the Core and Design team blogs and join the #core, #design, and #core-editor channels in the Making WordPress Slack group.

\n\n\n\n
\n\n\n\n

Further Reading:

\n\n\n\n\n\n\n\n

Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Jun 2019 10:21: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: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: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:75:\"WPTavern: Gutenberg Team is Exploring Adding Motion to Block Moving Actions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90465\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://wptavern.com/gutenberg-team-is-exploring-adding-motion-to-block-moving-actions\";s: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:4221:\"

In a post titled “Using Motion to Express Change,” Gutenberg designer and engineer Matías Ventura takes a deep dive into how animation can be applied to interfaces to replicate realistic motion. These animations can sometimes more clearly communicate changes, particularly in relationship to the action of moving or reordering items on a page.

\n

“Even though the instant transformation of the interface is accurate it may not be the clearest expression of the change that just occurred,” Ventura said. “The relationship between intention and effect might become harder to grasp. Motion can be a great aid in communicating relationships and clarifying the changes experienced in a more intuitive way.”

\n

This creates an interesting choice for an interface designer. Although instantaneous changes are possible to implement, they may require more time for the user’s brain to process. In the case of an editor, any added cognitive processing can pull a user out of the flow of writing. Ventura sets a good practical rule of thumb for determining if an animation adds value to an interaction:

\n

One could say that an animation is worth being present if the clarity of change it provides is greater than the time it would take to adjust cognitively to the new state in its absence.

\n

Ventura illustrates this concept with two video demos in his post – one showing how block reordering currently looks in WordPress’ editor and a second with an example of how it could be improved with subtle, tasteful animations. It’s an early prototype but very convincing:

\n

\n

When Gutenberg was still in the selling phase before being merged into core, some said that moving forward was simply a matter of retraining your muscle memory to work with the new editor. However, at that time there were still a number of markedly flawed interactions that didn’t feel natural and were even jarring for the user. The legacy editor didn’t have blocks to reorder or many of the other interactions introduced by the new block paradigm, so there wasn’t much prior context for comparison.

\n

User reviews have complained about the cognitive load that Gutenberg adds and have continued to identify problematic interactions with the core blocks. Unfortunately, in many heated exchanges that took place in comments and discussions prior to WordPress 5.0’s release, these concerns were often brushed aside as coming from people who were resistant to change.

\n

Many of the reviewers may not have had the right words to communicate what it was they were experiencing, but the cognitive load may be one of the strongest reasons why the Classic Editor plugin has more than 5 million active installs.

\n

Matías Ventura’s proposal to add motion to express change in the editor has the potential to solve some of these unintuitive interactions. The Gutenberg repository now has an issue dedicated to exploring and discussing the use of motion to add clarity to the action of reordering blocks.

\n

Ventura’s post is an encouraging read that demonstrates the thought and craftsmanship that go into architecting an interface that is required to meet the needs of millions of users. If you have been impatient with Gutenberg’s progress, as I have been, it’s important to recognize that these kinds of refinements to interactions take time to percolate. Replicating realistic motion comes from contemplating how we interact with the known world and understanding how that informs users’ digital expectations.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 04 Jun 2019 04: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"HeroPress: Ugyen’s Roadmap to WordPress Contributions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=2848\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:156:\"https://heropress.com/essays/ugyens-roadmap-to-wordpress-contributions/#utm_source=rss&utm_medium=rss&utm_campaign=ugyens-roadmap-to-wordpress-contributions\";s: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:44456:\"\"Pull

འབྲི་རྩོམ་འདི་རྫོང་ཁ་ན་ལུ་ཡ་ཡོདཔ་ཨིན།

\n

Ugyen Dorji is from Bhutan, the landlocked country situated between two giant neighbors, India to the south and China to the north. Ugyen works for ServMask Inc and is responsible for the robust Quality Assurance process for All-in-One WP Migration plugin. He believes in the Buddhist teaching that “the most valuable service is one rendered to our fellow humans” and his work ethic shows with managing WordPress translation projects for his Plugin ’All-in-One WP Migration.’  Ugyen also keeps multi-language support for WordPress; furthermore the plugin is now translated into 42 languages with more on the way.

\n

How Ugyen started his career with WordPress

\n

Life is a struggle – it is a mixture of success and failure which can come in any venture and that too late and sometimes most unexpectedly people lose heart after a failure; but a person who takes failure in his/her stride and continues his effort for success in long run in the word of EL Kerten means “The secret of success is knowing whom to blame for your failure.”

\n

Back in 2016, he had been looking for new working place after his former cloud company got shattered with some financial crisis, he has looked for a new job. For which he has tried his best and one fine day he makes it to an interview – where he has been triggered with WordPress questionnaires. On that moment he has no proper answer for interviewers saying big number to interviewers, though he has basic knowledge about WordPress. After that day, just sat in his room with silence and made up his mind to learn and get skilled himself with WordPress wisdom,  watching cities from his window receiving cool air, and said himself

\n

“I will make my career with WordPress and it will be my bread and butter”.

\n

After a few months, he received a call from ServMask Inc, who developed a great plugin called   “All-in-One WP Migration” which made his dream come true like an angle ServMask Inc blessed his dream to make his living with WordPress. Ugyen is now an active contributor to the WordPress Community.

\n

Ugyen’s First WordCamp Experience

\n

WordCamp is a genuine spotlight for plugin and theme developers to reach WordPress users and website developers. It’s a glorious atmosphere where many incredible talks about WordPress take place. The “tribe” meetings are a phenomenal moment for aspiring computer engineers, content writers and developers to showcase their talent and meet each other.

\n

WordCamp Bangkok 2018 was an essential day for Ugyen and ServMask because their sponsorship of the event delivered them the opportunity to connect with our active WordPress users and showcase their appreciation on better quality of WordPress plugin.

\n

Contributor Day

\n

The first day of WordCamp is Contributor Day. Ugyen associated with a community team and got to share a conversation with WordPress folks from all over the world. Community communication is the ground root of WordCamp and WordPress meetups, giving him all the chance to share and manifest what WordPress does and  how it is used. He also addressed encouraging more speakers and WordPress members to nurture their experience and whereby he could support new organizers to continue and contribute to building the WordPress community in places where it is not yet booming.

\n

Conference Day

\n

Conference Day is the main event of WordCamp and is held on the second day. Ugyen was taking care of a Photo Booth for people to snap their memories. I think this was a great idea to capture the memories of WordCamp for attendees, speakers, and organizers.

\n

The foremost intention of the conference day is the presentations that take place throughout the day. Ugyen had a great moment to attend various talks which were very beneficial for developers, entrepreneurs, firms, and young startups firms. What holds in Ugyen’s mind is a plan that exhibits leveraging website content has been shown to lead to 100% growth in business extension.

\n

How Ugyen became WordPress Meetup Thimphu Co-Organizer

\n

Following October 2016, Ugyen came over about WordPress Meetup Bangkok and WordCamp Bangkok 2018. From that onwards, the importance of WordPress Meetup catches on his mind to introduce WordPress to his home country and cities. The foremost incidence that clicks on his mind was on WordPress Translation Day 3 on September 30, 2017, during WordPress Meetup Bangkok where he has seen his locale Dzongkha was in lowest percentage comparing to another locale status on WordPress Core Translation. Later in WordCamp Bangkok 2018 Contributors day when he met with WordPress Folks and WordPress Community, Meetup Organizer from many countries.

\n

WordPress Meetup Thimphu is an easygoing, volunteer-organized, non-profit meetup covering everything related to WordPress and keeping our Bhutanese Gross National Happiness four pillars in mind with aims to preserve and promote our unique culture and national language. WordPress Meetup implies for individuals and all people who love WordPress and want to contribute and share their knowledge and have experience in meeting new faces and for networking. Ugyen’s Specific focus on encouraging local and international language WordPress bloggers and help startup companies to grow their assets with WordPress and share what he has learned from WordPress with his Bhutanese WordPress community.

\n

Ugyen’s First WordPress Meetup Thimphu was a huge success within his community coinciding with WordPress Main event WordPress Translation Day 4.  Ugyen would take a more vital role in preserving his national language by making use of WordPress actively by our Dzongkha bloggers, online Dzongkha news, government websites so that Bhutanese WordPress core contributors could hand over to our next generation very proudly.

\n

What we have achieved :

\n
    \n
  1. Done WordPress Core Translation for our locale Dzongkha.
  2. \n
  3. New Translation Contributor for our WordPress Core Translation for Dzongkha.
  4. \n
  5. Participated in Global WordPress Translation Day 4 Livestream.
  6. \n
  7. Invited WordPress Experts from other countries to http://wpbhutan.slack.com.
  8. \n
  9. Invited WordPress Meetup Thimphu members to http://wpbhutan.slack.com to discuss more on WordPress related topics and for helpline on WordPress for Bhutanese WordPress users and wordpress.org login for new users.
  10. \n
  11. Speaker of the event Tenzin Namgyel Senior ICT officer from DDC WordPress Local Manager and General Translation Editor for our locale Dzongkha.
  12. \n
  13. Good meal and tea with great place to host at Ariya Hotel
  14. \n
  15. Introduction of a member for networking.
  16. \n
  17. Became a part of Global WordPress Translation Day 4 team.
  18. \n
  19. Event Sponsored by ServMask Inc and Helped by Dzongkha Development Commission with Language Experts.
  20. \n
\n

WordPress Future Road Plans

\n

“The best preparation for tomorrow is to do today’s work superbly well” so that we can put all our effort, then we’ll see a very good result and success will surely be yours. No men can hope to have a very successful life but there will be one or two in exception in this earthly world in thousand cases of this matter which results strong determination can help to attain success. Therefore with Ugyen’s determination here are some of his road plans for WordPress.

\n

For WordPress Meetup: Ugyen’s next plan is to visit the language universities and teach them to blog in Dzongkha using WordPress. He said, “ We have plans to gather a group of active Bhutanese WordPress Bloggers and host panel talks to extend the beauty of Bhutan and unique culture of Bhutan to outside nations. And also one of the WordPress Main Events: Introduction to Open Source is in a process to be host soon. His Majesty the fourth King of Bhutan once said, “the future of our nation lies in the hands of our children.” Therefore Ugyen works to focus more on youth to enhance their WordPress Skills.

\n

For WordCamp: WordCamp Thimphu is my goal – to reach and invite more WordPress Experts as speakers of the main event and support Bhutanese to grow their career with WordPress. WordCamp Asia is in the process to kick start in 2020 and become one of the WordCamp Co-organizer among 41 WordCamp Asia Co-Organizers.

\n

To WordPress lovers – “If you want to be successful the ball is in your court, you think to throw a ball outside or smash the ball or play the game nicely and win the game’’

\n

ཚིག་གསར་དཔེ་སྐྲུན་ལས་ཁང་ལུ་རྒྱབ་སྐྱོར་གྱི་དོན་ལུ་ ཨོ་རྒྱན་གྱི་ལམ་ཡིག

\n

ཨོ་རྒྱན་རྡོ་རྗེ་གི་སྐྱེ་སའི་ཕ་ཡུལ་ནི་འབྲུག་རྒྱལ་ཁབབ་ཨིན། འབྲུག་རྒྱལ་ཁབ་འདི་ཁྱིམ་ཚང་རྒྱལ་ཁབ་ རྒྱ་དང་བོད་ཀྱི་བར་ན་ ཕྱི་ཡི་ལྕགས་རི་མཚུངས་པའི་ གང་རི་ཚུ་གི་བསྐོར་ཏེ་ ཡོདཔ་ཨིན། ཨོ་རྒྱན་གྱི་ ལཱ་འབད་ས་འདི་ ServMask Inc ནང་འབད་དོ་ཨིནམ་ད་ ཁོ་གི་ལཱ་འགན་ངོ་མ་འདི་ WordPress གི་ས་གནས་གཞན་ཁར་སྤོ་འགྱོ་ནིའི་ལས་རིམ་ཚུ་ པུས་ཚད་སྒྲིང་སྒྲིང་བཟོ་ནི་ལུ་ ཡིད་ཆེས་བསྐྱེད་བཅུག་ནི་འདི་ཨིན།

\n

ཁོ་ནང་པ་སངས་རྒྱས་ཀྱི་ཆོས་ལུགས་ལུ་ཡང་ སྙིང་ཐག་པའི་གཏིང་ལས་ ཡིད་ཆེས་ཡོད་མི་ཅིག་ཨིན་པའི་ཆ་གནས་ལས་ ཁོ་གིས་ལཱ་འབད་ཐངས་ཡང་ ཚིག་གསར་དཔེ་སྐྲུན་ལས་ཁང་གི་ སྐད་སྒྱུར་ལས་འཆར་གྱི་ འཛིན་སྐྱོང་འཐབ་ནི་འདི་ཨིན་མས། འདི་མ་ཚད་ ཁོ་གི་ WordPress གི་དོན་ལུ་ སྐད་ཡིག་སྣ་མང་གི་ རྒྱབ་སྐྱོར་ཚུ་འབད་དོ་ཡོདཔ་མ་ཚད་ ད་ཚུན་གྱི་རིང་  All-in-One WP Migration plugin འདི་སྐད་ཡིག་མ་འདྲཝ་༤༢་༢དེ་ཅིག་ནང་ སྐད་སྒྱུར་འབད་དེ་ཡོདཔ་ཨིན།

\n

ཨོ་རྒྱན་གྱི་ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་དང་མཉམ་གཡོག་གི་མདུན་ལས་ག་དེ་སྦེ་འགོ་བཙུགས་ཡི་ག་གི་སྐོར།

\n

ང་བཅས་རའི་མི་ཚེ་གི་ལམ་འདི་ གདོང་ལེན་དྲག་པོ་ཅིག་ཨིན། མི་ཚེ་འདི་ནང་ལཱ་དང་བྱ་བ་ག་ཅི་ར་འབད་རུང་ མཐར་འཁྱོལ་ནི་དང་འཐུས་ཤོར་ནི་འདི་ རང་བཞིན་ཅིག་ཨིན། ཨིན་རུང་མི་མང་ཤོས་ཅིག་གི་ར་ ལཱ་འདི་རང་གི་མནོ་བཞིན་བསམ་བཞིན་འགྱོ་མ་བཏུབ་པའི་བསྒང་ལས་ བློ་ཕམ་སི་སི་སྦེ་ ཚར་ཅིག་གུ་མནོ་བསམ་ག་ནི་ཡང་མ་གཏང་པར་ གདོང་ལེན་ཅན་གྱི་མི་ཚེ་འདི་ལུ་ གདོང་ལེན་འབད་མ་ཚུགས་པར་ རྒྱབ་ཤུད་རྐྱབ་སྡོདཔ་མས། རང་གི་མི་ཚེ་ནང་ཚགས་ཁ་མ་ཚུད་པའི་འཐུས་ཤོར་འབྱུང་རུང་ འདི་ལས་ཡོན་ཏན་ལེན་སྟེ་ མི་ཚེ་འདི་ནང་མཐར་འཁྱོལ་ནི་ལུ་གཙོ་བོ་བཏོན་ནི་བཀོ་མ་བཞག་པར་ འཕྲོ་མཐུད་དེ་ར་བརྩོན་འགྲུས་བསྐྱེད་དེ་ལཱ་འབད་མི་ མི་འདི་གིས་ མི་ཚེ་ནང་འབྲས་བུ་ལེགས་ཤོམ་འབག་ནི་ཡོདཔ་ཨིན། མཁས་དབང་ཨིལ་ཀར་ཊྲན་གྱི་ཡང་ མི་ཚེ་ནང་མཐར་མཁྱོལ་ནི་དོན་ལུ་གསང་བ་ངོ་མ་འདི་ར་ འཐུས་ཤོར་བའི་གནད་དོན་འདི་ལུ་རྫུན་ཁ་བཀལ་ཤེས་ནི་འདི་ཨིན་ ཟེར་གསུངས་ནུག དེ་བཟུམ་སྦེ་ར་ ཨོ་རྒྱན་ཡང་ཧེ་མ་ དབྱིན་ལོ་༢༠༡༦་ལུ་ཁོ་རའི་ལཱ་འབད་སའི་ ཀལཝཏ་ཚོང་སྡེ་འདི་དངུལ་འབྲེལ་གྱི་དཀའ་ངལ་ཅིག་འཐོན་སྟེ་ སྒོ་བསྡམ་པའི་ཤུལ་ལུ་ ཁོ་ཡང་ལཱ་གཡོག་གསརཔ་ཅིག་ནང་འཛུལ་ཞུགས་འབད་ནིའི་དོན་ལུ་ གཡོག་གི་ས་གོ་ཅིག་འཚོལ་སྟེ་ར་སྡོད་པའི་ཤུལ་ལུ་ ཉིནམ་ཅིག་འབདཝ་ད་ ཚིག་གསར་དཔེར་སྐྲུན་ལས་ཁང་དང་མཉམ་ གཡོག་གི་དོན་ལུ་དྲི་བ་དྲི་ལན་འབད་ནིའི་གོ་སྐབས་ཅིག་ཐོབ་ནུག རེ་འདོད་ཅན་གྱི་ཉིནམ་འདི་ལས་འགོ་བཟུང་ ཁོགི་སེམས་ཁར་ ཁོ་རའི་མི་ཚེ་འཚོ་ཐབས་ཀྱི་དོན་ལུ་ ཡུན་དུ་གནས་པའི་འོང་འབབ་ཀྱི་གཞི་གཙོ་བོ་འདི་ ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་ར་ཨིན་ཟེར་མནོ་ནུག ཟླཝ་དག་པ་ཅིག་གི་ཤུལ་ལས་ འཛམ་གླིང་ནང་གཞན་དང་མ་འདྲ་བའི་ལས་འགུལ་ ‘ག་ར་མཉམ་གཅིག་འཛོམས་ཚུགས་པའི་ ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་གི་ ས་གནས་སྤོ་བ་’ ཟེར་མི་གསར་བཟོ་ཚོང་སྡེ་ནང་ལས་ ServMask གིས་འགྲུལ་འཕྲིན་ལྷོད་དེ་ ཁོ་བཙག་འཐུ་བསྒྲུབ་པའི་གནས་ཚུལ་གོཝ་ད་ ཁོ་གིས་ཁོ་རའི་རེ་བ་བསྐྱེད་མི་ རེ་འདོད་འདི་དངོས་སུ་སྦེ་འགྲུབ་པའི་དགའ་བ་ཚད་མེདཔ་སྦེ་འབྱུང་ནུག འདི་འབདཝ་ལས་བརྟེན་ ད་རིས་ཨོ་རྒྱན་ཡང་ ཚིག་གསར་དཔེར་སྐྲུན་ལས་ཁང་གི་དོན་ལུ་ འཇོན་ཐངས་ཅན་གྱི་ལས་གཡོགཔ་ཅིག་ཨིན་མས།

\n

ལྟ་བ་མཐུན་པའི་གནས་ཚུལ་སྡེ་ཚན་ནང་ཨོ་རྒྱན་གྱི་ཉམས་མྱོང་འགོ་དང་པ།

\n

ལྟ་བ་མཐུན་པའི་གནས་ཚུལ་སྡེ་ཚན་འདི་ plugin དང་བརྗོད་དོན་གསར་བཟོ་མཛད་མི་ཚུ་ WordPress ལག་ལེན་འཐབ་མི་དང་་ཡོངས་འབྲེལ་ཁ་རྒྱང་གསར་བཟོ་འབད་མི་ཚུ་གི་ གནས་ཚད་ནང་ལྷོད་ཚུགས་ནི་དོན་ལུ་ཡིད་ཆེས་བཏུབ་པའི་ ཐད་དམིགས་བཟུམ་ཅིག་ཨིན་མས། WordPress གི་སྐོར་ལས་གནས་ཚུལ་དང་གསུང་བཤད་གནམ་མེད་ས་མེད་ལེགས་ཤོམ་ གོ་ཡོདཔ་ལས་ ཚོང་སྡེ་འདི་མིང་གཏམ་ཅན་ཅིག་ཨིན་པའི་ ཚོར་སྣང་དང་དགའ་བ་འབྱུང་ཡི། འདི་མ་ཚད་ ཁོང་མི་རིགས་ལེ་ཤ་གཅིག་ཁར་ཚོགས་སྟེ་ ཞལ་འཛོམས་གནང་ནིའི་སྲོལ་ཡོད་མི་འདི་ ལྷག་པར་དུ་ ཁོང་གློག་རིག་འགོ་དཔོན། བརྗོད་དོན་རྩོམ་སྒྲིག་པ་དང་གསར་བཟོ་པ་ཚུ་གི་དོན་ལུ་ ཁོང་རའི་རིག་རྩལ་དང་ལྕོགས་གྲུབ་དཔེ་སྟོན་འབད་ནིའི་དོན་ལུ་ རེ་འདོད་ཅན་གྱི་དུས་ཚོད་ལེགས་ཤོམ་ཅིག་འབད་མཇལ་ཡི།

\n

འཛམ་གླིང་ལྟ་བ་མཐུན་པའི་སྡེ་ཚན་ བེང་ཀོག ༢༠༡༨་འདི་ ཨོ་རྒྱན་དང་ ServMask གི་དོན་ལུ་ ཉིནམ་ཁག་ཆེ་ཏོག་ཏོ་ཅིག་ཨིན། འདི་ཡང་ཉིནམ་འདི་ཁར་ དུས་སྟོན་འདི་གི་དངུལ་གྱི་རྒྱབ་སྐྱོར་པ་གིས་ ཁོང་ཚུ་ལུ་སྤུ་འགྱིར་དྲག་ཡོད་པའི་ WordPress སྤྱོད་མི་ཚུ་དང་འབྲེལ་བ་འཐབ་སྟེ་ WordPress Plugin གི་སྤུས་ཚོད་ཧེང་སྐལ་ཡར་དྲག་འགྱོ་ནིའི་དོན་ལུ་ ཁོང་རའི་ངལ་རངས་གསལ་སྟོན་འབད་ནིའི་གོ་སྐབས་གནང་ཡོདཔ་ལས་བརྟེན་ཏེ་ཨིན་མས།

\n

རྒྱབ་སྐྱོར་པའི་ཉིནམ།

\n

WordCamp གི་ཉིནམ་དང་པ་འདི་ རྒྱབ་སྐྱོར་པའི་ཉིནམ་སྦེ་བརྩིཝ་ཨིན། ཉིནམ་འདི་ཁར་ཨོ་རྒྱན་གྱི་ མི་སྡེའི་སྡེ་ཚན་ཚུ་དང་འབྲེལ་བ་འཐབ་སྟེ་ ཕྱོགས་བཞི་མཚམས་བརྒྱད་ལས་འོང་མི་ WordPress གི་སྡེ་ཚན་ཚུ་དང་མཉམ་ ཁོ་རའི་བསམ་འཆར་བརྗེ་སོར་འབད་ནིའི་གོ་སྐབས་བཟང་པོ་ཡང་ཐོབ་ནུག མི་སྡེ་བརྡ་སྤྲོད་ཀྱི་ WordCamp དང WordPress གི་ཞལ་འཛོམས་འདི་ ཨོ་རྒྱན་གྱི་དོན་ལུ་ WordPress གི་ལཱ་ག་དེ་སྦེ་འབདཝ་ཨིན་ན་དང་ འདི་ག་དེ་སྦེ་ལག་ལེན་འཐབ་ནི་ཨིན་ན་ཚུའི་སྐོར་ གཞན་ལུ་བཤད་ནི་གོ་སྐབས་ཁྲིལ་བུ་སྤྲོད་མི་ ལམ་སྟོན་ཅིག་མས། དེ་གིས་སྦེ་ ཁོ་གི་ད་ལས་ཕར་གསལ་བཤད་པ་ག་དེ་མང་མང་དང་ WordPress གི་འཐུས་མི་ཚུ་ ཁོང་རའི་ཉམས་མྱོང་དང་ལྕོགས་གྲུབ་ཡར་དྲག་བཏང་ནིའི་སེམས་ཤུགས་ག་དེ་དྲག་དྲག་བསྐྱེད་བཅག་ནི་ཟེར་ སླབ་ཡོདཔ་མ་ཚད་ ཁོ་གི་འགོ་འདྲེན་པ་གསརཔ་ཚུ་ལུ་ཡང་ WordPress མི་སྡེ་འདི་དར་ཁྱབ་མ་འགྱོ་བའི་ས་གོ་ནང་ལས་ཕར་ ངོ་སྤྲོད་འབད་དེ་ ལག་ལེན་འཐབ་བཅུག་ནིའི་དོན་ལུ་ འཕྲོ་མཐུད་དེ་ར་ རྒྱབ་སྐྱོར་དང་གྲོགས་རམ་འབད་ནི་ཨིན་མས།

\n

གྲོས་ཚོགས་ཀྱིས་ཉིནམ།

\n

གྲོས་ཚོགས་ཀྱི་ཉིནམ་འདི་ WordCamp གི་ལས་རིམ་གཙོ་བོ་ཅིག་ཨིན། དེཡང་ཉིནམ་གཉིས་པའམ་འདི་ནང་ འགོ་འདྲེན་འཐབ་ཨིན། འདི་གི་སྐབས་ ཨོ་རྒྱན་གྱིས་ མི་ཚུ་གི་ དྲན་ཐེ་བཞག་ནིའི་དོན་ལས་ པར་བཏབ་ནི་གིས་ ལཱ་འགན་འདི་འབགཔ་ཨིན། ངེའི་སེམས་ཁར་ལས་འབད་བ་ཅིན་ འདི་བཟུམ་མའི་ གནས་སྐབས་འདི་ WordCamp གི་ལས་རོགསཔ་ གསལ་བཤདཔ་དང་ འགོ་འདྲེན་པ་ཚུ་གིས་ དྲན་ཐོ་བཞག་ནི་དོན་ལུ་ གནམ་མེད་ས་མེད་ལེགས་ཤོམ་ཅིག་ ཨིན་པས་ཟེར་མནོཝ་མས། མི་རིགས་ལུ་ཕན་ཐོགས་པའི་ཞབས་ཏོག་འདི་ཁྱད་དུ་འཕགསཔ་ཨིན། ང་བཅས་འགྲོ་བ་མི་ལུ་ ཕན་ཐོགས་པའི་ལཱ་འབད་མི་འདི་ ཞབས་ཏོག་ཚུ་གི་གྲས་ལས་ དྲག་ཤོས་ཅིག་ཨིན།

\n

ཨྱོན་འདི་ WordPress Meetup ཐིམ་ཕུག་གི་འགོ་འདྲེན་པ་ག་དེ་སྦེ་འབད་ཡོདཔ་ཨིན་ན།

\n

འདི་ཡང་ ཨྱོན་ཁོ་རང་ སྤྱི་ལོ་༢༠༡༦ སྤྱི་ཟླ་༡༠པའི་ ནང་ WordPress Meetup Bangkok དང་ WordCamp Bangkok ༢༠༡༨ ཀྱི་ནང་ལས་ WordPressགི་སྐོར་ལས་ཧ་གོ་བའི་ཤུལ་ འབྲུག་རྒྱལ་ཁབ་ནང་ལུ་ཡང་ གཞི་བཙུགས་འབད་དགོཔ་ཁག་ཆེ་བའི་སྐོར་ལས་ ཤེས་ཡོདཔ་ཨིན་མས།

\n

འདི་ཡང་ སྤྱི་ལོ་༢༠༡༧ སྤྱི་ཟླ་༩པའི་ སྤྱི་ཚེས་༣ རྒྱལ་སྤྱི་ WordPress སྐད་བསྒྱུར་གྱི་ཉིནམ་གྱི་སྐབས་ལུ་ WordPress Meetup Bangkok ལུ་ རྫོང་ཁ་འདི་ WordPress Core Translation ནང་ རྫོང་ཁ་འདི་ གཞན་མི་སྐད་ཡིག་དང་ཕྱདཔ་དང་ དམའ་ཤོས་ཅིག་སྦེ་ཡོདཔ་མཐོང་ཡོདཔ་ཨིན་མས།

\n

དེའི་ཤུལ་ལས་ WordCamp Bangkok ༢༠༡༨ རྒྱབ་སྐྱོར་པའི་ཉིནམ་གྱི་སྐབས་ལུ་ WordPress གི་མཉམ་རོགས་དང་ WordPress གི་མི་སྡེ་ དེ་ལས་ རྒྱལ་ཁབ་གཞན་ཁའི་ Meetup འགོ་འདྲེན་པ་ཚུ་དང་ཕྱད་ཡོདཔ་ཨིན་མས།

\n

WordPress Meetup ཐིམ་ཕུག་འདི་ ཁེབ་ས་མེད་པར་ ཁས་བླངས་ཀྱི་ཐོག་ལས་ རྒྱལ་ཡོངས་དགའ་སྐྱིད་དཔལ་འཛོམས་ཀྱི་ཀ་ཆེན་སེམས་ཁར་བཞག་སྟེ་ ལམ་སྲོལ་དང་ རྒྱལ་ཡོངས་སྐད་ཡིག་ མི་ཉམས་རྒྱུན་སྐྱོང་འབད་ནི་ལུ་དམིགས་གཏད་བསྐྱེདཔ་ཨིན།

\n

WordPress Meetup འདི་ མི་ངོམ་རང་རྐྱང་དང་ WordPress ལུ་དགའ་མི་ དེ་ལས་ རང་སོའི་ཡོན་ཏན་ བརྗེ་སོར་འབད་ནི་དང་ མི་གསརཔ་འཕྱེད་དེ་ མཐུན་ལམ་བཟོ་ནི་ལུ་ཕན་ཐོག་ཡོདཔ་ཨིན།

\n

ཨྱོན་གྱིས་ ནང་འཁོད་དང་ རྒྱལ་སྤྱིའི་སྐད་ཡིག་གི་ཐོག་ལུ་ WordPress ནང་བྲི་མི་ཚུ་ལུ་གཙོ་བོ་སྟོན་ཏེ་ ལས་སྡེ་ཚུ་ ཡང་རྒྱས་གཏང་ནི་རྒྱབ་སྐྱོར་འབདཝ་མ་ཚད་ WordPress ནང་ལས་ག་ཅིག་རང་ལྷབ་ཅི་ག་ འབྲུག་པའི་མི་སྡེ་ཚུ་ལུ་ བརྗེ་སོར་འབདཝ་ཨིན།

\n

WordPress གི་དུས་སྟོན་གྱི་ལས་རིམ་ WordPress སྐད་བསྒྱུར་གྱི་ཉིནམ་༤པ་དང་འབྲེལ་ ཨྱོན་གྱི་ WordPress Meetup Thimphu ཐེངས་དང་པའམ་འདི་ མཐར་འཁྱོལ་ཅན་སོང་ཡོདཔ་ཨིན།

\n

ཨྱོན་གྱི་རྒྱལ་ཡོངས་སྐད་ཡིག་གོང་འཕེལ་གཏང་ཐབས་ལུ་ WordPress འདི་ རྫོང་ཁ་ནང་བྲི་མི་དང་ ཡོངས་འབྲེལ་གྱི་ཐོག་ལས་ རྫོང་ཁའི་གནས་ཚུལ་ དེ་ལས་ གཞུང་གི་ཡོངས་འབྲེལ་ཚུ་ནང་ ལག་ལེན་འཐབ་སྟེ་ འབྲུག་པའི་ WordPress འདི་ མ་འོང་བུ་བརྒྱུད་ཚུ་ལུ་སྤྲོད་ནིའི་ འགན་ཁུར་གཙོ་བོ་ཅིག་འབག་སྟེ་ཡོདཔ་ཨིན།

\n

གྲུབ་འབྲས།:

\n

༡ རྫོང་ཁའི་ WordPress Core སྐད་བསྒྱུར་འབད་ཚར་ཏེ་ཡོདཔ།

\n

༢ WordPress Core སྐད་བསྒྱུར་གྱི་དོན་ལུ་ སྐ་བསྒྱུར་གསརཔ་གི་ཕན་འདེབས་འབད་ནི།

\n

༣ Global WordPress སྐད་བསྒྱུར་ཉིནམ་༤པའི་ དངོས་མཐོང་ ༼ https://wptranslationday.org/༽ ནང་བཅའ་མར་  གཏོགས་ཡོདཔ།

\n

༤ ཕྱི་རྒྱལ་ཁབ་ངགཞན་མིའི་ wordpress མཁས་མཆོག་ཚུ་ http://wpbhutan.slack.com. ནང་གདན་འདྲེན་ཞུ་ཡོདཔ།

\n

༥ WordPress Meetup ཐིམ་ཕུག་གི་འཐུས་མི་ཚུ་ WordPress དང་འབྲེལ་བའི་དོན་ཚན་ཐོག་ལུ་གྲོས་བསྡུར་འབད་ནིའི་དང་ འབྲུག་པའི་ WordPress ལག་ལེན་འཐབ་མི་ཚུ་དང་ wordpress.org ནང་འཐུས་མི་གསརཔ་ཚུ་ འཛུལ་ཞུགས་འབད་ནིའི་ནང་ རྒྱབ་སྐྱོར་འབད་ནིའི་དོན་ལུ་ http://wpbhutan.slack.com ནང་ གདན་འདྲེན་ཞུ་ཡོདཔ།

\n

༦ དེ་ནང་སྐུ་མགྲོན་སྦེ་ རྫོང་ཁག་གོང་འཕེལ་ལྷན་ཚོགས་ཀྱི་བརྡ་དོན་དང་འཕྲུལ་རིག་འགོ་དཔོན་གོངམ་ བསྟན་འཛིན་རྣམ་རྒྱལ་འབྱོན་ཡདོཔ་ཨིན།

\n

༧ ལས་རིམ་འགོ་འདྲེན་འཐབ་སའི་ས་ཁོངས་འདི་  བཟེས་སྒོ་ཡང་ལེགས་ལོམ་འཐོབ་ས་ Ariya Hotel ནང་ཨིན།

\n

༨ མཐུན་ལམ་བཟོ་ནིའི་དོན་ལུ་ འཐུས་མི་ངོ་སྤྲོད་འབད་ནི།

\n

༩ Global WordPress སྐད་བསྒྱུར་ཉིནམ་༤པའི་ སྡེ་ཚན་གྱི་གྲངས་སུ་འཛུལ་ནི།

\n

༡༠ ལས་རིམ་འདི་ ServMask Inc གི་གྲོགས་རམ་དང་ རྫོང་ཁག་གོང་འཕེལ་ལྷན་ཚོགས་ཀྱི་ སྐད་ཡིག་མཁས་མཆོག་ཚུ་གིས་རྒྱབ་སྐྱོར་འབད་ཡོདཔ།

\n

WordPress གི་མ་འོངས་པའི་འཆར་གཞི།

\n

ལཱ་དང་བྱ་བ་ག་ཅི་རང་འབད་རུང་ གྲུབ་འབྲས་ལེགས་ཤོམ་འོང་དགོ་པ་ཅིན་ ད་ལྟོ་ལས་རང་ རྩ་འགེངས་ཏེ་ ལེགས་ཤོམ་སྦེ་འབད་དགོཔ་ཨིན།

\n

ལཱ་ག་ཅིག་རང་འབད་རུང་ སྐལ་བ་ཅན་གྱི་མ་གཏོགས་རེ་བ་ཅན་གྱི་མི་འཐོབ་ཟེར་དོ་བཟུམ་ སྐལ་བ་ཡོད་པའི་ཁར་ ལཱ་ཚུ་ བརྩོན་འགྲུས་བསྐྱེད་དེ་འབད་བ་ཅིན་ ལཱ་ག་ཅི་རང་འབད་རུང་མཐར་མ་ཕྱིན་པའི་དཔེ་མི་སྲིད། དེ་འབདཝ་ལས་ ཨྱོན་གྱི་ བརྩོན་འགྲུས་དང་བསྟུན་ཁོང་གི་མ་འོངས་པའི་ Word Press གི་འཆར་གཞི་ཚུ་འོག་ལུ་འཁོད་དེ་ཡོདཔ་ཨིན།

\n

དེ་ཡང་ ཨྱོན་གྱི་ སྐད་ཡིག་གི་མཐོ་རིམ་སློབ་གྲྭ་དང་གཙུག་སྡེ་ཚུ་ནང་འགྱོ་སྟེ་ WordPress ལག་ལེན་འཐབ་ཐོག་ལས་ རྫོང་ཁའི ནང་བྲི་ཐངས་ཀྱི་སྐོར་ལས་སྟོན་བྱིན་ནི་ཨིན།

\n

དེ་མ་ཚད་ འབྲུག་པའི་ WordPressལག་ལེན་འཐབ་མི་ཚུ་འཛོམས་ཏེ་ འབུག་པའི་ལམ་སྲོལ་དང་ མཛེས་ཆའི་སྐོར་ལས་ གཞན་མི་རྒྱལ་ཁབ་ནང་ གསལ་སྟོན་འབད་ནིའི་དོན་ལུ་ གྲོས་བསྡུར་གོ་འདྲེན་འཐབ་ནི་དང་ WordPress གི་ལས་རིམ་གཙོ་ཅན་ཅིག་ཨིན་མི་ Introduction to Open Source ཟེར་མི་འདི་ འགོ་འདྲེན་འཐབ་ནིའི་ལཱ་འབད་བའི་བསྒང་རང་ཡོདཔ་ཨིན།

\n

དེ་ལས་ འབྲུག་མི་ཚུ་ WordPress ལག་ལེན་འཐབ་ནིའི་ནང་རྒྱབ་སྐྱར་འབད་དེ་ ཡར་རྒྱས་གཏང་ཞིནམ་ལས་ མི་ཚེ་སྐྱོང་ཚུགས་ནིའི་དོན་ལུ་ WordPress གི་མཁས་མཆོག་ཚུ་གདན་འདྲེན་ཞུ་སྟེ་ Wordcamp གི་དོན་ལུ་ Wordcamp ཐིམ་ཕུག་འགོ་འདྲེན་འཐབ་ནི་ཨིན།

\n

WordCamp Asia འདི་ཡང་ སྤྱི་ལོ་༢༠༢༠ལུ་འགོ་འདྲེན་འཐབ་ནི་ཨིནམ་ལས་ WordCamp Asia ནང་ལས་ འགོ་འདྲེན་པ་༤༡ཡོད་པའི་གྲལ་ཁར་ཚུད་དེ་ཡོདཔ་ཨིན།

\n

མཇུག་རང་ ཁྱོད་ར་ཚུ་ WordPress ལུ་དགའ་མི་ཅིག་ཨིན་པ་ཅིན་ ད་ལྟོ་ རང་ལུ་ རང་དབང་ཡོདཔ་་ལས་ རང་སོའི་མི་ཚེ་མཐར་འཁྱོལ་ཅན་བཟོ་ནིའི་གོ་སྐབས་ཡོདཔ་ཨིན།

\n

The post Ugyen’s Roadmap to WordPress Contributions appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Jun 2019 02:00:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Ugyen Dorji\";s: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:77:\"WPTavern: New WordProof Plugin Timestamps WordPress Content on the Blockchain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90424\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"https://wptavern.com/new-wordproof-plugin-timestamps-wordpress-content-on-the-blockchain\";s: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:5868:\"

WordProof Timestamp is a new free plugin that bridges the WordPress and blockchain communities in an approachable, user-friendly way. It gives users the ability to timestamp their posts and pages to demonstrate transparency and claim ownership of content.

\n

WordProof works with any EOSIO blockchain to create the timestamp and provides a custom certificate link with a frontend pop-up to display it.

\n

\n

The plugin adds a “View the blockchain certificate” link under each post or page, which pops up the URL, title, content, timestamp information, and will soon also display revisions. Users will be able to browse through different timestamps to view the changes.

\n

WordProof Timestamp was first created by Van Ons, a WordPress agency based in Amsterdam. This is the same company that recently open sourced Laraberg, a package that allows developers building applications with Laravel to integrate the Gutenberg editor. Development has now been passed on to a dedicated WordProof team that is funded by Tenos.

\n

“I have been working and investing with blockchain as a hobby since 2013,” Van Ons founder Sebastiaan van der Lans said. “After we built the WP GDPR Compliance plugin and started working Laraberg, I am trying to work more and more on open source projects. From my point of view, WordPress + blockchain could not only democratize publishing but also doing business as a whole.”

\n

Van der Lans said he expects that any type of publishing website or any site with “Terms & Conditions” pages can benefit from timestamping. It’s especially useful in mediating claims of plagiarism and content theft. WordProof has no transaction costs and is almost instant (0.5s). Van der Lans said it was important for this solution to have no transaction fees, since it is fundamental to proving the author’s identity and the integrity of the content.

\n

Right now the plugin offers the ability to timestamp an entire article, including the title and content. Block level time-stamping is not on the roadmap, but the team is open to adding it in the future. They are currently looking into time-stamping media files and legal documents.

\n

After launching the plugin in beta, a team of 60 testers, from both the WordPress and EOS.IO blockchain communities, gave feedback that led to the creation of a WordProof Wizard to make it easier for users to set up the required accounts.

\n

“Our testers’ main concern: it was too difficult to create an account on the blockchain and download and set-up a blockchain wallet afterwards,” Van Ons head of product Jelle van der Schoot said. “Therefore, we invested a lot of time into improving the UI/UX of the entire process (downloading the plugin, creating a blockchain account, downloading and setting up a wallet, timestamping).”

\n

The wizard supports both Telos and EOS and guides users through the process of setting up an account directly inside the WordPress dashboard. The process takes approximately five minutes.

\n

\n

“We believe the WordProof Wizard can have a massive impact on the onboarding of new users to the blockchain in general, but more specifically to the Telos and EOS blockchains,” van der Schoot said.

\n

Timestamping posts is by no means a new idea. There are already several free WordPress plugins that have similar functionality and work with various blockchain technology, such as WP Blockchain, STAMPD.IO, Po.et, and Mingrana WP to Blockchain. WordProof is different from many of them in that it doesn’t use a centralized middle layer.

\n

The team behind the plugin is working on more tools that bring blockchain features to WordPress and will soon be adding cryptographically secured decentralized WordPress hosting to the WordProof lineup. van der Lans will also be speaking about more of the benefits of timestamping content with the blockchain at WordCamp Europe in his presentation titled “From WordPress to blockchain: the future is 100% open source.”

\n

If you’re interested in the project, you can follow WordProof on Twitter or join the WordProof Telegram channel where users can also find support for the plugin.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Jun 2019 21:56:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:96:\"WPTavern: FreeCodeCamp Moves Off of Medium after being Pressured to Put Articles Behind Paywalls\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90381\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"https://wptavern.com/freecodecamp-moves-off-of-medium-after-being-pressured-to-put-articles-behind-paywalls\";s: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:5824:\"

After four years of publishing on Medium, FreeCodeCamp is migrating all of its articles to its own open source publishing platform, a modified version of Ghost. The platform allows approved authors to cross-post their blog articles on the new FreeCodeCamp News site for free, without any ads.

\n

“Medium was a great place to publish because it helped a lot of people discover your articles. But the community has outgrown Medium,” FreeCodeCamp founder Quincy Larson said.

\n

“Medium has shifted to a paywall model where they mainly recommend paywalled articles, then encourage visitors to pay to get around their paywall.

\n

“At the same time, not much of the traffic to Medium articles comes from Medium itself. Most of it comes from Google and social media.”

\n

In the detailed public announcement on the FreeCodeCamp forums, Larson said he noticed his articles started to get less distribution after he decided that putting them behind a paywall would not be compatible with the mission of his organization.

\n

“As of 2019, Medium won’t give you much ‘distribution’ within their platform unless you’re willing to put your articles to be behind their paywall,” Larson said. “At the same time, if you do put your article behind their paywall, you’re limiting your readership to just the people who have the resources to pay. This is at odds with the goals of the freeCodeCamp community. We want to make these learning resources as widely available as possible.”

\n

In an email to blog authors who had published on FreeCodeCamp’s Medium publication, Larson elaborated on more serious concerns that he had with the platform’s approach to his organization. Oleg Isonen, one of the blog authors, published the contents of the email, which was later deleted at Larson’s request.

\n

“But over the past year Medium had become more aggressive toward us,” Larson said. “They have pressured us to put our articles behind their paywalls. We refused. So they tried to buy us. (Which makes no sense. We’re a public charity.) We refused. Then they started threatening us with a lawyer.”

\n

\n

Many of those who read the email encouraged Larson to write a follow-up article, as Medium’s tactics towards publishers are a matter of legitimate public concern, both to those who use the platform and readers who support the company through subscriptions.

\n

Larson responded, confirming that he sent the email but that he wanted to move on from the situation.

\n
\n

This email was intended only for Oleg and a few of our other authors. I have messaged him asking to delete it. We are focused on the future and want to move on from this.

\n

— Quincy Larson (@ossia) May 31, 2019

\n

\n

The new freeCodeCamp News site has migrated the organization’s 5,000 articles that were previously posted on Medium. The articles will still be available on Medium, but from now on freeCodeCamp plans to publish on its own platform. The site promises users full control, better analytics, AMP support, and a better reader experience that doesn’t require people to sign in or pay to read articles.

\n

“I’m optimistic that all of us in the developer community can start our own blogs on the open web, then use community tools like freeCodeCamp News to raise awareness of them,” Larson said.

\n

Medium abruptly changed course in 2017 to become a publisher of subscription-based content, scrapping the ad-driven revenue model without notifying publishers ahead of time. Many publications that had invested heavily in building a following on Medium were forced to leave after discovering that the company did not have their best interests in mind. Medium’s new paywalled content model, which CEO Ev Williams claims is “a different, bolder approach” targeted at fixing what is broken with media, could not sustain publishers who were convinced to join the platform in its earlier days.

\n

FreeCodeCamp joins a wave of other publications that are moving back to WordPress and other open source platforms. This trend is set to continue as Medium’s obtrusive popups and poor reader experience drive readers away from the content hosted there. Publishers who are in it for the long haul, those who value stability and full control of their content, will return to the open web.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 01 Jun 2019 00:07:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:65:\"WPTavern: WPWeekly Episode 354 – Pantheon Acquires StagingPilot\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90371&preview=true&preview_id=90371\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/wpweekly-episode-354-pantheon-acquires-stagingpilot\";s: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:2065:\"

In this episode, John James Jacoby and I discuss Panethon’s acquisition of StagingPilot and why regression visual testing will likely become a standard feature across managed WordPress hosts if it’s not already. I rant about the size of text on so many sites being too large and having to shrink the site down to 80-90% in order for it to be manageable. We celebrate WordPress’ 16th birthday, discuss what happens to unloved patches, and GitHub’s Sponsors tool.

\n

Stories Discussed:

\n

Robots, Autopilot, and The Holy Grail of WebOps

\n

WordPress Turns 16

\n

Unloved Patches

\n

New GitHub Sponsors Tool Draws Concerns from Open Source Community

\n

Automattic Acquires Prospress, the company behind WooCommerce Subscriptions

\n

Transcript:

\n

EPISODE 354 – Pantheon Acquires StagingPilot Transcript

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, June 5th 3:00 P.M. Eastern

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #354:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 May 2019 22:40:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:72:\"WPTavern: Automattic is Testing an Experimental Full Site Editing Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90309\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://wptavern.com/automattic-is-testing-an-experimental-full-site-editing-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4288:\"

Automattic is working on a new experimental Full Site Editing plugin aimed at enhancing the page creation workflow in the block editor. Starting a new page from scratch may be overwhelming for those who don’t have a vision for how to tastefully put blocks together to lay out the page. This is a problem that this experimental plugin may be able to solve.

\n

Full Site Editing currently provides three custom blocks for post content, templates, and a blog posts listing. The Blog Posts Listing block expands upon core’s Latest Posts block to include an excerpt and meta information.

\n

The plugin is available in the WordPress Plugin Directory, although it is somewhat difficult to find when searching in the admin plugin installer. The most recent 0.1.1 version of the plugin seems to be broken, but if you roll back to the initial release, you can see some of the page template experiments. After activating the plugin, navigate to Pages » Add New and a new modal with a template selector should pop up.

\n

\n

The templates come pre-filled with demo content and images, so the user doesn’t have to think about how to configure the blocks to match the demo.

\n

\n

The functionality in Full Site Editing is being developed for use on WordPress.com. It makes sense for a network that regularly onboards new bloggers and site owners. It is in the company’s best interest to deliver the fastest possible site creation experience, rather than have new users get frustrated and confused about how to get started.

\n

A template selector for creating new pages could also be useful for the broader WordPress community. Plugin developer Jeffrey Carandang tested Full Site Editing and suggested that it might be useful to add this functionality to Gutenberg with custom hooks so that developers can add their own custom templates. This would make guiding users through the new theme setup process much easier for theme shops.

\n

Automattic has a label on the Calypso repository dedicated to categorizing issues in the full site editing project. The plugin is going to be enabled on a small set of sites for initial testing. There are quite a few issues that still need to be ironed out, including things like preventing users from deleting the header and footer and finalizing the theme used with the plugin. At the moment, the plugin seems to be tailored specifically to the Twenty Nineteen theme and the pre-filled templates do not look as good when used with other themes.

\n

The functionality included in the Full Site Editing plugin may also be coming to Jetpack. Automattic’s developers are currently researching the best way to include it, since so far it has been developed as a separate plugin and not geared towards becoming a Jetpack module.

\n

Full Site Editing is not recommended for use in production, as it’s still under active development. The plugin’s details explicitly state that it is “only designed to work on the WordPress.com environment and could break after an update.” Check it out if you want to explore some exciting new possibilities for how the block editor can work together with themes to make page creation more approachable for users.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 May 2019 22:17: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: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:75:\"WPTavern: Pantheon Acquires Visual Regression Testing Platform StagingPilot\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90288\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://wptavern.com/pantheon-acquires-visual-regression-testing-platform-stagingpilot\";s: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:2952:\"

Panethon, a managed host geared towards Drupal and WordPress sites, has acquired StagingPilot. Financial details of the deal were not disclosed. Nathan Tyler, founder of StagingPilot, and his brother Phil Tyler will be brought into the company.

\n\n\n\n

StagingPilot is a four year old company that runs a barrage of visual regression tests on WordPress sites before they’re automatically updated.

\n\n\n\n

StagingPilot creates a copy of the site and places it into a staging environment. The service then conducts a number of tests that include, checking for visual errors, a white screen of death, and elements on a page disappearing. A number of snapshots are created along with a detailed report on the errors that are discovered.

\n\n\n\n

Josh Koenig, Co-Founder and Head of Product at Pantheon, says the acquisition puts the company within reach of the ‘Holy Grail’ of WebOps.

\n\n\n\n

“Once you have a hundred sites (or heck, even twenty), the grind of keeping up with routine updates can be daunting,” Koenig said. “Our existing WebOps tools let our customers automate a lot of that maintenance, but building and managing that automation is on them. We want our users to automate their operations, not operate their automation.”

\n\n\n\n

Pantheon plans to integrate StagingPilot into its offerings in three phases. First, it will migrate StagingPilot’s technology into its existing managed updates feature and extend it beyond WordPress to support Drupal.

\n\n\n\n

Then, the company plans to fully integrate the service with its organizational features providing substantial benefits to agency partners or those who manage many sites.

\n\n\n\n

The third phase looks to take advantage of services such as Google’s applied learning machines to create AI-driven testing.

\n\n\n\n

Out-of-the box, WordPress only updates minor versions automatically and leaves major updates, plugins, and themes up to the user. One of the most common fears of enabling auto-updates is having something on the site break.

\n\n\n\n

Often, the process of testing updates is left up to the consultant or whoever manages the site. Depending on the size or number of sites being managed, it can become a major time suck.

\n\n\n\n

Hosting companies like Pantheon with StagingPilot, LiquidWeb, and others are easing the fear of auto updates in general and saving people a lot of time by using automatic visual regression testing.

\n\n\n\n

To learn more about StagingPilot and to see Nathan demo the service in-person, check out this episode of WPshowandtell hosted by Jason Tucker.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 May 2019 01:32: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:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"WPTavern: Gutenberg 5.8 Released with Prototype of New Block-based Widgets Screen\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90267\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"https://wptavern.com/gutenberg-5-8-released-with-prototype-of-new-block-based-widgets-screen\";s: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:3753:\"

Gutenberg 5.8 was released today with three new features and more than three dozen enhancements, documentation improvements, and bug fixes.

\n

This release gives users the ability to change the text color in the Heading block. The same color options available in the paragraph and button blocks are now available in the heading block.

\n

A recent release of the EditorsKit plugin (version 1.5) added this feature and the plugin’s author had tracked nearly two dozen issues and discussions where users have asked for text highlighting or similar features.

\n

“We really need this for all block controls (lists, paragraphs etc),” Ben Gillbanks commented on the relevant GitHub issue. “Anything that can be used on a group block with a colored background could cause readability issues and so the text color will need to be changeable.” Gutenberg designer Mark Uraine said that adding text color options to all the text blocks is the next step following this update.

\n

Gutenberg 5.8 adds support for reordering gallery images using a simple arrow control to move selections forwards or backwards. This isn’t an ideal interaction but Gutenberg phase 2 lead Riad Benguella said the team is exploring adding drag and drop support.

\n

Benguella shared a video that demonstrates these two new features:

\n

\n

This release introduces an initial version of the new widgets screen. You can check it out in the admin under the Gutenberg » Widgets (beta) menu. It’s currently just a proof of concept and has quite a few bugs but gives a preview of how the the widget management screen is shaping up. Benguella said users can currently edit/update widget areas using any available block. The proof of concept implementation in the plugin allows the team to continue polishing the UI and fix bugs in future releases.

\n

\n

The editor is also making progress on mobile, adding quotes and video to the available blocks, rich captions for the image block, and fixes for several critical bugs.

\n

The editor has also recaptured some of its performance gains that were lost in version 5.7, according to recent performance benchmarks.

\n

\n

We’ve had some commenters on previous posts who said they are confused about the difference between WordPress’ core editor and the Gutenberg plugin. The plugin is where active development gets committed. All the new features are put into the plugin first so they can be tested before being rolled into an official WordPress release later down the road. If you want to get access to all the latest features Gutenberg has to offer, install the plugin and you will be able to try it before it lands in core.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 29 May 2019 22:37:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:73:\"WPTavern: Google’s Mobile-First Indexing is Now Default for New Domains\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90195\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/googles-mobile-first-indexing-is-now-default-for-new-domains\";s: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:2957:\"

Google is enabling mobile-first indexing (crawling sites with a mobile user-agent) by default for new domains as of July 1, 2019. These are sites Google defines as “previously unknown to Google Search.”

\n

Mobile searches are the primary way that users engage with the search engine for the past few years, which caused Google to begin prodding website owners to make their content more mobile friendly. Google’s indexing and ranking systems originally used the desktop version of a page’s content, but this can cause problems when desktop and mobile sites contain different versions of content.

\n

Mobile-indexing is not default for all websites yet, but Google started rolling it out more widely in 2018. Google evaluates older websites for readiness based on a variety of factors:

\n

For existing websites we determine their readiness for mobile-first indexing based on parity of content (including text, images, videos, links), structured data, and other meta-data (for example, titles and descriptions, robots meta tags). We recommend double-checking these factors when a website is launched or significantly redesigned.

\n

It’s important to note that there is no separate “mobile-first index.” Google still references a unified index for serving search results. The difference is in whether a page is crawled by a desktop or mobile user-agent.

\n

Prior to responsive web design becoming the industry standard, having a separate mobile site was a common practice. Google is actively discouraging this approach now (although still supporting it), as it often causes confusion for users and search engines alike.

\n

WordPress sites using a responsive theme shouldn’t have any issues with mobile indexing as long as they are not farming out their mobile sites to a separate domain. A responsive theme is usually enough to make a site compatible with this method of crawling.

\n

Website owners can check to see how their sites are being crawled by clicking on the “URL Inspection” tab inside the Google Search Console.

\n

\n

Webmasters of older sites will get a notification from the Search Console when their sites are moved over to mobile-first indexing.

\n

After successfully ramping up mobile-first indexing from a small-scale experiment a few years ago, making it the default for new domains should be a good test for evaluating how aggressively it can be rolled out in the future.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 29 May 2019 15:49:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:60:\"HeroPress: I Grew Up With WordPress, Then WordPress Saved Me\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=2839\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:170:\"https://heropress.com/essays/i-grew-up-with-wordpress-then-wordpress-saved-me/#utm_source=rss&utm_medium=rss&utm_campaign=i-grew-up-with-wordpress-then-wordpress-saved-me\";s: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:10666:\"\"Pull

I grew up in the 90s and 2000s which was a weird time for technology. Part of me remembers carrying around a case of cassette tapes and the sound of dial-up occasionally screaming from the living room. The other half recalls hacking into my dad’s email from the shared family computer for the first time when I was ten. His passwords were never very hard to guess.

\n

In 2004 or 2005, I started taking more of an interest in the Internet. I wanted to start a blog maybe, but I wasn’t sure what a blog even was. WordPress was one of the first things I stumbled on, but it was still an infant compared to what it’s evolved into and I had no idea how it worked. Was WordPress a blogging website? Was it a thing I could build my own site with? How did it work?

\n

I just wanted somewhere to be myself online and WordPress intimidated me. So I dabbled, but I didn’t stay. Myspace and Tumblr would teach me to use HTML, because after all, I just wanted my own place to write online.

\n

Finding My Way Back to WordPress

\n

Eventually, my writing career led me back to WordPress. I was in college, studying English Literature when the opportunity for a Marketing Internship opened up. Around 2011, Chartwells Higher Education, a food service company for college campuses, had launched a huge multi-site network of university dining websites.

\n

Their largest initiative that year was to drive website traffic.

\n

Mine was to keep the students from kicking us off campus because of how much everyone hated Campus Dining.

\n

So I started a blog.

\n

“The Inside Scoop” gave students the perspective of a student who works for campus dining. Both goals were met and I fell in love with the idea of using writing to address business problems. Even more exciting, I finally understood WordPress. Although by then, nearly ten years had passed and WordPress had completely changed.

\n

Life Changed (a LOT), but WordPress Was Always There

\n

At the same time throughout college, I went through a major transition from life as an extremely active athlete to someone with mobility problems. I broke my back, went through everything you can think of to fix it, and ended up with a permanent disability.

\n

Thankfully, I knew by then how to work on a computer in an environment that didn’t necessarily require me to be in an office. It took a few years of adjustment, but eventually, I ended up working for a WordPress-based marketing agency remotely from an RV, which I took anywhere I felt like going.

\n

For a few years, I became a professional tourist.

\n

I’d wake up, get some work done, then adventure all day.

\n

By the time I was done, I could tour any city in a single day and still keep up with content writing. But writing content was all I did. Naturally, I still wanted my own website to write on, but all I had was Tumblr. How to actually set up a WordPress site from start to finish was a mystery to me.

\n

My partner at the agency was supposed to build the site for me, but it never happened. By the time my RV broke down in Rhode Island, 3,500 miles from my hometown, I had lost my chance to build a true travel blog and #vanlife became way too much of a fad to interest me anymore.

\n

Learning to Build Websites with WordPress

\n

My next step was to build my own website. I probably owe a lot of my “self-taught” skills to websites like WP Beginner and WPCrafter, but I really can’t remember how I learned other than trying and failing many times.

\n

After a few YouTube videos, I dove in and built the worst website that you could possibly imagine. It was atrocious, but I liked it enough, so I started writing on TaylorElizabethRose.com and building more websites.

\n

Returning to a Burning California

\n

My next few years were spent spinning my wheels on the East Coast and essentially failing at everything I tried. So I made a plan to move back to California and start my own WordPress-based business. By then I had learned a lot about website management, or so I thought.

\n

The first version of TaylordInk.com was launched in May of 2017 before I made the trip back to California in September.

\n

As we drove into Napa Valley, I noticed how dry it looked and said,“This is a fire hazard.” There were no fire breaks and I had seen what the terrain looks like before it burns when my house burned in San Diego in 2007. Napa and Santa Rosa were primed for flames.

\n

But, how many times in one person’s life can their house burn down?

\n

It was less than two weeks later when the Tubbs Fire came through and burned my entire future. The man I’d been with for two years ended up abandoning me. My business equipment was gone. Any professional clothes I may have had were incinerated. All I had were my dogs and my 2013 MacBook Pro, which happened to be with me at the time.

\n

Nothing but a Laptop

\n

Between October and December 2017, I couldn’t tell you much about what I did or what happened except that I ended up back in my hometown: San Diego. It was a blur of loneliness, depression, and complete failure. Finally, sometime mid-December, I logged into my personal website.

\n

May as well start with my own identity.

\n

It was hacked… and gone. I failed to update while I was swimming in my own sorrow.

\n

Luckily, my friend from my agency days actually had a backup of the original site. So I salvaged the posts from his files and started rebuilding. I really didn’t get very far until much later in 2019. I just kept designing and redesigning the same pages over and over again.

\n

On the second or third time I logged in after the fire, I saw the WordCamp San Diego information on the Dashboard and bought a ticket before I could change my mind about going.

\n

Discovering the WordPress Community

\n

WordCamp San Diego didn’t happen until months later, but it was the next time I really did anything productive in my life. It was kind of my last-ditch attempt to start a WordPress business or any business at all.

\n

I didn’t know what to expect. I didn’t know who I would meet, or how (or if) I would fit in. I certainly never expected to find a community with open arms.

\n

A weight was lifted from my shoulders almost immediately. Where had all these nerds been my whole life? These were my people!

\n

There’s a comfort that comes from fitting into a community and finding your people.

\n

Being in the company of like-minded people makes the future less bleak. I had hope again for the first time since the fire stole that from me.

\n

At some point during that WordCamp, a girl named Sochi found out that I was a content writer. She dragged me by the hand to meet Matt Cromwell at the Give booth. It was extremely intimidating because the entire Give Team was sitting there staring at me. I didn’t know it then, but I was meeting my own future coworkers.

\n

Give was hiring a content writer! In fact, they were close to hiring someone else, but I was intrigued. So I inquired the next day and disrupted Matt’s hiring process a bit.

\n

The next week, I joined Team Give.

\n

Over the next year, I spoke at 4 WordCamps and attended 6 or 7 total.

\n

Working at Impress.org and participating in WordCamps has been incredible and I’ve learned more about WordPress over the past year than in all the years before. I don’t think I would have succeeded as well with my own WordPress-based marketing agency without the community.

\n

More importantly, I wouldn’t have made it through some of the hardest times in my life without WordPress. It was there when I needed to work remotely and it was there when I needed a helping hand to lift me back out of tragedy.

\n

The post I Grew Up With WordPress, Then WordPress Saved Me appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 29 May 2019 15:00: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:11:\"Taylor Rose\";s: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:35:\"WPTavern: Happy Sweet 16, 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=90197\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/happy-sweet-16-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:8623:\"

Over the weekend, the WordPress community celebrated 16 years since Matt Mullenweg and Mike Little forked the B2/cafelog blogging platform to create the first official release of WordPress on May 27, 2003. It launched with a new admin interface, manual excerpts, intelligent line breaks, a link manager, and was compliant with XHTML 1.1 standards.

\n

image credit: Web Design Museum

\n

The first two months of posts on the WordPress development blog read like selections from a time capsule, capturing the early history of the software. Mullenweg shared his journey in a “thinking out loud” style throughout the process of selecting the best route for templating and other decisions that laid the groundwork for the first release. Since those early days, WordPress has outpaced all its early competitors to become the most popular CMS by a wide margin.

\n

Sixteen years later, the software is available in more than 200 languages and is now used by 33.9% of the top ten million websites. WordPress’ uncommon growth can be attributed to its unique combination of leadership, stability, and a community of thousands of contributors and entrepreneurs that are empowered by its open source licensing.

\n

Many WordPress product businesses, part of a commercial ecosystem that Mullenweg estimates at $10 billion/year, hosted sales, giveaways, and promotions in honor of the anniversary. Friends of WordPress all over the world celebrated the software’s birthday with cakes and tributes.

\n
\n

WordPress turned 16 today Happy 16th Birthday to WordPress https://t.co/1DCZ25Cr0Y pic.twitter.com/tf9LO3Qf9R

\n

— Code Pixelz Media (@codepixelzmedia) May 27, 2019

\n

\n

“We are proud to be a part of the WordPress community! Through thick and thin, WordPress has brought great innovation and inspiration to the online world,” WordPress Dhaka meetup organizer Lincoln Islam said.

\n

The WordPress community in Ahmedabad gathered together to celebrate with dinner, a custom Wapuu cake, and games. Ahmedabad, which is located in western India, is the largest city in the state of Gujarat. WordPress 4.6 was the first release to ship with a full Gujarati translation in August 2016, making the software more accessible to approximately 65.5 million Gujarati speakers worldwide. A year later, Ahmedabad hosted its first WordCamp and another followed in 2018.

\n
\n

It was awesome celebration of WordPress 16th Birthday! Discussion, Cake, Dinner and Game with WordPress Ahmedabad Community #WordPress16Birthday #WP16 #WordPress #WPAhmedabad #WPAhmedabad #Meetup pic.twitter.com/12gdpa6R3z

\n

— Chetan Prajapati ⓦ (@iamchetanp) May 27, 2019

\n

\n

The team at Bluehost published a video with a few short greetings they recorded for WordPress’ 16th birthday. When asked why they love WordPress, several said they are grateful for the opportunities and the friendships the community has brought them. Check out the #WP16 and #WordPress16thAnniversary hashtags for more WordPress cake pictures and celebrations.

\n
\n

Happy birthday WordPress! \"?\"

\n

16 years ago, on May 27, 2003, WordPress was released. We believe in WordPress and continue to be committed to growing and contributing to the WordPress open source project! Here\'s just a few of the things we love WordPress for. #WP16 pic.twitter.com/kEgLQMGnpG

\n

— Bluehost (@bluehost) May 27, 2019

\n

\n
\n

It was very amazing day to celebrate @WordPress 16th Birthday. My journey with #WordPress has been very exciting and surprising. Many more years to come with an amazing experiences.
Happy16th Birthday WordPress\"♥\"\"?\"@wcUdaipur #WP16 #WordPress16thAnniversary#Celebration #loveWP pic.twitter.com/ncyVjdZCms

\n

— Nidhi Jain (@jainnidhi03) May 27, 2019

\n

\n
\n

We had a delicious cake and a fun brain-teasing quiz with @WordPress folks. \"?\"
The cake was cut by rtCamper @am_pra_veen, who is just two years older than WordPress. \"?\"

\n

Happy sweet 16, @WordPress. Many more to come! \"?\" #WP16 pic.twitter.com/uLffaqjQni

\n

— rtCamp (@rtCamp) May 27, 2019

\n

\n
\n

WordPress is 16. Wow, I have been using it for 15 years. What an impact it has had on my life. Thank for the job, the friends and the community. I \"❤\" WordPress.

\n

— Jonny Harris \"??\" (@thespacedmonkey) May 28, 2019

\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 28 May 2019 18:53:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:44:\"WPTavern: In Case You Missed It – Issue 24\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90172&preview=true&preview_id=90172\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/in-case-you-missed-it-issue-24\";s: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:7125:\"

photo credit: Night Moves – (license)

\n

There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.

\n

Marcel Bootsman Is on His Way to WordCamp EU

\n

Earlier this week, Marcel Bootsman began walking his way to Berlin, Germany, the host city for WordCamp EU. The journey is more than 700 kilometers and Bootsman estimates it will take him about 30 days to reach his destination. Along the way, Bootsman has been publishing blog posts to keep readers informed of his progress.

\n
\n

Made it!#WalkToWCEU pic.twitter.com/sQ1XUv8Hje

\n

— \"??\" Marcel Bootsman (@mbootsman) May 24, 2019

\n

\n

So far, he’s published a post a day with stories that include a run-in with a bull in an open field, angry cyclists, and amazing photos of the scenery. You can follow along via the WalkToWordCamp.EU website. Donations raised from the event will go to DonateWC.

\n

WPSiteSync v1.5.2 Released

\n

The folks over at ServerPress have released a new version of WPSiteSync. This plugin enables users to migrate specific content from one site to another without the need to update target URLs for media files. This version fixes a couple of UI related bugs and interactions with Gutenberg.

\n

CannaBiz 2.4 Released

\n

Robert DeVore has released CannaBiz 2.4, a WordPress theme that’s specifically tailored for the Cannabis industry. This release includes two new action hooks, a Yelp social media link, CSS style updates, new customizer controls for button colors, and third-party plugin style updates.

\n

Alternative Gutenberg Block Styles Library

\n

Carolina Nymark has created a website and GitHub repository dedicated to creating and sharing alternative styles for Gutenberg blocks. The website contains tutorials on how to create new block styles, add them to child themes, and how to contribute to the library.

\n

Patches That Get Lost in the Void

\n

Daniel Jalkut describes what he experienced when trying to contribute a patch to WordPress to fix an issue he and his clients were having. Unfortunately, it wasn’t a good one.

\n

When somebody comes to your project with a well-thought-out, unit-tested fix, and is met by radio silence? The chances are high that they will never come back again. I have submitted WordPress patches in the past, but after this experience I don’t know if I will bother submitting them again. That’s a big change in my perspective on how the WordPress team works, and on how it should work.

\n

Jalkut isn’t the first nor will he be the last to have an experience like this. WordPress is a large project that encompasses many areas and if a particular ticket is not in line with higher priorities, the chances of it slipping through the cracks are pretty high.

\n

Human Made Launches A New Product but Some People Have No Idea What It Is

\n

Human Made has launched a new product called Altis which is a DXP or Digital Experience Platform for WordPress. After reading the press release and the associated blog post, I found it difficult to understand what the product is and who it’s for and I’m not the only one.

\n
\n

Maybe human made but not intended for humans. WTF did I just read? https://t.co/iM2sHKhLwu

\n

— Russell Heimlich (@kingkool68) May 21, 2019

\n

\n

Noel Tock, Chief Growth Officer, and Partner at Human Made chimed in and admits that the language used to describe the product is geared towards the enterprise market. He explains that Altis is an evolution beyond WordPress that supports personalization, artificial intelligence, experimentation, and faster developer experience.

\n

In a nutshell, Altis is a highly specialized version of WordPress with a UI and features that are geared towards specific clients. If you think you can explain what Altis is in a simpler way, please give it a shot in the comments.

\n

Tips for Speaking at Your First WordCamp

\n

Justin Foell of WebDevStudios explains what you need to know if you’re speaking at your first WordCamp. If you’re looking for tips on applying to speak at WordCamps, Jennifer Bourn has you covered.

\n

Speaking at Your First WordCamp? Here’s What You Need to Know!

\n

\n

After the Deadline Alternatives

\n

In light of After the Deadline being removed from Jetpack, users have been searching for alternatives. This post on WordPress.com highlights a few of them.

\n

WPCampus Diversity, Equity, and Inclusion statement

\n

Diversity, Equity, and Inclusion

\n

\n

That’s it for issue twenty-four. If you recently discovered a helpful resource or post related to WordPress, please share it with us in the comments.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 25 May 2019 02:19: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:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: New GitHub Sponsors Tool Draws Concerns 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=90081\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/new-github-sponsors-tool-draws-concerns-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:9474:\"

GitHub has launched a new Sponsors tool that allows open source developer to receive financial support. The program is rolling out slowly and currently has a waitlist for open source contributors or maintainers who want to join.

\n

\n

For the first year developers are in the program, GitHub will cover all the payment processing fees and has pledged to match all contributions up to $5,000.

\n

Individual developers participating in the program can customize the funding options displayed when potential supporters click on the Sponsor button. They can add links to other popular funding services, such as Open Collective, Community Bridge, Tidelift, Ko-fi, and Patreon. Open source projects an also specify funding models for contributors by adding a .github/FUNDING.yml file to the project’s master branch.

\n
\n

Just enabled @github\'s awesome new Sponsor button for @parceljs with a link to our @opencollect! \"?\" pic.twitter.com/DJnPAtahne

\n

— Devon Govett (@devongovett) May 23, 2019

\n

\n

GitHub has an advantage over other competing funding services by having its Sponsorship model embbeded in the GitHub workflow where much of the work actually takes place. However, this also raises concerns about how sponsor expectations may influence a project’s development.

\n

“You can now sponsor developers as a seamless part of your familiar workflow,” GitHub open source project manager Devon Zuegel said in the announcement. “When a contributor answers your question, triages your issue, or merges your code, you can head to their profile—or simply hover over their username—to sponsor their work.”

\n

\n

Sponsorship is a somewhat subjective term and GitHub isn’t defining what it means here in the context of marrying it to a contributor’s workflow. For some, it may mean a no-strings-attached donation. For others, the idea of sponsorship always comes the expectation of a return on an investment.

\n

Ruby on Rails creator and Basecamp founder David Heinemeier Hansson was one of the most prominent to raise concerns about GitHub’s Sponsors program on Twitter. He sees it as “a grave risk to open source.”

\n

“’Why haven’t you fixed my issue yet!? I sent you $10! I demand you honor your obligations here. I paid you,’ welcome to small-donation open source 2019,” Hansson said.

\n

“I’m sure GitHub had all the right intentions here. And I’m sure this will work out well for a select few developers who will amass enough donations to ignore individual claims to their time. But I think it’s a grave risk to the culture of open source.”

\n

Hansson referenced a recent keynote he delivered at RailsConf 2019 titled “Open source beyond the market,” challenging those whose initial reactions are simply that “donations are a good thing.” Bringing the concept of sponsorship a into the workflow introduces a transactional nature to the work, with unavoidable marketplace expectations that can complicate a project’s development.

\n

“The marketplace norms are hard to escape,” Hansson said in his keynote. “They seep into our unconsciousness. There are plenty of open source users who think themselves less as a recipient of a gift and more like customers with warranty claims, that they’ve done the makers of said open source software a great honor by merely choosing to use their thing.

\n

“In fact, it’s kind of a natural extension of a society that worships consumerism above little less. A natural extension of ‘the customer is always right,’ of the adversarial relationship between buyer and seller.”

\n

Others have expressed more specific concerns, such as Microsoft’s GitHub becoming the dominant payment platform for open source developers, sponsors receiving priority consideration in issues and PRs over user and project needs, and developers deliberately introducing bugs in order to solicit donations.

\n
\n

Already seeing “I will prioritise your issues” in the ‘rewards’ sections on the first sponsor-enabled accounts… so.. you called it

\n

— Lasse Rafn (@LasseRafn) May 23, 2019

\n

\n

Pia Mancini, co-founder of Open Collective, wrote a response to the concerns that people were sending her way on Twitter.

\n

“I am really happy to see such an important player in the ecosystem helping out with the problem of sustaining open source,” Mancini said. “Sustaining our commons is an effort that requires everyone to contribute. I am glad to see Github come on board.”

\n

This idea of the sustainability of open source and the “tragedy of the commons” is one that Hansson and many others reject, but it is one that is commonly embraced by copyleft advocates. It works for Open Collective’s business model, but comes with its own flavor of reciprocity. Open Collective is distinct in that its funding service is removed from the direct workflow of software development, instead of deeply integrated like GitHub’s Sponsors tool.

\n

Mancini said that her company can “happily coexist with GitHub Sponsors” because of Open Collective’s chief differentiators. It was built for projects, not individuals. It offers full transparency about where funds come from and how they are spent. The company also manages the paperwork and tax forms required for fiscal sponsorship.

\n

“Open Collective is for funding projects as opposed to individual maintainers,” Mancini said. “We strongly believe in supporting communities as a whole, as well as the individuals that make up that community. This helps with ensuring more diversity, and less concentration of power and decisions on one maintainer.”

\n

She also cautioned against GitHub trying to swallow up too many aspects of the open source community and injecting its own corporate interests. She hints at a line that the company has not yet crossed but many are still wary of what Microsoft plans to do with GitHub.

\n

“Of course, there’s risk: centralization and lock-in are very risky for communities,” Mancini said. “GitHub is Microsoft, which has its own metrics in mind, and it will be difficult for them to be independent, regardless of the good faith of the folks involved.

\n

“Attempting to own all aspects of the open source community is a harmful strategy. So far, I don’t think GitHub is trying to do this. They are in a position to help, and they are open to collaborating with existing players.

\n

“Does it compete with Open Collective? To some extent. But our growth has never been primarily driven by individuals giving to individuals, but by companies giving to projects. GitHub Sponsors does not solve the need sponsor companies have for invoices and a legal entity to engage with for their vendor systems and documentation requirements.”

\n

GitHub’s intentions may simply be a recognition of what open source software has matured to become – a driving force of innovation in all industries and an effort worthy of financial support. Giving developers an easy way to receive some reward for their contributions seems rather innocuous, but the concern is that Microsoft cannot foresee the long term consequences of its sponsorship implementation inside GitHub’s workflow. Open source project maintainers who pressed GitHub for more consideration of open source workflows may get more than they bargained for.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 24 May 2019 18:40:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:85:\"WPTavern: Automattic Acquires Prospress, the company behind WooCommerce Subscriptions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90102\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"https://wptavern.com/automattic-acquires-prospress-the-company-behind-woocommerce-subscriptions\";s: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:4052:\"

Automattic has acquired Prospress and its flagship WooCommerce Subscriptions product, along with the company’s entire suite of e-commerce plugins and automation tools. Prospress’ 20 employees will be joining Automattic to continue developing and supporting their products.

\n

There are no immediate changes planned for current WooCommerce Subscriptions customers. Automattic will begin working on a roadmap for the product after integrating the Prospress team into the company.

\n

In the announcement Q&A, Prospress founder Brent Shepherd said he is excited to see how Subscriptions will integrate with Automattic’s existing products and offered a glimpse at what they may be working on in the near future:

\n

In more specific terms, that could mean looking at closer relationships with how payments are handled, or integrations with other platforms such as WordPress.com. There are also a couple of things to solve both in WooCommerce and subscriptions to help them scale better. Interestingly, these challenges are almost identical for the two codebases. By working more closely to solve them than we ever could apart, I hope we can do a better job of implementing solutions and in a shorter time frame.

\n

WooCommerce Subscriptions can already be purchased a la carte and used on WordPress.com stores, so nothing will change in this department. I asked Paul Maiorana, head of partnerships for WooCommerce, if there are any plans to integrate Subscription functionality with Jetpack sites, as the plugin’s team is currently pursuing a Membership feature that is essentially recurring payments.

\n

“We’re excited to learn from the Prospress team as they’re experts in this space, and could see Memberships potentially leveraging some of the Subscriptions code to avoid duplicating efforts — but we have no plans to integrate the products,” Maiorana said.

\n

The Prospress acquisition also includes AutomateWoo, a marketing automation tool, and Robot Ninja, which offers automated checkout testing for WooCommerce stores. Prospress acquired AutomateWoo in June 2018 as a complementary product to Subscriptions. There are no immediate changes planned for these products that would affect customers.

\n

Prospress has been deeply invested in the WooCoommerce open source project for many years. WooCommerce has 834 contributors and Shepherd is currently among the top 10. His company committed to the five for the future initiative last year by sponsoring one of its employees to contribute full time to WooCommerce core. For the past five years Shepherd has also co-organized the WooCommerce San Francisco meet-up.

\n

Cornering the market on Subscriptions and being able to ensure a tight integration for customers gives WooCommerce a more competitive edge in the broader e-commerce space. Prospress’ smaller products are also strategic additions to WooCommerce’s offerings. If Automattic can integrate the marketing automation and automated checkout testing tools in one hosted package, these tools have the potential to greatly increase customer’s success and confidence in their WooCommerce powered stores.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 23:20: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: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:69:\"WPTavern: Take the 2019 WP&UP Mental Health and Well-Being Survey\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90124\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/take-the-2019-wpup-mental-health-and-well-being-survey\";s: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:652:\"

WP&UP is a mental health and well-being charitable organization founded by Dan Maby in 2018, whose mission is to promote positive mental health throughout the WordPress ecosystem.

\n\n\n\n

The organization is currently hosting a survey to better understand the needs of the community.

\n\n\n\n

The questions cover the general work environment, general mental health and well-being, and specific work-related mental health and well-being. The survey will close next week and the results will be anonymized, open-sourced, and shared with the 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 22:29:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:34:\"Matt: Prospress joining Automattic\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=49589\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://ma.tt/2019/05/prospress-joining-automattic/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1351:\"

As you may have read on the WooCommerce blog, Prospress blog, WP Tavern, Post Status, or Techcrunch, the team at Prospress is joining forces with WooCommerce at Automattic to help accelerate the adoption and democratization of ecommerce across the web. Whew that’s a lot of links! Prospress was best known for their extension that allowed many types of Subscriptions on top of WooCommerce, but also has some cool marketing automation and automated testing tools as well. I love that Prospress was already a Five for the Future company, which aligns really well with Automattic’s long-term goals and contributions to the wider 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 22:18:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"Post Status: Automattic has acquired Prospress, the makers of WooCommerce Subscriptions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=62313\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://poststatus.com/automattic-has-acquired-prospress-the-makers-of-woocommerce-subscriptions/\";s: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:5108:\"

Automattic has acquired Prospress, the team led by Brent Shepherd, and the makers of the largest WooCommerce extension, WooCommerce Subscriptions.

\n\n\n\n

The acquisition secures a future for Subscriptions under the primary Automattic umbrella, and it’s an increasingly important part of WooCommerce’s success.

\n\n\n\n

Subscriptions offers the most powerful and flexible subscription option in the eCommerce market, and it’s common for stores to use WooCommerce because they need Subscriptions.

\n\n\n\n

Other providers, namely market leader Shopify, do not offer an in-house subscription option, and their third-party options are not nearly as advanced as WooCommerce Subscriptions.

\n\n\n\n

Prospress brings a couple other products and services with them
— AutomateWoo and Robot Ninja primarily — but Subscriptions is the real breadwinner. It has long been the highest revenue extension in the WooCommerce marketplace.

\n\n\n\n

Paul Maiorana, WooCommerce’s Head of Payments, Shipping, and Partnerships, tells me, “Subscriptions is an important differentiator for WooCommerce amongst eCommerce platforms, and we’re really excited to now be working closely with the Prospress team to create a more unified experience.”

\n\n\n\n

I have known Brent and his team for a long time, and I’ve used Subscriptions for many years. It’s an outstanding and complex project that requires enormous amounts of testing, a skilled development team, and a lot of care.

\n\n\n\n

In 2017, the support structure changed for third-party WooCommerce extensions, which led to an immediate surge of support hiring by the largest extension providers — namely Prospress and SkyVerge — for whom, for the purpose of disclosure, I do contract work.

\n\n\n\n

Support is the biggest component of a plugin company, especially for a complex one like Subscriptions, which interfaces (sometimes in very different ways) with dozens of payment processors. I have seen spec documentation for their proposed new features, and it is astounding how much detail is required to be outlaid before a single line of code is changed or written.

\n\n\n\n

With Automattic, a company that formerly consisted of a few dozen folks now has the backing of hundreds of “Happiness Engineers” to help manage the load.

\n\n\n\n

The primary risk I see for Subscriptions with Automattic is that it will get lost in the fray if Prospress developers are pulled to other work and more pressing needs. I have perceived this to be the case with their ownership of WP Job Manager, WooCommerce Bookings, and some other extensions — though none with the significance of Subscriptions. I think the strategic importance of Subscriptions should keep that at bay under good management, and I know Automattic management understands that strategic importance.

\n\n\n\n

Automattic will eventually go public, I’m almost certain. Strategically, I fully believe the Prospress acquisition is the right move for them. If I were involved, I would’ve been trying to make this acquisition for years now.

\n\n\n\n

Having significant revenue streams under the scope of a company out of your control is a risk, to my thinking as a theoretical investor. I would take this now in-house feature set direct to marketing channels against Shopify
— which is an absolute juggernaut in the eCommerce space today, particularly among high revenue generating stores.

\n\n\n\n

I don’t know what led Brent to make the choice to join Automattic now, but it’s a much-deserved exit after something like eight years of work.

\n\n\n\n

Brent said the following in the announcement Q&A:

\n\n\n\n

I’m extremely proud of what we’ve achieved at Prospress. I’ve had the great pleasure of having some amazing people join me over the years. Together I believe we’ve advanced a mission that matters to me — so much so that it predated Prospress and even WooCommerce.

I believe joining Automattic is the best next stage for Prospress, and I am personally excited to lead the transition and work with the Automattic team to further WooCommerce.

\n\n\n\n

I’m very happy for Brent and the entire Prospress team. I hope they made a fortune with this acquisition; in my mind, Subscriptions is one of the key reasons for WooCommerce’s amazing growth as a platform. I think they will do great there, and I have no doubt they will stay committed to making Subscriptions continue as a terrific tool in the toolbox that is 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 19:31: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:\"Brian Krogsgard\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:74:\"WPTavern: Google Updates Mobile Search Results to Include Website Branding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90077\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://wptavern.com/google-updates-mobile-search-results-to-include-website-branding\";s: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:1999:\"

Google is rolling out an update to mobile search results that includes website branding. The new design displays a website’s name and icon at the top of the listing so users can easily scan results. If the result is an ad, it will be indicated in bold next to the website’s address. Below is a before and after look at the visual refresh of the mobile search results page:

\n

image credit: Google

\n

Google automatically fetches a website’s favicon for search results, so most website owners with a favicon already in place should not have to do anything to enable branded mobile search results.

\n

In 2015, WordPress 4.3 added Site Icon support to the Customizer, so users do not need to rely on a plugin to upload a favicon. WordPress stores the icon so that users do not have to upload it again when switching themes.

\n

\n

A simple, recognizable favicon establishes a visual identity for your site, and Google’s updates to mobile search results should be a strong reminder not to forget one when building a new site. Site owners may even want to spend more time designing the icon, now that a favicon’s usefulness extends beyond browser tabs to lend more authority to search results. The changes are just now rolling out to mobile but will likely be coming to desktop searches in the near future.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 17:06:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WPTavern: Elementor Launches Hello Theme on WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/elementor-launches-hello-theme-on-wordpress-org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5367:\"

Elementor launched its Hello theme on WordPress.org this week. After just a few days in the directory, the theme already has more than 10,000 active installations. It is essentially a blank starter theme that offers 100% compatibility with Elementor.

\n

\n

Page builders with a large user base are in a unique position to influence the WordPress theme market. Loyal users will often select a page builder before choosing a theme from a limited pool of those that boast compatibility with their preferred plugin. Elementor is no exception, with more than 2 million installations and a 4.8-star average rating on WordPress.org.

\n

Lately the trend with some of the most popular and intuitive WordPress themes is to offer a strong, niche design out of the box, where users don’t have to make too many choices or fiddle with settings. Hello takes a different path, opeorating as more of a conduit to the Elementor page template library.

\n

The theme’s screenshot shows a home page designed in Elementor but the actual theme has very few styles and doesn’t look like anything out of the box.

\n

\n

Once installed, the first step is to create a page and select “Edit in Elementor.” From there users can select from a library of different landing page templates or start building their own layouts from scratch.

\n

\n

Hello is not a new theme. Elementor first released it on GitHub in March 2018. Hosting it on WordPress.org allows users to more easily install it and get automatic updates for improvements and security fixes.

\n

“The plugin repository played a huge role in Elementor’s exceptional growth, and we hold similar high hopes for the Hello theme,” Elementor CMO Ben Pines said.

\n

There are a few major drawbacks to using the Hello theme that may hinder its potential growth. Access to headers, footers, and widgets is restricted to Elementor Pro users. This seems like a confusing way to build a WordPress site and might be a useful detail to include in the theme’s description on WordPress.org. If there’s another way to access headers and footers without purchasing Elementor Pro, I wasn’t able to find it.

\n

WooCommerce store owners should be aware that the Hello theme does not yet offer comprehensive support for WooCommerce page styles. Although the release post advertises the theme as having “out-of-the-box” compatibility with WooCommerce, the store pages are bare bones and not very attractive. One user commented that the checkout and cart pages do not look very inviting and asked if it will be possible to edit fonts and colors with Elementor.

\n

Elementor representative Matan Naveh responded to multiple concerns about WooCommerce support and said that full compatibility is still in development:

\n

WooCommerce is a highly complex plugin and any pages that rely on its basic elements (e.g. Cart, My Account, Checkout, etc.) are even more so. The level of complexity is such that changes in something as routine as a WooCommerce update could cause havoc on a layout, resulting in a devastating effect on the webpage’s functionality.

\n

Currently, Elementor enables you to customize the areas surrounding the WooCommerce elements. Take the cart page, for example – You may not be able to customize the table itself, but you can customize the title or the area where the table is located. You can also insert your own images, backgrounds, and content according to your needs (e.g. adding an FAQ).

\n

We are considering several options for achieving full compatibility with WooCommerce. But this is still in its development stages.

\n

Some users who switched from the Astra theme, another one commonly used by Elementor users, have reported significant (50%) decreases in loading time on real world sites after switching to the Hello theme. Elementor claims that it is “the fastest WordPress theme ever created,” but the comparison benchmarks posted don’t include any themes that are known for high performance.

\n

Elementor is working on creating a child theme for Hello. It is currently in development on GitHub and the team is working on getting it approved for WordPress.org.

\n

The primary purpose of the Hello theme is to offer compatibility with the page builder, but it is not recommended for users who are not using Elementor.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 02:10:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:73:\"WPTavern: WPWeekly Episode 353 – Slack of Boundaries and A Walk to WCEU\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90052&preview=true&preview_id=90052\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wptavern.com/wpweekly-episode-353-slack-of-boundaries-and-a-walk-to-wceu\";s: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:2125:\"

In this episode, John James Jacoby and I discuss an article published by Vox on how Slack is not improving productivity, especially in large team environments. We highlight what’s new in WordPress 5.2.1, why libraries are important to the communities they serve, and new security features in WordPress 5.2. At the end of the show, we send a shoutout and good wishes to Marcel Bootsman who has begun his walk to WordCamp EU.

\n

Stories Discussed:

\n

WordPress 5.2.1 Released

\n

The Productivity Pit: How Slack Is Ruining Work

\n

Marcel Bootsman begins his walk to WCEU

\n

WordPress 5.2 Improves the Security of Automatic Updates

\n

Loveland Public Library to Host Free Beginners WordPress Class Online May 22, 2019

\n

Transcript:

\n

EPISODE 353 – Slack of Boundaries and A Walk to WCEU Transcript

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, May 29th 3:00 P.M. Eastern

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #353:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 22 May 2019 22:47: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:\"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:48:\"HeroPress: Growing Through Translating WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=2828\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:148:\"https://heropress.com/essays/growing-through-translating-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=growing-through-translating-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:20861:\"\"Pull

このエッセーは日本語でも読めます。

\n

I have spent most of my adult life knowing WordPress. In November 2003, a few months after I discovered WordPress, I gave it a spin on my personal blog. A few months later, I started contributing in the form of translating WordPress core and documentation into Japanese.

\n

Today, I make a living as a project and community manager in the field of translation & localization. I get to help people all over the world publish their voice online using their own language, while raising two kids in Tokyo, Japan. This is all thanks to WordPress, which showed me the brand new world of open source I never knew existed, and those who had given me the opportunity to participate in it.

\n

Let me share my story about how WordPress has changed my life.

\nWordCamp Tokyo 2018 organizing team & volunteer staff\n

Discovering WordPress

\n

I first found WordPress in the summer of 2003. At that time, with a degree in graphic design at a state university in the Midwest, I was working in a field that had nothing to do with design or web. The small web marketing company I joined after graduation couldn’t make it through the dot com bubble. When I moved back to the U.S. with my then-husband for him to go back to graduate school in Detroit, I couldn’t re-enter the field because of my lack of experience. I settled with a temp in-house translator/admin assistant position at an automotive company to financially support the household. You could say it was a practical choice. Or, to put it frankly, I just gave up and went with the demand for the clerical job with Japanese skill.

\n

The good thing that came out of it was that I had plenty of time after work. My ex-husband had to study all day, and my temp job was precisely 9-5. Every night, we rarely watched T.V. or went out but headed for our computers. I worked on my own website and sometimes friend’s site for a fee, using just HTML and a little bit of CSS. Back then, reading blogs written by web designers was the best way to follow up-to-date news and techniques of frontend development.

\n

Inspired by those blogs in both English and Japanese, I decided to start mine. I published my first post on a Movable Type blog in April 2003. I wrote almost every day for a few months. Then as I was getting frustrated with some aspects of Movable Type, I tried several blog engines including WordPress.

\n

With WordPress, the process of customizing blog design through edits to PHP files was straightforward and enjoyable, so I got addicted to working with WordPress right away. I almost had no experience beyond HTML and CSS before then, but I was surprised that I was able to create a dynamic site myself.

\nMy blog design between 2003-2019\n

Translating WordPress

\n

In November 2003, I re-launched my blog using WordPress. In December, I learned that there was a person named Otsukare who made a Japanese version of WordPress. This fork of WordPress, called “WordPress ME (Multilingual Edition)”, had the first comprehensive WordPress resource site in Japanese, with documentation Wiki and phpBB forums. Through the forum, I started helping him with translating documentation from English to Japanese.

\n

WordPress stayed as a relatively minor blog tool/CMS in Japan for years, but that didn’t change the fact that it was a piece of software that I really enjoyed using. I kept translating Codex, participated in theme competitions, and helping others on the forums. It was the first time for me to experience being part of an open source community and working together with people I’ve never met in person (and without being paid!).

\n

What kept me going was the feeling that I’m part of something bigger. I loved using WordPress, and it was exciting that I could help spread the word. WordPress community gave me a chance to work with people around the world — years before “remote work” was a universally recognized word. There were no free voice/video chat applications, no Slack, but the interpersonal connections have grown deeper because everyone in the community was centered around a tool to deliver your voices to others far from reach.

\n
\n

WordPress Polyglots at #WCEU contributor day, translating to so many languages! Thank you for coming! \"❤\"\"✨\" pic.twitter.com/bGvnfTIBYI

\n

— WordCamp Europe (@WCEurope) June 26, 2016

\n

\n

 

\n

Organizing WordCamp Tokyo

\n

In 2007, I went to WordCamp San Francisco and had a short conversation with Matt Mullenweg. I vaguely remember my question – something like “I love WordPress, and I want to help spread it more in Japan. What should I do?” But I still clearly remember his answer.

\n

“You should do a WordCamp.”

\n

Although it probably was just a casual suggestion since we happened to be at a WordCamp, that idea stayed with me. That short interaction was no doubt the initial trigger of our first WordCamp in Japan, a year later. I was living in the U.S., but that really didn’t matter. Japanese WordPress translators, developers, and users who knew each other through the forums and blogs all worked together to run WordCamp Tokyo 2008.

\nWordCamp Tokyo 2008. Photo credit: Odyssey\n

Career and Leadership

\n

My career also changed dramatically between 2006 and 2009.

\n

Because I gained general blog template customization skills through working with WordPress, freelance work started to come in. I also had the opportunity to write WordPress books in Japanese. Thanks to WordPress, I was able to learn and practice the idea of ​​Web Standards. My ability to write solid markups was valued, and I got my first full-time technical job as a frontend engineer at an ad agency in a suburb of Detroit.

\n

In April 2009, I started as a part-time Happiness Engineer (customer support for WordPress.com) at Automattic, then in 2010 offered a full-time position. Since then, my role had evolved into the field of localization, and I’m happy to tell you that my 10th anniversary is coming up soon.

\n

In the past few years, I’ve taken up some more global responsibilities within the WordPress community, such as one of the Global Mentors for the Polyglots Team, and lead organizer of WordPress Translation Day 4. Most recently, I was selected as the global leader of the first WordCamp Asia (planned for 2020 in Bangkok, Thailand).

\n

Growing and Giving Back

\n

The WordPress community taught me so much.

\n\n

Sometimes the process of gaining such new insights was painful, but I still feel I’m lucky to have been given challenges that made me grow.

\n

To give back, I want to continue helping communities outside of the English speaking world. I believe that’s the most powerful thing I can do to remove the barriers on the web and the vast world that it touches.

\nTokyo WordPress Meetup / WordPress Translation Day 4\n

 

\n

WordPress を通して成長できたという話

\n

高野直子

\n

 

\n

WordPress のことを知ったのは、約16年前でした。

\n

その数カ月後には元持っていたブログを WordPress に切り替え、さらにまた数カ月後には現在も続いている WordPress への翻訳という形での貢献を始めることになりました。振り返ると、社会人になってからほとんどの年数を、WordPress とともに過ごしてきたわけです。

\n

私が現在東京で子育てをしながらグローバルかつ柔軟な環境で働くことができるのは、新しい世界を見せてくれ、機会を与えてくれた WordPress の存在のおかげです。

\n

今こうやって、「WordPress との関わりが自分と周りの『バリア』を破ったこと」というテーマで記事を書かせてもらうにあたって思いを巡らせてみると、本当にこのソフトウェアと出会わなければまったく違う人生を歩んでいただろうなと思います。多くの人たちにもめぐりあうことはなかっただろうし、仕事はもちろん、住んでもいる場所も違っていたかもしれない。

\n

そんな、私にとってとても大きな存在の WordPress が、迷える20代を過ごしていた自分をどんなふうに変えてくれたかのお話をしようと思います。

\n

WordPress との出会い

\n

私が WordPress を知ったのは、2003年の春か夏頃でした。その頃の私はというと、高校留学後にアメリカ中西部の地方大学でグラフィックデザインの学位を取ったものの、新卒で入った小さな会社がドットコムバブルで立ち行かなくなったり、当時の夫の大学院入学のためにアメリカに戻ってきても経験不足で Web 関係の仕事には就けなかったり。とは言え家計を支える立場を選んだわけで、一旦やりたかった仕事はあきらめて、日系自動車会社で派遣をやっていた日々でした。インハウス翻訳者兼事務補助職のような感じで、お給料と需要を優先して良く言えばがむしゃらにがんばっていたし、悪くいうと目の前のことでいっぱいいっぱいという状況。

\n

ただ、そのころ時間だけはたっぷりあったんです。夫は暇さえあれば勉強していたし、派遣の仕事もそんなに忙しいものではなかったので、定時に帰って夕食後はテレビを見たり出かけたりはせず、それぞれパソコンに向かっていました。

\n

趣味やフリーランスの制作者として細々と HTML 手打ちのサイトなんかも作っていたのですが、Web デザイナーが個人で発信する情報はその当時ブログを読むのが何より最新で、ワクワクするものでした。

\n

そこからいきなり WordPress をインストールしたわけではなくて、まずは一番簡単そうだった Blogger.com を触ってみて制限がちょっと多すぎると感じ、Movable Type をしばらく運用してあまり相性がよくないかもと感じた、というのが私のブログ作りのスタートでした。その後ぴったりなタイミングで b2 からフォークしたリリース版を出したばかりだった WordPress に出会いました。

\n

PHP のファイルを触りながら自分のブログを作っていく過程が本当に楽しくて、いつのまにか WordPress にハマっていました。そのころはシンプルな構成だったからというのはもちろんあるんですが、それまでほぼ HTML と CSS しか書いたことがなかった自分がいつのまにかそんなふうにいわゆる「動的」サイトを作れるようになっていくことに自分でも驚きました。

\n

WordPress 翻訳を始める

\n

2003年11月にブログエンジンの変更を完了したサイトを公開し、12月に日本語版の WordPress フォーク “WordPress ME (Multilingual Edition)” を公開しているサイトがあることを知りました。Otsukare さんというエンジニアが行なっていた日本語情報の発信や日本語フォーラムでの回答をお手伝いしているうち、1ユーザーからファンへ、そしてローカリゼーションという分野でのコントリビュートをするようになっていきました。

\n

それから何年も、WordPress は日本では比較的マイナーなブログツール/CMS ではあったんですが、自分の中では本当に大好きなソフトウェアで、地道に Codex の翻訳をしたり、テーマ作成コンテストに応募したり、フォーラムで回答したりしていました。オープンソースという世界も、会ったこともない人たちと(お金にならない!)作業を一緒にするのも初めてでしたが、WordPress を通して会う人たちは本当に様々で、固定観念を覆してくれた気がします。留学や在米で「世界」を分かった気になっていたけど、それよりも私にとって理解を深めてくれたのは、英語を使ってアクセスすることができるようになった、多様な価値観が存在するオンラインのコミュニティでした。

\n

自分がブログを書くことが好きで、そのツールの成長に少しでも関われるという喜びが、飽きずにオープンソース活動を続けられた理由だった気がします。まだ「リモートワーク」なんて言葉も、動画チャットツールや Slack さえもない時期からオンラインで世界中の人達とコラボレーションする文化を持つ WordPress でしたが、遠く離れた人に考えを届られるブログというツールが中心にあったからこそ、コミュニティは深みを持って成長してきたし、人と人のつながりが構築されていったのだと思います。

\n

WordCamp Tokyo の運営

\n

2007年、サンフランシスコで開かれた WordCamp に遠征し、マットに声をかけました。「WordPress が好きで、日本でももっと広めるために何かできないかなと思ってるけど、どうしたらいいかな?」そんな内容だったと思います。質問の記憶はおぼろげですが、彼の答えは今でも覚えています。

\n

「WordCamp やったらいいよ!(You should do a WordCamp.)」

\n

たまたま WordCamp にいたからの思いつきから出た言葉だったのかもしれませんが、そのときの一言が印象的で、約1年後に日本初の WordCamp を実行するきっかけになったのは間違いありません。私自身は日本に住んでいなかったにも関わらず WordCamp Tokyo 2008 が実行できたのは、単なる言い出しっぺの私に「いいね!」と言って一緒に運営をしてくれた他の翻訳者、開発者、日本語版ユーザーの方々とのつながりがあったからでした。

\n

キャリアへの影響

\n

2006年~2009年には、自分のキャリアも大きく変わりました。

\n

WordPress にハマることで身につけたブログテンプレート一般のカスタマイズ能力でフリーランスの仕事が入ってきたり、WordPress の本を日本語で書く機会もいただきました。Web 標準の考え方に触れて実践することができたのも WordPress のおかげで、「普通に、きちんとマークアップが書ける」スキルを評価されて、ずっと前から入社したかったデトロイト郊外の会社でフロントエンドエンジニアとしての経験を積むこともできました。その後、2009年にお声がけをいただき、Automattic でのカスタマーサポート職としてスタートして、2010年からフルタイムでこの会社の「社員」となり、現在はローカリゼーション関連のチームでプロジェクト管理を担当しています。もうすぐ勤務10年を迎えます。

\n

回り回って今は翻訳チームのグローバルメンターや、WordPress Translation Day 4のリードオーガナイザーを任せてもらったり、そして自分でも驚くことに第一回 WordCamp Asia(2020年、バンコクにて開催予定)のグローバルリードにも選んでいただきました。

\n

学びとお返し

\n\n

こういうことは当たり前のようでいて、実感できないような環境も少なくないのではないでしょうか。WordPress コミュニティだって常にパーフェクトではもちろんないにしろ、この場所ではそんな「当たり前」が大事されている、と私はよく感じます。みんなが納得できる普遍的な正しさが、長期的な視点での深みのあるコミュニティの維持と成長に欠かせない要素だと理解している人が多いからなのかなと思っています。

\n

自信も経験も少なかった自分にたくさんのことを学ばせてくれた WordPress と、その周りにいる人たちへの恩返しも込めて、これからさらに英語圏以外のコミュニティも手助けしていければと思っています。そうすることで、Web と世界を少しでも良い場所にできると信じているし、関わる多くの人のバリアを取り除くきっかけとなるはずです。

\n

The post Growing Through Translating WordPress appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 23:00: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:12:\"Naoko Takano\";s: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:92:\"WPTavern: Loveland Public Library to Host Free Beginners WordPress Class Online May 22, 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=89982\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/loveland-public-library-to-host-free-beginners-wordpress-class-online-may-22-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3315:\"

image credit: Janko Ferlic

\n

Public libraries are one of the few remaining community centers where people freely pass on valuable skills to neighbors young and old. In addition to offering free access to books, computers, and the internet, libraries often host educational classes as a public service, with an emphasis on teaching fundamental skills for navigating the digital world.

\n

Many people who are on fixed incomes or living paycheck to paycheck cannot afford to have internet service at home. For them, the library is a gateway to online communication, job hunting, and learning new skills.

\n

Over the past five years, using WordPress has become one of those important skills, as the software is now used by 33% of the top 10 million websites, across nearly every major industry.

\n

Packed into a full schedule of toddler story time, book chats, and knitting groups, the public library in Loveland, Colorado, is hosting a free workshop called Getting Started with a WordPress Website on May 22, 2019, from 9:00 AM – 10:30 AM MDT. Participants will learn the history and terminology of WordPress, along with the step-by-step basics of creating a website. Topics include posts vs pages, using media, installing a theme, and using plugins.

\n

Participants who cannot attend in person at the library can register online for a free ticket on Facebook or through Eventbrite. Those participating remotely will need to install the Adobe Connect meeting browser plugin and will be able to listen to the lecture through the digital classroom and ask questions via chat.

\n

Another class will be hosted July 2, 2019, for those who are unable to attend the May workshop.

\n

Loveland Public Library is one of many libraries that host free WordPress classes. Skokie Public Library in Skokie, Illinois, will be hosting a Build a Website with WordPress.com workshop on Friday, May 24, and the Denver Public Library offers similar courses for WordPress.com in various locations. The New York Public Library plans to offer a Blogging for Beginners course at its Woodland Heights location on October 3, 2019. These are just a small sampling of the educational opportunities offered in this format. If you know someone who wants to get started with WordPress, local libraries are a good resource for finding a free, in-person class.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 21:56:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:55:\"WordPress.org blog: WordPress 5.2.1 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=6976\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpress.org/news/2019/05/wordpress-5-2-1-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:4909:\"

WordPress 5.2.1 is now available! This maintenance release fixes 33 bugs, including improvements to the block editor, accessibility, internationalization, and the Site Health feature introduced in 5.2.

\n\n\n\n

You can browse the full list of changes on Trac.

\n\n\n\n

WordPress 5.2.1 is a short-cycle maintenance release. Version 5.2.2 is expected to follow in approximately two weeks.

\n\n\n\n

You can download WordPress 5.2.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

Jonathan Desrosiers and William Earnhardt co-led this release, with contributions from 52 other contributors. Thank you to everyone that made this release possible!

\n\n\n\n

Alex Dimitrov, Alex Shiels, Andrea Fercia, Andrew Duthie, Andrew Ozz, Andrey “Rarst” Savchenko, Andy Fragen, anischarolia, Birgir Erlendsson (birgire), chesio, Chetan Prajapati, daxelrod, Debabrata Karfa, Dima, Dion Hulse, Dominik Schilling, Ella van Durpe, Emil Dotsev, ghoul, Grzegorz (Greg) Ziółkowski, gwwar, Hareesh, Ian Belanger, imath, Jb Audras, Jeremy Felt, Joen Asmussen, Jonathan Desrosiers, Jonny Harris, Josepha, jrf, kjellr, Marius L. J., MikeNGarrett, Milan Dinić, Mukesh Panchal, onlanka, paragoninitiativeenterprises, parkcityj, Peter Wilson, Presskopp, Riad Benguella, Sergey Biryukov, Stephen Edgar, Sébastien SERRE, Thorsten Frommen, Tim Hengeveld, Timothy Jacobs, timph, TobiasBg, tonybogdanov, Tor-Bjorn Fjellner, William Earnhardt, and Yui.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 19:04:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s: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:101:\"WPTavern: New in EditorsKit 1.5: Justify Text Alignment, Autosave On/Off Toggle, and Highlighted Text\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=89826\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/new-in-editorskit-1-5-justify-text-alignment-autosave-on-off-toggle-and-highlighted-text\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5718:\"

WordPress plugin developer Jeffrey Carandang continues to plough forward with new features for EditorsKit, a collection of page building block options for Gutenberg. What began as a block visibility management plugin has grown to include more features aimed at tweaking various settings in the editor.

\n

Version 1.5 adds some text, heading, and paragraph styling and formatting options that aren’t currently available in core. For example, Gutenberg lets users change the background color and text color for an entire paragraph, but that’s where the color customizations end. EditorsKit now supports highlighting a section of text or a heading and choosing a color or background color.

\n

\n

This may seem like a niche request to implement but Carandang has tracked nearly two dozen related issues and discussions where users are asking for text highlighting or similar features.

\n

This release also adds underline and justify alignment options to the paragraph block. Gutenberg doesn’t include it by default, as WordPress 4.7 removed the justify button from the TinyMCE editor in 2016. However, the demand for justified text has not disappeared.

\n

In adding the format to EditorsKit, Carandang cited 10 issues from Gutenberg’s GitHub repository and eight WordPress.org support topics where users have asked for the justify text option or have commented on it being missing.

\n

\n

Those who have Jetpack installed will already have the justify alignment option. Carandang plans to add a check for wpcom/justify to the next release so users of both plugins won’t have two justify options.

\n

EditorsKit 1.5 tackles the widespread issues with Gutenberg’s autosave function by adding a toggle that allows users to enable/disable it. This setting can be found under the vertical ellipses menu at the top of the editor.
\nUsers have reported getting stuck in autosave, particularly with slower connection speeds, and some have experienced problems with their hosts.

\n
\n

Neat. I’ve seen users leave their browser tab open all night and their session expires, but the autosaves continue to post even though it’s now getting a 403. Then when the person wakes up their server blacklisted their IP.

\n

— Jay (@wpdevlife) April 30, 2019

\n

\n

As the result of getting stuck in autosave, users often attempt to refresh the screen only to lose the work. This has been an ongoing problem since last year. EditorsKit gives users the option to turn autosave off if they are experiencing problems and save manually as they see fit.

\n

Version 1.5 adds theme support for changing the block width to match the page template and layout. This allows theme developers to customize block sizes based on the template the users selects.

\n

Carandang has been adding new features based on his own needs but has found most of them to be fairly common requests in the Gutenberg repository. He made upcoming features and ideas for EditorsKit public on GitHub and is accepting feature suggestions in this format. A few of his current ideas under discussion include:

\n\n

I asked Carandang if he has any plans to add an option for paring down Gutenberg to the bare essentials with an interface more focused on writing. He said it is a possibility but is optimistic that the Gutenberg team may work to solve this common complaint in core.

\n

“I’ve thought of that, specially when my writer colleague asked me about it,” he said. “But I think it’s not time for that yet. I’ll wait for more Gutenberg releases before deciding if it’s needed in EditorsKit.”

\n

Carandang said he doesn’t plan to add any custom blocks to EditorsKit. His goal is to extend blocks for users to have options that they can utilize globally, while using whichever blocks plugin(s) they prefer. The plugin currently has no revenue model but he may pursue monetization in the future.

\n

“At of the moment, I’m more focused on building the plugin features rather than monetization, but extensions may come in a year or two when Gutenberg is more stable,” Carandang said.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 14:58: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: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:89:\"WPTavern: CoBlocks 1.9.5 Merges Block Gallery Plugin into Collection, Adds New Form Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=89869\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wptavern.com/coblocks-1-9-5-merges-block-gallery-plugin-into-collection-adds-new-form-block\";s: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:4217:\"

CoBlocks, a collection of page builder blocks that was recently acquired by GoDaddy, has added four new blocks in version 1.9.5. This is the first major release since the plugin was acquired from Rich Tabor and his co-creators. Tabor now heads up a WordPress Experience team at GoDaddy where CoBlocks’ development continues.

\n

This release merges the three gallery blocks (Masonry, Stacked, and Carousel) from the Block Gallery plugin into CoBlocks. There is a migration path for users to convert their existing Block Gallery blocks to CoBlocks’ gallery blocks. Block Gallery is still available on WordPress.org as a separate plugin with 5,000 active installs, which is actually more installs than CoBlocks (4,000). Tabor said his team is still discussing whether or not it will remove the plugin in the future.

\n

“CoBlocks is already a suite of blocks that level-up the block editor, bringing in those gallery blocks into the core plugin removes a barrier for folks who already have CoBlocks installed,” Tabor said. “Instead of folks having to install, activate, and maintain two plugins – only one is needed. On top of that, it’s far easier to maintain them collectively under one roof, as many of the components are shared between the two plugins.”

\n

In addition to merging the gallery blocks, CoBlocks 1.9.5 introduces a new Form block that allows users to customize a simple form directly within the editor. The block includes name, email, and message form fields but does not offer the ability to create new fields or change them to different types of fields. Users can set any of the fields as required using a toggle inside the block preview. For anything beyond these capabilities, a dedicated forms plugin would be required.

\n

\n

CoBlocks 1.9.5 also adds official support for Gutenberg 5.7 and includes more than a dozen tweaks and fixes.

\n

Tabor said his team is identifying further solutions that can be leveraged to make page building in WordPress more simple. CoBlocks is rapidly becoming a another one-stop shop for the mostly commonly used page building blocks.

\n

“We’re looking at how to make adding maps easier (a better Map block) and developing a system that enables restaurants to build out menus,” Tabor said.

\n

Several other block collections already offer a map block and/or a similar suite of page building functionality, such as Ghost Kit, Atomic Blocks, Stackable, and Editor Blocks. Collections seem to be the best way to offer multiple small UI elements, especially if they are all designed to be complimentary in style. Plugin authors differentiate their collections from the others with additional block options, support, complimentary themes, and immediate compatibility with the Gutenberg plugin.

\n

At the moment, there is little incentive for developers to maintain functionality as separate plugins, but WordPress’ planned single block directory may change the way blocks are packaged for optimal discovery. For now, it’s a race to see which block collection can offer the most useful suite with the most intuitive UI.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 00:57:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:66:\"WPTavern: WordPress 5.2 Improves the Security of Automatic Updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=89913\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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-5-2-improves-the-security-of-automatic-updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4791:\"

WordPress 5.2, released earlier this month, added the first step towards fully secure updates with offline digital signatures. Scott Arciszewski, Chief Development Officer for Paragon Initiative Enterprises, explains how it works and how developers can migrate away from mcrypt to libsodium.

\n\n\n\n

When your WordPress site installs an automatic update, from version 5.2 onwards, it will first check for the existence of an x-content-signature header.

If one isn’t provided by the update server, your WordPress site will instead query for a filenamehere.sig file.

No matter how it’s delivered, the signatures are calculated using Ed25519 of the SHA384 hash of the file’s contents. The signature is base64-encoded for safe transport.

Scott Arciszewski
\n\n\n\n

The WordPress core development team manages the signing or secret keys. WordPress 5.2 contains a signing key that expires on April 1, 2021. The verification key or public key is used to decipher the secret key. This value determines the validity of the signature.

\n\n\n\n

Since the feature is still in an experimental phase, WordPress 5.2 allows an update to occur if a soft error or invalid signature is encountered. This is to prevent more severe errors from causing the user to be locked out of the update process until a manual update is applied. The team will use the reported error information to improve the signature checking process.

\n\n\n\n

The digital signatures are only supported for core updates with Themes and Plugins to follow in a later release. It’s also likely that the team will include separate keys for core releases, plugins, themes, translations, etc. to allow for more fine-grained control.

\n\n\n\n

Digital signatures applied to WordPress core updates is an important milestone because it prevents users from unknowingly downloading updates from malicious sources.

\n\n\n\n

For example, without digital signatures, if the server or servers that house the core update files were compromised, a false update could be sent to millions of sites. In 2016, WordFence explained how this scenario could play out when they publicized a security vulnerability they discovered with api.wordpress.org.

\n\n\n\n

Persistence Pays Off

\n\n\n\n

In early 2017, Arciszewski published a plea to Matt Mullenweg to focus on securing WordPress’ automatic updates system by using secure cryptographic signatures. Mullenweg responded to the article with one of his own on Medium.

\n\n\n\n

We will at some point; as said above it’s a good idea — can’t hurt, might help. There are, however, some more important security issues in front of it, that impact millions of sites in the real world, so we are prioritizing those issues above a nice-to-have, defense in-depth effort.

Matt Mullenweg
\n\n\n\n

Arciszewski has spent at least six years trying to convince the core team to implement digitally signed updates. Four months ago, Gary Pendergast, WordPress core developer, responded to the ticket saying that the feature fell in line with the list of WordPress priorities planned for 2019 and beyond. Pendergast laid out a plan and with a confirmed commitment to landing it in core, Arciszewski worked with the core team to make it a reality.

\n\n\n\n

Millions of WordPress sites are on their way to becoming more secure thanks to the persistence and efforts of Arciszewski and the WordPress core team.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 20 May 2019 21:28:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:56:\"WPTavern: Jetpack Opens Signup for Membership Block Beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=89859\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wptavern.com/jetpack-opens-signup-for-membership-block-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1749:\"

Jetpack has opened a signup for the beta of its upcoming Membership feature in order to collect feedback from potential testers. The changelog for version 7.3, released two weeks ago, hinted at a new Membership block coming to the plugin. The work in progress was added behind the JETPACK_BETA_BLOCKS constant, presumably in preparation for wider testing.

\n

Based on the feature’s description on GitHub, the first iteration will function like a recurring payment/donation button that uses Stripe as the payment gateway. In this case, “membership” might be a misnomer for the feature. The wording on the beta signup page lends to the confusion: “WordPress.com is currently preparing a feature that will let you enable subscriptions on your site.”

\n

At the moment, it appears that the Jetpack team hasn’t fully decided what this feature will become and seems open to seeing where it will go. Beta testers will likely refine the direction of the block. If you have an interest in using Jetpack’s membership capabilities in the future and want to shape its development, you can sign up for the beta by providing your WordPress.com login and a description of your needs and expectations for the feature.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 18 May 2019 04:09:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Wed, 19 Jun 2019 01:15:54 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Wed, 19 Jun 2019 01:00:28 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:2:\"br\";}}s:5:\"build\";s:14:\"20130911073210\";}','no'),(142,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1560950154','no'),(143,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1560906954','no'),(144,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1560950154','no'),(145,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b','','no'),(146,'_transient_timeout_plugin_slugs','1560993354','no'),(147,'_transient_plugin_slugs','a:5:{i:0;s:19:\"akismet/akismet.php\";i:1;s:33:\"classic-editor/classic-editor.php\";i:2;s:51:\"featured-image-from-url/featured-image-from-url.php\";i:3;s:9:\"hello.php\";i:4;s:42:\"wordpress-seo-premium-1/wp-seo-premium.php\";}','no'),(148,'recently_activated','a:0:{}','yes'); /*!40000 ALTER TABLE `wp_options` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_postmeta` -- DROP TABLE IF EXISTS `wp_postmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_postmeta` -- LOCK TABLES `wp_postmeta` WRITE; /*!40000 ALTER TABLE `wp_postmeta` DISABLE KEYS */; INSERT INTO `wp_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'); /*!40000 ALTER TABLE `wp_postmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_posts` -- DROP TABLE IF EXISTS `wp_posts`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_posts` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_author` bigint(20) unsigned NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`ID`), KEY `post_name` (`post_name`(191)), KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), KEY `post_parent` (`post_parent`), KEY `post_author` (`post_author`) ) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_posts` -- LOCK TABLES `wp_posts` WRITE; /*!40000 ALTER TABLE `wp_posts` DISABLE KEYS */; INSERT INTO `wp_posts` VALUES (1,1,'2019-06-19 01:12:11','2019-06-19 01:12:11','\n

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

\n','Hello world!','','publish','open','open','','hello-world','','','2019-06-19 01:12:11','2019-06-19 01:12:11','',0,'https://pastes.vip/?p=1',0,'post','',1),(2,1,'2019-06-19 01:12:11','2019-06-19 01:12:11','\n

This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:

\n\n\n\n

Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)

\n\n\n\n

...or something like this:

\n\n\n\n

The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.

\n\n\n\n

As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!

\n','Sample Page','','publish','closed','open','','sample-page','','','2019-06-19 01:12:11','2019-06-19 01:12:11','',0,'https://pastes.vip/?page_id=2',0,'page','',0),(3,1,'2019-06-19 01:12:11','2019-06-19 01:12:11','

Who we are

Our website address is: https://pastes.vip.

What personal data we collect and why we collect it

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Contact forms

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Analytics

Who we share your data with

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

Additional information

How we protect your data

What data breach procedures we have in place

What third parties we receive data from

What automated decision making and/or profiling we do with user data

Industry regulatory disclosure requirements

','Privacy Policy','','draft','closed','open','','privacy-policy','','','2019-06-19 01:12:11','2019-06-19 01:12:11','',0,'https://pastes.vip/?page_id=3',0,'page','',0),(4,1,'2019-06-19 01:15:51','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2019-06-19 01:15:51','0000-00-00 00:00:00','',0,'https://pastes.vip/?p=4',0,'post','',0); /*!40000 ALTER TABLE `wp_posts` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_term_relationships` -- DROP TABLE IF EXISTS `wp_term_relationships`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_term_relationships` ( `object_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`object_id`,`term_taxonomy_id`), KEY `term_taxonomy_id` (`term_taxonomy_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_term_relationships` -- LOCK TABLES `wp_term_relationships` WRITE; /*!40000 ALTER TABLE `wp_term_relationships` DISABLE KEYS */; INSERT INTO `wp_term_relationships` VALUES (1,1,0); /*!40000 ALTER TABLE `wp_term_relationships` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_term_taxonomy` -- DROP TABLE IF EXISTS `wp_term_taxonomy`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_term_taxonomy` ( `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `taxonomy` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `description` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `parent` bigint(20) unsigned NOT NULL DEFAULT '0', `count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`term_taxonomy_id`), UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), KEY `taxonomy` (`taxonomy`) ) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_term_taxonomy` -- LOCK TABLES `wp_term_taxonomy` WRITE; /*!40000 ALTER TABLE `wp_term_taxonomy` DISABLE KEYS */; INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1); /*!40000 ALTER TABLE `wp_term_taxonomy` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_termmeta` -- DROP TABLE IF EXISTS `wp_termmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_termmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`meta_id`), KEY `term_id` (`term_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_termmeta` -- LOCK TABLES `wp_termmeta` WRITE; /*!40000 ALTER TABLE `wp_termmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wp_termmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_terms` -- DROP TABLE IF EXISTS `wp_terms`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_terms` ( `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `slug` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0', PRIMARY KEY (`term_id`), KEY `slug` (`slug`(191)), KEY `name` (`name`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_terms` -- LOCK TABLES `wp_terms` WRITE; /*!40000 ALTER TABLE `wp_terms` DISABLE KEYS */; INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0); /*!40000 ALTER TABLE `wp_terms` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_usermeta` -- DROP TABLE IF EXISTS `wp_usermeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_usermeta` ( `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`umeta_id`), KEY `user_id` (`user_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=19 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_usermeta` -- LOCK TABLES `wp_usermeta` WRITE; /*!40000 ALTER TABLE `wp_usermeta` DISABLE KEYS */; INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','admin'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wp_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','1'),(16,1,'session_tokens','a:1:{s:64:\"d4493538739c61f21a547cc10134b2b468fc9e11ada4df75548d77db9e6f2f35\";a:4:{s:10:\"expiration\";i:1561079750;s:2:\"ip\";s:13:\"172.68.222.68\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36\";s:5:\"login\";i:1560906950;}}'),(17,1,'wp_dashboard_quick_press_last_post_id','4'),(18,1,'community-events-location','a:1:{s:2:\"ip\";s:12:\"31.171.152.0\";}'); /*!40000 ALTER TABLE `wp_usermeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp_users` -- DROP TABLE IF EXISTS `wp_users`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp_users` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_login` varchar(60) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_pass` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_nicename` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_url` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT '0', `display_name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', PRIMARY KEY (`ID`), KEY `user_login_key` (`user_login`), KEY `user_nicename` (`user_nicename`), KEY `user_email` (`user_email`) ) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp_users` -- LOCK TABLES `wp_users` WRITE; /*!40000 ALTER TABLE `wp_users` DISABLE KEYS */; INSERT INTO `wp_users` VALUES (1,'admin','$P$BN/jJ.s9AfHq4wlBHoEnZbcWm.wg.y/','admin','admin@pastes.vip','','2019-06-19 01:12:11','',0,'admin'); /*!40000 ALTER TABLE `wp_users` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_commentmeta` -- DROP TABLE IF EXISTS `wpwb_commentmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_commentmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`meta_id`), KEY `comment_id` (`comment_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_commentmeta` -- LOCK TABLES `wpwb_commentmeta` WRITE; /*!40000 ALTER TABLE `wpwb_commentmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wpwb_commentmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_comments` -- DROP TABLE IF EXISTS `wpwb_comments`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_comments` ( `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0', `comment_author` tinytext COLLATE utf8mb4_unicode_ci NOT NULL, `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_content` text COLLATE utf8mb4_unicode_ci NOT NULL, `comment_karma` int(11) NOT NULL DEFAULT '0', `comment_approved` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '1', `comment_agent` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`comment_ID`), KEY `comment_post_ID` (`comment_post_ID`), KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), KEY `comment_date_gmt` (`comment_date_gmt`), KEY `comment_parent` (`comment_parent`), KEY `comment_author_email` (`comment_author_email`(10)) ) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_comments` -- LOCK TABLES `wpwb_comments` WRITE; /*!40000 ALTER TABLE `wpwb_comments` DISABLE KEYS */; INSERT INTO `wpwb_comments` VALUES (1,1,'A WordPress Commenter','wapuu@wordpress.example','https://wordpress.org/','','2019-05-29 05:52:34','2019-05-29 05:52:34','Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from Gravatar.',0,'post-trashed','','',0,0); /*!40000 ALTER TABLE `wpwb_comments` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_links` -- DROP TABLE IF EXISTS `wpwb_links`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_links` ( `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_image` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_target` varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_description` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_visible` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'Y', `link_owner` bigint(20) unsigned NOT NULL DEFAULT '1', `link_rating` int(11) NOT NULL DEFAULT '0', `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `link_rel` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_notes` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `link_rss` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', PRIMARY KEY (`link_id`), KEY `link_visible` (`link_visible`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_links` -- LOCK TABLES `wpwb_links` WRITE; /*!40000 ALTER TABLE `wpwb_links` DISABLE KEYS */; /*!40000 ALTER TABLE `wpwb_links` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_options` -- DROP TABLE IF EXISTS `wpwb_options`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_options` ( `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `option_name` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `option_value` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `autoload` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'yes', PRIMARY KEY (`option_id`), UNIQUE KEY `option_name` (`option_name`) ) ENGINE=MyISAM AUTO_INCREMENT=295 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_options` -- LOCK TABLES `wpwb_options` WRITE; /*!40000 ALTER TABLE `wpwb_options` DISABLE KEYS */; INSERT INTO `wpwb_options` VALUES (1,'siteurl','http://wordpressed.ml','yes'),(2,'home','http://wordpressed.ml','yes'),(3,'blogname','My Blog','yes'),(4,'blogdescription','My WordPress Blog','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','admin@wordpressed.ml','yes'),(7,'start_of_week','1','yes'),(8,'use_balanceTags','0','yes'),(9,'use_smilies','1','yes'),(10,'require_name_email','1','yes'),(11,'comments_notify','1','yes'),(12,'posts_per_rss','10','yes'),(13,'rss_use_excerpt','0','yes'),(14,'mailserver_url','mail.example.com','yes'),(15,'mailserver_login','login@example.com','yes'),(16,'mailserver_pass','password','yes'),(17,'mailserver_port','110','yes'),(18,'default_category','1','yes'),(19,'default_comment_status','open','yes'),(20,'default_ping_status','open','yes'),(21,'default_pingback_flag','1','yes'),(22,'posts_per_page','10','yes'),(23,'date_format','F j, Y','yes'),(24,'time_format','g:i a','yes'),(25,'links_updated_date_format','F j, Y g:i a','yes'),(26,'comment_moderation','0','yes'),(27,'moderation_notify','1','yes'),(28,'permalink_structure','/%postname%/','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(33,'active_plugins','a:3:{i:0;s:33:\"classic-editor/classic-editor.php\";i:1;s:51:\"featured-image-from-url/featured-image-from-url.php\";i:2;s:42:\"wordpress-seo-premium-1/wp-seo-premium.php\";}','yes'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','','no'),(40,'template','ribosome','yes'),(41,'stylesheet','ribosome','yes'),(42,'comment_whitelist','1','yes'),(43,'blacklist_keys','','no'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','44719','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','1','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','posts','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'widget_categories','a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(79,'widget_text','a:0:{}','yes'),(80,'widget_rss','a:0:{}','yes'),(81,'uninstall_plugins','a:1:{s:33:\"classic-editor/classic-editor.php\";a:2:{i:0;s:14:\"Classic_Editor\";i:1;s:9:\"uninstall\";}}','no'),(82,'timezone_string','','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','0','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'wp_page_for_privacy_policy','3','yes'),(92,'show_comments_cookies_opt_in','1','yes'),(93,'initial_db_version','44719','yes'),(94,'wpwb_user_roles','a:7:{s:13:\"administrator\";a:2:{s:4:\"name\";s:13:\"Administrator\";s:12:\"capabilities\";a:62:{s:13:\"switch_themes\";b:1;s:11:\"edit_themes\";b:1;s:16:\"activate_plugins\";b:1;s:12:\"edit_plugins\";b:1;s:10:\"edit_users\";b:1;s:10:\"edit_files\";b:1;s:14:\"manage_options\";b:1;s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:6:\"import\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:8:\"level_10\";b:1;s:7:\"level_9\";b:1;s:7:\"level_8\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:12:\"delete_users\";b:1;s:12:\"create_users\";b:1;s:17:\"unfiltered_upload\";b:1;s:14:\"edit_dashboard\";b:1;s:14:\"update_plugins\";b:1;s:14:\"delete_plugins\";b:1;s:15:\"install_plugins\";b:1;s:13:\"update_themes\";b:1;s:14:\"install_themes\";b:1;s:11:\"update_core\";b:1;s:10:\"list_users\";b:1;s:12:\"remove_users\";b:1;s:13:\"promote_users\";b:1;s:18:\"edit_theme_options\";b:1;s:13:\"delete_themes\";b:1;s:6:\"export\";b:1;s:20:\"wpseo_manage_options\";b:1;}}s:6:\"editor\";a:2:{s:4:\"name\";s:6:\"Editor\";s:12:\"capabilities\";a:36:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:15:\"wpseo_bulk_edit\";b:1;s:22:\"wpseo_manage_redirects\";b:1;}}s:6:\"author\";a:2:{s:4:\"name\";s:6:\"Author\";s:12:\"capabilities\";a:10:{s:12:\"upload_files\";b:1;s:10:\"edit_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;s:22:\"delete_published_posts\";b:1;}}s:11:\"contributor\";a:2:{s:4:\"name\";s:11:\"Contributor\";s:12:\"capabilities\";a:5:{s:10:\"edit_posts\";b:1;s:4:\"read\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:12:\"delete_posts\";b:1;}}s:10:\"subscriber\";a:2:{s:4:\"name\";s:10:\"Subscriber\";s:12:\"capabilities\";a:2:{s:4:\"read\";b:1;s:7:\"level_0\";b:1;}}s:13:\"wpseo_manager\";a:2:{s:4:\"name\";s:11:\"SEO Manager\";s:12:\"capabilities\";a:38:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:15:\"wpseo_bulk_edit\";b:1;s:28:\"wpseo_edit_advanced_metadata\";b:1;s:20:\"wpseo_manage_options\";b:1;s:22:\"wpseo_manage_redirects\";b:1;}}s:12:\"wpseo_editor\";a:2:{s:4:\"name\";s:10:\"SEO Editor\";s:12:\"capabilities\";a:37:{s:17:\"moderate_comments\";b:1;s:17:\"manage_categories\";b:1;s:12:\"manage_links\";b:1;s:12:\"upload_files\";b:1;s:15:\"unfiltered_html\";b:1;s:10:\"edit_posts\";b:1;s:17:\"edit_others_posts\";b:1;s:20:\"edit_published_posts\";b:1;s:13:\"publish_posts\";b:1;s:10:\"edit_pages\";b:1;s:4:\"read\";b:1;s:7:\"level_7\";b:1;s:7:\"level_6\";b:1;s:7:\"level_5\";b:1;s:7:\"level_4\";b:1;s:7:\"level_3\";b:1;s:7:\"level_2\";b:1;s:7:\"level_1\";b:1;s:7:\"level_0\";b:1;s:17:\"edit_others_pages\";b:1;s:20:\"edit_published_pages\";b:1;s:13:\"publish_pages\";b:1;s:12:\"delete_pages\";b:1;s:19:\"delete_others_pages\";b:1;s:22:\"delete_published_pages\";b:1;s:12:\"delete_posts\";b:1;s:19:\"delete_others_posts\";b:1;s:22:\"delete_published_posts\";b:1;s:20:\"delete_private_posts\";b:1;s:18:\"edit_private_posts\";b:1;s:18:\"read_private_posts\";b:1;s:20:\"delete_private_pages\";b:1;s:18:\"edit_private_pages\";b:1;s:18:\"read_private_pages\";b:1;s:15:\"wpseo_bulk_edit\";b:1;s:28:\"wpseo_edit_advanced_metadata\";b:1;s:22:\"wpseo_manage_redirects\";b:1;}}}','yes'),(95,'fresh_site','0','yes'),(96,'widget_search','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(97,'widget_recent-posts','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(98,'widget_recent-comments','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(99,'widget_archives','a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(100,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(101,'sidebars_widgets','a:5:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}s:12:\"wt-sub-title\";a:0:{}s:11:\"wt-post-end\";a:0:{}s:13:\"array_version\";i:3;}','yes'),(102,'cron','a:8:{i:1560909154;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1560912670;a:1:{s:26:\"upgrader_scheduled_cleanup\";a:1:{s:32:\"24daa8f49584a6f1b1395d475758a1de\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:1:{i:0;i:23;}}}}i:1560912688;a:1:{s:26:\"upgrader_scheduled_cleanup\";a:1:{s:32:\"799be243d6827cc0bc0951691920a50b\";a:2:{s:8:\"schedule\";b:0;s:4:\"args\";a:1:{i:0;i:24;}}}}i:1560923554;a:4:{s:16:\"wp_version_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:17:\"wp_update_plugins\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:16:\"wp_update_themes\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:10:\"twicedaily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:43200;}}s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1560923598;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1560923600;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1560991914;a:3:{s:41:\"wpseo-premium-prominent-words-recalculate\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:30:\"wpseo-premium-orphaned-content\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:19:\"wpseo-reindex-links\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}s:7:\"version\";i:2;}','yes'),(103,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(104,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(105,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(106,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(107,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(108,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(109,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(110,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(111,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(278,'_transient_timeout_wpseo_link_table_inaccessible','1592441514','no'),(279,'_transient_wpseo_link_table_inaccessible','0','no'),(280,'_transient_timeout_wpseo_meta_table_inaccessible','1592441514','no'),(281,'_transient_wpseo_meta_table_inaccessible','0','no'),(283,'wpseo_current_version','16','no'),(284,'wpseo_premium_version','10.1.1','yes'),(285,'status','valid','yes'),(286,'_transient_timeout_59c0e3c614b32dabbd3cbd89aaa064c7','1560991931','no'),(287,'_transient_59c0e3c614b32dabbd3cbd89aaa064c7','a:7:{s:4:\"name\";s:0:\"\";s:5:\"email\";s:20:\"admin@wordpressed.ml\";s:17:\"WordPress Version\";s:5:\"5.2.2\";s:6:\"Server\";s:217:\"
IP136.243.14.90
Hostnamecloudy.vapehost.cc
OSLinux
PHP5.6.40
CURL7.64.0
\";s:62:\"Theme\";s:138:\"Ribosome v2.5.0 by GalussoThemes\";s:65:\"Plugins\";s:258:\"Classic Editor v1.5
Featured Image from URL v2.5.0
Yoast SEO Premium v10.1.1
\";s:17:\"Yoast SEO Premium\";s:218:\"
Version10.1.1
License
Statusvalid
\";}','no'),(289,'_transient_timeout_c4cf71c30959782cee8fe845d05ddf48','1560991999','no'),(290,'_transient_c4cf71c30959782cee8fe845d05ddf48','a:6:{s:4:\"name\";s:0:\"\";s:5:\"email\";s:20:\"admin@wordpressed.ml\";s:17:\"WordPress Version\";s:5:\"5.2.2\";s:6:\"Server\";s:217:\"
IP136.243.14.90
Hostnamecloudy.vapehost.cc
OSLinux
PHP5.6.40
CURL7.64.0
\";s:62:\"Theme\";s:138:\"Ribosome v2.5.0 by GalussoThemes\";s:65:\"Plugins\";s:258:\"Classic Editor v1.5
Featured Image from URL v2.5.0
Yoast SEO Premium v10.1.1
\";}','no'),(291,'rewrite_rules','a:95:{s:19:\"sitemap_index\\.xml$\";s:19:\"index.php?sitemap=1\";s:31:\"([^/]+?)-sitemap([0-9]+)?\\.xml$\";s:51:\"index.php?sitemap=$matches[1]&sitemap_n=$matches[2]\";s:24:\"([a-z]+)?-?sitemap\\.xsl$\";s:25:\"index.php?xsl=$matches[1]\";s:11:\"^wp-json/?$\";s:22:\"index.php?rest_route=/\";s:14:\"^wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:21:\"^index.php/wp-json/?$\";s:22:\"index.php?rest_route=/\";s:24:\"^index.php/wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:47:\"category/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:42:\"category/(.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?category_name=$matches[1]&feed=$matches[2]\";s:23:\"category/(.+?)/embed/?$\";s:46:\"index.php?category_name=$matches[1]&embed=true\";s:35:\"category/(.+?)/page/?([0-9]{1,})/?$\";s:53:\"index.php?category_name=$matches[1]&paged=$matches[2]\";s:17:\"category/(.+?)/?$\";s:35:\"index.php?category_name=$matches[1]\";s:44:\"tag/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:39:\"tag/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?tag=$matches[1]&feed=$matches[2]\";s:20:\"tag/([^/]+)/embed/?$\";s:36:\"index.php?tag=$matches[1]&embed=true\";s:32:\"tag/([^/]+)/page/?([0-9]{1,})/?$\";s:43:\"index.php?tag=$matches[1]&paged=$matches[2]\";s:14:\"tag/([^/]+)/?$\";s:25:\"index.php?tag=$matches[1]\";s:45:\"type/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:40:\"type/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?post_format=$matches[1]&feed=$matches[2]\";s:21:\"type/([^/]+)/embed/?$\";s:44:\"index.php?post_format=$matches[1]&embed=true\";s:33:\"type/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?post_format=$matches[1]&paged=$matches[2]\";s:15:\"type/([^/]+)/?$\";s:33:\"index.php?post_format=$matches[1]\";s:60:\"yst_prominent_words/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:72:\"index.php?taxonomy=yst_prominent_words&term=$matches[1]&feed=$matches[2]\";s:55:\"yst_prominent_words/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:72:\"index.php?taxonomy=yst_prominent_words&term=$matches[1]&feed=$matches[2]\";s:36:\"yst_prominent_words/([^/]+)/embed/?$\";s:66:\"index.php?taxonomy=yst_prominent_words&term=$matches[1]&embed=true\";s:48:\"yst_prominent_words/([^/]+)/page/?([0-9]{1,})/?$\";s:73:\"index.php?taxonomy=yst_prominent_words&term=$matches[1]&paged=$matches[2]\";s:30:\"yst_prominent_words/([^/]+)/?$\";s:55:\"index.php?taxonomy=yst_prominent_words&term=$matches[1]\";s:12:\"robots\\.txt$\";s:18:\"index.php?robots=1\";s:48:\".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$\";s:18:\"index.php?feed=old\";s:20:\".*wp-app\\.php(/.*)?$\";s:19:\"index.php?error=403\";s:18:\".*wp-register.php$\";s:23:\"index.php?register=true\";s:32:\"feed/(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:27:\"(feed|rdf|rss|rss2|atom)/?$\";s:27:\"index.php?&feed=$matches[1]\";s:8:\"embed/?$\";s:21:\"index.php?&embed=true\";s:20:\"page/?([0-9]{1,})/?$\";s:28:\"index.php?&paged=$matches[1]\";s:41:\"comments/feed/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:36:\"comments/(feed|rdf|rss|rss2|atom)/?$\";s:42:\"index.php?&feed=$matches[1]&withcomments=1\";s:17:\"comments/embed/?$\";s:21:\"index.php?&embed=true\";s:44:\"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:39:\"search/(.+)/(feed|rdf|rss|rss2|atom)/?$\";s:40:\"index.php?s=$matches[1]&feed=$matches[2]\";s:20:\"search/(.+)/embed/?$\";s:34:\"index.php?s=$matches[1]&embed=true\";s:32:\"search/(.+)/page/?([0-9]{1,})/?$\";s:41:\"index.php?s=$matches[1]&paged=$matches[2]\";s:14:\"search/(.+)/?$\";s:23:\"index.php?s=$matches[1]\";s:47:\"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:42:\"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:50:\"index.php?author_name=$matches[1]&feed=$matches[2]\";s:23:\"author/([^/]+)/embed/?$\";s:44:\"index.php?author_name=$matches[1]&embed=true\";s:35:\"author/([^/]+)/page/?([0-9]{1,})/?$\";s:51:\"index.php?author_name=$matches[1]&paged=$matches[2]\";s:17:\"author/([^/]+)/?$\";s:33:\"index.php?author_name=$matches[1]\";s:69:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:64:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:80:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]\";s:45:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/embed/?$\";s:74:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&embed=true\";s:57:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:81:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]\";s:39:\"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$\";s:63:\"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]\";s:56:\"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:51:\"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$\";s:64:\"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]\";s:32:\"([0-9]{4})/([0-9]{1,2})/embed/?$\";s:58:\"index.php?year=$matches[1]&monthnum=$matches[2]&embed=true\";s:44:\"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$\";s:65:\"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]\";s:26:\"([0-9]{4})/([0-9]{1,2})/?$\";s:47:\"index.php?year=$matches[1]&monthnum=$matches[2]\";s:43:\"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:38:\"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?year=$matches[1]&feed=$matches[2]\";s:19:\"([0-9]{4})/embed/?$\";s:37:\"index.php?year=$matches[1]&embed=true\";s:31:\"([0-9]{4})/page/?([0-9]{1,})/?$\";s:44:\"index.php?year=$matches[1]&paged=$matches[2]\";s:13:\"([0-9]{4})/?$\";s:26:\"index.php?year=$matches[1]\";s:27:\".?.+?/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\".?.+?/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\".?.+?/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"(.?.+?)/embed/?$\";s:41:\"index.php?pagename=$matches[1]&embed=true\";s:20:\"(.?.+?)/trackback/?$\";s:35:\"index.php?pagename=$matches[1]&tb=1\";s:40:\"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:35:\"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$\";s:47:\"index.php?pagename=$matches[1]&feed=$matches[2]\";s:28:\"(.?.+?)/page/?([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&paged=$matches[2]\";s:35:\"(.?.+?)/comment-page-([0-9]{1,})/?$\";s:48:\"index.php?pagename=$matches[1]&cpage=$matches[2]\";s:24:\"(.?.+?)(?:/([0-9]+))?/?$\";s:47:\"index.php?pagename=$matches[1]&page=$matches[2]\";s:27:\"[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:37:\"[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:57:\"[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\"[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:52:\"[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:33:\"[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:16:\"([^/]+)/embed/?$\";s:37:\"index.php?name=$matches[1]&embed=true\";s:20:\"([^/]+)/trackback/?$\";s:31:\"index.php?name=$matches[1]&tb=1\";s:40:\"([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?name=$matches[1]&feed=$matches[2]\";s:35:\"([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:43:\"index.php?name=$matches[1]&feed=$matches[2]\";s:28:\"([^/]+)/page/?([0-9]{1,})/?$\";s:44:\"index.php?name=$matches[1]&paged=$matches[2]\";s:35:\"([^/]+)/comment-page-([0-9]{1,})/?$\";s:44:\"index.php?name=$matches[1]&cpage=$matches[2]\";s:24:\"([^/]+)(?:/([0-9]+))?/?$\";s:43:\"index.php?name=$matches[1]&page=$matches[2]\";s:16:\"[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:26:\"[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:46:\"[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:41:\"[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:41:\"[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:22:\"[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";}','yes'),(274,'wpseo','a:22:{s:15:\"ms_defaults_set\";b:0;s:7:\"version\";s:6:\"10.1.1\";s:20:\"disableadvanced_meta\";b:1;s:19:\"onpage_indexability\";b:1;s:11:\"baiduverify\";s:0:\"\";s:12:\"googleverify\";s:0:\"\";s:8:\"msverify\";s:0:\"\";s:12:\"yandexverify\";s:0:\"\";s:9:\"site_type\";s:0:\"\";s:20:\"has_multiple_authors\";s:0:\"\";s:16:\"environment_type\";s:0:\"\";s:23:\"content_analysis_active\";b:1;s:23:\"keyword_analysis_active\";b:1;s:21:\"enable_admin_bar_menu\";b:1;s:26:\"enable_cornerstone_content\";b:1;s:18:\"enable_xml_sitemap\";b:1;s:24:\"enable_text_link_counter\";b:1;s:22:\"show_onboarding_notice\";b:1;s:18:\"first_activated_on\";i:1560905514;s:13:\"myyoast-oauth\";b:0;s:23:\"enable_metabox_insights\";b:1;s:23:\"enable_link_suggestions\";b:1;}','yes'),(275,'wpseo_titles','a:67:{s:10:\"title_test\";i:0;s:17:\"forcerewritetitle\";b:0;s:9:\"separator\";s:7:\"sc-dash\";s:16:\"title-home-wpseo\";s:42:\"%%sitename%% %%page%% %%sep%% %%sitedesc%%\";s:18:\"title-author-wpseo\";s:41:\"%%name%%, Author at %%sitename%% %%page%%\";s:19:\"title-archive-wpseo\";s:38:\"%%date%% %%page%% %%sep%% %%sitename%%\";s:18:\"title-search-wpseo\";s:63:\"You searched for %%searchphrase%% %%page%% %%sep%% %%sitename%%\";s:15:\"title-404-wpseo\";s:35:\"Page not found %%sep%% %%sitename%%\";s:19:\"metadesc-home-wpseo\";s:0:\"\";s:21:\"metadesc-author-wpseo\";s:0:\"\";s:22:\"metadesc-archive-wpseo\";s:0:\"\";s:9:\"rssbefore\";s:0:\"\";s:8:\"rssafter\";s:53:\"The post %%POSTLINK%% appeared first on %%BLOGLINK%%.\";s:20:\"noindex-author-wpseo\";b:0;s:28:\"noindex-author-noposts-wpseo\";b:1;s:21:\"noindex-archive-wpseo\";b:1;s:14:\"disable-author\";b:0;s:12:\"disable-date\";b:0;s:19:\"disable-post_format\";b:0;s:18:\"disable-attachment\";b:1;s:23:\"is-media-purge-relevant\";b:0;s:20:\"breadcrumbs-404crumb\";s:25:\"Error 404: Page not found\";s:29:\"breadcrumbs-display-blog-page\";b:1;s:20:\"breadcrumbs-boldlast\";b:0;s:25:\"breadcrumbs-archiveprefix\";s:12:\"Archives for\";s:18:\"breadcrumbs-enable\";b:0;s:16:\"breadcrumbs-home\";s:4:\"Home\";s:18:\"breadcrumbs-prefix\";s:0:\"\";s:24:\"breadcrumbs-searchprefix\";s:16:\"You searched for\";s:15:\"breadcrumbs-sep\";s:7:\"»\";s:12:\"website_name\";s:0:\"\";s:11:\"person_name\";s:0:\"\";s:22:\"alternate_website_name\";s:0:\"\";s:12:\"company_logo\";s:0:\"\";s:12:\"company_name\";s:0:\"\";s:17:\"company_or_person\";s:0:\"\";s:17:\"stripcategorybase\";b:0;s:10:\"title-post\";s:39:\"%%title%% %%page%% %%sep%% %%sitename%%\";s:13:\"metadesc-post\";s:0:\"\";s:12:\"noindex-post\";b:0;s:13:\"showdate-post\";b:0;s:23:\"display-metabox-pt-post\";b:1;s:23:\"post_types-post-maintax\";i:0;s:10:\"title-page\";s:39:\"%%title%% %%page%% %%sep%% %%sitename%%\";s:13:\"metadesc-page\";s:0:\"\";s:12:\"noindex-page\";b:0;s:13:\"showdate-page\";b:0;s:23:\"display-metabox-pt-page\";b:1;s:23:\"post_types-page-maintax\";i:0;s:16:\"title-attachment\";s:39:\"%%title%% %%page%% %%sep%% %%sitename%%\";s:19:\"metadesc-attachment\";s:0:\"\";s:18:\"noindex-attachment\";b:0;s:19:\"showdate-attachment\";b:0;s:29:\"display-metabox-pt-attachment\";b:1;s:29:\"post_types-attachment-maintax\";i:0;s:18:\"title-tax-category\";s:53:\"%%term_title%% Archives %%page%% %%sep%% %%sitename%%\";s:21:\"metadesc-tax-category\";s:0:\"\";s:28:\"display-metabox-tax-category\";b:1;s:20:\"noindex-tax-category\";b:0;s:18:\"title-tax-post_tag\";s:53:\"%%term_title%% Archives %%page%% %%sep%% %%sitename%%\";s:21:\"metadesc-tax-post_tag\";s:0:\"\";s:28:\"display-metabox-tax-post_tag\";b:1;s:20:\"noindex-tax-post_tag\";b:0;s:21:\"title-tax-post_format\";s:53:\"%%term_title%% Archives %%page%% %%sep%% %%sitename%%\";s:24:\"metadesc-tax-post_format\";s:0:\"\";s:31:\"display-metabox-tax-post_format\";b:1;s:23:\"noindex-tax-post_format\";b:1;}','yes'),(113,'theme_mods_twentynineteen','a:2:{s:18:\"custom_css_post_id\";i:-1;s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1559109253;s:4:\"data\";a:2:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:6:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";i:3;s:10:\"archives-2\";i:4;s:12:\"categories-2\";i:5;s:6:\"meta-2\";}}}}','yes'),(149,'recently_activated','a:0:{}','yes'),(155,'category_children','a:0:{}','yes'),(246,'_site_transient_timeout_theme_roots','1560905852','no'),(247,'_site_transient_theme_roots','a:4:{s:8:\"ribosome\";s:7:\"/themes\";s:14:\"twentynineteen\";s:7:\"/themes\";s:15:\"twentyseventeen\";s:7:\"/themes\";s:13:\"twentysixteen\";s:7:\"/themes\";}','no'),(138,'_site_transient_update_themes','O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1560905507;s:7:\"checked\";a:4:{s:8:\"ribosome\";s:5:\"2.5.0\";s:14:\"twentynineteen\";s:3:\"1.4\";s:15:\"twentyseventeen\";s:3:\"2.2\";s:13:\"twentysixteen\";s:3:\"2.0\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}}','no'),(123,'can_compress_scripts','1','no'),(264,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1560947777','no'),(265,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1560904577','no'),(266,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1560947777','no'),(267,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b','','no'),(268,'_transient_timeout_plugin_slugs','1560991915','no'),(269,'_transient_plugin_slugs','a:5:{i:0;s:19:\"akismet/akismet.php\";i:1;s:33:\"classic-editor/classic-editor.php\";i:2;s:51:\"featured-image-from-url/featured-image-from-url.php\";i:3;s:9:\"hello.php\";i:4;s:42:\"wordpress-seo-premium-1/wp-seo-premium.php\";}','no'),(270,'_site_transient_timeout_poptags_40cd750bba9870f18aada2478b24840a','1560915384','no'),(271,'_site_transient_poptags_40cd750bba9870f18aada2478b24840a','O:8:\"stdClass\":100:{s:6:\"widget\";a:3:{s:4:\"name\";s:6:\"widget\";s:4:\"slug\";s:6:\"widget\";s:5:\"count\";i:4586;}s:11:\"woocommerce\";a:3:{s:4:\"name\";s:11:\"woocommerce\";s:4:\"slug\";s:11:\"woocommerce\";s:5:\"count\";i:3483;}s:4:\"post\";a:3:{s:4:\"name\";s:4:\"post\";s:4:\"slug\";s:4:\"post\";s:5:\"count\";i:2624;}s:5:\"admin\";a:3:{s:4:\"name\";s:5:\"admin\";s:4:\"slug\";s:5:\"admin\";s:5:\"count\";i:2492;}s:5:\"posts\";a:3:{s:4:\"name\";s:5:\"posts\";s:4:\"slug\";s:5:\"posts\";s:5:\"count\";i:1923;}s:9:\"shortcode\";a:3:{s:4:\"name\";s:9:\"shortcode\";s:4:\"slug\";s:9:\"shortcode\";s:5:\"count\";i:1738;}s:8:\"comments\";a:3:{s:4:\"name\";s:8:\"comments\";s:4:\"slug\";s:8:\"comments\";s:5:\"count\";i:1734;}s:7:\"twitter\";a:3:{s:4:\"name\";s:7:\"twitter\";s:4:\"slug\";s:7:\"twitter\";s:5:\"count\";i:1468;}s:6:\"images\";a:3:{s:4:\"name\";s:6:\"images\";s:4:\"slug\";s:6:\"images\";s:5:\"count\";i:1442;}s:8:\"facebook\";a:3:{s:4:\"name\";s:8:\"facebook\";s:4:\"slug\";s:8:\"facebook\";s:5:\"count\";i:1435;}s:6:\"google\";a:3:{s:4:\"name\";s:6:\"google\";s:4:\"slug\";s:6:\"google\";s:5:\"count\";i:1434;}s:5:\"image\";a:3:{s:4:\"name\";s:5:\"image\";s:4:\"slug\";s:5:\"image\";s:5:\"count\";i:1370;}s:3:\"seo\";a:3:{s:4:\"name\";s:3:\"seo\";s:4:\"slug\";s:3:\"seo\";s:5:\"count\";i:1327;}s:7:\"sidebar\";a:3:{s:4:\"name\";s:7:\"sidebar\";s:4:\"slug\";s:7:\"sidebar\";s:5:\"count\";i:1293;}s:7:\"gallery\";a:3:{s:4:\"name\";s:7:\"gallery\";s:4:\"slug\";s:7:\"gallery\";s:5:\"count\";i:1144;}s:5:\"email\";a:3:{s:4:\"name\";s:5:\"email\";s:4:\"slug\";s:5:\"email\";s:5:\"count\";i:1114;}s:4:\"page\";a:3:{s:4:\"name\";s:4:\"page\";s:4:\"slug\";s:4:\"page\";s:5:\"count\";i:1100;}s:6:\"social\";a:3:{s:4:\"name\";s:6:\"social\";s:4:\"slug\";s:6:\"social\";s:5:\"count\";i:1065;}s:9:\"ecommerce\";a:3:{s:4:\"name\";s:9:\"ecommerce\";s:4:\"slug\";s:9:\"ecommerce\";s:5:\"count\";i:1007;}s:5:\"login\";a:3:{s:4:\"name\";s:5:\"login\";s:4:\"slug\";s:5:\"login\";s:5:\"count\";i:937;}s:5:\"links\";a:3:{s:4:\"name\";s:5:\"links\";s:4:\"slug\";s:5:\"links\";s:5:\"count\";i:854;}s:7:\"widgets\";a:3:{s:4:\"name\";s:7:\"widgets\";s:4:\"slug\";s:7:\"widgets\";s:5:\"count\";i:842;}s:5:\"video\";a:3:{s:4:\"name\";s:5:\"video\";s:4:\"slug\";s:5:\"video\";s:5:\"count\";i:837;}s:8:\"security\";a:3:{s:4:\"name\";s:8:\"security\";s:4:\"slug\";s:8:\"security\";s:5:\"count\";i:796;}s:4:\"spam\";a:3:{s:4:\"name\";s:4:\"spam\";s:4:\"slug\";s:4:\"spam\";s:5:\"count\";i:743;}s:7:\"content\";a:3:{s:4:\"name\";s:7:\"content\";s:4:\"slug\";s:7:\"content\";s:5:\"count\";i:732;}s:10:\"buddypress\";a:3:{s:4:\"name\";s:10:\"buddypress\";s:4:\"slug\";s:10:\"buddypress\";s:5:\"count\";i:729;}s:6:\"slider\";a:3:{s:4:\"name\";s:6:\"slider\";s:4:\"slug\";s:6:\"slider\";s:5:\"count\";i:718;}s:10:\"e-commerce\";a:3:{s:4:\"name\";s:10:\"e-commerce\";s:4:\"slug\";s:10:\"e-commerce\";s:5:\"count\";i:705;}s:3:\"rss\";a:3:{s:4:\"name\";s:3:\"rss\";s:4:\"slug\";s:3:\"rss\";s:5:\"count\";i:700;}s:9:\"analytics\";a:3:{s:4:\"name\";s:9:\"analytics\";s:4:\"slug\";s:9:\"analytics\";s:5:\"count\";i:699;}s:5:\"pages\";a:3:{s:4:\"name\";s:5:\"pages\";s:4:\"slug\";s:5:\"pages\";s:5:\"count\";i:685;}s:5:\"media\";a:3:{s:4:\"name\";s:5:\"media\";s:4:\"slug\";s:5:\"media\";s:5:\"count\";i:673;}s:6:\"search\";a:3:{s:4:\"name\";s:6:\"search\";s:4:\"slug\";s:6:\"search\";s:5:\"count\";i:660;}s:4:\"form\";a:3:{s:4:\"name\";s:4:\"form\";s:4:\"slug\";s:4:\"form\";s:5:\"count\";i:657;}s:6:\"jquery\";a:3:{s:4:\"name\";s:6:\"jquery\";s:4:\"slug\";s:6:\"jquery\";s:5:\"count\";i:652;}s:4:\"feed\";a:3:{s:4:\"name\";s:4:\"feed\";s:4:\"slug\";s:4:\"feed\";s:5:\"count\";i:631;}s:4:\"ajax\";a:3:{s:4:\"name\";s:4:\"ajax\";s:4:\"slug\";s:4:\"ajax\";s:5:\"count\";i:622;}s:4:\"menu\";a:3:{s:4:\"name\";s:4:\"menu\";s:4:\"slug\";s:4:\"menu\";s:5:\"count\";i:621;}s:8:\"category\";a:3:{s:4:\"name\";s:8:\"category\";s:4:\"slug\";s:8:\"category\";s:5:\"count\";i:621;}s:5:\"embed\";a:3:{s:4:\"name\";s:5:\"embed\";s:4:\"slug\";s:5:\"embed\";s:5:\"count\";i:589;}s:6:\"editor\";a:3:{s:4:\"name\";s:6:\"editor\";s:4:\"slug\";s:6:\"editor\";s:5:\"count\";i:585;}s:10:\"javascript\";a:3:{s:4:\"name\";s:10:\"javascript\";s:4:\"slug\";s:10:\"javascript\";s:5:\"count\";i:570;}s:3:\"css\";a:3:{s:4:\"name\";s:3:\"css\";s:4:\"slug\";s:3:\"css\";s:5:\"count\";i:566;}s:4:\"link\";a:3:{s:4:\"name\";s:4:\"link\";s:4:\"slug\";s:4:\"link\";s:5:\"count\";i:561;}s:7:\"youtube\";a:3:{s:4:\"name\";s:7:\"youtube\";s:4:\"slug\";s:7:\"youtube\";s:5:\"count\";i:556;}s:12:\"contact-form\";a:3:{s:4:\"name\";s:12:\"contact form\";s:4:\"slug\";s:12:\"contact-form\";s:5:\"count\";i:544;}s:5:\"share\";a:3:{s:4:\"name\";s:5:\"share\";s:4:\"slug\";s:5:\"share\";s:5:\"count\";i:542;}s:5:\"theme\";a:3:{s:4:\"name\";s:5:\"theme\";s:4:\"slug\";s:5:\"theme\";s:5:\"count\";i:533;}s:7:\"comment\";a:3:{s:4:\"name\";s:7:\"comment\";s:4:\"slug\";s:7:\"comment\";s:5:\"count\";i:527;}s:10:\"responsive\";a:3:{s:4:\"name\";s:10:\"responsive\";s:4:\"slug\";s:10:\"responsive\";s:5:\"count\";i:525;}s:9:\"dashboard\";a:3:{s:4:\"name\";s:9:\"dashboard\";s:4:\"slug\";s:9:\"dashboard\";s:5:\"count\";i:516;}s:6:\"custom\";a:3:{s:4:\"name\";s:6:\"custom\";s:4:\"slug\";s:6:\"custom\";s:5:\"count\";i:511;}s:9:\"affiliate\";a:3:{s:4:\"name\";s:9:\"affiliate\";s:4:\"slug\";s:9:\"affiliate\";s:5:\"count\";i:507;}s:3:\"ads\";a:3:{s:4:\"name\";s:3:\"ads\";s:4:\"slug\";s:3:\"ads\";s:5:\"count\";i:504;}s:10:\"categories\";a:3:{s:4:\"name\";s:10:\"categories\";s:4:\"slug\";s:10:\"categories\";s:5:\"count\";i:496;}s:7:\"payment\";a:3:{s:4:\"name\";s:7:\"payment\";s:4:\"slug\";s:7:\"payment\";s:5:\"count\";i:489;}s:4:\"tags\";a:3:{s:4:\"name\";s:4:\"tags\";s:4:\"slug\";s:4:\"tags\";s:5:\"count\";i:477;}s:6:\"button\";a:3:{s:4:\"name\";s:6:\"button\";s:4:\"slug\";s:6:\"button\";s:5:\"count\";i:477;}s:7:\"contact\";a:3:{s:4:\"name\";s:7:\"contact\";s:4:\"slug\";s:7:\"contact\";s:5:\"count\";i:472;}s:4:\"user\";a:3:{s:4:\"name\";s:4:\"user\";s:4:\"slug\";s:4:\"user\";s:5:\"count\";i:469;}s:3:\"api\";a:3:{s:4:\"name\";s:3:\"api\";s:4:\"slug\";s:3:\"api\";s:5:\"count\";i:468;}s:6:\"mobile\";a:3:{s:4:\"name\";s:6:\"mobile\";s:4:\"slug\";s:6:\"mobile\";s:5:\"count\";i:459;}s:5:\"users\";a:3:{s:4:\"name\";s:5:\"users\";s:4:\"slug\";s:5:\"users\";s:5:\"count\";i:453;}s:6:\"events\";a:3:{s:4:\"name\";s:6:\"events\";s:4:\"slug\";s:6:\"events\";s:5:\"count\";i:438;}s:5:\"photo\";a:3:{s:4:\"name\";s:5:\"photo\";s:4:\"slug\";s:5:\"photo\";s:5:\"count\";i:430;}s:15:\"payment-gateway\";a:3:{s:4:\"name\";s:15:\"payment gateway\";s:4:\"slug\";s:15:\"payment-gateway\";s:5:\"count\";i:423;}s:9:\"slideshow\";a:3:{s:4:\"name\";s:9:\"slideshow\";s:4:\"slug\";s:9:\"slideshow\";s:5:\"count\";i:421;}s:6:\"photos\";a:3:{s:4:\"name\";s:6:\"photos\";s:4:\"slug\";s:6:\"photos\";s:5:\"count\";i:417;}s:5:\"stats\";a:3:{s:4:\"name\";s:5:\"stats\";s:4:\"slug\";s:5:\"stats\";s:5:\"count\";i:415;}s:10:\"navigation\";a:3:{s:4:\"name\";s:10:\"navigation\";s:4:\"slug\";s:10:\"navigation\";s:5:\"count\";i:410;}s:10:\"statistics\";a:3:{s:4:\"name\";s:10:\"statistics\";s:4:\"slug\";s:10:\"statistics\";s:5:\"count\";i:399;}s:8:\"calendar\";a:3:{s:4:\"name\";s:8:\"calendar\";s:4:\"slug\";s:8:\"calendar\";s:5:\"count\";i:398;}s:9:\"marketing\";a:3:{s:4:\"name\";s:9:\"marketing\";s:4:\"slug\";s:9:\"marketing\";s:5:\"count\";i:396;}s:4:\"chat\";a:3:{s:4:\"name\";s:4:\"chat\";s:4:\"slug\";s:4:\"chat\";s:5:\"count\";i:394;}s:5:\"popup\";a:3:{s:4:\"name\";s:5:\"popup\";s:4:\"slug\";s:5:\"popup\";s:5:\"count\";i:387;}s:10:\"shortcodes\";a:3:{s:4:\"name\";s:10:\"shortcodes\";s:4:\"slug\";s:10:\"shortcodes\";s:5:\"count\";i:384;}s:4:\"news\";a:3:{s:4:\"name\";s:4:\"news\";s:4:\"slug\";s:4:\"news\";s:5:\"count\";i:384;}s:10:\"newsletter\";a:3:{s:4:\"name\";s:10:\"newsletter\";s:4:\"slug\";s:10:\"newsletter\";s:5:\"count\";i:378;}s:12:\"social-media\";a:3:{s:4:\"name\";s:12:\"social media\";s:4:\"slug\";s:12:\"social-media\";s:5:\"count\";i:372;}s:5:\"forms\";a:3:{s:4:\"name\";s:5:\"forms\";s:4:\"slug\";s:5:\"forms\";s:5:\"count\";i:365;}s:7:\"plugins\";a:3:{s:4:\"name\";s:7:\"plugins\";s:4:\"slug\";s:7:\"plugins\";s:5:\"count\";i:361;}s:4:\"code\";a:3:{s:4:\"name\";s:4:\"code\";s:4:\"slug\";s:4:\"code\";s:5:\"count\";i:360;}s:3:\"url\";a:3:{s:4:\"name\";s:3:\"url\";s:4:\"slug\";s:3:\"url\";s:5:\"count\";i:356;}s:9:\"multisite\";a:3:{s:4:\"name\";s:9:\"multisite\";s:4:\"slug\";s:9:\"multisite\";s:5:\"count\";i:354;}s:8:\"redirect\";a:3:{s:4:\"name\";s:8:\"redirect\";s:4:\"slug\";s:8:\"redirect\";s:5:\"count\";i:350;}s:4:\"meta\";a:3:{s:4:\"name\";s:4:\"meta\";s:4:\"slug\";s:4:\"meta\";s:5:\"count\";i:349;}s:9:\"gutenberg\";a:3:{s:4:\"name\";s:9:\"gutenberg\";s:4:\"slug\";s:9:\"gutenberg\";s:5:\"count\";i:347;}s:4:\"list\";a:3:{s:4:\"name\";s:4:\"list\";s:4:\"slug\";s:4:\"list\";s:5:\"count\";i:346;}s:14:\"contact-form-7\";a:3:{s:4:\"name\";s:14:\"contact form 7\";s:4:\"slug\";s:14:\"contact-form-7\";s:5:\"count\";i:345;}s:11:\"performance\";a:3:{s:4:\"name\";s:11:\"performance\";s:4:\"slug\";s:11:\"performance\";s:5:\"count\";i:337;}s:12:\"notification\";a:3:{s:4:\"name\";s:12:\"notification\";s:4:\"slug\";s:12:\"notification\";s:5:\"count\";i:328;}s:11:\"advertising\";a:3:{s:4:\"name\";s:11:\"advertising\";s:4:\"slug\";s:11:\"advertising\";s:5:\"count\";i:325;}s:16:\"custom-post-type\";a:3:{s:4:\"name\";s:16:\"custom post type\";s:4:\"slug\";s:16:\"custom-post-type\";s:5:\"count\";i:321;}s:8:\"tracking\";a:3:{s:4:\"name\";s:8:\"tracking\";s:4:\"slug\";s:8:\"tracking\";s:5:\"count\";i:319;}s:16:\"google-analytics\";a:3:{s:4:\"name\";s:16:\"google analytics\";s:4:\"slug\";s:16:\"google-analytics\";s:5:\"count\";i:319;}s:6:\"simple\";a:3:{s:4:\"name\";s:6:\"simple\";s:4:\"slug\";s:6:\"simple\";s:5:\"count\";i:316;}s:4:\"html\";a:3:{s:4:\"name\";s:4:\"html\";s:4:\"slug\";s:4:\"html\";s:5:\"count\";i:312;}s:7:\"adsense\";a:3:{s:4:\"name\";s:7:\"adsense\";s:4:\"slug\";s:7:\"adsense\";s:5:\"count\";i:311;}s:6:\"author\";a:3:{s:4:\"name\";s:6:\"author\";s:4:\"slug\";s:6:\"author\";s:5:\"count\";i:310;}}','no'),(260,'_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1560947776','no'),(261,'_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1560904576','no'),(262,'_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9','1560947777','no'),(263,'_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:42:\"WPTavern: WordPress 5.2.2 Squashes 13 Bugs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90869\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wptavern.com/wordpress-5-2-2-squashes-13-bugs\";s: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:1305:\"

WordPress 5.2.2 dubbed a short-cycle maintenance release is available for download. This release addresses 13 bugs and improves the Site Heath features introduced in 5.2.

\n\n\n\n

One of the changes in 5.2.2 affects the theme update link in the Customizer of multisite installs. The update link for themes on multisite installs in the Customizer has been removed. This is because updates can not be performed from within the Customizer in this situation.

\n\n\n\n

Other changes include, adding a exit recovery mode button in the responsive view, making the Site Health page access filterable, and updates to the page editor packages.

\n\n\n\n

JB Audras, Justin Ahinon and Mary Baum co-led the release with guidance from Executive Director, Josepha Haden. Thirty people contributed to WordPress 5.2.2.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 21:24:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:55:\"WordPress.org blog: WordPress 5.2.2 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=6993\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpress.org/news/2019/06/wordpress-5-2-2-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:3947:\"

WordPress 5.2.2 is now available! This maintenance release fixes 13 bugs and adds a little bit of polish to the Site Health feature that made its debut in 5.2.

\n\n\n\n

For more info, browse the full list of changes on Trac or check out the Version 5.2.2 documentation page.

\n\n\n\n

WordPress 5.2.2 is a short-cycle maintenance release. The next major release will be version 5.3; check make.wordpress.org/core for details as they happen.

\n\n\n\n

You can download WordPress 5.2.2 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

JB Audras, Justin Ahinon and Mary Baum co-led this release, with invaluable guidance from our Executive Director, Josepha Haden Chomphosy, and contributions from 30 other contributors. Thank you to everyone who made this release possible!

\n\n\n\n

Andrea Fercia, Andrew Duthie, Andrew Ozz, Andy Fragen, Birgir Erlendsson (birgire), Chetan Prajapati, David Baumwald, Debabrata Karfa, Garrett Hyder, Janki Moradiya, Jb Audras, jitendrabanjara1991, Jonathan Desrosiers, Jonny Harris, Jorge Costa, Justin Ahinon, Marius L. J., Mary Baum, Meet Makadia, Milan Dinić, Mukesh Panchal, palmiak, Pedro Mendonça, Peter Wilson, Rami Yushuvaev, Riad Benguella, sarah semark, Sergey Biryukov, Shashank Panchal, Tammie Lister, Tim Hengeveld, vaishalipanchal, vrimill, and William Earnhardt

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 18:14:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"marybaum\";s: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:44:\"WPTavern: In Case You Missed It – Issue 26\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90840&preview=true&preview_id=90840\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/in-case-you-missed-it-issue-26\";s: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:7430:\"

photo credit: Night Moves – (license)

\n

There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.

\n

Birgit Olzem Could Use the Community’s Help

\n

Birgit Olzem has encountered some financial hard times due to multiple illnesses and paying for acupuncture treatments and osteopathic therapy which are not covered by her insurance. Olzem fell ill earlier this year which prevented her from generating income as a self-employed person.

\n
\n

Dear #WordPress community!

\n

Today I turn to you with a request that I find very difficult to make. \"?\"

\n

Over the last 7 years, I\'ve invested a lot of time and money in the contributions for WordPress. Despite five children, part-time jobs and chronic diseases. #Thread

\n

— Birgit Olzem (@CoachBirgit) June 13, 2019

\n

\n
\n

If my contributions to #WordPress have helped in any way over the years, or you just like me as a person, I\'d be happy if you would help me become healthy again.https://t.co/wfmJ3WOXMn

\n

My eternal thanks will come to you. \"?\"

\n

7/7 pic.twitter.com/i98dU1EC1S

\n

— Birgit Olzem (@CoachBirgit) June 13, 2019

\n

\n

Olzem has translated WordPress, compiled release packages for de_DE, organized Meetups, WordCamps, answered support questions and has been part of different make/WordPress teams, some of them as a team-rep. She’s also contributed to WordCamps as a Speaker, Volunteer and Contributor day team-lead.

\n

To learn more about her story and to donate, please read her request to the community.

\n

Liam Dempsey’s Take on Gutenberg

\n

Liam Dempsey describes what he likes and doesn’t like about the new WordPress editor.

\n

Defending the Right to Publish Open Source Software in the UK

\n

The EFF and Open Rights Group have submitted comments to the UK government defending the right to publish open source software.

\n

Moreover, source code is a form of written creative expression, and open source code is a form of public discourse. Regulating its publication under anti-money-laundering provisions fails to honor the free expression rights of software creators in the United Kingdom, and their collaborators and users in the rest of the world.

\n

Why Is It Important to Give Back to Open Source?

\n

JC Mae Palmes on Twitter asked, why is it important to give back to the WordPress community? Here are a few responses. To see all of the responses, check out this Twitter thread. 

\n
\n

WordPress powers 34% of the web, it\'s a career advantage, the community is awesome, the product is used by students and enterprises alike, you can directly talk to incredibly knowledgeable people and learn a ton

\n

— Mario Peshev (@no_fear_inc) June 13, 2019

\n

\n
\n

Open Source projects live and die by the willingness of those who benefit from the project giving back to the project.

\n

— Morten i Danmark \"??\" (@mor10) June 13, 2019

\n

\n
\n

You realize you’re not alone. The mistakes you make are normal, that everyone’s figuring it out as they go. It gives you access to experience at all levels and people to brainstorm with who have unique perspectives.

\n

— Cate DeRosia (@mysweetcate) June 13, 2019

\n

\n

WordCamp US Speaker Selection Process

\n

If you’re wondering how speakers are being selected for WordCamp US this year, check out this post by the Programming Team. The team is using a new process that includes, limiting the number of submissions per speaker to two instead of unlimited, reviewing submissions based on the organizer’s sphere of experience, and using blind reviews. Speakers who are chosen are scheduled to be notified by the end of this month.

\n

An Easy Way to Make an Impact in The WordPress Community

\n

David Bisset shared the following idea on Twitter and while a few companies have started doing this, I think it will catch on with individuals more than businesses.

\n
\n

Are you a company that wants to make an impact in the #WordPress space but doesn’t have alot of $$$?

\n

Buy some tickets for people to attend WordCamps. Especially people (youths, non-profits, not privileged) that wouldn’t normally consider going.

\n

— David Bisset (@dimensionmedia) June 14, 2019

\n

\n

That’s it for issue twenty-six. If you recently discovered a cool resource or post related to WordPress, please share it with us in the comments.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 14 Jun 2019 22:06: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: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:67:\"WPTavern: Justin Tadlock Proposes Idea to Solve Common Theme Issues\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90725\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/justin-tadlock-proposes-idea-to-solve-common-theme-issues\";s: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:2119:\"

The Theme Review Team has been discussing ideas in Slack on how to solve the problem of themes in the review queue suffering from common theme issues. Just Tadlock has proposed a idea he calls Theme Feature Repositories.

\n\n\n\n

The idea is to create standardized packages on the Theme Review Team GitHub repo that authors could use in their themes. If enough people bought into the idea and worked together, it would lessen the pain points between reviewers and theme authors. It would also decrease the amount of code written by hundreds of different authors to solve a common problem.

\n\n\n\n

Tadlock used Admin notices and Links to ‘Pro’ versions as two examples that could benefit from this approach. Packages would handle specific use cases and be installed using Composer. For those who don’t use composer, an autoloader would be provided as well as a .zip file that could be dropped into a theme.

\n\n\n\n

Tadlock is asking the theme community what packages do they need or what common problems could be solved together.

\n\n\n\n

“This can literally be any common feature in WordPress themes, not just admin or customizer-related things,” Tadlock said. “Nothing is ‘out of bounds’. Every idea is on the table right now.

\n\n\n\n

“This is an ambitious project. It’d require cooperation between authors and reviewers for the betterment of the theme directory as a whole. It’ll only work if we have buy-in from everyone.”

\n\n\n\n

Tadlock also mentioned that due to his schedule, he will be unable to lead or co-lead the project and is seeking people interested in taking on these roles. Those interested should have knowledge of Git, Composer, and Object-oriented programming.

\n\n\n\n

If you’re interested in this project or want to provide feedback, you can leave a comment on the proposal.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 21:07: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: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:106:\"WPTavern: WordPress Spanish Translation Team Now has Meta Sites, Apps, and Top 200 Plugins 100% Translated\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90804\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/wordpress-spanish-translation-team-now-has-meta-sites-apps-and-top-200-plugins-100-translated\";s: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:5640:\"

The Spanish WordPress community hit a remarkable milestone with translations this week. Polyglots volunteers have now translated the meta sites, WordPress apps, and the top 200 plugins at 100% completion, with no pending translations to review.

\n
\n

La comunidad #WordPress España @wp_es sigue batiendo récords.

\n

No solo no hay traducciones pendientes de revisar, sino que tiene siempre traducido al 100% WordPress, sitios meta, aplicaciones y, ahora, también al 100% el Top 200 Plugins.

\n

Únete al equipo: https://t.co/ymTyKpvt7L pic.twitter.com/6OtoQHwVoA

\n

— WordPress España (@wp_es) June 10, 2019

\n

\n

The size of the team is a major factor in reaching this milestone. According to stats Naoko Takano shared at WordPress Translation Day 4 last month, Spanish is the locale with the most translation contributors (2,863), followed by German (2,399), Italian (2,190), Dutch (1,584), and Russian (1,515). It is also one of the top non-English locales installed, with 5.0% of all WordPress sites using the translation. WordPress.com reports similar numbers, where Spanish is the second most popular language for blogs at 4.7%.

\n

Rocío Valdivia, a Community Wrangler at WordCamp Central who lives in Spain, gave us a look at what is behind the team’s extraordinary growth and momentum. She identified several key factors that have contributed to their success in working efficiently and sharing useful information among team members during the past 2-3 years.

\n

“We created a Slack instance some years ago, but at the beginning it was common for people to join and ask for support questions,” Valdivia said. “Now we have some protocols: the general channel is an only-read channel. If someone ask for support, we send them with a kind predef to the es.wordpress.org forums, where they get answers in a few hours. There are no questions in the forums waiting for longer than six hours ever, as we have a very active support team that coordinates in the #support channel of our Slack.”

\n

Valdivia said that removing the noise of support requests has given the team very productive channels for translations, plugin and theme translations, meetups (where Meetup organizers share tips and resources using a shared Google drive folder), and WordCamps (where WC organizers share info, tips, answer questions in Spanish, and share resources like email templates.)

\n

“Besides all of this, we’ve worked very well passing the philosophy of the project to the new members from the most experienced ones,” Valdivia said. “For example, people do very soft transitions from one lead organizer to the next one.”

\n

Although some WordCamp attendees have complained in the past that not much is accomplished at Contributor Days, the Spanish community has had success using these opportunities to transfer knowledge to new leaders and contributors. The community hosted 10 WordCamps in 2018 and Valdivia estimates they will have 9-10 in 2019. WordCamp Barcelona 2018 and 2019 had 400 attendees and 180 people at their Contributor Days. WC Irun 2019 had 220 attendees and 100 participants at Contributor Day. WordCamp Madrid 2019 sold out with 600 attendees and approximately 200 participated in Contributor Day.

\n

Although the Spanish community has experienced contributors across several WordPress.org teams, such as WPTV, Community, Support, and Polyglots, Valdivia said they are a bit thin on Core contributors.

\n

“We’re lacking people with experience contributing frequently to Core,” Valdivia said. “We have some of them who have contributed several times, but still need more people with more involvement to be able to pass all this info to newcomers.”

\n

Strong local meetups are another factor in the Spanish community’s success at keeping translations up-to-date. In addition to the largest team of translators in the world of WordPress, Spain has the second highest number of meetup groups and events per month. Spain is running 64 local meetups, with a population of 46 million people, compared to 201 groups in the U.S., which has 7x the population size (327 million).

\n

\n

“The language barrier has been an issue for years, as not everyone speaks English and not everyone feels confident following conversations in English,” Valdivia said. “So, being able to train our own teams of contributors in our own language and having our own shared resources and channels, has been very useful.”

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 20:22: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: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:105:\"WPTavern: WPWeekly Episode 356 – Gutenberg, Governance, and Contributing to WordPress with Jonny Harris\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90817&preview=true&preview_id=90817\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/wpweekly-episode-356-gutenberg-governance-and-contributing-to-wordpress-with-jonny-harris\";s: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:1955:\"

In this episode, John James Jacoby and I are joined by Jonny Harris. Jonny describes how he discovered WordPress and some of the core projects he’s been working on including, Site Health Checks, fatal error protection, and Multisite. We discuss WordPress’ focus on users vs developers in recent years, Jonny’s experience contributing to core, and his thoughts on a WordPress governance model.

\n

Stories Discussed:

\n

WordPress Is Borked So Enjoy This Glorious Plant That’s Taking Over the Internet

\n

WP Engine Launches DevKit Open Beta

\n

Drupal Gutenberg 1.0 Released, Now Ready for Production Sites

\n

BuddyPress 5.0 to Update Password Control to Match WordPress

\n

Transcript:

\n

Episode 356 Transcript

\n

WPWeekly Meta:

\n

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

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #356:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 20:08:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"WPTavern: Pika Project Launches New JavaScript CDN to Serve Modern, ESM Packages\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90762\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/pika-project-launches-new-javascript-cdn-to-serve-modern-esm-packages\";s: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:7138:\"

\n

Fred Schott, a software developer and former Google employee on the Polymer team, has launched a new CDN for his Pika project. Schott’s mission with Pika is “to make modern JavaScript more accessible by making it easier to find, publish, install, and use modern packages on npm.” Pika provides a searchable catalog of “module” packages available on npm – packages that use the more compact ES module syntax (ESM), which result in smaller Javascript bundles.

\n

npm currently lists 59,851 ES modules. This makes up approximately 7% of total packages on npm are exporting an ES module, but the number is steadily increasing:

\n

\n

Pika makes it easy to search for these packages and the results will only include those that have a defined “module” entry point in their package.json manifest. Each listing consolidates the relevant information on one page, highlighting the important details.

\n

\n

One of the chief advantages of using ES modules is that they run natively on the web, without the need for a bundler. In a post titled “A Future Without Webpack,” Schott contends that JavaScript developers are “so steeped in the world of bundlers” that they overlook the possibilities of using ESM dependencies that run directly on the web:

\n

Over the last several years, JavaScript bundling has morphed from a production-only optimization into a required build step for most web applications. Whether you love this or hate it, it’s hard to deny that bundlers have added a ton of new complexity to web development – a field of development that has always taken pride in its view-source, easy-to-get-started ethos.

\n

@pika/web is an attempt to free web development from the bundler requirement. In 2019, you should use a bundler because you want to, not because you need to.

\n

Schott created @pika/web to make it easy for developers to use ES modules, even when they don’t have compatible dependencies. It provides an install-time tool that is not exactly a build tool or a bundler but works to output web-native npm dependencies into a single ESM .js file:

\n

@pika/web checks your package.json manifest for any “dependencies” that export a valid ESM “module” entry point, and then installs them to a local web_modules/ directory. @pika/web works on any ESM package, even ones with ESM & Common.js internal dependencies.

\n

Installed packages run in the browser because @pika/web bundles each package into a single, web-ready ESM .js file. For example: The entire “preact” package is installed to web_modules/preact.js. This takes care of anything bad that the package may be doing internally, while preserving the original package interface.

\n

Here’s a demo of how that works:

\n
\n

¡OJO con @pika/web! \"?\"\"⚡\"

\n

\"?\" Instala tus dependencias npm y úsalas directamente en el navegador.
\"✨\" Sin bundlers, ni configuraciones de ningún tipo.
\"⚡\" Nativo, ESM, optimizado para http2… ¡y MUY rápido!

\n

¡Muy pronto, vídeo más completo y artículo en https://t.co/uc7bPEkbXB \"?‍?\"! pic.twitter.com/cdNWqBnrDc

\n

— Miguel Ángel Durán \"?‍?\" (@midudev) March 2, 2019

\n

\n

This week Schott announced the availability of a new Pika CDN for delivering modern ES module packages. It uses the pikapkg/web package builder to work with any ESM package and the CDN will automagically handle any non-ESM dependencies of that package. Pika CDN automatically detects the visitor’s browser and serves JS that is optimized to the environment, eliminating polyfills and transpiler bloat wherever possible.

\n

\n

“Pika CDN leverages your browser’s natural caching abilities to give your pages faster dependency load times, especially on first visit,” Schott said. “0ms first-loads are even possible (for your dependencies at least) if all packages have been seen before.

\n

“With our CDN, package authors can distribute more modern, unminified packages without worrying about how to serve them directly. Instead, our nifty package-builder automatically resolves each package — and any legacy sub-dependencies — into a single, minified, ready-to-import JavaScript file.”

\n

Schott recently left his position at Ripple to work full-time on Pika, a project that he believes will move the JavaScript ecosystem forward.

\n

“Leaving my team was one of the hardest decisions I’ve ever made, but I know that I’m needed here,” he said. “I’m so excited to be a part of the future of the web, whatever it ends up looking like.”

\n

Pika is looking for corporate sponsors. For now, Schott is funding the server costs using Patreon.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 13 Jun 2019 15:54:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:96:\"WPTavern: Gutenberg 5.9 Brings Major Improvements to Block Grouping, Introduces Snackbar Notices\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90747\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:106:\"https://wptavern.com/gutenberg-5-9-brings-major-improvements-to-block-grouping-introduces-snackbar-notices\";s: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:2988:\"

Gutenberg 5.9 is now available for those who are running the plugin to get the latest features on their sites. This release brings significant improvements to the grouping capabilities, allowing users to group and ungroup blocks inside a container block. Once placed inside a group, the blocks can be moved up or down within the group using simple up/down controls.

\n

\n

Nested blocks have also been improved so that users can click through to each layer to configure each and navigate to the deepest nested block.

\n

Gutenberg 5.9 introduces “Snackbar” notices to communicate completed actions in the block editor UI that do not require further action.

\n

The term “Snackbar” doesn’t adequately describe the way these notices behave. The concept was inspired by Material design and is traditionally used for providing brief messages about app processes at the bottom of the screen. Gutenberg’s new Snackbars pop up and disappear after a short delay, so the notice doesn’t have to be dismissed.

\n

“For a distraction-free experience, all the notices used in the editor to inform about the post saving/publishing, reusable blocks creation and updates have been updated to use this new type of notice,” Gutenberg Phase 2 lead Riad Benguella said. He posted a gif demonstrating Snackbar notices in action:

\n

\n

This release brings several visual enhancements to blocks and UI components, including a redesign of the Table block placeholder, refactoring and consolidation of dropdown menus, and improvements the output of the Spacer block.

\n

Gutenberg 5.9 contains more than two dozen fixes for bugs found in both desktop and mobile experiences. The editor took a slight dip in performance from the previous version, going from 4.8 to 4.9 seconds in loading time and 62.8ms to 66.3ms for keypress events. More than 40 people contributed to this release and approximately 15% were new contributors.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jun 2019 18:54:51 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:8;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"HeroPress: My “Hero’s Journey” Through the Dark Underworld of WordPress Hosting\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=2862\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:204:\"https://heropress.com/essays/my-heros-journey-through-the-dark-underworld-of-wordpress-hosting/#utm_source=rss&utm_medium=rss&utm_campaign=my-heros-journey-through-the-dark-underworld-of-wordpress-hosting\";s: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:22301:\"\"Pull

The following is an expanded and updated version of my presentation at WordCamp Salt Lake City 2017.

\n

My girls love Moana. Especially when it first came to video and they could watch it every day… or two or three times a day if mom wasn’t feeling good or catching up on sleep from being up with baby brother the night before.

\n

There’s this strange part of that movie where Moana follows Maui to a place under the ocean called “The Realm of Monsters.” It’s where monsters go after being killed. If you have younger kids, you know what I’m talking about. If you don’t have kids, it’s when the giant crab sings the song “Shiny.”

\n

\n

One common theme in myths, legends, and ancient religious writings, is where the hero visits the underworld, aka “afterlife” or “hell.” There they experience a symbolic or actual death for themselves or a loved one. Often through conquering a monster who is the Lord of the Underworld, they then re-emerge with their loved one, new knowledge and power, and/or some object to help them on their quest.

\n

The film Moana clearly plays out this theme. She and Maui emerge triumphant from the realm of monsters, having defeated the giant crab by flipping it on its back and retrieving Maui’s magical hook.

\n

In Return of the Jedi, Luke descends to the underworld of Jabba’s Palace. There, he’s able to bring his friend Han Solo back from a virtual death, defeat the Rancor, kill Jabba the Hut (lord of the criminal underworld), save the princess, and retrieve his lightsaber. All this happens before we see even one single, fuzzy, cute, unblinking Ewok…. Unless you believe in the “special editions,” in which case the Ewoks blink.

\n

\n

There are many movies, books, stories, mythologies, etc that all follow similar patterns.

\n

Like Maui’s hook or Luke’s lightsaber, in these stories the hero often emerges from the underworld with newfound knowledge and/or a powerful object. Briefly, I’d like to take you on my own personal “Hero’s Journey” to the dark underworld of WordPress hosting. Along with it my quest of building a business on WordPress and hosting, with its own mythical monsters to slay, trials to be conquered, riddles to be solved, and ultimately new knowledge and weapons gained.

\n

The Call to Adventure

\n

In the early days of my business, Fiddler Online (now called WordXpress), I envisioned building websites for companies on WordPress, then charging a monthly fee to maintain, support, edit, update, and manage them. I got started with a few clients and wanted to grow.

\n

I’d trusted someone to set me up with a very inexpensive VPS on unmanaged hosting. He was supposed to do the managing and ensure it all ran smoothly. I quickly learned you get what you pay for! Soon our members’ sites started going offline, usually all at once as the VPS crashed from one problem or another. It wasn’t just the server being down that caused problems. It was also corrupting data and other strange and scary things that I’d never encountered before, such as the body content of posts and pages being cut off, starting with the first special character that appeared in the content (a database issue).

\n

\n

These were dark and scary monsters to battle. I knew cPanel pretty well, but the APACHE stack that ran beneath it was mostly a mystery to me. So was database encoding and other advanced technical realms that all have an impact on the server, WordPress, and ultimately our clients’ businesses.

\n

The monsters appeared, seemingly determined to kill my small and struggling business, shortly after the birth of our first child. I was frequently up all night working with “Todd” the server guy (we’ll call him) to try and get the websites back online. We’d vanquish one monster, rest a day or so, and find another had taken some sites down again.

\n

After a few weeks of constant frustration, I said “enough” and signed up for a Hostgator reseller plan. This was back when they were an independent hosting company. On this new plan I could install as many cPanel’s as I needed and manage each separately! I thought it was wonderful and would solve all my problems. Hostgator transferred all our sites from the terrible VPS hosting we’d been on to their servers and I thought perhaps that was it!

\n

I thought my quest was over. I’d fought the monsters and won.

\n

Scary as it was, it had been relatively brief. I’d learned a lot, but felt like I’d been to the underworld and back!

\n

The Illusion of Safety

\n

Unfortunately, the wraiths had cast a spell over me, blinding me to the fact that they were still lurking in the shadows. When transferring our WordPress websites to our new account, Hostgator had copied each entire cPanel over from the VPS. This eliminated the underlying problems in the APACHE stack on that horrible VPS, but brought with it the fiends that had infiltrated cPanel and even our WordPress websites. To be clear: they weren’t infected with any kind of malware, but configuration problems, cruft, and who knows what else, caused some really bad results.

\n

With my new spellbound, but misled confidence, I pushed our business forward. I brought on a business partner, Kurt as the sales guy. Later we acquired another website company. Through all that, we’d learned a lot, and doing okay for that stage, but still struggled financially as we bootstrapped this new business from nothing.

\n

When we acquired this other business, they’d been running all their client’s sites on WordPress Multisite. It seemed like a great idea because of how it allowed us to manage all the websites in one place.

\n

Despite the progress the business made, the monstrosities emerged again and this time with higher stakes since our business had grown and was now managing many more websites. These monsters emerged partly from what had been transferred over with cPanel, and the difficulties of running a large Multisite where each child site had its own theme, plus the weight of adding more and more websites and traffic to hosting that was really just shared hosting with WHM access and more control.

\n

\n

The Plunge Into the Underworld

\n

In each hero’s journey, there’s often a wizard or goddess that helps guide and mentor the hero along his journey. I eventually made friends with a great guy we’ll call Sam. He ran his own hosting company with data centers and a great support staff. Sam was somewhat like Obi-Wan, Merlin, or Maui in these stories: he was my mentor and companion on my adventures into the underworld that followed. He made a great guide, because he’d been there before. Unfortunately, his own journey had never taken him to some of the deepest darkest places we would soon encounter.

\n

So we moved to Sam’s hosting, where he kindly watched things closely and provided a server admin’s perspective and advice at a much lower price than he would have normally charged.

\n

It wasn’t long before the demons, wraiths, monsters, and other ghouls started crawling from the darkness. It started with random downtime. Then followed strange limitations on websites. Next emails were not getting delivered. Then it was slowness. Now we were hacked… or were we? Suddenly all the contents of all pages and posts were cut off (we thought we killed this monster before)! Then email wasn’t being sent. Next our server is sending spam email. Now a hard drive is dying. It just kept going and going. Many of these demons were completely new to Sam and his very experienced team.

\n

It didn’t take long before there were whisperings of “the Fiddler curse.” This curse referred to Fiddler Online the name of our company. The hosting support team joked that we were cursed. All kinds of issues arose that they’d never seen before, and with a frequency they’d never experienced either.

\n

When a car crashed into the data center’s power regulation center during a freak storm, it cut off power from the normal power lines, as well as from their automatic backup power supply! It completely took the data center offline. The “Fiddler curse” was in full force.

\n

Or put better, we were in the deepest, darkest, part of the underworld, locked in an all-out battle with the worst demons and wraiths it had to send against us.

\n

We tried method after method to defeat the monsters. We tried rebuilding the server stacks. We tried various WordPress optimizations. We bought our own server and had it installed in their data center. We even tried a totally different Linux stack and something called Interworx, a cPanel alternative, that came with load balancing and real-time backup. But no matter how much money, time, and knowledge we threw at it, the issues continued. No matter how many monsters we slew, we were still losing the war.

\n

The “Real World” Dragons

\n

When I recently asked my wife Jill about that time of our lives, she said:

\n

“From my perspective, it was hard to know when to throw in the towel and say ‘enough’ because it’s just not working. Getting the hosting sorted out totally changed the entire dynamic and perspective of doing our own business. Before that, it felt like we were building a dream on a crumbling foundation.”

\n

\n

And don’t get the wrong idea from this image. Jill was no damsel in distress. She’s a warrior too. I’d have never completed this quest without her there, fighting alongside me. She may have not fought the technical fiends, but there were plenty other monsters in the form of financial struggles, moves, and difficult situations that arose from my unavailability, our lack of money, and more.

\n

This was all a lot like battling the Hydra of Lerna: we’d cut off one head, and two would grow back in its place. We’d take a breather for a week, and then here came the wraiths!

\n

The stress of it all exacerbated a gallstone problem I had. Because of a misdiagnosis, I thought it was something there was no solution for. So even when I wasn’t up in the middle of the night battling monsters demons of the hosting underworld with Sam, I was often awake at night in massive amounts of pain as my gallbladder tried to pass gigantic gallstones. So even then, I’d be sleeping the next day when I needed to be designing websites or networking.

\n

Throw in a healthy dose of anxiety and some intermittent depression and you get the picture. Instead of growing, our business stagnated. The quest through this dark underworld seemed to have no end in sight. It ruined vacations, stole away family time, punished me physically, hurt our client’s business, and was pushing myself, Jill, and our finances, to our very limits.

\n

Death and Rebirth

\n

It all seemed to come to a head when the pain of my gallstones became so intense I thought I was going to die. After 2 visits to the Emergency Room and 3 days in the hospital, I gave birth to this baby. They actually saw a larger one than this in the ultrasound beforehand, but my body had apparently broken it up before they removed my gallbladder. I returned home with real-world wounds that would turn into scars, and lighter by one gallbladder and several massive gallstones.

\n

\n

I left the hospital with a new lease on life. I felt like I’d been resurrected, fighting my way out of the underworld and back to the land of the living. It helped me open up to a completely different approach to hosting and allowed me to see that tiny speck of light that ended up being the doorway out of this underworld made up of the dark side of WordPress and hosting.

\n

I was able to use my newfound perspective to find some awesome new weapons, and fight my way to that exit. Luckily for you, you can learn from my pain and battles with the underworld.

\n

The Road Back: Simplify

\n

Illumination was mine! Of the knowledge I gained, one key principle stood out among the rest: make things as simple as possible, while avoiding single points of failure on mission-critical systems. Multisite was great for managing all the websites at once, but if one had a problem, they all went down! The same with having a single server to run all our sites: if the server went down, we had the urgency of 30 or 40 clients (back then) all being negatively impacted at once.

\n

We started by killing our Multisites and traditional hosting setups. Instead of a single Multisite with 1 database where a problem could take down all the sites in the Multisite, we moved to individual WordPress installs for each site. As we pulled each site out of the Multisite and migrated it to our new cloud hosting, we also checked the databases and files thoroughly to ensure they were clean, light, and that we eliminated any cruft that had built up in the database. We also stopped running email and DNS through our web servers. This effectively killed the demons that had moved with us in previous hosting migrations.

\n

Here’s my recommended do’s and don’ts for any smaller businesses hosting and maintaining WordPress websites:

\n

Don’t:

\n
    \n
  1. use shared hosting or hosting that uses cPanel
  2. \n
  3. use Multisite (SPoF)
  4. \n
  5. put all your sites on 1 server (SPoF)
  6. \n
  7. use your web server as an email server
  8. \n
  9. send WordPress transactional emails from your webserver
  10. \n
  11. use your web server for DNS
  12. \n
  13. use your hosting company for domain registration
  14. \n
\n

Do:

\n
    \n
  1. use cloud hosting with WordPress-optimized stack and custom control panel
  2. \n
  3. use a bulk-site-management tool
  4. \n
  5. spread your sites across multiple servers
  6. \n
  7. use an email suite (Hover, Zoho, G Suite, Office 365)
  8. \n
  9. use a transactional email service (SendGrid, Postmark, MailGun)
  10. \n
  11. use your registrar for DNS
  12. \n
  13. use a different registrar for registering domains, than your hosting
  14. \n
\n

Following these tips eliminates many single points of failure, simplifies things greatly, and gives you the tools and ability to go right to the source of the problem. Since all your important WordPress functionality isn’t in one place with one point of failure, you can go where the problem is.

\n

For example, if a client isn’t receiving WooCommerce new order emails from their website, we can quickly go to SendGrid to see why that is and what needs to be done to fix it in an easy to use interface. Try that on a traditional APACHE/cPanel setup that sends your client’s company emails, WordPress emails, etc. all from one place.

\n

\n

Cloud Hosting

\n

We eliminated cPanel and the normal Linux hosting stacks by moving to CloudWays, which has a nice WordPress setup that they run on top of a number of cloud hosting services such as Google, Amazon, Digital Ocean, and Vultr. They have their own in-house customized stack and management dashboard. CloudWays removed all the normal bloat and potential for problems that comes with it, and really took away most of the pain, hassle, and responsibility of the hosting part of WordPress and for quite cheap.

\n

On CloudWays, instead of putting all 40+ sites on one server, we split them up, with about 15 – 18 sites on one small Digital Ocean (and later Vultr) server. This meant that if one site had issues, it wouldn’t take down all our other sites. And even if the issue was bad enough to affect the whole server, or the server had its own issues, only a small portion of our clients would be affected at once.

\n

Email Accounts and Transactional Email

\n

Additionally, we stopped running email through our servers. Part of simplifying is outsourcing to people/services who can just do it better than you (or that old hosting you’re clinging to because it’s cheap). I love that good WordPress hosts like CloudWays, Flywheel, and Kinsta have no options for you to do this or include built-in services like SendGrid. I slew a lot of email monsters. Using something like SendGrid or Postmark for WordPress and G Suite or Office 365 for email accounts, eliminates tons of headaches.

\n

We set up WordPress’s emails to go through SendGrid and all our members’ email accounts we migrated to Hover, Google Apps, or Office 365.

\n

Bulk-WordPress Management

\n

In place of Multisite, we found MainWP and chose it over other options like InfiniteWP. It provided us the bulk-control of Multisite, but without the single point of failure issue. The upside is that it’s fairly inexpensive and runs on a WordPress install, so you control it on your hosting.

\n

That’s kinda its downside as well. If something goes wrong, it’s on my team and I to run the problem down and fix it. Or we have to go through the cumbersome process of reporting it to the MainWP support team, then providing them access to both the dashboard site and an affected child site. Eventually we decided to move to ManageWP because it’s a hosted platform. That means when something goes wrong, much of the time, it’s on them to fix, and they have access to fix their own platform, plus the logs, etc from our sites.

\n

MainWP:

\n\n

ManageWP:

\n\n

Master of Two Worlds of WordPress

\n

Fortunately today there are many awesome hosting options and bulk-management tools that simply weren’t available to me years ago when I started on this journey. After this last, final push, my team and I stood back and waited and rested, expecting more monsters. And occasionally one crawled out of it’s hole. But by and large the underworld was defeated and left far behind. Moving to cloud hosting and simplifying were finally the spell that broke the Fiddler curse and freed us from the underworld. Our business’s core service was stable and safe and running like it should be. We could start growing again! It was such a relief!

\n

To reiterate some of the illumination gained on my journey: simplify your WordPress websites and hosting through offloading everything you can to experts who do it better, often for cheaper (if you properly calculate the value of your own time). Focus on your super-power whether it be design or development, or just creating solutions on WP with existing plugins and tools. If your super-power isn’t WordPress at all, you can outsource maintenance, content updates, backups and security, plugin and core updates, and much more to a company like WordXpress. I’ve built this company based on the knowledge and tools I learned on my quest.

\n

The post My “Hero’s Journey” Through the Dark Underworld of WordPress Hosting appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 12 Jun 2019 12:00:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Tevya Washburn\";s: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:71:\"WPTavern: Drupal Gutenberg 1.0 Released, Now Ready for Production 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=90376\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/drupal-gutenberg-1-0-released-now-ready-for-production-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:6201:\"

The Gutenberg module for Drupal, created by Frontkom, reached the 1.0 milestone earlier this month. It is the first stable release recommended for use in production with Drupal 8.x.

\n

The 1.0 release removes the Gutenberg-JS dependency and uses Gutenberg core files directly. It is based on Gutenberg version 5.6.1, which was released in early May. The module boasts better handling for media files, adding support for title, caption, and alternative text. It also adds an “Allowed Blocks UI” to the content type admin UI, so administrators can restrict which blocks show up in the block selector.

\n

“We’re now ready for production sites in the sense that we’ll be more careful with structure changes, will try to do update paths when possible, and will create automated tests for crucial functionality,” Frontkom project manager Thor Andre Gretland said. “We’ve solved the blockers for a stable release.”

\n

Upgrading the module from RC-1 may require some extra steps, because it is a big jump, taking the Gutenberg library from 4.8.0 to 5.6.1. Users will need to update the database. It is also necessary to navigate to content types and click save to enable Gutenberg again so that it will begin storing the Allowed blocks in the database. If users get notices about invalid blocks, they are advised to try the Attempt Block Recovery option:

\n

\n

“It’s actually a rather large update,” Gretland said. “We were planning to add a couple of last needed features to release our 1.0 version, but ended up using the latest Gutenberg version with several new great features. We’re also using more of the Gutenberg Core, that we’ve been able to use before.”

\n

The module still has one critical issue that Frontkom is working on. Reusable blocks are not working with the latest release. Users are getting a “this block is unavailable or deleted” message when attempting to insert a reusable block. In the meantime, those who require this feature can roll back to RC1 to get it working again.

\n

So far the Gutenberg module has been well-received. It has been downloaded more than 12,000 times and 494 sites are reported to be using it.

\n
\n

Setup @drupalgutenberg on D8 yesterday (following meeting one of @frontkom at the recent Dutch #CiviCRM sprint) and was pretty blown away. Bringing Medium-style editing to all the CMSs & then some. If #Joomla doesn’t implement a Gutenberg.js integration we/they’ll be left behind. https://t.co/SfieuGfOlf

\n

— Nicol (@netribution) May 28, 2019

\n

\n

Drupal’s Gutenberg module includes access to the Gutenberg Cloud library of free blocks. Although the library has been slow to gain contributors, it does contain several blocks that are helpful for creating page layouts, such as Content in Columns, Hero Section, Section Wrapper, Section Row, and a Feature Box block. Site administrators can also use the Gutenberg module in combination with Drupal’s new Layout Builder, which was introduced as a stable module to Drupal 8.7 core.

\n

“We see a valid use case for mixing Drupal Gutenberg with the Drupal layout builder when you might want to create layout templates with the layout builder, and keep the actual content editing in Gutenberg,” Gretland said. “For example you could use the layout builder to define fixed byline elements for author and create date, but leave the actual content creation experience to Gutenberg.”

\n

There are a few limitations to using the two tools together. The only way to use them on the same project is if they deal with different content types.

\n

“Since Drupal Gutenberg takes over the whole node UI, it can have some unexpected effects when used together with Layout Builder,” Gretland said. “That doesn’t mean that they won’t ever ‘work’ together. One idea could be using the LB data structure to generate Gutenberg fixed layouts/templates and even save Gutenberg data in a structured way handled by Layout Builder.”

\n

Gretland said his team believes Gutenberg delivers a better editing experience than Layout Builder, as it is a more mature project. However, Layout Builder stores its data in a structured way, which has its advantages and disadvantages over Gutenberg.

\n

WebWash has a good video tutorial for Drupal users who want to learn how to configure the Gutenberg module and use it on the Page content type. It includes a walkthrough for common actions like uploading images, creating reusable blocks, and using the Gutenberg Cloud. If you want to see how Gutenberg can improve Drupal’s authoring experience without installing the module, check out the frontend demo of Drupal Gutenberg created by the team at Frontkom.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jun 2019 23:03: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: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: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:45:\"WPTavern: WP Engine Launches DevKit Open Beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90715\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wptavern.com/wp-engine-launches-devkit-open-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2627:\"

Those who host or manage sites on WP Engine now have a new tool at their disposal. It’s called DevKit, developed by Chris Wiegman and Jason Stallings.

\n\n\n\n

DevKit is a WordPress local development environment that includes SSH Gateway access, push and pull deployments to WP Engine, Command Line Interface commands for the Genesis theme framework and other tools.

\n\n\n\n

Although DevKit has tight integration with WP Engine the software can be used independently of the host. With Local by Flywheel, Vagrant, XAMPP, and other tools available, Wiegman explains what motivated him to create a new solution.

\n\n\n\n

“I’ve been working on the perfect WordPress developer environment since I learned about Vagrant in 2013,” he said. “As it was never my full-time job, I could never take it to the next level. DevKit gives me the power to do that.”

\n\n\n\n

Stallings added, “We wanted to build a kick ass set of tools for developers building on WP Engine. That’s been our mission from the start, build something that all developers want to use (including us)!”

\n\n\n\n

As what for what sets DevKit apart from the others, “I think our architecture is very different from both tools,” Stallings said.

\n\n\n\n

“Similar to Docker Engine, DevKit CLI is the interface to DevKit. So when we build the GUI it will 100% complement the CLI, and the two can be used interchangeably. This will enable us to build other interfaces in the future too.”

\n\n\n\n

DevKit provides the following features:

\n\n\n\n\n\n\n\n

Currently, DevKit’s user interface is command line only with plans to add a GUI later this year. It’s available for free and is in open beta for Mac and Linux. Those interested in participating in the open beta can sign up on the DevKit landing page.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jun 2019 20:12:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:83:\"WPTavern: Former npm, Inc. CTO Announces Entropic, a Decentralized Package Registry\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90574\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/former-npm-inc-cto-announces-entropic-a-decentralized-package-registry\";s: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:4561:\"

\n

CJ Silverio, former CTO of npm Inc., gave a presentation at JSConf EU 2019 in Berlin earlier this month titled “The Economics of Open Source.” More specifically, she discussed the economics of package management as it applies to open source software, based on her unique perspective and experience gained in working for the company that runs the world’s largest JavaScript package registry.

\n

Silverio tells the story of how npm gained official status and characterizes its success as a catastrophe for a centralized package registry and repository. Although centralization has some advantages for usability and reliability, success can be expensive when a centralized service becomes popular. She described the events leading up to npm’s incorporation in 2013. The registry was down more than it was up in October 2013 and npm needed money.

\n

npm’s owner took seed funding from a VC firm and the Node project continued to give npm special privileges. Developers perpetuated this by continuing to use npm, as over time it had come to define developers’ expectations in serving JavaScript packages. Silverio discusses some of the consequences of npm coming under private control, how developers now have no input into registry policies or how disputes are resolved.

\n

Presumably speaking from her intimate knowledge of the company’s inner workings, Silverio describes how VC-funding turned npm Inc. into a financial instrument.

\n

“Financial instruments are contracts about money,” she said. “npm Inc, the company that owns our language ecosystem, is a thing that might as well be a collection of pork bellies, as far as its owners are concerned. They make contracts with each other and trade bits of it around. npm Inc. is a means for turning money into more money.”

\n

Silverio contends that JavaScript’s package registry should not be privately controlled and that centralization is a burden that will inevitably lead to private control because the servers cost money.

\n

Her sharp criticism of centralized package management leads into her announcement of a federated, decentralized package registry called Entropic that she created with former npm colleague Chris Dickinson and more than a dozen contributors. The project is Apache 2.0 licensed and its creators are working in cooperation with the OpenJS Foundation.

\n
\n

Warming my heart right now: how many former npm-ers are contributing to entropic <3

\n

— Ceej is on vacation (@ceejbot) June 6, 2019

\n

\n

Entropic comes with its own CLI, and offers a new file-centric publication API. All packages published to the registry are public and developers are encouraged to use something like the GitHub Package Registry if they need to control access to packages. The project is just over a month old and is not ready for use.

\n

“I think it’s right that the pendulum is swinging away from centralization and I want to lend my push to the swing,” Silverio said. The last decade has been about consolidation and monolithic services, but the coming decade is going to be federated. Federation spreads out costs. It spreads out control. It spreads out policy-making. It hands control of your slice of our language ecosystem to you. My hope is that by giving Entropic away, I’ll help us take our language commons back.”

\n

Silverio’s Economics of Package Management essay is available on GitHub. Check out the video of the presentation from JSConf EU below. If decentralized package management gains momentum and becomes the standard for the industry, this video captures what may become a turning point in the JavaScript ecosystem and a defining moment for the future of the web.

\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 11 Jun 2019 03:41:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:70:\"WPTavern: BuddyPress 5.0 to Update Password Control to Match 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=90023\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/buddypress-5-0-to-update-password-control-to-match-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:3462:\"

BuddyPress 5.0 development began in December 2018 after 4.0.0 was released in November. The core BuddyPress team has not published a roadmap for what will be coming in 5.0, but features and fixes added so far can be found on GitHub in the commit log.

\n

One noteworthy addition to the upcoming major release is that the BP Nouveau template pack is being updated to use the same password control as the one used in WordPress core. BuddyPress users will now be able to set their passwords using WordPress’ interface on the registration page and on the user’s general settings page.

\n

Here’s what it will look like in the templates:

\n
\n

Here\'s how it looks \"?\" pic.twitter.com/g8DknNpUKl

\n

— imath (@imath) May 18, 2019

\n

\n

By default, BuddyPress will generate a strong password, but the user can still edit it, if necessary. If the user selects a password that is too weak, the submit button will be disabled until the user confirms they want to proceed by checking the checkbox.

\n

BP Nouveau replaced the bp-legacy template packs in 2018, introducing JavaScript-powered templates, integration with the Customizer, and more layout options for BuddyPress navigation and component directories. As a result of the password control update, the src/bp-templates/bp-nouveau/js/password-verify.js template is scheduled to be deprecated and deleted in BuddyPress 6.0.0, so developers will want to take note if using the bp-nouveau-password-verify script as a dependency for custom password control implementations.

\n

BuddyPress 5.0 also adds BP-specific debug into to the Site Health Info screen that was introduced in WordPress 5.2. This release will require WordPress 4.7 or greater for optimal compatibility and older versions will not be supported. Site owners running on older versions of WordPress have time to prepare.

\n

Although the BuddyPress core team and contributors have put out several security and maintenance releases since version 4.0.0, regular project meetings have been sporadic in 2019. BuddyPress 5.0 was expected at the end of May but a new timeline may be discussed at the next meeting, which is tentatively planned for Wednesday, June 12.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 10 Jun 2019 19:04: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: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:44:\"WPTavern: In Case You Missed It – Issue 25\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90643&preview=true&preview_id=90643\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/in-case-you-missed-it-issue-25\";s: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:7707:\"

photo credit: Night Moves – (license)

\n

There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.

\n

Open Call for People Interested in Being Team Leads

\n

Josepha Haden has published an open call on the Team Updates blog looking for people interested in learning about the Team Lead role. The post includes links to training materials that will be open for two weeks where people can make suggestions.

\n

Once the training materials are complete, interested parties will be sent the team leads training materials and quizzes. Those who pass the quizzes will then be part of a group orientation in which team leads and future leads will be chosen. Even if you’re not interested in becoming a team lead, the training materials in the post contain a lot of useful information about the inner workings of the project.

\n

Marcel Bootsman Continues on After Hospital Visit

\n

Marcel Bootsman who is walking more than 700km to Berlin, Germany for WCEU recently made a hospital visit. “The doctor asked about what I’m doing, and what the problem is, so I explained everything,” Bootsman said. “She examined both legs and found that there was a swelling on my right ankle. She sadly could not diagnose further, since it’s impossible. An expert has to look at it, and an x-ray picture has to be taken.”

\n
\n

YESS! Nothing serious, just an overloaded ankle which is almost healed.
Doctor said I can continue with just one more resting day, so I\'m going by train to my next stop. Just to be of extra help he bandaged my ankle.#WalkToWCEU pic.twitter.com/VdW7C8m71N

\n

— \"??\" Marcel Bootsman (@mbootsman) June 5, 2019

\n

\n

The doctor diagnosed him with having an overloaded right ankle. After wrapping his ankle for extra support, Bootsman continued on. Check out his description and photos from day 19 of his travels.

\n

WooSesh is Coming Back

\n

WooSesh, a global, virtual conference devoted to WooCommerce, is scheduled to take place on October 9-10th. You can follow WooSesh_ on Twitter or sign up to their email list to be notified of when tickets are available.

\n
\n

ANNOUNCEMENT: If you use @WooCommerce to build ecommerce sites, or do any kind of ecommerce development, you\'ll be thrilled to hear that @WooSesh returns on Oct 9 and 10!

\n

Follow @WooSesh_ and join the mailing list at https://t.co/Pyev9v2CPv to stay in the loop pic.twitter.com/hPdv8Yu5LU

\n

— WordSesh (@WordSesh) May 23, 2019

\n

\n

GitHub Repo Templates

\n

Earlier this week, GitHub launched Repository Templates to help developers manage and distribute boilerplate code. Web development agency 10UP has a Theme and Plugin repo template that is available for anyone to use.

\n

WordPress 5.2.2 Release Date Changed

\n

WordPress 5.2.2 was originally scheduled to be released on June 13th, but the release team has decided to push the date back. Tickets that are slated for WordPress 5.3 that meet the requirements to be in a minor release will be merged into 5.2.2. The new release date is Tuesday, June 18th, a few days before WordCamp EU.

\n

WordCamp US After Party Is Now Wordfest

\n

There won’t be a big after party at the conclusion of WordCamp US this year. Instead, organizers are hosting WordFest on Friday, November 1, 2019, at City Museum in St. Louis. According to organizers, the party doesn’t always have to be at the conclusion of the event thus the name change.

\n

How to Use and Create Reusable Block Templates

\n

Justin Tadlock has published a tutorial that explains how to create, use, import, and export reusable block templates in WordPress.

\n

“A lot of this is not intuitive at this point and might take some digging for someone not intimately familiar with all the block editor features. But, this is an extremely powerful feature that I’m sure will become more useful in the future. I can even see things like theme authors sharing reusable blocks to help users build out certain page designs.”

\n

I’m looking forward to seeing other people share their reusable blocks or templates. One of the beautiful things about the new editor is that it doesn’t require a developer to sort blocks into a particular layout and then save it as a reusable block that can be shared.

\n

C02 May Be the Cause of Feeling Drowsy During Conference Sessions

\n

I always thought it had something to do with lunch but I’ve felt drowsy before then. Interesting data shared in a Twitter thread. Hat tip to David Bisset.

\n
\n

Ever wonder why you get so sleepy during conference talks? Turns out lots of conference venues aren\'t well-ventilated, causing CO2 to rise to levels that cause drowsiness (>1000ppm). Data from @keflavich shows this steady rise over the first 50min of a conference session. pic.twitter.com/AjFO2eQDrJ

\n

— Cara Battersby (@battersbot) June 4, 2019

\n

\n

That’s it for issue twenty-five. If you recently discovered a cool resource or post related to WordPress, please share it with us in the comments.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jun 2019 21:33:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:14;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"WPTavern: Experimenting With Reusable Blocks to Create Post Templates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90636\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wptavern.com/experimenting-with-reusable-blocks-to-create-post-templates\";s: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:2177:\"

For the past several years, I’ve used the Post Template plugin developed by Vincent Prat to create and manage post templates. For example, some of the information in the WordPress Weekly and In Case You Missed It posts never changes and instead of manually entering it each time, it’s nice to use a template where only a few changes are necessary.

\n\n\n\n

The other day, I was wondering if I could use the reusable block feature in Gutenberg to replace the plugin. Justin Tadlock reached out and provided me a reusable block template JSON file that I imported into Gutenberg. By the way, if you successfully import a block into WordPress, the block won’t appear until you manually refresh the page.

\n\n\n\n

The reusable block template approach works fairly well. However, I noticed that I was unable to add a block inside the reusable block. When I tried, a red line was displayed and any blocks that were inserted were removed.

\n\n\n\n
Red Means No
\n\n\n\n

I understand that reusable blocks are meant to be restricted templates where changes are distributed across a site to wherever the block is displayed. But it’s still a bummer that I can’t add a block inside the template for a singular purpose if a need arises.

\n\n\n\n

One other thing I noticed is that reusable blocks are custom post types. While there is a link to manage them within the reusable block selector, there isn’t a dedicated item within the admin menu. Unless you know the location of the management link, adding and managing them can be a bit more time-consuming.

\n\n\n\n

If you want a quick shortcut to the reusable block management screen, add this to the URL after your domain name. wp-admin/edit.php?post_type=wp_block

\n\n\n\n

I think I’ll experiment with reusable blocks a bit more but as long as they’re not changing often, I believe they’ll make a nice replacement for the Post Templates plugin. What use cases have you encountered where reusable blocks were the solution?

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Jun 2019 02:13:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:15;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"WPTavern: Branch Continuous Integration Service Selected for TinySeed Startup Accelerator\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90611\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:100:\"https://wptavern.com/branch-continuous-integration-service-selected-for-tinyseed-startup-accelerator\";s: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:4298:\"

Branch, a Docker-based continuous integration service for WordPress, has been selected for TinySeed’s startup accelerator. The company was founded by Peter Suhm who is also the creator of WP Pusher, a plugin that lets developers install and update WordPress themes and plugins directly from GitHub, Bitbucket, and GitLab.

\n

TinySeed, founded by Rob Walling and Einar Vollset, is a remote accelerator that focuses on providing enough funding for early-stage SaaS founders to live for a year and focus full-time on their startups. It advertises itself as “the first startup accelerator designed for bootstrappers.” TinySeed is unique in that it does not have a bias against single founders. The website states that the majority of successful $1m-$30m SaaS companies that TinySeed is connected with were started by founders working alone.

\n

Branch fits the bill as a SaaS company with a single founder and no employees. As part of the investment terms, TinySeed invests $120k for the first founder (plus $20k per additional founder) in exchange for 8-15% equity. If founders do not need the money for living expenses they are free to spend it on growing the business. Both Branch and WP Pusher are included in Suhm’s participation in TinySeed.

\n

“WP Pusher was doing just enough to pay my bills living in a fairly cheap city (Glasgow), but not enough to pay a full time developer salary,” Suhm said. “However, I didn’t spend much time on WP Pusher in the past few years and was working part time for other companies – mainly Timekit as a backend developer.”

\n

Suhm said the TinySeed investment will allow him to work full time on Branch and WP Pusher for at least a year or two without having to worry about making a salary.

\n

“I may also decide to make a hire during the program, but I want the product to be a little bit more mature,” he said. “In terms of the roadmap, I’ll be able to focus more on building the best tool and less about making a lot of money in the beginning.”

\n

Branch and WP Pusher are fairly unique products in the WordPress space. Suhm said he sees most of his competition coming from continuous integration services that are not tailored to WordPress.

\n

“However, my biggest competitor at the moment is probably manual labor – WordPress developers testing and deploying everything manually,” Suhm said.

\n

TinySeed received approximately 900 applications from which they will select 10-15 companies for participation in 2019. Co-founder Rob Walling has knowledge of the WordPress ecosystem, as he previously invested in WP Engine’s 2011 round of funding.

\n

“Peter has a distinct advantage with Branch in that he’s building on the audience, customer base, and domain knowledge he’s developed with WP Pusher,” TinySeed co-founder Rob Walling said. “His methodical approach to shipping code and content every week has been a good signal for us that he’s pushing the product forward, as well as a key factor in building Branch’s traction in the space.”

\n

Branch is joining a handful of other SaaS companies that have already been selected for 2019, including ClientSherpa, Gather, SimSaaS, Reimbi, and Castos.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jun 2019 20:31: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: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:49:\"WPTavern: Automattic Adopts Alex Mills’ 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90583\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/automattic-adopts-alex-mills-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:4656:\"

Automattic announced today that a team inside the company will be adopting Alex Mills‘ plugins and continuing their development and support. Mills, also known around the web as @Viper007Bond, was a WordPress core contributor and prolific plugin developer who passed away in February 2019 after a battle with Leukemia.

\n

At one time last year, Mills was the primary author for and contributor to more than 40 plugins hosted on WordPress.org. The current collection seems to have been pared back to 17 of his most popular plugins. According to stats from WP Tally, these 17 plugins have a cumulative download count of 138,665,603 and a cumulative rating of 4.55 out of 5 stars.

\n

“Since all of my plugins are open-source, they are free to be forked by reputable authors in the WordPress community. It would mean a lot to have my legacy go on,” Mills said in his farewell post earlier this year. The plugins are all free without any pro versions or monetization efforts attached to them.

\n

“I’d never monetize any of my plugins,” Mills told the Tavern after his popular Regenerate Thumbnails plugin passed 5 million downloads in 2017. “I write them for fun not profit. It would be a conflict of interest anyway due to my employment at Automattic.”

\n

Regenerate Thumbnails is active on more than a million WordPress sites and passed the 10 million downloads milestone in January 2019. It has already been downloaded more than 7,000 times today and has regularly received 3K-12k downloads per day throughout 2019.

\n

The enduring popularity of Regenerate Thumbnails is a testament to Mills’ commitment to writing future-proof plugins. What started as a small plugin to fix a client’s problem in 2008 quickly became an indispensable utility for millions of WordPress users transitioning between themes with different image sizes. For those users who could never write their own script to generate new thumbnail sizes, Mills’ plugin was a little piece of time-saving magic that exemplifies the significant contributions plugin developers can make when they write and share code that solves a common problem.

\n

Automattic plans to fork each of Mills’ GitHub repositories and will add them to the Automattic Github account. The team behind this effort is also adding the following paragraph to each plugin’s readme file:

\n

In February 2019 Alex Mills, the author of this plugin, passed away. He leaves behind a number of plugins which will be maintained by Automattic and members of the WordPress community. If this plugin is useful to you please consider donating to the Oregon Health and Science University.

\n

Automattic will also be answering support queries on the forums and the team is open to receiving help from other members of the WordPress community in maintaining and supporting Mills’ plugins.

\n

“In times gone by authors left works of music, novels, poetry, and letters on their passing,” Donncha Ó Caoimh said on the Automattic Engineering blog. “They were static works of art frozen in time. Alex leaves behind his code that will continue to evolve and operate in a living world used by thousands (millions?) of people every day as they go about their online lives.”

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jun 2019 16:51:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:17;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:60:\"WPTavern: WPWeekly Episode 355 – Food Poisoning Is No Joke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90569&preview=true&preview_id=90569\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wptavern.com/wpweekly-episode-355-food-poisoning-is-no-joke\";s: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:1676:\"

In this episode, John James Jacoby and I discuss Joost de Valk’s decision to step down as WordPress’ Marketing Lead. I shared my recent encounter with food poisoning and some of the lifestyle changes I’m making to improve my health. We also talk about a new experimental plugin by Automattic that aims to provide full site editing and FreeCodeCamp’s decision to migrate away from Medium to Ghost.

\n

Stories Discussed:

\n

Joost de Valk Steps Down as WordPress Marketing Lead

\n

FreeCodeCamp Moves Off of Medium after being Pressured to Put Articles Behind Paywalls

\n

Automattic is Testing an Experimental Full Site Editing Plugin

\n

WPWeekly Meta:

\n

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

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #355:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Jun 2019 01:10:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:82:\"WPTavern: Google Adds New Desktop/Mobile Selector to the Rich Results Testing Tool\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90532\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/google-adds-new-desktop-mobile-selector-to-the-rich-results-testing-tool\";s: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:3254:\"

Google’s rich results testing tool has been updated to include a selector for desktop or mobile so website owners can check their results on both platforms. This tool shows if pages are properly structured for display in Google’s carousels, images, breadcrumbs, events, books, and other types of rich snippets. A glossary is available with images showing what each type of result looks like with the proper structured data in place.

\n

\n

Last week Google announced that it will begin enabling mobile-first indexing (crawling sites with a mobile user-agent) by default for new domains on July 1, 2019. Site owners can select “Googlebot Smartphone” as the user-agent on the rich results testing tool to see if their sites are prepared for mobile-first indexing. The tool is still in beta, so not all rich results and error types are supported yet.

\n

If your page supports rich results, you will see a confirmation and can click through to view the HTML. Certain rich result types will display a preview of how the result might appear in Google Search. If multiple result layouts are available, the tool will also let you drill down into the different layouts for both desktop and mobile.

\n

\n

If you get a result that says “Page not eligible for rich results known by this test” when you know that you have the structured data in place, it could be because the beta version of this tool only supports a subset of rich result types. These currently include job postings, recipes, courses, TV and movie, events, and Q&A pages.

\n

You can also test your page using this tool by putting in a code snippet, in case your content is not publicly accessible or is restricted behind authorization.

\n

Depending on your specific requirements, there are many different WordPress plugins that properly structure data to improve how your content appears in rich results around the web, such as Schema, All In One Schema Rich Snippets, Schema App Structured Data, Rank Math, and Yoast SEO, to name a handful of popular options.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jun 2019 19:57: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: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:62:\"WPTavern: Joost de Valk Steps Down as WordPress Marketing Lead\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90542\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/joost-de-valk-steps-down-as-wordpress-marketing-lead\";s: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:2397:\"

Joost de Valk has announced that he’s stepped down from the WordPress Marketing and Communications Lead role. The position was created and awarded to de Valk earlier this year. Not only was it a new position, but it also expanded the leadership roles in the WordPress project.

\n\n\n\n

Despite making progress, de Valk didn’t feel as though he was fulfilling the leadership aspect of his role. “My experience over the last few months made me feel that while I was doing things and getting things done, I certainly wasn’t leadership. I don’t want to pretend I have a say in things I don’t have a say in,” he said.

\n\n\n\n

Not having a clear definition of what marketing means and having people within the project on the same page contributed to his decision.

\n\n\n\n

“There’s a stark difference between where I thought I would be in the organization in this role, and where I am actually finding myself now,” de Valk said.

\n\n\n\n

“Even things that every outsider would consider marketing (release posts, about pages) are created without even so much as talking to me or others in the marketing team. Because I felt left out of all these decisions, I feel I can’t be a marketing lead.”

\n\n\n\n

He also cited a lack of clarity surrounding his position, “I’ve been asked dozens of times on Twitter, Facebook and at WordCamps why I now work for Automattic, which of course I don’t but that is the perception for a lot of people,” he said. “On other occasions, I seem to be the token non-Automattician, which I’m also uncomfortable with.”

\n\n\n\n

Due to taking a toll from failing to fulfill the position, de Valk plans to take an extended vacation during the Summer and when he returns, focus 100% of his efforts on Yoast and his Chief Product Officer role.

\n\n\n\n

Matt Mullenweg commented on de Valk’s article thanking him for being willing to try new things and for his passion, impatience, and drive to improve 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Jun 2019 17:57:05 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"WPTavern: Take Back Your Web: Tantek Çelik’s Call to Action to Join the Independent Web\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90416\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/take-back-your-web-tantek-celiks-call-to-action-to-join-the-independent-web\";s: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:4246:\"

Tantek Çelik, Web Standards Lead at Mozilla and co-founder of IndieWebCamp, delivered an inspirational talk titled “Take Back Your Web” at the most recent beyond tellerrand conference in Düsseldorf, Germany. He opened the presentation with a litany of Facebook’s wrongdoings, taking the world’s largest social network to task for its role in increasing polarization, amplifying rage, and spreading conspiracy theories.

\n

Çelik challenged the audience to “stop scrolling Facebook,” because its algorithms are designed to manipulate users’ emotions and behaviors. He noted that it is the only social network with a Wikipedia page dedicated to its criticism. This massive document has a dizzying number of references, which Wikipedia says “may be too long to read and navigate comfortably.” As an alternative to scrolling Facebook, Celik encouraged attendees to spend time doing nothing, an activity that can be uncomfortable yet productive.

\n

The “Take Back Your Web” presentation is a call to action to join the independent web by owning your own domain, content, social connections, and reading experience. Celik recommends a number of IndieWeb services and tools to empower users to take control of their experiences on the web.

\n

With a free site hosted on GitHub, he said the costs of owning your own domain are less than owning a phone or having internet service. Suggestions like this are targeted at developers who share Twitter names instead of domains and post articles on Medium. Setting up a site on GitHub is not a simple task for most. That’s why networks like WordPress.com, along with hosts that provide instant WordPress sites, are so important for enabling average internet users to create their own websites.

\n

Celik referenced Matthias Ott’s recent article “Into the Personal-Website-Verse,” highlighting the section about the value of learning new technologies by implementing them on your own website: “A personal website is also a powerful playground to tinker with new technologies and discover your powers.” It’s one of the few places developers can expand their skills and make mistakes without the pressure to have everything working. Ott enumerates the many benefits of people having their own enduring home on the web and encourages developers to use their powers to make this a reality:

\n

As idealistic as this vision of the Web might seem these days, it isn’t that far out of reach. Much of what’s needed, especially the publishing part, is already there. It’s also not as if our sites weren’t already connected in one way or another. Yet much of the discussions and establishment of connections, of that social glue that holds our community together – besides community events in real life, of course –, mostly happens on social media platforms at the moment. But: this is a choice. If we would make the conscious decision to find better ways to connect our personal sites and to enable more social interaction again, and if we would then persistently work on this idea, then we could, bit by bit, influence the development of Web technologies into this direction. What we would end up with is not only a bunch of personal websites but a whole interconnected personal-website-verse.

\n

Check out Çelik’s slides for the presentation and the recording below for a little bit of inspiration to re-evaluate your relationship with social networks, create your own site, or revive one that has been neglected.

\n
\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 04 Jun 2019 21:50: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: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:93:\"WPTavern: Jetpack 7.4 Adds Business Hours Block and Ability to Share Content Through WhatsApp\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90503\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/jetpack-7-4-adds-business-hours-block-and-ability-to-share-content-through-whatsapp\";s: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:2229:\"

Jetpack 7.4 is now available and includes a new Business Hours block. This block contains a toggle that users can set to show whether they’re open or closed.

\n\n\n\n

There’s also a way to add additional times so restaurants, for example, can display when they’re open for breakfast, lunch, and dinner. However, I couldn’t figure out a way to add text to label what the hours mean. Also, depending on the theme, the alignment displays incorrectly. You can see the block in action below.

\n\n\n
Sunday
Closed
Monday
9:00 AM – 1:00 PM
5:00 PM – 10:00 PM
Tuesday
9:00 AM – 5:00 PM
Wednesday
9:00 AM – 5:00 PM
Thursday
9:00 AM – 5:00 PM
Friday
9:00 AM – 5:00 PM
Saturday
Closed
\n\n\n

The Slideshow, Carousel, and Tiled Galleries blocks have all received enhancements to improve their look and performance on mobile devices. The Carousel block also contains better theme compatibility.

\n\n\n\n

WhatsApp is now included in the Jetpack Sharing module. Users can enable it by browsing to Jetpack > Settings > Sharing > Configure sharing buttons. The button supports sharing content through the stand-alone app and the web interface.

\n\n\n\n

Jetpack 7.4 also makes a number of enhancements to the Recurring Payments block such as improving the display of the renewal frequency in the button list and improving the look of the payment modal on mobile devices. This version also requires users to be on the Premium or Professional plan on WordPress.com in order to access the button.

\n\n\n\n

You can see a full list of changes in 7.4 by viewing the changelog.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 04 Jun 2019 20:19: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: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:52:\"WordPress.org blog: The Month in WordPress: May 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6987\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/06/the-month-in-wordpress-may-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6614:\"

This month saw the 16th anniversary since the launch of the first release of WordPress. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a significant global event.

\n\n\n\n
\n\n\n\n

Release of WordPress 5.2

\n\n\n\n

WordPress 5.2 “Jaco” was released on May 7 shipping some useful site management tools, such as the Site Health Check and PHP Error Protection, as well as a number of accessibility, privacy, and developer updates. You can read the field guide for this release for more detailed information about what was included and how it all works.

\n\n\n\n

327 individual volunteers contributed to the release. If you would like to be a part of that number for future releases, follow the Core team blog and join the #core channel in the Making WordPress Slack group.

\n\n\n\n

A Successful WordPress Translation Day 4

\n\n\n\n

WordPress Translation Day is a 24-hour event organised by the Polyglots team where community members from all over the world come together to translate WordPress into their local languages. For the fourth edition held on 11 May, 183 brand new contributors joined the Polyglots team from 77 communities across 35 countries in Africa, Asia, Europe, North America, South America, and Oceania.

\n\n\n\n

While the WP Translation Day is a great time for focussed contributions to localizing WordPress, but these contributions can happen at any time of the year, so if you would like to help make WordPress available in your local language, follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.

\n\n\n\n

Updated Plugin Guidelines Proposal

\n\n\n\n

The Plugins team has proposed some updates to the guidelines for developers on the Plugin Directory. The majority of the proposed changes are intended to address significant issues faced by developers who do not speak English as a first language, making the Plugin DIrectory a more accessible and beneficial place for everyone.

\n\n\n\n

The proposal will be open for comments until late June, so the community is encouraged to get involved with commenting on them and the direction they will take the Plugin Directory. If you would like to be involved in this discussion, comment on the proposal and join the #plugin review team in the Making WordPress Slack group.

\n\n\n\n

Continued Gutenberg Development

\n\n\n\n

Since the block editor was first released as part of WordPress Core in v5.0, development has continued in leaps and bounds with a new release every two weeks. The latest update includes some great incremental improvements that will be merged into the 5.2.2 release of WordPress along with the other recent enhancements.

\n\n\n\n

In addition to the editor enhancements, work has been ongoing in the Gutenberg project to bring the block editing experience to the rest of the WordPress dashboard. This second phase of the project has been going well and the latest update shows how much work has been done so far.

\n\n\n\n

In addition to that, the Block Library project that aims to bring a searchable library of available blocks right into the editor is deep in the planning phase with a recent update showing what direction the team is taking things.

\n\n\n\n

If you would like to get involved in planning and development of Gutenberg and the block editor, follow the Core and Design team blogs and join the #core, #design, and #core-editor channels in the Making WordPress Slack group.

\n\n\n\n
\n\n\n\n

Further Reading:

\n\n\n\n\n\n\n\n

Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Jun 2019 10:21: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: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: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:75:\"WPTavern: Gutenberg Team is Exploring Adding Motion to Block Moving Actions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90465\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://wptavern.com/gutenberg-team-is-exploring-adding-motion-to-block-moving-actions\";s: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:4221:\"

In a post titled “Using Motion to Express Change,” Gutenberg designer and engineer Matías Ventura takes a deep dive into how animation can be applied to interfaces to replicate realistic motion. These animations can sometimes more clearly communicate changes, particularly in relationship to the action of moving or reordering items on a page.

\n

“Even though the instant transformation of the interface is accurate it may not be the clearest expression of the change that just occurred,” Ventura said. “The relationship between intention and effect might become harder to grasp. Motion can be a great aid in communicating relationships and clarifying the changes experienced in a more intuitive way.”

\n

This creates an interesting choice for an interface designer. Although instantaneous changes are possible to implement, they may require more time for the user’s brain to process. In the case of an editor, any added cognitive processing can pull a user out of the flow of writing. Ventura sets a good practical rule of thumb for determining if an animation adds value to an interaction:

\n

One could say that an animation is worth being present if the clarity of change it provides is greater than the time it would take to adjust cognitively to the new state in its absence.

\n

Ventura illustrates this concept with two video demos in his post – one showing how block reordering currently looks in WordPress’ editor and a second with an example of how it could be improved with subtle, tasteful animations. It’s an early prototype but very convincing:

\n

\n

When Gutenberg was still in the selling phase before being merged into core, some said that moving forward was simply a matter of retraining your muscle memory to work with the new editor. However, at that time there were still a number of markedly flawed interactions that didn’t feel natural and were even jarring for the user. The legacy editor didn’t have blocks to reorder or many of the other interactions introduced by the new block paradigm, so there wasn’t much prior context for comparison.

\n

User reviews have complained about the cognitive load that Gutenberg adds and have continued to identify problematic interactions with the core blocks. Unfortunately, in many heated exchanges that took place in comments and discussions prior to WordPress 5.0’s release, these concerns were often brushed aside as coming from people who were resistant to change.

\n

Many of the reviewers may not have had the right words to communicate what it was they were experiencing, but the cognitive load may be one of the strongest reasons why the Classic Editor plugin has more than 5 million active installs.

\n

Matías Ventura’s proposal to add motion to express change in the editor has the potential to solve some of these unintuitive interactions. The Gutenberg repository now has an issue dedicated to exploring and discussing the use of motion to add clarity to the action of reordering blocks.

\n

Ventura’s post is an encouraging read that demonstrates the thought and craftsmanship that go into architecting an interface that is required to meet the needs of millions of users. If you have been impatient with Gutenberg’s progress, as I have been, it’s important to recognize that these kinds of refinements to interactions take time to percolate. Replicating realistic motion comes from contemplating how we interact with the known world and understanding how that informs users’ digital expectations.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 04 Jun 2019 04: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:24;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:55:\"HeroPress: Ugyen’s Roadmap to WordPress Contributions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=2848\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:156:\"https://heropress.com/essays/ugyens-roadmap-to-wordpress-contributions/#utm_source=rss&utm_medium=rss&utm_campaign=ugyens-roadmap-to-wordpress-contributions\";s: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:44456:\"\"Pull

འབྲི་རྩོམ་འདི་རྫོང་ཁ་ན་ལུ་ཡ་ཡོདཔ་ཨིན།

\n

Ugyen Dorji is from Bhutan, the landlocked country situated between two giant neighbors, India to the south and China to the north. Ugyen works for ServMask Inc and is responsible for the robust Quality Assurance process for All-in-One WP Migration plugin. He believes in the Buddhist teaching that “the most valuable service is one rendered to our fellow humans” and his work ethic shows with managing WordPress translation projects for his Plugin ’All-in-One WP Migration.’  Ugyen also keeps multi-language support for WordPress; furthermore the plugin is now translated into 42 languages with more on the way.

\n

How Ugyen started his career with WordPress

\n

Life is a struggle – it is a mixture of success and failure which can come in any venture and that too late and sometimes most unexpectedly people lose heart after a failure; but a person who takes failure in his/her stride and continues his effort for success in long run in the word of EL Kerten means “The secret of success is knowing whom to blame for your failure.”

\n

Back in 2016, he had been looking for new working place after his former cloud company got shattered with some financial crisis, he has looked for a new job. For which he has tried his best and one fine day he makes it to an interview – where he has been triggered with WordPress questionnaires. On that moment he has no proper answer for interviewers saying big number to interviewers, though he has basic knowledge about WordPress. After that day, just sat in his room with silence and made up his mind to learn and get skilled himself with WordPress wisdom,  watching cities from his window receiving cool air, and said himself

\n

“I will make my career with WordPress and it will be my bread and butter”.

\n

After a few months, he received a call from ServMask Inc, who developed a great plugin called   “All-in-One WP Migration” which made his dream come true like an angle ServMask Inc blessed his dream to make his living with WordPress. Ugyen is now an active contributor to the WordPress Community.

\n

Ugyen’s First WordCamp Experience

\n

WordCamp is a genuine spotlight for plugin and theme developers to reach WordPress users and website developers. It’s a glorious atmosphere where many incredible talks about WordPress take place. The “tribe” meetings are a phenomenal moment for aspiring computer engineers, content writers and developers to showcase their talent and meet each other.

\n

WordCamp Bangkok 2018 was an essential day for Ugyen and ServMask because their sponsorship of the event delivered them the opportunity to connect with our active WordPress users and showcase their appreciation on better quality of WordPress plugin.

\n

Contributor Day

\n

The first day of WordCamp is Contributor Day. Ugyen associated with a community team and got to share a conversation with WordPress folks from all over the world. Community communication is the ground root of WordCamp and WordPress meetups, giving him all the chance to share and manifest what WordPress does and  how it is used. He also addressed encouraging more speakers and WordPress members to nurture their experience and whereby he could support new organizers to continue and contribute to building the WordPress community in places where it is not yet booming.

\n

Conference Day

\n

Conference Day is the main event of WordCamp and is held on the second day. Ugyen was taking care of a Photo Booth for people to snap their memories. I think this was a great idea to capture the memories of WordCamp for attendees, speakers, and organizers.

\n

The foremost intention of the conference day is the presentations that take place throughout the day. Ugyen had a great moment to attend various talks which were very beneficial for developers, entrepreneurs, firms, and young startups firms. What holds in Ugyen’s mind is a plan that exhibits leveraging website content has been shown to lead to 100% growth in business extension.

\n

How Ugyen became WordPress Meetup Thimphu Co-Organizer

\n

Following October 2016, Ugyen came over about WordPress Meetup Bangkok and WordCamp Bangkok 2018. From that onwards, the importance of WordPress Meetup catches on his mind to introduce WordPress to his home country and cities. The foremost incidence that clicks on his mind was on WordPress Translation Day 3 on September 30, 2017, during WordPress Meetup Bangkok where he has seen his locale Dzongkha was in lowest percentage comparing to another locale status on WordPress Core Translation. Later in WordCamp Bangkok 2018 Contributors day when he met with WordPress Folks and WordPress Community, Meetup Organizer from many countries.

\n

WordPress Meetup Thimphu is an easygoing, volunteer-organized, non-profit meetup covering everything related to WordPress and keeping our Bhutanese Gross National Happiness four pillars in mind with aims to preserve and promote our unique culture and national language. WordPress Meetup implies for individuals and all people who love WordPress and want to contribute and share their knowledge and have experience in meeting new faces and for networking. Ugyen’s Specific focus on encouraging local and international language WordPress bloggers and help startup companies to grow their assets with WordPress and share what he has learned from WordPress with his Bhutanese WordPress community.

\n

Ugyen’s First WordPress Meetup Thimphu was a huge success within his community coinciding with WordPress Main event WordPress Translation Day 4.  Ugyen would take a more vital role in preserving his national language by making use of WordPress actively by our Dzongkha bloggers, online Dzongkha news, government websites so that Bhutanese WordPress core contributors could hand over to our next generation very proudly.

\n

What we have achieved :

\n
    \n
  1. Done WordPress Core Translation for our locale Dzongkha.
  2. \n
  3. New Translation Contributor for our WordPress Core Translation for Dzongkha.
  4. \n
  5. Participated in Global WordPress Translation Day 4 Livestream.
  6. \n
  7. Invited WordPress Experts from other countries to http://wpbhutan.slack.com.
  8. \n
  9. Invited WordPress Meetup Thimphu members to http://wpbhutan.slack.com to discuss more on WordPress related topics and for helpline on WordPress for Bhutanese WordPress users and wordpress.org login for new users.
  10. \n
  11. Speaker of the event Tenzin Namgyel Senior ICT officer from DDC WordPress Local Manager and General Translation Editor for our locale Dzongkha.
  12. \n
  13. Good meal and tea with great place to host at Ariya Hotel
  14. \n
  15. Introduction of a member for networking.
  16. \n
  17. Became a part of Global WordPress Translation Day 4 team.
  18. \n
  19. Event Sponsored by ServMask Inc and Helped by Dzongkha Development Commission with Language Experts.
  20. \n
\n

WordPress Future Road Plans

\n

“The best preparation for tomorrow is to do today’s work superbly well” so that we can put all our effort, then we’ll see a very good result and success will surely be yours. No men can hope to have a very successful life but there will be one or two in exception in this earthly world in thousand cases of this matter which results strong determination can help to attain success. Therefore with Ugyen’s determination here are some of his road plans for WordPress.

\n

For WordPress Meetup: Ugyen’s next plan is to visit the language universities and teach them to blog in Dzongkha using WordPress. He said, “ We have plans to gather a group of active Bhutanese WordPress Bloggers and host panel talks to extend the beauty of Bhutan and unique culture of Bhutan to outside nations. And also one of the WordPress Main Events: Introduction to Open Source is in a process to be host soon. His Majesty the fourth King of Bhutan once said, “the future of our nation lies in the hands of our children.” Therefore Ugyen works to focus more on youth to enhance their WordPress Skills.

\n

For WordCamp: WordCamp Thimphu is my goal – to reach and invite more WordPress Experts as speakers of the main event and support Bhutanese to grow their career with WordPress. WordCamp Asia is in the process to kick start in 2020 and become one of the WordCamp Co-organizer among 41 WordCamp Asia Co-Organizers.

\n

To WordPress lovers – “If you want to be successful the ball is in your court, you think to throw a ball outside or smash the ball or play the game nicely and win the game’’

\n

ཚིག་གསར་དཔེ་སྐྲུན་ལས་ཁང་ལུ་རྒྱབ་སྐྱོར་གྱི་དོན་ལུ་ ཨོ་རྒྱན་གྱི་ལམ་ཡིག

\n

ཨོ་རྒྱན་རྡོ་རྗེ་གི་སྐྱེ་སའི་ཕ་ཡུལ་ནི་འབྲུག་རྒྱལ་ཁབབ་ཨིན། འབྲུག་རྒྱལ་ཁབ་འདི་ཁྱིམ་ཚང་རྒྱལ་ཁབ་ རྒྱ་དང་བོད་ཀྱི་བར་ན་ ཕྱི་ཡི་ལྕགས་རི་མཚུངས་པའི་ གང་རི་ཚུ་གི་བསྐོར་ཏེ་ ཡོདཔ་ཨིན། ཨོ་རྒྱན་གྱི་ ལཱ་འབད་ས་འདི་ ServMask Inc ནང་འབད་དོ་ཨིནམ་ད་ ཁོ་གི་ལཱ་འགན་ངོ་མ་འདི་ WordPress གི་ས་གནས་གཞན་ཁར་སྤོ་འགྱོ་ནིའི་ལས་རིམ་ཚུ་ པུས་ཚད་སྒྲིང་སྒྲིང་བཟོ་ནི་ལུ་ ཡིད་ཆེས་བསྐྱེད་བཅུག་ནི་འདི་ཨིན།

\n

ཁོ་ནང་པ་སངས་རྒྱས་ཀྱི་ཆོས་ལུགས་ལུ་ཡང་ སྙིང་ཐག་པའི་གཏིང་ལས་ ཡིད་ཆེས་ཡོད་མི་ཅིག་ཨིན་པའི་ཆ་གནས་ལས་ ཁོ་གིས་ལཱ་འབད་ཐངས་ཡང་ ཚིག་གསར་དཔེ་སྐྲུན་ལས་ཁང་གི་ སྐད་སྒྱུར་ལས་འཆར་གྱི་ འཛིན་སྐྱོང་འཐབ་ནི་འདི་ཨིན་མས། འདི་མ་ཚད་ ཁོ་གི་ WordPress གི་དོན་ལུ་ སྐད་ཡིག་སྣ་མང་གི་ རྒྱབ་སྐྱོར་ཚུ་འབད་དོ་ཡོདཔ་མ་ཚད་ ད་ཚུན་གྱི་རིང་  All-in-One WP Migration plugin འདི་སྐད་ཡིག་མ་འདྲཝ་༤༢་༢དེ་ཅིག་ནང་ སྐད་སྒྱུར་འབད་དེ་ཡོདཔ་ཨིན།

\n

ཨོ་རྒྱན་གྱི་ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་དང་མཉམ་གཡོག་གི་མདུན་ལས་ག་དེ་སྦེ་འགོ་བཙུགས་ཡི་ག་གི་སྐོར།

\n

ང་བཅས་རའི་མི་ཚེ་གི་ལམ་འདི་ གདོང་ལེན་དྲག་པོ་ཅིག་ཨིན། མི་ཚེ་འདི་ནང་ལཱ་དང་བྱ་བ་ག་ཅི་ར་འབད་རུང་ མཐར་འཁྱོལ་ནི་དང་འཐུས་ཤོར་ནི་འདི་ རང་བཞིན་ཅིག་ཨིན། ཨིན་རུང་མི་མང་ཤོས་ཅིག་གི་ར་ ལཱ་འདི་རང་གི་མནོ་བཞིན་བསམ་བཞིན་འགྱོ་མ་བཏུབ་པའི་བསྒང་ལས་ བློ་ཕམ་སི་སི་སྦེ་ ཚར་ཅིག་གུ་མནོ་བསམ་ག་ནི་ཡང་མ་གཏང་པར་ གདོང་ལེན་ཅན་གྱི་མི་ཚེ་འདི་ལུ་ གདོང་ལེན་འབད་མ་ཚུགས་པར་ རྒྱབ་ཤུད་རྐྱབ་སྡོདཔ་མས། རང་གི་མི་ཚེ་ནང་ཚགས་ཁ་མ་ཚུད་པའི་འཐུས་ཤོར་འབྱུང་རུང་ འདི་ལས་ཡོན་ཏན་ལེན་སྟེ་ མི་ཚེ་འདི་ནང་མཐར་འཁྱོལ་ནི་ལུ་གཙོ་བོ་བཏོན་ནི་བཀོ་མ་བཞག་པར་ འཕྲོ་མཐུད་དེ་ར་བརྩོན་འགྲུས་བསྐྱེད་དེ་ལཱ་འབད་མི་ མི་འདི་གིས་ མི་ཚེ་ནང་འབྲས་བུ་ལེགས་ཤོམ་འབག་ནི་ཡོདཔ་ཨིན། མཁས་དབང་ཨིལ་ཀར་ཊྲན་གྱི་ཡང་ མི་ཚེ་ནང་མཐར་མཁྱོལ་ནི་དོན་ལུ་གསང་བ་ངོ་མ་འདི་ར་ འཐུས་ཤོར་བའི་གནད་དོན་འདི་ལུ་རྫུན་ཁ་བཀལ་ཤེས་ནི་འདི་ཨིན་ ཟེར་གསུངས་ནུག དེ་བཟུམ་སྦེ་ར་ ཨོ་རྒྱན་ཡང་ཧེ་མ་ དབྱིན་ལོ་༢༠༡༦་ལུ་ཁོ་རའི་ལཱ་འབད་སའི་ ཀལཝཏ་ཚོང་སྡེ་འདི་དངུལ་འབྲེལ་གྱི་དཀའ་ངལ་ཅིག་འཐོན་སྟེ་ སྒོ་བསྡམ་པའི་ཤུལ་ལུ་ ཁོ་ཡང་ལཱ་གཡོག་གསརཔ་ཅིག་ནང་འཛུལ་ཞུགས་འབད་ནིའི་དོན་ལུ་ གཡོག་གི་ས་གོ་ཅིག་འཚོལ་སྟེ་ར་སྡོད་པའི་ཤུལ་ལུ་ ཉིནམ་ཅིག་འབདཝ་ད་ ཚིག་གསར་དཔེར་སྐྲུན་ལས་ཁང་དང་མཉམ་ གཡོག་གི་དོན་ལུ་དྲི་བ་དྲི་ལན་འབད་ནིའི་གོ་སྐབས་ཅིག་ཐོབ་ནུག རེ་འདོད་ཅན་གྱི་ཉིནམ་འདི་ལས་འགོ་བཟུང་ ཁོགི་སེམས་ཁར་ ཁོ་རའི་མི་ཚེ་འཚོ་ཐབས་ཀྱི་དོན་ལུ་ ཡུན་དུ་གནས་པའི་འོང་འབབ་ཀྱི་གཞི་གཙོ་བོ་འདི་ ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་ར་ཨིན་ཟེར་མནོ་ནུག ཟླཝ་དག་པ་ཅིག་གི་ཤུལ་ལས་ འཛམ་གླིང་ནང་གཞན་དང་མ་འདྲ་བའི་ལས་འགུལ་ ‘ག་ར་མཉམ་གཅིག་འཛོམས་ཚུགས་པའི་ ཚིག་གསར་དཔར་སྐྲུན་ལས་ཁང་གི་ ས་གནས་སྤོ་བ་’ ཟེར་མི་གསར་བཟོ་ཚོང་སྡེ་ནང་ལས་ ServMask གིས་འགྲུལ་འཕྲིན་ལྷོད་དེ་ ཁོ་བཙག་འཐུ་བསྒྲུབ་པའི་གནས་ཚུལ་གོཝ་ད་ ཁོ་གིས་ཁོ་རའི་རེ་བ་བསྐྱེད་མི་ རེ་འདོད་འདི་དངོས་སུ་སྦེ་འགྲུབ་པའི་དགའ་བ་ཚད་མེདཔ་སྦེ་འབྱུང་ནུག འདི་འབདཝ་ལས་བརྟེན་ ད་རིས་ཨོ་རྒྱན་ཡང་ ཚིག་གསར་དཔེར་སྐྲུན་ལས་ཁང་གི་དོན་ལུ་ འཇོན་ཐངས་ཅན་གྱི་ལས་གཡོགཔ་ཅིག་ཨིན་མས།

\n

ལྟ་བ་མཐུན་པའི་གནས་ཚུལ་སྡེ་ཚན་ནང་ཨོ་རྒྱན་གྱི་ཉམས་མྱོང་འགོ་དང་པ།

\n

ལྟ་བ་མཐུན་པའི་གནས་ཚུལ་སྡེ་ཚན་འདི་ plugin དང་བརྗོད་དོན་གསར་བཟོ་མཛད་མི་ཚུ་ WordPress ལག་ལེན་འཐབ་མི་དང་་ཡོངས་འབྲེལ་ཁ་རྒྱང་གསར་བཟོ་འབད་མི་ཚུ་གི་ གནས་ཚད་ནང་ལྷོད་ཚུགས་ནི་དོན་ལུ་ཡིད་ཆེས་བཏུབ་པའི་ ཐད་དམིགས་བཟུམ་ཅིག་ཨིན་མས། WordPress གི་སྐོར་ལས་གནས་ཚུལ་དང་གསུང་བཤད་གནམ་མེད་ས་མེད་ལེགས་ཤོམ་ གོ་ཡོདཔ་ལས་ ཚོང་སྡེ་འདི་མིང་གཏམ་ཅན་ཅིག་ཨིན་པའི་ ཚོར་སྣང་དང་དགའ་བ་འབྱུང་ཡི། འདི་མ་ཚད་ ཁོང་མི་རིགས་ལེ་ཤ་གཅིག་ཁར་ཚོགས་སྟེ་ ཞལ་འཛོམས་གནང་ནིའི་སྲོལ་ཡོད་མི་འདི་ ལྷག་པར་དུ་ ཁོང་གློག་རིག་འགོ་དཔོན། བརྗོད་དོན་རྩོམ་སྒྲིག་པ་དང་གསར་བཟོ་པ་ཚུ་གི་དོན་ལུ་ ཁོང་རའི་རིག་རྩལ་དང་ལྕོགས་གྲུབ་དཔེ་སྟོན་འབད་ནིའི་དོན་ལུ་ རེ་འདོད་ཅན་གྱི་དུས་ཚོད་ལེགས་ཤོམ་ཅིག་འབད་མཇལ་ཡི།

\n

འཛམ་གླིང་ལྟ་བ་མཐུན་པའི་སྡེ་ཚན་ བེང་ཀོག ༢༠༡༨་འདི་ ཨོ་རྒྱན་དང་ ServMask གི་དོན་ལུ་ ཉིནམ་ཁག་ཆེ་ཏོག་ཏོ་ཅིག་ཨིན། འདི་ཡང་ཉིནམ་འདི་ཁར་ དུས་སྟོན་འདི་གི་དངུལ་གྱི་རྒྱབ་སྐྱོར་པ་གིས་ ཁོང་ཚུ་ལུ་སྤུ་འགྱིར་དྲག་ཡོད་པའི་ WordPress སྤྱོད་མི་ཚུ་དང་འབྲེལ་བ་འཐབ་སྟེ་ WordPress Plugin གི་སྤུས་ཚོད་ཧེང་སྐལ་ཡར་དྲག་འགྱོ་ནིའི་དོན་ལུ་ ཁོང་རའི་ངལ་རངས་གསལ་སྟོན་འབད་ནིའི་གོ་སྐབས་གནང་ཡོདཔ་ལས་བརྟེན་ཏེ་ཨིན་མས།

\n

རྒྱབ་སྐྱོར་པའི་ཉིནམ།

\n

WordCamp གི་ཉིནམ་དང་པ་འདི་ རྒྱབ་སྐྱོར་པའི་ཉིནམ་སྦེ་བརྩིཝ་ཨིན། ཉིནམ་འདི་ཁར་ཨོ་རྒྱན་གྱི་ མི་སྡེའི་སྡེ་ཚན་ཚུ་དང་འབྲེལ་བ་འཐབ་སྟེ་ ཕྱོགས་བཞི་མཚམས་བརྒྱད་ལས་འོང་མི་ WordPress གི་སྡེ་ཚན་ཚུ་དང་མཉམ་ ཁོ་རའི་བསམ་འཆར་བརྗེ་སོར་འབད་ནིའི་གོ་སྐབས་བཟང་པོ་ཡང་ཐོབ་ནུག མི་སྡེ་བརྡ་སྤྲོད་ཀྱི་ WordCamp དང WordPress གི་ཞལ་འཛོམས་འདི་ ཨོ་རྒྱན་གྱི་དོན་ལུ་ WordPress གི་ལཱ་ག་དེ་སྦེ་འབདཝ་ཨིན་ན་དང་ འདི་ག་དེ་སྦེ་ལག་ལེན་འཐབ་ནི་ཨིན་ན་ཚུའི་སྐོར་ གཞན་ལུ་བཤད་ནི་གོ་སྐབས་ཁྲིལ་བུ་སྤྲོད་མི་ ལམ་སྟོན་ཅིག་མས། དེ་གིས་སྦེ་ ཁོ་གི་ད་ལས་ཕར་གསལ་བཤད་པ་ག་དེ་མང་མང་དང་ WordPress གི་འཐུས་མི་ཚུ་ ཁོང་རའི་ཉམས་མྱོང་དང་ལྕོགས་གྲུབ་ཡར་དྲག་བཏང་ནིའི་སེམས་ཤུགས་ག་དེ་དྲག་དྲག་བསྐྱེད་བཅག་ནི་ཟེར་ སླབ་ཡོདཔ་མ་ཚད་ ཁོ་གི་འགོ་འདྲེན་པ་གསརཔ་ཚུ་ལུ་ཡང་ WordPress མི་སྡེ་འདི་དར་ཁྱབ་མ་འགྱོ་བའི་ས་གོ་ནང་ལས་ཕར་ ངོ་སྤྲོད་འབད་དེ་ ལག་ལེན་འཐབ་བཅུག་ནིའི་དོན་ལུ་ འཕྲོ་མཐུད་དེ་ར་ རྒྱབ་སྐྱོར་དང་གྲོགས་རམ་འབད་ནི་ཨིན་མས།

\n

གྲོས་ཚོགས་ཀྱིས་ཉིནམ།

\n

གྲོས་ཚོགས་ཀྱི་ཉིནམ་འདི་ WordCamp གི་ལས་རིམ་གཙོ་བོ་ཅིག་ཨིན། དེཡང་ཉིནམ་གཉིས་པའམ་འདི་ནང་ འགོ་འདྲེན་འཐབ་ཨིན། འདི་གི་སྐབས་ ཨོ་རྒྱན་གྱིས་ མི་ཚུ་གི་ དྲན་ཐེ་བཞག་ནིའི་དོན་ལས་ པར་བཏབ་ནི་གིས་ ལཱ་འགན་འདི་འབགཔ་ཨིན། ངེའི་སེམས་ཁར་ལས་འབད་བ་ཅིན་ འདི་བཟུམ་མའི་ གནས་སྐབས་འདི་ WordCamp གི་ལས་རོགསཔ་ གསལ་བཤདཔ་དང་ འགོ་འདྲེན་པ་ཚུ་གིས་ དྲན་ཐོ་བཞག་ནི་དོན་ལུ་ གནམ་མེད་ས་མེད་ལེགས་ཤོམ་ཅིག་ ཨིན་པས་ཟེར་མནོཝ་མས། མི་རིགས་ལུ་ཕན་ཐོགས་པའི་ཞབས་ཏོག་འདི་ཁྱད་དུ་འཕགསཔ་ཨིན། ང་བཅས་འགྲོ་བ་མི་ལུ་ ཕན་ཐོགས་པའི་ལཱ་འབད་མི་འདི་ ཞབས་ཏོག་ཚུ་གི་གྲས་ལས་ དྲག་ཤོས་ཅིག་ཨིན།

\n

ཨྱོན་འདི་ WordPress Meetup ཐིམ་ཕུག་གི་འགོ་འདྲེན་པ་ག་དེ་སྦེ་འབད་ཡོདཔ་ཨིན་ན།

\n

འདི་ཡང་ ཨྱོན་ཁོ་རང་ སྤྱི་ལོ་༢༠༡༦ སྤྱི་ཟླ་༡༠པའི་ ནང་ WordPress Meetup Bangkok དང་ WordCamp Bangkok ༢༠༡༨ ཀྱི་ནང་ལས་ WordPressགི་སྐོར་ལས་ཧ་གོ་བའི་ཤུལ་ འབྲུག་རྒྱལ་ཁབ་ནང་ལུ་ཡང་ གཞི་བཙུགས་འབད་དགོཔ་ཁག་ཆེ་བའི་སྐོར་ལས་ ཤེས་ཡོདཔ་ཨིན་མས།

\n

འདི་ཡང་ སྤྱི་ལོ་༢༠༡༧ སྤྱི་ཟླ་༩པའི་ སྤྱི་ཚེས་༣ རྒྱལ་སྤྱི་ WordPress སྐད་བསྒྱུར་གྱི་ཉིནམ་གྱི་སྐབས་ལུ་ WordPress Meetup Bangkok ལུ་ རྫོང་ཁ་འདི་ WordPress Core Translation ནང་ རྫོང་ཁ་འདི་ གཞན་མི་སྐད་ཡིག་དང་ཕྱདཔ་དང་ དམའ་ཤོས་ཅིག་སྦེ་ཡོདཔ་མཐོང་ཡོདཔ་ཨིན་མས།

\n

དེའི་ཤུལ་ལས་ WordCamp Bangkok ༢༠༡༨ རྒྱབ་སྐྱོར་པའི་ཉིནམ་གྱི་སྐབས་ལུ་ WordPress གི་མཉམ་རོགས་དང་ WordPress གི་མི་སྡེ་ དེ་ལས་ རྒྱལ་ཁབ་གཞན་ཁའི་ Meetup འགོ་འདྲེན་པ་ཚུ་དང་ཕྱད་ཡོདཔ་ཨིན་མས།

\n

WordPress Meetup ཐིམ་ཕུག་འདི་ ཁེབ་ས་མེད་པར་ ཁས་བླངས་ཀྱི་ཐོག་ལས་ རྒྱལ་ཡོངས་དགའ་སྐྱིད་དཔལ་འཛོམས་ཀྱི་ཀ་ཆེན་སེམས་ཁར་བཞག་སྟེ་ ལམ་སྲོལ་དང་ རྒྱལ་ཡོངས་སྐད་ཡིག་ མི་ཉམས་རྒྱུན་སྐྱོང་འབད་ནི་ལུ་དམིགས་གཏད་བསྐྱེདཔ་ཨིན།

\n

WordPress Meetup འདི་ མི་ངོམ་རང་རྐྱང་དང་ WordPress ལུ་དགའ་མི་ དེ་ལས་ རང་སོའི་ཡོན་ཏན་ བརྗེ་སོར་འབད་ནི་དང་ མི་གསརཔ་འཕྱེད་དེ་ མཐུན་ལམ་བཟོ་ནི་ལུ་ཕན་ཐོག་ཡོདཔ་ཨིན།

\n

ཨྱོན་གྱིས་ ནང་འཁོད་དང་ རྒྱལ་སྤྱིའི་སྐད་ཡིག་གི་ཐོག་ལུ་ WordPress ནང་བྲི་མི་ཚུ་ལུ་གཙོ་བོ་སྟོན་ཏེ་ ལས་སྡེ་ཚུ་ ཡང་རྒྱས་གཏང་ནི་རྒྱབ་སྐྱོར་འབདཝ་མ་ཚད་ WordPress ནང་ལས་ག་ཅིག་རང་ལྷབ་ཅི་ག་ འབྲུག་པའི་མི་སྡེ་ཚུ་ལུ་ བརྗེ་སོར་འབདཝ་ཨིན།

\n

WordPress གི་དུས་སྟོན་གྱི་ལས་རིམ་ WordPress སྐད་བསྒྱུར་གྱི་ཉིནམ་༤པ་དང་འབྲེལ་ ཨྱོན་གྱི་ WordPress Meetup Thimphu ཐེངས་དང་པའམ་འདི་ མཐར་འཁྱོལ་ཅན་སོང་ཡོདཔ་ཨིན།

\n

ཨྱོན་གྱི་རྒྱལ་ཡོངས་སྐད་ཡིག་གོང་འཕེལ་གཏང་ཐབས་ལུ་ WordPress འདི་ རྫོང་ཁ་ནང་བྲི་མི་དང་ ཡོངས་འབྲེལ་གྱི་ཐོག་ལས་ རྫོང་ཁའི་གནས་ཚུལ་ དེ་ལས་ གཞུང་གི་ཡོངས་འབྲེལ་ཚུ་ནང་ ལག་ལེན་འཐབ་སྟེ་ འབྲུག་པའི་ WordPress འདི་ མ་འོང་བུ་བརྒྱུད་ཚུ་ལུ་སྤྲོད་ནིའི་ འགན་ཁུར་གཙོ་བོ་ཅིག་འབག་སྟེ་ཡོདཔ་ཨིན།

\n

གྲུབ་འབྲས།:

\n

༡ རྫོང་ཁའི་ WordPress Core སྐད་བསྒྱུར་འབད་ཚར་ཏེ་ཡོདཔ།

\n

༢ WordPress Core སྐད་བསྒྱུར་གྱི་དོན་ལུ་ སྐ་བསྒྱུར་གསརཔ་གི་ཕན་འདེབས་འབད་ནི།

\n

༣ Global WordPress སྐད་བསྒྱུར་ཉིནམ་༤པའི་ དངོས་མཐོང་ ༼ https://wptranslationday.org/༽ ནང་བཅའ་མར་  གཏོགས་ཡོདཔ།

\n

༤ ཕྱི་རྒྱལ་ཁབ་ངགཞན་མིའི་ wordpress མཁས་མཆོག་ཚུ་ http://wpbhutan.slack.com. ནང་གདན་འདྲེན་ཞུ་ཡོདཔ།

\n

༥ WordPress Meetup ཐིམ་ཕུག་གི་འཐུས་མི་ཚུ་ WordPress དང་འབྲེལ་བའི་དོན་ཚན་ཐོག་ལུ་གྲོས་བསྡུར་འབད་ནིའི་དང་ འབྲུག་པའི་ WordPress ལག་ལེན་འཐབ་མི་ཚུ་དང་ wordpress.org ནང་འཐུས་མི་གསརཔ་ཚུ་ འཛུལ་ཞུགས་འབད་ནིའི་ནང་ རྒྱབ་སྐྱོར་འབད་ནིའི་དོན་ལུ་ http://wpbhutan.slack.com ནང་ གདན་འདྲེན་ཞུ་ཡོདཔ།

\n

༦ དེ་ནང་སྐུ་མགྲོན་སྦེ་ རྫོང་ཁག་གོང་འཕེལ་ལྷན་ཚོགས་ཀྱི་བརྡ་དོན་དང་འཕྲུལ་རིག་འགོ་དཔོན་གོངམ་ བསྟན་འཛིན་རྣམ་རྒྱལ་འབྱོན་ཡདོཔ་ཨིན།

\n

༧ ལས་རིམ་འགོ་འདྲེན་འཐབ་སའི་ས་ཁོངས་འདི་  བཟེས་སྒོ་ཡང་ལེགས་ལོམ་འཐོབ་ས་ Ariya Hotel ནང་ཨིན།

\n

༨ མཐུན་ལམ་བཟོ་ནིའི་དོན་ལུ་ འཐུས་མི་ངོ་སྤྲོད་འབད་ནི།

\n

༩ Global WordPress སྐད་བསྒྱུར་ཉིནམ་༤པའི་ སྡེ་ཚན་གྱི་གྲངས་སུ་འཛུལ་ནི།

\n

༡༠ ལས་རིམ་འདི་ ServMask Inc གི་གྲོགས་རམ་དང་ རྫོང་ཁག་གོང་འཕེལ་ལྷན་ཚོགས་ཀྱི་ སྐད་ཡིག་མཁས་མཆོག་ཚུ་གིས་རྒྱབ་སྐྱོར་འབད་ཡོདཔ།

\n

WordPress གི་མ་འོངས་པའི་འཆར་གཞི།

\n

ལཱ་དང་བྱ་བ་ག་ཅི་རང་འབད་རུང་ གྲུབ་འབྲས་ལེགས་ཤོམ་འོང་དགོ་པ་ཅིན་ ད་ལྟོ་ལས་རང་ རྩ་འགེངས་ཏེ་ ལེགས་ཤོམ་སྦེ་འབད་དགོཔ་ཨིན།

\n

ལཱ་ག་ཅིག་རང་འབད་རུང་ སྐལ་བ་ཅན་གྱི་མ་གཏོགས་རེ་བ་ཅན་གྱི་མི་འཐོབ་ཟེར་དོ་བཟུམ་ སྐལ་བ་ཡོད་པའི་ཁར་ ལཱ་ཚུ་ བརྩོན་འགྲུས་བསྐྱེད་དེ་འབད་བ་ཅིན་ ལཱ་ག་ཅི་རང་འབད་རུང་མཐར་མ་ཕྱིན་པའི་དཔེ་མི་སྲིད། དེ་འབདཝ་ལས་ ཨྱོན་གྱི་ བརྩོན་འགྲུས་དང་བསྟུན་ཁོང་གི་མ་འོངས་པའི་ Word Press གི་འཆར་གཞི་ཚུ་འོག་ལུ་འཁོད་དེ་ཡོདཔ་ཨིན།

\n

དེ་ཡང་ ཨྱོན་གྱི་ སྐད་ཡིག་གི་མཐོ་རིམ་སློབ་གྲྭ་དང་གཙུག་སྡེ་ཚུ་ནང་འགྱོ་སྟེ་ WordPress ལག་ལེན་འཐབ་ཐོག་ལས་ རྫོང་ཁའི ནང་བྲི་ཐངས་ཀྱི་སྐོར་ལས་སྟོན་བྱིན་ནི་ཨིན།

\n

དེ་མ་ཚད་ འབྲུག་པའི་ WordPressལག་ལེན་འཐབ་མི་ཚུ་འཛོམས་ཏེ་ འབུག་པའི་ལམ་སྲོལ་དང་ མཛེས་ཆའི་སྐོར་ལས་ གཞན་མི་རྒྱལ་ཁབ་ནང་ གསལ་སྟོན་འབད་ནིའི་དོན་ལུ་ གྲོས་བསྡུར་གོ་འདྲེན་འཐབ་ནི་དང་ WordPress གི་ལས་རིམ་གཙོ་ཅན་ཅིག་ཨིན་མི་ Introduction to Open Source ཟེར་མི་འདི་ འགོ་འདྲེན་འཐབ་ནིའི་ལཱ་འབད་བའི་བསྒང་རང་ཡོདཔ་ཨིན།

\n

དེ་ལས་ འབྲུག་མི་ཚུ་ WordPress ལག་ལེན་འཐབ་ནིའི་ནང་རྒྱབ་སྐྱར་འབད་དེ་ ཡར་རྒྱས་གཏང་ཞིནམ་ལས་ མི་ཚེ་སྐྱོང་ཚུགས་ནིའི་དོན་ལུ་ WordPress གི་མཁས་མཆོག་ཚུ་གདན་འདྲེན་ཞུ་སྟེ་ Wordcamp གི་དོན་ལུ་ Wordcamp ཐིམ་ཕུག་འགོ་འདྲེན་འཐབ་ནི་ཨིན།

\n

WordCamp Asia འདི་ཡང་ སྤྱི་ལོ་༢༠༢༠ལུ་འགོ་འདྲེན་འཐབ་ནི་ཨིནམ་ལས་ WordCamp Asia ནང་ལས་ འགོ་འདྲེན་པ་༤༡ཡོད་པའི་གྲལ་ཁར་ཚུད་དེ་ཡོདཔ་ཨིན།

\n

མཇུག་རང་ ཁྱོད་ར་ཚུ་ WordPress ལུ་དགའ་མི་ཅིག་ཨིན་པ་ཅིན་ ད་ལྟོ་ རང་ལུ་ རང་དབང་ཡོདཔ་་ལས་ རང་སོའི་མི་ཚེ་མཐར་འཁྱོལ་ཅན་བཟོ་ནིའི་གོ་སྐབས་ཡོདཔ་ཨིན།

\n

The post Ugyen’s Roadmap to WordPress Contributions appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Jun 2019 02:00:22 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:11:\"Ugyen Dorji\";s: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:77:\"WPTavern: New WordProof Plugin Timestamps WordPress Content on the Blockchain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90424\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:88:\"https://wptavern.com/new-wordproof-plugin-timestamps-wordpress-content-on-the-blockchain\";s: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:5868:\"

WordProof Timestamp is a new free plugin that bridges the WordPress and blockchain communities in an approachable, user-friendly way. It gives users the ability to timestamp their posts and pages to demonstrate transparency and claim ownership of content.

\n

WordProof works with any EOSIO blockchain to create the timestamp and provides a custom certificate link with a frontend pop-up to display it.

\n

\n

The plugin adds a “View the blockchain certificate” link under each post or page, which pops up the URL, title, content, timestamp information, and will soon also display revisions. Users will be able to browse through different timestamps to view the changes.

\n

WordProof Timestamp was first created by Van Ons, a WordPress agency based in Amsterdam. This is the same company that recently open sourced Laraberg, a package that allows developers building applications with Laravel to integrate the Gutenberg editor. Development has now been passed on to a dedicated WordProof team that is funded by Tenos.

\n

“I have been working and investing with blockchain as a hobby since 2013,” Van Ons founder Sebastiaan van der Lans said. “After we built the WP GDPR Compliance plugin and started working Laraberg, I am trying to work more and more on open source projects. From my point of view, WordPress + blockchain could not only democratize publishing but also doing business as a whole.”

\n

Van der Lans said he expects that any type of publishing website or any site with “Terms & Conditions” pages can benefit from timestamping. It’s especially useful in mediating claims of plagiarism and content theft. WordProof has no transaction costs and is almost instant (0.5s). Van der Lans said it was important for this solution to have no transaction fees, since it is fundamental to proving the author’s identity and the integrity of the content.

\n

Right now the plugin offers the ability to timestamp an entire article, including the title and content. Block level time-stamping is not on the roadmap, but the team is open to adding it in the future. They are currently looking into time-stamping media files and legal documents.

\n

After launching the plugin in beta, a team of 60 testers, from both the WordPress and EOS.IO blockchain communities, gave feedback that led to the creation of a WordProof Wizard to make it easier for users to set up the required accounts.

\n

“Our testers’ main concern: it was too difficult to create an account on the blockchain and download and set-up a blockchain wallet afterwards,” Van Ons head of product Jelle van der Schoot said. “Therefore, we invested a lot of time into improving the UI/UX of the entire process (downloading the plugin, creating a blockchain account, downloading and setting up a wallet, timestamping).”

\n

The wizard supports both Telos and EOS and guides users through the process of setting up an account directly inside the WordPress dashboard. The process takes approximately five minutes.

\n

\n

“We believe the WordProof Wizard can have a massive impact on the onboarding of new users to the blockchain in general, but more specifically to the Telos and EOS blockchains,” van der Schoot said.

\n

Timestamping posts is by no means a new idea. There are already several free WordPress plugins that have similar functionality and work with various blockchain technology, such as WP Blockchain, STAMPD.IO, Po.et, and Mingrana WP to Blockchain. WordProof is different from many of them in that it doesn’t use a centralized middle layer.

\n

The team behind the plugin is working on more tools that bring blockchain features to WordPress and will soon be adding cryptographically secured decentralized WordPress hosting to the WordProof lineup. van der Lans will also be speaking about more of the benefits of timestamping content with the blockchain at WordCamp Europe in his presentation titled “From WordPress to blockchain: the future is 100% open source.”

\n

If you’re interested in the project, you can follow WordProof on Twitter or join the WordProof Telegram channel where users can also find support for the plugin.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Jun 2019 21:56:39 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:96:\"WPTavern: FreeCodeCamp Moves Off of Medium after being Pressured to Put Articles Behind Paywalls\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90381\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:107:\"https://wptavern.com/freecodecamp-moves-off-of-medium-after-being-pressured-to-put-articles-behind-paywalls\";s: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:5824:\"

After four years of publishing on Medium, FreeCodeCamp is migrating all of its articles to its own open source publishing platform, a modified version of Ghost. The platform allows approved authors to cross-post their blog articles on the new FreeCodeCamp News site for free, without any ads.

\n

“Medium was a great place to publish because it helped a lot of people discover your articles. But the community has outgrown Medium,” FreeCodeCamp founder Quincy Larson said.

\n

“Medium has shifted to a paywall model where they mainly recommend paywalled articles, then encourage visitors to pay to get around their paywall.

\n

“At the same time, not much of the traffic to Medium articles comes from Medium itself. Most of it comes from Google and social media.”

\n

In the detailed public announcement on the FreeCodeCamp forums, Larson said he noticed his articles started to get less distribution after he decided that putting them behind a paywall would not be compatible with the mission of his organization.

\n

“As of 2019, Medium won’t give you much ‘distribution’ within their platform unless you’re willing to put your articles to be behind their paywall,” Larson said. “At the same time, if you do put your article behind their paywall, you’re limiting your readership to just the people who have the resources to pay. This is at odds with the goals of the freeCodeCamp community. We want to make these learning resources as widely available as possible.”

\n

In an email to blog authors who had published on FreeCodeCamp’s Medium publication, Larson elaborated on more serious concerns that he had with the platform’s approach to his organization. Oleg Isonen, one of the blog authors, published the contents of the email, which was later deleted at Larson’s request.

\n

“But over the past year Medium had become more aggressive toward us,” Larson said. “They have pressured us to put our articles behind their paywalls. We refused. So they tried to buy us. (Which makes no sense. We’re a public charity.) We refused. Then they started threatening us with a lawyer.”

\n

\n

Many of those who read the email encouraged Larson to write a follow-up article, as Medium’s tactics towards publishers are a matter of legitimate public concern, both to those who use the platform and readers who support the company through subscriptions.

\n

Larson responded, confirming that he sent the email but that he wanted to move on from the situation.

\n
\n

This email was intended only for Oleg and a few of our other authors. I have messaged him asking to delete it. We are focused on the future and want to move on from this.

\n

— Quincy Larson (@ossia) May 31, 2019

\n

\n

The new freeCodeCamp News site has migrated the organization’s 5,000 articles that were previously posted on Medium. The articles will still be available on Medium, but from now on freeCodeCamp plans to publish on its own platform. The site promises users full control, better analytics, AMP support, and a better reader experience that doesn’t require people to sign in or pay to read articles.

\n

“I’m optimistic that all of us in the developer community can start our own blogs on the open web, then use community tools like freeCodeCamp News to raise awareness of them,” Larson said.

\n

Medium abruptly changed course in 2017 to become a publisher of subscription-based content, scrapping the ad-driven revenue model without notifying publishers ahead of time. Many publications that had invested heavily in building a following on Medium were forced to leave after discovering that the company did not have their best interests in mind. Medium’s new paywalled content model, which CEO Ev Williams claims is “a different, bolder approach” targeted at fixing what is broken with media, could not sustain publishers who were convinced to join the platform in its earlier days.

\n

FreeCodeCamp joins a wave of other publications that are moving back to WordPress and other open source platforms. This trend is set to continue as Medium’s obtrusive popups and poor reader experience drive readers away from the content hosted there. Publishers who are in it for the long haul, those who value stability and full control of their content, will return to the open web.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 01 Jun 2019 00:07:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:65:\"WPTavern: WPWeekly Episode 354 – Pantheon Acquires StagingPilot\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90371&preview=true&preview_id=90371\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/wpweekly-episode-354-pantheon-acquires-stagingpilot\";s: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:2065:\"

In this episode, John James Jacoby and I discuss Panethon’s acquisition of StagingPilot and why regression visual testing will likely become a standard feature across managed WordPress hosts if it’s not already. I rant about the size of text on so many sites being too large and having to shrink the site down to 80-90% in order for it to be manageable. We celebrate WordPress’ 16th birthday, discuss what happens to unloved patches, and GitHub’s Sponsors tool.

\n

Stories Discussed:

\n

Robots, Autopilot, and The Holy Grail of WebOps

\n

WordPress Turns 16

\n

Unloved Patches

\n

New GitHub Sponsors Tool Draws Concerns from Open Source Community

\n

Automattic Acquires Prospress, the company behind WooCommerce Subscriptions

\n

Transcript:

\n

EPISODE 354 – Pantheon Acquires StagingPilot Transcript

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, June 5th 3:00 P.M. Eastern

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #354:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 May 2019 22:40:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"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:72:\"WPTavern: Automattic is Testing an Experimental Full Site Editing Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90309\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:83:\"https://wptavern.com/automattic-is-testing-an-experimental-full-site-editing-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4288:\"

Automattic is working on a new experimental Full Site Editing plugin aimed at enhancing the page creation workflow in the block editor. Starting a new page from scratch may be overwhelming for those who don’t have a vision for how to tastefully put blocks together to lay out the page. This is a problem that this experimental plugin may be able to solve.

\n

Full Site Editing currently provides three custom blocks for post content, templates, and a blog posts listing. The Blog Posts Listing block expands upon core’s Latest Posts block to include an excerpt and meta information.

\n

The plugin is available in the WordPress Plugin Directory, although it is somewhat difficult to find when searching in the admin plugin installer. The most recent 0.1.1 version of the plugin seems to be broken, but if you roll back to the initial release, you can see some of the page template experiments. After activating the plugin, navigate to Pages » Add New and a new modal with a template selector should pop up.

\n

\n

The templates come pre-filled with demo content and images, so the user doesn’t have to think about how to configure the blocks to match the demo.

\n

\n

The functionality in Full Site Editing is being developed for use on WordPress.com. It makes sense for a network that regularly onboards new bloggers and site owners. It is in the company’s best interest to deliver the fastest possible site creation experience, rather than have new users get frustrated and confused about how to get started.

\n

A template selector for creating new pages could also be useful for the broader WordPress community. Plugin developer Jeffrey Carandang tested Full Site Editing and suggested that it might be useful to add this functionality to Gutenberg with custom hooks so that developers can add their own custom templates. This would make guiding users through the new theme setup process much easier for theme shops.

\n

Automattic has a label on the Calypso repository dedicated to categorizing issues in the full site editing project. The plugin is going to be enabled on a small set of sites for initial testing. There are quite a few issues that still need to be ironed out, including things like preventing users from deleting the header and footer and finalizing the theme used with the plugin. At the moment, the plugin seems to be tailored specifically to the Twenty Nineteen theme and the pre-filled templates do not look as good when used with other themes.

\n

The functionality included in the Full Site Editing plugin may also be coming to Jetpack. Automattic’s developers are currently researching the best way to include it, since so far it has been developed as a separate plugin and not geared towards becoming a Jetpack module.

\n

Full Site Editing is not recommended for use in production, as it’s still under active development. The plugin’s details explicitly state that it is “only designed to work on the WordPress.com environment and could break after an update.” Check it out if you want to explore some exciting new possibilities for how the block editor can work together with themes to make page creation more approachable for users.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 May 2019 22:17: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: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:75:\"WPTavern: Pantheon Acquires Visual Regression Testing Platform StagingPilot\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90288\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://wptavern.com/pantheon-acquires-visual-regression-testing-platform-stagingpilot\";s: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:2952:\"

Panethon, a managed host geared towards Drupal and WordPress sites, has acquired StagingPilot. Financial details of the deal were not disclosed. Nathan Tyler, founder of StagingPilot, and his brother Phil Tyler will be brought into the company.

\n\n\n\n

StagingPilot is a four year old company that runs a barrage of visual regression tests on WordPress sites before they’re automatically updated.

\n\n\n\n

StagingPilot creates a copy of the site and places it into a staging environment. The service then conducts a number of tests that include, checking for visual errors, a white screen of death, and elements on a page disappearing. A number of snapshots are created along with a detailed report on the errors that are discovered.

\n\n\n\n

Josh Koenig, Co-Founder and Head of Product at Pantheon, says the acquisition puts the company within reach of the ‘Holy Grail’ of WebOps.

\n\n\n\n

“Once you have a hundred sites (or heck, even twenty), the grind of keeping up with routine updates can be daunting,” Koenig said. “Our existing WebOps tools let our customers automate a lot of that maintenance, but building and managing that automation is on them. We want our users to automate their operations, not operate their automation.”

\n\n\n\n

Pantheon plans to integrate StagingPilot into its offerings in three phases. First, it will migrate StagingPilot’s technology into its existing managed updates feature and extend it beyond WordPress to support Drupal.

\n\n\n\n

Then, the company plans to fully integrate the service with its organizational features providing substantial benefits to agency partners or those who manage many sites.

\n\n\n\n

The third phase looks to take advantage of services such as Google’s applied learning machines to create AI-driven testing.

\n\n\n\n

Out-of-the box, WordPress only updates minor versions automatically and leaves major updates, plugins, and themes up to the user. One of the most common fears of enabling auto-updates is having something on the site break.

\n\n\n\n

Often, the process of testing updates is left up to the consultant or whoever manages the site. Depending on the size or number of sites being managed, it can become a major time suck.

\n\n\n\n

Hosting companies like Pantheon with StagingPilot, LiquidWeb, and others are easing the fear of auto updates in general and saving people a lot of time by using automatic visual regression testing.

\n\n\n\n

To learn more about StagingPilot and to see Nathan demo the service in-person, check out this episode of WPshowandtell hosted by Jason Tucker.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 May 2019 01:32: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:30;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"WPTavern: Gutenberg 5.8 Released with Prototype of New Block-based Widgets Screen\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90267\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:92:\"https://wptavern.com/gutenberg-5-8-released-with-prototype-of-new-block-based-widgets-screen\";s: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:3753:\"

Gutenberg 5.8 was released today with three new features and more than three dozen enhancements, documentation improvements, and bug fixes.

\n

This release gives users the ability to change the text color in the Heading block. The same color options available in the paragraph and button blocks are now available in the heading block.

\n

A recent release of the EditorsKit plugin (version 1.5) added this feature and the plugin’s author had tracked nearly two dozen issues and discussions where users have asked for text highlighting or similar features.

\n

“We really need this for all block controls (lists, paragraphs etc),” Ben Gillbanks commented on the relevant GitHub issue. “Anything that can be used on a group block with a colored background could cause readability issues and so the text color will need to be changeable.” Gutenberg designer Mark Uraine said that adding text color options to all the text blocks is the next step following this update.

\n

Gutenberg 5.8 adds support for reordering gallery images using a simple arrow control to move selections forwards or backwards. This isn’t an ideal interaction but Gutenberg phase 2 lead Riad Benguella said the team is exploring adding drag and drop support.

\n

Benguella shared a video that demonstrates these two new features:

\n

\n

This release introduces an initial version of the new widgets screen. You can check it out in the admin under the Gutenberg » Widgets (beta) menu. It’s currently just a proof of concept and has quite a few bugs but gives a preview of how the the widget management screen is shaping up. Benguella said users can currently edit/update widget areas using any available block. The proof of concept implementation in the plugin allows the team to continue polishing the UI and fix bugs in future releases.

\n

\n

The editor is also making progress on mobile, adding quotes and video to the available blocks, rich captions for the image block, and fixes for several critical bugs.

\n

The editor has also recaptured some of its performance gains that were lost in version 5.7, according to recent performance benchmarks.

\n

\n

We’ve had some commenters on previous posts who said they are confused about the difference between WordPress’ core editor and the Gutenberg plugin. The plugin is where active development gets committed. All the new features are put into the plugin first so they can be tested before being rolled into an official WordPress release later down the road. If you want to get access to all the latest features Gutenberg has to offer, install the plugin and you will be able to try it before it lands in core.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 29 May 2019 22:37:14 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:73:\"WPTavern: Google’s Mobile-First Indexing is Now Default for New Domains\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90195\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:81:\"https://wptavern.com/googles-mobile-first-indexing-is-now-default-for-new-domains\";s: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:2957:\"

Google is enabling mobile-first indexing (crawling sites with a mobile user-agent) by default for new domains as of July 1, 2019. These are sites Google defines as “previously unknown to Google Search.”

\n

Mobile searches are the primary way that users engage with the search engine for the past few years, which caused Google to begin prodding website owners to make their content more mobile friendly. Google’s indexing and ranking systems originally used the desktop version of a page’s content, but this can cause problems when desktop and mobile sites contain different versions of content.

\n

Mobile-indexing is not default for all websites yet, but Google started rolling it out more widely in 2018. Google evaluates older websites for readiness based on a variety of factors:

\n

For existing websites we determine their readiness for mobile-first indexing based on parity of content (including text, images, videos, links), structured data, and other meta-data (for example, titles and descriptions, robots meta tags). We recommend double-checking these factors when a website is launched or significantly redesigned.

\n

It’s important to note that there is no separate “mobile-first index.” Google still references a unified index for serving search results. The difference is in whether a page is crawled by a desktop or mobile user-agent.

\n

Prior to responsive web design becoming the industry standard, having a separate mobile site was a common practice. Google is actively discouraging this approach now (although still supporting it), as it often causes confusion for users and search engines alike.

\n

WordPress sites using a responsive theme shouldn’t have any issues with mobile indexing as long as they are not farming out their mobile sites to a separate domain. A responsive theme is usually enough to make a site compatible with this method of crawling.

\n

Website owners can check to see how their sites are being crawled by clicking on the “URL Inspection” tab inside the Google Search Console.

\n

\n

Webmasters of older sites will get a notification from the Search Console when their sites are moved over to mobile-first indexing.

\n

After successfully ramping up mobile-first indexing from a small-scale experiment a few years ago, making it the default for new domains should be a good test for evaluating how aggressively it can be rolled out in the future.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 29 May 2019 15:49:21 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:60:\"HeroPress: I Grew Up With WordPress, Then WordPress Saved Me\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=2839\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:170:\"https://heropress.com/essays/i-grew-up-with-wordpress-then-wordpress-saved-me/#utm_source=rss&utm_medium=rss&utm_campaign=i-grew-up-with-wordpress-then-wordpress-saved-me\";s: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:10666:\"\"Pull

I grew up in the 90s and 2000s which was a weird time for technology. Part of me remembers carrying around a case of cassette tapes and the sound of dial-up occasionally screaming from the living room. The other half recalls hacking into my dad’s email from the shared family computer for the first time when I was ten. His passwords were never very hard to guess.

\n

In 2004 or 2005, I started taking more of an interest in the Internet. I wanted to start a blog maybe, but I wasn’t sure what a blog even was. WordPress was one of the first things I stumbled on, but it was still an infant compared to what it’s evolved into and I had no idea how it worked. Was WordPress a blogging website? Was it a thing I could build my own site with? How did it work?

\n

I just wanted somewhere to be myself online and WordPress intimidated me. So I dabbled, but I didn’t stay. Myspace and Tumblr would teach me to use HTML, because after all, I just wanted my own place to write online.

\n

Finding My Way Back to WordPress

\n

Eventually, my writing career led me back to WordPress. I was in college, studying English Literature when the opportunity for a Marketing Internship opened up. Around 2011, Chartwells Higher Education, a food service company for college campuses, had launched a huge multi-site network of university dining websites.

\n

Their largest initiative that year was to drive website traffic.

\n

Mine was to keep the students from kicking us off campus because of how much everyone hated Campus Dining.

\n

So I started a blog.

\n

“The Inside Scoop” gave students the perspective of a student who works for campus dining. Both goals were met and I fell in love with the idea of using writing to address business problems. Even more exciting, I finally understood WordPress. Although by then, nearly ten years had passed and WordPress had completely changed.

\n

Life Changed (a LOT), but WordPress Was Always There

\n

At the same time throughout college, I went through a major transition from life as an extremely active athlete to someone with mobility problems. I broke my back, went through everything you can think of to fix it, and ended up with a permanent disability.

\n

Thankfully, I knew by then how to work on a computer in an environment that didn’t necessarily require me to be in an office. It took a few years of adjustment, but eventually, I ended up working for a WordPress-based marketing agency remotely from an RV, which I took anywhere I felt like going.

\n

For a few years, I became a professional tourist.

\n

I’d wake up, get some work done, then adventure all day.

\n

By the time I was done, I could tour any city in a single day and still keep up with content writing. But writing content was all I did. Naturally, I still wanted my own website to write on, but all I had was Tumblr. How to actually set up a WordPress site from start to finish was a mystery to me.

\n

My partner at the agency was supposed to build the site for me, but it never happened. By the time my RV broke down in Rhode Island, 3,500 miles from my hometown, I had lost my chance to build a true travel blog and #vanlife became way too much of a fad to interest me anymore.

\n

Learning to Build Websites with WordPress

\n

My next step was to build my own website. I probably owe a lot of my “self-taught” skills to websites like WP Beginner and WPCrafter, but I really can’t remember how I learned other than trying and failing many times.

\n

After a few YouTube videos, I dove in and built the worst website that you could possibly imagine. It was atrocious, but I liked it enough, so I started writing on TaylorElizabethRose.com and building more websites.

\n

Returning to a Burning California

\n

My next few years were spent spinning my wheels on the East Coast and essentially failing at everything I tried. So I made a plan to move back to California and start my own WordPress-based business. By then I had learned a lot about website management, or so I thought.

\n

The first version of TaylordInk.com was launched in May of 2017 before I made the trip back to California in September.

\n

As we drove into Napa Valley, I noticed how dry it looked and said,“This is a fire hazard.” There were no fire breaks and I had seen what the terrain looks like before it burns when my house burned in San Diego in 2007. Napa and Santa Rosa were primed for flames.

\n

But, how many times in one person’s life can their house burn down?

\n

It was less than two weeks later when the Tubbs Fire came through and burned my entire future. The man I’d been with for two years ended up abandoning me. My business equipment was gone. Any professional clothes I may have had were incinerated. All I had were my dogs and my 2013 MacBook Pro, which happened to be with me at the time.

\n

Nothing but a Laptop

\n

Between October and December 2017, I couldn’t tell you much about what I did or what happened except that I ended up back in my hometown: San Diego. It was a blur of loneliness, depression, and complete failure. Finally, sometime mid-December, I logged into my personal website.

\n

May as well start with my own identity.

\n

It was hacked… and gone. I failed to update while I was swimming in my own sorrow.

\n

Luckily, my friend from my agency days actually had a backup of the original site. So I salvaged the posts from his files and started rebuilding. I really didn’t get very far until much later in 2019. I just kept designing and redesigning the same pages over and over again.

\n

On the second or third time I logged in after the fire, I saw the WordCamp San Diego information on the Dashboard and bought a ticket before I could change my mind about going.

\n

Discovering the WordPress Community

\n

WordCamp San Diego didn’t happen until months later, but it was the next time I really did anything productive in my life. It was kind of my last-ditch attempt to start a WordPress business or any business at all.

\n

I didn’t know what to expect. I didn’t know who I would meet, or how (or if) I would fit in. I certainly never expected to find a community with open arms.

\n

A weight was lifted from my shoulders almost immediately. Where had all these nerds been my whole life? These were my people!

\n

There’s a comfort that comes from fitting into a community and finding your people.

\n

Being in the company of like-minded people makes the future less bleak. I had hope again for the first time since the fire stole that from me.

\n

At some point during that WordCamp, a girl named Sochi found out that I was a content writer. She dragged me by the hand to meet Matt Cromwell at the Give booth. It was extremely intimidating because the entire Give Team was sitting there staring at me. I didn’t know it then, but I was meeting my own future coworkers.

\n

Give was hiring a content writer! In fact, they were close to hiring someone else, but I was intrigued. So I inquired the next day and disrupted Matt’s hiring process a bit.

\n

The next week, I joined Team Give.

\n

Over the next year, I spoke at 4 WordCamps and attended 6 or 7 total.

\n

Working at Impress.org and participating in WordCamps has been incredible and I’ve learned more about WordPress over the past year than in all the years before. I don’t think I would have succeeded as well with my own WordPress-based marketing agency without the community.

\n

More importantly, I wouldn’t have made it through some of the hardest times in my life without WordPress. It was there when I needed to work remotely and it was there when I needed a helping hand to lift me back out of tragedy.

\n

The post I Grew Up With WordPress, Then WordPress Saved Me appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 29 May 2019 15:00: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:11:\"Taylor Rose\";s: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:35:\"WPTavern: Happy Sweet 16, 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=90197\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/happy-sweet-16-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:8623:\"

Over the weekend, the WordPress community celebrated 16 years since Matt Mullenweg and Mike Little forked the B2/cafelog blogging platform to create the first official release of WordPress on May 27, 2003. It launched with a new admin interface, manual excerpts, intelligent line breaks, a link manager, and was compliant with XHTML 1.1 standards.

\n

image credit: Web Design Museum

\n

The first two months of posts on the WordPress development blog read like selections from a time capsule, capturing the early history of the software. Mullenweg shared his journey in a “thinking out loud” style throughout the process of selecting the best route for templating and other decisions that laid the groundwork for the first release. Since those early days, WordPress has outpaced all its early competitors to become the most popular CMS by a wide margin.

\n

Sixteen years later, the software is available in more than 200 languages and is now used by 33.9% of the top ten million websites. WordPress’ uncommon growth can be attributed to its unique combination of leadership, stability, and a community of thousands of contributors and entrepreneurs that are empowered by its open source licensing.

\n

Many WordPress product businesses, part of a commercial ecosystem that Mullenweg estimates at $10 billion/year, hosted sales, giveaways, and promotions in honor of the anniversary. Friends of WordPress all over the world celebrated the software’s birthday with cakes and tributes.

\n
\n

WordPress turned 16 today Happy 16th Birthday to WordPress https://t.co/1DCZ25Cr0Y pic.twitter.com/tf9LO3Qf9R

\n

— Code Pixelz Media (@codepixelzmedia) May 27, 2019

\n

\n

“We are proud to be a part of the WordPress community! Through thick and thin, WordPress has brought great innovation and inspiration to the online world,” WordPress Dhaka meetup organizer Lincoln Islam said.

\n

The WordPress community in Ahmedabad gathered together to celebrate with dinner, a custom Wapuu cake, and games. Ahmedabad, which is located in western India, is the largest city in the state of Gujarat. WordPress 4.6 was the first release to ship with a full Gujarati translation in August 2016, making the software more accessible to approximately 65.5 million Gujarati speakers worldwide. A year later, Ahmedabad hosted its first WordCamp and another followed in 2018.

\n
\n

It was awesome celebration of WordPress 16th Birthday! Discussion, Cake, Dinner and Game with WordPress Ahmedabad Community #WordPress16Birthday #WP16 #WordPress #WPAhmedabad #WPAhmedabad #Meetup pic.twitter.com/12gdpa6R3z

\n

— Chetan Prajapati ⓦ (@iamchetanp) May 27, 2019

\n

\n

The team at Bluehost published a video with a few short greetings they recorded for WordPress’ 16th birthday. When asked why they love WordPress, several said they are grateful for the opportunities and the friendships the community has brought them. Check out the #WP16 and #WordPress16thAnniversary hashtags for more WordPress cake pictures and celebrations.

\n
\n

Happy birthday WordPress! \"?\"

\n

16 years ago, on May 27, 2003, WordPress was released. We believe in WordPress and continue to be committed to growing and contributing to the WordPress open source project! Here\'s just a few of the things we love WordPress for. #WP16 pic.twitter.com/kEgLQMGnpG

\n

— Bluehost (@bluehost) May 27, 2019

\n

\n
\n

It was very amazing day to celebrate @WordPress 16th Birthday. My journey with #WordPress has been very exciting and surprising. Many more years to come with an amazing experiences.
Happy16th Birthday WordPress\"♥\"\"?\"@wcUdaipur #WP16 #WordPress16thAnniversary#Celebration #loveWP pic.twitter.com/ncyVjdZCms

\n

— Nidhi Jain (@jainnidhi03) May 27, 2019

\n

\n
\n

We had a delicious cake and a fun brain-teasing quiz with @WordPress folks. \"?\"
The cake was cut by rtCamper @am_pra_veen, who is just two years older than WordPress. \"?\"

\n

Happy sweet 16, @WordPress. Many more to come! \"?\" #WP16 pic.twitter.com/uLffaqjQni

\n

— rtCamp (@rtCamp) May 27, 2019

\n

\n
\n

WordPress is 16. Wow, I have been using it for 15 years. What an impact it has had on my life. Thank for the job, the friends and the community. I \"❤\" WordPress.

\n

— Jonny Harris \"??\" (@thespacedmonkey) May 28, 2019

\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 28 May 2019 18:53:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:44:\"WPTavern: In Case You Missed It – Issue 24\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90172&preview=true&preview_id=90172\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/in-case-you-missed-it-issue-24\";s: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:7125:\"

photo credit: Night Moves – (license)

\n

There’s a lot of great WordPress content published in the community but not all of it is featured on the Tavern. This post is an assortment of items related to WordPress that caught my eye but didn’t make it into a full post.

\n

Marcel Bootsman Is on His Way to WordCamp EU

\n

Earlier this week, Marcel Bootsman began walking his way to Berlin, Germany, the host city for WordCamp EU. The journey is more than 700 kilometers and Bootsman estimates it will take him about 30 days to reach his destination. Along the way, Bootsman has been publishing blog posts to keep readers informed of his progress.

\n
\n

Made it!#WalkToWCEU pic.twitter.com/sQ1XUv8Hje

\n

— \"??\" Marcel Bootsman (@mbootsman) May 24, 2019

\n

\n

So far, he’s published a post a day with stories that include a run-in with a bull in an open field, angry cyclists, and amazing photos of the scenery. You can follow along via the WalkToWordCamp.EU website. Donations raised from the event will go to DonateWC.

\n

WPSiteSync v1.5.2 Released

\n

The folks over at ServerPress have released a new version of WPSiteSync. This plugin enables users to migrate specific content from one site to another without the need to update target URLs for media files. This version fixes a couple of UI related bugs and interactions with Gutenberg.

\n

CannaBiz 2.4 Released

\n

Robert DeVore has released CannaBiz 2.4, a WordPress theme that’s specifically tailored for the Cannabis industry. This release includes two new action hooks, a Yelp social media link, CSS style updates, new customizer controls for button colors, and third-party plugin style updates.

\n

Alternative Gutenberg Block Styles Library

\n

Carolina Nymark has created a website and GitHub repository dedicated to creating and sharing alternative styles for Gutenberg blocks. The website contains tutorials on how to create new block styles, add them to child themes, and how to contribute to the library.

\n

Patches That Get Lost in the Void

\n

Daniel Jalkut describes what he experienced when trying to contribute a patch to WordPress to fix an issue he and his clients were having. Unfortunately, it wasn’t a good one.

\n

When somebody comes to your project with a well-thought-out, unit-tested fix, and is met by radio silence? The chances are high that they will never come back again. I have submitted WordPress patches in the past, but after this experience I don’t know if I will bother submitting them again. That’s a big change in my perspective on how the WordPress team works, and on how it should work.

\n

Jalkut isn’t the first nor will he be the last to have an experience like this. WordPress is a large project that encompasses many areas and if a particular ticket is not in line with higher priorities, the chances of it slipping through the cracks are pretty high.

\n

Human Made Launches A New Product but Some People Have No Idea What It Is

\n

Human Made has launched a new product called Altis which is a DXP or Digital Experience Platform for WordPress. After reading the press release and the associated blog post, I found it difficult to understand what the product is and who it’s for and I’m not the only one.

\n
\n

Maybe human made but not intended for humans. WTF did I just read? https://t.co/iM2sHKhLwu

\n

— Russell Heimlich (@kingkool68) May 21, 2019

\n

\n

Noel Tock, Chief Growth Officer, and Partner at Human Made chimed in and admits that the language used to describe the product is geared towards the enterprise market. He explains that Altis is an evolution beyond WordPress that supports personalization, artificial intelligence, experimentation, and faster developer experience.

\n

In a nutshell, Altis is a highly specialized version of WordPress with a UI and features that are geared towards specific clients. If you think you can explain what Altis is in a simpler way, please give it a shot in the comments.

\n

Tips for Speaking at Your First WordCamp

\n

Justin Foell of WebDevStudios explains what you need to know if you’re speaking at your first WordCamp. If you’re looking for tips on applying to speak at WordCamps, Jennifer Bourn has you covered.

\n

Speaking at Your First WordCamp? Here’s What You Need to Know!

\n

\n

After the Deadline Alternatives

\n

In light of After the Deadline being removed from Jetpack, users have been searching for alternatives. This post on WordPress.com highlights a few of them.

\n

WPCampus Diversity, Equity, and Inclusion statement

\n

Diversity, Equity, and Inclusion

\n

\n

That’s it for issue twenty-four. If you recently discovered a helpful resource or post related to WordPress, please share it with us in the comments.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 25 May 2019 02:19: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:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:35;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:76:\"WPTavern: New GitHub Sponsors Tool Draws Concerns 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=90081\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"https://wptavern.com/new-github-sponsors-tool-draws-concerns-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:9474:\"

GitHub has launched a new Sponsors tool that allows open source developer to receive financial support. The program is rolling out slowly and currently has a waitlist for open source contributors or maintainers who want to join.

\n

\n

For the first year developers are in the program, GitHub will cover all the payment processing fees and has pledged to match all contributions up to $5,000.

\n

Individual developers participating in the program can customize the funding options displayed when potential supporters click on the Sponsor button. They can add links to other popular funding services, such as Open Collective, Community Bridge, Tidelift, Ko-fi, and Patreon. Open source projects an also specify funding models for contributors by adding a .github/FUNDING.yml file to the project’s master branch.

\n
\n

Just enabled @github\'s awesome new Sponsor button for @parceljs with a link to our @opencollect! \"?\" pic.twitter.com/DJnPAtahne

\n

— Devon Govett (@devongovett) May 23, 2019

\n

\n

GitHub has an advantage over other competing funding services by having its Sponsorship model embbeded in the GitHub workflow where much of the work actually takes place. However, this also raises concerns about how sponsor expectations may influence a project’s development.

\n

“You can now sponsor developers as a seamless part of your familiar workflow,” GitHub open source project manager Devon Zuegel said in the announcement. “When a contributor answers your question, triages your issue, or merges your code, you can head to their profile—or simply hover over their username—to sponsor their work.”

\n

\n

Sponsorship is a somewhat subjective term and GitHub isn’t defining what it means here in the context of marrying it to a contributor’s workflow. For some, it may mean a no-strings-attached donation. For others, the idea of sponsorship always comes the expectation of a return on an investment.

\n

Ruby on Rails creator and Basecamp founder David Heinemeier Hansson was one of the most prominent to raise concerns about GitHub’s Sponsors program on Twitter. He sees it as “a grave risk to open source.”

\n

“’Why haven’t you fixed my issue yet!? I sent you $10! I demand you honor your obligations here. I paid you,’ welcome to small-donation open source 2019,” Hansson said.

\n

“I’m sure GitHub had all the right intentions here. And I’m sure this will work out well for a select few developers who will amass enough donations to ignore individual claims to their time. But I think it’s a grave risk to the culture of open source.”

\n

Hansson referenced a recent keynote he delivered at RailsConf 2019 titled “Open source beyond the market,” challenging those whose initial reactions are simply that “donations are a good thing.” Bringing the concept of sponsorship a into the workflow introduces a transactional nature to the work, with unavoidable marketplace expectations that can complicate a project’s development.

\n

“The marketplace norms are hard to escape,” Hansson said in his keynote. “They seep into our unconsciousness. There are plenty of open source users who think themselves less as a recipient of a gift and more like customers with warranty claims, that they’ve done the makers of said open source software a great honor by merely choosing to use their thing.

\n

“In fact, it’s kind of a natural extension of a society that worships consumerism above little less. A natural extension of ‘the customer is always right,’ of the adversarial relationship between buyer and seller.”

\n

Others have expressed more specific concerns, such as Microsoft’s GitHub becoming the dominant payment platform for open source developers, sponsors receiving priority consideration in issues and PRs over user and project needs, and developers deliberately introducing bugs in order to solicit donations.

\n
\n

Already seeing “I will prioritise your issues” in the ‘rewards’ sections on the first sponsor-enabled accounts… so.. you called it

\n

— Lasse Rafn (@LasseRafn) May 23, 2019

\n

\n

Pia Mancini, co-founder of Open Collective, wrote a response to the concerns that people were sending her way on Twitter.

\n

“I am really happy to see such an important player in the ecosystem helping out with the problem of sustaining open source,” Mancini said. “Sustaining our commons is an effort that requires everyone to contribute. I am glad to see Github come on board.”

\n

This idea of the sustainability of open source and the “tragedy of the commons” is one that Hansson and many others reject, but it is one that is commonly embraced by copyleft advocates. It works for Open Collective’s business model, but comes with its own flavor of reciprocity. Open Collective is distinct in that its funding service is removed from the direct workflow of software development, instead of deeply integrated like GitHub’s Sponsors tool.

\n

Mancini said that her company can “happily coexist with GitHub Sponsors” because of Open Collective’s chief differentiators. It was built for projects, not individuals. It offers full transparency about where funds come from and how they are spent. The company also manages the paperwork and tax forms required for fiscal sponsorship.

\n

“Open Collective is for funding projects as opposed to individual maintainers,” Mancini said. “We strongly believe in supporting communities as a whole, as well as the individuals that make up that community. This helps with ensuring more diversity, and less concentration of power and decisions on one maintainer.”

\n

She also cautioned against GitHub trying to swallow up too many aspects of the open source community and injecting its own corporate interests. She hints at a line that the company has not yet crossed but many are still wary of what Microsoft plans to do with GitHub.

\n

“Of course, there’s risk: centralization and lock-in are very risky for communities,” Mancini said. “GitHub is Microsoft, which has its own metrics in mind, and it will be difficult for them to be independent, regardless of the good faith of the folks involved.

\n

“Attempting to own all aspects of the open source community is a harmful strategy. So far, I don’t think GitHub is trying to do this. They are in a position to help, and they are open to collaborating with existing players.

\n

“Does it compete with Open Collective? To some extent. But our growth has never been primarily driven by individuals giving to individuals, but by companies giving to projects. GitHub Sponsors does not solve the need sponsor companies have for invoices and a legal entity to engage with for their vendor systems and documentation requirements.”

\n

GitHub’s intentions may simply be a recognition of what open source software has matured to become – a driving force of innovation in all industries and an effort worthy of financial support. Giving developers an easy way to receive some reward for their contributions seems rather innocuous, but the concern is that Microsoft cannot foresee the long term consequences of its sponsorship implementation inside GitHub’s workflow. Open source project maintainers who pressed GitHub for more consideration of open source workflows may get more than they bargained for.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 24 May 2019 18:40:15 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:85:\"WPTavern: Automattic Acquires Prospress, the company behind WooCommerce Subscriptions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90102\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:95:\"https://wptavern.com/automattic-acquires-prospress-the-company-behind-woocommerce-subscriptions\";s: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:4052:\"

Automattic has acquired Prospress and its flagship WooCommerce Subscriptions product, along with the company’s entire suite of e-commerce plugins and automation tools. Prospress’ 20 employees will be joining Automattic to continue developing and supporting their products.

\n

There are no immediate changes planned for current WooCommerce Subscriptions customers. Automattic will begin working on a roadmap for the product after integrating the Prospress team into the company.

\n

In the announcement Q&A, Prospress founder Brent Shepherd said he is excited to see how Subscriptions will integrate with Automattic’s existing products and offered a glimpse at what they may be working on in the near future:

\n

In more specific terms, that could mean looking at closer relationships with how payments are handled, or integrations with other platforms such as WordPress.com. There are also a couple of things to solve both in WooCommerce and subscriptions to help them scale better. Interestingly, these challenges are almost identical for the two codebases. By working more closely to solve them than we ever could apart, I hope we can do a better job of implementing solutions and in a shorter time frame.

\n

WooCommerce Subscriptions can already be purchased a la carte and used on WordPress.com stores, so nothing will change in this department. I asked Paul Maiorana, head of partnerships for WooCommerce, if there are any plans to integrate Subscription functionality with Jetpack sites, as the plugin’s team is currently pursuing a Membership feature that is essentially recurring payments.

\n

“We’re excited to learn from the Prospress team as they’re experts in this space, and could see Memberships potentially leveraging some of the Subscriptions code to avoid duplicating efforts — but we have no plans to integrate the products,” Maiorana said.

\n

The Prospress acquisition also includes AutomateWoo, a marketing automation tool, and Robot Ninja, which offers automated checkout testing for WooCommerce stores. Prospress acquired AutomateWoo in June 2018 as a complementary product to Subscriptions. There are no immediate changes planned for these products that would affect customers.

\n

Prospress has been deeply invested in the WooCoommerce open source project for many years. WooCommerce has 834 contributors and Shepherd is currently among the top 10. His company committed to the five for the future initiative last year by sponsoring one of its employees to contribute full time to WooCommerce core. For the past five years Shepherd has also co-organized the WooCommerce San Francisco meet-up.

\n

Cornering the market on Subscriptions and being able to ensure a tight integration for customers gives WooCommerce a more competitive edge in the broader e-commerce space. Prospress’ smaller products are also strategic additions to WooCommerce’s offerings. If Automattic can integrate the marketing automation and automated checkout testing tools in one hosted package, these tools have the potential to greatly increase customer’s success and confidence in their WooCommerce powered stores.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 23:20: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: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:69:\"WPTavern: Take the 2019 WP&UP Mental Health and Well-Being Survey\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90124\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/take-the-2019-wpup-mental-health-and-well-being-survey\";s: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:652:\"

WP&UP is a mental health and well-being charitable organization founded by Dan Maby in 2018, whose mission is to promote positive mental health throughout the WordPress ecosystem.

\n\n\n\n

The organization is currently hosting a survey to better understand the needs of the community.

\n\n\n\n

The questions cover the general work environment, general mental health and well-being, and specific work-related mental health and well-being. The survey will close next week and the results will be anonymized, open-sourced, and shared with the 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 22:29:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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: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:34:\"Matt: Prospress joining Automattic\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=49589\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://ma.tt/2019/05/prospress-joining-automattic/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1351:\"

As you may have read on the WooCommerce blog, Prospress blog, WP Tavern, Post Status, or Techcrunch, the team at Prospress is joining forces with WooCommerce at Automattic to help accelerate the adoption and democratization of ecommerce across the web. Whew that’s a lot of links! Prospress was best known for their extension that allowed many types of Subscriptions on top of WooCommerce, but also has some cool marketing automation and automated testing tools as well. I love that Prospress was already a Five for the Future company, which aligns really well with Automattic’s long-term goals and contributions to the wider 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 22:18:33 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"Matt\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:39;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:87:\"Post Status: Automattic has acquired Prospress, the makers of WooCommerce Subscriptions\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=62313\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://poststatus.com/automattic-has-acquired-prospress-the-makers-of-woocommerce-subscriptions/\";s: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:5108:\"

Automattic has acquired Prospress, the team led by Brent Shepherd, and the makers of the largest WooCommerce extension, WooCommerce Subscriptions.

\n\n\n\n

The acquisition secures a future for Subscriptions under the primary Automattic umbrella, and it’s an increasingly important part of WooCommerce’s success.

\n\n\n\n

Subscriptions offers the most powerful and flexible subscription option in the eCommerce market, and it’s common for stores to use WooCommerce because they need Subscriptions.

\n\n\n\n

Other providers, namely market leader Shopify, do not offer an in-house subscription option, and their third-party options are not nearly as advanced as WooCommerce Subscriptions.

\n\n\n\n

Prospress brings a couple other products and services with them
— AutomateWoo and Robot Ninja primarily — but Subscriptions is the real breadwinner. It has long been the highest revenue extension in the WooCommerce marketplace.

\n\n\n\n

Paul Maiorana, WooCommerce’s Head of Payments, Shipping, and Partnerships, tells me, “Subscriptions is an important differentiator for WooCommerce amongst eCommerce platforms, and we’re really excited to now be working closely with the Prospress team to create a more unified experience.”

\n\n\n\n

I have known Brent and his team for a long time, and I’ve used Subscriptions for many years. It’s an outstanding and complex project that requires enormous amounts of testing, a skilled development team, and a lot of care.

\n\n\n\n

In 2017, the support structure changed for third-party WooCommerce extensions, which led to an immediate surge of support hiring by the largest extension providers — namely Prospress and SkyVerge — for whom, for the purpose of disclosure, I do contract work.

\n\n\n\n

Support is the biggest component of a plugin company, especially for a complex one like Subscriptions, which interfaces (sometimes in very different ways) with dozens of payment processors. I have seen spec documentation for their proposed new features, and it is astounding how much detail is required to be outlaid before a single line of code is changed or written.

\n\n\n\n

With Automattic, a company that formerly consisted of a few dozen folks now has the backing of hundreds of “Happiness Engineers” to help manage the load.

\n\n\n\n

The primary risk I see for Subscriptions with Automattic is that it will get lost in the fray if Prospress developers are pulled to other work and more pressing needs. I have perceived this to be the case with their ownership of WP Job Manager, WooCommerce Bookings, and some other extensions — though none with the significance of Subscriptions. I think the strategic importance of Subscriptions should keep that at bay under good management, and I know Automattic management understands that strategic importance.

\n\n\n\n

Automattic will eventually go public, I’m almost certain. Strategically, I fully believe the Prospress acquisition is the right move for them. If I were involved, I would’ve been trying to make this acquisition for years now.

\n\n\n\n

Having significant revenue streams under the scope of a company out of your control is a risk, to my thinking as a theoretical investor. I would take this now in-house feature set direct to marketing channels against Shopify
— which is an absolute juggernaut in the eCommerce space today, particularly among high revenue generating stores.

\n\n\n\n

I don’t know what led Brent to make the choice to join Automattic now, but it’s a much-deserved exit after something like eight years of work.

\n\n\n\n

Brent said the following in the announcement Q&A:

\n\n\n\n

I’m extremely proud of what we’ve achieved at Prospress. I’ve had the great pleasure of having some amazing people join me over the years. Together I believe we’ve advanced a mission that matters to me — so much so that it predated Prospress and even WooCommerce.

I believe joining Automattic is the best next stage for Prospress, and I am personally excited to lead the transition and work with the Automattic team to further WooCommerce.

\n\n\n\n

I’m very happy for Brent and the entire Prospress team. I hope they made a fortune with this acquisition; in my mind, Subscriptions is one of the key reasons for WooCommerce’s amazing growth as a platform. I think they will do great there, and I have no doubt they will stay committed to making Subscriptions continue as a terrific tool in the toolbox that is 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 19:31: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:\"Brian Krogsgard\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:74:\"WPTavern: Google Updates Mobile Search Results to Include Website Branding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=90077\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:85:\"https://wptavern.com/google-updates-mobile-search-results-to-include-website-branding\";s: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:1999:\"

Google is rolling out an update to mobile search results that includes website branding. The new design displays a website’s name and icon at the top of the listing so users can easily scan results. If the result is an ad, it will be indicated in bold next to the website’s address. Below is a before and after look at the visual refresh of the mobile search results page:

\n

image credit: Google

\n

Google automatically fetches a website’s favicon for search results, so most website owners with a favicon already in place should not have to do anything to enable branded mobile search results.

\n

In 2015, WordPress 4.3 added Site Icon support to the Customizer, so users do not need to rely on a plugin to upload a favicon. WordPress stores the icon so that users do not have to upload it again when switching themes.

\n

\n

A simple, recognizable favicon establishes a visual identity for your site, and Google’s updates to mobile search results should be a strong reminder not to forget one when building a new site. Site owners may even want to spend more time designing the icon, now that a favicon’s usefulness extends beyond browser tabs to lend more authority to search results. The changes are just now rolling out to mobile but will likely be coming to desktop searches in the near future.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 17:06:25 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:41;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:57:\"WPTavern: Elementor Launches Hello Theme on WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=90021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/elementor-launches-hello-theme-on-wordpress-org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5367:\"

Elementor launched its Hello theme on WordPress.org this week. After just a few days in the directory, the theme already has more than 10,000 active installations. It is essentially a blank starter theme that offers 100% compatibility with Elementor.

\n

\n

Page builders with a large user base are in a unique position to influence the WordPress theme market. Loyal users will often select a page builder before choosing a theme from a limited pool of those that boast compatibility with their preferred plugin. Elementor is no exception, with more than 2 million installations and a 4.8-star average rating on WordPress.org.

\n

Lately the trend with some of the most popular and intuitive WordPress themes is to offer a strong, niche design out of the box, where users don’t have to make too many choices or fiddle with settings. Hello takes a different path, opeorating as more of a conduit to the Elementor page template library.

\n

The theme’s screenshot shows a home page designed in Elementor but the actual theme has very few styles and doesn’t look like anything out of the box.

\n

\n

Once installed, the first step is to create a page and select “Edit in Elementor.” From there users can select from a library of different landing page templates or start building their own layouts from scratch.

\n

\n

Hello is not a new theme. Elementor first released it on GitHub in March 2018. Hosting it on WordPress.org allows users to more easily install it and get automatic updates for improvements and security fixes.

\n

“The plugin repository played a huge role in Elementor’s exceptional growth, and we hold similar high hopes for the Hello theme,” Elementor CMO Ben Pines said.

\n

There are a few major drawbacks to using the Hello theme that may hinder its potential growth. Access to headers, footers, and widgets is restricted to Elementor Pro users. This seems like a confusing way to build a WordPress site and might be a useful detail to include in the theme’s description on WordPress.org. If there’s another way to access headers and footers without purchasing Elementor Pro, I wasn’t able to find it.

\n

WooCommerce store owners should be aware that the Hello theme does not yet offer comprehensive support for WooCommerce page styles. Although the release post advertises the theme as having “out-of-the-box” compatibility with WooCommerce, the store pages are bare bones and not very attractive. One user commented that the checkout and cart pages do not look very inviting and asked if it will be possible to edit fonts and colors with Elementor.

\n

Elementor representative Matan Naveh responded to multiple concerns about WooCommerce support and said that full compatibility is still in development:

\n

WooCommerce is a highly complex plugin and any pages that rely on its basic elements (e.g. Cart, My Account, Checkout, etc.) are even more so. The level of complexity is such that changes in something as routine as a WooCommerce update could cause havoc on a layout, resulting in a devastating effect on the webpage’s functionality.

\n

Currently, Elementor enables you to customize the areas surrounding the WooCommerce elements. Take the cart page, for example – You may not be able to customize the table itself, but you can customize the title or the area where the table is located. You can also insert your own images, backgrounds, and content according to your needs (e.g. adding an FAQ).

\n

We are considering several options for achieving full compatibility with WooCommerce. But this is still in its development stages.

\n

Some users who switched from the Astra theme, another one commonly used by Elementor users, have reported significant (50%) decreases in loading time on real world sites after switching to the Hello theme. Elementor claims that it is “the fastest WordPress theme ever created,” but the comparison benchmarks posted don’t include any themes that are known for high performance.

\n

Elementor is working on creating a child theme for Hello. It is currently in development on GitHub and the team is working on getting it approved for WordPress.org.

\n

The primary purpose of the Hello theme is to offer compatibility with the page builder, but it is not recommended for users who are not using Elementor.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 May 2019 02:10:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s: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:73:\"WPTavern: WPWeekly Episode 353 – Slack of Boundaries and A Walk to WCEU\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:59:\"https://wptavern.com/?p=90052&preview=true&preview_id=90052\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:80:\"https://wptavern.com/wpweekly-episode-353-slack-of-boundaries-and-a-walk-to-wceu\";s: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:2125:\"

In this episode, John James Jacoby and I discuss an article published by Vox on how Slack is not improving productivity, especially in large team environments. We highlight what’s new in WordPress 5.2.1, why libraries are important to the communities they serve, and new security features in WordPress 5.2. At the end of the show, we send a shoutout and good wishes to Marcel Bootsman who has begun his walk to WordCamp EU.

\n

Stories Discussed:

\n

WordPress 5.2.1 Released

\n

The Productivity Pit: How Slack Is Ruining Work

\n

Marcel Bootsman begins his walk to WCEU

\n

WordPress 5.2 Improves the Security of Automatic Updates

\n

Loveland Public Library to Host Free Beginners WordPress Class Online May 22, 2019

\n

Transcript:

\n

EPISODE 353 – Slack of Boundaries and A Walk to WCEU Transcript

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, May 29th 3:00 P.M. Eastern

\n

Subscribe to WordPress Weekly via Itunes

\n

Subscribe to WordPress Weekly via RSS

\n

Subscribe to WordPress Weekly via Stitcher Radio

\n

Subscribe to WordPress Weekly via Google Play

\n

Listen To Episode #353:
\n

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 22 May 2019 22:47: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:\"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:48:\"HeroPress: Growing Through Translating WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://heropress.com/?post_type=heropress-essays&p=2828\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:148:\"https://heropress.com/essays/growing-through-translating-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=growing-through-translating-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:20861:\"\"Pull

このエッセーは日本語でも読めます。

\n

I have spent most of my adult life knowing WordPress. In November 2003, a few months after I discovered WordPress, I gave it a spin on my personal blog. A few months later, I started contributing in the form of translating WordPress core and documentation into Japanese.

\n

Today, I make a living as a project and community manager in the field of translation & localization. I get to help people all over the world publish their voice online using their own language, while raising two kids in Tokyo, Japan. This is all thanks to WordPress, which showed me the brand new world of open source I never knew existed, and those who had given me the opportunity to participate in it.

\n

Let me share my story about how WordPress has changed my life.

\nWordCamp Tokyo 2018 organizing team & volunteer staff\n

Discovering WordPress

\n

I first found WordPress in the summer of 2003. At that time, with a degree in graphic design at a state university in the Midwest, I was working in a field that had nothing to do with design or web. The small web marketing company I joined after graduation couldn’t make it through the dot com bubble. When I moved back to the U.S. with my then-husband for him to go back to graduate school in Detroit, I couldn’t re-enter the field because of my lack of experience. I settled with a temp in-house translator/admin assistant position at an automotive company to financially support the household. You could say it was a practical choice. Or, to put it frankly, I just gave up and went with the demand for the clerical job with Japanese skill.

\n

The good thing that came out of it was that I had plenty of time after work. My ex-husband had to study all day, and my temp job was precisely 9-5. Every night, we rarely watched T.V. or went out but headed for our computers. I worked on my own website and sometimes friend’s site for a fee, using just HTML and a little bit of CSS. Back then, reading blogs written by web designers was the best way to follow up-to-date news and techniques of frontend development.

\n

Inspired by those blogs in both English and Japanese, I decided to start mine. I published my first post on a Movable Type blog in April 2003. I wrote almost every day for a few months. Then as I was getting frustrated with some aspects of Movable Type, I tried several blog engines including WordPress.

\n

With WordPress, the process of customizing blog design through edits to PHP files was straightforward and enjoyable, so I got addicted to working with WordPress right away. I almost had no experience beyond HTML and CSS before then, but I was surprised that I was able to create a dynamic site myself.

\nMy blog design between 2003-2019\n

Translating WordPress

\n

In November 2003, I re-launched my blog using WordPress. In December, I learned that there was a person named Otsukare who made a Japanese version of WordPress. This fork of WordPress, called “WordPress ME (Multilingual Edition)”, had the first comprehensive WordPress resource site in Japanese, with documentation Wiki and phpBB forums. Through the forum, I started helping him with translating documentation from English to Japanese.

\n

WordPress stayed as a relatively minor blog tool/CMS in Japan for years, but that didn’t change the fact that it was a piece of software that I really enjoyed using. I kept translating Codex, participated in theme competitions, and helping others on the forums. It was the first time for me to experience being part of an open source community and working together with people I’ve never met in person (and without being paid!).

\n

What kept me going was the feeling that I’m part of something bigger. I loved using WordPress, and it was exciting that I could help spread the word. WordPress community gave me a chance to work with people around the world — years before “remote work” was a universally recognized word. There were no free voice/video chat applications, no Slack, but the interpersonal connections have grown deeper because everyone in the community was centered around a tool to deliver your voices to others far from reach.

\n
\n

WordPress Polyglots at #WCEU contributor day, translating to so many languages! Thank you for coming! \"❤\"\"✨\" pic.twitter.com/bGvnfTIBYI

\n

— WordCamp Europe (@WCEurope) June 26, 2016

\n

\n

 

\n

Organizing WordCamp Tokyo

\n

In 2007, I went to WordCamp San Francisco and had a short conversation with Matt Mullenweg. I vaguely remember my question – something like “I love WordPress, and I want to help spread it more in Japan. What should I do?” But I still clearly remember his answer.

\n

“You should do a WordCamp.”

\n

Although it probably was just a casual suggestion since we happened to be at a WordCamp, that idea stayed with me. That short interaction was no doubt the initial trigger of our first WordCamp in Japan, a year later. I was living in the U.S., but that really didn’t matter. Japanese WordPress translators, developers, and users who knew each other through the forums and blogs all worked together to run WordCamp Tokyo 2008.

\nWordCamp Tokyo 2008. Photo credit: Odyssey\n

Career and Leadership

\n

My career also changed dramatically between 2006 and 2009.

\n

Because I gained general blog template customization skills through working with WordPress, freelance work started to come in. I also had the opportunity to write WordPress books in Japanese. Thanks to WordPress, I was able to learn and practice the idea of ​​Web Standards. My ability to write solid markups was valued, and I got my first full-time technical job as a frontend engineer at an ad agency in a suburb of Detroit.

\n

In April 2009, I started as a part-time Happiness Engineer (customer support for WordPress.com) at Automattic, then in 2010 offered a full-time position. Since then, my role had evolved into the field of localization, and I’m happy to tell you that my 10th anniversary is coming up soon.

\n

In the past few years, I’ve taken up some more global responsibilities within the WordPress community, such as one of the Global Mentors for the Polyglots Team, and lead organizer of WordPress Translation Day 4. Most recently, I was selected as the global leader of the first WordCamp Asia (planned for 2020 in Bangkok, Thailand).

\n

Growing and Giving Back

\n

The WordPress community taught me so much.

\n\n

Sometimes the process of gaining such new insights was painful, but I still feel I’m lucky to have been given challenges that made me grow.

\n

To give back, I want to continue helping communities outside of the English speaking world. I believe that’s the most powerful thing I can do to remove the barriers on the web and the vast world that it touches.

\nTokyo WordPress Meetup / WordPress Translation Day 4\n

 

\n

WordPress を通して成長できたという話

\n

高野直子

\n

 

\n

WordPress のことを知ったのは、約16年前でした。

\n

その数カ月後には元持っていたブログを WordPress に切り替え、さらにまた数カ月後には現在も続いている WordPress への翻訳という形での貢献を始めることになりました。振り返ると、社会人になってからほとんどの年数を、WordPress とともに過ごしてきたわけです。

\n

私が現在東京で子育てをしながらグローバルかつ柔軟な環境で働くことができるのは、新しい世界を見せてくれ、機会を与えてくれた WordPress の存在のおかげです。

\n

今こうやって、「WordPress との関わりが自分と周りの『バリア』を破ったこと」というテーマで記事を書かせてもらうにあたって思いを巡らせてみると、本当にこのソフトウェアと出会わなければまったく違う人生を歩んでいただろうなと思います。多くの人たちにもめぐりあうことはなかっただろうし、仕事はもちろん、住んでもいる場所も違っていたかもしれない。

\n

そんな、私にとってとても大きな存在の WordPress が、迷える20代を過ごしていた自分をどんなふうに変えてくれたかのお話をしようと思います。

\n

WordPress との出会い

\n

私が WordPress を知ったのは、2003年の春か夏頃でした。その頃の私はというと、高校留学後にアメリカ中西部の地方大学でグラフィックデザインの学位を取ったものの、新卒で入った小さな会社がドットコムバブルで立ち行かなくなったり、当時の夫の大学院入学のためにアメリカに戻ってきても経験不足で Web 関係の仕事には就けなかったり。とは言え家計を支える立場を選んだわけで、一旦やりたかった仕事はあきらめて、日系自動車会社で派遣をやっていた日々でした。インハウス翻訳者兼事務補助職のような感じで、お給料と需要を優先して良く言えばがむしゃらにがんばっていたし、悪くいうと目の前のことでいっぱいいっぱいという状況。

\n

ただ、そのころ時間だけはたっぷりあったんです。夫は暇さえあれば勉強していたし、派遣の仕事もそんなに忙しいものではなかったので、定時に帰って夕食後はテレビを見たり出かけたりはせず、それぞれパソコンに向かっていました。

\n

趣味やフリーランスの制作者として細々と HTML 手打ちのサイトなんかも作っていたのですが、Web デザイナーが個人で発信する情報はその当時ブログを読むのが何より最新で、ワクワクするものでした。

\n

そこからいきなり WordPress をインストールしたわけではなくて、まずは一番簡単そうだった Blogger.com を触ってみて制限がちょっと多すぎると感じ、Movable Type をしばらく運用してあまり相性がよくないかもと感じた、というのが私のブログ作りのスタートでした。その後ぴったりなタイミングで b2 からフォークしたリリース版を出したばかりだった WordPress に出会いました。

\n

PHP のファイルを触りながら自分のブログを作っていく過程が本当に楽しくて、いつのまにか WordPress にハマっていました。そのころはシンプルな構成だったからというのはもちろんあるんですが、それまでほぼ HTML と CSS しか書いたことがなかった自分がいつのまにかそんなふうにいわゆる「動的」サイトを作れるようになっていくことに自分でも驚きました。

\n

WordPress 翻訳を始める

\n

2003年11月にブログエンジンの変更を完了したサイトを公開し、12月に日本語版の WordPress フォーク “WordPress ME (Multilingual Edition)” を公開しているサイトがあることを知りました。Otsukare さんというエンジニアが行なっていた日本語情報の発信や日本語フォーラムでの回答をお手伝いしているうち、1ユーザーからファンへ、そしてローカリゼーションという分野でのコントリビュートをするようになっていきました。

\n

それから何年も、WordPress は日本では比較的マイナーなブログツール/CMS ではあったんですが、自分の中では本当に大好きなソフトウェアで、地道に Codex の翻訳をしたり、テーマ作成コンテストに応募したり、フォーラムで回答したりしていました。オープンソースという世界も、会ったこともない人たちと(お金にならない!)作業を一緒にするのも初めてでしたが、WordPress を通して会う人たちは本当に様々で、固定観念を覆してくれた気がします。留学や在米で「世界」を分かった気になっていたけど、それよりも私にとって理解を深めてくれたのは、英語を使ってアクセスすることができるようになった、多様な価値観が存在するオンラインのコミュニティでした。

\n

自分がブログを書くことが好きで、そのツールの成長に少しでも関われるという喜びが、飽きずにオープンソース活動を続けられた理由だった気がします。まだ「リモートワーク」なんて言葉も、動画チャットツールや Slack さえもない時期からオンラインで世界中の人達とコラボレーションする文化を持つ WordPress でしたが、遠く離れた人に考えを届られるブログというツールが中心にあったからこそ、コミュニティは深みを持って成長してきたし、人と人のつながりが構築されていったのだと思います。

\n

WordCamp Tokyo の運営

\n

2007年、サンフランシスコで開かれた WordCamp に遠征し、マットに声をかけました。「WordPress が好きで、日本でももっと広めるために何かできないかなと思ってるけど、どうしたらいいかな?」そんな内容だったと思います。質問の記憶はおぼろげですが、彼の答えは今でも覚えています。

\n

「WordCamp やったらいいよ!(You should do a WordCamp.)」

\n

たまたま WordCamp にいたからの思いつきから出た言葉だったのかもしれませんが、そのときの一言が印象的で、約1年後に日本初の WordCamp を実行するきっかけになったのは間違いありません。私自身は日本に住んでいなかったにも関わらず WordCamp Tokyo 2008 が実行できたのは、単なる言い出しっぺの私に「いいね!」と言って一緒に運営をしてくれた他の翻訳者、開発者、日本語版ユーザーの方々とのつながりがあったからでした。

\n

キャリアへの影響

\n

2006年~2009年には、自分のキャリアも大きく変わりました。

\n

WordPress にハマることで身につけたブログテンプレート一般のカスタマイズ能力でフリーランスの仕事が入ってきたり、WordPress の本を日本語で書く機会もいただきました。Web 標準の考え方に触れて実践することができたのも WordPress のおかげで、「普通に、きちんとマークアップが書ける」スキルを評価されて、ずっと前から入社したかったデトロイト郊外の会社でフロントエンドエンジニアとしての経験を積むこともできました。その後、2009年にお声がけをいただき、Automattic でのカスタマーサポート職としてスタートして、2010年からフルタイムでこの会社の「社員」となり、現在はローカリゼーション関連のチームでプロジェクト管理を担当しています。もうすぐ勤務10年を迎えます。

\n

回り回って今は翻訳チームのグローバルメンターや、WordPress Translation Day 4のリードオーガナイザーを任せてもらったり、そして自分でも驚くことに第一回 WordCamp Asia(2020年、バンコクにて開催予定)のグローバルリードにも選んでいただきました。

\n

学びとお返し

\n\n

こういうことは当たり前のようでいて、実感できないような環境も少なくないのではないでしょうか。WordPress コミュニティだって常にパーフェクトではもちろんないにしろ、この場所ではそんな「当たり前」が大事されている、と私はよく感じます。みんなが納得できる普遍的な正しさが、長期的な視点での深みのあるコミュニティの維持と成長に欠かせない要素だと理解している人が多いからなのかなと思っています。

\n

自信も経験も少なかった自分にたくさんのことを学ばせてくれた WordPress と、その周りにいる人たちへの恩返しも込めて、これからさらに英語圏以外のコミュニティも手助けしていければと思っています。そうすることで、Web と世界を少しでも良い場所にできると信じているし、関わる多くの人のバリアを取り除くきっかけとなるはずです。

\n

The post Growing Through Translating WordPress appeared first on HeroPress.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 23:00: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:12:\"Naoko Takano\";s: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:92:\"WPTavern: Loveland Public Library to Host Free Beginners WordPress Class Online May 22, 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=89982\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/loveland-public-library-to-host-free-beginners-wordpress-class-online-may-22-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3315:\"

image credit: Janko Ferlic

\n

Public libraries are one of the few remaining community centers where people freely pass on valuable skills to neighbors young and old. In addition to offering free access to books, computers, and the internet, libraries often host educational classes as a public service, with an emphasis on teaching fundamental skills for navigating the digital world.

\n

Many people who are on fixed incomes or living paycheck to paycheck cannot afford to have internet service at home. For them, the library is a gateway to online communication, job hunting, and learning new skills.

\n

Over the past five years, using WordPress has become one of those important skills, as the software is now used by 33% of the top 10 million websites, across nearly every major industry.

\n

Packed into a full schedule of toddler story time, book chats, and knitting groups, the public library in Loveland, Colorado, is hosting a free workshop called Getting Started with a WordPress Website on May 22, 2019, from 9:00 AM – 10:30 AM MDT. Participants will learn the history and terminology of WordPress, along with the step-by-step basics of creating a website. Topics include posts vs pages, using media, installing a theme, and using plugins.

\n

Participants who cannot attend in person at the library can register online for a free ticket on Facebook or through Eventbrite. Those participating remotely will need to install the Adobe Connect meeting browser plugin and will be able to listen to the lecture through the digital classroom and ask questions via chat.

\n

Another class will be hosted July 2, 2019, for those who are unable to attend the May workshop.

\n

Loveland Public Library is one of many libraries that host free WordPress classes. Skokie Public Library in Skokie, Illinois, will be hosting a Build a Website with WordPress.com workshop on Friday, May 24, and the Denver Public Library offers similar courses for WordPress.com in various locations. The New York Public Library plans to offer a Blogging for Beginners course at its Woodland Heights location on October 3, 2019. These are just a small sampling of the educational opportunities offered in this format. If you know someone who wants to get started with WordPress, local libraries are a good resource for finding a free, in-person class.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 21:56:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:55:\"WordPress.org blog: WordPress 5.2.1 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=6976\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpress.org/news/2019/05/wordpress-5-2-1-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:4909:\"

WordPress 5.2.1 is now available! This maintenance release fixes 33 bugs, including improvements to the block editor, accessibility, internationalization, and the Site Health feature introduced in 5.2.

\n\n\n\n

You can browse the full list of changes on Trac.

\n\n\n\n

WordPress 5.2.1 is a short-cycle maintenance release. Version 5.2.2 is expected to follow in approximately two weeks.

\n\n\n\n

You can download WordPress 5.2.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

Jonathan Desrosiers and William Earnhardt co-led this release, with contributions from 52 other contributors. Thank you to everyone that made this release possible!

\n\n\n\n

Alex Dimitrov, Alex Shiels, Andrea Fercia, Andrew Duthie, Andrew Ozz, Andrey “Rarst” Savchenko, Andy Fragen, anischarolia, Birgir Erlendsson (birgire), chesio, Chetan Prajapati, daxelrod, Debabrata Karfa, Dima, Dion Hulse, Dominik Schilling, Ella van Durpe, Emil Dotsev, ghoul, Grzegorz (Greg) Ziółkowski, gwwar, Hareesh, Ian Belanger, imath, Jb Audras, Jeremy Felt, Joen Asmussen, Jonathan Desrosiers, Jonny Harris, Josepha, jrf, kjellr, Marius L. J., MikeNGarrett, Milan Dinić, Mukesh Panchal, onlanka, paragoninitiativeenterprises, parkcityj, Peter Wilson, Presskopp, Riad Benguella, Sergey Biryukov, Stephen Edgar, Sébastien SERRE, Thorsten Frommen, Tim Hengeveld, Timothy Jacobs, timph, TobiasBg, tonybogdanov, Tor-Bjorn Fjellner, William Earnhardt, and Yui.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 19:04:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s: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:101:\"WPTavern: New in EditorsKit 1.5: Justify Text Alignment, Autosave On/Off Toggle, and Highlighted Text\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=89826\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/new-in-editorskit-1-5-justify-text-alignment-autosave-on-off-toggle-and-highlighted-text\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5718:\"

WordPress plugin developer Jeffrey Carandang continues to plough forward with new features for EditorsKit, a collection of page building block options for Gutenberg. What began as a block visibility management plugin has grown to include more features aimed at tweaking various settings in the editor.

\n

Version 1.5 adds some text, heading, and paragraph styling and formatting options that aren’t currently available in core. For example, Gutenberg lets users change the background color and text color for an entire paragraph, but that’s where the color customizations end. EditorsKit now supports highlighting a section of text or a heading and choosing a color or background color.

\n

\n

This may seem like a niche request to implement but Carandang has tracked nearly two dozen related issues and discussions where users are asking for text highlighting or similar features.

\n

This release also adds underline and justify alignment options to the paragraph block. Gutenberg doesn’t include it by default, as WordPress 4.7 removed the justify button from the TinyMCE editor in 2016. However, the demand for justified text has not disappeared.

\n

In adding the format to EditorsKit, Carandang cited 10 issues from Gutenberg’s GitHub repository and eight WordPress.org support topics where users have asked for the justify text option or have commented on it being missing.

\n

\n

Those who have Jetpack installed will already have the justify alignment option. Carandang plans to add a check for wpcom/justify to the next release so users of both plugins won’t have two justify options.

\n

EditorsKit 1.5 tackles the widespread issues with Gutenberg’s autosave function by adding a toggle that allows users to enable/disable it. This setting can be found under the vertical ellipses menu at the top of the editor.
\nUsers have reported getting stuck in autosave, particularly with slower connection speeds, and some have experienced problems with their hosts.

\n
\n

Neat. I’ve seen users leave their browser tab open all night and their session expires, but the autosaves continue to post even though it’s now getting a 403. Then when the person wakes up their server blacklisted their IP.

\n

— Jay (@wpdevlife) April 30, 2019

\n

\n

As the result of getting stuck in autosave, users often attempt to refresh the screen only to lose the work. This has been an ongoing problem since last year. EditorsKit gives users the option to turn autosave off if they are experiencing problems and save manually as they see fit.

\n

Version 1.5 adds theme support for changing the block width to match the page template and layout. This allows theme developers to customize block sizes based on the template the users selects.

\n

Carandang has been adding new features based on his own needs but has found most of them to be fairly common requests in the Gutenberg repository. He made upcoming features and ideas for EditorsKit public on GitHub and is accepting feature suggestions in this format. A few of his current ideas under discussion include:

\n\n

I asked Carandang if he has any plans to add an option for paring down Gutenberg to the bare essentials with an interface more focused on writing. He said it is a possibility but is optimistic that the Gutenberg team may work to solve this common complaint in core.

\n

“I’ve thought of that, specially when my writer colleague asked me about it,” he said. “But I think it’s not time for that yet. I’ll wait for more Gutenberg releases before deciding if it’s needed in EditorsKit.”

\n

Carandang said he doesn’t plan to add any custom blocks to EditorsKit. His goal is to extend blocks for users to have options that they can utilize globally, while using whichever blocks plugin(s) they prefer. The plugin currently has no revenue model but he may pursue monetization in the future.

\n

“At of the moment, I’m more focused on building the plugin features rather than monetization, but extensions may come in a year or two when Gutenberg is more stable,” Carandang said.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 14:58: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: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:89:\"WPTavern: CoBlocks 1.9.5 Merges Block Gallery Plugin into Collection, Adds New Form Block\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=89869\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:99:\"https://wptavern.com/coblocks-1-9-5-merges-block-gallery-plugin-into-collection-adds-new-form-block\";s: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:4217:\"

CoBlocks, a collection of page builder blocks that was recently acquired by GoDaddy, has added four new blocks in version 1.9.5. This is the first major release since the plugin was acquired from Rich Tabor and his co-creators. Tabor now heads up a WordPress Experience team at GoDaddy where CoBlocks’ development continues.

\n

This release merges the three gallery blocks (Masonry, Stacked, and Carousel) from the Block Gallery plugin into CoBlocks. There is a migration path for users to convert their existing Block Gallery blocks to CoBlocks’ gallery blocks. Block Gallery is still available on WordPress.org as a separate plugin with 5,000 active installs, which is actually more installs than CoBlocks (4,000). Tabor said his team is still discussing whether or not it will remove the plugin in the future.

\n

“CoBlocks is already a suite of blocks that level-up the block editor, bringing in those gallery blocks into the core plugin removes a barrier for folks who already have CoBlocks installed,” Tabor said. “Instead of folks having to install, activate, and maintain two plugins – only one is needed. On top of that, it’s far easier to maintain them collectively under one roof, as many of the components are shared between the two plugins.”

\n

In addition to merging the gallery blocks, CoBlocks 1.9.5 introduces a new Form block that allows users to customize a simple form directly within the editor. The block includes name, email, and message form fields but does not offer the ability to create new fields or change them to different types of fields. Users can set any of the fields as required using a toggle inside the block preview. For anything beyond these capabilities, a dedicated forms plugin would be required.

\n

\n

CoBlocks 1.9.5 also adds official support for Gutenberg 5.7 and includes more than a dozen tweaks and fixes.

\n

Tabor said his team is identifying further solutions that can be leveraged to make page building in WordPress more simple. CoBlocks is rapidly becoming a another one-stop shop for the mostly commonly used page building blocks.

\n

“We’re looking at how to make adding maps easier (a better Map block) and developing a system that enables restaurants to build out menus,” Tabor said.

\n

Several other block collections already offer a map block and/or a similar suite of page building functionality, such as Ghost Kit, Atomic Blocks, Stackable, and Editor Blocks. Collections seem to be the best way to offer multiple small UI elements, especially if they are all designed to be complimentary in style. Plugin authors differentiate their collections from the others with additional block options, support, complimentary themes, and immediate compatibility with the Gutenberg plugin.

\n

At the moment, there is little incentive for developers to maintain functionality as separate plugins, but WordPress’ planned single block directory may change the way blocks are packaged for optimal discovery. For now, it’s a race to see which block collection can offer the most useful suite with the most intuitive UI.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 00:57:04 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:66:\"WPTavern: WordPress 5.2 Improves the Security of Automatic Updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=89913\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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-5-2-improves-the-security-of-automatic-updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4791:\"

WordPress 5.2, released earlier this month, added the first step towards fully secure updates with offline digital signatures. Scott Arciszewski, Chief Development Officer for Paragon Initiative Enterprises, explains how it works and how developers can migrate away from mcrypt to libsodium.

\n\n\n\n

When your WordPress site installs an automatic update, from version 5.2 onwards, it will first check for the existence of an x-content-signature header.

If one isn’t provided by the update server, your WordPress site will instead query for a filenamehere.sig file.

No matter how it’s delivered, the signatures are calculated using Ed25519 of the SHA384 hash of the file’s contents. The signature is base64-encoded for safe transport.

Scott Arciszewski
\n\n\n\n

The WordPress core development team manages the signing or secret keys. WordPress 5.2 contains a signing key that expires on April 1, 2021. The verification key or public key is used to decipher the secret key. This value determines the validity of the signature.

\n\n\n\n

Since the feature is still in an experimental phase, WordPress 5.2 allows an update to occur if a soft error or invalid signature is encountered. This is to prevent more severe errors from causing the user to be locked out of the update process until a manual update is applied. The team will use the reported error information to improve the signature checking process.

\n\n\n\n

The digital signatures are only supported for core updates with Themes and Plugins to follow in a later release. It’s also likely that the team will include separate keys for core releases, plugins, themes, translations, etc. to allow for more fine-grained control.

\n\n\n\n

Digital signatures applied to WordPress core updates is an important milestone because it prevents users from unknowingly downloading updates from malicious sources.

\n\n\n\n

For example, without digital signatures, if the server or servers that house the core update files were compromised, a false update could be sent to millions of sites. In 2016, WordFence explained how this scenario could play out when they publicized a security vulnerability they discovered with api.wordpress.org.

\n\n\n\n

Persistence Pays Off

\n\n\n\n

In early 2017, Arciszewski published a plea to Matt Mullenweg to focus on securing WordPress’ automatic updates system by using secure cryptographic signatures. Mullenweg responded to the article with one of his own on Medium.

\n\n\n\n

We will at some point; as said above it’s a good idea — can’t hurt, might help. There are, however, some more important security issues in front of it, that impact millions of sites in the real world, so we are prioritizing those issues above a nice-to-have, defense in-depth effort.

Matt Mullenweg
\n\n\n\n

Arciszewski has spent at least six years trying to convince the core team to implement digitally signed updates. Four months ago, Gary Pendergast, WordPress core developer, responded to the ticket saying that the feature fell in line with the list of WordPress priorities planned for 2019 and beyond. Pendergast laid out a plan and with a confirmed commitment to landing it in core, Arciszewski worked with the core team to make it a reality.

\n\n\n\n

Millions of WordPress sites are on their way to becoming more secure thanks to the persistence and efforts of Arciszewski and the WordPress core team.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 20 May 2019 21:28:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jeff Chandler\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:56:\"WPTavern: Jetpack Opens Signup for Membership Block Beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=89859\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wptavern.com/jetpack-opens-signup-for-membership-block-beta\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1749:\"

Jetpack has opened a signup for the beta of its upcoming Membership feature in order to collect feedback from potential testers. The changelog for version 7.3, released two weeks ago, hinted at a new Membership block coming to the plugin. The work in progress was added behind the JETPACK_BETA_BLOCKS constant, presumably in preparation for wider testing.

\n

Based on the feature’s description on GitHub, the first iteration will function like a recurring payment/donation button that uses Stripe as the payment gateway. In this case, “membership” might be a misnomer for the feature. The wording on the beta signup page lends to the confusion: “WordPress.com is currently preparing a feature that will let you enable subscriptions on your site.”

\n

At the moment, it appears that the Jetpack team hasn’t fully decided what this feature will become and seems open to seeing where it will go. Beta testers will likely refine the direction of the block. If you have an interest in using Jetpack’s membership capabilities in the future and want to shape its development, you can sign up for the beta by providing your WordPress.com login and a description of your needs and expectations for the feature.

\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 18 May 2019 04:09:53 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Wed, 19 Jun 2019 00:36:17 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Wed, 19 Jun 2019 00:15:29 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:2:\"br\";}}s:5:\"build\";s:14:\"20130911073210\";}','no'),(253,'_site_transient_browser_fd1885f00291b83c2cb49a9bbb9a909a','a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:13:\"74.0.3729.169\";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'),(254,'_site_transient_timeout_php_check_a5907c2ea4d6fbd7e531b3aa7734f0e4','1561509375','no'),(255,'_site_transient_php_check_a5907c2ea4d6fbd7e531b3aa7734f0e4','a:5:{s:19:\"recommended_version\";s:3:\"7.3\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:0;s:9:\"is_secure\";b:0;s:13:\"is_acceptable\";b:1;}','no'),(257,'_site_transient_community-events-e151b4de1b48516b09bec68ad6fbd41b','a:2:{s:8:\"location\";a:1:{s:2:\"ip\";s:11:\"95.216.96.0\";}s:6:\"events\";a:6:{i:0;a:7:{s:4:\"type\";s:8:\"wordcamp\";s:5:\"title\";s:15:\"WordCamp Europe\";s:3:\"url\";s:33:\"https://2019.europe.wordcamp.org/\";s:6:\"meetup\";s:0:\"\";s:10:\"meetup_url\";s:0:\"\";s:4:\"date\";s:19:\"2019-06-20 00:00:00\";s:8:\"location\";a:4:{s:8:\"location\";s:15:\"Berlin, Germany\";s:7:\"country\";s:2:\"DE\";s:8:\"latitude\";d:52.50697000000000258523868978954851627349853515625;s:9:\"longitude\";d:13.2843064000000001811940819607116281986236572265625;}}i:1;a:7:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:25:\"WordPress Helsinki Meetup\";s:3:\"url\";s:51:\"https://www.meetup.com/WPHelsinki/events/258726852/\";s:6:\"meetup\";s:18:\"WordPress Helsinki\";s:10:\"meetup_url\";s:34:\"https://www.meetup.com/WPHelsinki/\";s:4:\"date\";s:19:\"2019-07-03 17:30:00\";s:8:\"location\";a:4:{s:8:\"location\";s:12:\"HKI, Finland\";s:7:\"country\";s:2:\"FI\";s:8:\"latitude\";d:60.169998168944999861196265555918216705322265625;s:9:\"longitude\";d:24.9400005340580008805773104541003704071044921875;}}i:2;a:7:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:25:\"WordPress Helsinki Meetup\";s:3:\"url\";s:51:\"https://www.meetup.com/WPHelsinki/events/258726857/\";s:6:\"meetup\";s:18:\"WordPress Helsinki\";s:10:\"meetup_url\";s:34:\"https://www.meetup.com/WPHelsinki/\";s:4:\"date\";s:19:\"2019-08-07 17:30:00\";s:8:\"location\";a:4:{s:8:\"location\";s:12:\"HKI, Finland\";s:7:\"country\";s:2:\"FI\";s:8:\"latitude\";d:60.169998168944999861196265555918216705322265625;s:9:\"longitude\";d:24.9400005340580008805773104541003704071044921875;}}i:3;a:7:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:25:\"WordPress Helsinki Meetup\";s:3:\"url\";s:51:\"https://www.meetup.com/WPHelsinki/events/258726864/\";s:6:\"meetup\";s:18:\"WordPress Helsinki\";s:10:\"meetup_url\";s:34:\"https://www.meetup.com/WPHelsinki/\";s:4:\"date\";s:19:\"2019-09-04 17:30:00\";s:8:\"location\";a:4:{s:8:\"location\";s:12:\"HKI, Finland\";s:7:\"country\";s:2:\"FI\";s:8:\"latitude\";d:60.169998168944999861196265555918216705322265625;s:9:\"longitude\";d:24.9400005340580008805773104541003704071044921875;}}i:4;a:7:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:25:\"WordPress Helsinki Meetup\";s:3:\"url\";s:51:\"https://www.meetup.com/WPHelsinki/events/258726867/\";s:6:\"meetup\";s:18:\"WordPress Helsinki\";s:10:\"meetup_url\";s:34:\"https://www.meetup.com/WPHelsinki/\";s:4:\"date\";s:19:\"2019-10-02 17:30:00\";s:8:\"location\";a:4:{s:8:\"location\";s:12:\"HKI, Finland\";s:7:\"country\";s:2:\"FI\";s:8:\"latitude\";d:60.169998168944999861196265555918216705322265625;s:9:\"longitude\";d:24.9400005340580008805773104541003704071044921875;}}i:5;a:7:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:25:\"WordPress Helsinki Meetup\";s:3:\"url\";s:51:\"https://www.meetup.com/WPHelsinki/events/258726871/\";s:6:\"meetup\";s:18:\"WordPress Helsinki\";s:10:\"meetup_url\";s:34:\"https://www.meetup.com/WPHelsinki/\";s:4:\"date\";s:19:\"2019-11-06 17:30:00\";s:8:\"location\";a:4:{s:8:\"location\";s:12:\"HKI, Finland\";s:7:\"country\";s:2:\"FI\";s:8:\"latitude\";d:60.169998168944999861196265555918216705322265625;s:9:\"longitude\";d:24.9400005340580008805773104541003704071044921875;}}}}','no'),(258,'_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3','1560947776','no'),(259,'_transient_feed_9bbd59226dc36b9b26cd43f15694c5c3','a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:49:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"News – – WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"https://wordpress.org/news\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"WordPress News\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 19:42: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: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=5.3-alpha-45546\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:10:{i:0;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.2.2 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2019/06/wordpress-5-2-2-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 18 Jun 2019 18:14:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6993\";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:348:\"WordPress 5.2.2 is now available! This maintenance release fixes 13 bugs and adds a little bit of polish to the Site Health feature that made its debut in 5.2. For more info, browse the full list of changes on Trac or check out the Version 5.2.2 documentation page. WordPress 5.2.2 is a short-cycle maintenance release. The next […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"marybaum\";s: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:3961:\"\n

WordPress 5.2.2 is now available! This maintenance release fixes 13 bugs and adds a little bit of polish to the Site Health feature that made its debut in 5.2.

\n\n\n\n

For more info, browse the full list of changes on Trac or check out the Version 5.2.2 documentation page.

\n\n\n\n

WordPress 5.2.2 is a short-cycle maintenance release. The next major release will be version 5.3; check make.wordpress.org/core for details as they happen.

\n\n\n\n

You can download WordPress 5.2.2 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

JB Audras, Justin Ahinon and Mary Baum co-led this release, with invaluable guidance from our Executive Director, Josepha Haden Chomphosy, and contributions from 30 other contributors. Thank you to everyone who made this release possible!

\n\n\n\n

Andrea Fercia, Andrew Duthie, Andrew Ozz, Andy Fragen, Birgir Erlendsson (birgire), Chetan Prajapati, David Baumwald, Debabrata Karfa, Garrett Hyder, Janki Moradiya, Jb Audras, jitendrabanjara1991, Jonathan Desrosiers, Jonny Harris, Jorge Costa, Justin Ahinon, Marius L. J., Mary Baum, Meet Makadia, Milan Dinić, Mukesh Panchal, palmiak, Pedro Mendonça, Peter Wilson, Rami Yushuvaev, Riad Benguella, sarah semark, Sergey Biryukov, Shashank Panchal, Tammie Lister, Tim Hengeveld, vaishalipanchal, vrimill, and William Earnhardt

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6993\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:1;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"The Month in WordPress: May 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/06/the-month-in-wordpress-may-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Jun 2019 10:21:27 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6987\";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:319:\"This month saw the 16th anniversary since the launch of the first release of WordPress. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:6602:\"\n

This month saw the 16th anniversary since the launch of the first release of WordPress. A significant milestone to be sure and one that speaks to the strength and stability of the project as a whole. In this anniversary month, we saw a new major release of WordPress, some exciting new development work, and a significant global event.

\n\n\n\n
\n\n\n\n

Release of WordPress 5.2

\n\n\n\n

WordPress 5.2 “Jaco” was released on May 7 shipping some useful site management tools, such as the Site Health Check and PHP Error Protection, as well as a number of accessibility, privacy, and developer updates. You can read the field guide for this release for more detailed information about what was included and how it all works.

\n\n\n\n

327 individual volunteers contributed to the release. If you would like to be a part of that number for future releases, follow the Core team blog and join the #core channel in the Making WordPress Slack group.

\n\n\n\n

A Successful WordPress Translation Day 4

\n\n\n\n

WordPress Translation Day is a 24-hour event organised by the Polyglots team where community members from all over the world come together to translate WordPress into their local languages. For the fourth edition held on 11 May, 183 brand new contributors joined the Polyglots team from 77 communities across 35 countries in Africa, Asia, Europe, North America, South America, and Oceania.

\n\n\n\n

While the WP Translation Day is a great time for focussed contributions to localizing WordPress, but these contributions can happen at any time of the year, so if you would like to help make WordPress available in your local language, follow the Polyglots team blog and join the #polyglots channel in the Making WordPress Slack group.

\n\n\n\n

Updated Plugin Guidelines Proposal

\n\n\n\n

The Plugins team has proposed some updates to the guidelines for developers on the Plugin Directory. The majority of the proposed changes are intended to address significant issues faced by developers who do not speak English as a first language, making the Plugin DIrectory a more accessible and beneficial place for everyone.

\n\n\n\n

The proposal will be open for comments until late June, so the community is encouraged to get involved with commenting on them and the direction they will take the Plugin Directory. If you would like to be involved in this discussion, comment on the proposal and join the #plugin review team in the Making WordPress Slack group.

\n\n\n\n

Continued Gutenberg Development

\n\n\n\n

Since the block editor was first released as part of WordPress Core in v5.0, development has continued in leaps and bounds with a new release every two weeks. The latest update includes some great incremental improvements that will be merged into the 5.2.2 release of WordPress along with the other recent enhancements.

\n\n\n\n

In addition to the editor enhancements, work has been ongoing in the Gutenberg project to bring the block editing experience to the rest of the WordPress dashboard. This second phase of the project has been going well and the latest update shows how much work has been done so far.

\n\n\n\n

In addition to that, the Block Library project that aims to bring a searchable library of available blocks right into the editor is deep in the planning phase with a recent update showing what direction the team is taking things.

\n\n\n\n

If you would like to get involved in planning and development of Gutenberg and the block editor, follow the Core and Design team blogs and join the #core, #design, and #core-editor channels in the Making WordPress Slack group.

\n\n\n\n
\n\n\n\n

Further Reading:

\n\n\n\n\n\n\n\n

Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6987\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.2.1 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2019/05/wordpress-5-2-1-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 May 2019 19:04:49 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:5:\"5.2.1\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6976\";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:405:\"WordPress 5.2.1 is now available! This maintenance release fixes 33 bugs, including improvements to the block editor, accessibility, internationalization, and the Site Health feature introduced in 5.2. You can browse the full list of changes on Trac. WordPress 5.2.1 is a short-cycle maintenance release. Version 5.2.2 is expected to follow in approximately two weeks. You can download […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s: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:4923:\"\n

WordPress 5.2.1 is now available! This maintenance release fixes 33 bugs, including improvements to the block editor, accessibility, internationalization, and the Site Health feature introduced in 5.2.

\n\n\n\n

You can browse the full list of changes on Trac.

\n\n\n\n

WordPress 5.2.1 is a short-cycle maintenance release. Version 5.2.2 is expected to follow in approximately two weeks.

\n\n\n\n

You can download WordPress 5.2.1 or visit Dashboard → Updates and click Update Now. Sites that support automatic background updates have already started to update automatically.

\n\n\n\n

Jonathan Desrosiers and William Earnhardt co-led this release, with contributions from 52 other contributors. Thank you to everyone that made this release possible!

\n\n\n\n

Alex Dimitrov, Alex Shiels, Andrea Fercia, Andrew Duthie, Andrew Ozz, Andrey “Rarst” Savchenko, Andy Fragen, anischarolia, Birgir Erlendsson (birgire), chesio, Chetan Prajapati, daxelrod, Debabrata Karfa, Dima, Dion Hulse, Dominik Schilling, Ella van Durpe, Emil Dotsev, ghoul, Grzegorz (Greg) Ziółkowski, gwwar, Hareesh, Ian Belanger, imath, Jb Audras, Jeremy Felt, Joen Asmussen, Jonathan Desrosiers, Jonny Harris, Josepha, jrf, kjellr, Marius L. J., MikeNGarrett, Milan Dinić, Mukesh Panchal, onlanka, paragoninitiativeenterprises, parkcityj, Peter Wilson, Presskopp, Riad Benguella, Sergey Biryukov, Stephen Edgar, Sébastien SERRE, Thorsten Frommen, Tim Hengeveld, Timothy Jacobs, timph, TobiasBg, tonybogdanov, Tor-Bjorn Fjellner, William Earnhardt, and Yui.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6976\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"Tomorrow is WordPress Translation Day 4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wordpress.org/news/2019/05/tomorrow-is-wordpress-translation-day-4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 May 2019 09:17: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:13:\"Documentation\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:6:\"Events\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=6961\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:11:\"isPermaLink\";s:5:\"false\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:342:\"The fourth edition of WordPress translation day is coming up on Saturday 11 May 2019: tomorrow! Get ready for a 24-hour, global marathon dedicated to localizing the WordPress platform and ecosystem. This event takes place both online and in physical locations across the world, so you can join no matter where you are! The 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: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:3747:\"\n

The fourth edition of WordPress translation day is coming up on Saturday 11 May 2019: tomorrow! Get ready for a 24-hour, global marathon dedicated to localizing the WordPress platform and ecosystem. This event takes place both online and in physical locations across the world, so you can join no matter where you are!

\n\n\n\n

The WordPress Polyglots Team has a mission to translate and make available the software’s features into as many languages as possible. As WordPress powers more than 33% of websites, people from across the world use it in their daily life. That means there is a lot that needs translating, and into many different languages.

\n\n\n\n

On 11 May 2019, from 00:00 UTC until 23:59 UTC, WordPress Translation Day aims to celebrate the thousands of volunteers who contribute to translation and internalization. The event is also an opportunity for encouraging more people to get involved and help increase the availability of themes and plugins in different languages.

\n\n\n\n

“At the time of the last event in 2017, WordPress was being translated into 178 languages, we have now reached the 200 mark!”

WPtranslationday.org
\n\n\n\n

What happens on WordPress Translation Day?

\n\n\n\n

There are a number of local meetings all over the world, as well as online talks by people from the WordPress community. More than 700 people from around the world took part in past WordPress Translation Days, and everyone welcome to join in this time around!

\n\n\n\n

Everyone is welcome to join the event to help translate and localize WordPress, no matter their level of experience. A lot is happening on the day, so join in and you will learn how to through online sessions!

\n\n\n\n

What can you expect?

\n\n\n\n\n\n\n\n

A number of experienced WordPress translators and internationalization experts are part of the line-up for the livestream, joined by some first time contributors.

\n\n\n\n

Whether you have or haven’t contributed to the Polyglots before, you can join in for WordPress Translation Day. Learn more about both local and online events and stay updated through the website and social media.

\n\n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6961\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:4;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:24:\"WordPress 5.2 “Jaco”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/news/2019/05/jaco/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 07 May 2019 21:03:35 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6925\";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:426:\"Version 5.2 of WordPress is available for download or update in your WordPress dashboard. New features in this update make it easier than ever to fix your site if something goes wrong. There are even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Matt Mullenweg\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:31720:\"\n

Keeping Sites Safer

\n\n\n\n
\"\"
\n\n\n\n

Version 5.2 of WordPress, named “Jaco” in honor of renowned and revolutionary jazz bassist Jaco Pastorius, is available for download or update in your WordPress dashboard. New features in this update make it easier than ever to fix your site if something goes wrong.

\n\n\n\n

There are even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.

\n\n\n\n
\n\n\n\n

Site Health Check

\n\n\n\n
\"\"
\n\n\n\n

Building on the Site Health features introduced in 5.1, this release adds two new pages to help debug common configuration issues. It also adds space where developers can include debugging information for site maintainers.

\n\n\n\n
\n\n\n\n

PHP Error Protection

\n\n\n\n
\"\"
\n\n\n\n

This administrator-focused update will let you safely fix or manage fatal errors without requiring developer time. It features better handling of the so-called “white screen of death,” and a way to enter recovery mode,  which pauses error-causing plugins or themes.

\n\n\n\n
\n\n\n\n
\n\n\n\n

Improvements for Everyone

\n\n\n\n

Accessibility Updates

\n\n\n\n

A number of changes work together to improve contextual awareness and keyboard navigation flow for those using screen readers and other assistive technologies.

\n\n\n\n

New Dashboard Icons

\n\n\n\n

Thirteen new icons including Instagram, a suite of icons for BuddyPress, and rotated Earth icons for global inclusion. Find them in the Dashboard and have some fun!

\n\n\n\n

Plugin Compatibility Checks

\n\n\n\n

WordPress will now automatically determine if your site’s version of PHP is compatible with installed plugins. If the plugin requires a higher version of PHP than your site currently uses, WordPress will not allow you to activate it, preventing potential compatibility errors.

\n\n\n\n
\n\n\n\n

Developer Happiness

\n\n\n\n
\n
\n

PHP Version Bump

\n\n\n\n

The minimum supported PHP version is now 5.6.20. As of WordPress 5.2*, themes and plugins can safely take advantage of namespaces, anonymous functions, and more!

\n
\n\n\n\n
\n

Privacy Updates

\n\n\n\n

A new theme page template, a conditional function, and two CSS classes make designing and customizing the Privacy Policy page easier.

\n
\n
\n\n\n\n
\n
\n

New Body Hook

\n\n\n\n

5.2 introduces a wp_body_open hook, which lets themes support injecting code right at the beginning of the <body> element.

\n
\n\n\n\n
\n

Building JavaScript

\n\n\n\n

With the addition of webpack and Babel configurations in the wordpress/scripts package, developers won’t have to worry about setting up complex build tools to write modern JavaScript.

\n
\n
\n\n\n\n

*If you are running an old version of PHP (less than 5.6.20), update your PHP before installing 5.2.

\n\n\n\n
\n\n\n\n

The Squad

\n\n\n\n

This release was led by Matt Mullenweg, Josepha Haden Chomphosy, and Gary Pendergast. They were graciously supported by 327 generous volunteer contributors. Load a Jaco Pastorius playlist on your favorite music service and check out some of their profiles:

\n\n\nAaron D. Campbell, Aaron Jorbin, Adam Silverstein, Adam Soucie, Adil Öztaşer, Ajit Bohra, Alain Schlesser, Alda Vigdís, Alex Denning, Alex Dimitrov, Alex Kirk, Alex Mills, Alex Shiels, Alexis, Alexis Lloyd, allancole, Allen Snook, André, andraganescu, Andrea Fercia, Andrea Middleton, Andrei Lupu, Andrew Dixon, Andrew Duthie, Andrew Nacin, Andrew Ozz, Andrey \"Rarst\" Savchenko, Andrés Maneiro, Andy Fragen, Andy Meerwaldt, Aniket Patel, anischarolia, Anton Timmermans, Anton Vanyukov, Antonio Villegas, antonypuckey, Aristeides Stathopoulos, Aslam Shekh, axaak, Bego Mario Garde, Ben Dunkle, Ben Ritner - Kadence Themes, Benjamin Intal, Bill Erickson, Birgir Erlendsson, Bodo (Hugo) Barwich, bonger, Boone Gorges, Bradley Taylor, Brandon Kraft, Brent Swisher, Burhan Nasir, Cathi Bosco, Chetan Prajapati, Chiara Magnani, Chouby, Chris Van Patten, D.S. Webster, Damon Cook, Daniel Bachhuber, Daniel James, Daniel Llewellyn, Daniel Richards, Daniele Scasciafratte, Darren Ethier, Dave Whitley, DaveFX, davetgreen, David Baumwald, David Binovec, David Binovec, David Herrera, David Roddick, David Smith, Davide \'Folletto\' Casali, daxelrod, Debabrata Karfa, dekervit, Denis de Bernardy, Dennis Snell, Derek Herman, Derrick Hammer, designsimply, Dhanukanuwan, Dharmesh Patel, Diane, diegoreymendez, Dilip Bheda, Dima, Dion Hulse, Dixita Dusara, Dmitry Mayorov, Dominik Schilling, Drew Jaynes, dsifford, EcoTechie, Eduardo Toledo, Ella Van Durpe, Emil Dotsev, fabiankaegy, Faisal Alvi, Farhad Sakhaei, Felix Arntz, Franklin Tse, Fuegas, Garrett Hyder, Gary Jones, Gennady Kovshenin, ghoul, Girish Panchal, Grzegorz Ziółkowski, Guido Scialfa, GutenDev \"✍\"\"㊙\", gwwar, Hannah Malcolm, Hardik Amipara, Hardik Thakkar, Hendrik Luehrsen, Henry, Henry Wright, Hoover, Ian Belanger, Ian Dunn, ice9js, Igor Zinovyev, imath, Ixium, J.D. Grimes, jakeparis, James, janak Kaneriya, Janki Moradiya, Jarred Kennedy, Javier Villanueva, Jay Upadhyay, Jaydip Rami, Jaye Simons, Jayman Pandya, jdeeburke, Jean-Baptiste Audras, Jeff Paul, Jeffrey de Wit, Jenny Wong, Jeremy Felt, Jeremy Green, Jeremy Herve, jitendrabanjara1991, JJJ, Joe Dolson, Joe McGill, Joen Asmussen, Johan Falk, Johanna de Vos, John Blackbourn, Jonathan Desrosiers, Jonathandejong, joneiseman, Jonny Harris, jonnybojangles, Joost de Valk, jordesign, Jorge Bernal, Jorge Costa, Jory Hogeveen, Jose Castaneda, josephwa, Josh Feck, JoshuaWold, Joy, jplo, JR Tashjian, jrf, Juhi Patel, juliarrr, justinahinon, K. Adam White, KamataRyo, Karine Do, Katyatina, Kelin Chauhan, Kelly Dwan, Khokan Sardar, killua99, Kite, Kjell Reigstad, Knut Sparhell, Koji Kuno, Konstantin Obenland, Konstantinos Xenos, Kʜᴀɴ (ಠ_ಠ), laurelfulford, lkraav, lovingboth, Luke Carbis, Luke Gedeon, Luke Pettway, Maciej Palmowski, Maedah Batool, Maja Benke, Malae, Manzoor Wani, Marcin, Marcin Pietrzak, Marco Fernandes, Marco Peralta, Marcus Kazmierczak, marekhrabe, Marius Jensen, Mariyan Belchev, Mark Uraine, markcallen, Markus Echterhoff, Marty Helmick, marybaum, mattnyeus, mdwolinski, Meet Makadia, Mel Choyce, mheikkila, Micah Wood, michelleweber, Miguel Fonseca, Miguel Torres, Mikael Korpela, Mike Auteri, Mike Schinkel [WPLib Box project lead], Mike Schroder, Mike Selander, MikeNGarrett, Milan Dinić, mirka, Mobin Ghasempoor, Mohadese Ghasemi, Mohammed Saimon, Morten Rand-Hendriksen, Morteza Geransayeh, Muhammad Muhsin, Mukesh Panchal, Mustafa Uysal, mzorz, Nahid F. Mohit, Naoki Ohashi, Nate Allen, Ned Zimmerman, Neokazis Charalampos, Nick Cernis, Nick Diego, Nick Halsey, Nidhi Jain, Niels, Niels de Blaauw, Nikolay Nikolov, Nilambar Sharma, ninio, notnownikki, Oliver Sadler, onlanka, pandelisz, Pascal Birchler, Paul Bearne, Paul Biron, Pedro Mendonça, Peter Booker, Peter Wilson, pfiled, pilou69, Pranali Patel, Pratik, Pratik K. Yadav, Presskopp, psealock, Punit Patel, Rachel Cherry, Rahmon, Ramanan, Rami Yushuvaev, Ramiz Manked, ramonopoly, Riad Benguella, Rinat Khaziev, Robert Anderson, Rudy Susanto, Ryan Boren, Ryan Welcher, Sébastien SERRE, Saeed Fard, Sal Ferrarello, Salar Gholizadeh, Samaneh Mirrajabi, Sami Keijonen, Samuel Elh, Santiago Garza, Sara Cope, saracup, sarah semark, Scott Arciszewski, Scott Reilly, Sebastian Pisula, Sekineh Ebrahimzadeh, Sergey Biryukov, SergioEstevao, sgastard, sharifkiberu, Shashank Panchal, shazdeh, Shital Marakana, sky_76, Soren Wrede, Stephen Edgar, Steven Word, Subrata Sarkar, Sudar Muthu, Sudhir Yadav, szepe.viktor, Takayuki Miyauchi, Tammie Lister, Themonic, thomstark, Thorsten Frommen, Thrijith Thankachan, Tim Hedgefield, Tim Wright, Timothy Jacobs, timph, tmatsuur, tmdesigned, tmdesigned, Tobias Zimpel, TobiasBg, TomHarrigan, tonybogdanov, Tor-Bjorn Fjellner, Toro_Unit (Hiroshi Urabe), torres126, Torsten Landsiedel, Towhidul Islam, Tracy Levesque, Umang Bhanvadia, Vaishali Panchal, vrimill, WebFactory, Weston Ruter, WFMattR, William \'Bahia\' Bay, William Earnhardt, williampatton, Willscrlt, Wolly aka Paolo Valenti, wrwrwr0, Yoav Farhi, Yui, Zebulan Stanphill, and Česlav Przywara.\n\n\n\n
\n\n\n\n

Also, many thanks to all of the community volunteers who contribute in the support forums. They answer questions from people across the world, whether they are using WordPress for the first time or since the first release. These releases are more successful for their efforts!

\n\n\n\n

If you want learn more about volunteering with WordPress, check out Make WordPress or the core development blog.

\n\n\n\n

Thanks for choosing WordPress!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6925\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:17:\"WordPress 5.2 RC2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:53:\"https://wordpress.org/news/2019/05/wordpress-5-2-rc2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 May 2019 16:17:59 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6914\";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:326:\"The second release candidate for WordPress 5.2 is now available! WordPress 5.2 will be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time! There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s: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:2472:\"\n

The second release candidate for WordPress 5.2 is now available!

\n\n\n\n

WordPress 5.2 will be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time!

\n\n\n\n

There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).

\n\n\n\n

For details about what to expect in WordPress 5.2, please see the first release candidate post.

\n\n\n\n

This release includes the final About page design. It also contains fixes for:

\n\n\n\n\n\n\n\n

Plugin and Theme Developers

\n\n\n\n

Please test your plugins and themes against WordPress 5.2 and update the Tested up to version in the readme to 5.2. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.

\n\n\n\n

The WordPress 5.2 Field Guide has also been published, which details the major changes.

\n\n\n\n

How to Help

\n\n\n\n

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

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

It’s the start of May
and the release is coming.
We all give a cheer!

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6914\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:6;a:6:{s:4:\"data\";s:48:\"\n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"The Month in WordPress: April 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2019/05/the-month-in-wordpress-april-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 02 May 2019 09:00:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6918\";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:324:\"This past month has been filled with anticipation as the community builds up towards a big new release, plans some important events, and builds new tools to grow the future of the project. WordPress 5.2 Almost Due for Release WordPress 5.2 is due for release on May 7 with many new features included for developers […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Hugh Lashbrooke\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:8386:\"\n

This past month has been filled with anticipation as the community builds up towards a big new release, plans some important events, and builds new tools to grow the future of the project.

\n\n\n\n
\n\n\n\n

WordPress 5.2 Almost Due for Release

\n\n\n\n

WordPress 5.2 is due for release on May 7 with many new features included for developers and end-users alike. The Field Guide for the release provides a lot of information about what is in it and what you can expect, including a few key elements:

\n\n\n\n

Site Health Check

\n\n\n\n

One of the most highly anticipated features for v5.2 is the Site Health Check. This feature adds two new pages in the admin interface to help end users maintain a healthy site through common configuration issues and other elements that go along with having a robust online presence. It also provides a standardized location for developers to add debugging information.

\n\n\n\n

Fatal Error Recovery Mode

\n\n\n\n

The Fatal Error Recovery Mode feature was originally planned for the 5.1 release but was delayed to patch up some last-minute issues that arose. This feature will help site-owners recover more quickly from fatal errors that break the display or functionality of their site that would ordinarily require code or database edits to fix.

\n\n\n\n

Privacy and Accessibility Updates

\n\n\n\n

Along with the headlining features mentioned above, there are some important enhancements to the privacy and accessibility features included in Core. These include some important developer-focused changes to how privacy policy pages are displayed and user data is exported, as well as moving to more semantic markup for admin tabs and other improvements such as switching post format icons to drop-down menus on post list tables, improved admin toolbar markup, and contextual improvements to archive widget drop-down menu.

\n\n\n\n

New Dashicons

\n\n\n\n

The Dashicons library was last updated was over 3 years ago. Now, in the upcoming release, a set of 13 new icons will be added to the library along with improvements to the build process and file format of the icons.

\n\n\n\n

Block Editor Upgrades

\n\n\n\n

The Block Editor has seen numerous improvements lately that will all be included in the v5.2 release. Along with the interface upgrades, the underlying Javascript module has been reorganized, improvements have been made to how the block editor is detected on the post edit screen, and the Javascript build process has been enhanced.

\n\n\n\n

WordPress 5.2 is now in the Release Candidate phase and you can test it by installing the Beta Tester plugin on any WordPress site.

\n\n\n\n

Want to get involved in building WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group.

\n\n\n\n

WordPress Translation Day 4 is Almost Here

\n\n\n\n

On 11 May 2019, the fourth WordPress Translation Day will take place. This is a 24-hour global event dedicated to the translation of all things WordPress, from Core to themes, plugins to marketing.

\n\n\n\n

Over the course of 24 hours, WordPress communities will meet to translate WordPress into their local languages and watch talks and sessions broadcast on wptranslationday.org. During the previous WordPress Translation Day, 71 local events took place in 29 countries, and even more communities are expected to take part this time.

\n\n\n\n

Want to get involved in WordPress Translation Day 4? Find out how to organize a local event, follow the updates on the Polyglots team blog, and join the #polyglots channel in the Making WordPress Slack group.

\n\n\n\n

Block Library Project Gets Started

\n\n\n\n

Since the initial proposal for a Block Library that would be made available from inside the block editor, work has been done to put together some designs for how this would look. Since then the project has received a more direct focus with a planned out scope and timeline.

\n\n\n\n

The project is being managed on GitHub and people interested in contributing are encouraged to get involved there. You can also keep up to date by following the Design team blog and joining the #design channel in the Making WordPress Slack group.

\n\n\n\n
\n\n\n\n

Further Reading:

\n\n\n\n\n\n\n\n

Have a story that we should include in the next “Month in WordPress” post? Please submit it here.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6918\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"WordPress 5.2 Release Candidate\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/04/wordpress-5-2-release-candidate/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 26 Apr 2019 01:28:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6909\";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:364:\"The first release candidate for WordPress 5.2 is now available! This is an important milestone as we progress toward the WordPress 5.2 release date. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.2 is scheduled to […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s: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:3117:\"\n

The first release candidate for WordPress 5.2 is now available!

\n\n\n\n

This is an important milestone as we progress toward the WordPress 5.2 release date. “Release Candidate” means that the new version is ready for release, but with millions of users and thousands of plugins and themes, it’s possible something was missed. WordPress 5.2 is scheduled to be released on Tuesday, May 7, but we need your help to get there—if you haven’t tried 5.2 yet, now is the time!

\n\n\n\n

There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the release candidate here (zip).

\n\n\n\n

What’s in WordPress 5.2?

\n\n\n\n

Continuing with the theme from the last release, WordPress 5.2 gives you even more robust tools for identifying and fixing configuration issues and fatal errors. Whether you are a developer helping clients or you manage your site solo, these tools can help get you the right information when you need it.

\n\n\n\n

The Site Health Check and PHP Error Protection tools have brand new features, giving you peace of mind if you discover any issues with plugins or themes on your site. There are also updates to the icons available in your dashboard, fresh accessibility considerations for anyone using assistive technologies and more.

\n\n\n\n

Plugin and Theme Developers

\n\n\n\n

Please test your plugins and themes against WordPress 5.2 and update the Tested up to version in the readme to 5.2. If you find compatibility problems, please be sure to post to the support forums so we can figure those out before the final release.

\n\n\n\n

The WordPress 5.2 Field Guide has also been published, which goes into the details of the major changes.

\n\n\n\n

How to Help

\n\n\n\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! This release also marks the hard string freeze point of the 5.2 release schedule.

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

Howdy, RC 1!
With tools this interesting,
I can hardly wait.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6909\";s: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:51:\"\n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.2 Beta 3\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2019/04/wordpress-5-2-beta-3/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 12 Apr 2019 21:33:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=6885\";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:316:\"WordPress 5.2 Beta 3 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. There are two ways to test the latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:19:\"Jonathan Desrosiers\";s: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:4391:\"\n

WordPress 5.2 Beta 3 is now available!

\n\n\n\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

\n\n\n\n

There are two ways to test the latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

\n\n\n\n

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 2, nearly 40 tickets have been closed since then. Here are the major changes and bug fixes:

\n\n\n\n\n\n\n\n

Minimum PHP Version Update

\n\n\n\n

Important reminder: as of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

\n\n\n\n
\n\n\n\n

Developer Notes

\n\n\n\n

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

\n\n\n\n

How to Help

\n\n\n\n

Do you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 3 release also marks the soft string freeze point of the 5.2 release schedule.

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

Would you look at that
each day brings release closer
test to be ready
.

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6885\";s: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:54:\"\n \n \n \n \n \n \n \n\n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.2 Beta 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2019/04/wordpress-5-2-beta-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 09 Apr 2019 01:27: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:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:11:\"Development\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:2;a:5:{s:4:\"data\";s:3:\"5.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:34:\"https://wordpress.org/news/?p=6874\";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:312:\"WordPress 5.2 Beta 2 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version. There are two ways to test the WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Gary Pendergast\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:4565:\"\n

WordPress 5.2 Beta 2 is now available!

\n\n\n\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.

\n\n\n\n

There are two ways to test the WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).

\n\n\n\n

WordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 1, nearly 100 tickets have been closed since then. Here are the major changes and bug fixes:

\n\n\n\n\n\n\n\n

Minimum PHP Version Update

\n\n\n\n

As of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.

\n\n\n\n
\n\n\n\n

Developer Notes

\n\n\n\n

WordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.

\n\n\n\n

How to Help

\n\n\n\n

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

\n\n\n\n

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

\n\n\n\n
\n\n\n\n

The wonderful thing
about betas, is betas
are wonderful things.
\"?\"

\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:7:\"post-id\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"6874\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n 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:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Wed, 19 Jun 2019 00:36:16 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, 18 Jun 2019 19:42:02 GMT\";s:4:\"link\";s:63:\"; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20130911073210\";}','no'),(273,'_site_transient_update_plugins','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1560905513;s:7:\"checked\";a:5:{s:19:\"akismet/akismet.php\";s:5:\"4.1.2\";s:33:\"classic-editor/classic-editor.php\";s:3:\"1.5\";s:51:\"featured-image-from-url/featured-image-from-url.php\";s:5:\"2.5.0\";s:9:\"hello.php\";s:5:\"1.7.2\";s:42:\"wordpress-seo-premium-1/wp-seo-premium.php\";s:6:\"10.1.1\";}s:8:\"response\";a:1:{s:51:\"featured-image-from-url/featured-image-from-url.php\";O:8:\"stdClass\":13:{s:2:\"id\";s:37:\"w.org/plugins/featured-image-from-url\";s:4:\"slug\";s:23:\"featured-image-from-url\";s:6:\"plugin\";s:51:\"featured-image-from-url/featured-image-from-url.php\";s:11:\"new_version\";s:5:\"2.5.1\";s:3:\"url\";s:54:\"https://wordpress.org/plugins/featured-image-from-url/\";s:7:\"package\";s:66:\"https://downloads.wordpress.org/plugin/featured-image-from-url.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:76:\"https://ps.w.org/featured-image-from-url/assets/icon-256x256.png?rev=1694895\";s:2:\"1x\";s:76:\"https://ps.w.org/featured-image-from-url/assets/icon-128x128.png?rev=1694895\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:79:\"https://ps.w.org/featured-image-from-url/assets/banner-1544x500.png?rev=1694895\";s:2:\"1x\";s:78:\"https://ps.w.org/featured-image-from-url/assets/banner-772x250.png?rev=1694895\";}s:11:\"banners_rtl\";a:0:{}s:14:\"upgrade_notice\";s:55:\"
    \n
  • New feature: save image dimensions.
  • \n
\";s:6:\"tested\";s:5:\"5.2.2\";s:12:\"requires_php\";b:0;s:13:\"compatibility\";O:8:\"stdClass\":0:{}}}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:3:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.1.2\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.1.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}}s:33:\"classic-editor/classic-editor.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:28:\"w.org/plugins/classic-editor\";s:4:\"slug\";s:14:\"classic-editor\";s:6:\"plugin\";s:33:\"classic-editor/classic-editor.php\";s:11:\"new_version\";s:3:\"1.5\";s:3:\"url\";s:45:\"https://wordpress.org/plugins/classic-editor/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/plugin/classic-editor.1.5.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:67:\"https://ps.w.org/classic-editor/assets/icon-256x256.png?rev=1998671\";s:2:\"1x\";s:67:\"https://ps.w.org/classic-editor/assets/icon-128x128.png?rev=1998671\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:70:\"https://ps.w.org/classic-editor/assets/banner-1544x500.png?rev=1998671\";s:2:\"1x\";s:69:\"https://ps.w.org/classic-editor/assets/banner-772x250.png?rev=1998676\";}s:11:\"banners_rtl\";a:0:{}}s:9:\"hello.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:5:\"1.7.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855\";s:2:\"1x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:66:\"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855\";}s:11:\"banners_rtl\";a:0:{}}}}','no'),(251,'auto_core_update_notified','a:4:{s:4:\"type\";s:7:\"success\";s:5:\"email\";s:20:\"admin@wordpressed.ml\";s:7:\"version\";s:5:\"5.2.2\";s:9:\"timestamp\";i:1560904066;}','no'),(195,'fifu_social','toggleoff','yes'),(196,'fifu_original','toggleoff','yes'),(197,'fifu_lazy','toggleoff','yes'),(198,'fifu_content','toggleoff','yes'),(199,'fifu_content_page','toggleoff','yes'),(200,'fifu_enable_default_url','toggleoff','yes'),(201,'fifu_fake','toggleoff','yes'),(202,'fifu_fake2','toggleon','yes'),(203,'fifu_css','','yes'),(204,'fifu_default_url','','yes'),(205,'fifu_wc_lbox','toggleon','yes'),(206,'fifu_wc_zoom','toggleon','yes'),(207,'fifu_hide_page','toggleoff','yes'),(208,'fifu_hide_post','toggleoff','yes'),(209,'fifu_get_first','toggleoff','yes'),(210,'fifu_pop_first','toggleoff','yes'),(211,'fifu_ovw_first','toggleoff','yes'),(212,'fifu_column_height','64','no'),(213,'fifu_priority','toggleoff','yes'),(214,'fifu_grid_category','toggleoff','yes'),(215,'fifu_auto_alt','toggleon','yes'),(216,'fifu_data_generation','toggleoff','yes'),(217,'fifu_data_clean','toggleoff','no'),(218,'fifu_image_height_shop','','no'),(219,'fifu_image_width_shop','','no'),(220,'fifu_image_height_prod','','no'),(221,'fifu_image_width_prod','','no'),(222,'fifu_image_height_cart','','no'),(223,'fifu_image_width_cart','','no'),(224,'fifu_image_height_ctgr','','no'),(225,'fifu_image_width_ctgr','','no'),(226,'fifu_image_height_arch','','no'),(227,'fifu_image_width_arch','','no'),(228,'fifu_image_height_home','','no'),(229,'fifu_image_width_home','','no'),(230,'fifu_image_height_page','','no'),(231,'fifu_image_width_page','','no'),(232,'fifu_image_height_post','','no'),(233,'fifu_image_width_post','','no'),(256,'_site_transient_timeout_community-events-e151b4de1b48516b09bec68ad6fbd41b','1560947776','no'),(252,'_site_transient_timeout_browser_fd1885f00291b83c2cb49a9bbb9a909a','1561509374','no'),(136,'recovery_keys','a:0:{}','yes'),(139,'current_theme','Ribosome','yes'),(140,'theme_mods_ribosome','a:3:{i:0;b:0;s:18:\"nav_menu_locations\";a:0:{}s:18:\"custom_css_post_id\";i:-1;}','yes'),(141,'theme_switched','','yes'),(249,'_site_transient_update_core','O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.2.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.2.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.2.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.2.2-new-bundled.zip\";s:7:\"partial\";b:0;s:8:\"rollback\";b:0;}s:7:\"current\";s:5:\"5.2.2\";s:7:\"version\";s:5:\"5.2.2\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.0\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1560905506;s:15:\"version_checked\";s:5:\"5.2.2\";s:12:\"translations\";a:0:{}}','no'),(276,'wpseo_social','a:20:{s:13:\"facebook_site\";s:0:\"\";s:13:\"instagram_url\";s:0:\"\";s:12:\"linkedin_url\";s:0:\"\";s:11:\"myspace_url\";s:0:\"\";s:16:\"og_default_image\";s:0:\"\";s:19:\"og_default_image_id\";s:0:\"\";s:18:\"og_frontpage_title\";s:0:\"\";s:17:\"og_frontpage_desc\";s:0:\"\";s:18:\"og_frontpage_image\";s:0:\"\";s:21:\"og_frontpage_image_id\";s:0:\"\";s:9:\"opengraph\";b:1;s:13:\"pinterest_url\";s:0:\"\";s:15:\"pinterestverify\";s:0:\"\";s:14:\"plus-publisher\";s:0:\"\";s:7:\"twitter\";b:1;s:12:\"twitter_site\";s:0:\"\";s:17:\"twitter_card_type\";s:19:\"summary_large_image\";s:11:\"youtube_url\";s:0:\"\";s:13:\"wikipedia_url\";s:0:\"\";s:10:\"fbadminapp\";s:0:\"\";}','yes'),(277,'wpseo_flush_rewrite','1','yes'),(292,'wpseo-premium-redirects-base','a:1:{i:0;a:4:{s:6:\"origin\";s:4:\"adcd\";s:3:\"url\";s:4:\"efgh\";s:4:\"type\";i:301;s:6:\"format\";s:5:\"plain\";}}','no'),(293,'wpseo-premium-redirects-export-plain','a:1:{s:4:\"adcd\";a:2:{s:3:\"url\";s:4:\"efgh\";s:4:\"type\";i:301;}}','no'),(294,'wpseo-premium-redirects-export-regex','a:0:{}','no'); /*!40000 ALTER TABLE `wpwb_options` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_postmeta` -- DROP TABLE IF EXISTS `wpwb_postmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=42 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_postmeta` -- LOCK TABLES `wpwb_postmeta` WRITE; /*!40000 ALTER TABLE `wpwb_postmeta` DISABLE KEYS */; INSERT INTO `wpwb_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'),(20,13,'_edit_last','1'),(4,6,'_edit_last','1'),(5,6,'_edit_lock','1559109240:1'),(6,7,'_wp_attached_file','2019/05/bk.jpg'),(7,7,'_wp_attachment_metadata','a:5:{s:5:\"width\";i:474;s:6:\"height\";i:843;s:4:\"file\";s:14:\"2019/05/bk.jpg\";s:5:\"sizes\";a:7:{s:9:\"thumbnail\";a:4:{s:4:\"file\";s:14:\"bk-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:6:\"medium\";a:4:{s:4:\"file\";s:14:\"bk-169x300.jpg\";s:5:\"width\";i:169;s:6:\"height\";i:300;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:26:\"ribosome-excerpt-thumbnail\";a:4:{s:4:\"file\";s:14:\"bk-240x180.jpg\";s:5:\"width\";i:240;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:34:\"ribosome-excerpt-thumbnail-rounded\";a:4:{s:4:\"file\";s:14:\"bk-180x180.jpg\";s:5:\"width\";i:180;s:6:\"height\";i:180;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:31:\"ribosome-recent-posts-thumbnail\";a:4:{s:4:\"file\";s:12:\"bk-60x60.jpg\";s:5:\"width\";i:60;s:6:\"height\";i:60;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:31:\"ribosome-related-post-thumbnail\";a:4:{s:4:\"file\";s:14:\"bk-150x150.jpg\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:10:\"image/jpeg\";}s:28:\"ribosome-slider-recent-posts\";a:4:{s:4:\"file\";s:14:\"bk-474x390.jpg\";s:5:\"width\";i:474;s:6:\"height\";i:390;s:9:\"mime-type\";s:10:\"image/jpeg\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(8,6,'_thumbnail_id','7'),(11,1,'_wp_trash_meta_status','publish'),(12,1,'_wp_trash_meta_time','1559109388'),(13,1,'_wp_desired_post_slug','hello-world'),(14,1,'_wp_trash_meta_comments_status','a:1:{i:1;s:1:\"1\";}'),(15,10,'_edit_last','1'),(16,10,'_edit_lock','1559109289:1'),(17,10,'_thumbnail_id','7'),(21,13,'_edit_lock','1559986335:1'),(34,19,'_edit_lock','1559987194:2'),(24,13,'fifu_image_url','https://i.ibb.co/CHZsMS1/Ashes-Cricket-2013-Box-Art.jpg'),(25,13,'fifu_image_alt','Featured Image'),(35,19,'_edit_last','2'),(39,23,'_wp_attachment_context','upgrader'),(38,23,'_wp_attached_file','2019/06/wordpress-seo-premium.zip'),(31,13,'_thumbnail_id','17'),(32,17,'_wp_attached_file',';https://i.ibb.co/CHZsMS1/Ashes-Cricket-2013-Box-Art.jpg'),(33,17,'_wp_attachment_image_alt','Featured Image'); /*!40000 ALTER TABLE `wpwb_postmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_posts` -- DROP TABLE IF EXISTS `wpwb_posts`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_posts` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_author` bigint(20) unsigned NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_title` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_excerpt` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `to_ping` text COLLATE utf8mb4_unicode_ci NOT NULL, `pinged` text COLLATE utf8mb4_unicode_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `guid` varchar(2048) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`ID`), KEY `post_name` (`post_name`(191)), KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), KEY `post_parent` (`post_parent`), KEY `post_author` (`post_author`) ) ENGINE=MyISAM AUTO_INCREMENT=25 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_posts` -- LOCK TABLES `wpwb_posts` WRITE; /*!40000 ALTER TABLE `wpwb_posts` DISABLE KEYS */; INSERT INTO `wpwb_posts` VALUES (1,1,'2019-05-29 05:52:34','2019-05-29 05:52:34','\n

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

\n','Hello world!','','trash','open','open','','hello-world__trashed','','','2019-05-29 05:56:28','2019-05-29 05:56:28','',0,'http://wordpressed.ml/?p=1',0,'post','',1),(2,1,'2019-05-29 05:52:34','2019-05-29 05:52:34','\n

This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:

\n\n\n\n

Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)

\n\n\n\n

...or something like this:

\n\n\n\n

The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.

\n\n\n\n

As a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!

\n','Sample Page','','publish','closed','open','','sample-page','','','2019-05-29 05:52:34','2019-05-29 05:52:34','',0,'http://wordpressed.ml/?page_id=2',0,'page','',0),(3,1,'2019-05-29 05:52:34','2019-05-29 05:52:34','

Who we are

Our website address is: http://wordpressed.ml.

What personal data we collect and why we collect it

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Contact forms

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Analytics

Who we share your data with

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

Additional information

How we protect your data

What data breach procedures we have in place

What third parties we receive data from

What automated decision making and/or profiling we do with user data

Industry regulatory disclosure requirements

','Privacy Policy','','draft','closed','open','','privacy-policy','','','2019-05-29 05:52:34','2019-05-29 05:52:34','',0,'http://wordpressed.ml/?page_id=3',0,'page','',0),(6,1,'2019-05-29 05:56:00','2019-05-29 05:56:00','First Post This Is\r\n\r\n\"\"','Firts Post','','publish','open','open','','firts-post','','','2019-05-29 05:56:00','2019-05-29 05:56:00','',0,'http://wordpressed.ml/?p=6',0,'post','',0),(7,1,'2019-05-29 05:55:47','2019-05-29 05:55:47','','bk','','inherit','open','closed','','bk','','','2019-05-29 05:55:47','2019-05-29 05:55:47','',6,'http://wordpressed.ml/wp-content/uploads/2019/05/bk.jpg',0,'attachment','image/jpeg',0),(8,1,'2019-05-29 05:56:00','2019-05-29 05:56:00','First Post This Is\r\n\r\n\"\"','Firts Post','','inherit','closed','closed','','6-revision-v1','','','2019-05-29 05:56:00','2019-05-29 05:56:00','',6,'http://wordpressed.ml/6-revision-v1/',0,'revision','',0),(9,1,'2019-05-29 05:56:28','2019-05-29 05:56:28','\n

Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

\n','Hello world!','','inherit','closed','closed','','1-revision-v1','','','2019-05-29 05:56:28','2019-05-29 05:56:28','',1,'http://wordpressed.ml/1-revision-v1/',0,'revision','',0),(10,1,'2019-05-29 05:57:05','2019-05-29 05:57:05','This Is Second Post\r\n\r\n\"\"','Second Post','','publish','open','open','','second-post','','','2019-05-29 05:57:05','2019-05-29 05:57:05','',0,'http://wordpressed.ml/?p=10',0,'post','',0),(11,1,'2019-05-29 05:57:05','2019-05-29 05:57:05','This Is Second Post\r\n\r\n\"\"','Second Post','','inherit','closed','closed','','10-revision-v1','','','2019-05-29 05:57:05','2019-05-29 05:57:05','',10,'http://wordpressed.ml/10-revision-v1/',0,'revision','',0),(13,1,'2019-06-08 09:32:47','2019-06-08 09:32:47','Hii','Featured Image','','publish','open','open','','featured-image','','','2019-06-08 09:34:27','2019-06-08 09:34:27','',0,'http://wordpressed.ml/?p=13',0,'post','',0),(15,1,'2019-06-08 09:32:47','2019-06-08 09:32:47','Hii','Featured Image','','inherit','closed','closed','','13-revision-v1','','','2019-06-08 09:32:47','2019-06-08 09:32:47','',13,'http://wordpressed.ml/13-revision-v1/',0,'revision','',0),(23,1,'2019-06-19 00:51:10','2019-06-19 00:51:10','http://wordpressed.ml/wp-content/uploads/2019/06/wordpress-seo-premium.zip','wordpress-seo-premium.zip','','private','open','closed','','wordpress-seo-premium-zip','','','2019-06-19 00:51:10','2019-06-19 00:51:10','',0,'http://wordpressed.ml/wp-content/uploads/2019/06/wordpress-seo-premium.zip',0,'attachment','',0),(19,2,'2019-06-08 09:48:29','2019-06-08 09:48:29','hi','admin1','','publish','open','open','','admin1','','','2019-06-08 09:48:29','2019-06-08 09:48:29','',0,'http://wordpressed.ml/?p=19',0,'post','',0),(17,77777,'2019-06-08 11:34:27','2019-06-08 11:34:27','','Featured Image','','inherit','open','open','','','','','2019-06-08 11:34:27','2019-06-08 11:34:27','',13,'https://i.ibb.co/CHZsMS1/Ashes-Cricket-2013-Box-Art.jpg',0,'attachment','image/jpeg',0),(22,1,'2019-06-19 00:36:15','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2019-06-19 00:36:15','0000-00-00 00:00:00','',0,'http://wordpressed.ml/?p=22',0,'post','',0),(21,2,'2019-06-08 09:48:29','2019-06-08 09:48:29','hi','admin1','','inherit','closed','closed','','19-revision-v1','','','2019-06-08 09:48:29','2019-06-08 09:48:29','',19,'http://wordpressed.ml/19-revision-v1/',0,'revision','',0); /*!40000 ALTER TABLE `wpwb_posts` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_term_relationships` -- DROP TABLE IF EXISTS `wpwb_term_relationships`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_term_relationships` ( `object_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) unsigned NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`object_id`,`term_taxonomy_id`), KEY `term_taxonomy_id` (`term_taxonomy_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_term_relationships` -- LOCK TABLES `wpwb_term_relationships` WRITE; /*!40000 ALTER TABLE `wpwb_term_relationships` DISABLE KEYS */; INSERT INTO `wpwb_term_relationships` VALUES (1,1,0),(6,3,0),(6,2,0),(10,5,0),(10,4,0),(13,1,0),(19,1,0); /*!40000 ALTER TABLE `wpwb_term_relationships` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_term_taxonomy` -- DROP TABLE IF EXISTS `wpwb_term_taxonomy`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_term_taxonomy` ( `term_taxonomy_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `parent` bigint(20) unsigned NOT NULL DEFAULT '0', `count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`term_taxonomy_id`), UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), KEY `taxonomy` (`taxonomy`) ) ENGINE=MyISAM AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_term_taxonomy` -- LOCK TABLES `wpwb_term_taxonomy` WRITE; /*!40000 ALTER TABLE `wpwb_term_taxonomy` DISABLE KEYS */; INSERT INTO `wpwb_term_taxonomy` VALUES (1,1,'category','',0,2),(2,2,'category','',0,1),(3,3,'post_tag','',0,1),(4,4,'category','',0,1),(5,5,'post_tag','',0,1); /*!40000 ALTER TABLE `wpwb_term_taxonomy` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_termmeta` -- DROP TABLE IF EXISTS `wpwb_termmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_termmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`meta_id`), KEY `term_id` (`term_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_termmeta` -- LOCK TABLES `wpwb_termmeta` WRITE; /*!40000 ALTER TABLE `wpwb_termmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wpwb_termmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_terms` -- DROP TABLE IF EXISTS `wpwb_terms`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_terms` ( `term_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0', PRIMARY KEY (`term_id`), KEY `slug` (`slug`(191)), KEY `name` (`name`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_terms` -- LOCK TABLES `wpwb_terms` WRITE; /*!40000 ALTER TABLE `wpwb_terms` DISABLE KEYS */; INSERT INTO `wpwb_terms` VALUES (1,'Uncategorized','uncategorized',0),(2,'First','first',0),(3,'First Tag','first-tag',0),(4,'Second','second',0),(5,'Second Tag','second-tag',0); /*!40000 ALTER TABLE `wpwb_terms` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_usermeta` -- DROP TABLE IF EXISTS `wpwb_usermeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_usermeta` ( `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`umeta_id`), KEY `user_id` (`user_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=39 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_usermeta` -- LOCK TABLES `wpwb_usermeta` WRITE; /*!40000 ALTER TABLE `wpwb_usermeta` DISABLE KEYS */; INSERT INTO `wpwb_usermeta` VALUES (1,1,'nickname','admin'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wpwb_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wpwb_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','1'),(16,1,'session_tokens','a:1:{s:64:\"d61775be1cccd99f3d0027ef1628716cde328b4fcad6019f26e0b9d831e3b9ab\";a:4:{s:10:\"expiration\";i:1562114173;s:2:\"ip\";s:14:\"172.68.182.224\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36\";s:5:\"login\";i:1560904573;}}'),(17,1,'wpwb_dashboard_quick_press_last_post_id','22'),(18,1,'community-events-location','a:1:{s:2:\"ip\";s:11:\"95.216.96.0\";}'),(19,1,'wpwb_user-settings','libraryContent=browse'),(20,1,'wpwb_user-settings-time','1559109356'),(35,2,'session_tokens','a:1:{s:64:\"0f6329ea5fccfbee2c5c65e7a314b1efcfc011b1303860faff05ada2a9e62ebc\";a:4:{s:10:\"expiration\";i:1561196872;s:2:\"ip\";s:15:\"162.158.183.117\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36\";s:5:\"login\";i:1559987272;}}'),(21,2,'nickname','admin1'),(22,2,'first_name','admin1_first'),(23,2,'last_name',''),(24,2,'description',''),(25,2,'rich_editing','true'),(26,2,'syntax_highlighting','true'),(27,2,'comment_shortcuts','false'),(28,2,'admin_color','fresh'),(29,2,'use_ssl','0'),(30,2,'show_admin_bar_front','true'),(31,2,'locale',''),(32,2,'wpwb_capabilities','a:1:{s:6:\"author\";b:1;}'),(33,2,'wpwb_user_level','2'),(34,2,'dismissed_wp_pointers',''),(36,2,'wpwb_dashboard_quick_press_last_post_id','18'),(37,2,'community-events-location','a:1:{s:2:\"ip\";s:11:\"95.216.96.0\";}'),(38,1,'wpwb_yoast_notifications','a:2:{i:0;a:2:{s:7:\"message\";s:165:\"Don\'t miss your crawl errors: connect with Google Search Console here.\";s:7:\"options\";a:9:{s:4:\"type\";s:7:\"warning\";s:2:\"id\";s:17:\"wpseo-dismiss-gsc\";s:5:\"nonce\";N;s:8:\"priority\";d:0.5;s:9:\"data_json\";a:0:{}s:13:\"dismissal_key\";N;s:12:\"capabilities\";s:20:\"wpseo_manage_options\";s:16:\"capability_check\";s:3:\"all\";s:14:\"yoast_branding\";b:0;}}i:1;a:2:{s:7:\"message\";s:293:\"You are not receiving updates or support! Fix this problem by adding this site and enabling Yoast SEO Premium for it in My Yoast.\";s:7:\"options\";a:9:{s:4:\"type\";s:5:\"error\";s:2:\"id\";s:31:\"wpseo-dismiss-yoast-seo-premium\";s:5:\"nonce\";N;s:8:\"priority\";d:0.5;s:9:\"data_json\";a:0:{}s:13:\"dismissal_key\";N;s:12:\"capabilities\";s:20:\"wpseo_manage_options\";s:16:\"capability_check\";s:3:\"all\";s:14:\"yoast_branding\";b:0;}}}'); /*!40000 ALTER TABLE `wpwb_usermeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_users` -- DROP TABLE IF EXISTS `wpwb_users`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_users` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_login` varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_pass` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_nicename` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_url` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT '0', `display_name` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', PRIMARY KEY (`ID`), KEY `user_login_key` (`user_login`), KEY `user_nicename` (`user_nicename`), KEY `user_email` (`user_email`) ) ENGINE=MyISAM AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_users` -- LOCK TABLES `wpwb_users` WRITE; /*!40000 ALTER TABLE `wpwb_users` DISABLE KEYS */; INSERT INTO `wpwb_users` VALUES (1,'admin','$P$B.xCcgcxx6Nt7uXWw8BaoS2m21/DGL.','admin','admin@wordpressed.ml','','2019-05-29 05:52:34','',0,'admin'),(2,'admin1','$P$BnQKAiwMqE29AVdyFSEjBwT7KHILia0','admin1','admin1@adminadmin.org','','2019-06-08 09:47:29','',0,'admin1_first'); /*!40000 ALTER TABLE `wpwb_users` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_yoast_seo_links` -- DROP TABLE IF EXISTS `wpwb_yoast_seo_links`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_yoast_seo_links` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_id` bigint(20) unsigned NOT NULL, `target_post_id` bigint(20) unsigned NOT NULL, `type` varchar(8) COLLATE utf8mb4_unicode_520_ci NOT NULL, PRIMARY KEY (`id`), KEY `link_direction` (`post_id`,`type`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_yoast_seo_links` -- LOCK TABLES `wpwb_yoast_seo_links` WRITE; /*!40000 ALTER TABLE `wpwb_yoast_seo_links` DISABLE KEYS */; /*!40000 ALTER TABLE `wpwb_yoast_seo_links` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wpwb_yoast_seo_meta` -- DROP TABLE IF EXISTS `wpwb_yoast_seo_meta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wpwb_yoast_seo_meta` ( `object_id` bigint(20) unsigned NOT NULL, `internal_link_count` int(10) unsigned DEFAULT NULL, `incoming_link_count` int(10) unsigned DEFAULT NULL, UNIQUE KEY `object_id` (`object_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wpwb_yoast_seo_meta` -- LOCK TABLES `wpwb_yoast_seo_meta` WRITE; /*!40000 ALTER TABLE `wpwb_yoast_seo_meta` DISABLE KEYS */; /*!40000 ALTER TABLE `wpwb_yoast_seo_meta` ENABLE KEYS */; UNLOCK TABLES; -- -- Dumping events for database 'groot_wbc' -- -- -- Dumping routines for database 'groot_wbc' -- /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2019-08-17 4:08:26