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

[BUG]: 404 Not Found error on valid collection player page. #20197

Open
jnvtnguyen opened this issue Apr 22, 2024 · 0 comments
Open

[BUG]: 404 Not Found error on valid collection player page. #20197

jnvtnguyen opened this issue Apr 22, 2024 · 0 comments
Labels
bug Label to indicate an issue is a regression good first issue Impact: Low -- ONLY DO IF GOOD FIRST ISSUE Postponing for now, since it doesn't affect users much. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.

Comments

@jnvtnguyen
Copy link
Contributor

jnvtnguyen commented Apr 22, 2024

Describe the bug

When I visit a valid collection player page, I get a 404 Not Found error.

URL of the page where the issue is observed.

/collection/

Steps To Reproduce

  1. Create a new collection (need collection editor rights).
  2. Create/add a exploration to the collection and publish it.
  3. Go to the collection player of that collection.

Expected Behavior

I expect there to be no 404 Not Found error.

Screenshots/Videos

Screenshot 2024-04-22 135125

What device are you using?

Desktop

Operating System

Windows

What browsers are you seeing the problem on?

Chrome

Browser version

No response

Additional context

The other parameter "key" error is a different issue which I filed here: #20198.

Tips for developers

Before addressing the bug, please identify which PR caused the issue (you can follow the steps here). If you identify the PR, comment on the issue with a link to it. If not, mention the commit hash of the oldest commit you saw the bug on (and the month and year it was made in).

Then, please leave a comment with details of the approach that you plan to take to fix the issue (see example).

Note: If this is your first Oppia issue, please make sure to follow our guidelines for choosing an issue and setting things up. You will also need to show a demo of the fix working correctly on your local machine. Thanks!

@jnvtnguyen jnvtnguyen added triage needed bug Label to indicate an issue is a regression labels Apr 22, 2024
@seanlip seanlip added Impact: Medium Will improve quality-of-life for at least 30% of users. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet. Impact: Low -- ONLY DO IF GOOD FIRST ISSUE Postponing for now, since it doesn't affect users much. and removed triage needed Impact: Medium Will improve quality-of-life for at least 30% of users. labels Apr 24, 2024
@seanlip seanlip added good first issue Impact: Medium Will improve quality-of-life for at least 30% of users. Impact: Low -- ONLY DO IF GOOD FIRST ISSUE Postponing for now, since it doesn't affect users much. and removed Impact: Low -- ONLY DO IF GOOD FIRST ISSUE Postponing for now, since it doesn't affect users much. Impact: Medium Will improve quality-of-life for at least 30% of users. labels Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Label to indicate an issue is a regression good first issue Impact: Low -- ONLY DO IF GOOD FIRST ISSUE Postponing for now, since it doesn't affect users much. Work: Medium The means to find the solution is clear, but it isn't at good-first-issue level yet.
Projects
Status: Todo
Development

No branches or pull requests

2 participants