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
FDSC 1.4.1 Bug: "False Positive" attempts without API key open MetaSmoke site for getting the key, but not the "Enter Code" window. #10
Comments
I think the code which closes the flag dialog after the false positive button is pressed is accidentally closing the input dialog too. Hopefully that should fix it. |
@angussidney that's what the afterFlag param is for |
@angussidney @ArtOfCode- Neither of you bumped the version with the change - the updates aren't getting grabbed as such... |
teward
added a commit
to teward/Userscripts
that referenced
this issue
Nov 1, 2016
No version bump was done so these changes are not caught by userscript update functions. Bump version accordingly.
ferrybig
added a commit
that referenced
this issue
Nov 1, 2016
Version bump (to 1.4.2) as a result of fix for #10
double-fault
added a commit
to double-fault/userscripts
that referenced
this issue
Feb 21, 2017
j-f1
added a commit
that referenced
this issue
Feb 21, 2017
small error, (should) fix issue #10 on the website repo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We initially reverted in 1.3.1 because we couldn't auth with 1.2.x. With 1.4.1, the auth issue is fixed... for typical flagging of a post. However, when "False Positive" is selected, and no API key / write token is stored, the MetaSmoke API page where you can authorize the application is displayed, but the prompt window for entering the API code from that MetaSmoke page does not show up.
It shows up for no-write-token flagging, but not "false positive" recording.
The text was updated successfully, but these errors were encountered: