logseq / logseq/logseq

Cannot type anything in "Zotero data directory" when connecting to Zotero, otherwise config.edn will be broken

Open
#7,448 5 comments 0 reactions 1 assignee View on GitHub

@xyhp915 is already working on this.

Since Nov 24, 2022.

:type/enhancement integration:zotero os:windows user-config
Dominant language
Clojure
Stars
45k
Forks
2.8k
Avg merge
1d 22h
Merged PRs (30d)
105

Description

### What happened?

`It seems that your config.edn is broken. We've restored it with the default content and saved the previous content to the file logseq/broken-config.edn.`

### Reproduce the Bug

Open `Zotero Settings`, type the path of zotero in the text box of `Zotero data directory`, then logseq will prompt `It seems that your config.edn is broken. We've restored it with the default content and saved the previous content to the file logseq/broken-config.edn.`

`

### Expected Behavior

No error shold be occured

### Screenshots

![image](https://user-images.githubusercontent.com/47599849/203722542-24ea7bee-c2f0-4285-b71d-b34949fc8212.png)

![image](https://user-images.githubusercontent.com/47599849/203722630-1f7f81ad-ec53-401a-acb0-3c2bfa2f0211.png)

![image](https://user-images.githubusercontent.com/47599849/203722706-d2b63148-4235-4d74-9a97-c2cb323f9cd7.png)

### Desktop Platform Information

Win 11, Logseq 0.8.11

### 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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.