Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Course Teacher goes out of sync if a new Lesson is added after a Course is published #7599

Open
markcummins opened this issue Apr 25, 2024 · 0 comments · May be fixed by #7600
Open

Course Teacher goes out of sync if a new Lesson is added after a Course is published #7599

markcummins opened this issue Apr 25, 2024 · 0 comments · May be fixed by #7600

Comments

@markcummins
Copy link
Contributor

Steps to Reproduce

  1. Create a New Course and Lessons (e.g. Lesson A and Lesson B)
  2. Set the Course Teacher to be another User
  3. Add another Lesson and assign it to the Course (e.g. Lesson C)
  4. Log in as the Course Teacher

What I Expected

When I logged in as the Course teacher, I expected to be able to Edit All the lessons for the course

What Happened Instead

I was only able to edit the lessons that were added before the Teacher was assigned to the Course

PHP / WordPress / Sensei LMS version

PHP Version: 8.2.7
WordPress: 6.5.2
Sensei: 4.23.1

Browser / OS version

Chrome: 124.0.6367.78

Context / Source

I believe that when you set the Course teacher, it sets the course teacher as the author for all of the lessons. If you later add another lesson to the course, the lesson can have a different author, and therefore the teacher won't be able to access it.

@markcummins markcummins added [Status] Needs Triage Issue needs to be triaged [Type] Bug labels Apr 25, 2024
@markcummins markcummins linked a pull request Apr 25, 2024 that will close this issue
15 tasks
@merkushin merkushin removed the [Status] Needs Triage Issue needs to be triaged label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants