We have a bunch of content that needs to be re-aliased. Could we have a checkbox to say, create new aliases not already created on cron run and still have that same "max" field so that cron won't be overburdened either. To me it's easier to keep running cron instead of having to refresh the admin page over and over.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Would it be worth it to have core patch that adds a {url_alias}.created or changed timestamp that stores when the URL alias was created or last changed. That way we would run a left join on node and check if any url aliases were last changed before the automatic node alias settings were changed.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Closed (duplicate)

The main page for these improvements is #212084: perform bulk updates during cron and/or via the batch API though there is documentation about alternate possible techniques at http://drupal.org/node/236304

JCB’s picture

JCB commented

I had some issues updating term aliases as I have vocabulary with 50,000 terms.
This lead to internal server errors.

I can confirm that updating URL alias is working with views bulk operations (VBO).

I installed the latest dev version which supplied the required options to make this possible.
6.x-2.x-dev tar.gz (42.96 KB) | zip (47.99 KB) 2012-Sep-28 Notes