[kronolith] new install/database query issue

[Larry Weldon]

Quoting Larry Weldon <lweldon at weldoncomputers.com>:

> Quoting Larry Weldon <lweldon at weldoncomputers.com>:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>>
>>>
>>> Larry Weldon <lweldon at weldoncomputers.com> schrieb:
>>>
>>>> On Tue, 2012-03-06 at 17:36 +0100, Jan Schneider wrote:
>>>>> Zitat von Larry Weldon <lweldon at weldoncomputers.com>:
>>>>>
>>>>
>>>>> Does the administration interface give a green light for the
>>>> Kronolith
>>>>> database scheme?
>>>>>
>>>>
>>>> yes. Please see:
>>>> http://www.weldoncomputers.us/transfer/screen1.pdf
>>>>
>>>> I don't know what "Content 1.0.3" is...
>>>>
>>>> Thanks.
>>>>
>>>> --
>>>> Kronolith mailing list
>>>> Frequently Asked Questions: http://horde.org/faq/
>>>> To unsubscribe, mail: kronolith-unsubscribe at lists.horde.org
>>>
>>> Then there went something wrong while running the database    
>>> migration scripts, which hasn't been catched - unlikely.
>>> Or you have upgraded the database from an earlier H3 version, that  
>>>    wasn't uptodate before you upgraded to H4.
>>>
>>
>> Can I drop the horde database and expect the migration scripts will
>> create the database properly?
>>
>
> Since I hadn't heard anything I used mysql and "drop database horde;".
> I set the conf.php back to conf.php.dist and used the button "Update
> all configurations".
>
> I then receive this message:
>
> The configuration for horde cannot be updated automatically. Please
> update the configuration manually.
>
> Tell me where shall I go to create the database schema and why would
> the instructions be so difficult to find?
>
> Thanks.
>

I went back into mysql and after "create database horde;" the button  
to create the database schemas then appeared in the horde control box.  
I had to push it twice because a schema related to kronolith didn't  
get created properly, though it did the second time.

Also, Jan was correct - during my struggles to get a working database  
I had copied the old (old) (old) horde database in. That's what must  
have created the issue to begin - H4 couldn't update those schemas.  
Although I had started with an empty database before that which did  
not work - whatever it was I did wrong.

Thanks.


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.