Skip to content

fix: use a single 'provider_type' key for storing discussion provider type in course - #36039

Merged
farhaanbukhsh merged 3 commits into
openedx:masterfrom
open-craft:kshitij/fix-discussion-clone
Jul 6, 2025
Merged

fix: use a single 'provider_type' key for storing discussion provider type in course#36039
farhaanbukhsh merged 3 commits into
openedx:masterfrom
open-craft:kshitij/fix-discussion-clone

Conversation

@xitij2000

Copy link
Copy Markdown
Contributor

Description

Both 'provider' and 'provider_type' have been used for storing the discussion provider type in course 'discussions_settings' field, there are some places in the code checking for 'provider' and others checking for 'provider_type', in some cases this can cause a bug where it doesn't detect the correct provider which causes discussion settings not being copied correctly when a course is cloned.

This change prioritises the provider_type setting over provider and reads provider only as a fallback. The provider setting is now made read-only just for backwards-compatibility, to avoid confusion.

Testing instructions

  • Create a course structure with discussions enable or disabled in different sections. You can use this test course.
  • Use the course clone API to clone the course: studio.local.openedx.io:8001/api/v1/course_runs/clone/
  • Check that the discussion enabled/disabled statues is copied over.

Deadline

None

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

openedx-webhooks commented Dec 17, 2024

Copy link
Copy Markdown

Thanks for the pull request, @xitij2000!

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 Dec 17, 2024

@0x29a 0x29a 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.

👍

  • I tested this: tried cloning a course with different discussion settings and ensured that they're preserved.
  • I read through the code.

@sarina

sarina commented May 29, 2025

Copy link
Copy Markdown
Contributor

I think this makes sense to me, but I don't think I can provide an approving review. @xitij2000 is there an edx-platform CC within OpenCraft who can provide an approving review for your PR?

@openedx-webhooks openedx-webhooks added the core contributor PR author is a Core Contributor (who may or may not have write access to this repo). label May 29, 2025
@xitij2000

Copy link
Copy Markdown
Contributor Author

I think this makes sense to me, but I don't think I can provide an approving review. @xitij2000 is there an edx-platform CC within OpenCraft who can provide an approving review for your PR?

Sorry for missing this comment. I'll check if @Agrendalath, @farhaanbukhsh or @navinkarkera can have a look.

@xitij2000
xitij2000 force-pushed the kshitij/fix-discussion-clone branch 2 times, most recently from 623c7f6 to ddaac3d Compare June 16, 2025 11:37
@farhaanbukhsh

Copy link
Copy Markdown
Member

@xitij2000 I wasn't able to get the testing instructions to work right. I tried to clone the course

from cms.djangoapps.contentstore.views.course import create_new_course, get_course_and_check_access, rerun_course
from django.contrib.auth import get_user_model
from opaque_keys.edx.keys import CourseKey

user = get_user_model().objects.get(username="edx")
source_course_key = CourseKey.from_string("course-v1:lib101+cs101+2020")
destination_course_key = CourseKey.from_string(course-v1:lib101_clone+cs101+2020)
source_course_run = get_course_and_check_access(source_course_key, user)
fields = {
    'display_name': source_course_run.display_name,
}

destination_course_run_key = rerun_course(
    user, source_course_key, destination_course_key.org, destination_course_key.course,
    destination_course_key.run, fields, background=False,
)

destination_course_run = get_course_and_check_access(destination_course_run_key, user)

In the original course, I went to studio -> page and resources -> discussion and Hide the discussion tab but when I clone the Hide the discussion tab toggle is off. Am I getting this wrong?

@farhaanbukhsh farhaanbukhsh left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you elaborate on the testing instructions please.

Comment thread cms/djangoapps/contentstore/tasks.py Outdated
if (
ENABLE_NEW_STRUCTURE_DISCUSSIONS.is_enabled()
and not course.discussions_settings['provider_type'] == Provider.OPEN_EDX
and not course.discussions_settings['provider'] == Provider.OPEN_EDX

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Nit: it would make sense to use .get() here, in case the course does not have this attribute.

… type in course

Both 'provider' and 'provider_type' have been used for storing the discussion provider type in course 'discussions_settings' field, there are some places in the code checking for 'provider' and others checking for 'provider_type', in some cases this can cause a bug where it doesn't detect the correct provider which causes discussion settings not being copied correctly when a course is cloned.

This change prioritises the `provider_type` setting over `provider` and reads `provider` only as a fallback. The `provider` setting is now made read-only just for backwards-compatibility, to avoid confusion.
@xitij2000
xitij2000 force-pushed the kshitij/fix-discussion-clone branch from ddaac3d to 4e97104 Compare June 26, 2025 10:06

@farhaanbukhsh farhaanbukhsh left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

👍

Thank you @xitij2000 for adding the comments explaining this decision.

  • ✅ I tested this using tutor and clone course code
  • ✅ I read through the code
  • ❌ I checked for accessibility issues
  • ✅ Includes documentation

@farhaanbukhsh
farhaanbukhsh merged commit 80fa4f3 into openedx:master Jul 6, 2025
@farhaanbukhsh
farhaanbukhsh deleted the kshitij/fix-discussion-clone branch July 6, 2025 12:08
@openedx-webhooks openedx-webhooks removed the needs reviewer assigned PR needs to be (re-)assigned a new reviewer label Jul 6, 2025
@github-project-automation github-project-automation Bot moved this from Ready for Review to Done in Contributions Jul 6, 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.

@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.

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

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). 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