From: Xavier de P. <xav...@ub...> - 2010-09-10 11:30:24
|
Hi Torsten and Suzanne: Could you please add this information to some of the documetation pages, if you think that it's not covered there clearly enough? (I have no idea, and no time to do that myself) At least those of you who have discovered how to improve the upgrade process that for some reason it didn't work successfully with whatever default process you tried first. Thanks! Xavi Al 09/09/10 01:38, En/na Torsten Fabricius ha escrit: > Hi Suzanne and @ll, > > I got the solution for my problem and I think, that could solve yours > aswell. > Thank a lot to luciash - a lot of hugs!!! > > I had to adjust the db/local.php and before that. > Recently I did set the encoding of the db to utf8. > As I understood, from Tiki5 the latin encoding would not be supported > anymore. > > So Suzanne, please check, if your Database is set to utf8 - I would > say utf8-general or so ;-) > > If your dump from 3.x is using latin, that could be the first problem. > For a first running Tiki5 for testing purpose use 'tiki.sql' as dump > not to risk to import 'latin1' in an empty database. > Please read carefully: > http://doc.tiki.org/Manual+Installation > > Do not mind if that is still not working: > In my case it was - additionally - necessary to start the database > driver - luciash asked me if I would have adodb or pdo running as driver. > I still do not know, it must be the adodb. Anyway, he gave me those links: > http://tikiwiki.org/ReleaseNotes5.0 > http://tiki.org/ReleaseNotes40 > > In my case (*Unix/Linux* Server) I had to add the following line to > the end *db/local.php*: > *$api_tiki='adodb';* > > For *Windows *use instead in the *php.ini* file: > *extension=php_pdo_mysql.dll* > > (and without anything else than PHP in this document you will *not need*: > *?> * > > So the *db/local.php* COULD look like the following code, to > (hopefully) work with Tiki5: > > <?php > $db_tiki='mysql'; > $dbversion_tiki='5.0'; > $host_tiki='localhost:/tmp/mysql5.sock'; //or// > $host_tiki='localhost'; > $user_tiki='DATABASEUSERNAME'; > $pass_tiki='PASSWORD'; > $dbs_tiki='DATABASENAME'; > *$client_charset='utf8'; > $api_tiki='adodb';* > > $client_charset='utf8'; seems to be optional - I have it in the file > and it works. > > $host_tiki='localhost:/tmp/mysql5.sock'; is specific for 1und1.de and > perhabs for 1and1.com. > 1und1.de (not necessarily rootserver, but managed server and > mostlikely virtual hosting) requires two steps of manual installation, > before finishing with the tiki-installer. > If anybody has issues with 1und1.de, please contact me. > This company did help me very intensive to get Tiki running there and > I promised to give the appropriate informations back to the community > ;-) . 1und1.de is not tikiunfriendly anymore :-) . > > If still not working, please also check > www.yourdomain.dns/tiki-phpinfo.php > <http://www.yourdomain.dns/tiki-phpinfo.php> to get the Version of PHP > - there are issues with 5.3.0 > > Anyway, try the above and please write back, weather it worked or not, > e.g. what worked and what worked not. > > Sincerely, > Torsten > > Am 08.09.2010 22:54, schrieb Torsten Fabricius: >> Hi Suzanne and @ll, >> >> I have a similar problem since a while. It did cost me two days together >> with one of my project-members and we did not solve it. >> Tonight I go to Berlin and will try to get there to get Tiki5 running on >> our productive server (1und1.de - manged) >> >> On our projectserver (all-inkl.de - vitual) I got a Tiki5 make running. >> >> I learned, that this might have something to do with utf8 encoding since >> there have been made changes to Version 5 of Tiki, that makes rules >> stronger and Tiki will not work any more with latin encoding. >> >> What I did read about that in the docs make sense ... >> ... but I do not understand the problem at 1und1.de (and other >> providers?), because: >> >> - 3.x is running absolutely fine on 1und1.de >> - I have access to PHPmyAdmin >> - 1und1.de uses utf8 in all variations >> - even the transfer of the database from all-inkl to 1und1 does not make >> Tiki5 work on 1und1.de, even using the proper working DB from >> all-inkl.de (sure, the dump of it and yes, it is mysql5 aswell) >> - manual installation did not work >> - the db-transfer from all-inkl.de to 1und1.de did work with Tiki3.x >> databases a couple of times BUT NOT with Tiki5 Database (Tiki5.1? not sure) >> >> Depending what I tried, I recieve the same or similar error messages as >> Suzanne. >> Anyway, Tiki5 and DB are not connecting on our needed managed productive >> system at 1und1.de >> That means, I cannot go ahead withe our hole project right now. But need >> to release soon. Big pressure now for me ;-) . >> >> So is this a Tiki or a provider problem? >> Who can help? >> >> I need to present our project at 26 th of September and I need to learn >> Workspaces and all that for our project and somehow for the community >> (have been asked and promised to do some job here aswell). >> >> I think this has to be sorted generally (not only for "my" 1und1.de). >> So who has the appropriate knowledge for that problem? >> I will be in Berlin from tomorrow morning (working with one of my Admins >> from Thursday early afternoon till Friday early afternoon) then I will >> stay till about Sunday to meet some people. >> >> => Who wants to join? Perhabs in Berlin or via internet? >> >> => Generally the next couple of weeks it would be easy meet me in >> Würzburg, Frankfurt or Karlsruhe, as I switch between WÜ and KA at least >> once every week. >> >> Sincerely, >> Torsten >> >> >> Am 06.09.2010 13:10, sch...@vi...: <mailto:PRS...@vi...:> >> >>> Hi all, >>> >>> I have a 3.0 tiki and wanted to do a fresh install of 5.1 and import my old >>> 3.0 db. I have problems with the db. >>> >>> I installed tiki 5.1 *locally* (xampp) successfully and exported my >>> excisting 3.0 db (followed thehttp://doc.tikiwiki.org/Backup instructions). >>> Couldn't import it because it was to big so I used bigdump.php. >>> Bigdump aborted because I had "extended inserts" checked when exporting. I >>> had to uncheck this and do an export again. >>> >>> So I did and bigdump started the import. >>> It crashed on 2 images and a pdf (content) so, with ultra-edit I removed the >>> "corrupt" insert records. >>> >>> Everything went fine, the db imported successful. I upgraded the database to >>> 5.1 also successful, but when I try to open tiki, I get the following error: >>> >>> **** >>> An error occured while performing the request. >>> >>> Things to check: >>> >>> 1. >>> >>> Did you complete the Tiki Installer? >>> 2. >>> >>> Is your database corrupt? Please see how to repair your database >>> 3. >>> >>> Are your database credentials accurate? (username, database name, etc >>> in db/local.php) >>> **** >>> >>> 1) yes, I did, went thru all the steps >>> 2) don't know, so in phpadmin I 'repaired' all tables >>> 3) looks ok >>> >>> >>> So, what to do? I was thinking about exporting just a few tables to see what >>> happens? What would be the best tables to try then? >>> Or.... does anyone have a better suggestion? >>> >>> Suzanne >>> > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > > > > _______________________________________________ > Tikiwiki-users mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-users > |