Yes I have CVS access, and am a longtime contributor to drupal. Thank you for your trust and appreciation, your too kind.. Best regards, Stefan Op 15-feb-2006, om 17:05 heeft naudefj het volgende geschreven:

Hi Stefan,

I'm sure the community will appreciate if you can jump in and maintain it!

Please contact the previous maintainer, Mike Ryan, to make the necessary arrangements. Also, do you have a CVS account? If not, please private mail me so I can help you to apply for one.

Best regards.

Frank

On Wednesday 15 February 2006 17:44, Stefan wrote:

...

Yes, I would LOVE to... This is a module I _really_ would like to maintain and improve (from a usability point of view) further..

please let me know if you would like me to be the new maintainer...

Stefan

Op 15-feb-2006, om 16:37 heeft naudefj het volgende geschreven:

...

Hi,

...

...

I'm no longer maintaining pathauto. However, I did update it to Drupal 4.7 - if you're using the latest CVS, it should work for you (unless there have been core changes since I last updated it). Mike Ryan

Anyone interested in taking over ownership of the PATHAUTO module?

Best regards.

Frank

--- Stefan Nagtegaal Drupal-Devel@iStyledThis.nl Drupal Development Mailinglist

--- Stefan Nagtegaal Drupal-Devel@iStyledThis.nl Drupal Development Mailinglist

Congratulations! And thanks for taking on the module! - Ken On Feb 15, 2006, at 12:07 PM, Stefan wrote:

For every one else on this list:

As you probably read on the list, I became the new maintainer of the pathauto-module.

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..

Hope to hear from you guys soon,

Stefan

PS: It looked like I disappeared for a couple of months, but I was moving houses. Tomorrow, my wife, kids and myself are permanently moving to our new home and I'll be available again for drupal related coding.

Op 15-feb-2006, om 17:43 heeft Stefan het volgende geschreven:

...

Yes I have CVS access, and am a longtime contributor to drupal.

Thank you for your trust and appreciation, your too kind..

Best regards,

Stefan

Op 15-feb-2006, om 17:05 heeft naudefj het volgende geschreven:

...

Hi Stefan,

I'm sure the community will appreciate if you can jump in and maintain it!

Please contact the previous maintainer, Mike Ryan, to make the necessary arrangements. Also, do you have a CVS account? If not, please private mail me so I can help you to apply for one.

Best regards.

Frank

On Wednesday 15 February 2006 17:44, Stefan wrote:

...

Yes, I would LOVE to... This is a module I _really_ would like to maintain and improve (from a usability point of view) further..

please let me know if you would like me to be the new maintainer...

Stefan

Op 15-feb-2006, om 16:37 heeft naudefj het volgende geschreven:

...

Hi,

...

> I'm no longer maintaining pathauto. However, I did update it to > Drupal > 4.7 - if you're using the latest CVS, it should work for you > (unless > there have been core changes since I last updated it). > Mike Ryan

Anyone interested in taking over ownership of the PATHAUTO module?

Best regards.

Frank

--- Stefan Nagtegaal Drupal-Devel@iStyledThis.nl Drupal Development Mailinglist

--- Stefan Nagtegaal Drupal-Devel@iStyledThis.nl Drupal Development Mailinglist

--- Stefan Nagtegaal Drupal-Devel@iStyledThis.nl Drupal Development Mailinglist

Hi Stefan, Thanks for taking on this important responsibility: pathauto is one of my favourite Drupal modules, and I know that many Drupal users depend on it heavily, for having a website that exhibits the Zen of URL semantics. ;-) One of the things on my to-do list is adding support for the category module (http://drupal.org/node/39683) to pathauto. I'll submit a patch for this when I get around to it. However, the category module is currently 4.7-only, so pathauto has to be upgraded to 4.7 first before this can happen. Cheers, Jaza.

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

A -1 for inclusion in core as it is. We need the *functionality* in core, but certainly not in this particular imlpementation.

I guess I also need to disclaim: "please refrain from voting on issues that are not up for vote". Also, we no longer cache all aliases at start of request. Let's not spread FUD. Storing 100,000 aliases is likely no longer a performance problem. I don't think that will be much slower than storing 100 aliases since the table is indexed on path. Benchmarks would say so definitively. I'm not against some token system but I don't think it is necessary.

On Thursday 16 February 2006 11:44, Bèr Kessels wrote:

We talked about tokenised menu system. Making that system work two ways (path->callbacks AND url()->paths) is the route to take IMO. Storing 20.000 blogs/My_user_name/feed is not a good idea. Storing one blogs/%username/feed that is parsed/cached for earh url() or so is a better idea. And no, I am not volunteering for this, but that fact should not rule me out of the -1ers for this one in core. :)

I'm not sure what was discussed in this tokenized menu system, so this may be what people already discussed when I wasn't looking, but what about defining a given menu as the "site tree" menu? If you have a menu: (contact, download, products (widget, cog, sprocket), support), then it seems logical that you'd have path aliases of: contact download products products/widget products/cog products/sprocket support For performance, the site tree menu could be compiled on edit to a simple associative array, and then reversed as well. Save both to the cache (or variable, or whatever). Then on page request pull out the reversed array and do an isset() check, and on l() pull the array out and static cache it. Total cost for l(): one SQL hit and n isset() calls. That would cover a LOT of sites quite easily and provide a user-friendly way to avoid seeing node/xxx pages, which corporate sites for instance wouldn't particularly like. The path table still overrides that, of course. Set the Primary Links menu to the Site Tree menu to the only Menu_OTF menu, and now you're cooking. <waits to be told that it's been thought of and rejected> (And yes, don't even think about coding it until after 4.7...) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson