kirrg001 c99557d9a3 🐛 Fixed disqus comment id when exporting/importing 1.x content ... no issue - while i was testing random failures, i discovered an edge case for disqus - you start a new 1.0 blog, you add disqus, the unique identifer is the post id (object id) - now you export your content and import it on a new instance - the importer detects that the amp field is null and imports the old object id as comment id - but the post model is not prepared for this case - see next commit for tests **NOTE**: The comment id had two different data types (Number or String). Disqus expects a string. So this should not change any behaviour, now that the comment_id is always a string.		2017-09-12 16:29:59 +01:00
..
base	🐛 fix transfer ownership (#8784)	2017-07-31 13:37:37 +04:00
plugins	🐛 Added 409 UpdateCollisionError for the editor (#8899)	2017-08-15 12:06:40 +02:00
accesstoken.js
app-field.js
app-setting.js
app.js
client-trusted-domain.js
client.js	🎨 😎 config env usages (#7929)	2017-02-03 18:25:39 +00:00
index.js
invite.js
permission.js
post.js	🐛 Fixed disqus comment id when exporting/importing 1.x content	2017-09-12 16:29:59 +01:00
refreshtoken.js
role.js
settings.js	🎨 do not run model listeners on import (#8720)	2017-07-21 09:58:58 +01:00
subscriber.js	✨ replace auto increment id's by object id (#7495)	2016-11-17 09:09:11 +00:00
tag.js
user.js	Add ghost-backup client to trigger export (#8911)	2017-08-22 11:15:40 +01:00