Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
There are various issues where people have reported issues with private message when they simply haven't enabled the sub-module.
It seems like if realname is enabled, privatemsg_realname should also be enabled without any intervention.
Comment | File | Size | Author |
---|---|---|---|
#1 | 2077223-privatemsg-realname-enabled-1.patch | 1.13 KB | japerry |
Comments
Comment #1
japerryHere is an initial patch. It checks upon enabling of modules if realname is enabled, and enables the associated privatemsg_realname module.
Also has an update hook to enable if it hasn't been enabled already yet.
Comment #2
japerryComment #3
ptmkenny CreditAttribution: ptmkenny commentedIs there any precedent for this? I don't know of any other Drupal modules that automatically enable themselves when another module is enabled (except dependencies).
If there are lots of issues being reported where this is a problem, please link to a few of them.
Modules are permitted to force their dependencies to be enabled, but if it is not a dependency, I do not think we should be automatically performing site administrator tasks (it is conceivable that someone wants to use Privatemsg and Real Name without combining the two.)
Comment #4
ptmkenny CreditAttribution: ptmkenny commentedComment #5
felipeolcav CreditAttribution: felipeolcav commented@ptmkenny
The issue is reported and discussed here: https://drupal.org/node/2070719
It looks like when realname is enabled, it's necessary to enable pvtmessage realname integration or it's impossible to send pvtmsg.
Comment #6
ptmkenny CreditAttribution: ptmkenny commented@felipeolcav
Is that true for all configurations of Privatemsg, or just the one used on Drupal Commons?
Comment #7
ptmkenny CreditAttribution: ptmkenny commentedMarked #2087137: "You must include one valid recipient" as a duplicate
Comment #8
ivnish CreditAttribution: ivnish commented