Forums

[Plugin: WP-o-Matic] Warning: gzuncompress() [function.gzuncompress]: data error (7 posts)

  1. diondev
    Member
    Posted 2 years ago #

    I keep getting the error:

    Warning: gzuncompress() [function.gzuncompress]: data error in /home/user/public_html/site/wp-includes/http.php on line 1792

    When fetching posts. How do I fix this?

  2. tiggsy
    Member
    Posted 2 years ago #

    Yes, I keep finding this in the error logs as well.

  3. tiggsy
    Member
    Posted 2 years ago #

    I also am getting this. I've found a fix for the same bug on a plugin, and that was fixed by changing the BLOB field on the plugin's table to a MEDIUMBLOB. However, I don't know which field it would be, or even if it's the same problem. It seems to be WordPress itself (the bug is in the file http.php), not a plugin.

  4. tiggsy
    Member
    Posted 2 years ago #

    I'm trying this:

    find the function decompress( $compressed, $length = null ) {
    in the file wp-includes/http.php and comment out these lines:

    `$decompressed = gzinflate( $compressed );

    if ( false !== $decompressed )
    return $decompressed;

    $decompressed = gzuncompress( $compressed );

    if ( false !== $decompressed )
    return $decompressed;`

    (you do this by putting /* at the beginning and */ at the end)

    If I don't come back in a week to say it failed, then it worked!!

  5. asuservice
    Member
    Posted 2 years ago #

    Thanks Tiggsy,
    Worked for me at the moment .... will let it run to see if it works over the long haul.

  6. dialogcrm
    Member
    Posted 2 years ago #

    I'm getting this as well
    PHP Fatal error: Cannot access empty property in /abc/public_html/wordpress/wp-includes/http.php on line 1686

    I'm wondering if there is an empty property if I can fix it by adding a value to that line?

    If so what would the value be and BTW this is version 2.9.1

  7. dialogcrm
    Member
    Posted 2 years ago #

    Update: because this is a core problem - looks like there is some discussion over at http://core.trac.wordpress.org/ticket/11600

    which says it is
    closed defect (bug): fixed) - but we have to wait for version 2.9.2 to see the fix

    "The code has been commited to the 2.9.2 and 3.0 branches, And will be available in those (and future) releases. "

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags