Closed (fixed)
Project:
Privatemsg
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Jun 2010 at 05:53 UTC
Updated:
6 Jul 2010 at 08:40 UTC
Jump to comment: Most recent file
Hey Berdir and all,
I've been the testing process on the latest 7.x-dev snapshot. I noticed that when a user who has a new private message logs in there is a White Screen of Death. Checking the Apache error logs, here is the message I'm getting:
PHP Fatal error: Cannot use string offset as an array in /home/sandboxes/sandbox10/public_html/sites/all/modules/contrib/privatemsg/privatemsg.module on line 1956
I tried unchecking "Inform the user about new messages on login," but that didn't fix the error.
Navigating to the home page or a node page causes the error (even after initial login). But navigating to /user or an admin page still works fine.
Thoughts?
--Ben
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | author_links_with_tests7.patch | 5.86 KB | berdir |
| #8 | author_links_with_tests6.patch | 5.83 KB | berdir |
| #7 | author_links_with_tests-D6.patch | 5.83 KB | berdir |
| #4 | author_links_with_tests.patch | 7.73 KB | berdir |
Comments
Comment #1
BenK commentedComment #2
BenK commentedNote that the user can navigate to /messages even though he can't visit the homepage or a node page.
I also tried deleting the message thread altogether, but that didn't fix the White Screen of Death.
--Ben
Comment #3
BenK commentedComment #4
berdirSee title, this happens when you have the setting to display privatemsg links enabled because Privatemsg still assumes that node titles are fields.
The patch fixes that and also two separate bugs for blocks and comes with tests (Took them together so that I can write a single test class for both).
Comment #5
berdirComment #6
berdirSame here, commited and backport to 6.x-2.x-dev is planned.
Comment #7
berdirComment #8
berdirfiles with D6 are still ignored... :)
Comment #9
berdirWith ending newline
Comment #10
BenK commentedJust wanted to let you know that Patch #4 solved this problem for me in D7... thanks!
--Ben
Comment #11
berdirCommited the tests to 6.x-2.x-dev and (a adapted version without node link tests) to 6.x-1.x-dev. Yay for more tests!