New Option to Allow Override "Anyone Can Register" Wordpress Setting #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds an option to override the "Anyone Can Register" option in Wordpress, allowing the site to be closed to new normal accounts yet open to new accounts with WP-OAuth
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new option that let's a user override the Wordpress option "users_can_register" to let WP-OAuth register new users while having the site closed to new Wordpress accounts.
The use case for this is wanting to have some users (admins) log in with Wordpress accounts, thus keeping the wordpress login form visible, while user accounts require OAuth logins. Enabling "Anyone Can Register" leaves the site owner open to spam registrations. I know, I had this problem which is why I made this pull request =)
Please note, the file register.php had multiple line ending types detected in the same file and even my beloved vim could not cope. The only change is line 12, the rest are just fixing the line endings.
Also, there is a small change on the style sheet to fix the options page. On my firefox the "toggle" options were pushing down col 2 and causing col 1 to stack beneath it.