gizmo21

Ich habe eine Frage zum mambo_4.5.2_stable.zip/germanf.zip ( 4.5.2
2005-02-17) Modul.

Ich wollte in der germanf.php (Rechte 744) eine Zeile ändern
da mir der Ausdruck nicht gefällt. Sobald ich jedoch auch nur einen Buchstaben ändere erhalte ich über meiner regulären Seite eine Fehlermeldung.

Die Zeile ist: DEFINE('_CONTACT_DOWNLOAD_AS','Download Information als eine');

Kann mir da einer weiterhelfen ?

btw. keine blank lines in configuration.php und solange ich nichts in der germanf ändere geht es auch.


mambo 4.5.2
Template AkoAutumnFog

gizmo21

gelöst:
es waren nicht die leer zeilen am ende der configuration.php sondern in der germanf.php nach der änderung die die probleme brachten. also nach änderung der germanf.php einfach alles löschen was nach '?>' erscheint.

Sabra

Hi,

This is a POSSIBLE solution:

1) open germanf.php and ....site/index.php in notepad, or even better in cpanel file editor.
2) go to the VERY end of the file(s) and delete every blank space AFTER the closing php tag (?>)
3) save the file(s).
4) try again.

I see that we posted at the same time.
If only I could understand what you say :-)

klinkhart

Hmmmm did not work for me...May problem ist that I accidentally dropped the danish.php after a change with an editor in the "root", believing I was in "languages" directory. After calling the site it gave me the following:

09:54 05.04.2005
Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/wyk/language/danish.php:1) in /www/htdocs/wyk/includes/mambo.php on line 711

Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/wyk/language/danish.php:1) in /www/htdocs/wyk/index.php on line 211

Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/wyk/language/danish.php:1) in /www/htdocs/wyk/index.php on line 212

Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/wyk/language/danish.php:1) in /www/htdocs/wyk/index.php on line 213

Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/wyk/language/danish.php:1) in /www/htdocs/wyk/index.php on line 214

Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/wyk/language/danish.php:1) in /www/htdocs/wyk/index.php on line 215

However, line 711 in mambo.php is about cookies and the lines in index.php do not give me a clue since i did not change them and they read lie this:

header( 'Expires: Mon, 26 Jul 1997 05:00:00 GMT' );
header( 'Last-Modified: ' . gmdate( 'D, d M Y H:i:s' ) . ' GMT' );
header( 'Cache-Control: no-store, no-cache, must-revalidate' );
header( 'Cache-Control: post-check=0, pre-check=0', false );
header( 'Pragma: no-cache' );

Any ideas anybody?

Grateful...

klinkhart

klinkhart

Aaaaaaarghhh.... Was für ein Idiot ich bin. Aus irgenwelchen Gründen stand vor <?php ein Datum samt Uhrzeit...Also nicht nur nach Leerzeichen/Leerzeilen Suchen, sondern auch nach so einem Quatsch!

Danke an alle, die mich mit der Fährte Leerzeichen/-Zeilen erst auf die Idee gebracht haben, mal genau zu gucken...

klinkhart

xjessie007

I had a problem with the "headers already sent" too at my http://www.maxi-pedia.com website. In my case, it was caused by a blank line at the beginning of one *.inc file. PHP seems to have problems with extra spaces here and there.

Check all your *.inc files to make sure you do not have closing ?> in any of them. Closing ?> is not needed in your *.inc files. Check all your *.php files to make sure you do not have blank lines at the beginning or at the end.

If you are working in a CMS, then it may be caused by some module, disable your modules one by one to find out which one causes this.

This can also be caused by UTF-8. If you have your website coded in ASCII and are saving your php files as UTF-8, it can cause this message. If your website and DB are UTF-8, you should be ok with saving php files as UTF-8 though.

Btw, this error message is related to output_buffering on/off in your php.ini. If you have output_buffering set to some cache, the server will allow to send headers with delay (or to modify them shortly after they are sent), and this error will not be tripped. But if you set output_buffering to 0 or not at all, then headers can be sent at only one moment, and if you have some bad code, it will trip this error message.