-- phpMyAdmin SQL Dump -- version 4.6.4 -- https://www.phpmyadmin.net/ -- -- Host: 127.0.0.1 -- Generation Time: Jun 20, 2017 at 12:43 PM -- Server version: 5.7.14 -- PHP Version: 7.0.10 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 utf8mb4 */; -- -- Database: `corcel` -- -- -------------------------------------------------------- -- -- Table structure for table `commentmeta` -- CREATE TABLE `commentmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `comment_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `comments` -- CREATE TABLE `comments` ( `comment_ID` bigint(20) UNSIGNED NOT NULL, `comment_post_ID` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `comment_author` tinytext NOT NULL, `comment_author_email` varchar(100) NOT NULL DEFAULT '', `comment_author_url` varchar(200) NOT NULL DEFAULT '', `comment_author_IP` varchar(100) 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 NOT NULL, `comment_karma` int(11) NOT NULL DEFAULT '0', `comment_approved` varchar(20) NOT NULL DEFAULT '1', `comment_agent` varchar(255) NOT NULL DEFAULT '', `comment_type` varchar(20) NOT NULL DEFAULT '', `comment_parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `comments` -- INSERT INTO `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, 'Mr WordPress', '', 'https://wordpress.org/', '', '2014-08-20 22:25:54', '2014-08-20 22:25:54', 'Hi, this is a comment.\nTo delete a comment, just log in and view the post's comments. There you will have the option to edit or delete them.', 0, '1', '', '', 0, 0), (2, 1, 'Test Author', '', 'https://wordpress.org/', '', '2014-08-21 22:25:54', '2014-08-21 22:25:54', 'test reply', 0, '1', '', '', 1, 0), (3, 0, '1', '', '', '', '2016-03-17 16:25:25', '2016-03-17 16:25:25', 'Test content', 0, '1', '', '', 0, 0), (4, 0, '1', '', '', '', '2016-03-17 16:28:43', '2016-03-17 16:28:43', 'Test content', 0, '1', '', '', 0, 0), (5, 2, '1', '', '', '', '2016-03-17 16:28:57', '2016-03-17 16:28:57', 'Test content', 0, '1', '', '', 0, 0), (6, 2, '1', '', '', '', '2016-03-17 16:30:18', '2016-03-17 16:30:18', 'Test content', 0, '1', '', '', 0, 0), (7, 2, '1', '', '', '', '2016-03-17 16:30:53', '2016-03-17 16:30:53', 'Test content', 0, '1', '', '', 0, 0), (8, 38, '1', '', '', '', '2016-03-17 16:31:05', '2016-03-17 16:31:05', 'Test content', 0, '1', '', '', 0, 0), (9, 40, '1', '', '', '', '2016-03-17 16:31:16', '2016-03-17 16:31:16', 'Test content', 0, '1', '', '', 0, 0), (10, 42, '1', '', '', '', '2016-03-17 16:34:10', '2016-03-17 16:34:10', 'Test content', 0, '1', '', '', 0, 0), (11, 44, '1', '', '', '', '2016-03-17 16:34:21', '2016-03-17 16:34:21', 'Test content', 0, '1', '', '', 0, 0), (12, 46, '1', '', '', '', '2016-03-17 16:34:40', '2016-03-17 16:34:40', 'Test content', 0, '1', '', '', 0, 0), (13, 48, '1', '', '', '', '2016-03-17 16:38:14', '2016-03-17 16:38:14', 'Test content', 0, '1', '', '', 0, 0), (14, 50, '1', '', '', '', '2016-04-19 19:05:16', '2016-04-19 19:05:16', 'Test content', 0, '1', '', '', 0, 0), (15, 52, '1', '', '', '', '2016-04-19 19:05:19', '2016-04-19 19:05:19', 'Test content', 0, '1', '', '', 0, 0), (16, 54, '1', '', '', '', '2016-04-19 19:05:24', '2016-04-19 19:05:24', 'Test content', 0, '1', '', '', 0, 0), (17, 56, '1', '', '', '', '2016-04-19 19:45:42', '2016-04-19 19:45:42', 'Test content', 0, '1', '', '', 0, 0), (18, 58, '1', '', '', '', '2016-04-29 17:45:28', '2016-04-29 17:45:28', 'Test content', 0, '1', '', '', 0, 0), (19, 62, '1', '', '', '', '2016-04-29 17:52:07', '2016-04-29 17:52:07', 'Test content', 0, '1', '', '', 0, 0), (20, 64, '1', '', '', '', '2016-04-29 17:52:21', '2016-04-29 17:52:21', 'Test content', 0, '1', '', '', 0, 0), (21, 65, '1', '', '', '', '2016-04-29 17:52:35', '2016-04-29 17:52:35', 'Test content', 0, '1', '', '', 0, 0), (22, 67, '1', '', '', '', '2016-04-29 17:53:40', '2016-04-29 17:53:40', 'Test content', 0, '1', '', '', 0, 0), (23, 69, '1', '', '', '', '2016-04-29 17:54:40', '2016-04-29 17:54:40', 'Test content', 0, '1', '', '', 0, 0), (24, 71, '1', '', '', '', '2016-04-29 17:54:50', '2016-04-29 17:54:50', 'Test content', 0, '1', '', '', 0, 0), (25, 73, '1', '', '', '', '2016-04-29 17:55:06', '2016-04-29 17:55:06', 'Test content', 0, '1', '', '', 0, 0), (26, 75, '1', '', '', '', '2016-04-29 17:56:25', '2016-04-29 17:56:25', 'Test content', 0, '1', '', '', 0, 0), (27, 77, '1', '', '', '', '2016-04-29 17:56:34', '2016-04-29 17:56:34', 'Test content', 0, '1', '', '', 0, 0), (28, 79, '1', '', '', '', '2016-04-29 17:57:09', '2016-04-29 17:57:09', 'Test content', 0, '1', '', '', 0, 0), (29, 81, '1', '', '', '', '2016-04-29 17:57:24', '2016-04-29 17:57:24', 'Test content', 0, '1', '', '', 0, 0), (30, 83, '1', '', '', '', '2016-04-29 17:58:05', '2016-04-29 17:58:05', 'Test content', 0, '1', '', '', 0, 0), (31, 85, '1', '', '', '', '2016-04-29 17:58:11', '2016-04-29 17:58:11', 'Test content', 0, '1', '', '', 0, 0), (32, 87, '1', '', '', '', '2016-04-29 17:58:31', '2016-04-29 17:58:31', 'Test content', 0, '1', '', '', 0, 0), (33, 89, '1', '', '', '', '2016-04-29 17:58:47', '2016-04-29 17:58:47', 'Test content', 0, '1', '', '', 0, 0), (34, 91, '1', '', '', '', '2016-04-29 17:59:22', '2016-04-29 17:59:22', 'Test content', 0, '1', '', '', 0, 0), (35, 93, '1', '', '', '', '2016-04-29 17:59:46', '2016-04-29 17:59:46', 'Test content', 0, '1', '', '', 0, 0), (36, 95, '1', '', '', '', '2016-04-29 17:59:51', '2016-04-29 17:59:51', 'Test content', 0, '1', '', '', 0, 0), (37, 97, '1', '', '', '', '2016-04-29 18:00:07', '2016-04-29 18:00:07', 'Test content', 0, '1', '', '', 0, 0), (38, 99, '1', '', '', '', '2016-04-29 18:00:46', '2016-04-29 18:00:46', 'Test content', 0, '1', '', '', 0, 0), (39, 101, '1', '', '', '', '2016-04-29 18:03:09', '2016-04-29 18:03:09', 'Test content', 0, '1', '', '', 0, 0), (40, 103, '1', '', '', '', '2016-04-29 18:03:25', '2016-04-29 18:03:25', 'Test content', 0, '1', '', '', 0, 0), (41, 105, '1', '', '', '', '2016-04-29 18:03:42', '2016-04-29 18:03:42', 'Test content', 0, '1', '', '', 0, 0), (42, 107, '1', '', '', '', '2016-04-29 18:03:49', '2016-04-29 18:03:49', 'Test content', 0, '1', '', '', 0, 0), (43, 109, '1', '', '', '', '2016-04-29 18:06:17', '2016-04-29 18:06:17', 'Test content', 0, '1', '', '', 0, 0), (44, 111, '1', '', '', '', '2016-04-29 18:09:07', '2016-04-29 18:09:07', 'Test content', 0, '1', '', '', 0, 0), (45, 113, '1', '', '', '', '2016-04-29 18:47:20', '2016-04-29 18:47:20', 'Test content', 0, '1', '', '', 0, 0), (46, 115, '1', '', '', '', '2016-04-29 18:56:19', '2016-04-29 18:56:19', 'Test content', 0, '1', '', '', 0, 0), (47, 117, '1', '', '', '', '2016-04-29 18:56:32', '2016-04-29 18:56:32', 'Test content', 0, '1', '', '', 0, 0), (48, 118, '1', '', '', '', '2016-04-29 19:04:37', '2016-04-29 19:04:37', 'Test content', 0, '1', '', '', 0, 0), (49, 120, '1', '', '', '', '2016-04-29 19:11:41', '2016-04-29 19:11:41', 'Test content', 0, '1', '', '', 0, 0), (50, 122, '1', '', '', '', '2016-05-02 22:38:05', '2016-05-02 22:38:05', 'Test content', 0, '1', '', '', 0, 0), (51, 124, '1', '', '', '', '2016-05-04 19:11:53', '2016-05-04 19:11:53', 'Test content', 0, '1', '', '', 0, 0), (52, 126, '1', '', '', '', '2016-08-22 16:02:30', '2016-08-22 16:02:30', 'Test content', 0, '1', '', '', 0, 0), (53, 129, '1', '', '', '', '2016-08-22 16:04:25', '2016-08-22 16:04:25', 'Test content', 0, '1', '', '', 0, 0), (54, 132, '1', '', '', '', '2016-08-22 16:06:19', '2016-08-22 16:06:19', 'Test content', 0, '1', '', '', 0, 0), (55, 135, '1', '', '', '', '2016-08-22 16:19:30', '2016-08-22 16:19:30', 'Test content', 0, '1', '', '', 0, 0), (56, 138, '1', '', '', '', '2016-08-22 16:20:14', '2016-08-22 16:20:14', 'Test content', 0, '1', '', '', 0, 0), (57, 141, '1', '', '', '', '2016-08-22 16:23:53', '2016-08-22 16:23:53', 'Test content', 0, '1', '', '', 0, 0), (58, 144, '1', '', '', '', '2016-08-22 16:24:11', '2016-08-22 16:24:11', 'Test content', 0, '1', '', '', 0, 0), (59, 147, '1', '', '', '', '2016-08-22 16:24:42', '2016-08-22 16:24:42', 'Test content', 0, '1', '', '', 0, 0), (60, 150, '1', '', '', '', '2016-08-22 16:24:53', '2016-08-22 16:24:53', 'Test content', 0, '1', '', '', 0, 0), (61, 153, '1', '', '', '', '2016-08-22 16:25:27', '2016-08-22 16:25:27', 'Test content', 0, '1', '', '', 0, 0), (62, 156, '1', '', '', '', '2016-08-22 16:27:45', '2016-08-22 16:27:45', 'Test content', 0, '1', '', '', 0, 0), (63, 159, '1', '', '', '', '2016-08-22 16:28:21', '2016-08-22 16:28:21', 'Test content', 0, '1', '', '', 0, 0), (64, 162, '1', '', '', '', '2016-08-22 16:28:42', '2016-08-22 16:28:42', 'Test content', 0, '1', '', '', 0, 0), (65, 165, '1', '', '', '', '2016-08-22 16:29:05', '2016-08-22 16:29:05', 'Test content', 0, '1', '', '', 0, 0), (66, 168, '1', '', '', '', '2016-08-22 16:29:16', '2016-08-22 16:29:16', 'Test content', 0, '1', '', '', 0, 0), (67, 171, '1', '', '', '', '2016-08-22 16:29:38', '2016-08-22 16:29:38', 'Test content', 0, '1', '', '', 0, 0), (68, 174, '1', '', '', '', '2016-08-22 16:30:46', '2016-08-22 16:30:46', 'Test content', 0, '1', '', '', 0, 0), (69, 177, '1', '', '', '', '2016-08-22 16:30:59', '2016-08-22 16:30:59', 'Test content', 0, '1', '', '', 0, 0), (70, 180, '1', '', '', '', '2016-08-22 16:31:04', '2016-08-22 16:31:04', 'Test content', 0, '1', '', '', 0, 0), (71, 183, '1', '', '', '', '2016-08-22 16:31:44', '2016-08-22 16:31:44', 'Test content', 0, '1', '', '', 0, 0), (72, 186, '1', '', '', '', '2016-08-22 16:32:25', '2016-08-22 16:32:25', 'Test content', 0, '1', '', '', 0, 0), (73, 189, '1', '', '', '', '2016-10-03 10:23:40', '2016-10-03 10:23:40', 'Test content', 0, '1', '', '', 0, 0), (74, 192, '1', '', '', '', '2016-10-03 10:32:39', '2016-10-03 10:32:39', 'Test content', 0, '1', '', '', 0, 0), (75, 195, '1', '', '', '', '2016-10-03 10:37:49', '2016-10-03 10:37:49', 'Test content', 0, '1', '', '', 0, 0), (76, 198, '1', '', '', '', '2016-10-07 12:11:51', '2016-10-07 12:11:51', 'Test content', 0, '1', '', '', 0, 0), (77, 201, '1', '', '', '', '2016-10-12 18:35:39', '2016-10-12 18:35:39', 'Test content', 0, '1', '', '', 0, 0), (78, 204, '1', '', '', '', '2016-10-12 18:35:51', '2016-10-12 18:35:51', 'Test content', 0, '1', '', '', 0, 0), (79, 207, '1', '', '', '', '2016-10-12 18:39:14', '2016-10-12 18:39:14', 'Test content', 0, '1', '', '', 0, 0), (80, 210, '1', '', '', '', '2016-10-12 18:39:43', '2016-10-12 18:39:43', 'Test content', 0, '1', '', '', 0, 0), (81, 213, '1', '', '', '', '2016-10-12 18:40:05', '2016-10-12 18:40:05', 'Test content', 0, '1', '', '', 0, 0), (82, 216, '1', '', '', '', '2016-10-12 18:41:20', '2016-10-12 18:41:20', 'Test content', 0, '1', '', '', 0, 0), (83, 219, '1', '', '', '', '2016-10-12 18:41:40', '2016-10-12 18:41:40', 'Test content', 0, '1', '', '', 0, 0), (84, 222, '1', '', '', '', '2016-10-12 18:42:47', '2016-10-12 18:42:47', 'Test content', 0, '1', '', '', 0, 0), (85, 225, '1', '', '', '', '2016-10-12 18:44:40', '2016-10-12 18:44:40', 'Test content', 0, '1', '', '', 0, 0), (86, 228, '1', '', '', '', '2016-10-12 18:46:25', '2016-10-12 18:46:25', 'Test content', 0, '1', '', '', 0, 0), (87, 231, '1', '', '', '', '2016-10-12 18:46:45', '2016-10-12 18:46:45', 'Test content', 0, '1', '', '', 0, 0), (88, 234, '1', '', '', '', '2016-10-12 18:48:08', '2016-10-12 18:48:08', 'Test content', 0, '1', '', '', 0, 0), (89, 237, '1', '', '', '', '2016-10-12 18:48:17', '2016-10-12 18:48:17', 'Test content', 0, '1', '', '', 0, 0), (90, 240, '1', '', '', '', '2016-10-12 18:48:38', '2016-10-12 18:48:38', 'Test content', 0, '1', '', '', 0, 0), (91, 243, '1', '', '', '', '2016-10-12 18:51:12', '2016-10-12 18:51:12', 'Test content', 0, '1', '', '', 0, 0), (92, 246, '1', '', '', '', '2016-10-12 18:51:28', '2016-10-12 18:51:28', 'Test content', 0, '1', '', '', 0, 0), (93, 249, '1', '', '', '', '2016-10-12 18:52:04', '2016-10-12 18:52:04', 'Test content', 0, '1', '', '', 0, 0), (94, 252, '1', '', '', '', '2016-10-12 18:52:15', '2016-10-12 18:52:15', 'Test content', 0, '1', '', '', 0, 0), (95, 255, '1', '', '', '', '2016-10-12 18:52:21', '2016-10-12 18:52:21', 'Test content', 0, '1', '', '', 0, 0), (96, 258, '1', '', '', '', '2016-10-12 18:53:44', '2016-10-12 18:53:44', 'Test content', 0, '1', '', '', 0, 0), (97, 261, '1', '', '', '', '2016-10-12 18:54:46', '2016-10-12 18:54:46', 'Test content', 0, '1', '', '', 0, 0), (98, 262, '1', '', '', '', '2016-10-12 18:54:58', '2016-10-12 18:54:58', 'Test content', 0, '1', '', '', 0, 0), (99, 263, '1', '', '', '', '2016-10-12 18:55:52', '2016-10-12 18:55:52', 'Test content', 0, '1', '', '', 0, 0), (100, 266, '1', '', '', '', '2016-10-12 18:55:59', '2016-10-12 18:55:59', 'Test content', 0, '1', '', '', 0, 0), (101, 269, '1', '', '', '', '2016-10-12 19:09:09', '2016-10-12 19:09:09', 'Test content', 0, '1', '', '', 0, 0), (102, 272, '1', '', '', '', '2016-10-12 19:17:42', '2016-10-12 19:17:42', 'Test content', 0, '1', '', '', 0, 0), (103, 275, '1', '', '', '', '2016-10-12 19:18:01', '2016-10-12 19:18:01', 'Test content', 0, '1', '', '', 0, 0), (104, 278, '1', '', '', '', '2016-10-12 19:18:22', '2016-10-12 19:18:22', 'Test content', 0, '1', '', '', 0, 0), (105, 281, '1', '', '', '', '2016-10-12 19:19:10', '2016-10-12 19:19:10', 'Test content', 0, '1', '', '', 0, 0), (106, 284, '1', '', '', '', '2016-10-12 19:19:21', '2016-10-12 19:19:21', 'Test content', 0, '1', '', '', 0, 0), (107, 287, '1', '', '', '', '2016-10-12 19:19:28', '2016-10-12 19:19:28', 'Test content', 0, '1', '', '', 0, 0), (108, 290, '1', '', '', '', '2016-10-12 19:22:35', '2016-10-12 19:22:35', 'Test content', 0, '1', '', '', 0, 0), (109, 293, '1', '', '', '', '2016-10-12 19:22:43', '2016-10-12 19:22:43', 'Test content', 0, '1', '', '', 0, 0), (110, 296, '1', '', '', '', '2016-10-12 19:22:47', '2016-10-12 19:22:47', 'Test content', 0, '1', '', '', 0, 0), (111, 299, '1', '', '', '', '2016-10-12 19:23:19', '2016-10-12 19:23:19', 'Test content', 0, '1', '', '', 0, 0), (112, 302, '1', '', '', '', '2016-10-12 19:24:29', '2016-10-12 19:24:29', 'Test content', 0, '1', '', '', 0, 0), (113, 305, '1', '', '', '', '2016-10-12 19:24:40', '2016-10-12 19:24:40', 'Test content', 0, '1', '', '', 0, 0), (114, 308, '1', '', '', '', '2016-10-12 19:27:23', '2016-10-12 19:27:23', 'Test content', 0, '1', '', '', 0, 0), (115, 311, '1', '', '', '', '2016-10-12 19:27:35', '2016-10-12 19:27:35', 'Test content', 0, '1', '', '', 0, 0), (116, 314, '1', '', '', '', '2016-10-12 19:29:00', '2016-10-12 19:29:00', 'Test content', 0, '1', '', '', 0, 0), (117, 317, '1', '', '', '', '2016-10-12 19:29:08', '2016-10-12 19:29:08', 'Test content', 0, '1', '', '', 0, 0), (118, 320, '1', '', '', '', '2016-10-13 13:31:30', '2016-10-13 13:31:30', 'Test content', 0, '1', '', '', 0, 0), (119, 323, '1', '', '', '', '2016-10-13 13:33:13', '2016-10-13 13:33:13', 'Test content', 0, '1', '', '', 0, 0), (120, 324, '1', '', '', '', '2016-10-17 22:15:53', '2016-10-17 22:15:53', 'Test content', 0, '1', '', '', 0, 0), (121, 327, '1', '', '', '', '2016-10-17 22:16:26', '2016-10-17 22:16:26', 'Test content', 0, '1', '', '', 0, 0), (122, 330, '1', '', '', '', '2016-10-17 22:43:59', '2016-10-17 22:43:59', 'Test content', 0, '1', '', '', 0, 0), (123, 333, '1', '', '', '', '2016-11-12 22:40:27', '2016-11-12 22:40:27', 'Test content', 0, '1', '', '', 0, 0), (124, 336, '1', '', '', '', '2016-11-12 23:00:33', '2016-11-12 23:00:33', 'Test content', 0, '1', '', '', 0, 0), (125, 339, '1', '', '', '', '2016-12-06 19:28:59', '2016-12-06 19:28:59', 'Test content', 0, '1', '', '', 0, 0), (126, 342, '1', '', '', '', '2016-12-06 19:29:20', '2016-12-06 19:29:20', 'Test content', 0, '1', '', '', 0, 0), (127, 345, '1', '', '', '', '2016-12-06 19:29:33', '2016-12-06 19:29:33', 'Test content', 0, '1', '', '', 0, 0), (128, 348, '1', '', '', '', '2016-12-06 19:32:05', '2016-12-06 19:32:05', 'Test content', 0, '1', '', '', 0, 0), (129, 349, '1', '', '', '', '2016-12-06 19:32:16', '2016-12-06 19:32:16', 'Test content', 0, '1', '', '', 0, 0), (130, 352, '1', '', '', '', '2016-12-06 19:32:30', '2016-12-06 19:32:30', 'Test content', 0, '1', '', '', 0, 0), (131, 355, '1', '', '', '', '2016-12-06 19:33:46', '2016-12-06 19:33:46', 'Test content', 0, '1', '', '', 0, 0), (132, 356, '1', '', '', '', '2016-12-06 19:33:55', '2016-12-06 19:33:55', 'Test content', 0, '1', '', '', 0, 0), (133, 359, '1', '', '', '', '2016-12-06 19:37:16', '2016-12-06 19:37:16', 'Test content', 0, '1', '', '', 0, 0), (134, 2, '1', '', '', '', '2016-12-06 19:38:47', '2016-12-06 19:38:47', 'Test content', 0, '1', '', '', 0, 0), (135, 2, '1', '', '', '', '2016-12-06 19:41:23', '2016-12-06 19:41:23', 'Test content', 0, '1', '', '', 0, 0), (136, 2, '1', '', '', '', '2016-12-06 19:41:45', '2016-12-06 19:41:45', 'Test content', 0, '1', '', '', 0, 0), (137, 2, '1', '', '', '', '2016-12-06 19:42:45', '2016-12-06 19:42:45', 'Test content', 0, '1', '', '', 0, 0), (138, 2, '1', '', '', '', '2016-12-06 19:43:18', '2016-12-06 19:43:18', 'Test content', 0, '1', '', '', 0, 0), (139, 2, '1', '', '', '', '2016-12-06 19:44:13', '2016-12-06 19:44:13', 'Test content', 0, '1', '', '', 0, 0), (140, 2, '1', '', '', '', '2016-12-06 19:47:15', '2016-12-06 19:47:15', 'Test content', 0, '1', '', '', 0, 0), (141, 2, '1', '', '', '', '2016-12-06 19:49:36', '2016-12-06 19:49:36', 'Test content', 0, '1', '', '', 0, 0), (142, 2, '1', '', '', '', '2016-12-06 19:49:50', '2016-12-06 19:49:50', 'Test content', 0, '1', '', '', 0, 0), (143, 380, '1', '', '', '', '2016-12-06 19:54:31', '2016-12-06 19:54:31', 'Test content', 0, '1', '', '', 0, 0), (144, 2, '1', '', '', '', '2016-12-06 19:56:21', '2016-12-06 19:56:21', 'Test content', 0, '1', '', '', 0, 0), (145, 385, '1', '', '', '', '2016-12-06 19:56:38', '2016-12-06 19:56:38', 'Test content', 0, '1', '', '', 0, 0), (146, 388, '1', '', '', '', '2016-12-06 19:58:36', '2016-12-06 19:58:36', 'Test content', 0, '1', '', '', 0, 0), (147, 389, '1', '', '', '', '2016-12-06 19:59:20', '2016-12-06 19:59:20', 'Test content', 0, '1', '', '', 0, 0), (148, 390, '1', '', '', '', '2016-12-06 19:59:46', '2016-12-06 19:59:46', 'Test content', 0, '1', '', '', 0, 0), (149, 2, '1', '', '', '', '2016-12-06 20:01:00', '2016-12-06 20:01:00', 'Test content', 0, '1', '', '', 0, 0), (150, 392, '1', '', '', '', '2016-12-06 20:02:31', '2016-12-06 20:02:31', 'Test content', 0, '1', '', '', 0, 0), (151, 2, '1', '', '', '', '2016-12-06 20:02:57', '2016-12-06 20:02:57', 'Test content', 0, '1', '', '', 0, 0), (152, 394, '1', '', '', '', '2016-12-06 20:10:10', '2016-12-06 20:10:10', 'Test content', 0, '1', '', '', 0, 0), (153, 395, '1', '', '', '', '2016-12-06 20:11:26', '2016-12-06 20:11:26', 'Test content', 0, '1', '', '', 0, 0), (154, 396, '1', '', '', '', '2016-12-06 20:12:04', '2016-12-06 20:12:04', 'Test content', 0, '1', '', '', 0, 0), (155, 397, '1', '', '', '', '2016-12-06 20:12:37', '2016-12-06 20:12:37', 'Test content', 0, '1', '', '', 0, 0), (156, 398, '1', '', '', '', '2016-12-06 20:12:53', '2016-12-06 20:12:53', 'Test content', 0, '1', '', '', 0, 0), (157, 399, '1', '', '', '', '2017-01-23 21:43:38', '2017-01-23 21:43:38', 'Test content', 0, '1', '', '', 0, 0), (158, 402, '1', '', '', '', '2017-01-23 21:44:52', '2017-01-23 21:44:52', 'Test content', 0, '1', '', '', 0, 0), (159, 405, '1', '', '', '', '2017-01-23 21:48:13', '2017-01-23 21:48:13', 'Test content', 0, '1', '', '', 0, 0), (160, 2, '1', '', '', '', '2017-01-23 21:49:23', '2017-01-23 21:49:23', 'Test content', 0, '1', '', '', 0, 0), (161, 2, '1', '', '', '', '2017-01-23 21:49:36', '2017-01-23 21:49:36', 'Test content', 0, '1', '', '', 0, 0), (162, 410, '1', '', '', '', '2017-01-23 21:50:13', '2017-01-23 21:50:13', 'Test content', 0, '1', '', '', 0, 0), (163, 411, '1', '', '', '', '2017-01-23 21:50:18', '2017-01-23 21:50:18', 'Test content', 0, '1', '', '', 0, 0), (164, 412, '1', '', '', '', '2017-01-23 21:50:28', '2017-01-23 21:50:28', 'Test content', 0, '1', '', '', 0, 0), (165, 415, '1', '', '', '', '2017-01-23 21:50:40', '2017-01-23 21:50:40', 'Test content', 0, '1', '', '', 0, 0), (166, 416, '1', '', '', '', '2017-01-23 21:51:57', '2017-01-23 21:51:57', 'Test content', 0, '1', '', '', 0, 0), (167, 419, '1', '', '', '', '2017-01-23 21:52:59', '2017-01-23 21:52:59', 'Test content', 0, '1', '', '', 0, 0), (168, 422, '1', '', '', '', '2017-01-26 10:54:15', '2017-01-26 10:54:15', 'Test content', 0, '1', '', '', 0, 0), (169, 425, '1', '', '', '', '2017-01-26 10:59:12', '2017-01-26 10:59:12', 'Test content', 0, '1', '', '', 0, 0), (170, 428, '1', '', '', '', '2017-01-31 16:54:34', '2017-01-31 16:54:34', 'Test content', 0, '1', '', '', 0, 0), (171, 431, '1', '', '', '', '2017-01-31 16:54:47', '2017-01-31 16:54:47', 'Test content', 0, '1', '', '', 0, 0), (172, 434, '1', '', '', '', '2017-01-31 16:55:42', '2017-01-31 16:55:42', 'Test content', 0, '1', '', '', 0, 0), (173, 437, '1', '', '', '', '2017-01-31 16:58:02', '2017-01-31 16:58:02', 'Test content', 0, '1', '', '', 0, 0), (174, 438, '1', '', '', '', '2017-01-31 16:58:13', '2017-01-31 16:58:13', 'Test content', 0, '1', '', '', 0, 0), (175, 2, '1', '', '', '', '2017-01-31 16:58:36', '2017-01-31 16:58:36', 'Test content', 0, '1', '', '', 0, 0), (176, 2, '1', '', '', '', '2017-01-31 16:58:46', '2017-01-31 16:58:46', 'Test content', 0, '1', '', '', 0, 0), (177, 2, '1', '', '', '', '2017-01-31 16:59:06', '2017-01-31 16:59:06', 'Test content', 0, '1', '', '', 0, 0), (178, 2, '1', '', '', '', '2017-01-31 16:59:39', '2017-01-31 16:59:39', 'Test content', 0, '1', '', '', 0, 0), (179, 2, '1', '', '', '', '2017-01-31 17:00:46', '2017-01-31 17:00:46', 'Test content', 0, '1', '', '', 0, 0), (180, 444, '1', '', '', '', '2017-01-31 17:01:57', '2017-01-31 17:01:57', 'Test content', 0, '1', '', '', 0, 0), (181, 445, '1', '', '', '', '2017-01-31 17:04:43', '2017-01-31 17:04:43', 'Test content', 0, '1', '', '', 0, 0), (182, 448, '1', '', '', '', '2017-01-31 17:06:11', '2017-01-31 17:06:11', 'Test content', 0, '1', '', '', 0, 0), (183, 451, '1', '', '', '', '2017-01-31 17:06:25', '2017-01-31 17:06:25', 'Test content', 0, '1', '', '', 0, 0), (184, 454, '1', '', '', '', '2017-01-31 17:06:57', '2017-01-31 17:06:57', 'Test content', 0, '1', '', '', 0, 0), (185, 457, '1', '', '', '', '2017-01-31 17:14:38', '2017-01-31 17:14:38', 'Test content', 0, '1', '', '', 0, 0), (186, 460, '1', '', '', '', '2017-01-31 17:31:02', '2017-01-31 17:31:02', 'Test content', 0, '1', '', '', 0, 0), (187, 463, '1', '', '', '', '2017-01-31 17:31:10', '2017-01-31 17:31:10', 'Test content', 0, '1', '', '', 0, 0), (188, 466, '1', '', '', '', '2017-01-31 17:31:40', '2017-01-31 17:31:40', 'Test content', 0, '1', '', '', 0, 0), (189, 469, '1', '', '', '', '2017-01-31 17:32:24', '2017-01-31 17:32:24', 'Test content', 0, '1', '', '', 0, 0), (190, 472, '1', '', '', '', '2017-01-31 17:32:49', '2017-01-31 17:32:49', 'Test content', 0, '1', '', '', 0, 0), (191, 475, '1', '', '', '', '2017-01-31 17:33:17', '2017-01-31 17:33:17', 'Test content', 0, '1', '', '', 0, 0), (192, 478, '1', '', '', '', '2017-01-31 17:43:27', '2017-01-31 17:43:27', 'Test content', 0, '1', '', '', 0, 0), (193, 481, '1', '', '', '', '2017-01-31 17:44:06', '2017-01-31 17:44:06', 'Test content', 0, '1', '', '', 0, 0), (194, 482, '1', '', '', '', '2017-01-31 17:48:04', '2017-01-31 17:48:04', 'Test content', 0, '1', '', '', 0, 0), (195, 485, '1', '', '', '', '2017-01-31 17:53:57', '2017-01-31 17:53:57', 'Test content', 0, '1', '', '', 0, 0), (196, 488, '1', '', '', '', '2017-01-31 17:54:39', '2017-01-31 17:54:39', 'Test content', 0, '1', '', '', 0, 0), (197, 491, '1', '', '', '', '2017-01-31 17:56:06', '2017-01-31 17:56:06', 'Test content', 0, '1', '', '', 0, 0), (198, 494, '1', '', '', '', '2017-01-31 17:56:27', '2017-01-31 17:56:27', 'Test content', 0, '1', '', '', 0, 0), (199, 497, '1', '', '', '', '2017-01-31 17:56:47', '2017-01-31 17:56:47', 'Test content', 0, '1', '', '', 0, 0), (200, 500, '1', '', '', '', '2017-01-31 17:57:16', '2017-01-31 17:57:16', 'Test content', 0, '1', '', '', 0, 0), (201, 503, '1', '', '', '', '2017-01-31 17:58:49', '2017-01-31 17:58:49', 'Test content', 0, '1', '', '', 0, 0), (202, 506, '1', '', '', '', '2017-01-31 18:06:36', '2017-01-31 18:06:36', 'Test content', 0, '1', '', '', 0, 0), (203, 509, '1', '', '', '', '2017-01-31 18:07:59', '2017-01-31 18:07:59', 'Test content', 0, '1', '', '', 0, 0), (204, 512, '1', '', '', '', '2017-01-31 18:08:47', '2017-01-31 18:08:47', 'Test content', 0, '1', '', '', 0, 0), (205, 515, '1', '', '', '', '2017-01-31 18:09:38', '2017-01-31 18:09:38', 'Test content', 0, '1', '', '', 0, 0), (206, 518, '1', '', '', '', '2017-01-31 18:10:47', '2017-01-31 18:10:47', 'Test content', 0, '1', '', '', 0, 0), (207, 521, '1', '', '', '', '2017-01-31 18:11:50', '2017-01-31 18:11:50', 'Test content', 0, '1', '', '', 0, 0), (208, 524, '1', '', '', '', '2017-01-31 18:12:07', '2017-01-31 18:12:07', 'Test content', 0, '1', '', '', 0, 0), (209, 527, '1', '', '', '', '2017-01-31 18:12:26', '2017-01-31 18:12:26', 'Test content', 0, '1', '', '', 0, 0), (210, 530, '1', '', '', '', '2017-01-31 18:12:50', '2017-01-31 18:12:50', 'Test content', 0, '1', '', '', 0, 0), (211, 533, '1', '', '', '', '2017-02-01 16:56:36', '2017-02-01 16:56:36', 'Test content', 0, '1', '', '', 0, 0), (212, 536, '1', '', '', '', '2017-02-01 16:57:48', '2017-02-01 16:57:48', 'Test content', 0, '1', '', '', 0, 0), (213, 539, '1', '', '', '', '2017-02-01 17:00:31', '2017-02-01 17:00:31', 'Test content', 0, '1', '', '', 0, 0), (214, 542, '1', '', '', '', '2017-02-01 17:01:08', '2017-02-01 17:01:08', 'Test content', 0, '1', '', '', 0, 0), (215, 545, '1', '', '', '', '2017-02-01 17:01:19', '2017-02-01 17:01:19', 'Test content', 0, '1', '', '', 0, 0), (216, 548, '1', '', '', '', '2017-02-01 17:01:38', '2017-02-01 17:01:38', 'Test content', 0, '1', '', '', 0, 0), (217, 551, '1', '', '', '', '2017-02-01 17:02:50', '2017-02-01 17:02:50', 'Test content', 0, '1', '', '', 0, 0), (218, 554, '1', '', '', '', '2017-02-01 17:06:49', '2017-02-01 17:06:49', 'Test content', 0, '1', '', '', 0, 0), (219, 557, '1', '', '', '', '2017-02-01 17:07:46', '2017-02-01 17:07:46', 'Test content', 0, '1', '', '', 0, 0), (220, 560, '1', '', '', '', '2017-06-14 14:15:04', '2017-06-14 14:15:04', 'Test content', 0, '1', '', '', 0, 0), (221, 563, '1', '', '', '', '2017-06-14 14:25:40', '2017-06-14 14:25:40', 'Test content', 0, '1', '', '', 0, 0), (222, 566, '1', '', '', '', '2017-06-20 12:19:21', '2017-06-20 12:19:21', 'Test content', 0, '1', '', '', 0, 0), (223, 570, '1', '', '', '', '2017-06-20 12:33:48', '2017-06-20 12:33:48', 'Test content', 0, '1', '', '', 0, 0), (224, 573, '1', '', '', '', '2017-06-20 12:35:04', '2017-06-20 12:35:04', 'Test content', 0, '1', '', '', 0, 0), (225, 574, '1', '', '', '', '2017-06-20 12:38:46', '2017-06-20 12:38:46', 'Test content', 0, '1', '', '', 0, 0), (226, 577, '1', '', '', '', '2017-06-20 12:39:17', '2017-06-20 12:39:17', 'Test content', 0, '1', '', '', 0, 0), (227, 580, '1', '', '', '', '2017-06-20 12:39:43', '2017-06-20 12:39:43', 'Test content', 0, '1', '', '', 0, 0), (228, 583, '1', '', '', '', '2017-06-20 12:41:43', '2017-06-20 12:41:43', 'Test content', 0, '1', '', '', 0, 0), (229, 586, '1', '', '', '', '2017-06-20 12:42:57', '2017-06-20 12:42:57', 'Test content', 0, '1', '', '', 0, 0), (230, 589, '1', '', '', '', '2017-06-20 12:43:22', '2017-06-20 12:43:22', 'Test content', 0, '1', '', '', 0, 0), (231, 592, '1', '', '', '', '2017-06-20 12:43:43', '2017-06-20 12:43:43', 'Test content', 0, '1', '', '', 0, 0); -- -------------------------------------------------------- -- -- Table structure for table `links` -- CREATE TABLE `links` ( `link_id` bigint(20) UNSIGNED NOT NULL, `link_url` varchar(255) NOT NULL DEFAULT '', `link_name` varchar(255) NOT NULL DEFAULT '', `link_image` varchar(255) NOT NULL DEFAULT '', `link_target` varchar(25) NOT NULL DEFAULT '', `link_description` varchar(255) NOT NULL DEFAULT '', `link_visible` varchar(20) 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) NOT NULL DEFAULT '', `link_notes` mediumtext NOT NULL, `link_rss` varchar(255) NOT NULL DEFAULT '' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -------------------------------------------------------- -- -- Table structure for table `options` -- CREATE TABLE `options` ( `option_id` bigint(20) UNSIGNED NOT NULL, `option_name` varchar(64) NOT NULL DEFAULT '', `option_value` longtext NOT NULL, `autoload` varchar(20) NOT NULL DEFAULT 'yes' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `options` -- INSERT INTO `options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (1, 'siteurl', 'http://localhost:8000', 'yes'), (2, 'blogname', 'Wordpress Corcel', 'yes'), (3, 'blogdescription', 'Just another WordPress site', 'yes'), (4, 'users_can_register', '0', 'yes'), (5, 'admin_email', 'juniorgro@gmail.com', 'yes'), (6, 'start_of_week', '1', 'yes'), (7, 'use_balanceTags', '0', 'yes'), (8, 'use_smilies', '1', 'yes'), (9, 'require_name_email', '1', 'yes'), (10, 'comments_notify', '1', 'yes'), (11, 'posts_per_rss', '10', 'yes'), (12, 'rss_use_excerpt', '0', 'yes'), (13, 'mailserver_url', 'mail.example.com', 'yes'), (14, 'mailserver_login', 'login@example.com', 'yes'), (15, 'mailserver_pass', 'password', 'yes'), (16, 'mailserver_port', '110', 'yes'), (17, 'default_category', '1', 'yes'), (18, 'default_comment_status', 'open', 'yes'), (19, 'default_ping_status', 'open', 'yes'), (20, 'default_pingback_flag', '0', 'yes'), (21, 'posts_per_page', '10', 'yes'), (22, 'date_format', 'F j, Y', 'yes'), (23, 'time_format', 'g:i a', 'yes'), (24, 'links_updated_date_format', 'F j, Y g:i a', 'yes'), (25, 'comment_moderation', '0', 'yes'), (26, 'moderation_notify', '1', 'yes'), (27, 'permalink_structure', '', 'yes'), (28, 'gzipcompression', '0', 'yes'), (29, 'hack_file', '0', 'yes'), (30, 'blog_charset', 'UTF-8', 'yes'), (31, 'moderation_keys', '', 'no'), (32, 'active_plugins', 'a:0:{}', 'yes'), (33, 'home', 'http://localhost:8000', 'yes'), (34, 'category_base', '', 'yes'), (35, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'), (36, 'advanced_edit', '0', 'yes'), (37, 'comment_max_links', '2', 'yes'), (38, 'gmt_offset', '0', 'yes'), (39, 'default_email_category', '1', 'yes'), (40, 'recently_edited', '', 'no'), (41, 'template', 'twentyfourteen', 'yes'), (42, 'stylesheet', 'twentyfourteen', 'yes'), (43, 'comment_whitelist', '1', 'yes'), (44, 'blacklist_keys', '', 'no'), (45, 'comment_registration', '0', 'yes'), (46, 'html_type', 'text/html', 'yes'), (47, 'use_trackback', '0', 'yes'), (48, 'default_role', 'subscriber', 'yes'), (49, 'db_version', '27916', 'yes'), (50, 'uploads_use_yearmonth_folders', '1', 'yes'), (51, 'upload_path', '', 'yes'), (52, 'blog_public', '0', 'yes'), (53, 'default_link_category', '2', 'yes'), (54, 'show_on_front', 'posts', 'yes'), (55, 'tag_base', '', 'yes'), (56, 'show_avatars', '1', 'yes'), (57, 'avatar_rating', 'G', 'yes'), (58, 'upload_url_path', '', 'yes'), (59, 'thumbnail_size_w', '150', 'yes'), (60, 'thumbnail_size_h', '150', 'yes'), (61, 'thumbnail_crop', '1', 'yes'), (62, 'medium_size_w', '300', 'yes'), (63, 'medium_size_h', '300', 'yes'), (64, 'avatar_default', 'mystery', 'yes'), (65, 'large_size_w', '1024', 'yes'), (66, 'large_size_h', '1024', 'yes'), (67, 'image_default_link_type', 'file', 'yes'), (68, 'image_default_size', '', 'yes'), (69, 'image_default_align', '', 'yes'), (70, 'close_comments_for_old_posts', '0', 'yes'), (71, 'close_comments_days_old', '14', 'yes'), (72, 'thread_comments', '1', 'yes'), (73, 'thread_comments_depth', '5', 'yes'), (74, 'page_comments', '0', 'yes'), (75, 'comments_per_page', '50', 'yes'), (76, 'default_comments_page', 'newest', 'yes'), (77, 'comment_order', 'asc', 'yes'), (78, 'sticky_posts', 'a:0:{}', 'yes'), (79, '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'), (80, 'widget_text', 'a:0:{}', 'yes'), (81, 'widget_rss', 'a:0:{}', 'yes'), (82, 'uninstall_plugins', 'a:0:{}', 'no'), (83, 'timezone_string', '', 'yes'), (84, 'page_for_posts', '0', 'yes'), (85, 'page_on_front', '0', 'yes'), (86, 'default_post_format', '0', 'yes'), (87, 'link_manager_enabled', '0', 'yes'), (88, 'initial_db_version', '27916', 'yes'), (89, 'wp_user_roles', 'a:5:{s:13:"administrator";a:2:{s:4:"name";s:13:"Administrator";s:12:"capabilities";a:62:{s:13:"switch_themes";b:1;s:11:"edit_themes";b:1;s:16:"activate_plugins";b:1;s:12:"edit_plugins";b:1;s:10:"edit_users";b:1;s:10:"edit_files";b:1;s:14:"manage_options";b:1;s:17:"moderate_comments";b:1;s:17:"manage_categories";b:1;s:12:"manage_links";b:1;s:12:"upload_files";b:1;s:6:"import";b:1;s:15:"unfiltered_html";b:1;s:10:"edit_posts";b:1;s:17:"edit_others_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:10:"edit_pages";b:1;s:4:"read";b:1;s:8:"level_10";b:1;s:7:"level_9";b:1;s:7:"level_8";b:1;s:7:"level_7";b:1;s:7:"level_6";b:1;s:7:"level_5";b:1;s:7:"level_4";b:1;s:7:"level_3";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:17:"edit_others_pages";b:1;s:20:"edit_published_pages";b:1;s:13:"publish_pages";b:1;s:12:"delete_pages";b:1;s:19:"delete_others_pages";b:1;s:22:"delete_published_pages";b:1;s:12:"delete_posts";b:1;s:19:"delete_others_posts";b:1;s:22:"delete_published_posts";b:1;s:20:"delete_private_posts";b:1;s:18:"edit_private_posts";b:1;s:18:"read_private_posts";b:1;s:20:"delete_private_pages";b:1;s:18:"edit_private_pages";b:1;s:18:"read_private_pages";b:1;s:12:"delete_users";b:1;s:12:"create_users";b:1;s:17:"unfiltered_upload";b:1;s:14:"edit_dashboard";b:1;s:14:"update_plugins";b:1;s:14:"delete_plugins";b:1;s:15:"install_plugins";b:1;s:13:"update_themes";b:1;s:14:"install_themes";b:1;s:11:"update_core";b:1;s:10:"list_users";b:1;s:12:"remove_users";b:1;s:9:"add_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'), (90, 'widget_search', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'), (91, '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'), (92, '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'), (93, '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'), (94, 'widget_meta', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'), (95, 'sidebars_widgets', 'a:5:{s:19:"wp_inactive_widgets";a:0:{}s:9:"sidebar-1";a:6:{i:0;s:8:"search-2";i:1;s:14:"recent-posts-2";i:2;s:17:"recent-comments-2";i:3;s:10:"archives-2";i:4;s:12:"categories-2";i:5;s:6:"meta-2";}s:9:"sidebar-2";a:0:{}s:9:"sidebar-3";a:0:{}s:13:"array_version";i:3;}', 'yes'), (96, 'cron', 'a:4:{i:1408605300;a:1:{s:20:"wp_maybe_auto_update";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:10:"twicedaily";s:4:"args";a:0:{}s:8:"interval";i:43200;}}}i:1408616761;a:3:{s:16:"wp_version_check";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:10:"twicedaily";s:4:"args";a:0:{}s:8:"interval";i:43200;}}s:17:"wp_update_plugins";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:10:"twicedaily";s:4:"args";a:0:{}s:8:"interval";i:43200;}}s:16:"wp_update_themes";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:10:"twicedaily";s:4:"args";a:0:{}s:8:"interval";i:43200;}}}i:1408659972;a:1:{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:7:"version";i:2;}', 'yes'), (105, '_transient_random_seed', '400d2c0e4869149f41fb458f4c5971c8', 'yes'), (106, 'auth_key', 'BzUGfHeSYf|2V5xlRqc[P#vwZ9u([Opee#o^ql5]+X.-y]y]=9DT9', 'yes'), (108, 'logged_in_key', '&s<1dV:~Is2{.@<>>;cK{|*j6MwqFTz0m|GsB a@(**6[6E3~HnG_(&j_+UX=eeq', 'yes'), (109, 'logged_in_salt', 'n!,pY9HWh@_rM+_]+$0A+E~`>epA:q-eig,Tv!0ld:iwNNCW!xDw-BdNlPrMtqv@', 'yes'), (110, 'nonce_key', '^>7lg-@IhAe76d<~&,yTB $}#hF]$T;V@lZIPE6(+barZ0D6BThe fourth and likely final beta for WordPress 4.0 is now available. We’ve made more than 250 changes in the past month, including:

\n
    \n
  • Further improvements to the editor scrolling experience, especially when it comes to the second column of boxes.
    • \n
  • Better handling of small screens in the media library modals.
    • \n
  • A separate bulk selection mode for the media library grid view.
    • \n
  • Improvements to the installation language selector.
    • \n
  • Visual tweaks to plugin details and customizer panels.
    • \n
\n

We need your help. We’re still aiming for a release this month, which means the next week will be critical for identifying and squashing bugs. If you’re just joining us, please see the Beta 1 announcement post for what to look out for.

\n

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums, where friendly moderators are standing by. Plugin developers, if you haven’t tested WordPress 4.0 yet, now is the time — and be sure to update the “tested up to” version for your plugins so they’re listed as compatible with 4.0.

\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.0, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

\n

We are working hard
\nTo finish up 4.0
\nWill you help us too?

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"http://wordpress.org/news/2014/08/wordpress-4-0-beta-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:1;a:6:{s:4:"data";s:45:"\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:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:32:"WordPress 3.9.2 Security Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2014/08/wordpress-3-9-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/news/2014/08/wordpress-3-9-2/#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:"Wed, 06 Aug 2014 19:04:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3269";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:377:"WordPress 3.9.2 is now available as a security release for all previous versions. We strongly encourage you to update your sites immediately. This release fixes a possible denial of service issue in PHP’s XML processing, reported by Nir Goldshlager of the Salesforce.com Product Security Team. It was fixed by Michael Adams and Andrew Nacin of the WordPress […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Andrew Nacin";s: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:2352:"

WordPress 3.9.2 is now available as a security release for all previous versions. We strongly encourage you to update your sites immediately.

\n

This release fixes a possible denial of service issue in PHP’s XML processing, reported by Nir Goldshlager of the Salesforce.com Product Security Team. It was fixed by Michael Adams and Andrew Nacin of the WordPress security team and David Rothstein of the Drupal security team. This is the first time our two projects have coordinated joint security releases.

\n

WordPress 3.9.2 also contains other security changes:

\n
    \n
  • Fixes a possible but unlikely code execution when processing widgets (WordPress is not affected by default), discovered by Alex Concha of the WordPress security team.
    • \n
  • Prevents information disclosure via XML entity attacks in the external GetID3 library, reported by Ivan Novikov of ONSec.
    • \n
  • Adds protections against brute attacks against CSRF tokens, reported by David Tomaschik of the Google Security Team.
    • \n
  • Contains some additional security hardening, like preventing cross-site scripting that could be triggered only by administrators.
    • \n
\n

We appreciated responsible disclosure of these issues directly to our security team. For more information, see the release notes or consult the list of changes.

\n

Download WordPress 3.9.2 or venture over to Dashboard → Updates and simply click “Update Now”.

\n

Sites that support automatic background updates will be updated to WordPress 3.9.2 within 12 hours. (If you are still on WordPress 3.8.3 or 3.7.3, you will also be updated to 3.8.4 or 3.7.4. We don’t support older versions, so please update to 3.9.2 for the latest and greatest.)

\n

Already testing WordPress 4.0? The third beta is now available (zip) and it contains these security fixes.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/08/wordpress-3-9-2/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:45:"\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:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.0 Beta 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/07/wordpress-4-0-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:64:"http://wordpress.org/news/2014/07/wordpress-4-0-beta-2/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 18 Jul 2014 21:15:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3261";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:374:"WordPress 4.0 Beta 2 is now available for download and testing. This is software still in development, so we don’t recommend that you run it on a production site. To get the beta, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip). For more of what’s new in version 4.0, check out […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Helen Hou-Sandi";s: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:1738:"

WordPress 4.0 Beta 2 is now available for download and testing. This is software still in development, so we don’t recommend that you run it on a production site. To get the beta, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

\n

For more of what’s new in version 4.0, check out the Beta 1 blog post. Some of the changes in Beta 2 include:

\n
    \n
  • Further refinements for the the plugin installation and media library experiences.
    • \n
  • Updated TinyMCE, which now includes better indentation for lists and the restoration of the color picker.
    • \n
  • Cookies are now tied to a session internally, so if you have trouble logging in, #20276 may be the culprit.
    • \n
  • Various bug fixes (there were nearly 170 changes since last week).
    • \n
\n

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. Or, if you’re comfortable writing a bug report, file one on the WordPress Trac. There, you can also find a list of known bugs and everything we’ve fixed.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"http://wordpress.org/news/2014/07/wordpress-4-0-beta-2/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:3;a:6:{s:4:"data";s:45:"\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:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.0 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:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/07/wordpress-4-0-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:64:"http://wordpress.org/news/2014/07/wordpress-4-0-beta-1/#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, 10 Jul 2014 10:17:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3248";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:329:"WordPress 4.0 Beta 1 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.0, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Helen Hou-Sandi";s: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:4025:"

WordPress 4.0 Beta 1 is now available!

\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.0, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

\n

4.0 is due out next month, but to get there, we need your help testing what we’ve been working on:

\n
    \n
  • Previews of embedding via URLs in the visual editor and the “Insert from URL” tab in the media modal. Try pasting a URL (such as a WordPress.tv or YouTube video) onto its own line in the visual editor. (#28195, #15490)
    • \n
  • The Media Library now has a “grid” view in addition to the existing list view. Clicking on an item takes you into a modal where you can see a larger preview and edit information about that attachment, and you can navigate between items right from the modal without closing it. (#24716)
    • \n
  • We’re freshening up the plugin install experience. You’ll see some early visual changes as well as more information when searching for plugins and viewing details. (#28785, #27440)
    • \n
  • Selecting a language when you run the installation process. (#28577)
    • \n
  • The editor intelligently resizes and its top and bottom bars pin when needed. Browsers don’t like to agree on where to put things like cursors, so if you find a bug here, please also let us know your browser and operating system. (#28328)
    • \n
  • We’ve made some improvements to how your keyboard and cursor interact with TinyMCE views such as the gallery preview. Much like the editor resizing and scrolling improvements, knowing about your setup is particularly important for bug reports here. (#28595)
    • \n
  • Widgets in the Customizer are now loaded in a separate panel. (#27406)
    • \n
  • We’ve also made some changes to some formatting functions, so if you see quotes curling in the wrong direction, please file a bug report.
    • \n
\n

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

\n

Developers: Never fear, we haven’t forgotten you. There’s plenty for you, too – more on that in upcoming posts. In the meantime, check out the API for panels in the Customizer.

\n

Happy testing!

\n

Plugins, editor
\nMedia, things in between
\nPlease help look for bugs

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"http://wordpress.org/news/2014/07/wordpress-4-0-beta-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: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:4;a:6:{s:4:"data";s:42:"\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:35:"WordPress 3.9.1 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2014/05/wordpress-3-9-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/news/2014/05/wordpress-3-9-1/#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 May 2014 18:40: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:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3241";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:385:"After three weeks and more than 9 million downloads of WordPress 3.9, we’re pleased to announce that WordPress 3.9.1 is now available. This maintenance release fixes 34 bugs in 3.9, including numerous fixes for multisite networks, customizing widgets while previewing themes, and the updated visual editor. We’ve also made some improvements to the new audio/video […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Andrew Nacin";s: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:3077:"

After three weeks and more than 9 million downloads of WordPress 3.9, we’re pleased to announce that WordPress 3.9.1 is now available.

\n

This maintenance release fixes 34 bugs in 3.9, including numerous fixes for multisite networks, customizing widgets while previewing themes, and the updated visual editor. We’ve also made some improvements to the new audio/video playlists feature and made some adjustments to improve performance. For a full list of changes, consult the list of tickets and the changelog.

\n

If you are one of the millions already running WordPress 3.9, we’ve started rolling out automatic background updates for 3.9.1. For sites that support them, of course.

\n

Download WordPress 3.9.1 or venture over to Dashboard → Updates and simply click “Update Now.”

\n

Thanks to all of these fine individuals for contributing to 3.9.1: Aaron Jorbin, Andrew Nacin, Andrew Ozz, Brian Richards, Chris Blower, Corey McKrill, Daniel Bachhuber, Dominik Schilling, feedmeastraycat, Gregory Cornelius, Helen Hou-Sandi, imath, Janneke Van Dorpe, Jeremy Felt, John Blackbourn, Konstantin Obenland, Lance Willett, m_i_n, Marius Jensen, Mark Jaquith, Milan Dinić, Nick Halsey, pavelevap, Scott Taylor, Sergey Biryukov, and Weston Ruter.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/05/wordpress-3-9-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: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:5;a:6:{s:4:"data";s:42:"\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 3.9 “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:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:40:"http://wordpress.org/news/2014/04/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:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:49:"http://wordpress.org/news/2014/04/smith/#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:"Wed, 16 Apr 2014 18: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:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3154";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:411:"Version 3.9 of WordPress, named “Smith” in honor of jazz organist Jimmy Smith, is available for download or update in your WordPress dashboard. This release features a number of refinements that we hope you’ll love. A smoother media editing experience Improved visual editing The updated visual editor has improved speed, accessibility, and mobile support. You can paste into the […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:23297:"

Version 3.9 of WordPress, named “Smith” in honor of jazz organist Jimmy Smith, is available for download or update in your WordPress dashboard. This release features a number of refinements that we hope you’ll love.

\n\n

A smoother media editing experience

\n
\n

editor

\n

Improved visual editing

\n

The updated visual editor has improved speed, accessibility, and mobile support. You can paste into the visual editor from your word processor without wasting time to clean up messy styling. (Yeah, we’re talking about you, Microsoft Word.)

\n
\n
\n
\n

image

\n

Edit images easily

\n

With quicker access to crop and rotation tools, it’s now much easier to edit your images while editing posts. You can also scale images directly in the editor to find just the right fit.

\n
\n
\n
\n

dragdrop

\n

Drag and drop your images

\n

Uploading your images is easier than ever. Just grab them from your desktop and drop them in the editor.

\n
\n
\n
\n

Gallery previews

\n

gallery

\n

Galleries display a beautiful grid of images right in the editor, just like they do in your published post.

\n
\n

Do more with audio and video

\n\nAin\'t Misbehavin\'\nDavenport Blues\nBuddy Bolden\'s Blues\nSquaty Roo\nDixie Blues\nWolverine Blues\n\n

Images have galleries; now we’ve added simple audio and video playlists, so you can showcase your music and clips.

\n
\n

Live widget and header previews

\n
\n
\n

Add, edit, and rearrange your site’s widgets right in the theme customizer. No “save and surprise” — preview your changes live and only save them when you’re ready.

\n

The improved header image tool also lets you upload, crop, and manage headers while customizing your theme.

\n
\n

Stunning new theme browser

\n

theme
\nLooking for a new theme should be easy and fun. Lose yourself in the boundless supply of free WordPress.org themes with the beautiful new theme browser.

\n
\n

The Crew

\n

This release was led by Andrew Nacin and Mike Schroder, with the help of these fine individuals. There are 267 contributors with props in this release, a new high:

\n

Aaron D. Campbell, Aaron Jorbin, Adam Harley, Adam Silverstein, adelval, Ajay, Akeda Bagus, Alex Concha, Alex Shiels, Alison Barrett, Allan Collins, Amy Hendrix (sabreuse), Andrea Fercia, Andrew Nacin, Andrew Norcross, Andrew Ozz, Andrey "Rarst" Savchenko, Andy Keith, Andy Skelton, Anton Timmermans, Aubrey Portwood, Barry, Bartosz Romanowski, bassgang, bcworkz, Ben Dunkle, Bernhard Riedl, bigdawggi, Bob Gregor, bobbingwide, Brad Touesnard, bradparbs, bramd, Brandon Kraft, brasofilo, bravokeyl, Bryan Petty, cgaffga, Chirag Swadia, Chouby, Chris Blower, Chris Marslender, Chris Olbekson, Chris Scott, chriseverson, chrisguitarguy, Christopher Finke, ciantic, Comparativa de Bancos, Connor Jennings, Cor van Noorloos, Corphi, cramdesign, Daniel Bachhuber, Daniel Jalkut (Red Sweater), Danny de Haan, Daryl Koopersmith, Dave Kellam (eightface), DaveE, David A. Kennedy, David Anderson, David Marichal, Denis de Bernardy, Dion Hulse, Dominik Schilling, Doug Wollison, Drew Jaynes, DrProtocols, Dustin Filippini, eatingrules, edik, Elio Rivero, enej, Eric Andrew Lewis, Eric Mann, Erica Varlese, Erick Hitter, Evan Anderson, Fahmi Adib, fboender, Frank Klein, Gary Cao, Gary Jones, Gary Pendergast, genkisan, Gennady Kovshenin, George Stephanis, Graham Armfield, Grant Mangham, Gregory Cornelius, Gregory Karpinsky (@tivnet), hakre, hanni, Helen Hou-Sandí, ippetkov, Ipstenu (Mika Epstein), J.D. Grimes, Jack Reichert, jameslee, Janneke Van Dorpe, janrenn, JayCC, Jeff Sebring, Jen Mylo, Jeremy Felt, Jesin A, Jesper Johansen (jayjdk), jnielsendotnet, Joan Artes, Joe Dolson, Joe Hoyle, John Blackbourn, John James Jacoby, John P. Bloch, John Regan, Jon Cave, Jonas Bolinder (jond3r), Joost de Valk, Josh Pollock, Joshua Abenazer, jstraitiff, Julio Potier, Justin Kopepasah, Justin Sainton, K.Adam White, Kailey (trepmal), Kaspars, Kelly Dwan, kerikae, Kevin Worthington, Kim Parsell, Kirk Wight, kitchin, klihelp, Knut Sparhell, Konstantin Kovshenin, Konstantin Obenland, Krzysiek Drozdz, Lance Willett, Lee Willis, lpointet, Luc De Brouwer, Lucas Karpiuk, Luke Woodward, Mark Barnes, Mark Jaquith, Marko Heijnen, Marventus, Matt (Thomas) Miklic, Matt Banks, Matt Mullenweg, Matthew Boynes, Matthew Denton, Matthew Haines-Young, mattonomics, mattyrob, Matías Ventura, Max Cutler, mcadwell, Mel Choyce, meloniq, Michael Arestad, Michel - xiligroup dev, Miguel Fonseca, Mike Burns, Mike Hansen, Mike Manger, Mike Schinkel, Mike Schroder, mikecorkum, mitcho (Michael Yoshitaka Erlewine), Mohammad Jangda, Morgan Estes, Morten Rand-Hendriksen, Naoko Takano, Nashwan Doaqan, nendeb55, Nick Halsey, Nicole Arnold, Nikhil Vimal (NikV), Nivi Jah, nofearinc, Nuno Morgadinho, olivM, Omer Korner, OriginalEXE, oso96_2000, patricknami, Paul Bearne, Paul Gibbs, Paul Wilde, pavelevap, Peter Westwood, Philip Arthur Moore, Pippin Williamson, Prasath Nadarajah, prettyboymp, Raam Dev, Rachel Baker, Ram Ratan Maurya, ramonchiara, Rescuework Support, Rhys Wynne, Ricardo Correia, Richard Sweeney, Richard Tape, richard2222, Ricky Lee Whittemore, Robert Chapin, robmiller, Rodrigo Primo, romaimperator, roothorick, Ruud Laan, Ryan Boren, Ryan McCue, Sal Ferrarello, Samuel Wood (Otto), Sandeep, Scott Lee, Scott Reilly, Scott Taylor, ScreenfeedFr, scribu, sdasse, Sean Butze, Sean Hayes, Sean Nessworthy, Sergey Biryukov, shahpranaf, Shaun Andrews, ShinichiN, Simon Prosser, Simon Wheatley, Siobhan, Siobhan Bamber (siobhyb), sirzooro, solarissmoke, sonjanyc, Spencer Finnell, Spencer Piontkowski, stephcook22, Stephen Edgar, Stephen Harris, Steve Bruner, Steven Word, Takayuki Miyauchi, Tanner Moushey, Taylor Lovett, tbrams, TobiasBg, Tom Auger, Tom Willmot, Topher, topquarky, Torsten Landsiedel, Toru, Travis Smith, Umesh Kumar, undergroundnetwork, VarunAgw, wawco, Weston Ruter, wokamoto, xsonic, Yoav Farhi, Yuri Victor, Zach Tirrell, and Ze Fontainhas. Also thanks to Michael Pick for producing the release video.

\n

If you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress. See you soon for version 4.0!

\n";s: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:45:"http://wordpress.org/news/2014/04/smith/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:45:"\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:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:33:"WordPress 3.9 Release Candidate 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"http://wordpress.org/news/2014/04/wordpress-3-9-release-candidate-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:77:"http://wordpress.org/news/2014/04/wordpress-3-9-release-candidate-2/#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:"Tue, 15 Apr 2014 09:47:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3151";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:356:"The second release candidate for WordPress 3.9 is now available for testing. If you haven’t tested 3.9 yet, you’re running out of time! We made about five dozen changes since the first release candidate, and those changes are all helpfully summarized in our weekly post on the development blog. Probably the biggest fixes are to live […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Andrew Nacin";s: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:2273:"

The second release candidate for WordPress 3.9 is now available for testing.

\n

If you haven’t tested 3.9 yet, you’re running out of time! We made about five dozen changes since the first release candidate, and those changes are all helpfully summarized in our weekly post on the development blog. Probably the biggest fixes are to live widget previews and the new theme browser, along with some extra TinyMCE compatibility and some RTL fixes.

\n

Plugin authors: Could you test your plugins against 3.9, and if they’re compatible, make sure they are marked as tested up to 3.9? It only takes a few minutes and this really helps make launch easier. Be sure to follow along the core development blog; we’ve been posting notes for developers for 3.9. (For example: HTML5, symlinks, MySQL, Plupload.)

\n

To test WordPress 3.9 RC2, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). If you’d like to learn more about what’s new in WordPress 3.9, visit the nearly complete About screen in your dashboard ( → About in the toolbar) and also check out the Beta 1 post.

\n

This is for testing,
\nso not recommended for
\nproduction sites—yet.

\n";s: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:73:"http://wordpress.org/news/2014/04/wordpress-3-9-release-candidate-2/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:42:"\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:35:"WordPress 3.8.3 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2014/04/wordpress-3-8-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/news/2014/04/wordpress-3-8-3/#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:"Mon, 14 Apr 2014 19:29:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3145";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:338:"WordPress 3.8.3 is now available to fix a small but unfortunate bug in the WordPress 3.8.2 security release. The “Quick Draft” tool on the dashboard screen was broken in the 3.8.2 update. If you tried to use it, your draft would disappear and it wouldn’t save. While we doubt anyone was writing a novella using […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Andrew Nacin";s: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:2339:"

WordPress 3.8.3 is now available to fix a small but unfortunate bug in the WordPress 3.8.2 security release.

\n

The “Quick Draft” tool on the dashboard screen was broken in the 3.8.2 update. If you tried to use it, your draft would disappear and it wouldn’t save. While we doubt anyone was writing a novella using this tool, any loss of content is unacceptable to us.

\n

We recognize how much trust you place in us to safeguard your content, and we take this responsibility very seriously. We’re sorry we let you down.

\n

We’ve all lost words we’ve written before, like an email thanks to a cat on the keyboard or a term paper to a blue screen of death. Over the last few WordPress releases, we’ve made a number of improvements to features like autosaves and revisions. With revisions, an old edit can always be restored. We’re trying our hardest to save your content somewhere even if your power goes out or your browser crashes. We even monitor your internet connection and prevent you from hitting that “Publish” button at the exact moment the coffee shop Wi-Fi has a hiccup.

\n

It’s possible that the quick draft you lost last week is still in the database, and just hidden from view. As an added complication, these “discarded drafts” normally get deleted after seven days, and it’s already been six days since the release. If we were able to rescue your draft, you’ll see it on the “All Posts” screen after you update to 3.8.3. (We’ll also be pushing 3.8.3 out as a background update, so you may just see a draft appear.)

\n

So, if you tried to jot down a quick idea last week, I hope WordPress has recovered it for you. Maybe it’ll turn into that novella.

\n

Download WordPress 3.8.3 or click “Update Now” on Dashboard → Updates.

\n

This affected version 3.7.2 as well, so we’re pushing a 3.7.3 to these installs, but we’d encourage you to update to the latest and greatest.

\n
\n

Now for some good news:
\nWordPress 3.9 is near.
\nExpect it this week

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/04/wordpress-3-8-3/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:45:"\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:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"WordPress 3.9 Release Candidate";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:66:"http://wordpress.org/news/2014/04/wordpress-3-9-release-candidate/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:75:"http://wordpress.org/news/2014/04/wordpress-3-9-release-candidate/#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:"Tue, 08 Apr 2014 21:05:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:11:"Development";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3129";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:338:"As teased earlier, the first release candidate for WordPress 3.9 is now available for testing! We hope to ship WordPress 3.9 next week, but we need your help to get there. If you haven’t tested 3.9 yet, there’s no time like the present. (Please, not on a production site, unless you’re adventurous.) To test WordPress 3.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:12:"Andrew Nacin";s: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:2967:"

As teased earlier, the first release candidate for WordPress 3.9 is now available for testing!

\n

We hope to ship WordPress 3.9 next week, but we need your help to get there. If you haven’t tested 3.9 yet, there’s no time like the present. (Please, not on a production site, unless you’re adventurous.)

\n

To test WordPress 3.9 RC1, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). If you’d like to learn more about what’s new in WordPress 3.9, visit the work-in-progress About screen in your dashboard ( → About in the toolbar) and check out the Beta 1 post.

\n

Think you’ve found a bug? Please post to the Alpha/Beta area in the support forums. If any known issues come up, you’ll be able to find them here.

\n

If you’re a plugin author, there are two important changes in particular to be aware of:

\n
    \n
  • TinyMCE received a major update, to version 4.0. Any editor plugins written for TinyMCE 3.x might require some updates. (If things broke, we’d like to hear about them so we can make adjustments.) For more, see TinyMCE’s migration guide and API documentation, and the notes on the core development blog.
    • \n
  • WordPress 3.9 now uses the MySQLi Improved extension for sites running PHP 5.5. Any plugins that made direct calls to mysql_* functions will experience some problems on these sites. For more information, see the notes on the core development blog.
    • \n
\n

Be sure to follow along the core development blog, where we will be continuing to post notes for developers for 3.9. (For example, read this if you are using Masonry in your theme.) And please, please update your plugin’s Tested up to version in the readme to 3.9 before April 16.

\n

Release candidate
\nThis haiku’s the easy one
\n3.9 is near

\n";s: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:71:"http://wordpress.org/news/2014/04/wordpress-3-9-release-candidate/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:45:"\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:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:32:"WordPress 3.8.2 Security Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/news/2014/04/wordpress-3-8-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:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/news/2014/04/wordpress-3-8-2/#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:"Tue, 08 Apr 2014 19:04: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:2:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3124";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:355:"WordPress 3.8.2 is now available. This is an important security release for all previous versions and we strongly encourage you to update your sites immediately. This releases fixes a weakness that could let an attacker force their way into your site by forging authentication cookies. This was discovered and fixed by Jon Cave of the WordPress […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Andrew Nacin";s: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:2272:"

WordPress 3.8.2 is now available. This is an important security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

This releases fixes a weakness that could let an attacker force their way into your site by forging authentication cookies. This was discovered and fixed by Jon Cave of the WordPress security team.

\n

It also contains a fix to prevent a user with the Contributor role from improperly publishing posts. Reported by edik.

\n

This release also fixes nine bugs and contains three other security hardening changes:

\n
    \n
  • Pass along additional information when processing pingbacks to help hosts identify potentially abusive requests.
    • \n
  • Fix a low-impact SQL injection by trusted users. Reported by Tom Adams of dxw.
    • \n
  • Prevent possible cross-domain scripting through Plupload, the third-party library WordPress uses for uploading files. Reported by Szymon Gruszecki.
    • \n
\n

We appreciated responsible disclosure of these security issues directly to our security team. For more information on all of the changes, see the release notes or consult the list of changes.

\n

Download WordPress 3.8.2 or venture over to Dashboard → Updates and simply click “Update Now.”

\n

Sites that support automatic background updates will be updated to WordPress 3.8.2 within 12 hours. If you are still on WordPress 3.7.1, you will be updated to 3.7.2, which contains the same security fixes as 3.8.2. We don’t support older versions, so please update to 3.8.2 for the latest and greatest.

\n

Already testing WordPress 3.9? The first release candidate is now available (zip) and it contains these security fixes. Look for a full announcement later today; we expect to release 3.9 next week.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/04/wordpress-3-8-2/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:31:"http://wordpress.org/news/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:6:"hourly";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 20 Aug 2014 22:26:16 GMT";s:12:"content-type";s:23:"text/xml; charset=UTF-8";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:10:"x-pingback";s:36:"http://wordpress.org/news/xmlrpc.php";s:13:"last-modified";s:29:"Fri, 15 Aug 2014 05:06:19 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";}s:5:"build";s:14:"20140820222237";}', 'no'); INSERT INTO `options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (117, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1408616776', 'no'), (118, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1408573576', 'no'), (119, '_transient_timeout_feed_867bd5c64f85878d03a060509cd2f92c', '1408616777', 'no'); INSERT INTO `options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (120, '_transient_feed_867bd5c64f85878d03a060509cd2f92c', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:61:"\n \n \n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"WordPress Planet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:28:"http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:2:"en";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:47:"WordPress Planet - http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:50:{i:0;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:77:"WPTavern: How to Find All Posts Using a Specific File Attachment In WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28834";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://wptavern.com/how-to-find-all-posts-using-a-specific-file-attachment?utm_source=rss&utm_medium=rss&utm_campaign=how-to-find-all-posts-using-a-specific-file-attachment";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1724:"

In a previous article, I mentioned how WordPress doesn’t provide information to locate posts where an attachment is in use. Comments to the article indicate others are interested in having this information as well. Find Posts Using Attachment created by Sergey Biryukov, is an easy to use plugin that solves this problem.

\n

The plugin adds a Used In column to the list view in the media library as well as to the attachment details modal. Not only can you find posts that use the image in a post or as a featured image, it works with custom post types too.

\nUsed In ColumnUsed In Column\n

Although it’s primarily for images, it also tells you where other attachment types are used in posts such as mp3s or text files. If you need to change or update attachments in the media library but don’t remember where they’re being used, this plugin is invaluable.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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 Aug 2014 21:22:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"WPTavern: Akismet Account Dashboard Gets a Major Overhaul";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28804";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:158:"http://wptavern.com/akismet-account-dashboard-gets-a-major-overhaul?utm_source=rss&utm_medium=rss&utm_campaign=akismet-account-dashboard-gets-a-major-overhaul";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2902:"

Akismet announced a redesign and complete update of the account dashboard today. Finding out what’s going on with your Akismet account is no longer a cryptic process thanks to the new additions to the dashboard. It now includes helpful stats and a full listing of all your active sites.

\n

akismet-dashboard

\n

Each active account links to a full page of stats that illustrate how effective Akismet has been at deterring spam recently and historically. It’s also a great reminder of how much time Akismet is saving you every day.

\n

akismet-stats

\n

The active site listing displays each site that has used your API key within the past 90 days, enabling you to monitor exactly where and how your Akismet account is being used. This will better help users to comply with Akismet’s terms of service agreement, which states:

\n

If you obtain or purchase an API Key, you are responsible for maintaining the security of your API Key, and you are fully responsible for all activities that occur under the account and any other actions taken in connection with your API Key.

\n

If you scan your list and find that you have client sites and others for which you’re not directly responsible, you might consider getting in touch with them to sign up for their own Akismet accounts.

\n

Billing information for premium users has been streamlined to its own section with quick access to transaction history and receipts.

\n

In the past it was difficult to know where to go for Akismet support. The new support section adds links to key documentation for common questions, the comprehensive knowledgebase, and the Happiness Engineers support team.

\n

The new user-friendly dashboard is a welcome update to Akismet, which has traditionally gone the most minimal route for getting users connected to the service. Sign in to Akismet with your WordPress.com account to check out all the updates.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Aug 2014 18:57: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: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:41:"Akismet: Welcome To Your New Account Page";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"http://blog.akismet.com/?p=1642";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"http://blog.akismet.com/2014/08/20/welcome-to-your-new-account-page/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2432:"

If you’ve logged in to your Akismet account within the past week or so, you’ve probably noticed quite a few changes. We’re happy to announce some updates to your account dashboard, which will make it easier to manage your Akismet subscription.

\n

The most significant update to the dashboard is an active site listing, which will display each site that has used your API key within the past 90 days. Each site is linked to its dedicated stats URL, which details specific usage. If you have numerous active sites, you can use the handy new search feature to quickly locate one of your URLs. This all makes it possible to know where and how your subscription is being used at any given time.

\n

New Akismet Account Dashboard

\n

In addition to this new stats goodness, the billing information (for users with premium subscriptions) has been moved to a unified section where you can quickly access your transaction history and receipts. This greatly reduces the amount of scrolling that your old dashboard required.

\n

We’ve also added a new Support section with some links to a few popular support documents and an option to get in touch with our Happiness Engineers.

\n

Oh, and the whole thing has been given a fresh coat of paint, as well.

\n

So, log in and take a look. We hope you enjoy these changes and always welcome your feedback. If you notice any problems or have suggestions, please don’t hesitate to get in touch. And because we like to keep the goodies coming, look out for a forthcoming update to our stats pages!


";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Aug 2014 17:00:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Anthony Bubel";s: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:73:"WPTavern: Create and Manage SVG Spritemaps in the WordPress Media 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:28:"http://wptavern.com/?p=28766";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:190:"http://wptavern.com/create-and-manage-svg-spritemaps-in-the-wordpress-media-library?utm_source=rss&utm_medium=rss&utm_campaign=create-and-manage-svg-spritemaps-in-the-wordpress-media-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:4721:"

If you try to upload an SVG in WordPress, you’ll discover that it doesn’t yet have native support for adding SVGs to the media library. However, it’s easy to add them to WordPress’ allowed mime types to remove the restriction via a plugin.

\n

Many users are eager to use SVGs, especially for logos, because of their many advantages over traditional graphics. SVGs can scale to any size without losing quality, which means they will look great on retina displays. They can also be easily styled via CSS to add multiple colors, gradients, filters, etc.

\n

SVG Spritemap is a relatively new plugin that allows you to upload SVGs to the media library. It also adds the ability to create and manage an SVG spritemap, which lets you display and manipulate the images separately while including them in one larger file to reduce HTTP requests.

\n

Once you install the plugin, you’ll find SVG Spritemap under the Media menu. You’ll see that you cannot create a spritemap until you upload a few SVGs.

\n

svg-spritemap

\n

The usage instructions outline the general workflow for using SVG Spritemaps:

\n
    \n
  1. Install and activate the WordPress plugin.
    2. \n
  2. Add SVG images through the Media Uploader.
    3. \n
  3. Select the SVGs for the spritemap in Settings > Media > SVG Spritemap.
    4. \n
\n

You can add SVGs to the medial library as your normally would and they will be displayed like any other file. I’ve added a handful from Flaticon.com as an example:

\n

add-svg

\n

Navigate back to SVG Spritemap and you’ll see all of your available SVGs. Click on the images you want to add to your new spritemap.

\n

create-svg-spritemap

\n

Click on “Update SVG Spritemap” to add your selections. Those files will now be listed as “In Use.” The defs.svg spritemap is automatically generated by the plugin.

\n

Below you will see the URL displayed for the SVG spritemap along with the estimated filesize, which represents the combined filesize of all the SVGs. It doesn’t factor in the gzip compression, so the live filesize is likely to be much smaller than the estimation.

\n

You can reference individual sprites by appending #: and the name of the sprite to this URL, i.e.:

\n
<svg><use xlink:href="http://www.test.dev/wp-content/plugins/svg-spritemap/defs.svg#:bunny"></svg>
\n

You can now display your SVGs on the frontend and further customize them with CSS.

\n

svg-bunny

\n

SVG Browser Support

\n

Before using SVG Spritemap, you should be aware that IE8 does not support external SVG display, but all other major browsers are SVG-capable. This may or may not be important to you. Jonathan Neal, the plugin’s author, has created a way around this with his SVG for Everybody project, which adds special assistance to browsers to display external SVG spritemaps.

\n

If you want an easy way to add SVGs to WordPress and create your own SVG spritemap, this plugin gives you a nice interface for generating it automatically. After testing, I can confirm that it works as advertised. Download SVG Spritemap for free from WordPress.org.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Aug 2014 16:09: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: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:89:"WPTavern: WordPress Customizer Library Provides a Simpler Way to Work with the Customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28715";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:222:"http://wptavern.com/wordpress-customizer-library-provides-a-simpler-way-to-work-with-the-customizer?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-customizer-library-provides-a-simpler-way-to-work-with-the-customizer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3718:"

customizer-library

\n

WordPress’ native customizer has evolved considerably since its early days when it when it was introduced for adding live previews to themes. WordPress 3.9 added widgets to the customizer and the 4.0 release is set to expand the role of the feature into other aspects of WordPress with support for a wider array of controls.

\n

Developers are eager to find new ways to harness the power of the customizer without getting caught up in writing a ton of code. Devin Price, co-owner of DevPress, is working on a new project to create a Customizer Library. The library is designed to abstract out some of the complexity of working with the customizer so that developers can easily add options by defining a simple array.

\n

Price describes the Customizer Library as “a collection of classes and functions that make it a bit easier to develop for the WordPress Customizer.” The library currently includes helper functions for Google fonts and inline styles, but he’s considering removing them into their own repositories in order to keep the project more focused for general use.

\n

The library can be included in a theme or plugin as a git submodule, according to the installation instructions. Price has built in only one custom control, for textarea, but he plans to add additional custom controls as the library matures. It currently supports the following options:

\n
    \n
  • Checkbox
    • \n
  • Select
    • \n
  • Radio
    • \n
  • Upload
    • \n
  • Color
    • \n
  • Textarea
    • \n
  • Select (Typography)
    • \n
\n

An example theme can be found in the Customizer Library Demo repository, which shows how to use the library to create options such as logo, primary and secondary colors, textareas, checkboxes, etc.

\n

The Customizer Library project is somewhat similar to the Kirki plugin, which aims to provide a framework for adding advanced controls. Although the projects are constructed differently, they both abstract the Customizer API to make it easier to add options. As the customizer evolves to become more powerful with more controls, libraries/frameworks like these provide an entry point for developers who want a quick way to build options.

\n

If you want to use the customizer in your projects but are having trouble getting a handle on it, the Customzer Library might be a reasonable starting place. Price is looking for feedback and suggestions as he continues to develop the library as a standalone project. You can help shape its future by joining the discussion on the post where he introduces the 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Aug 2014 00:37:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:84:"WPTavern: Send to WordPress: Chrome Extension Exports Google Docs to WordPress Posts";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28666";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:210:"http://wptavern.com/send-to-wordpress-chrome-extension-exports-google-docs-to-wordpress-posts?utm_source=rss&utm_medium=rss&utm_campaign=send-to-wordpress-chrome-extension-exports-google-docs-to-wordpress-posts";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4354:"photo credit: davekellam - ccphoto credit: davekellam – cc\n

If you’re a Google chrome user, there are many free extensions out there that are useful for getting other applications to work with WordPress. Earlier this year we shared a collection of Chrome extensions for WordPress users, many of which are specifically tailored toward content creation.

\n

Send to WordPress is a handy new extension that recently landed in the Chrome web store. It allows you to export a Google Drive document to WordPress as a post, with all the formatting and images preserved.

\n

Once the extension is installed, you can create a new WordPress post from a Google document by right clicking one or more documents and selecting “Open with” -> “Send to WordPress.”

\n

send-to-wordpress

\n

On the next screen you’ll be asked to enter your WordPress site URL and login credentials. You have the option to send the post to save as a draft or to publish immediately. You can also elect to use your theme’s text styles and add images as attachments.

\n

wordpress-login

\n

Click “Create Post(s)” and your document will be automatically sent to your WordPress site. Once you’ve verified that it’s there, you can edit the post and make any further changes. You’ll find that any images included in your post(s) have been added to your media library.

\n

draft

\n

After testing the extension, I found that it adds some unnecessary classes and inline styles to the content that is sent over. This may be something that you will want to clean up, depending on how you formatted the document in Google Drive.

\n

Why Not Compose Directly in WordPress?

\n

Publishing via the Send to WordPress extension may seem counterintuitive at first. Why not just compose directly within WordPress? One advantage is that when Google Drive is online, you can work with others to collaborate on a post as a group and then have a convenient way to send your work over to WordPress.

\n

The main benefit of this extension is that it allows you to keep working, even when you cannot access your site. Google Drive can be enabled for working offline, which allows you to organize folders, view your files, and edit Google documents without an internet connection.

\n

If you’re on a long plane ride and the wi-fi isn’t working or you’re stuck somewhere without internet, you can continue to write posts, add images, links and formatting in Google Drive. The Send to WordPress extension lets you automatically send all of that work over to your WordPress site as soon as you have a connection again.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Aug 2014 21:13: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: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:55:"WPTavern: How to Easily Add Icons to Menus in WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28664";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:154:"http://wptavern.com/how-to-easily-add-icons-to-menus-in-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=how-to-easily-add-icons-to-menus-in-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4899:"

Have you ever found yourself wanting to spice up the navigation menus on your site by adding icons? Typically, you’d have to edit the CSS of a theme but thanks to a new plugin, you don’t have to. Menu Icons is a plugin for WordPress that makes it easy to add icons to menus without having to touch any code.

\n

Built With Simplicity In Mind

\n

Dzikri Aziz handles most of the development work and is responsible for the initial idea of the plugin. Aziz helped create the plugin because most of the other solutions involve editing CSS classes or other complicated measures. “Most of the existing plugins force you to assign the icons blindly, and make you enter some classes and/or markup into the menu items. This didn’t seem very user-friendly to me. Also, I wanted to get better at developing with the media library,” Aziz told the Tavern.

\n

Once Menu Icons is activated, browse to Appearance > Menus. You should notice a new meta box on the left hand side labeled Menu Icons Settings. From here, you can select which icon sets are available to choose from as well as configure the default placement settings of each icon.

\nThe new meta box on the left with the link to select an icon on the rightThe new meta box on the left with the link to select an icon on the right\n

As you can see, four of the most popular icon fonts are available out of the box. The image option enables you to use the WordPress media library to upload an image or use one that’s already available. Although it’s not listed, Menu Icons supports Fontello Font packs thanks to Joshua Rountree. The Menu Icons FAQ contains information on how to install and select Fontello Icons.

\n

After clicking on the Select Icon link within the menu item, a modal window is displayed with icons to choose from.

\nPlenty Of Icons To Choose FromPlenty Of Icons To Choose From\n

When an icon is selected, the right side of the model presents you with some options to alter its display. The global settings are used by default.

\nSettings To Alter The Display Of IconsSettings To Alter The Display Of Icons\n

One of my favorite features is the ability to use icons from different packs. If a pack doesn’t have the icon you’re looking for, chances are, one of the other three does. It only took five minutes to find the right icons for my menus. Without modifying the default settings, this is what my menus looked like on the front end of the site.

\nThe End ResultThe End Result\n

The icons become part of the link, just like the text, and they blend in seamlessly. Can you tell which packs these icons belong to? If the icons don’t look like they’re aligned correctly, you’ll need to override the styles in the theme’s CSS file or use the Simple Custom CSS plugin to apply the correct style attributes. In most cases however, the icons should look fine in your theme.

\n

Simple Yet Effective

\n

Menu Icons is a great, effective plugin. I wish it existed five years ago when I really could have used it. It’s the easiest way I’ve come across to add icons to navigation menus in WordPress without having to edit CSS. If you know something easier, let us know in the comments. Also, how many of you plan on using this for client 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:"Tue, 19 Aug 2014 19:57:28 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:52:"Matt: Specialization is for Insects, and Developers?";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=44020";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:66:"http://ma.tt/2014/08/specialization-is-for-insects-and-developers/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2269:"

A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.

\n

That’s from Robert Heinlein’s character Lazarus Long.

\n

Peter Merel coined this version for developers:

\n

A programmer should be able to fix a bug, market an application, maintain a legacy, lead a team, design an architecture, hack a kernel, schedule a project, craft a class, route a network, give a reference, take orders, give orders, use configuration management, prototype, apply patterns, innovate, write documentation, support users, create a cool web-site, email efficiently, resign smoothly. Specialization is for recruiters.

\n

When I read that it definitely reminds me of some of my favorite colleagues, and something I aspire to myself even though I’m very heavily balanced toward the “lead a team” part right now in my life.

\n

Even as technology is becoming more accessible, modern web development grows more complex. Some might look at that is discouraging, I prefer to think that no matter how far along you get you can still have a lifetime of learning ahead of you.

\n

For interesting debate on the above, check out the c2 wiki Specialization for Insects discussion (last edited March, 2012) and also the page that says “If specialization is for insects then I’d very much like to be a humble insect.” (Last edited November, 2005. I love digging around older parts of the internet.)

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Aug 2014 16:02:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:28:"Joseph: How VaultPress Works";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://josephscott.org/?p=10862";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://josephscott.org/archives/2014/08/how-vaultpress-works/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:519:"

Mark has posted a few details on how VaultPress.com backups work. This should be especially helpful for those that have asked me about this in the past.

\n

If you don’t already have a VaultPress.com account you can get a free trial by first connecting your WordPress site to Jetpack.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 19 Aug 2014 14:24:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Joseph Scott";s: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:109:"WPTavern: Dependency Minification for WordPress: Automatically Concatenate and Minify Scripts and Stylesheets";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=27649";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:260:"http://wptavern.com/dependency-minification-for-wordpress-automatically-concatenate-and-minify-scripts-and-stylesheets?utm_source=rss&utm_medium=rss&utm_campaign=dependency-minification-for-wordpress-automatically-concatenate-and-minify-scripts-and-stylesheets";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5804:"photo credit: PetitPlat - Stephanie Kilgast - ccphoto credit: PetitPlat – Stephanie Kilgast – cc\n

If you’re obsessed with improving your site’s loading time then you’ve probably already looked into caching and server optimizations. Frontend optimization is often further down on the list but can have a tremendous effect on performance. One of the most common frontend optimization techniques is to concatenate and minify your resources, which reduces the number of requests as well as the file size of the resources requested.

\n

The process of “minifying” eliminates wasted space in the scripts and stylesheets, which makes them much smaller and able to load faster. Combining (“concatenating”) multiple scripts reduces the number of requests, allowing you to download more assets in parallel to speed things up.

\n

Dependency Minification is a plugin that will automatically concatenate and minify scripts and stylesheets for you. It’s a reincarnation and rewrite of the X-Team’s popular Optimize Scripts plugin, which is now officially retired.

\n

Dependency Minification grabs scripts and stylesheets that have been added via wp_enqueue_script and wp_enqueue_style and automatically concatenates and minifies them into logical groups using WP-Cron. When you first install it and visit the settings page, you’ll see a notice:

\n

There are no minified dependencies yet. Try browsing the site.

\n

After you browse the frontend (which activates WP-Cron) and then visit the settings page, you’ll see that the process of minifying and concatenating resources has begun:

\n

dependency-minification-settings

\n

How do you know it’s working? In addition to the information on the plugin’s settings page, you can view the source of your site. Minified and concatenated dependencies will appear in your code with /_minify/ in the path similar to this:

\n
<script type=\'text/javascript\' src=\'/_minify/wp_favico_js,wp_favicon_js,previewloader,pinterestRSSjs,yumprint-recipe-post,flexslider.df2e3e1be0c951f4cf3ea0932200f96c.314e77c0b7be97ba8913570dcc5ada67.js\'></script>
\n

Mouseover any group of dependencies on the settings page and you’ll see three options:

\n

script-options

\n
    \n
  • Expire – Expire this item to gracefully regenerate
    • \n
  • Purge – Purge item from cache (deletes immediately, not often recommended)
    • \n
  • View Minified – View minified dependencies in a new window
    • \n
\n

The minified sources are stored in the wp_options table, which means that no special filesystem access is required. The plugin also includes a filter to exclude dependencies that you don’t want to be minified. A few other important things to know about the plugin’s features and how they can be customized:

\n
    \n
  • Endpoint for minified requests is at /_minified, which can be configured.
    • \n
  • Dependencies hosted on other domains are excluded by default, but this behavior can be changed by filtering the default_exclude_remote_dependencies option via the dependency_minification_options filter, or on a case-by-case basis via the filter previously mentioned.
    • \n
  • Stale minified scripts and stylesheets remain until replaced by refreshed ones; this ensures that full-page caches which reference stale minified sources won’t result in any 404s.
    • \n
  • Transforms relatives paths in stylesheets (e.g. background-images) to absolute ones, so that they don’t 404.
    • \n
\n

WordPress super admins will be glad to know that Dependency Minification is also multisite-compatible. If you want to use it on a multisite network, the plugin’s instructions advise you to install and activate scribu‘s Proper Network Activation plugin before activating it network-wide.

\n

The Dependency Minification plugin is supported by a large group of experienced developers who continue to improve it. They have built a decent amount of flexibility into the plugin with several filters that allow you to control and tweak its default behavior. If you don’t need to modify how it works, the plugin is pretty much plug-and-play. It provides a quick and simple way to concatenate and minify resources on your site, without a ton of options to configure.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Aug 2014 23:10:55 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:61:"WPTavern: WPChat Relaunches as a Forum Dedicated to WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28616";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:166:"http://wptavern.com/wpchat-relaunches-as-a-forum-dedicated-to-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=wpchat-relaunches-as-a-forum-dedicated-to-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4934:"

A few years ago, Leland Fiegel created a site called WPChat. The site contained an iFrame with an embedded IRC client pointed to Freenode. It provided easy access to IRC where at anytime during the week, users could chat about WordPress. Here’s what the old site looked like.

\nWhat The Old WPChat Used To Look LikeWhat The Old WPChat Used To Look Like\n

After being dormant for the past year or two, Fiegel has turned the site into a dedicated forum devoted to WordPress topics.

\nWPChat Running DiscourseWPChat Running Discourse\n

The site is powered by Discourse, an open source, GPL licensed, discussion platform created by Jeff Atwood. In a post published on his personal site, Fiegel explains why he chose Discourse over other forum software such as bbPress, or phpBB.

\n

Discourse just has a more modern feel to it. The instant flow of discussions, the notification features, it just feels much more like a chatroom, rather than a more traditional piece of forum software.

\n

I felt it fit much more inline with the “brand” of WPChat, and just thought people would enjoy using it better.

\n

Over the weekend, I had the privilege of being one of the first members to the forum. It loads quick and is intuitive to use. The site works great on mobile devices. I’m able to administer, respond to, and create threads easily from my phone.

\n

Discourse Is a Breath Of Fresh Air

\n

Discourse is a fresh take on using forums for community discussion. One of the unique attributes it has is a trust system. As members spend more time replying to and creating more threads, their trust level increases. Higher trust levels provide more capabilities to the user, allowing them to take on a larger role of moderating the forum. I find this to be an interesting approach and wonder how well it does on large, established forums.

\n

Discourse 1.0 has yet to materialize but according to the blog, it’s right around the corner. Since it’s only a year old, there’s not much in the way of a third-party ecosystem. If you plan to install Discourse on your own server, be aware of the minimum requirements. As Fiegel mentions in his post, it’s not as easy to install as WordPress.

\n

A Forum Outside Of WordPress.org

\n

While there is a Google+ group devoted to WordPress and other watering holes, the closest one that feels like a forum to me is the Advanced WordPress user group on Facebook. However, Facebook groups in general lack significant features that make them useful such as threads and an easy way to locate previous discussions. You’re also tied to Facebook in terms of what you can do with the data.

\n

Ever since the WP Tavern forum disappeared, I’ve been looking for somewhere on the web to hang out and chat about WordPress. Not everything is deserving of a blog post but may be worthy of a discussion. WPChat is attempting to fill a void I think is missing in the WordPress community, a well-managed, diversified forum, devoted to WordPress, outside of what is already available on WordPress.org.

\n

Membership to WPChat is free and at the very least, gives you an opportunity to try out Discourse from a user perspective. You’ll be able to find me on WPChat via the username Jeffro.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Aug 2014 23:02:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:11;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:57:"WPTavern: The Problem With Image Attachments In WordPress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28598";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:158:"http://wptavern.com/the-problem-with-image-attachments-in-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=the-problem-with-image-attachments-in-wordpress";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4783:"

Something I’ve wanted to see in WordPress for a long time is the ability to determine which posts an image is being used on. WordPress 4.0 is expected to ship by the end of August and contains two subtle changes to image data in the media library. You’ll be able to view the author who uploaded the image and the post parent ID it’s attached to.

\nUploaded By and Uploaded To InformatiomUploaded By and Uploaded To Information\n

I find this information to be useful, especially for multi-author websites. Although you can view the parent post ID the image is attached to, you can’t locate each post the image is used on. It’s important to note the difference between an image attached to a post and using an image already available in the media library.

\n

Why Knowing Where An Image Is Used Comes In Handy

\n

Let’s say I use a featured image for a post and it’s the featured image for several other posts. If I want to change the featured image in one post and have it change in every other post, I can’t. I also can’t change the image for specific posts automatically, it’s either all or nothing. I can’t determine which posts are using the image because WordPress only sees it being used on the parent post. This is due to the attachment relationship.

\n

In other words, the first post the image is attached to is the only information WordPress has on where it’s being used. I could browse to every post and manually change it but my memory isn’t that good and it’s a tedious process.

\n

The History Behind The Dilemma

\n

In trying to figure out why this is, Justin Tadlock pointed out two Trac tickets, 10657 and 14513. Both contain lengthy, technical discussions, on how to add support for many-to-many relationships between posts and attachments in WordPress. Within the discussions, the Posts 2 Posts plugin is commonly referred to as a top-notch plugin that offers this functionality.

\n

Before the Community Summit in October of 2012, Andrew Nacin and a host of other WordPress developers came together to discuss the subject in detail. The ideas brought forth from that conversation are available on the Make.WordPress.com blog and is a potential roadmap for taxonomy meta and post relationships in WordPress.

\n

It’s Possible But Not Worth The Hassle

\n

WordPress automatically renames files if it detects the same name being used in the media library. This means you can’t upload a new image with the same file name to replace it. An alternative method is to use FTP to locate the original file and overwrite it, keeping the same name. The image will change in all posts using it, regardless of the attachment details. You’ll also need to overwrite any images that were resized automatically by WordPress or else they’ll show up instead of the new ones.

\n

After performing all sorts of tests in my local environment for trying to change one image across multiple posts, I’ve decided it’s too much of a hassle. Not being able to manage these relationships in WordPress doesn’t make sense. Ideally, I’d like to be able to determine which posts are using an image and replace that image across all of those posts at the same time. I also wouldn’t mind the flexibility to change an image for certain posts while leaving the others alone.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Aug 2014 22:15: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:85:"WPTavern: _s_backbone: A WordPress Starter Theme Based on Underscores and Backbone.js";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28545";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:212:"http://wptavern.com/_s_backbone-a-wordpress-starter-theme-based-on-underscores-and-backbone-js?utm_source=rss&utm_medium=rss&utm_campaign=_s_backbone-a-wordpress-starter-theme-based-on-underscores-and-backbone-js";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7139:"

The Underscores WordPress starter theme has seen a flurry of activity in recent days, adding support for Sass and automated testing with Travis CI. The theme has been forked more than 1300 times on GitHub with many interesting variations created to support various theme features and frameworks.

\n

One fork in particular is getting WordPress theme developers excited about the possibility of bringing in new Javascript-powered features. _s_backbone is a new theme based off of Underscores that incorporates the WordPress REST API Backbone.js client.

\n

_s_backbone

\n

Taylor Lovett, Director of Web Engineering at @10up, created the theme as a proof of concept but also hopes that it will become a useful tool for theme developers who want to get started using the WP REST API. The API is slated for inclusion in WordPress 4.1.

\n

Advantages of Using Backbone for Infinite Scroll

\n

_s_backbone_theme

\n

So how is _s_backbone different from vanilla Underscores? The major difference here is that the loops have infinite scroll built in using a “more” button, a feature powered by the Backbone client which grabs posts on the fly without reloading the page. This provides several advantages. “On the web today, people expect reactive, dynamic web applications. I think everyone can agree the web is shifting to a more JavaScript reliant place,” Lovett told the Tavern. “Powering your loops using JSON REST API’s Backbone client is the easiest way for you to add and customize infinite scroll to your website.”

\n

Adding infinite scroll to a theme using other methods can be a frustrating, complicated experience. “There are a few advantages to building infinite scroll with the JSON REST API as opposed to something else,” Lovett said. “The JSON REST API will be merged into WordPress so your code will always be backwards compatible. With the JSON REST API and Backbone client, you don’t have to build your own endpoints which is time consuming. Also, the JSON REST API is, well, RESTful making it extremely easy to use.”

\n

I asked Lovett how _s_backbone’s implementation of infinite scrolling differs from Jetpack’s module. Is this feature something that functions better as part of a theme vs. a plugin?

\n

“I’ve worked extensively with Jetpack’s Infinite Scroll module. In fact, _s_backbone takes some code from it,” he said. “I think valid arguments can be presented for including infinite scroll in either a plugin or a theme. However, I think with the advent of the JSON REST API and Backbone client, adding infinite scroll to the theme makes more sense.”

\n

Although the theme’s main attraction right now is a new way to power infinite scrolling, Lovett hopes that _s_backbone can provide a starting place for developers to create their own Backbone-powered features.

\n

_s_backbone is a starter theme, not a parent theme. Decisions are left to the theme developer. If the developer feels like it, they can rip out infinite scroll completely or put it in a plugin. The goal is to provide the theme developer with a good base with which to start and let them build from there.

\n

In the future, Lovett plans to add post format support to the theme, as it’s currently missing that feature. “I’m hoping to get some feedback on the starter theme to best assess what would be most useful to developers,” he said.

\n

The WP REST API Opens Up New Opportunities for Theme and Plugin Developers

\n

Lovett will be speaking this weekend at WordCamp Boston on the WP JSON REST API where he hopes to use the _s_backbone theme as an example. His largest contribution to the WP REST API project has been the creation of the Backbone.js client. He also contributes on the PHP side, assisting with post meta, comments, and revision endpoints.

\n

“I’m very excited about the implications of the JSON REST API in the backend,” Taylor commented on the future of the project. “I believe the JSON REST API will be incredibly useful internally, especially cross-site (in multisite). I’ve written many endpoints to retrieve different custom post types for backend features that could be dramatically simplified with the JSON REST API. Also, I think it will simplify the code powering the media library.”

\n

Lovett hopes to introduce developers to all the possibilities of using the API while at WordCamp Boston. “First and foremost, I want to show people why the API is useful and how you can use it,” he said. “I want to inspire plugin and theme developers to build amazing things with the API. I believe a RESTful API within WordPress opens up a lot of doors. I’d also like to show people how you can grab data from other websites that use the API instead of parsing feeds.”

\n

If you’re familiar with Underscores, then Lovett’s new _s_backbone theme is a nice starting point for learning more about using the API in a theme. Feel free to leave feedback on the project regarding additional features you’d like to see powered by Backbone. If you’re interested in contributing to the WP API project, the Backbone.js client, or elsewhere, Lovett encourages you to get involved, as the team is always looking for more help.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Aug 2014 17:57:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:29:"Matt: Commercial Whaling Ship";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=44017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://ma.tt/2014/08/commercial-whalingship/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:347:"

The Time I Spent On A Commercial Whaling Ship Totally Changed My Perspective On The World — I know the title sounds baity but this is the best writing I’ve read online in a while, almost like it’s from a different time.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Aug 2014 15:39: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:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:46:"Akismet: Akismet 3.0.2 for WordPress Available";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"http://blog.akismet.com/?p=1640";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://blog.akismet.com/2014/08/18/akismet-3-0-2-for-wordpress-available/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:931:"

Version 3.0.2 of the Akismet plugin for WordPress is now available.

\n

In version 3.0.2, we’ve improved performance and fixed a bug that could have negatively affected Akismet’s ability to determine whether a comment is spam.

\n

To upgrade, visit the Updates page of your WordPress dashboard and follow the instructions. If you need to download the plugin zip file directly, links to all versions are available in the WordPress plugins 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:"Mon, 18 Aug 2014 01:45: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:17:"Christopher Finke";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:31:"Matt: Internet’s Original Sin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=44015";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://ma.tt/2014/08/internets-original-sin/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:282:"

Ethan Zuckerman writes for the Atlantic on The Internet’s Original Sin, advertising.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sun, 17 Aug 2014 14:30:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:16;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:27:"Matt: Humans Need Not Apply";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=44009";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://ma.tt/2014/08/humans-need-not-apply/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:42:"

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 16 Aug 2014 17:42: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:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:66:"WPTavern: Time To Move On From The “Is WordPress A CMS” Debate";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28493";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:164:"http://wptavern.com/time-to-move-on-from-the-is-wordpress-a-cms-debate?utm_source=rss&utm_medium=rss&utm_campaign=time-to-move-on-from-the-is-wordpress-a-cms-debate";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3023:"WordPress Is A CMS Featured Imagephoto credit: Cesar Maia – cc\n

In the realm of WordPress, there is a particular debate that has been going on for years on whether WordPress is a CMS or not. CMSCritic has a great article by Kaya Ismail, that explains why WordPress is a CMS (Whether You Like it or Not). It’s one of the most refreshing perspectives I’ve read on the subject. The definition of a Content Management System is a web application designed to make it easy for non-technical users to add, edit and manage a website. WordPress fits that definition rather well and in many respects, excels at it. The problem as Ismail explains, is that the acronym has become muddied over the years.

\n

The issue arises when the stripped down, true meaning of “CMS” is blown up with unnecessary jargon. In reality, those definitions hold very little weight, other than when they describe added marketing or administrative extras. The fact of the matter is, WordPress fits the definition of a CMS perfectly.

\n

WordPress has grown up to be far more than just a blogging tool. It’s used to power apps, run large content heavy websites, and e-commerce. The reputation that it’s just a blogging tool and not a CMS is false.

\n

If you’re curious on how to use WordPress as a CMS, read this guide published by Ozh Richards that contains a simple four step process. It’s a process nearly all WordPress users go through everyday.

\n

It isn’t particularly amazing in any niche other than blogging, and it sacrifices being a powerhouse when it comes to things like digital asset management for the sake of simplicity. Yet at the same time, WordPress is a content management system, and a good one at that.

\n

So, maybe it’s time everybody got over it.

\n

Ismail sums it up rather well. I think it’s time to kick this debate to the curb.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Aug 2014 20:38:00 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:79:"WPTavern: Under the Hood of Semplice: A New Portfolio System Based on 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:28:"http://wptavern.com/?p=27810";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:200:"http://wptavern.com/under-the-hood-of-semplice-a-new-portfolio-system-based-on-wordpress?utm_source=rss&utm_medium=rss&utm_campaign=under-the-hood-of-semplice-a-new-portfolio-system-based-on-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:7120:"

Semplice has soft-launched its new WordPress-powered portfolio system. The commercial project popped up on our radar after debuting its extraordinary implementation of the WordPress content editor. Founded by German designers Michael Schmidt and Tobias van Schneider, Semplice is breaking onto the scene with high impact designs and its own radically simplified content editor.

\n

semplice

\n

“Semplice is and was built based on our own needs to create beautiful case studies and branded pages, mainly for designer and artist portfolios,” Van Schneider told the Tavern. “Our goal is to create a completely new high quality experience on top of WordPress, something you haven’t seen before,” he said. So far they appear to be achieving exactly that. Example portfolios built with Semplice are nothing less than stunning.

\n

semplice_adam

\n

A Unique Content Editor

\n

Semplice incorporates its own visual content editor which allows users to create unique branded pages or extensive case studies for their projects, without a single line of code. “We aim to create a flexible system, not a template,” Van Schneider said. “With Semplice you start mostly with a white canvas, not a template or theme where you just fill in the blanks.” Every project is 100% responsive and the content editor is completely tailored to creating a portfolio.

\n

semplice-content-editor

\n

So what’s under the hood?

\n

As beautiful as the front-end results are, we were most curious about what’s under the hood and assumed it was based on custom post types. On the contrary, the Semplice crew has taken a different route to create this unique editing experience.

\n

“For the basic theme options we use Advanced Custom Fields from Elliot Condon,” Van Schneider said. “The Content Editor itself is a combination of a Javascript frontend that uses the WordPress Ajax functions to communicate with the PHP backend.

\n

“As we worked on different Semplice iterations we quickly learned that we need something more than just Custom Post Types, especially since the performance suffered a lot in the beginning,” he explained. The Semplice content editor is optional and can be activated when creating new pages in WordPress. It includes a live preview as you edit on the frontend, as you can see in the video example below.

\n

\n

“What you build is exactly what you get,” he said. “This allows you to create very flexible editorial layouts for designers or artists who want to present their work in the best light possible.”

\n

Semplice also allows users the ability to brand every page with a unique visual look. Instead of having pages follow a set template, elements such as background color, navigation, and typography can be customized for each.

\n

The regular WordPress admin is still in play, for example, when a user adds new work. It starts off in the backend with branding and image options.

\n

add-new-work

\n

One unique feature of Semplice is the ability to easily add a new custom fontset to WordPress using the web service of your choice. This is especially important for designers who require unique fonts for presenting their work.

\n

custom-fontset

\n

Semplice is geared toward both experienced WordPress users, as well as those who are totally new to the platform. “Yes, we do aim for people who are familiar with WordPress since they will be able to take Semplice even further than what we offer,” Van Schneider said. “But with our Semplice Content Editor we even aim at people who don’t have that much experience with WordPress itself since you don’t really need it.”

\n

Licensing, Pricing, and Support

\n

Introductory Semplice pricing for a single domain is $69 and $299 for an agency. Semplice will be launching without offering customer support and is unusual in that it doesn’t offer any refunds. Support is limited to the first seven days after purchase. The team will assist with anything related to the default Semplice features and is currently working on establishing a pool of video tutorials for documentation.

\n

While the Semplice team cannot yet offer full product support, they are committed to delivering critical free updates to existing customers. The software is licensed under the GPL. Although Semplice hasn’t launched yet, early adopters can purchase the software now for a reduced price.

\n

While the Semplice content editor appeals to new WordPress users, they will still need to overcome the hurdle of installing and setting up a WordPress site on their own domains. Even with 1-click installers, the process can be more difficult than you might imagine for designers and artists with no WordPress experience. Without a fully hosted Semplice platform, the software is going to have to appeal to seasoned WordPress users who appreciate its unique take on building a fullscreen branded portfolio. Do you think Semplice can win out over other theme and plugin-based options?

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Aug 2014 20:05:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:64:"WPTavern: A Survival Guide To WordCamps For First Time 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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28486";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://wptavern.com/a-survival-guide-to-wordcamps-for-first-time-attendees?utm_source=rss&utm_medium=rss&utm_campaign=a-survival-guide-to-wordcamps-for-first-time-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2348:"Survival Guide Featured Imagephoto credit: Steve Rhodes – cc\n

WordCamps are excellent opportunities to learn WordPress and have of face-to-face interaction with a lot of different people. They can also be exhausting and possibly stressful for first timers. Carrie Dils has an awesome WordCamp Survival Guide filled with tips and information on how to get the most out of these events.

\n

Tip number five (don’t sit by yourself at lunch) routinely happens to me at WordCamps.

\n

When the last morning session breaks, there will be a mad dash to the lunch line (did someone say “food?!”). You’ll grab a sack lunch lovingly provided by some volunteer and then you’ll stand there, possibly awkward and not sure where to go. It’s lunch on the first day at a new school all over again.

\n

Try this: Head over to any table with open spots and simply ask to sit down. Unless you just really need that lunch break for personal time, don’t miss an opportunity to meet folks over lunch!

\n

I struggle with introducing myself to people I’ve never met before. At WordCamps, I’m generally extroverted but I’ve noticed at larger camps, I become introverted. It’s a personality thing I’ve been fighting with for the past few years with mild success. I keep telling myself that I’m going to introduce myself to everyone I see at a WordCamp but it never works out that way. I end up finding a group of people I’m familiar with and stick with them. Does anyone else struggle with introversion at WordCamps?

\n

The survival guide is filled with great information but I think the most important point is the last and that’s to have fun.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Aug 2014 19:00:40 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:92:"WPTavern: WPWeekly Episode 158 – Interview With Pippin Willamson Of Easy Digital Downloads";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:44:"http://wptavern.com?p=28482&preview_id=28482";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:220:"http://wptavern.com/wpweekly-episode-158-interview-with-pippin-willamson-of-easy-digital-downloads?utm_source=rss&utm_medium=rss&utm_campaign=wpweekly-episode-158-interview-with-pippin-willamson-of-easy-digital-downloads";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3212:"

Pippin Williamson of Easy Digital Downloads joined Marcus Couch and I to discuss a variety of topics. Williamson tells his story of how he got involved with WordPress. Later in the show, we discuss what it’s like to be a remote worker. Williamson tells us which tools he uses for project management and how important it is for him to have a disciplined routine.

\n

As a volunteer moderator of the WordPress.org plugin directory, he’s seen his fair share of plugin submissions. He tells us which types of plugins are automatically rejected and what it’s like being a gatekeeper for the plugin directory.

\n

Stories Discussed:

\n

WP Site Care Acquires Audit WP
\nNew WordPress Plugin Spell Checks Post Titles Before Publishing

\n

Plugins Picked By Marcus:

\n

HTML5 Slideshow Presentations – With this plugin, you’ll be able to create a presentation in no time using WordPress’ familiar built-in toolset and the best part is, you won’t need to upload to slideshare when you’re done! You host your own presentations allowing you to share or present them at anytime.

\n

Sidebar Automizer – This little plugin will remove the last widget or widgets from the sidebar if the content area height is smaller than the height of the sidebar area.

\n

Update from Bottom – This plug shows two extra buttons (Scroll to top and Publish/Update) in the bottom of the screen when a user scrolls near the bottom of the site. Suitable for posts and pages with a lot of meta boxes or when edit.php just tends to get very long.

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, August 20th 9:30 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #158:
\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Aug 2014 18:07:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:31:"Matt: SmartThings & Samsung";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=44005";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://ma.tt/2014/08/smartthings-samsung/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1419:"

SmartThings announced (on their WP-powered blog) that they’re joining forces with Samsung to continue working on their mission of becoming an operating system for your home. I’m both an investor and a fan of the company, which I even let take over my home in SF earlier this year for CNN. As a tinkerer most of what I do with SmartThings so far is relatively basic, I feel like it’s still the very early days of the platform and what’s going to come down the line. Samsung makes so much technology (and appliances, and TVs, and…) I can’t wait to see how they open it up and connect. I also wanted to take this opportunity to congratulate other Audrey companies Divide which joined Google and Creative Market which joined Autodesk earlier in 2014. I wasn’t as good about blogging before and didn’t get a chance to publicly congratulate those 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Aug 2014 13:49: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:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:82:"WPTavern: Automatically Tweet an Announcement for WordPress Plugin Version Updates";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28459";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://wptavern.com/automatically-tweet-an-announcement-for-wordpress-plugin-version-updates?utm_source=rss&utm_medium=rss&utm_campaign=automatically-tweet-an-announcement-for-wordpress-plugin-version-updates";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2517:"photo credit: MACSwriter - ccphoto credit: MACSwriter – cc\n

Here’s a quick tip for WordPress.org plugin authors and users, courtesy of Paul de Wouters: With the help of a task automation service like Zapier or IFTTT, you can automatically send out a tweet every time an updated version of your plugin is available. Simply set up an RSS -> Twitter action, like this one with Zapier:

\n

rss-tweet

\n

Users of IFTTT can do the same by creating an RSS to Twitter recipe. You’ll want to use the development log feed on the developers tab of the plugin page. Connecting RSS to Twitter via a service will automate the little tasks involved in promoting your plugin and keeping users up-to-date.

\n

Get Notified When a Plugin is Updated

\n

rss-to-email

\n

Plugin users can also harness the same feed URL to send themselves updates via email. Let’s say you’ve got a few specific plugins that you are watching intently for an update. Perhaps you’ve notified the plugin author of a bug and are waiting for a fix or a new feature that’s in development. Instead of checking your site or the plugin’s page on WordPress.org for updates, you can set up an RSS to Email automated task to pull from the plugin’s development log feed and shoot a notice to your inbox.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Aug 2014 05:14:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:30:"Dev Blog: WordPress 4.0 Beta 4";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"http://wordpress.org/news/?p=3280";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/news/2014/08/wordpress-4-0-beta-4/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1990:"

The fourth and likely final beta for WordPress 4.0 is now available. We’ve made more than 250 changes in the past month, including:

\n
    \n
  • Further improvements to the editor scrolling experience, especially when it comes to the second column of boxes.
    • \n
  • Better handling of small screens in the media library modals.
    • \n
  • A separate bulk selection mode for the media library grid view.
    • \n
  • Improvements to the installation language selector.
    • \n
  • Visual tweaks to plugin details and customizer panels.
    • \n
\n

We need your help. We’re still aiming for a release this month, which means the next week will be critical for identifying and squashing bugs. If you’re just joining us, please see the Beta 1 announcement post for what to look out for.

\n

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums, where friendly moderators are standing by. Plugin developers, if you haven’t tested WordPress 4.0 yet, now is the time — and be sure to update the “tested up to” version for your plugins so they’re listed as compatible with 4.0.

\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.0, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

\n

We are working hard
\nTo finish up 4.0
\nWill you help us too?

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 15 Aug 2014 05:06:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Helen Hou-Sandi";s: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:72:"WPTavern: Clear Tranquil: A Free Minimalist WordPress Theme for Bloggers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28368";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:186:"http://wptavern.com/clear-tranquil-a-free-minimalist-wordpress-theme-for-bloggers?utm_source=rss&utm_medium=rss&utm_campaign=clear-tranquil-a-free-minimalist-wordpress-theme-for-bloggers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2956:"

Clear Tranquil is one of the cleanest, most elegant blogging themes to hit WordPress.org in recent days. The theme was created by Woo Themes designer James Koster as a child theme for his responsive Highwind parent theme.

\n

Clear Tranquil lives up to its name, inspiring a light, peaceful reading experience that is clutter-free. The design puts your content in focus.

\n

clear-tranquil

\n

Koster gives meticulous attention to typography and highlights the first character of each post with elegant block letter styles. The theme includes a sticky, understated top navigation menu (optional), and zero widget areas. That’s right, Clear Tranquil is a completely widget-free zone.

\n

single-post

\n

The theme includes a handful of customization options built into WordPress’ native customizer. You can personalize it with a custom header, background, and your own color selections for text, links, and backgrounds.

\n

clear-tranquil-customizer

\n

Clear Tranquil includes no additional features, because everything has been intentionally stripped back to keep things simple. Koster hasn’t set up a live demo of the theme. Ordinarily, the WordPress.org demo gives an unrealistic representation of what a theme will look like. However, in this case, it’s fairly accurate.

\n

One of the things that I love about the WordPress theme installation process is that it will automatically install the parent theme for a child theme, if you don’t already have it installed. In this scenario, if you install Clear Tranquil without Highwind already in place, it will be automatically downloaded for you.

\n

If your blog has gotten bloated with widgets and is in need of a minimalist makeover, Clear Tranquil might be just the ticket. Download it for free from the WordPress Themes 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:"Thu, 14 Aug 2014 23:04: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: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:71:"WPTavern: Foster Me: A WordPress Plugin to Help Shelter Animals in Need";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28267";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:184:"http://wptavern.com/foster-me-a-wordpress-plugin-to-help-shelter-animals-in-need?utm_source=rss&utm_medium=rss&utm_campaign=foster-me-a-wordpress-plugin-to-help-shelter-animals-in-need";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5833:"photo credit: puck90 - ccphoto credit: puck90 – cc\n

Everybody knows that animals need homes. There are far more pets available for adoption than there are people lining up to adopt them. Call your local animal shelter and they’ll probably tell you that they’re at or over capacity. That’s where foster homes can help to provide quality care for animals in the interim, until they find their forever homes.

\n

Foster Me is a new WordPress plugin designed to help rescues and shelters make available pets more visible and easier to search. It was created by Stephanie Chow, a front-end developer and animal advocate located in Asheville, NC. Her Lending a Paw site features open source plugins and graphics for animal rescue organizations.

\n

Foster Me makes it easy to list and manage animals in WordPress where they can be searched with advanced pet-specific filters, such as age, type, gender, temperament, special needs, etc.

\n

foster-me

\n

When a visitor clicks on an available pet, the listing launches in a modal window. Individual pet listings display a full description, a slider with multiple photographs, and any applicable pet categories.

\n

pet-listing

\n

The plugin also makes it easy to list fostering information and to post your foster application. Chow has made every effort to make Foster Me a user-friendly plugin for rescues and shelters that may not have a WordPress expert on staff. The settings page allows you to easily customize the color and appearance of the header, pet options, pet grid and modal window.

\n

foster-me-settings

\n

Foster Me also includes an image widget for showcasing foster pets as well as a Recently Added widget to display new additions.

\n

foster-me-widget

\n

The plugin adds a whole suite of pet listing features that are general enough to be used in any kind of shelter or rescue website:

\n
    \n
  • Filterable – filter by Type, Age, Size, Gender, Temperament, and Special Needs
    • \n
  • Searchable – list is narrowed with every letter you type into search bar
    • \n
  • Click On Any Pet – to view more information and photos
    • \n
  • List Your Fostering Info – show how it works what to expect when you foster
    • \n
  • Colors – are completely customizable to match your brand
    • \n
  • Image Widget – place in sidebar to display a linkable, rotating image of foster pets
    • \n
  • Recently Added Widget – place in sidebar to display your most recently added fosters
    • \n
\n

Check out a live demo of Foster Me to test out the pet searching and filtering capabilities.

\n

Chow’s first plugin, Petfinder: Search and Rescue, is very similar to her latest release, except it requires the animals to be listed on Petfinder. If you already have your shelter or rescue pets listed on Petfinder, then this alternative will be a better option for automatically pulling in your existing listings.

\n

Saving Animals with WordPress

\n

The Foster Me plugin is an awesome open source tool that any shelter or rescue can use for free in combination with an existing WordPress site. When it comes to helping animals find their forever homes, open source software may not be the first thing that comes to mind, but Stephanie Chow is knocking it out of the park with her user-friendly tools designed to serve people who are rescuing creatures in need. Open source tools are more accessible to shelters and rescues that are spending every last dime to help animals find homes. If you have WordPress skills and are able to hook up a shelter with a website, then the Foster Me plugin will put you well on your 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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 14 Aug 2014 20:57:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:26;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"WPTavern: WebDevStudios Names Dre Armeda Vice President of Operations";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28328";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:182:"http://wptavern.com/webdevstudios-names-dre-armeda-vice-president-of-operations?utm_source=rss&utm_medium=rss&utm_campaign=webdevstudios-names-dre-armeda-vice-president-of-operations";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6086:"Dre Armeda and Brad Williams Join Forces Featured ImageDre Armeda and Brad Williams Join Forces\n

In the time Dre Armeda spent with Sucuri, he turned a two-person part-time hobby into a multi-million dollar, 30+ employee company. When Armeda left the company he helped found, he didn’t provide any hints as to where he was going.

\n

Three months after leaving Sucuri, Armeda has been named the Vice President of Operations for WebDevStudios. Brad Williams, co-owner of WebDevStudios and Armeda were kind enough to answer a few questions I had regarding the hire.

\n

Interview With Dre Armeda and Brad Williams

\n

What does the Vice President of Operations for WebDevStudios do?

\n

Brad Williams – The Vice President of Operations is a new role at WDS and our first Executive position outside of the original Partners. WDS has been growing quite a bit this year and we knew it was time to start expanding the leadership team. Dre brings a wealth of knowledge and a ton of experience to WDS, specifically around building a very successful distributed company. Some of the primary responsibilities for Dre include business development, improving operational efficiency, marketing, and even sales. Roles at WDS are always evolving, so I certainly expect Dre’s position to really evolve and be defined over the next few months.

\n

In some instances, businesses can ruin friendships. How did you two factor that into the equation before making the hire? Will the fact that you’re now co-workers have an effect on your personal relationship?

\nDre and Brad at WCSF 2013Image Courtesy Of Designsimply.com\n

Brad Williams – When we started discussing the possibility of Dre Armeda joining WDS, this was the first item we discussed. We knew from the start that we had to look at this from a business perspective and not because we are close friends. The last thing either of us would ever want would be to ruin the friendship that we have. Dre Armeda is a perfect fit for WDS, not only in the business sense, but also our company culture. We work hard, and play hard, and no one works and plays harder than Dre Armeda!

\n

Out of all the possible places to work in the WordPress ecosystem, why did you choose WebDevStudios?

\n

Dre Armeda – There is certainly a long relationship there with the leadership, the company, and the team. Brad Williams and I of course are the co-hosts of DradCast and have even presented on the topic of security together in years past at WordCamps. While part of Sucuri, we successfully worked with WebDevstudios in various capacities. The direction of the company, and the culture is very much inline with where I want to be, and where I want to go. Along with that connection, our long relationship, and the experience I can bring to the table, I think the decision was easy.

\n

Do you look at this as a long-term (2-3 year) position?

\n

Dre Armeda – One of the key points we talked about as we started looking into the possibility of working together was exactly that. We were looking for a long term situation and we’re excited about what the future brings!

\n

What lessons or experiences did you learn with Sucuri that you’ll be able to apply to improve WebDevStudios?

\n

Dre Armeda – The position will encompass a broad range of responsibilities and oversight ranging from organizational and business development, to talent development and strategy. I’ve had the great opportunity to work in these areas over the past five years as I helped build Sucuri into the successful organization it is today.

\n

I am very passionate about better serving our audience by expanding global reach and I’m certainly excited about increasing overall organizational efficiency through resourcing, process improvement, and business development. I really enjoy helping implement strategies to scale organizations efficiently and ultimately the lessons I have learned from my experience at Sucuri definitely align with the forward vision at WebDevStudios!

\n

What Was Once A Joke Has Become A Reality

\n

Those who know Williams and Armeda have joked that the two would some day work together but it was always a joke. Now, it’s real and it will be interesting to see how it works out. Based on the interview, Armeda is committed to the company for the long-term, something that’s not easily accomplished when hiring remote workers. Does this move surprise you or did you see the writing on the wall?

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 14 Aug 2014 14:59: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:27;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:58:"Matt: You Won’t Believe Who Wrote This Product Checklist";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=43998";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"http://ma.tt/2014/08/you-wont-believe-who-wrote-this-productchecklist/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1089:"
\n
    \n
  1. Understand what people need.
    2. \n
  2. Address the whole experience, from start to finish.
    3. \n
  3. Make it simple and intuitive.
    4. \n
  4. Build the service using agile and iterative practices.
    5. \n
  5. Structure budgets and contracts to support delivery.
    6. \n
  6. Assign one leader and hold that person accountable.
    7. \n
  7. Bring in experienced teams.
    8. \n
  8. Choose a modern technology stack.
    9. \n
  9. Deploy in a flexible hosting environment.
    10. \n
  10. Automate testing and deployments.
    11. \n
  11. Manage security and privacy through reusable processes.
    12. \n
  12. Use data to drive decisions.
    13. \n
  13. Default to open.
    14. \n
\n
\n

That sounds like a list anyone creating something online should follow. Would you guess it’s actually from the US government Digital Services Playbook? Great work by Steven VanRoekel and his team, which I had the pleasure of meeting last time I was in DC. Hat tip: Anil Dash.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 14 Aug 2014 14:10: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:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:28;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:86:"WPTavern: The Simple Criteria That Determines Which Jetpack Modules Are Auto-Activated";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28360";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:216:"http://wptavern.com/the-simple-criteria-that-determines-which-jetpack-modules-are-auto-activated?utm_source=rss&utm_medium=rss&utm_campaign=the-simple-criteria-that-determines-which-jetpack-modules-are-auto-activated";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3233:"Auto Activate Jetpack Modules Featured Imagephoto credit: 2create – cc\n

Since the release of Jetpack in 2011, there have been several articles highlighting the fact that it auto activates modules. George Stephanis, a member of the Jetpack development team, has consistently explained that “Jetpack only auto-activates modules that provide enhancements without affecting the front-end layout of the site.”

\n

Earlier today, Stephanis published a post on his blog that goes into detail on how the decision is made to auto-activate a module.

\n

We’ve spoken to many, many users who find a default feature set convenient, and resent having to make a bunch of ‘decision points’ if they had to manually activate each and every module. Good software should run well out of the box. So we’ve set up the defaults as we have. Yes, some people disagree and are vocal about not wanting anything to auto-activate. That’s okay. We try to design for the majority, with the best user experience we can provide.

\n

I appreciate the fact that new modules will not auto-activate if they impact the front end of my site. In this instance, the decisions being made for me are a convenience, not a hassle. If you disagree with the decisions being made, there are several filters you can use to customize the Jetpack experience, including one to deactivate all modules by default.

\n

add_filter( \'jetpack_get_default_modules\', \'__return_empty_array\' );

\n

I doubt his post will resonate with those who have a strong stance against auto-activating anything. As long as the development team stick to their current philosophy, I’m ok with 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, 14 Aug 2014 01:10: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:62:"WPTavern: Carl Hancock Shares Advice On Registering Trademarks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28347";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:168:"http://wptavern.com/carl-hancock-shares-advice-on-registering-trademarks?utm_source=rss&utm_medium=rss&utm_campaign=carl-hancock-shares-advice-on-registering-trademarks";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1553:"

Chris Lema published an interview with Carl Hancock of RocketGenius, where he shares his thoughts on why trademarks are important and how they help protect a brand’s identity. While you can register trademarks yourself, Hancock suggests working with a lawyer who knows intellectual property law and does it for a living.

\n

It’s not simple and straightforward.You don’t pay $100 and instantly gain protection for your brand name around the world. It’s why I recommend not doing it yourself – work with a lawyer who knows intellectual property law and does this for a living.

\n

Earlier this year, I wrote about how the GPL doesn’t give people the right to infringe trademarks. As the WordPress product market matures, I think we’ll see more businesses trademark their logo and product names, especially if more sites like GPL Club are created. If you’ve gone through the process of registering or enforcing a trademark for your product or business, share your experience in the comments.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 14 Aug 2014 01:00:57 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:30;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:90:"WPTavern: WPCore App Adds Export Feature: Save Active Plugins to a Collection with 1-Click";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28318";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:222:"http://wptavern.com/wpcore-app-adds-export-feature-save-active-plugins-to-a-collection-with-1-click?utm_source=rss&utm_medium=rss&utm_campaign=wpcore-app-adds-export-feature-save-active-plugins-to-a-collection-with-1-click";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3043:"

We’ve been following the evolution of the WPCore plugin management app, which recently added favoriting, update notifications, and the ability to add plugins that aren’t hosted on WordPress.org. Today, the app’s developer, Stuart Starr, announced what is perhaps the most convenient feature to date.

\n

With WPCore Plugin Manager installed, users can now export all of their plugins with one click and save them to a new collection on WPcore.com. This is useful if you have a site that already has all the plugins you want to include in a specific collection.

\n

export

\n

Despite the fact that the plugin makes it convenient to install all your favorite plugins in one click, you may find that building collections requires quite a bit of work. The new export feature makes it possible to build a collection instantly, based on an existing site’s active plugins. Currently, it can only export active plugins hosted on WordPress.org, but Starr plans to expand the feature in the future.

\n

Clone WordPress Plugin Collections

\n

Another new feature that you’ll find on the app side of WPCore is the ability to clone other users’ collections. Perhaps you want most of the plugins in one collection but want to add or remove a few selections. Click on the new clone button to copy the collection to your own account for editing.

\n

clone-collection

\n

Starr is continuing development on the app and plugin, inspired by positive feedback from users who are saving time with WPCore. “The feedback has been amazing. In terms of users we are getting new users daily,” he said. One satisfied fan dubbed WPCore the “Pinterest for WordPress plugins.”

\n

September will bring a major update to the service. Starr wouldn’t comment on the specifics of features on the way but he did reveal that he is currently working on a referral system. WPCore is moving to a paid subscription model as of August 31st but users who sign up before that time will be grandfathered in as Pro members for life. New free signups will continue to have access to the basic features of the app.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Aug 2014 23:47:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:31;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:73:"WPTavern: New WordPress Plugin Spell Checks Post Titles Before Publishing";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28230";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:190:"http://wptavern.com/new-wordpress-plugin-spell-checks-post-titles-before-publishing?utm_source=rss&utm_medium=rss&utm_campaign=new-wordpress-plugin-spell-checks-post-titles-before-publishing";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1941:"

Have you ever published a post in WordPress only to realize the title has a misspelled word? Sure, a quick edit will do the trick but wouldn’t it be nice if the misspelling was caught before the post went live? WordPress doesn’t spell check post titles but you can change that with a new plugin called Post Title Spell Check, developed by Robert Neu and Brady Vercher.

\nPost Title Spell Checking PluginYep, It Works\n

It’s a simple plugin that adds a small bit of code to the WordPress title input field. Activating the plugin allows all post types which support the default WordPress title input field to be spell checked by modern browsers. There are no settings to configure as it’s a set and forget type of plugin.

\n

How To Spell Check Post Titles Without Using A Plugin

\n

If Firefox is your browser of choice, I found a great guide on Rhour.com that explains how to change a value in Firefox’s configuration file to spell check post titles. The downside to this technique is that it’s for Firefox only. The plugin on the other hand, enables post title spell checking across all modern browsers.

\n

Is this something you’d like to see added to the core of WordPress or should it be left to web browsers to handle?

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Aug 2014 21:48:54 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:81:"WPTavern: WordPress Rainbow Hilite Plugin Adds Rainbow.js for Syntax Highlighting";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28270";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:206:"http://wptavern.com/wordpress-rainbow-hilite-plugin-adds-rainbow-js-for-syntax-highlighting?utm_source=rss&utm_medium=rss&utm_campaign=wordpress-rainbow-hilite-plugin-adds-rainbow-js-for-syntax-highlighting";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4034:"photo credit: Βethan - ccphoto credit: Βethan – cc\n

If you regularly blog code snippets, adding a syntax highlighter plugin can help make your code more readable and easier to copy. Many plugins use language-specific shortcodes to surround embedded code, but this generally requires you to remember the right way to form the shortcode. The new WordPress Rainbow Hilite plugin uses a different method for embedding code in posts.

\n

The plugin incorporates the lightweight Rainbow.js syntax highlighting library into WordPress and is completely themable via CSS. Rainbow Hilite utilizes the visual editor to add language-specific styles to pre tags.

\n

rainbow-hilite-editor

\n

The plugin includes support for 18 commonly used languages, which can be enabled or disabled in the settings located in the Writing panel:

\n

rainbow-languages

\n

It also includes 19 preset visual themes to choose from for making your code beautiful. The settings panel allows you to toggle a sample code block in order to conveniently preview each theme without having to navigate to the frontend.

\n

toggle-code

\n

Below is an example of how code appears on the frontend using the plugin’s sample code. One handy thing Rainbow Hilite’s output is that the highlighted code can be copy-pasted directly out of the site. There’s no “view raw” button to clutter up the code snippet.

\n

rainbow-example

\n

Line numbers are optional and when active they are added using rainbow.linenumbers. The plugin also includes some filters, which allow users to load their own language modules and themes and plugins to hook in.

\n

If you ever decide to stop using the plugin, pre tags aren’t as bad as orphaned shortcodes littered throughout your posts. In other words, using it doesn’t mean that you’re married to the plugin for life. If you’d like to suggest any changes, the development version of Rainbow Hilite is available on GitHub. If you want to use the plugin on your site, you can download it from WordPress.org.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Aug 2014 20:03: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: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:37:"Joseph: WordCamp Salt Lake City, 2014";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://josephscott.org/?p=10802";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://josephscott.org/archives/2014/08/wordcamp-salt-lake-city-2014/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1718:"

wcslc-2014

\n

WordCamp SLC 2014 is coming up fast. Just one month away: Saturday 13 September 2014. This is one day that brings together the local WordPress community like no other. We tend to get a wide range of people attending, from those just starting out, to designers, developers, consultants, and people who contribute to the core code of WordPress.

\n

WordCamp SLC is a great opportunity to learn a few things from the presentations. Even more important than that is the chance to get to know other WordPress users in the community.

\n

One really important thing to note for 2014, the location has changed:

\n

\n

City And County Building
\n451 Washington Square,
\nSalt Lake City, Utah

\n

The registration this year is only $15, which includes lunch. The reduced price is to help offset the cost of parking in down town SLC.

\n

If you are interested in speaking there is still time to submit a presentation proposal.

\n

Go register today and be sure to say hi when I see you on September 13th. Then go give a big thank you to Mike Hansen, he is organizing WordCamp SLC 2014.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Aug 2014 15:49: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:12:"Joseph Scott";s: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:41:"Matt: Extrinsic Motivation Doesn’t 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:21:"http://ma.tt/?p=43987";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:53:"http://ma.tt/2014/08/extrinsic-motivation-doesntwork/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:376:"

From Kathy Sierra, here’s “One of the longest deep studies on negative impact of external reinforcers (e.g. rewards) on long-term motivation”: Multiple types of motives don’t multiply the motivation of West Point cadets. Academic, but interesting.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Aug 2014 15:37: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:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:82:"WPTavern: Espied: A Free WordPress Portfolio Theme for Designers and Photographers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28131";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:206:"http://wptavern.com/espied-a-free-wordpress-portfolio-theme-for-designers-and-photographers?utm_source=rss&utm_medium=rss&utm_campaign=espied-a-free-wordpress-portfolio-theme-for-designers-and-photographers";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3633:"

If you’re on the hunt for a new design to showcase your work, WordPress.com’s beautiful Espied theme is now available for use on self-hosted sites. This striking minimalist portfolio theme was created with designers, photographers, and artists in mind.

\n

Espied utilizes WordPress.com’s portfolio feature, which was recently added to Jetpack. With this custom content type enabled, users can easily manage and showcase projects with the [portfolio] shortcode.

\n

espied

\n

Customization options for Espied include support for a 1600 × 320px header image, the ability to set the header text color, and a unique option for setting the thumbnail aspect ratio. Featured image ratio options include landscape (4:3), portrait (3:4), and square (1:1). This setting carries over to archive pages, the portfolio page template, and portfolio shortcodes.

\n

espied-archive-page

\n

The theme includes a sidebar that slides out to display navigation and widgets. It is hidden until clicked in order to keep the focus on showcasing your work.

\n

sidebar

\n

Espied also features a beautiful way to display your social links via a custom menu. Add your social URLs as menu items and the theme will automatically display the right icon, if it’s available. It currently includes 22 different icons for various social profiles.

\n

social-links

\n

Espied showcases images at full width on larger displays so it’s important to use images that are at least 1272px. Although the theme does include beautiful, readable typography for blogging, the design is probably best-suited for sites that are primarily portfolios or other visual showcases. Check out a live demo on WordPress.com to see the theme in action.

\n

With the release of Espied, the folks at Automattic are approaching 50 free themes listed on WordPress.org. This portfolio theme is a home run and responds nicely to any screen size. If you want an easy way to showcase your work without having to configure a ton of options, Espied is an excellent choice. Download it from the WordPress.org or install it directly via your admin themes panel.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 13 Aug 2014 04:42: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:36;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:101:"WPTavern: Theme Checklist Helps Prepare Developers To Submit A Theme To The WordPress Theme Directory";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28095";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:246:"http://wptavern.com/theme-checklist-helps-prepare-developers-to-submit-a-theme-to-the-wordpress-theme-directory?utm_source=rss&utm_medium=rss&utm_campaign=theme-checklist-helps-prepare-developers-to-submit-a-theme-to-the-wordpress-theme-directory";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4406:"

Theme Checklist is a new plugin by Greg Priday of SiteOrigin. The plugin provides a checklist of items to go through before submitting a theme to the WordPress theme directory. Once activated, you’ll find the checklist under Tools > Theme Checklist. Theme developers check off each item that successfully passes a test. Themes need to pass all tests before they can be accepted into the WordPress theme directory.

\nCheck List Of Items To Go ThroughCheck List Of Items To Go Through\n

If a test doesn’t pass, you can select the X and a small text area appears allowing you to write and save notes to that item. There are a total of 31 different tests ranging from Code Quality to Security. Each item has a link that takes users to a page on Themechecklist.org with more information. Theme Checklist also contains the ability to import or export tests enabling users to collaborate on testing themes in different environments.

\n

I used Theme Checklist to review the WP Tavern theme and it passed with flying colors.

\nRavel Passes Tests With Flying ColorsWP Tavern Theme Passes With Flying Colors\n

Theme Checklist Is An Alternative Learning Experience

\nTheme Check List Featured Imagephoto credit: Dr Case – cc\n

Although the plugin is not an exact match, Priday will do his best to keep the checklist in line with the official WordPress.org Theme Review Guidelines. “My goal is to make a kind of Dummies Guide to The Theme Review Guidelines” Priday said. “I’ve generally found that the theme review guidelines are really difficult for new theme developers to understand. I’ve tried to make something that makes all the requirements easier to understand.”

\n

Theme Checklist is not meant to be a replacement for the Theme Check plugin. Instead, it’s a collection of the most common snag points witnessed by Priday in the theme review queue. According to Priday, the queue has a five-week backlog. He hopes Theme Checklist helps decrease the queue and gets more theme developers to pass the initial review.

\n

I understand why the theme review guidelines need to be thorough and specific. It’s the WordPress.org theme directory and they help create a consistent user experience. Plugins like Theme Checklist provide an alternative learning experience to accomplish the same goal. However, it has to remain on par with the official guidelines or else it could end up doing more harm than good.

\n

Theme developers, is this a tool you see yourself using? What other tools do you use to increase the likelihood of passing a review on the first try?

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 22:45: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:89:"WPTavern: Right Meow Plugin Puts The Super Troopers Cat Game Into Your WordPress 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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28201";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:222:"http://wptavern.com/right-meow-plugin-puts-the-super-troopers-cat-game-into-your-wordpress-comments?utm_source=rss&utm_medium=rss&utm_campaign=right-meow-plugin-puts-the-super-troopers-cat-game-into-your-wordpress-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1976:"

Broken Lizard’s 2001 comedy “Super Troopers” introduced millions of viewers to the “cat game.” In the scene, a highway patrolman pulls Jim Gaffigan over and then tries to insert the word “meow” casually into the conversation as many times as possible. You remember that scene, right? If not, check it out here:

\n

\n

Am I Saying Meow?!

\n

Now, you can also have subliminal meow fun with Right Meow, a WordPress plugin that changes your comments section so that the word “now” automatically becomes “meow,” as shown below:

\n

meow

\n

The plugin was created by Thomas Leen and is his first submission on WordPress.org. It’s also available on GitHub, should you want to suggest any changes. After testing it, I can confirm that it works as advertised to transform all instances of “now” to “meow” in the comments.

\n

This may not be the most productive tool in the shed but it definitely adds a dash of frivolity and fun to your site by automatically trolling commenters with meows on your behalf. Please note that de-activating the plugin will return all your “meows” back to “nows.” If you want your comments to have a little more entertainment value, I recommend you download this plugin right meow.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 22:20: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: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:69:"Alex King: The Race to the Bottom Benefits Platforms (not Developers)";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://alexking.org/?p=20713";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://alexking.org/blog/2014/08/12/race-to-bottom-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3773:"

There’s been a ton of recent conversation in the iOS world about the inability for most indie developers to create sustainable businesses through the iOS app store. In particular, these devs are talking about apps that require larger development efforts – they want to charge more than “impulse purchase” prices for these, and thus want trials, upgrade pricing, etc. to support that model. They want things to work they way they always have – I don’t blame them.

\n

I think it’s worth considering who wins in this “race to the bottom”. In general, more stuff for free benefits consumers, which in turn benefits the platform.

\n

“But wait!” the developers cry. “When the platform doesn’t support building more sophisticated apps, the consumers ultimately lose!” I know this argument, I’ve made it myself regarding the WordPress ecosystem. I was wrong.

\n

Consumers have been well trained that they can expect incredible value for free. Sure, they may trade off their privacy and be subjected to ads, but they aren’t asked to fork over their cash directly.

\n

VC-backed companies often contribute to the problem as well. As they clamor for users to their platforms, they give everything away – it’s so easy to flip the switch in the future and start the money pouring in. Or if that doesn’t work, they fold up shop and call it a day. Oops!

\n

More complex apps will get made. They just won’t be built using the model that indie developers are used to.

\n

There will be apps supported by alternative revenue streams. Some might have ads or sponsorships, some might mine and sell the data they produce, some (like Evernote and Dropbox) will be a gateway to a commercial service. People will figure out ways to get money out of a large enough user base, and apps will get built.

\n

I’ve seen this happen in the WordPress ecosystem already. It’s a different beast because it’s an Open Source community, but it’s still an interesting parallel.

\n

Basically this happened:

\n
    \n
  1. A bunch of folks built stuff and released it all for free to a small community, largely consisting of fellow developers and tinkerers
    2. \n
  2. A whole bunch more folks started using the platform and the community grew – it wasn’t just developers anymore, it was end users with expectations of support, etc.
    3. \n
  3. Devs wanted to start monetizing the products they were providing
    4. \n
  4. The platform didn’t provide the tools to make money in the way that the devs wanted -instead it invested in tools to promote free products
    5. \n
  5. Eventually a variety of patterns arose to monetize both commercial and “free” products (subscription clubs with access to a bunch of different plugins/themes, free products with commercial add-ons, sponsorships and ads, products that were created to support hosting services, etc.)
    6. \n
\n

It’s not the :scare: pure :/scare: and direct approach of charging directly for the software, but it’s still developers writing code and making money.

\n

The same thing is happening for iOS. There is money to be made. The platform and consumers are winning.

\n

“Adapt or die” is our mantra for those business who are threatened by technology. We have little sympathy for newspapers, the music industry, etc. Perhaps it’s time to include software companies in that list.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 21:53:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Alex";s: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:110:"WPTavern: Sprout Apps to Launch a Suite of WordPress-Powered Apps Targeted at Freelancers and Small Businesses";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28141";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:264:"http://wptavern.com/sprout-apps-to-launch-a-suite-of-wordpress-powered-apps-targeted-at-freelancers-and-small-businesses?utm_source=rss&utm_medium=rss&utm_campaign=sprout-apps-to-launch-a-suite-of-wordpress-powered-apps-targeted-at-freelancers-and-small-businesses";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6601:"

sprout-apps

\n

Sprout Apps will soon be launching a suite of business apps targeted at WordPress freelancers and small businesses. WordPress developer Daniel Cameron is behind the project, which is centered around creating plugins that help business owners work more efficiently with WordPress. Sprout Apps aims to bring tasks like invoicing, estimates, and client tracking into the admin.

\n

Cameron is the creator of Smart eCart, a popular solution for daily deals, crowdfunding and social commerce. For five years he has supported and maintained the plugin, which was originally created for a client project. With the desire to venture out and create something new, Cameron has soft-launched Sprout Apps, starting with Sprout Invoices, now available for purchase.

\n

sprout-apps-invoices

\n

Sprout Invoicing is an idea that Cameron had cooked up year ago but was hesitant about, due to the fact that other plugin developers had explored it without much success.

\n

“I went back to my original idea that I had years ago, which was a new invoicing app that solved all the problems I’ve had with Freshbooks and Harvest,” he said. “I knew there were already plugins out there which made me reluctant to pursue it further, regardless if their approach was wrong in my opinion.”

\n

Sprout Invoicing Aims to Help Streamline and Brand All Client Communications

\n

In order to sell his product, Cameron will have to convince business owners of the value in using a WordPress-powered invoicing system instead of the many standalone services. He’s counting on customers’ desire to streamline all aspects of their businesses.

\n

“Those other standalone services are silo’d, expensive, limiting and offer limited customization for brand integrity,” Cameron contends. “I want to streamline the estimate and invoicing process. Integrating it within the site that already has the estimate request (contact form) helps tremendously.”

\n

In addition to fully automating estimating and invoicing, the app is designed to help business owners overcome the branding limitations of popular invoicing services, which generally only let you upload a logo to a subdomain. The freedom to fully brand all client communications is a big win for small businesses.

\n

“Sprout Invoice notification emails are sent from your server and your from address,” Cameron said. “No more http://yoursite.harvestbooks.com with a ‘Powered by A Service I Pay For’.”

\n

The invoicing app is built with business owner’s needs in mind. It’s packed full of dashboards and charts, summaries, and dynamic reporting that can be easily sorted and filtered in the WordPress admin.

\n

sprout-invoicing-charts

\n

Under the hood, Sprout Invoices is a WordPress plugin that uses custom post types, post meta and taxonomies for its data structure. “There are no additional tables created. The entire code base adheres to WordPress coding practices,” Cameron told the Tavern. “There’s hundreds of hooks and filters in SI, I want the entire app to be customizable and I anticipate it’s users to want more control than traditional WP users.”

\n

The apps he plans to build are actually WordPress plugins, though he felt that apps was a more applicable term. “I didn’t want to go with ‘Sprout plugins,’ for example, because I do have ideas that aren’t plugins and I didn’t want to box myself in,” he said. “I also think ‘Apps’ is a better term for these larger premium plugins since they offer more than a traditional plugin that might filter post content.”

\n

Sprout’s next app will be a CRM, followed by a team-based app. Cameron is also considering a PM app and a time tracker, depending on how sales go with the invoicing app. Pricing for Sprouts Invoicing is similar to that of popular invoicing services, with both monthly and yearly subscription rates at $5 and $9 respectively. Subscribers will receive updates, support and add-on discounts. Cameron also plans to launch a free version of the invoicing app later this year.

\n

Sprout Apps is built on the bold premise that your WordPress site can be more than just the marketing face of your business. It can also power the daily tasks of estimating work, billing clients, and charting progress. Cameron is aiming to provide all the business essentials with the added benefit of brand independence, a streamlined workflow, and total control. He’s got a big vision to create a superior suite of apps that will support the many freelancers and small businesses that make up a large segment of the WordPress ecosystem.

\n

Sprout Apps is currently in pre-launch mode and will officially launch at WordCamp LA in early September. A live demo of the app is available to preview and pre-launch subscribers will receive a discount at purchase.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 20:54: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: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:"WPTavern: WP Site Care Acquires Audit WP";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28140";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:124:"http://wptavern.com/wp-site-care-acquires-audit-wp?utm_source=rss&utm_medium=rss&utm_campaign=wp-site-care-acquires-audit-wp";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1996:"Merge Featured Imagephoto credit: rutlo – cc\n

Audit WP has been acquired by WP Site Care. According to the announcement, Audit WP will operate under WP Site Care while continuing to offer specialized SEO services. Rob Neu, who owned and operated Audit WP, will become WP Site Care’s Director of Digital Strategy.

\n

Rob will oversee product development as well as making sure that our brand, services, and content align with our ultimate goal of providing top-tier WordPress support, and making WordPress an asset for our clients and people who are new to the platform.

\n

Neu hints that new SEO training packages are being worked on and a new plugin is being developed that will make it easier for WP Site Care customers to receive support from the WordPress dashboard.

\n

Neu cites his passion for wanting to help businesses and individuals as one of the primary reasons for merging with WP Site Care. “At my core, the thing I like the most about everything that I do is that I’m able help people,” Neu said. “I want to help people improve their businesses, make more money, and be more successful.”

\n

By joining WP Site Care, a business dedicated to helping people solve WordPress problems, he’s in a great position to do just that.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 18:26:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:22:"Matt: The Great Filter";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=43964";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:36:"http://ma.tt/2014/08/thegreatfilter/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:423:"

\n

This is about the Great Filter. (No, not Akismet.) It’s Adam Ford and Robert Hanson on existential risks to humanity, a continuation of the Fermi Paradox discussion I posted about the other day.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 16:39: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:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:78:"Post Status: Audit WP to become part of WP Site Care with acquihire of Rob Neu";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"http://www.poststat.us/?p=7078";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:108:"http://www.poststat.us/wp-site-care-rob-neu/?utm_source=rss&utm_medium=rss&utm_campaign=wp-site-care-rob-neu";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3669:"

wp-site-care

\n

Audit WP had a short, but interesting life span. Started by Rob Neu and Jacob King, the site launched in February, and today it’s been acquired by WP Site Care.

\n

They made an early splash after their launch when Jacob wrote a provocative post about WP Engine’s SEO policies. Aside from that, they set out to productize technical SEO and general website strategy.

\n

Their product was fairly successful, but they learned a valuable lesson; they were limiting their consulting opportunities for larger contracts by productizing — and therefore bracketing themselves at a relatively low price — their entry level services. That said, the product was quite good, and will now be part of WP Site Care’s offering in the form of a la carte SEO consulting, reports, and tools.

\n

I had a call with Rob and Jacob a couple of months ago to demo their product, and because I needed real help from them. I’d been getting clobbered by Google, and they helped me identify some of the reasons why and set about a plan to fix it. I’m still working on it, and was very pleased with what they offered.

\n

audit-wp-overview

\n

This and other tools were quite nice, and the value I got from a short call and report were pretty enormous. I think this will be a compelling product for WP Site Care’s services, and it will fit in well with their other offerings.

\n

If you know Rob Neu and WP Site Care’s owner, Ryan Sullivan, then you already know they are friends. Rob joining WP Site Care doesn’t come as a shock, and seems to make sense all around. The two are already working on a separate side project together, called Flagship, a theme company. Additionally, WP Site Care was a sponsor and often attendee on WP Bacon, Rob’s old podcast that also unfortunately bit the dust.

\n

Rob and Ryan’s partnership for Flagship will remain separate, and Rob will be the Director of Digital Strategy for WP Site Care, now a team of five full time employees. Rob is a technical guy, and in addition to running strategy and marketing for WP Site Care, he’ll be working on refining some of their product offerings as well.

\n

What is WP Site Care anyway?

\n

I talked about WP Site Care and other WordPress maintenance services earlier this year. Essentially it’s a combination of monthly maintenance and support, and a la carte services. It’s been a wildly successful and growing niche in the WordPress market, and there seem to be new companies popping up every day.

\n

While I don’t know the degree of professionalism and expertise all of them have, I know that at least a few are very good at what they do. WP Site Care adding Rob and the variety of tools he brings to the table is a smart move for them to help set themselves apart in what is quickly becoming a crowded market.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 15:59: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:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:85:"WPTavern: Add Reddit Style Commenting to WordPress With the Comment Popularity Plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28045";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:214:"http://wptavern.com/add-reddit-style-commenting-to-wordpress-with-the-comment-popularity-plugin?utm_source=rss&utm_medium=rss&utm_campaign=add-reddit-style-commenting-to-wordpress-with-the-comment-popularity-plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5010:"

comments

\n

Comments are an important aspect of your content and can serve as a vehicle for building community. WordPress site admins put in a hefty amount of work moderating comments and combating spam, just to keep the conversation going with comments open. With all that work invested, admins are looking for new ways to make comment interaction more valuable to those who are participating.

\n

WordPress.com recently added comment likes to the delight of its users. Self-hosted WordPress site admins are hopeful that comment likes will find their way into Jetpack as well. If you’re interested in doing something more with comments, there are many plugins that help to promote interaction on your site.

\n

Comment Popularity is a new one that caught my eye. The plugin, created by Paul de Wouters and his colleagues at Human Made, adds Reddit style commenting to WordPress. Registered site members can vote comments up or down to increase or decrease comment visibility.

\n

comment-popularity

\n

When the plugin is active, comments are sorted by weight (number of votes) in a descending order. Site members receive karma each time one of their comments is upvoted. Administrators have the option to attribute more weight to “expert” commenters by adding an expert label and additional points on user profiles.

\n

user-profile-comment-popularity-settings

\n

There’s also an option in the discussion panel for setting a default expert karma.

\n

De Wouters and the folks at Human Made plan to support and maintain the plugin via the forums on WordPress.org. It was originally created for their client, CFO Publishing, who will be listed as a contributor on the next release.

\n

“I have a few ideas for integration with other plugins such as Stream, and our SaaS product WP Remote,” de Wouters said. I asked if he plans to add a UI for showing users their aggregate upvotes/ranks, and he confirmed that this is a possibility. “We’re already storing users voting activity, so it makes sense to offer an admin view for it,” he said. “Maybe a dashboard widget. Also, this is the kind of data we’d send to WP Remote or Stream.”

\n

The plugin is currently restricted to registered users, as it doesn’t make much sense to leave it open for anonymous users to vote. “I do however plan to develop a drop in class that will allow users to authenticate themselves via social networks, which will reduce friction and still provide a way to identify a user with relative reliabilty,” de Wouters commented regarding future development plans. Although he wants to keep it simple and focused on one particular functionality, he is open to suggestions and contributions via the plugin’s GitHub repository.

\n

Comment Popularity gives registered users a way to weigh in on discussions without having to comment. Consequently, there is a greater incentive for readers to register for your site. It gives everyone a chance to influence the conversation. As users attribute value to comments they like, the best comments will float to the top. This saves readers from having to scroll through all the mediocre comments in order to find the highest quality responses.

\n

If you’re looking for a new way to encourage interaction in your comments, the Comment Popularity plugin is simple and intuitive to use. It should work automatically with most standard comment forms. Download the plugin for free from WordPress.org and watch the GitHub repository for updates in development.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 12 Aug 2014 00:14:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:77:"WPTavern: Interview With Siobhan McKeown On The Future Of The WordPress Codex";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28089";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:198:"http://wptavern.com/interview-with-siobhan-mckeown-on-the-future-of-the-wordpress-codex?utm_source=rss&utm_medium=rss&utm_campaign=interview-with-siobhan-mckeown-on-the-future-of-the-wordpress-codex";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6798:"

If you use WordPress, chances are that you’ve run into the WordPress Codex. The Codex is a community maintained collection of documentation, hooks, filters, best practices, and other information related to WordPress. With various handbook projects underway, I’ve been wondering what the future of the Codex is. To find out, I got in touch with Siobhan McKeown, who is a member of the documentation team.

\n

Interview With Siobhan McKeown

\n

Is the roadmap outlined here still accurate and is it being followed? Is it still on time?

\n

The roadmap is still fairly accurate but it’s not on time. The number of contributors to docs is quite small and we’ve faced challenges around getting development work done and finding people to write. That said, the people who are involved are very dedicated and we’re slowly chipping away at things. We have made big strides forward, particularly in the area of inline docs (thanks Drew Jaynes and Kim Parsell) and in building developer.wordpress.org.

\n

Ultimately, is the future of the Codex for it to disappear in favor of all the other documentation resources outlined in the roadmap?

\n

I would like for that to happen, but the decision doesn’t ultimately lie with me and it’s a discussion that we’ll have to return to once new documentation is in place.

\n

Many free software projects in the early stages of their life use a wiki for their documentation. Over time, this can become out-of-date and inaccurate. As a project grows, it often out-grows a wiki, requiring more targeted documentation for both users and developers. Firefox and Ruby on Rails are good examples of FOSS projects that provide the types of targeted documentation that WordPress should be providing. I would hope that we can eventually get there ourselves, and keep the Codex as a historical archive.

\nMozilla FireFox Targeted DocumentationMozilla FireFox Targeted Documentation\n

Is it a waste of effort and energy for folks to continue to edit and update the Codex?

\n

No. For two reasons: First of all, while all of the docs work is going on, we need to ensure that the Codex stays up-to-date and accurate. It remains WordPress’ primary source of documentation and will be for some time, so contributions are still valuable there. When a new version of WordPress is released, the docs team usually does a sprint to get the Codex up-to-date.

\n

Secondly, the main problem with the Codex is its navigation and structure. There’s a lot of good content in there mixed with a lot of out-of-date content. As we create new resources, we look at the content in the Codex and migrate good-quality content. If you fix a page in the Codex, then it’s likely that will end up somewhere in a new documentation resource.

\n

How can folks get involved with helping the roadmap move along?

\n

We particularly need help in two areas:

\n
    \n
  1. Someone to help with ongoing development of WP-Parser (the parser used to generate the Code Reference). A lot of things are on hold until we get someone helping there.
    2. \n
  2. Writing the theme and plugin developer handbooks. These have been around for a long time and we really want to get them finished off so that we can move on to focusing on user support.
    3. \n
\n

To Some, Google Is The WordPress Codex

\n

It may be the largest collection of WordPress documentation but I bet it doesn’t compare to the amount of WordPress content published on sites across the web. The paradox of publishing content on the Codex for the benefit of everyone versus a personal site for the benefit of a small audience has existed since it was created.

\n

I think it would be awesome if content from sites like Justin Tadlock found a home on the Codex but perhaps we don’t need one at all. Maybe all we need is Google. When I asked the Tavern’s Twitter followers what aspect of WordPress do they take for granted, Jared Novack submitted the following answer:

\n\n

\n

If the Codex ever goes offline, it will be a sad day. However, if it’s replaced with easy to navigate, skill level targeted documentation, with a solid code reference, I think a lot of users and developers will be happy with its replacement. Has the Codex saved your bacon once or twice? Let us know in the comments.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Aug 2014 22:20:27 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:57:"WPTavern: WPWeekly Episode 157 – Jeffro Tells His Story";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:44:"http://wptavern.com?p=28075&preview_id=28075";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:150:"http://wptavern.com/wpweekly-episode-157-jeffro-tells-his-story?utm_source=rss&utm_medium=rss&utm_campaign=wpweekly-episode-157-jeffro-tells-his-story";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2274:"

The past 156 episodes of WordPress Weekly are filled with stories of people who are doing exciting things with WordPress. For this episode, I decided to try something a little different. I handed the show over to Marcus Couch, who interviewed me. In the show, I describe how I became interested in computers and the events that lead me to where I am today. It’s a lengthy episode but one I hope you enjoy.

\n

A reminder that beginning this week, WordPress Weekly will be recorded live on Wednesdays at 9:30 PM Eastern. The change better accommodates my schedule and the new day and time is also more compatible with guests.

\n

Stories Discussed:

\n

WordPress 3.9.2 Fixes Security Vulnerabilities, Users Strongly Encouraged To Update
\nCrowd Favorite Announces Chris Lema As New CTO
\nHow to Change Jetpack Accounts Without Losing Your Stats or Subscribers

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, August 13th 3 P.M. Eastern – Special Guest, Pippin Williamson

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #157:
\n

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Aug 2014 20:05:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:67:"WPTavern: Underscores WordPress Starter Theme Adds Support for Sass";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"http://wptavern.com/?p=28061";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:178:"http://wptavern.com/underscores-wordpress-starter-theme-adds-support-for-sass?utm_source=rss&utm_medium=rss&utm_campaign=underscores-wordpress-starter-theme-adds-support-for-sass";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3186:"

Underscores community project contributors announced today that the theme now includes support for Sass. The popular WordPress starter theme is an open source project maintained by Automattic, and many of its users requested Sass support, according to contributor Tammie Lister. “The community firstly asked for Sass. As Sass is in core, this makes sense. It was already part of most themers’ workflow.”

\n

If you visit Underscores.me and click on “Advanced Options”, you’ll now find that you can check a box to add Sass support:

\n

add-sass

\n

Lister emphasized in the announcement that support for Sass is included in a way that gives developers the freedom to use it as they please:

\n

Not everyone compiles or uses Sass the same, so _s shouldn’t force anyone to follow one path or another. In this sense, the Sass provided takes a pure approach, not requiring Compass or any other scripts.

\n

Sass support came about from a combination of numerous pull requests and forks of the project on GitHub. However, the project’s contributors do not wish to limit everyone to Sass and are open to other CSS preprocessors. “I’d still love to see a fork of Less for _s. We’re keen it opens up the way to other preprocessors,” Lister told the Tavern regarding the Sass support announced today.

\n

Earlier this year, WordPress.com formally opened up its marketplace to theme developers. Theme submission guidelines are fairly strict and developers are encouraged to use the _s theme for a head start. While many theme authors appreciate the ability to save time with mixins and variables, using a preprocessor is not required for submitting to WordPress.com.

\n

Every WordPress themer has a unique workflow that may or may not involve a preprocessor, and the Underscores project contributors plan to respect that. “_s doesn’t tell you how to do things, it gives you a start. Anything we add to it should also do that,” Lister said.

\n

The addition of Sass support marks another turning point for the project, as Lister notes that the GitHub repository will now be used solely for development. If you want to use Underscores in a project, the team encourages you to download it directly from Underscores.me.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Aug 2014 19:00:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:93:"Post Status: Week in review: theme shops, hub and spoke, you can’t afford me, and much more";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:30:"http://www.poststat.us/?p=7070";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:168:"http://www.poststat.us/week-review-theme-shops-hub-spoke-cant-afford-much/?utm_source=rss&utm_medium=rss&utm_campaign=week-review-theme-shops-hub-spoke-cant-afford-much";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10330:"

week-in-review

\n

Welcome to the seventh “Week in Review” on Post Status, where I hope to offer up some of the things you may have missed in the last week or so. A whole bunch of good stuff to read from the last week, so let’s get to it:

\n

Theme shops sorted by their Alexa rank

\n

Devin Price has updated his list of WordPress theme shops, sorted by Alexa rank, for 2014. This is a really interesting list that’s sure to enlighten you to some theme shops that you’ve never heard of. I’ve referenced the 2013 version many times in the past. I’m glad Devin put time into doing this again.

\n

Alexa isn’t a perfect way to rank theme shops, obviously, but it does offer good insight to see what average Joes unfamiliar with the WordPress theme landscape probably stumble upon as they search for WordPress themes. As Devin notes, the order of the top shops haven’t changed a whole lot in the past year, though pretty much all have gained ground, and WPMU Dev jumped all the way to number 1 from number 6.

\n

Hub and spoke versus distributed teams

\n

Jeff Chandler blogged about Crowd Favorite’s hub and spoke office (edit: it’s actually a constellation model; no “hub”) model (a central office + many smaller offices). Jake Goldman responded with his case for a fully distributed team (10up’s model). Both offer quality insight into how some of the larger WordPress consultancies operate.

\n

You can’t afford the plugin you want

\n

Chris Lema has written an excellent post about custom plugin development, and why you just can’t get the exact thing you want off the shelf (unless you get real lucky).

\n

That plugin that does everything you ever wanted? It doesn’t exist. And if it did, if someone built it, it would cost you thousands and thousands of dollars.

\n

Because what you often describe isn’t a plugin. It’s a system.

\n

And since you don’t want to connect several focused plugins, that each do the one thing they were made to do, you won’t really find the perfect plugin sitting there waiting for you.

\n

SSL all the things

\n

\n

Google spoke from on high, declaring SSL to be a portion of their ranking algorithm. The SEOs and the SSL sellers rejoiced. Tim Nash has a nice primer on the nerdy details of SSL. Joost de Valk also has some practical tips for switching over to SSL. And Zack Tollman has a great performance post over at The Theme Foundry about SPDY and SSL.

\n

Now, all that said, seriously don’t freak out about SSL. It is great, that’s true, but just because Google says it’s part of their algorithm doesn’t mean you have to have it no matter what. Still though, having SSL enabled is probably a good thing for most sites, if you can afford it. Just be smart about it, and not purely reactionary to Google’s whims.

\n

Some hosts start to support Clef, the password-less login app

\n

SiteGround and three other hosts announced default support for Clef last week. New installs on those platforms will enable the password-less login app. Clef works as a form of two-factor authentication, since you have to have your phone on you and scan the login screen to access the site.

\n

It’s obviously past time to rely purely on passwords, so it’s good to see folks supporting Clef and other two-factor methods out of the box.

\n

WordPress-based portfolio templates, with Semplice

\n

Semplice is a WordPress portfolio template product, that’s still in development, but it’s definitely outside of the normal WordPress themes you see. I got in touch with the folks behind Semplice and they expect to have something ready in a few weeks for beta testing. It seems you can already buy it though, so I don’t know what that’s about. Either way, this may be a product to keep an eye on.

\n

The WordPress security “delimma”

\n

Tony Perez, CEO of Sucuri, write about what he considers to be a delimma with WordPress security. I don’t personally agree with some of Tony’s conclusions here, but they are worth reading, as your mileage may vary. He takes some folks’ words to task (including my own), but I think in the end there is a more a difference in opinion on how to delivery the security message versus actual differences in implementing security measures.

\n

I believe the Drupal vs WordPress method for highlighting last week’s security release was a reflection of how WordPress and Drupal communicate in general; WordPress said it as if speaking to regular site owners and Drupal spoke to developers. To me, making WordPress accessible to regular people is paramount — related to security issues or not.

\n

I have a lot more I can say about this, but I have no desire to get in a pointless battle when I think we mostly agree on the goal, just not the message. But I do have one more note. Tony finishes his post with this:

\n

You can’t own 22% of the market and not expect issues. Is it best to fight it and blindly convince yourself that they don’t exist, or is it better to embrace it?

\n

I take exception to this. I don’t know anyone in a significant position within the WordPress project that takes such a “blind” stance. You can’t say WordPress core developers don’t take security seriously, because they absolutely do.

\n

Stellar and international payments

\n

Stellar is a “a decentralized protocol for sending and receiving money in any pair of currencies” with some big backers, like Stripe. Brent and Kirby, at Prospress, nerded out over Stellar when it launched, and then wrote up a great post about what this could mean for big savings in international eCommerce.

\n

Tablesaw: responsive tables, by Filament Group

\n

Responsive tables are a pain. The Filament Group really attacked them with Tablesaw. This is a really nice solution that you may consider for implementation with certain types of themes and websites.

\n

Comment likes on WordPress.com

\n

WordPress.com has introduced comment likes. This could be great for some sites with heavy amounts of comments, especially if they add some sorting options to bring good comments to the top. It might be a while before this one hits Jetpack though; apparently there are some technical challenges there.

\n

Get news of new WordPress.com themes

\n

Also in WordPress.com land, it turns out they aren’t really blogging about every theme release any more. So Luke McDonald put together a Twitter account to help keep you informed.

\n\n

\n

Why attend WordPress conferences (and updates on some of them)

\n

Andy Leverenz puts some good reasons together on the Elegant Themes blog about why you should attend WordPress conferences, and he highlights some of those coming up.

\n

Speaking of, if you want to go to PressNomics (the attendee list is awesome so far), you better act soon; that conference could sell out really soon.

\n

The first and second batches of WordCamp San Francisco speakers have been announced.

\n

WordCamp Europe’s speaker list is also dripping out, and it’s pretty amazing; that’s going to be an incredible event in Sofia.

\n

Finally, if you’re in the south, WordCamp Birmingham (my local camp — #WPYall!) is this Saturday. It’s going to be a great time, and I hope I get to meet some of you there. You can still register, so do that and come learn with us.

\n
\n

Have a great week, y’all. Make some news, and I’ll write it. Be on the lookout too, I’ve got my own news to share in the next month or so. Which means it’s probably a good time to subscribe to my newsletter.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Aug 2014 17:22:44 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:15:"Brian Krogsgard";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:26:"Matt: Mosquito Preferences";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:21:"http://ma.tt/?p=43977";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"http://ma.tt/2014/08/mosquito-preferences/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:340:"

Why Do Mosquitoes Bite Some People More Than Others? I’m pretty lucky in the mosquito-biting department, they tend to go for others around me. So this article is for those that take one for the team.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Aug 2014 14:10:54 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:74:"Lorelle on WP: Find, Search, Replace, and Delete in the WordPress Database";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:37:"http://lorelle.wordpress.com/?p=11808";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:97:"http://lorelle.wordpress.com/2014/08/10/find-search-replace-and-delete-in-the-wordpress-database/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:545:"The following was originally published on WordCast and authored by Lorelle VanFossen. It is reprinted here as a reference guide. You’ve moved your WordPress installation from one server to another. You’ve changed domain names. You’ve moved images around on your server and now they don’t load. You’ve changed your WordPress installation and now images show […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 10 Aug 2014 23:36: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:17:"Lorelle VanFossen";s:7:"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";a:10:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 20 Aug 2014 22:26:17 GMT";s:12:"content-type";s:8:"text/xml";s:14:"content-length";s:6:"206367";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Wed, 20 Aug 2014 22:15:13 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";s:13:"accept-ranges";s:5:"bytes";}s:5:"build";s:14:"20140820222237";}', 'no'); INSERT INTO `options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (121, '_transient_timeout_feed_mod_867bd5c64f85878d03a060509cd2f92c', '1408616778', 'no'), (122, '_transient_feed_mod_867bd5c64f85878d03a060509cd2f92c', '1408573578', 'no'), (123, '_transient_timeout_feed_b9388c83948825c1edaef0d856b7b109', '1408616778', 'no'), (124, '_transient_feed_b9388c83948825c1edaef0d856b7b109', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n \n";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:72:"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:39:"WordPress Plugins » View: Most Popular";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://wordpress.org/plugins/browse/popular/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:39:"WordPress Plugins » View: Most Popular";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"en-US";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 20 Aug 2014 22:08: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:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:25:"http://bbpress.org/?v=1.1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:15:{i:0;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:7:"Akismet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"http://wordpress.org/plugins/akismet/#post-15";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 09 Mar 2007 22:11:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"15@http://wordpress.org/plugins/";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:98:"Akismet checks your comments against the Akismet Web service to see if they look like spam or not.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:22:"WordPress SEO by Yoast";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:53:"http://wordpress.org/plugins/wordpress-seo/#post-8321";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Jan 2009 20:34: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"8321@http://wordpress.org/plugins/";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:131:"Improve your WordPress SEO: Write better content and have a fully optimized WordPress site using the WordPress SEO plugin by Yoast.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Joost de Valk";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"Contact Form 7";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:54:"http://wordpress.org/plugins/contact-form-7/#post-2141";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2007 12:45:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"2141@http://wordpress.org/plugins/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:54:"Just another contact form plugin. Simple but flexible.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Takayuki Miyoshi";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Jetpack by WordPress.com";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:48:"http://wordpress.org/plugins/jetpack/#post-23862";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Jan 2011 02:21:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"23862@http://wordpress.org/plugins/";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:104:"Supercharge your WordPress site with powerful features previously only available to WordPress.com users.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"Tim Moore";s: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:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"Wordfence Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/plugins/wordfence/#post-29832";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 04 Sep 2011 03:13: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"29832@http://wordpress.org/plugins/";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:137:"Wordfence Security is a free enterprise class security and performance plugin that makes your site up to 50 times faster and more secure.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Wordfence";s: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:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:15:"NextGEN Gallery";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"http://wordpress.org/plugins/nextgen-gallery/#post-1169";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 23 Apr 2007 20:08:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"1169@http://wordpress.org/plugins/";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:121:"The most popular WordPress gallery plugin and one of the most popular plugins of all time with over 10 million downloads.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Alex Rabe";s: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:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"MailPoet Newsletters";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/plugins/wysija-newsletters/#post-32629";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Dec 2011 17:09: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"32629@http://wordpress.org/plugins/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:94:"Send newsletters, post notifications or autoresponders from WordPress easily, and beautifully.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"MailPoet Staff";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"All in One SEO Pack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:58:"http://wordpress.org/plugins/all-in-one-seo-pack/#post-753";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 30 Mar 2007 20:08: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"753@http://wordpress.org/plugins/";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:126:"All in One SEO Pack is a WordPress SEO plugin to automatically optimize your WordPress blog for Search Engines such as Google.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"uberdose";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"WP Super Cache";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:54:"http://wordpress.org/plugins/wp-super-cache/#post-2572";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 05 Nov 2007 11:40: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"2572@http://wordpress.org/plugins/";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:73:"A very fast caching engine for WordPress that produces static html files.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Donncha O Caoimh";s: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:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"WordPress Importer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/plugins/wordpress-importer/#post-18101";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 May 2010 17:42: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"18101@http://wordpress.org/plugins/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:101:"Import posts, pages, comments, custom fields, categories, tags and more from a WordPress export file.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Brian Colinger";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"Google XML Sitemaps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:63:"http://wordpress.org/plugins/google-sitemap-generator/#post-132";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 09 Mar 2007 22:31:32 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:33:"132@http://wordpress.org/plugins/";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:105:"This plugin will generate a special XML sitemap which will help search engines to better index your blog.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:5:"arnee";s: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:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";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:"iThemes Security (formerly Better WP Security)";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:59:"http://wordpress.org/plugins/better-wp-security/#post-21738";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 22 Oct 2010 22:06: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"21738@http://wordpress.org/plugins/";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:63:"The easiest, most effective way to secure WordPress in seconds.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Chris Wiegman";s: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:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:33:"WooCommerce - excelling eCommerce";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:52:"http://wordpress.org/plugins/woocommerce/#post-29860";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 05 Sep 2011 08:13:36 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"29860@http://wordpress.org/plugins/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:97:"WooCommerce is a powerful, extendable eCommerce plugin that helps you sell anything. Beautifully.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"WooThemes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:13;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:11:"Meta Slider";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"http://wordpress.org/plugins/ml-slider/#post-49521";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 14 Feb 2013 16:56: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"49521@http://wordpress.org/plugins/";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:145:"Easy to use WordPress slider plugin. Create SEO optimised responsive slideshows with Nivo Slider, Flex Slider, Coin Slider and Responsive Slides.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"Matcha Labs";s: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:30:"\n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Fast Secure Contact Form";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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:"http://wordpress.org/plugins/si-contact-form/#post-12636";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 27 Aug 2009 01:20: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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:35:"12636@http://wordpress.org/plugins/";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:131:"An easy and powerful form builder that lets your visitors send you email. Blocks all automated spammers. No templates to mess with.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Mike Challis";s: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:45:"http://wordpress.org/plugins/rss/view/popular";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:4:"type";i:128;s:7:"headers";a:11:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Wed, 20 Aug 2014 22:26:18 GMT";s:12:"content-type";s:23:"text/xml; charset=UTF-8";s:10:"connection";s:5:"close";s:4:"vary";s:15:"Accept-Encoding";s:7:"expires";s:29:"Wed, 20 Aug 2014 22:43:11 GMT";s:13:"cache-control";s:0:"";s:6:"pragma";s:0:"";s:13:"last-modified";s:31:"Wed, 20 Aug 2014 22:08:11 +0000";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 250";}s:5:"build";s:14:"20140820222237";}', 'no'), (125, '_transient_timeout_feed_mod_b9388c83948825c1edaef0d856b7b109', '1408616778', 'no'), (126, '_transient_feed_mod_b9388c83948825c1edaef0d856b7b109', '1408573578', 'no'), (127, '_transient_timeout_plugin_slugs', '1408659978', 'no'), (128, '_transient_plugin_slugs', 'a:2:{i:0;s:19:"akismet/akismet.php";i:1;s:9:"hello.php";}', 'no'), (129, '_transient_timeout_dash_4077549d03da2e451c8b5f002294ff51', '1408616778', 'no'), (130, '_transient_dash_4077549d03da2e451c8b5f002294ff51', '
  • WordPress 4.0 Beta 4 August 15, 2014
    The fourth and likely final beta for WordPress 4.0 is now available. We’ve made more than 250 changes in the past month, including: Further improvements to the editor scrolling experience, especially when it comes to the second column of boxes. Better handling of small screens in the media library modals. A separate bulk selection mode […]
', 'no'), (131, 'can_compress_scripts', '1', 'yes'), (132, 'category_children', 'a:0:{}', 'yes'); -- -------------------------------------------------------- -- -- Table structure for table `postmeta` -- CREATE TABLE `postmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `post_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `postmeta` -- INSERT INTO `postmeta` (`meta_id`, `post_id`, `meta_key`, `meta_value`) VALUES (1, 2, '_wp_page_template', 'default'), (2, 2, 'username', 'juniorgrossi'), (3, 1, '_edit_lock', '1408573770:1'), (4, 1, '_edit_last', '1'), (6, 2, '_edit_lock', '1408573916:1'), (21, 10, 'username', 'juniorgrossi'), (8, 2, 'url', 'http://grossi.io'), (9, 1, 'username', 'juniorgrossi'), (10, 1, 'url', 'http://grossi.io'), (11, 5, 'username', 'juniorgrossi'), (12, 5, 'url', 'http://grossi.io'), (13, 6, 'username', 'juniorgrossi'), (14, 6, 'url', 'http://grossi.io'), (15, 7, 'username', 'juniorgrossi'), (16, 7, 'url', 'http://grossi.io'), (17, 8, 'username', 'juniorgrossi'), (18, 8, 'url', 'http://grossi.io'), (19, 9, 'username', 'juniorgrossi'), (20, 9, 'url', 'http://grossi.io'), (22, 10, 'url', 'http://grossi.io'), (23, 11, 'username', 'juniorgrossi'), (24, 11, 'url', 'http://grossi.io'), (25, 12, 'username', 'juniorgrossi'), (26, 12, 'url', 'http://grossi.io'), (27, 13, 'username', 'juniorgrossi'), (28, 13, 'url', 'http://grossi.io'), (29, 14, 'username', 'juniorgrossi'), (30, 14, 'url', 'http://grossi.io'), (31, 15, 'username', 'juniorgrossi'), (32, 15, 'url', 'http://grossi.io'), (33, 16, '_menu_item_type', 'post_type'), (34, 16, '_menu_item_menu_item_parent', '0'), (35, 16, '_menu_item_object_id', '2'), (36, 16, '_menu_item_object', 'page'), (37, 16, '_menu_item_target', ''), (38, 16, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (39, 16, '_menu_item_xfn', ''), (40, 16, '_menu_item_url', ''), (41, 17, '_menu_item_type', 'post_type'), (42, 17, '_menu_item_menu_item_parent', '16'), (43, 17, '_menu_item_object_id', '1'), (44, 17, '_menu_item_object', 'post'), (45, 17, '_menu_item_target', ''), (46, 17, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (47, 17, '_menu_item_xfn', ''), (48, 17, '_menu_item_url', ''), (49, 18, '_menu_item_type', 'custom'), (50, 18, '_menu_item_menu_item_parent', '0'), (51, 18, '_menu_item_object_id', '18'), (52, 18, '_menu_item_object', 'custom'), (53, 18, '_menu_item_target', ''), (54, 18, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (55, 18, '_menu_item_xfn', ''), (56, 18, '_menu_item_url', 'http://google.com'); -- -------------------------------------------------------- -- -- Table structure for table `posts` -- CREATE TABLE `posts` ( `ID` bigint(20) UNSIGNED NOT NULL, `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 NOT NULL, `post_title` text NOT NULL, `post_excerpt` text NOT NULL, `post_status` varchar(20) NOT NULL DEFAULT 'publish', `comment_status` varchar(20) NOT NULL DEFAULT 'open', `ping_status` varchar(20) NOT NULL DEFAULT 'open', `post_password` varchar(20) NOT NULL DEFAULT '', `post_name` varchar(200) NOT NULL DEFAULT '', `to_ping` text NOT NULL, `pinged` text 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 NOT NULL, `post_parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `guid` varchar(255) NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `posts` -- INSERT INTO `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, '2014-08-20 22:25:54', '2014-08-20 22:25:54', 'Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2014-08-20 22:30:27', '2014-08-20 22:30:27', '', 0, 'http://localhost:8000/?p=1', 0, 'post', '', 1), (2, 1, '2014-08-20 22:25:54', '2014-08-20 22:25:54', 'This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:\n\n
Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my blog. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)
\n\n...or something like this:\n\n
The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.
\n\nAs a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!', 'Sample Page', '', 'publish', 'open', 'open', '', 'sample-page', '', '', '2014-08-20 22:25:54', '2014-08-20 22:25:54', '', 0, 'http://localhost:8000/?page_id=2', 0, 'page', '', 0), (3, 1, '2014-08-20 22:26:13', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2014-08-20 22:26:13', '0000-00-00 00:00:00', '', 0, 'http://localhost:8000/?p=3', 0, 'post', '', 0), (4, 1, '2014-08-20 22:30:27', '2014-08-20 22:30:27', 'Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!', 'Hello world!', '', 'inherit', 'open', 'open', '', '1-revision-v1', '', '', '2014-08-20 22:30:27', '2014-08-20 22:30:27', '', 1, 'http://localhost:8000/?p=4', 0, 'revision', '', 0), (5, 0, '2014-08-20 19:34:59', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:34:59', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (6, 0, '2014-08-20 19:35:55', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:35:55', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (7, 0, '2014-08-20 19:37:21', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:37:21', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (8, 0, '2014-08-20 19:38:13', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:38:13', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (9, 0, '2014-08-20 19:39:00', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:39:00', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (10, 0, '2014-08-20 19:40:07', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:40:07', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (11, 0, '2014-08-20 19:42:05', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:42:05', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (12, 0, '2014-08-20 19:42:31', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:42:31', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (13, 0, '2014-08-20 19:43:18', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:43:18', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (14, 0, '2014-08-20 19:43:34', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:43:34', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (15, 0, '2014-08-20 19:44:52', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:44:52', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (16, 1, '2015-09-13 12:56:55', '2015-09-13 12:56:55', ' ', '', '', 'publish', 'closed', 'closed', '', '16', '', '', '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 0, 'http://site.vagrant/admin/?p=5', 1, 'nav_menu_item', '', 0), (17, 1, '2015-09-13 12:56:55', '2015-09-13 12:56:55', ' ', '', '', 'publish', 'closed', 'closed', '', '17', '', '', '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 0, 'http://site.vagrant/admin/?p=6', 2, 'nav_menu_item', '', 0), (18, 1, '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 'Google', '', 'publish', 'closed', 'closed', '', 'google', '', '', '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 0, 'http://site.vagrant/admin/?p=7', 3, 'nav_menu_item', '', 0); -- -------------------------------------------------------- -- -- Table structure for table `terms` -- CREATE TABLE `terms` ( `term_id` bigint(20) UNSIGNED NOT NULL, `name` varchar(200) NOT NULL DEFAULT '', `slug` varchar(200) NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `terms` -- INSERT INTO `terms` (`term_id`, `name`, `slug`, `term_group`) VALUES (1, 'Uncategorized', 'uncategorized', 0), (2, 'php', 'php', 0), (3, 'Menu1', 'menu1', 0); -- -------------------------------------------------------- -- -- Table structure for table `term_relationships` -- CREATE TABLE `term_relationships` ( `object_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `term_relationships` -- INSERT INTO `term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES (1, 2, 0), (16, 3, 0), (17, 3, 0), (18, 3, 0); -- -------------------------------------------------------- -- -- Table structure for table `term_taxonomy` -- CREATE TABLE `term_taxonomy` ( `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL, `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `taxonomy` varchar(32) NOT NULL DEFAULT '', `description` longtext NOT NULL, `parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `count` bigint(20) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `term_taxonomy` -- INSERT INTO `term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES (1, 1, 'category', '', 0, 0), (2, 2, 'category', '', 0, 1), (3, 3, 'nav_menu', '', 0, 3), (4, 0, '', '', 0, 0); -- -------------------------------------------------------- -- -- Table structure for table `usermeta` -- CREATE TABLE `usermeta` ( `umeta_id` bigint(20) UNSIGNED NOT NULL, `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) DEFAULT NULL, `meta_value` longtext ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `usermeta` -- INSERT INTO `usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (1, 1, 'first_name', ''), (2, 1, 'last_name', ''), (3, 1, 'nickname', 'admin'), (4, 1, 'description', ''), (5, 1, 'rich_editing', 'true'), (6, 1, 'comment_shortcuts', 'false'), (7, 1, 'admin_color', 'fresh'), (8, 1, 'use_ssl', '0'), (9, 1, 'show_admin_bar_front', 'true'), (10, 1, 'wp_capabilities', 'a:1:{s:13:"administrator";b:1;}'), (11, 1, 'wp_user_level', '10'), (12, 1, 'dismissed_wp_pointers', 'wp350_media,wp360_revisions,wp360_locks,wp390_widgets'), (13, 1, 'show_welcome_panel', '1'), (14, 1, 'wp_user-settings', 'libraryContent=browse&wplink=0&mfold=o&editor=tinymce&hidetb=1'), (15, 1, 'wp_user-settings-time', '1408573568'), (16, 1, 'wp_dashboard_quick_press_last_post_id', '3'), (17, 2, 'wp_capabilities', 'a:1:{s:13:"administrator";b:1;}'), (18, 2, 'wp_user_level', '10'), (19, 3, 'active', '1'), (20, 4, 'active', '1'), (21, 5, 'active', '1'), (22, 6, 'active', '1'), (23, 7, 'active', '1'), (24, 8, 'active', '1'), (25, 9, 'active', '1'), (26, 10, 'active', '1'), (27, 11, 'active', '1'), (28, 12, 'active', '1'), (29, 13, 'active', '1'), (30, 14, 'active', '1'), (31, 15, 'active', '1'), (32, 16, 'active', '1'), (33, 17, 'active', '1'), (34, 18, 'active', '1'), (35, 19, 'active', '1'), (36, 20, 'active', '1'), (37, 21, 'active', '1'), (38, 22, 'active', '1'), (39, 23, 'active', '1'), (40, 24, 'active', '1'), (41, 25, 'active', '1'), (42, 26, 'active', '1'), (43, 27, 'active', '1'), (44, 28, 'active', '1'), (45, 29, 'active', '1'), (46, 30, 'active', '1'), (47, 31, 'active', '1'), (48, 32, 'active', '1'), (49, 33, 'active', '1'), (50, 34, 'active', '1'), (51, 35, 'active', '1'), (52, 36, 'active', '1'), (53, 37, 'active', '1'), (54, 38, 'active', '1'), (55, 39, 'active', '1'), (56, 40, 'active', '1'), (57, 41, 'active', '1'), (58, 42, 'active', '1'), (59, 43, 'active', '1'), (60, 44, 'active', '1'), (61, 45, 'active', '1'), (62, 46, 'active', '1'), (63, 47, 'active', '1'), (64, 48, 'active', '1'), (65, 49, 'active', '1'), (66, 50, 'active', '1'), (67, 51, 'active', '1'), (68, 52, 'active', '1'), (69, 53, 'active', '1'), (70, 54, 'active', '1'), (71, 55, 'active', '1'), (72, 56, 'active', '1'), (73, 57, 'active', '1'), (74, 58, 'active', '1'), (75, 59, 'active', '1'), (76, 60, 'active', '1'), (77, 61, 'active', '1'), (78, 62, 'active', '1'), (79, 63, 'active', '1'), (80, 64, 'active', '1'), (81, 65, 'active', '1'), (82, 66, 'active', '1'), (83, 67, 'active', '1'), (84, 68, 'active', '1'), (85, 69, 'active', '1'), (86, 70, 'active', '1'), (87, 71, 'active', '1'), (88, 72, 'active', '1'), (89, 73, 'active', '1'), (90, 74, 'active', '1'), (91, 75, 'active', '1'), (92, 76, 'active', '1'), (93, 77, 'active', '1'), (94, 78, 'active', '1'), (95, 79, 'active', '1'), (96, 80, 'active', '1'), (97, 81, 'active', '1'), (98, 82, 'active', '1'), (99, 83, 'active', '1'), (100, 84, 'active', '1'), (101, 85, 'active', '1'), (102, 86, 'active', '1'), (103, 87, 'active', '1'), (104, 88, 'active', '1'), (105, 89, 'active', '1'), (106, 90, 'active', '1'), (107, 91, 'active', '1'), (108, 92, 'active', '1'), (109, 93, 'active', '1'), (110, 94, 'active', '1'), (111, 95, 'active', '1'), (112, 96, 'active', '1'), (113, 97, 'active', '1'), (114, 98, 'active', '1'), (115, 107, 'active', '1'), (116, 127, 'active', '1'), (117, 128, 'active', '1'), (118, 129, 'active', '1'), (119, 130, 'active', '1'), (120, 131, 'active', '1'), (121, 133, 'active', '1'), (122, 134, 'active', '1'), (123, 135, 'active', '1'), (124, 136, 'active', '1'), (125, 137, 'active', '1'), (126, 139, 'active', '1'), (127, 140, 'active', '1'), (128, 141, 'active', '1'), (129, 142, 'active', '1'), (130, 143, 'active', '1'), (131, 144, 'active', '1'), (132, 145, 'active', '1'), (133, 146, 'active', '1'), (134, 147, 'active', '1'), (135, 148, 'active', '1'), (136, 149, 'active', '1'), (137, 150, 'active', '1'), (138, 151, 'active', '1'), (139, 152, 'active', '1'), (140, 153, 'active', '1'), (141, 154, 'active', '1'), (142, 155, 'active', '1'), (143, 156, 'active', '1'), (144, 157, 'active', '1'), (145, 158, 'active', '1'), (146, 159, 'active', '1'), (147, 160, 'active', '1'), (148, 161, 'active', '1'), (149, 162, 'active', '1'), (150, 163, 'active', '1'), (151, 164, 'active', '1'), (152, 165, 'active', '1'), (153, 166, 'active', '1'), (154, 167, 'active', '1'), (155, 168, 'active', '1'); -- -------------------------------------------------------- -- -- Table structure for table `users` -- CREATE TABLE `users` ( `ID` bigint(20) UNSIGNED NOT NULL, `user_login` varchar(60) NOT NULL DEFAULT '', `user_pass` varchar(64) NOT NULL DEFAULT '', `user_nicename` varchar(50) NOT NULL DEFAULT '', `user_email` varchar(100) NOT NULL DEFAULT '', `user_url` varchar(100) NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(60) NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT '0', `display_name` varchar(250) NOT NULL DEFAULT '' ) ENGINE=MyISAM DEFAULT CHARSET=utf8; -- -- Dumping data for table `users` -- INSERT INTO `users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES (1, 'admin', '$P$B2Lceeosw6Md2kOTwY1QAOq0XPG7kl.', 'admin', 'juniorgro@gmail.com', '', '2014-08-20 22:25:54', '', 0, 'admin'), (2, 'testuser', '$P$B3XVcWLhmJ49k38ZJAf3ckouIIl1xZ.', 'testuser', 'testuser@gmail.com', '', '2015-08-20 22:25:54', '', 0, 'testuser'), (3, 'test', '', '', '', '', '2016-03-17 16:11:06', '', 0, ''), (4, 'test', '', '', '', '', '2016-03-17 16:13:53', '', 0, ''), (5, 'test', '', '', '', '', '2016-03-17 16:18:06', '', 0, ''), (6, 'test', '', '', '', '', '2016-03-17 16:21:53', '', 0, ''), (7, 'test', '', '', '', '', '2016-03-17 16:23:29', '', 0, ''), (8, 'test', '', '', '', '', '2016-03-17 16:23:56', '', 0, ''), (9, 'test', '', '', '', '', '2016-03-17 16:24:52', '', 0, ''), (10, 'test', '', '', '', '', '2016-03-17 16:25:25', '', 0, ''), (11, 'test', '', '', '', '', '2016-03-17 16:25:43', '', 0, ''), (12, 'test', '', '', '', '', '2016-03-17 16:26:38', '', 0, ''), (13, 'test', '', '', '', '', '2016-03-17 16:26:59', '', 0, ''), (14, 'test', '', '', '', '', '2016-03-17 16:27:39', '', 0, ''), (15, 'test', '', '', '', '', '2016-03-17 16:28:25', '', 0, ''), (16, 'test', '', '', '', '', '2016-03-17 16:28:44', '', 0, ''), (17, 'test', '', '', '', '', '2016-03-17 16:28:58', '', 0, ''), (18, 'test', '', '', '', '', '2016-03-17 16:30:18', '', 0, ''), (19, 'test', '', '', '', '', '2016-03-17 16:30:53', '', 0, ''), (20, 'test', '', '', '', '', '2016-03-17 16:31:05', '', 0, ''), (21, 'test', '', '', '', '', '2016-03-17 16:31:16', '', 0, ''), (22, 'test', '', '', '', '', '2016-03-17 16:34:10', '', 0, ''), (23, 'test', '', '', '', '', '2016-03-17 16:34:40', '', 0, ''), (24, 'test', '', '', '', '', '2016-03-17 16:38:14', '', 0, ''), (25, 'test', '', '', '', '', '2016-04-19 19:05:16', '', 0, ''), (26, 'test', '', '', '', '', '2016-04-19 19:05:20', '', 0, ''), (27, 'test', '', '', '', '', '2016-04-19 19:05:24', '', 0, ''), (28, 'test', '', '', '', '', '2016-04-19 19:45:42', '', 0, ''), (29, 'test', '', '', '', '', '2016-04-29 17:45:28', '', 0, ''), (30, 'test', '', '', '', '', '2016-04-29 17:52:07', '', 0, ''), (31, 'test', '', '', '', '', '2016-04-29 17:52:35', '', 0, ''), (32, 'test', '', '', '', '', '2016-04-29 17:53:40', '', 0, ''), (33, 'test', '', '', '', '', '2016-04-29 17:54:40', '', 0, ''), (34, 'test', '', '', '', '', '2016-04-29 17:54:51', '', 0, ''), (35, 'test', '', '', '', '', '2016-04-29 17:55:07', '', 0, ''), (36, 'test', '', '', '', '', '2016-04-29 17:56:25', '', 0, ''), (37, 'test', '', '', '', '', '2016-04-29 17:56:35', '', 0, ''), (38, 'test', '', '', '', '', '2016-04-29 17:57:09', '', 0, ''), (39, 'test', '', '', '', '', '2016-04-29 17:57:25', '', 0, ''), (40, 'test', '', '', '', '', '2016-04-29 17:58:05', '', 0, ''), (41, 'test', '', '', '', '', '2016-04-29 17:58:12', '', 0, ''), (42, 'test', '', '', '', '', '2016-04-29 17:58:31', '', 0, ''), (43, 'test', '', '', '', '', '2016-04-29 17:58:47', '', 0, ''), (44, 'test', '', '', '', '', '2016-04-29 17:59:23', '', 0, ''), (45, 'test', '', '', '', '', '2016-04-29 17:59:47', '', 0, ''), (46, 'test', '', '', '', '', '2016-04-29 17:59:51', '', 0, ''), (47, 'test', '', '', '', '', '2016-04-29 18:00:07', '', 0, ''), (48, 'test', '', '', '', '', '2016-04-29 18:00:47', '', 0, ''), (49, 'test', '', '', '', '', '2016-04-29 18:03:10', '', 0, ''), (50, 'test', '', '', '', '', '2016-04-29 18:03:26', '', 0, ''), (51, 'test', '', '', '', '', '2016-04-29 18:03:43', '', 0, ''), (52, 'test', '', '', '', '', '2016-04-29 18:03:49', '', 0, ''), (53, 'test', '', '', '', '', '2016-04-29 18:06:17', '', 0, ''), (54, 'test', '', '', '', '', '2016-04-29 18:09:08', '', 0, ''), (55, 'test', '', '', '', '', '2016-04-29 18:47:21', '', 0, ''), (56, 'test', '', '', '', '', '2016-04-29 18:56:20', '', 0, ''), (57, 'test', '', '', '', '', '2016-04-29 19:04:37', '', 0, ''), (58, 'test', '', '', '', '', '2016-04-29 19:11:41', '', 0, ''), (59, 'test', '', '', '', '', '2016-05-02 22:38:05', '', 0, ''), (60, 'test', '', '', '', '', '2016-05-04 19:11:53', '', 0, ''), (61, 'test', '', '', '', '', '2016-08-22 16:02:31', '', 0, ''), (62, 'test', '', '', '', '', '2016-08-22 16:04:26', '', 0, ''), (63, 'test', '', '', '', '', '2016-08-22 16:06:20', '', 0, ''), (64, 'test', '', '', '', '', '2016-08-22 16:27:45', '', 0, ''), (65, 'test', '', '', '', '', '2016-08-22 16:28:22', '', 0, ''), (66, 'test', '', '', '', '', '2016-08-22 16:28:42', '', 0, ''), (67, 'test', '', '', '', '', '2016-08-22 16:29:06', '', 0, ''), (68, 'test', '', '', '', '', '2016-08-22 16:29:16', '', 0, ''), (69, 'test', '', '', '', '', '2016-08-22 16:29:39', '', 0, ''), (70, 'test', '', '', '', '', '2016-08-22 16:30:47', '', 0, ''), (71, 'test', '', '', '', '', '2016-08-22 16:31:00', '', 0, ''), (72, 'test', '', '', '', '', '2016-08-22 16:31:05', '', 0, ''), (73, 'test', '', '', '', '', '2016-08-22 16:31:45', '', 0, ''), (74, 'test', '', '', '', '', '2016-08-22 16:32:25', '', 0, ''), (75, 'test', '', '', '', '', '2016-10-03 10:23:40', '', 0, ''), (76, 'test', '', '', '', '', '2016-10-03 10:32:39', '', 0, ''), (77, 'test', '', '', '', '', '2016-10-03 10:37:49', '', 0, ''), (78, 'test', '', '', '', '', '2016-10-07 12:11:51', '', 0, ''), (79, 'test', '', '', '', '', '2016-10-12 18:35:39', '', 0, ''), (80, 'test', '', '', '', '', '2016-10-12 18:35:51', '', 0, ''), (81, 'test', '', '', '', '', '2016-10-12 18:39:15', '', 0, ''), (82, 'test', '', '', '', '', '2016-10-12 18:48:17', '', 0, ''), (83, 'test', '', '', '', '', '2016-10-12 18:48:38', '', 0, ''), (84, 'test', '', '', '', '', '2016-10-12 18:51:12', '', 0, ''), (85, 'test', '', '', '', '', '2016-10-12 18:51:28', '', 0, ''), (86, 'test', '', '', '', '', '2016-10-12 18:52:05', '', 0, ''), (87, 'test', '', '', '', '', '2016-10-12 18:52:15', '', 0, ''), (88, 'test', '', '', '', '', '2016-10-12 18:52:21', '', 0, ''), (89, 'test', '', '', '', '', '2016-10-12 18:53:44', '', 0, ''), (90, 'test', '', '', '', '', '2016-10-12 18:55:52', '', 0, ''), (91, 'test', '', '', '', '', '2016-10-12 18:56:00', '', 0, ''), (92, 'test', '', '', '', '', '2016-10-12 19:09:09', '', 0, ''), (93, 'test', '', '', '', '', '2016-10-12 19:19:21', '', 0, ''), (94, 'test', '', '', '', '', '2016-10-17 22:15:53', '', 0, ''), (95, 'test', '', '', '', '', '2016-10-17 22:16:26', '', 0, ''), (96, 'test', '', '', '', '', '2016-10-17 22:43:59', '', 0, ''), (97, 'test', '', '', '', '', '2016-11-12 22:40:28', '', 0, ''), (98, 'test', '', '', '', '', '2016-11-12 23:00:33', '', 0, ''), (99, 'test', '', '', '', '', '2016-12-06 19:28:59', '', 0, ''), (100, 'test', '', '', '', '', '2016-12-06 19:29:20', '', 0, ''), (101, 'test', '', '', '', '', '2016-12-06 19:29:33', '', 0, ''), (102, 'test', '', '', '', '', '2016-12-06 19:32:17', '', 0, ''), (103, 'test', '', '', '', '', '2016-12-06 19:32:31', '', 0, ''), (104, 'test', '', '', '', '', '2016-12-06 19:33:55', '', 0, ''), (105, 'test', '', '', '', '', '2016-12-06 19:37:17', '', 0, ''), (106, 'test', '', '', '', '', '2016-12-06 19:38:48', '', 0, ''), (107, 'test', '', '', '', '', '2016-12-06 19:54:31', '', 0, ''), (108, 'test', '', '', '', '', '2017-01-23 21:43:38', '', 0, ''), (109, 'test', '', '', '', '', '2017-01-23 21:44:53', '', 0, ''), (110, 'test', '', '', '', '', '2017-01-23 21:48:14', '', 0, ''), (111, 'test', '', '', '', '', '2017-01-23 21:49:23', '', 0, ''), (112, 'test', '', '', '', '', '2017-01-23 21:50:29', '', 0, ''), (113, 'test', '', '', '', '', '2017-01-23 21:51:57', '', 0, ''), (114, 'test', '', '', '', '', '2017-01-23 21:53:00', '', 0, ''), (115, 'test', '', '', '', '', '2017-01-26 10:54:15', '', 0, ''), (116, 'test', '', '', '', '', '2017-01-26 10:59:13', '', 0, ''), (117, 'test', '', '', '', '', '2017-01-31 16:54:34', '', 0, ''), (118, 'test', '', '', '', '', '2017-01-31 16:54:48', '', 0, ''), (119, 'test', '', '', '', '', '2017-01-31 16:55:43', '', 0, ''), (120, 'test', '', '', '', '', '2017-01-31 17:04:43', '', 0, ''), (121, 'test', '', '', '', '', '2017-01-31 17:06:11', '', 0, ''), (122, 'test', '', '', '', '', '2017-01-31 17:06:25', '', 0, ''), (123, 'test', '', '', '', '', '2017-01-31 17:06:57', '', 0, ''), (124, 'test', '', '', '', '', '2017-01-31 17:14:38', '', 0, ''), (125, 'test', '', '', '', '', '2017-01-31 17:31:02', '', 0, ''), (126, 'test', '', '', '', '', '2017-01-31 17:31:11', '', 0, ''), (127, 'test', '', '', '', '', '2017-01-31 17:31:40', '', 0, ''), (128, 'test', '', '', '', '', '2017-01-31 17:32:24', '', 0, ''), (129, 'test', '', '', '', '', '2017-01-31 17:32:49', '', 0, ''), (130, 'test', '', '', '', '', '2017-01-31 17:33:17', '', 0, ''), (131, 'test', '', '', '', '', '2017-01-31 17:43:28', '', 0, ''), (132, 'test', '', '', '', '', '2017-01-31 17:48:05', '', 0, ''), (133, 'test', '', '', '', '', '2017-01-31 17:53:57', '', 0, ''), (134, 'test', '', '', '', '', '2017-01-31 17:54:40', '', 0, ''), (135, 'test', '', '', '', '', '2017-01-31 17:56:06', '', 0, ''), (136, 'test', '', '', '', '', '2017-01-31 17:56:27', '', 0, ''), (137, 'test', '', '', '', '', '2017-01-31 17:56:47', '', 0, ''), (138, 'test', '', '', '', '', '2017-01-31 17:57:16', '', 0, ''), (139, 'test', '', '', '', '', '2017-01-31 17:58:50', '', 0, ''), (140, 'test', '', '', '', '', '2017-01-31 18:06:36', '', 0, ''), (141, 'test', '', '', '', '', '2017-01-31 18:07:59', '', 0, ''), (142, 'test', '', '', '', '', '2017-01-31 18:08:47', '', 0, ''), (143, 'test', '', '', '', '', '2017-01-31 18:09:38', '', 0, ''), (144, 'test', '', '', '', '', '2017-01-31 18:10:47', '', 0, ''), (145, 'test', '', '', '', '', '2017-01-31 18:11:51', '', 0, ''), (146, 'test', '', '', '', '', '2017-01-31 18:12:08', '', 0, ''), (147, 'test', '', '', '', '', '2017-01-31 18:12:26', '', 0, ''), (148, 'test', '', '', '', '', '2017-01-31 18:12:51', '', 0, ''), (149, 'test', '', '', '', '', '2017-02-01 16:56:37', '', 0, ''), (150, 'test', '', '', '', '', '2017-02-01 16:57:48', '', 0, ''), (151, 'test', '', '', '', '', '2017-02-01 17:00:32', '', 0, ''), (152, 'test', '', '', '', '', '2017-02-01 17:01:08', '', 0, ''), (153, 'test', '', '', '', '', '2017-02-01 17:01:20', '', 0, ''), (154, 'test', '', '', '', '', '2017-02-01 17:01:39', '', 0, ''), (155, 'test', '', '', '', '', '2017-02-01 17:02:50', '', 0, ''), (156, 'test', '', '', '', '', '2017-02-01 17:06:50', '', 0, ''), (157, 'test', '', '', '', '', '2017-02-01 17:07:46', '', 0, ''), (158, 'test', '', '', '', '', '2017-06-14 14:15:05', '', 0, ''), (159, 'test', '', '', '', '', '2017-06-14 14:25:40', '', 0, ''), (160, 'test', '', '', '', '', '2017-06-20 12:19:23', '', 0, ''), (161, 'test', '', '', '', '', '2017-06-20 12:33:49', '', 0, ''), (162, 'test', '', '', '', '', '2017-06-20 12:38:47', '', 0, ''), (163, 'test', '', '', '', '', '2017-06-20 12:39:18', '', 0, ''), (164, 'test', '', '', '', '', '2017-06-20 12:39:43', '', 0, ''), (165, 'test', '', '', '', '', '2017-06-20 12:41:44', '', 0, ''), (166, 'test', '', '', '', '', '2017-06-20 12:42:58', '', 0, ''), (167, 'test', '', '', '', '', '2017-06-20 12:43:23', '', 0, ''), (168, 'test', '', '', '', '', '2017-06-20 12:43:44', '', 0, ''); -- -------------------------------------------------------- -- -- Table structure for table `wp_commentmeta` -- CREATE TABLE `wp_commentmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `comment_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `wp_comments` -- CREATE TABLE `wp_comments` ( `comment_ID` bigint(20) UNSIGNED NOT NULL, `comment_post_ID` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `comment_author` text COLLATE utf8mb4_unicode_ci NOT NULL, `comment_author_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_author_url` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `comment_content` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `comment_karma` int(11) NOT NULL DEFAULT '0', `comment_approved` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '1', `comment_agent` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- 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, 'Mr WordPress', '', 'https://wordpress.org/', '', '2014-08-20 22:25:54', '2014-08-20 22:25:54', 'Hi, this is a comment.\nTo delete a comment, just log in and view the post's comments. There you will have the option to edit or delete them.', 0, '1', '', '', 0, 0), (2, 1, 'Test Author', '', 'https://wordpress.org/', '', '2014-08-21 22:25:54', '2014-08-21 22:25:54', 'test reply', 0, '1', '', '', 1, 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_links` -- CREATE TABLE `wp_links` ( `link_id` bigint(20) UNSIGNED NOT NULL, `link_url` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_image` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_target` varchar(25) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_description` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_visible` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'Y', `link_owner` bigint(20) UNSIGNED NOT NULL DEFAULT '1', `link_rating` int(11) NOT NULL DEFAULT '0', `link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `link_rel` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `link_notes` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `link_rss` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -------------------------------------------------------- -- -- Table structure for table `wp_options` -- CREATE TABLE `wp_options` ( `option_id` bigint(20) UNSIGNED NOT NULL, `option_name` varchar(191) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `option_value` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `autoload` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'yes' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_options` -- INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (1, 'siteurl', 'http://localhost:8000', 'yes'), (2, 'blogname', 'Wordpress Corcel', 'yes'), (3, 'blogdescription', 'Just another WordPress site', 'yes'), (4, 'users_can_register', '0', 'yes'), (5, 'admin_email', 'juniorgro@gmail.com', 'yes'), (6, 'start_of_week', '1', 'yes'), (7, 'use_balanceTags', '0', 'yes'), (8, 'use_smilies', '1', 'yes'), (9, 'require_name_email', '1', 'yes'), (10, 'comments_notify', '1', 'yes'), (11, 'posts_per_rss', '10', 'yes'), (12, 'rss_use_excerpt', '0', 'yes'), (13, 'mailserver_url', 'mail.example.com', 'yes'), (14, 'mailserver_login', 'login@example.com', 'yes'), (15, 'mailserver_pass', 'password', 'yes'), (16, 'mailserver_port', '110', 'yes'), (17, 'default_category', '1', 'yes'), (18, 'default_comment_status', 'open', 'yes'), (19, 'default_ping_status', 'open', 'yes'), (20, 'default_pingback_flag', '0', 'yes'), (21, 'posts_per_page', '10', 'yes'), (22, 'date_format', 'F j, Y', 'yes'), (23, 'time_format', 'g:i a', 'yes'), (24, 'links_updated_date_format', 'F j, Y g:i a', 'yes'), (25, 'comment_moderation', '0', 'yes'), (26, 'moderation_notify', '1', 'yes'), (27, 'permalink_structure', '', 'yes'), (29, 'hack_file', '0', 'yes'), (30, 'blog_charset', 'UTF-8', 'yes'), (31, 'moderation_keys', '', 'no'), (32, 'active_plugins', 'a:0:{}', 'yes'), (33, 'home', 'http://localhost:8000', 'yes'), (34, 'category_base', '', 'yes'), (35, 'ping_sites', 'http://rpc.pingomatic.com/', 'yes'), (37, 'comment_max_links', '2', 'yes'), (38, 'gmt_offset', '0', 'yes'), (39, 'default_email_category', '1', 'yes'), (40, 'recently_edited', '', 'no'), (41, 'template', 'twentyseventeen', 'yes'), (42, 'stylesheet', 'twentyseventeen', 'yes'), (43, 'comment_whitelist', '1', 'yes'), (44, 'blacklist_keys', '', 'no'), (45, 'comment_registration', '0', 'yes'), (46, 'html_type', 'text/html', 'yes'), (47, 'use_trackback', '0', 'yes'), (48, 'default_role', 'subscriber', 'yes'), (49, 'db_version', '38590', 'yes'), (50, 'uploads_use_yearmonth_folders', '1', 'yes'), (51, 'upload_path', '', 'yes'), (52, 'blog_public', '0', 'yes'), (53, 'default_link_category', '2', 'yes'), (54, 'show_on_front', 'posts', 'yes'), (55, 'tag_base', '', 'yes'), (56, 'show_avatars', '1', 'yes'), (57, 'avatar_rating', 'G', 'yes'), (58, 'upload_url_path', '', 'yes'), (59, 'thumbnail_size_w', '150', 'yes'), (60, 'thumbnail_size_h', '150', 'yes'), (61, 'thumbnail_crop', '1', 'yes'), (62, 'medium_size_w', '300', 'yes'), (63, 'medium_size_h', '300', 'yes'), (64, 'avatar_default', 'mystery', 'yes'), (65, 'large_size_w', '1024', 'yes'), (66, 'large_size_h', '1024', 'yes'), (67, 'image_default_link_type', 'file', 'yes'), (68, 'image_default_size', '', 'yes'), (69, 'image_default_align', '', 'yes'), (70, 'close_comments_for_old_posts', '0', 'yes'), (71, 'close_comments_days_old', '14', 'yes'), (72, 'thread_comments', '1', 'yes'), (73, 'thread_comments_depth', '5', 'yes'), (74, 'page_comments', '0', 'yes'), (75, 'comments_per_page', '50', 'yes'), (76, 'default_comments_page', 'newest', 'yes'), (77, 'comment_order', 'asc', 'yes'), (78, 'sticky_posts', 'a:0:{}', 'yes'), (79, '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'), (80, 'widget_text', 'a:0:{}', 'yes'), (81, 'widget_rss', 'a:0:{}', 'yes'), (82, 'uninstall_plugins', 'a:0:{}', 'no'), (83, 'timezone_string', '', 'yes'), (84, 'page_for_posts', '0', 'yes'), (85, 'page_on_front', '0', 'yes'), (86, 'default_post_format', '0', 'yes'), (87, 'link_manager_enabled', '0', 'yes'), (88, 'initial_db_version', '27916', 'yes'), (89, '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'), (90, 'widget_search', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'), (91, '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'), (92, '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'), (93, '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'), (94, 'widget_meta', 'a:2:{i:2;a:1:{s:5:"title";s:0:"";}s:12:"_multiwidget";i:1;}', 'yes'), (95, 'sidebars_widgets', 'a:5:{s:19:"wp_inactive_widgets";a:0:{}s:9:"sidebar-1";a:6:{i:0;s:8:"search-2";i:1;s:14:"recent-posts-2";i:2;s:17:"recent-comments-2";i:3;s:10:"archives-2";i:4;s:12:"categories-2";i:5;s:6:"meta-2";}s:9:"sidebar-2";a:0:{}s:9:"sidebar-3";a:0:{}s:13:"array_version";i:3;}', 'yes'), (96, 'cron', 'a:3:{i:1497997561;a:3:{s:16:"wp_version_check";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:10:"twicedaily";s:4:"args";a:0:{}s:8:"interval";i:43200;}}s:17:"wp_update_plugins";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:10:"twicedaily";s:4:"args";a:0:{}s:8:"interval";i:43200;}}s:16:"wp_update_themes";a:1:{s:32:"40cd750bba9870f18aada2478b24840a";a:3:{s:8:"schedule";s:10:"twicedaily";s:4:"args";a:0:{}s:8:"interval";i:43200;}}}i:1497997572;a:1:{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:7:"version";i:2;}', 'yes'), (321, 'test_insert_5949175727063', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'), (322, 'test_insert_5949177593dcf', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'), (293, 'db_upgraded', '', 'yes'), (294, '_site_transient_update_core', 'O:8:"stdClass":4:{s:7:"updates";a:2:{i:0;O:8:"stdClass":10:{s:8:"response";s:7:"upgrade";s:8:"download";s:57:"https://downloads.wordpress.org/release/wordpress-4.8.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-4.8.zip";s:10:"no_content";s:68:"https://downloads.wordpress.org/release/wordpress-4.8-no-content.zip";s:11:"new_bundled";s:69:"https://downloads.wordpress.org/release/wordpress-4.8-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:3:"4.8";s:7:"version";s:3:"4.8";s:11:"php_version";s:5:"5.2.4";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"4.7";s:15:"partial_version";s:0:"";}i:1;O:8:"stdClass":11:{s:8:"response";s:10:"autoupdate";s:8:"download";s:57:"https://downloads.wordpress.org/release/wordpress-4.8.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-4.8.zip";s:10:"no_content";s:68:"https://downloads.wordpress.org/release/wordpress-4.8-no-content.zip";s:11:"new_bundled";s:69:"https://downloads.wordpress.org/release/wordpress-4.8-new-bundled.zip";s:7:"partial";b:0;s:8:"rollback";b:0;}s:7:"current";s:3:"4.8";s:7:"version";s:3:"4.8";s:11:"php_version";s:5:"5.2.4";s:13:"mysql_version";s:3:"5.0";s:11:"new_bundled";s:3:"4.7";s:15:"partial_version";s:0:"";s:9:"new_files";s:1:"1";}}s:12:"last_checked";i:1497961421;s:15:"version_checked";s:5:"4.7.5";s:12:"translations";a:0:{}}', 'no'), (105, '_transient_random_seed', '400d2c0e4869149f41fb458f4c5971c8', 'yes'), (106, 'auth_key', 'BzUGfHeSYf|2V5xlRqc[P#vwZ9u([Opee#o^ql5]+X.-y]y]=9DT9', 'yes'), (108, 'logged_in_key', '&s<1dV:~Is2{.@<>>;cK{|*j6MwqFTz0m|GsB a@(**6[6E3~HnG_(&j_+UX=eeq', 'yes'), (109, 'logged_in_salt', 'n!,pY9HWh@_rM+_]+$0A+E~`>epA:q-eig,Tv!0ld:iwNNCW!xDw-BdNlPrMtqv@', 'yes'), (110, 'nonce_key', '^>7lg-@IhAe76d<~&,yTB $}#hF]$T;V@lZIPE6(+barZ0D6BAn Update with You in Mind\n

\n

Gear up for a more intuitive WordPress!

\n

Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard. New features in 4.8 add more ways for you to express yourself and represent your brand.

\n

Though some updates seem minor, they’ve been built by hundreds of contributors with you in mind. Get ready for new features you’ll welcome like an old friend: link improvements, three new media widgets covering images, audio, and video, an updated text widget that supports visual editing, and an upgraded news section in your dashboard which brings in nearby and upcoming WordPress events.

\n
\n

Exciting Widget Updates

\n

\n

Image Widget

\n

Adding an image to a widget is now a simple task that is achievable for any WordPress user without needing to know code. Simply insert your image right within the widget settings. Try adding something like a headshot or a photo of your latest weekend adventure — and see it appear automatically.

\n

Video Widget

\n

A welcome video is a great way to humanize the branding of your website. You can now add any video from the Media Library to a sidebar on your site with the new Video widget. Use this to showcase a welcome video to introduce visitors to your site or promote your latest and greatest content.

\n

Audio Widget

\n

Are you a podcaster, musician, or avid blogger? Adding a widget with your audio file has never been easier. Upload your audio file to the Media Library, go to the widget settings, select your file, and you’re ready for listeners. This would be a easy way to add a more personal welcome message, too!

\n

Rich Text Widget

\n

This feature deserves a parade down the center of town! Rich-text editing capabilities are now native for Text widgets. Add a widget anywhere and format away. Create lists, add emphasis, and quickly and easily insert links. Have fun with your newfound formatting powers, and watch what you can accomplish in a short amount of time.

\n
\n

Link Boundaries

\n
\n

Have you ever tried updating a link, or the text around a link, and found you can’t seem to edit it correctly? When you edit the text after the link, your new text also ends up linked. Or you edit the text in the link, but your text ends up outside of it. This can be frustrating! With link boundaries, a great new feature, the process is streamlined and your links will work well. You’ll be happier. We promise.

\n
\n

Nearby WordPress Events

\n

\n

Did you know that WordPress has a thriving offline community with groups meeting regularly in more than 400 cities around the world? WordPress now draws your attention to the events that help you continue improving your WordPress skills, meet friends, and, of course, publish!

\n

This is quickly becoming one of our favorite features. While you are in the dashboard (because you’re running updates and writing posts, right?) all upcoming WordCamps and official WordPress Meetups — local to you — will be displayed.

\n

Being part of the community can help you improve your WordPress skills and network with people you wouldn’t otherwise meet. Now you can easily find your local events just by logging in to your dashboard and looking at the new Events and News dashboard widget.

\n
\n

Even More Developer Happiness 😊

\n

More Accessible Admin Panel Headings

\n

New CSS rules mean extraneous content (like “Add New” links) no longer need to be included in admin-area headings. These panel headings improve the experience for people using assistive technologies.

\n

Removal of Core Support for WMV and WMA Files

\n

As fewer and fewer browsers support Silverlight, file formats which require the presence of the Silverlight plugin are being removed from core support. Files will still display as a download link, but will no longer be embedded automatically.

\n

Multisite Updates

\n

New capabilities have been introduced to 4.8 with an eye towards removing calls to
\nis_super_admin(). Additionally, new hooks and tweaks to more granularly control site and user counts per network have been added.

\n

Text-Editor JavaScript API

\n

With the addition of TinyMCE to the text widget in 4.8 comes a new JavaScript API for instantiating the editor after page load. This can be used to add an editor instance to any text area, and customize it with buttons and functions. Great for plugin authors!

\n

Media Widgets API

\n

The introduction of a new base media widget REST API schema to 4.8 opens up possibilities for even more media widgets (like galleries or playlists) in the future. The three new media widgets are powered by a shared base class that covers most of the interactions with the media modal. That class also makes it easier to create new media widgets and paves the way for more to come.

\n

Customizer Width Variable

\n

Rejoice! New responsive breakpoints have been added to the customizer sidebar to make it wider on high-resolution screens. Customizer controls should use percentage-based widths instead of pixels.

\n
\n

The Squad

\n

This release was led by Matt and Jeff Paul, with the help of the following fabulous folks. There are 346 contributors with props in this release, with 106 of them contributing for the first time. Pull up some Bill Evans on your music service of choice, and check out some of their profiles:

\n[Inactive], Aaron 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, Antti Kuosmanen, apokalyptik, artoliukkonen, Arunas Liuiza, attitude, backermann, 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, Dipesh Kakadiya, 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, mageshp, Mahesh Waghmare, Mangesh Parte, Manish Songirkar, mantismamita, Marcel Bootsman, Marin Atanasov, Mario Valney, Marius L. J., Mark Jaquith, Mark Root-Wiley, Mark Uraine, Marko Heijnen, markshep, matrixik, Matt Banks, Matt Jaworski, Matt King, 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, 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, Vishal Kakadiya, vortfu, Vrunda Kansara, webbgaraget, WebMan Design | Oliver Juhas, websupporter, Weston Ruter, William Earnhardt, williampatton, Wolly aka Paolo Valenti, yale01, Yoav Farhi, Yoga Sukma, Zach Wills, Zack Tollman, Ze Fontainhas, zhildzik, and zsusag.\n

 

\n

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

\n

Do you want to report on WordPress 4.8? We’ve compiled a press kit featuring information about the release features, and some media assets to help you along.

\n

If you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress — we hope you enjoy!

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4770";s: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:33:"\n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:33:"WordPress 4.8 Release Candidate 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:69:"https://wordpress.org/news/2017/06/wordpress-4-8-release-candidate-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Jun 2017 22:13:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4765";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:336:"The second release candidate for WordPress 4.8 is now available. To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip). We’ve made a handful of changes since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Mel Choyce";s: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:1173:"

The second release candidate for WordPress 4.8 is now available.

\n

To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

\n

We’ve made a handful of changes since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the Beta 1, Beta 2, and RC1 blog posts.

\n

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

\n

Happy testing!

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4765";s: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:33:"\n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:31:"WordPress 4.8 Release Candidate";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:67:"https://wordpress.org/news/2017/05/wordpress-4-8-release-candidate/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 25 May 2017 23:04:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4758";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:325:"The release candidate for WordPress 4.8 is now available. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.8 on Thursday, June 8, but we need your help to get there. If you haven’t tested 4.8 yet, […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Mel Choyce";s: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:2365:"

The release candidate for WordPress 4.8 is now available.

\n

RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.8 on Thursday, June 8, but we need your help to get there. If you haven’t tested 4.8 yet, now is the time!

\n

To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

\n

We’ve made a handful of changes since releasing Beta 2 earlier this week. For more details about what’s new in version 4.8, check out the Beta 1 and Beta 2 blog posts.

\n

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

\n

Developers, please test your plugins and themes against WordPress 4.8 and update your plugin’s Tested up to version in the readme to 4.8. If you find compatibility problems please be sure to post to the support forums so we can figure those out before the final release – we work hard to avoid breaking things. An in-depth field guide to developer-focused changes is coming soon on the core development blog.

\n

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

\n

This release’s haiku is courtesy of @matveb:

\n

Érrese uno
\nCien veces y más
\nErre ce dos

\n

Thanks for your continued help testing out the latest versions of WordPress.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4758";s: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:33:"\n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.8 Beta 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2017/05/wordpress-4-8-beta-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 23 May 2017 00:02:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4749";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:329:"WordPress 4.8 Beta 2 is now available! This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.8, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Mel Choyce";s: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:1621:"

WordPress 4.8 Beta 2 is now available!

\n

This software is still in development, so we don’t recommend you run it on a production site. Consider setting up a test site just to play with the new version. To test WordPress 4.8, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the beta here (zip).

\n

For more information on what’s new in 4.8, check out the Beta 1 blog post. Since then, we’ve made over 50 changes in Beta 2.

\n

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

\n

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

\n

WordPress four point eight
\nOne step closer to release
\nPlease test Beta 2!

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4749";s: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:39:"\n \n \n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:48:"WordPress 4.7.5 Security and Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/news/2017/05/wordpress-4-7-5/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 16 May 2017 22:39:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4734";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:373:"WordPress 4.7.5 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7.4 and earlier are affected by six security issues: Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing. Improper handling of post meta data values in the XML-RPC […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Pascal Birchler";s: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:2349:"

WordPress 4.7.5 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

WordPress versions 4.7.4 and earlier are affected by six security issues:

\n
    \n
  1. Insufficient redirect validation in the HTTP class. Reported by Ronni Skansing.
    2. \n
  2. Improper handling of post meta data values in the XML-RPC API. Reported by Sam Thomas.
    3. \n
  3. Lack of capability checks for post meta data in the XML-RPC API. Reported by Ben Bidner of the WordPress Security Team.
    4. \n
  4. A Cross Site Request Forgery (CSRF)  vulnerability was discovered in the filesystem credentials dialog. Reported by Yorick Koster.
    5. \n
  5. A cross-site scripting (XSS) vulnerability was discovered when attempting to upload very large files. Reported by Ronni Skansing.
    6. \n
  6. A cross-site scripting (XSS) vulnerability was discovered related to the Customizer. Reported by Weston Ruter of the WordPress Security Team.
    7. \n
\n

Thank you to the reporters of these issues for practicing responsible disclosure.

\n

In addition to the security issues above, WordPress 4.7.5 contains 3 maintenance fixes to the 4.7 release series. For more information, see the release notes or consult the list of changes.

\n

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

\n

Thanks to everyone who contributed to 4.7.5.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4734";s: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:33:"\n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:26:"WordPress Now on HackerOne";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2017/05/wordpress-now-on-hackerone/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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 May 2017 16:02:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=4730";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:322:"WordPress has grown a lot over the last thirteen years – it now powers more than 28% of the top ten million sites on the web. During this growth, each team has worked hard to continually improve their tools and processes. Today, the WordPress Security Team is happy to announce that WordPress is now officially […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Aaron D. Campbell";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:1718:"

WordPress has grown a lot over the last thirteen years – it now powers more than 28% of the top ten million sites on the web. During this growth, each team has worked hard to continually improve their tools and processes. Today, the WordPress Security Team is happy to announce that WordPress is now officially on HackerOne!

\n

HackerOne is a platform for security researchers to securely and responsibly report vulnerabilities to our team. It provides tools that improve the quality and consistency of communication with reporters, and will reduce the time spent on responding to commonly reported issues. This frees our team to spend more time working on improving the security of WordPress.

\n

The security team has been working on this project for quite some time. Nikolay Bachiyski started the team working on it just over a year ago. We ran it as a private program while we worked out our procedures and processes, and are excited to finally make it public.

\n

With the announcement of the WordPress HackerOne program we are also introducing bug bounties. Bug bounties let us reward reporters for disclosing issues to us and helping us secure our products and infrastructure. We’ve already awarded more than $3,700 in bounties to seven different reporters! We are thankful to Automattic for paying the bounties on behalf of the WordPress project.

\n

The program and bounties cover all our projects including WordPress, BuddyPress, bbPress, GlotPress, and WP-CLI as well as all of our sites including WordPress.org, bbPress.org, WordCamp.org, BuddyPress.org, and GlotPress.org.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4730";s: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:33:"\n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"WordPress 4.8 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:"link";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/news/2017/05/wordpress-4-8-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:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Sat, 13 May 2017 00:15:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4727";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:342:"We’re planning a smaller WP release early next month, bringing in three major enhancements: An improved visual editor experience, with a new TinyMCE that allows you to navigate more intuitively in and out of inline elements like links. (Try it out to see, it’s hard to describe.) A revamp of the dashboard news widget to […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:1148:"

We’re planning a smaller WP release early next month, bringing in three major enhancements:

\n
    \n
  • An improved visual editor experience, with a new TinyMCE that allows you to navigate more intuitively in and out of inline elements like links. (Try it out to see, it’s hard to describe.)
    • \n
  • A revamp of the dashboard news widget to bring in nearby and upcoming events including meetups and WordCamps.
    • \n
  • Several new media widgets covering images, audio, and video, and an enhancement to the text widget to support visual editing.
    • \n
\n

The first beta of 4.8 is now available for testing. You can use the beta tester plugin (or just run trunk) to try the latest and greatest, and each of these areas could use a ton of testing. Our goals are to make editing posts with links more intuitive, make widgets easier for new users and more convenient for existing ones, and get many more people aware of and attending our community events.

\n

Four point eight is here
\nSmall changes with a big punch
\nBig ones come later

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4727";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:36:"\n \n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:35:"WordPress 4.7.4 Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/news/2017/04/wordpress-4-7-4/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Apr 2017 17:54:32 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:2:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:3:"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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4710";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:376:"After almost sixty million downloads of WordPress 4.7, we are pleased to announce the immediate availability of WordPress 4.7.4, a maintenance release. This release contains 47 bug fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST API.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:"Pascal Birchler";s: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:4518:"

After almost sixty million downloads of WordPress 4.7, we are pleased to announce the immediate availability of WordPress 4.7.4, a maintenance release.

\n

This release contains 47 maintenance fixes and enhancements, chief among them an incompatibility between the upcoming Chrome version and the visual editor, inconsistencies in media handling, and further improvements to the REST API. For a full list of changes, consult the release notes and the list of changes.

\n

Download WordPress 4.7.4 or visit Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.7.4.

\n

Thanks to everyone who contributed to 4.7.4:
\nAaron Jorbin, Adam Silverstein, Andrea Fercia, Andrew Ozz, aussieguy123, Blobfolio, boldwater, Boone Gorges, Boro Sitnikovski, chesio, Curdin Krummenacher, Daniel Bachhuber, Darren Ethier (nerrad), David A. Kennedy, davidbenton, David Herrera, Dion Hulse, Dominik Schilling (ocean90), eclev91, Ella Van Dorpe, Gustave F. Gerhardt, ig_communitysites, James Nylen, Joe Dolson, John Blackbourn, karinedo, lukasbesch, maguiar, MatheusGimenez, Matthew Boynes, Matt Wiebe, Mayur Keshwani, Mel Choyce, Nick Halsey, Pascal Birchler, Peter Wilson, Piotr Delawski, Pratik Shrestha, programmin, Rachel Baker, sagarkbhatt, Sagar Prajapati, sboisvert, Scott Taylor, Sergey Biryukov, Stephen Edgar, Sybre Waaijer, Timmy Crawford, vortfu, and Weston Ruter.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4710";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:48:"WordPress 4.7.3 Security and Maintenance Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:84:"https://wordpress.org/news/2017/03/wordpress-4-7-3-security-and-maintenance-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 06 Mar 2017 17:53:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4696";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:396:"WordPress 4.7.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7.2 and earlier are affected by six security issues: Cross-site scripting (XSS) via media file metadata.  Reported by Chris Andrè Dale, Yorick Koster, and Simon P. Briggs. Control characters can trick redirect […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:11:"James Nylen";s: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:6191:"

WordPress 4.7.3 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

WordPress versions 4.7.2 and earlier are affected by six security issues:

\n
    \n
  1. Cross-site scripting (XSS) via media file metadata.  Reported by Chris Andrè Dale, Yorick Koster, and Simon P. Briggs.
    2. \n
  2. Control characters can trick redirect URL validation.  Reported by Daniel Chatfield.
    3. \n
  3. Unintended files can be deleted by administrators using the plugin deletion functionality.  Reported by TrigInc and xuliang.
    4. \n
  4. Cross-site scripting (XSS) via video URL in YouTube embeds.  Reported by Marc Montpas.
    5. \n
  5. Cross-site scripting (XSS) via taxonomy term names.  Reported by Delta.
    6. \n
  6. Cross-site request forgery (CSRF) in Press This leading to excessive use of server resources.  Reported by Sipke Mellema.
    7. \n
\n

Thank you to the reporters for practicing responsible disclosure.

\n

In addition to the security issues above, WordPress 4.7.3 contains 39 maintenance fixes to the 4.7 release series. For more information, see the release notes or consult the list of changes.

\n

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

\n

Thanks to everyone who contributed to 4.7.3: Aaron D. Campbell, Adam Silverstein, Alex Concha, Andrea Fercia, Andrew Ozz, asalce, blobfolio, bonger, Boone Gorges, Boro Sitnikovski, Brady Vercher, Brandon Lavigne, Bunty, ccprog, chetansatasiya, David A. Kennedy, David Herrera, Dhanendran, Dion Hulse, Dominik Schilling (ocean90), Drivingralle, Ella Van Dorpe, Gary Pendergast, Ian Dunn, Ipstenu (Mika Epstein), James Nylen, jazbek, Jeremy Felt, Jeremy Pry, Joe Hoyle, Joe McGill, John Blackbourn, John James Jacoby, Jonathan Desrosiers, Kelly Dwan, Marko Heijnen, MatheusGimenez, Mike Nelson, Mike Schroder, Muhammet Arslan, Nick Halsey, Pascal Birchler, Paul Bearne, pavelevap, Peter Wilson, Rachel Baker, reldev, Robert O’Rourke, Ryan Welcher, Sanket Parmar, Sean Hayes, Sergey Biryukov, Stephen Edgar, triplejumper12, Weston Ruter, and wpfo.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4696";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:4:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:32:"WordPress 4.7.2 Security Release";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:68:"https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 26 Jan 2017 19:34:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:3:{i:0;a:5:{s:4:"data";s:8:"Releases";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:1;a:5:{s:4:"data";s:8:"Security";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}i:2;a:5:{s:4:"data";s:3:"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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4676";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:357:"WordPress 4.7.2 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.7.1 and earlier are affected by three security issues: The user interface for assigning taxonomy terms in Press This is shown to users who do not have permissions to use it. […]";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:17:"Aaron D. Campbell";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:2142:"

WordPress 4.7.2 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.

\n

WordPress versions 4.7.1 and earlier are affected by three security issues:

\n
    \n
  1. The user interface for assigning taxonomy terms in Press This is shown to users who do not have permissions to use it. Reported by David Herrera of Alley Interactive.
    2. \n
  2. WP_Query is vulnerable to a SQL injection (SQLi) when passing unsafe data. WordPress core is not directly vulnerable to this issue, but we’ve added hardening to prevent plugins and themes from accidentally causing a vulnerability. Reported by Mo Jangda (batmoo).
    3. \n
  3. A cross-site scripting (XSS) vulnerability was discovered in the posts list table. Reported by Ian Dunn of the WordPress Security Team.
    4. \n
  4. An unauthenticated privilege escalation vulnerability was discovered in a REST API endpoint. Reported by Marc-Alexandre Montpas of Sucuri Security. *
    5. \n
\n

Thank you to the reporters of these issues for practicing responsible disclosure.

\n

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

\n

Thanks to everyone who contributed to 4.7.2.

\n

* Update: An additional serious vulnerability was fixed in this release and public disclosure was delayed. For more information on this vulnerability, additional mitigation steps taken, and an explanation for why disclosure was delayed, please read Disclosure of Additional Security Fix in WordPress 4.7.2.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:7:"post-id";a:1:{i:0;a:5:{s:4:"data";s:4:"4676";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:32:"https://wordpress.org/news/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:6:"hourly";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:30:"com-wordpress:feed-additions:1";a:1:{s:4:"site";a:1:{i:0;a:5:{s:4:"data";s:8:"14607090";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Tue, 20 Jun 2017 12:23:48 GMT";s:12:"content-type";s:34:"application/rss+xml; charset=UTF-8";s:25:"strict-transport-security";s:11:"max-age=360";s:6:"x-olaf";s:3:"⛄";s:13:"last-modified";s:29:"Thu, 08 Jun 2017 16:08:34 GMT";s:4:"link";s:63:"; rel="https://api.w.org/"";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 249";}}s:5:"build";s:14:"20130911040210";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (301, '_transient_timeout_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1498004627', 'no'), (302, '_transient_feed_mod_ac0b00fe65abe10e0c5b588f3ed8c7ca', '1497961427', 'no'), (303, '_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9', '1498004629', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (304, '_transient_feed_d117b5738fbd35bd8c0391cda1f2b5d9', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:61:"\n \n \n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"WordPress Planet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:28:"http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"language";a:1:{i:0;a:5:{s:4:"data";s:2:"en";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:47:"WordPress Planet - http://planet.wordpress.org/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:50:{i:0;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:50:"WPTavern: Disqus 3.0 Beta Improves Comment Syncing";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=72176";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:61:"https://wptavern.com/disqus-3-0-beta-improves-comment-syncing";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2219:"

When we interviewed Daniel Ha, CEO and co-founder of Disqus, earlier this year, he explained why some users were reporting problems syncing comments between Disqus and WordPress and that improvements would be coming soon.

\n

“We may have taken some services offline to work on them which may have affected those who were trying to sync,” Ha said.

\n

Disqus has released 3.0 Beta 1 that fixes syncing issues and introduces a redesigned settings screen. Disqus 3.0 was rewritten to take advantage of newer APIs in WordPress which will allow for faster iterations of improvements.

\n

Comments are synced to the WordPress database using a webhook method instead of wp-cron making the process more reliable. This version also supports edited comments and comment states enabling users to see if comments are approved, pending, or deleted.

\nDisqus 3.0 Settings Screen\n

Disqus 3.0 has a redesigned settings screen that includes shortcuts to frequently visited sections of Disqus’ backend. Disqus replaces the Comments top-level menu item and shortcut links are now available in the WordPress Admin Bar.

\n

Other improvements to the plugin include:

\n
    \n
  • Replacing WordPress comments template with Disqus comments
    • \n
  • Replacing WordPress comment count with Disqus comment count
    • \n
  • Automatic closing of WordPress login window when using single sign-on
    • \n
\n

The plugin is only available via Gitub as the team seeks feedback to identify potential issues before rolling it out to the public. If you discover a bug, you can report it by opening a new issue on the project’s Github page.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 20 Jun 2017 07:28: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:21:"Matt: Peak Tea Demand";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:38:"https://ma.tt/2017/06/peak-tea-demand/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"https://ma.tt/2017/06/peak-tea-demand/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:459:"

I found this funny anecdote from a CNET article about the future of power:

\n

Power and utility companies must exactly balance supply with what people consume at any given moment. UK grid operators famously must cope with a demand surge after the TV soap opera “EastEnders” ends, when thousands of people start boiling water for tea.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Jun 2017 15:59: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: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: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:69:"WPTavern: WordCamp Europe 2017 Draws 1900 Attendees from 79 Countries";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=72127";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordcamp-europe-2017-draws-1900-attendees-from-79-countries";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5654:"photo credit: WP Tavern\n

WordCamp Europe was held this weekend in Paris, bringing together 1,900 attendees from 79 countries. Another 1,000 people joined via livestream from 77 countries to make a total audience of 2,900 participants from 92 countries. The number of attendees on the ground was about one third less than original estimates of 3,000, but everyone who wanted a ticket was able to get one. A team of 221 volunteers communicated on Slack behind the scenes to make the event run as smoothly as possible.

\n

The event’s 45 organizers made the presentations more accessible to speakers of different languages with live captioning and real-time audio translation.

\nphoto credit: WP Tavern\n

WordCamp Europe is the leading WordPress event for catching presentations about the ongoing efforts to bring the software to all the languages of the world. A large percentage of attendees were multi-lingual leaders in WordPress’ translation community, resulting in many presentations and lightning talks focused on topics like communication, internationalization, organizing translation sprints, and using inclusive language for interfaces.

\nphoto credit: WordCamp Europe 2017 Photography Team\n

Matt Mullenweg and Om Malik joined the event for a casual Q&A session with attendees wherein Mullenweg showed a demo of the new Gutenberg editor and announced its availability as a plugin on WordPress.org. We’ll cover their comments on the future of the editor and the open web more in-depth in another post.

\n

\n

This year’s WordCamp Europe sponsors had space for large 360° booths and the opportunity to be featured in 30-second advertisements between sessions. Organizers also arranged for sponsor workshops with a dedicated space for those who purchased the highest sponsorship levels. These workshops included topics like Creating a WordPress Theme for the Masses, Intro to WooCommerce, Jetpack tips, and hosting product demos.

\nphoto credit: WP Tavern\n

WordCamp Europe had no shortage of swag unique to the event, including a limited edition French plush Wapuu, posters, postcards, socks, stickers for European WordCamps, and other items for sale in the traveling Swag Store. A giant, stuffed French Wapuu made the rounds, appearing in pictures with attendees.

\n\n

\n\n

\n

Contributor Day kicked off the event on Thursday with a strong turnout of 473 attendees. Traditionally, WordCamp contributor days are held on Sunday after the main event, the day following the after party when many who signed up struggle to make it on time – or at all. WordCamp Europe attendees generally appreciated having the contributor day scheduled before the main conference and the higher attendance numbers demonstrate the success of this arrangement.

\n

The after party featured a 1930’s theme at the Pavillon d’Armenonville. Attendees dressed the part and enjoyed a relaxing end to the WordCamp with an evening of dancing and meeting new and old friends.

\n\n

\n

Organizers anticipate that videos of the presentations will be available next week. We will also be rolling out video interviews with interesting people from the European and global WordPress community in the coming days.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 18 Jun 2017 13:45:51 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:74:"WPTavern: 10 Lessons Learned From Five Years of Selling WordPress Products";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=72103";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/10-lessons-learned-from-five-years-of-selling-wordpress-products";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7934:"

This post was contributed by Rebecca Gill. Rebecca is the founder of Web Savvy Marketing, a web development, design, maintenance, and SEO consulting company based in Michigan and host of the SEO Bits podcast.

\n

Rebecca recently sold her Genesis Theme store to 9seeds, a store she managed and maintained for five years. In this post, she shares ten lessons learned from selling WordPress products.

\n
\n

When Jon Brown and I started talking about Web Savvy Marketing selling its theme store to 9seeds, it became abundantly clear that I wasn’t just selling him a portfolio of Genesis child themes. Anybody can do that. What I was really selling him was an established process and five long years of making mistakes and creating solutions.

\n

When I launched our theme store and stepped into the world of developing WordPress products, I was beyond naïve. I had no idea what I was getting myself into and I didn’t know how to run a successful e-commerce business.

\n

But after a lot of mistakes and course corrections, I found stability, a lot of great customers, and more revenue than I expected.

\n

Today, I’m sharing my top 10 lessons learned with you, so I can spare you from falling down the same rabbit holes and pitfalls.

\n

My 10 Lessons Learned

\n

Reputation Is Everything

\n

I didn’t set up out to create a strong reputation and I honestly didn’t know I was doing it. I was just following the rules given to me by my Grandmother and the basics of business I learned while working for my prior employers.

\n

What I realized was this – having a strong reputation helps you sell, but it also helps keep you out of hot water when things don’t go as you plan. People are more willing to buy from you, become your brand advocates, and forgive you when you make a mistake.

\n

A Strong FAQ Page Is Worth Its Weight in Gold

\n

I didn’t see this as a necessary page at first, but once I had the same question asked 100 times, I realized I needed to have an easily accessible page that answered common questions. Our comprehensive FAQ page has saved me time, but it also aided in sales. Visitors receive immediate answers to their questions and they are more inclined to hit the buy button while you still have their attention and interest.

\n

Thorough Post-sale Communication Is a Requirement

\n

During the first year of our store opening, I was flooded with post-sale emails and inquiries. No one was using our support forum and the option of self-service. I was so annoyed and frustrated it wasn’t even funny. And then something happened.

\n

I realized it wasn’t the buyers’ fault. I realized it was my fault. I had failed to communicate, provide next steps, and set expectations. Once I took ownership over this issue, I created a follow-up sequence that provided post-purchase instructions on where to go and what to do.

\n

A magical thing happened – or many things actually. I freed up my time because people stopped emailing me and I had happy customers who actually thanked me for all the great follow-up information. That was a win/win if there ever was one.

\n

Email Templates Save Oodles of Time

\n

Even with my stellar FAQ page and follow-up emails, I still received inquiries from people who asked similar questions. I learned to create email templates for anything I had to answer more than five times. This reduced my response time from five minutes to thirty seconds. This freed up my time and more importantly, it gave faster responses to my customers, so they were happy.

\n

Create Systems to Save Sanity

\n

I’m slightly obsessive-compulsive and I used this to our advantage with the theme store. I created project templates for any new theme launch and I mimicked the same type of tight structure I have with large custom website builds.

\n

We had a template full of to-do items, ownership of tasks, and expected turn around times. This made the design, coding, and launch of a theme very systematic. This in turn translated to faster product launches, fewer mistakes, and a reduction in development costs.

\n

Strong SEO Is Your Friend

\n

I could not have been successful without search engine optimization. I let SEO lead the way for what we would sell, who we would sell it to, and how we would market the final product. Strong SEO helped me select the right themes to develop, get quick sales, and cover my development costs within a few months of each launch.

\n

Social Media Is a Time Suck but Worth Every Minute Invested

\n

I have a love/hate relationship with social media. I hate that it takes so much time and it can be so emotionally draining. At the same time, I love that it helps you reach customers around the world and it supports the SEO process. Social media was a life raft in many ways and I don’t think the store or sales would have grown without it.

\n

If Things Can Go Wrong, They Will Go Wrong

\n

I have felt like this has been the norm for us this last year. Hosting, plugins, payment gateways, and third-party software sites have worn me out. And I’ve had a team to fix everything. You have to expect things to fail and you must have a plan to fix them quickly. It’s the nature of life and business. Learn to deal with issues quickly and to address one thing at a time.

\n

Grace Goes a Long Way in Diffusing Bad Situations

\n

No matter how hard you try and how hard you work, your customers will have bad days. When that happens you might receive the brunt of their emotions. This is called ‘transference’ and in most cases it has nothing to do with you or your product.

\n

You have to recognize this for what it is and handle it with grace. Close your email, walk away from your desk, or do whatever you have to do to not reply in anger. Instead, you need to let the moment pass so you can reply calmly and with grace. In each situation where I’ve used this tactic, I’ve had the crazy person reply with an apology, tell me they were having a really bad day, and then thank me for keeping my calm.

\n

People Will Steal Your Products, So Try Not to Take It Personally

\n

People will steal your work and your products. You’ll find your premium digital products sitting for download on forums and it will break your heart. Don’t let it. Address the situation and move on. Don’t let someone else’s bad juju ruin your mood, day, or momentum. It won’t help the situation and it will drive you crazy if you let it.

\n

In Hindsight

\n

I loved launching and owning our theme store. I didn’t sell it because I hated it or because it wasn’t profitable. I sold it because it was no longer the best fit for our company and me personally, which meant it wasn’t going to service our customers as it should.

\n

If I had the opportunity to do things over, I would still launch and I’d follow the same path I did over the last five years.

\n

The theme store brought me some wonderful employees, great online friends, and it brought me deeper into the WordPress community.

\n

Selling the store was a hard decision, but the right one. In my heart, I knew I wanted to focus the company more on custom development and I wanted to spend more time with my SEO courses and my new podcast.

\n

If you’re new to WordPress products and you’re considering launching a new product offering, I encourage you to jump in. Learn from my mistakes, but hold on, because you’re in for a wild ride.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 16 Jun 2017 22:36:13 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:29:"Matt: 4.8 and What’s Coming";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:22:"https://ma.tt/?p=47440";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://ma.tt/2017/06/4-8-and-whats-coming/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3844:"

Last week we released version 4.8 “Evans” of WordPress, as I write this it has had about 4.8 million downloads already. The release was stable and has been received well, and we were able do the merge and beta a bit faster than we have before.

\n

When I originally wrote about the three focuses for the year (and in the State of the Word) I said releases would be driven by improvements in those three areas, and people in particular are anticipating the new Gutenberg editor, so I wanted to talk a bit about what’s changed and what I’ve learned in the past few months that caused us to course correct and do an intermediate 4.8 release, and why there will likely be a 4.9 before Gutenberg comes in.

\n

Right now the vast majority of effort is going into the new editing experience, and the progress has been great, but because we’re going to use the new editor as the basis for our new customization experience it means that the leads for the customization focus have to wait for Gutenberg to get a bit further along before we can build on that foundation. Mel and Weston took this as an opportunity to think about not just the “Customizer”, which is a screen and code base within WP, but really thinking in a user-centric way about what it means to customize a site and they identified a number of low-hanging fruits, areas like widgets where we could have a big user impact with relatively little effort.

\n

WordPress is littered with little inconsistencies and gaps in the user experience that aren’t hard to fix, but are hard to notice the 500th time you’re looking at a screen.

\n

I didn’t think we’d be able to sustain the effort on the editor and still do a meaningful user release in the meantime, but we did, and I think we can do it again.

\n

4.8 also brought in a number of developer and accessibility improvements, including dropping support for old IE versions, but as I mentioned (too harshly) in my first quarter check-in there hasn’t been as much happening on the REST API side of things, but after talking to some folks at WordCamp EU and the community summit before I’m optimistic about that improving. Something else I didn’t anticipate was wp-cli coming under the wing of WP.org as an official project, which is huge for developers and people building on WP. (It’s worth mentioning wp-cli and REST API work great together.)

\n

To summarize: The main focus of the editor is going great, customization has been getting improvements shipped to users, the wp-cli has become like the third focus, and I’m optimistic about REST-based development the remainder of the year.

\n

I’ll be on stage at WordCamp Europe in Paris tomorrow afternoon doing a Q&A with Om Malik and taking audience questions, will also have a few announcements. You can get to the livestream tomorrow on the WordCamp EU homepage.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 16 Jun 2017 13:33:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:108:"WPTavern: WordCamp Europe 2017 Kicks Off with Contributor Day Focused on Growing WordPress through Inclusion";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=72072";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordcamp-europe-2017-kicks-off-with-contributor-day-focused-on-growing-wordpress-through-inclusion";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7322:"photo credit: WP Tavern\n

Hundreds of WordPress contributors gathered today with space for each team to have its own dedicated room. The Community Summit was held earlier in the week, lending a strong contingent of veteran contributors to this event, ready to use the short time they had together.

\n

With a high concentration of WordPress expertise gathered in Paris, WCEU organizers were able to include 13 talks and workshops aimed at enriching contributors. For an event that has always focused on serving diverse communities, it’s no surprise that many of the contributor projects were focused on growing and improving WordPress through accessibility, internationalization, documentation, and inclusion.

\n

WP REST API Team is Writing Docs to Make the API More Approachable to New Users and Contributors

\n

WP REST API project co-lead Ryan McCue said their team was concentrated on improving documentation to give developers a better understanding of the REST API infrastructure and how it integrates with the rest of WordPress.

\n

“The main thing we’re trying to work on is documentation for this sort of stuff, because we’re lacking a lot of documentation around the infrastructure,” McCue said. “One of the things we don’t do well is having a way to go from ‘I know nothing’ to ‘I know this stuff.’ A lot our documentation describes solutions without describing the problem and how you pick a solution.” Contributors are working on a new set of user guides, which are currently on GitHub, that will eventually be included in the developer handbook.

\n

McCue said the next major project is completing work on OAuth 2, the new authentication method that will allow users to authorize applications to access data on their sites. He anticipates the team will have a “very workable plugin” that could be ready for testing within the next six months.

\n

“We need to get this sorted if any of the mobile apps are going to use the REST API,” McCue said. These apps currently use the existing XML-RPC and WordPress.com APIs. Although OAuth hasn’t been a major focus so far this year, McCue said the team is looking at changing that going forward.

\n

Documentation Team is Working Towards Making HelpHub the Go-To Resource for WordPress Support

\nphoto credit: WordCamp Europe 2017 Photography Team\n

John Ang, who helped lead the Documentation team, said they have been focused on writing documentation for new contributors, as well as ensuring current docs are gender neutral and not overly technical so that content writers can understand them.

\n

“Helping with the project has traditionally been tough, because we don’t explain how you can get started,” Ang said. “We realized this across the entire documentation team. We are great at writing end-user documentation but not great at writing contributor documentation.”

\n

One of the major documentation projects they have been working on for the past few years is HelpHub, a companion resource to DevHub that will eventually hold all end-user documentation for WordPress. Migration from the codex is complete and the goal is to retire the codex once the project launches. Docs contributors are working towards making HelpHub the first place that users search for assistance before taking to the forums, lifting some of the burden from support volunteers. HelpHub is being designed to be easily searchable, possibly powered by elasticsearch, with inter-connected articles that focus on a single topic with bite-sized content.

\n

Ang estimates HelpHub is 30% complete in terms of content and 50% in terms of development. The backend is mostly finished and contributors are now working on the frontend. They are also bringing in content experts to write articles on critical topics, such as security. Ang hopes the team can deliver an MVP by the end of this year and finish the project within the next year.

\n

Community Team is Working on Redesigning Central.WordCamp.org to be More Useful to the Wider WordPress Community

\nCommunity Team Contributors – photo credit: WordCamp Europe 2017 Photography Team\n

A segment of Community Team contributors are working on marketing events better to the wider WordPress community that is not as well-connected with news about the project. As redesign of central.wordcamp.org is part of this effort.

\n

“Overall, the feeling is that we are not getting in front of the people who need our information the most,” Global Community Team member Josepha Hayden said. “Most WordCamps are educational. There is an aspirational aspect to all of them, of course. But the people who could use the information the most are, for example, the people who inherited a WordPress site and don’t know what to do about that.”

\n

After reviewing Google Trends to see what people are actually looking for when they get to a WordCamp site, the Community Team found that most visitors are searching for a WordCamp and the year. The only reason they get to the site is because they already know the event is happening.

\n

“The deputies we’ve spoken to in the last year or so have been echoing this feedback that the problem our WordCamp organizers have is they don’t have any way to get the information out to attendees better,” Hayden said. “If you already know about WordCamps, it’s easy to find your local WordCamp but if you don’t, then it’s not.”

\n

The Community Team has begun working on a communication and marketing plan that may include things like automated emails or social media campaigns but their first priority is redesigning central.wordCamp.org.

\n

“We realized the first place we need to start is to have a canonical place for them to go,” Hayden said. “Central.WordCamp.org was always supposed to be that place but for awhile it had kind of a hybrid audience. We’re working on identifying the content, who the correct audience is, and what we’re missing if we want to help somebody who has never heard about any WordPress events.”

\n

The discussion around redesigning central.wordcamp.org discussion has been happening for a few years and the team already has a design that was donated. They have the homepage and several other pages complete and hope to have the new site launched by the end of the year.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 16 Jun 2017 00:27: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: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:78:"WPTavern: Lifted, a WordPress Theme and Plugin Shop for the Marijuana Industry";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=72027";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:88:"https://wptavern.com/lifted-a-wordpress-theme-and-plugin-shop-for-the-marijuana-industry";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4731:"

Lifted is a new WordPress theme and plugin company founded by Drew Poland that caters to the marijuana industry. I reached out to Poland to learn more about his company, his pricing model, and get his perspective on this space in the WordPress ecosystem.

\n

Why did you decide to get into the marijuana industry with WordPress plugins and themes?

\n

Two primary reasons. The first is that, I truly believe in its medicinal use and there’s more than enough research out to support its effectiveness.

\n

Documentaries like Weed from CNN and Dr.Sanjay Gupta will bring you to tears watching children like Charlotte Figi, who suffer from extreme epilepsy, almost instantly stop the seizures and become functional with the things most of us take for granted like talking and walking.

\n

It’s tough to watch at times but there are a lot of cases from the extreme ones like end of life and debilitating issues, to everyday pain, stress, and PTSD management that make it a valuable alternative to harder, more addictive prescription drugs like Opioids, that are most commonly thrown at these as a solution.

\n

The second reason is less inspiring. It’s simply a budding industry with massive room for growth. It’s really just now coming around and I think will accelerate as it matures and the path will become clearer in terms of what clients need and want. An entire new industry has opened.

\n

What are some of the technologies used to power your themes?

\n

Everything is built the WordPress way so everyday users can for the most part, activate a theme and go. For the most part, its page templates, widgets, and some custom fields. If a user is comfortable with those than they can easily use a theme from Lifted.

\n

Are your themes and plugins GPL licensed or GPL compatible?

\n

Absolutely! Everything is 100% GPL licensed.

\n

How did you determine the price range for Grape Ape $129.99-$379.99 and can you provide an ETA on when it might be released? (I don’t think I’ve ever seen pre-orders for a theme before)

\nFront page of the Grape Ape Theme\n

I simply wanted to come in with a product priced on the higher end because I’m a firm believer that most WordPress products are priced entirely too low.

\n

I value my time on the highest level since I can’t make more of it, so a sell low and at volume approach just doesn’t work for me. I don’t want to support a $50 theme and the reality is that if this were a custom project for a client, the budget needs to be $10k minimum.

\n

The estimated release date for Grape Ape is the end of July.

\n

The pre-order was a result of simply wanting to force myself to get the actual Lifted Themes site up. Otherwise, I would have waited until Grape Ape was complete and then spent entirely too much time on the Lifted site.

\n

So I had to settle in with a good-looking theme I could live with and later work with my designer to develop something more custom. Had I really wanted to push the pre-order more I would have ramped up marketing months in advance to build up the anticipation and desire for it.

\n

Based on your research, how crowded is this space when it comes to WordPress themes and plugins?

\n

I would say it’s a clear lane and you can drive as fast or as slow as you like. I have been slow-moving up until this point and had the first marijuana plugin on WordPress.org, so there’s a lot of room.

\n

The marijuana industry is also not what I would call mature and at the end of the day there is still a stigma in professional settings. So if you are someone building products on the side or have a lot of clients in a specific industry that isn’t so receptive, you might not feel comfortable broadcasting that you are working in this space.

\n

Are there any legalities customers should be aware of before using your products?

\n

If used as intended, no. At its core, Grape Ape is fitted for your typical run of the mill business website, that’s no different from a coffee shop.

\n

At the moment, plugins are also in a clear zone. In the future, that may become more of a concern as services and tools are opening their APIs to connect dispensary back office systems with their web presence. That’s where things start to get tricky, more from a potential patient data view than anything else.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 15 Jun 2017 21:14:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:69:"WPTavern: 9seeds Acquires Web Savvy Marketing’s Genesis Theme Store";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71955";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/9seeds-acquires-web-savvy-marketings-genesis-theme-store";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3761:"

9seeds, a WordPress development agency launched in 2009, has acquired Web Savvy Marketing’s theme store for an undisclosed amount. Web Savvy Marketing launched its theme store in 2012 and currently has a library of 26 themes built on the Genesis Framework by StudioPress. 

\nWeb Savvy Marketing Theme Store\n

Chris Cree who helped launch and manage the theme store in 2012 departed from the company in 2016 and moved overseas to create a bible school. As the focus of Web Savvy Marketing shifted towards larger custom development projects and SEO, Rebbecca Gill, founder of Web Savvy Marketing, needed to find a way to maintain the theme store. 

\n

“I wanted Chris’ vision to live on and I wanted all my babies to continue to flourish and find their way to websites around the world,” Gill said. “I was at a crossroads and I didn’t know what to do.

\n

“I needed to make sure the company had a solid long-term strategy, but I also needed to protect our loyal theme customers. Five years of sales meant we had a lot of existing buyers who needed ongoing support.”

\n

Last year, Gill met Jon Brown, owner of 9seeds, and established a professional relationship.

\n

“We have very similar views on business, friendships, and ethics,” Gill said. “I liked him right away and I knew I wanted to spend more personal and professional time with him.

\n

“And as we grew closer, we started chatting about my struggles with the theme store and his long-term business goals. Before I knew it, he wanted to acquire the theme store and I wanted to give it to him.”

\n

9seeds has built a number of custom sites for clients using the Genesis Framework. For those who wanted to leverage existing themes, the company has often referred clients to Web Savvy Marketing’s theme store.

\n

“It took a bit more time of getting to know each other personally before I came to hold the same feelings that others had shared about her,” Brown said. “I felt deeply that this was a person I not only wanted to be friends with but wanted to be in business with. It became apparent to both of us that this was a perfect fit.”

\n

The acquisition brings the themes in-house and expands 9seeds reach into the WordPress products market.

\n

“It’s a win for 9seeds by giving us a springboard into a market we’ve long had our eye on accompanied by the best trail guide in the business showing us the path,” Brown said.

\n

“It’s a win for WSM by freeing Rebecca and her team up to align with where her focus now is on larger custom site builds and SEO consulting.”

\n

9seeds is providing support for existing customers and is working on a new theme. The support forums and theme store will migrate to the 9seeds domain later this year.

\n

To learn more about Brown and his work with 9seeds, listen to episode 276 of WordPress Weekly.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 15 Jun 2017 19:18: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:96:"Post Status: An entrepreneurial journey around eCommerce, with Patrick Rauland — Draft 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:31:"https://poststatus.com/?p=37565";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://poststatus.com/entrepreneurial-journey-around-ecommerce-patrick-rauland-draft-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:2487:"

Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by the creator and editor of Post Status, Brian Krogsgard, and this week’s guest host, Patrick Rauland.

\n

In this episode, Brian and Patrick Rauland discuss the state of eCommerce today, both from a product perspective, and for store owners. They also discuss Patrick’s own journeys in the land of eCommerce, as a former product manager for WooCommerce, a course author for Lynda (now LinkedIn Learning), consulting, and putting on an online eCommerce conference.

\n

\nhttps://audio.simplecast.com/72909.mp3
\nDirect Download

\n

Links

\n\n

Photo Credit

\n

Sponsor: Pagely

\n

Pagely offers best in class managed WordPress hosting, powered by the Amazon Cloud, the Internet’s most reliable infrastructure. Post Status is proudly hosted by Pagely. Thank you to Pagely for being a Post Status partner.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 15 Jun 2017 01:30:25 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Katie Richards";s: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:93:"WPTavern: WPWeekly Episode 277 – WordPress 4.8, Filing Good Bug Reports, and WP Super Cache";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=71968&preview=true&preview_id=71968";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:98:"https://wptavern.com/wpweekly-episode-277-wordpress-4-8-filing-good-bug-reports-and-wp-super-cache";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3427:"

In this episode, John James Jacoby and I start off the show by sending Jesse Peterson our thoughts, prayers, and positive energy. Peterson is a longtime member of the WordPress community, founder of Genesis The.me, and is battling Cystic Fibrosis. He received the call last Friday to receive a double-lung transplant but the surgery was cancelled after doctors determined the lungs were bad after removing them from the patient. We’re hoping he gets the call again soon!

\n

We give insight into what’s new in WordPress 4.8, provide tips for filing a good bug report, and tell you what to expect in the next major version of WP Super Cache. We discuss Imagely acquiring TeslaThemes and near the end of the show, we talk about the WordPress Community Summit at WordCamp Europe.

\n

Stories Discussed:

\n

WordPress 4.8 “Evans” Released Featuring Nearby WordPress Events, New Media Widgets, and Link Boundaries
\nHarare, Zimbabwe to Host Its 2nd WordCamp November 4, 2017
\nMajor Update Coming to WP Super Cache: New REST API, User-Friendly Settings Page, and Improvements to Legacy File Storage
\nImagely Acquires TeslaThemes, Is Seeking Other Acquisition Opportunities

\n

Picks of the Week:

\n

wpTestDrive allows you to try commercial themes and plugins before purchasing them. wpTestDrive creates a new WordPress instance with admin access where you can test plugins, themes, and their add-ons with or without demo content. It’s free, and test drives stay active for 10 days for registered members or 24 hours for guests. The site uses affiliate links to commercial products to offset the cost of running the site.

\n

CampTix is a free, open source ticketing plugin for WordPress that powers the ticket purchasing experience on WordCamp.org. Some of its features include, multiple ticket and attendee forms, coupon codes, mass emailing of attendees, exporting data into CSV or XML, refunds, and more.

\n

WPWeekly Meta:

\n

Next Episode: Wednesday, June 21st 3:00 P.M. Eastern

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #277:
\n

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 14 Jun 2017 23:22:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:10;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:25:"HeroPress: Trust Yourself";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=1915";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://heropress.com/essays/trust-yourself/?utm_source=rss&utm_medium=rss&utm_campaign=trust-yourself";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8453:"Pull Quote: Be open minded, trust yourself, and talk about what matters to you.

Editor’s Note: Birgit has been a friend of HeroPress since it’s very beginning. Through the oddities of life she was never able to do an essay. Recently she told me she would have one soon. This is not that essay. Our contributor this week needed some extra time and Birgit said she had something she wanted to write about, so here it is. Many thanks Birgit.

\n

Something is in the air. Do you feel the WordPress vibrations? It’s shortly before the fifth WordCamp Europe which will be held in Paris this year. The social channels like Twitter & Co. are flooded with pre-event messages. You can feel the emotions of excitement and sadness in the timeline nearby. People share their excitement about their upcoming attendance and others who can’t make it. I am a person who belongs to both groups.

\n

But let me begin some months ago to tell you how this came to be. After WordCamp Europe in Vienna last summer I purchased my ticket for WCEU 2017 in Paris directly after the ticket sale was opened. There was no doubt at all I would participate.

\n

How life’s play changes, it worked out differently than planned.

\n

I’ve struggled with some health issues over several years. Mostly caused by stress during and after the divorce, as well as some deaths in the vicinity. Nothing really serious, but not ignorable. I thought… But at the end of the summer last year I got seriously ill. Not the right place for details here, but I had to quit my day job in a small agency because the fixed-term employment contract ended at the same time. Also, I had to reduce any contributions to the WordPress project. I had to reduce my freelancing contracts, too.

\n

I ran from one medical specialist to the other to find the cause of my illness. I was so frustrated not to be able to work like I’ve done before and so upset about the brain-fog and the fatigue. It was so depressing. As a mom of five children, it is not funny to be ill. The three youngest kids are living at home with me and my new partner. My oldest daughter bought her own house. But I couldn’t help her while moving. Can you imagine, how frustrating this could be?

\n

But hey – I am a fighter like a lioness. I put everything on the plate, invested my small savings into healing treatments and so on.

\n

To make a long story short, I am getting healthier every day.

\n

We found the cause and the healing treatments are helping like expected. Two operations went well. It is a process, but it’s going forward.

\n

Sitting at home without a job is not my thing, so I searched for a new day job. I found a part-time employment in my hometown as a head of a tutoring institute. It is ok, but nothing WordPress related. It secures my existence. But my saving balance allowed no budget for WordCamp travels. I gave up thoughts of attending WordCamp Europe in Paris this year.

\n

So I decided to offer my ticket.

\n\n

\n

The unexpected miracle happened. I found sponsors for travel & stay without active seeking. My generous sponsors rewarded my past contributions to WordPress and Community over several years with this openhearted support. I am so grateful for this.

\n

Since 2012 I have been an active member of the WordPress Community. First as the main responsible person for the translations of WordPress into German, then as a part of the international Polyglots team. I am also editor and release manager for local German site and I am a member of some other contribution teams in the WordPress ecosystem. I spent a lot of spare time and money on contributions and WordCamp travels.

\n

Perhaps you can imagine how frustrating it was, that I couldn’t afford to travel to WordCamp Europe.

\n

An event where I can meet a lot of friends I made over the last years. Even more, I was happy to get the generous sponsoring. I am so grateful!

\n

In the last two years I had to reduce my contribution time and disappeared from the scene, but I followed the changes and enhancements within the community in the background. Nevertheless I wasn’t forgotten.

\n

And it’s not only me who get help to attend to WCEU:

\n\n

\n

Everyone has had some downs and some ups. If you ask, there is always someone who is willing to help you. It is an example of a mindset from an open-source community like the WordPress community and it reflects the philosophy. You can get everything, but you have to ask. Only speaking people can be helped.

\n

Apropos speaking people can get helped:

\n

I have a dream over some years to contribute to WordPress in full-time as a WordPress Community Manager. There are so many things I can do even if I am not a full-stack developer. Perhaps this miracle happens, too. But at this moment I am sitting on my suitcases to write about the generosity in the WordPress Community. This essay wasn’t planned, but it happened to have been written.

\n

I am so grateful for my heroes who made it happen, that I can go to the WordCamp Europe this year.

\n

There are so many unseen heroes outside who need to be seen.

\n

Be open minded, trust yourself and talk about what matters to you.

\n

There is a light at the end of the tunnel. Be your own hero.

\n

Beyond everything else: Care about yourself!

\n

The post Trust Yourself 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, 14 Jun 2017 08:00:34 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:12:"Birgit Olzem";s: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:82:"WPTavern: Imagely Acquires TeslaThemes, Is Seeking Other Acquisition Opportunities";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71716";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/imagely-acquires-teslathemes-is-seeking-other-acquisition-opportunities";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4432:"

In an effort to diversify and expand into the commercial WordPress theme market, Imagely, maintainers of NextGEN Gallery, have acquired TeslaThemes for an undisclosed amount.

\n

TeslaThemes launched in 2013 as a theme club and recently celebrated its fourth anniversary. The company has 68 themes in its library, including the TeslaThemes framework.

\n

Eric Danzer, Founder and CEO of Imagely, says no major changes will be happening with TeslaThemes and that their immediate focus will be to provide maintenance and support.

\n

“Beyond that, our goal is to do more of what Tesla has already been doing so well – creating beautiful new themes and continually enhancing the existing themes,” Danzer said.

\n

Imagely has been busy this year launching a managed WordPress hosting service for photographers, releasing new photography themes, and an Adobe Lightroom plugin that allows users to manage NextGEN galleries from within Lightroom.

\n

Later this year, Imagely plans to release a new version of NextGEN gallery with a redesigned backend interface. The company is also working on a way to add automated print fulfillment to WordPress.

\n

“Automated print fulfillment allows photographers to sell prints from their websites, and have those prints automatically delivered via the print lab without any intervention on their part,” Danzer said.

\n

“This functionality drives many large companies in the photo industry – SmugMug, ShootProof, Pixieset, Zenfolio, Photoshelter, and others. But it’s not possible yet on WordPress.

\n

“Bringing a full print solution to WordPress has the potential to revolutionize the photo industry and make WordPress the default web solution for photographers that it should be.”

\n

Marcel Sobieski, co-founder of TeslaThemes, thanked customers for their support and confirmed that they exited the company on June 9th.

\n

“We built a solid, trusted and valuable business, that is needed on the market and is appreciated both by industry colleagues and clients,” Sobieski said.

\n

This is the second exit in the last six months for Sobieski and his team. The sale of TeslaThemes will allow them to focus on a new venture called WPMatic.io, a one-on-one WordPress support and development company.

\n

“The six years of experience that we have in WordPress is already helping a few hundred clients and tens of companies and agencies in need, right after purchasing a WP Theme from the market,” Sobieski said.

\n

“Soon we will start partnering with some of the best WP Theme Clubs to deliver a unique experience for their clients.”

\n

The acquisition of TeslaThemes represents Imagely’s first major move into the general WordPress products market. The company is also seeking acquisition opportunities for other WordPress plugin and theme companies.

\n

“In the coming years, we’ll be both building and be acquiring a range of other WordPress theme and plugin companies,” Danzer said.

\n

“I’ll even add a small call here: if you have a solid WordPress product, with a great brand and stable revenue over around $200,000, and you are looking to exit, feel free to reach out to me directly to chat.”

\n

Correction: June 14th, 2017 The article incorrectly identifies Imagely as the creators of NextGEN Gallery. Alex Rabe is the creator of NextGEN Gallery and he released it in 2007. Photocrati acquired the plugin in February, 2016.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 13 Jun 2017 21:33:16 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:42:"Akismet: Coming Soon to a Jetpack Near You";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:31:"http://blog.akismet.com/?p=1942";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:70:"https://blog.akismet.com/2017/06/13/coming-soon-to-a-jetpack-near-you/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1007:"

If you haven’t tried Jetpack yet — our sister plugin — there’s never been a better time to add it to your bucket list.

\n

In the coming weeks we’ll be announcing a really exciting new addition to Jetpack’s services and you can sign up to get early access right here.

\n
\n

Coming Soon to Jetpack
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 13 Jun 2017 10: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:7:"Richard";s: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:82:"WPTavern: WordCamp for Publishers Opens Up Ticket Sales, 50% Sold in the First Day";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71732";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordcamp-for-publishers-opens-up-ticket-sales-50-sold-in-the-first-day";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2365:"

\n

WordCamp for Publishers, the first niche WordCamp to be focused around a specific industry, opened up ticket sales today. The event will take place in Denver, Colorado, August 17-19, and organizers have planned for just 230 attendees, due to venue constraints. In less than 24 hours since tickets went on sale, the event is already 50% sold out.

\n

Speakers and workshop facilitators have already been selected and published to the event’s website, featuring publication directors, developers, product managers, and other industry experts.

\n

The tentative schedule for the WordCamp includes a mixture of presentations, hands-on workshops, and social events to encourage networking and collaboration among publishers.

\n
    \n
  • Thursday, August 17: Presentations and workshops, followed by a brewery tour
    • \n
  • Friday, August 18: Presentations and workshops, followed by an after party
    • \n
  • Saturday, August 19: Publisher plugin contributor day, followed by a Rockies baseball game
    • \n
\n

One of the goals for the event is to encourage those who are maintaining open source tools for publishers to work together towards ensuring a strong future for those projects. Contributing is an important part of the event, as many of the organizers have experience working at or with publishing organizations that heavily rely on open source tools.

\n

The Denver Post has donated the venue for the event as an official sponsor and the official hotel is a five-minute walk from there. After purchasing a ticket online, attendees will receive an email with a link to make a reservation at the Sheraton Denver Downtown Hotel, which has a designated block of rooms for WordCampers.

\n

Organizers expect the event to sell out quickly, so if you’re thinking of attending, don’t wait to buy your ticket.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 09 Jun 2017 22:05:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:73:"WPTavern: Unsplash Updates its License, Raises GPL Compatibility Concerns";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71742";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/unsplash-updates-its-license-raises-gpl-compatibility-concerns";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6631:"

Unsplash.com, a site that provides high-resolution photos for free, updated its license and the change has people in the WordPress community concerned.

\n\n

\n

Prior to the change, Unsplash’s license stated the following:

\n

All photos published on Unsplash are licensed under Creative Commons Zero which means you can copy, modify, distribute and use the photos for free, including commercial purposes, without asking permission from or providing attribution to the photographer or Unsplash.

\n

According to GNU.org, the CC0 or Creative Commons Zero license is compatible with the GPL.

\n

CC0 is a public domain dedication from Creative Commons. A work released under CC0 is dedicated to the public domain to the fullest extent permitted by law. If that is not possible for any reason, CC0 also provides a lax, permissive license as a fallback. Both public domain works and the lax license provided by CC0 are compatible with the GNU GPL.

\n

If you want to release your work to the public domain, we recommend you use CC0.

\n

Unsplash’s new license states (emphasis mine):

\n

All photos published on Unsplash can be used for free. You can use them for commercial and noncommercial purposes. You do not need to ask permission from or provide credit to the photographer or Unsplash, although it is appreciated when possible.

\n

More precisely, Unsplash grants you a nonexclusive copyright license to download, copy, modify, distribute, perform, and use photos from Unsplash for free, including for commercial purposes, without permission from or attributing the photographer or Unsplash. This license does not include the right to compile photos from Unsplash to replicate a similar or competing service. 

\n

The inability to compile photos from Unsplash to replicate a similar or competing service is a restriction on how the photos can be used, calling into question its compatibility with the GPL.

\n

Luke Chesser, co-founder of Unsplash, explained on Twitter that individual photos have no restrictions.

\n

“The Unsplash license doesn’t violate GPL and can still be used in WordPress themes,” Chesser said. “There are no restrictions on the individual photos.

\n

“There is only a restriction on the collection of photos, which doesn’t even apply unless your intent is to create a similar service.”

\n

For example, it’s ok if someone creates a site that displays the best photos of bridges from Unsplash. But if the site makes those photos available for download, it would violate the license.

\n

On its FAQ page, Unsplash explains why the restriction was put in place:

\n

The fuel that drives Unsplash is the exceptional images that are generously contributed by people from all over the world. Without them, none of this would work. Unsplash would be nothing. We owe everyone who’s contributed a photo not only a thank you but support and empowerment for the gifts they’ve given us.

\n

Out of respect for our contributors and our ability to uphold our value of empowering creativity, we added this sentence to the Unsplash License.

\n

We don’t support the mass duplication of Unsplash photos with the purpose of replicating a similar or competing service because it leads to confusion which negatively impacts both the spirit of open creative use and the celebration of Unsplash contributors.

\n

Mass compiling of photos from Unsplash to distribute on other sites has created legal issues in the past. “Sites that mass duplicate and compile Unsplash photos point support and legal issues back to Unsplash, while continuing to redistribute photos that may be removed on Unsplash,” the company said.

\n

The reasons cited by Unsplash for putting the restriction in place are some of the same reasons WordPress plugin developers register trademarks. The GPL allows the following freedoms.

\n
    \n
  1. The freedom to run the program, for any purpose.
    2. \n
  2. The freedom to study how the program works, and change it so it does your computing as you wish.
    3. \n
  3. The freedom to redistribute copies so you can help your neighbor.
    4. \n
  4. The freedom to distribute copies of your modified versions, giving the community a chance to benefit from your changes.
    5. \n
\n

Over the years, there have been many instances in the WordPress community where businesses have taken advantage of these freedoms merely to profit from the work of others.

\n

The reselling of commercial plugins causes confusion in the market and resellers typically point support and other inquiries back to the plugin’s developers.

\n

Trademarks give commercial plugin authors measures to protect their brand without violating the GPL. A good example is the GravityForms Trademark page which clearly outlines how its brand can be used and displayed.

\n

For now, it appears that most people who use Unsplash will be unaffected by the licensing change. However, as long as there is one license that governs the use of images and it has at least one restriction, its compatibility with the GPL will remain in doubt.

\n

Correction June 14th Luke Chesser, co-founder of Unsplash, did not say that individual photos are still CC0-licensed but rather, have no restrictions.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 09 Jun 2017 21:27: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:15;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:131:"WPTavern: Major Update Coming to WP Super Cache: New REST API, User-Friendly Settings Page, and Improvements to Legacy File Storage";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71718";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:139:"https://wptavern.com/major-update-coming-to-wp-super-cache-new-rest-api-user-friendly-settings-page-and-improvements-to-legacy-file-storage";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2550:"

\n

WP Super Cache, a WordPress caching plugin maintained by Donncha Ó Caoimh and Automattic, is looking for users to help test the plugin ahead of the next major update. Ó Caoimh said the upcoming release is in a “stable and usable” state, but with the unusually large number of bug fixes and new features, it could use some testing in different environments.

\n

WP Super Cache is set to introduce a REST API, which will be useful for situations where administrators are not using wp-admin to manage their sites. The plugin is also changing the location for storing legacy cache files to the supercache directory.

\n

“This makes it easier to manage these files,” Ó Caoimh said. “The plugin doesn’t have to search through potentially hundreds of cache files for those that need to be deleted if a page updates or someone leaves a comment. Now all those files will be in the same directory structure the anonymous “supercache” files will be. I’m really excited about this feature as it makes caching for logged-in users/users who comment and caching of pages with parameters so much faster now.”

\n

Ó Caoimh is also updating the settings page to make it easier for new users to understand the options. Currently it asks the user to select from mod_rewrite, PHP, or Legacy page caching with little explanation for why a user might opt for a certain delivery method. The new settings page simplifies the language used to describe the caching types.

\n

\n

The upcoming release will also fix nearly 100 bugs. As WP Super Cache is one of the most popular WordPress caching solutions and is active on more than a million sites, any problems with a major release will have a far-reaching impact. The latest changes to the plugin are available on GitHub for anyone who wants to help test.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 09 Jun 2017 20:04: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:16;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:68:"WPTavern: Harare, Zimbabwe to Host Its 2nd WordCamp November 4, 2017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=71314";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/harare-zimbabwe-to-host-its-2nd-wordcamp-november-4-2017";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3375:"photo credit: Lonely Planet\n

Harare, Zimbabwe will be hosting its second WordCamp on November 4, 2017, at Hellenic Academy. The city was one of three selected to be part of the WordCamp Incubator Program in 2016. Harare’s first WordCamp was successful in connecting the local WordPress community and inspiring local leaders to carry on with organizing future events.

\n

Last year the Harare WordPress Meetup had 82 members and the group has nearly doubled in size with 142 members today. Members meet every month and communicate outside of meetings via an active WhatsApp group. The current venue they use was donated by Moto Republik, thanks to one of the members Munya Bloggo, who works there.

\n

“It was always the goal of the WordCamp Incubator program to organize an easily-reproducible event that we could organize independently in the years to come,” 2017 lead organizer Thabo Tswana said. “We expected it of ourselves. Some attendees and organizers actually approached me about the next WordCamp during WordCamp Harare 2016.”

\n

Tswana said the turnout at last year’s event was larger than he expected, because very few attendees booked tickets online. The majority ended up buying tickets at the door on the day of the event, a fairly uncommon scenario for most WordCamps that makes it somewhat difficult to estimate total attendees.

\n

“One of the biggest impacts that WordCamp had was introducing us to the WordPress Community,” Tswana said. “There are so many WordPress users in Zimbabwe (bloggers, designers, developers) but hardly anyone knew about the WordPress Community or how to contribute to WordPress. We now have a growing meetup group and the local community is starting to become more aware of what WordPress has to offer.”

\n

The local community consists primarily of developers and advanced WordPress users and Tswana said he would like see more of them getting involved with contributing. As the majority of meetup members are new to the larger WordPress community, they are still learning about the many ways users can contribute back to the project.

\n

Two Harare WordPress Meetup members, Kudakwashe Zafevere and Rima Trew, arranged for Hellenic Academy to donate a venue for WordCamp Harare 2017. The facilities are well-suited to hosting a tech event with wifi available.

\n

“This year, some local companies and organizations expressed interest in helping us out,” Tswana said. “We definitely expect more attendees due to the buzz that was created by last year’s WordCamp. To sum it all up, more people and organizations are getting involved this year.”

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 09 Jun 2017 02:33:43 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:118:"WPTavern: WordPress 4.8 “Evans” Released Featuring Nearby WordPress Events, New Media Widgets, and Link Boundaries";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71534";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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-4-8-evans-released-featuring-nearby-wordpress-events-new-media-widgets-and-link-boundaries";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:7169:"

WordPress 4.8 “Evans” is available for download and is the first major release of the year under the new release cycle. WordPress 4.8 is named after William John “Bill” Evans, an American jazz pianist.

\n

New Image, Video, and Audio Widgets

\n

WordPress 4.8 includes three new widgets. All three widgets make it easier to display images, video, or audio  without using HTML. The Text widget now has support for TinyMCE providing rich-text functionality. Similar to the post editor, users have a choice between using a Visual or Text editor with limited formatting options.

\nImage, Video, and Enhanced Text Widget\n

Because the Text widget uses TinyMCE, it inherits its nuances when it comes to pasting and displaying code. In a dev note that explains how TinyMCE was added to the Text Widget, Weston Ruter offers the following notice.

\n

When pasting HTML into the ‘Text’ (HTML) tab of the Text widget, any extraneous line breaks should be removed or else unwanted paragraphs and line beaks may result. This is particularly important when you paste in script or style tags (as in the case of 3rd-party JavaScript embeds), since auto-inserted paragraphs will cause script errors; this will be fixed in #2833.

\n

This behavior aligns with longstanding behavior in the post editor, so it is not new, although it does differ from how the Text widget has previously behaved. As noted above, for previously existing Text widgets that had the auto-add paragraphs’ checkbox unchecked (and thus the filter instance prop set to false), the previous behavior of not doing wpautop will be maintained: only once the widgets are modified will any extraneous line breaks need to be removed.

\n

Link Boundaries

\n

Adding and editing links in the visual editor is more intuitive thanks to link boundaries. Link boundaries provide a visual representation of where a link begins and ends. This helps prevent adding unnecessary text to the beginning or end of a link.

\n

\n

\n

See Nearby WordPress Events in the Dashboard

\n

One of the pillars of WordPress’ ecosystem is its community of meetups and WordCamps. In 2016, more than 62,566 people attended a local meetup in 58 countries. About a third of those were new members.

\n

WordPress 4.8 draws attention to these events by enhancing the News Dashboard widget. The widget will try to automatically guess your location and display meetups and WordCamps that are nearby.

\nNews Widget Shows Upcoming Meetups and WordCamps\n

If the location is incorrect, clicking the Pencil button opens a box where you can type in your city. The bottom of the widget includes links to the WordPress Meetup landing page, WordCamp Central Schedule, and the WordPress.org news blog.

\n

Responsive Customizer Sidebar

\n

In previous versions of WordPress, the Customizer Sidebar had a maximum width of 300 pixels. In WordPress 4.8, the Customizer Sidebar is responsive and its width will automatically increase based on the size of the screen up to a maximum of 600 pixels.

\nCustomizer Sidebar 345 Pixels Wide\n

More Accessible Admin Pages

\n

The headers on admin screens are now separate elements making it easier for assistive technologies to help people navigate pages.

\n

Support Dropped for Internet Explorer Versions 8, 9, and 10

\n

WordPress 4.8 drops support for Internet Explorer versions 8, 9, and 10 as these versions no longer receive security updates and are used by a small percentage of people. WordPress 4.8 will work in these browsers but some features related to TinyMCE will be limited. New features will no longer be tested against these older versions of IE.

\n

Noteworthy Changes

\n\n

This release was led by Matt Mullenweg and Jeff Paul. 346 people contributed to WordPress 4.8 and 106 of them were first time contributors.

\n

If you think you’ve discovered a bug in WordPress 4.8, read this support thread first to see if it’s a common issue that’s already been reported. If not, describe your issue in as much detail as possible and publish it to the Troubleshooting section on the support forums.

\n

As you upgrade your sites today, enjoy Time Remembered by Bill Evans, released in 1983.

\n
\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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 Jun 2017 19:29:12 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:18;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:62:"WPTavern: Worona Releases Free WordCamp Europe Paris Guide App";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71494";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/worona-releases-free-wordcamp-europe-paris-guide-app";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4240:"

Worona, a Madrid-based WordPress startup that builds mobile apps for free, has created an app for WordCamp Europe attendees. The WCEU Paris Guide app includes location and transportation information, schedules for the event, suggestions on where to eat (restaurants, bistros, a selection of the best cheap eats), a list of top attractions and museums, and nightlife recommendations.

\n

\n

Worona has released an Android app and an iOS app for attendees to download. Currently the app needs to be connected to the internet, but the company is working on supporting an offline mode in the next version, which is rolling out soon.

\n

“We used our online platform to turn a WordPress blog (paris.worona.org) into a native app,” Reyes Martínez, Worona’s marketing and communications specialist, said. “We use React and fetch the content using the WP-API. The apps are created with Cordova.”

\n

Worona is a relatively new WordPress startup in Europe, having released its first prototype in late 2014. The company offers its mobile app building platform to users for free via its plugin on WordPress.org. The platform turns WordPress sites into native mobile apps that users can publish to the app stores. Worona can also manage the process of publishing the app for a one-time 290€ fee.

\n

In 2016, Worona had more than 12,000 users from 150 different countries. After launching its new platform four months ago, more than 11,500 users have signed up.

\n

Martínez said that Worona differs from existing WordPress app builders in that it is free, user-friendly, completely open source, and extensible.

\n

“We studied the WordPress ecosystem and the mobile distribution trends during the last three years and realized that other existing solutions, such as AppPresser, are just focused on one or two mobile channels, but not in all of them,” Martínez said. “This can be a problem for publishers, as they have to configure the different channels (apps, web apps, AMP, Facebook Instant Articles) one by one and take care of being consistent with all of them. After launching our own beta in 2015 and testing similar solutions, we decided to develop an all-in-one platform with the vision of becoming the leading solution for mobile distribution.”

\n

Worona is also aiming to create an ecosystem of extensions and themes for the platform, allowing third-party developers to create new solutions.

\n

“The strategy of creating a marketplace of extensions has been successfully accomplished by the WordPress ecosystem before (but not by any of our direct competitors),” Martínez said. “WooCommerce, for example, gives you access to a variety of extensions aiming to solve any problems related to your e-commerce. Because it is open-source, these features can be created by any developer or user. The bigger the community, the higher the range of solutions.”

\n

Worona is currently a team of five, including two co-founders, a marketing specialist, and two full-stack developers. Most of the team will be at WordCamp Europe. They hope the WCEU Paris Guide app will be useful for attendees and also provide a good introduction to their product. If you have any feedback that would make the app more useful, make sure to comment on the announcement and Worona may be able to incorporate user suggestions before the event.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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 Jun 2017 17:32: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: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:35:"Dev Blog: WordPress 4.8 “Evans”";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=4770";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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://wordpress.org/news/2017/06/evans/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:31595:"

An Update with You in Mind

\n

\n

Gear up for a more intuitive WordPress!

\n

Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard. New features in 4.8 add more ways for you to express yourself and represent your brand.

\n

Though some updates seem minor, they’ve been built by hundreds of contributors with you in mind. Get ready for new features you’ll welcome like an old friend: link improvements, three new media widgets covering images, audio, and video, an updated text widget that supports visual editing, and an upgraded news section in your dashboard which brings in nearby and upcoming WordPress events.

\n
\n

Exciting Widget Updates

\n

\n

Image Widget

\n

Adding an image to a widget is now a simple task that is achievable for any WordPress user without needing to know code. Simply insert your image right within the widget settings. Try adding something like a headshot or a photo of your latest weekend adventure — and see it appear automatically.

\n

Video Widget

\n

A welcome video is a great way to humanize the branding of your website. You can now add any video from the Media Library to a sidebar on your site with the new Video widget. Use this to showcase a welcome video to introduce visitors to your site or promote your latest and greatest content.

\n

Audio Widget

\n

Are you a podcaster, musician, or avid blogger? Adding a widget with your audio file has never been easier. Upload your audio file to the Media Library, go to the widget settings, select your file, and you’re ready for listeners. This would be a easy way to add a more personal welcome message, too!

\n

Rich Text Widget

\n

This feature deserves a parade down the center of town! Rich-text editing capabilities are now native for Text widgets. Add a widget anywhere and format away. Create lists, add emphasis, and quickly and easily insert links. Have fun with your newfound formatting powers, and watch what you can accomplish in a short amount of time.

\n
\n

Link Boundaries

\n
Link Boundaries

Link Boundaries

\n

Have you ever tried updating a link, or the text around a link, and found you can’t seem to edit it correctly? When you edit the text after the link, your new text also ends up linked. Or you edit the text in the link, but your text ends up outside of it. This can be frustrating! With link boundaries, a great new feature, the process is streamlined and your links will work well. You’ll be happier. We promise.

\n
\n

Nearby WordPress Events

\n

\n

Did you know that WordPress has a thriving offline community with groups meeting regularly in more than 400 cities around the world? WordPress now draws your attention to the events that help you continue improving your WordPress skills, meet friends, and, of course, publish!

\n

This is quickly becoming one of our favorite features. While you are in the dashboard (because you’re running updates and writing posts, right?) all upcoming WordCamps and official WordPress Meetups — local to you — will be displayed.

\n

Being part of the community can help you improve your WordPress skills and network with people you wouldn’t otherwise meet. Now you can easily find your local events just by logging in to your dashboard and looking at the new Events and News dashboard widget.

\n
\n

Even More Developer Happiness 😊

\n

More Accessible Admin Panel Headings

\n

New CSS rules mean extraneous content (like “Add New” links) no longer need to be included in admin-area headings. These panel headings improve the experience for people using assistive technologies.

\n

Removal of Core Support for WMV and WMA Files

\n

As fewer and fewer browsers support Silverlight, file formats which require the presence of the Silverlight plugin are being removed from core support. Files will still display as a download link, but will no longer be embedded automatically.

\n

Multisite Updates

\n

New capabilities have been introduced to 4.8 with an eye towards removing calls to
\nis_super_admin(). Additionally, new hooks and tweaks to more granularly control site and user counts per network have been added.

\n

Text-Editor JavaScript API

\n

With the addition of TinyMCE to the text widget in 4.8 comes a new JavaScript API for instantiating the editor after page load. This can be used to add an editor instance to any text area, and customize it with buttons and functions. Great for plugin authors!

\n

Media Widgets API

\n

The introduction of a new base media widget REST API schema to 4.8 opens up possibilities for even more media widgets (like galleries or playlists) in the future. The three new media widgets are powered by a shared base class that covers most of the interactions with the media modal. That class also makes it easier to create new media widgets and paves the way for more to come.

\n

Customizer Width Variable

\n

Rejoice! New responsive breakpoints have been added to the customizer sidebar to make it wider on high-resolution screens. Customizer controls should use percentage-based widths instead of pixels.

\n
\n

The Squad

\n

This release was led by Matt and Jeff Paul, with the help of the following fabulous folks. There are 346 contributors with props in this release, with 106 of them contributing for the first time. Pull up some Bill Evans on your music service of choice, and check out some of their profiles:

\n1naveengiri, 4nickpick, Aaron D. Campbell, Aaron Jorbin, abhishek, Abhishek Kumar, abrain, Adam Harley (Kawauso), Adam Silverstein, Adam Soucie, Afzal Multani, Ahmad Awais, ajoah, Alex Concha, Alex Floyd Marshall, Alex King, Alex Shiels, Andrea Fercia, Andrea Middleton, Andrew Nacin, Andrew Ozz, Andrew Rockwell, Andy Mercer, Ankit K Gupta, arena94, Arshid, Arun, asalce, ashokkumar24, Barry Ceelen, bcworkz, Bharat Kambariya, Blobfolio, bonger, Boone B. Gorges, Boro Sitnikovski, Brad Touesnard, Brady Vercher, Brandon Kraft, Brandon Lavigne, Bridget Willard, Bunty, Cami Kaos, Carl Alberto, Casey Driscoll, cazm, ccprog, Chandra Patel, chesio, chetansatasiya, Chirag Patel, Chouby, Chris Klosowski, Chris Mok, chriseverson, Christian Chung, Corey McKrill, Courtney P.K., Cristiano Zanca, csloisel, Curdin Krummenacher, Cyrus Collier, Daniel Bachhuber , Daniel Llewellyn, Daniele Scasciafratte, Darren Ethier (nerrad), Darshan_dj, darthaud, Daryl L. L. Houston (dllh), David A. Kennedy, David Anderson, David Binovec, David Herrera, David Shanske, davidbenton, designsimply, Dhanendran, Dharmesh Patel, Dhaval Parekh, dingo-d, Dion Hulse, Dominik Schilling, Dotan Cohen, DoubleH, DreamOn11, Drew Jaynes, Drivingralle, dspilka, Edwin Cromley, Ejner Galaz, Ella Iseulde Van Dorpe, emirpprime, Eric Andrew Lewis, Erick Hitter, Ethan Allen, Fabien Quatravaux, Felix Arntz, fibonaccina, Florian TIAR, Francesca Marano, Frank Neumann-Staude, Franz Josef Kaiser, Gabriel Maldonado, Garth Mortensen, Gary Cao, Gary Pendergast, George Stephanis, Gustave F. Gerhardt, hedgefield, Helen Hou-Sandí, helgatheviking, Hristo Pandjarov, Ian Dunn, ig_communitysites, Igor Zinovyev, imath, Ipstenu (Mika Epstein), ireneyoast, Ivan Stefanov, ivantedja, J.D. Grimes, Jack Reichert, Jake Spurlock, James Nylen, Jaydeep Rami, jazbek, Jeff Bowen, Jeff Farthing, Jeff Paul, Jeffrey de Wit, Jen Miller, Jeremy Felt, Jeremy Pry, Jignesh Nakrani, Jip Moors, jjcomack, Joe Dolson, Joe Hoyle, Joe McGill, John Blackbourn, John James Jacoby, John Regan, Jonathan Desrosiers, Jonny Harris, Joost de Valk, Josepha, Josh Pollock, Juhi Saxena, Justin Kopepasah, Justin Tucker, K.Adam White, kafleg, Kailey (trepmal), karinedo, Kathryn, kaushik, Keanan Koppenhaver, keesiemeijer, Kelly Dwan, Kite, kjellr, Konstantin Kovshenin, Konstantin Obenland, kostasx, kubik-rubik, KUCKLU, Lance Willett, Laurel Fulford, Lee Willis, leemon, LewisCowles, LiamMcArthur, Lucas Stark, lukasbesch, Luke Cavanagh, Maedah Batool, maguiar, Mahesh Prajapati, mantismamita, Marin Atanasov, Mark Jaquith, Mark Root-Wiley, Mark Uraine, Marko Heijnen, Matheus Martins, MatheusGimenez, mathieuhays, matias, Matt Wiebe, Matthew Boynes, Matthew Haines-Young, mattyrob, Maxime Culea, Mayo Moriyama, Mayur Keshwani, Mel Choyce, Menaka S., Michael Arestad, michalzuber, michelleweber, Miina Sikk, Mike Crantea, Mike Hansen, Mike Jolley, Mike Little, Mike Nelson, Mike Schroder, Milan Dinić, Milind More, Mithun Raval, MMDeveloper, Mohammad Jangda, mohanjith, monikarao, Morgan Estes, moto hachi ( mt8.biz ), MrGregWaugh, mschadegg, Muhammet Arslan, MULTIDOTS, Naoko Takano, Naomi C. Bush, Nate Reist, Ned Zimmerman, Nick Halsey , Nikhil Chavan, Nitin Kevadiya, Nitish Kaila, nobremarcos, NoseGraze, nsundberg, nullvariable, odyssey, page-carbajal, Pascal Birchler, Paul Bearne, Paul Biron, Paul de Wouters, Paul Ryan, pavelevap, Payton Swick, pdufour, Perdaan, Peter Wilson, Philip John, Piotr Delawski, Piotr Soluch, postpostmodern, Pranali Patel, Pratik Shrestha, Presskopp, printsachen1, Priyanka Behera, prosti, ptbello, Rachel Baker, Rafael Ehlers, raggedrobins, raisonon, Rami Yushuvaev, ramiabraham, ranh, RC Lations, redrambles, reidbusi, reldev, rellect, RENAUT, rensw90, reportermike, Rian Rietveld, Riddhi Mehta, Robbie Cahill, Robert O\'Rourke, Robin Cornett, runciters, Ryan Boren, Ryan McCue, Ryan Welcher, Sagar Jadhav, Sagar Prajapati, sagarkbhatt, Sal Ferrarello, Samantha Miller, Sami Keijonen, Samuel Sidler, Sanket Parmar, sathyapulse, sboisvert, Scott Reilly, Scott Taylor, Sean Hayes, Sebastian Pisula, Sergey Biryukov, sfpt, sgolemon, Shady Sharaf, shashwatmittal, shazahm1, shulard, slbmeh, Soren Wrede, Stanimir Stoyanov, Stephane Daury (stephdau), Stephen Edgar, Stephen Harris, Steven Word, stormrockwell, Sudar Muthu, Supercoder, Sybre Waaijer, szaqal21, taggon, Takayuki Miyauchi, Takayuki Miyoshi, Tammie Lister, technopolitica, teinertb, tejas5989, terwdan, tharsheblows, theMikeD, thepelkus, Thorsten Frommen, Timmy Crawford, Timothy Jacobs, timph, tmatsuur, tomdxw, Topher, Travis Smith, triplejumper12, truongwp, tymvie, Ulrich, Utkarsh, vaishu.agola27, vijustin, vortfu, Weston Ruter, wpfo, xrmx, ze3kr, and Zeljko Ascic.\n

 

\n

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

\n

Do you want to report on WordPress 4.8? We’ve compiled a press kit featuring information about the release features, and some media assets to help you along.

\n

If you want to follow along or help out, check out Make WordPress and our core development blog. Thanks for choosing WordPress — we hope you enjoy!

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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 Jun 2017 14:49:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Matt Mullenweg";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}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:72:"WPTavern: Holler Box: A Smart Notification Plugin for WordPress Websites";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71490";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/holler-box-a-smart-notification-plugin-for-wordpress-websites";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4373:"

\n

Scott Bolinger, co-founder of AppPresser, has launched a new sales and conversion tool for WordPress websites called Holler Box. The plugin offers a lightweight, elegant popup message for capturing email addresses, displaying a (fake) live chat, or announcing a sale or event.

\n

Bolinger designed it to be non-intrusive – it’s not the kind of modal dialog that obscures content with an animated box in the middle of the page. Holler Box appears at the bottom right-hand of the page by default.

\n

After finding other WordPress popup plugins to be too complex for his needs, Bolinger decided to create his own solution for displaying a quick notification on his websites.

\n

“I’m a developer, and even adding a simple banner or popup to my site is not easy,” Bolinger said. I have to write the code, test locally, push to staging, test there, then push to production and do a final test. When I want to remove the message, I have to reverse the process. I’m busy, and that takes time.”

\n

Bolinger made it so that creating a new Holler Box is as easy as writing a new blog post. The content editing screen includes a meta box with options for customizing the display.

\n

\n

The “Advanced Settings” meta box allows users to set pages where the notification should be displayed, limit to logged-in only or logged-out visitors, set the display for new or returning visitors, and customize the delay based on time or scrolling. It also gives options for when the Holler Box should disappear and how often it should be shown to each visitor.

\n

Holler Box is capable of a wide range of uses. A few examples include the following:

\n
    \n
  • (Fake) Live Chat with Opt-in\n

    Show a live chat box to collect customer questions and emails, without having to actually deal with the hassle of live chat. As soon as your visitor types a question, an email opt-in pops up so you can follow up with them at a convenient time.

    • \n
  • Polls and Forms\n

    Embed anything into your Holler Box, including a feedback form or poll.

    • \n
  • Interactivity\n

    Add a link, video, contact form, or simple opt-in form that integrates with major email providers like MailChimp and Convertkit.

    • \n
\n

Below is an example of how the MailChimp email opt-in form works:

\n

\n

Holler Box also tracks impressions and conversions (link clicks and message opens) so that users can see how well their notifications are performing and optimize them as needed.

\n

The free version on WordPress.org has an impressive number of customization options, but Bolinger also plans to release a Pro version that will include additional features, such as an option for a header banner, more advanced display filters, automatic message deactivation, advanced email opt-in features, more conversion data, and support.

\n

“Holler Box aims to be more stylish and easier to use than existing options,” Bolinger said. “I use it when I need to make an announcement without spending a lot of time in a complex tool.” He said he could see the plugin working well side-by-side with well-established popup plugin competitors like OptinMonster.

\n

Bolinger said Holler Box is not affiliated with AppPresser, but he plans to use it as a sales tool on all of his sites. The plugin’s unique feature set is something he found missing in WordPress’ marketplace for sales/conversion tools.

\n

“I think Holler Box will increase sales and conversions without being as disruptive as other popups,” Bolinger said. “The sale notification popup and faux live chat feature are really unique. It’s how I want to communicate with my audience – hopefully other people feel the same.”

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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 Jun 2017 01:37:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:86:"WPTavern: WPWeekly Episode 276 – Interview with Jon Brown, a Traveling Digital Nomad";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=71482&preview=true&preview_id=71482";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wpweekly-episode-276-interview-with-jon-brown-a-traveling-digital-nomad";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2848:"

In this episode, John James Jacoby and I are joined by Jon Brown. Brown is a developer and author for 9seeds, a WordPress development agency. Brown describes what it’s like to work remotely and offers tips on how to stay productive while traveling. He tells us what items he can’t travel without. We also get his take on recent developments and debates going on in the WordPress community.

\n

Stories Discussed:

\n

Open Sourcing Mental Illness Surpasses $50K Fundraising Goal
\nVue.js Creator Evan You Weighs in on WordPress JavaScript Framework Discussion
\nWordCamp Europe 2017 Livestream Tickets Now Available
\nWPForms Acquires WP Mail SMTP Plugin
\nVersionPress Launches VersionPress.com to Fund Open Source Project

\n

Picks of the Week:

\n

GenerateWP is a collection of tools that generates code for Shortcodes, Post Types, Meta Boxes, Taxonomies, Term Meta, and Post Statuses.

\n

Holler Box enables users to create customizable marketing messages to display to site visitors. Use Holler Box to convert website visitors, upsell customers, and get messages out to the right people at the right time.

\n

WP Performance Profiler is a plugin by Interconnect.it that helps developers optimize the performance of WordPress sites running on PHP 5.3 to 5.6.

\n

WPWeekly Meta:

\n

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

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #276:
\n

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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 Jun 2017 01:10:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:72:"Post Status: Teaching what you learn with Joe Casabona — Draft 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:31:"https://poststatus.com/?p=37463";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:65:"https://poststatus.com/teaching-learn-joe-casabona-draft-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:1627:"

Welcome to the Post Status Draft podcast, which you can find on iTunes, Google Play, Stitcher, and via RSS for your favorite podcatcher. Post Status Draft is hosted by the creator and editor of Post Status, Brian Krogsgard, and this week’s guest host, Joe Casabona.

\n

Brian and Joe discuss the way they have learned WordPress over the years, and how they’ve gone about sharing and teaching what they’ve learned. They focus mostly on front-end parts of WordPress development.

\n

https://audio.simplecast.com/72351.mp3
\nDirect Download

\n

Links

\n\n

Sponsor: Yoast

\n

Yoast SEO Premium gives you 24/7 support from a great support team and extra features such as a redirect manager, recommended internal links, tutorial videos and integration with Google Webmaster Tools! Check out Yoast SEO Premium.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 07 Jun 2017 17:33:02 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Katie Richards";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:23;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:44:"Donncha: Take a sneak peek at WP Super Cache";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:28:"https://odd.blog/?p=89500269";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:64:"https://odd.blog/2017/06/07/take-a-sneak-peek-at-wp-super-cache/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4302:"

WP Super Cache is a full page caching plugin for WordPress that makes your site faster, and helps deal with unexpected surges in traffic.

\n

Over the last few months we’ve been busy working on the plugin to add new features and fix bugs and we can almost call it ready. It’s stable and usable and runs on this site but we would love more people to test it out before we release a new version.

\n

Here’s just some of the new features and bug fixes we’ve been working on:

\n
    \n
  • The plugin was based on WP-Cache which stored cache files in a single directory, and those (legacy caching) files were for the most part stored the same way all this time but now they’re being placed in the supercache directories (#177). This makes it easier to manage these files. The plugin doesn’t have to search through potentially hundreds of cache files for those that need to be deleted if a page updates or someone leaves a comment. Now all those files will be in the same directory structure the anonymous “supercache” files will be. I’m really excited about this feature as it makes caching for logged in users/users who comment and caching of pages with parameters so much faster now.
    • \n
  • We’re adding a REST API to the plugin because in the future not everyone is going to use wp-admin to take care of their sites. Take a look in the rest directory for the code we’re working on.
    • \n
  • Debug logs now have a username and password to protect them from prying eyes.
    • \n
  • And many bugs fixed over the last few months.
    • \n
\n

Since “legacy caching” or “WP-Cache caching” is now more maintainable and faster we want to change the language describing how the plugin caches and delivers pages.

\n

\n

Currently the plugin asks you to choose between mod_rewrite, PHP and “Legacy page caching” which isn’t really useful. Most users won’t recognise those terms. It’s also not accurate as “legacy page caching” is active all the time as long as caching is enabled.
\nInstead we should have “Standard Caching” and “Super Caching”. Super Caching will then have simple and expert delivery methods.

\n

Simple delivery is through PHP, while expert delivery uses mod_rewrite rules which means the .htaccess file has to be updated and hopefully the warning below it will discourage casual users from testing it.

\n

Due to the huge number of changes in the plugin we really need people to give it a try and check if everything works ok. The changes to the settings page will hopefully make it easier for new users to get to grips with it too.

\n

You can find the newest code on Github. The changes to the settings page are in #255 if you want to comment on them.

\n

Thanks in advance! 🙂

\n\n

Related Posts

\n

Source

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Wed, 07 Jun 2017 17:24: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:7:"Donncha";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:25:"HeroPress: Trust The Dots";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=1890";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:102:"https://heropress.com/essays/trust-the-dots/?utm_source=rss&utm_medium=rss&utm_campaign=trust-the-dots";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:12678:"Pull Quote: WordPress is such an amazing melting pot that involves people from everywhere, no matter how old they are, where they are from, or what languages they speak.

I was born twice: first, as a baby boy in the sunny morning of Monday June 14, 1993 in Taiz, Yemen; and then again, in the fall of 2008. It was my first time to study at a public high school, grade 10, class 12. It was completely different than the private school I used to study at. It was big and crowded, with a minimum of 80 students in each class!

\n

At that time, I was trying to improve my personality and explore new opportunities. I wanted to live my life fully, not as the teenager that I was. A way to organize my thoughts and connect with new people was needed. I did not have a clue what to do until the moment I got the chance to use the internet and began to read online blogs of many interesting bloggers. The idea of blogging was fascinating to me. “Why not starting one?” I thought to myself.

\n

Finding WordPress

\n

As days passed, I met four enthusiastic and ambitious schoolmates who became my friends till now.  Mohammed, one of them, was a relatively quiet and open minded person. My mates and I got to know him through MSN Messenger, and, surprisingly, he was studying in the next class! He was very absorbed in Web Development and was working on a custom CMS platform and some other web applications for his father’s clinic. I asked him about blogging software he would recommend. He strongly recommended Joomla and also suggested Drupal, WordPress and others. I tried them all.

\n

WordPress was so easy to use and out-of-the-box, although I had failed a few times while I was trying to install it locally. Once I had logged-in to the dashboard, honestly, I thrilled to pieces!

\n

After some time, my friends and I decided to start a simple blog about Graphics Design using WordPress. It was my beginning to learn the basics of Web Development (HTML, CSS, Javascript and PHP). Fortunately, Mohammed had a book that he lent me, and some PDFs, that I copied. We were constantly discussing and learning from each other during break times or in the afternoons. They were enjoyable and enlightening moments.

\n

I used to receive some positive messages as the developer of the blog we started and appreciative replies to my answers for some questions in Arab WordPress community, a forum to share knowledge among Arab WordPress users. This encouraged me to start a small freelancing business with WordPress. It seemed a great idea to expand expertise, earn some money, and follow my passion!

\n

Fitting It All In

\n

Being a freelancer and a high-school student at the same time was not that easy as one would think! Sometimes I was working until 3:00 a.m. to finish a client project, and then woke up at 6:30 a.m. rushing to school. Most often, classes were so dry that led me to write PHP codes in every copy-book of mine! If you would like to try this at your school, remember to move yourself to the end of your class or be ready for any of your teachers’ mean reactions to keep you attentive! On several afternoons, I used to take naps to restore my energy and be ready to work at night.

\n

Very rarely, I would have to stay out at internet cafés until 2:00 a.m. to upload/download things I needed because we had no Internet connection at home.

\n

For sure, this made my parents quite angry and obviously worried. Most importantly, I had neither a cell phone because of some strict rules in my family nor a national ID card because of the legal age requirement in Yemen. I was attempting to use my school ID card to receive money transactions, and guess what? I was lucky enough to manage it twice. But then I was asked to present a national ID. “ When will I turn 18?” I just had to overcome that obstacle, asking trustworthy friends to help.

\n

My clients were mostly from the Arab World, Europe, and USA. I had the chance to contact with many nice and outstanding people who not only boosted my experience but also showed me the way into some new opportunities and more success.

\n

Support At Home

\n

At the beginning, most of my family members thought I was playing, except my MOTHER. I remember the moment I told her about my fairly new business. She said, “Regardless of what it is, just do what you love and believe in!” However, I faced hard times trying to convince her I did not smoke as she smelled cigarette on my clothes whenever I got back home from those cafés! On the other hand, my father was the kind of man who stood backstage. He used to tell his friends how happy and proud he was of me. That was all what I needed from him.

\n

Giving Back

\n

On August 2012, I sent a message to Rasheed Bydousi, Arab WordPress community founder and translation editor of Arabic language, to suggest some ideas and ask to be a volunteer. He was very supportive and truly wise. We started discussing and working on some ideas for more than 4 months. In parallel with studying, working, and being a volunteer, I increased my efforts in translating, patching (helping in development), and reporting bugs for WordPress projects.

\n

It was very important for me to give back to the community I had taken a lot from.

\n

I felt the need of holding a WordPress meeting in my hometown, Taiz, because of the lack of specialized people who would like to collaborate and share knowledge. In 2013, I invited local developers to a small meeting in a local coffeeshop called “AL-Rassef”.

\n

WordPress Meeting in Taiz, Yemen

\n

Afterward, I presented a lecture about WordPress at Taiz University, in the same lecture hall I used to be a student in by that time. It was a warm beginning but I couldn’t continue due to my work and the deterioration of the political and security situation.

\n

Disruption

\n

Since 2011, my country has been facing major political changes and instability. On April 2015, the Yemeni crisis has reached its climax and war started in my city, Taiz, and it is still going on! Some of my relatives had decided to move out of Taiz but my father chose to stay, hoping that war will stop quickly. We lived for months without public electricity or Internet. When the fight crawled to our area, we lived for weeks in the ground floor of our house, no way to go out, tanks firing from 300 meters away, airstrikes on nearby areas, and snipers shooting whoever dared to walk on streets. Many friends and innocent people were killed and some members of my family were hurt. We couldn’t sleep for days, fearing that at any moment they will knock our house door.

\n

I thought that was the end for me and all of my dreams. I was pretending to be cool and calm so my younger brother and two sisters feel better. I was telling jokes, reading books or watching movies when we got some power from my uncle generator. “Life of Pi” was one of the movies we had watched and everyone enjoyed it! I refused to hold a gun, “How could it help?! That’s not my role in life!” I was thinking.

\n

I was struggling to believe in tomorrow, no matter how it looked miserable and sad.

\n

In one of the mornings, after a nearby airstrike, we got a chance to escape. I tried to hold every detail of our house, neighborhood and street. “Thank you for all great memories. I will definitely return,” I told my house, feeling torn apart back then! I only took my laptop, tablet, and few clothes, they were all what I needed to start over.

\n

Starting Over

\n

“You can’t connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future. You have to trust in something — your gut, destiny, life, karma, whatever. This approach has never let me down, and it has made all the difference in my life.”
\n— Steve Jobs

\n

After some time of catching my breath, I realized that I had to connect the dots, keep on following my dreams and aim higher. On May 2016, I moved to Sana’a, the capital city of Yemen, leaving the pain and frustration behind. I got to know some enthusiastic developers and we decided to establish a community called Yemeni Developers Club for people who are interested in computer programming and have the passion for it. We hold a meeting on the first Saturday of every month to share ideas, answer questions, and help one another to innovate, learn, and grow. We are planning to have, in the near future, special meetings to discuss WordPress related topics and learn how to obtain the maximum benefit from it.

\nPhotos for Ta’izz and Sana’a cites, photographed by Mona Athubhani.\n

Amazing Melting Pot

\n
\n
\n
\n
\n
\n
I am sure that WordPress helps thousands of developers, including me, be more independent, involves them to be parts of it, and offers opportunities to serve people from around the world.
\n
\n
\n
\n
\n
\n

WordPress is such an amazing melting pot that contains people from everywhere, no matter how old they are, where they are from, or what languages they speak.

\n

Become a Hero

\n

Being a WordPress hero is not about programming skills or contributions size, it is all about the challenges we face and overcome. It is even more about supporting the new users to be the next heroes.

\n
\n

Thank You

\n

Thanks to all my friends who contributed to make this essay better. Many thanks to Topher DeRosia for inviting me to write here and SPECIAL THANKS to Mona Athubhani without whom I would not have completed this essay.

\n

The post Trust The Dots 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, 07 Jun 2017 00:00:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Nashwan Doaqan";s: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:76:"WPTavern: VersionPress Launches VersionPress.com to Fund Open Source Project";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=71410";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/versionpress-launches-versionpress-com-to-fund-open-source-project";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3005:"

The founders of VersionPress have launched VersionPress.com, a WordPress managed hosting service. VersionPress.com is the best of what VersionPress offers paired with features such as, staging sites and backups, on an Amazon Web Services infrastructure.

\n

VersionPress is essentially an undo button for WordPress or full version-control. At the click of a button, users can undo an action and restore a site’s database to a previous point in history without having to export and import MySQL.

\n

Borek Bernard, co-founder of VersionPress, says the move is the result of trying to overcome two major challenges: WordPress plugins and Hosts. WordPress plugins can alter a site’s database. Building in support for the 40K+ plugins that exist in the repository has been a huge undertaking for the team.

\n

In order to use VersionPress, a webhost needs to have Git installed and allow proc_open which it uses to interact with Git. Most hosts do not allow proc_open for security reasons or have older versions of Git installed, generating incompatibilities. “Over time, it became clear we needed our own environment to run VersionPress in,” Bernard said.

\n

All sites hosted on the platform run PHP 7 or Nginx, HTTP/2, and at least two Docker instances that auto-scale based on load. VersionPress.com includes the ability to set up staging and production sites using VersionPress’ capabilities to merge changes between the two. Similar to Flywheel, billing can be assigned to a developer, agency, or client account. “The platform is geared towards WordPress developers and agencies but will help anyone who wants a fast, reliable WordPress site,” Bernard said.

\n

The model they’re using is similar to WordPress.com and self-hosted WordPress. “A hosted service will provide resources to fund the development of the open source project and its long-term stability,” he said. “So it became a no-brainer at some point.” General availability for VersionPress.com won’t open until July but those who pre-order will receive a substantial discount.

\n

Bernard re-iterated that VersionPress will always be a free, open source project and that VersionPress.com is a major step towards bringing full version control of WordPress to the masses.

\n

The managed WordPress hosting space is well established and perhaps a bit crowded. It will be interesting to see how VersionPress.com compares to and fits in with the competition.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 06 Jun 2017 21:45: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:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:26;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:36:"Matt: Remote Work Can’t Be Stopped";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=47433";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"https://ma.tt/2017/06/remote-work-cant-be-stopped/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:489:"

Christopher Mims writes for the Wall Street Journal Why Remote Work Can’t Be Stopped, also riffing off the IBM shift I wrote about a few weeks ago. I was exciting to see an Automattician Julia featured at the top and a few other colleagues having their voice in the article.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 06 Jun 2017 21:14: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: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: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:46:"WPTavern: WPForms Acquires WP Mail SMTP Plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=71426";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:57:"https://wptavern.com/wpforms-acquires-wp-mail-smtp-plugin";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:4349:"

\n

WPForms, founded by Syed Balkhi, has acquired the free WP Mail SMTP plugin from WordPress plugin developer Callum MacDonald. WP Mail SMTP has more than 600,000 active installs and WPForms will allow it to continue to operate as an independent plugin on WordPress.org. Balkhi said the plugin will become the company’s go-to recommendation on WPForms as well as WPBeginner.

\n

Email deliverability is a common problem for all types of WordPress websites, but it is the most frequent support issue for those using WPForms.

\n

“The number is only growing as Gmail, Yahoo, and others implement aggressive filters to reduce spam,” Balkhi said. “These spam filters look to see whether an email is originating from the location it claims to be originating from. This causes the emails sent from your WordPress site to either go in the spam folder or sometimes not be delivered at all! Having a proper SMTP solution significantly increases email deliverability. I believe that once we implement the new UX and workflow, this will significantly reduce our support load since this is the #1 issue our users deal with.”

\n

After a few months of email exchanges, Balkhi and Callum MacDonald reached an agreement for WPForms to purchase WP Mail SMTP. Balkhi would not disclose the exact financial details of the acquisition but said it was “a five-figure-deal because the plugin itself did not generate any revenue.”

\n

MacDonald had considered monetizing the plugin in the past but saw too many hurdles as he became less active in the WordPress space over the past few years.

\n

“There are a few recent developments around SMTP that mean the plugin could use an update,” MacDonald said. “I didn’t have the time, so it made sense to move on at this point. I went over [monetizing] it several times. My conclusion is that it’s a lot harder than it looks. If I was still active in the WordPress space, it would make more sense, but I’m not, so monetizing was going to be a long road and hard work. It made more sense to sell.”

\n

Balkhi said he approached MacDonald because email deliverability was a problem that he was looking to solve for WPForms users as well as the larger WPBeginner and WordPress community.

\n

“We didn’t want to build an add-on for WPForms because the problem isn’t unique to just us,” Balkhi said. “It affects every form plugin and basically every WordPress website that sends an email of any kind (forgot password, user registration, etc).”

\n

Last year Balkhi and his team acquired Yoast’s Google Analytics and renamed it to MonsterInsights. Over the past year the plugin has continued its growth from 10 million downloads at the time of acquisition to more than 16 million today.

\n

Balkhi reports that the MonsterInsights acquisition has been a success but the product was a very different type of acquisition from the one announced today. He said he has no plans to build an email deliverability service but rather wants to invest in a solution that will help his customers and others in the WordPress community.

\n

WP Mail SMTP plugin users can expect improvements to the plugin and a more “beginner-friendly” redesign, which Balkhi anticipates to release at the end of Q3 or Q4 of 2017.

\n

“In terms of growing our WPForms’ user base through WP Mail SMTP, that’s not our primary goal,” Balkhi said. “Our top priority is to solve the email deliverability issue that our existing users and the larger WordPress community faces.” Balkhi said he hopes to leverage the 600,000+ user base to negotiate better deals with established email deliverability services.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 06 Jun 2017 20:12: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:28;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:88:"WPTavern: Cory Miller and Dr. Sherry Walling Launch ZenTribes an Entrepreneur Peer Group";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71006";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:98:"https://wptavern.com/cory-miller-and-dr-sherry-walling-launch-zentribes-an-entrepreneur-peer-group";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3202:"

Being an entrepreneur can be stressful, emotional, and lonely, especially during a rough part of life. Cory Miller, founder of iThemes, has been at the forefront of advocating that entrepreneurs don’t have to go through the struggles of running a business alone.

\n

Two years after founding iThemes, Miller found himself going through a tough divorce at the same time his company started taking off.

\n

“Not many people in my life at that time could come close to relating to what I was going through as a human combined with being an entrepreneur,” Miller said.

\n

“I was suffering in solitude. And I was craving authentic relationships with like-minded people on a similar path who knew what living the entrepreneurial life — with its sometimes drastic ups and downs — meant and who were walking it every day, like me, and wanted to walk together with others too.”

\n

Miller eventually found himself in an entrepreneur peer group in Oklahoma City, OK, where entrepreneurs meet once a month for three hours to discuss the trials and tribulations of running a business.

\n

Miller says the group is partially responsible for his good health and happiness as a business owner, father, husband, and human being.

\n

In an effort to create similar opportunities for other business owners, Miller has partnered with Dr. Sherry Walling, who has a PhD in Psychology, to launch ZenTribes.

\n

ZenTribes is a group of 6-9 like-minded entrepreneurs that get together once a month online to share stories, encouragement, and express support for one another. Walling and Miller are both members of the group and will be sharing their expertise with members.

\n

Meetings will take place every Wednesday from 1-2:30 PM Central Standard Time for eight weeks using Zoom. The first meeting is on July 12th. The last meeting is on August 30th.

\n

The first 15 minutes of meetings will focus on a key topic with an hour set aside for discussions and sharing experiences related to that topic. The last 15 minutes are dedicated to sharing resources and giving attendees suggested homework.

\n

Some of the topics that will be discussed include:

\n
    \n
  • Burnout
    • \n
  • Depression
    • \n
  • Conflict
    • \n
  • Failure and loss
    • \n
  • Loneliness and friendship
    • \n
\n

ZenTribes is accepting applications for the first group of people until 1 PM CST June 15th. The cost to be a member of the group is $799. For more information about this initiative, listen to episode 120 of the ZenFounder podcast. In it, Miller and Sherry describe the program, why they created it, and how entrepreneurial groups can benefit business owners.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 06 Jun 2017 17:35:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:22:"Matt: Safe Avocado-ing";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=47427";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:39:"https://ma.tt/2017/06/safe-avocado-ing/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:460:"

I’m glad the New York Times is covering how to safely cut an avocado, because I’ve messed that up 100% of the time I’ve tried to handle an avocado in the past month. It makes you almost want to forgive them for that green pea guacamole thing.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 06 Jun 2017 04:07:59 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:63:"WPTavern: WordCamp Europe 2017 Livestream Tickets Now Available";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=71286";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:74:"https://wptavern.com/wordcamp-europe-2017-livestream-tickets-now-available";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1075:"

WordCamp Europe will be livestreaming all sessions again this year to make the event accessible to those who are unable to travel to Paris. Live stream tickets are free, but viewers must sign up on the tickets page.

\n

Organizers have also set up a page on the event’s website for people to advertise for buying or selling tickets. Many who have already purchased regular tickets have had a last-minute change of plans, problems with obtaining a visa, or have an extra ticket due to being selected as a speaker or a volunteer. More than two dozen tickets have already been posted for sale.

\n

Regular ticket sales concluded at the end of May, but there are 2,915 livestreaming tickets remaining, along with 272 micro-sponsorship slots at € 150.00 apiece.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 05 Jun 2017 20:07:50 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:88:"WPTavern: Vue.js Creator Evan You Weighs in on WordPress JavaScript Framework Discussion";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=71279";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/vue-js-creator-evan-you-weighs-in-on-wordpress-javascript-framework-discussion";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:8193:"photo credit: JSConf China\n

Last week WordPress core contributors narrowed their considerations for a new JavaScript framework to React and Vue. As the core team has more collective knowledge of working with React, they have reached out to developers with different experiences of using other frameworks in a WordPress context.

\n

One of the chief concerns contributors have regarding Vue is the longevity of the project. I asked Vue creator Evan You if he could weigh in on the topic to give WordPress contributors a better understanding of the project, specifically regarding his efforts to cultivate additional maintainers to help share the load of maintainership.

\n

“I think it’s important to look at the track record – Vue has been around for almost 4 years, and all the work has been done in public on GitHub so anyone can go and check the maintenance history,” You said. “While it has been largely developed by me, the current maintenance is a lot more community-driven. We have active core team members triaging most of the issues and a larger and larger percentage of the issues fixed by community PRs. So – yes, I had already been working on cultivating additional maintainers and will continue to do so.”

\n

You currently receives $10K/month from recurring Patreon donations that fund his full-time efforts working on Vue. Prior to this he also worked at Google and Meteor. During his time at Google, some of the projects You worked on used Angular, which he said he found to be too heavy for his use cases at the time. He built Vue.js to be a more lightweight implementation of the concepts that he liked about Angular.

\n

You also recently said he has learned quite a bit from the React community, which has influenced some of his technical decisions in Vue 2.

\n\n

\n

“First, Vue 2 uses the same Virtual DOM based rendering model underneath, which was first pioneered by React,” You said. “Introducing a Virtual DOM allowed Vue to expose the power of vdom composition while maintaining the approachability.

\n

“The React community is also very active when there are new problem domains being explored – e.g. state management and CSS management. There are many competing solutions and a lot of inspirations when I was implementing official solutions for Vue.”

\n

Evan You Addresses WordPress Core Contributors’ Misconceptions about Vue.js

\n

You said he has been following WordPress contributors’ discussions on React vs Vue but would not offer an opinion on which is a better choice for the project.

\n

“My answer would obviously be biased, and honestly I’m not in the shoes of the WP core team so I don’t have enough perspective to make a choice,” You said. “However, I can provide feedback on some of the issues being discussed in hope of helping them make a better-informed decision.”

\n

You left a comment on the most recent Javascript meeting notes with clarifications on a few misunderstandings about Vue.js. You addressed the point regarding “embracing JavaScript the language,” as some contributors think Vue’s templating language obscures the underlying JavaScript.

\n

“I think ’embracing JavaScript the language’ is another primitive of React we don’t see in Vue,” Andrew Duthie said during the last meeting.

\n

You’s reply compares Vue’s use of templates as “syntax sugar for view representation on top of HTML” to what he believes to be a similar usage in the case of JSX as view representation on top of JavaScript:

\n

The increasing richness of UI does NOT necessitate putting everything in JavaScript. On the other hand, just because Vue uses templates by default doesn’t mean it allows people to get by without learning JavaScript properly.

\n

Vue’s templates are compiled into JavaScript render functions under the hood and they are actually closer to JavaScript than to traditional string templating. It’s just a layer of syntax sugar on top of the underlying Virtual DOM representation. Think of JSX as syntax sugar for view representation on top of JS; Vue templates are syntax sugar for view representation on top of HTML.

\n

JSX/Raw JS does provide more flexibility when you need to apply direct manipulation of Virtual DOM nodes, this is why Vue also supports render functions. But this is not putting two opposing paradigms under the same tent – it’s simply allowing the user to skip the syntax sugar layer for more control.

\n

You said the idea behind templating on top of render functions is to provide “better approachability,” a concern shared by many other proponents of WordPress adopting Vue.

\n

“Users who are more comfortable with HTML and have simpler use cases could use the template, while users who are already familiar of JSX/render functions can leverage the full power of JS,” You said. “This would fit pretty nicely for the use of WP core: community users who care about approachability have an easier time getting started, while the core team have access to JSX/render functions for advanced use cases.”

\n

You also addressed the concern of longevity by offering more information on Vue’s development processes. He confirmed that the current codebase is largely developed by him alone, but maintenance is spread across a core team with members all over the world.

\n

“Other contributors have lower commit counts because their contributions are all submitted in the form of PRs and we use the ‘Squash and commit’ feature on GitHub so each PR results in only one commit for the contributor,” You said. “We’ve merged close to 500 PRs in the core repo alone, and many more across the organization. Other repos under the vuejs organization, e.g. vuex, vue-router, vuejs.org are also largely maintained by dedicated team members.”

\n

You also offered clarification on questions of stability and future compatibility, as WordPress contributors presented concerns regarding breaking changes in the templating language in Vue 2.0.

\n

“This begs for some clarification: Vue versioning strictly follows semver,” You said. “The only time there had been breaking API changes post 1.0 was the 2.0 bump. The template syntax is part of the API so it’s not going to [break], and in between major version bumps we commit to 100% API backwards compatibility. We take stability very seriously, so do our community and in-production users, including GitLab, Vice, and some of the biggest internet companies in China.”

\n

As many WordPress core contributors have been developing on top of React for years, You’s input offers a more detailed, in-depth look at Vue that contributors have been asking for during various rounds of feedback. The discussion will continue over the next several weeks and contributors plan to include the topic at WordCamp Europe’s contributor summit.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 05 Jun 2017 18:04:37 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:70:"WPTavern: Open Sourcing Mental Illness Surpasses $50K Fundraising Goal";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=71138";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:79:"https://wptavern.com/open-sourcing-mental-illness-surpases-50k-fundraising-goal";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3035:"

\n

Open Sourcing Mental Illness (OSMI), a non-profit organization that raises mental health awareness in the tech community, has surpassed its $50K fundraising goal for 2017. Ed Finkler, who founded OSMI in 2013, left his position as CTO of Graph Story to work full-time on speaking, educating, and providing resources to support mental wellness in the tech and open source communities. As of today, the campaign has raised more than $58,000.

\n

In addition to donations from individuals, OSMI has added several corporate sponsors, including CakeDC, Github, Digital Ocean, and Laravel. CakeDC has designated $1,000/month for 12 months to support Finkler’s salary. Finkler works together with a board of directors and a team of volunteers who also speak at conferences about mental health in tech. Several WordPress companies have also been involved in raising support for OSMI, including WebDevStudios and WP Elevation.

\n

OSMI conducts an annual Mental Health in Tech survey as part of ongoing research. Last year’s survey received more than 1,500 responses and the results underscore the great need for removing the stigma surrounding mental illness in the tech industry. A few examples Finkler highlighted include:

\n
    \n
  • Respondents believe it’s 6 times more likely that discussing a mental health issue with their employer would have a negative consequence, vs a physical health issue.
    • \n
  • Respondents are 3.5 times less likely to bring up a mental health issue in an interview than a physical health issue.
    • \n
  • 87% believe being identified as a person with a mental health issue would hurt their career.
    • \n
  • Only 30% of respondents’ employers provide information about mental health and how to seek help.
    • \n
\n

OSMI offers all of the resources it creates for free. The funds raised in the campaign will help to create more tools, documents, videos, and other educational resources. Finkler is working towards engaging with more HR departments and educating more executive teams. He also plans to use the funds to do more research and employ additional experts to reach more people.

\n

For more information about OSMI’s efforts to improve mental health in the tech industry, check out Jeff Chandler’s recent interview with Finkler on the WP Weekly podcast.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 03 Jun 2017 03:59: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: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:44:"WPTavern: In Case You Missed It – Issue 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:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=71142&preview=true&preview_id=71142";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wptavern.com/in-case-you-missed-it-issue-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:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6022:"photo credit: Night Moves – (license)\n

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

\n

Bob Dunn and Patrick Rauland Host Lift Off Summit

\n

Bob Dunn and Patrick Rauland have partnered up for Lift Off Summit. Between June 19-23, visitors will be able to watch 3-4 videos per day focused on getting more traffic, increasing social interactions, and keeping customers to their online stores. The virtual conference is free to watch.

\n

The Evolution of WordPress Magazine Themes

\n

Alex Denning takes a look back at the evolution of WordPress magazine themes over the last 10 years and offers insights into what might be next for the style.

\n

WordPress magazine themes were a huge deal between 2009-2011. Brian Gardner was able to create a profitable business with a single magazine style theme called Revolution, one of the first themes to display content in ways different from the typical single column blog layout.

\n

Magazine themes are a great chapter of WordPress’ history. Their popularity is why WordPress has featured images and automatic thumbnail generation in core.

\n

Highlights From Season Four of ManageWP’s Ask Me Anything

\n

ManageWP published highlights from season four of Ask Me Anything, a weekly event where members of the WordPress community voluntarily answer any questions submitted.

\n

WordPress 4.8 Field Guide

\n

Everything you need to know to prepare for WordPress 4.8, tentatively scheduled for release on June 8th, is in the field guide.

\n

Take the WPCampus WordPress in Higher Education Survey

\n

WPCampus is once again asking for those who work with WordPress in educational settings to fill out the following survey. This year, three randomly selected participants will receive a free ticket to attend WPCampus in Buffalo, NY, July 14-15.

\n

The data will be used to create a series of reports on how WordPress is used in public schools and higher education. Last year’s survey indicated that misconceptions surrounding WordPress security and scalability are slowing its growth in higher education.

\n

A Plugin for Monitoring Directory Sizes

\n

David Bisset shared a dashboard widget that displays the sizes of directories.

\n\n

\n

Stop Signup Spam Integrates with GiveWP

\n

Stop Signup Spam, a plugin we featured last month now integrates with GiveWP.

\n\n

\n

LED WordPress Badge

\n

George Stephanis unveiled his wifi-enabled light up WordPress badge on Twitter. He ordered the parts and soldered them together himself. You’ll get to see it in person if you’re attending WordCamp Kyoto.

\n\n

\n

Wabster!

\n

In what is a traditional part of this series, I end each issue by featuring a Wapuu design. For those who don’t know, Wapuu is the unofficial mascot of the WordPress project. This week’s edition features a variation of the Wapuu design. Wabster, created by Alison Knott, is the mascot of WordCamp Halifax.

\n

\n

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

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Jun 2017 20:23:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:81:"WPTavern: Chassis Desktop Application for Local WordPress Development 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=71126";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/chassis-desktop-application-for-local-wordpress-development-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:2112:"

\n

Human Made has released its first public beta of Chassis Desktop, an application for local WordPress development. Chassis is a Vagrant-based virtual server and a community project that Human Made has commercially supported since 2012. The new desktop app is in early beta at version 0.2.0 with version 1.0.0 coming soon.

\n

Chassis Desktop was designed with a user-friendly interface suitable for beginners and experts alike. It was built by Bronson Quick and Ryan McCue using Electron and contains code from the create-react-app project.

\n

On first launch the app makes sure that Vagrant and VirtualBox are installed and then guides the user to create a new box. Setting up a new Chassis install or adding Chassis to an existing install is fast and easy with the simple UI. The app also includes keyboard navigation and a built-in terminal for quick access to more control over your box.

\n

\n

Over the years Chassis contributors have created an ecosystem of extensions for things like MailHog, Photon, Memcache, debugging, and other software. These add-ons allow users to tailor their systems to their needs.

\n

Chassis Desktop aims to make it easy for users to manager their Chassis development environments without having to touch the command line. As it is currently in pre-release status, early adopters may discover some bugs. Beta testers are encouraged to log any issues on GitHub.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 02 Jun 2017 03:24:01 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:43:"Dev Blog: WordPress 4.8 Release Candidate 2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:34:"https://wordpress.org/news/?p=4765";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/2017/06/wordpress-4-8-release-candidate-2/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:1160:"

The second release candidate for WordPress 4.8 is now available.

\n

To test WordPress 4.8, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

\n

We’ve made a handful of changes since releasing RC 1 last week. For more details about what’s new in version 4.8, check out the Beta 1, Beta 2, and RC1 blog posts.

\n

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

\n

Happy testing!

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Jun 2017 22:13: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:10:"Mel Choyce";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:36;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:85:"WPTavern: Inpsyde Open Sources Wonolog, a Monolog-based Logging Package 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=71109";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:95:"https://wptavern.com/inpsyde-open-sources-wonolog-a-monolog-based-logging-package-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:1721:"

\n

Inpsyde, a WordPress agency and WordPress.com VIP partner based in Germany, has open sourced Wonolog, a package that integrates Monolog for sophisticated WordPress data logging. Monolog is the most widely used PHP logging library with more than 57 million downloads to date.

\n

Wonolog automatically creates logs that target specific WordPress requests and can be customized with action and filter hooks. Here are a few examples of WordPress data it can log:

\n
    \n
  • Log any failed logins
    • \n
  • Keep track of all WordPress cron requests
    • \n
  • Intercept the WordPress-specific exit function, wp_die(), and log any (direct or indirect) usage
    • \n
  • PHP core notices, warnings and (fatal) errors, uncaught exceptions (as well as PHP 7+ Throwable)
    • \n
  • WordPress core errors such as database errors, HTTP API errors, wp_mail() errors, and 404 errors
    • \n
\n

Wonolog is available as a Composer package and its creators recommend installing at the website level. Inpsyde has been using it successfully in production with different projects for several months. Wonolog requires PHP 5.6 or higher and WordPress 4.6+. A documentation site is available to help new users get started and the project can be found on GitHub.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Jun 2017 20:54: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: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:71:"WPTavern: WPWeekly Episode 275 – The JavaScript Framework Rabbit Hole";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=71102&preview=true&preview_id=71102";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:78:"https://wptavern.com/wpweekly-episode-275-the-javascript-framework-rabbit-hole";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2549:"

In this episode, John James Jacoby and I celebrate WordPress’ 14th birthday. We discuss the removal of HHVM from WordPress’ testing infrastructure and how it was likely the reason PHP 7 gained so many performance improvements.

\n

For a majority of the show, Jacoby and I spoke in-depth on which JavaScript framework WordPress core should choose. We discuss what’s at stake, who might be impacted, and why the discussion and eventual decision is important for WordPress’ future. To round out the show, we share our picks of the week and let you know about upcoming WordCamps.

\n

Stories Discussed:

\n

WordPress Turns 14
\nWordPress Removes HHVM from Testing Infrastructure
\nWordPress Core JavaScript Framework Debate Heats Up, Contributors Narrow Discussion to React vs. Vue

\n

Picks of the Week:

\n

Wapu.us, created by James Tryon, is a place to discover and learn about Wapuu, the unofficial mascot of the WordPress project.

\n

Cavalcade is a scalable job system, designed as a drop-in replacement for WordPress’ built-in pseudo-cron system created by Human Made.

\n

Give is a free WordPress donation management plugin by WordImpress.

\n

WPWeekly Meta:

\n

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

\n

Subscribe To WPWeekly Via Itunes: Click here to subscribe

\n

Subscribe To WPWeekly Via RSS: Click here to subscribe

\n

Subscribe To WPWeekly Via Stitcher Radio: Click here to subscribe

\n

Listen To Episode #275:
\n

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Jun 2017 01:09:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:57:"WPTavern: WP-CLI 1.2.0 Released, Project Unveils New Logo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71086";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:67:"https://wptavern.com/wp-cli-1-2-0-released-project-unveils-new-logo";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3398:"

\n

WP-CLI 1.2.0 was released today with a major overhaul that removes bundled commands from core in favor of maintaining them in distinct packages. This is the second release since the project was brought under the official WordPress umbrella and the first major release since hiring Alain Schlesser as a part-time co-maintainer.

\n

Splitting WP-CLI’s internal commands into separate packages moves the project closer to the goal of having official maintainers for the commands in the future. This new structure for the framework and its commands provides several benefits, as outlined by co-maintainer Daniel Bachhuber in the release post:

\n
    \n
  • While developing, the tests are only run for the specific component you’re working on, making the feedback loop much shorter.
    • \n
  • Individual command packages can be controlled and set up independently, opening up the opportunity for better collaboration.
    • \n
  • Hotfixes and intermediary releases can be published for individual commands, that can then be updated through the built-in package manager.
    • \n
  • Tests run really fast now.
    • \n
  • When you submit a pull request, you don’t have to wait two hours for the tests to run.
    • \n
\n

This release also includes three new commands, along with dozens of command improvements and framework enhancements.

\n
    \n
  • wp config get lists constants and globals defined in wp-config.php
    • \n
  • wp config path gets the path to wp-config.php
    • \n
  • wp db size gets the size of the database and its tables
    • \n
\n

Version 1.2.0 had 43 contributors, a 95% increase in contributors from the previous release. One of the next priorities for maintainers is to improve the contribution workflow. Bachhuber said there are no plans at the moment to bring on additional paid co-maintainers, but they plan to start onboarding more volunteer committers. These are developers who are involved with the project on a regular basis but not necessarily daily or weekly. They have also created a Good First Issues page for new contributors and have started working on a customized dashboard for committers.

\n

WP-CLI Has a New Logo

\n

Bachhuber introduced the project’s new logo today, designed by Chris Wallace and his team at Lift UX. Having an official logo opens up the possibility for WP-CLI swag. Bachhuber said he worked with contributors to create a logo, because “people can develop stronger emotional affinity to brands with logos (myself included).” He is also interested in getting stickers created, particularly ones that glow in the dark, but has not yet found a producer. Bachhuber said he is hoping to have some preliminary WP-CLI swag for WordCamp Europe.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 01 Jun 2017 00:17:15 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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:88:"WPTavern: Pods 2.7 Beta Introduces Flexible Relationships, Rewrites Fields in JavaScript";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71009";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:98:"https://wptavern.com/pods-2-7-beta-introduces-flexible-relationships-rewrites-fields-in-javascript";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2272:"

Pods Framework has released two new versions. Pods 2.6.9 is a maintenance release that includes bug fixes for Pods Templates, Auto Templates, and Pods Shortcodes. Meanwhile, Pods 2.7 beta 1 introduces a new feature called Flexible Relationships.

\n

Flexible Relationships uses WordPress’ media modal that allows users to add or edit records from within the parent record of a relationship. This feature will work on existing relationships once users upgrade to 2.7. Watch the following video to see Flexible Relationships in action.

\n
\n

In addition to providing Flexible Relationships, the fields were rewritten in JavaScript by Phil Lewis, Contributing Developer to Pods Framework.

\n

“Phil Lewis of our team rewrote our file upload and relationship fields in what we’re calling Dynamic Field Views which will allow us to convert all of our field types to be JavaScript powered,” Scott Kingsley Clark, lead developer of Pods Framework said.

\n

“The JavaScripts frameworks behind it are Marionette + Backbone. We wrote it with React in mind so we can convert it over whenever React.js is included in core and things settle there”

\n

The development team is asking for as many users as possible to test Flexible Relationships on a staging or testing site so issues can be addressed before its release, tentatively scheduled for the middle of July. Those interested in testing can download the beta from Pods’ GitHub repository.

\n

Testers are encouraged to download the GitHub Updater plugin, created by Andy Fragen, as it makes it easier to download updates from GitHub. If you participate in the testing process, be sure to add ‘2.7’ to any feature, enhancement requests, or bugs that you find when creating a new issue.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 31 May 2017 20:37:40 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:89:"WPTavern: GitHub Introduces Temporary Interaction Limits to Promote Healthier Discussions";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=71072";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:100:"https://wptavern.com/github-introduces-temporary-interaction-limits-to-promote-healthier-discussions";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:5118:"

\n

GitHub is continuing to make good on its promise to improve the platform for open source maintainers and communities with its new temporary interaction limits. The feature was introduced this week as a way for project maintainers to manage participation in heated discussions.

\n

Public repositories, especially those for projects with millions of users, can occasionally have issues or pull requests that become overrun with comments from anyone who has an opinion. Repository owners can now set a 24-hour “cool down period” to limit interaction (commenting, creating pull requests, and opening issues) to existing users, prior contributors, and/or repository collaborators.

\n

\n

Temporary Interaction Limits can help mitigate the effects of “brigading,” as one Hacker News commenter called it – when someone directs a large number of people to an issue from Twitter, Reddit, or other social channels in an attempt to influence the outcome of a discussion. Limiting the discussion to prior contributors or collaborators can help keep input focused around the ideas of those who are already invested in the project.

\n

Reactions to the new feature have been mostly positive, although some users don’t anticipate using it much since GitHub added emoji reactions to conversations last year. In addition to keeping threads from becoming unreadable with numerous +1’s, emoji reactions as an option for expression should help limit interactions from those prone to “drive-by” commenting.

\n

A curated repository of “GitHub Drama,” which includes projects like Bower, Docker, Django, and NodeJS, lists many instances wherein temporarily limiting interaction may have changed the overall tone of the discourse. However, some users questioned the feature’s usefulness in responses on Twitter and some see it as a way of purposely cutting outside voices out of the conversation.

\n\n

\n\n

\n\n

\n

In order for temporary interaction limiting to be useful to projects where locking down the whole repository would be too drastic of a measure, GitHub would need to extend it to include the ability to lock down individual issues and pull requests. Some users have also requested a convenient way for repository members to warn an individual without spamming the entire thread or to put specific users in a cool down period.

\n

“If it’s a legit heated discussion and you limit it, then you’re just [going] to come back in 24 hours to very long, impossible-to-follow responses,” Kris Siegel, Senior Engineer at PlayStation, commented on the related Hacker News thread. “At least this has been my experience when people have left things to cool down them come back and need to respond to everything.”

\n

GitHub is aiming to promote healthier discussions with the new interaction limiting feature, but every project’s community is unique and maintainers may not be able to predict user reactions to locking down an entire repository. If the feature is turned on when a new user is attempting to create their first pull request, it may hinder future contribution. Open source project maintainers should carefully consider the effects of silencing non-contributors when using the feature.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 31 May 2017 20:35:21 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:41;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:47:"HeroPress: Building A WordPress Career in India";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=1874";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:136:"https://heropress.com/essays/building-wordpress-career-india/?utm_source=rss&utm_medium=rss&utm_campaign=building-wordpress-career-india";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10728:"Pull Quote: Give your children the room to grow.

6 years back, I’d have never thought I would be where I am right now. At that time, I was a 12-year-old wondering how softwares were made. Despite the fact that I was born in a middle-class Indian family, my parents never forced me to opt for something I wasn’t interested in. Unlike other middle-class Indian children, the bar of expectations wasn’t set that high and I think it turned out to be for the best.

\n

My parents always supported me and constantly motivated me to learn whatever I liked. Eventually, from wondering about how software was made, I started wondering same about websites. For some reason, I felt more interested in websites than software. For starters, I felt coding in HTML was easier than working with C/C++

\n

Now that I’ve bored you already, let’s get to know each other too. I am Suyogya Shukla, a WordPress developer from Kanpur, India. I work with ThemeIsle as a Support Ninja where I make sure our users are always happy with our products. Let’s go ahead now.

\n

The Journey

\n

At the age of 12; still in class 6th, I started to learn about web coding. I started with HTML and learned how to make a really basic webpage. After understanding the basic concepts I wanted to start making a website already. I went ahead and googled – “How to make a free website” and the webs.com’s listing lead the page. I immediately clicked on it and started playing around, until I realized that it was WYSIWYG editor and it wasn’t possible for me to customize it a lot (Not that I knew how to!)

\n

At this time I had no idea about domain names and hosting. I researched some more and was introduced to the process of putting your website online, but it cost money! I decided to make a small website locally and then show it to my dad hoping he’d be impressed and provide me with the money I needed to put it online. While learning HTML, I came across this cool language called  “CSS” which would apparently make a website look and work better.

\n

Next thing you know, I was all over w3schools.com and YouTube watching videos about CSS, playing with the examples and much more. It took me a good 2 weeks to understand the basic concepts. I could finally change fonts, play with colors and do a lot more! While I liked how I had more control when I coded my own website, I still missed the easy content management webs.com and other WYSIWYG tools offered. This had me thinking again. What free software can I use to have the same level of control over my website but is just as easy to use when it comes to content management? This, in turn, initiated another research and I was finally introduced to this awesome software which went by the name of “WordPress”!

\n

Over the years I would work on a lot of WordPress based websites and continue to learn more about it every day. I worked for various small design agencies, as a freelancer and a lot more until one fine day in 2016 when I saw a “hiring” notice on ThemeIsle’s website and decided to give it a shot. After an initial trial period of some 2 weeks, I was hired. I worked part-time (three hours/day, to be exact) for a year because I had school. Two months back, I started working full time. I work with the support and development team (more involved in support as of now, but I eventually want to get into full-time development) where I continue to learn new things every day.

\n

It’s a Real Career Option!

\n

For everyone who thinks WordPress is just a blogging tool, you’re wrong! Sure, it’s a blogging tool but it is used for so much more. It’s a real career option with a lot of room for growth. Given you are passionate about WordPress and the technologies used in it, you’d be able to find a job easily.

\n

The best thing about the WordPress ecosystem is the people. They’re just so nice!

\n

WordPress ecosystem is indeed competitive like any other but in the best way possible. Even if you’re another company wanting to know how some other company manages things or what technologies they use, they won’t hesitate to tell you about it. Almost all of the WordPress enthusiasts go to WordCamps where they meet new people and share knowledge.

\n

Another good thing about choosing WordPress as a career? The flexibility. A large part of the people who work on WordPress, do it remotely. The company WordPress.com, Automattic, is a completely distributed team with people working from different parts of the world. Want even more reasons to choose WordPress? The earning potential. Companies in the WordPress ecosystem are known to pay generously and the best part? You get to work with the folks who are just as passionate about WordPress as you are.

\n

Engineering isn’t the only way to go

\n

This is for all the Indian parents who are pushing their children to join coachings for IIT and other examinations right now, without their children wanting to – DON’T. Engineering isn’t the only way one can get a job. Sure, there’s nothing wrong with it but forcing your children to do it because you think there’s no other way? That isn’t right.

\n

Introduce your children to WordPress, introduce them to the world of web programming and see if they like it. Why not promote them to do something they like than to burden them with the weight of engineering when they don’t like it?

\n

For all I know if my parents had forced me into engineering I would’ve missed out on everything. Give your children the room to grow.

\n

Make them learn new things, introduce them to WordPress and all other cool things ( not just tech related! ) and leave it up to them to choose a career path 🙂

\n

Working Remotely Is Fun

\n

Let’s talk about working remotely now. It’s fun. You don’t have to wear a suit or any kind of uniform. You get to work in your PJs. Does it get any better than that? Oh wait, it does. You get to choose your working hours. You can decide to work 3hrs in morning and 3hrs at night or you can work 6hours at a stretch. Fellow night crawler? You can work at night. Apart from that, it gives you a lot of freedom. You can work from wherever you want. You can go to a beach and work. You can work while traveling, basically, you can decide to work from anywhere, anytime! It’s all up to you.

\n

Flexible working hours allow me to concentrate on learning new things on a personal level and maintain a healthy Work/ Life balance. But over time, you might get bored working from home. ( Not sure about you but it did happen with me! )

\n

My two cents? Take some time out and go vacationing.

\n

Join a co-working space and see if that helps. All in all, I love having the freedom to work from anywhere and the best part still remains that I can work while wearing my PJs.

\n

What’s Next?

\n

Let me put it this way; I love WordPress. I have been doing some UI/UX work for a while now and I liked it. I am planning to learn more about it while learning more about WordPress development in parallel. For now, I am starting a small WordPress studio, Made With WP, with my friends (and colleagues) – Hardeep and Rohit. You might remember Hardeep talking about it in his essay. It’s the same project. I am working on my first WordPress theme and hope to see it in the theme directory soon. I am pretty good with HTML, CSS and comfortable with JS and PHP and I plan to learn more about them.

\n

Apart from that, I am the co-organizer of WordCamp Kanpur. I have been to two WordCamps so far and run an active meetup in my hometown, Kanpur. I gave my 12th exams this year and I plan to study more about new things as much as I can. Also, I am 18 years old as I write this.

\n

The post Building A WordPress Career in India 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, 31 May 2017 12:00:31 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Suyogya Shukla";s: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:110:"WPTavern: WordPress Core JavaScript Framework Debate Heats Up, Contributors Narrow Discussion to React vs. Vue";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=70985";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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/wordpress-core-javascript-framework-debate-heats-up-contributors-narrow-discussion-to-react-vs-vue";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:10702:"photo credit: oskay Small Parts – (license)\n

WordPress core contributors met this morning to continue the discussion on selecting a new JavaScript framework for use with new core features. The discussion on the Make/Core post intensified over the weekend with more Vue.js proponents commenting to add their thoughts.

\n

Adam Silverstein and Andrew Duthie facilitated this morning’s meeting and began by opening up the discussion to include other frameworks such as Preact, Angular, and Ember. However, the discussion quickly narrowed to React vs Vue.

\n

Silverstein encouraged participants to remember that the new framework is for use with new features such as the new editor and that they will continue to use Backbone when it is the right tool, as well as in existing JavaScript. He also emphasized that the discussion pertains to a framework for core and developers are free to use whatever framework they choose to build plugins or themes.

\n

Vue.js Proponents Consider “Ease of Learning” an Important Factor in Selecting a New Framework

\n

Ease of learning is not among the criteria contributors identified for selecting a new framework, but it is one of the major concerns for Vue.js proponents.

\n

“Vue can do everything that React can do and is much more approachable,” Justin Kopepasah said. “There is a huge adoption of Vue and growth does not show any signs of stopping. Some of the top open source frameworks have adopted Vue and it is used by the top three tech companies in China (including Alibaba). While I do agree that React is a good choice as well, it is not highly approachable by new developers and has Facebook behind it which can be very alarming for people in many ways (not just tech).”

\n

Justin Tadlock, a core contributor whose code and tutorials have assisted many developers learning WordPress, shared similar thoughts over the weekend on the Mare/Core post:

\n

I’ve tried React on a few occasions. Even with over 10 years of programming experience, it was tough to grok for me. I can’t imagine trying to learn it as someone new to WP development.

\n

Vue is dead simple to start learning. I had a small app up and going in minutes. In a couple of hours, I was building some cool, form-related stuff without the docs.

\n

If it were entirely up to me, I’d push for WP to build its own JS framework that solves the problems specific to WordPress. But, if we’re going to choose an existing framework, go with Vue.

\n

Matias Ventura, an Automattic engineer and contributor on both the Calypso and Gutenberg projects, is a proponent of WordPress adopting React. He contends that considering which is easier to learn is the wrong focus for determining what WordPress’ future interfaces will need.

\n

“In my opinion, instead of ‘easier to get started,’ we need to look at robust programming paradigms and an expressive approach to coding interfaces,” Ventura said. “This is what I fundamentally take from Matt’s ‘learn JavaScript deeply’ – the corollary being that WordPress becomes a platform for teaching JavaScript to new programmers, and we need to take that seriously, not just as a convenience to us in the short term.”

\n

Ventura also noted that WordPress has historically not been successful in attracting JavaScript developers and the JS interfaces in core lack contributors when compared to the PHP side.

\n

“We have an opportunity to make WordPress development more appealing to a newer generation of developers that learned how to code through JavaScript,” Ventura said. He encouraged other participants to examine the kinds of interfaces that WordPress needs to modernize and select the best framework for handling them in core.

\n

“The ‘easier to get started’ [argument] seems a bit fallacious to me,” Ventura said. “Easier to whom? At what cost to properly learning JavaScript? The demands of rich interfaces in web applications require a deeper understanding of the technologies used. That’s not something we can avoid. JavaScript cannot be seen as mere progressive enhancement anymore as it is the language in which modern interfaces are expressed.”

\n

Contributors are Concerned about React being Backed by Facebook

\n

At the moment, React is more established and more widely adopted than Vue, but contributors are concerned about the framework being backed and licensed by Facebook. In addition to concerns over the interpretation of React’s additional patent grant, the company has been the source of numerous controversies regarding censorship, data mining, and privacy, among other issues. Opponents don’t want to see WordPress hitch its wagon to Facebook by using React in core.

\n

“The adoption of React is much more than adding a library to WordPress: it is adding the culture, business practices, and code base led by a tech giant,” Justin Kopepasah said. “If we include React in Core, in a way we are asking users (from single site owners to enterprise) to accept Facebook has a key role in the future of WordPress. I have little doubt this will cause pause for some companies considering to adopt WordPress.”

\n

However, other contributors have concerns about Vue.js’ longevity, because it’s so heavily dependent on its creator Evan You. You funds his efforts on Patreon but the project doesn’t have any major corporate backing.

\n

“I’m uncomfortable relying on a project run by a single person that could disappear,” React proponent and WP REST API co-lead Ryan McCue said. “Being run by a corporation with a stake in the game means long-term support and relative stability.” McCue also noted that React has a “a massive community of teaching and support out there for people learning.”

\n

Many Feel WordPress Selecting React as the New JS Framework is a Foregone Conclusion

\n

Despite all the discussions in meetings and on Make/Core posts, many onlookers and community members are convinced that WordPress choosing React is a foregone conclusion. At the beginning of last week’s discussion it seemed that most core contributors are in favor of React, but a strong contingent of Vue proponents have turned out to add comments to the discussion.

\n

Selecting React appears to be the only viable choice when the criteria from the beginning includes items like “proven in a WordPress context” and “alignment with Calypso.” Many have commented to say that the criteria is biased and they assume the decision was already made through the backchannels with a public discussion held for “optics.” Automattic engineer James Nylen commented last week on an open ticket for the Gutenberg project, saying that “Per recent discussion in core Slack, WP core has basically decided to adopt React.”

\n

“If this was truly meant to be a community discussion, then why is it taking place now?” WordPress developer Christopher A. commented on our recent post that summarized the initial discussion. “Choosing a view framework should have happened before the first line of Gutenberg was written. It was known from the start that a view framework would be needed. It was Matt’s desire to get it off the ground as quickly as possible. The best way to accomplish this was to utilize Automattic developers who have experience with React.”

\n

WordPress is selecting a JavaScript framework at a time where frameworks are rapidly evolving, but contributors involved in the decision said they will preserve the ability for theme and plugin developers to use any framework they choose to build their products. No framework was selected during today’s meeting and Andrew Duthie said he expects the conversation will continue at WordCamp Europe’s contributor summit.

\n

“As to React vs Vue (vs Angular vs …), we’ve been discussing the arguments for and against each in the weekly chat, and we’re intentionally taking it slow,” Ryan McCue said. “The key criteria that we’ve picked come from what the project needs, and are not intended to bias the decision in a specific direction. Calypso and other projects are a strong signal towards React, but they’re not the ultimate argument (if they were, we wouldn’t even be discussing it).”

\n

McCue said he doesn’t see WordPress replacing the whole admin with Calypso in a way that doesn’t allow developers to use whatever they choose for their own extensions. The decision to adopt a JavaScript framework for core is more for making core developers’ work easier. At this time, core developers working on new features have a greater knowledge of React than other frameworks.

\n

“At the end of the day, we need to make a decision on what to use in core, and that decision directly impacts the people working on core,” McCue said. “Picking one framework over another doesn’t mean the others are worse, it’s just us (as core contributors) trying to make our own development easier.”

\n

A summary of the discussion should be posted to the Make/Core blog soon and the discussion on selecting a new JavaScript framework will continue in future meetings.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 30 May 2017 23:15:50 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}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:68:"BuddyPress: Building Bridges between Students and Educators in Nepal";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:32:"https://buddypress.org/?p=266185";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:88:"https://buddypress.org/2017/05/building-bridges-between-students-and-educators-in-nepal/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:9319:"
This is a guest post by Arjun Bhattarai (aju29), Founder and Developer of StudentsNepal.com. He is currently working towards a Masters degree in Economics.
\n

Peer reviewed by @boonebgorges

\n

StudentsNepal.com logged in

\n

StudentsNepal.com is the first and largest community website for students of Nepal with 9,700 registered members and 50,000 subscribers. The site helps students find answers to popular courses and colleges by acting as a bridge between the students and educators/educational organizations.

\n

Background

\n

I started working on this side project in December 2014. I remembered I had very little information about courses and colleges I could choose from after finishing Higher Secondary level back in 2011. There were no websites that could readily help students to explore the various opportunities available in Nepal. There are still a lot of students in Nepal who have been brain-fed that studying abroad is the one and only option to be successful. My vision was to change this mindset among the young students of Nepal by informing them about the abundant opportunities and options available within the country.

\n

The goal for creating StudentsNepal is to increase communication among different students with different educational backgrounds while helping them to learn all sorts of information and get hold of educational resources. Communication and interaction are the core values of StudentsNepal and these are the features that help the platform stand out from rest of the educational websites. BuddyPress and bbPress have helped us to achieve these values in a cost effective and efficient way. The beauty of these plugins is that our members can create content and help to rank us higher with search engines.

\n

Implementation

\n

The investment to create StudentsNepal.com was very low, a fraction of my pocket money during my final years in college. It is now one of the top educational portals of Nepal. Since WordPress was so easy to master, my dev team and I were able to use most of our free time to create initial content and other valuable resources for our visitors – students, parents, and educators – rather than spending time/money coding from scratch or buying a proprietary platform.

\n

Before choosing BuddyPress, I researched open-source social network scripts and platforms. My shortlist included WordPress (BuddyPress), Joomla (JomSocial), and Drupal (social modules). It was clear to me, after reading a lot of support forum posts and articles, that the BuddyPress/WordPress combo was the way to move forward with my dream. I am really happy about this choice today. The other heavyweight plugins that I added were GravityForms, Sucuri, bbPress, and MyCred plus other smaller plugins for specific tasks.

\n

Customizations & Improvements

\n

1. Login and Registration Pages
\nWe found out that the default login and registration pages made it difficult for members to log in and have kept site visitors from registering. We resolved the issues by installing the Gravity Forms plugin and adding log in integration via Facebook, Twitter, or Google+ as well as making the registration page more user-friendly.

\n

studentsnepal login screen

\n

2. Newsletters
\nI thought about adding a newsletter because I loved the way some of the blogs I subscribed to sent organized information and recent activities of the blog in a beautiful email format. I decided to add an optin form to start collecting names and emails 2 to 3 months after launching the site. During the first 6 months, only first names and emails were collected with the popup optin form. Later, I changed the optin forms to collect email addresses and phone numbers. I have been using the free package of mailmunch for optin forms (popups) and Amazon AWS for sending newsletters. The newsletter contains scholarship notices for different universities/colleges, student stories, youth events, and other useful academic information.

\n

The newsletters have become one of the most popular features for the community. We did a lot of testing for the positioning and timing of the popup to get the most sign ups. StudentsNepal had around 20,000 subscribers by the end of 2015. The number of subscribers started growing after I inserted the forms in all the subdomains. (news.studentsnepal.com, jobs.studentsnepal.com, quiz.studentsnepal.com, blog.studentsnepal.com). After 3 years, the site has 50,000+ subscribers.

\n

Currently, StudentsNepal sends 1 newsletter per week, and my dev team and I are planning to make it 2 newsletters per week. We had invited students and educators/institutions to contribute content for the newsletters and the response has been just great! Students, particularly, submit generously and regularly to benefit other members, subscribers, and online visitors.

\n

In addition, this project has also helped me connect with lots of awesome individuals and similar-minded startup owners.

\n

3. Design and CSS tweaks
\nOut of the box, BuddyPress has a plain and simple design and interfaces which can be customized easily. At the end of the day, the features and performance are what matters most to my users whether on mobile, tablet, or desktop. For me, due to extensibility and ease of customization, BuddyPress reigns as king when it comes to a free open source script for a social network.

\n

Forums Archive

\n

4. Upgrading Servers
\nStudentsNepal.com was on a shared hosting plan when I launched it in 2014. It took around 3 to 4 months to cross the benchmark of 500 visitors/day. After getting articles indexed in search engines and started getting higher ranks, StudentsNepal started getting a lot of visitors (especially from Google). Mid-2015 we upgraded to VPS hosting when the website’s articles and contents started getting listed on the 1st page of search engines and it started getting a couple of thousand visitors daily. Based on my experience, it’s a good decision to get a shared hosting plan while the site was starting out and then upgrade to more powerful hosting plan when data showed the increases in user engagement and participation.

\n

With a community of 9,700 registered members, 50k subscribers, and around 150k visitors/month, I am happy to say that our site runs smoothly with nary a downtime on all devices. If you install BuddyPress, you will need a bit more power on your server.

\n

Fast Forward

\n

Future plans for StudentsNepal.com include moving the Shopping and Jobs sections to separate domains and setting up a new site for online classes. I am testing Woocommerce, WP Job Manager, and Moodle for the other projects to expand our services to the community.

\n

If you are creating a site for any niche community and are not sure on which platform to choose, I definitely suggest using WordPress with BuddyPress. These have a lot of stable and robust add-on plugins to help you create awesome and feature-rich communities.

\n

StudentsNepal.com is the first website of its nature in Nepal and it has garnered a lot of media attention and praise. I received a lot of positive and encouraging messages from educators and students in Nepal for creating this platform. I’m just glad that the services provided by the site have been very helpful to so many Nepalese students as well to those who would like to study in Nepal.

\n

Thanks to WordPress and BuddyPress for making this site possible. If you want to learn more about the site or the other customizations implemented, please feel free to contact me. Also, I can help you promote your social network or other related websites with a guest post in the blog section of StudentsNepal.com 😀

\n
Arjun Bhattarai Arjun Bhattarai is a member of the Association of Chartered Certified Accountants (ACCA) and is currently working towards MA (Economics) at Tribhuwan University, Nepal. Apart from writing and playing with code, he loves swimming and watching sci-fi videos.
\nLinks: Facebook, Linkedin
\n

 

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 30 May 2017 19:18:06 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"@mercime";s: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:28:"Matt: A Delicious Compliment";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=47422";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"https://ma.tt/2017/05/a-delicious-compliment/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:780:"

Once a little boy sent me a charming card with a little drawing on it. I loved it. I answer all my children’s letters—sometimes very hastily—but this one I lingered over. I sent him a card and I drew a picture of a Wild Thing on it. I wrote, “Dear Jim: I loved your card.” Then I got a letter back from his mother and she said, “Jim loved your card so much he ate it.” That to me was one of the highest compliments I’ve ever received. He didn’t care that it was an original Maurice Sendak drawing or anything. He saw it, he loved it, he ate it.

\n

From Maurice Sendak, the author of Where the Wild Things Are.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 29 May 2017 17:43:54 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s: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: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:18:"Matt: WordPress 14";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=47405";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:35:"https://ma.tt/2017/05/wordpress-14/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:868:"

\n

Today is 14 years from the very first release of WordPress. The interface I’m using to write this (Calypso) is completely unrecognizable from what WordPress looked and worked like even a few years ago. Fourteen years in, I’m waking up every day excited about what’s coming next for us. The progress of the editor and CLI so far this year is awesome, and I’m looking forward to that flowing into improvements for customization and the REST API. Thanks as always to Mike for kicking off this crazy journey, all the people chipping in to make WordPress better, and Konstantin and Erick for surprising me with the cool cake above.

";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_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, 28 May 2017 02:38:33 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:4:"Matt";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:46;a:6:{s:4:"data";s:13:"\n \n \n \n \n \n \n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:2:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:44:"WPTavern: In Case You Missed It – Issue 20";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wptavern.com?p=70879&preview=true&preview_id=70879";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wptavern.com/in-case-you-missed-it-issue-20";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:6987:"photo credit: Night Moves – (license)\n

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

\n

WordPress Turns 14 Years Old

\n

WordPress turns 14 years old tomorrow. David Bisset celebrates the occasion and mentions four things he wants to see in the next year.

\n

WordPress 4.8 Dev Notes

\n

As the WordPress 4.8 release date draws near, component maintainers are publishing dev notes for the features they worked on. So far, the following dev notes have been published:

\n\n

Keep an eye on Make WordPress Core for further dev notes.

\n

HeroPress Announces Educational Scholarship Winners

\n

HeroPress has announced the winners of the WPShout Up and Running educational scholarships. Birgit Olzem, in Gerolstein, Germany, was one of the winners chosen.

\n\n

\n

A WordPress Plugin That Renames Excerpt to TL;DR

\n

The other day, I was thinking about how the TL;DR (Too long, didn’t read) summary of articles is similar to the way Excerpts work in WordPress. I browsed the plugin directory to see if anyone had created a plugin that renamed Excerpts to TL;DR.

\n

I wasn’t surprised when I discovered TL;DR created by Ozh Richard. It hasn’t been updated in more than two years so it won’t show up in casual searches. It simply renames Excerpt to TL;DR using a filter to replace a string with custom text.

\n

Human Made Shares Handbook

\n

Human Made, a WordPress development agency based in the UK, has published its handbook that includes on boarding practices, health and safety policies, and their hiring process.

\n

While it’s not a perfect fit for every one, it provides an in-depth look at the principles the company values. The company provides a number of great employee benefits. Take their bereavement policy for example.

\n

What’s in Matt’s Backpack?

\n

Matt Mullenweg provided an update on what he’s carrying around in his backpack. While it’s filled with technology, ear buds, and the like, the item that stands out to me is the fidget spinner.

\n

If you don’t know what a fidget spinner is, this article by Live Science is a good primer.

\n

Organizing WordCamps and Developing the Finnish Community

\n

A great article that describes the Finnish WordPress community and what transpired after switching the name of WordCamp Finland to WordCamp Helsinki.

\n

What’s in a name? Organizing WordCamps and developing the Finnish community

\n

\n

Five Things To Know about Video Headers

\n

Deborah Edwards-Onoro, of Lireo Designs, shares five things you should know about video headers, a feature that was introduced in WordPress 4.7.

\n

Marketing Tips and Experiences

\n

Scott Bolinger, shares what has and hasn’t worked in his marketing efforts:

\n

“I’ve had my nose stuck in product code on and off for 3 years now, but recently I’ve decided to shift my focus to marketing. This is something I’ve done before, and it seems to come in cycles, depending on what my business needs.

\n

Over the years I’ve tried many different things related to marketing, most of them have fallen short. A few things have worked, I thought I’d share some of my journey up to this point.”

\n

Women Who WordPress Wapuu!

\n

In what is a traditional part of this series, I end each issue by featuring a Wapuu design. For those who don’t know, Wapuu is the unofficial mascot of the WordPress project.

\n

The Women Who WP Wapuu represents the Women Who WP group. The group is dedicated to inspiring, connecting, challenging, and educating women throughout the WordPress community, through referrals, networking, workshops and mentorship focused on professional development and WordPress.

\n

The Women Who WP Wapuu pin was a huge hit at WordCamp Chicago earlier this year. If you’d like to purchase one, Wapu.us has 11 available for $6 each.

\nWomen Who WordPress Wapuu\n

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

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 May 2017 21:48:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:60:"WPTavern: WordPress Removes HHVM from Testing Infrastructure";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=70862";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wptavern.com/wordpress-removes-hhvm-from-testing-infrastructure";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3249:"

\n

Before the release of PHP 7 in 2015, many WordPress managed hosting companies looked to Facebook’s HHVM to provide better performance. Pagely, WP Engine, and SiteGround added HHVM hosting options in 2014 and early 2015. However, PHP 7 performance gains have been enough to preclude wider HHVM adoption.

\n

WordPress core developer John Blackbourn announced yesterday that the project has removed HHVM support in the Travis test suite after April 2017 stats showed a mere several dozen WordPress websites running on HHVM. WordPress never officially supported HHVM but Scott Taylor made many improvements to core for better HHVM compatibility three years ago. Blackbourn clarified on Slack that WordPress is not removing this support but rather will no longer include HHVM in its testing infrastructure.

\n

“Support for HHVM itself hasn’t been dropped, but support for testing WordPress on HHVM has been dropped,” Blackbourn said. “HHVM usage is so minuscule (literally in the dozens according to update stats) that we can’t warrant the time needed to ensure the test infrastructure works.”

\n

The change isn’t likely to affect too many developers, but it’s an important milestone that signifies how well PHP 7 has been performing for sites that have switched. Blackbourn suggests those running WordPress on HHVM should consider switching to PHP 7+, as it is “far more widely supported and tested, and offers all of the memory and performance benefits that HHVM pushed forward.”

\n

The open source MongoDB project also announced yesterday that it will no longer be supporting its HHVM driver, saying it no longer makes good use of contributors’ engineering time.

\n

“At the start of 2015 we began work on an HHVM driver for MongoDB, as part of our project to renew our PHP driver,” Derick Rethans, MongoDB engineer and author of Xdebug, said. “Back then, HHVM was in its ascendancy and outperforming PHP 5.6 two to one. With such a huge performance difference it was reasonable to assume that many users would be switching over…With PHP 7 released, we saw very little use of the HHVM driver for MongoDB.”

\n

These announcements may be the start of more open source projects giving HHVM compatibility a lower priority. On the ticket for removing HHVM from the test matrix on Travis, John Blackbourn thanked HHVM for its importance in helping move PHP forward.

\n

“The PHP world owes a lot to HHVM for helping it push it forward,” Blackbourn said. “Without HHVM, maybe we wouldn’t have seen such incredible performance gains in PHP 7.”

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 May 2017 19:07:30 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:60:"WPTavern: Rainmaker Digital to Partner with Nimble Worldwide";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"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=70828";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:71:"https://wptavern.com/rainmaker-digital-to-partner-with-nimble-worldwide";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:3341:"

Rainmaker Digital, formerly known as Copyblogger Media, has entered into a letter of intent to partner with Nimble Worldwide, a marketing agency based in Dallas, TX. Assets from both companies will be combined into a new entity with Rainmaker Digital being the majority owner. Brian Clark, CEO of Rainmaker Digital, says the partnership enables them to transform from a Software as a Service provider to Software and Services.

\n

“People need sophisticated marketing technology, yes — but they also need done-for-them services such as design, content, and lead generation strategy,” Clark said.

\n

“In that last year, we’ve explored several viable ways to do more for our customers and prospects as a hybrid technology and digital marketing service provider. After careful deliberation, we’ve come up with a path that allows us to expertly provide anything that a Rainmaker user needs.”

\n

This isn’t the first time both companies have worked together. Prior to RainMail, Rainmaker’s in-house email marketing service, the company used Nimble Worldwide as its email marketing provider. Although the partnership brings in a number of new employees under Rainmaker Digital, Clark admits that they had to let some employees go.

\n

“This deal provides instant access to an experienced team of digital marketing professionals and a network of talented contractors that ensures our service solutions are expertly crafted and delivered,” Clark said. “This grows the Rainmaker team significantly, without the pain and uncertainty of building an agency from scratch.”

\n

“The change in business model unfortunately left four of our existing employees without positions, along with the loss of some of our own contractors. That was certainly no fun, and our operations leadership preserved every job possible despite the significant reorganization.”

\n

Before the end of June, customers will no longer be able to purchase services à la carte. Instead, sales of the platform will be more hands on, bundled with services, and prices will significantly increase. Customers who start a free trial before the end of June will be able to use the platform at a cheaper rate and without the bundled service components.

\n

Genesis Framework Remains a Priority

\n

StudioPress, Synthesis, Copyblogger, Authority, and DCI are not part of the deal and remain separate entities. Clark says StudioPress sales are going strong and the Genesis Framework is still a priority.

\n

“Our Synthesis managed WordPress hosting line will be folded into the StudioPress brand at some point, which shows how much we value StudioPress going forward,” he said.

\n

“Genesis is still in the hands of Nathan Rice, and he’s moving it forward at a faster pace than in years past when he had to divide time to work on Rainmaker. Now that he’s free from that, I’m excited to see where he takes the framework, which will continue to be a part of Rainmaker as well.”

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 May 2017 17:24:58 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Jeff Chandler";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i: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:70:"WPTavern: WordPress to Select New JavaScript Framework for Use in Core";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wptavern.com/?p=70794";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:81:"https://wptavern.com/wordpress-to-select-new-javascript-framework-for-use-in-core";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:2892:"

WordPress core contributors have started collaborating more around their JavaScript efforts this year with regular core-js meetings. One item on the most recent meeting’s agenda was discussion on choosing a new JavaScript framework for use in core as an alternative to Backbone.

\n

Contributors began by summarizing the criteria for evaluating framework options, includes factors like stability, longevity, maturity, adoption, accessibility, proven in a WordPress context, and extensibility, among others. Most of the discussion centered on the benefits and drawbacks of React vs Vue.

\n

The majority of those who participated in the meeting seemed to favor React, as it is already used with several major WordPress projects such as Calypso, Gutenberg, and Jetpack. WordPress’ project lead, Matt Mullenweg, has publicly stated that Automattic is betting on React long-term. Mullenweg has also expressed a desire for Calypso, or a similar interface, to replace wp-admin in the future. The company has been building its products on React for several years and is pot committed at this point when it comes to the framework.

\n\n

\n

WordPress officially adopting a JavaScript framework will likely have a ripple effect that will influence how many products in the ecosystem are built and/or re-written. Proponents of Vue.js find it easy to learn and extend. Those who are advocating for React also cite its extensibility, stability, and its proven use with popular WordPress products.

\n

Contributors present for the meeting agreed they would be hesitant to commit a new framework to core without using it in some way for a core feature. The decision has not yet been made. Anyone with experiences to share on implementing JS frameworks in the context of WordPress is invited to comment in the discussion on the meeting notes and join the next core-js meeting Tuesday, May 30, 2017, 8:00 AM CDT.

\n
";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 26 May 2017 02:49:56 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Sarah Gooding";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:8:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Tue, 20 Jun 2017 12:23:49 GMT";s:12:"content-type";s:8:"text/xml";s:4:"vary";s:15:"Accept-Encoding";s:13:"last-modified";s:29:"Tue, 20 Jun 2017 12:15:10 GMT";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 249";s:16:"content-encoding";s:4:"gzip";}}s:5:"build";s:14:"20130911040210";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (305, '_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1498004629', 'no'), (306, '_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9', '1497961429', 'no'), (307, '_transient_timeout_feed_b9388c83948825c1edaef0d856b7b109', '1498004632', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (308, '_transient_feed_b9388c83948825c1edaef0d856b7b109', 'a:4:{s:5:"child";a:1:{s:0:"";a:1:{s:3:"rss";a:1:{i:0;a:6:{s:4:"data";s:3:"\n\n\n";s:7:"attribs";a:1:{s:0:"";a:1:{s:7:"version";s:3:"2.0";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:1:{s:0:"";a:1:{s:7:"channel";a:1:{i:0;a:6:{s:4:"data";s:49:"\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:7:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:29:"Popular — WordPress Plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:29:"https://wordpress.org/plugins";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:57:"Plugins extend and expand the functionality of WordPress.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:13:"lastBuildDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 20 Jun 2017 12:11: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:8:"language";a:1:{i:0;a:5:{s:4:"data";s:5:"en-US";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:9:"generator";a:1:{i:0;a:5:{s:4:"data";s:40:"https://wordpress.org/?v=4.9-alpha-40915";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"item";a:10:{i:0;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:14:"Contact Form 7";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:45:"https://wordpress.org/plugins/contact-form-7/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/plugins/contact-form-7/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 02 Aug 2007 12:43:39 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:48:"https://wordpress.org/plugins-wp/contact-form-7/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:54:"Just another contact form plugin. Simple but flexible.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:16:"Takayuki Miyoshi";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:5025:"

\n

Contact Form 7 can manage multiple contact forms, plus you can customize the form and the mail contents flexibly with simple markup. The form supports Ajax-powered submitting, CAPTCHA, Akismet spam filtering and so on.

\n

Docs & Support

\n

You can find docs, FAQ and more detailed information about Contact Form 7 on contactform7.com. If you were unable to find the answer to your question on the FAQ or in any of the documentation, you should check the support forum on WordPress.org. If you can’t locate any topics that pertain to your particular issue, post a new topic for it.

\n

Contact Form 7 Needs Your Support

\n

It is hard to continue development and support for this free plugin without contributions from users like you. If you enjoy using Contact Form 7 and find it useful, please consider making a donation. Your donation will help encourage and support the plugin’s continued development and better user support.

\n

Recommended Plugins

\n

The following plugins are recommended for Contact Form 7 users:

\n
    \n
  • Flamingo by Takayuki Miyoshi – With Flamingo, you can save submitted messages via contact forms in the database.
    • \n
  • Postman by
    \nJason Hendriks – Postman is a next-generation SMTP Mailer, software that assists in the delivery of email generated by your WordPress site.
    • \n
  • Bogo by Takayuki Miyoshi – Bogo is a straight-forward multilingual plugin that doesn’t cause headaches.
    • \n
\n

Translations

\n

You can translate Contact Form 7 on translate.wordpress.org.

\n

\n
    \n
  1. Upload the entire contact-form-7 folder to the /wp-content/plugins/ directory.
    2. \n
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.
    3. \n
\n

You will find ‘Contact’ menu in your WordPress admin panel.

\n

For basic usage, you can also have a look at the plugin web site.

\n

\n

Do you have questions or issues with Contact Form 7? Use these support channels appropriately.

\n
    \n
  1. Docs
    2. \n
  2. FAQ
    3. \n
  3. Support Forum
    4. \n
\n

Support

\n
\n
Installation Instructions
\n
\n
    \n
  1. Upload the entire contact-form-7 folder to the /wp-content/plugins/ directory.
    2. \n
  2. Activate the plugin through the ‘Plugins’ menu in WordPress.
    3. \n
\n

You will find ‘Contact’ menu in your WordPress admin panel.

\n

For basic usage, you can also have a look at the plugin web site.

\n
\n
\n

\n

For more information, see Releases.

\n

4.8

\n
    \n
  • Stopped using jquery.form.js.
    • \n
  • Added custom REST API endpoints for Ajax form submissions.
    • \n
  • WPCF7_FormTag class implements ArrayAccess interface.
    • \n
  • WPCF7_FormTagsManager::filter() filters form-tags based on features they support.
    • \n
  • New form-tag features: do-not-store, display-block, and display-hidden
    • \n
  • Removed inappropriate content from h1 headings.
    • \n
  • Added the support of size:invisible option to the reCAPTCHA form-tag.
    • \n
\n

4.7

\n
    \n
  • Added REST API custom endpoints to manipulate contact form data.
    • \n
  • Config Validator: Added test items for field names and attachment file paths.
    • \n
  • Added custom DOM events: wpcf7invalid, wpcf7spam, wpcf7mailsent, wpcf7mailfailed and wpcf7submit.
    • \n
  • New action hook: wpcf7_after_flamingo.
    • \n
  • Added size option to select and select* form-tag types.
    • \n
  • Made it possible to use the 3rd parameter of wpcf7_add_form_tag() to specify “features” of the form-tag type.
    • \n
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/contact-form-7/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:1;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:7:"Akismet";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"https://wordpress.org/plugins/akismet/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/akismet/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Oct 2005 08:57:41 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/plugins-wp/akismet/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:103:"Akismet checks your comments and contact form submissions against our global database of spam to…";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:18320:"

\n

Akismet checks your comments and contact form submissions against our global database of spam to prevent your site from publishing malicious content. You can review the comment spam it catches on your blog’s “Comments” admin screen.

\n

Major features in Akismet include:

\n
    \n
  • Automatically checks all comments and filters out the ones that look like spam.
    • \n
  • Each comment has a status history, so you can easily see which comments were caught or cleared by Akismet and which were spammed or unspammed by a moderator.
    • \n
  • URLs are shown in the comment body to reveal hidden or misleading links.
    • \n
  • Moderators can see the number of approved comments for each user.
    • \n
  • A discard feature that outright blocks the worst spam, saving you disk space and speeding up your site.
    • \n
\n

PS: You’ll need an Akismet.com API key to use it. Keys are free for personal blogs; paid subscriptions are available for businesses and commercial sites.

\n

\n

Upload the Akismet plugin to your blog, Activate it, then enter your Akismet.com API key.

\n

1, 2, 3: You’re done!

\n

\n

3.3.2

\n

Release Date – 10 May 2017

\n
    \n
  • Fixed a bug causing JavaScript errors in some browsers.
    • \n
\n

3.3.1

\n

Release Date – 2 May 2017

\n
    \n
  • Improve performance by only requesting the akismet_comment_nonce option when absolutely necessary.
    • \n
  • Fixed two bugs that could cause PHP warnings.
    • \n
  • Fixed a bug that was preventing the “Remove author URL” feature from working after a comment was edited using “Quick Edit.”
    • \n
  • Fixed a bug that was preventing the URL preview feature from working after a comment was edited using “Quick Edit.”
    • \n
\n

3.3

\n

Release Date – 23 February 2017

\n
    \n
  • Updated the Akismet admin pages with a new clean design.
    • \n
  • Fixed bugs preventing the akismet_add_comment_nonce and akismet_update_alert wrapper functions from working properly.
    • \n
  • Fixed bug preventing the loading indicator from appearing when re-checking all comments for spam.
    • \n
  • Added a progress indicator to the “Check for Spam” button.
    • \n
  • Added a success message after manually rechecking the Pending queue for spam.
    • \n
\n

3.2

\n

Release Date – 6 September 2016

\n
    \n
  • Added a WP-CLI module. You can now check comments and recheck the moderation queue from the command line.
    • \n
  • Stopped using the deprecated jQuery function .live().
    • \n
  • Fixed a bug in remove_comment_author_url() and add_comment_author_url() that could generate PHP notices.
    • \n
  • Fixed a bug that could cause an infinite loop for sites with very very very large comment IDs.
    • \n
  • Fixed a bug that could cause the Akismet widget title to be blank.
    • \n
\n

3.1.11

\n

Release Date – 12 May 2016

\n
    \n
  • Fixed a bug that could cause the “Check for Spam” button to skip some comments.
    • \n
  • Fixed a bug that could prevent some spam submissions from being sent to Akismet.
    • \n
  • Updated all links to use https:// when possible.
    • \n
  • Disabled Akismet debug logging unless WP_DEBUG and WP_DEBUG_LOG are both enabled.
    • \n
\n

3.1.10

\n

Release Date – 1 April 2016

\n
    \n
  • Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.
    • \n
  • Fixed a bug that could have resulted in comments that were caught by the core WordPress comment blacklist not to have a corresponding History entry.
    • \n
  • Fixed a bug that could have caused avoidable PHP warnings in the error log.
    • \n
\n

3.1.9

\n

Release Date – 28 March 2016

\n
    \n
  • Add compatibility with Jetpack so that Jetpack can automatically configure Akismet settings when appropriate.
    • \n
  • Fixed a bug preventing some comment data from being sent to Akismet.
    • \n
\n

3.1.8

\n

Release Date – 4 March 2016

\n
    \n
  • Fixed a bug preventing Akismet from being used with some plugins that rewrite admin URLs.
    • \n
  • Reduced the amount of bandwidth used on Akismet API calls
    • \n
  • Reduced the amount of space Akismet uses in the database
    • \n
  • Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.
    • \n
\n

3.1.7

\n

Release Date – 4 January 2016

\n
    \n
  • Added documentation for the ‘akismet_comment_nonce’ filter.
    • \n
  • The post-install activation button is now accessible to screen readers and keyboard-only users.
    • \n
  • Fixed a bug that was preventing the “Remove author URL” feature from working in WordPress 4.4
    • \n
\n

3.1.6

\n

Release Date – 14 December 2015

\n
    \n
  • Improve the notices shown after activating Akismet.
    • \n
  • Update some strings to allow for the proper plural forms in all languages.
    • \n
\n

3.1.5

\n

Release Date – 13 October 2015

\n
    \n
  • Closes a potential XSS vulnerability.
    • \n
\n

3.1.4

\n

Release Date – 24 September 2015

\n
    \n
  • Fixed a bug that was preventing some users from automatically connecting using Jetpack if they didn’t have a current Akismet subscription.
    • \n
  • Fixed a bug that could cause comments caught as spam to be placed in the Pending queue.
    • \n
  • Error messages and instructions have been simplified to be more understandable.
    • \n
  • Link previews are enabled for all links inside comments, not just the author’s website link.
    • \n
\n

3.1.3

\n

Release Date – 6 July 2015

\n
    \n
  • Notify users when their account status changes after previously being successfully set up. This should help any users who are seeing blank Akismet settings screens.
    • \n
\n

3.1.2

\n

Release Date – 7 June 2015

\n
    \n
  • Reduced the amount of space Akismet uses in the commentmeta table.
    • \n
  • Fixed a bug where some comments with quotes in the author name weren’t getting history entries
    • \n
  • Pre-emptive security improvements to ensure that the Akismet plugin can’t be used by attackers to compromise a WordPress installation.
    • \n
  • Better UI for the key entry field: allow whitespace to be included at the beginning or end of the key and strip it out automatically when the form is submitted.
    • \n
  • When deactivating the plugin, notify the Akismet API so the site can be marked as inactive.
    • \n
  • Clearer error messages.
    • \n
\n

3.1.1

\n

Release Date – 17th March, 2015

\n
    \n
  • Improvements to the “Remove comment author URL” JavaScript
    • \n
  • Include the pingback pre-check from the 2.6 branch.
    • \n
\n

3.1

\n

Release Date – 11th March, 2015

\n
    \n
  • Use HTTPS by default for all requests to Akismet.
    • \n
  • Fix for a situation where Akismet might strip HTML from a comment.
    • \n
\n

3.0.4

\n

Release Date – 11th December, 2014

\n
    \n
  • Fix to make .htaccess compatible with Apache 2.4.
    • \n
  • Fix to allow removal of https author URLs.
    • \n
  • Fix to avoid stripping part of the author URL when removing and re-adding.
    • \n
  • Removed the “Check for Spam” button from the “Trash” and “Approved” queues, where it would have no effect.
    • \n
  • Allow automatic API key configuration when Jetpack is installed and connected to a WordPress.com account
    • \n
\n

3.0.3

\n

Release Date – 3rd November, 2014

\n
    \n
  • Fix for sending the wrong data to delete_comment action that could have prevented old spam comments from being deleted.
    • \n
  • Added a filter to disable logging of Akismet debugging information.
    • \n
  • Added a filter for the maximum comment age when deleting old spam comments.
    • \n
  • Added a filter for the number per batch when deleting old spam comments.
    • \n
  • Removed the “Check for Spam” button from the Spam folder.
    • \n
\n

3.0.2

\n

Release Date – 18th August, 2014

\n
    \n
  • Performance improvements.
    • \n
  • Fixed a bug that could truncate the comment data being sent to Akismet for checking.
    • \n
\n

3.0.1

\n

Release Date – 9th July, 2014

\n
    \n
  • Removed dependency on PHP’s fsockopen function
    • \n
  • Fix spam/ham reports to work when reported outside of the WP dashboard, e.g., from Notifications or the WP app
    • \n
  • Remove jQuery dependency for comment form JavaScript
    • \n
  • Remove unnecessary data from some Akismet comment meta
    • \n
  • Suspended keys will now result in all comments being put in moderation, not spam.
    • \n
\n

3.0.0

\n

Release Date – 15th April, 2014

\n
    \n
  • Move Akismet to Settings menu
    • \n
  • Drop Akismet Stats menu
    • \n
  • Add stats snapshot to Akismet settings
    • \n
  • Add Akismet subscription details and status to Akismet settings
    • \n
  • Add contextual help for each page
    • \n
  • Improve Akismet setup to use Jetpack to automate plugin setup
    • \n
  • Fix “Check for Spam” to use AJAX to avoid page timing out
    • \n
  • Fix Akismet settings page to be responsive
    • \n
  • Drop legacy code
    • \n
  • Tidy up CSS and Javascript
    • \n
  • Replace the old discard setting with a new “discard pervasive spam” feature.
    • \n
\n

2.6.0

\n

Release Date – 18th March, 2014

\n
    \n
  • Add ajax paging to the check for spam button to handle large volumes of comments
    • \n
  • Optimize javascript and add localization support
    • \n
  • Fix bug in link to spam comments from right now dashboard widget
    • \n
  • Fix bug with deleting old comments to avoid timeouts dealing with large volumes of comments
    • \n
  • Include X-Pingback-Forwarded-For header in outbound WordPress pingback verifications
    • \n
  • Add pre-check for pingbacks, to stop spam before an outbound verification request is made
    • \n
\n

2.5.9

\n

Release Date – 1st August, 2013

\n
    \n
  • Update ‘Already have a key’ link to redirect page rather than depend on javascript
    • \n
  • Fix some non-translatable strings to be translatable
    • \n
  • Update Activation banner in plugins page to redirect user to Akismet config page
    • \n
\n

2.5.8

\n

Release Date – 20th January, 2013

\n
    \n
  • Simplify the activation process for new users
    • \n
  • Remove the reporter_ip parameter
    • \n
  • Minor preventative security improvements
    • \n
\n

2.5.7

\n

Release Date – 13th December, 2012

\n
    \n
  • FireFox Stats iframe preview bug
    • \n
  • Fix mshots preview when using https
    • \n
  • Add .htaccess to block direct access to files
    • \n
  • Prevent some PHP notices
    • \n
  • Fix Check For Spam return location when referrer is empty
    • \n
  • Fix Settings links for network admins
    • \n
  • Fix prepare() warnings in WP 3.5
    • \n
\n

2.5.6

\n

Release Date – 26th April, 2012

\n
    \n
  • Prevent retry scheduling problems on sites where wp_cron is misbehaving
    • \n
  • Preload mshot previews
    • \n
  • Modernize the widget code
    • \n
  • Fix a bug where comments were not held for moderation during an error condition
    • \n
  • Improve the UX and display when comments are temporarily held due to an error
    • \n
  • Make the Check For Spam button force a retry when comments are held due to an error
    • \n
  • Handle errors caused by an invalid key
    • \n
  • Don’t retry comments that are too old
    • \n
  • Improve error messages when verifying an API key
    • \n
\n

2.5.5

\n

Release Date – 11th January, 2012

\n
    \n
  • Add nonce check for comment author URL remove action
    • \n
  • Fix the settings link
    • \n
\n

2.5.4

\n

Release Date – 5th January, 2012

\n
    \n
  • Limit Akismet CSS and Javascript loading in wp-admin to just the pages that need it
    • \n
  • Added author URL quick removal functionality
    • \n
  • Added mShot preview on Author URL hover
    • \n
  • Added empty index.php to prevent directory listing
    • \n
  • Move wp-admin menu items under Jetpack, if it is installed
    • \n
  • Purge old Akismet comment meta data, default of 15 days
    • \n
\n

2.5.3

\n

Release Date – 8th Febuary, 2011

\n
    \n
  • Specify the license is GPL v2 or later
    • \n
  • Fix a bug that could result in orphaned commentmeta entries
    • \n
  • Include hotfix for WordPress 3.0.5 filter issue
    • \n
\n

2.5.2

\n

Release Date – 14th January, 2011

\n
    \n
  • Properly format the comment count for author counts
    • \n
  • Look for super admins on multisite installs when looking up user roles
    • \n
  • Increase the HTTP request timeout
    • \n
  • Removed padding for author approved count
    • \n
  • Fix typo in function name
    • \n
  • Set Akismet stats iframe height to fixed 2500px. Better to have one tall scroll bar than two side by side.
    • \n
\n

2.5.1

\n

Release Date – 17th December, 2010

\n
    \n
  • Fix a bug that caused the “Auto delete” option to fail to discard comments correctly
    • \n
  • Remove the comment nonce form field from the ‘Akismet Configuration’ page in favor of using a filter, akismet_comment_nonce
    • \n
  • Fixed padding bug in “author” column of posts screen
    • \n
  • Added margin-top to “cleared by …” badges on dashboard
    • \n
  • Fix possible error when calling akismet_cron_recheck()
    • \n
  • Fix more PHP warnings
    • \n
  • Clean up XHTML warnings for comment nonce
    • \n
  • Fix for possible condition where scheduled comment re-checks could get stuck
    • \n
  • Clean up the comment meta details after deleting a comment
    • \n
  • Only show the status badge if the comment status has been changed by someone/something other than Akismet
    • \n
  • Show a ‘History’ link in the row-actions
    • \n
  • Translation fixes
    • \n
  • Reduced font-size on author name
    • \n
  • Moved “flagged by…” notification to top right corner of comment container and removed heavy styling
    • \n
  • Hid “flagged by…” notification while on dashboard
    • \n
\n

2.5.0

\n

Release Date – 7th December, 2010

\n
    \n
  • Track comment actions under ‘Akismet Status’ on the edit comment screen
    • \n
  • Fix a few remaining deprecated function calls ( props Mike Glendinning )
    • \n
  • Use HTTPS for the stats IFRAME when wp-admin is using HTTPS
    • \n
  • Use the WordPress HTTP class if available
    • \n
  • Move the admin UI code to a separate file, only loaded when needed
    • \n
  • Add cron retry feature, to replace the old connectivity check
    • \n
  • Display Akismet status badge beside each comment
    • \n
  • Record history for each comment, and display it on the edit page
    • \n
  • Record the complete comment as originally submitted in comment_meta, to use when reporting spam and ham
    • \n
  • Highlight links in comment content
    • \n
  • New option, “Show the number of comments you’ve approved beside each comment author.”
    • \n
  • New option, “Use a nonce on the comment form.”
    • \n
\n

2.4.0

\n

Release Date – 23rd August, 2010

\n
    \n
  • Spell out that the license is GPLv2
    • \n
  • Fix PHP warnings
    • \n
  • Fix WordPress deprecated function calls
    • \n
  • Fire the delete_comment action when deleting comments
    • \n
  • Move code specific for older WP versions to legacy.php
    • \n
  • General code clean up
    • \n
\n

2.3.0

\n

Release Date – 5th June, 2010

\n
    \n
  • Fix “Are you sure” nonce message on config screen in WPMU
    • \n
  • Fix XHTML compliance issue in sidebar widget
    • \n
  • Change author link; remove some old references to WordPress.com accounts
    • \n
  • Localize the widget title (core ticket #13879)
    • \n
\n

2.2.9

\n

Release Date – 2nd June, 2010

\n
    \n
  • Eliminate a potential conflict with some plugins that may cause spurious reports
    • \n
\n

2.2.8

\n

Release Date – 27th May, 2010

\n
    \n
  • Fix bug in initial comment check for ipv6 addresses
    • \n
  • Report comments as ham when they are moved from spam to moderation
    • \n
  • Report comments as ham when clicking undo after spam
    • \n
  • Use transition_comment_status action when available instead of older actions for spam/ham submissions
    • \n
  • Better diagnostic messages when PHP network functions are unavailable
    • \n
  • Better handling of comments by logged-in users
    • \n
\n

2.2.7

\n

Release Date – 17th December, 2009

\n
    \n
  • Add a new AKISMET_VERSION constant
    • \n
  • Reduce the possibility of over-counting spam when another spam filter plugin is in use
    • \n
  • Disable the connectivity check when the API key is hard-coded for WPMU
    • \n
\n

2.2.6

\n

Release Date – 20th July, 2009

\n
    \n
  • Fix a global warning introduced in 2.2.5
    • \n
  • Add changelog and additional readme.txt tags
    • \n
  • Fix an array conversion warning in some versions of PHP
    • \n
  • Support a new WPCOM_API_KEY constant for easier use with WordPress MU
    • \n
\n

2.2.5

\n

Release Date – 13th July, 2009

\n
    \n
  • Include a new Server Connectivity diagnostic check, to detect problems caused by firewalls
    • \n
\n

2.2.4

\n

Release Date – 3rd June, 2009

\n
    \n
  • Fixed a key problem affecting the stats feature in WordPress MU
    • \n
  • Provide additional blog information in Akismet API calls
    • \n
\n

\n
\n
Installation Instructions
\n
\n

Upload the Akismet plugin to your blog, Activate it, then enter your Akismet.com API key.

\n

1, 2, 3: You’re done!

\n
\n
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:43:"https://wordpress.org/plugins/akismet/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"2";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:2;a:6:{s:4:"data";s:30:"\n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:5:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:9:"Yoast SEO";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:44:"https://wordpress.org/plugins/wordpress-seo/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Mon, 11 Oct 2010 20:55:35 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins-wp/wordpress-seo/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:103:"Improve your WordPress SEO: Write better content and have a fully optimized WordPress site using…";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:13:"Joost de Valk";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:12921:"

\n

WordPress out of the box is already technically quite a good platform for SEO. This was true when Joost wrote his original WordPress SEO article in 2008 (updated every few months) and it’s still true today, but that doesn’t mean you can’t improve it further! This plugin is written from the ground up by Joost de Valk and his team at Yoast to improve your site’s SEO on all needed aspects. While this Yoast SEO plugin goes the extra mile to take care of all the technical optimization, more on that below, it first and foremost helps you write better content. Yoast SEO forces you to choose a focus keyword when you’re writing your articles, and then makes sure you use that focus keyword everywhere.

\n
\n

Premium Support
\n The Yoast team does not always provide active support for the Yoast SEO plugin on the WordPress.org forums. One-on-one email support is available to people who bought the Premium Yoast SEO plugin only.
\n Note that the Premium SEO plugin has several extra features too, including the option to have multiple focus keywords and a redirect manager, so it might be well worth your investment!

\n

You should also check out the Yoast Local SEO, Yoast News SEO and Yoast Video SEO extensions to Yoast SEO. These of course come with support too.

\n

Bug Reports
\n Bug reports for Yoast SEO are welcomed on GitHub. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.

\n
\n

Write better content with Yoast SEO

\n

Using the snippet preview, you can see a rendering of what your post or page will look like in the search results, whether your title is too long or too short, and whether your meta description makes sense in the context of a search result. This way the plugin will help you not only increase rankings but also increase the click through rate for organic search results.

\n

Page Analysis

\n

The Yoast SEO plugins Page Analysis functionality checks simple things you’re bound to forget. It checks, for instance, if you have images in your post and whether they have an alt tag containing the focus keyword for that post. It also checks whether your posts are long enough, whether you’ve written a meta description and if that meta description contains your focus keyword, if you’ve used any subheadings within your post, etc. etc.

\n

The plugin alsgruo allows you to write meta titles and descriptions for all your category, tag and custom taxonomy archives, giving you the option to further optimize those pages.

\n

Combined, this plugin makes sure that your content is the type of content search engines will love!

\n

Technical WordPress Search Engine Optimization

\n

While out of the box WordPress is pretty good for SEO, it needs some tweaks here and there. This Yoast SEO plugin guides you through some of the settings needed, for instance by reminding you to enable pretty permalinks. But it also goes beyond that, by automatically optimizing and inserting the meta tags and link elements that Google and other search engines like so much:

\n

Meta & Link Elements

\n

With the Yoast SEO plugin you can control which pages Google shows in its search results and which pages it doesn’t show. By default, it will tell search engines to index all of your pages, including category and tag archives, but to only show the first pages in the search results. It’s not very useful for a user to end up on the third page of your “personal” category, right?

\n

WordPress itself only shows canonical link elements on single pages, but Yoast SEO makes it output canonical link elements everywhere. Google has recently announced they would also use rel="next" and rel="prev" link elements in the head section of your paginated archives. This plugin adds those automatically. See this post for more info.

\n

XML Sitemaps

\n

The Yoast SEO plugin has the most advanced XML Sitemaps functionality in any WordPress plugin. Once you check the box, it automatically creates XML sitemaps and notifies Google & Bing of the sitemaps’ existence. These XML sitemaps include the images in your posts & pages too, so that your images may be found better in the search engines too.

\n

These XML Sitemaps will even work on large sites, because of how they’re created, using one index sitemap that links to sub-sitemaps for each 1,000 posts. They will also work with custom post types and custom taxonomies automatically, while giving you the option to remove those from the XML sitemap should you wish to.

\n

Because of using XSL stylesheets for these XML Sitemaps, the XML sitemaps are easily readable for the human eye too, so you can spot things that shouldn’t be in there.

\n

RSS Optimization

\n

Are you being outranked by scrapers? Instead of cursing at them, use them to your advantage! By automatically adding a link to your RSS feed pointing back to the original article, you’re telling the search engine where they should be looking for the original. This way, the Yoast SEO plugin increases your own chance of ranking for your chosen keywords and gets rid of scrapers in one go!

\n

Breadcrumbs

\n

If your theme is compatible, and themes based on for instance Genesis or by WooThemes often are, you can use the built-in Breadcrumbs functionality. This allows you to create an easy navigation that is great for both users and search engines, and will support the search engines in understanding the structure of your site.

\n

Making your theme compatible isn’t hard either, check these instructions.

\n

Edit your .htaccess and robots.txt file

\n

Using the built-in file editor, you can edit your WordPress blog’s .htaccess and robots.txt file, giving you direct access to the two most powerful files, from an SEO perspective, in your WordPress install.

\n

Social Integration

\n

SEO and Social Media are heavily intertwined. That’s why this plugin also comes with a Facebook OpenGraph implementation and will soon also support Google+ sharing tags.

\n

Multi-Site Compatible

\n

The Yoast SEO plugin, unlike some others, is fully Multi-Site compatible. The XML Sitemaps work fine in all setups and you even have the option, in the Network settings, to copy the settings from one blog to another, or make blogs default to the settings for a specific blog.

\n

Import & Export functionality

\n

If you have multiple blogs, setting up plugins like this one on all of them might seem like a daunting task. Except that it’s not, because what you can do is simple: you set up the plugin once. You then export your settings and simply import them on all your other sites. It’s that simple!

\n

Import functionality for other WordPress SEO plugins

\n

If you’ve used All In One SEO Pack or HeadSpace2 before using this plugin, you might want to import all your old titles and descriptions. You can do that easily using the built-in import functionality. There’s also import functionality for some of the older Yoast plugins, like Robots Meta and RSS footer.

\n

Should you have a need to import from another SEO plugin to Yoast SEO, or from a theme like Genesis or Thesis, you can use the SEO Data Transporter plugin, which will easily convert your SEO meta data from and to a whole set of plugins like Platinum SEO, SEO Ultimate, Greg’s High Performance SEO, and themes like Headway, Hybrid, WooFramework, Catalyst etc.

\n

Read this migration guide if you still have questions about migrating from another SEO plugin to Yoast SEO.

\n

Yoast SEO Plugin in your Language!

\n

Currently a huge translation project is underway, translating Yoast SEO in as much as 24 languages. So far, the translations for French and Dutch are complete, but we still need help on a lot of other languages, so if you’re good at translating, please join us at translate.yoast.com.

\n

News SEO

\n

Be sure to also check out the premium News SEO module if you need Google News Sitemaps. It tightly integrates with Yoast SEO to give you the combined power of News Sitemaps and full Search Engine Optimization.

\n

Further Reading

\n

For more info, check out the following articles:

\n\n

From within WordPress

\n
    \n
  1. Visit ‘Plugins > Add New’
    2. \n
  2. Search for ‘Yoast SEO’
    3. \n
  3. Activate Yoast SEO from your Plugins page.
    4. \n
  4. Go to “after activation” below.
    5. \n
\n

Manually

\n
    \n
  1. Upload the wordpress-seo folder to the /wp-content/plugins/ directory
    2. \n
  2. Activate the Yoast SEO plugin through the ‘Plugins’ menu in WordPress
    3. \n
  3. Go to “after activation” below.
    4. \n
\n

After activation

\n
    \n
  1. You should see (a notice to start) the Yoast SEO configuration wizard.
    2. \n
  2. Go through the configuration wizard and set up the plugin for your site.
    3. \n
  3. You’re done!
    4. \n
\n

\n

You’ll find answers to many of your questions on kb.yoast.com.

\n

\n

4.9.0

\n

Release Date: June 7th, 2017

\n
    \n
  • \n

    Bugfixes

    \n
      \n
    • Fixes a bug where there were certain assessments missing when switching to cornerstone content.
      • \n
    • Fixes a bug where the configuration wizard button was visible for users who didn’t have enough rights to access the configuration wizard.
      • \n
    • Fixes a bug where the column ID was ambiguous, causing an SQL error.
      • \n
    • Fixes a bug where the category URL in the sitemap was encoded twice.
      • \n
    • Fixes a bug where an old upgrade notice is not removed.
      • \n
    \n
    • \n
  • \n

    Enhancements

    \n
      \n
    • Removes the noodp advanced robots meta value as it is no longer used.
      • \n
    • Loads the translations only when the configuration wizard endpoint is called, instead of every time rest_api_init is called.
      • \n
    \n
    • \n
\n

4.8.0

\n

Release Date: May 23rd, 2017

\n
    \n
  • \n

    Bugfixes

    \n
      \n
    • Fixes a bug where the tabs in the social and advanced metabox section are gone when keyword analysis has been disabled.
      • \n
    \n
    • \n
  • \n

    Enhancements

    \n
      \n
    • Optimizes the way the cornerstone flag is saved.
      • \n
    • Analyzes the content using cornerstone assessors when a post or page is cornerstone content.
      • \n
    \n
    • \n
\n

Earlier versions

\n

For the changelog of earlier versions, please refer to the separate changelog.txt file.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:3;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:24:"Jetpack by WordPress.com";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:38:"https://wordpress.org/plugins/jetpack/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/jetpack/#comments";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 Jan 2011 02:21:38 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:41:"https://wordpress.org/plugins-wp/jetpack/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:112:"The one plugin you need for stats, related posts, search engine optimization, social sharing, 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:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Automattic";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:13334:"

\n

Keep any WordPress site secure, increase traffic, and engage your readers.

\n

Traffic and SEO Tools

\n

Traffic is the lifeblood of any website. Jetpack includes:

\n
    \n
  • [free] Site stats and analytics
    • \n
  • [free] Automatic sharing on Facebook, Twitter, LinkedIn, Tumblr, Reddit, and WhatsApp
    • \n
  • [free] Related posts
    • \n
  • [paid] Search engine optimization tools for Google, Bing, Twitter, Facebook, and WordPress.com
    • \n
  • [paid] Advertising program that includes the best of AdSense, Facebook Ads, AOL, Amazon, Google AdX, and Yahoo
    • \n
\n

Security and Backup Services

\n

Stop worrying about data loss, downtime, and hacking. Jetpack provides:

\n
    \n
  • [free] Brute force attack protection
    • \n
  • [free] Downtime and uptime monitoring
    • \n
  • [free] Secured logins and two-factor authentication
    • \n
  • [paid] Malware scanning, code scanning, and threat resolution
    • \n
  • [paid] Site backups, restores, and migrations
    • \n
\n

Content Creation

\n

Add rich, beautifully-presented media — no graphic design expertise necessary:

\n
    \n
  • [free] A high-speed CDN for your images
    • \n
  • [free] Carousels, slideshows, and tiled galleries
    • \n
  • [free] Simple embeds from YouTube, Google Documents, Spotify and more
    • \n
  • [free] Sidebar customization including Facebook, Twitter, and RSS feeds
    • \n
  • [free] Extra sidebar widgets including blog stats, calendar, and author widgets
    • \n
  • [paid] High-speed, ad-free, and high-definition video hosting
    • \n
\n

Discussion and Community

\n

Create a connection with your readers and keep them coming back to your site with:

\n
    \n
  • [free] Email subscriptions
    • \n
  • [free] Comment login with Facebook, Twitter, and Google
    • \n
  • [free] Fully-customizable contact forms
    • \n
  • [free] Infinite scroll for your posts
    • \n
\n

Expert Support

\n

We have an entire team of Happiness Engineers ready to help you. Ask your questions in the support forum, or contact us directly.

\n

Paid Services

\n

Most of Jetpack’s features and services are free. Jetpack also provides advanced security and backup services, video hosting, site monetization, priority support, and more SEO tools in three simple and affordable plans.

\n

Get Started

\n

Installation is free, quick, and easy. Set up the free plan in minutes.

\n

\n

Automated Installation

\n

Installation is free, quick, and easy. Install Jetpack from our site in minutes.

\n

Manual Alternatives

\n

Alternatively, install Jetpack via the plugin directory, or upload the files manually to your server and follow the on-screen instructions. If you need additional help read our detailed instructions.

\n

\n
\n
Installation Instructions
\n
\n

Automated Installation

\n

Installation is free, quick, and easy. Install Jetpack from our site in minutes.

\n

Manual Alternatives

\n

Alternatively, install Jetpack via the plugin directory, or upload the files manually to your server and follow the on-screen instructions. If you need additional help read our detailed instructions.

\n
\n
Is Jetpack Free?
\n
\n

Yes! Jetpack’s core features are and always will be free.

\n

These include: site stats, a high-speed CDN for images, related posts, downtime monitoring, brute force attack protection, automated sharing to social networks, sidebar customization, and many more.

\n
\n
Should I purchase a paid plan?
\n
\n

Jetpack’s paid services include automated backups, security scanning, spam filtering, video hosting, site monetization, SEO tools, and priority support.

\n

If you’re interested in learning more about the extra layers of protection and advanced tools available, learn more about our paid plans.

\n
\n
Why do I need a WordPress.com account?
\n
\n

Since Jetpack and its services are provided and hosted by WordPress.com, a WordPress.com account is required for Jetpack to function.

\n
\n
I already have a WordPress account, but Jetpack isn’t working. What’s going on?
\n
\n

A WordPress.com account is different from the account you use to log into your self-hosted WordPress. If you can log into WordPress.com, then you already have a WordPress.com account. If you can’t, you can easily create one during installation.

\n
\n
How do I view my stats?
\n
\n

Once you’ve installed Jetpack your stats will be available on WordPress.com/Stats, on the official WordPress mobile apps, and on your Jetpack dashboard.

\n
\n
How do I contribute to Jetpack?
\n
\n

There are opportunities for developers at all levels to contribute. Learn more about contributing to Jetpack or consider joining our beta program.

\n
\n
\n

\n

5.0

\n
    \n
  • Release date: June 6th, 2017
    • \n
  • Release post: http://wp.me/p1moTy-5hK
    • \n
\n

Enhancements

\n
    \n
  • Several changes to the Jetpack dashboard and notices: alignment tweaks, code refactor, text simplification, and more.
    • \n
  • Changes to the communication layer between your site and WordPress.com, to improve performance and allow you to do more to manage your site from WordPress.com.
    • \n
  • Social menu gets icons for Etsy, Meetup, 500px, and Goodreads.
    • \n
  • Jetpack data sync now better supports WordPress updates, themes changes, widgets, and multisite networks.
    • \n
  • Video is updated to be fully compatible with the upcoming Media Widget.
    • \n
  • Force secure WordPress.com API requests for request body, remove deprecated stats methods, and add new endpoints for post listing and user invitations.
    • \n
  • Jetpack’s Command Line tools can now output information about the primary Jetpack site owner. Try wp jetpack status!
    • \n
  • Custom CSS now supports the animation-fill-mode, fill, and stroke properties.
    • \n
  • Remove the “Menus” item from the WordPress.com toolbar for parity with the toolbar on WordPress.com.
    • \n
  • Improve the display of the Omnisearch results page on sites using an RTL language.
    • \n
  • Trim any white space when adding new email address in the Contact Info Widget.
    • \n
  • Improve the look of your recipes in search engine result pages, when you use the Recipe shortcode.
    • \n
\n

Compatibility Improvements

\n
    \n
  • Improve the connection process for end users and hosts.
    • \n
  • Improve compatibility of Jetpack data sync with WooCommerce and Pet Manager plugins.
    • \n
  • Make sure Jetpack’s SEO Tools don’t conflict with other SEO plugins that may already be active on the site, like Yoast SEO or All In One SEO Pack.
    • \n
\n

Bug Fixes

\n
    \n
  • Add a “Set Up” button when a Personal plan is purchased, but VaultPress isn’t active yet.
    • \n
  • When the Ads feature is active, do not display Ads in RSS feeds.
    • \n
  • Comments do not use Photon for Facebook and Twitter avatars and now avoid non-secure warnings when submitting comments on a HTTP site in Safari.
    • \n
  • Contact form emails are now sent in a way that ensures they are correctly rendered as HTML.
    • \n
  • Properly print the full list of modules when using the sync command in Jetpack’s Command Line Interface (CLI).
    • \n
  • Avoid errors when reordering a lot of Restaurant menu items at once.
    • \n
  • Add a mechanism to detect broken connection states and resolve them.
    • \n
  • Autosaves can now be restored as Markdown.
    • \n
  • Photon no longer conflicts with Facebook’s CDN, local images, and plugins that customize reponsive images.
    • \n
  • Avoid potential PHP notice in Publicize.
    • \n
  • Fix bad jQuery selector in Presentations shortcode.
    • \n
  • Avoid fatal errors for Social Links on sites running PHP 7.1.
    • \n
  • Properly escape button attribute in spellchecker.
    • \n
  • Avoid PHP notices for stats on some sites when user roles are not attributed properly.
    • \n
  • No longer attempt to sync options that do not exist and avoid fatal errors when de/activating plugins.
    • \n
  • Avoid errors when Social Menu functions have already been defined in the theme or in another plugin.
    • \n
  • VideoPress media items now always return their unique ID, and do not trigger any PHP notice.
    • \n
  • Fix style of the EU Cookie Law Widget on themes with specific positioning.
    • \n
  • Use correct time constant to define an hour in Upcoming Events Widget.
    • \n
  • Avoid HTML encoding issues in sitemaps.
    • \n
\n

4.9

\n
    \n
  • Release date: May 2nd, 2017
    • \n
  • Release post: http://wp.me/p1moTy-4Rl
    • \n
\n

Major Enhancements

\n
    \n
  • New “EU Cookie Law Banner”, Flickr, and “Internet Defense League” widgets.
    • \n
\n

Slightly Less Exciting Enhancements

\n
    \n
  • Success notices are automatically dismissed after a short period.
    • \n
  • Removed unused code from “My Jetpack” interface and deprecated an XML-RPC method.
    • \n
  • Contact Form now adds display names to email addresses in the To header.
    • \n
  • Updated multiple unit tests to increase code coverage.
    • \n
  • Development mode now also shows module list.
    • \n
  • Updated the list of locales available in Jetpack.
    • \n
  • Plugin auto-updates only triggered from WordPress.com and now trigger WordPress’ maintenance mode.
    • \n
\n

Performance Improvements

\n
    \n
  • Record comment content modifications and moderation events to make sure comments are always up to date on WordPress.com.
    • \n
  • Sync post deletions, changes to sidebar, user events (addition, removal, and update) and theme installation.
    • \n
  • We now distinguish between a new and an updated attachment.
    • \n
  • Sync plugin and theme names when a related event is triggered including theme updates.
    • \n
\n

Compatibility Improvements

\n
    \n
  • Protect avoid conflicts with other plugins hooking into the log in form.
    • \n
  • Contact Form not auto-activated when Ninja Forms is active.
    • \n
  • WordPess.com REST API now allows HTTP PUT requests.
    • \n
  • Ensure that Jetpack’s Image Widget is fully compatible with the Media Widget soon to be available in WordPress 4.8.
    • \n
\n

Bug Fixes

\n
    \n
  • Fixed wording in Post By Email button when no email address has been generated.
    • \n
  • Fixed a notice in the subscription widget in PHP 7.1
    • \n
  • Properly display VaultPress notices in the Jetpack dashboard.
    • \n
  • VideoPress now included in search results for “video” and fixed positioning of search icon on mobile screens.
    • \n
  • Protect supports IPv6 addresses properly.
    • \n
  • Dashboard avoids API requests being cached on some hosts and avoids errors when Spellchecker is inactive.
    • \n
  • Contact Form message content type is now set properly to restore compatibility with email plugins.
    • \n
  • Ads not displayed in the portfolio projects custom content type.
    • \n
  • Display all sites available in a network, even on large multisite installations.
    • \n
  • Featured Image is always used in tweets posted via Publicize.
    • \n
  • Avoid fatal errors when the exclusion parameter in Related Posts is not a string.
    • \n
  • Allow the removal of all custom title settings in the SEO feature.
    • \n
  • Make sure images are not distorted when Tiled Galleries uses Photon.
    • \n
  • Avoid PHP warnings and errors in the Stats dashboard on Multisite.
    • \n
  • Avoid errors when the Jetpack plugin is deleted.
    • \n
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:43:"https://wordpress.org/plugins/jetpack/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:4;a:6:{s:4:"data";s:33:"\n \n \n \n \n \n\n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:3:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:18:"WordPress Importer";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:49:"https://wordpress.org/plugins/wordpress-importer/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 20 May 2010 18:48:47 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"category";a:1:{i:0;a:5:{s:4:"data";s:13:"Uncategorized";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:52:"https://wordpress.org/plugins-wp/wordpress-importer/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:101:"Import posts, pages, comments, custom fields, categories, tags and more from a WordPress export file.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Brian Colinger";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4618:"

\n

The WordPress Importer will import the following content from a WordPress export file:

\n
    \n
  • Posts, pages and other custom post types
    • \n
  • Comments
    • \n
  • Custom fields and post meta
    • \n
  • Categories, tags and terms from custom taxonomies
    • \n
  • Authors
    • \n
\n

For further information and instructions please see the Codex page on Importing Content

\n

Filters

\n

The importer has a couple of filters to allow you to completely enable/block certain features:

\n
    \n
  • import_allow_create_users: return false if you only want to allow mapping to existing users
    • \n
  • import_allow_fetch_attachments: return false if you do not wish to allow importing and downloading of attachments
    • \n
  • import_attachment_size_limit: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited)
    • \n
\n

There are also a few actions available to hook into:

\n
    \n
  • import_start: occurs after the export file has been uploaded and author import settings have been chosen
    • \n
  • import_end: called after the last output from the importer
    • \n
\n

\n
\n
Installation Instructions
\n
\n

The quickest method for installing the importer is:

\n
    \n
  1. Visit Tools -> Import in the WordPress dashboard
    2. \n
  2. Click on the WordPress link in the list of importers
    3. \n
  3. Click “Install Now”
    4. \n
  4. Finally click “Activate Plugin & Run Importer”
    5. \n
\n

If you would prefer to do things manually then follow these instructions:

\n
    \n
  1. Upload the wordpress-importer folder to the /wp-content/plugins/ directory
    2. \n
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
    3. \n
  3. Go to the Tools -> Import screen, click on WordPress
    4. \n
\n
\n
Help! I’m getting out of memory errors or a blank screen.
\n
\n

If your exported file is very large, the import script may run into your host’s configured memory limit for PHP.

\n

A message like “Fatal error: Allowed memory size of 8388608 bytes exhausted” indicates that the script can’t successfully import your XML file under the current PHP memory limit. If you have access to the php.ini file, you can manually increase the limit; if you do not (your WordPress installation is hosted on a shared server, for instance), you might have to break your exported XML file into several smaller pieces and run the import script one at a time.

\n

For those with shared hosting, the best alternative may be to consult hosting support to determine the safest approach for running the import. A host may be willing to temporarily lift the memory limit and/or run the process directly from their end.

\n

— WordPress Codex: Importing Content

\n
\n
\n

\n

0.6.3

\n
    \n
  • Add support for import term metadata.
    • \n
  • Fix bug that caused slashes to be stripped from imported content.
    • \n
  • Fix bug that caused characters to be stripped inside of CDATA in some cases.
    • \n
  • Fix PHP notices.
    • \n
\n

0.6.2

\n
    \n
  • Add wp_import_existing_post filter. See: https://core.trac.wordpress.org/ticket/33721
    • \n
\n

0.6

\n
    \n
  • Support for WXR 1.2 and multiple CDATA sections
    • \n
  • Post aren’t duplicates if their post_type’s are different
    • \n
\n

0.5.2

\n
    \n
  • Double check that the uploaded export file exists before processing it. This prevents incorrect error messages when
    \nan export file is uploaded to a server with bad permissions and WordPress 3.3 or 3.3.1 is being used.
    • \n
\n

0.5

\n
    \n
  • Import comment meta (requires export from WordPress 3.2)
    • \n
  • Minor bugfixes and enhancements
    • \n
\n

0.4

\n
    \n
  • Map comment user_id where possible
    • \n
  • Import attachments from wp:attachment_url
    • \n
  • Upload attachments to correct directory
    • \n
  • Remap resized image URLs correctly
    • \n
\n

0.3

\n
    \n
  • Use an XML Parser if possible
    • \n
  • Proper import support for nav menus
    • \n
  • … and much more, see Trac ticket #15197
    • \n
\n

0.1

\n
    \n
  • Initial release
    • \n
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:5;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:11:"WooCommerce";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:42:"https://wordpress.org/plugins/woocommerce/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/woocommerce/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Tue, 27 Sep 2011 15:32:48 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:45:"https://wordpress.org/plugins-wp/woocommerce/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:97:"WooCommerce is a powerful, extendable eCommerce plugin that helps you sell anything. Beautifully.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:9:"WooThemes";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:40601:"

\n

WooCommerce is a free eCommerce plugin that allows you to sell anything, beautifully. Built to integrate seamlessly with WordPress, WooCommerce is the world’s favorite eCommerce solution that gives both store owners and developers complete control.

\n

With endless flexibility and access to hundreds of free and premium WordPress extensions, WooCommerce now powers 30% of all online stores — more than any other platform.

\n\n

Sell anything, anywhere

\n

With WooCommerce, you can sell both physical and digital goods in all shapes and sizes, offer product variations, multiple configurations, and instant downloads to shoppers, and even sell affiliate goods from online marketplaces.

\n

With premium extensions, you can offer bookings, memberships, and recurring subscriptions. Perhaps you’d like to sell monthly subscriptions for physical goods, or offer your members a discount on digital downloads? It’s all possible.

\n

Ship wherever you like

\n

Offer free shipping, flat rate shipping, or make real-time calculations. Limit your shipments to specific countries, or open your store up to the world. Shipping is highly configurable, and WooCommerce even supports drop shipping.

\n

Extensive payment options

\n

WooCommerce comes bundled with the ability to accept major credit cards, PayPal, BACS (bank transfers), and cash on delivery. Need additional options? More than 140 region-specific gateways integrate with WooCommerce, including popular choices like Stripe, Authorize.Net, and Amazon Payments.

\n

You control it all — forever

\n

WooCommerce gives you complete control of your store, from taxes to stock levels to customer accounts. Add and remove extensions, change your design, and switch settings as you please. It’s all under your control.

\n

One of the biggest risks of using a hosted eCommerce platform is what happens to your store if the provider closes up shop. With WooCommerce, you have complete control, so there’s never any reason to worry. Your data belongs to you — and it’s kept secure, thanks to regular audits by industry leaders.

\n

Define your style with Storefront

\n

Storefront is a free WordPress theme available to any WooCommerce store. Along with deep WooCommerce integration, Storefront prioritizes speed and uptime while eliminating theme and plugin conflicts during major updates.

\n

Define your style even further by customizing Storefront to your liking or choosing from one of our several Storefront child themes. It’s all up to you, and all open source.

\n

Built with developers in mind

\n

Extendable, adaptable, and open source — WooCommerce was created with developers in mind. With its strong, robust framework, you can scale your client’s store all the way from basic to high-end (infinity and beyond).

\n

Built with a REST API, WooCommerce can integrate with virtually any service. Your store’s data can be accessed anywhere, anytime, 100% securely. WooCommerce allows developers to easily create, modify, and grow a store that meets their specifications.

\n

No matter the size of the store you want to build, WooCommerce will scale to meet your requirements. With a growing collection of more than 300 extensions, you can enhance each store’s features to meet your client’s unique needs — or even create your own solution.

\n

If security is a concern, rest easy. WooCommerce is audited by a dedicated team of developers working around the clock to identify and patch any and all discovered bugs.

\n

We also support WooCommerce and all its extensions with comprehensive, easily-accessible documentation. With our docs, you’ll learn how to create the exact site your client needs.

\n

Extensions galore

\n

WordPress.org is home to some amazing extensions for WooCommerce, including:

\n\n

Keen to see them all? Search WordPress.org for ‘WooCommerce’ to dive in.

\n

If you’re looking for something endorsed and maintained by the developers who built WooCommerce, there are a plethora of premium eCommerce extensions, the most popular of which include:

\n\n

And there’s plenty more where they came from. Visit our extensions page to find out everything you’re capable of and all that’s possible with premium WooCommerce extensions.

\n

Join our growing community

\n

When you download WooCommerce, you join a community of more than a million store owners, developers, and WordPress enthusiasts. We’re one of the fastest-growing open source communities online, and whether you’re a n00b or a Ninja, we’d love to have you!

\n

If you’re interested in contributing to WooCommerce we’ve got more than 350 contributors, and there’s always room for more. Head over to the WooCommerce GitHub Repository to find out how you can pitch in.

\n

Want to add a new language to WooCommerce? Swell! You can contribute via translate.wordpress.org.

\n

And, finally, consider joining or spearheading a WooCommerce Meetup locally, more about those here.

\n

\n

Minimum Requirements

\n
    \n
  • PHP version 5.2.4 or greater (PHP 5.6 or greater is recommended)
    • \n
  • MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)
    • \n
  • Some payment gateways require fsockopen support (for IPN access)
    • \n
  • WooCommerce 2.5 requires WordPress 4.1+
    • \n
  • WooCommerce 2.6 requires WordPress 4.4+
    • \n
\n

Visit the WooCommerce server requirements documentation for a detailed list of server requirements.

\n

Automatic installation

\n

Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.

\n

In the search field type “WooCommerce” and click Search Plugins. Once you’ve found our eCommerce plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”.

\n

Manual installation

\n

The manual installation method involves downloading our eCommerce plugin and uploading it to your webserver via your favourite FTP application. The WordPress codex contains instructions on how to do this here.

\n

Updating

\n

Automatic updates should work like a charm; as always though, ensure you backup your site just in case.

\n

If on the off-chance you do encounter issues with the shop/category pages after an update you simply need to flush the permalinks by going to WordPress > Settings > Permalinks and hitting ‘save’. That should return things to normal.

\n

Dummy data

\n

WooCommerce comes with some dummy data you can use to see how products look; either import dummy_data.xml via the WordPress importer or use our CSV Import Suite plugin to import dummy_data.csv and dummy_data_variations.csv.

\n

\n
\n
Installation Instructions
\n
\n

Minimum Requirements

\n
    \n
  • PHP version 5.2.4 or greater (PHP 5.6 or greater is recommended)
    • \n
  • MySQL version 5.0 or greater (MySQL 5.6 or greater is recommended)
    • \n
  • Some payment gateways require fsockopen support (for IPN access)
    • \n
  • WooCommerce 2.5 requires WordPress 4.1+
    • \n
  • WooCommerce 2.6 requires WordPress 4.4+
    • \n
\n

Visit the WooCommerce server requirements documentation for a detailed list of server requirements.

\n

Automatic installation

\n

Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.

\n

In the search field type “WooCommerce” and click Search Plugins. Once you’ve found our eCommerce plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking “Install Now”.

\n

Manual installation

\n

The manual installation method involves downloading our eCommerce plugin and uploading it to your webserver via your favourite FTP application. The WordPress codex contains instructions on how to do this here.

\n

Updating

\n

Automatic updates should work like a charm; as always though, ensure you backup your site just in case.

\n

If on the off-chance you do encounter issues with the shop/category pages after an update you simply need to flush the permalinks by going to WordPress > Settings > Permalinks and hitting ‘save’. That should return things to normal.

\n

Dummy data

\n

WooCommerce comes with some dummy data you can use to see how products look; either import dummy_data.xml via the WordPress importer or use our CSV Import Suite plugin to import dummy_data.csv and dummy_data_variations.csv.

\n
\n
Where can I find WooCommerce documentation and user guides?
\n
\n

For help setting up and configuring WooCommerce please refer to our user guide

\n

For extending or theming WooCommerce, see our codex.

\n
\n
Where can I get support or talk to other users?
\n
\n

If you get stuck, you can ask for help in the WooCommerce Plugin Forum.

\n

For help with premium extensions from WooThemes, use our helpdesk.

\n
\n
Will WooCommerce work with my theme?
\n
\n

Yes; WooCommerce will work with any theme, but may require some styling to make it match nicely. Please see our codex for help. If you’re looking for a theme with built in WooCommerce integration we recommend Storefront.

\n
\n
Where can I request new features, eCommerce themes and extensions?
\n
\n

You can vote on and request new features and extensions in our WooIdeas board

\n
\n
Where can I report bugs or contribute to the project?
\n
\n

Bugs can be reported either in our support forum or preferably on the WooCommerce GitHub repository.

\n
\n
Where can I find the REST API documentation?
\n
\n

You can find the documentation of our REST API on the WooCommerce REST API Docs.

\n
\n
WooCommerce is awesome! Can I contribute?
\n
\n

Yes you can! Join in on our GitHub repository 🙂

\n
\n
\n

\n

3.0.8 – 2017-06-06

\n
    \n
  • Fix – Include multi-dimensional array support in oAuth1.0.
    • \n
  • Fix – Stock/backorder notice when stock management is disabled.
    • \n
  • Fix – Handle shipping item taxes if set to avoid the legacy fallback.
    • \n
  • Fix – Variations should inherit purchase_note from parent.
    • \n
  • Fix – Check if subtotal is blank, not empty, before setting for order items.
    • \n
  • Fix – Cancelled email should be send for processing orders, not pending.
    • \n
  • Fix – Missing variable in legacy API.
    • \n
  • Fix – Correct price query when on a post type archive.
    • \n
  • Fix – Missing $ip Variable in geolocation class.
    • \n
  • Fix – A single multi-word attribute is fine for variation titles.
    • \n
  • Fix – Gallery should be updated even if empty in REST API.
    • \n
  • Fix – Fix saving of text attributes with special chars.
    • \n
  • Fix – Undefined index warning when saving variations with stock management disabled.
    • \n
  • Fix – Use meta id instead of key in WC_Order_Item::offsetGet.
    • \n
  • Fix – Format parent stock qty on read.
    • \n
  • Fix – Hide replies from recent reviews widgets.
    • \n
  • Fix – Use formatted weight and dimensions for variations.
    • \n
  • Fix – Ensure we have child before getting price to fix a notice in grouped products.
    • \n
  • Fix – Fixed unicode characters when saving webhook delivery logs.
    • \n
  • Fix – Avoid deprecated ID in legacy API.
    • \n
  • Fix – Add correct args to woocommerce_shipping_zone_method_deleted and woocommerce_shortcode_products_query hooks.
    • \n
  • Fix – Correctly append cache in product widget.
    • \n
  • Fix – Add ability to invalidate cache by object ID.
    • \n
  • Fix – Notice in structured data class.
    • \n
  • Fix – Only delete if an object has an ID in CRUD to avoid wp_delete_post using global ID.
    • \n
  • Fix – Avoid notices on checkout by ensuring all legacy data is correctly set.
    • \n
  • Fix – Add failed to processing event for the processing email.
    • \n
  • Fix – Store user ID and use that to determine if the session should be loaded or not. Ensures user data is correct and shipping calculator data is stored.
    • \n
\n

3.0.7 – 2017-05-16

\n
    \n
  • Fix – Display of grouped product permalinks + names.
    • \n
  • Fix – Ensure wc_get_payment_gateway_by_order has a valid order ID to avoid errors.
    • \n
  • Fix – Ensure get_plugin_updates exists in API.
    • \n
  • Fix – Correctly set rating term after updating product visibility.
    • \n
  • Fix – is_ip_address should be static.
    • \n
  • Fix – Handle clearing for 3, 4, and 5 columns in the product gallery.
    • \n
  • Fix – Some added protection against notices/errors in the assets and variation data-store files.
    • \n
  • Fix – If backorders are enabled, do not make variable products out of stock.
    • \n
  • Fix – Undefined function in class-wc-embed.php.
    • \n
  • Fix – Fix ‘base location’ not being returned via the settings API.
    • \n
  • Fix – When re-filling fields on checkout, only change the empty ones to avoid conflicts with gateway plugins and hidden fields.
    • \n
  • Fix – Make calculate tax function clear taxes if taxes are disabled on recalculation.
    • \n
  • Fix – Update all customer session address fields when updating via checkout.
    • \n
  • Fix – Support customer searches < 3 characters long, but with result limiting.
    • \n
\n

3.0.6 – 2017-05-09

\n
    \n
  • Fix – Fixed conflict between global attributes and custom attributes with the same names.
    • \n
  • Fix – Added missing “id” to API for shipping zone methods to support the CLI.
    • \n
  • Fix – Incorrect use of wc_format_price_range in get_price_html_from_to.
    • \n
  • Fix – Clone each meta object when cloning WC_Data object to avoid modifying original meta stdClass objects.
    • \n
  • Fix – Fix non numeric warning for some order data.
    • \n
  • Fix – Fixed a warning when no customer country is defined for state input.
    • \n
  • Fix – Use term name when reordering so correct data is passed to the new order.
    • \n
  • Fix – Formatting issues in wc_display_item_meta.
    • \n
  • Fix – Check if IP address is valid in IP address detection code.
    • \n
  • Fix – wc_attribute_taxonomy_id_by_name should use wc_sanitize_taxonomy_name to prevent breaking special chars.
    • \n
  • Fix – Correct variable name in order structured data.
    • \n
  • Fix – Prepend new item keys with $items_key to make them unique.
    • \n
  • Fix – Hide offers from structured markup when blank.
    • \n
  • Fix – Fixed “Process to checkout” button color in Twenty seventeen dark theme.
    • \n
  • Fix – Only set reply-to if the email + name is set.
    • \n
  • Fix – Correctly exclude terms in wc_get_related_products.
    • \n
  • Fix – Reset post data prevents grouped products working in shortcodes.
    • \n
  • Fix – Fix min price range comparisons.
    • \n
  • Fix – Properly save order items in legacy REST API.
    • \n
  • Fix – Use correct full size for variation images.
    • \n
  • Fix – Add noscript style for gallery.
    • \n
  • Fix – Fix/duplicate potential stock reduction with paypal.
    • \n
  • Tweak – Improve _wc_term_recount performance.
    • \n
  • Tweak – Improve plugin update detection in system status report to reduce timeouts.
    • \n
  • Tweak – Improve “Save Order” button to reproduce WordPress post/page behavior.
    • \n
  • Tweak – Added zipcode validation for France.
    • \n
  • Dev – Added woocommerce_shop_order_search_results filter.
    • \n
\n

3.0.5 – 2017-04-28

\n
    \n
  • Fix – Tooltip display within shipping zone modals.
    • \n
  • Fix – Fix missing title for actions column on mobile.
    • \n
  • Fix – Allow forward slash in telephone field.
    • \n
  • Fix – Sort grouped products by menu order when displaying.
    • \n
  • Fix – Fix term exclusion in term count queries.
    • \n
  • Fix – Filter invalid products before returning them for wc_get_products.
    • \n
  • Fix – Prevent orders being their own parent (causes errors).
    • \n
  • Fix – Correctly migrate legacy shipping taxes data.
    • \n
  • Fix – Make sure the meta data cache is not shared among instances.
    • \n
  • Fix – Correct the stock display notice when a variable product manages stock for it’s children.
    • \n
  • Fix – On multisite, add user to blog during checkout if not a user to prevent errors.
    • \n
  • Fix – Correct sale price date handling with some timezone setups.
    • \n
  • Fix – wc_attribute_taxonomy_id_by_name needs to use lowercase attribute slug to work.
    • \n
  • Fix – Make changes to the buyer’s company name in the shipping section of checkout persist.
    • \n
  • Tweak – Add required placeholder for meta fields in backend.
    • \n
  • Tweak – Don’t strtolower address strings on checkout validation messages.
    • \n
  • REST API – Prevent password change notification when creating a customer.
    • \n
  • REST API – Removed duplicated items returned in shipping and checkout endpoints.
    • \n
  • CLI – Fixed missing shipping zones route.
    • \n
  • Dev – Make get_price_html handling match 2.6 and pass all values through woocommerce_get_price_html filter.
    • \n
  • Dev – Legacy customer class missing get_address / get_address_2 functions.
    • \n
  • Dev – Restored filter woocommerce_checkout_customer_id during checkout validation.
    • \n
  • Dev – Adds missing $this argument for all woocommerce_payment_complete_order_status filters.
    • \n
\n

3.0.4 – 2017-04-20

\n
    \n
  • Fix – Variations were not inheriting the product image and shipping class ID.
    • \n
  • Fix – Prevent rating/review counts being duplicated when duplicating products.
    • \n
  • Fix – Fixed gallery navigation between images with long captions.
    • \n
  • Fix – Support transparent PNG in the gallery by setting a background color.
    • \n
  • Fix – Removed name/company from the shipping address Google map links.
    • \n
  • Fix – Fixed the address field sorting script on the checkout.
    • \n
  • Fix – Fixed the upgrade routine for grouped products so that parents are unset.
    • \n
  • Fix – Fixed support for WordPress 4.7 user locale settings.
    • \n
  • Fix – Fixed default option filter for product types in the product meta box.
    • \n
  • Fix – Improved the css in Twenty Seventeen for dark color schemes.
    • \n
  • Fix – Fixed display of refunds in sales report.
    • \n
  • Fix – Updated single-product/add-to-cart/variable.php template version to 3.0.0 since it had changes since 2.6.
    • \n
  • Fix – Fixed warnings when product attribute do not exists.
    • \n
  • Fix – Used a div for comment-form-rating to prevent invalid nested markup.
    • \n
  • Fix – Fixed some logic that checks if order taxes are compound.
    • \n
  • Fix – Fixed SKU checks to only exclude products that are trashed.
    • \n
  • Fix – Fixed display of download permissions in first email sent after checkout.
    • \n
  • Fix – Hidden the backorder notification stock text when notification is disabled.
    • \n
  • Fix – Fixed incorrect stock numbers in low stock emails.
    • \n
  • Tweak – Removed the non-functional order total input box, and combined the recalculation buttons into one working button.
    • \n
  • Tweak – Updated Guided Tour videos.
    • \n
  • Tweak – Updated js-cookie.js to 2.1.4.
    • \n
  • Tweak – Updated schema.org URLs to use HTTPS.
    • \n
  • Tweak – Status report request timeouts.
    • \n
  • REST API – Fixed an issue that prevented deleting a term if errors were thrown during creation.
    • \n
  • REST API – Fixed reports endpoint when querying by date.
    • \n
  • REST API – Fixed ignored order parameters when changing order status.
    • \n
  • Dev – Support guest orders in wc_get_orders function.
    • \n
  • Dev – Fixed downloadable variation filters for download URLs.
    • \n
  • Dev – Added safeguards to prevent infinite loops while saving coupons, products and orders in admin.
    • \n
  • Dev – Added a fallback for queue_transactional_email if background sending is disabled.
    • \n
  • Dev – Added has_shipping_address helper method.
    • \n
  • Dev – Introduced woocommerce_order_item_get_formatted_meta_data filter.
    • \n
  • Dev – Made wc_add_order_item pass correct values to woocommerce_new_order_item.
    • \n
  • Dev – Fixed legacy_posted_data access in checkout class.
    • \n
  • Dev – Fixed undefined property notice in WC_Order_Item::offsetGet.
    • \n
  • Dev – Fixed PHP 7.1 warnings when using non-float values to wc_get_weight().
    • \n
  • Dev – Fixed incorrect variable name in wc_add_order_item().
    • \n
\n

3.0.3 – 2017-04-13

\n
    \n
  • Fix – Fixed an issue with variation tax-classes when set to ‘parent’. This made taxes apply on top of the tax inclusive price in certain setups.
    • \n
  • Fix – Escaped attribute translations in the cart.php template and bumped the template version to match.
    • \n
  • Fix – Corrected the display of refund dates on the order screen.
    • \n
  • Fix – Fixed the grouped product visibility check in the grouped.php template and bumped the template version to match.
    • \n
  • Fix – Fixed the sale badge display for grouped products.
    • \n
  • Fix – Added the itemReviewed structured data for product reviews to make it validate.
    • \n
  • Fix – Made the get_attribute method work on variation objects.
    • \n
  • Tweak – Turned off the deferred email sending by default which was added in 3.0. Whilst it does improve performance, there were compatibility problems on some servers. It can be enabled with a filter if desired.
    • \n
  • Dev – Added backtrace information to the deprecation messages to help find problem plugins.
    • \n
\n

3.0.2 – 2017-04-12

\n
    \n
  • Fix – Removed required states for GP, GF, KW, LB, MQ, RE and YT countries.
    • \n
  • Fix – Made cache in the [products] shortcode respect filters from plugins.
    • \n
  • Fix – Added missing woocommerce_cross_sells_columns filter.
    • \n
  • Fix – Fixed shortcode rendering on the shop page.
    • \n
  • Fix – Fixed incorrect sale dates when bulk editing variations.
    • \n
  • Fix – Fixed calls to wc_reduce_stock_levels in PayPal and Simplify gateways.
    • \n
  • Fix – Exclude “location” meta when reading customer meta data.
    • \n
  • Fix – Updated emails/email-addresses.php, emails/email-order-details.php, content-single-product.php, checkout/form-shipping.php, myaccount/form-add-payment-method.php, myaccount/form-edit-address.php, myaccount/form-lost-password.php, myaccount/form-reset-password.php, myaccount/orders.php and myaccount/view-order.php template version to 3.0.0 since they had changes since 2.6.
    • \n
  • Fix – Fixed default behavior of variation tax classes when originally set to “parent”.
    • \n
  • Fix – When duplicating products, do not copy slug, append “(Copy)” to the product name, correctly copy all meta data, and prevent children of grouped products being duplicated too.
    • \n
  • Fix – Removed duplicated items when outputting cross sells on the cart page.
    • \n
  • Fix – Fixed output of default “add to cart” text of external products in loops.
    • \n
  • Fix – Fixed backwards compatibility of guest checkout rules when being altered by plugins directly.
    • \n
  • Fix – Use correct thumbnail sizes for variation images in the new gallery.
    • \n
  • Fix – Fixed captions on thumbnails and main image in the new gallery.
    • \n
  • Fix – Trigger wc_fragments_loaded after add to cart fragment refresh.
    • \n
  • Fix – Download permissions; Convert dates to timestamp on read so UTC is preserved.
    • \n
  • Fix – Fixed notices under PHP 7.1 when sorting products by name (numeric).
    • \n
  • Fix – Added additional checks to ensure objects are read before using class methods to avoid errors.
    • \n
  • Fix – Removed legacy suggest.js code which was causing JS error on bulk edit.
    • \n
  • Fix – Fixed warnings on the “Lost password” page and when loading a product with invalid attributes.
    • \n
  • Fix – Made background emailer update the queue after a successful send so duplicate mails are less likely.
    • \n
  • Fix – Typo in flexslider_enabled option in new gallery script.
    • \n
  • Fix – woocommerce_notify_low_stock and woocommerce_notify_no_stock options had no effect.
    • \n
  • Tweak – For downloadable files, only validate file type when dealing with relative paths.
    • \n
  • Tweak – Improved automatic variation name generation.
    • \n
  • Dev – Added product visibility terms to system status report to help debug.
    • \n
  • Dev – Introduced woocommerce_admin_order_date_format filter to replace missing post_date_column_time.
    • \n
  • Dev – Introduced woocommerce_update_customer_args filter to prevent updates to user objects if needed.
    • \n
  • REST API – Fixed saving of variations in legacy REST API v3.
    • \n
  • REST API – Fixed backwards compatibility of line_items meta in legacy REST API.
    • \n
\n

3.0.1 – 2017-04-06

\n
    \n
  • Fix – Show catalog hidden products within grouped products.
    • \n
  • Fix – Fade in the gallery in if no images are set or it’s custom.
    • \n
  • Fix – Use wc_deprecated_function in WC_Deprecated_Hooks so notices aren’t output in ajax requests.
    • \n
  • Fix – Added back the ability to include extra items to the System Status using the woocommerce_system_status_environment_rows filter.
    • \n
  • Fix – Coupon category restrictions and limits for variations.
    • \n
  • Fix – Allow shortcodes and HTML in variation descriptions like in 2.6.
    • \n
  • Fix – Unset post date when duplicating products.
    • \n
  • Fix – Show a sale price on variable products if on sale and all prices are the same.
    • \n
  • Fix – Corrected download links when a product has multiple downloads.
    • \n
  • Fix – Prevented potential errors if the product type was not posted for any reason on save.
    • \n
  • Fix – Updated single-product/up-sells.php, loop/add-to-cart.php, loop/rating.php, checkout/form-billing.php, and content-product.php template version to 3.0.0.
    • \n
  • Fix – Included clearfixes on billing and shipping field wrappers,
    • \n
  • Fix – Fixed styling of logs table in some languages.
    • \n
  • Fix – Fixed display of variation attributes on old orders.
    • \n
  • Fix – Use placeholder text for external products add to cart button text if left blank.
    • \n
  • Fix – Fallback to home URL if no shop page is set for system status security check for HTTPS.
    • \n
  • Fix – For variations, pull tax status and sold individually from the parent since there is no UI to set this at variation level.
    • \n
  • Fix – Moved cron emails to background processing to avoid multiple sends.
    • \n
  • Fix – Wrapped structured data in a hidden element when added to emails.
    • \n
  • Fix – Missing gateway information in queued emails.
    • \n
  • Fix – Fixed a bug that caused pages to permanently reload if “Default customer location” was set to “Geolocate (with page caching support)”.
    • \n
  • Fix – When forcing shipping to billing, set the shipping fields in the order itself.
    • \n
  • Fix – Check for invalid objects in WC_Register_WP_Admin_Settings.
    • \n
  • Fix – Check for error object in wc_get_object_terms.
    • \n
  • Fix – Removed slashes in shipping meta data on the order edit screen.
    • \n
  • Fix – Prevented permalink rewrites for attributes with missing names.
    • \n
  • Fix – Fixed saving of meta data when multiple extensions use the save_post action.
    • \n
  • Fix – Allow search customers by ID in edit order screen.
    • \n
  • Fix – Prevents session data overwriting customer data on login.
    • \n
  • Fix – Fixed cross-sell column display and variation support.
    • \n
  • Fix – Fixed variable product stock syncing on save.
    • \n
  • Fix – Included try/catch wrapper to prevent issues with Select2.
    • \n
  • Fix – Prevented a bug that deleted all variations when the product type was change from variable to simple.
    • \n
  • Fix – Switched to WPDB to quicker update when syncing titles for variations.
    • \n
  • Fix – Exclude deprecated properties when loading a customer object.
    • \n
  • Fix – Fixed notices while trying to order again.
    • \n
  • Fix – Fixed notices when $wpdb->prefix is empty.
    • \n
  • Fix – Prevent errors when loading a product with an invalid download file types.
    • \n
  • REST API – Fixed missing array declaration in CRUD controller.
    • \n
  • REST API – Removed extra exclude, include and search parameters from taxes endpoint.
    • \n
  • REST API – Fixed variation description formatting.
    • \n
  • REST API – Fixed incorrect attribute check in products endpoint in Legacy REST API.
    • \n
  • REST API – Allow variation image to be unset.
    • \n
\n

3.0.0 – 2017-04-04

\n
    \n
  • New gallery on single product pages with better mobile support, using PhotoSwipe and Zoom. Declare support with add_theme_support() – wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider
    • \n
  • Made the store notice dismissible on the frontend.
    • \n
  • Variable products no longer show striked out prices in combination with ranges for clarity when on sale.
    • \n
  • Prices no longer display as ‘free’ instead of 0, to fix issues with ranges and localization and for consistency.
    • \n
  • Improved structured product data by using JSON-LD instead of inline Microdata.
    • \n
  • Improved downloads list layout (template file).
    • \n
  • Respect stock status and prevent the “out of stock threshold” setting affecting existing in-stock products.
    • \n
  • Improved handling of shop page rewrite rules to allow subpages.
    • \n
  • Redirect to login after password reset.
    • \n
  • When using authorizations in PayPal Standard, automatically capture funds when the order goes processing/completed.
    • \n
  • On multisite, when a user logs into a store with an account on a site, but not the current site, rather than error, add the user to the current site as a customer.
    • \n
  • Show variable weights/dimensions even when parent values are not set.
    • \n
  • Automatically sort tax rates rather than allow clunky manual sorting.
    • \n
  • When deleting a tax rate class, remove it’s tax rates.
    • \n
  • Made WC_Logger pluggable via wc_get_logger function.
    • \n
  • Use ‘average rating’ post meta for ‘rating’ product sorting option.
    • \n
  • Show better labels in nav menus metabox.
    • \n
  • Sort “Recently Viewed” products by the view order.
    • \n
  • Removed internal scroll from log viewer.
    • \n
  • Add reply-to to admin emails.
    • \n
  • Improved the zone setup flow.
    • \n
  • Made wc_get_wildcard_postcodes return the orignal postcode plus * since wildcards should match empty strings too.
    • \n
  • Use all paid statuses in $customer->get_total_spent().
    • \n
  • Move location of billing email field to work with password managers.
    • \n
  • Option to restrict selling locations by country.
    • \n
  • Added tool to clear orphaned variations in system status.
    • \n
  • Remove checkbox options in system status tools and replace with constants.
    • \n
  • Added security section in system status report.
    • \n
  • Add image_url setting to PayPal Standard.
    • \n
  • Fixed attribute registration. Attributes are non-hierarchical by default (parent is not supported).
    • \n
  • Add sort parameter to checkout fields to aid with sorting per locale.
    • \n
  • Merged percent and percent product coupon types (they provide the same discount).
    • \n
  • Prevent payment details being cleared after update_checkout events.
    • \n
  • Performance – Converted _featured and _visibility meta data to terms for faster catalog queries. Upgrade routine handles migration. Developers may need to update queries to reflect this change.
    • \n
  • Includes product attributes archives links in “Additional Information” tab.
    • \n
  • Select2 has been upgraded to v4.
    • \n
  • Improved logging system for extensions.
    • \n
  • Tax suffix is now hidden on non-taxable products.
    • \n
  • Grouped products are linked from the parent rather than the children. Children can be in more than one group.
    • \n
  • Removed coupon usage link in coupons admin screen.
    • \n
  • Performance – Converted rating filters to visibility terms.
    • \n
  • Performance – Added visibility term for outofstock products to speed those queries up also.
    • \n
  • Performance – Introduced a new CRUD (create, read, update, delete) system for Products, Orders, Customers and Shipping Zones.
    • \n
  • Performance – Optimised variable product sync. Upper/lower price meta is no longer stored, just the main prices, if a child has weight, and if a child has dimensions.
    • \n
  • Performance – Removed WP_Query from up-sells.php and related.php and replaced with PHP foreach loop (since we already have the product IDs).
    • \n
  • Performance – Removed the feature where old orders get access to new downloads on product edit. Looping potentially thousands of orders to do this is too much of a performance burden for stores and this can sometimes be unexpected behavior too. This does however updates edited downloads.
    • \n
  • Performance – Removed ‘items’ column on orders screen due to loading excessive data.
    • \n
  • Performance – Deferred email sending for faster checkouts. Now uses CRON.
    • \n
  • API – New Rest API v2 with support for meta_data amongst other things.
    • \n
  • API – Removed last order from customers part of the API due to performance concerns – use orders endpoint instead. Other order data on the endpoint is now transient cached.
    • \n
  • API – Allow oAuth1.0a authentication using headers.
    • \n
  • API – New Shipping Zones endpoints.
    • \n
  • API – New variations endpoints.
    • \n
  • API – New settings endpoints.
    • \n
  • API – Payment gateways and shipping methods endpoints.
    • \n
  • API – Prevented the (broken) ability to manipulate variations directly on the products endpoints.
    • \n
  • CLI – New CLI which uses the REST API endpoints rather than it’s own functions.
    • \n
  • Localization – Improved RTL support.
    • \n
  • Localization – Added a language independent permalink setting function.
    • \n
  • Localization – Added inline comments for placeholder strings.
    • \n
  • Localization – Added Nigerian and Pakistan Provinces to i18n/state.
    • \n
  • Localization – US and Poland postcode validation.
    • \n
  • To read more about this release, see our dev blog announcement here: http://wp.me/p6wtcw-Uo
    • \n
\n

See changelog for all versions.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/woocommerce/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:6;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"All in One SEO Pack";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins/all-in-one-seo-pack/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/plugins/all-in-one-seo-pack/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 30 Mar 2007 19:30:03 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:53:"https://wordpress.org/plugins-wp/all-in-one-seo-pack/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:83:"The original SEO plugin for WordPress, downloaded over 30,000,000 times since 2007.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:8:"uberdose";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:4934:"

\n

Use All in One SEO Pack to optimize your WordPress site for SEO. It’s easy and works out of the box for beginners, and has advanced features and an API for developers.

\n

Upgrade to Pro Version

\n

Premium Support

\n

First created in 2007, see why AIOSEO is one of the all time most downloaded plugins for WordPress.

\n
    \n
  • XML Sitemap support – submit your sitemap to Google and Bing and improve your SEO
    • \n
  • Google AMP support (Accelerated Mobile Pages)
    • \n
  • Google Analytics support
    • \n
  • Support for SEO on Custom Post Types
    • \n
  • Advanced Canonical URLs
    • \n
  • Redirect attachment pages to parent post
    • \n
  • Automatically notifies search engines like Google and Bing about changes to your site
    • \n
  • Built-in API so other plugins/themes can access and extend functionality
    • \n
  • ONLY free plugin to provide SEO Integration for e-Commerce sites, including WooCommerce
    • \n
  • Nonce Security built into All in One SEO Pack
    • \n
  • Automatically optimizes your titles for Google and other search engines
    • \n
  • Generates META tags automatically
    • \n
  • Avoids the typical duplicate content found on WordPress blogs
    • \n
  • For beginners, you don’t even have to look at the options, it works out-of-the-box. Just install.
    • \n
  • For advanced users, you can fine-tune everything to optimize your SEO
    • \n
  • You can override any title and set any META description and any META keywords you want.
    • \n
  • Compatibility with many other plugins
    • \n
  • Translated into 57 languages
    • \n
  • PHP 7 100% Compatible
    • \n
\n

Follow me on Twitter to keep up with the latest updates Michael
\nTorbert

\n

\n

Tags

\n

seo, SEO, All in One, google, meta, meta description, search engine optimization, xml sitemap, xml sitemaps, google sitemap, sitemap, sitemaps, robots meta, rss, rss footer, yahoo, bing, widget, Post, plugin, admin, posts, shortcode, sidebar, twitter, page, images, comments, image, news sitemaps, XML News Sitemaps, WordPress SEO, multisite, canonical, nofollow, noindex, keywords, meta keywords, description, webmaster tools, google webmaster tools, seo pack, schema.org, search engines, custom post types, custom taxonomies, canonical

\n

\n

Please visit our complete Documentation before requesting support for SEO from the
\nAll in One SEO Pack Support Forum

\n

Translations

\n
\n
General Settings
\n
\n

\n
\n
XML Sitemaps
\n
\n

\n
\n
Social Meta
\n
\n

\n
\n
Performance
\n
\n

\n
\n
\n

\n

All in One SEO Pack Changelog

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/all-in-one-seo-pack/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:7;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:19:"Google XML Sitemaps";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/google-sitemap-generator/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:63:"https://wordpress.org/plugins/google-sitemap-generator/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 16 Jun 2005 09:33:19 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:58:"https://wordpress.org/plugins-wp/google-sitemap-generator/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:95:"This plugin will generate a special XML sitemap which will help search engines to better…";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:14:"Arne Brachhold";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:7635:"

\n

This plugin will generate a special XML sitemap which will help search engines like Google, Bing, Yahoo and Ask.com to better index your blog. With such a sitemap, it’s much easier for the crawlers to see the complete structure of your site and retrieve it more efficiently. The plugin supports all kinds of WordPress generated pages as well as custom URLs. Additionally it notifies all major search engines every time you create a post about the new content.

\n

Supported since over 9 years and rated as the best WordPress plugin, it will do exactly what it’s supposed to do – providing a complete XML sitemap for search engines. It will not break your site, slow it down or annoy you. Guaranteed!

\n
\n

If you like the plugin, feel free to rate it (on the right side of this page) or donate via PayPal. I’m gladly supporting this plugin since over 9 years! Thanks a lot! 🙂

\n
\n

Related Links:

\n\n

License

\n

Good news, this plugin is free for everyone! Since it’s released under the GPL, you can use it free of charge on your personal or commercial blog. But if you enjoy this plugin, you can thank me and leave a small donation for the time I’ve spent writing and supporting this plugin. And I really don’t want to know how many hours of my life this plugin has already eaten 😉

\n

Translations

\n

The plugin comes with various translations, please refer to the WordPress Codex for more information about activating the translation. If you want to help to translate the plugin to your language, please have a look at the sitemap.pot file which contains all definitions and may be used with a gettext editor like Poedit (Windows).

\n

\n
    \n
  1. Install the plugin like you always install plugins, either by uploading it via FTP or by using the “Add Plugin” function of WordPress.
    2. \n
  2. Activate the plugin at the plugin administration page
    3. \n
  3. If you want: Open the plugin configuration page, which is located under Settings -> XML-Sitemap and customize settings like priorities and change frequencies.
    4. \n
  4. The plugin will automatically update your sitemap of you publish a post, so there is nothing more to do 🙂
    5. \n
\n

\n
\n
Where can I find the options page of the plugin?
\n
\n

It is under Settings > XML Sitemap. I know nowadays many plugins add top-level menu items, but in most of the cases it is just not necessary. I’ve seen WP installations which looked like an Internet Explorer ten years ago with 20 toolbars installed. 😉

\n
\n
Do I have to create a sitemap.xml and sitemap.xml.gz by myself?
\n
\n

Not anymore. Since version 4, these files are dynamically generated. There must be no sitemap.xml or sitemap.xml.gz in your blog directory anymore! The plugin will try to rename them to sitemap.xml.bak if they still exists.

\n
\n
Does this plugin use static files or “I can’t find the sitemap.xml file!”
\n
\n

Not anymore. Since version 4, these files are dynamically generated just like any other WordPress content.

\n
\n
There are no comments yet (or I’ve disabled them) and all my postings have a priority of zero!
\n
\n

Please disable automatic priority calculation and define a static priority for posts.

\n
\n
So many configuration options… Do I need to change them?
\n
\n

No, only if you want to. Default values are ok for most sites.

\n
\n
Does this plugin work with all WordPress versions?
\n
\n

This version works with WordPress 3.3 and better. If you’re using an older version, please check the Google Sitemaps Plugin Homepage for the legacy releases. There is a working release for every WordPress version since 1.5, but you really should consider updating your WordPress installation!

\n
\n
My question isn’t answered here
\n
\n

Most of the plugin options are described at the plugin homepage as well as the dedicated Google Sitemaps FAQ.

\n
\n
My question isn’t even answered there
\n
\n

Please post your question at the WordPress support forum and tag your post with “google-sitemap-generator”.

\n
\n
What’s new in the latest version?
\n
\n

The changelog is maintained here

\n
\n
Why is the changelog on a separate page and not here?
\n
\n

The WordPress.org repository is just another place to download this plugin. I don’t want to maintain too many pages with the same content. Thank you for your understanding!

\n
\n
\n

\n

You can always find the changelog on the plugin website, since I don’t like to maintain the same content on different pages. Thank you for your understanding!

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:60:"https://wordpress.org/plugins/google-sitemap-generator/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:8;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:20:"Limit Login Attempts";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:51:"https://wordpress.org/plugins/limit-login-attempts/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:59:"https://wordpress.org/plugins/limit-login-attempts/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Thu, 15 Jan 2009 14:20:42 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:54:"https://wordpress.org/plugins-wp/limit-login-attempts/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:91:"Limit rate of login attempts, including by way of cookies, for each IP. Fully customizable.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:11759:"

\n

Limit the number of login attempts possible both through normal login as well as using auth cookies.

\n

By default WordPress allows unlimited login attempts either through the login page or by sending special cookies. This allows passwords (or hashes) to be brute-force cracked with relative ease.

\n

Limit Login Attempts blocks an Internet address from making further attempts after a specified limit on retries is reached, making a brute-force attack difficult or impossible.

\n

Features

\n
    \n
  • Limit the number of retry attempts when logging in (for each IP). Fully customizable
    • \n
  • Limit the number of attempts to log in using auth cookies in same way
    • \n
  • Informs user about remaining retries or lockout time on login page
    • \n
  • Optional logging, optional email notification
    • \n
  • Handles server behind reverse proxy
    • \n
  • It is possible to whitelist IPs using a filter. But you probably shouldn’t. 🙂
    • \n
\n

Translations: Bulgarian, Brazilian Portuguese, Catalan, Chinese (Traditional), Czech, Dutch, Finnish, French, German, Hungarian, Norwegian, Persian, Romanian, Russian, Spanish, Swedish, Turkish

\n

Plugin uses standard actions and filters only.

\n

\n
    \n
  1. Download and extract plugin files to a wp-content/plugin directory.
    2. \n
  2. Activate the plugin through the WordPress admin interface.
    3. \n
  3. Customize the settings on the options page, if desired. If your server is located behind a reverse proxy make sure to change this setting.
    4. \n
\n

If you have any questions or problems please make a post here: https://wordpress.org/tags/limit-login-attempts

\n

\n
\n
Why not reset failed attempts on a successful login?
\n
\n

This is very much by design. Otherwise you could brute force the “admin” password by logging in as your own user every 4th attempt.

\n
\n
What is this option about site connection and reverse proxy?
\n
\n

A reverse proxy is a server in between the site and the Internet (perhaps handling caching or load-balancing). This makes getting the correct client IP to block slightly more complicated.

\n

The option default to NOT being behind a proxy — which should be by far the common case.

\n
\n
How do I know if my site is behind a reverse proxy?
\n
\n

You probably are not or you would know. We show a pretty good guess on the option page. Set the option using this unless you are sure you know better.

\n
\n
Can I whitelist my IP so I don’t get locked out?
\n
\n

First please consider if you really need this. Generally speaking it is not a good idea to have exceptions to your security policies.

\n

That said, there is now a filter which allows you to do it: “limit_login_whitelist_ip”.

\n

Example:
\nfunction my_ip_whitelist($allow, $ip) {
\n return ($ip == ‘my-ip’) ? true : $allow;
\n}
\nadd_filter(‘limit_login_whitelist_ip’, ‘my_ip_whitelist’, 10, 2);

\n

Note that we still do notification and logging as usual. This is meant to allow you to be aware of any suspicious activity from whitelisted IPs.

\n
\n
I locked myself out testing this thing, what do I do?
\n
\n

Either wait, or:

\n

If you know how to edit / add to PHP files you can use the IP whitelist functionality described above. You should then use the “Restore Lockouts” button on the plugin settings page and remove the whitelist function again.

\n

If you have ftp / ssh access to the site rename the file “wp-content/plugins/limit-login-attempts/limit-login-attempts.php” to deactivate the plugin.

\n

If you have access to the database (for example through phpMyAdmin) you can clear the limit_login_lockouts option in the wordpress options table. In a default setup this would work: “UPDATE wp_options SET option_value = ” WHERE option_name = ‘limit_login_lockouts\'”

\n
\n
\n

\n

1.7.1

\n

This version fixes a security bug in version 1.6.2 and 1.7.0. Please upgrade immediately.

\n

“Auth cookies” are special cookies set at login that authenticating you to the system. It is how WordPress “remembers” that you are logged in between page loads.

\n

During lockout these are supposed to be cleared, but a change in 1.6.2 broke this. It allowed an attacker to keep trying to break these cookies during a lockout.

\n

Lockout of normal password login attempts still worked as it should, and it appears that all “auth cookie” attempts would keep getting logged.

\n

In theory the “auth cookie” is quite resistant to brute force attack. It contains a cryptographic hash of the user password, and the difficulty to break it is not based on the password strength but instead on the cryptographic operations used and the length of the hash value. In theory it should take many many years to break this hash. As theory and practice does not always agree it is still a good idea to have working lockouts of any such attempts.

\n

1.7.0

\n
    \n
  • Added filter that allows whitelisting IP. Please use with care!!
    • \n
  • Update to Spanish translation, thanks to Marcelo Pedra
    • \n
  • Updated Swedish translation
    • \n
  • Tested against WordPress 3.3.2
    • \n
\n

1.6.2

\n
    \n
  • Fix bug where log would not get updated after it had been cleared
    • \n
  • Do plugin setup in ‘init’ action
    • \n
  • Small update to Spanish translation file, thanks to Marcelo Pedra
    • \n
  • Tested against WordPress 3.2.1
    • \n
\n

1.6.1

\n
    \n
  • (WordPress 3.0+) An invalid cookie can sometimes get sent multiple times before it gets cleared, resulting in multiple failed attempts or even a lockout from a single invalid cookie. Store the latest failed cookie to make sure we only count it as one failed attempt
    • \n
  • Define “Text Domain” correctly
    • \n
  • Include correct Dutch tranlation file. Thanks to Martin1 for noticing. Thanks again to Bjorn Wijers for the translation
    • \n
  • Updated POT file for this version
    • \n
  • Tested against WordPress 3.1-RC4
    • \n
\n

1.6.0

\n
    \n
  • Happy New Year
    • \n
  • Tested against WordPress 3.1-RC1
    • \n
  • Plugin now requires WordPress version 2.8+. Of course you should never ever use anything but the latest version
    • \n
  • Fixed deprecation warnings that had been piling up with the old version requirement. Thanks to Johannes Ruthenberg for the report that prompted this
    • \n
  • Removed auth cookie admin check for version 2.7.
    • \n
  • Make sure relevant values in $_COOKIE get cleared right away on auth cookie validation failure. There are still some problems with cookie auth handling. The lockout can trigger prematurely in rare cases, but fixing it is plugin version 2 stuff unfortunately.
    • \n
  • Changed default time for retries to reset from 24 hours to 12 hours. The security impact is very minor and it means the warning will disappear “overnight”
    • \n
  • Added question to FAQ (“Why not reset failed attempts on a successful login?”)
    • \n
  • Updated screenshots
    • \n
\n

1.5.2

\n
    \n
  • Reverted minor cookie-handling cleanup which might somehow be responsible for recently reported cookie related lockouts
    • \n
  • Added version 1.x Brazilian Portuguese translation, thanks to Luciano Passuello
    • \n
  • Added Finnish translation, thanks to Ari Kontiainen
    • \n
\n

1.5.1

\n\n

1.5

\n\n

1.4.1

\n
    \n
  • Added Turkish translation, thanks to Yazan Canarkadas
    • \n
\n

1.4

\n
    \n
  • Protect admin page update using wp_nonce
    • \n
  • Added Czech translation, thanks to Jakub Jedelsky
    • \n
\n

1.3.2

\n
    \n
  • Added Bulgarian translation, thanks to Hristo Chakarov
    • \n
  • Added Norwegian translation, thanks to Rune Gulbrands?y
    • \n
  • Added Spanish translation, thanks to Marcelo Pedra
    • \n
  • Added Persian translation, thanks to Mostafa Soufi
    • \n
  • Added Russian translation, thanks to Jack Leonid (http://studio-xl.com)
    • \n
\n

1.3.1

\n
    \n
  • Added Catalan translation, thanks to Robert Buj
    • \n
  • Added Romanian translation, thanks to Robert Tudor
    • \n
\n

1.3

\n
    \n
  • Support for getting the correct IP for clients while server is behind reverse proxy, thanks to Michael Skerwiderski
    • \n
  • Added German translation, thanks to Michael Skerwiderski
    • \n
\n

1.2

\n
    \n
  • No longer replaces pluggable function when cookie handling active. Re-implemented using available actions and filters
    • \n
  • Filter error messages during login to avoid information leak regarding available usernames
    • \n
  • Do not show retries or lockout messages except for login (registration, lost password pages). No change in actual enforcement
    • \n
  • Slightly more aggressive in trimming old retries data
    • \n
\n

1.1

\n
    \n
  • Added translation support
    • \n
  • Added Swedish translation
    • \n
  • During lockout, filter out all other login errors
    • \n
  • Minor cleanups
    • \n
\n

1.0

\n
    \n
  • Initial version
    • \n
\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:56:"https://wordpress.org/plugins/limit-login-attempts/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}i:9;a:6:{s:4:"data";s:39:"\n \n \n \n \n \n \n \n \n \n \n \n ";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";s:5:"child";a:5:{s:0:"";a:6:{s:5:"title";a:1:{i:0;a:5:{s:4:"data";s:16:"TinyMCE Advanced";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:47:"https://wordpress.org/plugins/tinymce-advanced/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:55:"https://wordpress.org/plugins/tinymce-advanced/#respond";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:7:"pubDate";a:1:{i:0;a:5:{s:4:"data";s:31:"Fri, 22 Jun 2007 06:02:53 +0000";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:4:"guid";a:1:{i:0;a:5:{s:4:"data";s:50:"https://wordpress.org/plugins-wp/tinymce-advanced/";s:7:"attribs";a:1:{s:0:"";a:1:{s:11:"isPermaLink";s:5:"false";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:11:"description";a:1:{i:0;a:5:{s:4:"data";s:58:"Extends and enhances TinyMCE, the WordPress Visual Editor.";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:32:"http://purl.org/dc/elements/1.1/";a:1:{s:7:"creator";a:1:{i:0;a:5:{s:4:"data";s:10:"Andrew Ozz";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:40:"http://purl.org/rss/1.0/modules/content/";a:1:{s:7:"encoded";a:1:{i:0;a:5:{s:4:"data";s:10701:"

\n

This plugin will let you add, remove and arrange the buttons that are shown on the Visual Editor toolbar. You can configure up to four rows of buttons including Font Sizes, Font Family, text and background colors, tables, etc. It will also let you enable the editor menu, see the screenshots.

\n

It includes 15 plugins for TinyMCE that are automatically enabled or disabled depending on the buttons you have chosen. In addition this plugin adds some commonly used options as keeping the paragraph tags in the Text editor and importing the CSS classes from the theme’s editor-style.css.

\n

Some of the features added by this plugin

\n
    \n
  • Support for creating and editing tables.
    • \n
  • More options when inserting lists.
    • \n
  • Search and Replace in the editor.
    • \n
  • Ability to set Font Family and Font Sizes.
    • \n
  • And many others.
    • \n
\n

With this plugin you can also enable the TinyMCE menu above the toolbars. This will make the editor even more powerful and convenient.

\n

\n

Best is to install directly from WordPress. If manual installation is required, please make sure that the plugin files are in a folder named “tinymce-advanced” (not two nested folders) in the WordPress plugins folder, usually “wp-content/plugins”.

\n

\n
\n
Installation Instructions
\n
\n

Best is to install directly from WordPress. If manual installation is required, please make sure that the plugin files are in a folder named “tinymce-advanced” (not two nested folders) in the WordPress plugins folder, usually “wp-content/plugins”.

\n
\n
No styles are imported in the Formats sub-menu.
\n
\n

These styles are imported from your current theme editor-style.css file. However some themes do not have this functionality. For these themes TinyMCE Advanced has the option to let you add a customized editor-style.css and import it into the editor.

\n
\n
I have just installed this plugin, but it does not do anything.
\n
\n

Change some buttons on one of the toolbars, save your changes, clear your browser cache, and try again. If that does not work try reloding the Edit page several times while holding down Shift or Ctrl. There may also be a network cache somewhere between you and your host. You may need to wait for a few hours until this cache expires.

\n
\n
When I add “Smilies”, they do not show in the editor.
\n
\n

The “Emoticons” button in TinyMCE adds the codes for the smilies. The actual images are added by WordPress when viewing the Post. Make sure the checkbox “Convert emoticons to graphics on display” in “Options – Writing” is checked.

\n
\n
The plugin does not add any buttons.
\n
\n

Make sure the “Disable the visual editor when writing” checkbox under “Users – Your Profile” is not checked.

\n
\n
I still see the “old” buttons in the editor
\n
\n

Click the “Restore Default Settings” button on the plugin settings page and then set the buttons again and save.

\n
\n
Other questions? More screenshots?
\n
\n

Please post on the support forum or visit the homepage for TinyMCE Advanced.

\n
\n
\n

\n

4.6.3

\n
    \n
  • Updated for WordPress 4.8 and TinyMCE 4.6.3.
    • \n
\n

4.5.6

\n
    \n
  • Updated for WordPress 4.7.4 and TinyMCE 4.5.6.
    • \n
  • Fixed PHP notice after importing settings.
    • \n
\n

4.4.3

\n
    \n
  • Updated for WordPress 4.7 and TinyMCE 4.4.3.
    • \n
  • Fixed missing “Source code” button bug.
    • \n
\n

4.4.1

\n
    \n
  • Updated for WordPress 4.6 and TinyMCE 4.4.1.
    • \n
  • Fixed multisite saving bug.
    • \n
  • Added new button in the Text editor to add or reset the line breaks. Adds line breaks only between tags. Works only when it detects that line breaks are missing so it doesn’t reformat posts with removed paragraphs.
    • \n
\n

4.3.10.1

\n
    \n
  • Fixed adding paragraph tags when loading posts that were saved before turning autop off.
    • \n
  • Disabled the (new) inline toolbar for tables as it was overlapping the table in some cases.
    • \n
\n

4.3.10

\n
    \n
  • Updated for WordPress 4.5.1 and TinyMCE 4.3.10.
    • \n
  • Fixed support for adding editor-style.css to themes that don’t have it.
    • \n
\n

4.3.8

\n
    \n
  • Updated for WordPress 4.5 and TinyMCE 4.3.8.
    • \n
  • Separated standard options and admin options.
    • \n
  • Added settings that can disable the plugin for the main editor, other editors in wp-admin or editors on the front-end.
    • \n
  • Korean translation by Josh Kim and Greek translation by Stathis Mellios.
    • \n
\n

4.2.8

\n
    \n
  • Updated for WordPress 4.4 and TinyMCE 4.2.8.
    • \n
  • Japanese translation by Manabu Miwa.
    • \n
\n

4.2.5

\n
    \n
  • Updated for WordPress 4.3.1 and TinyMCE 4.2.5.
    • \n
  • Fixed text domain and plugin headers.
    • \n
\n

4.2.3.1

\n
    \n
  • Fix error with removing the ‘textpattern’ plugin.
    • \n
\n

4.2.3

\n
    \n
  • Updated for WordPress 4.3 and TinyMCE 4.2.3.
    • \n
  • Removed the ‘textpattern’ plugin as WordPress 4.3 includes similar functionality by default.
    • \n
  • French translation by Nicolas Schneider.
    • \n
\n

4.1.9

\n
    \n
  • Updated for WordPress 4.2 and TinyMCE 4.1.9.
    • \n
  • Fixed bugs with showing oEmbed previews when pasting an URL.
    • \n
  • Fixed bugs with getting the content from TinyMCE with line breaks.
    • \n
\n

4.1.7

\n
    \n
  • Updated for WordPress 4.1 and TinyMCE 4.1.7.
    • \n
  • Fixed bug where consecutive caption shortcodes may be split with an empty paragraph tag.
    • \n
\n

4.1.1

\n
    \n
  • Fix bug with image captions when wpautop is disabled.
    • \n
  • Add translation support to the settings page. Button names/descriptions are translated from JS using the existing WordPress translation, so this part of the settings page will be translated by default. The other text still needs separate translation.
    • \n
\n

4.1

\n
    \n
  • Updated for WordPress 4.0 and TinyMCE 4.1.
    • \n
  • Add the ‘textpattern’ plugin that supports some of the markdown syntax while typing, (more info).
    • \n
  • Add the updated ‘table’ plugin that supports background and border color.
    • \n
\n

4.0.2

\n
    \n
  • Fix showing of the second, third and forth button rows when the Toolbar Toggle button is not used.
    • \n
  • Fix adding the ”directionality” plugin when RTL or LTR button is selected.
    • \n
  • Show the ”Advanced Options” to super admins on multisite installs.
    • \n
  • Add the ”link” plugin including link rel setting. Replaces the Insert/Edit Link dialog when enabled.
    • \n
  • Include updated ”table” plugin that has support for vertical align for cells.
    • \n
\n

4.0.1

\n

Fix warnings on pages other than Edit Post. Update the description.

\n

4.0

\n

Updated for WordPress 3.9 and TinyMCE 4.0. Refreshed the settings screen. Added support for exporting and importing of the settings.

\n

3.5.9.1

\n

Updated for WordPress 3.8, fixed auto-embedding of single line URLs when not removing paragraph tags.

\n

3.5.9

\n

Updated for WordPress 3.7 and TinyMCE 3.5.9.

\n

3.5.8

\n

Updated for WordPress 3.5 and TinyMCE 3.5.8.

\n

3.4.9

\n

Updated for WordPress 3.4 and TinyMCE 3.4.9.

\n

3.4.5.1

\n

Fixed a bug preventing TinyMCE from importing CSS classes from editor-style.css.

\n

3.4.5

\n

Updated for WordPress 3.3 or later and TinyMCE 3.4.5.

\n

3.4.2.1

\n

Fix the removal of the media plugin so it does not require re-saving the settings.

\n

3.4.2

\n

Compatibility with WordPress 3.2 and TinyMCE 3.4.2, removed the options for support for iframe and HTML 5.0 elements as they are supported by default in WordPress 3.2, removed the media plugin as it is included by default.

\n

3.3.9.1

\n

Added advanced options: stop removing iframes, stop removing HTML 5.0 elements, moved the support for custom editor styles to editor-style.css in the current theme.

\n

Attention: if you have a customized tadv-mce.css file and your theme doesn’t have editor-style.css, please download tadv-mce.css, rename it to editor-style.css and upload it to your current theme directory. Alternatively you can add there the editor-style.css from the Twenty Ten theme. If your theme has editor-style.css you can add any custom styles there.

\n

3.3.9

\n

Compatibility with WordPress 3.1 and TinyMCE 3.3.9, improved P and BR tags option.

\n

3.2.7

\n

Compatibility with WordPress 2.9 and TinyMCE 3.2.7, several minor bug fixes.

\n

3.2.4

\n

Compatibility with WordPress 2.8 and TinyMCE 3.2.4, minor bug fixes.

\n

3.2

\n

Compatibility with WordPress 2.7 and TinyMCE 3.2, minor bug fixes.

\n

3.1

\n

Compatibility with WordPress 2.6 and TinyMCE 3.1, keeps empty paragraphs when disabling the removal of P and BR tags, the buttons for MCImageManager and MCFileManager can be arranged (if installed).

\n

3.0.1

\n

Compatibility with WordPress 2.5.1 and TinyMCE 3.0.7, added option to disable the removal of P and BR tags when saving and in the HTML editor (autop), added two more buttons to the HTML editor: autop and undo, fixed the removal of non-default TinyMCE buttons.

\n

3.0

\n

Support for WordPress 2.5 and TinyMCE 3.0.

\n

2.2

\n

Deactivate/Uninstall option page, font size drop-down menu and other small changes.

\n

2.1

\n

Improved language selection, improved compatibility with WordPress 2.3 and TinyMCE 2.1.1.1, option to override some of the imported css classes and other small improvements and bugfixes.

\n

2.0

\n

Includes an admin page for arranging the TinyMCE toolbar buttons, easy installation, a lot of bugfixes, customized “Smilies” plugin that uses the built-in WordPress smilies, etc. The admin page uses jQuery and jQuery UI that lets you “drag and drop” the TinyMCE buttons to arrange your own toolbars and enables/disables the corresponding plugins depending on the used buttons.

\n";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:36:"http://wellformedweb.org/CommentAPI/";a:1:{s:10:"commentRss";a:1:{i:0;a:5:{s:4:"data";s:52:"https://wordpress.org/plugins/tinymce-advanced/feed/";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:38:"http://purl.org/rss/1.0/modules/slash/";a:1:{s:8:"comments";a:1:{i:0;a:5:{s:4:"data";s:1:"0";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}s:27:"http://www.w3.org/2005/Atom";a:1:{s:4:"link";a:1:{i:0;a:5:{s:4:"data";s:0:"";s:7:"attribs";a:1:{s:0:"";a:3:{s:4:"href";s:50:"https://wordpress.org/plugins/browse/popular/feed/";s:3:"rel";s:4:"self";s:4:"type";s:19:"application/rss+xml";}}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}s:44:"http://purl.org/rss/1.0/modules/syndication/";a:2:{s:12:"updatePeriod";a:1:{i:0;a:5:{s:4:"data";s:6:"hourly";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}s:15:"updateFrequency";a:1:{i:0;a:5:{s:4:"data";s:1:"1";s:7:"attribs";a:0:{}s:8:"xml_base";s:0:"";s:17:"xml_base_explicit";b:0;s:8:"xml_lang";s:0:"";}}}}}}}}}}}}s:4:"type";i:128;s:7:"headers";O:42:"Requests_Utility_CaseInsensitiveDictionary":1:{s:7:"\0*\0data";a:9:{s:6:"server";s:5:"nginx";s:4:"date";s:29:"Tue, 20 Jun 2017 12:23:52 GMT";s:12:"content-type";s:34:"application/rss+xml; charset=UTF-8";s:25:"strict-transport-security";s:11:"max-age=360";s:6:"x-olaf";s:3:"⛄";s:13:"last-modified";s:29:"Tue, 20 Jun 2017 12:11:42 GMT";s:4:"link";s:66:"; rel="https://api.w.org/"";s:15:"x-frame-options";s:10:"SAMEORIGIN";s:4:"x-nc";s:11:"HIT lax 249";}}s:5:"build";s:14:"20130911040210";}', 'no'); INSERT INTO `wp_options` (`option_id`, `option_name`, `option_value`, `autoload`) VALUES (309, '_transient_timeout_feed_mod_b9388c83948825c1edaef0d856b7b109', '1498004632', 'no'), (310, '_transient_feed_mod_b9388c83948825c1edaef0d856b7b109', '1497961432', 'no'), (311, '_transient_timeout_plugin_slugs', '1498047832', 'no'), (312, '_transient_plugin_slugs', 'a:3:{i:0;s:34:"advanced-custom-fields-pro/acf.php";i:1;s:19:"akismet/akismet.php";i:2;s:9:"hello.php";}', 'no'), (313, '_transient_timeout_dash_88ae138922fe95674369b1cb3d215a2b', '1498004632', 'no'), (314, '_transient_dash_88ae138922fe95674369b1cb3d215a2b', '
  • WordPress 4.8 “Evans” June 8, 2017
    An Update with You in Mind Gear up for a more intuitive WordPress! Version 4.8 of WordPress, named “Evans” in honor of jazz pianist and composer William John “Bill” Evans, is available for download or update in your WordPress dashboard. New features in 4.8 add more ways for you to express yourself and represent your brand. Though some […]
', 'no'), (315, 'can_compress_scripts', '1', 'no'), (318, 'fresh_site', '0', 'yes'), (320, 'test_insert_5949162d13be8', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'), (323, 'test_insert_5949178f3e348', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'), (324, 'theme_mods_twentyfourteen', 'a:1:{s:16:"sidebars_widgets";a:2:{s:4:"time";i:1497962405;s:4:"data";a:4:{s:19:"wp_inactive_widgets";a:0:{}s:9:"sidebar-1";a:6:{i:0;s:8:"search-2";i:1;s:14:"recent-posts-2";i:2;s:17:"recent-comments-2";i:3;s:10:"archives-2";i:4;s:12:"categories-2";i:5;s:6:"meta-2";}s:9:"sidebar-2";a:0:{}s:9:"sidebar-3";a:0:{}}}}', 'yes'), (325, 'current_theme', 'Twenty Seventeen', 'yes'), (326, 'theme_mods_twentyseventeen', 'a:1:{i:0;b:0;}', 'yes'), (327, 'theme_switched', '', 'yes'), (328, 'test_insert_59491807d4e65', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'), (329, 'test_insert_5949185206ea5', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'), (330, 'test_insert_5949186b04914', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'), (331, 'test_insert_5949187fadb10', 'a:1:{s:4:"test";s:4:"1234";}', 'yes'); -- -------------------------------------------------------- -- -- Table structure for table `wp_postmeta` -- CREATE TABLE `wp_postmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `post_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- 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, 2, 'username', 'juniorgrossi'), (3, 1, '_edit_lock', '1408573770:1'), (4, 1, '_edit_last', '1'), (6, 2, '_edit_lock', '1408573916:1'), (21, 10, 'username', 'juniorgrossi'), (8, 2, 'url', 'http://grossi.io'), (9, 1, 'username', 'juniorgrossi'), (10, 1, 'url', 'http://grossi.io'), (11, 5, 'username', 'juniorgrossi'), (12, 5, 'url', 'http://grossi.io'), (13, 6, 'username', 'juniorgrossi'), (14, 6, 'url', 'http://grossi.io'), (15, 7, 'username', 'juniorgrossi'), (16, 7, 'url', 'http://grossi.io'), (17, 8, 'username', 'juniorgrossi'), (18, 8, 'url', 'http://grossi.io'), (19, 9, 'username', 'juniorgrossi'), (20, 9, 'url', 'http://grossi.io'), (22, 10, 'url', 'http://grossi.io'), (23, 11, 'username', 'juniorgrossi'), (24, 11, 'url', 'http://grossi.io'), (25, 12, 'username', 'juniorgrossi'), (26, 12, 'url', 'http://grossi.io'), (27, 13, 'username', 'juniorgrossi'), (28, 13, 'url', 'http://grossi.io'), (29, 14, 'username', 'juniorgrossi'), (30, 14, 'url', 'http://grossi.io'), (31, 15, 'username', 'juniorgrossi'), (32, 15, 'url', 'http://grossi.io'), (33, 16, '_menu_item_type', 'post_type'), (34, 16, '_menu_item_menu_item_parent', '0'), (35, 16, '_menu_item_object_id', '2'), (36, 16, '_menu_item_object', 'page'), (37, 16, '_menu_item_target', ''), (38, 16, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (39, 16, '_menu_item_xfn', ''), (40, 16, '_menu_item_url', ''), (41, 17, '_menu_item_type', 'post_type'), (42, 17, '_menu_item_menu_item_parent', '16'), (43, 17, '_menu_item_object_id', '1'), (44, 17, '_menu_item_object', 'post'), (45, 17, '_menu_item_target', ''), (46, 17, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (47, 17, '_menu_item_xfn', ''), (48, 17, '_menu_item_url', ''), (49, 18, '_menu_item_type', 'custom'), (50, 18, '_menu_item_menu_item_parent', '0'), (51, 18, '_menu_item_object_id', '18'), (52, 18, '_menu_item_object', 'custom'), (53, 18, '_menu_item_target', ''), (54, 18, '_menu_item_classes', 'a:1:{i:0;s:0:"";}'), (55, 18, '_menu_item_xfn', ''), (56, 18, '_menu_item_url', 'http://google.com'), (57, 19, 'username', 'juniorgrossi'), (58, 19, 'url', 'http://grossi.io'), (59, 1, 'title', 'New title'), (60, 20, 'username', 'juniorgrossi'), (61, 20, 'url', 'http://grossi.io'), (62, 21, 'username', 'juniorgrossi'), (63, 21, 'url', 'http://grossi.io'), (64, 22, 'username', 'juniorgrossi'), (65, 22, 'url', 'http://grossi.io'), (66, 23, 'username', 'juniorgrossi'), (67, 23, 'url', 'http://grossi.io'), (68, 24, 'username', 'juniorgrossi'), (69, 24, 'url', 'http://grossi.io'), (70, 25, 'username', 'juniorgrossi'), (71, 25, 'url', 'http://grossi.io'), (72, 26, 'username', 'juniorgrossi'), (73, 26, 'url', 'http://grossi.io'), (74, 27, 'username', 'juniorgrossi'), (75, 27, 'url', 'http://grossi.io'), (76, 28, 'username', 'juniorgrossi'), (77, 28, 'url', 'http://grossi.io'), (78, 29, 'username', 'juniorgrossi'), (79, 29, 'url', 'http://grossi.io'), (80, 30, 'username', 'juniorgrossi'), (81, 30, 'url', 'http://grossi.io'), (82, 31, 'username', 'juniorgrossi'), (83, 31, 'url', 'http://grossi.io'), (84, 32, 'username', 'juniorgrossi'), (85, 32, 'url', 'http://grossi.io'), (86, 33, 'username', 'juniorgrossi'), (87, 33, 'url', 'http://grossi.io'), (88, 34, 'username', 'juniorgrossi'), (89, 34, 'url', 'http://grossi.io'), (90, 35, 'username', 'juniorgrossi'), (91, 35, 'url', 'http://grossi.io'), (92, 36, 'username', 'juniorgrossi'), (93, 36, 'url', 'http://grossi.io'), (94, 37, 'username', 'juniorgrossi'), (95, 37, 'url', 'http://grossi.io'), (96, 39, 'username', 'juniorgrossi'), (97, 39, 'url', 'http://grossi.io'), (98, 41, 'username', 'juniorgrossi'), (99, 41, 'url', 'http://grossi.io'), (100, 43, 'username', 'juniorgrossi'), (101, 43, 'url', 'http://grossi.io'), (102, 45, 'username', 'a:1:{s:6:"toggle";s:4:"true";}'), (103, 45, 'url', 'http://grossi.io'), (104, 47, 'username', 'juniorgrossi'), (105, 47, 'url', 'http://grossi.io'), (106, 49, 'username', 'juniorgrossi'), (107, 49, 'url', 'http://grossi.io'), (108, 51, 'username', 'juniorgrossi'), (109, 51, 'url', 'http://grossi.io'), (110, 53, 'username', 'juniorgrossi'), (111, 53, 'url', 'http://grossi.io'), (112, 55, 'username', 'juniorgrossi'), (113, 55, 'url', 'http://grossi.io'), (114, 57, 'username', 'juniorgrossi'), (115, 57, 'url', 'http://grossi.io'), (116, 59, 'username', 'juniorgrossi'), (117, 59, 'url', 'http://grossi.io'), (118, 59, '_thumbnail_id', '60'), (119, 63, 'username', 'juniorgrossi'), (120, 63, 'url', 'http://grossi.io'), (121, 66, 'username', 'juniorgrossi'), (122, 66, 'url', 'http://grossi.io'), (123, 68, 'username', 'juniorgrossi'), (124, 68, 'url', 'http://grossi.io'), (125, 70, 'username', 'juniorgrossi'), (126, 70, 'url', 'http://grossi.io'), (127, 72, 'username', 'juniorgrossi'), (128, 72, 'url', 'http://grossi.io'), (129, 74, 'username', 'juniorgrossi'), (130, 74, 'url', 'http://grossi.io'), (131, 76, 'username', 'juniorgrossi'), (132, 76, 'url', 'http://grossi.io'), (133, 78, 'username', 'juniorgrossi'), (134, 78, 'url', 'http://grossi.io'), (135, 80, 'username', 'juniorgrossi'), (136, 80, 'url', 'http://grossi.io'), (137, 82, 'username', 'juniorgrossi'), (138, 82, 'url', 'http://grossi.io'), (139, 84, 'username', 'juniorgrossi'), (140, 84, 'url', 'http://grossi.io'), (141, 86, 'username', 'juniorgrossi'), (142, 86, 'url', 'http://grossi.io'), (143, 88, 'username', 'juniorgrossi'), (144, 88, 'url', 'http://grossi.io'), (145, 90, 'username', 'juniorgrossi'), (146, 90, 'url', 'http://grossi.io'), (147, 92, 'username', 'juniorgrossi'), (148, 92, 'url', 'http://grossi.io'), (149, 94, 'username', 'juniorgrossi'), (150, 94, 'url', 'http://grossi.io'), (151, 96, 'username', 'juniorgrossi'), (152, 96, 'url', 'http://grossi.io'), (153, 98, 'username', 'juniorgrossi'), (154, 98, 'url', 'http://grossi.io'), (155, 100, 'username', 'juniorgrossi'), (156, 100, 'url', 'http://grossi.io'), (157, 102, 'username', 'juniorgrossi'), (158, 102, 'url', 'http://grossi.io'), (159, 104, 'username', 'juniorgrossi'), (160, 104, 'url', 'http://grossi.io'), (161, 106, 'username', 'juniorgrossi'), (162, 106, 'url', 'http://grossi.io'), (163, 108, 'username', 'juniorgrossi'), (164, 108, 'url', 'http://grossi.io'), (165, 110, 'username', 'juniorgrossi'), (166, 110, 'url', 'http://grossi.io'), (167, 112, 'username', 'juniorgrossi'), (168, 112, 'url', 'http://grossi.io'), (169, 114, 'username', 'juniorgrossi'), (170, 114, 'url', 'http://grossi.io'), (171, 116, 'username', 'juniorgrossi'), (172, 116, 'url', 'http://grossi.io'), (173, 119, 'username', 'juniorgrossi'), (174, 119, 'url', 'http://grossi.io'), (175, 121, 'username', 'juniorgrossi'), (176, 121, 'url', 'http://grossi.io'), (177, 123, 'username', 'juniorgrossi'), (178, 123, 'url', 'http://grossi.io'), (179, 125, 'username', 'juniorgrossi'), (180, 125, 'url', 'http://grossi.io'), (181, 128, 'username', 'juniorgrossi'), (182, 128, 'url', 'http://grossi.io'), (183, 131, 'username', 'juniorgrossi'), (184, 131, 'url', 'http://grossi.io'), (185, 134, 'username', 'juniorgrossi'), (186, 134, 'url', 'http://grossi.io'), (187, 137, 'username', 'juniorgrossi'), (188, 137, 'url', 'http://grossi.io'), (189, 140, 'username', 'juniorgrossi'), (190, 140, 'url', 'http://grossi.io'), (191, 143, 'username', 'juniorgrossi'), (192, 143, 'url', 'http://grossi.io'), (193, 146, 'username', 'juniorgrossi'), (194, 146, 'url', 'http://grossi.io'), (195, 149, 'username', 'juniorgrossi'), (196, 149, 'url', 'http://grossi.io'), (197, 152, 'username', 'juniorgrossi'), (198, 152, 'url', 'http://grossi.io'), (199, 155, 'username', 'juniorgrossi'), (200, 155, 'url', 'http://grossi.io'), (201, 158, 'username', 'juniorgrossi'), (202, 158, 'url', 'http://grossi.io'), (203, 161, 'username', 'juniorgrossi'), (204, 161, 'url', 'http://grossi.io'), (205, 164, 'username', 'juniorgrossi'), (206, 164, 'url', 'http://grossi.io'), (207, 167, 'username', 'juniorgrossi'), (208, 167, 'url', 'http://grossi.io'), (209, 170, 'username', 'juniorgrossi'), (210, 170, 'url', 'http://grossi.io'), (211, 173, 'username', 'juniorgrossi'), (212, 173, 'url', 'http://grossi.io'), (213, 176, 'username', 'juniorgrossi'), (214, 176, 'url', 'http://grossi.io'), (215, 179, 'username', 'juniorgrossi'), (216, 179, 'url', 'http://grossi.io'), (217, 182, 'username', 'juniorgrossi'), (218, 182, 'url', 'http://grossi.io'), (219, 185, 'username', 'juniorgrossi'), (220, 185, 'url', 'http://grossi.io'), (221, 188, 'username', 'juniorgrossi'), (222, 188, 'url', 'http://grossi.io'), (223, 191, 'username', 'juniorgrossi'), (224, 191, 'url', 'http://grossi.io'), (225, 194, 'username', 'juniorgrossi'), (226, 194, 'url', 'http://grossi.io'), (227, 197, 'username', 'juniorgrossi'), (228, 197, 'url', 'http://grossi.io'), (229, 200, 'username', 'juniorgrossi'), (230, 200, 'url', 'http://grossi.io'), (231, 203, 'username', 'juniorgrossi'), (232, 203, 'url', 'http://grossi.io'), (233, 206, 'username', 'juniorgrossi'), (234, 206, 'url', 'http://grossi.io'), (235, 209, 'username', 'juniorgrossi'), (236, 209, 'url', 'http://grossi.io'), (237, 212, 'username', 'juniorgrossi'), (238, 212, 'url', 'http://grossi.io'), (239, 215, 'username', 'juniorgrossi'), (240, 215, 'url', 'http://grossi.io'), (241, 218, 'username', 'juniorgrossi'), (242, 218, 'url', 'http://grossi.io'), (243, 221, 'username', 'juniorgrossi'), (244, 221, 'url', 'http://grossi.io'), (245, 224, 'username', 'juniorgrossi'), (246, 224, 'url', 'http://grossi.io'), (247, 227, 'username', 'juniorgrossi'), (248, 227, 'url', 'http://grossi.io'), (249, 230, 'username', 'juniorgrossi'), (250, 230, 'url', 'http://grossi.io'), (251, 233, 'username', 'juniorgrossi'), (252, 233, 'url', 'http://grossi.io'), (253, 15, 'city', 'New York'), (254, 236, 'username', 'juniorgrossi'), (255, 236, 'url', 'http://grossi.io'), (256, 239, 'username', 'juniorgrossi'), (257, 239, 'url', 'http://grossi.io'), (258, 242, 'username', 'juniorgrossi'), (259, 242, 'url', 'http://grossi.io'), (260, 245, 'username', 'juniorgrossi'), (261, 245, 'url', 'http://grossi.io'), (262, 248, 'username', 'juniorgrossi'), (263, 248, 'url', 'http://grossi.io'), (264, 251, 'username', 'juniorgrossi'), (265, 251, 'url', 'http://grossi.io'), (266, 254, 'username', 'juniorgrossi'), (267, 254, 'url', 'http://grossi.io'), (268, 257, 'username', 'juniorgrossi'), (269, 257, 'url', 'http://grossi.io'), (270, 260, 'username', 'juniorgrossi'), (271, 260, 'url', 'http://grossi.io'), (272, 265, 'username', 'juniorgrossi'), (273, 265, 'url', 'http://grossi.io'), (274, 268, 'username', 'juniorgrossi'), (275, 268, 'url', 'http://grossi.io'), (276, 271, 'username', 'juniorgrossi'), (277, 271, 'url', 'http://grossi.io'), (278, 274, 'username', 'juniorgrossi'), (279, 274, 'url', 'http://grossi.io'), (280, 277, 'username', 'juniorgrossi'), (281, 277, 'url', 'http://grossi.io'), (282, 280, 'username', 'juniorgrossi'), (283, 280, 'url', 'http://grossi.io'), (284, 283, 'username', 'juniorgrossi'), (285, 283, 'url', 'http://grossi.io'), (286, 286, 'username', 'juniorgrossi'), (287, 286, 'url', 'http://grossi.io'), (288, 289, 'username', 'juniorgrossi'), (289, 289, 'url', 'http://grossi.io'), (290, 292, 'username', 'juniorgrossi'), (291, 292, 'url', 'http://grossi.io'), (292, 295, 'username', 'juniorgrossi'), (293, 295, 'url', 'http://grossi.io'), (294, 298, 'username', 'juniorgrossi'), (295, 298, 'url', 'http://grossi.io'), (296, 301, 'username', 'juniorgrossi'), (297, 301, 'url', 'http://grossi.io'), (298, 304, 'username', 'juniorgrossi'), (299, 304, 'url', 'http://grossi.io'), (300, 307, 'username', 'juniorgrossi'), (301, 307, 'url', 'http://grossi.io'), (302, 310, 'username', 'juniorgrossi'), (303, 310, 'url', 'http://grossi.io'), (304, 313, 'username', 'juniorgrossi'), (305, 313, 'url', 'http://grossi.io'), (306, 316, 'username', 'juniorgrossi'), (307, 316, 'url', 'http://grossi.io'), (308, 319, 'username', 'juniorgrossi'), (309, 319, 'url', 'http://grossi.io'), (310, 322, 'username', 'juniorgrossi'), (311, 322, 'url', 'http://grossi.io'), (312, 326, 'username', 'juniorgrossi'), (313, 326, 'url', 'http://grossi.io'), (314, 329, 'username', 'juniorgrossi'), (315, 329, 'url', 'http://grossi.io'), (316, 332, 'username', 'juniorgrossi'), (317, 332, 'url', 'http://grossi.io'), (318, 335, 'username', 'juniorgrossi'), (319, 335, 'url', 'http://grossi.io'), (320, 338, 'username', 'juniorgrossi'), (321, 338, 'url', 'http://grossi.io'), (322, 341, 'username', 'juniorgrossi'), (323, 341, 'url', 'http://grossi.io'), (324, 344, 'username', 'juniorgrossi'), (325, 344, 'url', 'http://grossi.io'), (326, 347, 'username', 'juniorgrossi'), (327, 347, 'url', 'http://grossi.io'), (328, 351, 'username', 'juniorgrossi'), (329, 351, 'url', 'http://grossi.io'), (330, 354, 'username', 'juniorgrossi'), (331, 354, 'url', 'http://grossi.io'), (332, 358, 'username', 'juniorgrossi'), (333, 358, 'url', 'http://grossi.io'), (334, 361, 'username', 'juniorgrossi'), (335, 361, 'url', 'http://grossi.io'), (336, 363, 'username', 'juniorgrossi'), (337, 363, 'url', 'http://grossi.io'), (338, 365, 'username', 'juniorgrossi'), (339, 365, 'url', 'http://grossi.io'), (340, 367, 'username', 'juniorgrossi'), (341, 367, 'url', 'http://grossi.io'), (342, 369, 'username', 'juniorgrossi'), (343, 369, 'url', 'http://grossi.io'), (344, 371, 'username', 'juniorgrossi'), (345, 371, 'url', 'http://grossi.io'), (346, 373, 'username', 'juniorgrossi'), (347, 373, 'url', 'http://grossi.io'), (348, 375, 'username', 'juniorgrossi'), (349, 375, 'url', 'http://grossi.io'), (350, 377, 'username', 'juniorgrossi'), (351, 377, 'url', 'http://grossi.io'), (352, 379, 'username', 'juniorgrossi'), (353, 379, 'url', 'http://grossi.io'), (354, 382, 'username', 'juniorgrossi'), (355, 382, 'url', 'http://grossi.io'), (356, 384, 'username', 'juniorgrossi'), (357, 384, 'url', 'http://grossi.io'), (358, 387, 'username', 'juniorgrossi'), (359, 387, 'url', 'http://grossi.io'), (360, 401, 'username', 'juniorgrossi'), (361, 401, 'url', 'http://grossi.io'), (362, 404, 'username', 'juniorgrossi'), (363, 404, 'url', 'http://grossi.io'), (364, 407, 'username', 'juniorgrossi'), (365, 407, 'url', 'http://grossi.io'), (366, 409, 'username', 'juniorgrossi'), (367, 409, 'url', 'http://grossi.io'), (368, 414, 'username', 'juniorgrossi'), (369, 414, 'url', 'http://grossi.io'), (370, 418, 'username', 'juniorgrossi'), (371, 418, 'url', 'http://grossi.io'), (372, 421, 'username', 'juniorgrossi'), (373, 421, 'url', 'http://grossi.io'), (374, 424, 'username', 'juniorgrossi'), (375, 424, 'url', 'http://grossi.io'), (376, 427, 'username', 'juniorgrossi'), (377, 427, 'url', 'http://grossi.io'), (378, 430, 'username', 'juniorgrossi'), (379, 430, 'url', 'http://grossi.io'), (380, 433, 'username', 'juniorgrossi'), (381, 433, 'url', 'http://grossi.io'), (382, 436, 'username', 'juniorgrossi'), (383, 436, 'url', 'http://grossi.io'), (384, 447, 'username', 'juniorgrossi'), (385, 447, 'url', 'http://grossi.io'), (386, 450, 'username', 'juniorgrossi'), (387, 450, 'url', 'http://grossi.io'), (388, 453, 'username', 'juniorgrossi'), (389, 453, 'url', 'http://grossi.io'), (390, 456, 'username', 'juniorgrossi'), (391, 456, 'url', 'http://grossi.io'), (392, 459, 'username', 'juniorgrossi'), (393, 459, 'url', 'http://grossi.io'), (394, 462, 'username', 'juniorgrossi'), (395, 462, 'url', 'http://grossi.io'), (396, 465, 'username', 'juniorgrossi'), (397, 465, 'url', 'http://grossi.io'), (398, 468, 'username', 'juniorgrossi'), (399, 468, 'url', 'http://grossi.io'), (400, 471, 'username', 'juniorgrossi'), (401, 471, 'url', 'http://grossi.io'), (402, 474, 'username', 'juniorgrossi'), (403, 474, 'url', 'http://grossi.io'), (404, 477, 'username', 'juniorgrossi'), (405, 477, 'url', 'http://grossi.io'), (406, 480, 'username', 'juniorgrossi'), (407, 480, 'url', 'http://grossi.io'), (408, 487, 'username', 'juniorgrossi'), (409, 487, 'url', 'http://grossi.io'), (410, 490, 'username', 'juniorgrossi'), (411, 490, 'url', 'http://grossi.io'), (412, 493, 'username', 'juniorgrossi'), (413, 493, 'url', 'http://grossi.io'), (414, 496, 'username', 'juniorgrossi'), (415, 496, 'url', 'http://grossi.io'), (416, 499, 'username', 'juniorgrossi'), (417, 499, 'url', 'http://grossi.io'), (418, 502, 'username', 'juniorgrossi'), (419, 502, 'url', 'http://grossi.io'), (420, 505, 'username', 'juniorgrossi'), (421, 505, 'url', 'http://grossi.io'), (422, 508, 'username', 'juniorgrossi'), (423, 508, 'url', 'http://grossi.io'), (424, 511, 'username', 'juniorgrossi'), (425, 511, 'url', 'http://grossi.io'), (426, 514, 'username', 'juniorgrossi'), (427, 514, 'url', 'http://grossi.io'), (428, 517, 'username', 'juniorgrossi'), (429, 517, 'url', 'http://grossi.io'), (430, 520, 'username', 'juniorgrossi'), (431, 520, 'url', 'http://grossi.io'), (432, 523, 'username', 'juniorgrossi'), (433, 523, 'url', 'http://grossi.io'), (434, 526, 'username', 'juniorgrossi'), (435, 526, 'url', 'http://grossi.io'), (436, 529, 'username', 'juniorgrossi'), (437, 529, 'url', 'http://grossi.io'), (438, 532, 'username', 'juniorgrossi'), (439, 532, 'url', 'http://grossi.io'), (440, 535, 'username', 'juniorgrossi'), (441, 535, 'url', 'http://grossi.io'), (442, 538, 'username', 'juniorgrossi'), (443, 538, 'url', 'http://grossi.io'), (444, 541, 'username', 'juniorgrossi'), (445, 541, 'url', 'http://grossi.io'), (446, 544, 'username', 'juniorgrossi'), (447, 544, 'url', 'http://grossi.io'), (448, 547, 'username', 'juniorgrossi'), (449, 547, 'url', 'http://grossi.io'), (450, 550, 'username', 'juniorgrossi'), (451, 550, 'url', 'http://grossi.io'), (452, 553, 'username', 'juniorgrossi'), (453, 553, 'url', 'http://grossi.io'), (454, 556, 'username', 'juniorgrossi'), (455, 556, 'url', 'http://grossi.io'), (456, 559, 'username', 'juniorgrossi'), (457, 559, 'url', 'http://grossi.io'), (458, 562, 'username', 'juniorgrossi'), (459, 562, 'url', 'http://grossi.io'), (460, 565, 'username', 'juniorgrossi'), (461, 565, 'url', 'http://grossi.io'), (462, 568, 'username', 'juniorgrossi'), (463, 568, 'url', 'http://grossi.io'), (464, 49, '_edit_lock', '1497962594:1'), (465, 49, 'city', 'amsterdam'), (466, 49, '_edit_last', '1'), (467, 45, '_edit_lock', '1497962601:1'), (468, 48, '_edit_lock', '1497962597:1'), (469, 46, '_edit_lock', '1497962601:1'), (470, 47, '_edit_lock', '1497962599:1'), (471, 44, '_edit_lock', '1497962592:1'), (472, 42, '_edit_lock', '1497962586:1'), (473, 43, '_edit_lock', '1497962589:1'), (474, 40, '_edit_lock', '1497962406:1'), (475, 44, 'city', 'london'), (476, 44, '_edit_last', '1'), (478, 572, 'username', 'juniorgrossi'), (479, 572, 'url', 'http://grossi.io'), (480, 576, 'username', 'juniorgrossi'), (481, 576, 'url', 'http://grossi.io'), (482, 579, 'username', 'juniorgrossi'), (483, 579, 'url', 'http://grossi.io'), (484, 582, 'username', 'juniorgrossi'), (485, 582, 'url', 'http://grossi.io'), (486, 585, 'username', 'juniorgrossi'), (487, 585, 'url', 'http://grossi.io'), (488, 588, 'username', 'juniorgrossi'), (489, 588, 'url', 'http://grossi.io'), (490, 591, 'username', 'juniorgrossi'), (491, 591, 'url', 'http://grossi.io'), (492, 594, 'username', 'juniorgrossi'), (493, 594, 'url', 'http://grossi.io'); -- -------------------------------------------------------- -- -- Table structure for table `wp_posts` -- CREATE TABLE `wp_posts` ( `ID` bigint(20) UNSIGNED NOT NULL, `post_author` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_title` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_excerpt` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'publish', `comment_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `ping_status` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'open', `post_password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `post_name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `to_ping` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `pinged` mediumtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `post_content_filtered` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `post_parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `guid` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `menu_order` int(11) NOT NULL DEFAULT '0', `post_type` varchar(20) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT 'post', `post_mime_type` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `comment_count` bigint(20) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- 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, '2014-08-20 22:25:54', '2014-08-20 22:25:54', '[gallery]', 'Hello world!', '', 'publish', 'open', 'open', '', 'hello-world', '', '', '2016-11-18 01:17:59', '2016-11-18 01:17:59', '', 0, 'http://localhost:8000/?p=1', 0, 'post', '', 1), (339, 0, '2016-12-06 19:28:59', '2016-12-06 19:28:59', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:28:59', '2016-12-06 19:28:59', '', 0, '', 0, '', '', 0), (2, 1, '2014-08-20 22:25:54', '2014-08-20 22:25:54', 'This is an example page. It\'s different from a blog post because it will stay in one place and will show up in your site navigation (in most themes). Most people start with an About page that introduces them to potential site visitors. It might say something like this:\n\n
Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my blog. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)
\n\n...or something like this:\n\n
The XYZ Doohickey Company was founded in 1971, and has been providing quality doohickeys to the public ever since. Located in Gotham City, XYZ employs over 2,000 people and does all kinds of awesome things for the Gotham community.
\n\nAs a new WordPress user, you should go to your dashboard to delete this page and create new pages for your content. Have fun!', 'Sample Page', '', 'publish', 'open', 'open', '', 'sample-page', '', '', '2014-08-20 22:25:54', '2014-08-20 22:25:54', '', 0, 'http://localhost:8000/?page_id=2', 0, 'page', '', 0), (3, 1, '2014-08-20 22:26:13', '0000-00-00 00:00:00', '', 'Auto Draft', '', 'auto-draft', 'open', 'open', '', '', '', '', '2014-08-20 22:26:13', '0000-00-00 00:00:00', '', 0, 'http://localhost:8000/?p=3', 0, 'post', '', 0), (4, 1, '2014-08-20 22:30:27', '2014-08-20 22:30:27', 'Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!', 'Hello world!', '', 'inherit', 'open', 'open', '', '1-revision-v1', '', '', '2014-08-20 22:30:27', '2014-08-20 22:30:27', '', 1, 'http://localhost:8000/?p=4', 0, 'revision', '', 0), (5, 0, '2014-08-20 19:34:59', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:34:59', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (6, 0, '2014-08-20 19:35:55', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:35:55', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (7, 0, '2014-08-20 19:37:21', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:37:21', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (8, 0, '2014-08-20 19:38:13', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:38:13', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (9, 0, '2014-08-20 19:39:00', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:39:00', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (10, 0, '2014-08-20 19:40:07', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:40:07', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (11, 0, '2014-08-20 19:42:05', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:42:05', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (12, 0, '2014-08-20 19:42:31', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:42:31', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (13, 0, '2014-08-20 19:43:18', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:43:18', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (14, 0, '2014-08-20 19:43:34', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:43:34', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (15, 0, '2014-08-20 19:44:52', '0000-00-00 00:00:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2014-08-20 19:44:52', '0000-00-00 00:00:00', '', 0, '', 0, 'post', '', 0), (16, 1, '2015-09-13 12:56:55', '2015-09-13 12:56:55', ' ', '', '', 'publish', 'closed', 'closed', '', '16', '', '', '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 0, 'http://site.vagrant/admin/?p=5', 1, 'nav_menu_item', '', 0), (17, 1, '2015-09-13 12:56:55', '2015-09-13 12:56:55', ' ', '', '', 'publish', 'closed', 'closed', '', '17', '', '', '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 0, 'http://site.vagrant/admin/?p=6', 2, 'nav_menu_item', '', 0), (18, 1, '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 'Google', '', 'publish', 'closed', 'closed', '', 'google', '', '', '2015-09-13 12:56:55', '2015-09-13 12:56:55', '', 0, 'http://site.vagrant/admin/?p=7', 3, 'nav_menu_item', '', 0), (19, 0, '2016-03-17 16:07:07', '2016-03-17 16:07:07', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:07:07', '2016-03-17 16:07:07', '', 0, '', 0, 'post', '', 0), (20, 0, '2016-03-17 16:11:06', '2016-03-17 16:11:06', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:11:06', '2016-03-17 16:11:06', '', 0, '', 0, 'post', '', 0), (21, 0, '2016-03-17 16:13:53', '2016-03-17 16:13:53', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:13:53', '2016-03-17 16:13:53', '', 0, '', 0, 'post', '', 0), (22, 0, '2016-03-17 16:18:06', '2016-03-17 16:18:06', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:18:06', '2016-03-17 16:18:06', '', 0, '', 0, 'post', '', 0), (23, 0, '2016-03-17 16:21:53', '2016-03-17 16:21:53', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:21:53', '2016-03-17 16:21:53', '', 0, '', 0, 'post', '', 0), (24, 0, '2016-03-17 16:22:37', '2016-03-17 16:22:37', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:22:37', '2016-03-17 16:22:37', '', 0, '', 0, 'post', '', 0), (25, 0, '2016-03-17 16:23:29', '2016-03-17 16:23:29', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:23:29', '2016-03-17 16:23:29', '', 0, '', 0, 'post', '', 0), (26, 0, '2016-03-17 16:23:56', '2016-03-17 16:23:56', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:23:56', '2016-03-17 16:23:56', '', 0, '', 0, 'post', '', 0), (27, 0, '2016-03-17 16:24:51', '2016-03-17 16:24:51', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:24:51', '2016-03-17 16:24:51', '', 0, '', 0, 'post', '', 0), (28, 0, '2016-03-17 16:25:25', '2016-03-17 16:25:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:25:25', '2016-03-17 16:25:25', '', 0, '', 0, 'post', '', 0), (29, 0, '2016-03-17 16:25:43', '2016-03-17 16:25:43', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:25:43', '2016-03-17 16:25:43', '', 0, '', 0, 'post', '', 0), (30, 0, '2016-03-17 16:26:38', '2016-03-17 16:26:38', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:26:38', '2016-03-17 16:26:38', '', 0, '', 0, 'post', '', 0), (31, 0, '2016-03-17 16:26:59', '2016-03-17 16:26:59', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:26:59', '2016-03-17 16:26:59', '', 0, '', 0, 'post', '', 0), (32, 0, '2016-03-17 16:27:39', '2016-03-17 16:27:39', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:27:39', '2016-03-17 16:27:39', '', 0, '', 0, 'post', '', 0), (33, 0, '2016-03-17 16:28:25', '2016-03-17 16:28:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:28:25', '2016-03-17 16:28:25', '', 0, '', 0, 'post', '', 0), (34, 0, '2016-03-17 16:28:43', '2016-03-17 16:28:43', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:28:43', '2016-03-17 16:28:43', '', 0, '', 0, 'post', '', 0), (35, 0, '2016-03-17 16:28:58', '2016-03-17 16:28:58', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:28:58', '2016-03-17 16:28:58', '', 0, '', 0, 'post', '', 0), (36, 0, '2016-03-17 16:30:18', '2016-03-17 16:30:18', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:30:18', '2016-03-17 16:30:18', '', 0, '', 0, 'post', '', 0), (37, 0, '2016-03-17 16:30:53', '2016-03-17 16:30:53', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:30:53', '2016-03-17 16:30:53', '', 0, '', 0, 'post', '', 0), (38, 0, '2016-03-17 16:31:05', '2016-03-17 16:31:05', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:31:05', '2016-03-17 16:31:05', '', 0, '', 0, 'post', '', 0), (39, 0, '2016-03-17 16:31:05', '2016-03-17 16:31:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:31:05', '2016-03-17 16:31:05', '', 0, '', 0, 'post', '', 0), (40, 0, '2016-03-17 16:31:16', '2016-03-17 16:31:16', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:31:16', '2016-03-17 16:31:16', '', 0, '', 0, 'post', '', 0), (41, 0, '2016-03-17 16:31:16', '2016-03-17 16:31:16', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:31:16', '2016-03-17 16:31:16', '', 0, '', 0, 'post', '', 0), (42, 0, '2016-03-17 16:34:10', '2016-03-17 16:34:10', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:34:10', '2016-03-17 16:34:10', '', 0, '', 0, 'post', '', 0), (43, 0, '2016-03-17 16:34:10', '2016-03-17 16:34:10', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:34:10', '2016-03-17 16:34:10', '', 0, '', 0, 'post', '', 0), (44, 1, '2016-03-17 16:34:21', '2016-03-17 16:34:21', 'Test', '', '', 'publish', 'open', 'open', '', '44', '', '', '2017-06-20 12:33:26', '2017-06-20 12:33:26', '', 0, '', 0, 'post', '', 0), (45, 0, '2016-03-17 16:34:22', '2016-03-17 16:34:22', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:34:22', '2016-03-17 16:34:22', '', 0, '', 0, 'post', '', 0), (46, 0, '2016-03-17 16:34:40', '2016-03-17 16:34:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:34:40', '2016-03-17 16:34:40', '', 0, '', 0, 'post', '', 0), (47, 0, '2016-03-17 16:34:40', '2016-03-17 16:34:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:34:40', '2016-03-17 16:34:40', '', 0, '', 0, 'post', '', 0), (48, 0, '2016-03-17 16:38:14', '2016-03-17 16:38:14', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:38:14', '2016-03-17 16:38:14', '', 0, '', 0, 'post', '', 0), (49, 0, '2016-03-17 16:38:14', '2016-03-17 16:38:14', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-03-17 16:38:14', '2016-03-17 16:38:14', '', 0, '', 0, 'post', '', 0), (50, 0, '2016-04-19 19:05:16', '2016-04-19 19:05:16', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:05:16', '2016-04-19 19:05:16', '', 0, '', 0, '', '', 0), (51, 0, '2016-04-19 19:05:16', '2016-04-19 19:05:16', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:05:16', '2016-04-19 19:05:16', '', 0, '', 0, '', '', 0), (52, 0, '2016-04-19 19:05:19', '2016-04-19 19:05:19', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:05:19', '2016-04-19 19:05:19', '', 0, '', 0, '', '', 0), (53, 0, '2016-04-19 19:05:20', '2016-04-19 19:05:20', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:05:20', '2016-04-19 19:05:20', '', 0, '', 0, '', '', 0), (54, 0, '2016-04-19 19:05:24', '2016-04-19 19:05:24', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:05:24', '2016-04-19 19:05:24', '', 0, '', 0, '', '', 0), (55, 0, '2016-04-19 19:05:24', '2016-04-19 19:05:24', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:05:24', '2016-04-19 19:05:24', '', 0, '', 0, '', '', 0), (56, 0, '2016-04-19 19:45:42', '2016-04-19 19:45:42', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:45:42', '2016-04-19 19:45:42', '', 0, '', 0, '', '', 0), (57, 0, '2016-04-19 19:45:42', '2016-04-19 19:45:42', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-19 19:45:42', '2016-04-19 19:45:42', '', 0, '', 0, '', '', 0), (58, 0, '2016-04-29 17:45:28', '2016-04-29 17:45:28', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:45:28', '2016-04-29 17:45:28', '', 0, '', 0, '', '', 0), (59, 0, '2016-04-29 17:45:28', '2016-04-29 17:45:28', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:45:28', '2016-04-29 17:45:28', '', 0, '', 0, '', '', 0), (60, 1, '2013-06-07 11:12:02', '2013-06-07 11:12:02', '', 'hoodie_6_front', '', 'inherit', 'open', 'open', '', 'hoodie_6_front', '', '', '2013-06-07 11:12:02', '2013-06-07 11:12:02', '', 60, 'http://store.dev/wp-content/uploads/2013/06/hoodie_6_front.jpg', 0, 'attachment', 'image/jpeg', 0), (62, 0, '2016-04-29 17:52:07', '2016-04-29 17:52:07', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:52:07', '2016-04-29 17:52:07', '', 0, '', 0, '', '', 0), (63, 0, '2016-04-29 17:52:07', '2016-04-29 17:52:07', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:52:07', '2016-04-29 17:52:07', '', 0, '', 0, '', '', 0), (64, 0, '2016-04-29 17:52:21', '2016-04-29 17:52:21', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:52:21', '2016-04-29 17:52:21', '', 0, '', 0, '', '', 0), (65, 0, '2016-04-29 17:52:35', '2016-04-29 17:52:35', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:52:35', '2016-04-29 17:52:35', '', 0, '', 0, '', '', 0), (66, 0, '2016-04-29 17:52:35', '2016-04-29 17:52:35', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:52:35', '2016-04-29 17:52:35', '', 0, '', 0, '', '', 0), (67, 0, '2016-04-29 17:53:40', '2016-04-29 17:53:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:53:40', '2016-04-29 17:53:40', '', 0, '', 0, '', '', 0), (68, 0, '2016-04-29 17:53:40', '2016-04-29 17:53:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:53:40', '2016-04-29 17:53:40', '', 0, '', 0, '', '', 0), (69, 0, '2016-04-29 17:54:40', '2016-04-29 17:54:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:54:40', '2016-04-29 17:54:40', '', 0, '', 0, '', '', 0), (70, 0, '2016-04-29 17:54:40', '2016-04-29 17:54:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:54:40', '2016-04-29 17:54:40', '', 0, '', 0, '', '', 0), (71, 0, '2016-04-29 17:54:50', '2016-04-29 17:54:50', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:54:50', '2016-04-29 17:54:50', '', 0, '', 0, '', '', 0), (72, 0, '2016-04-29 17:54:51', '2016-04-29 17:54:51', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:54:51', '2016-04-29 17:54:51', '', 0, '', 0, '', '', 0), (73, 0, '2016-04-29 17:55:06', '2016-04-29 17:55:06', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:55:06', '2016-04-29 17:55:06', '', 0, '', 0, '', '', 0), (74, 0, '2016-04-29 17:55:07', '2016-04-29 17:55:07', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:55:07', '2016-04-29 17:55:07', '', 0, '', 0, '', '', 0), (75, 0, '2016-04-29 17:56:25', '2016-04-29 17:56:25', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:56:25', '2016-04-29 17:56:25', '', 0, '', 0, '', '', 0), (76, 0, '2016-04-29 17:56:25', '2016-04-29 17:56:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:56:25', '2016-04-29 17:56:25', '', 0, '', 0, '', '', 0), (77, 0, '2016-04-29 17:56:34', '2016-04-29 17:56:34', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:56:34', '2016-04-29 17:56:34', '', 0, '', 0, '', '', 0), (78, 0, '2016-04-29 17:56:34', '2016-04-29 17:56:34', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:56:34', '2016-04-29 17:56:34', '', 0, '', 0, '', '', 0), (79, 0, '2016-04-29 17:57:09', '2016-04-29 17:57:09', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:57:09', '2016-04-29 17:57:09', '', 0, '', 0, '', '', 0), (80, 0, '2016-04-29 17:57:09', '2016-04-29 17:57:09', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:57:09', '2016-04-29 17:57:09', '', 0, '', 0, '', '', 0), (81, 0, '2016-04-29 17:57:24', '2016-04-29 17:57:24', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:57:24', '2016-04-29 17:57:24', '', 0, '', 0, '', '', 0), (82, 0, '2016-04-29 17:57:25', '2016-04-29 17:57:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:57:25', '2016-04-29 17:57:25', '', 0, '', 0, '', '', 0), (83, 0, '2016-04-29 17:58:05', '2016-04-29 17:58:05', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:05', '2016-04-29 17:58:05', '', 0, '', 0, '', '', 0), (84, 0, '2016-04-29 17:58:05', '2016-04-29 17:58:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:05', '2016-04-29 17:58:05', '', 0, '', 0, '', '', 0), (85, 0, '2016-04-29 17:58:11', '2016-04-29 17:58:11', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:11', '2016-04-29 17:58:11', '', 0, '', 0, '', '', 0), (86, 0, '2016-04-29 17:58:11', '2016-04-29 17:58:11', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:11', '2016-04-29 17:58:11', '', 0, '', 0, '', '', 0), (87, 0, '2016-04-29 17:58:31', '2016-04-29 17:58:31', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:31', '2016-04-29 17:58:31', '', 0, '', 0, '', '', 0), (88, 0, '2016-04-29 17:58:31', '2016-04-29 17:58:31', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:31', '2016-04-29 17:58:31', '', 0, '', 0, '', '', 0), (89, 0, '2016-04-29 17:58:47', '2016-04-29 17:58:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:47', '2016-04-29 17:58:47', '', 0, '', 0, '', '', 0), (90, 0, '2016-04-29 17:58:47', '2016-04-29 17:58:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:58:47', '2016-04-29 17:58:47', '', 0, '', 0, '', '', 0), (91, 0, '2016-04-29 17:59:22', '2016-04-29 17:59:22', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:59:22', '2016-04-29 17:59:22', '', 0, '', 0, '', '', 0), (92, 0, '2016-04-29 17:59:23', '2016-04-29 17:59:23', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:59:23', '2016-04-29 17:59:23', '', 0, '', 0, '', '', 0), (93, 0, '2016-04-29 17:59:46', '2016-04-29 17:59:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:59:46', '2016-04-29 17:59:46', '', 0, '', 0, '', '', 0), (94, 0, '2016-04-29 17:59:46', '2016-04-29 17:59:46', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:59:46', '2016-04-29 17:59:46', '', 0, '', 0, '', '', 0), (95, 0, '2016-04-29 17:59:51', '2016-04-29 17:59:51', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:59:51', '2016-04-29 17:59:51', '', 0, '', 0, '', '', 0), (96, 0, '2016-04-29 17:59:51', '2016-04-29 17:59:51', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 17:59:51', '2016-04-29 17:59:51', '', 0, '', 0, '', '', 0), (97, 0, '2016-04-29 18:00:07', '2016-04-29 18:00:07', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:00:07', '2016-04-29 18:00:07', '', 0, '', 0, '', '', 0), (98, 0, '2016-04-29 18:00:07', '2016-04-29 18:00:07', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:00:07', '2016-04-29 18:00:07', '', 0, '', 0, '', '', 0), (99, 0, '2016-04-29 18:00:46', '2016-04-29 18:00:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:00:46', '2016-04-29 18:00:46', '', 0, '', 0, '', '', 0), (100, 0, '2016-04-29 18:00:46', '2016-04-29 18:00:46', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:00:46', '2016-04-29 18:00:46', '', 0, '', 0, '', '', 0), (101, 0, '2016-04-29 18:03:09', '2016-04-29 18:03:09', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:09', '2016-04-29 18:03:09', '', 0, '', 0, '', '', 0), (102, 0, '2016-04-29 18:03:10', '2016-04-29 18:03:10', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:10', '2016-04-29 18:03:10', '', 0, '', 0, '', '', 0), (103, 0, '2016-04-29 18:03:25', '2016-04-29 18:03:25', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:25', '2016-04-29 18:03:25', '', 0, '', 0, '', '', 0), (104, 0, '2016-04-29 18:03:26', '2016-04-29 18:03:26', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:26', '2016-04-29 18:03:26', '', 0, '', 0, '', '', 0), (105, 0, '2016-04-29 18:03:42', '2016-04-29 18:03:42', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:42', '2016-04-29 18:03:42', '', 0, '', 0, '', '', 0), (106, 0, '2016-04-29 18:03:43', '2016-04-29 18:03:43', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:43', '2016-04-29 18:03:43', '', 0, '', 0, '', '', 0), (107, 0, '2016-04-29 18:03:49', '2016-04-29 18:03:49', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:49', '2016-04-29 18:03:49', '', 0, '', 0, '', '', 0), (108, 0, '2016-04-29 18:03:49', '2016-04-29 18:03:49', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:03:49', '2016-04-29 18:03:49', '', 0, '', 0, '', '', 0), (109, 0, '2016-04-29 18:06:17', '2016-04-29 18:06:17', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:06:17', '2016-04-29 18:06:17', '', 0, '', 0, '', '', 0), (110, 0, '2016-04-29 18:06:17', '2016-04-29 18:06:17', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:06:17', '2016-04-29 18:06:17', '', 0, '', 0, '', '', 0), (111, 0, '2016-04-29 18:09:07', '2016-04-29 18:09:07', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:09:07', '2016-04-29 18:09:07', '', 0, '', 0, '', '', 0), (112, 0, '2016-04-29 18:09:08', '2016-04-29 18:09:08', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:09:08', '2016-04-29 18:09:08', '', 0, '', 0, '', '', 0), (113, 0, '2016-04-29 18:47:20', '2016-04-29 18:47:20', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:47:20', '2016-04-29 18:47:20', '', 0, '', 0, '', '', 0), (114, 0, '2016-04-29 18:47:21', '2016-04-29 18:47:21', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:47:21', '2016-04-29 18:47:21', '', 0, '', 0, '', '', 0), (115, 0, '2016-04-29 18:56:19', '2016-04-29 18:56:19', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:56:19', '2016-04-29 18:56:19', '', 0, '', 0, '', '', 0), (116, 0, '2016-04-29 18:56:20', '2016-04-29 18:56:20', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:56:20', '2016-04-29 18:56:20', '', 0, '', 0, '', '', 0), (117, 0, '2016-04-29 18:56:32', '2016-04-29 18:56:32', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 18:56:32', '2016-04-29 18:56:32', '', 0, '', 0, '', '', 0), (118, 0, '2016-04-29 19:04:37', '2016-04-29 19:04:37', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 19:04:37', '2016-04-29 19:04:37', '', 0, '', 0, '', '', 0), (119, 0, '2016-04-29 19:04:37', '2016-04-29 19:04:37', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 19:04:37', '2016-04-29 19:04:37', '', 0, '', 0, '', '', 0), (120, 0, '2016-04-29 19:11:41', '2016-04-29 19:11:41', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 19:11:41', '2016-04-29 19:11:41', '', 0, '', 0, '', '', 0), (121, 0, '2016-04-29 19:11:41', '2016-04-29 19:11:41', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-04-29 19:11:41', '2016-04-29 19:11:41', '', 0, '', 0, '', '', 0), (122, 0, '2016-05-02 22:38:05', '2016-05-02 22:38:05', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-05-02 22:38:05', '2016-05-02 22:38:05', '', 0, '', 0, '', '', 0), (123, 0, '2016-05-02 22:38:05', '2016-05-02 22:38:05', 'test [gallery id="123" size="medium"] shortcodes', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-05-02 22:38:05', '2016-05-02 22:38:05', '', 0, '', 0, '', '', 0), (124, 0, '2016-05-04 19:11:53', '2016-05-04 19:11:53', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-05-04 19:11:53', '2016-05-04 19:11:53', '', 0, '', 0, '', '', 0), (125, 0, '2016-05-04 19:11:53', '2016-05-04 19:11:53', '1~[gallery id="1" size="small"]2~[gallery id="2" size="medium"]', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-05-04 19:11:53', '2016-05-04 19:11:53', '', 0, '', 0, '', '', 0), (126, 0, '2016-08-22 16:02:30', '2016-08-22 16:02:30', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:02:30', '2016-08-22 16:02:30', '', 0, '', 0, '', '', 0), (128, 0, '2016-08-22 16:02:30', '2016-08-22 16:02:30', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:02:30', '2016-08-22 16:02:30', '', 0, '', 0, '', '', 0), (129, 0, '2016-08-22 16:04:25', '2016-08-22 16:04:25', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:04:25', '2016-08-22 16:04:25', '', 0, '', 0, '', '', 0), (131, 0, '2016-08-22 16:04:25', '2016-08-22 16:04:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:04:25', '2016-08-22 16:04:25', '', 0, '', 0, '', '', 0), (132, 0, '2016-08-22 16:06:19', '2016-08-22 16:06:19', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:06:19', '2016-08-22 16:06:19', '', 0, '', 0, '', '', 0), (134, 0, '2016-08-22 16:06:19', '2016-08-22 16:06:19', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:06:19', '2016-08-22 16:06:19', '', 0, '', 0, '', '', 0), (135, 0, '2016-08-22 16:19:30', '2016-08-22 16:19:30', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:19:30', '2016-08-22 16:19:30', '', 0, '', 0, '', '', 0), (137, 0, '2016-08-22 16:19:31', '2016-08-22 16:19:31', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:19:31', '2016-08-22 16:19:31', '', 0, '', 0, '', '', 0), (138, 0, '2016-08-22 16:20:14', '2016-08-22 16:20:14', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:20:14', '2016-08-22 16:20:14', '', 0, '', 0, '', '', 0), (140, 0, '2016-08-22 16:20:14', '2016-08-22 16:20:14', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:20:14', '2016-08-22 16:20:14', '', 0, '', 0, '', '', 0), (141, 0, '2016-08-22 16:23:53', '2016-08-22 16:23:53', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:23:53', '2016-08-22 16:23:53', '', 0, '', 0, '', '', 0), (143, 0, '2016-08-22 16:23:53', '2016-08-22 16:23:53', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:23:53', '2016-08-22 16:23:53', '', 0, '', 0, '', '', 0), (144, 0, '2016-08-22 16:24:11', '2016-08-22 16:24:11', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:24:11', '2016-08-22 16:24:11', '', 0, '', 0, '', '', 0), (146, 0, '2016-08-22 16:24:11', '2016-08-22 16:24:11', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:24:11', '2016-08-22 16:24:11', '', 0, '', 0, '', '', 0), (147, 0, '2016-08-22 16:24:42', '2016-08-22 16:24:42', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:24:42', '2016-08-22 16:24:42', '', 0, '', 0, '', '', 0), (149, 0, '2016-08-22 16:24:42', '2016-08-22 16:24:42', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:24:42', '2016-08-22 16:24:42', '', 0, '', 0, '', '', 0), (150, 0, '2016-08-22 16:24:53', '2016-08-22 16:24:53', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:24:53', '2016-08-22 16:24:53', '', 0, '', 0, '', '', 0), (152, 0, '2016-08-22 16:24:54', '2016-08-22 16:24:54', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:24:54', '2016-08-22 16:24:54', '', 0, '', 0, '', '', 0), (153, 0, '2016-08-22 16:25:27', '2016-08-22 16:25:27', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:25:27', '2016-08-22 16:25:27', '', 0, '', 0, '', '', 0), (155, 0, '2016-08-22 16:25:28', '2016-08-22 16:25:28', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:25:28', '2016-08-22 16:25:28', '', 0, '', 0, '', '', 0), (156, 0, '2016-08-22 16:27:45', '2016-08-22 16:27:45', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:27:45', '2016-08-22 16:27:45', '', 0, '', 0, '', '', 0), (158, 0, '2016-08-22 16:27:45', '2016-08-22 16:27:45', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:27:45', '2016-08-22 16:27:45', '', 0, '', 0, '', '', 0), (159, 0, '2016-08-22 16:28:21', '2016-08-22 16:28:21', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:28:21', '2016-08-22 16:28:21', '', 0, '', 0, '', '', 0), (161, 0, '2016-08-22 16:28:22', '2016-08-22 16:28:22', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:28:22', '2016-08-22 16:28:22', '', 0, '', 0, '', '', 0), (162, 0, '2016-08-22 16:28:42', '2016-08-22 16:28:42', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:28:42', '2016-08-22 16:28:42', '', 0, '', 0, '', '', 0), (164, 0, '2016-08-22 16:28:42', '2016-08-22 16:28:42', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:28:42', '2016-08-22 16:28:42', '', 0, '', 0, '', '', 0), (165, 0, '2016-08-22 16:29:05', '2016-08-22 16:29:05', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:29:05', '2016-08-22 16:29:05', '', 0, '', 0, '', '', 0), (167, 0, '2016-08-22 16:29:05', '2016-08-22 16:29:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:29:05', '2016-08-22 16:29:05', '', 0, '', 0, '', '', 0), (168, 0, '2016-08-22 16:29:16', '2016-08-22 16:29:16', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:29:16', '2016-08-22 16:29:16', '', 0, '', 0, '', '', 0), (170, 0, '2016-08-22 16:29:16', '2016-08-22 16:29:16', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:29:16', '2016-08-22 16:29:16', '', 0, '', 0, '', '', 0), (171, 0, '2016-08-22 16:29:38', '2016-08-22 16:29:38', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:29:38', '2016-08-22 16:29:38', '', 0, '', 0, '', '', 0), (173, 0, '2016-08-22 16:29:39', '2016-08-22 16:29:39', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:29:39', '2016-08-22 16:29:39', '', 0, '', 0, '', '', 0), (174, 0, '2016-08-22 16:30:46', '2016-08-22 16:30:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:30:46', '2016-08-22 16:30:46', '', 0, '', 0, '', '', 0), (176, 0, '2016-08-22 16:30:47', '2016-08-22 16:30:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:30:47', '2016-08-22 16:30:47', '', 0, '', 0, '', '', 0), (177, 0, '2016-08-22 16:30:59', '2016-08-22 16:30:59', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:30:59', '2016-08-22 16:30:59', '', 0, '', 0, '', '', 0), (179, 0, '2016-08-22 16:30:59', '2016-08-22 16:30:59', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:30:59', '2016-08-22 16:30:59', '', 0, '', 0, '', '', 0), (180, 0, '2016-08-22 16:31:04', '2016-08-22 16:31:04', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:31:04', '2016-08-22 16:31:04', '', 0, '', 0, '', '', 0), (182, 0, '2016-08-22 16:31:05', '2016-08-22 16:31:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:31:05', '2016-08-22 16:31:05', '', 0, '', 0, '', '', 0), (183, 0, '2016-08-22 16:31:44', '2016-08-22 16:31:44', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:31:44', '2016-08-22 16:31:44', '', 0, '', 0, '', '', 0), (185, 0, '2016-08-22 16:31:45', '2016-08-22 16:31:45', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:31:45', '2016-08-22 16:31:45', '', 0, '', 0, '', '', 0), (186, 0, '2016-08-22 16:32:25', '2016-08-22 16:32:25', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:32:25', '2016-08-22 16:32:25', '', 0, '', 0, '', '', 0), (188, 0, '2016-08-22 16:32:25', '2016-08-22 16:32:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-08-22 16:32:25', '2016-08-22 16:32:25', '', 0, '', 0, '', '', 0), (189, 0, '2016-10-03 10:23:40', '2016-10-03 10:23:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-03 10:23:40', '2016-10-03 10:23:40', '', 0, '', 0, '', '', 0), (191, 0, '2016-10-03 10:23:40', '2016-10-03 10:23:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-03 10:23:40', '2016-10-03 10:23:40', '', 0, '', 0, '', '', 0), (192, 0, '2016-10-03 10:32:39', '2016-10-03 10:32:39', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-03 10:32:39', '2016-10-03 10:32:39', '', 0, '', 0, '', '', 0), (194, 0, '2016-10-03 10:32:39', '2016-10-03 10:32:39', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-03 10:32:39', '2016-10-03 10:32:39', '', 0, '', 0, '', '', 0), (195, 0, '2016-10-03 10:37:49', '2016-10-03 10:37:49', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-03 10:37:49', '2016-10-03 10:37:49', '', 0, '', 0, '', '', 0), (197, 0, '2016-10-03 10:37:49', '2016-10-03 10:37:49', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-03 10:37:49', '2016-10-03 10:37:49', '', 0, '', 0, '', '', 0), (198, 0, '2016-10-07 12:11:51', '2016-10-07 12:11:51', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-07 12:11:51', '2016-10-07 12:11:51', '', 0, '', 0, '', '', 0), (200, 0, '2016-10-07 12:11:51', '2016-10-07 12:11:51', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-07 12:11:51', '2016-10-07 12:11:51', '', 0, '', 0, '', '', 0), (201, 0, '2016-10-12 18:35:39', '2016-10-12 18:35:39', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:35:39', '2016-10-12 18:35:39', '', 0, '', 0, '', '', 0), (203, 0, '2016-10-12 18:35:39', '2016-10-12 18:35:39', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:35:39', '2016-10-12 18:35:39', '', 0, '', 0, '', '', 0), (204, 0, '2016-10-12 18:35:51', '2016-10-12 18:35:51', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:35:51', '2016-10-12 18:35:51', '', 0, '', 0, '', '', 0), (206, 0, '2016-10-12 18:35:51', '2016-10-12 18:35:51', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:35:51', '2016-10-12 18:35:51', '', 0, '', 0, '', '', 0), (207, 0, '2016-10-12 18:39:14', '2016-10-12 18:39:14', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:39:14', '2016-10-12 18:39:14', '', 0, '', 0, '', '', 0), (209, 0, '2016-10-12 18:39:14', '2016-10-12 18:39:14', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:39:14', '2016-10-12 18:39:14', '', 0, '', 0, '', '', 0), (210, 0, '2016-10-12 18:39:43', '2016-10-12 18:39:43', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:39:43', '2016-10-12 18:39:43', '', 0, '', 0, '', '', 0), (212, 0, '2016-10-12 18:39:44', '2016-10-12 18:39:44', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:39:44', '2016-10-12 18:39:44', '', 0, '', 0, '', '', 0), (213, 0, '2016-10-12 18:40:05', '2016-10-12 18:40:05', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:40:05', '2016-10-12 18:40:05', '', 0, '', 0, '', '', 0), (215, 0, '2016-10-12 18:40:05', '2016-10-12 18:40:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:40:05', '2016-10-12 18:40:05', '', 0, '', 0, '', '', 0), (216, 0, '2016-10-12 18:41:20', '2016-10-12 18:41:20', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:41:20', '2016-10-12 18:41:20', '', 0, '', 0, '', '', 0), (218, 0, '2016-10-12 18:41:21', '2016-10-12 18:41:21', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:41:21', '2016-10-12 18:41:21', '', 0, '', 0, '', '', 0), (219, 0, '2016-10-12 18:41:40', '2016-10-12 18:41:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:41:40', '2016-10-12 18:41:40', '', 0, '', 0, '', '', 0), (221, 0, '2016-10-12 18:41:40', '2016-10-12 18:41:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:41:40', '2016-10-12 18:41:40', '', 0, '', 0, '', '', 0), (222, 0, '2016-10-12 18:42:47', '2016-10-12 18:42:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:42:47', '2016-10-12 18:42:47', '', 0, '', 0, '', '', 0), (224, 0, '2016-10-12 18:42:47', '2016-10-12 18:42:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:42:47', '2016-10-12 18:42:47', '', 0, '', 0, '', '', 0), (225, 0, '2016-10-12 18:44:40', '2016-10-12 18:44:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:44:40', '2016-10-12 18:44:40', '', 0, '', 0, '', '', 0), (227, 0, '2016-10-12 18:44:40', '2016-10-12 18:44:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:44:40', '2016-10-12 18:44:40', '', 0, '', 0, '', '', 0), (228, 0, '2016-10-12 18:46:25', '2016-10-12 18:46:25', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:46:25', '2016-10-12 18:46:25', '', 0, '', 0, '', '', 0), (230, 0, '2016-10-12 18:46:25', '2016-10-12 18:46:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:46:25', '2016-10-12 18:46:25', '', 0, '', 0, '', '', 0), (231, 0, '2016-10-12 18:46:45', '2016-10-12 18:46:45', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:46:45', '2016-10-12 18:46:45', '', 0, '', 0, '', '', 0), (233, 0, '2016-10-12 18:46:45', '2016-10-12 18:46:45', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:46:45', '2016-10-12 18:46:45', '', 0, '', 0, '', '', 0), (234, 0, '2016-10-12 18:48:08', '2016-10-12 18:48:08', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:48:08', '2016-10-12 18:48:08', '', 0, '', 0, '', '', 0), (236, 0, '2016-10-12 18:48:08', '2016-10-12 18:48:08', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:48:08', '2016-10-12 18:48:08', '', 0, '', 0, '', '', 0), (237, 0, '2016-10-12 18:48:17', '2016-10-12 18:48:17', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:48:17', '2016-10-12 18:48:17', '', 0, '', 0, '', '', 0), (239, 0, '2016-10-12 18:48:17', '2016-10-12 18:48:17', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:48:17', '2016-10-12 18:48:17', '', 0, '', 0, '', '', 0), (240, 0, '2016-10-12 18:48:38', '2016-10-12 18:48:38', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:48:38', '2016-10-12 18:48:38', '', 0, '', 0, '', '', 0), (242, 0, '2016-10-12 18:48:38', '2016-10-12 18:48:38', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:48:38', '2016-10-12 18:48:38', '', 0, '', 0, '', '', 0), (243, 0, '2016-10-12 18:51:12', '2016-10-12 18:51:12', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:51:12', '2016-10-12 18:51:12', '', 0, '', 0, '', '', 0), (245, 0, '2016-10-12 18:51:12', '2016-10-12 18:51:12', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:51:12', '2016-10-12 18:51:12', '', 0, '', 0, '', '', 0), (246, 0, '2016-10-12 18:51:28', '2016-10-12 18:51:28', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:51:28', '2016-10-12 18:51:28', '', 0, '', 0, '', '', 0), (248, 0, '2016-10-12 18:51:28', '2016-10-12 18:51:28', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:51:28', '2016-10-12 18:51:28', '', 0, '', 0, '', '', 0), (249, 0, '2016-10-12 18:52:04', '2016-10-12 18:52:04', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:52:04', '2016-10-12 18:52:04', '', 0, '', 0, '', '', 0), (251, 0, '2016-10-12 18:52:05', '2016-10-12 18:52:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:52:05', '2016-10-12 18:52:05', '', 0, '', 0, '', '', 0), (252, 0, '2016-10-12 18:52:15', '2016-10-12 18:52:15', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:52:15', '2016-10-12 18:52:15', '', 0, '', 0, '', '', 0), (254, 0, '2016-10-12 18:52:15', '2016-10-12 18:52:15', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:52:15', '2016-10-12 18:52:15', '', 0, '', 0, '', '', 0), (255, 0, '2016-10-12 18:52:21', '2016-10-12 18:52:21', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:52:21', '2016-10-12 18:52:21', '', 0, '', 0, '', '', 0), (257, 0, '2016-10-12 18:52:21', '2016-10-12 18:52:21', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:52:21', '2016-10-12 18:52:21', '', 0, '', 0, '', '', 0), (258, 0, '2016-10-12 18:53:44', '2016-10-12 18:53:44', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:53:44', '2016-10-12 18:53:44', '', 0, '', 0, '', '', 0), (260, 0, '2016-10-12 18:53:44', '2016-10-12 18:53:44', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:53:44', '2016-10-12 18:53:44', '', 0, '', 0, '', '', 0), (261, 0, '2016-10-12 18:54:46', '2016-10-12 18:54:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:54:46', '2016-10-12 18:54:46', '', 0, '', 0, '', '', 0), (262, 0, '2016-10-12 18:54:58', '2016-10-12 18:54:58', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:54:58', '2016-10-12 18:54:58', '', 0, '', 0, '', '', 0), (263, 0, '2016-10-12 18:55:52', '2016-10-12 18:55:52', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:55:52', '2016-10-12 18:55:52', '', 0, '', 0, '', '', 0), (265, 0, '2016-10-12 18:55:52', '2016-10-12 18:55:52', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:55:52', '2016-10-12 18:55:52', '', 0, '', 0, '', '', 0), (266, 0, '2016-10-12 18:55:59', '2016-10-12 18:55:59', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:55:59', '2016-10-12 18:55:59', '', 0, '', 0, '', '', 0), (268, 0, '2016-10-12 18:55:59', '2016-10-12 18:55:59', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 18:55:59', '2016-10-12 18:55:59', '', 0, '', 0, '', '', 0), (269, 0, '2016-10-12 19:09:09', '2016-10-12 19:09:09', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:09:09', '2016-10-12 19:09:09', '', 0, '', 0, '', '', 0), (271, 0, '2016-10-12 19:09:09', '2016-10-12 19:09:09', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:09:09', '2016-10-12 19:09:09', '', 0, '', 0, '', '', 0), (272, 0, '2016-10-12 19:17:42', '2016-10-12 19:17:42', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:17:42', '2016-10-12 19:17:42', '', 0, '', 0, '', '', 0), (274, 0, '2016-10-12 19:17:42', '2016-10-12 19:17:42', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:17:42', '2016-10-12 19:17:42', '', 0, '', 0, '', '', 0), (275, 0, '2016-10-12 19:18:01', '2016-10-12 19:18:01', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:18:01', '2016-10-12 19:18:01', '', 0, '', 0, '', '', 0), (277, 0, '2016-10-12 19:18:01', '2016-10-12 19:18:01', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:18:01', '2016-10-12 19:18:01', '', 0, '', 0, '', '', 0), (278, 0, '2016-10-12 19:18:22', '2016-10-12 19:18:22', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:18:22', '2016-10-12 19:18:22', '', 0, '', 0, '', '', 0), (280, 0, '2016-10-12 19:18:22', '2016-10-12 19:18:22', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:18:22', '2016-10-12 19:18:22', '', 0, '', 0, '', '', 0), (281, 0, '2016-10-12 19:19:10', '2016-10-12 19:19:10', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:19:10', '2016-10-12 19:19:10', '', 0, '', 0, '', '', 0), (283, 0, '2016-10-12 19:19:10', '2016-10-12 19:19:10', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:19:10', '2016-10-12 19:19:10', '', 0, '', 0, '', '', 0), (284, 0, '2016-10-12 19:19:21', '2016-10-12 19:19:21', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:19:21', '2016-10-12 19:19:21', '', 0, '', 0, '', '', 0), (286, 0, '2016-10-12 19:19:21', '2016-10-12 19:19:21', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:19:21', '2016-10-12 19:19:21', '', 0, '', 0, '', '', 0), (287, 0, '2016-10-12 19:19:28', '2016-10-12 19:19:28', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:19:28', '2016-10-12 19:19:28', '', 0, '', 0, '', '', 0), (289, 0, '2016-10-12 19:19:28', '2016-10-12 19:19:28', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:19:28', '2016-10-12 19:19:28', '', 0, '', 0, '', '', 0), (290, 0, '2016-10-12 19:22:35', '2016-10-12 19:22:35', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:22:35', '2016-10-12 19:22:35', '', 0, '', 0, '', '', 0), (292, 0, '2016-10-12 19:22:35', '2016-10-12 19:22:35', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:22:35', '2016-10-12 19:22:35', '', 0, '', 0, '', '', 0), (293, 0, '2016-10-12 19:22:43', '2016-10-12 19:22:43', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:22:43', '2016-10-12 19:22:43', '', 0, '', 0, '', '', 0), (295, 0, '2016-10-12 19:22:44', '2016-10-12 19:22:44', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:22:44', '2016-10-12 19:22:44', '', 0, '', 0, '', '', 0), (296, 0, '2016-10-12 19:22:47', '2016-10-12 19:22:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:22:47', '2016-10-12 19:22:47', '', 0, '', 0, '', '', 0), (298, 0, '2016-10-12 19:22:47', '2016-10-12 19:22:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:22:47', '2016-10-12 19:22:47', '', 0, '', 0, '', '', 0), (299, 0, '2016-10-12 19:23:19', '2016-10-12 19:23:19', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:23:19', '2016-10-12 19:23:19', '', 0, '', 0, '', '', 0), (301, 0, '2016-10-12 19:23:19', '2016-10-12 19:23:19', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:23:19', '2016-10-12 19:23:19', '', 0, '', 0, '', '', 0), (302, 0, '2016-10-12 19:24:29', '2016-10-12 19:24:29', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:24:29', '2016-10-12 19:24:29', '', 0, '', 0, '', '', 0), (304, 0, '2016-10-12 19:24:29', '2016-10-12 19:24:29', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:24:29', '2016-10-12 19:24:29', '', 0, '', 0, '', '', 0), (305, 0, '2016-10-12 19:24:40', '2016-10-12 19:24:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:24:40', '2016-10-12 19:24:40', '', 0, '', 0, '', '', 0), (307, 0, '2016-10-12 19:24:40', '2016-10-12 19:24:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:24:40', '2016-10-12 19:24:40', '', 0, '', 0, '', '', 0), (308, 0, '2016-10-12 19:27:23', '2016-10-12 19:27:23', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:27:23', '2016-10-12 19:27:23', '', 0, '', 0, '', '', 0), (310, 0, '2016-10-12 19:27:23', '2016-10-12 19:27:23', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:27:23', '2016-10-12 19:27:23', '', 0, '', 0, '', '', 0), (311, 0, '2016-10-12 19:27:35', '2016-10-12 19:27:35', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:27:35', '2016-10-12 19:27:35', '', 0, '', 0, '', '', 0), (313, 0, '2016-10-12 19:27:35', '2016-10-12 19:27:35', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:27:35', '2016-10-12 19:27:35', '', 0, '', 0, '', '', 0), (314, 0, '2016-10-12 19:29:00', '2016-10-12 19:29:00', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:29:00', '2016-10-12 19:29:00', '', 0, '', 0, '', '', 0), (316, 0, '2016-10-12 19:29:00', '2016-10-12 19:29:00', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:29:00', '2016-10-12 19:29:00', '', 0, '', 0, '', '', 0), (317, 0, '2016-10-12 19:29:08', '2016-10-12 19:29:08', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:29:08', '2016-10-12 19:29:08', '', 0, '', 0, '', '', 0), (319, 0, '2016-10-12 19:29:09', '2016-10-12 19:29:09', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-12 19:29:09', '2016-10-12 19:29:09', '', 0, '', 0, '', '', 0), (320, 0, '2016-10-13 13:31:30', '2016-10-13 13:31:30', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-13 13:31:30', '2016-10-13 13:31:30', '', 0, '', 0, '', '', 0), (322, 0, '2016-10-13 13:31:30', '2016-10-13 13:31:30', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-13 13:31:30', '2016-10-13 13:31:30', '', 0, '', 0, '', '', 0), (323, 0, '2016-10-13 13:33:13', '2016-10-13 13:33:13', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-13 13:33:13', '2016-10-13 13:33:13', '', 0, '', 0, '', '', 0), (324, 0, '2016-10-17 22:15:53', '2016-10-17 22:15:53', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-17 22:15:53', '2016-10-17 22:15:53', '', 0, '', 0, '', '', 0), (326, 0, '2016-10-17 22:15:53', '2016-10-17 22:15:53', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-17 22:15:53', '2016-10-17 22:15:53', '', 0, '', 0, '', '', 0), (327, 0, '2016-10-17 22:16:26', '2016-10-17 22:16:26', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-17 22:16:26', '2016-10-17 22:16:26', '', 0, '', 0, '', '', 0), (329, 0, '2016-10-17 22:16:26', '2016-10-17 22:16:26', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-17 22:16:26', '2016-10-17 22:16:26', '', 0, '', 0, '', '', 0), (330, 0, '2016-10-17 22:43:59', '2016-10-17 22:43:59', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-17 22:43:59', '2016-10-17 22:43:59', '', 0, '', 0, '', '', 0); 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 (332, 0, '2016-10-17 22:43:59', '2016-10-17 22:43:59', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-10-17 22:43:59', '2016-10-17 22:43:59', '', 0, '', 0, '', '', 0), (333, 0, '2016-11-12 22:40:27', '2016-11-12 22:40:27', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-11-12 22:40:27', '2016-11-12 22:40:27', '', 0, '', 0, '', '', 0), (335, 0, '2016-11-12 22:40:27', '2016-11-12 22:40:27', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-11-12 22:40:27', '2016-11-12 22:40:27', '', 0, '', 0, '', '', 0), (336, 0, '2016-11-12 23:00:33', '2016-11-12 23:00:33', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-11-12 23:00:33', '2016-11-12 23:00:33', '', 0, '', 0, '', '', 0), (338, 0, '2016-11-12 23:00:33', '2016-11-12 23:00:33', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-11-12 23:00:33', '2016-11-12 23:00:33', '', 0, '', 0, '', '', 0), (342, 0, '2016-12-06 19:29:20', '2016-12-06 19:29:20', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:29:20', '2016-12-06 19:29:20', '', 0, '', 0, '', '', 0), (341, 0, '2016-12-06 19:28:59', '2016-12-06 19:28:59', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:28:59', '2016-12-06 19:28:59', '', 0, '', 0, '', '', 0), (344, 0, '2016-12-06 19:29:20', '2016-12-06 19:29:20', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:29:20', '2016-12-06 19:29:20', '', 0, '', 0, '', '', 0), (345, 0, '2016-12-06 19:29:33', '2016-12-06 19:29:33', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:29:33', '2016-12-06 19:29:33', '', 0, '', 0, '', '', 0), (347, 0, '2016-12-06 19:29:33', '2016-12-06 19:29:33', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:29:33', '2016-12-06 19:29:33', '', 0, '', 0, '', '', 0), (348, 0, '2016-12-06 19:32:05', '2016-12-06 19:32:05', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:32:05', '2016-12-06 19:32:05', '', 0, '', 0, '', '', 0), (349, 0, '2016-12-06 19:32:16', '2016-12-06 19:32:16', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:32:16', '2016-12-06 19:32:16', '', 0, '', 0, '', '', 0), (351, 0, '2016-12-06 19:32:16', '2016-12-06 19:32:16', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:32:16', '2016-12-06 19:32:16', '', 0, '', 0, '', '', 0), (352, 0, '2016-12-06 19:32:30', '2016-12-06 19:32:30', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:32:30', '2016-12-06 19:32:30', '', 0, '', 0, '', '', 0), (354, 0, '2016-12-06 19:32:30', '2016-12-06 19:32:30', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:32:30', '2016-12-06 19:32:30', '', 0, '', 0, '', '', 0), (355, 0, '2016-12-06 19:33:46', '2016-12-06 19:33:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:33:46', '2016-12-06 19:33:46', '', 0, '', 0, '', '', 0), (356, 0, '2016-12-06 19:33:55', '2016-12-06 19:33:55', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:33:55', '2016-12-06 19:33:55', '', 0, '', 0, '', '', 0), (358, 0, '2016-12-06 19:33:55', '2016-12-06 19:33:55', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:33:55', '2016-12-06 19:33:55', '', 0, '', 0, '', '', 0), (359, 0, '2016-12-06 19:37:16', '2016-12-06 19:37:16', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:37:16', '2016-12-06 19:37:16', '', 0, '', 0, '', '', 0), (361, 0, '2016-12-06 19:37:16', '2016-12-06 19:37:16', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:37:16', '2016-12-06 19:37:16', '', 0, '', 0, '', '', 0), (380, 0, '2016-12-06 19:54:31', '2016-12-06 19:54:31', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:54:31', '2016-12-06 19:54:31', '', 0, '', 0, '', '', 0), (363, 0, '2016-12-06 19:38:47', '2016-12-06 19:38:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:38:47', '2016-12-06 19:38:47', '', 0, '', 0, '', '', 0), (365, 0, '2016-12-06 19:41:23', '2016-12-06 19:41:23', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:41:23', '2016-12-06 19:41:23', '', 0, '', 0, '', '', 0), (367, 0, '2016-12-06 19:41:45', '2016-12-06 19:41:45', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:41:45', '2016-12-06 19:41:45', '', 0, '', 0, '', '', 0), (369, 0, '2016-12-06 19:42:45', '2016-12-06 19:42:45', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:42:45', '2016-12-06 19:42:45', '', 0, '', 0, '', '', 0), (371, 0, '2016-12-06 19:43:19', '2016-12-06 19:43:19', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:43:19', '2016-12-06 19:43:19', '', 0, '', 0, '', '', 0), (373, 0, '2016-12-06 19:44:14', '2016-12-06 19:44:14', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:44:14', '2016-12-06 19:44:14', '', 0, '', 0, '', '', 0), (375, 0, '2016-12-06 19:47:15', '2016-12-06 19:47:15', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:47:15', '2016-12-06 19:47:15', '', 0, '', 0, '', '', 0), (377, 0, '2016-12-06 19:49:37', '2016-12-06 19:49:37', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:49:37', '2016-12-06 19:49:37', '', 0, '', 0, '', '', 0), (379, 0, '2016-12-06 19:49:50', '2016-12-06 19:49:50', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:49:50', '2016-12-06 19:49:50', '', 0, '', 0, '', '', 0), (382, 0, '2016-12-06 19:54:31', '2016-12-06 19:54:31', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:54:31', '2016-12-06 19:54:31', '', 0, '', 0, '', '', 0), (385, 0, '2016-12-06 19:56:38', '2016-12-06 19:56:38', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:56:38', '2016-12-06 19:56:38', '', 0, '', 0, '', '', 0), (384, 0, '2016-12-06 19:56:21', '2016-12-06 19:56:21', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:56:21', '2016-12-06 19:56:21', '', 0, '', 0, '', '', 0), (387, 0, '2016-12-06 19:56:38', '2016-12-06 19:56:38', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:56:38', '2016-12-06 19:56:38', '', 0, '', 0, '', '', 0), (388, 0, '2016-12-06 19:58:36', '2016-12-06 19:58:36', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:58:36', '2016-12-06 19:58:36', '', 0, '', 0, '', '', 0), (389, 0, '2016-12-06 19:59:20', '2016-12-06 19:59:20', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:59:20', '2016-12-06 19:59:20', '', 0, '', 0, '', '', 0), (390, 0, '2016-12-06 19:59:46', '2016-12-06 19:59:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 19:59:46', '2016-12-06 19:59:46', '', 0, '', 0, '', '', 0), (391, 0, '2016-12-06 20:01:00', '2016-12-06 20:01:00', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:01:00', '2016-12-06 20:01:00', '', 0, '', 0, '', '', 0), (392, 0, '2016-12-06 20:02:31', '2016-12-06 20:02:31', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:02:31', '2016-12-06 20:02:31', '', 0, '', 0, '', '', 0), (393, 0, '2016-12-06 20:02:57', '2016-12-06 20:02:57', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:02:57', '2016-12-06 20:02:57', '', 0, '', 0, '', '', 0), (394, 0, '2016-12-06 20:10:10', '2016-12-06 20:10:10', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:10:10', '2016-12-06 20:10:10', '', 0, '', 0, '', '', 0), (395, 0, '2016-12-06 20:11:26', '2016-12-06 20:11:26', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:11:26', '2016-12-06 20:11:26', '', 0, '', 0, '', '', 0), (396, 0, '2016-12-06 20:12:04', '2016-12-06 20:12:04', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:12:04', '2016-12-06 20:12:04', '', 0, '', 0, '', '', 0), (397, 0, '2016-12-06 20:12:37', '2016-12-06 20:12:37', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:12:37', '2016-12-06 20:12:37', '', 0, '', 0, '', '', 0), (398, 0, '2016-12-06 20:12:53', '2016-12-06 20:12:53', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2016-12-06 20:12:53', '2016-12-06 20:12:53', '', 0, '', 0, '', '', 0), (399, 0, '2017-01-23 21:43:38', '2017-01-23 21:43:38', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:43:38', '2017-01-23 21:43:38', '', 0, '', 0, '', '', 0), (401, 0, '2017-01-23 21:43:38', '2017-01-23 21:43:38', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:43:38', '2017-01-23 21:43:38', '', 0, '', 0, '', '', 0), (402, 0, '2017-01-23 21:44:52', '2017-01-23 21:44:52', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:44:52', '2017-01-23 21:44:52', '', 0, '', 0, '', '', 0), (404, 0, '2017-01-23 21:44:52', '2017-01-23 21:44:52', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:44:52', '2017-01-23 21:44:52', '', 0, '', 0, '', '', 0), (405, 0, '2017-01-23 21:48:13', '2017-01-23 21:48:13', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:48:13', '2017-01-23 21:48:13', '', 0, '', 0, '', '', 0), (407, 0, '2017-01-23 21:48:14', '2017-01-23 21:48:14', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:48:14', '2017-01-23 21:48:14', '', 0, '', 0, '', '', 0), (410, 0, '2017-01-23 21:50:13', '2017-01-23 21:50:13', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:50:13', '2017-01-23 21:50:13', '', 0, '', 0, '', '', 0), (409, 0, '2017-01-23 21:49:23', '2017-01-23 21:49:23', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:49:23', '2017-01-23 21:49:23', '', 0, '', 0, '', '', 0), (411, 0, '2017-01-23 21:50:18', '2017-01-23 21:50:18', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:50:18', '2017-01-23 21:50:18', '', 0, '', 0, '', '', 0), (412, 0, '2017-01-23 21:50:28', '2017-01-23 21:50:28', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:50:28', '2017-01-23 21:50:28', '', 0, '', 0, '', '', 0), (414, 0, '2017-01-23 21:50:29', '2017-01-23 21:50:29', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:50:29', '2017-01-23 21:50:29', '', 0, '', 0, '', '', 0), (415, 0, '2017-01-23 21:50:40', '2017-01-23 21:50:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:50:40', '2017-01-23 21:50:40', '', 0, '', 0, '', '', 0), (416, 0, '2017-01-23 21:51:57', '2017-01-23 21:51:57', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:51:57', '2017-01-23 21:51:57', '', 0, '', 0, '', '', 0), (418, 0, '2017-01-23 21:51:57', '2017-01-23 21:51:57', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:51:57', '2017-01-23 21:51:57', '', 0, '', 0, '', '', 0), (419, 0, '2017-01-23 21:52:59', '2017-01-23 21:52:59', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:52:59', '2017-01-23 21:52:59', '', 0, '', 0, '', '', 0), (421, 0, '2017-01-23 21:52:59', '2017-01-23 21:52:59', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-23 21:52:59', '2017-01-23 21:52:59', '', 0, '', 0, '', '', 0), (422, 0, '2017-01-26 10:54:15', '2017-01-26 10:54:15', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-26 10:54:15', '2017-01-26 10:54:15', '', 0, '', 0, '', '', 0), (424, 0, '2017-01-26 10:54:15', '2017-01-26 10:54:15', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-26 10:54:15', '2017-01-26 10:54:15', '', 0, '', 0, '', '', 0), (425, 0, '2017-01-26 10:59:12', '2017-01-26 10:59:12', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-26 10:59:12', '2017-01-26 10:59:12', '', 0, '', 0, '', '', 0), (427, 0, '2017-01-26 10:59:13', '2017-01-26 10:59:13', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-26 10:59:13', '2017-01-26 10:59:13', '', 0, '', 0, '', '', 0), (428, 0, '2017-01-31 16:54:34', '2017-01-31 16:54:34', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:54:34', '2017-01-31 16:54:34', '', 0, '', 0, '', '', 0), (430, 0, '2017-01-31 16:54:34', '2017-01-31 16:54:34', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:54:34', '2017-01-31 16:54:34', '', 0, '', 0, '', '', 0), (431, 0, '2017-01-31 16:54:47', '2017-01-31 16:54:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:54:47', '2017-01-31 16:54:47', '', 0, '', 0, '', '', 0), (433, 0, '2017-01-31 16:54:47', '2017-01-31 16:54:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:54:47', '2017-01-31 16:54:47', '', 0, '', 0, '', '', 0), (434, 0, '2017-01-31 16:55:42', '2017-01-31 16:55:42', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:55:42', '2017-01-31 16:55:42', '', 0, '', 0, '', '', 0), (436, 0, '2017-01-31 16:55:43', '2017-01-31 16:55:43', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:55:43', '2017-01-31 16:55:43', '', 0, '', 0, '', '', 0), (437, 0, '2017-01-31 16:58:02', '2017-01-31 16:58:02', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:58:02', '2017-01-31 16:58:02', '', 0, '', 0, '', '', 0), (438, 0, '2017-01-31 16:58:13', '2017-01-31 16:58:13', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:58:13', '2017-01-31 16:58:13', '', 0, '', 0, '', '', 0), (439, 0, '2017-01-31 16:58:36', '2017-01-31 16:58:36', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:58:36', '2017-01-31 16:58:36', '', 0, '', 0, '', '', 0), (440, 0, '2017-01-31 16:58:46', '2017-01-31 16:58:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:58:46', '2017-01-31 16:58:46', '', 0, '', 0, '', '', 0), (441, 0, '2017-01-31 16:59:06', '2017-01-31 16:59:06', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:59:06', '2017-01-31 16:59:06', '', 0, '', 0, '', '', 0), (442, 0, '2017-01-31 16:59:39', '2017-01-31 16:59:39', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 16:59:39', '2017-01-31 16:59:39', '', 0, '', 0, '', '', 0), (443, 0, '2017-01-31 17:00:46', '2017-01-31 17:00:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:00:46', '2017-01-31 17:00:46', '', 0, '', 0, '', '', 0), (444, 0, '2017-01-31 17:01:57', '2017-01-31 17:01:57', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:01:57', '2017-01-31 17:01:57', '', 0, '', 0, '', '', 0), (445, 0, '2017-01-31 17:04:43', '2017-01-31 17:04:43', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:04:43', '2017-01-31 17:04:43', '', 0, '', 0, '', '', 0), (447, 0, '2017-01-31 17:04:43', '2017-01-31 17:04:43', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:04:43', '2017-01-31 17:04:43', '', 0, '', 0, '', '', 0), (448, 0, '2017-01-31 17:06:11', '2017-01-31 17:06:11', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:06:11', '2017-01-31 17:06:11', '', 0, '', 0, '', '', 0), (450, 0, '2017-01-31 17:06:11', '2017-01-31 17:06:11', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:06:11', '2017-01-31 17:06:11', '', 0, '', 0, '', '', 0), (451, 0, '2017-01-31 17:06:25', '2017-01-31 17:06:25', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:06:25', '2017-01-31 17:06:25', '', 0, '', 0, '', '', 0), (453, 0, '2017-01-31 17:06:25', '2017-01-31 17:06:25', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:06:25', '2017-01-31 17:06:25', '', 0, '', 0, '', '', 0), (454, 0, '2017-01-31 17:06:57', '2017-01-31 17:06:57', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:06:57', '2017-01-31 17:06:57', '', 0, '', 0, '', '', 0), (456, 0, '2017-01-31 17:06:57', '2017-01-31 17:06:57', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:06:57', '2017-01-31 17:06:57', '', 0, '', 0, '', '', 0), (457, 0, '2017-01-31 17:14:38', '2017-01-31 17:14:38', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:14:38', '2017-01-31 17:14:38', '', 0, '', 0, '', '', 0), (459, 0, '2017-01-31 17:14:38', '2017-01-31 17:14:38', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:14:38', '2017-01-31 17:14:38', '', 0, '', 0, '', '', 0), (460, 0, '2017-01-31 17:31:02', '2017-01-31 17:31:02', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:31:02', '2017-01-31 17:31:02', '', 0, '', 0, '', '', 0), (462, 0, '2017-01-31 17:31:02', '2017-01-31 17:31:02', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:31:02', '2017-01-31 17:31:02', '', 0, '', 0, '', '', 0), (463, 0, '2017-01-31 17:31:10', '2017-01-31 17:31:10', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:31:10', '2017-01-31 17:31:10', '', 0, '', 0, '', '', 0), (465, 0, '2017-01-31 17:31:10', '2017-01-31 17:31:10', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:31:10', '2017-01-31 17:31:10', '', 0, '', 0, '', '', 0), (466, 0, '2017-01-31 17:31:40', '2017-01-31 17:31:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:31:40', '2017-01-31 17:31:40', '', 0, '', 0, '', '', 0), (468, 0, '2017-01-31 17:31:40', '2017-01-31 17:31:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:31:40', '2017-01-31 17:31:40', '', 0, '', 0, '', '', 0), (469, 0, '2017-01-31 17:32:24', '2017-01-31 17:32:24', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:32:24', '2017-01-31 17:32:24', '', 0, '', 0, '', '', 0), (471, 0, '2017-01-31 17:32:24', '2017-01-31 17:32:24', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:32:24', '2017-01-31 17:32:24', '', 0, '', 0, '', '', 0), (472, 0, '2017-01-31 17:32:49', '2017-01-31 17:32:49', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:32:49', '2017-01-31 17:32:49', '', 0, '', 0, '', '', 0), (474, 0, '2017-01-31 17:32:49', '2017-01-31 17:32:49', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:32:49', '2017-01-31 17:32:49', '', 0, '', 0, '', '', 0), (475, 0, '2017-01-31 17:33:17', '2017-01-31 17:33:17', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:33:17', '2017-01-31 17:33:17', '', 0, '', 0, '', '', 0), (477, 0, '2017-01-31 17:33:17', '2017-01-31 17:33:17', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:33:17', '2017-01-31 17:33:17', '', 0, '', 0, '', '', 0), (478, 0, '2017-01-31 17:43:27', '2017-01-31 17:43:27', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:43:27', '2017-01-31 17:43:27', '', 0, '', 0, '', '', 0), (480, 0, '2017-01-31 17:43:27', '2017-01-31 17:43:27', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:43:27', '2017-01-31 17:43:27', '', 0, '', 0, '', '', 0), (481, 0, '2017-01-31 17:44:06', '2017-01-31 17:44:06', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:44:06', '2017-01-31 17:44:06', '', 0, '', 0, '', '', 0), (482, 0, '2017-01-31 17:48:04', '2017-01-31 17:48:04', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:48:04', '2017-01-31 17:48:04', '', 0, '', 0, '', '', 0), (483, 0, '2017-01-31 17:48:05', '2017-01-31 17:48:05', 'test utf8 é à', 'test', 'test chinese characters お問い合わせ', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:48:05', '2017-01-31 17:48:05', '', 0, '', 0, '', '', 0), (484, 0, '2017-01-31 17:48:05', '2017-01-31 17:48:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:48:05', '2017-01-31 17:48:05', '', 0, '', 0, '', '', 0), (485, 0, '2017-01-31 17:53:57', '2017-01-31 17:53:57', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:53:57', '2017-01-31 17:53:57', '', 0, '', 0, '', '', 0), (487, 0, '2017-01-31 17:53:57', '2017-01-31 17:53:57', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:53:57', '2017-01-31 17:53:57', '', 0, '', 0, '', '', 0), (488, 0, '2017-01-31 17:54:39', '2017-01-31 17:54:39', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:54:39', '2017-01-31 17:54:39', '', 0, '', 0, '', '', 0), (490, 0, '2017-01-31 17:54:40', '2017-01-31 17:54:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:54:40', '2017-01-31 17:54:40', '', 0, '', 0, '', '', 0), (491, 0, '2017-01-31 17:56:06', '2017-01-31 17:56:06', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:56:06', '2017-01-31 17:56:06', '', 0, '', 0, '', '', 0), (493, 0, '2017-01-31 17:56:06', '2017-01-31 17:56:06', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:56:06', '2017-01-31 17:56:06', '', 0, '', 0, '', '', 0), (494, 0, '2017-01-31 17:56:27', '2017-01-31 17:56:27', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:56:27', '2017-01-31 17:56:27', '', 0, '', 0, '', '', 0), (496, 0, '2017-01-31 17:56:27', '2017-01-31 17:56:27', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:56:27', '2017-01-31 17:56:27', '', 0, '', 0, '', '', 0), (497, 0, '2017-01-31 17:56:47', '2017-01-31 17:56:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:56:47', '2017-01-31 17:56:47', '', 0, '', 0, '', '', 0), (499, 0, '2017-01-31 17:56:47', '2017-01-31 17:56:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:56:47', '2017-01-31 17:56:47', '', 0, '', 0, '', '', 0), (500, 0, '2017-01-31 17:57:16', '2017-01-31 17:57:16', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:57:16', '2017-01-31 17:57:16', '', 0, '', 0, '', '', 0), (502, 0, '2017-01-31 17:57:16', '2017-01-31 17:57:16', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:57:16', '2017-01-31 17:57:16', '', 0, '', 0, '', '', 0), (503, 0, '2017-01-31 17:58:49', '2017-01-31 17:58:49', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:58:49', '2017-01-31 17:58:49', '', 0, '', 0, '', '', 0), (505, 0, '2017-01-31 17:58:50', '2017-01-31 17:58:50', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 17:58:50', '2017-01-31 17:58:50', '', 0, '', 0, '', '', 0), (506, 0, '2017-01-31 18:06:36', '2017-01-31 18:06:36', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:06:36', '2017-01-31 18:06:36', '', 0, '', 0, '', '', 0), (508, 0, '2017-01-31 18:06:36', '2017-01-31 18:06:36', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:06:36', '2017-01-31 18:06:36', '', 0, '', 0, '', '', 0), (509, 0, '2017-01-31 18:07:59', '2017-01-31 18:07:59', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:07:59', '2017-01-31 18:07:59', '', 0, '', 0, '', '', 0), (511, 0, '2017-01-31 18:07:59', '2017-01-31 18:07:59', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:07:59', '2017-01-31 18:07:59', '', 0, '', 0, '', '', 0), (512, 0, '2017-01-31 18:08:47', '2017-01-31 18:08:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:08:47', '2017-01-31 18:08:47', '', 0, '', 0, '', '', 0), (514, 0, '2017-01-31 18:08:47', '2017-01-31 18:08:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:08:47', '2017-01-31 18:08:47', '', 0, '', 0, '', '', 0), (515, 0, '2017-01-31 18:09:38', '2017-01-31 18:09:38', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:09:38', '2017-01-31 18:09:38', '', 0, '', 0, '', '', 0), (517, 0, '2017-01-31 18:09:38', '2017-01-31 18:09:38', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:09:38', '2017-01-31 18:09:38', '', 0, '', 0, '', '', 0), (518, 0, '2017-01-31 18:10:47', '2017-01-31 18:10:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:10:47', '2017-01-31 18:10:47', '', 0, '', 0, '', '', 0), (520, 0, '2017-01-31 18:10:47', '2017-01-31 18:10:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:10:47', '2017-01-31 18:10:47', '', 0, '', 0, '', '', 0), (521, 0, '2017-01-31 18:11:50', '2017-01-31 18:11:50', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:11:50', '2017-01-31 18:11:50', '', 0, '', 0, '', '', 0), (523, 0, '2017-01-31 18:11:50', '2017-01-31 18:11:50', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:11:50', '2017-01-31 18:11:50', '', 0, '', 0, '', '', 0), (524, 0, '2017-01-31 18:12:07', '2017-01-31 18:12:07', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:12:07', '2017-01-31 18:12:07', '', 0, '', 0, '', '', 0), (526, 0, '2017-01-31 18:12:08', '2017-01-31 18:12:08', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:12:08', '2017-01-31 18:12:08', '', 0, '', 0, '', '', 0), (527, 0, '2017-01-31 18:12:26', '2017-01-31 18:12:26', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:12:26', '2017-01-31 18:12:26', '', 0, '', 0, '', '', 0), (529, 0, '2017-01-31 18:12:26', '2017-01-31 18:12:26', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:12:26', '2017-01-31 18:12:26', '', 0, '', 0, '', '', 0), (530, 0, '2017-01-31 18:12:50', '2017-01-31 18:12:50', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:12:50', '2017-01-31 18:12:50', '', 0, '', 0, '', '', 0), (532, 0, '2017-01-31 18:12:51', '2017-01-31 18:12:51', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-01-31 18:12:51', '2017-01-31 18:12:51', '', 0, '', 0, '', '', 0), (533, 0, '2017-02-01 16:56:36', '2017-02-01 16:56:36', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 16:56:36', '2017-02-01 16:56:36', '', 0, '', 0, '', '', 0), (535, 0, '2017-02-01 16:56:37', '2017-02-01 16:56:37', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 16:56:37', '2017-02-01 16:56:37', '', 0, '', 0, '', '', 0), (536, 0, '2017-02-01 16:57:48', '2017-02-01 16:57:48', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 16:57:48', '2017-02-01 16:57:48', '', 0, '', 0, '', '', 0), (538, 0, '2017-02-01 16:57:48', '2017-02-01 16:57:48', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 16:57:48', '2017-02-01 16:57:48', '', 0, '', 0, '', '', 0), (539, 0, '2017-02-01 17:00:31', '2017-02-01 17:00:31', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:00:31', '2017-02-01 17:00:31', '', 0, '', 0, '', '', 0), (541, 0, '2017-02-01 17:00:32', '2017-02-01 17:00:32', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:00:32', '2017-02-01 17:00:32', '', 0, '', 0, '', '', 0), (542, 0, '2017-02-01 17:01:08', '2017-02-01 17:01:08', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:01:08', '2017-02-01 17:01:08', '', 0, '', 0, '', '', 0), (544, 0, '2017-02-01 17:01:08', '2017-02-01 17:01:08', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:01:08', '2017-02-01 17:01:08', '', 0, '', 0, '', '', 0), (545, 0, '2017-02-01 17:01:19', '2017-02-01 17:01:19', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:01:19', '2017-02-01 17:01:19', '', 0, '', 0, '', '', 0), (547, 0, '2017-02-01 17:01:19', '2017-02-01 17:01:19', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:01:19', '2017-02-01 17:01:19', '', 0, '', 0, '', '', 0), (548, 0, '2017-02-01 17:01:38', '2017-02-01 17:01:38', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:01:38', '2017-02-01 17:01:38', '', 0, '', 0, '', '', 0), (550, 0, '2017-02-01 17:01:38', '2017-02-01 17:01:38', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:01:38', '2017-02-01 17:01:38', '', 0, '', 0, '', '', 0), (551, 0, '2017-02-01 17:02:50', '2017-02-01 17:02:50', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:02:50', '2017-02-01 17:02:50', '', 0, '', 0, '', '', 0), (553, 0, '2017-02-01 17:02:50', '2017-02-01 17:02:50', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:02:50', '2017-02-01 17:02:50', '', 0, '', 0, '', '', 0), (554, 0, '2017-02-01 17:06:49', '2017-02-01 17:06:49', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:06:49', '2017-02-01 17:06:49', '', 0, '', 0, '', '', 0), (556, 0, '2017-02-01 17:06:50', '2017-02-01 17:06:50', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:06:50', '2017-02-01 17:06:50', '', 0, '', 0, '', '', 0), (557, 0, '2017-02-01 17:07:46', '2017-02-01 17:07:46', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:07:46', '2017-02-01 17:07:46', '', 0, '', 0, '', '', 0), (559, 0, '2017-02-01 17:07:46', '2017-02-01 17:07:46', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-02-01 17:07:46', '2017-02-01 17:07:46', '', 0, '', 0, '', '', 0), (560, 0, '2017-06-14 14:15:04', '2017-06-14 14:15:04', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-14 14:15:04', '2017-06-14 14:15:04', '', 0, '', 0, '', '', 0), (562, 0, '2017-06-14 14:15:05', '2017-06-14 14:15:05', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-14 14:15:05', '2017-06-14 14:15:05', '', 0, '', 0, '', '', 0), (563, 0, '2017-06-14 14:25:40', '2017-06-14 14:25:40', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-14 14:25:40', '2017-06-14 14:25:40', '', 0, '', 0, '', '', 0), (565, 0, '2017-06-14 14:25:40', '2017-06-14 14:25:40', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-14 14:25:40', '2017-06-14 14:25:40', '', 0, '', 0, '', '', 0), (566, 0, '2017-06-20 12:19:21', '2017-06-20 12:19:21', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:19:21', '2017-06-20 12:19:21', '', 0, '', 0, '', '', 0), (568, 0, '2017-06-20 12:19:22', '2017-06-20 12:19:22', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:19:22', '2017-06-20 12:19:22', '', 0, '', 0, '', '', 0), (569, 1, '2017-06-20 12:33:26', '2017-06-20 12:33:26', 'Test', '', '', 'inherit', 'closed', 'closed', '', '44-revision-v1', '', '', '2017-06-20 12:33:26', '2017-06-20 12:33:26', '', 44, 'http://localhost:8000/?p=569', 0, 'revision', '', 0), (570, 0, '2017-06-20 12:33:48', '2017-06-20 12:33:48', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:33:48', '2017-06-20 12:33:48', '', 0, '', 0, '', '', 0), (572, 0, '2017-06-20 12:33:49', '2017-06-20 12:33:49', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:33:49', '2017-06-20 12:33:49', '', 0, '', 0, '', '', 0), (573, 0, '2017-06-20 12:35:04', '2017-06-20 12:35:04', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:35:04', '2017-06-20 12:35:04', '', 0, '', 0, '', '', 0), (574, 0, '2017-06-20 12:38:47', '2017-06-20 12:38:47', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:38:47', '2017-06-20 12:38:47', '', 0, '', 0, '', '', 0), (576, 0, '2017-06-20 12:38:47', '2017-06-20 12:38:47', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:38:47', '2017-06-20 12:38:47', '', 0, '', 0, '', '', 0), (577, 0, '2017-06-20 12:39:17', '2017-06-20 12:39:17', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:39:17', '2017-06-20 12:39:17', '', 0, '', 0, '', '', 0), (579, 0, '2017-06-20 12:39:17', '2017-06-20 12:39:17', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:39:17', '2017-06-20 12:39:17', '', 0, '', 0, '', '', 0), (580, 0, '2017-06-20 12:39:43', '2017-06-20 12:39:43', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:39:43', '2017-06-20 12:39:43', '', 0, '', 0, '', '', 0), (582, 0, '2017-06-20 12:39:43', '2017-06-20 12:39:43', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:39:43', '2017-06-20 12:39:43', '', 0, '', 0, '', '', 0), (583, 0, '2017-06-20 12:41:43', '2017-06-20 12:41:43', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:41:43', '2017-06-20 12:41:43', '', 0, '', 0, '', '', 0), (585, 0, '2017-06-20 12:41:44', '2017-06-20 12:41:44', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:41:44', '2017-06-20 12:41:44', '', 0, '', 0, '', '', 0), (586, 0, '2017-06-20 12:42:57', '2017-06-20 12:42:57', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:42:57', '2017-06-20 12:42:57', '', 0, '', 0, '', '', 0), (588, 0, '2017-06-20 12:42:58', '2017-06-20 12:42:58', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:42:58', '2017-06-20 12:42:58', '', 0, '', 0, '', '', 0), (589, 0, '2017-06-20 12:43:22', '2017-06-20 12:43:22', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:43:22', '2017-06-20 12:43:22', '', 0, '', 0, '', '', 0), (591, 0, '2017-06-20 12:43:23', '2017-06-20 12:43:23', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:43:23', '2017-06-20 12:43:23', '', 0, '', 0, '', '', 0), (592, 0, '2017-06-20 12:43:43', '2017-06-20 12:43:43', 'Test', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:43:43', '2017-06-20 12:43:43', '', 0, '', 0, '', '', 0), (594, 0, '2017-06-20 12:43:43', '2017-06-20 12:43:43', '', '', '', 'publish', 'open', 'open', '', '', '', '', '2017-06-20 12:43:43', '2017-06-20 12:43:43', '', 0, '', 0, '', '', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_termmeta` -- CREATE TABLE `wp_termmeta` ( `meta_id` bigint(20) UNSIGNED NOT NULL, `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_termmeta` -- INSERT INTO `wp_termmeta` (`meta_id`, `term_id`, `meta_key`, `meta_value`) VALUES (1, 2, 'foo', 'bar'), (2, 2, 'foo', 'bar'), (3, 2, 'foo', 'bar'), (4, 2, 'foo', 'bar'), (5, 2, 'foo', 'bar'), (6, 2, 'foo', 'bar'), (7, 2, 'foo', 'bar'), (8, 2, 'foo', 'bar'), (9, 2, 'foo', 'bar'), (10, 2, 'foo', 'bar'), (11, 2, 'foo', 'bar'); -- -------------------------------------------------------- -- -- Table structure for table `wp_terms` -- CREATE TABLE `wp_terms` ( `term_id` bigint(20) UNSIGNED NOT NULL, `name` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `slug` varchar(200) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `term_group` bigint(10) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_terms` -- INSERT INTO `wp_terms` (`term_id`, `name`, `slug`, `term_group`) VALUES (1, 'Uncategorized', 'uncategorized', 0), (2, 'php', 'php', 0), (3, 'Menu1', 'menu1', 0), (4, 'post-format-video', 'post-format-video', 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_term_relationships` -- CREATE TABLE `wp_term_relationships` ( `object_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `term_order` int(11) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_term_relationships` -- INSERT INTO `wp_term_relationships` (`object_id`, `term_taxonomy_id`, `term_order`) VALUES (1, 2, 0), (16, 3, 0), (17, 3, 0), (18, 3, 0), (3, 4, 0), (44, 1, 0); -- -------------------------------------------------------- -- -- Table structure for table `wp_term_taxonomy` -- CREATE TABLE `wp_term_taxonomy` ( `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL, `term_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `taxonomy` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `description` longtext COLLATE utf8mb4_unicode_ci NOT NULL, `parent` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `count` bigint(20) NOT NULL DEFAULT '0' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_term_taxonomy` -- INSERT INTO `wp_term_taxonomy` (`term_taxonomy_id`, `term_id`, `taxonomy`, `description`, `parent`, `count`) VALUES (1, 1, 'category', '', 0, 1), (2, 2, 'category', '', 0, 1), (3, 3, 'nav_menu', '', 0, 3), (4, 4, 'post_format', '', 0, 1); -- -------------------------------------------------------- -- -- Table structure for table `wp_usermeta` -- CREATE TABLE `wp_usermeta` ( `umeta_id` bigint(20) UNSIGNED NOT NULL, `user_id` bigint(20) UNSIGNED NOT NULL DEFAULT '0', `meta_key` varchar(255) COLLATE utf8mb4_unicode_ci DEFAULT NULL, `meta_value` longtext COLLATE utf8mb4_unicode_ci ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_usermeta` -- INSERT INTO `wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (1, 1, 'first_name', ''), (2, 1, 'last_name', ''), (3, 1, 'nickname', 'admin'), (4, 1, 'description', ''), (5, 1, 'rich_editing', 'true'), (6, 1, 'comment_shortcuts', 'false'), (7, 1, 'admin_color', 'fresh'), (8, 1, 'use_ssl', '0'), (9, 1, 'show_admin_bar_front', 'true'), (10, 1, 'wp_capabilities', 'a:1:{s:13:"administrator";b:1;}'), (11, 1, 'wp_user_level', '10'), (12, 1, 'dismissed_wp_pointers', 'wp350_media,wp360_revisions,wp360_locks,wp390_widgets'), (13, 1, 'show_welcome_panel', '1'), (14, 1, 'wp_user-settings', 'libraryContent=browse&wplink=0&mfold=o&editor=tinymce&hidetb=1'), (15, 1, 'wp_user-settings-time', '1408573568'), (16, 1, 'wp_dashboard_quick_press_last_post_id', '3'), (17, 2, 'wp_capabilities', 'a:1:{s:13:"administrator";b:1;}'), (18, 2, 'wp_user_level', '10'), (19, 2, 'custom_meta1', 'Hello'), (20, 2, 'custom_meta2', 'world'), (21, 3, 'custom_meta1', 'Hallo'), (22, 3, 'custom_meta2', 'Wereld'), (23, 4, 'custom_meta1', 'Hallo'), (24, 4, 'custom_meta2', 'Wereld'), (25, 5, 'custom_meta1', 'Hallo'), (26, 5, 'custom_meta2', 'Wereld'), (27, 6, 'custom_meta1', 'Hallo'), (28, 6, 'custom_meta2', 'Wereld'), (29, 7, 'custom_meta1', 'Hallo'), (30, 7, 'custom_meta2', 'Wereld'), (31, 8, 'custom_meta1', 'Hallo'), (32, 8, 'custom_meta2', 'Wereld'), (33, 9, 'custom_meta1', 'Hallo'), (34, 9, 'custom_meta2', 'Wereld'), (35, 10, 'custom_meta1', 'Hallo'), (36, 10, 'custom_meta2', 'Wereld'), (37, 11, 'custom_meta1', 'Hallo'), (38, 11, 'custom_meta2', 'Wereld'), (39, 12, 'custom_meta1', 'Hallo'), (40, 12, 'custom_meta2', 'Wereld'), (41, 13, 'custom_meta1', 'Hallo'), (42, 13, 'custom_meta2', 'Wereld'), (43, 14, 'custom_meta1', 'Hallo'), (44, 14, 'custom_meta2', 'Wereld'), (45, 15, 'custom_meta1', 'Hallo'), (46, 15, 'custom_meta2', 'Wereld'), (47, 16, 'custom_meta1', 'Hallo'), (48, 16, 'custom_meta2', 'Wereld'), (49, 17, 'custom_meta1', 'Hallo'), (50, 17, 'custom_meta2', 'Wereld'), (51, 18, 'custom_meta1', 'Hallo'), (52, 18, 'custom_meta2', 'Wereld'), (53, 19, 'custom_meta1', 'Hallo'), (54, 19, 'custom_meta2', 'Wereld'), (55, 20, 'custom_meta1', 'Hallo'), (56, 20, 'custom_meta2', 'Wereld'), (57, 21, 'custom_meta1', 'Hallo'), (58, 21, 'custom_meta2', 'Wereld'), (59, 22, 'custom_meta1', 'Hallo'), (60, 22, 'custom_meta2', 'Wereld'), (61, 23, 'custom_meta1', 'Hallo'), (62, 23, 'custom_meta2', 'Wereld'), (63, 24, 'custom_meta1', 'Hallo'), (64, 24, 'custom_meta2', 'Wereld'), (65, 25, 'custom_meta1', 'Hallo'), (66, 25, 'custom_meta2', 'Wereld'), (67, 26, 'custom_meta1', 'Hallo'), (68, 26, 'custom_meta2', 'Wereld'), (69, 27, 'custom_meta1', 'Hallo'), (70, 27, 'custom_meta2', 'Wereld'), (71, 28, 'custom_meta1', 'Hallo'), (72, 28, 'custom_meta2', 'Wereld'), (73, 29, 'custom_meta1', 'Hallo'), (74, 29, 'custom_meta2', 'Wereld'), (75, 30, 'custom_meta1', 'Hallo'), (76, 30, 'custom_meta2', 'Wereld'), (77, 31, 'custom_meta1', 'Hallo'), (78, 31, 'custom_meta2', 'Wereld'), (79, 32, 'custom_meta1', 'Hallo'), (80, 32, 'custom_meta2', 'Wereld'), (81, 33, 'custom_meta1', 'Hallo'), (82, 33, 'custom_meta2', 'Wereld'), (83, 34, 'custom_meta1', 'Hallo'), (84, 34, 'custom_meta2', 'Wereld'), (85, 35, 'custom_meta1', 'Hallo'), (86, 35, 'custom_meta2', 'Wereld'), (87, 36, 'custom_meta1', 'Hallo'), (88, 36, 'custom_meta2', 'Wereld'), (89, 37, 'custom_meta1', 'Hallo'), (90, 37, 'custom_meta2', 'Wereld'), (91, 38, 'custom_meta1', 'Hallo'), (92, 38, 'custom_meta2', 'Wereld'), (93, 39, 'custom_meta1', 'Hallo'), (94, 39, 'custom_meta2', 'Wereld'), (95, 40, 'custom_meta1', 'Hallo'), (96, 40, 'custom_meta2', 'Wereld'), (97, 41, 'custom_meta1', 'Hallo'), (98, 41, 'custom_meta2', 'Wereld'), (99, 42, 'custom_meta1', 'Hallo'), (100, 42, 'custom_meta2', 'Wereld'), (101, 43, 'custom_meta1', 'Hallo'), (102, 43, 'custom_meta2', 'Wereld'), (103, 44, 'custom_meta1', 'Hallo'), (104, 44, 'custom_meta2', 'Wereld'), (105, 45, 'custom_meta1', 'Hallo'), (106, 45, 'custom_meta2', 'Wereld'), (107, 46, 'custom_meta1', 'Hallo'), (108, 46, 'custom_meta2', 'Wereld'), (109, 47, 'custom_meta1', 'Hallo'), (110, 47, 'custom_meta2', 'Wereld'), (111, 48, 'custom_meta1', 'Hallo'), (112, 48, 'custom_meta2', 'Wereld'), (113, 49, 'custom_meta1', 'Hallo'), (114, 49, 'custom_meta2', 'Wereld'), (115, 50, 'custom_meta1', 'Hallo'), (116, 50, 'custom_meta2', 'Wereld'), (117, 51, 'custom_meta1', 'Hallo'), (118, 51, 'custom_meta2', 'Wereld'), (119, 52, 'custom_meta1', 'Hallo'), (120, 52, 'custom_meta2', 'Wereld'), (121, 53, 'custom_meta1', 'Hallo'), (122, 53, 'custom_meta2', 'Wereld'), (123, 54, 'custom_meta1', 'Hallo'), (124, 54, 'custom_meta2', 'Wereld'), (125, 55, 'custom_meta1', 'Hallo'), (126, 55, 'custom_meta2', 'Wereld'), (127, 56, 'custom_meta1', 'Hallo'), (128, 56, 'custom_meta2', 'Wereld'), (129, 57, 'custom_meta1', 'Hallo'), (130, 57, 'custom_meta2', 'Wereld'), (131, 58, 'custom_meta1', 'Hallo'), (132, 58, 'custom_meta2', 'Wereld'), (133, 59, 'custom_meta1', 'Hallo'), (134, 59, 'custom_meta2', 'Wereld'), (135, 60, 'custom_meta1', 'Hallo'), (136, 60, 'custom_meta2', 'Wereld'), (137, 61, 'custom_meta1', 'Hallo'), (138, 61, 'custom_meta2', 'Wereld'), (139, 62, 'custom_meta1', 'Hallo'), (140, 62, 'custom_meta2', 'Wereld'), (141, 63, 'custom_meta1', 'Hallo'), (142, 63, 'custom_meta2', 'Wereld'), (143, 64, 'custom_meta1', 'Hallo'), (144, 64, 'custom_meta2', 'Wereld'), (145, 65, 'custom_meta1', 'Hallo'), (146, 65, 'custom_meta2', 'Wereld'), (147, 66, 'custom_meta1', 'Hallo'), (148, 66, 'custom_meta2', 'Wereld'), (149, 67, 'custom_meta1', 'Hallo'), (150, 67, 'custom_meta2', 'Wereld'), (151, 68, 'custom_meta1', 'Hallo'), (152, 68, 'custom_meta2', 'Wereld'), (153, 69, 'custom_meta1', 'Hallo'), (154, 69, 'custom_meta2', 'Wereld'), (155, 70, 'custom_meta1', 'Hallo'), (156, 70, 'custom_meta2', 'Wereld'), (157, 71, 'custom_meta1', 'Hallo'), (158, 71, 'custom_meta2', 'Wereld'), (159, 72, 'custom_meta1', 'Hallo'), (160, 72, 'custom_meta2', 'Wereld'), (161, 73, 'custom_meta1', 'Hallo'), (162, 73, 'custom_meta2', 'Wereld'), (163, 74, 'custom_meta1', 'Hallo'), (164, 74, 'custom_meta2', 'Wereld'), (165, 75, 'custom_meta1', 'Hallo'), (166, 75, 'custom_meta2', 'Wereld'), (167, 76, 'custom_meta1', 'Hallo'), (168, 76, 'custom_meta2', 'Wereld'), (169, 77, 'custom_meta1', 'Hallo'), (170, 77, 'custom_meta2', 'Wereld'), (171, 78, 'custom_meta1', 'Hallo'), (172, 78, 'custom_meta2', 'Wereld'), (173, 79, 'custom_meta1', 'Hallo'), (174, 79, 'custom_meta2', 'Wereld'), (175, 80, 'custom_meta1', 'Hallo'), (176, 80, 'custom_meta2', 'Wereld'), (177, 81, 'custom_meta1', 'Hallo'), (178, 81, 'custom_meta2', 'Wereld'), (179, 82, 'custom_meta1', 'Hallo'), (180, 82, 'custom_meta2', 'Wereld'), (181, 83, 'custom_meta1', 'Hallo'), (182, 83, 'custom_meta2', 'Wereld'), (183, 84, 'custom_meta1', 'Hallo'), (184, 84, 'custom_meta2', 'Wereld'), (185, 85, 'custom_meta1', 'Hallo'), (186, 85, 'custom_meta2', 'Wereld'), (187, 86, 'custom_meta1', 'Hallo'), (188, 86, 'custom_meta2', 'Wereld'), (189, 87, 'custom_meta1', 'Hallo'), (190, 87, 'custom_meta2', 'Wereld'), (191, 88, 'custom_meta1', 'Hallo'), (192, 88, 'custom_meta2', 'Wereld'), (193, 89, 'custom_meta1', 'Hallo'), (194, 89, 'custom_meta2', 'Wereld'), (195, 90, 'custom_meta1', 'Hallo'), (196, 90, 'custom_meta2', 'Wereld'), (197, 91, 'custom_meta1', 'Hallo'), (198, 91, 'custom_meta2', 'Wereld'), (199, 92, 'custom_meta1', 'Hallo'), (200, 92, 'custom_meta2', 'Wereld'), (201, 93, 'custom_meta1', 'Hallo'), (202, 93, 'custom_meta2', 'Wereld'), (203, 94, 'custom_meta1', 'Hallo'), (204, 94, 'custom_meta2', 'Wereld'), (205, 95, 'custom_meta1', 'Hallo'), (206, 95, 'custom_meta2', 'Wereld'), (207, 96, 'custom_meta1', 'Hallo'), (208, 96, 'custom_meta2', 'Wereld'), (209, 97, 'custom_meta1', 'Hallo'), (210, 97, 'custom_meta2', 'Wereld'), (211, 98, 'custom_meta1', 'Hallo'), (212, 98, 'custom_meta2', 'Wereld'), (213, 99, 'custom_meta1', 'Hallo'), (214, 99, 'custom_meta2', 'Wereld'), (215, 100, 'custom_meta1', 'Hallo'), (216, 100, 'custom_meta2', 'Wereld'), (217, 99, 'active', '1'), (218, 101, 'custom_meta1', 'Hallo'), (219, 101, 'custom_meta2', 'Wereld'), (220, 100, 'active', '1'), (221, 102, 'custom_meta1', 'Hallo'), (222, 102, 'custom_meta2', 'Wereld'), (223, 101, 'active', '1'), (224, 103, 'custom_meta1', 'Hallo'), (225, 103, 'custom_meta2', 'Wereld'), (226, 102, 'active', '1'), (227, 104, 'custom_meta1', 'Hallo'), (228, 104, 'custom_meta2', 'Wereld'), (229, 103, 'active', '1'), (230, 105, 'custom_meta1', 'Hallo'), (231, 105, 'custom_meta2', 'Wereld'), (232, 104, 'active', '1'), (233, 106, 'custom_meta1', 'Hallo'), (234, 106, 'custom_meta2', 'Wereld'), (235, 105, 'active', '1'), (236, 107, 'custom_meta1', 'Hallo'), (237, 107, 'custom_meta2', 'Wereld'), (238, 106, 'active', '1'), (239, 108, 'custom_meta1', 'Hallo'), (240, 108, 'custom_meta2', 'Wereld'), (241, 109, 'custom_meta1', 'Hallo'), (242, 109, 'custom_meta2', 'Wereld'), (243, 110, 'custom_meta1', 'Hallo'), (244, 110, 'custom_meta2', 'Wereld'), (245, 111, 'custom_meta1', 'Hallo'), (246, 111, 'custom_meta2', 'Wereld'), (247, 112, 'custom_meta1', 'Hallo'), (248, 112, 'custom_meta2', 'Wereld'), (249, 113, 'custom_meta1', 'Hallo'), (250, 113, 'custom_meta2', 'Wereld'), (251, 114, 'custom_meta1', 'Hallo'), (252, 114, 'custom_meta2', 'Wereld'), (253, 115, 'custom_meta1', 'Hallo'), (254, 115, 'custom_meta2', 'Wereld'), (255, 116, 'custom_meta1', 'Hallo'), (256, 116, 'custom_meta2', 'Wereld'), (257, 117, 'custom_meta1', 'Hallo'), (258, 117, 'custom_meta2', 'Wereld'), (259, 118, 'custom_meta1', 'Hallo'), (260, 118, 'custom_meta2', 'Wereld'), (261, 119, 'custom_meta1', 'Hallo'), (262, 119, 'custom_meta2', 'Wereld'), (263, 108, 'active', '1'), (264, 120, 'custom_meta1', 'Hallo'), (265, 120, 'custom_meta2', 'Wereld'), (266, 109, 'active', '1'), (267, 121, 'custom_meta1', 'Hallo'), (268, 121, 'custom_meta2', 'Wereld'), (269, 110, 'active', '1'), (270, 122, 'custom_meta1', 'Hallo'), (271, 122, 'custom_meta2', 'Wereld'), (272, 111, 'active', '1'), (273, 123, 'custom_meta1', 'Hallo'), (274, 123, 'custom_meta2', 'Wereld'), (275, 112, 'active', '1'), (276, 124, 'custom_meta1', 'Hallo'), (277, 124, 'custom_meta2', 'Wereld'), (278, 113, 'active', '1'), (279, 125, 'custom_meta1', 'Hallo'), (280, 125, 'custom_meta2', 'Wereld'), (281, 114, 'active', '1'), (282, 126, 'custom_meta1', 'Hallo'), (283, 126, 'custom_meta2', 'Wereld'), (284, 115, 'active', '1'), (285, 127, 'custom_meta1', 'Hallo'), (286, 127, 'custom_meta2', 'Wereld'), (287, 116, 'active', '1'), (288, 128, 'custom_meta1', 'Hallo'), (289, 128, 'custom_meta2', 'Wereld'), (290, 117, 'active', '1'), (291, 129, 'custom_meta1', 'Hallo'), (292, 129, 'custom_meta2', 'Wereld'), (293, 118, 'active', '1'), (294, 130, 'custom_meta1', 'Hallo'), (295, 130, 'custom_meta2', 'Wereld'), (296, 119, 'active', '1'), (297, 131, 'custom_meta1', 'Hallo'), (298, 131, 'custom_meta2', 'Wereld'), (299, 120, 'active', '1'), (300, 132, 'custom_meta1', 'Hallo'), (301, 132, 'custom_meta2', 'Wereld'), (302, 121, 'active', '1'), (303, 133, 'custom_meta1', 'Hallo'), (304, 133, 'custom_meta2', 'Wereld'), (305, 122, 'active', '1'), (306, 134, 'custom_meta1', 'Hallo'), (307, 134, 'custom_meta2', 'Wereld'), (308, 123, 'active', '1'), (309, 135, 'custom_meta1', 'Hallo'), (310, 135, 'custom_meta2', 'Wereld'), (311, 124, 'active', '1'), (312, 136, 'custom_meta1', 'Hallo'), (313, 136, 'custom_meta2', 'Wereld'), (314, 125, 'active', '1'), (315, 137, 'custom_meta1', 'Hallo'), (316, 137, 'custom_meta2', 'Wereld'), (317, 126, 'active', '1'), (318, 138, 'custom_meta1', 'Hallo'), (319, 138, 'custom_meta2', 'Wereld'), (320, 139, 'custom_meta1', 'Hallo'), (321, 139, 'custom_meta2', 'Wereld'), (322, 140, 'custom_meta1', 'Hallo'), (323, 140, 'custom_meta2', 'Wereld'), (324, 141, 'custom_meta1', 'Hallo'), (325, 141, 'custom_meta2', 'Wereld'), (326, 142, 'custom_meta1', 'Hallo'), (327, 142, 'custom_meta2', 'Wereld'), (328, 144, 'custom_meta1', 'Hallo'), (329, 144, 'custom_meta2', 'Wereld'), (330, 145, 'custom_meta1', 'Hallo'), (331, 145, 'custom_meta2', 'Wereld'), (332, 146, 'custom_meta1', 'Hallo'), (333, 146, 'custom_meta2', 'Wereld'), (334, 147, 'custom_meta1', 'Hallo'), (335, 147, 'custom_meta2', 'Wereld'), (336, 148, 'custom_meta1', 'Hallo'), (337, 148, 'custom_meta2', 'Wereld'), (338, 149, 'custom_meta1', 'Hallo'), (339, 149, 'custom_meta2', 'Wereld'), (340, 138, 'active', '1'), (341, 150, 'custom_meta1', 'Hallo'), (342, 150, 'custom_meta2', 'Wereld'), (343, 151, 'custom_meta1', 'Hallo'), (344, 151, 'custom_meta2', 'Wereld'), (345, 152, 'custom_meta1', 'Hallo'), (346, 152, 'custom_meta2', 'Wereld'), (347, 153, 'custom_meta1', 'Hallo'), (348, 153, 'custom_meta2', 'Wereld'), (349, 154, 'custom_meta1', 'Hallo'), (350, 154, 'custom_meta2', 'Wereld'), (351, 155, 'custom_meta1', 'Hallo'), (352, 155, 'custom_meta2', 'Wereld'), (353, 156, 'custom_meta1', 'Hallo'), (354, 156, 'custom_meta2', 'Wereld'), (355, 157, 'custom_meta1', 'Hallo'), (356, 157, 'custom_meta2', 'Wereld'), (357, 158, 'custom_meta1', 'Hallo'), (358, 158, 'custom_meta2', 'Wereld'), (359, 159, 'custom_meta1', 'Hallo'), (360, 159, 'custom_meta2', 'Wereld'), (361, 160, 'custom_meta1', 'Hallo'), (362, 160, 'custom_meta2', 'Wereld'), (363, 161, 'custom_meta1', 'Hallo'), (364, 161, 'custom_meta2', 'Wereld'), (365, 162, 'custom_meta1', 'Hallo'), (366, 162, 'custom_meta2', 'Wereld'), (367, 163, 'custom_meta1', 'Hallo'), (368, 163, 'custom_meta2', 'Wereld'), (369, 164, 'custom_meta1', 'Hallo'), (370, 164, 'custom_meta2', 'Wereld'), (371, 165, 'custom_meta1', 'Hallo'), (372, 165, 'custom_meta2', 'Wereld'), (373, 166, 'custom_meta1', 'Hallo'), (374, 166, 'custom_meta2', 'Wereld'), (375, 167, 'custom_meta1', 'Hallo'), (376, 167, 'custom_meta2', 'Wereld'), (377, 168, 'custom_meta1', 'Hallo'), (378, 168, 'custom_meta2', 'Wereld'), (379, 169, 'custom_meta1', 'Hallo'), (380, 169, 'custom_meta2', 'Wereld'), (381, 170, 'custom_meta1', 'Hallo'), (382, 170, 'custom_meta2', 'Wereld'), (383, 171, 'custom_meta1', 'Hallo'), (384, 171, 'custom_meta2', 'Wereld'), (385, 1, 'session_tokens', 'a:1:{s:64:"e048db730ef49c4aa37b9c24ce4f8126be2558ebbad7378560910830ab98d233";a:4:{s:10:"expiration";i:1498134220;s:2:"ip";s:3:"::1";s:2:"ua";s:115:"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36";s:5:"login";i:1497961420;}}'), (386, 1, 'closedpostboxes_post', 'a:0:{}'), (387, 1, 'metaboxhidden_post', 'a:6:{i:0;s:11:"postexcerpt";i:1;s:13:"trackbacksdiv";i:2;s:16:"commentstatusdiv";i:3;s:11:"commentsdiv";i:4;s:7:"slugdiv";i:5;s:9:"authordiv";}'), (388, 172, 'custom_meta1', 'Hallo'), (389, 172, 'custom_meta2', 'Wereld'), (390, 173, 'custom_meta1', 'Hallo'), (391, 173, 'custom_meta2', 'Wereld'), (392, 174, 'custom_meta1', 'Hallo'), (393, 174, 'custom_meta2', 'Wereld'), (394, 175, 'custom_meta1', 'Hallo'), (395, 175, 'custom_meta2', 'Wereld'), (396, 176, 'custom_meta1', 'Hallo'), (397, 176, 'custom_meta2', 'Wereld'), (398, 177, 'custom_meta1', 'Hallo'), (399, 177, 'custom_meta2', 'Wereld'), (400, 178, 'custom_meta1', 'Hallo'), (401, 178, 'custom_meta2', 'Wereld'), (402, 179, 'custom_meta1', 'Hallo'), (403, 179, 'custom_meta2', 'Wereld'); -- -------------------------------------------------------- -- -- Table structure for table `wp_users` -- CREATE TABLE `wp_users` ( `ID` bigint(20) UNSIGNED NOT NULL, `user_login` varchar(60) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_pass` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_nicename` varchar(50) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_email` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_url` varchar(100) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', `user_activation_key` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', `user_status` int(11) NOT NULL DEFAULT '0', `display_name` varchar(250) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '' ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; -- -- Dumping data for table `wp_users` -- INSERT INTO `wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_url`, `user_registered`, `user_activation_key`, `user_status`, `display_name`) VALUES (1, 'admin', '$P$B2Lceeosw6Md2kOTwY1QAOq0XPG7kl.', 'admin', 'juniorgro@gmail.com', '', '2014-08-20 22:25:54', '', 0, 'admin'), (2, 'testuser', '$P$B3XVcWLhmJ49k38ZJAf3ckouIIl1xZ.', 'testuser', 'testuser@gmail.com', '', '2015-08-20 22:25:54', '', 0, 'testuser'), (3, 'test', '', '', '', '', '2016-03-17 16:07:07', '', 0, ''), (4, 'test', '', '', '', '', '2016-03-17 16:11:06', '', 0, ''), (5, 'test', '', '', '', '', '2016-03-17 16:13:53', '', 0, ''), (6, 'test', '', '', '', '', '2016-03-17 16:18:06', '', 0, ''), (7, 'test', '', '', '', '', '2016-03-17 16:21:53', '', 0, ''), (8, 'test', '', '', '', '', '2016-03-17 16:23:29', '', 0, ''), (9, 'test', '', '', '', '', '2016-03-17 16:23:56', '', 0, ''), (10, 'test', '', '', '', '', '2016-03-17 16:24:52', '', 0, ''), (11, 'test', '', '', '', '', '2016-03-17 16:25:25', '', 0, ''), (12, 'test', '', '', '', '', '2016-03-17 16:25:43', '', 0, ''), (13, 'test', '', '', '', '', '2016-03-17 16:26:38', '', 0, ''), (14, 'test', '', '', '', '', '2016-03-17 16:26:59', '', 0, ''), (15, 'test', '', '', '', '', '2016-03-17 16:27:39', '', 0, ''), (16, 'test', '', '', '', '', '2016-03-17 16:28:25', '', 0, ''), (17, 'test', '', '', '', '', '2016-03-17 16:28:44', '', 0, ''), (18, 'test', '', '', '', '', '2016-03-17 16:28:58', '', 0, ''), (19, 'test', '', '', '', '', '2016-03-17 16:30:18', '', 0, ''), (20, 'test', '', '', '', '', '2016-03-17 16:30:53', '', 0, ''), (21, 'test', '', '', '', '', '2016-03-17 16:31:05', '', 0, ''), (22, 'test', '', '', '', '', '2016-03-17 16:31:16', '', 0, ''), (23, 'test', '', '', '', '', '2016-03-17 16:34:10', '', 0, ''), (24, 'test', '', '', '', '', '2016-03-17 16:34:40', '', 0, ''), (25, 'test', '', '', '', '', '2016-03-17 16:38:14', '', 0, ''), (26, 'test', '', '', '', '', '2016-04-19 19:05:16', '', 0, ''), (27, 'test', '', '', '', '', '2016-04-19 19:05:20', '', 0, ''), (28, 'test', '', '', '', '', '2016-04-19 19:05:24', '', 0, ''), (29, 'test', '', '', '', '', '2016-04-19 19:45:42', '', 0, ''), (30, 'test', '', '', '', '', '2016-04-29 17:45:28', '', 0, ''), (31, 'test', '', '', '', '', '2016-04-29 17:52:07', '', 0, ''), (32, 'test', '', '', '', '', '2016-04-29 17:52:35', '', 0, ''), (33, 'test', '', '', '', '', '2016-04-29 17:53:40', '', 0, ''), (34, 'test', '', '', '', '', '2016-04-29 17:54:40', '', 0, ''), (35, 'test', '', '', '', '', '2016-04-29 17:54:51', '', 0, ''), (36, 'test', '', '', '', '', '2016-04-29 17:55:07', '', 0, ''), (37, 'test', '', '', '', '', '2016-04-29 17:56:25', '', 0, ''), (38, 'test', '', '', '', '', '2016-04-29 17:56:35', '', 0, ''), (39, 'test', '', '', '', '', '2016-04-29 17:57:09', '', 0, ''), (40, 'test', '', '', '', '', '2016-04-29 17:57:25', '', 0, ''), (41, 'test', '', '', '', '', '2016-04-29 17:58:05', '', 0, ''), (42, 'test', '', '', '', '', '2016-04-29 17:58:12', '', 0, ''), (43, 'test', '', '', '', '', '2016-04-29 17:58:31', '', 0, ''), (44, 'test', '', '', '', '', '2016-04-29 17:58:47', '', 0, ''), (45, 'test', '', '', '', '', '2016-04-29 17:59:23', '', 0, ''), (46, 'test', '', '', '', '', '2016-04-29 17:59:46', '', 0, ''), (47, 'test', '', '', '', '', '2016-04-29 17:59:51', '', 0, ''), (48, 'test', '', '', '', '', '2016-04-29 18:00:07', '', 0, ''), (49, 'test', '', '', '', '', '2016-04-29 18:00:47', '', 0, ''), (50, 'test', '', '', '', '', '2016-04-29 18:03:10', '', 0, ''), (51, 'test', '', '', '', '', '2016-04-29 18:03:26', '', 0, ''), (52, 'test', '', '', '', '', '2016-04-29 18:03:43', '', 0, ''), (53, 'test', '', '', '', '', '2016-04-29 18:03:49', '', 0, ''), (54, 'test', '', '', '', '', '2016-04-29 18:06:17', '', 0, ''), (55, 'test', '', '', '', '', '2016-04-29 18:09:08', '', 0, ''), (56, 'test', '', '', '', '', '2016-04-29 18:47:21', '', 0, ''), (57, 'test', '', '', '', '', '2016-04-29 18:56:20', '', 0, ''), (58, 'test', '', '', '', '', '2016-04-29 19:04:37', '', 0, ''), (59, 'test', '', '', '', '', '2016-04-29 19:11:41', '', 0, ''), (60, 'test', '', '', '', '', '2016-05-02 22:38:05', '', 0, ''), (61, 'test', '', '', '', '', '2016-05-04 19:11:53', '', 0, ''), (62, 'test', '', '', '', '', '2016-08-22 16:02:31', '', 0, ''), (63, 'test', '', '', '', '', '2016-08-22 16:04:26', '', 0, ''), (64, 'test', '', '', '', '', '2016-08-22 16:06:20', '', 0, ''), (65, 'test', '', '', '', '', '2016-08-22 16:27:45', '', 0, ''), (66, 'test', '', '', '', '', '2016-08-22 16:28:22', '', 0, ''), (67, 'test', '', '', '', '', '2016-08-22 16:28:42', '', 0, ''), (68, 'test', '', '', '', '', '2016-08-22 16:29:06', '', 0, ''), (69, 'test', '', '', '', '', '2016-08-22 16:29:16', '', 0, ''), (70, 'test', '', '', '', '', '2016-08-22 16:29:39', '', 0, ''), (71, 'test', '', '', '', '', '2016-08-22 16:30:47', '', 0, ''), (72, 'test', '', '', '', '', '2016-08-22 16:31:00', '', 0, ''), (73, 'test', '', '', '', '', '2016-08-22 16:31:05', '', 0, ''), (74, 'test', '', '', '', '', '2016-08-22 16:31:45', '', 0, ''), (75, 'test', '', '', '', '', '2016-08-22 16:32:25', '', 0, ''), (76, 'test', '', '', '', '', '2016-10-03 10:23:40', '', 0, ''), (77, 'test', '', '', '', '', '2016-10-03 10:32:39', '', 0, ''), (78, 'test', '', '', '', '', '2016-10-03 10:37:49', '', 0, ''), (79, 'test', '', '', '', '', '2016-10-07 12:11:51', '', 0, ''), (80, 'test', '', '', '', '', '2016-10-12 18:35:39', '', 0, ''), (81, 'test', '', '', '', '', '2016-10-12 18:35:51', '', 0, ''), (82, 'test', '', '', '', '', '2016-10-12 18:39:14', '', 0, ''), (83, 'test', '', '', '', '', '2016-10-12 18:48:17', '', 0, ''), (84, 'test', '', '', '', '', '2016-10-12 18:48:38', '', 0, ''), (85, 'test', '', '', '', '', '2016-10-12 18:51:12', '', 0, ''), (86, 'test', '', '', '', '', '2016-10-12 18:51:28', '', 0, ''), (87, 'test', '', '', '', '', '2016-10-12 18:52:05', '', 0, ''), (88, 'test', '', '', '', '', '2016-10-12 18:52:15', '', 0, ''), (89, 'test', '', '', '', '', '2016-10-12 18:52:21', '', 0, ''), (90, 'test', '', '', '', '', '2016-10-12 18:53:44', '', 0, ''), (91, 'test', '', '', '', '', '2016-10-12 18:55:52', '', 0, ''), (92, 'test', '', '', '', '', '2016-10-12 18:56:00', '', 0, ''), (93, 'test', '', '', '', '', '2016-10-12 19:09:09', '', 0, ''), (94, 'test', '', '', '', '', '2016-10-12 19:19:21', '', 0, ''), (95, 'test', '', '', '', '', '2016-10-17 22:15:53', '', 0, ''), (96, 'test', '', '', '', '', '2016-10-17 22:16:26', '', 0, ''), (97, 'test', '', '', '', '', '2016-10-17 22:43:59', '', 0, ''), (98, 'test', '', '', '', '', '2016-11-12 22:40:28', '', 0, ''), (99, 'test', '', '', '', '', '2016-11-12 23:00:33', '', 0, ''), (100, 'test', '', '', '', '', '2016-12-06 19:28:59', '', 0, ''), (101, 'test', '', '', '', '', '2016-12-06 19:29:20', '', 0, ''), (102, 'test', '', '', '', '', '2016-12-06 19:29:33', '', 0, ''), (103, 'test', '', '', '', '', '2016-12-06 19:32:17', '', 0, ''), (104, 'test', '', '', '', '', '2016-12-06 19:32:31', '', 0, ''), (105, 'test', '', '', '', '', '2016-12-06 19:33:55', '', 0, ''), (106, 'test', '', '', '', '', '2016-12-06 19:37:17', '', 0, ''), (107, 'test', '', '', '', '', '2016-12-06 19:38:48', '', 0, ''), (108, 'test', '', '', '', '', '2016-12-06 19:41:23', '', 0, ''), (109, 'test', '', '', '', '', '2016-12-06 19:41:45', '', 0, ''), (110, 'test', '', '', '', '', '2016-12-06 19:42:45', '', 0, ''), (111, 'test', '', '', '', '', '2016-12-06 19:43:19', '', 0, ''), (112, 'test', '', '', '', '', '2016-12-06 19:44:14', '', 0, ''), (113, 'test', '', '', '', '', '2016-12-06 19:47:15', '', 0, ''), (114, 'test', '', '', '', '', '2016-12-06 19:49:37', '', 0, ''), (115, 'test', '', '', '', '', '2016-12-06 19:49:50', '', 0, ''), (116, 'test', '', '', '', '', '2016-12-06 19:54:31', '', 0, ''), (117, 'test', '', '', '', '', '2016-12-06 19:56:21', '', 0, ''), (118, 'test', '', '', '', '', '2016-12-06 19:56:38', '', 0, ''), (119, 'test', '', '', '', '', '2017-01-23 21:43:38', '', 0, ''), (120, 'test', '', '', '', '', '2017-01-23 21:44:53', '', 0, ''), (121, 'test', '', '', '', '', '2017-01-23 21:48:14', '', 0, ''), (122, 'test', '', '', '', '', '2017-01-23 21:49:23', '', 0, ''), (123, 'test', '', '', '', '', '2017-01-23 21:50:29', '', 0, ''), (124, 'test', '', '', '', '', '2017-01-23 21:51:57', '', 0, ''), (125, 'test', '', '', '', '', '2017-01-23 21:53:00', '', 0, ''), (126, 'test', '', '', '', '', '2017-01-26 10:54:15', '', 0, ''), (127, 'test', '', '', '', '', '2017-01-26 10:59:13', '', 0, ''), (128, 'test', '', '', '', '', '2017-01-31 16:54:34', '', 0, ''), (129, 'test', '', '', '', '', '2017-01-31 16:54:48', '', 0, ''), (130, 'test', '', '', '', '', '2017-01-31 16:55:43', '', 0, ''), (131, 'test', '', '', '', '', '2017-01-31 17:04:43', '', 0, ''), (132, 'test', '', '', '', '', '2017-01-31 17:06:11', '', 0, ''), (133, 'test', '', '', '', '', '2017-01-31 17:06:25', '', 0, ''), (134, 'test', '', '', '', '', '2017-01-31 17:06:57', '', 0, ''), (135, 'test', '', '', '', '', '2017-01-31 17:14:38', '', 0, ''), (136, 'test', '', '', '', '', '2017-01-31 17:31:02', '', 0, ''), (137, 'test', '', '', '', '', '2017-01-31 17:31:11', '', 0, ''), (138, 'test', '', '', '', '', '2017-01-31 17:31:40', '', 0, ''), (139, 'test', '', '', '', '', '2017-01-31 17:32:24', '', 0, ''), (140, 'test', '', '', '', '', '2017-01-31 17:32:49', '', 0, ''), (141, 'test', '', '', '', '', '2017-01-31 17:33:17', '', 0, ''), (142, 'test', '', '', '', '', '2017-01-31 17:43:28', '', 0, ''), (143, 'test', '', '', '', '', '2017-01-31 17:48:05', '', 0, ''), (144, 'test', '', '', '', '', '2017-01-31 17:53:57', '', 0, ''), (145, 'test', '', '', '', '', '2017-01-31 17:54:40', '', 0, ''), (146, 'test', '', '', '', '', '2017-01-31 17:56:06', '', 0, ''), (147, 'test', '', '', '', '', '2017-01-31 17:56:27', '', 0, ''), (148, 'test', '', '', '', '', '2017-01-31 17:56:47', '', 0, ''), (149, 'test', '', '', '', '', '2017-01-31 17:57:16', '', 0, ''), (150, 'test', '', '', '', '', '2017-01-31 17:58:50', '', 0, ''), (151, 'test', '', '', '', '', '2017-01-31 18:06:36', '', 0, ''), (152, 'test', '', '', '', '', '2017-01-31 18:07:59', '', 0, ''), (153, 'test', '', '', '', '', '2017-01-31 18:08:47', '', 0, ''), (154, 'test', '', '', '', '', '2017-01-31 18:09:38', '', 0, ''), (155, 'test', '', '', '', '', '2017-01-31 18:10:47', '', 0, ''), (156, 'test', '', '', '', '', '2017-01-31 18:11:50', '', 0, ''), (157, 'test', '', '', '', '', '2017-01-31 18:12:08', '', 0, ''), (158, 'test', '', '', '', '', '2017-01-31 18:12:26', '', 0, ''), (159, 'test', '', '', '', '', '2017-01-31 18:12:51', '', 0, ''), (160, 'test', '', '', '', '', '2017-02-01 16:56:37', '', 0, ''), (161, 'test', '', '', '', '', '2017-02-01 16:57:48', '', 0, ''), (162, 'test', '', '', '', '', '2017-02-01 17:00:32', '', 0, ''), (163, 'test', '', '', '', '', '2017-02-01 17:01:08', '', 0, ''), (164, 'test', '', '', '', '', '2017-02-01 17:01:20', '', 0, ''), (165, 'test', '', '', '', '', '2017-02-01 17:01:39', '', 0, ''), (166, 'test', '', '', '', '', '2017-02-01 17:02:50', '', 0, ''), (167, 'test', '', '', '', '', '2017-02-01 17:06:50', '', 0, ''), (168, 'test', '', '', '', '', '2017-02-01 17:07:46', '', 0, ''), (169, 'test', '', '', '', '', '2017-06-14 14:15:05', '', 0, ''), (170, 'test', '', '', '', '', '2017-06-14 14:25:40', '', 0, ''), (171, 'test', '', '', '', '', '2017-06-20 12:19:23', '', 0, ''), (172, 'test', '', '', '', '', '2017-06-20 12:33:49', '', 0, ''), (173, 'test', '', '', '', '', '2017-06-20 12:38:47', '', 0, ''), (174, 'test', '', '', '', '', '2017-06-20 12:39:18', '', 0, ''), (175, 'test', '', '', '', '', '2017-06-20 12:39:43', '', 0, ''), (176, 'test', '', '', '', '', '2017-06-20 12:41:44', '', 0, ''), (177, 'test', '', '', '', '', '2017-06-20 12:42:58', '', 0, ''), (178, 'test', '', '', '', '', '2017-06-20 12:43:23', '', 0, ''), (179, 'test', '', '', '', '', '2017-06-20 12:43:44', '', 0, ''); -- -- Indexes for dumped tables -- -- -- Indexes for table `commentmeta` -- ALTER TABLE `commentmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `comment_id` (`comment_id`), ADD KEY `meta_key` (`meta_key`); -- -- Indexes for table `comments` -- ALTER TABLE `comments` ADD PRIMARY KEY (`comment_ID`), ADD KEY `comment_post_ID` (`comment_post_ID`), ADD KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), ADD KEY `comment_date_gmt` (`comment_date_gmt`), ADD KEY `comment_parent` (`comment_parent`); -- -- Indexes for table `links` -- ALTER TABLE `links` ADD PRIMARY KEY (`link_id`), ADD KEY `link_visible` (`link_visible`); -- -- Indexes for table `options` -- ALTER TABLE `options` ADD PRIMARY KEY (`option_id`), ADD UNIQUE KEY `option_name` (`option_name`); -- -- Indexes for table `postmeta` -- ALTER TABLE `postmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `post_id` (`post_id`), ADD KEY `meta_key` (`meta_key`); -- -- Indexes for table `posts` -- ALTER TABLE `posts` ADD PRIMARY KEY (`ID`), ADD KEY `post_name` (`post_name`), ADD KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), ADD KEY `post_parent` (`post_parent`), ADD KEY `post_author` (`post_author`); -- -- Indexes for table `terms` -- ALTER TABLE `terms` ADD PRIMARY KEY (`term_id`), ADD UNIQUE KEY `slug` (`slug`), ADD KEY `name` (`name`); -- -- Indexes for table `term_relationships` -- ALTER TABLE `term_relationships` ADD PRIMARY KEY (`object_id`,`term_taxonomy_id`), ADD KEY `term_taxonomy_id` (`term_taxonomy_id`); -- -- Indexes for table `term_taxonomy` -- ALTER TABLE `term_taxonomy` ADD PRIMARY KEY (`term_taxonomy_id`), ADD UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), ADD KEY `taxonomy` (`taxonomy`); -- -- Indexes for table `usermeta` -- ALTER TABLE `usermeta` ADD PRIMARY KEY (`umeta_id`), ADD KEY `user_id` (`user_id`), ADD KEY `meta_key` (`meta_key`); -- -- Indexes for table `users` -- ALTER TABLE `users` ADD PRIMARY KEY (`ID`), ADD KEY `user_login_key` (`user_login`), ADD KEY `user_nicename` (`user_nicename`); -- -- Indexes for table `wp_commentmeta` -- ALTER TABLE `wp_commentmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `comment_id` (`comment_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_comments` -- ALTER TABLE `wp_comments` ADD PRIMARY KEY (`comment_ID`), ADD KEY `comment_post_ID` (`comment_post_ID`), ADD KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`), ADD KEY `comment_date_gmt` (`comment_date_gmt`), ADD KEY `comment_parent` (`comment_parent`), ADD KEY `comment_author_email` (`comment_author_email`(10)); -- -- Indexes for table `wp_links` -- ALTER TABLE `wp_links` ADD PRIMARY KEY (`link_id`), ADD KEY `link_visible` (`link_visible`); -- -- Indexes for table `wp_options` -- ALTER TABLE `wp_options` ADD PRIMARY KEY (`option_id`), ADD UNIQUE KEY `option_name` (`option_name`); -- -- Indexes for table `wp_postmeta` -- ALTER TABLE `wp_postmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `post_id` (`post_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_posts` -- ALTER TABLE `wp_posts` ADD PRIMARY KEY (`ID`), ADD KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`), ADD KEY `post_parent` (`post_parent`), ADD KEY `post_author` (`post_author`), ADD KEY `post_name` (`post_name`(191)); -- -- Indexes for table `wp_termmeta` -- ALTER TABLE `wp_termmeta` ADD PRIMARY KEY (`meta_id`), ADD KEY `term_id` (`term_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_terms` -- ALTER TABLE `wp_terms` ADD PRIMARY KEY (`term_id`), ADD KEY `slug` (`slug`(191)), ADD KEY `name` (`name`(191)); -- -- Indexes for table `wp_term_relationships` -- ALTER TABLE `wp_term_relationships` ADD PRIMARY KEY (`object_id`,`term_taxonomy_id`), ADD KEY `term_taxonomy_id` (`term_taxonomy_id`); -- -- Indexes for table `wp_term_taxonomy` -- ALTER TABLE `wp_term_taxonomy` ADD PRIMARY KEY (`term_taxonomy_id`), ADD UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`), ADD KEY `taxonomy` (`taxonomy`); -- -- Indexes for table `wp_usermeta` -- ALTER TABLE `wp_usermeta` ADD PRIMARY KEY (`umeta_id`), ADD KEY `user_id` (`user_id`), ADD KEY `meta_key` (`meta_key`(191)); -- -- Indexes for table `wp_users` -- ALTER TABLE `wp_users` ADD PRIMARY KEY (`ID`), ADD KEY `user_login_key` (`user_login`), ADD KEY `user_nicename` (`user_nicename`), ADD KEY `user_email` (`user_email`); -- -- AUTO_INCREMENT for dumped tables -- -- -- AUTO_INCREMENT for table `commentmeta` -- ALTER TABLE `commentmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `comments` -- ALTER TABLE `comments` MODIFY `comment_ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=232; -- -- AUTO_INCREMENT for table `links` -- ALTER TABLE `links` MODIFY `link_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `options` -- ALTER TABLE `options` MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=133; -- -- AUTO_INCREMENT for table `postmeta` -- ALTER TABLE `postmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=57; -- -- AUTO_INCREMENT for table `posts` -- ALTER TABLE `posts` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=19; -- -- AUTO_INCREMENT for table `terms` -- ALTER TABLE `terms` MODIFY `term_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4; -- -- AUTO_INCREMENT for table `term_taxonomy` -- ALTER TABLE `term_taxonomy` MODIFY `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5; -- -- AUTO_INCREMENT for table `usermeta` -- ALTER TABLE `usermeta` MODIFY `umeta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=156; -- -- AUTO_INCREMENT for table `users` -- ALTER TABLE `users` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=169; -- -- AUTO_INCREMENT for table `wp_commentmeta` -- ALTER TABLE `wp_commentmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_comments` -- ALTER TABLE `wp_comments` MODIFY `comment_ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3; -- -- AUTO_INCREMENT for table `wp_links` -- ALTER TABLE `wp_links` MODIFY `link_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT; -- -- AUTO_INCREMENT for table `wp_options` -- ALTER TABLE `wp_options` MODIFY `option_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=332; -- -- AUTO_INCREMENT for table `wp_postmeta` -- ALTER TABLE `wp_postmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=494; -- -- AUTO_INCREMENT for table `wp_posts` -- ALTER TABLE `wp_posts` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=595; -- -- AUTO_INCREMENT for table `wp_termmeta` -- ALTER TABLE `wp_termmeta` MODIFY `meta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=12; -- -- AUTO_INCREMENT for table `wp_terms` -- ALTER TABLE `wp_terms` MODIFY `term_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5; -- -- AUTO_INCREMENT for table `wp_term_taxonomy` -- ALTER TABLE `wp_term_taxonomy` MODIFY `term_taxonomy_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5; -- -- AUTO_INCREMENT for table `wp_usermeta` -- ALTER TABLE `wp_usermeta` MODIFY `umeta_id` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=404; -- -- AUTO_INCREMENT for table `wp_users` -- ALTER TABLE `wp_users` MODIFY `ID` bigint(20) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=180; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;