Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The pm_disable table has been removed, but is still referenced in privatemsg_user_cancel(), causing errors when cancelling user accounts. Patch attached.
Comment | File | Size | Author |
---|---|---|---|
privatemsg_delete_pm_disable.patch | 402 bytes | mikeryan | |
Comments
Comment #1
BerdirComment #2
BerdirStrange, why didn't my tests catch this...
Commited.
Comment #4
computerology CreditAttribution: computerology commentedThis 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
Comment #5
BerdirNo, it has not. That table exists there, this is not supposed to be removed.
Comment #6
computerology CreditAttribution: computerology commentedThen 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.
Comment #7
ptmkenny CreditAttribution: ptmkenny commentedIf you are still having issues, please provide specific steps to reproduce the error, preferably from a clean install of Drupal 7.
Comment #8
ptmkenny CreditAttribution: ptmkenny commentedSince there has been no activity for a month, I'm closing. Feel free to re-open if you have the same issue and can provide a detailed bug report.