Can't save new token format
See original GitHub issueRelated to #45. I tried to work around it by:
- Inspect element and removing the
disabled
attribute from the Save button - The input has attribute
pattern="[\da-f]{40}"
which doesn’t match the new token format — should bepattern="[\da-zA-Z_]{40}"
“Save” still doesn’t work tho :\\
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Error when installing and can't save contract/token names
First, I can't save contract address and token Name in NFT Login Plugin settings. Secord I got this error: Plugin Configuration.
Read more >Where to store my Git personal access token? - Stack Overflow
This allows to store the password/personal access token in an encrypted format. The git config file can be found in the .git/config file...
Read more >Troubleshoot Invalid Token Errors - Auth0
Select the OAuth view, change the value of JsonWebToken Signature Algorithm to RS256, and select Save Changes. If you proceed with this option...
Read more >Behind GitHub's new authentication token formats
Behind GitHub's new authentication token formats. We're excited to share a deep dive into how our new authentication token formats are built and ......
Read more >Creating a personal access token - GitHub Docs
In the left sidebar, under Personal access tokens, click Tokens (classic). Select Generate new token, then click Generate new token (classic). Give your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay, this should be fixed in 37232f0f1cf15f445872d9b1b73ada4cf79923d2
Will take a bit to propagate through the extension stores as usual
Hey, 0.2.4 is the latest version, with all token validation removed. Is it still not working for you?