I use it on my blog, but to be honest I think the current path system makes pathauto unusable for core inclusion. A more robust algorithmic url-aliasing mechnism, like the one that chx and company brainstormed a few months ago, has a lot more potential IMO. On large sites, auto-generating aliases creates unmanagably huge path tables, colliding urls with ugly _0, _1, _2 suffixes all over the place, and so on. That's not a failing of pathauto, just a testament to how much it DOES do in an alias scheme that's not well suited for some of the things it's often used for. --Jeff
-----Original Message----- From: Moshe Weitzman [mailto:weitzman@tejasa.com] Sent: Thursday, February 16, 2006 9:55 AM To: development@drupal.org Subject: Re: [development] Re: Update pathauto to Drupal 4.7
I'm planning to work on the pathauto-module next monday, so if anyone has idea's. plans or other big things in mind for the pathauto.module, don't hesitate to contact me..
So many people love this module, that I think it merits consideration for core. I suggest that you ask around the dev team for what features they want in a "pathauto for core." in the end, i hope that you will move part of your module into path.module and part will remain in Contrib. I haven't used the module yet on a real site, so I can't be of much use.
Someone is bound to say "yes, but not for 4.7". If that was going to be you, please try to restrain yourself from stating the obvious.
-moshe