logseq / logseq/logseq

Cannot import from Scrivener

Open
#6,587 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

can-be-reproduced import
Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

### What happened?

Cannot import from Scrivener via OPML format.

### Reproduce the Bug

It shows "An unexpected error occurred during block extraction."

### Expected Behavior

_No response_

### Screenshots

_No response_

### Desktop Platform Information

MacOS 10.14.6 (18G2022)

### Mobile Platform Information

_No response_

### Additional Context

_No response_

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the Scrivener OPML import and tracing the reported “block extraction” failure on the stated macOS version. The issue names no source file or test; done means a Scrivener-generated OPML file imports without the unexpected extraction error.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.