passe tout en utf8

Delimiter //
Drop procedure if exists changecharset//

Create procedure changecharset ()
Begin
	Declare tname varchar(255) ;
	Declare done int default 0;
	Declare tc Cursor For
		Select TABLE_NAME From information_schema.TABLES Where TABLE_SCHEMA = schema();
	DECLARE CONTINUE HANDLER FOR SQLSTATE '02000' SET done = 1;

	Open tc;
	myloop: loop
		Fetch tc into tname;
		If done = 1 Then
			Leave myloop;
		End if ;
		Set @query = Concat('Alter Table `', tname, '` convert to character set utf8 collate utf8_swedish_ci;');
		PREPARE alterstmt FROM @query; 
		execute alterstmt ;
		Deallocate prepare alterstmt;
	End loop;

	close tc;
End //

Delimiter ;

Que dis l'encodage défini dans le php.ini ?

phpBB 2.0.x and PHP 5
by Stefan Koopmanschap » Sat Jul 17, 2004 7:22 am

With the recent release of the official version of PHP 5, people and hosts may be switching to the latest PHP version. At this moment, the phpBB Team does not officially support running phpBB on PHP 5, as phpBB2.0.x was not written with PHP 5 in mind. However, many users have reported using it sucessfully on PHP 5 having made a configuration change in PHP to enable support for the deprecated HTTP_*_VARS arrays which is turned off by default in new PHP 5 installations. The relevant configuration option is register_long_arrays and it is decribed in the PHP Manual. phpBB 2.0.x makes use of these arrays in order to maintain backwards compatibility with PHP 3.x and early versions of PHP 4.x which is part of the original specification.

For this reason we do not support PHP 5 as platform for phpBB. It has been reported working, so you can try it. It's a risk you will be taking though.

phpBB 2.2.x will have a miminum requirement of PHP 4.1.0 and so will not require this configuration change to be made.

Et ça converti aussi le texte ou juste la configuration de l'encodage ?
Car pour avoir testé via phpmyadmin pour mysql la conversion ne converti pas le texte et on se retrouve avec des ? ou des @! et compagnie. :/

Et ça converti aussi le texte ou juste la configuration de l'encodage ?
Car pour avoir testé via phpmyadmin pour mysql la conversion ne converti pas le texte et on se retrouve avec des ? ou des @! et compagnie. :/

Pour ma part cela m'a tout converti, n'hésite pas à l'utiliser tu pourra le constater