Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

todo-ignore is ignored on journal pages that were created from templates #63

Closed
BreiteSeite opened this issue Dec 10, 2023 · 2 comments
Closed

Comments

@BreiteSeite
Copy link

Steps to reproduce:

  1. create a template that includes that todo-ignore: true property as part of the template content (not to confuse with template properties) which contains TODO items
  2. set the template as journal template in config.edn
 :default-templates
 {:journals "Template name here"}
  1. let logseq create todays journal page (ensure todo-ignore: true is at the beginning of the journal page)

Expected output:

  • TODO items are not listed in the plugin

Actual output:

  • TODO items are listed in the plugin (as scheduled as well as anytime)

Workaround:

  • update the property manually on the generated journal page
@ahonn
Copy link
Owner

ahonn commented Dec 11, 2023

Thank you for your feedback. I will fix this issue asap.

ahonn added a commit that referenced this issue Feb 4, 2024
…operties-missing

fix: fixed journals template properties missing, #63
github-actions bot pushed a commit that referenced this issue Feb 4, 2024
# [1.21.0](v1.20.2...v1.21.0) (2024-02-04)

### Bug Fixes

* fixed journals template properties missing, [#63](#63) ([450cdf9](450cdf9))

### Features

* refactor task creation process, force focus after create new task, [#68](#68) ([c7dc80e](c7dc80e))
* support task scheduled time sorting ([9570e68](9570e68))
@ahonn
Copy link
Owner

ahonn commented Feb 4, 2024

This seems to be a bug in Logseq. When you use a template to create a journal page automatically, the properties are not parsed correctly. However, this issue is resolved when you reopen Logseq.

I have found an alternative workaround for it, so please update to the latest version. If you have any questions, just let me know.

If you like this plugin, feel free to show your appreciation by buying me a coffee. It will motivate me to continue maintaining it.

@ahonn ahonn closed this as completed Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants