Comment 1 for bug 1402736

I think the original link is fine (the one you get when the page is first rendered from the template) but then the JS code in charge of updating the node's fields kicks in and changes the href property with a bogus link.