fix: discussion tab visibility on import

[Anas12091101]

Description

Problem

When a course is exported and imported (or rerun) into another course, the discussion tab's is_hidden state is copied verbatim via modulestore's course.tabs. However, DiscussionsConfiguration.enabled, a separate Django DB model, is not carried over. It either already exists with enabled=True (created when the destination course was set up) or gets freshly created with the default enabled=True.

This causes a desync:

• Modulestore (course.tabs[discussion].is_hidden = True) → LMS hides the Discussion tab
• DB (DiscussionsConfiguration.enabled = True) → Authoring MFE "Hide discussion tab" toggle shows OFF

The learner sees no Discussion tab, but Studio incorrectly shows it as not hidden.

Root Cause

The course_published signal handler in handlers.py creates/updates DiscussionsConfiguration without consulting the modulestore tab state. The serializer's _update_course_configuration syncs tab.is_hidden ↔ enabled, but only on API save (POST/PATCH), never on publish or import.

Fix

In update_course_discussion_config(), before creating or updating DiscussionsConfiguration, we now read the discussion tab's is_hidden from the published branch of modulestore and derive enabled = not tab.is_hidden. This applies to both new and existing config paths. If the modulestore read fails, enabled defaults to True for backward compatibility.

Useful information to include:

• Which edX user roles will this change impact? "Course Author"
• Include screenshots for changes to the UI (ideally, both "before" and "after" screenshots, if applicable).
• Provide links to the description of corresponding configuration changes. Remember to correctly annotate these
  changes.

Supporting information

https://github.com/mitodl/hq/issues/10272

Testing instructions

1. Create Course A → hide Discussion tab via Pages & Resources
2. Export Course A
3. Create Course B → import Course A tarball
4. Verify: Discussion tab hidden in LMS, "Hide discussion tab" toggle in Pages and Resources shows ON, DiscussionsConfiguration.enabled is False

Deadline

"None"

Other information

Include anything else that will help reviewers and consumers understand the change.

• Does this change depend on other changes elsewhere?
• Any special concerns or limitations? For example: deprecations, migrations, security, or accessibility.
• If your database migration can't be rolled back easily.

[openedx-webhooks]

Thanks for the pull request, @Anas12091101!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

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 approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To 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:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where 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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.