Support » Plugin: Google Apps Login » This plugin seems to be calling wp_cron.php and getting a Header error

  • Resolved Norman Cates

    (@normancates)


    I’m getting this error in my logs:

    Warning: Cannot modify header information – headers already sent by (output started at /home/nzin2020/dev.nzin2020.nz/wp-cron.php:23) in /home/nzin2020/dev.nzin2020.nz/wp-content/plugins/google-apps-login/core/core_google_apps_login.php on line 452

    The error actually seems to think the problem comes from wp_cron.php at line 23

    fastcgi_finish_request();

    If I comment out that line, then the header problem goes away. So it seems to be an interaction with fast cgi and headers…

    Although my understanding is that wp_cron.php should NOT be being called by plugins.

    And if it is, then there’s a problem???

    I have checked for rogue spacing in wp_cron.php and it doesn’t exist.

    Any ideas on this?

    Thanks

Viewing 5 replies - 1 through 5 (of 5 total)
  • Bhavesh

    (@bhaveshinuscg)

    Hello Norman Cates,

    Greetings of the day!

    Thanks for sharing your concern with us. We will surely help you in this matter.

    Sorry for the inconvenience caused to you.

    As I can see you are facing an error Cannot modify header information:

    I would like to inform you that what you are facing a warning “header is already sent” this is just because of some plugin is conflicting with the Google Apps login.

    Some plugin is sending some information in the header before the Google Apps login send.

    We would like to suggest you please try to deactivate all other plugin and re-activate one by one simultaneously check your log file it helps you to find the plugin which plugin is conflicting with Google Apps login so you can simply close the header by writing a small code in the conflicting plugin.

    Sometimes the headers already sent error is caused by an extra space after closing the php?> tag, So I would like to request you please check the functions.php file of your WordPress active theme.

    Also, we would like to inform you that Warnings never stops any of your plugin’s functionality. if you are not very concern about warnings you can simply avoid by writing a small code to stop the warnings.

    I hope I was able to help you. If you need further assistance, or if you have any query please let me know I will be more than happy to assist you.

    Thanks & Regards,
    Bhavesh Akhade
    Sr. Solution Engineer

    NoseGraze

    (@nosegraze)

    For what it’s worth, I have the exact same problem.

    NoseGraze

    (@nosegraze)

    This looks like the exact same issue: https://wordpress.org/support/topic/php-warning-in-wp-cron/

    (Different plugin, but exactly the same problem.)

    Presumably adding an ! headers_sent() check to this conditional in ga_init() would fix the problem:

    if (!isset($_COOKIE[self::$gal_cookie_name]) && apply_filters('gal_set_login_cookie', true)) {
    

    I’ll test and find out.

    NoseGraze

    (@nosegraze)

    Yes this looks to have solved it:

    function ag_gal_set_login_cookie( $set_cookie ) {
            return ! headers_sent();
    }
    add_filter( 'gal_set_login_cookie', 'ag_gal_set_login_cookie' );
    

    I’d recommend the fix get added into the plugin properly though.

    Plugin Author levertechadmin

    (@levertechadmin)

    Hello @nosegraze

    Greetings from the WP-Glogin team!

    Thank you for your valuable time and suggestion.

    I will definitely forward your suggestion to our development team and I assured you they will look into this and fix this quickly.

    I really appreciate your work.

    Thanks & Regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.