Good to know :up: I must admit, I still don't know if there was anything changed that might make it behave differently. So the mystery is not solved, but at least it's resolved :)

Ahh, I think I see what is going on. If a user account has contributed say a story, then the user URL is aliases:

http://de.castlecops.com/user/paul

If a user has not contributed, then the alias is not created:

http://de.castlecops.com/user/15

You can compare... http://de.castlecops.com/

"By mrrockford at Thu, 03/11/2005 - 05:55 "

"mrrockford" is aliases. If you check "Who's new", none at the moment are aliased.

So there seems to be a condition (without checking the code).

Correct :)

Roger that. Is there an option to cron this?

The module author has that planned for the next release.

10-4 thanks.

Quick question on maintaining this for the moment. I'll run the pathauto batch updates, and instead of /user/paul I get /user/paul_0 although there is no other paul. I think go into the url_aliases under admin and fix it up.

I believe the problem may have been with keeping old aliases but creating new ones too. So I simply selected overwrite any old aliases.

Is this alright?

Yes, the bulkupdate should only be used once. I'll make an update to make it update when a user enters their first blog/node entry, so this wouldn't happen.

Perfect, I'll let you know how it goes.

@tamarian, I got the update email but I don't see an attachment here?

Oops. Try it again.