[kronolith] Kronolith H4 (3.0-ALPHA1)

[lst_hoe02 at kwsoft.de]

Zitat von Michael Rubinsky <mrubinsk at horde.org>:

> Quoting lst_hoe02 at kwsoft.de:
>
>> Zitat von Jan Schneider <jan at horde.org>:
>>
>>> Zitat von lst_hoe02 at kwsoft.de:
>>>
>>>> Zitat von Jan Schneider <jan at horde.org>:
>>>>
>>>>> The Horde Team is pleased to announce the first alpha release of  
>>>>>  the  Kronolith
>>>>> Calendar Application version H4 (3.0).
>>>>>
>>>>> Kronolith is the Horde calendar application. It provides  
>>>>> web-based  calendars
>>>>> backed by a SQL database or a Kolab server. Supported features    
>>>>> include Ajax and
>>>>> mobile interfaces, shared calendars, remote calendars,  
>>>>> invitation  management
>>>>> (iCalendar/iTip), free/busy management, resource management,   
>>>>> alarms,  recurring
>>>>> events, and a sophisticated day/week view which handles  
>>>>> arbitrary  numbers of
>>>>> overlapping events.
>>>>>
>>>>> IMPORTANT! This is a preview version that should not be used on  
>>>>> production
>>>>> systems. This version is considered feature complete but there  
>>>>> are   likely to be
>>>>> bugs. You should not use this preview version with existing production
>>>>> data. Migration of data from earlier versions has not been fully  
>>>>>   tested yet and
>>>>> is not supported.
>>>>>
>>>>> We encourage widespread testing and feedback via the mailing  
>>>>> lists  or our bug
>>>>> tracking system. Updated translations are very welcome, though  
>>>>> some strings
>>>>> might still change before the release candidates are prepared.
>>>>>
>>>>> To install Kronolith, you need to install Horde first. See
>>>>> https://github.com/horde/horde/blob/master/horde/docs/INSTALL  
>>>>> for   details. Once
>>>>> Horde is installed, you can install Kronolith with the following command:
>>>>>
>>>>> pear install horde/kronolith-alpha
>>>>
>>>> After configuring i got the following:
>>>>
>>>> SQLSTATE[42P01]: Undefined table: 7 FEHLER: Relation   
>>>> »rampage_types«  existiert nicht LINE 1: SELECT type_id,  
>>>> type_name  FROM "rampage_types"  WHERE type_na... ^
>>>>
>>>> What am i missing?
>>>
>>> The next step. Creating the DB schemas.
>>
>> That would be too easy. I tried with Horde configuration panel and   
>> with "db_migrate kronolith". Both tell me all is well and in fact  
>> some  kronolith_* tables are created but obviously not all needed?
>
> It's a required dependency, so it was probably installed, but just  
> in case - did the Content application get installed and did you run  
> the migration for *that* application?

Not sure how to check. I installed kronolith with "pear install -a  
horde/kronolith-alpha" because of the problems without "-a" at horde  
install, so it should be installed no?
Migration for that application would be "db_migrate content" ? I don't  
see it in the Horde configuration list but "pear install -a  
horde/content-alpha" tell it is installed...

Regards

Andreas


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6046 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/kronolith/attachments/20110311/9c4b8299/attachment.bin>