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.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

IceCreamYou’s picture

Priority: Normal » Critical

I'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.

agentrickard’s picture

Status: Active » Postponed (maintainer needs more info)

Does the role have the 'view mysite' and the 'edit mysite' permission?

agentrickard’s picture

Assigned: Unassigned » agentrickard
Category: support » bug
Status: Postponed (maintainer needs more info) » Active

OK.

%#$#!

kpaul’s picture

Assigned: agentrickard » Unassigned
Category: bug » support
Priority: Critical » Normal

Yes, 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.

kpaul’s picture

Sorry.

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. ;)

agentrickard’s picture

Version: 5.x-3.0rc1 » 5.x-2.18
Status: Active » Needs review
FileSize
1.18 KB

It's ok. Just a little self loathing.

Attached is a patch for 5.x.2.18.

agentrickard’s picture

FileSize
1.18 KB

And a patch for 5.x.3 rc1.

agentrickard’s picture

Note that users must have both the 'view' and 'edit' mysite permissions. Still, this was a sloppy bug.

kpaul’s picture

Great job. Thanks.

agentrickard’s picture

FileSize
1.41 KB

Did it work?

And the 3.0 rc1 patch was malformed. Resending.

agentrickard’s picture

The issue was that I only tested as a user without a MySite page or collection. Sloppy.

kpaul’s picture

I 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

kpaul’s picture

Fixing so fast cancels it out, though, so no biggie. ;)

agentrickard’s picture

Yes, but this is why I'm on point release 18 (soon to be 19). :-)

kpaul’s picture

I can confirm the patch

http://drupal.org/files/issues/mysite18.patch

works...

agentrickard’s picture

OK. 5.x.2.19 rolled.

Waiting for confirmation on 5.x.3.

agentrickard’s picture

Version: 5.x-2.18 » 5.x-3.0rc1

Filing against 5.x.3 rc1, since 5.x.2.19 is the fix.

IceCreamYou’s picture

I 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.

agentrickard’s picture

Thanks, but it was a bad patch last night that got us into this mess.

Has anyone confirmed on 5.x.3 yet?

WISEOZ’s picture

Hello! 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!

IceCreamYou’s picture

Status: Needs review » Fixed

Since it's been confirmed that both major branches work now, I'm going to mark this fixed.

agentrickard’s picture

Status: Fixed » Reviewed & tested by the community

Please don't mark it fixed. Mark RTBC. I haven't committed the patch to rc3 yet!

agentrickard’s picture

Status: Reviewed & tested by the community » Fixed

Looks like I already committed this :-)

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

SamRose’s picture

Version: 5.x-3.0rc1 » 5.x-3.3

This 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