openedx / openedx/openedx-core
[Backup & Restore LibV2] Fix incorrect published status after restore
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 32
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 12
Description
Use case
Restoring a library from a ZIP file containing a single component with these versions:
- Version 9 – Draft
Actual result after restoring:
- Version 9 – Published
This is unexpected. The restored library should mirror exactly the version statuses present in the ZIP file. Instead, the published/draft states are being flipped during the restore process.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the ZIP restore case with a library containing one component and a Draft Version 9, then locate the library backup and restore entry point. Trace how version status is handled during restore; done means the restored version remains Draft and matches the status recorded in the ZIP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100