KosmosisDire / obsidian-webpage-export

Export html from single files, canvas pages, or whole vaults. Direct access to the exported HTML files allows you to publish your digital garden anywhere. Focuses on flexibility, features, and style parity.
https://docs.obsidianweb.net/
MIT License
693 stars 58 forks source link

[Bug]: DataView The control displays normally within the editor, but after exporting to HTML, the specific content is not visible. #435

Open zhoulonghao520 opened 1 month ago

zhoulonghao520 commented 1 month ago

What happened?

[Bug]: DataView The control displays normally within the editor, but after exporting to HTML, the specific content is not visible.

editview:

image

1 文档导航

dataview

table

where 版本="V1.11"

readyview:

image

HTMLVIEW:

image

Reproduction

null

Last Working Version

No response

Version

V1.8.01

Operating System

macos

Obsidian Version

Version 1.5.12 (Installer 1.5.8)

Which browsers can you reproduce this in?

No response

Relevant log output

NULL

Additional Info

No response

KosmosisDire commented 1 month ago

Does this work for any dataview or is all dataview broken? Can you give details for how to reproduce this?

zhoulonghao520 commented 1 month ago

TestNote.zip 发布.zip

image

I have prepared an example, please take a look.

zhoulonghao520 commented 1 month ago

Myplugins.zip

zhoulonghao520 commented 1 month ago

image

TickStop commented 1 month ago

I had the same issue. This only seems to be a problem when "Enable Inline JavaScript Queries" is disabled in the Dataview plugin settings. This plugin (Webpage HTML Export) probably uses JavaScript to create the HTML documents. So just enable Inline JavaScript Queries and you should be fine.

cnschu commented 2 weeks ago

I have the same problem. Enabling "Enable Inline JavaScript Queries" in dataview fixes the problem only temporarly.

Reproduction

1) "Enable Inline JavaScript Queries" = on 2) export to HTML 3) everything is fine 4) change something in your vault 5) export to HTML 6) the table from Dataview is empty 7) "Enable Inline JavaScript Queries" = off 8) "Enable Inline JavaScript Queries" = on 9) export to HTML 10) everything is fine 11) change something in your vault 12) export to HTML 13) the table from Dataview is empty

It is reproducable.

If you enable "Enable Inline JavaScript Queries" before the export, it works fine. if you leave "Enable Inline JavaScript Queries" untouched, the exyport is flawed.

Operating System

Windows 11

Which browsers can you reproduce this in?

workaround

1) Dataview / "Enable Inline JavaScript Queries" = off 2) Dataview / "Enable Inline JavaScript Queries" = on 3) Export

nnkn commented 2 weeks ago

+1 ,me too

coder114514 commented 11 hours ago

I have the same problem. Enabling "Enable Inline JavaScript Queries" in dataview fixes the problem only temporarly.

Reproduction

1. "Enable Inline JavaScript Queries" = on

2. export to HTML

3. everything is fine

4. change something in your vault

5. export to HTML

6. **the table from Dataview is empty**

7. "Enable Inline JavaScript Queries" = off

8. "Enable Inline JavaScript Queries" = on

9. export to HTML

10. everything is fine

11. change something in your vault

12. export to HTML

13. **the table from Dataview is empty**

It is reproducable.

If you enable "Enable Inline JavaScript Queries" before the export, it works fine. if you leave "Enable Inline JavaScript Queries" untouched, the exyport is flawed.

Operating System

Windows 11

Which browsers can you reproduce this in?

* Chrome

* Edge

workaround

1. Dataview / "Enable Inline JavaScript Queries" = off

2. Dataview / "Enable Inline JavaScript Queries" = on

3. Export

This workaround is not working for me. After tweaking "Minify HTML" and restarting obsidian it succeeded, but it does not seem to be very consistent.