Logseq does not update date links after changing the date format and those links become invalid. This is a plugin that replaces those links.
In Logseq, changing the user date format after graph construction is challenging. This is because even after performing a re-index, the links remain with the old date format. ( Logseq#4279 ) To address this issue, this plugin has been developed.
Warning
This plugin does not work with Logseq db version.
- Main: Replace journal links on all files
- Replace it from the legacy format to new format. Search and replace in queries.
After changing user date format and running re-index on Logseq.
- Replace inactive links with format yyyy-MM-dd, which is consistent with Obsidian.
- Replace it with hierarchy-enabled yyyy/MM/dd format.
- Replace it from the legacy format to new format. Search and replace in queries.
- Option: Redirect when open a page
- Enabling the use of expired links due to changes in user date formatting. When opening the page, if the title matches the legacy format, it will redirect to the journal page. Enabling this option prevents links from becoming inactive.
Install from Logseq Marketplace
- Press [
---
] on the top right toolbar to open [Plugins
]. Select marketplace. TypeOld
in the search field, select it from the search results and install.
-
Setup from Plugin Settings
-
Replace from the legacy format to new format
-
After changing the Date format, it's necessary to perform a re-index in Logseq. There are a few important points to note:
- The UUID of blocks gets changed, which might lead to the inability to use features like embedding or references.
- Pages other than journals have their "create-at" creation date property updated. This is an invisible property.
Go to the Discussions tab to ask and find this kind of things.
- Recommend
Date format | Today |
---|---|
E, d MMMM yyyy | Tue, 19 September 2023 |
E, MM/dd/yyyy | Tue, 09/19/2023 |
E, dd-MM-yyyy | Tue, 19-09-2023 |
E, dd.MM.yyyy | Tue, 19.09.2023 |
E, yyyy/MM/dd | Tue, 2023/09/19 |
EEE, MM/dd/yyyy | Tue, 09/19/2023 |
EEE, dd-MM-yyyy | Tue, 19-09-2023 |
EEE, dd.MM.yyyy | Tue, 19.09.2023 |
EEE, yyyy/MM/dd | Tue, 2023/09/19 |
EEEE, MM/dd/yyyy | Tuesday, 09/19/2023 |
EEEE, dd-MM-yyyy | Tuesday, 19-09-2023 |
EEEE, dd.MM.yyyy | Tuesday, 19.09.2023 |
EEEE, yyyy/MM/dd | Tuesday, 2023/09/19 |
MM-dd-yyyy | 09-19-2023 |
MM/dd/yyyy | 09/19/2023 |
dd-MM-yyyy | 19-09-2023 |
dd.MM.yyyy | 19.09.2023 |
yyyy/MM/dd | 2023/09/19 |
MM_dd_yyyy | 09_19_2023 |
do MMM yyyy | 19th Sep 2023 |
do MMMM yyyy | 19th September 2023 |
yyyy-MM-dd | 2023-09-19 |
yyyy-MM-dd EEEE | 2023-09-19 Tuesday |
yyyy/MM/dd | 2023/09/19 |
yyyyMMdd | 20230919 |
yyyy_MM_dd | 2023_09_19 |
yyyy年MM月dd日 | 2023年09月19日 |
- Author > @YU000jp