Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have the user/access set-up to give permissions...
However, when a user tries to view their own 'mysite' it shows Access Denied. They *can* edit it, though, and I can see other users mysite fine. Even as user1, though, I get access denied when looking at my own.
This happened with 5.2.18 as well...
I'm sure I'm forgetting something simple, but I can't for the life of me figure out what it is.
Any ideas on where to look?
Thanks.
Comment | File | Size | Author |
---|---|---|---|
#10 | mysite30.patch | 1.41 KB | agentrickard |
#7 | mysite30.patch | 1.18 KB | agentrickard |
#6 | mysite18.patch | 1.18 KB | agentrickard |
Comments
Comment #1
IceCreamYou CreditAttribution: IceCreamYou commentedI'm having this problem too. It's happened since I upgraded to 2.18 from 2.17. I intended to start using MySite as my site's homepage today, which makes it really alarming that this is happening!
I'm downgrading to 2.17 until this is fixed.
Comment #2
agentrickardDoes the role have the 'view mysite' and the 'edit mysite' permission?
Comment #3
agentrickardOK.
%#$#!
Comment #4
kpaul CreditAttribution: kpaul commentedYes, has both permissions. It happens for user1 too, though...
I tried going to RC3 of the 3.x line, but it happens there too.
I don't have TAC or TAClite or anything like that on this site either.
Thanks.
Comment #5
kpaul CreditAttribution: kpaul commentedSorry.
Let me take a moment to thank you for all your hard work - and for Morris letting you give it back to the Drupal community. ;)
Comment #6
agentrickardIt's ok. Just a little self loathing.
Attached is a patch for 5.x.2.18.
Comment #7
agentrickardAnd a patch for 5.x.3 rc1.
Comment #8
agentrickardNote that users must have both the 'view' and 'edit' mysite permissions. Still, this was a sloppy bug.
Comment #9
kpaul CreditAttribution: kpaul commentedGreat job. Thanks.
Comment #10
agentrickardDid it work?
And the 3.0 rc1 patch was malformed. Resending.
Comment #11
agentrickardThe issue was that I only tested as a user without a MySite page or collection. Sloppy.
Comment #12
kpaul CreditAttribution: kpaul commentedI haven't tried yet. I just rolled it out on this site, actually, so went back to 2.17 ... I'll try to patch, though, and report back...
-kpaul
Comment #13
kpaul CreditAttribution: kpaul commentedFixing so fast cancels it out, though, so no biggie. ;)
Comment #14
agentrickardYes, but this is why I'm on point release 18 (soon to be 19). :-)
Comment #15
kpaul CreditAttribution: kpaul commentedI can confirm the patch
http://drupal.org/files/issues/mysite18.patch
works...
Comment #16
agentrickardOK. 5.x.2.19 rolled.
Waiting for confirmation on 5.x.3.
Comment #17
agentrickardFiling against 5.x.3 rc1, since 5.x.2.19 is the fix.
Comment #18
IceCreamYou CreditAttribution: IceCreamYou commentedI am again impressed with how quickly you fix these problems, agentrickard. Bravo! And thanks! It's a great module and I appreciate the work that's gone into it.
Comment #19
agentrickardThanks, but it was a bad patch last night that got us into this mess.
Has anyone confirmed on 5.x.3 yet?
Comment #20
WISEOZ CreditAttribution: WISEOZ commentedHello! I've just confirmed the patch works for 5.x-3.0rc1. I'll continue my testing on 5.x-3.0rc1 and report any additional findings under a separate issue. Thanks!
Oh and, I like the new settings icons!
Comment #21
IceCreamYou CreditAttribution: IceCreamYou commentedSince it's been confirmed that both major branches work now, I'm going to mark this fixed.
Comment #22
agentrickardPlease don't mark it fixed. Mark RTBC. I haven't committed the patch to rc3 yet!
Comment #23
agentrickardLooks like I already committed this :-)
Comment #24
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #25
SamRose CreditAttribution: SamRose commentedThis problem has cropped up for me on one particular develepment copy of a site. The production copy works fine, but dev copy gives a 403. the patch above is of course part of 5.x-3.3 release. Any advice you might be able to give about what would make /mysite lead to a 403 forbidden greatly appreciated. Incedentally, if you visit /mysite/User+Name mysite pages are accessable, just not the redirect from /mysite based on $user