26 October 2010, 8:31

Hello,

Hope someone can help us with this.

I set the view access to Secret URL and i saved. I sent the URL by email to someone but when that person who is not a Mahara user pastes the link in a browser, it redirects them to the log in page. &login is added at the end of the URL. If you paste the link again in the same browser, the view is displayed.

Anyone has any idea why &login is being added to the Secret URL and how we can prevent that ??

Regards,

Lama

26 October 2010, 16:58

Hi Lama,

It's a bug:

https://bugs.launchpad.net/mahara/+bug/661613  (Already fixed for the next release)

03 November 2010, 2:33

Hey Richard,

Thank you for your reply. Just to double check, we are now on Mahara 1.3.

Is there a new release coming up higher than 1.3? if yes, when do you think it will be out?

Thanks a lot

Lama

03 November 2010, 16:54

Hi Lama,

Mahara 1.3.2 is already out and we're planning on releasing 1.3.3 next week.

Cheers,

Francois

03 November 2010, 5:50

Hello Richard,

The bug link you provided doesnt open it says:

Oops!

Sorry, something just went wrong in Launchpad.

I just need to find how to apply the fix on 1.3.1 which we have

thnx,

amer

03 November 2010, 5:57

Hi Amer,

I'm afraid that Launchpad is a little out of our hands - they seem to be experiencing some technical difficulties so I can't get to the bug information at present.

I think that this is the relevant patch in the git repository: http://gitorious.org/mahara/mahara/commit/1c807f3f424193c622dff67b5bae32986ecca670

If you apply this patch, then this should address your issue. I can't see any other patches relating to this bug, but Richard would be able to confirm.

Andrew

03 November 2010, 17:00

Yep, launchpad seems to be back in business, and that patch Andrew linked to is the right one.

The fix is not in 1.3.2 but it will be in 1.3.3, so if you can wait, just upgrade next week when 1.3.3 is available.

21 January 2011, 16:17

I just noticed this bug in my version 1.3.3...secret URL demands a login

Did the fix not make it into 1.3.3?

21 January 2011, 18:57

I'm having the same problem and am on 1.3.3.  Thanks