Posted by Dave Reid on February 13, 2010 at 4:32am
7 followers
| Project: | Pathauto |
| Version: | 7.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Dave Reid |
| Status: | closed (duplicate) |
Issue Summary
I'd like to split the bulk-updating code w/ the Batch API patch into a new sub-module or project called 'Pathauto Bulk Update'. Reasons for this:
1. Pathauto stays lean and mean and does what it does best (transfer updating and bulk-deleting to new module code)
2. Helps ease transition to D7 since we would most not likely bring these features into core
3. Bulk updating can focus on its own feature set and adding new cool things (updating for all languages, etc).
So, should we create a separate project or make it a sub-module included in Pathauto? I'm prepared to help maintain this.
Comments
#1
Could you please draw more of a line between what the updated PathAuto and the new PathAuto Bulk modules would do, where the existing functionality would go? Thanks.
#2
The functionality that would be moved from Pathauto to the new module is:
1. The 'Bulk generate aliases for [entity] that are not aliased' features on the pathauto settings page would be moved to its own batch API 'Update' page in the sub-module.
2. The 'Delete aliases' page would also be moved to the sub-module.
#3
For context, about 50 of the current pathauto open issues deal with the bulk update or deletes. I started tagging the major ones with 'bulk' but there are a lot.
#4
I posted a partial module for that long ago, which could serve as a starting point. http://drupal.org/node/201151#comment-1952406
#5
I'll start working on this in my sandbox for now.
#6
I say go for it. Since the functionality in question isn't needed most of the time, having the option to disable it would be nice. (I like modules that disappear when I don't need them.)
As for how to treat the split, if you can make Pathauto Bulk Update independent of the version of Pathauto then make it a seperate project. Otherwise you may as well keep it as a sub-module.
#7
Sorry about that, bad timing for a post.
#8
#9
errr, you started to work on this in your sandbox? Why that?
I'd take the code from #201151: Use batch API to perform path alias bulk updates and turn it into a module. Done.
Probably resolves a lot of bulk update issues in the queue, because I already fixed a couple of WTFs in that patch.
Bulk update = Batch API.
Nothing more, nothing less. I still disagree with a separate module though.
#10
FWIW, I like this idea.
#11
I think it's a good compromise. Pathauto should expose operations for VBO and we should also provide this module.
#12
Moving to 7.x-1.x and postponed.
#13
Fail.
Anyway, here's an updated version of the current batch module.
#14
Fail? I get that you disagree with the way that this particular issue was handled, but do you think you could be more constructive?
Or in other words: constructive cooperation fail.
#15
I think pushing it to D7 is a failure to fix the problem that exists. I think postponing is the wrong decision. This is an active problem in D6 that needs attention.
Apologies for my curtness earlier.
#16
@agentrickard: The current plan is outlined in #201151-50: Use batch API to perform path alias bulk updates, also (or even primarily) targeting 6.x-2.x
#17
Being fixed shortly in #201151: Use batch API to perform path alias bulk updates which will be backported to 6.x-2.x.
#18
Crosslinking for searchers (I know it's an old dead issue, but this is still the best search result for anyone looking for a related workaround). Also as the fix in 6.x-2.x hasn't been flagged stable yet.
Using Views Bulk Operations to perform bulk pathauto updates can be a powerful solution.