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

7th
Jun 2017
Hong Phuc Dang
@hpdang
Jun 07 2017 13:46
hi @/all , i can't see any event listed on the main page of eventyay https://eventyay.com
Hong Phuc Dang
@hpdang
Jun 07 2017 13:53
there are 3 events on the admin interface https://eventyay.com/admin/events/, can someone look into it asap please? I am asking other organizers to try out our system and how can we get people to try out our system if there is nothing on the page
Mario Behling
@mariobehling
Jun 07 2017 13:53
There should be 3 events that are live listed, e.g. https://eventyay.com/e/de88e486/
Hong Phuc Dang
@hpdang
Jun 07 2017 13:54
also on the search bar, why the default is United States?
Niranjan Rajendran
@niranjan94
Jun 07 2017 14:40
@hpdang issue fossasia/open-event-orga-server#3743 for the events created and assigned. Will be fixed soon.
Hong Phuc Dang
@hpdang
Jun 07 2017 14:40
great, thanks @niranjan94
Niranjan Rajendran
@niranjan94
Jun 07 2017 14:45
As for the search bar location ... It has been fixed in the nextgen branch (Related issue: fossasia/open-event-orga-server#2722) . But that fix cannot be applied to the current eventyay deployment since it involves a complete change of the kubernetes configuration.
Mario Behling
@mariobehling
Jun 07 2017 15:37
@niranjan94 Do you have some info what is the status of the redesign? Can the switch to nextgen happen soon?
Niranjan Rajendran
@niranjan94
Jun 07 2017 15:52
Yes. The API implementation has started. Basic APIs are done. The docs for the same would be done this week too. In the front end, public event pages, and event edit create, and detail pages UI is done. Admin UI is being done right now. Api implementation into the Frontend will begin from next week (milestone 6). So, I believe we could make a switch by Milestone 8 or 9.
Mario Behling
@mariobehling
Jun 07 2017 16:24
ok, great
Niranjan Rajendran
@niranjan94
Jun 07 2017 18:20

Hello @SaptakS @LuD1161 @magdalenesuo @enigmaeth @poush @shubham-padia

Please take the milestones more seriously. And work towards finished the issues assigned for a particular milestone before the milestone gets over. The new frontend will be starting with API implementation from Milestone 6 (upcoming week.)
So please ensure all the issues currently in Milestone 5 are done and the PRs merged.

Saptak Sengupta
@SaptakS
Jun 07 2017 18:20
@niranjan94 Yeah sure.
Niranjan Rajendran
@niranjan94
Jun 07 2017 18:21
Thanks @SaptakS
Saptak Sengupta
@SaptakS
Jun 07 2017 18:25
@niranjan94 @mariobehling @hpdang I just checked the admin panel, the other two events are not shown in homepage because their listing privacy is set to private
Should I make them public?
@magdalenesuo I doubt you will be able to reproduce this issue locally since it was an event setting problem. Could you reproduce?
Mario Behling
@mariobehling
Jun 07 2017 18:32
@SaptakS Where do we have a private feature?
Saptak Sengupta
@SaptakS
Jun 07 2017 18:32
In the event creation step 1
Mario Behling
@mariobehling
Jun 07 2017 18:33
ah yeah. I forgot about it.
In this case these events should neither show up in the new front-end, but they do.
Saptak Sengupta
@SaptakS
Jun 07 2017 18:34
Screenshot from 2017-06-08 00-02-54.png
Mario Behling
@mariobehling
Jun 07 2017 18:34
So apparently the front-end does not adhere to it.
Saptak Sengupta
@SaptakS
Jun 07 2017 18:34
That might be wrong in the new frontend then. Yes.
So the issue isn't with our eventyay development branch.
Mario Behling
@mariobehling
Jun 07 2017 18:34
Could you open an issue please? Might need to be implemented in both API and front-end
Saptak Sengupta
@SaptakS
Jun 07 2017 18:34
API it has been implemented while I reviewed the PR...
Mario Behling
@mariobehling
Jun 07 2017 18:34

So the issue isn't with our eventyay development branch.

Exactly.

ok
Saptak Sengupta
@SaptakS
Jun 07 2017 18:35
@niranjan94 can you open a relevant issue in the open-event-frontend?
@mariobehling I am closing this issue then:
fossasia/open-event-orga-server#3743
Niranjan Rajendran
@niranjan94
Jun 07 2017 18:36
@SaptakS @mariobehling the new Frontend will take care of that when the new api is implemented. Right now it's just loading some event data so that we are able to preview it the ui
Saptak Sengupta
@SaptakS
Jun 07 2017 18:37
@niranjan94 @mariobehling yes. I think it was problem with the old API... New API privacy information is being sent in event API
Afroz Ahamad
@enigmaeth
Jun 07 2017 18:54
@magdalenesuo @shubham-padia Could you please check fossasia/open-event-orga-server#3728 now ? I can push the discount codes API then. I already have it locally( but checked out from the same PR branch.. so it has to be merged first!!) Thanks :smile:
Niranjan Rajendran
@niranjan94
Jun 07 2017 18:56
@enigmaeth why is it checked out from the branch of a PR?
Work from fresh branches off the latest nextgen branch
So that these issue don't arrise
Saptak Sengupta
@SaptakS
Jun 07 2017 18:57
Afroz no big deal... you can create a new branch and cherry pick the commits from the already existing branch in case you have already committed..
in case you haven't just stash your changes..
create a new branch from nextgen...
and do git stash pop...
And they will come back..
:)
Afroz Ahamad
@enigmaeth
Jun 07 2017 18:58
Some part of the Discount Code had to be written to write a basic relationship. I had to add attributes to the same Schema, so I checked it out from the PR. @niranjan94
Thanks for this @SaptakS . I'll try doing it.
:sparkles:
Saptak Sengupta
@SaptakS
Jun 07 2017 18:59
:+1: