Help with timetables

I am having some issues with understanding the TimeTables. I follow the procedure on https://docs.gibbonedu.org/administrators/timetable/timetabling/ making sure I had all the prerequisites.

But when adding the days to dates, I tested with Monday only and showed up correctly, but then when I added the other days Monday disappeared, and it shows up as blocked?

it looks like the assignment got duplicated. Is that the reason it is being blocked? how can I clean those assignments?

Guess you have to do some cleaning up here. To get started click the edit icon of MO 5/25 and delete all *LU entries. You should see a change in your timetable. Good luck. :slight_smile:

Hi aremis,

Unfortunately, the bulk add lets you add multiple days from a single timetable to one date, although that then stops the timetable from displaying properly. This is a bug that it is on our list to fix!

For now, I’d recommend you truncate (SQL term for emptying) your gibbonTTDayDate table. This will remove entries, and then you can add again, making sure to avoid duplicates. Hopefully this fixes the issue. The command, if you want to run it directly using SQL is:

TRUNCATE gibbonTTDayDate;

Let us know if you get it resolved.

Cheers,

Ross

Hi aremis,

Unfortunately, the bulk add lets you add multiple days from a single timetable to one date, although that then stops the timetable from displaying properly. This is a bug that it is on our list to fix!

For now, I’d recommend you truncate (SQL term for emptying) your gibbonTTDayDate table. This will remove entries, and then you can add again, making sure to avoid duplicates. Hopefully this fixes the issue. The command, if you want to run it directly using SQL is:

TRUNCATE gibbonTTDayDate;

Let us know if you get it resolved.

Cheers,

Ross

Thank you Ross. It worked fine.

Excellent, thanks : )

Hi Andres, just to let you know that this bug has now been fixed in the v20 development branch, as per the following commit:

https://github.com/GibbonEdu/core/commit/f29dc6e1d80db708b0a8ec98e251161289c7de79

v20 is due for release on 20/06/2020, but the change should be backward compatible for v19, if you need it now.

Thanks for prompting us to make this improvement : )

Ross