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

Feedback sessions with # or ? in their name can't be edited. #9642

Closed
ChooJeremy opened this issue Apr 3, 2019 · 7 comments · Fixed by #9925
Closed

Feedback sessions with # or ? in their name can't be edited. #9642

ChooJeremy opened this issue Apr 3, 2019 · 7 comments · Fixed by #9925
Labels
c.Bug Bug/defect report help wanted Moderate difficulty, small localized change; suitable for novice contributors

Comments

@ChooJeremy
Copy link
Contributor

Other potential characters may cause this problem as well.

  • Environment: master branch at commit 3455dda.

Steps to reproduce

  1. Login as an instructor.
  2. Create a new feedback session with # in the name (i.e. test Feedback sessions with # or ? in their name can't be edited. #9642)
  3. Click edit on the new feedback session.

Expected behaviour
The feedback session edit page loads

Actual behaviour
It doesn't load.
image

Additional info

This error occurs even after applying the fix from #9638 .
The server outputs the error log:
WARNING: UnauthorizedAccessException caught by WebApiServlet: Trying to access system using a non-existent feedback session entity
The error appears to be from the frontend not sending the character # or ? in the query (and anything after it)

@ChooJeremy ChooJeremy added c.Bug Bug/defect report f-Sessions labels Apr 3, 2019
@TheDheeraj007
Copy link

Hello! This issue looks interesting. Can I work on this issue?

@ChooJeremy
Copy link
Contributor Author

ChooJeremy commented Jun 29, 2019

Sure, go ahead! Usually we recommend starting with a first timer issue, but since there aren't many first timer issues right now feel free to start working on this.

@dodgees
Copy link
Contributor

dodgees commented Oct 4, 2019

It looks like there hasn't been any activity on this issue. Mind if I pick it up?

@ChooJeremy
Copy link
Contributor Author

I don't mind - Go ahead :)

@hcwong
Copy link
Contributor

hcwong commented Jan 17, 2020

If this is inactive I would like to take it

@hcwong
Copy link
Contributor

hcwong commented Jan 17, 2020

It's probably the issue with URL special characters. I'm thinking of decoding/encoding the strings properly and also preventing future session names from having such characters.

@xpdavid xpdavid added the help wanted Moderate difficulty, small localized change; suitable for novice contributors label Jan 17, 2020
@ChooJeremy
Copy link
Contributor Author

Looks inactive - go ahead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c.Bug Bug/defect report help wanted Moderate difficulty, small localized change; suitable for novice contributors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants