TYPO3 Core

Currently, there is no possibility to such an automatic checking. However, with the new linkchecker in combination with the upcoming page spider it is possible to check for such links. Then, the link checker can be updated to implement the functionality described in this bug.
Greets, Sebastian

This issue isn't resolved, please reopen it.

This issue (feature request) is about updating the links from the old alias to the new one, not just finding broken links.

Finding broken links doesn't solve this issue for two reasons:
1. The user has to remember the old and new aliases and still manually change all links.
2. When the old alias has been reused before the link check takes places, the links aren't broekn, but point to the wrong page.

OK, it seems that I misunderstood you, sorry. I think without a "global link table" such replacements are impossible... What do you think? Currently, this table can be created with the link checker, but only if the pages have been browsed in the frontend. I am not sure how to fill this table in the BE.
Greets, Sebastian

A possible strategy would be to do an SQL query with regular expressions like this:

SELECT bodytext FROM tt_content WHERE bodytext REGEXP "<link[^>]*( )*oldalias( )*>"

and then do a string replace in the found records. (This REGEXP probably needs to be modified somewhat so that i catches all possible parameters of the LINK tag, but that is possible.)

related to http://wiki.typo3.org/index.php/LinkAbstraction

Hi,
currently I cannot work on this issue, but in general new ideas are always welcome. On the wiki page (linkAbstraction) this idea could be followed there.
Greets, Sebastian

Hi,
the new feature of "reference tables" will make this possible. See http://news.typo3.org/news/article/development-changelog-reference-table/ for details.
Somebody still needs to create an extension for it which might be integrated into the core later.
Greets, Sebastian

Using REGEXP is a no-no, as this is (AFAIK) MySQL-specific, at least non-standard. Thus +1 for the reference table usage. Go, Sebastian! :)