Pb avec caractères spéciaux suite à migration 3.4 5.2.7
Envoyé par jeff2001
|
mardi 1 avril 2008 07:57:41 |
|
mardi 1 avril 2008 09:23:20 |
|
mardi 1 avril 2008 10:13:14 |
|
mardi 1 avril 2008 10:42:08 |
|
mardi 1 avril 2008 11:54:49 |
|
mardi 1 avril 2008 13:18:27 |
|
mardi 1 avril 2008 16:22:37 |
|
mercredi 2 avril 2008 02:50:39 |
"table_prefix" => "phorum",
Maurice Makaay
Phorum Development Team
my blog 
linkedin profile 
secret sauce
|
mercredi 2 avril 2008 03:10:59 |
|
vendredi 4 avril 2008 03:50:03 |
In English:
This says that you added some characters or white space / newline in front of the starting <?php in your config.php file. There should be nothing in front of that.
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
Citation
Warning: Cannot modify header information - headers already sent by (output started at /mnt/119/sdb/0/4/customriders/phorum/include/db/config.php:1)
This says that you added some characters or white space / newline in front of the starting <?php in your config.php file. There should be nothing in front of that.
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
|
vendredi 4 avril 2008 04:37:58 |
Hmm... did you possibly save the file in your editor as an UTF-8 file? UTF-8 files can contain some so called "byte markers" as the start of the file. Maybe these are throwing off your PHP. In that case, saving it as a plain ASCII file (or ISO-8859-1) should work (there are no special characters in this file to worry about, we just want it to not be UTF-8).
Another option would be to suppress output during the loading. For this, open your common.php file. Search fort he following piece of code:
This would effectively ignore any output that occurs from the config.php. It's not the nicest thing to do (since it's a hack that you have to redo when upgrading), but it might work for you.
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
Another option would be to suppress output during the loading. For this, open your common.php file. Search fort he following piece of code:
// Load configuration.
if (! include_once( "./include/db/config.php" )) {
Change it to:
// Load configuration.
ob_start();
$loaded = include_once( "./include/db/config.php" );
ob_end_clean();
if (! $loaded) {
This would effectively ignore any output that occurs from the config.php. It's not the nicest thing to do (since it's a hack that you have to redo when upgrading), but it might work for you.
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
|
vendredi 4 avril 2008 06:27:47 |
It's not the same problem. The problem now has moved to common.php, meaning that your editor broke that file too now. I am pretty sure that this editor adds a byte order marker (BOM) at the start of your PHP files, which is interpreted as output in the page because the file is included from other PHP code.
Upload a fresh common.php, forget about the hacks.
Then edit config.php to make it plain text. Here's an instruction that I found for Expression Web:
Another option would be to use a local editor like wordpad to create the file and then upload the edited file to the server.
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
Upload a fresh common.php, forget about the hacks.
Then edit config.php to make it plain text. Here's an instruction that I found for Expression Web:
Citation
To change the character encoding of a text file, open it in EW, right-click in the document pane, and choose "Encoding...". In the "Text File Encoding" dialog select e.g. "US/Western European (ISO)" from the _lower_ list, click "Save As..." and overwrite your existing file.
Another option would be to use a local editor like wordpad to create the file and then upload the edited file to the server.
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
|
vendredi 4 avril 2008 14:58:34 |
The config.php from that zip file (better edit your posting and delete the link, so you stop distributing your config.php!) is certainly in UTF. It does have the three byte order marker bytes before the <?php. It's not a plain text file. Maybe you can upload it from your local system using FTP, where you set the FTP transfer to ASCII instead of binary.
These three bytes are not visible in an editor, but they are really there. Viewed with the right program, the start of your config.php looks like this:
This file being saved as an UTF-8 file is the only problem and you keep walking into it, it seems.
Another problem for you will be that you use the charset "ANSI_X3.4-1968" in your language config file, which is (as the warnings that you've seen) is not supported by PHP. I don't know what type of charset that is, but you will have to edit your language file to set the HCHARSET variable to a PHP supported charset (e.g. ISO-8559-1).
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
These three bytes are not visible in an editor, but they are really there. Viewed with the right program, the start of your config.php looks like this:
<?
This file being saved as an UTF-8 file is the only problem and you keep walking into it, it seems.
Another problem for you will be that you use the charset "ANSI_X3.4-1968" in your language config file, which is (as the warnings that you've seen) is not supported by PHP. I don't know what type of charset that is, but you will have to edit your language file to set the HCHARSET variable to a PHP supported charset (e.g. ISO-8559-1).
Maurice Makaay
Phorum Development Team
my blog linkedin profile secret sauce
Seuls les utilisateurs enregistrés peuvent poster des messages dans ce forum.