Skip to content
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

Closed
wants to merge 81 commits into from
Closed

Feanil/reset all passwords #3312

wants to merge 81 commits into from

Conversation

feanil
Copy link
Contributor

@feanil feanil commented Apr 10, 2014

No description provided.

FiloSottile and others added 30 commits April 5, 2014 18:13
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
Experiment with cell widths to see if images will appear
additional small typos and fixes
Merging release back to master
add acceptance tests for user profile pagination.
singingwolfboy and others added 19 commits April 25, 2014 16:03
Add test in import code to make sure two overlapping courses aren't imported
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.
Document our development/review process
Don't scrape unnecessary strings for i18n
@feanil
Copy link
Contributor Author

feanil commented Apr 28, 2014

@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.

@singingwolfboy
Copy link
Contributor

@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?

@feanil
Copy link
Contributor Author

feanil commented Apr 28, 2014

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.

@singingwolfboy
Copy link
Contributor

@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.
@feanil
Copy link
Contributor Author

feanil commented Apr 28, 2014

Closing this, will re-open against master when I have some time to work on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting on author PR author needs to resolve review requests, answer questions, fix tests, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.