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

Restrict synced items with space based sync with memex-desktop Logseq/Obsidian #1278

Open
TimLamoureux opened this issue Aug 16, 2024 · 1 comment

Comments

@TimLamoureux
Copy link

TimLamoureux commented Aug 16, 2024

Can you describe the problem and bug in more detail?
In the Import and Integrations settings, when configuring a Only sync pages & annotations that have these Spaces such as logseq_sync, I expect only the pages and annotations tagged/saved to that space to be sync'ed by memex-desktop. However, whenever I save or highlight a page (often by mistake), it shows up in Logseq because it gets sync'd.

Versions:

  • Memex 3.20.10
  • Memex desktop 0.0.50
  • Happens irrespective of browsers (though only Chrome based browsers have been tested). Chrome 127.0.6533.120 and Arc for Windows 1.15.0 (43650)

How can we replicate the issue?

  1. Install Memex-desktop
  2. Configure Import & Integrations for either Obsidian or Logseq. Select your sync directory (local dir in my case), File name format (Memex___{{{PageTitle}}} in my case), Only sync pages & annotations that have these Spaces (logseq_sync in my case, tried other variations such as test or multiple space names separated by commas). Date format: YYYY-MM-DD. Optional: Can set the Sync tags for pages (from_memex in my case).
  3. Ensure Sync Helper is Online is showing up
  4. Highlight or save any page, don't add it to a space. It will get synced to Logseq or Obsidian folder.

Expected behavior (i.e. solution)

Only pages tagged with logseq_sync or test should get synced, not every page saved or highlighted.

Error stack (from extension crash page)

No error stack. Sync happens when it should not.

Other comments

@TimLamoureux
Copy link
Author

Extra information for anyone coming here:

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