PELLUCID ANSWERS CODE

It doesn't translate 1-on-1 with the Links button in the menu, but it should give you some pointers in the right direction.Īs to your 2nd question: I believe that yes, the Link database does need to be rebuilt. While you're at it you could of course also put in some sorting functionality :-) You could possibly check whether the link item is the latest version, possibly by using something like.

PELLUCID ANSWERS CODE

From looking at it very quickly I think the code to change (which is actually in the nested Scanner class) is. For your requirements, what I would say would be the easiest is to create your own version of the BrokenLinksForm, possibly simply adding an export functionality on it, or modify the code so it only takes the latest version. Using Reflector you can see what it's executing. The application that gets started is /Applications/Tools/Broken Links.aspx, so if we look at *webroot*/sitecore/shell/Applications/Tools/Broken Links/Broken links.xml, we can see that the code used for it is .BrokenLinks.BrokenLinksForm in the Sitecore.Client assembly.

In the Core database you can check what gets executed on the click of the Broken Link Report (the item that defines it is located in : /sitecore/content/Documents and settings/All users/Start menu/Right/Reporting Tools/Scan for Broken Links. For your first (and partly third) questions:

Pellucid answers