legacy.module provides backwards compatibility for old-style paths and urls, like node/view/1 and node.php?1 if I remember correctly. It makes no attempt to provide legacy *API* support. Even that module reflects Drupal's philosophy that data (and urls/paths/end user experience) is sacred, while APIs and internal administrative tools are always subject to refactoring. --Jeff On Aug 13, 2007, at 8:18 AM, Earnie Boyd wrote:
One of the 4.6.x, 4.7.x and 5.x modules is named legacy[1] to provide supposed backward compatibility[2]. I do not know if it works, haven't tried it. Is is sticking around for 6.x? Should it go away? I've never seen it mentioned in this or the support list as a viable solution. I don't find it listed[3] so maybe it is gone already.