template="pages" appears blank but template="table" works fine
See original GitHub issueThanks for putting this together! It’s really nice. I’m unclear how to proceed to debug this, but I’m able to get images only when I use template="table"
. If I try template="pages"
(or leave it blank), then I can only see the “Sort by” bar, screenshot below. I’ve tested this using mols2grid
version 0.0.3, in a relatively clean conda
environment, on macOS using Chrome Version 89.0.4389.90 and Firefox 87.0b9.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Personal template opens as blank document for one user only
When she opened Word, selected Personal for templates and then clicked on the letterhead (it shows up there), a new BLANK document (Documentn) ......
Read more >Remarkable keeps setting the template to blank on all pages
I had the same problem with my Remarkable2. The preset template was grid, but after some pages, it became blank!
Read more >My page is blank when I try to import templates - Elementor
Learn everything about My page is blank when I try to import templates in this article from Elementor's Knowledge Base. Get Elementor tips...
Read more >Mysterious blank page appears before front page when ...
However, if I change oneside to twoside in the book class there is a mysterious first page appearing before the front page, with...
Read more >Why is my create page from template not working?
As I said, it works fine when opening in a new tab or window. So the answer to your question is no, the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had the same problem when I had a “nan” in the data frame.
I’ve just published a fix in v0.0.4 which should fix the NaN issue, can you try it ?