Closed (fixed)
Project:
me aliases
Version:
6.x-2.8
Component:
Miscellaneous
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Mar 2011 at 23:13 UTC
Updated:
9 May 2011 at 02:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Ela commentedAfter upgrading to 2.8 version (even tried 2.x.dev version) user profile pages return "Access denied" for anonymous visitors on profile pages even though permission to view user profiles is given to anonymous users.
...I'm sorry, I could not edit the first post so I fixed the sentence here...
Comment #2
Ela commentedThis also happens on other pages. So far I've noticed it on blog pages http://www.example.com/blogs/USERNAME?page=1 etc returns access denied for anonymous user... Again, switching back to version 2.7 returns page as expected.
Comment #3
lort commentedsame exact thing here.
Comment #4
nohup commentedPlease apply the attached patch. This will be part of the 6.x-2.9 release and should come up in the development snapshot.
Comment #5
Ela commentedThank you for the patch :)
Comment #6
brunorios1 commentedThank you for the patch :) [2]
Comment #7
Mascher commentedThis patch #4 included in new version of me aliases? I have som problem and I use 2.7 version...
Comment #8
nohup commentedpatch #4 is in the dev branch not in the release.
Comment #9
Michsk commentedwow this helped me out. May i suggest releasing (Very) quickly a 2.9, since this is quite a bug.
Comment #10
Anonymous (not verified) commentedI second lasac's post. This problem caused me great headaches until I read through the bug reports here.
Comment #11
trevorleenc commentedyeah, this is quite a bad bug if I say so myself...just spent several hours pulling my hair out trying to figure out what could possibly be wrong with my development site and then I find this...
the latest -dev seems to fix this problem...thanks :)
Comment #12
ledom commentedHeadaches here too.... thanks for the patch. Please release.
Comment #13
gateone commentedNot only that: on our installations, after upgrading von 2.7 to 2.8, if a user wanted to edit Drupal core profiles the fields were returned EMPTY although Data was resent forcing the user to reenter already entered data before he/she could do changes.
Comment #14
brunorios1 commented#13 fixed here: http://drupal.org/node/1102924#comment-4257030
Comment #15
debplatt commentedsubscribe
Comment #17
nohup commented6.x-2.9 released. Thanks for your patience guys.