Oz ,'Bring On The Night'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Unfortunately I don't have the brain cells to easily debug the regular expression in the check -- I think that it may have been a particular character legal in the username that was throwing it off.
Because it doesn't always fail, does it? Have we had that big a bug this whole time?
Have we had that big a bug this whole time?
I think so, yes. At least, I couldn't get it to work.
The problem looks like when the form loads, the replyto field on the form has a vaule of the user name and the user email address, when it only needs to have the email address. When the user submist the form, both the user name and the user email gets posted to the server, causing the email validity testing function to return false.
I think. I don't have the whole code in front of me, as I'm watching X-men United.
edit: I don't understand how the code for buffistas.org does works... unless that code is different.
I went and tested and it works just fine for me -- it may very well be punctuation in the username that sets it off.
We'll need to put that on the list, and hope someone with regex knowhow steps up for it.
tommy -- you have precisely the code that's running here.
I do regex.
The problem's not with regex. The function with the regex test was getting passed the user name, not the user email.
I'll have more details after X-Men is over.
The function with the regex test was getting passed the user name, not the user email.
I'll go dig into the code, but since it seems to think "ita" is a valid e-mail address, then we do have a problem with the regex anyway.
So thanks, Gus.
Cool. Point me at it, via the profile addy...
But I can use the form on buffistas.org, but not sql.buffistas.net. Maybe the function is getting passed the email address on buffistas.org.
What gets passed to the validation is "$_user->name <$_user->email>"
The regex is supposed to be able to accept "Jon. B <jonb@whatever.com>" as a valid e-mail address. It is not. However, it likes "ita <ita@wherever.com>" just fine. Which is why the problem is not in what's passed, but in how it's parsed.