Closed (won't fix)
Project:
User verification
Version:
7.x-2.0-alpha1
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
10 Oct 2013 at 16:15 UTC
Updated:
30 Sep 2014 at 02:50 UTC
Jump to comment: Most recent
Comments
Comment #1
doitDave commentedHi,
before digging into it, please split up your request into one task per issue. Also it would be nice if you could be a bit more specific esp. regarding part 2.
thx
Comment #2
doitDave commentedOK, as you have noticed, I appreciate your token-related suggestions.
For this one here, I still do not get exactly what you want to do. The module uses Drupal's API functions for mailout. I cannot see any advantage for you, even if I'd make that optional, because appr. 98% of your site's mails would still not reach your mail system.
Wouldn't it make *much* more sense if you hooked directly into Drupal's mail API? There are several hooks where you can do so and you can even change the site-wide mailer - of course.
So, honestly, I am not getting the point here. Maybe you can add some enlightenment. Thx!
Comment #3
peter.bozovic commentedWell, this is related to the "[user-verification:...] tokens" feature request
As I mentioned, I'm using "Entity Email" module that allows me two things:
- Send e-mails in html format (in combination with some other modules)
- I can let my content managers edit those e-mails without allowing them to change other site system configurations
So, my welcome e-mails are triggered with Rules on new user creations, and I'm using Entity Emails to send those e-mails
With the help of the other feature request, I'll be able to put user validation url within the contents of those welcome e-mails
And in that case, I don't want the "User verification" module to send his own verification mail since that will be already done trough the Rules/Entity Emails modules
I hope this is more clear now :)
Thanks again for your consideration
Peter
Comment #4
doitDave commentedYes, now it has become a lot clearer. I understand your planned workflow and it makes sense. I'll see what can be done!
Comment #5
doitDave commentedComment #6
doitDave commentedThis feature is now also available in 7.x-2.x-dev and 7.x-2.0-alpha1.
Comment #7
peter.bozovic commentedWhen this feature is enabled, the url token is not displaying the code part anymore
More details on the other thread: https://drupal.org/node/2109659#comment-8007727
Thanks
Comment #7.0
peter.bozovic commentedSplitting the request as two issues
Comment #8
doitDave commentedHey, thanks for your report. If you are already using u_v, you might have noticed the increasing spam reg level in the last months. This means obviously that the current implementation has been worked around by the other side - which was to be expected and then, not too difficult.
So far for the bad news. The good news is, I am working on an all new, really more powerful solution at the moment with a totally different and, by the way, far more hard-to-beat approach.
As we will not deal with registration anymore by then, I will close this issue as won't fix. Hope you understand.
Comment #9
doitDave commented