I ran into an unfortunate bug with the Comment module. Steps to reproduce:
- Create an article as the admin user.
- Log in as a regular user and leave a comment on the article.
- Log back in as the admin, disable the Comment module, delete the regular user, and then turn the Comment module back on again.
- Visit the node, and you get a nice fatal EntityMalformedException error.
The issue is that while the Comment module is disabled, its hooks (for user deletion) cannot run, so it can't delete the comment, and an orphaned comment is left over. (Similar orphaned comments occur if you delete a node while the Comment module is disabled, but in that case I'm not currently aware of any visible side effects; maybe you can get some with Views though.)
I debated between "normal" and "major" for this issue. It takes an odd set of steps to reproduce, but if you do find yourself in this situation you have broken nodes on your site and no way to repair them. I went with "major" for now.
Patches will follow in a second.
|PASSED: [[SimpleTest]]: [MySQL] 40,975 pass(es).|
|FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 72,509 pass(es), 30 fail(s), and 18 exception(s).|
|FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch comment-author-deleted-1451072-9.patch. Unable to apply patch. See the log in the details link for more information.|
|FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch comment-author-deleted-1451072-1_0.patch. Unable to apply patch. See the log in the details link for more information.|