-- MySQL dump 10.16 Distrib 10.2.33-MariaDB, for Linux (x86_64) -- -- Host: localhost Database: techtr18_wpcable -- ------------------------------------------------------ -- Server version 10.2.33-MariaDB-log /*!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 utf8mb4 */; /*!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: `techtr18_wpcable` -- -- -- Table structure for table `wp3v_commentmeta` -- DROP TABLE IF EXISTS `wp3v_commentmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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 DEFAULT NULL, 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 `wp3v_commentmeta` -- LOCK TABLES `wp3v_commentmeta` WRITE; /*!40000 ALTER TABLE `wp3v_commentmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wp3v_commentmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_comments` -- DROP TABLE IF EXISTS `wp3v_comments`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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', `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 `wp3v_comments` -- LOCK TABLES `wp3v_comments` WRITE; /*!40000 ALTER TABLE `wp3v_comments` DISABLE KEYS */; INSERT INTO `wp3v_comments` (`comment_ID`, `comment_post_ID`, `comment_author`, `comment_author_email`, `comment_author_url`, `comment_author_IP`, `comment_date`, `comment_date_gmt`, `comment_content`, `comment_karma`, `comment_approved`, `comment_agent`, `comment_type`, `comment_parent`, `user_id`) VALUES (1,1,'A WordPress Commenter','wapuu@wordpress.example','https://wordpress.org/','','2020-10-03 21:40:14','2020-10-03 21:40:14','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','','comment',0,0); /*!40000 ALTER TABLE `wp3v_comments` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_links` -- DROP TABLE IF EXISTS `wp3v_links`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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 `wp3v_links` -- LOCK TABLES `wp3v_links` WRITE; /*!40000 ALTER TABLE `wp3v_links` DISABLE KEYS */; /*!40000 ALTER TABLE `wp3v_links` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_options` -- DROP TABLE IF EXISTS `wp3v_options`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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`), KEY `autoload` (`autoload`) ) ENGINE=MyISAM AUTO_INCREMENT=242 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_options` -- LOCK TABLES `wp3v_options` WRITE; /*!40000 ALTER TABLE `wp3v_options` DISABLE KEYS */; INSERT INTO `wp3v_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (1,'siteurl','https://cablesoftwares.com','yes'),(2,'home','https://cablesoftwares.com','yes'),(3,'blogname','cablesoftware','yes'),(4,'blogdescription','Software and IT solutions','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','techtrivialpvtltd@gmail.com','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:137:{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:17:\"^wp-sitemap\\.xml$\";s:23:\"index.php?sitemap=index\";s:17:\"^wp-sitemap\\.xsl$\";s:36:\"index.php?sitemap-stylesheet=sitemap\";s:23:\"^wp-sitemap-index\\.xsl$\";s:34:\"index.php?sitemap-stylesheet=index\";s:48:\"^wp-sitemap-([a-z]+?)-([a-z\\d_-]+?)-(\\d+?)\\.xml$\";s:75:\"index.php?sitemap=$matches[1]&sitemap-subtype=$matches[2]&paged=$matches[3]\";s:34:\"^wp-sitemap-([a-z]+?)-(\\d+?)\\.xml$\";s:47:\"index.php?sitemap=$matches[1]&paged=$matches[2]\";s:13:\"^attribution$\";s:36:\"index.php?bg_attribution=attribution\";s:21:\"^attribution-staging$\";s:44:\"index.php?bg_attribution=attribution-staging\";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:42:\"bg_attribution/[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:52:\"bg_attribution/[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:72:\"bg_attribution/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:67:\"bg_attribution/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:67:\"bg_attribution/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:48:\"bg_attribution/[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:31:\"bg_attribution/([^/]+)/embed/?$\";s:47:\"index.php?bg_attribution=$matches[1]&embed=true\";s:35:\"bg_attribution/([^/]+)/trackback/?$\";s:41:\"index.php?bg_attribution=$matches[1]&tb=1\";s:43:\"bg_attribution/([^/]+)/page/?([0-9]{1,})/?$\";s:54:\"index.php?bg_attribution=$matches[1]&paged=$matches[2]\";s:50:\"bg_attribution/([^/]+)/comment-page-([0-9]{1,})/?$\";s:54:\"index.php?bg_attribution=$matches[1]&cpage=$matches[2]\";s:39:\"bg_attribution/([^/]+)(?:/([0-9]+))?/?$\";s:53:\"index.php?bg_attribution=$matches[1]&page=$matches[2]\";s:31:\"bg_attribution/[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:41:\"bg_attribution/[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:61:\"bg_attribution/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:56:\"bg_attribution/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:56:\"bg_attribution/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:37:\"bg_attribution/[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:55:\"bg-block-types/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?bg_block_type=$matches[1]&feed=$matches[2]\";s:50:\"bg-block-types/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:52:\"index.php?bg_block_type=$matches[1]&feed=$matches[2]\";s:31:\"bg-block-types/([^/]+)/embed/?$\";s:46:\"index.php?bg_block_type=$matches[1]&embed=true\";s:43:\"bg-block-types/([^/]+)/page/?([0-9]{1,})/?$\";s:53:\"index.php?bg_block_type=$matches[1]&paged=$matches[2]\";s:25:\"bg-block-types/([^/]+)/?$\";s:35:\"index.php?bg_block_type=$matches[1]\";s:36:\"bg-block/[^/]+/attachment/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:46:\"bg-block/[^/]+/attachment/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:66:\"bg-block/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:61:\"bg-block/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:61:\"bg-block/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:42:\"bg-block/[^/]+/attachment/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:25:\"bg-block/([^/]+)/embed/?$\";s:41:\"index.php?bg_block=$matches[1]&embed=true\";s:29:\"bg-block/([^/]+)/trackback/?$\";s:35:\"index.php?bg_block=$matches[1]&tb=1\";s:37:\"bg-block/([^/]+)/page/?([0-9]{1,})/?$\";s:48:\"index.php?bg_block=$matches[1]&paged=$matches[2]\";s:44:\"bg-block/([^/]+)/comment-page-([0-9]{1,})/?$\";s:48:\"index.php?bg_block=$matches[1]&cpage=$matches[2]\";s:33:\"bg-block/([^/]+)(?:/([0-9]+))?/?$\";s:47:\"index.php?bg_block=$matches[1]&page=$matches[2]\";s:25:\"bg-block/[^/]+/([^/]+)/?$\";s:32:\"index.php?attachment=$matches[1]\";s:35:\"bg-block/[^/]+/([^/]+)/trackback/?$\";s:37:\"index.php?attachment=$matches[1]&tb=1\";s:55:\"bg-block/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:50:\"bg-block/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$\";s:49:\"index.php?attachment=$matches[1]&feed=$matches[2]\";s:50:\"bg-block/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$\";s:50:\"index.php?attachment=$matches[1]&cpage=$matches[2]\";s:31:\"bg-block/[^/]+/([^/]+)/embed/?$\";s:43:\"index.php?attachment=$matches[1]&embed=true\";s:12:\"robots\\.txt$\";s:18:\"index.php?robots=1\";s:13:\"favicon\\.ico$\";s:19:\"index.php?favicon=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:9:{i:0;s:47:\"boldgrid-inspirations/boldgrid-inspirations.php\";i:1;s:24:\"wp-central/wpcentral.php\";i:2;s:19:\"weforms/wpforms.php\";i:3;s:19:\"jetpack/jetpack.php\";i:4;s:35:\"boldgrid-backup/boldgrid-backup.php\";i:5;s:51:\"boldgrid-backup-premium/boldgrid-backup-premium.php\";i:6;s:47:\"post-and-page-builder/post-and-page-builder.php\";i:7;s:63:\"post-and-page-builder-premium/post-and-page-builder-premium.php\";i:8;s:29:\"nginx-helper/nginx-helper.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','twentytwenty','yes'),(41,'stylesheet','twentytwenty','yes'),(42,'comment_registration','0','yes'),(43,'html_type','text/html','yes'),(44,'use_trackback','0','yes'),(45,'default_role','subscriber','yes'),(46,'db_version','48748','yes'),(47,'uploads_use_yearmonth_folders','1','yes'),(48,'upload_path','','yes'),(49,'blog_public','1','yes'),(50,'default_link_category','2','yes'),(51,'show_on_front','posts','yes'),(52,'tag_base','','yes'),(53,'show_avatars','1','yes'),(54,'avatar_rating','G','yes'),(55,'upload_url_path','','yes'),(56,'thumbnail_size_w','150','yes'),(57,'thumbnail_size_h','150','yes'),(58,'thumbnail_crop','1','yes'),(59,'medium_size_w','300','yes'),(60,'medium_size_h','300','yes'),(61,'avatar_default','mystery','yes'),(62,'large_size_w','1024','yes'),(63,'large_size_h','1024','yes'),(64,'image_default_link_type','none','yes'),(65,'image_default_size','','yes'),(66,'image_default_align','','yes'),(67,'close_comments_for_old_posts','0','yes'),(68,'close_comments_days_old','14','yes'),(69,'thread_comments','1','yes'),(70,'thread_comments_depth','5','yes'),(71,'page_comments','0','yes'),(72,'comments_per_page','50','yes'),(73,'default_comments_page','newest','yes'),(74,'comment_order','asc','yes'),(75,'sticky_posts','a:0:{}','yes'),(76,'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'),(77,'widget_text','a:3:{i:2;a:4:{s:5:\"title\";s:15:\"About This Site\";s:4:\"text\";s:85:\"This may be a good place to introduce yourself and your site or include some credits.\";s:6:\"filter\";b:1;s:6:\"visual\";b:1;}i:3;a:4:{s:5:\"title\";s:7:\"Find Us\";s:4:\"text\";s:168:\"Address\n123 Main Street\nNew York, NY 10001\n\nHours\nMonday–Friday: 9:00AM–5:00PM\nSaturday & Sunday: 11:00AM–3:00PM\";s:6:\"filter\";b:1;s:6:\"visual\";b:1;}s:12:\"_multiwidget\";i:1;}','yes'),(78,'widget_rss','a:2:{i:1;a:0:{}s:12:\"_multiwidget\";i:1;}','yes'),(79,'uninstall_plugins','a:0:{}','no'),(80,'timezone_string','','yes'),(81,'page_for_posts','0','yes'),(82,'page_on_front','0','yes'),(83,'default_post_format','0','yes'),(84,'link_manager_enabled','0','yes'),(85,'finished_splitting_shared_terms','1','yes'),(86,'site_icon','0','yes'),(87,'medium_large_size_w','768','yes'),(88,'medium_large_size_h','0','yes'),(89,'wp_page_for_privacy_policy','3','yes'),(90,'show_comments_cookies_opt_in','1','yes'),(91,'admin_email_lifespan','1617313214','yes'),(92,'disallowed_keys','','no'),(93,'comment_previously_approved','1','yes'),(94,'auto_plugin_theme_update_emails','a:0:{}','no'),(95,'initial_db_version','48748','yes'),(96,'wp3v_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'),(97,'fresh_site','1','yes'),(98,'widget_search','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(99,'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'),(100,'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'),(101,'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'),(102,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(103,'sidebars_widgets','a:4:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:3:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";}s:9:\"sidebar-2\";a:3:{i:0;s:10:\"archives-2\";i:1;s:12:\"categories-2\";i:2;s:6:\"meta-2\";}s:13:\"array_version\";i:3;}','yes'),(104,'cron','a:8:{i:1601764816;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:1601764912;a:1:{s:20:\"jetpack_clean_nonces\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1601804414;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:1601847614;a:2:{s:30:\"wp_site_health_scheduled_check\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"weekly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:604800;}}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:1601847713;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:1601847715;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:1601847904;a:1:{s:20:\"jetpack_v2_heartbeat\";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'),(105,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(106,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(107,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(108,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(109,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(110,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(111,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(112,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(113,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(115,'recovery_keys','a:0:{}','yes'),(116,'theme_mods_twentytwenty','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(117,'boldgrid_settings','a:3:{s:7:\"library\";a:3:{s:47:\"boldgrid-inspirations/boldgrid-inspirations.php\";s:8:\"2.13.2.0\";s:35:\"boldgrid-backup/boldgrid-backup.php\";s:8:\"2.13.2.0\";s:47:\"post-and-page-builder/post-and-page-builder.php\";s:8:\"2.12.3.0\";}s:15:\"plugins_checked\";a:5:{s:47:\"boldgrid-inspirations/boldgrid-inspirations.php\";a:1:{s:5:\"2.4.4\";i:1601761502;}s:47:\"post-and-page-builder/post-and-page-builder.php\";a:2:{s:6:\"1.13.0\";i:1601761311;s:6:\"1.13.4\";i:1601761502;}s:63:\"post-and-page-builder-premium/post-and-page-builder-premium.php\";a:1:{s:5:\"1.0.4\";i:1601761502;}s:35:\"boldgrid-backup/boldgrid-backup.php\";a:2:{s:6:\"1.13.3\";i:1601761311;s:6:\"1.14.5\";i:1601761502;}s:51:\"boldgrid-backup-premium/boldgrid-backup-premium.php\";a:1:{s:5:\"1.3.3\";i:1601761502;}}s:20:\"boldgrid_menu_option\";s:1:\"1\";}','yes'),(118,'wpcentral_auth_key','rv1l1perrjzkfzgrw9tlwmmhfwe21n4gchdk1nrf4rs36amtkk9roeex9piwdmcu6y8uvn5je2jc9yqvfs7gytgm6ykjvfxumlwpmerfme6l2zx2xctj6wbkhfh0vuch','yes'),(119,'wpcentral_version','1.5.3','yes'),(131,'rt_wp_nginx_helper_options','a:18:{s:9:\"log_level\";s:4:\"INFO\";s:12:\"log_filesize\";i:5;s:12:\"enable_purge\";i:1;s:10:\"enable_map\";i:0;s:10:\"enable_log\";i:0;s:12:\"enable_stamp\";i:0;s:21:\"purge_homepage_on_new\";i:1;s:22:\"purge_homepage_on_edit\";i:1;s:21:\"purge_homepage_on_del\";i:1;s:20:\"purge_archive_on_new\";i:1;s:21:\"purge_archive_on_edit\";i:1;s:20:\"purge_archive_on_del\";i:1;s:28:\"purge_archive_on_new_comment\";i:0;s:32:\"purge_archive_on_deleted_comment\";i:0;s:17:\"purge_page_on_mod\";i:1;s:25:\"purge_page_on_new_comment\";i:1;s:29:\"purge_page_on_deleted_comment\";i:1;s:12:\"purge_method\";s:11:\"get_request\";}','yes'),(121,'boldgrid_attribution_rebuild','1','yes'),(122,'boldgrid_staging_boldgrid_attribution_rebuild','1','yes'),(123,'boldgrid_attribution_upgraded_to_cpt','1','yes'),(211,'boldgrid_backup_environment','a:3:{s:8:\"hostname\";s:28:\"ecngx245.inmotionhosting.com\";s:10:\"phpversion\";s:5:\"7.4.9\";s:9:\"wpversion\";s:5:\"5.5.1\";}','yes'),(124,'_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.5.1.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.5.1.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.5.1-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.5.1-new-bundled.zip\";s:7:\"partial\";s:0:\"\";s:8:\"rollback\";s:0:\"\";}s:7:\"current\";s:5:\"5.5.1\";s:7:\"version\";s:5:\"5.5.1\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.3\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1601762287;s:15:\"version_checked\";s:5:\"5.5.1\";s:12:\"translations\";a:0:{}}','no'),(127,'_site_transient_timeout_theme_roots','1601764200','no'),(128,'_site_transient_theme_roots','a:2:{s:15:\"hello-elementor\";s:7:\"/themes\";s:12:\"twentytwenty\";s:7:\"/themes\";}','no'),(241,'_site_transient_update_themes','O:8:\"stdClass\":5:{s:12:\"last_checked\";i:1601762400;s:7:\"checked\";a:2:{s:15:\"hello-elementor\";s:5:\"2.3.0\";s:12:\"twentytwenty\";s:3:\"1.5\";}s:8:\"response\";a:0:{}s:9:\"no_update\";a:2:{s:15:\"hello-elementor\";a:6:{s:5:\"theme\";s:15:\"hello-elementor\";s:11:\"new_version\";s:5:\"2.3.0\";s:3:\"url\";s:45:\"https://wordpress.org/themes/hello-elementor/\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/theme/hello-elementor.2.3.0.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";b:0;}s:12:\"twentytwenty\";a:6:{s:5:\"theme\";s:12:\"twentytwenty\";s:11:\"new_version\";s:3:\"1.5\";s:3:\"url\";s:42:\"https://wordpress.org/themes/twentytwenty/\";s:7:\"package\";s:58:\"https://downloads.wordpress.org/theme/twentytwenty.1.5.zip\";s:8:\"requires\";s:3:\"4.7\";s:12:\"requires_php\";s:5:\"5.2.4\";}}s:12:\"translations\";a:0:{}}','no'),(240,'theme_mods_hello-elementor','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(205,'_transient_timeout_boldgrid_backup_is_functional','1601847904','no'),(206,'_transient_boldgrid_backup_is_functional','1','no'),(224,'_site_transient_boldgrid_plugins_filtered','a:5:{s:47:\"boldgrid-inspirations/boldgrid-inspirations.php\";a:13:{s:4:\"Name\";s:21:\"BoldGrid Inspirations\";s:9:\"PluginURI\";s:47:\"https://www.boldgrid.com/boldgrid-inspirations/\";s:7:\"Version\";s:5:\"2.4.4\";s:11:\"Description\";s:177:\"Find inspiration, customize, and launch! BoldGrid Inspirations includes FREE WordPress themes and is the easiest way to launch a new WordPress site complete with custom content.\";s:6:\"Author\";s:31:\"BoldGrid \";s:9:\"AuthorURI\";s:25:\"https://www.boldgrid.com/\";s:10:\"TextDomain\";s:21:\"boldgrid-inspirations\";s:10:\"DomainPath\";s:10:\"/languages\";s:7:\"Network\";b:0;s:10:\"RequiresWP\";s:0:\"\";s:11:\"RequiresPHP\";s:0:\"\";s:5:\"Title\";s:21:\"BoldGrid Inspirations\";s:10:\"AuthorName\";s:31:\"BoldGrid \";}s:47:\"post-and-page-builder/post-and-page-builder.php\";a:13:{s:4:\"Name\";s:21:\"Post and Page Builder\";s:9:\"PluginURI\";s:103:\"https://www.boldgrid.com/boldgrid-editor/?utm_source=ppb-wp-repo&utm_medium=plugin-uri&utm_campaign=ppb\";s:7:\"Version\";s:6:\"1.13.4\";s:11:\"Description\";s:175:\"Customized drag and drop editing for posts and pages. The Post and Page Builder adds functionality to the existing TinyMCE Editor to give you easier control over your content.\";s:6:\"Author\";s:31:\"BoldGrid \";s:9:\"AuthorURI\";s:87:\"https://www.boldgrid.com/?utm_source=ppb-wp-repo&utm_medium=author-uri&utm_campaign=ppb\";s:10:\"TextDomain\";s:15:\"boldgrid-editor\";s:10:\"DomainPath\";s:10:\"/languages\";s:7:\"Network\";b:0;s:10:\"RequiresWP\";s:0:\"\";s:11:\"RequiresPHP\";s:0:\"\";s:5:\"Title\";s:21:\"Post and Page Builder\";s:10:\"AuthorName\";s:31:\"BoldGrid \";}s:63:\"post-and-page-builder-premium/post-and-page-builder-premium.php\";a:13:{s:4:\"Name\";s:29:\"Post and Page Builder Premium\";s:9:\"PluginURI\";s:60:\"https://www.boldgrid.com/wordpress-page-builder-by-boldgrid/\";s:7:\"Version\";s:5:\"1.0.4\";s:11:\"Description\";s:48:\"Premium extension for the Post and Page Builder.\";s:6:\"Author\";s:8:\"BoldGrid\";s:9:\"AuthorURI\";s:25:\"https://www.boldgrid.com/\";s:10:\"TextDomain\";s:28:\"post-and-page-buider-premium\";s:10:\"DomainPath\";s:11:\"/languagesD\";s:7:\"Network\";b:0;s:10:\"RequiresWP\";s:0:\"\";s:11:\"RequiresPHP\";s:0:\"\";s:5:\"Title\";s:29:\"Post and Page Builder Premium\";s:10:\"AuthorName\";s:8:\"BoldGrid\";}s:35:\"boldgrid-backup/boldgrid-backup.php\";a:13:{s:4:\"Name\";s:12:\"Total Upkeep\";s:9:\"PluginURI\";s:41:\"https://www.boldgrid.com/boldgrid-backup/\";s:7:\"Version\";s:6:\"1.14.5\";s:11:\"Description\";s:159:\"Automated backups, remote backup to Amazon S3 and Google Drive, stop website crashes before they happen and more. Total Upkeep is the backup solution you need.\";s:6:\"Author\";s:8:\"BoldGrid\";s:9:\"AuthorURI\";s:25:\"https://www.boldgrid.com/\";s:10:\"TextDomain\";s:15:\"boldgrid-backup\";s:10:\"DomainPath\";s:10:\"/languages\";s:7:\"Network\";b:0;s:10:\"RequiresWP\";s:0:\"\";s:11:\"RequiresPHP\";s:0:\"\";s:5:\"Title\";s:12:\"Total Upkeep\";s:10:\"AuthorName\";s:8:\"BoldGrid\";}s:51:\"boldgrid-backup-premium/boldgrid-backup-premium.php\";a:13:{s:4:\"Name\";s:20:\"Total Upkeep Premium\";s:9:\"PluginURI\";s:41:\"https://www.boldgrid.com/boldgrid-backup/\";s:7:\"Version\";s:5:\"1.3.3\";s:11:\"Description\";s:46:\"Premium extension for the Total Upkeep plugin.\";s:6:\"Author\";s:8:\"BoldGrid\";s:9:\"AuthorURI\";s:25:\"https://www.boldgrid.com/\";s:10:\"TextDomain\";s:15:\"boldgrid-backup\";s:10:\"DomainPath\";s:10:\"/languages\";s:7:\"Network\";b:0;s:10:\"RequiresWP\";s:0:\"\";s:11:\"RequiresPHP\";s:0:\"\";s:5:\"Title\";s:20:\"Total Upkeep Premium\";s:10:\"AuthorName\";s:8:\"BoldGrid\";}}','no'),(209,'jetpack_connection_active_plugins','a:1:{s:7:\"jetpack\";a:1:{s:4:\"name\";s:7:\"Jetpack\";}}','yes'),(213,'_site_transient_timeout_boldgrid_plugins','1601790305','no'),(214,'_site_transient_boldgrid_plugins','O:8:\"stdClass\":2:{s:21:\"boldgrid-inspirations\";O:8:\"stdClass\":24:{s:5:\"title\";s:21:\"BoldGrid Inspirations\";s:7:\"version\";s:5:\"2.4.4\";s:8:\"asset_id\";i:1131870;s:12:\"release_date\";s:19:\"2020-09-22 18:08:09\";s:19:\"requires_wp_version\";s:3:\"4.4\";s:17:\"tested_wp_version\";s:3:\"5.5\";s:8:\"sections\";a:4:{s:11:\"description\";s:377:\"

BoldGrid Inspirations is an inspiration-driven plugin to assist with creating a fresh new website, or to customize an existing website.

\n

The first phase is Inspiration; the guided tool creates your base website. If you already have a website, then you can skip this step.

\n

The second phase is Customization; tools to transform your website into your vision.

\n\";s:12:\"installation\";s:283:\"
    \n

  1. Upload the entire boldgrid-inspirations folder to the /wp-content/plugins/ directory.

    2. \n

  2. Activate the plugin through the Plugins menu in WordPress.

    3. \n

  3. You will find the Inspirations menu in your WordPress Dashboard / admin panel.

    4. \n
\n\";s:9:\"changelog\";s:40767:\"

2.4.4

\n

Release date: September 22nd, 2020

\n
    \n
  • Update: Updated dependencies.
    • \n
\n

2.4.3

\n

Release date: August 11th, 2020

\n
    \n
  • Bug fix: WordPress 5.5 compatibility changes.
    • \n
  • Update: Optimized usage of setstaginginstalled.
    • \n
  • Update: Optimized \"get total coin cost\".
    • \n
  • Update: Updated links in login footer
    • \n
  • Update: Updated dependencies.
    • \n
\n

2.4.2

\n

Release date: June 15th, 2020

\n
    \n
  • Update: Updated dependencies.
    • \n
\n

2.4.1

\n

Release date: May 29th, 2020

\n
    \n
  • Update: Updated dependencies.
    • \n
\n

2.4.0

\n

Release date: May 18th, 2020

\n
    \n
  • Update: Changes needed for Crio.
    • \n
  • Bug fix: Attribution page will not show excpert.
    • \n
  • Bug fix: Fixed display / position of BoldGrid Connect image search results.
    • \n
\n

2.3.1

\n

Release date: March 12th, 2020

\n
    \n
  • Bug fix: Unable to click button on email confirmation page.
    • \n
  • Update: Removed \"Add new from GridBlocks\" feature.
    • \n
\n

2.3.0

\n

Release date: December 17th, 2019

\n
    \n
  • Bug fix: Added noindex to the attribution page.
    • \n
  • Update: Changed the form plugin from WPForms to weForms.
    • \n
  • Update: Updated dependencies.
    • \n
\n

2.2.2

\n

Release date: November 22st, 2019

\n
    \n
  • Update: BoldGrid Backup is now Total Upkeep - updating references.
    • \n
  • Update: Updated dependency boldgrid/library to 2.10.6.
    • \n
\n

2.2.1

\n

Release date: October 15th, 2019

\n
    \n
  • Update: Updated dependency boldgrid/library to 2.10.4.
    • \n
\n

2.2.0

\n

Release date: September 17th, 2019

\n
    \n
  • New feature: Recommend the BoldGrid Backup plugin for users needing to transfer a site.
    • \n
  • Update: Updating dependencies
    • \n
\n

2.1.1

\n

Release date: September 5th, 2019

\n
    \n
  • Update: Updating dependencies
    • \n
\n

2.1.0

\n

Release date: August 29th, 2019

\n
    \n
  • Update: Removed the \"Welcome to BoldGrid\" dashboard widget.
    • \n
  • Update: Add notice to dashboard widget.
    • \n
  • Update: Remove news widget from dashboard.
    • \n
\n

2.0.7

\n

Release date: August 16, 2019

\n
    \n
  • Bug fix: Fixing compact warnings
    • \n
\n

2.0.6

\n

Release date: August 1st, 2019

\n
    \n
  • Update: Updated dependencies
    • \n
\n

2.0.5

\n

Release date: July 25th, 2019

\n
    \n
  • Update: Added a switch for toggling branding of the login page.
    • \n
  • Update: Cleaned up logic on purchase coins page.
    • \n
  • Update: Updated dependencies
    • \n
\n

2.0.4

\n

Release date: July 2nd, 2019

\n
    \n
  • Update: Replaced the BoldGrid RSS feed widget on the dashboard with one in the updated library package.
    • \n
  • Update: Updated dependencies.
    • \n
\n

2.0.3

\n

Release date: May 21st, 2019

\n
    \n
  • Bug fix: Fixing \"Call to undefined method getAttribute\" error.
    • \n
  • Bug fix: Replacing deprecated filter on login: loginheadertitle / loginheadertext.
    • \n
\n

2.0.2

\n

Release date: Apr 23nd, 2019

\n
    \n
  • Bug fix: Fixing usage of php\'s empty function for php < 5.5
    • \n
\n

2.0.1

\n

Release date: Apr 19th, 2019

\n
    \n
  • Bug fix: Fixing class property declaration for php < 5.6
    • \n
\n

2.0.0

\n

Release date: Apr 16th, 2019

\n
    \n
  • Update: Made translation ready. Text domain is boldgrid-inspirations.
    • \n
  • Update: Inspirations process with full screen mode and design updates.
    • \n
  • New feature: Inspirations dashboard.
    • \n
  • New feature: German translations added - de_DE.
    • \n
\n

1.6.5

\n

Release date: Jan 29th, 2019

\n
    \n
  • Bug fix: Pages fail to install on Pages > Add New.
    • \n
\n

1.6.4

\n

Release date: Dec 5th, 2018

\n
    \n
  • Bug fix: Unable to save \"boldgridmenuoption\" on settings page.
    • \n
  • Bug fix: Fixed updating plugin via ajax.
    • \n
\n

1.6.3

\n

Release date: Dec 4th, 2018

\n
    \n
  • Bug fix: Coin Budget help was not toggling when clicked.
    • \n
\n

1.6.2

\n

Release date: Nov 26th, 2018

\n
    \n
  • Bug fix: JIRA BGINSP-33 Fixed missing build for library dependencies; Updated production build process to use composer post-autoload-dump hook.
    • \n
\n

1.6.1

\n

Release date: Nov 20th, 2018

\n
    \n
  • Update: JIRA BGCONN-20 Removed update settings; have been moved to the BoldGrid Library packages.
    • \n
  • Bug fix: JIRA BGTHEME-558 Fixed conflict between tgmpa plugin installer and the BoldGrid custom update classes.
    • \n
  • Bug fix: BoldGrid Connect Search / WP 5.0 fix.
    • \n
  • Bug fix: Attribution page not being rebuilt / WP 5.0 fix.
    • \n
  • Bug fix: BoldGrid Connect Search in the Customizer / WP 5.0 fix.
    • \n
  • Bug fix: Recommended image sizes not working as expected.
    • \n
\n

1.6.0

\n
    \n
  • Update: Updated BoldGrid library to version 2.4.2.
    • \n
  • New feature: JIRA BGINSP-24 Log data when there may be a connection or Ajax error.
    • \n
\n

1.5.8

\n
    \n
  • Bug fix: JIRA BGINSP-16 Warnings and notices within inspiration w/ Crio theme
    • \n
  • Bug fix: JIRA BGINSP-23 Fixed issue: Connect Search may load with connection notice.
    • \n
\n

1.5.7

\n
    \n
  • Update: Updated to library version 2.3.5.
    • \n
\n

1.5.6

\n
    \n
  • Bug fix: JIRA BGINSP-14 Fatal in PHP >=7.1.0 when creating internal preview builds.
    • \n
  • Bug fix: JIRA WPB-3767 Prevent invalid API calls for check-version.
    • \n
  • Update: JIRA BGBKUP-180 Auto update code moved to library and removed from Inspirations.
    • \n
  • Update: JIRA WPB-3730 Updated library dependency to ^2.0.0.
    • \n
  • Update: JIRA BGINSP-3 Forcing display of Connect Key prompt admin notice on the Inspirations page, even if dismissed, until key is entered.
    • \n
  • Update: JIRA WPB-3684 Updated composer.json, due to package changes.
    • \n
  • New feature: JIRA BGCNTRL-46 Added filters for manipulating Dashboard help in trial sites.
    • \n
\n

1.5.5

\n
    \n
  • Bug fix: JIRA BGSTAGE-32 Fixed staging plugin install.
    • \n
\n

1.5.4

\n
    \n
  • Update: JIRA BGINSP-4 Removed admin notice recommending plugin installations.
    • \n
\n

1.5.3

\n
    \n
  • New feature: JIRA WPB-3643 Ensure that deployment does not install new wporg plugins if old ones are installed.
    • \n
\n

1.5.2

\n
    \n
  • Bug fix: JIRA WPB-3587 Menu assignment after deployment broken in WP 4.9.
    • \n
  • Bug fix: JIRA WPB-3570 Inspirations Select button misplaced in WP 4.9.
    • \n
  • Bug fix: JIRA WPB-3593 Changes require to help Staging support new Customizer scheduler.
    • \n
\n

1.5.1

\n
    \n
  • Update: Updates to library.
    • \n
\n

1.5

\n
    \n
  • Update: Bump version.
    • \n
\n

1.4.11

\n
    \n
  • Update: Bump version.
    • \n
\n

1.4.10

\n
    \n
  • Bug fix: JIRA WPB-3336 All and Default categories do not align.
    • \n
  • Bug fix: JIRA WPB-3337 On a fresh install, Pages - New From GridBlocks fails.
    • \n
  • Bug fix: JIRA WPB-3333 Image search only searching one provider instead of all.
    • \n
  • Bug fix: JIRA WPB-3346 Edit Image button not working for attachment.
    • \n
  • Bug fix: JIRA WPB-3387 Loading GridBlocks just spins.
    • \n
  • Update: JIRA WPB-3352 Purchase coins through BoldGrid Central.
    • \n
  • Update: JIRA WPB-3355 Add data-image-url attribute.
    • \n
  • Update: JIRA WPB-3382 More descriptive creative commons icon.
    • \n
  • Update: JIRA WPB-3384 Add License details to attachment details.
    • \n
  • Update: JIRA WPB-3383 Filter out boldgrid-gridblock-set-preview-page.
    • \n
\n

1.4.9

\n
    \n
  • Bug fix: JIRA WPB-3318 When forcing a preferred form plugin install, first check if plugin is installed before trying to activate.
    • \n
  • Bug fix: JIRA WPB-3312 Ensure activation of preferred form plugin. Added filter for preferred slug.
    • \n
  • Bug fix: JIRA WPB-3317 New page from GridBlocks not working.
    • \n
  • Update: JIRA WPB-3252 Disable \'default\' category and configure \'showcase\'.
    • \n
  • Bug fix: JIRA WPB-3332 New from gridblocks button not showing.
    • \n
\n

1.4.8

\n
    \n
  • New feature: JIRA WPB-3200 Added WPForms support.
    • \n
  • Update: JIRA WPB-3292 Updated plugin URI.
    • \n
  • Update: JIRA WPB-3296 Add Inspirations as first menu item child.
    • \n
  • Bug Fix: JIRA WPB-3274 Plugins > Add New Updates fail in modals.
    • \n
  • New feature: JIRA WPB-3293 Resize images during deployment vs imgr server.
    • \n
\n

1.4.7

\n
    \n
  • Update: JIRA WPB-3243 Change feedback admin notice display frequency.
    • \n
  • Update: JIRA WPB-3264 Adding twitch social media option.
    • \n
  • New Feature: Added BoldGrid Library to plugin.
    • \n
\n

1.4.6

\n
    \n
  • Bug fix: JIRA WPB-3179 Gradient style being lost during normal deployment.
    • \n
  • Bug fix: JIRA WPB-3180 Open WordPress/BoldGrid links in attribution page in new tab.
    • \n
\n

1.4.5

\n
    \n
  • Bug fix: JIRA WPB-3161 Fixed auto plugin update.
    • \n
  • Bug fix: JIRA WPB-3162 Fixed issue creating .htaccess file in deployment.
    • \n
  • Bug fix: JIRA WPB-3171 As an author, when installing a site I do not want background images to be processed.
    • \n
  • Bug fix: JIRA WPB-3176 Background gradient / url bug during deplyment.
    • \n
\n

1.4.4

\n
    \n
  • Bug fix: JIRA WPB-3151 Added check and load before using getplugindata() for updates.
    • \n
  • Bug fix: JIRA WPB-3141 Fixed invalid updates for BoldGrid Prime theme.
    • \n
  • Bug fix: JIRA WPB-3158 Deployment\'s gallery updates are not saved.
    • \n
\n

1.4.3

\n
    \n
  • New feature: JIRA WPB-3106 As an Author, I can set background images for elements.
    • \n
  • New feature: JIRA WPB-3095 Update generic builds to display per theme channel.
    • \n
\n

1.4.2

\n
    \n
  • Bug fix: JIRA WPB-2745 Fixed upgrade notices displaying when activation version was not recorded.
    • \n
  • Update: JIRA WPB-3019 Updating attribution link creation.
    • \n
\n

1.4.1

\n
    \n
  • New feature: JIRA WPB-3044 Automatically get Unsplash attribution.
    • \n
  • Update: JIRA WPB-3043 Updating plugin description.
    • \n
\n

1.4.0.1

\n
    \n
  • Bug fix: JIRA WPB-3232 Deploy Staging menu item missing.
    • \n
  • Bug fix: JIRA WPB-3233 BoldGrid Connect Search missing from new image widget.
    • \n
\n

1.4

\n
    \n
  • Update: JIRA WPB-2936 Updating YouTube videos for BoldGrid Dashboard\'s new release.
    • \n
  • Bug fix: JIRA WPB-2927 Social media menu disappears.
    • \n
  • Update: JIRA WPB-2949 Configure blog using categories.
    • \n
  • Bug fix: JIRA WPB-2950 Added max height for reseller logos on login page.
    • \n
  • Bug fix: JIRA WPB-2925 Sidebar widgets don\'t match between preview and installed site.
    • \n
  • Bug fix: JIRA WPB-2951 Images in staging posts not being downloaded.
    • \n
  • Bug fix: JIRA WPB-2955 Backwards compatibility - maps taking up 200px empty space.
    • \n
  • Bug fix: JIRA WPB-2984 Attribution page 404.
    • \n
\n

1.3.9

\n
    \n
  • Bug fix: JIRA WPB-2912 Fixed issue when installing plugins from the Tools Import page.
    • \n
  • Bug fix: JIRA WPB-2916 Inspirations deploy fatal error if an old forked plugin had the original installed.
    • \n
  • Bug fix: JIRA WPB-2905 If installing via Author, do not update pages with survey data.
    • \n
  • Bug fix: JIRA WPB-2910 Unterminated entity reference bug.
    • \n
  • Update: JIRA WPB-2913 Validate email address in survey.
    • \n
  • Bug fix: JIRA WPB-2404 iframe timeout in step 2 of Inspirations.
    • \n
  • Bug fix: JIRA WPB-2173 Error deleting image and redownloading.
    • \n
  • Bug fix: JIRA WPB-2635 Start over staging affecting active site.
    • \n
  • Bug fix: JIRA WPB-2493 Publish private posts during staging deployment.
    • \n
  • Bug fix: JIRA WPB-2796 Social media urls end in /username, go to 404s.
    • \n
\n

1.3.8

\n
    \n
  • Bug fix: JIRA WPB-2892 Fixed plugin update checks for some scenarios (WP-CLI, Plesk, etc).
    • \n
  • Update: JIRA WPB-2900 Update verbiage of build coin cost.
    • \n
  • Bug fix: JIRA WPB-2901 Scroll bars not visible on preview iframe in Chrome.
    • \n
  • Bug fix: Removing CTA hooks.
    • \n
\n

1.3.7

\n
    \n
  • Update: JIRA WPB-2819 Use switch instead of checkbox for Demo.
    • \n
  • Bug fix: JIRA WPB-2780 Theme screenshots opening directly, rather than within gallery.
    • \n
  • Update: JIRA WPB-2825 Adjust do not display formatting.
    • \n
  • Update: JIRA WPB-2829 Updating hook to resolve BoldGrid SEO plugin conflicts.
    • \n
  • Update: JIRA WPB-2837 Remove loading image after selecting theme in Gallery.
    • \n
  • Update: JIRA WPB-2839 Minor verbiage change for Add a blog.
    • \n
  • Update: JIRA WPB-2785 Entering words with apostrophe in it for Site title displays with a Backslash.
    • \n
  • Bug fix: JIRA WPB-2848 Customize link takes users back to Inspirations.
    • \n
  • Bug fix: JIRA WPB-2527 \'New from GridBlocks\' preview page appearing in cart.
    • \n
  • Bug fix: JIRA WPB-2862 Survey, invalid argument supplied for foreach.
    • \n
  • Bug fix: JIRA WPB-2601 Inspirations Internet Explorer/ Stuck on loading themes.
    • \n
  • Bug fix: JIRA WPB-2854 Downloading Image spinner never stops spinning.
    • \n
\n

1.3.6

\n
    \n
  • Bug fix: JIRA WPB-2772 PHP warnings on deploy in WordPress 4.3.7.
    • \n
  • Bug fix: JIRA WPB-2766 Plesk and WP-CLI were not getting private repo updates.
    • \n
  • Update: JIRA WPB-2763 Update email and address on Contact Us page.
    • \n
  • Update: JIRA WPB-2764 Remove option to add a map.
    • \n
  • Update: JIRA WPB-2765 Allow iframes for preview builds.
    • \n
  • New feature: JIRA WPB-2771 Update footer-company-details widget with survey data.
    • \n
  • New feature: JIRA WPB-2777 Add an Install sample blog checkbox.
    • \n
  • New feature: JIRA WPB-2778 Setup a blog during deployment.
    • \n
  • Bug fix: JIRA WPB-2792 Staged posts (private posts) are trashed when starting over active site.
    • \n
  • Update: JIRA WPB-2800 Ensure \'Install a blog\' works with Staging.
    • \n
  • Update: JIRA WPB-2801 Remove milestones classes.
    • \n
  • Bug fix: JIRA WPB-2779 Survey not working with Staging.
    • \n
  • Update: JIRA WPB-2805 Preview builds w & w/o blogs.
    • \n
  • New feature: JIRA WPB-2806 Add filter for Inspirations configs.
    • \n
  • Bug fix: JIRA WPB-2808 Do not request generic builds when requesting blog as well.
    • \n
\n

1.3.5

\n
    \n
  • Testing: JIRA WPB-2744 Tested on WordPress 4.7.
    • \n
  • Update: JIRA WPB-2376 Filter the bgtfw contact blocks.
    • \n
  • Update: JIRA WPB-2476 Update case of Company name.
    • \n
  • Update: JIRA WPB-2747 Update Add a map verbiage.
    • \n
  • Update: JIRA WPB-2749 Add a map to my Contact page.
    • \n
  • Bug fix: JIRA WPB-2658 Fix spacing issues atop Inspirations.
    • \n
  • Bug fix: JIRA WPB-2751 Show all in the smaller view of inspirations doesn\'t work anymore.
    • \n
  • Bug fix: JIRA WPB-2757 Apostrophe and other strange characters installed via Inspirations.
    • \n
  • Bug fix: JIRA WPB-2759 DOMDocument::loadHTML(): htmlParseEntityRef: expecting \';\'.
    • \n
\n

1.3.4

\n
    \n
  • Bug fix: JIRA WPB-2696 Remove placeholders from survey.
    • \n
  • New feature: JIRA WPB-2697 Update phone numbers in widgets.
    • \n
  • New feature: JIRA WPB-2699 Use phone number entered during survey.
    • \n
  • Update: JIRA WPB-2704 Adjust format of how social media icons are saved.
    • \n
  • New feature: JIRA WPB-2705 Use survey social media items when creating menu.
    • \n
  • Update: JIRA WPB-2711 Show optional message in survey.
    • \n
  • Update: JIRA WPB-2712 Have plus sign toggle more social icons.
    • \n
  • Update: JIRA WPB-2723 Update phone in pages.
    • \n
\n

1.3.3

\n
    \n
  • Bug fix: JIRA WPB-2627 Back / next buttons should not be clickable.
    • \n
  • Bug fix: JIRA WPB-2625 Behavior of last image\'s next button in Inspirations.
    • \n
\n

1.3.2

\n
    \n
  • Update: JIRA WPB-2582 Always show arrows in Inspirations gallery.
    • \n
  • Update: JIRA WPB-2583 Ensure first letter in theme\'s title attribute is capitalized.
    • \n
  • Update: JIRA WPB-2599 Add placeholder for 4th step to Inspirations.
    • \n
  • Update: JIRA WPB-2551 Duplicate images.
    • \n
  • New feature: JIRA WPB-2603 Add initial version of survey.
    • \n
  • Bug fix: JIRA WPB-2622 Inspirations - Step 4 - Go back button installs site.
    • \n
\n

1.3.1

\n
    \n
  • Misc: JIRA WPB-2503 Added plugin requirements to readme.txt file.
    • \n
  • Bug fix: JIRA WPB-2539 Fix possible duplicate connection issue notice from ajax.js call.
    • \n
  • Bug fix: JIRA WPB-2558 Don\'t display feedback widget if user hasn\'t entered their key.
    • \n
  • Bug fix: JIRA WPB-2559 Don\'t allow widgets to drag into welcome box area.
    • \n
  • Bug fix: JIRA WPB-2555 Images in search results flicker.
    • \n
  • Update: JIRA WPB-2563 Convert Attribution page to use custom post type.
    • \n
  • Update: JIRA WPB-2568 Added fancybox and large previews to Inspirations.
    • \n
  • Update: JIRA WPB-2570 Milestone blogname change.
    • \n
  • Update: JIRA WPB-2574 Milestone Social Media Change.
    • \n
  • Update: JIRA WPB-2578 Milestone Contact Info Footer Change.
    • \n
\n

1.3

\n
    \n
  • Bug fix: JIRA WPB-2544 Disable \'Install\' button after clicking it.
    • \n
\n

1.2.13

\n
    \n
  • Bug fix: JIRA WPB-2531 Javascript error checking needed for mine count.
    • \n
\n

1.2.12

\n
    \n
  • Update: JIRA WPB-2472 Added update notice for 1.3.
    • \n
  • Bug fix: JIRA WPB-2486 Incorrect page count on All Pages.
    • \n
  • Bug fix: JIRA WPB-2467 With staging disabled, Customize goes to \"Change Themes\".
    • \n
  • Update: JIRA WPB-2488 Remove \'Permanently delete pages instead of sending to trash\'.
    • \n
  • Update: JIRA WPB-2490 Move default option to \'install as staging\'.
    • \n
  • Update: JIRA WPB-2491 Add \'Customize > Active Theme\' navigation to Inspirations.
    • \n
  • Bug fix: JIRA WPB-2496 Require comment text in feedback form.
    • \n
  • Update: JIRA WPB-2229 Update error reporting when purchasing images.
    • \n
  • Update: JIRA WPB-2498 Change \'Company Name\' to theme name.
    • \n
  • Update: JIRA WPB-2497 Add new dashboard videos.
    • \n
  • Bug fix: JIRA WPB-2376 \'No search results\' method is not cleared in BGCS.
    • \n
\n

1.2.11

\n
    \n
  • Bug fix: JIRA WPB-2468 Switching between boldgrid admin menu and standard wp menu no longer works.
    • \n
  • Bug fix: JIRA WPB-2477 If you have an existing site non BG, no route for staging exists.
    • \n
\n

1.2.10

\n
    \n
  • Bug fix: JIRA WPB-2446 Fixed missing build id passed on site install.
    • \n
  • Bug fix: JIRA WPB-2426 Insert Gridblock button is missing.
    • \n
  • Bug fix: JIRA WPB-2443 When starting over, I get a blank page.
    • \n
  • Bug fix: JIRA WBP-2445 Inspirations is not fetching cached themes.
    • \n
  • Update: JIRA WPB-2458 Update \'Recommended\' verbiage in last step of Inspirations.
    • \n
\n

1.2.9

\n
    \n
  • Misc: JIRA WPB-2420 Added EOF line breaks.
    • \n
  • Bug fix: JIRA WPB-2387 Fixed issue with AJAX theme updates and BG theme slugs duplicated in the WP repo.
    • \n
  • Bug fix: JIRA WPB-2324 Attribution should not show in 404 sitemap.
    • \n
  • Bug fix: JIRA WPB-2403 No plugins recommended still showing notice.
    • \n
  • Update: JIRA WPB-2416 Text changes for confirmation section of Inspirations.
    • \n
  • Update: JIRA WPB-2417 Add additional text to deployment success page for staging.
    • \n
  • Bug fix: JIRA WPB-2421 Message showing when it shouldn\'t - We\'ve recognized that you haven\'t installed...
    • \n
  • Bug fix: JIRA WPB-2112 BoldGrid Connect Search missing for galleries.
    • \n
  • Bug fix: JIRA WPB-2422 Fixed CSS Loading graphic animation in chrome to display properly.
    • \n
  • Bug fix: JIRA WPB-2401 Gallery not displaying correctly in Chrome && FF.
    • \n
  • Bug fix: JIRA WPB-2423 Trying to get property of non-object in ...stock-photography.php.
    • \n
\n

1.2.8

\n
    \n
  • Bug fix: JIRA WPB-2398 Error requesting free key.
    • \n
  • Bug fix: JIRA WPB-2399 Only show feedback widget to admins.
    • \n
\n

1.2.7

\n
    \n
  • Bug fix: JIRA WPB-2389 Fixed saving BoldGrid Settings.
    • \n
  • Bug fix: JIRA WPB-2388 Removed duplicate boldgrid_activate().
    • \n
  • Update: JIRA WPB-2390 Update verbiage for inspirations install success.
    • \n
  • Bug fix: JIRA WPB-2391 Hide BoldGrid Welcome Panel if key isn\'t entered yet.
    • \n
  • Bug fix: JIRA WPB-2392 If key is less than 32 char don\'t make call to validate.
    • \n
  • Bug fix: JIRA WPB-2393 Error messages should be removed when resubmitting keys.
    • \n
  • Bug fix: JIRA WPB-2394 Cursor for show/hide log should be a pointer.
    • \n
  • Update: JIRA WPB-2395 Update login page styling.
    • \n
  • Bug fix: JIRA WPB-2396 Remove staging from recommended plugin notices.
    • \n
  • Bug fix: JIRA WPB-2327 Check if framework is handling plugin recommendations before recommending.
    • \n
\n

1.2.6

\n
    \n
  • Misc: JIRA WPB-2344 Updated readme.txt for Tested up to 4.6.1.
    • \n
  • Bug fix: JIRA WPB-2336 Load BoldGrid settings from the correct WP option (site/blog).
    • \n
  • Bug fix: JIRA WPB-2248 Removed \'New From GridBlocks\' button on edit submission page.
    • \n
  • Bug fix: JIRA WPB-2332 Reset scroll position on step 2 of Inspirations to top.
    • \n
  • Bug fix: JIRA WPB-2339 Remove notices from Inspirations page.
    • \n
  • Update: JIRA WPB-2208 Removed tutorials from Inspirations.
    • \n
  • Update: JIRA WPB-2359 Order \'Category Filter\' by category display order.
    • \n
  • Update: JIRA WPB-2360 Sort themes by category and then order within category.
    • \n
  • Update: JIRA WPB-2368 Read version constant from plugin file.
    • \n
  • Update: JIRA WPB-2361 Add BoldGrid Connect Search to Editor\'s background image tool.
    • \n
  • Update: JIRA WPB-2354 Preview button needs to always be visible in mobile view.
    • \n
  • Update: JIRA WPB-2355 Remove extraneous \'Preview\' button.
    • \n
  • Bug fix: JIRA WPB-2364 Inspirations not respecting theme release channel.
    • \n
  • Bug fix: JIRA WPB-2370 Color in screenshot does not match preview.
    • \n
  • Bug fix: JIRA WPB-2373 Duplicate themes in Inspirations.
    • \n
  • Bug fix: JIRA WPB-2379 Wrong budget passed when going form step 2 to step 1.
    • \n
  • Update: JIRA WPB-2380 Remove references to tutorials in deployment congrats message.
    • \n
  • Bug fix: JIRA WPB-2383 Image Search tab appears when clicking \'Add GridBlock\'.
    • \n
\n

1.2.5

\n
    \n
  • Bug fix: JIRA WPB-2325 Added wrapper to handle mbconvertencoding() if mbstring is not loaded.
    • \n
  • Bug fix: JIRA WPB-2313 Disabled GridBlocks in network admin pages.
    • \n
  • New feature: JIRA WPB-2268 Changed to resized preview screenshots for Inspirations Design First concept.
    • \n
  • New feature: JIRA WPB-2287 Adjust device preview buttons in step 2 to behave like those in editor.
    • \n
  • New feature: JIRA WPB-2291 Auto install staging in final step if user chooses staging.
    • \n
  • Update: JIRA WPB-2290 Changed \'Install\' button to \'Next\'.
    • \n
  • Bug fix: JIRA WPB-2289 Continuously clicking category in step 1 shuffles themes.
    • \n
  • Update: JIRA WPB-2267 Added message to Inspirations when no generic themes are available.
    • \n
  • Update: JIRA WPB-2315 Added error handling for malformed ajax results for call to /api/build/get-generic.
    • \n
  • Update: JIRA WPB-2316 Add error handling for failures to fetch categories.
    • \n
  • Update: JIRA WPB-2317 Add error handling for failures to fetch pagesets.
    • \n
  • Update: JIRA WPB-2319 Check user capabilities before prompting for api key.
    • \n
  • Update: JIRA WPB-2320 Ensure user has permission to edit page before allowing downloadandinsertintopage.
    • \n
  • Update: JIRA WPB-2322 Sanitize user feedback before adding to options table.
    • \n
  • Update: JIRA WPB-2323 Allow admin notices to be dismissed per user.
    • \n
  • Update: JIRA WPB-2326 Update \'update\' class to utilize Admin Notices class.
    • \n
  • Update: JIRA WPB-2327 Check user capabilities before showing admin notices.
    • \n
  • Update: JIRA WPB-2331 Update confirmation messages.
    • \n
\n

1.2.4

\n
    \n
  • Bug fix: JIRA WPB-2269 Typo fix in BoldgridInspirationsDependencyPlugins::printuninstalled_plugins().
    • \n
  • Bug fix: JIRA WPB-2270 New From GridBlocks became unavailable.
    • \n
\n

1.2.3

\n
    \n
  • New feature: JIRA WPB-2172 For preview generic builds, added an option for identification for purges, etc.
    • \n
  • Bug fix: JIRA WPB-2263 For preview sites under multisite, set the admin email address using the network admin email address.
    • \n
  • Bug fix: JIRA WPB-2223 Reworked API key validation and connection issue notices, formatting.
    • \n
  • Misc: JIRA WPB-2256 Updated readme.txt for Tested up to: 4.6.
    • \n
  • Rework: JIRA WPB-2150 Moved API methods to a new class, formatting, and phpcs rework.
    • \n
  • Bug fix: JIRA WPB-2224 Hide the email address field when widget is loaded.
    • \n
  • Bug fix: JIRA WPB-2225 Fixed jQuery Migrate deprecated warning.
    • \n
  • Update: JIRA WPB-2245 Changed feed to pull from dashboard tag on blog.
    • \n
  • Bug fix: JIRA WPB-2265 Uncaught TypeError: IMHWPB.BaseAdmin is not a constructor.
    • \n
  • Bug fix: JIRA WBP-2236 Errors everywhere when logging in as an Editor.
    • \n
  • Bug fix: JIRA WPB-2234 Add currentusercan checks to BoldgridInspirations->setapikeycallback().
    • \n
  • Bug fix: JIRA WPB-2237 Limit ajax requests by user.
    • \n
  • Bug fix: JIRA WPB-2240 Limit printing of configs in head.
    • \n
\n

1.2.2

\n
    \n
  • Bug fix: JIRA WPB-2058 Added wrap class to the tutorials page.
    • \n
  • Bug fix: JIRA WPB-2184 In PHP 5.2, deactivate and die properly.
    • \n
  • New feature: Added BoldGrid news widget to dashboard.
    • \n
  • Bug fix: JIRA WPB-1994 Fixed issue with WP Theme Editor not being available.
    • \n
  • New feature: Added BoldGrid Feedback widget.
    • \n
  • Bug fix: JIRA WPB-2169 Connect Search defaults to smallest image size when no recommended sizes available.
    • \n
  • Bug fix: JIRA WPB-2192 Allow bug report to correctly show parent themes if submitted.
    • \n
\n

1.2.1

\n
    \n
  • Bug fix: JIRA WPB-2160 New From GridBlocks, multiple pages are installed.
    • \n
  • Update: Changed text of getting and entering connect keys.
    • \n
  • Security: JIRA WPB-2151 Disabled autocomplete for API key entry fields.
    • \n
  • Bug fix: JIRA WPB-2145 Fixing issue with theme screenshots on Chrome Ubuntu.
    • \n
\n

1.2

\n
    \n
  • Bug fix: JIRA WPB-2119 For asset downloads, when Imagick is loaded, set the thread limit to 1.
    • \n
  • Bug fix: JIRA WPB-2125 Fixing issue where theme was overwritten without version change.
    • \n
  • Bug fix: JIRA WPB-2104 Go back button hides all themes (Inspirations > Add Theme).
    • \n
  • Bug fix: JIRA WPB-2107 BoldGrid Connect Search overlapping footer (Dashboard > Media).
    • \n
  • Bug fix: JIRA WPB-2109 Session issues when starting over and importing active site.
    • \n
  • Bug fix: JIRA WPB-2116 Changes to the order of images in a gallery are not saving.
    • \n
  • Bug fix: JIRA WPB-2134 Staging\'s boldgrid_attribution option and \'Uninitialized string offset\' Notice.
    • \n
  • Bug fix: JIRA WPB-2135 Image not replaced in Page & Post Editor after using Connect Search.
    • \n
\n

1.1.8

\n
    \n
  • Bug fix: JIRA WPB-2058 Added wrap class to Inspirations, so admin notices are displayed at the top.
    • \n
  • Bug fix: JIRA WPB-2041 Fixed BoldGrid theme update check in WordPress 4.6.
    • \n
  • Testing: JIRA WPB-2046 Tested on WordPress 4.5.3.
    • \n
  • New feature: JIRA WPB-599 Added options for plugin and theme auto-updates via WordPress autoupdater.
    • \n
  • Update: JIRA WPB-2008 Deploy class updated to allow for is_generic flag.
    • \n
  • Bug fix: JIRA WPB-1950 Prevent a portait image from displaying atop \'Crop Image\' and \'Skip Cropping\' buttons.
    • \n
\n

1.1.7

\n
    \n
  • Bug fix: JIRA WPB-2032 Fixed issue when activating key. Added nonce to api key form.
    • \n
  • Rework: JIRA WPB-2030 Updated the \"I don\'t have an API key\" section.
    • \n
  • New feature: JIRA WPB-2029 Added TOS box to API key submission form.
    • \n
  • New feature: JIRA WPB-1905 Added capability for auto-updates of boldgrid-inspirations by API response.
    • \n
  • Bug fix: JIRA WPB-2002 Fixed theme update issue where upgrader says is up to date at times.
    • \n
  • Bug fix: JIRA WPB-2006 Pdes and Homepage not installing correctly on Inpirations Theme Only installs.
    • \n
\n

1.1.6

\n
    \n
  • New feature: JIRA WPB-1839 Users can now change their theme release channel.
    • \n
  • Security fix: JIRA WPB-1977 Validate nonce for feedback form diagnostic data callback and form submit.
    • \n
  • Bug fix: JIRA WPB-1955 Fatal error: Class \'BoldgridStagingPlugin\' not found.
    • \n
\n

1.1.5

\n
    \n
  • Bug fix: JIRA WPB-1914 Staged image used on Active page not showing in cart.
    • \n
\n

1.1.4

\n
    \n
  • Bug fix: JIRA WPB-1886 Fixed feedback notice being displayed too often (more than a week after submitting).
    • \n
  • New feature: JIRA WPB-1183 Refresh the Library Tab after downloading an image.
    • \n
  • Update: JIRA WPB-1865 Update style of \'Transactions\' pages to better incorporate BoldGrid Staging\'s nav menu.
    • \n
  • Update: JIRA WPB-1884 Passed WordPress 4.5.1 testing.
    • \n
  • Bug fix: JIRA WPB-1855 Do not display feedback notice on update or setting pages.
    • \n
  • Bug fix: JIRA WPB-1860 Fixed horizontal line through screenshot in step 2.
    • \n
  • Bug fix: JIRA WPB-1863 Cart does not look for watermarked images used within staged pages.
    • \n
  • Bug fix: JIRA WPB-1891 View / Download of images within receipts not working for images purchased via Staging.
    • \n
  • Bug fix: JIRA WPB-1893 JS errors in console when viewing attachments.
    • \n
  • Bug fix: JIRA WPB-1900 Attribution shows in menu when menu generated using wppagemenu.
    • \n
\n

1.1.3

\n
    \n
  • Bug fix: JIRA WPB-1824 Fixed order of plugin deactivation and uninstall in Start Over process.
    • \n
  • Bug fix: JIRA WPB-1814 Fixed PHP notice in page and post editor for In Menu when there is a corrupted nav menu array.
    • \n
  • Bug fix: JIRA WPB-1823 Fixed display of \"Themes\" H1 and the additional themes bar when choosing active or staging before installing a theme.
    • \n
  • Bug fix: JIRA WPB-1840 Fixing thumbnail presentation in inspirations and add new theme.
    • \n
\n

1.1.2.3

\n
    \n
  • Update: Sync version. See version 1.1.1.1.
    • \n
\n

1.1.2.2

\n
    \n
  • Bug fix: JIRA WPB-1833 Fixed checking for previously downloaded assets in deployment when using multisite (wp-preview).
    • \n
\n

1.1.2.1

\n
    \n
  • Bug fix: JIRA WPB-1817 BoldGrid Connect Search: Was not being added when changing a header image in the Customizer.
    • \n
  • Rework: JIRA WPB-1541 Removed feedback form bug report diagnostic report items.
    • \n
  • Bug fix: JIRA WPB-1816 Fixed update class interference with the Add Plugins page.
    • \n
\n

1.1.2

\n
    \n
  • Bug fix: JIRA WPB-1809 Fixed undefined index \"action\" for some scenarios. Optimized update class and addressed CodeSniffer items.
    • \n
  • Rework: JIRA WPB-1541 Reworked admin feedback notice.
    • \n
  • Rework: JIRA WPB-1751 Removed analysis processing and optional logging capabilities. Added support for XHProf.
    • \n
  • Bug fix: JIRA WPB-1805 Now adds theme update info on the Customizer Themes page.
    • \n
  • Rework: JIRA WPB-1785 Enabled and reworked image caching for the preview server.
    • \n
  • Rework: JIRA WPB-1751 Reworked analysis processing.
    • \n
  • Update: JIRA WPB-1658 Storing more reliable install data through inspirations.
    • \n
  • Bug fix: JIRA WPB-1787 When not using BoldGrid menu, cart does not dynamically update total page price.
    • \n
  • Update: JIRA WPB-1754 Remove attribution page from search results.
    • \n
  • Bug fix: JIRA WPB-1788 webkit css missing from \'new from gridblocks\'.
    • \n
  • New feature: JIRA WPB-1806 Add \'BoldGrid search\' tab when replacing an image.
    • \n
\n

1.1.1.1

\n
    \n
  • Bug Fix: Fixing logo display on login screen.
    • \n
\n

1.1.1

\n
    \n
  • Bug fix: Fixed analysis include for preview server.
    • \n
  • Bug fix: New From GridBlocks: Asset download issues.
    • \n
\n

1.1

\n
    \n
  • New feature: JIRA WPB-1751 Added analysis processing and optional logging capabilities.
    • \n
  • Bug fix: JIRA WPB-1781 Removed boldgriddismissedadmin_notices from Start Over cleanup.
    • \n
  • New feature: JIRA WPB-1541 Added feedback notice.
    • \n
  • Bug fix: JIRA WPB-1747 New From GridBlocks: For non BoldGrid themes, only load grid css.
    • \n
  • Bug fix: JIRA WPB-1760 New From GridBlocks: Ensure page title shows on preview page.
    • \n
  • Update: JIRA WPB-1779 New From GridBlocks: Update verbiage for \'Downloading GridBlocks\'.
    • \n
\n

1.0.12.1

\n
    \n
  • Bug fix: JIRA WPB-1710 Fixed missing device preview tabs on Add New Theme preview modal.
    • \n
  • Bug fix: JIRA WPB-1710 Fixed notice dismissal checking.
    • \n
  • Bug fix: JIRA WPB-1749 On start over, staging menus are not deleted.
    • \n
  • Bug fix: JIRA WPB-1755 Gallery images not showing in cart.
    • \n
\n

1.0.12

\n
    \n
  • Bug fix: JIRA WPB-1740 Fixed \"In Menu\" messages in editor when staging plugin is not active, and fixed saving menu selections.
    • \n
  • New feature: JIRA WPB-1726 Added optional feedback for GridBlock Add Page.
    • \n
  • Removed Ft: JIRA WPB-1710 Removed Inspirations Add Pages; replaced by GridBlocks.
    • \n
  • Misc: JIRA WPB-1361 Added license file.
    • \n
  • New feature: Don\'t assign footer contact widget if using base pagesets.
    • \n
  • Bug Fix: JIRA WPB-1732 Fixing css issues on login screen (firefox).
    • \n
  • Bug Fix: JIRA WPB-1687 Image search: Title, Caption, Alt Text and Description do not display on new pages.
    • \n
\n

1.0.11

\n
    \n
  • New feature: JIRA WPB-1699 Added optional feedback for theme activation.
    • \n
  • New feature: JIRA WPB-1690 Adding BoldGrid themes to All themes install menu.
    • \n
  • Bug fix: JIRA WPB-1686 Limited items loaded in network admin pages.
    • \n
  • Improvement: JIRA WPB-1604 Added a \"Cancel\" link to the \"In Menu\" section.
    • \n
  • Improvement: JIRA WPB-1603 Display menu locations in the editor \"In Menu\" section.
    • \n
  • Bug fix: JIRA WPB-1602 Corrected capitalization of \"None\" under \"In menu\" in the editor.
    • \n
  • Improvement: JIRA WPB-1664 Gets apikey and sitehash from configs instead of get_option.
    • \n
  • Bug fix: JIRA WPB-1597 Fixing indefined index error
    • \n
  • New feature: JIRA WPB-1649 Added reporting of PHP version and mobile ratio.
    • \n
  • Bug fix: JIRA WPB-1598 \'Mine\' count on \'all pages\' is incorrect.
    • \n
  • Bug fix: JIRA WPB-1647 JS error with easy-attachment-preview-size.js.
    • \n
  • Bug fix: JIRA WPB-1651 When the BG menu is turned off, Appearance link should take you to themes.
    • \n
\n

1.0.10

\n
    \n
  • Bug fix: JIRA WPB-1632 Fixed handling of subcategoryid in deploypage_sets.
    • \n
  • New feature: JIRA WPB-1510 Moved adhoc functions.php to class-boldgrid-inspirations-utility.php (class BoldgridInspirationsUtility).
    • \n
  • Rework: JIRA WPB-1553 Updated require and include statements for standards.
    • \n
  • Bug fix: JIRA WPB-1563 Updated pages in which wpiframe-mediaupload.css is loaded.
    • \n
  • Bug fix: JIRA WPB-1549 Resolve attribution page missing attribution for several images.png.
    • \n
\n

1.0.9.2

\n
    \n
  • Bug fix: Add GridBlock Sets feature disabled.
    • \n
\n

1.0.9.1

\n
    \n
  • Bug fix: JIRA WPB-1553 Fixed support for PHP 5.2 to deactivate plugin.
    • \n
  • Bug fix: Prevent click of links in addnewpage_selection previews.
    • \n
  • Bug fix: JIRA WPB-1554 Fixed undefined JavaScript variable pagenow for customizer link.
    • \n
\n

1.0.9

\n
    \n
  • Bug fix: JIRA WPB-1554 Fixed theme link in network dashboard nav menu.
    • \n
  • Bug fix: JIRA WPB-1590 Fixed JavaScript error for undefined screen info in network dashboard.
    • \n
  • Bug fix: JIRA WPB-1535 Fixed theme deployment issues.
    • \n
  • New feature: JIRA WPB-1584 Added an opt-out feedback payload delivery system.
    • \n
  • New feature: JIRA WPB-1580 Added optional feedback for customizer_start.
    • \n
  • Bug fix: JIRA WPB-1571 Removed plugin dependency admin notice when editing an attachment (image).
    • \n
  • New feature: JIRA WPB-1579 Added feedback opt-out in BoldGrid Settings, hidden for now.
    • \n
  • Bug fix: JIRA WPB-1575 Addressed an issue causing mismatch color palettes on cached previews
    • \n
  • New feature: JIRA WPB-1514 Add new pages offers page templates to choose from.
    • \n
\n

1.0.8.1

\n
    \n
  • Bug fix: JIRA WPB-1553 Fixed PHP version check condition (<5.3).
    • \n
\n

1.0.8

\n
    \n
  • Bug fix: JIRA WPB-1561 Fixed missing getplugindata on update calls.
    • \n
  • New feature: JIRA WPB-1511 Added dependency plugin notice on editor pages.
    • \n
  • Bug fix: JIRA WPB-1553 Added support for DIR in PHP <=5.2.
    • \n
  • Bug fix: JIRA WPB-1371 JSON encoded image data for media download requests.
    • \n
  • New feature: JIRA WPB-1332 Swapping loading GIF to CSS loading image.
    • \n
  • New feature: JIRA WPB-1072 Storing static pages on install
    • \n
  • New feature: JIRA WPB-1539 When deleting a page, remove it from any applicable menus as well.
    • \n
  • New feature JIRA WPB-1542 Manage menu assignment within editor.
    • \n
  • New feature JIRA WPB-1555 Add wp-image-## class to images during deployment.
    • \n
  • New feature JIRA WPB-1557 Add wp-image-## class to images when adding gridblocks.
    • \n
  • Bug fix: JIRA WPB-1506 Theme naming missing in preview.
    • \n
  • Bug fix: JIRA WPB-1443 Extra page listed under \'Mine\'.
    • \n
  • Bug fix: JIRA WPB-1560 Install options not available on preview server
    • \n
\n

1.0.7

\n
    \n
  • Rework: JIRA WPB-1533 Ensured activation data is sent after first login.
    • \n
\n

1.0.7

\n
    \n
  • Rework: JIRA WPB-1533 Ensured activation data is sent after first login.
    • \n
\n

1.0.6

\n
    \n
  • Rework: JIRA WPB-1411 Added more output to the deploy log.
    • \n
\n

1.0.5

\n
    \n
  • Bug fix: JIRA WPB-1462 Fixed position of dependency plugins admin notice. Also limited to Dashboard and plugins page.
    • \n
  • Bug fix: JIRA WPB-1290 Fixing issues with galleries leaving empty spaces
    • \n
  • Bug fix: JIRA WPB-1471 Made deployment plugin installation respect release channel.
    • \n
  • Rework: JIRA WPB-1452 Remove unneeded call to \'boldgridactivateframework\' during deployment.
    • \n
  • Bug fix: JIRA WPB-946 Fixed margin bug on step 2 additional themes.
    • \n
  • Bug fix: JIRA WPB-1384 Increase width of select input on image search modal.
    • \n
  • Bug fix: JIRA WPB-1508 BoldGrid Image search box size is inconsistent.
    • \n
\n

1.0.4

\n
    \n
  • Bug fix: JIRA WPB-1442 Fixing inspiration border styles for wordpress 4.4
    • \n
  • Bug fix: JIRA WPB-1461 Updating login button styles for wordpress 4.4
    • \n
  • Bug fix: JIRA WPB-1411 Added initialization and checks for empty image queues in deployment.
    • \n
  • Bug fix: JIRA WPB-1406 Attribution page still showing in \'All Pages\'.
    • \n
  • Bug fix: JIRA WPB-1451 Active images are showing in Staging attribution page.
    • \n
  • Bug fix: JIRA WPB-1466 Tabs on tutorials page too small at 1035px - 1482px.
    • \n
\n

1.0.3

\n
    \n
  • New feature: JIRA WPB-1363 Updated readme.txt for WordPress standards.
    • \n
  • New feature: JIRA WPB-1389 When starting over theme mods are saved with a flag to recompile sass
    • \n
  • Bug fix: JIRA WPB-1420 Content of Attribution page is overwriting page saves.
    • \n
\n

1.0.2

\n
    \n
  • Bug fix: JIRA WPB-1395 Adjusted theme update data; now gets theme uri from theme style.css, download url from api data.
    • \n
  • Rework JIRA WPB-1374 Updated activation timestamp to use GMT/UTC.
    • \n
  • Bug fix: JIRA WPB-1377 Reseller option is now set on first call to either the front end or wp_login.
    • \n
  • Bug fix: Adjusted handling for image purchases when errors occur.
    • \n
  • Bug fix: JIRA WPB-1365 Purchase link on editing a page goes to wrong link.
    • \n
  • Bug fix: JIRA WPB-1368 Inspirations step 0 text refers to nonexisting help tabs.
    • \n
  • Rework: JIRA WPB-1378 Adjusted formatting of footer in Dashboard.
    • \n
  • Rework: JIRA WPB-1369 Update minus signs on \'Transaction History\'.
    • \n
  • New feature: JIRA WPB-1379 On the transactions page, show the reseller that processed the credits.
    • \n
  • Bug fix: Count of \'All\' pages inaccurate on \'All pages\'.
    • \n
  • Bug fix: JIRA WPB-1367 Updated link for \'Lost your BoldGrid Connect Key?\'.
    • \n
\n

1.0.1

\n
    \n
  • Bug fix: JIRA WPB-1374 Updated activation timestamp to include timezone in UTC.
    • \n
  • Bug fix: Attribution page shows style tags.
    • \n
  • Bug fix: Strict Standards fix for wpksesallowed_html.
    • \n
  • Bug fix: Fixed incorrect link.
    • \n
\n

1.0

\n
    \n
  • Initial public release.
    • \n
\n\";s:14:\"upgrade_notice\";s:311:\"

1.3

\n

Version 1.3 has been released with a redesigned Inspiration phase. For more information on this change and others, please visit our blog at https://www.boldgrid.com/boldgrid-1-3-released/ .

\n

1.0.2

\n

Users should upgrade to version 1.0.2 to ensure proper BoldGrid theme updates.

\n\";}s:7:\"siteurl\";s:25:\"https://www.boldgrid.com/\";s:13:\"compatibility\";s:58667:\"{\"5.5\":{\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.4.2\":{\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.4.1\":{\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.4\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.3.4\":{\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.3.3\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.3.2\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.3.1\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.3\":{\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2.7\":{\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2.6\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2.5\":{\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2.4\":{\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2.3\":{\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2.2\":{\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2.1\":{\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.2\":{\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.1.6\":{\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.1.5\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.1.4\":{\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.1.3\":{\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.1.2\":{\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.1.1\":{\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.1\":{\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.9\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.8\":{\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.7\":{\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.6\":{\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.5\":{\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.4\":{\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.3\":{\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.2\":{\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.10\":{\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0.1\":{\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"5.0\":{\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.9\":{\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.8\":{\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.7\":{\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.6\":{\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.5\":{\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.4\":{\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.3\":{\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.2\":{\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.14\":{\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.13\":{\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.12\":{\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.11\":{\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.10\":{\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9.1\":{\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.9\":{\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.9\":{\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.8\":{\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.7\":{\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.6\":{\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.5\":{\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.4\":{\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.3\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.2\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.10\":{\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8.1\":{\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.8\":{\"1.4.0.1\":[100,12],\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.9\":{\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.8\":{\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.7\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.6\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.5\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.4\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.3\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.2\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.13\":{\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.12\":{\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.11\":{\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.10\":{\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7.1\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.7\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.9\":{\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.8\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.7\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.6\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.5\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.4\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.3\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.2\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.12\":{\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.11\":{\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.10\":{\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6.1\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.6\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.9\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.8\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.7\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.6\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.5\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.4\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.3\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.2\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.12\":{\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.11\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.10\":{\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5.1\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.5\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.4.9\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.4.8\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.4.7\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.4.6\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.4.5\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.4.10\":{\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]},\"4.3.1\":{\"0.29\":[100,12],\"1.0.2\":[100,12],\"1.0.3\":[100,12],\"1.0.4\":[100,12],\"1.0.5\":[100,12],\"1.0.6\":[100,12],\"1.0.7\":[100,12],\"1.0.8.1\":[100,12],\"1.0.9.1\":[100,12],\"1.0.9.2\":[100,12],\"1.0.10\":[100,12],\"1.0.11\":[100,12],\"1.0.12.1\":[100,12],\"1.1.1\":[100,12],\"1.1.2.1\":[100,12],\"1.1.2.3\":[100,12],\"1.1.1.1\":[100,12],\"1.1.3\":[100,12],\"1.1.4\":[100,12],\"1.1.5\":[100,12],\"1.1.6\":[100,12],\"1.1.7\":[100,12],\"1.1.8\":[100,12],\"1.2\":[100,12],\"1.2.1\":[100,12],\"1.2.2\":[100,12],\"1.2.4\":[100,12],\"1.2.5\":[100,12],\"1.2.8\":[100,12],\"1.2.9\":[100,12],\"1.2.11\":[100,12],\"1.2.13\":[100,12],\"1.3\":[100,12],\"1.3.1\":[100,12],\"1.3.2\":[100,12],\"1.3.3\":[100,12],\"1.3.4\":[100,12],\"1.3.5\":[100,12],\"1.3.6\":[100,12],\"1.3.7\":[100,12],\"1.3.8\":[100,12],\"1.3.9\":[100,12],\"1.3.10\":[100,12],\"1.4\":[100,12],\"1.4.1\":[100,12],\"1.4.2\":[100,12],\"1.4.3\":[100,12],\"1.4.4\":[100,12],\"1.4.5\":[100,12],\"1.4.6\":[100,12],\"1.4.0.1\":[100,12],\"1.4.7\":[100,95],\"1.4.8\":[100,95],\"1.4.9\":[100,95],\"1.4.10\":[100,95],\"1.4.11\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95],\"1.5.2\":[100,95],\"1.5.3\":[100,95],\"1.5.4\":[100,95],\"1.5.5\":[100,95],\"1.5.6-rc.1\":[100,95],\"1.5.6\":[100,95],\"1.5.7\":[100,95],\"1.5.8\":[100,95],\"1.6.0\":[100,95],\"1.6.1\":[100,95],\"1.6.2\":[100,95],\"1.6.3\":[100,95],\"1.6.4\":[100,95],\"1.6.5\":[100,95],\"1.7.0-rc.1\":[100,95],\"1.7.0-rc.2\":[100,95],\"2.0.0-rc.1\":[100,95],\"2.0.0-rc.2\":[100,95],\"2.0.0-rc.3\":[100,95],\"2.0.0\":[100,95],\"2.0.1\":[100,95],\"2.0.2\":[100,95],\"2.0.3\":[100,95],\"2.0.4\":[100,95],\"2.0.5\":[100,95],\"2.0.6\":[100,95],\"2.0.7\":[100,95],\"2.1.0-rc.1\":[100,95],\"2.1.0\":[100,95],\"2.1.1\":[100,95],\"2.2.0\":[100,95],\"2.2.1\":[100,95],\"2.2.2\":[100,95],\"2.3.0\":[100,95],\"2.3.1\":[100,95],\"2.4.0\":[100,95],\"2.4.1\":[100,95],\"2.4.2\":[100,95],\"2.4.3\":[100,95],\"2.4.4\":[100,95]}}\";s:6:\"rating\";i:100;s:11:\"num_ratings\";i:100000;s:4:\"tags\";a:5:{s:11:\"inspiration\";s:11:\"Inspiration\";s:13:\"customization\";s:13:\"Customization\";s:5:\"build\";s:5:\"Build\";s:6:\"create\";s:6:\"Create\";s:6:\"design\";s:6:\"Design\";}s:7:\"banners\";a:2:{s:3:\"low\";s:65:\"//repo.boldgrid.com/assets/banner-inspirations-banner-772x250.png\";s:4:\"high\";s:66:\"//repo.boldgrid.com/assets/banner-inspirations-banner-1544x500.png\";}s:11:\"new_version\";s:5:\"2.4.4\";s:4:\"name\";s:21:\"BoldGrid Inspirations\";s:4:\"slug\";s:21:\"boldgrid-inspirations\";s:17:\"short_description\";s:135:\"BoldGrid Inspirations is an inspiration-driven plugin to assist with creating a fresh new website, or to customize an existing website.\";s:12:\"last_updated\";s:19:\"2020-09-22 18:08:09\";s:6:\"author\";s:65:\"BoldGrid \";s:5:\"icons\";a:3:{s:2:\"1x\";s:71:\"https://repo.boldgrid.com/assets/icon-boldgrid-inspirations-128x128.png\";s:2:\"2x\";s:71:\"https://repo.boldgrid.com/assets/icon-boldgrid-inspirations-256x256.png\";s:3:\"svg\";s:71:\"https://repo.boldgrid.com/assets/icon-boldgrid-inspirations-128x128.svg\";}s:5:\"added\";s:10:\"2015-03-19\";s:3:\"url\";s:25:\"https://www.boldgrid.com/\";s:15:\"active_installs\";b:1;s:13:\"download_link\";s:111:\"https://api.boldgrid.com/api/open/getAsset?id=1131870&installed_plugin_version=2.4.4&installed_wp_version=5.5.1\";}s:16:\"boldgrid-gallery\";O:8:\"stdClass\":24:{s:5:\"title\";s:16:\"BoldGrid Gallery\";s:7:\"version\";s:5:\"1.5.1\";s:8:\"asset_id\";i:1118061;s:12:\"release_date\";s:19:\"2020-07-27 20:25:23\";s:19:\"requires_wp_version\";s:3:\"4.4\";s:17:\"tested_wp_version\";s:3:\"5.5\";s:8:\"sections\";a:4:{s:11:\"description\";s:82:\"

BoldGrid Gallery is a standalone plugin used for slideshows and galleries.

\n\";s:12:\"installation\";s:183:\"
    \n

  1. Upload the entire boldgrid-gallery folder to the /wp-content/plugins/ directory.

    2. \n

  2. Activate the plugin through the Plugins menu in WordPress.

    3. \n
\n\";s:9:\"changelog\";s:3079:\"

1.5.1

\n
    \n
  • Bug fix: Fix update class.
    • \n
  • Bug fix: Trying to access array offset on value of type bool.
    • \n
\n

1.5

\n
    \n
  • Update: Bump version.
    • \n
\n

1.4.3

\n
    \n
  • Update: JIRA WPB-3292 Updated plugin URI.
    • \n
\n

1.4.2

\n
    \n
  • Bug fix: JIRA WPB-3161 Fixed auto plugin update.
    • \n
\n

1.4.1

\n
    \n
  • Bug fix: JIRA WPB-3151 Added check and load before using getplugindata() for updates.
    • \n
  • Update: JIRA WPB-3112 Updated wc-gallery: 1.52 => 1.55.
    • \n
\n

1.4

\n
    \n
  • Bug fix: JIRA WPB-2912 Fixed issue when installing plugins from the Tools Import page.
    • \n
\n

1.3.1

\n
    \n
  • Bug fix: JIRA WPB-2892 Fixed plugin update checks for some scenarios (WP-CLI, Plesk, etc).
    • \n
  • Testing: JIRA WPB-2744 Tested on WordPress 4.7.
    • \n
  • Misc: JIRA WPB-2503 Added plugin requirements to readme.txt file.
    • \n
\n

1.3

\n
    \n
  • Update: Bump Version.
    • \n
\n

1.2.3

\n
    \n
  • Misc: JIRA WPB-2344 Updated readme.txt for Tested up to 4.6.1.
    • \n
  • Bug fix: JIRA WPB-2336 Load BoldGrid settings from the correct WP option (site/blog).
    • \n
  • Update: JIRA WPB-2368 Version constant is now set from plugin file.
    • \n
\n

1.2.2

\n
    \n
  • Bug fix: JIRA WPB-2310 Removed broken plugin Settings link. Pending review on WPB-2309.
    • \n
\n

1.2.1

\n
    \n
  • Misc: JIRA WPB-2256 Updated readme.txt for Tested up to: 4.6.
    • \n
  • Rework: JIRA WPB-1825 Formatting.
    • \n
\n

1.2

\n
    \n
  • Bug fix: JIRA WPB-2114 Fixed gallery displaying in editor on wordpress 4.6.
    • \n
  • Bug fix: JIRA WPB-2114 Fixing ordering of gallery items.
    • \n
\n

1.1.2

\n
    \n
  • New feature: JIRA WPB-2037 Added capability for auto-updates by BoldGrid API response.
    • \n
  • Update: JIRA WPB-2024 Updated wc-gallery: 1.48 => 1.52.
    • \n
  • Misc: Updated editor.js to pass JSHint.
    • \n
\n

1.1.1

\n
    \n
  • Update: JIRA WPB-1884 Passed WordPress 4.5.1 testing.
    • \n
  • Bug fix: JIRA WPB-1893 JS errors in console when viewing attachments.
    • \n
\n

1.1.0.1

\n
    \n
  • Bug fix: JIRA WPB-1816 Fixed update class interference with the Add Plugins page.
    • \n
\n

1.1

\n
    \n
  • Bug fix: JIRA WPB-1809 Fixed undefined index \"action\" for some scenarios. Optimized update class and addressed CodeSniffer items.
    • \n
\n

1.0.4

\n
    \n
  • Misc: JIRA WPB-1361 Added license file.
    • \n
  • Bug Fix: JIRA WPB-1646 Fixing Issues where masonry gallery was not WYSIWYG.
    • \n
\n

1.0.3

\n
    \n
  • Update: JIRA WPB-1611 Updated wc-gallery: 1.40 => 1.48.
    • \n
  • Rework: JIRA WPB-1617 Updated require and include statements for standards.
    • \n
\n

1.0.2

\n
    \n
  • Bug fix: JIRA WPB-1553 Changed DIR to dirname( FILE ) for PHP <=5.2.
    • \n
  • Misc JIRA WPB-1468 Updated readme.txt for Tested up to: 4.4.1
    • \n
\n

1.0.1

\n
    \n
  • New feature: JIRA WPB-1363 Updated readme.txt for WordPress standards.
    • \n
\n

1.0

\n
    \n
  • Initial public release.
    • \n
\n\";s:14:\"upgrade_notice\";s:1:\"\n\";}s:7:\"siteurl\";s:24:\"http://www.boldgrid.com/\";s:13:\"compatibility\";s:2163:\"{\"5.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95]},\"4.8.1\":{\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.3\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.2\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7.1\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.7\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.3\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.2\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6.1\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.9\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.8\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.7\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.4\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.3\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.2\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5.1\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.9\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.8\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.7\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.6\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.5\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.4.10\":{\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]},\"4.3.1\":{\"0.4\":[100,12],\"1.0\":[100,12],\"1.0.1\":[100,12],\"1.0.2\":[100,12],\"1.0.3\":[100,12],\"1.0.4\":[100,12],\"1.1.0.1\":[100,12],\"1.1.1\":[100,12],\"1.1.2\":[100,12],\"1.2\":[100,12],\"1.2.1\":[100,12],\"1.2.2\":[100,12],\"1.2.3\":[100,12],\"1.3\":[100,12],\"1.3.1\":[100,12],\"1.3.2\":[100,12],\"1.4\":[100,12],\"1.4.1\":[100,12],\"1.4.2\":[100,12],\"1.4.3\":[100,95],\"1.5\":[100,95],\"1.5.1\":[100,95]}}\";s:6:\"rating\";i:100;s:11:\"num_ratings\";i:100000;s:4:\"tags\";a:4:{s:7:\"gallery\";s:7:\"Gallery\";s:6:\"slider\";s:6:\"Slider\";s:9:\"slideshow\";s:9:\"Slideshow\";s:7:\"masonry\";s:7:\"Masonry\";}s:7:\"banners\";a:2:{s:3:\"low\";s:53:\"//repo.boldgrid.com/assets/banner-gallery-772x250.png\";s:4:\"high\";s:54:\"//repo.boldgrid.com/assets/banner-gallery-1544x500.png\";}s:11:\"new_version\";s:5:\"1.5.1\";s:4:\"name\";s:16:\"BoldGrid Gallery\";s:4:\"slug\";s:16:\"boldgrid-gallery\";s:17:\"short_description\";s:74:\"BoldGrid Gallery is a standalone plugin used for slideshows and galleries.\";s:12:\"last_updated\";s:19:\"2020-07-27 20:25:23\";s:6:\"author\";s:67:\"BoldGrid.com\";s:5:\"icons\";a:3:{s:2:\"1x\";s:66:\"https://repo.boldgrid.com/assets/icon-boldgrid-gallery-128x128.png\";s:2:\"2x\";s:66:\"https://repo.boldgrid.com/assets/icon-boldgrid-gallery-256x256.png\";s:3:\"svg\";s:66:\"https://repo.boldgrid.com/assets/icon-boldgrid-gallery-128x128.svg\";}s:5:\"added\";s:10:\"2015-03-19\";s:3:\"url\";s:24:\"http://www.boldgrid.com/\";s:15:\"active_installs\";b:1;s:13:\"download_link\";s:80:\"https://api.boldgrid.com/api/open/getAsset?id=1118061&installed_wp_version=5.5.1\";}}','no'),(137,'boldgrid_backup_id','6ef2bc45','no'),(138,'boldgrid_backup_settings','a:13:{s:8:\"schedule\";a:10:{s:10:\"dow_sunday\";i:0;s:10:\"dow_monday\";i:0;s:11:\"dow_tuesday\";i:0;s:13:\"dow_wednesday\";i:0;s:12:\"dow_thursday\";i:0;s:10:\"dow_friday\";i:0;s:12:\"dow_saturday\";i:0;s:5:\"tod_h\";i:1;s:5:\"tod_m\";i:50;s:5:\"tod_a\";s:2:\"AM\";}s:15:\"retention_count\";i:5;s:18:\"notification_email\";s:27:\"techtrivialpvtltd@gmail.com\";s:13:\"notifications\";a:3:{s:6:\"backup\";i:1;s:7:\"restore\";i:1;s:10:\"site_check\";b:1;}s:11:\"auto_backup\";i:1;s:13:\"auto_rollback\";i:1;s:6:\"remote\";a:1:{s:5:\"local\";a:1:{s:7:\"enabled\";b:1;}}s:14:\"exclude_tables\";a:0:{}s:24:\"folder_exclusion_include\";s:18:\"WPCORE,/wp-content\";s:24:\"folder_exclusion_exclude\";s:17:\".git,node_modules\";s:10:\"site_check\";a:4:{s:7:\"enabled\";b:1;s:6:\"logger\";b:1;s:13:\"auto_recovery\";b:0;s:8:\"interval\";i:15;}s:10:\"encrypt_db\";b:0;s:16:\"backup_directory\";s:30:\"/home/techtr18/boldgrid_backup\";}','no'),(139,'_transient_timeout_boldgrid_backup_system_zip_test','1601847712','no'),(140,'_transient_boldgrid_backup_system_zip_test','1','no'),(143,'jetpack_sync_settings_disable','0','yes'),(144,'_transient_timeout_jetpack_idc_allowed','1601764912','no'),(145,'_transient_jetpack_idc_allowed','1','no'),(146,'widget_boldgrid_component_post','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(147,'widget_boldgrid_component_postlist','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(152,'boldgrid_editor','a:2:{s:19:\"has_flushed_rewrite\";b:1;s:19:\"has_checked_version\";i:0;}','yes'),(153,'bglib_activity','a:1:{s:5:\"bgppb\";a:1:{s:14:\"dedicated_user\";i:2;}}','yes'),(154,'bglib_rating_prompt','a:1:{i:0;a:4:{s:6:\"plugin\";s:5:\"bgppb\";s:4:\"name\";s:14:\"dedicated_user\";s:6:\"slides\";a:4:{s:5:\"start\";a:2:{s:4:\"text\";s:238:\"Great job keeping your plugin up to date and thank you for being a dedicated BoldGrid user. If you feel you\'re getting really good value from the Post and Page Builder by BoldGrid, could you do us a favor and rate us 5 stars on WordPress?\";s:9:\"decisions\";a:3:{s:9:\"sure_will\";a:3:{s:4:\"text\";s:17:\"Yes, I sure will!\";s:4:\"link\";s:67:\"https://wordpress.org/support/plugin/post-and-page-builder/reviews/\";s:5:\"slide\";s:6:\"thanks\";}s:19:\"maybe_still_testing\";a:3:{s:4:\"text\";s:42:\"Maybe later, I\'m still testing the plugin.\";s:6:\"snooze\";i:604800;s:5:\"slide\";s:11:\"maybe_later\";}s:11:\"already_did\";a:2:{s:4:\"text\";s:13:\"I already did\";s:5:\"slide\";s:11:\"already_did\";}}}s:6:\"thanks\";a:1:{s:4:\"text\";s:405:\"Thanks! A new page should have opened to the Post and Page Builder ratings page on WordPress.org. You will need to log in to your WordPress.org account before you can post a review. If the page didn\'t open, please click the following link: https://wordpress.org/support/plugin/post-and-page-builder/reviews/\";}s:11:\"maybe_later\";a:1:{s:4:\"text\";s:240:\"No problem, maybe now is not a good time. We want to be your WordPress page builder of choice. If you\'re experiencing a problem or want to make a suggestion, please click here.\";}s:11:\"already_did\";a:1:{s:4:\"text\";s:280:\"Thank you for the previous rating! You can help us to continue improving the Post and Page Builder by reporting any bugs or submitting feature requests here. Thank you for using the Post and Page Builder by BoldGrid!\";}}s:10:\"time_added\";i:1601761313;}}','yes'),(155,'_site_transient_timeout_boldgrid_available','1601763208','no'),(156,'_site_transient_boldgrid_available','1','no'),(157,'_site_transient_timeout_boldgrid_ppbp_version_data','1601790113','no'),(158,'_site_transient_boldgrid_ppbp_version_data','O:8:\"stdClass\":4:{s:6:\"status\";i:200;s:7:\"message\";s:2:\"OK\";s:6:\"result\";O:8:\"stdClass\":1:{s:4:\"data\";O:8:\"stdClass\":13:{s:5:\"title\";s:29:\"Post and Page Builder Premium\";s:7:\"version\";s:5:\"1.0.4\";s:8:\"asset_id\";i:1034507;s:12:\"release_date\";s:19:\"2019-11-11 21:26:07\";s:19:\"requires_wp_version\";s:3:\"4.7\";s:17:\"tested_wp_version\";s:3:\"5.3\";s:8:\"sections\";s:7313:\"{\"description\":\"

What is the Post and Page Builder by BoldGrid?<\\/h4>\\n\\n

The Post and Page Builder is an intuitive drag and drop editor plugin and the easiest way to create and edit pages for any theme. Whether you are new to WordPress or consider yourself a pro, BoldGrid solutions will make your WordPress life better. Stop dealing with site-breaking shortcodes and theme restricted editors. You are going to love just how fast and easily you can create beautiful websites now.<\\/p>\\n\\n

Try out the BoldGrid Demo<\\/a> on Cloud WordPress to see for yourself!<\\/p>\\n\\n

[youtube https:\\/\\/youtu.be\\/QoIb7OhV9ys?rel=0]<\\/p>\\n\\n

Features<\\/h4>\\n\\n
    \\n
  • Drag and Drop Editing<\\/strong> - Create simple or complex layouts with our unique editing experience<\\/li>\\n
  • BoldGrid Blocks<\\/strong> - Hundreds of professional layout designs to work from<\\/li>\\n
  • 100% Mobile-friendly<\\/strong> - Responsive layouts and controls to change the design per device<\\/li>\\n
  • Google Fonts<\\/strong> - Change font family, font size, font color, letter spacing, line height and more<\\/li>\\n
  • Theme Compatibility<\\/strong> - Our WordPress Page Builder is designed to work with any WordPress Theme<\\/li>\\n
  • Custom Backgrounds<\\/strong> - Add background images, gradient backgrounds, patterns, overlays, and background colors<\\/li>\\n
  • Fast and Free Support<\\/strong> - Growing Community and knowledge base<\\/li>\\n
  • Animations<\\/strong> - Add effects as the user scrolls down the page with Animate.css or background parallax scroll effects<\\/li>\\n
  • Advanced Controls<\\/strong> - Add margin, padding, box shadows, borders, alignment and more to almost any element<\\/li>\\n
  • Bootstrap Grid<\\/strong> - Drag and drop controls for bootstrap rows and columns elements<\\/li>\\n
  • Add Custom CSS Classes<\\/strong> - Complete control over any element<\\/li>\\n
  • Clean, Simple Markup<\\/strong> - Easily create a professionally coded template without experience<\\/li>\\n
  • Google Maps<\\/strong> - Embed and customize maps into your post or page<\\/li>\\n
  • Web Components<\\/strong> - High quality reusable and customizable HTML elements<\\/li>\\n
  • Font Awesome Icons<\\/strong> - Insert and customize any Font Awesome icons<\\/li>\\n
  • CSS Grid<\\/strong> - Full width, column and row based layouts<\\/li>\\n
  • Image Editing<\\/strong> - Apply image filters and automatically crop images<\\/li>\\n
  • Button Designs<\\/strong> - Fully customizable button designs<\\/li>\\n
  • Custom Post Types<\\/strong> - Save and reuse full page layouts or BoldGrid Block designs<\\/li>\\n
  • WordPress Editor Integration<\\/strong> - Integrated into TinyMCE so you can keep the same workflow<\\/li>\\n
  • No Need for Shortcodes!<\\/strong> - Faster page loads by saving your custom HTML5 elements<\\/li>\\n<\\/ul>\\n\\n

    Additional Features when used with other BoldGrid plugins:<\\/p>\\n\\n

      \\n
    • Dozens of free layout templates<\\/li>\\n
    • Integrated with professional image banks<\\/li>\\n
    • Contact Forms<\\/li>\\n
    • On-page SEO recommendations for targeted search phrase<\\/li>\\n<\\/ul>\\n\\n

      Visit our website to learn more about additional BoldGrid plugins<\\/a> to further improve your WordPress experience!<\\/p>\\n\\n

      People Love BoldGrid<\\/h4>\\n\\n

      \\\"It\'s really the perfect starting point for just about any web project, allowing users to get their site up and running in very short time. \\\" - Digital.com<\\/p>\\n\\n

      \\\"BoldGrid is a great extension to WordPress that will make my job a lot easier and faster while creating custom layouts and pages.\\\" - Webhostingmedia.net<\\/p>\\n\\n

      \\\"Well, I have seen many site builders but this is the only one that provides so many features.\\\" - Woblogger.com<\\/p>\\n\\n

      A Post and Page Builder That Works With Your Theme and Plugins<\\/h4>\\n\\n

      The Post and Page Builder by BoldGrid is designed to work with almost any WordPress theme. Add it to your existing website today, or try a BoldGrid theme for your new website. Alternatively, consider upgrading and using the powerful BoldGrid framework theme (available in Premium subscription) as an excellent time saver for agencies and developers.<\\/p>\\n\\n

      A Post and Page Builder Stuffed With Pre-Designed Templates & Blocks<\\/h4>\\n\\n

      Create layouts and pages faster and easier than ever with Blocks by BoldGrid. Blocks are pre-built page sections consisting of various layouts of rows and columns prepopulated with content that can be edited visually or with HTML and CSS. Blocks utilize a wide variety of content that can be completely customized to fit your needs such as icons, buttons, free and premium images, font packs, and more.<\\/p>\\n\\n

      A Post and Page Builder That Is Faster Than The Rest<\\/h4>\\n\\n

      The Post and Page Builder by BoldGrid is designed to create pages that load fast. BoldGrid ditches shortcodes in favor of clean markup that can be served quickly. That also means BoldGrid code is easy to assess and customize.<\\/p>\\n\\n

      Coming Soon \\/ Maintenance Page<\\/h4>\\n\\n

      Great for making \\\"under construction\\\" or \\\"coming soon\\\" pages. You can create a simple page within minutes by using free professionally designed WordPress Blocks.<\\/p>\\n\\n

      Bootstrap WYSIWYG Post & Page Builder for WordPress<\\/h4>\\n\\n

      Our drag and drop system is built on the Bootstrap Grid. You can drag columns, rows, and containers around your pages to make quick updates to pages. Advanced CSS controls allow you to make pixel perfect designs.<\\/p>\\n\\n

      Create Custom Color Palette<\\/h4>\\n\\n

      Choose your brand\'s colors and we\'ll help your design stay unified. Our unique color palette system is built with SASS and allows you to change all the colors on your site. You don\'t have to choose from a few presets anymore!<\\/p>\\n\",\"installation\":\"

      Minimum Requirements<\\/h4>\\n\\n
        \\n
      • PHP version 5.4 or greater<\\/li>\\n
      • WordPress 4.4 or greater<\\/li>\\n<\\/ul>\\n\\n

        Manually<\\/h4>\\n\\n
          \\n
        1. Upload the entire post-and-page-builder folder to the \\/wp-content\\/plugins\\/ directory.<\\/li>\\n
        2. Activate the plugin through the Plugins menu in WordPress.<\\/li>\\n<\\/ol>\\n\\n

          You will find a \'Post and Page Builder\' menu in your WordPress admin panel and find most features within the\\nWordPress Editor.<\\/p>\\n\",\"changelog\":\"

          1.0.4<\\/h4>\\n\\n

          Release date: November 11th, 2019<\\/p>\\n\\n

            \\n
          • Fix: Order posts by date instead of id.<\\/li>\\n<\\/ul>\\n\\n

            1.0.3<\\/h4>\\n\\n

            Release date: October 30th, 2019<\\/p>\\n\\n

              \\n
            • Update: Optimizing build files.<\\/li>\\n<\\/ul>\\n\\n

              1.0.2<\\/h4>\\n\\n

              Release date: December 5th, 2018<\\/p>\\n\\n

                \\n
              • Bug fix: Fixed updating plugin via ajax<\\/li>\\n<\\/ul>\\n\\n

                1.0.1<\\/h4>\\n\\n

                Release Date: December 4th, 2018<\\/p>\\n\\n

                  \\n
                • Bug Fix: Fixing post excerpt wrapping element<\\/li>\\n<\\/ul>\\n\\n

                  1.0.0<\\/h4>\\n\\n

                  Release Date: October 16th, 2018<\\/p>\\n\\n

                    \\n
                  • New feature: Slider Components<\\/li>\\n
                  • New feature: Post List Widget<\\/li>\\n
                  • New feature: Single Post Widget<\\/li>\\n<\\/ul>\\n\"}\";s:7:\"siteurl\";s:24:\"http://www.boldgrid.com/\";s:13:\"compatibility\";s:6162:\"{\"5.2.4\":{\"1.0.4\":[100,95]},\"5.2.3\":{\"1.0.4\":[100,95]},\"5.2.2\":{\"1.0.4\":[100,95]},\"5.2.1\":{\"1.0.4\":[100,95]},\"5.2\":{\"1.0.4\":[100,95]},\"5.1.3\":{\"1.0.4\":[100,95]},\"5.1.2\":{\"1.0.4\":[100,95]},\"5.1.1\":{\"1.0.4\":[100,95]},\"5.1\":{\"1.0.4\":[100,95]},\"5.0.7\":{\"1.0.4\":[100,95]},\"5.0.6\":{\"1.0.4\":[100,95]},\"5.0.5\":{\"1.0.4\":[100,95]},\"5.0.4\":{\"1.0.4\":[100,95]},\"5.0.3\":{\"1.0.4\":[100,95]},\"5.0.2\":{\"1.0.4\":[100,95]},\"5.0.1\":{\"1.0.4\":[100,95]},\"5.0\":{\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.9\":{\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.8\":{\"1.0.0-alpha.0\":[100,12],\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.7\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.6\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.5\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.4\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.3\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.2\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.12\":{\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.11\":{\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.10\":{\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9.1\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.9\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8.7\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8.6\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8.5\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8.4\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8.3\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8.2\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8.1\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.8\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.9\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.8\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.7\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.6\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.5\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.4\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.3\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.2\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.11\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.10\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7.1\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.7\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]},\"4.6.12\":{\"1.0.0-rc.1\":[100,95],\"1.0.0-rc.2\":[100,95],\"1.0.0-rc.3\":[100,95],\"1.0.0-rc.4\":[100,95],\"1.0.0\":[100,95],\"1.0.1\":[100,95],\"1.0.2\":[100,95],\"1.0.3\":[100,95],\"1.0.4\":[100,95]}}\";s:6:\"rating\";i:100;s:11:\"num_ratings\";i:100000;s:4:\"tags\";s:153:\"{\"boldgrid\":\"Boldgrid\",\"page builder\":\"Page builder\",\"drag and drop\":\"Drag and drop\",\"tinymce\":\"Tinymce\",\"editor\":\"Editor\",\"landing page\":\"Landing page\"}\";s:7:\"banners\";s:137:\"{\"low\":\"//ps.w.org/post-and-page-builder/assets/banner-772x250.png\",\"high\":\"//ps.w.org/post-and-page-builder/assets/banner-1544x500.png\"}\";}}s:7:\"updated\";i:1601761313;}','no'),(180,'can_compress_scripts','1','no'),(181,'_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:\"Fri, 02 Oct 2020 09:34: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: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.6-alpha-49085\";s:7:\"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:57:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:38:\"The Month in WordPress: September 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wordpress.org/news/2020/10/the-month-in-wordpress-september-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 02 Oct 2020 09:34: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: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=9026\";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:363:\"This month was characterized by some exciting announcements from the WordPress core team! Read on to catch up with all the WordPress news and updates from September.  WordPress 5.5.1 Launch On September 1, the  Core team released WordPress 5.5.1. This maintenance release included several bug fixes for both core and the editor, and many other […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Hari Shanker R\";s: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:8713:\"\n

                    This month was characterized by some exciting announcements from the WordPress core team! Read on to catch up with all the WordPress news and updates from September. 

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

                    WordPress 5.5.1 Launch

                    \n\n\n\n

                    On September 1, the  Core team released WordPress 5.5.1. This maintenance release included several bug fixes for both core and the editor, and many other enhancements. You can update to the latest version directly from your WordPress dashboard or download it directly from WordPress.org. The next major release will be version 5.6.

                    \n\n\n\n

                    Want to be involved in the next release?  You can help to build WordPress Core by following the Core team blog, and joining the #core channel in the Making WordPress Slack group.

                    \n\n\n\n

                    Gutenberg 9.1, 9.0, and 8.9 are out

                    \n\n\n\n

                    The core team launched version 9.0 of the Gutenberg plugin on September 16, and version 9.1 on September 30. Version 9.0 features some useful enhancements — like a new look for the navigation screen (with drag and drop support in the list view) and modifications to the query block (including search, filtering by author, and support for tags). Version 9.1 adds improvements to global styles, along with improvements for the UI and several blocks. Version 8.9 of Gutenberg, which came out earlier in September, enables the block-based widgets feature (also known as block areas, and was previously available in the experiments section) by default — replacing the default WordPress widgets to the plugin. You can find out more about the Gutenberg roadmap in the What’s next in Gutenberg blog post.

                    \n\n\n\n

                    Want to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.

                    \n\n\n\n

                    Twenty Twenty One is the WordPress 5.6 default theme

                    \n\n\n\n

                    Twenty Twenty One, the brand new default theme for WordPress 5.6, has been announced! Twenty Twenty One is designed to be a blank canvas for the block editor, and will adopt a straightforward, yet refined, design. The theme has a limited color palette: a pastel green background color, two shades of dark grey for text, and a native set of system fonts. Twenty Twenty One will use a modified version of the Seedlet theme as its base. It will have a comprehensive system of nested CSS variables to make child theming easier, a native support for global styles, and full site editing. 

                    \n\n\n\n

                    Follow the Make/Core blog if you wish to contribute to Twenty Twenty One. There will be weekly meetings every Monday at 15:00 UTC and triage sessions every Friday at 15:00 UTC in the #core-themes Slack channel. Theme development will happen on GitHub. 

                    \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:\"9026\";s: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:57:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.5.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/2020/09/wordpress-5-5-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, 01 Sep 2020 19:13: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: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=8979\";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:460:\"WordPress 5.5.1 is now available! This maintenance release features 34 bug fixes, 5 enhancements, and 5 bug fixes for the block editor. These bugs affect WordPress version 5.5, so you’ll want to upgrade. You can download WordPress 5.5.1 directly, or visit the Dashboard → Updates screen and click Update Now. If your sites support automatic background updates, they’ve already started the update process. […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"Jb Audras\";s: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:9020:\"\n

                    WordPress 5.5.1 is now available!

                    \n\n\n\n

                    This maintenance release features 34 bug fixes, 5 enhancements, and 5 bug fixes for the block editor. These bugs affect WordPress version 5.5, so you’ll want to upgrade.

                    \n\n\n\n

                    You can download WordPress 5.5.1 directly, or visit the Dashboard → Updates screen and click Update Now. If your sites support automatic background updates, they’ve already started the update process.

                    \n\n\n\n

                    WordPress 5.5.1 is a short-cycle maintenance release. The next major release will be version 5.6.

                    \n\n\n\n

                    To see a full list of changes, you can browse the list on Trac, read the 5.5.1 RC1 and 5.5.1 RC2 posts, or visit the 5.5.1 documentation page.

                    \n\n\n\n

                    Thanks and props!

                    \n\n\n\n

                    The 5.5.1 release was led by @audrasjb, @azhiyadev, @davidbaumwald, @desrosj, @johnbillion, @planningwrite, @sergeybiryukov and @whyisjake.

                    \n\n\n\n

                    Thank you to everyone who helped make WordPress 5.5.1 happen:

                    \n\n\n\nAmit Dudhat, Andrea Fercia, Andrey “Rarst” Savchenko, Andy Fragen, Angel Hess, avixansa, bobbingwide, Brian Hogg, chunkysteveo, Clayton Collie, David Baumwald, David Herrera, dd32, demetris, Dominik Schilling, dushakov, Earle Davies, Enrique Sánchez, Frankie Jarrett, fullofcaffeine, Garrett Hyder, Gary Jones, gchtr, Hauwa, Herre Groen, Howdy_McGee, Ipstenu (Mika Epstein), Jb Audras, Jeremy Felt, Jeroen Rotty, Joen A., Johanna de Vos, John Blackbourn, John James Jacoby, Jonathan Bossenger, Jonathan Desrosiers, Jonathan Stegall, Joost de Valk, Jorge Costa, Justin Ahinon, Kalpesh Akabari, Kevin Hagerty, Knut Sparhell, Kyle B. Johnson, landau, Laxman Prajapati, Lester Chan, mailnew2ster, Marius L. J., Mark Jaquith, Mark Uraine, Matt Gibson, Michael Beckwith, Mikey Arce, Mohammad Jangda, Mukesh Panchal, Nabil Moqbel, net, oakesjosh, O André, Omar Reiss, Ov3rfly, Paddy, Pascal Casier, Paul Biron, Peter Wilson, rajeshsingh520, Rami Yushuvaev, rebasaurus, riaanlom, Riad Benguella, Rodrigo Arias, rtagliento, salvoaranzulla, Sanjeev Aryal, sarahricker, Sergey Biryukov, Stephen Bernhardt, Steven Stern (sterndata), Thomas M, Timothy Jacobs, TobiasBg, tobifjellner (Tor-Bjorn Fjellner), TwentyZeroTwo, Winstina, wittich, and Yoav Farhi.\n\";s: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:\"8979\";s: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:57:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"The Month in WordPress: August 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://wordpress.org/news/2020/09/the-month-in-wordpress-august-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 01 Sep 2020 09:32:47 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s: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=8983\";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:362:\"August was special for WordPress lovers, as one of the most anticipated releases, WordPress 5.5, was launched. The month also saw several updates from various contributor teams, including the soft-launch of the Learn WordPress project and updates to Gutenberg. Read on to find out about the latest updates from the WordPress world. WordPress 5.5 Launch […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Hari Shanker R\";s: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:9605:\"\n

                    August was special for WordPress lovers, as one of the most anticipated releases, WordPress 5.5, was launched. The month also saw several updates from various contributor teams, including the soft-launch of the Learn WordPress project and updates to Gutenberg. Read on to find out about the latest updates from the WordPress world.

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

                    WordPress 5.5 Launch

                    \n\n\n\n

                    The team launched WordPress 5.5 on August 11. The major release comes with a host of features like automatic updates for plugins and themes, enabling updates over uploaded ZIP files, a block directory, XML sitemaps, block patterns, inline image editing, and lazy-loading images, to name a few. WordPress 5.5 is now available in 50 languages too! You can update to the latest version directly from your WordPress dashboard or download it directly from WordPress.org. Subsequent to the 5.5 release, the 5.5.1 release candidate came out on August 28, which will be followed by its official launch of the minor release on September 1.

                    \n\n\n\n

                    A record 805 people contributed to WordPress 5.5, hailing from 58 different countries. @audrasjb has compiled many more stats like that and they’re well worth a read!

                    \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

                    Gutenberg 8.7 and 8.8

                    \n\n\n\n

                    The core team launched Gutenberg 8.7 and 8.8. Version 8.7 saw many improvements to the Post Block suite, along with other changes like adding a block example to the Buttons block, consistently autosaving edits, and updating the group block description. Version 8.8 offers updates to Global Styles, the Post Block suite, and Template management. The release significantly improves the back-compatibility of the new Widget Screen, and also includes other important accessibility and mobile improvements to user interfaces like the Toolbar, navigation menus, and Popovers. For full details on the latest versions of these Gutenberg releases, visit these posts about 8.7 and 8.8.

                    \n\n\n\n

                    Want to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.

                    \n\n\n\n

                    Check out the brand new Learn WordPress platform!

                    \n\n\n\n

                    Learn WordPress is a brand new cross-team initiative led by the WordPress Community team, with support from the training team, the TV team, and the meta team. This platform is a learning repository on learn.wordpress.org, where WordPress learning content will be made available. Video workshops published on the site will be followed up by supplementary discussion groups based on workshop content. The first of these discussion groups have been scheduled, and you can join an upcoming discussion on the dedicated meetup group. The community team invites members to contribute to the project. You can apply to present a workshop, assist with reviewing submitted workshops, and add ideas for workshops that you would like to see on the site. You can also apply to be a discussion group leader to organize discussions directly through the learn.wordpress.org platform. We are also creating a dedicated Learn WordPress working group and have posted a call for volunteers. Meetup organizers can use Learn WordPress content for their meetup events (without applying as a discussion group leader). Simply ask your meetup group to watch one of the workshops in the weeks leading up to your scheduled event, and then host a discussion group for that content as your event.

                    \n\n\n\n

                    Want to get involved with the Community team? Follow the Community blog, or join them in the #community-events channel in the Making WordPress Slack group. To organize a local WordPress community event, visit the handbook page. 

                    \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:\"8983\";s: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:63:\"\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:28:\"WordPress 5.5 “Eckstine”\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:44:\"https://wordpress.org/news/2020/08/eckstine/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Aug 2020 19:03:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:8:\"Releases\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:3:\"5.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8799\";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:354:\"Version 5.5 \"Eckstine\" of WordPress is available for download or update in your WordPress dashboard. With this release, your site gets new power in three major areas: \nspeed (lazy-loading images), search (sitemaps included by default), and security (auto-updates for plugins and themes), along with many new features and improvements to the block editor.\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"enclosure\";a:3:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:48:\"https://s.w.org/images/core/5.5/auto-updates.mp4\";s:6:\"length\";s:6:\"238264\";s:4:\"type\";s:9:\"video/mp4\";}}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:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:50:\"https://s.w.org/images/core/5.5/block-patterns.mp4\";s:6:\"length\";s:7:\"3518792\";s:4:\"type\";s:9:\"video/mp4\";}}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:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:3:\"url\";s:56:\"https://s.w.org/images/core/5.5/inline-image-editing.mp4\";s:6:\"length\";s:7:\"3145140\";s:4:\"type\";s:9:\"video/mp4\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:71064:\"\n

                    Here it is! Named “Eckstine” in honor of Billy Eckstine, this latest and greatest version of WordPress is available for download or update in your dashboard.

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

                    Welcome to WordPress 5.5.

                    \n\n\n\n

                    In WordPress 5.5, your site gets new power in three major areas:
                    speed, search, and security.

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

                    Speed

                    \n\n\n\n

                    Posts and pages feel faster, thanks to lazy-loaded images.

                    \n\n\n\n

                    Images give your story a lot of impact, but they can sometimes make your site seem slow.

                    \n\n\n\n

                    In WordPress 5.5, images wait to load until they’re just about to scroll into view. The technical term is ‘lazy loading.’

                    \n\n\n\n

                    On mobile, lazy loading can also keep browsers from loading files meant for other devices. That can save your readers money on data — and help preserve battery life.

                    \n\n\n\n

                    Search

                    \n\n\n\n

                    Say hello to your new sitemap.

                    \n\n\n\n

                    WordPress sites work well with search engines.

                    \n\n\n\n

                    Now, by default, WordPress 5.5 includes an XML sitemap that helps search engines discover your most important pages from the very minute you go live.

                    \n\n\n\n

                    So more people will find your site sooner, giving you more time to engage, retain and convert them to subscribers, customers or whatever fits your definition of success.

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

                    Security

                    \n\n\n\n
                    Now you can choose to update plugins and themes automatically–or pick just a few–from the screens you’ve always used.
                    \n\n\n\n

                    Auto-updates for Plugins and Themes

                    \n\n\n\n

                    Now you can set plugins and themes to update automatically — or not! — in the WordPress admin. So you always know your site is running the latest code available.

                    \n\n\n\n

                    You can also turn auto-updates on or off for each plugin or theme you have installed — all on the same screens you’ve always used.

                    \n\n\n\n

                    Update by uploading ZIP files

                    \n\n\n\n

                    If updating plugins and themes manually is your thing, now that’s easier too — just upload a ZIP file.

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

                    Highlights from the block editor

                    \n\n\n\n

                    Once again, the latest WordPress release packs a long list of exciting new features for the block editor. For example:

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

                    Block patterns

                    \n\n\n\n

                    New block patterns make it simple and fun to create complex, beautiful layouts, using combinations of text and media that you can mix and match to fit your story.

                    \n\n\n\n

                    You will also find block patterns in a wide variety of plugins and themes, with more added all the time. Pick any of them from a single place — just click and go!

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

                    The new block directory

                    \n\n\n\n

                    Now it’s easier than ever to find the block you need. The new block directory is built right into the block editor, so you can install new block types to your site without ever leaving the editor.

                    \n\n\n\n

                    Inline image editing

                    \n\n\n\n

                    Crop, rotate, and zoom your photos right from the image block. If you spend a lot of time on images, this could save you hours!

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

                    And so much more.

                    \n\n\n\n

                    The highlights above are a tiny fraction of the new block editor features you’ve just installed. Open the block editor and enjoy!

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

                    Accessibility

                    \n\n\n\n

                    Every release adds improvements to the accessible publishing experience, and that remains true for WordPress 5.5.

                    \n\n\n\n

                    Now you can copy links in media screens and modal dialogs with a button, instead of trying to highlight a line of text.

                    \n\n\n\n

                    You can also move meta boxes with the keyboard, and edit images in WordPress with your assistive device, as it can read you the instructions in the image editor.

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

                    For developers

                    \n\n\n\n

                    5.5 also brings a big box of changes just for developers.

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

                    Server-side registered blocks in the REST API

                    \n\n\n\n

                    The addition of block types endpoints means that JavaScript apps (like the block editor) can retrieve definitions for any blocks registered on the server.

                    \n\n\n\n

                    Defining environments

                    \n\n\n\n

                    WordPress now has a standardized way to define a site’s environment type (staging, production, etc). Retrieve that type with wp_get_environment_type() and execute only the appropriate code.

                    \n\n\n\n

                    Dashicons

                    \n\n\n\n

                    The Dashicons library has received its final update in 5.5. It adds 39 block editor icons along with 26 others.

                    \n\n\n\n

                    Passing data to template files

                    \n\n\n\n

                    The template loading functions (get_header(), get_template_part(), etc.) have a new $args argument. So now you can pass an entire array’s worth of data to those templates.

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

                    More changes for developers

                    \n\n\n\n
                    • The PHPMailer library just got a major update, going from version 5.2.27 to 6.1.6.
                    • Now get more fine-grained control of redirect_guess_404_permalink().
                    • Sites that use PHP’s OPcache will see more reliable cache invalidation, thanks to the new wp_opcache_invalidate() function during updates (including to plugins and themes).
                    • Custom post types associated with the category taxonomy can now opt-in to supporting the default term.
                    • Default terms can now be specified for custom taxonomies in register_taxonomy().
                    • The REST API now officially supports specifying default metadata values through register_meta().
                    • You will find updated versions of these bundled libraries: SimplePie, Twemoji, Masonry, imagesLoaded, getID3, Moment.js, and clipboard.js.
                    \n
                    \n
                    \n
                    \n\n\n\n
                    \n
                    \n\n\n\n
                    \n
                    \n\n\n\n
                    \n

                    The Squad

                    \n\n\n\n

                    Leading this release were Matt Mullenweg, Jake Spurlock, and David Baumwald. Supporting them was this highly enthusiastic release squad:

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

                    Joining the squad throughout the release cycle were 805 generous volunteer contributors who collectively worked on over 523 tickets on Trac and over 1660 pull requests on GitHub.

                    \n\n\n\n

                    Put on a Billy Eckstine playlist, click that update button (or download it directly), and check the profiles of the fine folks that helped:

                    \n\n\nA2 Hosting, a4jp . com, a6software, Aaron D. Campbell, Aaron Jorbin, abderrahman, Abha Thakor, Achal Jain, achbed, Achyuth Ajoy, acosmin, acsnaterse, Adam Silverstein, Addie, addyosmani, adnan.limdi, adrian, airamerica, Ajay Ghaghretiya, Ajit Bohra, akbarhusen, akbarhusen429, Akhilesh Sabharwal, Akira Tachibana, Alain Schlesser, Albert Juhé Lluveras, Alex Concha, Alex Kirk, Alex Lende, Alex Shiels, Ali Shan, ali11007, Allen Snook, amaschas, Amit Dudhat, anbumz, andfinally, Andrea Fercia, Andrea Middleton, Andrea Tarantini, Andrei Draganescu, Andrew Duthie, Andrew Nacin, Andrew Nevins, Andrew Ozz, Andrey \"Rarst\" Savchenko, Andrés Maneiro, Andy Fragen, Andy Meerwaldt, Andy Peatling, Angel Hess, Angela Jin, Angelika Reisiger, Anh Tran, Ankit Gade, Ankit K Gupta, Ankit Panchal, Anne McCarthy, Anthony Burchell, Anthony Hortin, Anton Timmermans, Antonis Lilis, apedog, archon810, argentite, Arpit G Shah, Arslan Ahmed, asalce, ashiagr, ashour, Atharva Dhekne, Aurélien Joahny, aussi, automaton, avixansa, Ayesh Karunaratne, BackuPs, Barry, Barry Ceelen, Bart Czyz, bartekcholewa, bartkalisz, Bastien Ho, Bastien Martinent, bcworkz, bdbch, bdcstr, Ben Dunkle, Bence Szalai, bencroskery, Benjamin Gosset, Benoit Chantre, Bernhard Reiter, BettyJJ, bgermann, bigcloudmedia, bigdawggi, Bill Erickson, Birgir Erlendsson (birgire), Birgit Pauli-Haack, BjornW, bobbingwide, bonger, Boone Gorges, Boris Brdarić, Boy Witthaya, Brandon Kraft, Brandon Payton, Brent Swisher, Brian Hogg, Brian Krogsgard, bruandet, Bunty, Burhan Nasir, caiocrcosta, Cameron Voell, cameronamcintyre, Carike, Carl Wuensche, Carlos Galarza, Carolina Nymark, Caroline Moore, Carrigan, ceyhun, Chad, Chad Butler, Charles Fulton, Chetan Prajapati, Chintan hingrajiya, Chip Snyder, Chloé Bringmann, Chouby, Chris Van Patten, chriscct7, Christian Chung, Christian Jongeneel, Christian Sabo, Christian Wach, Christoph Herr, Christopher Churchill, chunkysteveo, cklee, clayray, Clayton Collie, Clifford Paulick, codeforest, Commeuneimage, Copons, Corey McKrill, cpasqualini, Cristovao Verstraeten, Csaba (LittleBigThings), Curtis Belt, Cyrus Collier, D.PERONNE, d6, Daniel Bachhuber, Daniel Hüsken, Daniel James, Daniel Llewellyn, Daniel Richards, Daniel Roch, Daniele Scasciafratte, Danny, Darko G., Darren Ethier (nerrad), Dave McHale, Dave Whitley, David A. Kennedy, David Aguilera, David Anderson, David Artiss, David Baumwald, David Binovec, David Brumbaugh, David E. Smith, David Herrera, David Ryan, David Shanske, David Smith, davidvee, dchymko, Debabrata Karfa, Deepak Lalwani, dekervit, Delowar Hossain, demetris, Denis Yanchevskiy, derekakelly, Derrick Hammer, Derrick Tennant, Diane Co, Dilip Bheda, Dimitris Mitsis, dingo-d, Dion Hulse, Dixita Dusara, djennez, dmenard, dmethvin, doc987, Dominik Schilling, donmhico, Dono12, Doobeedoo, Dossy Shiobara, dpacks, dratwas, Drew Jaynes, DrLightman, DrProtocols, dsifford, dudo, dushakov, Dustin Bolton, dvershinin, Dylan Kuhn, Earle Davies, ecotechie, Eddie Moya, Eddy, Edi Amin, ehtis, Eileen Violini, Ekaterina, Ella van Durpe, elmastudio, Emanuel Blagonic, Emilie LEBRUN, Emmanuel Hesry, Enej Bajgoric, Enrico Sorcinelli, Enrique Piqueras, Enrique Sánchez, Eric, Eric Andrew Lewis, Eric Binnion, Erik Betshammar, Erin \'Folletto\' Casali, esemlabel, esoj, espiat, Estela Rueda, etoledom, etruel, Ev3rywh3re, Evan Mullins, Fabian Kägy, Fabian Todt, Faisal Ahmed, Felix Arntz, Felix Edelmann, ferdiesletering, finomeno, Florian Brinkmann, Florian TIAR, Florian Truchot, florianatwhodunit, FolioVision, Francesca Marano, Francois Thibaud, Frank Goossens, Frank Klein, Frank.Prendergast, Frankie Jarrett, Franz Armas, fullofcaffeine, Gabriel Koen, Gabriel Maldonado, Gabriel Mays, gadgetroid, Gal Baras, Garavani, garethgillman, Garrett Hyder, Gary Cao, Gary Jones, Gary Pendergast, gchtr, Geert De Deckere, Gemini Labs, Gennady Kovshenin, geriux, Giorgio25b, gisselfeldt, glendaviesnz, goldsounds, Goto Hayato, Govind Kumar, Grégory Viguier, gradina, Greg Ziółkowski, gregmulhauser, grierson, Grzegorz.Janoszka, gsmumbo, Guido Scialfa, guidobras, Gunther Pilz, gwwar, H-var, hakre, Halacious, hankthetank, Hapiuc Robert, Hareesh, haukep, Hauwa, Haz, Hector Farahani, Helen Hou-Sandi, Henry Wright, Herre Groen, hlanggo, hommealone, Hoover, Howdy_McGee, Hronak Nahar, huntlyc, Ian Belanger, Ian Dunn, Ian Stewart, ianjvr, ifrins, infinum, Ipstenu (Mika Epstein), Isabel Brison, ishitaka, J.D. Grimes, jackfungi, jacklinkers, Jadon N, jadpm, jagirbahesh, Jake Spurlock, Jake Whiteley, James Koster, James Nylen, Jan Koch, Jan Reilink, Jan Thiel, Janvo Aldred, Jarret, Jason Adams, Jason Coleman, Jason Cosper, Jason Crouse, Jason LeMahieu (MadtownLems), Jason Rouet, JasWSInc, Javier Casares, Jayson Basanes, jbinda, jbouganim, Jean-Baptiste Audras, Jean-David Daviet, Jeff Chandler, Jeff Farthing, Jeff Ong, Jeff Paul, Jen, Jenil Kanani, Jeremy Felt, Jeremy Herve, Jeremy Yip, Jeroen Rotty, jeryj, Jesin A, Jignesh Nakrani, Jim_Panse, Jip Moors, jivanpal, Joe Dolson, Joe Hoyle, Joe McGill, Joen Asmussen, Johanna de Vos, John Blackbourn, John Dorner, John James Jacoby, John P. Green, John Richards II, John Watkins, johnnyb, Jon Quach, Jon Surrell, Jonathan Bossenger, Jonathan Champ, Jonathan Christopher, Jonathan Desrosiers, Jonathan Stegall, jonkolbert, Jonny Harris, jonnybot, Jono Alderson, Joost de Valk, Jorge Bernal, Jorge Costa, Joseph Dickson, Josepha Haden, Josh Smith, JoshuaWold, Joy, Juanfra Aldasoro, juanlopez4691, Jules Colle, julianm, Juliette Reinders Folmer, Julio Potier, Julka Grodel, Justin Ahinon, Justin de Vesine, Justin Tadlock, justlevine, justnorris, K. Adam White, kaggdesign, Kailey (trepmal), Kaira, Kaitlin Bolling, Kalpesh Akabari, KamataRyo, Kantari Samy, Kaspars, Kavya Gokul, keesiemeijer, Kelly Dwan, kennethroberson5556, Kevin Hagerty, Kharis Sulistiyono, Khokan Sardar, kinjaldalwadi, Kiril Zhelyazkov, Kirsty Burgoine, Kishan Jasani, kitchin, Kite, Kjell Reigstad, Knut Sparhell, Konstantin Obenland, Konstantinos Xenos, ksoares, KT Cheung, Kukhyeon Heo, Kyle B. Johnson, lalitpendhare, landau, Laterna Studio, laurelfulford, Laurens Offereins, Laxman Prajapati, Lester Chan, Levdbas, Lew Ayotte, Lex Robinson, linyows, lipathor, Lisa Schuyler, liuhaibin, ljharb, logig, lucasbustamante, luiswill, Luke Cavanagh, Luke Walczak, lukestramasonder, M Asif Rahman, M.K. Safi, Maarten de Boer, Mahfoudh Arous, mailnew2ster, manojlovic, Manuel Schmalstieg, maraki, Marcin Pietrzak, Marcio Zebedeu, Marco Pereirinha, MarcoZ, Marcus, Marcus Kazmierczak, Marek Dědič, Marek Hrabe, Mario Valney, Marius Jensen, Mark Chouinard, Mark Jaquith, Mark Parnell, Mark Uraine, markdubois, markgoho, Marko Andrijasevic, Marko Heijnen, MarkRH, markshep, markusthiel, Martijn van der Kooij, martychc23, Mary Baum, Matheus Martins, Mathieu Viet, Matias Ventura, matjack1, Matt Cromwell, Matt Gibson, Matt Mullenweg, Matt Radford, Matt van Andel, mattchowning, Matthew Boynes, Matthew Eppelsheimer, Matthew Gerring, Matthias Kittsteiner, Matthias Pfefferle, Matthieu Mota, mattyrob, Maxime Culea, Maxime Pertici, maxme, Mayank Majeji, mcshane, Mel Choyce-Dwan, Menaka S., mensmaximus, metalandcoffee, Michael, Michael Arestad, Michael Arestad, Michael Beckwith, Michael Fields, Michael Nelson, Michele Butcher-Jones, Michelle, Miguel Fonseca, mihdan, Miina Sikk, Mikael Korpela, mikaumoto, Mike Crantea, Mike Glendinning, Mike Haydon, Mike Schinkel [WPLib Box project lead], Mike Schroder, Mikey Arce, Milana Cap, Milind More, mimi, mislavjuric, Mohammad Jangda, Mohammad Rockeybul Alam, Mohsin Rasool, Monika Rao, Morgan Kay, Morten Rand-Hendriksen, Morteza Geransayeh, moto hachi ( mt8.biz ), mrgrt, mrmist, mrTall, msaggiorato, Muhammad Usama Masood, Mukesh Panchal, munyagu, Nabil Moqbel, Nadir Seghir, Nahid Ferdous Mohit, Nalini Thakor, Naoko Takano, narwen, Nate Gay, Nathan Rice, Navid, neonkowy, net, netpassprodsr, Nextendweb, Ngan Tengyuen, Nick Daugherty, Nicky Lim, nicolad, Nicolas Juen, NicolasKulka, Nidhi Jain, Niels de Blaauw, Niels Lange, nigro.simone, Nik Tsekouras, Nikhil Bhansi, Nikolay Bachiyski, Nilo Velez, Niresh, nmenescardi, Noah Allen, NumidWasNotAvailable, oakesjosh, obliviousharmony, ockham, Olga Gleckler, Omar Alshaker, Omar Reiss, onokazu, Optimizing Matters, Ov3rfly, ovann86, overclokk, p_enrique, Paal Joachim Romdahl, Pablo Honey, Paddy, palmiak, Paresh Shinde, Parvand, Pascal Birchler, Pascal Casier, Paul Bearne, Paul Biron, Paul Fernhout, Paul Gibbs, Paul Ryan, Paul Schreiber, Paul Stonier, Paul Von Schrottky, pavelevap, Pedro Mendonça, pentatonicfunk, pepe, Peter \"Pessoft\" Kolínek, Peter Westwood, Peter Wilson, Phil Derksen, Phil Johnston, Philip Jackson, Pierre Gordon, pigdog234, pikamander2, pingram, Pionect, Piyush Patel, pkarjala, pkvillanueva, Prashant Baldha, pratik028, Pravin Parmar, Presskopp, Presslabs, Priyank Patel, Priyo Mukul, ProGrafika, programmin, Puneet Sahalot, pvogel2, r-a-y, Raaj Trambadia, Rachel Peter, raine, rajeshsingh520, Ramanan, Rami Yushuvaev, RavanH, Ravat Parmar, ravenswd, rawrly, rebasaurus, Red Sand Media Group, Remy Perona, Remzi Cavdar, Renatho, renggo888, retlehs, retrofox, riaanlom, Riad Benguella, Rian Rietveld, riasat, Rich Tabor, Ringisha, ritterml, Rnaby, Rob Cutmore, Rob Migchels, rob006, Robert Anderson, Robert Chapin, Robert Peake, Robert Windisch, Rodrigo Arias, Ronald Huereca, Rostislav Wolný, Roy Tanck, rtagliento, ruxandra, Ryan Boren, Ryan Fredlund, Ryan Kienstra, Ryan McCue, Ryan Welcher, Ryota Sakamoto, ryotsun, Sören Wrede, Søren Brønsted, Sachit Tandukar, Sagar Jadhav, Sajjad Hossain Sagor, Sal Ferrarello, Salvatore Formisano, salvoaranzulla, Sam Fullalove, Sam Webster, Samir Shah, Samuel Wood (Otto), samueljseay, Sander van Dragt, Sanjeev Aryal, Sanket Mehta, sarahricker, Sathiyamoorthy V, Sayed Taqui, scarolan, scholdstrom, Scott Kingsley Clark, Scott Reilly, Scott Smith, Scott Taylor, scribu, scruffian, Sean Hayes, seanpaulrasmussen, seayou, senatorman, Sergey Biryukov, Sergey Predvoditelev, Sergio de Falco, sergiomdgomes, Shannon Smith, Shantanu Desai, shaunandrews, Shawn Hooper, shawnz, Shital Marakana, shulard, siliconforks, Simon Wheatley, simonjanin, sinatrateam, sjmur, skarabeq, skorasaurus, skoskie, slushman, snapfractalpop, SpearsMarketing, sphakka, squarecandy, sreedoap, Stanimir Stoyanov, Stefano Minoia, Stefanos Togoulidis, Steph Wells, Stephen Bernhardt, Stephen Cronin, Stephen Edgar, Steve Dufresne, stevegibson12, Steven Stern (sterndata), Steven Word, stevenkussmaul, stevenlinx, Stiofan, Subrata Sarkar, SUM1, Sunny, Sunny Ratilal, Sushyant Zavarzadeh, suzylah, Sybre Waaijer, Synchro, Sérgio Estêvão, Takayuki Miyauchi, Tammie Lister, Tang Rufus, TeBenachi, Tessa Watkins LLC, Tetsuaki Hamano, theMikeD, theolg, Thierry Muller, Thimal Wickremage, Thomas M, Thorsten Frommen, Thrijith Thankachan, Tiago Hillebrandt, Till Krüss, Timothy Jacobs, Tkama, tmdesigned, tmoore41, TobiasBg, tobifjellner (Tor-Bjorn Fjellner), Tofandel, tomdude, Tommy Ferry, Tony G, Toro_Unit (Hiroshi Urabe), torres126, Torsten Landsiedel, Toru Miki, Travis Northcutt, treecutter, truongwp, tsimmons, Tung Du, Udit Desai, Ulrich, Vagios Vlachos, valchovski, Valentin Bora, Vayu Robins, veromary, Viktor Szépe, vinkla, virginienacci, Vladimir, Vladislav Abrashev, vortfu, voyager131, vtieu, webaware, Weston Ruter, William Earnhardt, williampatton, Winstina, wittich, wpdesk, WPDO, WPMarmite, wppinar, Yahil Madakiya, yashrs, yoancutillas, Yoav Farhi, yohannp, yuhin, Yui, Yuri Salame, Yvette Sonneveld, Zack Tollman, zaheerahmad, zakkath, Zebulan Stanphill, zieladam, and Česlav Przywara.\n\n\n\n

                     

                    \n\n\n\n

                    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

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

                    \n\n\n\n

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

                    \n
                    \n\n\n\n
                    \n
                    \n\";s: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:\"8799\";s: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:63:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"WordPress 5.5 Release Candidate 2\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:69:\"https://wordpress.org/news/2020/08/wordpress-5-5-release-candidate-2/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Aug 2020 19:12:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s: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.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8764\";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:420:\"The second release candidate for WordPress 5.5 is here! WordPress 5.5 is slated for release on August 11, 2020, but we need your help to get there—if you haven’t tried 5.5 yet, now is the time! You can test the WordPress 5.5 release candidate in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option) Or download the 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Jake Spurlock\";s: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:2503:\"\n

                    The second release candidate for WordPress 5.5 is here!

                    \n\n\n\n

                    WordPress 5.5 is slated for release on August 11, 2020, but we need your help to get there—if you haven’t tried 5.5 yet, now is the time!

                    \n\n\n\n

                    You can test the WordPress 5.5 release candidate in two ways:

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

                    Thank you to all of the contributors who tested the Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

                    \n\n\n\n

                    Plugin and Theme Developers

                    \n\n\n\n

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

                    \n\n\n\n

                    For a more detailed breakdown of the changes included in WordPress 5.5, check out the WordPress 5.5 beta 1 post. The WordPress 5.5 Field Guide is also out! It’s your source for details on all 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.5 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, fill one on WordPress Trac, where you can also find a list of known bugs.

                    \n\";s: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:\"8764\";s: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:57:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"The Month in WordPress: July 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wordpress.org/news/2020/08/the-month-in-wordpress-july-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Aug 2020 13:54:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"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=8755\";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:340:\"July was an action-packed month for the WordPress project. The month saw a lot of updates on one of the most anticipated releases – WordPress 5.5! WordCamp US 2020 was canceled and the WordPress community team started experimenting with different formats for engaging online events, in July. Read on to catch up with all the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Hari Shanker R\";s: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:11539:\"\n

                    July was an action-packed month for the WordPress project. The month saw a lot of updates on one of the most anticipated releases – WordPress 5.5! WordCamp US 2020 was canceled and the WordPress community team started experimenting with different formats for engaging online events, in July. Read on to catch up with all the updates from the WordPress world.

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

                    WordPress 5.5 Updates

                    \n\n\n\n

                    July was full of WordPress 5.5 updates! The WordPress 5.5 Beta 1 came out on July 7, followed by Beta 2 on July 14, Beta 3 on July 21, and Beta 4 on July 27. Subsequently, the team also published the first release candidate of WordPress 5.5 on July 28. 

                    \n\n\n\n

                    WordPress 5.5, which is slated for release on August 11, 2020, is a major update with features like automatic updates for plugins and themes, a block directory, XML sitemaps, block patterns, and lazy-loading images, among others. To learn more about the release, check out its field guide post.

                    \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

                    Gutenberg 8.5 and 8.6

                    \n\n\n\n

                    The core team launched Gutenberg 8.5 and 8.6. Version 8.5 – the last plugin release will be included entirely (without experimental features) in WordPress 5.5, introduced improvements to block drag-and-drop and accessibility, easier updates for external images, and support for the block directory. Version 8.6 comes with features like Cover block video position controls and block pattern updates. For full details on the latest versions on these Gutenberg releases, visit these posts about 8.5 and 8.6.

                    \n\n\n\n

                    Want to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.

                    \n\n\n\n

                    Reimagining Online WordPress Events

                    \n\n\n\n

                    The Community team made the difficult decision to suspend in-person WordPress events for the rest of 2020 in light of the COVID-19 pandemic. The team has also started working on reimagining online events. Based on feedback from the community members, the team decided to make changes to the current online WordCamp format. Key changes include wrapping up financial support for A/V vendors, ending event swag support for newer online WordCamps, and suspending the Global Community Sponsorship program for 2020. The team encourages upcoming online WordCamps to experiment with their events to facilitate an effective learning experience for attendees while avoiding online event fatigue. The team is currently working on a proposal to organize community-supported recorded workshops and synchronous discussion groups to help community members learn WordPress.

                    Want to get involved with the Community team? Follow the Community blog here, or join them in the #community-events channel in the Making WordPress Slack group. To organize a Meetup or WordCamp, visit the handbook page. 

                    \n\n\n\n

                    WordCamp US 2020 is canceled

                    \n\n\n\n

                    The organizers of WordCamp US 2020 have canceled the event in light of the continued pandemic and online event fatigue. The flagship event, which was originally scheduled for October 27-29 as an in-person event, had already planned to transition to an online event. Several WCUS Organizers will be working with the WordPress Community team to focus on other formats and ideas for online events, including a 24-hour contributor day, and contributing to the workshops initiative currently being discussed. Matt Mullenweg’s State of the Word (which typically accompanies WordCamp US) is likely to take place in a different format later in 2020.

                    \n\n\n\n

                    Plugin and theme updates are now available over zip files

                    \n\n\n\n

                    After eleven years, WordPress now allows users to update plugins and themes by uploading a ZIP file, in WordPress 5.5.  The feature, which was merged on July 7, has been one of the most requested features in WordPress. Now, when a user tries to upload a plugin or theme zip file from the WordPress dashboard by clicking the “Install Now” button, WordPress will direct users to a new screen that compares the currently-installed extension with the uploaded versions. Users can then choose between continuing with the installation or canceling. WordPress 5.5 will also offer automatic plugin and theme updates. 

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

                    Further Reading:

                    \n\n\n\n
                    • The Block directory is coming to WordPress with the 5.5 release. Plugin authors can now submit their Block plugins to the directory.
                    • The Core team has opened up the call for features in the WordPress 5.6 release. You can comment on the post with features that you’d like to be included, current UX pain points, or maintenance tickets that need to be addressed. August 20 is the deadline for feature requests. 
                    • Editor features such as the new Navigation block, the navigation screen, and the widget screen that were originally planned to be merged with WordPress 5.5 have been pushed for the next release. 
                    • The Theme team is inviting proposals on whether to allow themes to place an additional top-level menu link in the admin.
                    • BuddyPress 6.2 beta is out in the wild, and the team will soon release the stable version. The update includes changes that will make BuddyPress fully compatible with WordPress 5.5.
                    • WordCamp EU 2021, which was being planned as an in-person event in Porto, Portugal, is moving online. The team is considering an in-person WordCamp EU in 2022. 
                    • The Polyglots team has prepared and finalized a Translation Editor & Locale Manager Vetting Criteria to provide more clarity on how global mentors assign PTE/GTE/Locale Managers and to help locale teams set their own guidelines. The document, which was finalized after a lot of discussion, is now available in the Polyglots handbook.
                    • Members of the Community team are discussing whether WordCamp volunteers, WordCamp attendees, or Meetup attendees should be awarded a WordPress.org profile badge. The ongoing discussion will be open for comments until August 13.
                    • The WP Notify project, which aims to create a better way to manage and deliver notifications to the relevant audience, is on to its next steps. The team has finalized the initial requirements, and is kicking off the project build.
                    • The WordPress documentation team is considering a ban on links to commercial websites in a revision to its external linking policy. The policy change does not remove external links to commercial sites from WordPress.org and only applies to documentation sites. The idea is to protect documentation from being abused, and to prevent the WordPress project from being biased. Discussion on this post is still ongoing, and a decision has not yet been made. Feel free to comment on the discussion posts, if you would like to share your thoughts on the topic.
                    \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:\"8755\";s: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:63:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"WordPress 5.5 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/2020/07/wordpress-5-5-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:\"Tue, 28 Jul 2020 19:08:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8732\";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:370:\"The first release candidate for WordPress 5.5 is now available! This is an important milestone in the community’s progress toward the final release of WordPress 5.5. “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.5 […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"Jb Audras\";s: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:2970:\"\n

                    The first release candidate for WordPress 5.5 is now available!

                    \n\n\n\n

                    This is an important milestone in the community’s progress toward the final release of WordPress 5.5.

                    \n\n\n\n

                    “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.5 is slated for release on August 11, 2020, but we need your help to get there—if you haven’t tried 5.5 yet, now is the time!

                    \n\n\n\n

                    You can test the WordPress 5.5 release candidate in two ways:

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

                    Thank you to all of the contributors who tested the Beta releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

                    \n\n\n\n

                    What’s in WordPress 5.5?

                    \n\n\n\n

                    WordPress 5.5 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 developer notes tag for updates on those and other changes that could affect your products.

                    \n\n\n\n

                    Plugin and Theme Developers

                    \n\n\n\n

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

                    \n\n\n\n

                    The WordPress 5.5 Field Guide, due very shortly, will give you a more detailed dive into 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.5 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, fill one on WordPress Trac, where you can also find a list of known bugs.

                    \n\";s: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:\"8732\";s: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:63:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.5 Beta 4\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:56:\"https://wordpress.org/news/2020/07/wordpress-5-5-beta-4/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 27 Jul 2020 20:56:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8719\";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:313:\"WordPress 5.5 Beta 4 is now available! This software is still in development, so it’s not recommended to run this version on a production site. Consider setting up a test site to play with the new version. You can test WordPress 5.5 Beta 4 in two ways: Try the WordPress Beta Tester plugin (choose the […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"David Baumwald\";s: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:3812:\"\n

                    WordPress 5.5 Beta 4 is now available!

                    \n\n\n\n

                    This software is still in development, so it’s not recommended to run this version on a production site. Consider setting up a test site to play with the new version.

                    \n\n\n\n

                    You can test WordPress 5.5 Beta 4 in two ways:

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

                    WordPress 5.5 is slated for release on August 11th, 2020, and we need your help to get there!

                    \n\n\n\n

                    Thank you to all of the contributors who tested the beta 3 development release and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

                    \n\n\n\n

                    Some highlights

                    \n\n\n\n

                    Since beta 3, 43 bugs have been fixed. Here are a few changes in beta 4:

                    \n\n\n\n
                    • Add \"loading\" as an allowed kses image attribute (see #50731).
                    • Add filter for the plugin/theme auto-update message in the Info tab of Site health (see #50663).
                    • $_SERVER[\'SERVER_NAME\'] not a reliable when generating email host names (see #25239)
                    • Several backported fixes from Gutenberg are included in WordPress 5.5 Beta 4 (See PR #24218)
                    \n\n\n\n

                    Developer notes

                    \n\n\n\n

                    WordPress 5.5 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 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!

                    \n\n\n\n

                    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\";s: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:\"8719\";s: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:63:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.5 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/2020/07/wordpress-5-5-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:\"Tue, 21 Jul 2020 17:51:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s: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.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8706\";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:\"WordPress 5.5 Beta 3 is now available! This software is still in development,so it’s not recommended to run this version on a production site. Consider setting up a test site to play with the new version. You can test WordPress 5.5 Beta 3 in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Jake Spurlock\";s: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:3876:\"\n

                    WordPress 5.5 Beta 3 is now available!

                    \n\n\n\n

                    This software is still in development,so it’s not recommended to run this version on a production site. Consider setting up a test site to play with the new version.

                    \n\n\n\n

                    You can test WordPress 5.5 Beta 3 in two ways:

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

                    WordPress 5.5 is slated for release on August 11th, 2020, and we need your help to get there!

                    \n\n\n\n

                    Thank you to all of the contributors who tested the beta 2 development release and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

                    \n\n\n\n

                    Some highlights

                    \n\n\n\n

                    Since beta 2, 43 bugs have been fixed. Here are a few changes in beta 3:

                    \n\n\n\n
                    • Plugin and theme versions are now shared in the emails when automatically updated (see #50350).
                    • REST API routes without a permission_callback now trigger a _doing_it_wrong() warning (see #50075).
                    • Over 23 Gutenberg changes and updates (see #24068 and #50712).
                    • A bug with the new import and export database Dashicons has been fixed (see #49913).
                    \n\n\n\n

                    Developer notes

                    \n\n\n\n

                    WordPress 5.5 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 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!

                    \n\n\n\n

                    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\";s: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:\"8706\";s: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:63:\"\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:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:20:\"WordPress 5.5 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/2020/07/wordpress-5-5-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, 14 Jul 2020 17:24:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s: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.5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8681\";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:358:\"WordPress 5.5 Beta 2 is now available! This software is still in development, so it’s not recommended to run this version on a production site. Consider setting up a test site to play with the new version. You can test WordPress 5.5 beta 2 in two ways: Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"Jake Spurlock\";s: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:4552:\"\n


                    WordPress 5.5 Beta 2 is now available!

                    \n\n\n\n

                    This software is still in development, so it’s not recommended to run this version on a production site. Consider setting up a test site to play with the new version.

                    \n\n\n\n

                    You can test WordPress 5.5 beta 2 in two ways:

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

                    WordPress 5.5 is slated for release on August 11th, 2020, and we need your help to get there!

                    \n\n\n\n

                    Thank you to all of the contributors that tested the beta 1 development release and provided feedback. Testing for bugs is an important part of polishing each release and a great way to contribute to WordPress. Here are some of the changes since beta 1 to pay close attention to while testing.

                    \n\n\n\n

                    Some highlights

                    \n\n\n\n

                    Since beta 1, 48 bugs have been fixed. Here is a summary of a few changes included in beta 2:

                    \n\n\n\n
                    • 19 additional bugs have been fixed in the block editor (see #23903 and #23905).
                    • The Dashicons icon font has been updated (see #49913).
                    • Broken widgets stemming from changes in Beta 1 have been fixed (see #50609).
                    • Query handling when counting revisions has been improved (see #34560).
                    • An alternate, expanded view was added for wp_list_table (see #49715).
                    • Some adjustments were made to the handling of default terms for custom taxonomies (see #43517)
                    \n\n\n\n

                    Several updates have been made to the block editor. For details, see #23903 and #23905.

                    \n\n\n\n

                    Developer notes

                    \n\n\n\n

                    WordPress 5.5 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!

                    \n\n\n\n

                    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\";s: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:\"8681\";s: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:\"Sat, 03 Oct 2020 21:42:00 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:\"Fri, 02 Oct 2020 09:34:04 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:\"20200501235608\";}','no'),(215,'_transient_timeout_jetpack_file_data_8.9.1','1604267106','no'),(216,'_transient_jetpack_file_data_8.9.1','a:52:{s:32:\"212a162108f1dc20cc6c768d5b47d4f2\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"d3576702faeb399eb47ad20f586c3804\";a:14:{s:4:\"name\";s:8:\"Carousel\";s:11:\"description\";s:75:\"Display images and galleries in a gorgeous, full-screen browsing experience\";s:4:\"sort\";s:2:\"22\";s:20:\"recommendation_order\";s:2:\"12\";s:10:\"introduced\";s:3:\"1.5\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:17:\"Photos and Videos\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:80:\"gallery, carousel, diaporama, slideshow, images, lightbox, exif, metadata, image\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"55409a5f8388b8d33e2350ef80de3ea3\";a:14:{s:4:\"name\";s:13:\"Comment Likes\";s:11:\"description\";s:64:\"Increase visitor engagement by adding a Like button to comments.\";s:4:\"sort\";s:2:\"39\";s:20:\"recommendation_order\";s:2:\"17\";s:10:\"introduced\";s:3:\"5.1\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:6:\"Social\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:37:\"like widget, like button, like, likes\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"e914e6d31cb61f5a9ef86e1b9573430e\";a:14:{s:4:\"name\";s:8:\"Comments\";s:11:\"description\";s:81:\"Let visitors use a WordPress.com, Twitter, Facebook, or Google account to comment\";s:4:\"sort\";s:2:\"20\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.4\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:6:\"Social\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:53:\"comments, comment, facebook, twitter, google+, social\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"f1b8c61705fb18eb8c8584c9f9cdffd9\";a:14:{s:4:\"name\";s:12:\"Contact Form\";s:11:\"description\";s:81:\"Add a customizable contact form to any post or page using the Jetpack Form Block.\";s:4:\"sort\";s:2:\"15\";s:20:\"recommendation_order\";s:2:\"14\";s:10:\"introduced\";s:3:\"1.3\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:3:\"Yes\";s:11:\"module_tags\";s:5:\"Other\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:214:\"contact, form, grunion, feedback, submission, contact form, email, feedback, contact form plugin, custom form, custom form plugin, form builder, forms, form maker, survey, contact by jetpack, contact us, forms free\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"4fca6eb23a793155d69fdb119a094926\";a:14:{s:4:\"name\";s:9:\"Copy Post\";s:11:\"description\";s:77:\"Enable the option to copy entire posts and pages, including tags and settings\";s:4:\"sort\";s:2:\"15\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"7.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:7:\"Writing\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:15:\"copy, duplicate\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"cfdac01e3c3c529f93a8f49edef1f5db\";a:14:{s:4:\"name\";s:20:\"Custom content types\";s:11:\"description\";s:74:\"Display different types of content on your site with custom content types.\";s:4:\"sort\";s:2:\"34\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"3.1\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:7:\"Writing\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:72:\"cpt, custom post types, portfolio, portfolios, testimonial, testimonials\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"4b9137ecf507290743735fb1f94535df\";a:14:{s:4:\"name\";s:10:\"Custom CSS\";s:11:\"description\";s:88:\"Adds options for CSS preprocessor use, disabling the theme\'s CSS, or custom image width.\";s:4:\"sort\";s:1:\"2\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.7\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:10:\"Appearance\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:108:\"css, customize, custom, style, editor, less, sass, preprocessor, font, mobile, appearance, theme, stylesheet\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"95d75b38d76d2ee1b5b537026eadb8ff\";a:14:{s:4:\"name\";s:21:\"Enhanced Distribution\";s:11:\"description\";s:27:\"Increase reach and traffic.\";s:4:\"sort\";s:1:\"5\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.2\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:6:\"Public\";s:11:\"module_tags\";s:7:\"Writing\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:54:\"google, seo, firehose, search, broadcast, broadcasting\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"f1bb571a95c5de1e6adaf9db8567c039\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"822f9ef1281dace3fb7cc420c77d24e0\";a:14:{s:4:\"name\";s:16:\"Google Analytics\";s:11:\"description\";s:56:\"Set up Google Analytics without touching a line of code.\";s:4:\"sort\";s:2:\"37\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"4.5\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:37:\"webmaster, google, analytics, console\";s:12:\"plan_classes\";s:37:\"business, premium, security, complete\";}s:32:\"c167275f926ef0eefaec9a679bd88d34\";a:14:{s:4:\"name\";s:19:\"Gravatar Hovercards\";s:11:\"description\";s:58:\"Enable pop-up business cards over commenters’ Gravatars.\";s:4:\"sort\";s:2:\"11\";s:20:\"recommendation_order\";s:2:\"13\";s:10:\"introduced\";s:3:\"1.1\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:18:\"Social, Appearance\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:20:\"gravatar, hovercards\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"58cbd4585a74829a1c88aa9c295f3993\";a:14:{s:4:\"name\";s:15:\"Infinite Scroll\";s:11:\"description\";s:53:\"Automatically load new content when a visitor scrolls\";s:4:\"sort\";s:2:\"26\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"2.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:10:\"Appearance\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:33:\"scroll, infinite, infinite scroll\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"d4a35eabc948caefad71a0d3303b95c8\";a:14:{s:4:\"name\";s:8:\"JSON API\";s:11:\"description\";s:51:\"Allow applications to securely access your content.\";s:4:\"sort\";s:2:\"19\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.9\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:6:\"Public\";s:11:\"module_tags\";s:19:\"Writing, Developers\";s:7:\"feature\";s:7:\"General\";s:25:\"additional_search_queries\";s:50:\"api, rest, develop, developers, json, klout, oauth\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"7b0c670bc3f8209dc83abb8610e23a89\";a:14:{s:4:\"name\";s:14:\"Beautiful Math\";s:11:\"description\";s:74:\"Use the LaTeX markup language to write mathematical equations and formulas\";s:4:\"sort\";s:2:\"12\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.1\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:7:\"Writing\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:47:\"latex, math, equation, equations, formula, code\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"b00e4e6c109ce6f77b5c83fbaaaead4c\";a:14:{s:4:\"name\";s:11:\"Lazy Images\";s:11:\"description\";s:137:\"Speed up your site and create a smoother viewing experience by loading images as visitors scroll down the screen, instead of all at once.\";s:4:\"sort\";s:2:\"24\";s:20:\"recommendation_order\";s:2:\"14\";s:10:\"introduced\";s:5:\"5.6.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:23:\"Appearance, Recommended\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:150:\"mobile, theme, fast images, fast image, image, lazy, lazy load, lazyload, images, lazy images, thumbnail, image lazy load, lazy loading, load, loading\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"8e46c72906c928eca634ac2c8b1bc84f\";a:14:{s:4:\"name\";s:5:\"Likes\";s:11:\"description\";s:63:\"Give visitors an easy way to show they appreciate your content.\";s:4:\"sort\";s:2:\"23\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"2.2\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:6:\"Social\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:26:\"like, likes, wordpress.com\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"2df2264a07aff77e0556121e33349dce\";a:14:{s:4:\"name\";s:8:\"Markdown\";s:11:\"description\";s:50:\"Write posts or pages in plain-text Markdown syntax\";s:4:\"sort\";s:2:\"31\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"2.8\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:7:\"Writing\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:12:\"md, markdown\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"0337eacae47d30c946cb9fc4e5ece649\";a:14:{s:4:\"name\";s:21:\"WordPress.com Toolbar\";s:11:\"description\";s:91:\"Replaces the admin bar with a useful toolbar to quickly manage your site via WordPress.com.\";s:4:\"sort\";s:2:\"38\";s:20:\"recommendation_order\";s:2:\"16\";s:10:\"introduced\";s:3:\"4.8\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:7:\"General\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:19:\"adminbar, masterbar\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"cb5d81445061b89d19cb9c7754697a39\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"ea0fbbd64080c81a90a784924603588c\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"5c53fdb3633ba3232f60180116900273\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"40b97d9ce396339d3e8e46b833a045b5\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"0739df64747f2d02c140f23ce6c19cd8\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"c54bb0a65b39f1316da8632197a88a4e\";a:14:{s:4:\"name\";s:7:\"Monitor\";s:11:\"description\";s:118:\"Jetpack’s downtime monitoring will continuously watch your site, and alert you the moment that downtime is detected.\";s:4:\"sort\";s:2:\"28\";s:20:\"recommendation_order\";s:2:\"10\";s:10:\"introduced\";s:3:\"2.6\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:11:\"Recommended\";s:7:\"feature\";s:8:\"Security\";s:25:\"additional_search_queries\";s:123:\"monitor, uptime, downtime, monitoring, maintenance, maintenance mode, offline, site is down, site down, down, repair, error\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"cc013f4c5480c7bdc1e7edb2f410bf3c\";a:14:{s:4:\"name\";s:13:\"Notifications\";s:11:\"description\";s:57:\"Receive instant notifications of site comments and likes.\";s:4:\"sort\";s:2:\"13\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.9\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:3:\"Yes\";s:11:\"module_tags\";s:5:\"Other\";s:7:\"feature\";s:7:\"General\";s:25:\"additional_search_queries\";s:62:\"notification, notifications, toolbar, adminbar, push, comments\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"b3b34928b1e549bb52f866accc0450c5\";a:14:{s:4:\"name\";s:9:\"Asset CDN\";s:11:\"description\";s:154:\"Jetpack’s Site Accelerator loads your site faster by optimizing your images and serving your images and static files from our global network of servers.\";s:4:\"sort\";s:2:\"26\";s:20:\"recommendation_order\";s:1:\"1\";s:10:\"introduced\";s:3:\"6.6\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:42:\"Photos and Videos, Appearance, Recommended\";s:7:\"feature\";s:23:\"Recommended, Appearance\";s:25:\"additional_search_queries\";s:160:\"site accelerator, accelerate, static, assets, javascript, css, files, performance, cdn, bandwidth, content delivery network, pagespeed, combine js, optimize css\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"714284944f56d6936a40f3309900bc8e\";a:14:{s:4:\"name\";s:9:\"Image CDN\";s:11:\"description\";s:141:\"Mirrors and serves your images from our free and fast image CDN, improving your site’s performance with no additional load on your servers.\";s:4:\"sort\";s:2:\"25\";s:20:\"recommendation_order\";s:1:\"1\";s:10:\"introduced\";s:3:\"2.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:42:\"Photos and Videos, Appearance, Recommended\";s:7:\"feature\";s:23:\"Recommended, Appearance\";s:25:\"additional_search_queries\";s:171:\"photon, photo cdn, image cdn, speed, compression, resize, responsive images, responsive, content distribution network, optimize, page speed, image optimize, photon jetpack\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"348754bc914ee02c72d9af445627784c\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"041704e207c4c59eea93e0499c908bff\";a:14:{s:4:\"name\";s:13:\"Post by email\";s:11:\"description\";s:33:\"Publish posts by sending an email\";s:4:\"sort\";s:2:\"14\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"2.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:7:\"Writing\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:20:\"post by email, email\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"26e6cb3e08a6cfd0811c17e7c633c72c\";a:14:{s:4:\"name\";s:7:\"Protect\";s:11:\"description\";s:151:\"Enabling brute force protection will prevent bots and hackers from attempting to log in to your website with common username and password combinations.\";s:4:\"sort\";s:1:\"1\";s:20:\"recommendation_order\";s:1:\"4\";s:10:\"introduced\";s:3:\"3.4\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:3:\"Yes\";s:11:\"module_tags\";s:11:\"Recommended\";s:7:\"feature\";s:8:\"Security\";s:25:\"additional_search_queries\";s:173:\"security, jetpack protect, secure, protection, botnet, brute force, protect, login, bot, password, passwords, strong passwords, strong password, wp-login.php, protect admin\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"915a504082f797395713fd01e0e2e713\";a:14:{s:4:\"name\";s:9:\"Publicize\";s:11:\"description\";s:128:\"Publicize makes it easy to share your site’s posts on several social media networks automatically when you publish a new post.\";s:4:\"sort\";s:2:\"10\";s:20:\"recommendation_order\";s:1:\"7\";s:10:\"introduced\";s:3:\"2.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:19:\"Social, Recommended\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:220:\"facebook, jetpack publicize, twitter, tumblr, linkedin, social, tweet, connections, sharing, social media, automated, automated sharing, auto publish, auto tweet and like, auto tweet, facebook auto post, facebook posting\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"a7b21cc562ee9ffa357bba19701fe45b\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"9243c1a718566213f4eaf3b44cf14b07\";a:14:{s:4:\"name\";s:13:\"Related posts\";s:11:\"description\";s:113:\"Keep visitors engaged on your blog by highlighting relevant and new content at the bottom of each published post.\";s:4:\"sort\";s:2:\"29\";s:20:\"recommendation_order\";s:1:\"9\";s:10:\"introduced\";s:3:\"2.9\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:11:\"Recommended\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:360:\"related, jetpack related posts, related posts for wordpress, related posts, popular posts, popular, related content, related post, contextual, context, contextual related posts, related articles, similar posts, easy related posts, related page, simple related posts, free related posts, related thumbnails, similar, engagement, yet another related posts plugin\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"583e4cda5596ee1b28a19cde33f438be\";a:14:{s:4:\"name\";s:6:\"Search\";s:11:\"description\";s:102:\"Help visitors quickly find answers with highly relevant instant search results and powerful filtering.\";s:4:\"sort\";s:2:\"34\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"5.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:5:\"false\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:6:\"Search\";s:25:\"additional_search_queries\";s:110:\"search, elastic, elastic search, elasticsearch, fast search, search results, search performance, google search\";s:12:\"plan_classes\";s:18:\"business, complete\";}s:32:\"15346c1f7f2a5f29d34378774ecfa830\";a:14:{s:4:\"name\";s:9:\"SEO Tools\";s:11:\"description\";s:50:\"Better results on search engines and social media.\";s:4:\"sort\";s:2:\"35\";s:20:\"recommendation_order\";s:2:\"15\";s:10:\"introduced\";s:3:\"4.4\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:18:\"Social, Appearance\";s:7:\"feature\";s:7:\"Traffic\";s:25:\"additional_search_queries\";s:81:\"search engine optimization, social preview, meta description, custom title format\";s:12:\"plan_classes\";s:37:\"business, premium, security, complete\";}s:32:\"72a0ff4cfae86074a7cdd2dcd432ef11\";a:14:{s:4:\"name\";s:7:\"Sharing\";s:11:\"description\";s:120:\"Add Twitter, Facebook and Google+ buttons at the bottom of each post, making it easy for visitors to share your content.\";s:4:\"sort\";s:1:\"7\";s:20:\"recommendation_order\";s:1:\"6\";s:10:\"introduced\";s:3:\"1.1\";s:7:\"changed\";s:3:\"1.2\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:19:\"Social, Recommended\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:229:\"share, sharing, sharedaddy, social buttons, buttons, share facebook, share twitter, social media sharing, social media share, social share, icons, email, facebook, twitter, linkedin, pinterest, pocket, social widget, social media\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"bb8c6c190aaec212a7ab6e940165af4d\";a:14:{s:4:\"name\";s:16:\"Shortcode Embeds\";s:11:\"description\";s:177:\"Shortcodes are WordPress-specific markup that let you add media from popular sites. This feature is no longer necessary as the editor now handles media embeds rather gracefully.\";s:4:\"sort\";s:1:\"3\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.1\";s:7:\"changed\";s:3:\"1.2\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:46:\"Photos and Videos, Social, Writing, Appearance\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:236:\"shortcodes, shortcode, embeds, media, bandcamp, dailymotion, facebook, flickr, google calendars, google maps, google+, polldaddy, recipe, recipes, scribd, slideshare, slideshow, slideshows, soundcloud, ted, twitter, vimeo, vine, youtube\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"1abd31fe07ae4fb0f8bb57dc24592219\";a:14:{s:4:\"name\";s:16:\"WP.me Shortlinks\";s:11:\"description\";s:47:\"Generates shorter links using the wp.me domain.\";s:4:\"sort\";s:1:\"8\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.1\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:6:\"Social\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:17:\"shortlinks, wp.me\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"cae5f097f8d658e0b0ae50733d7c6476\";a:14:{s:4:\"name\";s:8:\"Sitemaps\";s:11:\"description\";s:50:\"Make it easy for search engines to find your site.\";s:4:\"sort\";s:2:\"13\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"3.9\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:20:\"Recommended, Traffic\";s:7:\"feature\";s:11:\"Recommended\";s:25:\"additional_search_queries\";s:39:\"sitemap, traffic, search, site map, seo\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"e9b8318133b2f95e7906cedb3557a87d\";a:14:{s:4:\"name\";s:14:\"Secure Sign On\";s:11:\"description\";s:63:\"Allow users to log in to this site using WordPress.com accounts\";s:4:\"sort\";s:2:\"30\";s:20:\"recommendation_order\";s:1:\"5\";s:10:\"introduced\";s:3:\"2.6\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:10:\"Developers\";s:7:\"feature\";s:8:\"Security\";s:25:\"additional_search_queries\";s:51:\"sso, single sign on, login, log in, 2fa, two-factor\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"17e66a12031ccf11d8d45ceee0955f05\";a:14:{s:4:\"name\";s:10:\"Site Stats\";s:11:\"description\";s:44:\"Collect valuable traffic stats and insights.\";s:4:\"sort\";s:1:\"1\";s:20:\"recommendation_order\";s:1:\"2\";s:10:\"introduced\";s:3:\"1.1\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:3:\"Yes\";s:11:\"module_tags\";s:23:\"Site Stats, Recommended\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:54:\"statistics, tracking, analytics, views, traffic, stats\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"346cf9756e7c1252acecb9a8ca81a21c\";a:14:{s:4:\"name\";s:13:\"Subscriptions\";s:11:\"description\";s:58:\"Let visitors subscribe to new posts and comments via email\";s:4:\"sort\";s:1:\"9\";s:20:\"recommendation_order\";s:1:\"8\";s:10:\"introduced\";s:3:\"1.2\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:6:\"Social\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:74:\"subscriptions, subscription, email, follow, followers, subscribers, signup\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"4f84d218792a6efa06ed6feae09c4dd5\";a:14:{s:4:\"name\";s:0:\"\";s:11:\"description\";s:0:\"\";s:4:\"sort\";s:0:\"\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:0:\"\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:0:\"\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:0:\"\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"ca086af79d0d9dccacc934ccff5b4fd7\";a:14:{s:4:\"name\";s:15:\"Tiled Galleries\";s:11:\"description\";s:61:\"Display image galleries in a variety of elegant arrangements.\";s:4:\"sort\";s:2:\"24\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"2.1\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:17:\"Photos and Videos\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:43:\"gallery, tiles, tiled, grid, mosaic, images\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"43c24feb7c541c376af93e0251c1a261\";a:14:{s:4:\"name\";s:20:\"Backups and Scanning\";s:11:\"description\";s:100:\"Protect your site with daily or real-time backups and automated virus scanning and threat detection.\";s:4:\"sort\";s:2:\"32\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:5:\"0:1.2\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:5:\"false\";s:4:\"free\";s:5:\"false\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:16:\"Security, Health\";s:25:\"additional_search_queries\";s:386:\"backup, cloud backup, database backup, restore, wordpress backup, backup plugin, wordpress backup plugin, back up, backup wordpress, backwpup, vaultpress, backups, off-site backups, offsite backup, offsite, off-site, antivirus, malware scanner, security, virus, viruses, prevent viruses, scan, anti-virus, antimalware, protection, safe browsing, malware, wp security, wordpress security\";s:12:\"plan_classes\";s:47:\"personal, business, premium, security, complete\";}s:32:\"b9396d8038fc29140b499098d2294d79\";a:14:{s:4:\"name\";s:17:\"Site verification\";s:11:\"description\";s:58:\"Establish your site\'s authenticity with external services.\";s:4:\"sort\";s:2:\"33\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"3.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:3:\"Yes\";s:11:\"module_tags\";s:0:\"\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:56:\"webmaster, seo, google, bing, pinterest, search, console\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"afe184082e106c1bdfe1ee844f98aef3\";a:14:{s:4:\"name\";s:10:\"VideoPress\";s:11:\"description\";s:101:\"Save on hosting storage and bandwidth costs by streaming fast, ad-free video from our global network.\";s:4:\"sort\";s:2:\"27\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"2.5\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:5:\"false\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:0:\"\";s:11:\"module_tags\";s:17:\"Photos and Videos\";s:7:\"feature\";s:7:\"Writing\";s:25:\"additional_search_queries\";s:118:\"video, videos, videopress, video gallery, video player, videoplayer, mobile video, vimeo, youtube, html5 video, stream\";s:12:\"plan_classes\";s:37:\"business, premium, security, complete\";}s:32:\"44637d43460370af9a1b31ce3ccec0cd\";a:14:{s:4:\"name\";s:17:\"Widget Visibility\";s:11:\"description\";s:42:\"Control where widgets appear on your site.\";s:4:\"sort\";s:2:\"17\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"2.4\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:10:\"Appearance\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:54:\"widget visibility, logic, conditional, widgets, widget\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"694c105a5c3b659acfcddad220048d08\";a:14:{s:4:\"name\";s:21:\"Extra Sidebar Widgets\";s:11:\"description\";s:49:\"Provides additional widgets for use on your site.\";s:4:\"sort\";s:1:\"4\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"1.2\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:2:\"No\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:18:\"Social, Appearance\";s:7:\"feature\";s:10:\"Appearance\";s:25:\"additional_search_queries\";s:65:\"widget, widgets, facebook, gallery, twitter, gravatar, image, rss\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"21b59e7bb3fe0784e7525ad11ad8a8f6\";a:14:{s:4:\"name\";s:21:\"WooCommerce Analytics\";s:11:\"description\";s:53:\"Enhanced analytics for WooCommerce and Jetpack users.\";s:4:\"sort\";s:2:\"13\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:3:\"8.4\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:3:\"Yes\";s:11:\"module_tags\";s:18:\"Other, Recommended\";s:7:\"feature\";s:10:\"Engagement\";s:25:\"additional_search_queries\";s:69:\"woocommerce, analytics, stats, statistics, tracking, analytics, views\";s:12:\"plan_classes\";s:0:\"\";}s:32:\"ae15da72c5802d72f320640bad669561\";a:14:{s:4:\"name\";s:3:\"Ads\";s:11:\"description\";s:60:\"Earn income by allowing Jetpack to display high quality ads.\";s:4:\"sort\";s:1:\"1\";s:20:\"recommendation_order\";s:0:\"\";s:10:\"introduced\";s:5:\"4.5.0\";s:7:\"changed\";s:0:\"\";s:10:\"deactivate\";s:0:\"\";s:4:\"free\";s:0:\"\";s:19:\"requires_connection\";s:3:\"Yes\";s:13:\"auto_activate\";s:2:\"No\";s:11:\"module_tags\";s:19:\"Traffic, Appearance\";s:7:\"feature\";s:0:\"\";s:25:\"additional_search_queries\";s:26:\"advertising, ad codes, ads\";s:12:\"plan_classes\";s:37:\"premium, business, security, complete\";}}','no'),(162,'do_activate','0','yes'),(163,'jetpack_activated','2','yes'),(164,'jetpack_options','a:3:{s:7:\"version\";s:14:\"8.5:1601761313\";s:11:\"old_version\";s:14:\"8.5:1601761313\";s:14:\"last_heartbeat\";i:1601761505;}','yes'),(165,'_transient_timeout_jetpack_https_test','1601847713','no'),(166,'_transient_jetpack_https_test','1','no'),(167,'_transient_timeout_jetpack_https_test_message','1601847713','no'),(168,'_transient_jetpack_https_test_message','','no'),(169,'boldgrid_pointers','a:4:{i:0;a:6:{s:2:\"id\";s:37:\"boldgrid_image_search_internal_only_8\";s:6:\"screen\";s:4:\"page\";s:6:\"target\";s:19:\"#media-search-input\";s:5:\"title\";s:12:\"Image search\";s:7:\"content\";s:222:\"This search function helps you find images you\'ve already uploaded to your Media Library. If you would like to search the web for new images, click the BoldGrid Connect Search tab in the top menu.\";s:8:\"position\";a:2:{s:4:\"edge\";s:5:\"right\";s:5:\"align\";s:6:\"middle\";}}i:1;a:6:{s:2:\"id\";s:49:\"boldgrid_media_library_image_search_internal_only\";s:6:\"screen\";s:6:\"upload\";s:6:\"target\";s:19:\"#media-search-input\";s:5:\"title\";s:12:\"Image search\";s:7:\"content\";s:222:\"This search function helps you find images you\'ve already uploaded to your Media Library. If you would like to search the web for new images, click the BoldGrid Connect Search tab in the top menu.\";s:8:\"position\";a:3:{s:4:\"edge\";s:3:\"top\";s:5:\"align\";s:6:\"middle\";s:17:\"open_on_page_load\";b:0;}}i:2;a:6:{s:2:\"id\";s:38:\"boldgrid_image_size_do_you_need_help_8\";s:6:\"screen\";s:12:\"media-upload\";s:6:\"target\";s:11:\"#image_size\";s:5:\"title\";s:10:\"Image size\";s:7:\"content\";s:33:\"Need help choosing an image size?\";s:8:\"position\";a:2:{s:4:\"edge\";s:5:\"right\";s:5:\"align\";s:6:\"middle\";}}i:3;a:6:{s:2:\"id\";s:29:\"boldgrid_customization_widget\";s:6:\"screen\";s:9:\"dashboard\";s:6:\"target\";s:21:\"#customization_widget\";s:5:\"title\";s:35:\"Begin customizing your new website!\";s:7:\"content\";s:130:\"Congratulations, you've just installed your new website! Below you'll find tips to help you begin customizing your site.\";s:8:\"position\";a:2:{s:4:\"edge\";s:6:\"bottom\";s:5:\"align\";s:6:\"middle\";}}}','yes'),(170,'_site_transient_timeout_browser_ce4e9e986b0fbc713624d54b83c36283','1602366113','no'),(171,'_site_transient_browser_ce4e9e986b0fbc713624d54b83c36283','a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:13:\"85.0.4183.121\";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'),(172,'_site_transient_timeout_php_check_e26e33de4a278e301580d402dcb3d659','1602366113','no'),(173,'_site_transient_php_check_e26e33de4a278e301580d402dcb3d659','a:5:{s:19:\"recommended_version\";s:3:\"7.4\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:1;s:9:\"is_secure\";b:1;s:13:\"is_acceptable\";b:1;}','no'),(194,'finished_updating_comment_type','1','yes'),(179,'_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3','1601804520','no'),(176,'_site_transient_timeout_community-events-9bc580255edd00cc269fea52088e8c5f','1601804520','no'),(177,'_site_transient_community-events-9bc580255edd00cc269fea52088e8c5f','a:4:{s:9:\"sandboxed\";b:0;s:5:\"error\";N;s:8:\"location\";a:1:{s:2:\"ip\";s:11:\"5.146.192.0\";}s:6:\"events\";a:7:{i:0;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:58:\"Discussion Group: WordPress Troubleshooting Basics: Part 1\";s:3:\"url\";s:68:\"https://www.meetup.com/learn-wordpress-discussions/events/273614907/\";s:6:\"meetup\";s:27:\"Learn WordPress Discussions\";s:10:\"meetup_url\";s:51:\"https://www.meetup.com/learn-wordpress-discussions/\";s:4:\"date\";s:19:\"2020-10-06 06:00:00\";s:8:\"end_date\";s:19:\"2020-10-06 07:00:00\";s:20:\"start_unix_timestamp\";i:1601989200;s:18:\"end_unix_timestamp\";i:1601992800;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"US\";s:8:\"latitude\";d:37.7799987792970028976924368180334568023681640625;s:9:\"longitude\";d:-122.419998168950002082056016661226749420166015625;}}i:1;a:10:{s:4:\"type\";s:8:\"wordcamp\";s:5:\"title\";s:27:\"WordCamp Rochester, NY, USA\";s:3:\"url\";s:36:\"https://2020.rochester.wordcamp.org/\";s:6:\"meetup\";N;s:10:\"meetup_url\";N;s:4:\"date\";s:19:\"2020-10-03 08:35:00\";s:8:\"end_date\";s:19:\"2020-10-03 08:35:00\";s:20:\"start_unix_timestamp\";i:1601728500;s:18:\"end_unix_timestamp\";i:1601728500;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"US\";s:8:\"latitude\";d:43.156577900000002045999281108379364013671875;s:9:\"longitude\";d:-77.608846499999998513885657303035259246826171875;}}i:2;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:49:\"WP Meetup Stuttgart – Ein einfaches Admin-Menü\";s:3:\"url\";s:63:\"https://www.meetup.com/wpmeetup-stuttgart/events/bpqbsrybcnbkb/\";s:6:\"meetup\";s:26:\"WordPress Meetup Stuttgart\";s:10:\"meetup_url\";s:42:\"https://www.meetup.com/wpmeetup-stuttgart/\";s:4:\"date\";s:19:\"2020-10-14 19:00:00\";s:8:\"end_date\";s:19:\"2020-10-14 21:00:00\";s:20:\"start_unix_timestamp\";i:1602694800;s:18:\"end_unix_timestamp\";i:1602702000;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"DE\";s:8:\"latitude\";d:48.7900009155270026894868351519107818603515625;s:9:\"longitude\";d:9.18999958038330078125;}}i:3;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:57:\"WordPress -Meetup Neustadt Weinstraße - Barrierefreiheit\";s:3:\"url\";s:70:\"https://www.meetup.com/WordPress-Meetup-Neustadt/events/xdghgrybcnbcb/\";s:6:\"meetup\";s:25:\"WordPress Meetup Neustadt\";s:10:\"meetup_url\";s:49:\"https://www.meetup.com/WordPress-Meetup-Neustadt/\";s:4:\"date\";s:19:\"2020-10-15 18:00:00\";s:8:\"end_date\";s:19:\"2020-10-15 20:00:00\";s:20:\"start_unix_timestamp\";i:1602777600;s:18:\"end_unix_timestamp\";i:1602784800;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"DE\";s:8:\"latitude\";d:49.3600006103520030364961712621152400970458984375;s:9:\"longitude\";d:8.130000114440900205181605997495353221893310546875;}}i:4;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:18:\"WP Meetup Mannheim\";s:3:\"url\";s:63:\"https://www.meetup.com/WordPress-Mannheim/events/nvxhtrybcnbbc/\";s:6:\"meetup\";s:25:\"WordPress Meetup Mannheim\";s:10:\"meetup_url\";s:42:\"https://www.meetup.com/WordPress-Mannheim/\";s:4:\"date\";s:19:\"2020-10-20 19:00:00\";s:8:\"end_date\";s:19:\"2020-10-20 22:00:00\";s:20:\"start_unix_timestamp\";i:1603213200;s:18:\"end_unix_timestamp\";i:1603224000;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"DE\";s:8:\"latitude\";d:49.5;s:9:\"longitude\";d:8.4700002670287997119658029987476766109466552734375;}}i:5;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:19:\"WP Meetup Stuttgart\";s:3:\"url\";s:63:\"https://www.meetup.com/wpmeetup-stuttgart/events/bpqbsrybcpbgb/\";s:6:\"meetup\";s:26:\"WordPress Meetup Stuttgart\";s:10:\"meetup_url\";s:42:\"https://www.meetup.com/wpmeetup-stuttgart/\";s:4:\"date\";s:19:\"2020-11-04 19:00:00\";s:8:\"end_date\";s:19:\"2020-11-04 21:00:00\";s:20:\"start_unix_timestamp\";i:1604512800;s:18:\"end_unix_timestamp\";i:1604520000;s:8:\"location\";a:4:{s:8:\"location\";s:6:\"Online\";s:7:\"country\";s:2:\"DE\";s:8:\"latitude\";d:48.7900009155270026894868351519107818603515625;s:9:\"longitude\";d:9.18999958038330078125;}}i:6;a:10:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:38:\"WordPress -Meetup Neustadt Weinstraße\";s:3:\"url\";s:70:\"https://www.meetup.com/WordPress-Meetup-Neustadt/events/xdghgrybcpbhb/\";s:6:\"meetup\";s:25:\"WordPress Meetup Neustadt\";s:10:\"meetup_url\";s:49:\"https://www.meetup.com/WordPress-Meetup-Neustadt/\";s:4:\"date\";s:19:\"2020-11-05 18:00:00\";s:8:\"end_date\";s:19:\"2020-11-05 20:00:00\";s:20:\"start_unix_timestamp\";i:1604595600;s:18:\"end_unix_timestamp\";i:1604602800;s:8:\"location\";a:4:{s:8:\"location\";s:17:\"Neustadt, Germany\";s:7:\"country\";s:2:\"de\";s:8:\"latitude\";d:49.35363388061499989589719916693866252899169921875;s:9:\"longitude\";d:8.136813163757299349754248396493494510650634765625;}}}}','no'),(182,'_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1601804520','no'),(183,'_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1601761320','no'),(184,'_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9','1601804520','no'),(185,'_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:105:\"WPTavern: Gutenberg 9.1 Adds Patterns Category Dropdown and Reverts Block-Based Widgets in the Customizer\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105629\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:255:\"https://wptavern.com/gutenberg-9-1-adds-patterns-category-dropdown-and-reverts-block-based-widgets-in-the-customizer?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-1-adds-patterns-category-dropdown-and-reverts-block-based-widgets-in-the-customizer\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5615:\"

                    Gutenberg 9.1 was released to the public on Wednesday. The team announced over 200 commits from 77 contributors in its release post yesterday. One of the biggest changes to the interface was the addition of a new dropdown selector for block pattern categories. The team also reverted the block-based widgets section in the customizer and added an image size control to the Media & Text block.

                    \n\n\n\n

                    One of the main focuses of this release was improving the block-based widgets editor. The feature was taken out of the experimental stage in Gutenberg 8.9 and continues to improve. The widgets screen now uses the same inserter UI as the post-editing screen. However, users can currently only insert regular blocks. Patterns and reusable blocks are still not included.

                    \n\n\n\n

                    Theme authors can now control aspects of the block editor via a custom theme.json file. This is part of the ongoing Global Styles project, which will allow theme authors to configure features for their users.

                    \n\n\n\n

                    The development team has also added an explicit box-sizing style rule to the Cover and Group blocks. This is to avoid any potential issues with the new padding/spacing options. Theme authors who rely on the block editor styles should test their themes to make sure this change does not break anything.

                    \n\n\n\n

                    Better Pattern Organization

                    \n\n\n\nNew block patterns UI in the inserter.\n\n\n\n

                    I have been calling for the return of the tabbed pattern categories since Gutenberg 8.0, which was a regression from previous versions. For 11 versions, users have had to scroll and scroll and scroll through every block pattern just to find the one they wanted. The development team has sought to address this issue by using a category dropdown selector. When selecting a specific category, its patterns will appear.

                    \n\n\n\n

                    At first, I was unsure about this method over the old tabbed method. However, after some use, it feels like the right direction.

                    \n\n\n\n

                    As more and more theme and plugin authors add block pattern categories to users’ sites, the dropdown is a more sensible route. Even tabs could become unwieldy over time. The dropdown better organizes the list of categories and makes the UI cleaner. More than anything, I am enjoying the experience and look forward to this eventually landing in WordPress 5.6 later this year.

                    \n\n\n\n

                    Customizer Widgets Reverted

                    \n\n\n\nReverted widgets panel in the customizer.\n\n\n\n

                    On the subject of WordPress 5.6, one of its flagship features has been hitting some roadblocks. Block-based widgets are expected to land in core with the December release, but the team just reverted part of the feature. They had to remove the widgets block editor from the customizer they added just two major releases ago.

                    \n\n\n\n

                    It was for the best. The customizer’s block-based widgets editor was fundamentally broken. It was not ready for primetime and should have remained in the experimental stage until it was somewhat usable.

                    \n\n\n\n

                    “I will approve this since the current state of the customizer in the Gutenberg plugin is broken, and there is no clear path forward about how to fix that,” wrote Andrei Draganescu in the reversion ticket. “With this patch, the normal widgets can still be edited in the customizer and the block ones don’t break it anymore. This is NOT to mean that we won’t proceed with fixing the block editor in the customizer, that is still an ongoing discussion.”

                    \n\n\n\n

                    The current state of editing widgets via the customizer is at least workable with this change. If end-users add a block via the admin-side widgets editor, it will merely appear as an uneditable, faux widget named “Block” in the customizer. They will need to edit blocks via the normal widgets screen.

                    \n\n\n\n

                    There is no way that WordPress can ship the current solution when 5.6 rolls out. However, we are still two months out. This leaves plenty of time for a fix, but Draganescu’s note that “there is no clear path forward” may make some people a bit uneasy at this stage of development.

                    \n\n\n\n

                    Control Image Size for Media & Text

                    \n\n\n\nImage size dropdown selector for the Media & Text block.\n\n\n\n

                    One of the bright spots in this update is the addition of an image size control to the Media & Text block. Like the normal Image block, end-users can choose from any registered image size created for their uploaded image.

                    \n\n\n\n

                    This is a feature I have been looking forward to in particular. Previously, using the full-sized image often made the page weight a bit heftier than necessary. It is also nice to go along with themes that register sizes for both landscape and portrait orientations, giving users more 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:\"Fri, 02 Oct 2020 20:56: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:14:\"Justin Tadlock\";s: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:58:\"WordPress.org blog: The Month in WordPress: September 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=9026\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:73:\"https://wordpress.org/news/2020/10/the-month-in-wordpress-september-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8711:\"

                    This month was characterized by some exciting announcements from the WordPress core team! Read on to catch up with all the WordPress news and updates from September. 

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

                    WordPress 5.5.1 Launch

                    \n\n\n\n

                    On September 1, the  Core team released WordPress 5.5.1. This maintenance release included several bug fixes for both core and the editor, and many other enhancements. You can update to the latest version directly from your WordPress dashboard or download it directly from WordPress.org. The next major release will be version 5.6.

                    \n\n\n\n

                    Want to be involved in the next release?  You can help to build WordPress Core by following the Core team blog, and joining the #core channel in the Making WordPress Slack group.

                    \n\n\n\n

                    Gutenberg 9.1, 9.0, and 8.9 are out

                    \n\n\n\n

                    The core team launched version 9.0 of the Gutenberg plugin on September 16, and version 9.1 on September 30. Version 9.0 features some useful enhancements — like a new look for the navigation screen (with drag and drop support in the list view) and modifications to the query block (including search, filtering by author, and support for tags). Version 9.1 adds improvements to global styles, along with improvements for the UI and several blocks. Version 8.9 of Gutenberg, which came out earlier in September, enables the block-based widgets feature (also known as block areas, and was previously available in the experiments section) by default — replacing the default WordPress widgets to the plugin. You can find out more about the Gutenberg roadmap in the What’s next in Gutenberg blog post.

                    \n\n\n\n

                    Want to get involved in building Gutenberg? Follow the Core team blog, contribute to Gutenberg on GitHub, and join the #core-editor channel in the Making WordPress Slack group.

                    \n\n\n\n

                    Twenty Twenty One is the WordPress 5.6 default theme

                    \n\n\n\n

                    Twenty Twenty One, the brand new default theme for WordPress 5.6, has been announced! Twenty Twenty One is designed to be a blank canvas for the block editor, and will adopt a straightforward, yet refined, design. The theme has a limited color palette: a pastel green background color, two shades of dark grey for text, and a native set of system fonts. Twenty Twenty One will use a modified version of the Seedlet theme as its base. It will have a comprehensive system of nested CSS variables to make child theming easier, a native support for global styles, and full site editing. 

                    \n\n\n\n

                    Follow the Make/Core blog if you wish to contribute to Twenty Twenty One. There will be weekly meetings every Monday at 15:00 UTC and triage sessions every Friday at 15:00 UTC in the #core-themes Slack channel. Theme development will happen on GitHub. 

                    \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:\"Fri, 02 Oct 2020 09:34: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:14:\"Hari Shanker R\";s: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:75:\"WPTavern: Cloudflare Launches New Web Analytics Product Focusing on Privacy\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105446\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:195:\"https://wptavern.com/cloudflare-launches-new-web-analytics-product-focusing-on-privacy?utm_source=rss&utm_medium=rss&utm_campaign=cloudflare-launches-new-web-analytics-product-focusing-on-privacy\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2448:\"

                    In pursuit of “democratizing web analytics,” Cloudflare announced it is launching privacy-first analytics as a new standalone product. The company is entering a market that has been dominated by Google Analytics for years but with a major differentiating feature – it will not track individual users by a cookie or IP address to show unique visits.

                    \n\n\n\n

                    Cloudflare Web Analytics defines a visit as “a successful page view that has an HTTP referer that doesn’t match the hostname of the request.” It’s not the same as Google’s “unique” metric, and Cloudflare says it may differ from other reporting tools. Weeding out bots from the total traffic numbers is a nascent feature that Cloudflare is improving as part of its Bot Management product.

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

                    Cloudflare Web Analytics is launching with features that are largely similar to Google Analytics but with some unique ways of zooming into different traffic segments and time ranges to see where traffic is originating from.

                    \n\n\n\n

                    “The most popular analytics services available were built to help ad-supported sites sell more ads,” Cloudflare product manager Jon Levine said. “But, a lot of websites don’t have ads. So if you use those services, you’re giving up the privacy of your users in order to understand how what you’ve put online is performing.

                    \n\n\n\n

                    “Cloudflare’s business has never been built around tracking users or selling advertising. We don’t want to know what you do on the Internet — it’s not our business.”

                    \n\n\n\n

                    Paying customers on the Pro, Biz, and Enterprise plans can access their analytics from their dashboards immediately. Cloudflare is also offering the product for free as JavaScript-based analytics for users who are not currently customers. Those who want access to the free plan can sign up for the waitlist.

                    \n\n\n\n

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 02 Oct 2020 04:03:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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: Virtual WordPress Page Builder Summit Kicks Off October 5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105570\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:179:\"https://wptavern.com/virtual-wordpress-page-builder-summit-kicks-off-october-5?utm_source=rss&utm_medium=rss&utm_campaign=virtual-wordpress-page-builder-summit-kicks-off-october-5\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6348:\"

                    From October 5 through October 9, the first Page Builder Summit will open its virtual doors to all attendees for free. Nathan Wrigley, the podcaster behind WP Builds, and Anchen le Roux, the founder and lead developer of Simply Digital Design, are hosting the five-day online event that focuses on the vast ecosystem of page builders for WordPress.

                    \n\n\n\n

                    The summit will include 35 sessions spread out over the event schedule. Each session will last around 30 minutes, so it will be easy to pop in and watch one in your downtime. Sessions will cover a range of builders, including the default WordPress block editor, Elementor, Beaver Builder, Oxygen, Brizy, and Divi.

                    \n\n\n\n

                    “It’s an event specifically for users of WordPress page builders, or those curious about what they can do,” said Wrigley. “I feel like a page builder style interface for creating websites is the future for our industry. WordPress itself is moving in this direction with the block editor (a.k.a. Gutenberg). With that in mind, it seemed like a good idea to create a dedicated event to share knowledge about this side of WordPress. We’ve tried to include presentations from as many page builders as we could.”

                    \n\n\n\n

                    Wrigley made sure to point out that it is not all geared toward developers, discussing the inner-workings of builders. Some of the sessions focus on marketing, optimization, and conversion, which provides a wider range of topics for potential attendees.

                    \n\n\n\n

                    The summit hosts created an online quiz for those who are unsure about which sessions to watch.

                    \n\n\n\n

                    There is a small catch. The sessions will be freely available only from the time they begin and the following 24 hours. After that, accessing the videos will come at a premium. Attendees can gain lifetime access to the PowerPack for $47 if they purchase within 15 minutes of signing up. Then, prices will rise to $97 until the event kicks off on October 5. Beyond, the price jumps to $147. The lifetime access includes access to the presentations, transcripts, a workbook, and other bonuses from the speakers.

                    \n\n\n\n

                    For those unsure about forking over the cash, they can still watch the sessions during the 24-hour window.

                    \n\n\n\n

                    The proceeds from the event will go out to paying affiliate commissions to speakers and partners. Some of it will go into planning and investing in a second summit down the road.

                    \n\n\n\n

                    “Both myself and Nathan have specific charities that we want to donate to after the event,” said le Roux. “It was part of our goals to be able to do this, but we didn’t want to make this an official contribution.”

                    \n\n\n\n

                    Why a Page Builder Summit?

                    \n\n\n\n

                    Both Wrigley and le Roux have their preferred builders. But, the goal of the summit is to offer a wide look at the tools available and help freelancers and agencies better streamline their businesses and create happier clients.

                    \n\n\n\n

                    “I’ve been a user of page builders for many years, but only at the point where they truly showed in the editing interface something that almost perfectly reflected what the end-user would see did I get really immersed,” said Wrigley. “Having come from a background in which I built entire websites from a collection of text files (HTML, CSS, PHP, etc.), I was fascinated that we’d reached a point where the learning curve for building a good website was significantly reduced.”

                    \n\n\n\n

                    He pointed out that it is not always so simple though. While the same level of coding skills may not be necessary, people must figure out how to navigate their preferred page builder, which can come with its own learning curve.

                    \n\n\n\n

                    “You need to learn their way of doing things and how to achieve your design choices,” he said. “It’s always going to work out better if you know the code, but the WordPress mission of democratizing publishing certainly seems to align quite nicely with the adoption of tools, like page builders, which mean that once-difficult tasks are now easier.”

                    \n\n\n\n

                    For le Roux, her interest in hosting the Page Builder Summit falls back to her design studio.

                    \n\n\n\n

                    “As a developer, my main reason for switching to page builders was around streamlining and creating more efficient but quality websites in the shortest amount of time,” she said. “Especially now that we focus on day rates, creating the best possible website that clients would love fast would not have been possible without page builders.”

                    \n\n\n\n

                    The Hosts’ Go-To Builders

                    \n\n\n\n

                    “We prefer using Beaver Builder with Themer at Simply Digital Design,” said le Roux. “We use Gutenberg for blog posts or where possible with custom post types or LMS software. However, we’ve also taken on a few Elementor projects where that’s the client’s preferred option.”

                    \n\n\n\n

                    Wrigley uses some of the same tools. His main work is on the WP Builds website where he hosts podcasts.

                    \n\n\n\n

                    “I have used Beaver Builder’s Themer to create templates for specific layouts, but for content creation within those layouts I’m using the block editor,” said Wrigley. “My content is mainly text and the WordPress editor is utterly remarkable in this situation. I kept the classic editor installed for a few months after WordPress 5.0 came about, but I soon realized that this was folly and that the editing interface of Gutenberg is superior. The ability to insert and move text, buttons, etc. is such a joy to work with, and the iterations that have been made in the last two years make it, in my opinion, the best text editing experience on the web.”

                    \n\n\n\n

                    Wrigley sees a future in which the WordPress block editor takes over much of the work that page builders are currently handling. However, that future is “still over the horizon.”

                    \n\n\n\n

                    “I’m excited about this future though, and we’ve got a few crystal ball-gazing presentations; trying to work out what that future might look like,” he 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:\"Thu, 01 Oct 2020 20:31: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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:99:\"WPTavern: Jetpack 9.0 to Introduce New Feature for Publishing WordPress Posts to Twitter as Threads\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105448\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:243:\"https://wptavern.com/jetpack-9-0-to-introduce-new-feature-for-publishing-wordpress-posts-to-twitter-as-threads?utm_source=rss&utm_medium=rss&utm_campaign=jetpack-9-0-to-introduce-new-feature-for-publishing-wordpress-posts-to-twitter-as-threads\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3318:\"

                    Jetpack 9.0, coming on October 6, will debut a new feature that allows users to share blog posts as Twitter threads in multiples tweets. A recent version of Jetpack introduced the ability to import and unroll tweetstorms for publishing inside a post. The 9.0 release will run it back the other way so the content originates in WordPress, yet still reaps all the same benefits of circulation on Twitter as a thread.

                    \n\n\n\n

                    The new Twitter threads feature is being added as part of Jetpack’s Publicize module under the Twitter settings. After linking up a Twitter account, the Jetpack sidebar options for Publicize allow users to publish to Twitter as a link to the blog or a set of threaded tweets. It’s not just limited to text content – the threads feature will also upload and attach any images and videos included in the post.

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

                    When first introduced to the idea of publishing a Twitter thread from WordPress, I wondered if threads might lose their trademark pithy punch, since users aren’t forced to keep each segment to the standard length of a tweet. Would each tweet be separated in an odd, unreadable way? The Jetpack team anticipated this, so the thread option adds more information to the block editor to show where the paragraphs will be split into multiple tweets.

                    \n\n\n\n

                    “Threads are wildly underused on Twitter,” Gary Pendergast said in a post introducing the feature. “I think a big part of that is the UI for writing threads: while it’s suited to writing a thread as a series of related tweet-sized chunks, it doesn’t lend itself to writing, revising, and editing anything more complex.” The tool Pendergast has been working on for Jetpack gives users the best of both worlds.

                    \n\n\n\n

                    In response to a comment requesting Automattic “concentrate on tools to get people off social media,” Pendergast said, “If we’re also able to improve the quality of conversations on social media, I think it’d be remiss of us to not do so.” He also credits IndieWeb discussions on Tweetstorms and POSSE (Publish (on your) Own Site, Syndicate Elsewhere) as inspirations for the feature.

                    \n\n\n\n

                    For years, blogging advocates have tried to convince those who post lengthy tweetstorms to switch to a publishing medium that is more suitable to the length of their thoughts. The problem is that Twitter users lose so much of the immediate feedback and momentum that their thoughts would have generated when composed as a tweetstorm.

                    \n\n\n\n

                    Instead of lecturing people about how they should really be blogging instead of tweetstorming, Jetpack is taking a fresh approach by enabling full content ownership with effortless social syndication. You can test out the experience for yourself by adding the Jetpack Beta Testers plugin and running the 9.0 RC version on your site.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 01 Oct 2020 02:56:46 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:63:\"WPTavern: Ask the Bartender: How To WordPress in a Block World?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105491\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:167:\"https://wptavern.com/ask-the-bartender-how-to-wordpress-in-a-block-world?utm_source=rss&utm_medium=rss&utm_campaign=ask-the-bartender-how-to-wordpress-in-a-block-world\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9752:\"

                    I love your articles. And now, in the middle of the WordPress revolution, I realized I’m constantly searching for an answer regarding WP these days.

                    So many things are being said, so many previsions of the future, problems, etc., but, right now, I think I, as a designer, just want to understand one thing that seemed answered already but it’s never clear:

                    Is WordPress a good choice to build a client’s template where he just has to insert the info that will show in the frontend where I want to? And he doesn’t have to worry about formatting blocks? I love blocks, don’t get me wrong, but will normal templating end?

                    I just think that having a super CMS, HTML, CSS, and being able to play with a database with ACF is so powerful, that I’m wondering if it’s lost. After so much reading, I still don’t understand if this paradigm is going to disappear.

                    Right now, I don’t know if it’s best to stop making websites as I used to and adopt block patterns instead.

                    Ricardo
                    \n\n\n\n

                    WordPress is definitely changing. Over the past two years, we have seen much of it reshaped into something different from the previous decade and more. However, this is not new. WordPress has always been a constantly-changing platform. It just feels far too different this time around, almost foreign to many. The platform had to make a leap. Otherwise, it would have started falling behind.

                    \n\n\n\n

                    And, it is a big ask of the existing community to come along with it, to take that leap together.

                    \n\n\n\n

                    It can be scary as a developer whose livelihood has depended on things working a certain way or who has built tools and systems around pre-block WordPress. Many freelancers and agencies had their world turned upside down with the launch of the block editor. It is perfectly OK to feel a bit lost.

                    \n\n\n\n

                    Now, it is time for a little tough love. It has been two years. As a professional, you need to have a plan in place already. Whether that is an educational plan for yourself or a transitional plan for your clients, you should already be tackling projects that leverage the block editor. If you are at a point where you have not been building with blocks, you are now behind. However, you can still catch up and continue advancing in your WordPress career.

                    \n\n\n\n

                    There are so many changes coming down the pipeline that anyone who plans to develop for WordPress will be in continual education mode for years to come.

                    \n\n\n\n

                    When building for clients, the biggest thing to remember is that it is not about you. It is about getting something into the hands of your clients that addresses their specific needs. Freelancers and agencies need to often be the Jacks and Jills of all trades. Sometimes, this even means having a backup CMS or two that you can use that are not named WordPress. It helps to be well-rounded enough to jump around when needed, especially if you are not a point in your career where you can demand specific work and pass on jobs that would put food on the table.

                    \n\n\n\n

                    It is also easy to look at every job as a nail and WordPress as the hammer. Or, even specific plugins as the tool that will always get the job done. I have seen developers in the past rely on tools like ACF, CMB2, or Meta Box but could not code a custom metadata solution when necessary to save their life. Sometimes a bigger toolbox is necessary.

                    \n\n\n\n

                    Every WordPress developer needs a solid, foundational understanding of the languages that WordPress uses. Gone are the days of skating by on HTML, CSS, and PHP knowledge. You need to learn JavaScript deeply. Matt Mullenweg, the co-founder of WordPress, was not joking around when he said this back in 2015. It holds true more and more each day. In another five years, it will tough to be a developer in the WordPress world without knowing JavaScript, at least for backend work.

                    \n\n\n\n

                    It also depends on what types of sites you are building. If you are primarily handling front-end design, you will likely be able to get by with a lower skill level. You will just need to know the “WordPress way” of building themes.

                    \n\n\n\n

                    Within the next year, you should be able to build just about any theme design with decent CSS and HTML knowledge along with an understanding of how the block system works. Full-site editing and block-based themes will change how we build the front end of the web. It is going to be a challenging transition at first, especially for those of us who are steeped in traditional theme development, but client sites will often be far easier to build. I highly recommend the twice-monthly block-based themes meetings if your focus is on the front end.

                    \n\n\n\n

                    Block Templates

                    \n\n\n\n

                    Based on your question, I am going to make some assumptions. You have a history of essentially building out meta boxes via ACF where the client just pops in their data. Then, you format that data on the front end. You are likely mixing this with custom post types (CPTs). This is a fairly common scenario.

                    \n\n\n\n

                    One of the great things about the block system is that you can lock the post editor for individual CPTs. WordPress already has you covered with its block templates feature, which allows you to define just what a post should look like. You can set up which blocks you want to appear and have the client drop their content in. At the moment, this feature is limited to the post type level. However, it should grow more robust over time, particularly when it works alongside the traditional “page templates” system.

                    \n\n\n\n

                    Block templates are a powerful tool in the ol’ toolbox that will come in handy when building client sites.

                    \n\n\n\n

                    Block Patterns

                    \n\n\n\n

                    You do not have to stop making websites as you are accustomed to at the moment. However, you should start leveraging new block features as they become available and make sense for a specific project. I am a fanatic when it comes to block patterns, so my bias will definitely show.

                    \n\n\n\n

                    The biggest thing with block patterns and clients is education. For the uninitiated, you will need to spend some time teaching them how to insert a pattern and how it can be used to their advantage. That is the hurdle you must jump.

                    \n\n\n\n

                    For many of the users that I have seen introduced to well-designed patterns, they have fallen in love with the feature. Even many who were reluctant to switch to the block editor became far more comfortable working with it after learning how patterns worked. This is not the case for every user or client, but it has been a good introduction point to the block editor for many.

                    \n\n\n\n

                    To answer your question regarding patterns: yes, you should absolutely begin to adopt them.

                    \n\n\n\n

                    ACF Is Evolving

                    \n\n\n\n

                    Because you are accustomed to ACF, you should be aware that the framework is evolving to keep up with the block editor. Version 5.8.0 introduced a PHP framework for creating custom blocks over a year ago. And, it has been improving ever since. There are even projects like ACF Blocks, which will provide even more tools for your arsenal.

                    \n\n\n\n

                    It is important to learn from what some of the larger agencies are doing. Read up on how WebDevStudios is tackling block development. The company also has an open-source block library for ACF.

                    \n\n\n\n

                    Solving Problems

                    \n\n\n\n

                    Your job as a developer is to be a problem solver. Whatever system you are building with is merely a part of your toolset. You need to be able to solve issues regardless of what tool you are using. At the end of the day, it is just code. If you can learn HTML, you can learn CSS. If you can learn those, you can learn PHP. And, if you can manage PHP, you can certainly pick up JavaScript.

                    \n\n\n\n

                    A decade or two from now, you will need to learn something else to stay relevant in your career. Web technology changes. You must change with it. Always consider yourself a student and continue your education. Surround yourself and learn from those who are more advanced than you. Emulate, borrow, and steal good ideas. Use what you have learned to make them great.

                    \n\n\n\n

                    There is no answer I can give that will be perfect for every scenario. Each client is unique, and you will need to decide the best direction for each.

                    \n\n\n\n

                    However, yes, you should already be on the path to building with a block-first mindset if you plan to continue working with WordPress for the long haul. Immerse yourself in the system. Read, study, and build something any chance you get.

                    \n\n\n\n

                    This is the first post in the Ask the Bartender series. Have a question of your own? Shoot it over.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 30 Sep 2020 20:35: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:14:\"Justin Tadlock\";s: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:91:\"WPTavern: Supercharge the Default WordPress Theme With Twentig, a Toolbox for Twenty Twenty\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105344\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:225:\"https://wptavern.com/supercharge-the-default-wordpress-theme-with-twentig-a-toolbox-for-twenty-twenty?utm_source=rss&utm_medium=rss&utm_campaign=supercharge-the-default-wordpress-theme-with-twentig-a-toolbox-for-twenty-twenty\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6455:\"Custom page pattern from the Twentig plugin.\n\n\n\n

                    I am often on the hunt for those hidden gems when it comes to block-related plugins. I like to see the interesting places that plugin authors venture. That is why it came as a surprise when someone recommended I check out the Twentig plugin a few days ago. Somehow, it has flown under my radar for months. And, it has managed to do this while being one of the more interesting plugins for WordPress I have seen in the past year.

                    \n\n\n\n

                    Twentig is a plugin that essentially gives superpowers to the default Twenty Twenty theme. Diane and Yann Collet are the sibling co-founders and brains behind the plugin.

                    \n\n\n\n

                    While I have been generally a fan of Twenty Twenty since it was first bundled in core, it was almost a bit of a letdown in some ways. It was supposed to be the theme that truly showcased what the block editor could do — and it does a fine job of styling the default blocks — but there was a lot of potential left on the table. The Twentig plugin turns Twenty Twenty into something worthier of a showcase for the block editor. It is that missing piece, that extra mile in which WordPress should be marching its default themes.

                    \n\n\n\n

                    While the new Twenty Twenty-One default theme is just around the corner, Twentig is breathing new life into the past year’s theme. The developers behind the plugin are still fixing bugs and bringing new features users.

                    \n\n\n\n

                    Of its 34 reviews on WordPress.org, Twentig has earned a solid five-star rating. That is a nice score for a plugin with only 4,000 active installations. As I said, it has flown under the radar a bit, but the users who have found it have obviously discovered something that adds those extra touches to their sites they need.

                    \n\n\n\n

                    What Does Twentig Do?

                    \n\n\n\n

                    It is a toolbox for Twenty Twenty. The headline feature is its block editor features, such as custom patterns and page layouts. It also offers a slew of customizer options that allow end-users to put their own design spin on the default theme. However, my interest is primarily in how it extends the block editor.

                    \n\n\n\n

                    Let’s get this out of the way up front. Twentig’s one downside is that it adds a significant amount of additional CSS on top of the already-heavy Twenty Twenty and block editor styles. I will blame the current lack of a full design system from WordPress on most of this. Styling for the block editor can easily bloat a stylesheet. Adding an extra 100+ kb per page load might be a blocker for some who would like to try the plugin. Users will need to weigh the trade-offs between the additional features and the added page size.

                    \n\n\n\n

                    The thing that makes Twentig special is its extensive patterns and pages library, which offers one-click access to hundreds of layouts specifically catered to the Twenty Twenty theme.

                    \n\n\n\nInserting one of the hero patterns.\n\n\n\n

                    It took me a few minutes to figure out how to access the patterns — mainly because I did not read the manual. I expected to find them mixed in with the core patterns inserter. However, the plugin adds a new sidebar panel to the editor, which users can access by clicking the “tw” icon. After seeing the list of options, I can understand why they probably would not fit into WordPress’s limited block and patterns inserter UI.

                    \n\n\n\n

                    It would be easier to list what the plugin does not have than to go through each of the custom patterns and pages.

                    \n\n\n\n

                    The one thing that truly sets this plugin apart from the dozens of other block-library types of plugins is that there are no hiccups with the design. Almost every similar plugin or tool I have tested has had CSS conflicts with themes because they are trying to be a tool for every user. Twentig specifically targets the Twenty Twenty theme, which means it does not have to worry about whether it looks good with the other thousands of themes out there. It has one job, which is to extend its preferred theme, and it does it with well-designed block output.

                    \n\n\n\n

                    The other aspect of this is that it does not introduce new blocks. Every pattern and page layout option uses the core WordPress blocks, which includes everything from hero sections to testimonials to pricing tables to event listings. And more.

                    \n\n\n\n

                    Twentig does not stop adding features to the block editor with custom patterns. The useful and sometimes fun bits are on the individual block level, and I have yet to explore everything. I continue to discover new settings each time I open my editor.

                    \n\n\n\n

                    Whether it is custom pullquote styles, a photo image frame, or an inner border tweak to the Cover block (shown below), the plugin adds little extras that push what users can do with their content.

                    \n\n\n\nInner border style for the Cover block.\n\n\n\n

                    Each block also gets some basic top and bottom margin options, which comes in handy when laying out a page. At this point, I am simply looking forward to discovering features I have yet to find.

                    \n\n\n\n

                    Areas Themes Should Explore

                    \n\n\n\n

                    One of the things I dislike about many of these features being within the Twentig plugin is that I would like to see them within the Twenty Twenty theme instead. Obviously not every feature belongs in the theme — some features firmly land in plugin territory. The default WordPress themes should also leave some room for plugin authors to explore. But, shipping some of the more prominent patterns and styles with Twenty Twenty would make a more robust experience for the average end-user looking to get the most out of blocks.

                    \n\n\n\n

                    Block patterns were not a core WordPress feature when Twenty Twenty landed. However, for the upcoming Twenty Twenty-One theme, which is expected to bundle some unique patterns, the design team should explore what the Twentig plugin has brought to the current default. That is the direction that theme development should be heading, and theme developers can learn a lot by stealing borrowing from this 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:\"Tue, 29 Sep 2020 22:00:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:105:\"WPTavern: Coming in Jetpack 9.0: Shortcode Embeds Module Updated to Handle Facebook and Instagram oEmbeds\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105381\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:253:\"https://wptavern.com/coming-in-jetpack-9-0-shortcode-embeds-module-updated-to-handle-facebook-and-instagram-oembeds?utm_source=rss&utm_medium=rss&utm_campaign=coming-in-jetpack-9-0-shortcode-embeds-module-updated-to-handle-facebook-and-instagram-oembeds\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2938:\"

                    Facebook and Instagram are dropping unauthenticated oEmbed support on October 24. WordPress will be removing both Facebook and Instagram as oEmbed providers in an upcoming release. After evaluating third-party solutions, WordPress VIP is recommending its partners enable Jetpack’s Shortcode Embeds module. Jetpack will be shipping the update in its 9.0 release, which is anticipated to land prior to the October 24th deadline.

                    \n\n\n\n

                    The module is being updated to provide a seamless transition for users who might otherwise be negatively impacted by Facebook’s upcoming API change. WordPress contributors have run some simulations but are not yet sure what will happen to the display for previously embedded content.

                    \n\n\n\n

                    “It is possible that they change the contents of the JS file to manipulate cached embeds, perhaps to display a warning that the site is using an old method to embed content or that the request is not properly authenticated,” Jonathan Desrosiers commented on the trac ticket for removing the oEmbed providers.

                    \n\n\n\n

                    WordPress.com VIP roughly outlined what users can expect if they do not enable a solution to begin authenticating oEmbeds:

                    \n\n\n\n

                    By default, WordPress caches oEmbed contents in post metadata. These embeds will continue to display in previously-published content. If you edit older posts in the Block Editor, regardless of whether you update the post by saving changes, the embeds in the post will no longer be cached and will stop displaying. If you view these older posts using the Classic Editor, so long as the post is not re-saved, the embeds will continue to function and display properly. If you update the post content, the embed will cease functioning unless you have a mitigation installed.

                    \n\n\n\n

                    Although WordPress VIP recommends using the Jetpack module as the best solution, self-hosted WordPress users may want to investigate other options if they are not already using Jetpack. oEmbed Plus is a free plugin created specifically for solving the problem of WordPress dropping Facebook and Instagram as oEmbed providers but it is more work to set up and configure. It requires users to register as a Facebook developer and create an app to get API credentials.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 29 Sep 2020 21:18:52 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s: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:52:\"WPTavern: W3C Selects Craft CMS for Redesign Project\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105265\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:149:\"https://wptavern.com/w3c-selects-craft-cms-for-redesign-project?utm_source=rss&utm_medium=rss&utm_campaign=w3c-selects-craft-cms-for-redesign-project\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:9407:\"

                    W3C has selected Craft CMS over Statamic for its redesign project, after dropping WordPress from consideration in an earlier round of elimination:

                    \n\n\n\n

                    In the end, our decision mostly came down to available resources. Craft had already committed to reach AA compliance in Craft 4 (it is currently on version 3.5, the release of version 4 is planned for April 2021). They had also arranged for an external agency to provide them with accessibility issues to tackle weekly. In the end, they decided instead to hire an in-house accessibility specialist to perform assessments and assist the development team in adopting accessibility patterns in the long run.

                    W3C CMS Selection Report
                    \n\n\n\n

                    Last week we published a post urging W3C to revisit Gutenberg for a fair shake against the proprietary CMS’s or consider adopting another open source option. During the selection process, Studio 24, the agency contracted for the redesign, cited its extensive experience with WordPress as the reason for not performing any accessibility testing on more recent versions of Gutenberg.

                    \n\n\n\n

                    When asked if the team contacted anyone from WordPress’ Accessibility Team during the process or put Gutenberg through the same tests as the proprietary CMS’s, Studio 24 founder Simon Jones confirmed they had not.

                    \n\n\n\n

                    “No, we only reached out to the two shortlisted CMS’s” Jones said. “I’m afraid we didn’t have time to do more. We did test GB a few months ago based on editing content – though it wasn’t the only factor in our choice. As an agency we do plan to keep reviewing GB in the future.”

                    \n\n\n\n

                    In response to our concerns regarding licensing, Jones penned an update titled “On not choosing WordPress,” which further elaborated on the reasons why the agency was not inclined towards using or evaluating the new editor:

                    \n\n\n\n

                    From a business perspective I also believe Gutenberg creates a complexity issue that makes it challenging for use by many agencies who create custom websites for clients; where we have a need to create lots of bespoke blocks and page elements for individual client projects.

                    The use of React complicates front-end build. We have very talented front-end developers, however, they are not React experts – nor should they need to be. I believe front-end should be built as standards-compliant HTML/CSS with JavaScript used to enrich functionality where necessary and appropriate.

                    As of yet, we have not found a satisfactory (and profitable) way to build custom Gutenberg blocks for commercial projects. 

                    \n\n\n\n

                    The CMS selection report also stated that W3C needs the CMS to be “usable by non-sighted users” by the launch date, since some members of the staff who contribute to the website are non-sighted.

                    \n\n\n\n

                    Since the most recent version of WordPress was not tested in comparison with the proprietary CMS’s, it’s unclear how much better they handle accessibility. Ultimately, W3C and Studio 24 were more comfortable moving forward with a proprietary vendor that was able to make certain assurances about the future accessibility of its authoring tool, despite having a smaller pool of contributors.

                    \n\n\n\n

                    “[I’m] also deeply curious since the cursory notes on accessibility for both of the reviewed CMSes seem to highlight a ton of issues like ‘Buttons and Checkboxes are built using div elements’ or most inputs lacking clear focus styles,” Gutenberg technical lead Matías Ventura said. “An element like the Calendar for choosing a post date seems entirely inoperable with keyboard on Craft, for example, while WordPress’ has had significant effort and rounds of feedback poured into that element alone to make it fully operable.”

                    \n\n\n\n

                    WordPress developer Anthony Burchell commented on how using a relatively new proprietary CMS seemed counter to W3C’s stated goal to select an option on the basis of longevity. Craft CMS’s continued success is contingent upon its business model and the company’s ability to remain profitable.

                    \n\n\n\n

                    “FOSS have the same opportunity of direct access to developers,” Burchell said. “I recognize there are many accessibility shortcomings in popular software, but I think it’s more constructive to rally behind and contribute, not use a proprietary CMS that boasts beer budget in their guidelines.”

                    \n\n\n\n

                    On the other side of the issue, accessibility advocates took the W3C’s decision as a referendum on Gutenberg’s continued struggles to meet WCAG AA standards. WordPress accessibility specialist Amanda Rush said it was “nice to see the W3C flip tables over this.”

                    \n\n\n\n

                    “Gutenberg is not mature software,” accessibility consultant and WordPress contributor Joe Dolson said in a post elaborating on his comments at WPCampus 2020 Online. He emphasized the lack of stability in the project that Studio 24 alluded to when documenting the reasons against using WordPress.

                    \n\n\n\n

                    “It is still undergoing rapid changes, and has grand goals to add a full-site editing experience for WordPress that almost guarantees that it will continue to undergo rapid changes for the next few years,” Dolson said. “Why would any organization that is investing a large amount into a site that they presumably hope will last another 10 years want to invest in something this uncertain?”

                    \n\n\n\n

                    Dolson also said the accessibility improvements he referenced regarding the audit were only a small part of the whole picture.

                    \n\n\n\n

                    “They only encompass issues that existed in the spring of 2019,” he said. “Since then, many features have been added and changed, and those features both resolve issues and have created new ones. The accessibility team is constantly playing catch up to try and provide enough support to improve Gutenberg. And even now, while it is more or less accessible, there are critical features that are not yet implemented. There are entirely new interface patterns introduced on a regular basis that break prior accessibility expectations.”

                    \n\n\n\n

                    WordPress is also being used by millions of people who are constantly reporting issues to fuel the software’s continued refinement, which increases the backlog of issues. Unfortunately, Studio 24 did not properly evaluate Gutenberg against the proprietary CMS’s in order to determine if these software projects are in any better shape.

                    \n\n\n\n

                    Instead, they decided that Craft CMS’s community was more receptive to collaborating on issues without reaching out to WordPress. Given the W3C’s stated preference for open source software, WordPress, as the only CMS under consideration with an OSD-compliant license, should have received the same accessibility evaluation.

                    \n\n\n\n

                    “I can’t make any statements that would be meaningful about the other content management systems under consideration; but if WordPress wants to be taken seriously in environments where accessibility is a legal, ethical, and mission imperative, there’s still a lot of work to be done,” Dolson said.

                    \n\n\n\n

                    Studio 24’s evaluation may not have been equitable to the only open source CMS under consideration, but the situation serves to highlight a unique quandary: when using open source software becomes the impractical choice for organizations requiring a high level of accessibility in their authoring tools.

                    \n\n\n\n

                    “Studio 24 ultimately determined that working with a CMS to make it better was more possible with a smaller, proprietary vendor than with a large open-source project,” accessibility advocate Brian DeConinck said. “Project leadership would be more receptive, and the smaller community means changes can be made more quickly. That should prompt a lot of soul-searching for…well, everyone. What does that say about the future of open source?”

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 29 Sep 2020 04:56: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: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:30:\"Gary: More than 280 characters\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:25:\"https://pento.net/?p=5405\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://pento.net/2020/09/29/more-than-280-characters/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5187:\"

                    It’s hard to be nuanced in 280 characters.

                    \n\n\n\n

                    The Twitter character limit is a major factor of what can make it so much fun to use: you can read, publish, and interact, in extremely short, digestible chunks. But, it doesn’t fit every topic, ever time. Sometimes you want to talk about complex topics, having honest, thoughtful discussions. In an environment that encourages hot takes, however, it’s often easier to just avoid having those discussions. I can’t blame people for doing that, either: I find myself taking extended breaks from Twitter, as it can easily become overwhelming.

                    \n\n\n\n

                    For me, the exception is Twitter threads.

                    \n\n\n\n

                    Twitter threads encourage nuance and creativity.

                    \n\n\n\n

                    Creative masterpieces like this Choose Your Own Adventure are not just possible, they rely on Twitter threads being the way they are.

                    \n\n\n\n
                    \n

                    Being Beyoncé’s assistant for the day: DONT GET FIRED THREAD pic.twitter.com/26ix05Hkhp

                    — green chyna (@CORNYASSBITCH) June 23, 2019
                    \n
                    \n\n\n\n

                    Publishing a short essay about your experiences in your job can bring attention to inequality.

                    \n\n\n\n
                    \n

                    DOWNTOWN BROOKLYN: I\'m working arraignments tonight, representing poor New Yorkers who were arrested yesterday on Thanksgiving.

                    It was the coldest Thanksgiving in more than a century. Tonight\'s also bitterly cold, even in the courtroom. I\'m wearing my scarf & coat.

                    — Rebecca Kavanagh (@DrRJKavanagh) November 24, 2018
                    \n
                    \n\n\n\n

                    And Tumblr screenshot threads are always fun to read, even when they take a turn for the epic (over 4000 tweets in this thread, and it isn’t slowing down!)

                    \n\n\n\n
                    \n

                    Tumblr textposts thread, probably?

                    — we are a family forged in bureaucracy (@ex_aItiora) August 26, 2019
                    \n
                    \n\n\n\n

                    Everyone can think of threads that they’ve loved reading.

                    \n\n\n\n

                    My point is, threads are wildly underused on Twitter. I think I big part of that is the UI for writing threads: while it’s suited to writing a thread as a series of related tweet-sized chunks, it doesn’t lend itself to writing, revising, and editing anything more complex.

                    \n\n\n\n

                    To help make this easier, I’ve been working on a tool that will help you publish an entire post to Twitter from your WordPress site, as a thread. It takes care of transforming your post into Twitter-friendly content, you can just… write. \"🙂\"

                    \n\n\n\n

                    It doesn’t just handle the tweet embeds from earlier in the thread: it handles handle uploading and attaching any images and videos you’ve included in your post.

                    \n\n\n\n
                    • \"A
                    • \"A
                    • \"A
                    • \"A
                    \n\n\n\n

                    All sorts of embeds work, too. \"😉\"

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

                    It’ll be coming in Jetpack 9.0 (due out October 6), but you can try it now in the latest Jetpack Beta! Check it out and tell me what you think. \"🙂\"

                    \n\n\n\n

                    This might not fix all of Twitter’s problems, but I hope it’ll help you enjoy reading and writing on Twitter a little more. \"💖\"

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 29 Sep 2020 02:33: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:4:\"Gary\";s: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:100:\"WPTavern: Themes Team Releases a Web Fonts Loader, Likely To Prohibit Hotlinking Any Off-Site Assets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105363\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:243:\"https://wptavern.com/themes-team-releases-a-web-fonts-loader-likely-to-prohibit-hotlinking-any-off-site-assets?utm_source=rss&utm_medium=rss&utm_campaign=themes-team-releases-a-web-fonts-loader-likely-to-prohibit-hotlinking-any-off-site-assets\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5815:\"

                    Last Friday, the WordPress Themes Team announced the release of its new Webfonts Loader project. It is a drop-in script that allows theme authors to load web fonts from the user’s site instead of a third-party CDN. The secondary message included in the team’s announcement is that it no longer plans to allow themes to hotlink Google Fonts in the future.

                    \n\n\n\n

                    Throughout most of the team’s history, it has not allowed themes to hotlink or use CDNs for hosting theme assets, such as CSS, JavaScript, and fonts. The one exception to this rule was the use of Google Fonts. This allowed themes to have richer typography options at their disposal from what the team has generally declared a reliable source.

                    \n\n\n\n

                    “The exception was made because there was no practical way to not have the exception at the time,” said Aria Stathopoulos, a Themes Team representative and developer behind the Webfonts Loader project. “The exception for Google Fonts was made out of necessity. Now that there is another way, the exception will not be necessary.”

                    \n\n\n\n

                    In effect, disallowing the Google Fonts CDN would not be a new ban. It would be a removal of an exception to the existing ban.

                    \n\n\n\n

                    Google Fonts has become so embedded into the theme developer toolset over the years, there was no way the team could simply pull the plug and prohibit the use of the CDN overnight. If the Themes Team members wanted to focus more on privacy, they would need to build a tool that made it dead simple for theme authors to use.

                    \n\n\n\n

                    There is no hard deadline for when the team will remove the exception for Google Fonts, and it is not set in stone at this point. Stathopoulos said removing it has been the goal from the beginning, disallowing all CDNs. However, it took a while to find an efficient way to handle this. With a viable alternative in place, they can discuss moving forward.

                    \n\n\n\n

                    Webfonts Loader for Themes

                    \n\n\n\n

                    The Webfonts Loader project keeps it simple for theme authors. It introduces a new wptt_get_webfont_styles() function that developers can plug in a stylesheet URL. Once a page is loaded with that function call, it will download the fonts locally to a /fonts folder in the user’s /wp-content directory. This way, fonts will always be served from the user’s site.

                    \n\n\n\n

                    The system is not limited to Google Fonts either. Any URL that serves CSS with an @font-face {} rule will work. It does not currently include authentication for CDNs that require API keys, such as Adobe Fonts. However, that is something the team might add in the future.

                    \n\n\n\n

                    “For end-users, moving away from CDNs and locally hosting web fonts will improve performance (fewer handshake roundtrips for SSL), and is the privacy-conscious choice,” said Stathopoulos. “The only ‘valid privacy concern’ is that the web fonts’ CDN does not disclose information that is fundamental to the GDPR: what information gets logged, for how long these logs remain, how they are processed, if there is any cross-referencing with all the other wealth of information the company has from users, etc. The concern is a lack of disclosure and information. If a site owner doesn’t know what kind of information a third-party logs for its visitors, then they should ethically not enforce that on their visitors. With this package, the CDN is removed from the equation and the font still gets served fast — if not faster.”

                    \n\n\n\n

                    A Path to Core WordPress

                    \n\n\n\n

                    Today, there is now a broader focus on privacy concerns related to third-party resources, particularly with tech giants like Google. Such concerns extend to whether third parties are tracking users or collecting data. Additional concerns are around whether sites are disclosing the use of third-party resources, which may be required in some jurisdictions. Site owners who are often unable to work through the web of potential issues are stuck in the middle.

                    \n\n\n\n

                    Jono Alderson opened a ticket to create an API for loading web fonts locally in core WordPress in February 2019. It is a lengthy and detailed proposal, but it has yet to see much buy-in outside of a handful of developers.

                    \n\n\n\n

                    “If such a script is standardized and included in WordPress core, one of the main benefits would be more respect for the end-user’s privacy,” said Stathopoulos. “In the end, that’s all privacy is about: respecting users.”

                    \n\n\n\n

                    A standard API like Alderson proposes could solve some issues. Namely, it would virtually eliminate any privacy concerns. However, loading fonts locally could allow WordPress to optimize font loading and would create a shared system where plugins and themes do not load duplicate assets because of the current limitations of the enqueuing system. A standard API would also put the responsibility of efficiently loading fonts on WordPress’s shoulders instead of theme and plugin developers.

                    \n\n\n\n

                    The Themes Team’s new project is a solid start and strengthens the current proposal.

                    \n\n\n\n

                    “If we’re serious about WordPress becoming a fast, privacy-friendly platform, we can’t rely on theme developers to add and manage fonts without providing a framework to support them,” wrote Alderson in the ticket.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 28 Sep 2020 20:58: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:14:\"Justin Tadlock\";s: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:87:\"WPTavern: Fuxia Scholz First to Pass 100K Reputation Points on WordPress Stack Exchange\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:219:\"https://wptavern.com/fuxia-scholz-first-to-pass-100k-reputation-points-on-wordpress-stack-exchange?utm_source=rss&utm_medium=rss&utm_campaign=fuxia-scholz-first-to-pass-100k-reputation-points-on-wordpress-stack-exchange\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5096:\"

                    Fuxia Scholz, a prolific WordPress Stack Exchange (WPSE) contributor, is the first member to reach 100,000 reputation points. The popular Q&A community site rewards expert advice by floating the highest quality answers to the top, allowing users to earn reputation points. The gamified help community has proven to be more motivating for developers than many traditional forums, since the upvotes communicate how useful their answers are to others.

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

                    Scholz started on Stack Overflow a few months before WordPress had its own site. She wrote around 50 answers and made connections with other WordPress developers ahead of the site’s beta phase in June 2010. Once the site graduated and got its own logo and design, Scholz started writing more.

                    \n\n\n\n

                    “One core idea for all Stack Exchange sites is gamification: You earn reputation, and you get access to certain privileges,” Scholz said.

                    \n\n\n\n

                    “You can say I got a bit addicted. My favorite questions were about problems for which I didn’t know the answer, and couldn’t find one with a search engine, because no one else had solved that before. I used my answers to teach myself, and I learned a lot this way! In May 2011 my reputation on WPSE was already higher than on Stack Overflow, and for the next years it went up in a steep curve.” Ten years after WPSE launched, Scholz has become the first to reach 100,000 reputation points.

                    \n\n\n\n

                    “What reputation and karma do is send a message that this is a community with norms, it’s not just a place to type words onto the internet. (That would be 4chan.)” Stack Overflow co-creator Joel Spolsky said. “We don’t really exist for the purpose of letting you exercise your freedom of speech. You can get your freedom of speech somewhere else. Our goal is to get the best answers to questions. All the voting makes it clear that we have standards, that some posts are better than others, and that the community itself has some norms about what’s good and bad that they express through the vote.”

                    \n\n\n\n

                    The reputation points were originally inspired by Reddit Karma. Spolsky admits that the points not a perfect system but they do tend to “drive a tremendous amount of good behavior.” Gamification can shape and encourage certain behaviors but Spolsky said it’s a weak force that cannot motivate people to do things they are not already interested in doing. For Scholz, it was the community aspect and an earned sense of ownership and responsibility that kept her hooked.

                    \n\n\n\n

                    “In 2012, the community elected me as a moderator, and that changed a lot,” she said. “Now it wasn’t just a game anymore, it was a duty. I felt responsible for the site. I still do. I also found some friends on there. We met at WordCamps and in private, and worked together on different projects.”

                    \n\n\n\n

                    Scholz no longer works in development and said she doesn’t care about WordPress anymore, but she is still a regular contributor on the WPSE.

                    \n\n\n\n

                    “I switched careers and work as a writer, translator, and community manager for Chess24.com now,” she said. “But I still care about the site WordPress Stack Exchange! I keep an eye on new tags, handle flagged posts and comments, try to make every new user feel welcome, and I search for people who are abusing the system — vote fraud and spam. And, very rarely, I even write an answer, because I still know all this stuff.

                    \n\n\n\n

                    “Checking the site has become a part of my daily routine, like feeding the cat.”

                    \n\n\n\n

                    This daily habit has snowballed into Scholz racking up more than 2,000 answers. She is getting upvotes on many of her old answers nearly every day, which is what pushed her over the 100k milestone.

                    \n\n\n\n

                    “There is a lot to say about the way our site developed over the years,” Scholz said. “I’m not happy about some things. The enthusiasm of the early days is gone. We don’t have enough regulars, there is no discussion about the site on WordPress Development Meta Stack Exchange, and our chat, once very active, funny, and friendly, is now almost dead.

                    \n\n\n\n

                    “Maybe that’s normal, I don’t know. But it’s still ‘my’ site. Reputation and badges don’t really mean anything for a long time now, but keeping the site working, useful and friendly is more important.”

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 26 Sep 2020 15:27:03 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:82:\"WPTavern: PhotoPress Plugin Seeks to Revolutionize Photography for WordPress Users\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104770\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"https://wptavern.com/photopress-plugin-seeks-to-revolutionize-photography-for-wordpress-users?utm_source=rss&utm_medium=rss&utm_campaign=photopress-plugin-seeks-to-revolutionize-photography-for-wordpress-users\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5638:\"

                    Peter Adams, the owner of the PhotoPress plugin, announced a couple of weeks ago that now is the time for his project to take center stage. “It’s Time for PhotoPress,” read the title of his post in which he laid out a four-phase plan for the future of his project.

                    \n\n\n\n

                    Adams is no stranger to manipulating WordPress to suit the needs of photographers. He described photography as his first love and second career. He initially found the art of taking photos in high school and set off to college to become a professional photographer in the early ’90s.

                    \n\n\n\n

                    As his university graduation loomed, he was recruited to run web development for an internet ad agency that built websites for Netscape, Bill Clinton’s White House, and dozens of Fortune 500 companies. He spent the next 15 years starting or running tech companies before returning to his roots as a photographer.

                    \n\n\n\n

                    Today, he photographs for various magazines and companies. And, that’s where his PhotoPress project comes in.

                    \n\n\n\n

                    “As far as WordPress has come, it is at risk of losing an entire generation of photographers to photo website services such as Photoshelter, SmugMug, Squarespace, and PhotoFolio,” he said. Adams wants to change that, making WordPress the go-to platform for photographers around the world.

                    \n\n\n\n

                    The Jetpack of Photography Plugins

                    \n\n\n\n

                    If you dig into the history of the PhotoPress plugin on WordPress.org, it seems to have a 15-year history. However, this is not the same plugin that was published a decade and a half ago by a different developer. The original plugin is now defunct, and Adams took over when the name was freed up on the directory.

                    \n\n\n\n

                    Adams wrote in his announcement post that WordPress has done a great job of delivering several media features over the years. “Yet despite that, there are still many rough edges and missing features that keep WordPress from being the first choice for a photographer that needs to publish a beautiful portfolio of their work, put their image catalog/archive online, or showcase a photo editorial/project.”

                    \n\n\n\n

                    He outlined a list of 10 specific problem areas that he wants to address in a “Jetpack-like” plugin for photographers. This is the bread and butter of the first of the planned four phases, which he said is about 80% finished. He had originally planned to develop PhotoPress as a series of separate plugins, each addressing a specific problem. Now, it is a single plugin with modules than can be enabled or disabled.

                    \n\n\n\n

                    When asked why the “right time” is now, Adams explained it is because the Gutenberg (block editor) project is a giant leap forward in usability in terms of creating photography blogs.

                    \n\n\n\nPhotoPress Gallery block in the editor.\n\n\n\n

                    “Photogs are a rare breed of non-technical users with high design sense,” he said. “Things that I used to have to teach photographers to do using shortcode syntax and custom CSS can now be simple controls with live feedback inside a Gutenberg block. It’s really a game-changer for getting people comfortable with customizing things like gallery styling — which is the number one thing photographers need to do.”

                    \n\n\n\n

                    The primary piece of the PhotoPress plugin is its custom PhotoPress Gallery block. It allows users to choose between a range of gallery styles, such as columns, masonry, justified, and mosaic. Each style has its own options. Images can also be launched into a slideshow when one is clicked.

                    \n\n\n\n

                    Based on some quick tests, the block’s front-end output will go farther with some themes than others. This is mainly because of conflicting CSS and issues which can be solved by testing against more themes.

                    \n\n\n\n

                    Aside from the block, the plugin can automatically extract image metadata and group that data through custom taxonomies, such as cameras, lenses, locations, keywords, and more. WordPress stores this information out of the box, but it is hidden away as post meta. The plugin uses the taxonomy system to make it manageable for end-users.

                    \n\n\n\n

                    Ultimately, Adams set out to create a photography plugin that fits in with the WordPress admin user interface and experience, which he has accomplished.

                    \n\n\n\n

                    The Future of PhotoPress

                    \n\n\n\n

                    The project is still a work in progress. Adams is still moving through Phase I of the four-phase plan. Once it is complete, he can move on to the next steps in the process.

                    \n\n\n\n

                    Phase II is to create themes that are designed specifically to work with the PhotoPress plugin. He has three planned thus far. One for handling portfolio sites. Another for creating a stock photo archive. And the last for photojournalism and exhibits. Each will be built on top of his photography theme framework.

                    \n\n\n\n

                    The themes in Phase II will likely be commercial products. Adams said he needs a way to fund the next phases of the project. He hopes to have this step underway by the end of the year.

                    \n\n\n\n

                    For 2021, he wants to begin tackling Phases III and IV. The former will be a website-as-a-service (WaaS) similar to WordPress.com but for photographers. It will begin as a paid project but could have some free options for emerging photographers and students. The final phase is to build an onboarding system.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 25 Sep 2020 19:08: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:14:\"Justin Tadlock\";s: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:73:\"WPTavern: Google Officially Releases Its Web Stories for WordPress 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:30:\"https://wptavern.com/?p=105227\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:191:\"https://wptavern.com/google-officially-releases-its-web-stories-for-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=google-officially-releases-its-web-stories-for-wordpress-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:5593:\"Web Stories for WordPress dashboard.\n\n\n\n

                    Two and a half months after the launch of its public beta, Google released its Web Stories for WordPress plugin. So far, the plugin has over 10,000 active installations and has garnered a solid five-star rating from four reviews.

                    \n\n\n\n

                    Google created the Web Stories format through its AMP Project to allow publishers to create visually-rich stories. It is primarily geared toward mobile site visitors, allowing them to quickly jump through story pages with small chunks of content.

                    \n\n\n\n

                    The Web Stories plugin creates a visual interface within WordPress for creating Stories. It breaks away from the traditional WordPress interface and introduces users to an almost Photoshop-like experience for building out individual Stories. The Stories editor is completely drag-and-drop.

                    \n\n\n\n

                    The plugin also offers eight predesigned templates out of the box that cover a small range of niches. However, according to Google’s announcement, the company plans to add more templates in future updates.

                    \n\n\n\n

                    Web Stories Are for Storytelling

                    \n\n\n\n

                    “Firstly…the power of Stories,” wrote Jamie Marsland, founder of Pootlepress, in a Twitter thread. “Stories are how we (humans) see the world and share our experiences. Up to now the platforms that we have to tell stories have been limited to books/films/tv/websites/blogs/instagram stories etc.”

                    \n\n\n\n

                    “Websites are ok for telling stories but in many ways the format doesn’t really fit the linear arc of storytelling. When Marshall McLuhan said ‘the medium is the message’ in 1964 he was talking about how the medium itself has a social impact, and change the communication itself…and the possibilities for what is communicated and how it is perceived. But we should keep coming back to Stories. Stories are the key here imo. Now we have an open format to tell Stories, and we have an open platform (WordPress) where those Stories can be told easily.”

                    \n\n\n\n

                    Marsland finished his thread by saying that using Stories as a replacement for a brochure or website is a missed opportunity. He said that it was a platform for storytelling and should be used as such.

                    \n\n\n\n

                    It is far too early to tell if Web Stories will simply be a fad or still in wide use years from now. The technology certainly lends itself well to telling stories, particularly in mobile format, but I doubt we have seen the best of what is possible on the web. The format feels too limited to be the end-all-be-all of storytelling. It is merely one medium that will live and die by its popularity with users.

                    \n\n\n\n

                    With the right design skills, some people will craft beautiful Web Stories. And, that is just what Marsland has done with the first Story he shared:

                    \n\n\n\nPage from the Wilson and Pootle Web Story by Jamie Marsland.\n\n\n\n

                    I agree with his conclusion. Web Stories should be about storytelling. When you move outside of that zone, the technology feels out of place.

                    \n\n\n\n

                    Where I disagree is that websites are not ideal for storytelling. Ultimately, the WordPress block editor will allow artistic end-users to craft intricate stories, mixing content and design in ways that we have not seen. We are just now scratching the surface. I expect our community of developers to build more intricate tools than what the Web Stories plugin currently allows, and we can do so in a way that revolutionizes storytelling on the web.

                    \n\n\n\n

                    New Features

                    \n\n\n\nStory editor with Unsplash photo integration.\n\n\n\n

                    The Web Stories plugin now adds support for Unsplash images and Coverr videos out of the box. The plugin adds a new tab with a “media” icon. For users of the first beta version of the plugin, this may be a bit confusing. The previous media icon was for a tab that displayed the user’s media. Now, the user’s media is under the tab with the “upload” icon.

                    \n\n\n\n

                    It is also not immediately clear that the Unsplash images and Coverr videos are not hosted on the site itself. There is a “powered by” notice at the bottom of the tab, but it can be easy to miss because it blends in with the media in the background.

                    \n\n\n\n

                    Media from Unsplash and Coverr is hosted off-site and not downloaded to the user’s WordPress media library. I could find no mention of this in the plugin’s documentation. Such hotlinking was a cause for debate over the recent official release of the Unsplash plugin.

                    \n\n\n\n

                    Google also announced it planned to add more “stock media integrations” in the near future. According to a document shared via a GitHub ticket, such future integrations may include Google Photos and GIF-sharing site Tenor.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 24 Sep 2020 21:13:42 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:106:\"WPTavern: W3C Drops WordPress from Consideration for Redesign, Narrows CMS Shortlist to Statamic and Craft\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105108\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:255:\"https://wptavern.com/w3c-drops-wordpress-from-consideration-for-redesign-narrows-cms-shortlist-to-statamic-and-craft?utm_source=rss&utm_medium=rss&utm_campaign=w3c-drops-wordpress-from-consideration-for-redesign-narrows-cms-shortlist-to-statamic-and-craft\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11563:\"

                    The World Wide Web Consortium (W3C), the international standards organization for the web, is redesigning its website and will soon be selecting a new CMS. Although WordPress is already used to manage W3C’s blog and news sections of the website, the organization is open to adopting a new CMS to meet its list of preferences and requirements.

                    \n\n\n\n

                    Studio 24, the digital agency selected for the redesign project, narrowed their consideration to three CMS candidates:

                    \n\n\n\n
                    1. Statamic
                    2. Craft CMS
                    3. WordPress
                    \n\n\n\n

                    Studio 24 was aiming to finalize their recommendations in July but found that none of them complied with the W3C’s authoring tool accessibility guidelines. The CMS’s that were better at compliance with the guidelines were not as well suited to the other project requirements.

                    \n\n\n\n

                    In the most recent project update posted to the site, Studio 24 reported they have shortlisted two CMS platforms. Coralie Mercier, Head of Marketing and Communications at W3C, confirmed that these include Statamic and Craft CMS.

                    \n\n\n\n

                    WordPress was not submitted to the same review process as the Studio 24 team claims to have extensive experience working with it. In the summary of their concerns, Studio 24 cited Gutenberg, accessibility issues, and the fact that the Classic Editor plugin will stop being officially maintained on December 31st, 2021:

                    \n\n\n\n

                    First of all, we have concerns about the longevity of WordPress as we use it. WordPress released a new version of their editor in 2018: Gutenberg. We have already rejected the use of Gutenberg in the context of this project due to accessibility issues.

                    If we choose to do away with Gutenberg now, we cannot go back to it at a later date. This would amount to starting from scratch with the whole CMS setup and theming.

                    Gutenberg is the future of WordPress. The WordPress core development team keeps pushing it forward and wants to roll it out to all areas of the content management system (navigation, sidebar, options etc.) as opposed to limiting its use to the main content editor as is currently the case.

                    This means that if we want to use WordPress long term, we will need to circumvent Gutenberg and keep circumventing it for a long time and in more areas of the CMS as time goes by. 

                    \n\n\n\n

                    Another major factor in the decision to remove WordPress from consideration was that they found “no elegant solution to content localization and translation.”

                    \n\n\n\n

                    Studio 24 also expressed concerns that tools like ACF, Fewbricks, and other plugins might not being maintained for the Classic Editor experience “in the context of a widespread adoption of Gutenberg by users and developers.”

                    \n\n\n\n

                    “More generally, we think this push to expand Gutenberg is an indication of WordPress focusing on the requirements of their non-technical user base as opposed to their audience of web developers building custom solutions for their clients.”

                    \n\n\n\n

                    It seems that the digital agency W3C selected for the project is less optimistic about the future of Gutenberg and may not have reviewed recent improvements to the overall editing experience since 2018, including those related to accessibility.

                    \n\n\n\n

                    Accessibility consultant and WordPress contributor Joe Dolson recently gave an update on Gutenberg accessibility audit at WPCampus 2020 Online. He reported that while there are still challenges remaining, many issues raised in the audit have been addressed across the whole interface and 2/3 of them have been solved. “Overall accessibility of Gutenberg is vastly improved today over what it was at release,” Dolson said.

                    \n\n\n\n

                    Unfortunately, Studio 24 didn’t put WordPress through the same content creation and accessibility tests that it used for Statamic and Craft CMS. This may be because they had already planned to use a Classic Editor implementation and didn’t see the necessity of putting Gutenberg through the paces.

                    \n\n\n\n

                    These tests involved creating pages with “flexible components” which they referred to as “blocks of layout,” for things like titles, WYSIWYG text input, and videos. It also involved creating a template for news items where all the content input by the user would be displayed (without formatting).

                    \n\n\n\n

                    Gutenberg would lend itself well to these uses cases but was not formally tested with the other candidates, due to the team citing their “extensive experience” with WordPress. I would like to see the W3C team revisit Gutenberg for a fair shake against the proprietary CMS’s.

                    \n\n\n\n

                    W3C Is Prioritizing Accessibility Over Its Open Source Licensing Preferences

                    \n\n\n\n

                    The document outlining the CMS requirements for the project states that “W3C has a strong preference for an open-source license for the CMS platform” as well as “a CMS that is long-lived and easy to maintain.” This preference may be due to the economic benefits of using a stable, widely adopted CMS, or it may be inspired by the undeniable symbiosis between open source and open standards.

                    \n\n\n\n

                    “The industry has learned by experience that the only software-related standards to fully achieve [their] goals are those which not only permit but encourage open source implementations. Open source implementations are a quality and honesty check for any open standard that might be implemented in software…”

                    Open Source Initiative
                    \n\n\n\n

                    WordPress is the only one of the three original candidates to be distributed under an OSD-compliant license. (CMS code available on GitHub isn’t the same.)

                    \n\n\n\n

                    Using proprietary software to publish the open standards that underpin the web isn’t a good look. While proprietary software makers are certainly capable of implementing open standards, regardless of licensing, there are a myriad of benefits for open standards in the context of open source usage:

                    \n\n\n\n

                    “The community of participants working with OSS may promote open debate resulting in an increased recognition of the benefits of various solutions and such debate may accelerate the adoption of solutions that are popular among the OSS participants. These characteristics of OSS support evolution of robust solutions are often a significant boost to the market adoption of open standards, in addition to the customer-driven incentives for interoperability and open standards.”

                    International Journal of Software Engineering & Applications
                    \n\n\n\n

                    Although both Craft CMS and Statamic have their code bases available on GitHub, they share similarly restrictive licensing models. The Craft CMS contributing document states:

                    \n\n\n\n

                    Craft isn’t FOSS
                    Let’s get one thing out of the way: Craft CMS is proprietary software. Everything in this repo, including community-contributed code, is the property of Pixel & Tonic.

                    That comes with some limitations on what you can do with the code:

                    – You can’t change anything related to licensing, purchasing, edition/feature-targeting, or anything else that could mess with our alcohol budget.
                    – You can’t publicly maintain a long-term fork of Craft. There is only One True Craft.

                    \n\n\n\n

                    Statamic’s contributing docs have similar restrictions:

                    \n\n\n\n

                    Statamic is not Free Open Source Software. It is proprietary. Everything in this and our other repos on Github — including community-contributed code — is the property of Wilderborn. For that reason there are a few limitations on how you can use the code:

                    \n\n\n\n

                    Projects with this kind of restrictive licensing often fail to attract much contribution or adoption, because the freedoms are not clear.

                    \n\n\n\n

                    In a GitHub issue requesting Craft CMS go open source, Craft founder and CEO Brandon Kelly said, “Craft isn’t closed source – all the source code is right here on GitHub,” and claims the license is relatively unrestrictive as far as proprietary software goes, that contributing functions in a similar way to FOSS projects. This rationale is not convincing enough for some developers commenting on the thread.

                    \n\n\n\n

                    “I am a little hesitant to recommend Craft with a custom open source license,” Frank Anderson said. “Even if this was a MIT+ license that added the license and payment, much like React used to have. I am hesitant because the standard open source licenses have been tested.”

                    \n\n\n\n

                    When asked about the licensing concerns of Studio 24 narrowing its candidates to two proprietary software options, Coralie Mercier told me, “we are prioritizing accessibility.” A recent project update also reports that both CMS suppliers W3C is reviewing “have engaged positively with authoring tool accessibility needs and have made progress in this area.”

                    \n\n\n\n

                    Even if you have cooperative teams at proprietary CMS’s that are working on accessibility improvements as the result of this high profile client, it cannot compare to the massive community of contributors that OSD-compliant licensing enables.

                    \n\n\n\n

                    It’s unfortunate that the state of open source CMS accessibility has forced the organization to narrow its selections to proprietary software options for its first redesign in more than a decade.

                    \n\n\n\n

                    Open standards go hand in hand with open source. There is a mutually beneficial connection between the two that has caused the web to flourish. I don’t see using a proprietary CMS as an extension of W3C values, and it’s not clear how much more benefit to accessibility the proprietary options offer in comparison. W3C may be neutral on licensing debates, but in the spirit of openness, I think the organization should adopt an open source CMS, even if it is not 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:\"Thu, 24 Sep 2020 20:13:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:79:\"WPTavern: First Look at Twenty Twenty-One, WordPress’s Upcoming Default Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105166\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:195:\"https://wptavern.com/first-look-at-twenty-twenty-one-wordpresss-upcoming-default-theme?utm_source=rss&utm_medium=rss&utm_campaign=first-look-at-twenty-twenty-one-wordpresss-upcoming-default-theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6907:\"

                    Fashion is ephemeral. Art is eternal. Indeed what is a fashion really? A fashion is merely a form of ugliness so absolutely unbearable that we have to alter it every six months!

                    \n\n\n\n

                    Thus wrote Oscar Wilde on Victorian-era fashion in an article titled “The Philosophy of Dress” for the New-York Tribune in 1885.

                    \n\n\n\n

                    In many ways, WordPress theming is the same as the ever-changing landscape of fashion. Rounded corners are in one day and out the next. Box shadows are in one year after being frowned up just months earlier. Perhaps web design is so intolerable that we must change it every six months. Or, at least freshen it up every year in the case of WordPress.

                    \n\n\n\n

                    If art is eternal, there are only two default, Twenty* themes that I can truly recall from past years: Twenty Ten and Twenty Fourteen — yes, Twenty Twenty is memorable, but it is also still the current default. Twenty Ten was a classic that paid homage to WordPress’s past. Twenty Fourteen was such a leap away from tradition that it is hard to forget. Everything else has seemed to fade to varying degrees.

                    \n\n\n\n

                    With WordPress 5.6 and the end of the year looming, it is time to look forward to the latest trend. As Mel Choyce-Dwan noted in the announcement of Twenty Twenty-One, the next default theme, “Pastels and muted colors are pretty in right now.”

                    \n\n\n\n

                    She is not wrong. The colors are a refreshing change of pace. Now that we are into the second day of autumn, I am getting the good kind of vibes from some of the more earthy-tones from a couple of the color palettes expected to ship with the theme.

                    \n\n\n\nPotential color palette options for Twenty Twenty-One.\n\n\n\n

                    Whether Twenty Twenty-One will be a fashionable theme for the year or art that we can remember a decade from now, only history will be able to judge. For now, let’s enjoy the creation and take a look at what we should expect from the next default WordPress theme.

                    \n\n\n\n

                    The Current Twenty Twenty-One

                    \n\n\n\n

                    The new default theme is a fork of Automattic’s Seedlet, a project in which I lauded as the next step in the evolution of theming. It is a theme that is focused on WordPress’s future of being completely comprised of blocks. It gives us an ideal insight into where theme development is heading. It makes sense as the foundation for the new default. Few other themes would make for a good starting point right now. With WordPress theme development in flux, Seedlet is simply ahead of the pack in terms of foundational elements.

                    \n\n\n\nSeedlet WordPress theme screenshot.\n\n\n\n

                    “This provides us with a thorough system of nested CSS variables to make child theming easier, and to help integrate with the global styles functionality that’s under development for full-site editing,” wrote Choyce-Dwan of using Seedlet as a starting point.

                    \n\n\n\n

                    There are no plans to spin up a Google Web Font for this theme. The design team is going native and sticking with the default system font stack. Choyce-Dwan listed several reasons for the choice, such as keeping a neutral font that allows broad use, speed, and customizability via a child theme.

                    \n\n\n\n

                    Despite the neutral font, the default pastel green is a fairly opinionated design decision. It will not be used broadly across industries. However, the team plans to create multiple color palettes that will give it more range. Presumably, these palettes can also be overwritten.

                    \n\n\n\nPastel green color scheme on single post view.\n\n\n\n

                    Other than the colors, the design is relatively simple. Choyce-Dwan said that the theme’s block patterns support is where it will be truly unique.

                    \n\n\n\n

                    I was initially unhappy with the patterns that were going to ship with WordPress 5.5. However, an 11th-hour update improved the situation so that they did not feel entirely experimental. The foundational Seedlet theme for Twenty Twenty-One has some unique patterns that begin to scratch the surface of what’s possible with this WordPress feature. My hope is that the new default theme steps it up a notch.

                    \n\n\n\n

                    Currently, the theme does not register any custom patterns. However, it has a placeholder file and a note that they are a work in progress. Choyce-Dwan shared some patterns the team has already designed in the announcement.

                    \n\n\n\nCurrently-designed block patterns.\n\n\n\n

                    “We’ll be relying on our talented community designers for more ideas,” she wrote. The team has also created a GitHub template for anyone to contribute pattern design ideas.

                    \n\n\n\n

                    Currently, the theme does not support the upcoming full-site editing feature of WordPress. After the Beta 1 release of WordPress 5.6, the team plans to begin exploring the addition of this support. WordPress is expected to ship a public beta of full-site editing in its next major release, but it is unclear whether it will be far enough along to be a headline feature for the Twenty Twenty-One theme.

                    \n\n\n\n

                    The team and volunteers have less than a month before the October 20th deadline for committing the new theme to trunk, the core WordPress development branch. At that stage, the theme should be nearly complete and ready for production. Of course, there will be several rounds of patches, bug fixes, and updates before WordPress 5.6 lands in December. Right now is the best time for anyone who wants to get involved with Twenty Twenty-One to do so.

                    \n\n\n\n

                    Useful links with more information:

                    \n\n\n\n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 23 Sep 2020 20:01: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:14:\"Justin Tadlock\";s: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:37:\"HeroPress: Hello World – Hevo Nyika\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=3308\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:176:\"https://heropress.com/essays/hello-world-discovering-the-world-through-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=hello-world-discovering-the-world-through-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:14438:\"\"Pull

                    Unokwanisa kuverenga rondedzero iyi muChiShona

                    \n

                    So I chose a career in Web Development!!

                    \n

                    To be honest it’s kind of funny when I think about it and quite surreal to be here talking about my story. It has been a journey and I would like to share my story with you.

                    \n

                    I have been lucky in the Dad department. My Dad encouraged me to work hard and dream big from a very young age. I remember occasionally having ‘when I grow up’ talks.

                    \n

                    For quite some time I wanted to be a Judge, however awesome this dream sounds it was not very inspired. After binge-watching Judge Judy for a whole weekend, I started calling myself Judge Thelma. Though I don’t remember much of this my sister says that I used to say I would arrest all the men in the World if I ever became a Judge. HAHAHA! (clearly I didn’t understand how the World works)

                    \n

                    I did not understand what being a Judge meant or what was required for me to start banging that gavel to my heart’s desire. Eventually, I learnt that I had to become a lawyer first then magistrate before I could be nominated to be a Judge and let us just say that is how I sentenced that dream to a lifetime down the drain.

                    \n

                    See what I did there? hahaha!

                    \nWith Daddy Dearest\n

                    A few years later, I was in High School and that is when I decided to pursue a career in Computer Science. I did not know what I would be doing or how I would get there but I just knew that I was going to pursue a career in ICT. I wrote my first line of code when I was 16 years old.

                    \n

                    This was after I had joined the school’s computer class, initially, I thought I would be learning about Excel Sheets and Word Documents until I was assigned to write my first program in C (talk about a double-take!!). It was not easy but it was very exciting, l remember writing up simple code for a Video Club – a simple check-in/out for VHS tapes and CDs. Dear World, thus began my fascination with computers.

                    \n

                    Seven years later, I was now in university studying ICT as I had always wanted. I was doing a Bachelors in Business Management & Information Technology. In my third year, I was interning at a local Webdesign and hosting company. This was never my plan, I only took on that job after I had failed to get a job with local banks or telecommunications companies. Before I was introduced to Website Design I envisioned myself suiting up and working in IT Audit or offering IT support. Even though things did not go as I had planned, I am glad they did not exactly go my way in that aspect. So in 2017, I was designing websites using HTML, CSS, PHP, JavaScripts and Joomla which was the prefered content management system at that company. I knew about WordPress but I was not using it for anything. People have this misconception that WordPress is not for real developers and it is not secure and at that time I was one of those people.

                    \n

                    Finding my tribe

                    \n

                    One day when I was working at the front desk Thabo Tswana came to give a colleague of mine a purple WooCommerce pen. I did not know what WooCommerce was at that time but I was taken by the purple shirt and pen he was carrying. I asked him about it and he explained what WooCommerce was and that what he was carrying was called ‘swag’. So the love of freebies led me to the WordCamp Harare website, instead of buying a ticket I applied to volunteer. I learnt more about WordPress, I was a volunteer, without any knowledge on WordPress.org or WordPress.com. I only started using WordPress because of the awesome people that l had met at that Wordcamp.

                    \n

                    Everyone was so welcoming, a week later with help from Thabo I designed my first ever WP website.

                    \n

                    Soon after I was part of the community and a bit more involved in the meetups. We had our first-ever Women Who WordPress meetup in 2018. So many ladies came on board bloggers and developers alike. We were free to talk and discuss a lot of things. We had more time to discuss the difference between WordPress.com and WordPress.org we shared views on how to handle discrimination at work, how to promote your website and a whole lot of other things.

                    \n

                    \n

                    Establishing roots

                    \n

                    In 2018, Harare had its first-ever female Lead Organiser Tapiwanashe Manhobo whoop whoop! I was also part of the organising team that year, I was assigned to handle Harare’s first Kids Camp. The planning process was stressful because the economic crisis in Zimbabwe was getting worse, luckily we had over 8 months to plan and with help from sponsors, we managed to pull through. In the end, everything turned out great. I wrote an article about the Kids Camp here.

                    \n

                    After the first Kids Camp, we had several WordPressors that were enthusiasts about encouraging kids to embrace ICT. In 2019 we had not planned to have a Kids Camp because of financial constraints but to our surprise, we had some anonymous donations and we managed to have a WordPress Community outreach to a youth centre a week after our WordCamp. We had the outreach at the Centre for Total Transformation which is a non-formal school that caters for underprivileged and vulnerable children. We taught them about WordPress, Computer Hardware and Software.

                    \n

                    Here is a small video I took with Ellen when we were about to leave. Did l mention that I am terrible on camera? hahaha!

                    \n
                    https://thelmachido.me/vid.mp4
                    \n

                    Kids Camp 2019 – Centre for Total Transformation

                    \n

                    I have fallen deeply for WordPress because of the Community, I enjoy attending WordCamps, meeting new people and just learning new stuff. I have a huge list of WordCamps I need to attend before l kick the bucket, hopefully. Last year I managed to cross WordCamp

                    \n

                    Johannesburg off my bucket list. This year I was going to attend WordCamp Capetown but unfortunately, 2020 had other plans for the whole world. Anyway when everything is back to normal my plan to travel to WordCamps will proceed. (fingers crossed)

                    \n

                    Reaping Fruits

                    \n

                    Meanwhile, my plan to improve my developing skills has not been on hold. Even though I can still cook up code in C and Java, for now, I have also included WordPress PHP functions to the mix. It was not easy to get to this point, daring myself got me to this slightly better stage. My IQ is not way up there, however, I try to do my best where I can and I am happy to say it has paid off so far.

                    \n

                    Around November last year, I was designing as a freelancer while job hunting. Out of the blue l got a call for a job offer from Trust Nhokovenzo who is big on Digital marketing and also part of the WordPress Community. He had asked someone in the community about developers and my name happened to come up. So since February, I have been part of his team at Calmlock Digital Marketing Agency.

                    \n

                    There is so much more in the world of WordPress that l am yet to tap into so even though I am ending my write up here, for now, my story is going to continue …

                    \n

                    Until next time…

                    \n

                    Hevo Nyika

                    \n

                    Saka ini ndakasarudza kugadzira mawebhusayiti.

                    \n

                    Ndakaita rombo rakanaka pana baba vandakapihwa naMwari. Baba vangu vaindikurudzira kuti ndishande nesimba. Ndinoyeuka pano neapo tichiita hurukuro dzedu dzekuti ‘kana ndakura ndoda kuveyi’.

                    \n

                    Kwenguva yakati rebei ndaida kuve Mutongi. Kunyangwe ini ndisingazvirangariri mukoma wangu anotaura kuti ndaiti ndaizosunga varume vese vari pasi rino kana ndikangoita mutongi HAHAHA zveshuwa handaiziva kuti mitemo yenyika inofambiswa seyi.
                    \nNdanga ndisinga nzwisisi kuti kuva mutongi kwairevei kana zvaidikanwa kwandiri kuti nditange kurova iro ghavheu kuchishuwo chemoyo wangu. Pakupedzisira, ndakadzidza kuti ndaifanirwa kuzoita gweta ipapo magistrate ndisati ndasarudzwa kuita Mutongi naizvozvo ndokupera kwakaita chiroto chekuva Mutongi.

                    \nNa Baba Vangu\n

                    Gare gare papfura makore mashoma pandakanga ndave kuHigh School ndakanga ndakuda kuita basa rema kombiyuta. Ndakanyora mutsara wekutanga wekodhi pandaive nemakore gumi nematanhatu. Izvi zvakaitika mushure mekunge ndapinda mukirasi yemakombiyuta, pakutanga ndaifunga kuti ndinenge ndichidzidza nezveExcel Sheets neWord zvisineyi ndakaona ndakunyora kodhi yangu yekutanga muC. Zvaisave nyore kunyora kodhi asi zvainakidza kwazvo, ndorangarira ndichinyora kodhi yeVhidhiyo Kirabhu.

                    \n

                    Makore manomwe apfura, ndakanga ndava kuyunivhesiti ndichidzidza ICT zvandakagara ndakaronga. Ndaiita Bachelors muBusiness Management & Information Technology. Mugore rangu rechitatu ndainge ndave kushanda kune imwe kambani yaita zvekugadzira mawebhusaiti. Ndakawana basa iri mushure mekunge ndatadza kuwana basa kumabhanga. Kunyangwe hazvo zvinhu zvisina kuenda sezvandaive ndakaronga, ndinofara kuti hazvina kunyatso enda nenzira yangu. Saka muna 2017 ndaigadzira mawebhusaiti ndichishandisa HTML, CSS, PHP, JavaScript uye Joomla iyo yaive iyo inokurudzirwa kukambani kwandaive. Panguva iyi ndaiziva nezve WordPress asi ndakanga ndisingaishandisi.

                    \n

                    Kuwanana neWordPress

                    \n

                    Rimwe zuva pandakanga ndichishanda ndakaona Thabo Tswana akauya kuzopa mumwe mukomana wandayishanda naye chinyoreso cheWooCommerce. Ndakanga ndisingazive kuti WooCommerce yaive chii asi ndakafarira chinyoreso nehembe ye WooCommerce yaanga akapfeka. Ndakamubvunza nezvazvo akatsanangura kuti WooCommerce yaive chii. Saka nekudawo zvakanaka, zvemahara ndakaenda pawebhusaiti yeWordCamp Harare ndikabata zvimbo zvegore iroro. Ndakazvipira kubatsirawo vamwe vekuWordPress kuWordCamp Harare. Nerubatsiro kubva kunaThabo ndakagadzira webhusaiti yangu yekutanga yeWordPress vhiki rakatevera .

                    \n

                    Mushure mekunge ndaitawo chipato cheavo vanoshandisa WordPress ndakanga ndakuenda kumisangano yeWordPress yaitwa muHarare. Takaita musangano wevakadzi chete muna 2018. Vakadzi vazhinji vakauya kumusangano uyu. Tainga takasununguka kukurukura zvinhu zvakawanda. Takakurukura pamusoro pemutsauko uripo pakati peWordPress.com neWordPress.org takagovana maonero ekugadzirisa rusarura kubasa nezvimwewo.

                    \n

                    \n

                    Nguva yandakatanga kushandisa WordPress

                    \n

                    Muna 2018, kurongwa kweWordCamp Harare kwakatungamirwa kekutanga nemusikana ainzi Tapiwanashe Manhobo (waiva mufaro mukuru). Ndakanga ndiri mumwe wevairongawo naye. Hurongwa hwekuronga WordCamp Harare mugore iri hwainetsa pamusaka pekuoma kwehupfumi wemuZimbabwe, zvisineyi takaita rombo rakanaka nokuti takawana rubatsiro kubva kunevamwewo vanhu vakatiwedzera mari. Pakupedzisira, zvese zvakabudirira zvakanaka. Takarongawo WordCamp yevana varipasi pemakore gumi nechishanu, munokwanisa kuverenga pamusoro pezuva iri pawebhisaiti yangu apa.

                    \n

                    Mushure mekuita WordCamp yevana, takave nevamwe vanhu veWordPress aifarira kukurudzira vana kuti vagamuchire ICT. Muna 2019 takanga tisina kuronga kuve neWordCamo yeVana nekuda kwezvimhingamupinyi zvemari asi chakatishamisa ndechekuti takawana mari kubvawo kune vamwe. Takaita Camp iyi paCentre for Total Transformation chinova chikoro chisiri chepamutemo chinodzidzisa vana vanotambura. Tadzidzisa vana ava pamusoro peWordPress, Computer Hardware uye Software.

                    \n
                    https://thelmachido.me/vid.mp4
                    \n

                    Ndofarira WordPress zvakanyanya nekuda kweavo varimu nharaunda yacho, ini ndinonakidzwa nekuenda kumaWordCampi, kusangana nevanhu vatsva uye kungo dzidza zvinhu zvitsva. Gore rakapera ndakakwanisa kuyambuka muganhu weZimbabwe ndichienda kuWordCamp Johannesburg, dai pasina kuti 2020 nyika dzepasi rino dzakawirwa nedenda reCOVID 19 zvimwe ndingadayi ndakaenda kuWordCamp Capetown. Zvisinei hazvo kana denda ranani zvimwe ndichakwanisa kufamba ndichienda kumaWordCamp edzimwe nyika.

                    \n

                    Kukowa zvandakadyara

                    \n

                    Zvichakadaro, chirongwa changu chekuvandudza hunyanzvi hwangu hachina kumira. Kunyangwe ini ndichiri kukwanisa kubika kodhi muC uye Java, ikozvino, ndasanganisirawo WordPress PHP. Zvaive zvisiri nyore kusvika apa, zvakatora kuzvishingisa nekushanda nesimba. Ndinofara mwari aiva neni pamufambo wangu uyu.

                    \n

                    Muna Mbudzi gore rakapera, ndaive ndichigadzira mawebhusayiti apo nditsvaga basa. Pasina nguva ndakataura naTrust Nhokovenzo uyo akaandipa basa mukambani yake, kambani iyi inonzi Calmlock Digital Marketing Agency.

                    \n

                    Pane zvimwe zvakawanda kuWordPress zvandisati ndapinda mazviri. Nhaizvozvo kunyangwe ndiri kupedzisa kunyora kwangu apa, nyaya yehupenyu wangu ichaenderera mberi…

                    \n

                    Kusvikira nguva inotevera …

                    \n

                    …. tsvaga chinangwa chako, chiite mushe mushe ..

                    \n

                    The post Hello World – Hevo Nyika 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, 23 Sep 2020 06:00: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:\"Thelma Mutete\";s: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:102:\"WPTavern: WordPress Contributors Debate Dashboard Notice for Upcoming Facebook oEmbed Provider Removal\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105132\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:249:\"https://wptavern.com/wordpress-contributors-debate-dashboard-notice-for-upcoming-facebook-oembed-provider-removal?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-contributors-debate-dashboard-notice-for-upcoming-facebook-oembed-provider-removal\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5885:\"

                    WordPress contributors are discussing different strategies for responding to Facebook and Instagram dropping unauthenticated oEmbed support on October 24. WordPress will be removing both Facebook and Instagram as oEmbed providers. When a user attempts to embed content by pasting a URL as they have in the past, they may not understand why it no longer works. They may assume that WordPress broke embeds, causing an increase in the support burden for this change.

                    \n\n\n\n

                    A few participants on the trac ticket for this issue have suggested WordPress detect users who will be impacted and attempt to warn them with a notice.

                    \n\n\n\n

                    “Since this may impact users unknowingly, it is possible to push a dashboard notice to users who have Facebook/Instagram embeds in their content, showing for site admins, as a one-off that can be dismissed,” Marius Jensen said.

                    \n\n\n\n

                    “We’ve previously done post-update-processing to clean up comments, so the idea of looking over content for an embed isn’t completely outlandish, and would help with those who don’t follow WordPress’ usual channels to learn of this.”

                    \n\n\n\n

                    Others don’t see the necessity. “Why should we make exception here?” Milan Dinić said. “It’s not the first time oEmbed support was discontinued for a provider, and I don’t remember anything specific was done then.”

                    \n\n\n\n

                    There is still some uncertainty about what will happen with existing oEmbeds after Facebook updates its API. During a recent core developer meeting, Helen Helen Hou-Sandí confirmed that WordPress does not clear oEmbed caches regularly. “Technically oEmbed caches are cleared if you save and a valid response is returned, we do not do cron-based garbage collection,” Hou-Sandí said.

                    \n\n\n\n

                    In a post today on the core development blog, Jake Spurlock assured users and developers that the existing embeds added before Facebook’s API change should still work:

                    \n\n\n\n

                    Because oEmbed responses are cached in the database using the hidden oembed_cache post type, any embed added prior to the October 24th deadline will be preserved past the deprecation date. These posts are not purged by default in WordPress Core, so the contents of the embed will persist unless manually deleted.

                    \n\n\n\n

                    Marius Jensen cautioned that there is still the possibility that existing embeds may not work going, depending on what Facebook does.

                    \n\n\n\n

                    “We don’t know how they plan on implementing the use of unauthorized embed attempts,” Jensen said. “It could not return an embed code and your link would remain a plain link, or maybe they decide to return some kind of embedded ‘unauthorized’ content. I don’t think anyone has heard any specifics on how Facebook plans on doing this, so we’re all just kinda waiting to either hear more, or see what happens.”

                    \n\n\n\n

                    Jensen said WordPress doesn’t re-check the cached results except when something changes with the post, but there may be plugins that clean up temporary data that may create an unpredictable outcome.

                    \n\n\n\n

                    “The reliability of the caches are hard to determine (and being caches, it’s sort of in the term that it’s not guaranteed to always be there, but rather fetched and saved for a while when needed),” Jensen said.

                    \n\n\n\n

                    Ideally WordPress’ oEmbed caches will prevent millions of embeds from breaking, but it’s still unknown how Facebook and third party plugins could change things.

                    \n\n\n\n

                    Coming off a rocky 5.5 core update that deprecated jQuery Migrate and flooded official support forums with reports of broken sites, some contributors are wary of having another situation where users are left in the dark.

                    \n\n\n\n

                    “I think a dashboard notice is desirable,” Jon Brown said. “Otherwise we’re not preemptively warning people in a way they can prepare and transition to another solution. We’re letting them know the same instant it’s going to break (when editing a specific post). I don’t think we can safely assume cached data is going to persist forever either, plenty of routines out there purge transient data before its stated expiration date.

                    \n\n\n\n

                    “I see this as potentially being similar to the problems seen in dropping JQM. It’ll cause avoidable and silent breakage client side without even any error logging for a site developer to pick up on. In hindsight, what ideally would have happened with JQM would have been incorporating the detection code from Enable jQuery Migrate Helper into core temporarily, or simply installing that plugin automatically on behalf of users.”

                    \n\n\n\n

                    Brown suggested WordPress detect calls to the cached embeds and warn users before the calls have the chance to fail so they can consider enabling a plugin to keep their embeds working more reliably.

                    \n\n\n\n

                    The discussion remains open in the make.wordpress.org/core post and the corresponding trac ticket. Spurlock said WordPress will likely remove Facebook and Instagram oEmbed providers in the upcoming 5.6 release (scheduled for December 8) but it could also be shipped in a 5.x minor release that happens after October 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 23 Sep 2020 04:28:56 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:65:\"WPTavern: Gutenberg Hub Launches Landing Page Templates Directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105009\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:175:\"https://wptavern.com/gutenberg-hub-launches-landing-page-templates-directory?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-hub-launches-landing-page-templates-directory\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7657:\"\n\n\n\n

                    Munir Kamal has created copy-and-paste blocks. He has built sections or “patterns” from those blocks. He has created a plugin that allows users to completely customize the two features via block options. Yesterday, he released an initial offering of 22 landing page templates that build upon his earlier work.

                    \n\n\n\n

                    Gutenberg Hub can almost be called his magnum opus, at least at this stage of his career. It is a continually growing library of free tools for WordPress’s block editor.

                    \n\n\n\n

                    Like previous projects, Gutenberg Hub’s landing templates require the EditorPlus plugin. This plugin is essentially a suite of design controls for the core WordPress blocks. The templates make use of these options by default. Given the limitations of the block editor’s current design controls, the use of such a plugin is necessary. Otherwise, there would be few other ways to realistically create a template system like this.

                    \n\n\n\n

                    Currently, users must copy the block code — via a convenient “copy” button — from the Gutenberg Hub website and then paste it in the editor. It is not an ideal situation, and I have been asking Kamal whether he would consider building a template inserter for months now.

                    \n\n\n\n

                    This time around, he preemptively said, “And, by the way, I am already working on adding a Template Inserter in my EditorPlus plugin. That will allow users to browse and insert these templates directly from Gutenberg without leaving the website.”

                    \n\n\n\n

                    He knew the question was coming. No need for me to ask again. He was unable to share a current screenshot of what the inserter looks like, but he is asking for feedback on what people expect of the user experience and interface.

                    \n\n\n\n

                    “Earlier, I created a template inserter similar to other blocks plugins, but later I changed my mind and thought that I should integrate with the Gutenberg Patterns API and load the templates into the ‘patterns’ panel in the block inserter,” he said. “But, I am having a few issues and thinking about going back to the original idea to have a Templates button on the top toolbar that opens a popup window to browse and filter templates that users can insert on a click.”

                    \n\n\n\n

                    For now, it is still early. However, at least it is on the long-term roadmap and being worked on.

                    \n\n\n\n

                    The Landing Page Templates

                    \n\n\n\nTesting the photography template (with minor adjustments).\n\n\n\n

                    At the moment, Gutenberg Hub offers 22 landing page templates. The “page” terminology may not mean “full page.” It simply depends on the active theme. Some themes have an open-canvas type of template that allows users to create the entire page via the editor. However, that is not a common feature, so these page templates will be confined to the post content area in most cases.

                    \n\n\n\n

                    The templates also work better with themes that have at least a full-width or no-sidebar option. End-users will want a lot of breathing room to use the templates and tinker with their designs.

                    \n\n\n\n

                    Kamal has built templates that stretch across a variety of industries. From restaurants to gyms to education to fashion, there is a lot to choose from right now. He promises more are on the way and at least a 23rd template in the next few days.

                    \n\n\n\n

                    “For the niches, I did some research from the top WordPress and HTML marketplaces and found the following most common or popular niches,” he said. “I think I will stick with these niches unless I get some more recommendations.”

                    \n\n\n\n

                    In comparison, Redux Templates offers access to over 1,000 sections and templates. Of course, there are trade-offs, such as some of those being commercial and the plugin typically requiring other third-party plugins. While quantity is not the only thing to look at, it proves there are miles of landscape that Gutenberg Hub’s templates have not yet explored. But, it is merely the beginning.

                    \n\n\n\n

                    Gutenberg Hub’s full-page templates are not quite as plug-and-play as its blocks and section templates. This is not so much a fault from the developer’s end. It is an issue of the platform, which is constantly being updated, and the range of support from current themes. End-users will start seeing some of the current limitations of the system when a layout does not quite look right with one theme but does with another. Or, if their theme has not been updated to support a new feature, such as the Social Links block, the typical horizontal menu design will likely be a normal vertical list of links instead.

                    \n\n\n\n

                    These are not insurmountable issues. Gutenberg and themes need more time to mature before projects like Gutenberg Hub’s landing templates are perfect or at least as close to perfect as can be expected.

                    \n\n\n\n

                    There are some things that Gutenberg Hub could improve with its templates. With several that I tested, I needed to switch specific blocks to be full width. This should be set up as the default with templates that are clearly meant to be full width in the example screenshots available on the site. It is a minor issue, but correcting this in the editor fixed several layout issues I was having when using the templates.

                    \n\n\n\n

                    Monetization Plans

                    \n\n\n\n

                    The second question that Kamal has not been prepared to answer fully over the past several months is how he will monetize Gutenberg Hub. Eventually, developers need some return on their investment when building tons of free tools. Many would do it all for free as long as their bills somehow got paid, but the reality is that there will come a tipping point where their projects need funding for long-haul maintenance.

                    \n\n\n\n

                    Kamal said he has laid the groundwork for funding but has not finalized anything yet. Currently, he is working on three ideas:

                    \n\n\n\n
                    • Creating a pro version of his EditorPlus plugin.
                    • Offering premium templates and blocks but is looking for a talented designer to work with.
                    • Using ads specific to Gutenberg users, but he is not a fan of going this route or ads in general.
                    \n\n\n\n

                    He is open to feedback on how to best monetize the website and its projects. However, he said he is unwilling to compromise on giving away current and future free templates and tools.

                    \n\n\n\n

                    Future Gutenberg Projects

                    \n\n\n\n

                    Kamal said he does not have any new Gutenberg-related projects in the pipeline. The current plan is to work on what he has already created, which is a large ecosystem of Gutenberg tools that somehow work together.

                    \n\n\n\n

                    Outside of blocks, templates, and plugins, he is beginning to write more free tutorials on the Gutenberg Hub blog and focusing on creating videos around the project, including a new tutorial series for beginners.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 22 Sep 2020 21:05: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:14:\"Justin Tadlock\";s: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:97:\"WPTavern: WordPress Mobile Engineers Propose Dual Licensing Gutenberg under GPL v2.0 and MPL v2.0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105025\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:239:\"https://wptavern.com/wordpress-mobile-engineers-propose-dual-licensing-gutenberg-under-gpl-v2-0-and-mpl-v2-0?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-mobile-engineers-propose-dual-licensing-gutenberg-under-gpl-v2-0-and-mpl-v2-0\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6556:\"

                    During a Q&A session at WordCamp Europe 2020 online, Matt Mullenweg mentioned that Gutenberg contributors were considering dual licensing for embedding Gutenberg in mobile apps, along with the requirement that they would need to get an agreement from all contributors. WordPress mobile engineer Maxime Biais has just published a proposal for discussion, recommending dual licensing the editor under GPL v2.0 and MPL v2.0.

                    \n\n\n\n

                    “The GPL v2.0 license is a blocker for distributing the Gutenberg library in proprietary mobile apps,” Biais said in the corresponding GitHub issue. “Currently the only known users of Gutenberg on mobile are the WordPress mobile apps which are under GPL v2.0 (WordPress for Android, WordPress for iOS). Mobile apps under the GPL v2.0 are not common and this limits Gutenberg usage in many apps.

                    \n\n\n\n

                    “Rich text editor libraries in the mobile space are lacking. There is no well known open source rich text editor for Android or iOS. We believe that Gutenberg could be a key library for many mobile apps, but that will never happen with the GPL v2.”

                    \n\n\n\n

                    Mobile app developers are limited by the GPL, because it requires the entire app to be distributed under the same license. The team is proposing dual licensing under MPL v2.0, a weaker copyleft license that is often considered to be more “business-friendly.” It allows users to combine the software with proprietary code. MPL v2.0 requires the source code for any changes to be available under the MPL, ensuring improvements are shared back to the community. The rest of the app can be distributed under any terms with the MPL v2.0 code included as part of a “larger work.”

                    \n\n\n\n

                    “The idea here is to keep some of the WordPress-specific modules under the GPL v2.0 only; some of them are not needed and not relevant for using Gutenberg in another software. Ideally, there would be a different way of bundling the project for being used in WordPress or in a non-GPL software,” Biais said.

                    \n\n\n\n

                    The GitHub ticket has several comments from developers who hope to be able to use the editor in their own projects. Radek Pietruszewski, tech lead for a collaborative todo app called Nozbe Teams, has been requesting a relicensing of Gutenberg since October 2019.

                    \n\n\n\n

                    “Our tech stack is essentially React on web and React Native on iOS and Android,” Pietruszewski said. “We’re a tiny company, and so we share >80% of app’s codebase between these 3 platforms.

                    \n\n\n\n

                    “Our app sorely lacks a WYSIWYG editor. We had a working implementation on web, but we decided to scrap it, because there was no way to port it on iOS and Android. There are pretty much no viable rich text editors for iOS or Android, yet alone both. But even then, shipping three completely separate, but somehow compatible editors would be a vast amount of work.”

                    \n\n\n\n

                    When Peitruszewski originally made his case to the mobile team, he identified Gutenberg/Aztec as a basic infrastructure that has the potential to enable many different apps:

                    \n\n\n\n

                    And that infrastructure is sorely lacking. There are very few rich text editor libraries on both iOS and Android — and most of them suck. And if you want an editor that has a shared API for both platforms… you’re stuck. There are no options – Gutenberg is the only game in town (and it’s really good).

                    And it’s very hard to create this infrastructure. WYSIWYG editors are very hard, and it takes entire teams years to develop them (and they still usually suck). Almost no-one has the resources to develop it just for themselves, and if they do, they’re unwilling to open-source it.

                    \n\n\n\n

                    Automattic’s mobile app engineers have struggled to get regular contributions to the apps, despite them being open source. Dual licensing Gutenberg could open up a new world of contributors with the editor being used more widely across the industry.

                    \n\n\n\n

                    “While we might not be big enough to be able to tackle a challenge of developing a rich text editor from scratch, we’re big enough to contribute features and bug fixes to open source projects,” Pietruszewski said.

                    \n\n\n\n

                    Matt Mullenweg was the first comment on Biais’ post in favor of the change:

                    \n\n\n\n

                    I think Gutenberg has a chance to become a cross-CMS standard, giving users a familiar interface any place they currently have a rich text box. There are hundreds and hundreds of engineers at other companies solving similar problems in a proprietary way, it would be amazing to get them working together but a huge barrier now is supporting Gutenberg in mobile apps, which every modern web service or CMS has. (Hypothetically, think of Mailchimp as a possible consumer and collaborator here, but it could be any company, SaaS, or other open source CMS.)

                    \n\n\n\n

                    Unless any major blockers come up in further discussion, this dual licensing change appears to be on track to move forward. Biais noted that a similar license change has already happened on Aztec-Android and Aztec-iOS. The last hurdle is gaining the approval of all the original code contributors or rewriting the code for those who decline to give approval.

                    \n\n\n\n

                    Once Gutenberg can be used under the MPL v2.0, the editor will gain a broader reach, with people already on deck wanting to use it. Other companies and projects that are normally outside WordPress’ open source orbit will also have the opportunity to enrich Gutenberg’s ecosystem with contributions back to the project. At the same time, the MPL 2.0 protects Gutenberg from companies that would try to re-release the code as a closed-source project.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 21 Sep 2020 22:59:10 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:20;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:124:\"WPTavern: GitHub to Use ‘Main’ Instead of ‘Master’ as the Default Branch on All New Repositories Starting Next Month\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=105014\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:269:\"https://wptavern.com/github-to-use-main-instead-of-master-as-the-default-branch-on-all-new-repositories-starting-next-month?utm_source=rss&utm_medium=rss&utm_campaign=github-to-use-main-instead-of-master-as-the-default-branch-on-all-new-repositories-starting-next-month\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4844:\"

                    In August, GitHub announced that it would change the “master” branch name for all new repositories created on the platform to “main” starting October 1. The date is less than two weeks away, and WordPress developers need to be prepared for the change if they use the service for version control or project management.

                    \n\n\n\n

                    The larger tech and web development community began conversations through various venues in June, a time in which the Black Lives Matter was gaining more traction in the U.S. and worldwide. The discussion centered on removing any terminology that could be discriminatory or oppressive to specific groups of people. This ongoing discussion has shown that there is a deep division over whether such changes are necessary or even helpful.

                    \n\n\n\n

                    The WordPress community is dealing with this division itself. Aaron Jorbin proposed a change at the same time to rename the default branch name on WordPress-owned repositories. Through discussion on his post and elsewhere, the community landed on “trunk,” which keeps WordPress projects in line with its SVN roots.

                    \n\n\n\n

                    “To close the circle on this, a decision was made in June and earlier today (August 19),” wrote Helen Hou-Sandí, a lead WordPress developer, in the comments of the original proposal. “I updated the default branch name for new GitHub repositories under the WordPress organization to be trunk after GitHub enabled early access to that feature.”

                    \n\n\n\n

                    As evidenced by the comments on the Tavern’s coverage of the proposal and those on the original post, the WordPress development community as a whole did not support this decision.

                    \n\n\n\n

                    Jorbin has updated several of WordPress’s repositories and switched them to use trunk instead of master. However, there are still some lingering projects yet to be updated, including the primary WordPress and WordPress Develop repositories. He left a comment with an updated list in June. There is no public word on whether the existing, leftover projects will be changed.

                    \n\n\n\n

                    WordPress Developer Preparations

                    \n\n\n\nCustomizing the default branch for a user’s GitHub repositories.\n\n\n\n

                    GitHub is merely changing the default branch name for new repositories starting on October 1. This change does not affect existing repositories. Individual users, organization owners, and enterprise administrators can customize the default branch via their account settings now before the switch is made. Owners can also change the default branch name for individual repositories.

                    \n\n\n\n

                    The biggest thing that developers need to watch out for is their tooling or other integrations that might still require the master branch. There may be cases where an alternative default branch name will break workflows. If planning to use a different branch name, the best thing to do right now is to spin up the tools you use on a test repository. If something breaks, check to see whether the particular tool you are using will be getting an update. In most cases, this should not be a problem because customized default branch names will be an industry standard.

                    \n\n\n\n

                    The great thing about how GitHub is rolling out this feature is that it offers a choice. Those who believe that “master” is oppressive can change the branch name to something they feel is more inclusive. For those who believe otherwise, they can keep their master branch. But, everyone can use the branch name they prefer.

                    \n\n\n\n

                    For existing repositories, GitHub is asking that developers be patient for now. The company is investing in tools to make this a seamless experience later this year. There are a few technical hurdles to clear first.

                    \n\n\n\n

                    Developers should read the full GitHub guide on setting the default branch for more information.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 21 Sep 2020 20:39:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:125:\"WPTavern: Matt Mullenweg and Jamstack Community Square Off, Making Long-Term Bets on the Predominant Architecture for the 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:30:\"https://wptavern.com/?p=104428\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:293:\"https://wptavern.com/matt-mullenweg-and-jamstack-community-square-off-making-long-term-bets-on-the-predominant-architecture-for-the-web?utm_source=rss&utm_medium=rss&utm_campaign=matt-mullenweg-and-jamstack-community-square-off-making-long-term-bets-on-the-predominant-architecture-for-the-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:19953:\"

                    Over the past two weeks, Matt Mullenweg and Jamstack community leaders have forged a new rivalry, after Mullenweg told The New Stack that he sees Jamstack as “a regression for the vast majority of the people adopting it.”

                    \n\n\n\n

                    “The usability and functionality is actually lower,” Mullenweg said to Richard MacManus in an email. “Even rebuilding sites in Jamstack harkens back to the Movable Type days, where the bigger your site gets the slower it is to rebuild or update templates.”

                    \n\n\n\n

                    Mullenweg also described a “fragile” chain of services required to run Jamstack sites.

                    \n\n\n\n

                    “You can patch together a dozen services, each with its own account and billing, for hundreds of dollars a month, to get a similar result you’d have for a few dollars a month using WordPress on shared hosting,” he said. “And it would be more fragile, because the chain is only as strong as its weakest link. You are chaining together different toolsets, logins, billing, hosting… any part of it going down can break the entire flow.”

                    \n\n\n\n

                    Mullenweg has since further clarified his comments while also doubling down on his original premise, saying that “there isn’t a vast number of people adopting Jamstack in the first place, and those who do are probably fully aware of the tradeoffs.” He outlined how he sees WordPress providing a better experience for users in terms of performance, security, scaling, and developer experience. 

                    \n\n\n\n

                    Mullenweg’s provocative remarks set off a chain of open letters from the CEO’s of Jamstack-related services. They are convinced that the LAMP stack is on its way out and that Jamstack is on the precipice of replacing its incumbent as the most dominant architecture of the web.

                    \n\n\n\n

                    Ohad Eder-Pressman, co-founder and CEO of Stackbit, was the first to fire back. He believes that Jamstack is a “disruptive innovation” that may appear to be inferior now because it is still relatively low level and new when compared to a 17-year old product like WordPress.

                    \n\n\n\n

                    “We should be asking whether Jamstack is a better architecture than LAMP and what gaps currently exist with products and solutions built on top of the Jamstack,” Eder-Pressman said. He agreed that Jamstack tools are still largely focused on developers but makes a bold prediction on the stack’s future reach:

                    \n\n\n\n

                    The achievements of WordPress in terms of market share and how it democratized early web publishing are amazing. When it comes to architecture I think it was best in class for the early 2000s but it’s time to move forward. We already see cohorts of websites where Jamstack adoption crosses 20% – it’s no longer a question of if the Jamstack becomes the predominant architecture for the web but a question of when. The cliche is a cliche but it also rings true – First, they ignore you, then they laugh at you (we are here), then you win.

                    \n\n\n\n

                    Eder-Pressman agreed with Mullenweg regarding Jamstack’s lower usability and functionality but touted the architecture as “infinitely more resilient” due to being hosted on a CDN. He admitted that rebuilding larger sites can be slow but cited developments like build parallelization, build cache, partial rebuild, and incremental static regeneration as optimizations as efforts the Jamstack ecosystem is exploring to solve this known issue.

                    \n\n\n\n

                    Netlify CEO Mathias Biilmann, who originally coined the term “Jamstack,” goes so far as to hail “the end of the WordPress era” in his article refuting Mullenweg’s remarks.

                    \n\n\n\n

                    “There’s often a moment right around the time when an old technology is about to be displaced by the next thing, where the main leader in the field goes out and makes a strong argument that absolutely nothing is happening,” Biilmann said. “A moment that ends up looking like a turning point where the new was undeniably present enough to be worth being in denial about.”

                    \n\n\n\n

                    The Bet: By September 2025, what will be the predominant architecture for the web?

                    \n\n\n\n

                    In a brief exchange on Twitter, Mullenweg and Eder-Pressman made a wager for five years into the future, to see if Eder-Pressman’s prediction will hold up, as measured by the Alexa top 10k. In order for Jamstack to become the predominant architecture for the web, it will need to surpass WordPress’ numbers, which are currently hovering at 39.75% (via BuiltWith) and 38.4% (via w3techs).

                    \n\n\n\n
                    \n

                    They currently have us ~37% of top 10k. I wonder if you\'re undercounting us with YC companies too? https://t.co/ki9Ng3DGqI

                    — Matt Mullenweg (@photomatt) September 5, 2020
                    \n
                    \n\n\n\n

                    “I’m happy to make a long bet: 1 year, 5 years, 10 years,” Mullenweg said in another thread in response to Netlify’s CEO. “We’re building and rebuilding WordPress to be generational. We’ve navigated and created bigger architectural shifts in the past, and will do so in the future.”

                    \n\n\n\n

                    “I’m a developer, founder, and investor in the space of web technologies – if I’m not willing to engage in a public discussion and share my predictions for where the web is heading then what merit does my work have?” Eder-Pressman said when I asked him why he was willing to make this public wager.

                    \n\n\n\n

                    “I felt compelled given Mullenweg’s comments and what I believe is the lack of appreciation for how much adoption and momentum Jamstack technologies already have. If anything I would say that my bet is actually pretty cautious.”

                    \n\n\n\n

                    Eder-Pressman and his team at Stackbit are working on a tool to track Jamstack adoption across the web, as BuiltWith does not yet have a Jamstack stat panel that correctly aggregates all the technologies associated with this relatively new category of websites.

                    \n\n\n\n

                    “We’ve built an internal tool that tracks adoption of Jamstack technologies across different cohorts of websites which we find informative,” he said. “This isn’t unlike what say Builtwith provides except that we track a few technologies that they don’t and we bundle this into a Jamstack adoption indicator. We’ve used this internally up until now and are planning to release some public facing version of it later this year.”

                    \n\n\n\n

                    As the CEO of Stackbit, a service that cranks out Jamstack sites in 60 seconds while bypassing any requirement to use the command line or download npm packages, Eder-Pressman is actively engaged in trying to bring this technology stack to the masses. The company aims to solve the very problems that Mullenweg identified in his critical comments, as is evident in the marketing copy on the Stackbit website. It acknowledges that piecing together a Jamstack website can be challenging even for developers:

                    \n\n\n\n

                    “In a fragmented Jamstack environment, developers struggle to glue products together when trying out the latest tech. Stackbit connects the best tools on the market, and helps them play together.”

                    \n\n\n\n

                    A year ago, Stackbit caught my attention and I contacted them to find out when WordPress would land among their list of CMS import options. At that time they said they were considering WordPress as a headless CMS option but did not have it on the immediate roadmap. One year later, Stackbit is no closer to building import capabilities for the most popular CMS on the web.

                    \n\n\n\n

                    “It’s on the horizon but its not something we’ve prioritized,” Eder-Pressman said. “WordPress is a full blown monolithic CMS. It has been used before as a headless CMS but there are better headless CMS choices out there. Even Mullenweg agrees it’s a complicated premise.”

                    \n\n\n\n

                    When asked if his recent conversations have changed the company’s plans to support WordPress imports, he said, “No, it doesn’t make us want to do this any more or less. I really enjoyed the conversation and am glad that Mullenweg recognizes the rise of the Jamstack so much so that he found it necessary to take aim at it. We as a company are driven by the market, user demand, growth opportunities and a healthy vision for the future of the web.”

                    \n\n\n\n

                    Jamstack will need to make itself accessible to the wide world of non-technical website owners if its advocates hope to capture any meaningful segment of the Alexa top 10k marketshare. Stackbit, for one, is still grossly underestimating WordPress’ ability to sustain its phenomenal growth, and doesn’t see the necessity for creating a simple path to convert WordPress users. Eder-Pressman believes that making Jamstack accessible starts with developers.

                    \n\n\n\n

                    “The Jamstack is an architecture which is winning the minds of developers around the world and across the web development stack,” he said. “Adoption for new architectures often begins with developers so I’m excited to see a company like say Netlify boast over 1 million developers on its Jamstack platform.”

                    \n\n\n\n

                    Eder-Pressman’s tool for measuring Jamstack adoption will need to produce some compelling data on the stack’s growth, if his bet is going to materialize. While nearly every offering in the Jamstack ecosystem still falls squarely within the realm of experienced developers, it doesn’t seem likely that five years is enough time for it to overtake WordPress as the predominant architecture for the web. WordPress hasn’t achieved its dominance by prioritizing developer happiness over usability.

                    \n\n\n\n

                    Looking at the numbers five years from now, will we see Jamstack overtake WordPress as the most popular way to build a website? Will Jamstack grow with developer usage and then plateau once it fails to reach regular people who don’t have a git-based workflow at the top of their wishlists? Are we going to find Jamstack and WordPress neck and neck in the battle for the predominant architecture for the web? Those who work with a hybrid of both technologies see no need for this kind of rivalry.

                    \n\n\n\n

                    Shifting the conversation towards collaboration: “Jamstack can be an opportunity for our industry, rather than a threat.”

                    \n\n\n\n

                    “Reading Mullenweg’s comments and the responses from CEOs in the Jamstack community make me feel caught in the middle and a bit frustrated,” Shifter COO Daniel Olson said. “I see friction between two communities that have so much in common.”

                    \n\n\n\n

                    Olson has been a proponent of using Jamstack with WordPress for the past four years since launching Shifter, a static site generator and hosting company that supports headless WordPress sites on the Jamstack.

                    \n\n\n\n

                    “If you look for the most secure, cost-effective way to build and host a high-traffic website today, the cross-section you’ll arrive at is the Jamstack. Looking at how it offers each of those benefits, you will find inspiration and ways WordPress could do the same,” Olson said. “Rather than write something off wholesale, see what you can learn and apply it.”

                    \n\n\n\n

                    Olson said his mission is to bridge the gaps between WordPress and the benefits Jamstack offers, while working through its early days and messy parts, innovating on the tools that work.

                    \n\n\n\n

                    “We should be working together to address specific challenges and worry less about how we get there,” Olson said. “Some technologies are indeed a better fit for solving each of those challenges but you don’t need to leave one ecosystem for the other to do it. You can share knowledge and best practices and discover what’s possible. There’s a good chance you’ll end up creating something new, which is part of that innovation we need in our communities.”

                    \n\n\n\n

                    Jamstack hosting services for WordPress are eager to remind users that they don’t have to go all in on the technology. You can have your JAM and spread it on top of WordPress, accommodating developers’ love for experimenting with new frontend technologies, while preserving the dynamic publishing power that has been refined over the past 17 years. These hybrid hosting companies aim to enable this without leaving users behind.

                    \n\n\n\n

                    “Matt is absolutely right that the usability and functionality of the Jamstack is lower,” Strattic co-founder and CEO Miriam Schwab said. “The Jamstack is a great example of technology that is incredibly appealing to developers, but the actual end users – writers, marketers, business owners – cannot use it. I’ve heard many stories of major companies that have come to the decision to adopt Jamstack for all web development as a company-wide policy, only to find that their marketing team has gone rogue and is installing WordPress sites in order to get their job done.

                    \n\n\n\n

                    “The reason for this is like Matt said: every Jamstack site is a compilation of layers of services, and each layer has dozens of options available: you need a static site generator, a CMS, static hosting, and a CDN – and you need to tie it all together with version control. This is all cool and shiny, and the output is truly fantastic because when you have a site that’s a collection of pre-rendered static files served up through a CDN it’s fast, secure, scalable and stable. But then along comes marketing and they want to set up a landing page and they are totally dependent on their dev team and can’t move forward without them. That defeats the purpose of a CMS-driven website! With WP, you get all the layers in one platform…but you don’t get the awesome output.”

                    \n\n\n\n

                    Schwab said she sees WordPress having its age work both for it and against it, but ultimately she believes in enabling real world users to manage their own websites without having to rely on developers.

                    \n\n\n\n

                    “I’ve seen many companies abandon WP for the shiny new stack, and then come back to it,” Schwab said. “Github is a good example of this – yes Github, the modern repository of cutting-edge code moved their blog off of WordPress, and then came back because it truly is the best tool for just getting your content out there. There aren’t a zillion steps and integrations – you write content, click Publish, and that’s it. It gets the job done, and the fanciest tools will never beat something that just gets the job done.”

                    \n\n\n\n

                    At the same time, WordPress needs to be open to enabling diverse frontend implementations, if it wants to remain relevant for the next decade. “WP is running on legacy architecture,” Schwab said. “It’s showing its age, and it’s not appealing to new generations of developers. We need to keep WordPress appealing and interesting to developers in order to secure its future for years to come. If we don’t make developers excited, we will inevitably see a decline.” She encourages the WordPress community to embrace Jamstack as “a breath of fresh air.”

                    \n\n\n\n

                    “Jamstack can be an opportunity for our industry, rather than a threat,” Schwab said. “There are ways for the two industries to collaborate, like in the case of headless WP deployments using Gatsby.”

                    \n\n\n\n

                    Unlike many other Jamstack service companies, the team behind Gatsby has more readily embraced WordPress as a data source and a critical component of its continued success. The company hired Jason Bahl, creator of the GraphQL for WordPress project, to work on WPGraphQL (and its immediate ecosystem) full-time, while providing a bridge to the WordPress world.

                    \n\n\n\n

                    “Maybe I’m getting caught up in semantics, but the JAM in JAMStack means JavaScript, APIs and Markup,” Bahl said. “It wasn’t long ago when Matt prescribed the WordPress ecosystem to ‘Learn JavaScript Deeply,’ and not long after that when a Jamstack application called Gutenberg was merged into WordPress core, along with React. Gutenberg is the JavaScript, the WP REST API is the API and the end result is markup. Jamstack isn’t a regression, it’s a future that Automattic is helping drive WordPress toward.”

                    \n\n\n\n

                    When Mullenweg says he is ready to build and rebuild WordPress to be generational, it’s a promise he has already delivered on by introducing the React-based Gutenberg editor two years ago, successfully pushing past an enormous amount of resistance from the developer community.

                    \n\n\n\n

                    Bahl said he sees this continued legacy of improvement happening over and over again in various ways, made possible by WordPress’ pluggable system:

                    \n\n\n\n

                    WordPress ships with a lot of APIs, but often they are replaced with something newer and better. For example, it’s common for sites to offload images to a CDN instead of use the built-in file system for media. Or instead of using built-in WordPress MySQL search, users will reach for ElasticSearch, Algolia or Solr. In the case of WordPress and the JAMStack, reaching for Next, Gatsby or Gridsome to replace the built-in Theme API isn’t a regression, it’s using newer technology to handle things that built-in parts of WordPress might not do as well. The Theme API of WordPress is just one API and replacing it with technology that does the job better isn’t a regression.

                    \n\n\n\n

                    Gatsby’s build step, which has received negative attention in the news recently, is one example of what Bahl thinks Mullenweg was referring to as a regression for users. Bahl is working with Gatsby to reduce the friction associated with decoupled architectures when using WordPress as the API in Jamstack.

                    \n\n\n\n

                    “I don’t see Jamstack competing against WordPress,” Bahl said. “In my mind, Jamstack with WordPress as the API is the future of the web. WordPress is the best CMS. Gatsby specifically is trying to embrace this. This isn’t a zero sum game. If the Gatsby + WordPress experience can allow users to use the best CMS in the world while using modern dev tooling, it’s a win all around.”

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 19 Sep 2020 18:54:01 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:22;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:51:\"WPTavern: Matt Mullenweg Clarifies Jamstack Remarks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104883\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:147:\"https://wptavern.com/matt-mullenweg-clarifies-jamstack-remarks?utm_source=rss&utm_medium=rss&utm_campaign=matt-mullenweg-clarifies-jamstack-remarks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6205:\"

                    Two weeks ago, Matt Mullenweg made some pointed remarks in an article from The New Stack, calling Jamstack “a regression for the vast majority of the people adopting it.” In preparation for an upcoming article that will include comments from leaders across both the WordPress and Jamstack communities, I asked Mullenweg if he stands by his remarks characterizing Jamstack as a regression. His response was lengthy and is printed here in its entirety to preserve cohesion.

                    \n\n\n\n

                    Q: Do you stand by your remarks that Jamstack is a regression for the vast majority of the people adopting it?

                    \n\n\n\n

                    Answer:

                    \n\n\n\n

                    “Vast majority of people adopting it” was probably too harsh, because there isn’t a vast number of people adopting Jamstack in the first place, and those who do are probably fully aware of the tradeoffs. There are some good reasons, for certain situations, to decouple and add complexity to your architecture, and WordPress’ REST API works fantastically as a backend there. But I worry they are over-selling the promise of what’s really an architectural decision. If you look at the benefits they purport, it’s better performance, security, scaling, and developer experience:

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

                    Better Performance: You can achieve the same performance by putting a great CDN like Cloudflare on top of WordPress, and your life will be infinitely easier when you want to add dynamic features like a store or comments. You can also easily find a static WordPress host like Strattic or Shifter.

                    \n\n\n\n

                    Higher security: I don’t believe that introducing a number of proprietary and sub-scale SaaS services like Netlify into your stack will make your site more secure. I believe the most secure thing you can do is run fully open source code, as widely vetted and used as possible, on servers you control, or from the fewest number of vendors possible. WordPress securely runs some of the most attacked websites on the internet, including major media, Facebook, and WhiteHouse.gov. Having this many moving parts doesn’t inspire confidence:

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

                    Cheaper, easier scaling: CDNs are more expensive than normal hosting accounts, and you can get WordPress running on a decent host for less than $5/mo. And there are even more powerful offerings: The personal plan on WP.com can serve tens of millions of visitors per day, to the website or the headless API, includes a global CDN, and a domain name for $4/mo, and we still have a profit margin. GraphCMS starts at $29/mo and only gives you “5,000 entities,” whatever that means. Contentstack is $3,500/mo. And that’s just for the headless CMS part! You still need to sign up and pay for a bunch of the other stuff in that graphic before you have a website a human can visit in a browser.

                    \n\n\n\n

                    Better developer experience: If your developer wants to copy and paste updates from marketing to the website, sure, but if they want people to be able to update the website without their help, they should go with something easier for users like WordPress. If you’re curious about the developer experience, or an investor thinking about this space, I really suggest you watch this three hour and thirty minute tutorial to really understand what is being sold under the premise of “better”:

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

                    Have I ever built stuff like that? Totally! It can be a ton of fun, like building a rocket at home or fixing up an old car. I’ve seen some awesome sites built on decoupled architectures or static publishing, using headless WordPress rather than the CMS’s above, but still a similar idea. People are trying to paint me as being against Jamstack, but that is as foreign to me as being against duct tape — it’s good for some things, bad for others, and it’s not going away. I just wish they would be more intellectually rigorous and honest when marketing it. I expect a Jamstack-like approach to exist forever, just like the ideas behind Jamstack pre-date it getting jammed down our throats by Netlify’s marketing team.

                    \n\n\n\n

                    Biilmann has got the Ballmer / iPhone story backwards — Microsoft’s mistake there was they made something too complicated, and the iPhone simplified it. Jamstack introduces numerous vendors, build steps, network calls, interfaces, even billing relationships for something that’s a single button press in WordPress.

                    \n\n\n\n

                    The reason services like WordPress.com and Shopify are growing so much is they are taking things that were complicated and making them simpler and accessible to a much wider audience. My mission is to democratize publishing and commerce, to make it radically accessible to everyone regardless of technical or economic ability, and increase the freedom and openness on the internet. As I said on Twitter, the first 15 years of WordPress were just the first few chapters. I’m looking forward to building and rebuilding the platform the rest of my lifetime, and when that comes to an end I hope future generations will carry the torch.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 18 Sep 2020 22:49: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: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:65:\"WPTavern: Gutenberg’s Custom Spacing Should Be Theme Controlled\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104867\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:169:\"https://wptavern.com/gutenbergs-custom-spacing-should-be-theme-controlled?utm_source=rss&utm_medium=rss&utm_campaign=gutenbergs-custom-spacing-should-be-theme-controlled\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5679:\"Adjusting padding on a Group block.\n\n\n\n

                    When Gutenberg 9.0 landed earlier this week, it came with an experimental padding control for the Group block. Most users will not see it unless their theme has opted into supporting the feature using the experimental-custom-spacing flag.

                    \n\n\n\n

                    This was not the first that we have seen of the padding option on a block. Gutenberg 8.3 introduced it for the Cover block. Since then, nothing has changed with the implementation.

                    \n\n\n\n

                    The problem with the custom spacing/padding option is that it creates an inline style that does not adjust based on the design of the theme. Fortunately, the feature is still experimental. This means that we have time to reevaluate how it works.

                    \n\n\n\n

                    Unless we’re doing away with any remaining illusion that themes will play an important aspect of WordPress’s future and front-end design becomes fully entrenched within core, theme authors need some level of control. And, even if themes are going the way of the dinosaur, custom padding numbers on the block level will create design consistency issues down the road. Using 100 pixels of padding might make sense within a site’s current design, but 96 pixels might make sense within a future design. When a user adds dozens or hundreds of blocks with custom padding today, it will wreak havoc on tomorrow’s spacing and rhythm.

                    \n\n\n\n

                    Besides that, the average user has little concept of design rules. Having a standardized system for spacing would give theme authors control over the output while giving end-users the ability to customize the look.

                    \n\n\n\n

                    I have argued that WordPress needs some sort of design framework. For example, Tailwind CSS has specific padding classes. So does Bootstrap and nearly every other CSS framework. The web development community has been down this road. It is a well-trodden path, and WordPress is not innovating by using inline styles.

                    \n\n\n\n

                    If the WordPress platform is going to put this sort of power into the hands of its users, it should do so in a way that allows designers to do their thing and not push users toward semi-permanent, inline-style soup in their content.

                    \n\n\n\n

                    Pre-Gutenberg, I would have been entirely against the idea of WordPress introducing any sort of CSS or design framework. However, the platform is consistently moving toward becoming a UI-based design tool rather than simply a way to manage content. Users will have design-related options on a global scale all the way down to individual blocks. Users should absolutely have the ability to adjust a block’s padding in such a system. They should not need an understanding of CSS to do so. Instead, for most use cases, users should be able to adjust padding based on whether they want larger or smaller spacing, not specific CSS values.

                    \n\n\n\n

                    I propose a full set of standardized padding classes. The same would go for margins or other design-related options down the road. Gutenberg/WordPress should create a set of default values for these classes, which theme authors could override based on their design.

                    \n\n\n\n

                    This is not a new concept. Dave Smith, a developer for Automattic, introduced a patch in 2019 that used named selectors for spacing on the Group block. He gave the following reasoning for choosing this approach over absolute values:

                    \n\n\n\n

                    Imagine you are a Theme designer. You craft your CSS with spacing that is perfect for the design. You want to ensure that is consistent throughout your Theme, even if the page layout is being created by the end-user in the Block Editor.

                    With the approach I’ve taken here, when a size is selected only classes are added to the Block in the DOM. This affords the Theme creator the opportunity to provide custom sizes in CSS that are suitable for their Theme. If they opt not to do this then sensible defaults are provided.

                    With the pixels approach, we’re locking users of the Block into absolute values and asking them to make a lot of decisions that they’d probably prefer not to have to make. It could also lead to an inconsistent visual experience.

                    \n\n\n\n

                    This ship has already sailed and sunk with custom colors and font sizes. Gutenberg had an opportunity to standardize class names for these options but left it to theme authors. As a result, there is no standard across the theme market, which means that choosing the “large” font size or the “blue” text color provided by the theme will likely not carry across to the user’s next theme. Now, we are on the cusp of far more design-related options as WordPress moves toward full-site editing. It is time to consider some standards on design-related class names and provide a framework that all themes can use.

                    \n\n\n\n

                    Gutenberg could still provide a custom padding option just like it does for colors and font sizes. Users who choose to go this route would be making an explicit choice to work outside of the standard. But, let’s not go down this road of allowing users to set absolute spacing values as the default option.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 18 Sep 2020 18:49: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:14:\"Justin Tadlock\";s: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:75:\"WPTavern: GoDaddy Acquires SkyVerge, Creator of Over 60 WooCommerce Add-Ons\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104658\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:193:\"https://wptavern.com/godaddy-acquires-skyverge-creator-of-over-60-woocommerce-add-ons?utm_source=rss&utm_medium=rss&utm_campaign=godaddy-acquires-skyverge-creator-of-over-60-woocommerce-add-ons\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4911:\"

                    On September 14, GoDaddy announced it had acquired SkyVerge, a major WooCommerce-focused development company, for an undisclosed amount. At the moment, GoDaddy is playing it close to the vest in terms of its future plans. It has not publicly announced anything beyond a continued commitment to current customers.

                    \n\n\n\n

                    The initial announcement makes note that SkyVerge’s free plugins on WordPress.org have been downloaded more than 3.1 million times. However, the company’s nine plugins in the directory currently have over 155,000 active installs. Nevertheless, SkyVerge’s real value is in its team and its impressive array of free and commercial add-on plugins available directly from its site.

                    \n\n\n\n

                    WooCommerce is a cash cow for companies with the right products and marketing at the moment. GoDaddy seems to be going all-in on the back of WordPress’s most popular eCommerce solution. It launched a managed WooCommerce hosting plan in October 2019. The hosting company has now added over 60 WooCommerce extensions to its inventory in one swoop.

                    \n\n\n\n

                    “As more small businesses and entrepreneurs go online, having a highly performant eCommerce experience is becoming more important than ever,” said Rich Tabor, Senior Product Manager of WordPress Experience at GoDaddy. “Late last year we launched a Managed WooCommerce offering, bundling many WooCommerce extensions in the Managed WordPress environment.”

                    \n\n\n\n

                    SkyVerge has quietly become a massively successful WordPress and WooCommerce business. It was bringing in $350,000 per month at the end of 2019. There was no response on how well the business has performed thus far in 2020.

                    \n\n\n\n

                    The entire SkyVerge team came along for the transition to GoDaddy. “We’re just beginning to deliver more capabilities and an even better setup and ongoing usage experience for our customers,” said Tabor. “The SkyVerge team will lead and accelerate those plans. They are an incredibly talented and innovative team that lives and breathes WooCommerce. Joining forces with them advances GoDaddy’s WordPress strategy and enhances our ability to deliver intuitive eCommerce experiences that help everyday entrepreneurs sell online.”

                    \n\n\n\n

                    With so many extensions in place, the big question for average users is whether those extensions will become a part of GoDaddy’s eCommerce hosting bundle. Tabor either did not or could not let slip any plans in the works. “We’re just beginning to determine how to best deliver SkyVerge’s wonderful products to GoDaddy customers. SkyVerge brings a lot of great software. It’s reasonable to expect we’ll be delivering that to our customers who are selling online.”

                    \n\n\n\n

                    It is doubtful that GoDaddy went into this acquisition without at least some short-term plans or visions for how its managed hosting service would use these extensions. For now, we will have to wait and see.

                    \n\n\n\n

                    It seems that the immediate plan will be to maintain business as usual. Tabor said GoDaddy had no changes to announce related to SkyVerge’s products and website. “We are committed to continuing support of SkyVerge’s customers and investing in the SkyVerge software,” he said.

                    \n\n\n\n

                    SkyVerge also created Jilt, which is an email marketing platform for eCommerce sites. The platform currently supports WooCommerce, Easy Digital Downloads, Shopify, and Shopify Plus. Tabor did not directly respond to what the future looked like for Jilt’s non-WooCommerce customers nor did he give any indication of whether there were plans to expand Jilt to other eCommerce systems.

                    \n\n\n\n

                    He did say that GoDaddy would continue to invest in its priority eCommerce platforms, which are WooCommerce and GoDaddy Websites + Marketing.

                    \n\n\n\n

                    Max Rice, co-founder of SkyVerge, did leave some indication of Jilt’s future in his announcement post. “We made a commitment to be there for your business with software you can depend on, and we’re sticking to it,” he said. “We’ll continue to support our existing WooCommerce plugins and Jilt. While we’ll be building something new at GoDaddy, everything we’ve already built is a big part of that.”

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 17 Sep 2020 20:59:02 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:86:\"WPTavern: Gutenberg 9.0 Brings Major Improvements to Navigation Screen and Query 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:30:\"https://wptavern.com/?p=104795\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:217:\"https://wptavern.com/gutenberg-9-0-brings-major-improvements-to-navigation-screen-and-query-block?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-9-0-brings-major-improvements-to-navigation-screen-and-query-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:2749:\"

                    If you haven’t played around with Gutenberg’s experiments lately, the Navigation block is getting some exciting updates. Version 9.0 was released today with drag-and-drop support added to the list view of navigation items.

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

                    Contributors have been working through several different prototypes aimed at unifying the controls and simplifying the menu building process. The Navigation screen included in version 9.0 has been redesigned to improve the “Create Menu” flow and includes the following changes:

                    \n\n\n\n
                    • New Header and Toolbar components.
                    • Manage Locations has been rewritten and is now a popover.
                    • Add New form has been rewritten and now appears inline in the toolbar.
                    • Automatically Add Pages checkbox and Delete menu button has been rewritten and now appears in the block inspector.
                    \n\n\n\n

                    The screen is starting to take shape but is still very much a work in progress. If you want to test it, you can enable it under Gutenberg > Experiments.

                    \n\n\n\n

                    The Query block was another main focus fr the 9.0 release. It is taking a giant leap forward with new features like search, filtering by author, support for order/order by (date + title), and tags. This block should be tested locally and is still behind the __experimentalEnableFullSiteEditing flag since it requires full site editing blocks to display queried content.

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

                    Other notable UI enhancements include a new drag handle added to block toolbar for drag-and-drop capability. (It is not visible on the top toolbar). Blocks can be dragged to other areas of a post as an alternative to using the up/down arrows.

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

                    This release also removes the Facebook and Instagram blocks from the inserter, as Facebook will be dropping unauthenticated oEmbed support on October 24. WordPress core is also set to remove Facebook and Instagram as an oEmbed provider in an upcoming release.

                    \n\n\n\n

                    For a full list of all the enhancements, bug fixes, experiments, and documentation updates, check out the 9.0 release post 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 17 Sep 2020 03:18: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:\"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:81:\"HeroPress: How To Become A Freelancer – A Few Things I Learned Before I Gave Up\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=3280\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:206:\"https://heropress.com/essays/how-to-become-a-freelancer-a-few-things-i-learned-before-i-gave-up/#utm_source=rss&utm_medium=rss&utm_campaign=how-to-become-a-freelancer-a-few-things-i-learned-before-i-gave-up\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:28154:\"\"Pull

                    Članak je takođe dostupan na sprskom jeziku.

                    \n

                    Everyone’s story is unique. Our life journeys differ in so many aspects and these experiences shape us into who we are now. Therefore, things that we, as individuals, learn along the way can’t always apply to someone else’s life goals, potentials, aspirations, and struggles.

                    \n

                    But, sometimes, knowing about other people’s mistakes and successes can help us navigate through our life challenges better. We can avoid making the same mistakes and, even better, we can get inspired to accomplish similar achievements.

                    \n

                    That is why I decided to share a few things that I have learned by trying to become a freelancer. Spoiler alert – I’m a corporate employee now.

                    \n

                    My career path was a bit unusual. I wasn’t quite tech-savvy until 5 years ago and my entire focus was around the fitness industry from 2006 until 2015. Being a fitness trainer was a dream job for me when I was 26 but, by the age of 35, it became somehow, well, boring.

                    \n

                    Then I had a huge epiphany – numerous opportunities come with WordPress and freelancing was one of them. So, if you are at the stage of your life when becoming a freelancer seems like a good idea, read on.

                    \n

                    I will try to break down 5 things that helped me in starting my freelance career. They are formulated as general tips for beginners but some of them can also be applied when changing the course of your career. So, let’s dive right in.

                    \n

                    Question your motives

                    \n

                    The first and the most important thing that you should ask yourself before you do anything in your life is why. “Why am I doing this?”

                    \n

                    So, why do you want to become a freelancer?

                    \n

                    Is it because you need an extra income? Or maybe because of flexible working hours. Or because you will be able to work from different locations? Or you see freelancing as just a phase before you get enough experience to open your agency and have others working for you.

                    \n

                    Be honest with yourself. List all the reasons why you want to become a freelancer. This will help you later on in choosing the right jobs or maybe in considering some other alternatives to freelancing.

                    \n

                    For example, these are my top 3 motives to become a freelancer:

                    \n
                      \n
                    • Opportunity to grow intellectually and learn new things
                      • \n
                    • Flexible working hours (by not being forced to work 9 am to 5 pm every day, I was able to avoid the boring routine)
                      • \n
                    • Peaceful and quiet working environment – quite opposite to the gym where everything is so loud
                      • \n
                    \n

                    So, after you question your goals and motives, and you are certain that you want to become a freelancer what’s next? My suggestion is – develop WordPress related skills.

                    \n

                    Get the skills – choose WordPress

                    \n

                    Why WordPress you might ask? Well, for a start, WordPress gives various opportunities and it is not a developer-only niche.

                    \n

                    Although, when someone thinks of freelancing and WordPress, web developer and web designer are first associations, there is a huge variety of WordPress related freelance jobs:

                    \n
                      \n
                    • Web developer (coding websites, themes, and plugins)
                      • \n
                    • Web implementor (creating websites from existing themes without coding)
                      • \n
                    • Web designer (designing website mockups, editing images or creating infographics for websites)
                      • \n
                    • Client support professional (helping people with their websites)
                      • \n
                    • Website maintenance professional (takes care of the website to make sure that WordPress, themes, and plugins are up to date and new backups are created regularly)
                      • \n
                    • WordPress teacher (teaching clients how to use WordPress or teaching other web professionals)
                      • \n
                    • Content writer
                      • \n
                    • Accessibility specialist (making sure that certain standards are met and suggesting solutions for accessibility barriers)
                      • \n
                    • SEO consultant
                      • \n
                    • Statistics consultant (especially for webshops)
                      • \n
                    • WordPress assistant (adding new content and editing existing posts)
                      • \n
                    • Website migration specialist (moving websites from one server to another)
                      • \n
                    • Web security specialist
                      • \n
                    \n

                    Another reason why WordPress is great for freelancers is a strong community that exists around this CMS. There are regular meetups, WordCamps, and other events (they are now switched to online), where you can get a ton of useful information, and also get to ask like-minded people literally anything. The community is so large and diverse, that you will definitely find the answer to any question. It’s much easier to start your freelance career when you have such a great community around you.

                    \n

                    Plan in advance

                    \n

                    Now that you know where the opportunity lies, you can start planning your career.

                    \n

                    Becoming a freelancer is a process. At the beginning of that process, you should acquire or improve relevant skills that will make you stand out in the freelance market. And, of course, as you learn and grow, you will be able to take more challenging and better-paid jobs.

                    \n

                    Which skill should you focus on? If you already have a basic skill set for at least one of the previously listed jobs, you can improve your knowledge in that direction and specialize in that area.

                    \n

                    However, if you don’t have any relevant skills, in my opinion, it would be the easiest to step into the freelancing world with a job that has a shorter learning curve and build your knowledge around that. Example – you can start with either content writing or as a web implementer since these jobs have a shorter learning curve than SEO related jobs or web development. Then, from content writing, you can expand your knowledge towards SEO and from a web implementer, you can become a developer. Just don’t stop learning.

                    \n

                    Also, if you have specific talents or hobbies like writing or design, you can base your career on that.

                    \n

                    There is nothing better than doing what you love.

                    \n

                    Additionally, it would be a good idea to analyze the market before you jump into the learning process.

                    \n

                    For example, now it would not be the best time to specialize in writing travel-related content, while it would be a great moment for any job related to webshops and online sales.

                    \n

                    If you want to learn web development, web design, web security, or SEO, you should always focus on new trends, so your skills can be useful in the future as well.

                    \n

                    For different jobs, working terms often vary so you should take this into consideration when choosing your career path. At some jobs, you can work flexible hours while at others you have to be available during predefined hours. This is what you should have in mind when specializing in a certain area or looking for a first job.

                    \n

                    Hurray, it’s time to get a first freelancing job

                    \n

                    If you currently have a job, it would be wise to either save some money before you quit your job to become a full-time freelancer or try freelancing for a few hours per week, in the beginning, to see if you like it or not. If you become successful and decide that freelancing is something that fits your needs, only then quit your job, not before.

                    \n

                    Although some people do benefit when taking a risk, think twice before you take any irreversible actions.

                    \n

                    And here are some tactics that worked for me when trying to get my first freelancing job:

                    \n

                    Use a freelancing platform – although this is not mandatory, it is much easier to get the first job when you are using a freelancing platform. My choice was Upwork back in the day, but there are several platforms that you can use to get the first job faster.

                    \n

                    Triple-check your resume – I guess that this is not something that I should mention but I will anyway, just in case. Don’t make spelling mistakes in your resume, it will give the impression that you are not thorough and that you will oversee mistakes in your other work as well.

                    \n

                    Present yourself in a professional manner – Take the time to present your professional skills in the best possible light but still stay humble. Don’t write: “Best WordPress developer that never wrote a bad code”. This is not evidence-based, and it will make you seem arrogant. Instead, you can write: “Web developer with 3 years of experience and over 50 satisfied clients, specialized in WordPress.” This statement is based on facts and it shows your credibility.

                    \n

                    Fill up your portfolio – If you have any previous work (that is presentable, of course) you should put it in your portfolio. Emphasis on presentable. If not, you can make a few websites, designs, or write some example texts if you are a content writer in order to showcase your skills. This is not applicable to all jobs, like SEO consultants or customer support but if you have the opportunity to create a portfolio, use the opportunity.

                    \n

                    Use video material – Short introductory video will make you stand out since making promotional video material is not something that many freelancers do. It will help you create a more human professional approach. For your clients, you will not be just a list of skills and previous experiences, but a real person that has these skills and experiences and that provides a certain service for them.

                    \n

                    Have a detailed strategy when choosing your first employer – Choose your first employer wisely, very wisely. I can’t emphasize enough how important this is so I will give you an example. When I had to apply for my first job, I considered the following:

                    \n
                      \n
                    • How this employer was rated by other freelancers which worked for him previously
                      • \n
                    • How the employer rated other freelancers
                      • \n
                    • How much money he had already spent on this platform and if he posts regular job offers
                      • \n
                    • The number of open positions for this job and the number of freelancers that have already applied. In my case, the job had about 10 open positions so that amplified my chances of getting hired, even if the competition is high.
                      • \n
                    \n

                    The first job is not all about the money – Don’t get greedy on your first job. If you get good reviews, your second job can be paid 2-3 times more. And your third job can go up to 5 times more. That was my experience at least.

                    \n

                    Be careful, you are an adult

                    \n

                    Individual responsibility is key when it comes to freelancing. You have the freedom to choose who you are going to work for, what kind of job are you going to take, and how it is going to be delivered. And freedom often comes with responsibility. They are like two sides of the same coin.

                    \n

                    You should never miss a deadline. If you are not sure that you are going to be able to deliver, don’t take the job or as an alternative have someone very reliable as a backup, just in case. When you miss a deadline, your client loses money, and they have every right to be angry. This will very likely affect your reviews after the job is complete. And then, the opportunity to get your next job and so on. This can start a downward spiral for your career.

                    \n

                    However, we are all humans and unpredictable things can happen. If for some reason you are not able to complete your work in a timely manner, let your client know immediately so they can have enough time to hire someone else.

                    \n

                    Also, it is important to make everything clear in advance, before you accept the job. Let your clients know what your expectations are and make sure that you understand what they expect from you. For example, if you are a content writer, make sure that you know the length of the text in characters or words, ask if some keywords should be used and how frequently, what writing style your client prefers, and so on. And if you are a designer, specify how many revisions are included in the price.

                    \n

                    The clearer the initial arrangement is, the more satisfied both you and your client will be at the end.

                    \n

                    If you have flexible working hours, don’t let other people interrupt you. If your friends and family wouldn’t show up in your office every day if you were a bank clerk, they shouldn’t interrupt you when you work from home. It’s the same principle and it’s up to you to set the boundaries and let them know about your working schedule. It’s not up to them.

                    \n

                    So, these are some basic guidelines that helped me in starting my freelance career and I hope that they will be helpful for you as well.

                    \n

                    There is no unique recipe and one size doesn’t fit all when it comes to the path you ought to take.

                    \n

                    It’s just important to stay focused on your goals and to be open to new opportunities.

                    \n

                    If you were wondering why I’m not a freelancer anymore, this is where the answer lies. By constantly being interested in different opportunities, I realized that freelancing is not the only way to achieve my goals. There are companies that offer flexible working hours and peaceful work environment while stimulating professional growth and creative thinking.

                    \n

                    Plus I gained something very precious by joining a team – my colleagues became my support system both professionally and privately, and that is what I have been missing while being a freelancer.

                    \n

                    I wish you a lot of luck and success in the future, regardless of the path you choose to take.

                    \n

                    Kako postati frilenser – stvari koje sam naučila pre nego što sam odustala

                    \n

                    Naše životne priče su različite. Svako od nas ima svoj jedinstveni životni put, a iskustva koja steknemo oblikuju nas u osobe koje smo danas. Zbog toga, stvari koje mi, kao pojedinci, naučimo na svom putu ne mogu uvek lako da se primene na situacije kroz koje prolazi neko drugi.

                    \n

                    Ipak, ponekad sagledavanje tuđih uspeha i grešaka može da nam pomogne da se bolje snađemo u sopstvenim životnim izazovima. Možemo da izbegnemo da napravimo istu grešku koju je napravio naš prijatelj ili, još bolje, možemo postati motivisani da postignemo jednak ako ne i veći uspeh kao neko iz našeg okruženja.

                    \n

                    Zbog toga sam odlučila da sa vama podelim ono što sam naučila pokušavajući da postanem frilenser. Spoiler alert – sada sam zaposlena u korporacji.

                    \n

                    Moja karijera je isla pomalo neuobičajenim putem. Nisam uopšte bila naklonjena informatici do pre pet godina. Tačnije nisam znala skoro ništa o toj oblasti. Bila sam potpuno fokusirana na fitnes industriju i radila sam isključivo kao fitnes trener od 2006. do 2015. To je za mene bio posao iz snova dok sam bila mlađa ali mi je oko moje 35. godine već pomalo dosadio.

                    \n

                    Tada sam otkrila WordPress i shvatila da se mnogobrojne prilike otvaraju bas sa poznavanjem ove platforme. A frilensing je jedna od njih. Tako da, ako ste trenutno u fazi kada vam se frilensovanje čini kao dobra ideja, nastavite da čitate.

                    \n

                    Pokušaću da detaljno opišem pet stvari koje sam naučila pokušavajući da postanem frilenser. Formulisala sam ih kao uopštene savete za početnike, ali neki od njih mogu da se primene i kada menjate kurs svoje frilens karijere.

                    \n

                    Preispitajte svoje motive

                    \n

                    Prva i najvažnija stvar koju treba da se zapitate pre nego što uradite išta u životu je zašto. “Zašto to radim?” Zbog čega želite da postanete frilenseri? Da li zbog toga što vam treba dodatni prihod? Ili zbog fleksibilnog radnog vremena? Ili da biste mogli da radite sa bilo koje lokacije na svetu? Ili frilensing vidite kao fazu pre nego što steknete dovoljno iskustva da možete da otvorite svoju agenciju.

                    \n

                    Budite iskreni prema sebi. Popišite koji su to razlozi zbog kojih želite da budete frilenser. Ovo će vam kasnije pomoći pri izboru adekvatnog frilensing posla ili pri razmatranju neke druge alternative.

                    \n

                    Na primer, ovo su bila moja tri glavna razloga:

                    \n
                      \n
                    • Prilika da naučim nesto novo i da se intelektualno razvijam u nekom novom pravcu
                      • \n
                    • Fleksibilno radno vreme – time što sam imala fleksibilno radno vreme bila sam u mogućnosti da izbednem dosadnu “od 9 do 5” rutinu
                      • \n
                    • Tiho i mirno radno okruženje, potpuno u suprotnosti sa teretanama u kojima je uvek bučno
                      • \n
                    \n

                    Nakon što ste preispitali svoje ciljeve i motive, i sigurni ste da želite da se bavite frilensingom, šta dalje? Moj predlog je naučite nešto što je vezano za WordPress.

                    \n

                    Steknite znanja vezana za WordPress

                    \n

                    Sada se možda pitate zašto baš WordPress. Za početak, zato što WordPress nudi mnoštvo raznovrsnih prilika, i to ne samo za developere.

                    \n

                    Iako, kad se pomene WordPress, prvo što će nekome pasti na pamet je ili developer ili web dizajner, postoji veliki broj različitih poslova vezanih za WordPress:

                    \n
                      \n
                    • Web developer (kodira sajtove, teme i dodatke)
                      • \n
                    • Web implementator (pravi sajtove od gotovih tema bez kodiranja)
                      • \n
                    • Web dizajner (dizajnira skice sajtova, edituje slike i kreira infografike za sajtove)
                      • \n
                    • Korisnička podrška (pomaže klijentima kada se nešto desi sa sajtom)
                      • \n
                    • Održavanje sajtova (redovno održava sajt, kreira bekape, ažurira teme, dodatke i sam WordPress)
                      • \n
                    • WordPress predavač (uči klijente kako da koriste WordPress ili uči druge web profesionalce koji se usavršavaju u nekoj oblasti)
                      • \n
                    • Pisac tekstova za sajtove
                      • \n
                    • Specijalista za aksesibilnost (vodi računa da određeni standardi budu ispunjeni i predlaže rešenja za barijere u aksesibilnosti)
                      • \n
                    • SEO konsultant
                      • \n
                    • Statističar (najčešće radi za velike onlajn prodavnice)
                      • \n
                    • WordPress asistent (unosi novi sadržaj i menja postojći)
                      • \n
                    • Specijalista za migracije (seli sajtove sa servera na server)
                      • \n
                    • Specjalista za web bezbednost
                      • \n
                    \n

                    Još jedan razlog zbog kojeg mislim da je dobro izabrati WordPress je jaka zajednica koja se okupila oko ovog CMS-a. Redovno se održavaju manja okupljanja (trenutno na daljinu) ali i ona veća koja su nazvana WordCamp (takođe na daljinu do daljnjeg) na kojima možete dobiti pregršt korisnih informacija i pitati druge profesionalce sve što vas interesuje. Zajednica je toliko velika i raznolika da ćete tu pronaći odgovor na skoro svako stručno pitanje. Mnogo je lakse započeti frilens karijeru kada su sjajni ljudi oko vas.

                    \n

                    Planirajte unapred

                    \n

                    Sada kada znate u kom ćete pravcu ići, vreme je da počnete da planirate svoju karijeru.

                    \n

                    Postati frilenser je proces. Na početku tog procesa potrebno je da steknete ili dodatno unapredite svoje veštine kojima ćete se istaći u odnosu na konkurenciju. I naravno kako učite i napredujete, moći ćete da prihvatate izazovnije i bolje plaćene poslove.

                    \n

                    Na koja se onda znanja fokusirati? Ukoliko već imate neko predznanje za neki od prethodno navedenih poslova, možete se dalje razvijati u tom pravcu i specijalizovati se za tu oblast.

                    \n

                    S druge strane, ukoliko nemate nikakvo relevantno predznanje, po mom mišljenju bi najlakše bilo započeti sa poslom koji ima kraći period učenja pa da kasnije nadograđujete znanje. Na primer, možete početi kao pisac tekstova za sajtove ili kao implementator jer se ti poslovi brže savladavaju nego poslovi vezani za SEO ili web development. Onda od pisanja sadržaja za sajtove možete proširiti znanje na SEO a od implementatora vremenom postati developer. Samo budite radoznali i ne prestajte da učite.

                    \n

                    Takođe, ukoliko imate specifične talente ili neki hobi kao npr. pisanje ili dizajn, možete da bazirate karijeru oko toga.

                    \n

                    Najlepše je kad neko zarađuje od nečega što inače voli da radi.

                    \n

                    Uz to, valjalo bi da proučite tržište pre nego što se “bacite” na učenje.

                    \n

                    Na primer, sada nije trenutak da se specijalizujete za pisanje sadržaja koji je vezan za putovanja, a pravi je momenat za sticanje veština koje, na bilo koji način, imaju veze sa onlajn prodavnicama i prodajom putem Interneta.

                    \n

                    Ukoliko želite da savladate web development, SEO, web dizajn ili web bezbednost, bitno je da se fokusirate na nove trendove, tehnologije i alate, kako bi vaše veštine bile primenljive i u budućnosti.

                    \n

                    Za različite poslove, uslovi rada mogu biti veoma različiti, pa bi i to valjalo imati na umu. Za neke vrste posla, radno vreme je fleksibilno, dok za druge, morate biti raspoloživi tokom određenog doba dana (ako radite kao korisnička podrška, na primer). I ovo bi trebalo da uzmete u obzir kada birate za koju oblast ćete se specijalizovati.

                    \n

                    Konačno! Vreme je za prvi posao!

                    \n

                    Ako ste zaposleni, bilo bi pametno da prištedite novac pre nego što napustite posao da biste se bavili isključivo frilensingom. Druga pametna opcija bi bila da vam na početku frilensing bude dodatni posao uz ono što već radite kako biste videli da li vam takav način rada odgovara ili ne. Ako postanete uspešni i shvatite da je frilensing nešto što odgovara vašim potrebama, tek tada napustite trenutni posao, ne pre toga.

                    \n

                    Iako neki ljudi profitiraju kada rizikuju, dobro razmislite pre nego što preduzmete korake posle kojih nema nazad.

                    \n

                    Evo nekoliko taktika koje su mi pomogle kada sam pokušavala da dobijem svoj prvi posao kao frilenser:

                    \n

                    Koristite platformu za frilensere – iako nije obavezno, mnogo je lakše doći do prvog posla kada koristite neku platformu namenjenu frilenserima. U to doba, moj izbor je bio Upwork. Svakako, sada postoji i nekoliko drugih platformi pomoću kojih možete brže doći do prvog posla.

                    \n

                    Triput proverite svoju biografiju – pretpostavljam da to nije nešto što bi trebalo da pomenem, ali svejedno ću naglasiti, za svaki slučaj. Ne pravite pravopisne greške u biografiji jer ćete time stvoriti utisak da niste temeljni i da će vam se greške lako potkrasti i dok obavljate svoj posao.

                    \n

                    Predstavite se profesionalno – Uložite trud da svoje profesionalne veštine predstavite u najboljem mogućem svetlu, ali i dalje budite skromni. Nemojte napisati: “Najbolji WordPress developer koji nikada nije napisao loš kod”. Ovo nije zasnovano na dokazima i učiniće da izgledate arogantno. Umesto toga, možete napisati: “Web programer sa 3 godine iskustva i preko 50 zadovoljnih klijenata, specijalizovan za WordPress.” Ova izjava je zasnovana na činjenicama i deluje verodostojno.

                    \n

                    Popunite portfolio – Ako imate bilo kakav prethodni rad (koji je naravno reprezentativan), trebalo bi da ga dodate u portfolio. Naglasak je na reprezentativan. Ako ne, možete da napravite nekoliko sajtova, dizajnirate skice sajtova ili napišete primere tekstova kako biste prikazali svoje veštine. Ovo se ne odnosi na sve poslove, kao što su SEO konsultanti ili korisnička podrška, ali ako imate priliku da napravite portfolio, iskoristite priliku.

                    \n

                    Koristite video materijale – Kratki uvodni video će skrenuti pažnju na vas jer izrada promotivnog video materijala nije nešto što mnogi frilenseri rade. Pomoći će vam da delujete ljudskije i profesionalnije. Za svoje klijente nećete biti samo lista veština i prethodnih iskustava, već stvarna osoba koja zaista ima te veštine i iskustva i koja im pruža određenu uslugu.

                    \n

                    Imajte detaljnu strategiju pri izboru prvog poslodavca – Birajte svog prvog poslodavca mudro. Ne mogu dovoljno da naglasim koliko je ovo važno, pa ću vam dati primer. Kada sam se prijavljivala za svoj prvi posao, uzela sam u obzir sledeće:

                    \n
                      \n
                    • Kako su ovog poslodavca ocenili drugi frilenseri koji su ranije radili za njega
                      • \n
                    • Kako je poslodavac ocenio druge frilensere
                      • \n
                    • Koliko novca je već potrošio na ovoj platformi i da li redovno objavljuje ponude za posao
                      • \n
                    • Broj otvorenih pozicija za ponuđeni posao i broj frilensera koji su se već prijavili. U mom slučaju, posao je imao oko 10 otvorenih radnih mesta, što je povećalo moje šanse za zapošljavanje, čak i u slučaju da je konkurencija velika.
                      • \n
                    \n

                    Kod prvog posla nije bitan samo novac – nemojte biti pohlepni. Ako budete dobro ocenjeni, vaš drugi posao može biti plaćen 2-3 puta više. A vaš treći posao može biti vrednovan i do 5 puta više. To je barem bilo moje iskustvo.

                    \n

                    Vodite računa, odrasla ste osoba

                    \n

                    Individualna odgovornost je ključna kada je u pitanju uspeh u frilensingu. Imate slobodu da izaberete za koga ćete raditi, kakav ćete posao prihvatiti i kako ćete isporučiti dogovoreno. A uz slobodu često dolazi i odgovornost. Oni su poput dve strane iste medalje.

                    \n

                    Nikada ne smete propustiti rok. Ako niste sigurni da ćete uspeti da završite, nemojte ni prihvatati posao ili, umesto toga, za svaki slučaj imajte nekoga vrlo pouzdanog da priskoči u pomoć ako zatreba. Kada propustite rok, vaš klijent gubi novac i ima puno pravo da se naljuti. Ovo će vrlo verovatno uticati na vaše ocene nakon obavljenog posla. A posledično, i na priliku da dobijete sledeći posao i tako dalje. To može pokrenuti silaznu spiralu za vašu karijeru.

                    \n

                    Međutim, svi smo ljudi i mogu se dogoditi nepredvidive stvari. Ako iz nekog razloga niste u mogućnosti da svoj posao obavite u roku, odmah obavestite svog klijenta kako bi imao dovoljno vremena da zaposli nekog drugog.

                    \n

                    Takođe je važno da sve bude jasno definisano unapred, pre nego što prihvatite posao. Obavestite svoje klijente o svojim očekivanjima i uverite se da razumete šta oni očekuju od vas. Na primer, ako treba da pišete tekst za sajt, uverite se da znate dužinu teksta u karakterima ili rečima, pitajte da li treba koristiti neke ključne reči i koliko često, koji stil pisanja preferira vaš klijent itd. A ako ste dizajner, navedite koliko je revizija uključeno u cenu.

                    \n

                    Što je početni dogovor jasniji, to ćete na kraju biti zadovoljniji i vi i vaši klijenti.

                    \n

                    Ako imate fleksibilno radno vreme, ne dozvolite da vas drugi ljudi prekidaju. Ako se vaši prijatelji i porodica ne bi svakodnevno pojavljivali u vašoj kancelariji da ste bankarski službenik, ne bi trebalo da vas prekidaju ni kada radite od kuće. To je isti princip i na vama je da postavite granice i obavestite ih o svom radnom vremenu. To nije njihov zadatak.

                    \n

                    Ovo su neke osnovne smernice koje su mi pomogle u započinjanju karijere frilensera i nadam se da će biti korisne i vama.

                    \n

                    Ne postoji jedinstveni recept i jedna veličina ne odgovara svima kada je reč o putu kojim treba da krenete.

                    \n

                    Važno je samo ostati fokusiran na svoje ciljeve i biti otvoren za nove mogućnosti.

                    \n

                    Ako ste se pitali zašto više nisam frilenser, evo odgovora. Stalnim sagledavanjem različitih mogućnosti, shvatila sam da frilensing nije jedini način da postignem svoje ciljeve. Postoje kompanije koje nude fleksibilno radno vreme i mirno radno okruženje, istovremeno stimulišući profesionalni rast i kreativno razmišljanje.

                    \n

                    Uz to, stekla sam nešto vrlo dragoceno pridruživanjem timu – moje kolege su postale moj sistem podrške i profesionalno i privatno, i to je ono što mi je nedostajalo dok sam bila frilenser.

                    \n

                    Želim vam puno sreće i uspeha u budućnosti, bez obzira na put koji ste odabrali!

                    \n

                    The post How To Become A Freelancer – A Few Things I Learned Before I Gave Up 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, 16 Sep 2020 06:00:13 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:15:\"Tijana Andrejic\";s: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:112:\"WPTavern: Upcoming API Change Will Break Facebook and Instagram oEmbed Links Across the Web Beginning October 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:30:\"https://wptavern.com/?p=104140\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:269:\"https://wptavern.com/upcoming-api-change-will-break-facebook-and-instagram-oembed-links-across-the-web-beginning-october-24?utm_source=rss&utm_medium=rss&utm_campaign=upcoming-api-change-will-break-facebook-and-instagram-oembed-links-across-the-web-beginning-october-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:5294:\"

                    In an extraordinarily inconvenient API change, Facebook and Instagram will be dropping unauthenticated oEmbed support on October 24, breaking content across millions of websites. The change will force users to generate an app ID with a developer account in order to continue embedding links via oEmbed:

                    \n\n\n\n

                    Changes to tokenless access for User Picture and FB/IG OEmbed endpoints: By October 24, 2020, developers must leverage a user, app, or client token when querying Graph API for user profile pictures via UID, FB OEmbeds and IG OEmbeds. Developers should provide a user or app token when querying for profile pictures via a UID or ASID, though client tokens are supported as well. Please visit our changelog for User Picture, Facebook OEmbed and Instagram OEmbed for details on how to start calling these Graph API endpoints today.

                    Facebook for Developers blog
                    \n\n\n\n

                    In 2008, Leah Culver, one of the collaborators on the oEmbed spec, said it was created to be “an open web API standard for fetching embed code based on a URL.” Requiring authentication in order to use oEmbed links seems like a violation of its intended purpose. For more than a decade, oEmbed has made it possible for users to easily share media across websites and social networks, without having to touch any code. It underpins a flourishing, connected landscape of web sharing that opens up new audiences for posts that might otherwise be buried in a social network’s fast-moving timeline.

                    \n\n\n\n

                    In pursuit of a more secure walled garden, Facebook will now require all publishers to obtain developer app credentials in order to embed content that was previously available through simple URLs. Many users will be understandably frustrated when they find they can no longer embed Facebook and Instagram links the way they could in the past. Some will not be motivated to surmount the hurdle of setting up a Facebook app and may resort to posting screenshots or omitting the content altogether. A feature so widely used by non-technical users should not be suddenly locked away behind developer credentials.

                    \n\n\n\n
                    \n

                    Facebook turning off its oEmbed endpoint for FB and Instagram is another brick in the wall around Facebook reality.

                    — ⚫ Your roots are in the infinite (@thejaymo) September 15, 2020
                    \n
                    \n\n\n\n

                    At the time of publishing, none of the original oEmbed spec authors were available for comment regarding Facebook’s API change, but we will update the post as new information becomes available.

                    \n\n\n\n

                    WordPress to Remove Facebook and Instagram oEmbed Providers

                    \n\n\n\n

                    In response to Facebook’s API change, WordPress will be removing Facebook as an oEmbed provider in an upcoming core release. This will break a lot of content – many years’ worth of posts in some instances, and will require users to install a fallback plugin. WordPress plugin developer Ayesh Karunaratne has created a new plugin called oEmbed Plus that brings back support for Facebook and Instagram content embedding. It guides users through the process of setting up Facebook developer app credentials.

                    \n\n\n\n

                    For those who are using the Gutenberg plugin, the Facebook and Instagram blocks have been removed as part of tomorrow’s version 9.0 release. oEmbed links will continue to work until Facebook’s API change goes into effect.

                    \n\n\n\n

                    Moving forward, publishers will need to re-examine how they include social media links within their content. Hulu recently dropped oEmbed support after being available as an oEmbed provider in WordPress for the past 11 years. As major players like Facebook and Instagram follow suit in abandoning open web API’s, the web is growing increasingly more fragmented. Facebook’s upcoming API change will leave millions of broken embeds in its wake, with little pieces of embedded history lost along the way, in instances where website owners are no longer updating their content.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Sep 2020 22:47:12 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:82:\"WPTavern: Digging Into Recipe Card Blocks, WPZOOM’s Solution for Recipe Bloggers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104730\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:201:\"https://wptavern.com/digging-into-recipe-card-blocks-wpzooms-solution-for-recipe-bloggers?utm_source=rss&utm_medium=rss&utm_campaign=digging-into-recipe-card-blocks-wpzooms-solution-for-recipe-bloggers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8785:\"

                    After publishing a post about the new Recipe Block plugin last week, several people were quick to point out that WPZOOM had released a recipe-related block plugin two years ago. Among them, was the plugin author, Pavel Ciorici. I had previously tested the Recipe Card Blocks plugin and thought it fit into that “overly complex” category that is not ideal for the average user who wants to share a recipe here or there. However, it may fit the bill for more dedicated recipe bloggers.

                    \n\n\n\n

                    Over the past few days, I have been testing the plugin and giving it a more in-depth second look.

                    \n\n\n\n

                    My thoughts on the plugin? Not much has changed. I would still recommend the Recipe Block plugin that I covered last week for its simplicity and ease of use. However, this is not a comparison post. There is a lot to like about WPZOOM’s Recipe Card Blocks plugin, and it caters to a similar but somewhat different audience. It is also not a single block plugin and would never be in the official WordPress block directory in its current form. Instead, it is a more fully-featured recipe plugin. Blocks are merely its primary component.

                    \n\n\n\n

                    Recipe Card Blocks is packed full of options and features. If that’s your thing, it might interest you as a potential user. And, the pro version tacks on tons more, such as star ratings, social sharing, and adjustable serving sizes from the front end.

                    \n\n\n\n

                    Recipe Card Blocks

                    \n\n\n\nUsing the Recipe Card block in the editor.\n\n\n\n

                    The primary feature of the plugin is its Recipe Card block, which outputs Schema markup. This could give a search results boost or at least help search engines understand that you have a recipe on the site. For serious recipe bloggers, this is probably one of the most important features this plugin offers.

                    \n\n\n\n

                    The question is really if the plugin’s Recipe Card block is worth using. For users who want options, options, and more options, the plugin offers at least a couple dozen of them for this one block alone. It has a plethora of toggles, inputs, buttons, and other things to customize. The downside is that it can be a bit overwhelming. With so many options, it also means the plugin developers must maintain tighter control over the elements within the block, which can mean less flexibility in other ways.

                    \n\n\n\n

                    The block includes the standard fields that one might expect for a recipe card, such as servings, cook and prep time, ingredients and directions lists, and an image. However, it goes above and beyond by including extra features like:

                    \n\n\n\n
                    • Grouping for ingredients and directions.
                    • Recipe video section.
                    • Notes section.
                    • Pinterest button.
                    • Print button.
                    \n\n\n\n

                    One of my favorite features of the Recipe Card block is that site readers can check off ingredients on the front end. For ingredient-heavy recipes, this can be a time-saver in the kitchen as you gather the things you need to get started.

                    \n\n\n\nTicking items off the ingredients checklist on the front end.\n\n\n\n

                    The default design is beautiful. There is ample spacing between elements. The sections are clearly separate so that there’s no confusion for the reader. It simply looks good.

                    \n\n\n\n

                    However, there are some limitations and issues. At times, the default design is too opinionated, overruling theme styles. It also does not support wide alignment and has a hard limit on its maximum width of 750 pixels. This could make it undesirable with some site designs. Nevertheless, the plugin team made generally smart design decisions. It should work well within most contexts.

                    \n\n\n\n

                    What makes the Recipe Card block tough to use is that end-users must jump back and forth between the post content area and the block options in the right sidebar panel. For example, users must add the course, cuisine, and difficulty text in the sidebar but add the servings, prep time, and cooking time in the content editor.

                    \n\n\n\n

                    Entering items in the ingredients or directions lists also requires more work than one might think. Typically, in visual editors, simply hitting the Enter key should create a new list item. This is not the case with the Recipe Card block. Even tabbing moves users to other controls instead of hopping between items in the list. It is particularly frustrating if you prefer to use the keyboard over the mouse.

                    \n\n\n\n

                    These usability issues keep the plugin from being simply a good plugin rather than a great plugin. User experience issues are not insurmountable. They can be addressed, and I hope the team can continue iterating on and improving the experience.

                    \n\n\n\n

                    I would also like to see the block opened up for the addition of other inner, sub-blocks. Currently, the layout is locked in place. While it may be suitable for some users, locking the block template means that users can neither move the current elements around nor add custom sections that suit their needs. Locking the block means that the plugin author retains control over much of the output, which can sometimes be a good thing — quality control. However, it makes the block less flexible.

                    \n\n\n\n

                    This inflexibility is somewhat mitigated with the plugin’s other blocks. While the Recipe Card block is the primary feature of the plugin, it does break its sub-elements down into individual blocks that users can use to create their own layout by dropping them into a Group or other container-type block. It offers the following extra blocks:

                    \n\n\n\n
                    • Details
                    • Directions
                    • Ingredients
                    • Jump to Recipe
                    • Print Recipe
                    • Nutrition
                    \n\n\n\nSeparate Nutrition block in the editor.\n\n\n\n

                    With a little ingenuity and perhaps a plugin like Block Pattern Builder (a plugin that I maintain), end-users could create custom, reusable recipe layouts.

                    \n\n\n\n

                    The Big Issue

                    \n\n\n\n

                    The thing I dislike about the plugin the most is that it outputs a “RECIPE CARD PLUGIN BY WPZOOM” message in the front-end post content output. This message is hidden in the editor view. Plugin users can see it only on the front end. For the average user, there is no easy way to remove this message without upgrading to the pro version of the plugin, which costs at least $69.

                    \n\n\n\n

                    Frankly, commercializing the removal of a credit link a shady business practice. It is a tactic that preys on those who do not know how to code. Sorry, I got no love to give for this.

                    \n\n\n\n

                    This was frowned up 10-15 years ago when theme authors were doing it. It should be frowned upon today when plugin authors do the same.

                    \n\n\n\n

                    Upsell custom branding. Upsell a 100 other things that add value. Don’t upsell removing a credit link that you are outputting in the user’s post content. This one problem with the plugin paints a stain over everything else that is good about it.

                    \n\n\n\n

                    Final Thoughts

                    \n\n\n\n

                    I do not want to end on a negative note. Recipe Card Blocks is a useful plugin for those who want more than a basic recipe block. It is almost more of a recipe management tool but not quite.

                    \n\n\n\n

                    I would have taken a different route with some of the development based on the publicly-known plans for the plugin. For example, I could see creating a recipe custom post type separate from the block system. Then, allow users to insert these “recipe posts” into the block editor. With plans to add custom taxonomies to the plugin, it makes sense to keep the whole data layer separate.

                    \n\n\n\n

                    It seems the plugin is torn between being a recipe block and a full recipe management plugin. I would like to see it fully commit to the latter because that seems to be the direction it is heading. However, from an architectural standpoint, it will need work to get there. It can still be done, despite two years of legacy code, and it has the opportunity to carve out its own space in the ecosystem.

                    \n\n\n\n

                    If the plugin’s development team would remove the upsell of the credit link, I would absolutely recommend this plugin to people who want to run a serious, full-time recipe blog. It has those extra features like a nutrition label, a print button, and Schema markup that give it an edge over some of the competition. For users who simply want to add a recipe on their blog from time to time, it is overkill.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Sep 2020 21:25:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:42:\"Akismet: Introducing updated Akismet plans\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"http://blog.akismet.com/?p=2086\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:70:\"https://blog.akismet.com/2020/09/15/introducing-updated-akismet-plans/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3109:\"

                    Since Akismet launched nearly 15 years ago, it has blocked 500 billion spam comments. We’re proud to have saved you countless hours of moderation time, reduced frustration for millions of people, and helped make the web a more beautiful place.

                    \n

                    Akismet is the most powerful solution on the market for stopping spam, but spammers are continually inventing new ways to get past our filters. Adding new spam detection techniques will ensure we keep Akismet one step ahead of bad actors, but it will require additional investment. We don’t take changing prices lightly. In fact, we haven’t changed the price of the entry-level plan since it was introduced in 2005.

                    \n

                    For commercial sites, the price of Akismet will be better aligned to API usage. This means that as you use Akismet more, the cost per API call will decrease.

                    \n

                    For those that use Akismet on your personal sites — we’re 100% committed to offer Akismet at a price you can afford. Spam is a menace to the internet and we feel that everyone should have the ability to stop spam on their websites. Even if you’re not making money from your site, we want you to have the best spam filter available. We will continue to provide the option to pay what you can, and we thank you for helping to contribute to this project.

                    \n

                    To our current customers, you don’t need to do anything now. Your plan will remain at its original price and API limits at least into 2021. If you’d like to switch plans or start a new account, your plan will start at the new price.

                    \n

                    \n

                    What’s different?

                    \n

                    Personal

                    \n

                    No changes. For sites that don’t sell anything, advertise, or have affiliate links, Akismet is available for whatever amount you are able to pay.

                    \n

                    Plus

                    \n

                    Akismet will block spam on one site for up to 10,000 API calls and provide priority support for $8.33 per month billed yearly. The price for monthly billing is $10. That’s equal to two months free for selecting yearly billing.

                    \n

                    Enterprise

                    \n

                    We’re decreasing the price of our Enterprise plan! Yearly plans will now be $41.66 per month, with the total yearly cost at $500 instead of $550. For monthly billing, the price is staying the same at $50 per month. For enterprise plans, Akismet will block spam on multiple sites for up to 60,000 API calls per month, as well as provide priority support on all sites.

                    \n

                    Enterprise Plus

                    \n

                    For our largest customers, we’re happy to provide discounted pricing and dedicated support through this new plan. If your sites have more than 60,000 API calls per month, contact us and we’ll be happy to set you up.

                    \n

                    Thank you for your continued support of Akismet. If you have questions specifically related to your own Akismet account or API key, then please visit our Support page.

                    \n

                     

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 15 Sep 2020 15:59: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:10:\"Josh Smith\";s: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:83:\"WPTavern: Podcasting During the Pandemic: Castos Sees 300% Growth in New Podcasters\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=102111\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:207:\"https://wptavern.com/podcasting-during-the-pandemic-castos-sees-300-growth-in-new-podcasters?utm_source=rss&utm_medium=rss&utm_campaign=podcasting-during-the-pandemic-castos-sees-300-growth-in-new-podcasters\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6841:\"“My Podcast Set I” by brainblogger is licensed with CC BY 2.0. \n\n\n\n

                    Podcasting, like many other industries during the pandemic, is seeing a strong shift over the past six months, which has resulted in more shows and fewer listeners. While some avid podcast fans have taken solace in listening to their favorite shows to stay connected, many listeners who previously had podcasts built into their routines have turned to other forms of media consumption in the absence of a daily commute.

                    \n\n\n\n

                    In April, global podcast listening was up 42% (and 53% in Europe) as lockdowns began in the U.S. and other parts of the world. Although listening in the U.S. went down 20%, certain verticals remained strong, such as true crime, music interviews, science, medicine, religion and spirituality, and self-improvement.

                    \n\n\n\n
                    \n

                    worst part of still quarantining is the fact that I don’t drive anywhere so im super behind on my podcasts

                    — Brad Parbs (@bradparbs) September 3, 2020
                    \n
                    \n\n\n\n

                    Prior to the pandemic, the podcasting industry was experiencing a boom, with experts projecting marketers to spend over $1 billion in advertising by 2021. The pandemic has thrown a wrench into the industry’s growth. In the months of continued isolation and social distancing, E-marketer recorded its first contraction in time spent listening since it began tracking in 2015 but estimates a rebound in the coming years.

                    \n\n\n\nSource: eMarketer, June 2020 (https://www.emarketer.com/content/time-spent-with-podcasts-will-dip-amid-pandemic-should-rebound-by-2022?ecid=NL1001)\n\n\n\n

                    The pandemic may have temporarily stunted the growth of listeners, but the team at Castos is witnessing a new trend emerging: individual creators and businesses are finding the time and inspiration for firing up new shows. From April until now, the podcast hosting company has seen a 300% increase in new trials, and a 102% increase in MRR over last two years. Castos currently has nearly 2,000 paying customers.

                    \n\n\n\n

                    The company started in 2017 after non-technical founder Craig Hewitt acquired the Seriously Simple Podcasting plugin from its original creator, Hugh Lashborooke. Hewitt expanded the platform to allow both WordPress and non-WordPress users to create podcasts, and has grown the business to support seven remote, full-time employees. He attributes most of the industry’s fresh infusion of new shows to companies that are exploring new ways of getting into customers’ homes.

                    \n\n\n\n

                    “Many brands are finding that traditional marketing efforts are falling short in these turbulent times, but great content that serves a specific audience always has an impact,” Hewitt said. “Many companies are pivoting from more conventional paid acquisition approaches to building stronger and longer lasting relationships with their audiences through podcasting.”

                    \n\n\n\n

                    Hewitt said he expects the trend to continue after the pandemic subsides. Many of the companies Castos works with have reported that podcasting is likely to become a core part of their marketing efforts for the long haul, in both B2B and B2C environments.

                    \n\n\n\n

                    “Like the move to remote work many companies are seeing that podcasting isn’t hard to do, and provides great returns for them in terms of branding and as a top of funnel customer acquisition strategy,” Hewitt said. “Whether in the midst of Coronavirus or afterwards this will continue to be true and the momentum that podcasting has gained should continue.”

                    \n\n\n\n

                    Approximately 70% of Castos’ hosting customers are using the Seriously Simple Podcasting plugin. The hosting platform is unique in the podcasting market in that it automates YouTube Republishing, transcriptions, and Headliner integration, while allowing users to manage it all via WordPress. Castos recently hired Matt Medeiros, an experienced podcaster and YouTube creator, to help new podcasters keep pushing with their shows and convert into longterm customers. He shares Hewitt’s optimistic outlook on the future of the industry.

                    \n\n\n\n

                    “There were early reports that podcast download stats dropped in tandem with listener commute times, but I think that opened up opportunity for creators to really capture their most loyal audiences,” Medeiros said.

                    \n\n\n\n

                    “The other side of that coin are the businesses that needed to stay top of mind with the customers while their doors were closed. Spinning up a podcast is a perfect way to do that. Podcasts come in all shapes and sizes, so building one that’s tailored to your customers is what really matters and will survive through our post-pandemic ‘new normal.\'”

                    \n\n\n\n

                    Portability is the common denominator for podcasts – people are listening from their desktops, mobile devices, and smart speakers, using a variety of different apps. But audiences vary in their appetites for staying informed, educated, and entertained through the podcasting medium. Medeiros advises both new and established podcasters to find out what kind of show their customers want them to produce.

                    \n\n\n\n

                    “Podcasts don’t have to be cookie cutter,” Medeiros said. “If you spend time getting feedback from your customers or audience, you want to tailor the show around that. Do they like 15 minute news highlights or 3 hour 1-on-1 interviews? Do they want hard news or laugh out loud entertainment? What’s in it for them as a listener? What’s in it for you as a creator?

                    \n\n\n\n

                    “At the end of the day, the biggest opportunity for podcasting is that it opens the door to having your favorite creators and fans in the same room every time you publish an episode. It’s a chance to (literally) have a conversation and build trust through creative storytelling – your brand’s digital handshake.” 

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Sep 2020 01:44:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:85:\"WPTavern: Plugin Authors Can Opt Into Email Confirmation for WordPress Plugin 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:30:\"https://wptavern.com/?p=104653\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:215:\"https://wptavern.com/plugin-authors-can-opt-into-email-confirmation-for-wordpress-plugin-updates?utm_source=rss&utm_medium=rss&utm_campaign=plugin-authors-can-opt-into-email-confirmation-for-wordpress-plugin-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:5149:\"

                    Overnight, the Meta Team for WordPress.org flipped the switch for a new plugin author feature in the official directory. It allows plugin authors to opt into confirming plugin updates via email. Release confirmations will strengthen security and make sure any updates sent in are intentional.

                    \n\n\n\n

                    Dion Hulse opened the original ticket six weeks ago with a detailed proposal and set of questions. WordPress 5.5 introduced automatic updates for plugin and theme authors. While auto-updates are completely opt-in for end-users, Hulse wanted to make sure that WordPress.org was on top of any potential disasters that may arise from the new system, such as accidental or even malicious plugin releases.

                    \n\n\n\n

                    “I’d like to propose that we add an extra optional step into the release flow for plugins, not intended on adding friction, but intending to ensure that plugin releases only get made when they’re intended to,” he wrote. “A simple Email confirmation.”

                    \n\n\n\n

                    At the moment, release confirmation via email is merely an opt-in feature that all plugin authors can take advantage of. However, the original proposal required it for high-usage plugins — there was never a definitive minimum install count that constituted “high usage” in the ticket.

                    \n\n\n\n

                    The general agreement on how this feature should work seems to be:

                    \n\n\n\n
                    • Opt-in for all plugin authors now.
                    • Forced opt-in and no opt-out for high-usage plugins soon.
                    • Opt-out for all other plugins in the future.
                    \n\n\n\n

                    For larger plugins with multiple committers, there was some discussion on requiring confirmation from a separate committer who did not push the code live. This would essentially require two people to confirm that a plugin update is valid. This could potentially add to the friction that Hulse wanted to avoid in the original proposal. However, some friction for plugins with millions of installs might not always be such a bad thing. These plugins serve a massive user base and can damage WordPress’s reputation if a malicious actor gained commit access somehow. Having two people confirm an update is a good kind of friction in some cases.

                    \n\n\n\n

                    However, requiring two-person confirmation is a more nuanced discussion that will need to happen. For example, Chris Christoff brought up examples in the ticket of not being able to send updates for plugins with two committers when one is on vacation or when the committers live in different time zones. Perhaps this will be an opt-in feature for plugin companies that choose to go this route in the future, depending on what fits their release flow best.

                    \n\n\n\n

                    On the whole, the current implementation is a good starting position that will allow the community to iron out further details. This is about making WordPress more secure. If there is an extra step involved in publishing a code update, plugin authors should be on board with the process. Verifying the validity of a release sounds like a common-sense security feature. I would welcome WordPress.org making this a hard requirement — neither opt-in nor opt-out — in the long run after the feature has gone through a few rounds of real-world testing.

                    \n\n\n\n

                    Theme developers do not have access to this feature at this time. However, the theme authors do not have access to SVN and must submit updates via a ZIP file. It is a much more manual process and should not be subjected to the same number of potential mishaps as plugin updates.

                    \n\n\n\n

                    How Plugin Authors Can Enable Release Confirmation Emails

                    \n\n\n\nEnable email release confirmation form for plugin authors.\n\n\n\n

                    Plugin authors should now see a new administration option for each of their projects listed in the official plugin directory. The Danger Zone section of the Advanced View tab should display a new sub-section for enabling release confirmation emails. From there, authors merely need to click a button to turn them on.

                    \n\n\n\n

                    It is important to note that, once enabled, release confirmation emails cannot be disabled from the same screen. Plugin authors are presented with the following notice before enabling the feature:

                    \n\n\n\n

                    Warning: Enabling release confirmations is intended to be a permanent action. There is no way to disable this without contacting the plugins team.

                    \n\n\n\n

                    Do not let the warning put you off if you are a plugin author. This is a good thing. Go ahead and enable it on at least one plugin if you want to test it first. I already have done so for one of my plugins. It is a simple process and helps add one additional layer of security over your 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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 14 Sep 2020 20:34:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:48:\"BuddyPress: BuddyPress 6.3.0 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:32:\"https://buddypress.org/?p=313809\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://buddypress.org/2020/09/buddypress-6-3-0/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1260:\"

                    Immediately available is BuddyPress 6.3.0. This maintenance release:

                    \n\n\n\n
                    • fixes 1 bug related to the 6.2.0 release,
                    • fixes 2 bug related to the 6.0.0 release,
                    • is a recommended upgrade for all BuddyPress installations.
                    \n\n\n\n

                    For details on the changes, please read the 6.3.0 release notes.

                    \n\n\n\n

                    Update to BuddyPress 6.3.0 today in your WordPress Dashboard, or by downloading from the WordPress.org plugin repository.

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

                    Many thanks to 6.3.0 contributors

                    \n\n\n\n

                     Paul Gibbs (DJPaul), scipi, r-a-y, David Cavins (dcavins), webmasterfreya,  Mathieu Viet (imath).

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 14 Sep 2020 17:26: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:12:\"Mathieu Viet\";s: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:90:\"WPTavern: WordPress Themes Directory Adds New “Delist” Status for Non-Compliant Themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104585\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:213:\"https://wptavern.com/wordpress-themes-directory-adds-new-delist-status-for-non-compliant-themes?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-themes-directory-adds-new-delist-status-for-non-compliant-themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4182:\"

                    In August, following the suspension of the popular Astra theme, WordPress Meta contributors opened a ticket to add a new “delisting” status for non-compliant themes. Astra’s infraction, breaking the directory’s ban on affiliate links, put more than a million users at risk of not getting theme updates just as WordPress 5.5 was on deck for release. This week the team committed a patch for a delist status that will temporarily hide a theme from search, while still making it available directly. Alex Shiels outlined how the new status will work:

                    \n\n\n\n
                    • Delist is only available from a published state.
                    • Relist will set the status back to publish.
                    • Delisted themes are excluded from site search.
                    \n\n\n\n

                    While a full suspension may seem like the best retributive action when theme authors violate directory guidelines, the necessity for users to be able to continue to get updates outweighs throwing the book at the author, especially for a first-time offense. A delisting policy is more restorative in that it seeks to maintain the connection that users have with the theme’s author instead of merely imposing a penalty that might ultimately have a negative impact on everyone involved.

                    \n\n\n\n

                    In the past, the Themes Team has been limited on available actions for responding to violations. Ionut Neagu, CEO of ThemeIsle, had his company’s popular Zerif Lite theme suspended from the directory in 2016 for a five-month period that left 300,000+ users without maintenance and security updates. It also resulted in a 63% decline in the company’s revenue for that theme, since ThemeIsle was using WordPress.org as the primary channel for distribution.

                    \n\n\n\n

                    Neagu remarked on how the new “delist” status provides a less severe transition back into the directory for popular themes:

                    \n\n\n\n

                    The practice of delisting is something that’s already been done by other companies in similar situations. For instance, delisting is what Google does all the time when they find a website that doesn’t comply. Then, the website is allowed to come back and appear on the ranking pages again when the issues are fixed.

                    In the end, I think this is a move in the right direction and an improvement to the process of what happens with a problematic theme.

                    \n\n\n\n

                    Despite the controversial decision that slashed ThemeIsle’s revenue from $120k/month to $45k/month in 2017, the company continued to support the theme, as well as new products, with WordPress.org as the main place to find them. Neagu reported that when the theme was reinstated, its revenue continued to be hard hit. It lost momentum and was unable to ride the wave of its initial success. Astra faired much better in the aftermath of its violation, given its short-lived suspension.

                    \n\n\n\n

                    WordPress Themes Team member Alexandru Cosmin requested the ticket for adding the delisting status receive prompt attention, as the team is set to introduce some new policies and requirements that are tied to it. The patch was committed and then reverted temporarily to review how it impacted theme trac tickets, but the bugs appear to be unrelated to the patch.

                    \n\n\n\n

                    The volunteer Themes Team has essentially been the de facto guardians of the WordPress.org marketplace that sends millions of dollars to theme authors, and they perform a great service to the community. But in the interest of supporting and accelerating the growth of the WordPress ecosystem, the team needs to adopt policies that create a more restorative path for violators, instead of obstructing the growth of products where issues have been quickly resolved.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 11 Sep 2020 22:59:30 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:95:\"WPTavern: Addressing the Theme Design Problem With Gutenberg’s New Block-Based Widgets System\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104569\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:229:\"https://wptavern.com/addressing-the-theme-design-problem-with-gutenbergs-new-block-based-widgets-system?utm_source=rss&utm_medium=rss&utm_campaign=addressing-the-theme-design-problem-with-gutenbergs-new-block-based-widgets-system\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5655:\"

                    I could hardly sleep last night. Once in a blue moon, I have an idea I want to try out. While my day job as a writer means I spend far less time breaking sites through the rigorous trials and errors of building plugins and themes, some problems bug me with WordPress, the sort that keeps me from dozing into restful and peaceful dreams.

                    \n\n\n\n

                    Last week, Gutenberg 8.9 dropped the experimental flag from its block-based widgets system. Overall, it was a solid first outing for a feature that should land in WordPress 5.6 this December. However, the largest problem centered on how theme authors would be able to style widgets in traditional fashion. Because actual widgets are being phased out and replaced with blocks, theme authors will no longer have access to the standard widget and widget title classes. This is problematic because there is no predictable way to style all widgets of a particular sidebar to look the same.

                    \n\n\n\n

                    The classic example is of the boxed widget design. Many themes, such as the popular Colibri, employ such a design for their sidebars as shown in the following screenshot.

                    \n\n\n\nBoxed widget design in right sidebar of Colibri theme.\n\n\n\n

                    In its current state, there is no reliable way for theme authors to create such a sidebar design via the block-based widgets system. Because there is no way to exert any sort of control over the structure of whatever content users will drop into a sidebar, it would be easy to look at this situation and think that theme designers are losing control.

                    \n\n\n\n

                    Based on a recent GitHub ticket and a related Slack discussion from earlier this week, it does not appear that the Gutenberg development team intends to create parity between the old and new widgets systems, at least as far as theme design is concerned.

                    \n\n\n\n

                    It bears repeating. I am a fervent supporter of handing over this type of ultimate control to the user. However, we need to balance that with helping them to make smart choices.

                    \n\n\n\n

                    Theme authors must begin thinking about how this impacts the work they do and come up with creative solutions for sidebars, widgets, and other areas that will be affected by full-site editing in the future.

                    \n\n\n\n

                    A Potential Solution

                    \n\n\n\n

                    That thing that kept me up last night was an idea of combining block patterns, one of my favorite features, with widgets. The trouble was that the block-based widgets system does not currently support block patterns. And, until a quick discussion with Mark Uraine, one of Gutenberg’s designers, on a GitHub ticket, the idea did not seem to even be on the table.

                    \n\n\n\n

                    For theme authors, the traditional sidebar and widget system of the past was nothing more than a pattern. WordPress provided theme devs with the ability to set a wrapping HTML element for the entire widget and the widget title. It was a rigid and inflexible system, but it was a reliable standard.

                    \n\n\n\n

                    Block-based widgets are the complete opposite. They are essentially a free-for-all where users can drop arbitrary content into a “block area.”

                    \n\n\n\n

                    What happens when we combine the structure of patterns with the flexibility of blocks inside of sidebars?

                    \n\n\n\n

                    That was the idea that got me out of bed and behind the computer screen early this morning after my restless night. It was such a simple concept. Theme authors could provide a “widget” pattern to their end-users. This would provide users with a choice between what the theme author thinks best and forging their own path — the best of both worlds.

                    \n\n\n\nSimple example of recreating a boxed “widget” pattern.\n\n\n\n

                    And, here is where the beauty of the block system really comes in. Theme authors can create any number of patterns. This provides even more options for users.

                    \n\n\n\n

                    Regardless of whether the Gutenberg plugin currently supports patterns for the block-based widget system, the idea was simple to test. In a sidebar on the new widgets screen, I merely needed to add a new Group block with the widget class. Then, I added an H3 Heading block with the widget__title class. Those classes may even be unnecessary in the context of patterns unless theme authors want to directly target them. Outside of the custom classes, I added a simple background to the Group block and changed the text color of the Heading. I also inserted an empty paragraph where the user’s custom content would go.

                    \n\n\n\n

                    Afterward, it was a simple matter of testing it with various blocks.

                    \n\n\n\nFaux block pattern in the widgets block editor.\n\n\n\n

                    I would love to know what theme authors and the Gutenberg team think of the idea. I think it has some merit while soothing some of the transitional pains between traditional widgets and block-based widgets.

                    \n\n\n\n

                    The biggest issue I see is the discoverability aspect. Will end-users know these “widget/block patterns” exist if theme authors went this route?

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 11 Sep 2020 18:56: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:14:\"Justin Tadlock\";s: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:72:\"WPTavern: AMP Plugin 2.0 Adds Onboarding Wizard and Expanded Reader Mode\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104487\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:189:\"https://wptavern.com/amp-plugin-2-0-adds-onboarding-wizard-and-expanded-reader-mode?utm_source=rss&utm_medium=rss&utm_campaign=amp-plugin-2-0-adds-onboarding-wizard-and-expanded-reader-mode\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4008:\"

                    The official AMP plugin for WordPress recently crossed the 2.0 milestone, a major release that closed 141 issues and merged 174 pull requests. The release was originally planned for v1.6 but due to the number of major changes the team decided to bump it to 2.0.

                    \n\n\n\n

                    One of the most significant updates in this release is the expansion of the Reader Mode. The plugin has a lot of AMP-specific terminology associated with it and unless you are working with it every day, it’s easy to get confused by the different modes. Standard Mode is an AMP-first site where all URLs are presented as AMP pages. Transitional Mode uses one theme but canonical non-AMP URLs may offer a separate AMP version. Reader Mode uses two themes with the active one for canonical non-AMP URLs and a separate “Reader” theme for AMP URLs.

                    \n\n\n\n

                    Version 2.0 introduces a new AMP Customizer for customizing the Reader theme. It loads with a mobile view and does not support widgets or homepage settings, as they are not applicable for the AMP version. The AMP Customizer makes it easy for site owners to make tweaks and changes that will only apply to the AMP version of URLs.

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

                    The Reader Mode is especially useful for sites that are not using AMP-compatible themes. Google engineer Weston Ruter described the expanded Reader Mode as follows:

                    \n\n\n\n

                    Reader mode now allows for any AMP-compatible theme to be used to serve AMP pages, rather than just the legacy post templates. This allows for long-requested features including nav menus, logos, commenting, and template design variations. It also makes it possible to serve all URLs of a Reader-mode site in AMP, as opposed to just singular posts. 

                    \n\n\n\n

                    One major usability update in version 2.0 is the addition of an onboarding wizard and revamped Settings screen that guides users through the different templating modes when configuring the plugin. Users who are routed to Reader Mode will be presented with a selection of themes for serving AMP pages and the wizard will handle installation. The final step of the configuration process allows users to review their choices in a preview screen.

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

                    Given the complexity of the AMP plugin and its many configuration options, the onboarding wizard was a critical addition if the plugin is going to grow past 500,000 active installs to reach a larger number of non-technical users.

                    \n\n\n\n

                    Another notable update in this release includes a feature called “Plugin Suppression” that allows administrators to turn certain plugins off for AMP pages if they are causing validation errors. It also introduces mobile redirection for Transitional/Reader mode sites where AMP is intended to be the mobile version.

                    \n\n\n\n

                    AMP is still far from a plug-and-play experience for WordPress users but the plugin does a lot of the heavy lifting and is evolving towards becoming more approachable for non-technical users. To that end, the AMP plugin team just announced a new video series that will focus on success with WordPress as a content creator, as well as performance and usability.

                    \n\n\n\n

                    “We are crafting it with an audience in mind that covers both technical and non-technical users,” Google Developer Advocate Alberto Medina said. “The 2.0 version of the plugin makes an emphasis on providing options for users that are non technical but still want to take advantage of AMP to bring great page experiences to their users.”

                    \n\n\n\n

                    The series will launch next week on Google’s AMP YouTube channel. Medina is also working on another series geared towards content creators that will cover topics like Web Stories in the first episodes.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 10 Sep 2020 22:44:54 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:68:\"WPTavern: Start a Recipe Blog With the Recipe Block WordPress 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:30:\"https://wptavern.com/?p=104474\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:181:\"https://wptavern.com/start-a-recipe-blog-with-the-recipe-block-wordpress-plugin?utm_source=rss&utm_medium=rss&utm_campaign=start-a-recipe-blog-with-the-recipe-block-wordpress-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:4468:\"

                    “Organize your quarantine-inspired baking blog with a ‘Recipe’ block!” read the opening description of Kelly Choyce-Dwan’s new plugin, Recipe Block. That was enough to pique my interest. I love food. I love baking — mostly pizza and bread. Food-related plugins and themes almost inspire me to spin up a recipe blog of my own. Almost.

                    \n\n\n\n

                    At least with plugins like this, I can dream of building that site. Or, I can vicariously live through those who have the inclination, passion, and drive to post recipes regularly.

                    \n\n\n\n

                    For far too long, building a recipe blog has required specialized themes or overly complex plugins. I have been eagerly awaiting a simple recipe block because I have known since Day 1 of Gutenberg’s launch that it would be well-suited to such a feature. Choyce-Dwan’s Recipe Block plugin makes the complex simple and brings recipe-blogging to any WordPress user.

                    \n\n\n\n

                    Using the Recipe Block

                    \n\n\n\n
                    • Recipe Block
                    • Cover + Recipe Block
                    • EditorPlus + Recipe Block
                    \n\n\n\n

                    Within a couple of minutes of installing and activating the plugin, I had a quick pizza recipe set up and published on my test install. It worked well with the several themes I tested it against. I did make a couple of spacing adjustments via CSS for my personal theme, but that is not uncommon for plugins that have front-end output.

                    \n\n\n\n

                    Technically, the plugin adds four blocks:

                    \n\n\n\n
                    • Recipe: Primary block that houses other blocks.
                    • Information: Sub-block for adding servings, time, and difficulty level.
                    • Ingredients: Sub-block for listing ingredients.
                    • Directions: Sub-block for listing directions.
                    \n\n\n\n

                    The Recipe block also makes use of the core Image and Heading blocks. It is as simple to use as nearly any other block. Add the block to a post via the inserter or the /recipe slash command. From there, end-users can customize the output to their heart’s content.

                    \n\n\n\n

                    Because the Recipe block itself lacks any custom colors or other stylistic options outside of wide and full-width alignment, the easiest way to spruce up the design a bit is to drop it into a Cover or Group block. Doing so provides a wider range of design options. For those users who need even more design control, Munir Kamal’s EditorPlus plugin is a nice addition when wrapping it with the Group block.

                    \n\n\n\n

                    One of the best things about the Recipe block is that it is not locked. End-users can move sub-blocks around to their liking. It even allows nesting of other blocks. Not everyone creates the exact same type of recipe cards, so it makes sense to have some extra customizability.

                    \n\n\n\n

                    The block is also flexible enough for recipes that have multiple ingredients and directions lists. So, that pie and pie crust recipe you want to share? No problem. You can split the ingredients and directions so that your readers are not accidentally dropping lard into the pie filling.

                    \n\n\n\n

                    Missing Features

                    \n\n\n\n

                    The Recipe Block plugin is by no means ideal for every situation. Some features could make it stand out a bit more. For the most part, I wanted a few additional styling options.

                    \n\n\n\n

                    Choyce-Dwan makes it clear in the plugin description that it does not support Schema or structured content. That would make a nice block option for those who want to enable it.

                    \n\n\n\n

                    I would like to be able to change the text and background color of the main Recipe block. However, this is easily done by wrapping it with the core Group block. Ultimately, I would like to have the option to add some different styles to it, such as a custom border. Such a feature should probably land in core WordPress first so that there is a standard.

                    \n\n\n\n

                    It would be nice to allow users to change the font size and colors within the Information, Ingredients, and Directions blocks similar to how the core Paragraph block works. Again, you can wrap this with the Group block and at least set the colors at a higher level.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 10 Sep 2020 21:00: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:14:\"Justin Tadlock\";s: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:91:\"WPTavern: Deque Systems to Host Axe-Con Virtual Accessibility Conference, March 10-11, 2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104433\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:223:\"https://wptavern.com/deque-systems-to-host-axe-con-virtual-accessibility-conference-march-10-11-2021?utm_source=rss&utm_medium=rss&utm_campaign=deque-systems-to-host-axe-con-virtual-accessibility-conference-march-10-11-2021\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3263:\"

                    Deque Systems, a widely respected accessibility firm that has contributed to setting up automated accessibility testing for WordPress core, will be hosting a new “Axe-con” virtual conference focusing on digital accessibility. Axe-con is named for the company’s axe-core project, an open source library and accessibility testing engine that can be customized to integrate with all modern browsers and testing frameworks. It’s happening March 10-11th, 2021, and tickets are free.

                    \n\n\n\n

                    Learning how to create accessible experiences for the web is challenging. Axe-con will bring together experts from around the world who can accelerate that journey for developers, designers, business owners, accessibility professionals, and anyone involved in the team effort required to make digital experiences accessible. The event will feature multiple tracks with a variety of topics, including sustainable accessibility, compliance, best practices, and case studies from organizations leading large-scale accessibility efforts.

                    \n\n\n\n

                    For those interested in obtaining or maintaining IAAP (International Association of Accessibility Professionals) certification, attendance at Axe-con sessions can count towards IAAP continuing education (CE) credits.

                    \n\n\n\n

                    The event will also include a hackathon where attendees will have the opportunity to network with each other while coding and collaborating on accessibility projects. A few examples include testing open source component libraries and logging issues, building new axe integrations, and working on personal projects.

                    \n\n\n\n

                    Deque Systems is hosting this new conference the same week as the CSUN Assistive Technology Conference. The company is has attended and sponsored the event in the past but sees the need for a conference focused more on building accessible digital experiences. Deque could no longer meet this need by tackling those topics in a single sponsorship room limited to 100 people. When its CSUN 2020 sessions were forced to go virtual, the team discovered that thousands were able to join in on topics more related to digital accessibility.

                    \n\n\n\n

                    Organizers anticipate that attendees will join both CSUN and axe-con in 2021. By scheduling the events in the same week, they are hoping to help attendees make more efficient use of their time that would normally be set aside for traveling to an in-person conference.

                    \n\n\n\n

                    Registration is open and last week organizers reported there were already more than 2,000 people signed up. The Call for Papers will be open until 8:00PM ET Friday, October 23rd, 2020, and speakers will be notified by November 23. Talks will be broadcast in the Eastern timezone but international speakers are welcome.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 10 Sep 2020 05:23:40 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:38;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"WPTavern: Exploring Seedlet, Automattic’s Block-First WordPress Theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104405\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:179:\"https://wptavern.com/exploring-seedlet-automattics-block-first-wordpress-theme?utm_source=rss&utm_medium=rss&utm_campaign=exploring-seedlet-automattics-block-first-wordpress-theme\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5580:\"\n\n\n\n

                    On August 26, Automattic launched a new theme titled Seedlet that focused on integrating with the WordPress block editor. A few days later, it was also live in the WordPress.org theme directory. The theme development team wanted to produce a theme that would be in a good position to transition to full-site editing later this year as WordPress 5.6 lands.

                    \n\n\n\n

                    Seedlet makes wide use of features that integrate with the block editor. It does so in what is the simplest of ways, which is a testament to how much easier theme development is becoming in the dawn of the block-based themes era. The theme makes liberal use of theme-supported features like custom font sizes, colors, and gradients. It takes its integration an extra step by registering block styles and patterns.

                    \n\n\n\n

                    Seedlet almost feels like a skin around the block editor. It is a prime example of the future that we’re hurtling toward, which will mean less focus on code and more focus on design configuration. Themes will not be themes in the traditional sense. I use the term “skin” because it harkens to various systems in days gone by where designers simply added CSS to skin a site. WordPress themes will always be a bit more complex than a simple stylesheet but not much more so. We will be getting back to the basics of CSS and HTML.

                    \n\n\n\n

                    That is what I see when I look through the Seedlet theme’s code. While it still has copious PHP, there is an unmistakable structure that clearly says that that theme development is changing — and here is what it looks like as we transition.

                    \n\n\n\n

                    I have seen many themes that developers have built to work with the block editor. However, I have seen only a few that have taken a block-editor-first approach. It is almost subtle, and unless you have been neck-deep into theme development for years, you may miss it. Automattic’s theme team is riding the winds of change. Theme authors who want to ride along should pay attention to where this project goes in the coming months.

                    \n\n\n\n

                    The one thing I do not understand is why Automattic did not choose to add the “Block Editor Styles” tag to the theme. It clearly adds such styles. This is a missed opportunity to help users find themes compatible with the block editor.

                    \n\n\n\n

                    The theme will not suit everyone’s taste. It is a basic blogging theme at its core. However, its wide-open canvas makes it suitable for a variety of sites. The theme’s typography is on point, creating a comfortable reading pace for longer-form work. There is a lot to like about the theme, but I am primarily interested in what the development team has built for the block editor.

                    \n\n\n\n

                    Kjell Reigstad, the primary designer on the theme, also announced the team is working on a completely block-based version called Seedlet Blocks. The current plan is to continue iterating on it and launching it as a separate, standalone theme in the future.

                    \n\n\n\n

                    Experimenting With Block Patterns

                    \n\n\n\n

                    While Seedlet includes only three block patterns, they immediately stood out to me. The patterns are not overly complex, but they are unique designs that make use of core blocks with a mixture of the theme’s presets, such as custom gradients and block styles.

                    \n\n\n\n

                    The “Group with Split Background” pattern uses a Group block with the theme’s preset diagonal gradient to create a background for an Image block. It is not a particularly groundbreaking design. However, the beauty is in the simplicity. It shows that theme authors can create interesting designs without adding extra CSS code.

                    \n\n\n\nGroup with Split Background pattern in the editor.\n\n\n\n

                    The theme’s “Group with Image Overlap” pattern kicks it up a notch in complexity. Starting with the same concept of a Group block with another custom gradient preset, it throws in a Columns block. In the left column, users can add two images, stacked. In the right column, users can add one image. The end result is a custom layout — primarily because of the gradient background — where the two images from the left column overlap the solid background.

                    \n\n\n\nFront-end output of the Group with Image Overlap pattern.\n\n\n\n

                    The technique is simple in terms of code, but it takes a good designer to create the concept. We are just now scratching the surface of what theme designers will be able to accomplish when they begin thinking about applying various techniques to the block system. Seedlet has some of that sort of outside-the-box thinking with its use of gradients. We need to see more of that from the theming community.

                    \n\n\n\n

                    Admittedly, I am not a fan of the third pattern the theme adds. “Alternating Grid of Latest Posts” inserts the Latest Posts block into the editor with the theme’s custom “Alternating Grid” style. Mostly, I just do not care for the layout, but that is simply based on my personal taste.

                    \n\n\n\nAlternating Grid of Latest Posts pattern in the editor.\n\n\n\n

                    On the whole, I love what the theme is doing with block patterns. This type of exploration is exactly what the WordPress community needs right now.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 09 Sep 2020 21:10:31 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Justin Tadlock\";s: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:127:\"WPTavern: Jetpack Launches Email Marketing Tools with Creative Mail Integration, WooCommerce-Triggered Store Emails Coming Soon\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104350\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:297:\"https://wptavern.com/jetpack-launches-email-marketing-tools-with-creative-mail-integration-woocommerce-triggered-store-emails-coming-soon?utm_source=rss&utm_medium=rss&utm_campaign=jetpack-launches-email-marketing-tools-with-creative-mail-integration-woocommerce-triggered-store-emails-coming-soon\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6173:\"

                    Jetpack is firing up a new suite of email marketing tools in partnership with Endurance International Group’s Constant Contact brand. Last week version 8.9 of the plugin introduced a new newsletter signup form inside its Form block, based on an integration with the Creative Mail plugin that Constant Contact recently launched as a solution tailored specifically to WordPress and WooCommerce.

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

                    The release post highlighted the ability to add WordPress posts and WooCommerce products into email marketing campaigns, but today the Jetpack team elaborated on where they are taking the integration. The features Creative Mail has on deck for future releases are heavily geared towards e-commerce stores. The initial launch includes the ability for store owners to sync their contacts to their email lists in order to market to them directly. Curt Raffi, Senior VP of Product Innovation at EIG, said WooCommerce-triggered store emails are on the way.

                    \n\n\n\n

                    “Soon, we’ll add automated customer lifecycle marketing journeys that are geared toward more advanced marketers and eCommerce seller,” Raffi said. The planned features include the following:

                    \n\n\n\n
                    • Create triggered, multi-step customer lifecycle marketing journeys
                    • Send WooCommerce abandoned cart emails
                    • Send post-purchase follow-up emails
                    • Send emails about related products
                    \n\n\n\n

                    Email marketing is a critical piece of the puzzle for online store owners looking to connect to customers, as they adapt to the pandemic with reduced foot traffic for brick and mortar locations. Stats from Campaign Monitor show that email send volumes increased by 31% for a random selection of their customers with mid-sized email lists during the 30-day period after March 17 versus the 30 days prior to that. Despite a sizeable increase in send volumes, average open rates for these decreased only slightly, from 31% to 30%, while click-through rates remained the same at 4%.

                    \n\n\n\n

                    Even with all the perfunctory messages acknowledging “these uncertain times,” email is still an important channel for reaching customers. As social networks are becoming increasingly hostile and unfavorable environments for advertising, email stands as one of the few remaining direct lines where content won’t get instantly buried by potential customers doomscrolling their news feeds.

                    \n\n\n\n

                    Automattic CEO Matt Mullenweg commented on Twitter last month about the value of having a follower’s email address vs a connection on a social network. “So many of these people with newsletters should really be blogging,” Mullenweg said.

                    \n\n\n\n

                    “I do think that a follower you have an email address of and a direct relationship with is worth 1,000x a follower on a social network. Maybe it’s just about making things more website-first than email-first, especially for younger audiences that don’t use email.”

                    \n\n\n\n
                    \n

                    Jetpack needs to make it much easier to blog and newsletter at the same time :)

                    — Stephane Boisvert (@stephBoisvert) August 18, 2020
                    \n
                    \n\n\n\n

                    One response to his tweet caught my attention – a suggestion that Jetpack make it more convenient to manage a website-first solution for email marketing. It looks like this idea was already in the works with Creative Mail and the Constant Contact partnership.

                    \n\n\n\n

                    Although Constant Contact already had an official plugin for WordPress, it only has 40,000 installs. Compare that with MailChimp, which is far and away the market leader when it comes to email marking providers. Mailchimp has many third-party plugins for WordPress, which collectively have more than a million users, including an official Mailchimp for WooCommerce plugin, with 800k+ active installs. Constant Contact stands to have a better chance penetrating the WordPress market by partnering with a highly successful plugin like Jetpack.

                    \n\n\n\n

                    Email marketing is not an easy plugin niche to break into, which is evident by the slow growth of newcomers like Newsletter Glue. The plugin is marketed as a Substack alternative, with its “Send as newsletter” feature inside the WordPress editor. It connects to different emails services, provides easy-to-share past issues, and creates a search engine-friendly newsletter archive. Despite all the promotion and buzz on social networks, the plugin only has ~30 active installs after one month in the official directory.

                    \n\n\n\n

                    With its deep integration with Jetpack and WooCommerce, Creative Mail has the chance to quickly become a contender among established WordPress email marketing plugins like MC4WP: Mailchimp for WordPress (1 million+ installs), MailPoet (100k), Email Subscribers (100k), and Newsletter (300k). Creative Mail has a broader scope of features that it will be supporting, but it may be able to find success on the basis of Jetpack’s ubiquity.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 09 Sep 2020 05:20:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:66:\"WPTavern: More Power in the Hands of WordPress Support Forum Users\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104352\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:177:\"https://wptavern.com/more-power-in-the-hands-of-wordpress-support-forum-users?utm_source=rss&utm_medium=rss&utm_campaign=more-power-in-the-hands-of-wordpress-support-forum-users\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6013:\"

                    What level of control should users have over their WordPress support forum topics? That is the question at the heart of a recent discussion opened by Mika Epstein on the Make Support blog. The goal is to grant more power to users, particularly when they post private or privileged information to the public forums.

                    \n\n\n\n

                    The proposal is twofold. One idea is to give users total control over deleting or “archiving” topics they create. This would remove it from public view at least. The second part of the equation would extend the amount of time users have to edit their topics.

                    \n\n\n\n

                    Currently, users can edit topics for one hour after posting. For the most part, this is reasonable. However, there are some cases where users inadvertently post sensitive data and need to remove it later. After their hour is up, the only solution for editing is to contact a forum moderator, increasing the burden on the WordPress support team. The easiest solution is to increase the length of time to edit.

                    \n\n\n\n

                    The big downside to editing topics is that they can be changed so much that replies are out of context. This can make discussions, particularly, lengthier ones with more replies, hard to follow. However, given the nature of the WordPress forums being for support instead of long-form discussion, increasing the time-to-edit should not hurt. It should help users fix mistakes and lighten the load on forum moderators. There are proposals for increasing the limit between three to seven days.

                    \n\n\n\n

                    In general, I am supportive of increasing the time-to-edit for forum topics. There is some room for abuse of the system, but such abuse will not likely outweigh the benefits. However, the ability to delete a topic does not sit well with me.

                    \n\n\n\n

                    I see the problem. WordPress’s user base has changed over the past decade. The average user from 10 years ago was tech-savvy enough to not drop private info — or info they are not legally allowed to share — into public forums. The game has changed. Users are no longer webmasters, running every aspect of their sites. They are using one-click installs to launch software they have no technical knowledge of. They do not know the difference between a debug log and server info. This is not a bad thing — the more WordPress users the more we inch toward that democratize-publishing goal. However, the makeup of WordPress’s users has shifted drastically to a point where many may not realize they are posting information they shouldn’t.

                    \n\n\n\n

                    The burden ultimately falls on forum moderators. They do all the cleanup, and it is likely overwhelming at times to keep up. It is a decision that should probably fall into their hands.

                    \n\n\n\n

                    One of the catalysts for this discussion was a forum topic from last week. “Someone had posted information that isn’t exactly ‘private’ but could land them in legal trouble for sharing,” wrote Epstein. “They did so by posting a debug log that had information that probably should not be public.”

                    \n\n\n\n

                    The WordPress support system has had a long-standing, in-house rule of not deleting posts except under extreme circumstances. However, the proposal would allow users to delete their own topics at any time.

                    \n\n\n\n

                    I dislike the idea of removing support forum topics. The best form of support is to already have a question answered. This gives others the ability to search and find the answer to their own questions. It allows moderators to link to existing answers for repeat questions. Allowing users to remove topics means that others could miss out on free knowledge.

                    \n\n\n\n

                    I ran a plugin and theme support forum for over a decade. It racked up hundreds of thousands of posts. I personally answered every question or made sure that each was answered by someone else. Over the years, the forums became a wealth of knowledge because, except in those extreme circumstances, no topic was ever deleted. Granted, my support burden was far lighter than that of the WordPress support moderators. However, past forum topics were an important tool in the arsenal.

                    \n\n\n\n

                    Moreso than my time running support, I have relied on past support forum topics for my edification throughout the years. Rarely has there been a time I have needed an answer that I could not find through a basic support search. No need to hassle others with my already-answered questions.

                    \n\n\n\n

                    I dislike the idea of deleting knowledge.

                    \n\n\n\n

                    Of course, we must weigh this against privacy. I doubt many users would take advantage of the ability to delete their topics. In those rare cases when they do, I imagine they will have a good reason for doing so, such as hiding information they no longer want to share publicly. Still, the idea does not sit well with me. I want a balance of retaining knowledge while removing personal data.

                    \n\n\n\n

                    I do have respect for privacy. There are steps WordPress.org could take. Users should absolutely be able to remove their own accounts from WordPress.org. Currently, they can remove any personal data from their profile, which is essentially the same thing. The one problem with this is if their username, which cannot be changed, identifies the person (e.g., I use justintadlock for many online accounts).

                    \n\n\n\n

                    I would still take this the extra step and allow users to completely delete their accounts. This would be a clean sweep, ensuring they did not accidentally miss something when clearing out their profile. After doing so, their former topics in the forums should simply be assigned to an anonymous account. It doesn’t matter who created a particular topic, only that the content still exists.

                    \n\n\n\n

                    What steps do you think WordPress.org should take to provide end-users more agency over their support topics?

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 08 Sep 2020 21:24: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:14:\"Justin Tadlock\";s: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:\"WordCamp Central: WordCamp Finland Online 2020 is coming!\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:39:\"https://central.wordcamp.org/?p=3128690\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://central.wordcamp.org/news/2020/09/08/wordcamp-finland-online-2020-is-coming/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1942:\"
                    \n

                    We are pleased to announce that the WordCamp Finland Online will on November 12 2020, 12:00-17:00 Helsinki time (UTC+2). Check the time in your local timezone.

                    \n

                    We are looking for speakers to present their knowledge, skills, experiences, and stories with the WordPress community. Applications from all areas of expertise are most welcome.

                    \n

                    Call for Speakers is open now! Submissions will close on October 2, 2020. See all details and send your application on Call for Speakers page.

                    \n

                    WordCamps would be nothing without awesome sponsors, helping us to cover the costs and providing great offers for attendees! Not forgetting all the useful information they provide.

                    \n

                    Call for Sponsors will open soon, we are currently finalizing our offerings for sponsors! If you are interested to sponsor WordCamp Finland Online 2020, make sure to subscribe for updates!

                    \n

                    Tickets to WordCamp Finland Online 2020 will be free of charge! Registration is not required but recommended for getting the full experience and all the offers from our sponsors.

                    \n

                    Remember to subscribe, using the form in the footer, to stay up to date regarding event news and announcements. We’ll be posting regularly in the months leading up to WordCamp Finland with information about speakers, tickets, and practical information.

                    \n

                    You will also be able to find updates from our Twitter. The official hashtag for WordCamp Finland Online is #WCFI. If you need to reach us you can comment on one of our social media posts or contact us using the website.

                    \n

                    We hope you’ll join us online in November!

                    \n
                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 08 Sep 2020 12:51:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"Timi Wahalahti\";s: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:94:\"WPTavern: iThemes Enters the WordPress Membership Plugin Market, Acquires Restrict Content Pro\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104095\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:231:\"https://wptavern.com/ithemes-enters-the-wordpress-membership-plugin-market-acquires-restrict-content-pro?utm_source=rss&utm_medium=rss&utm_campaign=ithemes-enters-the-wordpress-membership-plugin-market-acquires-restrict-content-pro\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6902:\"

                    Last Tuesday, iThemes announced it had acquired the Restrict Content Pro plugin from Sandhills Development. iThemes is part of the Liquid Web family of brands. Pippin Williamson, Managing Director at Sandhills, said the company had no intention of selling the plugin last October when talks of the acquisition began. However, moving forward has created some opportunities for his company and narrowed its focus to its existing products.

                    \n\n\n\n

                    Restrict Content Pro will remain an independent product with its own website. However, iThemes will include it as part of its Plugin Suite and Toolkit product bundles from the iThemes website. The Plugin Suite bundle runs at $249 per year, which is the same as the regular Restrict Content Pro price. However, the bundle includes other products such as the company’s popular BackupBuddy plugin. The Toolkit bundle runs between $700 and $997 per year. It includes the Plugin Suite, a themes package, training, and more.

                    \n\n\n\n

                    This structuring of product sites falls directly within the company’s long-term plans. “Earlier this year we actually started down a number of avenues experimenting with moving some of our products off ithemes.com and over to their own sites,” said AJ Morris, the Product Innovation and Marketing Manager at iThemes. “When COVID became a pandemic, we paused a lot of those projects to provide relief and help to the WordPress community. Now that things have calmed down for us a bit, we’re going to continue on that path.”

                    \n\n\n\n

                    Outside of the change of ownership, end-users should not see much change with the plugin or the site. Users should expect some admin-side changes in the future as the new development team refreshes the plugin.

                    \n\n\n\n

                    The Membership Plugin Space

                    \n\n\n\n

                    Membership plugins represent a slice of the overall WordPress market that still has no true dominant player. There are several solutions out there, but it is still an emerging area that any company can dive into and see returns on with a solid product. It is a niche that will undoubtedly continue growing along with WordPress and has plenty of untrodden ground just waiting for the right people to take their first steps across. There will always be a need for more fine-tuned control over users and permissions than what WordPress offers out of the box.

                    \n\n\n\n

                    “We are always in the market looking at other plugins that make sense for our business,” said Morris of why they made the acquisition. “Our audience is primarily freelance developers that are building a wide range of sites for clients. Over the years, we’ve focused on a number of non-utility products (like iThemes Exchange) and we learned a lot during that time. We’ve also learned a lot over the years of running our own membership site. For us looking at a membership plugin played with into the iThemes strategy and really the Liquid Web strategy as a whole.”

                    \n\n\n\n

                    I spent nine years developing and maintaining a membership-related plugin but sold it in 2019. If there is one lesson I learned during that time, it’s that no two sites have the exact same membership needs. There is always room for individual companies to build a product that meets specific user needs in the membership space.

                    \n\n\n\n

                    “What I feel like is everyone is currently trying to create the best Swiss Army knife,” said Morris. “I don’t think that anyone sets out saying I want to be good at all things, but when you’re developing a plugin that has so much possibilities for the market it serves, you have to feel out where you want to play and claim stake to that area. You become the best you can in that area and work at making sure you succeed there. Then you can start to properly branch out to other segments of the space that are within close proximity to where your core is.”

                    \n\n\n\n

                    iThemes is stepping into the game at an ideal time. Restrict Content Pro is currently a $500,000+ per year product, according to Williamson. In the right hands and with continued growth, it could become the go-to solution for memberships in the WordPress ecosystem. iThemes has a solid history in the plugin space. This is a good opportunity to see where they take the project.

                    \n\n\n\n

                    The Future of Restrict Content Pro

                    \n\n\n\n

                    Morris said that Sandhills Dev already had a solid short to mid-term plan for the plugin. These plans are providing iThemes with a head-start on features and ideas, some of which are already in progress. The team’s plan is to continue down this path, which matches some of the areas the company wanted to address.

                    \n\n\n\n

                    “After that, we’ve got some ideas, but we also want to get to know the community around Restrict Content Pro,” said Morris. “[Matt Danner] has mentioned in several places that the RCP community is more developer-centric while the iThemes community is historically not. Right now we’re in listening mode. We’re starting conversations all over the web with RCP customers to get a sense of what they are looking at and apply those learnings with where we want to take RCP in the membership space. Right now, I think it’s a bit premature to talk about specific features we’re including or what direction we’re fully going.”

                    \n\n\n\n

                    The one area that is currently lacking is the free Restrict Content plugin. Its user base is still relatively small (10,000 active installs). Its average 3.7 star-rating from end-users does not spell confidence, but it could be brought up with some active work.

                    \n\n\n\n

                    Restrict Content Pro has long had the benefit of being associated with Williamson and Sandhills Development’s other products like Easy Digital Downloads and AffiliateWP. All of these projects fit well together — often a user of one plugin needs at least one of the others. The pro plugin has likely not relied on the traffic from WordPress.org for success. However, it would not hurt to bring those numbers up. While the install count from the free version does not always directly correlate to success with commercial versions, it is usually a good indicator. Putting some resources behind beefing up the free plugin could translate to better returns in the long term.

                    \n\n\n\n

                    Morris said that iThemes will be sharing news about the free Restrict Content plugin soon. However, he is remaining tight-lipped about what those plans are for now.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 07 Sep 2020 21:35: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:14:\"Justin Tadlock\";s: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:41:\"WP Mobile Apps: How do I make a new 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"http://apps.wordpress.com/?p=4145\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://apps.wordpress.com/2020/09/06/how-do-i-make-a-new-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:459:\"

                    To make a new page, tap the icon and select your site, then select “Site Pages”. Tap the icon in the bottom-right corner to open a new page. You can edit any page by selecting it by title from the “Pages” screen.If you are looking for your drafts or your scheduled pages, check the menu across the top of the page and select the “Drafts” or “Scheduled” tab to access the list of the pages.

                    \n

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 06 Sep 2020 15:53:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"logosom\";s: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:41:\"WP Mobile Apps: How do I make a new Post?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"http://apps.wordpress.com/?p=4136\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:63:\"https://apps.wordpress.com/2020/09/06/how-do-i-make-a-new-post/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:538:\"

                    To make a new post, tap the icon and select your site, select “Blog Posts”, then tap the icon in the bottom-right corner. You can edit any post by selecting it from the “Blog Posts” screen.  If you are looking for your drafts or your scheduled posts, check the menu across the top of the page and select the “Drafts” or “Scheduled” tab to access the list of the posts.

                    \n

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sun, 06 Sep 2020 15:47: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:7:\"logosom\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:45;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: WordPress Support Team Seeks to Curb Support Requests for Commercial Plugins and Themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104255\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:239:\"https://wptavern.com/wordpress-support-team-seeks-to-curb-support-requests-for-commercial-plugins-and-themes?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-support-team-seeks-to-curb-support-requests-for-commercial-plugins-and-themes\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7049:\"\n\n\n\n

                    WordPress’ Support Team contributors are discussing how they can curb support requests for commercial products on the official WordPress.org forums. Users sometimes seek help for commercial product upgrades on the forums of the free version, not knowing that the moderators’ official policy is to refer them to the extension’s commercial support channel. In other instances, it is not immediately clear whether the issue is with the free version or a paid upgrade that the user has installed.

                    \n\n\n\n

                    “This has come up a few times the past weeks, mostly in relation to plugins that have a free base product on WordPress.org, but sell addons on their own site, and where the line is drawn on who can get supported where,” WordPress contributor Marius Jensen said during the team’s most recent meeting. “Authors are not allowed to support their paid products on WordPress.org as is, but where do you draw the line, for example, when a base plugin causes issues with a paid addon, should then support be allowed for the base product on WordPress.org, since that’s the root issue, or should it be shipped off to the author’s own site, since it affects a paying user?”

                    \n\n\n\n

                    This type of issue is common among products where WordPress.org is the main distribution channel for a popular free theme or plugin. The support relationship between the free and commercial products often intersects in an ambiguous way.

                    \n\n\n\n

                    “The goal is to ensure that paying customers and free users get the best support they can, from the ones that can give it,” Jensen said. Volunteers do not have access to the commercial products, nor is it their job to support them. This is the crux of the matter.

                    \n\n\n\n

                    “It’s an unacceptable misuse of volunteers time to support a product someone else has been paid to support,” Jensen said.

                    \n\n\n\n

                    Contributors discussed how they can handle different scenarios where it’s unclear where the root of the problem is, in order to move the burden away from the support moderators, allowing the extension’s author to discern if the problem is with the free version or commercial add-on. Volunteers should not have to familiarize themselves with the minute distinctions between the features that are offered for free or as an upgrade.

                    \n\n\n\n

                    On the other side of these support scenarios, where it isn’t clear where the problem originates, plugin and theme authors can be inconvenienced when support topics are hastily closed.

                    \n\n\n\n

                    “It’s just that the closing of topics seems counter productive for those (users and devs alike) that get it wrong,” plugin developer Arnan de Gans said. “Since plugin/theme makers do not have any control over these forums we can’t do a thing after topics get closed. Which works against the user experience by creating confusion.” He suggested the team consider a grace period where the developer has a day or two to respond.

                    \n\n\n\n

                    Ben Meredith, head of support for a freemium plugin, chimed in on the discussion, urging the support team to consider how closing issues can sometimes create a bad user experience:

                    \n\n\n\n

                    An issue related to premium products is raised, and summarily closed by forum mods for being about a premium product. This creates a “googleable” record of the error message/problem that then attracts other visitors. Once the issue has been closed, we get copy-cat issues “I am having the same problem (link to closed post)” We get those replies in both followup forum posts and internal tickets. To the layperson who has no idea the distinction between “WordPress core volunteer” and “Company I just paid money to,” this creates a bad experience all around.

                    Premium users are treated like second-class citizens on the forums. They don’t know the guidelines, and reached out for help. This may be their first interaction with the WordPress community, and sometimes a well-meaning forum moderator can come across as wrist-slapping the exact people we want to give white-glove service to (they just paid us!).

                    \n\n\n\n

                    Michelle Frechette, Head of Customer Success at GiveWP, also shared this sentiment regarding the user experience.

                    \n\n\n\n

                    “Something I’m not seeing addressed much here is how alienating it can feel to be corrected by the mods (or even the plugin authors) to be directed from the forums back to the paid support page,” she said.

                    \n\n\n\n

                    Ben Meredith said that despite sticky posts telling users not to post questions about commercial products, notes in the readme file, website notices, and canned replies, users will inevitably end up posting in the forums anyway. Steering them away to commercial support channels should be done in a way that does not make seeking help on WordPress.org an unwelcoming experience.

                    \n\n\n\n

                    “I want for the forums to feel as welcoming as a WordCamp,” Meredith said.

                    \n\n\n\n

                    “The current enforcement of the ‘premium plugins can’t get support here’ is not in line with that overarching goal: users using and enjoying WordPress. Currently, premium users (who are potential community members and community leaders!) are getting a first impression of the community that is ‘You’re doing it wrong!’

                    \n\n\n\n

                    “I’d rather their first impression be ‘Happy to help! heads up, for questions like this in the future, we need you to go here.\'”

                    \n\n\n\n

                    In trying to ease the burden placed on volunteer support forum moderators, it’s important to consider how any new policy might also negatively impact developers hosting their plugins and themes on WordPress.org, and what kind of vibe the response gives to users in search of help. There are more suggestions for solutions in the comments on the post, and the discussion is open until Saturday, September 12, 2020, 07:00 PM CDT. The Support Team is seeking to get a wider range of viewpoints from plugin and theme authors before making a final decision on new guidelines for addressing requests for support on commercial products. Make sure to jump in on the comments within the next week if you have something to add to the discussion.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 05 Sep 2020 02:03:55 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i: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:80:\"WPTavern: Gutenberg 8.9 Brings Block-Based Widgets Out of the Experimental Stage\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104238\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:205:\"https://wptavern.com/gutenberg-8-9-brings-block-based-widgets-out-of-the-experimental-stage?utm_source=rss&utm_medium=rss&utm_campaign=gutenberg-8-9-brings-block-based-widgets-out-of-the-experimental-stage\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6765:\"

                    On Wednesday, September 2, Gutenberg 8.9 launched with a set of new features, enhancements, and several bug fixes. The development team took the block-based widgets system out of its experimental stage, making it the default experience for all plugin users.

                    \n\n\n\n

                    Block-based widgets have taken months upon months of work. The team has surpassed some of my expectations by essentially sticking a square peg into a square hole, granting the power of blocks to the sidebars/widgets system. On the whole, the system works. However, the team still has a lot of work to mold this feature into the shape it needs to be in for the upcoming WordPress 5.6 release in December. It is important that the community at large test, provide feedback, and contribute where possible.

                    \n\n\n\n

                    Gutenberg plugin users who have not yet enabled block-based widgets via the experiments screen in past versions will be in for a surprise. The new system will have some of the familiarity of the block editor. However, it is a much different experience than traditional widgets.

                    \n\n\n\n

                    The big questions we must answer is whether the feature is currently usable and whether it can be ready for WordPress 5.6.

                    \n\n\n\n

                    New Widgets Screen

                    \n\n\n\nBlock-based widgets screen.\n\n\n\n

                    Gutenberg completely replaces the old Appearance > Widgets screen in the WordPress admin. The plugin no longer has an option for end-users to disable it, which was expected. The goal is to begin getting users accustomed to building their sidebars with blocks rather than traditional widgets.

                    \n\n\n\n

                    For the most part, the new widgets screen handles block-based widgets without issue from a usability perspective. Adding blocks is little different from working with the post-editing screen. It should feel relatively natural for users who are accustomed to the block editor. If anything, the experience seems scaled down in comparison.

                    \n\n\n\n

                    Unlike widgets in the past, blocks cannot be collapsed (the sidebars themselves can be). As a long-time WordPress user, this feels uncomfortable. However, it is the sort of uncomfortableness that will simply take some adjustment time.

                    \n\n\n\n

                    Core legacy widgets worked well. However, I could not get legacy widgets to work from several third-party plugins. Sometimes, they disappeared from the editor. Then, they would later appear, seemingly at random. Eventually, during testing, I completely broke the page to the point where it did not display anything. Fortunately, I was able to fix it by clearing out a few widget-related rows from the database.

                    \n\n\n\n

                    As a developer, I want to simply wipe the slate clean and leave the old widgets system in the dust of history. However, doing so may very well alienate many end-users. For this feature to be successful, we need to carry them along and allow them to easily transition from their current tools to the new system.

                    \n\n\n\n

                    Widget Blocks in the Customizer

                    \n\n\n\nWidget blocks section in the customizer.\n\n\n\n

                    While the primary widget blocks screen was generally solid, that was not the case with widget blocks in the customizer. At best, it was sub-par.

                    \n\n\n\n

                    We may finally be at that point where I agree with all those earlier complaints of the customizer control panel being too narrow. The most obvious issue was that the block toolbar was too wide for the control panel, hiding pieces of it off-screen. For some blocks, there are buttons that users cannot access.

                    \n\n\n\n

                    That is not the end of the issues. Block options are unavailable, so users cannot even add something as basic as an image alt attribute. The core legacy widget blocks are not editable. The “more options” button popup has a transparent background, making the text unreadable and, for all intents and purposes, not worth attempting a use.

                    \n\n\n\n

                    I understand that WordPress is still far from launching widget blocks in the customizer, but the feature was practically unusable. It is still very much in an experimental state and probably should have remained optional for another plugin update or two or three. I cannot recommend using this within any sort of production environment. Stick with the widgets screen in the admin.

                    \n\n\n\n

                    Widgets/Blocks Styling Issues for Theme Authors

                    \n\n\n\nNo structured grouping of “widget” HTML.\n\n\n\n

                    One of the largest changes that theme authors need to be aware of is that blocks in sidebars do not have the typical widget HTML wrappers. This could present some issues with styling widgets in the traditional fashion. For example, themes usually register a widget wrapper element and a wrapper for the widget title. This allows theme authors to build consistent styles for each widget. With blocks, this becomes much tougher because the theme author loses that control — this control is passed to the end-user.

                    \n\n\n\n

                    The great part of this system is that users can do some really interesting things and have the flexibility to style their sidebars in any way they want. The bad part is that if a theme author has any sort of intricate styles, such as a boxed widget design, there is no easy way for the end-user to simply drop widgets into place and have them all use that boxed design. There is no standard class name for the theme author to target with CSS, which is what is required for consistently-styled widgets.

                    \n\n\n\n

                    This is not necessarily a good or bad thing in and of itself. It is simply different.

                    \n\n\n\n

                    With that said, I would have much preferred the Gutenberg development team created a new and separate system from the old sidebars/widgets system. Leave that in place, then build and promote “block areas” as a new system for theme authors to take advantage of. In the long run, it would allow theme authors to make the transition and even potentially support both systems in their themes. Theme authors are down in the trenches, working with their users on a day-to-day basis. They are in a much better position to handle the transition from old to new.

                    \n\n\n\n

                    Theme authors who are not prepared to go all in with block-based widgets in WordPress 5.6 can add the following line of PHP to their theme’s setup code to disable the widgets block editor:

                    \n\n\n\n
                    remove_theme_support( \'widgets-block-editor\' );
                    \n\n\n\n

                    Over time, theme authors will want to fully transition to the new system. However, this will provide additional time for them to make any adjustments that may be needed with how widgets are handled.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 04 Sep 2020 17:05: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:47;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"WPTavern: Sunlit 3.0 for iOS Released, Featuring New Post Editor and Improved Discovery Interface\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=103996\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:237:\"https://wptavern.com/sunlit-3-0-for-ios-released-featuring-new-post-editor-and-improved-discovery-interface?utm_source=rss&utm_medium=rss&utm_campaign=sunlit-3-0-for-ios-released-featuring-new-post-editor-and-improved-discovery-interface\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3794:\"

                    Sunlit 3.0 was released this week and is now available in the App Store. The free photoblogging app is a companion app to the Micro.blog indie microblogging platform. Sunlit has some similarities to Instagram minus the deadweight of ads and algorithms. Users can follow each other, comment on posts, and timeline photos are displayed in chronological order.

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

                    “The idea is to get more people posting photos to their own blogs, whether that’s hosted on Micro.blog, WordPress.com, or a self-hosted WordPress,” Micro.blog creator Manton Reece said. Publishing to WordPress does not require any extra plugins, because the app uses the built-in XML-RPC support.

                    \n\n\n\n

                    Sunlit uses Micro.blog’s infrastructure for the social aspect (replies and mentions). Users must be signed into a Micro.blog account (either paid or free) to view the timeline or reply to posts. In the current version, users are required to go to Micro.blog on the web to register first but Reece said his team is aiming to make this more seamless in the future so users can start using all the features in Sunlit right away.

                    \n\n\n\n

                    “Some people use Micro.blog for their blog exclusively, and some people have a mix of a microblog or photoblog on Micro.blog, as well as a full blog on WordPress,” Reece said.

                    \n\n\n\n

                    Sunlit also has support for following Tumblr photoblogs. In the app’s Discover tab, users can enter a Tumblr subdomain like “username.tumblr.com,” and then follow the blog even if the user is not on Sunlit.

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

                    “Micro.blog is based on blogs and IndieWeb standards so that it can integrate well with the rest of the web, not be walled off like a silo,” Reece said. “One aspect of this is that you can follow many blogs in Micro.blog even if the author of the blog hasn’t registered on Micro.blog yet, similar to how you can subscribe to blogs in a feed reader like NetNewsWire or Feedbin.”

                    \n\n\n\n

                    Sunlit 3.0 has been redesigned with a new Discover interface and a faster, more flexible posting screen. Users can publish a quick photo or even a full blog post with text and photos uploaded to the users’ blog, along with the HTML layout for the post. This version also includes user search and support for mentions when replying to conversations.

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

                    Micro.blog is currently supporting the app’s development, and Reese said he has no plans to add any commercial upgrades into Sunlit.

                    \n\n\n\n

                    “We support Sunlit as part of running Micro.blog,” he said. “Sunlit makes an existing Micro.blog subscription more useful, so it helps with the overall platform sustainability, even if not everyone using Sunlit is paying for a subscription. We hope that more people will sign up for a paid Micro.blog subscription, but it’s not required.”

                    \n\n\n\n

                    Sunlit does not have an Android app but the teams would like to support Android in the future. The app is open source and available on GitHub under the MIT License.

                    \n\n\n\n

                    “Because Sunlit for iOS is open source, this [Android support] might be something that comes from the community or it might be something we take the lead on. I personally have much more experience with iOS, so we started there.”

                    \n\n\n\n

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 03 Sep 2020 23:15: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: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:82:\"WPTavern: WordPress Plugin Authors Should Avoid Confusing Users When Naming Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104091\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"https://wptavern.com/wordpress-plugin-authors-should-avoid-confusing-users-when-naming-blocks?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-plugin-authors-should-avoid-confusing-users-when-naming-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7172:\"

                    On May 4, the StudioPress development team made a small but significant user-facing change to its Atomic Blocks plugin (now rebranded to Genesis Blocks). It removed the “AB” branding from its block titles. This minor update changed block titles such as AB Accordion and AB Button to Accordion and Button, respectively. On the surface, this change probably seemed of little consequence to the developers on the project. However, for at least one user, it created a massive workload.

                    \n\n\n\n

                    Unless users religiously followed the GitHub code commits, they would have missed this update. Stacked with several other code changes for a seemingly unrelated ticket, the team left a message that read, “Remove unnecessary ‘AB’ from block titles.”

                    \n\n\n\n

                    The change made it into version 2.8.2 of the plugin, which launched a day later.

                    \n\n\n\n

                    The problem was that there was no message in the change log that noted this. Users had no indication that the blocks from the plugin were being renamed. Typically, this would not be a big deal since the plugin team had merely dropped the “AB” prefix from the otherwise unchanged titles. However, what happens when one of those blocks’ titles matches a core block title?

                    \n\n\n\n

                    That was the issue that Marcus Tibesar ran into. The AB Button block suddenly became the Button block. Thinking he was using the core WordPress Button, he made liberal use of it throughout his site. Throw in his decision to drop the plugin after StudioPress rebranded its plugin to Genesis Blocks, it became a bit of a disaster to clean up.

                    \n\n\n\n

                    “I have been using the Button block for months now only to discover that I’m actually using the Atomic Blocks button block!” wrote Tibesar in a comment on the Atomic Blocks rebranding post.

                    \n\n\n\n

                    Theoretically, he should have needed to update only any lingering blocks from Atomic Blocks that he had knowingly used. But, he was stuck with blocks that he had unknowingly added to his posts and pages through no fault of his own.

                    \n\n\n\n

                    This particular scenario was made worse because WordPress 5.4, released on March 31, introduced a new Buttons (plural) block. The old single Button block was removed from the normal inserter. While not all block-naming issues are so convoluted, it still begs the question: how can plugin authors avoid causing these types of user-experience issues?

                    \n\n\n\n

                    It is easy to throw blame toward StudioPress — and the team could perhaps use a scolding for not being clear about the change when it happened. However, this brings forth a couple of things the greater WordPress community needs to figure out. The first is whether plugin authors need to use a consistent, prefixed naming scheme for their blocks. The second is what can WordPress do to help mitigate issues.

                    \n\n\n\n

                    Prefix All the Things

                    \n\n\n\nButtons, buttons, and more buttons.\n\n\n\n

                    That is the common saying in the WordPress development world, right? Prefixing and namespacing guidelines generally apply to the actual code, which is where conflicts arise. However, there are times when prefixing public-facing text is warranted.

                    \n\n\n\n

                    And those times are when plugins utilize a shared space.

                    \n\n\n\n

                    The block editor is one such shared space. With more and more block plugins landing in the directory, it is time that plugin authors consider how block-naming schemes affect end-users. The issue is certainly not limited to Atomic/Genesis Blocks. This has been an ongoing trend with several block library plugins. Some do better than others, but it’s a toss-up each time a user installs such a plugin.

                    \n\n\n\n

                    The easiest route is for plugin authors to simply prefix all custom blocks with their company branding (e.g., AB Button). On the other hand, not every block shares a title with one of the core blocks. For example, a block titled Product Carousel may not need to distinguish itself further from other blocks. It is unlikely that end-users are running multiple eCommerce plugins with blocks that share the same title.

                    \n\n\n\n

                    “All, repeat all, should have a prefix,” said Tibesar. “The prefixes eliminate any confusion as to whether we users are selecting a core block or a third-party block. The most popular plugins appear at the top of the list, and it’s confusing from whence they came when prefixes are absent.”

                    \n\n\n\n

                    At the very least, third-party blocks should have a prefix if their titles match one of the core blocks. End-users should not see two different Cover blocks in the block inserter, for example. Instead, they should see the core Cover and a second, uniquely-titled block. Prefixing is an easy way to do that. But, I could live with anything that does not cause user confusion.

                    \n\n\n\n

                    Locating Instances of Block Usage

                    \n\n\n\nManage Blocks screen.\n\n\n\n

                    In late 2019, the Gutenberg team released the first prototype of a potential block management area for the WordPress admin. The Manage Blocks screen from the prototype showcased an area that would allow users to manage every block on their site. One of the more important bits of information on this screen was an “Instances” count, which displayed the number of times a block was in use. It further linked to a screen with every post that had a particular block.

                    \n\n\n\n

                    One of the reasons this feature is important is that it would allow end-users to locate posts that they may want to clean up. Using the Atomic/Genesis Button block as an example, Tibesar could track down all those old uses and make any changes he wanted.

                    \n\n\n\n

                    He said he would absolutely welcome this feature in WordPress. “New users are tempted to load up on zillions of block plugins all to be forgotten later. Also, maintainers would use this tool when cleaning up broken sites. Just being able to see an overview of what blocks were used where, will allow publishers to dial back the number of block plugins installed on their sites, especially when new plugins and technologies emerge.”

                    \n\n\n\n

                    Because this feature is not in core yet, he had to turn to the Find My Blocks plugin, which helped him identify 22 posts and pages where he had unknowingly used the Button block from Atomic/Genesis Blocks. In the long term, this is something that needs to be handled directly in WordPress. It is unlikely to be the last time a user needs to clean house and get rid of old blocks.

                    \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 03 Sep 2020 19:41: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:14:\"Justin Tadlock\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:49;a:6:{s:4:\"data\";s:13:\"\n \n \n \n \n \n \n\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:2:{s:0:\"\";a:5:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:82:\"WPTavern: WordPress 5.5.1 Released with Backfill for Deprecated JavaScript Globals\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:30:\"https://wptavern.com/?p=104101\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:209:\"https://wptavern.com/wordpress-5-5-1-released-with-backfill-for-deprecated-javascript-globals?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-5-5-1-released-with-backfill-for-deprecated-javascript-globals\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4766:\"

                    WordPress 5.5.1 was released yesterday with 34 bug fixes, 4 enhancements, and 5 bug fixes for the block editor.

                    \n\n\n\n

                    Version 5.5 removed 19 legacy JavaScript localization objects, in favor of using the new functions and utilities found in the i18n package introduced in WordPress 5.0. One of the most notable changes in this maintenance release is the inclusion of a backfill for these now deprecated JavaScript globals, which were causing errors with many popular plugins and themes.

                    \n\n\n\n

                    “If we only count plugins or themes with more than 100k installs or more, some of these already have an incredible impact, which is why we decided to patch this as fast possible.” Joost de Valk said in an update compiling a list of affected extensions, with the the help of Omar Reiss.

                    \n\n\n\n

                    Themes impacted include Astra (1 million+ installs), Storefront (200k+), Hestia (100k+), and dozens more. A small selection of the popular plugins that were impacted include Advanced Custom Fields (1 million+), SiteOrigins Widgets Bundle (1 million+), AMP for WP, (100k+), WooCommerce Services (1 million+), Ocean Extra (600k+), and Rank Math SEO (400k+).

                    \n\n\n\n

                    Theme and plugin developers still need to update their code to use wp.i18n but in the meantime the legacy code will not block JavaScript execution. De Valk said the new plan is to remove this fallback code in two major versions, so developers need to have their code updated by the time WordPress 5.7 rolls around in 2021. 

                    \n\n\n\n

                    “It sounds like a question that also ought to be addressed is how such wide-spread breakage could happen, and how it can be prevented in future,” David Anderson commented on the announcement regarding the backfill. “What part of the release process ought to have flagged up that this was about to happen, how did that part fail, and how can future similar failures be prevented.” Jake Spurlock suggested a retrospective on WordPress 5.5 might be a good idea.

                    \n\n\n\n

                    Three weeks after WordPress 5.5 was released, the Enable jQuery Migrate Helper has more than 100,000 active installs. The plugin is available as a stopgap for users who experience problems with jQuery after updating to WP 5.5. Although several bumps along the road are expected for users during WordPress’ process of updating to use the latest version of jQuery, the official support forums were inundated with reports of broken sites after 5.5 was released. Many users found out about the plugin after hours of troubleshooting and hunting for a fix. This is another issue that would be helpful to address in a 5.5 retrospective.

                    \n\n\n\n

                    This maintenance release also removes the ability to alter the list of environment types in the new wp_get_environment_type() function. Contributors decided that introducing new types wasn’t the intention of the feature and that it makes it so that theme and plugin developers cannot rely on a set, predictable list of types. They are now limited to production, staging, development, and local, with definitions for each available in the announcement.

                    \n\n\n\n

                    “By limiting the set of environment types in this way, WordPress core, plugins, and themes can change their behavior depending on this setting,” Joost de Valk said.

                    \n\n\n\n

                    WordPress 5.5.1 also fixes XML sitemaps paginating incorrectly, adds the site environment to debug information, and improves a number of other features that shipped with defects. The full list of changes is available on the release 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:\"Wed, 02 Sep 2020 18:45:43 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"Sarah Gooding\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}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:\"Sat, 03 Oct 2020 21:42:00 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Sat, 03 Oct 2020 21:30:08 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:\"20200501235608\";}','no'),(186,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1601804520','no'),(187,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1601761320','no'),(188,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1601804520','no'),(189,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b','
                    ','no'),(207,'_site_transient_update_plugins','O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1601762287;s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:9:{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.6\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.1.6.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: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:{}}s:19:\"jetpack/jetpack.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:21:\"w.org/plugins/jetpack\";s:4:\"slug\";s:7:\"jetpack\";s:6:\"plugin\";s:19:\"jetpack/jetpack.php\";s:11:\"new_version\";s:5:\"8.9.1\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/jetpack/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/jetpack.8.9.1.zip\";s:5:\"icons\";a:3:{s:2:\"2x\";s:60:\"https://ps.w.org/jetpack/assets/icon-256x256.png?rev=1791404\";s:2:\"1x\";s:52:\"https://ps.w.org/jetpack/assets/icon.svg?rev=1791404\";s:3:\"svg\";s:52:\"https://ps.w.org/jetpack/assets/icon.svg?rev=1791404\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:63:\"https://ps.w.org/jetpack/assets/banner-1544x500.png?rev=1791404\";s:2:\"1x\";s:62:\"https://ps.w.org/jetpack/assets/banner-772x250.png?rev=1791404\";}s:11:\"banners_rtl\";a:0:{}}s:29:\"nginx-helper/nginx-helper.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:26:\"w.org/plugins/nginx-helper\";s:4:\"slug\";s:12:\"nginx-helper\";s:6:\"plugin\";s:29:\"nginx-helper/nginx-helper.php\";s:11:\"new_version\";s:5:\"2.2.2\";s:3:\"url\";s:43:\"https://wordpress.org/plugins/nginx-helper/\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/plugin/nginx-helper.2.2.2.zip\";s:5:\"icons\";a:3:{s:2:\"2x\";s:65:\"https://ps.w.org/nginx-helper/assets/icon-256x256.png?rev=2360932\";s:2:\"1x\";s:57:\"https://ps.w.org/nginx-helper/assets/icon.svg?rev=2360932\";s:3:\"svg\";s:57:\"https://ps.w.org/nginx-helper/assets/icon.svg?rev=2360932\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:68:\"https://ps.w.org/nginx-helper/assets/banner-1544x500.png?rev=2360932\";s:2:\"1x\";s:67:\"https://ps.w.org/nginx-helper/assets/banner-772x250.png?rev=2360926\";}s:11:\"banners_rtl\";a:2:{s:2:\"2x\";s:72:\"https://ps.w.org/nginx-helper/assets/banner-1544x500-rtl.png?rev=2360932\";s:2:\"1x\";s:71:\"https://ps.w.org/nginx-helper/assets/banner-772x250-rtl.png?rev=2360932\";}}s:47:\"post-and-page-builder/post-and-page-builder.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:35:\"w.org/plugins/post-and-page-builder\";s:4:\"slug\";s:21:\"post-and-page-builder\";s:6:\"plugin\";s:47:\"post-and-page-builder/post-and-page-builder.php\";s:11:\"new_version\";s:6:\"1.13.4\";s:3:\"url\";s:52:\"https://wordpress.org/plugins/post-and-page-builder/\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/plugin/post-and-page-builder.1.13.4.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:74:\"https://ps.w.org/post-and-page-builder/assets/icon-256x256.png?rev=1768477\";s:2:\"1x\";s:74:\"https://ps.w.org/post-and-page-builder/assets/icon-128x128.png?rev=1768477\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:77:\"https://ps.w.org/post-and-page-builder/assets/banner-1544x500.png?rev=1768477\";s:2:\"1x\";s:76:\"https://ps.w.org/post-and-page-builder/assets/banner-772x250.png?rev=1768477\";}s:11:\"banners_rtl\";a:0:{}}s:35:\"boldgrid-backup/boldgrid-backup.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:29:\"w.org/plugins/boldgrid-backup\";s:4:\"slug\";s:15:\"boldgrid-backup\";s:6:\"plugin\";s:35:\"boldgrid-backup/boldgrid-backup.php\";s:11:\"new_version\";s:6:\"1.14.5\";s:3:\"url\";s:46:\"https://wordpress.org/plugins/boldgrid-backup/\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/plugin/boldgrid-backup.1.14.5.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:68:\"https://ps.w.org/boldgrid-backup/assets/icon-256x256.png?rev=1880952\";s:2:\"1x\";s:68:\"https://ps.w.org/boldgrid-backup/assets/icon-128x128.png?rev=1880952\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:71:\"https://ps.w.org/boldgrid-backup/assets/banner-1544x500.png?rev=1880952\";s:2:\"1x\";s:70:\"https://ps.w.org/boldgrid-backup/assets/banner-772x250.png?rev=1880952\";}s:11:\"banners_rtl\";a:0:{}}s:19:\"weforms/weforms.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:21:\"w.org/plugins/weforms\";s:4:\"slug\";s:7:\"weforms\";s:6:\"plugin\";s:19:\"weforms/weforms.php\";s:11:\"new_version\";s:5:\"1.5.1\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/weforms/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/weforms.1.5.1.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:60:\"https://ps.w.org/weforms/assets/icon-256x256.png?rev=1978687\";s:2:\"1x\";s:60:\"https://ps.w.org/weforms/assets/icon-128x128.png?rev=1978687\";}s:7:\"banners\";a:2:{s:2:\"2x\";s:63:\"https://ps.w.org/weforms/assets/banner-1544x500.png?rev=2243402\";s:2:\"1x\";s:62:\"https://ps.w.org/weforms/assets/banner-772x250.png?rev=2243402\";}s:11:\"banners_rtl\";a:0:{}}s:24:\"wp-central/wpcentral.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:24:\"w.org/plugins/wp-central\";s:4:\"slug\";s:10:\"wp-central\";s:6:\"plugin\";s:24:\"wp-central/wpcentral.php\";s:11:\"new_version\";s:5:\"1.5.3\";s:3:\"url\";s:41:\"https://wordpress.org/plugins/wp-central/\";s:7:\"package\";s:53:\"https://downloads.wordpress.org/plugin/wp-central.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:63:\"https://ps.w.org/wp-central/assets/icon-256x256.png?rev=1965788\";s:2:\"1x\";s:63:\"https://ps.w.org/wp-central/assets/icon-128x128.png?rev=1965788\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:65:\"https://ps.w.org/wp-central/assets/banner-772x250.png?rev=1965788\";}s:11:\"banners_rtl\";a:0:{}}s:63:\"post-and-page-builder-premium/post-and-page-builder-premium.php\";O:8:\"stdClass\":5:{s:4:\"slug\";s:29:\"post-and-page-builder-premium\";s:6:\"plugin\";s:63:\"post-and-page-builder-premium/post-and-page-builder-premium.php\";s:11:\"new_version\";s:5:\"1.0.4\";s:3:\"url\";s:24:\"http://www.boldgrid.com/\";s:7:\"package\";s:112:\"https://api.boldgrid.com/api/open/get-asset?id=1034507&installed_plugin_version=1.0.4&installed_wp_version=5.5.1\";}}}','no'),(217,'jetpack_available_modules','a:1:{s:5:\"8.9.1\";a:42:{s:8:\"carousel\";s:3:\"1.5\";s:13:\"comment-likes\";s:3:\"5.1\";s:8:\"comments\";s:3:\"1.4\";s:12:\"contact-form\";s:3:\"1.3\";s:9:\"copy-post\";s:3:\"7.0\";s:20:\"custom-content-types\";s:3:\"3.1\";s:10:\"custom-css\";s:3:\"1.7\";s:21:\"enhanced-distribution\";s:3:\"1.2\";s:16:\"google-analytics\";s:3:\"4.5\";s:19:\"gravatar-hovercards\";s:3:\"1.1\";s:15:\"infinite-scroll\";s:3:\"2.0\";s:8:\"json-api\";s:3:\"1.9\";s:5:\"latex\";s:3:\"1.1\";s:11:\"lazy-images\";s:5:\"5.6.0\";s:5:\"likes\";s:3:\"2.2\";s:8:\"markdown\";s:3:\"2.8\";s:9:\"masterbar\";s:3:\"4.8\";s:7:\"monitor\";s:3:\"2.6\";s:5:\"notes\";s:3:\"1.9\";s:10:\"photon-cdn\";s:3:\"6.6\";s:6:\"photon\";s:3:\"2.0\";s:13:\"post-by-email\";s:3:\"2.0\";s:7:\"protect\";s:3:\"3.4\";s:9:\"publicize\";s:3:\"2.0\";s:13:\"related-posts\";s:3:\"2.9\";s:6:\"search\";s:3:\"5.0\";s:9:\"seo-tools\";s:3:\"4.4\";s:10:\"sharedaddy\";s:3:\"1.1\";s:10:\"shortcodes\";s:3:\"1.1\";s:10:\"shortlinks\";s:3:\"1.1\";s:8:\"sitemaps\";s:3:\"3.9\";s:3:\"sso\";s:3:\"2.6\";s:5:\"stats\";s:3:\"1.1\";s:13:\"subscriptions\";s:3:\"1.2\";s:13:\"tiled-gallery\";s:3:\"2.1\";s:10:\"vaultpress\";s:5:\"0:1.2\";s:18:\"verification-tools\";s:3:\"3.0\";s:10:\"videopress\";s:3:\"2.5\";s:17:\"widget-visibility\";s:3:\"2.4\";s:7:\"widgets\";s:3:\"1.2\";s:21:\"woocommerce-analytics\";s:3:\"8.4\";s:7:\"wordads\";s:5:\"4.5.0\";}}','yes'),(218,'wpc_dismiss_notice_date','2020-10-03','yes'),(238,'theme_mods_business-way','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(226,'widget_business-way-quote-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(227,'widget_business-way-welcome-msg-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(228,'widget_business_way_feature_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(229,'widget_business_way_service_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(230,'widget_business-way-our-mission-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(231,'widget_business-way-recent-post-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(232,'widget_business-way-our-work-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(233,'widget_business_way_about_widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(234,'widget_business-way-contact-widget','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(235,'category_children','a:0:{}','yes'),(236,'theme_mods_business-path','a:1:{s:18:\"custom_css_post_id\";i:-1;}','yes'),(237,'_transient_is_multi_author','0','yes'); /*!40000 ALTER TABLE `wp3v_options` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_postmeta` -- DROP TABLE IF EXISTS `wp3v_postmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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 DEFAULT NULL, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=18 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_postmeta` -- LOCK TABLES `wp3v_postmeta` WRITE; /*!40000 ALTER TABLE `wp3v_postmeta` DISABLE KEYS */; INSERT INTO `wp3v_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'),(3,5,'_wp_page_template','default'),(4,6,'_wp_attached_file','2020/10/2020-landscape-1.png'),(5,6,'_wp_attachment_metadata','a:5:{s:5:\"width\";i:1200;s:6:\"height\";i:769;s:4:\"file\";s:28:\"2020/10/2020-landscape-1.png\";s:5:\"sizes\";a:4:{s:6:\"medium\";a:4:{s:4:\"file\";s:28:\"2020-landscape-1-300x192.png\";s:5:\"width\";i:300;s:6:\"height\";i:192;s:9:\"mime-type\";s:9:\"image/png\";}s:5:\"large\";a:4:{s:4:\"file\";s:29:\"2020-landscape-1-1024x656.png\";s:5:\"width\";i:1024;s:6:\"height\";i:656;s:9:\"mime-type\";s:9:\"image/png\";}s:9:\"thumbnail\";a:4:{s:4:\"file\";s:28:\"2020-landscape-1-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";}s:12:\"medium_large\";a:4:{s:4:\"file\";s:28:\"2020-landscape-1-768x492.png\";s:5:\"width\";i:768;s:6:\"height\";i:492;s:9:\"mime-type\";s:9:\"image/png\";}}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:{}}}'),(6,6,'_starter_content_theme','twentytwenty'),(7,6,'_customize_draft_post_name','the-new-umoma-opens-its-doors'),(8,7,'_thumbnail_id','6'),(9,7,'_customize_draft_post_name','the-new-umoma-opens-its-doors'),(10,7,'_customize_changeset_uuid','fc209c21-c1a7-4579-9cca-074c8f2c84cf'),(11,8,'_customize_draft_post_name','about'),(12,8,'_customize_changeset_uuid','fc209c21-c1a7-4579-9cca-074c8f2c84cf'),(13,9,'_customize_draft_post_name','contact'),(14,9,'_customize_changeset_uuid','fc209c21-c1a7-4579-9cca-074c8f2c84cf'),(15,10,'_customize_draft_post_name','blog'),(16,10,'_customize_changeset_uuid','fc209c21-c1a7-4579-9cca-074c8f2c84cf'),(17,11,'_customize_restore_dismissed','1'); /*!40000 ALTER TABLE `wp3v_postmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_posts` -- DROP TABLE IF EXISTS `wp3v_posts`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `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=12 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_posts` -- LOCK TABLES `wp3v_posts` WRITE; /*!40000 ALTER TABLE `wp3v_posts` DISABLE KEYS */; INSERT INTO `wp3v_posts` (`ID`, `post_author`, `post_date`, `post_date_gmt`, `post_content`, `post_title`, `post_excerpt`, `post_status`, `comment_status`, `ping_status`, `post_password`, `post_name`, `to_ping`, `pinged`, `post_modified`, `post_modified_gmt`, `post_content_filtered`, `post_parent`, `guid`, `menu_order`, `post_type`, `post_mime_type`, `comment_count`) VALUES (1,1,'2020-10-03 21:40:14','2020-10-03 21:40:14','\n

                    Welcome to WordPress. This is your first post. Edit or delete it, then start writing!

                    \n','Hello world!','','publish','open','open','','hello-world','','','2020-10-03 21:40:14','2020-10-03 21:40:14','',0,'https://cablesoftwares.com/?p=1',0,'post','',1),(2,1,'2020-10-03 21:40:14','2020-10-03 21:40:14','\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','','','2020-10-03 21:40:14','2020-10-03 21:40:14','',0,'https://cablesoftwares.com/?page_id=2',0,'page','',0),(3,1,'2020-10-03 21:40:14','2020-10-03 21:40:14','

                    Who we are

                    Our website address is: https://cablesoftwares.com.

                    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','','','2020-10-03 21:40:14','2020-10-03 21:40:14','',0,'https://cablesoftwares.com/?page_id=3',0,'page','',0),(4,1,'2020-10-03 21:41:55','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2020-10-03 21:41:55','0000-00-00 00:00:00','',0,'https://cablesoftwares.com/?p=4',0,'post','',0),(5,1,'2020-10-03 21:45:36','2020-10-03 21:45:36','\n

                    Coming soon.

                    \n','Attribution','','publish','closed','closed','','attribution','','','2020-10-03 21:45:36','2020-10-03 21:45:36','',0,'https://cablesoftwares.com/attribution/',0,'bg_attribution','',0),(6,1,'2020-10-03 21:58:15','0000-00-00 00:00:00','','The New UMoMA Opens its Doors','','auto-draft','open','closed','','','','','2020-10-03 21:58:13','0000-00-00 00:00:00','',0,'https://cablesoftwares.com/wp-content/uploads/2020/10/2020-landscape-1.png',0,'attachment','image/png',0),(7,1,'2020-10-03 21:58:15','0000-00-00 00:00:00','

                    The premier destination for modern art in Northern Sweden. Open from 10 AM to 6 PM every day during the summer months.

                    \"\"

                    Works and Days

                    August 1 -- December 1

                    Read More
                    \"\"

                    Theatre of Operations

                    October 1 -- December 1

                    Read More
                    \"\"

                    The Life I Deserve

                    August 1 -- December 1

                    Read More
                    \"\"

                    From Signac to Matisse

                    October 1 -- December 1

                    Read More
                    \"\"

                    “Cyborgs, as the philosopher Donna Haraway established, are not reverent. They do not remember the cosmos.”

                    With seven floors of striking architecture, UMoMA shows exhibitions of international contemporary art, sometimes along with art historical retrospectives. Existential, political and philosophical issues are intrinsic to our programme. As visitor you are invited to guided tours artist talks, lectures, film screenings and other events with free admission

                    The exhibitions are produced by UMoMA in collaboration with artists and museums around the world and they often attract international attention. UMoMA has received a Special Commendation from the European Museum of the Year, and was among the top candidates for the Swedish Museum of the Year Award as well as for the Council of Europe Museum Prize.

                    Become a Member and Get Exclusive Offers!

                    Members get access to exclusive exhibits and sales. Our memberships cost $99.99 and are billed annually.

                    Join the Club
                    • \"\"
                    • \"\"
                    ','The New UMoMA Opens its Doors','','auto-draft','closed','closed','','','','','2020-10-03 21:58:13','0000-00-00 00:00:00','',0,'https://cablesoftwares.com/?page_id=7',0,'page','',0),(8,1,'2020-10-03 21:58:15','0000-00-00 00:00:00','\n

                    You might be an artist who would like to introduce yourself and your work here or maybe you’re a business with a mission to describe.

                    \n','About','','auto-draft','closed','closed','','','','','2020-10-03 21:58:13','0000-00-00 00:00:00','',0,'https://cablesoftwares.com/?page_id=8',0,'page','',0),(9,1,'2020-10-03 21:58:15','0000-00-00 00:00:00','\n

                    This is a page with some basic contact information, such as an address and phone number. You might also try a plugin to add a contact form.

                    \n','Contact','','auto-draft','closed','closed','','','','','2020-10-03 21:58:13','0000-00-00 00:00:00','',0,'https://cablesoftwares.com/?page_id=9',0,'page','',0),(10,1,'2020-10-03 21:58:15','0000-00-00 00:00:00','','Blog','','auto-draft','closed','closed','','','','','2020-10-03 21:58:13','0000-00-00 00:00:00','',0,'https://cablesoftwares.com/?page_id=10',0,'page','',0),(11,1,'2020-10-03 21:58:15','0000-00-00 00:00:00','{\n \"widget_text[2]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YTo0OntzOjU6InRpdGxlIjtzOjE1OiJBYm91dCBUaGlzIFNpdGUiO3M6NDoidGV4dCI7czo4NToiVGhpcyBtYXkgYmUgYSBnb29kIHBsYWNlIHRvIGludHJvZHVjZSB5b3Vyc2VsZiBhbmQgeW91ciBzaXRlIG9yIGluY2x1ZGUgc29tZSBjcmVkaXRzLiI7czo2OiJmaWx0ZXIiO2I6MTtzOjY6InZpc3VhbCI7YjoxO30=\",\n \"title\": \"About This Site\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"4ccf26b71939e7a8f9048164fda5075b\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"sidebars_widgets[sidebar-1]\": {\n \"starter_content\": true,\n \"value\": [\n \"text-2\"\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"widget_text[3]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YTo0OntzOjU6InRpdGxlIjtzOjc6IkZpbmQgVXMiO3M6NDoidGV4dCI7czoxNjg6IjxzdHJvbmc+QWRkcmVzczwvc3Ryb25nPgoxMjMgTWFpbiBTdHJlZXQKTmV3IFlvcmssIE5ZIDEwMDAxCgo8c3Ryb25nPkhvdXJzPC9zdHJvbmc+Ck1vbmRheSZuZGFzaDtGcmlkYXk6IDk6MDBBTSZuZGFzaDs1OjAwUE0KU2F0dXJkYXkgJmFtcDsgU3VuZGF5OiAxMTowMEFNJm5kYXNoOzM6MDBQTSI7czo2OiJmaWx0ZXIiO2I6MTtzOjY6InZpc3VhbCI7YjoxO30=\",\n \"title\": \"Find Us\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"225751404a2de9b08e4008f7eac63d06\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"sidebars_widgets[sidebar-2]\": {\n \"starter_content\": true,\n \"value\": [\n \"text-3\"\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menus_created_posts\": {\n \"starter_content\": true,\n \"value\": [\n 6,\n 7,\n 8,\n 9,\n 10\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Primary\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"custom\",\n \"title\": \"Home\",\n \"url\": \"https://cablesoftwares.com/\",\n \"position\": 0,\n \"nav_menu_term_id\": -1,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-2]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 8,\n \"position\": 1,\n \"nav_menu_term_id\": -1,\n \"title\": \"About\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-3]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 10,\n \"position\": 2,\n \"nav_menu_term_id\": -1,\n \"title\": \"Blog\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-4]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 9,\n \"position\": 3,\n \"nav_menu_term_id\": -1,\n \"title\": \"Contact\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"twentytwenty::nav_menu_locations[primary]\": {\n \"starter_content\": true,\n \"value\": -1,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Primary\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"custom\",\n \"title\": \"Home\",\n \"url\": \"https://cablesoftwares.com/\",\n \"position\": 0,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-6]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 8,\n \"position\": 1,\n \"nav_menu_term_id\": -5,\n \"title\": \"About\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-7]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 10,\n \"position\": 2,\n \"nav_menu_term_id\": -5,\n \"title\": \"Blog\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-8]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 9,\n \"position\": 3,\n \"nav_menu_term_id\": -5,\n \"title\": \"Contact\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"twentytwenty::nav_menu_locations[expanded]\": {\n \"starter_content\": true,\n \"value\": -5,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu[-9]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Social Links Menu\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-9]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Yelp\",\n \"url\": \"https://www.yelp.com\",\n \"position\": 0,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-10]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Facebook\",\n \"url\": \"https://www.facebook.com/wordpress\",\n \"position\": 1,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-11]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Twitter\",\n \"url\": \"https://twitter.com/wordpress\",\n \"position\": 2,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-12]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Instagram\",\n \"url\": \"https://www.instagram.com/explore/tags/wordcamp/\",\n \"position\": 3,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"nav_menu_item[-13]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Email\",\n \"url\": \"mailto:wordpress@example.com\",\n \"position\": 4,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"twentytwenty::nav_menu_locations[social]\": {\n \"starter_content\": true,\n \"value\": -9,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"show_on_front\": {\n \"starter_content\": true,\n \"value\": \"page\",\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"page_on_front\": {\n \"starter_content\": true,\n \"value\": 7,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n },\n \"page_for_posts\": {\n \"starter_content\": true,\n \"value\": 10,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-10-03 21:58:15\"\n }\n}','','','auto-draft','closed','closed','','fc209c21-c1a7-4579-9cca-074c8f2c84cf','','','2020-10-03 21:58:15','0000-00-00 00:00:00','',0,'https://cablesoftwares.com/?p=11',0,'customize_changeset','',0); /*!40000 ALTER TABLE `wp3v_posts` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_term_relationships` -- DROP TABLE IF EXISTS `wp3v_term_relationships`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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 `wp3v_term_relationships` -- LOCK TABLES `wp3v_term_relationships` WRITE; /*!40000 ALTER TABLE `wp3v_term_relationships` DISABLE KEYS */; INSERT INTO `wp3v_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES (1,1,0); /*!40000 ALTER TABLE `wp3v_term_relationships` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_term_taxonomy` -- DROP TABLE IF EXISTS `wp3v_term_taxonomy`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_term_taxonomy` -- LOCK TABLES `wp3v_term_taxonomy` WRITE; /*!40000 ALTER TABLE `wp3v_term_taxonomy` DISABLE KEYS */; INSERT INTO `wp3v_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES (1,1,'category','',0,1); /*!40000 ALTER TABLE `wp3v_term_taxonomy` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_termmeta` -- DROP TABLE IF EXISTS `wp3v_termmeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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 DEFAULT NULL, 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 `wp3v_termmeta` -- LOCK TABLES `wp3v_termmeta` WRITE; /*!40000 ALTER TABLE `wp3v_termmeta` DISABLE KEYS */; /*!40000 ALTER TABLE `wp3v_termmeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_terms` -- DROP TABLE IF EXISTS `wp3v_terms`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_terms` -- LOCK TABLES `wp3v_terms` WRITE; /*!40000 ALTER TABLE `wp3v_terms` DISABLE KEYS */; INSERT INTO `wp3v_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES (1,'Uncategorized','uncategorized',0); /*!40000 ALTER TABLE `wp3v_terms` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_usermeta` -- DROP TABLE IF EXISTS `wp3v_usermeta`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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 DEFAULT NULL, PRIMARY KEY (`umeta_id`), KEY `user_id` (`user_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=MyISAM AUTO_INCREMENT=23 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_usermeta` -- LOCK TABLES `wp3v_usermeta` WRITE; /*!40000 ALTER TABLE `wp3v_usermeta` DISABLE KEYS */; INSERT INTO `wp3v_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (1,1,'nickname','Atquil'),(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,'wp3v_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp3v_user_level','10'),(14,1,'dismissed_wp_pointers',',wp410_dfw'),(15,1,'show_welcome_panel','1'),(16,1,'session_tokens','a:1:{s:64:\"d43d47c7240366aa57683d065871f18aa2da38ed0f0bbd9229439450975c516e\";a:4:{s:10:\"expiration\";i:1601934111;s:2:\"ip\";s:13:\"5.146.192.133\";s:2:\"ua\";s:115:\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36\";s:5:\"login\";i:1601761311;}}'),(17,1,'bglibDashboardOrder','1'),(18,1,'jetpack_tracks_anon_id','jetpack:JgXB/OAbBVaMW4n0ihKm18CS'),(19,1,'wp3v_dashboard_quick_press_last_post_id','4'),(20,1,'community-events-location','a:1:{s:2:\"ip\";s:11:\"5.146.192.0\";}'),(21,1,'boldgrid_dismissed_admin_notices','a:2:{s:2:\"id\";s:13:\"bg-key-prompt\";s:9:\"timestamp\";i:1601761457;}'),(22,1,'boldgrid_dismissed_admin_notices','a:2:{s:2:\"id\";s:21:\"bgppb_upgrade_premium\";s:9:\"timestamp\";i:1601761607;}'); /*!40000 ALTER TABLE `wp3v_usermeta` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_users` -- DROP TABLE IF EXISTS `wp3v_users`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_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=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_users` -- LOCK TABLES `wp3v_users` WRITE; /*!40000 ALTER TABLE `wp3v_users` DISABLE KEYS */; INSERT INTO `wp3v_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES (1,'Atquil','$P$Brbdw1zhflzuPLIzmKWwr.1SEB3JO91','Atquil','techtrivialpvtltd@gmail.com','https://cablesoftwares.com','2020-10-03 21:40:14','',0,'Atquil'); /*!40000 ALTER TABLE `wp3v_users` ENABLE KEYS */; UNLOCK TABLES; -- -- Table structure for table `wp3v_wpforms_lite` -- DROP TABLE IF EXISTS `wp3v_wpforms_lite`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `wp3v_wpforms_lite` ( `rid` int(10) NOT NULL AUTO_INCREMENT, `start` bigint(20) NOT NULL, `end` bigint(20) NOT NULL, `status` tinyint(2) NOT NULL DEFAULT 1, `date` int(10) NOT NULL, PRIMARY KEY (`rid`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Dumping data for table `wp3v_wpforms_lite` -- LOCK TABLES `wp3v_wpforms_lite` WRITE; /*!40000 ALTER TABLE `wp3v_wpforms_lite` DISABLE KEYS */; /*!40000 ALTER TABLE `wp3v_wpforms_lite` ENABLE KEYS */; UNLOCK TABLES; -- -- Dumping events for database 'techtr18_wpcable' -- -- -- Dumping routines for database 'techtr18_wpcable' -- /*!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 2020-10-03 18:11:46