Replies: 2 comments
-
|
Even with the new dates it doesn't seem to work for me. Created #1108. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Yes, sorry I didn’t update. It doesn’t work for me anymore, and I think I misunderstood what the problem is when opening this thread. In fact, it doesn’t seem to be a timestamp problem. Categories are only taken into account once the file has been opened. Thank you for opening an issue, I missed time to do it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I don’t fill a bug report as I’m not sure it is not intended and when the problem started. I don’t feel qualified to consider it as a bug myself as it’s just need some adjustment from the user, which is normal when using a fast moving project as neorg !
It may comes from a8f7a9e who kind of broke
generate-workspace-summary, at least it’s linked to a change in the timestamp format that disturb the parser.Most of my neorg files have categories in the metadata like :
or
generate-workspace-summarydon’t sort links by categories anymore if the categorized files have the old timestamp in the metadata. All files are "uncategorised".Updating the file (so the updated field) solves the problem. It works as intended with the following sample :
@champignoom would be in a better position to judge if it’s need more investigation and devs attention/time, but I share it here as it may help other end-users facing the same problem, as it’s easy to fix by the users themselves : just re-save the considered files or update the updated timestamp with some shell command. New workspaces and files will use the new timestamp by default so the problem should not occur in the future.
Tell me if it’s worth a bug report or need some infos !
Beta Was this translation helpful? Give feedback.
All reactions