Org doesn't resolve [[id:UUID::*subtree name][link name]] hyperlinks

Question

I'm trying to make org links leveraging the org-id-link-to-org-use-id and org-id-link-consider-parent-id variables, as described in section 4.5 of the org manual (Org mode buffers paragraph's example). But org doesn't resolve these links.

I get these error:

• org-roam-id-open: Cannot find entry with ID "3b654d4d-b4a9-4cf5-a5bf-d55335f3853e::*subtree name" with org-roam activated
• org-id-open: Cannot find entry with ID "3b654d4d-b4a9-4cf5-a5bf-d55335f3853e::*subtree nwme" using a plain emacs -Q instance.

Whether the ID property is attached to a headline that is inside the same org file, or to another file's buffer properties leads to the same result.

EDIT: added the following example

Here is how I would do a minimal example:

• create and save sractch.org
• create an * example heading
• add an ID property to that heading using org-id-get-create
• create a ** first subtree heading under * example
• create a ** second subtree heading following the first one
• call org-store-link while point is under ** first subtree heading
• call org-insert-link while point is under ** second subtree heading, enter the description test link.

Here is what I get (as raw text):

* example heading
:PROPERTIES:
:ID:       f3805217-ff72-4dbe-b8aa-72a266eb5498
:END:
** first subtree heading

** second subtree heading

[[id:f3805217-ff72-4dbe-b8aa-72a266eb5498::*first subtree heading][test link]]

EDIT 2: This used to work as I updated to org 9.7.14 but now stopped working again!

EDIT 3: Trying to troubleshoot again. I've updated org to 9.7.15.

When I start emacs normally, i.e. using the systemd daemon + an emacsclient, org-version returns 9.7.15, and the minimal example fails with the org-roam-id-open message.

When I start a quick emacs -Q, two things happen:

1. Inside my Packages buffer, I see org 9.6.15 as built-in and org 9.7.15 as "dependency", while the latter is set as (manually) "installed" when I start emacs normally.
2. When I open an org file, org-version returns 9.6.15, so I'm unable to confirm that org 9.7 works as it should and that org-roam is the culprit.

Thanks for your help!

Answer 1

Well, thanks for asking for a version check, this feature appeared in 9.7 as stated in the changelog

I'm not sure why, but my info pages were more up to date than my built-in org package…