Hi,

when building new sites, the final path aliasing scheme often can't be pre-coordinated; thus for some content types aliases are generated that have to be removed at a later stage. In bulk operations, the current user interface only allows to replace all path aliases. I'd like to have more selective control and be able to only re-generate path aliases for a certain node type.

Thanks & greetings, -asb

Comments

asb’s picture

Title: Allow to update/delete path aliases selectively » Bulk generate path aliases for large sites
Version: 7.x-1.x-dev » 6.x-1.1
Category: feature » support

Hi,

I'm trying to add path aliases through the "path auto" module for a D6 site with ~29.000 nodes. As far as I understand the pathauto UI, the only setting to bulk generate path aliases is located at ./admin/build/path/pathauto. There I can set a value like "50" or "100" to bulk edit path aliases which are generated when clicking on "Save configuration".

Setting this to a higher value (like "1000"), pathauto will time out during the operation, a setting like "100" requires me to click 290 times on the "Save configuration" button and hope for the module not to time out; that's half a day of work for a brain amputated monkey and becomes quite unmanageable on really large sites.

As far as I can see, pathauto neither utilizes Cron nor D6's batch API to bulk generate path aliases. Would it be possible to add this functionality to the module, or have I misunderstood something in the UI?

Thanks & greetings, -asb

greggles’s picture

Thanks for letting me know about this concern. I believe it is addressed in the Pathauto documentation here on drupal.org.

Specifically, please see the sub-page for Bulk updating which includes solutions for large sites.

greggles’s picture

Status: Active » Fixed
asb’s picture

Hi Greg,

thank you for the pointer; I already tried that script, which is tagged for Drupal 5.x only, and got the same results as comment #1599666: nothing (= PHP script returns immediately; nothing happens; no path aliases are generated).

Since you changed the category of this issue from "feature request" to "support request": Can we assume that you would at least require a patch to consider adding support for the batch API or some other built-in solution?

Thanks & greetings, -asb

greggles’s picture

Component: User interface » Documentation
Status: Fixed » Active

In comment #1 you changed it to support request ;)

I changed it from active to fixed (I thought the docs were accurate, but I guess not). I don't consider batch API as a good solution compared to command line code. The views bulk operations module can update node aliases via the batch API.

If I were to spend time on this, it would be to update the documentation so that it worked for 6.x-1.x (which is not that much different from 5.x-2.x).

mvc’s picture

Status: Active » Fixed

I've updated the documentation with notes for Drupal 6.

http://drupal.org/node/236304

Status: Fixed » Closed (fixed)

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