• Got this error when I upgraded automatically from 2.7.1 to 2.8:

    Warning: gzinflate() [function.gzinflate]: data error in /home/acctname/public_html/wp-includes/http.php on line 1787

    I don’t know what the effect is, everything seems to be running fine, but I got this error on all my WP blogs. Also, after the upgrade, WP didn’t ask to upgrade the database….

Viewing 12 replies - 46 through 57 (of 57 total)
  • Confirmed… follow lisachon and c-bass suggestions.

    I’m having the same problem with the admin as thpanagos – I’m on 2.8.4 and I have put the http fix in and still the same thing. I get 2 errors that has to do with javascript. I’m not sure what my clients server is on.

    Error: illegal character
    Source File: https://dev2.grindvision.com/wp-admin/load-scripts.php?c=1&load=jquery,utils,quicktags&ver=b64ae9a301a545332f1fcd4c6c5351b4
    Line: 1
    Source Code:
    ?kWI?6????????=-??r?$$.???-p??$@.!Q?(?B?o??wDdd*?vO????Um??q??w???K?i??7????N?G|Л?煽??4??6+?+?X?r>??????E+???:?????????r^(?J?g?(?L.?w???~??G??7??????旃?~?S??????=?yV??Oz????6a??%????????6?O????6 k??(;?7a?3)Vb?? g??Z??g?O?Y?K??f??]?t?G
    Error: illegal character
    Source File: https://dev2.grindvision.com/wp-admin/load-scripts.php?c=1&load=hoverIntent,common,jquery-color,wp-ajax-response,wp-lists,jquery-ui-core,jquery-ui-resizable,admin-comments,jquery-ui-sortable,postbox,dashboard,plugin-install,thickbox,media-upload&ver=678e1505aa95fa2e2bc5e32f8227d388
    Line: 1
    Source Code:
    ?ywG?'?w?S@?n0?"?? Y??:?m,????,??XHl@Q,?????n?d&??\5???L[Dd?q???o}p>???Y=k\e??5????f?|????q?>[???U>[??????e?t????????????|~?n??N;Y+??^??izztE??')}=?iO???<??????~?A?j???0??ù??????)*? ?]wz?<[??y? ??A??c????>j?;?W?9k4?L[??#?A?u>??d:?_?S,$I??

    The admin screen only goes wacky in firefox for me but my client says it goes crazy in in Safari too for him.

    I’ve been having the same trouble since uploading to 2.8.4, and none of the http.php fixes seem to have helped.

    It only seems to occur when I save or edit a post, it seems like.

    Does anyone have any more information on this? It doesn’t seem to be hampering my functionality any, it’s just very annoying to see this filling up my error log.

    I have the same problem with the admin area only and the errors in the HTTP.PHP file. I too have just upgraded to 3.8.4 a little over a week ago. I did try fix above from sbrunners and it did work but for the edit a post/page. The post/page seems to go into the html editor only and not allow the visual edit with all the nice icons.

    getting these error when upgrading to 2.8.5

    I followed this whole thread – I’m one of the people where the http.php fixes didn’t work, but I think I figured out the source of the problem.

    At some point I started getting hacked with those messages that thpanagos mentioned:

    /**/eval(base64_decode(‘aWYoZnVu…

    I discovered that those lines weren’t just in my theme, but scattered all over wordpress, in nearly every php file. The one in particular that was causing the exact gzinflate, gzcompress as well as the http.php errors was one that got into my wp-config.php file, located in the root of the wordpress install.

    Now begins the process of going through every php file and getting rid of that line.

    Hopefully 2.8.5 will prevent further hacks.

    mrgtb

    (@mrgtb)

    This problem is there in WordPress 2.8.6. Both on a localhost and a live site I’m running, I’m getting the same errors every now and then:

    [13-Nov-2009 01:34:29] PHP Warning: gzuncompress() [<a href='function.gzuncompress'>function.gzuncompress</a>]: data error in F:\wamp\www\wp-includes\http.php on line 1792

    I get the same code and line number on my live site too online using a domain.(1792)

    Strange thing is, I wasn’t getting this error when using WordPress 3.8.4. Only after upgrading to 3.8.5 onwards did it start appearing. They made some changes to the HTPP file in 3.8.5 from 3.8.4 security wise. Since then this error has been popping-up. But it wasn’t there in 3.8.4

    And the fixes in this thread don’t work for me either. WordPress need to get this sorted out! Because a lot of people are getting it. It looks like something they changed when going from 3.8.4 to 3.8.5 started making this to happen.

    morcom

    (@morcom)

    I too have been having these errors on a number of my sites and agrre that I don’t remember seeing them a few months ago. In order to see if it was an 2.8.x upgrade problem I rebuilt one of them from scratch using the latest 2.8.6.
    I am also using various templates so don’t believe it it tied to the theme design.
    The others have all been upgraded through all the upgrades from 2.7 so not sure when the problem occured but suspect this last summertime.
    Not being a programmer I will rely on those wizards who are and keep looking at this post for a future solution

    I’ve had the same error messages and think I’ve come to the same conclusion as epiyoo

    First thing I did was checked one of my theme files – and I found the

    /**/eval(base64_decode(

    I stripped out the characters from that, and decoded them which revealed the following php code:
    if(function_exists(‘ob_start’)&&!isset($GLOBALS[‘sh_no’])){$GLOBALS[‘sh_no’]=1;if(file_exists(‘/home/directory/www/libs/templates/skel/views/elements/email/html/copper.php’))

    I dug into the file copper.php (which was never placed there by me) and found it was further obfusticated code. Which I deleted and replaced with “echo ‘Hello World!'” doing that revealed just how often that copper.php file was called.

    I upgraded my wordpress install, but “Hello World!” still appeared so I went digging into my template files/plugins where I discovered, again, that “/**/eval(base64_decode(” was the first line of many of those. I deleted and reinstalled the templates that seemed to to be calling it (and double checked them afterwards). Then I went through my plugins – one at a time – not all of them seem to be calling the code, but lots did. So I simply deleted the line from them.

    Once done, I deleted the copper.php file. I think it’s clean now. But blimey, that was a nightmare… And I’m pretty sure it’s been on my site for some time (despite upgrading everytime there’s an upgrade available – I think it got in via a backdoor on an earlier build of WP and has just clung on, malignantly in the plugins and themes, which is why further upgrades haven’t shifted them).

    -pj

    is anyone experiencing this issue on wp 2.9????

    For several months I had a problem with the “Dashboard”, not the site itself. Very similar to screen capture that “thpanagos” posted above. I also received error messages like:

    Warning: gzinflate() [function.gzinflate]: data error in /public_html/blog/wp-includes/http.php on line 1788

    Warning: gzuncompress() [function.gzuncompress]: data error in /public_html/blog/wp-includes/http.php on line 1793

    “sbruner’s” http.php file download above did not work for me at first. However, after (1) deleting the “/**/eval(base64_decode(‘aWYoZnVu…” code I found at the begining of all php theme files and (2)replacing the http.php file downloaded from “sbruner” above and (3) upgrading from 2.8.4 to 2.9.1 the problem was solved.

    For me, I think what I had been missing was the hacked code…
    “/**/eval(base64_decode(‘aWYoZnVu…”
    This code was found in every PHP file located in the dashboard themes editor. I did not find this code in any other WP php files anywhere.

    I did notice the /**/eval(base64_decode(‘aWYoZnVu… problem was present with all themes. On a special note: I was running 5 WP sites on the same database and all 5 had the same problem. I had to delete the files on each separate site, update the http.php file and upgrade the software individually.

    Good luck,
    Smoke House Willie

    I have this same problem running 2.9.1. It started happening after I installed the @feed plugin.

    None of my theme files have:

    eval(base64_decode

    When I re-upload http.php the problem goes away, but then comes back again later.

Viewing 12 replies - 46 through 57 (of 57 total)
  • The topic ‘Error when upgrading to WP2.8’ is closed to new replies.