The default bug view has changed. See this FAQ.

Kuma: Add a "what links here" feature

NEW
Unassigned

Status

Mozilla Developer Network
General
P2
enhancement
4 years ago
3 years ago

People

(Reporter: Louis-Rémi BABE, Unassigned)

Tracking

(Blocks: 2 bugs)

Details

(Whiteboard: [specification][type:feature][triaged])

(Reporter)

Description

4 years ago
Before marking a page as junk, it is important to know "what links here".

This feature was available before the switch to Kuma.

Updated

4 years ago
Priority: -- → P2
Whiteboard: feature request;
This would go in the "Site tools" drop-down menu we haven't added yet, along with the dashboards. See bug 841534.
Whiteboard: feature request; → [type:feature]

Comment 2

4 years ago
bug 773855 is about the same feature for templates.

Updated

3 years ago
Whiteboard: [type:feature] → [specification][type:feature][triaged]
Blocks: 724930
fwiw, Sumo has exactly this feature:

https://support.mozilla.org/en-US/kb/common-questions-after-updating-to-new-firefox/links
https://github.com/mozilla/kitsune/blob/master/kitsune/wiki/views.py#L1314
Blocks: 1023763
(In reply to Florian Scholz [:fscholz] (elchi3) from comment #3)
> fwiw, Sumo has exactly this feature:
> 
> https://support.mozilla.org/en-US/kb/common-questions-after-updating-to-new-
> firefox/links
> https://github.com/mozilla/kitsune/blob/master/kitsune/wiki/views.py#L1314

Hmm, though also FWIW, I'm not sure I'd do it *exactly* the way kitsune does it [1].

Looks like they maintain a MySQL table with an inventory of links between docs. Rows get deleted and reinserted on parsing the doc at render time. I'd rather try doing this in elasticsearch as a parse-and-index job in the background, similar to what we do with CSS class names and such.

[1] https://github.com/mozilla/kitsune/commit/2de9fcd0555d42bb62889af7cb2dca00d75e0188
Oh, and another reason why I'd rather do it in elasticsearch: One of our use cases is bug 1023763, where docs are possibly linking to wiki URLs that don't exist yet. The kitsune approach tracks existing docs linking to existing docs. So, that is kind of a non-starter.

I think we need to find all docs that contain a link to some arbitrary URL string, whether that doc exists yet or not.
Duplicate of this bug: 1038515
You need to log in before you can comment on or make changes to this bug.