WordPress.org

Ready to get started?Download WordPress

Forums

WP Super Cache
[resolved] PHP error when replying to a comment - weird (8 posts)

  1. Martin
    Member
    Posted 1 year ago #

    This is most weird so any help in being able to track it down would be fantastic.

    I get the following error when replying to an existing comment.

    Warning: extract() [function.extract]: First argument should be an array in /home/rastarr/public_html/gajwp/wp-includes/pluggable.php on line 216
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/rastarr/public_html/gajwp/wp-includes/pluggable.php:216) in /home/rastarr/public_html/gajwp/wp-includes/pluggable.php on line 881

    Making comments seems to be fine but not when replying to a comment.

    Here's the debug snippet of the activity relating to the event, in case it actually highlights something that I don't understand:

    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome supercache dir: /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome/
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome No wp-cache file exists. Must generate a new one.
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome In WP Cache Phase 2
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Setting up WordPress actions
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Created output buffer
    02:26:24 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:26:29 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Output buffer callback
    02:26:29 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:26:29 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:26:29 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Not caching for known user.
    02:26:29 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Cache is not enabled. Sending buffer to browser.
    02:26:29 /top-4-reasons-han-solo-suffered-bad-boy-syndrome wp_cache_shutdown_callback: collecting meta data.
    02:26:29 /top-4-reasons-han-solo-suffered-bad-boy-syndrome Did not write meta file: wp-cache-6feb3b18bd457e758c305faf6c2018db.meta ** *1* *1*
    02:27:19 /top-4-reasons-han-solo-suffered-bad-boy-syndrome?replytocom=2821 Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:27:19 /top-4-reasons-han-solo-suffered-bad-boy-syndrome?replytocom=2821 Non empty GET request. Caching disabled on settings page.
    02:27:20 /top-4-reasons-han-solo-suffered-bad-boy-syndrome?replytocom=2821 Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:27:20 /top-4-reasons-han-solo-suffered-bad-boy-syndrome?replytocom=2821 In WP Cache Phase 2
    02:27:20 /top-4-reasons-han-solo-suffered-bad-boy-syndrome?replytocom=2821 Setting up WordPress actions
    02:28:11 /wp-admin/admin-ajax.php?action=blc_dashboard_status&random=0.05839749818979989 Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:28:11 /wp-admin/admin-ajax.php?action=blc_dashboard_status&random=0.05839749818979989 Non empty GET request. Caching disabled on settings page.
    02:28:12 /wp-admin/admin-ajax.php?action=blc_dashboard_status&random=0.05839749818979989 Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:28:12 /wp-admin/admin-ajax.php?action=blc_dashboard_status&random=0.05839749818979989 In WP Cache Phase 2
    02:28:12 /wp-admin/admin-ajax.php?action=blc_dashboard_status&random=0.05839749818979989 Setting up WordPress actions
    02:29:36 /wp-comments-post.php Cookie detected: wordpress_logged_in_339368835c8dcfba64887c27db9280e0
    02:29:36 /wp-comments-post.php In WP Cache Phase 2
    02:29:36 /wp-comments-post.php Setting up WordPress actions
    02:29:36 /wp-comments-post.php Not caching POST request.
    02:29:37 /wp-comments-post.php wp_cache_post_edit: Clearing cache for post 7778 on post edit.
    02:29:37 /wp-comments-post.php wp_cache_post_change: comment detected. only deleting post page.
    02:29:37 /wp-comments-post.php supercache dir: /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome/
    02:29:37 /wp-comments-post.php wp_cache_post_id_gc post_id: 7778 http://www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome clearing cache in /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome/.
    02:29:37 /wp-comments-post.php prune_super_cache: wp_cache_rebuild_or_delete( /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome/index.html.gz )
    02:29:37 /wp-comments-post.php rebuild_or_gc: rename to /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome/index.html.gz.needs-rebuild
    02:29:37 /wp-comments-post.php prune_super_cache: wp_cache_rebuild_or_delete( /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome/index.html )
    02:29:37 /wp-comments-post.php rebuild_or_gc: rename to /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome/index.html.needs-rebuild
    02:29:37 /wp-comments-post.php wp_cache_post_id_gc clearing cache in /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com/top-4-reasons-han-solo-suffered-bad-boy-syndrome//page/.
    02:29:37 /wp-comments-post.php wp_cache_post_id_gc clearing cache in /home/rastarr/public_html/gajwp/wp-content/cache/supercache/www.geekandjock.com//page/.
    02:29:37 /wp-comments-post.php wp_cache_post_edit: draft post, not deleting any cache files.
    02:29:37 /wp-comments-post.php wp_cache_post_edit: draft post, not deleting any cache files.
    02:29:37 /wp-comments-post.php wp_cache_post_edit: draft post, not deleting any cache files.
    02:29:37 /wp-comments-post.php wp_cache_post_change: Already processed post 7778.
    02:29:37 /wp-comments-post.php Post 7778 changed. Update cache.
    02:29:37 /wp-comments-post.php wp_cache_post_change: Already processed post 7778.

    Even more odd is that the reply is processed and enters the comment stream for the site. An email is sent using the plugin Comment Reply Notification as well.

    The error line in pluggable.php is pointing to wp_mail code:

    extract( apply_filters( 'wp_mail', compact( 'to', 'subject', 'message', 'headers', 'attachments' ) ) );
    and line 881 points to the line:
    header("Location: $location", true, $status);
    in this function:

    if ( !function_exists('wp_redirect') ) :
    /**
     * Redirects to another page.
     *
     * @since 1.5.1
     * @uses apply_filters() Calls 'wp_redirect' hook on $location and $status.
     *
     * @param string $location The path to redirect to
     * @param int $status Status code to use
     * @return bool False if $location is not set
     */
    function wp_redirect($location, $status = 302) {
    	global $is_IIS;
    
    	$location = apply_filters('wp_redirect', $location, $status);
    	$status = apply_filters('wp_redirect_status', $status, $location);
    
    	if ( !$location ) // allows the wp_redirect filter to cancel a redirect
    		return false;
    
    	$location = wp_sanitize_redirect($location);
    
    	if ( !$is_IIS && php_sapi_name() != 'cgi-fcgi' )
    		status_header($status); // This causes problems on IIS and some FastCGI setups
    
    	header("Location: $location", true, $status);
    }
    endif;

    Any ideas anyone ... anyone?
    Martin

    http://wordpress.org/extend/plugins/wp-super-cache/

  2. Keije
    Member
    Posted 1 year ago #

    Do you have wysija newsletter plugin installed? Deactivating it solved the problem for me

  3. Martin
    Member
    Posted 1 year ago #

    Oh NO!!!
    Really? Yes, I do use Wysija and that's unfortunate too. Thank you for your reply. I'll check that out and ping the Wysija guys.

  4. Martin
    Member
    Posted 1 year ago #

    Yep, seems the current Wysija version is the cause. Logged a support ticket with them to get to the bottom of all this.

  5. BK
    Member
    Posted 1 year ago #

    I had the exact same problem and disabling Wysija fixed it too, which is disappointing because I really liked the plug-in and had big plans for it. I will try to go submit a trouble ticket with them as well so they will know yours was not an isolated incident. Thanks! Your post just saved me a boatload of time troubleshooting!

  6. Martin
    Member
    Posted 1 year ago #

    I just got a reply to my own support ticket, BK
    Apparently this is already fixed and was only evident in the initial release of their 2.15 code so only initial updaters to that version should be affected.

    No idea why they don't issue a point release update so people like us can get fixed up.

    Anyway, they recommend deleting the plugin folder and reinstalling. I haven't done this yet so unable to report on that.

  7. Martin
    Member
    Posted 1 year ago #

    Confirmed. Reinstalling to the latest v2.15 solved this error, for me.

  8. BK
    Member
    Posted 1 year ago #

    Heard back from them as well. Worked for me too! WooHoo!

    Thanks so much!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags