[TYPO3-dam] brand new typo3 installation & DAM: only error messages

[Dan Osipov]

 > i have checked the ext_tables.sql.
 > all fields in be_grous, be_users and tt_content are initialised.
 > also the tables
 > - tx_dam_cat
 > - tx_dam_mm_cat
 > - tx_dam_metypes_avail
 > - tx_dam_mm_ref
 > - tx_dam_log_index
 > - tx_dam_file_tracking
 > - tx_dam_selection
 >
 > but just not tx_dam itself.

That tells me there might be an issue with MySQL having a problem with a 
definition of that table. In that case there might be an error it throws 
when it tries to create that table. Without the detailed error message, 
its tough to debug (I would have to mimick your install to reproduce the 
error).

I know that MySQL 5.1 is a fresh release, and hasn't been battle tested. 
It's odd for your hosting to upgrade to it...

Dan Osipov
Calkins Media
http://danosipov.com/blog/

grac wrote:
> hi martin
> 
> Martin Holtz wrote:
>> sometimes it can happen, that you include extensions in the wrong order
> 
> what do you mean by wrong order?
> there is nowhere any hint of a necessary installation order of the EXT.
> 
> i remember from my former catastrophe that someone suggested to install 
> dam before templavoila.
> was of no use at all.
> 
>> and the tx_dam would probably created not from tx_dam. If you install
>> after that tx_dam, it can lead to such errors.
> 
> and what would you suggest? remember: it's a brand news installation.
> 
> 
>> if tx_dam doesnt exists, try to create it by hand.
> 
> i am an ordinary admin, not a developer.
> and therefore hesitate to fiddle around with the database itself.
> on the other hand i would expect an EXT to work well with others.
> not true?
> 
> 
>> in the extension folder there should be an *.sql file with create
>> statements.
> 
> i have checked the ext_tables.sql.
> all fields in be_grous, be_users and tt_content are initialised.
> also the tables
> - tx_dam_cat
> - tx_dam_mm_cat
> - tx_dam_metypes_avail
> - tx_dam_mm_ref
> - tx_dam_log_index
> - tx_dam_file_tracking
> - tx_dam_selection
> 
> but just not tx_dam itself.
> 
> 
> 
>>
>> perhaps that helps,
>>
>> martin
>>
>>
>>
>