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

Free Text (Label) in Registration not shown in Modification #3682

Closed
knusperman opened this Issue Dec 4, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@knusperman

knusperman commented Dec 4, 2018

Describe the bug
When placing a label (free text) in a registration form it is only shown at the registration itself, but when I want to modify the registration, I do not see the label. Likely this bug has appeared in 2.1.x, because I am almost certain that in 2.0.x it worked.

To Reproduce
Steps to reproduce the behavior:

  1. Create an event and a registration form
  2. Add a "free text" aka label field to it
  3. Open up the registration and register (you will see that your label is there)
  4. Modify the registration afterwards (no label there)

I also checked it on the sandbox.getindico.io

Expected behavior
I expect the label to be also present when being in modification mode. The whole point of it is to allow resubmitting information as a registrant, therefore I do not only need the modifiable fields but also the labels that have some reason to be there (e.g. stating "please only choose type x, when you are under 18...)

Screenshots
screenshot 2018-12-04 at 18 30 30
screenshot 2018-12-04 at 18 30 59

@ThiefMaster ThiefMaster added the bug label Dec 6, 2018

@ThiefMaster ThiefMaster added this to the v2.1 milestone Dec 6, 2018

@ThiefMaster ThiefMaster self-assigned this Dec 6, 2018

@ThiefMaster

This comment has been minimized.

Member

ThiefMaster commented Dec 6, 2018

Looks like a bug I introduced 3y ago in fc5ec8e. Will be fixed in 2.1.5 which will be released within the next days.

@ThiefMaster

This comment has been minimized.

Member

ThiefMaster commented Dec 7, 2018

2.1.5 is out which contains the fix for this (among some other fixes).

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