Submitted by greggles (not verified) on Fri, 2008/02/15 - 11:39.
Good to hear the update went smoothly.
It's the Pathauto module not "autopath" (nor "auto_path" nor "path_auto" as so many people like to say).
The update status issue may be temporary and related to new releases. Since the code that runs on drupal.org is very expensive the results are cached so newly released packages are not listed.
The code also allows maintainers to signal to users that they should downgrade, so I don't think the simple version check you propose would solve that problem. The better solution is proposed and in the issue queue (update the relevant bits of the cache for updated projects).
*cough* /Path/autho *cough*
Good to hear the update went smoothly.
It's the Pathauto module not "autopath" (nor "auto_path" nor "path_auto" as so many people like to say).
The update status issue may be temporary and related to new releases. Since the code that runs on drupal.org is very expensive the results are cached so newly released packages are not listed.
The code also allows maintainers to signal to users that they should downgrade, so I don't think the simple version check you propose would solve that problem. The better solution is proposed and in the issue queue (update the relevant bits of the cache for updated projects).