php warnings on login

[palgrave]

I have vbulletin integrated with phpfox, and when you login via vbulletin the following warnings appear briefly:

Warning: Cannot modify header information - headers already sent in /home/palgrave/public_html/include/modules/Account/classes/PhpFox_ServiceSecurity.class.php on line 231

Warning: Cannot modify header information - headers already sent in /home/palgrave/public_html/include/modules/Account/classes/PhpFox_ServiceSecurity.class.php on line 232

Warning: Cannot modify header information - headers already sent in /home/palgrave/public_html/include/modules/Account/classes/PhpFox_ServiceSecurity.class.php on line 235

Warning: Cannot modify header information - headers already sent in /home/palgrave/public_html/include/modules/Account/classes/PhpFox_ServiceSecurity.class.php on line 236

Warning: Cannot modify header information - headers already sent in /home/palgrave/public_html/include/modules/Account/classes/PhpFox_ServiceSecurity.class.php on line 237

Warning: Cannot modify header information - headers already sent in [path]/includes/functions_login.php(288) : eval()'d code on line 14

Warning: Cannot modify header information - headers already sent in [path]/includes/functions_login.php(288) : eval()'d code on line 1

When you login via phpfox everything is ok.

Anybody know what's going on?

[Steve Machol]

That is a problem with your add-on. You will need to ask about this in the appropriate thread for that add-on over at www.vbulletin.org.

[calorie]

That looks like there might be extra white space before the <?php or after the ?> in one of the add-on's files, or some code is sending output to the browser before the headers are sent, hence the error message.

[palgrave]

That is a problem with your add-on. You will need to ask about this in the appropriate thread for that add-on over at www.vbulletin.org.

I wasn't sure as most of the warnings refer to phpfox files, but the last 2 refer to a vbulletin file, so I asked at phpfox forums too. Registering at .org now.

That looks like there might be extra white space before the <?php or after the ?> in one of the add-on's files

Not in the file referred to in the warnings, but haven't checked them all.

some code is sending output to the browser before the headers are sent, hence the error message.

Wouldn't know where to start with that one.

[Steve Machol]

That last two eval() errors are also due to your add-on.