This might be an issue with CCK....

Under 'Node path settings,' I am trying to set the pattern for all press release paths like so:

press/releases/[field_release_date]

and for events like so:

calendar/[cat]/[field_date]

The date fields (which are named correctly) aren't showing up in the URLs. It's like the fields don't exist. I have also tried other CCK fields to make sure it's not a date.module issue. I get the same bad results.

Comments

robomalo’s picture

robomalo commented
Title: Not working properly with CCK » I forgot to mention

When I create a new node, then click submit, the path is created. The really, really bad thing is that all aliases with CCK fields disappear and aren't written when I do a bulk node path update.

jvalletto’s picture

jvalletto commented
Title: I forgot to mention » Not working properly with CCK
Priority: Normal » Critical

I am also having this issue, so you are not alone.

To confirm:

When a node is individually created, the correct path set in pathauto works.
(e.g. /reviews/[field_software_type]/[title] would be correctly set as /reviews/open-source/drupal/)

When bulk updated the [field_software_type] seems to dissappear.
(e.g. /reviews/[field_software_type]/[title] would be incorrectly set as /reviews/drupal/)

So there is obviously a bug with the bulk updating with CCK.

Since this can severly hurt by having to manually set the individual paths for already created content, I set this as critical.

I hope this clears things up, and makes it easier to diagnose the problem and fix the bug.

Thanks,
Jeremy.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Closed (duplicate)

Hello, thanks for your reports and the detailed descriptions of how to repeat the problem.

I believe this is a duplicate of http://drupal.org/node/69789

If you would like to see this committed, please test that patch and let us know if it solves your problem. It would also be helpful if you would review the code and see if it makes sense to you.

Please don't comment on that issue only to change the priority to critical. I hope to have it fixed within the next week and changing the priority won't accelerate that.