Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nutmeg regression in "Course Visibility In Catalog" == "none" behavior #195

Closed
throwaway-a opened this issue Aug 8, 2022 · 2 comments
Closed
Labels
bug Report of or fix for something that isn't working as intended
Milestone

Comments

@throwaway-a
Copy link

throwaway-a commented Aug 8, 2022

If "Course Visibility In Catalog" is set to "none", students who have already enrolled in a course can no longer access the class.

Citations of people who've run into this here and here.

I was previously on Lilac, and students who were enrolled in closed beta testing classes could continue to access the content even after visibility was set to "none". But now it errors out in a very difficult to debug fashion (until I saw Regis saying it needs to be debugging in the browser rather than logs.)

The current workaround is to set the visibility to "about", so that it won't show up on the catalog. But this is undesirable because it will still be accessible via course About page URLs that were previously posted.

Based on the Firefox -> Inspect -> Console output, it seems like this may have something to do with MFE accessing "apps." instead of just , and that having some cross-origin conflict?

image

@BbrSofiane BbrSofiane added this to the Nutmeg.3 milestone Aug 13, 2022
@arbrandes arbrandes added the bug Report of or fix for something that isn't working as intended label Dec 6, 2022
@arbrandes
Copy link

Closing as stale.

@arbrandes
Copy link

arbrandes commented Dec 12, 2022

Related forum discussion where this was brought up:

https://discuss.openedx.org/t/how-to-programmatically-set-a-course-advanced-fields/8901

Basically, we'll want to reopen this if the 3 items listed in this comment are satisfied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Report of or fix for something that isn't working as intended
Development

No branches or pull requests

3 participants