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

Error importing a File Graph: A duplicate journal page is created when the page contains a task #192

Closed
1 of 2 tasks
geosmina opened this issue Dec 18, 2024 · 5 comments
Closed
1 of 2 tasks

Comments

@geosmina
Copy link

Search first

  • I searched and no similar issues were found

What Happened?

When I try to import a File Graph, all the Journal pages that have a task in them end up duplicated. The new pages created are blank and only have the Linked Reference to that same date.

  1. The page with tasks:
    Task in a Journal

  2. The blank page with the linked reference:
    Duplicated Journal Entry

Reproduce the Bug

  1. Go to "Import existing notes".
  2. Select "File to DB Graph".
  3. Select the File Graph folder.
  4. Import
  5. Search for a journal page that has a task in it. There should be two pages with that date.

Expected Behavior

No response

Files

No response

Browser, Desktop or Mobile Platform Information

Logseq DB 0.10.10 - 7c2d17e
Firefox 133.0 (64-bit)
Google Chrome 131.0.6778.108 (64-bit)

Additional Context

  • This behavior is independent of the status of tasks.
  • This appears to only occur in journals where the tasks have a deadline.

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

  • I'm willing to submit a PR (Thank you!)
@logseq-cldwalker
Copy link
Contributor

Hi. Same feedback as in #191. We'll need the specific files in order to reproduce the issue

@geosmina
Copy link
Author

Files sent by email for privacy reasons. If you need more, please let me know.

logseq-cldwalker added a commit to logseq/logseq that referenced this issue Dec 19, 2024
as block's page. Switched to using page-names-to-uuids instead
of db since it has the uuids of current page. Fixes logseq/db-test#192
@logseq-cldwalker
Copy link
Contributor

Obrigado. A fix should be up on test.logseq.com in ~10m

@geosmina
Copy link
Author

Worked as a charm!

@logseq-cldwalker
Copy link
Contributor

logseq-cldwalker commented Dec 19, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants