Currently when clicking the connect button and it fails, the error message is "Unknow issues, may you can connect with author".
Should be "Unknown issues. Maybe you can contact with the author.".
More importantly, most often this error is because Logseq is not running, or the API Server is not started. So, instead of "contact with the author", we should prompt the user to check these first. E.g. :
[Connection failed] (button)
(text) Can't connect to the Logseq API Server. Please check that:
1. Logseq is running.
2. Logseq API Server is started. ((link)Guide)
3. The Logseq host and token entered above are correct.
API Server doesn't need Developer Mode in the latest Logseq, so the setup guide should be changed accordingly.
Currently when clicking the connect button and it fails, the error message is "Unknow issues, may you can connect with author".
Should be "Unknown issues. Maybe you can contact with the author.".
More importantly, most often this error is because Logseq is not running, or the API Server is not started. So, instead of "contact with the author", we should prompt the user to check these first. E.g. :
API Server doesn't need Developer Mode in the latest Logseq, so the setup guide should be changed accordingly.