Imported Notes without a Zotero schema marker are imported with an empty body

[BlueBlueKitty]

ZotLit version

2.1.1

Host application versions

Obsidian 1.13.7, Zotero 10.0.1, Winodows 11

Obsidian debug info

SYSTEM INFO:
	Obsidian version: 1.13.7
	Installer version: 1.13.7
	Operating system: Windows 11 Pro 10.0.26100
	Login status: not logged in
	Language: zh
	Insider build toggle: off
	Live preview: on
	Base theme: adapt to system
	Community theme: none
	Snippets enabled: 0
	Restricted mode: off
	Plugins installed: 12
	Plugins enabled: 11
		1: ZotLit v2.1.1
		2: Custom Attachment Location v11.10.0
		3: Image Converter v1.4.6
		4: Claudian v2.2.5
		5: Remotely Save v0.5.25
		6: Recent Files v1.7.10
		7: Tasks v8.4.0
		8: Easy Typing v6.0.9
		9: Editing Toolbar v4.1.1
		10: Calendar v1.5.10
		11: Find orphaned files and broken links v1.11.0

RECOMMENDATIONS:
	Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Reproduces in a sandbox vault?

Yes

Steps to reproduce

What happened

When an Imported Note is created by a Zotero plugin and then imported into Obsidian through ZotLit, the generated Markdown file contains only frontmatter. The note body is empty.

This happens when the Zotero note contains ordinary HTML but does not include Zotero's data-schema-version marker.

Example affected note

The note was automatically created by a Zotero plugin. Its content is ordinary HTML similar to:

<h2>Summary of a Research Article</h2>

<p><strong>Source:</strong> Academic literature review</p>

<p><strong>Summary date:</strong> 2026-07-22</p>

<div>
  <p>
    This article examines how environmental changes can be detected
    using satellite observations and statistical analysis.
  </p>

  <p>
    The authors combine observations from multiple sources to improve
    the accuracy and reliability of the results.
  </p>

  <h3>Key findings</h3>

  <p>
    The study shows that combining complementary data sources can
    improve detection performance, especially in areas with incomplete
    or noisy observations.
  </p>

  <ul>
    <li>The proposed method improves the consistency of the results.</li>
    <li>The approach can be applied to large geographic areas.</li>
    <li>Further validation is needed for operational use.</li>
  </ul>
</div>

The note starts directly with elements such as <h2>, <p>, and <div>. It does not contain a Zotero schema wrapper or a data-schema-version attribute.

Steps to reproduce

1. Use a Zotero plugin or automation to create a child note containing ordinary HTML.
2. Confirm that the note does not contain data-schema-version.
3. Create or update the corresponding Literature Note in Obsidian with ZotLit.
4. Import the child note.
5. Open the generated Imported Note in Obsidian.

Expected behavior

ZotLit should attempt to convert the note body from ordinary HTML to Markdown, even when the Zotero schema marker is absent.

The example above should be imported with its headings, paragraphs, bold text, and list items preserved as Markdown.

When a supported Zotero schema is present, the existing Zotero-specific parsing behavior should remain unchanged. If conversion fails, ZotLit should preserve the content or show a clear warning instead of silently creating an empty note.

Actual behavior

The imported Note is empty.

Logs or screenshots

No response

[aidenlx]

will be fixed in next version

[aidenlx]

Fixed in ZotLit 2.1.4, out now.

A Child Note created by a Zotero plugin or by automation carries ordinary HTML with no Zotero note-editor schema marker, and ZotLit only converted notes that had one — so the body was dropped and you were left with frontmatter alone. These notes now import with their content intact: headings, paragraphs, bold text, and lists all become Markdown. Notes written in Zotero's own note editor import exactly as before.

Update the plugin from Settings → Community plugins, then re-import the note.

Release notes: https://zotlit.aidenlx.site/changelog/2.1.4

Thanks for the clear report and the sample HTML — being able to see that the note started straight in at <h2> with no schema wrapper is what made this quick to pin down.