You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, thank you for this amazing plugin! I want to take the opportunity to report a bug that has been confirmed by others.
Whenever I move a page or whole sub-namespace (?), I have noticed that the relative namespace removes the "~:" in front of the namespace and it reverts back to ":" -- For example.
In one of the sub-namespaces, I would have:
[[~:example|Example Link]]
And I move a page, it would suddenly be (note the tilde is gone):
[[:example|Example Link]]
The result is that I would have to go back to every page that references the relative link and manually update the link to add back in the "~" tilde to make it relative again to the sub-namespace.
Is there a way to make it so that Links to the relative sub-namespace/folder in a given page are automatically updated after a Move?
The text was updated successfully, but these errors were encountered:
splitbrain
changed the title
Relative Link Broken after Moving a Page
Plugin breaks new ~ syntax for page relative namespace links
Mar 28, 2024
Hi there, thank you for this amazing plugin! I want to take the opportunity to report a bug that has been confirmed by others.
Whenever I move a page or whole sub-namespace (?), I have noticed that the relative namespace removes the "~:" in front of the namespace and it reverts back to ":" -- For example.
In one of the sub-namespaces, I would have:
[[~:example|Example Link]]
And I move a page, it would suddenly be (note the tilde is gone):
[[:example|Example Link]]
The result is that I would have to go back to every page that references the relative link and manually update the link to add back in the "~" tilde to make it relative again to the sub-namespace.
Is there a way to make it so that Links to the relative sub-namespace/folder in a given page are automatically updated after a Move?
The text was updated successfully, but these errors were encountered: