We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While searching for logseq docs via DDG ( https://duckduckgo.com/?t=ffab&q=logseq+docs&ia=web ) the second entry points to https://logseq.com/docs which is a blank page. Please update the page to mention that you really want to go to https://docs.logseq.com/ or setup a redirect to the correct location.
logseq docs
1: go to https://logseq.com/docs 2: note page is empty with no indication that docs are located at https://docs.logseq.com
a non blank page with some text like:
docs can now be found at <a href='https://docs.logseq.com'>https://docs.logseq.com</a>
able to replicate on macbook air and android pixel 6a
No response
The text was updated successfully, but these errors were encountered:
Thanks for your report. Track this at logseq/sites#33
CC @xyhp915
Sorry, something went wrong.
No branches or pull requests
Search first
What Happened?
While searching for
logseq docs
via DDG ( https://duckduckgo.com/?t=ffab&q=logseq+docs&ia=web ) the second entry points to https://logseq.com/docs which is a blank page. Please update the page to mention that you really want to go to https://docs.logseq.com/ or setup a redirect to the correct location.Reproduce the Bug
1: go to https://logseq.com/docs
2: note page is empty with no indication that docs are located at https://docs.logseq.com
Expected Behavior
a non blank page with some text like:
docs can now be found at <a href='https://docs.logseq.com'>https://docs.logseq.com</a>
Screenshots
Desktop or Mobile Platform Information
able to replicate on macbook air and android pixel 6a
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: