Nested Page Title Links lead to Wrong Page

[LeonBein]

Search first

• I searched and no similar issues were found

What Happened?

When referencing a page that has two other references in its title, such as [[[[Strawberry]] [[Cake]]]] for the page called [[Strawberry]] [[Cake]], clicking on the resulting link leads to a page with missing brackets, in the example it leads to Strawberry]] [[Cake.

Reproduce the Bug

1. Write a block with [[[[Strawberry]] [[Cake]]]] and exit edit mode with Esc
2. Click on the resulting link
3. You are now at page Strawberry]] [[Cake

Expected Behavior

The link should lead to page [[Strawberry]] [[Cake]]

Screenshots

No response

Desktop or Mobile Platform Information

Windows App, Version 0.9.17, revision 645a8d3

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[LeonBein]

Btw, using links via the graph view works, i.e., it seems as if clicking on links in text and clicking on graph nodes use different logic to determine the target. (I'd assume because the text one also has to determine what part of the text belongs to the link?)

[gbro3n]

Here is another example:

If the link is `[[[[Butterfly [[Sweep]]]] from [[Half Guard]]]]``

Clicking 'Butterfly' in [[Butterfly [[Sweep]]]] goes to Butterfly [[Sweep]] page (as expected)
Clicking 'Sweep' in [[Sweep]] goes to Sweep page (as expected)
Clicking 'Half Guard' in [[Half Guard]] goes to Half Guard page (as expected)

Clicking 'from' in [[[[Butterfly [[Sweep]]]] from [[Half Guard]]]] goes to butterfly [[sweep]]]] from [[half guard page (which does not exist)

[HumanistAtypik]

Yeah you are right! Very messy. It has always been my nightmare in Logseq, since all my graph relies on intricate/nested node names...

[github-actions]

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!