Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi, the problem I'm facing is really annoying, because suddenly when doing changes in the settings page of the Relationships module, now it asks me for a required Sender of the private messages. Unfortunately looks like the default doesn't work, and nowhere is specified the variable to use. So now all the messages sent are anonymous, no matter who is the sender, they're always shown as anonymous.
I've tried everything, and the default variable of the code looks like useless.
Any help please?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 446874.patch | 1.56 KB | alex.k |
Comments
Comment #1
alex.k commentedWhen you say 'suddenly', did it not ask you before? I just never used Privatemsg integration for UR 5.x. Also, by 'sender', do you mean the email From: header, or something else. Thanks.
Comment #2
GuybrushSThreepwood commentedNo, just from the last change I did, it vanished, and now Idk what to add in that field; nothing of what I fill it with doesn't work. When I'm talking about the sender field (actually that's its name) I mean the privatemsg system email 'From'.
Thanks.
Comment #3
GuybrushSThreepwood commentedNo matter what I do, each time I update my settings page now it doesn't allow me doing so, indicating that the Sender field is Required; but despite I tried with with everything, even adding the admin user name, nothing works; I mean, eaach time I do a little change, no matter what I do, I have to fill the sender field; then each time I return the sender field is empty.
I've tried everything but nothing works out; I even restored old backups but still it doesn't work. Unfortunately the only solution I see is just to quit using the user relationships privmsg plugin. (As always with Drupal no one can help me) Unfortunately I've been working on this project for a long time now and I'm stuck, but I can tell you Drupal doesn't help at all; on the other hand it complicates things. Next time I'll build my whole site with PHP and MySQL from scratch (the good old school), no more Drupal; it's just a tool to make things more difficult.
Finally the community never helped me on anything, ANYTHING. I've posted about ten issues, and never got an answer; I've solved them all by my self without any help. So what's the point of Drupal.....nothing just to make things more difficult. Drupal is like wishing to travel from NY to NJ but going eastwards 20k miles around the world.
Comment #4
GuybrushSThreepwood commentedLooks like again I won't get any help...except for someone who was kind, and democratic, enough to clear my issue. That's the only solution they gave me, I said something "not suitable" for Drupal and they come and clear your posts.
Ok, I'll never come back to the Drupal forum and as soon as I get rid of this work I'll try to avoid by all means this Drupal thing.
Thank you this community is really great.
Comment #5
AppleBag commentedI'm having a problem with this on the latest 5.x version as well.
I've typed in a "Sender" (autocomplete actually did for me), saved the settings. And now anytime a private message is sent from the module, it's sent as an anonymous user, rather than the user that I entered in the "Sender" field.
Then, any time you load the same settings page, the "Sender" field is blank again, whereas it should be showing the name of the sender that was saved there previously. It is marked as a required field, so each time you want to save settings, you have to re-enter the sender name you want in order to save (which of course starts the process all over again)
It almost seems to me that the Sender isn't getting stored to the database, although the email fields for customizing the email messages does. However, I can't seem to find in the code any reference to storing/reading these from the DB.
Anyone have any ideas?
Comment #6
alex.k commentedThe problem is, you are probably trying to use Privatemsg 5.x-3.x. UR integration for Privatemsg was written in early 2008 if not earlier, at that point only 5.x-1.8 existed. 3.x stores sender usernames, whereas 1.8 stores user IDs.
Options are:
* You could use Privatemsg 5.x-1.8
* Apply attached patch to UR-Privatemsg which makes it compatible with 3.x. I can't commit this patch as is because it will break existing installs which probably still use 1.8.
* Find a way to check in UR-Privatemsg which version of Privatemsg we're dealing with, and use appropriate code - this would be preferrable.
Comment #7
AppleBag commentedThanks a million alex, the patch worked perfect :D
Comment #8
alex.k commentedWatch out if you ever update to another release (2.9 is highly recommended), as it will wipe out the patch. If you could do a little research and find a code snippet that determines a given module's version, then I can make this a permanent feature.