Summary | Importing event with category name > 80 char fails |
Queue | Kronolith |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | jan (at) horde (dot) org |
Requester | patrick.abiven (at) apitech (dot) fr |
Created | 04/04/2007 (6664 days ago) |
Due | |
Updated | 04/02/2008 (6300 days ago) |
Assigned | 03/14/2008 (6319 days ago) |
Resolved | 04/02/2008 (6300 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
Assigned to Jan Schneider
State ⇒ Resolved
would of course be possible to cut off the categories at 80 chars.
OTOH, how many people really do change the default SQL scheme that we
provide with Kronolith?
automatically.
Taken from Karsten Fourmont
State ⇒ Feedback
Queue ⇒ Kronolith
Assigned to Karsten Fourmont
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Importing event with category name > 80 char fails
Queue ⇒ Synchronization
State ⇒ Unconfirmed
In the kronolith_events table, the field event_category is defined as
VARCHAR(80). But in kronolith/lib/Driver.php, the setCategory()
function doesn't check the size of $category. So importing or
synchronizing events having a category name greater than 80 char fails
(DB Error: unknown error).
A workaround is to reduce the $category to 80 char.
Regards
Patrick