dave123

I released a new version 1.2.4 that removed the call to get the token id, or at least not fail when that happens. The token id isn’t really necessary to verifying the user but I was capturing it as part of the registered user’s profile, to maybe add the nft image as their profile image and other things. It’s hard for me to fully test your scenario without buying some new nft’s so let me know if you run into any errors. I appreciate your help

Yes, this info helps. The plugin uses a contract method called tokenOfOwnerByIndex to determine which token in the collection the account owns. The problem is that I see now that this is an optional part of the spec and not all contracts implement it.

Your token contract does not implement it and therefore gets error
https://etherscan.io/address/0x244FC4178fa685Af909c88b4D4CD7eB9127eDb0B#readContract

For comparison, look at the methods of another token contract which does include the method https://etherscan.io/address/0xa3AEe8BcE55BEeA1951EF834b99f3Ac60d1ABeeB#readContract

I’ll need to think about how the plugin can still work without this method. Specifically, the content locking feature uses the token id that is found with that method

I didn’t get any error using that contract. Of course, I don’t have that NFT so the verification didn’t pass, but no console errors.

The error stack looks like it’s coming from Metamask extension (inpage.js:1) and not the NFT Login plugin’s javascript. Is there anything in the stack from nft-login-module.js?

At what point does the error occur? After you click the verify button or when the page loads? Maybe try disconnecting and reconnecting your account in Metamask

You can input your own contract address just enter into the Contract Address field.

Other pages can be locked by checking the box under NFT Content Protection. Look for the checkbox on the right side of the Edit Post page, near where the tags and categories are set.

On which chain is the contract and is it ERC721? There is a known issue with ERC1155. Can you share the contract address?

New version 1.2.3 is available with the contract and address match error removed

When logging in, “Verified NFT does not match registered user” means that the contract and wallet address at login do not match the ones that were used when the user registered. Could be that you changed the contract address after registration, or that a different wallet was used?

Back when I added that, I guess I was thinking to make sure it was the same user that registered. So, if you register for the site but then sell your NFT, the new person with the NFT should not be able to login as the person who originally registered because the wallet would be different. But now I’m thinking this check may not be necessary and I should remove it.

In the meantime, to get past this error, you could either register a new user. Or go into the wp_usermeta table (or find a user metadata plugin) and update with the correct contract and address.

You can open an issue here https://github.com/davehagler/nftlogin/issues which allows images

Please try the new version 1.2.2 which has some fixes

Give version 1.2.2 a try. Thanks for helping!

Yes, thanks for the help. The callback name got changed in a prior version. I think some of us may be running with looser error handling so the missing function didn’t cause a fatal error and the plugin appeared to be working. I added the function back in version 1.2.1 of the plugin. Hopefully this will fix your error

That’s an interesting use case for an NFT. As I understand it, you want the NFT verification to be optional at registration, and the user group would be set depending on if they verified or not. That’s not something that the plugin does today.

You might be able use the content locking feature to achieve the same result. The promotions posts would be locked and only NFT holders would be able to see the contents.

Polygon network is supported now as of version 1.2.0

Thanks. These are good features I will add to the roadmap

Just released a new version of the plugin 1.2.0 with Polygon support. Give it a try and let me know

I tried a clean WordPress install with no plugins and installed NFT login and no errors. Do you have other plugins installed? Maybe try deactivating them to see if one of them is causing the error. There is now a new 1.2.0 version of the plugin you could try. There isn’t anything specific to address your error but maybe it will work.

Localhost shouldn’t be a problem. I use localhost for testing too.