[TYPO3-4-3] indexed search installation warnings/errors

[Leander Seige]

Hello Xavier,

> Have a look at proposed changes to be made on your database, at the
> beginning of the page, there's likely something you miss to create in
> database. If you have DBAL though, the changes that are proposed is to
> change the ENGINE to InnoDB because DBAL fails to return the engine that
> is used when you use for instance a native (=MySQL) database but have
> DBAL installed for external tables.

No, I don't have DBAL (if you are referring to the "dbal" extension).

When creating the tables during install everything goes well. I even 
copied every single sql statment to phpmyadmin to doublecheck, but no 
errors occur. Then I changed all tables to InnoDB (most of already have 
been InnoDB) w/o problems. Later I changed everything to MyISAM but the 
extension wanted to change back to InnoDB, I did so.
But the error message

* Database status:      Table error!
Probably one or more required fields/tables are missing in the database!

doesn't go away...

Thanks for your answer btw

Leander





>
> There's "nothing" to do with this bug.
>
>> * Code warnings:
>> (developer-relevant) Some tables or fields are of wrong type!
>> No XCLASS inclusion code found in file "class.doublemetaphone.php".
>> No XCLASS inclusion code found in file
>> "hooks/class.tx_indexedsearch_tslib_fe_hook.php".
>
> Confirmed.
>
>> * A difference between the originally installed version and the current
>> one was detected!
>>
>> Modified files:
>> modfunc1/class.tx_indexedsearch_modfunc1.php
>> modfunc2/class.tx_indexedsearch_modfunc2.php
>
> Confirmed.
>
>> people on the IRC suggested that these messages might by just warnings.
>> Is it ok to ignore these or should I care about them?
>> If so, what can I do? "Compare"ing the DB from the install tool doesnt
>> help.
>
> Could you please report a bug in bugtracker [1] by selecting
> indexed_search (sub-)project in the right drop-down with the 2 warnings
> I confirmed? We'll fix that for next releases of TYPO3.
>
> In the meantime, you may silently ignore those warnings. There's really
> nothing to worry about. Just make sure you don't have anything to do
> with your DB schema.
>
> Regards
>
> [1] http://bugs.typo3.org
>