Headers already sent

[dotOne]

Hi,

Since I use a radius server for authentication our VPN clients (MOTP) the captive portal is not working anymore.
It looks like it tries to use radius authentication also.
The CP is configured to use vouchers but it looks like its trying to use radius anyway.

Warning: Cannot modify header information - headers already sent by (output started at /usr/local/captiveportal/radius_authentication.inc:191) in /usr/local/captiveportal/index.php on line 41 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/captiveportal/radius_authentication.inc:191) in /usr/local/captiveportal/index.php on line 42 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/captiveportal/radius_authentication.inc:191) in /usr/local/captiveportal/index.php on line 43 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/captiveportal/radius_authentication.inc:191) in /usr/local/captiveportal/index.php on line 44 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/captiveportal/radius_authentication.inc:191) in /usr/local/captiveportal/index.php on line 45 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/captiveportal/radius_authentication.inc:191) in /usr/local/captiveportal/index.php on line 77

How can I change this?

[dotOne]

To solve this I removed the line "require_once("radius.inc");" from the /etc/inc/captiveportal.inc

This disables the radius support for the captive portal but I don't need it anyway.
It's a crude way of going around the error but it's effective and quick.
Maybe it gets solved in the future.