Skip to content

[willow] Legacy Libraries DEPR: Dead code cleanup #39371

Open

Description

@kdmccormick

Note

This issue and the linked plan were drafted by Claude Fable 5.2 under direction from @kdmccormick, who has not yet reviewed them in detail.

Part of the Legacy Content Libraries (V1) deprecation, under the epic openedx/frontend-app-authoring#2044.

Why

The post-Verawood removal step of the deprecation was only partly carried out. An audit of current master found that:

  • The legacy library view/edit page is still served at /library/<key>, and POST /library/ still creates a legacy library.
  • The legacy Randomized Content Block (library_content) still has its whole authoring side: the library picker, the problem-type filter, and "Update now".
  • Several Studio APIs still accept library-v1: keys, and a number of toggles, settings and Studio Home API fields exist only for legacy library authoring.

This issue tracks removing that code. It follows on from #38056 and #38058.

What stays until after the Xylon cutoff

  • Storage of legacy libraries in the modulestore.
  • Learner-side rendering of existing Randomized Content Blocks, and their remaining settings.
  • Migration to Content Libraries in every form (the Studio workflow, the REST API, Django admin, management commands), including "Update reference" on a Randomized Content Block.
  • The legacy libraries listing API, and OLX export of a legacy library.

Plan

Full plan: https://gist.github.com/kdmccormick/6f37a6f32fba1498fc8cd5b71d5cde67

Audit it is based on: https://gist.github.com/kdmccormick/57f0cc18f6f151ee6718331ba73e55b9 (see 05-legacy-libraries.md)

The platform PRs are stacked in the order shown.

# Repo Removes Status
1 openedx-platform The legacy library page, library_handler, the listing's per-library url field, and the JavaScript only that page loaded PR Needed
2 openedx-platform Preview plumbing that only the library page used: paging, placeholders, LibraryRoot's Studio rendering PR Needed
3 openedx-platform Legacy-library support in the remaining Studio write paths: /xblock/ create and duplicate, course_team, course import routes and tasks, the import_content_library command, git export of a legacy library PR Needed
4 openedx-platform The Randomized Content Block's authoring side, leaving rendering and migration. Adds a validation message for unsupported blocks and a new class docstring PR Needed
5 openedx-platform LegacyLibraryToolsService and its Celery tasks, replaced by one helper that copies children on duplicate, paste and course import PR Needed
6 openedx-platform Unread legacy-library fields in the Studio Home API, and the toggles and settings tied to legacy libraries PR Needed
A frontend-app-authoring Legacy library leftovers: unused fields, legacy branches in the block editors, an unrendered alert, unused Redux state PR Needed

Behaviour changes to announce

  • GET and POST /library/... in Studio return 404. Legacy libraries can no longer be created through Studio.
  • course_team, course import and /xblock/ create and duplicate stop accepting library-v1: keys. The import_content_library command is removed, and git_export no longer accepts a legacy library key.
  • The Randomized Content Block's library and problem-type settings become read-only, and "Update now" is removed. In the component picker it is named "Legacy Randomized Content Block (Deprecated)". A block with no source library shows an error telling the author to use a Problem Bank instead.
  • GET /api/contentstore/v1/home loses libraries, libraries_enabled, libraries_v1_enabled, show_new_library_button and split_studio_home.
  • The waffle flag contentstore.new_studio_mfe.disable_legacy_libraries and the settings DISABLE_LIBRARY_CREATION, ENABLE_LIBRARY_INDEX and LIBRARY_BLOCK_TYPES are removed. Legacy libraries that can be migrated are always listed.

Open points

Activity

  1. self-assigned this
    on Nov 12, 2026
  2. kdmccormick commented on Nov 12, 2026

    @kdmccormick
    MemberAuthor
  3. self-assigned this
    on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions