sql
stringlengths 6
1.05M
|
|---|
<gh_stars>0
DROP TABLE IF EXISTS cell;
CREATE TABLE cell
(
added_at INTEGER PRIMARY KEY AUTO_INCREMENT,
driver_partner_uuid VARCHAR(36) NULL,
city_uuid VARCHAR(36) NOT NULL,
trip_created_at DATETIME NULL
) ENGINE=InnoDB;
|
olympics.schema.sql
Author: <NAME>
A .txt file containing all of the SQL queries
for the 10/15 lab
# CREATE TABLE STATEMENTS #
CREATE TABLE athletes(
athlete_id integer,
athlete_name text,
sex text);
CREATE TABLE noc(
noc_id integer,
team_name text,
noc_name text);
CREATE TABLE sport(
sport_id SERIAL,
event text);
CREATE TABLE game(
game_id integer,
game text,
year integer,
season text,
city text);
CREATE TABLE medal(
medal_id integer,
medal_type text);
CREATE TABLE connector(
athlete_id integer,
noc_id integer,
sport_id integer,
game_id integer,
medal_id integer,);
# SELECT STATEMENTS #
LIST ALL NOCS IN ALPHABETICAL ORDER BY ABBREVIATION:
SELECT * FROM noc ORDER BY team_name ASC;
LIST OF ALL ALL ATHLETES FROM KENYA:
SELECT athletes.athlete_name, noc.noc_name
FROM noc, athletes, connector
WHERE connector.noc_id = noc.noc_id
AND connector.athlete_id = athletes.athlete_id
AND noc.noc_name = 'KEN';
LIST OF MEDALS WON BY GREG LOUGANIS:
SELECT athlete_name, medal_type, year
FROM athletes, medal, game, connector
WHERE connector.athlete_id = athletes.athlete_id
AND connector.medal_id = medal.medal_id
AND connector.game_id = game.game_id
AND medal.medal_id <> 1
AND athletes.athlete_name = '<NAME> "<NAME>'
ORDER BY game.year;
|
-- phpMyAdmin SQL Dump
-- version 4.8.3
-- https://www.phpmyadmin.net/
--
-- Servidor: 127.0.0.1
-- Tiempo de generación: 05-12-2018 a las 01:02:16
-- Versión del servidor: 10.1.37-MariaDB
-- Versión de PHP: 7.2.12
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
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 */;
--
-- Base de datos: `red_social`
--
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `migrations`
--
CREATE TABLE `migrations` (
`id` int(10) UNSIGNED NOT NULL,
`migration` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`batch` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
--
-- Volcado de datos para la tabla `migrations`
--
INSERT INTO `migrations` (`id`, `migration`, `batch`) VALUES
(1, '2014_10_12_000000_create_users_table', 1),
(2, '2014_10_12_100000_create_password_resets_table', 1),
(3, '2018_11_30_054710_add_usuarios_table', 1);
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `password_resets`
--
CREATE TABLE `password_resets` (
`email` varchar(150) COLLATE utf8mb4_unicode_ci NOT NULL,
`token` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`created_at` timestamp NULL DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `users`
--
CREATE TABLE `users` (
`id` int(10) UNSIGNED NOT NULL,
`name` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`apellido` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`alias` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`fecha_nacimiento` date NOT NULL,
`email` varchar(150) COLLATE utf8mb4_unicode_ci NOT NULL,
`email_verified_at` timestamp NULL DEFAULT NULL,
`password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`remember_token` varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
`created_at` timestamp NULL DEFAULT NULL,
`updated_at` timestamp NULL DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
--
-- Volcado de datos para la tabla `users`
--
INSERT INTO `users` (`id`, `name`, `apellido`, `alias`, `fecha_nacimiento`, `email`, `email_verified_at`, `password`, `remember_token`, `created_at`, `updated_at`) VALUES
(1, 'juan', '<PASSWORD>', '<EMAIL>', '2018-12-08', '<EMAIL>', NULL, '$2y$10$NVSPGfQ8xgeGsH.pfovV4O1s74ax3LFN8xxgLclC2uqzplARlO/5W', NULL, '2018-12-05 01:20:20', '2018-12-05 01:20:20'),
(2, 'yarince', 'veliz', '<EMAIL>', '2018-12-05', '<EMAIL>', NULL, '$2y$10$zK2rzHr.Ts4ngtwdOT2oduFnRCW1KW1mPLMrLzSzgzZjBpmkjLqga', '1e6d9H0VwntCJQNsvBYKX2btgMHr24mHjgx3791EgD5IskDZpKur0BlPiIvl', '2018-12-05 01:21:39', '2018-12-05 01:21:39');
-- --------------------------------------------------------
--
-- Estructura de tabla para la tabla `usuarios`
--
CREATE TABLE `usuarios` (
`id` int(10) UNSIGNED NOT NULL,
`nombre` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`apellido` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`alias` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`fecha_nacimiento` date NOT NULL,
`email` varchar(150) COLLATE utf8mb4_unicode_ci NOT NULL,
`password` varchar(255) COLLATE utf8mb4_unicode_ci NOT NULL,
`created_at` timestamp NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`updated_at` timestamp NULL DEFAULT '0000-00-00 00:00:00'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;
--
-- Volcado de datos para la tabla `usuarios`
--
INSERT INTO `usuarios` (`id`, `nombre`, `apellido`, `alias`, `fecha_nacimiento`, `email`, `password`, `created_at`, `updated_at`) VALUES
(1, 'juan', 'veliz', '<EMAIL>', '2018-12-11', '<EMAIL>', '$2y$10$3fE3C2z5Iy4ZMsd4LI1xPO35VhP/vkqkK1U3lST7Ld17wneHvlmHG', '2018-12-04 07:08:35', '2018-12-04 07:08:35'),
(2, 'juan', 'veliz', '<EMAIL>', '2018-12-04', '<EMAIL>', '$2y$10$0wxSkJ.C.oN9GDarX5SfrOoI9AzDgUFXCpMV5hBimyM3OQAJaHto2', '2018-12-04 07:32:32', '2018-12-04 07:32:32'),
(3, 'juan', 'veliz', '<EMAIL>', '2018-12-03', '<EMAIL>', '$2y$10$AC9HAqJJFA92s0TOQXcMYO8mgSSof/Vq0Ylikoep4kheBgrsGaDpq', '2018-12-04 07:34:46', '2018-12-04 07:34:46');
--
-- Índices para tablas volcadas
--
--
-- Indices de la tabla `migrations`
--
ALTER TABLE `migrations`
ADD PRIMARY KEY (`id`);
--
-- Indices de la tabla `password_resets`
--
ALTER TABLE `password_resets`
ADD KEY `password_resets_email_index` (`email`);
--
-- Indices de la tabla `users`
--
ALTER TABLE `users`
ADD PRIMARY KEY (`id`);
--
-- Indices de la tabla `usuarios`
--
ALTER TABLE `usuarios`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT de las tablas volcadas
--
--
-- AUTO_INCREMENT de la tabla `migrations`
--
ALTER TABLE `migrations`
MODIFY `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
--
-- AUTO_INCREMENT de la tabla `users`
--
ALTER TABLE `users`
MODIFY `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT de la tabla `usuarios`
--
ALTER TABLE `usuarios`
MODIFY `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
COMMIT;
/*!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 */;
|
CREATE TABLE [Transactions] (
TransactionId int IDENTITY NOT NULL PRIMARY KEY NONCLUSTERED,
VendingMachineId char(36),
ItemName varchar(255),
ItemId int,
PurchasePrice smallmoney,
TransactionStatus int,
TransactionDate datetime,
INDEX Transactions_CCI CLUSTERED COLUMNSTORE
) WITH (
MEMORY_OPTIMIZED = ON
);
ALTER DATABASE CURRENT
SET MEMORY_OPTIMIZED_ELEVATE_TO_SNAPSHOT=ON;
|
CREATE TABLE [dbo].[CustomerUsers] (
[Id] UNIQUEIDENTIFIER NOT NULL,
[CreatedDate] DATETIMEOFFSET (7) NOT NULL,
[CustomerId] UNIQUEIDENTIFIER NOT NULL,
[CustomerName] NVARCHAR (MAX) NULL,
[CustomerRegion] INT NULL,
[FullName] NVARCHAR (MAX) NULL,
[UserName] NVARCHAR (MAX) NULL,
CONSTRAINT [PK_CustomerUsers] PRIMARY KEY CLUSTERED ([Id] ASC),
CONSTRAINT [FK_CustomerUsers_Customers_CustomerId] FOREIGN KEY ([CustomerId]) REFERENCES [dbo].[Customers] ([Id]) ON DELETE CASCADE
);
GO
CREATE NONCLUSTERED INDEX [IX_CustomerUsers_CustomerId]
ON [dbo].[CustomerUsers]([CustomerId] ASC);
|
CREATE TABLE public.geocodes (
address character varying,
geocoded_address character varying,
geocoded_lng double precision,
geocoded_lat double precision,
geocoded_city character varying,
geocoded_state character varying,
geocoded_zip character varying,
geocode_accuracy float,
geocode_accuracy_type character varying,
geocode_geojson jsonb,
geom geometry(Geometry,4326)
)
|
CREATE TABLE sources (
id serial primary key,
name text not null,
origin text not null,
kind text not null
);
CREATE TABLE records (
id serial primary key,
title text,
guid text not null,
source_id int not null constraint records_source_id_fk references sources,
content text not null,
date timestamp not null
);
create unique index records_unique_guid_source_key on records (guid, source_id);
|
CREATE TABLE `subscribe` (
`id` int NOT NULL AUTO_INCREMENT COMMENT 'primary key',
`account` varchar(255) NOT NULL COMMENT '账号',
`stock` int NOT NULL COMMENT '股票消息',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;
|
ALTER TABLE ARBEIDSLISTE ADD OVERSKRIFT VARCHAR2(500);
|
/*
Do citation counts tend to be higher in any of the datasets?
This is a standalone descriptive query.
*/
select coalesce(ds_times_cited, 0) = 0 zero_ds,
coalesce(mag_times_cited, 0) = 0 zero_mag,
count(*) count
from oecd.all_citation_counts
where ds_id is not null
and mag_id is not null
group by 1, 2
|
alter table user add column home_page_preference varchar(100);
alter table user drop column preferences;
alter table user drop column reset_password_datetime;
create table whitelist (
id bigint auto_increment not null,
domain_name varchar(50) not null,
constraint pk_whitelist primary key (id))
;
|
create database car_catalog;
\c car_catalog;
|
select c_date, c_integer, count(c_integer) over() from j1_v order by 1, 2, 3;
|
create table turmas(
id bigint(20) primary key auto_increment,
nome varchar(80) not null,
capacidade integer not null,
id_disciplina bigint(20) not null references disciplinas,
id_professor bigint(20) not null references professores
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
insert into turmas (nome, capacidade, id_disciplina, id_professor) values
('CCT001', 30, 1, 1), ('CCT002', 25, 2, 3), ('CCT003', 30, 3, 1),
('CCT004', 30, 4, 4), ('CCT005', 25, 5, 5), ('CCT006', 30, 4, 2),
('CCT007', 30, 3, 5);
|
CREATE SCHEMA [Reports]
AUTHORIZATION [dbo];
|
/*
Write an SQL query that reports for every date within at most 90 days from today,
the number of users that logged in for the first time on that date. Assume today is 2019-06-30.
*/
# Write your MySQL query statement below
select login_date, count(user_id) as user_count
from
(select user_id, min(activity_date) as login_date
from Traffic
where activity = 'login'
group by user_id) t
where datediff('2019-06-30', login_date) <= 90
group by login_date
|
<filename>tests/suites/0_stateless/02_0040_function_strings_length.sql
SELECT LENGTH('word');
SELECT LENGTH('кириллица'); -- cyrillic in russian
SELECT LENGTH('кириллица and latin');
SELECT LENGTH('你好');
SELECT LENGTH(NULL);
|
CREATE TABLE "C##LIQUIBASE".createTableDataTypeText (textCol CLOB)
|
PRINT 'Removing ProjectStatusTransitions'
DELETE FROM dbo.[ProjectStatusTransitions]
WHERE [FromWorkflowId] = 4 -- ASSESS-EX-DISPOSAL
AND [FromStatusId] = 22 -- Not in SPL
AND [ToWorkflowId] = 4 -- ASSESS-EX-DISPOSAL
AND [ToStatusId] = 23 -- Cancelled
DELETE FROM dbo.[ProjectStatusTransitions]
WHERE [FromWorkflowId] = 4 -- ASSESS-EX-DISPOSAL
AND [FromStatusId] = 22 -- Not in SPL
AND [ToWorkflowId] = 4 -- ASSESS-EX-DISPOSAL
AND [ToStatusId] = 20 -- Transferred within GRE
DELETE FROM dbo.[ProjectStatusTransitions]
WHERE [FromWorkflowId] = 4 -- 'ASSESS-EX-DISPOSAL'
AND [FromStatusId] = 22 -- Not in SPL
AND [ToWorkflowId] = 6 -- SPL
AND [ToStatusId] = 21 -- Approved for SPL
DELETE FROM dbo.[ProjectStatusTransitions]
WHERE [FromWorkflowId] = 4 -- 'ASSESS-EX-DISPOSAL'
AND [FromStatusId] = 22 -- Not in SPL
AND [ToWorkflowId] = 5 -- ERP
AND [ToStatusId] = 14 -- Approved for ERP
|
<gh_stars>1000+
CREATE TABLE "identities" (
"id" UUID NOT NULL,
PRIMARY KEY("id"),
"traits_schema_id" VARCHAR (2048) NOT NULL,
"traits" json NOT NULL,
"created_at" timestamp NOT NULL,
"updated_at" timestamp NOT NULL
);
|
<gh_stars>1-10
set grammar to oracle;
create table aa(id int, dt timestamp);
insert into aa values(1,to_date('2000-3-31','YYYY-MM-DD'));
insert into aa values(2,to_date('2000-2-29','YYYY-MM-DD'));
select months_between(to_date('2000-3-31','yyyy-mm-dd'),to_date('2000-2-29','yyyy-mm-dd')) from dual;
select id,months_between(dt,to_date('2000-2-29','yyyy-mm-dd')) from aa;
select months_between(to_date('2000-3-31','yyyy-mm-dd'),to_date('2000-4-30','yyyy-mm-dd')) from dual;
select months_between(to_date('2000-2-29','yyyy-mm-dd'),to_date('1999-2-28','yyyy-mm-dd')) from dual;
select months_between(to_date('1-1-1','yyyy-mm-dd'),to_date('9999-12-1','yyyy-mm-dd')) from dual;
select months_between(null,to_date('9999-12-1','yyyy-mm-dd')) from dual;
select months_between(to_date('2000-2-29','yyyy-mm-dd'),null) from dual;
select months_between(null,null) from dual;
select months_between(to_date('2000-4-30 23:59:59','yyyy-mm-dd hh24:mi:ss'),to_date('2000-4-30 0:0:0','yyyy-mm-dd HH24:MI:SS')) from dual;
drop table aa;
|
<filename>dss/tpch-load.sql
BEGIN;
CREATE TABLE PART (
P_PARTKEY SERIAL8,
P_NAME VARCHAR(55),
P_MFGR CHAR(25),
P_BRAND CHAR(10),
P_TYPE VARCHAR(25),
P_SIZE INTEGER,
P_CONTAINER CHAR(10),
P_RETAILPRICE DECIMAL,
P_COMMENT VARCHAR(23)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY part FROM '/tmp/dss-data/part.csv' WITH csv DELIMITER '|';
COMMIT;
BEGIN;
CREATE TABLE REGION (
R_REGIONKEY SERIAL8,
R_NAME CHAR(25),
R_COMMENT VARCHAR(152)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY region FROM '/tmp/dss-data/region.csv' WITH csv DELIMITER '|';
COMMIT;
BEGIN;
CREATE TABLE NATION (
N_NATIONKEY SERIAL8,
N_NAME CHAR(25),
N_REGIONKEY BIGINT NOT NULL, -- references R_REGIONKEY
N_COMMENT VARCHAR(152)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY nation FROM '/tmp/dss-data/nation.csv' WITH csv DELIMITER '|';
COMMIT;
BEGIN;
CREATE TABLE SUPPLIER (
S_SUPPKEY SERIAL8,
S_NAME CHAR(25),
S_ADDRESS VARCHAR(40),
S_NATIONKEY BIGINT NOT NULL, -- references N_NATIONKEY
S_PHONE CHAR(15),
S_ACCTBAL DECIMAL,
S_COMMENT VARCHAR(101)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY supplier FROM '/tmp/dss-data/supplier.csv' WITH csv DELIMITER '|';
COMMIT;
BEGIN;
CREATE TABLE CUSTOMER (
C_CUSTKEY SERIAL8,
C_NAME VARCHAR(25),
C_ADDRESS VARCHAR(40),
C_NATIONKEY BIGINT NOT NULL, -- references N_NATIONKEY
C_PHONE CHAR(15),
C_ACCTBAL DECIMAL,
C_MKTSEGMENT CHAR(10),
C_COMMENT VARCHAR(117)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY customer FROM '/tmp/dss-data/customer.csv' WITH csv DELIMITER '|';
COMMIT;
BEGIN;
CREATE TABLE PARTSUPP (
PS_PARTKEY BIGINT NOT NULL, -- references P_PARTKEY
PS_SUPPKEY BIGINT NOT NULL, -- references S_SUPPKEY
PS_AVAILQTY INTEGER,
PS_SUPPLYCOST DECIMAL,
PS_COMMENT VARCHAR(199)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY partsupp FROM '/tmp/dss-data/partsupp.csv' WITH csv DELIMITER '|';
COMMIT;
BEGIN;
CREATE TABLE ORDERS (
O_ORDERKEY SERIAL8,
O_CUSTKEY BIGINT NOT NULL, -- references C_CUSTKEY
O_ORDERSTATUS CHAR(1),
O_TOTALPRICE DECIMAL,
O_ORDERDATE DATE,
O_ORDERPRIORITY CHAR(15),
O_CLERK CHAR(15),
O_SHIPPRIORITY INTEGER,
O_COMMENT VARCHAR(79)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY orders FROM '/tmp/dss-data/orders.csv' WITH csv DELIMITER '|';
COMMIT;
BEGIN;
CREATE TABLE LINEITEM (
L_ORDERKEY BIGINT NOT NULL, -- references O_ORDERKEY
L_PARTKEY BIGINT NOT NULL, -- references P_PARTKEY (compound fk to PARTSUPP)
L_SUPPKEY BIGINT NOT NULL, -- references S_SUPPKEY (compound fk to PARTSUPP)
L_LINENUMBER INTEGER,
L_QUANTITY DECIMAL,
L_EXTENDEDPRICE DECIMAL,
L_DISCOUNT DECIMAL,
L_TAX DECIMAL,
L_RETURNFLAG CHAR(1),
L_LINESTATUS CHAR(1),
L_SHIPDATE DATE,
L_COMMITDATE DATE,
L_RECEIPTDATE DATE,
L_SHIPINSTRUCT CHAR(25),
L_SHIPMODE CHAR(10),
L_COMMENT VARCHAR(44)
) with (APPENDONLY=true,BLOCKSIZE=2097152,ORIENTATION=COLUMN,COMPRESSTYPE=QUICKLZ,CHECKSUM=true,OIDS=false);
COPY lineitem FROM '/tmp/dss-data/lineitem.csv' WITH csv DELIMITER '|';
COMMIT;
|
<reponame>softcontext/spring1107
drop table if exists emp;
--identity : 디비가 지원하는 키 생성전략을 사용한다.
--H2는 자동으로 키 값을 제너레이트 한다.
create table emp (
empno int identity not null primary key,
ename varchar(100),
job varchar(100),
sal double
);
|
-- @testpoint:opengauss关键字ada(非保留)，作为模式名
--关键字不带引号-成功
drop schema if exists ada;
create schema ada;
--清理环境
drop schema ada;
--关键字带双引号-成功
drop schema if exists "ada";
create schema "ada";
--清理环境
drop schema "ada";
--关键字带单引号-合理报错
drop schema if exists 'ada';
--关键字带反引号-合理报错
drop schema if exists `ada`;
|
<gh_stars>0
-- @testpoint:opengauss关键字Implementation(非保留)，作为字段数据类型(合理报错)
--前置条件
drop table if exists explain_test cascade;
--关键字不带引号-合理报错
create table explain_test(id int,name Implementation);
--关键字带双引号-合理报错
create table explain_test(id int,name "Implementation");
--关键字带单引号-合理报错
create table explain_test(id int,name 'Implementation');
--关键字带反引号-合理报错
create table explain_test(id int,name `Implementation`);
|
<gh_stars>0
create table users(
user_id INT AUTO_INCREMENT PRIMARY KEY,
username VARCHAR(20),
role VARCHAR(10),
email VARCHAR(50),
pin int(4)
);
|
<reponame>sarajaksa/IS2020
CREATE TABLE "anime" (
"anime" TEXT UNIQUE,
"finished" DATE,
"finished_metadata" DATE,
PRIMARY KEY("anime")
);
|
<reponame>MARobison/Cleesh-ayy-yeet<gh_stars>0
/*
Insertions for TASK table
*/
insert into task ( task_label, create_date, due_date) values ('Assignment 1', CURDATE(), '2018-09-04');
insert into task (task_label, create_date, due_date) values ('Assignment 3', CURDATE(), '2018-08-02');
insert into task (task_label, create_date, due_date) values ('Project 1',CURDATE(), '2018-09-22');
insert into task (task_label, create_date, due_date) values ('Midterm 2',CURDATE(), '2018-09-25');
insert into task (task_label, create_date, due_date) values ('Final',CURDATE(), '2018-10-19');
insert into task (task_label, create_date, due_date) values ('Assignment 2',CURDATE(), '2018-05-17');
insert into task (task_label, create_date, due_date) values ('Midterm 1',CURDATE(), '2018-05-15');
insert into task (task_label, create_date, due_date) values ('Final Project',CURDATE(), '2018-08-24');
insert into task (task_label, create_date, due_date) values ('Project 2',CURDATE(), '2018-07-06');
insert into task (task_label, create_date, due_date) values ('Extra Credit',CURDATE(), '2018-09-07');
insert into task (task_label, create_date, due_date) values ('Spring Cleaning','2018-01-01', '2018-05-05');
/*
Insertions for TAG table
*/
insert into tag (tag_id, tag_label) values (1, 'school');
insert into tag (tag_id, tag_label) values (2, 'homework');
insert into tag (tag_id, tag_label) values (3, 'exam');
insert into tag (tag_id, tag_label) values (4, 'project');
insert into tag (tag_id, tag_label) values (5, 'final');
insert into tag (tag_id, tag_label) values (6, 'PRIORITY');
insert into tag (tag_id, tag_label) values (7, 'extra credit');
insert into tag (tag_id, tag_label) values (8, 'chore');
/*
Insertions for TAGGED table
*/
insert into assign(task_id, tag_id) values (1, 1);
insert into assign(task_id, tag_id) values (1, 2);
insert into assign(task_id, tag_id) values (2, 1);
insert into assign(task_id, tag_id) values (2, 2);
insert into assign(task_id, tag_id) values (3, 1);
insert into assign(task_id, tag_id) values (3, 4);
insert into assign(task_id, tag_id) values (4, 1);
insert into assign(task_id, tag_id) values (4, 3);
insert into assign(task_id, tag_id) values (5, 1);
insert into assign(task_id, tag_id) values (5, 5);
insert into assign(task_id, tag_id) values (5, 6);
insert into assign(task_id, tag_id) values (6, 1);
insert into assign(task_id, tag_id) values (6, 2);
insert into assign(task_id, tag_id) values (7, 1);
insert into assign(task_id, tag_id) values (7, 3);
insert into assign(task_id, tag_id) values (8, 1);
insert into assign(task_id, tag_id) values (8, 4);
insert into assign(task_id, tag_id) values (8, 6);
insert into assign(task_id, tag_id) values (9, 1);
insert into assign(task_id, tag_id) values (9, 4);
insert into assign(task_id, tag_id) values (10, 1);
insert into assign(task_id, tag_id) values (10, 7);
insert into assign(task_id, tag_id) values (11, 8);
|
<filename>homework-3/db_create_titile.sql
/*Требует наличия спавочника по языкам*/
CREATE TABLE IF NOT EXISTS movie_title
(
MOVIE_ID int not null,
LANGUAGE_ID char(2) not null,
TITLE varchar(500) not null,
PRIMARY KEY (MOVIE_ID, LANGUAGE_ID),
FOREIGN KEY FK_MT_MOVIE (MOVIE_ID)
REFERENCES movie (ID)
ON UPDATE RESTRICT
ON DELETE RESTRICT,
FOREIGN KEY FK_MT_LANGUAGE (LANGUAGE_ID)
REFERENCES language (ID)
ON UPDATE RESTRICT
ON DELETE RESTRICT
);
|
CREATE TRIGGER tr_DeleteEmployees
ON Employees
AFTER DELETE
AS
BEGIN
INSERT INTO Deleted_Employees
SELECT
FirstName,
LastName,
MiddleName,
JobTitle,
DepartmentID,
Salary
FROM deleted
END
|
<reponame>setor7soft/mapos<filename>updates/update_v3.3.x_to_3.4.x.sql
-- -----------------------------------------------------
-- Table `Garantia`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `garantias` (
`idGarantias` INT NOT NULL AUTO_INCREMENT,
`dataGarantia` DATE NULL,
`refGarantia` VARCHAR(15) NULL,
`textoGarantia` VARCHAR(2000) NULL,
`usuarios_id` INT(11) NULL,
PRIMARY KEY (`idGarantias`),
INDEX `fk_garantias_usuarios1` (`usuarios_id` ASC),
CONSTRAINT `fk_garantias_usuarios1`
FOREIGN KEY (`usuarios_id`)
REFERENCES `usuarios` (`idUsuarios`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
ALTER TABLE `os` ADD `garantias_id` INT NULL;
|
-- MySQL Script generated by MySQL Workbench
-- Sat Nov 28 22:18:52 2020
-- Model: New Model Version: 1.0
-- MySQL Workbench Forward Engineering
SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION';
-- -----------------------------------------------------
-- Schema mydb
-- -----------------------------------------------------
-- -----------------------------------------------------
-- Schema mydb
-- -----------------------------------------------------
CREATE SCHEMA IF NOT EXISTS `mydb` DEFAULT CHARACTER SET utf8 ;
USE `mydb` ;
-- -----------------------------------------------------
-- Table `mydb`.`produto`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`produto` (
`idproduto` INT NOT NULL AUTO_INCREMENT,
`nome` VARCHAR(80) NOT NULL,
`valor` FLOAT NOT NULL,
`descricao` TEXT NOT NULL,
`genero` VARCHAR(60) NOT NULL,
`classificacao` INT NOT NULL,
`plataforma` VARCHAR(60) NOT NULL,
`lancamento` DATE NOT NULL,
PRIMARY KEY (`idproduto`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`plataforma`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`plataforma` (
`idplataforma` INT NOT NULL AUTO_INCREMENT,
`nome` VARCHAR(45) NOT NULL,
`valor` FLOAT NOT NULL,
`lancamento` DATE NOT NULL,
`descricao` TEXT NOT NULL,
PRIMARY KEY (`idplataforma`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`inventario`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`inventario` (
`idinventario` INT NOT NULL AUTO_INCREMENT,
`nome` VARCHAR(80) NOT NULL,
`aquisicao` DATE NOT NULL,
`produto_idproduto` INT NOT NULL,
`valor` FLOAT NOT NULL,
`plataforma_idplataforma` INT NOT NULL,
PRIMARY KEY (`idinventario`, `produto_idproduto`, `plataforma_idplataforma`),
INDEX `fk_inventario_produto1_idx` (`produto_idproduto` ASC),
INDEX `fk_inventario_plataforma1_idx` (`plataforma_idplataforma` ASC),
CONSTRAINT `fk_inventario_produto1`
FOREIGN KEY (`produto_idproduto`)
REFERENCES `mydb`.`produto` (`idproduto`)
ON DELETE NO ACTION
ON UPDATE NO ACTION,
CONSTRAINT `fk_inventario_plataforma1`
FOREIGN KEY (`plataforma_idplataforma`)
REFERENCES `mydb`.`plataforma` (`idplataforma`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`usuario`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`usuario` (
`idusuario` INT NOT NULL AUTO_INCREMENT,
`nome` VARCHAR(80) NOT NULL,
`nascimento` DATE NOT NULL,
`cpf` VARCHAR(14) NOT NULL,
`email` VARCHAR(80) NOT NULL,
`senha` VARCHAR(150) NOT NULL,
`tipo` INT NOT NULL,
`endereco` VARCHAR(80) NOT NULL,
`telefone` VARCHAR(45) NOT NULL,
PRIMARY KEY (`idusuario`))
ENGINE = InnoDB;
-- -----------------------------------------------------
-- Table `mydb`.`pedido`
-- -----------------------------------------------------
CREATE TABLE IF NOT EXISTS `mydb`.`pedido` (
`idpedido` INT NOT NULL AUTO_INCREMENT,
`produto_idproduto` INT NOT NULL,
`usuario_idusuario` INT NOT NULL,
`plataforma_idplataforma` INT NOT NULL,
`dataPedido` DATE NOT NULL,
`endereco` VARCHAR(45) NOT NULL,
`dataEntrega` VARCHAR(45) NOT NULL,
PRIMARY KEY (`idpedido`, `produto_idproduto`, `usuario_idusuario`, `plataforma_idplataforma`),
INDEX `fk_pedido_produto1_idx` (`produto_idproduto` ASC),
INDEX `fk_pedido_usuario1_idx` (`usuario_idusuario` ASC),
INDEX `fk_pedido_plataforma1_idx` (`plataforma_idplataforma` ASC),
CONSTRAINT `fk_pedido_produto1`
FOREIGN KEY (`produto_idproduto`)
REFERENCES `mydb`.`produto` (`idproduto`)
ON DELETE NO ACTION
ON UPDATE NO ACTION,
CONSTRAINT `fk_pedido_usuario1`
FOREIGN KEY (`usuario_idusuario`)
REFERENCES `mydb`.`usuario` (`idusuario`)
ON DELETE NO ACTION
ON UPDATE NO ACTION,
CONSTRAINT `fk_pedido_plataforma1`
FOREIGN KEY (`plataforma_idplataforma`)
REFERENCES `mydb`.`plataforma` (`idplataforma`)
ON DELETE NO ACTION
ON UPDATE NO ACTION)
ENGINE = InnoDB;
SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;
|
-- MySQL dump 10.13 Distrib 8.0.19, for Linux (x86_64)
--
-- Host: localhost Database: wordpress
-- ------------------------------------------------------
-- Server version 8.0.19
/*!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 */;
/*!50503 SET NAMES utf8mb4 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table `wp_commentmeta`
--
DROP TABLE IF EXISTS `wp_commentmeta`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_commentmeta` (
`meta_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`comment_id` bigint unsigned NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (`meta_id`),
KEY `comment_id` (`comment_id`),
KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_commentmeta`
--
LOCK TABLES `wp_commentmeta` WRITE;
/*!40000 ALTER TABLE `wp_commentmeta` DISABLE KEYS */;
/*!40000 ALTER TABLE `wp_commentmeta` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_comments`
--
DROP TABLE IF EXISTS `wp_comments`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_comments` (
`comment_ID` bigint unsigned NOT NULL AUTO_INCREMENT,
`comment_post_ID` bigint unsigned NOT NULL DEFAULT '0',
`comment_author` tinytext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`comment_author_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_author_url` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_author_IP` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`comment_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`comment_content` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`comment_karma` int NOT NULL DEFAULT '0',
`comment_approved` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '1',
`comment_agent` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_parent` bigint unsigned NOT NULL DEFAULT '0',
`user_id` bigint unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (`comment_ID`),
KEY `comment_post_ID` (`comment_post_ID`),
KEY `comment_approved_date_gmt` (`comment_approved`,`comment_date_gmt`),
KEY `comment_date_gmt` (`comment_date_gmt`),
KEY `comment_parent` (`comment_parent`),
KEY `comment_author_email` (`comment_author_email`(10))
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_comments`
--
LOCK TABLES `wp_comments` WRITE;
/*!40000 ALTER TABLE `wp_comments` DISABLE KEYS */;
INSERT INTO `wp_comments` VALUES (1,1,'A WordPress Commenter','<EMAIL>','https://wordpress.org/','','2020-02-08 17:46:49','2020-02-08 17:46:49','Hi, this is a comment.\nTo get started with moderating, editing, and deleting comments, please visit the Comments screen in the dashboard.\nCommenter avatars come from <a href=\"https://gravatar.com\">Gravatar</a>.',0,'1','','',0,0);
/*!40000 ALTER TABLE `wp_comments` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_links`
--
DROP TABLE IF EXISTS `wp_links`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_links` (
`link_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`link_url` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_name` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_image` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_target` varchar(25) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_description` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_visible` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'Y',
`link_owner` bigint unsigned NOT NULL DEFAULT '1',
`link_rating` int NOT NULL DEFAULT '0',
`link_updated` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`link_rel` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`link_notes` mediumtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`link_rss` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
PRIMARY KEY (`link_id`),
KEY `link_visible` (`link_visible`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_links`
--
LOCK TABLES `wp_links` WRITE;
/*!40000 ALTER TABLE `wp_links` DISABLE KEYS */;
/*!40000 ALTER TABLE `wp_links` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_options`
--
DROP TABLE IF EXISTS `wp_options`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_options` (
`option_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`option_name` varchar(191) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`option_value` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`autoload` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'yes',
PRIMARY KEY (`option_id`),
UNIQUE KEY `option_name` (`option_name`),
KEY `autoload` (`autoload`)
) ENGINE=InnoDB AUTO_INCREMENT=164 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_options`
--
LOCK TABLES `wp_options` WRITE;
/*!40000 ALTER TABLE `wp_options` DISABLE KEYS */;
INSERT INTO `wp_options` VALUES (1,'siteurl','http://localhost','yes'),(2,'home','http://localhost','yes'),(3,'blogname','<NAME>','yes'),(4,'blogdescription','Vinicius Fotografia e Cobertura de eventos.','yes'),(5,'users_can_register','0','yes'),(6,'admin_email','<EMAIL>','yes'),(7,'start_of_week','1','yes'),(8,'use_balanceTags','0','yes'),(9,'use_smilies','1','yes'),(10,'require_name_email','1','yes'),(11,'comments_notify','1','yes'),(12,'posts_per_rss','10','yes'),(13,'rss_use_excerpt','0','yes'),(14,'mailserver_url','mail.example.com','yes'),(15,'mailserver_login','<EMAIL>','yes'),(16,'mailserver_pass','password','<PASSWORD>'),(17,'mailserver_port','110','yes'),(18,'default_category','1','yes'),(19,'default_comment_status','open','yes'),(20,'default_ping_status','open','yes'),(21,'default_pingback_flag','1','yes'),(22,'posts_per_page','10','yes'),(23,'date_format','F j, Y','yes'),(24,'time_format','g:i a','yes'),(25,'links_updated_date_format','F j, Y g:i a','yes'),(26,'comment_moderation','0','yes'),(27,'moderation_notify','1','yes'),(28,'permalink_structure','','yes'),(29,'rewrite_rules','','yes'),(30,'hack_file','0','yes'),(31,'blog_charset','UTF-8','yes'),(32,'moderation_keys','','no'),(33,'active_plugins','a:0:{}','yes'),(34,'category_base','','yes'),(35,'ping_sites','http://rpc.pingomatic.com/','yes'),(36,'comment_max_links','2','yes'),(37,'gmt_offset','0','yes'),(38,'default_email_category','1','yes'),(39,'recently_edited','','no'),(40,'template','photoblogster','yes'),(41,'stylesheet','photoblogster','yes'),(42,'comment_whitelist','1','yes'),(43,'blacklist_keys','','no'),(44,'comment_registration','0','yes'),(45,'html_type','text/html','yes'),(46,'use_trackback','0','yes'),(47,'default_role','subscriber','yes'),(48,'db_version','45805','yes'),(49,'uploads_use_yearmonth_folders','1','yes'),(50,'upload_path','','yes'),(51,'blog_public','1','yes'),(52,'default_link_category','2','yes'),(53,'show_on_front','posts','yes'),(54,'tag_base','','yes'),(55,'show_avatars','1','yes'),(56,'avatar_rating','G','yes'),(57,'upload_url_path','','yes'),(58,'thumbnail_size_w','150','yes'),(59,'thumbnail_size_h','150','yes'),(60,'thumbnail_crop','1','yes'),(61,'medium_size_w','300','yes'),(62,'medium_size_h','300','yes'),(63,'avatar_default','mystery','yes'),(64,'large_size_w','1024','yes'),(65,'large_size_h','1024','yes'),(66,'image_default_link_type','none','yes'),(67,'image_default_size','','yes'),(68,'image_default_align','','yes'),(69,'close_comments_for_old_posts','0','yes'),(70,'close_comments_days_old','14','yes'),(71,'thread_comments','1','yes'),(72,'thread_comments_depth','5','yes'),(73,'page_comments','0','yes'),(74,'comments_per_page','50','yes'),(75,'default_comments_page','newest','yes'),(76,'comment_order','asc','yes'),(77,'sticky_posts','a:0:{}','yes'),(78,'widget_categories','a:2:{i:2;a:4:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:12:\"hierarchical\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(79,'widget_text','a:3:{i:2;a:4:{s:5:\"title\";s:15:\"About This Site\";s:4:\"text\";s:85:\"This may be a good place to introduce yourself and your site or include some credits.\";s:6:\"filter\";b:1;s:6:\"visual\";b:1;}i:3;a:4:{s:5:\"title\";s:7:\"Find Us\";s:4:\"text\";s:168:\"<strong>Address</strong>\n123 Main Street\nNew York, NY 10001\n\n<strong>Hours</strong>\nMonday—Friday: 9:00AM–5:00PM\nSaturday & Sunday: 11:00AM–3:00PM\";s:6:\"filter\";b:1;s:6:\"visual\";b:1;}s:12:\"_multiwidget\";i:1;}','yes'),(80,'widget_rss','a:2:{i:1;a:0:{}s:12:\"_multiwidget\";i:1;}','yes'),(81,'uninstall_plugins','a:0:{}','no'),(82,'timezone_string','','yes'),(83,'page_for_posts','0','yes'),(84,'page_on_front','0','yes'),(85,'default_post_format','0','yes'),(86,'link_manager_enabled','0','yes'),(87,'finished_splitting_shared_terms','1','yes'),(88,'site_icon','0','yes'),(89,'medium_large_size_w','768','yes'),(90,'medium_large_size_h','0','yes'),(91,'wp_page_for_privacy_policy','3','yes'),(92,'show_comments_cookies_opt_in','1','yes'),(93,'admin_email_lifespan','1596736008','yes'),(94,'initial_db_version','45805','yes'),(95,'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'),(96,'fresh_site','1','yes'),(97,'widget_search','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(98,'widget_recent-posts','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(99,'widget_recent-comments','a:2:{i:2;a:2:{s:5:\"title\";s:0:\"\";s:6:\"number\";i:5;}s:12:\"_multiwidget\";i:1;}','yes'),(100,'widget_archives','a:2:{i:2;a:3:{s:5:\"title\";s:0:\"\";s:5:\"count\";i:0;s:8:\"dropdown\";i:0;}s:12:\"_multiwidget\";i:1;}','yes'),(101,'widget_meta','a:2:{i:2;a:1:{s:5:\"title\";s:0:\"\";}s:12:\"_multiwidget\";i:1;}','yes'),(102,'sidebars_widgets','a:6:{s:19:\"wp_inactive_widgets\";a:2:{i:0;s:6:\"text-2\";i:1;s:6:\"text-3\";}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:18:\"footer_widget_left\";a:0:{}s:20:\"footer_widget_middle\";a:0:{}s:19:\"footer_widget_right\";a:0:{}s:13:\"array_version\";i:3;}','yes'),(103,'cron','a:6:{i:1581194918;a:1:{s:34:\"wp_privacy_delete_old_export_files\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:6:\"hourly\";s:4:\"args\";a:0:{}s:8:\"interval\";i:3600;}}}i:1581227318;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:1581270517;a:1:{s:32:\"recovery_mode_clean_expired_keys\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1581271592;a:2:{s:19:\"wp_scheduled_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}s:25:\"delete_expired_transients\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}i:1581271593;a:1:{s:30:\"wp_scheduled_auto_draft_delete\";a:1:{s:32:\"40cd750bba9870f18aada2478b24840a\";a:3:{s:8:\"schedule\";s:5:\"daily\";s:4:\"args\";a:0:{}s:8:\"interval\";i:86400;}}}s:7:\"version\";i:2;}','yes'),(104,'widget_pages','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(105,'widget_calendar','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(106,'widget_media_audio','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(107,'widget_media_image','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(108,'widget_media_gallery','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(109,'widget_media_video','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(110,'widget_tag_cloud','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(111,'widget_nav_menu','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(112,'widget_custom_html','a:1:{s:12:\"_multiwidget\";i:1;}','yes'),(114,'theme_mods_twentytwenty','a:2:{s:18:\"custom_css_post_id\";i:-1;s:16:\"sidebars_widgets\";a:2:{s:4:\"time\";i:1581185623;s:4:\"data\";a:3:{s:19:\"wp_inactive_widgets\";a:0:{}s:9:\"sidebar-1\";a:3:{i:0;s:8:\"search-2\";i:1;s:14:\"recent-posts-2\";i:2;s:17:\"recent-comments-2\";}s:9:\"sidebar-2\";a:3:{i:0;s:10:\"archives-2\";i:1;s:12:\"categories-2\";i:2;s:6:\"meta-2\";}}}}','yes'),(115,'recovery_keys','a:0:{}','yes'),(116,'_site_transient_update_core','O:8:\"stdClass\":4:{s:7:\"updates\";a:1:{i:0;O:8:\"stdClass\":10:{s:8:\"response\";s:6:\"latest\";s:8:\"download\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.3.2.zip\";s:6:\"locale\";s:5:\"en_US\";s:8:\"packages\";O:8:\"stdClass\":5:{s:4:\"full\";s:59:\"https://downloads.wordpress.org/release/wordpress-5.3.2.zip\";s:10:\"no_content\";s:70:\"https://downloads.wordpress.org/release/wordpress-5.3.2-no-content.zip\";s:11:\"new_bundled\";s:71:\"https://downloads.wordpress.org/release/wordpress-5.3.2-new-bundled.zip\";s:7:\"partial\";b:0;s:8:\"rollback\";b:0;}s:7:\"current\";s:5:\"5.3.2\";s:7:\"version\";s:5:\"5.3.2\";s:11:\"php_version\";s:6:\"5.6.20\";s:13:\"mysql_version\";s:3:\"5.0\";s:11:\"new_bundled\";s:3:\"5.3\";s:15:\"partial_version\";s:0:\"\";}}s:12:\"last_checked\";i:1581185616;s:15:\"version_checked\";s:5:\"5.3.2\";s:12:\"translations\";a:0:{}}','no'),(118,'_site_transient_update_plugins','O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1581185616;s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}s:9:\"no_update\";a:2:{s:19:\"akismet/akismet.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:21:\"w.org/plugins/akismet\";s:4:\"slug\";s:7:\"akismet\";s:6:\"plugin\";s:19:\"akismet/akismet.php\";s:11:\"new_version\";s:5:\"4.1.3\";s:3:\"url\";s:38:\"https://wordpress.org/plugins/akismet/\";s:7:\"package\";s:56:\"https://downloads.wordpress.org/plugin/akismet.4.1.3.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:59:\"https://ps.w.org/akismet/assets/icon-256x256.png?rev=969272\";s:2:\"1x\";s:59:\"https://ps.w.org/akismet/assets/icon-128x128.png?rev=969272\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:61:\"https://ps.w.org/akismet/assets/banner-772x250.jpg?rev=479904\";}s:11:\"banners_rtl\";a:0:{}}s:9:\"hello.php\";O:8:\"stdClass\":9:{s:2:\"id\";s:25:\"w.org/plugins/hello-dolly\";s:4:\"slug\";s:11:\"hello-dolly\";s:6:\"plugin\";s:9:\"hello.php\";s:11:\"new_version\";s:5:\"1.7.2\";s:3:\"url\";s:42:\"https://wordpress.org/plugins/hello-dolly/\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/plugin/hello-dolly.1.7.2.zip\";s:5:\"icons\";a:2:{s:2:\"2x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-256x256.jpg?rev=2052855\";s:2:\"1x\";s:64:\"https://ps.w.org/hello-dolly/assets/icon-128x128.jpg?rev=2052855\";}s:7:\"banners\";a:1:{s:2:\"1x\";s:66:\"https://ps.w.org/hello-dolly/assets/banner-772x250.jpg?rev=2052855\";}s:11:\"banners_rtl\";a:0:{}}}}','no'),(119,'_site_transient_timeout_theme_roots','1581187415','no'),(120,'_site_transient_theme_roots','a:5:{s:13:\"photoblogster\";s:7:\"/themes\";s:14:\"twentynineteen\";s:7:\"/themes\";s:15:\"twentyseventeen\";s:7:\"/themes\";s:13:\"twentysixteen\";s:7:\"/themes\";s:12:\"twentytwenty\";s:7:\"/themes\";}','no'),(122,'_site_transient_timeout_browser_428f289d131527a8146ba85d8282beb4','1581789992','no'),(123,'_site_transient_browser_428f289d131527a8146ba85d8282beb4','a:10:{s:4:\"name\";s:6:\"Chrome\";s:7:\"version\";s:13:\"79.0.3945.130\";s:8:\"platform\";s:9:\"Macintosh\";s:10:\"update_url\";s:29:\"https://www.google.com/chrome\";s:7:\"img_src\";s:43:\"http://s.w.org/images/browsers/chrome.png?1\";s:11:\"img_src_ssl\";s:44:\"https://s.w.org/images/browsers/chrome.png?1\";s:15:\"current_version\";s:2:\"18\";s:7:\"upgrade\";b:0;s:8:\"insecure\";b:0;s:6:\"mobile\";b:0;}','no'),(124,'_site_transient_timeout_php_check_9ebfd0137bc00e03d9dbfb76ffb119e8','1581789993','no'),(125,'_site_transient_php_check_9ebfd0137bc00e03d9dbfb76ffb119e8','a:5:{s:19:\"recommended_version\";s:3:\"7.3\";s:15:\"minimum_version\";s:6:\"5.6.20\";s:12:\"is_supported\";b:1;s:9:\"is_secure\";b:1;s:13:\"is_acceptable\";b:1;}','no'),(128,'can_compress_scripts','0','no'),(129,'_site_transient_timeout_community-events-2eef883554c6a8b141bb80b5a73a1a02','1581228396','no'),(130,'_site_transient_community-events-2eef883554c6a8b141bb80b5a73a1a02','a:3:{s:9:\"sandboxed\";b:0;s:8:\"location\";a:1:{s:2:\"ip\";s:10:\"172.23.0.0\";}s:6:\"events\";a:1:{i:0;a:8:{s:4:\"type\";s:6:\"meetup\";s:5:\"title\";s:62:\"SEO técnico na prática + Planejamento e gestão de conteúdo\";s:3:\"url\";s:48:\"https://www.meetup.com/wpsampa/events/268447792/\";s:6:\"meetup\";s:20:\"WordPress São Paulo\";s:10:\"meetup_url\";s:31:\"https://www.meetup.com/wpsampa/\";s:4:\"date\";s:19:\"2020-02-13 19:00:00\";s:8:\"end_date\";s:19:\"2020-02-13 22:00:00\";s:8:\"location\";a:4:{s:8:\"location\";s:18:\"São Paulo, Brazil\";s:7:\"country\";s:2:\"br\";s:8:\"latitude\";d:-23.55703163147;s:9:\"longitude\";d:-46.662288665771;}}}}','no'),(131,'_transient_timeout_feed_9bbd59226dc36b9b26cd43f15694c5c3','1581228397','no'),(132,'_transient_feed_9bbd59226dc36b9b26cd43f15694c5c3','a:4:{s:5:\"child\";a:1:{s:0:\"\";a:1:{s:3:\"rss\";a:1:{i:0;a:6:{s:4:\"data\";s:3:\"\n\n\n\";s:7:\"attribs\";a:1:{s:0:\"\";a:1:{s:7:\"version\";s:3:\"2.0\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:1:{s:0:\"\";a:1:{s:7:\"channel\";a:1:{i:0;a:6:{s:4:\"data\";s:49:\"\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:7:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:27:\"News – – WordPress.org\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:26:\"https://wordpress.org/news\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"WordPress News\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:13:\"lastBuildDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Feb 2020 09:54:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"language\";a:1:{i:0;a:5:{s:4:\"data\";s:5:\"en-US\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:9:\"generator\";a:1:{i:0;a:5:{s:4:\"data\";s:40:\"https://wordpress.org/?v=5.4-alpha-47202\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"item\";a:10:{i:0;a:6:{s:4:\"data\";s:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"The Month in WordPress: January 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2020/02/the-month-in-wordpress-january-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Feb 2020 09:54:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8316\";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:\"Following an action-packed December, 2020 is off to a fine start with some new releases and announcements. Read on to find out what happened in the WordPress project in January. Release of Gutenberg 7.2 & 7.3 Gutenberg 7.2, the first Gutenberg release of 2020, was deployed on January 8th and included over 180 pull requests […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"<NAME>\";s: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:5943:\"\n<p>Following an action-packed December, 2020 is off to a fine start with some new releases and announcements. Read on to find out what happened in the WordPress project in January.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Release of Gutenberg 7.2 & 7.3</h2>\n\n\n\n<p><a href=\"https://make.wordpress.org/core/2020/01/09/whats-new-in-gutenberg-8-january/\">Gutenberg 7.2</a>, the first Gutenberg release of 2020, was deployed on January 8th and included over 180 pull requests from more than 56 contributors. This was followed soon after by <a href=\"https://make.wordpress.org/core/2020/01/22/whats-new-in-gutenberg-22-january/\">Gutenberg 7.3</a>. New features include a new Buttons block, support in adding links to Media & Text block images, improvements to the Navigation and Gallery blocks, performance improvements, and accessibility enhancements. These releases also included many additional enhancements, fixes, new APIs, documentation, and more.</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Proposal for an XML Sitemaps Feature Plugin</h2>\n\n\n\n<p>In June last year, a team of contributors <a href=\"https://make.wordpress.org/core/2019/06/12/xml-sitemaps-feature-project-proposal/\">proposed</a> a feature plugin that would bring standardized XML sitemaps to WordPress Core. Since then, the team has been working to bring this to reality and <a href=\"https://make.wordpress.org/core/2020/01/27/feature-plugin-xml-sitemaps/\">have now published a working plugin</a> to demonstrate this new capability.</p>\n\n\n\n<p>The plugin is still in development, but the included features already provide much-needed functionality from which all WordPress sites can benefit. You can install the plugin from your WordPress dashboard or <a href=\"https://wordpress.org/plugins/core-sitemaps/\">download it here</a>.</p>\n\n\n\n<p>Want to get involved in bringing this feature to Core? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, report any issues you find <a href=\"https://github.com/GoogleChromeLabs/wp-sitemaps/issues\">on GitHub</a>, and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>A New Block-Based Themes Meeting</h2>\n\n\n\n<p>The Theme Review Team has <a href=\"https://make.wordpress.org/themes/2020/01/29/new-bi-weekly-block-based-themes-meeting/\">announced</a> that they will be holding bi-weekly meetings in the #themereview channel focused on discussing block-based themes. If you are interested in discussing themes within the context of Gutenberg’s full-site editing framework, this will be the place to do so! The first meeting will be held on Wednesday, February 5, at 16:00 UTC.</p>\n\n\n\n<p>Want to get involved with the Theme Review Team or <a href=\"https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/\">become a reviewer</a>? Follow <a href=\"https://make.wordpress.org/themes/\">their blog</a>, and join the #themereview channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading</h2>\n\n\n\n<ul><li>The Core team has started work on WordPress 5.4 and kicked off their planning with <a href=\"https://make.wordpress.org/core/2020/01/14/wordpress-5-4-planning-roundup/\">a summary post</a>. You can follow all the v5.4 updates by watching <a href=\"https://make.wordpress.org/core/tag/5-4/\">the version tag</a> on the Core team blog.</li><li>The inaugural <a href=\"https://2020.asia.wordcamp.org/\">WordCamp Asia</a> event is taking place in February. This will be the largest WordPress event in the region, bringing together around 1,500 WordPress enthusiasts from around the world.</li><li>Two WordPress community leaders, <a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a> and <a href=\'https://profiles.wordpress.org/andreamiddleton/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>andreamiddleton</a>, <a href=\"https://wordpress.org/news/2020/01/wordpress-leaders-nominated-for-cmx-awards/\">were nominated for CMX awards</a> due to their work on the WordPress project, with <a href=\'https://profiles.wordpress.org/andreamiddleton/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>andreamiddleton</a> winning the award for Executive Leader of a Community Team.</li><li><a href=\"https://make.wordpress.org/core/2020/01/29/lazy-loading-images-in-wordpress-core/\">A feature plugin has been proposed</a> that introduces lazy-loading images to WordPress Core, which will be a huge step forward in improving performance all across the web.</li><li>The Core team has put together <a href=\"https://make.wordpress.org/core/handbook/tutorials/faq-for-new-contributors/\">an extensive and informative FAQ</a> to help new contributors get involved in contributing to the project.</li><li>One key priority for Gutenberg is the ability to control the block editor. There are already a number of APIs that control the experience, but there is a lack of consistency and missing APIs. <a href=\"https://make.wordpress.org/core/2020/01/23/controlling-the-block-editor/\">A method to address this</a> has been proposed.</li><li>The Design team <a href=\"https://make.wordpress.org/design/2020/01/24/gutenberg-phase-2-friday-design-update-43/\">published detailed information</a> on the recent design improvements in Gutenberg.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\n\";s: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:\"8316\";s: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:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:36:\"People of WordPress: <NAME>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2020/01/people-of-wordpress-robert-cheleuka/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 25 Jan 2020 15:26: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:9:\"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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8300\";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:\"You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories. Meet Robert Cheleuka Robert is a self-taught graphic and motion designer turned web […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:16:\"Yvette Sonneveld\";s: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:8428:\"\n<p><em>You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.</em></p>\n\n\n\n<h2><strong>Meet <NAME></strong></h2>\n\n\n\n<p>Robert is a self-taught graphic and motion designer turned web designer (and aspiring web developer) from Malawi, Africa. Over the years, he has grown fond of WordPress and has become a loyal user. Still, the journey is rough.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2020/01/DSC08818.jpg?resize=632%2C790&ssl=1\" alt=\"<NAME>\" class=\"wp-image-8303\" data-recalc-dims=\"1\" /><figcaption><NAME></figcaption></figure>\n\n\n\n<h3><strong>Malawi</strong></h3>\n\n\n\n<p>Malawi is one of the poorest countries in the world. A tiny landlocked country with a population of 17 million, it’s largely rural and still considered a developing country. The average entry-level monthly pay for most skilled jobs is about $110. If you’re employed full-time in the creative industry and if you’re very lucky, you might be able to earn more than that. Employees earning more than $300 a month are rare to non-existent.</p>\n\n\n\n<p>Robert has been a freelance graphic designer since about 2011. He started by doing gigs from his dorm in college and from home. Earnings from his freelance jobs increased his interest in entrepreneurship and he started to consider starting his own creative agency.</p>\n\n\n\n<h3><strong>How Robert was introduced to WordPress</strong></h3>\n\n\n\n<p>Robert first came into contact with WordPress in 2014 when he and a friend started a local tech blog. Before that, all he knew was basic, outdated HTML from high school and some knowledge of Adobe Dreamweaver. They decided to use WordPress, and their new blog looked like it came from the future. They used a theme from the repo and got such positive feedback from the blog they decided to open a content and media publishing agency.</p>\n\n\n\n<p>While they got a few web redesign jobs thanks to the exposure the blog brought, they lacked the administrative and business skills needed and ended up going their separate ways. Then in his first real job after college Robert finally took it upon himself to learn the ins and outs of WordPress. He learned how to install WordPress on a server and did some research on customizing themes. </p>\n\n\n\n<p>With that knowledge alone he got his first web design clients and started earning nearly as much as he did at his job. Robert soon realized that free WordPress themes would only take him so far, especially with his limited code skills.</p>\n\n\n\n<p>Because in Malawi only people who travel abroad have access to credit cards, paying for premium themes was impossible. Like many WordPress designers in developing countries, Robert turned to using pirated themes instead. He knew that was both unsafe and unethical, and decided to learn how to code. Knowing how to build themes from scratch would surely help him rise above the competition. </p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2020/01/20180905_1971270886435744_8835917058488139776_n.jpg?fit=632%2C632&ssl=1\" alt=\"\" class=\"wp-image-8304\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2020/01/20180905_1971270886435744_8835917058488139776_n.jpg?w=1080&ssl=1 1080w, https://i1.wp.com/wordpress.org/news/files/2020/01/20180905_1971270886435744_8835917058488139776_n.jpg?resize=300%2C300&ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2020/01/20180905_1971270886435744_8835917058488139776_n.jpg?resize=1024%2C1024&ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2020/01/20180905_1971270886435744_8835917058488139776_n.jpg?resize=150%2C150&ssl=1 150w, https://i1.wp.com/wordpress.org/news/files/2020/01/20180905_1971270886435744_8835917058488139776_n.jpg?resize=768%2C768&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" /></figure>\n\n\n\n<h3><strong>The WordPress community from Robert’s perspective</strong></h3>\n\n\n\n<p>Robert doesn’t have a lot of interaction with the WordPress community. Although he would search for solutions from blogs about WordPress he had never actually talked to or asked anyone from the community for a solution. </p>\n\n\n\n<p>Robert believes that this isolation is the result of a glass ceiling — the WordPress community is partially online and partially in-person, but there isn’t a local group in Malawi. And because Malawi, like many other developing nations, lacks a way to pay online many can’t access premium support, online learning, or most other types of professional development. No matter how welcoming the people of WordPress might be, it can still feel like it mostly belongs to those with enough privilege to conduct business on the internet.</p>\n\n\n\n<h3><strong>WordPress & inclusion</strong></h3>\n\n\n\n<p>As most freelancers know, it’s really hard to learn while you also still need to earn. Add pitching to clients and shipping graphic design projects… there are only so many hours in a day.</p>\n\n\n\n<p>Robert didn’t have a programming background and had always been more of a creative person. In order to grow as a web designer/developer, he needed to learn PHP. Again, without access to a credit card, that was complicated. Also, free coding training wasn’t as widely available as it is now.</p>\n\n\n\n<p>Robert wishes that more developers would consider alternative ways for users who cannot pay for courses, themes, or plugins (whether that’s because of available infrastructure or otherwise). He wishes that WordPress tutors and developers would open up ways to accommodate aspiring learners in developing countries who cannot access plugins, courses, and themes, to be able to give back and to participate at another level.</p>\n\n\n\n<p>WordPress has allowed him to build an income he would have no other way of earning and it makes a huge difference. He believes sharing stories like his will hopefully make WordPress products and services become more universally available. In addition, he hopes that more aspiring, self-taught developers will find courage in reaching out to connect with others out there.</p>\n\n\n\n<h2><strong>Contributors</strong></h2>\n\n\n\n<p><NAME> (<a href=\'https://profiles.wordpress.org/wpfiddlybits/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>wpfiddlybits</a>), <NAME> (<a href=\'https://profiles.wordpress.org/yvettesonneveld/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>yvettesonneveld</a>), <NAME> (<a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a>), <NAME> (<a href=\'https://profiles.wordpress.org/siobhanseija/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>siobhanseija</a>), <NAME> (<a href=\'https://profiles.wordpress.org/topher1kenobe/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>topher1kenobe</a>)</p>\n\n\n\n<div class=\"wp-block-columns\">\n<div class=\"wp-block-column\" style=\"flex-basis:33.33%\">\n<figure class=\"wp-block-image size-large\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2019/07/heropress_large_white_logo.jpg?resize=632%2C474&ssl=1\" alt=\"\" class=\"wp-image-7025\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2019/07/heropress_large_white_logo.jpg?w=1024&ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2019/07/heropress_large_white_logo.jpg?resize=300%2C225&ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2019/07/heropress_large_white_logo.jpg?resize=768%2C576&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n</div>\n\n\n\n<div class=\"wp-block-column\" style=\"flex-basis:66.66%\">\n<p> <em>This post is based on an article originally published on HeroPress.com, a community initiative created by <a href=\"https://profiles.wordpress.org/topher1kenobe/\"><NAME></a>. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.</em> </p>\n</div>\n</div>\n\n\n\n<p> <em>Meet more WordPress community members over at </em><a href=\"https://heropress.com/\"><em>HeroPress.com</em></a><em>!</em> </p>\n\n\n\n<p><br></p>\n\";s: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:\"8300\";s: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:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"WordPress Leaders Nominated for CMX Awards\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpress.org/news/2020/01/wordpress-leaders-nominated-for-cmx-awards/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Jan 2020 21:42: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:8:\"category\";a:2:{i:0;a:5:{s:4:\"data\";s:6:\"Awards\";s: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:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8288\";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:366:\"Two members of the WordPress leadership team were nominated for excellent work in their field in the first ever Community Industry Awards. <NAME> is nominated for Executive Leader of a Community Team and <NAME> is nominated for Community Professional of the Year. CMX is one of the largest professional organizations dedicated 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:16:\"<NAME>\";s: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:4014:\"\n<p>Two members of the WordPress leadership team were nominated for excellent work in their field in the first ever Community Industry Awards. <a href=\"https://profiles.wordpress.org/andreamiddleton/\"><NAME></a> is nominated for <a href=\"https://cmxhub.com/awards-executive\">Executive Leader of a Community Team</a> and <a href=\"https://profiles.wordpress.org/chanthaboune/\"><NAME></a> is nominated for <a href=\"https://cmxhub.com/awards-professional\">Community Professional of the Year</a>.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?fit=632%2C281&ssl=1\" alt=\"\" class=\"wp-image-8292\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?w=2412&ssl=1 2412w, https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?resize=300%2C133&ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?resize=1024%2C455&ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?resize=768%2C341&ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?resize=1536%2C683&ssl=1 1536w, https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?resize=2048%2C910&ssl=1 2048w, https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?w=1264&ssl=1 1264w, https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?w=1896&ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" /></figure>\n\n\n\n<p><a href=\"https://cmxhub.com/\">CMX</a> is one of the largest professional organizations dedicated to community builders. The awards were open to public nomination, and finalists were chosen by panels of their peers in the CMX community.</p>\n\n\n\n<p>Andrea has been a vital community strategist for the WordPress project since 2011. Her work to build and support a vibrant community has played a part in the success around the popular open source CMS. Her work is sponsored by Automattic, where she leads a team that focuses on educational efforts, funding, and in-person community-driven events that serve a global base.</p>\n\n\n\n<p>Josepha has been the Executive Director of the WordPress project since 2019. Her work to coordinate and guide volunteer efforts spans 20 teams and involves thousands of volunteers. Her work is also sponsored by Automattic, where she leads the open source division that focuses on all aspects of open source contribution including design, development, volunteer engagement, and the health of the overall WordPress ecosystem.</p>\n\n\n\n<h2>Votes are Open</h2>\n\n\n\n<p>Final recipients are chosen with open voting — if you feel like either Andrea or Josepha have had an impact on your careers, your trajectory in the WordPress project, or the health of WordPress as a whole, there are three ways you can show your support:</p>\n\n\n\n<ul><li>Stop by and vote for them (Andrea <a href=\"https://href.li/?https://cmxhub.com/awards-executive\">here</a>, Josepha <a href=\"https://href.li/?https://cmxhub.com/awards-professional\">here</a>)!</li><li>Share this post with your own communities!</li><li>Tweet some inspirational thoughts about your time/experience/learnings with WordPress (using #WordPress, naturally)!</li></ul>\n\n\n\n<h2>Thank You Notes</h2>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>A lot of care and passion goes into making the WordPress Project as fantastic as it is. I think these awards are a reflection of how wonderful the community and ecosystem are, and I appreciate everyone’s continued trust in my stewardship!</p><cite><NAME></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>WordPress community organizers are some of the most generous and creative people in the world — working with them is exciting and interesting every day. I’m humbled by this nomination; thank you!</p><cite><NAME></cite></blockquote>\n\";s: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:\"8288\";s: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:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"The Month in WordPress: December 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2020/01/the-month-in-wordpress-december-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 03 Jan 2020 17:05: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8282\";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:353:\"As 2019 draws to a close and we look ahead to another exciting year let’s take a moment to review what the WordPress community achieved in December. WordPress 5.3.1 and 5.3.2 Releases The WordPress 5.3.1 security and maintenance release was announced on December 13. It features 46 fixes and enhancements. This version corrects four 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"<NAME>\";s: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:8186:\"\n<p>As 2019 draws to a close and we look ahead to another exciting year let’s take a moment to review what the WordPress community achieved in December.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.3.1 and 5.3.2 Releases</h2>\n\n\n\n<p>The WordPress 5.3.1 security and maintenance release was announced on December 13. It features 46 fixes and enhancements. This version corrects four security issues in WordPress versions 5.3 and earlier. Shortly afterwards, WordPress 5.3.2 was released, addressing a couple high severity Trac tickets, and includes 5 fixes and enhancements, so you’ll want to upgrade. You can read more about these releases in the announcements for <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\">5.3.1</a> and <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-2-maintenance-release/\">5.3.2</a>.</p>\n\n\n\n<h2>Update on the Nine Core Projects for 2019</h2>\n\n\n\n<p>At the end of 2018, <a href=\'https://profiles.wordpress.org/matt/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>matt</a> <a href=\"https://make.wordpress.org/core/2018/12/08/9-priorities-for-2019/\">announced</a> the nine projects that would be the main focus areas for Core development in the next year. Have we made progress? Yes! <a href=\'https://profiles.wordpress.org/chanthaboune/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>chanthaboune</a> <a href=\"https://make.wordpress.org/core/2019/12/06/update-9-projects-for-2019/\">posted a full update</a> on the team’s work. In brief, two of the projects have been completed and shipped in major releases, four are targeted for release in versions 5.4 and 5.5 of WordPress, and the remaining three have seen significant progress but are not yet slated for completion. These will continue to see progress throughout 2020.</p>\n\n\n\n<p>Want to get involved in building WordPress Core? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>WordPress Major Release Calendar</h2>\n\n\n\n<p>The Core team has published <a href=\"https://make.wordpress.org/core/2019/11/21/tentative-release-calendar-2020-2021/\">a tentative release calendar</a> for 2020 and 2021. This is intended to provide the community with more information about what lies ahead.</p>\n\n\n\n<p>The schedule is considered tentative because there are always variables that could affect these plans — not least that the Core team may need more time to finish the work planned for a release.</p>\n\n\n\n<h2>Initial Documentation for Block-Based WordPress Themes</h2>\n\n\n\n<p>The Gutenberg team has started working on <a href=\"https://github.com/WordPress/gutenberg/pull/18890/files\">the initial documentation</a> for what block-based themes might look like, marking a significant change in the way themes are conceptualized. With full-site editing now a realistic goal for WordPress, themes will certainly look different in the future.</p>\n\n\n\n<p>Want to help shape the future of block-based themes in WordPress Core? Following <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> is a good start! You can also join in on the discussion <a href=\"https://make.wordpress.org/themes/2019/12/04/questions-about-the-future-of-themes/\">on this blog post</a>, or help out with the work to <a href=\"https://github.com/WordPress/gutenberg/blob/master/lib/demo-block-templates/index.html\">create a demo space for experimentation with the future of themes</a>. As always, contribution to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a> is open to everyone! Join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a> to see what other people are saying, and contribute your own thoughts.</p>\n\n\n\n<h2>Gutenberg Updates Abound</h2>\n\n\n\n<p>It’s been a busy month for Gutenberg! Version 7.0, including a new navigation block, <a href=\"https://make.wordpress.org/core/2019/11/27/whats-new-in-gutenberg-27-november/\">was announced</a> on November 27. This was followed by <a href=\"https://make.wordpress.org/core/2019/12/11/whats-new-in-gutenberg-11-december/\">version 7.1</a>, announced on December 11; it includes 161 merged pull requests that offer a fresh UI to new users, an option to switch between edit and navigation modes, captions for the table block, and many other enhancements.</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Arrival of the BuddyPress Beta Tester Plugin</h2>\n\n\n\n<p>On December 2, <a href=\"https://buddypress.org/2019/12/bp-beta-tester-1-0-0/\">the BuddyPress Beta Tester plugin</a> was added to the WordPress.org plugins directory. This feature is a great way for the WordPress community to provide early feedback on releases.</p>\n\n\n\n<p>You can <a href=\"https://wordpress.org/plugins/bp-beta-tester/\">download the plugin</a> now. If you find that something is not working as expected during your beta tests, let the BuddyPress team know by submitting a ticket on the <a href=\"https://buddypress.trac.wordpress.org/newticket\">Development Tracker</a> or posting a new topic in the BuddyPress <a href=\"https://buddypress.org/support/\">support forums</a>.</p>\n\n\n\n<h2>An Update on the Block Directory in the WordPress Editor </h2>\n\n\n\n<p>The Design team received lots of excellent feedback on the <a href=\"https://make.wordpress.org/design/2019/07/11/block-directory-in-wp-admin-concepts/\">early concepts for the Block Directory</a>. This feedback was incorporated into a Version 1 update to the <a href=\"https://make.wordpress.org/design/tag/block-directory/\">#block-directory</a> project. The Block Directory is to be included in WordPress 5.5, which is slated for August 2020. To learn more about the Block Directory, check out <a href=\"https://make.wordpress.org/design/2019/12/19/block-directory-in-wp-admin-v1/\">this announcement post</a> and help out by sharing your feedback. </p>\n\n\n\n<p>Want to get involved in building the Block Directory? Follow <a href=\"https://make.wordpress.org/design/\">the Design team blog</a>. If you have a block you’d like to include in the directory you can <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">submit it following the information here</a>. </p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">Guidelines for the Block Directory</a> have been drafted; the team is actively working on them now.</li><li>The<a href=\"https://make.wordpress.org/community/2020-wordpress-global-community-sponsorship-program/\"> Global Community Sponsorship Program for 2020</a> has been announced. </li><li>The Theme Review Team <a href=\"https://make.wordpress.org/themes/2019/12/09/do-not-contact-reviewers-outside-of-the-wordpress-org-system-about-your-review/\">has published a reminder</a> for developers about the proper way to communicate with reviewers.</li><li>The Community Team is in the process of <a href=\"https://make.wordpress.org/community/2019/12/05/community-team-reps-for-2020/\">selecting new team reps</a>.</li><li><a href=\"https://meetup.com/pro/wordpress\">The WordPress meetup program</a> crossed the 800-group mark this month and includes groups from more than 100 countries.</li><li>The team that helped to create the 2019 State of the Word slide deck <a href=\"https://wordpress.org/news/2019/12/state-of-the-word-the-story-of-the-slides/\">shared how the slides were created using Gutenberg</a>, powered by the Slides plugin. </li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\n\";s: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:\"8282\";s: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:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:35:\"WordPress 5.3.2 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2019/12/wordpress-5-3-2-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 18 Dec 2019 22:42:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s: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=8275\";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:391:\"WordPress 5.3.2 is now available! This maintenance release features 5 fixes and enhancements. WordPress 5.3.2 is a short-cycle maintenance release. The next major release will be version 5.4. You can download WordPress 5.3.2 by clicking the button at the top of this page, or visit your Dashboard → Updates and click Update Now. If you have sites that support […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"Jb Audras\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:2874:\"\n<p>WordPress 5.3.2 is now available!</p>\n\n\n\n<p>This maintenance release features 5 fixes and enhancements.</p>\n\n\n\n<p>WordPress 5.3.2 is a short-cycle maintenance release. The next major release will be version 5.4.</p>\n\n\n\n<p>You can download WordPress 5.3.2 by clicking the button at the top of this page, or visit your<strong> Dashboard → Updates</strong> and click <strong>Update Now</strong>.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h2>Maintenance updates</h2>\n\n\n\n<p>Shortly after <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\">WordPress 5.3.1 was released</a>, a couple of high severity Trac tickets were opened. The Core team scheduled this quick maintenance release to resolve these issues.</p>\n\n\n\n<p>Main issues addressed in 5.3.2:</p>\n\n\n\n<ul><li>Date/Time: Ensure that <code>get_feed_build_date()</code> correctly handles a modified post object with invalid date.</li><li>Uploads: Fix file name collision in <code>wp_unique_filename()</code> when uploading a file with upper case extension on non case-sensitive file systems.</li><li>Media: Fix PHP warnings in <code>wp_unique_filename()</code> when the destination directory is unreadable.</li><li>Administration: Fix the colors in all color schemes for buttons with the <code>.active</code> class.</li><li>Posts, Post Types: In <code>wp_insert_post()</code>, when checking the post date to set <code>future</code> or <code>publish</code> status, use a proper delta comparison.</li></ul>\n\n\n\n<p>For more information, <a href=\"https://core.trac.wordpress.org/query?status=closed&type=!task+(blessed)&resolution=fixed&milestone=5.3.2&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority\">browse the full list of changes on Trac</a> or check out the <a href=\"https://wordpress.org/support/wordpress-version/version-5-3-2/\">version 5.3.2 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks!</h2>\n\n\n\n<p>Thank you to everyone who contributed to WordPress 5.3.2:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/azaozz/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey “Rarst” Savchenko</a>, <a href=\"https://profiles.wordpress.org/dd32/\">Dion hulse</a>, <a href=\"https://profiles.wordpress.org/eden159/\">eden159</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/ryelle/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/pbiron/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</a>.</p>\n\";s: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:\"8275\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:5;a:6:{s:4:\"data\";s:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:42:\"State of the Word: the story of the 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:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:77:\"https://wordpress.org/news/2019/12/state-of-the-word-the-story-of-the-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:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 17 Dec 2019 19:27: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"General\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=8233\";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:142:\"Curious about the Gutenberg powered slides used during State of the Word? This post uncovers some technical and design aspects of the 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:11767:\"\n<p>During the State of the Word at WordCamp US 2019, <NAME> shared that Gutenberg was used to create his slides and the presentation was powered by the Slides plugin. Using WordPress to power a slide deck isn’t an obvious choice, so we wanted to showcase the process and give some tips for making slide layouts using Gutenberg.</p>\n\n\n\n<p><em>This post is co-written by Ella and <a href=\"https://profiles.wordpress.org/karmatosed/\">Tammie</a>, who (along with <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel</a>, <a href=\"https://profiles.wordpress.org/mapk/\">Mark</a>, <a href=\"https://profiles.wordpress.org/nrqsnchz/\">Enrique</a>, <a href=\"https://profiles.wordpress.org/itsjonq/\">Q</a></em> <em>and a cast of supporters) helped create this year’s State of the Word slide deck.</em></p>\n\n\n\n<h2>How it Started</h2>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/ellatrix/\"><NAME></a> was selected to speak at <a href=\"https://www.youtube.com/watch?v=ZNWNhUPrqB4\">JSConf</a> and ReactEurope and wanted slides for her presentation. </p>\n\n\n\n<p>In the past, she’d used Reveal.js to create slides and enjoyed the freedom to create anything using HTML, CSS and JavaScript. These languages were comfortable, familiar, and also can be published on the web in their native format. </p>\n\n\n\n<p>For these new presentations, she wanted to use Reveal.js again but didn’t feel like writing all the HTML by hand. Creating blocks of content visually, without having to actually write any code, which can be published natively to the web, is exactly what Gutenberg was built for.</p>\n\n\n\n<p>The plugin was prototyped quickly, with hardcoded styles on the slides and zero options. At the end of each presentation, Ella shared a brief demo of the Gutenberg-based slides and the audience was amazed.</p>\n\n\n\n<figure class=\"wp-block-embed-twitter wp-block-embed is-type-rich is-provider-twitter\"><div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\"><p lang=\"en\" dir=\"ltr\">.<a href=\"https://twitter.com/ellatrx?ref_src=twsrc%5Etfw\">@ellatrx</a> any chance you might open source this? <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /> <a href=\"https://t.co/6hygMpBqUA\">https://t.co/6hygMpBqUA</a></p>— <NAME> (@swissspidy) <a href=\"https://twitter.com/swissspidy/status/1131573525612048385?ref_src=twsrc%5Etfw\">May 23, 2019</a></blockquote><script async src=\"https://platform.twitter.com/widgets.js\" charset=\"utf-8\"></script>\n</div></figure>\n\n\n\n<p>As WordCamp US approached, Ella suggested that her plugin be used for State of the Word. Since it was such a hit with her audience members, it seemed like this would be a great chance to share it with the WordPress community as a whole.</p>\n\n\n\n<span id=\"more-8233\"></span>\n\n\n\n<h2>How it Works</h2>\n\n\n\n<h3>Technical information</h3>\n\n\n\n<p>The plugin registers a custom post type called “presentation” and a new “slide” block. The slide block is a sort of enhanced “Group” block, which is restricted to the root of the post, but you can put any other block inside it. As a result, you have a post filled with only slides at the root and slides filled with content. This maps perfectly to the Reveal.js markup, which requires content in HTML section elements.</p>\n\n\n\n<p>Since these slides each have their own design, the theme styles are disabled and styling is set from each slide. A custom presentation template is provided by the plugin to render the custom post on the front-end.</p>\n\n\n\n<p>Then Ella added options to style the slides. For example, she added options to control the slide background and font, at both the document level and individual slide level. She also added Reveal.js options, which allow you to change the transition style and speed. Lastly, she added a custom CSS field to allow style overwrites.</p>\n\n\n\n<p>For the State of the Word, she also added speaker notes and a speaker view.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/image.png?fit=632%2C363&ssl=1\" alt=\"\" class=\"wp-image-8271\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2019/12/image.png?w=1256&ssl=1 1256w, https://i0.wp.com/wordpress.org/news/files/2019/12/image.png?resize=300%2C172&ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2019/12/image.png?resize=1024%2C588&ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2019/12/image.png?resize=768%2C441&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" /></figure>\n\n\n\n<h3>How it’s Designed</h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/01.png?fit=632%2C515&ssl=1\" alt=\"\" class=\"wp-image-8262\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2019/12/01.png?w=1114&ssl=1 1114w, https://i0.wp.com/wordpress.org/news/files/2019/12/01.png?resize=300%2C245&ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2019/12/01.png?resize=1024%2C835&ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2019/12/01.png?resize=768%2C626&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" /></figure>\n\n\n\n<p>The inspiration for the slide designs came from Blue Note album covers (which were also the inspiration for the <a href=\"https://www.slideshare.net/photomatt/state-of-the-word-2011/\">2011 State of the Word slides</a>). These album covers inspired the recent “About” page in WordPress core and the starter content for the new Twenty Twenty theme. This style consists of strong, geometric shapes and simple forms with clean lines. Photography and bold typography are at the heart of this look.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?fit=632%2C541&ssl=1\" alt=\"\" class=\"wp-image-8267\" srcset=\"https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?w=3586&ssl=1 3586w, https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?resize=300%2C257&ssl=1 300w, https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?resize=1024%2C877&ssl=1 1024w, https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?resize=768%2C658&ssl=1 768w, https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?resize=1536%2C1316&ssl=1 1536w, https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?resize=2048%2C1754&ssl=1 2048w, https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?w=1264&ssl=1 1264w, https://i1.wp.com/wordpress.org/news/files/2019/12/image-17.png?w=1896&ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" /></figure>\n\n\n\n<p>Various color palettes and font pairings were explored before selecting the best combination for the presentation.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/03.png?fit=632%2C407&ssl=1\" alt=\"\" class=\"wp-image-8259\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2019/12/03.png?w=1311&ssl=1 1311w, https://i0.wp.com/wordpress.org/news/files/2019/12/03.png?resize=300%2C193&ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2019/12/03.png?resize=1024%2C660&ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2019/12/03.png?resize=768%2C495&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" /></figure>\n\n\n\n<p>A strong photographic element was needed for the slides. Past WordCamps are a great source of photos, so we dug through years of photo galleries to find just the right shots. With colors, fonts, and photos, we laid the foundation to build the deck.</p>\n\n\n\n<h2>Tips for Making Gutenberg Slides</h2>\n\n\n\n<h3>Tip One: columns are your friends</h3>\n\n\n\n<p>If you want slides with a precise layout, use columns. As you can see here, we used a 3 column layout to center content within a slide:</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/3.png?w=632&ssl=1\" alt=\"\" class=\"wp-image-8260\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2019/12/3.png?w=874&ssl=1 874w, https://i0.wp.com/wordpress.org/news/files/2019/12/3.png?resize=300%2C168&ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2019/12/3.png?resize=768%2C431&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h3>Tip Two: spacer blocks are useful</h3>\n\n\n\n<p>Want to really unlock the power of columns? Combine them with the spacer block! We used spacer blocks to position content over background images, like in this slide:</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2019/12/6.png?w=632&ssl=1\" alt=\"\" class=\"wp-image-8264\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2019/12/6.png?w=865&ssl=1 865w, https://i2.wp.com/wordpress.org/news/files/2019/12/6.png?resize=300%2C171&ssl=1 300w, https://i2.wp.com/wordpress.org/news/files/2019/12/6.png?resize=768%2C438&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" data-recalc-dims=\"1\" /></figure>\n\n\n\n<h3>Tip Three: test on large screens</h3>\n\n\n\n<p>It’s important to preview and test your slides as you go. Make sure to design for the size and aspect ratio of the projector you’ll be using and do a visual check in presentation mode from time to time.</p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/notes.png?fit=632%2C405&ssl=1\" alt=\"\" class=\"wp-image-8269\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2019/12/notes.png?w=1096&ssl=1 1096w, https://i0.wp.com/wordpress.org/news/files/2019/12/notes.png?resize=300%2C192&ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2019/12/notes.png?resize=1024%2C657&ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2019/12/notes.png?resize=768%2C493&ssl=1 768w\" sizes=\"(max-width: 632px) 100vw, 632px\" /></figure>\n\n\n\n<h3>Tip Four: check your videos</h3>\n\n\n\n<p>A good demo video is integral to showcase new features. <NAME> has a great post on <a href=\"https://automattic.design/2019/11/12/good-ui-demo-videos/\">creating effective demo videos</a>.</p>\n\n\n\n<h2>Lessons learned</h2>\n\n\n\n<blockquote class=\"wp-block-quote\"><p><em>I’d love to make the art directed compositions easier to create. </em></p><cite><em><NAME></em></cite></blockquote>\n\n\n\n<p>As Gutenberg evolves, one big improvement is that art direction will get easier. Even with the improvements this year, creating some layouts in Gutenberg was trickier than expected. For the more complicated compositions, we relied on SVGs. Eventually, the need for hacks will dissolve away, and a new world of exciting possibilities will open for everyone.</p>\n\n\n\n<p>Browsers offered one of our biggest learnings in this presentation, more than they would if you use Keynote or Powerpoint, for example (tools most of us have used). Often, we found that what we created in the editor varied a when viewed full-screen. We were able to mitigate this by updating the plugin to use a fixed size, instead of using the entire browser window.</p>\n\n\n\n<h2>Wrapping it up</h2>\n\n\n\n<p>If you would like to check out the State of the Word, you can watch the <a href=\"https://wordpress.tv/2019/11/03/2019-state-of-the-word/\">video</a> and read all about it in a <a href=\"https://ma.tt/2019/11/state-of-the-word-2019/\">post</a>.</p>\n\n\n\n<p>The Slides plugin is not only available on the plugin repo, but you can also get the code from <a href=\"https://github.com/WordPress/slides\">GitHub</a> and <a href=\"https://translate.wordpress.org/projects/wp-plugins/slide/\">help translate</a>.</p>\n\";s: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:\"8233\";s: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:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"WordPress 5.3.1 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/2019/12/wordpress-5-3-1-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:\"Fri, 13 Dec 2019 00:07:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"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:34:\"https://wordpress.org/news/?p=8203\";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:360:\"WordPress 5.3.1 is now available! This security and maintenance release features 46 fixes and enhancements. Plus, it adds a number of security fixes—see the list below. WordPress 5.3.1 is a short-cycle maintenance release. The next major release will be version 5.4. You can download WordPress 5.3.1 by clicking the button at the top of this 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:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"Jb Audras\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:12709:\"\n<p>WordPress 5.3.1 is now available!</p>\n\n\n\n<p>This security and maintenance release features 46 fixes and enhancements. Plus, it adds a number of security fixes—see the list below.</p>\n\n\n\n<p>WordPress 5.3.1 is a short-cycle maintenance release. The next major release will be version 5.4.</p>\n\n\n\n<p>You can download WordPress 5.3.1 by clicking the button at the top of this page, or visit your<strong> Dashboard → Updates</strong> and click <strong>Update Now</strong>.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h2>Security updates</h2>\n\n\n\n<p>Four security issues affect WordPress versions 5.3 and earlier; version 5.3.1 fixes them, so you’ll want to upgrade. If you haven’t yet updated to 5.3, there are also updated versions of 5.2 and earlier that fix the security issues.</p>\n\n\n\n<ul><li>Props to <a href=\"https://danielbachhuber.com/\"><NAME></a> for finding an issue where an unprivileged user could make a post sticky via the REST API.</li><li>Props to <a href=\"https://blog.ripstech.com/authors/simon-scannell\"><NAME> of RIPS Technologies</a> for finding and disclosing an issue where cross-site scripting (XSS) could be stored in well-crafted links.</li><li>Props to the <a rel=\"noreferrer noopener\" target=\"_blank\" href=\"https://wordpress.org/\">WordPress.org</a> Security Team for hardening <code>wp_kses_bad_protocol()</code> to ensure that it is aware of the named colon attribute.</li><li>Props to <a href=\"https://twitter.com/ducnt_\">Nguyen The Duc</a> for discovering a stored XSS vulnerability using block editor content.</li></ul>\n\n\n\n<h2>Maintenance updates</h2>\n\n\n\n<p>Here are a few of the highlights:</p>\n\n\n\n<ul><li>Administration: improvements to admin form controls height and alignment standardization (see related <a href=\"https://make.wordpress.org/core/2019/12/11/admin-form-controls-height-and-alignment-standardization-in-wordpress-5-3-1/\">dev note</a>), dashboard widget links accessibility and alternate color scheme readability issues (see related <a href=\"https://make.wordpress.org/core/2019/12/10/alternate-color-schemes-changes-in-wordpress-5-3-1/\">dev note</a>).</li><li>Block editor: fix Edge scrolling issues and intermittent JavaScript issues.</li><li>Bundled themes: add customizer option to show/hide author bio, replace JS based smooth scroll with CSS (see related <a href=\"https://make.wordpress.org/core/2019/12/08/twenty-twenty-animated-scroll-changes-in-wordpress-5-3-1/\">dev note</a>) and fix Instagram embed CSS.</li><li>Date/time: improve non-GMT dates calculation, fix date format output in specific languages and make <code>get_permalink()</code> more resilient against PHP timezone changes.</li><li>Embeds: remove CollegeHumor oEmbed provider as the service doesn’t exist anymore.</li><li>External libraries: update <code>sodium_compat</code>.</li><li>Site health: allow the remind interval for the admin email verification to be filtered.</li><li>Uploads: avoid thumbnails overwriting other uploads when filename matches, and exclude PNG images from scaling after upload.</li><li>Users: ensure administration email verification uses the user’s locale instead of the site locale.</li></ul>\n\n\n\n<p>For more information, <a href=\"https://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=5.3.1&order=priority\">browse the full list of changes on Trac</a> or check out the <a href=\"https://wordpress.org/support/wordpress-version/version-5-3-1/\">version 5.3.1 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks!</h2>\n\n\n\n<p>In addition to the security researchers mentioned above, thank you to everyone who contributed to WordPress 5.3.1:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/123host/\">123host</a>, <a href=\"https://profiles.wordpress.org/acosmin/\">acosmin</a>, <a href=\"https://profiles.wordpress.org/adamsilverstein/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/aljullu/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/xknown/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/viper007bond/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/anantajitjg/\">Anantajit JG</a>, <a href=\"https://profiles.wordpress.org/anlino/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/andraganescu/\">andraganescu</a>, <a href=\"https://profiles.wordpress.org/afercia/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/aduth/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/azaozz/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey “Rarst” Savchenko</a>, <a href=\"https://profiles.wordpress.org/aravindajith/\">aravindajith</a>, <a href=\"https://profiles.wordpress.org/archon810/\">archon810</a>, <a href=\"https://profiles.wordpress.org/ate-up-with-motor/\">Ate Up With Motor</a>, <a href=\"https://profiles.wordpress.org/ayeshrajans/\"><NAME>unaratne</a>, <a href=\"https://profiles.wordpress.org/birgire/\"><NAME>sson (birgire)</a>, <a href=\"https://profiles.wordpress.org/boga86/\">Boga86</a>, <a href=\"https://profiles.wordpress.org/boonebgorges/\">Boone Gorges</a>, <a href=\"https://profiles.wordpress.org/poena/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/chetan200891/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/littlebigthing/\">Csaba (LittleBigThings)</a>, <a href=\"https://profiles.wordpress.org/xendo/\">Dademaru</a>, <a href=\"https://profiles.wordpress.org/danielbachhuber/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/mte90/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/talldanwp/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/davidbaumwald/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/dlh/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/dd32/\">Dion hulse</a>, <a href=\"https://profiles.wordpress.org/ehtis/\">ehtis</a>, <a href=\"https://profiles.wordpress.org/ellatrix/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/epiqueras/\">epiqueras</a>, <a href=\"https://profiles.wordpress.org/fabifott/\">Fabian</a>, <a href=\"https://profiles.wordpress.org/flixos90/\"><NAME>ntz</a>, <a href=\"https://profiles.wordpress.org/flaviozavan/\">flaviozavan</a>, <a href=\"https://profiles.wordpress.org/garrett-eclipse/\">Garrett Hyder</a>, <a href=\"https://profiles.wordpress.org/hometowntrailers/\">Glenn</a>, <a href=\"https://profiles.wordpress.org/gziolo/\">Grzegorz (<NAME></a>, <a href=\"https://profiles.wordpress.org/grzegorzjanoszka/\">Grzegorz.Janoszka</a>, <a href=\"https://profiles.wordpress.org/hareesh-pillai/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/ianbelanger/\">Ian Belanger</a>, <a href=\"https://profiles.wordpress.org/ispreview/\">ispreview</a>, <a href=\"https://profiles.wordpress.org/whyisjake/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/macmanx/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/jameskoster/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/jarretc/\">Jarret</a>, <a href=\"https://profiles.wordpress.org/studiotwee/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/audrasjb/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/jeichorn/\">jeichorn</a>, <a href=\"https://profiles.wordpress.org/jeremyclarke/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/jeremyfelt/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/jipmoors/\">Jip Moors</a>, <a href=\"https://profiles.wordpress.org/joehoyle/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/johnjamesjacoby/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/desrosj/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/spacedmonkey/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/joostdevalk/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/jorgefilipecosta/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/joyously/\">Joy</a>, <a href=\"https://profiles.wordpress.org/jrf/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/justdaiv/\">justdaiv</a>, <a href=\"https://profiles.wordpress.org/ryelle/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/kharisblank/\">Kharis Sulistiyono</a>, <a href=\"https://profiles.wordpress.org/ixkaito/\">Kite</a>, <a href=\"https://profiles.wordpress.org/kyliesabra/\">kyliesabra</a>, <a href=\"https://profiles.wordpress.org/lisota/\">lisota</a>, <a href=\"https://profiles.wordpress.org/lukaswaudentio/\">lukaswaudentio</a>, <a href=\"https://profiles.wordpress.org/maciejmackowiak/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/marcelo2605/\">marcelo2605</a>, <a href=\"https://profiles.wordpress.org/clorith/\"><NAME>.</a>, <a href=\"https://profiles.wordpress.org/mat-lipe/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/mayanksonawat/\">mayanksonawat</a>, <a href=\"https://profiles.wordpress.org/melchoyce/\">Mel Choyce-Dwan</a>, <a href=\"https://profiles.wordpress.org/michael-arestad/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/miette49/\">miette49</a>, <a href=\"https://profiles.wordpress.org/mcsf/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/mihdan/\">mihdan</a>, <a href=\"https://profiles.wordpress.org/mauteri/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/msaari/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/gdragon/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/mukesh27/\">Mukesh Panchal</a>, <a href=\"https://profiles.wordpress.org/nextscripts/\">NextScripts</a>, <a href=\"https://profiles.wordpress.org/nickdaugherty/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/nielslange/\">Niels Lange</a>, <a href=\"https://profiles.wordpress.org/noyle/\">noyle</a>, <a href=\"https://profiles.wordpress.org/ov3rfly/\">Ov3rfly</a>, <a href=\"https://profiles.wordpress.org/paragoninitiativeenterprises/\">Paragon Initiative Enterprises</a>, <a href=\"https://profiles.wordpress.org/pbiron/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/peterwilsoncc/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/larrach/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/youknowriad/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/quicoto/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/murgroland/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/rmccue/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/welcher/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/samuelfernandez/\">SamuelFernandez</a>, <a href=\"https://profiles.wordpress.org/sathyapulse/\">sathyapulse</a>, <a href=\"https://profiles.wordpress.org/wonderboymusic/\"><NAME>aylor</a>, <a href=\"https://profiles.wordpress.org/scvleon/\">scvleon</a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/sergiomdgomes/\">sergiomdgomes</a>, <a href=\"https://profiles.wordpress.org/sgr33n/\">SGr33n</a>, <a href=\"https://profiles.wordpress.org/simonjanin/\">simonjanin</a>, <a href=\"https://profiles.wordpress.org/smerriman/\">smerriman</a>, <a href=\"https://profiles.wordpress.org/steevithak/\">steevithak</a>, <a href=\"https://profiles.wordpress.org/sabernhardt/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/netweb/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/dufresnesteven/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/subratamal/\">Subrata Mal</a>, <a href=\"https://profiles.wordpress.org/manikmist09/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/cybr/\">Sybre Waaijer</a>, <a href=\"https://profiles.wordpress.org/karmatosed/\">Tammie Lister</a>, <a href=\"https://profiles.wordpress.org/tanvirul/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</a>, <a href=\"https://profiles.wordpress.org/timon33/\">timon33</a>, <a href=\"https://profiles.wordpress.org/timothyblynjacobs/\">Timothy Jacobs</a>, <a href=\"https://profiles.wordpress.org/spaceshipone/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/tmatsuur/\">tmatsuur</a>, <a href=\"https://profiles.wordpress.org/dinhtungdu/\">Tung Du</a>, <a href=\"https://profiles.wordpress.org/veminom/\">Veminom</a>, <a href=\"https://profiles.wordpress.org/vortfu/\">vortfu</a>, <a href=\"https://profiles.wordpress.org/waleedt93/\">waleedt93</a>, <a href=\"https://profiles.wordpress.org/williampatton/\">williampatton</a>, <a href=\"https://profiles.wordpress.org/wpgurudev/\">wpgurudev</a>, and <a href=\"https://profiles.wordpress.org/tollmanz/\"><NAME></a>.</p>\n\";s: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:\"8203\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}i:7;a:6:{s:4:\"data\";s:63:\"\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"People of WordPress: <NAME>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:67:\"https://wordpress.org/news/2019/12/people-of-wordpress-jill-binder/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 06 Dec 2019 23:27:23 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:8:\"category\";a:3:{i:0;a:5:{s:4:\"data\";s:9:\"Community\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}i:1;a:5:{s:4:\"data\";s:9:\"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:\"\";}i:2;a:5:{s:4:\"data\";s:10:\"Interviews\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=8192\";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:\"You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories. Meet Jill Binder Jill Binder never meant to become an activist. She insists […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:7:\"Josepha\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:40:\"http://purl.org/rss/1.0/modules/content/\";a:1:{s:7:\"encoded\";a:1:{i:0;a:5:{s:4:\"data\";s:12123:\"\n<p><em>You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.</em></p>\n\n\n\n<h2><strong>Meet J<NAME></strong></h2>\n\n\n\n<p><NAME> never meant to become an activist. She insists it was an accident.</p>\n\n\n\n<p>Despite that, Jill has led the Diversity Outreach Speaker Training working group in the WordPress Community team since 2017. This group is dedicated to increasing the number of women and other underrepresented groups who are stepping up to become speakers at WordPress Meetups, WordCamps, and events. </p>\n\n\n\n<h2><strong>Jill’s back story</strong></h2>\n\n\n\n<h3><strong>Internship</strong></h3>\n\n\n\n<p>Jill’s WordPress story begins in 2011, in Vancouver, Canada. Jill secured an internship for her college program, working on a higher education website that was built in WordPress. As a thank you, her practicum advisor bought Jill a ticket to WordCamp Vancouver 2011: Developer’s Edition. After that Jill began freelancing with WordPress as a Solopreneur. </p>\n\n\n\n<h3><strong>First steps in the WordPress community</strong></h3>\n\n\n\n<p>The following year her internship advisor, who had become a client, was creating the first ever BuddyCamp for BuddyPress. He asked Jill to be on his organizing team. At that event she also moderated a panel that had <NAME> on it. Then, Jill was invited to be on the core organizing team for WordCamp Vancouver.</p>\n\n\n\n<p>Part of this role meant reviewing and selecting speakers. From 40 speaker applications that could be a fit the team had to pick only 14 to speak.</p>\n\n\n\n<h2><strong>The diversity challenge when selecting speakers</strong></h2>\n\n\n\n<p>For anyone who has organized a conference, you know that speaker selection is hard. Of the 40 applications, 7 were from women, and the lead organizer selected 6 of those to be included in the speaker line up.</p>\n\n\n\n<p>At this point Jill wasn’t aware that very few women apply to speak at tech conferences and suggested selection should be made on the best fit for the conference. The team shared that not only did they feel the pitches were good and fit the conference, but they also needed to be accepted or the Organizers would be criticized for a lack of diversity.</p>\n\n\n\n<p>Selecting women for fear of criticism is embarrassing to admit, but that’s how people felt in 2013.</p>\n\n\n\n<p>By the time the event happened, though, the number of women speakers dropped to 4. And with an additional track being added, the number of speakers overall was up to 28. Only 1 speaker in 7 was a woman (or 14%) and attendees did ask questions and even blogged about the lack of representation.</p>\n\n\n\n<h2><strong>What keeps women from applying?</strong></h2>\n\n\n\n<p>Later that year at WordCamp San Francisco—the biggest WordCamp at the time (before there was a WordCamp US)—Jill took the opportunity to chat with other organizers about her experience. She found out that many organizers had trouble getting enough women to present.</p>\n\n\n\n<p>Surprisingly Vancouver had a high number of women applicants in comparison to others, and the consensus was more would be accepted if only more would apply.</p>\n\n\n\n<p>Jill decided that she needed to know why this was happening? Why weren’t there more women applying? She started researching, reading, and talking to people.</p>\n\n\n\n<p>Though this issue is complex, two things came up over and over:</p>\n\n\n\n<ul><li>“What would I talk about?”</li><li>“I’m not an expert on anything. I don’t know enough about anything to give a talk on it.”</li></ul>\n\n\n\n<h2><strong>A first workshop with encouraging results</strong></h2>\n\n\n\n<p>Then Jill had an idea. She brought up the issue at an event and someone suggested that they should get women together in a room and brainstorm speaker topics.</p>\n\n\n\n<p>So Jill became the lead of a small group creating a workshop in Vancouver: the talented <NAME>, <NAME>, and <NAME>. In one of the exercises that they created, participants were invited to brainstorm ideas—this proved that they had literally a hundred topic ideas and the biggest problem then became picking just one!</p>\n\n\n\n<p>In the first workshop, they focussed on:</p>\n\n\n\n<ul><li>Why it matters that women (<em>added later: diverse groups</em>) are in the front of the room</li><li>The myths of what it takes to be the speaker at the front of the room (aka beating impostor syndrome)</li><li>Different presentation formats, especially story-telling</li><li>Finding and refining a topic</li><li>Tips to become a better speaker</li><li>Leveling up by speaking in front of the group throughout the afternoon</li></ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i2.wp.com/wordpress.org/news/files/2019/12/image-2.png?w=632&ssl=1\" alt=\"women gathering to discussion presentation topics\" class=\"wp-image-8195\" srcset=\"https://i2.wp.com/wordpress.org/news/files/2019/12/image-2.png?w=600&ssl=1 600w, https://i2.wp.com/wordpress.org/news/files/2019/12/image-2.png?resize=300%2C200&ssl=1 300w\" sizes=\"(max-width: 600px) 100vw, 600px\" data-recalc-dims=\"1\" /><figcaption>Vancouver Workshop 2014</figcaption></figure>\n\n\n\n<h2><strong>Leading to workshops across North America and then the world</strong></h2>\n\n\n\n<p>Other cities across North America heard about the workshop and started hosting them, adding their own material.</p>\n\n\n\n<p>Many women who initially joined her workshop wanted help getting even better at public speaking. So Jill’s Vancouver team added in some material created from the other cities and a bit more of their own. Such as:</p>\n\n\n\n<ul><li>Coming up with a great title</li><li>Writing a pitch that is more likely to get accepted</li><li>Writing a bio</li><li>Creating an outline</li></ul>\n\n\n\n<p>At WordCamp Vancouver 2014—only one year since Jill started—there were 50% women speakers and 3 times the number of women applicants! Not only that, but this WordCamp was a Developer’s Edition, where it’s more challenging to find women developers in general, let alone those who will step up to speak.</p>\n\n\n\n<h3><strong>More work is needed!</strong></h3>\n\n\n\n<p>Impressive as those results were, the reason Jill is so passionate about this work is because of what happened next:</p>\n\n\n\n<ul><li>Some of the women who attended the workshop stepped up to be leaders in the community and created new content for other women.</li><li>A handful of others became WordCamp organizers. One year Vancouver had an almost all-female organizing team – 5 out of 6!</li><li>It also influenced local businesses. One local business owner loved what one of the women speakers said so much that he hired her immediately. She was the first woman developer on the team, and soon after she became the Senior Developer.</li></ul>\n\n\n\n<h2><strong>Diversity touches on many levels</strong></h2>\n\n\n\n<p>Jill has seen time and again what happens when different people speak at the front of the room. More people feel welcome in the community. The speakers and the new community members bring new ideas and new passions that help to make the technology we are creating more inclusive. And together we generate new ideas that benefit everyone.</p>\n\n\n\n<p>This workshop was so successful, with typical results of going from 10% to 40-60% women speakers at WordCamps, that the WordPress Global Community Team asked Jill to promote it and train it for women and all diverse groups around the world. In late 2017, Jill started leading the Diverse Speaker Training group (<a href=\"https://make.wordpress.org/community/tag/wpdiversity/\">#wpdiversity</a>).</p>\n\n\n\n<p>Dozens of community members across the world have now been trained to lead the workshop. With now dozens of workshops worldwide, for WordPress and other open source software projects as well, there is an increase in speaker diversity. </p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img src=\"https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?fit=632%2C474&ssl=1\" alt=\"Diverse Speaker Training group \" class=\"wp-image-8196\" srcset=\"https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?w=2048&ssl=1 2048w, https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?resize=300%2C225&ssl=1 300w, https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?resize=1024%2C768&ssl=1 1024w, https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?resize=768%2C576&ssl=1 768w, https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?resize=1536%2C1152&ssl=1 1536w, https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?w=1264&ssl=1 1264w, https://i0.wp.com/wordpress.org/news/files/2019/12/image-3.png?w=1896&ssl=1 1896w\" sizes=\"(max-width: 632px) 100vw, 632px\" /><figcaption>WordCamp US 2019</figcaption></figure>\n\n\n\n<p>As a result of the success, Jill is now sponsored to continue the program. The first sponsor is Automattic. She’s proud of how the diversity represented on the stage adds value not only to the brand but also in the long-term will lead to the creation of a better product. She’s inspired by seeing the communities change as a result of the new voices and new ideas at the WordPress events.</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p><em>Jill’s leadership in the development and growth of the Diversity Outreach Speaker Training initiative has had a positive, measurable impact on WordPress community events worldwide. When WordPress events are more diverse, the WordPress project gets more diverse — which makes WordPress better for more people.”</em></p><cite><em> <NAME>, Community organizer on the WordPress open source project</em></cite></blockquote>\n\n\n\n<h3><strong>Resources:</strong></h3>\n\n\n\n<ul><li>The Workshop: <a href=\"http://diversespeakers.info/\">http://diversespeakers.info/</a></li><li>More information: <a href=\"https://tiny.cc/wpdiversity\">https://tiny.cc/wpdiversity</a></li><li><a href=\"https://make.wordpress.org/community/handbook/wordcamp-organizer/planning-details/speakers/building-a-diverse-speaker-roster/\">How to build a diverse speaker roster</a></li><li><a href=\"https://make.wordpress.org/community/2017/11/13/call-for-volunteers-diversity-outreach-speaker-training/\">Diversity Outreach Speaker Training Team</a></li></ul>\n\n\n\n<h2><strong>Contributors</strong></h2>\n\n\n\n<p><NAME> (<a href=\"https://profiles.wordpress.org/wpfiddlybits/\">@wpfiddlybits</a>), <NAME> (<a href=\"https://profiles.wordpress.org/yvettesonneveld/\">@yvettesonneveld</a>), <NAME> (<a href=\"https://profiles.wordpress.org/chanthaboune/\">@chanthaboune</a>), <NAME> (<a href=\"https://profiles.wordpress.org/topher1kenobe/\">@topher1kenobe</a>)</p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"alignleft is-resized\"><img src=\"https://lh6.googleusercontent.com/fq6qus5qmviDZaznrQnW-4wcbSs6NSrqeqEEGnPjgi2WJrVevNm4Em4KsP-VVH_0kMgWuNtW7mm_V9-hKtrrJFohRi6KrUXAoLHjrymChCltMr9fuh4dBIu_0SqNPts0MZgcvh_W\" alt=\"\" width=\"153\" height=\"115\" /></figure></div>\n\n\n\n<p><em>This post is based on an article originally published on HeroPress.com, a community initiative created by </em><a href=\"https://profiles.wordpress.org/topher1kenobe/\"><em><NAME></em></a><em>. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.</em></p>\n\n\n\n<p></p>\n\n\n\n<p><em>Meet more WordPress community members over at </em><a href=\"https://heropress.com/\"><em>HeroPress.com</em></a><em>!</em></p>\n\n\n\n<p><em><strong>Correction: December 7, 2019</strong><br>The original article mentioned the team Jill lead, but did not mention the team members who joined her. Those have been added. Apologies to Vanessa, Kate, and Mandi. <img src=\"https://s.w.org/images/core/emoji/12.0.0-1/72x72/1f642.png\" alt=\"🙂\" class=\"wp-smiley\" style=\"height: 1em; max-height: 1em;\" /> </em></p>\n\";s: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:\"8192\";s: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:57:\"\n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:37:\"The Month in WordPress: November 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2019/12/the-month-in-wordpress-november-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 02 Dec 2019 08: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:8:\"category\";a:1:{i:0;a:5:{s:4:\"data\";s:18:\"Month in WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8156\";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:330:\"November has been a big month in the WordPress community. New releases, big events, and a push for more contributors have characterized the work being done across the project — read on to find out more! The release of WordPress 5.3 “Kirk” WordPress 5.3 was released on November 12, and is available for download or […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}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:\"<NAME>\";s: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:8119:\"\n<p>November has been a big month in the WordPress community. New releases, big events, and a push for more contributors have characterized the work being done across the project — read on to find out more!</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>The release of WordPress 5.3 “Kirk”</h2>\n\n\n\n<p><a href=\"https://wordpress.org/news/2019/11/kirk/\">WordPress 5.3 was released</a> on November 12, and is <a href=\"https://wordpress.org/download/\">available for download</a> or update in your dashboard! Named “Kirk,” after jazz multi-instrumentalist <NAME>, 5.3 enhances the block editor with <a href=\"https://make.wordpress.org/core/2019/09/24/new-block-apis-in-wordpress-5-3/\">new APIs</a> and <a href=\"https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/\">theme-related features</a>, adds more intuitive interactions, and improves accessibility in a number of areas — including <a href=\"https://make.wordpress.org/core/2019/10/18/noteworthy-admin-css-changes-in-wordpress-5-3/\">CSS in the dashboard</a>, the <a href=\"https://make.wordpress.org/core/2019/10/14/improvements-in-media-component-accessibility-in-wordpress-5-3/\">media manager</a>, <a href=\"https://make.wordpress.org/core/2019/09/23/core-widgets-new-aria-current-attribute-in-wordpress-5-3/\">core widgets</a>, and <a href=\"https://core.trac.wordpress.org/query?focuses=~accessibility&milestone=5.3&group=component&max=500&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=id\">dozens of other areas</a>.</p>\n\n\n\n<p>You can read the full details of all the included enhancements in the <a href=\"https://make.wordpress.org/core/2019/10/17/wordpress-5-3-field-guide/\">5.3 Field Guide</a>.</p>\n\n\n\n<p>Along with 5.3 came <a href=\"https://wordpress.org/themes/twentytwenty/\">the new Twenty Twenty theme</a>, which gives users more design flexibility and integrates with the block editor. For more information about the improvements to the block editor, expanded design flexibility, the Twenty Twenty theme, and to see the huge list of amazing contributors who made this release possible, read <a href=\"https://wordpress.org/news/2019/11/kirk/\">the full announcement</a>.</p>\n\n\n\n<p>Want to get involved in building WordPress Core? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>. You can also <a href=\"https://make.wordpress.org/core/2019/11/15/5-3-retrospective-call-for-feedback/\">provide feedback</a> on the 5.3 release process.</p>\n\n\n\n<h2>At Last! bbPress 2.6!</h2>\n\n\n\n<p><a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6/\">bbPress 2.6 was released</a> on November 12 after a little over six years in development. This new release includes per-forum moderation, new platforms to import from, and an extensible engagements API. You can read more about all of this in <a href=\"https://codex.bbpress.org/\">the bbPress codex</a>.</p>\n\n\n\n<p><a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6-1-is-out/\">Version 2.6.1</a> and <a href=\"https://bbpress.org/blog/2019/11/bbpress-2-6-2-is-out/\">2.6.2</a> quickly followed, both of which fixed a number of bugs that required immediate attention.</p>\n\n\n\n<p>Want to get involved in building bbPress? Follow <a href=\"https://bbpress.org/blog/\">the bbPress blog</a> and join the #bbpress channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>State of the Word</h2>\n\n\n\n<p><a href=\"https://2019.us.wordcamp.org/\">WordCamp US 2019</a> was held in St. Louis, MO this year on November 1-3. At the event, <a href=\'https://profiles.wordpress.org/matt/\' class=\'mention\'><span class=\'mentions-prefix\'>@</span>matt</a> gave his annual State of the Word address, during which he shared what had been accomplished in the past year, announced what is coming next, and shared several ways to get involved.</p>\n\n\n\n<p>You can watch <a href=\"https://www.youtube.com/watch?v=LezbkeV059Q&t=21s\">the State of the Word</a> as well as <a href=\"https://www.youtube.com/watch?v=fFsVbAo8HwI\">the Q&A session at the end</a>, and <a href=\"https://ma.tt/2019/11/state-of-the-word-2019/\">read Matt’s recap</a> of the address. If you didn’t make it to St. Louis, you can still <a href=\"https://www.youtube.com/playlist?list=PL1pJFUVKQ7ETHl165LvLVXfB3yBZEzV-q\">watch all the sessions</a> at your leisure.</p>\n\n\n\n<h2>Five for the Future</h2>\n\n\n\n<p>During the State of the Word, Matt announced that there is now <a href=\"https://wordpress.org/five-for-the-future/\">a dedicated landing page for Five for the Future</a>, which features the people and organizations that commit at least it 5% of their resources to the WordPress open source project. There are many ways to contribute to WordPress, such as core development, marketing, translation, training, and community organizing, among many other important paths to contribution.</p>\n\n\n\n<p>Five for the Future welcomes individuals and organizations, and highlights all the incredible ways we build WordPress together. For more information, visit <a href=\"https://wordpress.org/five-for-the-future/\">the Five for the Future page</a>.<br></p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li>After releasing WordPress 5.3, the Core team announced <a href=\"https://make.wordpress.org/core/2019/11/21/tentative-release-calendar-2020-2021/\">a tentative release schedule</a> for 2020 and 2021.</li><li>The Core team has announced <a href=\"https://make.wordpress.org/core/2019/11/28/new-css-focus-in-core/\">a new CSS focus</a> to complement the existing ones for PHP and JavaScript — this focus comes with dedicated tags, targeted work, and a new #core-css Slack channel.</li><li>Version 2.2 of the WordPress Coding Standards <a href=\"https://github.com/WordPress/WordPress-Coding-Standards/releases/tag/2.2.0\">has been released</a> — this new release is ready for WordPress 5.3, includes five brand new sniffs, and plenty of new command-line documentation.</li><li>The latest update to the Theme Review Coding Standards, <a href=\"https://github.com/WPTRT/WPThemeReview/releases/tag/0.2.1\">v0.2.1</a>, is compatible with v2.2 of the WordPress Coding Standards, and helps authors to build more standards-compatible themes.</li><li><a href=\"https://2019.us.wordcamp.org/2019/11/11/wordcamp-us-2020/\">The WordCamp US team has announced</a> the dates for next year’s event in St. Louis, MO — WordCamp US 2020 will be held on October 27-29. This will be the first time that the event will be held during the week and not on a weekend. The team has also announced a Call for Organizers. If you are interested in joining the team, <a href=\"https://2020.us.wordcamp.org/2019/11/21/join-the-wcus-2020-organizing-team/\">learn more</a>. </li><li>The WP Notify project, which is building a unified notification system for WordPress Core, <a href=\"https://make.wordpress.org/core/2019/11/29/wp-notify-hiatus-till-january-2020/\">is on hiatus</a> until January 2020.</li><li>A working group on the Community Team <a href=\"https://make.wordpress.org/community/2019/11/25/handbook-update-how-to-improve-the-diversity-of-your-wordpress-events/\">has updated their Handbook</a> to help organizers create more diverse events.</li><li>The WP-CLI team <a href=\"https://make.wordpress.org/cli/2019/11/12/wp-cli-v2-4-0-release-notes/\">released v2.4.0</a> of the WordPress command-line tool. This release includes support for WordPress 5.3 and PHP 7.4.</li><li>Gutenberg development continues rapidly with <a href=\"https://make.wordpress.org/core/2019/11/27/whats-new-in-gutenberg-27-november/\">the latest 7.0 release</a> including an early version of the navigation menus block, among other enhancements and fixes.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\n\";s: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:\"8156\";s: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:60:\"\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";s:5:\"child\";a:4:{s:0:\"\";a:6:{s:5:\"title\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"WordPress 5.2.4 Update\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:58:\"https://wordpress.org/news/2019/11/wordpress-5-2-4-update/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 19 Nov 2019 04:47: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: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:34:\"https://wordpress.org/news/?p=7787\";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:346:\"Late-breaking news on the 5.2.4 short-cycle security release that landed October 14. When we released the news post, I inadvertently missed giving props to <NAME> of RIPS Technologies for finding and disclosing an issue where path traversal can lead to remote code execution. Simon has done a great deal of work on the WordPress […]\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:13:\"<NAME>\";s: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:1102:\"\n<p>Late-breaking news on the<a href=\"https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/\"> 5.2.4 short-cycle security release </a>that landed October 14. When we released the news post, I inadvertently missed giving props to <NAME> of <a href=\"https://blog.ripstech.com/\">RIPS Technologies</a> for finding and disclosing an issue where path traversal can lead to remote code execution. </p>\n\n\n\n<p>Simon has done a <a href=\"https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/\">great</a> <a href=\"https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/\">deal</a> of <a href=\"https://wordpress.org/news/2019/09/wordpress-5-2-3-security-and-maintenance-release/\">work</a> on the WordPress project, and failing to mention his contributions is a huge oversight on our end.</p>\n\n\n\n<p>Thank you to all of the reporters for <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">privately disclosing</a> vulnerabilities, which gave us time to fix them before WordPress sites could be attacked.</p>\n\";s: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:\"7787\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}s:27:\"http://www.w3.org/2005/Atom\";a:1:{s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:0:\"\";s:7:\"attribs\";a:1:{s:0:\"\";a:3:{s:4:\"href\";s:32:\"https://wordpress.org/news/feed/\";s:3:\"rel\";s:4:\"self\";s:4:\"type\";s:19:\"application/rss+xml\";}}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:44:\"http://purl.org/rss/1.0/modules/syndication/\";a:2:{s:12:\"updatePeriod\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"\n hourly \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:15:\"updateFrequency\";a:1:{i:0;a:5:{s:4:\"data\";s:4:\"\n 1 \";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:30:\"com-wordpress:feed-additions:1\";a:1:{s:4:\"site\";a:1:{i:0;a:5:{s:4:\"data\";s:8:\"14607090\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:9:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Sat, 08 Feb 2020 18:06:36 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:\"Mon, 03 Feb 2020 09:54:06 GMT\";s:4:\"link\";s:63:\"<https://wordpress.org/news/wp-json/>; rel=\"https://api.w.org/\"\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 1\";}}s:5:\"build\";s:14:\"20130911040210\";}','no'),(133,'_transient_timeout_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1581228397','no'),(134,'_transient_feed_mod_9bbd59226dc36b9b26cd43f15694c5c3','1581185197','no'),(135,'_transient_timeout_feed_d117b5738fbd35bd8c0391cda1f2b5d9','1581228399','no'),(136,'_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:80:\"WPTavern: Convert Classic Content to Blocks With the Bulk Block Converter 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=97056\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/convert-classic-content-to-blocks-with-the-bulk-block-converter-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:3462:\"<p>Organic Themes released the <a href=\"https://wordpress.org/plugins/bulk-block-converter/\">Bulk Block Converter </a>WordPress plugin last month and updated it in the past week. The plugin allows users to convert classic content, written in the old editor, to the new block format.</p>\n\n\n\n<p>Unless end-users have the Classic Editor plugin installed, their old content is placed into the classic block in the newer block editor. WordPress provides an option for transforming this content into individual blocks from the block-editor interface. However, this must be done on a per-post basis.</p>\n\n\n\n<p>“Going back and converting each post and page with a classic block to individual blocks can be a very long and tedious process,” said <NAME>, co-founder of Organic Themes. “The Bulk Block Converter plugin quickly scans all your posts and pages for classic blocks, and allows you to quickly convert them all to individual blocks within one interface.”</p>\n\n\n\n<p>Originally, Organic Themes built the plugin for internal use at their company. “We developed the plugin to help us convert the content of our theme demos to blocks more efficiently,” said Morgan. The company had to convert over 40 theme-demo sites with an average of 50 posts and pages per site. They built this plugin to avoid a long and painstaking process. Then decided to share it. “We thought the tool could be very useful for other users migrating to Gutenberg.”</p>\n\n\n\n<p>For users with a lot of old content, Bulk Block Converter could be the key to moving it all to the new block editor system. Based on the conversions I ran on a couple of test installations, it worked flawlessly.</p>\n\n\n\n<h2>How the Plugin Works</h2>\n\n\n\n<img /> Block Conversion plugin screen in the admin.\" class=\"wp-image-97059\" srcset=\"https://wptavern.com/wp-content/uploads/2020/02/bulk-block-converter-tool.png 896w, https://wptavern.com/wp-content/uploads/2020/02/bulk-block-converter-tool-300x175.png 300w, https://wptavern.com/wp-content/uploads/2020/02/bulk-block-converter-tool-768x449.png 768w, https://wptavern.com/wp-content/uploads/2020/02/bulk-block-converter-tool-500x292.png 500w\" sizes=\"(max-width: 896px) 100vw, 896px\" />Bulk Block Converter admin screen for converting content.\n\n\n\n<p>The Bulk Block Converter plugin adds a new “Block Conversion” sub-menu item to the WordPress “Tools” menu in the admin. Once on that screen, it provides a “Scan Content” button. When clicked, it checks all of your posts, pages, and other custom post types for classic content. It then builds a list table of all the content.</p>\n\n\n\n<p>From that point, you can choose between converting each post individually or running a bulk conversion of all posts. I always recommend being cautious with such plugins by converting and checking a couple of individual posts before trying bulk conversions.</p>\n\n\n\n<p>The process for converting posts was snappy during my tests. In just a few moments, I converted all of my old content over without issue.</p>\n\n\n\n<p class=\"has-text-color has-background has-white-color has-blue-700-background-color is-style-highlight shadow-md text-white bg-blue-700\">Like any plugin that modifies content in this way, it is prudent to store a backup of your site before converting the posts. This is also a one-way conversion process. Once a post is transformed, there is no going back.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 07 Feb 2020 20:49: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:14:\"<NAME>\";s: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:94:\"WPTavern: Gutenberg 7.4 Adds New Color Controls, Link UI, and Block Scaffolding for Developers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=97032\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://wptavern.com/gutenberg-7-4-adds-new-color-controls-link-ui-and-block-scaffolding-for-developers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4443:\"<p class=\"has-drop-cap\">The Gutenberg development team <a href=\"https://make.wordpress.org/core/2020/02/05/whats-new-in-gutenberg-5-february/\">launched version 7.4 of the plugin</a> yesterday. The update includes a few user-facing features: a text color control for the group block, background-color control for the columns block, and a new link UI for rich text components. For developers, the team introduced a script for launching a block plugin from the command line.</p>\n\n\n\n<p>After a dramatic increase in speed in the <a href=\"https://wptavern.com/gutenberg-7-3-brings-navigation-block-colors-block-collections-api-and-dynamic-post-blocks\">last update</a>, version 7.4 continues down the same path. When tested against a post with approximately 36,000 words and 1,000 blocks, page load speeds dropped from 5.461s to 5.037s and keypress events from 34.63ms to 34.54ms. This is not a significant reduction, but every improvement helps.</p>\n\n\n\n<p>The update includes over two dozen bug fixes and several enhancements. Work toward the navigation block continues. The experience is slowly getting better, but it still doesn’t feel ready for production.</p>\n\n\n\n<p>The team also launched an early, experimental <a href=\"https://github.com/WordPress/gutenberg/pull/19883\">mechanism for handling global styles</a>, a feature that may be complete this year. <a href=\"https://wptavern.com/key-takeaways-from-the-first-future-of-themes-meeting\">Global styles</a> would allow themes to set default colors, typographical settings, and potentially more. Theme authors should keep an eye on the development of this feature and offer feedback.</p>\n\n\n\n<h2>Group Block Gets Text Color Control</h2>\n\n\n\n<img />Changing the text color for an entire group.\n\n\n\n<p>The Gutenberg team once again cleans up one of my biggest gripes. When using the group block in the past, end-users could not apply a text color to every sub-element of the group block. Instead, they had to add a text color to any blocks within the group. It was a painstaking process at times, particularly with groups of many blocks.</p>\n\n\n\n<p>With this change in version 7.4, users can apply a <a href=\"https://github.com/WordPress/gutenberg/pull/19181\">text color to the entire group</a> at once, and that color should trickle down to sub-blocks. Of course, users can still change the color of inner blocks if necessary.</p>\n\n\n\n<h2>Columns Block Gets Background Color Control</h2>\n\n\n\n<img />Customizing the background color on a columns block.\n\n\n\n<p>Gutenberg 7.4 adds the <a href=\"https://github.com/WordPress/gutenberg/pull/17813\">background color control to the columns block</a>. This makes it work similarly to the group block by adding a background color to the entire containing block. Unfortunately, it did not receive the same text color control in this release.</p>\n\n\n\n<p>Currently, there is still no way to add background and text colors to an individual column. End-users can only add a color on the sub-blocks within a column. The feature is a step in the right direction, but it’s still missing some essential color options.</p>\n\n\n\n<h2>Link UI Updated</h2>\n\n\n\n<img />Inserting a link into a paragraph with the new UI.\n\n\n\n<p>This is a minor change but welcome. The link UI for rich text, a component used for blocks such as paragraphs, <a href=\"https://github.com/WordPress/gutenberg/pull/19686\">now has the same UI</a> as the navigation and button blocks. The consistency is nice, but I am a fan of the improvement overall. </p>\n\n\n\n<p>The UI change is subtle, but it already feels slightly more comfortable after a day of use.</p>\n\n\n\n<h2>Block Scaffolding for Developers</h2>\n\n\n\n<img />Initial JavaScript file for an auto-created block plugin.\n\n\n\n<p>For developers who want to jump-start a new block plugin, the Gutenberg team <a href=\"https://www.npmjs.com/package/create-wordpress-block\">released an official script</a> for getting started. By running the <code>npm init @wordpress/block</code> command, the script will install and run you through setting up a custom block. The script creates an entire plugin folder, including the necessary PHP, CSS, and JavaScript files.</p>\n\n\n\n<p>This script is ideal for building single-block plugins, which will eventually be exposed via the official WordPress block directory. Because it creates an entire plugin, it is probably not the best route for creating new blocks within an existing plugin.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Feb 2020 21:06: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:14:\"<NAME>\";s: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:76:\"Post Status: Syed Balkhi on Awesome Motive’s acquisition of All In One 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=76000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://poststatus.com/syed-balkhi-on-awesome-motives-acquisition-of-all-in-one-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:31030:\"<p>Syed Balkhi joins me to discuss the acquisition of AIO SEO.</p>\n\n\n\n<p>All in One SEO is one of the most widely used plugins in the WordPress ecosystem, with more than two million installs.</p>\n\n\n\n<p>In the <a href=\"https://semperplugins.com/all-in-one-seo-is-now-part-of-the-awesome-motive-family/\">announcement post</a>, Syed says the entire All in One SEO team is joining Awesome Motive, aside from founder <NAME>:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Aside from new ownership change, it’s business as usual. You can continue to use the plugin that you love without any interruptions.</p><p>With the exception of Michael, the entire All in One SEO team joined Awesome Motive. This means that you are still being supported by the same talented people.</p><p>On top of that, we have added more team members from Awesome Motive who will be working on the All in One SEO project, including me.</p><p>In a near future release, you will see a small plugin design refresh in the WordPress admin area.</p><p>With our experience and a dedicated team, we will be adding several new features and improvements to the All in One SEO WordPress plugin in the near future.</p></blockquote>\n\n\n\n\n\n\n\n<p><strong>Some of the questions he answers:</strong></p>\n\n\n\n<ul><li>So who is your target customer with All in One SEO?</li><li>How is the model structured? You’re directing strategy… is there a partner you\'re working with?</li><li>How does your vision for AIO SEO compare to what you see in Yoast SEO?</li><li>How do you envision the free/premium divide?</li><li>What are the first three things you plan to do?</li><li>How did the conversation with Michael start? Did you approach him? Did he approach you? Tell me a story.</li><li>How far do you think you can scale this business model?</li><li>What do you think about the consolidation we’re seeing in the plugin ecosystem — the consolidation you’re a major player in?</li></ul>\n\n\n\n<p><strong>Links:</strong></p>\n\n\n\n<ul><li><a href=\"https://awesomemotive.com/\">Awesome Motive</a></li><li><a href=\"https://wordpress.org/plugins/all-in-one-seo-pack/\">AIO SEO on WP.org</a></li><li><a href=\"https://semperplugins.com/all-in-one-seo-is-now-part-of-the-awesome-motive-family/\">Acquisition announcement</a></li></ul>\n\n\n\n<h3>Full Transcript</h3>\n\n\n\n<div class=\"transcript\">\n<p>Transcribed by https://otter.ai</p>\n\n\n\n<p><strong><NAME> 0:02 </strong><br />This episode of the Draft podcast is brought to you by Jilt. Jilt is email marketing built for eCommerce stores. Go to jilt.com to try it today. I know that Jilt is an awesome product because I work on it every single week. And I get to see it up close and personal. Jilt has amazing integrations for WooCommerce, Shopify, and ads so no matter what platform you\'re building your eCommerce site on, it will work for you. It\'s built specifically for eCommerce with extremely powerful segmentation options for you to set up automations to work for you while you sleep. And you can do your manual email marketing through our broadcasts feature in Jilt. It\'s a great tool. I know you\'ll love it. Try it today. Go to Jilt.com. And thanks to Jilt for being a Post Status partner. Hello and welcome to the Draft podcast. My name is <NAME>. I\'m with <NAME>. Hey Syed. </p>\n\n\n\n<p><strong>Syed Balkhi 0:55</strong><br />Hey man, how are you? </p>\n\n\n\n<p><strong><NAME>ard 0:56</strong><br />I\'m doing great. So you know like you Guys have news coming out all the time. And you\'ve got another plugin that you\'ve put under the automotive umbrella. And it\'s all in one SEO. So first off just congrats on the acquisition of a really long-running popular plugin.</p>\n\n\n\n<p><strong>Sy<NAME>hi 1:18 </strong><br /> Thank you. Thank you.</p>\n\n\n\n<p><strong><NAME> 1:20 </strong><br /> So let\'s start with what attracted you to all in one SEO as the type of plugin that you were interested in.</p>\n\n\n\n<p><strong><NAME> 1:29 </strong><br /> So when I started a web beginner I was I started with all in one SEO, I\'ve had a lot of respect for the plugin in industry. I believe it you know, it is one of the tools that are essential for a website owner. And it is something that our users have continued to, to build. If you haven\'t checked out the WP begin to engage Facebook group, this question comes up a lot I did a, I did a video about it and people were asking, like, you know, when are you going to build a SEO plugin that is beginner-friendly. And, you know, it\'s just keeps coming up over and over every year if you\'ve been able to build one product, what would it be? And SEO keeps coming upset. We tried to make a deal happen. And you know, I approached several authors and this was the one that we ended up going with.</p>\n\n\n\n<p><strong><NAME> 2:25 </strong><br /> So you say, you know, people from the dopey beginner groups were the ones that initiated this conversation. So who is your target customer with a plugin like this?</p>\n\n\n\n<p><strong><NAME> 2:38 </strong><br /> Small business owners like you know, DIY website owners, I would say is there is a target market you know, we try to stay away from the super-advanced super Dev audience, we want to help small business owners so our goal at awesome motive is to you know, help small businesses go and compete with the big guys. And that is something that we continue with all of our products.</p>\n\n\n\n<p><strong><NAME> 3:00 </strong><br /> So obviously the I guess I would say the market leader in this genre has been Yoast SEO for years. If I remember the correlation of how the usage worked out all in one, SEO was the most popular plugin for a really long time in the SEO market, and then Yost took over that spot. What\'s the comparison that you see in Yost? I mean, I think you and Yost divock are friendly and the team at Yost, how does how to your efforts here? You know, like, how does it differ from Yoast? Is Yost an advanced plugin? Like what makes you most advanced versus like the beginner features that you envision? All in one Seo? That\'s the stuff that I don\'t quite know how to nail down in my mind.</p>\n\n\n\n<p><strong><NAME> 3:45 </strong><br /> For sure, for sure. Yeah. So I mean, I\'m friends of yours. Of course, I told. I told Yost about, about the field before he went public. So it doesn\'t affect our friendship. I think you know, in any market you have multiple players, right? They have their own unique sets of features and divisions that they carry forward. And I know Yost has a vision that he is moving forward with. My, my goal is to really focused on two things, one, reliability, and the second is to be results-focused. And that the second one is definitely a primary thing I want a plugin, that is results focus on, you know, almost every SEO plugin, when you look at it in the market, and there\'s some newcomers that are that have entered the market as well. They kind of just help you set up and let you optimize some pages. And that\'s kind of it like there hasn\'t been any innovation, if you may, from a bigger picture point of view in the SEO plugin market in a while.</p>\n\n\n\n<p>And I want to change that.</p>\n\n\n\n<p><strong><NAME> 4:56 </strong><br /> So talk to me about that. Because I know I know. I know <NAME> well enough to know he\'s got a plan. As soon as he has control, you\'ve got some things that you want to do. I have to admit, I haven\'t installed all in one SEO and I don\'t even know how long I don\'t know what it looks like, once you get working on it on the interior. What\'s it like today? And I guess, what are your big three things that you want to do? I know you got those mapped out?</p>\n\n\n\n<p><strong><NAME> 5:24 </strong><br /> Yeah, I mean, we have a very clear 12-month plan the three-year picture, I would say, you know, install it, just so you can see, you can have a before and after comparison, I think that you know that you can see the impact that we\'re, we\'re about to happen on this plugin. So, you know, over the years, like, I\'ve built a lot of internal tools that we just use, and like when you asked like, you know, what is the target market release me and I\'m like, I try to dog food pretty much all of our own products and I think that\'s, that\'s one of our secret sauces on how we make the best product. So I want to bring in a lot of the internal tools that we have, that we already have into a central plugin that we can control manage, and also, you know, share it with the WordPress community and in the small business community as well. I am also you know when you think about like a lot of my friends who are influencers somewhere, you know, meeting SEO experts as well they all have, you know, their own internal SEO tools that they\'ve built, we kind of shared that knowledge, we sometimes shared those scripts with each other. So we can kind of have an advantage and I want to bring that level the playing field. So we\'re going to be bringing a lot of those other tools in it so when it when you know when you think about the name all in one SEO, I think this is going to really become that. Without divulging too much of the you know, fine details, I think, think about it from that way it finally is true SEO suite for WordPress.</p>\n\n\n\n<p><strong><NAME> 6:59 </strong><br />You mentioned how the way that people typically look at SEO and WordPress right now is you go to a single singular URL. So let\'s say it\'s a, you know, it\'s a page of, you know, the best WordPress host or whatever. And you optimize that page. So is what you\'re talking about more of how to figure out a site wide plan or overview, is that right?</p>\n\n\n\n<p><strong><NAME> 7:22 </strong><br />Exactly. So when you think about that, you know, a small business owner they come in and install the plugin then what what happens do they do the chase a light, a specific color, but what is that in regards to anyways? I want to I want to really help people discover new growth opportunities. So like SEO is not just some acronym. That doesn\'t mean anything new. Most people will be they everybody kind of has a vision, but everybody\'s lost. really making that easy, making people making easy to identifying opportunities, measure those opportunities and you know, doing a little bit More than just setting up an optimizing. Okay. Yeah.</p>\n\n\n\n<p><strong><NAME> 8:03 </strong><br /> So, you know, when I think of small businesses, and when I talk to the friends that are, you know, they run small businesses like a dentist or something I usually start thinking about SEO in terms of local stuff or so what\'s the free and premium divide for you?</p>\n\n\n\n<p><strong><NAME> 8:20 </strong><br /> Yeah, there\'s gonna be a lot of premium features that we\'re going to add, of course, over the years, we\'re going to continue improving the tree offering, which is, you know, core of this plugin anyways. That\'s, that\'s, that\'s, that\'s where I think I\'ll pretty much stop at you know, there\'s gonna be a lot of cool tools that are going to come in that we\'re going to add in the premium version. There\'s also going to be a lot of really cool thing that we\'re going to add in the free version that we just haven\'t seen. Is this going to happen over the course of the next three months? No regular we\'re going to do some like small refreshes the three in the three month period, but the bigger picture and the big things are going to be rolled out over the, you know, 12 month period because we have to take our internal tools and then, you know, turn it into so it can be used by tuning people.</p>\n\n\n\n<p><strong><NAME> 9:12 </strong><br /> <em>I\'m pretty biased towards Jilt. And it\'s with good reason. When I was considering to take on some part-time work to complement what I was doing with Post Status, I went straight to Skyverge and said, I think that Skyverge seems like a fantastic company to work for. And Jilt seems like a really exciting product to work on. Jilt is really the tool that you need to complement your eCommerce store. It\'s email marketing, but it\'s built specifically for eCommerce stores. So what\'s that mean in practice? Well, you can do your marketing outreach through a manual newsletter built into Jillson, some people don\'t even know that. That\'s done via the broadcast feature. But then there are the automation tools. jilt started out as an abandoned cart automation tool, but it\'s a lot more than that. Now, you can segment based on anything that\'s part of your historical store data. So if you will Want to email people just who purchased a product in a certain category, then you can do it. If you have an update for a product and you want to send an email to people who have purchased that historically, you can do it. If you want to send an email because people have spent a certain amount of money in their lifetime, and your store, you can do it. You can do so much with guilts Automation features, the segmentation data is extremely thorough, whether you\'re running a WooCommerce store, or a Shopify store or an ed d store, and you\'re not using jilt, then, quite frankly, you\'re giving up potential revenue. Try jilt today, go to jilt.com. I know you\'ll love it. </em><br /><br />How did the conversation with Michael start then? Did you approach him? Did he approach you? Tell me a story around the process of acquiring a plugin especially one was such a huge user base. And I guess there\'s a lot of implications when someone new takes over one of the most popular plugins in the plugin repo.</p>\n\n\n\n<p><strong>Sy<NAME> 10:59 </strong><br /> Absolutely. So, you know, I think I mentioned to you, you this came back from the WP beginner communities after I did the web kind of census survey, which happened at the beginning of the year, I start getting all sorts of data from the audience and from survey responses and start analyzing. And I reached out to, to Michael, as I started the conversation, you know, it started from discussing of what does this look like, you know, does this look like us partnering together and running that does it look like us taking a full hundred percent stake into the business then, you know, Michael walks from Italy, you know, there was, like, a lot of conversation that, you know, started with things like maybe March, so we didn\'t close the deal until January 3. So it takes you know, it\'s like think about it when this is something that you have been doing for 10 plus years this is your baby. It\'s an emotional process. It\'s a yes, it\'s a very emotional process. It\'s not an easy decision to make, and I\'m not you know that. I think the things that made it easy or easier to make things you know a little bit smoother was that I\'ve known Michael for a long time, right. Michael has been in the WordPress ecosystem. This was the original WordPress SEO plugin. I\'ve had numerous occasions where I hang out with Michael, at the WordPress community summit, the first-ever … network in Raleigh several times. I actually flew out to Raleigh to hang out with Michael to kind of share our vision because you know, for both of us, the most important part is users and the community. And, you know, we were in you know, we were lying there. So that\'s like that\'s, that\'s really a nutshell what happened in the nine-month period, right? Of course legal comes in Ba ba ba ba ba that\'s normal of any deal, boring stuff.</p>\n\n\n\n<p><strong><NAME> 13:02 </strong><br />You can have it all settled, I guess and still have several months left on Enter before it actually, you know, get signed and is ready to go.</p>\n\n\n\n<p><strong><NAME> 13:12 </strong><br /> Right. And especially with my travel schedule, it kind of made things a little difficult, right? Because we\'re growing and then I you know, I have certain like level commitments already like that that are planned six months plus in advance always. So it becomes a little tricky. So we wanted to do face to deal in December, but it kind of went in by the January.</p>\n\n\n\n<p><strong><NAME> 13:35 </strong><br /> Yeah. So the, you know, I\'ve seen you do this a couple times now where you acquire another business and obviously you don\'t acquire something unless you see potential growth in it. So you see growth in this product. However, I would say this product may be different than some of the others whereas where, you know, it was at the top of the game for a while and then it had a you know, maybe it grew WordPress a little bit, but it wasn\'t the market leader there were there was growth and other plugins in the sector, significantly higher than all in one, SEO is growth. Whereas some tools that you started, you were the growth plugin, like WP forms was a fresh plugin, you know, brand new, or you acquire one that is on a high growth trajectory. So this one\'s a little bit different than that. So how do you view the business model? And then how do you think that you can continue to scale this business model that there\'s so many products under the automotive umbrella these days?</p>\n\n\n\n<p><strong><NAME> 14:33 </strong><br /> You know, I think the important part is that you that you highlighted is almost every plugin grows with WordPress. You know, when I started using WordPress in 2006, I don\'t recall the exact number of how big WordPress was, but it wasn\'t 35% of the web.</p>\n\n\n\n<p><strong><NAME> 14:52 </strong><br /> Right? If I did a post on this, I think it was in 2010. And we weren\'t 8% of the web yet, so 20,006 it was probably like 1% Maybe 2% of the web, right?</p>\n\n\n\n<p><strong><NAME> 15:02 </strong><br /> So, So when you think about this right I\'m very bullish on WordPress. I really believe in WordPress, I even posted a story about like my cab driver using WordPress and learn from the … Uber driver and I was like, wow, this is crazy like you could get picked up from the Atlanta airport. So the, you know, the business model really is, you know, anytime you build an ecosystem, you rely on the ecosystem. I think the WordPress ecosystem has a lot of growth happening right now. And users are always looking for so you know, whether it be just because we have WP forms and needed it is the best hands down. WordPress form plugin doesn\'t mean people don\'t use others. Right. So I don\'t look for Oh, is this is this plugin necessarily growing or not? I think this is a plugin with a very loyal user base. Good, you know framework I haven\'t had a lot of sentimental values, you know, tied to all them on SEO because this was a plugin I started using, you know, and when I launched WP beginner, I think for a long time I was the de facto maybe an official doc for this because I would share my configuration and people would just come and copy and paste that into the chat back and forth. Michael and Steve, you know, who\'s been with all the one for 10 years, he actually joined us a motive. That\'s pretty, pretty awesome. But we also had a lot of sentimental values for this. And I\'ve learned a ton from Michael who\'s been very generous mean in the early days of the WordPress ecosystem. So I think there\'s a lot we can do in terms of the growth side of the plugin for sure.</p>\n\n\n\n<p><strong><NAME> 16:49 </strong><br /> As an aside, you mentioned in the announcement posts that Michael is not joining awesome motive, it sounds like he\'s gonna go find out what he wants to do next, but the rest of the Anyone that was working on all in one SEO is actually going to become an automotive employee.</p>\n\n\n\n<p><strong><NAME> 17:05 </strong><br /> Absolutely. that\'s already been done yet our goal whenever we make an acquisition, are you in a position or you know, one of the automotive core values people first and we always take care of that first.</p>\n\n\n\n<p><strong><NAME> 17:15 </strong><br /> So you\'ve got WP forms monster inside see prod webmail, SMTP raffle press. And you know, now we\'re putting all in one SEO as kind of primary product things. You\'ve got some other stuff too. If people go to automotive com, they can see everything that your team is working on. But what about this scale side of this? So we talked actually last week I don\'t know if you probably didn\'t listen to it. We talked last week about back when you showed me your schedule blocking and you know, we\'re talking about trying to manage multiple projects and you\'re the kind of the key to this to me, in our space, because there\'s so many things that you\'re paying personal attention to, but you\'ve created ways to where, you know, you don\'t have to be there. You\'re your vessel You add but like, Is there a ceiling for how you can scale like is it 10 products? Is it 15 or 20? what\'s this business model for you?</p>\n\n\n\n<p><strong><NAME> 18:11 </strong><br /> I wish I knew what the number was, I\'ve tentatively put it at 30? I think it is one of the things that you know that like I never do anything alone, right? There\'s like I\'ve worked like my secret against it\'s not such a big secret is I work with really really awesome partners, really talented people. You know, <NAME>, who leads OptinMonster and TrustPulse, you know, products. <NAME> who leads WP Forms and SMTP. These guys are phenomenal leaders right. <NAME> leading Monster Insights, phenomenal leader and they all have their own strengths. Right and we what makes us work really well together is how we compliment each other. So you know with <NAME> in SeedProd and RafflePress, right, that he brings a whole new set of values to Awesome Motive and what we\'re looking to do over the next 10 years. So, you know, when when we decided to acquire all in one SEO we looked for, you know, who would that personally because Michael was not going to be coming on board. And, of course, like, this is it. This is something I\'m really passionate about. And I know a lot about this industry. I wanted to make sure that there\'s somebody else who\'s really, really talented who can lead and <NAME>, I don\'t know, I don\'t know if you know him or not in the WordPress ecosystem. He\'s a phenomenal developer had had several other products in the EBD ecosystem that he sold to Pippin when you know, they did the market consolidation, their position. He\'s been working in the OptinMonster team for I believe, like four years, three, four years, and so He\'s actually going to be leading this division and department call and Seo? Of course, I\'m going to be I\'m very involved that, you know, I\'m not involved in OptinMonster day today, but you know, I\'ve been for two years. Same thing with WP Forms, that division is run by <NAME>, you know, my stream says pretty much online, so I\'m going to be very involved in it. So like, while we have a lot going on, I\'m not liking every single thing all the time. It\'s not it\'s not humanly possible. You see my time blocks, right? So these things move around around every quarter.</p>\n\n\n\n<p><strong><NAME> 20:34 </strong><br /> Okay, so you are bringing in Benjamin he\'s going to be the Christoff or the Acheson version of your partner? Your — almost like an implementation partner — whereas you\'re the strategic partner?</p>\n\n\n\n<p><strong><NAME> 20:49 </strong><br /> Yeah, absolutely. I— you know, we could call it the integrator role that you know, GM …</p>\n\n\n\n<p>So yeah, Ben, Ben is awesome. And I\'ve had a pleasure working with him for last years. And he just continues to impress me, is literally like two and a half, three people into one. And you get to that pretty much about like, you know, Christoff, you\'ve seen the energy that he brings in Jared and Thomas, John,…</p>\n\n\n\n<p><strong><NAME> 21:23 </strong><br /> It seems like everybody, do you think this is a pattern of just the WordPress ecosystem? or part of the way you\'ve made these partnership decisions? Everybody that has played that role internally for you as a developer? Do you think is that strategic or just circumstance?</p>\n\n\n\n<p><strong><NAME> 21:40 </strong><br /> I think it\'s a circumstantial, more so than not, I don\'t believe that, you know, this role has to go to a developer. I think this role has to go to somebody who understands product and building products. So you know my extent of development, I —</p>\n\n\n\n<p><strong><NAME> 22:02 </strong><br /> It\'s more than you let on but no, you —</p>\n\n\n\n<p><NAME> 22:08 <br /> I don\'t think you have to be a developer you have to be — you have to understand the products and more importantly understand the problem you\'re solving and being able to improvise at, you know, at a, at a fast scale and being able to solve problems faster than other people. I think that\'s — that\'s what I look for, more so than anything.</p>\n\n\n\n<p><strong><NAME> 22:29 </strong><br /> All right, I want to finish up.</p>\n\n\n\n<p>I want to get your take on the consolidation that we\'re seeing in the\n plugin ecosystem is something I\'ve been talking about. I think since \n2017. We\'ve seen that playing out in hosting business, we\'ve seen it of \ncourse, that\'s kind of par for the course in the landscape of broader \nhosting. We\'re really seeing it ramp up in terms of plugins in the \nWordPress space. You You\'re one of the big players in that consolidation\n process, but there are others too. There\'s some people Whether they\'re \npublic yet or not, that are you know bundling up plugins and they\'re \ncoming at it with a strategy to take advantage of this market. So what \nare your What are your thoughts about consolidation and where we are \nkind of in I guess the market cycle of WordPress plugin businesses</p>\n\n\n\n<p><strong><NAME> 23:18 </strong><br /> think they in an important thing to look at is not just the consolidation part of WordPress but scale that new plugins are coming and being introduced. Right. So it\'s not it\'s it would be not fair to look at the market just from one angle because there\'s so much growth happening with a new plugins being added and when the market is growing at that scale consolidation becomes natural. And this just shows that WordPress is not in its infancy. anymore right when you because they are players. Better. That is certain sides enough to be able to have this kind of conversation. This was, you know, the consolidation doesn\'t always happen for monetary reasons, sometimes, you know, you\'ve been doing this for you have a plugin that you\'ve been building for like, seven, eight years, maybe you just want to move on. Right? So I don\'t necessarily, you know, that\'s just natural now that WordPress has been around for so long, then that\'s just a natural transition of people\'s lives. That\'s happening from an ecosystem point of view. Just the growth is phenomenal. When you look at the new plugins being added all the Gutenberg bought collection plugins that are being added, you know, and all of them are getting installs. There\'s not like, you know, there\'s one or two or three that just kind of own the market, every single one of them is getting itself. You know, you there\'s like, just because like we launched web form doesn\'t mean there hasn\'t been new contact or plugins. I mean, it says, I think that\'s just a natural phase of any ecosystem. And it means great things for the user, like the users of WordPress are going to benefit the most out of it. Because it shows that there\'s truly legitimate resources being put into building products and it\'s not just, you know, one person, you know, doing this as a side hustle. And there\'s nothing wrong with that there\'s a lot of great plugins come out of solid there are some really good ones that are still you know, somebody\'s side hustling and just crushing it right in the market. So I think it just it\'s just good It shows that businesses can use you know, WordPress plugin, and reliably knowing that they\'re this is not going to be disappeared is not just going to be discontinued. So, I think that I\'m very bullish on the WordPress market, and I have been for the last 10 years of running WP Beginner.</p>\n\n\n\n<p><strong><NAME> 25:48 </strong><br />Awesome. And you think this consolidation will probably continue on as a natural part of our ecosystem?</p>\n\n\n\n<p><strong><NAME> 25:55 </strong><br /> Yeah, I mean, absolutely.</p>\n\n\n\n<p>That\'s just natural for any system whether you\'re in WordPress, or you\'re in landscaping, or pool cleaning,</p>\n\n\n\n<p><strong><NAME> 26:06 </strong><br /> Maybe the difference from here on out will be that we\'ll start to see larger ones. And maybe I don\'t know if you have an opinion on that. But I think that\'s my gut feeling. You mentioned something like you get to a stage and, you know, some people are looking to exit and some people now have the resources to be able to make those acquisitions. So as time goes on that discrepancy between the big, you know, the people that are big enough now to where, let\'s say, I don\'t know, a million-dollar acquisition is in their wheelhouse, whereas five years ago, that was totally impossible for them to even consider as that becomes more and more the type of thing that is possible for a company to do will naturally see more of it. Would you agree with that?</p>\n\n\n\n<p><strong><NAME> 26:49 </strong><br /> I think they you know, what I would like to see is, you know, more of this happening, right because this just further validates the industry in itself. I think it is happening, right, you know, have it happening, whether it\'s public or not public, right. I know several players that are that are in the market. And in terms of big, I think that\'s just reality, right? You lay outside looking in big is not always what you see. Yeah, we\'re all small and big and not what you think. I think that it\'s just relative. Right. So to the individual perspective.</p>\n\n\n\n<p><strong><NAME> 27:27 </strong><br /> All right. So that\'s all I really have for you. I just wanted to chat with you about this acquisition and get your take on it. Is there anything that you want to either leaf people, whether they\'re an all in one SEO user, or if it\'s somebody in the post s audience question for me, the floor is yours.</p>\n\n\n\n<p><strong><NAME> 27:45 </strong><br /> No, you know, I always appreciate the work that you\'re doing and really excited to see Cory on board with post status. I just wanna say thank you, you know, to the community for the continued support of automotive our suite of products. We, we always strive to do better and serve our users. And I just hope to continue to earn everybody\'s trust for years to come.</p>\n\n\n\n<p><strong><NAME> 28:08 </strong><br /> Awesome. I appreciate it. Thanks for joining us and we will talk to everybody soon. Bye.</p>\n\n\n\n<p>Transcribed by https://otter.ai<br />\n</p>\n\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 06 Feb 2020 19:14: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:\"<NAME>\";s: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:69:\"WPTavern: Key Takeaways From the First ‘Future of Themes’ Meeting\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96997\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/key-takeaways-from-the-first-future-of-themes-meeting\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:10639:\"<p>There are few clear answers.</p>\n\n\n\n<p>As members of the <a href=\"https://wptavern.com/join-the-future-of-wordpress-themes-conversation-theme-review-team-to-hold-biweekly-discussions\">core design, editor, and theme review teams joined</a> for the <a href=\"https://make.wordpress.org/themes/2020/02/03/block-based-themes-meeting-agenda-for-february-5/\">inaugural biweekly meeting</a> that may decide the fate, at least in part, of WordPress themes, it became clear that there is no structured game plan. There are many ideas. There are several moving pieces. There are components and teams and ideas that must all coalesce and build something that has never been done before in WordPress.</p>\n\n\n\n<p>There is room for both excitement and concern.</p>\n\n\n\n<p>It is not necessarily a bad thing to be in an early experimental stage. However, WordPress is a mature product. It <em>feels</em> like there should be something more concrete about the future of one of its most integral parts — themes.</p>\n\n\n\n<p>That is what these meetings are for. They are about building bridges between various teams and making some decisions. One of the problems going forward will be cutting through the noise.</p>\n\n\n\n<p><strong>Takeaway #1:</strong> there are still more questions than there are answers.</p>\n\n\n\n<h2>Moving Forward With Block-Based Themes</h2>\n\n\n\n<p>If there is one thing that almost feels like a foregone conclusion it is that we are transitioning into a future where themes will be built entirely of blocks. Even the meeting was dubbed the “Block-Based Themes Meeting,” despite <a href=\"https://make.wordpress.org/themes/2020/01/29/new-bi-weekly-block-based-themes-meeting/#comment-43993\">some pushback</a> that such a meeting name was biased.</p>\n\n\n\n<p>This is no surprise. Block-based themes are where we are going. The real question is how that will work and what level of control theme authors will ultimately have over their creations.</p>\n\n\n\n<p><NAME>, a design director for Automattic, kicked off the meeting with an introduction of block-based themes and what the meeting would cover. “As most of you probably know, Gutenberg is in the process of <a href=\"https://make.wordpress.org/core/2019/09/05/defining-content-block-areas/\">expanding beyond the editor</a>,” he said. “As we’ve already seen, Gutenberg allows for a great deal of user-customization inside of post and page content. It allows any user to create custom layouts all by themselves, and style adjustments too. These will all usually be retained even after a user switches themes.”</p>\n\n\n\n<p>Full-site editing seeks to bring blocks to the entire site, which is traditionally the domain of themes. “By turning elements like the header and footer into block areas, users will have the flexibility to place any sort of content wherever they want,” said Reigstad. “It allows for a lot of creativity! They’ll theoretically be able to click and edit their header in place, or change their sites entire color scheme without needing to jump into an entirely separate interface.”</p>\n\n\n\n<p><strong>Takeaway #2:</strong> block-based themes are happening.</p>\n\n\n\n<h2>The Definition of Block-Based Themes</h2>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>Live Demo Q&A from <a href=\"https://gutenbergtimes.com/theme-templates-full-site-editing-experience-enrique-piqueras/\">The Gutenberg Times</a>.\n\n\n\n<p>After a quick introduction of how the meeting would work, <NAME>, designer at Automattic, filled in the details of how block-based themes work. Currently, such themes are experimental and must be activated by ticking the full-site editing (FSE) checkbox via the Gutenberg plugin’s Experiments settings screen.</p>\n\n\n\n<p>“Once you’ve activated this FSE experiment option, a few major changes will occur in how WordPress behaves,” said Ong. “WordPress will look for HTML templates inside of a block-templates directory of your theme, instead of using the PHP templates, to determine how your site will appear.”</p>\n\n\n\n<p>This was not a new concept to the people present. Most have explored the <a href=\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\">initial documentation for block-based themes</a> over the past two months.</p>\n\n\n\n<p>This part of the meeting was more about providing information. The following are key links for further exploration of full-site editing and block-based themes:</p>\n\n\n\n<ul><li><a href=\"https://github.com/WordPress/gutenberg/projects/35\">Full-Site Editing Project</a></li><li><a href=\"https://github.com/WordPress/gutenberg/issues?utf8=%E2%9C%93&q=label%3A%22New+Block%22+label%3A%22%5BFeature%5D+Full+Site+Editing%22+\">Full-Site Editing Tickets</a></li><li><a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments Repository</a></li><li><a href=\"https://developer.wordpress.org/block-editor/developers/themes/block-based-themes/\">Block-Based Themes Documentation</a></li></ul>\n\n\n\n<h2>Global Styles Are a Part of the Process</h2>\n\n\n\n<img />Example mockup from the primary <a href=\"https://github.com/WordPress/gutenberg/issues/19255\">global styles ticket</a>.\n\n\n\n<p><NAME>, experience designer at Automattic, introduced <a href=\"https://github.com/WordPress/gutenberg/projects/40\">global styles</a>, a feature coming to the Gutenberg plugin and eventually core WordPress. She described global styles as being at the “what goes into the cake” stage, meaning the team is still deciding what the feature will entail.</p>\n\n\n\n<p>“So what are global styles?” Lister began. “In short, it’s style you can apply across your site right there in the browser. Pretty neat! Think of it as a kit full of component tools you can activate and take advantage of. Tried, tested and ready to go. It’s your decorating kit to get your site space just the way you want it.”</p>\n\n\n\n<p>At the moment, the baseline for the “kit” includes text, background, and primary colors in which themes can set the defaults. The baseline would also include typographical settings for changing the font size, scale, and alignment.</p>\n\n\n\n<p>“However, is that enough?” asked Lister. “This is currently a big question. There needs to be exploration on what are common things needed and what needs to be available.”</p>\n\n\n\n<p>Another argument for the biggest question award would be whether global styles are a necessary feature for core WordPress at all. With the possibility that users can directly manipulate templates in the WordPress admin, adding styles to the mix may make some theme authors feel like they will be permanently sitting in the back seat.</p>\n\n\n\n<p>Lister made it clear that global styles should not go too far. “These are tools available in the editor, so addressing what is needed or not is key, over allowing everything and creating a complicated experience,” she said. “A personal point I’m thinking about here is how when I had a crowded art box I could never find that ‘one pencil’ I wanted, we want to avoid that.”</p>\n\n\n\n<p><strong>Takeaway #3:</strong> End-users will likely be able to set global styles from the WordPress admin. For many, this level of power will be a good thing. For theme authors who build hyper-detailed designs, they may be cringing at the thought.</p>\n\n\n\n<h2>Open-Ended Questions Going Forward</h2>\n\n\n\n<p><em>When will block templates and global styles land?</em> The rough timeline for block-based themes is for it to remain experimental through mid-year and have something basic in place as we close 2020. Global styles are likely to land this year, but there is no definite date yet.</p>\n\n\n\n<p>Global styles could easily land in the next several months. It has a tighter scope than themes made of HTML block templates. Given the point that block-based themes are currently at and the unanswered questions about how the system will work, its time frame may be optimistic. The scope touches almost everything in WordPress to some degree, at least anything that ends up on the front end of the site.</p>\n\n\n\n<p>Everything about themes will change. How theme authors approach design will likely move toward styling on the component/block level. Blocks will go into sidebars as widgets are slowly replaced. Even theme options may be a thing of the past. “Personally, I don’t think the customizer will disappear immediately, but I do think it’s clear that many of its current duties won’t be necessary in this Gutenbergy future,” said Reigstad.</p>\n\n\n\n<p>One question on many theme authors’ minds is what sort of quality control they will have over their theme if users are handed so much power to change things. </p>\n\n\n\n<p>One proposal in the meeting was to allow theme authors to lock down certain templates so that users could not mess up the design by moving parts (e.g., a meticulously-crafted header and nav menu template that works across browsers and screen sizes). There is not yet an open ticket for this possibility, but some theme authors will need to have a level of control over this for certain designs to work.</p>\n\n\n\n<p>Ending the meeting on a high note, <NAME>, a representative from the theme review team, gave his final thoughts. “Themes are not going away,” he said. “They may change, completely transform in many ways. The tools we’re currently using and the way we’re currently building themes is not the way themes will be built next year. But they will still exist, and the new way is neither better nor worse. It’s just different. If we embrace that and open up our imagination, there’s lots of amazing things we — as theme authors — can build.”</p>\n\n\n\n<p>I am cautiously optimistic that things will work out in the end. I’m excited about the idea of end-users being given tools to build out the websites of their dreams. I’m concerned, along with many theme authors I have chatted with, about what the role of theme designer will be in a year.</p>\n\n\n\n<p>At the moment, I imagine a major split in types of themes: block-based vs. traditional with perhaps some block elements. Only time will tell whether this becomes an insurmountable rift or whether there is a place for both concepts.</p>\n\n\n\n<p><strong>Takeaway #4:</strong> it’s still far too early to come to any solid conclusions about what the future holds.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 05 Feb 2020 21:08: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:14:\"<NAME>\";s: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:92:\"WPTavern: Guteblock Joins the Block Collection Plugin Arena With an Initial 12 Custom Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96944\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://wptavern.com/guteblock-joins-the-block-collection-plugin-arena-with-an-initial-12-custom-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6780:\"<p>Last week, London-based digital marketing agency Sweans Technologies released <a href=\"https://wordpress.org/plugins/guteblock/\">Guteblock</a>, its new block collection plugin. Currently, the plugin boasts 12 custom blocks. The company plans to add more and has big plans for the plugin’s future.</p>\n\n\n\n<p>While the team earns no points for originality in plugin naming, they are nevertheless throwing their hat into the ring of ever-growing block collection plugins alongside the likes of <a href=\"https://wptavern.com/array-launches-free-gutenberg-ready-atomic-blocks-theme-on-wordpress-org\">Atomic Blocks</a>, <a href=\"https://wptavern.com/coblocks-1-9-5-merges-block-gallery-plugin-into-collection-adds-new-form-block\">CoBlocks</a>, and <a href=\"https://wptavern.com/kioken-blocks-the-new-street-fighter-inspired-block-collection-that-is-taking-aim-at-page-builders\">Kioken Blocks</a>. There is already steep competition in this arena, but there is also a lot of space for growth.</p>\n\n\n\n<p>“WordPress bets high on Gutenberg editor and the block styles,” said <NAME>, CEO of Sweans. “With the introduction of blocks, WordPress allows greater user control over the page-designing process beyond what the theme can handle. For the upcoming block directory, we believe that blocks will be the third integral part of WordPress after plugins and themes.”</p>\n\n\n\n<p>The plugin’s team has put together the following video to show installation and usage examples:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<h2>Plugin Blocks</h2>\n\n\n\n<p>Guteblock is still a little rough around the edges in comparison to more mature block library plugins. Some things were confusing, such as some block color options not using the theme-defined colors. The drop cap block felt like it could have simply been added as extra settings to WordPress’ paragraph block.</p>\n\n\n\n<p>The container block currently does nothing but group elements. At the moment, it is a step down from WordPress’ existing group block. Thomas explained that the team wanted to develop other blocks before fleshing it out. “The main features we will add to the container block are custom background settings, which include color, customizable gradient, an image with parallax effect, video, customizable SVG and other features including shadow, border-radius, etc.,” he said.</p>\n\n\n\n<p>Of its library of 12 blocks, it has some interesting blocks that will come in handy, such as the number box block, which allows users to add columns of numbered boxes. The notification block is also useful for adding a bold warning, note, or similar message.</p>\n\n\n\n<img />Number Box block from the Guteblock plugin.\n\n\n\n<p>The post grid block is one of the nicest blocks in the collection. It lets users create a grid of posts, showcasing the featured image, post title, and optional excerpt. It has settings to control the post count, number of columns, and font sizes.</p>\n\n\n\n<img />Post Grid block from the Guteblock plugin.\n\n\n\n<p>The biggest downside to the post grid block at the moment is that it relies on the <code>post-thumbnail</code> size for featured images, which may make them look stretched and distorted on the front end. In the future, it would help if the user could select their preferred featured image size.</p>\n\n\n\n<p>The plugin includes a social sharing block. Currently, it adds sharing links for Facebook, Twitter, LinkedIn, Pinterest, and Reddit. Each social network can be enabled or disabled individually. The plugin also includes round, square, and modern block styles.</p>\n\n\n\n<img />Social Sharing block from the Guteblock plugin.\n\n\n\n<p>A social sharing block will likely be more useful when WordPress moves toward <a href=\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\">block-based themes</a>. Controlling this at the post level instead of globally is unnecessary work except in some edge cases where a user wants social sharing only on a limited number of posts or pages.</p>\n\n\n\n<p>Thomas believes the team members and author profiles blocks are the most useful blocks. “One of the extremely important features of team members block is that users can highlight one block separately by changing the background color, font color, etc. and drag and drop members to reorganize, he said. “Regarding the author profile block, our block will fetch the author’s name, bio, and image and display there. Users can modify the same if needed.”</p>\n\n\n\n<h2>Upcoming Blocks and a Premium Version</h2>\n\n\n\n<p>At the moment, Guteblock is a free plugin. However, Sweans plans to launch a commercial version in the future. The company did not provide an exact date of launch but said it will happen shortly. It is also unclear what the pricing model will look like.</p>\n\n\n\n<p>“This will be mainly a more customizable plugin with some other blocks such as Amazon link builder, events and shows, a premium slider, etc.,” said Thomas. He stressed that the free version will have at least 34 blocks down the road.</p>\n\n\n\n<p>The plugin’s development team is currently working on two primary blocks to include in the premium edition. “The first block will help Amazon affiliates search for their products in the Amazon catalog, access real-time price and availability information, and effortlessly create links in your posts to products on Amazon.com using the Amazon Product Advertising API,” said Thomas. “The second block is for adding event details in a post or page. You can show the time, date, venue, and the details of the event, and this can be directly added to your desktop/mobile calendar with one click.”</p>\n\n\n\n<p>Along with work toward their commercial version, the development team is preparing to add 16 extra blocks to their free version. This update will include blocks for Google Maps, video, grids, advanced columns, newsletters, pricing tables, and more. They will also provide alternative versions of some core blocks, such as blockquotes and buttons.</p>\n\n\n\n<p>The company plans to dip its toes into the <a href=\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced\">upcoming block directory</a> too. “We are planning to release some very useful and unique blocks into the block directory and will maintain its excellence and effectiveness,” said Thomas. “But, at the same time, we will improve our plugin’s collection to make them stand out from the rest as we are updating them regularly to give the finest user experience.” It will be interesting to see if the block collection plugin or the individual blocks perform better.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Feb 2020 19:53: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:14:\"<NAME>\";s: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:66:\"Post Status: Working on multiple things, and working with partners\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=75833\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://poststatus.com/working-with-business-partners/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:47497:\"<p>A lot of folks in the WordPress economy, whether employed with a side hustle or self-employed, manage multiple things. Also, many of us work with partners, or are interested in partnerships.</p>\n\n\n\n<p>Cory has long worked with partners, and we\'re now running Post Status as partners. Also, we are both working on several projects.</p>\n\n\n\n<p>In this episode of Draft, we talk about how to balance multiple things, how we try and structure our weeks, and some things to consider when working with partners.</p>\n\n\n\n\n\n\n\n<h3>Show links</h3>\n\n\n\n<ul><li><a href=\"https://kolbe.com\">Kolbe</a></li><li><a href=\"https://www.gallup.com/cliftonstrengths/en/strengthsfinder.aspx\">Strengthsfinder</a></li><li><a href=\"https://waitbutwhy.com/2013/11/how-to-beat-procrastination.html\">Wait But Why</a></li></ul>\n\n\n\n<h3>Sponsor: Pagely</h3>\n\n\n\n<p><a href=\"https://pagely.com/\">Pagely</a> offers best-in-class managed WordPress hosting, powered by Amazon\'s Cloud, the Internet’s most reliable infrastructure. Pagely helps big brands scale WordPress. Their new platform <a href=\"https://northstack.com/\">NorthStack</a> is a completely serverless solution for managed application hosting. Thank you to <a href=\"https://pagely.com/\">Pagely</a> for being a Post Status partner!</p>\n\n\n\n<h3>Full Transcript</h3>\n\n\n\n<div class=\"transcript\">\n\n<p>Transcribed by https://otter.ai</p>\n\n<p><strong><NAME> 0:05 </strong><br /> This episode of Post Status Draft is brought to you by Pagely\'s best in class WordPress managed hosting. They help big brands scale. And it\'s really the place you want to be. If your website is a mission-critical site, they have an extremely flexible tech stack to help you accomplish your goals with your website. And they have the three things that they really like to focus on: Number one, flexibility. Number two, scalability. And number three, reliability. What I think occasionally in the years that I\'ve hosted my main website PostStatus.com on Pagely, that\'s what I keep in mind myself — I know I can do the things I want to do. It\'s not overly opinionated. It\'s highly scalable, and it\'s reliable. I never worry about my WordPress going down because it\'s on Pagely. Go to pagely.com to check it out. Thanks so much to Pagely for being a Post Status partner, and welcome to Post Status Draft. My name is <NAME>. I\'m here with my partner for Post Status, <NAME>. Hey, Cory.</p>\n\n\n\n<p><strong>Cory Miller 1:07 </strong><br /> Hey, Brian.</p>\n\n\n\n<p><strong>Brian Krogsgard 1:09 </strong><br /> Alright, official podcast.</p>\n\n\n\n<p>It\'s our second podcast. Every, every trend starts with two, right? Yep. So we have a couple of topics that are highly relevant to us that we want to discuss today. And number one is juggling multiple things. We\'re both doing so so we\'re going to talk about the process of it and some of the things we\'ve tried to instill in our own habits and otherwise. And then the second thing is the process of working with a partner because when juggling several things, often the choice would be to have a partner in crime as you do. So obviously, this is highly relative to our, our own situations, with post status and then each of us are, you know, Post Status as our common plate but we each have other plates that were spinning So that\'s what we want to discuss and iron out today. You know, I\'m thinking of who\'s our listener who\'s, who\'s listening to this and thinking, I\'m interested. And you know, one type of person sticks out to me in particular, which is a, like a plugin or product developer, someone that\'s got a WordPress product and maybe it\'s not their full-time gig yet or maybe they\'re balancing the product side with doing some freelance work. Why don\'t we jump back to the first time you had to start balancing something and go from there so like, what have you learned since you you know since you started doing full-time WordPress back in 2008 or so? Was I themes paying the bills right out of the gate, or how did that work?</p>\n\n\n\n<p><strong>Cory Miller 2:49 </strong><br /> Yeah, I think it was paying the bills right out the gate, but I\'ve kind of notorious mine. People that have worked with me to be a plate spinner anyway, I kind of relish In the place multiple things keep me engaged. And so, but I woke up you know, couple weeks ago post that this is one of five projects I\'ve got going right now and back into being a plate spinner again but and iThemes Yeah, I spend a lot of plates in the first year, of course, we had full time, you know, I had money to be able to kind of get started and then we try to get revenue in the first month as best we could and be self-sustainable. But uh, for that year, I tried to only spend one plate and that was just I themes, but on the project plate for products, it was just trying to iterate on themes and stuff, but the year, a year or two prior, I was doing the same thing we\'re doing now which is balancing a full-time gig with stuff on the side, in my freelance business just happened to be, you know, it worked out but I was also I don\'t know, 13-14 years younger and I can power through until midnight or one now it\'s like I\'m going to bed at night.</p>\n\n\n\n<p><strong><NAME> 4:07 </strong><br /> Yeah, definitely makes a difference I\'ve said on this podcast and elsewhere many times that my I used to call it my tended to time. So 10 pm to 2 am was my window where typically my wife was in bed before I had kids. And I was a night owl, so I would get stuff done. And that was how I maintained my side hustles while I had full-time jobs, and I can\'t do that anymore, like just physically, my I can\'t do that now. And, you know, if I have to get some stuff done late at night, I might be able to put in an hour or so. But I run out of steam like if I\'m going to do something else. It has to be something replenishing or balancing my work efforts, like reading a book or something that\'s not by, you know, fingers to keyboard type of activity.</p>\n\n\n\n<p><strong><NAME> 4:59 </strong><br /> I know a lot I know most probably of our community can relate to all this as burning the midnight oil, so to speak. And then now as I\'ve gotten older it\'s like, it\'s just not going to work. And you and I both have young kids. So when I get home, it\'s hard to like, I can\'t pull up my computer one, I\'ve got a kid sitting in my lap. And, you know, wanting to know what I\'m dead. I\'m like, I\'m trying to get something done.</p>\n\n\n\n<p><strong><NAME> 5:25 </strong><br /> If I\'m, if my two-year-old is here, he will literally just make every effort to just slam the spacebar. He\'s like, that\'s the biggest thing that\'s on that board that you, you know, put your fingers on and he\'s just like, I gotta get on that, you know. I can\'t, I can\'t really work with them awake. What that means for us is that we\'re juggling things and we\'re not like inventing new hours in the day where we\'re figuring out how do we juggle within our standard, our standard day. So how do you physically process this and terms of playing And execution?</p>\n\n\n\n<p><strong><NAME> 6:03 </strong><br /> Gosh, you know, I put the five projects like in December, I thought I have four, this is all one and then something happened and I was like, okay, there\'s a fifth can\'t turn down. And I realized real quickly like, okay, I don\'t want to get into old bad ruts. I knew I had to get organized new posters is a priority for me, for us, for our family, too. And I\'ve got a lot of other projects kind of spinning, but I had to get really organized and go, okay, you know, I\'m going to need help at some point. So I actually hired a virtual assistant. A couple of weeks ago, I don\'t even know if I told you that run. But yeah, you mentioned to me Yeah. How to virtual assistant because I had a longtime executive assistant at it. Named Patty color, Painkiller, excuse kill. And I was like, I\'ve got to find figure that out. So I hired a virtual assistant and starting to delegate trying to delegate things to her to help me chase down some things but there\'s so much like, she can\'t go to the bank and sign, you know, a bank account for me. So I\'m trying to be strategic about it. And then now you know you and I both said we\'re in a different stage now. So we got young kids, work, work-life balance, if that\'s even a thing work-life alignment is a thing for me. But I don\'t know if I want to be working. After six o\'clock, I need to devote that time to my kiddos, and I know you do too. So I\'ve got to really prioritize I think Jason freed said it best is in one of his books or podcasts or something a long time ago that constraints particularly time constraints are such a good thing. I\'m like, Yes, absolutely. You know, when I saw those names and people, you know, have their opinions about where they think my financial future is. But honestly, when everything is an option, everything sucks. And I think constraints. I can\'t believe I\'m saying this, but constraints are good. In certain situations, everything is an option. And I\'ve kind of taken the mindset from Jason freed that, you know, having kids is good because it gives me some boundaries, or at least that need to be setting boundaries to not repeat bad habits that I did over 10 years. And I think,</p>\n\n\n\n<p><strong><NAME> 8:19 </strong><br /> yeah, so you\'re saying constraints in terms of what you choose to work on. And that\'s interesting. For me, I kind of know what I\'m working on now. Like, I made those decisions. And, you know, I\'m contracting a significant chunk of my week with sky verge, working the majority of the rest of that with post status, and then I have this one thing, and this is where I really had to make my biggest decision, which is on the like, crypto side of things where I had huge community following and stuff. I had to say, I\'m going to establish scope on what\'s achievable within that project, and really limit myself self to, to what I know I can do well and efficiently. So for that, it really meant narrowing it all the way down to just like a podcast. So I do a podcast in that space. And now I know like, I\'m not going to spend more than, you know, x hours in the week on that because I\'ve established scope for that project. And then it\'s deciding, okay, well, where, where\'s the differentiator between, you know, being productive with my time and relying on teammates, like in our scenario, that was one of the big things selling half a post at us. It\'s not just Oh, great. There\'s a little bit of money now that I get to bring in which I\'m obviously thankful for. But it\'s also to say, Okay, if I treat this as part-time and you treat this as part-time, we have two part-time contractors, will you put all four of us together we\'re combining multiple people\'s skills, and the end result is better than me as a full time or upon myself could have ever done in the first place. So I feel like That\'s a really effective use of part-time efforts and allows me to juggle multiple things and in my opinion, put out a better product on the thing that I was trying to do alone. So that was a big part of it for me is defining the scope and identifying how can I make something better while spending less time on it?</p>\n\n\n\n<p><strong><NAME> 10:22 </strong><br /> Yeah, I think what has been for me is prioritization of like, I can\'t, I can\'t goof off. I\'ve been here in my little office from, you know, 830 to five roughly and it\'s straight through and it\'s good. It\'s engaging senior wanted to level off at some point. But there is a focusing power, like I\'ve got to be very good about prioritizing what my time is, particularly with juggling some projects like you do. I\'m thankful that our partnership we\'re in the same time zone and roughly on the same hours, work hours. So that\'s really good. My partner, <NAME>, another project. She\'s in Eastern Time Zone. I always have to kind of convert a little bit on that. So,</p>\n\n\n\n<p><strong><NAME> 11:04 </strong><br /> and then really hard for our friends who have partners or whatnot that are six hours or 10 hours apart, that the offset that you create in your communication cycle forces your projects to go slower.</p>\n\n\n\n<p><strong><NAME> 11:16 </strong><br /> We were very deliberate about when we took on our Portugal team and iThemes and because they were six hours ahead of us, and knowing there\'s going to be a lag and man that just slows things down when you\'re trying to ship product. So it\'s, it\'s, you know, I\'m definitely thankful we\'re in the same time zone and even Rebecca and I are just an hour apart, but still, it\'s like she\'s already started her day, you know, I might get an email at 630 in the morning, and I\'m just kind of getting around and it\'s like, oh, man, her days getting going now.</p>\n\n\n\n<p><strong><NAME> 11:47 </strong><br /> Yeah, she\'s full force. I\'m ready.</p>\n\n\n\n<p><strong><NAME> 11:48 </strong><br /> Yeah. So but again, I think it is the constraint is the prioritization. Like today I just thought, Okay, well, you know, one thing I\'ve done is have specific For the first time, probably in my career in about 12 years, I am blocking time out of my, my calendar for recurring meetings to that never done before, but I have to do it and I have to get better at time prioritization to and so even getting the newsletter out today, for instance, I was like, Okay, I got to think about this better because I need to block it out a time, reverse engineer, whatever, we\'re going to get the newsletter out, and then block out time when you guys aren\'t waiting on me for something. So we make sure you get out a good product.</p>\n\n\n\n<p><NAME> 12:31 <br /> Yeah. Discipline it. Yeah, it certainly is. And the first person that I saw doing this really effectively They showed me their calendar, they talked to me about how they balance was actually cited baki and, you know, a lot of our listeners will know through awesome motive. He\'s got his hands in five different products at any given time, and incredible amounts of other businesses as well like he does it to an extremely He\'s a robot. He\'s a yes. But he is a time blocking master like I, he showed me his calendar and it\'s colour-coordinated, it\'s day by day. And it\'s broken into, you know, a two hour or four-hour block, 30-minute block. And he\'s got every day of every week assigned to a thing. And it\'s like, here\'s a half-day that goes towards working with Jared on WP forums or a half-day working towards OptinMonster. You know, it may change depending on week by week but he knows before he starts this week, essentially where he\'s spending the every like work hour of that week, he\'s designed his workouts and he\'s designed his, you know, it\'s like, if there\'s family time or travel during the normal workweek like it\'s built-in there too. And I was inspired by that I could not mimic it like I tried it for a little bit and it was too structured for my discipline like his discipline level is just beyond mine. Yeah. But it did give me a framework for saying, Okay, well I have my focus, like Mondays we have a lot of meetings with sky verge. And that\'s like, basically a sky verge only day aside, aside from, if something that really needs urgency from post status comes along. And then it just allows me to structure my days and say, This is my big thing today. It\'s my big thing this other day, this is where I want the majority of my time in my hour spent and I\'ve actually started tracking my hours. And I\'ve been evolving that I\'ve always hated time tracking any job where they like, you know, focused on that. I was always like, Look, I don\'t want to this, you know, like, negotiated my way out of it. And now, I\'m embracing it, but it\'s more for my personal accountability than anything else because I want to know, like, Okay, well, it was I actually spending these hours of these days. On the things that I planned, of course, it helps me like for, you know, for a contract job that helps if you\'re paid hourly. But even for something like what we\'re doing, I had a partnership line item on my time tracker. And I was tracking generally, like, if we got sidetracked, you know, or like, we had a meeting, I would track it. And then if we had, you know, something, especially where it was in a zone that was supposed to be geared towards something else, I wanted to know, like, how far off of my routine Am I getting? And it\'s this intro week, accountability process. So you kind of have an idea of like, oh, man, I\'ve spent more hours over here and I need to be over there. And it\'s been really good accountability for me to better audit my time so that I can then more effectively move forward and be knowledgeable about the way I\'m approaching it. And I\'m not succeeding, like if I say, Okay, well, I want to spend 25 hours over here. 15 over here and two over there like it doesn\'t always work that way. But it allows me to have a target and audit my effectiveness against that target and you really learn a lot when you start doing that.</p>\n\n\n\n<p><strong><NAME> 16:15 </strong><br /> Yeah, I go back to the side comment and I\'m joking when I say robot kit but his worth it work ethic i is unparalleled and never seen anything like it maybe my dad who\'s now should be retired for the second time and working 60 hours a week-long gas industry but said is a maniac. But he\'s also I think it the thought about that was like it\'s how we\'re all kind of wired, like, I\'ve had so many people over the years they know I juggle things, spin plates and go Why would you do that? Like tell them wired I mean, and I used to go Why do you only have one project that sounds boring. And so we had this telephone realize to each his own like wired in different ways and have a lot to do that, having said that, you said the word discipline, it\'s some it\'s a word I\'ve been trying to kind of reintroduce into my life. Consistency is another big word. So I\'ve gotten more organized and, and want to line things up where I\'m not dropping balls for sure. And I\'m mixing metaphors here. But, you know, I play doesn\'t drop. But they\'re all important to me. They\'re engaging and I think that makes me me, you know, if we were all carbon copy of each other, it\'d be a bland world and, and all that. So I think to each his own for sure. But I think you\'re talking about something we\'re talking about something that a lot of people go through, they want to strike out on the entrepreneurial adventure, and but they\'re balancing a day job and then I can potentially family. I have a couple of business friends here in Oklahoma City that their entrepreneur story started with. I started my business when my child was six months old. Like, I can\'t imagine that you know, I kind of say, I think it was in kindergarten when we had our first kids had our kids so like, it was to the point where that one that little baby had kind of graduated and was under adult supervision. And then I could kind of turn my time. Now on this season to toe, it\'s just very drastically different. And so, man, I just admire the stories of people that juggle so much, particularly with family while starting this crazy job. This crazy gig we have come entrepreneurship. I, you know, if entrepreneurship was easy, by the way, everybody would do it. Because think about the freedom, the lifestyle you\'re having to live as an entrepreneur, but it comes with a heavy cost. Just talking to a dear friend of mine that I\'ve known for a long time entrepreneur and comparing stories and him saying he\'s had a rough couple of years and going in my part was to say to encourage to go I\'m going to be in your seat at some point. Mukherjee that like this thing, this thing we do called entrepreneurship is just not meant for everybody. And it\'s just a tough thing, but it\'s really thrilling for me to come would say, join you in something that\'s already started, by the way. So that makes this project. They\'re all exciting to me. But this is different in that I can help take something really, really good and make it even better. Where starting new projects. Oh, that\'s that\'s a ton of work, man.</p>\n\n\n\n<p>There\'s a different kind of grind. And they\'re like, what did two years of post as before the club, you know? Yeah, well, that grind of getting the thing off the ground like business takes time.</p>\n\n\n\n<p><strong><NAME> 19:45 </strong><br /> One of the things that I think plays into this idea of structure and being able to juggle different things, a lot of it does come down to personality. And for me, you know, I\'ve always achieved a lot So it\'s not it\'s there\'s a difference to me between what I\'m about to describe and like if it\'s laziness or something for me, it\'s not laziness. I have no threat of saying, Oh, I work from home or I don\'t have a, you know, nine to five job. So I\'m going to sit on the couch at my house. That\'s never my personality. But I do procrastinate in my own way, and wait, but why.com is a great website that it\'s called, has a long series from 2013 called how procrastinators procrastinate, and it\'s like the brain of a procrastinator. And what he really breaks it down to is this intimidation of long tasks that makes a procrastinator put that off, and how you can kind of beat that and how to beat procrastination or the way he describes it is he says effective planning turns a daunting item, say like writing a book or launching a website or something big and turning it into a series of small clear, manageable tasks. When you do that, you\'re making something that sounds big he calls he says a remarkable glorious achievement is just what a long series of unremarkable and glorious tasks looks like from far away. So if you break things down, if you have this type of mentality where you can see the short, short term finish line, and turn it into a to-do list or you know a task, then that\'s no big deal. It\'s like, okay, boom, knock out that test, boom, knocked down that task. And then all of a sudden, you\'ve done lots of things that add up to be this really big, more glorious thing of accomplishing your goal. And I\'ve found that I have got to structure my day to day that way. And I\'ve really embraced note-taking but it\'s kind of a hybrid between notetaking and to-do list stuff, where I take notes of like, okay, what\'s my, what\'s my main jam, like what I have to capture today? Sometimes it\'s an idea and some times it\'s deliverable, and then turning it into these to-do lists that I accomplish inside that week. And then you add that in weekend and week out and hitting those to-do items. That\'s when the real changes and effects start to take place for me.</p>\n\n\n\n<p><strong><NAME> 22:14 </strong><br /> Yeah, well, no, I completed my master\'s degree. When I was in my late 20s. I went back to school, and the staff there at that college in the adult program said, How do you eat an elephant? One bite at a time. And, you know, I\'ve used that a lot with teams, helping coach teams that I\'ve led, and others is this big task that you have breaking it up into small parts. And then I think there\'s something to be said of, I think it\'s James clear. The author, prolific blogger that talks about, you know, consistency, like if you\'re going to write a best selling book, it\'s, you know, break it down if it\'s 50,000 words is 500 words a day. For X amount of months kind of thing. Now, I don\'t know what to believe I have that discipline in me to show up every day and just write 500 words a day. And but I believe that if you do that you will show up, you know, an X amount of months with something. And this is the harder pill for me to swallow sometimes, just again, how I\'m wired. I\'m not trying to make excuses, but just saying it\'s, it\'s not an easy task. Some people make it look easy, but the reality is, you\'re probably wired in a different way.</p>\n\n\n\n<p><strong><NAME> 23:30 </strong><br /> One of the things I learned from Pagely was that the price of hosting or the expensive hosting is really a relative thing. What Pagely might be able to do for $1,000 might end up costing three to 5000. At hosts that don\'t do these large setups all the time. I called our chatted rather with the CEO of Pagely, <NAME>, several years ago and said, Hey, we\'re comparing options between Pagely and some of the other options in the market for really high scale websites. And what I realized was that on an apples-to-apples comparison, I was getting more with Pagely for less money. Now granted, we\'re talking about hosting for $1,000 a month, but so it\'s expensive for a website. But when a website was being quoted from other providers for $3,000 Plus, I was really getting excellent service from Pagely, for the price. If you have websites where you really rely on your website provider, being reliable, have excellent human support. I can\'t remember the last time it took longer than I don\'t know an hour for like a real answer to a support question, not an auto-answer, but someone that was, you know, taking a technical look at my issue. And getting back to me for about some question. I have almost always a question of my own fault. Not to do with my actual hosting plan, but where I just needed help. Pagely has plans for everybody. Whether it\'s that thousand dollar type of VPS or $200 for five sites, that\'s what their small VPS instance sets up for you. It\'s all built on AWS, they\'ve really fine-tuned it really, really well over the years. It\'s an excellent service go to Pagely.com to try Pagely today, let a little post that essentially. And they\'ve been a longtime partner, good friends of the show, and Post Status, and I can\'t recommend them enough. I trust my own websites to Pagely, go to Pagely.com. Thanks to Pagely for being a Post Status partner.</p>\n\n\n<p>One of the things you had me do when we were just trying to figure out would we make good partners was an assessment through Colby, calm kayo LP calm, and that was stuck with me. You had me do a couple of them which I thought was fun across the board. And just the fact that you wanted me to do that told me a lot about the type of partner you could be you know, like the way your mind works first. is mine. The Colby one I thought was interesting because it gave me an understanding of how I work. You have an understanding of how you work based on your assessment profile. And then it tells you Okay, well because you have this and you have this, you YouTube may have conflict in this way. Or you may have a really nice jelling in this way, and why you talk about how that kind of fits into this. So if I\'m talking about my, I need these, you know, big pictures fine. But then if you just say, take the big picture, go write a book, I\'m in trouble. But if you say take the big picture and go write some like thousand-word articles on like, okay, I can accomplish this. So, take this assessment, how you blend that and turn it into an effective partnership.</p>\n\n\n\n<p><strong><NAME> 26:46 </strong><br /> So my belief is whether it\'s a team or a partner is to leverage your their unique strengths and experiences that I probably don\'t have or if we overlap, there\'s unique this in there and so it\'s Specifically with our partnership, and we did these discovery tools, and I think was two years strengthsfinder from Gallup was the one, we can put these in the show notes. It gives you your top five strengths. And then so let me unpack that. So Strengths Finder is one that I had to do because I kind of wanted to see verify probably what I already thought about what your unique strengths were and what you believe that they are. And real quickly with that, I can go there\'s overlap, but there are differences. And that\'s why I like one of yours, I think is analytical. And that shines brightly, everything post at us. Like I told you years ago, what I always found value was your insight and analysis of everything that was breaking. Like I wanted. I might not agree with you every single time but I was like, No, I want a different perspective. And that\'s something I knew ahead of time, but it helped me just kind of really identify that. So the street corner does that with teams with partnerships, whatever. And by the way, that joke was I thought you\'re gonna say this But when my wife and I first met I had to do these two and she was like what the heck you\'re you have to take a test today you to see if I\'m, you know, married. Now she\'s a big fan. But Colby is really interesting because it\'s how you instinctively take action. And we started with Strengths Finder and then we evolved into Colby because I wanted to see how you instinctively took action. So this four modes factfinder, which is, you know, a high fat fighter which you happen to be is very I mean, it lends to everything you\'ve done, which is analytical research, I mean, dive deep into an area of a middle road factor under which is I want the essential truth. And the three other areas are quickstart. Most entrepreneurs, many entrepreneurs, I should say are quickstarts Hi, quickstarts. I\'m a high quickstart The other one is the blue one, which is follow through and it\'s not like you can\'t ever fall through but it\'s step by step. mode of action. If you have a problem, I\'m going to figure out step one, step two, step three, step four, the yellow is implementation. People behind that are the ones like mad Danner who are amazing with their hands and like woodworking and different things or whatever, like very high implementers, are. And then we also want to focus found from you is that we had, we had compatible things where I knew we could work really well together, but I knew there was also willing sounds like you\'re a medium quickstart which you and I could ideate all day and not get anything done. So that was the thing we talked about, you already recognized it. factfinder is great because we\'re kind of in that mode, where we\'re not in what Colby calls conflict, but we\'re low in the blue, which is step-by-step plan. We\'re kind of find the shortcuts, bandaid it together, put it together and do that. So we talked about that actively. You already recognize that but I helped us talk through, okay, our similarities can also be our weaknesses. We need someone to kind of help us. And I know David and Dan really help us with some of those things that we might go, man, let us we\'ll do it at the last minute.</p>\n\n\n\n<p><strong><NAME> 30:10 </strong><br /> And just being cognizant of that, as we go about our day to day in partnership, you know, it allows me to say, Okay, I need to think I need to be sure and know, like, here\'s our plan, we came up with our plan, we\'ve got these ideas and the follow-through component or the, you know, the take it to execution side of things. It\'s like, I have to make sure that we both understand what to do, where to go and bring people along to help us accomplish that. And so far, I think that\'s been effective. And sometimes that\'s tooling you know like it\'s one thing if we have our all our conversations and slack and we have these pages of notes, in our note keeping apps and we, you know, collect our thoughts, but then it\'s another to say, Okay, well, let\'s put it on a schedule and let\'s set a date for When we\'re going to launch this thing, and let\'s have our plan of action for, you know, who\'s responsible for what, and put deadlines on that across the way. And to me that tooling side of things, which could be as simple as base camp or whatever, is my way of introducing accountability to an area where we both identified kind of on the same side of the spectrum, which is, in that in that particular instance, it\'s kind of the kind where it\'s like, ours has its own benefits, like the way we sit. But you really need that person that\'s like, the big long spreadsheet, project manager, very type a type of person to help rein us in, when we could end up down a whole bunch of different rabbit holes. You know, Id aiding the next two years of what post status is going to be and it\'s like, well, someone\'s got to do what we\'re going to do in the next two weeks or the next two months and yeah, so that gives us that accountability there.</p>\n\n\n\n<p><strong><NAME> 31:57 </strong><br /> Well, we\'re supposed to record this podcast six hours. ago, I think. And we had, you know, part of that was we had thought we still were so new in our partnership and trying to get some things done at post that is that we need to have the time. But we had deliberately two weeks ago, set this date to record and then now we\'re six hours later recording it. But I know we\'ll get to those types of things. But it\'s that, you know, we could wear that. I think you and I are kind of wired to be the squirrel. You know, movie idea. Okay, let\'s face it. We\'ve talked about that. And we both have, I think helped each other rein it in on that, like, hold on. This is first that second, this third, right? Yep, yep. Yep. Let\'s go back to that because it\'s really fun to dream. It\'s really fun to ideate and think about cool stuff, especially as quickstarts and the Colby kind of mantra. So, but there needs to be somebody that also says, Okay, let\'s stop dreaming now. Let\'s go do</p>\n\n\n\n<p><strong><NAME> 32:58 </strong><br /> Yeah, and I think been proud of how we\'ve so far been able to do that. And we realize it\'s important. And I think maybe one of the things that has allowed us to do it is, when we first started the partnership, we, and you really helped me outline this. And it\'s like, what are our goals? For the business for the partnership, where we want to be a year, two years and three years? And therefore we say, Okay, if this thing is effective in January next January, what have we accomplished? And we said, okay, we want you know, certain things, it\'s a number of subscribers or it\'s a number of page views or a number of members or a degree of like member satisfaction, like things that you want to strike and then it\'s how do you plan to accomplish that and keep that as your goal, how many dollars you need to make a day if your dollar goal for the year is this? And that was really helpful for me to put all that in context.</p>\n\n\n\n<p><strong><NAME> 34:00 </strong><br /> So one other thing I did, I think I told you this either as I\'ve had a coach for a year and a half now a personal coach. Fantastic. name is Kelly. We came into this and she was like, Okay, got five projects, what do you need for me? And I was like, here\'s what I think I need me to go weekly. And what I don\'t want to do, my virtual assistant helps me take certain tasks that I need to just create my time, you know, to do other things. My coach is okay, here\'s the deal. I\'m highly invested in my time, my money, my energy and all these projects, and they\'ve got to make progress. I\'ve got to move the needle. That is the most impactful things. So what we do now is each week we do a 30-minute laser call. And I talked to the big issues, I think through the projects, and I go, can we post those this week? We need this. And what and she helps me get clarity on that before by the way. I have my partner calls like with you. We knew our calls on Friday to do my call with Rebecca on Wednesday. My partner Jeff on Monday. So I\'m like, man, there\'s too much stuff going on, I\'ve got to have that kind of clarity. And she\'s helped me rehearse and get ready for because like, for instance, I try hard not to ping you. Because I know there\'s a bucket of time, there\'s a bucket of energy that probably is owned mostly by Erica and your two kiddos. And I want to be really careful what I withdraw from that. So. So she\'s helped me go in, I looked over the last 30 days. So every week is a 30-minute call to kind of get ready and make sure I\'m on task for all the projects. The last meeting, which I just had this week, is a one hour kind of look back over the last 30 days, and then they look forward to next Thursday. So make sure I\'m keeping progress with all the critical projects going on. And that\'s just another level of optimizing for. There\'s a lot on the line for me. There\'s a lot of love for you and my other partners and so I want to make sure we\'re focused and making the most progress, we can For all of these so that we can say, high five and go, this is this, these were the best times. What resonated with me for you, Brian is you said for years, you know, Kevin did it by yourself, I Exodus ran into your burnout that post like it was the first sentence burned out. And I was like me and I can resonate with that. And one of the compelling things that he said to me as I said, I don\'t want to do this alone. Again, I could, I could sell this, I could do this and just leave. But I just really don\'t want to do it alone. And that I told you then resonates with a lot of social entrepreneurs. It\'s tough doing it by yourself. I had aside amazing psychic command, enter and I think to help me not do it alone. And then a group of us were friends, WordPress, none of WordPress helped me over the years. But man, that\'s something that you can mention too, is how a partner or a team or somebody that can come alongside you is so powerful.</p>\n\n\n\n<p><strong><NAME> 36:55 </strong><br /> Yeah, there\'s two things there applies to both of these. I guess. A lot of people, you know, they dream when they\'re in a normal nine to five job. They\'re like, Okay, well, I have so much more upside potential or so much more opportunity for freedom and all these things if I go out on my, on my own, and work on this thing and turn my hobby into my business or turn my side gig into a full-time gig, and I think it takes several years potentially, of doing that before you oftentimes for and maybe it\'s for certain personality types that then they say, Okay, this has some real benefits, but there are some real drawdowns to that I need to consider and for me, okay, I love the freedom. I love the upside potential. But at the same time, I liked working with people and I liked bouncing things off teammates, and that was an important thing for me to figure out how can I recapture and I think a lot of people that might be listening to this talking about juggling multiple things, working with a partner, maybe they\'ve all kind of landed on that. So now, there\'s this kind of fundamental balance there, where when you\'re juggling multiple things, none of them is necessarily such a security blanket or a safety that is the same as a full-time job. So this balance is how do you spend time in the places where you can make money, yet none of them are probably sufficient relative to what you could make it a full-time job. Like, say, if you were making $100,000 and a full-time job while your main side hustle, it, maybe it\'s making $50,000 and your other side hustles making, you know, another $50,000? Well, you\'re making $100,000 total, but it requires this balance between the two of them. In our situation, you have partners so like my needs from the business, do they align well with your needs from the business from a revenue standpoint, there\'s so much balance and inertia. So you have to balance like, okay, I want to work with people. I want to have this freedom. But there\'s all this balance. that\'s required there and I would be curious if you have any kind of final tips to find the sweet spot while you\'re doing that.</p>\n\n\n\n<p><strong><NAME> 39:09 </strong><br /> Yeah, so you know for years I said it\'s a sidekick it\'s it\'s the <NAME>, it\'s someone that just is doesn\'t have as has compatible strings to you. And but you\'re not strong in the same area where you can kind of divide and conquer. And so I\'ve honestly thought about it as a work spouse, you know, to Bandy that. That phrase around a little bit, but I mean, there\'s an element to that work spouse, like having someone you can confide in. And I bet you there are entrepreneurs and founders solopreneurs listening to this today. That is like, in the spot you were and by the way, when I struck out, it\'s been a year ago this week, I\'m back on my own. I didn\'t want to do it alone. I wanted to do with other people, and I found some great people. One of them being you and Do it together and collaborate. So, but I think, you know, somebody goes, why don\'t we give away equity I get that then finally struggle psychic, a workout spouse that feels ownership that you could give some rewards if they need it. But find that person that is the end to your Yang. We missed that. And then secondarily, I\'ll tell you, I know the work psychic work spouse type thing is hard. And the partnership conversation is hard. But I\'ll tell you and this is something you\'re not been talking about. Small groups of like-minded people on the same path with the same values have been life-saving and changing for me. So I\'ve been in one group for nine years now. 10 years almost. I\'ve helped start to more. We\'re talking about trying to get that kind of group. people in the room to rub elbows that get it they understand the story. So I always get the joke. Most of us don\'t know. Your parents don\'t know what they we do. Living Dead still thinks I just upgrade the computer somehow. But you know, having a group of people that just get you, know you, not talk you\'ve got some dear friends you lean on, you meet with weekly even as the same can be those kinds of compatriots that like, you can let your guard down and, and share like today sucks. And I\'ve tried to be that for people and also clean to those that are like vulnerable and genuine and authentic and are willing to let the guard down the shields down, take the mask off all that kind of stuff and go Hey, not everything is rosy. So, you know the two things is one is finding someone in the business that can work with it, that just gets it. That\'s a hard one I know. Second is to find a group of people that are on the same path as you then share life and go deep and it doesn\'t always have to be personal or a business. It can be personal, some of the most endearing moments I\'ve had with my friends. That I count as brothers and sisters. I mean, like they are family to me. If something were to happen to me, they\'d be the first people at my house scene if Lindsay and the kids were okay. But finding that group of people and you and I\'ve been talking about this, how do we do that through post tennis community to pull in our amazing community of founders, entrepreneurs, and give that type of like, being in the room together and sharing that stuff that it\'s the high fives, and it\'s the hugs that you need when things are just bad. So that\'d be my two takeaways.</p>\n\n\n\n<p><strong><NAME> 42:35 </strong><br /> How about yourself? That\'s really good on and I think that\'s, I\'ll leave it there from a partner perspective. I\'ll jump back to the juggling things and just get my final. My final comparison maybe so I\'m thinking, Okay, well for you know, somebody that\'s somewhat technical or works in the web industry at minimum. All right. So if I gave you the challenge to say, hey, this website\'s slow, we need to speed it up. Well, if the first thing you would want to know is, where is it slow? Why\'s that slow and cut audit that process. And I think that that was the biggest thing that I had to come to the terms with, which was if I\'m going to juggle multiple things I need to know, where\'s my time going? I don\'t know how many times I had these weeks where the week goes by much less the day and it\'s like, okay, I had stuff I wanted to accomplish. I know I didn\'t accomplish everything on my list. But when I look back, I felt busy. But the results weren\'t there. What happened? And that is dangerous. Because you\'re not auditing. You\'re not knowing where your energy actually went. So that you can iterate and improve. It doesn\'t mean you have to be perfect. It doesn\'t mean you have to have like every hour tracked. But I think if you\'re going to make your website faster and more efficient, the first thing to do is to identify what are the processes that are slowing it down right now what is like what are the pivot points The what are the bottlenecks? Where\'s my time being consumed? And where, when I look at that, if I say I\'m spending 10 hours a week on phone calls, or if I\'m spending 10 hours a week, you know, in support, okay, what\'s the value of the time that I\'m spending there? And the best thing to do in juggling those multiple things is to try to find the difference makers in that time and spend more time on the difference makers and find out how to bring someone else in a contract or the or offload it to your partner if they\'re really good at it, and getting them to do those things. You\'ve told me I don\'t even know how many times since, you know, we started talking about talks about you know, managing support, which is pretty light with post status, but you were like, I don\'t want you in support, like get out of there. And I\'m like, okay, that\'s okay, that makes sense. But we still need to take care of support, but it starts by identifying how much time am I spending in that type of communication and Therefore, how can I effectively bring someone else on to take that task or put it in a certain bucket like I\'m going to do support every Monday and every Thursday or something like that. And that way, it\'s not kind of floating along with me the whole time. And that\'s what I found most effective in terms of auditing, and improving my personal processes to be able to juggle multiple things, which is an ongoing battle and ongoing struggle, but one that I\'ve certainly seen progress on, especially since I started self-auditing where I was spending my time</p>\n\n\n\n<p><strong><NAME> 45:38 </strong><br /> Yeah, that\'s really good. In my calendar if it\'s on my calendar, so I can get done. I don\'t do the time blocking like said this, but for mostly, but man I live by that calendar and I\'ve had to start trying to bracket time for certain things. But I think the audit is so good. Always be optimizing. You know, because again, We, you know, in this project have very limited time and energy. And so we put our best into it, but I want to prioritize that time and then optimize for bugs like, Okay, are we spend too much time here too. We, you know, and I think that kind of review helps us make good decisions to and going, Okay, this is the new here. This is the morning side, like the dashboard says, overheat or something, you know, we can go in and go Okay, well, how do we collaboratively figure this out?</p>\n\n\n\n<p><strong><NAME> 46:31 </strong><br /> Yeah. Well, let\'s optimize this podcast a bit and leave it there. Thanks, everybody, for joining us. Thanks, Corey, for chatting with me. This was obviously relevant for us and these are always self-reflective, we\'ll be able to think back on what we said here and how we can do better from here. I hope that it helps you as well. I hope everybody has a great week and we go to post that comm slash club and sign up if you haven\'t already. Corey and I spent the majority of our time figuring out how to make the club better and more appealing to people that are already members and would consider being members. So if you\'re not opposed to as club member, you\'re going to miss out. So go to PostStatus.com/Club and sign up and we\'ll talk to you soon. Bye-bye.</p>\n\n<p>Transcribed by https://otter.ai</p>\n\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 04 Feb 2020 01:13: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:15:\"<NAME>\";s: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:86:\"WPTavern: Ahmad Awais Launches Script to Automatically Deploy WordPress Plugin Updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96942\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:97:\"https://wptavern.com/ahmad-awais-launches-script-to-automatically-deploy-wordpress-plugin-updates\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6426:\"<p>Today, <NAME> <a href=\"https://github.com/ahmadawais/wp-continuous-deployment\">launched WP Continuous Deployment</a>, a continuous deployment pipeline for updating plugins hosted on WordPress.org via GitHub actions. It is a Node.js-based CLI script that simplifies the process of keeping plugins updated. Developers only need to type out a single line in their terminal or command prompt. Other than setting up a couple of secret keys on GitHub, the script handles everything in just a few moments.</p>\n\n\n\n<p>“We live in the age of agile workflows,” wrote Awais in the <a href=\"https://ahmadawais.com/wp-continuous-deployment/\">project announcement</a>. “Developers only want to <code>git commit && git push</code> and expect their products to be deployed globally…It’s been a minute since I worked on a WordPress project, but for the last year or so, I’ve been fantasizing about a git-based plugin deployments workflow that will allow me to get away from those old SVN repositories finally.”</p>\n\n\n\n<p>On November 14, GitHub <a href=\"https://github.blog/2019-11-14-powering-community-led-innovation-with-github-actions/\">announced it was rolling out GitHub Actions</a>. Actions are a way for developers to automate workflows from their Git repositories. Developers can share, fork, and reuse them across projects. A few days later, <a href=\"https://wptavern.com/10up-releases-github-actions-for-simplifying-wordpress-plugin-deployment\">10up launched two GitHub actions</a> for WordPress plugin developers. These Actions are the basis for WP Continuous Deployment.</p>\n\n\n\n<p>10up’s <a href=\"https://github.com/marketplace/actions/wordpress-plugin-deploy\">WordPress Plugin Deploy</a> Action handles deploying plugin updates directly to the WordPress plugin directory. The <a href=\"https://github.com/marketplace/actions/wordpress-plugin-readme-assets-update\">WordPress.org Plugin Readme/Assets Update</a> Action handles committing changes to a plugin’s readme or assets. The WP Continuous Deployment script automatically adds both and sets up appropriate GitHub workflow files for each.</p>\n\n\n\n<p>“What I hope to accomplish with WP Continuous Deployment is make it easy for any developer to use the GitHub Actions built by 10up and others and help migrate to this new workflow with a pinch of automation,” said Awais. “Without WP Continuous Deployment, migrating to GitHub Actions for deploying WordPress plugins is a task that requires knowledge of how GitHub Actions work, what files you have to create, what secrets are, and where to put them. We lose a great number of developers that are unable to figure out this step — due to a bulky and dry operational experience.”</p>\n\n\n\n<p>The workflow for many WordPress developers today runs directly through Git, primarily with repositories hosted on GitHub. Often, developers expect any committed code to automatically deploy to the places it should go, such as production websites. </p>\n\n\n\n<p>The WordPress plugin directory system, which relies on SVN instead of Git, can sometimes be a bottleneck in team workflows. Some teams even have developers who have never used SVN in their careers. It makes sense for teams to use a single system. Doing so leads to fewer bugs and requires fewer resources to train people on a dying version control system.</p>\n\n\n\n<p>“We’re not doing anyone a favor by keeping SVN around,” said Awais. “Projects are hiring hundreds of open source developers to make it easy for the developers’ community to interact with their projects. Whereas WordPress — that once held that edge — has started to lag behind by making it hard and impractical to get started with WordPress development. Go pick 100 random students for universities all over the world and ask them to start an open-source project. You’ll be amazed by the majority of them choosing to start with Git and MIT license. And, here in the WordPress community, we ask people to use SVN. That’s impractical and inaccessible for a majority of developers today.”</p>\n\n\n\n<p>Awais said that GitHub Actions have allowed his team to shed a lot of dead weight. He originally did not make his GitHub Actions open source because they were specific to his use cases. After trimming the code down, he realized they were not any different from the Actions that 10up had already released.</p>\n\n\n\n<p>“I see dealing with SVN as a DevOps task,” he said. “Something web developers should not be concerned with in 2020. Web developers want to build websites. They want to use Git to do that. With JAMstack, everyone has become accustomed to the idea of pushing a git commit and getting the new build/release. That’s why I built WP Continuous Deployment.”</p>\n\n\n\n<h2>Set up in 1, 2…</h2>\n\n\n\n<img />Running the setup process for WP Continuous Deployment\n\n\n\n<p>When I originally tested 10up’s GitHub Actions last year, there was a small learning curve. I had to figure out what those new workflow files were for and whether I needed to change things. It was not an overly complicated process, but there was a moment of confusion or two.</p>\n\n\n\n<p>What Awais’ script does is take those two GitHub Actions one step further and automate nearly all of the setup.</p>\n\n\n\n<p>Developers must have Node.js installed on their computer to run the script, which is fairly common today. With a single command of <code>npx wp-continuous-deployment</code>, the script is installed. It then prompts you to enter your WordPress.org plugin slug to set everything up. Once done, you merely need to create a couple of secret keys on your GitHub repository.</p>\n\n\n\n<p>Awais wanted to automate the entire process. However, GitHub does not yet have an API for creating secret keys. Until that happens, it is the only manual step required.</p>\n\n\n\n<p>Within two minutes of choosing which repository I wanted to test the script on, I had everything in place and ready to go. Now, I just need to find some time to actually write code for some of my numerous plugins so I can truly put this script to the test. Thus far, things are looking good.</p>\n\n\n\n<p>It may finally be possible for me to purge everything related to SVN from my life. That would be a welcome change. <code>#lifegoals</code></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Feb 2020 21:23: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:14:\"<NAME>\";s: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:56:\"WordPress.org blog: The Month in WordPress: January 2020\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8316\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2020/02/the-month-in-wordpress-january-2020/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5941:\"<p>Following an action-packed December, 2020 is off to a fine start with some new releases and announcements. Read on to find out what happened in the WordPress project in January.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Release of Gutenberg 7.2 & 7.3</h2>\n\n\n\n<p><a href=\"https://make.wordpress.org/core/2020/01/09/whats-new-in-gutenberg-8-january/\">Gutenberg 7.2</a>, the first Gutenberg release of 2020, was deployed on January 8th and included over 180 pull requests from more than 56 contributors. This was followed soon after by <a href=\"https://make.wordpress.org/core/2020/01/22/whats-new-in-gutenberg-22-january/\">Gutenberg 7.3</a>. New features include a new Buttons block, support in adding links to Media & Text block images, improvements to the Navigation and Gallery blocks, performance improvements, and accessibility enhancements. These releases also included many additional enhancements, fixes, new APIs, documentation, and more.</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Proposal for an XML Sitemaps Feature Plugin</h2>\n\n\n\n<p>In June last year, a team of contributors <a href=\"https://make.wordpress.org/core/2019/06/12/xml-sitemaps-feature-project-proposal/\">proposed</a> a feature plugin that would bring standardized XML sitemaps to WordPress Core. Since then, the team has been working to bring this to reality and <a href=\"https://make.wordpress.org/core/2020/01/27/feature-plugin-xml-sitemaps/\">have now published a working plugin</a> to demonstrate this new capability.</p>\n\n\n\n<p>The plugin is still in development, but the included features already provide much-needed functionality from which all WordPress sites can benefit. You can install the plugin from your WordPress dashboard or <a href=\"https://wordpress.org/plugins/core-sitemaps/\">download it here</a>.</p>\n\n\n\n<p>Want to get involved in bringing this feature to Core? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, report any issues you find <a href=\"https://github.com/GoogleChromeLabs/wp-sitemaps/issues\">on GitHub</a>, and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>A New Block-Based Themes Meeting</h2>\n\n\n\n<p>The Theme Review Team has <a href=\"https://make.wordpress.org/themes/2020/01/29/new-bi-weekly-block-based-themes-meeting/\">announced</a> that they will be holding bi-weekly meetings in the #themereview channel focused on discussing block-based themes. If you are interested in discussing themes within the context of Gutenberg’s full-site editing framework, this will be the place to do so! The first meeting will be held on Wednesday, February 5, at 16:00 UTC.</p>\n\n\n\n<p>Want to get involved with the Theme Review Team or <a href=\"https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/\">become a reviewer</a>? Follow <a href=\"https://make.wordpress.org/themes/\">their blog</a>, and join the #themereview channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading</h2>\n\n\n\n<ul><li>The Core team has started work on WordPress 5.4 and kicked off their planning with <a href=\"https://make.wordpress.org/core/2020/01/14/wordpress-5-4-planning-roundup/\">a summary post</a>. You can follow all the v5.4 updates by watching <a href=\"https://make.wordpress.org/core/tag/5-4/\">the version tag</a> on the Core team blog.</li><li>The inaugural <a href=\"https://2020.asia.wordcamp.org/\">WordCamp Asia</a> event is taking place in February. This will be the largest WordPress event in the region, bringing together around 1,500 WordPress enthusiasts from around the world.</li><li>Two WordPress community leaders, <a href=\"https://profiles.wordpress.org/chanthaboune/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>chanthaboune</a> and <a href=\"https://profiles.wordpress.org/andreamiddleton/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>andreamiddleton</a>, <a href=\"https://wordpress.org/news/2020/01/wordpress-leaders-nominated-for-cmx-awards/\">were nominated for CMX awards</a> due to their work on the WordPress project, with <a href=\"https://profiles.wordpress.org/andreamiddleton/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>andreamiddleton</a> winning the award for Executive Leader of a Community Team.</li><li><a href=\"https://make.wordpress.org/core/2020/01/29/lazy-loading-images-in-wordpress-core/\">A feature plugin has been proposed</a> that introduces lazy-loading images to WordPress Core, which will be a huge step forward in improving performance all across the web.</li><li>The Core team has put together <a href=\"https://make.wordpress.org/core/handbook/tutorials/faq-for-new-contributors/\">an extensive and informative FAQ</a> to help new contributors get involved in contributing to the project.</li><li>One key priority for Gutenberg is the ability to control the block editor. There are already a number of APIs that control the experience, but there is a lack of consistency and missing APIs. <a href=\"https://make.wordpress.org/core/2020/01/23/controlling-the-block-editor/\">A method to address this</a> has been proposed.</li><li>The Design team <a href=\"https://make.wordpress.org/design/2020/01/24/gutenberg-phase-2-friday-design-update-43/\">published detailed information</a> on the recent design improvements in Gutenberg.</li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 03 Feb 2020 09:54:06 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:10:\"<NAME>\";s: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:106:\"WPTavern: Join the Future of WordPress Themes Conversation: Theme Review Team to Hold Biweekly 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=96885\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:116:\"https://wptavern.com/join-the-future-of-wordpress-themes-conversation-theme-review-team-to-hold-biweekly-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:4418:\"<p class=\"has-drop-cap\">In collaboration with the core design and editor teams, the WordPress theme review team will begin <a href=\"https://make.wordpress.org/themes/2020/01/29/new-bi-weekly-block-based-themes-meeting/\">hosting biweekly (fortnightly) meetings</a> on the future of themes. The meetings will be held every other Wednesday on the <a href=\"https://wordpress.slack.com/messages/themereview/\">#themereview WordPress Slack channel</a> at 16:00 UTC. The first meeting is on February 5.</p>\n\n\n\n<p>Phase 2 of the Gutenberg project is about tackling site customization. This covers everything from turning sidebars into block containers to redefining how themes will work in a block-based system in the coming years. The latter is a huge unanswered question. There are several ideas on how themes should be handled.</p>\n\n\n\n<p><NAME>, a design director for Automattic, proposed the meeting as a step toward answering the future-of-themes question. “The main thing I’d like to accomplish is to build up regular cross-team communication around the theme plus full-site editing work,” he said. “There are so many potential changes on the horizon, and we really need perspective from both the Gutenberg folks and theme authors. I know it’s difficult to keep up with all the development happening, and I thought this dedicated meeting would be a great place to stay up to date and share ideas on a regular basis.”</p>\n\n\n\n<p>Currently, the agenda for the first meeting is still open but should be posted next week. Anyone who wants to participate or make sure an idea sees discussion, should let the team know in the <a href=\"https://make.wordpress.org/themes/2020/01/29/new-bi-weekly-block-based-themes-meeting/\">announcement post’s</a> comments.</p>\n\n\n\n<p>“I’d initially like to try and get everyone on the same page in terms of what’s happening already on the Gutenberg front,” said Reigstad. “So for instance, the experimental block-based themes implementation and the global styles work. We’ll likely go over those a little bit, share links and updates, and then pivot into some discussion questions.”</p>\n\n\n\n<p>Bringing in the theme review team is imperative for a smooth transition into whatever themes eventually become. “There’s already a lot of full-site editing work going on, and there are already experimental reference documents for block-based themes,” said Reigstad earlier this week in the team’s regular meeting. “It’s important for the TRT and the theme community to keep up to date on this work, and to develop a clear communication loop with the Gutenberg teams.”</p>\n\n\n\n<p>There is some concern that the concept of full, block-based themes will simply be railroaded into core WordPress, regardless of feedback. Not all members of the theme review team or theme authors are supportive of the idea.</p>\n\n\n\n<p>Theme reviewer <NAME> pointed out in the announcement’s comments that using the phrase “block-based themes” in the meeting title shows bias in favor of themes made of blocks. “Why is the current Full Site Editing code outside the scope of the Customizer?” she asked. “What is the goal? Is it even something that makes sense for themes? Don’t we need a merge proposal? Or even a consensus on design before forcing these changes into core and having meetings about using experimental code as if it’s the only choice?”</p>\n\n\n\n<p>These are questions that will certainly come up in the meeting.</p>\n\n\n\n<p>Block-based themes already feel like a foregone conclusion. The initial code is currently in the Gutenberg plugin, albeit as an experimental feature. There is already <a href=\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\">documentation for building such themes</a>. There is a core <a href=\"https://wptavern.com/get-involved-with-block-based-wordpress-theme-experiments\">theme experiments repository</a> Everything seems to be moving full-steam ahead in that direction.</p>\n\n\n\n<p>Whatever direction themes end up going, the meeting will at least offer an opportunity for the community to add their input. For success, the editor, design, and theme review team members will need to find some common ground to begin their discussions.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 31 Jan 2020 20:49: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:\"<NAME>\";s: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:57:\"WPTavern: Native Lazy Loading Support Coming to WordPress\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96875\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:68:\"https://wptavern.com/native-lazy-loading-support-coming-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:4789:\"<p class=\"has-drop-cap\">It seems to be the week for dropping news of WordPress feature plugins. <NAME>, WordPress core committer and developer programs engineer at Google, announced a <a href=\"https://make.wordpress.org/core/2020/01/29/lazy-loading-images-in-wordpress-core/\">plan to push a lazy loading feature</a> to the platform. If testing goes well, this feature could land in WordPress 5.4 in March.</p>\n\n\n\n<p>The concept of lazy loading allows a webpage to render without loading certain resources until they are needed. This leads to faster page loads and saves data on the visitor’s end. Lazy loading is particularly useful when rendering images on the web. </p>\n\n\n\n<p>The opposite of lazy loading is called <em>eager</em> loading, which loads everything in bulk. By default, this is how all images are loaded on the web. This often leads to poor performance on image-heavy webpages where many of the images are not in the site visitor’s viewport when first viewing the page.</p>\n\n\n\n<p>For many years, various JavaScript libraries have handled this feature but not always to success. A native solution is slowly making its way into browsers. Native lazy loading works by adding a <code>loading</code> attribute to an <code><img></code> or <code><iframe></code> element. Browsers can then decide how to load a resource based on the value of the attribute. Currently, <a href=\"https://caniuse.com/#feat=loading-lazy-attr\">Chrome, Edge, and Opera</a> all handle the loading attribute. Once the attribute officially makes it into the <a href=\"https://github.com/whatwg/html/pull/3752\">HTML specification</a>, the feature should be a standard that all browsers support.</p>\n\n\n\n<blockquote><p> Adopting the new loading attribute is a great chance for WordPress to lead the way for a faster web overall. </p><cite> <NAME></cite></blockquote>\n\n\n\n<p>The new <a href=\"https://wordpress.org/plugins/wp-lazy-loading/\">Lazy Loading feature plugin</a> is now available in the WordPress plugin directory. The plugin relies only on native browser support and does not add extra JavaScript. The implementation adds a loading attribute to images in post content, excerpts, comments, text widgets, avatars, and instances of using core WordPress image functions. By default, the plugin sets all images to load lazily rather than eagerly.</p>\n\n\n\n<p>It is refreshing to see the continued work by core contributors on more robust image solutions. Along with WordPress 5.3’s <a href=\"https://wptavern.com/wordpress-5-3-improves-large-image-handling\">large image size handling</a>, both features will lead to a generally faster web. With more users loading high-quality images via mobile phones over the past few years, it has only exacerbated the problem of a slow web. That is why it imperative that WordPress continually push for image optimization.</p>\n\n\n\n<p>“With WordPress enabling native lazy-loading by default, it would significantly impact performance and user experience for millions of sites, without requiring any technical knowledge or even awareness of lazy-loading as a concept,” wrote Arntz in the announcement post. “Adopting the new loading attribute is a great chance for WordPress to lead the way for a faster web overall.”</p>\n\n\n\n<p>Arntz and a team of engineers originally <a href=\"https://wptavern.com/google-releases-native-lazyload-plugin-for-wordpress\">released a native lazy loading plugin</a> in September 2019. This was shortly after <a href=\"https://wptavern.com/chrome-76-adds-native-lazy-loading-wordpress-contributors-continue-discussion-regarding-core-support\">Google brought the “loading” attribute</a> feature to version 76 of its Chrome browser. The Native Lazyload plugin currently has over 7,000 installations.</p>\n\n\n\n<h2>How This Affects Existing Plugins</h2>\n\n\n\n<p>Because not all web browsers support the loading attribute, users may not want to automatically drop their current plugins when the feature lands in WordPress. Users may choose to support browsers without native lazy loading for a while</p>\n\n\n\n<p>The proposed code within the Lazy Loading plugin attempts to detect whether the <code>loading</code> attribute exists on an image before applying it. This means the code should play nicely with existing plugins and avoid conflicts in most cases.</p>\n\n\n\n<p>Developers of plugins that handle lazy loading need to start testing their plugins and updating them for WordPress 5.4. Follow the <a href=\"https://core.trac.wordpress.org/ticket/44427\">Lazy Loading API ticket</a> on core Trac to stay updated on when the feature lands and the <a href=\"https://github.com/WordPress/wp-lazy-loading\">GitHub repository</a> for contributing to its development.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 30 Jan 2020 20:22:45 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:67:\"WPTavern: XML Sitemaps Feature Plugin Open for Testing and Feedback\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96800\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/xml-sitemaps-feature-plugin-open-for-testing-and-feedback\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6492:\"<p><NAME>, a Developer Relations Program Manager at Google, and several contributors posted an <a href=\"https://make.wordpress.org/core/2020/01/27/feature-plugin-xml-sitemaps/\">update on the XML sitemaps feature</a> that may land in WordPress this year. After seven months of development, the team has made the <a href=\"https://github.com/GoogleChromeLabs/wp-sitemaps\">XML Sitemaps feature plugin</a> available on GitHub. It is currently open for testing and feedback. The plugin should also be available in the WordPress plugin directory by next week.</p>\n\n\n\n<p class=\"has-background has-gray-100-background-color is-style-default bg-gray-100\"><strong>Update (January 31, 2020):</strong> The <a href=\"https://wordpress.org/plugins/core-sitemaps/\">Core Sitemaps feature plugin</a> is now available in the WordPress plugin repository.</p>\n\n\n\n<p>The project aims to ship a basic version of an XML sitemaps feature to all WordPress installations. It will also offer an API for plugin developers to manipulate. Therefore, sitemap plugins would not automatically disappear. Instead, plugins would offer users various options on how their sitemaps work.</p>\n\n\n\n<p>A team created by Google, Yoast, and other contributors <a href=\"https://wptavern.com/developers-at-yoast-and-google-collaborate-on-proposal-to-add-xml-sitemaps-to-wordpress-core\">originally proposed XML sitemaps as a core WordPress feature</a> in June 2019. Traditionally, WordPress has left this feature to plugins to implement, and many have filled this role over the years. However, several other major content management systems ship with sitemaps as part of their core codebase.</p>\n\n\n\n<p>Many praised the initiative, such as WordPress project lead <NAME>. “This makes a lot of sense, looking forward to seeing the v1 of this in core and for it to evolve in future releases and cement WordPress’ well-deserved reputation of being the best CMS for SEO,” he said.</p>\n\n\n\n<p>However, several people questioned whether WordPress should ship with XML sitemaps. Some were worried about performance and others felt like the feature should remain in plugins.</p>\n\n\n\n<p>“At a high level, expanding the number of WordPress sites with Sitemaps ultimately speeds up content discoverability by search engines and re-crawl fresher content flagged by the lastmod date faster than a scheduled bot would,” Muller said of the primary reasons the feature belongs in core.</p>\n\n\n\n<p>WordPress users may see this feature arrive in major update this year. “Ambitiously [version] 5.4,” said Muller of the release goal. “Realistically 5.5.”</p>\n\n\n\n<p>The feature plugin currently indexes the following URLs for a site:</p>\n\n\n\n<ul><li>Homepage</li><li>Blog posts page (if not the homepage)</li><li>Posts and pages</li><li>Categories and tags</li><li>Custom post types</li><li>Custom taxonomies</li><li>Users/Authors</li></ul>\n\n\n\n<p>Custom post types and taxonomies are registered only if they are public. There is also a filter hook available to change which post types, taxonomies, and users are indexed. Ideally, WordPress would provide a registration flag for post types and taxonomies.</p>\n\n\n\n<h2>Solving the Performance Issues</h2>\n\n\n\n<p>One of the primary concerns with the initial proposal is how well a core sitemaps feature would perform and scale, particularly on larger sites. Without a full caching solution built into core, it presented some hurdles for the team.</p>\n\n\n\n<p>“Solving the performance issue is not trivial, and we have looked into various solutions,” said Muller. “We believe that we landed on a solution that doesn’t need full caching and will still be scalable.”</p>\n\n\n\n<p>For performance, there are two primary challenges:</p>\n\n\n\n<ul><li>The number of URLs per page.</li><li>The <code>lastmod</code> date in the <code>index.xml</code> file.</li></ul>\n\n\n\n<p>“Addressing the number of URLs per page is fairly trivial,” said Muller. “While sitemaps can have up to 50,000 URLs per sitemap, we found that capping it at 2,000 is acceptable from a performance perspective and totally acceptable from a search engine perspective.” The team decided to stick with a default of 2,000 URLs per sitemap and to provide a filter hook for plugins to alter if necessary.</p>\n\n\n\n<p>Finding a solution for the <code>lastmod</code> date was not as easy. “We believe we found a good balance, which will be scalable and doesn’t open the can of worms that full caching exposes us to,” said Muller.</p>\n\n\n\n<p>The solution the team implemented involved scheduling a cron task that runs twice daily (the frequency can be filtered by plugins). The cron job fetches the <code>lastmod</code> dates of each sitemap and stores them in the options table, which essentially works as a light caching solution.</p>\n\n\n\n<p>“Relying on cron should be stable enough for small to medium websites,” said Muller. “Enterprise websites usually have server cron set up to more regularly ping WP Cron instead of relying on website visitors to trigger it. In fact, most managed hosting providers have that for all plans.”</p>\n\n\n\n<p>If the team’s initial implementation is not well-rounded enough, they have been researching an alternative implementation that uses custom post types to store and update sitemap data. Two open GitHub tickets further explore performance that developers may want to check out: <a href=\"https://github.com/GoogleChromeLabs/wp-sitemaps/issues/1\">Issue #1</a> and <a href=\"https://github.com/GoogleChromeLabs/wp-sitemaps/issues/39\">Issue #39</a>.</p>\n\n\n\n<h2>What Happens to Sites With Existing Sitemaps?</h2>\n\n\n\n<p>One question that remains unanswered is what happens when a user updates to WordPress 5.4/5.5 and already has a sitemap. There are likely millions of WordPress sites that are running a plugin or have some sort of sitemap solution in place. </p>\n\n\n\n<p>“This is a question which we haven’t quite solved,” said Muller. “It is important to work with plugin authors, and in an ideal world, all plugins providing advanced sitemaps solutions would extend the core API. We would love to get feedback from the community on that one.”</p>\n\n\n\n<p>WordPress must take care to avoid any major conflicts or indexing errors, or at least alleviate issues for the users who may be unaware of this upcoming feature.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 29 Jan 2020 20:37:36 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:71:\"WPTavern: Emoji Conbini and the Case for a Block Enhancements 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:29:\"https://wptavern.com/?p=96802\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/emoji-conbini-and-the-case-for-a-block-enhancements-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:8193:\"<p>In December of 2019, <NAME>, the owner of <a href=\"https://sortabrilliant.com/\">Sort<NAME></a>, quietly launched <a href=\"https://block.garden/\">Block Garden</a> with a proposal for plugin authors to build block-based plugins off concepts, called <em><a href=\"https://block.garden/seeds/\">seeds</a></em>, from his site. He has since written extensively on the block editor and has shared a multitude of ideas, many of which are <em>sorta brilliant</em>.</p>\n\n\n\n<p>It is easy to be drawn in by Hamze’s unabashed love for blocks. In a post titled “<a href=\"https://block.garden/not-busy/\">You aren’t busy, you’re just not excited</a>,” Hamze challenges developers to build something, anything and not worry about it being perfect or becoming an earth-shattering product. “The purpose of Block Garden is to get you excited about blocks,” he wrote in the post. “To make you so excited about blocks that you’ll make the time to bring them to life. The community needs you more than you realize. I honestly believe that every person has at least one block in them. If I can get you to create that first block, I know you’ll be hooked for life.”</p>\n\n\n\n<p>He has created a space for those who genuinely love the block editor. Block Garden is reminiscent of some of the early WordPress blogs where normal, everyday end-users shared their love of the platform. It is refreshingly optimistic. It is block geekdom at its finest. <em>And, I kind of love it.</em></p>\n\n\n\n<p>Hamze put out a <a href=\"https://block.garden/block-builder/\">job posting for block developers</a> earlier this month. Several developers answered the call. “I can’t code but I have ideas and cash that I’m investing into blocks, mostly to keep the boredom at bay that is slowly killing me,” he said. “We are making some really fun blocks together. This is just the tip of the iceberg.”</p>\n\n\n\n<p>In a few short weeks, Hamze and his co-authors have released multiple block-related plugins through his Sorta Brilliant brand that are now available on the WordPress plugin directory:</p>\n\n\n\n<ul><li><a href=\"https://wordpress.org/plugins/post-script/\">P.S.</a> – A container block for grouping blocks into a popover.</li><li><a href=\"https://wordpress.org/plugins/streamshare/\">StreamShare for Twitch</a> – Embed Twitch content into the block editor.</li><li><a href=\"https://wordpress.org/plugins/ghstwrtr/\">Ghostwriter</a> – Adds a heading block style that types out the text on the front end, <em>Ghostwriter</em> style (for you fans of the ’90s TV series).</li><li><a href=\"https://wordpress.org/plugins/ubiquitous-blocks/\">Ubiquitous Blocks</a> – Exposes the Reusable Blocks admin screen and allows users to automatically add them to posts.</li></ul>\n\n\n\n<h2>Emoji Conbini</h2>\n\n\n\n<img />Inserting an emoji with the Emoji Conbini plugin.\n\n\n\n<p>In collaboration with <NAME>, Hamze’s latest release is the <a href=\"https://wordpress.org/plugins/emoji-conbini/\">Emoji Conbini</a> plugin. It adds an emoji inserter to the block editor toolbar.</p>\n\n\n\n<p>Emoji Conbini utilizes the <a href=\"https://github.com/missive/emoji-mart\">Emoji Mart</a> library, which offers a Slack-like emoji picker. When the picker is open, the user merely needs to choose their preferred emoji. Users can also search for a specific emoji.</p>\n\n\n\n<p>Hamze was aware of the <a href=\"https://wordpress.org/plugins/emoji-autocomplete-gutenberg/\">Emoji Autocomplete Gutenberg</a> plugin before commissioning his emoji plugin for the block editor. “I loved how easy it made adding emoji but I didn’t like the UI,” he said. “It seemed like you had to know what emoji you wanted to add and relied on keyboard shortcuts, which I don’t think everyone is comfortable with.”</p>\n\n\n\n<p>The problem with both emoji plugins is that they insert the WordPress-based emoji image directly into the editor instead of the emoji character. By default, WordPress will automatically convert emoji characters to images on the front end. For the average user, this is likely a non-issue. However, some users prefer to use the browser-based emoji and disable the images that core outputs. Both emoji plugins remove this possibility. They also remove the possibility of using a different emoji image library.</p>\n\n\n\n<p>“To be honest, I’m not really a fan of the browser versions, but I’m willing to consider anything if there is a demand for it,” said Hamze of the possibility of simply inserting the emoji character. “To me, getting version 1 out there is the most important, and if anything needs to be changed, people will let me know.”</p>\n\n\n\n<p>The term “conbini” initially drew me to the plugin, which is the name given to Japanese convenient stores 🏪. If you have never been to one, they are like stepping into another world (<em>almost everything in Japan seems otherworldly to this smalltown guy from the southern U.S.</em>).</p>\n\n\n\n<p>“I love everything from Japan,” said Hamze. “The music, anime, the tech. I bid on items on Yahoo Japan daily as I love surrounding myself with cool stuff from Japan. I’ve only been to Japan once, but it was magical. I especially loved going to conbini. My favorite thing to get there was rice balls from Lawsons.”</p>\n\n\n\n<p>The plugin name also plays into Hamze’s goals with Sorta Brilliant and Block Garden. While many other plugins are offering full packages for blocks, he is dropping smaller, <em>convenient</em> extensions to the block editor. Emoji Conbini shows that there is perhaps a market for add-ons that are block-related but not necessarily blocks, or at least some people are thinking about it.</p>\n\n\n\n<h2>Discovering Block Extensions</h2>\n\n\n\n<p>In his post “<a href=\"https://block.garden/more-than-just-blocks/\">The block directory needs more than just blocks</a>,” Hamze argues that one of the largest hurdles for block-related plugins is discoverability. He further argues the block directory is too tightly focused on individual blocks, proposing a “block enhancements” category as a solution.</p>\n\n\n\n<p>For Emoji Conbini, 10up’s <a href=\"https://wptavern.com/inserting-special-characters-into-the-block-editor\">Insert Special Characters</a>, ThemeIsle’s <a href=\"https://wordpress.org/plugins/blocks-css/\">Blocks CSS</a>, and other plugins that extend the block editor, there is no way for users to discover these plugins without specifically searching for them. These are useful plugins that could help sell the block editor to users who are on the fence.</p>\n\n\n\n<p>There is an unknown number of possibilities for enhancements to the block editor. This sub-category of block-editor plugins does not seem to get the attention that is going toward blocks. However, in some cases, they can be far more useful for everyday writing than the numerous blocks in development.</p>\n\n\n\n<p>Hamze’s initial idea proposes an enhancements category for the <a href=\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced\">upcoming block directory</a>, but that has problems. For one, the block directory will be directly tied to the block inserter in a future version of WordPress. Plus, these types of plugins are not actual blocks. However, the concept of making block enhancements more visible to users is a necessary part of the puzzle. For the block editor’s continued success, WordPress needs to expose its users to a wider world of possibilities than simply installing another block.</p>\n\n\n\n<p>Now is the time to start thinking about exposure for plugins that enhance the block editor. Eventually, these types of plugins may need to be further grouped into editor toolbar (e.g., character inserters), block options (e.g., extra settings for existing blocks), and other categories. I suspect that we are only now glimpsing a future where users will be asking how to find not just blocks but block editor extensions.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 28 Jan 2020 20:54: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:\"<NAME>\";s: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:75:\"WPTavern: Swift Control Replaces WordPress Toolbar With Custom Access 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96787\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:86:\"https://wptavern.com/swift-control-replaces-wordpress-toolbar-with-custom-access-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5397:\"<img />Swift Control expanded panel on the site front end.\n\n\n\n<p><NAME>, creator of the <a href=\"https://wordpress.org/themes/page-builder-framework\">Page Builder Framework</a> theme, launched the <a href=\"https://wordpress.org/plugins/swift-control/\">Swift Control plugin</a> last week. The plugin is billed as a replacement for the core WordPress toolbar (admin bar). It allows site owners to customize the front-end control panel’s appearance and what links are displayed.</p>\n\n\n\n<p>Swift Control adds a new button on the front end of any site the plugin is active on. When clicked, the button expands to open the full array of button-like links to various admin screens. By default, the links point to the dashboard, edit screen for the current post, and the customizer.</p>\n\n\n\n<p>On the whole, the default functionality is not much different from the normal toolbar. The selling point for this plugin is its customizability. For users who want more control over admin access links from the front end, the plugin is a nice option.</p>\n\n\n\n<p>Vongries said the plugin made it easier for his customers to work with than the WordPress toolbar. He had wanted to release it as a standalone plugin for others to use over the years. However, he lacked the time and resources to put the release together.</p>\n\n\n\n<p>“We built this for our multisite network around 3 years ago to make it easier for our customers to navigate and access the key areas of their website,” said Vongries. “We actually ended up using this — what was back then just a couple pieces of custom code — on all of our client websites. I got so used to it, I’m using it on my own sites as well.”</p>\n\n\n\n<p>The plugin is simple to use and does its job well. For the moment, the largest downside is that the front-end controls are always positioned in the middle of the left side of the screen. This means it is not a one-size-fits-all solution. “We’ve actually planned to provide some position options so you can align the panel to the left, right, top-left, top-right and so on,” said Vongries. “That’s on the roadmap as well as some different styling options for the panel.” Both the positioning and styling options are planned for the free version of the plugin.</p>\n\n\n\n<p>It would also be nice to see some mobile-specific options for the control panel. An option to move it to a different location on smaller screens would be helpful so that the buttons do not inadvertently cover content. Adding an option to disable it completely on mobile may also be worth considering.</p>\n\n\n\n<p>The positioning is the only <em>potential</em> downside of an otherwise well-made plugin. Because it is being actively worked on, it may be a non-issue in future versions (<em>I’m currently running version 1.2.1</em>).</p>\n\n\n\n<h2>Customize the Swift Control Panel</h2>\n\n\n\n<img />Swift Control plugin settings screen.\n\n\n\n<p>The beauty of Swift Control is in its options for customizing what buttons appear in the front-end panel. By default, the free version of the plugin contains seven “widgets” (what the plugin calls its buttons/links):</p>\n\n\n\n<ul><li>Dashboard</li><li>Edit {Post Type}</li><li>Customize</li><li>New Post</li><li>New Page</li><li>Themes</li><li>Plugins</li></ul>\n\n\n\n<p>Users can drag and drop these widgets wherever they prefer in the control panel. Each widget has its own options. By clicking the edit button, users can change both the icon and title for the widget. Users can also decide whether links should open in a new browser tab.</p>\n\n\n\n<p><a href=\"https://wpswiftcontrol.com/\">Swift Control Pro</a>, the commercial version of the plugin, kicks customization up a notch. Besides the widgets available in the free version, it adds widgets for custom post types, launches the editor for page builders (Elementor, Brizy, Divi or Beaver Builder), supports WooCommerce, and adds a logout widget. Users can also create custom buttons.</p>\n\n\n\n<p>Both the free and pro versions offer additional settings. Users can customize each of the colors used in the control panel so that it matches their site. Other settings are switches to enable or disable features, such as turning off the WordPress toolbar.</p>\n\n\n\n<p>The following video shows how Swift Control Pro works (the free version is essentially the same but does not have the pro widgets):</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<h2>Future Plugin Plans</h2>\n\n\n\n<p>Besides new positioning options, Vongries said they are working on an import and export feature. Ideally, this would allow users to keep their settings from test environments or when copying to new sites. It could also be interesting in use on multisite.</p>\n\n\n\n<p>“One of the other features we’re going to work on next is the ability to show controls based on user roles,” said Vongries. “This will require us to change the UI of the widgets though, and we haven’t yet decided on what they should look like.” Currently, the team is exploring various ideas with the UI for such a feature, such as creating an expanding section for access to advanced widget settings.</p>\n\n\n\n<p>The first order of business is bringing in more users and getting feedback, which should help steer the future direction of the plugin.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 27 Jan 2020 19:46: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:14:\"<NAME>\";s: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:56:\"WordPress.org blog: People of WordPress: <NAME>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=8300\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2020/01/people-of-wordpress-robert-cheleuka/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7036:\"<p><em>You’ve probably heard that WordPress is open-source software, and may know that it’s created and run by volunteers. WordPress enthusiasts share many examples of how WordPress changed people’s lives for the better. This monthly series shares some of those lesser-known, amazing stories.</em></p>\n\n\n\n<h2><strong>Meet <NAME></strong></h2>\n\n\n\n<p>Robert is a self-taught graphic and motion designer turned web designer (and aspiring web developer) from Malawi, Africa. Over the years, he has grown fond of WordPress and has become a loyal user. Still, the journey is rough.</p>\n\n\n\n<img src=\"https://i2.wp.com/wordpress.org/news/files/2020/01/DSC08818.jpg?resize=632%2C790&ssl=1\" alt=\"<NAME>\" class=\"wp-image-8303\" /><NAME>\n\n\n\n<h3><strong>Malawi</strong></h3>\n\n\n\n<p>Malawi is one of the poorest countries in the world. A tiny landlocked country with a population of 17 million, it’s largely rural and still considered a developing country. The average entry-level monthly pay for most skilled jobs is about $110. If you’re employed full-time in the creative industry and if you’re very lucky, you might be able to earn more than that. Employees earning more than $300 a month are rare to non-existent.</p>\n\n\n\n<p>Robert has been a freelance graphic designer since about 2011. He started by doing gigs from his dorm in college and from home. Earnings from his freelance jobs increased his interest in entrepreneurship and he started to consider starting his own creative agency.</p>\n\n\n\n<h3><strong>How Robert was introduced to WordPress</strong></h3>\n\n\n\n<p>Robert first came into contact with WordPress in 2014 when he and a friend started a local tech blog. Before that, all he knew was basic, outdated HTML from high school and some knowledge of Adobe Dreamweaver. They decided to use WordPress, and their new blog looked like it came from the future. They used a theme from the repo and got such positive feedback from the blog they decided to open a content and media publishing agency.</p>\n\n\n\n<p>While they got a few web redesign jobs thanks to the exposure the blog brought, they lacked the administrative and business skills needed and ended up going their separate ways. Then in his first real job after college Robert finally took it upon himself to learn the ins and outs of WordPress. He learned how to install WordPress on a server and did some research on customizing themes. </p>\n\n\n\n<p>With that knowledge alone he got his first web design clients and started earning nearly as much as he did at his job. Robert soon realized that free WordPress themes would only take him so far, especially with his limited code skills.</p>\n\n\n\n<p>Because in Malawi only people who travel abroad have access to credit cards, paying for premium themes was impossible. Like many WordPress designers in developing countries, Robert turned to using pirated themes instead. He knew that was both unsafe and unethical, and decided to learn how to code. Knowing how to build themes from scratch would surely help him rise above the competition. </p>\n\n\n\n<img src=\"https://i1.wp.com/wordpress.org/news/files/2020/01/20180905_1971270886435744_8835917058488139776_n.jpg?fit=632%2C632&ssl=1\" alt=\"\" class=\"wp-image-8304\" />\n\n\n\n<h3><strong>The WordPress community from Robert’s perspective</strong></h3>\n\n\n\n<p>Robert doesn’t have a lot of interaction with the WordPress community. Although he would search for solutions from blogs about WordPress he had never actually talked to or asked anyone from the community for a solution. </p>\n\n\n\n<p>Robert believes that this isolation is the result of a glass ceiling — the WordPress community is partially online and partially in-person, but there isn’t a local group in Malawi. And because Malawi, like many other developing nations, lacks a way to pay online many can’t access premium support, online learning, or most other types of professional development. No matter how welcoming the people of WordPress might be, it can still feel like it mostly belongs to those with enough privilege to conduct business on the internet.</p>\n\n\n\n<h3><strong>WordPress & inclusion</strong></h3>\n\n\n\n<p>As most freelancers know, it’s really hard to learn while you also still need to earn. Add pitching to clients and shipping graphic design projects… there are only so many hours in a day.</p>\n\n\n\n<p>Robert didn’t have a programming background and had always been more of a creative person. In order to grow as a web designer/developer, he needed to learn PHP. Again, without access to a credit card, that was complicated. Also, free coding training wasn’t as widely available as it is now.</p>\n\n\n\n<p>Robert wishes that more developers would consider alternative ways for users who cannot pay for courses, themes, or plugins (whether that’s because of available infrastructure or otherwise). He wishes that WordPress tutors and developers would open up ways to accommodate aspiring learners in developing countries who cannot access plugins, courses, and themes, to be able to give back and to participate at another level.</p>\n\n\n\n<p>WordPress has allowed him to build an income he would have no other way of earning and it makes a huge difference. He believes sharing stories like his will hopefully make WordPress products and services become more universally available. In addition, he hopes that more aspiring, self-taught developers will find courage in reaching out to connect with others out there.</p>\n\n\n\n<h2><strong>Contributors</strong></h2>\n\n\n\n<p><NAME> (<a href=\"https://profiles.wordpress.org/wpfiddlybits/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>wpfiddlybits</a>), <NAME> (<a href=\"https://profiles.wordpress.org/yvettesonneveld/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>yvettesonneveld</a>), <NAME> (<a href=\"https://profiles.wordpress.org/chanthaboune/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>chanthaboune</a>), <NAME> (<a href=\"https://profiles.wordpress.org/siobhanseija/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>siobhanseija</a>), <NAME> (<a href=\"https://profiles.wordpress.org/topher1kenobe/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>topher1kenobe</a>)</p>\n\n\n\n<div class=\"wp-block-columns\">\n<div class=\"wp-block-column\">\n<img src=\"https://i1.wp.com/wordpress.org/news/files/2019/07/heropress_large_white_logo.jpg?resize=632%2C474&ssl=1\" alt=\"\" class=\"wp-image-7025\" />\n</div>\n\n\n\n<div class=\"wp-block-column\">\n<p> <em>This post is based on an article originally published on HeroPress.com, a community initiative created by <a href=\"https://profiles.wordpress.org/topher1kenobe/\"><NAME></a>. HeroPress highlights people in the WordPress community who have overcome barriers and whose stories would otherwise go unheard.</em> </p>\n</div>\n</div>\n\n\n\n<p> <em>Meet more WordPress community members over at </em><a href=\"https://heropress.com/\"><em>HeroPress.com</em></a><em>!</em> </p>\n\n\n\n<p><br /></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Sat, 25 Jan 2020 15:26: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:16:\"<NAME>\";s: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:62:\"WPTavern: 10up Releases Autoshare for Twitter WordPress Plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96737\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/10up-releases-autoshare-for-twitter-wordpress-plugin\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3951:\"<p>On Tuesday, 10up <a href=\"https://10up.com/blog/2020/autoshare-for-twitter-wordpress-plugin/\">released its Autoshare for Twitter plugin</a>. The plugin is designed to automatically tweet blog posts as they are published. By default, it will send the post title, featured image, and link to Twitter. Users can also add a custom message. The <a href=\"https://wordpress.org/plugins/autoshare-for-twitter/\">plugin is available</a> in the WordPress plugin directory.</p>\n\n\n\n<p>If you threw a rock into a crowd of WordPress plugins, you would likely smack a social-networking extension. The WordPress plugin market is crowded with similar plugins, so it would make sense if this one flew under the radar. Plus, powerhouse plugins like Jetpack provide similar functionality, such as the <a href=\"https://jetpack.com/support/publicize/\">Jetpack Publicize feature</a>. Yet, with the prevalence of similar plugins, Autoshare for Twitter is worth checking out.</p>\n\n\n\n<p>Many similar plugins work with multiple social networks, but 10up’s plugin is designed specifically for sharing via Twitter. For users who only need a solution for that specific social network, it is a solid solution for version 1.0.</p>\n\n\n\n<p>10up originally built the plugin to provide the company’s clients more control and customization than they found in existing solutions. “Recognizing its widespread potential, we decided to follow our own best practices for managing open-source software by releasing it as a free plugin on the official WordPress plugin repository,” wrote <NAME>, Associate Director of Open Source Initiatives at 10up.</p>\n\n\n\n<p>The plugin works with both the block and classic editors. When in use with the block editor, it is added as part of the pre-publish check system as shown in the following screenshot:</p>\n\n\n\n<img />Pre-publish check for tweeting a post.\n\n\n\n<p>The custom message box tracks the number of characters so that users do not go over Twitter’s character count. The plugin also displays a message in the Status & Visibility panel to let users know if a post was shared on Twitter. </p>\n\n\n\n<p>Overall, the plugin does its job well (<em>sorry to folks who were bombarded with some test tweets earlier</em>). It would be nice to see similar one-off solutions that are specific to other social networks. I often find myself in need of such plugins without dealing with a full array of social networking options.</p>\n\n\n\n<p>The plugin is also <a href=\"https://github.com/10up/autoshare-for-twitter\">available on GitHub</a> for others to contribute. Currently, there are several open issues that would improve how the plugin works.</p>\n\n\n\n<h2>Setup Is Not User-Friendly</h2>\n\n\n\n<img />Settings page for Twitter credentials.\n\n\n\n<p>The biggest downside to the plugin is there are no links, no admin help tab, and no instructions on how to set up the Twitter Credentials on the plugin’s setting screen. The page simply has some text fields for things like an API Key, API Secret, and so on. These are not user-friendly terms, and will likely be confusing for many. Not to mention, similar plugins can connect users at the click of a button. For a plugin that does nearly everything else right, this is a missing piece of what would be a near-perfect release.</p>\n\n\n\n<p>The plugin is ideal for power users or developers who want to set up Twitter sharing for a client. In the current version of the plugin, users need to set up a <a href=\"https://developer.twitter.com/\">Twitter Developer account</a> and create a Twitter App. This generates the API keys and necessary tokens for using the plugin.</p>\n\n\n\n<p>The plugin does have an <a href=\"https://github.com/10up/autoshare-for-twitter/issues/57\">open ticket on GitHub</a> for a better onboarding process, which could solve this issue. Therefore, the team is aware of and actively working on making this smoother in a future version.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 24 Jan 2020 21: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:\"<NAME>\";s: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:102:\"WPTavern: Gutenberg 7.3 Brings Navigation Block Colors, Block Collections API, and Dynamic Post Blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96706\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:111:\"https://wptavern.com/gutenberg-7-3-brings-navigation-block-colors-block-collections-api-and-dynamic-post-blocks\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5495:\"<p>The Gutenberg team <a href=\"https://make.wordpress.org/core/2020/01/22/whats-new-in-gutenberg-22-january/\">announced version 7.3</a> of the plugin yesterday. This was the second release of the year, which included 159 contributions from 56 people. The major changes to the plugin include settings for changing the navigation block’s text and background colors, a new Block Collections API for developers, and placeholder blocks for post elements.</p>\n\n\n\n<p>One of the most significant changes with this release is the speed improvement for page load times and input events. Speed tests are done against posts with ~36,000 words and ~1,000 blocks. The team reduced total load time from 6.431 seconds in version 7.2 to 4.55 seconds in version 7.3. Input events saw larger improvements. Events in 7.3 take 33.8 milliseconds in comparison to 64.7 milliseconds in 7.2.</p>\n\n\n\n<p>Changes in Gutenberg 7.3 covered a wide range of areas in the plugin. The team added an <a href=\"https://github.com/WordPress/gutenberg/pull/18132\">experimental label function</a> for improving block accessibility. They corrected over a dozen bugs with editor navigation. They also introduced some new developer APIs such as a <a href=\"https://github.com/WordPress/gutenberg/pull/19317\">warning utility</a>, <a href=\"https://github.com/WordPress/gutenberg/pull/18495\">text component</a>, and <a href=\"https://github.com/WordPress/gutenberg/pull/17148\">image size control component</a>.</p>\n\n\n\n<p>Work toward full-site editing continued in this release. It is now possible to <a href=\"https://github.com/WordPress/gutenberg/pull/19203\">edit existing template part files</a>. The site editor can also <a href=\"https://github.com/WordPress/gutenberg/pull/19081\">load the front page block template</a>.</p>\n\n\n\n<h2>Navigation Block Colors</h2>\n\n\n\n<img />Selecting custom colors for the navigation block.\n\n\n\n<p>The existing Navigation block continues to improve with each release. Version 7.3 <a href=\"https://github.com/WordPress/gutenberg/pull/19108\">added new options</a> for setting the text color for all navigation items and background color for the entire navigation block.</p>\n\n\n\n<p>It is nice to see some work done toward providing users control over navigation colors. However, it is a far cry from what a good theme designer can do with the flexibility of plain ol’ CSS. Handling navigation colors is tricky because there is so much that is missing. Link colors also need hover and focus state changes. Some designs may need borders for links and border color changes for the various link states or even background color changes.</p>\n\n\n\n<p>Suffice it to say, I am still skeptical about how good the navigation block will be when it is time to move onto full-site editing, especially in comparison to the fine-tuned control that a theme author would normally have.</p>\n\n\n\n<h2>Dynamic Post Element Blocks</h2>\n\n\n\n<img />Post element placeholder blocks.\n\n\n\n<p>In previous releases, the Gutenberg team dropped post title and post content blocks. These are placeholder blocks that will dynamically output the title and content for posts. The long-term goal is for these blocks to be used along with full-site editing, which will allow users to manipulate how everything on their sites is output, including posts.</p>\n\n\n\n<p>Gutenberg 7.3 introduced three new placeholder blocks for post elements:</p>\n\n\n\n<ul><li><a href=\"https://github.com/WordPress/gutenberg/pull/19576\">Post author block</a></li><li><a href=\"https://github.com/WordPress/gutenberg/pull/19578\">Post date block</a></li><li><a href=\"https://github.com/WordPress/gutenberg/pull/19579\">Post excerpt block</a></li></ul>\n\n\n\n<p>This still represents early work toward full-site editing. Eventually, Gutenberg will need to turn nearly every important template tag into a block to get full coverage of what is currently possible with PHP.</p>\n\n\n\n<p>To test these features, you must enable “Full Site Editing” via the Gutenberg > Experiments screen in the WordPress admin.</p>\n\n\n\n<h2>Block Collections API for Developers</h2>\n\n\n\n<pre class=\"wp-block-code alignwide\"><code>registerBlockCollection( \'super-duper\', {\n title: \'Super Duper\',\n icon: ( <SVG xmlns=\"http://www.w3.org/2000/svg\" viewBox=\"0 0 24 24\"><Path d=\"M11 5v7H9.5C7.6 12 6 10.4 6 8.5S7.6 5 9.5 5H11m8-2H9.5C6.5 3 4 5.5 4 8.5S6.5 14 9.5 14H11v7h2V5h2v16h2V5h2V3z\" /></SVG> ),\n} );</code></pre>\n\n\n\n<p>A new Block Collections API was added to version 7.3 for plugin developers. Instead of registering a block category and adding blocks to specific categories, plugin developers can register a collection based on the namespace for their blocks.</p>\n\n\n\n<p>For instance, suppose you develop a plugin with a collection of blocks. Each block is under the namespace <code>super-duper</code>. When you register a block collection with the <code>super-duper</code> namespace, all of the blocks would be automatically registered to your custom block collection. This seems to be a smarter way to handle groups of blocks than the existing category system. </p>\n\n\n\n<p>Right now, collections work the same way as categories within the UI. However, it does open collections to other possibilities in the future.</p>\n\n\n\n<p>Blocks can still be registered to a specific category that makes the most sense for the individual block. However, by registering collections, an avenue exists for finding all blocks coming from a single source.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 Jan 2020 21:17: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:14:\"<NAME>\";s: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:45:\"HeroPress: Thinking Outside the WordPress Box\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=3054\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:142:\"https://heropress.com/essays/thinking-outside-the-wordpress-box/#utm_source=rss&utm_medium=rss&utm_campaign=thinking-outside-the-wordpress-box\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7186:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2021/01/012320-min.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: I feel that we’ve only scratched the surface of what WordPress can be.\" /><p>Most people, when they discover WordPress, start on the challenging and rewarding path of developing themes, plugins and similar products. I decided to think outside the box.</p>\n<p>My name is Alexander, and my WordPress journey began in 2009. I’m from Chisinau, Republic of Moldova. I originally discovered WordPress while looking for a content management system for one of my projects. Intrigued by how it worked, I started like many others do — learning how WordPress works through developing WordPress websites.</p>\n<p>I started using what I knew to provide development services on freelance platforms. For the next decade, I mostly concentrated on the lesser known, yet still critically important parts of WordPress: particularly security and search engine optimization.</p>\n<p>For many people building up a freelance business in the WordPress world, these are the parts that are important to do, but are often thought of as secondary to deeper development. Theme and plugin authors in particular, get the lion’s share of the spotlight when it comes to WordPress development.</p>\n<h3>Speed and Sophistication</h3>\n<p>I soon learned that after a decade of polishing my skills, that what the world needed wasn’t more WordPress theme developers or plugin authors. What it needed were people who could take care of the kinds of tasks that seemed simple on the surface (like protecting a WordPress site from hackers or optimizing it for search engines), yet were very involved and continued to get more complex over time.</p>\n<p>Contrary to popular belief, you can’t just install a plugin or two and think your site is secure or well-optimized for Google and other sites. Sure, there are plugins which can help the process, but when disaster strikes and your site gets hacked, or you find that your site is loading sluggishly compared to your competition, or worse, your site disappears from the search rankings — you know you need help, and FAST.</p>\n<h3>A Dandy Idea!</h3>\n<p>In 2019 I decided to turn my love for WordPress into full-time work through <a href=\"https://wpdandy.com\">WPDandy</a>. Rather than marketing myself strictly as a WordPress developer or theme designer (although I also do development and design work from time to time), I decided to think outside the box and offer the kinds of services I knew that people needed, but didn’t know how much they needed them, until it was too late!</p>\n<p>Through WPDandy, I focused on WordPress maintenance, management and support services. These include but are not limited to: <b>WordPress speed improvements</b>, <b>security</b>,<b> search engine optimization</b>, <b>backups, etc.</b></p>\n<h3>How WPDandy Has Changed My Life</h3>\n<p>WPDandy has changed my life in many ways. It has enabled me to enjoy the freedom and flexibility of working for myself, doing something that I love. Today, I lead a team of highly professional and passionate WordPress developers from around the world.</p>\n<p>Through my online work, I’m able to help clients reach their business and personal goals, and grow their WordPress sites without worrying about keeping everything up to date (which can be a full-time job in itself, especially if there are multiple sites to run!). My company allows me to help others, and that brings me immense satisfaction!</p>\n<h3>Contributing to the Future of WordPress</h3>\n<p>Although I’m immensely proud of what I’ve built with WPDandy as well as thankful to all of the clients who helped me to discover and master the art and science of WordPress, I felt like I also owed something to the WordPress community itself.</p>\n<p>That’s why I’ve also signed on to be a WordPress contributor. I routinely offer suggestions, advice and share code that can help make managing and maintaining WordPress easier, as well as keep it more secure and less vulnerable to hacking and suspicious attacks.</p>\n<p>Beyond that, I’m overjoyed to be a WordCamp speaker as well. I love sharing knowledge with others and collaborating with like minds on powerful new ideas that can help shape WordPress and make it even better than before.</p>\n<h3>Shaping the Future of Content Management</h3>\n<p>It continues to amaze me how what once started as a small, ordinary blogging platform has blossomed into an absolute content management powerhouse. WordPress can become so many things: an e-commerce storefront, a message board, a membership site, and of course a blog. But I feel that, by and large, we’ve only scratched the surface of what WordPress can be.</p>\n<p>I look forward to continuing to be able to provide outstanding WordPress development, maintenance and management services for all of the many iterations of WordPress that exist and will be created in the future. It’s going to be an exciting ride, and I can’t wait to see what’s next.</p>\n<div class=\"rtsocial-container rtsocial-container-align-right rtsocial-horizontal\"><div class=\"rtsocial-twitter-horizontal\"><div class=\"rtsocial-twitter-horizontal-button\"><a title=\"Tweet: Thinking Outside the WordPress Box\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=Thinking%20Outside%20the%20WordPress%20Box&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fthinking-outside-the-wordpress-box%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-fb-horizontal fb-light\"><div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: Thinking Outside the WordPress Box\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fthinking-outside-the-wordpress-box%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-linkedin-horizontal\"><div class=\"rtsocial-linkedin-horizontal-button\"><a class=\"rtsocial-linkedin-button\" href=\"https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fthinking-outside-the-wordpress-box%2F&title=Thinking+Outside+the+WordPress+Box\" rel=\"nofollow\" target=\"_blank\" title=\"Share: Thinking Outside the WordPress Box\"></a></div></div><div class=\"rtsocial-pinterest-horizontal\"><div class=\"rtsocial-pinterest-horizontal-button\"><a class=\"rtsocial-pinterest-button\" href=\"https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/thinking-outside-the-wordpress-box/&media=https://heropress.com/wp-content/uploads/2021/01/012320-min-150x150.jpg&description=Thinking Outside the WordPress Box\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: Thinking Outside the WordPress Box\"></a></div></div><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/essays/thinking-outside-the-wordpress-box/\" title=\"Thinking Outside the WordPress Box\"></a></div><p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/thinking-outside-the-wordpress-box/\">Thinking Outside the WordPress Box</a> appeared first on <a rel=\"nofollow\" href=\"https://heropress.com\">HeroPress</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Thu, 23 Jan 2020 18:00: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:16:\"<NAME>\";s: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:75:\"WPTavern: GiveWP Plugin Users Raised Over $100 Million in Donations in 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96639\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/givewp-plugin-users-raised-over-100-million-in-donations-in-2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5667:\"<img />\n\n\n\n<p><a href=\"https://wordpress.org/plugins/give/\">GiveWP plugin</a> users raised $106 million in donations in 2019. This is the first time donation amounts have crossed the $100 million threshold in a year. <NAME>, GiveWP’s COO, made the <a href=\"https://www.facebook.com/photo.php?fbid=10219125809314580\">announcement on Facebook</a> last week. This is a jump from the $88 million and $41 million raised in 2018 and 2017, respectively.</p>\n\n\n\n<p>“I’m constantly amazed at what we’ve been able to accomplish at GiveWP,” said Cromwell. “The team continues to excel as experts in their fields, the platform itself continues to improve and become even more top-notch. But this number we observed recently really puts the rubber to the road.”</p>\n\n\n\n<p>The $106 million is not an exact total in donations users have gained in their fundraising campaigns. It only represents the numbers by users who are using PayPal or Stripe. “Both PayPal and Stripe provide partner programs where platforms like GiveWP get a small percentage of each processing fee,” said Cromwell. “This isn’t an additional amount, it’s money the processor will take either way, but shares with us because we help them generate more business.” The partners programs rely on transparency in reporting, which is how GiveWP can see the total donations made through those payment processors. “In order for us to know that they are paying us appropriately, they need to provide us with numbers to see how much revenue was processed through our platform.”</p>\n\n\n\n<p>Both PayPal Standard and Stripe are supported in the free version of the GiveWP plugin, which makes them the go-to choices of payment gateways for end-users. “Authorize.net is the next largest,” said Cromwell. “But Authorize is maybe a tenth of the number of users as either PayPal or Stripe (rough estimate).” Without data from the other processors, it’s impossible to know the total donation numbers, which would be higher than the amount the team is aware of.</p>\n\n\n\n<p>GiveWP currently has over 70,000 active installations, many of which power the donation system on small sites. The plugin is also used for large non-profit organizations such as <a href=\"https://lifewater.org/\">Lifewater</a>, a Christian-based organization that brings clean water to families living in poverty around the world; <a href=\"https://liberomagazine.com/\">Libero Magazine</a>, a Vancouver-based mental health magazine and community; and <a href=\"https://www.lovebutton.org/\">Love Button</a>, an organization that promotes a culture of love and aims to inspire humans to act with kindness.</p>\n\n\n\n<h2>From the Past to the Future</h2>\n\n\n\n<p>Impress, the company behind the plugin, <a href=\"https://wptavern.com/give-a-new-free-donations-plugin-for-wordpress\">launched GiveWP</a> in 2015 to “Democratize Generosity.” The goal was to provide non-profits and other causes the ability to launch campaigns without going through the middle-man of crowd-funding sites, which can sometimes carry a hefty fee. Handling all of this within WordPress provided a more robust and customizable solution that put site owners in control of how they ran their fundraising efforts.</p>\n\n\n\n<p>It was a bold move to build to launch in a crowded market of existing donation plugins and add-ons for major eCommerce plugins. Thus far, the venture has turned out well. However, the GiveWP team is not looking to slow down.</p>\n\n\n\n<p>“Honestly, from a plugin/development perspective it feels like we’ve learned everything new all over again,” said Cromwell of the journey thus far. “The things that we felt were the biggest strengths of the platform still are strong, but also now are technical debt that we’re working to revamp to continue to carry GiveWP strong into the future. Our form builder leveled up a lot when we built our own settings API (for example), but now in a post-Gutenberg era, it feels like it needs a more visual refresh. Doing that well with backward compatibility is a serious challenge.”</p>\n\n\n\n<p>The team feels like much of their early success was by targeting the WordPress community. “That’s playing ‘inside baseball,\'” he said. “Getting into the broader WP community and then additionally into the NPO community is where our challenge is now. So we’re flexing new muscles in marketing.”</p>\n\n\n\n<p>The original partners had to pick up new skills over the past four years. They had to learn how to switch gears from simply being owners and workers to managing individual teams. “We’re so proud of our team that it’s become one of our biggest strengths as a company,” said Cromwell. “Now getting from 20 employees (where we’re at now) to 50 will be an even bigger challenge.”</p>\n\n\n\n<p>The GiveWP team does not plan to focus solely on the WordPress ecosystem. They want to branch out and see where new avenues for growth will take them.</p>\n\n\n\n<p>“While WordPress having 35% internet market share is a big deal, there’s still more market outside WordPress than inside,” said Cromwell. “So for the growth and strength of our company we are now building out a new fundraising SaaS which we’re excited to launch this calendar year.”</p>\n\n\n\n<p>If the team manages to launch a successful SaaS product on the GiveWP platform, this year’s $106 million in fundraising could pale in comparison to 2020’s numbers and beyond.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 22 Jan 2020 21:19: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:14:\"<NAME>\";s: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:101:\"WPTavern: GoDaddy’s ‘Go’ WordPress Theme Offers a Page-Building Experience via the Block Editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96641\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:103:\"https://wptavern.com/godaddys-go-wordpress-theme-offers-a-page-building-experience-via-the-block-editor\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8640:\"<img />\n\n\n\n<p>GoDaddy launched its <a href=\"https://wordpress.org/themes/go/\">Go WordPress theme</a> last week. It has been publicly available through its <a href=\"https://github.com/godaddy-wordpress/go\">GitHub repository</a> for several months, but the theme review team finally approved and set it live in the theme directory. Thus far, the theme has garnered 7,000 active installs and is likely to hit the popular list, given GoDaddy’s history of releasing popular themes. It also provides translations in 27 languages out of the box.</p>\n\n\n\n<p>Go is simple. After working with the theme through GoDaddy’s <a href=\"https://wptavern.com/inside-look-at-godaddys-onboarding-process-for-managed-wordpress-hosting\">managed hosting onboarding process</a> in October last year, I was admittedly a little disappointed this time around. The onboarding process made things almost too easy. I had a predesigned site without thinking about it. After installing and activating Go in my test environment, I couldn’t help but feel like it would take 100 times more work to recreate the magic I once basked in. I knew the power of the theme because I had been presented an ideal set of options that were preconfigured for me in the past. Without the configuration, the theme seemed a little less impressive.</p>\n\n\n\n<p>That’s the beauty of great marketing and onboarding. GoDaddy had already reeled me in.</p>\n\n\n\n<p>While the Go theme is simple, it is also powerful. A lot of that power is in its block styles. Instead of focusing on theme-specific features, the team behind the project poured their work into creating an experience that allows theme users to piece their sites together with the block editor. The theme is ideal for users who want to utilize the block editor as a page builder.</p>\n\n\n\n<p>The theme has a handful of customizer options that provide additional flexibility, but the main selling point is that it gets out of the way and lets the user do the designing. I suspect we will see many similar themes in the next year as theme authors come to grips with building themes in a block world. A large part of the market will want themes that are essentially open canvases for site owners to manipulate the output of their site via blocks.</p>\n\n\n\n<p>Go is also designed to work with WooCommerce, which is a large part of the company’s <a href=\"https://wptavern.com/godaddy-launches-ecommerce-hosting-plan-in-partnership-with-woocommerce\">eCommerce hosting service</a>. This integration should make it a nice option for small business owners.</p>\n\n\n\n<h2>CoBlocks Companion Recommended</h2>\n\n\n\n<img />Features block from the CoBlocks plugin.\n\n\n\n<p>The magic of Go is not in the theme itself. It’s in GoDaddy’s companion plugin <a href=\"https://wordpress.org/plugins/coblocks/\">CoBlocks</a>, which the company <a href=\"https://wptavern.com/godaddy-acquires-themebeans-coblocks-block-gallery-and-block-unit-tests\">acquired last year</a> in a deal with ThemeBeans. The plugin has soared from a mere 3,000 active installs to over 100,000 since.</p>\n\n\n\n<p>CoBlocks offers everything from accordions to maps, from logos to pricing tables, and a lot more in between. It covers a lot of ground that the core WordPress editor blocks do not cover.</p>\n\n\n\n<p>The Go theme is designed to go hand-in-hand with CoBlocks (<em>can we get GoDaddy to just go ahead and rename the plugin to <strong>Go</strong>Blocks?</em>). The theme is meant to offer a page-building experience. Because GoDaddy owns both products, it makes sense they would offer one of the nicer integrations between the plugin and a theme.</p>\n\n\n\n<h2>Not Ideal for Blogging</h2>\n\n\n\n<img />A lot of whitespace between text and other blocks in posts.\n\n\n\n<p>The theme makes generous use of whitespace, but its overuse can often break the reading flow for blog posts. The flow from paragraph to paragraph is fine. However, the moment you drop an image, gallery, pull-quote, or one of many other blocks into the content, the theme adds an extra 140 pixels of whitespace above and below the block. It completely throws off the vertical rhythm of the post.</p>\n\n\n\n<p>Go also displays the full posts on the blog posts page instead of excerpts. There are few things I dislike more when it comes to blogs. Providing an option for users to choose between a full and summary view would be ideal.</p>\n\n\n\n<p>The theme does not claim to be well-suited to blogging. None of the demos for the theme show off a blog. If you’re looking for a theme to handle blogging with media mixed in the content, you will find better offerings elsewhere, such as the <a href=\"https://wptavern.com/blocksy-wordpress-theme-provides-a-solid-block-editor-experience\">Blocksy theme</a></p>\n\n\n\n<h2>Limited Yet Useful Theme Options</h2>\n\n\n\n<img />Design style and color scheme options in the customizer.\n\n\n\n<p>The theme adds five sections to the customizer:</p>\n\n\n\n<ul><li>Site Design</li><li>Header</li><li>Footer</li><li>Social</li><li>Site Settings</li></ul>\n\n\n\n<p>Within each section, Go provides a few basic options, most of which are related to colors and layout. The most useful options reside under the “Site Design” section. The theme presents a design style option that changes the theme’s fonts and colors. Currently, there are five design styles: traditional, modern, trendy, welcoming, and playful. Once a design style is selected, users can choose from four color schemes for that style. The design of this system is brilliant. It gives users choices without forcing them to become designers and handpick the perfect hex code for each color.</p>\n\n\n\n<p>Users who prefer to manage individual colors are not left out. The theme also provides options for overriding any of the colors from the chosen color scheme.</p>\n\n\n\n<p>I was disappointed that Go opted for creating individual options for various social networks instead of using a navigation menu. Using WordPress’ built-in nav menu system for social links has become the <em>de facto</em> standard in the last several years, which allows users to carry their social links from one theme to the next. Unfortunately, users are required to retype all of their links with this theme.</p>\n\n\n\n<p>The theme keeps does not go overboard with options but provides enough customizability to make the theme unique to the user.</p>\n\n\n\n<h2>How Does the Code Stack Up?</h2>\n\n\n\n<p>The theme offers a solid and well-documented codebase. There is not much PHP or JavaScript code, so there are few areas where it can go wrong. The theme’s strength is in its CSS.</p>\n\n\n\n<p>The theme templates were primarily HTML with PHP sprinkled in. For DIY users who like to hack away at theme templates, you should not find any surprises.</p>\n\n\n\n<h2>Final Thoughts</h2>\n\n\n\n<p>Users who want to customize every page of their site will likely enjoy this theme. It is well-suited for small business owners and others with small sites. It could work well for artists and others with portfolios as well.</p>\n\n\n\n<p>It does not fit with my personal taste because it does not cater to my blogging style, which is my primary interest in themes. However, I would not hesitate to recommend it to anyone who wants a ton of control over their site’s inner page design.</p>\n\n\n\n<p>The following is a list of the available demos. There is a lot that can be done in combination with the CoBlocks plugin, which you will want to use in combination with Go.</p>\n\n\n\n<p><strong>Demos with the CoBlocks plugin:</strong></p>\n\n\n\n<ul><li><a href=\"https://wpnux.godaddy.com/v2/?template=alder\">Alder</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=ashby\">Ashby</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=barista\">Barista</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=bento\">Bento</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=everett\">Everett</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=figure\">Figure</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=keynote\">Keynote</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=salt\">Salt</a></li></ul>\n\n\n\n<p><strong>Demos with the CoBlocks and WooCommerce plugins:</strong></p>\n\n\n\n<ul><li><a href=\"https://wpnux.godaddy.com/v2/?template=avenue\">Avenue</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=chai\">Chai</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=jane\">Jane</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=philo\">Philo</a></li><li><a href=\"https://wpnux.godaddy.com/v2/?template=wares\">Wares</a></li></ul>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 21 Jan 2020 21:52: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:14:\"<NAME>\";s: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:73:\"WPTavern: Gutenberg Can Tackle the Problems the Fields API Tried to Solve\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96617\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:84:\"https://wptavern.com/gutenberg-can-tackle-the-problems-the-fields-api-tried-to-solve\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6098:\"<p><strong>The Fields API.</strong></p>\n\n\n\n<p><em>Never heard of it?</em> That’s OK. Outside of the inner development community, it is not widely known. The average WordPress user does not need to know about it. Before understanding how the Fields API fits into Gutenberg’s future, you must first understand what it is and the problems it was meant to fix.</p>\n\n\n\n<p>The Fields API was a proposed solution to one of WordPress’ biggest problems: to build form fields in the admin and save data from those fields, developers need to know multiple APIs, depending on the specific admin screen. </p>\n\n\n\n<p><em>Want to build a plugin settings screen?</em> Use the Settings API.</p>\n\n\n\n<p><em>Need some theme options?</em> Build them with the Customize API. </p>\n\n\n\n<p><em>Have some fields to output on the user screen?</em> Here are two hooks and a mess of HTML table markup; sorry, no official API.</p>\n\n\n\n<p>Those are just a few examples, but the truth of it comes down to this: to show something as basic as a text field to end-users, WordPress developers need to know how to do this in a variety of ways based on competing or even missing APIs.</p>\n\n\n\n<p>There are historical reasons for this. New features were bolted on top of WordPress over time. In the mad rush to continue shipping features with each major update, few people stepped back and asked the fundamental question about the technical debt that would pile up over the past 16 years. Shipping end-user features helped the platform grow, but developers had to learn all-new functions and methods each time.</p>\n\n\n\n<p>Adding to the technical burden, when the Gutenberg project launched, it introduced a new system in a different programming language.</p>\n\n\n\n<p>The Fields API would have created a standardized system for outputting form fields and saving field data. It would work with all the existing admin screens and any new features added in the future. Developers could learn a single system and be able to build plugins that worked with practically any area of WordPress.</p>\n\n\n\n<p>In 2014, <NAME> Clark took over the <a href=\"https://make.wordpress.org/core/2014/02/25/metadata-project-update/\">Metadata UI Project</a>. The initial idea was to create an API for adding custom fields (meta box fields) on the post-editing screen. Eventually, Clark and those working on the project realized the problem that needed solving was larger than meta boxes. WordPress needed an API that worked across the board. After a year, the project was <a href=\"https://make.wordpress.org/core/2015/05/27/metadata-api-project-reborn-the-new-fields-api-project/\">relaunched as the Fields API</a>.</p>\n\n\n\n<p>After years of working on the code behind the project, Clark became burned out. He <a href=\"https://wptavern.com/wordpress-core-fields-api-project-is-seeking-new-leadership\">stepped down as the project’s lead</a> in 2018. With no buy-in from the decision-makers for the WordPress project, there was little hope of it making it into core. At that point, the <a href=\"https://wptavern.com/wpweekly-episode-326-long-live-the-fields-api-project\">project was all but dead</a>.</p>\n\n\n\n<p>Gutenberg’s development was in full swing. Developers were gearing up for relearning how to add the same basic text fields and other form elements in whole new ways.</p>\n\n\n\n<p>The Fields API, had it made it into WordPress before the block editor, could have alleviated the need for developers to learn a new system. However, that’s not where we’re at today. The Fields API never made it past the gatekeepers, and developers have one more thing to stay knowledgeable on.</p>\n\n\n\n<p>The question is: how do we address this going forward?</p>\n\n\n\n<h2>How the Gutenberg Project Can Solve the Fields API Problem</h2>\n\n\n\n<p>What many don’t understand is that the Gutenberg project is larger than the content editor. The first iteration, Phase 1, of the project was to create a new editing experience. Phase 2 will create new admin screens for site editing using the same components for the editor. Custom text fields, select dropdowns, color options, or one of many other field types all run through the same reusable, component-based system.</p>\n\n\n\n<p>That sounds remarkably similar to the Fields API. At the end of the day, the Fields API is simply a standardized method of reusing components to output form fields and save data, regardless of the screen in WordPress.</p>\n\n\n\n<p>WordPress needs to be rebuilt from the ground up. Gutenberg provides us the opportunity to rewrite every admin page in WordPress using a standardized system for handling form fields.</p>\n\n\n\n<p>From a technical standpoint, Gutenberg has <a href=\"https://github.com/WordPress/gutenberg/tree/master/packages/components/src\">dozens of components</a>. These include a text control, button, checkbox, and much more. It covers the majority of use cases plugin and theme authors need for form fields. These things are not tied directly to the block system. They are simply components that can be used anywhere.</p>\n\n\n\n<p>The next step would be setting the foundational layer for other admin screens. It will not be easy. There will be backward-compatibility mountains that the Fields API could have climbed for us years ago.</p>\n\n\n\n<p>Given WordPress’ history, developers will likely continue using competing APIs for fields on various admin pages. And, if we’re still at that point in five years, the Gutenberg project will have failed for not going as far as it could have.</p>\n\n\n\n<p>For success, the Gutenberg project needs to have a wider vision and a longer-term roadmap that addresses the issues of fields on every screen. Otherwise, projects with easier-to-learn APIs will be more enticing to developers.</p>\n\n\n\n<p>The idea of <em>Gutenberg-ifying</em> the entirety of the WordPress admin will be off-putting to many, but WordPress has to solve its form fields issue at some point. It might as well reuse the components that will be seeing active development for years to come.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 20 Jan 2020 21:29:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:74:\"WPTavern: Blocksy WordPress Theme Provides a Solid Block-Editor Experience\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96555\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/blocksy-wordpress-theme-provides-a-solid-block-editor-experience\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7060:\"<img />Screenshot of the Blocksy theme blog posts page.\n\n\n\n<p>Creative Themes dropped version 1.6.8 of its <a href=\"https://wordpress.org/themes/blocksy/\">Blocksy WordPress theme</a> yesterday. It was an update to a theme that is quickly becoming popular, having garnered 58 five-star reviews and one thousand active installs since it first went live in the WordPress theme directory. The theme is specifically built to work with the block editor and is a nice example of what is currently possible with blocks.</p>\n\n\n\n<p>Blocksy is billed as a general-purpose theme and also works with other popular page builders like Elementor, Beaver Builder, and Visual Composer. The truth-test is whether it handles the block editor, especially given its primary audience (it is named <em>Blocksy</em>, after all). Aside from a few trivial quirks, the theme handled nearly every bit of test content I threw at it.</p>\n\n\n\n<p>Blocksy is one of the better-designed free themes for the block editor that I have seen.</p>\n\n\n\n<p>I want to use this theme for a project. Unfortunately, I have no site to use it on at the moment. I do not say this about many free, repository-hosted WordPress themes. The quality of work is on par with themes from the majority of commercial theme shops I have tested or used over the years.</p>\n\n\n\n<p>The theme is not without a few issues, which we’ll get to, but it is a solid offering.</p>\n\n\n\n<h2>Block Design</h2>\n\n\n\n<img />A few block design examples from the theme.\n\n\n\n<p>With a name like <em>Blocksy</em>, I went into this review with a mindset that the theme better handle every test block I dropped into the block editor with grace. I wanted to make sure it lived up to its name.</p>\n\n\n\n<p>I am happy to report that it handles block design as good as or better than most themes designed for showcasing the block system. It adds just enough stylistic flair, such as a unique pull-quote design, without getting in the way of the content.</p>\n\n\n\n<p>One problem area is the font in the editor does not match the font on the front end completely. This is a minor issue that should be easily fixed in an update.</p>\n\n\n\n<p>You can find some good examples of block design on the theme’s <a href=\"https://demo.creativethemes.com/blocksy/main/gutenberg/\">Gutenberg demo page</a>.</p>\n\n\n\n<h2>Block Editor Sidebar</h2>\n\n\n\n<img />Custom block editor sidebar for post meta.\n\n\n\n<p>The latest update of the theme includes additional integration with the block editor. The team moved its old meta box, which sat below the post content editor, to a new sidebar panel. This change is refreshing.</p>\n\n\n\n<p>I did not know the meta box existed until the theme developers pointed out this change in feature (I first started testing the previous version of the theme). At this point, I never look at the bottom of the block editor for meta boxes. I expect any additional settings to be placed firmly in the right sidebar area. I applaud this move. It could confuse old theme users when updating, but it feels more natural in its new home.</p>\n\n\n\n<p>The team has done a nice job with this custom sidebar for the most part. The biggest issue is with the button for switching to it. By using both an icon and the “Page Settings” text, it uses more room than necessary. To fit in line with the existing UI, it should simply display an icon. The button text is also hard to read when selected, which is a minor CSS issue that can be corrected in an update.</p>\n\n\n\n<h2>Customizer Options</h2>\n\n\n\n<img />Custom-designed customizer control panel.\n\n\n\n<p>For users who like to have full control over the site’s display, this theme won’t disappoint. For users who dislike by many options, the number of design settings will likely feel overwhelming. </p>\n\n\n\n<p>Blocksy has more design options than most people will ever need. Some options, such as letter-spacing and line-height controls for fonts may be going overboard. Ideally, those things would be automatically adjusted based on the chosen font family.</p>\n\n\n\n<p>The theme also uses a custom design for the customizer control panel. In general, the custom design looks nice. However, is not good practice for themes to customize a shared WordPress UI element. Plugins with options in the customizer could break. It is best to stick with the default design.</p>\n\n\n\n<h2>Blocksy Companion Plugin</h2>\n\n\n\n<p>The theme promotes an additional plugin named Blocksy Companion. The add-on plugin provides users with additional widgets, a cookies-consent feature for the front end, and integrations with Mailchimp, Instagram, and WooCommerce. It also provides an avenue for importing custom-made demo content.</p>\n\n\n\n<p>Most of the companion plugin’s features are fairly routine compared to similar themes in the WordPress theme repository. The cookies-consent feature is something I haven’t seen before as part of a theme add-on plugin.</p>\n\n\n\n<p>My biggest complaint with the plugin is that it makes the “Blocksy” admin menu item a top-level item. It is a waste of valuable real estate in an already-cluttered admin menu. Plus, there is no good reason for a single theme/plugin screen to take a top-level spot when it has no sub-menus.</p>\n\n\n\n<h2>How Does the Code Look?</h2>\n\n\n\n<p>If I were describing the code in one phrase: <em>average but gets the job done</em>.</p>\n\n\n\n<p>The theme has a lot of PHP code. Most of it is dropped into a single <code>/inc</code> folder and not organized nearly as well as it could be. It feels like a giant mish-mash of functions with almost non-existent inline documentation for most of them. It’s not something a developer who is not intimately familiar with the theme would want to dive into.</p>\n\n\n\n<p>This is not an argument that the theme’s code is bad. It passed the official WordPress.org review process and made it into the theme directory, so it is at least doing the minimum necessary. It’s simply unimpressive, which is par for the course when it comes to most WordPress themes. Code architecture seems like an afterthought, which could make it tougher to maintain over the long haul. With a theme that has as much code as this one, this is more important than it is for simpler themes. It can also easily be remedied with a week or so of dev time strictly devoted to architecture.</p>\n\n\n\n<h2>Final Thoughts</h2>\n\n\n\n<p>Blocksy is a well-designed theme that does the job it sets out to do. It is ideal for users who are working with the block editor or a third-party page builder. The theme is packed with far more options than I could cover in this review. If customizability is your thing, you will likely enjoy it.</p>\n\n\n\n<p>The team shared some of their future ideas. They have plans to add conditional headers, footers, and sidebars; a sticky header; AMP support; and more. They seem excited about the future of the theme.</p>\n\n\n\n<p>Overall, I would recommend this theme for users who want a clean, relatively fast, block-ready WordPress theme.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 17 Jan 2020 21:34:37 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:51:\"WPTavern: WordCamp Houston Returning After 10 Years\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96499\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://wptavern.com/wordcamp-houston-returning-after-10-years\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4308:\"<img />\n\n\n\n<p>After a 10-year hiatus, <a href=\"https://2020.houston.wordcamp.org/\">WordCamp Houston</a> will return in 2020. The event will run from May 9-10 at the Hilton Houston NASA Clear Lake and expects 250-300 attendees. The team behind the Texas-based WordCamp is still in the process of putting the event together and is looking for volunteers, speakers, and sponsors.</p>\n\n\n\n<p>With 10 years between events, local organizers had to rebuild their WordPress community. “After <a href=\"https://wptavern.com/it-took-houston-four-years\">WordCamp 2010</a>, the community seemed to have dismantled,” said <NAME>, lead organizer for WordCamp Houston. “I can only guess that because it takes an active community and dedicated volunteers, that if any piece starts to have trouble, it becomes challenging to continue,” she speculated as to why the original event never continued.</p>\n\n\n\n<p>Hawkins began the Sugar Land meetup, located south of Houston but a greater part of the Houston area. The overall area has several regular WordPress meetups. “<NAME> and a few others were instrumental in building the community again,” she said. “They were dedicated and made sure we had regular monthly meetings with quality speakers.” Currently, they have 12 wranglers who are working to make sure this year’s WordCamp runs smoothly.</p>\n\n\n\n<p>Considering that Houston is the hometown of <NAME>, the co-creator of WordPress, it would seem like the city would be the ideal location for an annual WordPress event. He is not involved in the event or currently on the speaker roster, which is still open. Hawkins hopes that he can at least attend the event in an unofficial capacity. “I want to iron out any wrinkles first and present a flawless WordCamp for him,” she said. “We expect 2020 to be a WordCamp that knocks it out of the park, but I want to make sure we represent WordPress in the best light and formally invite him as a keynote next year.”</p>\n\n\n\n<p>WordCamp Houston is currently <a href=\"https://2020.houston.wordcamp.org/call-for-speakers/\">accepting speaker applications</a>. The process will remain open until February 29. Those who want to speak should submit a topic and plan for a session that lasts 30-40 minutes.</p>\n\n\n\n<p>“<NAME> is our Speaker Wrangler,” said Hawkins. “Since this is the first one in years, she has been actively training future speakers. We had an in-person workshop last fall and we are preparing a webinar series soon that will be broken up in chunks.”</p>\n\n\n\n<p>Thus far, the event organizers have received 29 applications and are expecting more. They will evaluate applications from the first of March and let speakers know if their session is approved on March 15.</p>\n\n\n\n<p>The team is still on the hunt for sponsors. “We have the national sponsors, which is very helpful, but we are in the process of getting the word out locally,” said Hawkins. “Most of Houston has never heard of WordCamp so it’s up to us to start knocking on doors. We have a long list of people and companies that we are reaching out to.”</p>\n\n\n\n<p>Individuals or businesses who wish to sponsor the event can sign up via the <a href=\"https://2020.houston.wordcamp.org/become-a-sponsor/\">sponsorship page</a>. There are four tiers, ranging from $150 to $3,000, with various perks for each level.</p>\n\n\n\n<p>The team chose the Hilton Houston NASA Clear Lake venue for this year’s event. The location was ideal because it had a good room setup, which could allow them to expand in case they had an increase in attendance. They can also add an extra room if they need to add another speaker track.</p>\n\n\n\n<p>“It’s also close to NASA which fits our overall theme of ‘Taking Off!\'” said Hawkins.</p>\n\n\n\n<p>The team initially had some trouble finding a venue that met their needs, budget, and location. “Houston is a vast city, and it is not very easy to manage so many people that live all over,” said Hawkins. “I am sure other cities like Atlanta, LA, and Chicago have the same problem with having a vast city that can extend to an hour drive in each direction.”</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Jan 2020 19:59: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:14:\"<NAME>\";s: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:79:\"Post Status: Introducing a new chapter, with <NAME> as 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:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"https://poststatus.com/?p=73897\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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:\"https://poststatus.com/cory/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4335:\"<p>I <a href=\"https://poststatus.com/launched/\">created</a> Post Status in January 2013 and <a href=\"https://poststatus.com/lets-grow/\">started</a> the Club in January 2015. January 2020 marks another huge milestone for this community and business.</p>\n\n\n\n<p>I’m very excited to share that <a href=\"https://corymiller.com/\"><NAME></a> is now an equal partner of Post Status. Cory purchased half the business and will be working with me in the day-to-day management, writing, community engagement, and everything else we do with Post Status.</p>\n\n\n\n<p>Many should know Cory from his ten years running <a href=\"https://ithemes.com/\">iThemes</a>. After they sold the business to Liquid Web and he spent some time there, he decided to step away and continue his entrepreneurial journey. He’s working on a few projects, and Post Status is a significant part of where he’s dedicating his time and energy.</p>\n\n\n\n<p>Cory is a long-time friend, and iThemes has been a Post Status sponsorship partner since 2015. Cory understands the community, the role Post Status plays in the space, and he brings so much to the table, from established community relationships to product and business experience.</p>\n\n\n\n<p>We’ve known one another going back to 2010 or so. I got to watch as he navigated the WordPress space as the CEO of a theme company turned plugin company, from inception to exit.</p>\n\n\n\n<p>Cory has so many qualities I admire. Most of all, I admire his honesty, his compassion, his passion for people, and his vision for what’s possible. I look forward to working with a true partner on Post Status after so many years of managing the primary responsibilities with much help from many friends and contractors along the way.</p>\n\n\n\n<p>In addition to Cory and myself, <NAME> and <NAME> continue to be integral parts of the Post Status effort. Cory and I are thankful for their energy, consistency, and talents.</p>\n\n\n\n<p>We are working together in Oklahoma City this week to finalize our plans for the 2020 year. We already have a lot planned and are looking to get these new initiatives and processes off to a rocking start.</p>\n\n\n\n<h3>Potential in the WordPress community</h3>\n\n\n\n<p>There is so much potential in the WordPress community, and Post Status plays an important role through news, community, and professional development. We are going to continue to do that, and we are also going to make changes that we think will benefit the community as a whole and Post Status Club Members in particular.</p>\n\n\n\n<p>If you’ve ever thought about joining the <a href=\"https://poststatus.com/club\">Post Status Club</a>, it’s a great time to do so. At a minimum, anyone in the WordPress community should subscribe to the <a href=\"https://poststatus.com/newsletter\">newsletter</a>. If you’ve been a member before, we thank you, and we hope we are able to continue to serve you for years to come — better than ever, better together.</p>\n\n\n\n<h3>Cory\'s thoughts</h3>\n\n\n\n<p>I asked Cory to share a couple of his own thoughts on why he’s investing in Post Status, both with his money and energy.</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>I’ve been a fan and supporter of Post Status since the beginning. At iThemes we were one of Brian’s first sponsors. Over the years I leaned on Brian’s insights and counsel — personally as well as through Post Status — to inform and grow iThemes.</p><p>When Brian approached me about becoming a partner my first reaction was, “Heck yes!” Over our weeks and months of conversations, my excitement grew and grew as our goals and aspirations for Post Status were revealed to be so well aligned.</p><p>I truly believe in what Brian has built. And I only want to be a value add and look forward to coming alongside Brian, the Post Status team and this great community.</p></blockquote>\n\n\n\n<p>We\'re so excited to finally be able to make this official. We look forward to continuing to serve you our readers, our Club members, our partners, and the broader community.</p>\n\n\n\n<p>Onward!</p>\n\n\n\n<h3>Audio & Video Q&A; with Cory and Brian</h3>\n\n\n\n<p>We’ll be announcing more specific plans over the coming weeks, and below is our conversation post-announcement by audio and video:</p>\n\n\n\n\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<div class=\"embed-vimeo\"></div>\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Jan 2020 13:55: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:15:\"<NAME>\";s: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:16:\"Matt: Thirty Six\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=50760\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:33:\"https://ma.tt/2020/01/thirty-six/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3332:\"<p>I am now solidly entering my late thirties, and fortunately I am in good health, good cheer, and doing one of my favorite things — exploring a part of the world and culture I haven’t experienced before (Maldives and Sri Lanka).</p>\n\n\n\n<p>The past year has included a number of professional milestones including <a href=\"https://ma.tt/2019/09/series-d/\">a significant amount of fundraising</a> and related activity, bringing in <a href=\"https://ma.tt/2019/08/tumblr-the-day-after/\">a major new product to the Automattic family</a>, the <a href=\"https://ma.tt/2019/11/state-of-the-word-2019/\">maturation of Gutenberg in the WordPress ecosystem</a>, launching the <a href=\"https://distributed.blog\">Distributed blog and podcast</a>, and a growth in the breadth and depth of the Automattic team.</p>\n\n\n\n<p>Partially because of the schedule those milestones required, this ended up being my year with the most travel ever since I started tracking: I flew over 515k miles, to 124 cities in 24 countries. I was able to incorporate a <a href=\"https://photomatt.tumblr.com/post/186959053572/some-beautiful-trails-near-aspen-ran-the-heavy\">good amount of running</a> in my routine, started picking up musical instruments again, and learning more about sound and its impact on our lives. I found <a href=\"https://streaksapp.com/\">small daily habits</a>, like a little bit of exercise or stretching first thing in the morning, to be sustainable and high-impact.</p>\n\n\n\n<p>What suffered in 2019 was my <a href=\"https://ma.tt/2020/01/29-books-in-2019/\">book reading time</a> and making a dent on the <a href=\"https://www.theworlds50best.com\">top 50 list</a>. I still check <a href=\"https://www.techmeme.com\">tech news every day</a>, but I had to unplug from daily non-tech news because it was just too hectic — I’ve found a lot of value in <a href=\"https://www.economist.com\">weekly publications like the Economist</a> to make sense of what’s going on in the world with the benefit of a little distance and time.</p>\n\n\n\n<p>Personally my main goals this year are for the health and wellness of my family, incorporating more playing music and photography into my life, and strengthening <a href=\"https://www.calm.com\">my meditation practice</a>. If you’re reading this, I hope to run into you online or in person and this year let’s do our best together to leave the world a little better than we found it.</p>\n\n\n\n<p>All birthdays: <a href=\"https://ma.tt/2003/01/bday/\">19</a>, <a href=\"https://ma.tt/2004/01/so-im-20/\">20</a>, <a href=\"https://ma.tt/2005/01/hot-barely-legal-matt/\">21</a>, <a href=\"https://ma.tt/2006/01/matt-22/\">22</a>, <a href=\"https://ma.tt/2007/01/twenty-three/\">23</a>, <a href=\"https://ma.tt/2008/01/twenty-four/\">24</a>, <a href=\"https://ma.tt/2009/01/twenty-five/\">25</a>, <a href=\"https://ma.tt/2010/01/twenty-six/\">26</a>, <a href=\"https://ma.tt/2011/01/twenty-seven/\">27</a>, <a href=\"https://ma.tt/2012/01/twenty-eight/\">28</a>, <a href=\"https://ma.tt/2013/01/twenty-nine/\">29</a>, <a href=\"https://ma.tt/2014/01/matt-3-0/\">30</a>, <a href=\"https://ma.tt/2015/01/thirty-one/\">31</a>, <a href=\"https://ma.tt/2016/01/thirty-two/\">32</a>, <a href=\"https://ma.tt/2017/01/thirty-three/\">33</a>, <a href=\"https://ma.tt/2018/01/thirty-four/\">34</a>, <a href=\"https://ma.tt/2019/01/thirty-five/\">35</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Jan 2020 09:15: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: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: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:62:\"WordPress.org blog: WordPress Leaders Nominated for CMX Awards\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=8288\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wordpress.org/news/2020/01/wordpress-leaders-nominated-for-cmx-awards/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3074:\"<p>Two members of the WordPress leadership team were nominated for excellent work in their field in the first ever Community Industry Awards. <a href=\"https://profiles.wordpress.org/andreamiddleton/\"><NAME></a> is nominated for <a href=\"https://cmxhub.com/awards-executive\">Executive Leader of a Community Team</a> and <a href=\"https://profiles.wordpress.org/chanthaboune/\"><NAME></a> is nominated for <a href=\"https://cmxhub.com/awards-professional\">Community Professional of the Year</a>.</p>\n\n\n\n<img src=\"https://i0.wp.com/wordpress.org/news/files/2020/01/josepha_and_andrea.jpg?fit=632%2C281&ssl=1\" alt=\"\" class=\"wp-image-8292\" />\n\n\n\n<p><a href=\"https://cmxhub.com/\">CMX</a> is one of the largest professional organizations dedicated to community builders. The awards were open to public nomination, and finalists were chosen by panels of their peers in the CMX community.</p>\n\n\n\n<p>Andrea has been a vital community strategist for the WordPress project since 2011. Her work to build and support a vibrant community has played a part in the success around the popular open source CMS. Her work is sponsored by Automattic, where she leads a team that focuses on educational efforts, funding, and in-person community-driven events that serve a global base.</p>\n\n\n\n<p>Josepha has been the Executive Director of the WordPress project since 2019. Her work to coordinate and guide volunteer efforts spans 20 teams and involves thousands of volunteers. Her work is also sponsored by Automattic, where she leads the open source division that focuses on all aspects of open source contribution including design, development, volunteer engagement, and the health of the overall WordPress ecosystem.</p>\n\n\n\n<h2>Votes are Open</h2>\n\n\n\n<p>Final recipients are chosen with open voting — if you feel like either Andrea or Josepha have had an impact on your careers, your trajectory in the WordPress project, or the health of WordPress as a whole, there are three ways you can show your support:</p>\n\n\n\n<ul><li>Stop by and vote for them (Andrea <a href=\"https://href.li/?https://cmxhub.com/awards-executive\">here</a>, Josepha <a href=\"https://href.li/?https://cmxhub.com/awards-professional\">here</a>)!</li><li>Share this post with your own communities!</li><li>Tweet some inspirational thoughts about your time/experience/learnings with WordPress (using #WordPress, naturally)!</li></ul>\n\n\n\n<h2>Thank You Notes</h2>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>A lot of care and passion goes into making the WordPress Project as fantastic as it is. I think these awards are a reflection of how wonderful the community and ecosystem are, and I appreciate everyone’s continued trust in my stewardship!</p><cite><NAME></cite></blockquote>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>WordPress community organizers are some of the most generous and creative people in the world — working with them is exciting and interesting every day. I’m humbled by this nomination; thank you!</p><cite><NAME></cite></blockquote>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Jan 2020 21:42: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:16:\"<NAME>\";s: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:67:\"WPTavern: Get Involved With Block-Based WordPress Theme Experiments\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96502\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/get-involved-with-block-based-wordpress-theme-experiments\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4426:\"<p>As the WordPress theme review team wound down their team meeting yesterday, they were finalizing what their focus area for 2020 would be. The general agreement among members was that block-based themes should be at the top of the list. There was some pushback from a minority that did not want to see block-based themes at all. The reality is that themes will be changing in the next year or two.</p>\n\n\n\n<p>As a team, this is the group of people who will ultimately need to set guidelines based on something WordPress has never done before. They will also need to work diligently to bring theme authors up to speed on how themes of the future will be built.</p>\n\n\n\n<p>At this point, there are many unknowns, but work on <a href=\"https://github.com/WordPress/gutenberg/labels/%5BFeature%5D%20Full%20Site%20Editing\">tickets for full-site editing</a> is happening at a quick pace.</p>\n\n\n\n<p><NAME>, Theme Imagineer at Automattic, later invited team members to get involved with the <a href=\"https://github.com/WordPress/theme-experiments\">Theme Experiments project</a> on GitHub. It is a way for developers in the WordPress community to help steer the theme-development ship. Currently, the repository is fairly bare-bones and represents only the early work toward creating themes from blocks. Each sub-directory in the repository will be an individual experiment that explores creating themes using blocks or block templates.</p>\n\n\n\n<p>The <a href=\"https://wptavern.com/initial-documentation-for-block-based-wordpress-themes-proposed\">initial documentation</a> for block-based themes was introduced in early December 2019. Since then, a handful of contributors have put together some working theme examples to get the ball rolling.</p>\n\n\n\n<p>The repository is <a href=\"https://github.com/WordPress/theme-experiments/blob/master/CONTRIBUTING.md\">open to contributions</a> from anyone. This would be a good moment for members of the larger theme development community to start sending in pull requests to share their experiments.</p>\n\n\n\n<p>To test any of the experiments in this repository, you need to be running the latest version of the Gutenberg plugin. You must also enable the “Full Site Editing” and “Full Site Editing Demo Templates” options from within the plugin’s “Experiments” screen.</p>\n\n\n\n<h2>Parisienne Theme</h2>\n\n\n\n<img />Screenshot of the Parisienne theme.\n\n\n\n<p>Currently, the only approved theme experiment is the Parisienne theme. It’s a test of how block templates and template parts work. A <a href=\"https://parisiennetheme.mystagingwebsite.com/\">live demo</a> of the theme is available.</p>\n\n\n\n<p>Don’t expect to be blown away. There are many missing pieces in the Gutenberg plugin, such as blocks for displaying posts and similar items. The idea is to explore how templating will work and provide feedback to the Gutenberg development team.</p>\n\n\n\n<p>One major concern I have at this point is the flat nature of the two sub-directories for housing templates and template parts. With the seven template part files in this theme, I worry that we are not learning from the mistakes of the past. The sub-folders could become unruly, particularly <code>/template-parts</code>, and house dozens upon dozens of files in a real-world scenario. This is no different from how themes currently work other than the location of the template files. Now would be a good time to reimagine the folder structure and optimize the organization of theme templates. For example, group sidebar templates under a <code>/template-parts/sidebar</code> folder instead of dumping everything into one location.</p>\n\n\n\n<h2>Twenty Nineteen and Twenty Twenty</h2>\n\n\n\n<img />Early look at a block-based Twenty Nineteen theme.\n\n\n\n<p>The repository has two open pull requests for experimenting with blocked-based versions of the <a href=\"https://github.com/WordPress/theme-experiments/pull/4\">Twenty Nineteen</a> and <a href=\"https://github.com/WordPress/theme-experiments/pull/5\">Twenty Twenty</a> default themes. Of the two, the Twenty Nineteen Blocks theme seemed the least broken, despite the original not being designed specifically for the block editor.</p>\n\n\n\n<p>Porting the most recent default WordPress themes is important because it provides theme authors a way to compare how old methods of handling features will work in the new block system.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Jan 2020 21:39: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:14:\"<NAME>\";s: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:116:\"HeroPress: How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=3037\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:118:\"https://heropress.com/essays/starting-early-in-tech/#utm_source=rss&utm_medium=rss&utm_campaign=starting-early-in-tech\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:34324:\"<img width=\"960\" height=\"480\" src=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/011320-min-1024x512.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"Pull Quote: WordPress people tend to be generous, trusting, and helpful.\" /><p><a href=\"https://heropress.com/feed/#indonesian\">Esai ini juga tersedia dalam bahasa Indonesia.</a></p>\n<p>Growing up, I’ve always been surrounded by technology.</p>\n<p>My dad is a programmer, he created my Gmail account and my first blog on Blogger (Blogspot) when I was 10 years old (it’s around 2006?). I filled up my blog with posts resembling diary entries. The content became too private eventually, so I decided to set it on private.</p>\n<p>Besides that first blog, I had about 5 other blogs on Blogger. One was for posts I believed not too private and could be consumed by the public, one was for my class’ blog in middle school, and one for me to learn how to write in English. I don’t remember what the other blogs are for, since I just kept creating and deleting them. I got satisfaction and happiness from pouring my thoughts in writing and publishing them in my blog. Many times, writing my thoughts and feelings helped me process them, even until now.</p>\n<p>Fast forward to high school graduation. Since I love languages (English is one of my favorite subjects!), I actually wanted to major in English in a top public university in my country, but I didn’t get in, so my second option was Information Systems in a private university. There, I learned a lot about IT and business, I learned Java, HTML, CSS, Javascript, and Android programming. I even took some Coursera and Codecademy courses to learn Bootstrap and Ruby on Rails. I was a good student, I love learning the algorithms and I did more than okay, but I didn’t love programming. I’m not that people who can stay calm finding errors in their codes, and then finding out that it’s only missing a character.</p>\n<h3>Meeting WordPress for the first time</h3>\n<p>At that time, my parents built some websites to sell backlinks (don’t hate me). I helped them with the sites, mainly proofreading and formatting the articles, and they would pay me. That’s when I first encountered WordPress. I saw WordPress as something more advanced than Blogger, with more themes and plugins to choose from. The default WordPress websites already looked more professional than Blogger does.</p>\n<p>I also like to earn extra money (who doesn’t?), so I helped a teacher in my neighborhood teaching high school students from my old high school. I don’t know how to explain this, but in Indonesia, it’s common to take extra courses (outside the school) to learn what you’re already taught at school and prepare for tests. So it’s another 2-hour study time after school.</p>\n<p>During another semester, I taught English at a Kumon center (it’s a Japanese franchise for math and English). I also taught about 10 of my peers for 2 semesters and got a pretty good discount for my tuition as a reward. At home, I tried every legal and safe method available to make money online. Some worked, like translating texts from English to Indonesian on Gengo and writing articles in English on Zerys. Some, like online surveys, didn’t. I also created an Upwork account and applied to some jobs there, but I never got one.</p>\n<p>In my last year at university, I had to do a year-long full-time internship. I got mine at a big general insurance company as their IT QC Staff. I learned a lot and met many amazing people there, but when I was offered to continue working there as a Business Analyst, I said no. I wanted to apply for a scholarship for a masters’ degree. And I don’t really like the fact that I have to wake up at 6 and be back home at 7 in the evening and do it all over again the next day.</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image2.jpg\"><img /></a>With my colleagues, I’m the one with the white blouse.\n<p>But one thing I realized just now when I’m writing this is, the whole remote work wouldn’t have happened without the internship. My daily 1.5-hour commute to work made me read Medium everyday. And reading people’s stories on Medium made me want to write and share my stories, so I started writing and sharing my stories there. You’ll see in the next 2 paragraphs the significance of this Medium profile in my career.</p>\n<h3>Start working remotely</h3>\n<p>So after the internship, while I prepared for the scholarship application, I went back to my Upwork profile, revised it, and applied to some jobs as a virtual assistant. Starting from a very low pay, I did everything, like formatting WordPress posts (surprise!), designing social media posts, and processing orders for online shops. I work with people from Singapore, Australia, Europe, and America. After a few happy clients, I increased my hourly rate, slowly but surely. I got familiar with common tools used in a remote work setting, like Slack, Asana, Trello, and Google Suites. I also started writing in English a lot more, on my personal blog on WordPress.com and my Medium.</p>\n<p>One day, around 3 months after I started, a job opening on Upwork caught my attention. They’re a WordPress plugin company called Caldera Labs/Caldera Forms, and they’re looking for someone who could deliver consistency on their blog. They want to publish one blog post per week. I sent my proposal along with my Medium profile URL. <a href=\"http://christiechirinos.com\">Christ<NAME></a> then replied to my proposal. I remembered she mentioned checking my writings on Medium and that I have a ‘great writing tone’. She wanted to ‘meet’ me in video, so she sent me a Calendly link. I notified her that I would be available at 5 a.m. my time. That was my first time seeing Calendly.. (Calendly is awesome!).</p>\n<p>That was also my first time having to be interviewed via video call. I was ecstatic, but panicked. On the day, I woke up at 4, got dressed, and opened my laptop. Weirdly, my wi-fi died that morning. So I went to the nearest McDonalds to get the interview done, and it went great!</p>\n<p>Long story short, I continued to work with my other clients and started working with Caldera Forms for 15 hours a week. Besides Christie, I also met <a href=\"https://twitter.com/Josh412\"><NAME></a>, Ariella, Anchaal, Rosa, Nico, and Swapnil. At first, I was only tasked with formatting blog posts on WordPress following their style guide. Then I was involved in their overall content strategy, like crafting onboarding emails and coordinating with guest writers. But I’ve always felt welcomed since day one at Caldera Forms. We’re a team of only 5-6 people, we had monthly all-hands video meetings, we talked about our day in Slack. It wasn’t like with any of my clients.</p>\n<p>Christie and Josh are also very active in the WordPress community, they had introduced me to the ‘right’ people to connect with. In order to do that, I had to make an account on WordPress’ Slack. I got to know the amazing community behind WordPress. How people voluntarily contribute their time, energy, and skills to the community, from development, marketing, to translating. It was really inspiring. During my time with Caldera Forms, I also went to my first WordCamp, WordCamp Jakarta 2018, sponsored by Caldera Forms!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image3.jpg\"><img /></a>Some swags from WordCamp Jakarta 2018, that’s Wapuu ondel-ondel!\n<p>It’s only natural then that I wanted to have my own WordPress website. I had a WordPress.com blog once, but this one is different. You can see <a href=\"http://ascenciafike.com\">my blog here</a>. I felt like a grown-up using WordPress.</p>\n<h3>Transitioning to full-time</h3>\n<p>One day, Caldera Forms was acquired by <a href=\"http://saturdaydrive.com\">Saturday Drive</a>, the company behind <a href=\"http://ninjaforms.com\">Ninja Forms</a>. Josh, Nico, Rosa, and I ‘moved’ there, too. Josh introduced me to <a href=\"http://jameslaws.com\"><NAME></a>, the CEO. But because I was still freelancing and have a few other clients, we used my old contract on Upwork. Saturday Drive was much bigger than Caldera, with 20+ people onboard, and I was really excited! They have product team, support team, and communications team. When we moved there, they’re also in another big transition, which was switching to remote work.</p>\n<p>After a month working with Saturday Drive using the old contract, James offered me a full-time position to manage their affiliate program. It was morning in the U.S., but it’s already 8 p.m. where I live. I was <i>really</i> excited, but it’s also a really hard decision to make. Taking the offer would mean letting go all of my clients and specializing in one side of digital marketing, which is affiliate marketing. I would also have to work 8 hours a day. I stayed up late that night, discussing the possibilities with my parents.</p>\n<p>The next day, I replied to James’ message and accepted his offer.</p>\n<p>It’s been more than 4 months since I started working with Saturday Drive now (time of writing: January 2020). Obviously, it’s different from freelancing, but I love almost every moment of it.</p>\n<p>We use Basecamp instead of Slack, where we set up different questions for different times of the week. Every Wednesday, we would be asked: “What do you look like today?”. There are also questions like “What are you looking forward to most this week?”, “What were the highlights of your work day today?”, and “Read any good books lately?”. We even have fiction and non-fiction book clubs!</p>\n<p>We also use Basecamp’s method of working, called <a href=\"https://basecamp.com/shapeup\">Shape Up</a>. We work on projects in a six-week cycle, and then we’ll have two weeks of cooldown. In the cooldown period, we get to work on things we want to work on. And before the next cycle starts, we’ll submit pitches about the projects we want to work on next.</p>\n<p>What about video calls? We have a big monthly meeting with all team members, and occasional coffee break chats with 4-5 people. If urgently needed, we would also have video calls for projects. Except for these calls, I work in my time zone’s working hours.</p>\n<p>So far, I love working with Saturday Drive and getting to know the people. Although I can’t really relate to the U.S. culture (almost all of the team members are U.S. based), I relate to the values that Saturday Drive has. Most importantly, I’m proud of the work we’re doing!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image1.png\"><img /></a>We have virtual ‘coffee breaks’.\n<h3>Giving back to the WordPress Community</h3>\n<p>Notice the pattern in my story?</p>\n<p>WordPress people tend to be generous, trusting, and helpful, because the WordPress itself is open-source. WordPress is powered by volunteers, kind people from all over the world doing development, marketing, translation, support, and many more. There are WordPress meetups, local and regional WordCamps, which are organized by organizers and volunteers.</p>\n<p>Because I’ve experienced the generosity of the WordPress people, I wanted to give back to the community. Several months ago, I tried contributing to the Marketing team by attending a few weekly meetings on Slack. But I eventually stopped attending because I was too busy with work (and the meetings are at 10 pm my time).</p>\n<p>Around November 2019, <NAME> from WordPress Indonesia contacted me through Instagram DM. She invited me to join PerempuanWP, an initiative for Indonesian women working in the WordPress world, similar to WomeninWP. So I followed <a href=\"https://twitter.com/PerempuanWP\">@PerempuanWP</a> on Twitter and joined the WordPress Indonesia’s Slack. Not long after that, I contributed to Indonesia’s polyglot team as well, translating the Code of Conduct and revising our Translation Style Guide.</p>\n<p>Currently, I’m preparing an <a href=\"https://wp-id.org/kulgram-4-onboarding-e-mail/\">‘online webinar’ on Telegram</a> and <a href=\"https://wp-id.org/wpjkt-meetup-21-onboarding-email-and-woocommerce-theme-for-your-business\">a talk for WordPress Meetup Jakarta</a>, both about email marketing (both will be done by the time you’re reading this).</p>\n<p>By putting myself out there, or here in this article. I want to represent Asian women. In the future, I hope I can inspire more women, especially Asians, to work remotely.</p>\n<h3>What you should do if you want to work remotely</h3>\n<p>If you’re an introvert, working remotely may sound like a dream come true. Without leaving the comfort of your house (or even your pajamas), you can still work and earn money. But, it’s not all rainbows and butterflies. From my experience, here’s what you should prepare if you want to work remotely.</p>\n<ol>\n<li>You should be comfortable working with computers. All day.<br />\nAt least you can do a basic Google search, because that’s where most of the answers are, especially if you want to start as a general virtual assistant. Take care of your eyes. Stand up and walk around once in awhile.</li>\n<li>It gets boring. You should be OK with <i>not </i>meeting people all day.<br />\nSometimes you just have to focus on your work so much that you can’t afford to get out of the house. But sometimes, the only way to have that focus is to get out of the house and work from a cafe. Just find the balance you need, it’ll get better with experience.</li>\n<li>Learn the English language. Or other international languages.<br />\nIf you want to work internationally, this one is crucial. You won’t be able to work with people from another country if you can’t speak their language.</li>\n<li>Do your best in your current job.<br />\nOne of the best books I’ve read this year was So Good They Can’t Ignore You by Cal Newport. “Don’t follow your passion; rather, let it follow you in your quest to become, in the words of my favorite Steve Martin quote, “so good that they can’t ignore you.”” So, instead of trying to find your passion, enjoy the work you’re doing at the moment, try to master it, and adopt the craftsman mindset. Collect as many skills as you can, and see what those skills can do for the world.<br />\nTLDR; don’t be obsessed with wanting to work remotely. The opportunity will come, eventually.</li>\n<li>Don’t settle for mediocrity.<br />\nJust learn things. As much as you can. From anywhere, about anything. Keep an open mind. Read books, listen to podcasts, and learn new skills.</li>\n<li>Join the community.<br />\nIf you’re working in the WordPress world, join the WordPress community. It’s a great place to learn from and connect with great people.</li>\n</ol>\n<p>Of course, I won’t be able to tell you to follow the same path that I took, but I hope my story and the pointers above can help you to pursue the (remote) career you want.</p>\n<hr />\n<h2 id=\"indonesian\">Bertumbuh bersama teknologi</h2>\n<p>Saya sudah dikelilingi teknologi sejak kecil.</p>\n<p>Papa saya adalah seorang programmer yang familier dengan teknologi. Saat umur saya 10 tahun, Papa membuatkan akun email Gmail dan blog pertama saya di Blogger (Blogspot). Saat itu, artikel blog saya kebanyakan menyerupai diari, catatan dari kejadian sehari-hari yang saya alami. Akhirnya, saya merasa konten tersebut terlalu pribadi, sehingga saya atur aksesnya menjadi pribadi.</p>\n<p>Selain blog pertama itu, saya mempunyai 5 blog lain di Blogger. Satu untuk tulisan yang saya nilai tidak terlalu privat dan bisa dibaca oleh publik, satu untuk blog kelas saya di SMP, dan satu untuk saya belajar menulis dalam Bahasa Inggris. Saya tidak ingat blog yang lain untuk apa, karena banyak yang saya buat lalu saya hapus. Saya merasa puas dan senang saat bisa menuangkan pikiran saya dalam bentuk tulisan. Menulis membantu saya memroses pikiran dan perasaan saya, bahkan sampai saat ini.</p>\n<p>Setelah lulus SMA, saya tadinya ingin kuliah Sastra Inggris di salah satu universitas negeri (saya suka bahasa, Bahasa Inggris mata pelajaran favorit saya!), tetapi karena tidak berhasil masuk, akhirnya saya berkuliah di universitas swasta, mengambil jurusan Sistem Informasi. Di kuliah, saya belajar banyak mengenai TI dan bisnis, saya mempelajari bahasa pemrograman Java, HTML, CSS, Javascript, dan pemrograman Android. Saya juga belajar Bootstrap dan Ruby on Rails secara otodidak lewat Coursera dan Codecademy. Saya bisa memahami pelajaran pemrograman dan mendapat nilai bagus, tetapi saya tidak suka <i>‘coding</i>’. Saya merasa saya tidak cukup sabar untuk menulis kode dan mencari kesalahan dalam kode saya.</p>\n<h3>Bertemu WordPress pertama kali</h3>\n<p>Saat saya kuliah, orangtua saya membangun beberapa website menggunakan WordPress untuk menjual link. Saya membantu mereka mengecek kualitas artikel dan menyusunnya di WordPress, dan mereka membayar saya. Ini pertama kalinya saya bekerja dengan WordPress. Saya ingat, saya menganggap WordPress sebagai platform yang lebih canggih dari Blogger, karena ada lebih banyak cara untuk modifikasi lewat tema dan plugin.</p>\n<p>Saya suka mendapat uang tambahan (siapa yang tidak suka?), sehingga saya membantu mengajar bimbel di dekat rumah. Di semester lain, saya mengajar Inggris di Kumon, di dekat rumah juga. Selain itu, selama 2 semester, saya menjadi mentor di kampus, mengajar 10 orang teman saya yang butuh pelajaran tambahan. Sebagai gantinya, saya mendapat potongan uang kuliah.</p>\n<p>Di rumah, saya juga mencari semua cara yang legal dan aman untuk mencari uang. Saya menerjemahkan teks dari Inggris ke Indonesia menggunakan Gengo dan menulis artikel dalam Bahasa Inggris di Zerys. Saya juga mendaftar di Upwork (marketplace untuk freelancer), apply ke beberapa pekerjaan, tetapi tidak pernah mendapat satupun.</p>\n<p>Di tahun terakhir perkuliahan, saya diwajibkan menjalani magang selama 1 tahun. Saya mendapat kesempatan untuk magang di Asuransi Astra sebagai Staff IT Quality Control mereka. Selama 1 tahun tersebut, saya belajar banyak dan bertemu banyak orang hebat, tetapi saat ditawari posisi tetap menjadi Business Analyst, saya menolak. Saat itu saya ingin mendaftar beasiswa untuk melanjutkan pendidikan S2. Dan saya juga tidak terlalu suka harus bangun jam 6 pagi, sampai di rumah jam 7 malam, dan harus mengulanginya setiap hari.</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image2-1.jpg\"><img /></a>Foto dengan teman-teman kantor, saya yang berbaju putih.\n<p>Tetapi satu hal yang baru saya sadari saat menulis ini, kesempatan remote work yang saya miliki sekarang ini tidak mungkin ada tanpa pengalaman magang tersebut. Perjalanan bus ke kantor setiap hari membuat saya rutin membaca Medium. Membaca cerita-cerita orang di Medium membuat saya ingin menulis dan membagikan cerita saya, sehingga saya melakukannya di Medium.</p>\n<h3>Mulai bekerja remote</h3>\n<p>Setelah magang, saat saya mempersiapkan diri untuk mendaftar beasiswa, saya teringat dengan profil Upwork saya. Saya perbarui info diri dan CV, dan mendaftar ke beberapa lowongan sebagai asisten virtual (virtual assistant). Saya lakukan segala hal mulai dari bayaran yang kecil, seperti mem-format artikel di WordPress, desain pos media sosial, dan memroses pesanan untuk toko online. Saya bekerja dengan klien dari Singapura, Australia, Eropa, dan Amerika. Setelah beberapa review yang bagus dari klien, saya menaikkan tarif per jam saya perlahan-lahan. Saya menjadi mahir menggunakan aplikasi yang sering digunakan di lingkungan kerja remote, seperti Slack, Asana, Trello, dan Google Suites. Saya juga mulai menulis lebih banyak artikel lagi dalam bahasa Inggris, di blog pribadi saya di WordPress.com dan Medium.</p>\n<p>Suatu hari, 3 bulan setelah mulai kerja di Upwork, ada sebuah lowongan yang menarik perhatian saya. Sebuah perusahaan plugin WordPress bernama Caldera Labs/Caldera Forms sedang mencari seseorang yang dapat menjaga konsistensi blog mereka. Mereka ingin menghasilkan satu artikel per minggu. Saya mengirim proposal beserta URL profil Medium saya.</p>\n<p>Tidak lama kemudian, proposal saya dijawab oleh salah satu co-founder mereka, <a href=\"http://christiechirinos.com/\"><NAME></a>. Saya ingat Christie berkata bahwa ia sudah melihat profil Medium saya dan saya mempunyai ‘nada menulis yang bagus’. Lalu, ia mengirimi saya link Calendly (aplikasi untuk mengatur pertemuan secara online, bisa melihat jadwal kosong dari orang yang bersangkutan), dan saya memberitahunya bahwa saya akan dapat bertemu jam 5 pagi keesokan harinya.</p>\n<p>Itu juga merupakan kali pertama saya diwawancara lewat video. Saya senang dan bersemangat, tetapi juga panik. Pada hari H, saya bangun jam 4 pagi, bersiap-siap, dan membuka laptop. Anehnya, hari itu wi-fi saya putus! Saya akhirnya pergi ke McDonalds terdekat untuk mendapatkan koneksi internet. Untungnya, wawancara tersebut berjalan lancar.</p>\n<p>Saya diterima bekerja di Caldera Forms, sambil terus bekerja dengan klien yang lain, karena beban pekerjaan Caldera Forms saat itu hanya 15 jam seminggu, bahkan kurang. Selain Christie, saya juga bertemu dengan <NAME> (co-founder), Ariella, Anchaal, Rosa, Nico, dan Swapnil. Mereka berada di Amerika Serikat, India, dan Perancis.</p>\n<p>Awalnya, saya hanya ditugaskan untuk menyusun artikel di WordPress sesuai dengan style guide yang sudah mereka susun. Setelah beberapa bulan, saya dilibatkan di dalam strategi konten mereka secara keseluruhan, seperti membuat email onboarding dan berkoordinasi dengan penulis tamu. Dari awal, walaupun kami belum pernah bertemu secara langsung, saya merasa disambut oleh tim Caldera Forms. Dalam satu waktu, tim kami hanya berjumlah 5-6 orang, dengan pertemuan bulanan melalui video, dan ‘ngobrol’ harian melalui Slack. Pengalaman dengan Caldera Forms tidak seperti dengan klien saya yang lain.</p>\n<p>Christie dan Josh juga sangat aktif di komunitas WordPress, mereka mengenalkan saya ke orang-orang yang tepat. Untuk berkomunikasi dengan orang-orang tersebut, saya harus membuat akun di Slack Make WordPress. Saya jadi kenal dengan komunitas di balik WordPress, bagaimana orang secara sukarela menyumbangkan waktu, energi, dan kemampuan mereka untuk kemajuan komunitas, kode, pemasaran, hingga penerjemahan. Melihat itu semua sangat menginspirasi saya. Selama di Caldera Forms, saya juga dikirim untuk menghadiri WordCamp pertama saya, WordCamp Jakarta 2018!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image3-1.jpg\"><img /></a>Merchandise dari WordCamp Jakarta, Wapuu Ondel-ondel!\n<p>Setelah menghadiri WordCamp tersebut, tentunya saya ingin mempunyai website WordPress sendiri dengan domain nama saya sendiri. Teman-teman dapat melihat blog saya <a href=\"http://ascenciafike.com\">disini</a>. Mempunyai blog dengan domain nama saya sendiri terasa seperti langkah selanjutnya dalam perjalanan karir saya.</p>\n<h3>Proses transisi ke pekerjaan penuh waktu</h3>\n<p>Suatu hari, Caldera Forms diakuisisi oleh <a href=\"http://saturdaydrive.com\">Saturday Drive</a>, perusahaan di balik plugin form builder lainnya, <a href=\"http://ninjaforms.com\">Ninja Forms</a>. Josh, Nico, Rosa, dan saya ‘berpindah’ juga. Josh memperkenalkan saya ke <a href=\"http://jameslaws.com\">James Laws</a>, CEO dari Saturday Drive. Saat itu, kami masih menggunakan kontrak lama saya di Upwork, dengan batas waktu kerja 15 jam seminggu. Di Saturday Drive, semuanya berbeda, tim mereka jauh lebih besar dibandingkan Caldera (ada lebih dari 20 orang) sehingga saya sangat bersemangat! Mereka mempunyai tim produk, tim suport, dan tim komunikasi. Tetapi, selain akuisisi tersebut, mereka juga sedang melewati transisi yang lain, yaitu berubah menjadi perusahaan remote.</p>\n<p>Setelah satu bulan bekerja bersama Saturday Drive dengan kontrak lama saya, James tiba-tiba menawari saya posisi penuh waktu untuk mengelola program afiliasi mereka. Saya sangat senang dan bersyukur mendapatkan penawaran tersebut, tetapi juga mengalami dilema. Mengambil tawaran tersebut dan bekerja penuh waktu dengan Saturday Drive berarti melepas semua klien saya dan harus mengambil spesialisasi <i>affiliate marketing</i> (pemasaran afiliasi). Saya juga harus bekerja selama 8 jam sehari. Malam itu, saya tidak bisa tidur, dan saya berdiskusi dengan kedua orangtua saya yang sama bersemangatnya.</p>\n<p>Keesokan harinya, saya menjawab pesan dari James dan menerima tawarannya.</p>\n<p>Sudah lebih dari 4 bulan sejak saya mulai bekerja dengan Saturday Drive (waktu penulisan: bulan Januari 2020). Bekerja penuh waktu dengan satu perusahaan memang sangat berbeda dengan freelancing (bekerja lepas), tetapi saya menikmati hampir setiap momennya.</p>\n<p>Di Saturday Drive, kami menggunakan Basecamp, bukan Slack, dimana kami dapat mengatur pertanyaan rutin untuk anggota yang lain setiap minggunya. Misalnya, setiap Rabu kami akan mendapat pertanyaan: “Bagaimana penampilanmu hari ini?”. Ada juga pertanyaan-pertanyaan seperti: “Apa yang kamu tunggu-tunggu minggu ini?”, “Apa yang berjalan lancar dari kerjamu hari ini?”, dan “Buku apa yang baru kamu baca dan menurutmu bagus akhir-akhir ini?”. Bahkan kami mempunyai klub membaca untuk buku fiksi dan non-fiksi!</p>\n<p>Kami juga menggunakan metode kerja dari Basecamp, yang disebut <a href=\"https://basecamp.com/shapeup\">Shape Up</a>. Kami bekerja dalam siklus, yaitu 6 minggu mengerjakan proyek, lalu 2 minggu mengerjakan hal-hal yang kami ingin kerjakan (disebut <i>cooldown</i>). Sebelum siklus selanjutnya mulai, kami akan mengumpulkan <i>pitch</i> mengenai proyek yang ingin kita lakukan.</p>\n<p>Bagaimana dengan panggilan/konferensi video? Kami mengadakan pertemuan dengan semua anggota tim setiap bulannya, dan <i>ngobrol </i>dengan 4-5 orang setiap 2 minggu. Kalau diperlukan sekali, kami juga mengadakan panggilan video untuk pekerjaan. Saya bekerja dalam zona waktu Indonesia, kecuali untuk mengikuti panggilan-panggilan ini.</p>\n<p>Sejauh ini, saya menikmati bekerja dengan Saturday Drive dan mengenal orang-orang di dalamnya. Walaupun sulit untuk terhubung dengan budaya Amerika (hampir 90% stafnya berada di Amerika), tetapi saya terhubung dan sangat mendukung nilai-nilai yang Saturday Drive pegang. Dan yang terpenting, saya bangga dengan kerja Saturday Drive sebagai perusahaan!</p>\n<a href=\"https://s20094.pcdn.co/wp-content/uploads/2020/01/image1-1.png\"><img /></a>Ngobrol virtual dengan tim Saturday Drive.\n<h3>Memberi kembali ke Komunitas WordPress</h3>\n<p>Apakah teman-teman bisa melihat pola di dalam cerita saya?</p>\n<p>Orang-orang di dalam komunitas WordPress biasanya suka berbagi, sangat percaya kepada orang lain (dan potensi orang lain), dan suka menolong, karena WordPress sendiri bersifat open-source (terbuka). WordPress bisa berjalan karena dibantu oleh para relawan, orang-orag dari seluruh dunia yang secara sukarela menulis kode, membantu pemasaran, penerjemahan, suport, dan masih banyak lagi. Meetup dan WordCamp, baik lokal dan regional, diadakan oleh organizer dan relawan.</p>\n<p>Karena selama ini saya telah merasakan kebaikan dari orang-orang WordPress, saya ingin memberi kembali/membantu komunitas WordPress. Beberapa bulan lalu, saya mencoba berkontribusi ke tim Marketing WordPress global dengan mengikuti beberapa kali pertemuan mingguannya di Slack. Tetapi lama kelamaan saya tidak datang lagi, karena terlalu sibuk dengan pekerjaan (dan pertemuannya diadakan pukul 10 malam).</p>\n<p>Sekitar bulan November 2019, <NAME> dari WordPress Indonesia menghubungi saya lewat DM Instagram. Ia mengundang saya untuk ikut PerempuanWP, sebuah komunitas untuk perempuan Indonesia yang bekerja di dunia WordPress (mirip dengan WomeninWP). Hari itu, saya mulai mengikuti <a href=\"https://twitter.com/PerempuanWP\">@PerempuanWP</a> di Twitter dan bergabung dengan Slack WordPress Indonesia. Tidak lama setelahnya, saya berkontribusi di tim poliglot Indonesia juga, menerjemahkan Kode Etik Komunitas WordPress Indonesia (<i>Code of Conduct</i>) dan merevisi Panduan Penerjemahan (<i>Translation Style Guide</i>).</p>\n<p>Saat ini, saya sedang mempersiapkan <a href=\"https://wp-id.org/kulgram-4-onboarding-e-mail/\">kulgram di grup Telegram PerempuanWP</a> dan menjadi <a href=\"https://wp-id.org/wpjkt-meetup-21-onboarding-email-and-woocommerce-theme-for-your-business\">pembicara di Meetup WordPress Jakarta</a>, keduanya tentang <i>email marketing.</i></p>\n<p>Dengan membagikan pengalaman dan cerita saya, salah satunya melakui artikel ini, saya ingin mewakili perempuan Indonesia dan Asia. Saya berharap saya dapat menginspirasi banyak perempuan di Indonesia dan Asia untuk bekerja secara remote.</p>\n<h3>Apa yang harus Anda lakukan jika ingin bekerja secara <i>remote</i></h3>\n<p>Jika teman-teman adalah seorang yang introver (seperti saya!), bekerja remote mungkin terdengar seperti mimpi yang jadi kenyataan. Tanpa harus meninggalkan rumah (bahkan kadang masih memakai baju tidur), Anda dapat bekerja dan menghasilkan uang. Tetapi tidak semua aspek bekerja remote itu menyenangkan.</p>\n<p>Berdasarkan pengalaman saya, berikut hal-hal yang harus Anda persiapkan jika ingin bekerja secara remote:</p>\n<ol>\n<li>Anda harus siap bekerja di depan komputer. Satu hari penuh.<br />\nPaling tidak Anda harus bisa melakukan pencarian lewat Google, karena akan sangat dibutuhkan untuk bekerja, terutama jika Anda ingin memulai sebagai asisten virtual. Jaga mata Anda. Berdiri dan jalan setiap 30 menit.</li>\n<li>Anda harus siap bosan, dan tidak bertemu orang lain (selain keluarga) selama satu hari.<br />\nKadang Anda harus fokus sekali dengan pekerjaan hingga tidak bisa keluar rumah. Tetapi kadang, satu-satunya cara untuk fokus adalah keluar rumah dan kerja di kafe. Sesuaikan dengan kebutuhan, lama-kelamaan Anda akan menemukan kombinasi yang pas.</li>\n<li>Pelajari bahasa Inggris. Atau bahasa internasional lainnya.<br />\nJika Anda ingin bekerja secara internasional. Poin ini adalah keharusan. Anda tidak akan bisa bekerja dengan orang dari negara lain jika Anda tidak dapat berkomunikasi dalam bahasa mereka.</li>\n<li>Lakukan yang terbaik di pekerjaan Anda saat ini.<br />\nSalah satu buku terbaik yang saya baca di tahun 2019 adalah So Good They Can’t Ignore You oleh Cal Newport. “Jangan ikuti passion Anda; melainkan biarkan passion Anda mengikuti Anda dalam perjalanan, yang <NAME> sebagai, “bagus sekali hingga mereka tidak dapat mengabaikan Anda.”” Jadi, jangan ikuti passion Anda, tetapi jalani pekerjaan yang Anda punya sekarang sebaik mungkin, coba untuk menguasai kemampuan yang dibutuhkan, dan adopsi cara pikir ‘pengrajin’. Jangan menunggu pekerjaan yang ‘sempurna’, percaya bahwa setiap pekerjaan mempunyai pelajaran bagi diri kita, kumpulkan kemampuan sebanyak mungkin, dan pikirkan apa yang dapat Anda lakukan bagi dunia dengan kemampuan-kemampuan tersebut.<br />\nSingkatnya, jangan terlalu terobsesi dengan ingin bekerja secara remote. Kerjakan pekerjaan Anda sebaik mungkin, kesempatan akan datang pada waktunya.</li>\n<li>Jangan mudah puas.<br />\nApapun tingkat kemampuan Anda saat ini, belajar sebanyak-banyaknya. Darimana saja, tentang apa saja. Tetap terbuka. Baca buku, dengarkan podcast, dan pelajari kemampuan baru.</li>\n<li>Ikut komunitas.<br />\nJika Anda bekerja di dunia WordPress, ikut komunitas WordPress! Selain bisa menolong orang lain, kita juga bisa belajar dari banyak orang hebat dan menambah koneksi.</li>\n</ol>\n<p>Saya berharap pengalaman saya dan tips-tips di atas dapat menginspirasi dan menolong teman-teman yang ingin berkarir secara remote.</p>\n<div class=\"rtsocial-container rtsocial-container-align-right rtsocial-horizontal\"><div class=\"rtsocial-twitter-horizontal\"><div class=\"rtsocial-twitter-horizontal-button\"><a title=\"Tweet: How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\" class=\"rtsocial-twitter-button\" href=\"https://twitter.com/share?text=How%20WordPress%20Enabled%20Me%20To%20Work%20Remotely%20%2D%20Bagaimana%20WordPress%20Memungkinkan%20Saya%20Bekerja%20Secara%20Remote&via=heropress&url=https%3A%2F%2Fheropress.com%2Fessays%2Fstarting-early-in-tech%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-fb-horizontal fb-light\"><div class=\"rtsocial-fb-horizontal-button\"><a title=\"Like: How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\" class=\"rtsocial-fb-button rtsocial-fb-like-light\" href=\"https://www.facebook.com/sharer.php?u=https%3A%2F%2Fheropress.com%2Fessays%2Fstarting-early-in-tech%2F\" rel=\"nofollow\" target=\"_blank\"></a></div></div><div class=\"rtsocial-linkedin-horizontal\"><div class=\"rtsocial-linkedin-horizontal-button\"><a class=\"rtsocial-linkedin-button\" href=\"https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fheropress.com%2Fessays%2Fstarting-early-in-tech%2F&title=How+WordPress+Enabled+Me+To+Work+Remotely+%26%238211%3B+Bagaimana+WordPress+Memungkinkan+Saya+Bekerja+Secara+Remote\" rel=\"nofollow\" target=\"_blank\" title=\"Share: How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\"></a></div></div><div class=\"rtsocial-pinterest-horizontal\"><div class=\"rtsocial-pinterest-horizontal-button\"><a class=\"rtsocial-pinterest-button\" href=\"https://pinterest.com/pin/create/button/?url=https://heropress.com/essays/starting-early-in-tech/&media=https://heropress.com/wp-content/uploads/2020/01/011320-min-150x150.jpg&description=How WordPress Enabled Me To Work Remotely - Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\" rel=\"nofollow\" target=\"_blank\" title=\"Pin: How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\"></a></div></div><a rel=\"nofollow\" class=\"perma-link\" href=\"https://heropress.com/essays/starting-early-in-tech/\" title=\"How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote\"></a></div><p>The post <a rel=\"nofollow\" href=\"https://heropress.com/essays/starting-early-in-tech/\">How WordPress Enabled Me To Work Remotely – Bagaimana WordPress Memungkinkan Saya Bekerja Secara Remote</a> appeared first on <a rel=\"nofollow\" href=\"https://heropress.com\">HeroPress</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 15 Jan 2020 01:00: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:11:\"<NAME>\";s: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:104:\"WPTavern: Dollie Platform Launches, Provides Tools to Build and Deploy Pre-Configured WordPress Installs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96477\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:114:\"https://wptavern.com/dollie-platform-launches-provides-tools-to-build-and-deploy-pre-configured-wordpress-installs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4720:\"<p>Stratus5, a company that specializes in cloud container management and business service automation, launched <a href=\"https://getdollie.com/\">Dollie</a> today. Dollie is a cloud-based eCommerce solution for WordPress developers looking to provide white-label hosting services to their customers. The platform allows developers and agencies to sell custom, pre-configured WordPress solutions to their clients.</p>\n\n\n\n<p>Dollie is built on top of the Stratus5 Cloudware system. It includes tools like Blueprints, which allows developers to save and clone custom WordPress configurations. These configurations are saved to the cloud. Developers can then launch new instances and monetize them at the click of a button.</p>\n\n\n\n<p>It also has management tools such as billing automation, customer resource management, analytics, backups, permissions, and more. The platform serves sites via isolated Docker containers. It runs on a modern stack that includes NGINX, PHP 7.3, Redis, and PerconaDB.</p>\n\n\n\n<p>“In the simplest terms, we let developers launch their own cloud hosting service similar to Wix or Squarespace but using WordPress,” said <NAME>, VP of Dollie and Stratus5 Cloudware.</p>\n\n\n\n<p>Developers can try Dollie for free and only start paying once they are ready to accept customers. Pricing begins at $100 per month for the first 10 customers.</p>\n\n\n\n<p>Customer billing can be done via Dollie’s payment gateway or the developer’s gateway of choice. The system is backed by the WooCommerce plugin, so any payment gateway that supports WooCommerce Subscriptions is available. There are no limits on the business model that developers employ. They can set up custom pricing.</p>\n\n\n\n<p>Take a quick tour of how Dollie works:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<h2>Filling a Missing Gap in the Market</h2>\n\n\n\n<p>“We built Dollie because there’s a competitive gap in the market between the hosting companies and the developers who actually build websites, themes, and plugins,” <NAME>. “I’ve seen agencies and many of my developer friends constantly stuck in the rat race of trying to find that next customer, get that next download, and struggle to build sustainable businesses. This is the struggle I faced with CyberChimps selling one-off WordPress products. Meanwhile, the hosting companies have turned into multi-million and even billion-dollar corporations on the backs of these same developers.”</p>\n\n\n\n<p>Lapinski feels like Dollie will level the playing field for developers. He wishes these tools had existed when he bootstrapped his WordPress startup. The goal is to allow developers to compete on their own terms. </p>\n\n\n\n<p>“By empowering developers to build sustainable products and services and generate reoccurring-subscription revenue, much like the hosting companies have accomplished, we can grow WordPress by helping developers and agencies grow their businesses,” he said. “The key is helping them acquire subscription customers so they can forecast, budget, and bootstrap their businesses in a way I never could when I ran my own theme shop.”</p>\n\n\n\n<p>The platform is built on top of WordPress and WooCommerce. The custom-built technology on top of this allows developers to set up white-label cloud services with minimal up-front knowledge. The biggest requirement is that developers need to be comfortable with WordPress and WooCommerce.</p>\n\n\n\n<p>“Bringing these enterprise-level tools to WordPress developers and giving them the freedom to choose their own business models has simply never been done before,” said Lapinski. “Dollie automates many of the processes developers have had to work around for decades, and makes saving, cloning, deploying, and monetizing WordPress products and services as easy as a few clicks.”</p>\n\n\n\n<p>Dollie takes no part in what developers or agencies charge their clients outside of providing the tools. That relationship exists directly between the developer and the client. Dollie gets paid when developers convert subscribing customers to cover the cloud hosting costs.</p>\n\n\n\n<p>They also allow larger agencies to select third-party cloud providers. They can then license and partner with Dollie to manage their cloud infrastructure. The goal is to allow developers to scale as large as needed and customize to suit their needs.</p>\n\n\n\n<p>“We are optimistic these tools and the freedom we are enabling for our partners will be the point of difference in how developers view their own value in what they can deliver to their clients and customers,” said Lapinski.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 14 Jan 2020 21:13: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:\"<NAME>\";s: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:65:\"WPTavern: Can the Block Directory and Business Interests Coexist?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96444\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:75:\"https://wptavern.com/can-the-block-directory-and-business-interests-coexist\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5388:\"<p>WordPress.org is not an official marketplace for plugins and themes. Except for some plugins that are strictly SaaS products, all extensions to the platform are publicly available for the low cost of $0.</p>\n\n\n\n<p>Despite not directly selling through WordPress.org, the plugin directory is a huge source of income for many individual developers and companies via product and service upsells. Plugins are big business. Besides a bounty of third-party marketplaces and individual shops, commercial interests often flow directly in and out of the official WordPress site. For many developers, it essentially serves as a marketplace.</p>\n\n\n\n<p>In December, we dove into an <a href=\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced\">early proposal of the WordPress block directory</a>. The new directory should land within the WordPress software itself in version 5.5 and will house a new type of plugin. The idea behind the <a href=\"https://wordpress.org/plugins/browse/block/\">block directory</a> is that it will allow plugin developers to create and share one-off blocks that users can install on their websites.</p>\n\n\n\n<p>This is the future of WordPress.</p>\n\n\n\n<p>Love it or hate it, there will come a time when end-users are primarily looking to install individual blocks to solve their problems. This is not to say that other types of plugins won’t exist or have their place. They will continue to be a major part of the platform. However, blocks will be a big deal once users can install them at the click of a button via the WordPress admin.</p>\n\n\n\n<p>The question is whether blocks can also be big business.</p>\n\n\n\n<p>Tavern reader <NAME> <a href=\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced#comment-316657\">believes the guidelines</a> for the block directory could be an issue. “There’s a lot to like here,” he said. “Though I’m still troubled by the directory submission rules that are fairly stringently not allowing for any sort of promotional link or defined up-sell of any kind so as not to ‘disrupt the flow.\'”</p>\n\n\n\n<p>Currently, the <a href=\"https://github.com/WordPress/wporg-plugin-guidelines/blob/block-guidelines/blocks.md\">block directory guidelines</a> make it clear that advertising of any kind is disallowed:</p>\n\n\n\n<blockquote class=\"wp-block-quote\"><p>Block Plugins are blocks. They must not include advertisements, prompts, or promotional messages.</p></blockquote>\n\n\n\n<p>On the one hand, it makes sense, particularly for something that is not yet built and will eventually serve as a version 1.0. If every block a user installs begins advertising, it could be a recipe for disaster without some type of standard.</p>\n\n\n\n<p>On the other hand, would the idea of not having an upselling route turn WordPress businesses away? While many developers would be willing to submit blocks, is this sustainable? Many of the most popular plugins are backed by businesses. The more popular any particular piece of software becomes, the more likely it is that the software will need funding to cover maintenance, feature updates, and support.</p>\n\n\n\n<p>“More often than not these days, people don’t have as much free time to invest in coding just for the fun of it,” said Gowdy. “I speak mainly of myself, but I have the notion that while WordPress is still grounded pretty firmly in Open Source (not a bad thing), it’s been the open markets that have allowed it to grow as much as it has. I don’t think it’s wrong to allow people the opportunity (within reason) to make something back off their hard work should they choose. Donations are non-viable in my experience as the vast majority of humanity are way cheaper than they would like to admit.”</p>\n\n\n\n<p>Currently, the upcoming directory has a limited number of blocks available. The WordPress Meta and Plugin teams should expect more. However, it is unclear whether the guideline will slow its growth.</p>\n\n\n\n<p>“Without any sort of up-sell channel (rule-defined or element defined in blocks), we aren’t going to see the plethora that we are hoping for, nor in some cases the quality that could be brought in by people working professionally on a block plugin,” said Gowdy. “The time to define these up-sell and link options is right now.”</p>\n\n\n\n<p>Gowdy is not alone in his concerns. Several others expressed similar opinions in the comments on the <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines\">block directory announcement post</a>.</p>\n\n\n\n<p>“Where WordPress started and where it is now are two separate points in time,” said Gowdy. “I hope the Open Source community and the marketplaces can find a way to co-exist here in order to really rev up the platform for the future.”</p>\n\n\n\n<p class=\"has-text-color has-background has-white-color has-blue-700-background-color is-style-highlight text-white bg-blue-700\">This post is part of a new <a href=\"https://wptavern.com/category/from-the-comments\">From the Comments</a> series where we highlight interesting points of discussion from comments on WP Tavern articles. The hope is to give these comments, which can sometimes get lost, the attention they deserve.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 13 Jan 2020 20:46:34 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:77:\"WPTavern: Upcoming Tailwind CSS 1.2.0 Includes Grid Support and New Utilities\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96387\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/upcoming-tailwind-css-1-2-0-includes-grid-support-and-new-utilities\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:3499:\"<p><NAME>, creator of the Tailwind CSS, <a href=\"https://github.com/tailwindcss/tailwindcss/releases/tag/v1.2.0-canary.4\">published the early release notes</a> for the upcoming version 1.2.0 update to the framework. The new version will include the much-anticipated <a href=\"https://github.com/tailwindcss/tailwindcss/pull/1274\">support for CSS grids</a> and several other useful features for app and website designers. There are no planned breaking changes with the update.</p>\n\n\n\n<p>Tailwind CSS is a utility-first CSS framework that is quickly gaining support from designers and developers. Some WordPress themes are starting to pop up in the public sphere that use it, but is more often used as part of the in-house toolset at agencies, in which standards are necessary to keep teams on the same page.</p>\n\n\n\n<p>For developers already using the framework, they can look for an update within days. “Right now I don’t have any changes to these features planned, so as long as nobody finds any huge issues I’ll tag the real v1.2.0 next week once I get some documentation together,” said Wathan on <a href=\"https://twitter.com/adamwathan/status/1214982042083090433\">Twitter</a>.</p>\n\n\n\n<p>Now is a good time for new developers to start tinkering with the CSS framework. With the addition of new CSS grid classes, there is little that is not possible for the majority of use cases.</p>\n\n\n\n<p>I have been building with Tailwind, or a subset of its classes, for about a year now. Aside from highly-custom scenarios, I have been able to build most projects while writing little CSS code. For someone who comes primarily from a developer background, it has been a godsend for quickly putting together complex layouts. CSS grid support was the big item I had been waiting for. I had already built a custom grid system based on Tailwind’s naming scheme. My implementation is nearly the same as what is shipping in Tailwind CSS 1.2.0.</p>\n\n\n\n<p>Other new features include classes for CSS features such as:</p>\n\n\n\n<ul><li><code>transition</code></li><li><code>transform</code></li><li><code>stroke-width</code></li><li><code>box-sizing</code></li><li><code>clear</code></li></ul>\n\n\n\n<p>Version 1.2.0 adds extra utility classes for rounded corners and shadow sizes. It also extends its support for setting an element’s maximum width. New utility classes were added for removing a max-width and setting it based on predefined breakpoints.</p>\n\n\n\n<p>The <a href=\"https://rsms.me/inter/\">Inter font</a> now sits at the top of the font stack and will be used if installed on the user’s system or if the developer loads it on the site. Inter is a popular font created specifically for computer screens. It comes in both fixed and variable options. The Twenty Twenty theme <a href=\"https://wptavern.com/wordpress-5-3-kirk-released-brings-new-default-theme-editor-improvements-and-ui-tweaks\">released with WordPress 5.3</a> uses the variable version of Inter for several elements within its design.</p>\n\n\n\n<p>For developers who are extending Tailwind CSS, they now have a <a href=\"https://github.com/tailwindcss/tailwindcss/pull/1268\">new plugin API</a> for building custom plugins. Plugins can also <a href=\"https://github.com/tailwindcss/tailwindcss/pull/1162\">extend the user’s configuration file</a>.</p>\n\n\n\n<p>Overall, it looks like it will be a solid update. I am excited about digging into it and using some of the new utility classes.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 10 Jan 2020 21:11: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:14:\"<NAME>\";s: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: Gutenberg 7.2 Adds Long-Awaited Multi-Button Block and Gallery Image Size Option\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=96362\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:101:\"https://wptavern.com/gutenberg-7-2-adds-long-awaited-multi-button-block-and-gallery-image-size-option\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4723:\"<p>The Gutenberg team <a href=\"https://make.wordpress.org/core/2020/01/09/whats-new-in-gutenberg-8-january/\">released version 7.2</a> of the plugin yesterday after a four-week release hiatus for the holidays. This update includes at least 180 pull requests to the project’s repository by 56 contributors. The largest user-facing features include a new “buttons” block that allows users to add multiple buttons in a row and the ability to define the size of images in a gallery block. These were two highly-requested features.</p>\n\n\n\n<p>The update supports changing the font size in the relatively new navigation block. Users can also add a link for the image in the media & text block. A few dozen other minor enhancements across multiple components made their way into the update. Most enhancements continue to clean up the interface and improve usability.</p>\n\n\n\n<p>Many bug fixes are included in version 7.2. Accessibility improvements include using radio inputs for text alignment, adding an appropriate <code>group</code> role to the block wrapper, adding a label to the social icons block, and more. Several fixes should improve how pasting content in the editor works, which generally works well already.</p>\n\n\n\n<p>The team continued building upon experimental features, which must be activated via the Gutenberg > Experiments screen in the admin. Outside of a handful of bug fixes and enhancements, the most interesting change is the introduction of a new experimental admin screen. Gutenberg 7.2 now includes an early beta of a full-site editing page.</p>\n\n\n\n<h2>Adding Buttons in a Row</h2>\n\n\n\n<img />Adding multiple buttons within the Buttons block.\n\n\n\n<p><em>If I had a nickel for every time a user asked how to put two buttons next to each other…</em>You know how the story goes.</p>\n\n\n\n<p>One of the most-common website layouts today is a large “hero” section, a heading, some text, and a button, perhaps two. An end-user could easily build this with a combination of the cover, heading, paragraph, and button blocks if only a single button was needed. However, that second button was troubling without some custom code work.</p>\n\n\n\n<p>The introduction of the buttons block changes everything. It is a block that allows end-users to add any number of individual button blocks in a row. At the moment, the block essentially serves as a wrapper. The block’s only option is the ability to set the alignment of the inner button blocks.</p>\n\n\n\n<h2>Image Size Selector for Galleries</h2>\n\n\n\n<img />Selecting a custom image size for the Gallery block.\n\n\n\n<p>The lack of an option to set the size of gallery images has been one of Gutenberg’s largest failures since its inception. After years of this basic option for the gallery shortcode with the classic editor, the gallery block has always felt incomplete.</p>\n\n\n\n<p>For some users, the lack of basic features that have long existed in the classic editor <a href=\"https://wptavern.com/gutenberg-one-year-later#comment-314188\">is frustrating</a>. That frustration is understandable, given the fast-paced movement on newer and shinier features. It is refreshing to see work being done toward addressing long-missing features such as this.</p>\n\n\n\n<p>The gallery block now has a new “Images Sizes” dropdown select for choosing the size of the images shown. This option will solve at least a couple of major issues. By selecting a custom size, the images will utilize less bandwidth for site visitors. Previously, full-sized images were displayed. It also allows users to select a consistent size so that galleries with multiple image aspect ratios are better aligned in a grid. Basically, it can make for prettier galleries.</p>\n\n\n\n<h2>Site Editor Screen Beta</h2>\n\n\n\n<img />Testing the beta Site Editor screen.\n\n\n\n<p>Gutenberg 7.2 introduces a “Site Editor” screen, which can be enabled by ticking the “Enable Full Site Editing” checkbox on the Gutenberg > Experiments admin page. The new screen is an early, bare-bones beta exploration into what will eventually be fully-fledged site editor.</p>\n\n\n\n<p>At this point, the screen does not do much. End-users can insert blocks and little else. Content on this screen is not stored for later. There is not even a save button yet. Mostly, it serves as another step toward site editing, which could possibly land in core WordPress late in 2020. However, that is an optimistic schedule, and it is far too early to make a solid guess. There are a lot of open questions that need answers and technical hurdles to jump. A 2021 release might be more realistic, depending on the pace of development.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 09 Jan 2020 20:47: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:14:\"<NAME>\";s: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:77:\"WPTavern: BobWP.com Shifts Focus to WooCommerce, Rebrands as ‘Do the Woo’\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96305\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/bobwp-com-shifts-focus-to-woocommerce-rebrands-as-do-the-woo\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4426:\"<img />\n\n\n\n<p>BobWP.com <a href=\"https://bobwp.com/bobwp-is-now-do-the-woo-woocommerce-news-and-community/\">announced yesterday</a> that the site and its podcast would be rebranded to “Do the Woo at BobWP .” After a decade of more generalized WordPress topics and news, it will now focus specifically on the WooCommerce plugin and its community. The podcast will also be aired weekly, notching up their previous twice-monthly episodes.</p>\n\n\n\n<p>For <NAME>, founder and co-host, this was move was a natural result of where the community he had built was heading. “Over the last 3 years, we have consistently created content around WooCommerce on our site,” he said. “I saw that this was what our readers wanted, so built that up and in March of last year, made the decision to focus entirely on WooCommerce.”</p>\n\n\n\n<p>Dunn said he has been a fan of WooCommerce since its launch. “It has always been a favorite of mine, and I have used it to sell a lot of stuff. But oddly enough, never physical products.”</p>\n\n\n\n<p>Starting in 2020, the podcast will run weekly. To keep up the brisk pace, the show is bringing on two new co-hosts. Joining the team is <NAME>, community lead for WooCommerce, and <NAME>, developer advocate a Liquid Web. <NAME>, CEO of WebDevStudios, has been a co-host since 2018.</p>\n\n\n\n<p>New episodes of the podcast will air every Thursday. The show is pre-recorded on Tuesday of the same week, so the content should remain timely.</p>\n\n\n\n<p>Do the Woo will specifically cater to its WooCommerce audience, but it may delve into the larger eCommerce world from time to time. However, Dunn recommends listening in on the <a href=\"https://wpecommerceshow.com/\">WP eCommerce Show</a> for topics that explore the larger WordPress and eCommerce landscape.</p>\n\n\n\n<p>Dunn does not feel like there will be a shortage of topics to explore every week with WooCommerce-specific content. “At first, yes, it is a bit of a challenge finding topics around it,” he said. “But, expanding it to bring in more of what people are doing in the space, no matter how big or small, opens it up more.” He is optimistic about the show’s future. “I’ll dig as deep as I need to go. And, with its growth, it may come to the time where there will always be more [content] than I need.”</p>\n\n\n\n<p>The podcast’s format remains simple. “We basically bring a guest in, learn more about what they are doing and their involvement in the Woo ecosystem,” said Dunn. “We wrap it up, typically covering two or three news items. The conversation isn’t planned at all. We just take it where it leads us.”</p>\n\n\n\n<p>Dunn originally began the Doo the Woo podcast in 2016 but broadened the scope that same year to WordPress and eCommerce. “I missed it, and at the end of 2017, brought it back as more of an interview-style show, with me and a guest,” he said. “For the next few months, I did very few shows and felt I need to change it up to be more conversational.” He brought on Williams as a co-host at that point. “We did a few shows where Brad and I would just chat Woo stuff, and both came to the conclusion it would be fun to bring on a guest, but still keeping it conversational.”</p>\n\n\n\n<p>The podcast episodes were sporadic until the middle of 2019, which was the start of the bi-weekly schedule. Today, with three extra co-hosts, the team can rotate who is hosting a particular episode.</p>\n\n\n\n<p>Dunn said he still catches a few other podcasts but not as many as in the past. “Always been a fan of and still listen to <a href=\"https://mattreport.com/\">Matt Report</a> and <a href=\"https://getoptionspodcast.com/\">Get Options</a>,” he said. “I am sure I have listened to just about every WP-centric podcast a few times over the years. Without naming each one, there are several good choices depending on what you are looking for. Podcast listening is a very personal choice and I just recommend people dabble in what is out there and find those that click with you.”</p>\n\n\n\n<p>Listen to <a href=\"https://bobwp.com/whats-coming-to-the-do-the-woo-podcast-in-2020/\">episode 33</a> where the team discusses the show’s plans for 2020 and beyond:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 08 Jan 2020 21:07:20 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:76:\"WPTavern: Landing Kit for WordPress Maps Any Post or Page to a Custom Domain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96301\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/landing-kit-for-wordpress-maps-any-post-or-page-to-a-custom-domain\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:7094:\"<img />\n\n\n\n<p><NAME> and <NAME> launched a new WordPress product named <a href=\"https://wplandingkit.com/\">Landing Kit</a> today. The plugin allows end-users to map a domain name to any post, page, or custom post type entry. It includes other features such as SSL support and URL redirecting. More features like custom templates and Gutenberg blocks are on the way.</p>\n\n\n\n<p>Kurth is the director and WordPress product developer at <a href=\"https://hookturn.io/\">Hookturn.io</a>, a premium WordPress plugin company, and runs <a href=\"https://www.awesomeacf.com/\">Awesome ACF</a>, a community hub around the Advanced Custom Fields plugin. Schuller has several ongoing projects. He runs <a href=\"https://rivyt.com/\">RIVYT</a>, a website for video creators to share their work. In October, he <a href=\"https://wptavern.com/jason-schuller-launches-dsko-a-discovery-network-for-creators-and-brands\">launched DSKO</a>, which is a discovery network built on WordPress for creators and brands.</p>\n\n\n\n<p><a href=\"https://leeflets.com\">Leeflets</a>, a project Schuller created for building single-page websites, served as the catalyst for the Landing Kit project. The plugin brings similar functionality to any WordPress install.</p>\n\n\n\n<p>Often, WordPress is overkill for single-page sites. The platform is ideal for larger sites and applications. For people who need to manage multiple single-page sites, Landing Kit could be a blessing. By setting up a single WordPress install with the plugin active, users can map any domain to any post or page. It also works with custom post types. This keeps site management limited to a single admin interface and point of maintenance.</p>\n\n\n\n<p>The plugin should not be confused with domain-mapping plugins built for multisite. While it will work on multisite, the intent is not to map domains to subsites in a network. Instead, it is meant to specifically map domains to single posts or pages on single-site installations.</p>\n\n\n\n<p>The plugin has two pricing tiers. The lower tier costs $59 per year for support and updates on up to three installations. It will also include access to a single page template in the near future. The larger pricing tier at $159 per year offers support and updates for unlimited installations and will provide access to all templates as they become available.</p>\n\n\n\n<p>Landing Kit is Schuller’s first foray in the WordPress product market space since selling his former WordPress theme business, Press75, in 2014. His return is already making a splash and seems to be a welcome addition to the ecosystem given the feedback on his <a href=\"https://twitter.com/jasonpatricksc/status/1214574389036900353\">Twitter announcement</a>.</p>\n\n\n\n<p>“It was never a goal of mine to jump back in, but sometimes these things just happen naturally,” said Schuller. “I’ve consistently used WordPress as a platform to iterate on ideas, and with each new build I end up creating unique functionality to solve specific problems. Landing Kit is the result of one of those problems I had the solve while creating Leeflets.”</p>\n\n\n\n<p>Kurth was brought in to work on the project because of his experience building WordPress plugins. He described the first version as not having many technical challenges because they had a working prototype to build from. “The most difficult part was thinking across multiple contexts and maintaining a clear picture of what would be happening across multiple domains at any time,” he said. “I expect more difficult challenges as we start to move deeper into feature territory as we’ll have bigger decisions to make and new technical hurdles to face, particularly when we start exploring remote block/template libraries.”</p>\n\n\n\n<h2>Plugin Features</h2>\n\n\n\n<img />Potential book template for Landing Kit.\n\n\n\n<p>Version 1.0 of the plugin keeps things simple, which is a signature of Schuller’s past work. The plugin has a domain management screen. It provides a convenient location to edit and configure all mapped domains for the installation. Domain mapping is also available through the post-editing screen.</p>\n\n\n\n<p>The SSL options allow users to serve individual domains over HTTPS or to do so on a global basis. The plugin also makes it easy to decide whether a post or page should be available via the main website or if requests to the single view should be 301 redirected to the mapped domain.</p>\n\n\n\n<p>There are some technical requirements to make use of the plugin. Users must be on a host with the ability to add alias or add-on domains, have a dedicated IP address for their website, and be running WordPress 5.0 or above. End-users should also be familiar with managing DNS records, specifically A-Records, with their web host. These requirements are necessary to make sure domains are pointing to the correct location. These are common features and available through many hosts. Each host should have specific instructions for working with these features.</p>\n\n\n\n<p>The big value-add will be the plugin’s custom templates and its upcoming Gutenberg blocks. These will allow users to quickly build out single-page sites that look and feel different from the active theme for their WordPress installation.</p>\n\n\n\n<p>“In line with the idea of complete niche templates (essentially bundled blocks), it makes sense to break that concept down a level in form of niche specific blocks you could pick and choose to create your own landing pages with a bit more freedom,” said Schuller. “There’s so much potential with Gutenberg to get creative, especially when you’re thinking specifically about landing pages and what creators might need to achieve a specific goal.”</p>\n\n\n\n<p>Kurth and Schuller plan to release templates aimed at specific product niches. “I’m hoping to get the first template out the door within the next few weeks,” said Schuller on <a href=\"https://twitter.com/jasonpatricksc/status/1214576733669617664\">Twitter</a>. The concept could be interesting as templates could essentially serve as “mini themes.” If the plugin gains enough traction and a large user base, there is potential for a larger marketplace to form around single-page template designs.</p>\n\n\n\n<p>Take a video tour of the plugin:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n\n</div>\n\n\n\n<p>Schuller said that they are kicking around some other feature ideas for the future. Nothing is set in stone yet. “People have also expressed interest in a Leeflets-style front-end experience for managing pages, which would essentially make Landing Kit a SaaS in a box,” he said. “I’m not sure if that’s something we’ll explore in the near term, but an option at the very least.”</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<p class=\"has-background has-gray-100-background-color bg-gray-100\"><strong>Update – January 8, 2020:</strong> Additional quotes from Landing Kit creators added.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 08 Jan 2020 03:34: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:14:\"<NAME>\";s: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:68:\"WPTavern: Lessons Learned by Stepping Outside WordPress Comfort Zone\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96264\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/lessons-learned-by-stepping-outside-wordpress-comfort-zone\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6861:\"<p>It was late summer in 2018. I was an aging developer who wasn’t quite sure where I fit into the WordPress world anymore. I had spent over a decade learning the ins and outs of the platform that launched my career and also served as a hobby for other pet projects I wanted to tackle.</p>\n\n\n\n<p>In part, I was bored. I needed a new challenge.</p>\n\n\n\n<p>I love WordPress. More than that, I appreciate what WordPress has allowed me to accomplish over the years. However, I was no longer happy with it for my personal blog. It was suitable for the job, but I often found it had a lot more gadgets and gizmos than I needed. I had also been writing blog posts in Markdown for many years rather than the classic editor. WordPress was simply no longer a part of my workflow for my blog. At times, it was a hindrance.</p>\n\n\n\n<p><em>Challenge accepted.</em></p>\n\n\n\n<p>Over a weekend, I built a working custom blog system. I am hesitant to call it a Content Manage System (CMS) because it lacked crucial features, such as an administrative interface, that are at the heart of any CMS. Nevertheless, I built a working system from scratch in two days.</p>\n\n\n\n<p>I had no idea I could accomplish such a feat without relying on the useful functions and tools that WordPress had so generously provided for most of my programming career. I cannot count the number of times I accidentally typed out <code>esc_attr()</code> or <code>esc_html()</code> only to remember those were WordPress functions. <em>My WordPress muscle memory was strong.</em> Without knowing it, everything I had learned through building on top of WordPress pushed me to become a more well-rounded PHP developer. There are few APIs I had not worked with from core WordPress. I understood much of the source code and knew the reasons for a lot of the legacy gunk.</p>\n\n\n\n<p>My personal project paled in comparison to WordPress’ power and still does to this day. However, it moved me outside my comfort zone. It allowed me to explore old ideas in new ways.</p>\n\n\n\n<p>One example was understanding how rewrite rules and routing worked. Some of my friends and I recently joked that no one really understands the WordPress Rewrite API. You just tinker with it until something works and the new code no longer breaks your site. There are many existing libraries out there, but I wanted to understand how this worked for my own edification. Therefore, I set out to build an HTTP request, router, and controller class. The end result was an elegant solution, which borrowed heavily from other PHP frameworks.</p>\n\n\n\n<p>With a simple line of code, as shown below for setting up a “book” content type, I could handle incoming requests for a book page, map it to the correct resource, and output the template on the front end. I began to wonder why I had shied away from this foundational website concept for so many years as a developer.</p>\n\n\n\n<pre class=\"wp-block-code\"><code>// Create \'example.com/books/book-name\'.\n$this->router->get( \'books/{name}\', Controller::class );</code></pre>\n\n\n\n<p>There were many other areas where I began to question the “WordPress way” of doing things. During this journey of discovery, I was able to learn things that I could bring back for use in my WordPress projects. By stepping out into the larger world of website development, I was able to better see the flaws in the platform that helped me fall in love with programming. However, I was also better able to see the beauty in the system that thousands of developers have kept running for the preceding 15 years.</p>\n\n\n\n<h2>It Is Not All About Code</h2>\n\n\n\n<p>I had the opportunity to study and learn large frameworks like <a href=\"https://laravel.com/\">Laravel</a> and <a href=\"https://symfony.com/\">Symfony</a>. However, I also studied how other platforms worked from a pure user-experience perspective.</p>\n\n\n\n<p>The one thing I knew for certain is that I wanted to test platforms created for people who wrote in Markdown. I wasn’t looking for huge platforms to compete with WordPress’ power, such as Joomla or Drupal. Instead, I was looking at lighter-weight solutions like <a href=\"https://getgrav.org/\">Grav</a>, <a href=\"https://jekyllrb.com/\">Jekyll</a>, and <a href=\"https://gohugo.io/\">Hugo</a>. I wanted to understand how the user experience fit in with my workflow.</p>\n\n\n\n<p>Of all the solutions I tested, each had its advantages. Each also had features or methods of doing things that wasn’t to my taste. The good thing about the experience was that I was able to identify how I wanted my blogging platform to work for me. Reading thoughts from others in those communities also allowed me to hear from users outside of the WordPress community about why they loved their preferred blogging system.</p>\n\n\n\n<p>I soldiered forward. Using what I learned from those platforms, I built something that I was happy to use. It wasn’t perfect and would likely never be. Room for growth is not a bad thing.</p>\n\n\n\n<p>During this time, I rekindled my love of blogging with WordPress. While not always the popular opinion, the block editor felt leaps and bounds better than the classic editor. It was something I could see myself using regularly. Aside from my personal blog, I began using it on other projects. I still write in Markdown every day. However, I find myself enjoying writing within WordPress’ editor for the first time in years.</p>\n\n\n\n<h2>Why You Should Try New Platforms</h2>\n\n\n\n<p>From a developer perspective, it is not a good idea to become complacent and rely on a single system. Instead of calling yourself a “WordPress developer,” think beyond that terminology. Instead, you should be a PHP programmer or JavaScript programmer. Or, better yet, simply call yourself a programmer. Programmers solve problems. The tools or languages are what you use to get from Point A to Point B.</p>\n\n\n\n<p>On the job market, being a more well-rounded programmer opens up more opportunities. While most of us can only hope that WordPress will be the leading platform for the next 10, 20, or 50 years, you should be prepared for any future.</p>\n\n\n\n<p>Another benefit of working with other platforms from time to time is that you learn ideas that you can bring back into the WordPress ecosystem. For example, it is interesting to see how the <a href=\"https://roots.io/sage/\">Sage starter theme</a> implements Laravel Blade’s templating engine. These ideas can help shape WordPress’ future.</p>\n\n\n\n<p>Some ideas can be pushed into core WordPress. Others can improve team workflows within agencies.</p>\n\n\n\n<p>Continuing education benefits the WordPress community as a whole. Don’t limit that education to WordPress-specific ideas. Learn from the outside and bring it back.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Jan 2020 21:19: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:14:\"<NAME>\";s: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:45:\"BuddyPress: BuddyPress 5.1.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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=309637\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://buddypress.org/2020/01/buddypress-5-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:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1190:\"<p><a href=\"https://downloads.wordpress.org/plugin/buddypress.5.1.2.zip\">BuddyPress 5.1.2</a> is now available. This is a security release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.</p>\n\n\n\n<p>The 5.1.2 release addresses one security issue:</p>\n\n\n\n<ul><li>Certain REST API requests could result in the exposure of private data. Discovered and reported independently by <a href=\"https://profiles.wordpress.org/walbo/\"><NAME></a> and <a href=\"https://profiles.wordpress.org/finebet/\"><NAME></a>.</li></ul>\n\n\n\n<p>The vulnerability was reported privately to the BuddyPress team, in accordance with <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">WordPress’s security policies</a>. Our thanks to the reporters for practicing coordinated disclosure.</p>\n\n\n\n<p>For complete details, visit the <a href=\"https://codex.buddypress.org/releases/version-5-1-2/\">5.1.2 changelog</a>.</p>\n\n\n\n<p>Update to BuddyPress 5.1.2 today in your WordPress Dashboard, or by <a href=\"https://wordpress.org/plugins/buddypress/\">downloading from the WordPress.org plugin repository</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 03 Jan 2020 21:36:11 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"Boone Gorges\";s: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:80:\"WPTavern: Pods Framework Loses Primary Sponsorship, Seeks Donors To Fund 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=96194\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:90:\"https://wptavern.com/pods-framework-loses-primary-sponsorship-seeks-donors-to-fund-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:8184:\"<img />\n\n\n\n<p><NAME>, lead developer of the Pods Framework, <a href=\"https://pods.io/2020/01/02/pods-needs-your-help-in-2020/\">announced the project was seeking new donors</a> on Thursday. Automattic, the primary sponsor, dropped out after funding the project since 2012. This has put the team in a position to seek help for maintaining and supporting the project. Automattic was previously covering around 90% of the costs.</p>\n\n\n\n<p>The <a href=\"https://wordpress.org/plugins/pods/\">Pods Framework</a> is a WordPress plugin that allows end-users or developers to create and extend custom post types, content types, users, media, and comments. Essentially, it is a complete content management framework for those who need more than the basics that WordPress offers. It has well over a dozen <a href=\"https://pods.io/plugins/\">add-on plugins</a> for extra functionality and currently has over 80,000 active installations.</p>\n\n\n\n<p>There are <a href=\"https://friends.pods.io/about-the-team/\">six primary contributors</a> to the Pods plugin. They have also brought on a React developer who is just getting started with UI work on Pods 2.8. Other than work from the team, the project receives patches and contributions from the larger Pods community.</p>\n\n\n\n<p>With the loss of funding from Automattic, Pods is receiving around $700 each month from donors. “Once we found out that Automattic was going to focus their sponsorship funding towards other priorities of theirs, we put together a plan of action to reduce overall costs,” said Clark.</p>\n\n\n\n<p>The team’s goal is to have at least 200 sponsors. The average recurring monthly donation is about $17. Coupled with their current 40 regular donors, they need an additional 160 at the same donation average to cover costs. This would at least allow the team to be efficient with their time.</p>\n\n\n\n<p>“Right now our feature/fix development and support efforts will begin to suffer from lack of funding because we’ll be spread too thin,” said Clark. “I work a full-time job and can’t pick up the extra weight entirely on my own.” Clark’s job with Modern Tribe gives him some flexibility to work on the project, but it is minimal and only when time is available.</p>\n\n\n\n<p>People who are willing to sponsor the project monthly can contribute via the <a href=\"https://friends.pods.io/donations/become-a-friend/\">Friends of Pods</a> sponsorship page. The project also has a <a href=\"https://friends.pods.io/donations/one-time-donation/\">one-time donation option</a> for those wanting to go that route.</p>\n\n\n\n<h2>Automattic Was Crucial to Success</h2>\n\n\n\n<p>In his announcement, Clark said Automattic’s decision to pull their sponsorship was because the company wanted to put their funds toward native Gutenberg projects. Pods is a project that spans beyond Gutenberg. However, it does have some Gutenberg integration and more features in the works.</p>\n\n\n\n<p>Since 2012, Automattic has been the largest sponsor of Pods. Their funding allowed the team to support and continue developing the plugin. “We’re so appreciative of Automattic’s support,” said <a href=\"https://twitter.com/podsframework/status/1212792297911443456\">Clark on Twitter</a>. “They’ve sponsored Pods for over 7 years, I know their decision was a tough one for them.”</p>\n\n\n\n<p>In 2011, <a href=\"https://wptavern.com/pods-what-happened-after-the-kickstarter-campaign\">Pods surpassed its goal</a> in a Kickstarter campaign. The project raised over $4,000 with a goal of $1,500. The campaign was intended to fund the development of Pods 2.0. In hindsight, the dollar amount was far too low to realistically fund such a complex project.</p>\n\n\n\n<p>“I naively thought that would be enough to accomplish everything and more we wanted to do for our big Pods 2.0 release,” said Clark. “I was really wrong. Adding developers at a late stage in a project can take even more time than you anticipate. I also had to work around those developers’ schedules and spend time coordinating with them instead of building things myself. It was a huge challenge as I hadn’t really led a team on a side project while having a full-time job before.”</p>\n\n\n\n<p>Clark had to reach into his pocket and put money towards the funding problem. Yet, the team hit more roadblocks getting Pods 2.0 released. “That’s when I reached out to Automattic, which they offered to help out here and there to sponsor some more development”, he said. “I was at the right job and had the right developers in place to really make the most of that arrangement. I had tons of time on the clock at work to build projects with Pods and I could build features/fix problems every day. With the added help of the funding, we were covered for many years to come.”</p>\n\n\n\n<p>The arrangement was a blessing for the project, propelling it forward for years. “Without Automattic, we surely couldn’t have continued on with the huge undertaking that the Pods 2.0 rewrite was,” said Clark. “We would have just shelved everything and only added minor fixes/enhancements to Pods going forward.”</p>\n\n\n\n<p>Clark described the funding as crucial to maintaining a premium product for free. “Given what I know about many other free products out there, I can see why our support for Pods itself has sometimes been compared to premium support because of the people we could keep involved helping everyone with their project challenges and Pods questions,” he said.</p>\n\n\n\n<p>After success with Pods 2.0 and several releases, the Pods team reached back out to Automattic. They were able to secure more funding with the agreement that they would diversify their funding and bring in more sponsors, which they were able to accomplish.</p>\n\n\n\n<h2>What the Future Holds</h2>\n\n\n\n<p>Clark is hopeful that they can meet their sponsorship goals. If not, they may have to explore some commercial options. However, he said Pods and its primary features will remain free of charge.</p>\n\n\n\n<p>“Development is not cheap,” said Clark. “In fact, we’ve thought about diversifying our funding for a while, but ironically our sponsorship agreement with Automattic prohibited us from exploring premium add-ons to help fund more growth.”</p>\n\n\n\n<p>While the funding was a blessing, it may have also been a crutch. “If we had suddenly gotten millions of active installs to support, we would have been in big trouble,” he said. “You can’t scale sponsorships with a growing userbase.”</p>\n\n\n\n<p>Clark said he is committed to making sure the next three major feature releases go out for free as part of the main Pods plugin, regardless of the funding situation. “I believe in making it easy to build projects in WordPress and some of those features are just really crucial to normal projects,” he said.</p>\n\n\n\n<p>The team is exploring the potential for premium add-ons. However, if going that route, the add-ons would be with useful features that go beyond the core needs of the plugin. “We have some really awesome features that we’ve always wanted to do and this could be the avenue to build them while giving huge value to our Friends of Pods,” he said. “This could be an added benefit to them for supporting our project, which they’d get as a reward for keeping their Friends of Pods membership active.”</p>\n\n\n\n<p>The future is uncertain. The project is not in danger of disappearing at this point. However, the reality is that development and support have real-world costs that need to be met.</p>\n\n\n\n<p>“It’s still too early to know exactly what we can do with the funding we have and what we can expect to get from our 2020 fundraising efforts,” said Clark. “We don’t know if those ongoing funding struggles will prevent us from spending time to build new add-ons to generate new revenue either. It’s all up in the air right now.”</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 03 Jan 2020 17:59: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:\"<NAME>\";s: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:57:\"WordPress.org blog: The Month in WordPress: December 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8282\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:72:\"https://wordpress.org/news/2020/01/the-month-in-wordpress-december-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:8184:\"<p>As 2019 draws to a close and we look ahead to another exciting year let’s take a moment to review what the WordPress community achieved in December.</p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>WordPress 5.3.1 and 5.3.2 Releases</h2>\n\n\n\n<p>The WordPress 5.3.1 security and maintenance release was announced on December 13. It features 46 fixes and enhancements. This version corrects four security issues in WordPress versions 5.3 and earlier. Shortly afterwards, WordPress 5.3.2 was released, addressing a couple high severity Trac tickets, and includes 5 fixes and enhancements, so you’ll want to upgrade. You can read more about these releases in the announcements for <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\">5.3.1</a> and <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-2-maintenance-release/\">5.3.2</a>.</p>\n\n\n\n<h2>Update on the Nine Core Projects for 2019</h2>\n\n\n\n<p>At the end of 2018, <a href=\"https://profiles.wordpress.org/matt/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>matt</a> <a href=\"https://make.wordpress.org/core/2018/12/08/9-priorities-for-2019/\">announced</a> the nine projects that would be the main focus areas for Core development in the next year. Have we made progress? Yes! <a href=\"https://profiles.wordpress.org/chanthaboune/\" class=\"mention\"><span class=\"mentions-prefix\">@</span>chanthaboune</a> <a href=\"https://make.wordpress.org/core/2019/12/06/update-9-projects-for-2019/\">posted a full update</a> on the team’s work. In brief, two of the projects have been completed and shipped in major releases, four are targeted for release in versions 5.4 and 5.5 of WordPress, and the remaining three have seen significant progress but are not yet slated for completion. These will continue to see progress throughout 2020.</p>\n\n\n\n<p>Want to get involved in building WordPress Core? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> and join the #core channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>WordPress Major Release Calendar</h2>\n\n\n\n<p>The Core team has published <a href=\"https://make.wordpress.org/core/2019/11/21/tentative-release-calendar-2020-2021/\">a tentative release calendar</a> for 2020 and 2021. This is intended to provide the community with more information about what lies ahead.</p>\n\n\n\n<p>The schedule is considered tentative because there are always variables that could affect these plans — not least that the Core team may need more time to finish the work planned for a release.</p>\n\n\n\n<h2>Initial Documentation for Block-Based WordPress Themes</h2>\n\n\n\n<p>The Gutenberg team has started working on <a href=\"https://github.com/WordPress/gutenberg/pull/18890/files\">the initial documentation</a> for what block-based themes might look like, marking a significant change in the way themes are conceptualized. With full-site editing now a realistic goal for WordPress, themes will certainly look different in the future.</p>\n\n\n\n<p>Want to help shape the future of block-based themes in WordPress Core? Following <a href=\"https://make.wordpress.org/core/\">the Core team blog</a> is a good start! You can also join in on the discussion <a href=\"https://make.wordpress.org/themes/2019/12/04/questions-about-the-future-of-themes/\">on this blog post</a>, or help out with the work to <a href=\"https://github.com/WordPress/gutenberg/blob/master/lib/demo-block-templates/index.html\">create a demo space for experimentation with the future of themes</a>. As always, contribution to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a> is open to everyone! Join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a> to see what other people are saying, and contribute your own thoughts.</p>\n\n\n\n<h2>Gutenberg Updates Abound</h2>\n\n\n\n<p>It’s been a busy month for Gutenberg! Version 7.0, including a new navigation block, <a href=\"https://make.wordpress.org/core/2019/11/27/whats-new-in-gutenberg-27-november/\">was announced</a> on November 27. This was followed by <a href=\"https://make.wordpress.org/core/2019/12/11/whats-new-in-gutenberg-11-december/\">version 7.1</a>, announced on December 11; it includes 161 merged pull requests that offer a fresh UI to new users, an option to switch between edit and navigation modes, captions for the table block, and many other enhancements.</p>\n\n\n\n<p>Want to get involved in building Gutenberg? Follow <a href=\"https://make.wordpress.org/core/\">the Core team blog</a>, contribute to <a href=\"https://github.com/WordPress/gutenberg/\">Gutenberg on GitHub</a>, and join the #core-editor channel in <a href=\"https://make.wordpress.org/chat/\">the Making WordPress Slack group</a>.</p>\n\n\n\n<h2>Arrival of the BuddyPress Beta Tester Plugin</h2>\n\n\n\n<p>On December 2, <a href=\"https://buddypress.org/2019/12/bp-beta-tester-1-0-0/\">the BuddyPress Beta Tester plugin</a> was added to the WordPress.org plugins directory. This feature is a great way for the WordPress community to provide early feedback on releases.</p>\n\n\n\n<p>You can <a href=\"https://wordpress.org/plugins/bp-beta-tester/\">download the plugin</a> now. If you find that something is not working as expected during your beta tests, let the BuddyPress team know by submitting a ticket on the <a href=\"https://buddypress.trac.wordpress.org/newticket\">Development Tracker</a> or posting a new topic in the BuddyPress <a href=\"https://buddypress.org/support/\">support forums</a>.</p>\n\n\n\n<h2>An Update on the Block Directory in the WordPress Editor </h2>\n\n\n\n<p>The Design team received lots of excellent feedback on the <a href=\"https://make.wordpress.org/design/2019/07/11/block-directory-in-wp-admin-concepts/\">early concepts for the Block Directory</a>. This feedback was incorporated into a Version 1 update to the <a href=\"https://make.wordpress.org/design/tag/block-directory/\">#block-directory</a> project. The Block Directory is to be included in WordPress 5.5, which is slated for August 2020. To learn more about the Block Directory, check out <a href=\"https://make.wordpress.org/design/2019/12/19/block-directory-in-wp-admin-v1/\">this announcement post</a> and help out by sharing your feedback. </p>\n\n\n\n<p>Want to get involved in building the Block Directory? Follow <a href=\"https://make.wordpress.org/design/\">the Design team blog</a>. If you have a block you’d like to include in the directory you can <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">submit it following the information here</a>. </p>\n\n\n\n<hr class=\"wp-block-separator\" />\n\n\n\n<h2>Further Reading:</h2>\n\n\n\n<ul><li><a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">Guidelines for the Block Directory</a> have been drafted; the team is actively working on them now.</li><li>The<a href=\"https://make.wordpress.org/community/2020-wordpress-global-community-sponsorship-program/\"> Global Community Sponsorship Program for 2020</a> has been announced. </li><li>The Theme Review Team <a href=\"https://make.wordpress.org/themes/2019/12/09/do-not-contact-reviewers-outside-of-the-wordpress-org-system-about-your-review/\">has published a reminder</a> for developers about the proper way to communicate with reviewers.</li><li>The Community Team is in the process of <a href=\"https://make.wordpress.org/community/2019/12/05/community-team-reps-for-2020/\">selecting new team reps</a>.</li><li><a href=\"https://meetup.com/pro/wordpress\">The WordPress meetup program</a> crossed the 800-group mark this month and includes groups from more than 100 countries.</li><li>The team that helped to create the 2019 State of the Word slide deck <a href=\"https://wordpress.org/news/2019/12/state-of-the-word-the-story-of-the-slides/\">shared how the slides were created using Gutenberg</a>, powered by the Slides plugin. </li></ul>\n\n\n\n<p><em>Have a story that we should include in the next “Month in WordPress” post? Please </em><a href=\"https://make.wordpress.org/community/month-in-wordpress-submissions/\"><em>submit it here</em></a><em>.</em></p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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, 03 Jan 2020 17:05: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:10:\"<NAME>\";s: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:22:\"Matt: 29 Books in 2019\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:22:\"https://ma.tt/?p=50689\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/2020/01/29-books-in-2019/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4654:\"<p>As a follow-on to my lists in <a href=\"https://ma.tt/2017/12/books-in-2017/\">2017</a> and <a href=\"https://ma.tt/2019/01/39-books-in-2018/\">2018</a>, here are the books I completed this year. I’ve linked all to the Kindle edition except the Great Mental Models, which is so gorgeous in hardcover you should get that one, and the The World is Sound isn’t available as an ebook. Bold are ones I particularly enjoyed or found myself discussing with others a lot.</p>\n\n\n\n<ol><li><a href=\"https://www.amazon.com/dp/B000JMKNZG/\">The Pilgrimage by <NAME></a></li><li><strong><a href=\"https://www.amazon.com/dp/B079WM7KLS/\">21 Lessons for the 21st Century by Y<NAME></a></strong></li><li><a href=\"https://www.amazon.com/dp/B005MHHRQG/\">No Longer at Ease by Chinua Achebe</a></li><li><a href=\"https://www.amazon.com/dp/B078LJW4G4/\">Imagine it Forward by <NAME></a></li><li><strong><a href=\"https://www.amazon.com/gp/product/1999449002/\">The Great Mental Models Vol. 1 by <NAME></a></strong></li><li><strong><a href=\"https://www.amazon.com/dp/B01MPZNG63/\">Why Buddhism is True by <NAME></a></strong></li><li><a href=\"https://www.amazon.com/dp/B079WNQFZQ/\">There Will Be No Miracles Here by <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B01MSICPW3/\">Less by <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B078VW3VM7/\">Bad Blood by <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B07TMKPD67/\">nejma by <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B07CRJB8WJ/\">Trust Exercise by <NAME></a> (also on <a href=\"https://twitter.com/BarackObama/status/1211033245812441091\">Obama’s book list</a>, and based on the high school I went to, HSPVA)</li><li><strong><a href=\"https://www.amazon.com/dp/B000FCK206/\">Genghis Khan and the Making of the Modern World by <NAME></a></strong></li><li><strong><a href=\"https://www.amazon.com/dp/B005GFBNSW/\">The Way to Love by <NAME></a></strong></li><li><a href=\"https://www.amazon.com/dp/B005BRSFCC/\">The Fifth Agreement by <NAME>, <NAME>, and <NAME></a></li><li><strong><a href=\"https://www.amazon.com/dp/B07CWHYVW5/\">Empty Planet by <NAME></a></strong></li><li><a href=\"https://www.amazon.com/dp/B00JTYQJ3K/\">Brave New World by <NAME></a></li><li><a href=\"https://www.amazon.com/gp/product/B005GG0MXI/\">How to Talk So Kids Will Listen & Listen So Kids Will Talk by <NAME> and <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B07MPXZYJ7/\">Make it Scream, Make it Burn by <NAME></a></li><li><strong><a href=\"https://www.amazon.com/dp/B001JAHG98/\">A Short History of Progress by <NAME></a></strong></li><li><strong><a href=\"https://www.amazon.com/dp/B07G13W75M/\">Conscious: A Brief Guide to the Fundamental Mystery of the Mind by <NAME></a></strong></li><li><strong><a href=\"https://www.amazon.com/dp/0892813180/\">The World Is Sound: Nada Brahma: Music and the Landscape of Consciousness by Joachim-<NAME></a></strong></li><li><a href=\"https://www.amazon.com/dp/B00R3MHWUE/\">The 15 Commitments of Conscious Leadership by <NAME> and <NAME></a></li><li><strong><a href=\"https://www.amazon.com/dp/B004W3FM4A/\">Finite and Infinite Games by <NAME></a></strong></li><li><a href=\"https://www.amazon.com/dp/B079G6KMVS/\">Four Soldiers by <NAME></a></li><li><strong><a href=\"https://www.amazon.com/dp/B07L2F9S6H/\">Working by <NAME></a></strong></li><li><a href=\"https://www.amazon.com/dp/B0049H9AVU/\">Attached by <NAME> and <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B075HYVP7C/\">Skin in the Game by <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B012271Z5M/\">The Devil’s Financial Dictionary by <NAME></a></li><li><a href=\"https://www.amazon.com/dp/B07FLNFRGK/\">How to Do Nothing: Resisting the Attention Economy by <NAME></a> (also on Obama’s book list)</li></ol>\n\n\n\n<p>What’s interesting is that if you were to purchase every single one of those books, it would be about $349. You could get them all for nothing from your local library, <a href=\"https://www.amazon.com/gp/help/customer/display.html?nodeId=200747550\">even on a Kindle</a>. The money I spend on books is by far and away the best investment I make every year — books expand my mind and enrich my life in a way that nothing else does.</p>\n\n\n\n<p>All years: <a href=\"https://ma.tt/2017/12/books-in-2017/\">2017</a>, <a href=\"https://ma.tt/2019/01/39-books-in-2018/\">2018</a>, <a href=\"https://ma.tt/2020/01/29-books-in-2019/\">2019</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Jan 2020 07: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: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: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:43:\"WPTavern: Building the Community We Deserve\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96166\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:54:\"https://wptavern.com/building-the-community-we-deserve\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:4338:\"<img />\n\n\n\n<p>One of our internal discussions about the future of WP Tavern has stuck with me since it wrapped up. The discussion was centered on pushing comment threads in the right direction. We often receive comments that border on conspiracy-theory territory (<em>and those that cross over head first</em>). We also get comments that make statements of fact without backing up those claims with evidence.</p>\n\n\n\n<p>Not all those who make such comments have ill intentions. The issue is often that the ideas presented in a comment are not fully-fleshed out. Often, the commentator had not taken the time to shape their words into something that births thoughtful responses. Such is the nature of comments on the web.</p>\n\n\n\n<p>WP Tavern’s big goal for 2020 should be about shepherding our community. Going forward, we will take steps toward fostering better discussions.</p>\n\n\n\n<h2>Building Our Community in the New Year</h2>\n\n\n\n<p>Shepherding the community is about creating a welcoming environment for everyone. All of our readers should feel comfortable leaving their thoughts on a given topic.</p>\n\n\n\n<p>As a new writer in a long-standing community, I sometimes receive uplifting private messages and emails from community members. They often have kind words or love the coverage of a specific topic. The trouble is getting some of those people to engage in the comments. As my grandma, who would welcome anyone into her home, would say, “Y’all stop by sometime and chat for a while.” Some people are timid about commenting publicly. Others feel like they will be attacked or their ideas will be dismissed offhand. Fostering a community they would feel comfortable participating in is the goal.</p>\n\n\n\n<p>The first step toward this goal is an <a href=\"https://wptavern.com/comment-policy\">update to our comment policy</a>.</p>\n\n\n\n<p>The intention of our policy has remained the same. In general, be kind to people. The updated policy includes some new guidelines on what is unacceptable and some clearer language in some areas. It would be nice to eventually move back to the point where we no longer moderated every comment before publishing them on the site. We are not there yet, but I remain optimistic.</p>\n\n\n\n<p>The other major plan is around integrating community elements into the site design. Rest assured that this is something being worked on. Better showcasing recent comments is high on the list. However, we can go beyond that by showcasing users with the most comments, top comments by the number of likes, and more. I have some ideas that I hope to implement this year to make our readers feel like they have more of a stake in the site. This place is as much about you all as it is about our team.</p>\n\n\n\n<h2>Ask the Bartender</h2>\n\n\n\n<p>We have quietly added an <a href=\"https://wptavern.com/contact-me/ask-the-bartender\">Ask the Bartender</a> form on the site. This is our idea of an advice column that you might see in traditional journalism.</p>\n\n\n\n<p>At this point, it is experimental. The plan is to publish a periodic article where one of our writers answers questions from our readers. This will give you all an opportunity to bring up the big questions that you want our community to discuss.</p>\n\n\n\n<p>We do not have an official format for how this will work yet. It will largely depend on the questions that people submit. We are open to nearly any type of WordPress-related question right now.</p>\n\n\n\n<h2>What We All Can Do</h2>\n\n\n\n<p>The biggest thing I ask of the Tavern community that we make 2020 the year that we thoughtfully engage with one another. </p>\n\n\n\n<p>More than that, when discussing topics with others online, there is no need to feel like you must win an argument. That usually leads to nowhere good. Present your ideas and let them stand on their own merit.</p>\n\n\n\n<p>With that idea in mind, think about writing responses in the form of a blog post. Then, let us know about the post here at the Tavern. Taking the time to write a post allows your ideas to mature. Doing this lets you build a stronger argument if you rationally think it through. Also, WordPress is blogging software at heart. We should use it more often to blog about WordPress.</p>\n\n\n\n<p>Happy New Year, everyone! Let’s make this a memorable one.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 01 Jan 2020 21:01:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:48:\"WPTavern: Reflecting on 2019: The Year in Review\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96134\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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:\"https://wptavern.com/reflecting-on-2019-the-year-in-review\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:11823:\"<img />\n\n\n\n<p>Another year is in the bag. With a project as large and far-reaching as WordPress, there was no shortage of news and controversy. We covered a lot of stories in 2019 and are gearing up for another exciting year.</p>\n\n\n\n<p>I always like to take a moment at the end of the year to look over everything that happened. Despite how well a website or project performs, it is good to take stock of each success. It is a time of reflection. Even in bad years, you should be able to find positive things to remember. This helps shape how you view your websites, projects, or even life. Ending the year remembering those positive things can help propel you into the new year.</p>\n\n\n\n<p>It is equally important to find areas for improvement. However, you cannot understand what the next steps are until you have taken a look at where you have been. </p>\n\n\n\n<p>With that in mind, let’s take a moment to reflect on the past year’s journey for WP Tavern and WordPress.</p>\n\n\n\n<h2>WP Tavern Stats</h2>\n\n\n\n<p>In 2019, WP Tavern published 382 posts. That is an increase of 52 posts over 2018.</p>\n\n\n\n<p>Average words per post are the highest in WP Tavern’s history, coming in at 587 words. I am certain my long-windedness played a small role in that. We also had fewer quick posts on the whole. That is a format we should experiment with more.</p>\n\n\n\n<p>Total and average comments are down. Admittedly, we have been a bit heavy-handed with deleting comments that break our comment policy this year. Average Jetpack-powered “likes” per post are at an all-time high (6.9 likes per post). Total likes are the second-highest for a year (2,614 likes). We are also seeing a lot of engagement on Twitter. It will be interesting to see how this plays out in 2020 with social media having such a stronghold on how people engage with one another online.</p>\n\n\n\n<p>We need to continue improving both the frequency and the quality of comments.</p>\n\n\n\n<h2>The Year in WordPress</h2>\n\n\n\n<p>WordPress <a href=\"https://wptavern.com/happy-sweet-16-wordpress\">turned 16 years old</a> this year. <em>It’s old enough to drive now.</em></p>\n\n\n\n<p>The community enjoyed three major updates throughout the year:</p>\n\n\n\n<ul><li><a href=\"https://wptavern.com/wordpress-5-1-improves-editor-performance-encourages-users-to-update-outdated-php-versions\">Version 5.1 “Betty”</a> improved editor performance and encouraged users to update PHP.</li><li><a href=\"https://wptavern.com/wordpress-5-2-jaco-released-includes-fatal-php-error-protection-and-a-recovery-mode\">Version 5.2 “Jaco”</a> included PHP fatal error protection and a recovery mode.</li><li><a href=\"https://wptavern.com/wordpress-5-3-kirk-released-brings-new-default-theme-editor-improvements-and-ui-tweaks\">Version 5.3 “Kirk”</a> introduced the Twenty Twenty theme and made significant UI tweaks.</li></ul>\n\n\n\n<p>Most of the year was focused on the Gutenberg plugin and porting its features and improvements into WordPress. WP Tavern covered nearly <a href=\"https://wptavern.com/tag/gutenberg\">everything you ever wanted to know about Gutenberg</a>.</p>\n\n\n\n<p><NAME>’s <a href=\"https://wptavern.com/state-of-the-word-2019-recap-all-roads-lead-to-the-block-editor\">2019 State of the Word</a> primarily focused on the work that went into the block editor in the past 12 months. He also outlined the next phases of the project, which include full-site customization, collaboration between post authors, and multilingual sites.</p>\n\n\n\n<h2><NAME> (Viper007Bond) Passed Away</h2>\n\n\n\n<p>In February, the WordPress community lost one of its greatest members, <NAME>, as his <a href=\"https://wptavern.com/alex-mills-ends-his-battle-with-leukemia\">battle with leukemia ended</a>. Alex was a mentor and hero to many of us. As a developer, I learned more from his work than I may ever be able to pay forward. We never met in person, but he was one of my early teachers by simply leading the way for people like me.</p>\n\n\n\n<p>His <a href=\"https://wordpress.org/plugins/regenerate-thumbnails/\">Regenerate Thumbnails</a> plugin also saved me countless hours over the years. I cannot imagine building or testing WordPress themes without it. <a href=\"https://wptavern.com/automattic-adopts-alex-mills-plugins\">Automattic adopted the plugins</a> Alex built during his WordPress journey.</p>\n\n\n\n<p>Alex, thank you for everything you contributed to the WordPress community.</p>\n\n\n\n<h2>Favorites From 2019</h2>\n\n\n\n<p>The following are various WordPress and Tavern-related things that I found most interesting throughout 2019.</p>\n\n\n\n<h3>Posts From Tavern Writers</h3>\n\n\n\n<p>We have had numerous well-written stories from everyone who has contributed in 2019. The following are personal favorites from contributors other than myself that I wanted to highlight before we close the year out. </p>\n\n\n\n<p>These are my favorites for various reasons and presented in no particular order. Sometimes, I liked the content of the article. At other times, I appreciated them for how well-written they were. If you missed them, now is a good time to hop back and check out some stories our team has written this year.</p>\n\n\n\n<ul><li><a href=\"https://wptavern.com/wordpress-governance-project-flagged-as-unsanctioned-first-meeting-set-for-january-15\">WordPress Governance Project Flagged as Unsanctioned, First Meeting Set for January 15</a></li><li><a href=\"https://wptavern.com/gpl-author-richard-stallman-resigns-from-free-software-foundation\">GPL Author <NAME> Resigns from Free Software Foundation</a></li><li><a href=\"https://wptavern.com/matt-mullenweg-and-david-heinemeier-hansson-discuss-wordpress-market-share-monopolies-and-power-in-open-source-communities\"><NAME> and <NAME> Discuss WordPress Market Share, Monopolies, and Power in Open Source Communities</a></li><li><a href=\"https://wptavern.com/proposal-to-auto-update-old-versions-of-wordpress-to-4-7-sparks-heated-debate\">Proposal to Auto-Update Old Versions of WordPress to 4.7 Sparks Heated Debate</a></li><li><a href=\"https://wptavern.com/automattic-acquires-tumblr-plans-to-rebuild-the-backend-powered-by-wordpress\">Automattic Acquires Tumblr, Plans to Rebuild the Backend Powered by WordPress</a></li><li><a href=\"https://wptavern.com/gutenberg-one-year-later\">Gutenberg: One Year Later</a></li><li><a href=\"https://wptavern.com/possibilities-of-a-cms-in-the-spatial-computing-future\">Possibilities of a CMS in the Spatial Computing Future </a></li></ul>\n\n\n\n<h3>My Articles</h3>\n\n\n\n<p>I am closing in on 70 posts since becoming a fulltime contributor to WP Tavern. This job has allowed me to explore a variety of topics in a few months, and I look forward to continuing this into 2020. I enjoyed writing many stories, but there were two that I was particularly happy to have the opportunity to cover.</p>\n\n\n\n<p>The first was my coverage of the <a href=\"https://wptavern.com/u-s-supreme-court-denies-dominos-appeal-to-determine-whether-websites-must-be-accessible\">U.S. Supreme Court’s denial of Domino’s appeal</a> to determine whether its website must be accessible to all of its customers. This story helped me jump far outside my comfort zone of strictly writing about WordPress and development topics. It was also a stark reminder that we, as a community, need to become better at making the web accessible for all people.</p>\n\n\n\n<p>The post I enjoyed working on the most was <a href=\"https://wptavern.com/chilean-news-publication-el-soberano-first-to-launch-on-newspack\">El Soberano’s launch on Newspack</a>. The interesting thing about covering this story was not the actual re-launch of the publication. It was getting to chat with other journalists, particularly those who were down in the trenches and fighting for justice. It reminded me that, at the end of the day, journalism is always about people.</p>\n\n\n\n<h3>Favorite Theme</h3>\n\n\n\n<p>This was an easy pick. <a href=\"https://wordpress.org/themes/twentytwenty/\">Twenty Twenty</a> takes the top spot on my list. There were themes released this year with designs better-suited to my tastes. There were certainly other themes pushing more limits in terms of functionality.</p>\n\n\n\n<p>What I like most about Twenty Twenty is that it seems unafraid to be bold. It showcases how a theme can have personality while being designed around the block editor. I am not sure if I would ever use it for my sites simply because it’s not my preferred style. However, I appreciate its artistic merit.</p>\n\n\n\n<h3>Favorite Plugin</h3>\n\n\n\n<p>While it was not released in 2019, <a href=\"https://wordpress.org/plugins/give/\">GiveWP</a> is the most interesting plugin I have used this year. It is a fundraising plugin that allows WordPress users to accept donations directly from their website.</p>\n\n\n\n<p>I worked with the plugin in two capacities this year. The first was as a plugin developer who was building an integration between it and another plugin. As a developer, I appreciated how well-written and well-documented the code was. The team behind the plugin includes top-notch programmers.</p>\n\n\n\n<p>I also helped push a couple of friends to set it up for their projects. Both were pleased with their experiences.</p>\n\n\n\n<h2>Top 10 Posts From 2019</h2>\n\n\n\n<p>The following posts are the most-commented posts of the year. Loads of comments typically mean controversy around here, so this list may contain, more or less, the most controversial topics of the year. Either way, there are some great discussions in some of the comment threads.</p>\n\n\n\n<ul><li><a href=\"https://wptavern.com/wp-taverns-new-design-no-more-wood-grain\">WP Tavern’s New Design: No More Wood-Grain</a> <em>(91 comments, 32 likes)</em></li><li><a href=\"https://wptavern.com/jetpack-7-1-adds-feature-suggestions-to-plugin-search-results\">Jetpack 7.1 Adds Feature Suggestions to Plugin Search Results</a> <em>(76 comments, 8 likes)</em></li><li><a href=\"https://wptavern.com/gutenberg-one-year-later\">Gutenberg: One Year Later</a> <em>(75 comments, 29 likes)</em></li><li><a href=\"https://wptavern.com/pluginvulnerabilities-com-is-protesting-wordpress-org-support-forum-moderators-by-publishing-zero-day-vulnerabilities\">PluginVulnerabilities.com is Protesting WordPress.org Support Forum Moderators by Publishing Zero-Day Vulnerabilities</a> <em>(64 comments, 10 likes)</em></li><li><a href=\"https://wptavern.com/black-friday-banner-gone-wrong-advertising-in-free-plugins\">Black Friday Banner Gone Wrong: Advertising in Free Plugins</a> <em>(59 comments, 20 likes)</em></li><li><a href=\"https://wptavern.com/justin-tadlock-joins-wp-tavern\"><NAME> Joins WP Tavern</a> <em>(52 comments, 45 likes)</em></li><li><a href=\"https://wptavern.com/yoastcon-overshadowed-by-twitter-storm-joost-de-valk-seo-industry-leaders-called-out-for-objectifying-women\">YoastCon Overshadowed by Twitter Storm: Joost de Valk, SEO Industry Leaders Called Out for Objectifying Women</a> <em>(37 comments, 5 likes)</em></li><li><a href=\"https://wptavern.com/wordpress-poised-to-begin-implementing-proposal-to-auto-update-older-sites-to-4-7\">WordPress Poised to Begin Implementing Proposal to Auto-Update Older Sites to 4.7</a> <em>(36 comments, 4 likes)</em></li><li><a href=\"https://wptavern.com/rebirth-of-creativity-gutenberg-and-the-future-of-wordpress-themes\">Rebirth of Creativity: Gutenberg and the Future of WordPress Themes</a> <em>(33 comments, 41 likes)</em></li><li><a href=\"https://wptavern.com/wordpress-5-3-kirk-released-brings-new-default-theme-editor-improvements-and-ui-tweaks\">WordPress 5.3 “Kirk” Released, Brings New Default Theme, Editor Improvements, and UI Tweaks</a> <em>(32 comments, 24 likes)</em></li></ul>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 31 Dec 2019 21:06:09 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:85:\"WPTavern: WordPress Theme Review Team Announces Alpha Color Picker for 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:29:\"https://wptavern.com/?p=96116\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:96:\"https://wptavern.com/wordpress-theme-review-team-announces-alpha-color-picker-for-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:5142:\"<img />Using the color picker in the customizer.\n\n\n\n<p>The WordPress Theme Review Team <a href=\"https://make.wordpress.org/themes/2019/12/30/new-color-alpha-package-available/\">announced its color picker control</a> today. The project is a single package that allows theme authors to include an advanced color control in the customizer. The control allows users to select a hex color with an optional alpha channel to handle transparency.</p>\n\n\n\n<p>The color control is the fourth feature package released by the team in 2019. The <a href=\"https://wptavern.com/justin-tadlock-proposes-idea-to-solve-common-theme-issues\">idea for feature packages</a> took off in June. Feature packages are repositories for single features that theme authors may use in their themes. Their purpose is to standardize common features so that developers do not have to <em>recreate the wheel</em>, so to speak.</p>\n\n\n\n<p>Arguably, the color control is the most complex package the team has built. The bulk of the work was handled by feature packages lead, <NAME>. The project is available via its <a href=\"https://github.com/WPTRT/control-color-alpha\">GitHub repository</a> and <a href=\"https://packagist.org/packages/wptrt/control-color-alpha\">Packagist</a>.</p>\n\n\n\n<p>Officially, the team launched version 1.0 in October, but the project has undergone some changes since its release. Initially, the project utilized the Iris color picker script included with WordPress. However, the team ran into trouble making it work as they wanted with RGBA colors. The team refactored the project to use <a href=\"https://casesandberg.github.io/react-color/\">React Color</a> instead.</p>\n\n\n\n<p>“The main issue with this project was the thing that WordPress is most famous for — backward-compatibility,” said Stathopoulos. “Compatibility is one of WP’s greatest assets, but at the same time, a pain for developers. Things don’t get updated because they need to work for plugin A/B/C that hasn’t been updated in 6 years. So scripts like the Iris picker, things that were great half a decade ago, have been abandoned and are just dead weight. RGBA support could easily have been in WP core’s picker. There was always a demand for it. But it never happened.”</p>\n\n\n\n<p>The team decided to move forward without relying on past solutions. Stathopoulos said the biggest hurdle with building the control to use React Color was making it look native to WordPress. He described the project as an example for others to see that it was possible to use React in the customizer.</p>\n\n\n\n<p>Setting up the control with the basics is relatively easy. Theme authors should be able to quickly integrate it into their themes by following the <a href=\"https://github.com/WPTRT/control-color-alpha/blob/v1.1.2/README.md#usage\">usage instructions</a>. Color data is stored as a hex value (e.g., <code>#000000</code>) if there is no transparency or as a RGBA value (e.g., <code>rgba(0,0,0,0)</code>) if there is.</p>\n\n\n\n<p>The control does come with more advanced features. For example, it is possible to store color data as an array, which includes a slew of information, such as:</p>\n\n\n\n<ul><li>RGB (red, green, blue)</li><li>HSL (hue, saturation, lightness)</li><li>Alpha transparency</li><li>Hex</li><li>CSS value</li><li>Accessibility properties</li></ul>\n\n\n\n<p>The accessibility properties are interesting and may allow theme authors to help to ensure users choose colors that meet accessibility standards. Some of the included data is the color’s luminance, contrast with white and black, max contrast color, and more.</p>\n\n\n\n<h2>The Future of Feature Packages</h2>\n\n\n\n<p>Currently, the TRT’s feature packages are not widely adopted by theme authors. The overall project is still in its infancy. In the wake of the news that WordPress will be moving toward full-site editing, the team is not sure what that will mean for the project going forward.</p>\n\n\n\n<p>Stathopoulos said that some theme authors are hesitant to do big things at the moment. It’s a tough sell to get developers on board when the future of theme development is in a holding pattern, waiting for the other Gutenberg shoe to drop.</p>\n\n\n\n<p>“We’ve been discussing and thinking of what packages we should build,” said Stathopoulos. “The problem is that the editor is the centerpiece of WordPress. Everything else just surrounds the editor. Gutenberg is expanding, and it looks like it’s taking over everything else in WordPress. So we think the next packages should be around the editor too.”</p>\n\n\n\n<p>He said some of the initial package ideas like a standardized hook system, more customizer controls, and accessible menus may not be the best route. Those ideas may not make sense in the context of a block-editing world. The team could see the launch of such packages dead on arrival.</p>\n\n\n\n<p>“It’s a tricky, transitional period for themes and theme developers,” said Stathopoulos. “We all need to learn how to better leverage the editor.”</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Mon, 30 Dec 2019 20:28: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:14:\"<NAME>\";s: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:52:\"WPTavern: What Should an Author Bio Block Look Like?\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=96070\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:62:\"https://wptavern.com/what-should-an-author-bio-block-look-like\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:6173:\"<img />Two author bio block mock-ups compared.\n\n\n\n<p><NAME>, co-representative for the WordPress design team, <a href=\"https://make.wordpress.org/design/2019/12/23/author-card-block-exploration/\">shared an early exploration</a> of an author card block. Community members explored several ideas at the design table during the contributor day at WordCamp US 2019. In the post, Wold followed up on the original sketches from that melding of design minds.</p>\n\n\n\n<p>The original idea for the author block was a <a href=\"https://github.com/WordPress/gutenberg/issues/1844\">GitHub ticket</a> created in July 2017, but it was far ahead of its time. The Gutenberg project needed to focus on the basics and more common blocks for post content at that point. Now is the time to shift gears and begin work on these more complex blocks that will likely be a large part of the full-site editing phase of the project.</p>\n\n\n\n<p>Currently, there are several proposed components to the author block:</p>\n\n\n\n<ul><li>Image/Avatar</li><li>Name</li><li>Description/Biography</li><li>Website Link</li><li>Social Network Links</li><li>Recommended Posts</li></ul>\n\n\n\n<p>I am on the fence about a recommended posts option as part of the block. If they were recommended posts written by that author, it could be an interesting concept to explore. However, version 1 of the block should focus on the most common elements, which the other components in the list cover.</p>\n\n\n\n<p>Wold asked four key questions about the future of the block. The following are my responses to each.</p>\n\n\n\n<h2>What Is the Value of the Block and How Will It Be Used?</h2>\n\n\n\n<p>Coming from the theme world, what surprises me is that WordPress has never standardized on this feature at this point. Author bio sections are commonplace in theme development. Core should have standardized this feature years ago. We have a standard search form, comment list, featured image, and more. Many of the features that WordPress has standardized over the years were born out of theme designers carving the path forward, and author bios are no different.</p>\n\n\n\n<p>It has long made sense for an author bio template tag to exist. However, we are living in a block world. The concept has merely shifted.</p>\n\n\n\n<p>We do not need an author bio block today. We will need it tomorrow. As we shift closer and closer to full-site editing, we need to be building, iterating, and testing these types of blocks in preparation for the point of no return. This block, along with similar blocks, should drop in core at the same time the switch is flipped on full-site editing.</p>\n\n\n\n<p>The primary use case will be for end-users to edit their theme’s block templates to stick the author bio at the end of their single post views. However, such a block need not be limited to that scenario. Users could create a “team” or “authors” page on their site. Some may want to drop these into columns or create some sort of gallery of author bios.</p>\n\n\n\n<p>I could see taking this even further and naming it a “user bio” block. Use cases do not have to be centered around the concept of an author.</p>\n\n\n\n<h2>Where Should the Author Data Come From?</h2>\n\n\n\n<p>The primary, or at least initial, source of data should come from user data and metadata stored in the database. It does not make sense to duplicate efforts by retyping content within the block if it already exists.</p>\n\n\n\n<p>One big question will be around social icons. If these are a part of the block, there is no current source to pull the URLs from. If automatically generating the data, WordPress will need to add social media contact methods to the user profile screen in the admin. That can be a slippery slope when deciding which social networks to include. However, core WordPress could stick to three or four major networks and provide a filter hook for plugin authors to utilize along with a standard for how additional fields are handled.</p>\n\n\n\n<p>There is also the possibility that this block could simply be a pre-defined pattern of existing, smaller blocks that pulled in data like a user biography, user social icons, and user avatar. Then, the site owner could move other blocks in and out as they saw fit.</p>\n\n\n\n<h2>What Block Design Options Should Be Available?</h2>\n\n\n\n<p>The obvious design options are the standard text color, background color, and font size options. <a href=\"https://github.com/WordPress/gutenberg/issues/16848\">Border design options</a> would be a bonus, but that goes beyond the scope of this specific block.</p>\n\n\n\n<p>The standard alignment options would be welcome, particularly center, wide, and full. An alignment option for the avatar image to shift it left or right could also be useful. It could work similarly to the existing Media & Text core block.</p>\n\n\n\n<p>I would not go overboard with design options. Let theme authors create custom block styles for users to choose from. That is the theme author’s job.</p>\n\n\n\n<h2>What Additional Features Should the Block Handle?</h2>\n\n\n\n<p>Outside of an avatar and biography, a social icon list is the most necessary feature. It is almost ubiquitous with author bio boxes.</p>\n\n\n\n<p>What I would like to see is an author/user “gallery” block that builds upon this initial idea. At the moment, I am already imagining the painful user experience of creating a team page and putting individual user bio blocks into columns. Then, I am further imagining having to update that page and potentially move columns around. As an end-user, there are times when I want to micro-manage certain aspects of my site. This would not be one of them. Just give me a simple block to list user bios in some sort of columnized format.</p>\n\n\n\n<p>Such a block could provide an avenue for many types of options. Maybe an option to list authors of a certain post type. Perhaps an option to list users by role. Or, let me list the top users by post count.</p>\n\n\n\n<p>This idea may be pushing over into plugin territory. However, in terms of what I would want to do with my sites, this would be high on the list.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Dec 2019 20:00:24 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s: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:18:\"Joseph: 2020 Style\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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:\"https://blog.josephscott.org/?p=17917\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://blog.josephscott.org/2019/12/27/2020-style/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:951:\"<p>With the year 2020 fast approaching, I thought it would be a good time to change up the style on <a href=\"https://blog.josephscott.org/\">blog.josephscott.org</a>. To that end, I’m trying out the <a href=\"https://wordpress.org/themes/twentytwenty/\">Twenty Twenty WordPress theme</a>.</p>\n<a href=\"https://blog.josephscott.org/wp-content/uploads/2019/12/screenshot-blog-josephscott-org.png\"><img src=\"https://blog.josephscott.org/wp-content/uploads/2019/12/screenshot-blog-josephscott-org-450x1024.png\" alt=\"\" width=\"450\" height=\"1024\" class=\"size-large wp-image-17932\" /></a>blog.josephscott.org\n<p>One of the things I’m really happy to see in the Twenty Twenty theme is the use of <a href=\"https://github.com/WordPress/twentytwenty/pull/163\">vanilla JavaScript, without jQuery</a>. I’m hopeful that more WordPress themes will follow that pattern ( jQuery has been great, but if you don’t need it, don’t use it ).</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 27 Dec 2019 18:02: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:11:\"josephscott\";s: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:66:\"WPTavern: Rank Math SEO Plugin Adds WordPress Block Editor Support\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=95921\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/rank-math-seo-plugin-adds-wordpress-block-editor-support\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5310:\"<p>The team behind the <a href=\"https://wordpress.org/plugins/seo-by-rank-math/\">Rank Math SEO plugin</a> released an update that includes full support for the block editor on December 18. The update includes around two dozen features, improvements, and fixes. The biggest feature update was the inclusion of a new plugin sidebar for the block editor.</p>\n\n\n\n<p>Some of the new features include a filter for unlimited focus keywords, an email notification each time the plugin is automatically updated, and a warning when using the review Schema type. It also improved compatibility with the Elementor plugin’s sitemap module and added Advanced Custom Fields integration to the sidebar. A full list of features is available in the plugin’s <a href=\"https://rankmath.com/changelog/\">public change log</a>.</p>\n\n\n\n<p>The team has a <a href=\"https://s.rankmath.com/demo\">public demo available</a> for end-users to test the plugin without having to install it on their sites.</p>\n\n\n\n<p><NAME>, co-founder and CMO at Rank Math, said that everyone on the team had been experimenting with the Gutenberg plugin since the first beta was released. “We had some experience with Gutenberg, but working on Rank Math has taught us so many things and helped us on so many levels,” he said.</p>\n\n\n\n<p>It was not always a smooth journey. Ahluwalia said the team wanted to keep the plugin lightweight and not sacrifice speed with new technologies. “We had to learn React, Webpack, ES6, etc.,” he said. “In essence, we had to re-learn patterns, practices, and pitfalls of Gutenberg, and we had to do it all with little-to-no documentation available. We had to dive deep into the code and get ourselves familiar with every line of code to ensure nothing interfered with the existing functions of our plugin.”</p>\n\n\n\n<h2>Testing the Block Editor Sidebar</h2>\n\n\n\n<img />Rank Math sidebar as seen in the block editor.\n\n\n\n<p>Immediately upon activating the update, I noted the Rank Math button at the top right of the editor. Admittedly, I was not happy with the space the button took up or its difference in design when compared to other plugin sidebar buttons. Instead of a simple icon, the button includes both an icon and an SEO score. As more and more plugins and themes begin adding sidebars of their own, this space could become cluttered quickly. I would like to see this scaled back to simply be an icon and not take up precious screen real estate.</p>\n\n\n\n<p>The plugin manages to pack a ton of options and information into a tight spot. Once viewing the plugin sidebar, it presents four sub-tabs (General, Advanced, Schema, and Social), each with custom panels or sections. While I am not generally a fan of complex SEO plugins and prefer solutions such as <a href=\"https://wptavern.com/slim-seo-keeps-options-simple-and-handles-the-legwork-of-seo\">Slim SEO</a>, the plugin handles the interface gracefully.</p>\n\n\n\n<p>In comparison to the old meta boxes, the interface is a huge step up. The meta box system used in previous versions of the plugin or with the current Classic editor is cumbersome at best. The team had to get more creative to pull off a solution for the sidebar, which forced them to tighten up the interface.</p>\n\n\n\n<p>Not all users were happy with the <a href=\"https://wordpress.org/support/topic/sidebar-really/\">narrow space</a> provided by the new sidebar. The Rank Math team was ahead of the game and included a <a href=\"https://rankmath.com/kb/filters-hooks-api-developer/#disable-gutenberg-sidebar\">filter hook to disable</a> this feature. Disabling will return the old-style meta box at the bottom of the post-editing area.</p>\n\n\n\n<p>“Supporting both the Classic Editor and Gutenberg at once with a single plugin is hectic to say the least,” said Ahluwalia. “We would rather put our energy into a single editing experience, but seeing how WordPress is evolving after Gutenberg, we have to double our efforts to offer a consistent user experience.”</p>\n\n\n\n<p>At the moment, the team plans to continue supporting the classic editor until at least 2022. “Depending on the user feedback and the acceptance of the Classic editor, we can continue to support it even further,” said Ahluwalia.</p>\n\n\n\n<p>The Rank Math also team shared a video of block editor support on Twitter:</p>\n\n\n\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\"><p lang=\"en\" dir=\"ltr\">🎉 Here\'s a sneak preview of Rank Math\'s upcoming major update which adds <a href=\"https://twitter.com/hashtag/Gutenberg?src=hash&ref_src=twsrc%5Etfw\">#Gutenberg</a> support – now it\'s even easier for people using the latest version of <a href=\"https://twitter.com/hashtag/WordPress?src=hash&ref_src=twsrc%5Etfw\">#WordPress</a> to use Rank Math <a href=\"https://twitter.com/hashtag/SEO?src=hash&ref_src=twsrc%5Etfw\">#SEO</a> 🔝<br /><br />Want to take the Beta for a spin now? Join us on Facebook<a href=\"https://t.co/Ykfhj2d5Z1\">https://t.co/Ykfhj2d5Z1</a> <a href=\"https://t.co/E1ItpD0b4B\">pic.twitter.com/E1ItpD0b4B</a></p>— <NAME> SEO (@rankmathseo) <a href=\"https://twitter.com/rankmathseo/status/1198226289129189376?ref_src=twsrc%5Etfw\">November 23, 2019</a></blockquote>\n</div>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Dec 2019 19:53: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:14:\"<NAME>\";s: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:45:\"BuddyPress: BuddyPress 5.1.1 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:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:32:\"https://buddypress.org/?p=309527\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:48:\"https://buddypress.org/2019/12/buddypress-5-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:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:1122:\"<p><a href=\"https://downloads.wordpress.org/plugin/buddypress.5.1.1.zip\">BuddyPress 5.1.1</a> is now available. This is a security release. All BuddyPress installations are strongly encouraged to upgrade as soon as possible.</p>\n\n\n\n<p>The 5.1.1 release addresses one security issue:</p>\n\n\n\n<ul><li>A denied of service was fixed that could allow a logged in user to remove another user’s avatar and also any empty folder. Discovered by <a href=\"https://hackerone.com/nomnom\">nomnom</a>.</li></ul>\n\n\n\n<p>Thi vulnerability was reported privately to the BuddyPress team, in accordance with <a href=\"https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/\">WordPress’s security policies</a>. Our thanks to the reporter for practicing coordinated disclosure.</p>\n\n\n\n<p>For complete details, visit the <a href=\"https://codex.buddypress.org/releases/version-5-1-1/\">5.1.1 changelog</a>.</p>\n\n\n\n<p>Update to BuddyPress 5.1.1 today in your WordPress Dashboard, or by <a href=\"https://wordpress.org/plugins/buddypress/\">downloading from the WordPress.org plugin repository</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_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 Dec 2019 09:45:07 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:12:\"<NAME>\";s: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:78:\"WPTavern: Version 1 Prototype of the WordPress Admin Block Directory Announced\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=95946\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:89:\"https://wptavern.com/version-1-prototype-of-the-wordpress-admin-block-directory-announced\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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:\"<p><NAME> shared the first version of the <a href=\"https://make.wordpress.org/design/2019/12/19/block-directory-in-wp-admin-v1/\">WordPress admin block directory prototype</a> the design team has been working on. The goal is to bring the block directory to the admin in WordPress 5.5, which is currently <a href=\"https://wptavern.com/progress-on-wordpress-2019-projects-sets-2020-roadmap\">set for August 2020 on the roadmap</a>. The post also outlines reusable components that can be used in other areas of the admin in the long term.</p>\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-wp-admin?node-id=1460%3A277&viewport=366%2C373%2C0.25&scaling=min-zoom\">Figma prototype</a> is available for those who want to give it a test run. It is important to remember that this is an early version and many things can change by the time the block directory lands in WordPress.</p>\n\n\n\n<p>The prototype was built after feedback from the <a href=\"https://make.wordpress.org/design/2019/07/11/block-directory-in-wp-admin-concepts/\">first round of concepts shared</a> in July on the Make Design blog.</p>\n\n\n\n<p>For this admin project to be successful, WordPress plugin developers will need to start submitting blocks to the <a href=\"https://wordpress.org/plugins/browse/block/\">block directory</a> on WordPress.org. At the moment, there are only 10 blocks listed. Getting in early will give block authors an edge on the competition. The block directory has a few <a href=\"https://make.wordpress.org/meta/2019/12/06/block-directory-plugin-guidelines/\">additional guidelines</a> beyond normal plugins that authors should review.</p>\n\n\n\n<h2>About Blocks Screen</h2>\n\n\n\n<img />About Blocks admin screen.\n\n\n\n<p>The About Blocks screen is the primary blocks admin screen. It appears to be an informational page with resources for users to learn more about using blocks on their sites. It also has links to development resources for designing and building blocks. </p>\n\n\n\n<p>Making this information directly available, especially to users, would be a smart decision if it makes it into the final design. As we move toward an entirely new way to build websites with WordPress, it is important to provide learning tools to users. This seemed to be one of the missing components when the block editor first launched in core. If done right, it could ease the burden on new users and old users who are transitioning to the new editor.</p>\n\n\n\n<p>The above screenshot also shows the new admin screen header proposal. The page title is followed by a short description of what the screen is about. Followed the intro are action links on the left and meta-type links on the right. I am a fan of the generous use of whitespace and extra information.</p>\n\n\n\n<h2>Add Blocks Screen</h2>\n\n\n\n<img />Add Blocks screen.\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A2958&viewport=366%2C373%2C0.25&scaling=min-zoom\">add blocks screen</a> is similar to the current new plugin screen in the WordPress admin. The primary “Featured” tab (the tab opened when first visiting the screen) is broken down into various sections, such as “Blocks We Love” and “Popular Tags.”</p>\n\n\n\n<p>One of the more interesting sections of this page is the “Top Authors” list. This concept would be a great way to give recognition to block authors who are building useful blocks for the community.</p>\n\n\n\n<p>There is also a “Recent Blocks” section near the bottom of the page. I would rather see a top tab for that. It feels a bit buried in the current design. New plugin and theme authors already struggle to break into popular lists. Recently-added blocks should be higher up the page or have a dedicated tab/page to showcase them a bit more.</p>\n\n\n\n<h2>Installed Blocks Screen</h2>\n\n\n\n<img />Installed Blocks screen.\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A2958&viewport=366%2C373%2C0.25&scaling=min-zoom\">block installation screen</a> is similar to the existing installed plugins screen in core and lists all of the blocks that are installed. There are also active and inactive tabs. Improvements here are primarily around list table design. On the whole, they are minor adjustments, but the look of the tables is much nicer. <em>Can we have this in core, across the board, now?</em></p>\n\n\n\n<p>A new element is the “Instances” column, which lists the number of times a block has been used on the site. By clicking the number, you are taken to a new screen that lists the posts the block has been used in. It also displays the instances for each post. This would be a useful feature for deciding whether to deactivate or remove a block.</p>\n\n\n\n<p>Side note to this: I have worked on numerous projects in the past where I was doing cleanup and attempting to figure out if a plugin, especially those with shortcodes, were in use on the site. Showing the instances count for blocks is brilliant.</p>\n\n\n\n<h2>Manage Blocks Screen</h2>\n\n\n\n<img />Manage Blocks screen.\n\n\n\n<p>Plugins such as <a href=\"https://wordpress.org/plugins/block-options/\">EditorsKit</a> have had built-in block management for a while. However, this feature feels like it should be in core WordPress. There are numerous core blocks that some users will likely never use. Having the ability to hide them from the block inserter will reduce clutter and make it easier to find the blocks they need.</p>\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A14224&viewport=366%2C373%2C0.25&scaling=min-zoom\">block management screen</a> will allow users to activate or deactivate any specific block on their website. Like the block installation screen, it also displays the number of instances a block is in use.</p>\n\n\n\n<h2>Reusable Blocks Screen</h2>\n\n\n\n<img />Reusable Blocks screen.\n\n\n\n<p>The <a href=\"https://www.figma.com/proto/Y4jCNPkjCuSRiGYEoaAZujhm/Gutenberg-Block-Directory-(wp-admin)?node-id=1460%3A15861&viewport=366%2C373%2C0.25&scaling=min-zoom\">reusable blocks screen</a> is already available in WordPress. It does not currently have an admin menu link, so it is not easily discoverable. You can view it by going to the <code>yoursite.com/wp-admin/edit.php?post_type=wp_block</code> URL or clicking the “Manage All Reusable Blocks” link under the “Reusable” tab in the block inserter.</p>\n\n\n\n<p>This screen allows users to manage blocks that are stored for reuse within multiple posts. Like the installation and management screens, the prototype displays an instances column for tracking how often the block has been used.</p>\n\n\n\n<p>Users can import and export reusable blocks. It will be interesting to see if more WordPress users start sharing their block creations with others once this screen has better exposure or if it will be something people simply use to copy blocks from site to site.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 20 Dec 2019 21:09: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:14:\"<NAME>\";s: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:53:\"WPTavern: WordPress 5.3.2 Addresses a Handful of Bugs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:29:\"https://wptavern.com/?p=95927\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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://wptavern.com/wordpress-5-3-2-addresses-a-handful-of-bugs\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2810:\"<p>On December 18, less than a week since <a href=\"https://wptavern.com/wordpress-5-3-1-includes-security-and-bug-fixes-accessibility-enhancements-and-twenty-twenty-changes\">WordPress 5.3.1 security update</a> shipped to the masses, the core team dropped a <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-2-maintenance-release/\">version 5.3.2 maintenance release</a>. No security issues were named in this update. Instead, 5.3.2 addresses a couple of high-priority bugs along with a few other issues.</p>\n\n\n\n<p>Users with automatic updates enabled should already be updated to the latest version or will receive an update soon. Other users should update as soon as they are able, especially if their installation is affected by any of the following issues.</p>\n\n\n\n<p>The first high-priority fix addressed an issue with modified post objects that have an invalid date. The fix ensures that the <code>get_feed_build_date()</code> function handles this scenario. The documentation was updated to clarify the function will return <code>false</code> on failure. This change also led to a comparison-check fix in the test tools when inserting a post with a future or published status.</p>\n\n\n\n<p>The second major bug fixed in 5.3.2 was an edge case where unique file names could clash. On case-sensitive systems, the <code>wp_unique_filename()</code> function failed to rename some files when the uploaded file matched an existing file with an uppercase file extension. The fix addresses a fatal error in those cases.</p>\n\n\n\n<p>Developers tackled another issue with the <code>wp_unique_filename()</code> function. When a destination directory for an uploaded file was unreadable, WordPress was throwing PHP warnings. The fix includes only running the final filename-collision test for files that are saved to the user’s <code>/uploads</code> directory.</p>\n\n\n\n<p>Building off the accessibility work in the previous release, buttons with the <code>.active</code> class are now properly styled in the non-default admin color schemes. On some screens, particularly the Permalinks admin screen, active buttons had white text on a light gray background, making them unreadable.</p>\n\n\n\n<p>Users who wish to do so, can <a href=\"https://wordpress.org/support/wordpress-version/version-5-3-2/\">view the full release documentation</a> from WordPress.</p>\n\n\n\n<p>With the widespread usage of automatic updates, it would be nice to see more of these quicker releases during the development cycle. Maybe weekly releases are a bit much. However, shipping a few extra minor releases between major upgrades would be a good opportunity to knock out some of the 6,500 Trac tickets on <a href=\"https://wptavern.com/progress-on-wordpress-2019-projects-sets-2020-roadmap\">WordPress’ 2020 roadmap</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Fri, 20 Dec 2019 00:19: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:14:\"<NAME>\";s: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:55:\"WordPress.org blog: WordPress 5.3.2 Maintenance Release\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"guid\";a:1:{i:0;a:5:{s:4:\"data\";s:34:\"https://wordpress.org/news/?p=8275\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:4:\"link\";a:1:{i:0;a:5:{s:4:\"data\";s:71:\"https://wordpress.org/news/2019/12/wordpress-5-3-2-maintenance-release/\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:2828:\"<p>WordPress 5.3.2 is now available!</p>\n\n\n\n<p>This maintenance release features 5 fixes and enhancements.</p>\n\n\n\n<p>WordPress 5.3.2 is a short-cycle maintenance release. The next major release will be version 5.4.</p>\n\n\n\n<p>You can download WordPress 5.3.2 by clicking the button at the top of this page, or visit your<strong> Dashboard → Updates</strong> and click <strong>Update Now</strong>.</p>\n\n\n\n<p>If you have sites that support automatic background updates, they’ve already started the update process.</p>\n\n\n\n<h2>Maintenance updates</h2>\n\n\n\n<p>Shortly after <a href=\"https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/\">WordPress 5.3.1 was released</a>, a couple of high severity Trac tickets were opened. The Core team scheduled this quick maintenance release to resolve these issues.</p>\n\n\n\n<p>Main issues addressed in 5.3.2:</p>\n\n\n\n<ul><li>Date/Time: Ensure that <code>get_feed_build_date()</code> correctly handles a modified post object with invalid date.</li><li>Uploads: Fix file name collision in <code>wp_unique_filename()</code> when uploading a file with upper case extension on non case-sensitive file systems.</li><li>Media: Fix PHP warnings in <code>wp_unique_filename()</code> when the destination directory is unreadable.</li><li>Administration: Fix the colors in all color schemes for buttons with the <code>.active</code> class.</li><li>Posts, Post Types: In <code>wp_insert_post()</code>, when checking the post date to set <code>future</code> or <code>publish</code> status, use a proper delta comparison.</li></ul>\n\n\n\n<p>For more information, <a href=\"https://core.trac.wordpress.org/query?status=closed&type=!task+(blessed)&resolution=fixed&milestone=5.3.2&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority\">browse the full list of changes on Trac</a> or check out the <a href=\"https://wordpress.org/support/wordpress-version/version-5-3-2/\">version 5.3.2 HelpHub documentation page</a>.</p>\n\n\n\n<h2>Thanks!</h2>\n\n\n\n<p>Thank you to everyone who contributed to WordPress 5.3.2:</p>\n\n\n\n<p><a href=\"https://profiles.wordpress.org/azaozz/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/rarst/\">Andrey “Rarst” Savchenko</a>, <a href=\"https://profiles.wordpress.org/dd32/\">Dion hulse</a>, <a href=\"https://profiles.wordpress.org/eden159/\">eden159</a>, <a href=\"https://profiles.wordpress.org/audrasjb/\">Jb Audras</a>, <a href=\"https://profiles.wordpress.org/ryelle/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/pbiron/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/sergeybiryukov/\"><NAME></a>, <a href=\"https://profiles.wordpress.org/tellyworth/\">Tellyworth</a>.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 18 Dec 2019 22:42:26 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:9:\"Jb Audras\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}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:64:\"WPTavern: One-Time vs. Recurring Payments for 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=95900\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/one-time-vs-recurring-payments-for-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:6248:\"<p><NAME> posed the question at Digging into WordPress: <a href=\"https://digwp.com/2019/12/pricing-model-better/\">Which Pricing Model Do You Prefer: One-Time or Recurring?</a></p>\n\n\n\n<p>It is not the first time the question has been asked in the WordPress community and will not be the last. It is important that we keep coming back to it from time to time.</p>\n\n\n\n<p>In the early days of the commercial WordPress ecosystem, many shops sold products for a one-time fee. This was particularly true during the 2007-2010 years, which were what many dub the “WordPress themes heyday,” a period in which theme shops raked in tons of cash due to lack of competition.</p>\n\n\n\n<p>As the market became more saturated, many businesses saw the writing on the wall. One-time fees for commercial themes or plugins did not make for a sustainable business model. Of course, some companies pushed forward with that model. They were either large enough to capitalize on an influx of new customers every year or they continued to push out new products for existing customers to buy.</p>\n\n\n\n<p>Today, most theme and plugin shops utilize a recurring business model. Many of those shops also set up automatic renewals. From a business perspective, companies need to keep existing customers while bringing in new buyers to continue maintaining, supporting, and building new features for the current product catalog. Companies also need growth to build new products. A recurring fee helps ease the burden of supporting and maintaining the existing products.</p>\n\n\n\n<p><NAME> <a href=\"https://pippinsplugins.com/automatic-license-renewals-twenty-months-later/\">saw massive revenue growth</a> over 20 months after turning on automatic renewals across his company’s various products. Other companies have seen similar increases with the same model.</p>\n\n\n\n<p>As a former business owner, I <em>dumb-lucked</em> my way into yearly, recurring payments. When I first launched a theme shop in 2008, that was the model I went with. I did not know a single thing about running a business except that money exchanged hands. I was in my early 20s and accustomed to living off minimum wage, digging change from the couch to buy a value meal, and finding creative ways — short of dumpster diving — to scrape by. Anything better than that was a success for me. Recurring payments just made sense, especially because I was vastly undercutting my competitors in price. That one decision helped sustain my business for many years. In hindsight, I would not have had the little success I had with a single-payment model because I never brought in enough new customers.</p>\n\n\n\n<p>Having worked on the business end of WordPress for over a decade and being a member of the community for even longer, it is easy for me to say most companies should use a recurring business model.</p>\n\n\n\n<p>However, as a software customer in general, I have not always maintained that mindset. There are many pieces of software that I loathe paying for each year. This was particularly true before running a business that dealt with software. There is a part of me that feels some shame for disliking the recurring model with non-WordPress software. Those businesses need to pay their employees and afford to continue making the product better.</p>\n\n\n\n<p>On the other hand, there is always that part of me that simply wants to pay for something once and always have access to it. Perhaps I am a product of my culture. Software is unlike other art forms where Version 1.0 is the finished product. Customers do not always see the work that goes on to maintain, support, and continue building a product. That is certainly true when I look at non-WordPress software.</p>\n\n\n\n<p>For WordPress products, I am always more than happy to pay a recurring fee because I have been on the other side. I also get to talk with others every day who are trying to run their own companies. That human variable in the equation changes how I view software in the WordPress ecosystem in a way that is much harder with other software.</p>\n\n\n\n<h2>A Middle Ground</h2>\n\n\n\n<p>Starr pointed out a middle-of-the-road option that few WordPress companies take but is often the model used for other software products. Major releases of software carry an upgrade fee while minor and patch releases are included with the initial purchase. Often, major software releases have years in between. Customers may not feel like they are constantly having to pay for updates in this system. Major upgrades also mean feature upgrades. Features are what sell the product to the average end-user.</p>\n\n\n\n<p><a href=\"https://www.literatureandlatte.com/scrivener/overview\">Scrivener</a>, a writing program for authors, uses this model. Instead of having to pay yearly, I can upgrade to the new, shiny version when it drops with loads of features. As a customer, I feel like I am getting something tangible when forking over the cash for an update.</p>\n\n\n\n<p>Perhaps I am happy to continue paying for software that helps me pursue my lifelong dream of becoming a novelist. Perhaps the company simply knows how to sell to its customer base. Either way, it is one piece of software that I have never complained about renewing.</p>\n\n\n\n<h2>What is the Best Option?</h2>\n\n\n\n<p>To answer the question posed by Starr, I will always prefer a one-time fee as a customer simply because it is in my nature to want to pay the least amount I can for anything. However, I would prefer most WordPress businesses to go with whatever model is most sustainable for their specific business. We are all in this boat together, and I wish growth for the ecosystem.</p>\n\n\n\n<p>One of the missing pieces with many WordPress plugin and theme shops is that they need to find creative ways to sell the customer on coming back. Support and maintenance can be eye-catching for agencies and freelancers, but they are not always selling points for the average consumer after that initial purchase.</p>\n\n\n\n<p>Right now, there is a sense of complacency as WordPress-related businesses have stuck with similar recurring options over the last several years. It might be time for someone to shake things up.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Wed, 18 Dec 2019 20:37: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:\"<NAME>\";s: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:76:\"WPTavern: Bluehost Launches Premium WordPress Theme Marketplace to Customers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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=95726\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"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/bluehost-launches-premium-wordpress-theme-marketplace-to-customers\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:11:\"description\";a:1:{i:0;a:5:{s:4:\"data\";s:5675:\"<img />Screenshot of the Bluehost Marketplace from the customer dashboard.\n\n\n\n<p>In November, web hosting provider Bluehost <a href=\"https://www.bluehost.com/blog/bluehost-news/introducing-wordpress-themes-to-the-bluehost-marketplace-12981/\">launched a WordPress plugin and theme marketplace</a>. The company integrated with <a href=\"https://www.mojomarketplace.com/\">MOJO Marketplace</a> to provide access to WordPress products via its customer dashboard. Currently, the marketplace is open to third-party theme developers. Plugin authors will have to wait, but they will eventually be able to sell their plugins through the Bluehost Marketplace.</p>\n\n\n\n<p>By integrating with MOJO Marketplace, much of the existing infrastructure and products are already in place. Bluehost can simply offer the products to its customers through a custom-built interface and provide MOJO sellers with another avenue for distribution.</p>\n\n\n\n<p>The idea behind the marketplace is for Bluehost’s customers to be able to build their websites without ever leaving their control panel. “Ultimately, we are trying to save customers time and energy from having to hunt for these things themselves and instead work within the dashboard to find the themes and plugins that are best fit for their site,” said <NAME>, general manager for Bluehost.</p>\n\n\n\n<p>“Our native marketplace also provides our customers with the ability to automatically install the themes and plugins they have purchased, reducing the amount of time and number of steps required to get their site appearance and functionality up and running,” he said.</p>\n\n\n\n<p>The Bluehost Marketplace currently has over 900 themes and 18 WooCommerce plugins for customers to choose from. The themes are all viewable via the <a href=\"https://www.mojomarketplace.com/themes/wordpress\">WordPress themes page</a> on the MOJO website. All themes uploaded by sellers go through a manual review process by the Bluehost Marketplace team before approval. This includes basic items like design quality, functionality, installation, and documentation.</p>\n\n\n\n<p>There is also a “Bluehost Certified” filter available to users who want to use themes that have been further tested for quality control. “We conduct additional reviews to certify themes for our Bluehost Certified category on a quarterly basis,” said Zaheer .</p>\n\n\n\n<p>There appear to be 85 themes that are Bluehost Certified based on a screenshot acquired of the marketplace. However, that number is not verified. The MOJO Marketplace page does not appear to have a filter to view these, but it is available to users of Bluehost’s hosting service.</p>\n\n\n\n<h2>Selling on the Bluehost Marketplace</h2>\n\n\n\n<p>Theme developers who want to sell themes via Bluehost can apply through <a href=\"https://mojosupport.zendesk.com/hc/en-us/categories/200823136-Sellers\">MOJO Marketplace</a>. Authors should note that they would like to be Bluehost Certified. </p>\n\n\n\n<p>Theme sellers who want to get certification must meet the <a href=\"https://my.bluehost.com/hosting/help/certified-wordpress-themes\">Bluehost Certified guidelines</a>. Some are fairly normal and would be expected in today’s market such as responsiveness, browser compatibility, fast load times, and active support from the author.</p>\n\n\n\n<p>Others are a bit of a head-scratcher. </p>\n\n\n\n<p>Certification requires that themes support page builders. It’s unclear which page builders need to be supported and what level of support is necessary. Ideally, this would be the other way around. Page builders should be built in such a way that they do not need theme-specific support.</p>\n\n\n\n<p>Demo content is required. It is not clear if the requirements simply mean to provide an installable XML file with demo content or for the theme to output demo content in the absence of user content. Based on the description, it seems like the latter. If so, I would not want any part of that as a potential theme author. I could see requiring the use of the WordPress starter content feature in this case but nothing more.</p>\n\n\n\n<p>The requirements also list “plugins supported” with no additional description. <em>Good luck to theme authors figuring out exactly what that means.</em></p>\n\n\n\n<p>Bluehost needs to make its Bluehost Certified page more detailed to be attractive to potential theme authors. There are far too many unanswered questions.</p>\n\n\n\n<p><a href=\"https://mojosupport.zendesk.com/hc/en-us/articles/115001076306-Commission-Rates\">Commission rates</a> are the same rates as other themes on the MOJO Marketplace. Themes sold exclusively through the marketplace earn between 50% and 70% based on the number of sales. Non-exclusive theme commissions are at a flat rate of 50%. Both exclusive and non-exclusive authors can distribute their themes through the Bluehost Marketplace.</p>\n\n\n\n<p>“Theme sellers are welcome to set the price of their item,” said Zaheer. “However, we recommend they stay within $49-$69 range. If the review team does not feel the price is uniform with other themes in the same category, they will request a price change in order to be sold on the Marketplace.”</p>\n\n\n\n<p>The pricing recommendation seems to be a bit on the low end, but it is consistent with the theme industry’s race to the bottom. Quality theme work should be at least double.</p>\n\n\n\n<p>Fortunately for theme authors, pricing is based on yearly renewals. They are required to offer technical assistance within 24-48 hours while a user’s yearly support license is up to date.</p>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}s:7:\"pubDate\";a:1:{i:0;a:5:{s:4:\"data\";s:31:\"Tue, 17 Dec 2019 20:40:48 +0000\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}s:32:\"http://purl.org/dc/elements/1.1/\";a:1:{s:7:\"creator\";a:1:{i:0;a:5:{s:4:\"data\";s:14:\"<NAME>\";s:7:\"attribs\";a:0:{}s:8:\"xml_base\";s:0:\"\";s:17:\"xml_base_explicit\";b:0;s:8:\"xml_lang\";s:0:\"\";}}}}}}}}}}}}}}}}s:4:\"type\";i:128;s:7:\"headers\";O:42:\"Requests_Utility_CaseInsensitiveDictionary\":1:{s:7:\"\0*\0data\";a:8:{s:6:\"server\";s:5:\"nginx\";s:4:\"date\";s:29:\"Sat, 08 Feb 2020 18:06:38 GMT\";s:12:\"content-type\";s:8:\"text/xml\";s:4:\"vary\";s:15:\"Accept-Encoding\";s:13:\"last-modified\";s:29:\"Sat, 08 Feb 2020 18:00:07 GMT\";s:15:\"x-frame-options\";s:10:\"SAMEORIGIN\";s:4:\"x-nc\";s:9:\"HIT ord 2\";s:16:\"content-encoding\";s:4:\"gzip\";}}s:5:\"build\";s:14:\"20130911040210\";}','no'),(137,'_transient_timeout_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1581228399','no'),(138,'_transient_feed_mod_d117b5738fbd35bd8c0391cda1f2b5d9','1581185199','no'),(139,'_transient_timeout_dash_v2_88ae138922fe95674369b1cb3d215a2b','1581228399','no'),(140,'_transient_dash_v2_88ae138922fe95674369b1cb3d215a2b','<div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wordpress.org/news/2020/02/the-month-in-wordpress-january-2020/\'>The Month in WordPress: January 2020</a></li></ul></div><div class=\"rss-widget\"><ul><li><a class=\'rsswidget\' href=\'https://wptavern.com/convert-classic-content-to-blocks-with-the-bulk-block-converter-plugin\'>WPTavern: Convert Classic Content to Blocks With the Bulk Block Converter Plugin</a></li><li><a class=\'rsswidget\' href=\'https://wptavern.com/gutenberg-7-4-adds-new-color-controls-link-ui-and-block-scaffolding-for-developers\'>WPTavern: Gutenberg 7.4 Adds New Color Controls, Link UI, and Block Scaffolding for Developers</a></li><li><a class=\'rsswidget\' href=\'https://poststatus.com/syed-balkhi-on-awesome-motives-acquisition-of-all-in-one-seo/\'>Post Status: Syed Balkhi on Awesome Motive’s acquisition of All In One SEO</a></li></ul></div>','no'),(147,'_site_transient_update_themes','O:8:\"stdClass\":4:{s:12:\"last_checked\";i:1581185623;s:7:\"checked\";a:5:{s:13:\"photoblogster\";s:3:\"5.3\";s:14:\"twentynineteen\";s:3:\"1.4\";s:15:\"twentyseventeen\";s:3:\"2.2\";s:13:\"twentysixteen\";s:3:\"2.0\";s:12:\"twentytwenty\";s:3:\"1.1\";}s:8:\"response\";a:0:{}s:12:\"translations\";a:0:{}}','no'),(148,'current_theme','PhotoBlogster','yes'),(149,'theme_mods_photoblogster','a:3:{i:0;b:0;s:18:\"nav_menu_locations\";a:0:{}s:18:\"custom_css_post_id\";i:-1;}','yes'),(150,'theme_switched','','yes'),(152,'_site_transient_timeout_available_translations','1581196461','no'),(153,'_site_transient_available_translations','a:121:{s:2:\"af\";a:8:{s:8:\"language\";s:2:\"af\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-05 08:33:42\";s:12:\"english_name\";s:9:\"Afrikaans\";s:11:\"native_name\";s:9:\"Afrikaans\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/af.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"af\";i:2;s:3:\"afr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Gaan voort\";}}s:2:\"ar\";a:8:{s:8:\"language\";s:2:\"ar\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-03 13:14:07\";s:12:\"english_name\";s:6:\"Arabic\";s:11:\"native_name\";s:14:\"العربية\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/ar.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:2;s:3:\"ara\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:3:\"ary\";a:8:{s:8:\"language\";s:3:\"ary\";s:7:\"version\";s:5:\"4.7.7\";s:7:\"updated\";s:19:\"2017-01-26 15:42:35\";s:12:\"english_name\";s:15:\"Moroccan Arabic\";s:11:\"native_name\";s:31:\"العربية المغربية\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.7/ary.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ar\";i:3;s:3:\"ary\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"المتابعة\";}}s:2:\"as\";a:8:{s:8:\"language\";s:2:\"as\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-22 18:59:07\";s:12:\"english_name\";s:8:\"Assamese\";s:11:\"native_name\";s:21:\"অসমীয়া\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/as.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"as\";i:2;s:3:\"asm\";i:3;s:3:\"asm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"az\";a:8:{s:8:\"language\";s:2:\"az\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-06 00:09:27\";s:12:\"english_name\";s:11:\"Azerbaijani\";s:11:\"native_name\";s:16:\"Azərbaycan dili\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/az.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:2;s:3:\"aze\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Davam\";}}s:3:\"azb\";a:8:{s:8:\"language\";s:3:\"azb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-12 20:34:31\";s:12:\"english_name\";s:17:\"South Azerbaijani\";s:11:\"native_name\";s:29:\"گؤنئی آذربایجان\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/azb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"az\";i:3;s:3:\"azb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:3:\"bel\";a:8:{s:8:\"language\";s:3:\"bel\";s:7:\"version\";s:6:\"4.9.13\";s:7:\"updated\";s:19:\"2019-10-29 07:54:22\";s:12:\"english_name\";s:10:\"Belarusian\";s:11:\"native_name\";s:29:\"Беларуская мова\";s:7:\"package\";s:63:\"https://downloads.wordpress.org/translation/core/4.9.13/bel.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"be\";i:2;s:3:\"bel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Працягнуць\";}}s:5:\"bg_BG\";a:8:{s:8:\"language\";s:5:\"bg_BG\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-22 10:57:09\";s:12:\"english_name\";s:9:\"Bulgarian\";s:11:\"native_name\";s:18:\"Български\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/bg_BG.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bg\";i:2;s:3:\"bul\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:22:\"Продължение\";}}s:5:\"bn_BD\";a:8:{s:8:\"language\";s:5:\"bn_BD\";s:7:\"version\";s:6:\"4.8.12\";s:7:\"updated\";s:19:\"2017-10-01 12:57:10\";s:12:\"english_name\";s:20:\"Bengali (Bangladesh)\";s:11:\"native_name\";s:15:\"বাংলা\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.8.12/bn_BD.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"bn\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:23:\"এগিয়ে চল.\";}}s:2:\"bo\";a:8:{s:8:\"language\";s:2:\"bo\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-23 02:24:08\";s:12:\"english_name\";s:7:\"Tibetan\";s:11:\"native_name\";s:21:\"བོད་ཡིག\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/bo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bo\";i:2;s:3:\"tib\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"མུ་མཐུད།\";}}s:5:\"bs_BA\";a:8:{s:8:\"language\";s:5:\"bs_BA\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-18 19:20:00\";s:12:\"english_name\";s:7:\"Bosnian\";s:11:\"native_name\";s:8:\"Bosanski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/bs_BA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"bs\";i:2;s:3:\"bos\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:2:\"ca\";a:8:{s:8:\"language\";s:2:\"ca\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-15 19:05:13\";s:12:\"english_name\";s:7:\"Catalan\";s:11:\"native_name\";s:7:\"Català\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/ca.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ca\";i:2;s:3:\"cat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:3:\"ceb\";a:8:{s:8:\"language\";s:3:\"ceb\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-02 17:25:51\";s:12:\"english_name\";s:7:\"Cebuano\";s:11:\"native_name\";s:7:\"Cebuano\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/ceb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"ceb\";i:3;s:3:\"ceb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Padayun\";}}s:5:\"cs_CZ\";a:8:{s:8:\"language\";s:5:\"cs_CZ\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-27 14:39:02\";s:12:\"english_name\";s:5:\"Czech\";s:11:\"native_name\";s:9:\"Čeština\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/cs_CZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cs\";i:2;s:3:\"ces\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:11:\"Pokračovat\";}}s:2:\"cy\";a:8:{s:8:\"language\";s:2:\"cy\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-10 11:38:15\";s:12:\"english_name\";s:5:\"Welsh\";s:11:\"native_name\";s:7:\"Cymraeg\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/cy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"cy\";i:2;s:3:\"cym\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Parhau\";}}s:5:\"da_DK\";a:8:{s:8:\"language\";s:5:\"da_DK\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-15 20:45:17\";s:12:\"english_name\";s:6:\"Danish\";s:11:\"native_name\";s:5:\"Dansk\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/da_DK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"da\";i:2;s:3:\"dan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Fortsæt\";}}s:5:\"de_AT\";a:8:{s:8:\"language\";s:5:\"de_AT\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-11-14 11:38:17\";s:12:\"english_name\";s:16:\"German (Austria)\";s:11:\"native_name\";s:21:\"Deutsch (Österreich)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/de_AT.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:14:\"de_CH_informal\";a:8:{s:8:\"language\";s:14:\"de_CH_informal\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-12 08:02:56\";s:12:\"english_name\";s:30:\"German (Switzerland, Informal)\";s:11:\"native_name\";s:21:\"Deutsch (Schweiz, Du)\";s:7:\"package\";s:73:\"https://downloads.wordpress.org/translation/core/5.3.2/de_CH_informal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Weiter\";}}s:5:\"de_CH\";a:8:{s:8:\"language\";s:5:\"de_CH\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-12 08:02:09\";s:12:\"english_name\";s:20:\"German (Switzerland)\";s:11:\"native_name\";s:17:\"Deutsch (Schweiz)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/de_CH.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Fortfahren\";}}s:12:\"de_DE_formal\";a:8:{s:8:\"language\";s:12:\"de_DE_formal\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-24 17:26:42\";s:12:\"english_name\";s:15:\"German (Formal)\";s:11:\"native_name\";s:13:\"Deutsch (Sie)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/5.3.2/de_DE_formal.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Fortfahren\";}}s:5:\"de_DE\";a:8:{s:8:\"language\";s:5:\"de_DE\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-24 17:29:56\";s:12:\"english_name\";s:6:\"German\";s:11:\"native_name\";s:7:\"Deutsch\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/de_DE.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"de\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Fortfahren\";}}s:3:\"dzo\";a:8:{s:8:\"language\";s:3:\"dzo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-06-29 08:59:03\";s:12:\"english_name\";s:8:\"Dzongkha\";s:11:\"native_name\";s:18:\"རྫོང་ཁ\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/dzo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"dz\";i:2;s:3:\"dzo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"el\";a:8:{s:8:\"language\";s:2:\"el\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-10 10:14:21\";s:12:\"english_name\";s:5:\"Greek\";s:11:\"native_name\";s:16:\"Ελληνικά\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/el.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"el\";i:2;s:3:\"ell\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Συνέχεια\";}}s:5:\"en_GB\";a:8:{s:8:\"language\";s:5:\"en_GB\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-11-28 17:31:58\";s:12:\"english_name\";s:12:\"English (UK)\";s:11:\"native_name\";s:12:\"English (UK)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/en_GB.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_ZA\";a:8:{s:8:\"language\";s:5:\"en_ZA\";s:7:\"version\";s:5:\"5.1.4\";s:7:\"updated\";s:19:\"2019-06-06 15:48:01\";s:12:\"english_name\";s:22:\"English (South Africa)\";s:11:\"native_name\";s:22:\"English (South Africa)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.1.4/en_ZA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_NZ\";a:8:{s:8:\"language\";s:5:\"en_NZ\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-11-28 21:29:53\";s:12:\"english_name\";s:21:\"English (New Zealand)\";s:11:\"native_name\";s:21:\"English (New Zealand)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/en_NZ.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_CA\";a:8:{s:8:\"language\";s:5:\"en_CA\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-11-28 17:04:17\";s:12:\"english_name\";s:16:\"English (Canada)\";s:11:\"native_name\";s:16:\"English (Canada)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/en_CA.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"en_AU\";a:8:{s:8:\"language\";s:5:\"en_AU\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-11-28 21:30:20\";s:12:\"english_name\";s:19:\"English (Australia)\";s:11:\"native_name\";s:19:\"English (Australia)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/en_AU.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"en\";i:2;s:3:\"eng\";i:3;s:3:\"eng\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"eo\";a:8:{s:8:\"language\";s:2:\"eo\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-16 16:42:18\";s:12:\"english_name\";s:9:\"Esperanto\";s:11:\"native_name\";s:9:\"Esperanto\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/eo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eo\";i:2;s:3:\"epo\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Daŭrigi\";}}s:5:\"es_VE\";a:8:{s:8:\"language\";s:5:\"es_VE\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-11 03:56:06\";s:12:\"english_name\";s:19:\"Spanish (Venezuela)\";s:11:\"native_name\";s:21:\"Español de Venezuela\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/es_VE.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CO\";a:8:{s:8:\"language\";s:5:\"es_CO\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-23 23:02:03\";s:12:\"english_name\";s:18:\"Spanish (Colombia)\";s:11:\"native_name\";s:20:\"Español de Colombia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/es_CO.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_UY\";a:8:{s:8:\"language\";s:5:\"es_UY\";s:7:\"version\";s:3:\"5.3\";s:7:\"updated\";s:19:\"2019-11-12 04:43:11\";s:12:\"english_name\";s:17:\"Spanish (Uruguay)\";s:11:\"native_name\";s:19:\"Español de Uruguay\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.3/es_UY.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CR\";a:8:{s:8:\"language\";s:5:\"es_CR\";s:7:\"version\";s:3:\"5.3\";s:7:\"updated\";s:19:\"2019-11-14 16:08:46\";s:12:\"english_name\";s:20:\"Spanish (Costa Rica)\";s:11:\"native_name\";s:22:\"Español de Costa Rica\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.3/es_CR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_CL\";a:8:{s:8:\"language\";s:5:\"es_CL\";s:7:\"version\";s:5:\"5.2.5\";s:7:\"updated\";s:19:\"2019-12-07 04:01:34\";s:12:\"english_name\";s:15:\"Spanish (Chile)\";s:11:\"native_name\";s:17:\"Español de Chile\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.2.5/es_CL.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_GT\";a:8:{s:8:\"language\";s:5:\"es_GT\";s:7:\"version\";s:3:\"5.1\";s:7:\"updated\";s:19:\"2019-03-02 06:35:01\";s:12:\"english_name\";s:19:\"Spanish (Guatemala)\";s:11:\"native_name\";s:21:\"Español de Guatemala\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.1/es_GT.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_PE\";a:8:{s:8:\"language\";s:5:\"es_PE\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-09 09:36:22\";s:12:\"english_name\";s:14:\"Spanish (Peru)\";s:11:\"native_name\";s:17:\"Español de Perú\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/es_PE.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_ES\";a:8:{s:8:\"language\";s:5:\"es_ES\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-09 12:35:27\";s:12:\"english_name\";s:15:\"Spanish (Spain)\";s:11:\"native_name\";s:8:\"Español\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/es_ES.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_MX\";a:8:{s:8:\"language\";s:5:\"es_MX\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-04 17:46:33\";s:12:\"english_name\";s:16:\"Spanish (Mexico)\";s:11:\"native_name\";s:19:\"Español de México\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/es_MX.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"es_AR\";a:8:{s:8:\"language\";s:5:\"es_AR\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-02-06 05:52:53\";s:12:\"english_name\";s:19:\"Spanish (Argentina)\";s:11:\"native_name\";s:21:\"Español de Argentina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/es_AR.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"es\";i:2;s:3:\"spa\";i:3;s:3:\"spa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"et\";a:8:{s:8:\"language\";s:2:\"et\";s:7:\"version\";s:9:\"5.0-beta3\";s:7:\"updated\";s:19:\"2018-11-28 16:04:33\";s:12:\"english_name\";s:8:\"Estonian\";s:11:\"native_name\";s:5:\"Eesti\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/5.0-beta3/et.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"et\";i:2;s:3:\"est\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Jätka\";}}s:2:\"eu\";a:8:{s:8:\"language\";s:2:\"eu\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-08 17:55:03\";s:12:\"english_name\";s:6:\"Basque\";s:11:\"native_name\";s:7:\"Euskara\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/eu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"eu\";i:2;s:3:\"eus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Jarraitu\";}}s:5:\"fa_IR\";a:8:{s:8:\"language\";s:5:\"fa_IR\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-15 23:45:20\";s:12:\"english_name\";s:7:\"Persian\";s:11:\"native_name\";s:10:\"فارسی\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/fa_IR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fa\";i:2;s:3:\"fas\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:2:\"fi\";a:8:{s:8:\"language\";s:2:\"fi\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-02 09:08:55\";s:12:\"english_name\";s:7:\"Finnish\";s:11:\"native_name\";s:5:\"Suomi\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/fi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fi\";i:2;s:3:\"fin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Jatka\";}}s:5:\"fr_FR\";a:8:{s:8:\"language\";s:5:\"fr_FR\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-02-07 15:53:24\";s:12:\"english_name\";s:15:\"French (France)\";s:11:\"native_name\";s:9:\"Français\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/fr_FR.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"fr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_CA\";a:8:{s:8:\"language\";s:5:\"fr_CA\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-02 12:30:18\";s:12:\"english_name\";s:15:\"French (Canada)\";s:11:\"native_name\";s:19:\"Français du Canada\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/fr_CA.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:5:\"fr_BE\";a:8:{s:8:\"language\";s:5:\"fr_BE\";s:7:\"version\";s:5:\"4.9.5\";s:7:\"updated\";s:19:\"2018-01-31 11:16:06\";s:12:\"english_name\";s:16:\"French (Belgium)\";s:11:\"native_name\";s:21:\"Français de Belgique\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.9.5/fr_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"fr\";i:2;s:3:\"fra\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:3:\"fur\";a:8:{s:8:\"language\";s:3:\"fur\";s:7:\"version\";s:5:\"4.8.6\";s:7:\"updated\";s:19:\"2018-01-29 17:32:35\";s:12:\"english_name\";s:8:\"Friulian\";s:11:\"native_name\";s:8:\"Friulian\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8.6/fur.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"fur\";i:3;s:3:\"fur\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:2:\"gd\";a:8:{s:8:\"language\";s:2:\"gd\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-08-23 17:41:37\";s:12:\"english_name\";s:15:\"Scottish Gaelic\";s:11:\"native_name\";s:9:\"Gàidhlig\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/gd.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"gd\";i:2;s:3:\"gla\";i:3;s:3:\"gla\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"Lean air adhart\";}}s:5:\"gl_ES\";a:8:{s:8:\"language\";s:5:\"gl_ES\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-01 17:58:42\";s:12:\"english_name\";s:8:\"Galician\";s:11:\"native_name\";s:6:\"Galego\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/gl_ES.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gl\";i:2;s:3:\"glg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:2:\"gu\";a:8:{s:8:\"language\";s:2:\"gu\";s:7:\"version\";s:5:\"4.9.8\";s:7:\"updated\";s:19:\"2018-09-14 12:33:48\";s:12:\"english_name\";s:8:\"Gujarati\";s:11:\"native_name\";s:21:\"ગુજરાતી\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.9.8/gu.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"gu\";i:2;s:3:\"guj\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:31:\"ચાલુ રાખવું\";}}s:3:\"haz\";a:8:{s:8:\"language\";s:3:\"haz\";s:7:\"version\";s:5:\"4.4.2\";s:7:\"updated\";s:19:\"2015-12-05 00:59:09\";s:12:\"english_name\";s:8:\"Hazaragi\";s:11:\"native_name\";s:15:\"هزاره گی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.4.2/haz.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"haz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"ادامه\";}}s:5:\"he_IL\";a:8:{s:8:\"language\";s:5:\"he_IL\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-20 16:09:08\";s:12:\"english_name\";s:6:\"Hebrew\";s:11:\"native_name\";s:16:\"עִבְרִית\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/he_IL.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"he\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"להמשיך\";}}s:5:\"hi_IN\";a:8:{s:8:\"language\";s:5:\"hi_IN\";s:7:\"version\";s:5:\"4.9.7\";s:7:\"updated\";s:19:\"2018-06-17 09:33:44\";s:12:\"english_name\";s:5:\"Hindi\";s:11:\"native_name\";s:18:\"हिन्दी\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.9.7/hi_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hi\";i:2;s:3:\"hin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"जारी\";}}s:2:\"hr\";a:8:{s:8:\"language\";s:2:\"hr\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-17 16:22:28\";s:12:\"english_name\";s:8:\"Croatian\";s:11:\"native_name\";s:8:\"Hrvatski\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/hr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hr\";i:2;s:3:\"hrv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nastavi\";}}s:3:\"hsb\";a:8:{s:8:\"language\";s:3:\"hsb\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-11-28 17:22:10\";s:12:\"english_name\";s:13:\"Upper Sorbian\";s:11:\"native_name\";s:17:\"Hornjoserbšćina\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.3.2/hsb.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"hsb\";i:3;s:3:\"hsb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:4:\"Dale\";}}s:5:\"hu_HU\";a:8:{s:8:\"language\";s:5:\"hu_HU\";s:7:\"version\";s:5:\"5.1.1\";s:7:\"updated\";s:19:\"2019-03-19 14:36:40\";s:12:\"english_name\";s:9:\"Hungarian\";s:11:\"native_name\";s:6:\"Magyar\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.1.1/hu_HU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hu\";i:2;s:3:\"hun\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Tovább\";}}s:2:\"hy\";a:8:{s:8:\"language\";s:2:\"hy\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-03 16:21:10\";s:12:\"english_name\";s:8:\"Armenian\";s:11:\"native_name\";s:14:\"Հայերեն\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/hy.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"hy\";i:2;s:3:\"hye\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Շարունակել\";}}s:5:\"id_ID\";a:8:{s:8:\"language\";s:5:\"id_ID\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-04 22:54:51\";s:12:\"english_name\";s:10:\"Indonesian\";s:11:\"native_name\";s:16:\"Bahasa Indonesia\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/id_ID.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"id\";i:2;s:3:\"ind\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Lanjutkan\";}}s:5:\"is_IS\";a:8:{s:8:\"language\";s:5:\"is_IS\";s:7:\"version\";s:6:\"4.7.11\";s:7:\"updated\";s:19:\"2018-09-20 11:13:37\";s:12:\"english_name\";s:9:\"Icelandic\";s:11:\"native_name\";s:9:\"Íslenska\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.7.11/is_IS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"is\";i:2;s:3:\"isl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Áfram\";}}s:5:\"it_IT\";a:8:{s:8:\"language\";s:5:\"it_IT\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-20 17:02:39\";s:12:\"english_name\";s:7:\"Italian\";s:11:\"native_name\";s:8:\"Italiano\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/it_IT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"it\";i:2;s:3:\"ita\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continua\";}}s:2:\"ja\";a:8:{s:8:\"language\";s:2:\"ja\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-02 04:22:13\";s:12:\"english_name\";s:8:\"Japanese\";s:11:\"native_name\";s:9:\"日本語\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/ja.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"ja\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"続ける\";}}s:5:\"jv_ID\";a:8:{s:8:\"language\";s:5:\"jv_ID\";s:7:\"version\";s:5:\"4.9.5\";s:7:\"updated\";s:19:\"2018-03-24 13:53:29\";s:12:\"english_name\";s:8:\"Javanese\";s:11:\"native_name\";s:9:\"Basa Jawa\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.9.5/jv_ID.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"jv\";i:2;s:3:\"jav\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Nutugne\";}}s:5:\"ka_GE\";a:8:{s:8:\"language\";s:5:\"ka_GE\";s:7:\"version\";s:5:\"5.1.4\";s:7:\"updated\";s:19:\"2019-11-04 08:57:25\";s:12:\"english_name\";s:8:\"Georgian\";s:11:\"native_name\";s:21:\"ქართული\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.1.4/ka_GE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ka\";i:2;s:3:\"kat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"გაგრძელება\";}}s:3:\"kab\";a:8:{s:8:\"language\";s:3:\"kab\";s:7:\"version\";s:5:\"4.9.8\";s:7:\"updated\";s:19:\"2018-09-21 14:15:57\";s:12:\"english_name\";s:6:\"Kabyle\";s:11:\"native_name\";s:9:\"Taqbaylit\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.8/kab.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"kab\";i:3;s:3:\"kab\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuer\";}}s:2:\"kk\";a:8:{s:8:\"language\";s:2:\"kk\";s:7:\"version\";s:5:\"4.9.5\";s:7:\"updated\";s:19:\"2018-03-12 08:08:32\";s:12:\"english_name\";s:6:\"Kazakh\";s:11:\"native_name\";s:19:\"Қазақ тілі\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.9.5/kk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"kk\";i:2;s:3:\"kaz\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Жалғастыру\";}}s:2:\"km\";a:8:{s:8:\"language\";s:2:\"km\";s:7:\"version\";s:5:\"5.0.3\";s:7:\"updated\";s:19:\"2019-01-09 07:34:10\";s:12:\"english_name\";s:5:\"Khmer\";s:11:\"native_name\";s:27:\"ភាសាខ្មែរ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.0.3/km.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"km\";i:2;s:3:\"khm\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"បន្ត\";}}s:2:\"kn\";a:8:{s:8:\"language\";s:2:\"kn\";s:7:\"version\";s:6:\"4.9.13\";s:7:\"updated\";s:19:\"2019-12-04 12:22:34\";s:12:\"english_name\";s:7:\"Kannada\";s:11:\"native_name\";s:15:\"ಕನ್ನಡ\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.13/kn.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"kn\";i:2;s:3:\"kan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"ಮುಂದುವರೆಸಿ\";}}s:5:\"ko_KR\";a:8:{s:8:\"language\";s:5:\"ko_KR\";s:7:\"version\";s:5:\"5.2.5\";s:7:\"updated\";s:19:\"2019-11-05 01:54:57\";s:12:\"english_name\";s:6:\"Korean\";s:11:\"native_name\";s:9:\"한국어\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.2.5/ko_KR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ko\";i:2;s:3:\"kor\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"계속\";}}s:3:\"ckb\";a:8:{s:8:\"language\";s:3:\"ckb\";s:7:\"version\";s:5:\"4.9.9\";s:7:\"updated\";s:19:\"2018-12-18 14:32:44\";s:12:\"english_name\";s:16:\"Kurdish (Sorani)\";s:11:\"native_name\";s:13:\"كوردی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.9.9/ckb.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ku\";i:3;s:3:\"ckb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"بهردهوام به\";}}s:2:\"lo\";a:8:{s:8:\"language\";s:2:\"lo\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 09:59:23\";s:12:\"english_name\";s:3:\"Lao\";s:11:\"native_name\";s:21:\"ພາສາລາວ\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/lo.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lo\";i:2;s:3:\"lao\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"ຕໍ່\";}}s:5:\"lt_LT\";a:8:{s:8:\"language\";s:5:\"lt_LT\";s:7:\"version\";s:5:\"5.2.5\";s:7:\"updated\";s:19:\"2019-10-19 19:23:46\";s:12:\"english_name\";s:10:\"Lithuanian\";s:11:\"native_name\";s:15:\"Lietuvių kalba\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.2.5/lt_LT.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lt\";i:2;s:3:\"lit\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Tęsti\";}}s:2:\"lv\";a:8:{s:8:\"language\";s:2:\"lv\";s:7:\"version\";s:6:\"4.7.15\";s:7:\"updated\";s:19:\"2019-05-10 10:24:08\";s:12:\"english_name\";s:7:\"Latvian\";s:11:\"native_name\";s:16:\"Latviešu valoda\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.15/lv.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"lv\";i:2;s:3:\"lav\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Turpināt\";}}s:5:\"mk_MK\";a:8:{s:8:\"language\";s:5:\"mk_MK\";s:7:\"version\";s:5:\"5.2.3\";s:7:\"updated\";s:19:\"2019-09-08 12:57:25\";s:12:\"english_name\";s:10:\"Macedonian\";s:11:\"native_name\";s:31:\"Македонски јазик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.2.3/mk_MK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mk\";i:2;s:3:\"mkd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:16:\"Продолжи\";}}s:5:\"ml_IN\";a:8:{s:8:\"language\";s:5:\"ml_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:43:32\";s:12:\"english_name\";s:9:\"Malayalam\";s:11:\"native_name\";s:18:\"മലയാളം\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ml_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ml\";i:2;s:3:\"mal\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:18:\"തുടരുക\";}}s:2:\"mn\";a:8:{s:8:\"language\";s:2:\"mn\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-12 07:29:35\";s:12:\"english_name\";s:9:\"Mongolian\";s:11:\"native_name\";s:12:\"Монгол\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/mn.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mn\";i:2;s:3:\"mon\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"Үргэлжлүүлэх\";}}s:2:\"mr\";a:8:{s:8:\"language\";s:2:\"mr\";s:7:\"version\";s:6:\"4.8.11\";s:7:\"updated\";s:19:\"2018-02-13 07:38:55\";s:12:\"english_name\";s:7:\"Marathi\";s:11:\"native_name\";s:15:\"मराठी\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8.11/mr.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"mr\";i:2;s:3:\"mar\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"सुरु ठेवा\";}}s:5:\"ms_MY\";a:8:{s:8:\"language\";s:5:\"ms_MY\";s:7:\"version\";s:5:\"4.9.8\";s:7:\"updated\";s:19:\"2018-08-30 20:27:25\";s:12:\"english_name\";s:5:\"Malay\";s:11:\"native_name\";s:13:\"Bahasa Melayu\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.9.8/ms_MY.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ms\";i:2;s:3:\"msa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Teruskan\";}}s:5:\"my_MM\";a:8:{s:8:\"language\";s:5:\"my_MM\";s:7:\"version\";s:6:\"4.1.20\";s:7:\"updated\";s:19:\"2015-03-26 15:57:42\";s:12:\"english_name\";s:17:\"Myanmar (Burmese)\";s:11:\"native_name\";s:15:\"ဗမာစာ\";s:7:\"package\";s:65:\"https://downloads.wordpress.org/translation/core/4.1.20/my_MM.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"my\";i:2;s:3:\"mya\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:54:\"ဆက်လက်လုပ်ေဆာင်ပါ။\";}}s:5:\"nb_NO\";a:8:{s:8:\"language\";s:5:\"nb_NO\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-19 02:18:44\";s:12:\"english_name\";s:19:\"Norwegian (Bokmål)\";s:11:\"native_name\";s:13:\"Norsk bokmål\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/nb_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nb\";i:2;s:3:\"nob\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Fortsett\";}}s:5:\"ne_NP\";a:8:{s:8:\"language\";s:5:\"ne_NP\";s:7:\"version\";s:5:\"4.9.5\";s:7:\"updated\";s:19:\"2018-03-27 10:30:26\";s:12:\"english_name\";s:6:\"Nepali\";s:11:\"native_name\";s:18:\"नेपाली\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.9.5/ne_NP.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ne\";i:2;s:3:\"nep\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:31:\"जारीराख्नु \";}}s:5:\"nl_BE\";a:8:{s:8:\"language\";s:5:\"nl_BE\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-17 19:42:41\";s:12:\"english_name\";s:15:\"Dutch (Belgium)\";s:11:\"native_name\";s:20:\"Nederlands (België)\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/nl_BE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:12:\"nl_NL_formal\";a:8:{s:8:\"language\";s:12:\"nl_NL_formal\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-15 20:22:22\";s:12:\"english_name\";s:14:\"Dutch (Formal)\";s:11:\"native_name\";s:20:\"Nederlands (Formeel)\";s:7:\"package\";s:71:\"https://downloads.wordpress.org/translation/core/5.3.2/nl_NL_formal.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nl_NL\";a:8:{s:8:\"language\";s:5:\"nl_NL\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-12 09:57:15\";s:12:\"english_name\";s:5:\"Dutch\";s:11:\"native_name\";s:10:\"Nederlands\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/nl_NL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nl\";i:2;s:3:\"nld\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Doorgaan\";}}s:5:\"nn_NO\";a:8:{s:8:\"language\";s:5:\"nn_NO\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-01 08:53:00\";s:12:\"english_name\";s:19:\"Norwegian (Nynorsk)\";s:11:\"native_name\";s:13:\"Norsk nynorsk\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/nn_NO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"nn\";i:2;s:3:\"nno\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Hald fram\";}}s:3:\"oci\";a:8:{s:8:\"language\";s:3:\"oci\";s:7:\"version\";s:5:\"4.8.3\";s:7:\"updated\";s:19:\"2017-08-25 10:03:08\";s:12:\"english_name\";s:7:\"Occitan\";s:11:\"native_name\";s:7:\"Occitan\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.8.3/oci.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"oc\";i:2;s:3:\"oci\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Contunhar\";}}s:5:\"pa_IN\";a:8:{s:8:\"language\";s:5:\"pa_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-16 05:19:43\";s:12:\"english_name\";s:7:\"Punjabi\";s:11:\"native_name\";s:18:\"ਪੰਜਾਬੀ\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/pa_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pa\";i:2;s:3:\"pan\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:25:\"ਜਾਰੀ ਰੱਖੋ\";}}s:5:\"pl_PL\";a:8:{s:8:\"language\";s:5:\"pl_PL\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-22 13:20:49\";s:12:\"english_name\";s:6:\"Polish\";s:11:\"native_name\";s:6:\"Polski\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/pl_PL.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pl\";i:2;s:3:\"pol\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Kontynuuj\";}}s:2:\"ps\";a:8:{s:8:\"language\";s:2:\"ps\";s:7:\"version\";s:6:\"4.1.20\";s:7:\"updated\";s:19:\"2015-03-29 22:19:48\";s:12:\"english_name\";s:6:\"Pashto\";s:11:\"native_name\";s:8:\"پښتو\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.1.20/ps.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ps\";i:2;s:3:\"pus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"دوام\";}}s:5:\"pt_PT\";a:8:{s:8:\"language\";s:5:\"pt_PT\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-22 00:32:52\";s:12:\"english_name\";s:21:\"Portuguese (Portugal)\";s:11:\"native_name\";s:10:\"Português\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/pt_PT.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"pt_AO\";a:8:{s:8:\"language\";s:5:\"pt_AO\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-14 08:20:00\";s:12:\"english_name\";s:19:\"Portuguese (Angola)\";s:11:\"native_name\";s:20:\"Português de Angola\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/pt_AO.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:10:\"pt_PT_ao90\";a:8:{s:8:\"language\";s:10:\"pt_PT_ao90\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-08 13:01:50\";s:12:\"english_name\";s:27:\"Portuguese (Portugal, AO90)\";s:11:\"native_name\";s:17:\"Português (AO90)\";s:7:\"package\";s:69:\"https://downloads.wordpress.org/translation/core/5.3.2/pt_PT_ao90.zip\";s:3:\"iso\";a:1:{i:1;s:2:\"pt\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:5:\"pt_BR\";a:8:{s:8:\"language\";s:5:\"pt_BR\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-02-04 11:20:43\";s:12:\"english_name\";s:19:\"Portuguese (Brazil)\";s:11:\"native_name\";s:20:\"Português do Brasil\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/pt_BR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"pt\";i:2;s:3:\"por\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuar\";}}s:3:\"rhg\";a:8:{s:8:\"language\";s:3:\"rhg\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-16 13:03:18\";s:12:\"english_name\";s:8:\"Rohingya\";s:11:\"native_name\";s:8:\"Ruáinga\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/rhg.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"rhg\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"ro_RO\";a:8:{s:8:\"language\";s:5:\"ro_RO\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-02-04 16:57:22\";s:12:\"english_name\";s:8:\"Romanian\";s:11:\"native_name\";s:8:\"Română\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/ro_RO.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ro\";i:2;s:3:\"ron\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Continuă\";}}s:5:\"ru_RU\";a:8:{s:8:\"language\";s:5:\"ru_RU\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-17 16:11:46\";s:12:\"english_name\";s:7:\"Russian\";s:11:\"native_name\";s:14:\"Русский\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/ru_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ru\";i:2;s:3:\"rus\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продолжить\";}}s:3:\"sah\";a:8:{s:8:\"language\";s:3:\"sah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-21 02:06:41\";s:12:\"english_name\";s:5:\"Sakha\";s:11:\"native_name\";s:14:\"Сахалыы\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/sah.zip\";s:3:\"iso\";a:2:{i:2;s:3:\"sah\";i:3;s:3:\"sah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Салҕаа\";}}s:3:\"snd\";a:8:{s:8:\"language\";s:3:\"snd\";s:7:\"version\";s:3:\"5.3\";s:7:\"updated\";s:19:\"2019-11-12 04:37:38\";s:12:\"english_name\";s:6:\"Sindhi\";s:11:\"native_name\";s:8:\"سنڌي\";s:7:\"package\";s:60:\"https://downloads.wordpress.org/translation/core/5.3/snd.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"sd\";i:2;s:2:\"sd\";i:3;s:3:\"snd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"اڳتي هلو\";}}s:5:\"si_LK\";a:8:{s:8:\"language\";s:5:\"si_LK\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-12 06:00:52\";s:12:\"english_name\";s:7:\"Sinhala\";s:11:\"native_name\";s:15:\"සිංහල\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/si_LK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"si\";i:2;s:3:\"sin\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:44:\"දිගටම කරගෙන යන්න\";}}s:5:\"sk_SK\";a:8:{s:8:\"language\";s:5:\"sk_SK\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-02 07:46:23\";s:12:\"english_name\";s:6:\"Slovak\";s:11:\"native_name\";s:11:\"Slovenčina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/sk_SK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sk\";i:2;s:3:\"slk\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Pokračovať\";}}s:3:\"skr\";a:8:{s:8:\"language\";s:3:\"skr\";s:7:\"version\";s:5:\"5.2.3\";s:7:\"updated\";s:19:\"2019-06-26 11:40:37\";s:12:\"english_name\";s:7:\"Saraiki\";s:11:\"native_name\";s:14:\"سرائیکی\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/5.2.3/skr.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"skr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:17:\"جاری رکھو\";}}s:5:\"sl_SI\";a:8:{s:8:\"language\";s:5:\"sl_SI\";s:7:\"version\";s:5:\"4.9.2\";s:7:\"updated\";s:19:\"2018-01-04 13:33:13\";s:12:\"english_name\";s:9:\"Slovenian\";s:11:\"native_name\";s:13:\"Slovenščina\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.9.2/sl_SI.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sl\";i:2;s:3:\"slv\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Nadaljujte\";}}s:2:\"sq\";a:8:{s:8:\"language\";s:2:\"sq\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-14 22:44:44\";s:12:\"english_name\";s:8:\"Albanian\";s:11:\"native_name\";s:5:\"Shqip\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/sq.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sq\";i:2;s:3:\"sqi\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"Vazhdo\";}}s:5:\"sr_RS\";a:8:{s:8:\"language\";s:5:\"sr_RS\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-15 22:50:02\";s:12:\"english_name\";s:7:\"Serbian\";s:11:\"native_name\";s:23:\"Српски језик\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/sr_RS.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sr\";i:2;s:3:\"srp\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:14:\"Настави\";}}s:5:\"sv_SE\";a:8:{s:8:\"language\";s:5:\"sv_SE\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-12 07:05:13\";s:12:\"english_name\";s:7:\"Swedish\";s:11:\"native_name\";s:7:\"Svenska\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/sv_SE.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sv\";i:2;s:3:\"swe\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:9:\"Fortsätt\";}}s:2:\"sw\";a:8:{s:8:\"language\";s:2:\"sw\";s:7:\"version\";s:5:\"5.2.5\";s:7:\"updated\";s:19:\"2019-10-22 00:19:41\";s:12:\"english_name\";s:7:\"Swahili\";s:11:\"native_name\";s:9:\"Kiswahili\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.2.5/sw.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"sw\";i:2;s:3:\"swa\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:7:\"Endelea\";}}s:3:\"szl\";a:8:{s:8:\"language\";s:3:\"szl\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-09-24 19:58:14\";s:12:\"english_name\";s:8:\"Silesian\";s:11:\"native_name\";s:17:\"Ślōnskŏ gŏdka\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/szl.zip\";s:3:\"iso\";a:1:{i:3;s:3:\"szl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:13:\"Kōntynuować\";}}s:5:\"ta_IN\";a:8:{s:8:\"language\";s:5:\"ta_IN\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-27 03:22:47\";s:12:\"english_name\";s:5:\"Tamil\";s:11:\"native_name\";s:15:\"தமிழ்\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/ta_IN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ta\";i:2;s:3:\"tam\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:24:\"தொடரவும்\";}}s:2:\"te\";a:8:{s:8:\"language\";s:2:\"te\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2017-01-26 15:47:39\";s:12:\"english_name\";s:6:\"Telugu\";s:11:\"native_name\";s:18:\"తెలుగు\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/te.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"te\";i:2;s:3:\"tel\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:30:\"కొనసాగించు\";}}s:2:\"th\";a:8:{s:8:\"language\";s:2:\"th\";s:7:\"version\";s:5:\"5.2.4\";s:7:\"updated\";s:19:\"2019-10-19 08:19:37\";s:12:\"english_name\";s:4:\"Thai\";s:11:\"native_name\";s:9:\"ไทย\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.2.4/th.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"th\";i:2;s:3:\"tha\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:15:\"ต่อไป\";}}s:2:\"tl\";a:8:{s:8:\"language\";s:2:\"tl\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-12-30 02:38:08\";s:12:\"english_name\";s:7:\"Tagalog\";s:11:\"native_name\";s:7:\"Tagalog\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/4.7.2/tl.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tl\";i:2;s:3:\"tgl\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:10:\"Magpatuloy\";}}s:5:\"tr_TR\";a:8:{s:8:\"language\";s:5:\"tr_TR\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-18 12:53:53\";s:12:\"english_name\";s:7:\"Turkish\";s:11:\"native_name\";s:8:\"Türkçe\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/tr_TR.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tr\";i:2;s:3:\"tur\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:5:\"Devam\";}}s:5:\"tt_RU\";a:8:{s:8:\"language\";s:5:\"tt_RU\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-11-20 20:20:50\";s:12:\"english_name\";s:5:\"Tatar\";s:11:\"native_name\";s:19:\"Татар теле\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.7.2/tt_RU.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"tt\";i:2;s:3:\"tat\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:17:\"дәвам итү\";}}s:3:\"tah\";a:8:{s:8:\"language\";s:3:\"tah\";s:7:\"version\";s:5:\"4.7.2\";s:7:\"updated\";s:19:\"2016-03-06 18:39:39\";s:12:\"english_name\";s:8:\"Tahitian\";s:11:\"native_name\";s:10:\"Reo Tahiti\";s:7:\"package\";s:62:\"https://downloads.wordpress.org/translation/core/4.7.2/tah.zip\";s:3:\"iso\";a:3:{i:1;s:2:\"ty\";i:2;s:3:\"tah\";i:3;s:3:\"tah\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:8:\"Continue\";}}s:5:\"ug_CN\";a:8:{s:8:\"language\";s:5:\"ug_CN\";s:7:\"version\";s:5:\"4.9.5\";s:7:\"updated\";s:19:\"2018-04-12 12:31:53\";s:12:\"english_name\";s:6:\"Uighur\";s:11:\"native_name\";s:16:\"ئۇيغۇرچە\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/4.9.5/ug_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ug\";i:2;s:3:\"uig\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:26:\"داۋاملاشتۇرۇش\";}}s:2:\"uk\";a:8:{s:8:\"language\";s:2:\"uk\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-02-03 23:36:03\";s:12:\"english_name\";s:9:\"Ukrainian\";s:11:\"native_name\";s:20:\"Українська\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/uk.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uk\";i:2;s:3:\"ukr\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продовжити\";}}s:2:\"ur\";a:8:{s:8:\"language\";s:2:\"ur\";s:7:\"version\";s:5:\"5.1.4\";s:7:\"updated\";s:19:\"2019-03-31 10:39:40\";s:12:\"english_name\";s:4:\"Urdu\";s:11:\"native_name\";s:8:\"اردو\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.1.4/ur.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"ur\";i:2;s:3:\"urd\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:19:\"جاری رکھیں\";}}s:5:\"uz_UZ\";a:8:{s:8:\"language\";s:5:\"uz_UZ\";s:7:\"version\";s:5:\"5.0.3\";s:7:\"updated\";s:19:\"2019-01-23 12:32:40\";s:12:\"english_name\";s:5:\"Uzbek\";s:11:\"native_name\";s:11:\"O‘zbekcha\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.0.3/uz_UZ.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"uz\";i:2;s:3:\"uzb\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:20:\"Продолжить\";}}s:2:\"vi\";a:8:{s:8:\"language\";s:2:\"vi\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-07 15:52:24\";s:12:\"english_name\";s:10:\"Vietnamese\";s:11:\"native_name\";s:14:\"Tiếng Việt\";s:7:\"package\";s:61:\"https://downloads.wordpress.org/translation/core/5.3.2/vi.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"vi\";i:2;s:3:\"vie\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:12:\"Tiếp tục\";}}s:5:\"zh_CN\";a:8:{s:8:\"language\";s:5:\"zh_CN\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-08 21:26:25\";s:12:\"english_name\";s:15:\"Chinese (China)\";s:11:\"native_name\";s:12:\"简体中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/zh_CN.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"继续\";}}s:5:\"zh_TW\";a:8:{s:8:\"language\";s:5:\"zh_TW\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2020-01-16 03:03:10\";s:12:\"english_name\";s:16:\"Chinese (Taiwan)\";s:11:\"native_name\";s:12:\"繁體中文\";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/zh_TW.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}s:5:\"zh_HK\";a:8:{s:8:\"language\";s:5:\"zh_HK\";s:7:\"version\";s:5:\"5.3.2\";s:7:\"updated\";s:19:\"2019-12-29 17:33:44\";s:12:\"english_name\";s:19:\"Chinese (Hong Kong)\";s:11:\"native_name\";s:16:\"香港中文版 \";s:7:\"package\";s:64:\"https://downloads.wordpress.org/translation/core/5.3.2/zh_HK.zip\";s:3:\"iso\";a:2:{i:1;s:2:\"zh\";i:2;s:3:\"zho\";}s:7:\"strings\";a:1:{s:8:\"continue\";s:6:\"繼續\";}}}','no'),(156,'WPLANG','','yes'),(157,'new_admin_email','<EMAIL>','yes'),(162,'_transient_is_multi_author','0','yes');
/*!40000 ALTER TABLE `wp_options` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_postmeta`
--
DROP TABLE IF EXISTS `wp_postmeta`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_postmeta` (
`meta_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`post_id` bigint unsigned NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (`meta_id`),
KEY `post_id` (`post_id`),
KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB AUTO_INCREMENT=19 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_postmeta`
--
LOCK TABLES `wp_postmeta` WRITE;
/*!40000 ALTER TABLE `wp_postmeta` DISABLE KEYS */;
INSERT INTO `wp_postmeta` VALUES (1,2,'_wp_page_template','default'),(2,3,'_wp_page_template','default'),(3,5,'_wp_attached_file','2020/02/2020-landscape-1.png'),(4,5,'_wp_attachment_metadata','a:5:{s:5:\"width\";i:1200;s:6:\"height\";i:769;s:4:\"file\";s:28:\"2020/02/2020-landscape-1.png\";s:5:\"sizes\";a:4:{s:6:\"medium\";a:4:{s:4:\"file\";s:28:\"2020-landscape-1-300x192.png\";s:5:\"width\";i:300;s:6:\"height\";i:192;s:9:\"mime-type\";s:9:\"image/png\";}s:5:\"large\";a:4:{s:4:\"file\";s:29:\"2020-landscape-1-1024x656.png\";s:5:\"width\";i:1024;s:6:\"height\";i:656;s:9:\"mime-type\";s:9:\"image/png\";}s:9:\"thumbnail\";a:4:{s:4:\"file\";s:28:\"2020-landscape-1-150x150.png\";s:5:\"width\";i:150;s:6:\"height\";i:150;s:9:\"mime-type\";s:9:\"image/png\";}s:12:\"medium_large\";a:4:{s:4:\"file\";s:28:\"2020-landscape-1-768x492.png\";s:5:\"width\";i:768;s:6:\"height\";i:492;s:9:\"mime-type\";s:9:\"image/png\";}}s:10:\"image_meta\";a:12:{s:8:\"aperture\";s:1:\"0\";s:6:\"credit\";s:0:\"\";s:6:\"camera\";s:0:\"\";s:7:\"caption\";s:0:\"\";s:17:\"created_timestamp\";s:1:\"0\";s:9:\"copyright\";s:0:\"\";s:12:\"focal_length\";s:1:\"0\";s:3:\"iso\";s:1:\"0\";s:13:\"shutter_speed\";s:1:\"0\";s:5:\"title\";s:0:\"\";s:11:\"orientation\";s:1:\"0\";s:8:\"keywords\";a:0:{}}}'),(5,5,'_starter_content_theme','twentytwenty'),(6,5,'_customize_draft_post_name','the-new-umoma-opens-its-doors'),(7,6,'_thumbnail_id','5'),(8,6,'_customize_draft_post_name','the-new-umoma-opens-its-doors'),(9,6,'_customize_changeset_uuid','bcb8ddd5-4ded-4b26-b470-f7f2dc75171d'),(10,7,'_customize_draft_post_name','about'),(11,7,'_customize_changeset_uuid','bcb8ddd5-4ded-4b26-b470-f7f2dc75171d'),(12,8,'_customize_draft_post_name','contact'),(13,8,'_customize_changeset_uuid','bcb8ddd5-4ded-4b26-b470-f7f2dc75171d'),(14,9,'_customize_draft_post_name','blog'),(15,9,'_customize_changeset_uuid','bcb8ddd5-4ded-4b26-b470-f7f2dc75171d'),(16,10,'_customize_restore_dismissed','1'),(17,11,'_edit_lock','1581185970:1'),(18,11,'_customize_restore_dismissed','1');
/*!40000 ALTER TABLE `wp_postmeta` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_posts`
--
DROP TABLE IF EXISTS `wp_posts`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_posts` (
`ID` bigint unsigned NOT NULL AUTO_INCREMENT,
`post_author` bigint unsigned NOT NULL DEFAULT '0',
`post_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_date_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_content` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_title` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_excerpt` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'publish',
`comment_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open',
`ping_status` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'open',
`post_password` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`post_name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`to_ping` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`pinged` text COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_modified_gmt` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`post_content_filtered` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`post_parent` bigint unsigned NOT NULL DEFAULT '0',
`guid` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`menu_order` int NOT NULL DEFAULT '0',
`post_type` varchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT 'post',
`post_mime_type` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`comment_count` bigint NOT NULL DEFAULT '0',
PRIMARY KEY (`ID`),
KEY `post_name` (`post_name`(191)),
KEY `type_status_date` (`post_type`,`post_status`,`post_date`,`ID`),
KEY `post_parent` (`post_parent`),
KEY `post_author` (`post_author`)
) ENGINE=InnoDB AUTO_INCREMENT=12 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_posts`
--
LOCK TABLES `wp_posts` WRITE;
/*!40000 ALTER TABLE `wp_posts` DISABLE KEYS */;
INSERT INTO `wp_posts` VALUES (1,1,'2020-02-08 17:46:49','2020-02-08 17:46:49','<!-- wp:paragraph -->\n<p>Welcome to WordPress. This is your first post. Edit or delete it, then start writing!</p>\n<!-- /wp:paragraph -->','Hello world!','','publish','open','open','','hello-world','','','2020-02-08 17:46:49','2020-02-08 17:46:49','',0,'http://localhost/?p=1',0,'post','',1),(2,1,'2020-02-08 17:46:49','2020-02-08 17:46:49','<!-- wp:paragraph -->\n<p>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:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>Hi there! I\'m a bike messenger by day, aspiring actor by night, and this is my website. I live in Los Angeles, have a great dog named Jack, and I like piña coladas. (And gettin\' caught in the rain.)</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>...or something like this:</p>\n<!-- /wp:paragraph -->\n\n<!-- wp:quote -->\n<blockquote class=\"wp-block-quote\"><p>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.</p></blockquote>\n<!-- /wp:quote -->\n\n<!-- wp:paragraph -->\n<p>As a new WordPress user, you should go to <a href=\"http://localhost/wp-admin/\">your dashboard</a> to delete this page and create new pages for your content. Have fun!</p>\n<!-- /wp:paragraph -->','Sample Page','','publish','closed','open','','sample-page','','','2020-02-08 17:46:49','2020-02-08 17:46:49','',0,'http://localhost/?page_id=2',0,'page','',0),(3,1,'2020-02-08 17:46:49','2020-02-08 17:46:49','<!-- wp:heading --><h2>Who we are</h2><!-- /wp:heading --><!-- wp:paragraph --><p>Our website address is: http://localhost.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>What personal data we collect and why we collect it</h2><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Comments</h3><!-- /wp:heading --><!-- wp:paragraph --><p>When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Media</h3><!-- /wp:heading --><!-- wp:paragraph --><p>If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Contact forms</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Cookies</h3><!-- /wp:heading --><!-- wp:paragraph --><p>If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Embedded content from other websites</h3><!-- /wp:heading --><!-- wp:paragraph --><p>Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.</p><!-- /wp:paragraph --><!-- wp:heading {\"level\":3} --><h3>Analytics</h3><!-- /wp:heading --><!-- wp:heading --><h2>Who we share your data with</h2><!-- /wp:heading --><!-- wp:heading --><h2>How long we retain your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>What rights you have over your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Where we send your data</h2><!-- /wp:heading --><!-- wp:paragraph --><p>Visitor comments may be checked through an automated spam detection service.</p><!-- /wp:paragraph --><!-- wp:heading --><h2>Your contact information</h2><!-- /wp:heading --><!-- wp:heading --><h2>Additional information</h2><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>How we protect your data</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What data breach procedures we have in place</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What third parties we receive data from</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>What automated decision making and/or profiling we do with user data</h3><!-- /wp:heading --><!-- wp:heading {\"level\":3} --><h3>Industry regulatory disclosure requirements</h3><!-- /wp:heading -->','Privacy Policy','','draft','closed','open','','privacy-policy','','','2020-02-08 17:46:49','2020-02-08 17:46:49','',0,'http://localhost/?page_id=3',0,'page','',0),(4,1,'2020-02-08 18:06:33','0000-00-00 00:00:00','','Auto Draft','','auto-draft','open','open','','','','','2020-02-08 18:06:33','0000-00-00 00:00:00','',0,'http://localhost/?p=4',0,'post','',0),(5,1,'2020-02-08 18:08:09','0000-00-00 00:00:00','','The New UMoMA Opens its Doors','','auto-draft','open','closed','','','','','2020-02-08 18:08:08','0000-00-00 00:00:00','',0,'http://localhost/wp-content/uploads/2020/02/2020-landscape-1.png',0,'attachment','image/png',0),(6,1,'2020-02-08 18:08:09','0000-00-00 00:00:00','<!-- wp:group {\"align\":\"wide\"} --><div class=\"wp-block-group alignwide\"><div class=\"wp-block-group__inner-container\"><!-- wp:heading {\"align\":\"center\"} --><h2 class=\"has-text-align-center\">The premier destination for modern art in Northern Sweden. Open from 10 AM to 6 PM every day during the summer months.</h2><!-- /wp:heading --></div></div><!-- /wp:group --><!-- wp:columns {\"align\":\"wide\"} --><div class=\"wp-block-columns alignwide\"><!-- wp:column --><div class=\"wp-block-column\"><!-- wp:group --><div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container\"><!-- wp:image {\"align\":\"full\",\"id\":37,\"sizeSlug\":\"full\"} --><figure class=\"wp-block-image alignfull size-full\"><img src=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-1.png\" alt=\"\" class=\"wp-image-37\"/></figure><!-- /wp:image --><!-- wp:heading {\"level\":3} --><h3>Works and Days</h3><!-- /wp:heading --><!-- wp:paragraph --><p>August 1 -- December 1</p><!-- /wp:paragraph --><!-- wp:button {\"className\":\"is-style-outline\"} --><div class=\"wp-block-button is-style-outline\"><a class=\"wp-block-button__link\" href=\"https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/\">Read More</a></div><!-- /wp:button --></div></div><!-- /wp:group --><!-- wp:group --><div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container\"><!-- wp:image {\"align\":\"full\",\"id\":37,\"sizeSlug\":\"full\"} --><figure class=\"wp-block-image alignfull size-full\"><img src=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-3.png\" alt=\"\" class=\"wp-image-37\"/></figure><!-- /wp:image --><!-- wp:heading {\"level\":3} --><h3>Theatre of Operations</h3><!-- /wp:heading --><!-- wp:paragraph --><p>October 1 -- December 1</p><!-- /wp:paragraph --><!-- wp:button {\"className\":\"is-style-outline\"} --><div class=\"wp-block-button is-style-outline\"><a class=\"wp-block-button__link\" href=\"https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/\">Read More</a></div><!-- /wp:button --></div></div><!-- /wp:group --></div><!-- /wp:column --><!-- wp:column --><div class=\"wp-block-column\"><!-- wp:group --><div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container\"><!-- wp:image {\"align\":\"full\",\"id\":37,\"sizeSlug\":\"full\"} --><figure class=\"wp-block-image alignfull size-full\"><img src=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-2.png\" alt=\"\" class=\"wp-image-37\"/></figure><!-- /wp:image --><!-- wp:heading {\"level\":3} --><h3>The Life I Deserve</h3><!-- /wp:heading --><!-- wp:paragraph --><p>August 1 -- December 1</p><!-- /wp:paragraph --><!-- wp:button {\"className\":\"is-style-outline\"} --><div class=\"wp-block-button is-style-outline\"><a class=\"wp-block-button__link\" href=\"https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/\">Read More</a></div><!-- /wp:button --></div></div><!-- /wp:group --><!-- wp:group --><div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container\"><!-- wp:image {\"align\":\"full\",\"id\":37,\"sizeSlug\":\"full\"} --><figure class=\"wp-block-image alignfull size-full\"><img src=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-three-quarters-4.png\" alt=\"\" class=\"wp-image-37\"/></figure><!-- /wp:image --><!-- wp:heading {\"level\":3} --><h3>From Signac to Matisse</h3><!-- /wp:heading --><!-- wp:paragraph --><p>October 1 -- December 1</p><!-- /wp:paragraph --><!-- wp:button {\"className\":\"is-style-outline\"} --><div class=\"wp-block-button is-style-outline\"><a class=\"wp-block-button__link\" href=\"https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/\">Read More</a></div><!-- /wp:button --></div></div><!-- /wp:group --></div><!-- /wp:column --></div><!-- /wp:columns --><!-- wp:image {\"align\":\"full\",\"id\":37,\"sizeSlug\":\"full\"} --><figure class=\"wp-block-image alignfull size-full\"><img src=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-landscape-2.png\" alt=\"\" class=\"wp-image-37\"/></figure><!-- /wp:image --><!-- wp:group {\"align\":\"wide\"} --><div class=\"wp-block-group alignwide\"><div class=\"wp-block-group__inner-container\"><!-- wp:heading {\"align\":\"center\",\"textColor\":\"accent\"} --><h2 class=\"has-accent-color has-text-align-center\">”Cyborgs, as the philosopher <NAME> established, are not reverent. They do not remember the cosmos.”</h2><!-- /wp:heading --></div></div><!-- /wp:group --><!-- wp:paragraph {\"dropCap\":true} --><p class=\"has-drop-cap\">With seven floors of striking architecture, UMoMA shows exhibitions of international contemporary art, sometimes along with art historical retrospectives. Existential, political and philosophical issues are intrinsic to our programme. As visitor you are invited to guided tours artist talks, lectures, film screenings and other events with free admission</p><!-- /wp:paragraph --><!-- wp:paragraph --><p>The exhibitions are produced by UMoMA in collaboration with artists and museums around the world and they often attract international attention. UMoMA has received a Special Commendation from the European Museum of the Year, and was among the top candidates for the Swedish Museum of the Year Award as well as for the Council of Europe Museum Prize.</p><!-- /wp:paragraph --><!-- wp:paragraph --><p></p><!-- /wp:paragraph --><!-- wp:group {\"customBackgroundColor\":\"#ffffff\",\"align\":\"wide\"} --><div class=\"wp-block-group alignwide has-background\" style=\"background-color:#ffffff\"><div class=\"wp-block-group__inner-container\"><!-- wp:group --><div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container\"><!-- wp:heading {\"align\":\"center\"} --><h2 class=\"has-text-align-center\">Become a Member and Get Exclusive Offers!</h2><!-- /wp:heading --><!-- wp:paragraph {\"align\":\"center\"} --><p class=\"has-text-align-center\">Members get access to exclusive exhibits and sales. Our memberships cost $99.99 and are billed annually.</p><!-- /wp:paragraph --><!-- wp:button {\"align\":\"center\"} --><div class=\"wp-block-button aligncenter\"><a class=\"wp-block-button__link\" href=\"https://make.wordpress.org/core/2019/09/27/block-editor-theme-related-updates-in-wordpress-5-3/\">Join the Club</a></div><!-- /wp:button --></div></div><!-- /wp:group --></div></div><!-- /wp:group --><!-- wp:gallery {\"ids\":[39,38],\"align\":\"wide\"} --><figure class=\"wp-block-gallery alignwide columns-2 is-cropped\"><ul class=\"blocks-gallery-grid\"><li class=\"blocks-gallery-item\"><figure><img src=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-square-2.png\" alt=\"\" data-id=\"39\" data-full-url=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-square-2.png\" data-link=\"assets/images/2020-square-2/\" class=\"wp-image-39\"/></figure></li><li class=\"blocks-gallery-item\"><figure><img src=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-square-1.png\" alt=\"\" data-id=\"38\" data-full-url=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-square-1.png\" data-link=\"http://localhost/wp-content/themes/twentytwenty/assets/images/2020-square-1/\" class=\"wp-image-38\"/></figure></li></ul></figure><!-- /wp:gallery -->','The New UMoMA Opens its Doors','','auto-draft','closed','closed','','','','','2020-02-08 18:08:09','0000-00-00 00:00:00','',0,'http://localhost/?page_id=6',0,'page','',0),(7,1,'2020-02-08 18:08:09','0000-00-00 00:00:00','<!-- wp:paragraph -->\n<p>You might be an artist who would like to introduce yourself and your work here or maybe you’re a business with a mission to describe.</p>\n<!-- /wp:paragraph -->','About','','auto-draft','closed','closed','','','','','2020-02-08 18:08:09','0000-00-00 00:00:00','',0,'http://localhost/?page_id=7',0,'page','',0),(8,1,'2020-02-08 18:08:09','0000-00-00 00:00:00','<!-- wp:paragraph -->\n<p>This is a page with some basic contact information, such as an address and phone number. You might also try a plugin to add a contact form.</p>\n<!-- /wp:paragraph -->','Contact','','auto-draft','closed','closed','','','','','2020-02-08 18:08:09','0000-00-00 00:00:00','',0,'http://localhost/?page_id=8',0,'page','',0),(9,1,'2020-02-08 18:08:09','0000-00-00 00:00:00','','Blog','','auto-draft','closed','closed','','','','','2020-02-08 18:08:09','0000-00-00 00:00:00','',0,'http://localhost/?page_id=9',0,'page','',0),(10,1,'2020-02-08 18:08:09','0000-00-00 00:00:00','{\n \"widget_text[2]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"YTo0OntzOjU6InRpdGxlIjtzOjE1OiJBYm91dC<KEY>n \"title\": \"About This Site\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"4cb1f50e1662ca55dfec0a125e639037\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"sidebars_widgets[sidebar-1]\": {\n \"starter_content\": true,\n \"value\": [\n \"text-2\"\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"widget_text[3]\": {\n \"starter_content\": true,\n \"value\": {\n \"encoded_serialized_instance\": \"<KEY>n \"title\": \"Find Us\",\n \"is_widget_customizer_js_value\": true,\n \"instance_hash_key\": \"a629d95f2b63903e0b3418abf2737dee\"\n },\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"sidebars_widgets[sidebar-2]\": {\n \"starter_content\": true,\n \"value\": [\n \"text-3\"\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menus_created_posts\": {\n \"starter_content\": true,\n \"value\": [\n 5,\n 6,\n 7,\n 8,\n 9\n ],\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Primary\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-1]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"custom\",\n \"title\": \"Home\",\n \"url\": \"http://localhost/\",\n \"position\": 0,\n \"nav_menu_term_id\": -1,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-2]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 7,\n \"position\": 1,\n \"nav_menu_term_id\": -1,\n \"title\": \"About\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-3]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 9,\n \"position\": 2,\n \"nav_menu_term_id\": -1,\n \"title\": \"Blog\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-4]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 8,\n \"position\": 3,\n \"nav_menu_term_id\": -1,\n \"title\": \"Contact\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"twentytwenty::nav_menu_locations[primary]\": {\n \"starter_content\": true,\n \"value\": -1,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Primary\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-5]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"custom\",\n \"title\": \"Home\",\n \"url\": \"http://localhost/\",\n \"position\": 0,\n \"nav_menu_term_id\": -5,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-6]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 7,\n \"position\": 1,\n \"nav_menu_term_id\": -5,\n \"title\": \"About\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-7]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 9,\n \"position\": 2,\n \"nav_menu_term_id\": -5,\n \"title\": \"Blog\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-8]\": {\n \"starter_content\": true,\n \"value\": {\n \"type\": \"post_type\",\n \"object\": \"page\",\n \"object_id\": 8,\n \"position\": 3,\n \"nav_menu_term_id\": -5,\n \"title\": \"Contact\"\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"twentytwenty::nav_menu_locations[expanded]\": {\n \"starter_content\": true,\n \"value\": -5,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu[-9]\": {\n \"starter_content\": true,\n \"value\": {\n \"name\": \"Social Links Menu\"\n },\n \"type\": \"nav_menu\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-9]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Yelp\",\n \"url\": \"https://www.yelp.com\",\n \"position\": 0,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-10]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Facebook\",\n \"url\": \"https://www.facebook.com/wordpress\",\n \"position\": 1,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-11]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Twitter\",\n \"url\": \"https://twitter.com/wordpress\",\n \"position\": 2,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-12]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Instagram\",\n \"url\": \"https://www.instagram.com/explore/tags/wordcamp/\",\n \"position\": 3,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"nav_menu_item[-13]\": {\n \"starter_content\": true,\n \"value\": {\n \"title\": \"Email\",\n \"url\": \"mailto:<EMAIL>\",\n \"position\": 4,\n \"nav_menu_term_id\": -9,\n \"object_id\": 0\n },\n \"type\": \"nav_menu_item\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"twentytwenty::nav_menu_locations[social]\": {\n \"starter_content\": true,\n \"value\": -9,\n \"type\": \"theme_mod\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"show_on_front\": {\n \"starter_content\": true,\n \"value\": \"page\",\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"page_on_front\": {\n \"starter_content\": true,\n \"value\": 6,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n },\n \"page_for_posts\": {\n \"starter_content\": true,\n \"value\": 9,\n \"type\": \"option\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:08:09\"\n }\n}','','','auto-draft','closed','closed','','bcb8ddd5-4ded-4b26-b470-f7f2dc75171d','','','2020-02-08 18:08:09','0000-00-00 00:00:00','',0,'http://localhost/?p=10',0,'customize_changeset','',0),(11,1,'2020-02-08 18:19:30','0000-00-00 00:00:00','{\n \"custom_css[photoblogster]\": {\n \"value\": \".customize-unpreviewable {\\n\\tdisplay: none;\\n}\",\n \"type\": \"custom_css\",\n \"user_id\": 1,\n \"date_modified_gmt\": \"2020-02-08 18:19:30\"\n }\n}','','','auto-draft','closed','closed','','188301e0-3976-45e3-95a4-aee0e51e71d7','','','2020-02-08 18:19:30','0000-00-00 00:00:00','',0,'http://localhost/?p=11',0,'customize_changeset','',0);
/*!40000 ALTER TABLE `wp_posts` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_term_relationships`
--
DROP TABLE IF EXISTS `wp_term_relationships`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_term_relationships` (
`object_id` bigint unsigned NOT NULL DEFAULT '0',
`term_taxonomy_id` bigint unsigned NOT NULL DEFAULT '0',
`term_order` int NOT NULL DEFAULT '0',
PRIMARY KEY (`object_id`,`term_taxonomy_id`),
KEY `term_taxonomy_id` (`term_taxonomy_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_term_relationships`
--
LOCK TABLES `wp_term_relationships` WRITE;
/*!40000 ALTER TABLE `wp_term_relationships` DISABLE KEYS */;
INSERT INTO `wp_term_relationships` VALUES (1,1,0);
/*!40000 ALTER TABLE `wp_term_relationships` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_term_taxonomy`
--
DROP TABLE IF EXISTS `wp_term_taxonomy`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_term_taxonomy` (
`term_taxonomy_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`term_id` bigint unsigned NOT NULL DEFAULT '0',
`taxonomy` varchar(32) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`description` longtext COLLATE utf8mb4_unicode_520_ci NOT NULL,
`parent` bigint unsigned NOT NULL DEFAULT '0',
`count` bigint NOT NULL DEFAULT '0',
PRIMARY KEY (`term_taxonomy_id`),
UNIQUE KEY `term_id_taxonomy` (`term_id`,`taxonomy`),
KEY `taxonomy` (`taxonomy`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_term_taxonomy`
--
LOCK TABLES `wp_term_taxonomy` WRITE;
/*!40000 ALTER TABLE `wp_term_taxonomy` DISABLE KEYS */;
INSERT INTO `wp_term_taxonomy` VALUES (1,1,'category','',0,1);
/*!40000 ALTER TABLE `wp_term_taxonomy` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_termmeta`
--
DROP TABLE IF EXISTS `wp_termmeta`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_termmeta` (
`meta_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`term_id` bigint unsigned NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (`meta_id`),
KEY `term_id` (`term_id`),
KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_termmeta`
--
LOCK TABLES `wp_termmeta` WRITE;
/*!40000 ALTER TABLE `wp_termmeta` DISABLE KEYS */;
/*!40000 ALTER TABLE `wp_termmeta` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_terms`
--
DROP TABLE IF EXISTS `wp_terms`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_terms` (
`term_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`slug` varchar(200) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`term_group` bigint NOT NULL DEFAULT '0',
PRIMARY KEY (`term_id`),
KEY `slug` (`slug`(191)),
KEY `name` (`name`(191))
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_terms`
--
LOCK TABLES `wp_terms` WRITE;
/*!40000 ALTER TABLE `wp_terms` DISABLE KEYS */;
INSERT INTO `wp_terms` VALUES (1,'Uncategorized','uncategorized',0);
/*!40000 ALTER TABLE `wp_terms` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_usermeta`
--
DROP TABLE IF EXISTS `wp_usermeta`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_usermeta` (
`umeta_id` bigint unsigned NOT NULL AUTO_INCREMENT,
`user_id` bigint unsigned NOT NULL DEFAULT '0',
`meta_key` varchar(255) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,
`meta_value` longtext COLLATE utf8mb4_unicode_520_ci,
PRIMARY KEY (`umeta_id`),
KEY `user_id` (`user_id`),
KEY `meta_key` (`meta_key`(191))
) ENGINE=InnoDB AUTO_INCREMENT=19 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_usermeta`
--
LOCK TABLES `wp_usermeta` WRITE;
/*!40000 ALTER TABLE `wp_usermeta` DISABLE KEYS */;
INSERT INTO `wp_usermeta` VALUES (1,1,'nickname','admin'),(2,1,'first_name',''),(3,1,'last_name',''),(4,1,'description',''),(5,1,'rich_editing','true'),(6,1,'syntax_highlighting','true'),(7,1,'comment_shortcuts','false'),(8,1,'admin_color','fresh'),(9,1,'use_ssl','0'),(10,1,'show_admin_bar_front','true'),(11,1,'locale',''),(12,1,'wp_capabilities','a:1:{s:13:\"administrator\";b:1;}'),(13,1,'wp_user_level','10'),(14,1,'dismissed_wp_pointers',''),(15,1,'show_welcome_panel','1'),(16,1,'session_tokens','a:2:{s:64:\"ed6f08a3654de4357b71d9a32e63f518075893cc5be7277cbe826393632173ca\";a:4:{s:10:\"expiration\";i:1581357991;s:2:\"ip\";s:10:\"172.23.0.1\";s:2:\"ua\";s:121:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36\";s:5:\"login\";i:1581185191;}s:64:\"aa88ac3e8d3f2699b8bc2081403cd4beb5b335216bdbae1a85e576df98976e94\";a:4:{s:10:\"expiration\";i:1581364671;s:2:\"ip\";s:10:\"172.23.0.1\";s:2:\"ua\";s:121:\"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36\";s:5:\"login\";i:1581191871;}}'),(17,1,'wp_dashboard_quick_press_last_post_id','4'),(18,1,'community-events-location','a:1:{s:2:\"ip\";s:10:\"172.23.0.0\";}');
/*!40000 ALTER TABLE `wp_usermeta` ENABLE KEYS */;
UNLOCK TABLES;
--
-- Table structure for table `wp_users`
--
DROP TABLE IF EXISTS `wp_users`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `wp_users` (
`ID` bigint unsigned NOT NULL AUTO_INCREMENT,
`user_login` varchar(60) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_pass` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_nicename` varchar(50) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_email` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_url` varchar(100) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_registered` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
`user_activation_key` varchar(255) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
`user_status` int NOT NULL DEFAULT '0',
`display_name` varchar(250) COLLATE utf8mb4_unicode_520_ci NOT NULL DEFAULT '',
PRIMARY KEY (`ID`),
KEY `user_login_key` (`user_login`),
KEY `user_nicename` (`user_nicename`),
KEY `user_email` (`user_email`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wp_users`
--
LOCK TABLES `wp_users` WRITE;
/*!40000 ALTER TABLE `wp_users` DISABLE KEYS */;
INSERT INTO `wp_users` VALUES (1,'admin','$P$BRtOJg/aQvAJ6UHbcyoBxWxr8/1T9p/','admin','<EMAIL>','','2020-02-08 17:46:49','',0,'admin');
/*!40000 ALTER TABLE `wp_users` ENABLE KEYS */;
UNLOCK TABLES;
/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
-- Dump completed on 2020-02-08 20:16:04
|
<gh_stars>0
create database Deca;
use Deca;
create table [dbo].[Dete](
[ID] int primary key identity not null,
[Ime] varchar(20) null,
[Prezime] varchar(30) null,
[Pol] varchar(10) null,
[DatumRodjenja] Date null,
[ImeOca] varchar(20) null,
[ImeMajke] varchar(20) null,
[Slika] varchar(150) null
);
create procedure [dbo].[GetDete]
as
begin
select * from Dete
end
create procedure [dbo].[AddDete] (
@Ime varchar(20),
@Prezime varchar(30),
@Pol varchar(10),
@DatumRodjenja Date,
@ImeOca varchar(20),
@ImeMajke varchar(20),
@Slika varchar(150)
)
as
begin
insert into Dete values(@Ime,@Prezime,@Pol,@DatumRodjenja,@ImeOca,@ImeMajke,@Slika)
end
create procedure [dbo].[UpdateDete] (
@ID int,
@Ime varchar(20),
@Prezime varchar(30),
@Pol varchar(10),
@DatumRodjenja Date,
@ImeOca varchar(20),
@ImeMajke varchar(20),
@Slika varchar(150)
)
as
begin
update Dete set Ime=@Ime,Prezime = @Prezime, Pol=@Pol,DatumRodjenja = @DatumRodjenja,ImeOca = @ImeOca,ImeMajke=@ImeMajke,Slika=@Slika where ID=@ID;
end
create procedure [dbo].[DeleteDete]
(
@ID int
)
as
begin
delete from Dete where ID=@ID;
end
|
<reponame>DSSG-EUROPE/wef_oceans
DELETE
FROM ais_messages.full_year_position
WHERE (mmsi IS NULL OR mmsi < 100000000)
OR (timestamp IS NULL OR timestamp = '1970-01-01 00:00:00')
OR (longitude IS NULL OR longitude NOT BETWEEN -180 AND 180)
OR (latitude IS NULL OR latitude NOT BETWEEN -90 AND 90);
DELETE
FROM ais_messages.full_year_static
WHERE (mmsi IS NULL OR mmsi < 100000000)
OR (timestamp IS NULL OR timestamp = '1970-01-01 00:00:00');
|
WITH MaxRecursionTest AS ( SELECT 0 AS Tally
UNION ALL
SELECT Tally + 1 AS Tally
FROM MaxRecursionTest
WHERE Tally < 110
)
SELECT * FROM MaxRecursionTest OPTION ( MAXRECURSION 110 )
|
create schema if not exists database_migration;
/*
This script will generate create schema, create table and create import statements
to load all needed data from an EXASOL database. Automatic datatype conversion is
applied whenever needed. Feel free to adjust it.
*/
--/
create or replace script database_migration.EXASOL_TO_EXASOL(
CONNECTION_NAME -- name of the database connection inside exasol -> e.g. my_exa
,IDENTIFIER_CASE_INSENSITIVE -- true if identifiers should be stored case-insensitiv (will be stored upper_case)
,SCHEMA_FILTER -- filter for the schemas to generate and load (except EXA_SATISTICS and SYS) -> '%' to load all
,TABLE_FILTER -- filter for the tables to generate and load -> '%' to load all
,GENERATE_VIEWS -- flag to control inclusion of views
,VIEW_FILTER -- filter for the views to generate -> '%' to generate all
) RETURNS TABLE
AS
exa_upper_begin=''
exa_upper_end=''
if IDENTIFIER_CASE_INSENSITIVE == true then
exa_upper_begin='upper('
exa_upper_end=')'
end
suc, res = pquery([[
with vv_exa_columns as (
select ]]..exa_upper_begin..[[table_schema]]..exa_upper_end..[[ as "exa_table_schema", ]]..exa_upper_begin..[[table_name]]..exa_upper_end..[[ as "exa_table_name", ]]..exa_upper_begin..[[column_name]]..exa_upper_end..[[ as "exa_column_name", exasql.* from
(import from exa at ]]..CONNECTION_NAME..[[ statement
'select table_schema, table_name, column_name, COLUMN_ORDINAL_POSITION ordinal_position, COLUMN_TYPE data_type, column_type, COLUMN_MAXSIZE character_maximum_length, COLUMN_NUM_PREC numeric_precision, COLUMN_NUM_SCALE numeric_scale
from EXA_ALL_COLUMNS c join EXA_ALL_TABLES t on t.table_schema = c.column_schema and t.table_name = c.column_table
where table_schema not in (''SYS'',''EXA_STATISTICS'')
AND table_schema like '']]..SCHEMA_FILTER..[[''
AND table_name like '']]..TABLE_FILTER..[[''
') as exasql
)
,vv_create_schemas as(
SELECT 'create schema "' || "exa_table_schema" || '";' as sql_text from vv_exa_columns group by "exa_table_schema" order by "exa_table_schema"
)
,vv_create_tables as (
select 'create or replace table "' || "exa_table_schema" || '"."' || "exa_table_name" || '" (' || group_concat('"' || "exa_column_name" || '" ' || data_type
order by ordinal_position) || ');' as sql_text
from vv_exa_columns group by "exa_table_schema", "exa_table_name"
order by "exa_table_schema","exa_table_name"
)
, vv_imports as (
select 'import into "' || "exa_table_schema" || '"."' || "exa_table_name" || '" from exa at ]]..CONNECTION_NAME..[[ table "' || table_schema||'"."'||table_name||'";' as sql_text
from vv_exa_columns group by "exa_table_schema","exa_table_name", table_schema,table_name
order by "exa_table_schema","exa_table_name", table_schema,table_name
)
,vv_create_views as(
select view_text || ';' as sql_text from
(import from exa at ]]..CONNECTION_NAME..[[ statement
'select view_text from EXA_ALL_VIEWS
where view_schema like '']]..SCHEMA_FILTER..[[''
and ]]..GENERATE_VIEWS..[[
and view_name like '']]..VIEW_FILTER..[[''
order by view_schema, view_name
') as exasql
)
select SQL_TEXT from (
select 1 as ord, cast('-- ### SCHEMAS ###' as varchar(2000000)) SQL_TEXT
union all
select 2, a.* from vv_create_schemas a
UNION ALL
select 3, cast('-- ### TABLES ###' as varchar(2000000)) SQL_TEXT
union all
select 4, b.* from vv_create_tables b
UNION ALL
select 5, cast('-- ### IMPORTS ###' as varchar(2000000)) SQL_TEXT
union all
select 6, c.* from vv_imports c
union all
select 7, cast('-- ### VIEWS - Add FORCE as needed to avoid ordering dependencies ###' as varchar(2000000)) SQL_TEXT
from dual where ]]..GENERATE_VIEWS..[[
union all
select 8, d.* from vv_create_views d
) order by ord
]],{})
if not suc then
error('"'..res.error_message..'" Caught while executing: "'..res.statement_text..'"')
end
return(res)
/
-- Create a connection to the your other Exasol database
create connection SECOND_EXASOL_DB to '192.168.6.11..14:8563' user 'username' identified by 'exasolRocks!';
execute script database_migration.EXASOL_TO_EXASOL(
'SECOND_EXASOL_DB' -- name of your database connection
,TRUE -- case sensitivity handling for identifiers -> false: handle them case sensitiv / true: handle them case insensitiv --> recommended: true
,'MY_SCHEMA' -- schema filter --> '%' to load all schemas except 'SYS' and 'EXA_STATISTICS'/ '%pub%' to load all schemas like '%pub%'
,'%' -- table filter --> '%' to load all tables
,'FALSE' -- view inclusion flag --> 'TRUE' to include views
,'%' -- view filter --> '%' to generate all views
);
commit;
|
<filename>data/github.com/ccondrup/mage-reset/1f0894be655a45e0fbcb85f539a89d3f1f3af245/reset_increment_ids.sql
-- Resets testdata for Magento --
-- This will delete your existing increment ids for orders, invoices, creditmemos and shipment and replace with values specified
-- Credits: Elias Interactive http://goo.gl/E03d5 & ChiliPepperDesign http://goo.gl/FcWGx
-- Merged and compiled by ccondrup for CCData.no
-- Start config section. Set your options here --
-- For empty values, leave blank ('') rather than delete the variables --
SET @id_store := '3'; -- The id of the Mage store you wish to change. Run this script for each store.
SET @id_prefix := NULL; -- Prefix for new numbers, alphanumeric is OK, NULL or numeric preferrable
SET @nr_nextid := 10101; -- Next order id. Match padlength! Mage default 00000001 = 8 digits, means @nr_padding should be 8.
SET @nr_padding := char_length(@nr_nextid); -- Automatic. Override if needed. How many digits was set for nr_nextid? Mage default 8
-- The set values will result in next id = #310102 --
-- End config section. No need to edit below --
SET FOREIGN_KEY_CHECKS = 0;
SET NAMES utf8; -- Make sure to preserve Unicode characters outside Basic Multilingual Plane (Æ,ö, etc etc.)
-- First set pad length
UPDATE `eav_entity_type`
SET `increment_pad_length` = @nr_padding
WHERE (
`entity_type_code` = 'order'
OR `entity_type_code` = 'invoice'
OR `entity_type_code` = 'shipment'
OR `entity_type_code` = 'creditmemo'
);
-- Create and run the procedure to set defaults for orders, invoices, shipments, credit memos
DELIMITER ||
DROP PROCEDURE IF EXISTS `ccdata_set_defaults`||
CREATE PROCEDURE ccdata_set_defaults (IN id_store INT(5), IN id_prefix VARCHAR(15), IN nr_nextid VARCHAR(15))
MODIFIES SQL DATA
BEGIN
DECLARE id_type,done INT;
DECLARE cur_1 CURSOR FOR SELECT entity_type_id FROM `eav_entity_type` WHERE entity_type_code IN ('order', 'invoice', 'creditmemo', 'shipment');
DECLARE CONTINUE HANDLER FOR NOT FOUND SET done = 1;
IF id_prefix = 'NULL' THEN SET id_prefix = NULL; END IF;
OPEN cur_1;
REPEAT
FETCH cur_1 INTO id_type;
DELETE FROM `eav_entity_store` WHERE `entity_type_id` = id_type AND `store_id` = id_store;
INSERT INTO `eav_entity_store` (`entity_type_id`, `store_id`, `increment_prefix`, `increment_last_id`)
VALUES(id_type, id_store, id_prefix, CONCAT(CAST(id_store AS CHAR), nr_nextid));
UNTIL done = 1
END REPEAT;
CLOSE cur_1;
END;||
CALL ccdata_set_defaults(@id_store, @id_prefix, @nr_nextid)||
DROP PROCEDURE IF EXISTS `ccdata_set_defaults`||
DELIMITER ;||
SET FOREIGN_KEY_CHECKS = 1;
|
-- file:plpgsql.sql ln:4046 expect:true
create or replace function conflict_test() returns setof int8_tbl as $$
#variable_conflict use_column
declare r record
|
create table world_maps_merchant
(
CharacterId int not null
primary key,
AccountId int not null,
MapId int null,
Cell int not null,
Direction int not null,
EntityLookString mediumtext null,
Name mediumtext not null,
SellType int not null,
IsActive tinyint not null,
MerchantSince datetime not null
)
engine = MyISAM
charset = utf8;
|
<gh_stars>0
-- SPDX-License-Identifier: Apache-2.0
-- Licensed to the Ed-Fi Alliance under one or more agreements.
-- The Ed-Fi Alliance licenses this file to you under the Apache License, Version 2.0.
-- See the LICENSE and NOTICES files in the project root for more information.
CREATE UNIQUE INDEX IF NOT EXISTS UX_91a31b_Id ON tpdm.AnonymizedStudent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_a5aeb2_Id ON tpdm.AnonymizedStudentAcademicRecord(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_e4eb73_Id ON tpdm.AnonymizedStudentAssessment(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_e6ba6c_Id ON tpdm.AnonymizedStudentAssessmentCourseAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_64d5d3_Id ON tpdm.AnonymizedStudentAssessmentSectionAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_2abb16_Id ON tpdm.AnonymizedStudentCourseAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_d194a8_Id ON tpdm.AnonymizedStudentCourseTranscript(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_7f59f4_Id ON tpdm.AnonymizedStudentEducationOrganizationAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_562e9d_Id ON tpdm.AnonymizedStudentSectionAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_0a1ce1_Id ON tpdm.Applicant(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_57cdba_Id ON tpdm.ApplicantProspectAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_e7ad52_Id ON tpdm.Application(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_143de6_Id ON tpdm.ApplicationEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_447e8f_Id ON tpdm.CompleterAsStaffAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_055fb2_Id ON tpdm.CourseCourseTranscriptFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_6cdc01_Id ON tpdm.CourseStudentAcademicRecordFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_157c1d_Id ON tpdm.CourseStudentAssessmentFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_81ddd0_Id ON tpdm.CourseStudentFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_092fc4_Id ON tpdm.EducationOrganizationCourseTranscriptFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_f4fab0_Id ON tpdm.EducationOrganizationFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_347c34_Id ON tpdm.EducationOrganizationStudentAcademicRecordFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_7c74f1_Id ON tpdm.EducationOrganizationStudentAssessmentFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_eedec2_Id ON tpdm.EducationOrganizationStudentFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_786774_Id ON tpdm.EmploymentEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_f51cef_Id ON tpdm.EmploymentSeparationEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_e809b0_Id ON tpdm.OpenStaffPositionEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_97e755_Id ON tpdm.PerformanceMeasure(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_e21917_Id ON tpdm.PerformanceMeasureCourseAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_be96e7_Id ON tpdm.PerformanceMeasureFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_8c4ca1_Id ON tpdm.ProfessionalDevelopmentEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_f84f61_Id ON tpdm.Prospect(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_dc8233_Id ON tpdm.ProspectProfessionalDevelopmentEventAttendance(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_6232e8_Id ON tpdm.RecruitmentEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_f13a78_Id ON tpdm.Rubric(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_6ab97b_Id ON tpdm.RubricLevel(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_c8ffc2_Id ON tpdm.RubricLevelResponse(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_98f7aa_Id ON tpdm.RubricLevelResponseFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_51c6b9_Id ON tpdm.SectionCourseTranscriptFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_f7814e_Id ON tpdm.SectionStudentAcademicRecordFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_aeccab_Id ON tpdm.SectionStudentAssessmentFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_5b8d40_Id ON tpdm.SectionStudentFacts(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_11e466_Id ON tpdm.StaffApplicantAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_5f5473_Id ON tpdm.StaffEvaluation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_60e7ab_Id ON tpdm.StaffEvaluationComponent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_6b5a36_Id ON tpdm.StaffEvaluationComponentRating(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_9e0757_Id ON tpdm.StaffEvaluationElement(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_e94b2b_Id ON tpdm.StaffEvaluationElementRating(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_e34e81_Id ON tpdm.StaffEvaluationRating(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_420d2e_Id ON tpdm.StaffFieldworkAbsenceEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_fe2944_Id ON tpdm.StaffFieldworkExperience(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_aa4534_Id ON tpdm.StaffFieldworkExperienceSectionAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_b4a1e0_Id ON tpdm.StaffProfessionalDevelopmentEventAttendance(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_990b71_Id ON tpdm.StaffProspectAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_609983_Id ON tpdm.StaffStudentGrowthMeasure(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_f22014_Id ON tpdm.StaffStudentGrowthMeasureCourseAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_120788_Id ON tpdm.StaffStudentGrowthMeasureEducationOrganizationAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_fbfeb4_Id ON tpdm.StaffStudentGrowthMeasureSectionAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_7bf40b_Id ON tpdm.StaffTeacherPreparationProviderAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_5bac62_Id ON tpdm.StaffTeacherPreparationProviderProgramAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_c4d5a9_Id ON tpdm.TalentManagementGoal(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_835b49_Id ON tpdm.TeacherCandidate(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_163dde_Id ON tpdm.TeacherCandidateAcademicRecord(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_87fd83_Id ON tpdm.TeacherCandidateCourseTranscript(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_30d301_Id ON tpdm.TeacherCandidateFieldworkAbsenceEvent(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_fe5770_Id ON tpdm.TeacherCandidateFieldworkExperience(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_1a948e_Id ON tpdm.TeacherCandidateFieldworkExperienceSectionAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_8c39c1_Id ON tpdm.TeacherCandidateProfessionalDevelopmentEventAttendance(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_3395e5_Id ON tpdm.TeacherCandidateStaffAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_464a58_Id ON tpdm.TeacherCandidateStudentGrowthMeasure(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_512fab_Id ON tpdm.TeacherCandidateStudentGrowthMeasureCourseAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_22b9a4_Id ON tpdm.TeacherCandidateStudentGrowthMeasureEducationOrganizatio_22b9a4(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_b8b1b0_Id ON tpdm.TeacherCandidateStudentGrowthMeasureSectionAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_0dff08_Id ON tpdm.TeacherCandidateTeacherPreparationProviderAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_81475b_Id ON tpdm.TeacherCandidateTeacherPreparationProviderProgramAssociation(Id);
CREATE UNIQUE INDEX IF NOT EXISTS UX_aceeb9_Id ON tpdm.TeacherPreparationProviderProgram(Id);
|
<reponame>rmulvey/bptest<gh_stars>1-10
-- BP 6.1D content: domain syschar: 3
INSERT INTO S_DOM
VALUES (171286,
'G_ALL_performance_test3',
'Test3 sends an instance event, with no supplemental data, between instances of different classes 10000 times ( 5000 times from each instance ).',
0,
1);
INSERT INTO S_CDT
VALUES (524289,
0);
INSERT INTO S_DT
VALUES (524289,
171286,
'void',
'');
INSERT INTO S_CDT
VALUES (524290,
1);
INSERT INTO S_DT
VALUES (524290,
171286,
'boolean',
'');
INSERT INTO S_CDT
VALUES (524291,
2);
INSERT INTO S_DT
VALUES (524291,
171286,
'integer',
'');
INSERT INTO S_CDT
VALUES (524292,
3);
INSERT INTO S_DT
VALUES (524292,
171286,
'real',
'');
INSERT INTO S_CDT
VALUES (524293,
4);
INSERT INTO S_DT
VALUES (524293,
171286,
'string',
'');
INSERT INTO S_CDT
VALUES (524294,
5);
INSERT INTO S_DT
VALUES (524294,
171286,
'unique_id',
'');
INSERT INTO S_CDT
VALUES (524295,
6);
INSERT INTO S_DT
VALUES (524295,
171286,
'state<State_Model>',
'');
INSERT INTO S_CDT
VALUES (524296,
7);
INSERT INTO S_DT
VALUES (524296,
171286,
'same_as<Base_Attribute>',
'');
INSERT INTO S_CDT
VALUES (524297,
8);
INSERT INTO S_DT
VALUES (524297,
171286,
'inst_ref<Object>',
'');
INSERT INTO S_CDT
VALUES (524298,
9);
INSERT INTO S_DT
VALUES (524298,
171286,
'inst_ref_set<Object>',
'');
INSERT INTO S_CDT
VALUES (524299,
10);
INSERT INTO S_DT
VALUES (524299,
171286,
'inst<Event>',
'');
INSERT INTO S_CDT
VALUES (524300,
11);
INSERT INTO S_DT
VALUES (524300,
171286,
'inst<Mapping>',
'');
INSERT INTO S_CDT
VALUES (524301,
12);
INSERT INTO S_DT
VALUES (524301,
171286,
'inst_ref<Mapping>',
'');
INSERT INTO S_UDT
VALUES (524302,
524300,
1);
INSERT INTO S_DT
VALUES (524302,
171286,
'date',
'');
INSERT INTO S_UDT
VALUES (524303,
524300,
2);
INSERT INTO S_DT
VALUES (524303,
171286,
'timestamp',
'');
INSERT INTO S_UDT
VALUES (524304,
524301,
3);
INSERT INTO S_DT
VALUES (524304,
171286,
'inst_ref<Timer>',
'');
INSERT INTO S_EE
VALUES (524289,
'Architecture',
'',
'ARCH',
171286);
INSERT INTO S_BRG
VALUES (524289,
524289,
'shutdown',
'',
0,
524289,
'',
1);
INSERT INTO GD_MD
VALUES (524289,
1,
171286,
1,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (524293,
524289,
524289,
12);
INSERT INTO GD_SHP
VALUES (524293,
1856,
1520,
2080,
1680);
INSERT INTO GD_GE
VALUES (524294,
524289,
1048578,
11);
INSERT INTO GD_SHP
VALUES (524294,
1856,
1296,
2080,
1456);
INSERT INTO GD_MD
VALUES (524290,
2,
171286,
1,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (524295,
524290,
1048578,
11);
INSERT INTO GD_SHP
VALUES (524295,
1856,
1296,
2080,
1456);
INSERT INTO GD_MD
VALUES (524291,
3,
171286,
1,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (524296,
524291,
1048578,
11);
INSERT INTO GD_SHP
VALUES (524296,
1856,
1296,
2080,
1456);
INSERT INTO GD_MD
VALUES (524292,
4,
171286,
1,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (524297,
524292,
1048578,
11);
INSERT INTO GD_SHP
VALUES (524297,
1856,
1296,
2080,
1456);
INSERT INTO S_SS
VALUES (1048578,
'Test3',
'',
'T3',
1,
171286,
1048578);
INSERT INTO O_OBJ
VALUES (1048577,
'Initialization',
1,
'INIT',
'',
1048578);
INSERT INTO O_NBATTR
VALUES (1048577,
1048577);
INSERT INTO O_BATTR
VALUES (1048577,
1048577);
INSERT INTO O_ATTR
VALUES (1048577,
1048577,
0,
'id',
'',
'',
'id',
0,
524294);
INSERT INTO O_NBATTR
VALUES (1048578,
1048577);
INSERT INTO O_BATTR
VALUES (1048578,
1048577);
INSERT INTO O_ATTR
VALUES (1048578,
1048577,
1048577,
'current_state',
'',
'',
'current_state',
0,
524295);
INSERT INTO O_ID
VALUES (0,
1048577);
INSERT INTO O_OIDA
VALUES (1048577,
1048577,
0);
INSERT INTO SM_ISM
VALUES (1572867,
1048577);
INSERT INTO SM_SM
VALUES (1572867,
'',
3);
INSERT INTO SM_MOORE
VALUES (1572867);
INSERT INTO SM_STATE
VALUES (1572865,
1572867,
0,
'Start',
1,
0);
INSERT INTO SM_MOAH
VALUES (1572865,
1572867,
1572865);
INSERT INTO SM_AH
VALUES (1572865,
1572867);
INSERT INTO SM_ACT
VALUES (1572865,
1572867,
1,
'create object instance tc of TC;
create object instance tc2 of TC2;
generate TC1 to tc;
OP::GetMasterStart( );',
'');
INSERT INTO GD_MD
VALUES (1572865,
8,
1572867,
40,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (1572866,
1572865,
1572865,
41);
INSERT INTO GD_SHP
VALUES (1572866,
1712,
1248,
2000,
1456);
INSERT INTO O_OBJ
VALUES (1048578,
'Test Class',
2,
'TC',
'',
1048578);
INSERT INTO O_NBATTR
VALUES (1048579,
1048578);
INSERT INTO O_BATTR
VALUES (1048579,
1048578);
INSERT INTO O_ATTR
VALUES (1048579,
1048578,
0,
'id',
'',
'',
'id',
0,
524294);
INSERT INTO O_NBATTR
VALUES (1048580,
1048578);
INSERT INTO O_BATTR
VALUES (1048580,
1048578);
INSERT INTO O_ATTR
VALUES (1048580,
1048578,
1048579,
'current_state',
'',
'',
'current_state',
0,
524295);
INSERT INTO O_ID
VALUES (0,
1048578);
INSERT INTO O_OIDA
VALUES (1048579,
1048578,
0);
INSERT INTO SM_ISM
VALUES (2097156,
1048578);
INSERT INTO SM_SM
VALUES (2097156,
'',
4);
INSERT INTO SM_MOORE
VALUES (2097156);
INSERT INTO SM_SUPDT
VALUES (2097153,
2097156,
0);
INSERT INTO SM_STATE
VALUES (2097153,
2097156,
2097153,
'State One',
1,
0);
INSERT INTO SM_LEVT
VALUES (2097153,
2097156,
2097153);
INSERT INTO SM_SEVT
VALUES (2097153,
2097156,
2097153);
INSERT INTO SM_EVT
VALUES (2097153,
2097156,
2097153,
1,
'',
0,
'',
'TC1',
'');
INSERT INTO SM_SEME
VALUES (2097153,
2097153,
2097156,
2097153);
INSERT INTO SM_NSTXN
VALUES (2097153,
2097156,
2097153,
2097153,
2097153);
INSERT INTO SM_TXN
VALUES (2097153,
2097156,
2097153,
2097153);
INSERT INTO SM_MOAH
VALUES (2097153,
2097156,
2097153);
INSERT INTO SM_AH
VALUES (2097153,
2097156);
INSERT INTO SM_ACT
VALUES (2097153,
2097156,
1,
'if ( OP::IncreaseCount( ) == 10001 )
OP::GetMasterFinish( );
OP::CalculateTime( );
ARCH::shutdown( );
else
select any tc2 from instances of TC2;
generate TC21 to tc2;
end if;
',
'');
INSERT INTO GD_MD
VALUES (2097153,
8,
2097156,
40,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (2097154,
2097153,
2097153,
41);
INSERT INTO GD_SHP
VALUES (2097154,
1840,
1392,
2160,
1616);
INSERT INTO GD_GE
VALUES (2097155,
2097153,
2097153,
42);
INSERT INTO GD_CON
VALUES (2097155,
2097154,
2097154,
0);
INSERT INTO GD_CTXT
VALUES (2097155,
0,
0,
0,
0,
0,
0,
1733,
1328,
1771,
1350,
1,
-47,
0,
0,
0,
0,
0,
0);
INSERT INTO GD_LS
VALUES (2097156,
2097155,
1840,
1440,
1776,
1440,
0);
INSERT INTO GD_LS
VALUES (2097157,
2097155,
1776,
1440,
1776,
1328,
2097156);
INSERT INTO GD_LS
VALUES (2097158,
2097155,
1776,
1328,
1888,
1328,
2097157);
INSERT INTO GD_LS
VALUES (2097159,
2097155,
1888,
1328,
1888,
1392,
2097158);
INSERT INTO O_OBJ
VALUES (1048579,
'Test Class 2',
3,
'TC2',
'',
1048578);
INSERT INTO O_NBATTR
VALUES (1048581,
1048579);
INSERT INTO O_BATTR
VALUES (1048581,
1048579);
INSERT INTO O_ATTR
VALUES (1048581,
1048579,
0,
'id',
'',
'',
'id',
0,
524294);
INSERT INTO O_NBATTR
VALUES (1048582,
1048579);
INSERT INTO O_BATTR
VALUES (1048582,
1048579);
INSERT INTO O_ATTR
VALUES (1048582,
1048579,
1048581,
'current_state',
'',
'',
'current_state',
0,
524295);
INSERT INTO O_ID
VALUES (0,
1048579);
INSERT INTO O_OIDA
VALUES (1048581,
1048579,
0);
INSERT INTO SM_ISM
VALUES (2621445,
1048579);
INSERT INTO SM_SM
VALUES (2621445,
'',
5);
INSERT INTO SM_MOORE
VALUES (2621445);
INSERT INTO SM_SUPDT
VALUES (2621441,
2621445,
0);
INSERT INTO SM_STATE
VALUES (2621441,
2621445,
2621441,
'State One',
1,
0);
INSERT INTO SM_LEVT
VALUES (2621441,
2621445,
2621441);
INSERT INTO SM_SEVT
VALUES (2621441,
2621445,
2621441);
INSERT INTO SM_EVT
VALUES (2621441,
2621445,
2621441,
1,
'',
0,
'',
'TC21',
'');
INSERT INTO SM_SEME
VALUES (2621441,
2621441,
2621445,
2621441);
INSERT INTO SM_NSTXN
VALUES (2621441,
2621445,
2621441,
2621441,
2621441);
INSERT INTO SM_TXN
VALUES (2621441,
2621445,
2621441,
2621441);
INSERT INTO SM_MOAH
VALUES (2621441,
2621445,
2621441);
INSERT INTO SM_AH
VALUES (2621441,
2621445);
INSERT INTO SM_ACT
VALUES (2621441,
2621445,
1,
'x = OP::IncreaseCount( );
select any tc from instances of TC;
generate TC1 to tc;',
'');
INSERT INTO GD_MD
VALUES (2621441,
8,
2621445,
40,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (2621442,
2621441,
2621441,
41);
INSERT INTO GD_SHP
VALUES (2621442,
1856,
1344,
2112,
1552);
INSERT INTO GD_GE
VALUES (2621443,
2621441,
2621441,
42);
INSERT INTO GD_CON
VALUES (2621443,
2621442,
2621442,
0);
INSERT INTO GD_CTXT
VALUES (2621443,
0,
0,
0,
0,
0,
0,
1757,
1296,
1804,
1318,
2,
-55,
0,
0,
0,
0,
0,
0);
INSERT INTO GD_LS
VALUES (2621444,
2621443,
1856,
1424,
1808,
1424,
0);
INSERT INTO GD_LS
VALUES (2621445,
2621443,
1808,
1424,
1808,
1296,
2621444);
INSERT INTO GD_LS
VALUES (2621446,
2621443,
1808,
1296,
1936,
1296,
2621445);
INSERT INTO GD_LS
VALUES (2621447,
2621443,
1936,
1296,
1936,
1344,
2621446);
INSERT INTO O_OBJ
VALUES (1048580,
'Op Class',
4,
'OP',
'',
1048578);
INSERT INTO O_TFR
VALUES (1048577,
1048580,
'GetMasterStart',
'',
524289,
0,
'',
1);
INSERT INTO O_TFR
VALUES (1048578,
1048580,
'GetMasterFinish',
'',
524289,
0,
'',
1);
INSERT INTO O_TFR
VALUES (1048579,
1048580,
'CalculateTime',
'',
524289,
0,
'',
1);
INSERT INTO O_TFR
VALUES (1048580,
1048580,
'IncreaseCount',
'',
524291,
0,
'return -1;',
1);
INSERT INTO O_NBATTR
VALUES (1048583,
1048580);
INSERT INTO O_BATTR
VALUES (1048583,
1048580);
INSERT INTO O_ATTR
VALUES (1048583,
1048580,
0,
'id',
'',
'',
'id',
0,
524294);
INSERT INTO O_ID
VALUES (0,
1048580);
INSERT INTO O_OIDA
VALUES (1048583,
1048580,
0);
INSERT INTO GD_MD
VALUES (1048577,
5,
1048578,
11,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (1048580,
1048577,
1048577,
21);
INSERT INTO GD_SHP
VALUES (1048580,
1664,
1248,
1888,
1424);
INSERT INTO GD_GE
VALUES (1048581,
1048577,
1048578,
21);
INSERT INTO GD_SHP
VALUES (1048581,
1968,
1248,
2208,
1424);
INSERT INTO GD_GE
VALUES (1048582,
1048577,
1048579,
21);
INSERT INTO GD_SHP
VALUES (1048582,
1968,
1504,
2208,
1664);
INSERT INTO GD_GE
VALUES (1048583,
1048577,
1048580,
21);
INSERT INTO GD_SHP
VALUES (1048583,
1664,
1504,
1888,
1664);
INSERT INTO GD_MD
VALUES (1048578,
6,
1048578,
11,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (1048584,
1048578,
1048577,
21);
INSERT INTO GD_SHP
VALUES (1048584,
1664,
1248,
1856,
1312);
INSERT INTO GD_GE
VALUES (1048585,
1048578,
1048578,
21);
INSERT INTO GD_SHP
VALUES (1048585,
1968,
1248,
2160,
1312);
INSERT INTO GD_GE
VALUES (1048586,
1048578,
1048579,
21);
INSERT INTO GD_SHP
VALUES (1048586,
1968,
1504,
2160,
1568);
INSERT INTO GD_MD
VALUES (1048579,
7,
1048578,
11,
1,
0,
1,
1,
0,
12,
1600,
4200,
1.000000,
0);
INSERT INTO GD_GE
VALUES (1048587,
1048579,
1048577,
21);
INSERT INTO GD_SHP
VALUES (1048587,
1664,
1248,
1856,
1312);
INSERT INTO GD_GE
VALUES (1048588,
1048579,
1048578,
21);
INSERT INTO GD_SHP
VALUES (1048588,
1968,
1248,
2160,
1312);
INSERT INTO GD_GE
VALUES (1048589,
1048579,
1048579,
21);
INSERT INTO GD_SHP
VALUES (1048589,
1968,
1504,
2160,
1568);
|
-- Demonstration 2
-- Step 1: Open a new query window against the tempdb database
USE tempdb;
GO
-- Step 2: Create a table with a primary key specified
CREATE TABLE dbo.PhoneLog
( PhoneLogID int IDENTITY(1,1) PRIMARY KEY,
LogRecorded datetime2 NOT NULL,
PhoneNumberCalled nvarchar(100) NOT NULL,
CallDurationMs int NOT NULL
);
GO
-- Step 3: Query sys.indexes to view the structure
-- (note also the name chosen by SQL Server for the constraint and index)
-- In the GUI expand Databases, System Databases, tempdb, Tables, dbo.PhoneLog, and Indexes
-- Show that even though no clustered index was specified, one was created automatically
SELECT * FROM sys.indexes WHERE OBJECT_NAME(object_id) = N'PhoneLog';
GO
SELECT * FROM sys.key_constraints WHERE OBJECT_NAME(parent_object_id) = N'PhoneLog';
GO
-- Step 4: Insert some data into the table
SET NOCOUNT ON;
INSERT dbo.PhoneLog (LogRecorded, PhoneNumberCalled, CallDurationMs)
VALUES(SYSDATETIME(),'999-9999',CAST(RAND() * 1000 AS int))
GO 100000 --insert dummy data, 100,000 times
-- Step 5: Check the level of fragmentation via sys.dm_db_index_physical_stats
SELECT * FROM sys.dm_db_index_physical_stats(DB_ID(),OBJECT_ID('dbo.PhoneLog'),NULL,NULL,'DETAILED');
GO
-- Step 6: Note the avg_fragmentation_in_percent and avg_page_space_used_in_percent
-- Step 7: Modify the data in the table - this will increase data and cause page fragmentation
-- (note how much more quickly this command runs)
SET NOCOUNT ON;
DECLARE @Counter int = 0;
WHILE @Counter < 100000 BEGIN
UPDATE dbo.PhoneLog SET PhoneNumberCalled = REPLICATE('9',CAST(RAND() * 100 AS int))
WHERE PhoneLogID = @Counter % 100000;
IF @Counter % 100 = 0 PRINT @Counter;
SET @Counter += 1;
END;
GO
-- Step 8: Check the level of fragmentation via sys.dm_db_index_physical_stats
SELECT * FROM sys.dm_db_index_physical_stats(DB_ID(),OBJECT_ID('dbo.PhoneLog'),NULL,NULL,'DETAILED');
GO
-- Step 9: Note the avg_fragmentation_in_percent and avg_page_space_used_in_percent
-- Step 10: Rebuild the table and its indexes
ALTER INDEX ALL ON dbo.PhoneLog REBUILD;
GO
-- Step 11: Check the level of fragmentation via sys.dm_db_index_physical_stats
SELECT * FROM sys.dm_db_index_physical_stats(DB_ID(),OBJECT_ID('dbo.PhoneLog'),NULL,NULL,'DETAILED');
GO
-- Step 12: Note the avg_fragmentation_in_percent and avg_page_space_used_in_percent
-- Step 13: Run a query showing the execution plan (CTR+M)
SELECT [PhoneLogID]
,[LogRecorded]
,[PhoneNumberCalled]
,[CallDurationMs]
,p.Name
FROM [tempdb].[dbo].[PhoneLog] pl join [AdventureWorks].[Production].Product p
ON pl.CallDurationMs = p.ProductID
GO
-- Step 14: Create a covering index, point out the columns included
CREATE NONCLUSTERED INDEX NCIX_CallDurationMS
ON [dbo].[PhoneLog] ([CallDurationMs])
INCLUDE ([PhoneLogID],[LogRecorded],[PhoneNumberCalled])
GO
-- Step 15: Run the query showing the execution plan (CTR+M) - it now uses the new index
SELECT [PhoneLogID]
,[LogRecorded]
,[PhoneNumberCalled]
,[CallDurationMs]
,p.Name
FROM [tempdb].[dbo].[PhoneLog] pl join [AdventureWorks].[Production].Product p
ON pl.CallDurationMs = p.ProductID
GO
-- Step 16: Drop the table
DROP TABLE dbo.PhoneLog;
GO
|
<reponame>nmbazima/SQL-Scripts<filename>Training/20762/Allfiles/Labfiles/Lab15/Starter/Project/31 - Demonstration 3A.sql
-- Demonstration 3A
-- Step 1 - Open a new query window to the AdventureWorks database
USE AdventureWorks;
GO
ALTER TABLE Person.Address ADD SpatialLocation geography;
GO
UPDATE Person.Address SET SpatialLocation =
geography::STGeomFromText(CASE AddressID WHEN 1 THEN 'POINT (-74.05 40)'
WHEN 2 THEN 'POINT (-40 40)'
WHEN 3 THEN 'POINT (-73 40.5)'
END,4326);
GO
-- Step 2 - Which salesperson is closest to New York?
DECLARE @NewYork geography;
SET @NewYork = geography::STGeomFromText('POINT (-74.007339 40.726966)',4326);
SELECT c.ContactID,
c.FirstName,
c.LastName,
a.SpatialLocation.STDistance(@NewYork) / 1000 AS DistanceKms
FROM Person.Contact AS c
INNER JOIN Sales.SalesPerson AS sp
ON c.ContactID = sp.SalesPersonID
INNER JOIN HumanResources.EmployeeAddress AS ea
ON c.ContactID = ea.EmployeeID
INNER JOIN Person.Address AS a
ON ea.AddressID = a.AddressID
WHERE (a.SpatialLocation.STDistance(@NewYork) / 1000) < 500
ORDER BY DistanceKms;
GO
-- Step 3 - Which two salespeople live the closest together?
WITH SalesPersonLocation
AS ( SELECT c.ContactID,
c.FirstName,
c.LastName,
a.SpatialLocation
FROM Person.Contact AS c
INNER JOIN Sales.SalesPerson AS sp
ON c.ContactID = sp.SalesPersonID
INNER JOIN HumanResources.EmployeeAddress AS ea
ON sp.SalesPersonID = ea.EmployeeID
INNER JOIN Person.Address AS a
ON ea.AddressID = a.AddressID
)
SELECT TOP(1)
sp1.FirstName,
sp1.LastName,
sp2.FirstName,
sp2.LastName,
sp1.SpatialLocation.STDistance(sp2.SpatialLocation) / 1000
AS DistanceKms
FROM SalesPersonLocation AS sp1
CROSS JOIN SalesPersonLocation AS sp2
WHERE sp1.ContactID <> sp2.ContactID
ORDER BY DistanceKms;
GO
|
INSERT INTO cloudin.t_sys_user_role (seq_id, user_seq_id, role_seq_id) VALUES (1, 1, 1);
INSERT INTO cloudin.t_sys_user_role (seq_id, user_seq_id, role_seq_id) VALUES (2, 1, 2);
|
<gh_stars>1-10
CREATE STREAM BUS_RAW( \
key STRING KEY, \
VP STRING) \
WITH (KAFKA_TOPIC='bus_raw',FORMAT='KAFKA');
CREATE STREAM BUS WITH (KAFKA_TOPIC='bus_prepped',VALUE_FORMAT='JSON_SR', TIMESTAMP='TIME_INT') \
AS SELECT \
SPLIT(AS_VALUE(KEY), '/')[12] AS HEADSIGN, \
EXTRACTJSONFIELD(VP, '$.VP.desi') AS ROUTE_NUM, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.dir') AS INT) AS DIRECTION_ID, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.oper') AS INT) AS OPERATOR_ID, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.veh') AS INT) AS VEH_ID, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.tsi') AS BIGINT) AS TIME_INT, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.spd') AS DOUBLE) AS SPEED, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.hdg') AS INT) AS HEADING, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.lat') AS DOUBLE) AS LAT, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.long') AS DOUBLE) AS LONG, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.acc') AS DOUBLE) AS ACCEL, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.dl') AS INT) AS DEVIATION, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.odo') AS INT) AS ODOMETER, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.drst') AS INT) AS DOOR_STATUS, \
EXTRACTJSONFIELD(VP, '$.VP.start') AS START_TIME, \
EXTRACTJSONFIELD(VP, '$.VP.loc') AS LOC_SRC, \
CAST(EXTRACTJSONFIELD(VP, '$.VP.occu') AS INT) AS OCCUPANCY \
FROM BUS_RAW \
PARTITION BY NULL \
EMIT CHANGES;
CREATE STREAM BUS_SAFETY WITH (KAFKA_TOPIC='bus_safety',VALUE_FORMAT='JSON_SR', TIMESTAMP='TIME_INT') \
AS SELECT \
HEADSIGN, \
ROUTE_NUM, \
DIRECTION_ID, \
OPERATOR_ID, \
VEH_ID, \
TIME_INT, \
DEVIATION, \
START_TIME, \
CAST(LAT AS STRING)+', '+CAST(LONG AS STRING) AS LOC, \
CASE \
WHEN DOOR_STATUS=1 AND ABS(SPEED)>2.8 \
THEN 1 \
ELSE 0 \
END AS DOOR_OPEN_MOVING, \
CASE \
WHEN ABS(ACCEL)>5 \
THEN 1 \
ELSE 0 \
END AS HARSH_BRAKING, \
CASE \
WHEN ABS(SPEED)>13.89 \
THEN 1 \
ELSE 0 \
END AS SPEEDING \
FROM BUS \
WHERE LAT IS NOT NULL AND LONG IS NOT NULL \
EMIT CHANGES;
CREATE TABLE BUS_SAFETY_TABLE WITH (KAFKA_TOPIC='bus_safety_table',FORMAT='JSON_SR') \
AS SELECT \
LATEST_BY_OFFSET(HEADSIGN) AS HEADSIGN, \
LATEST_BY_OFFSET(ROUTE_NUM) AS ROUTE_NUM, \
LATEST_BY_OFFSET(DIRECTION_ID) AS DIRECTION_ID, \
OPERATOR_ID, \
VEH_ID, \
AVG(DEVIATION) AS AVERAGE_DEVIATION, \
LATEST_BY_OFFSET(START_TIME) AS START_TIME, \
SUM(DOOR_OPEN_MOVING) AS DOOR_OPEN_MOVING_T, \
SUM(HARSH_BRAKING) AS HARSH_BRAKING_T, \
SUM(SPEEDING) AS SPEEDING_T, \
COUNT(*) AS TRIP_T \
FROM BUS_SAFETY \
WINDOW SESSION (60 SECONDS, RETENTION 1 DAY, GRACE PERIOD 10 SECONDS) \
GROUP BY OPERATOR_ID, VEH_ID \
EMIT CHANGES;
|
<filename>tests/Platinum.Data.Tests/Sql/Multi2.sql
declare @a int;
declare @b int;
set @a = 1;
set @b = 2;
--//
begin
set nocount on;
select 5+@a A, getutcdate() Moment;
select 9+@b B
union all
select 13+@b B;
end;
/* eof */
|
INSERT INTO acl_class (id, class) VALUES
(1, 'za.org.grassroot.core.domain.Group'),
(2, 'za.org.grassroot.core.domain.Event')
;
|
select Weapon, author( "<NAME>" ), description( "Weapons available to the player" ), label( "Weapon" )
{
fist, description( "Bare hands" ), label( "Fist" );
chainsaw, description( "A la Chainsaw Massacre" ), label( "Chainsaw" );
pistol, description( "Simple pistol" ), label( "Pistol" ), default;
shotgun, description( "A single-barrel shotgun" ), label( "Shotgun" );
chaingun, description( "A machine gun" ), label( "Chaingun" );
rocketLauncher, description( "Portable rocket launcher" ), label( "Rocket launcher" );
plasmaGun, description( "Plasma gun" ), label( "Plasma gun" );
BFG9000, description( "*The* BFG 9000" ), label( "BFG 9000" );
}
bitfield Powerup, author( "<NAME>" ), description( "Powerup pickups" ), label( "Powerup" )
{
none, description( "Help me!" ), empty;
radiationSuit, description( "Makes the player immune to radiation for a limited time" ), label( "Radiation suit" );
partialInvisibility, description( "Makes the player almost invisible to enemies for a limited time" ), label( "Partial invisibility" );
invulnerability, description( "Makes the player invulnerable for a limited time" ), label( "Invulnerability" );
computerMap, description( "Gives the complete map of the level to the player" ), label( "Computer map" );
lightVisor, description( "Allows the player to see in the dark for a limited time" ), label( "Light visor" );
berserk, description( "Gives the player the ability to quickly kill enemies with his fists" ), label( "Berserk" );
all, value( radiationSuit | partialInvisibility | invulnerability | computerMap | lightVisor | berserk );
}
struct Position
{
f32 x, value( 0 );
f32 y, value( 0 );
f32 angle, value( 0 ), description( "The direction the player is looking at ( degrees )" );
}
struct Mariner, author( "<NAME>" ), description( "The player character" ), label( "Player" )
{
u32 health, value( 100 ), description( "The player's health" );
Weapon weapon, value( pistol ), description( "The player's current weapon" );
Powerup powerup, value( berserk ), description( "The player's powerups" );
i32[ 8 ] ammunition, value( { 0, 0, 20, -1, -1, -1, -1, -1 } ), description( "The ammunition of each weapon, -1 means the player doesn't have it" );
string name, value( "Mariner" ), description( "The player's name for multiplayer sessions" );
Position position, value( { x = 100, y = 120 } ), description( "The player's position" );
Position[] deaths, description( "Places the player has died in" );
u32{ string } completed, description( "Percent completed for each level indexed by level name" );
}
|
<filename>db/seeds.sql
INSERT INTO burgers (burger_name, devoured)
VALUES ('Burger a la Mode', 1),('Ruta-Bag-A Burger', 1),('Peas and Thank You Burger', 1),
('Bohemian Radishy', 0), ('Don''t you four cheddar ''bout me', 0);
|
/*
Let N be the number of CITY entries in STATION, and let N’ be the number of distinct CITY names in STATION; query the value of N - N’ from STATION. In other words, find the difference between the total number of CITY entries in the table and the number of distinct CITY entries in the table.
Input Format
The STATION table is described as follows:
STATION
Field Type
ID NUMBER
CITY VARCHAR2(21)
STATE VARCHAR2(2)
LAT_N NUMBER
LONG_W NUMBER
where LAT_N is the northern latitude and LONG_W is the western longitude.
*/
SELECT COUNT(CITY) - COUNT(DISTINCT CITY) FROM STATION;
|
<gh_stars>0
-- phpMyAdmin SQL Dump
-- version 4.8.5
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Waktu pembuatan: 14 Agu 2019 pada 08.40
-- Versi server: 10.1.40-MariaDB
-- Versi PHP: 7.1.29
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
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: `sk_scm`
--
-- --------------------------------------------------------
--
-- Struktur dari tabel `bank_account`
--
CREATE TABLE `bank_account` (
`id_account` int(11) NOT NULL,
`id_supplier` varchar(11) NOT NULL,
`nama_bank` varchar(30) NOT NULL,
`cabang` varchar(50) NOT NULL,
`pemilik_account` varchar(100) NOT NULL,
`no_rekening` varchar(20) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `bank_account`
--
INSERT INTO `bank_account` (`id_account`, `id_supplier`, `nama_bank`, `cabang`, `pemilik_account`, `no_rekening`) VALUES
(7, 'SP-00000001', 'BCA', 'Jembatan 5', 'Haviz Indra Maulana', '1791606298');
-- --------------------------------------------------------
--
-- Struktur dari tabel `category`
--
CREATE TABLE `category` (
`id_category` varchar(11) NOT NULL,
`nama_category` varchar(50) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `category`
--
INSERT INTO `category` (`id_category`, `nama_category`) VALUES
('CAT-0000001', 'Makanan'),
('CAT-0000002', 'Minuman'),
('CAT-0000003', 'Perlengkapan');
-- --------------------------------------------------------
--
-- Struktur dari tabel `group`
--
CREATE TABLE `group` (
`id_group` int(11) NOT NULL,
`nama_group` varchar(50) NOT NULL,
`lokasi_group` varchar(100) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `group`
--
INSERT INTO `group` (`id_group`, `nama_group`, `lokasi_group`) VALUES
(2, 'Area 1', 'DKI Jakarta'),
(5, 'Area 2', 'Depok');
-- --------------------------------------------------------
--
-- Struktur dari tabel `invoice`
--
CREATE TABLE `invoice` (
`no_invoice` varchar(11) NOT NULL,
`no_order` varchar(11) NOT NULL,
`status_invoice` enum('Open','Close') NOT NULL,
`tgl_invoice` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`tgl_tempo` date NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `invoice`
--
INSERT INTO `invoice` (`no_invoice`, `no_order`, `status_invoice`, `tgl_invoice`, `tgl_tempo`) VALUES
('INV-0000001', 'PO-00000001', 'Close', '2019-08-13 20:42:35', '2019-08-15');
-- --------------------------------------------------------
--
-- Struktur dari tabel `invoice_detail`
--
CREATE TABLE `invoice_detail` (
`no_invoice` varchar(11) NOT NULL,
`deskripsi` varchar(100) NOT NULL,
`harga` int(10) NOT NULL,
`qty` int(5) NOT NULL,
`ppn` int(10) NOT NULL,
`total_harga` int(10) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `invoice_detail`
--
INSERT INTO `invoice_detail` (`no_invoice`, `deskripsi`, `harga`, `qty`, `ppn`, `total_harga`) VALUES
('INV-0000001', 'Test 1', 200000, 1, 20000, 220000),
('INV-0000001', 'Test 2', 100000, 1, 10000, 110000);
-- --------------------------------------------------------
--
-- Struktur dari tabel `order`
--
CREATE TABLE `order` (
`no_order` varchar(11) NOT NULL,
`id_warehouse` varchar(11) NOT NULL,
`id_supplier` varchar(11) NOT NULL,
`status_order` enum('Open','Close') NOT NULL,
`tgl_order` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `order`
--
INSERT INTO `order` (`no_order`, `id_warehouse`, `id_supplier`, `status_order`, `tgl_order`) VALUES
('PO-00000001', 'WH-00000001', 'SP-00000001', 'Close', '2019-08-13 20:07:14'),
('PO-00000002', 'WH-00000001', 'SP-00000001', 'Close', '2019-08-13 20:06:35');
-- --------------------------------------------------------
--
-- Struktur dari tabel `order_detail`
--
CREATE TABLE `order_detail` (
`no_order` varchar(11) NOT NULL,
`id_product` varchar(11) NOT NULL,
`qty` int(5) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `order_detail`
--
INSERT INTO `order_detail` (`no_order`, `id_product`, `qty`) VALUES
('PO-00000001', 'PR-00000002', 2),
('PO-00000001', 'PR-00000001', 100),
('PO-00000002', 'PR-00000003', 2),
('PO-00000002', 'PR-00000002', 3),
('PO-00000002', 'PR-00000001', 100);
-- --------------------------------------------------------
--
-- Struktur dari tabel `payment`
--
CREATE TABLE `payment` (
`no_payment` varchar(11) NOT NULL,
`id_account` int(11) NOT NULL,
`tgl_payment` date NOT NULL,
`total_bayar` int(10) NOT NULL,
`status_payment` enum('Open','Close') NOT NULL,
`tgl_input_payment` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `payment`
--
INSERT INTO `payment` (`no_payment`, `id_account`, `tgl_payment`, `total_bayar`, `status_payment`, `tgl_input_payment`) VALUES
('PVC-0000001', 7, '2019-08-13', 220000, 'Close', '2019-08-14 05:41:45');
-- --------------------------------------------------------
--
-- Struktur dari tabel `payment_detail`
--
CREATE TABLE `payment_detail` (
`no_payment` varchar(11) NOT NULL,
`no_invoice` varchar(11) NOT NULL,
`jml_bayar` int(10) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `payment_detail`
--
INSERT INTO `payment_detail` (`no_payment`, `no_invoice`, `jml_bayar`) VALUES
('PVC-0000001', 'INV-0000001', 220000);
-- --------------------------------------------------------
--
-- Struktur dari tabel `pic`
--
CREATE TABLE `pic` (
`id_pic` int(11) NOT NULL,
`id_supplier` varchar(11) NOT NULL,
`nama_pic` varchar(50) NOT NULL,
`handphone` varchar(12) NOT NULL,
`email_pic` varchar(30) NOT NULL,
`username` varchar(30) NOT NULL,
`password` varchar(25) NOT NULL,
`token` varchar(20) NOT NULL,
`tgl_reg_pic` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `pic`
--
INSERT INTO `pic` (`id_pic`, `id_supplier`, `nama_pic`, `handphone`, `email_pic`, `username`, `password`, `token`, `tgl_reg_pic`) VALUES
(6, 'SP-00000001', 'Ndi', '081355754092', '<EMAIL>', '<PASSWORD>', '<PASSWORD>', '<PASSWORD>', '2019-08-13 16:45:48');
-- --------------------------------------------------------
--
-- Struktur dari tabel `product`
--
CREATE TABLE `product` (
`id_product` varchar(11) NOT NULL,
`id_supplier` varchar(11) NOT NULL,
`id_category` varchar(11) NOT NULL,
`satuan` varchar(10) NOT NULL,
`nama_product` varchar(100) NOT NULL,
`harga` int(10) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `product`
--
INSERT INTO `product` (`id_product`, `id_supplier`, `id_category`, `satuan`, `nama_product`, `harga`) VALUES
('PR-00000001', 'SP-00000001', 'CAT-0000002', 'Crat', 'Fanta', 2),
('PR-00000002', 'SP-00000001', 'CAT-0000002', 'Meter', 'Coba', 20000),
('PR-00000003', 'SP-00000001', 'CAT-0000002', 'Pcs', 'Lap Basah', 15000);
-- --------------------------------------------------------
--
-- Struktur dari tabel `shipping`
--
CREATE TABLE `shipping` (
`no_shipping` varchar(11) NOT NULL,
`no_order` varchar(11) NOT NULL,
`tgl_shipping` date NOT NULL,
`status_shipping` enum('Open','Close') NOT NULL,
`tgl_receive` date NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `shipping`
--
INSERT INTO `shipping` (`no_shipping`, `no_order`, `tgl_shipping`, `status_shipping`, `tgl_receive`) VALUES
('DO-00000001', 'PO-00000001', '2019-08-13', 'Close', '2019-08-13'),
('DO-00000002', 'PO-00000001', '2019-08-14', 'Close', '2019-08-14');
-- --------------------------------------------------------
--
-- Struktur dari tabel `shipping_detail`
--
CREATE TABLE `shipping_detail` (
`no_shipping` varchar(11) NOT NULL,
`id_product` varchar(11) NOT NULL,
`actual_qty` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `shipping_detail`
--
INSERT INTO `shipping_detail` (`no_shipping`, `id_product`, `actual_qty`) VALUES
('DO-00000002', 'PR-00000002', 2),
('DO-00000002', 'PR-00000001', 100);
-- --------------------------------------------------------
--
-- Struktur dari tabel `supplier`
--
CREATE TABLE `supplier` (
`id_supplier` varchar(11) NOT NULL,
`nama_supplier` varchar(50) NOT NULL,
`alamat` varchar(100) NOT NULL,
`telepon` varchar(12) NOT NULL,
`fax` varchar(12) NOT NULL,
`npwp` varchar(20) NOT NULL,
`email` varchar(30) NOT NULL,
`tgl_reg_supplier` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
`status_supplier` enum('Aktif','Nonaktif','','') NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `supplier`
--
INSERT INTO `supplier` (`id_supplier`, `nama_supplier`, `alamat`, `telepon`, `fax`, `npwp`, `email`, `tgl_reg_supplier`, `status_supplier`) VALUES
('SP-00000001', 'PT. AAA', 'Jakarta', '081355754092', '021 13758371', '13768137691', '<EMAIL>', '2019-08-13 04:38:03', 'Aktif');
-- --------------------------------------------------------
--
-- Struktur dari tabel `supply_group`
--
CREATE TABLE `supply_group` (
`id_group` int(11) NOT NULL,
`id_supplier` varchar(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `supply_group`
--
INSERT INTO `supply_group` (`id_group`, `id_supplier`) VALUES
(2, 'SP-00000001');
-- --------------------------------------------------------
--
-- Struktur dari tabel `user`
--
CREATE TABLE `user` (
`id_user` varchar(11) NOT NULL,
`nama_lengkap` varchar(30) NOT NULL,
`email` varchar(30) NOT NULL,
`telepon` varchar(12) NOT NULL,
`jenis_kelamin` enum('L','P','','') NOT NULL,
`alamat` varchar(100) NOT NULL,
`username` varchar(50) NOT NULL,
`password` varchar(25) NOT NULL,
`level` enum('Admin','Finance','Warehouse','','') NOT NULL,
`status` enum('Aktif','Nonaktif','','') NOT NULL,
`token` varchar(15) NOT NULL,
`tgl_reg_user` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `user`
--
INSERT INTO `user` (`id_user`, `nama_lengkap`, `email`, `telepon`, `jenis_kelamin`, `alamat`, `username`, `password`, `level`, `status`, `token`, `tgl_reg_user`) VALUES
('USR-0000001', 'Helpdesk - Administrator', '<EMAIL>', '081355754092', 'L', 'Jakarta', 'helpdesk', 'helpdesk', 'Admin', 'Aktif', '8<PASSWORD>', '2019-08-11 19:49:47'),
('USR-0000002', '<NAME>', '<EMAIL>', '081355754092', 'L', 'Jakarta', 'rudiubk', 'rudi', 'Warehouse', 'Aktif', '6f0f639126c5d9e', '2019-08-13 08:30:44'),
('USR-0000003', '<NAME>', '<EMAIL>', '081355754092', 'L', 'Jakarta', 'yugi', 'yugi', 'Finance', 'Aktif', '72c9b19f83c4468', '2019-08-12 01:20:10'),
('USR-0000004', '<NAME>', '<EMAIL>', '08135891385', 'P', 'Jakarta', 'ulfia', 'u3moa', 'Warehouse', 'Aktif', 'f3ff4c466a058ef', '2019-08-13 15:13:07');
-- --------------------------------------------------------
--
-- Struktur dari tabel `warehouse`
--
CREATE TABLE `warehouse` (
`id_warehouse` varchar(11) NOT NULL,
`id_group` int(11) NOT NULL,
`id_user` varchar(11) NOT NULL,
`nama_warehouse` varchar(50) NOT NULL,
`alamat` varchar(100) NOT NULL,
`telepon` varchar(12) NOT NULL,
`fax` varchar(12) NOT NULL,
`email` varchar(50) NOT NULL,
`tgl_reg_warehouse` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data untuk tabel `warehouse`
--
INSERT INTO `warehouse` (`id_warehouse`, `id_group`, `id_user`, `nama_warehouse`, `alamat`, `telepon`, `fax`, `email`, `tgl_reg_warehouse`) VALUES
('WH-00000001', 2, 'USR-0000002', 'Dominos Angke Jaya', 'Jl. Angke Jaya Raya', '081355754092', '021123123', '<EMAIL>', '2019-07-25 12:05:59'),
('WH-00000002', 5, 'USR-0000004', 'Dominos Pizza Depok', 'Depok', '081257832131', '138691378691', '<EMAIL>', '2019-08-13 15:14:20');
--
-- Indexes for dumped tables
--
--
-- Indeks untuk tabel `bank_account`
--
ALTER TABLE `bank_account`
ADD PRIMARY KEY (`id_account`),
ADD KEY `supplier` (`id_supplier`);
--
-- Indeks untuk tabel `category`
--
ALTER TABLE `category`
ADD PRIMARY KEY (`id_category`);
--
-- Indeks untuk tabel `group`
--
ALTER TABLE `group`
ADD PRIMARY KEY (`id_group`);
--
-- Indeks untuk tabel `invoice`
--
ALTER TABLE `invoice`
ADD PRIMARY KEY (`no_invoice`),
ADD KEY `order` (`no_order`);
--
-- Indeks untuk tabel `invoice_detail`
--
ALTER TABLE `invoice_detail`
ADD KEY `invoice` (`no_invoice`);
--
-- Indeks untuk tabel `order`
--
ALTER TABLE `order`
ADD PRIMARY KEY (`no_order`),
ADD KEY `warehouse` (`id_warehouse`),
ADD KEY `supplier` (`id_supplier`);
--
-- Indeks untuk tabel `order_detail`
--
ALTER TABLE `order_detail`
ADD KEY `order` (`no_order`),
ADD KEY `product` (`id_product`);
--
-- Indeks untuk tabel `payment`
--
ALTER TABLE `payment`
ADD PRIMARY KEY (`no_payment`),
ADD KEY `bank` (`id_account`),
ADD KEY `bank_2` (`id_account`);
--
-- Indeks untuk tabel `payment_detail`
--
ALTER TABLE `payment_detail`
ADD KEY `payment` (`no_payment`),
ADD KEY `invoice` (`no_invoice`);
--
-- Indeks untuk tabel `pic`
--
ALTER TABLE `pic`
ADD PRIMARY KEY (`id_pic`),
ADD KEY `supplier` (`id_supplier`);
--
-- Indeks untuk tabel `product`
--
ALTER TABLE `product`
ADD PRIMARY KEY (`id_product`),
ADD KEY `supplier` (`id_supplier`),
ADD KEY `category` (`id_category`);
--
-- Indeks untuk tabel `shipping`
--
ALTER TABLE `shipping`
ADD PRIMARY KEY (`no_shipping`),
ADD KEY `invoice` (`no_order`);
--
-- Indeks untuk tabel `shipping_detail`
--
ALTER TABLE `shipping_detail`
ADD KEY `no_shipping` (`no_shipping`),
ADD KEY `id_product` (`id_product`);
--
-- Indeks untuk tabel `supplier`
--
ALTER TABLE `supplier`
ADD PRIMARY KEY (`id_supplier`);
--
-- Indeks untuk tabel `supply_group`
--
ALTER TABLE `supply_group`
ADD KEY `supplier` (`id_supplier`),
ADD KEY `group` (`id_group`);
--
-- Indeks untuk tabel `user`
--
ALTER TABLE `user`
ADD PRIMARY KEY (`id_user`);
--
-- Indeks untuk tabel `warehouse`
--
ALTER TABLE `warehouse`
ADD PRIMARY KEY (`id_warehouse`),
ADD KEY `group` (`id_group`),
ADD KEY `user` (`id_user`);
--
-- AUTO_INCREMENT untuk tabel yang dibuang
--
--
-- AUTO_INCREMENT untuk tabel `bank_account`
--
ALTER TABLE `bank_account`
MODIFY `id_account` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=10;
--
-- AUTO_INCREMENT untuk tabel `group`
--
ALTER TABLE `group`
MODIFY `id_group` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6;
--
-- AUTO_INCREMENT untuk tabel `pic`
--
ALTER TABLE `pic`
MODIFY `id_pic` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=8;
--
-- Ketidakleluasaan untuk tabel pelimpahan (Dumped Tables)
--
--
-- Ketidakleluasaan untuk tabel `bank_account`
--
ALTER TABLE `bank_account`
ADD CONSTRAINT `bank_account_ibfk_1` FOREIGN KEY (`id_supplier`) REFERENCES `supplier` (`id_supplier`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `invoice`
--
ALTER TABLE `invoice`
ADD CONSTRAINT `invoice_ibfk_1` FOREIGN KEY (`no_order`) REFERENCES `order` (`no_order`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `invoice_detail`
--
ALTER TABLE `invoice_detail`
ADD CONSTRAINT `invoice_detail_ibfk_1` FOREIGN KEY (`no_invoice`) REFERENCES `invoice` (`no_invoice`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `order`
--
ALTER TABLE `order`
ADD CONSTRAINT `order_ibfk_1` FOREIGN KEY (`id_warehouse`) REFERENCES `warehouse` (`id_warehouse`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `order_ibfk_2` FOREIGN KEY (`id_supplier`) REFERENCES `supplier` (`id_supplier`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `order_detail`
--
ALTER TABLE `order_detail`
ADD CONSTRAINT `order_detail_ibfk_1` FOREIGN KEY (`no_order`) REFERENCES `order` (`no_order`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `order_detail_ibfk_2` FOREIGN KEY (`id_product`) REFERENCES `product` (`id_product`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `payment`
--
ALTER TABLE `payment`
ADD CONSTRAINT `payment_ibfk_1` FOREIGN KEY (`id_account`) REFERENCES `bank_account` (`id_account`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `payment_detail`
--
ALTER TABLE `payment_detail`
ADD CONSTRAINT `payment_detail_ibfk_1` FOREIGN KEY (`no_invoice`) REFERENCES `invoice` (`no_invoice`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `payment_detail_ibfk_2` FOREIGN KEY (`no_payment`) REFERENCES `payment` (`no_payment`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `pic`
--
ALTER TABLE `pic`
ADD CONSTRAINT `pic_ibfk_1` FOREIGN KEY (`id_supplier`) REFERENCES `supplier` (`id_supplier`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `product`
--
ALTER TABLE `product`
ADD CONSTRAINT `product_ibfk_1` FOREIGN KEY (`id_supplier`) REFERENCES `supplier` (`id_supplier`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `product_ibfk_2` FOREIGN KEY (`id_category`) REFERENCES `category` (`id_category`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `shipping`
--
ALTER TABLE `shipping`
ADD CONSTRAINT `shipping_ibfk_1` FOREIGN KEY (`no_order`) REFERENCES `order` (`no_order`);
--
-- Ketidakleluasaan untuk tabel `shipping_detail`
--
ALTER TABLE `shipping_detail`
ADD CONSTRAINT `Detail to Product` FOREIGN KEY (`id_product`) REFERENCES `product` (`id_product`) ON UPDATE CASCADE,
ADD CONSTRAINT `Detail to Shipping` FOREIGN KEY (`no_shipping`) REFERENCES `shipping` (`no_shipping`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `supply_group`
--
ALTER TABLE `supply_group`
ADD CONSTRAINT `supply_group_ibfk_1` FOREIGN KEY (`id_group`) REFERENCES `group` (`id_group`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `supply_group_ibfk_2` FOREIGN KEY (`id_supplier`) REFERENCES `supplier` (`id_supplier`) ON DELETE CASCADE ON UPDATE CASCADE;
--
-- Ketidakleluasaan untuk tabel `warehouse`
--
ALTER TABLE `warehouse`
ADD CONSTRAINT `warehouse_ibfk_1` FOREIGN KEY (`id_group`) REFERENCES `group` (`id_group`) ON DELETE CASCADE ON UPDATE CASCADE,
ADD CONSTRAINT `warehouse_ibfk_2` FOREIGN KEY (`id_user`) REFERENCES `user` (`id_user`) ON DELETE CASCADE ON UPDATE CASCADE;
COMMIT;
/*!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 */;
|
<reponame>mrjazz/spring-boot-store<filename>src/test/resources/db/data.sql
insert into MOVIES(id, title, category, year, "cast", director, story, price) values(21,'Full Metal Jacket','ACTION','1987','<NAME>, <NAME>, et al.','<NAME>','Bardzo ciekawy film. Jak wszystkie inne...',45);
insert into MOVIES(id, title, category, year, "cast", director, story, price) values(22,'American Pie 2','COMEDY','2001','<NAME>, <NAME>, et al.','<NAME> (II)','Bardzo ciekawy film. Jak wszystkie inne...',55);
insert into MOVIES(id, title, category, year, "cast", director, story, price) values(23,'Lost Highway','DRAMA','1997','<NAME>, <NAME>, et al.','<NAME>','Bardzo ciekawy film. Jak wszystkie inne...',65);
insert into MOVIES(id, title, category, year, "cast", director, story, price) values(24,'The Naked Gun','COMEDY','1988','<NAME>, <NAME>, et al.','<NAME>','Bardzo ciekawy film. Jak wszystkie inne...',50);
insert into MOVIES(id, title, category, year, "cast", director, story, price) values(25,'The Naked Gun 2 1/2 - The Smell of Fear','COMEDY','1991','<NAME>, <NAME>, et al.','<NAME>','Bardzo ciekawy film. Jak wszystkie inne...',65);
insert into MOVIES(id, title, category, year, "cast", director, story, price) values(6,'Armageddon','SCI-FI','1998','<NAME>, <NAME>, et al.','<NAME>','Bardzo ciekawy film. Jak wszystkie inne...',40);
|
<reponame>nurfan27/siakadubj<gh_stars>0
/*
SQLyog Ultimate v11.11 (64 bit)
MySQL - 5.5.16 : Database - db_siakad
*********************************************************************
*/
/*!40101 SET NAMES utf8 */;
/*!40101 SET SQL_MODE=''*/;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
CREATE DATABASE /*!32312 IF NOT EXISTS*/`db_siakad` /*!40100 DEFAULT CHARACTER SET latin1 */;
USE `db_siakad`;
/*Table structure for table `tbl_jabatan` */
DROP TABLE IF EXISTS `tbl_jabatan`;
CREATE TABLE `tbl_jabatan` (
`id_jabatan` int(11) NOT NULL AUTO_INCREMENT,
`jabatan` varchar(100) NOT NULL,
`lembaga_id` int(11) NOT NULL,
PRIMARY KEY (`id_jabatan`)
) ENGINE=MyISAM AUTO_INCREMENT=6 DEFAULT CHARSET=latin1;
/*Data for the table `tbl_jabatan` */
insert into `tbl_jabatan`(`id_jabatan`,`jabatan`,`lembaga_id`) values (1,'Superadmins',1),(4,'Operator',4);
/*Table structure for table `tbl_karyawan` */
DROP TABLE IF EXISTS `tbl_karyawan`;
CREATE TABLE `tbl_karyawan` (
`id_kary` int(11) NOT NULL AUTO_INCREMENT,
`nik` varchar(50) NOT NULL,
`nama` varchar(50) NOT NULL,
`jns_kel` varchar(2) NOT NULL,
`alamat` text NOT NULL,
`hp` varchar(30) NOT NULL,
`email` varchar(50) DEFAULT NULL,
`jabatan_id` int(11) NOT NULL,
`status` int(11) NOT NULL COMMENT '1 = aktif , 0 = tidak',
`pictures` varchar(255) DEFAULT NULL,
PRIMARY KEY (`nik`),
KEY `id_kary` (`id_kary`)
) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=latin1;
/*Data for the table `tbl_karyawan` */
insert into `tbl_karyawan`(`id_kary`,`nik`,`nama`,`jns_kel`,`alamat`,`hp`,`email`,`jabatan_id`,`status`,`pictures`) values (1,'201110225043','Superadmin','P','matramans','+6287781042439','<EMAIL>',1,1,NULL);
/*Table structure for table `tbl_lembaga` */
DROP TABLE IF EXISTS `tbl_lembaga`;
CREATE TABLE `tbl_lembaga` (
`id_lembaga` int(11) NOT NULL AUTO_INCREMENT,
`kode_lembaga` varchar(50) NOT NULL,
`lembaga` varchar(100) NOT NULL,
`telepon` varchar(20) DEFAULT NULL,
`alamat` text,
PRIMARY KEY (`kode_lembaga`),
KEY `id_lembaga` (`id_lembaga`)
) ENGINE=MyISAM AUTO_INCREMENT=8 DEFAULT CHARSET=latin1;
/*Data for the table `tbl_lembaga` */
insert into `tbl_lembaga`(`id_lembaga`,`kode_lembaga`,`lembaga`,`telepon`,`alamat`) values (1,'UBJ-BKS','Kampus Bekasi',NULL,NULL),(4,'UBJ-JKT','Kampus Jakarta',NULL,NULL);
/*Table structure for table `tbl_menu` */
DROP TABLE IF EXISTS `tbl_menu`;
CREATE TABLE `tbl_menu` (
`id_menu` int(11) NOT NULL AUTO_INCREMENT,
`menu` varchar(30) NOT NULL,
`url` varchar(100) NOT NULL,
`parent_menu` int(11) NOT NULL,
`icon` varchar(30) DEFAULT NULL,
PRIMARY KEY (`id_menu`)
) ENGINE=MyISAM AUTO_INCREMENT=39 DEFAULT CHARSET=latin1;
/*Data for the table `tbl_menu` */
insert into `tbl_menu`(`id_menu`,`menu`,`url`,`parent_menu`,`icon`) values (2,'Form','-',0,'icon-th-list '),(3,'Setting','-',0,'icon-cogs '),(4,'User Apps','setting/user',3,NULL),(5,'Role Menu','setting/role',3,NULL),(6,'Jabatan','data/jabatan',7,NULL),(7,'Data','-',0,'icon-folder-open '),(8,'Karyawan','data/karyawan',7,NULL),(25,'Master','-',0,'icon-book '),(9,'Report','#',0,'icon-list-alt'),(10,'Menu','setting/menu',3,NULL),(33,'Akademik','-',0,'icon-book '),(32,'Mahasiswa','#',7,''),(31,'Pengisian KRS / FRS','#',2,''),(18,'Lembaga','data/lembaga',7,NULL),(30,'Pendaftaran Mahasiswa Baru','#',2,''),(29,'Jurusan','#',25,''),(28,'Fakultas','master/fakultas',25,''),(34,'Mata Kuliah','#',33,''),(35,'Jadwal Perkuliahan','#',33,''),(36,'Tahun Ajaran','master/tahunajaran',25,''),(37,'Pengajuan Cuti','#',2,''),(38,'Hasil Studi','#',33,'');
/*Table structure for table `tbl_role_access` */
DROP TABLE IF EXISTS `tbl_role_access`;
CREATE TABLE `tbl_role_access` (
`id_role` int(11) NOT NULL AUTO_INCREMENT,
`menu_id` int(11) NOT NULL,
`lembaga_id` int(11) NOT NULL,
PRIMARY KEY (`id_role`)
) ENGINE=MyISAM AUTO_INCREMENT=275 DEFAULT CHARSET=latin1;
/*Data for the table `tbl_role_access` */
insert into `tbl_role_access`(`id_role`,`menu_id`,`lembaga_id`) values (273,9,1),(272,25,1),(271,7,1),(270,3,1),(269,2,1),(268,38,1),(267,35,1),(266,34,1),(265,36,1),(264,28,1),(263,29,1),(262,18,1),(261,32,1),(260,8,1),(259,6,1),(258,10,1),(257,5,1),(256,4,1),(274,33,1),(255,37,1),(254,30,1),(253,31,1);
/*Table structure for table `tbl_user_login` */
DROP TABLE IF EXISTS `tbl_user_login`;
CREATE TABLE `tbl_user_login` (
`id_user` int(11) NOT NULL AUTO_INCREMENT,
`username` varchar(50) NOT NULL,
`password` varchar(100) NOT NULL,
`password_plain` varchar(30) NOT NULL,
`nik` varchar(50) NOT NULL,
`status` int(11) NOT NULL COMMENT '1 = aktif , 0 = tidak',
PRIMARY KEY (`id_user`)
) ENGINE=MyISAM AUTO_INCREMENT=7 DEFAULT CHARSET=latin1;
/*Data for the table `tbl_user_login` */
insert into `tbl_user_login`(`id_user`,`username`,`password`,`password_plain`,`nik`,`status`) values (1,'admin','<PASSWORD>','123456','201110225043',1);
/*Table structure for table `view_role` */
DROP TABLE IF EXISTS `view_role`;
/*!50001 DROP VIEW IF EXISTS `view_role` */;
/*!50001 DROP TABLE IF EXISTS `view_role` */;
/*!50001 CREATE TABLE `view_role`(
`id_role` int(11) ,
`menu_id` int(11) ,
`lembaga_id` int(11) ,
`menu` varchar(30) ,
`id_menu` int(11) ,
`parent_menu` int(11)
)*/;
/*Table structure for table `view_user` */
DROP TABLE IF EXISTS `view_user`;
/*!50001 DROP VIEW IF EXISTS `view_user` */;
/*!50001 DROP TABLE IF EXISTS `view_user` */;
/*!50001 CREATE TABLE `view_user`(
`id_user` int(11) ,
`nik` varchar(50) ,
`password_plain` varchar(30) ,
`status` int(11) ,
`username` varchar(50) ,
`nama` varchar(50)
)*/;
/*View structure for view view_role */
/*!50001 DROP TABLE IF EXISTS `view_role` */;
/*!50001 DROP VIEW IF EXISTS `view_role` */;
/*!50001 CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `view_role` AS select `b`.`id_role` AS `id_role`,`b`.`menu_id` AS `menu_id`,`b`.`lembaga_id` AS `lembaga_id`,`a`.`menu` AS `menu`,`a`.`id_menu` AS `id_menu`,`a`.`parent_menu` AS `parent_menu` from ((`tbl_menu` `a` left join `tbl_role_access` `b` on((`a`.`id_menu` = `b`.`menu_id`))) left join `tbl_lembaga` `c` on((`b`.`lembaga_id` = `c`.`id_lembaga`))) */;
/*View structure for view view_user */
/*!50001 DROP TABLE IF EXISTS `view_user` */;
/*!50001 DROP VIEW IF EXISTS `view_user` */;
/*!50001 CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `view_user` AS select `a`.`id_user` AS `id_user`,`a`.`nik` AS `nik`,`a`.`password_plain` AS `password_plain`,`a`.`status` AS `status`,`a`.`username` AS `username`,`b`.`nama` AS `nama` from (((`tbl_user_login` `a` join `tbl_karyawan` `b` on((`a`.`nik` = `b`.`nik`))) join `tbl_jabatan` `c` on((`b`.`jabatan_id` = `c`.`id_jabatan`))) join `tbl_lembaga` `d` on((`c`.`lembaga_id` = `d`.`id_lembaga`))) */;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
|
ALTER TABLE "public"."patient_clinical_history" DROP COLUMN "facility";
|
<filename>sql_files/example.sql
SELECT *
FROM `bigquery-public-data.austin_waste.waste_and_diversion` LIMIT 100
|
<reponame>thebyronc/teamtracker
SET MODE PostgreSQL;
CREATE TABLE IF NOT EXISTS teams_two (
id int PRIMARY KEY auto_increment,
teamname VARCHAR,
description VARCHAR
);
CREATE TABLE IF NOT EXISTS members_three (
id int PRIMARY KEY auto_increment,
teamId int,
name VARCHAR,
email VARCHAR
);
|
<reponame>francois/elm-scoutges<gh_stars>0
-- Revert scoutges:extensions/que from pg
SET client_min_messages TO 'warning';
BEGIN;
ALTER TABLE que_jobs RESET (fillfactor);
ALTER TABLE que_jobs DROP CONSTRAINT que_jobs_pkey;
DROP INDEX que_poll_idx;
DROP INDEX que_jobs_data_gin_idx;
DROP TRIGGER que_job_notify ON que_jobs;
DROP FUNCTION que_job_notify();
DROP TRIGGER que_state_notify ON que_jobs;
DROP FUNCTION que_state_notify();
DROP FUNCTION que_determine_job_state(que_jobs);
DROP TABLE que_lockers;
DROP TABLE que_values;
DROP INDEX que_jobs_args_gin_idx;
ALTER TABLE que_jobs RENAME COLUMN id TO job_id;
ALTER SEQUENCE que_jobs_id_seq RENAME TO que_jobs_job_id_seq;
ALTER TABLE que_jobs RENAME COLUMN last_error_message TO last_error;
DELETE FROM que_jobs WHERE (finished_at IS NOT NULL OR expired_at IS NOT NULL);
ALTER TABLE que_jobs
DROP CONSTRAINT error_length,
DROP CONSTRAINT queue_length,
DROP CONSTRAINT job_class_length,
DROP CONSTRAINT valid_args,
DROP COLUMN finished_at,
DROP COLUMN expired_at,
ALTER args TYPE JSON using args::json;
UPDATE que_jobs
SET
queue = CASE queue WHEN 'default' THEN '' ELSE queue END,
last_error = last_error || coalesce(E'\n' || last_error_backtrace, '');
ALTER TABLE que_jobs
DROP COLUMN data,
DROP COLUMN last_error_backtrace,
ALTER COLUMN args SET NOT NULL,
ALTER COLUMN args SET DEFAULT '[]',
ALTER COLUMN queue SET DEFAULT '';
ALTER TABLE que_jobs
ADD PRIMARY KEY (queue, priority, run_at, job_id);
DROP FUNCTION que_validate_tags(jsonb);
ALTER TABLE que_jobs
DROP CONSTRAINT que_jobs_pkey,
DROP COLUMN queue,
ALTER COLUMN priority TYPE integer,
ADD CONSTRAINT que_jobs_pkey PRIMARY KEY (priority, run_at, job_id);
ALTER TABLE que_jobs ALTER COLUMN priority SET DEFAULT 1;
DROP TABLE que_jobs;
COMMIT;
|
CREATE OR REPLACE PROCEDURE Greatings
AS
BEGIN
dbms_output.put_line(' YOU INSIDE THE GREATING PROCEDURE ');
END ;
/
|
<reponame>boltonvandy/gerrymander<filename>State_Data/ri/riinsert.sql
BEGIN TRANSACTION;
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "101", "Barrington", "REP", 973.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "101", "Barrington", "DEM", 343.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "101", "Barrington", "OTH", 954.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "102", "Barrington", "REP", 1380.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "102", "Barrington", "DEM", 384.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "102", "Barrington", "OTH", 1182.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "103", "Barrington", "REP", 1004.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "103", "Barrington", "DEM", 345.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "103", "Barrington", "OTH", 886.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "104", "Barrington", "REP", 1246.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "104", "Barrington", "DEM", 413.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "104", "Barrington", "OTH", 1157.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "105", "Barrington", "REP", 1242.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "105", "Barrington", "DEM", 415.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "105", "Barrington", "OTH", 1198.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "201", "Bristol", "REP", 515.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "201", "Bristol", "DEM", 252.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "201", "Bristol", "OTH", 770.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "202", "Bristol", "REP", 436.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "202", "Bristol", "DEM", 115.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "202", "Bristol", "OTH", 374.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "203", "Bristol", "REP", 1135.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "203", "Bristol", "DEM", 404.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "203", "Bristol", "OTH", 1208.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "204", "Bristol", "REP", 821.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "204", "Bristol", "DEM", 256.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "204", "Bristol", "OTH", 930.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "205", "Bristol", "REP", 822.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "205", "Bristol", "DEM", 328.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "205", "Bristol", "OTH", 1222.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "206", "Bristol", "REP", 747.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "206", "Bristol", "DEM", 232.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "206", "Bristol", "OTH", 992.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "207", "Bristol", "REP", 480.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "207", "Bristol", "DEM", 137.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "207", "Bristol", "OTH", 488.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "208", "Bristol", "REP", 656.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "208", "Bristol", "DEM", 212.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "208", "Bristol", "OTH", 819.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "209", "Bristol", "REP", 184.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "209", "Bristol", "DEM", 42.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "209", "Bristol", "OTH", 189.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "301", "Burrillville", "REP", 599.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "301", "Burrillville", "DEM", 461.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "301", "Burrillville", "OTH", 977.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "302", "Burrillville", "REP", 511.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "302", "Burrillville", "DEM", 456.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "302", "Burrillville", "OTH", 977.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "303", "Burrillville", "REP", 703.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "303", "Burrillville", "DEM", 536.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "303", "Burrillville", "OTH", 1266.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "304", "Burrillville", "REP", 405.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "304", "Burrillville", "DEM", 313.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "304", "Burrillville", "OTH", 735.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "305", "Burrillville", "REP", 448.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "305", "Burrillville", "DEM", 359.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "305", "Burrillville", "OTH", 948.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "306", "Burrillville", "REP", 461.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "306", "Burrillville", "DEM", 396.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "306", "Burrillville", "OTH", 950.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "401", "Central Falls", "REP", 828.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "401", "Central Falls", "DEM", 95.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "401", "Central Falls", "OTH", 499.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "402", "Central Falls", "REP", 421.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "402", "Central Falls", "DEM", 37.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "402", "Central Falls", "OTH", 285.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "403", "Central Falls", "REP", 819.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "403", "Central Falls", "DEM", 98.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "403", "Central Falls", "OTH", 452.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "404", "Central Falls", "REP", 730.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "404", "Central Falls", "DEM", 54.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "404", "Central Falls", "OTH", 387.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "405", "Central Falls", "REP", 345.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "405", "Central Falls", "DEM", 41.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "405", "Central Falls", "OTH", 145.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "406", "Central Falls", "REP", 464.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "406", "Central Falls", "DEM", 69.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "406", "Central Falls", "OTH", 225.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "407", "Central Falls", "REP", 198.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "407", "Central Falls", "DEM", 20.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "407", "Central Falls", "OTH", 131.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "408", "Central Falls", "REP", 636.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "408", "Central Falls", "DEM", 61.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "408", "Central Falls", "OTH", 351.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "501", "Charlestown", "REP", 607.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "501", "Charlestown", "DEM", 335.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "501", "Charlestown", "OTH", 865.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "502", "Charlestown", "REP", 578.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "502", "Charlestown", "DEM", 346.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "502", "Charlestown", "OTH", 846.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "503", "Charlestown", "REP", 526.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "503", "Charlestown", "DEM", 368.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "503", "Charlestown", "OTH", 696.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "504", "Charlestown", "REP", 442.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "504", "Charlestown", "DEM", 275.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "504", "Charlestown", "OTH", 612.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "601", "Coventry", "REP", 403.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "601", "Coventry", "DEM", 299.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "601", "Coventry", "OTH", 843.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "602", "Coventry", "REP", 140.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "602", "Coventry", "DEM", 103.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "602", "Coventry", "OTH", 278.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "603", "Coventry", "REP", 638.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "603", "Coventry", "DEM", 435.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "603", "Coventry", "OTH", 1283.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "604", "Coventry", "REP", 442.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "604", "Coventry", "DEM", 256.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "604", "Coventry", "OTH", 859.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "605", "Coventry", "REP", 374.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "605", "Coventry", "DEM", 278.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "605", "Coventry", "OTH", 881.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "606", "Coventry", "REP", 214.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "606", "Coventry", "DEM", 180.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "606", "Coventry", "OTH", 513.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "607", "Coventry", "REP", 617.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "607", "Coventry", "DEM", 449.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "607", "Coventry", "OTH", 1094.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "608", "Coventry", "REP", 613.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "608", "Coventry", "DEM", 412.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "608", "Coventry", "OTH", 1093.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "609", "Coventry", "REP", 412.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "609", "Coventry", "DEM", 294.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "609", "Coventry", "OTH", 844.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "610", "Coventry", "REP", 333.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "610", "Coventry", "DEM", 172.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "610", "Coventry", "OTH", 563.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "611", "Coventry", "REP", 414.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "611", "Coventry", "DEM", 285.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "611", "Coventry", "OTH", 709.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "612", "Coventry", "REP", 480.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "612", "Coventry", "DEM", 256.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "612", "Coventry", "OTH", 891.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "613", "Coventry", "REP", 397.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "613", "Coventry", "DEM", 272.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "613", "Coventry", "OTH", 721.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "614", "Coventry", "REP", 241.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "614", "Coventry", "DEM", 132.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "614", "Coventry", "OTH", 298.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "615", "Coventry", "REP", 426.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "615", "Coventry", "DEM", 336.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "615", "Coventry", "OTH", 926.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "616", "Coventry", "REP", 492.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "616", "Coventry", "DEM", 353.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "616", "Coventry", "OTH", 1025.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "617", "Coventry", "REP", 319.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "617", "Coventry", "DEM", 315.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "617", "Coventry", "OTH", 723.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "618", "Coventry", "REP", 169.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "618", "Coventry", "DEM", 172.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "618", "Coventry", "OTH", 367.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "701", "Cranston", "REP", 1279.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "701", "Cranston", "DEM", 306.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "701", "Cranston", "OTH", 971.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "702", "Cranston", "REP", 1057.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "702", "Cranston", "DEM", 241.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "702", "Cranston", "OTH", 870.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "703", "Cranston", "REP", 525.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "703", "Cranston", "DEM", 233.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "703", "Cranston", "OTH", 690.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "704", "Cranston", "REP", 230.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "704", "Cranston", "DEM", 65.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "704", "Cranston", "OTH", 242.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "705", "Cranston", "REP", 212.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "705", "Cranston", "DEM", 85.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "705", "Cranston", "OTH", 273.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "706", "Cranston", "REP", 601.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "706", "Cranston", "DEM", 540.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "706", "Cranston", "OTH", 1298.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "707", "Cranston", "REP", 609.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "707", "Cranston", "DEM", 486.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "707", "Cranston", "OTH", 1169.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "708", "Cranston", "REP", 759.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "708", "Cranston", "DEM", 456.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "708", "Cranston", "OTH", 1341.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "709", "Cranston", "REP", 951.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "709", "Cranston", "DEM", 533.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "709", "Cranston", "OTH", 1623.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "710", "Cranston", "REP", 849.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "710", "Cranston", "DEM", 304.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "710", "Cranston", "OTH", 891.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "711", "Cranston", "REP", 627.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "711", "Cranston", "DEM", 391.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "711", "Cranston", "OTH", 1017.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "712", "Cranston", "REP", 694.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "712", "Cranston", "DEM", 400.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "712", "Cranston", "OTH", 1142.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "713", "Cranston", "REP", 694.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "713", "Cranston", "DEM", 379.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "713", "Cranston", "OTH", 1066.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "714", "Cranston", "REP", 240.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "714", "Cranston", "DEM", 75.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "714", "Cranston", "OTH", 271.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "715", "Cranston", "REP", 549.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "715", "Cranston", "DEM", 240.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "715", "Cranston", "OTH", 693.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "716", "Cranston", "REP", 715.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "716", "Cranston", "DEM", 337.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "716", "Cranston", "OTH", 1024.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "717", "Cranston", "REP", 410.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "717", "Cranston", "DEM", 113.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "717", "Cranston", "OTH", 332.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "718", "Cranston", "REP", 379.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "718", "Cranston", "DEM", 185.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "718", "Cranston", "OTH", 466.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "719", "Cranston", "REP", 609.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "719", "Cranston", "DEM", 302.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "719", "Cranston", "OTH", 943.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "720", "Cranston", "REP", 182.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "720", "Cranston", "DEM", 114.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "720", "Cranston", "OTH", 276.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "721", "Cranston", "REP", 961.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "721", "Cranston", "DEM", 301.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "721", "Cranston", "OTH", 1085.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "722", "Cranston", "REP", 559.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "722", "Cranston", "DEM", 197.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "722", "Cranston", "OTH", 591.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "723", "Cranston", "REP", 1564.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "723", "Cranston", "DEM", 242.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "723", "Cranston", "OTH", 933.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "724", "Cranston", "REP", 1089.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "724", "Cranston", "DEM", 175.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "724", "Cranston", "OTH", 620.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "725", "Cranston", "REP", 1458.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "725", "Cranston", "DEM", 317.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "725", "Cranston", "OTH", 1273.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "726", "Cranston", "REP", 821.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "726", "Cranston", "DEM", 232.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "726", "Cranston", "OTH", 770.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "727", "Cranston", "REP", 524.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "727", "Cranston", "DEM", 126.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "727", "Cranston", "OTH", 384.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "728", "Cranston", "REP", 26.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "728", "Cranston", "DEM", 7.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "728", "Cranston", "OTH", 15.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "730", "Cranston", "REP", 807.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "730", "Cranston", "DEM", 817.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "730", "Cranston", "OTH", 1637.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "731", "Cranston", "REP", 765.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "731", "Cranston", "DEM", 412.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "731", "Cranston", "OTH", 1265.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "801", "Cumberland", "REP", 616.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "801", "Cumberland", "DEM", 234.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "801", "Cumberland", "OTH", 700.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "802", "Cumberland", "REP", 778.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "802", "Cumberland", "DEM", 266.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "802", "Cumberland", "OTH", 865.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "803", "Cumberland", "REP", 935.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "803", "Cumberland", "DEM", 371.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "803", "Cumberland", "OTH", 1081.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "804", "Cumberland", "REP", 243.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "804", "Cumberland", "DEM", 125.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "804", "Cumberland", "OTH", 346.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "805", "Cumberland", "REP", 1038.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "805", "Cumberland", "DEM", 342.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "805", "Cumberland", "OTH", 1115.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "806", "Cumberland", "REP", 889.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "806", "Cumberland", "DEM", 312.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "806", "Cumberland", "OTH", 989.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "807", "Cumberland", "REP", 1068.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "807", "Cumberland", "DEM", 526.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "807", "Cumberland", "OTH", 1469.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "808", "Cumberland", "REP", 1041.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "808", "Cumberland", "DEM", 458.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "808", "Cumberland", "OTH", 1323.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "809", "Cumberland", "REP", 313.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "809", "Cumberland", "DEM", 151.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "809", "Cumberland", "OTH", 467.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "810", "Cumberland", "REP", 1001.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "810", "Cumberland", "DEM", 186.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "810", "Cumberland", "OTH", 836.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "811", "Cumberland", "REP", 1022.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "811", "Cumberland", "DEM", 291.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "811", "Cumberland", "OTH", 913.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "812", "Cumberland", "REP", 793.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "812", "Cumberland", "DEM", 252.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "812", "Cumberland", "OTH", 915.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "813", "Cumberland", "REP", 316.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "813", "Cumberland", "DEM", 152.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "813", "Cumberland", "OTH", 486.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "901", "East Greenwich", "REP", 191.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "901", "East Greenwich", "DEM", 105.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "901", "East Greenwich", "OTH", 290.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "902", "East Greenwich", "REP", 814.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "902", "East Greenwich", "DEM", 532.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "902", "East Greenwich", "OTH", 1191.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "903", "East Greenwich", "REP", 846.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "903", "East Greenwich", "DEM", 373.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "903", "East Greenwich", "OTH", 960.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "904", "East Greenwich", "REP", 849.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "904", "East Greenwich", "DEM", 476.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "904", "East Greenwich", "OTH", 1210.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "905", "East Greenwich", "REP", 849.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "905", "East Greenwich", "DEM", 565.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "905", "East Greenwich", "OTH", 1197.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1001", "East Providence", "REP", 1134.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1001", "East Providence", "DEM", 277.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1001", "East Providence", "OTH", 1027.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1002", "East Providence", "REP", 1029.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1002", "East Providence", "DEM", 196.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1002", "East Providence", "OTH", 820.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1003", "East Providence", "REP", 710.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1003", "East Providence", "DEM", 115.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1003", "East Providence", "OTH", 445.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1004", "East Providence", "REP", 1037.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1004", "East Providence", "DEM", 255.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1004", "East Providence", "OTH", 877.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1005", "East Providence", "REP", 845.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1005", "East Providence", "DEM", 208.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1005", "East Providence", "OTH", 703.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1006", "East Providence", "REP", 109.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1006", "East Providence", "DEM", 17.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1006", "East Providence", "OTH", 61.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1007", "East Providence", "REP", 147.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1007", "East Providence", "DEM", 24.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1007", "East Providence", "OTH", 121.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1008", "East Providence", "REP", 1452.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1008", "East Providence", "DEM", 270.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1008", "East Providence", "OTH", 1132.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1009", "East Providence", "REP", 1483.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1009", "East Providence", "DEM", 279.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1009", "East Providence", "OTH", 1139.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1010", "East Providence", "REP", 1469.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1010", "East Providence", "DEM", 266.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1010", "East Providence", "OTH", 1060.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1011", "East Providence", "REP", 1132.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1011", "East Providence", "DEM", 323.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1011", "East Providence", "OTH", 1002.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1012", "East Providence", "REP", 593.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1012", "East Providence", "DEM", 145.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1012", "East Providence", "OTH", 592.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1013", "East Providence", "REP", 980.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1013", "East Providence", "DEM", 238.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1013", "East Providence", "OTH", 924.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1014", "East Providence", "REP", 1034.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1014", "East Providence", "DEM", 288.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1014", "East Providence", "OTH", 955.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1015", "East Providence", "REP", 438.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1015", "East Providence", "DEM", 101.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1015", "East Providence", "OTH", 336.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1016", "East Providence", "REP", 496.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1016", "East Providence", "DEM", 146.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1016", "East Providence", "OTH", 629.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1017", "East Providence", "REP", 951.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1017", "East Providence", "DEM", 295.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1017", "East Providence", "OTH", 1036.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1018", "East Providence", "REP", 404.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1018", "East Providence", "DEM", 97.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1018", "East Providence", "OTH", 372.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1101", "Exeter", "REP", 454.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1101", "Exeter", "DEM", 286.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1101", "Exeter", "OTH", 775.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1102", "Exeter", "REP", 392.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1102", "Exeter", "DEM", 329.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1102", "Exeter", "OTH", 801.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1103", "Exeter", "REP", 538.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1103", "Exeter", "DEM", 428.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1103", "Exeter", "OTH", 1094.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1201", "Foster", "REP", 479.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1201", "Foster", "DEM", 447.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1201", "Foster", "OTH", 1033.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1202", "Foster", "REP", 373.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1202", "Foster", "DEM", 400.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1202", "Foster", "OTH", 902.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1301", "Glocester", "REP", 676.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1301", "Glocester", "DEM", 604.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1301", "Glocester", "OTH", 1532.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1302", "Glocester", "REP", 682.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1302", "Glocester", "DEM", 588.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1302", "Glocester", "OTH", 1601.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1303", "Glocester", "REP", 160.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1303", "Glocester", "DEM", 143.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1303", "Glocester", "OTH", 340.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1304", "Glocester", "REP", 499.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1304", "Glocester", "DEM", 332.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1304", "Glocester", "OTH", 920.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1401", "Hopkinton", "REP", 725.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1401", "Hopkinton", "DEM", 621.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1401", "Hopkinton", "OTH", 1409.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1402", "Hopkinton", "REP", 744.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1402", "Hopkinton", "DEM", 524.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1402", "Hopkinton", "OTH", 1220.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1403", "Hopkinton", "REP", 273.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1403", "Hopkinton", "DEM", 224.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1403", "Hopkinton", "OTH", 486.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1501", "Jamestown", "REP", 1085.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1501", "Jamestown", "DEM", 371.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1501", "Jamestown", "OTH", 843.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1502", "Jamestown", "REP", 1101.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1502", "Jamestown", "DEM", 310.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1502", "Jamestown", "OTH", 997.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1601", "Johnston", "REP", 761.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1601", "Johnston", "DEM", 230.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1601", "Johnston", "OTH", 662.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1602", "Johnston", "REP", 885.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1602", "Johnston", "DEM", 281.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1602", "Johnston", "OTH", 714.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1603", "Johnston", "REP", 988.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1603", "Johnston", "DEM", 287.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1603", "Johnston", "OTH", 870.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1604", "Johnston", "REP", 907.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1604", "Johnston", "DEM", 344.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1604", "Johnston", "OTH", 857.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1605", "Johnston", "REP", 759.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1605", "Johnston", "DEM", 306.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1605", "Johnston", "OTH", 764.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1606", "Johnston", "REP", 224.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1606", "Johnston", "DEM", 63.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1606", "Johnston", "OTH", 158.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1607", "Johnston", "REP", 257.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1607", "Johnston", "DEM", 86.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1607", "Johnston", "OTH", 229.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1608", "Johnston", "REP", 1073.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1608", "Johnston", "DEM", 347.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1608", "Johnston", "OTH", 1017.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1609", "Johnston", "REP", 825.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1609", "Johnston", "DEM", 235.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1609", "Johnston", "OTH", 614.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1610", "Johnston", "REP", 1126.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1610", "Johnston", "DEM", 360.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1610", "Johnston", "OTH", 1053.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1611", "Johnston", "REP", 670.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1611", "Johnston", "DEM", 171.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1611", "Johnston", "OTH", 503.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1612", "Johnston", "REP", 658.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1612", "Johnston", "DEM", 228.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1612", "Johnston", "OTH", 605.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1613", "Johnston", "REP", 627.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1613", "Johnston", "DEM", 278.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1613", "Johnston", "OTH", 674.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1701", "Lincoln", "REP", 873.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1701", "Lincoln", "DEM", 578.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1701", "Lincoln", "OTH", 1433.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1702", "Lincoln", "REP", 449.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1702", "Lincoln", "DEM", 194.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1702", "Lincoln", "OTH", 597.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1703", "Lincoln", "REP", 673.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1703", "Lincoln", "DEM", 280.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1703", "Lincoln", "OTH", 1000.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1704", "Lincoln", "REP", 886.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1704", "Lincoln", "DEM", 410.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1704", "Lincoln", "OTH", 1227.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1705", "Lincoln", "REP", 578.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1705", "Lincoln", "DEM", 265.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1705", "Lincoln", "OTH", 928.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1706", "Lincoln", "REP", 159.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1706", "Lincoln", "DEM", 100.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1706", "Lincoln", "OTH", 234.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1707", "Lincoln", "REP", 187.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1707", "Lincoln", "DEM", 126.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1707", "Lincoln", "OTH", 287.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1708", "Lincoln", "REP", 734.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1708", "Lincoln", "DEM", 353.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1708", "Lincoln", "OTH", 1065.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1709", "Lincoln", "REP", 269.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1709", "Lincoln", "DEM", 152.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1709", "Lincoln", "OTH", 422.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1710", "Lincoln", "REP", 296.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1710", "Lincoln", "DEM", 122.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1710", "Lincoln", "OTH", 415.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1711", "Lincoln", "REP", 359.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1711", "Lincoln", "DEM", 138.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1711", "Lincoln", "OTH", 459.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1801", "<NAME>", "REP", 1105.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1801", "Little Compton", "DEM", 581.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1801", "Little Compton", "OTH", 1420.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1901", "Middletown", "REP", 716.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1901", "Middletown", "DEM", 289.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1901", "Middletown", "OTH", 759.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1902", "Middletown", "REP", 804.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1902", "Middletown", "DEM", 301.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1902", "Middletown", "OTH", 894.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1903", "Middletown", "REP", 771.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1903", "Middletown", "DEM", 270.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1903", "Middletown", "OTH", 826.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1904", "Middletown", "REP", 1194.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1904", "Middletown", "DEM", 407.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1904", "Middletown", "OTH", 1329.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1905", "Middletown", "REP", 798.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1905", "Middletown", "DEM", 376.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "1905", "Middletown", "OTH", 942.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2001", "Narragansett", "REP", 120.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2001", "Narragansett", "DEM", 43.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2001", "Narragansett", "OTH", 123.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2002", "Narragansett", "REP", 1068.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2002", "Narragansett", "DEM", 395.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2002", "Narragansett", "OTH", 1282.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2003", "Narragansett", "REP", 1044.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2003", "Narragansett", "DEM", 421.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2003", "Narragansett", "OTH", 1266.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2004", "Narragansett", "REP", 1084.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2004", "Narragansett", "DEM", 474.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2004", "Narragansett", "OTH", 1272.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2005", "Narragansett", "REP", 932.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2005", "Narragansett", "DEM", 433.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2005", "Narragansett", "OTH", 1271.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2201", "New Shoreham", "REP", 577.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2201", "New Shoreham", "DEM", 153.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2201", "New Shoreham", "OTH", 406.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2101", "Newport", "REP", 639.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2101", "Newport", "DEM", 187.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2101", "Newport", "OTH", 622.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2102", "Newport", "REP", 1336.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2102", "Newport", "DEM", 285.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2102", "Newport", "OTH", 1019.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2103", "Newport", "REP", 441.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2103", "Newport", "DEM", 105.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2103", "Newport", "OTH", 329.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2104", "Newport", "REP", 343.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2104", "Newport", "DEM", 75.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2104", "Newport", "OTH", 225.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2105", "Newport", "REP", 941.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2105", "Newport", "DEM", 261.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2105", "Newport", "OTH", 696.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2106", "Newport", "REP", 1013.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2106", "Newport", "DEM", 368.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2106", "Newport", "OTH", 839.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2107", "Newport", "REP", 940.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2107", "Newport", "DEM", 323.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2107", "Newport", "OTH", 820.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2108", "Newport", "REP", 564.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2108", "Newport", "DEM", 115.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2108", "Newport", "OTH", 373.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2109", "Newport", "REP", 442.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2109", "Newport", "DEM", 39.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2109", "Newport", "OTH", 268.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2301", "North Kingstown", "REP", 574.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2301", "North Kingstown", "DEM", 355.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2301", "North Kingstown", "OTH", 954.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2302", "North Kingstown", "REP", 1119.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2302", "North Kingstown", "DEM", 495.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2302", "North Kingstown", "OTH", 1498.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2303", "North Kingstown", "REP", 873.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2303", "North Kingstown", "DEM", 503.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2303", "North Kingstown", "OTH", 1301.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2304", "North Kingstown", "REP", 841.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2304", "North Kingstown", "DEM", 448.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2304", "North Kingstown", "OTH", 1276.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2305", "North Kingstown", "REP", 469.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2305", "North Kingstown", "DEM", 305.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2305", "North Kingstown", "OTH", 764.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2306", "North Kingstown", "REP", 495.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2306", "North Kingstown", "DEM", 259.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2306", "North Kingstown", "OTH", 811.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2307", "North Kingstown", "REP", 1076.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2307", "North Kingstown", "DEM", 431.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2307", "North Kingstown", "OTH", 1260.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2308", "North Kingstown", "REP", 989.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2308", "North Kingstown", "DEM", 444.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2308", "North Kingstown", "OTH", 1379.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2309", "North Kingstown", "REP", 1081.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2309", "North Kingstown", "DEM", 470.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2309", "North Kingstown", "OTH", 1391.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2401", "North Providence", "REP", 617.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2401", "North Providence", "DEM", 129.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2401", "North Providence", "OTH", 426.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2402", "North Providence", "REP", 855.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2402", "North Providence", "DEM", 164.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2402", "North Providence", "OTH", 646.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2403", "North Providence", "REP", 859.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2403", "North Providence", "DEM", 188.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2403", "North Providence", "OTH", 588.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2404", "North Providence", "REP", 515.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2404", "North Providence", "DEM", 85.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2404", "North Providence", "OTH", 329.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2405", "North Providence", "REP", 631.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2405", "North Providence", "DEM", 122.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2405", "North Providence", "OTH", 451.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2406", "North Providence", "REP", 952.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2406", "North Providence", "DEM", 205.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2406", "North Providence", "OTH", 688.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2407", "North Providence", "REP", 933.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2407", "North Providence", "DEM", 192.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2407", "North Providence", "OTH", 629.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2408", "North Providence", "REP", 837.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2408", "North Providence", "DEM", 175.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2408", "North Providence", "OTH", 705.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2409", "North Providence", "REP", 497.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2409", "North Providence", "DEM", 91.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2409", "North Providence", "OTH", 333.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2410", "North Providence", "REP", 658.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2410", "North Providence", "DEM", 142.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2410", "North Providence", "OTH", 468.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2411", "North Providence", "REP", 900.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2411", "North Providence", "DEM", 176.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2411", "North Providence", "OTH", 593.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2412", "North Providence", "REP", 980.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2412", "North Providence", "DEM", 178.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2412", "North Providence", "OTH", 691.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2413", "North Providence", "REP", 565.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2413", "North Providence", "DEM", 107.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2413", "North Providence", "OTH", 358.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2414", "North Providence", "REP", 477.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2414", "North Providence", "DEM", 87.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2414", "North Providence", "OTH", 354.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2415", "North Providence", "REP", 705.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2415", "North Providence", "DEM", 100.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2415", "North Providence", "OTH", 423.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2416", "North Providence", "REP", 1315.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2416", "North Providence", "DEM", 226.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2416", "North Providence", "OTH", 873.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2501", "North Smithfield", "REP", 591.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2501", "North Smithfield", "DEM", 434.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2501", "North Smithfield", "OTH", 1136.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2502", "North Smithfield", "REP", 590.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2502", "North Smithfield", "DEM", 465.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2502", "North Smithfield", "OTH", 1196.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2503", "North Smithfield", "REP", 562.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2503", "North Smithfield", "DEM", 352.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2503", "North Smithfield", "OTH", 967.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2504", "North Smithfield", "REP", 583.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2504", "North Smithfield", "DEM", 348.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2504", "North Smithfield", "OTH", 853.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2505", "North Smithfield", "REP", 355.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2505", "North Smithfield", "DEM", 215.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2505", "North Smithfield", "OTH", 499.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2601", "Pawtucket", "REP", 350.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2601", "Pawtucket", "DEM", 32.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2601", "Pawtucket", "OTH", 207.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2602", "Pawtucket", "REP", 831.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2602", "Pawtucket", "DEM", 58.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2602", "Pawtucket", "OTH", 480.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2603", "Pawtucket", "REP", 1472.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2603", "Pawtucket", "DEM", 198.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2603", "Pawtucket", "OTH", 917.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2604", "Pawtucket", "REP", 721.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2604", "Pawtucket", "DEM", 114.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2604", "Pawtucket", "OTH", 398.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2605", "Pawtucket", "REP", 616.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2605", "Pawtucket", "DEM", 57.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2605", "Pawtucket", "OTH", 360.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2606", "Pawtucket", "REP", 793.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2606", "Pawtucket", "DEM", 66.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2606", "Pawtucket", "OTH", 435.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2607", "Pawtucket", "REP", 1638.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2607", "Pawtucket", "DEM", 112.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2607", "Pawtucket", "OTH", 819.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2608", "Pawtucket", "REP", 1378.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2608", "Pawtucket", "DEM", 154.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2608", "Pawtucket", "OTH", 696.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2609", "Pawtucket", "REP", 210.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2609", "Pawtucket", "DEM", 29.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2609", "Pawtucket", "OTH", 121.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2610", "Pawtucket", "REP", 166.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2610", "Pawtucket", "DEM", 16.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2610", "Pawtucket", "OTH", 110.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2611", "Pawtucket", "REP", 707.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2611", "Pawtucket", "DEM", 85.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2611", "Pawtucket", "OTH", 391.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2612", "Pawtucket", "REP", 862.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2612", "Pawtucket", "DEM", 172.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2612", "Pawtucket", "OTH", 672.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2613", "Pawtucket", "REP", 1238.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2613", "Pawtucket", "DEM", 164.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2613", "Pawtucket", "OTH", 814.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2614", "Pawtucket", "REP", 1091.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2614", "Pawtucket", "DEM", 116.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2614", "Pawtucket", "OTH", 655.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2615", "Pawtucket", "REP", 443.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2615", "Pawtucket", "DEM", 44.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2615", "Pawtucket", "OTH", 261.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2616", "Pawtucket", "REP", 201.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2616", "Pawtucket", "DEM", 38.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2616", "Pawtucket", "OTH", 123.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2617", "Pawtucket", "REP", 263.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2617", "Pawtucket", "DEM", 30.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2617", "Pawtucket", "OTH", 182.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2618", "Pawtucket", "REP", 1373.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2618", "Pawtucket", "DEM", 274.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2618", "Pawtucket", "OTH", 1056.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2619", "Pawtucket", "REP", 709.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2619", "Pawtucket", "DEM", 132.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2619", "Pawtucket", "OTH", 539.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2620", "Pawtucket", "REP", 1454.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2620", "Pawtucket", "DEM", 257.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2620", "Pawtucket", "OTH", 1071.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2621", "Pawtucket", "REP", 359.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2621", "Pawtucket", "DEM", 79.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2621", "Pawtucket", "OTH", 297.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2622", "Pawtucket", "REP", 217.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2622", "Pawtucket", "DEM", 46.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2622", "Pawtucket", "OTH", 182.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2623", "Pawtucket", "REP", 337.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2623", "Pawtucket", "DEM", 54.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2623", "Pawtucket", "OTH", 289.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2624", "Pawtucket", "REP", 313.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2624", "Pawtucket", "DEM", 70.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2624", "Pawtucket", "OTH", 245.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2625", "Pawtucket", "REP", 389.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2625", "Pawtucket", "DEM", 59.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2625", "Pawtucket", "OTH", 252.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2626", "Pawtucket", "REP", 211.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2626", "Pawtucket", "DEM", 20.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2626", "Pawtucket", "OTH", 109.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2627", "Pawtucket", "REP", 866.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2627", "Pawtucket", "DEM", 136.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2627", "Pawtucket", "OTH", 569.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2628", "Pawtucket", "REP", 1076.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2628", "Pawtucket", "DEM", 235.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2628", "Pawtucket", "OTH", 817.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2629", "Pawtucket", "REP", 1533.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2629", "Pawtucket", "DEM", 282.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2629", "Pawtucket", "OTH", 1185.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2630", "Pawtucket", "REP", 107.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2630", "Pawtucket", "DEM", 24.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2630", "Pawtucket", "OTH", 78.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2631", "Pawtucket", "REP", 678.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2631", "Pawtucket", "DEM", 56.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2631", "Pawtucket", "OTH", 350.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2701", "Portsmouth", "REP", 55.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2701", "Portsmouth", "DEM", 29.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2701", "Portsmouth", "OTH", 78.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2702", "Portsmouth", "REP", 131.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2702", "Portsmouth", "DEM", 88.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2702", "Portsmouth", "OTH", 169.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2703", "Portsmouth", "REP", 804.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2703", "Portsmouth", "DEM", 334.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2703", "Portsmouth", "OTH", 996.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2704", "Portsmouth", "REP", 1064.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2704", "Portsmouth", "DEM", 563.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2704", "Portsmouth", "OTH", 1371.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2705", "Portsmouth", "REP", 362.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2705", "Portsmouth", "DEM", 247.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2705", "Portsmouth", "OTH", 452.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2706", "Portsmouth", "REP", 362.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2706", "Portsmouth", "DEM", 202.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2706", "Portsmouth", "OTH", 389.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2707", "Portsmouth", "REP", 1011.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2707", "Portsmouth", "DEM", 570.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2707", "Portsmouth", "OTH", 1326.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2708", "Portsmouth", "REP", 1079.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2708", "Portsmouth", "DEM", 574.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2708", "Portsmouth", "OTH", 1346.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2801", "Providence", "REP", 141.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2801", "Providence", "DEM", 19.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2801", "Providence", "OTH", 46.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2802", "Providence", "REP", 286.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2802", "Providence", "DEM", 28.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2802", "Providence", "OTH", 154.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2803", "Providence", "REP", 1363.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2803", "Providence", "DEM", 96.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2803", "Providence", "OTH", 648.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2804", "Providence", "REP", 1376.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2804", "Providence", "DEM", 75.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2804", "Providence", "OTH", 751.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2805", "Providence", "REP", 1539.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2805", "Providence", "DEM", 118.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2805", "Providence", "OTH", 686.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2806", "Providence", "REP", 111.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2806", "Providence", "DEM", 13.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2806", "Providence", "OTH", 63.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2807", "Providence", "OTH", 2.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2808", "Providence", "REP", 1164.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2808", "Providence", "DEM", 92.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2808", "Providence", "OTH", 520.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2809", "Providence", "REP", 1509.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2809", "Providence", "DEM", 81.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2809", "Providence", "OTH", 546.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2810", "Providence", "REP", 80.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2810", "Providence", "DEM", 6.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2810", "Providence", "OTH", 32.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2811", "Providence", "REP", 1174.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2811", "Providence", "DEM", 82.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2811", "Providence", "OTH", 653.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2812", "Providence", "REP", 1212.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2812", "Providence", "DEM", 111.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2812", "Providence", "OTH", 691.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2813", "Providence", "REP", 903.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2813", "Providence", "DEM", 73.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2813", "Providence", "OTH", 524.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2814", "Providence", "REP", 598.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2814", "Providence", "DEM", 65.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2814", "Providence", "OTH", 330.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2815", "Providence", "REP", 843.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2815", "Providence", "DEM", 115.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2815", "Providence", "OTH", 553.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2816", "Providence", "REP", 1769.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2816", "Providence", "DEM", 133.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2816", "Providence", "OTH", 714.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2817", "Providence", "REP", 1858.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2817", "Providence", "DEM", 127.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2817", "Providence", "OTH", 740.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2818", "Providence", "REP", 1405.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2818", "Providence", "DEM", 100.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2818", "Providence", "OTH", 604.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2819", "Providence", "REP", 1450.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2819", "Providence", "DEM", 179.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2819", "Providence", "OTH", 726.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2820", "Providence", "REP", 198.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2820", "Providence", "DEM", 17.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2820", "Providence", "OTH", 87.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2821", "Providence", "REP", 1076.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2821", "Providence", "DEM", 102.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2821", "Providence", "OTH", 591.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2822", "Providence", "REP", 369.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2822", "Providence", "DEM", 21.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2822", "Providence", "OTH", 202.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2823", "Providence", "REP", 1672.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2823", "Providence", "DEM", 138.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2823", "Providence", "OTH", 830.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2824", "Providence", "REP", 1749.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2824", "Providence", "DEM", 134.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2824", "Providence", "OTH", 848.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2825", "Providence", "REP", 284.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2825", "Providence", "DEM", 34.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2825", "Providence", "OTH", 173.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2826", "Providence", "REP", 1455.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2826", "Providence", "DEM", 95.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2826", "Providence", "OTH", 676.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2827", "Providence", "REP", 1627.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2827", "Providence", "DEM", 104.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2827", "Providence", "OTH", 640.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2828", "Providence", "REP", 1039.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2828", "Providence", "DEM", 76.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2828", "Providence", "OTH", 551.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2829", "Providence", "REP", 1210.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2829", "Providence", "DEM", 61.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2829", "Providence", "OTH", 388.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2830", "Providence", "REP", 93.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2830", "Providence", "DEM", 9.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2830", "Providence", "OTH", 33.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2831", "Providence", "REP", 1152.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2831", "Providence", "DEM", 58.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2831", "Providence", "OTH", 460.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2832", "Providence", "REP", 1573.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2832", "Providence", "DEM", 104.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2832", "Providence", "OTH", 675.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2833", "Providence", "REP", 725.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2833", "Providence", "DEM", 44.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2833", "Providence", "OTH", 350.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2834", "Providence", "REP", 353.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2834", "Providence", "DEM", 24.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2834", "Providence", "OTH", 142.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2835", "Providence", "REP", 226.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2835", "Providence", "DEM", 36.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2835", "Providence", "OTH", 140.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2836", "Providence", "REP", 18.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2836", "Providence", "DEM", 8.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2836", "Providence", "OTH", 18.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2837", "Providence", "REP", 508.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2837", "Providence", "DEM", 74.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2837", "Providence", "OTH", 278.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2838", "Providence", "REP", 321.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2838", "Providence", "DEM", 35.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2838", "Providence", "OTH", 134.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2839", "Providence", "REP", 573.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2839", "Providence", "DEM", 67.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2839", "Providence", "OTH", 267.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2840", "Providence", "REP", 450.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2840", "Providence", "DEM", 31.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2840", "Providence", "OTH", 161.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2841", "Providence", "REP", 451.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2841", "Providence", "DEM", 35.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2841", "Providence", "OTH", 287.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2842", "Providence", "REP", 185.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2842", "Providence", "DEM", 28.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2842", "Providence", "OTH", 118.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2843", "Providence", "REP", 231.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2843", "Providence", "DEM", 28.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2843", "Providence", "OTH", 133.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2844", "Providence", "REP", 1070.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2844", "Providence", "DEM", 336.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2844", "Providence", "OTH", 830.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2845", "Providence", "REP", 499.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2845", "Providence", "DEM", 70.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2845", "Providence", "OTH", 260.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2846", "Providence", "REP", 632.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2846", "Providence", "DEM", 82.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2846", "Providence", "OTH", 362.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2847", "Providence", "REP", 489.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2847", "Providence", "DEM", 45.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2847", "Providence", "OTH", 336.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2848", "Providence", "REP", 193.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2848", "Providence", "DEM", 28.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2848", "Providence", "OTH", 110.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2849", "Providence", "REP", 1093.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2849", "Providence", "DEM", 109.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2849", "Providence", "OTH", 560.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2850", "Providence", "REP", 640.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2850", "Providence", "DEM", 66.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2850", "Providence", "OTH", 333.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2851", "Providence", "REP", 770.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2851", "Providence", "DEM", 88.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2851", "Providence", "OTH", 445.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2852", "Providence", "REP", 301.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2852", "Providence", "DEM", 30.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2852", "Providence", "OTH", 182.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2853", "Providence", "REP", 230.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2853", "Providence", "DEM", 39.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2853", "Providence", "OTH", 146.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2854", "Providence", "REP", 1843.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2854", "Providence", "DEM", 150.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2854", "Providence", "OTH", 811.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2855", "Providence", "REP", 1733.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2855", "Providence", "DEM", 177.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2855", "Providence", "OTH", 935.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2856", "Providence", "REP", 82.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2856", "Providence", "DEM", 8.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2856", "Providence", "OTH", 43.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2857", "Providence", "REP", 154.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2857", "Providence", "DEM", 10.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2857", "Providence", "OTH", 80.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2858", "Providence", "REP", 407.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2858", "Providence", "DEM", 41.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2858", "Providence", "OTH", 267.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2859", "Providence", "REP", 253.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2859", "Providence", "DEM", 31.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2859", "Providence", "OTH", 121.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2860", "Providence", "REP", 180.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2860", "Providence", "DEM", 22.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2860", "Providence", "OTH", 109.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2861", "Providence", "REP", 1398.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2861", "Providence", "DEM", 89.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2861", "Providence", "OTH", 668.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2862", "Providence", "REP", 1389.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2862", "Providence", "DEM", 115.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2862", "Providence", "OTH", 572.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2863", "Providence", "REP", 838.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2863", "Providence", "DEM", 75.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2863", "Providence", "OTH", 433.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2864", "Providence", "REP", 396.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2864", "Providence", "DEM", 37.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2864", "Providence", "OTH", 168.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2865", "Providence", "REP", 303.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2865", "Providence", "DEM", 13.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2865", "Providence", "OTH", 158.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2866", "Providence", "REP", 916.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2866", "Providence", "DEM", 45.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2866", "Providence", "OTH", 305.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2867", "Providence", "REP", 146.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2867", "Providence", "DEM", 16.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2867", "Providence", "OTH", 96.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2868", "Providence", "REP", 1065.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2868", "Providence", "DEM", 59.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2868", "Providence", "OTH", 448.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2869", "Providence", "REP", 161.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2869", "Providence", "DEM", 18.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2869", "Providence", "OTH", 121.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2870", "Providence", "REP", 1000.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2870", "Providence", "DEM", 80.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2870", "Providence", "OTH", 424.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2871", "Providence", "REP", 561.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2871", "Providence", "DEM", 45.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2871", "Providence", "OTH", 255.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2872", "Providence", "REP", 62.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2872", "Providence", "DEM", 6.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2872", "Providence", "OTH", 25.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2873", "Providence", "REP", 170.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2873", "Providence", "DEM", 18.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2873", "Providence", "OTH", 101.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2874", "Providence", "REP", 1225.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2874", "Providence", "DEM", 127.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2874", "Providence", "OTH", 620.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2875", "Providence", "REP", 1366.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2875", "Providence", "DEM", 141.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2875", "Providence", "OTH", 694.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2876", "Providence", "REP", 862.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2876", "Providence", "DEM", 72.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2876", "Providence", "OTH", 361.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2877", "Providence", "REP", 403.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2877", "Providence", "DEM", 50.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2877", "Providence", "OTH", 248.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2878", "Providence", "REP", 79.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2878", "Providence", "DEM", 8.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2878", "Providence", "OTH", 31.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2879", "Providence", "REP", 1001.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2879", "Providence", "DEM", 65.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2879", "Providence", "OTH", 453.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2880", "Providence", "REP", 781.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2880", "Providence", "DEM", 33.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2880", "Providence", "OTH", 325.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2901", "Richmond", "REP", 905.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2901", "Richmond", "DEM", 627.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2901", "Richmond", "OTH", 1556.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2902", "Richmond", "REP", 874.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2902", "Richmond", "DEM", 686.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "2902", "Richmond", "OTH", 1558.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3001", "Scituate", "REP", 622.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3001", "Scituate", "DEM", 701.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3001", "Scituate", "OTH", 1447.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3002", "Scituate", "REP", 639.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3002", "Scituate", "DEM", 719.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3002", "Scituate", "OTH", 1523.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3003", "Scituate", "REP", 595.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3003", "Scituate", "DEM", 650.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3003", "Scituate", "OTH", 1521.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3101", "Smithfield", "REP", 803.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3101", "Smithfield", "DEM", 452.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3101", "Smithfield", "OTH", 1300.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3102", "Smithfield", "REP", 787.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3102", "Smithfield", "DEM", 367.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3102", "Smithfield", "OTH", 1194.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3103", "Smithfield", "REP", 777.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3103", "Smithfield", "DEM", 343.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3103", "Smithfield", "OTH", 1191.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3104", "Smithfield", "REP", 818.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3104", "Smithfield", "DEM", 430.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3104", "Smithfield", "OTH", 1400.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3105", "Smithfield", "REP", 812.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3105", "Smithfield", "DEM", 356.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3105", "Smithfield", "OTH", 1300.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3106", "Smithfield", "REP", 749.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3106", "Smithfield", "DEM", 383.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3106", "Smithfield", "OTH", 1117.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3201", "South Kingstown", "REP", 306.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3201", "South Kingstown", "DEM", 135.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3201", "South Kingstown", "OTH", 426.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3202", "South Kingstown", "REP", 965.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3202", "South Kingstown", "DEM", 292.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3202", "South Kingstown", "OTH", 903.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3203", "South Kingstown", "REP", 962.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3203", "South Kingstown", "DEM", 324.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3203", "South Kingstown", "OTH", 970.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3204", "South Kingstown", "REP", 1104.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3204", "South Kingstown", "DEM", 224.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3204", "South Kingstown", "OTH", 907.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3205", "South Kingstown", "REP", 1150.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3205", "South Kingstown", "DEM", 220.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3205", "South Kingstown", "OTH", 1047.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3206", "South Kingstown", "REP", 716.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3206", "South Kingstown", "DEM", 273.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3206", "South Kingstown", "OTH", 890.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3207", "South Kingstown", "REP", 1193.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3207", "South Kingstown", "DEM", 297.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3207", "South Kingstown", "OTH", 1200.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3208", "South Kingstown", "REP", 1163.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3208", "South Kingstown", "DEM", 430.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3208", "South Kingstown", "OTH", 1335.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3209", "South Kingstown", "REP", 486.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3209", "South Kingstown", "DEM", 172.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3209", "South Kingstown", "OTH", 543.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3210", "South Kingstown", "REP", 754.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3210", "South Kingstown", "DEM", 275.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3210", "South Kingstown", "OTH", 782.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3301", "Tiverton", "REP", 821.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3301", "Tiverton", "DEM", 407.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3301", "Tiverton", "OTH", 1096.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3302", "Tiverton", "REP", 909.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3302", "Tiverton", "DEM", 461.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3302", "Tiverton", "OTH", 1123.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3303", "Tiverton", "REP", 523.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3303", "Tiverton", "DEM", 251.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3303", "Tiverton", "OTH", 591.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3304", "Tiverton", "REP", 588.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3304", "Tiverton", "DEM", 314.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3304", "Tiverton", "OTH", 770.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3305", "Tiverton", "REP", 156.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3305", "Tiverton", "DEM", 69.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3305", "Tiverton", "OTH", 210.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3306", "Tiverton", "REP", 770.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3306", "Tiverton", "DEM", 430.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3306", "Tiverton", "OTH", 1276.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3307", "Tiverton", "REP", 578.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3307", "Tiverton", "DEM", 301.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3307", "Tiverton", "OTH", 706.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3401", "Warren", "REP", 889.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3401", "Warren", "DEM", 265.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3401", "Warren", "OTH", 1028.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3402", "Warren", "REP", 960.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3402", "Warren", "DEM", 376.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3402", "Warren", "OTH", 1303.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3403", "Warren", "REP", 1179.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3403", "Warren", "DEM", 361.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3403", "Warren", "OTH", 1397.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3501", "Warwick", "REP", 1066.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3501", "Warwick", "DEM", 345.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3501", "Warwick", "OTH", 1126.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3502", "Warwick", "REP", 991.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3502", "Warwick", "DEM", 346.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3502", "Warwick", "OTH", 1145.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3503", "Warwick", "REP", 579.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3503", "Warwick", "DEM", 215.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3503", "Warwick", "OTH", 676.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3504", "Warwick", "REP", 941.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3504", "Warwick", "DEM", 227.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3504", "Warwick", "OTH", 846.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3505", "Warwick", "REP", 415.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3505", "Warwick", "DEM", 145.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3505", "Warwick", "OTH", 511.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3506", "Warwick", "REP", 397.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3506", "Warwick", "DEM", 181.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3506", "Warwick", "OTH", 492.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3507", "Warwick", "REP", 229.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3507", "Warwick", "DEM", 88.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3507", "Warwick", "OTH", 296.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3508", "Warwick", "REP", 877.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3508", "Warwick", "DEM", 305.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3508", "Warwick", "OTH", 1120.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3509", "Warwick", "REP", 199.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3509", "Warwick", "DEM", 72.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3509", "Warwick", "OTH", 269.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3510", "Warwick", "REP", 528.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3510", "Warwick", "DEM", 202.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3510", "Warwick", "OTH", 684.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3511", "Warwick", "REP", 937.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3511", "Warwick", "DEM", 334.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3511", "Warwick", "OTH", 1180.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3512", "Warwick", "REP", 663.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3512", "Warwick", "DEM", 269.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3512", "Warwick", "OTH", 795.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3513", "Warwick", "REP", 837.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3513", "Warwick", "DEM", 323.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3513", "Warwick", "OTH", 1165.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3514", "Warwick", "REP", 1149.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3514", "Warwick", "DEM", 434.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3514", "Warwick", "OTH", 1418.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3515", "Warwick", "REP", 1112.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3515", "Warwick", "DEM", 436.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3515", "Warwick", "OTH", 1363.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3516", "Warwick", "REP", 302.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3516", "Warwick", "DEM", 117.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3516", "Warwick", "OTH", 367.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3517", "Warwick", "REP", 350.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3517", "Warwick", "DEM", 143.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3517", "Warwick", "OTH", 453.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3518", "Warwick", "REP", 1019.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3518", "Warwick", "DEM", 516.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3518", "Warwick", "OTH", 1402.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3519", "Warwick", "REP", 1083.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3519", "Warwick", "DEM", 453.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3519", "Warwick", "OTH", 1403.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3520", "Warwick", "REP", 871.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3520", "Warwick", "DEM", 379.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3520", "Warwick", "OTH", 1167.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3521", "Warwick", "REP", 781.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3521", "Warwick", "DEM", 325.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3521", "Warwick", "OTH", 1069.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3522", "Warwick", "REP", 643.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3522", "Warwick", "DEM", 263.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3522", "Warwick", "OTH", 780.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3523", "Warwick", "REP", 941.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3523", "Warwick", "DEM", 358.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3523", "Warwick", "OTH", 1170.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3524", "Warwick", "REP", 570.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3524", "Warwick", "DEM", 284.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3524", "Warwick", "OTH", 859.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3525", "Warwick", "REP", 720.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3525", "Warwick", "DEM", 350.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3525", "Warwick", "OTH", 987.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3526", "Warwick", "REP", 265.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3526", "Warwick", "DEM", 123.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3526", "Warwick", "OTH", 351.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3527", "Warwick", "REP", 607.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3527", "Warwick", "DEM", 324.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3527", "Warwick", "OTH", 885.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3528", "Warwick", "REP", 397.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3528", "Warwick", "DEM", 169.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3528", "Warwick", "OTH", 499.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3529", "Warwick", "REP", 687.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3529", "Warwick", "DEM", 310.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3529", "Warwick", "OTH", 867.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3530", "Warwick", "REP", 917.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3530", "Warwick", "DEM", 410.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3530", "Warwick", "OTH", 1177.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3531", "Warwick", "REP", 957.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3531", "Warwick", "DEM", 511.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3531", "Warwick", "OTH", 1278.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3532", "Warwick", "REP", 445.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3532", "Warwick", "DEM", 174.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3532", "Warwick", "OTH", 583.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3533", "Warwick", "REP", 381.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3533", "Warwick", "DEM", 175.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3533", "Warwick", "OTH", 560.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3701", "West Greenwich", "REP", 354.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3701", "West Greenwich", "DEM", 408.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3701", "West Greenwich", "OTH", 797.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3702", "West Greenwich", "REP", 360.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3702", "West Greenwich", "DEM", 274.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3702", "West Greenwich", "OTH", 683.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3703", "West Greenwich", "REP", 227.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3703", "West Greenwich", "DEM", 271.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3703", "West Greenwich", "OTH", 545.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3704", "West Greenwich", "REP", 276.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3704", "West Greenwich", "DEM", 267.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3704", "West Greenwich", "OTH", 581.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3801", "West Warwick", "REP", 742.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3801", "West Warwick", "DEM", 338.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3801", "West Warwick", "OTH", 1024.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3802", "West Warwick", "REP", 505.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3802", "West Warwick", "DEM", 227.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3802", "West Warwick", "OTH", 765.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3803", "West Warwick", "REP", 288.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3803", "West Warwick", "DEM", 136.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3803", "West Warwick", "OTH", 449.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3804", "West Warwick", "REP", 1206.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3804", "West Warwick", "DEM", 558.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3804", "West Warwick", "OTH", 1499.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3805", "West Warwick", "REP", 473.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3805", "West Warwick", "DEM", 200.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3805", "West Warwick", "OTH", 704.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3806", "West Warwick", "REP", 432.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3806", "West Warwick", "DEM", 178.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3806", "West Warwick", "OTH", 491.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3807", "West Warwick", "REP", 1067.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3807", "West Warwick", "DEM", 472.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3807", "West Warwick", "OTH", 1433.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3808", "West Warwick", "REP", 830.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3808", "West Warwick", "DEM", 463.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3808", "West Warwick", "OTH", 1128.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3809", "West Warwick", "REP", 704.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3809", "West Warwick", "DEM", 328.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3809", "West Warwick", "OTH", 957.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3810", "West Warwick", "REP", 631.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3810", "West Warwick", "DEM", 285.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3810", "West Warwick", "OTH", 888.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3601", "Westerly", "REP", 351.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3601", "Westerly", "DEM", 246.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3601", "Westerly", "OTH", 576.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3602", "Westerly", "REP", 1148.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3602", "Westerly", "DEM", 497.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3602", "Westerly", "OTH", 1444.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3603", "Westerly", "REP", 1035.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3603", "Westerly", "DEM", 467.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3603", "Westerly", "OTH", 1331.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3604", "Westerly", "REP", 843.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3604", "Westerly", "DEM", 565.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3604", "Westerly", "OTH", 1177.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3605", "Westerly", "REP", 882.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3605", "Westerly", "DEM", 574.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3605", "Westerly", "OTH", 1241.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3606", "Westerly", "REP", 894.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3606", "Westerly", "DEM", 485.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3606", "Westerly", "OTH", 1313.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3607", "Westerly", "REP", 653.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3607", "Westerly", "DEM", 402.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3607", "Westerly", "OTH", 1124.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3901", "Woonsocket", "REP", 206.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3901", "Woonsocket", "DEM", 69.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3901", "Woonsocket", "OTH", 287.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3902", "Woonsocket", "REP", 553.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3902", "Woonsocket", "DEM", 149.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3902", "Woonsocket", "OTH", 587.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3903", "Woonsocket", "REP", 432.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3903", "Woonsocket", "DEM", 119.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3903", "Woonsocket", "OTH", 443.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3904", "Woonsocket", "REP", 1051.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3904", "Woonsocket", "DEM", 251.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3904", "Woonsocket", "OTH", 1022.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3905", "Woonsocket", "REP", 737.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3905", "Woonsocket", "DEM", 252.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3905", "Woonsocket", "OTH", 858.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3906", "Woonsocket", "REP", 663.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3906", "Woonsocket", "DEM", 252.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3906", "Woonsocket", "OTH", 896.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3907", "Woonsocket", "REP", 821.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3907", "Woonsocket", "DEM", 290.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3907", "Woonsocket", "OTH", 1075.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3908", "Woonsocket", "REP", 720.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3908", "Woonsocket", "DEM", 361.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3908", "Woonsocket", "OTH", 906.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3909", "Woonsocket", "REP", 1004.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3909", "Woonsocket", "DEM", 377.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3909", "Woonsocket", "OTH", 1191.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3910", "Woonsocket", "REP", 991.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3910", "Woonsocket", "DEM", 372.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3910", "Woonsocket", "OTH", 1219.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3911", "Woonsocket", "REP", 944.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3911", "Woonsocket", "DEM", 301.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3911", "Woonsocket", "OTH", 1117.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3912", "Woonsocket", "REP", 649.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3912", "Woonsocket", "DEM", 251.0);
INSERT INTO precinct('STATE', 'PRECINCT', 'DISTRICT', 'PARTY', 'VOTERS') VALUES("RI", "3912", "Woonsocket", "OTH", 761.0);
COMMIT;
|
SELECT * FROM t1 LEFT JOIN (t2 , t3 , t4) ON (t2.a = t1.a AND t3.b = t1.b AND t4.c = t1.c)
|
CREATE TABLE [dbo].[Task]
(
[Id] INT NOT NULL PRIMARY KEY,
[AllDay] BIT NULL,
[PriorityId] INT NOT NULL,
[TypeId] INT NOT NULL,
[Description] VARCHAR(256) NULL
)
|
USE [msdb]
GO
BEGIN TRANSACTION
DECLARE @ReturnCode INT
SELECT @ReturnCode = 0
IF NOT EXISTS (SELECT name FROM msdb.dbo.syscategories WHERE name=N'Data Collector' AND category_class=1)
BEGIN
EXEC @ReturnCode = msdb.dbo.sp_add_category @class=N'JOB', @type=N'LOCAL', @name=N'Data Collector'
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
END
DECLARE @jobId BINARY(16)
EXEC @ReturnCode = msdb.dbo.sp_add_job @job_name=N'DatabaseFileStats Collect',
@enabled=1,
@notify_level_eventlog=0,
@notify_level_email=0,
@notify_level_netsend=0,
@notify_level_page=0,
@delete_level=0,
@description=N'No description available.',
@category_name=N'Data Collector',
@owner_login_name=N'sa', @job_id = @jobId OUTPUT
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXEC @ReturnCode = msdb.dbo.sp_add_jobstep @job_id=@jobId, @step_name=N'Collect data',
@step_id=1,
@cmdexec_success_code=0,
@on_success_action=1,
@on_success_step_id=0,
@on_fail_action=2,
@on_fail_step_id=0,
@retry_attempts=0,
@retry_interval=0,
@os_run_priority=0, @subsystem=N'TSQL',
@command=N'SET NOCOUNT ON
DECLARE @file_type CHAR(1)
, @database_name VARCHAR(128)
, @include_mnts bit
, @sql_string nvarchar(4000)
SELECT @file_type = ''a''
, @include_mnts = 1
CREATE TABLE #log_statistics (
[database_name] VARCHAR(200),
[log_size_mb] NUMERIC(18,2),
[log_used_pct] NUMERIC(18,2),
[log_status] INT)
CREATE TABLE #file_list (
[database_name] VARCHAR(200),
[filegroup_name] VARCHAR(200) NULL,
[file_id] INT,
[file_name] VARCHAR(200),
[volume_mount_point] VARCHAR(200),
[file_path] VARCHAR(200),
[file_size] INT,
[max_size] BIGINT,
[growth_size] INT,
[growth_type] INT,
[file_type] INT,
[drive] CHAR(1),
[used_size] INT NULL,
[disk_size] INT NULL,
[free_space] INT NULL)
CREATE TABLE #file_statistics (
[file_id] INT,
[filegroup_id] INT,
[total_extents] INT,
[used_extents] INT,
[database_name] VARCHAR(200),
[file_path] VARCHAR(200))
INSERT #log_statistics EXEC(''DBCC SQLPERF(LOGSPACE) WITH NO_INFOMSGS'')
DECLARE database_cursor CURSOR
FOR SELECT [name] FROM master.sys.databases WITH (NOLOCK) WHERE state_desc = ''ONLINE'' ORDER BY [name]
OPEN database_cursor
FETCH NEXT
FROM database_cursor INTO @database_name
WHILE @@FETCH_STATUS = 0
BEGIN
SET @sql_string = ''USE ['' + @database_name +'']''
SET @sql_string = @sql_string + '' TRUNCATE TABLE #file_statistics''
SET @sql_string = @sql_string + '' INSERT #file_statistics EXEC(''''DBCC SHOWFILESTATS WITH NO_INFOMSGS'''')''
EXEC sp_executesql @sql_string
SET @sql_string = ''INSERT #file_list''
SET @sql_string = @sql_string + '' SELECT database_name='''''' + DB_NAME(DB_ID(@database_name)) + '''''', fg.name, df.file_id, df.name, s.volume_mount_point, df.physical_name, df.size, df.max_size, df.growth, df.is_percent_growth, df.type, drive=UPPER(LEFT(df.physical_name,1)), fs.used_extents, CONVERT(INT,ROUND(s.total_bytes /1024.0/1024/1024,0)), CONVERT(INT,ROUND(s.available_bytes/1024.0/1024/1024,0))''
SET @sql_string = @sql_string + '' FROM ['' + @database_name + ''].sys.database_files df WITH (NOLOCK)''
SET @sql_string = @sql_string + '' LEFT OUTER JOIN ['' + @database_name + ''].sys.filegroups fg WITH (NOLOCK) ON df.data_space_id = fg.data_space_id''
SET @sql_string = @sql_string + '' LEFT OUTER JOIN #file_statistics fs WITH (NOLOCK) ON df.file_id = fs.file_id''
SET @sql_string = @sql_string + '' CROSS APPLY sys.dm_os_volume_stats(DB_ID('''''' + @database_name + ''''''), df.file_id) s''
EXEC sp_executesql @sql_string
FETCH NEXT FROM database_cursor INTO @database_name
END
CLOSE database_cursor
DEALLOCATE database_cursor
UPDATE fl
SET used_size = ls.log_size_mb * ls.log_used_pct / 100 * 1024 / 64
FROM #file_list fl
JOIN #log_statistics ls ON fl.[database_name] = ls.[database_name]
WHERE fl.file_type = 1
INSERT INTO DBA.dbo.DatabaseFileStats
SELECT GETDATE() [date]
, @@SERVERNAME [instance_name]
, [database_name] [database_name]
, file_name [file_name]
, volume_mount_point [mount_point]
, file_path [file_path]
, file_size * 8 / 1024 [size]
, ISNULL(used_size,0) * 64 / 1024 [used]
, (file_size * 8 / 1024) - (ISNULL(used_size,0) * 64 / 1024) [free]
, ISNULL(used_size,0) * 64 / 1024 * 100 / (file_size * 8 / 1024 + 1) [pct]
, CASE WHEN growth_size = 0 THEN '''' WHEN growth_type = 1 THEN growth_size ELSE growth_size * 8 / 1024 END [growth]
, CASE max_size WHEN 0 THEN '''' WHEN -1 THEN '''' WHEN 268435456 THEN '''' ELSE max_size * 8 / 1024 END [max]
, disk_size [drive_size]
, free_space [drive_free]
FROM #file_list
ORDER BY [database_name], file_type, [filegroup_name], [file_id]
',
@database_name=N'master',
@flags=8
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXEC @ReturnCode = msdb.dbo.sp_update_job @job_id = @jobId, @start_step_id = 1
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXEC @ReturnCode = msdb.dbo.sp_add_jobschedule @job_id=@jobId, @name=N'DatabaseFileStats Collect 10pm',
@enabled=1,
@freq_type=4,
@freq_interval=1,
@freq_subday_type=1,
@freq_subday_interval=0,
@freq_relative_interval=0,
@freq_recurrence_factor=0,
@active_start_date=20190415,
@active_end_date=99991231,
@active_start_time=220000,
@active_end_time=235959
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXEC @ReturnCode = msdb.dbo.sp_add_jobschedule @job_id=@jobId, @name=N'DatabaseFileStats Collect 8am',
@enabled=1,
@freq_type=4,
@freq_interval=1,
@freq_subday_type=1,
@freq_subday_interval=0,
@freq_relative_interval=0,
@freq_recurrence_factor=0,
@active_start_date=20190415,
@active_end_date=99991231,
@active_start_time=80000,
@active_end_time=235959
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
EXEC @ReturnCode = msdb.dbo.sp_add_jobserver @job_id = @jobId, @server_name = N'(local)'
IF (@@ERROR <> 0 OR @ReturnCode <> 0) GOTO QuitWithRollback
COMMIT TRANSACTION
GOTO EndSave
QuitWithRollback:
IF (@@TRANCOUNT > 0) ROLLBACK TRANSACTION
EndSave:
GO
|
with completed_lap_subquery as
(select distinct on (effort_id) effort_id, case when kind = 1 then lap else lap - 1 end as completed_laps
from split_times
join splits on splits.id = split_times.split_id
order by effort_id, lap desc, distance_from_start desc, sub_split_bitkey desc)
select es.effort_id,
e.first_name,
e.last_name,
e.bib_number,
e.city,
e.state_code,
e.country_code,
e.age,
e.gender,
e.slug,
es.begin_split_id,
es.begin_bitkey,
es.begin_split_kind,
es.end_split_id,
es.end_bitkey,
es.end_split_kind,
lap,
begin_time,
elapsed_seconds,
home_time_zone,
laps_required != 1 as multiple_laps,
completed_laps >= laps_required as finished
from efforts e
join effort_segments es on es.effort_id = e.id
join events ev on ev.id = e.event_id
join event_groups eg on eg.id = ev.event_group_id
join completed_lap_subquery cls on cls.effort_id = e.id
|
-- table.test
--
-- execsql {
-- CREATE TABLE t7(
-- a integer primary key,
-- b number(5,10),
-- c character varying (8),
-- d VARCHAR(9),
-- e clob,
-- f BLOB,
-- g Text,
-- h
-- );
-- INSERT INTO t7(a) VALUES(1);
-- SELECT typeof(a), typeof(b), typeof(c), typeof(d),
-- typeof(e), typeof(f), typeof(g), typeof(h)
-- FROM t7 LIMIT 1;
-- }
CREATE TABLE t7(
a integer primary key,
b number(5,10),
c character varying (8),
d VARCHAR(9),
e clob,
f BLOB,
g Text,
h
);
INSERT INTO t7(a) VALUES(1);
SELECT typeof(a), typeof(b), typeof(c), typeof(d),
typeof(e), typeof(f), typeof(g), typeof(h)
FROM t7 LIMIT 1;
|
-- file:opr_sanity.sql ln:646 expect:true
SELECT p1.oid, p1.oprname
FROM pg_operator AS p1
WHERE p1.oprcanhash AND NOT EXISTS
(SELECT 1 FROM pg_amop
WHERE amopmethod = (SELECT oid FROM pg_am WHERE amname = 'hash') AND
amopopr = p1.oid AND amopstrategy = 1)
|
-- file:security_label.sql ln:35 expect:true
SECURITY LABEL ON ROLE regress_seclabel_user1 IS '...invalid label...'
|
-- http://emkjp.github.io/WebTools/dot.html に session_id と bloking_session_id を渡して確認
SELECT
r.session_id, r.blocking_session_id ,
r.wait_time, r.last_wait_type, r.wait_resource,
SUBSTRING(s.text, (r.statement_start_offset/2)+1,
((CASE r.statement_end_offset
WHEN -1 THEN DATALENGTH(s.text)
ELSE r.statement_end_offset
END - r.statement_start_offset)/2) + 1) AS statement_text
FROM sys.dm_exec_requests AS r
CROSS APPLY
sys.dm_exec_sql_text(sql_handle) AS s
WHERE r.blocking_session_id > 0
GO
-- 親のブロッカーのクエリの取得
SET NOCOUNT ON
DECLARE @blocker_session_id int
DECLARE cur_blocker CURSOR LOCAL FORWARD_ONLY FOR
SELECT r.session_id
FROM sys.dm_exec_sessions AS r
INNER JOIN
(SELECT
r.session_id, r.blocking_session_id
FROM sys.dm_exec_requests AS r
WHERE r.blocking_session_id > 0
) AS b
ON
b.blocking_session_id = r.session_id
AND r.session_id NOT IN (
SELECT session_id FROM
(SELECT
r.session_id, r.blocking_session_id
FROM sys.dm_exec_requests AS r
WHERE r.blocking_session_id > 0
) AS b2
)
IF OBJECT_ID('tempdb..#inputbuffer_temp') IS NOT NULL
BEGIN
DROP TABLE #inputbuffer_temp
END
CREATE TABLE #inputbuffer_temp (EventType nvarchar(30), Parameters smallint, EventInfo nvarchar(4000))
IF OBJECT_ID('tempdb..#inputbuffer') IS NOT NULL
BEGIN
DROP TABLE #inputbuffer
END
CREATE TABLE #inputbuffer (session_id int, EventType nvarchar(30), Parameters smallint, EventInfo nvarchar(4000))
DECLARE @buf_sql nvarchar(max)
OPEN cur_blocker
FETCH NEXT FROM cur_blocker
INTO @blocker_session_id
WHILE @@FETCH_STATUS = 0
BEGIN
SET @buf_sql = N'DBCC INPUTBUFFER(' + CAST(@blocker_session_id AS varchar(10)) + N') WITH NO_INFOMSGS'
INSERT INTO #inputbuffer_temp EXEC (@buf_sql)
INSERT INTO #inputbuffer SELECT @blocker_session_id, * FROM #inputbuffer_temp
TRUNCATE TABLE #inputbuffer_temp
FETCH NEXT FROM cur_blocker
INTO @blocker_session_id
END
SELECT * FROM #inputbuffer
|
DELETE FROM `mangos_string` WHERE `entry` IN (582);
INSERT INTO `mangos_string` VALUES
(582, 'SpawnTime: Full:%s Remain:%s',NULL,NULL,NULL,NULL,NULL,NULL,NULL);
|
DROP TABLE IF EXISTS public.export_messages CASCADE;
DROP TABLE IF EXISTS public.export_resources CASCADE;
DROP TABLE IF EXISTS public.exports CASCADE;
DROP TABLE IF EXISTS public.import_messages CASCADE;
DROP TABLE IF EXISTS public.import_resources CASCADE;
DROP TABLE IF EXISTS public.imports CASCADE;
DROP TABLE IF EXISTS public.compliance_check_blocks CASCADE;
DROP TABLE IF EXISTS public.compliance_check_messages CASCADE;
DROP TABLE IF EXISTS public.compliance_check_resources CASCADE;
DROP TABLE IF EXISTS public.compliance_check_sets CASCADE;
DROP TABLE IF EXISTS public.compliance_checks CASCADE;
DROP TABLE IF EXISTS public.access_links CASCADE;
DROP TABLE IF EXISTS public.access_points CASCADE;
DROP TABLE IF EXISTS public.api_keys CASCADE;
DROP TABLE IF EXISTS public.calendars CASCADE;
DROP TABLE IF EXISTS public.clean_up_results CASCADE;
DROP TABLE IF EXISTS public.clean_ups CASCADE;
DROP TABLE IF EXISTS public.companies CASCADE;
DROP TABLE IF EXISTS public.compliance_control_blocks CASCADE;
DROP TABLE IF EXISTS public.compliance_control_sets CASCADE;
DROP TABLE IF EXISTS public.compliance_controls CASCADE;
DROP TABLE IF EXISTS public.connection_links CASCADE;
DROP TABLE IF EXISTS public.custom_fields CASCADE;
DROP TABLE IF EXISTS public.facilities CASCADE;
DROP TABLE IF EXISTS public.facilities_features CASCADE;
DROP TABLE IF EXISTS public.footnotes CASCADE;
DROP TABLE IF EXISTS public.footnotes_vehicle_journeys CASCADE;
DROP TABLE IF EXISTS public.group_of_lines CASCADE;
DROP TABLE IF EXISTS public.group_of_lines_lines CASCADE;
DROP TABLE IF EXISTS public.journey_frequencies CASCADE;
DROP TABLE IF EXISTS public.journey_patterns CASCADE;
DROP TABLE IF EXISTS public.journey_patterns_stop_points CASCADE;
DROP TABLE IF EXISTS public.line_referential_memberships CASCADE;
DROP TABLE IF EXISTS public.line_referential_sync_messages CASCADE;
DROP TABLE IF EXISTS public.line_referential_syncs CASCADE;
DROP TABLE IF EXISTS public.line_referentials CASCADE;
DROP TABLE IF EXISTS public.lines CASCADE;
DROP TABLE IF EXISTS public.merges CASCADE;
DROP TABLE IF EXISTS public.networks CASCADE;
DROP TABLE IF EXISTS public.organisations CASCADE;
DROP TABLE IF EXISTS public.pt_links CASCADE;
DROP TABLE IF EXISTS public.referential_clonings CASCADE;
DROP TABLE IF EXISTS public.referential_metadata CASCADE;
DROP TABLE IF EXISTS public.referential_suites CASCADE;
DROP TABLE IF EXISTS public.referentials CASCADE;
DROP TABLE IF EXISTS public.routes CASCADE;
DROP TABLE IF EXISTS public.routing_constraint_zones CASCADE;
DROP TABLE IF EXISTS public.routing_constraints_lines CASCADE;
DROP TABLE IF EXISTS public.schema_migrations CASCADE;
DROP TABLE IF EXISTS public.stop_area_referential_memberships CASCADE;
DROP TABLE IF EXISTS public.stop_area_referential_sync_messages CASCADE;
DROP TABLE IF EXISTS public.stop_area_referential_syncs CASCADE;
DROP TABLE IF EXISTS public.stop_area_referentials CASCADE;
DROP TABLE IF EXISTS public.stop_areas CASCADE;
DROP TABLE IF EXISTS public.stop_areas_stop_areas CASCADE;
DROP TABLE IF EXISTS public.stop_points CASCADE;
DROP TABLE IF EXISTS public.taggings CASCADE;
DROP TABLE IF EXISTS public.tags CASCADE;
DROP TABLE IF EXISTS public.time_table_dates CASCADE;
DROP TABLE IF EXISTS public.time_table_periods CASCADE;
DROP TABLE IF EXISTS public.time_tables CASCADE;
DROP TABLE IF EXISTS public.time_tables_vehicle_journeys CASCADE;
DROP TABLE IF EXISTS public.timebands CASCADE;
DROP TABLE IF EXISTS public.users CASCADE;
DROP TABLE IF EXISTS public.vehicle_journey_at_stops CASCADE;
DROP TABLE IF EXISTS public.vehicle_journeys CASCADE;
DROP TABLE IF EXISTS public.workbenches CASCADE;
DROP TABLE IF EXISTS public.workgroups CASCADE;
|
<reponame>ajcaldera1/yugabyte-db
--
-- CREATE_INDEX
-- Create ancillary data structures (i.e. indices)
--
--
-- BTREE
--
CREATE INDEX onek_unique1 ON onek USING btree(unique1 int4_ops);
CREATE INDEX IF NOT EXISTS onek_unique1 ON onek USING btree(unique1 int4_ops);
CREATE INDEX IF NOT EXISTS ON onek USING btree(unique1 int4_ops);
CREATE INDEX onek_unique2 ON onek USING btree(unique2 int4_ops);
CREATE INDEX onek_hundred ON onek USING btree(hundred int4_ops);
CREATE INDEX onek_stringu1 ON onek USING btree(stringu1 name_ops);
CREATE INDEX tenk1_unique1 ON tenk1 USING btree(unique1 int4_ops);
CREATE INDEX tenk1_unique2 ON tenk1 USING btree(unique2 int4_ops);
CREATE INDEX tenk1_hundred ON tenk1 USING btree(hundred int4_ops);
CREATE INDEX tenk1_thous_tenthous ON tenk1 (thousand, tenthous);
CREATE INDEX tenk2_unique1 ON tenk2 USING btree(unique1 int4_ops);
CREATE INDEX tenk2_unique2 ON tenk2 USING btree(unique2 int4_ops);
CREATE INDEX tenk2_hundred ON tenk2 USING btree(hundred int4_ops);
CREATE INDEX rix ON road USING btree (name text_ops);
CREATE INDEX iix ON ihighway USING btree (name text_ops);
CREATE INDEX six ON shighway USING btree (name text_ops);
CREATE INDEX onek_two_idx ON onek USING btree(two);
DROP INDEX onek_two_idx;
DROP INDEX onek_two_idx;
DROP INDEX IF EXISTS onek_two_idx;
--
-- Create index on existing table with data
--
CREATE TABLE index_test (col1 int, col2 int);
INSERT INTO index_test (col1, col2) VALUES (1, 100);
INSERT INTO index_test (col1, col2) VALUES (2, 200);
CREATE INDEX index_test_idx1 ON index_test(col1);
CREATE INDEX index_test_idx2 ON index_test(col1, col2);
DROP INDEX index_test_idx1;
DROP INDEX index_test_idx2;
DROP TABLE index_test;
CREATE TABLE test_index (v1 INT, v2 INT, v3 INT);
CREATE INDEX ON test_index (v1);
CREATE INDEX ON test_index (v2, v3);
INSERT INTO test_index VALUES (1, 11, 21), (2, 12, 22), (3, 13, 23), (4, 14, 24), (5, 15, 25);
-- Verify order by on indexed column
SELECT * FROM test_index ORDER BY v1;
-- Verify delete with hash value in index
DELETE FROM test_index WHERE v2 = 12 OR v2 = 13;
SELECT * FROM test_index ORDER BY v1;
-- Verify different WHERE conditions are supported.
SELECT * FROM test_index WHERE v1 IS NULL;
SELECT * FROM test_index WHERE v1 IS NOT NULL;
SELECT * FROM test_index WHERE v1 IN (1, 2, 3);
-- Verify indexes on system catalog tables are updated properly
CREATE TABLE test_sys_catalog_update (k int primary key, v int);
EXPLAIN SELECT relname FROM pg_class WHERE relname = 'test_sys_catalog_update';
SELECT relname FROM pg_class WHERE relname = 'test_sys_catalog_update';
EXPLAIN SELECT typname FROM pg_type WHERE typname = 'test_sys_catalog_update';
SELECT typname FROM pg_type WHERE typname = 'test_sys_catalog_update';
EXPLAIN SELECT attname, atttypid FROM pg_attribute WHERE attname = 'v';
SELECT attname, atttypid FROM pg_attribute WHERE attname = 'v';
ALTER TABLE test_sys_catalog_update RENAME TO test_sys_catalog_update_new;
ALTER TABLE test_sys_catalog_update_new RENAME COLUMN v TO w;
SELECT relname FROM pg_class WHERE relname = 'test_sys_catalog_update';
SELECT typname FROM pg_type WHERE typname = 'test_sys_catalog_update';
SELECT attname, atttypid FROM pg_attribute WHERE attname = 'v';
SELECT relname FROM pg_class WHERE relname = 'test_sys_catalog_update_new';
SELECT typname FROM pg_type WHERE typname = 'test_sys_catalog_update_new';
SELECT attname, atttypid FROM pg_attribute WHERE attname = 'w';
-- Test primary key as index
CREATE TABLE t1 (h INT, r INT, v1 INT, v2 INT, PRIMARY KEY (h, r));
CREATE INDEX ON t1 (v1);
CREATE UNIQUE INDEX ON t1 (v1, v2);
CREATE TABLE t2 (h INT, r INT, v1 INT, v2 INT, PRIMARY KEY (h, r));
\d t1
\d t2
INSERT INTO t1 VALUES (1, 1, 11, 11), (1, 2, 11, 12);
INSERT INTO t2 VALUES (1, 1, 21, 21);
-- The following 2 inserts should produce error due to duplicate primary key / unique index value
INSERT INTO t1 VALUES (1, 1, 99, 99);
INSERT INTO t1 VALUES (1, 3, 11, 11);
INSERT INTO t1 VALUES (1, 3, 11, 13), (2, 1, 12, 13), (2, 2, 12, 14);
EXPLAIN (COSTS OFF) SELECT * FROM t1 ORDER BY h, r;
SELECT * FROM t1 ORDER BY h, r;
EXPLAIN (COSTS OFF) SELECT * FROM t1 WHERE h = 1 ORDER BY r;
SELECT * FROM t1 WHERE h = 1 ORDER BY r;
EXPLAIN (COSTS OFF) SELECT * FROM t1 WHERE h > 1 ORDER BY h, r;
SELECT * FROM t1 WHERE h > 1 ORDER BY h, r;
EXPLAIN (COSTS OFF) SELECT * FROM t1 WHERE h = 1 AND r = 1;
SELECT * FROM t1 WHERE h = 1 AND r = 1;
EXPLAIN (COSTS OFF) SELECT * FROM t1 WHERE v1 = 11 ORDER BY h, r;
SELECT * FROM t1 WHERE v1 = 11 ORDER BY h, r;
-- Disabled this test because we do not have proper stats. We return the same cost estimate
-- for indexes t1_v1_idx and t1_v1_v2_idx and Postgres will be either of them at random.
-- EXPLAIN (COSTS OFF) SELECT * FROM t1 WHERE v1 = 11 AND v2 = 11;
-- SELECT * FROM t1 WHERE v1 = 11 AND v2 = 11;
EXPLAIN (COSTS OFF) SELECT t1.h, t1.r, t1.v1, t2.v1 FROM t1, t2 WHERE t1.h = t2.h AND t1.r = t2.r;
SELECT t1.h, t1.r, t1.v1, t2.v1 FROM t1, t2 WHERE t1.h = t2.h AND t1.r = t2.r;
--
-- NULL value in index
--
CREATE TABLE null_index(k int, v int);
CREATE INDEX null_index_v ON null_index(v);
INSERT INTO null_index(k) VALUES(1);
INSERT INTO null_index VALUES(2, NULL);
INSERT INTO null_index VALUES(3, 3);
SELECT * FROM null_index ORDER BY k;
SELECT * FROM null_index WHERE v IS NULL ORDER BY k;
SELECT * FROM null_index WHERE v IS NOT NULL ORDER BY k;
--
-- NULL value in unique index
--
CREATE TABLE null_unique_index(k int, v int);
CREATE UNIQUE INDEX ON null_unique_index(v);
INSERT INTO null_unique_index(k) values(1);
INSERT INTO null_unique_index values(2, NULL);
INSERT INTO null_unique_index values(3, NULL);
INSERT INTO null_unique_index values(4, 4);
INSERT INTO null_unique_index values(5, 4); -- fail
SELECT * FROM null_unique_index WHERE v IS NULL ORDER BY k;
DELETE FROM null_unique_index WHERE k = 2;
SELECT * FROM null_unique_index WHERE v IS NULL ORDER BY k;
DELETE FROM null_unique_index WHERE v IS NULL;
SELECT * FROM null_unique_index ORDER BY k;
-- Test index update with UPDATE and DELETE
CREATE TABLE test_unique (k int PRIMARY KEY, v1 int, v2 int);
CREATE UNIQUE INDEX ON test_unique (v1);
CREATE INDEX ON test_unique (v2);
-- Insert a row
INSERT INTO test_unique VALUES (1, 1, 1);
SELECT * FROM test_unique;
-- UPDATE a row and verify the content of associated indexes via index-only scan
UPDATE test_unique SET v1 = 2 WHERE k = 1;
SELECT v1 FROM test_unique WHERE v1 IN (1, 2);
SELECT v2 FROM test_unique WHERE v2 IN (1, 2);
-- DELETE a row and verify the content of associated indexes via index-only scan
DELETE FROM test_unique WHERE k = 1;
SELECT v1 FROM test_unique WHERE v1 IN (1, 2);
SELECT v2 FROM test_unique WHERE v2 IN (1, 2);
-- Insert 2 rows of the affected v1 values. Make sure both can be inserted
-- with no duplicate key violation.
INSERT INTO test_unique VALUES (1, 1, 1);
INSERT INTO test_unique VALUES (2, 2, 2);
SELECT * FROM test_unique;
|
--! Previous: sha1:9acd3c09d1b12fb16353ef940d4caa662d7c7b9a
--! Hash: sha1:c6b398b4ba13a8bb86387ad079e66497bfc37d37
--! Message: create-categories
-- Create categories table
-- Undo if rerunning
DROP TABLE IF EXISTS categories;
-- Create table
CREATE TABLE categories (
id SERIAL PRIMARY KEY,
accumulated BOOLEAN NOT NULL DEFAULT true,
active BOOLEAN NOT NULL DEFAULT true,
description TEXT NULL,
notes TEXT NULL,
ordinal INTEGER NOT NULL,
section_id INTEGER NOT NULL,
service TEXT NOT NULL,
slug TEXT NOT NULL
);
-- Create unique indexes
CREATE UNIQUE INDEX categories_section_id_ordinal
ON categories (section_id, ordinal);
-- Create foreign key constraints
ALTER TABLE categories ADD CONSTRAINT categories_section_id_fkey
FOREIGN KEY (section_id) REFERENCES sections (id)
ON UPDATE CASCADE ON DELETE CASCADE;
|
create table mytable(_id int primary key, _value varchar(64));
insert into mytable values (1, 'first');
insert into mytable values (2, 'second');
|
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[MedType] (
[MedTypeID] [varchar](16) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[MedType]
ADD
CONSTRAINT [PK_MedType]
PRIMARY KEY
CLUSTERED
([MedTypeID])
ON [PRIMARY]
GO
ALTER TABLE [dbo].[MedType] SET (LOCK_ESCALATION = TABLE)
GO
|
<filename>pcm/src/main/resources/db/migration/V1.1.0__Alter patient id to varchar.sql
LOCK TABLES
patient WRITE,
patient_providers WRITE,
patient_aud WRITE,
consent WRITE,
consent_aud WRITE;
ALTER TABLE patient_providers
DROP FOREIGN KEY FK9yk8mkbajtynqjk49xe1abqm2,
MODIFY patient_id varchar(255) NOT NULL;
ALTER TABLE consent
DROP FOREIGN KEY FK975ajb9rne9852qoi9c2rq2pg,
MODIFY patient_id varchar(255);
ALTER TABLE consent_aud MODIFY patient_id varchar(255);
ALTER TABLE patient MODIFY id varchar(255) NOT NULL;
ALTER TABLE patient_aud MODIFY id varchar(255);
ALTER TABLE patient_providers
ADD CONSTRAINT FK9yk8mkbajtynqjk49xe1abqm2
FOREIGN KEY (patient_id)
REFERENCES patient (id);
ALTER TABLE consent
ADD CONSTRAINT FK975ajb9rne9852qoi9c2rq2pg
FOREIGN KEY (patient_id)
REFERENCES patient (id);
UNLOCK TABLES;
|
CREATE KEYSPACE IF NOT EXISTS pluralsight
WITH replication = {'class':'SimpleStrategy','replication_factor':1};
USE pluralsight;
create table users (
id varchar primary key,
first_name varchar,
last_name varchar,
email varchar,
password varchar,
reset_token varchar
) with comment = 'A table of users';
insert into users (id, first_name, last_name, email)
values ('john-doe', 'John', 'Doe', '<EMAIL>');
insert into users (id, first_name, last_name, email)
values ('jane-doe', 'Jane', 'Doe', '<EMAIL>');
|
<filename>integration_tests/models/count_orders/input_count_orders_by_year_and_payment_type.sql
-- depends on: {{ ref('mock_purchase_data') }}
select * from {{
metrics.metric(
'count_orders',
'year',
dimensions=['payment_type']
)
}}
|
<filename>macros/calendar_date/next_month_number.sql
{%- macro next_month_number(tz=None) -%}
{{ dbt_date.date_part('month', dbt_date.next_month(1, tz)) }}
{%- endmacro -%}
|
PRINT 'Adding ProjectRisks'
SET IDENTITY_INSERT dbo.[ProjectRisks] ON
-- Parent Agencies.
INSERT INTO dbo.[ProjectRisks] (
[Id]
, [Code]
, [Name]
, [Description]
, [IsDisabled]
, [SortOrder]
) VALUES (
1
, 'COMP'
, 'Complete'
, '100% of the property value'
, 0
, 1
), (
2
, 'GREEN'
, 'Green'
, '90% of the property value'
, 0
, 2
), (
3
, 'YELLOW'
, 'Yellow'
, '50% of the property value'
, 0
, 3
), (
4
, 'RED'
, 'Red'
, '0% of the property value'
, 0
, 4
)
SET IDENTITY_INSERT dbo.[ProjectRisks] OFF
|
--
-- Regression tests for schemas (namespaces)
--
CREATE SCHEMA test_schema_1
CREATE UNIQUE INDEX abc_a_idx ON abc (a)
CREATE VIEW abc_view AS
SELECT a+1 AS a, b+1 AS b FROM abc
CREATE TABLE abc (
a serial,
b int UNIQUE
);
-- verify that the objects were created
SELECT COUNT(*) FROM pg_class WHERE relnamespace =
(SELECT oid FROM pg_namespace WHERE nspname = 'test_schema_1');
INSERT INTO test_schema_1.abc DEFAULT VALUES;
INSERT INTO test_schema_1.abc DEFAULT VALUES;
INSERT INTO test_schema_1.abc DEFAULT VALUES;
SELECT * FROM test_schema_1.abc;
SELECT * FROM test_schema_1.abc_view;
ALTER SCHEMA test_schema_1 RENAME TO test_schema_renamed;
SELECT COUNT(*) FROM pg_class WHERE relnamespace =
(SELECT oid FROM pg_namespace WHERE nspname = 'test_schema_1');
-- test IF NOT EXISTS cases
CREATE SCHEMA test_schema_renamed; -- fail, already exists
CREATE SCHEMA IF NOT EXISTS test_schema_renamed; -- ok with notice
CREATE SCHEMA IF NOT EXISTS test_schema_renamed -- fail, disallowed
CREATE TABLE abc (
a serial,
b int UNIQUE
);
DROP SCHEMA test_schema_renamed CASCADE;
-- verify that the objects were dropped
SELECT COUNT(*) FROM pg_class WHERE relnamespace =
(SELECT oid FROM pg_namespace WHERE nspname = 'test_schema_renamed');
|
sql_execute explain select c_custkey, c_name, sum(l_extendedprice * (1 - l_discount)) as revenue, c_acctbal, n_name, c_address, c_phone, c_comment from customer, orders, lineitem, nation where c_custkey = o_custkey and l_orderkey = o_orderkey and o_orderdate >= '1994-04-01' and o_orderdate < adddate('1994-04-01', 90) and l_returnflag = 'R' and c_nationkey = n_nationkey group by c_custkey, c_name, c_acctbal, c_phone, n_name, c_address, c_comment order by revenue desc
sql_execute select * from show
|
ALTER TABLE `apply_application` ADD (
`program_selection` varchar(50) NOT NULL,
`benefit` longtext NOT NULL,
`want_designer` tinyint DEFAULT 0 NOT NULL
);
|
<gh_stars>1-10
--+ holdcas on;
drop table if exists test_tbl;
CREATE TABLE test_tbl(groupid int,itemno int);
INSERT INTO test_tbl VALUES(1,null);
INSERT INTO test_tbl VALUES(1,null);
INSERT INTO test_tbl VALUES(1,1);
INSERT INTO test_tbl VALUES(1,null);
INSERT INTO test_tbl VALUES(1,2);
INSERT INTO test_tbl VALUES(1,3);
INSERT INTO test_tbl VALUES(1,4);
INSERT INTO test_tbl VALUES(1,5);
INSERT INTO test_tbl VALUES(2,null);
INSERT INTO test_tbl VALUES(2,null);
INSERT INTO test_tbl VALUES(2,null);
INSERT INTO test_tbl VALUES(2,6);
INSERT INTO test_tbl VALUES(2,7);
SELECT groupid, itemno, NTH_VALUE(itemno, 2) IGNORE NULLS OVER(PARTITION BY groupid ORDER BY itemno NULLS FIRST) AS ret_val
FROM test_tbl;
drop table if exists test_tbl;
--+ holdcas off;
commit;
|
-- @testpoint:opengauss关键字shutdown(非保留)，作为用户组名
--关键字不带引号-成功
drop group if exists shutdown;
create group shutdown with password '<PASSWORD>';
drop group shutdown;
--关键字带双引号-成功
drop group if exists "shutdown";
create group "shutdown" with password '<PASSWORD>';
drop group "shutdown";
--关键字带单引号-合理报错
drop group if exists 'shutdown';
create group 'shutdown' with password '<PASSWORD>';
--关键字带反引号-合理报错
drop group if exists `shutdown`;
create group `shutdown` with password '<PASSWORD>';
|
<reponame>HBPMedical/Enabling_Services<gh_stars>0
CREATE TABLE PATHOLOGIES(
ID UUID PRIMARY KEY NOT NULL,
CODE VARCHAR(50) UNIQUE NOT NULL,
LABEL TEXT,
VERSION VARCHAR(50) NOT NULL,
METADATA JSON NOT NULL
);
CREATE TABLE HOSPITALS(
ID UUID PRIMARY KEY NOT NULL,
CODE VARCHAR(50) UNIQUE NOT NULL,
LABEL TEXT
);
CREATE TABLE DATASETS(
ID UUID PRIMARY KEY NOT NULL,
CODE VARCHAR(50) UNIQUE NOT NULL,
LABEL TEXT,
HOSPITAL_ID UUID NOT NULL REFERENCES HOSPITALS(ID),
PATHOLOGY_ID UUID NOT NULL REFERENCES PATHOLOGIES(ID)
);
CREATE TABLE MIP_USERS(
ID UUID PRIMARY KEY NOT NULL,
USERNAME VARCHAR(50) UNIQUE NOT NULL,
PASSWORD TEXT NOT NULL
);
CREATE TABLE EXPERIMENTS(
ID UUID PRIMARY KEY NOT NULL,
CODE VARCHAR(50) NOT NULL,
LABEL TEXT,
MIP_USER_ID UUID NOT NULL REFERENCES MIP_USERS(ID),
ALGORITHM_CODE VARCHAR(50) NOT NULL,
INPUT_JSON JSON NOT NULL,
RESULT_JSON JSON
);
|
<reponame>TyreX6/symfony3.4
-- phpMyAdmin SQL Dump
-- version 4.6.4
-- https://www.phpmyadmin.net/
--
-- Client : 127.0.0.1
-- Généré le : Jeu 26 Avril 2018 à 08:45
-- Version du serveur : 5.7.14
-- Version de PHP : 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 */;
--
-- Base de données : `reservation_ressources`
--
-- --------------------------------------------------------
--
-- Structure de la table `admin`
--
CREATE TABLE `admin` (
`id` int(11) NOT NULL,
`username` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`username_canonical` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`email` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`email_canonical` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`enabled` tinyint(1) NOT NULL,
`salt` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
`password` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`last_login` datetime DEFAULT NULL,
`confirmation_token` varchar(180) COLLATE utf8_unicode_ci DEFAULT NULL,
`password_requested_at` datetime DEFAULT NULL,
`roles` longtext COLLATE utf8_unicode_ci NOT NULL COMMENT '(DC2Type:array)'
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `admin`
--
INSERT INTO `admin` (`id`, `username`, `username_canonical`, `email`, `email_canonical`, `enabled`, `salt`, `password`, `last_login`, `confirmation_token`, `password_requested_at`, `roles`) VALUES
(1, 'admin', 'admin', '<EMAIL>', '<EMAIL>', 1, NULL, '$2y$13$f6q.ke7jCWeqmEuapWjSv.qGXJpRJrR2b5eC/ARpB4uwHc8Pk5kHS', '2018-04-26 04:52:56', NULL, NULL, 'a:1:{i:0;s:10:"ROLE_ADMIN";}');
-- --------------------------------------------------------
--
-- Structure de la table `application`
--
CREATE TABLE `application` (
`id` int(11) NOT NULL,
`dispositif_id` int(11) DEFAULT NULL,
`name` varchar(255) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `application`
--
INSERT INTO `application` (`id`, `dispositif_id`, `name`) VALUES
(1, 1, 'Chrome'),
(2, 1, 'Youtube'),
(3, 3, 'Chrome'),
(4, 3, 'Instagram'),
(5, 3, 'Facebook'),
(6, 4, 'IOS Tools'),
(7, 4, 'Facebook');
-- --------------------------------------------------------
--
-- Structure de la table `categorie`
--
CREATE TABLE `categorie` (
`id` int(11) NOT NULL,
`name` varchar(255) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `categorie`
--
INSERT INTO `categorie` (`id`, `name`) VALUES
(1, 'SmartPhone IOS'),
(2, 'SmartPhone Android'),
(3, 'Projecteur'),
(4, 'Salle');
-- --------------------------------------------------------
--
-- Structure de la table `dispositif`
--
CREATE TABLE `dispositif` (
`id` int(11) NOT NULL,
`model` varchar(50) COLLATE utf8_unicode_ci NOT NULL,
`os` varchar(20) COLLATE utf8_unicode_ci NOT NULL,
`OsVersion` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`cpu` varchar(40) COLLATE utf8_unicode_ci NOT NULL,
`ram` double NOT NULL,
`disk_space` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`resolution` varchar(20) COLLATE utf8_unicode_ci NOT NULL,
`deviceName` varchar(50) COLLATE utf8_unicode_ci NOT NULL,
`cpu_cores` int(11) NOT NULL,
`free_disk_space` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`used_disk_space` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`device_uuid` varchar(80) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `dispositif`
--
INSERT INTO `dispositif` (`id`, `model`, `os`, `OsVersion`, `cpu`, `ram`, `disk_space`, `resolution`, `deviceName`, `cpu_cores`, `free_disk_space`, `used_disk_space`, `device_uuid`) VALUES
(1, 'Samsung Note 4', 'ANDROID', 'Marshmallow 6.0', 'Snapdragon 805', 3.072, '595292529252529', '2048x1440', 'Samsung Test', 0, '', '', 'sqdf56qsd554fs5d4f4fz'),
(3, 'Google Pixel 2', 'ANDROID', 'Marshmallow 7.0', 'Snapdragon 805', 2.048, '59529247245252529', '2048x1440', 'Pixel Test', 0, '', '', 'zef54d5fdz5fdzfz'),
(4, 'Iphone 6', 'IOS', 'iOS 9.1', 'Octa-core', 2.048, '456754527252529', '1080x1920', 'Iphone Test', 0, '', '', 'zdf545q1s5d1f5zef5'),
(12, 'iPhone 7 (GSM)', 'IOS', '11.2', 'A10 Fusion , 2.34 GHz', 2.048, '31.99 GB', '1334x750', 'iPhone de Proxym (Ref 51)', 2, '24.27 GB', '7.72 GB', 'B9F27A3F-4992-4C0B-BD17-F3C18597ECCC'),
(13, 'iPhone Simulator', 'IOS', '11.2', 'A9 , 1.85 GHz', 12, '998.97 GB', '1136x640', 'support’s MacBook Pro', 2, '851.18 GB', '147.79 GB', 'D4D109BA-B94D-48B5-AE65-D9FB264B741B');
-- --------------------------------------------------------
--
-- Structure de la table `fos_user`
--
CREATE TABLE `fos_user` (
`id` int(11) NOT NULL,
`username` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`username_canonical` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`email` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`email_canonical` varchar(180) COLLATE utf8_unicode_ci NOT NULL,
`enabled` tinyint(1) NOT NULL,
`salt` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
`password` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`last_login` datetime DEFAULT NULL,
`confirmation_token` varchar(180) COLLATE utf8_unicode_ci DEFAULT NULL,
`password_requested_at` datetime DEFAULT NULL,
`roles` longtext COLLATE utf8_unicode_ci NOT NULL COMMENT '(DC2Type:array)',
`dn` varchar(255) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `fos_user`
--
INSERT INTO `fos_user` (`id`, `username`, `username_canonical`, `email`, `email_canonical`, `enabled`, `salt`, `password`, `last_login`, `confirmation_token`, `password_requested_at`, `roles`, `dn`) VALUES
(1, 'ghandri', 'ghandri', '<EMAIL>', '<EMAIL>', 1, NULL, '', '2018-04-26 04:39:07', NULL, NULL, 'a:1:{i:0;s:9:"ROLE_USER";}', 'uid=ghandri,ou=People,dc=localhost'),
(2, 'jbrown', 'jbrown', '<EMAIL>', '<EMAIL>', 1, NULL, '', '2018-04-14 19:33:19', NULL, NULL, 'a:1:{i:0;s:9:"ROLE_USER";}', 'uid=jbrown,ou=People,dc=localhost');
-- --------------------------------------------------------
--
-- Structure de la table `image`
--
CREATE TABLE `image` (
`id` int(11) NOT NULL,
`dispositive_id` int(11) DEFAULT NULL,
`file_name` varchar(45) COLLATE utf8_unicode_ci NOT NULL,
`path` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
`date_ajout` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
-- --------------------------------------------------------
--
-- Structure de la table `inventory`
--
CREATE TABLE `inventory` (
`id` int(11) NOT NULL,
`etat_inventaire` varchar(30) COLLATE utf8_unicode_ci NOT NULL,
`date_inventaire` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `inventory`
--
INSERT INTO `inventory` (`id`, `etat_inventaire`, `date_inventaire`) VALUES
(1, 'Terminé', '2018-04-15 17:20:41'),
(2, 'Ouvert', '2018-04-15 22:48:55'),
(3, 'Terminé', '2018-04-19 16:06:33'),
(4, 'Ouvert', '2018-04-26 04:36:06');
-- --------------------------------------------------------
--
-- Structure de la table `ldapconfig`
--
CREATE TABLE `ldapconfig` (
`id` int(11) NOT NULL,
`host` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`base_dn` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`port` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `ldapconfig`
--
INSERT INTO `ldapconfig` (`id`, `host`, `base_dn`, `port`) VALUES
(1, '192.168.56.102', 'ou=people,dc=localhost', 389);
-- --------------------------------------------------------
--
-- Structure de la table `line_inventory`
--
CREATE TABLE `line_inventory` (
`id` int(11) NOT NULL,
`resource_id` int(11) DEFAULT NULL,
`inventaire_id` int(11) DEFAULT NULL,
`etat` varchar(20) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `line_inventory`
--
INSERT INTO `line_inventory` (`id`, `resource_id`, `inventaire_id`, `etat`) VALUES
(1, 1, 1, 'Fonctionnel'),
(2, 4, 1, 'Fonctionnel'),
(16, 3, 1, 'Fonctionnel');
-- --------------------------------------------------------
--
-- Structure de la table `message`
--
CREATE TABLE `message` (
`id` int(11) NOT NULL,
`user_id` int(11) NOT NULL,
`vu` tinyint(1) NOT NULL,
`date_envoi` datetime NOT NULL,
`message` varchar(255) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `message`
--
INSERT INTO `message` (`id`, `user_id`, `vu`, `date_envoi`, `message`) VALUES
(1, 1, 1, '2018-04-22 11:30:00', 'hello people');
-- --------------------------------------------------------
--
-- Structure de la table `notification`
--
CREATE TABLE `notification` (
`id` int(11) NOT NULL,
`reservation_id` int(11) NOT NULL,
`vu` tinyint(1) NOT NULL,
`date_res` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `notification`
--
INSERT INTO `notification` (`id`, `reservation_id`, `vu`, `date_res`) VALUES
(50, 52, 1, '2018-04-12 10:17:45'),
(54, 56, 1, '2018-04-12 15:03:31'),
(65, 67, 1, '2018-04-13 09:43:16'),
(79, 82, 1, '2018-04-13 11:22:28'),
(82, 85, 1, '2018-04-14 17:48:39'),
(88, 92, 1, '2018-04-16 23:57:46'),
(89, 93, 1, '2018-04-16 23:57:53'),
(90, 94, 1, '2018-04-16 23:58:14'),
(125, 129, 1, '2018-04-18 23:09:11'),
(126, 130, 1, '2018-04-18 23:19:34'),
(130, 134, 1, '2018-04-18 23:26:08'),
(132, 136, 1, '2018-04-18 23:32:36'),
(135, 139, 1, '2018-04-18 23:45:10'),
(138, 142, 1, '2018-04-18 23:46:46'),
(140, 144, 1, '2018-04-18 23:47:53'),
(141, 145, 1, '2018-04-18 23:48:09'),
(142, 146, 1, '2018-04-18 23:48:12'),
(143, 147, 1, '2018-04-18 23:48:53'),
(147, 151, 1, '2018-04-19 00:57:15'),
(153, 157, 1, '2018-04-20 10:20:13'),
(155, 159, 1, '2018-04-20 16:12:42'),
(156, 162, 1, '2018-04-22 01:22:08'),
(157, 163, 1, '2018-04-22 01:27:28'),
(158, 164, 1, '2018-04-22 01:32:28'),
(159, 165, 1, '2018-04-22 01:34:54'),
(160, 166, 1, '2018-04-22 01:48:23'),
(161, 13, 1, '2018-04-22 23:54:15'),
(163, 16, 1, '2018-04-23 16:53:48'),
(171, 24, 1, '2018-04-23 23:43:22'),
(172, 25, 1, '2018-04-24 00:31:00'),
(173, 26, 1, '2018-04-24 10:36:00'),
(174, 27, 1, '2018-04-24 10:46:27'),
(177, 30, 1, '2018-04-24 23:00:04'),
(181, 34, 1, '2018-04-25 00:25:24'),
(182, 35, 1, '2018-04-25 11:28:42');
-- --------------------------------------------------------
--
-- Structure de la table `projecteur`
--
CREATE TABLE `projecteur` (
`id` int(11) NOT NULL,
`model` varchar(50) COLLATE utf8_unicode_ci NOT NULL,
`resolution` varchar(20) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `projecteur`
--
INSERT INTO `projecteur` (`id`, `model`, `resolution`) VALUES
(2, 'Projecteur Sharp', '2048x1092'),
(14, 'Projecteur Canon', '2048x1092');
-- --------------------------------------------------------
--
-- Structure de la table `regles`
--
CREATE TABLE `regles` (
`id` int(11) NOT NULL,
`lim_duree_reservation` int(11) NOT NULL,
`nbr_limite_par_jour` int(11) NOT NULL,
`nbr_limite_par_semaine` int(11) NOT NULL,
`nbr_max_reserv_parallel_par` int(11) NOT NULL,
`date_crea` datetime NOT NULL,
`date_modif` datetime DEFAULT NULL,
`duree_timeout` int(11) NOT NULL,
`max_res_parall` int(11) NOT NULL,
`dtype` varchar(255) COLLATE utf8_unicode_ci NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `regles`
--
INSERT INTO `regles` (`id`, `lim_duree_reservation`, `nbr_limite_par_jour`, `nbr_limite_par_semaine`, `nbr_max_reserv_parallel_par`, `date_crea`, `date_modif`, `duree_timeout`, `max_res_parall`, `dtype`) VALUES
(1, 3, 2, 5, 0, '2018-03-11 14:06:04', '2018-03-31 21:58:05', 55, 0, 'regles');
-- --------------------------------------------------------
--
-- Structure de la table `reservation`
--
CREATE TABLE `reservation` (
`id` int(11) NOT NULL,
`user_id` int(11) NOT NULL,
`ressource_id` int(11) DEFAULT NULL,
`statut` varchar(20) COLLATE utf8_unicode_ci NOT NULL,
`date_debut` datetime NOT NULL,
`date_fin` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `reservation`
--
INSERT INTO `reservation` (`id`, `user_id`, `ressource_id`, `statut`, `date_debut`, `date_fin`) VALUES
(2, 1, 1, 'En attente', '2018-04-23 10:00:00', '2018-04-23 12:00:00'),
(3, 1, 1, 'En attente', '2018-04-26 11:15:00', '2018-04-26 13:15:00'),
(4, 1, 1, 'En attente', '2018-04-25 15:00:00', '2018-04-25 17:00:00'),
(5, 1, 1, 'En attente', '2018-04-27 13:00:00', '2018-04-27 14:15:00'),
(6, 1, 3, 'En attente', '2018-04-24 10:00:00', '2018-04-24 12:00:00'),
(7, 2, 3, 'En attente', '2018-04-26 12:00:00', '2018-04-26 14:30:00'),
(8, 2, 3, 'En attente', '2018-04-23 13:30:00', '2018-04-23 16:30:00'),
(9, 1, 15, 'En attente', '2018-04-24 11:30:00', '2018-04-24 13:00:00'),
(10, 1, 15, 'En attente', '2018-04-27 12:00:00', '2018-04-27 15:00:00'),
(11, 2, 15, 'En attente', '2018-04-23 11:00:00', '2018-04-23 14:00:00'),
(13, 1, 13, 'En attente', '2018-04-25 16:55:00', '2018-04-25 19:00:00'),
(16, 1, 12, 'En attente', '2018-04-24 11:00:00', '2018-04-24 13:00:00'),
(24, 1, 4, 'En attente', '2018-04-24 10:00:00', '2018-04-24 11:30:00'),
(25, 1, 4, 'En attente', '2018-04-24 12:00:33', '2018-04-24 14:00:33'),
(26, 1, 12, 'En attente', '2018-04-24 13:45:00', '2018-04-24 15:45:00'),
(27, 1, 4, 'En attente', '2018-04-26 12:01:09', '2018-04-26 14:15:20'),
(30, 1, 4, 'En attente', '2018-04-27 10:30:00', '2018-04-27 13:00:00'),
(34, 1, 1, 'En attente', '2018-04-27 09:45:00', '2018-04-27 12:15:00'),
(35, 1, 3, 'En attente', '2018-04-26 09:15:00', '2018-04-26 10:45:00');
-- --------------------------------------------------------
--
-- Structure de la table `reservationprojecteur`
--
CREATE TABLE `reservationprojecteur` (
`id` int(11) NOT NULL,
`projecteur_id` int(11) NOT NULL,
`statut` varchar(20) COLLATE utf8_unicode_ci NOT NULL,
`date_debut` datetime NOT NULL,
`date_fin` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
-- --------------------------------------------------------
--
-- Structure de la table `ressource`
--
CREATE TABLE `ressource` (
`id` int(11) NOT NULL,
`categorie_id` int(11) NOT NULL,
`bar_code` varchar(255) COLLATE utf8_unicode_ci DEFAULT NULL,
`status` varchar(20) COLLATE utf8_unicode_ci NOT NULL,
`date_add` datetime NOT NULL,
`discr` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`last_check_date` datetime DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `ressource`
--
INSERT INTO `ressource` (`id`, `categorie_id`, `bar_code`, `status`, `date_add`, `discr`, `last_check_date`) VALUES
(1, 2, '51146465416546', 'Fonctionnel', '2018-03-31 14:59:24', '1', '2018-04-15 19:26:17'),
(2, 3, 'ddfq 252912df5d6516', 'Fonctionnel', '2018-04-01 00:30:42', '2', NULL),
(3, 2, '651sd1sdcfsd65csdc', 'Fonctionnel', '2018-04-07 13:34:01', '1', '2018-04-15 22:48:24'),
(4, 1, 'sdcsdc25df20dc20c2d2csd6547', 'Fonctionnel', '2018-04-07 13:37:32', '1', '2018-04-15 21:37:13'),
(12, 1, NULL, 'Fonctionnel', '2018-04-20 09:42:36', '1', '2018-04-20 10:15:54'),
(13, 1, NULL, 'Fonctionnel', '2018-04-20 15:10:55', '1', '2018-04-25 14:20:41'),
(14, 3, '21612654qsdf6qzerf4sdf35461351461', 'Fonctionnel', '2018-04-22 22:13:10', '2', NULL),
(15, 4, NULL, 'Fonctionnel', '2018-04-22 22:15:36', '3', NULL),
(16, 4, NULL, 'Fonctionnel', '2018-04-26 04:34:41', '3', NULL);
-- --------------------------------------------------------
--
-- Structure de la table `salle`
--
CREATE TABLE `salle` (
`id` int(11) NOT NULL,
`name` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
`numero_salle` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
--
-- Contenu de la table `salle`
--
INSERT INTO `salle` (`id`, `name`, `numero_salle`) VALUES
(15, '<NAME>', 9),
(16, 'Salle conferences', 15);
--
-- Index pour les tables exportées
--
--
-- Index pour la table `admin`
--
ALTER TABLE `admin`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `UNIQ_880E0D7692FC23A8` (`username_canonical`),
ADD UNIQUE KEY `UNIQ_880E0D76A0D96FBF` (`email_canonical`),
ADD UNIQUE KEY `UNIQ_880E0D76C05FB297` (`confirmation_token`);
--
-- Index pour la table `application`
--
ALTER TABLE `application`
ADD PRIMARY KEY (`id`),
ADD KEY `IDX_A45BDDC1D9BB2E9F` (`dispositif_id`);
--
-- Index pour la table `categorie`
--
ALTER TABLE `categorie`
ADD PRIMARY KEY (`id`);
--
-- Index pour la table `dispositif`
--
ALTER TABLE `dispositif`
ADD PRIMARY KEY (`id`);
--
-- Index pour la table `fos_user`
--
ALTER TABLE `fos_user`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `UNIQ_957A647992FC23A8` (`username_canonical`),
ADD UNIQUE KEY `UNIQ_957A6479A0D96FBF` (`email_canonical`),
ADD UNIQUE KEY `UNIQ_957A6479C05FB297` (`confirmation_token`);
--
-- Index pour la table `image`
--
ALTER TABLE `image`
ADD PRIMARY KEY (`id`),
ADD KEY `IDX_C53D045F928A171F` (`dispositive_id`);
--
-- Index pour la table `inventory`
--
ALTER TABLE `inventory`
ADD PRIMARY KEY (`id`);
--
-- Index pour la table `ldapconfig`
--
ALTER TABLE `ldapconfig`
ADD PRIMARY KEY (`id`);
--
-- Index pour la table `line_inventory`
--
ALTER TABLE `line_inventory`
ADD PRIMARY KEY (`id`),
ADD KEY `IDX_12EB14489329D25` (`resource_id`),
ADD KEY `IDX_12EB144CE430A85` (`inventaire_id`);
--
-- Index pour la table `message`
--
ALTER TABLE `message`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `UNIQ_B6BD307FA76ED395` (`user_id`);
--
-- Index pour la table `notification`
--
ALTER TABLE `notification`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `UNIQ_BF5476CAB83297E7` (`reservation_id`);
--
-- Index pour la table `projecteur`
--
ALTER TABLE `projecteur`
ADD PRIMARY KEY (`id`);
--
-- Index pour la table `regles`
--
ALTER TABLE `regles`
ADD PRIMARY KEY (`id`);
--
-- Index pour la table `reservation`
--
ALTER TABLE `reservation`
ADD PRIMARY KEY (`id`),
ADD KEY `IDX_42C84955A76ED395` (`user_id`),
ADD KEY `IDX_42C84955FC6CD52A` (`ressource_id`);
--
-- Index pour la table `reservationprojecteur`
--
ALTER TABLE `reservationprojecteur`
ADD PRIMARY KEY (`id`),
ADD KEY `IDX_A27C715C1992C1C2` (`projecteur_id`);
--
-- Index pour la table `ressource`
--
ALTER TABLE `ressource`
ADD PRIMARY KEY (`id`),
ADD KEY `IDX_939F4544BCF5E72D` (`categorie_id`);
--
-- Index pour la table `salle`
--
ALTER TABLE `salle`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT pour les tables exportées
--
--
-- AUTO_INCREMENT pour la table `admin`
--
ALTER TABLE `admin`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
--
-- AUTO_INCREMENT pour la table `application`
--
ALTER TABLE `application`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=8;
--
-- AUTO_INCREMENT pour la table `categorie`
--
ALTER TABLE `categorie`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;
--
-- AUTO_INCREMENT pour la table `fos_user`
--
ALTER TABLE `fos_user`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT pour la table `image`
--
ALTER TABLE `image`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT pour la table `inventory`
--
ALTER TABLE `inventory`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;
--
-- AUTO_INCREMENT pour la table `ldapconfig`
--
ALTER TABLE `ldapconfig`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
--
-- AUTO_INCREMENT pour la table `line_inventory`
--
ALTER TABLE `line_inventory`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=17;
--
-- AUTO_INCREMENT pour la table `message`
--
ALTER TABLE `message`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
--
-- AUTO_INCREMENT pour la table `notification`
--
ALTER TABLE `notification`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=183;
--
-- AUTO_INCREMENT pour la table `regles`
--
ALTER TABLE `regles`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
--
-- AUTO_INCREMENT pour la table `reservation`
--
ALTER TABLE `reservation`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=36;
--
-- AUTO_INCREMENT pour la table `reservationprojecteur`
--
ALTER TABLE `reservationprojecteur`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT pour la table `ressource`
--
ALTER TABLE `ressource`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=17;
--
-- Contraintes pour les tables exportées
--
--
-- Contraintes pour la table `application`
--
ALTER TABLE `application`
ADD CONSTRAINT `FK_A45BDDC1D9BB2E9F` FOREIGN KEY (`dispositif_id`) REFERENCES `dispositif` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `dispositif`
--
ALTER TABLE `dispositif`
ADD CONSTRAINT `FK_4719F6CDBF396750` FOREIGN KEY (`id`) REFERENCES `ressource` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `image`
--
ALTER TABLE `image`
ADD CONSTRAINT `FK_C53D045F928A171F` FOREIGN KEY (`dispositive_id`) REFERENCES `dispositif` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `line_inventory`
--
ALTER TABLE `line_inventory`
ADD CONSTRAINT `FK_12EB14489329D25` FOREIGN KEY (`resource_id`) REFERENCES `ressource` (`id`),
ADD CONSTRAINT `FK_12EB144CE430A85` FOREIGN KEY (`inventaire_id`) REFERENCES `inventory` (`id`);
--
-- Contraintes pour la table `message`
--
ALTER TABLE `message`
ADD CONSTRAINT `FK_B6BD307FA76ED395` FOREIGN KEY (`user_id`) REFERENCES `fos_user` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `notification`
--
ALTER TABLE `notification`
ADD CONSTRAINT `FK_BF5476CAB83297E7` FOREIGN KEY (`reservation_id`) REFERENCES `reservation` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `projecteur`
--
ALTER TABLE `projecteur`
ADD CONSTRAINT `FK_2D3297D6BF396750` FOREIGN KEY (`id`) REFERENCES `ressource` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `reservation`
--
ALTER TABLE `reservation`
ADD CONSTRAINT `FK_42C84955A76ED395` FOREIGN KEY (`user_id`) REFERENCES `fos_user` (`id`) ON DELETE CASCADE,
ADD CONSTRAINT `FK_42C84955FC6CD52A` FOREIGN KEY (`ressource_id`) REFERENCES `ressource` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `reservationprojecteur`
--
ALTER TABLE `reservationprojecteur`
ADD CONSTRAINT `FK_A27C715C1992C1C2` FOREIGN KEY (`projecteur_id`) REFERENCES `projecteur` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `ressource`
--
ALTER TABLE `ressource`
ADD CONSTRAINT `FK_939F4544BCF5E72D` FOREIGN KEY (`categorie_id`) REFERENCES `categorie` (`id`) ON DELETE CASCADE;
--
-- Contraintes pour la table `salle`
--
ALTER TABLE `salle`
ADD CONSTRAINT `FK_4E977E5CBF396750` FOREIGN KEY (`id`) REFERENCES `ressource` (`id`) ON DELETE CASCADE;
/*!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 */;
|
-- phpMyAdmin SQL Dump
-- version 4.8.5
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Mar 27, 2019 at 01:17 PM
-- Server version: 10.1.38-MariaDB
-- PHP Version: 7.2.15
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET AUTOCOMMIT = 0;
START TRANSACTION;
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: `cardb`
--
-- --------------------------------------------------------
--
-- Table structure for table `animals`
--
CREATE TABLE `animals` (
`id` int(11) NOT NULL,
`animal_name` varchar(100) NOT NULL,
`animal_type` varchar(100) NOT NULL,
`animal_owner_name` varchar(100) NOT NULL,
`animal_owner_email` varchar(100) NOT NULL,
`status` enum('active','deactivated') NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `animals`
--
INSERT INTO `animals` (`id`, `animal_name`, `animal_type`, `animal_owner_name`, `animal_owner_email`, `status`) VALUES
(4, 'Boen', 'Dog', '<NAME>', '<EMAIL>', 'active'),
(5, 'Ako', 'Cat', 'Ghea', '<EMAIL>', 'active'),
(7, 'Cathy', 'Dog', '<NAME>', '<EMAIL>', 'active'),
(8, 'Bruce', 'Fish', '<NAME>', '<EMAIL>', 'active');
-- --------------------------------------------------------
--
-- Table structure for table `car_rating`
--
CREATE TABLE `car_rating` (
`id` int(11) NOT NULL,
`car_id` int(11) NOT NULL,
`rating` int(11) NOT NULL,
`comment` text NOT NULL,
`comment_date` date NOT NULL,
`user` varchar(100) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `car_rating`
--
INSERT INTO `car_rating` (`id`, `car_id`, `rating`, `comment`, `comment_date`, `user`) VALUES
(1, 1, 4, 'test comment one', '2019-03-27', 'Anonymous'),
(2, 1, 4, 'test two comment', '2019-03-27', 'Anonymous');
-- --------------------------------------------------------
--
-- Table structure for table `parts`
--
CREATE TABLE `parts` (
`sellparts_id` int(11) NOT NULL,
`price_range` int(11) NOT NULL,
`parts_category` varchar(50) NOT NULL,
`brand` varchar(50) NOT NULL,
`color` varchar(10) NOT NULL,
`desc` text NOT NULL,
`note` varchar(200) NOT NULL,
`seller_id` int(11) NOT NULL,
`picture` varchar(200) NOT NULL,
`pictureTwo` varchar(200) NOT NULL,
`pictureThree` varchar(200) NOT NULL,
`seller_name` varchar(200) NOT NULL,
`post_date` date NOT NULL,
`status` enum('approved','pending','sold','removed') NOT NULL,
`model_name` varchar(200) NOT NULL,
`rfs` varchar(200) NOT NULL,
`update_part_on` date NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `parts`
--
INSERT INTO `parts` (`sellparts_id`, `price_range`, `parts_category`, `brand`, `color`, `desc`, `note`, `seller_id`, `picture`, `pictureTwo`, `pictureThree`, `seller_name`, `post_date`, `status`, `model_name`, `rfs`, `update_part_on`) VALUES
(1, 28290, 'WHEELS', 'COOPER', 'Black', 'The tyre that will never disappoint.', 'All-terrain tyre', 21, '5bf644465447d1.JPG', '5bf6444655f502.JPG', '5bf644465c7353.JPG', 'RUEY AGCANG', '2018-12-19', 'approved', 'Discoverer', 'Extra parts in the garage', '2018-12-19'),
(2, 0, 'TIRES', 'PIRELLI', 'Black', 'qweasd', 'None', 22, '5bfbe83a7dcb91957-Ferrari-250-GT-California.jpg', '5bfbe83a83a441957-Ferrari-250-TR-750x422.jpg', '5bfbe83a8544b1957-Ferrari-250-GT-California.jpg', 'REYNANTE CRISTOBAL', '2018-11-26', 'approved', 'Angel', 'None', '2018-03-02'),
(3, 29000, 'INTERNAL ACCESSORIES', 'COOPER', 'Black', 'The king of all.', 'None', 21, '5c0284aaa4c02566x566-WranglerTrippleMax-Nameontop-300x300.png', '5c0284aaaaabcoptimok415.jpg', '5c0284aaac15cwmtrk-angle2-300x300.png', 'RUEY AGCANG', '2018-12-01', 'pending', 'Discoverer', 'None', '2019-01-05');
-- --------------------------------------------------------
--
-- Table structure for table `part_rating`
--
CREATE TABLE `part_rating` (
`id` int(11) NOT NULL,
`part_id` int(11) NOT NULL,
`rating` int(11) NOT NULL,
`comment` text NOT NULL,
`user` varchar(100) NOT NULL,
`comment_date` date NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `part_rating`
--
INSERT INTO `part_rating` (`id`, `part_id`, `rating`, `comment`, `user`, `comment_date`) VALUES
(1, 1, 4, 'test one comment part', 'Anonymous', '2019-03-27');
-- --------------------------------------------------------
--
-- Table structure for table `product`
--
CREATE TABLE `product` (
`sellcar_id` int(11) NOT NULL,
`sellerId` int(11) NOT NULL,
`make` varchar(50) NOT NULL,
`price` int(11) NOT NULL,
`model` varchar(50) NOT NULL,
`pictureOne` varchar(200) NOT NULL,
`status` enum('sold','pending','approved','removed') NOT NULL,
`year` year(4) NOT NULL,
`transmission` enum('AT','MT','CVT') NOT NULL,
`seating_capacity` varchar(200) NOT NULL,
`bodystyle` varchar(200) NOT NULL,
`mileage` int(11) NOT NULL,
`color` varchar(10) NOT NULL,
`cylinder_engine` varchar(100) NOT NULL,
`door` varchar(10) NOT NULL,
`drive_type` varchar(20) NOT NULL,
`fuel_type` varchar(10) NOT NULL,
`note` varchar(200) NOT NULL,
`rfs` varchar(100) NOT NULL,
`pictureTwo` varchar(200) NOT NULL,
`pictureThree` varchar(200) NOT NULL,
`pictureFour` varchar(200) NOT NULL,
`pictureFive` varchar(200) NOT NULL,
`seller_name` varchar(200) NOT NULL,
`post_date` date NOT NULL,
`update_car_on` date NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `product`
--
INSERT INTO `product` (`sellcar_id`, `sellerId`, `make`, `price`, `model`, `pictureOne`, `status`, `year`, `transmission`, `seating_capacity`, `bodystyle`, `mileage`, `color`, `cylinder_engine`, `door`, `drive_type`, `fuel_type`, `note`, `rfs`, `pictureTwo`, `pictureThree`, `pictureFour`, `pictureFive`, `seller_name`, `post_date`, `update_car_on`) VALUES
(1, 21, 'NISSAN', 1800000, 'JUKE', '5bf63e146ddecjuke1.JPG', 'approved', 2018, 'CVT', '4', 'SUV', 12000, 'Yellow', 'Twin Turbo', '4', 'AWD', 'Diesel', 'None', 'Bought a new car already', '5bf63e14dced9juke2.JPG', '5bf63e14de6fbjuke3.JPG', '5bf63e14eacd8juke4.JPG', '5bf63e14ec54djuke5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-12-11'),
(2, 21, 'NISSAN', 919000, 'NAVARA', '5bf63f1163a02navara1.JPG', 'approved', 2018, 'AT', '4', 'Trucks', 500, 'Brown', 'Bi-turbo', '4', '4WD', 'Diesel', 'The prince of pick-up trucks', 'None', '5bf63f11661a8navara2.JPG', '5bf63f1167adfnavara3.JPG', '5bf63f11696f7navara4.JPG', '5bf63f116b3dfnavara5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-11-29'),
(3, 21, 'HYUNDAI', 526000, 'EON', '5bf63ffd8e8d4eon1.JPG', 'approved', 2016, 'MT', '4', 'Sedan', 20000, 'Red', 'V6', '5', 'FWD', 'Diesel', 'Needs to be maintained every 6 months', 'Too much car in the garage', '5bf63ffd901a5eon2.JPG', '5bf63ffd91beaeon3.JPG', '5bf63ffd93555eon4.JPG', '5bf63ffd9c558eon5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-12-18'),
(4, 21, 'HYUNDAI', 25520421, 'I20', '5bf640ac8cfd4i20-1.JPG', 'approved', 2018, 'CVT', '4', 'Sedan', 10000, 'Blue', '2.0 Diesel', '5', '4WD', 'Petrol', 'The most expensive sedan yet', 'Need funds', '5bf640ac8e8bfi20-2.JPG', '5bf640ac8ff01i20-3.JPG', '5bf640ac916f4i20-4.JPG', '5bf640ac9306ei20-5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-12-27'),
(5, 21, 'FORD', 1168000, 'ECOSPORT', '5bf64172577a3eco1.JPG', 'approved', 2017, 'AT', '5', 'SUV', 5000, 'Blue', '2.5 Turbo Diesel', '5', '4WD', 'Diesel', 'Fuel-efficient sub-compact SUV', 'Brought a brand new Ford Everest', '5bf64172590e9eco2.JPG', '5bf641725a8baeco3.JPG', '5bf641725c509eco4.JPG', '5bf641725dc97eco5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-11-30'),
(6, 21, 'FORD', 1695000, 'RANGER', '5bf641ddd4599ranger1.JPG', 'approved', 2018, 'AT', '5', 'Trucks', 2000, 'Brown', '3.0 Bi-turbo', '4', '4WD', 'Diesel', 'The king of pick-up trucks', 'Too much car in the garage', '5bf641dddb9ffranger2.JPG', '5bf641dddd2ebranger3.JPG', '5bf641dde109cranger4.JPG', '5bf641dde2a61ranger5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-12-13'),
(7, 21, 'FORD', 2228000, 'EVEREST', '5bf64287c7417eve1.JPG', 'approved', 2018, 'CVT', '7', 'SUV', 1000, 'Red', 'V8 engine', '5', '4WD', 'Petrol', 'Fuel-hungry type of SUV', 'Cannot accommodate it in the garage', '5bf64287c8baeeve2.JPG', '5bf64287cd39feve3.JPG', '5bf64287ceb73eve4.JPG', '5bf64287d0594eve5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-12-31'),
(8, 21, 'HONDA', 1288000, 'CIVIC', '5bf642fb9ce5dcivic1.JPG', 'approved', 2017, 'CVT', '4', 'Sedan', 15000, 'Red', '2.0 Diesel', '5', 'RWD', 'Diesel', 'One of the most popular city car', 'Need funds for new SUV', '5bf642fba3050civic2.JPG', '5bf642fba47e5civic3.JPG', '5bf642fba5d3fcivic4.JPG', '5bf642fba7a8acivic5.JPG', 'RUEY AGCANG', '2018-11-22', '2018-12-23'),
(10, 21, 'TOYOTA', 700000, 'WIGO', '5c0350817e9f4wigo1.JPG', 'approved', 2018, 'AT', '5', 'Sedan', 20000, 'Red', 'V8 engine', '5', 'FWD', 'Diesel', 'None', 'None', '5c035081a803awigo2.JPG', '5c035081aaf04wigo3.JPG', '5c035081b473bwigo4.JPG', '5c035081b6ce4wigo5.JPG', 'RUEY AGCANG', '2018-12-02', '2019-01-01');
-- --------------------------------------------------------
--
-- Table structure for table `user`
--
CREATE TABLE `user` (
`id` int(11) NOT NULL,
`email` varchar(20) NOT NULL,
`password` varchar(20) NOT NULL,
`fname` varchar(50) NOT NULL,
`lname` varchar(50) NOT NULL,
`address` varchar(200) NOT NULL,
`contact` varchar(11) NOT NULL,
`type` enum('seller','admin') NOT NULL,
`status` enum('active','deactivated') NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `user`
--
INSERT INTO `user` (`id`, `email`, `password`, `fname`, `lname`, `address`, `contact`, `type`, `status`) VALUES
(20, '<EMAIL>', 'admin', 'Ruey', 'Agcang', 'Nasipit, Talamban, Cebu City, Philippines', '09476436562', 'admin', 'active'),
(21, '<EMAIL>', 'ruey1234', 'Ruey', 'Agcang', 'Bahak, Liloan, Cebu', '424-4485', 'seller', 'deactivated'),
(22, '<EMAIL>', 'qwertyui', 'reynante', 'cristobal', 'Bahak, Poblacion, Liloan, Cebu', '09171552501', 'seller', 'deactivated');
--
-- Indexes for dumped tables
--
--
-- Indexes for table `animals`
--
ALTER TABLE `animals`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `car_rating`
--
ALTER TABLE `car_rating`
ADD PRIMARY KEY (`id`),
ADD KEY `FK_carRating` (`car_id`);
--
-- Indexes for table `parts`
--
ALTER TABLE `parts`
ADD PRIMARY KEY (`sellparts_id`),
ADD KEY `seller_id` (`seller_id`);
--
-- Indexes for table `part_rating`
--
ALTER TABLE `part_rating`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `product`
--
ALTER TABLE `product`
ADD PRIMARY KEY (`sellcar_id`),
ADD KEY `sellerId` (`sellerId`);
--
-- Indexes for table `user`
--
ALTER TABLE `user`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `animals`
--
ALTER TABLE `animals`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=9;
--
-- AUTO_INCREMENT for table `car_rating`
--
ALTER TABLE `car_rating`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;
--
-- AUTO_INCREMENT for table `parts`
--
ALTER TABLE `parts`
MODIFY `sellparts_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
--
-- AUTO_INCREMENT for table `part_rating`
--
ALTER TABLE `part_rating`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;
--
-- AUTO_INCREMENT for table `product`
--
ALTER TABLE `product`
MODIFY `sellcar_id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=11;
--
-- AUTO_INCREMENT for table `user`
--
ALTER TABLE `user`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=23;
--
-- Constraints for dumped tables
--
--
-- Constraints for table `car_rating`
--
ALTER TABLE `car_rating`
ADD CONSTRAINT `FK_carRating` FOREIGN KEY (`car_id`) REFERENCES `product` (`sellcar_id`);
--
-- Constraints for table `parts`
--
ALTER TABLE `parts`
ADD CONSTRAINT `parts_ibfk_1` FOREIGN KEY (`seller_id`) REFERENCES `user` (`id`);
--
-- Constraints for table `product`
--
ALTER TABLE `product`
ADD CONSTRAINT `product_ibfk_1` FOREIGN KEY (`sellerId`) REFERENCES `user` (`id`);
COMMIT;
/*!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 */;
|
-- sqlite3 wsu-twitter.db
-- sqlite> .read makedb.sql
-- sqlite> .exit
-- sudo chgrp www .
-- sudo chgrp www wsu-twitter.db
-- chmod 664 wsu-twitter.db
-- chmod 775 .
CREATE TABLE users (user_id INTEGER PRIMARY KEY AUTOINCREMENT,
username VARCHAR(45),
passwd_hash VARCHAR(45),
session_token VARCHAR(45) DEFAULT "0");
INSERT INTO users (user_id, username, passwd_hash)
VALUES(0, 'wcochran', '<PASSWORD>');
CREATE TABLE TWEETS (tweet_id INTEGER PRIMARY KEY AUTOINCREMENT,
user_id INTEGER,
time_stamp DATE DEFAULT (datetime('now','localtime')),
isdeleted INTEGER DEFAULT 0,
tweet VARCHAR(200));
INSERT INTO tweets (user_id, tweet)
VALUES (0, 'Welcome to the CS 458 Twitter Service');
|
--Create a user defined stored procedure, named usp_CancelFlights
--The procedure must cancel all flights on which the arrival time is before the departure time. Cancel means you need to leave the departure and arrival time empty.
CREATE PROC usp_CancelFlights
AS
UPDATE Flights
SET DepartureTime = NULL, ArrivalTime = NULL
WHERE ArrivalTime > DepartureTime
|
<filename>db/ctc_seeds.sql
-- department
INSERT INTO department(name)
VALUES("Hematology/Oncology"), ("Radiation Oncology"), ("Front Office"), ("Billing"), ("Administration");
-- role
INSERT INTO role(title, salary, deptid)
VALUES("RN (Hem/Onc)", "75000.00", 1);
INSERT INTO role(title, salary, deptid)
VALUES("RN (Rad/Onc)", "85000.00", 2);
INSERT INTO role(title, salary, deptid)
VALUES("MD (Hem/Onc)", "350000.00", 1);
INSERT INTO role(title, salary, deptid)
VALUES("MD (Rad/Onc)", "420000.00", 2);
INSERT INTO role(title, salary, deptid)
VALUES("MA", "35000.00", 1);
INSERT INTO role(title, salary, deptid)
VALUES("MA", "35000.00", 2);
INSERT INTO role(title, salary, deptid)
VALUES("F/O Coordinator", "27000.00", 3);
INSERT INTO role(title, salary, deptid)
VALUES("A/R Specialist", "45000.00", 4);
INSERT INTO role(title, salary, deptid)
VALUES("Coding Specialist", "54000.00", 4);
INSERT INTO role(title, salary, deptid)
VALUES("Manager", "65000.00", 5);
INSERT INTO role(title, salary, deptid)
VALUES("Practice Administrator", "70000.00", 5);
|
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
SET time_zone = "+00:00";
CREATE TABLE `pins` (
`id` int(11) NOT NULL,
`user_id` varchar(255) NOT NULL,
`title` varchar(255) NOT NULL,
`description` text,
`phrase` text,
`url` text NOT NULL,
`timestamp` int(11) NOT NULL DEFAULT '0',
`tags` text,
`created_at` datetime NOT NULL,
`updated_at` datetime NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
-- CREATE TABLE `rel_pin_tags` (
-- `pin_id` int(11) unsigned NOT NULL DEFAULT '0',
-- `tag_id` int(11) unsigned NOT NULL DEFAULT '0',
-- `created_at` datetime NOT NULL,
-- `updated_at` datetime NOT NULL
-- ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
--
-- CREATE TABLE `tags` (
-- `id` int(11) NOT NULL,
-- `user_id` varchar(255) NOT NULL COMMENT 'ユーザID',
-- `name` varchar(255) NOT NULL,
-- `created_at` datetime NOT NULL,
-- `updated_at` datetime NOT NULL
-- ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
CREATE TABLE `users` (
`id` int(11) NOT NULL COMMENT 'ID',
`user_id` varchar(255) NOT NULL COMMENT 'ユーザID',
`facebook_id` varchar(255) DEFAULT NULL COMMENT 'FacebookID',
`github_id` varchar(255) DEFAULT NULL COMMENT 'GithubID',
`twitter_id` varchar(255) DEFAULT NULL COMMENT 'TwitterID',
`token` varchar(64) NOT NULL COMMENT 'アクセストークン',
`profile_url` text,
`username` varchar(64) NOT NULL COMMENT 'ユーザ名',
`created_at` datetime NOT NULL COMMENT '作成日時',
`updated_at` datetime NOT NULL COMMENT '更新日時'
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Indexes for table `pins`
--
ALTER TABLE `pins`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `rel_pin_tags`
--
-- ALTER TABLE `rel_pin_tags`
-- ADD KEY `pin_tag_id` (`pin_id`,`tag_id`);
--
-- Indexes for table `tags`
--
-- ALTER TABLE `tags`
-- ADD PRIMARY KEY (`id`);
--
-- Indexes for table `users`
--
ALTER TABLE `users`
ADD PRIMARY KEY (`user_id`),
ADD UNIQUE KEY `token` (`token`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `pins`
--
ALTER TABLE `pins`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `tags`
--
-- ALTER TABLE `tags`
-- MODIFY `id` int(11) NOT NULL AUTO_INCREMENT;
--
-- AUTO_INCREMENT for table `users`
--
ALTER TABLE `users`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT COMMENT 'ユーザID',AUTO_INCREMENT;
|
-- phpMyAdmin SQL Dump
-- version 5.0.2
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Jun 19, 2020 at 05:09 PM
-- Server version: 10.4.13-MariaDB
-- PHP Version: 7.4.7
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
START TRANSACTION;
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: `db_elearning`
--
-- --------------------------------------------------------
--
-- Table structure for table `admin`
--
CREATE TABLE `admin` (
`id` int(64) NOT NULL,
`username` varchar(128) NOT NULL,
`password` varchar(128) NOT NULL,
`email` varchar(128) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `admin`
--
INSERT INTO `admin` (`id`, `username`, `password`, `email`) VALUES
(0, 'admin', <PASSWORD>.', '<EMAIL>');
-- --------------------------------------------------------
--
-- Table structure for table `guru`
--
CREATE TABLE `guru` (
`nip` int(64) NOT NULL,
`email` varchar(255) NOT NULL,
`nama_guru` varchar(128) NOT NULL,
`password` varchar(255) NOT NULL,
`nama_mapel` varchar(64) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `guru`
--
INSERT INTO `guru` (`nip`, `email`, `nama_guru`, `password`, `nama_mapel`) VALUES
(214748364, '<EMAIL>', '<NAME>', '', 'Pendidikan Agama Islam'),
(214748365, '<EMAIL>', 'Saauky', <PASSWORD>', 'Matematika'),
(1819107728, '<EMAIL>', '<NAME>', <PASSWORD>', 'Matematika');
-- --------------------------------------------------------
--
-- Table structure for table `kelas`
--
CREATE TABLE `kelas` (
`id` int(255) NOT NULL,
`kelas` varchar(128) NOT NULL,
`nama_siswa` varchar(128) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
-- --------------------------------------------------------
--
-- Table structure for table `materi`
--
CREATE TABLE `materi` (
`id` int(11) NOT NULL,
`nama_guru` varchar(128) NOT NULL,
`nama_mapel` varchar(128) NOT NULL,
`video` varchar(255) NOT NULL,
`deskripsi` varchar(1024) NOT NULL,
`kelas` varchar(128) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `materi`
--
INSERT INTO `materi` (`id`, `nama_guru`, `nama_mapel`, `video`, `deskripsi`, `kelas`) VALUES
(38, 'Saauky', 'Matematika', 'Matematika_-_Dummy_-_1.mp4', ' RG Squad, siapa yang pernah dengar kata aljabar? Ini merupakan satu cabang matematika dalam pemecahan masalah dengan menggunakan huruf-huruf untuk mewakili angka-angka. Berasal dari bahasa Arab, al-jabr yang artinya penyelesaian. Kamu tahu siapa penemunya? Ia merupakan cendikiawan bernama Al-Khawarizmi. Sekarang, mari kita simak lebih lanjut tentang definisi dan bentuk-bentuk aljabar secara lebih mendalam ya! s', 'X'),
(42, 'Saauky', 'Matematika', 'Matematika_-_Dummy_-_1.mp4', 'Dalam matematika dan ilmu komputer, Aljabar Boolean adalah struktur aljabar yang "mencakup intisari" operasi logika AND, OR, NOR, dan NAND dan juga teori himpunan untuk operasi union, interseksi dan komplemen. Penamaan Aljabar Boolean sendiri berasal dari nama seorang matematikawan asal Inggris, bernama George Boole.', 'X'),
(43, 'Saauky', 'Matematika', 'Matematika_-_Dummy_-_2.mp4', 'Aljabar linear adalah bidang studi matematika yang mempelajari sistem persamaan linear dan solusinya, vektor, serta transformasi linear. Matriks dan operasinya juga merupakan hal yang berkaitan erat dengan bidang aljabar linear.', 'XI'),
(44, 'Saauky', 'Matematika', 'Matematika_-_Dummy_3.mp4', 'Vektor merupakan kajian aljabar yang biasanya digunakan untuk memecahkan permasalahan fisika seperti gerak, gaya, dan sebagainya. ... Sebuah vektor bisa dinyatakan dalam bentuk geometri yang digambarkan sebagai sebuah ruas garis dengan arah tertentu dimana salah satunya merupakan pangkal dan satunya lagi merupakan ujung.', 'XI'),
(45, 'Saauky', 'Matematika', 'Matematika_-_Dummy_4.mp4', 'Vektor dalam matematika dan fisika adalah objek geometri yang memiliki besar dan arah. Vektor jika dilambangkan dengan tanda panah. Besar vektor proporsional dengan panjang panah dan arahnya bertepatan dengan arah panah. Vektor dapat melambangkan perpindahan dari titik A ke B. Vektor sering ditandai sebagai', 'XII'),
(46, 'Saauky', 'Matematika', 'Matematika_-_Dummy_5.mp4', 'Pecahan, atau disebut fraksi adalah istilah dalam matematika yang terdiri dari pembilang dan penyebut. Hakikat transaksi dalam bilangan pecahan adalah bagaimana cara menyederhanakan pembilang dan penyebut.', 'XII'),
(47, 'Zaaidan', 'IPA', 'IPA_-_Dummy_1.mp4', 'Fisika adalah salah satu disiplin akademik paling tua, mungkin yang tertua melalui astronomi yang juga termasuk di dalamnya.[6] Lebih dari dua milenia, fisika menjadi bagian dari Ilmu Alam bersama dengan kimia, biologi, dan cabang tertentu matematika, tetapi ketika munculnya revolusi ilmiah pada abad ke-17, ilmu alam berkembang sebagai program penelitian sendiri.[b] Fisika berkembang dengan banyak spesialisasi bidang ilmu lain, seperti biofisika dan kimia kuantum, dan batasan fisiknya tidak didefinisikan dengan jelas. Ilmu baru dalam fisika terkadang digunakan untuk menjelaskan mekanisme dasar sains lainnya[3] serta membuka jalan area penelitian lainnya seperti matematika dan filsafat.', 'X'),
(50, 'Zaaidan', 'IPA', 'IPA_-_Dummy_2.mp4', 'Kristalisasi adalah proses pembentukan bahan padat dari pengendapan larutan, melt, atau lebih jarang pengendapan langsung dari gas. Kristalisasi juga merupakan teknik pemisahan kimia antara bahan padat-cair, di mana terjadi perpindahan massa dari suat zat terlarut dari cairan larutan ke fase kristal padat', 'X'),
(51, 'Zaaidan', 'IPA', 'IPA_-_Dummy_3.mp4', 'Peleburan adalah proses reduksi bijih sehingga menjadi logam unsur yang dapat digunakan berbagai macam zat seperti karbid, hidrogen, logam aktif atau dengan cara elektrolisis. Pemilihan zat pereduksi ini tergantung dari kereaktifan masing-masing zat.', 'XI'),
(52, 'Zaaidan', 'IPA', 'IPA_-_Dummy_4.mp4', 'Pencairan, pelelehan atau Peleburan adalah proses yang menghasilkan perubahan fase zat dari padat ke cair. Energi internal dari zat padat meningkat mencapai temperatur tertentu saat zat ini berubah menjadi cair.Benda yang telah mencair sepenuhnya disebut benda cair.', 'XI'),
(53, 'Zaaidan', 'IPA', 'IPA_-_Dummy_5.mp4', 'Dalam ilmu fisika dan kimia, pembekuan adalah proses di mana cairan berubah menjadi padatan. Titik beku adalah temperatur di mana hal ini terjadi. Peleburan, adalah proses kebalikan dari pembekuan di mana padatan berubah manjadi cairan. Pada sebagian besar zat, titik beku dan titik lebur biasanya sama.', 'XII'),
(54, 'Zaaidan', 'IPA', 'IPA_-_Dummy_6.mp4', 'Teknologi pembekuan makanan adalah teknologi mengawetkan makanan dengan menurunkan temperaturnya hingga di bawah titik beku air.', 'XII'),
(55, 'Khaairan', 'Bahasa Inggris', 'Inggris_-_Dummy_1.mp4', 'Bahasa Inggris adalah bahasa Jermanik yang pertama kali dituturkan di Inggris pada Abad Pertengahan Awal dan saat ini merupakan bahasa yang paling umum digunakan di seluruh dunia.[4] Bahasa Inggris dituturkan sebagai bahasa pertama oleh mayoritas penduduk di berbagai negara, termasuk Britania Raya, Irlandia, Amerika Serikat, Kanada, Australia, Selandia Baru, dan sejumlah negara-negara Karibia; serta menjadi bahasa resmi di hampir 60 negara berdaulat. Bahasa Inggris adalah bahasa ibu ketiga yang paling banyak dituturkan di seluruh dunia, setelah bahasa Mandarin dan bahasa Spanyol.[5] Bahasa Inggris juga digunakan sebagai bahasa kedua dan bahasa resmi oleh Uni Eropa, Negara Persemakmuran, dan Perserikatan Bangsa-Bangsa, serta beragam organisasi lainnya.', 'X'),
(56, 'Khaairan', 'Bahasa Inggris', 'Inggris_-_Dummy_2.mp4', 'Bahasa Inggris berkembang pertama kali di Kerajaan Anglo-Saxon Inggris dan di wilayah yang saat ini membentuk Skotlandia tenggara. Setelah meluasnya pengaruh Britania Raya pada abad ke-17 dan ke-20 melalui Imperium Britania, bahasa Inggris tersebar luas di seluruh dunia.[6][7][8] Di samping itu, luasnya penggunaan bahasa Inggris juga disebabkan oleh penyebaran kebudayaan dan teknologi Amerika Serikat yang mendominasi di sepanjang abad ke-20.[9] Hal-hal tersebut telah menyebabkan bahasa Inggris saat ini menjadi bahasa utama dan secara tidak resmi (de facto) dianggap sebagai lingua franca di berbagai belahan dunia.[10][11]', 'X'),
(57, 'Khaairan', 'Bahasa Inggris', 'Inggris_-_Dummy_3.mp4', 'Menurut sejarahnya, bahasa Inggris berasal dari peleburan beragam dialek terkait, yang saat ini secara kolektif dikenal sebagai bahasa Inggris Kuno, yang dibawa ke pantai timur Pulau Britania oleh pendatang Jermanik (Anglo-Saxons) pada abad ke-5; kata English\' berasal dari nama Angles.[12] Suku Anglo-Saxons ini sendiri berasal dari wilayah Angeln (saat ini Schleswig-Holstein, Jerman). Bahasa Inggris awal juga dipengaruhi oleh bahasa Norse Kuno setelah Viking menaklukkan Inggris pada abad ke-9 dan ke-10.', 'XI'),
(58, 'Khaairan', 'Bahasa Inggris', 'Inggris_-_Dummy_4.mp4', 'Penaklukan Normandia terhadap Inggris pada abad ke-11 menyebabkan bahasa Inggris juga mendapat pengaruh dari bahasa Prancis Norman, dan kosakata serta ejaan dalam bahasa Inggris mulai dipengaruhi oleh bahasa Latin Romawi (meskipun bahasa Inggris sendiri bukanlah rumpun bahasa Romawi),[13][14] yang kemudian dikenal dengan bahasa Inggris Pertengahan. Pergeseran Vokal yang dimulai di Inggris bagian selatan pada abad ke-15 adalah salah satu peristiwa bersejarah yang menandai peralihan bahasa Inggris Pertengahan menjadi bahasa Inggris Modern.', 'XI'),
(59, 'Khaairan', 'Bahasa Inggris', 'Inggris_-_Dummy_5.mp4', 'Selain Anglo-Saxons dan Prancis Norman, sejumlah besar kata dalam bahasa Inggris juga berakar dari bahasa Latin, karena Latin adalah lingua franca Gereja Kristen dan bahasa utama di kalangan intelektual Eropa,[15] dan telah menjadi dasar kosakata bagi bahasa Inggris modern.', 'XII'),
(60, 'Khaairan', 'Bahasa Inggris', 'Inggris_-_Dummy_6.mp4', 'Karena telah mengalami perpaduan beragam kata dari berbagai bahasa di sepanjang sejarah, bahasa Inggris modern memiliki kosakata yang sangat banyak, dengan pengejaan yang kompleks dan tidak teratur (irregular), khususnya vokal. Bahasa Inggris modern tidak hanya merupakan perpaduan dari bahasa-bahasa Eropa, tetapi juga dari berbagai bahasa di seluruh dunia. Oxford English Dictionary memuat daftar lebih dari 250.000 kata berbeda, tidak termasuk istilah-istilah teknis, sains, dan bahasa gaul yang jumlahnya juga sangat banyak.[16][17]', 'XII'),
(61, '<NAME>', 'Bahasa Indonesia', 'Indonesia_-_Dummy_1.mp4', 'Bahasa Indonesia adalah bahasa Melayu yang dijadikan sebagai bahasa resmi Republik Indonesia[1] dan bahasa persatuan bangsa Indonesia.[2] Bahasa Indonesia diresmikan penggunaannya setelah Proklamasi Kemerdekaan Indonesia, tepatnya sehari sesudahnya, bersamaan dengan mulai berlakunya konstitusi. Di Timor Leste, bahasa Indonesia berstatus sebagai bahasa kerja.', 'X'),
(62, '<NAME>', 'Bahasa Indonesia', 'Indonesia_-_Dummy_2.mp4', 'Dari sudut pandang linguistik, bahasa Indonesia adalah salah satu dari banyak varietas bahasa Melayu.[3] Dasar yang dipakai sebagai dasar bahasa Indonesia baku adalah bahasa Melayu Tinggi ("Riau").[4][5] Dalam perkembangannya, ia mengalami perubahan akibat penggunaannya sebagai bahasa kerja di lingkungan administrasi kolonial dan berbagai proses pembakuan sejak awal abad ke-20. Penamaan "bahasa Indonesia" diawali sejak dicanangkannya Sumpah Pemuda, 28 Oktober 1928, untuk menghindari kesan "imperialisme bahasa" apabila nama bahasa Melayu tetap digunakan.[6] Proses ini menyebabkan berbedanya bahasa Indonesia saat ini dari varian bahasa Melayu yang digunakan di Riau maupun Semenanjung Malaya. Hingga saat ini, bahasa Indonesia merupakan bahasa yang hidup, yang terus menghasilkan kata-kata baru, baik melalui penciptaan maupun penyerapan dari bahasa daerah dan bahasa asing.', 'X'),
(63, '<NAME>', 'Bahasa Indonesia', 'Indonesia_-_Dummy_3.mp4', 'Meskipun dipahami dan dituturkan oleh lebih dari 90% warga Indonesia, bahasa Indonesia bukanlah bahasa ibu bagi kebanyakan penuturnya. Sebagian besar warga Indonesia menggunakan salah satu dari 748 bahasa yang ada di Indonesia sebagai bahasa ibu.[7] Istilah "bahasa Indonesia" paling umum dikaitkan dengan bahasa baku yang digunakan dalam situasi formal.[4] Ragam bahasa baku tersebut berhubungan diglosik dengan bentuk-bentuk bahasa Melayu vernacular yang digunakan sebagai peranti komunikasi sehari-hari.[4] Artinya, penutur bahasa Indonesia kerap kali menggunakan versi sehari-hari (colloquial) dan/atau mencampuradukkan dengan dialek Melayu lainnya atau bahasa ibunya. Meskipun demikian, bahasa Indonesia digunakan sangat luas di perguruan-perguruan, di media massa, sastra, perangkat lunak, surat-menyurat resmi, dan berbagai forum publik lainnya,[8] sehingga dapatlah dikatakan bahwa bahasa Indonesia digunakan oleh semua warga Indonesia.', 'XI'),
(64, '<NAME>', 'Bahasa Indonesia', 'Indonesia_-_Dummy_4.mp4', 'Aksara pertama dalam bahasa Melayu atau Jawi ditemukan di pesisir tenggara Pulau Sumatra, menunjukkan bahwa bahasa ini menyebar ke berbagai tempat di Nusantara dari wilayah ini, berkat penggunaannya oleh Kerajaan Sriwijaya yang menguasai jalur perdagangan. Istilah Melayu atau sebutan bagi wilayahnya sebagai Malaya sendiri berasal dari Kerajaan Malayu yang bertempat di Batang Hari, Jambi.', 'XI'),
(65, '<NAME>', 'Bahasa Indonesia', 'Indonesia_-_Dummy_5.mp4', 'stilah Melayu atau Malayu berasal dari Kerajaan Malayu, sebuah kerajaan Hindu-Buddha pada abad ke-7 di hulu sungai Batanghari, Jambi di pulau Sumatra, jadi secara geografis semula hanya mengacu kepada wilayah kerajaan tersebut yang merupakan sebagian dari wilayah pulau Sumatra. Dalam perkembangannya, pemakaian istilah Melayu mencakup wilayah geografis yang lebih luas dari wilayah Kerajaan Malayu tersebut, mencakup negeri-negeri di pulau Sumatra sehingga pulau tersebut disebut juga Bumi Melayu seperti disebutkan dalam Kakawin Nagarakretagama.', 'XII'),
(67, '<NAME>', 'Bahasa Indonesia', 'Indonesia_-_Dummy_6.mp4', 'Ibu kota Kerajaan Melayu semakin mundur ke pedalaman karena serangan Sriwijaya dan masyarakatnya diaspora keluar Bumi Melayu, belakangan masyarakat pendukungnya yang mundur ke pedalaman berasimilasi ke dalam masyarakat Minangkabau menjadi klan Malayu (suku Melayu Minangkabau) yang merupakan salah satu marga di Sumatra Barat. Sriwijaya berpengaruh luas hingga ke Filipina membawa penyebaran Bahasa Melayu semakin meluas, tampak dalam prasasti Keping Tembaga Laguna.\r\n\r\nBahasa Melayu kuno yang berkembang di Bumi Melayu tersebut berlogat "o" seperti Melayu Jambi, Minangkabau, Kerinci, Palembang dan Bengkulu. Semenanjung Malaka dalam Nagarakretagama disebut Hujung Medini artinya Semenanjung Medini.', 'XII'),
(69, '<NAME>', 'Pendidikan Agama Islam', 'Agama_Islam_-_Dummy_-_1.mp4', 'Islam (bahasa Arab: ???????, translit. al-isl?m?, Tentang suara ini dengarkan) adalah salah satu agama dari kelompok agama yang diterima oleh seorang nabi (agama samawi) yang mengajarkan monoteisme tanpa kompromi, iman terhadap wahyu, iman terhadap akhir zaman, dan tanggung jawab.[1] Bersama para pengikut Yudaisme dan Kekristenan, seluruh muslim–pengikut ajaran Islam–adalah anak turun Ibrahim.[2] Islam diikuti oleh 1,8 miliar orang di seluruh dunia sehingga menjadi agama terbesar kedua setelah Kristen.[3]', 'X'),
(70, '<NAME>', 'Pendidikan Agama Islam', 'Agama_Islam_-_Dummy_-_2.mp4', 'Kata “isl?m” berasal dari bahasa Arab aslama - yuslimu dengan arti semantik sebagai berikut: tunduk dan patuh (khadha‘a wa istaslama), berserah diri, menyerahkan, memasrahkan (sallama), mengikuti (atba‘a), menunaikan, menyampaikan (add?), masuk dalam kedamaian, keselamatan, atau kemurnian (dakhala fi al-salm au al-silm au al-sal?m).[4] Dari istilah-istilah lain yang akar katanya sama, “isl?m” berhubungan erat dengan makna keselamatan, kedamaian, dan kemurnian.[5]', 'X'),
(71, '<NAME>', 'Pendidikan Agama Islam', 'Agama_Islam_-_Dummy_-_3.mp4', 'Islam dapat juga disebut dengan iman, millah, dan syariah dalam pengertiannya sebagai aturan yang diturunkan oleh Allah melalui para utusan yang mencakup kepercayaan, keyakinan, adab, akhlak, perintah, dan larangan.[9] Agama Islam berdasarkan kewajiban untuk berserah diri dan menunaikan ajarannya disebut islam; jika dilihat berdasarkan kepercayaan terhadap Allah dan yang Dia turunkan, maka disebut iman; karena Islam itu diktatif dan terdokumentasikan, maka disebut millah; dan karena sumber hukumnya adalah Allah, maka disebut syariah.[9]', 'XI'),
(72, '<NAME>', 'Pendidikan Agama Islam', 'Agama_Islam_-_Dummy_-_4.mp4', 'Allah, menurut ajaran Islam, adalah satu-satunya Tuhan yang berhak disembah, memiliki nama-nama terbaik, dan memiliki sifat dan karakter tertinggi.[11] Ajaran monoteisme Islam disebut tauhid, yang didefinisikan sebagai pengesaan Allah dalam hal-hal yang menjadi kekhususan Tuhan dan yang Dia wajibkan.[12] Pengesaan Allah dalam hal-hal kekhususan Tuhan dibagi menjadi dua bahasan: tauhid rububiyah dan tauhid asma\' wash-shifat, sedangkan pengesaan Allah dalam hal-hal yang Dia wajibkan dibahas dalam tauhid uluhiyah.[13]', 'XI'),
(73, '<NAME>', 'Pendidikan Agama Islam', 'Agama_Islam_-_Dummy_-_4.mp4', 'Dalam tauhid rububiyah, Allah diakui sebagai satu-satunya Rabb (Yang Menguasai), sehingga semua selain Allah adalah ‘abd (hamba/budak/yang dikuasai).[14] Allah adalah Rabb Yang Berkuasa dalam penciptaan, pengurusan, dan kerajaan alam semesta.[15] Allah sebagai satu-satunya Pencipta adalah juga Yang Memberi rezeki, Yang Menghidupkan, Yang Mematikan, serta Yang Memberi kebaikan dan keburukan.[16] Allah yang mengurus segala sesuatu; semua urusan yang Dia tangani adalah kebaikan; dan Allah Mahakuasa terhadap apa yang Dia kehendaki.[16] Dalilnya adalah ayat dalam Alquran, “Segala penciptaan dan urusan menjadi hak-Nya.”[Al-A\'raf:54][15]', 'XII'),
(76, '<NAME>', 'Pendidikan Agama Islam', 'Agama_Islam_-_Dummy_-_6.mp4', 'Islam adalah salah satu agama dari kelompok agama yang diterima oleh seorang nabi yang mengajarkan monoteisme tanpa kompromi, iman terhadap wahyu, iman terhadap akhir zaman, dan tanggung jawab. Bersama para pengikut Yudaisme dan Kekristenan, seluruh muslim–pengikut ajaran Islam–adalah anak turun Ibrahim.', 'XII'),
(77, 'Saauky', 'Matematika', 'Agama_Islam_-_Dummy_-_6.mp4', 'Test', 'X');
-- --------------------------------------------------------
--
-- Table structure for table `siswa`
--
CREATE TABLE `siswa` (
`id` int(64) NOT NULL,
`nama` varchar(255) NOT NULL,
`password` varchar(255) NOT NULL,
`email` varchar(128) NOT NULL,
`image` varchar(255) NOT NULL,
`is_active` int(1) NOT NULL,
`date_created` int(64) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
--
-- Dumping data for table `siswa`
--
INSERT INTO `siswa` (`id`, `nama`, `password`, `email`, `image`, `is_active`, `date_created`) VALUES
(39, '<NAME>', '$2y$10$djI2M/FQH2k3H7b6tLK5X.MZG1R.wrARoR6NerH3tsScNnsNCnexa', '<EMAIL>', '73349393_156861225523800_2119508204152772215_n_(1)6.jpg', 1, 1586163321);
-- --------------------------------------------------------
--
-- Table structure for table `token`
--
CREATE TABLE `token` (
`id` int(11) NOT NULL,
`email` varchar(255) NOT NULL,
`token` varchar(255) NOT NULL,
`date_created` int(11) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
--
-- Indexes for dumped tables
--
--
-- Indexes for table `admin`
--
ALTER TABLE `admin`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `guru`
--
ALTER TABLE `guru`
ADD PRIMARY KEY (`nip`);
--
-- Indexes for table `kelas`
--
ALTER TABLE `kelas`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `materi`
--
ALTER TABLE `materi`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `siswa`
--
ALTER TABLE `siswa`
ADD PRIMARY KEY (`id`);
--
-- Indexes for table `token`
--
ALTER TABLE `token`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT for dumped tables
--
--
-- AUTO_INCREMENT for table `materi`
--
ALTER TABLE `materi`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=78;
--
-- AUTO_INCREMENT for table `siswa`
--
ALTER TABLE `siswa`
MODIFY `id` int(64) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=47;
--
-- AUTO_INCREMENT for table `token`
--
ALTER TABLE `token`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=41;
COMMIT;
/*!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 */;
|
{{ config(materialized='view') }}
select day,
COALESCE((payload#>>'{0,newCases}')::int,0) as cases
from {{ ref('covid_19_ingestion') }}
|
<filename>sqls/outer/update.sql<gh_stars>0
UPDATE test_table SET test = TRUE
|
<reponame>DavyVerbeke/madoc-platform
--subject-parent (down)
alter table tasks drop column subject_parent;
|
/*
* Copyright (c) Facebook, Inc. and its affiliates.
*
* This source code is licensed under the MIT license found in the
* LICENSE file in the root directory of this source tree.
*/
-- testing line numbers for simple statement boundaries, any statement will do
-- something with no "interior" works best.
create proc based_statements()
begin
declare x integer not null;
set x := 1;
set x := 2;
set x := 3;
@echo c, "/* hello "; -- no line info for these!
@echo c, "world \n"; -- no line info for these!
set x := 4;
set x := 5;
end;
-- testing simple if statements in various forms
create proc if_test()
begin
declare x integer not null;
if x = 1 then
set x := 10;
end if;
if x = 2 then
set x := 21;
else
set x := 22;
end if;
if x = 3 then
set x := 31;
else if x = 3 then
set x := 32;
else
set x := 32;
end if;
end;
-- testing if and case together with a coalesce thrown in
create proc case_if()
begin
if 1 then
call printf("one");
else
call printf("two");
end if;
declare x integer;
set x := coalesce( case
when 1
then 200
when 2
then 300
end,
3000);
end;
-- testing the in predicate by itself
create proc in_pred_lines(i integer not null, out b bool not null )
begin
set b := i in (
1,
3,
7);
end;
-- testing in predicate mixed with case
create proc in_pred_and_case(i integer not null, out b bool not null )
begin
set b := case when
i > 8
then
i in (
10,
12,
14)
else
i in (
1,
3,
7)
end;
end;
|
<reponame>Torii-HITSE-2014/Crawl-Robots<gh_stars>1-10
DROP DATABASE Pinboard;
CREATE DATABASE IF NOT EXISTS Pinboard;
USE Pinboard;
CREATE TABLE IF NOT EXISTS `NewsObject`(`ID` INT NOT NULL AUTO_INCREMENT,`Title` VARCHAR(255) NOT NULL,`Date` VARCHAR(20) NOT NULL,`Filepath` VARCHAR(255) NOT NULL,`Link` VARCHAR(255) NOT NULL,PRIMARY KEY (`ID`, `Link`)) DEFAULT CHARSET=utf8;
CREATE TABLE IF NOT EXISTS `Object_Tags`(`ID` INT NOT NULL AUTO_INCREMENT,`ID_News` INT NOT NULL,`Tag_Value` VARCHAR(10) NOT NULL,PRIMARY KEY (`ID`),FOREIGN KEY (`ID_News`) REFERENCES `NewsObject`(`ID`)) DEFAULT CHARSET=utf8;
CREATE TABLE IF NOT EXISTS `Subscriber`(`UUID` NVARCHAR(64) NOT NULL,`Tags` VARCHAR(255),PRIMARY KEY (`UUID`)) DEFAULT CHARSET=utf8;
|
<gh_stars>1-10
DROP TABLE IF EXISTS public.bet_wallet_market;
CREATE TABLE IF NOT EXISTS public.bet_wallet_market(
betId VARCHAR(255) NOT NULL,
walletId VARCHAR(255) NOT NULL,
marketId VARCHAR(255) NOT NULL,
stake BIGINT NOT NULL,
PRIMARY KEY (betId));
|
<filename>src/test/resources/sql/create/56c6bc73.sql
-- file:returning.sql ln:137 expect:true
CREATE TEMP TABLE joinme (f2j text, other int)
|
<filename>packages/intranet-core/import_sql/lexcelera/15-create-translator-phone.sql
---------------------------------------------------------------------------------
-- tblTranNotes - Notes for companies
---------------------------------------------------------------------------------
create or replace function inline_0 ()
returns integer as '
DECLARE
row RECORD;
v_company_id integer;
v_topic_id integer;
v_note_text text;
v_subject text;
v_person_id integer;
BEGIN
for row in
select *
from "tblTranNote" n,
"tblTranMaster" m
where
n."TranID" = m."TranID"
loop
select company_id into v_company_id
from im_companies where lxc_company_id = row."TranID";
select person_id into v_person_id
from persons where lxc_user_id = row."MatUserID";
IF v_person_id is NULL THEN v_person_id = 624; END IF;
v_note_text := coalesce(row."Note", ''Note ''||row."NoteID"::varchar);
select topic_id into v_topic_id
from im_forum_topics
where object_id = v_company_id
and message = v_note_text;
RAISE NOTICE ''Note: tid=%, cid=%, fn=%, ln=%, note=%'',
row."TranID", v_company_id, row."FirstNm", row."LastNm", v_note_text;
IF v_company_id is not null AND v_topic_id is NULL THEN
insert into im_forum_topics (
topic_id, object_id,
topic_type_id, topic_status_id,
posting_date,
owner_id,
scope,
subject,
message,
due_date
) values (
nextval(''im_forum_topics_seq''), v_company_id,
1108, 1200,
row."MatDte"::date,
v_person_id,
''group'',
substring(v_note_text for 60),
v_note_text,
row."FollowUpDte"
);
END IF;
end loop;
return 0;
END;' language 'plpgsql';
select inline_0 ();
drop function inline_0 ();
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.