I'm using pathauto on Drupal 6.2. Under "Node path setting", I removed the "Default path pattern" and instead added it to Blog, Forum and Story (i.e., I want to create url aliases for "Page" manually).

However, with "Default" disabled for pathauto, no url aliases are created for Blog entries. If I add "content/[title-raw]" back to the "Default path pattern", it works as expected (even if "Blog" has it set separately), but this way I cannot set the page aliases manually.

CommentFileSizeAuthor
#3 257473_6_alter_form_language_regression.patch965 bytesgreggles

Comments

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: No auto paths for "Blog entry" » No auto paths for "Blog entry" if default is blank
Status: Active » Postponed (maintainer needs more info)

I just tried this on both 5.x and 6.x and was unable to repeat the behavior as you describe.

Perhaps you can start with a fresh test site and see if the behavior is easy to repeat? Is there anything else that needs to be done to get this to occur like use of other modules or settings?

rene_w’s picture

rene_w commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

My bad -- the aliases are actually created after hitting save. The difference I've seen is that with the default pattern set, the "URL path settings" field is grayed out when creating a new entry, whereas with "default" empty and "blog pattern" set, it is emtpy and editable, which looked like automatic aliases are disabled.

Sorry for the confusion & thanks for the help.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: No auto paths for "Blog entry" if default is blank » the node/add node/nid/edit form doesn't get the checkbox/disable when default pattern is blank but with node specific pattern
Status: Closed (fixed) » Needs review
StatusFileSize
new 257473_6_alter_form_language_regression.patch965 bytes

Ah, then that's a different bug and I definitely CAN reproduce it :)

Can you test out this patch? There was a bug introduced in #208860: Add per-language patterns for multilingual node types which caused this.

rene_w’s picture

rene_w commented

OK, glad this makes more sense to you ;)

Unfortunately I can't test the patch right away as I'm currently traveling and have only limited ssh access to the live system...

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Needs review » Fixed

And committed. Let me know if this doesn't fix it for you.

Freso’s picture

Freso commented

Is there a reason to have

if (!trim($pattern)) {
  ...
}
if (!trim($pattern)) {
  ...

? Looks like cruft to me. :)

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

Yes, it's mostly on purpose. Also, as you pointed out separately, I just updated this to put those in a nested form so they are cleaner and slightly faster and fixed this in the hook_nodeapi since we do basically the same test there...

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.