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

[grac]

hi dan


> Is there an error message? 

besides the error messages i already sent? no.


> Can you try to run the create queries through 
> phpMyAdmin?

has never been a problem.
it's just another, brand new db in my webhoster's offer.
all other db's are working nicely.
just not with dam, as it seems.


> I haven't tested MySQL 5.1, and I would say it's most likely due to it, 
> but without a more concrete error message, I can't say.

that's the version my webhoster is offering.
so i had no complaints about that before.

therefore it must be the EXT dam, i think.

and it would explain why i have the same problems as before with another db.

that's very annoying.
and would make dam unusable for me?!

i wouldn't believe it.

stephan



> 
> Dan Osipov
> Calkins Media
> http://danosipov.com/blog/
> 
> grac wrote:
>> hello again
>>
>> after a total crash with a former version of dam and after having 
>> waited for the next stable version of dam 1.1.1 i tried to install it 
>> again - this time in a brand new installation and clean of typo3 4.2.5 
>> with templavoila and YAML (EXT dbttv).
>>
>> nothing else.
>>
>> everything went absolutely smooth - until i tried dam.
>>
>> nothing but error messages:
>>
>> about 20 times in the module "datei" (file):
>> Warning: mysql_num_rows(): supplied argument is not a valid MySQL 
>> result resource in /.../t3lib/class.t3lib_db.php on line 796
>>
>> three times in module "liste "(list):
>> Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL 
>> result resource in /.../t3lib/class.t3lib_db.php on line 809
>>
>> at least the error message in the module "info" was clear:
>> Table '....tx_dam' doesn't exist
>>
>> and the module "tools" again with two error messages:
>>
>> Warning: reset() [function.reset.php]: Passed variable is not an array 
>> or object in 
>> /.../typo3conf/ext/dam/modfunc_tools_indexupdate/class.tx_dam_tools_indexupdate.php 
>> on line 304
>>
>>
>> so i checked in the install tool/database analyser.
>> and right, there was a whole table which was not generated.
>> and fields in other tables that were not created as well.
>>
>> and could not be generated.
>> whatever i tried.
>>
>> MySQL version: 5.1.29-rc
>>
>>
>> so: who is to blame? the EXT or MySQL? or both?
>>
>>
>> thanks for any hints and help
>>
>> stephan