link tool lookup window should open to link reference's container

[Andy Altepeter]

If an existing link in kupu goes to an area within Silva, it would be neat if the "get link reference" button in the link tool opened the lookup window to the container of the existing link.

Use case: I accidentally selected the wrong link, in the same container as the correct link, and that container took five clicks in the lookup window to get to.

(this may happen more frequently now that clicking the radio button places the link)

[Eric Casteleijn (thisfred)]

Hmm, I thought we had this solved. I know we do in DLCMS, so it should be ported to silva core if it isn't already there. Assigning to my bad self...

[Andy Altepeter (aaltepet)]

I should point out that this "lack of a feature" was in Silva 2.0, so it is quite possible that the trunk is working correctly.

[Andy Altepeter (aaltepet)]

this is actually rather difficult. how do you determine whether a link is a valid path, and from that how you know what the container is? It may be possible to send the existing link as a parameter, and then, the first thing the lookup window does is determine if the existing link is a path to a silva object, get it's container, and redirect.

[Kit Blake (kitblake)]

The lookup window is probably the most complex screen in Silva. This adds yet more complexity but it's a great feature.

It should be possible to check whether the linked object exists, then get it's container, and use that path as the url. Or maybe check whether the linked object is a container, and if not, go to its container. This could handle the not found use case, and bring the user to the container where the link destination used to be.

Of course, the enclosing container could be not found too, so I guess we should check whether it exists, and if not, just bring up the lookup window in the current container.

[Andy Altepeter (aaltepet)]

this is now implemented and checked into the Silva trunk (to be 2.2)