When you "Edit notification texts" on the admin/settings/login_security screen, only certain field changes are actually affecting the output of the notifications when used. So this is not an issue of the admin screen form submitting properly (I think) because I can see the changes I've saved/made on the admin screen. The problem is the changes actually being output in the email notification.
My example is with the "Email to be sent to the administrator user (uid 1) for ongoing attack detections." I've changed the Email subject and Email body for this item. When I get the email notification it has the Subject changes, but not the Body changes. The body of the email is just the canned, default message. Not sure about the on-screen notifications as I didn't test any of those.
Also, placeholders seem to be wrapped in <em></em> tags by default, even if I don't write them in there.
P.S. Great module!
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | login_security-730288-13.patch | 23.75 KB | ilo |
| #8 | login_security-730288-8.patch | 21.23 KB | heltem |
| #1 | login_security-mail_body-730288.patch | 2.7 KB | heltem |
Comments
Comment #1
heltem commentedHere is a patch for mail body.
But I haven't found where does the
<em></em>placeholder wrapping come from, yet.Comment #2
deekayen commented#1 committed to DRUPAL-6--1 and HEAD
Comment #3
deekayen commentedWhen using % with t(), that adds em tags.
I didn't see any use of core's t() to cause em additions, unless somehow the declaration at define() is doing it.
Comment #4
heltem commentedI guess the guilty is login_security_t() function which call theme('placeholder', ....) which does the emphasis.
I suggest :
Comment #5
deekayen commentedHow about instead swapping the % out for @ in the relevant define()s up top?
Comment #6
heltem commentedProbably because, change only this won't change anything.
The emphasis does not come from the % but from the call to theme('placeholder', ...) that calls theme_placeholder()
But, maybe you can combine @ use with a t() call instead of calling theme('placeholder', ....)
Indeed, I see no reason to call theme() rather than t()...
Comment #7
deekayen commented@heltem: Care to propose a patch to wrap this up?
Comment #8
heltem commentedHere is a patch for 6.x-1.0.
Please review.
Comment #9
grub3 commentedI cannot even see admin/settings/login_security
using latest dev release.
Comment #10
deekayen commented@jmpoure: you mean it shows just a totally white screen, you get a 403 denied error, or the strings in the patch aren't displaying?
Comment #11
grub3 commentedSorry my late reply. I cannot see a link in the admin panel for admin/settings/login_security screen.
When I enter the URL manually http://www.mysite.org/admin/settings/login_security, nothing displays.
I am using Drupal latest version with PostgreSQL.
Comment #12
timwoodSorry, I haven't been able to review the latest patch. Has anyone else been able to do so? Will this patch make it into a full release soon?
Comment #13
ilo commentedI have updated the patch to remove a pair of coder issues. I haven't tested appart of the tests included in the module. Could anyone using smtp server (Heltem?) verify the email now does not contain the tags?
(I've verified that admin/settings/login_security is already there)..
Comment #14
deekayen commented#1722814: <em> tags are showing up in email subject line when using %site