-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feanil/reset all passwords #3312
Conversation
Show a button at the top of lms/templates/courseware/progress.html if the lowest nonzero grade cutoff has been reached. Introduce two settings: PROGRESS_SUCCESS_BUTTON_URL is the href of that button (the course id is appended); PROGRESS_SUCCESS_BUTTON_TEXT is the text, defaults to "Download your certificate"
The button text default is now in the template and i18n-able, a PROGRESS_SUCCESS_BUTTON_TEXT_OVERRIDE option is offered in settings. The button url now uses string formatting.
install and set up paver before using it
install and set up paver before using it
JIRA: FOR-492
Experiment with cell widths to see if images will appear
additional small typos and fixes
DOC-275, location & Language columns
Merging release back to master
…ializing the xblock
add acceptance tests for user profile pagination.
Ahodges/documentation/lms2476
Removed evil HEAD line
stud-1566
HTML Editor Changes - Raw Editor
Add test in import code to make sure two overlapping courses aren't imported
Forums visual styling adjustments
Correct copy/paste error in Adaptive Hint section
Show a success button at the top of the Progress page
Change signin control from text list to buttons.
Sarina/042914 language update
Release for Apr 27, 2014
Configure youtube stub for bok-choy
Document our development/review process
Add info about removing prompt
Don't scrape unnecessary strings for i18n
@singingwolfboy It was originally added to be able to reset password after heartbleed if we decided to do that. I'm going to re-base this off of master in case we need this logic in the future. |
@feanil so there's no intent to actually get this merged into master right now, is that correct? If that's the case, can this pull request be closed? |
no sorry I was not clear, I'm going to re-base this work from master and get it reviewed so it can be merged into master. We may need this feature in the future so I want it in place if we do. |
@feanil Gotcha. Who needs to review this pull request? (You can just apply the relevant labels onto the pull request -- this is a new organizational scheme I'm starting to implement.) |
If an 'OLDEST_VALID_PASSWORD_TIME' is defined, any passwords that are older will need to be reset.
Closing this, will re-open against master when I have some time to work on this. |
No description provided.