[Tickets #15070] Re: Timezone information of event is lost after sync. This causes problems with Android client.

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/15070
------------------------------------------------------------------------------
  Ticket           | 15070
  Aktualisiert Von | wahnes at uni-koeln.de
  Zusammenfassung  | Timezone information of event is lost after sync. This
                   | causes problems with Android client.
  Warteschlange    | Kronolith
  Version          | 4.2.29
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


wahnes at uni-koeln.de (2021-05-23 20:38) hat geschrieben:

I've seen some trouble with timezone information in Kronolith/Horde as  
well, especially when trying to use an URL based on the "file"  
protocol for Horde's $conf['timezone']['location'] setting. I suppose  
the trouble you are having is accompanied with some messages stating  
"Unable to locate the tz database" in Horde's log files? At least  
that's what I have been seeing.

Unfortunately, I haven't been able to really pinpoint the issue. I'm  
tempted to say that using anything but the default
$conf['timezone']['location'] = 'ftp://ftp.iana.org/tz/tzdata-latest.tar.gz';
is causing trouble here, but that assessment may not be entirely correct.

Regarding your remark about granting internet access for said user and  
using the default timezone file download setting, I'd like to point  
out that Horde's caching mechanism seems to play a role here. When I  
tried to troubleshoot this, I got the feeling that my changes to  
settings for timezone location were simply ignored. As far as I can  
tell, it seems that setting a prefix for caching will help for changes  
to the timezone location setting to actually take effect. So maybe try  
something along the lines of
$conf['cache']['params']['prefix'] = 'test';
and retry the default timezone location setting. You can of course  
undo the prefix setting after a day or so; it's just meant to defeat  
Horde's caching of (unsuccessful) timezone file retrieval after  
changing the timezone location setting.