DROP TABLE IF EXISTS `dbdkeniz_commentmeta`; CREATE TABLE IF NOT EXISTS `dbdkeniz_commentmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`meta_id`), KEY `comment_id` (`comment_id`), KEY `meta_key` (`meta_key`(191))) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; DROP TABLE IF EXISTS `dbdkeniz_comments`; CREATE TABLE IF NOT EXISTS `dbdkeniz_comments` ( `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0', `comment_author` tinytext COLLATE utf8mb4_unicode_ci NOT NULL, `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_content` text COLLATE utf8mb4_unicode_ci NOT NULL, `comment_karma` int(11) NOT NULL DEFAULT '0', `comment_approved` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '1', `comment_agent` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`comment_ID`), KEY `comment_post_ID` (`comment_post_ID`), KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), KEY `comment_date_gmt` (`comment_date_gmt`), KEY `comment_parent` (`comment_parent`), KEY `comment_author_email` (`comment_author_email`(10))) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_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/', '', '2018-08-03 09:09:53', '2018-08-03 09:09:53', 'Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from Gravatar.', '0', '1', '', '', '0', '0'); DROP TABLE IF EXISTS `dbdkeniz_links`; CREATE TABLE IF NOT EXISTS `dbdkeniz_links` ( `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_image` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_target` varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_description` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_visible` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'Y', `link_owner` bigint(20) unsigned NOT NULL DEFAULT '1', `link_rating` int(11) NOT NULL DEFAULT '0', `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `link_rel` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_notes` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `link_rss` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', PRIMARY KEY (`link_id`), KEY `link_visible` (`link_visible`)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; DROP TABLE IF EXISTS `dbdkeniz_options`; CREATE TABLE IF NOT EXISTS `dbdkeniz_options` ( `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `option_name` varchar(191) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `option_value` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `autoload` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'yes', PRIMARY KEY (`option_id`), UNIQUE KEY `option_name` (`option_name`)) ENGINE=InnoDB AUTO_INCREMENT=157 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('1', 'siteurl', 'http://localhost/dkeniz', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('2', 'home', 'http://localhost/dkeniz', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('3', 'blogname', 'Dkeniz', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('4', 'blogdescription', 'Just another WordPress site', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('5', 'users_can_register', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('6', 'admin_email', 'roka.manoj12@gmail.com', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('7', 'start_of_week', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('8', 'use_balanceTags', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('9', 'use_smilies', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('10', 'require_name_email', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('11', 'comments_notify', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('12', 'posts_per_rss', '10', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('13', 'rss_use_excerpt', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('14', 'mailserver_url', 'mail.example.com', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('15', 'mailserver_login', 'login@example.com', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('16', 'mailserver_pass', 'password', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('17', 'mailserver_port', '110', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('18', 'default_category', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('19', 'default_comment_status', 'open', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('20', 'default_ping_status', 'open', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('21', 'default_pingback_flag', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('22', 'posts_per_page', '10', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('23', 'date_format', 'F j, Y', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('24', 'time_format', 'g:i a', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('25', 'links_updated_date_format', 'F j, Y g:i a', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('26', 'comment_moderation', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('27', 'moderation_notify', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('28', 'permalink_structure', '/%year%/%monthnum%/%day%/%postname%/', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('29', 'rewrite_rules', 'a:89:{s:11:"^wp-json/?$";s:22:"index.php?rest_route=/";s:14:"^wp-json/(.*)?";s:33:"index.php?rest_route=/$matches[1]";s:21:"^index.php/wp-json/?$";s:22:"index.php?rest_route=/";s:24:"^index.php/wp-json/(.*)?";s:33:"index.php?rest_route=/$matches[1]";s:47:"category/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$";s:52:"index.php?category_name=$matches[1]&feed=$matches[2]";s:42:"category/(.+?)/(feed|rdf|rss|rss2|atom)/?$";s:52:"index.php?category_name=$matches[1]&feed=$matches[2]";s:23:"category/(.+?)/embed/?$";s:46:"index.php?category_name=$matches[1]&embed=true";s:35:"category/(.+?)/page/?([0-9]{1,})/?$";s:53:"index.php?category_name=$matches[1]&paged=$matches[2]";s:17:"category/(.+?)/?$";s:35:"index.php?category_name=$matches[1]";s:44:"tag/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?tag=$matches[1]&feed=$matches[2]";s:39:"tag/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?tag=$matches[1]&feed=$matches[2]";s:20:"tag/([^/]+)/embed/?$";s:36:"index.php?tag=$matches[1]&embed=true";s:32:"tag/([^/]+)/page/?([0-9]{1,})/?$";s:43:"index.php?tag=$matches[1]&paged=$matches[2]";s:14:"tag/([^/]+)/?$";s:25:"index.php?tag=$matches[1]";s:45:"type/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?post_format=$matches[1]&feed=$matches[2]";s:40:"type/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?post_format=$matches[1]&feed=$matches[2]";s:21:"type/([^/]+)/embed/?$";s:44:"index.php?post_format=$matches[1]&embed=true";s:33:"type/([^/]+)/page/?([0-9]{1,})/?$";s:51:"index.php?post_format=$matches[1]&paged=$matches[2]";s:15:"type/([^/]+)/?$";s:33:"index.php?post_format=$matches[1]";s: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'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('30', 'hack_file', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('31', 'blog_charset', 'UTF-8', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('32', 'moderation_keys', '', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('33', 'active_plugins', 'a:0:{}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('34', 'category_base', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('35', 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('36', 'comment_max_links', '2', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('37', 'gmt_offset', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('38', 'default_email_category', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('39', 'recently_edited', '', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('40', 'template', 'wr-nitro', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('41', 'stylesheet', 'wr-nitro', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('42', 'comment_whitelist', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('43', 'blacklist_keys', '', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('44', 'comment_registration', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('45', 'html_type', 'text/html', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('46', 'use_trackback', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('47', 'default_role', 'subscriber', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('48', 'db_version', '38590', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('49', 'uploads_use_yearmonth_folders', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('50', 'upload_path', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('51', 'blog_public', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('52', 'default_link_category', '2', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('53', 'show_on_front', 'posts', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('54', 'tag_base', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('55', 'show_avatars', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('56', 'avatar_rating', 'G', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('57', 'upload_url_path', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('58', 'thumbnail_size_w', '150', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('59', 'thumbnail_size_h', '150', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('60', 'thumbnail_crop', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('61', 'medium_size_w', '300', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('62', 'medium_size_h', '300', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('63', 'avatar_default', 'mystery', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('64', 'large_size_w', '1024', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('65', 'large_size_h', '1024', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('66', 'image_default_link_type', 'none', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('67', 'image_default_size', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('68', 'image_default_align', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('69', 'close_comments_for_old_posts', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('70', 'close_comments_days_old', '14', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('71', 'thread_comments', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('72', 'thread_comments_depth', '5', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('73', 'page_comments', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('74', 'comments_per_page', '50', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('75', 'default_comments_page', 'newest', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('76', 'comment_order', 'asc', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('77', 'sticky_posts', 'a:0:{}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('78', 'widget_categories', 'a:2:{i:2;a:4:{s:5:"title";s:0:"";s:5:"count";i:0;s:12:"hierarchical";i:0;s:8:"dropdown";i:0;}s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('79', 'widget_text', 'a:0:{}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('80', 'widget_rss', 'a:0:{}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('81', 'uninstall_plugins', 'a:0:{}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('82', 'timezone_string', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('83', 'page_for_posts', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('84', 'page_on_front', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('85', 'default_post_format', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('86', 'link_manager_enabled', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('87', 'finished_splitting_shared_terms', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('88', 'site_icon', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('89', 'medium_large_size_w', '768', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('90', 'medium_large_size_h', '0', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('91', 'wp_page_for_privacy_policy', '3', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('92', 'initial_db_version', '38590', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('93', 'dbdkeniz_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'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('94', 'fresh_site', '1', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('95', 'widget_search', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('96', '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'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('97', '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'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('98', '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'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('99', 'widget_meta', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('100', 'sidebars_widgets', 'a:9:{s:19:"wp_inactive_widgets";a:0:{}s:15:"primary-sidebar";a:6:{i:0;s:8:"search-2";i:1;s:14:"recent-posts-2";i:2;s:17:"recent-comments-2";i:3;s:10:"archives-2";i:4;s:12:"categories-2";i:5;s:6:"meta-2";}s:8:"footer-1";a:0:{}s:8:"footer-2";a:0:{}s:8:"footer-3";a:0:{}s:8:"footer-4";a:0:{}s:8:"footer-5";a:0:{}s:14:"canvas-sidebar";a:0:{}s:13:"array_version";i:3;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('101', 'widget_pages', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('102', 'widget_calendar', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('103', 'widget_media_audio', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('104', 'widget_media_image', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('105', 'widget_media_gallery', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('106', 'widget_media_video', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('107', 'widget_tag_cloud', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('108', 'widget_nav_menu', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('109', 'widget_custom_html', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('110', 'cron', 'a:5:{i:1533290996;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:1533294937;a:1:{s:26:"upgrader_scheduled_cleanup";a:1:{s:32:"c9059feef497c200e69cb9956a81f005";a:2:{s:8:"schedule";b:0;s:4:"args";a:1:{i:0;i:5;}}}}i:1533330596;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:1533373961;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;}}}s:7:"version";i:2;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('111', 'theme_mods_twentyseventeen', 'a:2:{s:18:"custom_css_post_id";i:-1;s:16:"sidebars_widgets";a:2:{s:4:"time";i:1533287826;s:4:"data";a:4:{s:19:"wp_inactive_widgets";a:0:{}s:9:"sidebar-1";a:6:{i:0;s:8:"search-2";i:1;s:14:"recent-posts-2";i:2;s:17:"recent-comments-2";i:3;s:10:"archives-2";i:4;s:12:"categories-2";i:5;s:6:"meta-2";}s:9:"sidebar-2";a:0:{}s:9:"sidebar-3";a:0:{}}}}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('118', '_site_transient_timeout_theme_roots', '1533289617', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('119', '_site_transient_theme_roots', 'a:4:{s:13:"twentyfifteen";s:7:"/themes";s:15:"twentyseventeen";s:7:"/themes";s:13:"twentysixteen";s:7:"/themes";s:8:"wr-nitro";s:7:"/themes";}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('121', '_site_transient_update_plugins', 'O:8:"stdClass":4:{s:12:"last_checked";i:1533287818;s:8:"response";a:1:{s:19:"akismet/akismet.php";O:8:"stdClass":12:{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.0.8";s:3:"url";s:38:"https://wordpress.org/plugins/akismet/";s:7:"package";s:56:"https://downloads.wordpress.org/plugin/akismet.4.0.8.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:6:"tested";s:5:"4.9.6";s:12:"requires_php";b:0;s:13:"compatibility";O:8:"stdClass":0:{}}}s:12:"translations";a:0:{}s:9:"no_update";a:1:{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:3:"1.6";s:3:"url";s:42:"https://wordpress.org/plugins/hello-dolly/";s:7:"package";s:58:"https://downloads.wordpress.org/plugin/hello-dolly.1.6.zip";s:5:"icons";a:2:{s:2:"2x";s:63:"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=969907";s:2:"1x";s:63:"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=969907";}s:7:"banners";a:1:{s:2:"1x";s:65:"https://ps.w.org/hello-dolly/assets/banner-772x250.png?rev=478342";}s:11:"banners_rtl";a:0:{}}}}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('123', '_site_transient_timeout_browser_a86483e46b670f7632c84374159a18f1', '1533892364', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('124', '_site_transient_browser_a86483e46b670f7632c84374159a18f1', 'a:10:{s:4:"name";s:6:"Chrome";s:7:"version";s:12:"68.0.3440.84";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'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('125', '_site_transient_timeout_community-events-d41d8cd98f00b204e9800998ecf8427e', '1533330868', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('126', '_site_transient_community-events-d41d8cd98f00b204e9800998ecf8427e', 'a:2:{s:8:"location";a:1:{s:2:"ip";b:0;}s:6:"events";a:1:{i:0;a:7:{s:4:"type";s:8:"wordcamp";s:5:"title";s:16:"WordCamp Pokhara";s:3:"url";s:33:"https://2018.pokhara.wordcamp.org";s:6:"meetup";N;s:10:"meetup_url";N;s:4:"date";s:19:"2018-11-24 00:00:00";s:8:"location";a:4:{s:8:"location";s:21:"Pokhara, Kaski, Nepal";s:7:"country";s:2:"NP";s:8:"latitude";d:28.194758900000000068075678427703678607940673828125;s:9:"longitude";d:83.9731033000000053334588301368057727813720703125;}}}}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('128', 'can_compress_scripts', '1', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('129', '_transient_timeout_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1533330770', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('130', '_transient_feed_ac0b00fe65abe10e0c5b588f3ed8c7ca', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:26:"https://wordpress.org/news";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:14:"WordPress News";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:34:"\n Thu, 02 Aug 2018 22:13: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: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.0-alpha-43550";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:10:{i:0;a:6:{s:4:"data";s:33:"\n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"WordPress 4.9.8 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/2018/08/wordpress-4-9-8-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:"Thu, 02 Aug 2018 21:25:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a: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=6165";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:398:"We are pleased to announce the immediate availability of WordPress 4.9.8. This maintenance release fixes 46 bugs, enhancements and blessed tasks, including updating the Twenty Seventeen bundled theme. Following are the highlights of what is now available. “Try Gutenberg” callout Most users will now be presented with a notice in their WordPress dashboard. This “Try Gutenberg” […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Paul Biron";s: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:10398:"

We are pleased to announce the immediate availability of WordPress 4.9.8. This maintenance release fixes 46 bugs, enhancements and blessed tasks, including updating the Twenty Seventeen bundled theme.

Following are the highlights of what is now available.

“Try Gutenberg” callout

Most users will now be presented with a notice in their WordPress dashboard. This “Try Gutenberg” is an opportunity for users to use the Gutenberg block editor before it is released in WordPress 5.0.

In WordPress 4.9.8, the callout will be shown to the following users:

If Gutenberg is not installed or activated, the callout will be shown to Admin users on single sites, and Super Admin users on multisites.
If Gutenberg is installed and activated, the callout will be shown to Contributor users and above.
If the Classic Editor plugin is installed and activated, the callout will be hidden for all users.

You can learn more by reading “Try Gutenberg” Callout in WordPress 4.9.8.

Privacy fixes/enhancements

This release includes 18 Privacy fixes focused on ensuring consistency and flexibility in the new personal data tools that were added in 4.9.6, including:

The type of request being confirmed is now included in the subject line for all privacy confirmation emails.
Improved consistency with site name being used for privacy emails in multisite.
Pagination for Privacy request admin screens can now be adjusted.
Increased the test coverage for several core privacy functions.

This post has more information about all of the issues fixed in 4.9.8 if you’d like to learn more.

Download WordPress 4.9.8 or venture over to Dashboard → Updates and click “Update Now.” Sites that support automatic background updates are already beginning to update automatically.

Thank you to everyone who contributed to WordPress 4.9.8:

1naveengiri, Aaron D. Campbell, Aaron Jorbin, Abdullah Ramzan, alejandroxlopez, Allen Snook, Andrea Fercia, Andrew Ozz, Andrew Taylor, Arun, Ayesh Karunaratne, Birgir Erlendsson (birgire), Birgit Pauli-Haack, BjornW, Boone Gorges, Brandon Kraft, Burhan Nasir, Chetan Prajapati, Chris Lema, Corey McKrill, Daniel Bachhuber, Daniel James, David Herrera, Dion Hulse, Dominik Schilling (ocean90), dontstealmyfish, dyrer, Felipe Elia, Felix Arntz, Fernando Claussen, Gareth, Garrett Hyder, Gary Pendergast, Gennady Kovshenin, GM_Alex, Heather Burns, Ian Dunn, ibelanger, imath, Jb Audras, Jeremy Pry, JJJ, Joe McGill, Joen Asmussen, John Blackbourn, Jonathan Desrosiers, Jonny Harris, Josepha, JoshuaWold, Joy, jrf, K. Adam White, khaihong, kjellr, Konstantinos Xenos, laurelfulford, lbenicio, Leander Iversen, leemon, macbookandrew, Marius L. J., Matias Ventura, Mel Choyce, mensmaximus, mermel, metalandcoffee, michelleweber, Milan Dinić, Muhammad Kashif, Naoko Takano, Nathan Johnson, Ov3rfly, palmiak, Paul Biron, Prashant Baldha, PressTigers, programmin, Rafsun Chowdhury, redcastor, Robin Cornett, Sergey Biryukov, Simon Prosser, skoldin, spyderbytes, Subrata Sarkar, Sébastien SERRE, Tammie Lister, tharsheblows, Thomas Patrick Levy, timbowesohft, Timothy Jacobs, Tobias Zimpel, Tor-Bjorn Fjellner, Towhidul Islam, Usman Khalid, warmlaundry, William Earnhardt, Yui, and YuriV.

With WordPress 5.0 coming closer, there’s lots of work going on all across the project. Read on to learn about how we progressed in July.

\n\n

Release of WordPress 4.9.7

\n\n

On July 5, WordPress 4.9.7 was released, fixing one security issue and 17 other bugs across the platform.

\n\n

While this is a minor release, incremental fixes are essential to keep WordPress running smoothly. Everyone is encouraged to update as soon as possible and to make sure that automatic updates are switched on.

\n\n

Would you like 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

The New WordPress Editor

\n\n

In the upcoming minor release of WordPress, 4.9.8, a new section in the dashboard will feature Gutenberg, the upcoming content editor for WordPress.

\n\n

While the official release of Gutenberg is scheduled for the coming months, you can already install it as a plugin to test it out right now. Additionally, a brand new demo page is now available — play around with the many features the editor has to offer, without installing it on your own site.

\n\n

Would you like to help build or test Gutenberg? Follow the Core team blog and join the #core-editor channel in the Making WordPress Slack group.

\n\n

Page Design Updates on WordPress.org

\n\n

Bit by bit we’re refreshing the design of WordPress.org. The latest pages to get a new treatment have been the Download page and user profiles.

\n\n

The Meta and Design teams worked hard to make these new designs a reality, with notable contributions from @melchoyce, @obenland, @mapk, and @kjellr. The new designs enhance the overall look of the site and provide more relevant information to those searching.

\n\n

Would you like to get involved in the design refresh? Follow the Meta and Design team blogs and join the #meta and #design channels in the Making WordPress Slack group.

\n\n

The First WP-CLI Hack Day

\n\n

On Friday July 20, the WP-CLI team held their first hack day — a global event encouraging people to contribute to the official command line tool for WordPress.

\n\n

Run by @schlessera, the event was a great success. Twelve pull requests were merged and another 13 submitted. It also included a video chat to give all contributors a space to meet each other and connect directly.

\n\n

Would you like to get involved in contributing to WP-CLI? Follow the team blog and join the #cli channel in the Making WordPress Slack group.

\n\n

Accessibility

\n\n

Contacted: @rianrietveld, @joedolson, @afercia
Priority: Working to make sure that Gutenberg is reasonably accessible prior to merge. ETA is before 5.0
Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. The team is doing outreach to help solve this problem.
Big Win: Interest from companies like The Paciello Group and Tenon.io to help out with Gutenberg code review and testing tools.

\n\n

CLI

\n\n

Contacted: @danielbachhuber, @schlessera
Priority: Very first global Hack Day is coming up July 20. Version 2.0.0 is still in progress (new ETA is end of July).
Struggle: The team continues to need new contributors. The current team is tiny but tough.
Big Win: WP-CLI is currently one of the project’s four main focuses, as mentioned in the Summer Update at WordCamp Europe.

\n\n

Community

\n\n

Contacted: @francina, @hlashbrooke
Priority: Focusing on smoothing out the processes in our community management by building up our team of volunteers and establishing what tools we need to keep things running well. ETA is ongoing.
Struggle: Our two biggest struggles at the moment are tracking what we need to get done, and making final decisions on things. There is current work on the tools available to assist with tracking progress.
Big Win: After making a concerted effort to get more contributors on the Community Team, we now have a much larger group of volunteers working as deputies and WordCamp mentors

\n\n

Core

\n\n

Contacted: @jeffpaul
Priority: Following the WordCamp Europe summer update (and the companion post here), the team is getting Gutenberg (the new WordPress editing experience) into a strong state for the 5.0 release. Potential ETA as soon as August.
Struggle: Coordinating momentum and direction as we start seeing more contributors offering their time. Still working our way through open issues. The team is starting multiple bug scrubs each week to work through these more quickly and transparently.
Big Win: Had a sizable release in 4.9.6 which featured major updates around privacy tools and functionality in Core.

\n\n

Design

\n\n

Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
Priority: Better on-boarding of new contributors, especially creating better documentation. ETA is end of July.
Struggle: It’s hard to identify reasonably small tasks for first-time contributors.
Big Win: The team is much more organized now which has helped clear out the design backlog, bring in new contributors, and also keep current contributors coming back. Bonus: Joshua Wold will co-lead the upcoming release.

\n\n

Documentation

\n\n

Contacted: @kenshino
Priority: Opening up the work on HelpHub to new contributors and easing the onboarding process. No ETA.
Struggle: Some blockers with making sure the code and database can be ready to launch on https://wordpress.org/support/
Big Win: The first phase of HelpHub creation is complete, which means content updates (current info, more readable, easier discovery), internal search, design improvements, and REST API endpoints.

\n\n

Hosting

\n\n

Contacted: @mikeschroder, @jadonn
Priority: Preparing hosts for supporting Gutenberg, especially support questions they’re likely to see when the “Try Gutenberg” callout is released. ETA July 31st, then before WordPress 5.0
Struggle: Most contributions are still made a by a small team of volunteers. Seeing a few more people join, but progress is slow.
Big Win: New team members and hosting companies have joined the #hosting-community team and have started contributing.

\n\n

Marketing

\n\n

Contacted: @bridgetwillard
Priority: Continuing to write and publish case studies from the community. ETA is ongoing.
Struggle: No current team struggles.
Big Win: Wrote and designed a short Contributor Day onboarding card. It was used at Contributor Day at WCEU and onboarding time went down to 1 hour instead of 3 hours.

\n\n

Meta (WordPress.org Site)

\n\n

Contacted: @tellyworth, @coffee2code
Priority: Reducing manual work around the contributor space (theme review, GDPR/privacy, plugin review). ETA for small wins is end of quarter, larger efforts after that.
Struggle: Maintaining momentum on tickets. There are also some discussions about updating the ticket management process across teams that use the Meta trac system.
Big Win: The new About page launched and has been translated across most locale sites.

\n\n

Mobile

\n\n

Contacted: @elibud
Priority: Getting Gutenberg in the mobile applications. ETA is late December.
Struggle: Consuming the Gutenberg source in the ReactNative app directly. More info can be found here: https://make.wordpress.org/mobile/2018/07/09/next-steps-for-gutenberg-mobile/
Big Win: The WordPress mobile applications now fully support right-to-left languages and are compliant with the latest standards for accessibility.

\n\n

Plugins

\n\n

Contacted: @ipstenu
Priority: Clearing ~8,000 unused plugins from the queues. Likely ETA is September.
Struggles: Had to triage a lot of false claims around plugins offering GDPR compliance.
Big Win: Released 4.9.6 and updated expectations with plugin authors. Huge thanks to the Core Privacy team for their hard work on this.

\n\n

Polyglots

\n\n

Contacted: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
Priority: Keep WordPress releases translated to 100% and then concentrate on the top 100 plugins and themes. ETA is ongoing.
Struggle: Getting new PTEs fast enough, and complex tools/systems. Overall, the volume of strings awaiting approval.

\n\n

Support

\n\n

Contacted: @clorith
Priority: Getting ready for the Gutenberg callout (it got pushed last quarter). Needing a better presence on the official support forums, and outreach for that is underway, ETA end of July.
Struggle: Keeping contributors participating post-contributor days/drives. Considering the creation of a dedicated post-contributor day survey to get some insight here.
Big Win: The increase in international liaisons joining for weekly meetings, helping bring the wider support community together.

\n\n

Theme Review

\n\n

Contacted: @acosmin, @rabmalin, @thinkupthemes, @williampatton
Priority: Building a better Theme Check/Sniffer in order to automate most of the checks done right now by reviewers. ETA late 2018, early 2019.
Struggle: Bringing in new contributors to the team.
Big Win: Trusted Authors program

\n\n

Tide

\n\n

Contacted: @valendesigns (but usually @jeffpaul)
Priority: Storing PHPCompatibilty results inside the WordPress.org API and building a UI to display those results, an endpoint to request an audit is required for this work to continue.
Struggle: Development has dramatically slowed down while team members are on leave or pulled into internal client work.
Big Win: Migration to Google Cloud Platform (GCP) from Amazon Web Services (AWS) is complete and the audit servers have all been rewritten in Go. (This allows us to be faster with greater capacity and less cost.)

\n\n

Training

\n\n

Contacted: @bethsoderberg, @juliek
Priority: Lesson plan production. ETA is ongoing.
Struggle: The workflow is a little complex, so recruiting and training enough contributors to keep the process moving is a struggle.
Big Win: WordCamp Europe’s Contributor Day was very productive. New tools/workflow are in place and two team representatives were there to lead and help.

\n\n

Interested in updates from the first quarter of this year? You can find those here: https://make.wordpress.org/updates/2018/04/24/quarterly-updates-q1-2018/\n \n

Progress on the Gutenberg project, the new content creating experience coming to WordPress, has come a long way. Since the start of the project, there have been 30 releases and 12 of those happened after WordCamp US 2017. In total since then, there have been 1,764 issues opened and 1,115 closed as of WordCamp Europe. As the work on phase one moves into its final stretch, here is what you can expect.

\n\n

In Progress

\n\n

Freeze new features in Gutenberg (the feature list can be found here).
Hosts, agencies, teachers invited to opt-in sites they have influence over.
WordPress.com has opt-in for wp-admin users. The number of sites and posts will be tracked.
Mobile app support for Gutenberg will be across iOS and Android.

\n\n

July

\n\n

4.9.x release with an invitation to install either Gutenberg or Classic Editor plugin.
WordPress.com will move to opt-out. There will be tracking to see who opts out and why.
Triage increases and bug gardening escalates to get blockers in Gutenberg down to zero.
Gutenberg phase two, Customization exploration begins by moving beyond the post.

\n\n

August and beyond

\n\n

All critical issues within Gutenberg are resolved.
There is full integration with Calypso and there is opt-in for users there.
A goal will be 100k+ sites having made 250k+ posts using Gutenberg.
Core merge of Gutenberg begins the 5.0 release cycle.
5.0 moves into beta releases and translations are completed.
There will be a mobile version of Gutenberg by the end of the year.

\n\n

WordPress 5.0 could be as soon as August with hundreds of thousands of sites using Gutenberg before release. Learn more about Gutenberg here, take it for a test drive, install on your site, follow along on GitHub and give your feedback.

WordPress 4.9.7 is now available. This is a security and maintenance release for all versions since WordPress 3.7. We strongly encourage you to update your sites immediately.

\n\n

WordPress versions 4.9.6 and earlier are affected by a media issue that could potentially allow a user with certain capabilities to attempt to delete files outside the uploads directory.

\n\n

Thank you to Slavco for reporting the original issue and Matt Barry for reporting related issues.

\n\n

Seventeen other bugs were fixed in WordPress 4.9.7. Particularly of note were:

\n\n

Taxonomy: Improve cache handling for term queries.
Posts, Post Types: Clear post password cookie when logging out.
Widgets: Allow basic HTML tags in sidebar descriptions on Widgets admin screen.
Community Events Dashboard: Always show the nearest WordCamp if one is coming up, even if there are multiple Meetups happening first.
Privacy: Make sure default privacy policy content does not cause a fatal error when flushing rewrite rules outside of the admin context.

\n\n

Download WordPress 4.9.7 or venture over to Dashboard → Updates and click “Update Now.” Sites that support automatic background updates are already beginning to update automatically.

\n\n

The previously scheduled 4.9.7 is now referred to as 4.9.8, and will follow the release schedule posted yesterday.

\n\n

Thank you to everyone who contributed to WordPress 4.9.7:

\n\n

1naveengiri, Aaron Jorbin, abdullahramzan, alejandroxlopez, Andrew Ozz, Arun, Birgir Erlendsson (birgire), BjornW, Boone Gorges, Brandon Kraft, Chetan Prajapati, David Herrera, Felix Arntz, Gareth, Ian Dunn, ibelanger, John Blackbourn, Jonathan Desrosiers, Joy, khaihong, lbenicio, Leander Iversen, mermel, metalandcoffee, Migrated to @jeffpaul, palmiak, Sergey Biryukov, skoldin, Subrata Sarkar, Towhidul Islam, warmlaundry, and YuriV.

With one of the two flagship WordCamp events taking place this month, as well as some important WordPress project announcements, there’s no shortage of news. Learn more about what happened in the WordPress community in June.

\n\n

Another Successful WordCamp Europe

\n\n

On June 14th, WordCamp Europe kicked off three days of learning and contributions in Belgrade. Over 2,000 people attended in person, with hundreds more watching live streams of the sessions.

\n\n

The WordCamp was a great success with plenty of first-time attendees and new WordPress contributors getting involved in the project and community. Recorded sessions from the 65 speakers at the event will be available on WordPress.tv in the coming weeks. In the meantime, check out the photos from the event.

\n\n

The next WordCamp Europe takes place on June 20-22 2019 in Berlin, Germany. If you’re based in Europe and would like to serve on the organizing team, fill in the application form.

\n\n

Updated Roadmap for the New WordPress Content Editor

\n\n

During his keynote session at WordCamp Europe, Matt Mullenweg presented an updated roadmap for Gutenberg, the new content editor coming in WordPress 5.0.

\n\n

While the editor is in rapid development, with v3.1 being released this past month, the team is aiming to ship Gutenberg with WordPress Core in August, 2018. This is not set in stone — the release date may shift as development progresses — but this gives the first realistic idea of when we can expect the editor to be released.

\n\n

If you would like to contribute to Gutenberg, read the handbook, follow the Core team blog, and join the #core-editor channel in the Making WordPress Slack group.

\n\n

WordCamp Incubator Cities Announced

\n\n

The WordCamp Incubator program helps spread WordPress to underserved communities by providing organizing support for their first WordCamp. The first iteration of this program ran successfully in 2016 and empowered three cities to start their own WordPress communities.

\n\n

This year, the Community Team is running the Incubator program again. After receiving applications from 104 communities, they have selected Montevideo, Uruguay and Kota Kinabalu, Malaysia to participate in the program. Both cities will receive direct help from experienced WordCamp organizers to run their first-ever WordCamp as a way to help their WordPress community get started.

\n\n

To find out more about the Incubator program follow the Community team blog, and join the #community-events channel in the Making WordPress Slack group.

\n\n

Local Communities Celebrate the 15th Anniversary of WordPress

\n\n

Last Sunday, May 27, WordPress turned 15 years old. This is a noteworthy occasion for an open-source project like WordPress and one well worth celebrating. To mark the occasion, WordPress communities across the world gathered for parties and meetups in honor of the milestone.

\n\n

Altogether, there were 224 events globally, with a few more of those still scheduled to take place in some communities — attend one in your area if you can.

\n\n

If your city doesn’t have a WordPress meetup group, this is a great opportunity to start one! Learn how with the Meetup Organizer Handbook, and join the #community-events channel in the Making WordPress Slack group.

\n\n

Privacy Tools added to WordPress core

\n\n

In light of recent changes to data privacy regulations in the EU, WordPress Core shipped important updates in the v4.9.6 release, giving site owners tools to help them comply with the new General Data Protection Regulation (GDPR). It is worth noting, however, that WordPress cannot ensure you are compliant — this is still a site owner’s responsibility.

\n\n

The new privacy tools include a number of features focused on providing privacy and personal data management to all site users — asking commenters for explicit consent to store their details in a cookie, providing site owners with an easy way to publish a Privacy Policy, and providing data export and erasure tools to all site users that can be extended by plugins to allow the handling of data that they introduce.

\n\n

To find out more about these features and the other updates, read the 4.9.6 update guide. You can also get involved in contributing to this part of WordPress Core by jumping into the #core-privacy channel in the Making WordPress Slack group, and following the Core team blog.

\n\n

Updates to the WordPress.org Privacy Policy

\n\n

In a similar vein, WordPress.org itself has received an updated Privacy Policy to make clear what is being tracked and how your data is handled. Along with that, a Cookie Policy has also been added to explain just what is collected and stored in your browser when using the site.

\n\n

These policies cover all sites on the WordPress.org network — including WordPress.org, WordPress.net, WordCamp.org, BuddyPress.org, bbPress.org, and other related domains and subdomains. It’s important to note that this does not mean that anything has changed in terms of data storage; rather that these documents clarify what data is stored and how it is handled.

\n\n

Privacy

\n\n

The European Union’s General Data Protection Regulation (GDPR) takes effect on May 25. The GDPR requires companies and site owners to be transparent about how they collect, use, and share personal data. It also gives individuals more access and choice when it comes to how their own personal data is collected, used, and shared.

\n\n

It’s important to understand that while the GDPR is a European regulation, its requirements apply to all sites and online businesses that collect, store, and process personal data about EU residents no matter where the business is located.

\n\n

You can learn more about the GDPR from the European Commission’s Data Protection page.

\n\n

We’re committed to supporting site owners around the world in their work to comply with this important law. As part of that effort, we’ve added a number of new privacy features in this release.

\n\n

Comments

\n\n

A screenshot of a comment form, where the new "Save my name, email, and website in this browser for the next time I comment" checkbox is featured.

\n\n

Logged-out commenters will be given a choice on whether their name, email address, and website are saved in a cookie on their browser.

\n\n

Privacy Policy Page

\n\n

A screenshot of the new Privacy Settings page.

\n\n

Site owners can now designate a privacy policy page. This page will be shown on your login and registration pages. You should manually add a link to your policy to every page on your website. If you have a footer menu, that’s a great place to include your privacy policy.

\n\n

In addition, we’ve created a guide that includes insights from WordPress and participating plugins on how they handle personal data. These insights can be copied and pasted into your site’s privacy policy to help you get started.

\n\n

If you maintain a plugin that collects data, we recommend including that information in WordPress’ privacy policy guide. Learn more in our Privacy section of the Plugin Handbook.

\n\n

Data Handling

\n\n

A screenshot of the new Export Personal Data tools page. Several export requests are listed on the page, to demonstrate how the new feature will work.

\n\n

Data Export

\n \n

Site owners can export a ZIP file containing a user’s personal data, using data gathered by WordPress and participating plugins.

\n \n

Data Erasure

\n \n

Site owners can erase a user’s personal data, including data collected by participating plugins.

\n\n

\n
Howdy,
\n
A request has been made to perform the following action on your account:

\n
Export Personal Data

\n
To confirm this, please click on the following link:
http://.wordpress.org/wp-login.php?action=confirmaction…

\n
You can safely ignore and delete this email if you do not want to
take this action.

\n
This email has been sent to you@example.com.

\n
Regards,
Your friends at WordPress
http://wordpress.org
\n

\n\n

Site owners have a new email-based method that they can use to confirm personal data requests. This request confirmation tool works for both export and erasure requests, and for both registered users and commenters.

\n\n

Maintenance

\n\n

95 updates were made in WordPress 4.9.6. In addition to the above, particularly of note were:

\n\n

“Mine” has been added as a filter in the media library.
When viewing a plugin in the admin, it will now tell you the minimum PHP version required.
We’ve added new PHP polyfills for forwards-compatibility and proper variable validation.
TinyMCE was updated to the latest version (4.7.11).

\n\n

This post has more information about all of the issues fixed in 4.9.6 if you’d like to learn more.

\n\n

Download WordPress 4.9.6 or venture over to Dashboard → Updates and click “Update Now.” Sites that support automatic background updates will start updating soon.

\n\n

Please note that if you’re currently on WordPress 4.9.3, you should manually update your site immediately.

\n\n

Thank you to everyone who contributed to WordPress 4.9.6:
Aaron D. Campbell, Aaron Jorbin, abdullahramzan, Adam Silverstein, Alain Schlesser, allendav, Andrea Fercia, Andrea Middleton, Andrew Ozz, Ayesh Karunaratne, Birgir Erlendsson (birgire), bridgetwillard, Burlington Bytes, Chetan Prajapati, claudiu, Corey McKrill, Daniel Bachhuber, David Herrera, Dominik Schilling (ocean90), Ella Van Dorpe, Eric Daams, Fernando Claussen, Garrett Hyder, Gary Pendergast, Heather Burns, Helen Hou-Sandi, herregroen, Ian Dunn, ibelanger, imath, Jb Audras, Jeffrey Paul, Jeremy Felt, Jesper V Nielsen, JJJ, Joe McGill, John Blackbourn, Jonathan Desrosiers, Josepha, jrf, Kåre Mulvad Steffensen, Laken Hafner, laurelfulford, lbenicio, macbookandrew, Marius L. J., Mel Choyce, Michael Nelson, Mike Jolley, Pascal Casier, pbrocks, postphotos, Prashant Baldha, PressTigers, programmin, Robin Cornett, Sergey Biryukov, Stefano Lissa, Stephane Daury (stephdau), Subrata Sarkar, Tammie Lister, teddytime, thomasplevy, Timothy Jacobs, Tobias Zimpel, Tom J Nowell, Tor-Bjorn Fjellner, Towhidul Islam, voneff, William Earnhardt, and Xenos (xkon) Konstantinos.

This past month saw a lot of preparation for upcoming events and releases across the WordPress project. Read on to find out more about these plans, and everything else that happened around the community in April.

\n\n

The WordPress 15th Anniversary is Coming

\n\n

On May 27 2018, WordPress will turn 15 years old — this is a huge milestone for the project, or, indeed, for any open-source platform. The Community Team has been hard at work helping communities around the world plan local anniversary parties.

\n\n

Check the central anniversary website to see if there’s already a party being planned near you. These parties are all organized by local communities — if there’s no local community in your area, you can start one today and host a party yourself.

\n\n

Work has Started on a Gutenberg Migration Guide

\n\n

With Gutenberg, the upcoming WordPress content editor, in rapid development, a lot of people have been wondering how they will convert their existing plugins to work with the new features. To mitigate the issues here and help people overcome any migration hurdles, a Gutenberg Migration Guide is underway to assist developers with making their code Gutenberg-compatible.

\n\n

If you’d like to contribute to this guide, you can review the existing documentation on GitHub and open a new issue if you find something to add.

\n\n

Theme Review Team Launches Trusted Authors Program

\n\n

Reviews of themes submitted to the Theme Directory can take quite a while to complete. In order to combat this issue and to make the theme submission process smoother for everyone, the Theme Review Team is introducing a Trusted Authors Program.

\n\n

This program will allow frequent and reliable theme authors to apply for trusted status, allowing them to upload themes more frequently and to have their themes automatically approved. This will allow more high-quality themes to be added to the directory, as well as recognize the hard work that authors put in to build their themes.

\n\n

If you would like to get involved with reviewing themes, you can read their getting started guide, follow the team blog and join the #themereview channel in the Making WordPress Slack group.

\n\n

“Try Gutenberg” callout

In WordPress 4.9.8, the callout will be shown to the following users:

If Gutenberg is not installed or activated, the callout will be shown to Admin users on single sites, and Super Admin users on multisites.
If Gutenberg is installed and activated, the callout will be shown to Contributor users and above.
If the Classic Editor plugin is installed and activated, the callout will be hidden for all users.

You can learn more by reading “Try Gutenberg” Callout in WordPress 4.9.8.

Privacy fixes/enhancements

This release includes 18 Privacy fixes focused on ensuring consistency and flexibility in the new personal data tools that were added in 4.9.6, including:

The type of request being confirmed is now included in the subject line for all privacy confirmation emails.
Improved consistency with site name being used for privacy emails in multisite.
Pagination for Privacy request admin screens can now be adjusted.
Increased the test coverage for several core privacy functions.

This post has more information about all of the issues fixed in 4.9.8 if you’d like to learn more.

Download WordPress 4.9.8 or venture over to Dashboard → Updates and click “Update Now.” Sites that support automatic background updates are already beginning to update automatically.

Thank you to everyone who contributed to WordPress 4.9.8:

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2018 21:25:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Paul Biron";s: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:84:"WPTavern: Official Gutenberg Information Site Updated with Interactive Frontend Demo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82821";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:95:"https://wptavern.com/official-gutenberg-information-site-updated-with-interactive-frontend-demo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2132:"

The official Gutenberg information site has been updated to feature an interactive demo that can be manipulated on the frontend. It is based on Frontenberg, a site created by Tom Nowell, VIP Wrangler at Automattic. It loads an instance of WordPress with Gutenberg on the frontend so visitors don’t have to login or create a test site to try it.

Gutenberg’s new demo replaces the walls of text that were there previously, which described the vision and approach for the new editor and explained blocks in depth with screenshots. Instead, the updated page features shorter, more succinct explanations of the new editor as an interactive part of demo.

The demo is also live on all Rosetta sites, like fr.wordpress.org/gutenberg, so WordPress users from around the world can view it in their own languages.

WordPress contributors are feverishly working to prepare for the “Try Gutenberg” callout that will ship with WordPress 4.9.8, which is scheduled for Thursday, August 2nd. It will be many users’ first exposure to the new editor and the demo gives them a chance to experience it in a hands-on way before making a decision about installing it. Instead of dismissing Gutenberg out of hand based on a quick glance at the screenshots and text, users have the opportunity to test drive it without breaking anything.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2018 05:01:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:68:"WPTavern: WPWeekly Episode 325 – A Different Facebook for Everyone";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=82830&preview=true&preview_id=82830";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:75:"https://wptavern.com/wpweekly-episode-325-a-different-facebook-for-everyone";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2387:"

In this episode, John James Jacoby and I discuss what’s new in Gutenberg 3.4 and share our recent experiences with the editor. We talk about Facebook’s decision to shut down its API for apps to publish to user’s profiles on their behalf. This leads to a side rant of our user experience with Facebook and the history between it and Twitter.

We talk about what’s new in WordPress 4.9.8 RC 3 and when you can expect a final release. Last but not least, we discuss Slack’s acquisition of HipChat and share our reasons for joining Twitter.

Stories Discussed:

Gutenberg 3.4 Adds New Warning to Classic Editor When Editing Posts Containing Blocks

WordPress 4.9.8 RC 3 Released, Limits ‘Try Gutenberg’ Callout Visibility

Facebook Shuts Down API for Publishing to User Timelines, Impacts Jetpack’s Publicize Feature

WordPress Coding Standards 1.0.0 Released

WooSesh Virtual WooCommerce Conference to be Held October 18-19

Slack Acquires HipChat, Moves Blog from Medium to WordPress

WPWeekly Meta:

Next Episode: Wednesday, August 8th 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #325:
\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2018 02:02:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:82:"WPTavern: Easy Digital Downloads Substantially Reduces Prices for Extension Passes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82825";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:93:"https://wptavern.com/easy-digital-downloads-substantially-reduces-prices-for-extension-passes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3693:"

Pippin Williamson, founder of Easy Digital Downloads, published an apology on the company’s blog today admitting that it made a mistake in its pricing model for extension passes.

\n\n

In mid-June, the company introduced a new set of pricing options or passes. The passes come with a single license that provide access to a group of extensions. The prices for each pass were as follows:

\n\n

Personal Pass: $199
Extended Pass: $399
Professional Pass: $699
All Access Pass: $899

\n\n

After six weeks, Williamson noticed that customers were continuing to purchase individual extensions instead of the passes.

\n\n

“Our expectation and intent in creating the passes was for store owners to be able to purchase access to multiple individual extensions in a more economical way, but that’s not what happened,” he said.

\n\n

“Instead, store owners continued to purchase only the individual extensions they needed because the price tags of the passes were still too high. It is clear that we made a mistake in our pass pricing, and so today we’d like to apologize for that and announce new, lower prices.”

\n\n

After two weeks of testing, the prices of each pass have been significantly reduced to the following amounts:

\n\n

Personal Pass: $99
Extended Pass: $199
Professional Pass: $299
All Access Pass: $499

\n\n

In addition to the pricing changes, customers who purchased a pass between June 1st and August 1st are eligible for a refund. The refund is equal to the difference of the purchased price and the new price. Customers have until August 15th, to request a refund.

\n\n

Customers who purchased passes before the reduction will have their renewal amounts automatically changed to the lower price.

\n\n

Pricing WordPress products and services is tough and requires experimentation. There are numerous WordCamp sessions, articles, and in-depth guides on the subject but there’s not one answer that’s best for every business.

\n\n

Publicly admitting to a pricing mistake is one thing, but offering refunds to try to get customers on equal footing is going the extra mile.

\n\n

The company could have handled things in a way that’s not as beneficial to customers, but they chose what I think is a commendable way. Williamson’s closing statement speaks about the way he leads his company and how he makes these types of decisions.

\n\n

While we are far from perfect, as this pricing mistake clearly indicates, we are dedicated to doing right by our customers. To each of you, we would like to extend our most sincere thanks for sticking with us as we work through these changes
Pippin Williamson

\n\n

It’s a luxury to have business owners like Williamson in the WordPress economy.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2018 01:00:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:95:"WPTavern: Gutenberg 3.4 Adds New Warning to Classic Editor When Editing Posts Containing Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82772";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:106:"https://wptavern.com/gutenberg-3-4-adds-new-warning-to-classic-editor-when-editing-posts-containing-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:2614:"

Gutenberg 3.4 was released yesterday with fixes intended to prepare the plugin for converting existing content to blocks. A wave of new users will soon be testing the new plugin as the result of the “Try Gutenberg” prompt in WordPress 4.9.8. The release date has been pushed back to Thursday, August 2nd.

In early July, the Gutenberg team froze new features on the plugin and shifted to focus on bugs, enhancements, compatibility, and API stability. An overview of the major functionality shipping in Gutenberg is available as a list on GitHub. Gutenberg 3.4 continues refinements on these features.

In preparation for users switching back and forth between the new and old editors, this release adds a warning in the classic editor when users attempt to edit posts that contain blocks.

Shared blocks have been renamed to “Reusable blocks” to better convey their function.

Theme developers can now configure font sizes that show in the editor.

This release also adds other little enhancements, including an edit button for embed blocks, the ability to create a video block by dropping a video on an insertion point, RTL CSS, and accessibility improvements.

Check out the release post for a full list of all the enhancements and bugs fixes in Gutenberg 3.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:"Wed, 01 Aug 2018 16:46:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:43:"Dev Blog: The Month in WordPress: July 2018";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=6158";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2018/08/the-month-in-wordpress-july-2018/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6410:"

With WordPress 5.0 coming closer, there’s lots of work going on all across the project. Read on to learn about how we progressed in July.

\n\n

Release of WordPress 4.9.7

\n\n

On July 5, WordPress 4.9.7 was released, fixing one security issue and 17 other bugs across the platform.

\n\n

Would you like 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

The New WordPress Editor

\n\n

In the upcoming minor release of WordPress, 4.9.8, a new section in the dashboard will feature Gutenberg, the upcoming content editor for WordPress.

\n\n

Would you like to help build or test Gutenberg? Follow the Core team blog and join the #core-editor channel in the Making WordPress Slack group.

\n\n

Page Design Updates on WordPress.org

\n\n

Bit by bit we’re refreshing the design of WordPress.org. The latest pages to get a new treatment have been the Download page and user profiles.

\n\n

Would you like to get involved in the design refresh? Follow the Meta and Design team blogs and join the #meta and #design channels in the Making WordPress Slack group.

\n\n

The First WP-CLI Hack Day

\n\n

On Friday July 20, the WP-CLI team held their first hack day — a global event encouraging people to contribute to the official command line tool for WordPress.

\n\n

Would you like to get involved in contributing to WP-CLI? Follow the team blog and join the #cli channel in the Making WordPress Slack group.

\n\n

Begin at the Beginning…

I was a youngish mother of a youngish child and a full time stay at home parent. I didn’t work outside the home; I was raising my kid. That was both a privilege and a problem. I realized that, as a mother consumed with caring for this new human, I was beginning to lose the very strong sense of identity that I’d always had.

This was my first experience with not knowing who I was. I always knew who I was, even if I didn’t know who I wanted to be. As a mother though, most of who I am was sucked into caring for my family. Not sleeping. Not taking proper care of myself. Not taking time for my interests. Putting the others in my house before me and saying that it was what I wanted.

Narrator: It wasn’t.

There was a pivot point. A moment before my daughter turned three. When I realized that if she were to choose to become a mother I would not want her to go down the same path of self denial that I had. I would want her to be who she is first and a mother second so that she could be the best self and mother she could be.

And I realized that was something I could only show by example. But how to start? I’d always been a writer. I often say that I only learned to read so that I could write. Journaling, short stories, poetry. Sometimes just long strings of thoughts and observations that wouldn’t leave my head until I wrote them down. I would write out long “stories” on MySpace about my experiences and realizations. I would scrawl poetry on scrap paper laying around the house. None of it was enough.

Also, as I understand is fairly typical for a stay at home parent, I had no one to talk to most of the time except for my small child. And while she was super awesome and receptive to any conversation I may want to start, they all tended to transition to discussion of My Little Ponies or a request for ice cream or screen time. So I looked for something more. For a place to discuss the mommified version of myself with no one and everyone. I started a blog.

But it wasn’t on WordPress.

Go On…

I wrote and I wrote and I wrote. My experiences, my kid’s experiences. Dreams and hopes and bad poetry. And I found a group of people who shared with me their struggles and dreams as they dove into mine. A web of women and men who got me. Who got what I was going through. Who got what I was doing. A community of individuals, not all like minded, but all understanding.

And then one day I was asked to write for a city blog, and then another. And as my writing began to expand I found other communities. My sense of self was first preserved but then invigorated and it grew and I stretched my arms and I stretched my wings and I realized I was beginning to feel whole for the first time in a long while.

But using multiple platforms for my blogging gave me the understanding that the platform I was using was restrictive and unsatisfying. Clunky.

And that’s when a friend mentioned WordCamp Portland. It was this new thing. We were doing it for the first time. A bunch of bloggers getting together to talk about WordPress and blogging and stuff.

I had no idea what WordPress was. But my friend said they needed some volunteers to help out, and I’m always one to support my friends, my community. So I asked what I needed to do to help.

“Move your blog to WordPress”

And so I did. And something clicked. Once I had moved to a WordPress site I found my passion for blogging was something more. I played with themes, I made headers that felt like art pieces, I helped others transfer their content, set up their sites. I introduced them to a community that I was just beginning to get to know.

And then there was a cascade of activity. More blogs, podcasting, events, community, and every year there was WordCamp Portland. And I continued to learn and grow my skills as a writer, as a blogger, as a podcaster, and as a WordPresser. I continued to volunteer, and then to speak, and to help organize.

And on…

But life changes. Sometimes for the better sometimes for the worse. But change is hard. People change or stay the same. Relationships change. Life changes. Sometimes all of the above. So I ended a marriage and found myself stumped. I knew who I was, but who I happened to be was a stay at home mom who hadn’t worked outside the home in eight years and had no marketable skills that I could find that would also allow me to continue to be home for my kid.

And I panicked and I procrastinated and then I found an opening. A small startup I knew through my interactions with the community needed a customer support person who also knew WordPress.

A light went on. And I had a job for the first time in eight years. And I knew what I was doing. And I was good at it. And I continued to blog. A little. And I stuck to the little tiny fringes of the WordPress community I knew. Still not realizing how big the rest of it was.

The Portland WordPress folks were like a river feeding into the ocean of the worldwide community. But I’d only ever stood on the shores of the river and dipped my toes in. All that was about to change.

Till You Come to the End…

But as I said at the beginning, it’s not that simple. There is no end. There is just more. More stories, more people, more learning, more community. And that’s where we begin the part of the story that tells us where I am today.

This part begins with an email from a community friend with a link to a job posting. And a new beginning.

I was working happily at that small startup, spreading my wings. But starting to feel a little bit like my passion wasn’t being put to use when that email arrived. A link to a job posting working as a sponsored volunteer within the WordPress community and question. It was a simple question. “Do you know anyone who would kick ass at this job?”

DID I? I was reeling from the possibility and doubled over with imposter syndrome and fear. Fear that I wasn’t good enough. Fear that they wouldn’t like me. Fear that I’d be leaving my boss in the lurch.

So I did what I always did at that time. And what I still do to this day. I procrastinated. I talked. I thought. I woke up in the middle of the night in a panic thinking I had forgotten something. Thinking I had done something wrong.

But as I sat there one day tinkering on the startup’s site, scheduling posts, checking in on our customers all while getting my daughter ready for school that morning I realized that it was time to set aside those fears. To look that imposter syndrome right in the eye and say “not today” and I started putting together my resume and working on the cover email.

No one was more surprised than I when I found myself two months later starting my first day at Automattic.

It’s been about 5 and a half years since that email landed in my inbox. It’s been more than a decade since WordPress landed in my heart and I’m proud to make my living in the wide wonderful world of WordPress. As I write this story for all of you to read—not a cautionary tale I hope, but an inspirational one—I’m just a few days away from the end of my three-month sabbatical (a benefit that all Automatticians are eligible for after 5 years.)

It’s been a time of rest, readjustment, relaxation. Of edification. But it’s also been a renewal. A time to look back at how I got where I am and remember how lucky I am to be here today. And I owe it all to a little bit of gumption and to the amazing community of WordPressers who opened their world to me. And also to everyone else who is willing to be a part of this great big community founded on open source. On WordPress.

The post Begin at the Beginning 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, 01 Aug 2018 08:00:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"Cami Kaos";s: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:86:"WPTavern: WordPress 4.9.8 RC 3 Released, Limits ‘Try Gutenberg’ Callout Visibility";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82803";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:90:"https://wptavern.com/wordpress-4-9-8-rc-3-released-limits-try-gutenberg-callout-visibility";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1701:"

WordPress 4.9.8 Release Candidate 3 is available for testing. This version includes one important enhancement that limits the visibility of the ‘Try Gutenberg’ callout.

\n\n

If Gutenberg is not installed or activated on a site, the callout will be displayed to users with the install_plugins capability. If Gutenberg is activated, the callout will be shown to users with the edit_posts capability.

\n\n

Limiting the visibility of the callout to a specific subset of users will avoid inundating the WordPress.org support forums with Gutenberg support requests. A concern that was expressed by Daniel Bachhuber four months ago.

\n\n

“There’s a good amount of fit and finish to be desired before rolling out to a large number of unacquainted users,” Bachhuber said. “We’re not quite over the hump on the issues we do already know about. There’s not a ton of sense in having 10,000 users re-report them.”

\n\n

Other than this change, the change log from WordPress 4.9.8 RC 1 remains the same. WordPress 4.9.8 was originally scheduled to be released today, but has been rescheduled for Thursday, August 2nd.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 01 Aug 2018 00:14:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:105:"WPTavern: Facebook Shuts Down API for Publishing to User Timelines, Impacts Jetpack’s Publicize Feature";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82768";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:112:"https://wptavern.com/facebook-shuts-down-api-for-publishing-to-user-timelines-impacts-jetpacks-publicize-feature";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4690:"

In the aftermath of the Cambridge Analytica data scandal, Facebook is tightening its control on third-party applications and will no longer allow apps to post to user profiles. In April, the platform announced sweeping changes to the publish_actions permission, which allowed apps to publish to users’ timeline on their behalf.

On August 1st, 2018, the Live API publish_actions permission, which allows an app to publish on behalf of its Users, will be reserved for approved partners. A new permission model that allows apps to publish Videos to their User’s Groups and Timeline will be created instead.
\n
Access to the Pages APIs requires re-submission of the application for review before August 1, 2018. This will be required to continue publishing live and VOD video to Pages, as well as reading insights.

Facebook is notorious for swiftly changing its APIs in ways that break apps (sometimes without warning), often sending developers scrambling. For a long time, apps auto-posting to user timelines was part of the wild west of app permissions granted without much oversight from Facebook. Users often unknowingly gave permission to apps that would collect data and spam their Facebook connections with posts made on their behalf.

Those days are over, but an unfortunate byproduct of this restriction is that apps like WordPress.com and Jetpack’s Publicize feature can no longer automatically publish posts to user timelines. This change also adversely affects apps like Buffer and Hootsuite that allow users to schedule and publish posts to their social accounts.

Jetpack 6.3.3 removes the ability for users to select Facebook Profile connections and displays a notice regarding existing connections, so users will be aware of which auto-posting connections they are losing. Besides Jetpack, this Facebook API change affects tens of thousands of users who have this functionality implemented through one of many other plugins on WordPress.org.

Users are now required to manually share their posts to their timelines. They can no longer schedule content to be shared to Facebook at specific times for different audiences.

Auto-posting to Facebook Pages still works, and one option users have is to convert their Profile to a Page or set up a new page. This may not be a suitable alternative for bloggers and those whose writing is not attached to a business or an organization.

In a recent post on his blog, Automattic CEO Matt Mullenweg commented on Facebook’s decision to turn off auto-posting to profiles.

“As it turns out, Facebook also is turning off the ability for WordPress sites — and all websites — to post directly to users’ profile pages,” Mullenweg said. “The decision to shut down the API is ostensibly to fight propaganda and misinformation on the platform, but I think it’s a big step back for their embrace of the open web. I hope they change their minds.”

If only a select few “approved partners” are allowed to automatically broadcast to user timelines, it puts smaller players at a disadvantage, requiring manual sharing each time they publish. Facebook is setting itself up as a gatekeeper that enables news from a small selection of partners to keep pumping through the platform on schedule. Individual voices on smaller websites are no longer able to syndicate to the Facebook platform unless they decide to create a Page.

Put a different way, the only syndicated content allowed on Facebook will be through channels the company can monetize – business/organization Pages or partners who are approved to post to user timelines. Users who care about retaining their Facebook audiences will need to remember to manually post their content to the social network after August 1, 2018, when the API changes go into effect.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 31 Jul 2018 22:11:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:50:"Matt: My Recode Decode Interview with Kara Swisher";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=48262";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://ma.tt/2018/07/my-recode-decode-interview-with-kara-swisher/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1780:"

“We want to make the best tools in the world, and we want to do it for decades to come. I’ve been doing WordPress for 15 years, I want to do it the rest of my life.”

\n\n

The last time I chatted with Kara was in 2013 in the back of a pedicab in Austin. This time I got to sit in the red chair at Vox headquarters in San Francisco, and per usual Kara was thoughtful, thorough and to the point: we talked about WordPress and the future of the open web, the moral imperative of user privacy, and how it all relates to what’s going on at Facebook.

\n\n

(As it turns out, Facebook also is turning off the ability for WordPress sites — and all websites — to post directly to users’ profile pages. The decision to shut down the API is ostensibly to fight propaganda and misinformation on the platform, but I think it’s a big step back for their embrace of the open web. I hope they change their minds.)

\n\n

Kara and I also talked about distributed work, Automattic’s acquisition of Atavist and Longreads, and why every tech company should have an editorial team. Thanks again to Kara and the Recode team for having me.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 31 Jul 2018 08:31:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:12;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:51:"WPTavern: WordPress Coding Standards 1.0.0 Released";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82761";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:62:"https://wptavern.com/wordpress-coding-standards-1-0-0-released";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2215:"

After nine years since the project began, version 1.0.0 of the WordPress Coding Standards is available for download. The WordPress Coding Standards is a collection of PHP_CodeSniffer rules or sniffs to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, including the official WordPress Coding Standards.

\n\n

In addition to being a big milestone, 1.0.0 contains breaking changes. “A number of sniffs have been moved between categories and the old sniff names have been deprecated,” Juliette Reinders Folmer, a significant contributor to the project, said.

\n\n

“If you selectively include any of these sniffs in your custom ruleset or set custom property values for these sniffs, your custom ruleset will need to be updated.”

\n\n

The WordPress-VIP ruleset has been deprecated as well. “This ruleset has not been valid for some time, as we have our own VIP coding standards, available for public use,” David Artiss, a member of the WordPress.com VIP support team, said.

\n\n

“If you are a VIP client and you are not using the alternative rulesets, then we would strongly recommend switching to these. If you used the WordPress-VIP ruleset for any other reason, you should use WordPress-Extra or WordPress instead.”

\n\n

Those who use the WordPress Coding Standards Sniffs are strongly encouraged to read the changelog before updating. WordPress Coding Standards is a free, open source project, that’s available on GitHub where contributions are welcomed.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 30 Jul 2018 23:43:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:101:"WPTavern: David Needham Chats about Venturing Outside WordCamp to Visit Other Open Source Communities";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82750";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:112:"https://wptavern.com/david-needham-chats-about-venturing-outside-wordcamp-to-visit-other-open-source-communities";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1439:"

While at WordCamp Europe I had the chance to chat with David Needham, a developer advocate at Pantheon, about his session titled “Intro to Drupal for WordPress Folks.” Needham frequently travels between the WordPress and Drupal communities, representing his company as a developer liaison. He has spoken at various Drupal camps and WordCamps and is also one of the organizers for WordCamp US 2018 in Nashville.

During our chat, Needham discussed some of the more notable differences between the WordPress and Drupal communities and how the two can inspire each other in various ways. He encouraged attendees at his session to venture outside of WordCamps and said he hopes to see more collaboration across the platforms in the future. From his unique vantage point, Needham said he doesn’t think CMS rivalries are as big of a deal as they used to be.

“We’re realizing that we’re really not competing,” Needham said. “The internet is a big place and there’s plenty of room for all of our communities to work together – especially since our values are so closely aligned already. If there is a rivalry, it feels a little bit more like a friendly sibling rivalry than anything.”

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 30 Jul 2018 21:50:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:83:"WPTavern: WordPress Developers: Learn How to Convert Shortcodes to Gutenberg Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82737";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:93:"https://wptavern.com/wordpress-developers-learn-how-to-convert-shortcodes-to-gutenberg-blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2208:"

Gutenberg contributor Gary Pendergast has published a handy sample plugin that demonstrates how to convert shortcode functionality to a Gutenberg block.

\n
Do you have a bunch of shortcodes that you’d like to really easily turn into blocks? Here’s a sample plugin showing how to re-use your exisiting shortcode functionality in a block!https://t.co/bppHcumBlB
\n
— Gary (@GaryPendergast) July 29, 2018

The first file shows a basic example of how to register a block with JavaScript and add block inspector controls to the sidebar. The second file is the PHP code for the plugin that converts the existing shortcode logic into a block that will work inside the new editor.

“This sample uses the ServerSideRender element,” Pendergast said. “It’s critical to remember that ServerSideRender is a stepping stone to a full block editing experience: having to call back to the server to re-render is a worse UX than native JS rendering. Use ServerSideRender to get your existing functionality ready for WordPress 5.0 now, and plan to phase it out over time.”

With WordPress 4.9.8’s “Try Gutenberg” callout just around the corner, this sample plugin may be helpful for developers who have created custom shortcode plugins for clients. If you’re not sure where to start, Pendergast’s sample plugin makes Gutenberg block creation more approachable. The Gutenberg handbook has more in-depth documentation for developers who want to improve their blocks beyond this basic example.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 30 Jul 2018 13:47: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: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:52:"WPTavern: Plugin Review: Theme Support for Gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82710";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:62:"https://wptavern.com/plugin-review-theme-support-for-gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2655:"

As Gutenberg nears a merge with WordPress, Theme Authors are running out of time to ensure that their themes are compatible. The Gutenberg handbook has an excellent article on how to opt-in and add support for enhanced features.

\n\n

Most themes will present the default blocks without any issues as the blocks themselves provide their own styles. If you use a theme that does not fully support Gutenberg such as the Wide or Full Block Alignment options, the Theme Support for Gutenberg plugin may be for you.

\n\n

Created by Weweaver, Theme Support for Gutenberg claims to allow most WordPress themes to be compatible with Gutenberg. In addition to theme support, the plugin adds a Classic Editor button to the admin bar to easily switch between Gutenberg and the Classic Editor.

\n\n

Since a default WordPress theme is used to show how this plugin is beneficial, I decided to try it for myself. I installed the plugin on a fresh install of WordPress 4.9.7, Gutenberg 3.3, and the latest version of Twenty Sixteen. I published a Gutenberg Demo post which uses many of the default blocks.

\n\n

Twenty Sixteen Looks Better Without It

\n\n

Here is what the Gallery block looks like in Twenty Sixteen with the plugin disabled. The content looks good and fits within the content column.

\n\nTheme Support for Gutenberg Disabled\n\n

When the plugin is enabled, the images are so large, a horizontal scroll bar appears.

\n\nTheme Support for Gutenberg Enabled\n\n

The plugin includes additional styling for default blocks. One block that doesn’t benefit from the enhanced styles is the Video block. With the plugin disabled, the video block appears normally.

\n\nVideo Block With The Plugin Disabled
\n\n

With the plugin enabled, the video block overflows the content column and breaches into the left sidebar.

\n\nVideo Block With The Plugin Enabled \n\n

Although the plugin initially shipped with no options, version 0.2 includes new settings that provide better compatibility for some themes. I checked the box to disable Fitvids support which solved the video block issue. However, the other options had no effect on the oversized image blocks.

\n\nTheme Support Options\n\n

Twenty Sixteen and Twenty Seventeen do not work well with this plugin. There may be themes, particularly older ones that benefit, but more modern themes will likely be ok without it.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 27 Jul 2018 22:42:22 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:73:"WPTavern: WooSesh Virtual WooCommerce Conference to be Held October 18-19";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82508";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://wptavern.com/woosesh-virtual-woocommerce-conference-to-be-held-october-18-19";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4964:"

WooSesh, a new two-day virtual conference focused on WooCommerce topics, will be held October 18-19. While wrapping up another successful edition of WordSesh, Brian Richards announced WooSesh as the next event coming under the WordSesh brand. On Wednesday, nearly 500 attendees joined WordSesh. People tuned in from around the world, although the audience was heavily US-based due to the time the event was scheduled.

Since WooConf is not happening this year, WooSesh is an exciting alternative that will be accessible to anyone in the world. Co-organizers Brian Richards and Patrick Rauland will be hosting eight presentations each day, so the event will last between 8-10 hours both days, including breaks and announcements.

“Once we learned that WooConf wouldn’t be taking place this year we reached out to our friends at Automattic to see if we could work with them as well to still provide a high-quality event but for a much more global audience,” Richards said.

WooCommerce is sponsoring the entire event, making it free for all live attendees. Richards said they are working with other prominent companies in the WooCommerce space who are lending their knowledgeable staff as presenters, as well as providing the event with digital swag for attendees.

WooSesh organizers are employing an interesting concept for encouraging attendance and engagement. The conference will have a $200 ticket price for those who do not attend live. Those who register in advance and attend live will receive the $200 ticket for free.

“That means if a person joins the mailing list and shows up for the event, they’ll be able to experience the whole thing at no cost to them,” Richards said. “Similar to WordSesh, a ticket grants attendees access to the entire broadcast, chat, recordings, real-time transcriptions, and some cool digital swag. But with WooSesh they’ll also get some targeted follow-up content, and perhaps a private community, to further help them succeed and increase the impact of this conference.

“And I think it’s in everyone’s best interest to register and attend live – at least trying to make it to one of the sessions across the two days – so they can get all of that for free.”

Richards said recordings may still make it out there for people to view afterwards but none of the other perks and follow-ups will be available without purchasing a ticket or attending live.

“We talked about asking people for a credit card up front and building a mechanism that would either charge them after the fact (like a pre-order) or charge them up-front but then refund them after the fact,” Richards said. “Instead we’re going with the simpler route and asking only for a person’s name and email address up-front. If they come to the live event they’ll be able to access all of the content afterwards just as if they had paid, and if they don’t attend live they’ll instead be greeted with a payment form.”

Building on their collective knowledge of organizing successful in-person and virtual conferences, Richards said he and his co-organizer wanted to reduce the friction as much as possible for people getting into their seats and engaged with the speakers and other attendees.

“Making it a virtual event already knocks down a ton of barriers,” Richard said. “Making the content available for free eliminates even more. Except that, people will often discredit free things and we didn’t want anyone to think of this content as any less valuable or serious than it really is.”

WooSesh organizers plan to host compelling case studies, as well as talks about SEO, security, tips for building different kinds of e-commerce stores, and share advice from others’ hard-earned lessons. The event will also host sessions for developers that delve into WooCommerce architecture, performance, how to build and support custom extensions, and how to expand service offerings to better support e-commerce projects.

“Our biggest goal with WooSesh is that it will help store builders as well as coders to have more impact with what they build,” Richards said. “Specifically, we’d like to see them make some measurable progress in their own goals, whether that’s more sales, better customer experiences, greater depth of knowledge, or otherwise. We’re also hoping that some of these talks will inspire attendees to do more than they originally thought possible – either for their own e-commerce stores or for their customers/clients.”

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 27 Jul 2018 22:34: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:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:17;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"WPTavern: Slack Acquires HipChat, Moves Blog from Medium to WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82681";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:79:"https://wptavern.com/slack-acquires-hipchat-moves-blog-from-medium-to-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:2732:"

Slack announced today that it has acquired HipChat from Atlassian. The friendly rivalry between the two competing group chat platforms will be laid to rest as Slack plans to retire HipChat and Stride. Atlassian will receive a stake in Slack’s business in exchange for shutting down its chat collaboration services and migrating all of its customers over.

Atlassian acquired HipChat in 2012 with the intention of scaling the business but found a formidable challenge in taking on the well-funded, market-dominating Slack app. As of May 2018, Slack reported 8 million daily active users and 70,000 paid teams. More than half of the app’s users are outside the U.S. and 65% of companies in the Fortune 100 pay to use Slack.

Atlassian and Slack are now joining forces to compete against Microsoft, who jumped into the enterprise collaboration market in 2016 with its Teams product. Teams’ free tier offers support for up to 300 people, with unlimited chat messages and search, and is aimed squarely at competing with Slack.

The news was announced on “Several People Are Typing,” the official Slack blog, which has just moved from Medium to WordPress. It is being hosted on the WordPress.com VIP platform.

\n
I can’t really answer the question (bias, yada yada), but it sure is good to be hosting the Slack blog at @WordPressVIP https://t.co/86aQQ5Pkaz
\n
— Simon Wheatley (@simonwheatley) July 26, 2018

The answer to that question, by the way, is ‘yes.’

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 27 Jul 2018 02:55:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:61:"WPTavern: How to Create A Gutenberg Block Attributes Glossary";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82684";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:72:"https://wptavern.com/how-to-create-a-gutenberg-block-attributes-glossary";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1242:"

If you want to see what Gutenberg blocks are available on a site along with their attributes, check out the Block Attributes Glossary plugin by NC State’s Office of Information Technology and Design.

\n\nBlock Attributes Glossary Index\n\n

The plugin adds a Glossary Attributes Block to Gutenberg that when added to a post or page, displays an index of blocks that are available. Clicking on a block name will display its attributes.

\n\nAtomic Blocks Drop Cap Block Attributes\n\n

This is especially useful for creating block templates. Note that if you install plugins that add new blocks, you’ll need to visit the post or page that has the glossary, remove the Glossary block, and re-add it.

\n\n

You can see a live demo of this plugin in action by visiting NC State’s OIT Block Attributes Glossary. The plugin is not available from the WordPress plugin directory but you can download it for free from the project’s Github 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:"Thu, 26 Jul 2018 20:47:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:93:"WPTavern: Font Awesome 5.2 Adds 372 New Icons, Introduces Automotive and Education Categories";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82617";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:103:"https://wptavern.com/font-awesome-5-2-adds-372-new-icons-introduces-automotive-and-education-categories";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3091:"image credit: Font Awesome\n

Font Awesome 5.2 was released yesterday with two new categories and 372 new icons, bringing the total number of free icons to 1,295. The open source vector icon font is used on more than 22 million sites across the internet. It’s also a popular icon font with WordPress theme and plugin developers.

Version 5.2 introduces automotive and education categories, which should be useful to fill the gaps for designers and developers creating sites around these subjects. The release also adds 66 new and updated icons to the Medical category and 126 new and updated Maps icons.

Font Awesome, originally created by Dave Gandy, is an SIL OFL-licensed icon font, with the code under the MIT License. Thanks to its GPL-friendly license, the icon font is widely used in WordPress’ theme and plugin ecosystem in both commercial and free products. Font Awesome’s Github issues queue is also loaded with icon requests that would be used in niche WordPress themes, as well as icons for WordPress-related company logos.

Two years ago, Font Awesome announced the beta release of its new CDN, which allows developers to implement it using a single line of code to bring the icons and CSS toolkit into their projects. At that time, Font Awesome was used by more than 300 plugins on WordPress.org. In 2018, searching the official plugin directory turns up more than 800 plugins that make use of the icon font in some way. Thousands of free and commercial themes also use it to provide users with easy customization options.

Font Awesome support for Gutenberg is going to be fairly important, as hundreds of thousands of websites are using plugins like Better Font Awesome, Font Awesome Shortcodes, and Font Awesome for Menus to allow users to add icons to content and menus. Currently there are no Gutenberg-compatible plugins for adding Font Awesome icons to 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:"Thu, 26 Jul 2018 18:08:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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:62:"WPTavern: WPWeekly Episode 324 – Getting NC State Gutenready";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=82650&preview=true&preview_id=82650";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wptavern.com/wpweekly-episode-324-getting-nc-state-gutenready";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1804:"

In this episode, John James Jacoby and I are joined by Jen McFarland, Web Services Coordinator at NC state’s Office of Information and Technology. McFarland describes how the campus is using WordPress, what they’re doing to prepare students and staff for Gutenberg, and what they’ve experienced thus far in the transition.

Near the end of the show, we cover WordPress 4.9.8 RC 1 and provide an update on WP-CLI Hack Day.

Stories Discussed:

Gutenberg 3.3 Released, Adds Archives and Recent Comments Blocks
\nWordPress 4.9.8 RC 1 Released
\nWP-CLI Hack Day Is A Success
\nGoogle Chrome Rolls Out “Not Secure” Warning for Plain HTTP Sites

WPWeekly Meta:

Next Episode: Wednesday, August 1st 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #324:
\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 26 Jul 2018 01:01:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:63:"WPTavern: Frontenberg Lets Users Test Gutenberg on the Frontend";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82526";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:74:"https://wptavern.com/frontenberg-lets-users-test-gutenberg-on-the-frontend";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2733:"

WordPress 5.0 will bring the world a brand new editor that is currently code-named Gutenberg. If you have been hearing the buzz around Gutenberg but have yet to try it, Frontenberg (testgutenberg.com) is the easiest way to check it out.

Frontenberg allows visitors to try Gutenberg without having to set up a separate test site of their own. It loads an instance of WordPress plus the Gutenberg plugin on the frontend so visitors don’t have to log in to play around with the new editor.

Frontenberg has a limited range of capabilities for testing purposes. Users have access to a pre-populated media library but cannot upload images to the test site. It’s also not possible to create shared blocks or save the post. Attempting to save an action will trigger an “updating failed” notice. Apart from those few limitations, Frontenberg allows users to test nearly all of Gutenberg’s features.

The tool was created by Tom Nowell, VIP Wrangler at Automattic. He launched the frontend testing instance on his own website at frontenberg.tomjn.com and the WordPress VIP team built its own version to handle more traffic. Frontenberg contains links to numerous Gutenberg resources, including vipgutenberg.com, which has some free training videos the team created for VIP clients.

Nowell has written a post called How Frontenberg Works for developers who are interested in the tech behind the tool. In it he describes the challenges he encountered in building Frontenberg and the solutions he wrote to make it work.

The “Try Gutenberg” prompt will soon be going out to millions of users in WordPress 4.9.8. Those who conservatively opt to use the Classic Editor plugin can still give Gutenberg a try using the Frontenberg tool or install it on a test site to see how interacts with themes and 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:"Wed, 25 Jul 2018 19:59: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: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:69:"WPTavern: WordPress Core Fields API Project is Seeking New Leadership";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82602";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:80:"https://wptavern.com/wordpress-core-fields-api-project-is-seeking-new-leadership";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10702:"

In 2014, Pods lead developer, Scott Kingsley Clark, took over the primary lead role for the Metadata UI project. In 2015, the Metadata UI project was reborn as the Fields API.

\n\n

The Fields API was developed to allow registering fields to different screens in the admin area through a single API. New meta boxes and fields within them could be added to posts while new sections and fields could be added to the profile screen.

\n\n

The goal of the API is to integrate with all of the various admin screens including, Posts, Terms, Users, Media, and Comments and provide standardization.

\n\n

Clark has been leading the project for three years and despite seeing renewed interest last year, announced in the project’s Slack channel that he is stepping down.

\n\n

It is with a heavy heart that I must pass the torch on this project. After hundreds of hours of my time, I no longer believe I can effect change within WordPress core.
The Fields API vision was too big, too much of an undertaking for any one person. I believe so deeply that WordPress needs a Fields API, but the journey to where we are at with the Fields API has been long and arduous.
The truth is, I burned out years ago while building the first and second prototypes. Not everyone agreed on how to architect the code, it went through many revisions based on core contributor feedback. I just couldn’t get enough people excited about it, I couldn’t get enough companies and people interested in supporting it.
I need to let someone else have their chance, I am dragging it down. If someone steps up to lead in the future, then I would be happy to assist where I am able to. But I am unable to continue leading the Fields API proposal/project. I am sorry, please accept my apology and I hope you can forgive me for failing to take this project over the finish line. I still believe to be such a vital part of WordPress’ future success.
Scott Kingsley Clark

\n\n

The Trials and Tribulations of Leading an Open Source Project

\n\n

In the following interview, Clark explains why he feels personally responsible for the project’s lack of progress, why the API is important for WordPress’ future, and reflects on what he could have done differently.

\n\n

Are you looking to pass the torch on to anyone in particular?

\n\n

No, I’m not sure who would have the drive and the clout to see the project through. It’s a large scale project that should be approached with a long-term vision but in small enough increments to make it into WordPress core. It’s a lot to ask of somebody, it’s also not a priority for people right now since they are distracted by Gutenberg being released in the near future.

\n\n

Why is the Fields API a vital part of WordPress’ future?

\n\n

People look at WordPress today and wonder how they ever survived without the REST API. Well, at least I know I do! The same thing can be said about the Fields API even though it’s not there yet. There are so many cases where it’s frustrating to build solutions for WordPress across all of the different hooks.

\n\n

For consistency, it’s the wild west out there. You get a meta box registered and you fill it with whatever you want. You need your own CSS to style the form fields and everyone has their own idea of how this interface should look. You are in charge of your own responsive layouts that are mobile-friendly, there’s just so much you have to handle on your own. You should be able to customize appearances, but every place you want to add a field or form to should really have a proper API.

\n\n

Long-term, imagine registering fields to WordPress like you register post types. Imagine fields and their configurations being available to the REST API and accessible through the WordPress App or other custom apps.

\n\n

The whole world opens up because you have a consistent API, the whole world make sense because you have a consistent interface for those fields across the various edit screens. Posts, terms, comments, users, media, even the Customizer would all have the same underlying API to add groups, panels, and fields to their screens.

\n\n

If Gutenberg was done after the Fields API was in, migration for folks wouldn’t have been as difficult. Gutenberg could have automatically shown all of the Fields API interfaces like it does for the meta box backward compatibility. It would have looked so much nicer too.

\n\n

Taking some time to reflect, what could you have done differently to get more core contributors to buy into the project and turn it into a higher priority?

\n\n

I’m not sure, it’s a delicate balance of taking input and being confident in the end result. At first, the feedback was about how the API was foreign for WordPress, they asked if it could be similar in structure to other APIs such as the Customizer.

\n\n

We scrapped the code and rebuilt from the ground up as a fork of the Customizer, it even supported having the Customizer utilizing the Fields API too. At the height of development, we had all areas of the Fields API implemented.

\n\n

Core releases were moving pretty fast, there was a lot of code changes from WordPress release to release that we had to keep up with because we had essentially created a project that was a giant patch for WordPress.

\n\n

There weren’t enough hooks in place to do what we needed to do, and many sections were not extensible because of code decisions that marked themselves as ‘final’, which means you can’t extend a specific class to customize how it works.

\n\n

I wish I could have been at all the big WordCamps in the US and Europe, essentially lobbying for this feature. Gathering supporters and such, it feels like politics in a way. I hung around in Core dev meetings, trying to bring it up. I tried to legitimize the feature by having a dedicated channel in the official WordPress Slack, posting updates on https://make.wordpress.org/core/, and holding weekly meetings.

\n\n

Ultimately, I prioritized my time for development over the time to gather the troops. That was the downfall, I began to burn out quickly after the first few rewrites as I had many other responsibilities elsewhere on top of Fields API.

\n\n

It’s not like companies will easily want to pay you to work on a project like this indefinitely, even though both WebDevStudios and 10up gave me time to push it forward. It wasn’t a blank check, at some point I had to get back to billable work. From then on, it was all in my free time and that was difficult to manage during times of financial stress and house selling/buying.

\n\n

There’s demand for a Fields API in core but not enough hands to build it. Why do you think that is?

\n\n

Everyone is focused elsewhere. There’s a lot of areas of WordPress that need people’s attention. There are things like Accessibility that deserve a lot more attention than it gets. But the focus to me, seems to be on Gutenberg and REST API.

\n\n

Gutenberg especially has been a huge time sink for people contributing and people implementing. It’s a really large feature. It’s definitely larger in scale than Fields API, it’s like a whole new app that lives in WordPress. Integration with it has required a lot of education and trial/error. People’s focus is where it needs to be right now. It’s just unfortunate that Gutenberg came before Fields API in terms of priority and interest level.

\n\n

What advice would you give to the next Fields API project leader?

\n\n

This is a big project, everyone will want to say it should be a certain way. You have to evaluate the options and put forth something bite sized for core to start with. Build upon that, but never lose sight of the long-term goal of integration across all of the WordPress screens. Even the front-end comment forms could thrive with the Fields API.

\n\n

Why do you feel personally responsible for the project not being a core priority?

\n\n

At one point, we had momentum. We had at least three to four people who were active. It fell apart because I ran out of time. It’s my shortsightedness, it’s my fault. I spent hundreds of hours developing the project over a couple of years. I should have left myself much more time for organizing the feature proposal text and keeping the fires burning in our contributors’ hearts.

\n\n

Considering the time and effort you’ve put into the project the last few years, do you feel any sense of relief passing the torch on?

\n\n

If the torch gets passed or picked up, I will feel a ton better. The main relief is that it’s officially not a weight I have to carry alone any longer. It’s okay to try and fail, it’s still sad though.

\n\n

I hope that someone or some company steps up and puts time into this. They could even reignite the fire in my own heart that burned itself out. For now, I have one less major to-do item. I still have a hefty plate but it’s no longer as heavy of a burden.

\n\n

While the immediate future of the project is unclear, those interested in taking it over are encouraged to read posts marked with the Fields API tag on Make.WordPress.Core to learn about its history. You can also check out the project’s Github page.

\n\n

If you’re interested in taking over the project, you can contact Clark on Twitter, Slack, or through his website.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 25 Jul 2018 16:53:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;a:6:{s:4:"data";s:11:"\n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"HeroPress: Global Unity";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://heropress.com/?p=2596";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:91:"https://heropress.com/global-unity/#utm_source=rss&utm_medium=rss&utm_campaign=global-unity";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3268:" Pull Quote: I am quite lucky to wake up every morning and work, all on my own, in a country where 54% of the population are unemployed and over 70% are youth.

Pull Quote: I am quite lucky to wake up every morning and work, all on my own, in a country where 54% of the population are unemployed and over 70% are youth.

One of the things I’ve loved most about HeroPress is getting to know people far away. It’s getting harder and harder to name a country where I can’t say “Hey, I have a friend there!”. This week I’m in Australia for WordCamp Sydney, and I’m crazy excited about all the people I’m going to meet. The global unity of the WordPress community is exhilarating.

The replay essay I picked for this week is titled “A Bottomless World of Possibilities” by Jamaal Jaamac in Mogadishu, Somalia. His world is so completely different from mine that sometimes I even have a hard time asking the right questions to find out what it’s like.

Jamaal doesn’t live in a place where good work comes easy or often. It’s chiseled out of society with labor and love. There’s a stereotype that people in poor countries are lazy, but I think they have to be stronger and work harder just to make it. Jamaal is one of my heroes.

Check out his essay.

A Bottomless World of Possibilities

The post Global Unity 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, 25 Jul 2018 10:52:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:79:"WPTavern: Google Chrome Rolls Out “Not Secure” Warning for Plain HTTP Sites";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82489";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://wptavern.com/google-chrome-rolls-out-not-secure-warning-for-plain-http-sites";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7926:"

As part of a long term plan to push the web to adopt HTTPS encryption, Google Chrome is now marking all plain HTTP sites as “not secure,” as of July 24, 2018, with the release of Chrome 68. Previously, the “not secure” warning was hidden behind the security indicator in the URL bar as shown below.

That warning has become more prominent with the release of Chrome 68. The browser now immediately displays the “Not secure” message in the omnibox for all HTTP pages.

Today Google announced a time frame for eventually marking HTTP sites with a red “not secure” warning:

Eventually, our goal is to make it so that the only markings you see in Chrome are when a site is not secure, and the default unmarked state is secure. We will roll this out over time, starting by removing the “Secure” wording in September 2018. And in October 2018, we’ll start showing a red “not secure” warning when users enter data on HTTP pages.

\nimage source: Google Security Blog\n

Google Chrome currently captures 60% of the browser marketshare worldwide, making it one of the company’s most effective vehicles for driving HTTPS adoption. Let’s Encrypt, the free and open certificate authority (of which Chrome is a platinum sponsor), has also been a key player in precipitating the rise in secure traffic over the past few years. Firefox Telemetry shows that HTTPS traffic is at 81% for US users and 73% for all users.

Google’s Transparency report shows similar numbers for percentage of pages loaded over HTTPS in Chrome. 84% of US traffic is encrypted by HTTPS.

Google has even more weapons in its arsenal for compelling website owners to switch to HTTPS. Even before Chrome began flagging unencrypted sites, the search engine added HTTPS as a ranking signal in 2014. It started as a lightweight signal that affected fewer than 1% of global queries. Google has also indicated that HTTPS may break ties between two equal search results, making a difference for competitive niches. With more sites adopting HTTPS as the norm, the company may choose to strengthen the signal in the future.

Not everyone is comfortable with a for-profit company making an aggressive push to require websites to deliver content over HTTPS. Some fear that prioritizing encryption in search results, while also using Chrome to cast doubt on websites’ security, is just the beginning.

Dave Winer, one of Google’s most vocal critics regarding this initiative, sees the push towards HTTPS as the company’s attempt to take control of the open web. His concern is that if Google succeeds, it might “make a lot of the web’s history inaccessible.”

“Google makes a popular browser and is a tech industry leader,” Winer said. “They can, they believe, encircle the web, and at first warn users as they access HTTP content. Very likely they will do more, requiring the user to consent to open a page, and then to block the pages outright.”

\n
BTW, if I had to guess, the *real* reason Google hates HTTP has to do with Google\'s ad revenue, and not wanting Verizon and Comcast to remove their ads and replace them with their own.
\n
— scripting.com (@davewiner) July 23, 2018

Others have speculated that another driving factor behind Google’s push for HTTPS adoption may be its investment in advancing PWA technologies, which require HTTPS to be enabled. Last year Google dumped Chrome apps from the Chrome Web Store in favor of building PWAs that can be installed on the desktop. HTTPS is a requirement for the permission workflows, new features, and updated APIs that the company is using to build its future products.

It’s easy to see how HTTPS is critical for e-commerce, banking, and other sites that collect highly sensitive data from users, but many wonder if it is necessary for simple blogs and content websites. Google contends that all websites need HTTPS protection to prevent intruders from injecting ads or exploits.

Few would dispute the value of HTTPS but critics are wary of Google establishing itself as the arbiter of safe browsing on the web.

\n
My blog, https://t.co/gPQ9VPYOLB, is not “not secure.” It uses the standard protocol of the web, HTTP. It will not hurt you.
\n
— scripting.com (@davewiner) July 24, 2018

For the moment, Winer seems to be committed to using HTTP to deliver his content. In Google’s feverish quest to push the entire web to adopt HTTPS, sites that are holding fast to HTTP on principle now appear as a sort of protest.

“This blog and all my other sites use HTTP,” Winer said. “I don’t see that changing. I expect this will make writing for the web more of a chore. That’s life I guess. I don’t want Google to be able to mold the web to its needs. I never signed on to being a Google developer, and never would. Basic rule: Google is a guest on the web, as we all are, and guests don’t make the rules.”

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 24 Jul 2018 23:07: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: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:32:"Mark Jaquith: Page Links To v3.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:40:"http://markjaquith.wordpress.com/?p=5675";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"https://markjaquith.wordpress.com/2018/07/23/page-links-to/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2482:"

Today I pushed an update to my redirect and repointing plugin, Page Links To. Tomorrow, this plugin will have been in the WordPress.org Plugin Directory for 13 years (it was the 339th plugin in the WordPress plugin repository; there are now over 75,000!).

To celebrate its transition to a teenager, I’ve added some new features and UI enhancements.

Last month, I received survey responses from over 800 Page Links To users and learned a lot about how it’s being put to work. One of the most interesting things I found was how many people are using it for URL redirects. For example, they might have a really long URL on their own site or someone else’s site that they want to be nice. example.com/summer-sale instead of example.com/store/specials.aspx?season=summer&_utm_source=internal. But in order to create these redirects, you have to go through the cluttered and sometimes slow post creation screen. All you really need to create a redirect is a title, a destination URL, and a local short URL.

You’ll now find a menu item “Add Page Link” that will allow you to quickly add a redirected Page without having to wait for the entire WordPress post editing interface to load. It’s super fast, and it doesn’t redirect you away from the screen you’re on.

Since short URLs are better for sharing (and remembering), the UI will give you a little push to shorten the URL if the one generated from your title is too long. From there, you can Save Draft or Publish.

\nHey, that URL is getting a bit long\nCustom slug, for a better short URL\n

Additionally, this release includes a “link” indicator on post and page list screens, so you can easily see what items have been re-pointed with Page Links To. When hovered, the link icon will reveal the destination URL for a quick view.

\nThe “link” icon means that this item has been pointed elsewhere.\n

If you want to grab the “local” short URL (which will be redirected to your chosen URL when someone visits it), just click “Copy Short URL” from the actions, and it’ll be in your clipboard.

\nHover the “link” icon to see where it’s pointing.\n

That’s it for version 3.0, but I’ll have more to announce soon — stay tuned!

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 23 Jul 2018 22:02:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Mark Jaquith";s: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:"WPTavern: Thoughts From Two Founders Who Recently Sold Their WordPress Businesses";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82531";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:92:"https://wptavern.com/thoughts-from-two-founders-who-recently-sold-their-wordpress-businesses";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2299:"

Last month, WP Engine acquired StudioPress. Brian Gardner, founder of StudioPress, recently shared his thoughts on why he didn’t want to sell the business, but did.

\n\n

Making a decision that not only affects your livelihood, the livelihood of your partners and employees, and the livelihood of an entire community isn’t for the faint of heart. It certainly wasn’t a responsibility I took lightly and spent quite a bit of time wrestling with.
The fact of the matter is this: When you make a decision that affects thousands of people, you have to wrestle with it. And then wrestle with it some more.
Brian Gardner

\n\n

I appreciate Gardner’s down-to-earth perspective on how he reached the decision to sell.

\n\n

Ryan Sullivan, founder of WP Site Care, sold his WordPress maintenance and support business to Southern Web. On his personal site, Sullivan describes what it has been like to run a business the last seven years and drifting away from the reason he created the business in the first place.

\n\n

As the team grew, I slowly moved further and further away from the reason I started my business in the first place. It’s a trend that’s talked about extensively in the E-Myth.
People start a business because they love what they do, but then the growth of the business, management of people, and demands of administrivia become too much, and the person who started the business finds themselves in a totally foreign land with no roadmap for how to get back to the thing they once loved.
Ryan Sullivan

\n\n

Merging with Southern Web allows Sullivan to get back to what he enjoys doing most, helping people and businesses with their sites. Sullivan also shared a great piece of advice, “Ask for help before you think you need it.”

\n\n

Both articles are great reads and provide insight into the tough decisions founders inevitably have to make.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 23 Jul 2018 21:08:26 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:38:"WPTavern: WP-CLI Hack Day Is A Success";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82458";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:49:"https://wptavern.com/wp-cli-hack-day-is-a-success";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2239:"

Alain Schlesser hosted the first WP-CLI Hack Day last Friday and by all accounts, it was a smashing success.

\n\n

The main goal was to merge 20 pull requests during the event but due to technical issues with Travis CI, only 12 were merged. Travis CI is open source software used to perform automated testing.

\n\n

In addition to the 12 pull requests that were merged, 13 more were submitted. The last two hours of the event featured a video call where contributors could talk through issues or receive help on submitting pull requests.

\n\n

“We peaked at 13 participants to that video chat,” Schlesser said. “It allowed for people to make a more personal connection, which added another dimension to the act of contributing.”

\n\n

Despite not reaching the goal, Schlesser is pleased with how it turned out.

\n\n

“The event was also an experiment, to see whether a more direct, interactive form of contribution would attract more contributors,” he said. “I think it did succeed in doing so, and I think it was a positive experience for the participants.”

\n\n

Feedback from participants is positive and folks enjoyed having Schlesser available to answer questions and walk them through how to set up an environment for testing.

\n\n

Though we fell a little short of that goal, it was heartening to be a part of the communal experience, learn how to write my first Behat test (something that has been on my to-do list for a long time!), and get immediate feedback on my submitted pull request. And, of course, getting that PR merged was a thrill as well, as I can now say that I’ve contributed back to the project.
Jeremy Ward

\n\n

You can find links to all of the merged and submitted pull requests on the WP-CLI Hack Day summary 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:"Mon, 23 Jul 2018 19:43:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:94:"WPTavern: WordSesh Returns Wednesday, July 25, Experiments with Charging Attendees for Tickets";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82496";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:103:"https://wptavern.com/wordsesh-returns-wednesday-july-25-experiments-with-charging-attendees-for-tickets";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6630:"

WordSesh, a virtual conference dedicated to WordPress topics, is returning for a 5th edition on Wednesday, July 25, 2018. Scott Basgaard, the original organizer of the event, has passed the torch this year to Brian Richards, who has co-organized previous WordSesh events.

The online-only event will feature 12 hours of sessions on a variety of tech and business topics, including e-commerce, freelancing, and security. In the past, WordSesh has been a marathon 24-hour event, but Richards decided to pare it down to 12 hours this year in order to organize the details quickly and get the next event on the calendar as soon as possible.

WordSesh Experiments with Charging Attendees for Tickets, Adds Real-Time Transcription

For the first time in WordSesh history, the event is charging attendees for tickets (rather than making it free for everyone as in years past). Richards is using the ticket money to pay speakers and have every video professionally transcribed in real-time. He has received some pushback on the decision but wants to see how things fare with this arrangement.

“I thought the community might get behind that so we can stop asking speakers to completely volunteer their time, and the transcriptions are a huge accessibility bonus for non-native English speakers as well as the hard of hearing,” Richards said. “There have been just a few people pipe up to voice their distaste that I converted a free event to a paid event, which suggests there are many others stewing about it quietly, and I’m guessing it’s because they don’t realize where the money’s going (not that it should matter in either case).”

Richards said tickets are dynamically priced to be the operational equivalent of $25 USD in every person’s home country. In India, for example, the ticket price is closer to $9 USD. He has kept quiet about the tech until now because he didn’t want people gaming the system but has since decided that it’s not a major concern.

“The site accounts for purchase power parity so that the cost is not more than a couple of billable hours (or, ideally, much less) for everyone,” Richards said. “And for people whom the cost of a ticket is still a stretch, well, that’s where the scholarships come in.”

WordSesh still has 18 donated scholarships to give away but Richards said he is struggling to find people willing to apply to watch the event for free. Prospective attendees can apply for a scholarship or nominate others to receive one.

A ticket to the event grants attendees access to the sessions, both live and after it has been recorded. Attendees will also receive virtual swag. A few samples include:

A steep discount on WPSessions annual memberships (33%)
Stripe is providing an exclusive link to skip the invitation process on their Atlas program and cover the cost for processing their first $5k of payments
CorgiBytes is offering a $1k discount (~20%) on their code auditing services

Previous WordSesh events averaged 1,000 online attendees and a good portion of them showed up the same day the events aired. This year there are approximately 400 registered so far. Richards said he won’t rule out the possibility of making the event free again for the next edition.

“Asking more from sponsors could make a free event possible again without paying for everything personally (right now I’m still about $1000 in the red), but I really want to put the onus on the community at large,” Richard said. “Quality events take a lot of time and effort to accomplish, and most of that cost is on the backs of the organizers, speakers, and sponsors rather than attendees (at least in the WP community). Having been in all of those seats I’d really like to see more responsibility shift to the attendees. I would personally be happy to pay more for an event and be glad knowing that both speakers and organizers weren’t burning all this time in hopes of a return.”

Virtual conferences have started gaining more traction in the global WordPress community after the success of previous WordSesh events. WordPress educator Zac Gordon recently hosted more than 1,000 attendees at his free JavaScript for WordPress conference in June. The Polyglots’ virtual Global WordPress Translation day has also attracted hundreds of participants at each event (448 attendees in April 2016, 780 attendees in November 2016, and 1,300 local event RSVPs in September 2017).

Virtual events often reach far more people than an average local WordCamp, and many also inspire in-person meetups. Watch parties for WordSesh’s 5th edition are happening in cities across the globe, including Antwerp, Lagos, Minneapolis, Mumbai, and Bar Harbor (Maine).

“I’ve always enjoyed seeing people pour in to the event each year, and there was a delightful hum throughout the WordPress community every time a WordSesh took place,” Richards said.

WordSesh has been a valuable addition to the virtual event space around WordPress, and attendee numbers at the upcoming event will be important for measuring how much traction the event can retain with its conversion to a paid event. Richards says he is committed to keeping the event alive and hopes to host it two times per year, which is one of the reasons for cutting it back to 12 hours.

“I’m already excited for the next event,” Richards said. “I’m a little concerned at the moment, only because I don’t expect this one will sell enough tickets to break even, but I’m absolutely committed to hosting WordSesh again in the future. I’m more interested in hosting an incredible event and providing a ton of value to attendees than I am in breaking even this time 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:"Mon, 23 Jul 2018 17:41:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:29;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:74:"WPTavern: Gutenberg 3.3 Released, Adds Archives and Recent Comments Blocks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82478";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://wptavern.com/gutenberg-3-3-released-adds-archives-and-recent-comments-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:1354:"

\n\n

Gutenberg 3.3 is available and continues the trend of refining the user experience, user interface, and tools. Two new Widget blocks have been added, Post Archives and Recent Comments.

\n\nArchive and Recent Comments Widget Blocks\n\n

If your archives span across multiple months and years, you can configure the block to display as a drop-down menu. Otherwise, the list may be too long and look unwieldy on your site.

\n\n

Video blocks now have attributes users can can configure for Autoplay, Loop, Muted, and display Playback Controls.

\n\nVideo Block Attributes\n\n

There are a number of enhancements in this release that you can view via the change log.

\n\n

Considering Gutenberg 3.2 released earlier this month generally completed the MVP or minimum viable product feature set, users can expect more of these types of releases to tie up loose ends and prepare Gutenberg for merge into WordPress 5.0 later this year.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 21 Jul 2018 01:31:49 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:94:"WPTavern: Karachi to Host First WordCamp in Pakistan Following Cancellation of WordCamp Lahore";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82062";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:105:"https://wptavern.com/karachi-to-host-first-wordcamp-in-pakistan-following-cancellation-of-wordcamp-lahore";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:9479:"photo credit: Bilalhassan88\n

WordCamp Karachi is happening on August 4, 2018, and organizers are expecting more than 400 attendees. Karachi is the largest city in Pakistan with a population of more than 30 million people. Its airport connects the country to other international cities and smaller cities within Pakistan are available by rail or bus. Organizers behind the camp are overcoming a rocky history that has plagued the planning of WordPress-related events in the country for the past several years.

At the close of 2015, Pakistan was on track to host its first WordCamp in Lahore, building on momentum from the phenomenal growth of the local meetup group. Muhammad Kashif, one of the organizers, was averaging 200-500 attendees at meetups and his team’s application to host WordCamp Lahore was approved for 2016.

The meetup events, which attracted young students, developers, freelancers, and entrepreneurs, had grown so large that Kashif was having to close registration ahead of time because they were exceeding the capacity of the venue. Organizers expected 400-500 attendees at the WordCamp before it was cancelled after several delays near the end of the planning stage.

After contacting the WordPress Community team for the reason why it was cancelled, I received an official response from representative Hugh Lashbrooke:

Sometimes a WordCamp doesn’t make it all the way from pre-planning to being an actual event — occasionally due to logistical challenges, but other times because of broader concerns. In this case, once the WordCamp planning was underway, some tense dynamics arose within the local team. Everyone worked really hard to reach a positive solution, but we weren’t able to move forward with the event in the end.
\n
Cancelling an event is never anyone’s preference, to be clear, but it is also a customary response when it’s clear that collaboration isn’t possible in the short term. Local organizers are always encouraged to reapply as soon as the barriers to collaboration have been resolved.

Lashbrooke also cited issues with the camp’s budget for the venue organizers selected. He said the situation was thoroughly investigated before the camp was cancelled and that they would never take that kind of decision lightly.

WordCamp Lahore organizers gave me a different report on what happened and were disappointed with the decision from the Community Team.

“Representatives from the Foundation cancelled the camp in the last stage based on a complaint from one person out of a community of 3,000 people,” Kashif said. “The Foundation made a direct decision of cancellation without giving me a chance for explanation as the Primary Organizer. I suggested the Foundation conduct a survey from the whole Lahore community to know the facts but they had already made the decision to cancel.”

Kashif claims there was no disagreement between the organizers, because the community member in question, Ahmad Awais, was never part of the original organizing team.

One member of the planning team agreed to speak to me anonymously about why he believes the camp was canceled. He claims that Awais fractured the team after his request to be given a prominent position in the organization was denied.

“Ahmad Awais started hijacking Kashif and his team,” he said. “He was not a lead organizer at all, but on the planning team. Instead of contributing, Ahmad wanted to speak at every meetup and didn’t spend time with organizing team. He broke the team and started pointing fingers at Kashif and the existing organizing team. He was NOT there until WC Lahore was approved. He joined the team after that.”

Multiple leaders from WordCamp Karachi’s 14-person organizing team, who wish to remain anonymous, have reported that Awais also requested to be named keynote speaker and was unhappy with the team after they told him that speaker decisions do not work like that. Several said they feared his retaliation against the camp, given they previously had no recourse with the Community Team after the experience of WordCamp Lahore getting shut down.

Awais is not attending WordCamp Karachi and has declined to answer any questions about WordCamp Lahore due to personal reasons.

Kashif received hundreds of messages from the community after the event in Lahore was cancelled. He had been working since 2013 to bring a WordCamp to the area. He said that while the Community Team was helpful with other queries he had, he was disappointed with how quickly the camp was cancelled.

“I worked tirelessly for years to get a WordCamp to Lahore and grew the community from 430 to 2600 in one year but the Foundation didn’t even give me a chance to explain before canceling WC Lahore, Kashif said. “I am a bit disheartened by that action.”

Kashif is now helping with other WordCamps, including Karachi and NYC. He is also willing to work to re-establish a WordCamp Lahore in the future.

“Like me there are lots of other WordPress enthusiasts in Pakistan who want to participate in WordCamps but not everyone can do that outside of Pakistan due to financial or visa reasons,” Kashif said. “I was accepted as a volunteer in WordCamp Europe but couldn’t join due to visa issues. I have seen so much excitement for WordCamp Karachi in the WordPress community across the whole country. Everyone is willing to help to make it a successful event so that there are more frequent WordCamps in Pakistan. The first one is so important as it will set expectations of outcomes of a WordCamp for people who are new to these events.”

WordCamp Karachi Organizers Aim to Make a Positive Impact on Pakistan

WordCamp Karachi organizers are attempting to move past the Pakistani WordPress community’s checkered history of contention. They are also eager to distance themselves from the conflict that took down WordCamp Lahore.

Usman Khalid, lead organizer of the camp, said he has put in a lot of effort asking organizers and volunteers to work together, regardless of the credit they will receive, and focus on the community.

“I want to spend time on having a positive impact for this country, avoiding any kind of noise,” Khalid said. “The Pakistani WordPress community is vibrant in many ways. We have around 6,000 plus WordPressers in our community, with people who are selling their products and services worldwide.”

Khalid said there are many users in Karachi, Lahore, Islamabad, Peshawer, and Faisalabad who are doing well with WordPress but are not yet connected to the community or participating in meetups and events. People from all over Pakistan will be attending the event as their first exposure to the WordPress community. Sessions will mostly be conducted in English but a few will be mixed with Urdu, the regional language.

Khalid has experienced many growing pains in bringing the event to a community that is new to understanding how WordCamps work. In a country that is notorious for its censorship, WordPress’ mission of democratizing publishing has the potential to change many lives.

“Since this is first Wordcamp, many people even don’t know about it,” Khalid said. “Those who know want to be a speaker, or any lead role that can promote them. When we tell them it doesn’t work like this, they are mostly get annoyed.”

Tech publications around Pakistan have not been exposed to WordCamps either. Khalid said several of them have asked for money in order to cover the story of the event, unaware that the purpose of the camps and meetups is not to translate everything into business but to give back to the community.

“I am simply working to actually deliver first and prove that this community can create a positive impact,” Khalid said. “I am sure after Wordcamp Karachi, the entire community within Pakistan will flourish, regardless of what happened in Lahore.” He said he hopes the next camps will be even more interesting in the future and that WordCamp Karachi will help to create new jobs and more businesses in Pakistan.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 20 Jul 2018 23:14:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"Post Status: Why the makers of Ninja Forms are getting into eCommerce";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"https://poststatus.com/?p=46627";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:80:"https://poststatus.com/why-the-makers-of-ninja-forms-are-getting-into-ecommerce/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1982:"

Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by Brian Krogsgard and co-host Brian Richards.

In this episode, I bring on James Laws and Kevin Stover — cofounders of Saturday Drive, the parent company of Ninja Forms — to discuss why they are entering the world of eCommerce. I found this especially interesting given the market dominance of WooCommerce for general WordPress-based eCommerce needs.

Saturday Drive purchased Exchange, the plugin initially developed by iThemes and then handed off to A.J. Morris, with the intention of making a play for the eCommerce market, much like they did successfully once already for the somewhat-saturated forms market.

Episode Links

Ninja Shop plugin
Ninja Shop website
James Laws on Twitter
Kevin Stover on Twitter

Sponsor: Sandhills Development

Sandhills Development makes a suite of excellent plugins to power your WordPress website. Whether you need to sell digital downloads, restrict content, create an affiliate program, or manage an events calendar, they’ve got you covered. Thanks to Sandhills for being a Post Status partner.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 20 Jul 2018 22:29: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:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:63:"WPTavern: WordPress 4.9.8 Will Significantly Reduce Memory Leak";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82423";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:74:"https://wptavern.com/wordpress-4-9-8-will-significantly-reduce-memory-leak";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2723:"

WordPress 4.9.8 Beta two recently shipped and although much of the focus will be on the “Try Gutenberg” call-out, there’s a patch included that addresses a memory leak that was quite a problem for some users.

\n\n

When WordPress 4.9.7 shipped, the WordPress.org support forums saw an increase in reports of memory exhausted errors due to the wp_is_stream function.

\n\n

The bug is actually in PHP and is related to the stream-get-wrappers function. WordPress 4.9.7 increased the number of times it calls the wp_is_stream() function generating the error more often.

\n\n

After thoughtful conversations within the trac ticket, a patch was created that after further testing, was committed to core. According to Gary Pendergast, the patch does the following.

\n\n

\n
Bailing if the path isn’t a stream. This isn’t perfect: it’s still possible to trigger the PHP bug, but it does significantly reduce the chances of the bug being encountered. For many WordPress sites (those that don’t have plugins that use streams), it reduces the chance to zero.
\n

\n\n

If you encountered memory exhaustion errors after installing or upgrading to WordPress 4.9.7, try WordPress 4.9.8 Beta 2 to see if it fixes the issue.

\n\n

Aside from coming up with a solution, Trac ticket #44532 is a bit refreshing to see. In open source, tickets or issues can get bogged down with suggestions, hypothetical scenarios, and bike-shed commentary.

\n\n

In this instance, the issue was identified and folks from the community along with core contributors worked together in a focused fashion to create a fix in time for the next point release. The ticket is a good example of what it’s like when open source is firing on all cylinders.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 20 Jul 2018 20:33:11 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:42:"Donncha: WP Super Cache and Cookie Banners";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"https://odd.blog/?p=89501949";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:62:"https://odd.blog/2018/07/20/wp-super-cache-and-cookie-banners/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5289:"

More sites use cookie banners now that the GDPR is active but some are finding that their banners are misbehaving once they enable caching.

\n\n

This is a similar issue to the one that happened to some page counter plugins in the past. The page counter wouldn’t increment.

\n\n

When a cookie banner is clicked a cookie is set in the browser so the website knows this visitor has agreed to accept cookies. If the cookie is set then the cookie banner html is not sent to the browser.

\n\n

I suspect the main issue is that the code that sets and checks if the cookie is set is PHP. Unfortunately because the page is cached then no PHP code is executed, and the cookie banner is displayed because it was originally cached that way.

\n\n

Since WP Super Cache only knows about certain WordPress cookies it assumes everyone who doesn’t have those cookies is a first time “anonymous” visitor. It doesn’t know about your cookie banner cookie.

\n\n

You have two options:

\n\n

Rewrite your cookie banner so it’s completely in Javascript. Do the cookie detection in Javascript and also set the cookie in Javascript. If the cookie banner has been clicked then you need to trigger an action, and other Javascript that is hooked on to that trigger will run and load the tracking cookies.
Modify WP Super Cache so it knows about the cookie your cookie banner uses. Caching won’t work quite as well as before as it’ll be split between visitors who have clicked the cookie banner and those that haven’t. One cached file will display the cookie banner, and the other will not but it will have ad tracking Javascript.

\n\n

Using Javascript completely is a better solution because it runs in the browser on every page load but that might not be possible every time.

\n\n

Otherwise, use PHP to get WP Super Cache to play nicely with your existing code:

\n\n

You’ll need to write a WP Super Cache plugin.
You need to hook into the wp_cache_get_cookies_values cacheaction and add the value of the cookie banner cookie to the end of that string.
Caching can only be performed by simple caching now, unless you’re willing to edit mod_rewrite rules in your .htaccess file.

\n\n

Something like this will do. Make sure you note the warning about $wp_cache_plugins_dir in the link above about writing these plugins.

\n\n

function add_cookie_banner_to_cache_cookie( $string ) {\n    if ( isset( $_COOKIE[\'cookie_banner\'] ) ) {\n        $string .= \'cb,\';\n    }\n    return $string\n}\nadd_cacheaction( \'wp_cache_get_cookies_values\', \'add_cookie_banner_to_cache_cookie\' );

\n\n

Substitute the name of the cookie for your cookie name, change the name of the function, and the text it adds to the string. There is an intentional PHP fatal error in the code above to discourage copy/pasting.

\n\n

Your cookie banner plugin could automate setting this up, but it may have unforeseen consequences if not done correctly. It should check if $wp_cache_plugins_dir is set already, and use that location, otherwise it will have to make a directory and update the WP Super Cache configuration, where ABC is the new location for the plugins.

\n\n

wp_cache_setting( \'wp_cache_plugins_dir\', ABSPATH . \'wp-content/ABC\' );

\n\n

The new code can be copied into a file in that directory. The files in the original WP Super Cache plugins directory (found at WPCACHEHOME . \'plugins\') should be copied into that directory too and a warning shown to the user. They may need to set up one of those plugins again.

\n\n

The reason it is this convoluted is because this code will run before all of WordPress loads. You can’t rely on blog options or most of the nice configuration tools WordPress provides.

\n\n

When your plugin is uninstalled it should of course restore the plugins directory to the way it was before.

\n\n

For future reference, since cookie banners will hopefully not be around forever, here’s what they looked like in the deep, distant past of 2018.

\n\n\n\n\n The LA Times just gave up and don’t show anything to EU visitors.\n\n\n\n\n\n\n\n\n

Related Posts

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:"Fri, 20 Jul 2018 13:33:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:7:"Donncha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:34;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:76:"WPTavern: First Look at “Try Gutenberg” Prompt in WordPress 4.9.8 Beta 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82425";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:81:"https://wptavern.com/first-look-at-try-gutenberg-prompt-in-wordpress-4-9-8-beta-2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3384:"

WordPress 4.9.8 Beta 2 was released today, featuring the new “Try Gutenberg” prompt that will appear in user dashboards when the official release drops at the end of the month.

The prompt invites users to install Gutenberg if they want to try the new editor or install the Classic Editor to keep using the current editor until they are ready to make the change. WordPress contributors discussed variations on the design and wording of the callout and finally settled on what you see in 4.9.8 Beta 2.

Even if users don’t get involved in Gutenberg testing, the callout serves to inform them that the new editor will be enabled by default in the next major release of WordPress. It includes a link to the Gutenberg information page so users can learn more about the project.

Contributors agreed that they wanted to clearly communicate three important points in the callout, as per designer @kjellr’s suggestions on trac:

Gutenberg is coming in the next major release.
If you’re worried about compatibility, there’s a plugin to help ease the transition.
The plugin lets you use the editor you’re used to until you’re ready to switch.

The prompt is clearly geared towards encouraging users to test Gutenberg, as that section has a more prominent, colored button. If your clients’ installations are not ready for users to act on the “Try Gutenberg” prompt, now is the time to install a plugin that will disable it. Clients with free-range of the WordPress admin, in sites that are running Gutenberg-compatible extensions, are better candidates for testing the new editor.

The Classic Editor Addon is one option that will suppress the prompt and automatically suppress Gutenberg when it ships in WordPress 5.0. It was also recently updated to auto-install the Classic Editor plugin as a dependency so users don’t have to install two plugins as part of the process.

A release candidate is slated for July 24, and the official 4.9.8 release is scheduled for July 31st. The Gutenberg plugin is currently sitting at 10,000+ active installations and the Classic Editor at 5,000+. After 4.9.8 is released, changes in these numbers will demonstrate how WordPress users across the globe are responding to the call for testing.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Jul 2018 21:48:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:74:"WPTavern: Insight Into How North Carolina State Is Preparing for Gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82410";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:85:"https://wptavern.com/insight-into-how-north-carolina-state-is-preparing-for-gutenberg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1838:"

Jennifer McFarland, the web services coordinator for the North Carolina State Office of Information Technology (OIT), recently did an interview with Technician, the official student newspaper of NC State University.

\n\n

Since Gutenberg’s announcement in December of 2017, McFarland has published a series of articles on the NC State Office of Information Technology website educating staff and students on what to expect.

\n\n

McFarland was asked how the team plans to help staff and students after Gutenberg ships with WordPress.

\n\n

“A couple of times a year, we go and speak at various classes, professors will have us come out and do demos of WordPress,” McFarland told the Technician.

\n\n

“We are expecting an uptake of people requesting us to come out and do a demo of WordPress or something like that, but generally our plan right now, at least for students, is mostly just offer the sort of self-help, like the video tutorials and things like that, and we figure that the students will mostly try and solve their own problems.”

\n\n

Speaking of McFarland, she and Brian DeConinck presented on Gutenberg at WPCampus 2018. The videos from the event are still being processed but we’ll add a link to the presentation once it becomes available.

\n\n

It’s pretty cool to see people in McFarland’s position in higher education already have a firm grasp of Gutenberg and doing what they can to ease the transition for staff and students

\n\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 19 Jul 2018 00:27:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:83:"WPTavern: Meet Bernhard Kau, Local Lead Organizer of WordCamp Europe 2019 in Berlin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82335";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:93:"https://wptavern.com/meet-bernhard-kau-local-lead-organizer-of-wordcamp-europe-2019-in-berlin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4788:"

Bernhard Kau, a WordPress developer, meetup organizer, and four-time organizer of WordCamp Berlin, is the local lead organizer for the next WordCamp Europe. Kau will join Milan Ivanović, the global lead, at the helm of WordCamp Europe in Berlin next June.

Kau submitted an application with his team to host WCEU and won out over a competing application from the WordPress community in Barcelona. The selection team cited Berlin’s accessibility, reasonable prices, and its strong community as the final deciding factors.

Berlin’s monthly WordPress meetups have 1,300 members. The community also holds dedicated meetups for beginners, developers, and women in WordPress. Five WordCamps have been organized in Berlin since 2010.

\n
Attending #WPBerlin and they are already preparing WordPress community for next #WCEU pic.twitter.com/MWLwTZ4hrf
\n
— Milan Ivanović (@lanche86) June 28, 2018

“Compared to other communities in Europe, we are a community that is very likely to travel to other cities to attend meetups and other WordCamps,” Kau said. “We usually only have one or two WordCamps per year in Germany but then usually all the German community members travel to that city to attend the WordCamp. Whereas in Spain, for example, they had 11 WordCamps this year that are more local and smaller. As a German community we are more used to traveling to a central place and meeting there.”

What to Expect at WCEU in Berlin: A Diverse Community, More Workshops, and a Unique After Party

The Estrel Hotel and Congress Center will host the entire event, including both conference days, the contributor day, and the after party. Although the venue has a max capacity of 12,000 people, Kau said organizers are planning for 2,500 – 3,000 attendees. The local team is excited to introduce the European WordPress community to their home city.

“Berlin is one of the most diverse cities in Europe,” Kau said. “When I prepared the application, I figured out that there are people from 191 countries living in Berlin. It’s a very international, very diverse city, so you can be just as you are and feel quite comfortable and welcome in Berlin.”

Kau said organizers intend to continue with workshops as a part of the event in 2019 but they are planning to make the signup experience more efficient.

“This was the first year we tried workshops,” Kau said. “We had three workshop tracks and workshops of 60 minutes, 90 minutes, and three hours. We are not sure how many workshops we want to have in Berlin. The idea was new but turned out quite well. There were workshops with many people waiting to get in and from what I’ve heard it was quite good.”

Kau said he wants to improve the process for workshops, because there was no easy way for attendees to sign up and managing waiting lists was a lot of manual work for the content team. This is one bottleneck from the most recent WCEU experience that he hopes to rectify.

“There is also something special planned but I don’t want to spoil it,” Kau said. “It’s going to be a very unique after party to say the least.” Although Berlin is renowned for its legendary nightlife, Kau said he doesn’t anticipate the party lasting all night.

“We’re probably not going to make it Berlin-typical until 10 in the morning but it’s going to be a bit longer than maybe here [Belgrade] or in Paris where people were kicked at at 3:30,” he said.

The call for applications for organizers is still open. Within 24 hours of announcing Berlin as the next host city, the team had already received 27 applications. The application window closes July 31, 2018.

Check out the full interview below to learn more about the German WordPress community and what they have planned for WCEU 2019.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 18 Jul 2018 20:18:28 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:37;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:43:"WPTavern: WP-CLI Hack Day Friday, July 20th";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82269";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wptavern.com/wp-cli-hack-day-friday-july-20th";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1541:"

WP-CLI or WordPress Command Line Interface has become an integral tool for developers to launch and manage sites. To encourage new contributors to the project, Alain Schlesser is organizing the first WP-CLI Hack Day, Friday, July 20th beginning at 08:00 CEST.

\n\n

Schlesser and other contributors will be available in the WP-CLI Slack channel all day and on the project’s GitHub site to answer questions and help people contribute to the project.

\n\n

From 16:00-18:00 CEST, Schlesser will host a video call that’s open to everyone where people can join in, discuss issues, and visually work through pull requests. The goal is to reach 20 pull requests that have been merged during the event. A post on Make/CLI blog will be published once WP-CLI Hack Day concludes summarizing any progress that was made.

\n\n

To prepare prospecting contributors for the event, Schlesser has published a detailed guide on how to contribute to WP-CLI.

\n\n

Folks can follow along on Twitter using the hashtag #hackwpcli. If Hack CLI Day is successful, more events will likely be created in the future to cover more time zones.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Jul 2018 16:47:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:11:"\n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:30:"HeroPress: Making A Safe Place";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://heropress.com/?p=2589";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:105:"https://heropress.com/making-a-safe-place/#utm_source=rss&utm_medium=rss&utm_campaign=making-a-safe-place";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2907:" Pull Quote: The WordPress community is, slowly but surely, helping me get rid of my ingrown fear of the unknown, of others.

Pull Quote: The WordPress community is, slowly but surely, helping me get rid of my ingrown fear of the unknown, of others.

Being a remote worker makes it easy to hide from a world that you find scary or dangerous. If you’re never in the presence of other people they can’t hit you. Retreat becomes so easy. Marius Jensen from Sola, Norway grew up in a society that did not care for him, and made him want to hide from the world forever.

The WordPress community gave him a safe place to talk to people online, and after time, in person. WordCamps became a place of safety and compassion. This isn’t the case for all people, but it is for many people, in many places. Check out Marius’ essay from last July, about finding a safe place.

Becoming Myself Again

The post Making A Safe Place 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, 18 Jul 2018 08: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:"";}}}}}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:42:"WPTavern: iThemes Enters the Hosting Space";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82379";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wptavern.com/ithemes-enters-the-hosting-space";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3428:"

iThemes is getting into the hosting business after launching three plans that take advantage of its relationship with Liquid Web. The plans are finely tuned around the company’s products and come with free SSL certificates.

\n\n

I reached out to Cory Miller, Founder of iThemes to figure out why they’ve entered the hosting space, what it means to be able to control the user experience of their products from the top-down, and how their plans compare to those from hosts that offer Jetpack Premium.

\n\n

Interview With Cory Miller

\n\n

What does it mean for you and iThemes to be able to control the user experience from the top-down?

\n\n

In short, it means a better overall experience for our customers. For more than 10 years, we’ve dealt with most of the hosts, especially the ones offering catered WordPress offerings, and it has been a terribly frustrating experience for us trying to troubleshoot problems and help our mutual customers.

\n\n

Additionally, we’ve long said you have to have two things to be our customer: WordPress and web hosting. Now we install WordPress for you, along with SSL, essentially with a click on our own hosting.

\n\n

How would you compare iThemes hosting packages to hosts that offer Jetpack Premium services as part of their plans?

\n\n

The thing that sticks out for me is having everything under one brand and team. But we think using iThemes Sync Pro as the hosting control panel gives us a significant edge for our customers to do more with their WP sites, in particular, our reporting features in Sync Pro.

\n\n

Now our customers can get WP backups, security, site management and in-depth reporting all from one dashboard, along with their hosting. With our Business plan, they get BackupBuddy, our WordPress backup plugin; iThemes Security Pro, our WordPress security plugin & iThemes Sync Pro all in one. Plus they get an awesome team of WordPress pros for support if they need help or have any issues.

\n\n

What are you most looking forward too offering these hosting packages specifically tuned for iThemes products and WordPress?

\n\n

The actual implementation of the vision of offering the key essentials we think people want and need, along with a roadmap to do more, from our team at iThemes. It was one of the motivators for joining the Liquid Web family — the ability to finally do what we’ve always wanted to do for our customers, offering a more complete experience for them, from us.

\n\n

Were there any challenges that you overcame when putting these packages together?

\n\n

The main one that comes to mind is trying to ensure we offer what people actually want and will buy. But there was several months of hard work by our team and others to get this launched. Some long nights to pull all the pieces together in order to do this, with many more to come.

\n\n

Prices range from $15 per month to $25 per month billed on an annual basis. New customers can take advantage of a coupon code on the site to purchase the Business plan, normally $25 for $15.

\n\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 17 Jul 2018 23:19:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:92:"WPTavern: WooCommerce Custom Product Tables Plugin Now in Beta, Boasts 30% Faster Page Loads";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82363";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:101:"https://wptavern.com/woocommerce-custom-product-tables-plugin-now-in-beta-boasts-30-faster-page-loads";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3615:"

WooCommerce is celebrating 10th years of Woo this week. Over the past several years WooCommerce has grown to become a dominant player among e-commerce solutions on the web. E-commerce Usage Distribution stats from BuiltWith currently rank WooCommerce as the most commonly used platform for stores in the top 1 million sites.

Performance and scalability were the main focuses for the WooCommerce development team last year and these issues continue to be top priority. Version 3.0, released in April 2017, included significant performance improvements when WooCommerce switched from post meta to taxonomies for features like product visibility, featured products, and out of stock products. It also introduced CRUD (Create, Read, Update, Delete) classes for developers, making it easier to write and retrieve data from the database with less code.

Building on the CRUD work done last year, WooCommerce has just announced the beta of its new Custom Products Tables plugin. It replaces the WooCommerce product Data Store with new, dedicated product tables for significant reductions in page load time across shop, checkout, and admin pages.

“The results, so far, have been great – with improvements of up to 30% on page load times!” WooCommerce engineer Gerhard Potgieter said. “Checkout, arguably the most important part of the store experience, has seen the biggest performance gains.”

The WooCommerce development team tested the plugin’s impact on performance using two identical stores running the Storefront theme and no additional plugins. They created a data set of 500 products using the WooCommerce Smooth Generator, and both stores had 70,000 orders in the database and meta data in the range of 1.4 million rows.

\nimage credit: WooCommerce Development Blog\n

The Custom Product Tables plugin is not ready for use in production but developers can download version 1 and test it against WooCommerce 3.5 dev (switch to the master branch).

Getting the plugin rolled into WooCommerce core is an exciting update on the horizon, as faster page loads generally improve conversion for store owners. WooCommerce engineers anticipate releasing the plugin on WordPress.org as the next step. They plan to include the new product tables in a major version update early next year.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 17 Jul 2018 20:20:09 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:76:"WPTavern: New WordPress Feature Plugin Adds Support for Progressive Web Apps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82311";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:87:"https://wptavern.com/new-wordpress-feature-plugin-adds-support-for-progressive-web-apps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5800:"

WordPress contributors are working on getting support for Progressive Web Apps (PWA) into core. A new PWA feature plugin is now available on WordPress.org, spearheaded by the teams at XWP, Google, and Automattic.

Progressive Web Apps are applications that run on the web but provide a speedy app-like experience inside a mobile browser. Google describes them as having the following three qualities:

Reliable – Load instantly and never show the downasaur, even in uncertain network conditions
Fast – Respond quickly to user interactions with silky smooth animations and no janky scrolling
Engaging – Feel like a natural app on the device, with an immersive user experience

The plugin adds support for technologies that PWAs require, including Service Workers, a Web App Manifest, and HTTPS. These technologies support functions like background syncing, offline content, push notifications, mobile home screen icon, and other PWA features.

XWP CTO Weston Ruter said the purpose of the feature plugin is to curate PWA capabilities for proposed merging into core. The idea is to merge them piece by piece. Core tickets are already in process for adding support for web app manifests and support for service workers, as well as bringing improvements to HTTPS.

“This PWA feature plugin is intended to equip and facilitate other plugins which implement PWA features,” Ruter said. “It’s not intended to negate any existing plugins with these features, but rather to allow such plugins (and themes) to work together seamlessly and expand upon them.”

The first release of the plugin on WordPress.org (v0.1.0) adds support for web app manifests and initial support for allowing theme and plugin developers to register scripts for service workers via wp_register_service_worker(). It also includes an API for detecting whether HTTPS is available.

“A next step for service workers in the PWA feature plugin is to integrate Workbox to provide a declarative WordPress PHP abstraction for managing the caching strategies for routes, with support for detecting conflicts,” Ruter said. Anyone who is interested to contribute to PWA support for WordPress can check out the discussions and plugin on GitHub.

In the past, app-like experiences were only available for sites and services that had their own native mobile apps, but native apps can be costly to develop and maintain. Progressive web apps use the greater web as their platform and are quick to spin up. They make content easier to access on mobile even without an internet connection. It’s also far easier to tap a home screen icon than to enter a URL on mobile, and this makes users more likely to engage with their favorite sites.

PWA Stats is a site that features case studies of progressive web apps that have significantly increased performance, engagement, and conversion. A few compelling examples include:

Tinder cut load times from 11.91 seconds to 4.69 seconds with their new PWA. The PWA is 90% smaller than Tinder’s native Android app. User engagement is up across the board on the PWA.
Grand Velas Riviera Maya resort increased its Black Friday conversion rate by 53% due to its progressive web app’s speed and notifications.
Trivago saw an increase of 150% for people who add its PWA to the home screen. Increased engagement led to a 97% increase in clickouts to hotel offers. Users who go offline while browsing can continue to access the site and 67% continue to browse the site when they come back online.\n
Pinterest rebuilt their mobile site as a PWA and core engagements increased by 60%. They also saw a 44% increase in user-generated ad revenue and time spent on the site has increased by 40%.

PWA support in WordPress will enable the plugin and theme ecosystems to work together in providing site owners with more engaging ways to connect with their visitors. Once the market starts building on core support, site owners should soon be able to offer better experiences for mobile users without having to become experts in the technologies that power progressive web apps.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 17 Jul 2018 00:16: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: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:37:"Dev Blog: Quarterly Updates | Q2 2018";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=6140";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:61:"https://wordpress.org/news/2018/07/quarterly-updates-q2-2018/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:15621:"

\n\n

Accessibility

\n\n

Contacted: @rianrietveld, @joedolson, @afercia
Priority: Working to make sure that Gutenberg is reasonably accessible prior to merge. ETA is before 5.0
Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. The team is doing outreach to help solve this problem.
Big Win: Interest from companies like The Paciello Group and Tenon.io to help out with Gutenberg code review and testing tools.

\n\n

CLI

\n\n

Contacted: @danielbachhuber, @schlessera
Priority: Very first global Hack Day is coming up July 20. Version 2.0.0 is still in progress (new ETA is end of July).
Struggle: The team continues to need new contributors. The current team is tiny but tough.
Big Win: WP-CLI is currently one of the project’s four main focuses, as mentioned in the Summer Update at WordCamp Europe.

\n\n

Community

\n\n

Contacted: @francina, @hlashbrooke
Priority: Focusing on smoothing out the processes in our community management by building up our team of volunteers and establishing what tools we need to keep things running well. ETA is ongoing.
Struggle: Our two biggest struggles at the moment are tracking what we need to get done, and making final decisions on things. There is current work on the tools available to assist with tracking progress.
Big Win: After making a concerted effort to get more contributors on the Community Team, we now have a much larger group of volunteers working as deputies and WordCamp mentors

\n\n

Core

\n\n

Contacted: @jeffpaul
Priority: Following the WordCamp Europe summer update (and the companion post here), the team is getting Gutenberg (the new WordPress editing experience) into a strong state for the 5.0 release. Potential ETA as soon as August.
Struggle: Coordinating momentum and direction as we start seeing more contributors offering their time. Still working our way through open issues. The team is starting multiple bug scrubs each week to work through these more quickly and transparently.
Big Win: Had a sizable release in 4.9.6 which featured major updates around privacy tools and functionality in Core.

\n\n

Design

\n\n

Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
Priority: Better on-boarding of new contributors, especially creating better documentation. ETA is end of July.
Struggle: It’s hard to identify reasonably small tasks for first-time contributors.
Big Win: The team is much more organized now which has helped clear out the design backlog, bring in new contributors, and also keep current contributors coming back. Bonus: Joshua Wold will co-lead the upcoming release.

\n\n

Documentation

\n\n

Contacted: @kenshino
Priority: Opening up the work on HelpHub to new contributors and easing the onboarding process. No ETA.
Struggle: Some blockers with making sure the code and database can be ready to launch on https://wordpress.org/support/
Big Win: The first phase of HelpHub creation is complete, which means content updates (current info, more readable, easier discovery), internal search, design improvements, and REST API endpoints.

\n\n

Hosting

\n\n

Contacted: @mikeschroder, @jadonn
Priority: Preparing hosts for supporting Gutenberg, especially support questions they’re likely to see when the “Try Gutenberg” callout is released. ETA July 31st, then before WordPress 5.0
Struggle: Most contributions are still made a by a small team of volunteers. Seeing a few more people join, but progress is slow.
Big Win: New team members and hosting companies have joined the #hosting-community team and have started contributing.

\n\n

Marketing

\n\n

Contacted: @bridgetwillard
Priority: Continuing to write and publish case studies from the community. ETA is ongoing.
Struggle: No current team struggles.
Big Win: Wrote and designed a short Contributor Day onboarding card. It was used at Contributor Day at WCEU and onboarding time went down to 1 hour instead of 3 hours.

\n\n

Meta (WordPress.org Site)

\n\n

Contacted: @tellyworth, @coffee2code
Priority: Reducing manual work around the contributor space (theme review, GDPR/privacy, plugin review). ETA for small wins is end of quarter, larger efforts after that.
Struggle: Maintaining momentum on tickets. There are also some discussions about updating the ticket management process across teams that use the Meta trac system.
Big Win: The new About page launched and has been translated across most locale sites.

\n\n

Mobile

\n\n

Contacted: @elibud
Priority: Getting Gutenberg in the mobile applications. ETA is late December.
Struggle: Consuming the Gutenberg source in the ReactNative app directly. More info can be found here: https://make.wordpress.org/mobile/2018/07/09/next-steps-for-gutenberg-mobile/
Big Win: The WordPress mobile applications now fully support right-to-left languages and are compliant with the latest standards for accessibility.

\n\n

Plugins

\n\n

Contacted: @ipstenu
Priority: Clearing ~8,000 unused plugins from the queues. Likely ETA is September.
Struggles: Had to triage a lot of false claims around plugins offering GDPR compliance.
Big Win: Released 4.9.6 and updated expectations with plugin authors. Huge thanks to the Core Privacy team for their hard work on this.

\n\n

Polyglots

\n\n

Contacted: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
Priority: Keep WordPress releases translated to 100% and then concentrate on the top 100 plugins and themes. ETA is ongoing.
Struggle: Getting new PTEs fast enough, and complex tools/systems. Overall, the volume of strings awaiting approval.

\n\n

Support

\n\n

Contacted: @clorith
Priority: Getting ready for the Gutenberg callout (it got pushed last quarter). Needing a better presence on the official support forums, and outreach for that is underway, ETA end of July.
Struggle: Keeping contributors participating post-contributor days/drives. Considering the creation of a dedicated post-contributor day survey to get some insight here.
Big Win: The increase in international liaisons joining for weekly meetings, helping bring the wider support community together.

\n\n

Theme Review

\n\n

Contacted: @acosmin, @rabmalin, @thinkupthemes, @williampatton
Priority: Building a better Theme Check/Sniffer in order to automate most of the checks done right now by reviewers. ETA late 2018, early 2019.
Struggle: Bringing in new contributors to the team.
Big Win: Trusted Authors program

\n\n

Tide

\n\n

Contacted: @valendesigns (but usually @jeffpaul)
Priority: Storing PHPCompatibilty results inside the WordPress.org API and building a UI to display those results, an endpoint to request an audit is required for this work to continue.
Struggle: Development has dramatically slowed down while team members are on leave or pulled into internal client work.
Big Win: Migration to Google Cloud Platform (GCP) from Amazon Web Services (AWS) is complete and the audit servers have all been rewritten in Go. (This allows us to be faster with greater capacity and less cost.)

\n\n

Training

\n\n

Contacted: @bethsoderberg, @juliek
Priority: Lesson plan production. ETA is ongoing.
Struggle: The workflow is a little complex, so recruiting and training enough contributors to keep the process moving is a struggle.
Big Win: WordCamp Europe’s Contributor Day was very productive. New tools/workflow are in place and two team representatives were there to lead and help.

\n\n

Interested in updates from the first quarter of this year? You can find those here: https://make.wordpress.org/updates/2018/04/24/quarterly-updates-q1-2018/\n \n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 16 Jul 2018 14:50: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:7:"Josepha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:93:"WPTavern: WordCamp Europe 2018 Draws 2,085 Attendees, Organizers Look Ahead to 2019 in Berlin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82313";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://wptavern.com/wordcamp-europe-2018-draws-2085-attendees-organizers-look-ahead-to-2019-in-berlin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6531:"photo credit: WCEU Photography Team\n

WordCamp Europe closed out a successful event in Belgrade with 2,085 attendees from 76 countries. More than 800 others joined via livestream for a total audience of nearly 3,000 participants. A record-setting Contributor Day kicked off the event, followed by two days of conference sessions and workshops from 65 speakers.

A team of 54 organizers and 170 volunteers made WCEU possible, with 10 different organizing teams. Last year WordCamp Europe added a PR team and this year the event introduced an Attendee Services team to fill gaps in the organization. The operation ran smoothly, despite the conference being spread out across many rooms in the sprawling Sava Centar venue.

WordCamp Europe’s PWA (progressive web app) was the highlight of the new features and services introduced this year. It was a central hub for keeping attendees informed on what was happening at any given moment. Organizers also added new amenities, including a site health check station, Community Room, and info booth to handle attendee questions.

Gutenberg and Progressive web apps were the hot topics of this year’s WordCamp Europe. In addition to Matt Mullenweg unveiling a roadmap for Gutenberg’s inclusion in core, a strong contingent of designers and engineers from the team were present to educate attendees on Gutenberg’s architecture and the vision behind the project.

Many attendees were visiting Serbia for the first time and Belgrade delivered with its renowned hospitality and captivating nightlife. Attendees found no shortage of delicious options for food and drink.

Berlin to Host WordCamp Europe 2019

At the conclusion of the event, organizers announced Berlin as the next host city for WordCamp Europe, June 20-22, 2019. The conference, Contributor Day, and the after party will all be held at the Estrel Hotel and Congress Center, a venue with a capacity for 12,000 attendees.

Organizers said that Berlin’s accessibility, reasonable prices, and strong community were the final deciding factors for its selection as the next host city.

Behind the Scenes at WordCamp Europe 2018 with Lead Organizers Jenny Beaumont and Milan Ivanović

Hosting a volunteer-led event at this scale requires an enormous amount of effort from the organizers, especially those taking the lead for multiple years in a row. There is nearly no down time as the team is already planning for the next edition of the camp.

I sat down with lead organizers Jenny Beaumont, the global lead, and Milan Ivanović, the local lead, to get a look behind the scenes at what is involved in bringing WordCamp Europe to thousands of WordPress enthusiasts in one weekend. We interviewed them at the conclusion of WCEU 2017 in Paris. Over the past two years these leaders have developed a strong working relationship built on encouraging each other and keeping a positive outlook for their teams.

Beaumont said she was hesitant going into a third year for this role, as Paris was the project that captured her heart and motivation. After going through this event as the global lead, she said she discovered what she could bring to the role and how she could serve the team.

“The event has been their project,” Beaumont said. “My project this year has been the team, how I can really concentrate on this team, on its growth, on its health, on its sustainability. That’s what I learned in Paris – the importance of making sure that was part of the project.”

Beaumont and Ivanović explained the difference between the global and local lead roles, a structure that works well for flagship WordCamps.

“The local team is really about making it a good experience in this new place that everybody is going to be discovering for the first time,” Beaumont said. “It’s the hard work, it’s the logistics, it’s all of the small details, everything that’s behind the scenes that make it so you walk in as an attendee and it just feels like you’re at home. They do all of that hard work. The global role, as it has evolved, is really about being that sort of team care-giver, making sure that there is good communication happening, making sure the team is healthy and happy and motivated. Because you’ve got to get up and do this every day while you’re also doing your day job, and that takes a lot.”

WordCamp Europe had a strong impact on the local community with more than 400 Serbian attendees and 20 Serbian organizers. They worked to build awareness of WordPress in the local community ahead of the event.

“We used this event to grow our community and used our community to promote the event,” Ivanović said. “When we announced last year in Paris that Belgrade is going to be next, at that time we had five or six cities for WordPress meetups. Currently, we are in 14 cities and starting the 15th in July. WordCamp Europe and the conference itself was such a win for the whole community.”

Ivanović will return next year as the global lead for WCEU in Berlin. Beaumont is taking some time off after three years organizing WordCamp Paris and WordCamp Europe, but she hopes to return in some capacity in the future. They are working together with their team to publish a WordCamp Europe handbook that covers some of the important specifics of the event for upcoming teams. Check out the full interview in the video below.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 14 Jul 2018 00:24:08 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:82:"WPTavern: Array Launches Free Gutenberg-Ready Atomic Blocks Theme on WordPress.org";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82258";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:93:"https://wptavern.com/array-launches-free-gutenberg-ready-atomic-blocks-theme-on-wordpress-org";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6391:"

Mike McAlister and the team at Array Themes have fully embraced Gutenberg and are one of the first shops on the scene with a free WordPress theme designed specifically to work with the new editor. The Atomic Blocks theme is now available on WordPress.org with minimal styling and seamless support for all core content and media blocks.

The theme allows users to control the width of the content area to create full-screen posts and pages. It supports full-screen images, videos, and galleries, showcasing the new editor’s wide alignment styles for content. Atomic Blocks includes Customizer options for uploading a logo, customizing the font style, setting body and title font sizes, and selecting an accent color.

Check out the theme’s demo to see the blocks in action: https://preview.arraythemes.com/atomicblocks.

The theme also seamlessly supports McAlister’s new Atomic Blocks project, a collection of page-building blocks included in the accompanying Atomic Blocks plugin. It currently includes blocks for creating a post grid, call-to-action, testimonials, inline notices, sharing icons, author profiles, accordions, customizable buttons, drop caps, and spacer/dividers, with many more blocks planned.

“I knew Gutenberg was going to be a game changer from the second I saw it and started hashing out product ideas in October 2017,” McAlister said. “To me, it felt like a very natural evolution and transition for WordPress into a more forward-thinking content creator. All of the tools outside of WordPress are evolving and becoming better and easier to use and WordPress is starting to feel quite dated in comparison.”

McAlister said his team is building Atomic Blocks into a full-fledged content block solution that will include a commercial version in the future.

“We have a long list of blocks that we’ll be releasing into the plugin in the coming months — everything from eCommerce to email marketing to full-page layouts,” he said. “There will definitely be a commercial version of the plugin for those extra awesome blocks that will take your site to the next level.”

McAlister is keeping Atomic Blocks separate from Array Themes but plans to cross promote between the two. He also plans to update the Array themes collection to support the blocks found in the plugin.

“Atomic Blocks aims to solve a different problem in a different way than the traditional WordPress themes you’ll find on Array,” McAlister said. “By launching it separately from Array Themes, it gave me the opportunity to diversify my projects a bit and create a dedicated marketing stream for a Gutenberg solution.”

Many products in the Array Themes catalog are already working with the new editor, but McAlister and his team intend to provide more in-depth support for specific Gutenberg features in themes where appropriate.

“We’ve stayed fiercely committed to beautiful design, simplicity, and core coding standards and practices to ensure wide-spread support and compatibility with our themes,” McAlister said. “While this has served us well, we are all ready for a core-supported solution to providing a better experience for our customers. Gutenberg will solve this problem by providing a cohesive, unified way of extending content creation with a core user interface. Gutenberg is quite extensible as is, and will only grow more capable with time.”

McAlister said one of the most challenging aspects of launching Atomic Blocks has been keeping pace with Gutenberg’s rapid development, requiring the team to follow multiple conversations across various WordPress core development discussion channels.

“I followed Gutenberg development closely during the second half of last year and then started developing Atomic Blocks for Gutenberg early this year,” McAlister said. “You have to follow the Github repo, Make blog posts, and Slack conversations closely to keep up with the changes, deprecations, and feature additions. Luckily, now that features are being frozen, the code is churning less and things are starting to stabilize.”

In order to keep up with all the news and changes, McAlister started the Gutenberg News site to collect helpful resources, tutorials, and code snippets he found. The site contains more than 200 links to resources for both beginners and developers.

McAlister predicts that Gutenberg will bring a greater separation between the roles of themes and plugins in the site-building experience.

“The demand for themes will certainly begin to change more drastically in the long term,” he said. “Traditional WordPress themes will still be desirable for a number of years, simply due to the number of sites out there and the solutions needed to build them. Eventually, much of what can be provided by a theme will be provided by blocks via a plugin instead. Themes will still be responsible for providing a degree of styling and functionality that will remain critical to the site-building experience, but they will take a secondary role to content blocks.”

Gutenberg will inevitably change the landscape of the theme industry, but McAlister sees it as a chance to reach customers in a new way.

“Theme designers and developers should be excited about this opportunity and not feel threatened by Gutenberg,” McAlister said. “This is a fantastic opportunity to learn a new set of skills, attract a new segment of customers, and start pivoting to a block-based product model.”

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 12 Jul 2018 22:33:16 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:90:"WPTavern: WPWeekly Episode 323 – Recap of WordCamp Grand Rapids and A Gutenberg Road Map";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=82285&preview=true&preview_id=82285";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:97:"https://wptavern.com/wpweekly-episode-323-recap-of-wordcamp-grand-rapids-and-a-gutenberg-road-map";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2142:"

In this episode, John James Jacoby recaps his trip to WordCamp Grand Rapids and shares his experience. WordCamp Grand Rapids had a strong focus on tools, plugins, and themes and by all accounts, was a successful event.

We discussed Matt Mullenweg’s Summertime update, the roadmap for merging Gutenberg into core, and what comes after Gutenberg. We shared our thoughts on Automattic’s new board member, General Ann Dunwoody and speculated on Automattic’s vision.

We wrap up the show by talking about generational divides in WordPress.

Stories Discussed:

WordPress 4.9.7 Security and Maintenance Release
\nUpdate on Gutenberg
\nWhat’s New in Gutenberg? (6th July)
\nAutomattic’s First New Board Member: General Ann Dunwoody
\nBlock Unit Test Plugin Helps WordPress Theme Developers Prepare for Gutenberg
\nGenerational divides in WordPress

WPWeekly Meta:

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

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #323:
\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 12 Jul 2018 00:42:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:108:"WPTavern: Video: A Quick Introduction to Gutenberg and the New WordPress Block Editor from LinkedIn Learning";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82276";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:118:"https://wptavern.com/video-a-quick-introduction-to-gutenberg-and-the-new-wordpress-block-editor-from-linkedin-learning";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1005:"

Although WordPress developers and professionals have been inundated with Gutenberg news for more than a year, there’s a whole wide world of users who will learn about the project for the first time when 4.9.8 includes a “Try Gutenberg” prompt in the admin. If you haven’t been following the news closely and are wondering what all of this Gutenberg talk is about, Morten Rand-Hendriksen provides a succinct introduction to the new editor that is coming in WordPress 5.0.

The video was created as part of LinkedIn’s WordPress Essentials Training course. The first part explains the basic concept of a block and includes a mini tour of the new interface, followed by a short overview of where the Gutenberg project is going in the future.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 11 Jul 2018 23:04:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:47;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:86:"WPTavern: WordCamp Ticket Sales Move from PayPal to Stripe for Default Payment Gateway";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82267";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:97:"https://wptavern.com/wordcamp-ticket-sales-move-from-paypal-to-stripe-for-default-payment-gateway";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1857:"

The WordPress Community Team announced an update to the CampTix, the plugin used for selling WordCamp tickets, that makes Stripe the default payment method. The gateway was previously available as a beta plugin and could be enabled on a per-site basis but is now available to all WordCamps.

When proposing Stripe as the default payment gateway in April, Hugh Lashbrooke cited the fact that PayPal is entirely blocked and inaccessible in some countries. He also identified Stripe’s simpler UI and larger number of supported currencies as its chief advantages.

PayPal has been the default for years on WordCamp websites but it currently supports only 26 currencies. Stripe supports 136 currencies, allowing WordCamp organizers to offer ticket purchases in more places than before. Previously, some communities were forced to build a local gateway integration to sell WordCamp tickets via PayPal, requiring those sales to be inconveniently funneled through a local bank account. The Stripe gateway option is a welcome update to support WordPress’ growing international community, which held camps in 73 countries in 2017.

It’s important to note that Stripe isn’t fully replacing PayPal. The Camptix plugin allows organizers to activate multiple payment gateways for cases where one or both make more sense, retaining the flexibility to support ticket sales at camps with different payment requirements.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 11 Jul 2018 18:02:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:11:"\n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"HeroPress: Translating For Love";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://heropress.com/?p=2587";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:107:"https://heropress.com/translating-for-love/#utm_source=rss&utm_medium=rss&utm_campaign=translating-for-love";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3006:" Pull Quote: I started translating WordPress so that my seven-year-old daughter can share her personal stories.

Pull Quote: I started translating WordPress so that my seven-year-old daughter can share her personal stories.

We all have our reasons for the things we do. Money, love, orders, etc. Vladimir Petkov started using WordPress because it solved a problem. As the years went by it continued to solve problems, and he continued to use it. His time to give back didn’t arrive until much later though.

His 7 year old daughter wanted a blog, and WordPress wasn’t completely translated into her language. So Vladimir learned how to translate WordPress, so his little girl (and every other Bulgarian speaker) can use their voice to speak to the world.

Why do you give back to WordPress? If you’d like more info about how you can (no coding required!) drop a note in the comments.

Also, check out Vladimir’s essay.

Rebirth

The post Translating For Love 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, 11 Jul 2018 12:13: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:"";}}}}}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:66:"WPTavern: Video: Matt Mullenweg’s Summertime Update At WCEU 2018";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=82254";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:73:"https://wptavern.com/video-matt-mullenwegs-summertime-update-at-wceu-2018";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:861:"

Sessions from WordCamp Europe 2018 are making their way onto WordPress.tv, including Matt Mullenweg’s Summertime Update.

\n\n

In the video, Mullenweg shares the progress that’s been made on Gutenberg, WordPress core development, a Gutenberg road map for including it into core, and what to expect after WordPress 5.0 is released.

\n\n

Be sure to watch the video to the end to catch the memorable, GDPR cookie joke.

\n\n\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 10 Jul 2018 23:56:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"*data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Fri, 03 Aug 2018 09:12:54 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Fri, 03 Aug 2018 09:00:27 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 2";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20130911040210";}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('135', '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1533330774', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('136', '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1533287574', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('137', '_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b', '1533330774', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('138', '_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b', '', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('140', '_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-4.9.8.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-4.9.8.zip";s:10:"no_content";s:70:"https://downloads.wordpress.org/release/wordpress-4.9.8-no-content.zip";s:11:"new_bundled";s:71:"https://downloads.wordpress.org/release/wordpress-4.9.8-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:5:"4.9.8";s:7:"version";s:5:"4.9.8";s:11:"php_version";s:5:"5.2.4";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"4.7";s:15:"partial_version";s:0:"";}}s:12:"last_checked";i:1533287818;s:15:"version_checked";s:5:"4.9.8";s:12:"translations";a:0:{}}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('141', 'auto_core_update_notified', 'a:4:{s:4:"type";s:7:"success";s:5:"email";s:22:"roka.manoj12@gmail.com";s:7:"version";s:5:"4.9.8";s:9:"timestamp";i:1533287600;}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('143', '_site_transient_update_themes', 'O:8:"stdClass":4:{s:12:"last_checked";i:1533287826;s:7:"checked";a:4:{s:13:"twentyfifteen";s:3:"2.0";s:15:"twentyseventeen";s:3:"1.6";s:13:"twentysixteen";s:3:"1.5";s:8:"wr-nitro";s:5:"1.6.4";}s:8:"response";a:1:{s:15:"twentyseventeen";a:4:{s:5:"theme";s:15:"twentyseventeen";s:11:"new_version";s:3:"1.7";s:3:"url";s:45:"https://wordpress.org/themes/twentyseventeen/";s:7:"package";s:61:"https://downloads.wordpress.org/theme/twentyseventeen.1.7.zip";}}s:12:"translations";a:0:{}}', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('144', 'current_theme', 'WR Nitro', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('145', 'theme_mods_wr-nitro', 'a:3:{i:0;b:0;s:18:"nav_menu_locations";a:0:{}s:13:"header_layout";i:6;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('146', 'theme_switched', '', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('147', 'widget_nitro_instagram', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('148', 'widget_recent_posts', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('149', 'widget_recent_comments', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('150', 'widget_nitro_subscription', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('151', 'widget_nitro_social', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('152', '_transient_7f874452dc44c2ca60ad0038bc238c13', 'a:2:{s:11:"last_update";i:1533287829;s:7:"presets";a:3:{s:9:"profile-1";a:2:{s:5:"title";s:5:"Light";s:4:"data";a:28:{s:12:"custom_color";s:7:"#ff4064";s:18:"content_body_color";a:2:{s:9:"body_text";s:7:"#646464";s:12:"heading_text";s:7:"#323232";}s:18:"general_line_color";s:7:"#ebebeb";s:20:"content_loader_color";a:2:{s:4:"icon";s:7:"#ffffff";s:2:"bg";s:18:"rgba(0, 0, 0, 0.7)";}s:18:"content_meta_color";s:7:"#ababab";s:26:"wr_general_container_color";s:7:"#ffffff";s:22:"wr_layout_offset_color";s:7:"#ffffff";s:21:"wr_page_body_bg_color";s:7:"#ffffff";s:29:"wr_layout_boxed_bg_mask_color";s:16:"rgba(0, 0, 0, 0)";s:21:"general_overlay_color";s:7:"#f2f2f2";s:17:"general_fields_bg";s:7:"#f9f9f9";s:26:"wr_page_title_custom_color";i:0;s:22:"wr_page_title_bg_color";s:7:"#f2f2f2";s:24:"wr_page_title_mask_color";s:16:"rgba(0, 0, 0, 0)";s:25:"wr_page_title_link_colors";a:2:{s:6:"normal";s:7:"#323232";s:5:"hover";s:7:"#ff4064";}s:19:"wr_page_title_color";a:2:{s:4:"head";s:7:"#323232";s:4:"body";s:7:"#646464";}s:22:"footer_customize_color";i:0;s:16:"footer_top_color";a:2:{s:4:"text";s:7:"#646464";s:7:"heading";s:7:"#323232";}s:21:"footer_top_link_color";a:2:{s:6:"normal";s:7:"#646464";s:5:"hover";s:7:"#ff4064";}s:19:"footer_top_bg_color";s:7:"#ffffff";s:16:"footer_bot_color";a:2:{s:2:"bg";s:7:"#f2f2f2";s:4:"text";s:7:"#646464";}s:21:"footer_bot_link_color";a:2:{s:6:"normal";s:7:"#646464";s:5:"hover";s:7:"#ff4064";}s:20:"btn_primary_bg_color";a:2:{s:6:"normal";s:7:"#323232";s:5:"hover";s:4:"#222";}s:17:"btn_primary_color";a:2:{s:6:"normal";s:4:"#fff";s:5:"hover";s:4:"#fff";}s:24:"btn_primary_border_color";a:2:{s:6:"normal";s:7:"#323232";s:5:"hover";s:7:"#323232";}s:22:"btn_secondary_bg_color";a:2:{s:6:"normal";s:22:"rgba(255, 255, 255, 0)";s:5:"hover";s:4:"#222";}s:19:"btn_secondary_color";a:2:{s:6:"normal";s:7:"#323232";s:5:"hover";s:4:"#222";}s:26:"btn_secondary_border_color";a:2:{s:6:"normal";s:7:"#323232";s:5:"hover";s:7:"#323232";}}}s:9:"profile-2";a:2:{s:5:"title";s:4:"Dark";s:4:"data";a:28:{s:12:"custom_color";s:7:"#1a7aeb";s:18:"content_body_color";a:2:{s:9:"body_text";s:7:"#95a1bc";s:12:"heading_text";s:7:"#ffffff";}s:18:"general_line_color";s:7:"#374056";s:20:"content_loader_color";a:2:{s:4:"icon";s:7:"#40b6ff";s:2:"bg";s:25:"rgba(255, 255, 255, 0.92)";}s:18:"content_meta_color";s:7:"#868fa6";s:26:"wr_general_container_color";s:7:"#1c2334";s:22:"wr_layout_offset_color";s:7:"#ffffff";s:21:"wr_page_body_bg_color";s:7:"#ffffff";s:29:"wr_layout_boxed_bg_mask_color";s:16:"rgba(0, 0, 0, 0)";s:21:"general_overlay_color";s:7:"#20283b";s:17:"general_fields_bg";s:7:"#374056";s:26:"wr_page_title_custom_color";i:0;s:22:"wr_page_title_bg_color";s:7:"#1c1c26";s:24:"wr_page_title_mask_color";s:16:"rgba(0, 0, 0, 0)";s:25:"wr_page_title_link_colors";a:2:{s:6:"normal";s:7:"#b0b0c0";s:5:"hover";s:7:"#40b6ff";}s:19:"wr_page_title_color";a:2:{s:4:"head";s:7:"#ffffff";s:4:"body";s:7:"#b0b0c0";}s:22:"footer_customize_color";i:0;s:16:"footer_top_color";a:2:{s:4:"text";s:7:"#95a1bc";s:7:"heading";s:7:"#ffffff";}s:21:"footer_top_link_color";a:2:{s:6:"normal";s:7:"#95a1bc";s:5:"hover";s:7:"#2088e7";}s:19:"footer_top_bg_color";s:7:"#262e41";s:16:"footer_bot_color";a:2:{s:2:"bg";s:7:"#1c2334";s:4:"text";s:7:"#95a1bc";}s:21:"footer_bot_link_color";a:2:{s:6:"normal";s:7:"#95a1bc";s:5:"hover";s:7:"#ffffff";}s:20:"btn_primary_bg_color";a:2:{s:6:"normal";s:7:"#1d80e9";s:5:"hover";s:7:"#0f61b7";}s:17:"btn_primary_color";a:2:{s:6:"normal";s:7:"#ffffff";s:5:"hover";s:7:"#ffffff";}s:24:"btn_primary_border_color";a:2:{s:6:"normal";s:7:"#1d80e9";s:5:"hover";s:7:"#0f61b7";}s:22:"btn_secondary_bg_color";a:2:{s:6:"normal";s:7:"#151b28";s:5:"hover";s:7:"#1d80e9";}s:19:"btn_secondary_color";a:2:{s:6:"normal";s:7:"#ffffff";s:5:"hover";s:7:"#ffffff";}s:26:"btn_secondary_border_color";a:2:{s:6:"normal";s:7:"#374056";s:5:"hover";s:7:"#1d80e9";}}}s:9:"profile-3";a:2:{s:5:"title";s:5:"Light";s:4:"data";a:28:{s:12:"custom_color";s:7:"#4593fc";s:18:"content_body_color";a:2:{s:9:"body_text";s:7:"#676c77";s:12:"heading_text";s:7:"#546175";}s:18:"general_line_color";s:7:"#e7eaf1";s:20:"content_loader_color";a:2:{s:4:"icon";s:7:"#40b6ff";s:2:"bg";s:25:"rgba(255, 255, 255, 0.92)";}s:18:"content_meta_color";s:7:"#868fa6";s:26:"wr_general_container_color";s:7:"#ffffff";s:22:"wr_layout_offset_color";s:7:"#ffffff";s:21:"wr_page_body_bg_color";s:7:"#ffffff";s:29:"wr_layout_boxed_bg_mask_color";s:16:"rgba(0, 0, 0, 0)";s:21:"general_overlay_color";s:7:"#edf0f5";s:17:"general_fields_bg";s:7:"#f8f9fb";s:26:"wr_page_title_custom_color";i:0;s:22:"wr_page_title_bg_color";s:7:"#edf0f5";s:24:"wr_page_title_mask_color";s:16:"rgba(0, 0, 0, 0)";s:25:"wr_page_title_link_colors";a:2:{s:6:"normal";s:7:"#546175";s:5:"hover";s:7:"#4593fc";}s:19:"wr_page_title_color";a:2:{s:4:"head";s:7:"#546175";s:4:"body";s:7:"#676c77";}s:22:"footer_customize_color";i:0;s:16:"footer_top_color";a:2:{s:4:"text";s:7:"#676c77";s:7:"heading";s:7:"#546175";}s:21:"footer_top_link_color";a:2:{s:6:"normal";s:7:"#676c77";s:5:"hover";s:7:"#4593fc";}s:19:"footer_top_bg_color";s:7:"#edf0f5";s:16:"footer_bot_color";a:2:{s:2:"bg";s:7:"#546175";s:4:"text";s:7:"#edf0f5";}s:21:"footer_bot_link_color";a:2:{s:6:"normal";s:7:"#edf0f5";s:5:"hover";s:7:"#ffffff";}s:20:"btn_primary_bg_color";a:2:{s:6:"normal";s:7:"#1d80e9";s:5:"hover";s:7:"#0f61b7";}s:17:"btn_primary_color";a:2:{s:6:"normal";s:7:"#ffffff";s:5:"hover";s:7:"#ffffff";}s:24:"btn_primary_border_color";a:2:{s:6:"normal";s:7:"#1d80e9";s:5:"hover";s:7:"#0f61b7";}s:22:"btn_secondary_bg_color";a:2:{s:6:"normal";s:7:"#edf0f5";s:5:"hover";s:7:"#4593fc";}s:19:"btn_secondary_color";a:2:{s:6:"normal";s:7:"#868fa6";s:5:"hover";s:7:"#ffffff";}s:26:"btn_secondary_border_color";a:2:{s:6:"normal";s:7:"#ccd5e4";s:5:"hover";s:7:"#4593fc";}}}}}', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('153', '_transient_timeout_wr_nitro_sample_packages', '1533291432', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('154', '_transient_wr_nitro_sample_packages', '[\n {\n "id": "main",\n "name": "Main Demo",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-00.jpg",\n "demo": "http://nitro.woorockets.com/niche-00",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-00_sample_data.zip",\n "tags": ["all"],\n "main": true,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/home.jpg"\n },\n "home-02": {\n "name": "Home - 02",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/home-02.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/home-02.jpg"\n },\n "home-03": {\n "name": "Home - 03",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/home-03.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/home-03.jpg"\n },\n "home-04": {\n "name": "Home - 04",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/home-04.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/home-04.jpg"\n },\n "home-05": {\n "name": "Home - 05",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/home-05.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/home-05.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/about.jpg"\n },\n "faq": {\n "name": "FAQs",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/faq.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/faq.jpg"\n },\n "lookbook": {\n "name": "Lookbook",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/lookbook.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/lookbook.jpg"\n },\n "product-mapper": {\n "name": "Product Mapper",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/product-mapper.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/product-mapper.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-00/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-00/contact.jpg"\n }\n }\n },\n {\n "id": "niche-21",\n "name": "Taste Tea",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-21.jpg",\n "demo": "http://nitro.woorockets.com/niche-21",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-21_sample_data.zip",\n "tags": ["single-product"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-21/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-21/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-21/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-21/about.jpg"\n },\n "contact": {\n "name": "Contact us",\n "download": "http://www.woorockets.com/files/sampledata/niche-21/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-21/contact.jpg"\n }\n }\n },\n {\n "id": "niche-20",\n "name": "Citiz Market",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-20.jpg",\n "demo": "http://nitro.woorockets.com/niche-20",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-20_sample_data.zip",\n "tags": ["wholesales"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-20/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-20/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-20/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-20/about.jpg"\n },\n "contact": {\n "name": "Contact us",\n "download": "http://www.woorockets.com/files/sampledata/niche-20/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-20/contact.jpg"\n }\n }\n },\n {\n "id": "niche-18",\n "name": "Brasity",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-18.jpg",\n "demo": "http://nitro.woorockets.com/niche-18",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-18_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-18/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-18/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-18/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-18/about.jpg"\n },\n "contact": {\n "name": "Contact us",\n "download": "http://www.woorockets.com/files/sampledata/niche-18/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-18/contact.jpg"\n }\n }\n },\n {\n "id": "niche-13",\n "name": "Pet Accessories",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-13.jpg",\n "demo": "http://nitro.woorockets.com/niche-13",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-13_sample_data.zip",\n "tags": ["accessories"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-13/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-13/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-13/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-13/about.jpg"\n },\n "contact": {\n "name": "Contact us",\n "download": "http://www.woorockets.com/files/sampledata/niche-13/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-13/contact.jpg"\n },\n "sale": {\n "name": "Sale",\n "download": "http://www.woorockets.com/files/sampledata/niche-13/sale.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-13/sale.jpg"\n }\n }\n },\n {\n "id": "niche-15",\n "name": "Sports Equipment",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-15.jpg",\n "demo": "http://nitro.woorockets.com/niche-15",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-15_sample_data.zip",\n "tags": ["sport"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-15/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-15/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-15/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-15/about.jpg"\n },\n "contact": {\n "name": "Contact us",\n "download": "http://www.woorockets.com/files/sampledata/niche-15/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-15/contact.jpg"\n }\n }\n },\n {\n "id": "niche-24",\n "name": "WatchMatch",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-24.jpg",\n "demo": "http://nitro.woorockets.com/niche-24",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-24_sample_data.zip",\n "tags": ["beauty"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-24/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-24/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-24/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-24/about.jpg"\n },\n "clearance": {\n "name": "Clearance",\n "download": "http://www.woorockets.com/files/sampledata/niche-24/clearance.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-24/clearance.jpg"\n }\n }\n },\n {\n "id": "niche-23",\n "name": "Digibits",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-23.jpg",\n "demo": "http://nitro.woorockets.com/niche-23",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-23_sample_data.zip",\n "tags": ["beauty"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-23/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-23/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-23/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-23/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-23/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-23/contact.jpg"\n }\n }\n },\n {\n "id": "niche-22",\n "name": "Venus",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-22.jpg",\n "demo": "http://nitro.woorockets.com/niche-22",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-22_sample_data.zip",\n "tags": ["beauty"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-22/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-22/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-22/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-22/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-22/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-22/contact.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-22/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-22/sales.jpg"\n }\n }\n },\n {\n "id": "niche-07",\n "name": "Glasia",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-07.jpg",\n "demo": "http://nitro.woorockets.com/niche-07",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-07_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-07/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-07/home.jpg"\n },\n "our-stories": {\n "name": "Our Stories",\n "download": "http://www.woorockets.com/files/sampledata/niche-07/our-stories.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-07/our-stories.jpg"\n },\n "store-location": {\n "name": "Store Location",\n "download": "http://www.woorockets.com/files/sampledata/niche-07/store-location.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-07/store-location.jpg"\n }\n }\n },\n {\n "id": "niche-16",\n "name": "Organia",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-16.jpg",\n "demo": "http://nitro.woorockets.com/niche-16",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-16_sample_data.zip",\n "tags": ["food & drink"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-16/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-16/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-16/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-16/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-16/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-16/contact.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-16/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-16/sales.jpg"\n }\n }\n },\n {\n "id": "niche-05",\n "name": "Mondo",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-05.jpg",\n "demo": "http://nitro.woorockets.com/niche-05",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-05_sample_data.zip",\n "tags": ["decor & furniture"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-05/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-05/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-05/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-05/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-05/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-05/contact.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-05/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-05/sales.jpg"\n }\n }\n },\n {\n "id": "niche-06",\n "name": "Medisene",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-06.jpg",\n "demo": "http://nitro.woorockets.com/niche-06",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-06_sample_data.zip",\n "tags": ["health"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-06/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-06/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-06/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-06/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-06/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-06/contact.jpg"\n }\n }\n },\n {\n "id": "niche-09",\n "name": "Fashion Store",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-09.jpg",\n "demo": "http://nitro.woorockets.com/niche-09",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-09_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-09/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-09/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-09/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-09/about.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-09/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-09/sales.jpg"\n }\n }\n },\n {\n "id": "niche-04",\n "name": "Women Fashion",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-04.jpg",\n "demo": "http://nitro.woorockets.com/niche-04",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-04_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-04/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-04/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-04/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-04/about.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-04/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-04/sales.jpg"\n }\n }\n },\n {\n "id": "niche-02",\n "name": "Men Fashion",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-02.jpg",\n "demo": "http://nitro.woorockets.com/niche-02",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-02_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-02/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-02/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-02/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-02/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-02/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-02/contact.jpg"\n }\n }\n },\n {\n "id": "niche-11",\n "name": "Teen Fashion",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-11.jpg",\n "demo": "http://nitro.woorockets.com/niche-11",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-11_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-11/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-11/home.jpg"\n },\n "location": {\n "name": "Location",\n "download": "http://www.woorockets.com/files/sampledata/niche-11/location.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-11/location.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-11/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-11/sales.jpg"\n }\n }\n },\n {\n "id": "niche-17",\n "name": "Kid Fashion",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-17.jpg",\n "demo": "http://nitro.woorockets.com/niche-17",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-17_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-17/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-17/home.jpg"\n },\n "store-location": {\n "name": "Store Location",\n "download": "http://www.woorockets.com/files/sampledata/niche-17/store-location.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-17/store-location.jpg"\n }\n }\n },\n {\n "id": "niche-12",\n "name": "Jewelry / Accessories",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-12.jpg",\n "demo": "http://nitro.woorockets.com/niche-12",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-12_sample_data.zip",\n "tags": ["jewelry"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-12/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-12/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-12/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-12/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-12/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-12/contact.jpg"\n },\n "lookbook": {\n "name": "Lookbook",\n "download": "http://www.woorockets.com/files/sampledata/niche-12/lookbook.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-12/lookbook.jpg"\n },\n "testimonials": {\n "name": "Testimonial",\n "download": "http://www.woorockets.com/files/sampledata/niche-12/testimonials.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-12/testimonials.jpg"\n }\n }\n },\n {\n "id": "niche-08",\n "name": "Shoes",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-08.jpg",\n "demo": "http://nitro.woorockets.com/niche-08",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-08_sample_data.zip",\n "tags": ["fashion"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-08/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-08/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-08/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-08/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-08/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-08/contact.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-08/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-08/sales.jpg"\n }\n }\n },\n {\n "id": "niche-03",\n "name": "Electronic Gadgets",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-03.jpg",\n "demo": "http://nitro.woorockets.com/niche-03",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-03_sample_data.zip",\n "tags": ["electronics"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-03/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-03/home.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-03/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-03/contact.jpg"\n },\n "sales": {\n "name": "Sales",\n "download": "http://www.woorockets.com/files/sampledata/niche-03/sales.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-03/sales.jpg"\n }\n }\n },\n {\n "id": "niche-01",\n "name": "Bakery / Coffee Shop",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-01.jpg",\n "demo": "http://nitro.woorockets.com/niche-01",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-01_sample_data.zip",\n "tags": ["food & drink"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-01/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-01/home.jpg"\n },\n "menu": {\n "name": "Menu",\n "download": "http://www.woorockets.com/files/sampledata/niche-01/menu.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-01/menu.jpg"\n },\n "reservations": {\n "name": "Reservations",\n "download": "http://www.woorockets.com/files/sampledata/niche-01/reservations.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-01/reservations.jpg"\n }\n }\n },\n {\n "id": "niche-19",\n "name": "Book Author",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-19.jpg",\n "demo": "http://nitro.woorockets.com/niche-19",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-19_sample_data.zip",\n "tags": ["book & novel"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-19/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-19/home.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-19/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-19/contact.jpg"\n },\n "author": {\n "name": "Author",\n "download": "http://www.woorockets.com/files/sampledata/niche-19/author.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-19/author.jpg"\n }\n }\n },\n {\n "id": "niche-10",\n "name": "Decor / Furniture",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-10.jpg",\n "demo": "http://nitro.woorockets.com/niche-10",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-10_sample_data.zip",\n "tags": ["decor"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-10/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-10/home.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-10/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-10/contact.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-10/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-10/about.jpg"\n },\n "collection": {\n "name": "Collection",\n "download": "http://www.woorockets.com/files/sampledata/niche-10/collection.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-10/collection.jpg"\n }\n }\n },\n {\n "id": "niche-14",\n "name": "Sport Gears",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/niche-14.jpg",\n "demo": "http://nitro.woorockets.com/niche-14",\n "download": "http://www.woorockets.com/files/sampledata/nitro_niche-14_sample_data.zip",\n "tags": ["sport"],\n "main": false,\n "sample-page": {\n "home": {\n "name": "Home",\n "download": "http://www.woorockets.com/files/sampledata/niche-14/home.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-14/home.jpg"\n },\n "about": {\n "name": "About us",\n "download": "http://www.woorockets.com/files/sampledata/niche-14/about.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-14/about.jpg"\n },\n "contact": {\n "name": "Contact",\n "download": "http://www.woorockets.com/files/sampledata/niche-14/contact.xml",\n "thumbail": "http://www.woorockets.com/files/sampledata/niche-14/contact.jpg"\n }\n }\n },\n {\n "name": "Suggest Demo",\n "thumbail": "http://www.woorockets.com/files/sampledata/screenshot/demo-suggestion.jpg",\n "demo": "http://www.woorockets.com/contact",\n "text": "Suggest",\n "main": false\n }\n]\n', 'no'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('155', 'wr_download_token', 'f4ed0db95d4a3ba433292c93a847936a', 'yes'); INSERT INTO `dbdkeniz_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES ('156', 'nitro_customer', 'a:4:{s:4:"name";s:13:"Attila Akyüz";s:5:"email";s:16:"attila@madads.de";s:13:"purchase_code";s:36:"98a61eb4-e349-447c-933a-a99603e6ca57";s:8:"timezone";s:4:"-345";}', 'yes'); DROP TABLE IF EXISTS `dbdkeniz_postmeta`; CREATE TABLE IF NOT EXISTS `dbdkeniz_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191))) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES ('1', '2', '_wp_page_template', 'default'); INSERT INTO `dbdkeniz_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES ('2', '3', '_wp_page_template', 'default'); INSERT INTO `dbdkeniz_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES ('5', '6', 'hb_status', 'default'); DROP TABLE IF EXISTS `dbdkeniz_posts`; CREATE TABLE IF NOT EXISTS `dbdkeniz_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=InnoDB AUTO_INCREMENT=7 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_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', '2018-08-03 09:09:53', '2018-08-03 09:09:53', 'Welcome to WordPress. This is your first post. Edit or delete it, then start writing!', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2018-08-03 09:09:53', '2018-08-03 09:09:53', '', '0', 'http://localhost/dkeniz/?p=1', '0', 'post', '', '1'); INSERT INTO `dbdkeniz_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 ('2', '1', '2018-08-03 09:09:53', '2018-08-03 09:09:53', '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

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...or something like this:\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\nAs a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!', 'Sample Page', '', 'publish', 'closed', 'open', '', 'sample-page', '', '', '2018-08-03 09:09:53', '2018-08-03 09:09:53', '', '0', 'http://localhost/dkeniz/?page_id=2', '0', 'page', '', '0'); INSERT INTO `dbdkeniz_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 ('3', '1', '2018-08-03 09:09:53', '2018-08-03 09:09:53', '

Who we are

Our website address is: http://localhost/dkeniz.

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 have an account and you log in to this site, 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', '', '', '2018-08-03 09:09:53', '2018-08-03 09:09:53', '', '0', 'http://localhost/dkeniz/?page_id=3', '0', 'page', '', '0'); INSERT INTO `dbdkeniz_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 ('4', '1', '2018-08-03 09:12:44', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2018-08-03 09:12:44', '0000-00-00 00:00:00', '', '0', 'http://localhost/dkeniz/?p=4', '0', 'post', '', '0'); INSERT INTO `dbdkeniz_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 ('6', '1', '2018-08-03 09:17:10', '2018-08-03 09:17:10', 'a:6:{s:7:"desktop";a:2:{s:4:"rows";a:1:{i:0;a:7:{s:4:"cols";a:1:{i:0;a:3:{s:5:"items";a:2:{i:0;a:7:{s:4:"_rel";s:4:"logo";s:5:"index";i:0;s:5:"style";a:17:{s:10:"paddingTop";i:10;s:13:"paddingBottom";i:10;s:12:"paddingRight";i:10;s:11:"paddingLeft";i:10;s:8:"maxWidth";i:138;s:14:"borderTopWidth";i:0;s:17:"borderBottomWidth";i:0;s:15:"borderLeftWidth";i:0;s:16:"borderRightWidth";i:0;s:11:"borderStyle";s:4:"none";s:11:"borderColor";s:0:"";s:10:"fontFamily";s:4:"Lato";s:8:"fontSize";i:20;s:10:"lineHeight";i:30;s:13:"letterSpacing";i:0;s:5:"color";s:7:"#333333";s:10:"fontWeight";i:400;}s:7:"content";s:4:"Logo";s:8:"logoType";s:5:"image";s:9:"logoImage";s:84:"http://localhost/dkeniz/wp-content/themes/wr-nitro/assets/woorockets/images/logo.png";s:13:"alignVertical";s:4:"left";}i:1;a:3:{s:4:"_rel";s:4:"flex";s:5:"style";a:0:{}s:5:"index";i:1;}}s:4:"unit";s:2:"px";s:5:"style";a:8:{s:8:"maxWidth";s:4:"1170";s:14:"borderTopWidth";i:0;s:17:"borderBottomWidth";i:0;s:15:"borderLeftWidth";i:0;s:16:"borderRightWidth";i:0;s:11:"borderStyle";s:4:"none";s:11:"borderColor";s:0:"";s:15:"backgroundColor";s:0:"";}}}s:5:"style";a:7:{s:14:"borderTopWidth";i:0;s:17:"borderBottomWidth";i:0;s:15:"borderLeftWidth";i:0;s:16:"borderRightWidth";i:0;s:11:"borderStyle";s:4:"none";s:11:"borderColor";s:0:"";s:15:"backgroundColor";s:0:"";}s:8:"vertical";b:1;s:21:"backgroundColorSticky";s:0:"";s:15:"textColorSticky";s:0:"";s:6:"sticky";b:0;s:5:"index";i:0;}}s:8:"settings";a:8:{s:4:"type";s:10:"horizontal";s:8:"position";s:7:"inherit";s:16:"positionVertical";s:4:"left";s:4:"unit";s:2:"px";s:13:"showHideFixed";s:4:"hide";s:9:"fixedList";a:5:{s:13:"miscellaneous";a:0:{}s:25:"custom_post_type_archives";a:0:{}s:10:"taxonomies";a:0:{}s:6:"single";a:0:{}s:5:"pages";a:0:{}}s:5:"style";a:8:{s:5:"width";i:400;s:14:"borderTopWidth";i:0;s:17:"borderBottomWidth";i:0;s:15:"borderLeftWidth";i:0;s:16:"borderRightWidth";i:0;s:11:"borderStyle";s:4:"none";s:11:"borderColor";s:0:"";s:15:"backgroundColor";s:0:"";}s:8:"selected";b:0;}}s:6:"mobile";a:3:{s:4:"rows";a:0:{}s:8:"settings";a:2:{s:5:"style";a:0:{}s:4:"type";i:1;}s:4:"type";s:6:"mobile";}s:9:"listFonts";a:0:{}s:6:"layout";s:7:"desktop";s:8:"hbLayout";s:10:"horizontal";s:12:"switchLayout";b:0;}', 'Header sample', '', 'publish', 'closed', 'closed', '', 'header-sample', '', '', '2018-08-03 09:17:10', '2018-08-03 09:17:10', '', '0', 'http://localhost/dkeniz/2018/08/03/header-sample/', '0', 'header_builder', '', '0'); DROP TABLE IF EXISTS `dbdkeniz_termmeta`; CREATE TABLE IF NOT EXISTS `dbdkeniz_termmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `term_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`meta_id`), KEY `term_id` (`term_id`), KEY `meta_key` (`meta_key`(191))) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; DROP TABLE IF EXISTS `dbdkeniz_terms`; CREATE TABLE IF NOT EXISTS `dbdkeniz_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=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES ('1', 'Uncategorized', 'uncategorized', '0'); DROP TABLE IF EXISTS `dbdkeniz_term_relationships`; CREATE TABLE IF NOT EXISTS `dbdkeniz_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=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES ('1', '1', '0'); DROP TABLE IF EXISTS `dbdkeniz_term_taxonomy`; CREATE TABLE IF NOT EXISTS `dbdkeniz_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=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES ('1', '1', 'category', '', '0', '1'); DROP TABLE IF EXISTS `dbdkeniz_usermeta`; CREATE TABLE IF NOT EXISTS `dbdkeniz_usermeta` ( `umeta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci, PRIMARY KEY (`umeta_id`), KEY `user_id` (`user_id`), KEY `meta_key` (`meta_key`(191))) ENGINE=InnoDB AUTO_INCREMENT=18 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('1', '1', 'nickname', 'Dkenizadmin'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('2', '1', 'first_name', ''); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('3', '1', 'last_name', ''); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('4', '1', 'description', ''); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('5', '1', 'rich_editing', 'true'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('6', '1', 'syntax_highlighting', 'true'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('7', '1', 'comment_shortcuts', 'false'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('8', '1', 'admin_color', 'fresh'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('9', '1', 'use_ssl', '0'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('10', '1', 'show_admin_bar_front', 'true'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('11', '1', 'locale', ''); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('12', '1', 'dbdkeniz_capabilities', 'a:1:{s:13:"administrator";b:1;}'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('13', '1', 'dbdkeniz_user_level', '10'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('14', '1', 'dismissed_wp_pointers', 'wp496_privacy'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('15', '1', 'show_welcome_panel', '1'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('16', '1', 'session_tokens', 'a:1:{s:64:"f51119b07788864b157608b04c2d4feee678bf2429e252a3e5552152a19d5b80";a:4:{s:10:"expiration";i:1534497160;s:2:"ip";s:3:"::1";s:2:"ua";s:114:"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.84 Safari/537.36";s:5:"login";i:1533287560;}}'); INSERT INTO `dbdkeniz_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES ('17', '1', 'dbdkeniz_dashboard_quick_press_last_post_id', '4'); DROP TABLE IF EXISTS `dbdkeniz_users`; CREATE TABLE IF NOT EXISTS `dbdkeniz_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=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; INSERT INTO `dbdkeniz_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES ('1', 'Dkenizadmin', '$P$Bkk0z1sQuKr2/4a0qixTp2KDg1C/Pk1', 'dkenizadmin', 'roka.manoj12@gmail.com', '', '2018-08-03 09:09:51', '', '0', 'Dkenizadmin');

“Try Gutenberg” callout

Privacy fixes/enhancements

Release of WordPress 4.9.7

The New WordPress Editor

Page Design Updates on WordPress.org

The First WP-CLI Hack Day

Further Reading:

Meta (WordPress.org Site)

In Progress

July

August and beyond

Another Successful WordCamp Europe

Updated Roadmap for the New WordPress Content Editor

WordCamp Incubator Cities Announced

Further Reading:

Local Communities Celebrate the 15th Anniversary of WordPress

Privacy Tools added to WordPress core

Updates to the WordPress.org Privacy Policy

Further Reading:

Privacy

Comments

Privacy Policy Page

Data Handling

Data Export

Data Erasure

Maintenance

The WordPress 15th Anniversary is Coming

Work has Started on a Gutenberg Migration Guide

Theme Review Team Launches Trusted Authors Program

Further Reading:

“Try Gutenberg” callout

Privacy fixes/enhancements

Stories Discussed:

WPWeekly Meta:

Release of WordPress 4.9.7

The New WordPress Editor

Page Design Updates on WordPress.org

The First WP-CLI Hack Day

Further Reading:

Begin at the Beginning…

Go On…

And on…

Till You Come to the End…

Twenty Sixteen Looks Better Without It

Stories Discussed:

WPWeekly Meta:

The Trials and Tribulations of Leading an Open Source Project

WordSesh Experiments with Charging Attendees for Tickets, Adds Real-Time Transcription

WordCamp Karachi Organizers Aim to Make a Positive Impact on Pakistan

Episode Links

Sponsor: Sandhills Development

What to Expect at WCEU in Berlin: A Diverse Community, More Workshops, and a Unique After Party

Interview With Cory Miller

Meta (WordPress.org Site)

Berlin to Host WordCamp Europe 2019

Behind the Scenes at WordCamp Europe 2018 with Lead Organizers Jenny Beaumont and Milan Ivanović

Stories Discussed:

WPWeekly Meta:

Who we are

What personal data we collect and why we collect it

Comments

Media

Contact forms

Cookies

Embedded content from other websites

Analytics

Who we share your data with

How long we retain your data

What rights you have over your data

Where we send your data

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