The problem: If Drupal is running in a shared environment with limited resources and pathauto is installed on an existing site with thousands of existing nodes you may run out of allowed server resources when you choose to bulk update paths. I had experienced this on a shared server. The script exited with Allowed memory size of 15728640 bytes exhausted (tried to allocate 10240 bytes). Conclusion: bulk update paths is a very resources intensive process.

Feature request: I think that a cron scheduled bulk update paths should be considered instead of the current bulk update method. Something similar to the scheduled indexing of the site needed for search.

Comments

claudiu.cristea’s picture

claudiu.cristea
Primary language Romanian
Location Arad 🇷🇴
commented

Ohhh! Sorry! It's related/same with http://drupal.org/node/67665

greggles’s picture

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

Yes, it is a duplicate of that.

There was another issue which might be more directly related: http://drupal.org/node/123186 I just committed that fix to the 5-1 version, so it will be in dev versions and in a 1.2 whenever I release that.

Also, you said this was in "HEAD" which I hope is not the case. I don't maintain head. So, I assume/hope that was an accident...