You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have installed Repairs in my server .... but i have this error:
Fatal error: Call to a member function GetIsCalendarSubscriptionAllowed() on null in /web/htdocs/debiancool_777/home/macchine/lib/Application/Schedule/CalendarSubscriptionService.php on line 251
when i click on
127.0.0.1/Web/calendar.php?sid=8
Thx
The text was updated successfully, but these errors were encountered:
Yes. That is because we use hardcoded links to schedules for the "Schedules → …" (or in German "Werkstattpläne → …") menu items. The link you tried goes to a schedule with ID 8 (?sid=8) and that schedule does not exist (yet).
You can create new schedules under "Admin → Schedules" (or in German "Admin → Werkstattpläne"), see /Web/admin/manage_schedules.php. And then, if you want to use the same mechanism of hardcoding menu items to your schedules, you would adapt the menu entries in file tpl/globalheader.tpl.
This hardcoding of links to specific schedules is obviously just a quick fix. Ideally, we would create a GUI mechanism for that, or just create a menu entry for each schedule automatically. So I keep this issue open to remind us that we should do this some day …
tanius
changed the title
Error
Fix that menu items for schedules are hardcoded (creating an error in new installations)
May 25, 2019
tanius
changed the title
Fix that menu items for schedules are hardcoded (creating an error in new installations)
Fix that menu items for schedules are hardcoded in the template
May 25, 2019
Hi,
I have installed Repairs in my server .... but i have this error:
Fatal error: Call to a member function GetIsCalendarSubscriptionAllowed() on null in /web/htdocs/debiancool_777/home/macchine/lib/Application/Schedule/CalendarSubscriptionService.php on line 251
when i click on
127.0.0.1/Web/calendar.php?sid=8
Thx
The text was updated successfully, but these errors were encountered: