Bulk Update + "Do Nothing" Should Still create aliases for unaliased items
nicholasThompson - July 20, 2008 - 20:16
| Project: | Pathauto |
| Version: | 6.x-2.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
If you set the update action to "Do Nothing", it appears that bulk updates dont actually do anything.
Maybe its worth displaying some kind of message saying that "x" aliases were skipped due to a setting?
I only ask because I just spent half an hour trying to debug the module expecting a bug - turned out I'd just configured it wrong. :)
Cheers for a great module :)
#1
As long as they have Verbose on this idea seems reasonable to me.
#2
Bumping version - given that we're in a string freeze for 5.x-2.x and 6.x-1.x and given that this is a feature it should just be in 6.x-2.x-dev.
#3
The other question is that apparently "Do nothing" used to actually mean "Do nothing unless it has no alias and in that case do something"
So...I guess we should bring that back since a lot of people liked it.
#4
The thread indicates that it's never been reverted to "Do nothing unless it has no alias and in that case do something". Is this correct?
I agree that this change or a message would be beneficial.
#5
I agree with #3 that it should be changed back to mean "...unless it has no alias and in that case do something".
Subscribing.
#6
I agree this button should either do something, or there should be a fifth option added that DOES do something.
This is especially counter-intuitive when the checkbox for bulk updates reads "Generate aliases for all existing terms which do not already have aliases.", making it seem like marking the checkbox will cause some action to occur.