The problem is that it parses all the links within the tables, now this might not be a bug per se but my only option is to tell related links to not show up in all the nodes where I use table manager tables with links, which is counterproductive as some of the tables show links that should be discovered or parsed by related links but not all of them. So my request is for a smart way for this module to detect the administrative links--edit, delete, and the sortable table headings--and exclude those from the parsed links, and just parse the real links--links to other nodes, outside/external links. At the moment I get every single link inside a table, including the edit/delete links that show up for me as an admin, plus the link on the heading columns that are sortable.

Comments

rgracia’s picture

bump

rgracia’s picture

Is anyone supporting this module? I have waited two days now and no sign of acknowledgement from any person responsible for it.

rgracia’s picture

Edited: doesn't belong here.

rgracia’s picture

Edited. need to put request elsewhere.

Zen’s picture

Title: Bug when used with Table Manager » Parsed links: Avoid cataloguing unnecessary links
Version: 5.x-2.2-beta » 6.x-1.x-dev
Category: bug » feature
dman’s picture

Title: Parsed links: Avoid cataloguing unnecessary links » Parsed links: Avoid cataloguing unnecessary links (in-page #anchors)

Hijacking this issue, as it seems it's not exactly the same cause, but the request is similar:

Avoid parsing in-page #anchors as related links :-)

I've got some large pages which have their own table of content which links to sections inside the same page.
relatedlinks finds these and (accurately) lists them as found links, but y'know, I don't rally need to see them there :-)

Should be a reasonable feature request to just *not* index #anchor hrefs?

Also, while I'm feature dreaming, maybe a way to split off and treat or group external links differently from site-local ones.