keywords changed
keywordsneeds-refresh added; has-patch removed Patch will need refreshing, because sanitization changes introduced in r21993 (#21552) mean that items containing asterisks are now stripped when the...
View ArticleArticle 22
Since "Banned Email Domains" field already supports regexps, wouldn't it make sense to do the same in "Limited Email Registrations" for consistency? Done in 15706.2.patch.
View Articlestatus, milestone changed; owner set
owner set to westistatus changed from new to reviewingmilestone changed from 3.3 to Future Release Tend to agree that a filter would be better. A filter on the response, that passes in the emaildomain....
View ArticleArticle 18
I still think a better solution here is a filter which allows for a plugin to implement this or any other rule for allowed domains rather than complicating the core code in this case. We should just...
View Articlekeywords changed
keywordsdev-feedback added We're at freeze for 3.3. Leads/committers, please weigh in on commit vs punt. As always an incremental improvement over the course of several releases is better than not...
View ArticleArticle 16
Replying to andrea_r: 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...
View Articlekeywords, milestone changed
keywords3.2-early removedmilestone changed from Future Release to 3.3 Refreshed for 3.3, adjusted as per nacin's comments.
View ArticleArticle 13
I am a sad panda. This didn't make it into 3.2 beta 1, and I think this has real utility for academia and any large institution that wants to create easy to manage multisite installs. Any chance this...
View Articlecc changed
ccwesti added I wonder how many people use the limited email domains feature - didn't even realise it existed. I also wonder if this would not be better served by better hooks and a plugin?
View ArticleArticle 11
Replying to djcp: 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...
View ArticleArticle 10
Replying to djcp: Replying to nacin: As this is my first contribution to the wordpress core, I'm a little unsure of standards. Sorry! Should I make those change and re-upload? Not a problem. Congrats...
View ArticleArticle 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 Article