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

Schedule: Calendar View Errors #4996

Closed
mariobehling opened this issue Sep 5, 2020 · 2 comments · Fixed by #5997
Closed

Schedule: Calendar View Errors #4996

mariobehling opened this issue Sep 5, 2020 · 2 comments · Fixed by #5997

Comments

@mariobehling
Copy link
Member

After the last update the calendar reloads nicely on timezone changes. There are few issues with the display though.

  • On two day events, it only displays one date as "day", "day"
  • The first day does not display the view of sessions below each other
    Screenshot from 2020-09-05 14-21-18
  • Loading another view is not persistent, e.g. if a user chooses two day view and then switches the timezone, the display will move back to one day view
@iamareebjamal
Copy link
Member

iamareebjamal commented Sep 5, 2020

That is not day switcher, it's view switcher. Day switcher is on left. First view is timeline view, second is default (resource agenda), then it's multi-day view and week view

And we can't change the text of the items on right. FullCalendar does not provide the feature. These can be hidden however

@mariobehling
Copy link
Member Author

Ok, I got confused, because there is a 2 x day.

It is more logic in the "schedule".

Screenshot from 2020-09-05 16-51-01

I also see that switching the days with the buttons on the left results in the second day starting at 0:00

Screenshot from 2020-09-05 16-49-30

I wonder what is the best solution to all this. Possibly we could require an organizer to define start and end times for each day. Let's talk about it in the weekly meeting.

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

Successfully merging a pull request may close this issue.

2 participants