Skip to content

fix: unhide discussion tab when enabling it (#677) - #35431

Merged
sarina merged 1 commit into
openedx:masterfrom
open-craft:viadanna/unhide-discussions
Jun 25, 2025
Merged

fix: unhide discussion tab when enabling it (#677)#35431
sarina merged 1 commit into
openedx:masterfrom
open-craft:viadanna/unhide-discussions

Conversation

@viadanna

@viadanna viadanna commented Sep 4, 2024

Copy link
Copy Markdown
Contributor

Description

Update the is_hidden property in the modulestore to store the visibility of the discussions tab properly.

Supporting information

Testing instructions

  1. Create a course in a Palm devstack/sandbox.
  2. Set the discussion tab to hidden.
  3. Export the course.
  4. Import the course in a Redwood devstack/sandbox.
  5. Create a Course Update
  6. Verify the discussion tab disappears in the LMS.
  7. Apply this change to the devstack/sandbox.
  8. Enable the discussions in Studio Pages & Resources.
  9. Create a Course Update.
  10. Verify the discussion tab does not disappear this time.

Deadline

None

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Sep 4, 2024
@openedx-webhooks

openedx-webhooks commented Sep 4, 2024

Copy link
Copy Markdown

Thanks for the pull request, @viadanna!

This repository is currently maintained by @openedx/wg-maintenance-edx-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:

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.

@mphilbrick211 mphilbrick211 added the needs reviewer assigned PR needs to be (re-)assigned a new reviewer label Sep 6, 2024
@viadanna
viadanna force-pushed the viadanna/unhide-discussions branch from 8c4abae to 9ea51d7 Compare September 9, 2024 11:54

@xitij2000 xitij2000 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@viadanna Could you add a test case for this?

@viadanna
viadanna force-pushed the viadanna/unhide-discussions branch from 4dee709 to ec86ca9 Compare September 11, 2024 14:48
@arslanashraf7

Copy link
Copy Markdown
Contributor

@viadanna I have seen a similar problem with the Progress page as well. Maybe this is related to all the pages which were once managed through legacy Studio (Pages) and are now managed by Authoring MFE's (Pages & Resources)

@xitij2000 xitij2000 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Working well!

  • I tested this: tested on tutor nightly devstack
  • I read through the code

@viadanna

Copy link
Copy Markdown
Contributor Author

@arslanashraf7 I haven't seen this issue with the progress page yet. I'd look into the endpoint handler view to check if the problem has the same cause as this one.

@viadanna

Copy link
Copy Markdown
Contributor Author

Thanks @xitij2000

@arslanashraf7

Copy link
Copy Markdown
Contributor

@arslanashraf7 I haven't seen this issue with the progress page yet. I'd look into the endpoint handler view to check if the problem has the same cause as this one.

@viadanna Thanks.

For me, the steps were almost identical to yours and they are as follows:

  1. Disable Authoring MFE (Disable discussions.pages_and_resources_mfe waffle flag)
  2. Open the Pages page for a course in the studio from course settings
  3. Hide the progress page & save
  4. Re-enable the Authoring MFE (Enable discussions.pages_and_resources_mfe waffle flag)
  5. Export the course, And re-import
  6. Open Pages & Resources from the authoring MFE settings menu and Toggle the switch on the Progress card through
  7. The progress pages in the LMS/LearningMFE would stay hidden even if the switch for the progress page is On.

@mphilbrick211

Copy link
Copy Markdown

Hi @viadanna! Apologies for the delay in getting reviews. I've put this out to the community to help get it looked at.

In the meantime, would you be able to run the new tests that have popped up?

@viadanna

Copy link
Copy Markdown
Contributor Author

Sure thing, done @mphilbrick211

@mphilbrick211

Copy link
Copy Markdown

Sure thing, done @mphilbrick211

Hi @viadanna - apologies, but another test has popped up. Would you mind running it when you get a moment? Thanks!

@sarina

sarina commented May 29, 2025

Copy link
Copy Markdown
Contributor

@viadanna I don't think I fully understand the problem here based on your description. What was the previous behavior this is trying to fix?

@viadanna

Copy link
Copy Markdown
Contributor Author

@sarina Redwood changed how discussions are hidden or disabled, which didn't unhide courses previously hidden on Palm.

@sarina

sarina commented Jun 2, 2025

Copy link
Copy Markdown
Contributor

I still don't think I understand, I'm sorry. Could you describe:

  • Previous behavior (pre-palm)
  • Current behavior (on master)
  • What problem this fix solves?

I am not really familiar with discussions, this problem, and the code comments don't help me. aton.

@viadanna

Copy link
Copy Markdown
Contributor Author

Sorry for not being clear, Sarina. There are currently two mechanisms for hiding the discussions tab in Open edX:

  1. Pre-palm, we would mark the discussion tab with the is_hidden property.
  2. Redwood and later, we disable discussions entirely by toggling the discussion configuration enabled property.

The problem is that these properties aren't kept in sync when disabling discussions in master.

So a course that had its discussions hidden pre-Palm would feature the is_hidden property. If that course is loaded into a master instance, it will never change that property when enabling discussions, leading to the discussions tab being hidden.

With this PR, whenever the discussions configuration is updated, the is_hidden property on the discussion tab will be set to match the enabled state, so enabling discussions will always unhide the tab, and disabling will hide it. This ensures that older courses with is_hidden set will behave consistently with newer courses using the enabled flag.

Comment thread openedx/core/djangoapps/discussions/serializers.py Outdated
Comment thread openedx/core/djangoapps/discussions/tests/test_views.py Outdated
@viadanna

Copy link
Copy Markdown
Contributor Author

Thanks for the recommendations @sarina

@sarina

sarina commented Jun 24, 2025

Copy link
Copy Markdown
Contributor

@viadanna apologies but could you kindly address the failing test?

@viadanna
viadanna force-pushed the viadanna/unhide-discussions branch from d28ecaf to 4155613 Compare June 24, 2025 17:34
@viadanna

Copy link
Copy Markdown
Contributor Author

Sure, done @sarina

@sarina
sarina merged commit 31218a5 into openedx:master Jun 25, 2025
49 checks passed
@github-project-automation github-project-automation Bot moved this from Ready for Review to Done in Contributions Jun 25, 2025
@openedx-webhooks openedx-webhooks removed the needs reviewer assigned PR needs to be (re-)assigned a new reviewer label Jun 25, 2025
@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

1 similar comment
@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

@viadanna

Copy link
Copy Markdown
Contributor Author

Thank you, Sarina!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

8 participants