Why require so many timestamps?

[xeruf]

Why does a lazyblorg post require a CREATED and a MODIFIED property, if we can already deduce these from the logbook?
This feels annoyingly redundant.
Would be good to document these requirements as well in the steps of the readme, and which timestamp is used for which purpose.

[novoid]

Good point. Somewhere I think I summarized the reasoning but that can be made more accessible.

In short: CREATED is created automatically in my setup so it's no effort on my side.

I don't think that MODIFIED is part of lazyblorg.

[xeruf]

true, it requires CREATED and a logbook - my setup unfortunately depends on the used file at the moment so I often have to edit post properties
anyways, still don't see the use of this redunancy

[novoid]

What do you mean "on the used file"?

[xeruf]

I have different org defaults for different org files.

[xeruf]

So the logbook timestamp is used for dating the post and the published footer, I am struggling to find out what created is used for after all?

[novoid]

The parser parses it and stores it under entry_data['created'].

lib/htmlizer.py doesn't seem to use it for anything at the moment.

It looks to me that the parser is expecting it (and reports an error if missing) but it is not used. As a test, you could remove the corresponding check in __check_if_entry_is_OK() (orgparser.py, 4 lines) and do a test-run if everything is working. If so, report back and I'll think about removing it upstream as well.