Paths

Pathauto now has 3 maintainers (greggles, mikeryan and Freso).

We've got a couple of practices that we're trying to follow to help coordinate and minimize work and I thought it could be helpful to share these ideas and allow others to contribute their thoughts on best practices for co-maintainership:

1. Use the Issue Queue: nearly all changes go through the issue queue and are committed using meaningful commit messages

This is a wiki to keep track of changes people will need to keep in mind when they upgrade.

Settings Page Location:

admin/settings/pathauto is now admin/build/path/pathauto and is called "Automated alias settings"

Hi All
I have searched this group & the docs in drupal main site and didn't find the answer, so i am trying here :

Can I use pathauto (with token) that all the posts in group will have path like

groups/{group_path}/[nid]

I want the user to set a path for the group manually (it's hebrew site to i dont want to use [ogname] ), and from than on every post in the group will have this pattern

the issue is that posts can be public and can be a group post , so if i use "Node path settings" it is global

so my questions are :

It's come time for another point release of Pathauto and you can get a "sneak preview" of this by downloading and using 5.x-2.x-dev.

One bug left to fix?

There are still some issues that I'd like to clean up. It seems that 5.x-2.1 caused some problems for modules that make heavy use of taxonomy for their own purposes (forum, image gallery, etc.). Nancyw came up with a patch that will improve the situation for bulk updates: http://drupal.org/node/188606#comment-782627 If more folks could test that, it would be great. That doesn't solve all the problems that 2.1 introduced for these modules, and if someone wants to fix that problem prior to 5.x-2.2 please let me know. Otherwise it will have to be a "known bug".

Bulk Generation Got Faster

Also, stennie came up with some good work to improve the speed of bulk udpates though this code should ideally get some more testing. In fact, all of it needs a little more testing. That's where you come in!

Sneak Preview (aka help test)

If you're a 5.x-2.1 user and can help test this 5.x-2.x-dev you'll help me make sure that 5.x-2.2 will be a nice and solid release so that I can focus on making Pathauto rock for 6.x.

I'm a bit confused about the "0" part of the default feed path of "0/feed". Why is it there, and under what circumstances should I leave or remove it? Apologies if this has been previously asked, I didn't find it.

Somewhere in fall 2007 I started working on Vocabulary Index. The 1.0 version has been available for some weeks now and I have already started working on 2.0 (although a final won't be released for a few months. It's mostly brainstorming at this time).

I would like pathauto to have a behaviour where, when I edit nodes, it will automatically create a new alias for those nodes that don't have an alias yet, but Pathauto should never modify my existing aliases or create duplicate aliases.

Hello folks,

I've fixed a bunch of bugs in Pathauto recently and think it's about time for a 5.x-2.1 release. The current 5.x-2.x-dev is basically what I plan on tagging as a 5.x-2.1. If I could get some "yes, looks good" or "no, need to fix bug #x beforehand" that would be really helpful.

This is likely to be the last release for a couple of months so I'd like it to be really solid.

Thanks.

Hey all,

To get strait to the point.

Pathauto creates alias for taxonomy/term/1 and you can set it to be [vocab]/[catpath].

What if I would like to create more aliases for the same vocabulary like for soccer/[catpath] to be soccer/[catpath] ?

I took a look at pathauto_taxonomy.inc and tried to hard code it in but with no luck.

I would like that so I can rewrite Views urls. Now you can say that I can pass a taxonomy term to a view and solve that.
For some reason it's just not the solution I'm looking for ...

Can anyone help me with this ?

Cheers!

Here's the list of bugs that need to be fixed to get that working:

0 Since I reverted the code so far and stuck it in 180440 that would probably go in first and then...
1 http://drupal.org/node/193825 - maintenance for url_alias_extra
2 http://drupal.org/node/206461 - delete from url_alias_extra as well as creating the entries
3 http://drupal.org/node/201659 - which mostly works, but needs some more work in 193825

Is it possible to use these modules now? It appears with the latest update that the paths aren't being recognized anymore. Any ideas?

Hi,

I've been asking folks to help with this for a while, but the situation is getting more serious (other projects are pulling me away and I will be offline for a while later this year) so I want to make a more clear request for assistance.

If you want to be the maintainer of the module, let me know but also prove that desire by helping in the issue queue and then you get to be the maintainer.

Note that as Pathauto maintainer you kind of also get to be token maintainer since the two are so closely tied.

i am working to call up different backgrounds using the path. i need the category in the path using autopath: like [cat]/[title] - or so i thought. i set it as such in the pathauto config settings, but pathauto is only creating the /[title] path and seemingly ignoring the category demand. on each new entry i AM selecting a category (of course.).

any thoughts on this? i am on drupal 4.7, and have the 4.7 version of pathauto installed (obviously.) has anyone had this experience or know a fix?
thanks
a.

In Pathauto 5.x-2.0 you now have the option (if you have the permission to create aliases) to tell Pathauto not to do its job and instead to let you set the path alias.

There is a new feature in the 2.x development branch of Pathauto which keeps track of whether the admin created the alias or not. If it appears to Pathauto that the admin created the alias, then Pathauto will not try to alias the object in the future.

So,

• create (or edit) a node and uncheck the box for "Automatic alias"

after installing pahauto i see this how to fix it?

You are using the token [user] which has a -raw companion available [user-raw]. For Pathauto patterns you should use the -raw version of tokens unless you really know what you are doing. See the Pathauto help for more details.

I've been working on a few issues that I want to have fixed before a 5.x-2.1 release. I thought I'd create this roadmap so people can provide their own input and also see what is left to do. When the top list gets empty it will be time for a new release. None of these changes are drastic, so the 5.x-2.x-dev release should be reasonably good for people who want to help with testing incremental changes.

If you are one of the folks who enabled the "index aliases" feature and later found out that it wasn't such a great idea then you may be wondering how do I get rid of those aliases? Further, pathauto 5.x-2.x doesn't support them so they are now pretty useless.

You can see if you have any by opening up a connection to your database (e.g. using phpMyAdmin or the mysql shell tool) and running this query:

select * from url_alias where src like 'pathauto/%';

First, some statistics:

I grouped together 4.7-1.x and 5.x-1.x since they are largely the same code base.

Some of those 4.7.x-1.x/5.x-1.x bugs probably can get updated into the 5.x-2 queue or into the Token issue queue. But the point is - new version is pretty golden. Last statistics I saw showed several hundred sites running the 2.x version so it's getting fair amounts of testing.

<

table>
Descriptoin 4.7.x-1.x & 5.x-1.x 5.x-2.x

For users upgrading from Pathauto 5.x-1 to 5.x-2 here are some tips:

5.x-2.0 to 5.x-2.1 note:

The Internal feed alias text (leave blank to disable): is used to determine what, if any, feed alias will be created for the nodes. This was hardcoded previously but due to the fact that other modules can provide the rss feed (e.g. Views) it is now exposed as something that you can change. In general you should either leave it blank or leave it at the default. If you use views for your taxonomy aliases you probable want to use "feed" instead of the default "0/feed".

In reviewing old bugs I dug up: feed aliases don't get updated following normal "update action" settings.

But I'm not sure how this should behave.

One theory is that it should follow the update action because that's what the admin specified.

Another is that it should simply follow the "create new alias in addition to old one" style pattern so that old feed readers won't lose the feed.

Thoughts? "Yet Another Option" doesn't feel very good.

I've lately been working on a few sites with 10K plus path aliases, all generated from pathauto. Mostly on dedicated boxes so resources aren't too much of an issue. It got me thinking about an alternate approach, maybe an addition to pathauto or a separate module. Ok, here goes ...

Pathauto has a nice way of defining path naming rules for content types. These paths are stored in the database as aliases. Good. But how about NOT storing any of these paths in the database. Just "hook" into Drupal to generate a path on the fly based on the pathauto ruleset.

There is some concern that pathauto's i18n integration isn't functioning properly. I don't understand it or have the interest to work on it. So, I'm writing here to say:

1) If it's agreed that nobody has it working, I'll remove it so we don't confuse people about totally buggy code. Please respond either here or in that issue if you have a feeling about that.

Three cheers for duplication and redundancy and doing the same thing over and over and repetitiveness. /sarcasm off...

Ok, well there's a new module called Path Search http://drupal.org/project/pathsearch it searches paths.

You may be confused because it wasn't that long ago that we got a "find path" module (written up here on g.d.o http://drupal.org/project/find_path)

Perhaps the best bits of both can be combined into one super module!

Well folks, I've just done a few changes to pathauto.

The first thing was to create a Pathauto 5.x-1.1 which is likely the last in this line. It should be relatively stable and feature complete with the 4.7 version (or a little better).

The second was to create a new development branch for 5.x-2.x which is where I committed 10 patches that had been sitting in the queue. There may be some "fallout" from all these changes, but I think it's generally headed in the right direction.

A new module was announced yesterday "Find Path"

http://drupal.org/project/find_path

For those of you using Pathauto or URLIFY this could be quite a handy module to keep you from having to go login to your database to edit the records - instead you get this simple interface.

Has anyone tried this? Any thoughts?

Note: I haven't tried it, just read the description

I'm moving my existing corporate site (html) to Drupal and want to include what had been three Wordpress installs in the single Drupal site (1 blog and 2 podcasts). I've got it all pretty much worked out ... except that one of the Wordpress installs lives in a subdomain.

I want to include that content in the main Drupal site/database so it can be indexed with everything else. The question: how do i accomplish this without setting up a second site pointing to the subdomain directory?

I'm interested in something that sounds like maybe pathauto will fill be none of the words I've seen exactly tell me that it does.

So tell me about pathauto. Does it use menus and menu titles to know what to make the alias? Does it use the Title of the node? Is it configurable to use either or both?

Now to go find a menuauto that fills in by default from the node title.

TIA,
Earnie

I hope it's ok to post this here. I first posted this question in the support forums -- but it was suggested that I post here instead since it's a path question.

I'm totally new to Drupal but experienced in SEO and PHP. I've always rolled my own crappy CMS because of custom needs. I'm REALLY hoping Drupal will help me to stop this wasteful methodology.

This wiki page documents a set of test for the Pathauto module. It needs help, but I wanted to publish the work that I've done so far so that others can help in coming up with other tests. Eventually I would like to turn these tests into something that can be automated with a tool like selenium and then run them before making any commits/releases.

One TODO: decide on a reference module that implements it's own pathauto to use for testing. Date could be a good one.

without further ado....

Pathauto Test Pattern for Pathauto 5

Prior to a 5.x release I'd like to finish off these issues:

Remove listing page functionality
Remove Index Aliases
Remove or Make optional the Transliteration
New algorithm and/or exposed control for transliteration

And of course this bug:

taxonomy_get_term and illegal_offset errors when adding taxonomy/nodes

It would be great to get some comments from folks on some of these issues because I haven't really decided on whether to do them or not. I'll also post back here when I've got a more firm "beta" for 5.0 and 4.7 for people to test and will then do a tag release.

Steven recently got frustrated enough with the Drupal core restriction on international letters in path module that he removed it..

So, now pathauto and urlify can use any character from the node title that the user submits.

I've created an issue for pathauto to see how to best handle this. Please provide your input on the ideas there.