Rishabh Garg 169daead1f Fixed post meta migration for 3.x (#11438) ... no issue Since we added `email_subject` to `posts_meta` table in `3.1`, the migration tries to add `email_subject` column from post table, which does not exist and thus tries adding `undefined` value for column. Since sqlite expects default values while inserting new columns, this breaks any migration directly from `1.x`/`2.x` to 3.x. The fix adds a default `null` value for any post_schema entry which doesn't has a value.		2019-12-17 17:14:53 +05:30
..
db	Updated links to docs (#10941)	2019-07-22 18:17:50 +08:00
exporter	Removed all accesstokens and refreshtokens related code	2019-09-12 15:45:27 +01:00
importer	Removed subscribers from the codebase (#11153)	2019-10-09 11:47:04 +02:00
migrations	Fixed post meta migration for 3.x (#11438)	2019-12-17 17:14:53 +05:30
schema	✨ Added new brand blog setting (#11408)	2019-12-17 16:15:31 +05:30
validation	🏗 Migrated posts.page column to posts.type (#11111)	2019-09-16 11:51:54 +01:00
timezones.json	Adds UTC as select option to timezones select list	2016-06-10 15:19:16 +02:00