XML Courses get put back into the course overviews table even though they have been retired
Description
When the XML courses got retired we removed them from the course_overviews_courseoverview table. The understanding was that they would not get put back in unless an editing trigger happened which populated the table. However it looks like something else is populating this table with them even though no modulestore can serve them. The code should be updated to not add a course to the course_overviews_courseoverview table unless it can be found in one of the modulestores.
can you please look at this ASAP. Students are seeing courses on their dashboard that give them a 404 when they try to go to them.
Steps to Reproduce
Current Behavior
Expected Behavior
Reason for Variance
Release Notes
User Impact Summary
Activity
XML courses are usually on disk, the way we remove them is to remove them from disk and remove them form the MixedModulestore list of XML courses.
, what does mean by retired ? if its means deleting the course how could we delete an xml course ?
here's one on prod: https://courses.edx.org/courses/MITx/6.00x/2013_Spring/info
The problem is that these are ending up in the CourseOverview table even though they're not in the modulestore.
It might be good to check how many courses are in the Overview table but aren't in the modulestore. can you check that? Or , is there a discrepancy between the amount of items in the Overview vs coursestructure tables?
can you tell example of such course mention in description !?
TNL already has a large backlog of CAT-2s that the team is already working on. Can it wait until your team can pick it up? Or can I help you prioritize CAT-2s on your side so that you can take this on ASAP?
Assignee
Reporter
Labels
Reach
Impact
Platform Area
Customer
Partner Manager
URL
Contributor Name
Groups with Read-Only Access
Actual Points
Category of Work
Platform Map Area (Levels 1 & 2)
Platform Map Area (Levels 3 & 4)
Priority
