[TYPO3] seriuos problem migrating 4.2.1 installtion to another server

G.Unger skyfreak1 at gmx.net
Tue Aug 26 19:51:32 CEST 2008


hi list

everything on hold
here is sth rally going wrong, it looks like the dumps the customer 
made and provided me with are corrupt!

I insested to get shell access and pack everything again, dump 
everything on my own and test it again.

rgds
GUIDO





On 2008-08-26 19:12:48 +0200, G.Unger <skyfreak1 at gmx.net> said:

> hi dimitry
> 
> thx for popping in on this one!
> 
> although I do not consider myself expert/advanced TYPO3 user, the way 
> of moving (dumping files and DB + modifying localconf.php) is the way 
> that always forked for me.
> 
> strange enough, that a new install of T3 4.2.1 workz even with umlaute 
> in TS. I can move it online as I always do, make changes (more umlaute 
> in TS) and dump it back to my local machine.
> 
> coming back to the problem:
> 
> how do I set
> 
>> SET NAMES utf8
>> SET character_set_server utf8
> 
> in install tool? there is only one input field and no more textarea 
> showing up in install tool of 4.2.1 no textarea to insert 2 seperate 
> lines.
> 
> I tried inserting them comma seperated and even with a semicolon, 
> nothing worked.
> than I tried to insert it manually in the localconf.php like
> 
> $TYPO3_CONF_VARS['SYS']['setDBinit'] = 'SET NAMES utf8'.chr(10).'SET 
> character_set_server utf8';
> 
> no success either, apart that in install tool the field ['setDBinit'] 
> vanished completely.
> 
> I am really helpless on this one, sorry.
> tried an export from T3 backend as well, apart of a couple of files 
> beeing too big from user_upload folder (zips with more than 1MB) the 
> export and import worked. Yet the error persists :(
> 
> 
> rgds,
> GUIDO
> 
> 
> 
> 
> 
> 
> 
> On 2008-08-26 17:21:00 +0200, "Dmitry Dulepov [typo3]" <dmitry at typo3.org> said:
> 
>> Hi!
>> 
>> G.Unger wrote:
>>> - client made a complete download of all files and folders by ftp from 
>>> the online development server
>>> - database was exported/dumped by phpMyAdmin extension. looking in the 
>>> sql file I see that charset is utf-8 and collation as well
>> 
>> Next time use import/export inside TYPO3. File copying and SQl import 
>> is better for advanced TYPO3 users.
>> 
>>> where do I go wrong?
>> 
>> It seems that you did not set db init commands in Install tool. Set them to:
>> 
>> SET NAMES utf8
>> SET character_set_server utf8
>> 
>> You will need to clear page cache after that.




More information about the TYPO3-english mailing list