As the first user (user 1) I can access all features and when I go to "My Account" (hxxp://www.domainname.com/user/1 ) I see my account page.
However, a new user registers, and upon loging in for the first time, specifying a password, they then get "404 Error - File not found!" and it's a server error page, not a drupal error page. They are actual logged in, can view and create pages but can't access their "My Account" page. If the user name is 'Test', then the my account link is hxxp://www.domainname.com/users/test but even if I try .../user/2 (or whatever their user number is) , the url is rewritten and I get "404 Error - File not found!".
The "URL alias" was set for user/2 as users/test, when I changed the alias to user/2 the user can now see their account page.
It was definitely the Pathauto module. I disabled it, created a new user and could access the account page fine.
The default setting in Pathauto for Pattern for user account page paths is 'users/[user-raw]' . Why this shouldn't work anyway is a mystery to me. I would assume setting the default to 'user/[uid]' will work, but less URL friendly :P
Sack
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | WellesleyCollegeBeta-working--2008-07-11T18-49-00.sql_.gz | 7.06 KB | dean.p |
Comments
Comment #1
gregglesPlease attach an export of the url_alias table and the system table.
Comment #2
dean.p commentedThere you go, although this is an export after I've fixed the URL alias
Comment #3
sdgreene commentedI encountered a similar problem. In Firefox, I noticed <?> blocks after each segment in newly generated aliases after doing an upgrade to a newer version of pathauto. After clicking one of the aliases, I noticed the 404 and the status bar had had %00 where the <?> glyphs had been. I figured a null character had crept in somewhere, so after some testing I realized it wasn't Firefox doing it. I starting scanning the code and finally came across this block in pathauto.inc starting at line 182:
After commenting out the if clause and the brackets, everything worked fine and I regenerated all my aliases and no <?>'s or %00 had cropped up. I'm pretty sure my host has mb_string, because the function didn't produce any errors, just odd output. I do know the php version is rather old, 4.3x or 4.4x.
So, here's the snippet with edits:
Hope this helps save some people the gut wrenching half-hour it took me to find out what had happened.
-Seth
Comment #4
damienmckennaAnother user affected by this bug, specifically:
warning: mb_eregi_replace() expects parameter 3 to be string, array given in
[sitehomedir]/sites/all/modules/pathauto/pathauto.inc on
line 182.
Yes, they have mbstring enabled, specifically:
Multibyte Support: enabled
Multibyte string engine: libmbfl
Multibyte (japanese) regex support: enabled
Multibyte regex (oniguruma) version: 4.4.4
Multibyte regex (oniguruma) backtrack check: On
Comment #5
greggles@DamienMcKenna - it would be useful if you could figure out what the array is in mb_eregi_replace when this happens.
Something like
drupal_set_message('<pre>'. print_r($output, TRUE) .'</pre>');right before the call to mb_eregi_replace and then paste the output from that into this issue.Comment #6
greggles2+ weeks without specific details on how to repeat the bug. I imagine it is OS/PHP version/other module specific though I'm not entirely sure.
If this were a bug in the module on it's own then we'd have hundreds of reports of it... :/
Comment #7
Anonymous (not verified) commentedI can confirm this bug. I had (and still have) it on several D5 installations on several servers. All servers are Debian Etch (AMD64 versions) systems with all updates applied. Last occasion: After migrating a customer's development system from his ex-hoster to one of my machines last night.
If you need any specific details, logs, whatever, don't hesitate to ask.
For the time being I'll go without pathauto for users.
Comment #8
Anonymous (not verified) commentedComment #9
gregglesI believe this is a duplicate of #341807: My Account/URL alias for user account returns 404.
At least that has a decent solution to the problem which none of the other similar issues have.
Comment #10
Anonymous (not verified) commentedThank you for pointing me there. Haven't come across that entry and I am indeed using ISPC on my root servers...