Closed saffar4ever closed 1 year ago
hey sorry for the late reply, the most likely explanation is that some tags
pages are private, thus not exported and that breaks the css.
the easiest solution is to use publishing/all-pages-public? true
in your config.edn
, but that would publish all pages so make sure you are not exposing private stuff.
alternatively, you can go to the respective page of each Tag
used in logtools (eg: .v-kanban
, .v-kanban-wide
, ...there are a bunch of them) and add a public:: true
page-property (it HAS to be in the first block, as a page-property).
Then the export
will also export the tags and hopefully solve your issue.
for the record, the css relies on html attributes [data-refs] and [data-refs-self], if you are using tags that are not public, these attributes will be empty as in the pic below :
closing for now, but feel free to reopen if the issue is not fixed with the steps above :)
I added the public:: true
to the tag and it worked! Thanks a lot for the solution, much appreciated.
Hello,
I really like the plugin and the potential that offers. Unfortunately, I have faced a productivity stopper. I'm not sure whether it's a bug with the plugin or a bug with Logseq or something I have missed regarding the CSS code.
My target is to export the pages retaining the effects of the plugin specifically the Kanban columns. This is the issue I'm currently facing. I have tried many attempts but none of them worked. I have tried copying the CSS code of the plugin to the custom.css. I have tried copying the CSS code of the plugin to the export.css. The weird thing is that my modifications to the custom CSS file are reflected in the Logseq application; however, it is not reflected after the export. For example, I have tried the following code on the custom.css even without the CSS code of the plugin:
div[data-refs-self*="eisenhower-matrix"]>.block-children-container.flex>.block-children>div.ls-block { display: inline-block; width: 46%; overflow: auto; margin: 5px; height: 30rem; /* default value is 18rem */ }
Here I was attempting to increase the height of the matrix. Surprisingly, it worked without even the CSS code of the plugin. It worked within the Logseq application, but it didn't work after exporting it to HTML pages.
I would really appreciate some advice or assistance to get the CSS effect to work after exporting the pages. Since, it seems that I ran out of options to try, I became very confused, as I started to think that Logseq may have retained some code behind the scene, which I doubt it.
Please let me know if there is anything I can do to resolve that.
Kind regards, Meshaal