-- phpMyAdmin SQL Dump -- version phpStudy 2014 -- http://www.phpmyadmin.net -- -- Host: localhost -- Generation Time: May 22, 2019 at 03:34 PM -- Server version: 5.6.40-log -- PHP Version: 5.6.27 SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO"; SET time_zone = "+00:00"; /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; -- -- Database: `bcb5` -- -- -------------------------------------------------------- -- -- Table structure for table `wp_commentmeta` -- CREATE TABLE IF NOT EXISTS `wp_commentmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`meta_id`), KEY `comment_id` (`comment_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=1 ; -- -------------------------------------------------------- -- -- Table structure for table `wp_comments` -- CREATE TABLE IF NOT EXISTS `wp_comments` ( `comment_ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `comment_post_ID` bigint(20) unsigned NOT NULL DEFAULT '0', `comment_author` tinytext COLLATE utf8mb4_unicode_520_ci NOT NULL, `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_content` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `comment_karma` int(11) NOT NULL DEFAULT '0', `comment_approved` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '1', `comment_agent` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `user_id` bigint(20) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (`comment_ID`), KEY `comment_post_ID` (`comment_post_ID`), KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), KEY `comment_date_gmt` (`comment_date_gmt`), KEY `comment_parent` (`comment_parent`), KEY `comment_author_email` (`comment_author_email`(10)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=2 ; -- -- Dumping data for table `wp_comments` -- INSERT INTO `wp_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, '一位WordPress评论者', 'wapuu@wordpress.example', 'https://wordpress.org/', '', '2019-04-06 18:20:54', '2019-04-06 10:20:54', '嗨,这是一条评论。\n要开始审核、编辑及删除评论,请访问仪表盘的“评论”页面。\n评论者头像来自Gravatar。', 0, '1', '', '', 0, 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_links` -- CREATE TABLE IF NOT EXISTS `wp_links` ( `link_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `link_url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_image` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_target` varchar(25) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_description` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_visible` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'Y', `link_owner` bigint(20) unsigned NOT NULL DEFAULT '1', `link_rating` int(11) NOT NULL DEFAULT '0', `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `link_rel` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `link_notes` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `link_rss` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', PRIMARY KEY (`link_id`), KEY `link_visible` (`link_visible`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=1 ; -- -------------------------------------------------------- -- -- Table structure for table `wp_options` -- CREATE TABLE IF NOT EXISTS `wp_options` ( `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `option_name` varchar(191) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `option_value` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `autoload` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'yes', PRIMARY KEY (`option_id`), UNIQUE KEY `option_name` (`option_name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=271 ; -- -- Dumping data for table `wp_options` -- INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (1, 'siteurl', 'http://localhost', 'yes'), (2, 'home', 'http://localhost', 'yes'), (3, 'blogname', '农校旅游', 'yes'), (4, 'blogdescription', '-快乐的旅游网站', 'yes'), (5, 'users_can_register', '0', 'yes'), (6, 'admin_email', '1656004343@qq.com', 'yes'), (7, 'start_of_week', '1', 'yes'), (8, 'use_balanceTags', '0', 'yes'), (9, 'use_smilies', '1', 'yes'), (10, 'require_name_email', '1', 'yes'), (11, 'comments_notify', '1', 'yes'), (12, 'posts_per_rss', '10', 'yes'), (13, 'rss_use_excerpt', '0', 'yes'), (14, 'mailserver_url', 'mail.example.com', 'yes'), (15, 'mailserver_login', 'login@example.com', 'yes'), (16, 'mailserver_pass', 'password', 'yes'), (17, 'mailserver_port', '110', 'yes'), (18, 'default_category', '1', 'yes'), (19, 'default_comment_status', 'open', 'yes'), (20, 'default_ping_status', 'open', 'yes'), (21, 'default_pingback_flag', '0', 'yes'), (22, 'posts_per_page', '10', 'yes'), (23, 'date_format', 'Y年n月j日', 'yes'), (24, 'time_format', 'ag:i', 'yes'), (25, 'links_updated_date_format', 'Y年n月j日ag:i', 'yes'), (26, 'comment_moderation', '0', 'yes'), (27, 'moderation_notify', '1', 'yes'), (28, 'permalink_structure', '/%year%/%monthnum%/%day%/%postname%/', 'yes'), (29, 'rewrite_rules', 'a:140:{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:33:"album/[^/]+/attachment/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:43:"album/[^/]+/attachment/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:63:"album/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:58:"album/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:58:"album/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:39:"album/[^/]+/attachment/([^/]+)/embed/?$";s:43:"index.php?attachment=$matches[1]&embed=true";s:22:"album/([^/]+)/embed/?$";s:38:"index.php?album=$matches[1]&embed=true";s:26:"album/([^/]+)/trackback/?$";s:32:"index.php?album=$matches[1]&tb=1";s:34:"album/([^/]+)/page/?([0-9]{1,})/?$";s:45:"index.php?album=$matches[1]&paged=$matches[2]";s:41:"album/([^/]+)/comment-page-([0-9]{1,})/?$";s:45:"index.php?album=$matches[1]&cpage=$matches[2]";s:30:"album/([^/]+)(?:/([0-9]+))?/?$";s:44:"index.php?album=$matches[1]&page=$matches[2]";s:22:"album/[^/]+/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:32:"album/[^/]+/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:52:"album/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:47:"album/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:47:"album/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:28:"album/[^/]+/([^/]+)/embed/?$";s:43:"index.php?attachment=$matches[1]&embed=true";s:44:"genre/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$";s:44:"index.php?genre=$matches[1]&feed=$matches[2]";s:39:"genre/(.+?)/(feed|rdf|rss|rss2|atom)/?$";s:44:"index.php?genre=$matches[1]&feed=$matches[2]";s:20:"genre/(.+?)/embed/?$";s:38:"index.php?genre=$matches[1]&embed=true";s:32:"genre/(.+?)/page/?([0-9]{1,})/?$";s:45:"index.php?genre=$matches[1]&paged=$matches[2]";s:14:"genre/(.+?)/?$";s:27:"index.php?genre=$matches[1]";s:32:"work/[^/]+/attachment/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:42:"work/[^/]+/attachment/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:62:"work/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:57:"work/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:57:"work/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:38:"work/[^/]+/attachment/([^/]+)/embed/?$";s:43:"index.php?attachment=$matches[1]&embed=true";s:21:"work/([^/]+)/embed/?$";s:37:"index.php?work=$matches[1]&embed=true";s:25:"work/([^/]+)/trackback/?$";s:31:"index.php?work=$matches[1]&tb=1";s:33:"work/([^/]+)/page/?([0-9]{1,})/?$";s:44:"index.php?work=$matches[1]&paged=$matches[2]";s:40:"work/([^/]+)/comment-page-([0-9]{1,})/?$";s:44:"index.php?work=$matches[1]&cpage=$matches[2]";s:29:"work/([^/]+)(?:/([0-9]+))?/?$";s:43:"index.php?work=$matches[1]&page=$matches[2]";s:21:"work/[^/]+/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:31:"work/[^/]+/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:51:"work/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:46:"work/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:46:"work/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:27:"work/[^/]+/([^/]+)/embed/?$";s:43:"index.php?attachment=$matches[1]&embed=true";s:49:"work_genre/(.+?)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?work_genre=$matches[1]&feed=$matches[2]";s:44:"work_genre/(.+?)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?work_genre=$matches[1]&feed=$matches[2]";s:25:"work_genre/(.+?)/embed/?$";s:43:"index.php?work_genre=$matches[1]&embed=true";s:37:"work_genre/(.+?)/page/?([0-9]{1,})/?$";s:50:"index.php?work_genre=$matches[1]&paged=$matches[2]";s:19:"work_genre/(.+?)/?$";s:32:"index.php?work_genre=$matches[1]";s:46:"group/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:44:"index.php?group=$matches[1]&feed=$matches[2]";s:41:"group/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:44:"index.php?group=$matches[1]&feed=$matches[2]";s:22:"group/([^/]+)/embed/?$";s:38:"index.php?group=$matches[1]&embed=true";s:34:"group/([^/]+)/page/?([0-9]{1,})/?$";s:45:"index.php?group=$matches[1]&paged=$matches[2]";s:16:"group/([^/]+)/?$";s:27:"index.php?group=$matches[1]";s:12:"robots\\.txt$";s:18:"index.php?robots=1";s:48:".*wp-(atom|rdf|rss|rss2|feed|commentsrss2)\\.php$";s:18:"index.php?feed=old";s:20:".*wp-app\\.php(/.*)?$";s:19:"index.php?error=403";s:18:".*wp-register.php$";s:23:"index.php?register=true";s:32:"feed/(feed|rdf|rss|rss2|atom)/?$";s:27:"index.php?&feed=$matches[1]";s:27:"(feed|rdf|rss|rss2|atom)/?$";s:27:"index.php?&feed=$matches[1]";s:8:"embed/?$";s:21:"index.php?&embed=true";s:20:"page/?([0-9]{1,})/?$";s:28:"index.php?&paged=$matches[1]";s:27:"comment-page-([0-9]{1,})/?$";s:38:"index.php?&page_id=2&cpage=$matches[1]";s:41:"comments/feed/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?&feed=$matches[1]&withcomments=1";s:36:"comments/(feed|rdf|rss|rss2|atom)/?$";s:42:"index.php?&feed=$matches[1]&withcomments=1";s:17:"comments/embed/?$";s:21:"index.php?&embed=true";s:44:"search/(.+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:40:"index.php?s=$matches[1]&feed=$matches[2]";s:39:"search/(.+)/(feed|rdf|rss|rss2|atom)/?$";s:40:"index.php?s=$matches[1]&feed=$matches[2]";s:20:"search/(.+)/embed/?$";s:34:"index.php?s=$matches[1]&embed=true";s:32:"search/(.+)/page/?([0-9]{1,})/?$";s:41:"index.php?s=$matches[1]&paged=$matches[2]";s:14:"search/(.+)/?$";s:23:"index.php?s=$matches[1]";s:47:"author/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?author_name=$matches[1]&feed=$matches[2]";s:42:"author/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:50:"index.php?author_name=$matches[1]&feed=$matches[2]";s:23:"author/([^/]+)/embed/?$";s:44:"index.php?author_name=$matches[1]&embed=true";s:35:"author/([^/]+)/page/?([0-9]{1,})/?$";s:51:"index.php?author_name=$matches[1]&paged=$matches[2]";s:17:"author/([^/]+)/?$";s:33:"index.php?author_name=$matches[1]";s:69:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$";s:80:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]";s:64:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$";s:80:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&feed=$matches[4]";s:45:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/embed/?$";s:74:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&embed=true";s:57:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/page/?([0-9]{1,})/?$";s:81:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&paged=$matches[4]";s:39:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/?$";s:63:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]";s:56:"([0-9]{4})/([0-9]{1,2})/feed/(feed|rdf|rss|rss2|atom)/?$";s:64:"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]";s:51:"([0-9]{4})/([0-9]{1,2})/(feed|rdf|rss|rss2|atom)/?$";s:64:"index.php?year=$matches[1]&monthnum=$matches[2]&feed=$matches[3]";s:32:"([0-9]{4})/([0-9]{1,2})/embed/?$";s:58:"index.php?year=$matches[1]&monthnum=$matches[2]&embed=true";s:44:"([0-9]{4})/([0-9]{1,2})/page/?([0-9]{1,})/?$";s:65:"index.php?year=$matches[1]&monthnum=$matches[2]&paged=$matches[3]";s:26:"([0-9]{4})/([0-9]{1,2})/?$";s:47:"index.php?year=$matches[1]&monthnum=$matches[2]";s:43:"([0-9]{4})/feed/(feed|rdf|rss|rss2|atom)/?$";s:43:"index.php?year=$matches[1]&feed=$matches[2]";s:38:"([0-9]{4})/(feed|rdf|rss|rss2|atom)/?$";s:43:"index.php?year=$matches[1]&feed=$matches[2]";s:19:"([0-9]{4})/embed/?$";s:37:"index.php?year=$matches[1]&embed=true";s:31:"([0-9]{4})/page/?([0-9]{1,})/?$";s:44:"index.php?year=$matches[1]&paged=$matches[2]";s:13:"([0-9]{4})/?$";s:26:"index.php?year=$matches[1]";s:58:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:68:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:88:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:83:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:83:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:64:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/attachment/([^/]+)/embed/?$";s:43:"index.php?attachment=$matches[1]&embed=true";s:53:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/embed/?$";s:91:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&embed=true";s:57:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/trackback/?$";s:85:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&tb=1";s:77:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:97:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]";s:72:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:97:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&feed=$matches[5]";s:65:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/page/?([0-9]{1,})/?$";s:98:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&paged=$matches[5]";s:72:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)/comment-page-([0-9]{1,})/?$";s:98:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&cpage=$matches[5]";s:61:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/([^/]+)(?:/([0-9]+))?/?$";s:97:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&name=$matches[4]&page=$matches[5]";s:47:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:57:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:77:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:72:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:72:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:53:"[0-9]{4}/[0-9]{1,2}/[0-9]{1,2}/[^/]+/([^/]+)/embed/?$";s:43:"index.php?attachment=$matches[1]&embed=true";s:64:"([0-9]{4})/([0-9]{1,2})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$";s:81:"index.php?year=$matches[1]&monthnum=$matches[2]&day=$matches[3]&cpage=$matches[4]";s:51:"([0-9]{4})/([0-9]{1,2})/comment-page-([0-9]{1,})/?$";s:65:"index.php?year=$matches[1]&monthnum=$matches[2]&cpage=$matches[3]";s:38:"([0-9]{4})/comment-page-([0-9]{1,})/?$";s:44:"index.php?year=$matches[1]&cpage=$matches[2]";s:27:".?.+?/attachment/([^/]+)/?$";s:32:"index.php?attachment=$matches[1]";s:37:".?.+?/attachment/([^/]+)/trackback/?$";s:37:"index.php?attachment=$matches[1]&tb=1";s:57:".?.+?/attachment/([^/]+)/feed/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:52:".?.+?/attachment/([^/]+)/(feed|rdf|rss|rss2|atom)/?$";s:49:"index.php?attachment=$matches[1]&feed=$matches[2]";s:52:".?.+?/attachment/([^/]+)/comment-page-([0-9]{1,})/?$";s:50:"index.php?attachment=$matches[1]&cpage=$matches[2]";s:33:".?.+?/attachment/([^/]+)/embed/?$";s:43:"index.php?attachment=$matches[1]&embed=true";s:16:"(.?.+?)/embed/?$";s:41:"index.php?pagename=$matches[1]&embed=true";s:20:"(.?.+?)/trackback/?$";s:35:"index.php?pagename=$matches[1]&tb=1";s:40:"(.?.+?)/feed/(feed|rdf|rss|rss2|atom)/?$";s:47:"index.php?pagename=$matches[1]&feed=$matches[2]";s:35:"(.?.+?)/(feed|rdf|rss|rss2|atom)/?$";s:47:"index.php?pagename=$matches[1]&feed=$matches[2]";s:28:"(.?.+?)/page/?([0-9]{1,})/?$";s:48:"index.php?pagename=$matches[1]&paged=$matches[2]";s:35:"(.?.+?)/comment-page-([0-9]{1,})/?$";s:48:"index.php?pagename=$matches[1]&cpage=$matches[2]";s:24:"(.?.+?)(?:/([0-9]+))?/?$";s:47:"index.php?pagename=$matches[1]&page=$matches[2]";}', 'yes'), (30, 'hack_file', '0', 'yes'), (31, 'blog_charset', 'UTF-8', 'yes'), (32, 'moderation_keys', '', 'no'), (33, 'active_plugins', 'a:2:{i:0;s:63:"apollo13-framework-extensions/apollo13-framework-extensions.php";i:1;s:55:"rife-elementor-extensions/rife-elementor-extensions.php";}', 'yes'), (34, 'category_base', '', 'yes'), (35, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'), (36, 'comment_max_links', '2', 'yes'), (37, 'gmt_offset', '0', 'yes'), (38, 'default_email_category', '1', 'yes'), (39, 'recently_edited', 'a:4:{i:0;s:65:"C:\\myphp_www\\PHPTutorial\\WWW/wp-content/themes/rife-free/page.php";i:1;s:66:"C:\\myphp_www\\PHPTutorial\\WWW/wp-content/themes/rife-free/style.css";i:2;s:66:"C:\\myphp_www\\PHPTutorial\\WWW/wp-content/themes/rife-free/index.php";i:3;s:0:"";}', 'no'), (40, 'template', 'rife-free', 'yes'), (41, 'stylesheet', 'rife-free', 'yes'), (42, 'comment_whitelist', '1', 'yes'), (43, 'blacklist_keys', '', 'no'), (44, 'comment_registration', '0', 'yes'), (45, 'html_type', 'text/html', 'yes'), (46, 'use_trackback', '0', 'yes'), (47, 'default_role', 'subscriber', 'yes'), (48, 'db_version', '43764', 'yes'), (49, 'uploads_use_yearmonth_folders', '1', 'yes'), (50, 'upload_path', '', 'yes'), (51, 'blog_public', '0', 'yes'), (52, 'default_link_category', '2', 'yes'), (53, 'show_on_front', 'page', 'yes'), (54, 'tag_base', '', 'yes'), (55, 'show_avatars', '1', 'yes'), (56, 'avatar_rating', 'G', 'yes'), (57, 'upload_url_path', '', 'yes'), (58, 'thumbnail_size_w', '150', 'yes'), (59, 'thumbnail_size_h', '150', 'yes'), (60, 'thumbnail_crop', '1', 'yes'), (61, 'medium_size_w', '300', 'yes'), (62, 'medium_size_h', '300', 'yes'), (63, 'avatar_default', 'mystery', 'yes'), (64, 'large_size_w', '1024', 'yes'), (65, 'large_size_h', '1024', 'yes'), (66, 'image_default_link_type', 'none', 'yes'), (67, 'image_default_size', '', 'yes'), (68, 'image_default_align', '', 'yes'), (69, 'close_comments_for_old_posts', '0', 'yes'), (70, 'close_comments_days_old', '14', 'yes'), (71, 'thread_comments', '1', 'yes'), (72, 'thread_comments_depth', '5', 'yes'), (73, 'page_comments', '0', 'yes'), (74, 'comments_per_page', '50', 'yes'), (75, 'default_comments_page', 'newest', 'yes'), (76, 'comment_order', 'asc', 'yes'), (77, 'sticky_posts', 'a:0:{}', 'yes'), (78, 'widget_categories', 'a:2:{i:2;a:4:{s:5:"title";s:0:"";s:5:"count";i:0;s:12:"hierarchical";i:0;s:8:"dropdown";i:0;}s:12:"_multiwidget";i:1;}', 'yes'), (79, 'widget_text', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (80, 'widget_rss', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (81, 'uninstall_plugins', 'a:0:{}', 'no'), (82, 'timezone_string', 'Asia/Shanghai', 'yes'), (83, 'page_for_posts', '0', 'yes'), (84, 'page_on_front', '2', 'yes'), (85, 'default_post_format', '0', 'yes'), (86, 'link_manager_enabled', '0', 'yes'), (87, 'finished_splitting_shared_terms', '1', 'yes'), (88, 'site_icon', '0', 'yes'), (89, 'medium_large_size_w', '768', 'yes'), (90, 'medium_large_size_h', '0', 'yes'), (91, 'wp_page_for_privacy_policy', '3', 'yes'), (92, 'show_comments_cookies_opt_in', '0', 'yes'), (93, 'initial_db_version', '43764', 'yes'), (94, 'wp_user_roles', 'a:5:{s:13:"administrator";a:2:{s:4:"name";s:13:"Administrator";s:12:"capabilities";a:61:{s:13:"switch_themes";b:1;s:11:"edit_themes";b:1;s:16:"activate_plugins";b:1;s:12:"edit_plugins";b:1;s:10:"edit_users";b:1;s:10:"edit_files";b:1;s:14:"manage_options";b:1;s:17:"moderate_comments";b:1;s:17:"manage_categories";b:1;s:12:"manage_links";b:1;s:12:"upload_files";b:1;s:6:"import";b:1;s:15:"unfiltered_html";b:1;s:10:"edit_posts";b:1;s:17:"edit_others_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:10:"edit_pages";b:1;s:4:"read";b:1;s:8:"level_10";b:1;s:7:"level_9";b:1;s:7:"level_8";b:1;s:7:"level_7";b:1;s:7:"level_6";b:1;s:7:"level_5";b:1;s:7:"level_4";b:1;s:7:"level_3";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:17:"edit_others_pages";b:1;s:20:"edit_published_pages";b:1;s:13:"publish_pages";b:1;s:12:"delete_pages";b:1;s:19:"delete_others_pages";b:1;s:22:"delete_published_pages";b:1;s:12:"delete_posts";b:1;s:19:"delete_others_posts";b:1;s:22:"delete_published_posts";b:1;s:20:"delete_private_posts";b:1;s:18:"edit_private_posts";b:1;s:18:"read_private_posts";b:1;s:20:"delete_private_pages";b:1;s:18:"edit_private_pages";b:1;s:18:"read_private_pages";b:1;s:12:"delete_users";b:1;s:12:"create_users";b:1;s:17:"unfiltered_upload";b:1;s:14:"edit_dashboard";b:1;s:14:"update_plugins";b:1;s:14:"delete_plugins";b:1;s:15:"install_plugins";b:1;s:13:"update_themes";b:1;s:14:"install_themes";b:1;s:11:"update_core";b:1;s:10:"list_users";b:1;s:12:"remove_users";b:1;s:13:"promote_users";b:1;s:18:"edit_theme_options";b:1;s:13:"delete_themes";b:1;s:6:"export";b:1;}}s:6:"editor";a:2:{s:4:"name";s:6:"Editor";s:12:"capabilities";a:34:{s:17:"moderate_comments";b:1;s:17:"manage_categories";b:1;s:12:"manage_links";b:1;s:12:"upload_files";b:1;s:15:"unfiltered_html";b:1;s:10:"edit_posts";b:1;s:17:"edit_others_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:10:"edit_pages";b:1;s:4:"read";b:1;s:7:"level_7";b:1;s:7:"level_6";b:1;s:7:"level_5";b:1;s:7:"level_4";b:1;s:7:"level_3";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:17:"edit_others_pages";b:1;s:20:"edit_published_pages";b:1;s:13:"publish_pages";b:1;s:12:"delete_pages";b:1;s:19:"delete_others_pages";b:1;s:22:"delete_published_pages";b:1;s:12:"delete_posts";b:1;s:19:"delete_others_posts";b:1;s:22:"delete_published_posts";b:1;s:20:"delete_private_posts";b:1;s:18:"edit_private_posts";b:1;s:18:"read_private_posts";b:1;s:20:"delete_private_pages";b:1;s:18:"edit_private_pages";b:1;s:18:"read_private_pages";b:1;}}s:6:"author";a:2:{s:4:"name";s:6:"Author";s:12:"capabilities";a:10:{s:12:"upload_files";b:1;s:10:"edit_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:4:"read";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:12:"delete_posts";b:1;s:22:"delete_published_posts";b:1;}}s:11:"contributor";a:2:{s:4:"name";s:11:"Contributor";s:12:"capabilities";a:5:{s:10:"edit_posts";b:1;s:4:"read";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:12:"delete_posts";b:1;}}s:10:"subscriber";a:2:{s:4:"name";s:10:"Subscriber";s:12:"capabilities";a:2:{s:4:"read";b:1;s:7:"level_0";b:1;}}}', 'yes'), (95, 'fresh_site', '0', 'yes'), (96, 'WPLANG', 'zh_CN', 'yes'), (97, 'widget_search', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'), (98, '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'), (99, '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'), (100, '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'), (101, 'widget_meta', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'), (102, 'sidebars_widgets', 'a:10:{s:19:"wp_inactive_widgets";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:16:"blog-widget-area";a:0:{}s:16:"post-widget-area";a:0:{}s:16:"page-widget-area";a:0:{}s:16:"shop-widget-area";a:0:{}s:16:"side-widget-area";a:0:{}s:18:"basket-widget-area";a:0:{}s:18:"header-widget-area";a:0:{}s:18:"footer-widget-area";a:0:{}s:13:"array_version";i:3;}', 'yes'), (103, 'widget_pages', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (104, 'widget_calendar', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (105, 'widget_media_audio', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (106, 'widget_media_image', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (107, 'widget_media_gallery', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (108, 'widget_media_video', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (109, 'widget_tag_cloud', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (110, 'widget_nav_menu', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (111, 'widget_custom_html', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (112, 'cron', 'a:6:{i:1556230856;a:2:{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:1556246815;a:1:{s:30:"wp_scheduled_auto_draft_delete";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:5:"daily";s:4:"args";a:0:{}s:8:"interval";i:86400;}}}i:1556274065;a:2:{s:19:"wp_scheduled_delete";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:5:"daily";s:4:"args";a:0:{}s:8:"interval";i:86400;}}s:25:"delete_expired_transients";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:5:"daily";s:4:"args";a:0:{}s:8:"interval";i:86400;}}}i:1558542056;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:1558563656;a:1:{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:7:"version";i:2;}', 'yes'), (113, 'theme_mods_twentynineteen', 'a:2:{s:18:"custom_css_post_id";i:-1;s:16:"sidebars_widgets";a:2:{s:4:"time";i:1554546152;s:4:"data";a:2:{s:19:"wp_inactive_widgets";a:0:{}s:9:"sidebar-1";a:6:{i:0;s:8:"search-2";i:1;s:14:"recent-posts-2";i:2;s:17:"recent-comments-2";i:3;s:10:"archives-2";i:4;s:12:"categories-2";i:5;s:6:"meta-2";}}}}', 'yes'), (126, 'can_compress_scripts', '1', 'no'), (143, 'auto_core_update_notified', 'a:4:{s:4:"type";s:7:"success";s:5:"email";s:17:"1656004343@qq.com";s:7:"version";s:5:"5.0.4";s:9:"timestamp";i:1554546078;}', 'no'), (149, 'current_theme', 'Rife Free', 'yes'), (150, 'theme_mods_rife-free', 'a:3:{i:0;b:0;s:18:"nav_menu_locations";a:1:{s:11:"header-menu";i:7;}s:18:"custom_css_post_id";i:-1;}', 'yes'), (151, 'theme_switched', '', 'yes'), (152, 'a13_rife-free_rating', '1554546153', 'yes'), (157, 'a13_force_to_flush', 'off', 'yes'), (158, 'recently_activated', 'a:0:{}', 'yes'), (159, 'a13_user_css_update', 'off', 'yes'), (160, 'widget_a13-shortcodes', 'a:1:{s:12:"_multiwidget";i:1;}', 'yes'), (165, 'widget_recent-works', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (166, 'widget_recent-albums', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (167, 'widget_popular-posts', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (168, 'widget_related-posts', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (169, 'widget_a13-social-icons', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (170, 'widget_filter', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (171, 'widget_contact-info', 'a:2:{i:1;a:0:{}s:12:"_multiwidget";i:1;}', 'yes'), (195, 'category_children', 'a:0:{}', 'yes'), (197, 'nav_menu_options', 'a:2:{i:0;b:0;s:8:"auto_add";a:0:{}}', 'yes'), (204, '_site_transient_update_core', 'O:8:"stdClass":4:{s:7:"updates";a:4:{i:0;O:8:"stdClass":10:{s:8:"response";s:7:"upgrade";s:8:"download";s:59:"https://downloads.wordpress.org/release/wordpress-5.2.1.zip";s:6:"locale";s:5:"en_US";s:8:"packages";O:8:"stdClass":5:{s:4:"full";s:59:"https://downloads.wordpress.org/release/wordpress-5.2.1.zip";s:10:"no_content";s:70:"https://downloads.wordpress.org/release/wordpress-5.2.1-no-content.zip";s:11:"new_bundled";s:71:"https://downloads.wordpress.org/release/wordpress-5.2.1-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:5:"5.2.1";s:7:"version";s:5:"5.2.1";s:11:"php_version";s:6:"5.6.20";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"5.0";s:15:"partial_version";s:0:"";}i:1;O:8:"stdClass":11:{s:8:"response";s:10:"autoupdate";s:8:"download";s:59:"https://downloads.wordpress.org/release/wordpress-5.2.1.zip";s:6:"locale";s:5:"en_US";s:8:"packages";O:8:"stdClass":5:{s:4:"full";s:59:"https://downloads.wordpress.org/release/wordpress-5.2.1.zip";s:10:"no_content";s:70:"https://downloads.wordpress.org/release/wordpress-5.2.1-no-content.zip";s:11:"new_bundled";s:71:"https://downloads.wordpress.org/release/wordpress-5.2.1-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:5:"5.2.1";s:7:"version";s:5:"5.2.1";s:11:"php_version";s:6:"5.6.20";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"5.0";s:15:"partial_version";s:0:"";s:9:"new_files";s:1:"1";}i:2;O:8:"stdClass":11:{s:8:"response";s:10:"autoupdate";s:8:"download";s:57:"https://downloads.wordpress.org/release/wordpress-5.2.zip";s:6:"locale";s:5:"en_US";s:8:"packages";O:8:"stdClass":5:{s:4:"full";s:57:"https://downloads.wordpress.org/release/wordpress-5.2.zip";s:10:"no_content";s:68:"https://downloads.wordpress.org/release/wordpress-5.2-no-content.zip";s:11:"new_bundled";s:69:"https://downloads.wordpress.org/release/wordpress-5.2-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:3:"5.2";s:7:"version";s:3:"5.2";s:11:"php_version";s:6:"5.6.20";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"5.0";s:15:"partial_version";s:0:"";s:9:"new_files";s:1:"1";}i:3;O:8:"stdClass":11:{s:8:"response";s:10:"autoupdate";s:8:"download";s:59:"https://downloads.wordpress.org/release/wordpress-5.1.1.zip";s:6:"locale";s:5:"en_US";s:8:"packages";O:8:"stdClass":5:{s:4:"full";s:59:"https://downloads.wordpress.org/release/wordpress-5.1.1.zip";s:10:"no_content";s:70:"https://downloads.wordpress.org/release/wordpress-5.1.1-no-content.zip";s:11:"new_bundled";s:71:"https://downloads.wordpress.org/release/wordpress-5.1.1-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:5:"5.1.1";s:7:"version";s:5:"5.1.1";s:11:"php_version";s:5:"5.2.4";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"5.0";s:15:"partial_version";s:0:"";s:9:"new_files";s:1:"1";}}s:12:"last_checked";i:1558539040;s:15:"version_checked";s:5:"5.0.4";s:12:"translations";a:0:{}}', 'no'), (249, '_site_transient_timeout_theme_roots', '1556194242', 'no'), (250, '_site_transient_theme_roots', 'a:4:{s:9:"rife-free";s:7:"/themes";s:14:"twentynineteen";s:7:"/themes";s:15:"twentyseventeen";s:7:"/themes";s:13:"twentysixteen";s:7:"/themes";}', 'no'), (251, '_site_transient_update_themes', 'O:8:"stdClass":4:{s:12:"last_checked";i:1556192447;s:7:"checked";a:4:{s:9:"rife-free";s:5:"2.3.7";s:14:"twentynineteen";s:3:"1.2";s:15:"twentyseventeen";s:3:"2.0";s:13:"twentysixteen";s:3:"1.8";}s:8:"response";a:4:{s:9:"rife-free";a:4:{s:5:"theme";s:9:"rife-free";s:11:"new_version";s:5:"2.3.8";s:3:"url";s:39:"https://wordpress.org/themes/rife-free/";s:7:"package";s:57:"https://downloads.wordpress.org/theme/rife-free.2.3.8.zip";}s:14:"twentynineteen";a:4:{s:5:"theme";s:14:"twentynineteen";s:11:"new_version";s:3:"1.3";s:3:"url";s:44:"https://wordpress.org/themes/twentynineteen/";s:7:"package";s:60:"https://downloads.wordpress.org/theme/twentynineteen.1.3.zip";}s:15:"twentyseventeen";a:4:{s:5:"theme";s:15:"twentyseventeen";s:11:"new_version";s:3:"2.1";s:3:"url";s:45:"https://wordpress.org/themes/twentyseventeen/";s:7:"package";s:61:"https://downloads.wordpress.org/theme/twentyseventeen.2.1.zip";}s:13:"twentysixteen";a:4:{s:5:"theme";s:13:"twentysixteen";s:11:"new_version";s:3:"1.9";s:3:"url";s:43:"https://wordpress.org/themes/twentysixteen/";s:7:"package";s:59:"https://downloads.wordpress.org/theme/twentysixteen.1.9.zip";}}s:12:"translations";a:0:{}}', 'no'), (252, '_site_transient_update_plugins', 'O:8:"stdClass":5:{s:12:"last_checked";i:1558539041;s:7:"checked";a:5:{s:19:"akismet/akismet.php";s:3:"4.1";s:63:"apollo13-framework-extensions/apollo13-framework-extensions.php";s:5:"1.6.3";s:33:"classic-editor/classic-editor.php";s:3:"1.4";s:9:"hello.php";s:5:"1.7.1";s:55:"rife-elementor-extensions/rife-elementor-extensions.php";s:5:"1.1.0";}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.1.1";s:3:"url";s:38:"https://wordpress.org/plugins/akismet/";s:7:"package";s:56:"https://downloads.wordpress.org/plugin/akismet.4.1.1.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:"5.1.1";s:12:"requires_php";b:0;s:13:"compatibility";O:8:"stdClass":0:{}}}s:12:"translations";a:0:{}s:9:"no_update";a:4:{s:63:"apollo13-framework-extensions/apollo13-framework-extensions.php";O:8:"stdClass":9:{s:2:"id";s:43:"w.org/plugins/apollo13-framework-extensions";s:4:"slug";s:29:"apollo13-framework-extensions";s:6:"plugin";s:63:"apollo13-framework-extensions/apollo13-framework-extensions.php";s:11:"new_version";s:5:"1.6.3";s:3:"url";s:60:"https://wordpress.org/plugins/apollo13-framework-extensions/";s:7:"package";s:72:"https://downloads.wordpress.org/plugin/apollo13-framework-extensions.zip";s:5:"icons";a:2:{s:2:"2x";s:82:"https://ps.w.org/apollo13-framework-extensions/assets/icon-256x256.png?rev=1854162";s:2:"1x";s:82:"https://ps.w.org/apollo13-framework-extensions/assets/icon-128x128.png?rev=1854162";}s:7:"banners";a:0:{}s:11:"banners_rtl";a:0:{}}s:33:"classic-editor/classic-editor.php";O:8:"stdClass":9:{s:2:"id";s:28:"w.org/plugins/classic-editor";s:4:"slug";s:14:"classic-editor";s:6:"plugin";s:33:"classic-editor/classic-editor.php";s:11:"new_version";s:3:"1.4";s:3:"url";s:45:"https://wordpress.org/plugins/classic-editor/";s:7:"package";s:61:"https://downloads.wordpress.org/plugin/classic-editor.1.4.zip";s:5:"icons";a:2:{s:2:"2x";s:67:"https://ps.w.org/classic-editor/assets/icon-256x256.png?rev=1998671";s:2:"1x";s:67:"https://ps.w.org/classic-editor/assets/icon-128x128.png?rev=1998671";}s:7:"banners";a:2:{s:2:"2x";s:70:"https://ps.w.org/classic-editor/assets/banner-1544x500.png?rev=1998671";s:2:"1x";s:69:"https://ps.w.org/classic-editor/assets/banner-772x250.png?rev=1998676";}s:11:"banners_rtl";a:0:{}}s:9:"hello.php";O:8:"stdClass":9:{s:2:"id";s:25:"w.org/plugins/hello-dolly";s:4:"slug";s:11:"hello-dolly";s:6:"plugin";s:9:"hello.php";s:11:"new_version";s: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:64:"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855";s:2:"1x";s:64:"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855";}s:7:"banners";a:1:{s:2:"1x";s:66:"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855";}s:11:"banners_rtl";a:0:{}}s:55:"rife-elementor-extensions/rife-elementor-extensions.php";O:8:"stdClass":9:{s:2:"id";s:39:"w.org/plugins/rife-elementor-extensions";s:4:"slug";s:25:"rife-elementor-extensions";s:6:"plugin";s:55:"rife-elementor-extensions/rife-elementor-extensions.php";s:11:"new_version";s:5:"1.1.0";s:3:"url";s:56:"https://wordpress.org/plugins/rife-elementor-extensions/";s:7:"package";s:68:"https://downloads.wordpress.org/plugin/rife-elementor-extensions.zip";s:5:"icons";a:2:{s:2:"2x";s:78:"https://ps.w.org/rife-elementor-extensions/assets/icon-256x256.jpg?rev=1916344";s:2:"1x";s:78:"https://ps.w.org/rife-elementor-extensions/assets/icon-128x128.jpg?rev=1916344";}s:7:"banners";a:2:{s:2:"2x";s:81:"https://ps.w.org/rife-elementor-extensions/assets/banner-1544x500.jpg?rev=1982742";s:2:"1x";s:80:"https://ps.w.org/rife-elementor-extensions/assets/banner-772x250.jpg?rev=1982742";}s:11:"banners_rtl";a:0:{}}}}', 'no'), (253, '_site_transient_timeout_browser_a15531ff5476d10a9d1fc1bc26fafc75', '1556797253', 'no'), (254, '_site_transient_browser_a15531ff5476d10a9d1fc1bc26fafc75', 'a:10:{s:4:"name";s:14:"Microsoft Edge";s:7:"version";s:8:"18.17763";s:8:"platform";s:7:"Windows";s:10:"update_url";s:0:"";s:7:"img_src";s:0:"";s:11:"img_src_ssl";s:0:"";s:15:"current_version";s:8:"15.15063";s:7:"upgrade";b:0;s:8:"insecure";b:0;s:6:"mobile";b:0;}', 'no'), (255, '_site_transient_timeout_community-events-d41d8cd98f00b204e9800998ecf8427e', '1556237639', 'no'), (256, '_site_transient_community-events-d41d8cd98f00b204e9800998ecf8427e', 'a:2:{s:8:"location";a:1:{s:2:"ip";b:0;}s:6:"events";a:0:{}}', 'no'), (257, '_transient_timeout_feed_7d1d7866a17d17cf5f79e1f075b87a31', '1556235662', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (258, '_transient_feed_7d1d7866a17d17cf5f79e1f075b87a31', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"China 简体中文";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:24:"https://cn.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:41:"官方 WordPress China 简体中文站点";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Dec 2014 08:15: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:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"zh-CN";s: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.2-beta3-45265";s:7:"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:63:"\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:5:{s:0:"";a:8:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:23:"WordPress 5.0“Bebo”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:41:"https://cn.wordpress.org/2018/12/10/bebo/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:49:"https://cn.wordpress.org/2018/12/10/bebo/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 09 Dec 2018 20:44:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:6:"发布";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://cn.wordpress.org/?p=1172";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:387:"WordPress 5.0简体中文版现已开放下载,或在您的WordPress仪表盘中升级。\n\n我们为编辑器做出了许多改进。我们全新的区块编辑器是为您在全站提供流畅的编辑体验的第一步。不管您是在建立您的第一个站点、翻新您的博客还是编写代码为业,您都将有更多的灵活性来决定如何展示您的站点内容。";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"enclosure";a:2:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"url";s:52:"https://s.w.org/images/core/5.0/videos/add-block.mp4";s:6:"length";s:7:"8086508";s:4:"type";s:9:"video/mp4";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"url";s:48:"https://s.w.org/images/core/5.0/videos/build.mp4";s:6:"length";s:7:"2623964";s:4:"type";s:9:"video/mp4";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Jimmy Xu";s: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:46040:"\n
WordPress 5.0简体中文版现已开放下载,或在您的WordPress仪表盘中升级。
\n\n\n\n\n\n\n\n我们为编辑器做出了许多改进。我们全新的区块编辑器是为您在全站提供流畅的编辑体验的第一步。不管您是在建立您的第一个站点、翻新您的博客还是编写代码为业,您都将有更多的灵活性来决定如何展示您的站点内容。
\n\n\n\n\n\n\n\n全新的区块编辑器不会让您的访客看到的内容发生变化。它能让您随时插入任何类型的多媒体,并随意重新排列。每部分内容都会在独立的区块之内,而区块会成为方便操作的独立包装。如果您更倾向于使用HTML和CSS,区块也不会阻住您的去路。WordPress希望为您简化流程,而不是简化结果。
\n\n\n\n\n\n\n\n我们已经为您准备了许多区块,我们的社群也每天都在为您带来更多。下面是一些能让您起步的区块:
\n\n\n\n全新的编辑体验能更一致地对待您的设计和内容。如果您在构建客户网站,您可以创建可重用区块。它可以让您的客户随时添加新内容,同时维持一致的观感。
\n\n\n\n\n\n\n\n向您介绍二〇一九,一份全新的默认主题来为您展示新编辑器的强大。
\n\n\n\n二〇一九包含了为5.0中预设的区块所设计的自定义样式。该主题在整个网站大量使用了编辑器样式,这样您在内容编辑器中看到的,就是您会在网站前端所看到的。
\n二〇一九包含了充足的空白,现代的无衬线标题和传统的衬线正文,从开箱即美丽。该主题使用了系统字体来加快载入速度,不再等待缓慢的网络!
\n二〇一九被设计用于许多使用场景。不管您是在运作图片博客、开展新业务还是支持一项慈善事业,二〇一九都有足够的灵活性来满足您的要求。
\n区块能让用户舒服地进行内容修改,同时也确保了内容结构不会被无心的代码编辑破坏。这能让开发者来控制输出,构建优雅且符合语义的标记,且让它们在编辑时更健壮而不易损坏。
\n使用多种多样的API和界面组件来轻松地创建包含直观控制的区块。使用这些组件不仅能加速开发工作,还能向所有用户提供更一致、更可用也更容易接近的界面。
\n新的区块范式为解决用户所需开辟了一条全新的探索和想象之路。通过统一的区块插入工作流,您的客户和用户能够更轻松地找到并使用适合各种内容的区块。开发者则可专注于愿景及改良编辑体验,而不用与难以使用的API战斗。
\n想继续使用熟悉的经典编辑器?我们会支持经典编辑器插件直到2021年。
\n\n\n\n传统编辑器插件会将WordPress编辑器和“编辑文章”页恢复为旧版,且能让您继续使用那些扩展了旧版编辑器功能、使用了旧式的meta box或其他依赖旧版编辑器的插件。要安装,请访问您的插件页面并点击“传统编辑器”旁的“现在安装”按钮。在安装完成后,点击“激活”即可!
\n\n\n\n对于使用辅助功能的用户:如果您在使用区块编辑器时遇到了可用性问题,我们推荐您继续使用传统编辑器。
\n\n\n\n \n\n\n\n这次发布向开创性的古巴爵士音乐家拜博·巴尔德斯致敬。
\n\n\n\n此次发布由Matt Mullenweg领头,及由Allan Cole、Anthony Burchell、Gary Pendergast、Josepha Haden Chomphosy、Laurel Fulford、Omar Reiss、Daniel Bachhuber、Matías Ventura、Miguel Fonseca、Tammie Lister、Matthew Riley MacPherson共同领头。他们得到了以下个人的帮助。这次发布包含了423人的贡献。在您喜欢的音乐服务中听听拜博·巴尔德斯,并看看下面这些个人资料吧:Aaron Jorbin、Abdul Wahab、Abdullah Ramzan、Abhijit Rakas、Adam Silverstein、afraithe、Ahmad Awais、ahmadawais、Airat Halitov、Ajit Bohra、Alain Schlesser、albertomedina、aldavigdis、Alex Sanford、Alexander Botteram、alexis、Alexis Lloyd、Amanda Rush、amedina、Andrés、Andrea Fercia、Andrea Middleton、Andrei Lupu、andreiglingeanu、Andrew Duthie、Andrew Munro、Andrew Nevins、Andrew Ozz、Andrew Roberts、Andrew Taylor、andrewserong、Andy Peatling、Angie Meeker、Anna Harrison、Anton Timmermans、ArnaudBan、Arshid、Arya Prakasa、Asad、Ashar Irfan、Asvin Balloo、Atanas Angelov、Bappi、bcolumbia、belcherj、Ben Lowery、Benjamin Eyzaguirre、Benjamin Zekavica、benlk、Bernhard Kau、Bernhard Reiter、betsela、Bhargav Mehta、Birgir Erlendsson (birgire)、Birgit Pauli-Haack、bobbingwide、boblinthorst、Boone Gorges、Brady Vercher、Brandon Kraft、Brandon Payton、Brent Swisher、Brianna Privett、briannaorg、Bronson Quick、Brooke.、Burhan Nasir、CantoThemes、cathibosco、Chetan Prajapati、chetansatasiya、chetansatasiya、Chouby、Chris Lloyd、Chris Runnells、Chris Van Patten、chriskmnds、Christian Sabo、Christoph Herr、Claudio Sanches、coderkevin、Copons、courtney0burton、Crisoforo Gaspar Hernandez、Csaba (LittleBigThings)、csabotta、Daniel James、Daniel Richards、danielhw、daniloercoli、DannyCooper、Darren Ethier (nerrad)、davemoran118、David Cavins、David Herrera、David Kennedy、David Ryan、David Sword、Davide ‘Folletto’ Casali、davidherrera、Davis、dciso、Dennis Snell、Derek Smart、designsimply、Devin Walker、Devio Digital、dfangstrom、Dhanendran、Diego de Oliveira、diegoreymendez、dingo-d、Dion Hulse、Dixita Dusara、Dixita Dusara Gohil、Dominik Schilling、Donna Peplinskie、Drew Jaynes、dsawardekar、dsifford、Duane Storey、Edwin Cromley、ehg、ElectricFeet、Elio Rivero、Elisabeth Pointal、Ella Iseulde Van Dorpe、elrae、enodekciw、ephoxjames、ephoxmogran、Eric Amundson、ericnmurphy、etoledom、Evan Mullins、fabiankaegy、fabs_pim、faishal、Felix Arntz、Florian Simeth、foobar4u、foreverpinetree、Frank Klein、fuyuko、Gabriel Maldonado、Garrett Hyder、Gary Jones、Gary Thayer、garyjones、Gennady Kovshenin、George Olaru、George Stephanis、georgeh、gnif、goldsounds、Grappler、Grzegorz Ziółkowski、Gustavo Bordoni、gwwar、Hardeep Asrani、hblackett、Helen Hou-Sandi、Hendrik Luehrsen、herbmiller、Herre Groen、Hugo Baeta、hypest、Ian Dunn、ianstewart、ibelanger、iCaleb、idpokute、Igor、imath、Imran Khalid、intronic、Ipstenu (Mika Epstein)、Irene Strikkers、Ismail El Korchi、israelshmueli、J.D. Grimes、J.D. Grimes、Jacob Peattie、jagnew、jahvi、James Nylen、jamestryon、jamiehalvorson、Jan Dembowski、janalwin、Jason Caldwell、Jason Stallings、Jason Yingling、Javier Villanueva、Jay Hoffmann、Jb Audras、Jeff Bowen、Jeffrey Paul、Jeremy Felt、Jip Moors、JJJ、Joe Bailey-Roberts、Joe Dolson、Joe Hoyle、Joe McGill、joemaller、Joen Asmussen、Johan Falk、John Blackbourn、John Godley、johndyer、JohnPixle、johnwatkins0、jomurgel、Jonathan Desrosiers、Jonny Harris、jonsurrell、Joost de Valk、Jorge Bernal、Jorge Costa、Jose Fremaint、Josh Pollock、Josh Visick、Joshua Wold、Joy、jrf、jryancard、jsnajdr、JulienMelissas、Justin Kopepasah、K.Adam White、Kallehauge、KalpShit Akabari、Kat Hagan、Kelly Dwan、Kevin Hoffman、khleomix、Kite、Kjell Reigstad、kluny、Konstantin Obenland、Konstantinos Xenos、krutidugade、Lance Willett、Lara Schenck、leahkoerper、lloyd、Loïc Blascos、Lucas Stark、LucasRolff、luigipulcini、Luke Cavanagh、Luke Kowalski、Luke Pettway、Luminus、lynneux、macbookandrew、Maedah Batool、Mahdi Yazdani、mahmoudsaeed、Maja Benke、Marcus Kazmierczak、Marin Atanasov、marina_wp、Marius L. J.、mariusvw、Mark Jaquith、Mark Uraine、Marko Andrijasevic、martinlugton、Marty Helmick、mathiu、Matt Cromwell、Matt Mullenweg、MattGeri、Matthew Boynes、Matthew Haines-Young、maurobringolf、Maxime BERNARD-JACQUET、Mayo Moriyama、meetjey、Mel Choyce、mendezcode、Micah Wood、Michael Adams (mdawaffe)、Michael Hull、Michael Nelson、Michele Mizejewski、Migrated to @jeffpaul、Miina Sikk、Mikael Korpela、Mike Crantea、Mike Haydon、Mike Schroder、mikehaydon、Mikey Arce、Milan Dinić、Milana Cap、Milen Petrinski – Gonzo、milesdelliott、mimo84、mirka、mmtr86、Monique Dubbelman、Morten Rand-Hendriksen、Mostafa Soufi、motleydev、mpheasant、mrmadhat、mrwweb、msdesign21、mtias、Muhammad Irfan、Mukesh Panchal、munirkamal、Muntasir Mahmud、mzorz、nagayama、Nahid F. Mohit、Naoko Takano、napy84、nateconley、Native Inside、Ned Zimmerman、Neil Murray、nic.bertino、Nicola Heald、Niels Lange、Nikhil Chavan、Nikolay Bachiyski、nitrajka、njpanderson、nshki、Okamoto Hidetaka、oskosk、Paresh Radadiya、Pascal Birchler、Paul Bearne、Paul Dechov、Paul Stonier、Paul Wilde、Pedro Mendonça、Peter Wilson、pglewis、Philipp Bammes、piersb、Pieter Daalder、pilou69、Piotr Delawski、poena、postphotos、potbot、Prateek Saxena、Pratik K. Yadav、Presskopp、psealock、ptasker、Rachel、Rachel Baker、Rahmohn、Rahmon、Rahul Prajapati、rakshans1、ramonopoly、Rastislav Lamos、revgeorge、Riad Benguella、Rian Rietveld、richsalvucci、Riddhi Mehta、rileybrook、Robert Anderson、Robert O’Rourke、robertsky、Rocio Valdivia、Rohit Motwani、Ross Wintle、Ryan McCue、Ryan Welcher、ryo511、Sagar Prajapati、Sami Keijonen、Samuel Wood (Otto)、Sang-Min Yoon、sarah semark、Scott Weaver、Sergey Biryukov、SergioEstevao、Shahjehan Ali、Shailee Sheth、Sharaz Shahid、Shaun sc、shaunandrews、Shawn Hooper、shenkj、sikander、Simon Prosser、siriokun、sirjonathan、sirreal、Sisanu、skorasaurus、Slushman、Sofia Sousa、SOMTIJDS、Soren Wrede、spocke、Stagger Lee、Stanimir Stoyanov、Stephen Edgar、Steve Henty、Store Locator Plus、strategio、stuartfeldt、tacrapo、talldan、Tammie Lister、ThemeRoots、Thorsten Frommen、Thrijith Thankachan、Tim Hengeveld、timgardner、Timmy Crawford、Timothy Jacobs、Tom J Nowell、Toni Laakso、Toni Viemerö、Tor-Bjorn Fjellner、Toro_Unit (Hiroshi Urabe)、Toshihiro Kanai、Towhidul Islam、Travis Lopes、truongwp、Tunji Ayoola、twoelevenjay、Ulrich、Vishal Kakadiya、Vitor Paladini、Walter Ebert、warmarks、WebMan Design | Oliver Juhas、websupporter、Weston Ruter、William Earnhardt、williampatton、Willy Bahuaud、wpscholar、Yahil Madakiya、yingles、Yoav Farhi、Yusuke Takahashi、zebulan和Ziyaddin Sadigov。
\n\n\n\n最后,让我们感谢为本次发布提供了翻译的贡献者。WordPress 5.0在发布时被翻译成了37种语言,还有更多在路上。
\n\n\n\n如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。
\n\n\n\n感谢您选择WordPress,我们希望您喜欢!
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:46:"https://cn.wordpress.org/2018/12/10/bebo/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:61:"\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:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:27:"WordPress 4.9.4维护更新";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:52:"https://cn.wordpress.org/2018/02/08/wordpress-4-9-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:60:"https://cn.wordpress.org/2018/02/08/wordpress-4-9-4/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 08 Feb 2018 05:02:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:6:"发布";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://cn.wordpress.org/?p=1092";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:30:"WordPress 4.9.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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Jimmy Xu";s: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:1395:"WordPress 4.9.4现已发布。
\n此维护性更新修正了4.9.3版中的一个严重问题。该问题会导致站点不能进行自动更新,并需要您(或您的主机提供商)进行操作来升级到4.9.4。
\n在四年前,我们在WordPress 3.7“Basie”中加入了WordPress的自动更新功能,来让您不用费力也能有一个安全且无漏洞的站点。在这四年中,该功能已经为数百万计的WordPress实例提供了自动更新,并极少出现问题。不幸的是,我们在昨天发布4.9.3版后,找出了其中存在的一个严重问题。该问题会导致WordPress在试图更新到4.9.4时遇到错误,并需要您通过WordPress仪表盘或主机更新工具来进行更新。
\n要获得关于此问题的技术详情,请查阅我们的核心开发博客。要查阅完整更新列表,请参见工单列表。
\n下载WordPress 4.9.4简体中文版或在仪表盘→更新中点击“现在更新”。
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:57:"https://cn.wordpress.org/2018/02/08/wordpress-4-9-4/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:61:"\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:5:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:25:"WordPress 4.9“Tipton”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:43:"https://cn.wordpress.org/2017/11/16/tipton/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:52:"https://cn.wordpress.org/2017/11/16/tipton/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Nov 2017 01:33:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:6:"发布";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://cn.wordpress.org/?p=1075";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:49:"WordPress 4.9简体中文版现已开放下载。";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Jimmy Xu";s: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:42194:"WordPress 4.9简体中文版现已开放下载,或在您的WordPress仪表盘中升级。我们将此版本命名为“Tipton”,以纪念爵士音乐家和乐队领唱比利·蒂普顿。WordPress 4.9的新功能能让您的设计工作流更顺滑,防止您的代码出现错误。
\n包括了设计草稿、锁、计划和预览链接等新功能,全新的定制器工作流为内容创作者提升了协作体验。此外,代码语法高亮和错误检查能让您的站点建设体验更整洁平滑。我们还为您带来了全新画廊小工具并改善了主题浏览和切换的体验。
\n就像您可以在撰写文章时打草稿并在您希望的日期和时间发布一样,您也可以对站点设计做同样的事。现在可以随您所好地调整并计划设计更新。
\n想要为您提议的站点设计修改取得反馈?WordPress 4.9向您提供了能发送给您的团队或客户的预览链接,让您能够取得并整合来自他人的反馈,并在计划的日期公开您的修改。我们能说协作++吗?
\n遇到过两名设计师同时修改一个项目,设计师A覆盖了设计师B的优美修改的事情吗?WordPress 4.9的设计锁功能与文章锁相似,在您进行设计修改时保护您,防止他人修改或抹除您的工作成果。
\n您在保存您的全新设计草稿前就离开了?别怕,当您回来时,WordPress 4.9会礼貌地问您是否想要保存这些未保存的修改。
\n您遇到了一个显示问题,但不能确定您所写的CSS到底出了什么问题。在CSS编辑和WordPress 4.8.1中引入的自定义HTML小工具有了语法高亮和错误检查后,您将能够快速找出代码错误。我们保证这项功能可以帮助您更轻松地扫描代码,并快速修复代码错误。
\n可怕的白色屏幕。现在WordPress 4.9在您要保存的主题或插件代码有错误时会提出警告,让您能够避免损坏整个站点,也让您晚上睡得更安心。
\n当您直接编辑主题和插件时,WordPress 4.9会礼貌地警告您这是一种很危险的做法,同时会建议您在保存前备份您的文件,这样您的修改就不会在下次更新时遭到覆盖。请走安全路线:未来的您会感谢您,您的团队和客户也会感谢您。
\n从WordPress 4.8的媒体变更延伸而来的渐进式改进,现在您可以通过小工具添加一个画廊了!
\n想要向您的文字小工具加入媒体?通过我们简单而有用的”添加媒体“按钮,在小工具中向您的文字旁边嵌入图像、视频和音频。喔!
\n在您切换主题时,有的时候小工具会自行移动位置。WordPress 4.9的改进在您更换主题时向您带来更可靠的菜单和挂件位置。此外,您可以预览已安装的主题,或正确地下载、安装并预览新主题。在部署之前,没有什么能够像预览一样方便的。
\n要为您的站点找一个新主题?现在,您可以在定制器中搜索、浏览并预览超过2600个主题,并可以直接应用到您的站点。此外,您也可以通过过滤主题、功能和布局来加速您的搜索。
\n您被创建新菜单的步骤搞糊涂了吗?现在不会了!我们向您带来了更顺滑的菜单创建用户体验。新的说明文字会指导您。
\nWordPress正致力于一种新的创建并控制您的内容的方式,我们需要您的帮助。想要成为早期测试者或投身于Gutenberg项目?在GitHub贡献。
\n(PS:这篇文章就是用Gutenberg写的!)
\n我们在WordPress 4.9中对定制器JS API进行了数项改进,消除了许多痛点,让它和PHP API一样易用。现在也有了新的基本控制模板、日期/时间控件和小节/页面/全局通知。查看完整列表。
\n我们向您介绍在核心中使用的全新的代码编辑库,CodeMirror。请用它来改进您插件中编辑代码的体验,如CSS或JavaScript编辑框。
\nWordPress包含了升级版的MediaElement.js,其中移除了对jQuery的依赖、增强了无障碍访问、有了现代化的界面并修正了许多问题。
\n新的能力让您能够更细致地管理插件和翻译文件。此外,多站点中的站点切换过程已被调整,让对可用的角色和能力的更新过程更可靠和连贯。
\n此次发布由Mel Choyce和Weston Ruter领头,并得到了以下个人的帮助。这次发布包含了443人的贡献,其中185人更是第一次贡献。在您喜欢的音乐服务中听听比利·蒂普顿,并看看下面这些个人资料吧:
\nAaron D. Campbell、Aaron Jorbin、abrightclearweb、Achal Jain、achbed、Acme Themes、Adam Silverstein、adammacias、Ahmad Awais、ahmadawais、airesvsg、ajoah、Aki Björklund、akshayvinchurkar、Alain Schlesser、Alex Concha、Alex Dimitrov、Alex Hon、alex27、allancole、Amanda Rush、Andrea Fercia、Andreas Panag、Andrew Nacin、Andrew Ozz、Andrey “Rarst” Savchenko、Andy Meerwaldt、Andy Mercer、Andy Skelton、Aniket Pant、Anil Basnet、Ankit K Gupta、Anthony Hortin、antisilent、Anton Timmermans、apokalyptik、artoliukkonen、Arunas Liuiza、attitude、backermann1978、Bappi、Ben Cole、Bernhard Gronau、Bernhard Kau、binarymoon、Birgir Erlendsson (birgire)、BjornW、bobbingwide、boblinthorst、boboudreau、bonger、Boone B. Gorges、Brady Vercher、Brainstorm Force、Brandon Kraft、Brian Hogg、Brian Krogsgard、Bronson Quick、Caroline Moore、Casey Driscoll、Caspie、Chandra Patel、Chaos Engine、cheeserolls、chesio、chetansatasiya、choong、Chouby、chredd、Chris Jean、Chris Marslender、Chris Smith、Chris Van Patten、Chris Wiegman、chriscct7、chriseverson、Christian Chung、Christian Nolen、Christian Wach、Christoph Herr、Clarion Technologies、Claudio Sanches、Claudio Sanches、ClaudioLaBarbera、codemovement.pk、coderkevin、codfish、coreymcollins、Curdin Krummenacher、Curtiss Grymala、Cătălin Dogaru、danhgilmore、Daniel Bachhuber 、Daniel Kanchev、Daniel Pietrasik、Daniele Scasciafratte、Daryl L. L. Houston (dllh)、Dave Pullig、Dave Romsey (goto10)、David A. Kennedy、David Chandra Purnama、David Herrera、David Lingren、David Mosterd、David Shanske、davidbhayes、Davide ‘Folletto’ Casali、deeptiboddapati、delphinus、deltafactory、Denis de Bernardy、Derek Herman、Derrick Hammer、Derrick Koo、dimchik、Dinesh Chouhan、Dion Hulse、dipeshkakadiya、dmsnell、Dominik Schilling、Dotan Cohen、Doug Wollison、doughamlin、DreamOn11、Drew Jaynes、duncanjbrown、dungengronovius、DylanAuty、Eddie Hurtig、Eduardo Reveles、Edwin Cromley、ElectricFeet、Elio Rivero、Ella Iseulde Van Dorpe、elyobo、enodekciw、enshrined、Eric Andrew Lewis、Eric Lanehart、Evan Herman、Felix Arntz、Fencer04、Florian Brinkmann、Florian TIAR、FolioVision、fomenkoandrey、Francesco Taurino、Frank Klein、Frankie Jarrett、Fred、Fredrik Forsmo、fuscata、Gabriel Maldonado、Garth Mortensen、Gary Jones、Gary Pendergast、Geeky Software、George Stephanis、Goran Šerić、Graham Armfield、Grant Derepas、Gregory Karpinsky (@tivnet)、Hardeep Asrani、Helen Hou-Sandí、Henry Wright、hiddenpearls、Hinaloe、Hristo Pandjarov、Hugo Baeta、Iain Poulson、Ian Dunn、Ian Edington、idealien、Ignacio Cruz Moreno、imath、implenton、Ionut Stanciu、Ipstenu (Mika Epstein)、ivdimova、J.D. Grimes、Jacob Peattie、Jake Spurlock、James Nylen、jamesacero、Japh、Jared Cobb、jayarjo、jdolan、jdoubleu、Jeff Bowen、Jeff Paul、Jeffrey de Wit、Jeremy Felt、Jeremy Pry、jimt、Jip Moors、jmusal、Joe Dolson、Joe Hoyle、Joe McGill、Joel James、johanmynhardt、John Blackbourn、John Dittmar、John James Jacoby、John P. Bloch、John Regan、johnpgreen、Jon (Kenshino)、Jonathan Bardo、Jonathan Brinley、Jonathan Daggerhart、Jonathan Desrosiers、Jonny Harris、jonnyauk、jordesign、JorritSchippers、Joseph Fusco、Josh Eaton、Josh Pollock、joshcummingsdesign、joshkadis、Joy、jrf、JRGould、Juanfra Aldasoro、Juhi Saxena、Junko Nukaga、Justin Busa、Justin Sainton、Justin Shreve、Justin Sternberg、K.Adam White、kacperszurek、Kailey (trepmal)、KalenJohnson、Kat Hagan、Keanan Koppenhaver、keesiemeijer、kellbot、Kelly Dwan、Kevin Hagerty、Kirk Wight、kitchin、Kite、kjbenk、Knut Sparhell、koenschipper、kokarn、Konstantin Kovshenin、Konstantin Obenland、Konstantinos Kouratoras、kuchenundkakao、kuldipem、Laurel Fulford、Lee Willis、Leo Baiano、LittleBigThings (Csaba)、Lucas Stark、Luke Cavanagh、Luke Gedeon、Luke Pettway、lyubomir_popov、Mário Valney、mageshp、Mahesh Waghmare、Mangesh Parte、Manish Songirkar、mantismamita、Marcel Bootsman、Marin Atanasov、Marius L. J.、Mariyan Belchev、Mark Jaquith、Mark Root-Wiley、Mark Uraine、Marko Heijnen、markshep、matrixik、Matt Banks、Matt King、Matt Mullenweg、Matt PeepSo、Matt van Andel、Matt Wiebe、Matthew Haines-Young、mattyrob、Max Cutler、Maxime Culea、Mayo Moriyama、mckernanin、mhowell、Michael Arestad、Michael Arestad、michalzuber、Miina Sikk、Mike Auteri、Mike Crantea、Mike Glendinning、Mike Hansen、Mike Little、Mike Schroder、Mike Viele、Milan Dinić、modemlooper、Mohammad Jangda、Mohan Dere、monikarao、morettigeorgiev、Morgan Estes、Morten Rand-Hendriksen、moto hachi ( mt8.biz )、mrbobbybryant、Naim Naimov、Nate Reist、NateWr、nathanrice、Nazgul、Ned Zimmerman、net、Nick Halsey 、Nicolas GUILLAUME、Nikhil Chavan、Nikhil Vimal、Nikolay Bachiyski、Nilambar Sharma、noplanman、nullvariable、odie2、odyssey、Okamoto Hidetaka、orvils、oskosk、Otto Kekäläinen、ovann86、Pantip Treerattanapitak (Nok)、Pascal Birchler、patilvikasj、Paul Bearne、Paul Wilde、Payton Swick、pdufour、Perdaan、Peter Wilson、phh、php、Piotr Delawski、pippinsplugins、pjgalbraith、pkevan、Pratik、Pressionate、Presskopp、procodewp、Rachel Baker、Rahul Prajapati、Ramanan、Rami Yushuvaev、ramiabraham、ranh、Red Sand Media Group、Riad Benguella、Rian Rietveld、Richard Tape、Robert D Payne、Robert Jolly、Robert Noakes、Rocco Aliberti、Rodrigo Primo、Rommel Castro、Ronald Araújo、Ross Wintle、Roy Sivan、Ryan Kienstra、Ryan McCue、Ryan Plas、Ryan Welcher、Sal Ferrarello、Sami Keijonen、Samir Shah、Samuel Sidler、Sandesh、Sang-Min Yoon、Sanket Parmar、Sarah Gooding、Sayed Taqui、schrapel、Scott Reilly、Scott Taylor、scrappy@hub.org、scribu、seancjones、Sebastian Pisula、Sergey Biryukov、Sergio De Falco、sfpt、shayanys、shazahm1、shprink、simonlampen、skippy、smerriman、snacking、solal、Soren Wrede、Stanimir Stoyanov、Stanko Metodiev、Steph、Steph Wells、Stephanie Leary、Stephen Edgar、Stephen Harris、Steven Word、stevenlinx、Sudar Muthu、Swapnil V. Patil、swapnild、szaqal21、Takahashi Fumiki、Takayuki Miyauchi、Tammie Lister、tapsboy、Taylor Lovett、team、tg29359、tharsheblows、the、themeshaper、thenbrent、thomaswm、Thorsten Frommen、tierra、Tim Nash、Timmy Crawford、Timothy Jacobs、timph、Tkama、tnegri、Tom Auger、Tom J Nowell、tomdxw、Toro_Unit (Hiroshi Urabe)、Torsten Landsiedel、transl8or、traversal、Travis Smith、Triet Minh、Trisha Salas、tristangemus、truongwp、tsl143、Ty Carlson、Ulrich、Utkarsh、Valeriu Tihai、Viljami Kuosmanen、Vishal Kakadiya、vortfu、Vrunda Kansara、webbgaraget、WebMan Design | Oliver Juhas、websupporter、Weston Ruter、William Earnhardt、williampatton、Wolly aka Paolo Valenti、WraithKenny、yale01、Yoav Farhi、Yoga Sukma、Zach Wills、Zack Tollman、Ze Fontainhas、zhildzik和zsusag。
\n最后,让我们感谢为本次发布提供了翻译的贡献者。WordPress 4.9被翻译成了43种语言,还有更多在路上。
\n您想发表关于WordPress 4.9的新闻吗?我们为您准备了媒体包,来告知您关于此次更新的新功能,我们也为您准备了一些媒体资源。
\n如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。
\n感谢您选择WordPress,我们希望您喜欢!
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:48:"https://cn.wordpress.org/2017/11/16/tipton/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:64:"\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:5:{s:0:"";a:8:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:26:"WordPress 4.7“Vaughan”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"https://cn.wordpress.org/2016/12/08/vaughan/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:53:"https://cn.wordpress.org/2016/12/08/vaughan/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 08 Dec 2016 05:09:23 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:6:"发布";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://cn.wordpress.org/?p=1040";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:49:"WordPress 4.7简体中文版现已开放下载。";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"enclosure";a:3:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"url";s:64:"https://wordpress.org/news/files/2016/12/starter-content.mp4?_=1";s:6:"length";s:7:"3736020";s:4:"type";s:9:"video/mp4";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"url";s:63:"https://wordpress.org/news/files/2016/12/edit-shortcuts.mp4?_=2";s:6:"length";s:7:"1127483";s:4:"type";s:9:"video/mp4";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:3:"url";s:62:"https://wordpress.org/news/files/2016/12/video-headers.mp4?_=3";s:6:"length";s:7:"1549803";s:4:"type";s:9:"video/mp4";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"Jimmy Xu";s: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:41950:"WordPress 4.7简体中文版现已开放下载,或在您的WordPress仪表盘中升级。我们将此版本命名为“Vaughan”,以纪念爵士歌手莎拉·沃恩。4.7的全新功能让您以您的想法来建立您的网站。
\n\n一个全新默认主题可让您的网站通过引人入胜的特色图片和影音页头生动呈现。
\n\n“二〇一七”专注于商业网站,提供了一个可自定义各部分的首页。使用挂件、导航、社交菜单、标志、自定颜色等来个性化。我们的2017年默认主题能支持更多语言、任何设备及广泛的用户群。
\nWordPress 4.7为外观编辑加入新功能,帮助您完成主题的初始设置,在一个不间断的工作流程中对所有修改进行非破坏性的实时预览。
\n网站的许多菜单包含链接指向您的网站其他页面,但当您还没有任何页面时该怎么办?现在,您可以在建立菜单时新增页面,而不必离开定制器并放弃修改。一旦您发布了自定选项,您就可以准备好在新的页面加入内容。\n
有时候您只需要一些视觉上的微调就能使您的网站更臻完美。WordPress 4.7允许您加入自定义CSS并能立即在网站看到变化。实时预览加快您的工作速度,且无须反复刷新网页。\n
在WordPress 4.7管理您的文件集变得更容易。上传PDF文件将会产生缩略图,因此您可以在所有文件中更轻易区分他们。\n
只是因为您的网站在单一语言设定下,但这不代表每一位协助管理网站的伙伴都使用该语言。新增更多语言至您的网站,让用户可以在他的个人资料页面选择不同语言。\n
WordPress 4.7为文章、评论、自定义字段、用户、元数据和设置带来了REST API节点。
\n\n内容节点让您的WordPress拥有机器可读的额外访问资源,具备清晰、标准导向接口,为网站与插件、主题和App开创一条平稳的前进之路。准备好开始开发了吗?查看REST API参考。
\n通过开启所有文章类型的页面模板功能,主题开发者可以有更弹性的WordPress模板结构。
\nWordPress 4.7为主题开发者带来新函数、钩子和行为。
\n批处理现在除了编辑和删除外加入更多功能。
\nWP_Hook
依靠动作和过滤器的代码已被大幅调整与改写,同时修正了一些错误。
\nregister_setting()已经强化,加入包含类型、描述及REST API能见度管理。
\n自定义变更集让定制器中的修改持久化,就像自动保存草稿一样。他们也让像起始内容一样的新功能成为可能。
\n此次发布由Helen Hou-Sandí领头,由Jeff Paul和Aaron Jorbin担任发布代表,并得到了以下个人的帮助。这次发布包含了482人的贡献,创下新高,其中205人更是第一次贡献。在您喜欢的音乐服务中听听莎拉·沃恩,并看看下面这些个人资料吧:
\nAaron D. Campbell、abrightclearweb、Achal Jain、achbed、Acme Themes、Adam Silverstein、adammacias、Ahmad Awais、ahmadawais、airesvsg、ajoah、Aki Björklund、AkshayVinchurkar、Alex Concha、Alex Dimitrov、Alex Hon、alex27、allancole、Amanda Rush、Andrea Fercia、Andreas Panag、Andrew Nacin、Andrew Ozz、Andrey “Rarst” Savchenko、Andy Meerwaldt、Andy Mercer、Andy Skelton、Aniket Pant、Anil Basnet、Ankit K Gupta、Anthony Hortin、antisilent、Anton Timmermans、Antti Kuosmanen、apokalyptik、artoliukkonen、Arunas Liuiza、attitude、backermann、Bappi、Ben Cole、Bernhard Kau、BinaryMoon、Birgir Erlendsson (birgire)、BjornW、bobbingwide、boblinthorst、boboudreau、bonger、Boone B. Gorges、Brady Vercher、Brainstorm Force、Brandon Kraft、Brian Hogg、Brian Krogsgard、Bronson Quick、Caroline Moore、Casey Driscoll、Caspie、Chaos Engine、cheeserolls、chesio、chetansatasiya、choong、Chouby、chredd、Chris Jean、Chris Marslender、Chris Smith、Chris Van Patten、Chris Wiegman、chriscct7、chriseverson、Christian Nolen、Christian Wach、Christoph Herr、Clarion Technologies、Claudio Sanches、Claudio Sanches、ClaudioLaBarbera、codemovement.pk、coderkevin、codfish、coreymcollins、Curdin Krummenacher、Curtiss Grymala、Cătălin Dogaru、danhgilmore、Daniel Bachhuber 、Daniel Kanchev、Daniele Scasciafratte、danielpietrasik、Daryl L. L. Houston (dllh)、Dave Pullig、Dave Romsey (goto10)、David A. Kennedy、David Chandra Purnama、David Herrera、David Lingren、David Mosterd、David Shanske、davidbhayes、Davide ‘Folletto’ Casali、deeptiboddapati、delphinus、deltafactory、Denis de Bernardy、Derek Herman、Derrick Hammer、Derrick Koo、dimchik、dineshc、Dion Hulse、dipeshkakadiya、dmsnell、Dominik Schilling、Dotan Cohen、Doug Wollison、doughamlin、Drew Jaynes、duncanjbrown、dungengronovius、DylanAuty、Eddie Hurtig、Eduardo Reveles、Edwin Cromley、ElectricFeet、Elio Rivero、Ella Iseulde Van Dorpe、elyobo、enodekciw、enshrined、Eric Andrew Lewis、Eric Lanehart、Evan Herman、Felix Arntz、Fencer04、Florian Brinkmann、Florian TIAR、FolioVision、fomenkoandrey、Frank Klein、Frankie Jarrett、frankiet、Fred、Fredrik Forsmo、fuscata、Gabriel Maldonado、Gary Jones、Gary Pendergast、Geeky Software、George Stephanis、Goran Šerić、Graham Armfield、Grant Derepas、greatislander、Gregory Karpinsky (@tivnet)、Hardeep Asrani、Henry Wright、hiddenpearls、Hinaloe、Hugo Baeta、Iain Poulson、iamjolly、Ian Dunn、ian.edington、idealien、Ignacio Cruz Moreno、imath、Imnok、implenton、Ionut Stanciu、Ipstenu (Mika Epstein)、Ivan、ivdimova、J.D. Grimes、Jacob Peattie、Jake Spurlock、James Nylen、jamesacero、Japh、Jared Cobb、jayarjo、jdolan、jdoubleu、Jeffrey de Wit、Jeremy Felt、Jeremy Pry、jimt、Jip Moors、jmusal、Joe Dolson、Joe Hoyle、Joe McGill、Joel James、johanmynhardt、John Blackbourn、John Dittmar、John James Jacoby、John P. Bloch、John Regan、johnpgreen、Jon (Kenshino)、Jonathan Bardo、Jonathan Brinley、Jonathan Daggerhart、Jonathan Desrosiers、Jonny Harris、jonnyauk、jordesign、JorritSchippers、Joseph Fusco、Josh Eaton、Josh Pollock、joshcummingsdesign、joshkadis、Joy、jrf、JRGould、Juanfra Aldasoro、Juhi Saxena、Junko Nukaga、Justin Busa、Justin Sainton、Justin Shreve、Justin Sternberg、K.Adam White、kacperszurek、Kailey (trepmal)、KalenJohnson、Kat Hagan、Keanan Koppenhaver、keesiemeijer、kellbot、Kelly Dwan、Ken Newman、Kevin Hagerty、Kirk Wight、kitchin、Kite、kjbenk、Knut Sparhell、koenschipper、kokarn、Konstantin Kovshenin、Konstantin Obenland、Konstantinos Kouratoras、kuchenundkakao、kuldipem、Laurel Fulford、Lee Willis、Leo Baiano、LittleBigThings (Csaba)、Lucas Stark、Luke Cavanagh、Luke Gedeon、lukepettway、lyubomir_popov、mageshp、Mahesh Waghmare、Mangesh Parte、Manish Songirkar、mantismamita、Marcel Bootsman、Marin Atanasov、Mario Valney、Marius L. J. (Clorith)、Mark Jaquith、Mark Root-Wiley、Mark Uraine、Marko Heijnen、markshep、matrixik、Matt Banks、Matt Jaworski、Matt King、Matt Mullenweg、Matt van Andel、Matt Wiebe、Matthew Haines-Young、mattyrob、Max Cutler、Maxime Culea、Mayo Moriyama、mbelchev、mckernanin、Mel Choyce、mhowell、Michael Arestad、Michael Arestad、michalzuber、Mike Auteri、Mike Crantea、Mike Glendinning、Mike Hansen、Mike Little、Mike Schroder、Mike Viele、Milan Dinić、modemlooper、Mohammad Jangda、Mohan Dere、monikarao、morettigeorgiev、Morgan Estes、Morten Rand-Hendriksen、moto hachi ( mt8.biz )、mrbobbybryant、Naim Naimov、NateWr、nathanrice、Nazgul、Nick Halsey 、Nicolas GUILLAUME、Nikhil Chavan、Nikhil Vimal、Nikolay Bachiyski、Nilambar Sharma、noplanman、nullvariable、odie2、odyssey、Okamoto Hidetaka、orvils、oskosk、Otto Kekäläinen、ovann86、Pascal Birchler、patilvikasj、Paul Bearne、Paul Wilde、Payton Swick、pdufour、Perdaan、Peter Wilson、phh、php、Piotr Delawski、pippinsplugins、pjgalbraith、pkevan、Pratik、Pressionate、Presskopp、procodewp、quasel、Rachel Baker、Rahul Prajapati、Ramanan、Rami Yushuvaev、ramiabraham、ranh、Red Sand Media Group、Rian Rietveld、Richard Tape、Robert D Payne、Robert Noakes、Rocco Aliberti、Rodrigo Primo、Rommel Castro、Ronald Araújo、Ross Wintle、Roy Sivan、Ryan Kienstra、Ryan McCue、Ryan Plas、Ryan Welcher、Sal Ferrarello、Sami Keijonen、Samir Shah、Samuel Sidler、Sandesh、Sang-Min Yoon、Sarah Gooding、Sayed Taqui、schlessera、schrapel、Scott Reilly、Scott Taylor、scrappy@hub.org、scribu、seancjones、Sebastian Pisula、Sergey Biryukov、Sergio De Falco、shayanys、shprink、simonlampen、skippy、smerriman、snacking、Soeren Wrede、solal、Stanimir Stoyanov、Stanko Metodiev、Steph、Steph Wells、Stephanie Leary、Stephen Edgar、Stephen Harris、Steven Word、stevenlinx、stubgo、Sudar Muthu、Swapnil V. Patil、Takahashi Fumiki、Takayuki Miyauchi、Tammie Lister、tapsboy、Taylor Lovett、team、tg29359、tharsheblows、the、themeshaper、thenbrent、thomaswm、Thorsten Frommen、tierra、Tim Nash、Timmy Crawford、Timothy Jacobs、Tkama、tnegri、Tom Auger、Tom J Nowell、tomdxw、Toro_Unit (Hiroshi Urabe)、Torsten Landsiedel、transl8or、traversal、Travis Smith、Triet Minh、Trisha Salas、tristangemus、Truong Giang、tsl143、Ty Carlson、Ulrich、Utkarsh、Valeriu Tihai、Vishal Kakadiya、voldemortensen、Vrunda Kansara、webbgaraget、WebMan Design | Oliver Juhas、websupporter、Weston Ruter、William Earnhardt、williampatton、Wolly aka Paolo Valenti、yale01、Yoav Farhi、Yoga Sukma、youknowriad、Zach Wills、Zack Tollman、Ze Fontainhas、zhildzik和zsusag。
\n特别感谢Rami Abraham制作发布视频。
\n最后,让我们感谢为本次发布提供了翻译的贡献者。WordPress 4.7被翻译成了52种语言,这次的发布视频也被翻译成了44种语言!
\n如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。感谢您选择WordPress,我们希望您喜欢!
\nWordPress 4.5简体中文版现已开放下载,或在您的WordPress仪表盘中升级。我们将此版本命名为“Coleman”,以纪念爵士萨克斯手科尔曼·霍金斯。4.5的全新功能协助您精简工作流程,无论您要写作还是建构网站。
\n\n通过降低分心的编写界面,轻易地链接内容,让您更专注在您的写作上。
\n\n您喜欢在编写列表和标题时使用格式捷径吗?伴随着水平线和<code>
现在它们变得更好用了。
确保您的站点在所有设备屏幕上都能完美呈现!在定制器中直接预览手机、平板及桌面的版面。
\n\n“二〇一五”及“二〇一六”主题已经更新,现已支持自定标志,您可以在定制器的“站点识别”一节找到,
\n生成图片的速度现在提升了50%且无损品质。这真的非常酷。
\n定制器现在支持全方位框架来渲染各部分的预览,无须使用JavaScript重写您的PHP代码。
\n更好地支持了脚本头/尾的依赖关系。新的wp_add_inline_script()
可以针对已注册的脚本加入额外的代码。
嵌入模板已分离为不同部分,并且可以通过模板层级直接由主题进行覆盖。
\njQuery 1.12.3、jQuery Migrate 1.4.0、Backbone 1.2.3和Underscore 1.8.3现已收录。
\n此次发布由Mike Schroder领头,由Adam Silverstein担任发布代表,Mel Choyce担任发布设计主管,并得到了以下个人的帮助。这次发布包含了298人的贡献。在您喜欢的音乐服务中听听科尔曼·霍金斯,并看看下面这些个人资料吧:
\n@mercime、Aaron D. Campbell、Aaron Edwards、Aaron Hockley、Aaron Jorbin、Abiral Neupane、Ahmad Awais、aidanlane、Alice Brosey、Amanda Rush、Andrea Fercia、Andrea Gandino、Andrew Nacin、Andrew Ozz、Andrew Rockwell、Andy、Ankit K Gupta、Anton Timmermans、apaliku、Aram Zucker-Scharff、ash.matadeen、Ashok Kumar Nath、BandonRandon、Barry Ceelen、Ben Dunkle、berengerzyla、Bernhard Riedl、Bhushan S. Jawle、Birgir Erlendsson (birgire)、Boone B. Gorges、Brad Williams、Brady Vercher、Brandon Allen、Brandon Hubbard、Brandon Kraft、Brian Krogsgard、Bruno Borges、Callum Macdonald、Cami Kaos、Chandra Patel、Charles Fulton、Chetan Chauhan、Chouby、ChriCo、Chris Christoff、Chris Mok、Christoph Herr、ckoerner、Claudio Sanches、Compute、coreymcollins、d4z_c0nf、Daisuke Takahashi、danhgilmore、Daniel Bachhuber、Daniel Bailey、Daniel Jalkut (Red Sweater)、Daniel Llewellyn、Daniele Scasciafratte、danielpataki、Danny van Kooten、Dave Clements、David A. Kennedy、David Brumbaugh、David Herrera、David Newton、David Shanske、Davide ‘Folletto’ Casali、Denis de Bernardy、Dennis Ploetner、Derek Herman、Dion Hulse、dmsnell、Dominik Schilling、Dossy Shiobara、Dotan Cohen、Dreb Bits、Drew Jaynes、duaneblake、Dzikri Aziz、Elio Rivero、Ella Iseulde Van Dorpe、Emerson Maningo、enej、Eric Andrew Lewis、Eric Binnion、Eric Daams、Erick Hitter、Evan Herman、Fabien Quatravaux、faishal、fantasyworld、Felix Arntz、finnj、firebird75、Fredrik Forsmo、fusillicode、Gary Jones、Gary Pendergast、gblsm、George Stephanis、Giuseppe Mamone、Giustino Borzacchiello、Grant Palin、groovecoder、Guido Scialfa、Gustavo Bordoni、hakre、Helen Hou-Sandí、Henry Wright、Hinaloe、Hugh Lashbrooke、Hugo Baeta、Iain Poulson、Ignacio Cruz Moreno、imath、Ionut Staicu、Ivan Kristianto、J.D. Grimes、jadpm、James DiGioia、Jason、Jasper de Groot、Jeffrey de Wit、Jeffrey Schutzman、Jennifer M. Dodd、Jeremy Felt、Jeremy Herve、Jeremy Pry、Jesin A、Jess G.、Joan Boluda、Joe Hoyle、Joe McGill、joelerr、John Blackbourn、John James Jacoby、JohnnyPea、Jonathan Brinley、Jonny Harris、Jory Hogeveen、Joseph Fusco、Josh Levinson、Josh Pollock、jrchamp、jrf、Juanfra Aldasoro、Juhi Saxena、Julio Potier、katieburch、Kelly Dwan、Kevin Hagerty、Kiran Potphode、Kirk Wight、Kite、kjbenk、Konstantin Kovshenin、Konstantin Obenland、Konstantinos Kouratoras、KrissieV、Lance Willett、leemon、Lew Ayotte、Liam Dempsey、Luan Ramos、luciole135、Lukas Pawlik、Lutz Schröer、madvic、Marco Chiesi、Marin Atanasov、Mario Peshev、Mark Barnes、Mark Jaquith、Mark Uraine、Marko Heijnen、Martin Burke、Matt Felten、Matt Mullenweg、Matt Wiebe、MattGeri、Matthew Ell、maweder、Mayo Moriyama、mcapybara、Mehul Kaklotar、Meitar、mensmaximus、Michael Arestad、michalzuber、micropat、Mika Epstein、Mike Glendinning、Mike Hansen、Mike Jolley、Milan Dinić、Morgan Estes、moto hachi ( mt8.biz )、Mr Papa、mwidmann、nexurium、Niall Kennedy、Nic Ford、Nick Halsey 、Nilambar Sharma、Ninos、oaron、overclokk、Pascal Birchler、Pat O’Brien、Paul Bearne、Paul de Wouters、Payton Swick、Perez Labs、Pete Nelson、Peter Wilson、petermolnar、Petter Walbø Johnsgård、Pieter、Pippin Williamson、Pirate Dunbar、prettyboymp、Profforg、programmin、Rachel Baker、rahal.aboulfeth、Rami Yushuvaev、Rastislav Lamos、Ricky Lee Whittemore、Ritesh Patel、rob、Roger Chen、RomSocial、Ruud Laan、Ryan Boren、Ryan Kienstra、Ryan McCue、Ryan Welcher、Sagar Jadhav、Sal Ferrarello、salvoaranzulla、Sam Hotchkiss、Sara Rosso、Scott Arciszewski、Scott Kingsley Clark、Scott Reilly、Scott Taylor、scottbrownconsulting、scribu、Sebastian Pisula、Sergej Müller、Sergey Biryukov、Shane、Shinichi Nishikawa、sidati、Siobhan、sky、slushman、smerriman、stephanethomas、Stephen Edgar、Stephen Harris、Steve Grunwell、Steven Word、Store Locator Plus、Subharanjan、Sudar Muthu、Sumit Singh、Taco Verdonschot、tahteche、Takashi Irie、Takayuki Miyoshi、Tammie Lister、tharsheblows、theMikeD、thomaswm、Timothy Jacobs、timplunkett、tmuikku、Toni Viemerö、Toro_Unit (Hiroshi Urabe)、Tracy Levesque、Tran Ngoc Tuan Anh、Travis Smith、Ty Carlson、Ulrich、Utkarsh、vhomenko、virgodesign、vlad.olaru、voldemortensen、vtieu、webaware、Wesley Elfring、Weston Ruter、WisdmLabs、WP Delighter、xavortm、yetAnotherDaniel和zinigor。
\n特别感谢Siobhan McKeown制作发布视频,及Jack Lenox的配音。
\n最后,让我们感谢为本次发布提供了翻译的贡献者。WordPress 4.5被翻译成了44种语言,这次的发布视频也被翻译成了32种语言!
\n如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。感谢您选择WordPress,我们4.6见!
\nWordPress 4.4简体中文版现已开放下载,或在您的WordPress仪表盘中升级。我们将此版本命名为“Clifford”,以纪念爵士小号手克利福德·布朗。4.4让您的网站更具连接性且反应敏捷。Clifford也带来了全新的默认主题,二〇一六。
\n我们最新的默认主题,二〇一六,是一个具现代感又不失经典博客设计风格的主题。
\n二〇一六在任何设备上都看起来很棒。一个流动式网格设计、灵活页首,搭配各式趣味的配色,让你的内容大放异彩。
\nWordPress现在以更聪明的方式显示适合任何设备的图片尺寸,确保每次皆完美呈现。您甚至不需要修改您的主题,
\n\n\n
现在您可以将文章嵌入到其他WordPress网站。只要将文章URL贴入编辑器,即可看到即时嵌入预览,完整的标题、摘要及特色图片(如果您有设定),甚至会包含您的网站图标以及评论与分享链接。
\n除了文章嵌入外,WordPress 4.4还加入五个新的oEmbed提供者:Cloudup、Reddit留言、ReverbNation、Speaker Deck及VideoPress。
\nREST API基础设施已整合于WordPress的核心中,将开发模式带入一个崭新的纪元。REST API为开发者提供在WordPress之上建设并扩展RESTful API的道路。
\n基础设施是REST API多阶段推出的第一部分,而将会在未来的发布中包含核心节点。要了解更多关于核心节点或是扩展REST API的信息,请查阅官方WordPress REST API扩展。
\n项目现在像文章一样支持元数据。请参阅add_term_meta()
、get_term_meta()
和update_term_meta()
来获得更多信息。
评论查询现在有缓存机制来改善性能。全新WP_Comment_Query
参数能更轻松地调用、访问评论。
新的WP_Term
、WP_Comment
和WP_Network
对象让与项目、评论和网络的交互变得更直观、更可预测。
此次发布由Scott Taylor领头,并得到了以下个人的帮助。这次发布包含了471人的贡献(创下新高!)。在您喜欢的音乐服务中听听克利福德·布朗,并看看下面这些个人资料吧:
\n@mercime、_smartik_、A5hleyRich、Aaron D. Campbell、Aaron Jorbin、Aaron Rutley、Adam Harley (Kawauso)、Adam Silverstein、adamholisky、aduth、Ahmad Awais、Aki Bjorklund、AlbertoCT、Alex Kirk、Alex Mills (Viper007Bond)、Alex Shiels、Alexander Gounder、alireza1375、Amanda Giles、amereservant、Amy Hendrix (sabreuse)、Andrea Fercia、Andrew Nacin、Andrew Norcross、Andrew Ozz、Andy Fragen、Angelo Mandato、Ankit Gade、Ankit K Gupta、Anthony Burchell、ap.koponen、apokalyptik、Athsear’J.S.、atomicjack、Austin Ginder、Austin Matzko、Barry Ceelen、Barry Kooij、bcworkz、BdN3504、Bego Mario Garde、Ben May、Benjamin Pick、Bernhard Riedl、bigdawggi、bilalcoder、BinaryKitten、Birgir Erlendsson (birgire)、Bjorn Johansen、bobbingwide、bonger、Boone B. Gorges、Brad Touesnard、bradparbs、Brady Vercher、Brandon Kraft、bravokeyl、brentvr、brettz95、Bruno Kos、Cam、Cami Kaos、carolinegeven、Casey Bisson、Catalin Dogaru、ch1902、chacha102、Chandra M、Chase Wiseman、Chiara Dossena、Chip Bennett、Chirag Swadia、Chris Christoff、Chris Kindred、Chris Klosowski、chriscoyier、Chrisdc1、christianoliff、Christoph Herr、Christopher Finke、cjhaas、codeelite、Coen Jacobs、Compute、Courtney Ivey、Craig Ralston、Curtiss Grymala、Daisuke Takahashi、Dan Boulet、Daniel Bachhuber、Daniel Koskinen、Daniel Menard、Daniele Scasciafratte、daniellandau、daniloercoli、Danny de Haan、Darren Ethier (nerrad)、Daryl L. L. Houston (dllh)、Datta Parad、Dave McHale、David A. Kennedy、David Anderson、David Herrera、David Shanske、david.binda、DeBAAT、Denis de Bernardy、Dennis Ploetner、Derek Herman、Devin Price、Dezzy、Dion Hulse、Dipali Dhole、dipesh.kakadiya、Dominik Bruderer、Dominik Schilling、Dreb Bits、Drew Jaynes、dustinbolton、Dzikri Aziz、edirect24、Eduardo Reveles、Eduardo Zulian、Edward Caissie、Egill R. Erlendsson、egower、Ehsaan、ehtis、Ella Iseulde Van Dorpe、Ellie Strejlau、Elliott Stocks、elusiveunit、enshrined、Eric Andrew Lewis、Eric Binnion、Eric Daams、Eric Mann、ericjuden、Evan Herman、F4rkie、Felix Arntz、Firdaus Zahari、fonglh、francoisb、Frank Klein、Frankie Jarrett、Fredrik Forsmo、Gaelan Lloyd、Gagan Deep Singh、Gary Cao、Gary Jones、Gary Pendergast、garza、Gaurav Pareek、Gautam Gupta、geminorum、Gerhard Potgieter、geza.miklo、Gijs Jorissen、Giuseppe Mamone、Giustino Borzacchiello、gnaka08、gradyetc、Greg Rickaby、Gregory Karpinsky (@tivnet)、Gustavo Bordoni、Gustavo Bordoni、gwinh.lopez、hakre、hauvong、Helen Hou-Sandí、Hinaloe、Hrishikesh Vaipurkar、Hugh Lashbrooke、Hugo Baeta、Iain Poulson、Ian Dunn、Ian Stewart、icetee、Ignacio Cruz Moreno、Ihor Vorotnov、imath、ippetkov、J.D. Grimes、jakub.tyrcha、James Huff、janhenckens、Japh、Jasper de Groot、jazbek、jcroucher、Jeff Farthing、Jeff Stieler、JeffMatson、Jeffrey de Wit、jeichorn、Jeremy Felt、Jeremy Pry、Jeroen Schmit、Jesin A、Jesper van Engelen、jim912、jliman、jmayhak、jnylen0、Jobst Schmalenbach、Joe Dolson、Joe Hoyle、Joe McGill、joehills、John Blackbourn、John James Jacoby、John P. Bloch、John Parris、Jon Cave、Jonathan Bardo、Jonathan Desrosiers、Joost de Valk、Jorge Bernal、Josh Betz、Josh Eaton、Josh Pollock、jrf、Juhi Saxena、Julio Potier、justdaiv、Justin Sainton、Justin Shreve、Justin Sternberg、Justin Tadlock、K.Adam White、Kailey (trepmal)、KalenJohnson、karinedo、karpstrucking、Kelly Dwan、Kevin Behrens、Kevin Langley、kevinatelement、kitchin、Kite、Konstantin Kovshenin、Konstantin Obenland、kraftner、Krzysiek Drozdz、Kurt Payne、laceous、Lance Willett、Laurens Offereins、lcherpit、ldinclaux、Lee Willis、leemon、lessbloat、linuxologos、Lucas Karpiuk、lucatume、luciole135、lucymtc、Luke Carbis、madalin.ungureanu、Mako、manolis09、Marcin Pietrzak、Marin Atanasov、Mario Peshev、Marius (Clorith)、Mark Jaquith、Marko Heijnen、Markus、Mat Marquis、Matheus Martins、Matt Bagwell、Matt Gibbs、Matt Martz、Matt Mullenweg、Matt van Andel、Matthew Boynes、Matthew Haines-Young、mazurstas、mbrandys、mdmcginn、mehulkaklotar、Mel Choyce、meloniq、micahmills、micahwave、Michael Adams (mdawaffe)、Michael Arestad、Michael Cain、Michiel Habraken、Mickey Kay、Mike Glendinning、Mike Hansen、Mike Jolley、Mike Jordan、Mike Schinkel、Mike Schroder、Milan Dinic、mismith227、misterunknown、mitcho (Michael Yoshitaka Erlewine)、Monika、Morgan Estes、Morten Rand-Hendriksen、moto hachi ( mt8.biz )、Mr Papa、mrmist、mulvane、neoscrib、NExT-Season、Niall Kennedy、nicholas_io、Nick Ciske、Nick Halsey、NickDuncan、Nicolas Juen、nikeo、Nikhil Chavan、Niklas、Nikola Nikolov、Nikolay Bachiyski、Nilambar Sharma、OriginalEXE、Paresh Radadiya、Pascal Birchler、Pat O’Brien、Paul Bearne、Paul de Wouters、Paul Ryan、Paul Wilde、pavelevap、Payton Swick、Peter Wilson、Petter Walbo Johnsgard、Petya Raykovska、pfefferle、Philip Arthur Moore、PhilipLakin、Philipp Cordes、Piotr Delawski、Piotr Soluch、Pippin Williamson、Prasad Nevase、Prasath Nadarajah、Pratik、Rachel Baker、rajnikmit、Rakesh Lawaju (Racase Lawaju)、ramay、Rami Yushuvaev、Raul Illana、renoirb、rhubbardreverb、Rhys Wynne、Rian Rietveld、Richard Tape、Robert Chapin、Rodrigo Primo、Rommel Castro、Ron Rennick、Ronald Huereca、Russell Heimlich、Ruud Laan、Ryan Kienstra、Ryan Markel、Ryan McCue、Ryan Welcher、Safirul Alredha、Sal Ferrarello、Sam Brodie、sam2kb、Samir Shah、Samuel Sidler、Samuel Wood (Otto)、Sanket Parmar、Sara Rosso、sarciszewski、Scott Grant、Scott Kingsley Clark、Scott Reilly、ScreenfeedFr、scribu、Sean Davis、Sean Hayes、Sebastian Pisula、Sergey Biryukov、serpent7776、several27、shimakyohsuke、side777、Simon Prosser、Simon Wheatley、Siobhan、sirzooro、sjmur、smerriman、Spacedmonkey、Stanislav Khromov、Stanko Metodiev、stebbiv、Stefan Froehlich、Stephane Boisvert、Stephanie Leary、Stephen Edgar、Stephen Harris、Steve Grunwell、stevehenty、SteveHoneyNZ、Steven Word、Store Locator Plus、Sudar Muthu、Sujay、Sumit Singh、summerblue、Sunny Ratilal、Takashi Irie、Takayuki Miyauchi、Tammie Lister、Tanner Moushey、tbcorr、Terry Chay、tharsheblows、theMikeD、thomaswm、Thorsten Frommen、Thorsten Ott、tigertech、Till Kruss、Tim Evko、tmatsuur、tmeister、TobiasBg、Tom Willmot、TomHarrigan、tommarshall、tomsommer、Toni Viemero、Toro_Unit (Hiroshi Urabe)、Tracy (LilJimmi) Levesque、Tran Ngoc Tuan Anh、Travis Smith、trenzterra、Tryon Eggleston、tszming、ty、Ty Carlson、Ulrich、Ulrich Sossou、Umesh Kumar、Umesh Nevase、Utkarsh、vilkatis、voldemortensen、Walter Ebert、walterbarcelos、webdevmattcrom、WEN Solutions、WEN Themes、Weston Ruter、wmertens、Wojtek Szkutnik、WP Plugin Dev dot com、wpdev101、wpseek、wturrell、Yam Chhetri、Yoav Farhi、Zach Wills、Zack Rothauser和Zack Tollman。
\n特别感谢Siobhan McKeown与Sara Rosso制作发布视频,及Cami Kaos的配音。
\n最后,让我们感谢为发布视频制作了字幕的贡献者,这次的发布视频被翻译成了23种语言!
\n如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。感谢您选择WordPress,我们4.5见!
\n建立您的菜单,更新,然后指定至适当位置,同时还能在定制器里即时预览。流线式定制器设计提供对手机友好且更方便的介面。随着每个版本发布,它将变得更快、更好用。
\n*
和#
看起来更加美好。\n
\n在浏览器标签、收藏夹和移动设备主画面以站点图标作为您的站点代表。在定制器里新增您独一无二的站点图标;当您切换主题时仍保持不变。使您的站点呈现出自己的品牌。
\n借助WordPress改进的密码设定功能使网站更安全。不再使用电子邮件接收密码,而是取得一个密码重设链接。当您在网站新增用户或编辑用户资料时,WordPress将会自动产生一个安全密码。
\n此次发布由Konstantin Obenland领头,并得到了以下个人的帮助。这次发布包含了246人的贡献。在您喜欢的音乐服务中听听比莉·荷莉戴,并看看下面这些个人资料吧:
@mercime、Aaron D. Campbell、Aaron Jorbin、Adam Heckler、Adam Silverstein、Aki Bjorklund、Alex Kirk、Alex Mills (Viper007Bond)、Alex Shiels、Alin Marcu、andfinally、Andrea Fercia、Andrea Gandino、Andrew Nacin、Andrew Ozz、Andy Fragen、Ankit K Gupta、Anthony Burchell、anubisthejackle、Aram Zucker-Scharff、Arjun S Kumar、avnarun、Bad Feather、Ben Cole、Ben Dunkle、BinaryKitten、Birgir Erlendsson (birgire)、Bjorn Johansen、bolo1988、Boone B. Gorges、Brad Touesnard、Bram Duvigneau、Brandon Kraft、Brian Krogsgard、Brian Layman、Caleb Burks、CalEvans、Chase Wiseman、Chip Bennett、Chouby、Chris Olbekson、chriscct7、Clement Biron、Craig Ralston、Daniel Bachhuber、Daniel Jalkut (Red Sweater)、Daniele Mte90 Scasciafratte、daniluk4000、Dave McHale、DaveAl、David A. Kennedy、David Herrera、daxelrod、Denis de Bernardy、Dennis Ploetner、Derek Herman、Dion Hulse、dipesh.kakadiya、dmsnell、Dominik Schilling、Drew Jaynes、Dzikri Aziz、eclev91、eligijus、Elio Rivero、Ella Iseulde Van Dorpe、Eric Andrew Lewis、Eric Binnion、Eric Mann、Fabien Quatravaux、Felix Arntz、francoeurdavid、Frank Klein、gabrielperezs、Garth Mortensen、Gary Jones、Gary Pendergast、George Stephanis、glennm、gtuk、hailin、hauvong、Helen Hou-Sandí、henrikakselsen、Hinaloe、Hrishikesh Vaipurkar、Hugo Baeta、Iain Poulson、imath、Ipstenu (Mika Epstein)、isaacchapman、izem、J.D. Grimes、Jack Lenox、jadpm、jamesgol、jancbeck、Jeff Farthing、Jeremy Felt、Jeremy Pry、Jeremy Ward、Jesin A、jipmoors、Joe Dolson、Joe Hoyle、Joe McGill、Joey Kudish、John Blackbourn、John James Jacoby、John Leschinski、Joost de Valk、Jpyper、jrf、Julio Potier、Justin Sternberg、Kai、karinchristen、karpstrucking、Kelly Dwan、Kevin Koehler、kitchin、Kite、Konstantin Kovshenin、Lance Willett、Lee Willis、Leo Gopal、loushou、Lumaraf、Marin Atanasov、Mario Peshev、Marius (Clorith)、Mark Jaquith、Marko Heijnen、marsjaninzmarsa、martinsachse、Matt Mullenweg、Matt van Andel、Matt Wiebe、mattyrob、maxxsnake、Mel Choyce、Michael、Michael Adams (mdawaffe)、Michael Arestad、michaelryanmcneill、Mickey Kay、mihai、Mike Hansen、Mike Nelson、Mike Schroder、Milan Dinic、Morgan Estes、mrutz、nabil_kadimi、Naoko Takano、Nazmul Hossain Nihal、nicholas_io、Nick Halsey、Nick Momrik、Nikolay Bachiyski、Nilambar Sharma、Onni Hakala、Ozh、Paresh Radadiya、Pascal Birchler、Paul Gibbs、Paul Wilde、pavelevap、Pete Nelson、Peter Wilson、PeterRKnight、Philip Arthur Moore、Pippin Williamson、pragunbhutani、Rachel Baker、Rami Yushuvaev、rarylson、Rastislav Lamos、rauchg、Ravinder Kumar、RC Lations、Reuben Gunday、Rian Rietveld、Ritesh Patel、Robert Chapin、Robert Dall、Rodrigo Primo、Rommel Castro、Ross Wintle、Rouven Hurling、Ryan Boren、Ryan Marks、Ryan McCue、Ryan Neudorf、Ryan Welcher、Sagar Jadhav、Sal Ferrarello、Samir Shah、santagada、Scott Kingsley Clark、Scott Reilly、Scott Taylor、scribu、scruffian、Sean Hayes、Sebastian、Sergey Biryukov、Shawn Hooper、Sheri Bigelow、Simon Wheatley、Siobhan、Stanko Metodiev、Stephane Daury (stephdau)、Stephen Edgar、Steve Grunwell、Steven Word、stuartshields、Sudar、Sunny Ratilal、taka2、tharsheblows、Thor Brink、Tim Smith、tlexcellent、tmatsuur、TobiasBg、Tomas Mackevicius、TomHarrigan、Toro_Unit (Hiroshi Urabe)、Toru Miki、Tracy (LilJimmi) Levesque、Tryon Eggleston、Ty Carlson、Udit Desai、vivekbhusal、Weston Ruter、Will Norris、willgladstone、William Earnhardt、willstedt、WPMU DEV Jose、Yoav Farhi、Yuri Salame、Zach Wills、Zack Katz和Zack Tollman。
\n特别感谢Siobhan McKeown制作发布视频、Hugo Baeta的设计和Jack Lenox的配音。
\n最后,让我们感谢为发布视频制作了字幕的贡献者,这次的发布视频被翻译成了30种语言!
\n如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。感谢您选择WordPress,我们4.4见!\n
\n收藏、编辑、发布,向您介绍最新的”按这里“工具。在工具菜单中,将”按这里“加入到您的浏览器书签或移动设备主屏幕,然后您就可以迅雷不及掩耳地共享您的内容。共享您喜欢的视频、图片和内容从来没有像现在这样简单快捷。
\n无论您使用何种语言,在WordPress中写作都将变得更好。WordPress 4.2将原生支持许多新字符,包括中日韩文字、音乐和数学符号,以及象形文字。
即使您没有在使用以上那些字符,您仍可获益——WordPress现已支持颜文字!发挥创意并用、、、与所有其他颜文字来装点您的内容。
\n您可以在定制器中浏览和预览已安装的主题,并可让主题在您的站点亮相之前确保它能够搭配您的内容。
\n\n\n把Tumblr.com和Kickstarter的链接粘贴进编辑器,那些内容就将魔法般地出现在您眼前。您的发布和编辑体验会随着我们的每次发布变得更密不可分。
\n\n\n向无聊的加载屏幕说再见,并向简单顺滑的插件升级说你好。点击现在升级,您即可以看到魔法发生。
\n\n数据库字符编码已从utf8变为utf8mb4,加入了对所有4字节字符的支持。
\n您现在可以在JavaScript中通过wp.a11y.speak()
向屏幕阅读器发送音频提醒。传入字符串,更新就会被发送到专用的ARIA即时通知区域。
不同分类法间共享的条目信息将在其中一条获得更新时分离。您可以在插件开发者手册中获取更多信息。
\nWP_Query
、WP_Comment_Query
和WP_User_Query
现在支持使用具名的元查询条款进行复杂排序。
此次发布由Drew Jaynes领头,并得到了以下个人的帮助。这次发布包含了283人的贡献,创下新高。在您喜欢的音乐服务中听听巴德·鲍威尔,并看看下面这些个人资料吧:
\n@mercime、A5hleyRich、Aaron D. Campbell、Aaron Jorbin、abhishekfdd、Adam Silverstein、Ahmad Awais、Alex King、Alex Mills (Viper007Bond)、Alin Marcu、Allan Collins、Andrea Fercia、Andrew Bauer、Andrew Nacin、Andrew Norcross、Andrew Ozz、Ankit Gade、Ankit K Gupta、Anton Timmermans、Aram Zucker-Scharff、ArminBraun、Ashfame、Austin Matzko、avryl、Barry Kooij、Beau Lebens、Ben Doherty (Oomph、Inc)、Billy Schneider、Boone B. Gorges、Brandon Kraft、Brian Krogsgard、Brian Watson、CalEvans、carolinegeven、Casey Driscoll、Caspie、Catalin Dogaru、Chip Bennett、chipx86、ChriCo、Chris Baldelomar、Chris Olbekson、Christian Foellmann、Christopher Finke、Clifton Griffin、Code Master、Corphi、Courtney Ivey、Craig Ralston、cweiske、Daisuke Takahashi、Damian、Daniel Bachhuber、Daniel Jalkut (Red Sweater)、Darin Kotter、Darren Ethier (nerrad)、Daryl L. L. Houston (dllh)、Dave McHale、David A. Kennedy、David Anderson、David Herrera、Davide ‘Folletto’ Casali、davideugenepratt、davidhamiltron、Denis de Bernardy、Derek Herman、Derek Smart、designsimply、Dion Hulse、dipesh.kakadiya、Dominik Schilling、doublesharp、DzeryCZ、Dzikri Aziz、e.mazovetskiy、Eduardo Reveles、Edward Caissie、Elio Rivero、Ella Iseulde Van Dorpe、elliottcarlson、enej、Eric Binnion、Eric Lewis、Erick Hitter、Evan Solomon、Fabien Quatravaux、fhwebcs、Florian Simeth、Frank、Frank P. Walentynowicz、Franz Josef Kaiser、Gary Cao、Gary Jones、Gary Pendergast、Geert De Deckere、genkisan、George Stephanis、Graham Armfield、Gustavo Bordoni、hakre、Harish Chaudhari、hauvong、Helen Hou-Sandí、herbmillerjr、Hew、horike、Hugh Lashbrooke、Hugo Baeta、Ian Dunn、ianmjones、idealien、imath、Ipstenu (Mika Epstein)、J.D. Grimes、Jack Lenox、James Collins、janhenckens、Jeff de Wit、Jeff Farthing、Jeremy Felt、Jesin A、jipmoors、Joan Artes、Joe Dolson、Joe McGill、Joel Bernerman、Joen Asmussen、John Blackbourn、John Eckman、John James Jacoby、John Levandowski、Jonathan Desrosiers、joost de keijzer、Joost de Valk、Jose Castaneda、Josh Levinson、jphase、Julio Potier、Justin Kopepasah、Justin Sternberg、Justin Watt、K.Adam White、Kailey (trepmal)、Kelly Dwan、Kevin Ruscoe、Kim Parsell、Kite、Konstantin Kovshenin、Konstantin Obenland、Lance Willett、Leonard、Leonardo Giacone、Liam Gladdy、magicroundabout、maimairel、Mako、Manny Fleurmond、marcelomazza、Marco Chiesi、Marcus Kazmierczak、Marin Atanasov、Mario Peshev、Marius (Clorith)、Mark Jaquith、Mark Senff、Marko Heijnen、Matt、Matt Martz、Matt Mullenweg、Matt Wiebe、Matthew Boynes、Matthew Eppelsheimer、Matthew Haines-Young、mattyrob、Max Cutler、mehulkaklotar、Mel Choyce、meloniq、mgibbs189、Michael Adams (mdawaffe)、Michael Arestad、Michael Beckwith、michalzuber、Mike Glendinning、Mike Hansen、Mike Jordan、Mike Schinkel、MikeNGarrett、Milan Dinic、mmn-o、Mohammad Jangda、MomDad、Morgan Estes、Morpheu5、Naoko Takano、nathan_dawson、Neil Pie、Nick Halsey、nicnicnicdevos、Nikhil Vimal、ninnypants、nitkr、Nuno Morgadinho、OriginalEXE、Paresh Radadiya、Pat Hawks、Paul Bearne、Paul Schreiber、Paul Wilde、pavelevap、Payton Swick、Pete Mall、Pete Nelson、Peter Wilson、Pippin Williamson、podpirate、postpostmodern、Prasath Nadarajah、prasoon2211、Primoz Cigler、r-a-y、Rachel Baker、rahulbhangale、Rami Yushuvaev、Rastislav Lamos、Ravindra Pal Singh、Rian Rietveld、Ritesh Patel、Robert Chapin、Rodrigo Primo、Ryan Boren、Ryan Marks、sagarjadhav、samo9789、samuelsidler、Scott Grant、Scott Reilly、Scott Taylor、scott.gonzalez、ScreenfeedFr、scribu、Sean Hayes、Sergej Muller、Sergey Biryukov、sevenspark、Simon Wheatley、Siobhan、sippis、Slobodan Manic、solarissmoke、Stephane Daury、Stephanie Leary、Stephen Edgar、Steve Grunwell、stevehickeydesign、Steven Word、Takashi Irie、Takuro Hishikawa、theMikeD、thomaswm、Thorsten Frommen、Till、Timothy Jacobs、tiqbiz、tmatsuur、tmeister、Tobias Schutter、TobiasBg、tomdxw、Travis Northcutt、trishasalas、Ty Carlson、UaMV、Udit Desai、Ulrich Sossou、Veritaserum、voldemortensen、VolodymyrC、vortfu、welcher、Weston Ruter、William Earnhardt和WordPressor。
\n特别感谢Siobhan McKeown制作发布视频及Cami Kaos为视频配音。
\n最后,让我们感谢为发布视频制作了字幕的贡献者,这次的发布视频被翻译成了30种语言!
\nAdrian Pop、Alin Marcu、Bagerathan Sivarajah、Besnik、Bjørn Johansen、Chantal Coolsma、cubells、Daisuke Takahashi、Diana K. Cury、DjZoNe、dyrer、Elzette Roelofse、fxbtacoverdoenard、Gabriel Reguly、Jenny Wong、Gary Jones、Håvard Grimelid、Joachim Jensen、Jimmy Xu、Junko Nukaga、Justina、Kostas Vrouvas、Krzysztof Trynkiewicz、Luís Rodrigues、Luis Rull、Mark Thomas Gazel 、Marius Jensen、matthee、Mattias Tengblad、Matúš Záhradník、Mayuko Moriyama、Michal Vittek、Milan Dinić、MrShemek、Naoko Takano、pavelevap、Peter Holme Obrestad、Petya Raykovska、Przemysław Mirota、qraczek、Rafa Poveda、Rami Yushuvaev、Rasheed Bydousi、Rhoslyn Prys、Robert Axelsen、Sergey Biryukov、Siobhan Bamber、Stephen Edgar、ک To Have داشتن、Torsten Landsiedel、Victor J. Quesada、Wolly、Xavi Ivars和Xavier Borderie。
\n如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。感谢您选择WordPress,我们4.3见!\n
感谢Google的Noto字体家族,Twenty Fifteen有着无懈可击的语言支持。
\n简单的排版在任何屏幕尺寸上都容易阅读。
\n您的内容永远居于最中,无论是在手机、平板、膝上型电脑还是台式机上阅读都是如此。
\n有时,您需要集中精力遣词造句。试试打开免打扰写作模式,在您开始打字时,所有会让您分心的东西都会淡出,让您只注意您的写作。您的所有编辑工具都会在您需要用到它们时立刻出现。
\n现在,WordPress 4.1已经有了40多种语言版本,我们也一直在进行更多翻译。您可以在常规选项中切换到任意一种语言。
\n如果您曾经担心过忘记在公用电脑上登出,您现在可以前往您的个人资料页面并登出您的所有会话。
\n嵌入来自Vine的视频也已被简化为了将URL粘贴进文章里。查看我们支持的嵌入的完整列表。
\n插件安装器现在会为您推荐值得一试的插件。推荐是基于您和其他用户已经安装的插件做出的。
\n元数据、日期和信息查询现已支持高级条件逻辑,如嵌套语句和多种操作符——A AND ( B OR C )
。
定制器现在能够根据当前预览的页面有条件地显示面板和小节。
\n<title>
标签add_theme_support( ''title-tag'' )
让WordPress来处理复杂的页面标题。
通过对内联代码文档的改善,开发者参考现在比以往任何时候都更完整。
\n本次发布由John Blackbourn领头,并得到了如下个人的帮助。在您喜欢的音乐服务中听听黛娜·华盛顿,并看看下面这些个人资料吧:
\nAaron D. Campbell、Aaron Jorbin、Adam Silverstein、akumria、Alex Concha、Alex Mills (Viper007Bond)、Alex Shiels、Allan Collins、Amaury Balmer、Amruta Bhosale、Andrea Fercia、Andrea Gandino、Andrew Munro (sumobi)、Andrew Nacin、Andrew Ozz、Andrew Ryno、Andrey “Rarst” Savchenko、Ankit Gade、Ankit K Gupta、antpb、arippberger、Austin Matzko、Bainternet、Barry Kooij、Ben Dunkle、Ben May、Bernhard Riedl、Birgir Erlendsson (birgire)、bobbingwide、Boone B. Gorges、Brady Vercher、Bram Duvigneau、Brandon Kraft、Brian DiChiara、Brian Richards、Brian Watson、Camden Segal、Captain Theme、Carlos Zuniga、Caspie、ccprice、Charles Fulton、ChriCo、Chris Aprea、Chris Jean、Chris Marslender、Chris Reynolds、chriscct7、chrisl27、Christian Foellmann、Christopher Finke、Corey Snow、Corphi、curtjen、Damon Cook、Dan Cameron、Daniel Bachhuber、Daniel Convissor、Darren Ethier (nerrad)、Daryl Koopersmith、Dave McHale、David A. Kennedy、David Herrera、David Laietta、David Wood、DavidTheMachine、dcavins、Dennis Ploetner、Dion Hulse、Dirk Weise、Dominik Schilling、Dominik Schwind、Drew Jaynes、Dustin Filippini、Dustin Hartzler、Elio Rivero、Eric Binnion、Eric Holmes、Eric Lewis、Fabien Quatravaux、florianziegler、Gabe Shackle、Gary Cao、Gary Pendergast、Gennady Kovshenin、George Olaru、George Stephanis、Greg Rickaby、Gregory Cornelius、Gregory Karpinsky (@tivnet)、Gustavo Bordoni、hardy101、hauvong、Helen Hou-Sandí、heshiming、honeysilvas、hugodelgado、Ian Stewart、ianmjones、Ignacio Cruz Moreno、imath、Ipstenu (Mika Epstein)、Ivan Kristianto、J.D. Grimes、jaimieolmstead、jakub.tyrcha、janhenckens、Janneke Van Dorpe、Japh、Jared Wenerd、jarednova、jeanyoungkim、Jeff Farthing、Jeff Stieler、Jeremy Felt、Jeremy Herve、Jesin A、Jesper Johansen (jayjdk)、Jesper van Engelen、Jesse Pollak、jipmoors、Joe Dolson、Joe McGill、John Eckman、johnrom、johnstonphilip、Jon Brown、Jon Cave、Jonathan Brinley、Jonathan Desrosiers、Joost de Valk、Jordi Cabot、Joshua Abenazer、JOTAKI Taisuke、jrf、julien731、Justin Sainton、Justin Sternberg、K.Adam White、Kailey (trepmal)、Kaito、kamelkev、karpstrucking、keesiemeijer、Kelly Dwan、Kevin Langley、Kiko Doran、Kim Parsell、Kirk Wight、kitchin、Knut Sparhell、Konstantin Kovshenin、Konstantin Obenland、Kostas Vrouvas、kraftner、kristastevens、Kurt Payne、Lance Willett、Laurens Offereins、linuxologos、Liuiza Arunas、loushou、Lutz Schroer、Manoz69、mantismamita、marco、Mario Peshev、Marius (Clorith)、Mark Hudnall、Mark Jaquith、Mark Senff、Marko Heijnen、marsjaninzmarsa、Matias Ventura、Matt Mullenweg、Matt Wiebe、Matthew Boynes、Matthew Haines-Young、mattkeys、Maura Teal、Mel Choyce、Mert Yazicioglu、Michael Adams (mdawaffe)、Michael Arestad、Michael Beckwith、Michael Cain、Michael Pick、michalzuber、Michelle Langston、Miguel Fonseca、Mike Hansen、Mike Jolley、Mike Nelson、Mike Schroder、Mikey Arce、Mitch Canter (studionashvegas)、Morgan Estes、Morten Rand-Hendriksen、mvd7793、Nashwan Doaqan、Niall Kennedy、Nick Halsey、Nikhil Vimal (NikV)、Nikola Nikolov、nobleclem、noplanman、Nowell VanHoesen、OriginalEXE、p_enrique、Paul、Paul de Wouters、Paul Schreiber、Paul Wilde、pavelevap、Peter Chester、Peter J. Herrel、Peter Westwood、Peter Wilson、Philip Arthur Moore、phpmypython、Pippin Williamson、Prasath Nadarajah、psycleuk、Ptah Dunbar、quietnic、Rachel Baker、Rami Yushuvaev、ramiabraham、Reuben Gunday、Rian Rietveld、Richard Archambault、Ricky Lee Whittemore、Robert Chapin、Rodrigo Primo、Ryan Boren、Ryan Kienstra、Ryan McCue、Sakin Shrestha、Sam Hotchkiss、Samuel Wood (Otto)、Scott Kingsley Clark、Scott Reilly、Scott Taylor、Sergey Biryukov、Shawn Hooper、Simon Pollard、Simon Wheatley、skaeser、Slobodan Manic、socki03、solarissmoke、Stephane Daury、Stephen Edgar、Stephen Harris、Steve Grunwell、Sumit Singh、TacoVerdo、Takashi Irie、Takayuki Miyauchi、Tammie、Tareq Hasan、Taylor Lovett、Thorsten Frommen、Till Kruss、Tobias Schutter、TobiasBg、Toby McKes、Tom J Nowell、Tomas Mackevicius、TomHarrigan、Topher、Torsten Landsiedel、Tracy Levesque、transom、Travis Smith、Ty Carlson、Udit Desai、Umesh Kumar、Vinod Dalvi、vlajos、voldemortensen、Weston Ruter、Yoav Farhi、Yuta Sekine、Zack Rothauser和Zack Tollman。
\n本次发布得到了283人的贡献,再次创下新高。
如果您想帮忙,请查阅Make WordPress和我们的核心开发博客。
\n感谢您选择WordPress。节日快乐,我们4.2见!\n
WordPress 4.0.1现已发布,这是一次对所有较早版本的重要安全更新,我们强烈建议您立即升级您的站点。
\n支持后台自动更新的站点将在未来几个小时内被自动升级到WordPress 4.0.1。如果您仍在使用WordPress 3.9.2、3.8.4或3.7.4,请升级到3.9.3、3.8.5或3.7.5来保证您站点的安全性。(我们不对旧版本提供支持,所以也请考虑升级到4.0.1来使用我们最新最强大的版本。)
\nWordPress 3.9.2与更早版本均受一严重的跨站脚本漏洞影响,可能使匿名用户危害站点安全。此漏洞由Jouko Pynnonen报告。这项问题并不影响4.0版,但4.0.1版也修正了如下8个安全问题:
\n4.0.1版也修正了4.0中的23个bug,我们也做出了两项强化修改,包括在从上传的照片中提取EXIF数据时进行更好的验证,由Chris Andrè Dale报告。
\n我们感谢这些问题被负责任地透漏给我们的安全小组。要获取更多信息,请参见发布说明或查阅修改列表。
\n下载WordPress 4.0.1简体中文版或在仪表盘→更新中点击“现在更新”。
\n已经在测试WordPress 4.1了?包含这些安全更新的beta 2现已发布(zip)。更多有关4.1的信息,请参见beta 1发布说明。
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:57:"https://cn.wordpress.org/2014/11/21/wordpress-4-0-1/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:2:"21";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:30:"https://cn.wordpress.org/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:9:"\n hourly ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:4:"\n 1 ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Thu, 25 Apr 2019 11:40:58 GMT";s:12:"content-type";s:34:"application/rss+xml; charset=UTF-8";s:6:"x-olaf";s:3:"⛄";s:13:"last-modified";s:29:"Wed, 13 Mar 2019 03:59:19 GMT";s:4:"link";s:61:"Clean Blocks is a new free theme from Catch Themes that was released last week on WordPress.org. The design is suitable for businesses, agencies, freelancers, and other service professionals who require featured content, a portfolio, testimonials, a blog, and a services section.
\n\nClean Blocks includes basic Gutenberg compatibility in that it supports all core blocks and is has a few enhanced block styles.
\nIt may seem unnecessary to specify that it is Gutenberg-compatible, since the editor has been part of WordPress core since early December 2018. However, more than half of all WordPress users (~55%) are not running version 5.0+. Nearly 30% are hanging back at 4.9 and 25% are on even older versions.
\n\nTheme authors who create products that have Gutenberg-only features are not yet building for the majority of WordPress users. These authors are carving a path for the future of theme development. The Clean Blocks theme doesn’t really fall into this category, as its essentially enables users on WordPress 5.0+ to continue using the new editor without any styling issues. It is also compatible with earlier versions of WordPress (4.8+).
\nClean Blocks recommends a collection of Catch Themes’ functionality plugins upon theme activation. These plugins handle things like galleries, infinite scroll, Instagram feeds, widgets, and additional content types. The theme includes dozens of options in the Customizer for controlling nearly every aspect of how content is displayed – from excerpt length to categories displayed on the home page to header text color. This sort of overloaded Customizer options panel is common for multipurpose style themes, and many users have come to expect it.
\nCheck out a demo of the free version to see all the features in action.
\nThe name “Clean Blocks” implies that the theme goes beyond the basics to customize the Gutenberg experience, but that doesn’t seem to be the case. The vast majority of the features seen in the demo are controlled by the Customizer. For example, features like Testimonials and Services are not available as blocks. While some theme authors opt to integrate features like this by pairing their themes with block collection plugins, Catch Themes has put everything into the Customizer.
\nEven with Gutenberg compatibility, many themes still have a disconnect between the back and frontend where certain features can only be configured in the Customizer. This fractured customization experience is one of the necessary evils for this transition time before the block editor is fully capable of handling more complex aspects of site customization.
\nClean Blocks is an example of a multipurpose theme that is essentially keeping it old school in terms of content customization, while providing basic Gutenberg compatibility for users who are running WordPress 5.0+. The theme is available on WordPress.org and has already been downloaded several hundred times during its first week in the directory.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 24 Apr 2019 22:46: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:1;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:74:"WPTavern: Laraberg, a Gutenberg Implementation for Laravel, is Now in Beta";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=89058";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:83:"https://wptavern.com/laraberg-a-gutenberg-implementation-for-laravel-is-now-in-beta";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3953:"\nThe family of Gutenberg derivatives is expanding with the beta release of Laraberg, an implementation for Laravel. Maurice Wijnia, a developer at Van Ons, an agency based in Amsterdam, created Laraberg as an easy way for developers building applications with Laravel to integrate the Gutenberg editor. It includes a simple API and support for the Laravel File Manager for uploading files.
\n\n“The goal for Laraberg is to give developers the ability to add the Gutenberg editor to any page they like in a way that is as easy as possible, but at the same time it has to prove enough options to tailor the editor so it can fit into any Laravel project out there,” Wijnia said.
\nVan Ons has a preference for using Laravel in their projects, due to its increasing popularity and active community. Laraberg makes it possible for the agency to tap into the convenience of the Gutenberg editor without giving up the performance and features they enjoy in the Laravel framework. The beta release is now available on GitHub and Pacagist. Van Ons plans to actively implement Laraberg in their own projects and will also be collecting feedback from beta testers.
\nWijnia said he was inspired by the Drupal Gutenberg project, whose creators also authored Gutenberg.js, a package that makes it easier to bring Gutenberg into other applications. Providing a foundation for using Gutenberg on any CMS or framework is part of Frontkom’s long term vision for improving the open web and enabling communities to collaborate on mutually beneficial extensions.
\nAs the editor continues to expand to more platforms and frameworks, a CMS-agnostic block library would offer a central place for Gutenberg’s increasingly diverse user base to discover new blocks. WordPress.org has the opportunity to provide that in its own block library, with the support of the Gutenberg Cloud team that pioneered the idea in 2018.
\n“If Gutenberg Cloud can serve as a proof of concept that WP.org can later adopt as their own, we are happy,” Frontkom CTO Per Andre Rønsen said. He also further commented on the WordPress.org Block Library proposal, advocating for the team to grow their vision beyond the WordPress community only. No official decision has been announced yet. If WordPress decides to forgo the opportunity of providing a block library inclusive of other frameworks and platforms, then the Gutenberg Cloud will continue to be the place for discovering blocks that can be used across multiple platforms.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 24 Apr 2019 17:24:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:60:"HeroPress: How the WordPress community helped me find my way";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2786";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:172:"https://heropress.com/essays/how-the-wordpress-community-helped-me-find-my-way/#utm_source=rss&utm_medium=rss&utm_campaign=how-the-wordpress-community-helped-me-find-my-way";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:30665:"Este ensaio também está disponível em português.
\nAs I make a checklist of all the things I’ll have to pack to travel from São Paulo to Berlin, to attend WordCamp Europe 2019, I can’t stop thinking how hard the path to this point has been.
\nFor some of people, a travel like this may seem ordinary, but for me, this will be the farthest I’ve ever been until now, in many ways. Especially because the last time I was planning to attend an international WordCamp, things didn’t work out at all.
\nSo let me tell you about the path.
\nI was born and raised in São Paulo. Allow me to give you some context about my city. São Paulo is the richest and biggest city of Brazil. With more than 14 million people, it’s also the biggest city of the south hemisphere. It’s even bigger than New York.
\nLike every big city, São Paulo is a place of opportunities, but also a place of contrasts.
\nGrowing up, although we were poor, my family cared a lot about the education of me and my little brother. My father who always liked technology, managed to get a computer for us in 1996. At that time, I was 6 years old, and we were the only family in my neighborhood to have a computer for a long time, and that was sad. That early exposure to technology made a big difference in my life.
\nAt age 13, I was very interested in graphic design and coding.
\n\nWe had a very limited and expensive dial-up internet, that was only free after midnight and at weekends.
So to learn these skills, my best options were the CD-ROM magazines that my father would bring home. I also learned about HTML with a book about Microsoft Front Page. At age 14 I sold my first website, entirely created on Front Page, with lots of GIFs and <marquee> tags, for a neighbour who needed it for a college project. She loved it!
\nI decided I wanted to work with design. So I started a Graphic Design course during the high school. With my love for web design, all I wanted was to have a site that was actually online. I couldn’t afford a host, but fortunately at this time, blogs became very popular here in Brazil.
\nI looked for a platform to create a portfolio. I played a little with one called WordPress (you may have heard of it) and ended up using Blogger instead, because there was the possibility to customize the theme’s CSS online. I made a very dark grungy theme for my blog that’s still online.
\nI got a scholarship for Graphic Design at a good College in São Paulo, but I still would have to pay for half of the monthly tuition. The problem was that my family definitely had no means to afford it. My parents said they would cut some expenses and help me, but I knew that there wasn’t anything they could cut. So I told them to not worry, I would find a job.
\nAt this point I had made a freelance gig creating a HTML website (in Dreamweaver this time). With exactly 1 month left for the College application, this client proposed that I started working there to maintain the website I just made. So I was able to (barely) pay for the college. After six months, I applied for a full scholarship and it was granted. Things got a little better financially, but the path was still rocky.
\nIt took me 3 hours by bus from my house to the college every single day, just inside the city of São Paulo (remember when I said this city is huge?).
\n\nI had the cheapest hot dog for lunch every day, because I couldn’t afford a real meal.
Then I would go to work (another 1h30 of bus from the college), and at night I would head back home (another bus, another 1h30). That was my routine for one and a half year throughout the college. As you can imagine, I was exhausted, and eventually getting ill.
\nThat’s when I decided that I would quit my job and start a business with my boyfriend Allyson Souza, that I met during my Graphic Design course in High School. We started the company officially in july, 2009. We named it Haste (the portuguese word for “stem”).
\nWe were 19 years old, not much experience, zero network and money, a lot of energy, and some extra self-confidence (I could have summarized simply as “millennials”, right?). Allyson’s father gave us a computer and a part of his office, for which I am very grateful, and we created all the graphic materiais for his courses company in exchange.
\nWe started working with graphic design only, and it took us some time to realize that web development was our future.
\nI remembered WordPress and tried it again. I liked how the platform had evolved. We made a second version of our website in WordPress, using a simple free theme, which I edited the CSS directly (oh god). We tried to create websites for clients modifying existing themes (at least we learned about child themes later), but we definitely didn’t feel in control of what we were doing.
\nIn January 2011, my mother had a stroke. She had a brain surgery, and after a month, she was back home with a 6 inches scar in the head. That was the lowest point on my path.
\nThe next years I had to take care of her, because of some consequences of the stroke, both physical and psychological. As the only family member who hadn’t a “formal” job, with a boss and a defined schedule, I was the one who had to take her to appointments, or the ER, or stay home when she wasn’t ok. It was very hard to reconcile the final year of college, the work and my mom’s health care.
\nAt Haste, we felt that things were not evolving. In 2013, after some partnerships that took us to some confusing paths, we decided to have a complete makeover. We defined a new focus: web design and development with WordPress. We created a new website, with a theme fully developed by us. We wanted to overcome the fear of coding, and wanted to know exactly what we were doing. So we started studying a lot by ourselves.
\nAllyson was responsible for the PHP and JavaScript and I was supposed to make the design, the HTML and CSS. He started to ask a lot of questions in the group of WordPress Brasil community at Facebook. We finished the website, and people loved it, specially the illustration with parallax effect that made the girl move her eyes.
\n\nWe were proud WordPress developers now.
We started attending the meetups, and then the WordCamp. I was amazed how the open-source culture was all about sharing knowledge with strangers, with no fear of competition, just the spirit of collaboration. We felt no longer isolated. We made real friends (shout out to all my WordPress friends).
\nSoon we were both involved in the community, and became WordCamp São Paulo organizers in 2014.
\nThe new website and our participation in the WordPress community were really what we needed to give us some perspective and stability. So we didn’t stop there.
\nIn the 2014 edition of WordCamp São Paulo, I was the only female speaker. That made me realize a few things.
\nFirst that the proportion of men in the community events was not only the majority but, we almost didn’t had any women at all, which was very weird.
\nSecond, we know that lots of girls feel intimidated in an environment with too much men. I always had a majority of male friends since I was a kid, and even so, I probably wouldn’t get involved with the community if it wasn’t by the fact that my boyfriend / partner was with me.
\nA few sexists incidents had happened with me too. I reacted, and the men involved seemed to understand that I wasn’t ok, and changed their behavior as far as I know.
\nWe don’t have as many meetups and WordCamps here in Brazil as in US. Although Brazil is becoming a technology hub, the WordPress community has still a lot of room to grow, compared to other communities. So, I think we have the opportunity to make things different while everything is not settled yet.
\nSo I decided to act now.
\n\nI started a poll asking the women involved with WordPress the reasons why they wouldn’t attend the events. The results proved it wasn’t just me complaining about small things.
Some jokes kept women away. Some condescending actions made them feel diminished. And even the lack of information from our part, that the WordCamps are inclusive events, made the women not to come. The lack of time, was an important factor too.
\nBased on this data, the next year we managed to increase the proportion of female speakers from 5% to 32% at WordCamp São Paulo 2015. More women became organizers too. In 2019 we have 4 women out of 10 active organizers. The last WordCamp we had blind people attending, and their feedback was great. We still need to improve racial diversity though.
\nIn 2015, Allyson had told me about this new scholarship program from the WordPress Foundation for women who work for equality in the community around the world. So I applied for the very first Kim Parsell Memorial Scholarship. Kim Parsell left a beautiful legacy of inclusion and love, having worked to bring more women, older people, and other minorities to the WordPress community. She was known as the #WPMom.
\nThe result came few months later. I received an email, and had no reaction for a few minutes. I had won the scholarship, and it granted me a travel to WordCamp US 2015, in Philadelphia Pennsylvania, with flights and hotel covered.
\nYou see: I had never left my country. I had just took flight for the first time that same year. I was not even close to dream to go to US, because it was impossible for me at the moment. Sometimes your mindset in the only thing putting limitations in your dreams.
\nI was so happy, you have no idea. Alx Block and Cami Kaos reached to me to give me instructions and they were very kind.
\nBut then… my visa application was denied. They considered my sudden passport and visa solicitation, with no money to travel (that’s exactly the point of a scholarship!), and lack “ties” in Brazil very suspicious. I told them that the WordPress Foundation would pay for everything. The flights and the hotel were already booked. The officer even told me that the WordPress Foundation letter could be easily forged. I tried again, with no success.
\n\nI couldn’t go to WordCamp US 2015.
I couldn’t go to WordCamp US 2016 too, when they asked if I wanted to try again, and my visa was denied… again. This time I think at least the officer searched online for me, saw it was true, but couldn’t do anything, since my situation hadn’t change.
\nI was so disappointed. This still hurts me, I must confess. Sometimes, there are real barriers and gates that a simple mindset change cannot open.
\nThe next years, I focused on my company and the work at the community. My mom’s health improved, she’s in great shape now. My family supports my work.
\nWe became specialists in WordPress at Haste. We developed themes, plugins and sites for companies in Brazil and America. I now have a stable income and I live exclusively from my work with WordPress. We are celebrating 10 years in 2019.
\nI traveled through Brazil because of WordPress, to speak at WordCamps and Meetups. I see more and more women working with WordPress, attending meetups and WordCamps, and talking to each other, finding something familiar in every other woman’s face.
\n\nLast year we decided we would go to WordCamp Europe 2019 in Berlin, since we don’t need a visa to most countries there, including Germany.
This time I can afford it (with a lot of planning and expenses cut, but I’ll be ok). I have to confess that I’m a little anxious about the immigration process.
\nMy goal at WordCamp Europe is to know the most people I can. It’s not a matter of quantity, but if the WordPress community taught me something was that every person has something to teach and to learn. So If you are attending WordCamp Europe, let’s meet!
\nSo now I hope you can see what this travel really means to me, and why every small conquest means a lot. It’s not just because it was hard. But because I’m not the only one who deserve it, but unfortunately I’m a exception between other people who have the same background as I.
\nThere are so many young girls and boys that don’t dare to dream about visiting other countries, or even getting in the college. Lots of kids that don’t have a computer, or even access to internet. The only difference is that I was given opportunities, people believed in me. Doors were opened. And just then I could prove my value.
\nNow my next dream is to be able to make the journey a little easier than it was for me, specially for women and young Brazilians. Because I think that’s our responsibility in the community. Teach others, share information, donate some of your time, create new tools, plugins and resources, mentor people. As my brother’s tattoo says, be the person you needed when you were younger.
\nEnquanto faço uma lista de todas as coisas que preciso para viajar de São Paulo para Berlim, para participar do WordCamp Europe 2019, não posso deixar de pensar no quão difícil foi o caminho até esse ponto.
\nPara algumas pessoas, uma viagem como essa pode parecer comum, mas, para mim, esse será o mais longe que já fui até agora, de muitas maneiras. Especialmente porque, da última vez que eu planejava participar de um WordCamp internacional, as coisas não deram certo.
\nEntão deixe-me contar sobre esse caminho.
\nEu nasci e cresci em São Paulo. Permita-me dar um pouco de contexto sobre minha cidade. São Paulo é a mais rica e maior cidade do Brasil. Com mais de 14 milhões de pessoas, é também a maior cidade do hemisfério sul. É maior que Nova York.
\nComo toda grande cidade, São Paulo é um lugar de oportunidades, mas também de contrastes.
\nCrescendo, apesar de sermos pobres, minha família se importava muito com a minha educação e do meu irmão mais novo. Meu pai, que sempre gostou de tecnologia, conseguiu um computador para nós em 1996. Naquela época, eu tinha 6 anos, e éramos a única família das redondezas a ter um computador por um longo tempo, e isso era triste. Essa exposição precoce à tecnologia fez uma grande diferença na minha vida.
\nAos 13 anos, eu já estava interessada em design gráfico e programação. Nós tínhamos aquela internet discada muito limitada e cara, que só era gratuita depois da meia-noite e nos fins de semana. Então, para aprender essas habilidades, minhas melhores opções eram as revistas em CD-ROM que meu pai trazia para casa. Eu também aprendi sobre HTML com um livro sobre o Microsoft Front Page. Aos 14 anos, vendi meu primeiro site, inteiramente criado no Front Page, com muitos GIFs e tags <marquee>, para uma vizinha que precisava para um projeto da faculdade. Ela adorou!
\nEu decidi que queria trabalhar com design. Então fiz o curso técnico em design gráfico durante o ensino médio. Com o meu interesse pelo web design, tudo o que eu queria era ter um site que estivesse online. Eu não podia pagar um servidor, mas felizmente, neste momento, os blogs se tornaram muito populares aqui no Brasil.
\nProcurei uma plataforma para criar um portfólio. Eu brinquei um pouco com uma plataforma chamada WordPress (você pode ter ouvido falar dela) mas acabei usando o Blogger, porque havia a possibilidade de personalizar o CSS do tema online. Eu fiz um tema escuro e grunge para o meu blog que ainda está online.
\nConsegui uma bolsa de Design Gráfico em uma boa faculdade em São Paulo, mas ainda teria que pagar metade da mensalidade. O problema era que minha família definitivamente não tinha como arcar com isso. Meus pais disseram que cortariam algumas despesas e me ajudariam, mas eu sabia que não havia nada que pudessem cortar. Então eu disse a eles para não se preocuparem, eu encontraria um emprego.
\nNeste momento, eu havia feito um trabalho freelancer criando um site HTML (no Dreamweaver desta vez). Com exatamente 1 mês para o aplicativo da faculdade, esta cliente propôs que eu começasse a trabalhar lá para manter o site que tinha acabado de criar. Então eu pude pagar pela faculdade (bem mal). Depois de seis meses, solicitei uma bolsa de estudos integral e ela foi concedida. As coisas melhoraram um pouco financeiramente, mas o caminho ainda era rochoso.
\nLevava 3 horas de ônibus da minha casa para a faculdade todos os dias, apenas dentro da cidade de São Paulo (lembra quando eu disse que essa cidade é enorme?). Eu comia um cachorro-quente mais barato para o almoço todos os dias, porque eu não podia pagar uma refeição de verdade. Então eu ia trabalhar (outra 1h30 de ônibus da faculdade), e à noite eu voltava para casa (outro ônibus, outro 1h30). Essa foi a minha rotina por um ano e meio durante a faculdade. Como você pode imaginar, eu estava exausta e ficando doente.
\nFoi então que decidi largar meu trabalho e começar um negócio com meu namorado Allyson Souza, que conheci durante o curso de Design Gráfico no Ensino Médio. Nós começamos a empresa oficialmente em julho de 2009. Nós a nomeamos Haste.
\nNós tínhamos 19 anos de idade, não muita experiência, zero networking e dinheiro, muita energia e alguma autoconfiança extra (eu poderia ter resumido simplesmente como “millennials”, certo?). O pai do Allyson nos deu um computador e uma parte de seu escritório, pelo que sou muito grata, e criamos todos os materiais gráficos para sua empresa de cursos em troca.
\nComeçamos a trabalhar apenas com design gráfico e levamos algum tempo para perceber que o desenvolvimento web era o nosso futuro.
\nLembrei-me do WordPress e tentei novamente. Eu gostei de como a plataforma evoluiu. Fizemos uma segunda versão do nosso site no WordPress, usando um simples tema gratuito, que eu editei diretamente o CSS (não façam isso!). Tentamos criar websites para clientes que modificando temas existentes (pelo menos aprendemos sobre temas filhos mais tarde), mas definitivamente não nos sentíamos no controle do que estávamos fazendo.
\nEm janeiro de 2011, minha mãe teve um AVC. Ela fez uma cirurgia no cérebro, e depois de um mês, ela estava em casa com uma cicatriz na cabeça. Esse foi o ponto mais baixo do meu caminho.
\nNos anos seguintes eu tive que cuidar dela, por causa de algumas consequências do AVC, tanto físicas quanto psicológicas. Como a única pessoa da família que não tinha um emprego “formal”, com um chefe e um horário de trabalho definido, fui eu quem teve que levá-la às consultas, ao pronto-socorro ou ficar em casa quando ela não estava bem. Foi bem difícil conciliar o último ano da faculdade, o trabalho e cuidar da saúde da minha mãe.
\nNa Haste, sentimos que as coisas não estavam evoluindo. Em 2013, após algumas parcerias que nos levaram a caminhos confusos, decidimos fazer uma reformulação completa. Definimos um novo foco: web design e desenvolvimento com WordPress. Criamos um novo site, com um tema totalmente desenvolvido por nós. Queríamos superar o medo de programar e queríamos saber exatamente o que estávamos fazendo. Então começamos a estudar muito por conta própria.
\nAllyson ficou responsável pelo PHP e JavaScript e eu deveria fazer o design, o HTML e CSS. Ele começou a postar muitas perguntas no grupo da comunidade WordPress Brasil no Facebook. Nós terminamos o site, e as pessoas adoraram, especialmente a ilustração com efeito de paralaxe que fez a garota mover seus olhos. Nós éramos orgulhosos desenvolvedores do WordPress agora.
\nNós começamos a frequentar os meetups, e depois o WordCamp da comunidade WordPress. Fiquei espantada com a forma como a cultura de código aberto era toda sobre compartilhar conhecimento com estranhos, sem medo de competir, apenas o espírito de colaboração. Não nos sentíamos mais isolados. Nós fizemos amigos de verdade (alô amigos do WordPress).
\nLogo nos envolvemos na comunidade e nos tornamos organizadores do WordCamp São Paulo em 2014.
\nO novo site e nossa participação na comunidade WordPress foram realmente o que precisávamos para nos dar alguma perspectiva e estabilidade. Então nós não paramos por aí.
\nNa edição de 2014 do WordCamp São Paulo, eu era a única palestrante mulher. Isso me fez perceber algumas coisas.
\nPrimeiro, a proporção de homens nos eventos da comunidade não era apenas a maioria, mas quase não tínhamos nenhuma mulher. O que era muito estranho.
\nEm segundo lugar, sabemos que muitas mulheres se sentem intimidadas em um ambiente com muitos homens. Eu sempre tive a maioria de amigos homens desde criança, e mesmo assim, eu provavelmente não me envolveria com a comunidade se não fosse pelo fato de meu namorado / sócio estar comigo.
\nAlguns incidentes sexistas também aconteceram comigo. Eu reagi, e os homens envolvidos parecem ter entendido o problema, e mudaram seus comportamentos até onde eu sei.
\nNão temos tantos meetups e WordCamps aqui no Brasil como nos EUA. Embora o Brasil esteja lentamente se tornando um polo de tecnologia, a comunidade WordPress ainda tem muito espaço para crescer, em comparação com outras comunidades. Então, acho que temos a oportunidade de fazer as coisas diferentes enquanto tudo ainda não está definido.
\nEntão eu decidi mudar isso.
\nEu comecei uma pesquisa perguntando às mulheres envolvidas com WordPress quais eram as razões pelas quais elas não compareciam aos eventos. Os resultados provaram que não era só eu reclamando de pequenas coisas.
\nAlgumas piadas mantinham as mulheres afastadas. Algumas ações condescendentes fizeram com que se sentissem diminuídas. E mesmo a falta de informação de nossa parte, de que os WordCamps são eventos inclusivos, fez com que as mulheres não viessem. A falta de tempo também foi um fator importante.
\nCom base nesses dados, no ano seguinte conseguimos aumentar a proporção de mulheres palestrantes de 5% para 32% no WordCamp São Paulo 2015. Mais mulheres se tornaram organizadoras também. Em 2019, temos 4 mulheres de 10 organizadores ativos. No último WordCamp, tivemos deficientes visuais comparecendo e o feedback deles foi ótimo. Ainda precisamos melhorar a diversidade racial.
\nEm 2015, Allyson me contou sobre o novo programa de bolsas de estudos da Fundação WordPress para mulheres que trabalham pela igualdade na comunidade em todo o mundo. Então me inscrevi para a primeira bolsa Kim Parsell Memorial. Kim Parsell deixou um lindo legado de inclusão e amor, tendo trabalhado para trazer mais mulheres, pessoas mais velhas e outras minorias para a comunidade WordPress. Ela era conhecida como a #WPMom.
\nO resultado veio alguns meses depois. Recebi um email e não tive reação por alguns minutos. Eu tinha ganhado a bolsa que me garantia uma viagem para o WordCamp US 2015, na Filadélfia, na Pensilvânia, com voos e hotel cobertos.
\nVeja bem: eu nunca tinha saído do meu país. Eu tinha acabado de voar de avião pela primeira vez naquele mesmo ano. Eu não estava nem perto de sonhar em ir para os EUA, porque era impossível para mim no momento. Às vezes sua mentalidade na única coisa colocando limitações em seus sonhos.
\nEu estava tão feliz, você não faz ideia. Alx Block e Cami Kaos entraram em contato para me dar instruções e foram muito gentis.
\nMas então… meu pedido de visto foi negado. Eles consideraram minha solicitação repentina de passaporte e visto, sem dinheiro para viajar (esse é exatamente o ponto de uma bolsa de estudos!), e a falta de “laços” no Brasil muito suspeitos. Eu disse a eles que a Fundação WordPress pagaria por tudo. Os voos e o hotel já estavam reservados. O oficial até me disse que a carta da Fundação WordPress poderia ser facilmente falsificada. Eu tentei de novo, sem sucesso.
\nEu não pude ir para o WordCamp US 2015.
\nEu também não pude ir ao WordCamp US 2016, quando eles perguntaram se eu queria tentar novamente, e meu visto foi negado… de novo. Desta vez, acho que pelo menos o oficial pesquisou on-line por mim, viu que era verdade, mas não conseguiu fazer nada, pois minha situação não mudara.
\nEu estava tão desapontada. Ainda fico triste de lembrar, devo confessar. Às vezes, existem barreiras e portões reais que uma simples mudança de mentalidade não pode abrir.
\nNos anos seguintes, concentrei-me em minha empresa e no trabalho na comunidade. A saúde da minha mãe melhorou, ela está em ótima agora. Minha família apóia meu trabalho.
\nNós nos tornamos especialistas em WordPress na Haste. Desenvolvemos temas, plugins e sites para empresas no Brasil e na América. Agora tenho uma renda estável e vivo exclusivamente do meu trabalho com o WordPress. Estamos comemorando 10 anos em 2019.
\nEu viajei pelo Brasil por causa do WordPress, para falar em WordCamps e Meetups. Fui para Fortaleza, Belo Horizonte, Curitiba, Porto Alegre. Eu vejo mais e mais mulheres trabalhando com o WordPress, participando de meetups e WordCamps, e conversando, encontrando algo familiar no rosto das outras mulheres.
\nNo ano passado, decidimos que iríamos para o WordCamp Europa 2019 em Berlim, já que não precisamos de visto para a maioria dos países, incluindo a Alemanha.
\nDesta vez, posso pagar (com muito planejamento e redução de despesas). Tenho que confessar que estou um pouco ansiosa com o processo de imigração.
\nMeu objetivo no WordCamp Europa é conhecer o máximo de pessoas que posso. Não é uma questão de quantidade, mas se a comunidade do WordPress me ensinou algo foi que cada pessoa tem algo para ensinar e aprender. Então, se você estiver participando do WordCamp Europa, vamos nos conhecer!
\nEntão agora eu espero que você possa ver o que essa viagem realmente significa para mim, e porque cada pequena conquista significa muito. Não é só porque foi difícil. Mas porque eu não sou a única que merece isso, mas infelizmente sou uma exceção entre outras pessoas que têm o mesmo histórico que eu.
\nHá tantas meninas e meninos que não se atrevem a sonhar em visitar outros países ou até mesmo entrar na faculdade. E quando se atrevem, tem seus sonhos podados. Muitas crianças que não têm computador nem acesso à internet. A única diferença é que me foram dadas oportunidades, as pessoas acreditaram em mim. Portas foram abertas. E só então eu pude provar o meu valor.
\nAgora meu próximo sonho é poder tornar a jornada um pouco mais fácil do que foi para mim, especialmente para mulheres e jovens brasileiros. Porque acho que é nossa responsabilidade na comunidade. Ensine outras pessoas, compartilhe informações, doe um pouco do seu tempo, crie novas ferramentas, plugins e recursos, oriente as pessoas. Como diz a tatuagem do meu irmão, seja a pessoa de que você precisava quando era mais jovem.
\nThe post How the WordPress community helped me find my way 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, 24 Apr 2019 12:00: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:15:"Anyssa Ferreira";s: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:62:"WPTavern: Henry Zhu Launches New Maintainers Anonymous Podcast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=89021";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/henry-zhu-launches-new-maintainers-anonymous-podcast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3117:"Maintainers Anonymous is a new podcast created by Henry Zhu, who has been the primary maintainer of Babel for the past two years. Babel is a JavaScript compiler used by Facebook, Netflix, Spotify, and millions of others. It is downloaded over 18 million times per month and used by more than 1.8 million repositories on GitHub. Zhu recently left his job at Adobe to work on Babel and open source full-time.
\nIn his new podcast, Zhu is talking with other maintainers to unearth their valuable perspectives and share similar struggles. By presenting them as regular people, rather than faceless code projects, Zhu is aiming to encourage empathy for maintainers.
\nMaintainers Anonymous is centered around the “how” of maintenance and Zhu is open to having guests from a variety of fields and disciplines, such as a librarian, gardener, or moderator. In an episode titled “Speedrunning with Omnigamer,” Zhu and his first guest, Eric Koziel, discuss the intricacies of “speedrunning,” playing a video game with the goal of beating it as fast as possible. Koziel describes it as a medium for doing an optimization challenge. Since the games are just software, he and Zhu explored how speedrunning intersects with coding and talked about some of the parallels with maintaining open source software.
\nThe next two episodes are a series with guest Stephanie Hurlburt, a graphics engineer and owner of the company that makes Basis, an image/texture compression product. They delve deeper into how business development is relevant to open source, setting healthy boundaries, inherent vs. perceived value, marketing, and more.
\nIf you’re looking for a new podcast to add to your subscriptions, Zhu’s Maintainers Anonymous offers a wide variety of topics and perspectives that touch on open source, maintainership, and other aspects of life and business in the world of technology. New episodes are available on the podcast’s website, and listeners can also subscribe via RSS, Apple Podcasts, Google Podcasts, or Spotify. Follow @MaintainersAnono on Twitter for all the latest.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 23 Apr 2019 17:53:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:104:"WPTavern: Celebrate Earth Day by Learning about Environmentally Friendly Web Development on WordPress.tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88997";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:115:"https://wptavern.com/celebrate-earth-day-by-learning-about-environmentally-friendly-web-development-on-wordpress-tv";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3247:"Today is Earth Day, a worldwide annual event first celebrated in 1970 that focuses on addressing environmental concerns. Earth Day Network coordinates 192 countries with more than a billion people participating in today’s event. The organization uses WordPress to build the world’s largest environmental movement through education, public policy, and consumer campaigns.
\nOver the past few years, environmentally-friendly web development has become an increasingly popular topic at WordCamps. Several presentations are available on WordPress.tv that highlight how web developers have the ability to make a positive impact on reducing the internet’s carbon footprint.
\nJenn Schlick, a project manager at the MIT Energy Initiative, was one of the first WordCamp speakers to bring greater awareness to this topic with her presentation on Low-Carbon Web Design at WordCamp Finland in 2016. She explained a few ways that developers can minimize a website’s carbon footprint by choosing online services that are powered by renewable energy and optimizing for performance.
\n\nIn 2017, Tom Greenwood gave a presentation titled Zero Carbon WordPress that challenged the community to help tackle climate change. With WordPress powering such a large percentage of the web, the community has the opportunity to lead the way in developing sites that use less energy, powered by hosts that run on renewable energy sources.
\n\nMore recently, Jack Lenox spoke at WordCamp Bordeaux 2019 on “How better performing websites can help save the planet.” His presentation had a stronger emphasis on performance with practical steps for simplifying the interface, reducing code, using the right image file types, caching, accessibility, and more.
\n\nLenox has also created a tiny WordPress theme called Susty that he said is “an experiment in minimalism.” It loads WordPress with just 6KB of data transfer.
\nAt WordCamp Nordic 2019, Jaakko Alajoki gave a presentation titled Environmentally friendly WordPress development, with experiments that used a Raspberry Pi web server and power meter to demonstrate power consumption. The session should be available on WordPress.tv soon.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 22 Apr 2019 22:11:17 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:137:"WPTavern: AMP Plugin for WordPress 1.1 Adds Experimental PWA Plugin Integration, Pre-release of AMP Stories Editor Available in 1.2-alpha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88968";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:147:"https://wptavern.com/amp-plugin-for-wordpress-1-1-adds-experimental-pwa-plugin-integration-pre-release-of-amp-stories-editor-available-in-1-2-alpha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2980:"Version 1.1 of the AMP Plugin for WordPress was released this week after four months in development and 125 merged pull requests from contributors. It includes CSS tree shaking improvements that restore AMP compatibility for WordPress’ default Twenty Nineteen theme, reducing the size of its stylesheet by 53%.
\nIn an effort to get more users opting for the Native mode option, the plugin’s development team has rebranded the template modes:
\n\nIn this release the Paired mode has been rebranded as Transitional mode. One reason for this is that the classic mode was also a paired mode (where there are separate parallel URLs for the AMP version). But more importantly, the goal for this mode is to help facilitate a transition a site to being AMP-first, where there is no separate AMP-specific URLs. So the goal of the Transitional mode is to be a path to Native mode.
The team has also decided to rebrand Classic mode to “Reader” mode, instead of deprecating it. It provides a basic AMP template for getting started that doesn’t necessarily match the site’s theme. Users can can add an “Exit Reader Mode” to the header of their sites with a setting in the Customizer.
\nVersion 1.1 introduces compatibility with the PWA feature plugin, bringing support for the service worker to AMP pages. It extends the service worker to cache AMP CDN assets, images, and Google Fonts. Since the PWA feature plugin is still under active development, the service worker integration is still considered experimental.
\nSupport for creating AMP Stories in WordPress is the next major feature coming to the plugin. A pre-release of the AMP Stories editor is available in 1.2 alpha 1, which also requires the latest version of the Gutenberg plugin. It uses the Gutenberg editor to allow users to build AMP stories with rich media capabilities.
\n\nA preview of the AMP Stories editor was unveiled at AMP Conf 2019 in Tokyo, Japan. Check out the video below to see Alberto Medina give a quick demonstration of how it will work in the upcoming version 1.2 of the AMP for WordPress plugin.
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 20 Apr 2019 02:16: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: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:84:"Post Status: “Become the best version of yourself.” An Interview with Rich Tabor";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=60141";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:52:"https://poststatus.com/an-interview-with-rich-tabor/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5043:"Rich Tabor is transitioning to a new role now as Senior Product Manager of WordPress Experience with GoDaddy. In the past three years, Rich founded a digital agency, launched a popular PhotoShop resource site, and started ThemeBeans, a successful WordPress theme shop.
\n\n\n\nThemeBeans and CoBlocks, Rich’s suite of page builder blocks in a plugin, have gone with him to Godaddy. (CoBlocks remains free, and now all the ThemeBeans products are too.) Rich took some time to reflect with us on his path so far and where he sees the WordPress ecosystem going in the future.
\n\n\n\nQ: What led you to dive into the new post-Gutenberg reality of WordPress and create CoBlocks and Block Gallery?
\n\n\n\nI’ve been fascinated by the block editor ever since Matias’s Gutenberg demo during WordCamp US 2017. I was instantly convinced that Gutenberg would lead us into the next era of creation in WordPress. I saw an opportunity, was in a position to execute and had enough expertise to take it on.
\n\n\n\nQ: Did sales for these products meet your expectations?
I actually did not release paid versions for either CoBlocks or Block Gallery. There were plans to monetize both plugins, but at the time we were focused on delivering innovative solutions to Gutenberg and pushing the editor to its extremes. Adoption-wise, both plugins grew particularly fast, and are continuing to do so. In that sense, they most certainly exceeded my expectations.
\n\n\n\nQ: What do you see as the near and long term future of the WordPress ecosystem? As solo developers and small firms are increasingly hired by bigger fish, especially hosting companies, will there still be a place for small entrepreneurs?
I believe that the WordPress ecosystem will continue to be an innovative field for both entrepreneurs and larger companies. It’s all about innovation and being able to execute — regardless of the size of the team behind the product or idea.
And over the last few years, the WordPress economy and its entrepreneurial leaders, have evolved into quite a mature ecosystem. I’d say the fact that companies such as GoDaddy are investing in the future of WordPress is a huge sign of that maturity and growth in our industry. Hosts, in particular, are uniquely equipped to make a huge difference in how so many folks use WordPress. Investing in products and talent that level-up the overall WordPress experience is good for us all.
\n\n\n\nQ: What about GoDaddy made it seem like a good fit or you? Did you consider any other types of companies outside the hosting space?
I flew out to Phoenix to meet the WordPress leadership team at GoDaddy and it became quite clear that they were all-in on this new future of WordPress + Gutenberg.
GoDaddy has assembled a passionate and highly qualified team of folks who are hyper-focused on improving the WordPress experience and leading the next wave of innovation in this space. Joining this team and leading the efforts as the Senior Product Manager of WordPress Experience is a good and logical fit to fulfilling my personal mission to help make WordPress beautifully simpler. I knew that what we’d build would touch millions of sites and empower people all over the world to succeed online.
\n\n\n\nQ: Before GoDaddy came along, what was your plan in terms of growth and long-term sustainability?
Having run a successful theme shop for a number of years, I understood the importance of having a solid plan for growth and sustainability.
My plan for both CoBlocks and Block Gallery was to release top-tiered paid versions of each, with innovative tools, blocks and design systems. Those would have likely arrived in Q3 of 2019, as our focus for the first half of the year was to innovate and grow our user base. Now I hope to continue on that same development trajectory, adding many of those same features to the current plugins.
\n\n\n\nQ: What is your best advice for someone who is currently independent and wants to build a small business in the WordPress space today? What are the best lessons or advice you can provide?
First off, don’t let an opportunity get away from you. Learn to identify opportunities that you are perfectly suited to execute on, then dive right in. Don’t hesitate to ask for help and don’t be afraid to try something new. Learning how to learn and then taking that a step further by continuing to learn every single day, is a catalyst for enormous personal and professional growth. It’s not all about making cool stuff, it’s about challenging yourself to become the best version of yourself; the rest will fall into place.
Dashicons, the WordPress admin icon font, will be getting its first update in three years when WordPress 5.2 ships. The library will be updated to use WOFF2 (Web Open Font Format 2), replacing the previous WOFF 1.0 format for improved compression. WOFF 1.0 will still be included in core to maintain backwards compatibility.
\nIn addition to the new font file format, Dashicons is adding 13 new icons to the library and CSS declarations for 18 icons that were previously unavailable. The additions span a range of categories, including Buddicons, Core Teams, sites, menus, social, and miscellaneous.
\nNate Allen, a Senior Web Engineer at 10up, is a new contributor to the Dashicons library, even though he is not a designer.
\n“WordPress has had a ‘businessman’ dashicon for as long as I can remember, but didn’t have a female or gender neutral version – until now!” Allen said.
\n“Previously I worked for Firefly Partners, an agency that builds WordPress sites for nonprofits. I was working on a project for a woman’s rights organization that needed a ‘staff’ post type. It was a little awkward explaining to them that there was a ‘businessman’ icon we could use for free, or they could pay extra to have a custom ‘businesswoman’ icon designed. Not a great look for WordPress.”
\nAllen submitted a GitHub issue, to see if someone would be willing to create a “businesswoman” and “businessperson” icon, but nobody had the time. Dashicons is maintained by a volunteer team and it can take a long time to get new icons designed.
\n“About 5-6 months later I learned how to use Illustrator to create vector icons and submitted the icons myself,” Allen said. He submitted the PR and the new icons he created will be included in the next release of WordPress.
\n\nThese business people icons are useful for projects that include creating things like custom post types for bios, testimonials, team members, and job postings. WordPress 5.2’s updates to Dashicons make the library more inclusive and useful for more diverse projects.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 19 Apr 2019 02:05: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:8;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:93:"WPTavern: WooCommerce 3.6 Released with New Product Blocks and Major Performance Improvements";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88913";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:104:"https://wptavern.com/woocommerce-3-6-released-with-new-product-blocks-and-major-performance-improvements";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3374:"WooCommerce 3.6 was released this week after six months in development. Store owners with sites running on WordPress 5.0+ will now have access to eight new product blocks, including hand picked products, featured products, products by category/attribute, sale products, new products, top rated, products, and best selling products.
\n\nThese blocks were previously available as a feature plugin but have now been rolled into WooCommerce core. The plugin now requires WooCommerce 3.6 and will continue to be used for iterating and exploring future WooCommerce block editor features.
\nPerformance improvements were one of the major focuses for this version, which introduces product data lookup tables. WooCommerce core developers’ long term plan is to move post meta to custom tables and a feature plugin is currently in development towards this goal. In the meantime, lookup tables provide a structured index for product data that speeds up querying. This version also brings improvements to transient invalidation, changes to REST API initialization, caching improvements, and more.
\nWooCommerce developer Timmy Crawford highlighted a few frontend performance improvements in the 3.6 release post:
\nThis release also includes the controversial new marketplace suggestions that advertise official extensions inside the WooCommerce admin. The setting for turning them off can be found under the “Accounts & Privacy” section of the admin.
\nFor the full list of additional enhancements in 3.6, check out the release post or view the plugin’s changelog. The release should be backwards compatible with sites running WooCommerce 3.0+, but testing how the update affects themes and extensions is highly recommended before updating. Version 3.6.1 was released today to fix some issues 3.6.0 had with certain hosting environments.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Apr 2019 19:31:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:69:"WPTavern: Gutenberg 5.5 Adds New Group Block for Nesting Child 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=88886";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/gutenberg-5-5-adds-new-group-block-for-nesting-child-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:3822:"Gutenberg 5.5 was released with the long-awaited Group block, previously known as the Section block. It was renamed to avoid confusion with the HTML5 section element and prevent potential overlap with future site/theme type sections, such as headers, sidebars, and footers. The first iteration of the Group block supports the ability to nest other blocks inside it and the ability to align the block and any of its child blocks that include alignment settings.
\n\n“It’s a minimal version at the moment and improvements about the flows to add inner blocks, group/ungroup blocks are expected in follow-up releases,” Gutenberg phase 2 technical lead Riad Benguella said. In testing the feature I found that it is indeed a rocky start and far from intuitive to use but a more refined grouping experience will be developed after further testing and feedback.
\nThe Group block lays the foundation for a future where WordPress themes may evolve to become block templates. In response to a comment about how the Group block could essentially replace the widget management interface, Benguella offered a glimpse of how Gutenberg will eventually transform the theme industry:
\n\nIn a world where themes are made of block templates instead of php templates, there’s no need for widget areas.
\nThat said, Gutenberg is a huge change for WordPress and its community. With the new blocks concept, Phase 2 is about helping the WordPress community adopt this new concept without completely changing what a theme means in WordPress. We shouldn’t just abandon existing themes and switch into full-site editing without an iterative plan.
\nWe’ll eventually get there where everything is made of block templates and blocks but we need to make smaller steps first and the first one is the ability to use blocks instead of widgets in existing themes.
Gutenberg 5.5 also adds the image fill option and vertical alignment support to the Media and Text blocks.
\n\nThis release also includes a few minor but useful improvements, such as automatically populating the link field when the selected text is an email.
\n\nThe Gutenberg team is also making progress on the new widgets screen with a barebones testing version in place that will allow them to start investigating and tackling technical issues related to this screen. It’s not functional yet but provides a place to further explore the block editor in this context.
\nThe bug fixes included in Gutenberg 5.5 will be in the upcoming WordPress 5.2 release, which was previously targeted for April 30. There is currently a proposal open for pushing it back to May 7, due to the number of open 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 18 Apr 2019 03:00:45 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:139:"HeroPress: Building Stability With WordPress – WordPress এবং স্থিতিশীলতা, বাংলা তে পড়ুন";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2744";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:140:"https://heropress.com/essays/building-stability-with-wordpress/#utm_source=rss&utm_medium=rss&utm_campaign=building-stability-with-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:9488:"এই নিবন্ধটি বাংলায় পাওয়া যায়
\nThis is the first time my real life story is going to be live for the people of the World. Till now I was living my life with my own surroundings, now it will be no more that much of hidden.
\nI am a very simple person from Kolkata, India. I started my career with IBM ACE i.e an IBM education wing, as a Technical Teacher. I used to teach my students several subjects like C,C++, Perl and PHP. Although I was teaching many subjects my focus was in PHP starting from 2003. In the early days of 2009 I came to know about WordPress. From the first few days I was struggling with the Administrative panel and other services.
\nIn 2009 end I decided to step down from my job and started differently. I started development work and also continue teaching the students.
\nI was decided to develop the websites and web applications with the WordPress only, and I got the version called `Carmen` 2.9 which was a relief for me to handle the CMS. I got some help from my students and friends who were engaged in WordPress development at that time. They teach me how I can handle the WordPress more proficient way. I learnt how to develop WordPress themes, started developing the plugins.
\nI started developing the website using WordPress from 2010 onwards. Later on 2014 I started developing WordPress theme for the Themeforest Market place. I also started developing the plugins which helps my development process to run smoothly.
\nMy life started changing from 2010 when I started developing with WordPress. The instability of my life was changed into a stable life, which was beyond my expectation. I was living a good life with my family. What else I can expect from WordPress.
\nApart from developing the Websites and other application, I started my research on how the development process can be more smoother and flexible. I started working on WP CLI to developing the automated process for WordPress. I developed a script that helps developers to install the WordPress flawlessly using WP CLI. My linux knowledge also helped me to write shell scripts. The script can be found in my account at github. I am also trying to get into the easy deployment process with CI/CD for the developers using Bitbucket Pipeline and AWS.
\nI slowly become an expert on the theme approval guidelines of Themeforest Market place. Apart from that I started writing blogs on the various topics related to WordPress. Achieved almost 3K reputation in StackOverflow. Developed Plugins in wordpress.org.
\nEven though I was developed many plugins and theme I never thought of uploading that in wordpress.org. I start realizing that to help many more people in WordPress, wordpress.org will be a better place than StackOverflow.
\nI joined Kolkata WordPress Community who was planning the WordCamp Kolkata, and thankfully they have selected me as a volunteer. Mr Subrata Sarkar( WordPress Core Contributor ) and the team who recognized me and give a huge responsibilities in WordCamp Kolkata 2019. It was again a tremendous experiences with WordPress. Since that was my first WordCamp I tried to fulfill my responsibilities. Become a Volunteer I learnt to be more polite and more decent to the people, make many more friends from different regions and countries.
\nThere are many people who inspired and helped me during my journey, its small tribute to them by mentioning a few : Abhik Goswami, Sneh Sagar Prajapati, Prabhas Chowdhury, Debobrata Debnath, Prosenjit Manna, Sk. Shamim Ullah, Soumit Pal, Subrata Sarkar.
\nBe polite to others. Be friendly to your Juniors and fellow developers. Try to teach them rather pointing to the mistakes. Attend Meetups. Contribute to the Community. Think what new you have done, and what new can be.
\nStay healthy, stay fit with WordPress
\nWordPress র সাথে পরিচয় ২০০৯ এর December এ, শুরু থেকেই ভালো লাগা. Website বা Plugin বানান দিযে কাজ শুরু করি ২০১০ এ. তারপর থেকে শুধু WordPress এই কাজ করে চলেছি . ২০০৯ এ যখ্ন চাকরি ছেড়ে শুধু development র কাজ শুরু করি সাথে পড়ানো ও চলতে থাকে. কিছু Friend আর Student দের help নিয়ে WordPress self learning চলতে থাকে .
\n২০১৪ সাল থেকে themefores এ theme বানান শুরু করি. ধীরে ধীরে আমি আমার সামনে চলার পথ খুজে পাই. আমি themeforest theme approve guideline expert হয়ে উঠি. আমি github এ আমার wpcli experiment করতে থাকি. Automation আমার main target হয়ে ওঠে.
\nStackoverflow ছাড়াও wordpress.org তে plugin তৈরী করি.
\nWordCamp Kolkata 2019 : এখানে volunteering অনেক নতুন মানুষের সাথে আলাপ হয়. বূঝতে পারি Community কে enjoy করতে, জানতে পারি কি করে community কে কি করে return করতে হয়.
আগামী দিনে আমি WordPress র popularity বারিয়ে যেতে চেষ্টা চালিয়ে যাব.
\nThe post Building Stability With WordPress – WordPress এবং স্থিতিশীলতা, বাংলা তে পড়ুন appeared first on HeroPress.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 17 Apr 2019 12:00:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Tristup Ghosh";s: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:127:"WPTavern: PluginVulnerabilities.com is Protesting WordPress.org Support Forum Moderators by Publishing Zero-Day Vulnerabilities";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88854";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:138:"https://wptavern.com/pluginvulnerabilities-com-is-protesting-wordpress-org-support-forum-moderators-by-publishing-zero-day-vulnerabilities";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8257:"image credit: Jason Blackeye\nA security service called Plugin Vulnerabilities, founded by John Grillot, is taking a vigilante approach to addressing grievances against WordPress.org support forum moderators. The company is protesting the moderators’ actions by publishing zero-day vulnerabilities (those for which no patch has been issued) and then attempting to contact the plugin author via the WordPress.org support forums:
\n\nDue to the moderators of the WordPress Support Forum’s continued inappropriate behavior we are full disclosing vulnerabilities in protest until WordPress gets that situation cleaned up, so we are releasing this post and then only trying to notify the developer through the WordPress Support Forum. You can notify the developer of this issue on the forum as well. Hopefully the moderators will finally see the light and clean up their act soon, so these full disclosures will no longer be needed (we hope they end soon).
In the linked incidents cited above, Grillot claims that moderators have deleted his comments, covered up security issues instead of trying to fix them, and promoted certain security companies for fixing hacked sites, among other complaints.
\nIn response, Plugin Vulnerabilities has published a string of vulnerabilities with full disclosure since initiating the protest in September 2018. These posts detail the exact location of the vulnerabilities in the code, along with a proof of concept. The posts are followed up with an attempt to notify the developer through the WordPress.org support forum.
\nGrillot said he hopes to return to Plugin Vulnerabilities’ previous policy of responsible disclosure but will not end the protest until WordPress.org support forum moderators comply with the list of what he outlined as “appropriate behavior.”
\nWordPress’ security leadership is currently going through a transitional period after Aaron Campbell, head of WordPress Ecosystem at GoDaddy, stepped down from his position as head of security in December 2018. Automattic Technical Account Engineer Jake Spurlock is coordinating releases while the next person to wrangle the team is selected. This announcement was made in the #security channel, but Josepha Haden said there are plans for a more public post soon. Campbell did wish to publish the details of why he stepped down but said that he thinks it is important to rotate that role and that “the added influx of fresh energy in that position is really healthy.”
\nWhen asked about the Plugin Vulnerabilities’ protest against WordPress.org, Spurlock referenced the Responsible Disclosure guidelines on WordPress’ Hackerone profile. It includes the following recommendation regarding publishing vulnerabilities:
\n\nGive us a reasonable time to correct the issue before making any information public. We care deeply about security, but as an open-source project, our team is mostly comprised of volunteers.
Spurlock said that since those guidelines are more pertinent to core, dealing with third-party plugins is a trickier scenario. Ideally, the plugin author would be notified first, so they can work with the plugins team to push updates and remove old versions that may contain those vulnerabilities.
\n“The WordPress open-source project is always looking for responsible disclosure of security vulnerabilities,” Spurlock said. “We have a process for disclosing for plugins and for core. Neither of theses processes include posting 0-day exploits.”
\nGrillot did not respond to our request for comment, but the company’s recent blog posts contend that following responsible disclosure in the past would sometimes lead to vulnerabilities being “covered up,” and even at times cause them to go unfixed.
\nWordPress.org support forum moderators do not permit people to report vulnerabilities on the support forums or to engage in discussion regarding vulnerabilities that remain unfixed. The preferred avenue for reporting is to email plugins@wordpress.org so the plugins team can work with authors to patch plugins in a timely way.
\nHowever, in the wild west world of plugins, which includes more than 55,000 hosted on WordPress.org, there are times when responsible disclosure falls apart and occasionally fails users. Responsible disclosure is not a perfect policy, but overall it tends to work better than the alternative. The Plugin Vulnerabilities service even states that they intend to return to responsible disclosure after the protest, essentially recognizing that this policy is the best way to coexist with others in the plugin ecosystem.
\nIn the meantime, publishing zero-day vulnerabilities exposes sites to potential attacks if the plugin author is not immediately available to write a patch. The only thing WordPress.org can do is remove the plugin temporarily until a fix can be released. This measure protects new users from downloading vulnerable software but does nothing for users who already have the plugin active. If site owners are going to protect themselves by disabling it until there is a fix, they need to know that the plugin is vulnerable.
\nPlugin Vulnerabilities’ controversial protest, which some might even call unethical, may not be the most inspired catalyst for improving WordPress.org’s approach to security. It is a symptom of a larger issue. WordPress needs strong, visible security leadership and a team with dedicated resources for improving the plugin ecosystem. Plugin authors need a better notification system for advising users of important security updates inside the WordPress admin. Most users are not subscribed to industry blogs and security services – they depend on WordPress to let them know when an update is important. Refining the infrastructure available to plugin developers and creating a more streamlined security flow is critical for repairing the plugin ecosystem’s reputation.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 17 Apr 2019 03:37:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:99:"WPTavern: WordCamp for Publishers is Coming to Columbus, OH, August 7-9, Call for Speakers Now Open";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88366";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:107:"https://wptavern.com/wordcamp-for-publishers-is-coming-to-columbus-oh-august-7-9-call-for-speakers-now-open";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2696:"The third edition of WordCamp for Publishers will be held in Columbus, OH, August 7-9, 2019, at the Vue Columbus. This unique event is a niche-specific WordCamp for professionals working in the publishing industry. Previous locations include Denver and Chicago. In looking for a host city for 2019, organizers had a preference for cities that are “underrepresented media markets” where attendees may not see as many of these types of events. Columbus certainly fits the bill.
\nThe call for speakers and workshop facilitators is now open. Organizers are looking for presentations from all types of professionals across the publishing industry, including writers, journalists, editors, designers, developers, data journalists, project managers, product managers, and program managers. The event will feature three types of sessions:
\nApplicants may submit up to three proposals until the deadline on Monday, May 6th at 11:59 EDT.
\nLast year’s event brought controversial and thought-provoking presentations, such as “Why we ditched AMP, and other UX choices we made for launching membership” and “Reader revenue and the less open web,” an interesting exploration of the implications of paywalls on the open web. All 2018 presentations are available on WordPress.tv, if speaker applicants need any ideas about the types of presentations that are relevant to the event. Last year’s theme was “Taking Back the Open Web,” but organizers have not yet announced a theme for 2019.
\nThe first batch of tickets is already on sale. Previous years have sold out fairly fast, so make sure to follow @wcpublishers on Twitter for all the latest information.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 15 Apr 2019 22:50:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:41:"Matt: Happy Tools, for the Future of Work";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=49336";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:34:"https://ma.tt/2019/04/happy-tools/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2372:"Distributed work is becoming a reality for more companies. Automattic has been operating in a distributed-first fashion for more than 13 years now — we’re now up to more than 850 employees in 68 countries. But even in companies with physical offices, more employees are distributed around the globe and working together. Google just shared some fascinating stats about its work culture, with 100,000 employees working across 150 cities. Two out of five work groups have employees working from more than one location:
\n\n\n\n\n\n\n\nWe’re a more connected world, so it makes sense that global business wouldn’t be confined to just one physical space. I often use Google as an example because I’ve been in meetings there where people were one building away from each other but still using video chat because of the time required to walk between meetings on their campus.
\n\n\n\nWith that in mind, the team at Automattic has decided to start sharing our expertise and the technology that makes it all work. Introducing Happy Tools:
\n\n\n\n \n\n\n\nOur first product is Happy Schedule, which helps teams manage flexible schedules across time zones. Right now we’re rolling it out in a consultative way with just a few early customers to make sure the team can be totally responsive to their needs. We’re excited about this and other upcoming tools, because we believe that this is the future of work. We’re excited to have other companies give it a try.
\n\n\n\nKeep an eye on this space: There’s an entire suite of tools that make up the operating system of what has helped Automattic scale so effectively over the years. I’ve always believed it’s important to invest in your internal tools, and I’m excited to release more of them. If there’s something better in the market, we won’t release a tool for it—I’d rather use something external than have to build things ourselves—but where the industry still has a gap after such a long time, we’ll throw our hat into the ring.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 15 Apr 2019 19:54:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:97:"WPTavern: WordCamp Europe Publishes 2019 Speaker Lineup, Contributor Day Registration is Now Open";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88804";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:107:"https://wptavern.com/wordcamp-europe-publishes-2019-speaker-lineup-contributor-day-registration-is-now-open";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2135:"WordCamp Europe 2019 is 66 days away. The event will be held in Berlin on June 20-22, occupying 13,000m² of the Estrel Congress Center. More than 2,266 tickets have been sold so far, roughly 100 tickets short of what the event sold last year.
\nAll 59 speakers have now been announced and the schedule is published on the website. Organizers added a third track this year to accommodate the various lightning and traditional talks, workshops, and panels.
\nWordCamp Europe received a record-breaking number of submissions and applicants this year after making a stronger effort to improve representation of the diversity of the WordPress’ community. Organizers received 453 submissions from 267 applicants, a 20 percent increase over 2018 submissions. Approximately 1% (4 applicants) identified outside of the gender binary, 34% were female, and 65% male. The breakdown for 2019 selected speakers is 43.4% female and 56.6% male.
\nContributor Day registration opened today and will close May 31, 2019. The event will take place on June 20, one the day before the main conference in the same venue. Organizers have build a new Contributor Orientation Tool to help new contributors identify one or more of the Make WordPress teams where they can apply their skills. Tickets are free for WCEU attendees but spots are limited. There were only 157 Contributor Day tickets remaining this morning and those places are going quickly.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 15 Apr 2019 16:33: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: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:40:"WordPress.org blog: WordPress 5.2 Beta 3";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=6885";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2019/04/wordpress-5-2-beta-3/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3784:"WordPress 5.2 Beta 3 is now available!
\n\n\n\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
\n\n\n\nThere are two ways to test the latest WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).
\n\n\n\nWordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 2, nearly 40 tickets have been closed since then. Here are the major changes and bug fixes:
\n\n\n\nImportant reminder: as of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.
\n\n\n\n \n\n\n\nWordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages! The beta 3 release also marks the soft string freeze point of the 5.2 release schedule.
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nWould you look at that
each day brings release closer
test to be ready.
Quirk is a new GPL-licensed Cognitive Behavioral Therapy (CBT) app for iOS and Android built in React Native/Expo. The app helps users challenge their “automatic thoughts,” a term that refers to thoughts that come to a person spontaneously in response to a trigger, which can often be negative.
\nQuirk lets users record a quick thought and will automatically narrow down a list of potential ways these thoughts are distorted. The distortions were inspired by the ones popularized in Feeling Good: The New Mood Therapy. The user is then invited to challenge those distortions and write an alternative thought.
\n\nEvan Conrad, a software engineer at Segment, created Quirk as a non-commercial, personal project to make it easy for people to take control of their irrational thoughts using a common CBT technique. Quirk is not a substitute for a trained therapist but rather a tool for people to use on their own. Left unchecked, negative automatic thoughts can become emotional weights and lead to distorted thinking. Quirk is a simple app that helps people experience the world in a less negative way and develop more rational thinking patterns.
\n“It’s super useful for day-to-day stuff,” Conrad said in response to comments on Hacker News. “Take a thought like ‘I took too many hints in that interview question.’
\n“That thought might lead to ‘I must have failed that interview,’ which leads to ‘I’ll fail all the rest of my interviews,’ which leads to ‘I’ll never get another job,’ which leads to ‘I must be really bad at this, I should just give up.’
\n“Each step seemed kind of logical at the time, but one thought led to the next and now you feel awful.
\n“CBT is a counter measure to this; it stops you at that first point and gives you a bunch of common logical fallacies that help you recognize why your thought is overreaching. You don’t know if you really flunked that interview, besides flunking one is good practice to pass the next one.”
\nConrad said these types of thought processes aren’t exactly a mental health issue but are common struggles for many people. Quirk can be a useful tool for anyone looking to recognize and remove their own cognitive biases.
\nThe iOS version of the app currently works better than the Android one, as the author said he doesn’t have an Android phone and finds it difficult to support the app on that platform. However, fixes are being pushed out regularly and many of the issues with crashing are getting resolved.
\nThe code for Quirk can be found on GitHub and is open source under the GPL-3.0, which is not a popular choice for licensing mobile apps. I asked Conrad why he opted for the GPL license, as opposed to other popular open source licenses.
\n“Mental Health tech is a really weird world,” Conrad said. “There’s a lot of folks who want to do the right thing, but end up doing really sketchy stuff.
\n“For example, a lot of apps collect the thoughts you’re recording for ML (Machine Learning) or NLP (Natural Language Processing). The stated purpose of this is to help better identify suicide, depression, etc. Partially because of the subject matter, many apps aren’t clearly telling their users that this is happening.
\n“So what ends up happening is a bunch of well intended researchers get access to your most sensitive thoughts. Which is fine, but they frequently aren’t aware of how valuable of a target they’re holding to a nefarious actor. Because it’s not like a database of passwords or credit card numbers, they tend to not think about security.
\n“But thoughts are super valuable and dangerous for abusers and blackmailers; plus most people would rather give you their password in plaintext than show you their mental health thoughts.
\n“So if I made Quirk MIT, I would worry that someone would take Quirk and launch their own version for research that tracks and stores user thoughts. Because the license doesn’t follow them, they could do it without telling a user and there would be little way for an average person to /know/ that this is happening.”
\nConrad has taken an inspiring, user-centric approach to licensing and privacy that ensures users of his app (and any derivatives) will have access to the code and a better understanding of where their data is being stored. In a recent Twitter thread, he outlined the privacy principles that underpin Quirk’s architecture:
\n\nIn Quirk, FOSS and privacy isn’t a focus, it’s a given. Outside the tech world, Quirk is not trying to be a FOSS CBT app, it’s trying to be a really good CBT app that happens to be FOSS. It’s not coming out and saying “hey we don’t store your deepest darkest secrets on some server somewhere.” User’s don’t care. It’s a given. It doesn’t store things on the device because it’s trying to sell you on privacy, it does it because it’s the correct engineering decision.
\nRegular people don’t look at the Golden Gate bridge and think about the structural quality of the bolts. They pull out their phones and take a picture. The responsibility of software is to make things frictionless and reduce the stuff someone has to think about before buying in.
Conrad said he would like to see other developers build things using the app and conduct research, as long as they do so ethically. The project’s GitHub repo has a detailed writeup of its design and engineering logic. It includes specific goals the code was built around in order to respect users’ privacy and mental health, such as:
\n“I really do want to see people use Quirk for research,” he said. “I just want it to follow more ethical practices of consent and data security. Someone should willingly give a researcher their thoughts and as little information should be given about the person as possible. When it’s stored, it should be stored safely and not on a publicly exposed DB for example. But for that to happen, it has to be open.”
\nBeyond GPL-specific licensing, making the app open source has many other benefits. Quirk has already been translated into six different languages. One of the byproducts of making a useful app open source is that it energizes contributors and speeds up the process of bringing the app to new audiences.
\n\n\n\nI cannot express how absolutely amazing it is that Quirk was translated into 6 languages in just a few days.
\n— Evan Conrad (@flaqueEau) April 10, 2019
Feedback on the app so far has been mostly positive. One commenter on Hacker News thanked Conrad for open sourcing the app because he wasn’t able to continue in-person CBT due to the cost:
\n\nI’ve been through CBT and stopped because of the cost. I feel that an app like this can complement those of us that have had face to face time but stopped for whatever reason.
Quirk is an inspiring example of how open source software can help people with every day problems. Its carefully-considered implementation respects users’ sensitive information and doesn’t encourage an unhealthy attachment to the app.
\nIf you like Quirk and want to contribute, you can find the app on GitHub, including directions for translating it into different languages. Mental health professionals who want to contribute are encouraged to audit the descriptions of the cognitive distortions. Users can report bugs as GitHub issues or directly to the app’s creator via email to Humans @ usequirk.com.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 12 Apr 2019 20:06:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:108:"WPTavern: WPGraphQL Project Gains Momentum with Growing Library of Extensions for Popular WordPress Projects";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88737";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:119:"https://wptavern.com/wpgraphql-project-gains-momentum-with-growing-library-of-extensions-for-popular-wordpress-projects";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5898:"The WPGraphQL project, a plugin that provides an extendable GraphQL schema and API for WordPress sites, has been gaining momentum over the past several months. Creator and maintainer Jason Bahl put the project up on Open Collective last week after people frequently asked how the community can support the project. WPGraphQL already has five backers, an $800 balance, and an estimated annual budget of $2,687.
\n“Large well-known sites such as qz.com and theplayerstribune.com are in production with JavaScript front-ends that consume data from WordPress via WPGraphQL,” Bahl said. “PostLight Studio maintains a popular “Headless WP Starter” project that initially started as a React + REST API boilerplate, but recently added WPGraphQL support as well.”
\nOne of the most important signs of the project’s growth are the extensions that developers are building on top of it, such as WPGraphQL for Yoast SEO, WPGraphQL for Gutenberg, and WPGraphQL Content Blocks. WPGraphQL for Advanced Custom Fields is getting very close to an initial release and Caldera Forms is also exploring integrations with WPGraphQL.
\n“The two most-searched things on WPGraphQL.com are “Advanced Custom Fields” and “WooCommerce,” Bahl said. “People are interested in using WPGraphQL with other popular WordPress projects, and WPGraphQL for WooCommerce is a reaction to the folks that are already looking for alternatives to the WooCommerce REST API.”
\nWPGraphQL for WooCommerce is an extension created by Geoffry Taylor that has started to gain some traction. Taylor is a core contributor to the main WPGraphQL plugin. He has just published a Kickstarter to help fund development of the extension and Bahl is consulting with him on implementation details and code reviews.
\nTaylor began contributing to the WPGraphQL project last year after discovering the repository and finding that it lacked the features he needed.
\n“I was looking for a solution that would allow me to create React-Apollo JS apps that could be used as WordPress themes,” he said. “And the solution couldn’t rely on a node server, because a large portion of my clients use shared hosting. WPGraphQL was a perfect fit for what I needed, but it lacked the features I needed at the time. This led to me contributing.”
\nSince then Taylor has also created other libraries and tools that work directly or indirectly with WPGraphQL, such as WPGraphQL Composer, a React-Apollo component library, and Oil-Based Boilerplate, a boilerplate for developing React-powered WordPress themes, plugins, and guten-blocks that use shared components.
\nTaylor is seeking $15K in funding for development of the WPGraphQL WooCommerce extension, which would enable him to apply 100% of his time to the project.
\n“The question I think a lot of people have, is what does this extension provide that WPGraphQL and WooCommerce doesn’t already?” Taylor said. “It adds WooCommerce support to the WPGraphQL server. It is being designed to match and increase the functionality of WooCommerce REST to make it as easy as possible to convert your app from the WooCommerce REST API.”
\nTaylor said the extension is past the initial explorations and is well into development. If a developer follows the instructions in the README they will be able to query products and their variations, coupons, orders, refunds, customer information, and (after the next update), order items from the WPGraphQL endpoint. He said that with the exception of products, none of the data is queryable for any user without shop-manager level capabilities.
\n“Customer-level functionality is the target goal right now, meaning customers can register/login, update the cart, and checkout,” Taylor said.
\nAnyone interested can follow the project’s progress on GitHub or get involved on Slack at wp-graphql.slack.com in the #woocommerce channel.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 11 Apr 2019 22:49:14 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:81:"WPTavern: WordSesh Returns May 22, 2019, Speaker Application Deadline is April 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=88047";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordsesh-returns-may-22-2019-speaker-application-deadline-is-april-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:1978:"The next edition of WordSesh is scheduled for Wednesday, May 22, 2019, from 10am-8pm EDT (UTC-4) – just a little over one month away. For the past six years, the virtual conference for WordPress professionals has consistently delivered high quality sessions from industry experts. Last year’s event inspired viewing parties across the globe in Belgium, Nigeria, India, and the USA. The event has been so successful that its organizers also created a WooCommerce-focused edition called WooSesh, which was held last year as an alternative to WooConf.
\nSpeaker applications are still open but will close soon on Friday, April 19. Organizers expect applicants to submit original talks that do not already exist online. The process is somewhat competitive, as only 10 speakers will be selected for the event. Those with approved applications will receive two coaching and review sessions for their talks and a $250 stipend. WordSesh organizers plan to notify applicants of their status by Monday, April 29, and will announce the accepted speakers May 1. Applicants may submit two different presentation topics and are also encouraged to record a two-minute video pitch to sell their ideas.
\nAll WordSesh presentations will be recorded and available online after the live event. Previous years’ sessions and interviews can be viewed on the WordSesh Youtube channel. For more information on applying to speak, check out the event’s 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:"Thu, 11 Apr 2019 04:02:46 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:113:"WPTavern: WooCommerce 3.6 RC2 Removes Marketplace Suggestions from Product Listing, Adds Setting to Turn them Off";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88702";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:123:"https://wptavern.com/woocommerce-3-6-rc2-removes-marketplace-suggestions-from-product-listing-adds-setting-to-turn-them-off";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4906:"WooCommerce 3.6 RC2 was released today with changes to the planned Marketplace Suggestions feature after core developers received overwhelmingly negative feedback on its implementation. This RC removes the ads from the product listings, which was one of the most controversial placements for them. It also adds a new setting to turn Marketplace Suggestions off entirely.
\nFor many WooCommerce developers, 3.6 RC1 was the first time they discovered the marketplace suggestions. Some even felt blindsided by the original implementation.
\n“Last week, the release candidate was running on my staging server, and out of nowhere, I noticed these ads being inserted inline with the rest of the WC admin list tables,” Tobin Fekkes said. “What a shock that was! I thought I’d developed a bad case of malware or something. What nasty plugin was corrupting my core, default products table, order table, etc?! Oh, just core WooCommerce.
\n“I have never once gone looking to add a plugin to my site by starting at the ‘Products’ tab. Because it doesn’t belong there. If I want to install an extension or plugin, I will go to the (aptly named) ‘Extensions’ tab or “Plugins” tab.
\n“It is rather telling that we as longtime developers who attend every Dev chat, bookmark and check this Dev blog daily, and test all your betas and release candidates STILL had no idea about this blatant abuse of trust.”
\nTodd Wilkens, Head of WooCommerce, addressed the issue of marketplace suggestions seeming to come out of nowhere in a comment on our recent post:
\n\nWe are committed to working with our community, including the plugin review team, and responding to feedback. Just as a reminder, the Marketplace Suggestions feature was developed in the open in a long-running feature branch/PR which was merged to master a month ago. It was mentioned in the Beta 1 Release notes, and was testable during Beta1 and prior on master.
\nIt is often only when the release candidate comes out that we get certain kinds of feedback. It’s an important stage in the development cycle when we want and expect input. With the 3.6 RC1 live, we received specific feedback that we could take into consideration and act on. Thanks to the developers, end users, and the plugin review team for all their help.
WooCommerce 3.6 RC2 doesn’t make any changes to the frequency with which users will need to dismiss the ads. Some have commented that it is more like “snoozing” the ads, since they require dismissal every day for five days, only to return every month thereafter.
\n“We continue to be in contact with the plugin review team to ensure the suggestions are in accordance with the guidelines,” Wilkens said. “There is a live conversation on the definition of suggestion/advert dismissibility. We will participate in that conversation and honor the outcomes.”
\nAs this implementation of marketplace suggestions still is not satisfactory to many WooCommerce users and developers, a plugin for turning off has already been submitted and approved in the WordPress plugin directory. WooCommerce Without Marketplace Suggestions removes the suggestions permanently without users having to continually dismiss them.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 10 Apr 2019 20:18:49 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:39:"HeroPress: Firefighter to Web Developer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2735";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:130:"https://heropress.com/essays/firefighter-to-web-developer/#utm_source=rss&utm_medium=rss&utm_campaign=firefighter-to-web-developer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:13123:"I’m jolted awake to the sound of the tones going off in my room. I knew that I hadn’t been asleep long because we’d already run a late call and it was still dark outside. Running to the truck, I hear the address come out over the radio for a medical call. It’s the third time this week we’ve been called to the same house.
\nMy driving is on autopilot because I know the city streets like the back of my hand. Not only had I worked in the same fire department for the last 6 years, but I’d also grown up in this city. On this and many other times I’d been woken up in the middle of the night, I’m starting to realize that I’m losing my passion for the job I once loved.
\nAt 19 years old I was working in fast food, and I knew I needed to do something more with my life. I wasn’t really keen on going to college just yet, so I started looking for jobs that only needed vocational school. Knowing that I wouldn’t be a very good police officer, I signed up for fire school.
\nDuring fire school I found the only way to get a job as a firefighter in Florida was to also be an EMT in order to run medical calls, so I enrolled in there as well. While I was in school, one of the instructors I met told me their department was taking on volunteers.
\n\nSix years in the field, a year of paramedic school, and many sleepless nights later, I’m driving to a call feeling trapped in a career that I don’t care for anymore.
One of the perks of being a firefighter is that in between calls the free time is ours to do what we like, we just need to be ready to leave at a moment’s notice. Some of the time we watch movies and play video games, but I wanted that time to do something productive that I could turn into an opportunity for a side gig.
\nI stumbled across a YouTube video that demonstrated how to create a webpage with HTML. I loaded a page that stereotypically read “Hello World” and I was hooked. I didn’t even own a computer at this time in my life, but my wife had a MacBook Air. She was nice enough to let me borrow it so I could keep learning. Downloading a text editor, I started creating web pages and loading them up in a browser. Though, as I was creating these pages, it was pretty obvious there weren’t any live websites out there that looked as bad as what I was creating.
\nWhile going through YouTube looking for more tutorials, I kept seeing videos for this thing called WordPress in the sidebar. Curiosity got the better of me and I clicked on one of the videos. I saw how pages were being created from an admin background and how themes changed the look of sites, while plugins added functionality. I was completely blown away.
\nBy this time, I had purchased a $250 Chromebook I was running Linux from, and I decided that I was going to run a local development environment on this little computer with a 16GB hard drive. I managed to succeed, and with each accomplishment I had, I found that I was becoming extremely passionate about building these little websites.
\nI knew that I wasn’t going to make it very far past the beginning stages without help from someone other than a search engine. Though without any knowledge of the community and how they would act towards me, going to a local meetup was something that made me very uncomfortable. I thought the second they caught a glimpse of my Chromebook and my silly beginner questions they’d have me out the door before I could sit down.
\n\nEven in the parking lot before my first meetup, I was sitting in my car telling myself that I should just drive home.
When I walked into the meetup I was surprised to find people in all stages of their growth with WordPress. There were even people that knew less than me, and they were accepted just as much as I was. It was there I learned about this event called a WordCamp. I knew that whatever it was, I needed to be there and it was only two months away.
\nSitting in my car in front of my first WordCamp Orlando, I felt the same feelings that I did before my first meetup. I reminded myself how welcoming the meetup was, and that this wasn’t going to be any different. When I grabbed my seat in the main auditorium, I started feeling pretty strongly that I was alone in a room of 300 people. There were business owners that could actually make money off WordPress, and it felt that there weren’t many people at my experience level. As I went from talk to talk, the topics flew over my head and I became very overwhelmed. I told myself that I was going to stick it out till lunch and that I could go home after if I wanted.
\nLunch came and as I was walking around looking for a good place to sit, I noticed a familiar face sitting at a table with no one next to him. Up until now, I had been learning exclusively at Lynda.com and Treehouse. I was learning to use the Genesis Framework and took a couple courses by an instructor named Jesse Petersen, and this guy looked just like him. Walking up next to him I said: “I’m sure you’ve heard this before, but you look just like an instructor I learned from on Treehouse.” He laughed and said that he was indeed that instructor from Treehouse.
\nThe pitch of my voice shot up an octave, and I started fanning out over how I had learned so much from him and asked if I could eat with him. While we ate, I told him that I was a firefighter and how I also wanted to become a web developer and build websites. By the end of the lunch, he told me that he saw something in me and that he wanted to mentor me if I was ok with that. Was I ok with that?!? Of course, I was ok with that! I was doing my best to sound cool all the while I’m absolutely ecstatic on the inside.
\nThe rest of the day I followed him around to talks, and while I was listening, he was setting up my computer with tools to help get me set up for further development. He added me to his Slack channel and told me that we were going to be working together remotely. When the day finished he asked me where we were having dinner in between the last session and the after-party.
\n\nI’ve never gone from feeling so out of place somewhere to then feeling so welcomed.
I was talking to a person that had absolutely no gain from helping me out, yet spent the entirety of his day getting me set up to work with him in the future.
\nJesse wasn’t feeling well the next day due to an illness he had called Cystic Fibrosis. He said that he would keep up with me through the day on Slack though. Whenever I felt like I didn’t belong I would look at the tools Jesse had installed on my computer and the Slack channel and would remember that I was welcome. I was going to be learning some awesome stuff, and now I had a mentor.
\nI spent the next few months going to two other WordCamps learning as much as I could and meeting as many people as possible. After going down to WordCamp Miami, I got approached by a local agency owner at a meetup that had some extra work I could help out with. Little did I know, they were also friends with Jesse and he had told them about me and what I’d been learning. This gave me a chance to get my feet wet and build some very strong friendships with some amazing people. I was now making money doing what I loved.
\n\nFour months later I got a Slack message from one of my friends telling me that Jesse had passed away.
I was on shift at the fire department that day, and I felt like someone had hit me with a bat. He was due to get new lungs any time, and just the day before was telling me how he was going to start a new life once he had the strength of new lungs to do so. We were all crushed to hear of his passing. I knew it was going to be hard moving forward without him, but I knew that’s what he would have wanted.
\nI continued working on my skills until I was asked to do a keynote presentation at WordCamp Orlando. The very WordCamp I’d thought about leaving halfway through just a year before. The owner of the agency I was working for, Chris Edwards, told me they’d had a speaker back out and they needed someone to fill in, so they asked me. They wanted me to tell my story of how I had gotten into the WordPress community. I agreed, believing it was only going to a small room full of people, but when I said yes, I was then told I would be giving the opening keynote address in front of the entire WordCamp. I had already said yes, so now there was no way that I could back down and tell him no.
\nAs I was standing on stage waiting to be introduced, I was relieved to find there was a podium. Now no one could see my legs shaking as I stood there for an hour. I could now put all my focus on making sure the hand holding the microphone stayed steady. My talk was on the past year that had led me to this point and all of the fears and vulnerabilities I’d faced. If there was someone that was feeling the way I had a year ago, I wanted them to know that they were welcome and I was excited to have them there.
\nThe rest of the weekend passed, and I got a message from my friend Chris Edwards telling me that a company that makes a donation plugin called Give was looking for a support technician. Matt Cromwell, who was about to be my new boss, was sitting in the audience while I gave my keynote presentation. I filled out the application and got a response back that he wanted to set up an interview.
\nA year has passed since that time, and I’ve grown so much in my knowledge of web development, website management, and WordPress. I’ve just started my first business as a freelance WordPress developer, and again I’m feeling the same fears, excitement, and vulnerabilities I felt every time I started to push myself. It’s now to the point where I almost keep a lookout for the fear because I know that something amazing is going to happen on the other side.
\n\nI’m always going to remember the compassion that Jesse Petersen had for me, and remember to pay that kindness forward in helping others.
There’s no way I could have planned this path for myself even if I’d tried. I know that I’m in the right place now, because every day I wake up I’m happy that I get to work with WordPress and interact with this awesome community. I wouldn’t be anything without the help of those around me, and I will always be grateful for everything they’ve done.
\nThe post Firefighter to Web Developer 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, 10 Apr 2019 12:00:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"Sam Smith";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:84:"WPTavern: GoDaddy Acquires ThemeBeans, CoBlocks, Block Gallery, and Block Unit Tests";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88673";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/godaddy-acquires-themebeans-coblocks-block-gallery-and-block-unit-tests";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4970:"GoDaddy has acquired CoBlocks, ThemeBeans, Block Gallery and Block Unit Tests, one of the leading Gutenberg product lines in the WordPress ecosystem. Founder Rich Tabor is joining GoDaddy as Senior Product Manager of WordPress Experience and will lead a team dedicated to understanding users’ needs and expanding the company’s Gutenberg-related products. Tabor’s fellow CoBlocks founders Jeffrey Carandang and Alex Denning will not be joining GoDaddy.
\nAll the commercial themes in the ThemeBeans catalog are now available for free on GitHub. Current customers will continue to receive theme support and remote updates until April 8, 2020.
\nAccording to Aaron Campbell, GoDaddy’s head of WordPress Ecosystem & Community, CoBlocks will continue to be freely available on WordPress.org. It currently has more than 3,000 active installations and averages a 4.7-star rating.
\n“Nothing will change with the plugin except that it will be added to the GoDaddy account on .org,” Campbell said. “It’s possible it might be renamed or rebranded in the future, but that’s unknown either way at this point. And yes, it will still be on the WordPress.org directory for everyone not just GoDaddy customers (and we plan to add more to it as we develop new blocks).”
\nCampbell could not yet share a roadmap for the plugin as Tabor just started and will be heavily involved in determining the plugin’s future at GoDaddy. Tabor will also be leading a development team that is bringing on more React talent to assist with Gutenberg tasks.
\n“Hiring React devs that are capable with Gutenberg is a newer thing that we’re really not totally sure whether it’ll be difficult or not or even how it’ll look,” Campbell said. “Do you hire WordPress people? React people? Only those that do both? Do you hire both and pair them up to learn from each other? It’s a thing we’re learning in this new post-Gutenberg world.”
\nTabor said he was surprised that his products had attracted GoDaddy’s interest but also found it to be validating of his own efforts and the potential of the block editor.
\n“Throughout my time building themes, and then blocks, I’ve learned the real value of getting eyes on a project: Not only do you get the community rallying behind your ideas, such as the Block Manager recently added in Gutenberg 5.3, but you receive a TON of feedback and inspiration,” Tabor said. “Building on that feedback, consistently delivering clever ideas, and executing on the marketing front with inspiring videos, has landed us in a very opportune position.”
\nGoDaddy has acquired a handful of WordPress companies and services during the past few years (ManageWP, Sucuri, WP Curve), but Tabor’s products are the first Gutenberg-related acquisition for the company.
\n“I think it means that the WordPress ecosystem is important, that it’s maturing, and probably most of all – that it’s moving and changing,” Tabor said. “And I think all of those are good.
\n“Gutenberg has changed a lot in WordPress. It’s not just a new editor or new interface, it’s a whole new system that brings with it a whole new group of challenges. Companies like GoDaddy recognizing this and supporting innovation is a healthy sign of growth and maturity.”
\nGoDaddy’s resources will enable CoBlocks, ThemeBeans, and Block Gallery to move faster and add features that were previously out of reach for Tabor’s small team.
\n“We’ll go from just two developers, to a team of incredibly bright engineers,” Tabor said. “And I won’t be spending time figuring out all the intricacies of monetizing a premium plugin in today’s ever-changing WordPress ecosystem. Instead, I can focus on leading the team’s efforts on bringing a better page building experience to WordPress.”
\nHe will also have access to insights and data that will enable his team to make more informed decisions about the tools and blocks they build.
\n“This view into how entrepreneurs and business owners are using WordPress is something I could never have achieved at a meaningful scale, and I know it will help me move more confidently in the future landscape of Gutenberg,” Tabor said.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 10 Apr 2019 04:15:18 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:40:"WordPress.org blog: WordPress 5.2 Beta 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=6874";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2019/04/wordpress-5-2-beta-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3882:"WordPress 5.2 Beta 2 is now available!
\n\n\n\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
\n\n\n\nThere are two ways to test the WordPress 5.2 beta: try the WordPress Beta Tester plugin (you’ll want to select the “bleeding edge nightlies” option), or you can download the beta here (zip).
\n\n\n\nWordPress 5.2 is slated for release on April 30, and we need your help to get there! Thanks to the testing and feedback from everyone who tried beta 1, nearly 100 tickets have been closed since then. Here are the major changes and bug fixes:
\n\n\n\nwp_body_open()
template tag (and corresponding wp_body_open
action) will let themes (and plugins!) add content right after the <body>
is opened (#12563).As of WordPress 5.2 beta 2, the minimum PHP version that WordPress will require is 5.6.20. If you’re running an older version of PHP, we highly recommend updating it now, before WordPress 5.2 is officially released.
\n\n\n\n \n\n\n\nWordPress 5.2 has lots of refinements to polish the developer experience. To keep up, subscribe to the Make WordPress Core blog and pay special attention to the developers notes for updates on those and other changes that could affect your products.
\n\n\n\nDo you speak a language other than English? Help us translate WordPress into more than 100 languages!
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nThe wonderful thing
about betas, is betas
are wonderful things.
In the wake of last week’s Pipdidg scandal, the WordPress blogger and developer communities have been working together to help the company’s customers get on new themes and ensure the safety of their websites. Pipdig has been reported to various UK and internet authorities and is currently under investigation.
\nPipdig’s hosting provider has proactively disabled malicious code in certain files while the company conducts its own investigation.
\n\n\n\nProps to @kualo, @pipdig''s hosting provider, for stepping in and commenting out (disabling) malicious code. To @pipdig''s WordPress customers: make sure you''re using version 4.9.0 and you''ll be *okay*, for now at least. I still can''t recommend staying with them, though. pic.twitter.com/V0c40A29lL
\n— Nicky Bloor (@nickstadb) April 3, 2019
Meanwhile, Pipdig has been denying customers’ refund requests, in accordance with its “no refund” policy. Customers have received responses from the company claiming that the recent accusations were either “false, twisted, or sensationalized.”
\n\n\n\nAnyone trying to get a refund from Pipdig, this is the reply I got #pipdig pic.twitter.com/sGaysyyVkW
\n— Sophiaaaxo (@sophiatranterxo) April 5, 2019
Customers who have purchased Pipdig products within the last 180 days may still be able to receive a refund through other channels. The Twitter thread below suggests lodging a payment dispute with PayPal or your bank or credit card provider, by referencing consumer protection laws and providing evidence of Pipdig’s false and misleading conduct.
\n\n\n\nExplainer: How to get a refund from @Pipdig. If you have bought the plugin in the last 180 days first email #pipdig asking for a refund. /1
\n— ⓘⓌⓡⓘⓣⓔ (@opinionhacker) April 2, 2019
If you work in WordPress every day, you may not realize how much of a challenge it is for some users to switch themes. WordPress developers and bloggers are stepping up to provide resources to help those who want to transition to a new theme.
\n“I understand that bloggers using Pipdig themes for WordPress might want to switch away, but don’t have the time, money, or skills to do so right away,” Mark Jaquith said. “So here’s P3 Neutraliser — a plugin that will prevent the P3 plugin from updating or ‘phoning home.''” The plugin is available on GitHub with step-by-step instructions for downloading and installing it. It is intended as a stopgap measure for users to activate while they are in the process of transitioning to a new theme.
\nFormer Pipdig customers are struggling to find new themes, as a large number of them fall into the fashion blogger demographic. This is a niche with specific requirements for design and functionality. Many are also confused about the findings in the reports and don’t know how to act on this information.
\n\n\n\nI need to change my theme from Pipdig to another safe one but I''m struggling I''m in love with my Pipdig theme now. However, I do like the 17th Avenue themes. Does anyone know if they''re safe? #pipdig I don''t want to do this all over again in a few months
\n— Melissa (@rosymelissax) April 7, 2019
\n\n\nNot sure what to do i have a pipdig theme for my blog
\n— Erin (@Erin_Louisee) April 3, 2019
\n\n\nSO overwhelmed by all the #pipdig issues I''m reading & don''t understand half of it… Defs time for a theme refresh but no idea where to start. Do I spend ££ designing one with a developer? V confusing for someone who has no coding knowledge at all. Anyone else feeling the same?
\n— Luisa-Christie Ⓥ (@luisachristie) April 3, 2019
Searching WordPress.org for fashion-inspired themes does not turn up many relevant results. Former Pipdig customers hunting for new themes will need a more curated list of recommendations. WordPress developer Tia Wood published a post with a list of both free and commercial alternative themes that may be helpful to those still looking. Freelance designer Rachel Sulek has a Twitter thread with options that are comparable to Pipdig’s theme designs.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 08 Apr 2019 17:49:17 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:74:"WPTavern: Gutenberg Team Publishes RFC Document on Widget-Block Interfaces";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88619";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/gutenberg-team-publishes-rfc-document-on-widget-block-interfaces";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2916:"The Gutenberg team has published a Blocks in Widget Areas RFC (request for comments) document, detailing a technical approach that brings blocks to the wp-admin/widgets.php screen and the Customizer. This is one of the goals on the roadmap Matt Mullenweg outlined in his 9 Projects for 2019 post.
\n\nBased on the requirements outlined in the beginning of the document, it looks like the Gutenberg team is working to make the transition from widgets to blocks as seamless as possible:
\nThe requirements for backwards compatibility are a tall order but will make it much easier for users to trust WordPress during this transition. Content will not be forced into the new interface and users will retain the option to use the classic widget-editing screen if they prefer. The team has not yet announced a date for when widgets will be officially deprecated.
\nGutenberg version 5.4 was released last week with vertical alignment support for the columns block, a playsInline option in the video block, and a number of other minor enhancements. It also contains nearly two dozen bug fixes that will be rolled into the next beta of WordPress 5.2.
\nGutenberg phase 2 technical lead Riad Bengella also confirmed in comments on the release post that the long-awaited section/container block is coming in the next release of the plugin. This will be an important milestone on the journey to full site editing with the block interface.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 08 Apr 2019 04:28: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: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:90:"WPTavern: Jetpack 7.2.1 Removes Promotions for Paid Upgrades from the Plugin Search Screen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88581";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:94:"https://wptavern.com/jetpack-7-2-1-removes-promotions-for-paid-upgrades-from-the-search-screen";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4846:"Earlier this month, Jetpack 7.1 added suggestions to the plugin search screen, a controversial change that has sparked debate this week. When users search for a plugin that matches a term for an existing Jetpack feature, the plugin now inserts an artificial, dismissible search result into the first plugin card slot, identifying the corresponding Jetpack feature.
\nThe Jetpack team said users have a hard time knowing what features are available, with 45 modules packaged into the plugin. The idea behind the proof of concept for the suggestions was to improve the discoverability of Jetpack’s existing features. Many in the developer community became outraged after it was discovered that Jetpack was also advertising paid upgrades in this space as well.
\nThe fact that it was rolled out with promotions for paid upgrades made it seem to many onlookers that the discoverability problem was just a pretext for injecting advertising. The WordPress Plugin Team also said it may or may not be a violation of the plugin directory guidelines but that the team was still “arguing about the semantics internally.”
\nVersion 7.2.1 was released today, removing all feature suggestions that previously advertised upgrades.
\n“We made a mistake, and we’re moving to correct it immediately,” Jetpack team representative Jesse Friedman said. “Our intention with these feature hints is to help you discover helpful features of Jetpack that you already have, right when you need them most. Today we’re correcting an error in judgement that resulted in the hints suggesting Jetpack features that actually required an upgrade.”
\nCharacterizing the mistake as “an error in judgment” is an admission that rolling out feature suggestions with paid upgrades was a conscious decision. One month later, the Jetpack team decided it was a poor choice. This appears to have be driven by the community’s reaction, but Jetpack did not elaborate on how or why they reached the decision to revert the promotions for paid upgrades.
\nThe 7.2.1 maintenance release also changes the design for the feature suggestions, which they are now referring to as “Feature Hints.”
\n“We’re reducing confusion around feature hints by simplifying the design and changing some text; this way it’s clear that feature hints are from Jetpack and are easily dismissible,” Friedman said.
\nAfter updating to the latest release, you can see the revised design on the plugin search screen with new text: “This suggestion was made by Jetpack, the security and performance plugin already installed on your site.” Jetpack will disable the hints once administrators have dismissed three hints.
\n\n“Going forward we want to help create a feature hints solution that works for all WordPress users and plugin developers,” Friedman said. “We are excited to work with suggestions like this one, by Joost de Valk, and see how we might be able to find a solution in WordPress core to help users discover plugin features, and prevent this very common issue. Once a core solution is available, we plan to adopt it for Jetpack.”
\nDevelopers who still do not want to see any sort of feature hint when searching for plugins can use the jetpackcom_remove_search_hints
filter to turn it off. Users can also install the Hide Jetpack Promotions plugin as an alternative.
In one of the most unpopular changes in the history of the WooCommerce open source project, version 3.6 will introduce “Marketplace Suggestions.” The update adds suggestions to the products admin screen, which vary based on whether it’s an empty state or within the list of products.
\n\n“They are contextual mentions of official extensions that may be relevant to a customer,” Todd Wilkens, Head of WooCommerce, said. “This currently includes all extensions on the official WooCommerce marketplace, which is open for submissions and lists extensions written by Automattic as well as by trusted partners and third-party developers.”
\nThe suggestions are on by default for users who can install and activate plugins. They are dismissible, but the frequency with which they will be shown is one of the most contentious aspects of WooCommerce’s proposed implementation:
\nWooCommerce is providing a filter to turn off the suggestions, and this will likely soon be available as a plugin from the community. It is not something that is easy for non-technical store owners to implement.
\nadd_filter( ‘woocommerce_allow_marketplace_suggestions’, ‘__return_false’ );
“If the above removal-by-script option proves to be difficult to implement – for example, for those who are not comfortable adding custom code – we will explore introducing a simpler way to turn them off and include this in a point release (e.g. a toggle in core settings),” Wilkens said.
\nThe feedback coming in on the announcement post and WooCommerce’s GitHub repository is overwhelmingly negative. In a comment on an issue titled “Rethinking 3.6’s Dashboard Ads,” Josh Kohlbach contends that WooCommerce should limit its marketing to the plugin’s dedicated Extensions screen in the dashboard:
\n\nIn addition, didn’t anyone think it might be a conflict of interest for WooCommerce the commercial entity to use WooCommerce the open source plugin to show ads in this manner? Bit anti-competitive to all the 3rd party devs out there (of which there are a lot).
\nWooCommerce already has an amazing page under WooCommerce->Extensions with full searching capabilities etc. Why would you want to show irrelevant ads during a user’s everyday workflow?! Store owners use these screen daily, it’s terrible UX.
\nI suggest that it gets ripped out in its entirety and filed under “cool implementation/fun to code but horrible idea for actual users.
For those who do not stand to benefit from profits from the 400+ extensions on the WooCommerce.com marketplace, the intrusions in the product admins screen seem all the more offensive. Marketplace suggestions have not been well-received by third-party extension developers.
\n“This is in direct competition to every third-party developer that is not selling on WooCommerce’s marketplace,” Jamie Madden, founder of the WC Vendors Marketplace, said. “I am one of these. This is advertising for your commercial products, no matter how you try and wrap this. You have an extensions page already which is more than enough, but advertising your products every 24 hours is going too far. This is completely unacceptable.”
\nThe general consensus of those participating in the ticket is that injecting ads into product management screens will create a disruption to store managers’ workflow.
\n“I too am very concerned about this,” digital agency owner Erik Bernskiold said. “I get that WooCommerce want to benefit from their commercial side, too, and there are many ways to do this. But in this case, it feels like this is at a great disregard for the users. Hijacking a product list, order list or a user interface element in this way is a major interruption of the user experience. It’s not the place for an ad.”
\nSeveral participants in the discussion have suggested that WooCommerce make it an opt-in toggle in the settings.
\n“There is only one scenario where I think this feature should stay in place and could be beneficial: If this feature is controlled by an opt-in toggle in WC settings,” Jeremy Pry said. “Otherwise, this whole feature should be removed entirely. Store owners don’t need advertisements in their admin dashboard. In my opinion, leaving this feature in place would be very harmful to the WooCommerce community.”
\nThe fact that the suggestions cannot actually be dismissed for good is one issue that developers predict will end up aggravating WooCommerce users.
\n“Dismissing just to keep hounding the user, that’s not dismissing… that is snoozing,” WordPress developer Patrick Garman said. “Because I told you 5 times that I don’t want to see your ads, that doesn’t mean come back in a month. The average user shouldn’t have to use a filter to make ads go away.”
\nI would not be surprised if WooCommerce ends up dialing back the frequency of the ads after they are closed, given that nearly all those participating in the conversation consider it unacceptable to require dismissal five days in a row, with the same process repeated every month thereafter. The frequency with which they are displayed is unusually aggressive.
\n“I don’t think it technically violates the guidelines it’s just obnoxious and makes WooCommerce look like a low rent solution,” Astoundify founder Adam Pickering said. “It seems we are in a midst of a monetization push and they are looking for any where they can add up sells. Apparently doing so gracefully has gone out the window.”
\nDespite the overwhelmingly negative feedback, WooCommerce appears to be ploughing forward on its plan to ramp up its marketing in the admin. Automattic is a business and it needs to make money with WooCommerce. Most participants in the discussion do not seem opposed to WooCommerce making money with marketplace suggestions but are strongly requesting that they do not inject ads in places where users are working on their own products in the admin.
\n“There’s nothing necessarily wrong with ya’ll trying to squeeze out some more money from users – so long as it’s done tastefully, and in a way that actually provides value to the user, instead of spamming and hindering them,” @justlevine commented on the GitHub issue.
\nBased on the WooCommerce developer community’s feedback, many are in agreement that they will only support changes will be respectful to store owners working in the admin. They would prefer WooCommerce focused its efforts on improving the existing Extensions tab, instead of injecting items from the marketplace on other screens. The current implementation of marketplace suggestions needs work, because it is too heavy-handed in displaying ads after users indicate through the UI that they want to dismiss them.
\nMost participants in the discussion are in favor of letting store owners decide if they want to see ads for extensions on their product admin screens. They would prefer that users opt in through a more transparent way than simply agreeing to terms of service. At the very least, most prefer WooCommerce add a setting that would allow store owners to easily turn marketplace suggestions off. If Automattic wants this new feature to be successful, the company needs to revise the implementation to be something that doesn’t instantly make the majority of the WooCommerce developer community want to turn it off.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 04 Apr 2019 22:55:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:27;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"WPTavern: WPWeekly Episode 350 – Don’t Touch My Plugin Search Results";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wptavern.com/?p=88558&preview=true&preview_id=88558";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:77:"https://wptavern.com/wpweekly-episode-350-dont-touch-my-plugin-search-results";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1895:"In this episode, John James Jacoby and I discuss a controversial feature in Jetpack 7.1 that adds feature suggestions to plugin search results. We also talk about extension suggestions that are coming to WooCommerce.
\nWe talk about the security implications from the recent investigations into the Pipdig plugin and what users can do about it. Near the end of the show, we send a shout-out to Carole Olinger for her contributions to the WordPress community.
\nJetpack 7.1 Adds Feature Suggestions to Plugin Search Results
\n\nOn Health, WordPress and a Tough Decision
\nNext Episode: Wednesday, April 10th 3:00 P.M. Eastern
\nSubscribe to WordPress Weekly via Itunes
\nSubscribe to WordPress Weekly via RSS
\nSubscribe to WordPress Weekly via Stitcher Radio
\nSubscribe to WordPress Weekly via Google Play
\nListen To Episode #350:
\n
As React (via Gutenberg) becomes more present in the WordPress world, I’m seeing some common themes pop up in conversations about it. I spoke a bit about this kind of thing at WordCamp US last year, but if you don’t feel like sitting through a half hour video, let me summarise my thoughts.
\n\n\n\n \n\n\n\nI agree that React is hard. I strongly disagree with the commonly contrasted view that HTML, CSS, PHP, or vanilla JavaScript are easy. They’re all just as hard to work with as React, sometimes more-so, particularly when having to deal with the exciting world of cross-browser compatibility.
\n\n\n\nThe advantage that PHP has over modern JavaScript development isn’t that it’s easy, or that the tooling is better, or more reliable, or anything like that. The advantage is that it’s familiar. If you’re new to web development, React is just as easy anything else to start with.
\n\n\n\n \n\n\n\nI’m honestly shocked when someone manages to wade through the mess of tooling (even pre-Gutenberg) to contribute to WordPress. It’s such an incomprehensible, thankless, unreliable process, the tenacity of anyone who makes it out the other side should be applauded. That said, this high barrier is unacceptable.
\n\n\n\nI’ve been working in this industry for long enough to have forgotten the number of iterations of my personal development environment I’ve gone through, to get to where I can set up something for myself which isn’t awful. React wasn’t around for all of that time, so that can’t be the reason web development has been hard for as long as I remember. What is, then?
\n\n\n\nOver the past year or so, I’ve been tinkering with a tool to help deal with the difficulties of contributing to WordPress. That tool is called TestPress, it’s getting pretty close to being usable, at least on MacOS. Windows support is a little less reliable, but getting better. If you enjoy tinkering with tools, too, you’re welcome to try out the development version, but it does still has some bugs in it. Feedback and PRs are always welcome! There are some screenshots in this issue that give an idea of what the experience is like, if you’d like to check it out that way.
\n\n\n\nTestPress is not a panacea: at best, it’s an attempt at levelling the playing field a little bit. You shouldn’t need years of experience to build a reliable development environment, that should be the bare minimum we provide.
\n\n\n\nThere’s still a lot of work to do to make web development something that anyone can easily get into. I think React is part of the solution to this, however.
\n\n\n\nReact isn’t without its problems, of course. Modern JavaScript can encourage iteration for the sake of iteration. Certainly, there’s a drive to React-ify All The Things (a trap I’m guilty of falling into, as well). React’s development model is fundamentally different to that of vanilla JavaScript or jQuery, which is why it can seem incomprehensible if you’re already well versed in the old way of doing things: it requires a shift in your mental model of how JavaScript works. This is a hard problem to solve, but it’s not insurmountable.
\n\n\n\nPerhaps a little controversially, I don’t think that React is guilty of causing the web to become less accessible. At worst, it’s continuing the long standing practice of web standards making accessibility an optional extra. Building anything beyond a basic, non-interactive web page with just HTML and CSS will inevitably cause accessibility issues, unless you happen to be familiar with the mystical combinations of accessible tags, or applying aria attributes, or styling your content in just the right way (and none of the wrong ways).
\n\n\n\nReact (or any component-based development system, really) can improve accessibility for everyone, and we’re seeing this with Gutenberg already. By providing a set of base components for plugin and theme authors to use, we can ensure the correct HTML is produced for screen readers to work with. Much like desktop and mobile app developers don’t need to do anything to make their apps accessible (because it’s baked into the APIs they use to build their apps), web developers should have the same experience, regardless of the complexity of the app they’re building.
\n\n\n\nArguing that accessibility needs to be part of the design process is the wrong argument. Accessibility shouldn’t be a consideration, it should be unavoidable.
\n\n\n\nNow, can we do better? Absolutely. There’s always room for improvement. People shouldn’t need to learn React if they don’t want to. They shouldn’t have to deal with the complexities of the WCAG. They should have the freedom to tinker, and the reassurance that they can tinker without breaking everything.
\n\n\n\nThe pre-React web didn’t arrive in its final form, all clean, shiny, and perfect. It took decades of evolution to get there. The post-React web needs some time to evolve, too, but it has the benefit of hindsight: we can compress the decades of evolving into a much shorter time period, provide a fresh start for those who want it, while also providing backwards compatibility with the existing ways of doing things.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 04 Apr 2019 06:31:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Gary";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:148:"WPTavern: Jetpack Is Promoting Paid Upgrades on Plugin Search Screen, WordPress Plugin Team Says it “May be a Violation” of Directory Guidelines";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88485";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:152:"https://wptavern.com/jetpack-is-promoting-paid-upgrades-on-plugin-search-screen-wordpress-plugin-team-says-it-may-be-a-violation-of-directory-guidelines";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8991:"Yesterday the discussion surrounding Jetpack’s implementation of feature suggestions in the plugin search screen became heated after developers pointed out that Automattic is also using these suggestions to promote paid upgrades. You can test this by searching for “backups” where you find that Jetpack’s commercial offering takes the place of the first result, pushing all other results further down one slot.
\n\nThe feature suggestions were added in versions 7.1 to inform users of an existing feature in Jetpack when they search for something similar. The Jetpack team said they developed it to solve a discovery problem, where users are quite often not familiar with all of Jetpack’s 45 modules and end up installing plugins to perform functionality that Jetpack already includes. A PR in the Jetpack repository has been merged to only show feature suggestions when the user’s plan supports it, so it looks like these promotions for commercial features will be removed in a future release of the plugin.
\nIt’s not clear whether Automattic intentionally rolled out the feature suggestions in its current form (with paid upgrades included) to test the waters and gauge the community’s reaction, or if it is simply a mistake. The PR was marked as an enhancement, not a bug.
\nAccording to Plugin Team member Samuel “Otto” Wood, feature suggestions with paid upgrades included is “likely a violation” of the plugin directory’s guidelines.
\n“Promoting other plugins or premium upgrades in the same space would likely not be allowed, because it would be misleading or an incorrect place to put ‘advertising,’ Wood said. “Guidelines already say not to do that.”
\nI contacted the Plugin Team today and it seems the topic of feature suggestions on the plugin screen are still a matter of ongoing debate. The team would not officially confirm whether or not Jetpack is currently in violation.
\n“I can’t confirm that at this time,” Mika Epstein said. “It might be a violation, but it also may not be. Much of that comes down to intent.
\n“A case can be made that they’re promoting paid services for existing features, and is that different from an image-optimizer plugin promoting it’s own service which you’re already using? It’s not like they’re promoting separate plugins, so it’s in a very odd grey area for services.”
\nEpstein said the team is “still arguing the semantics internally about that one.”
\nMany people have asked why Jetpack has not been removed from the plugin directory for advertising its commercial offerings on the plugin screen. The Plugin Team’s official response is that if Jetpack is in violation, they reserve the right to make an exception and opt not to close it. Epstein, on behalf of the team, offered the following statement:
\n\nIt falls under our 18th guideline:
\nWe reserve the right to NOT close a plugin and grant exceptions.
\nClosing plugins is ALWAYS a tricky thing. We regularly warn, and do not close, larger plugins as closing them would have an adverse impact on the entire WordPress community. Closing plugins with 500,000 users can be more harmful than helpful, even when there are security problems. The more users a plugin gets, the more difficult it is to weigh the risks of closing versus not closing.
\nMaintaining the trust in larger plugins is as important as doing so with the directory as a whole. With so many outlets wanting to spin up FUD and blast outrage at everyone involved as their first reaction, we try to stem the tide a little and not act like the sky is falling all the time.
Jetpack has more than 5 million active installs. If it is found to be in violation of the guidelines, it is not likely to be removed due to the impact it would have on millions of WordPress users, not to mention the hosts who have it pre-installed on WordPress hosting plans.
\nThe discussion regarding how WordPress can improve the implementation of feature suggestions on the plugin screen for all plugins is happening in a ticket on trac opened by Joost de Valk. This ticket does not debate whether or not feature suggestions are a good idea in general but rather focuses on how results can better communicate that a feature is already active or available. de Valk shared a screenshot of what the screen currently looks like when a user searches for a plugin for which they already have a match installed:
\n\n“The disabled ‘Active’ button there is not very useful, as it doesn’t provide any context as to why that button is disabled,” de Valk said. “I’d like to propose a change: let’s turn this into two separate groups of results, one that says ‘these plugins you already have installed might be able to help’ and then a second group below that with other plugins.”
\nTim Hengeveld posted a mockup of what an implementation of that might look like:
\n\nThe topic of feature suggestions on this screen is still highly controversial, despite the Plugin Team confirming that it is not breaking the guidelines (as long as plugins don’t promote paid upgrades). Plugin authors have worked for years towards better rankings on this screen by providing quality support and updates that translate into better ratings and more installs. Any mega plugin that offers multiple modules packed into one can easily usurp these rankings by suggesting its own features and having them automatically appear in that top slot. These features could even be broken down into multiple micro-modules so that there is always something to suggest.
\n\n\n\nI make a bit of side income off of https://t.co/aqHIydpjrL
\nALL folks who purchase come from free users of my WordPress(dot)org-hosted plugin.
\nAfter years of hard work, it shows up first in the list when you search for the word "Tweet."
\nUnless you have Jetpack installed. pic.twitter.com/9stTJ4TJre
\n— Ben Meredith-speaking at #WCRaleigh (@benUNC) April 3, 2019
\n\n\nBecause it’s Jetpack and they’ve created this precedence with blessings from .org, it’ll be interesting to see if and how many plugin providers are going to pivot towards Jetpack’s business model of a branded ‘suite’ instead of maintaining separate plugins for separate concerns.
\n— CasparHübinger (@glueckpress) April 3, 2019
Many in the WordPress development community are worried that plugin authors will move towards distributing their work as large suites of modules in order to take advantage of promoting their own features in the plugin search screen. This seems even more likely with block developers releasing massive collections of Gutenberg blocks.
\nWordPress.org is at a crossroads here that may open the floodgates to plugin authors looking to leverage this screen to their own advantage. Jetpack’s move to suggest its own features on this screen, instead of opting for an admin notice or using its own dashboard, is going to have a major ripple effect throughout the plugin ecosystem that has the potential to change how plugins are packaged, distributed, and marketed.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 03 Apr 2019 19:56: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: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:119:"WPTavern: Pipdig Updates P3 Plugin after Reports Expose Vendor Backdoors, Built-in Kill Switch, and Malicious DDoS Code";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88368";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:128:"https://wptavern.com/pipdig-updates-p3-plugin-after-reports-expose-vendor-backdoors-built-in-kill-switch-and-malicious-ddos-code";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:20144:"Over the weekend, Pipdig, a small commercial theme company, has been at the center of a scandal after multiple reports exposed a litany of unethical code additions to its Pipdig Power Pack (P3) plugin.
\nOn Friday, March 29, Wordfence threat analyst Mikey Veenstra published a report with code examples of the backdoors Pipdig built into their plugin, along with some unsavory and questionable additions to the code.
\n“We have confirmed that the plugin, Pipdig Power Pack (or P3), contains code which has been obfuscated with misleading variable names, function names, and comments in order to hide these capabilities,” Veenstra said.
\nThese include an unauthenticated password reset to a hard-coded string, which was deliberately obscured with code comments indicating it was added to “check for new social channels to add to navbar.” Veenstra also demonstrated how the plugin contained code for an unauthenticated database deletion, wherein the Pipdig team could remotely destroy any site WordPress site using the P3 plugin.
\nThe code for remote site deletion was removed in version 4.8.0 but it still a concern for users who haven’t updated. Michael Waterfall, iOS Engineer at ASOS, tested the “kill switch” function and demonstrated that it still works with prior versions.
\n\n\n\nIt also confirms they lied. They _still_ have the ability to wipe any blog that hasn''t updated to the new plugin version (4.8.0), which they hurriedly released to delete the kill switch after they were exposed the other day. pic.twitter.com/bNMfRQUBpr
\n— Michael Waterfall (@mwaterfall) March 31, 2019
Veenstra’s investigation also uncovered questionable remote calls in the plugin’s cron events, undisclosed content and configuration rewrites, and a list of popular plugins that are immediately deactivated when P3 is activated, without the user’s knowledge. He found that some of these plugins are deactivated alongside admin_init, so any user attempts to reactivate the plugins will not stick.
\nWordfence estimates the P3 plugin to have an install base of 10,000-15,000 sites. The changes made in version 4.8.0 of the plugin are not transparently identified in the changelog, so it’s not easy for users to know what has changed. The content filtering and the plugin deactivations remain in the most recent release. These types of veiled functions performed without permission could have unintended consequences on sites using the plugin, which non-technical users may not be able to fix themselves.
\nJem Turner, a freelance web developer based in the UK, published a lengthy analysis of the P3 plugin the same day that Wordfence released its analysis. She drilled down further into the remote requests, demonstrating how Pipdig has been using the P3 plugin to perform a DDoS attack on a competitor who also provides WordPress themes and installation services to bloggers. The code triggers an hourly cron job on users’ sites, effectively using their customers’ servers to send malicious requests to the competitor’s site.
\n\nThe code comment tells us this is “checking the CDN (content delivery network) cache”. It’s not. This is performing a GET request on a file (id39dqm3c0_license_h.txt) sat on pipdigz.co.uk, which yesterday morning returned ‘https://kotrynabassdesign.com/wp-admin/admin-ajax.php’ in the response body.
\nEvery single hour night and day, without any manual intervention, any blogger running the pipdig plugin will send a request with a faked User Agent to ‘https://kotrynabassdesign.com/wp-admin/admin-ajax.php’ with a random number string attached. This is effectively performing a small scale DDoS (Distributed Denial of Service) on kotrynabassdesign.com’s server.
Turner also contacted Kotryna Bass, Pipdig’s competitor, who said she had contacted her host after finding that her admin-ajax.php file was under some kind of attack. Bass’ exchanges with her host are also published in Turner’s report.
\nTurner’s post explained how Pipdig’s P3 plugin code manipulated links to point to their own products and services when a user includes a link to a competitor in the the content:
\n\nHere we have pipdig’s plugin searching for mentions of ‘blogerize.com‘ with the string split in two and rejoined – concatenated – to make it harder to find mentions of competitors when doing a mass ‘Find in Files’ across the plugin (amongst other things). When the plugin finds links to blogerize.com in blogger’s content (posts, pages), they’re swapped out with a link to ‘pipdig.co/shop/blogger-to-wordpress-migration/’ i.e. pipdig’s own blog migration services. Swapping these links out boost the SEO benefit to pipdig, and the vast majority of bloggers wouldn’t notice the switcheroo (especially as if the page/post was edited, the link to blogerize would appear in the backend as normal).
The plugin did not ask users’ permission before performing any of these actions and most of them were implemented with obfuscated code. Turner’s investigation also covers how the P3 plugin could harvest data and change admin passwords. Many of the findings overlap with Wordfence’s analysis.
\n“I was aware that Wordfence had been contacted for an opinion, although I was unaware they were writing a post and vice versa,” Turner said. “I wasn’t surprised that they wrote about it though, given the risk to WordPress users.”
\nShe has been in contact with authorities regarding Pipdig’s unethical coding practices and privacy violations.
\n“From my side of things, I’ve been in contact with Action Fraud (submitted a report through their website) and NCSC (who pointed me back to Action Fraud and gave me a number to call). From pipdig’s side, there are threats of legal action in their blog post but I’ve received nothing yet.”
\nPipdig Creative Director Phil Clothier published a public response from the company which opens by characterizing the recent investigations as “various accusations and rumours spreading about pipdig” and includes an emotional plea regarding how distressing recent developments have been for his company. He claims that his team and their supporters are being harassed.
\nAfter pushing out the 4.8.0 version of the P3 plugin, removing some but not all of the offensive code, Clothier opts for a Q&A style format for his post, putting every question in the present tense:
\n\nDo you DDOS competitors?
\n
\nNo.Do you “kill” sites?
\n
\nNo!Do you have the ability to kill sites via the pipdig Power Pack?
\nNo
Regarding the “kill switch” feature they built in, which detects all tables with the WordPress prefix and drops each of them, Clothier said it was simply a function to reset a site back to its default settings. He deliberately misrepresented what it does:
\n\nThere was function in an older version of the plugin which could be used to reset a site back to the default settings. This function had no risk of of malicious or unintentional use. I can say categorically that there was no risk to your site if you were using a pipdig theme. This feature has been dug up and labelled a “Kill Switch” for maximum negative impact on us.
Clothier claims the function was available in the P3 plugin in July 2018 when a third party started posting Pipdig themes for sale on their own site:
\n\nA 3rd party was able to download all of our themes illegitimately and post them on a clone of our own site. This included previews of our themes and the ability to purchase them. We were first alerted to this by people which had purchased a pipdig theme from there, but were finding that certain features did not work correctly. After investigation, we found that the victim had purchased the theme from the 3rd party, thinking it was us. The 3rd party not only gained the financial benefit of the theme payment, but also used it as a way to inject malware and ads into the victim’s site. The reset function was put in place in order to remove the 3rd party’s ability to host preview sites with our themes. It worked, and they have since disappeared. The function was then removed in a later version of the plugin.
This is a false claim, as Wordfence pointed out in an updated article. The first instance of the code responsible for database deletion was committed to the plugin in November 2017.
\nThe company failed to address the most critical concerns presented in the Wordfence analysis in its first pass at issuing a public statement. Instead, on the matter of coordinating a DDoS attack on competitors, Pipdig blames users and suggests they may have added the competitor’s URL to their sites.
\n“We’re now looking into why this function is returning this url,” Clothier said. “However, it seems to suggest that some of the ‘Author URLs’ have been set to ‘kotrynabassdesign.com’. We don’t currently know why this is the case, or whether the site owner has intentionally changed this.”
\nFurther investigations published by Wordfence today showed that Pipdig also added DDoS code to its Blogger templates and was actively issuing malicious requests up until yesterday:
\n\nDuring the investigation of Pipdig’s WordPress plugin and themes, we also came across some curious code associated with their Blogger themes. This code is part of Pipdig’s suspected DDoS campaign against their competitor, and was active until April 1, four days after Pipdig’s denial of any such behavior.
\nSome of Pipdig’s Blogger themes have been confirmed to make external JavaScript calls to Pipdig’s server, specifically to the script hXXps://pipdigz[.]co[.]uk/js/zeplin1.js.
On March 31, as the investigations became public, Pipdig deleted its public Bitbucket repository and replaced it with a “clean one,” removing three years of commit history. Wordfence and many others cloned the repository before it was deleted and saved snapshots of pages to cite in the investigation.
\n\n\n\nThat clean repository @pipdig published earlier today in place of the one containing all of their malicious code… They changed the reported release date of version 4.8.0. pic.twitter.com/YqKASTUZE7
\n— Nicky Bloor (@nickstadb) April 1, 2019
Pipdig’s public statement contains a number of other false claims that are outlined in Wordfence’s followup piece with code examples. Clothier closes the article by casting aspersion on the press, presumably to encourage customers not to trust what they read from other sources.
\nI contacted Pipdig for their comment on recent events, but Clothier declined to answer any of my questions. One of those was why the plugin disables Bluehost’s caching plugin without informing customers.
\n\n\n\nAnother one from the @pipdig plugin. If you use one of their themes on @bluehost then they intentionally slow your website down by disabling the BlueHost cache plugin, then they can inject content with the title "Is your host slowing you down?" CC @jemjabella @heyitsmikeyv pic.twitter.com/48DUXsDyBj
\n— Nicky Bloor (@nickstadb) March 31, 2019
Clothier said he didn’t have any comments beyond what he said in the public statement but encouraged anyone interested to read the new comments added to the code in version 4.9.0:
\n\nWe’ve also updated version 4.9.0 of the plugin which includes extra commenting in the code, which will hopefully help clear things up like issues with Bluehost caching and the_content() filter.
\nIf anyone is unsure, we recommend updating to the latest version as always. However we also contend that the previous versions had no serious issues too.
Pipdig declined to answer questions about licensing but the products do not appear to be GPL-licensed. This may be why the company deemed it within its rights to take action on those who they believe to have “stolen” their themes.
\nIn what is perhaps one of the most brazen abuses I’ve ever seen from a theme company in WordPress’ history, Pipdig’s user base has unknowingly been used to target the company’s competitors. Regardless of the company’s motive in combatting the unauthorized distribution of their themes, these types of backdoors and undisclosed content rewrites are indefensible. They prey upon user trust and in this case the victims were primarily bloggers.
\n\n\n\nI think that''s why so many of us are so angry. Bloggers are the lifeblood of #WordPress, you create content and for the most part don''t have big budgets to spend. So when someone takes advantage of that those at the "low budget" end of the market, those that cant afford devs…
\n— Andy Powell (@p0welly) March 31, 2019
One of the more puzzling aspects of this story is that many of Pipdig’s users seem to be unfazed by the gravity of the findings in these reports. Without full knowledge of the inner workings of a product, many customers make decisions based on how they feel about a company, regardless of being confronted with facts that should cause them to question their experiences.
\n\n\n\nI’m not concerned. I trust them. And I’m certainly not panicking and acting on the words of two blog posts citing their competitors. They’ve served me well for years.
\n— Caroline Hirons (@CarolineHirons) March 29, 2019
Others are angry to have had their sites used in an attack. Getting set up on a new theme is not a trivial task for non-technical users who may have had to pay a developer to launch their sites in the first place.
\n\n\n\nHonestly? I’m really angry. I trusted them for years, and in return my site has been used maliciously against other small businesses. I’ve been watching this unfold since Friday but even this update shocked me. https://t.co/mPsO8EoHBp
\n— Charlotte (@bycharlotteann_) April 2, 2019
“My mind is absolutely blown by pipdig’s public response,” Jem Turner said. “I understand that they were counting on their users’ completely non-tech background to bamboozle them, and it certainly seemed to be working in the beginning, but anyone with even the slightest bit of coding knowledge can see that they are lying and I genuinely don’t understand how they think they’ll get away with it.”
\n\n\n\nThe crazy part is if we want to be really real about this, it''s more like
\nThe cable guy cut a big hole in my wall and installed a door handle on it. He took some painter''s tape and scrawled "THIS IS A CABLE BOX" on the drywall. Then looked me in the eyes and said "No I didn''t."
\n— Mikey Veenstra (@heyitsmikeyv) March 31, 2019
This incident shines a spotlight on how unregulated the commercial plugin and theme ecosystem is and how little protection users have from companies that abuse their power. If you are a Pipdig customer affected by this incident, there is no assurance that the company will not build more backdoors into your site in the future. The plugin updates are not reviewed by any kind of authority. Fortunately, there are a few actions you can take to create a safer environment for your website.
\nFirst, look for GPL-licensed themes and plugins, because they grant you more freedoms as the user and are compatible with WordPress’ legal license. GPL-licensed products are also a strong indication that the authors respect user freedoms and the shared economic principles that this open source license supports.
\nMany reputable theme companies choose to host their products’ companion plugins on WordPress.org for ease of distribution and shipping updates. The official directory does not permit these kinds of shady coding practices described in this article and all of the plugins go through a security review by the WordPress Plugin Team. If you are concerned about code quality and the potential for abuse, do a little research on your next prospective commercial theme provider or opt for free WordPress.org-hosted themes and plugins that have undergone a more rigorous vetting process.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 03 Apr 2019 05:55: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: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:50:"HeroPress: Growing a WordPress business in Vietnam";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2727";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:152:"https://heropress.com/essays/growing-a-wordpress-business-in-vietnam/#utm_source=rss&utm_medium=rss&utm_campaign=growing-a-wordpress-business-in-vietnam";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:23606:"Xem nội dung tiếng Việt ở dưới.
\nIt’s been 13 years since I first knew WordPress. Thinking of it, I found it to be one of the most fortunate things I had in my career and life. I can do what I love, can make money to support myself, my family and have many good friends.
\nWhen I found out about WordPress, I was still a second-year student at the university. The major I studied was not IT but mechanical engineering. I chose it with the desire to get a scholarship abroad (it was in Russia). But in the process of learning, I found myself inclined to and more passionate about coding. Therefore, I taught myself coding.
\nIn my second year of university, I wanted to set up a website to download software. It is not a very proud thing, because at that time I just wanted to share the software with everyone, including free software and pirated software (software pirating is still a big problem in Russia and in Vietnam). It can be said that software was what attracted me the most at that time. I was passionate about finding new software, testing, running them, finding great features and sharing experiences with people.
\n\nAt that time, the web was still something very new to me and I didn’t have many concepts about it. I just needed to find a free platform to build a blog about software.
At that time, there were two platforms that caught my attention – WordPress and BoBlog. BoBlog was a Chinese platform (it’s dead now), and WordPress seemed more international, so I chose WordPress.
\nIt can be said that the choice of WordPress has made me learn more seriously about the web and related technologies. By editing the theme, making additional features for my blog, I learned a lot about HTML, CSS, JavaScript, and PHP. During my time at the university, I had been exploring these things and gradually improving my knowledge base.
\nFor me, the web has a big advantage comparing to other software, which is any line of code you write, you can see the result right in the browser by just pressing F5. This was the point that I was very excited about because when I tried coding in other languages, the compiling process made me feel time-consuming and not very intuitive.
\nAfter that, I felt that the knowledge I learned was quite interesting and wanted to share it with everyone. So I started my personal blog, it is still active at deluxeblogtips.com. Blogging is an important thing in my career, maybe the most. It brings a lot of fortunate to me:
\nEnglish: English is not my native language. But by blogging, my reading and communication skill in English has improved significantly. Although there are still many errors, I feel quite confident when talking to international friends. This has been happening for a long time and I am very grateful for it.
\nThe first freelance jobs: Blogging has been around for a while, some people knew about me thanks to my helpful sharing. And they started contacting me and asked if I wanted to work for them. At that time, as a student, I was very happy, because I could earn some money. Later, when I graduated from university, I started my career with those freelance jobs. I did freelancing for about 4-5 years since 2010. I participated in many projects, learned a lot of things and knew a lot of friends. During this time, I also gathered a group of Vietnamese friends to work on those freelance jobs. Until now, although the group is no longer available, we are still good friends and still meet often.
\nStart ideas for products: precisely Meta Box. This is my company’s flagship product at the moment. Its idea started from my tutorial on the blog. Thanks to those sharing, it’s now a plugin of 400,000 active installs that based on a tutorial.
\nBlogging makes many people known about me. And my share (and other products) is also useful for many people and thanks to that, I connect with many developers around the world and in Vietnam. In 2012, when Philip Author Moore came to Vietnam, we met the first time, and it was a “fateful” meeting between us. Together, we built the WordPress community in Vietnam from those early years, started the Hanoi WordPress Meetup and shared a lot of things about WordPress. There were many companies in Vietnam starting to redirect and working on WordPress from such meetup sessions.
\nSo far, the community has been strong and we are no longer involved because we’re quite busy and we do not have too much experience in organizing and maintaining offline activities. Online activities are still very exciting thanks to Facebook!
\nBeing a developer and having the opportunity to work on projects with customers, in 2010, I found many things missing from WordPress. And at that time, I had the idea of Meta Box, which is a developer framework to quickly create custom fields. I shared a series of tutorials on my blog. What I didn’t expect was that there were so many people having the same interest.
\nAfter that, I continuously upgraded the plugin, based on feedback from other users and developers. I also get a lot of help from other developers, especially Kaiser. I am really grateful to them because, without them, Meta Box could not become a plugin with 400,000 active installs.
\nWhen I first developed the plugin, I didn’t have much idea about commercializing it. All were free. At that time, I didn’t know much about interacting on wordpress.org and the Trac system, so I released the code on Google Code. A long time later, I uploaded it to wordpress.org. Therefore, when comparing the custom fields plugins, Meta Box is sometimes not considered the first plugin, while it should be.
\n\nThe idea of Meta Box was later inherited by many people and developed similar plugins. And I really like that, because that’s the idea of open source!
The success of Meta Box was the basis for me to establish my own company – eLightUp to develop products for WordPress.
\nIn addition to Meta Box, while creating a freelance team, we also tried to become a theme provider and joined ThemeForest. It was not very successful, because I feel ThemeForest is a battlefield in which the parties race to add features to make a theme become powerful, able to do many things and therefore very bloated and not optimal. As a developer, I always feel uncomfortable with those things.
\nThe theme work then was separated into two brands of our company: FitWP for themes on ThemeForest and GretaThemes for themes that are simple, optimal and serve a specific purpose. Currently, the focus of our company are Meta Box and GretaThemes.
\nAnd for freelance work, we moved into a division of our company that specializes in projects with customers. We carry out projects for both domestic and international customers.
\nBefore establishing the company, the income from the products and projects helped me and my family have a comfortable life in Vietnam. But for a long time in the WordPress community, I’ve seen many brands that I’ve always admired, especially WooThemes (now merged into Automattic). Seeing their great contributions to the community, I always want to do the same. And to do that, it’s difficult to do as an individual. So I founded eLightUp, wishing to create good products and contribute to the community.
\nWhen I founded the company, I did not measure all the management issues or predicted that. I had to learn a lot, from managing people, resources, finance to strategy, market research and marketing. As a developer, they are all new and challenging things. There were times when I was very stressful because I had to do both developing products and other work which were not my strength.
\nSo far, things have gotten better, I have become more comfortable to work, although I still have to code and manage at the same time.
\nAbove all, I see what I have now is big luck, and that is totally love and support from the community for me. Therefore, no matter how difficult or challenging things are, I still feel very happy with what I have and will try to do better.
\nĐã 13 năm kể từ khi tôi biết đến WordPress lần đầu tiên. Nghĩ lại, tôi thấy đó là một trong những điều may mắn nhất mà tôi có được trong sự nghiệp và cuộc sống của mình. Tôi được làm điều mà tôi yêu thích, có thể kiếm tiền nuôi sống được bản thân, gia đình và có thêm nhiều bạn bè tốt.
\nKhi tôi biết đến WordPress, tôi vẫn còn là 1 cậu sinh viên năm thứ 2. Chuyên ngành mà tôi học không phải là IT mà là cơ khí chế tạo máy. Tôi đã chọn chuyên ngành đó với mong muốn có được 1 suất học bổng ở nước ngoài, khi đó là ở Nga. Nhưng trong quá trình học tập, tôi thấy mình có thiên hướng và đam mê về lập trình nhiều hơn. Vì thế, tôi đã tự học và bổ sung các kiến thức về IT cho mình.
\nNăm thứ 2 đại học, tôi muốn lập 1 website về download phần mềm. Cũng không phải là một điều tự hào gì lắm, vì lúc đó tôi chỉ muốn chia sẻ các phần mềm với mọi người, trong đó có phần mềm miễn phí và có cả phần mềm crack (vấn nạn crack phần mềm ở Nga và ở Việt Nam vẫn còn rất lớn). Có thể nói phần mềm là thứ thu hút tôi lúc đó nhiều nhất. Tôi say mê tìm phần mềm mới, thử nghiệm, chạy chúng, tìm các tính năng hay và chia sẻ kinh nghiệm với mọi người. Lúc đó, web vẫn còn là một thứ gì đó rất thô sơ và tôi cũng chưa có nhiều khái niệm về nó. Tôi loay hoay tìm một nền tảng có sẵn để xây dựng một blog về phần mềm. Vào thời điểm đó, có 2 nền tảng đã gây sự chú ý với tôi – đó là WordPress và BoBlog. BoBlog là 1 blog của Trung Quốc, còn WordPress thì có vẻ quốc tế hơn, nên tôi đã chọn WordPress.
\nCó thể nói sự lựa chọn WordPress đã khiến tôi học hỏi nghiêm túc hơn về web và các công nghệ liên quan. Bằng cách chỉnh sửa giao diện, làm thêm các tính năng bổ sung cho blog của mình mà tôi đã học được nhiều điều về HTML, CSS, JavaScript và PHP. Trong suốt thời gian học đại học, tôi đã mày mò những cái này và dần hoàn thiện nền tảng kiến thức của mình.
\nĐối với tôi, web có 1 điểm hơn các phần mềm khác, đó là bất kỳ dòng code nào mà bạn viết, bạn có thể thấy kết quả của nó ngay trên trình duyệt (chỉ với 1 lần nhấn F5). Đây là điểm mà tôi rất thích thú, vì trước đó tôi đã thử lập trình trên một số ngôn ngữ khác, nhưng quá trình biên dịch khiến tôi cảm thấy mất thời gian và không trực quan lắm.
\nSau đó, tôi cảm thấy những kiến thức mà tôi học hỏi được cũng khá thú vị và muốn chia sẻ nó với mọi người. Và tôi bắt đầu viết blog để chia sẻ. Blog của tôi đến nay vẫn hoạt động tại deluxeblogtips.com. Có thể nói viết blog là bước ngoặt quan trọng trong sự nghiệp của tôi. Nó đã giúp tôi có được nhiều thứ quyết định trong sự nghiệp của mình:
\nTiếng Anh: tiếng Anh vốn không phải là ngôn ngữ mẹ đẻ của tôi. Nhưng nhờ trau dồi viết blog mà khả năng đọc hiểu và trao đổi bằng tiếng Anh của tôi tiến bộ rõ rệt. Mặc dù còn nhiều lỗi, nhưng tôi cảm thấy khá tự tin khi nói chuyện với bạn bè quốc tế. Việc này xảy ra trong khoảng thời gian dài và tôi rất biết ơn điều đó.
\nNhững công việc freelance đầu tiên: Viết blog được 1 khoảng thời gian, nhờ những chia sẻ có ích của mình mà một số người đã biết đến tôi. Và họ bắt đầu contact với tôi và hỏi xem tôi có muốn làm việc cho họ không. Lúc đó, với 1 sinh viên thì tôi rất vui mừng, vì có thể kiếm được chút ít tiền. Về sau này, khi tôi tốt nghiệp đại học, tôi đã bắt đầu sự nghiệp của mình bằng những công việc freelance đó. Tôi đã làm freelance trong suốt khoảng 4-5 năm kể từ 2010. Tôi đã được tham gia nhiều dự án, học hỏi được rất nhiều điều và biết được thêm rất nhiều bạn bè. Trong khoảng thời gian này, tôi cũng đã tập hợp được 1 số bạn bè cùng làm WordPress tại Việt Nam thành 1 nhóm và cùng làm các công việc freelance đó. Đến nay, tuy nhóm cũ không còn, nhưng chúng tôi vẫn là những người bạn tốt và vẫn hay thường xuyên gặp nhau.
\nBắt đầu ý tưởng cho các sản phẩm: cụ thể là Meta Box. Đây là sản phẩm flagship của công ty của tôi hiện tại. Ý tưởng của nó bắt nguồn từ những chia sẻ của tôi trên blog. Nhờ những chia sẻ đó mà tôi đã xây dựng 1 sản phẩm được 400.000 người sử dụng với gốc là từ 1 bài tutorial.
\nViết blog khiến nhiều người biết đến tôi. Và những chia sẻ của tôi (và cả các sản phẩm nữa) cũng có ích cho nhiều người và nhờ đó tôi cũng kết nối được với nhiều bạn developer trên thế giới và ở Việt Nam. Năm 2012, khi anh Philip Author Moore tới Việt Nam, chúng tôi đã gặp nhau lần đầu tiên, và đó là buổi gặp “định mệnh” giữa chúng tôi. Cả 2 chúng tôi đã xây dựng cộng đồng WordPress Việt Nam từ những năm đầu đó, cùng start Hanoi WordPress meetup và chia sẻ rất nhiều điều về WordPress. Có rất nhiều công ty ở Việt Nam bắt đầu chuyển hướng và làm về WordPress từ những buổi meetup như vậy.
\nĐến nay, cộng đồng đã vững mạnh và chúng tôi không còn tham gia nhiều nữa vì công việc khá bận rộn và bản thân chúng tôi cũng không có quá nhiều kinh nghiệm trong việc tổ chức và duy trì các hoạt động offline. Các hoạt động online thì vẫn diễn ra rất sôi động nhờ vào Facebook!
\nVốn là 1 developer và đã có cơ hội làm việc với các dự án với khách hàng, vào những năm 2010, tôi thấy có nhiều điều còn thiếu trong WordPress. Và lúc đó, tôi đã có ý tưởng về Meta Box, là một framework giúp developer tạo nhanh các custom fields. Tôi đã chia sẻ 1 loạt bài tutorial về việc xây dựng nó trên blog của mình. Và điều tôi không ngờ lúc đó là có rất nhiều người có cùng mối quan tâm như vậy.
\nSau đó, tôi đã liên tục nâng cấp plugin, dựa theo những phản hồi của các developer khác. Tôi cũng nhận được sự giúp đỡ rất nhiều của các bạn developer khác, mà trong đó không thể không nhắc tới Kaiser. Tôi thực sự rất biết ơn các bạn, cả những người dùng nữa, vì không có các bạn thì Meta Box đã không thể trở thành 1 plugin với 400.000 lượt active installs được.
\nKhi mới phát triển plugin, tôi chưa có ý niệm nhiều về thương mại hoá nó. Toàn bộ đều được chia sẻ miễn phí. Lúc đó, tôi cũng chưa biết nhiều về tương tác trên wordpress.org với hệ thống Trac, nên tôi release code trên Google Code. Mãi sau này tôi mới đưa lên wordpress.org. Vì thế nên nhiều khi so sánh tuổi đời của các plugin về custom fields, Meta Box đôi khi không được coi là plugin đầu tiên, trong khi đúng ra là nó phải là như vậy.
\nÝ tưởng của Meta Box sau này còn được nhiều người kế thừa và phát triển ra các plugin tương tự. Và tôi rất thích điều đó, vì đó là tư tưởng của open source!
\nSự thành công của Meta Box là cơ sở để tôi thành lập công ty của riêng mình – eLightUp để phát triển các sản phẩm cho WordPress.
\nNgoài Meta Box, trong khi thành lập nhóm làm freelance, chúng tôi cũng đã thử dấn thân vào mảng làm theme và đã tham gia ThemeForest. Có thể nói là mảng đó không được thành công lắm, vì tôi cảm thấy ThemeForest là một chiến trường trong đó các bên đua nhau thêm những tính năng để cho 1 theme trở nên mạnh mẽ, làm được nhiều thứ và do đó rất nặng nề và không tối ưu. Mà tôi là 1 developer nên luôn cảm thấy không thoải mái với những điều đó.
\nMảng làm theme sau này phân tách ra thành 2 brands của công ty chúng tôi: FitWP cho những theme trên ThemeForest và GretaThemes cho những theme đơn giản, tối ưu và phục vụ 1 mục đích cụ thể. Hiện nay thì trọng tâm của công ty chúng tôi là Meta Box và GretaThemes.
\nCòn mảng làm freelance sau này chúng tôi tách thành một nhánh trong công ty của chúng tôi là chuyên làm các dự án với khách hàng. Chúng tôi thực hiện các dự án cho cả khách hàng trong nước và quốc tế.
\nTrước khi thành lập công ty, nguồn thu nhập mà các sản phẩm và dự án mang lại cũng đã giúp tôi và gia đình có 1 cuộc sống khá thoải mái ở Việt Nam. Nhưng ở trong cộng đồng WordPress đã lâu, tôi đã thấy rất nhiều brand mà khiến tôi luôn ngưỡng mộ, trong đó nổi bật là WooThemes (nay đã không còn nữa). Thấy các đóng góp to lớn của họ cho cộng đồng, tôi cũng mong muốn mình làm được những điều tương tự. Và để làm việc đó, sức lực của 1 cá nhân rất khó. Nên tôi đã thành lập eLightUp, với mong muốn tạo ra những sản phẩm tốt, đóng góp cho cộng đồng và cả những đóng góp miễn phí nữa.
\nKhi thành lập công ty, tôi đã không lường được hết những vấn đề về mặt quản lý công ty. Tôi đã phải học rất nhiều điều, từ việc quản lý con người, nguồn lực, tài chính đến những vấn đề về định hướng, chiến lược, nghiên cứu thị trường, marketing. Đối với 1 developer, đây đều là những thứ mới mẻ và thách thức. Có những khoảng thời gian tôi đã rất áp lực, vì vừa phải phát triển sản phẩm, vừa phải làm những công việc khác vốn không phải là thế mạnh của mình.
\nĐến nay, mọi thứ đã tốt hơn, tôi đã quen dần hơn với công việc, mặc dù tôi vẫn phải code và quản lý cùng một lúc.
\nNhưng mà, trên tất cả, tôi thấy những gì mà mình có được bây giờ đều là sự may mắn, và đó đều là sự yêu thương, support từ cộng đồng đã dành cho tôi. Bởi thế, cho dù mọi thứ có khó khăn, thách thức như thế nào, tôi vẫn cảm thấy rất vui với những gì mình đang có, và sẽ cố gắng để làm mọi thứ tốt hơn.
\nThe post Growing a WordPress business in Vietnam 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, 03 Apr 2019 02:00: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:8:"Anh Tran";s: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:71:"WPTavern: Jetpack 7.1 Adds Feature Suggestions to Plugin Search Results";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88404";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:82:"https://wptavern.com/jetpack-7-1-adds-feature-suggestions-to-plugin-search-results";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10445:"Jetpack 7.1 was released earlier this month with new blocks for WordAds, Business Hours, Contact Info, Slideshows, and Videos. This release also quietly added suggestions to the plugin search screen, a change that has not been well-received by the developer community. If a user searches for a plugin that has a feature that is already offered by Jetpack, the plugin will insert an artificial (and dismissible) search result into the first plugin card slot, identifying the corresponding Jetpack feature.
\n\nAlthough these suggestions in plugin search results were not presented as a headline feature in the 7.1 release post, it was clearly listed in the changelog under enhancements. More people began taking notice after WordPress developer Mehul Gohil tweeted a screenshot of it on a live site:
\n\n\n\nNowadays, plugin search in #WordPress admin suggests a product/add-on. I see the future of these suggestions to be used by plugin authors to keep their product first in certain plugin search terms for upsells like admin notices.
\nWhat do you think about this? #DontHijackWPAdmin pic.twitter.com/TERjrPgEt6
\n— Mehul Gohil (@mehul_gohil0810) March 26, 2019
Manipulating search results, even to insert an artificial result, using a plugin that is already installed, is a major new development among plugins hosted on WordPress.org. Automattic is setting a precedent for other plugin authors that want to recommend their own add-ons or extensions when users match certain search terms.
\nIn the feature’s initial proof of concept, Jetpack product lead Beau Lebens explained the motivation behind adding suggestions to the search screen:
\n\nWe’ve seen that people with Jetpack installed and activated often search for Jetpack features (even by name) in the Plugins > Add New screen in wp-admin. This new module attempts to spot those searches, and provide an artificial search result that calls out that what they’re looking for is in Jetpack, which they already have, and which is already active.
Eight years since its initial release, Jetpack has grown to 45 modules. Most users are not familiar with everything the plugin offers. In fact, many users may not have even installed Jetpack themselves, as it often comes pre-installed with hosting. The suggestions may prevent users from adding alternate third-party plugins, as Jetpack’s module placement in the results subtly implies that these are inferior options to its existing modules.
\nOne of the reasons the feature has many developers rattled is because the UI fails to make it clear that this is an artificial result and not something generated by the plugin directory’s algorithm. Although it is intended to function more as a notice, for the regular user, it is virtually indistinguishable from an advertisement in its current implementation. It hasn’t been live for very long, but over time it may even make it more difficult for plugin developers to offer plugins that compete with Jetpack features.
\nThe feature suggestions in plugin search results became a hot topic on Post Status‘ Slack where Automattic’s Gary Pendergast dropped in to reiterate the Jetpack team’s intentions.
\n“I’ve been talking to some folks on Jetpack about what’s going on,” Pendergast said. “I think the team’s end goal is pretty good, and it solves a real problem WordPress has. Too often, site owners install masses of plugins that they don’t need, which ultimately creates all sorts of security, performance, and stability issues. In this particular use case, if a site owner is looking for functionality that Jetpack already handles, then the owner should be aware of that.”
\nPendergast also said he thinks WordPress core should offer an API for any plugin to be able to do something similar.
\nAlthough it’s easy to conjure up different ways to abuse this avenue for advertising a plugin’s existing features, WordPress.org’s plugin team is ready to deal with a potential influx of various implementations on a case-by-case basis.
\n“It’s not really advertising anything – it’s just adding search results for pieces of a plugin that you already have and might not know about, so it’s not really against any rules,” Samuel “Otto” Wood said. “If it was misleading in some manner, then that would be different.”
\nWood said the team discussed it but concluded that any implementation of something similar in other plugins will need to be reviewed to see if it’s doing anything misleading.
\n“Realistically it’s always going to be a judgment call of some sort,” Wood said. “For example, if a plugin was to insert search results for other plugins, then that wouldn’t be okay, because it’s misleading. But, this isn’t that case. It’s just trying to say ‘hey, you have a plugin already installed which does what you’re looking for,’ so it’s trying to be helpful in that respect. It may not necessarily be the best way of accomplishing that goal, admittedly. But it’s pretty valid.”
\nWood did not place a hard requirement on having the artificial result be dismissible but said anytime a developer inserts something into a screen where would not normally be, having dismiss functionality is good UX. He doesn’t think it’s likely that many other plugin authors will implement something similar since most are not collections of dozens of plugins and add-ons. However, this type of suggestion seems like it would also be applicable to block collection plugins that include dozens of Gutenberg blocks.
\n“It will be really difficult for users when all the essential plugin authors implement it,” Gohil said in response to comments on the screenshot he tweeted. “They are using JS to hack into plugin search using hook ‘admin_enqueue_scripts’ and that’s not good. I’m not in favor of it.”
\nIf more plugin authors begin adding suggestions, users could see several rows of artificial results before seeing any real ones, depending on which plugins they have installed. Plugin developers are already brainstorming ways to strip the feature suggestions out. It likely will not be long before plugins like Hide Jetpack Promotions removes the artificial search results to maintain results as delivered by WordPress.org.
\nWood said the plugin team does not intend to write any new guidelines for plugin authors creating their own implementations of feature suggestions on the search screen.
\n“The difference is always going to be one of intent,” Wood said. “It’s JP’s intent here to notify the user of the existence of a feature they may not know about. That’s trying to be helpful to the user, not trying to shut out competition. It doesn’t remove search results. It doesn’t reorder them or filter them. It just adds a card about the feature you’re searching for. If you don’t have JP, then it can’t do anything. It’s not advertising for other plugins or anything like that.”
\nJetpack is also tracking search terms longer than three characters, and Wood confirmed that this is also within the guidelines, as long as it is disclosed to the user.
\n“The whole tracking module doesn’t activate until after you agree to the ToS thingy, so honestly, it’s allowed,” Wood said. “They track lots of things for stats and such. Realistically, so do many other plugins. As long as you ask the user first, before tracking anything, then tracking data is allowed. Opt-in is the rule.”
\nWood said he found the search term tracking to be unnecessary since WordPress.org already collects this information through its new search system that runs on ElasticSearch.
\n“We get all the search terms on the WordPress.org servers, anyway, so both we and they kinda already have them,” Wood said. “Automatticians built our newest plugin search engine, after all. It seems kind of a waste to track them using Jetpack when they literally receive all the searches to run through the search engine.”
\nJetpack’s artificial search results, although dismissible, take up the top spot, bypassing the algorithm altogether. It gives the appearance that Jetpack’s built-in feature is either a promoted listing or superior to all other options available in the directory.
\nAlthough a suggested module may work more harmoniously with other Jetpack features than a third-party plugin, the modules are built to be fairly general in terms of features. They address the basic needs for the largest number of users but rarely provide more options than a standalone plugin dedicated to performing something similar. Users may very well be searching for a replacement for what Jetpack provides. The ability to easily turn off suggestions in search results with a toggle could go a long way for diplomacy.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 02 Apr 2019 15:40:05 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:33;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:76:"WPTavern: Automattic Launches Happy Tools Product Line for Distributed Teams";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88372";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/automattic-launches-happy-tools-product-line-for-distributed-teams";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3144:"Automattic has released Happy Schedule, the first in a new line of products called “Happy Tools,” created to solve problems for distributed teams. The products have grown out of internal tools that Automattic uses with its distributed team of more than 850 employees in 68 countries.
\nMost employee scheduling tools are designed for more traditional work environments where people report to work in person in the same timezone. Happy Schedule allows employees to set their own flexible schedules all the way down to 15-minute increments, seamlessly managing timezones for team members in one calendar. Automattic uses it to manage 24-hour global support with its 300+ Happiness Engineers.
\n\nHappy Tools is currently priced at $60/month for 12 users and then $5/user after that.
\n“In addition to Happy Schedule, we’ll be looking to bring our customer chat tool into Happy Tools,” Happy Tools product lead Matt Wondra said. “We’ll also look at other applications Automattic has already built to help with team communication, people-management, and customer support.”
\nThe product suite complements Matt Mullenweg’s recent TED talk in which he evangelizes distributed work as “the future of work.” Mullenweg predicts that companies will evolve to become distributed first or will soon be replaced by ones that are.
\nBeyond simply recognizing the benefits of employees being able to design their own work environments, there are some real challenges to becoming a distributed company. This is especially true for those that didn’t start out that way. Smaller companies have less experience navigating all the tax laws and legal processes around hiring people from different countries. These hurdles make it difficult to grow an international team and retain employees as anything more than hourly contractors.
\nAnswering some of these difficult questions gets into the meat of making distributed teams a reality. With its position as one of the few distributed companies that has successfully scaled into the hundreds, Automattic has an opportunity to open source some of its counsel, documents, and HR guides around international hiring. This would be a valuable addition to distributed.blog or the Happy Tools blog that would help more companies move beyond their initial explorations of distributed work and ultimately create a larger market for these kinds of tools.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 02 Apr 2019 04:28:20 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:46:"WordPress.org blog: Minimum PHP Version update";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=6810";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:62:"https://wordpress.org/news/2019/04/minimum-php-version-update/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2947:"WordPress 5.2 is targeted for release at the end of this month, and with it comes an update to the minimum required version of PHP. WordPress will now require a minimum of PHP 5.6.20.
\n\n\n\nBeginning in WordPress 5.1, users running PHP versions below 5.6 have had a notification in their dashboard that includes information to help them update PHP. Since then, the WordPress stats have shown an increase in users on more recent versions of PHP.
\n\n\n\nIf your site is running on an unsupported version of PHP, the WordPress updater will not offer WordPress 5.2 to your site. If you attempt to update WordPress manually, that update will fail. To continue using the latest features of WordPress you must update to a newer version of PHP.
\n\n\n\nWhen updating to a new version of PHP, WordPress encourages updating to its recommended version, PHP 7.3. The PHP internals team has done a great job making its most recent version the fastest version of PHP yet. This means that updating will improve the speed of your site, both for you and your visitors.
\n\n\n\nThis performance increase also means fewer servers are needed to host websites. Updating PHP isn’t just good for your site, it also means less energy is needed for the 1-in-3 sites that use WordPress, so it’s good for the planet.
\n\n\n\nIf you need help updating to a new version of PHP, detailed documentation is available. This includes sample communication to send to your host for them to assist you. Many hosting companies have published information on how to update PHP that is specific for them.
\n\n\n\nThis is the first increase in PHP required version for WordPress since 2010, but may not be the only increase in 2019. The WordPress core team will monitor the adoption of the most recent versions of PHP with an eye towards making PHP 7+ the minimum version towards the end of the year.
\n\n\n\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 01 Apr 2019 14:51: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:12:"Aaron Jorbin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:35;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:54:"WordPress.org blog: The Month in WordPress: March 2019";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=6846";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wordpress.org/news/2019/04/the-month-in-wordpress-march-2019/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7947:"
WordPress reached a significant milestone this month. With some exciting developments in Core, an interesting new proposal, and the return of a valuable global event, March was certainly an interesting time.
\n\n\n\nWordPress’ market share has been steadily increasing, and as of halfway through this month, it powers over one-third of the top 10 million sites on the web (according to W3Techs, which tracks usage statistics for all major web platforms).
\n\n\n\nThis growth of WordPress is only made possible by the large team of volunteers working to build the project and community. If you would like to get involved in building the future of WordPress, then check out the Make network for a contributor team that fits your skill set.
\n\n\n\nWordPress 5.1.1 was released this month, with 14 fixes and enhancements, and the Core team is now focusing on the next major release, version 5.2. This release will include some great new features, along with the latest updates to the block editor.
\n\n\n\nOne of the most anticipated new features is the improved fatal error detection – this was removed from v5.1 shortly before release so that it could be improved and made more secure for this release. Along with that, PHP 5.6 is going to become the minimum required PHP version for WordPress, a significant step towards a more modern web and updated coding standards.
\n\n\n\nWordPress 5.2 is now in beta and you can test it by installing the Beta Tester plugin on any WordPress site.
\n\n\n\nWant to get involved in building WordPress Core? Follow the Core team blog and join the #core channel in the Making WordPress Slack group.
\n\n\n\nWith blocks becoming the new way to manage content in WordPress, more and more types of blocks are being developed to cater for different use cases and content types. In an effort to make it easier for content creators to find these block types, there is a proposal for a new type of plugin and a directory to handle it.
\n\n\n\nThe proposal outlines a new type of WordPress plugin that provides blocks and nothing else, named Single Block Plugins. The primary benefit would be to provide content creators with individual pieces of functionality and new types of blocks without the need to search for and install new plugins.
\n\n\n\nThe Single Block Plugins would be hosted in a separate Block Directory section of the Plugin Directory and they would initially be JavaScript-based. Each plugin will register a single block, and they will be searchable and installable from within the editor itself. This puts blocks at the publishers’ fingertips — you no longer have to leave the editor to find them.
\n\n\n\nWant to get involved in shaping this new type of plugin? Join in the conversation on the proposal post, follow the Meta team blog, and join the #meta channel in the Making WordPress Slack group.
\n\n\n\nOn 11 May 2019, the fourth Global WordPress Translation Day will take place. This is a 24-hour global event dedicated to the translation of all things WordPress, from core to themes, plugins to marketing.
\n\n\n\nOver the course of 24 hours, WordPress communities will meet to translate WordPress into their local languages and watch talks and sessions broadcast on wptranslationday.org. During the last Global WordPress Translation Day, 71 local events took place in 29 countries, and even more communities are expected to take part this time.
\n\n\n\nWant to get involved in the Global WordPress Translation Day? Find out how to organize a local event, apply to be a speaker, follow the updates on the Polyglots team blog, and join the #polyglots channel in the Making WordPress Slack group.
\n\n\n\nWith the block editor in WordPress Core, the team has been able to focus on adding some frequently requested features. Version 5.3 of Gutenberg, released this month, includes a new block manager modal, the ability to nest different elements in the cover block, and some UI tweaks to improve the hover state of blocks.
\n\n\n\nWant to get involved in developing Gutenberg? Check out the GitHub repository and join the #core-editor channel in the Making WordPress Slack group.
\n\n\n\nHave a story that we should include in the next “Month in WordPress” post? Please submit it here.
On March 25th, 2015, I published Rarst’s HeroPress essay “Finding Your Place“. It’s been four years.
\n\n\n\nAs of this post there are 165 essays published. 165 stories of dreams, successes, failures, and courage. 165 people I’ve gotten to know and love. It feels like it’s always been there.
\n\n\n\nFor a while this last year I only published once a month, so I could both focus on work a little more as well as draw attention to past essays. A few weeks ago I went back to weekly, and I’m happy with it. It’s exciting getting to know a new person every week. Not just meet them, but have good conversation and really get to know them.
\n\n\n\nI have some fun news. The other day Josepha The Magnificent approached me about syndicating HeroPress on https://wordpress.org/news/. It’s already on WordPress Planet (Thanks Matt!), which is the number one driver of traffic to this site, by FAR. I’ll be interested to see what being on /news does.
\n\n\n\nPeople often ask me about the future of HeroPress, but I don’t really see it changing much. Getting syndicated is nice, but doesn’t really change what I do or publish. We did a scholarship giveaway a couple years ago and we’ve discussed doing it again. I really enjoyed that, I’d welcome more things like it from other organizations.
\n\n\n\nTo all of you who’ve read over the years, I thank you. To all of you who’ve been transparent and had the courage to let the world see your story, I can’t thank you enough. Every time someone says to me “HeroPress is such an encouragement to me” it’s because of you.
\n\n\n\nHere’s to the future, and many more stories.
\nThe post Four Years 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:"Sat, 30 Mar 2019 02:49:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:62:"WPTavern: WordCamp Asia Proposed for 2020 in Bangkok, Thailand";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88339";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordcamp-asia-proposed-for-2020-in-bangkok-thailand";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2775:"photo credit: Eustaquio Santimano\nThe organizers of WordCamp Asia, a brand new regional WordCamp, have published a proposal for making Bangkok, Thailand, the host city for a 2-3 day event in early 2020. They are currently planning for February or March to avoid clashing with other regional WordCamps (WCEU, WCUS). The camp has been informally discussed since 2015 while organizers focused on growing new city-based WordCamps across the region.
\n“WordCamps in Asia have reached a critical mass that will enable a successful regional WordCamp,” Jon Ang said in the introduction to the proposal. “We believe that running this WordCamp will contribute directly to long term efforts in fostering WordPress interest in countries that lack it.”
\nWordCamp Asia organizers are being mentored by lead organizers of WordCamp Europe and have created an official proposal based heavily on the one submitted by WordCamp Nordic organizers. They have submitted it to the broader WordCamp community leaders for review before submitting and official application to WordCamp Central.
\nAsia has many vibrant and diverse WordPress communities across distant geographical areas. It technically includes Middle Eastern countries such as Turkey, Israel, and Iran, as well as all of Russia and India and everything in between.
\nHugh Lashbrooke commented on the proposal, asking if it is actually a “WordCamp South-East Asia,” given all the currently listed organizers are from this region, or if they intend to include other countries beyond this area. Ang said that the event will certainly include leaders from India and Pakistan and they have discussed forming a global team with two representatives from each country. The leaders currently listed in the proposal are those who were specifically involved in drafting it.
\nBangkok is proposed for the first host city due to its relatively affordable location, the ease of obtaining a visa on arrival for attendees from many Asian counties, and the availability of inexpensive flights to most major cities in Asia. The local WordPress community is also experienced at running large WordCamps (500+ attendees) and Bangkok’s local meetup group has more than 1,500 members. WordCamp Asia organizers are planning for 750-1,000 attendees.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 29 Mar 2019 20:19:24 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:38;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:116:"WPTavern: New Gutenberg Playground Offers a Standalone Version of the Editor for Testing Outside the WordPress Admin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88324";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:127:"https://wptavern.com/new-gutenberg-playground-offers-a-standalone-version-of-the-editor-for-testing-outside-the-wordpress-admin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1992:"The Gutenberg team merged a pull request three days ago that adds a local “playground” development environment for testing outside of the WordPress admin. Riad Benguella, the technical lead for Gutenberg phase 2, said that the playground could grow over time to contain “more than just a standalone version of the editor” and could become a way for developers to test out components in isolation. He shared a screenshot of the playground in action:
\n\nDuring Tuesday’s JavaScript chat meeting, Benguella elaborated on the playground’s intended use.
\n“Now that we’re expanding the usage of Gutenberg outside of the edit-post and also talking about cross-CMS usage and external usage (in the broad sense), we need a way to run the block editor in a context independent from the WordPress Admin. This means no WordPress admin styles, no API.”
\nTesting Gutenberg in the playground’s “no-context” mode allows developers to ensure their components don’t rely on WP-Admin styles to be present. Benguella said it demonstrates how core blocks can be used without requiring a post object, which will be useful for architecting the widgets screen.
\n“This playground could evolve to contain examples of our reusable components (think Storybook),” Benguella said. “It could also serve as a contributor tool. For example, we could include a way to search for selectors.”
\nThe playground was just merged this week, so contributors are working on better documentation. In the meantime, check out the PR for more details on how to test 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:"Thu, 28 Mar 2019 20:04:10 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:113:"WPTavern: WordPress 5.2 Beta 1 Released: Help Test New Blocks, Block Manager, and Improved Fatal Error Protection";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88304";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:121:"https://wptavern.com/wordpress-5-2-beta-1-released-help-test-new-blocks-block-manager-and-improved-fatal-error-protection";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3149:"WordPress 5.2 beta 1 was released this evening with an exciting lineup of new user-facing features that are ready for testing. The upcoming release introduces new blocks for RSS, Search, Calendar, Tag Cloud, and Amazon Kindle embed.
\nThe proliferation of block collection plugins as a block distribution mechanism has caused some WordPress installations to become bloated with too many unused blocks. Version 5.2 includes new block management capabilities that will make it easy to turn blocks on or off and tidy up the block inserter tool for greater efficiency.
\nThis release also introduces fatal error protection that catches errors before they produce a white screen, so that users can still log into the admin to attempt to resolve the issue. This feature was previously targeted for 5.1 but needed a few security issues ironed out before it was ready for core.
\nIf you’re just getting started with testing WordPress, the 5.2 beta is a very approachable release with features that anyone can put through the paces. The easiest way is to install the WordPress Beta Testing plugin and select “bleeding edge nightlies.” Try out the new blocks, experiment with turning blocks and and off. Do the new features seem like they work as advertised? Are there any bumps in the road when trying to use them? You can report any issues to the Alpha/Beta area in the support forums or log a ticket on trac.
\nDevelopers have a few big items to test as well. Plugin authors can now specify a minimum PHP version that the plugin will support. WordPress is also adding the sodium_compat library, a libsodium-compatible cryptography API for PHP 7.2+.
\nAccording to the notes from today’s core developer chat, there are currently 116 open tickets that contributors plan to address in three betas. The goal is to slash that number down to 66 before beta 2. WordPress 5.2 is targeted for April 30, 2019.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 28 Mar 2019 03:36:04 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:40:"WordPress.org blog: WordPress 5.2 Beta 1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=6798";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2019/03/wordpress-5-2-beta-1/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6940:"WordPress 5.2 Beta 1 is now available!
\n\n\n\nThis software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site to play with the new version.
\n\n\n\nYou can test the WordPress 5.2 Beta two ways:
\n\n\n\nWordPress 5.2 is slated for release on April 30, and we need your help to get there. Here are some of the big items to test so we can find as many bugs as possible in the coming weeks.
\n\n\n\nThe block editor has received significant performance improvements since WordPress 5.1, shaving 35% off the load time for massive posts, and cutting the keypress time (how responsive it feels when you’re typing) in half!
\n\n\n\nAccessibility continues to improve, too. The block editor now supports your browser’s reduced motion settings. The post URL slug has better labelling and help text. The focus styling for keyboard navigating through landmarks is clearer and more consistent. There are a variety of new speak messages, and existing messages have been tweaked for more useful screen-reader behaviour.
\n\n\n\nWe’ve added several new blocks:
\n\n\n\nTo help you keep track of these blocks, and only show the ones you need, there’s a new block management tool to switch blocks on and off.
\n\n\n\nBlock Management Modal\n\n\n\nWe’re constantly working on existing blocks, too. There are hundreds of bug fixes and improvements in the block editor, you can read more about them in the Gutenberg plugin releases: 4.9, 5.0, 5.1, 5.2, and 5.3.
\n\n\n\nThe block editor isn’t just for websites, either. The WordPress mobile apps now include an experimental version of a built-in block editor. This is still under development, but you can try it out now!
\n\n\n\n \n\n\n\nSite Health Check is an ongoing project aimed at improving the stability and performance of the entire WordPress ecosystem.
\n\n\n\nThe first phase of this project (originally scoped for WordPress 5.1) is now included in WordPress 5.2. For the first time, WordPress will catch and pause the problem code, so you can log in to your Dashboard and see what the problem is (#44458). Before, you’d have to FTP in to your files or get in touch with your host.
\n\n\n\n \n\n\n\nIn addition, we’re adding a new Health Check tool to your Dashboard. Visit the Tools menu and click on Health Check to get information that can help improve the speed and security of your site.
\n\n\n\nWith this release, WordPress will increase its minimum supported PHP version to 5.6. To help you check if you’re prepared for this change, WordPress 5.2 will show you a warning and help you upgrade your version of PHP, if necessary.
\n\n\n\nsodium_compat
library, which provides backwards compatibility for the Sodium-based cryptography library added in PHP 7.2. (#45806)get_search_form()
, improving accessibility. (#42057)There have been 130 tickets closed in WordPress 5.2 so far, with numerous small bug fixes and improvements to help smooth your WordPress experience.
\n\n\n\nKeep your eyes on the Make WordPress Core blog for developer notes (which are assigned the dev-notes
tag) in the coming weeks detailing other changes in 5.2 that you should be aware of.
Do you speak a language other than English? Help us translate WordPress into more than 100 languages!
\n\n\n\nIf you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.
\n\n\n\nWith each new release,
bearing multiple betas;
We fix, then we fly.
rtCamp, a 60+ person agency and WordPress.com VIP service partner, has released three new GitHub Actions that handle automated code review, WordPress deployment, and Slack notifications.
\nThe PHPCS Code Review action takes advantage of GitHub’s pull request review feature. It performs an automated code review on pull requests using PHPCS. This Action is based on WordPress.com VIP’s GPL-licensed review scripts.
\n\n“Our action is a wrapper around the original vip-go-ci project,” rtCamp CEO Rahul Bansal said. “VIP’s project uses Teamcity which is expensive and very hard to get up and running. We built a wrapper around it to get it working with Github. Still huge props to them for sharing what we consider to be the USP of the VIP platform to the public at large.”
\nThe Deploy WordPress GitHub action uses the Deployer.org tool to deploy code changes. Using it requires your git repo to match rtCamp’s WordPress Skeleton which is very similar to the VIP Go Skeleton. The action includes optional support for Hashicorp Vault, which is useful for managing multiple servers.
\n“Our action supports secrets fetching via HashiCorp Vault project,” Bansal said. “For small teams or indies using Vault might be overkill. But at scale, such as our hosting dept, where they are responsible for more than 100+ servers, Vault streamlines WordPress Deploys. It’s partly because of Vault, devs can simply change the hostname on the fly and everything still works.”
\nrtCamp has also released a GitHub action called Slack Notify that sends a message to a Slack channel. It can be customized to notify a channel about deployment status. The Site and SSH Host details are available if the action is run following the Deploy WordPress GitHub action. All three of the new Actions are designed to work seamlessly together.
\nrtCamp plans to add more Actions to its GitHub Actions Library in the future. Bansal said they are currently working on build actions to cover Sass, Webpack, and Grunt, as well as Testing actions for phpunit and QUnit. Further down the road they are planning to build an action that will automatically update their theme and plugin products in their EDD store when there is a GitHub 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:"Wed, 27 Mar 2019 22:46: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: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:81:"WPTavern: How Will Gutenberg Phase 4 Impact Multilingual Solutions for WordPress?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88262";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:91:"https://wptavern.com/how-will-gutenberg-phase-4-impact-multilingual-solutions-for-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3056:"During the 2018 State of the Word address, Matt Mullenweg announced that Phase 4 of the Gutenberg project would be aimed at developing an official way for WordPress to support multilingual sites. There are no technical details available yet for what approach core will take, because it’s still in the experimental stage. The site building objectives in Phase 2 are currently the primary focus of the Gutenberg team.
\nAlthough Phase 4 is still a long way off (targeted for 2020 and beyond), WordPress multilingual product owners are starting to speculate about the impact of core offering its own standardized solution for multilingual sites. At WordCamp Nordic I had a quick chat with Robert Windisch, CIO of Inpsyde, a large WordPress agency in Germany and the creators of the MultilingualPress plugin.
\nWindisch predicts a culling of the multilingual solutions for WordPress after Phase 4, in the same way that Gutenberg has challenged page builders. Maintaining a plugin with thousands of users takes a toll on a company, because users require support and product owners need to have a way to continue offering something that isn’t already available by default in core.
\n“It’s the same with Gutenberg and all the page builders,” Windisch said. “You need to adapt. If core tackles 80-90% of the features the plugin does, then I’m sure some will decide to pursue other roads or extend core features with a new plugin.”
\nWindisch doesn’t see any issues for his company’s multilingual solution because of how it is architected to closely align with WordPress core in its use of multisite. The MultilingualPress website advertises the product as having “future-proof, WordPress core-based architecture.” Windisch said that big agencies and companies with local sites tend to opt for MultilingualPress’ solution because of the separation of access that multisite provides.
\nAfter some consideration, he said he found that Mullenweg’s timeline for getting multilingual support in core made sense, because existing solutions mean there is no pressing need to provide this functionality.
\n“Currently nobody waits for the multilingual in core, because there are already solutions out there,” Windisch said. “There’s not really the pressure to have it right now.”
\nCheck out the quick interview below to hear more thoughts on how Gutenberg Phase 4 may impact other multilingual solutions:
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 26 Mar 2019 19:00:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"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: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:49:"WPTavern: Codecademy Launches New Free PHP Course";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=88229";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:60:"https://wptavern.com/codecademy-launches-new-free-php-course";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2262:"Codecademy introduced a new free course today called Learn PHP. The company, which offers free coding courses, is rebuilding its PHP education after removing all of its PHP courses in 2017.
\nA Codecademy representative explained that the courses were outdated and that their team thought PHP was declining in popularity:
\n\nThe PHP courses were very old, buggy, and outdated. They were the least used courses on Codecademy by far, and declining in use all the time, just as PHP itself is declining in popularity in the web development world. Student demand was far higher towards making, for example, more content in other languages like JavaScript or offer all-new languages like C#, rather than continuing to maintain PHP. Continued support and maintenance of any course for us costs money, and hiring PHP specialists to rewrite a course costs more money, but the market for PHP is very small. So, the decision was clear – to sunset this course.
PHP was created in 1994 by Rasmus Lerdorf, and it is still going strong 25 years later. Roughy 80% of websites run on PHP. Redmonk’s 2019 language rankings put PHP at #4 behind JavaScript, Java, and Python, based on data from GitHub and Stack Overflow.
\nCodecademy’s new Learn PHP course offers users an introduction to the fundamentals of PHP with language-specific syntax. Prerequisites include basic HTML. Students will learn about PHP variables and the string and number data types. Codecademy Pro users will get more quizzes and will create a portfolio project to showcase their new skills, but the basic course is free. The course currently takes approximately three hours to complete, and the company plans to add more content 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:"Tue, 26 Mar 2019 00:26: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:112:"WPTavern: Gutenberg Cloud Team Advocates for Making WordPress.org’s New Block Directory a CMS-Agnostic Library";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88181";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:120:"https://wptavern.com/gutenberg-cloud-team-advocates-for-making-wordpress-orgs-new-block-directory-a-cms-agnostic-library";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4955:"\nFrontkom‘s presentation at WordCamp Nordic introduced the audience to the Gutenberg Cloud project, which allows developers to share JS-only blocks across CMS platforms. Marco Fernandes and Thor Andre Gretland, representatives of the 45-person agency based in Europe, are also part of the Drupal Gutenberg project that brings WordPress’ open source editor to Drupal via an optional module. The module’s release candidate has been downloaded more than 9,000 times.
\nIn the video below, I had the opportunity to sit down with the team at WordCamp Nordic to discuss the progress on their Gutenberg-related projects. Frontkom has clients using the Drupal module in production and their experience echoes a theme that seems common among those who are using the Gutenberg editor with clients.
\n“We see that especially people who don’t have too much experience in general working with visual content online, they find it easier to use than the ones that are into a routine where they expect some behavior,” Gretland said.
\nDrupal’s Gutenberg module could become a primary driver for the Gutenberg Cloud project, as access to the cloud blocks is included by default for all installations. The Cloud Blocks plugin for WordPress has been much less popular so far, with an estimated 100 active installations.
\nWe discussed the potential of Drupal adopting Gutenberg as its core editor and the Frontkom team predicts that it will likely remain a separate module. Their vision for both Drupal Gutenberg and the Gutenberg Cloud is to make Gutenberg “the go-to solution for editing rich content on the web.” It is still achievable as a separate module but would have more impetus behind it if Drupal adopted it for its default editor.
\nGretland said idea behind the Gutenberg Cloud was to provide “a sustainable ecosystem of blocks but also ease of use.” The project is a precursor to WordPress.org’s planned JS-only single block library. We discussed whether they perceive any competition between the two directories.
\nAs the discussion on make.wordpress.org was just developing at the time of the interview, I contacted Frontkom CTO Per Andre Rønsen later on to get their thoughts on WordPress.org’s planned block directory. He had commented on the proposal, asking if this could become a library of truly CMS-agnostic blocks.
\n“I commented on the Make WP blog post right away, because I simply loved the idea of a directory of JS-only blocks,” Rønsen said. “We haven’t discussed it directly with Matt, but have had some good chats with the core Gutenberg team, and are planning to meet on a weekly basis. If Gutenberg Cloud can serve as a proof of concept that WP.org can later adopt as their own, we are happy. As the spec is very similar to what we already have created, porting between the two will be easy.”
\nRønsen is advocating for a more open approach that isn’t so strictly tied to WordPress’ infrastructure.
\n“A more ideal approach however, would be to merge the two efforts,” Rønsen said. “The key for us, is to make the infrastructure open to other communities, not just WP developers. We are happy to put our project in the hands of the WP core team – given that they share the same open vision.”
\nA CMS-agnostic library for Gutenberg blocks is part of Frontkom’s long term vision for improving the open web. This is one of reasons the team created Gutenberg.js, which provides a foundation for using Gutenberg on any CMS or framework. Gretland said they see it as “more than just a new editor but a platform that enables communities to build new features.” This is the vision the team came to share at WordCamp Nordic. Check out the video below to hear more about how the Gutenberg Cloud team is working to make Gutenberg an editor that more open source communities on the web can share.
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 25 Mar 2019 20:00:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:92:"WPTavern: WPWeekly Episode 349 – Sandy Edwards and the Kids Event Working Group Initiative";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wptavern.com/?p=88216&preview=true&preview_id=88216";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:99:"https://wptavern.com/wpweekly-episode-349-sandy-edwards-and-the-kids-event-working-group-initiative";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2166:"In this episode, John James Jacoby and I are joined by Sandy Edwards. Sandy gave us a behind the scenes look at what it takes to organize a WordPress event for children and teens.
\nShe also provides background information on a new group that’s been formed called the Kids Events Working Group. This group is responsible for setting the foundation for organizers to create and manage WordPress events geared towards children.
\nJohn recaps his experience at WordCamp Miami last weekend and we discussed some noteworthy news items.
\nWordPress 5.1.1 Patches Critical Vulnerability
\nDark Mode WordPress Plugin Up for Adoption
\n\n\nNext Episode: Wednesday, March 27th 3:00 P.M. Eastern
\nSubscribe to WordPress Weekly via Itunes
\nSubscribe to WordPress Weekly via RSS
\nSubscribe to WordPress Weekly via Stitcher Radio
\nSubscribe to WordPress Weekly via Google Play
\nListen To Episode #349:
\n
WordPress has officially ended support for PHP 5.2 – 5.5 and bumped its minimum required PHP version to 5.6. The plan announced last December was to bump the minimum required version in early 2019 and, depending on the results, bump it again to PHP 7 in December 2019. Sites on PHP 5.5 or earlier can still get security updates but will not be able to upgrade to the latest major WordPress version.
\nToday only 2% of WordPress sites remain on PHP 5.2. Roughly 20% are on versions 5.5 or earlier. Nearly half of WordPress installs are on PHP 7.0+.
\n\nOne might wonder why WordPress’ approach isn’t to just bump it all the way up to PHP 7. With its influence and dominant market share, this requirement would inevitably force users to get on board. However, WordPress contributors believe in supporting users who, for whatever reason, need more help upgrading PHP. Steamrolling this requirement has not been the WordPress way, despite years of immense pressure from the developer community.
\n“Leaving users behind for technical reasons creates a two-folded web with only few being able to leverage its power,” WordPress Core Committer Felix Arntz said. “Collaborating with and supporting these users gives that power to everyone in the long run.”
\nGary Pendergast shared a few stats about how effective WordPress 5.1’s PHP update notice has been in prodding site owners to get on newer versions of PHP:
\n\nFor WordPress 5.0, sites updated their PHP version from PHP <= 5.6 to PHP 7+ at the rate of 1 basis point per day. That is, the percentage of WordPress 5.0 sites using PHP <= 5.6 dropped by 0.01 every day, prior to the release of WordPress 5.1.\n
\nFor WordPress 5.1 (after adding the update notice), that has increased to a steady 5 basis points per day. Doesn’t sounds like much? Every day, that’s hundreds of extra site owners choosing to go through the (frankly, terrifying) process of updating their PHP version. All they needed was a little extra nudge, and a little bit of information.
\nScary EOL notices and attitudes of “well, we’re just bumping our supported PHP version, too bad if you don’t know what to do next” don’t help. Giving people the information they need to help themselves works.
\nWordPress folks are doing our part to help clean up the ancient PHP installs that are still running a large percentage of the internet, and we’re find that this isn’t an insurmountable problem. It just requires a bit of patience and empathy to solve.
WordPress developers around the web sent out celebration tweets after the news was announced. Although PHP 5.6 is the new minimum required version for running WordPress, the project’s technical requirements page recommends users ask their hosts for PHP version 7.3 or greater. PHP 7+ offers massive performance gains for users and developers will be able to update their plugins to use more modern syntax.
\n\n\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 21 Mar 2019 04:10:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:84:"WPTavern: Gutenberg 5.3 Introduces Block Management, Adds Nesting to the Cover Block";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88148";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:94:"https://wptavern.com/gutenberg-5-3-introduces-block-management-adds-nesting-to-the-cover-block";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3894:"This is big news!!
\nWPGraphQL has a minimum requirement of PHP 5.6, so it couldn’t even be considered for core until now.
\nStill a ways to go before we’re ready for serious consideration, but pretty big news. https://t.co/gCbJM9VcRc
\n— GraphQL for WordPress (@wpgraphql) March 21, 2019
Gutenberg 5.3 was released today with basic block management, a feature that will be included in WordPress 5.2. It is a new modal that can be launched from the vertical ellipses menu, inspired by Rich Tabor’s CoBlocks implementation. Users can turn individual blocks on/off or even entire sections, such as Common Blocks, Formatting, and Embeds. Block management should help users avoid the bloat that happens when installing block collections with more blocks than they need.
\nThis version’s updates to the Cover Block make it possible to nest other blocks inside of it. Users can now add buttons, paragraphs, and headers to easily create a call to action. It’s not immediately evident that nesting blocks is possible, despite the floating inserter. It takes a little bit of time to discover that it is available. There are still some quirks with this feature, but overall it makes the Cover Block much more useful than previous versions.
\n\nA few contributors commenting on the Cover Block’s nesting PR said that it seems like the work on this iteration is essentially a light version of a section block. They questioned if it might be better to finish the work on the Section block (#4900) and build from there. Many developers and designers are eagerly awaiting the addition of a Section block to core, which will provide a standard for the plugin and theme industries to build on.
\n“I think the cover block has very specific functionality that the section may not have like the focal point selector,” Automattic JavaScript engineer Jorge Costa said. “It is also important to note that the adjustments we make here to the way nesting works will also benefit a future section. This also allows us to test nesting a little bit more, before going to the section block. I expect the section block to be widely used in the community and will probably serve as a basis for many things being built in the future so it is important that we get it right. Exploring in cover will contribute to that.”
\nGutenberg 5.3 adds an experimental Legacy Widget Block that allows existing WordPress widgets to be added as Gutenberg blocks. It offers a dropdown of available widgets. After selecting one, the block populates that area with the widget’s settings.
\n\nThis version also improves block outlines for the hover and selected states for a more accessible UI with less distraction. Performance benchmarks show a slight decrease in performance with Gutenberg 5.3. Check out the release post for a full list of enhancements and bug fixes. This is the last plugin release that will be rolled into the upcoming WordPress 5.2 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:"Wed, 20 Mar 2019 21:14:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:48;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:78:"HeroPress: Sometimes bad things that happen to you are good things in disguise";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:56:"https://heropress.com/?post_type=heropress-essays&p=2716";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:208:"https://heropress.com/essays/sometimes-bad-things-that-happen-to-you-are-good-things-in-disguise/#utm_source=rss&utm_medium=rss&utm_campaign=sometimes-bad-things-that-happen-to-you-are-good-things-in-disguise";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10468:"My Mom used to say that things you remember from your past the most are things that had an impact on who you are today. Negative or positive, they affected you in a way that helped create the person you are.
\nHer father said to her, “Jean, you are always welcome but leave your kids at home.” That I will remember until the day I die. Why? We were biracial. My mother (who was White) left her home in Virginia to run away to Cleveland with my father (who was Black, and from West Virginia) to get married. That was in 1956.
\nMy father left us when I was about 8. Left us high and dry. The only positive thing I remember that he gave me was a typewriter. He said to me, “Teach yourself how to type and you’ll always be able to make a living.” I didn’t realize he “gave me anything” until after he died.
\nAfter my second failed marriage, I moved my Mom in with me because she was ill. That was 2005 and that’s when my journey with WordPress began. I originally started using Joomla but found that it was too cumbersome to keep up-to-date because things needed to be done manually, whereas WordPress had this cool way of updating the plugins right inside the dashboard. I was hooked and left Joomla behind.
\nI went back to work full time at one of the local hospitals. But not even a year into it I quit.
\n\nOne morning as I am waiting for the home health aide to arrive, my Mom started to cry and said, “I don’t want to die alone.” I stopped and looked at her and said, “You aren’t going to die alone.”
That day, I got to work and one of the doctor’s pissed me off. I thought about what my Mom said and then starting thinking, “I don’t need this bullshit.” I went to my desk and started packing my things. My co-worker said, “What are you doing?” I said, “I quit.” She said, “What?” I said, “I quit.” The doctor ran out, “What are you doing and where are you going?” I said, “I quit, and you can kiss my ass!”
\nI got home too early and my Mom asks, “Why are you home?” I just stood there. She looked at me and said, “Did you quit?” I started laughing, “Yep sure did and told that doctor he could kiss my ass!” She started giggling! “We’ll be okay.” she said.
\nAt that moment I said I must take this hobby of building sites part time, to a full fledge business. I hunkered down in one of the upstairs bedrooms and started to write out my strategy. I had already completed a few small business websites, so I contacted them and from there and word of mouth, my business started to grow.
\nBut it wasn’t until after my Mom died that WordPress really saved my life.
\nWe were thick as thieves my Mom and me. She almost died having me. I had a sister (she died last April) but she wasn’t close to us and kept mainly to herself. But Mom and I…we were two peas in a pod all the way up to the day she died. I sat with her for five days in hospice and those were some of the longest days and nights of my life.
\n\nI felt like someone dropped a weight on my chest. I couldn’t breathe. I felt faint. I felt lost.
Thank God I had Buster, my dog. If it hadn’t been for him, I don’t know what I would have done. There was a night I just couldn’t bear not having my Mom. I had a bottle of Valium and thought, “I should just get it over with, go be with my Mom.” But I looked down at Buster and thought, “No one is going to take better care of him than me. I can’t do that to him.”
\nI struggled with depression. Slowly over time I couldn’t function to even work on projects. It finally got to a point where my gas was turned off in the winter and I didn’t have food. I was bundled up with blankets and small heaters in my house to stay warm.
\n\nEvery penny I got, was basically food for Buster. One time I went 5 days without food.
My car was repossessed. It was just crazy. Then I got evicted in mid-January 2013. Yep, evicted.
\nMy sister, who I wasn’t close to, had received a lump sum of money from Social Security. She sent money to me since I had cared for our Mom all that time by myself. I rented a van, packed up what I could fit in the U-Haul on my own and ended up at an Extended Stay hotel – in the middle of a blizzard. Left all my furniture behind because I didn’t have help.
\nI got to the hotel and sat there in the U-Haul. I looked in the mirror and said out loud, “How the fuck did you get here? You don’t even have a pot to piss in!” Buster sitting in the other seat looking at me like I was crazy. That’s when I knew I had hit rock bottom. Depression led me to the bottom.
\nBut… that was a good thing! I met a lot of wonderful people online. I joined a few WordPress groups, but mainly the StudioPress forum because I had been using their free themes when they were Revolution Two. Then they developed the Genesis Framework. Their old forum was a gold mine of information and the people were awesome. I learned so much from that forum.
\nEvery day from that point on was WordPress and Genesis. Meeting more people, learning more code. I was completely off the grid in that hotel room! No one here even knew where I was that’s how far off the grid I was. But sometimes, you must do that in order to focus and get back on track.
\n\nThere were a lot of bumps in that road the first year, too many to even write out in this essay, but I learned something from each bump.
My business grew from word-of-mouth, I started getting work from people who needed help who saw me on social media and through the forums. Work from people all over the world. It truly was exciting.
\nEach day is still WordPress and websites. Learning new things every day. Sitting with Slack windows open and chatting with other WordPress people online. It’s been my entire world since 2013 and pretty much my “Saving Grace” because I feel like I know some people online better than people right here in the same city where I live at. I lived in the hotel for 2 years. Not because I had to but because I wanted to.
\nThe WordPress community is awesome and giving. The Genesis community is the same. It feels like family and I’ve never met anyone in person but care so much about the people! I would hope that those who know me would feel the same.
\nA friend recently shared a quote by the author Dodinsky that started off, “A lot of walking away will do your life good.” But it was the end that really caught my attention and it said, “The more you walk away from things that poison your soul, the healthier your life will be.”
\nAnd that is so true. Healthier in a sense that I walked away from all the bad, negative things and people that were in my space. I was able to grieve and heal. Sometimes bad things that happen to you are good things in disguise.
\nWhat’s in my future? Well, one of my dreams is to get a Sprinter Van, have it customized for living on the road and drive cross country with Bella. Buster passed end of 2016 and Bella is my other life-saver. I’d love to drive cross country and stop and meet people I’ve met in the WordPress community. I know I can’t really make that happen, but I can dream, can’t I? LOL!
\nI’d love to follow you on Twitter. Follow me at @thecre8tivediva and I’ll follow you back!
\n \nThe post Sometimes bad things that happen to you are good things in disguise 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, 20 Mar 2019 12:00: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:12:"Anita Carter";s: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:122:"WPTavern: WordCamp Miami Draws 100+ for Kid’s Camp, Plans to Host Standalone Kid’s WordPress Conference in Summer 2019";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=88102";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:125:"https://wptavern.com/wordcamp-miami-draws-100-for-kids-camp-plans-to-host-standalone-kids-wordpress-conference-in-summer-2019";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4384:"The 11th edition of WordCamp Miami was held this past weekend, a three-day event that featured multiple learning workshops and six different tracks. The speaker ratio was 50% male and 50% female, and nearly half of the speakers were new to WordCamp Miami.
\n\n\n\nAnother great year of amazing, diverse speakers! #WCMIA #WordPress pic.twitter.com/e2smmCpPAF
\n— WordCamp Miami (@wordcampmiami) March 17, 2019
One of the highlights of this year’s event were the WordPress stories coming out of the Kid’s Panel. WordCamp Miami has been hosting learning experiences for kids since 2014 and for the past four years has included a two-day Kid’s Camp along with a Kid’s Panel. More than 100 children (not including parents and guardians) attended this year’s event. Some of the kids who are more experienced with WordPress shared their experiences during the Kid’s Panel.
\nKids reported that they using WordPress for blogs, science projects, and robotic competitions. One fifth grade student, who has been using WordPress for three years, said she plans to continue using it to document her life and share her future educational experiences:
\n“I plan to be using it later in my life when I go to college, so I can be talking about what my life journey was and what I’m going to be studying, which is software engineering.”
\n\n\n\nListen to how a 4th grader explains why she likes using #WordPress. #WCMIA pic.twitter.com/Zd5cRP3Afg
\n— David Bisset (@dimensionmedia) March 17, 2019
The growing popularity of WordCamp Miami’s kids events has inspired organizers to host a new one-day event for kids and teachers. The date has not yet been set but the plan is to have it scheduled for summer 2019.
\nThe event will be divided into two tracks, one for kids aged 6 to 18 and another for teachers and educators. The kid’s track will include talks on WordPress, MineCraft, STEAM/STEM activities, and ways they can improve their coding skills. Teachers and educators will have a dedicated track with talks that will help them incorporate coding, WordPress, and broader STEAM/STEM activities into their curricula.
\nIn their announcement, WordCamp Miami’s organizers said they believe the next generation of WordPress users are “vital to the growth of the open web.” They are looking for sponsors to cover the costs of snacks and lunch for approximately 100 students, volunteers and speakers to give presentations on various subjects for kids and teachers, and people to spread the word to schools in the Dade/Broward area.
\nKids engaging with WordPress is one of the most inspiring things happening in the community right now. It’s the spark of a new generation of users who are embracing the concept of sharing their ideas on the open web. WordPress’ Community team also has a new Kids Event Working Group that kicked off last month to support the growth of these kinds of events around the world. They are currently working on documentation, training guides, legal documents, supply lists, and other resources. This is another way to get involved if you don’t live near a local kid’s event.
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Mar 2019 00:57:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Thu, 25 Apr 2019 11:41:04 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Thu, 25 Apr 2019 11:30:09 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:9:"HIT ord 1";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20130910200210";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (263, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1556235667', 'no'), (264, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1556192467', 'no'), (265, '_transient_timeout_dash_v2_5438fb5baf31c513fff2b9a1067656a6', '1556235667', 'no'), (266, '_transient_dash_v2_5438fb5baf31c513fff2b9a1067656a6', ' ', 'no'), (267, '_site_transient_timeout_browser_046e6917d0cffe5eff9ed704d17c7159', '1556799230', 'no'), (268, '_site_transient_browser_046e6917d0cffe5eff9ed704d17c7159', 'a:10:{s:4:"name";s:6:"Chrome";s:7:"version";s:13:"73.0.3683.103";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'), (269, '_transient_doing_cron', '1558539027.7823789119720458984375', 'yes'), (270, 'auto_updater.lock', '1558539041', 'no'); -- -------------------------------------------------------- -- -- Table structure for table `wp_postmeta` -- CREATE TABLE IF NOT EXISTS `wp_postmeta` ( `meta_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_id` bigint(20) unsigned NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_520_ci, PRIMARY KEY (`meta_id`), KEY `post_id` (`post_id`), KEY `meta_key` (`meta_key`(191)) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=279 ; -- -- Dumping data for table `wp_postmeta` -- INSERT INTO `wp_postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES (1, 2, '_wp_page_template', 'default'), (2, 3, '_wp_page_template', 'default'), (3, 5, '_edit_lock', '1556192483:1'), (4, 5, '_edit_last', '1'), (5, 5, '_content_layout', 'global'), (6, 5, '_content_padding', 'both'), (7, 5, '_content_side_padding', 'both'), (8, 5, '_widget_area', 'G'), (9, 5, '_sidebar_to_show', 'default'), (10, 5, '_content_under_header', 'G'), (11, 5, '_horizontal_header_show_header_at', '0'), (12, 5, '_subtitle', ''), (13, 5, '_title_bar_settings', 'global'), (14, 5, '_title_bar_position', 'outside'), (15, 5, '_title_bar_variant', 'classic'), (16, 5, '_title_bar_width', 'full'), (17, 5, '_title_bar_image_fit', 'repeat'), (18, 5, '_title_bar_parallax', 'off'), (19, 5, '_title_bar_parallax_type', 'tb'), (20, 5, '_title_bar_parallax_speed', '1.00'), (21, 5, '_title_bar_bg_color', ''), (22, 5, '_title_bar_title_color', ''), (23, 5, '_title_bar_color_1', ''), (24, 5, '_title_bar_space_width', '40px'), (25, 5, '_breadcrumbs', 'on'), (26, 5, '_image_or_video', 'post_image'), (27, 5, '_image_parallax', 'off'), (28, 5, '_image_parallax_height', '260px'), (29, 5, '_post_video', ''), (30, 5, '_page_bg_settings', 'global'), (31, 5, '_page_image', ''), (32, 5, '_page_image_fit', 'cover'), (33, 5, '_page_bg_color', ''), (34, 5, '_content_sticky_one_page', 'off'), (35, 5, '_content_sticky_one_page_bullet_color', 'rgba(0,0,0,1)'), (36, 5, '_content_sticky_one_page_bullet_icon', ''), (38, 10, '_wp_trash_meta_status', 'publish'), (39, 10, '_wp_trash_meta_time', '1554605422'), (40, 2, '_edit_lock', '1554605524:1'), (41, 12, '_wp_attached_file', '2019/04/1.jpg'), (42, 12, '_wp_attachment_metadata', 'a:5:{s:5:"width";i:1404;s:6:"height";i:870;s:4:"file";s:13:"2019/04/1.jpg";s:5:"sizes";a:4:{s:9:"thumbnail";a:4:{s:4:"file";s:13:"1-150x150.jpg";s:5:"width";i:150;s:6:"height";i:150;s:9:"mime-type";s:10:"image/jpeg";}s:6:"medium";a:4:{s:4:"file";s:13:"1-300x300.jpg";s:5:"width";i:300;s:6:"height";i:300;s:9:"mime-type";s:10:"image/jpeg";}s:12:"medium_large";a:4:{s:4:"file";s:13:"1-768x475.jpg";s:5:"width";i:768;s:6:"height";i:475;s:9:"mime-type";s:10:"image/jpeg";}s:5:"large";a:4:{s:4:"file";s:15:"1-1024x1024.jpg";s:5:"width";i:1024;s:6:"height";i:1024;s:9:"mime-type";s:10:"image/jpeg";}}s:10:"image_meta";a:12:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";s:11:"orientation";s:1:"0";s:8:"keywords";a:0:{}}}'), (43, 2, '_edit_last', '1'), (44, 2, '_content_layout', 'global'), (45, 2, '_content_padding', 'both'), (46, 2, '_content_side_padding', 'both'), (47, 2, '_widget_area', 'G'), (48, 2, '_sidebar_to_show', 'default'), (49, 2, '_content_under_header', 'G'), (50, 2, '_horizontal_header_show_header_at', '0'), (51, 2, '_subtitle', ''), (52, 2, '_title_bar_settings', 'global'), (53, 2, '_title_bar_position', 'outside'), (54, 2, '_title_bar_variant', 'classic'), (55, 2, '_title_bar_width', 'full'), (56, 2, '_title_bar_image_fit', 'repeat'), (57, 2, '_title_bar_parallax', 'off'), (58, 2, '_title_bar_parallax_type', 'tb'), (59, 2, '_title_bar_parallax_speed', '1.00'), (60, 2, '_title_bar_bg_color', ''), (61, 2, '_title_bar_title_color', ''), (62, 2, '_title_bar_color_1', ''), (63, 2, '_title_bar_space_width', '40px'), (64, 2, '_breadcrumbs', 'on'), (65, 2, '_image_or_video', 'post_image'), (66, 2, '_image_parallax', 'off'), (67, 2, '_image_parallax_height', '260px'), (68, 2, '_post_video', ''), (69, 2, '_page_bg_settings', 'global'), (70, 2, '_page_image', ''), (71, 2, '_page_image_fit', 'cover'), (72, 2, '_page_bg_color', ''), (73, 2, '_content_sticky_one_page', 'off'), (74, 2, '_content_sticky_one_page_bullet_color', 'rgba(0,0,0,1)'), (75, 2, '_content_sticky_one_page_bullet_icon', ''), (76, 14, '_menu_item_type', 'taxonomy'), (77, 14, '_menu_item_menu_item_parent', '0'), (78, 14, '_menu_item_object_id', '3'), (79, 14, '_menu_item_object', 'category'), (80, 14, '_menu_item_target', ''), (81, 14, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (82, 14, '_menu_item_xfn', ''), (83, 14, '_menu_item_url', ''), (85, 14, '_a13_mega_menu', ''), (86, 14, '_a13_mm_remove_item', ''), (87, 14, '_a13_mm_html', ''), (88, 14, '_a13_item_icon', ''), (89, 14, '_a13_unlinkable', ''), (90, 15, '_menu_item_type', 'taxonomy'), (91, 15, '_menu_item_menu_item_parent', '0'), (92, 15, '_menu_item_object_id', '2'), (93, 15, '_menu_item_object', 'category'), (94, 15, '_menu_item_target', ''), (95, 15, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (96, 15, '_menu_item_xfn', ''), (97, 15, '_menu_item_url', ''), (99, 15, '_a13_mega_menu', ''), (100, 15, '_a13_mm_remove_item', ''), (101, 15, '_a13_mm_html', ''), (102, 15, '_a13_item_icon', ''), (103, 15, '_a13_unlinkable', ''), (104, 16, '_menu_item_type', 'taxonomy'), (105, 16, '_menu_item_menu_item_parent', '0'), (106, 16, '_menu_item_object_id', '6'), (107, 16, '_menu_item_object', 'category'), (108, 16, '_menu_item_target', ''), (109, 16, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (110, 16, '_menu_item_xfn', ''), (111, 16, '_menu_item_url', ''), (113, 16, '_a13_mega_menu', ''), (114, 16, '_a13_mm_remove_item', ''), (115, 16, '_a13_mm_html', ''), (116, 16, '_a13_item_icon', ''), (117, 16, '_a13_unlinkable', ''), (118, 17, '_menu_item_type', 'taxonomy'), (119, 17, '_menu_item_menu_item_parent', '0'), (120, 17, '_menu_item_object_id', '5'), (121, 17, '_menu_item_object', 'category'), (122, 17, '_menu_item_target', ''), (123, 17, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (124, 17, '_menu_item_xfn', ''), (125, 17, '_menu_item_url', ''), (127, 17, '_a13_mega_menu', ''), (128, 17, '_a13_mm_remove_item', ''), (129, 17, '_a13_mm_html', ''), (130, 17, '_a13_item_icon', ''), (131, 17, '_a13_unlinkable', ''), (132, 18, '_menu_item_type', 'taxonomy'), (133, 18, '_menu_item_menu_item_parent', '0'), (134, 18, '_menu_item_object_id', '4'), (135, 18, '_menu_item_object', 'category'), (136, 18, '_menu_item_target', ''), (137, 18, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (138, 18, '_menu_item_xfn', ''), (139, 18, '_menu_item_url', ''), (141, 18, '_a13_mega_menu', ''), (142, 18, '_a13_mm_remove_item', ''), (143, 18, '_a13_mm_html', ''), (144, 18, '_a13_item_icon', ''), (145, 18, '_a13_unlinkable', ''), (146, 19, '_menu_item_type', 'post_type'), (147, 19, '_menu_item_menu_item_parent', '0'), (148, 19, '_menu_item_object_id', '5'), (149, 19, '_menu_item_object', 'page'), (150, 19, '_menu_item_target', ''), (151, 19, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (152, 19, '_menu_item_xfn', ''), (153, 19, '_menu_item_url', ''), (155, 19, '_a13_mega_menu', ''), (156, 19, '_a13_mm_remove_item', ''), (157, 19, '_a13_mm_html', ''), (158, 19, '_a13_item_icon', ''), (159, 19, '_a13_unlinkable', ''), (160, 20, '_menu_item_type', 'post_type'), (161, 20, '_menu_item_menu_item_parent', '0'), (162, 20, '_menu_item_object_id', '2'), (163, 20, '_menu_item_object', 'page'), (164, 20, '_menu_item_target', ''), (165, 20, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (166, 20, '_menu_item_xfn', ''), (167, 20, '_menu_item_url', ''), (169, 20, '_a13_mega_menu', ''), (170, 20, '_a13_mm_remove_item', ''), (171, 20, '_a13_mm_html', ''), (172, 20, '_a13_item_icon', ''), (173, 20, '_a13_unlinkable', ''), (174, 20, '_a13_mm_columns', '2'), (175, 14, '_a13_mm_columns', '2'), (176, 15, '_a13_mm_columns', '2'), (177, 16, '_a13_mm_columns', '2'), (178, 17, '_a13_mm_columns', '2'), (179, 18, '_a13_mm_columns', '2'), (180, 19, '_a13_mm_columns', '2'), (181, 21, '_edit_lock', '1554605889:1'), (183, 21, '_edit_last', '1'), (185, 21, '_alt_link', ''), (186, 21, '_brick_ratio_x', '1'), (187, 21, '_image_or_video', 'post_image'), (188, 21, '_image_parallax', 'off'), (189, 21, '_image_parallax_height', '260px'), (190, 21, '_post_video', ''), (191, 21, '_content_under_header', 'G'), (192, 21, '_title_bar_settings', 'global'), (193, 21, '_title_bar_position', 'outside'), (194, 21, '_title_bar_variant', 'classic'), (195, 21, '_title_bar_width', 'full'), (196, 21, '_title_bar_image_fit', 'repeat'), (197, 21, '_title_bar_parallax', 'off'), (198, 21, '_title_bar_parallax_type', 'tb'), (199, 21, '_title_bar_parallax_speed', '1.00'), (200, 21, '_title_bar_bg_color', ''), (201, 21, '_title_bar_title_color', ''), (202, 21, '_title_bar_color_1', ''), (203, 21, '_title_bar_space_width', '40px'), (204, 21, '_breadcrumbs', 'on'), (205, 21, '_page_bg_settings', 'global'), (206, 21, '_page_image', ''), (207, 21, '_page_image_fit', 'cover'), (208, 21, '_page_bg_color', ''), (211, 31, '_edit_lock', '1554624937:1'), (212, 32, '_wp_attached_file', '2019/04/1-1.jpg'), (213, 32, '_wp_attachment_metadata', 'a:5:{s:5:"width";i:1404;s:6:"height";i:870;s:4:"file";s:15:"2019/04/1-1.jpg";s:5:"sizes";a:4:{s:9:"thumbnail";a:4:{s:4:"file";s:15:"1-1-150x150.jpg";s:5:"width";i:150;s:6:"height";i:150;s:9:"mime-type";s:10:"image/jpeg";}s:6:"medium";a:4:{s:4:"file";s:15:"1-1-300x300.jpg";s:5:"width";i:300;s:6:"height";i:300;s:9:"mime-type";s:10:"image/jpeg";}s:12:"medium_large";a:4:{s:4:"file";s:15:"1-1-768x475.jpg";s:5:"width";i:768;s:6:"height";i:475;s:9:"mime-type";s:10:"image/jpeg";}s:5:"large";a:4:{s:4:"file";s:17:"1-1-1024x1024.jpg";s:5:"width";i:1024;s:6:"height";i:1024;s:9:"mime-type";s:10:"image/jpeg";}}s:10:"image_meta";a:12:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";s:11:"orientation";s:1:"0";s:8:"keywords";a:0:{}}}'), (214, 33, '_wp_attached_file', '2019/04/微信截图_20190407161538.png'), (215, 33, '_wp_attachment_metadata', 'a:5:{s:5:"width";i:1208;s:6:"height";i:769;s:4:"file";s:39:"2019/04/微信截图_20190407161538.png";s:5:"sizes";a:4:{s:9:"thumbnail";a:4:{s:4:"file";s:39:"微信截图_20190407161538-150x150.png";s:5:"width";i:150;s:6:"height";i:150;s:9:"mime-type";s:9:"image/png";}s:6:"medium";a:4:{s:4:"file";s:39:"微信截图_20190407161538-300x300.png";s:5:"width";i:300;s:6:"height";i:300;s:9:"mime-type";s:9:"image/png";}s:12:"medium_large";a:4:{s:4:"file";s:39:"微信截图_20190407161538-768x488.png";s:5:"width";i:768;s:6:"height";i:488;s:9:"mime-type";s:9:"image/png";}s:5:"large";a:4:{s:4:"file";s:41:"微信截图_20190407161538-1024x1024.png";s:5:"width";i:1024;s:6:"height";i:1024;s:9:"mime-type";s:9:"image/png";}}s:10:"image_meta";a:12:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";s:11:"orientation";s:1:"0";s:8:"keywords";a:0:{}}}'), (216, 34, '_wp_attached_file', '2019/04/1.png'), (217, 34, '_wp_attachment_metadata', 'a:5:{s:5:"width";i:1208;s:6:"height";i:769;s:4:"file";s:13:"2019/04/1.png";s:5:"sizes";a:4:{s:9:"thumbnail";a:4:{s:4:"file";s:13:"1-150x150.png";s:5:"width";i:150;s:6:"height";i:150;s:9:"mime-type";s:9:"image/png";}s:6:"medium";a:4:{s:4:"file";s:13:"1-300x300.png";s:5:"width";i:300;s:6:"height";i:300;s:9:"mime-type";s:9:"image/png";}s:12:"medium_large";a:4:{s:4:"file";s:13:"1-768x488.png";s:5:"width";i:768;s:6:"height";i:488;s:9:"mime-type";s:9:"image/png";}s:5:"large";a:4:{s:4:"file";s:15:"1-1024x1024.png";s:5:"width";i:1024;s:6:"height";i:1024;s:9:"mime-type";s:9:"image/png";}}s:10:"image_meta";a:12:{s:8:"aperture";s:1:"0";s:6:"credit";s:0:"";s:6:"camera";s:0:"";s:7:"caption";s:0:"";s:17:"created_timestamp";s:1:"0";s:9:"copyright";s:0:"";s:12:"focal_length";s:1:"0";s:3:"iso";s:1:"0";s:13:"shutter_speed";s:1:"0";s:5:"title";s:0:"";s:11:"orientation";s:1:"0";s:8:"keywords";a:0:{}}}'), (219, 31, '_edit_last', '1'), (221, 31, '_alt_link', ''), (222, 31, '_brick_ratio_x', '1'), (223, 31, '_image_or_video', 'post_image'), (224, 31, '_image_parallax', 'off'), (225, 31, '_image_parallax_height', '260px'), (226, 31, '_post_video', ''), (227, 31, '_content_under_header', 'G'), (228, 31, '_title_bar_settings', 'global'), (229, 31, '_title_bar_position', 'outside'), (230, 31, '_title_bar_variant', 'classic'), (231, 31, '_title_bar_width', 'full'), (232, 31, '_title_bar_image_fit', 'repeat'), (233, 31, '_title_bar_parallax', 'off'), (234, 31, '_title_bar_parallax_type', 'tb'), (235, 31, '_title_bar_parallax_speed', '1.00'), (236, 31, '_title_bar_bg_color', ''), (237, 31, '_title_bar_title_color', ''), (238, 31, '_title_bar_color_1', ''), (239, 31, '_title_bar_space_width', '40px'), (240, 31, '_breadcrumbs', 'on'), (241, 31, '_page_bg_settings', 'global'), (242, 31, '_page_image', ''), (243, 31, '_page_image_fit', 'cover'), (244, 31, '_page_bg_color', ''), (247, 39, '_edit_lock', '1556194767:1'), (249, 39, '_edit_last', '1'), (251, 39, '_alt_link', ''), (252, 39, '_brick_ratio_x', '1'), (253, 39, '_image_or_video', 'post_image'), (254, 39, '_image_parallax', 'off'), (255, 39, '_image_parallax_height', '260px'), (256, 39, '_post_video', ''), (257, 39, '_content_under_header', 'G'), (258, 39, '_title_bar_settings', 'global'), (259, 39, '_title_bar_position', 'outside'), (260, 39, '_title_bar_variant', 'classic'), (261, 39, '_title_bar_width', 'full'), (262, 39, '_title_bar_image_fit', 'repeat'), (263, 39, '_title_bar_parallax', 'off'), (264, 39, '_title_bar_parallax_type', 'tb'), (265, 39, '_title_bar_parallax_speed', '1.00'), (266, 39, '_title_bar_bg_color', ''), (267, 39, '_title_bar_title_color', ''), (268, 39, '_title_bar_color_1', ''), (269, 39, '_title_bar_space_width', '40px'), (270, 39, '_breadcrumbs', 'on'), (271, 39, '_page_bg_settings', 'global'), (272, 39, '_page_image', ''), (273, 39, '_page_image_fit', 'cover'), (274, 39, '_page_bg_color', ''), (277, 41, '_edit_lock', '1554625425:1'), (278, 46, '_edit_lock', '1556194321:1'); -- -------------------------------------------------------- -- -- Table structure for table `wp_posts` -- CREATE TABLE IF NOT EXISTS `wp_posts` ( `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `post_author` bigint(20) unsigned NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL, `post_parent` bigint(20) unsigned NOT NULL DEFAULT '0', `guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0', PRIMARY KEY (`ID`), KEY `post_name` (`post_name`(191)), KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), KEY `post_parent` (`post_parent`), KEY `post_author` (`post_author`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci AUTO_INCREMENT=47 ; -- -- Dumping data for table `wp_posts` -- INSERT INTO `wp_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, '2019-04-06 18:20:54', '2019-04-06 10:20:54', '\n欢迎使用WordPress。这是您的第一篇文章。编辑或删除它,然后开始写作吧!
\n', '世界,您好!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2019-04-06 18:20:54', '2019-04-06 10:20:54', '', 0, 'http://localhost/?p=1', 0, 'post', '', 1), (2, 1, '2019-04-06 18:20:54', '2019-04-06 10:20:54', '\n\n\n\n\n您可以在以上国家随意旅游。
\n\n\n\n我们有比较专业的推荐。
\n', '欢迎来到农校旅游', '', 'publish', 'closed', 'open', '', 'sample-page', '', '', '2019-04-07 10:54:10', '2019-04-07 02:54:10', '', 0, 'http://localhost/?page_id=2', 0, 'page', '', 0), (3, 1, '2019-04-06 18:20:54', '2019-04-06 10:20:54', '我们的站点地址是:http://localhost。
当访客留下评论时,我们会收集评论表单所显示的数据,和访客的IP地址及浏览器的user agent字符串来帮助检查垃圾评论。
由您的电子邮件地址所生成的匿名化字符串(又称为哈希)可能会被提供给Gravatar服务确认您是否有使用该服务。Gravatar服务的隐私政策在此:https://automattic.com/privacy/。在您的评论获批准后,您的资料图片将在您的评论旁公开展示。
如果您向此网站上传图片,您应当避免上传那些有嵌入地理位置信息(EXIF GPS)的图片。此网站的访客将可以下载并提取此网站的图片中的位置信息。
如果您在我们的站点上留下评论,您可以选择用cookies保存您的姓名、电子邮件地址和网站。这是通过让您可以不用在评论时再次填写相关内容而向您提供方便。这些cookies会保留一年。
如果您有此站点的账户并且您登录了此站点,我们会设置一个临时的cookie来确认您的浏览器是否接受cookies。此cookie不包含个人数据且会在您关闭浏览器时被丢弃。
当您登录时,我们也会设置多个cookies来保存您的登录信息及屏幕显示选项。登录cookies会保留两天,而屏幕显示选项cookies会保留一年。如果您选择了“记住我”,您的登录状态则会保留两周。如果您登出您的账户,用于登录的cookies将会被移除。
如果您编辑或发布文章,我们会在您的浏览器中保存一个额外的cookie。这个cookie不包含个人数据而只记录了您刚才编辑的文章的ID。这个cookie会保留一天。
此站点上的文章可能会包含嵌入的内容(如视频、图像、文章等)。来自其他站点的嵌入内容的行为和您直接访问这些其他站点没有区别。
这些站点可能会收集关于您的数据、使用cookies、嵌入额外的第三方跟踪程序及监视您与这些嵌入内容的交互,包括在您有这些站点的账户并登录了这些站点时,跟踪您与嵌入内容的交互。
如果您留下评论,评论和其元数据将被无限期保存。我们这样做以便能识别并自动批准任何后续评论,而不用将这些后续评论加入待审队列。
对于本网站的注册用户,我们也会保存用户在个人资料中提供的个人信息。所有用户可以在任何时候查看、编辑或删除他们的个人信息(除了不能变更用户名外)、站点管理员也可以查看及编辑那些信息。
如果您有此站点的账户,或曾经留下评论,您可以请求我们提供我们所拥有的您的个人数据的导出文件,这也包括了所有您提供给我们的数据。您也可以要求我们抹除所有关于您的个人数据。这不包括我们因管理、法规或安全需要而必须保留的数据。
访客评论可能会被自动垃圾评论监测服务检查。
联系地址:怀化职业技术学院
\n\n\n\n计应三班,易先生
\n\n\n\n联系我们的方式就是来怀化职业技术学院找我!
\n', '联系我们', '', 'inherit', 'closed', 'closed', '', '5-revision-v1', '', '', '2019-04-07 10:47:40', '2019-04-07 02:47:40', '', 5, 'http://localhost/2019/04/07/5-revision-v1/', 0, 'revision', '', 0), (10, 1, '2019-04-07 10:50:22', '2019-04-07 02:50:22', '{\n "blogname": {\n "value": "\\u519c\\u6821\\u65c5\\u6e38",\n "type": "option",\n "user_id": 1,\n "date_modified_gmt": "2019-04-07 02:50:22"\n },\n "blogdescription": {\n "value": "-\\u5feb\\u4e50\\u7684\\u65c5\\u6e38\\u7f51\\u7ad9",\n "type": "option",\n "user_id": 1,\n "date_modified_gmt": "2019-04-07 02:50:22"\n },\n "show_on_front": {\n "value": "page",\n "type": "option",\n "user_id": 1,\n "date_modified_gmt": "2019-04-07 02:50:22"\n },\n "page_on_front": {\n "value": "2",\n "type": "option",\n "user_id": 1,\n "date_modified_gmt": "2019-04-07 02:50:22"\n }\n}', '', '', 'trash', 'closed', 'closed', '', '1d3c06dc-4c10-490c-a535-e61b4dadf458', '', '', '2019-04-07 10:50:22', '2019-04-07 02:50:22', '', 0, 'http://localhost/2019/04/07/1d3c06dc-4c10-490c-a535-e61b4dadf458/', 0, 'customize_changeset', '', 0), (12, 1, '2019-04-07 10:53:15', '2019-04-07 02:53:15', '', '1', '', 'inherit', 'open', 'closed', '', '1', '', '', '2019-04-07 10:53:15', '2019-04-07 02:53:15', '', 2, 'http://localhost/wp-content/uploads/2019/04/1.jpg', 0, 'attachment', 'image/jpeg', 0), (13, 1, '2019-04-07 10:54:03', '2019-04-07 02:54:03', '\n\n\n\n\n您可以在以上国家随意旅游。
\n\n\n\n我们有比较专业的推荐。
\n', '欢迎来到农校旅游', '', 'inherit', 'closed', 'closed', '', '2-revision-v1', '', '', '2019-04-07 10:54:03', '2019-04-07 02:54:03', '', 2, 'http://localhost/2019/04/07/2-revision-v1/', 0, 'revision', '', 0), (14, 1, '2019-04-07 10:55:14', '2019-04-07 02:55:14', ' ', '', '', 'publish', 'closed', 'closed', '', '14', '', '', '2019-04-07 15:54:15', '2019-04-07 07:54:15', '', 0, 'http://localhost/?p=14', 2, 'nav_menu_item', '', 0), (15, 1, '2019-04-07 10:55:15', '2019-04-07 02:55:15', ' ', '', '', 'publish', 'closed', 'closed', '', '15', '', '', '2019-04-07 15:54:15', '2019-04-07 07:54:15', '', 0, 'http://localhost/?p=15', 3, 'nav_menu_item', '', 0), (16, 1, '2019-04-07 10:55:15', '2019-04-07 02:55:15', ' ', '', '', 'publish', 'closed', 'closed', '', '16', '', '', '2019-04-07 15:54:15', '2019-04-07 07:54:15', '', 0, 'http://localhost/?p=16', 4, 'nav_menu_item', '', 0), (17, 1, '2019-04-07 10:55:15', '2019-04-07 02:55:15', ' ', '', '', 'publish', 'closed', 'closed', '', '17', '', '', '2019-04-07 15:54:15', '2019-04-07 07:54:15', '', 0, 'http://localhost/?p=17', 5, 'nav_menu_item', '', 0), (18, 1, '2019-04-07 10:55:15', '2019-04-07 02:55:15', ' ', '', '', 'publish', 'closed', 'closed', '', '18', '', '', '2019-04-07 15:54:15', '2019-04-07 07:54:15', '', 0, 'http://localhost/?p=18', 6, 'nav_menu_item', '', 0), (19, 1, '2019-04-07 10:55:15', '2019-04-07 02:55:15', ' ', '', '', 'publish', 'closed', 'closed', '', '19', '', '', '2019-04-07 15:54:15', '2019-04-07 07:54:15', '', 0, 'http://localhost/?p=19', 7, 'nav_menu_item', '', 0), (20, 1, '2019-04-07 10:55:14', '2019-04-07 02:55:14', ' ', '', '', 'publish', 'closed', 'closed', '', '20', '', '', '2019-04-07 15:54:15', '2019-04-07 07:54:15', '', 0, 'http://localhost/?p=20', 1, 'nav_menu_item', '', 0), (21, 1, '2019-04-07 10:56:06', '2019-04-07 02:56:06', '\n①西安 千年古都
\n\n\n\n\n\n\n\n西安是一个历史文化底蕴深厚的城市 ,雄伟的古城、壮观的兵马俑、以及各种特色小吃,西安是中国最佳旅游目的地、中国国际形象最佳城市之一 ,有两项六处遗产被列入《世界遗产名录》,分别是:秦始皇陵及兵马俑、大雁塔、小雁塔、唐长安城大明宫遗址、汉长安城未央宫遗址、兴教寺塔。
\n\n\n\n西安的特色小吃也有很多:biangbiang面、饺子宴、秦镇凉皮、羊肉泡馍、老童家腊羊肉、锅盔、肉夹馍等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-10月,最适合出行。
\n\n\n\n②南京 六朝金粉地,金陵帝王州
\n\n\n\n\n\n\n\n“六朝古都”的沧桑洗礼,现代化都市的灿烂文明,让南京这座依山傍水的历史名城独具魅力。
\n\n\n\n南京的特色美食:金陵四大菜(松鼠鱼、美味肝、蛋烧卖、凤尾虾)、鸭血粉丝汤、盐水鸭、梅花糕、鸡汁汤包、桂花蜜汁藕等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-10月,春秋两季最为舒适。
\n\n\n\n③北京 举世无双的皇家建筑
\n\n\n\n\n\n\n\n北京最有皇家气息,是一座非常适合旅行和深度探索的城市。
\n\n\n\n北京的特色美食:北京烤鸭、涮羊肉、炸酱面、豆汁儿、卤煮火烧、炒肝儿、爆肚儿等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-11月,春秋两季最为舒适。
\n\n\n\n④苏州 苏州园林甲天下
\n\n\n\n\n\n\n\n苏州是一个备受宠爱的城市,江南的富庶延续至今“人间天堂”实至名归,你可以在写意园林中陶醉、为苏州博物馆点赞,品尝品味微甜的四季时鲜、听柔软婉转的昆曲评弹,夜宿小桥流水的江南古镇。
\n\n\n\n苏州的特色美食:松鼠桂鱼、碧螺虾仁、响油鳝糊、桂花鸡头米、生煎、藏书镇羊肉、阳澄湖大闸蟹等等。
\n\n\n\n\n\n\n\n最佳旅游时间:四季皆宜,春天最佳。
\n\n\n\n⑤大理 风花雪月地,山光水色城
\n\n\n\n\n\n\n\n大理山川秀丽、气候宜人,上关花、下关风、苍山雪、洱海月,构成了大理“四绝”,素有“东方瑞士”之称。
\n\n\n\n大理的特色美食:白族饵块、云南木瓜水、邓川乳扇、毫糯索、喜洲破酥粑粑、巍山耙肉饵丝、白族三道茶、大理生皮等等。
\n\n\n\n\n\n\n\n最佳旅游时间:大理四季如春,春秋两季最美。
\n\n\n\n⑥澳门 东方的“拉斯维加斯”
\n\n\n\n\n\n\n\n澳门位于中国东南沿海的珠江三角洲,距离香港只有1小时船程,这里有着亚洲“拉斯维加斯”的称号,澳门虽小,但是却有深厚的历史沉淀。
\n\n\n\n澳门的特色美食:猪扒包、葡式蛋挞、木糠布甸、大菜糕、金钱饼、竹升打面、水蟹粥、马介休、葡国鸡等等。
\n\n\n\n\n\n\n\n最佳旅游时间:10月—次年2月。
\n\n\n\n⑦丽江 有一段时光叫丽江
\n\n\n\n\n\n\n\n丽江有浓郁的民族风情、小桥流水式的布局、错落有致的居民建筑、还有散漫的生活节奏丰富的夜生活。
\n\n\n\n丽江的特色美食:腊排骨、黑山羊火锅、三文鱼、鸡豆凉粉、野生菌、汽锅鸡、酥油茶、杜鹃花炒蛋、纳西烤鱼、米灌肠、丽江粑粑等等。
\n\n\n\n\n\n\n\n最佳旅游时间:一年四季皆宜
\n\n\n\n⑧腾冲 极边第一城
\n\n\n\n\n\n\n\n腾冲城不大,但历史悠久,有着厚重的历史底蕴和很多人文景观建筑。
\n\n\n\n腾冲的特色美食:土锅子、三滴水、大救驾、饵丝、大薄片等等。
\n\n\n\n\n\n\n\n最佳旅游时间:一年四季都适合,11—12月初可以看到银杏的最佳季节。
\n\n\n\n⑨喀什 丝路明珠
\n\n\n\n\n\n\n\n喀什是中国最西端的一座城市,是中国对西方经济文化交流的交通枢纽与门户之地。
\n\n\n\n喀什的特色美食:羊肉串、凉粉、囊坑烤肉、酸奶、囊等等。
\n\n\n\n\n\n\n\n最佳旅游时间:8—10月最佳。
\n\n\n\n⑩伊犁 塞外江南
\n\n\n\n\n\n\n\n伊犁素有“塞外江南”、“瓜果之乡”的美称。这里雨水相对充沛,天气温润,被称为“瀚海湿岛”,草地、森林的植被覆盖率达67.7%。
\n\n\n\n伊犁的特色美食:卡瓦斯、熏肉和熏马肠、凉粉、马奶、纳仁、辣罐血肠等等。
\n\n\n\n\n\n\n\n最佳旅游时间:6—10月最佳,6月中旬是薰衣草盛开的季节,7月是油菜花盛开的季节。
\n', '强烈推荐10个国内旅游地', '', 'publish', 'open', 'open', '', '%e5%bc%ba%e7%83%88%e6%8e%a8%e8%8d%9010%e4%b8%aa%e5%9b%bd%e5%86%85%e6%97%85%e6%b8%b8%e5%9c%b0', '', '', '2019-04-07 10:58:08', '2019-04-07 02:58:08', '', 0, 'http://localhost/?p=21', 0, 'post', '', 0), (22, 1, '2019-04-07 10:56:06', '2019-04-07 02:56:06', '\n①西安 千年古都
\n\n\n\n\n\n\n\n西安是一个历史文化底蕴深厚的城市 ,雄伟的古城、壮观的兵马俑、以及各种特色小吃,西安是中国最佳旅游目的地、中国国际形象最佳城市之一 ,有两项六处遗产被列入《世界遗产名录》,分别是:秦始皇陵及兵马俑、大雁塔、小雁塔、唐长安城大明宫遗址、汉长安城未央宫遗址、兴教寺塔。
\n\n\n\n西安的特色小吃也有很多:biangbiang面、饺子宴、秦镇凉皮、羊肉泡馍、老童家腊羊肉、锅盔、肉夹馍等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-10月,最适合出行。
\n\n\n\n②南京 六朝金粉地,金陵帝王州
\n\n\n\n\n\n\n\n“六朝古都”的沧桑洗礼,现代化都市的灿烂文明,让南京这座依山傍水的历史名城独具魅力。
\n\n\n\n南京的特色美食:金陵四大菜(松鼠鱼、美味肝、蛋烧卖、凤尾虾)、鸭血粉丝汤、盐水鸭、梅花糕、鸡汁汤包、桂花蜜汁藕等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-10月,春秋两季最为舒适。
\n\n\n\n③北京 举世无双的皇家建筑
\n\n\n\n\n\n\n\n北京最有皇家气息,是一座非常适合旅行和深度探索的城市。
\n\n\n\n北京的特色美食:北京烤鸭、涮羊肉、炸酱面、豆汁儿、卤煮火烧、炒肝儿、爆肚儿等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-11月,春秋两季最为舒适。
\n\n\n\n④苏州 苏州园林甲天下
\n\n\n\n\n\n\n\n苏州是一个备受宠爱的城市,江南的富庶延续至今“人间天堂”实至名归,你可以在写意园林中陶醉、为苏州博物馆点赞,品尝品味微甜的四季时鲜、听柔软婉转的昆曲评弹,夜宿小桥流水的江南古镇。
\n\n\n\n苏州的特色美食:松鼠桂鱼、碧螺虾仁、响油鳝糊、桂花鸡头米、生煎、藏书镇羊肉、阳澄湖大闸蟹等等。
\n\n\n\n\n\n\n\n最佳旅游时间:四季皆宜,春天最佳。
\n\n\n\n⑤大理 风花雪月地,山光水色城
\n\n\n\n\n\n\n\n大理山川秀丽、气候宜人,上关花、下关风、苍山雪、洱海月,构成了大理“四绝”,素有“东方瑞士”之称。
\n\n\n\n大理的特色美食:白族饵块、云南木瓜水、邓川乳扇、毫糯索、喜洲破酥粑粑、巍山耙肉饵丝、白族三道茶、大理生皮等等。
\n\n\n\n\n\n\n\n最佳旅游时间:大理四季如春,春秋两季最美。
\n\n\n\n⑥澳门 东方的“拉斯维加斯”
\n\n\n\n\n\n\n\n澳门位于中国东南沿海的珠江三角洲,距离香港只有1小时船程,这里有着亚洲“拉斯维加斯”的称号,澳门虽小,但是却有深厚的历史沉淀。
\n\n\n\n澳门的特色美食:猪扒包、葡式蛋挞、木糠布甸、大菜糕、金钱饼、竹升打面、水蟹粥、马介休、葡国鸡等等。
\n\n\n\n\n\n\n\n最佳旅游时间:10月—次年2月。
\n\n\n\n⑦丽江 有一段时光叫丽江
\n\n\n\n\n\n\n\n丽江有浓郁的民族风情、小桥流水式的布局、错落有致的居民建筑、还有散漫的生活节奏丰富的夜生活。
\n\n\n\n丽江的特色美食:腊排骨、黑山羊火锅、三文鱼、鸡豆凉粉、野生菌、汽锅鸡、酥油茶、杜鹃花炒蛋、纳西烤鱼、米灌肠、丽江粑粑等等。
\n\n\n\n\n\n\n\n最佳旅游时间:一年四季皆宜
\n\n\n\n⑧腾冲 极边第一城
\n\n\n\n\n\n\n\n腾冲城不大,但历史悠久,有着厚重的历史底蕴和很多人文景观建筑。
\n\n\n\n腾冲的特色美食:土锅子、三滴水、大救驾、饵丝、大薄片等等。
\n\n\n\n\n\n\n\n最佳旅游时间:一年四季都适合,11—12月初可以看到银杏的最佳季节。
\n\n\n\n⑨喀什 丝路明珠
\n\n\n\n\n\n\n\n喀什是中国最西端的一座城市,是中国对西方经济文化交流的交通枢纽与门户之地。
\n\n\n\n喀什的特色美食:羊肉串、凉粉、囊坑烤肉、酸奶、囊等等。
\n\n\n\n\n\n\n\n最佳旅游时间:8—10月最佳。
\n\n\n\n⑩伊犁 塞外江南
\n\n\n\n\n\n\n\n伊犁素有“塞外江南”、“瓜果之乡”的美称。这里雨水相对充沛,天气温润,被称为“瀚海湿岛”,草地、森林的植被覆盖率达67.7%。
\n\n\n\n伊犁的特色美食:卡瓦斯、熏肉和熏马肠、凉粉、马奶、纳仁、辣罐血肠等等。
\n\n\n\n\n\n\n\n最佳旅游时间:6—10月最佳,6月中旬是薰衣草盛开的季节,7月是油菜花盛开的季节。
\n', '强烈推荐10个国内旅游地', '', 'inherit', 'closed', 'closed', '', '21-revision-v1', '', '', '2019-04-07 10:56:06', '2019-04-07 02:56:06', '', 21, 'http://localhost/2019/04/07/21-revision-v1/', 0, 'revision', '', 0), (26, 1, '2019-04-07 10:58:19', '2019-04-07 02:58:19', '\n①西安 千年古都
\n\n\n\n\n\n\n\n西安是一个历史文化底蕴深厚的城市 ,雄伟的古城、壮观的兵马俑、以及各种特色小吃,西安是中国最佳旅游目的地、中国国际形象最佳城市之一 ,有两项六处遗产被列入《世界遗产名录》,分别是:秦始皇陵及兵马俑、大雁塔、小雁塔、唐长安城大明宫遗址、汉长安城未央宫遗址、兴教寺塔。
\n\n\n\n西安的特色小吃也有很多:biangbiang面、饺子宴、秦镇凉皮、羊肉泡馍、老童家腊羊肉、锅盔、肉夹馍等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-10月,最适合出行。
\n\n\n\n②南京 六朝金粉地,金陵帝王州
\n\n\n\n\n\n\n\n“六朝古都”的沧桑洗礼,现代化都市的灿烂文明,让南京这座依山傍水的历史名城独具魅力。
\n\n\n\n南京的特色美食:金陵四大菜(松鼠鱼、美味肝、蛋烧卖、凤尾虾)、鸭血粉丝汤、盐水鸭、梅花糕、鸡汁汤包、桂花蜜汁藕等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-10月,春秋两季最为舒适。
\n\n\n\n③北京 举世无双的皇家建筑
\n\n\n\n\n\n\n\n北京最有皇家气息,是一座非常适合旅行和深度探索的城市。
\n\n\n\n北京的特色美食:北京烤鸭、涮羊肉、炸酱面、豆汁儿、卤煮火烧、炒肝儿、爆肚儿等等。
\n\n\n\n\n\n\n\n最佳旅游时间:3-5月、9-11月,春秋两季最为舒适。
\n\n\n\n④苏州 苏州园林甲天下
\n\n\n\n\n\n\n\n苏州是一个备受宠爱的城市,江南的富庶延续至今“人间天堂”实至名归,你可以在写意园林中陶醉、为苏州博物馆点赞,品尝品味微甜的四季时鲜、听柔软婉转的昆曲评弹,夜宿小桥流水的江南古镇。
\n\n\n\n苏州的特色美食:松鼠桂鱼、碧螺虾仁、响油鳝糊、桂花鸡头米、生煎、藏书镇羊肉、阳澄湖大闸蟹等等。
\n\n\n\n\n\n\n\n最佳旅游时间:四季皆宜,春天最佳。
\n\n\n\n⑤大理 风花雪月地,山光水色城
\n\n\n\n\n\n\n\n大理山川秀丽、气候宜人,上关花、下关风、苍山雪、洱海月,构成了大理“四绝”,素有“东方瑞士”之称。
\n\n\n\n大理的特色美食:白族饵块、云南木瓜水、邓川乳扇、毫糯索、喜洲破酥粑粑、巍山耙肉饵丝、白族三道茶、大理生皮等等。
\n\n\n\n\n\n\n\n最佳旅游时间:大理四季如春,春秋两季最美。
\n\n\n\n⑥澳门 东方的“拉斯维加斯”
\n\n\n\n\n\n\n\n澳门位于中国东南沿海的珠江三角洲,距离香港只有1小时船程,这里有着亚洲“拉斯维加斯”的称号,澳门虽小,但是却有深厚的历史沉淀。
\n\n\n\n澳门的特色美食:猪扒包、葡式蛋挞、木糠布甸、大菜糕、金钱饼、竹升打面、水蟹粥、马介休、葡国鸡等等。
\n\n\n\n\n\n\n\n最佳旅游时间:10月—次年2月。
\n\n\n\n⑦丽江 有一段时光叫丽江
\n\n\n\n\n\n\n\n丽江有浓郁的民族风情、小桥流水式的布局、错落有致的居民建筑、还有散漫的生活节奏丰富的夜生活。
\n\n\n\n丽江的特色美食:腊排骨、黑山羊火锅、三文鱼、鸡豆凉粉、野生菌、汽锅鸡、酥油茶、杜鹃花炒蛋、纳西烤鱼、米灌肠、丽江粑粑等等。
\n\n\n\n\n\n\n\n最佳旅游时间:一年四季皆宜
\n\n\n\n⑧腾冲 极边第一城
\n\n\n\n\n\n\n\n腾冲城不大,但历史悠久,有着厚重的历史底蕴和很多人文景观建筑。
\n\n\n\n腾冲的特色美食:土锅子、三滴水、大救驾、饵丝、大薄片等等。
\n\n\n\n\n\n\n\n最佳旅游时间:一年四季都适合,11—12月初可以看到银杏的最佳季节。
\n\n\n\n⑨喀什 丝路明珠
\n\n\n\n\n\n\n\n喀什是中国最西端的一座城市,是中国对西方经济文化交流的交通枢纽与门户之地。
\n\n\n\n喀什的特色美食:羊肉串、凉粉、囊坑烤肉、酸奶、囊等等。
\n\n\n\n\n\n\n\n最佳旅游时间:8—10月最佳。
\n\n\n\n⑩伊犁 塞外江南
\n\n\n\n\n\n\n\n伊犁素有“塞外江南”、“瓜果之乡”的美称。这里雨水相对充沛,天气温润,被称为“瀚海湿岛”,草地、森林的植被覆盖率达67.7%。
\n\n\n\n伊犁的特色美食:卡瓦斯、熏肉和熏马肠、凉粉、马奶、纳仁、辣罐血肠等等。
\n\n\n\n\n\n\n\n最佳旅游时间:6—10月最佳,6月中旬是薰衣草盛开的季节,7月是油菜花盛开的季节。
\n', '强烈推荐10个国内旅游地', '', 'inherit', 'closed', 'closed', '', '21-autosave-v1', '', '', '2019-04-07 10:58:19', '2019-04-07 02:58:19', '', 21, 'http://localhost/2019/04/07/21-autosave-v1/', 0, 'revision', '', 0), (27, 1, '2019-04-07 16:01:35', '2019-04-07 08:01:35', '\n联系地址:怀化职业技术学院
\n\n\n\n计应二班,易先生
\n\n\n\n\n', '联系我们', '', 'inherit', 'closed', 'closed', '', '5-revision-v1', '', '', '2019-04-07 16:01:35', '2019-04-07 08:01:35', '', 5, 'http://localhost/2019/04/07/5-revision-v1/', 0, 'revision', '', 0), (28, 1, '2019-04-07 16:01:57', '2019-04-07 08:01:57', '\n联系地址:怀化职业技术学院
\n\n\n\n计应二班,易先生
\n\n\n\n北京春天有三大花节:玉渊潭公园的樱花节、北京植物园的桃花节、元大都城垣遗址公园的海棠花节。其中,元大都公园没有像玉渊潭那样熙熙攘攘的人群,也不像植物园一样地处京郊。它就在我们身边——小月河边。这是北京最大的海棠林,每年四五月份,西府海棠、贴梗海棠、金星海棠、垂丝海棠等诸多品种的海棠树花开小月河两岸,于是这里变成了海棠的天地,吸引了很多人到这里赏花踏青。
地铁十号线安贞门东南口出来,就是这一片花的海洋。这周以来,元大都的十多个品种3000余株海棠开始进入盛花期。
\n\n\n\n“海棠笑迎客,留步看花溪”,海棠花溪这个名字,一听便觉心驰神往。或许,海棠花溪的名字便由来于此吧,海棠花开的时候,水里也是花瓣。
\n\n\n\n海棠,是元大都公园的特色,盛放的海棠,红的热烈,粉的娇倩。而含苞的海棠,只有浅浅的粉红,仿佛含羞的少年,欲说还休,更添了一份柔美。
\n\n\n\n\n\n\n\n元大都公园里,数量最多的当属西府海棠了。因晋朝时生长于西府而得名,海棠花是我国的传统名花之一,花姿潇洒,花开似锦,自古以来是雅俗共赏的名花,素有花中神仙、花贵妃有“国艳”之誉,历代文人墨客题咏不绝。
\n\n\n\n西府海棠在海棠花类中树态峭立,似亭亭少女。花朵红粉相间,叶子嫩绿可爱,果实鲜美诱人,不论孤植、列植、丛植均极为美观。最宜植于水滨及小庭一隅。郭稹海棠诗中“朱栏明媚照黄塘,芳树交加枕短墙。”就是最生动形象的写照。
\n\n\n\n海棠花开娇艳动人,但一般的海棠花无香味,只有西府海棠既香且艳,是海棠中的上品。其花未开时,花蕾红艳,似胭脂点点,开后则渐变粉红,有如晓天明霞。
\n\n\n\n一代大文豪苏东坡也为之倾倒,“只恐夜深花睡去,故烧高烛照红妆”,又因“明皇秋八月,太液池有千叶白莲数枝盛开,帝与贵戚宴赏焉。
垂丝海棠花色艳丽,花姿优美,花期在4月左右。叶卵形或椭圆形。花朵簇生于顶端,花瓣呈玫瑰红色,朵朵弯曲下垂,如遇微风飘飘荡荡,娇柔红艳。
\n\n\n\n望犹如彤云密布,美不胜收,是深受人们喜爱的庭院木本花卉。垂丝海棠柔蔓迎风,垂英凫凫,如秀发遮面的淑女,脉脉深情,风姿怜人。
\n\n\n\n宋代杨万里诗中:“垂丝别得一风光,谁道全输蜀海棠。风搅玉皇红世界,日烘青帝紫衣裳。懒无气力仍春醉,睡起精神欲晓妆。举似老夫新句子,看渠桃杏敢承当。”形容妖艳的垂丝海棠鲜红的花瓣把蓝天、天界都搅红了,闪烁着紫色的花萼如紫袍,柔软下垂的红色花朵如喝了酒的少妇,玉肌泛红,娇弱乏力。其姿色、妖态更胜桃、李、杏。
作为传统海棠的一种,贴梗海棠的花色红黄杂揉,相映成趣,“占尽春色最风流”,是良好的观花、观果花木。多栽培于庭园供绿化用,也供作绿篱的材料,可孤植或与迎春、连翘丛植。
\n\n\n\n花朵鲜润丰腴、绚烂耀目,加上它的花瓣光洁剔透,真的是非常美丽。
\n\n\n\n贴梗海棠不仅是盆栽庭院观赏的优良花木,在园林应用中,也占据重要的位置。在江苏、安徽、山东、北京、天津、上海、浙江等地,贴梗海棠是春季重要的观赏花卉之一。其移栽成活极高,花期长,观赏价值高,栽植后体现速度快。
\n\n\n\n贴梗海棠的花语:平凡、热情。它的花语还有:早熟,妖精的光辉,先驱者,领导人
\n\n\n\n\n\n\n\n\n\n\n\n除了鲜艳的红色,还有这种浅浅的橘色花朵,更多了一份娇艳。
\n\n\n\n\n\n\n\n这种洁白如雪的海棠名字叫春雪。“暗中自有清香在,不是幽人不得知”。
\n\n\n\n洁白的花瓣,真的犹如春雪一般。
还有许多不知道名字的海棠,这两天出去溜达溜达,看看有没有写。
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n★2013元大都赏花小贴士
花节时间:4月12日----4月22日
赏花门票:免费
地点:北京市朝阳区元大都城垣遗址公园 “海棠花溪”景区(三号景区)内至“安定生辉”景区(四号景区)
乘车路线:
★乘坐公共交通:
1)407路公交车安贞西里下车即到;
2)653、409、380、849、特2路、515安贞医院北站下车即到;
3)地铁10号线北土城站下车出站即到;
★自驾车路线:
1)北三环安华桥向北至土城东路右拐(向东)约100米路南即到;
2)北四环安惠桥向南至土城东路右拐(向西)约500米路南即到。
北京春天有三大花节:玉渊潭公园的樱花节、北京植物园的桃花节、元大都城垣遗址公园的海棠花节。其中,元大都公园没有像玉渊潭那样熙熙攘攘的人群,也不像植物园一样地处京郊。它就在我们身边——小月河边。这是北京最大的海棠林,每年四五月份,西府海棠、贴梗海棠、金星海棠、垂丝海棠等诸多品种的海棠树花开小月河两岸,于是这里变成了海棠的天地,吸引了很多人到这里赏花踏青。
地铁十号线安贞门东南口出来,就是这一片花的海洋。这周以来,元大都的十多个品种3000余株海棠开始进入盛花期。
\n\n\n\n“海棠笑迎客,留步看花溪”,海棠花溪这个名字,一听便觉心驰神往。或许,海棠花溪的名字便由来于此吧,海棠花开的时候,水里也是花瓣。
\n\n\n\n海棠,是元大都公园的特色,盛放的海棠,红的热烈,粉的娇倩。而含苞的海棠,只有浅浅的粉红,仿佛含羞的少年,欲说还休,更添了一份柔美。
\n\n\n\n\n\n\n\n元大都公园里,数量最多的当属西府海棠了。因晋朝时生长于西府而得名,海棠花是我国的传统名花之一,花姿潇洒,花开似锦,自古以来是雅俗共赏的名花,素有花中神仙、花贵妃有“国艳”之誉,历代文人墨客题咏不绝。
\n\n\n\n西府海棠在海棠花类中树态峭立,似亭亭少女。花朵红粉相间,叶子嫩绿可爱,果实鲜美诱人,不论孤植、列植、丛植均极为美观。最宜植于水滨及小庭一隅。郭稹海棠诗中“朱栏明媚照黄塘,芳树交加枕短墙。”就是最生动形象的写照。
\n\n\n\n海棠花开娇艳动人,但一般的海棠花无香味,只有西府海棠既香且艳,是海棠中的上品。其花未开时,花蕾红艳,似胭脂点点,开后则渐变粉红,有如晓天明霞。
\n\n\n\n一代大文豪苏东坡也为之倾倒,“只恐夜深花睡去,故烧高烛照红妆”,又因“明皇秋八月,太液池有千叶白莲数枝盛开,帝与贵戚宴赏焉。
垂丝海棠花色艳丽,花姿优美,花期在4月左右。叶卵形或椭圆形。花朵簇生于顶端,花瓣呈玫瑰红色,朵朵弯曲下垂,如遇微风飘飘荡荡,娇柔红艳。
\n\n\n\n望犹如彤云密布,美不胜收,是深受人们喜爱的庭院木本花卉。垂丝海棠柔蔓迎风,垂英凫凫,如秀发遮面的淑女,脉脉深情,风姿怜人。
\n\n\n\n宋代杨万里诗中:“垂丝别得一风光,谁道全输蜀海棠。风搅玉皇红世界,日烘青帝紫衣裳。懒无气力仍春醉,睡起精神欲晓妆。举似老夫新句子,看渠桃杏敢承当。”形容妖艳的垂丝海棠鲜红的花瓣把蓝天、天界都搅红了,闪烁着紫色的花萼如紫袍,柔软下垂的红色花朵如喝了酒的少妇,玉肌泛红,娇弱乏力。其姿色、妖态更胜桃、李、杏。
作为传统海棠的一种,贴梗海棠的花色红黄杂揉,相映成趣,“占尽春色最风流”,是良好的观花、观果花木。多栽培于庭园供绿化用,也供作绿篱的材料,可孤植或与迎春、连翘丛植。
\n\n\n\n花朵鲜润丰腴、绚烂耀目,加上它的花瓣光洁剔透,真的是非常美丽。
\n\n\n\n贴梗海棠不仅是盆栽庭院观赏的优良花木,在园林应用中,也占据重要的位置。在江苏、安徽、山东、北京、天津、上海、浙江等地,贴梗海棠是春季重要的观赏花卉之一。其移栽成活极高,花期长,观赏价值高,栽植后体现速度快。
\n\n\n\n贴梗海棠的花语:平凡、热情。它的花语还有:早熟,妖精的光辉,先驱者,领导人
\n\n\n\n\n\n\n\n\n\n\n\n除了鲜艳的红色,还有这种浅浅的橘色花朵,更多了一份娇艳。
\n\n\n\n\n\n\n\n这种洁白如雪的海棠名字叫春雪。“暗中自有清香在,不是幽人不得知”。
\n\n\n\n洁白的花瓣,真的犹如春雪一般。
还有许多不知道名字的海棠,这两天出去溜达溜达,看看有没有写。
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n★2013元大都赏花小贴士
花节时间:4月12日----4月22日
赏花门票:免费
地点:北京市朝阳区元大都城垣遗址公园 “海棠花溪”景区(三号景区)内至“安定生辉”景区(四号景区)
乘车路线:
★乘坐公共交通:
1)407路公交车安贞西里下车即到;
2)653、409、380、849、特2路、515安贞医院北站下车即到;
3)地铁10号线北土城站下车出站即到;
★自驾车路线:
1)北三环安华桥向北至土城东路右拐(向东)约100米路南即到;
2)北四环安惠桥向南至土城东路右拐(向西)约500米路南即到。
我的旅游
\n', '后端编写', '', 'draft', 'open', 'open', '', '', '', '', '2019-04-07 16:26:13', '2019-04-07 08:26:13', '', 0, 'http://localhost/?p=41', 0, 'post', '', 0), (43, 1, '2019-04-14 16:39:41', '2019-04-14 08:39:41', '\n北京春天有三大花节:玉渊潭公园的樱花节、北京植物园的桃花节、元大都城垣遗址公园的海棠花节。其中,元大都公园没有像玉渊潭那样熙熙攘攘的人群,也不像植物园一样地处京郊。它就在我们身边——小月河边。这是北京最大的海棠林,每年四五月份,西府海棠、贴梗海棠、金星海棠、垂丝海棠等诸多品种的海棠树花开小月河两岸,于是这里变成了海棠的天地,吸引了很多人到这里赏花踏青。
地铁十号线安贞门东南口出来,就是这一片花的海洋。这周以来,元大都的十多个品种3000余株海棠开始进入盛花期。
\n\n\n\n“海棠笑迎客,留步看花溪”,海棠花溪这个名字,一听便觉心驰神往。或许,海棠花溪的名字便由来于此吧,海棠花开的时候,水里也是花瓣。
\n\n\n\n海棠,是元大都公园的特色,盛放的海棠,红的热烈,粉的娇倩。而含苞的海棠,只有浅浅的粉红,仿佛含羞的少年,欲说还休,更添了一份柔美。
\n\n\n\n\n\n\n\n元大都公园里,数量最多的当属西府海棠了。因晋朝时生长于西府而得名,海棠花是我国的传统名花之一,花姿潇洒,花开似锦,自古以来是雅俗共赏的名花,素有花中神仙、花贵妃有“国艳”之誉,历代文人墨客题咏不绝。
\n\n\n\n西府海棠在海棠花类中树态峭立,似亭亭少女。花朵红粉相间,叶子嫩绿可爱,果实鲜美诱人,不论孤植、列植、丛植均极为美观。最宜植于水滨及小庭一隅。郭稹海棠诗中“朱栏明媚照黄塘,芳树交加枕短墙。”就是最生动形象的写照。
\n\n\n\n海棠花开娇艳动人,但一般的海棠花无香味,只有西府海棠既香且艳,是海棠中的上品。其花未开时,花蕾红艳,似胭脂点点,开后则渐变粉红,有如晓天明霞。
\n\n\n\n一代大文豪苏东坡也为之倾倒,“只恐夜深花睡去,故烧高烛照红妆”,又因“明皇秋八月,太液池有千叶白莲数枝盛开,帝与贵戚宴赏焉。
垂丝海棠花色艳丽,花姿优美,花期在4月左右。叶卵形或椭圆形。花朵簇生于顶端,花瓣呈玫瑰红色,朵朵弯曲下垂,如遇微风飘飘荡荡,娇柔红艳。
\n\n\n\n望犹如彤云密布,美不胜收,是深受人们喜爱的庭院木本花卉。垂丝海棠柔蔓迎风,垂英凫凫,如秀发遮面的淑女,脉脉深情,风姿怜人。
\n\n\n\n宋代杨万里诗中:“垂丝别得一风光,谁道全输蜀海棠。风搅玉皇红世界,日烘青帝紫衣裳。懒无气力仍春醉,睡起精神欲晓妆。举似老夫新句子,看渠桃杏敢承当。”形容妖艳的垂丝海棠鲜红的花瓣把蓝天、天界都搅红了,闪烁着紫色的花萼如紫袍,柔软下垂的红色花朵如喝了酒的少妇,玉肌泛红,娇弱乏力。其姿色、妖态更胜桃、李、杏。
作为传统海棠的一种,贴梗海棠的花色红黄杂揉,相映成趣,“占尽春色最风流”,是良好的观花、观果花木。多栽培于庭园供绿化用,也供作绿篱的材料,可孤植或与迎春、连翘丛植。
\n\n\n\n花朵鲜润丰腴、绚烂耀目,加上它的花瓣光洁剔透,真的是非常美丽。
\n\n\n\n贴梗海棠不仅是盆栽庭院观赏的优良花木,在园林应用中,也占据重要的位置。在江苏、安徽、山东、北京、天津、上海、浙江等地,贴梗海棠是春季重要的观赏花卉之一。其移栽成活极高,花期长,观赏价值高,栽植后体现速度快。
\n\n\n\n贴梗海棠的花语:平凡、热情。它的花语还有:早熟,妖精的光辉,先驱者,领导人
\n\n\n\n\n\n\n\n\n\n\n\n除了鲜艳的红色,还有这种浅浅的橘色花朵,更多了一份娇艳。
\n\n\n\n\n\n\n\n这种洁白如雪的海棠名字叫春雪。“暗中自有清香在,不是幽人不得知”。
\n\n\n\n洁白的花瓣,真的犹如春雪一般。
还有许多不知道名字的海棠,这两天出去溜达溜达,看看有没有写。
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n★2013元大都赏花小贴士
花节时间:4月12日----4月22日
赏花门票:免费
地点:北京市朝阳区元大都城垣遗址公园 “海棠花溪”景区(三号景区)内至“安定生辉”景区(四号景区)
乘车路线:
★乘坐公共交通:
1)407路公交车安贞西里下车即到;
2)653、409、380、849、特2路、515安贞医院北站下车即到;
3)地铁10号线北土城站下车出站即到;
★自驾车路线:
1)北三环安华桥向北至土城东路右拐(向东)约100米路南即到;
2)北四环安惠桥向南至土城东路右拐(向西)约500米路南即到。
联系地址:怀化职业技术学院
\n\n\n\n计应三班,易先生
\n\n\n\n