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

Unable to move questions up or down #1743

Closed
skryukova opened this issue Apr 14, 2024 · 2 comments
Closed

Unable to move questions up or down #1743

skryukova opened this issue Apr 14, 2024 · 2 comments
Labels
type: bug Needs fix

Comments

@skryukova
Copy link

Problem and impact

When trying to move per speaker questions up or down, nothing appears to happen. The UI does display The order has been updated. message, but nothing changes on the screen. Refreshing the screen also shows original order.

The CFP is closed, and we are in the review process. I was trying to add a few questions for the "accepted" speakers to fill out.

Looking at the Network panel in the Dev Tools, I see that calls to the backend endpoints result in 302 Found

Expected behaviour

No response

Steps to reproduce

  1. Create CFP with several "per speaker" questions
  2. After CFP closes, create new question.
  3. Try to move the original or new questions up or down in the list.

Screenshots

No response

Link

No response

Browser (software, desktop or mobile?) and version

Google Chrome

Operating system, dependency versions

No response

Version

No response

@skryukova skryukova added the type: bug Needs fix label Apr 14, 2024
@rixx
Copy link
Member

rixx commented Apr 14, 2024

Link
No response

These fields exist for a reason: without knowing which instance or which pretalx version bug reports refer to, this maximises the work we get to do to reproduce the bug or figure out what's going on.

@rixx rixx closed this as not planned Won't fix, can't repro, duplicate, stale Apr 14, 2024
@rixx
Copy link
Member

rixx commented Apr 14, 2024

For reference, this is a bug that was fixed in 3aab65e, and knowing if the bug occurred on pretalx.com or in development or on a self-hosted instance would have narrowed it down quite a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Needs fix
Projects
None yet
Development

No branches or pull requests

2 participants