Closed (won't fix)
Project:
Advanced User
Version:
master
Component:
Feature
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
12 Feb 2007 at 14:58 UTC
Updated:
21 Aug 2018 at 03:30 UTC
Jump to comment: Most recent
Comments
Comment #1
mcurry commentedThank you for the suggestion. There are numerous other modules for newsletter creation and management.
This request is beyond the scope of the advanced user module at this time, or for the foreseeable future.
Comment #2
Anonymous (not verified) commentedAnd the _you_ in ``won't fix'' is ok but I've added this as a ``feature request'' to at least be discussed as meritable. Why do you not see this as a likely feature that enhances this module? Yes there are other modules for subscription and newsletter creation. Why can't the email sent from this package become a node? If I supply the patch would the patch be reviewed as a possibility or would you find the idea objectionable to the point that such a patch would be rejected as well?
Comment #3
mcurry commentedDiscussions of new features are fine, but someone has to decide what belongs in this module and what doesn't - at present, that's me.
In my judgment, this feature request (making emailed messages sent from this module into a node) doesn't belong in this module regardless of the complexity of the implementation. This module has limited scope: advanced user management features. I may even drop the mass emailing feature if making that work well and efficiently is too much work, and the feature is available in other modules.
Setting this to 'wontfix' is my way of saying that I am not inclined to implement such a feature, and, if a patch is submitted, I am not inclined to commit the patch.
Comment #4
Anonymous (not verified) commentedThat would be a shame. This is the only module that does a mass mail of all users and that functionality is why I'm interested in this module.
Comment #5
mcurry commentedI thought there were other modules that did this. In any case, I agree, this is a useful feature, but only if it works well. I've seen this module cause major problems when trying to mass-email large #'s of users; so I hardly ever use that feature. I guess it all depends on what you think is most important. Personally, I find the email notification of new and updated user registration the most useful feature.
Bottom line, if a feature doesn't work well and reliably, and can't be made to do so in a reasonable period of time, I'd rather cut it than have long-standing bugs sitting in the issue queue.
I see that you've switched over to the mass email issue thread and left comments there, so we'll end this thread in this issue.
Regardless of whether the mass email feature works well, I still don't see how creating a node from the email messages sent to users by this module fits as a module feature - I don't see how it fits this module's scope. Why would anyone want this module to create a node from a mass emailing? What problem does it solve related to advance user management?
Comment #6
Anonymous (not verified) commentedI understand. The request doesn't fit the intended use of the module. I'll look at the code and perhaps make a different request with a patch.