Currently our Bulk update only works for un-aliased entities. Let's add a checkbox with something like 'Also update objects that already have URL aliases. If their URL aliases have changed, then the update action applies."

Comments

Dave Reid’s picture

Component: Code » Bulk generation
klonos’s picture

Dave Reid’s picture

Status: Active » Closed (won't fix)

Greggles pointed out, this is what VBO and our 'Update URL alias' action is for.

klonos’s picture

Status: Closed (won't fix) » Active

...just a last try to persuade you to implement this: I still find myself going first in the bulk update page in order to re-alias already existing URLs, then searching my issues in d.o for this issue, then seeing the reply from Dave, then installing & enabling VBO if not already installed, then updating the aliases from the content page.

Point is that users not aware of VBO and the "Update aliases" option available in the drop-down or this issue here to begin with, they will keep looking in the aliases admin pages to do this and most likely go through the first-delete-then-update procedure.

Having the tab still say "Bulk update" doesn't help either. Seriously now, if updating is not possible through that tab, then it should be "Bulk generate": #1001206: Bulk update or Bulk generate? - Change the green, success-looking-like message to a yellow warning

Dave Reid’s picture

Going to rename 'Bulk update' to 'Bulk generate' for now.

Dave Reid’s picture

Version: 7.x-1.x-dev » 6.x-2.x-dev
Status: Active » Patch (to be ported)

Committed change in http://drupalcode.org/project/pathauto.git/commit/8b934e4, needs to backport to 6.x-2.x for now, and then set back to 7.x-1.x to re-evaluate allowing updates of existing items.

klonos’s picture

Thanx Dave!

ryan.gibson’s picture

Heh, I finally made it to this thread with the same confusion. So, just to be clear, this needs a D6 port yea but doesn't actually exist?

Dave Reid’s picture

Version: 6.x-2.x-dev » 7.x-1.x-dev
Issue summary: View changes
Status: Patch (to be ported) » Fixed

Status: Fixed » Closed (fixed)

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