Outliner plugin super-picky about block formatting

Help
1

(not sure if I should post this here or in a plugin bug reports section? where would that be?)

I would really like to migrate from Logseq to Obsidian (Logseq search functionality is weak and no good sync options), but the Outliner plugin in Obsidian is so temperamental that I can’t get it to work for even short 12,000 word pages.

The Outliner plugin will almost always respond to the Expand/Collapse keyboard shortcuts, even if it doesn’t like some of the formatting, but it will not do move up/down (with children) or indent/outdent (with children).

It would be great if the Outliner plugin would highlight which blocks it doesn’t like and even better would be to offer suggestions for changing the block to a format it does like.

Someone else had this problem back in Jan 2024 (Strange behavior in Outliner plugin - #13 by ariehen) and was told to just search through their files to find the problems.

But when I search through files imported from Logseq, it is quite messy to fix things. And in some cases, I can’t find any way to fix the block it doesn’t like.

But I have learned that it doesn’t like:
-places where I had numbers in Logseq. Even when I delete all of the front-end stuff, it doesn’t always like that block
-shift-Enter carriage returns instead of regular line breaks

Thanks for any help you can give!

2

The place to report plugin bugs is on the plugin dev’s GitHub.

1 Like
3

As this report is about a community plugin, I’ll move it to Help.

As Synchronicity suggested, please check their GitHub page for issues and/or you can post a report there.

1 Like
4

Thank you so much for your guidance. I found an open issue for this in the plugin’s github page. People shared there that the problem is primarily when spaces and tabs get mixed at the start of lines. But cleaning these up over many, big files is quite daunting. Manual clean-up is possible but there don’t seem to be any tools/functionality yet for auto-highlighting problems or auto-correcting the problems.

All of this means that it is quite hard to use the Outliner plugin with imported (or not fully conforming) pages.