Error msg when trying to login

[reallybites]

i get this error msg when i try to login to pixelpost.


Warning: Cannot modify header information - headers already sent by (output started at /home/bites/public_html/fotolog/includes/pixelpost.php:50) in /home/bites/public_html/fotolog/admin/index.php on line 125

whats up?

[Connie]

This message mostly means that some code, which does not belong there, is sent to the browser

1) possible reasons:
mostly this happens because ASCII-files are transported by FTP in BINARY mode to the server

check that and re-upload in ASCII-mode (not AUTOMATIC or BINARY)

2) did you edit the index.php?????

If yes, maybe you left some code there

I bet it is reason #1
give it a try!

[reallybites]

Oh but i have been using pixelpost for about 7 months already.

I never had to login all these while (logins saved),but recently i used a different OS,so i have to login.And i found out that i couldnt'.

The photoblog is working fine (fotolog.reallybites.net)

Just that i cant login.

If i were to reupload,which files should i re-upload?

[Connie]

are cookies allowed at that other PC?

if you did not change anything, just use another computer, check the following:

- empty browser cache
- delete all cookies

- check the security- options of that PC:
- are cookies allowed

maybe that will help

[reallybites]

Nope it didnt work.I upgraded to 1.4.2,and i still get the same error msg.


Warning: Cannot modify header information - headers already sent by (output started at /home/bites/public_html/fotolog/includes/functions.php:187) in /home/bites/public_html/fotolog/admin/index.php on line 127

If i do a clean install,can i preserve my images?

[raminia]

I don't think with a new install you will gain anything.

[reallybites]

then what do you suggest I do? Install a new pixelpost and start all over again?

[raminia]

you have some extra spaces at the end (or at the top) of functions.php or pixelpost.php or some other file. (before <?php or after ?> tags!)

if you edit the pixelpost.php with a bad unicode editor you will get the same behavior. edit it with notpade if you are using windows and choose save as and then set the encoding to be ANSI.

[reallybites]

solved it.turned out there were some space left after the <? in functions.

thanks a lot!

[raminia]

solved it.turned out there were some space left after the <? in functions.

thanks a lot!
sometimes simple solution work and sometimes big problem came from simple faults;)

glad that it works now.