Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It would not be normal in a production site, but if a translation "source" node is deleted without previously deleting all its translations, then the MultiLink cache will not be properly updated, because translation_node_get_translations() will no longer return relevant translations. The result is that links may be shown to the deleted source node, resulting in a 404 if they are clicked. Since ML does not provide a way to manually clear or rebuild its cache, there is no simple solution. User would either have to edit all relevant ML links in content, or clear the ML cache via db tools.
Comments
Comment #1
Andy Inman CreditAttribution: Andy Inman commentedRelated, if a node in the translation set is deleted (not the "source" node) then cache entry for *that* node should be deleted but is not. Confirmed these issues have been in all versions of ML.
Comment #2
Andy Inman CreditAttribution: Andy Inman commentedFixed, and released as 2.3.