| Summary | horde_prefs loose display_remote_calenders, when accessing kronolith/fb.php |
| Queue | Kronolith |
| Queue Version | 4.2.27 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | christopher.etz (at) time2bi (dot) de |
| Created | 07/10/2019 (2189 days ago) |
| Due | |
| Updated | 12/23/2019 (2023 days ago) |
| Assigned | |
| Resolved | 12/23/2019 (2023 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
within the same session, or using the scheduling/attendees tab when
adding a new event.
Marking as not reproducible until steps to reproduce are provided.
Might have been solved by an intermediate upgrade.
Thanks for your effort trying to reproduce the behavior.
Cheers,
Christopher
Assigned to Michael Rubinsky
Priority ⇒ 1. Low
State ⇒ Not Reproducible
within the same session, or using the scheduling/attendees tab when
adding a new event.
Marking as not reproducible until steps to reproduce are provided.
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ horde_prefs loose display_remote_calenders, when accessing kronolith/fb.php
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
"unselected", whenever I access my free/busy information. The
free/busy information itself is correct, including information from
external calendars.
But when I re-login to the Horde web application, all previously
selected external calendars are unselected.
My suspect, that kronolith/fb.php is to blame, comes from logging the
SQL statement (in PostgreSQL) in parallel.
The problem arises probably from somewhere near line 31 of kronolith/fb.php:
$prefs =
$GLOBALS['injector']->getInstance('Horde_Core_Factory_Prefs')->create('kronolith',
array(
'cache' => false,
'user' => $user
));
This seems to create a new set of user preferences (with no external
calendars selected) and writes the "Unselection" of the external
calendars back to the table horde_prefs.
Unfortunately, my knowledge von PHP and the structure of the Horde
source code is not sufficient to locate and repair this misbehavior.
Regards,
Christopher