88c7cd7bf3
* feat!: Remove all trivial mentions of PREVIEW_LMS_BASE There are a few more mentions but these are all the ones that don't need major further followup. BREAKING CHANGE: The learning MFE now supports preview functionality natively and it is no longer necessary to use a different domain on the LMS to render a preview of course content. See https://github.com/openedx/frontend-app-learning/issues/1455 for more details. * feat: Drop the `in_preview_mode` function. Since we're no longer using a separate domain, that check always returned false. Remove it and update any places/tests where it is used. * feat: Drop courseware_mfe_is_active function. With the removal of the preview check this function is also a no-op now so drop calls to it and update the places where it is called to not change other behavior. * feat!: Drop redirect to preview from the legacy courseware index. The CoursewareIndex view is going to be removed eventually but for now we're focusing on removing the PREVIEW_LMS_BASE setting. With this change, if someone tries to load the legacy courseware URL from the preview domain it will no longer redirect them to the MFE preview. This is not a problem that will occur for users coming from existing studio links because those links have already been updated to go directly to the new urls. The only way this path could execute is if someone goes directly to the old Preview URL that they saved off platform somewhere. eg. If they bookmarked it for some reason. BREAKING CHANGE: Saved links (including bookmarks) to the legacy preview URLs will no longer redirect to the MFE preview URLs. * test: Drop the set_preview_mode test helper. This test helper was setting the preview mode for tests by changing the hostname that was set while tests were running. This was mostly not being used to test preview but to run a bunch of legacy courseware tests while defaulting to the new learning MFE for the courseware. This commit updates various tests in the `courseware` app to not rely on the fact that we're in preview to test legacy courseware behavior and instead directly patches either the `_redirect_to_learning_mfe` function or uses the `_get_legacy_courseware_url` or both to be able to have the tests continue to test the legacy coursewary. This will hopefully make the tests more accuarte even though hopefully we'll just be removing many of them soon as a part of the legacy courseware cleanup. We're just doing the preview removal separately to reduce the number of things that are changing at once. * test: Drop the `_get_urls_function` With the other recent cleanup, this function is no longer being referenced by anything so we can just drop it. * test: Test student access to unpublihsed content. Ensure that students can't get access to unpublished content.
Status: Maintenance Responsibilities ================ The Course Experience directory contains a Django application that provides the Course Home page (or course landing page), and various resources in support of the landing experience. Direction: Deprecate ==================== This will be replaced eventually by new UI in the form of Microfrontends. New functionality should not be added here. Glossary ======== More Documentation ================== The course experience consists of a number of views: 1. **Course Home** The course home page is the landing page for the course. It presents the learner with information necessary to understand the purpose of the course, its content, and its milestones. It includes a "Course Tools" section that provides links to other tools associated with the course. For example, it includes tools such as reviews, updates and bookmarks. 2. **Welcome Message** The welcome message is a fragment view which is typically shown on the course home page. It provides the user with a description of the course and helps them to understand its requirements. 3. **Course Outline** The course outline is a fragment view which shows an outline of the content of the course. 4. **Course Dates** The course dates fragment is a view which shows users important dates for the course, such as the start and end dates. 5. **Course Sock** The course sock is a fragment view which is typically shown just above the footer of course pages (hence the name). The default implementation presents the users with a message encouraging them to purchase a verified certificate. 6. **Course Updates** The course updates page shows the user all of the course team's updates in a scrolling list. The updates page is also provided as a course tool. A number of the features in the course experience are controlled via Waffle flags. For documentation, see `Waffle flag definitions`_. .. _Waffle flag definitions: https://github.com/openedx/edx-platform/blob/master/openedx/features/course_experience/__init__.py