Katharina Irrgang 5ff7574324 🐛 user was not imported, but the importer tries to correct the reference (#8722) ... no issue - this is usually an edge case, but i investigated because i thought that the importer is broken - the importer logic is build like this: - it creates a transaction - this transactions runs through: - beforeImport - doImport - afterImport - afterImport corrects user references and if a user could not be imported, we have to protect that NOTE: we could create two transactions to be more correct, but building this had no priority because of edge cases only having two transactions would solve: you first add the data (error or success), then you correct the data - usually a user can be always imported (!), but there are a few edge cases (e.g. multiple roles attached)		2017-07-21 09:59:18 +01:00
..
client@fa921f8367	Updated Ghost-Admin to 1.0.0-rc.1	2017-07-11 16:41:08 +02:00
server	🐛 user was not imported, but the importer tries to correct the reference (#8722)	2017-07-21 09:59:18 +01:00
test	🐛 be able to serve locked users (#8711)	2017-07-20 12:45:13 +01:00
index.js