Thanks for reporting @MarkS. So far I was unable to reproduce this on Joplin v3.6.14 (Android). When I click on a checkbox in the Markdown editor / preview / RTE / ITN panel, the checkbox state changes and remains stable on my end, even after a few seconds. I'll keep watching though to see if this occurs. I recommend checking the latest Android pre-release (or wait for it to be released soon). Perhaps ITN causes this in the presence of another plugin (that I don't have)?
Thanks for the update.
Does this always happen after your computer has slept, or have you seen it during continuous use?
How much RAM does your machine have?
Could you install the latest v2.10.2 of the plugin? It includes a few optimisations that may reduce memory usage. If the plugin will take longer to freeze, this may help diagnose whether this is memory-related.
So the good news is that after updating to v2.10.2, the checkbox problem seems to have disappeared.
The bad news is that sorting by the custom field sorting appears to have broken. The sorting appears to be random. So if you test you need a large enough set of data because small sets of random data can sometimes accidentally be in the order you want.
SUGGESTION FOR FUTURE UPDATES: I think it'll be great if items can be grouped by custom properties like colour, nested tags, etc. just the way it is with sorting. Thanks again for this great plugin.
I'm using the custom regex to treat checkboxes as tags (as documented) (?<=^|\s)(([#@+]|//)([^\s#@'",.()[]:;?\]+)|(-\s[[x\s@?!~]]))
This allows me to search for all open tasks (- [ ]) across all notes - combined with tag inheritance, it's incredibly powerful for my outliner-style journal workflow.
However, when Search: Highlight filter / tag results is enabled, the checkbox tags get highlighted too, which breaks their visual rendering as interactive checkboxes (they show as plain text instead of clickable squares). Disabling highlight fixes the checkboxes but removes highlighting for all other tags (#project, @mentions, etc.).
Request: Would it be possible to either:
Exclude checkbox-pattern tags from highlight rendering, or
Add a setting/CSS class to selectively disable highlight for specific tag types?
Have you tried this: ^(?!.-\s[[xX]]).+ in your filter? It excludes checked boxes as opposed to including unchecked boxes. It might work, it's what i use.
Thanks @xpleromax! Could you share more about your workflow with this filter?
My challenge: I want a single dashboard showing all open tasks across all notes and all projects. But Tag Navigator requires a tag to start a search – the filter only works on results that are already found by a tag query.
That's why I made checkboxes into tags (via custom Tag regex) – so I can search by - [ ] directly across all notes. It works, but breaks checkbox rendering when Search: Highlight filter / tag results is enabled.
Please see the combined screenshot:
Example note
With checkbox Tag regex + Search: Highlight filter / tag resultsenabled - checkboxes render as plain text instead of interactive squares
With checkbox Tag regex + Search: Highlight filter / tag resultsdisabled - checkboxes render correctly, but tags like #important and #blocker are no longer highlighted
That gets sorted at the start of the month instead of near the end. Sorting by custom #2026. I think it’s because “#monthly” is being treated as “#month” internally, being viewed then as #2026/04 . But to me “#monthly” shouldn’t be the same as “#month”.
There's actually no need to make check boxes into tags, that seems to be complicating things, this is what i should have said in the first place if i saw the pictures. Actually, if you delete the regex you are currently using to make checkboxes tags from your settings and type that same regex into the "filter tags box" (see picture below), it'll produce the result you want without any issues. There no need to use this ^(?!.-\s[[xX]]).+ anymore except for any other reasons.
I just had my computer sleep after starting Joplin about half an hour before, and it was still working when I came back and woke it back up, this was with v2.10.2.
I have 32 GB of RAM.
This morning when I logged on the plugin had stopped working overnight.
Joplin is using quite a bit of memory, about 1.8 GB. If I remove the plugin and restart Joplin it runs around 862 MB after it’s initial loading. If I turn the plugin on again and restart Joplin it runs around 1.1 GB after initial loading. I will note the value the next time it freezes up.
I asked about this because I suspected that this could be memory related. I tried to do my best from the plugin side, but also opened an upstream issue in Joplin (#14919, resolved in #14920). So if this is indeed memory related, I expect it to be resolved soon.
I was converting individual notes and I noticed converting inline tags to Joplin did not work 100% of the time, if the note had any kind of attachment. I had quite a few notes with PDF attachments or images in them.
I'm not sure how attachments could affect conversion, but if you can provide an example that fails (does it reproduce consistently?), I'd be happy to check.
I'm experimenting today and I only see the problem when I am in the WYSIWYG editor. But in the WYSIWYG editor, some notes without attachments fail to convert tags also. In the Markdown editor it works 100% of the time.
One thing I am seeing in bothe Markdown and WYSIWYG editor is if you delete Joplin tags that the plugin created, but still have inline tags and then try to convert inline tags to Joplin tags, it fails. I'm not sure if that's expected behaviour.
I honestly only needed this plugin to convert the notes I imported from Obsidian to use Joplin tags. So, don't go nuts trying to fix this, since I am sure that this is not the intended use-case of the plugin.
