Use registration field order when using a registration extension form - #26633
Conversation
|
Thanks for the pull request, @igobranco! I've created OSPR-5632 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
|
@igobranco Thank you for the contribution! When you have a chance, could you please send in a signed Contributor Agreement mentioned in the earlier comment? You only need to do this once and we can then review all your future code contributions. Thanks |
|
@igobranco We now have the same agreement available in Docusign here, so you don't need to print. Please sign when you have a chance. |
|
@igobranco Thank you for joining the Open edX community! We have added your user to our records and can now review your code going forward. |
|
jenkins run all |
|
@igobranco Could you please look into the failing tests? |
|
jenkins run all |
|
@wajeeha-khalid Could you please provide early feedback once you have a chance? |
|
@waheedahmed ^^ review required |
|
@natabene and @waheedahmed thank you with your information. So I'm going to try to fix the tests and update this pull request. |
|
jenkins run all |
1 similar comment
|
jenkins run all |
|
📣 💥 Heads-up: You must either rebase onto master or merge master into your branch to avoid breaking the build. We recently removed diff-quality and introduced lint-amnesty. This means that the automated quality check that has run on your branch doesn't work the same way it will on master. If you have introduced any quality failures, they might pass on the PR but then break the build on master. This branch has been detected to not have commit 2e33565 as an ancestor. Here's how to see for yourself: If you have any questions, please reach out to the Architecture team (either #edx-shared-architecture on Open edX Slack or #architecture on edX internal). |
|
Hi @natabene finally the jenkins didn't end with my errors or other errors ! I've been fetching from upstream a couple of time because the last builds stopped with completed strange errors. Can you help so anyone from edX could validate the changes ? |
|
@waheedahmed Could you validate please? |
|
@natabene sure, taking a look. |
waheedahmed
left a comment
There was a problem hiding this comment.
@natabene I have verified and tested these changes locally and looks good to me.
|
@igobranco Thank you for making these changes! Please squash your commits and make sure your branch is rebased with the latest master. |
|
Hey @igobranco, are you still interested in this change? If not, I'd be happy to continue squashing and rebasing as we need this change too. cc: @waheedahmed |
|
@natabene Are we good to move forward and merge this PR or any further step is required here? |
53e8301 to
baf0207
Compare
|
@waheedahmed If the author @igobranco is ready, no problem from my side. |
|
Your PR has finished running tests. There were no failures. |
|
@waheedahmed I've updated the PR: rebased and squashed the commits. cc @gabor-boros |
|
Thank you @natabene and @igobranco! Merging it now. Thanks again, everyone! |
|
@igobranco 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
|
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production. |
|
EdX Release Notice: This PR has been deployed to the production environment. |
|
@gabor-boros could you port this changes to lilac.master? as part of BB-4877 |
…n form (openedx#26633) (cherry-picked from commit 6f0255b)
…to registration form (#441) * feat: add `optional-exposed` extra field type to registration form This defines optional extra fields that are not hidden under the toggle on the registration page. (cherry picked from commit 230795f) Signed-off-by: Gabor Boros <gabor.brs@gmail.com> * Fix use a registration field order when using a registration extension form (openedx#26633) (cherry-picked from commit 6f0255b) Co-authored-by: Ivo Branco <igobranco@gmail.com>
Description
On registration screen, make it possible to change the
REGISTRATION_FIELD_ORDERwhen using a customREGISTRATION_EXTENSION_FORM.If you are managing an open edx installation probably you need to ask more information about your users on the registration form. For that you use a registration extension form. But when you configure that extension form you no longer can change the ordering of presentation of each field on the registration form. This pull request tries to fix that specific thing.
This change has impact for Developers and Operators that manage a custom open edx installation.
Example, with this configuration, we can
Required fields:


Optional fields: