[BUG] The `Open a local directory` and `Add existing graph` buttons are missing

Open
#1,479 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
desktop

Research direction

Start by tracing the graph options and all graphs menu in the Logseq desktop app, then check how the Shift+Alt+G action is registered on Windows. Reproduce with Logseq 2.0.2 by opening the sidebar and selecting the graph title, then All graphs. Done when both local graph buttons appear and work, including opening an existing graph.

Written by the indexing model from the issue text.

Description

Search first
  • I searched and no similar issues were found
What Happened?

After a recent Logseq update, the Open a local directory and Add existing graph buttons disappeared from the graph options and all graphs menu, and Shift+Alt+G shows Yes, add a local graph, but clicking it again, opens an URL through the OS, not in Logseq, with no registered link handler

Reproduce the Bug
  1. Open Logseq
  2. Open the left sidebar
  3. Click on the graph's title
  4. The Add local graph option is missing
  5. Click on All graphs
  6. The Open a local directory button is missing
Expected Behavior

Add local graph and Open a local directory buttons appear and work

Screenshots
Image Image Image
Desktop or Mobile Platform Information

Windows 11 Pro
Logseq 2.0.2

Additional Context

I'm trying to import an existing graph after OS reinstall

Are you willing to submit a PR? If you know how to fix the bug.
  • I'm willing to submit a PR (Thank you!)
Dominant language
No language data
Stars
29
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from logseq/db-test

All issues in logseq/db-test

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.