Only show user creation fields as restricted if they are actually needed. #3326
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.
All Submissions:
Changes proposed in this Pull Request:
Resolves #3165
Alternative to #3320
The
pmpro_get_field_class()
function has logic to show billing and user creation fields as required if they are set to be required during checkout. However, the checkout page template hardcoded the user creation fields to always show as required.This PR removes the hardcoded logic in the checkout template to allow
pmpro_get_field_class()
to correctly control therequired
asterisk.How to test the changes in this Pull Request:
Add this snippet and check whether the username and password fields are marked as required.
add_filter('pmpro_required_user_fields', 'custom_remove_required_user_fields', 10, 1); function custom_remove_required_user_fields($pmpro_required_user_fields) { unset($pmpro_required_user_fields['username']); unset($pmpro_required_user_fields['password']); unset($pmpro_required_user_fields['password2']); return $pmpro_required_user_fields; }
Other information:
Changelog entry