mirror of
https://github.com/TryGhost/Ghost.git
synced 2024-12-21 01:41:46 +03:00
3817f583fa
closes https://github.com/TryGhost/Team/issues/2275 When deleting a member, after confirming deletion another "unsaved changes" modal popped up. From that point, if you clicked to stay you remained on the member screen with stale data (the member was still deleted) resulting in further errors when any attempt to make changes was made. - prevented the unsaved changes check running for a deleted member because it would always return `true` in that case - ensured the data setup for the unsaved changes check still occurs when a member is accessed directly via the URL - previously it was skipped because the data setup only occurred inside `fetchMemberTask` but that isn't called when the route already loaded the model via it's `model()` hook |
||
---|---|---|
.. | ||
bulk-add-label.hbs | ||
bulk-add-label.js | ||
bulk-delete.hbs | ||
bulk-delete.js | ||
bulk-remove-label.hbs | ||
bulk-remove-label.js | ||
bulk-unsubscribe.hbs | ||
bulk-unsubscribe.js | ||
delete-member.hbs | ||
delete-member.js |