The Calendar view uses a 1 or two digit month and day argument. Pathauto seems to only have support for [mm] and [dd] two digit only formats.

So it would be great to have a new [m] for 1 or two digit month and [d] for 1 or two digit day, as in token.module

Comments

greggles’s picture

Project: Pathauto » Calendar
Version: 5.x-1.0 » 5.x-1.3

I believe that's up to calendar module to do, not pathauto.

@Karens - I don't know which version you want so I selected the latest official.

karens’s picture

Not completely sure what the issue is. You're saying the Calendar arguments must have the leading zero for pathauto to work, or are you saying some change needs to be made to the pathauto.inc file?

greggles’s picture

Project: Calendar » Date
Status: Active » Postponed (maintainer needs more info)

Maybe it's actually a feature for the Date module (which has pathauto integration) and not calendar - sorry for the mis-label on that.

This isn't a bug, but a feature request to have new patterns provided by "The Calendar". I'm not sure which calendar this is so I'm marking it as active (needs more info).

In general I can agree that the date related modules (Date, Event) should have both [m] and [mm] style patterns. So, once we find out which "Calendar" this issue is against we can get to work :)

neubreed’s picture

Hey,

It's this module: http://drupal.org/project/calendar

Thanks everyone...

greggles’s picture

Except that I don't think calendar provides pathauto integration, right?

So this is against Date which is used by calendar.

karens’s picture

Correct, there is no pathauto integration for Calendar, only Date. I'm not familiar enough with pathauto to know what fix to make, so if someone can supply a patch, that would be great.

karens’s picture

Status: Postponed (maintainer needs more info) » Active

Making this active again so someone can find it to provide a patch :-)

karens’s picture

Title: [m] and [d] compatibility with calendar view arguments » Pathauto needs [m] and [d] compatibility
Version: 5.x-1.3 » 5.x-2.x-dev

Bumping this, I need someone using pathauto to suggest a patch.

greggles’s picture

I'm not really sure. Now that I look at this more closely it's for Pathauto5.x-1. I believe this is solved in Pathauto5.x-2 (which relies on token). So, I think we can just close this is "fixed" (since I think it's fixed in token) or "by design"/"won't fix" since I don't plan to put any effort into integrationfor 5.x-1 and I doubt anyone else will.

karens’s picture

Status: Active » Closed (won't fix)

OK, won't fix then :)