Closed (fixed)
Project:
Pathauto
Version:
5.x-1.2
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Jun 2007 at 14:13 UTC
Updated:
12 Nov 2007 at 22:41 UTC
Submitting the Pathauto admin page with "bulk update node paths" checked results in an empty page. Returning to any (working) Drupal page then produces the "The configuration options have been saved." message so I guess it's getting that far and then failing.
Hmm ... I'm afraid that's about all I can say, it's as simple as that - not working. Is it possible that localization would mess up the process? It's submitting to /admin/settings/pathauto instead of admin/settings/pathauto ... but that should still fire the bulk update procedure, right? It certainly saves the submitted settings correctly.
Comments
Comment #1
gregglesdoes "returns nothing" mean a totally blank page, like a "white screen of death" ?
If so, please look in your web server's error log for more information.
Comment #2
kingandyYep, the browser gets a completely blank page, no theme, no <html>, no nothing.
Looking in the error log, I think these two lines appeared when I fired the bulk update:
The 'Unserialize()' error has been popping up for a while now, which I suspect is why we've turned off error reporting - it doesn't appear to affect site operation. It doesn't seem likely that would cause a function redeclaration error. The question, I suppose, becomes whether pathauto is causing common.inc to try to redeclare insert_content, or if that's happening - and killing the page - before it even gets to pathauto. Any ideas?
Comment #3
gregglesWell, this search comes up with nothing. I'm not sure where it comes from.
I guess can you see if there are any other scenarios where your site has that problem? Unless some more folks find this I don't see it as a deifnite pathauto bug yet since I've never encountered it.
Comment #4
gregglesSeems to be similar to http://drupal.org/node/128458
Perhaps combining efforts over there can help find the cause of this bug.
Comment #5
gregglesBased on the debugging in that other issue this seems to come from a really long running query.
This was "fixed" in the 5.x-2.x version of pathauto by making the bulk updates more scalable. If you can please help test out that version.
Comment #6
kingandyI'd completely forgotten about this bug ... I think in the end we realised it wasn't just bulk updates, it was any time the Pathauto module tried to create a path.
I believe it turned out to be because the Token module wasn't enabled (we upgraded to a version of Pathauto that required Token, and since Pathauto was already enabled when we upgraded it didn't automatically enable Token).
Whatever the case, I'm afraid it's behaving itself now, sorry :)
Comment #7
gregglesGood to hear that you finally got it working.
Comment #8
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.