Closed (fixed)
Project:
Privatemsg
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
27 Jan 2006 at 02:32 UTC
Updated:
23 Jun 2006 at 15:45 UTC
Jump to comment: Most recent file
hook_user changed in HEAD. Keeping up with the new array structure.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | 46623-privatemsg-user-profile-shows-p.patch | 2.29 KB | webchick |
| #6 | privatemsg_2.module | 25.68 KB | brashquido |
| privatemsg.module_0.diff | 2.11 KB | drumm |
Comments
Comment #1
Shiva Thomas commentedWorks for me. :-)
Comment #2
polSubscribe msg ;)
I'll try at home !
Comment #3
kus commentedworks perfect.
Comment #4
ajwwong commentedDitto. Patch works perfect for me too. Thx.
Comment #5
ultraBoy commentedanybody commit it please
Comment #6
brashquido commentedPatched module file for those not familiar with patching files, or no access to a *nix OS or Cygwin install for Windows.
Comment #7
hectorplus commentedThis is the error i get when sending the message when there is no userName entered.
Fatal error: Call to undefined function: array2object() in /............/.../modules/privatemsg/privatemsg.module on line 475
Comment #8
fool2 commentedThat is part of another error in the code. I really wish someone would commit to CVS so we had a new version to work with.
Also, maybe it's adviseable to use the ajax autocomplete that comes with the forms API now instead of the dropdown select.
Comment #9
MrEricSir commentedThis patch exposes another bug.
If you follow a link to message someone (i.e. privatemsg/msgto/1) the "To" field is never filled in.
This seems to occur in privatemsg_page(). Comment out the following lines and you're good to go:
Comment #10
Carlos Miranda Levy commentedIs the patch or the patched module listed here v4.7, cvs or 4.6?
Comment #11
MrEricSir commentedIt's for the CVS version of the module.
Comment #12
webchickHere's a patch for 4.7 (should also apply to CVS) with both drumm and MrEricSir's fixes.
Comment #13
mindless commentedI think the original patch attached here is correct, but the 2nd issue mentioned I think should be resolved by this patch rather than comment #9/12 here.
Comment #14
mindless commentedComment #15
mindless commentedI have included the original patch in 67612.
Comment #16
mindless commentedComment #17
(not verified) commented