These are chat archives for fossasia/open-event-server

6th
Dec 2017
Mario Behling
@mariobehling
Dec 06 2017 08:47
@shubham-padia @SaptakS @niranjan94 We have an issue here. People seem to have difficulties to sign up through eventyay. There is an issue here, where Roland asks for a Google form instead: https://github.com/fossasia/open-event-legacy/issues/5#issuecomment-349548983
What do you think? Is there anything we can do?
Saptak Sengupta
@SaptakS
Dec 06 2017 09:06
@mariobehling the flow which is now there is the one which we planned later, else it was exactly as Roland wants. Initially there was always a single form with both session and speaker information which didn't need login/signup and needed to be just filled up and submitted.
But then we decided to make it such that to register speakers into the system first so that they can submit the session later.
This flow was thought of seeing some other event management site doing the same if I remember correctly.
Saptak Sengupta
@SaptakS
Dec 06 2017 09:15
@mariobehling as of implementing it back to the same flow as suggested by Roland, I feel it can be done but then again it will be a pretty lengthy form with all speaker and session informations, which I guess was the root cause of changing the flow. @niranjan94 comments.
@mariobehling however this exact same flow is followed almost at all the event management sites. One needs to register and login first to fill up details and so on... But then again since few days back I made the non verified user allowance, we can actually make this flow...
@mariobehling @niranjan94 the task is straight forward, question is whether we want it that way. Because changing the cfp flow again and again for every other event seems weird. This flow was implemented before another event because they found this way more easier.
Mario Behling
@mariobehling
Dec 06 2017 10:15

@SaptakS I think the issue is, that once the speaker register, they do not come back automatically to the sign up form. And once the speaker adds the speaker details, they do not always come back to the sign up form neither. So, let me tryout the flow again. We dont want to change it too many times. Do you have ideas how we could direct the speaker to the session form?

E.g. could we add a link or buttons below the speaker form with a list of their sessions and if there is no session "Add a session now"?

Mario Behling
@mariobehling
Dec 06 2017 10:34
@SaptakS @niranjan94 @shubham-padia so thinking this through, i think it would solve the problem.
Saptak Sengupta
@SaptakS
Dec 06 2017 10:36
@mariobehling after registration getting them directly to the speaker registration form can be done.
Mario Behling
@mariobehling
Dec 06 2017 10:36
we need a button at the end/below the speaker form "add a session" and show the
Existing sessions
Saptak Sengupta
@SaptakS
Dec 06 2017 10:36
And after speaker registration we can put 2 buttons. "Save speaker information" and "Save speaker and add a session".
If it's a new speaker he won't be having any session, so this makes sense I feel
Mario Behling
@mariobehling
Dec 06 2017 10:38
redirecting them to the sessions form immediately only makes sense if they only fill in one session but we have the option to fill in severeal session proposals
@SaptakS yes, your way is the fastest step forward
Please do it
And we add other things afterwards
please open an issue and see if it can be solved
👍
Rahul Tiwari
@invinciblycool
Dec 06 2017 13:55
@shubham-padia How do I use the open-event-legacy with the front end?
I mean it looks like this now...
opev.png
Shubham Padia
@shubham-padia
Dec 06 2017 15:16
@invinciblycool open event legacy does not have any seperate frontend and backend, both are coupled in the same repo, you can use the system as it is.
You would have to install bower dependencies to fix the problem in the screenshot
Just type bower install
Rahul Tiwari
@invinciblycool
Dec 06 2017 15:31
Yes, that's what I was puzzled about... :smile:
Thanks very much...
Rahul Tiwari
@invinciblycool
Dec 06 2017 15:49
@shubham-padia The switch to enable ticketing system is missing when I render the site locally.
legacy.png
Shubham Padia
@shubham-padia
Dec 06 2017 15:50
Please enable the ticketing module in admin settings
Rahul Tiwari
@invinciblycool
Dec 06 2017 15:50
On it.
Rahul Tiwari
@invinciblycool
Dec 06 2017 15:57
Yeah its there now. :thumbsup:
Rahul Tiwari
@invinciblycool
Dec 06 2017 16:13
@shubham-padia If I create an event with the ticketing system enabled and also create a free ticket and hit save and proceed and then again come back and again hit save and proceed, I am unable to save the event.
When I come back I don't change any form data.
Shubham Padia
@shubham-padia
Dec 06 2017 16:14
Please check again once and then open an issue for the same
Rahul Tiwari
@invinciblycool
Dec 06 2017 16:14
This is due to the integrity error since the ticket name remains same. But shouldn't it be saved?
I mean if user edits any other data except the ticket name, then you can't save the event.
Key (name, event_id)=(Blah blah, 2) already exists
This was the traceback when I created a ticket, saved, came back and then again saved.
Am I right? Shouldn't the event be saved?
And where should I open the issue.
Mario Behling
@mariobehling
Dec 06 2017 16:17
@SaptakS @shubham-padia I created two issues to implement Rolands request to make things easier: fossasia/open-event-legacy#7 and fossasia/open-event-legacy#7 Does these make sense to you?
Rahul Tiwari
@invinciblycool
Dec 06 2017 16:18
In legacy repo or the normal one.
Shubham Padia
@shubham-padia
Dec 06 2017 16:19
@mariobehling yes
@invinciblycool legacy
Rahul Tiwari
@invinciblycool
Dec 06 2017 16:27
@shubham-padia Please check fossasia/open-event-legacy#8 and confirm so that I can work on it.
Shubham Padia
@shubham-padia
Dec 06 2017 16:28
:+1: