Closed (works as designed)
Project:
Privatemsg
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Aug 2013 at 18:17 UTC
Updated:
27 Jul 2022 at 07:02 UTC
Jump to comment: Most recent, Most recent file
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 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 commentedComment #5
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 commented@felipeolcav
Is that true for all configurations of Privatemsg, or just the one used on Drupal Commons?
Comment #7
ptmkenny commentedMarked #2087137: "You must include one valid recipient" as a duplicate
Comment #8
ivnish