Forum Replies Created

Viewing 1 replies (of 1 total)
  • Thread Starter steven1350

    (@steven1350)

    I am not to sure about your answer here.

    Looking at the plugins source code, it looks like the wp_redirect() is set to trigger on the WordPress login_head action, which is after WordPress has begun to output the HTML headers (hence triggering the error). Looking at the page source above the warning also agrees with this idea (the <html> and <head> tags are present, which should never happen when using wp_redirect())

    Here is the stack trace if it helps

    ( ! ) Warning: Cannot modify header information - headers already sent by (output started at /var/www/multisite-wordpress/wp-login.php:63) in /var/www/multisite-wordpress/wp-includes/pluggable.php on line 1174
    Call Stack
    #	Time	Memory	Function	Location
    1	0.0001	122512	{main}( )	../wp-login.php:0
    2	0.1260	3549636	login_header( )	../wp-login.php:891
    3	0.1292	3560012	do_action( )	../wp-login.php:98
    4	0.1333	3569548	call_user_func_array ( )	../plugin.php:524
    5	0.1333	3569620	WP_Plugin_Authorizer->login_head_maybe_redirect_to_cas( )	../plugin.php:524
    6	0.1337	3576688	wp_redirect( )	../authorizer.php:1921
    7	0.1340	3581828	header ( )	../pluggable.php:1174
    • This reply was modified 9 years, 1 month ago by steven1350.
    • This reply was modified 9 years, 1 month ago by steven1350. Reason: typo
Viewing 1 replies (of 1 total)