-
Notifications
You must be signed in to change notification settings - Fork 69
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
Fixes issue with QIT authentication parsing #9755
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.34 MB ℹ️ View Unchanged
|
@dmallory42 following the guide to set up QIT, I noticed there are
In my case, the QIT thing works because it looks like this:
so, we may not need this improvement, WDYT? |
Hi @oaratovskyi, sorry - only now seeing this comment!
We still need it, even if you use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for explanation @dmallory42 ! It's good to go then
Fixes #9750
Changes proposed in this Pull Request
Prerequisites
Please read the P2 post linked for context on QIT and create the
local.env
file as specified in the instructions.Testing instructions
develop
, use a password with a space in it in thelocal.env
file for theQIT_PASSWORD
variable (it doesn't need to be the correct password to see this error).npm run test:qit-security
No arguments expected for "partner:add" command, got "<password>".
See: PaJDYF-6n7-p2
npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge