Steps to replicate the issue (include links if applicable):
- Delete a newsletter
- Try to recreate another newsletter with the same name
- (after that fails) Try to move an already existing newsletter to that name
What happens?:
The creation fails with "A newsletter with the name "H" already exists. Please try again with another name."
The move spews a warning and appears to succeed but leaves the newsletter database in an inconsistent state
What should have happened instead?:
Both creation attempts succeeded
Other information (browser name/version, screenshots, etc.):
This is due to the nl_name key being unique, which doesn't quite match the conceptual model