|
From: Harald N. <hoc...@gm...> - 2025-09-03 00:04:51
|
Solved - it was exactly the problem described here: https://gitlab.com/davical-project/davical/-/issues/171 specifically the command sudo -u postgres psql davical -f /usr/share/davical/dba/caldav_functions.sql br, Harald Am 31.08.25 um 15:13 schrieb Harald Nikolisin: > Hello, > > I migrated an old davical installation (davical 1.1.7 / postgresql 9.2 > / php 5.6 / apache 2.2) > to a new server environment which uses (davical 1.1.7 / postgresql 11 > / php 7.4 / apache 2.4) > > Actually it runs out of the box, but only with the private calendars. > Currently there are 4 users in that setup - each of them has their own > calendar, but there is also a "group principal" where every of the 4 > user is member of. Principals grants were set to have read/write > access from every user. > > In the old system everything worked. Every user had r/w access to the > group calendar. Even the free/busy system worked (at least with > clients which supported it, like Thunderbird calendar) > > In the new system neither the group calendar, nor the free/busy access > of the other calenders is working. > > What I did is to copy the database to an experimental server, also > with postgresql 11 / php 7.4 and apache 2.4. > Here I updated davial - first to 1.1.9-3 (database schema update to > 1.3.3) and then to the lastest version 1.1.12 (database schema upgrade > to 1.3.5). > > Unfortunately without success - does anybody has an idea? > My davical config file contains only 3 entries (c->domainname, > c->admin-email, c->pg_connect). > > best regards, > Harald > > |