Bug #61154
closed"Migrate all file links of RTE-enabled fields to FAL" fails with "Reference index was probably out of date."
0%
Description
Meanwhile I did upgrades from TYPO3 4.7 to 6.2 for three different instances and every time I ran into this problem.
Reason are links in content elements of hidden or (from database point of view: logical) deleted pages where the target (usually the file in fileadmin) does not exist anymore.
cli_dispatch.phpsh lowlevel_refindex -cdoes not detect these broken links. So this is a deadlock during migration.
I found this workaround which requires using a SQL client for the mysql database:
1) check if the result of this query matches the list of "Reference index was probably out of date" elements
select * from sys_refindex where softref_key = 'typolink_tag' AND ref_table = '_FILE';
2) If so you can update these records:
update sys_refindex set softref_key = 'typolink' where softref_key = 'typolink_tag' AND ref_table = '_FILE';
Updated by Michael Ganner over 10 years ago
Christoph Ascherl wrote:
I found this workaround which requires using a SQL client for the mysql database:
1) check if the result of this query matches the list of "Reference index was probably out of date" elements
[...]2) If so you can update these records:
[...]
I also ran into this problem. But the described workaround did the job perfectly :) Thank you!
Updated by Uwe Jakobs almost 10 years ago
Same problem with upgrading to 6.2.10.
Workaround confirmed. Thank you!
Updated by Joe Schäfer almost 10 years ago
Same problem while upgrading from 4.5.x to 6.2.11...
Workaround worked fine. Thank you!
Updated by Heinrich Pegelow almost 10 years ago
Same problem while upgrading from 4.5.40 to 6.2.11.
Workaround worked fine. Thank you!
Updated by Andreas Drygala almost 10 years ago
Same problem while upgrading from 6.0.12 to 6.2.12.
Workaround worked fine. Thank you!
Updated by Thomas Beck over 9 years ago
Same problem while upgrading from 4.5.40 to 6.2.14.
Updated by uwe no-lastname-given over 9 years ago
Same problem while upgrading from 4.5.40 to 6.2.15.
Updated by Stefa No almost 8 years ago
Same problem while upgrading from 4.5.40 to 6.2.30.
Workaround (=query 1&2) seemed to work fine.
Thank you!
Updated by Riccardo De Contardi over 7 years ago
- Status changed from New to Closed
Sorry, but this will not be fixed as TYPO3 6.2.x has reached its end of life.
@christoph - Ascherl we owe you a big "thank you" for having provided a workaround that had so many positive feedbacks and will help the people in need of it.
Best Regards
Riccardo