Open-event-frontend: Call for Speakers: Does not show all form fields in Speaker and Session page

[mariobehling]

In the wizard it is possible to enable/disable form fields for speakers and sessions. The form does not actually show the fields that are enabled in the speakers and session form.

Here is the wizard form. A lot of form fields are enabled, e.g. Github. But: They dont show up in the form of the speaker.

Here is the speaker form. Many of the above enabled form fields don't show up.

The session form is also missing a lot of form elements.

[kushthedude]

Checking it, As the CFS issues were solved way back but by seeing the order of fields in session form, I think the issue is related to legacy.
@mariobehling Can you please the event name ?

[mariobehling]

It is not related to legacy. The event was setup as a fresh event. Please try testing it.

[mariobehling]

Also, save the event and edit it. There is also the questions if editing event is possible and if the fields change accordingly.

[kushthedude]

I got the issue for rendering, but in session the fields are jumbled which
will have to be fixed manually as it was earlier for OTS Thailand.

On Thu, 31 Oct, 2019, 17:32 Mario Behling, [e-mail] wrote:

Also, save the event and edit it. There is also the questions if editing
event is possible and if the fields change accordingly.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-frontend/issues/3585?email_source=notifications&email_token=AKQMTLR4R4EKQ6OVWLSUU63QRLCMRA5CNFSM4JHHVHSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXPZNQ#issuecomment-548338870,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLRRTSADT5W3ZQG3OWDQRLCMRANCNFSM4JHHVHSA
.

[prateekj117]

@mariobehling Looking into it.

[mariobehling]

When a new speaker submits speaker info for the first time, it still does not show all the fields. Please test with an event that shows all fields (enable all fields in wizard step 4 and test it please).
Compare https://eventyay.com/e/a74665c3/cfs/new-speaker

[iamareebjamal]

@mariobehling This fix has not been deployed yet. You can try it out on the dev instance

[kushthedude]

@iamareebjamal the session issue is still not solved

[prateekj117]

@kushthedude Can you please provide screenshots, I will have a look at it right away.

[iamareebjamal]

@kushthedude Which fields are missing?

I can see comment, level, session type, short abstract, slide, title and track enabled. All of which are present in the form

[kushthedude]

@kushthedude Which fields are missing?

I can see comment, level, session type, short abstract, slide, title and track enabled. All of which are present in the form

https://github.com/fossasia/open-event-server/issues/6273

[kushthedude]

The order and the issue which I told you earlier to fix the order manually .

[prateekj117]

@kushthedude So unordered, not missing, right?

[kushthedude]

Yup.

On Sun, 3 Nov, 2019, 23:28 Prateek Jain, [e-mail] wrote:

@kushthedude https://github.com/kushthedude So unordered, not missing,
right?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-frontend/issues/3585?email_source=notifications&email_token=AKQMTLT5ZVTSCLSG55YO6VTQR4GK5A5CNFSM4JHHVHSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC5Y2NY#issuecomment-549162295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLU2ZRQSGMNBCYU3EFDQR4GK5ANCNFSM4JHHVHSA
.

[prateekj117]

@iamareebjamal Ya, they are unordered. I will see if I am able to find the cause of it.

[kushthedude]

Actually there is no bug for this, all the new events getting created are
with correct order in fields.
I have mentioned a link to issue where this was occurring before and it was
solved by manually correcting the order in DB

On Sun, 3 Nov, 2019, 23:31 Prateek Jain, [e-mail] wrote:

@iamareebjamal https://github.com/iamareebjamal Ya, they are unordered.
I will see if I am able to find the bug causing it.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-frontend/issues/3585?email_source=notifications&email_token=AKQMTLWHMX6NIGYWURHUWQLQR4GXBA5CNFSM4JHHVHSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC5Y4TY#issuecomment-549162575,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLS5KEG5VMAGIVRRA4LQR4GXBANCNFSM4JHHVHSA
.

[prateekj117]

It was happening at my local machine as well. There must be a reason that they are rendered unordered. @iamareebjamal Need your insight.

[iamareebjamal]

Because there is no order defined in the backend, so they are returned in the order of IDs. That is another issue and should be solved by allowing the admin to reorder the fields. Fixing it in the DB is a workaround. Let's create another issue for that