[go: up one dir, main page]

Skip to content
New issue

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

Possible bug / missing feature #11404

Open
1 of 2 tasks
ullech opened this issue Jul 3, 2024 · 0 comments
Open
1 of 2 tasks

Possible bug / missing feature #11404

ullech opened this issue Jul 3, 2024 · 0 comments

Comments

@ullech
Copy link
ullech commented Jul 3, 2024

Search first

  • I searched and no similar issues were found

What Happened?

Suppose I do have two graphs, one synced on remote, another one just locally.
If I switch between the graphs I assumed the fav- and recent-tabs (including pinned pages) would sync with the selected graph. If not, I do have pinned links, fav-pages which points to no indexed files (and therefore do not display any content)

Reproduce the Bug

  1. Make sure two have at least two graphs (not sure if one of them have to be remote)
  2. Pin and make a few pages as favourites in both of the graphs
  3. Switch to 2nd graph, the fav/recent tabs still show the items from 1st graph

Expected Behavior

fav/pinned/recent data should sync with the selected graph

Screenshots

No response

Desktop or Mobile Platform Information

App Version: 0.10.9
Git Revision: c67b8b5
Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.10.9 Chrome/118.0.5993.159 Electron/27.1.3 Safari/537.36
Language: en-US
Plugins: logseq-bullet-threading (v1.1.4), logseq-tabs (v1.19.4), logseq-tocgen (v2.13.0)

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

  • I'm willing to submit a PR (Thank you!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant