[Solved] Moved from Logseq - get my Wikilinks back on Track

This post was last updated for 448 days ago, and the information may already be changed

Hi guys,

Imported my Markdown files as folders from Logseq. The wiki links no longer work. These are - superficially - in the same format, but of course do not reference the corresponding GUID under the hood. But now to rewrite thousands of wikilinks within this complete package by hand is something for people who have nothing to do all day. Search and Replace does not do it. Does anyone have a good idea for this?

Best regards

Achim

    1 Operate
    TaxDevOp updated this article at 2023-09-02 04:24:02

    Related articles

    Welcome to here!

    Here we can learn from each other how to use SiYuan, give feedback and suggestions, and build SiYuan together.

    Signup About
    Please input reply content ...
    • ciwoyipang 1 Comment

      If you're talking about [[]] links.

      This link may be helpful?

      automatic link- Quicker (getquicker.net)

      1 Operate
      ciwoyipang updated this reply at 2023-06-04 10:08:53
      English is recommended, thank you.
      88250
    • MiscReply
    • ednico
      VIP Warrior

      I recently imported from both Obsidian and Logseq - worked an absolute treat. Did have to remove a folder the Logseq creates if not was getting an error but once that wa done, wow. Very good job all.

    • frostime

      To date, there is no official level solution that might quickly resolve [[wiki-links]] (or ref-links called in SiYuan) from other software.

      The community does have some solutions of its own, but they are dependent on other software and not very internationalised, so it is not certain that it would cost you too much extra to use them.

    • ciwoyipang

      Document level conversion is currently supported by a software called Quicker, but there is no English version available.

      The conversion plugin may arrive soon, and we hope that capable users can participate more in plugin development and enrich usage scenarios.

    • Visit all replies