[4.0] Fix custom fields in com_users #31366
Merged
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
|
I have tested this item ✅ successfully on 529e882 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/31366. |
1 similar comment
|
I have tested this item ✅ successfully on 529e882 This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/31366. |
|
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/31366. |
|
Tks. |
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.
Fixes #31334.
Summary of Changes
Fixes custom fields functionality in com_users.
Testing Instructions
Enable user registration.
Go to Users -> Fields. Notice that context select box is missing.
Create a field. Configure permissions or enable
Display When Read-Onlysetting.Go to register in frontend.
Actual result BEFORE applying this Pull Request
Custom fields not shown in registration form.
Expected result AFTER applying this Pull Request
Custom fields shown in registration form.
Documentation Changes Required
No.