Hi Fish
You would have to sign with the same wallet address binded to your Liker Id.
Could you please check if your Liker ID is binded with the same wallet address displayed in your metamask?
You can check your binded wallet address in https://like.co/in/settings , you can also bind a address with metamask if you haven’t done it yet.
Thanks William,
By using the link you provided, I found that the wallet address is exactly the same as the fox (metamask) shown on my Chrome Browser.
Is there any other way to check it ?
Fish
Hi Fish
Can you please check if there is any error shown in the Chrome Developer console?
Please navigate to “Your LikeCoin Rewards” in LikeCoin plugin settings( ${your_wp_site}/wp-admin/admin.php?page=lc_user_options) , right click anywhere blank in the page, click Inspect, choose Console tab in the Chrome Developer tools popup.
Please try to click “Connect to Liker ID” with the above developer tool open, and see if there is any error.
Please also attach a print screen of both the setting page and console.
Sorry for all your trouble.
Hi William,
It’s my pleasure to improve like.coin plugin.
Attached please find both the console and the plugin error for your information.
Thanks for your assistance.
Fish
https://nimb.ws/ex4ykT
Hi Fish,
Thank you very much for helping the plugin development
It looks like it is related to the new default privacy mode of metamask
We are investigating the issue and is working on a fix, should have a develop build update in a few days
Hi Fish,
We have just released plugin version 1.2.0
Please see if it solves your problem
Thanks
Hi, William,
It works! Thanks Billion!
Fish
Hi,
I can’t connect the Liker ID. I’ve installed the metamask on my browser, and have a liker ID. When I click the connect Liker ID, the browser will popup a blank page, close itself and nothing happened. Please help me to solve the issue.
Thanks
Ching
Hi Ching,
We are currently moving to a new version which allows you to input your Liker ID directly, without dealing with MetaMask.
Would you please update to version 1.3.0, and see if it works for you?
Hi William,
I updated to 1.3.0 and it works. Thank you.
Ching