Article 9
Replying to andrea_r: +1, yes please. As an extra, anyway you could make the same in the DISallowed email field? So super admins can block all *.info or *.ru domains from signing up (for example)....
View ArticleArticle 8
Replying to nacin: Cool. (Not a problem, also. I killed the attachment.) Patch looks great, at a glance. All I see are coding standards improvements to be addressed. Marking for 3.2-early. As this is...
View Articlecc changed
ccandrea_r added +1, yes please. As an extra, anyway you could make the same in the DISallowed email field? So super admins can block all *.info or *.ru domains from signing up (for example).
View Articlekeywords changed
keywords3.2-early added Cool. (Not a problem, also. I killed the attachment.) Patch looks great, at a glance. All I see are coding standards improvements to be addressed. Marking for 3.2-early. foreach...
View ArticleArticle 4
Done, sorry about that. I can't see a way to remove the old .txt file (not that familiar with trac).
View ArticleArticle 2
Replying to djcp: I suppose you could do something stupid like enter "*.com" and allow anyone with a .com address to register in your multisite install, but c'mon. You can't fix stupid. :-) I like...
View Articlekeywords changed
keywordshas-patch added; needs-patch removed So if a limited domain begins with "*.", we nick off those characters and check it against the right side of the user's email domain. If a limited domain...
View Articlemilestone changed; keywords set
keywordsneeds-patch added milestone changed from Awaiting Review to Future Release Seems sensible. A patch would be great.
View Article
