search

thexerteproject / xerteonlinetoolkits

Xerte Online Toolkits
www.xerte.org.uk
Apache License 2.0
62 stars 61 forks source link

LO not accessible even when access is set to public (develop branch) when Moodle authentication is also used #822

Closed obgeneralao closed 5 months ago

obgeneralao commented 5 years ago

Hi,

The current develop branch makes LO inaccessible even when set to public.

ronm123 commented 5 years ago

You'll have to provide more detail here I can't reproduce this. e.g. I can make LO's public with develop and all works fine.

obgeneralao commented 5 years ago

Hi Ron, I have XOT installed inside moodle. Accessing the LO would just show a white blank page. So, for now I am stucked on master branch which enables my LO to be accessible to anyone when set as public.

In the develop branch, my LO stopped being accessible publicly from the commit 373b677bcdb458fc18689d2478f6092707c66e4b and thereafter.

I was able to reproduce the issue by installing XOT in my local computer. In master branch LO is accessible but in develop branch , LO stopped being accessible publicly from the commit 373b677bcdb458fc18689d2478f6092707c66e4b and thereafter.

ronm123 commented 5 years ago

Ok so yes I can replicate this now. To be clear your original issue just referred to "develop branch makes LO inaccessible even when set to public" with no mention of using Moodle for authentication. Public LOs work fine from develop when using guest or db authentication but at the moment there does seem to be a bug when current develop is used together with Moodle for authentication. We'll update this issue once resolved and were already aware of an issue with the LTI integration when Moodle is used for authentication too which @torinfo is looking at. I suspect the two issues may be related.

obgeneralao commented 5 years ago

Hi,

Is this issue solved with 2d1f1f8?

torinfo commented 5 years ago

No regrettably not, but I will look into this.

ronm123 commented 5 months ago

Reviewing this and I can't replicate e.g. an install with moodle authentication enabled but projects made public work fine. It's obviously an old issue anyway so I suspect fixed long ago.