Versions Compared

Old Version 35

changes.mady.by.user Peter Pinch

Saved on

compared with

New Version 36

changes.mady.by.user Kyle McCormick

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Feature Changes

  • The Learning MFE is slated to be the default experience courseware experience for Lilac Micro-Frontend (MFE) may be installed for opt-in usage (Kyle McCormick).

    • Both course-run-level and global opt-out will be available via Waffle flag, falling back to the Legacy courseware frontend.

    • This necessitates that the Learning MFE will work out-of-the-box in Lilac. Need to connect more with BTR on this.

    • We expect all this to be true for the Outlines and Dates pages as well (Michael Terry (Deactivated) , Jason Myatt (Deactivated) )

      • Note: The Dates page will be available to all enrolled learners. Previously, it was gated on the Relative Dates Flag.

    • We expect that this is the last named release to support Legacy courseware frontendBy default, the course experience is still run in the legacy LMS templated frontend, so this should not affect the out-of-the-box Lilac experience.

    • If the Learning MFE is installed using the MFE Deployer Ansible role (I lack the details on what entails) then certain features can be opted in to the Micro-Frontend, as noted below.

    • These Waffle flags can be toggled on (globally, per-user, or per-course) to switch certain features over the Learning MFE:

      • courseware.courseware_mfe : Enable to host courseware (ie, the learning sequence experience) in the MFE.

      • courseware.microfrontend_course_team_preview : Enable to show global and course-level staff members the ability to preview courseware in the MFE. Does not affect learners.

      • course_home.course_home_mfe : Enable in conjunction with one or more of the following (contact Michael Terry (Deactivated) or Jason Myatt (Deactivated) for details):

        • course_home.course_home_mfe_dates_tab : Display the “Dates” course tab in the MFE.

        • course_home.course_home_mfe_outline_tab : Display the course outline (the target of the “Course” course tab) in the MFE.

        • course_home.course_home_mfe_progress_tab: Display the “Progress” course tab in the MFE.

  • Switched from Elasticsearch 1 to Elasticsearch 7 across Open edX. This may require some syntax changes for custom scripts that used search APIs. (Michael Terry (Deactivated) )

    • Please change queries that used __not to __exclude

    • Please properly URL-encode any plus signs in query URLs (like in course run key parameters) to %2b. Our Elasticsearch 7 implementation is more strict in that regard.

    • Please change queries against course-discovery that used pacing to pacing_type

  • Xblock URL token signing can now be migrated to use a new multi-key mechanism rather than being tied to SECRET_KEY. It is recommended that you perform this migration, as it permits easier rotation of SECRET_KEY. (Tim McCormack)

  • Various bug fixes and updates around course certificate generation (crice (Deactivated))

    • In an effort to be more inclusive, code referencing the course CertificateWhitelist model is being updated to instead refer to a Certificate Allowlist. The model itself has not yet been renamed.

    • Temporary CourseWaffleFlag added to control access to updated behavior of the CertificateWhitelist (aka Certificate Allowlist)

    • Temporary CourseWaffleFlag added to control access to updated behavior of the course certificates

    • The management command named create_fake_cert has been removed. The Certificate Allowlist should be used in its place.

    • The management command named gen_cert_report has been removed. To view the status of generated course certificates, query the certificates_generatedcertificate database table.

    • A user can no longer be added to both the Certificate Allowlist (meaning the user should be granted certificate) and the Certificate Invalidation list (meaning the user should not be granted a certificate) for the same course run.

    • Removal of the allow_certificate field on the UserProfile model has begun (https://openedx.atlassian.net/browse/DEPR-140)

  • Added a new export-course-metadata-to-storage feature. In order to use it set COURSE_METADATA_EXPORT_BUCKET and COURSE_METADATA_EXPORT_STORAGE. Useful for external services you might have that want to scrape course data.' (Matthew Piatetsky (Deactivated))

  • In common.djangoapps.student.models, the save parameter is deprecated for functions anonymous_id_for_user and unique_id_for_user, and these functions will always save generated IDs to the database. This allows future decoupling of ID generation from SECRET_KEY. Including the parameter will result in a DeprecationWarning; after Lilac we plan to remove the parameter (which will be a separate breaking change – DEPR-148). (Tim McCormack)

...