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

My Sessions: Shows past sessions in unscheduled session of past event in tab "Upcoming" #3702

Closed
mariobehling opened this issue Dec 15, 2019 · 6 comments · Fixed by #3791
Closed
Labels

Comments

@mariobehling
Copy link
Member

mariobehling commented Dec 15, 2019

My Sessions: Shows past sessions in unscheduled session of past event in tab "Upcoming"
The private link is at https://eventyay.com/my-sessions/upcoming.
Furthermore the sessions shows up 4 x times.

EXPECTED: Even though the session is unscheduled, the system should take the time of the overall event. If the event is past the unscheduled session should also show up in the "past tab".

Screenshot from 2019-12-15 18-30-13

@kushthedude
Copy link
Member

@mariobehling What about having a tab for Unscheduled, It would make more sense as showing sessions with time & date = null in upcoming and past doesn't seem nice ?

@maze-runnar
Copy link
Contributor

@kushthedude while working on my-session showing multiple times issue , i solved this . Can i open a PR for it ,
Implementation is as @mariobehling has said.when session is unscheduled, the system should take the time of the overall event. If event is past , session is also past.

@kushthedude
Copy link
Member

kushthedude commented Jan 10, 2020 via email

@kushthedude
Copy link
Member

kushthedude commented Jan 10, 2020 via email

@maze-runnar
Copy link
Contributor

ok, i will keep that in mind .

@maze-runnar
Copy link
Contributor

actually making changes in open-event-frontend/app/routes/my-sessions/list.js .

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

Successfully merging a pull request may close this issue.

3 participants