Conversation
CCX course_published signals are dispatched in the LMS process but the Studio-side handler that writes CourseOutlineData (cms.djangoapps.contentstore.signals.handlers.listen_for_course_publish) runs only in the CMS process, so CCX courses never had outlines and the learning_sequences API raised CourseOutlineData.DoesNotExist when the LMS Outline view tried to render them. Per ADR 0011 we cannot move outline generation into the LMS because it would require modulestore access. Instead, derive the CCX outline from the parent course's already-published CourseOutlineData, which lives in learning_sequences and is safe to read from LMS. The new replace_course_outline_for_ccx helper clones the parent outline into the CCX namespace using map_into_course, and a new LMS Celery task update_ccx_course_outline is wired to SignalHandler.course_published for CCXLocator keys. CCX overrides (start, due, visible_to_staff_only) are not baked into CourseOutlineData so cloning preserves the contract. Closes #37365
openedx-webhooks
added
the
open-source-contribution
|
Thanks for the pull request, @kingoftech-v01! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Submit a signed contributor agreement (CLA)
If you've signed an agreement in the past, you may need to re-sign. Once you've signed the CLA, please allow 1 business day for it to be processed. 🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
3 participants
Closed.