Posted by mikeryan on June 16, 2011 at 4:53pm
4 followers
Jump to:
| Project: | Privatemsg |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
The pm_disable table has been removed, but is still referenced in privatemsg_user_cancel(), causing errors when cancelling user accounts. Patch attached.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| privatemsg_delete_pm_disable.patch | 402 bytes | Idle | PASSED: [[SimpleTest]]: [MySQL] 37,038 pass(es). | View details | Re-test |
Comments
#1
#2
Strange, why didn't my tests catch this...
Commited.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.
#4
This bug has now migrated to the production release of 1.3.
I fixed it by wiping out the whole section of code referring to pm_disabled but if someone could commit a better fix that would be great
#5
No, it has not. That table exists there, this is not supposed to be removed.
#6
Then what is required to eliminate the error showing that the table pm_disable does not exist. I started on D7.0 and have upgraded periodically up to the current release 7.19. Been using privatemsg.module ever since, the update.php script has never attempted throughout anything to create or handle such a table, even when I installed a fresh copy of privatemsg 7.x - 1.3. I skimmed the MySQL db and the table did not exist, went looking for answers and found this bugfix, and stripping that chunk of code seemed to fix the problem.