WordPress.org

31. Elpie
    Member
    Posted 2 years ago #

    I wouldn't bother with patching anything - just download and install WP 2.8.1 RC. The latest is RC2 and it seems to be pretty stable.

32. flapane
    Member
    Posted 2 years ago #

    I can confirm that using Rick's http.php file causes Lastfm plugin to work correctly.

33. matstillo
    Member
    Posted 2 years ago #

    I'm also confirming that using sbruners replacement .txt for the http.php file has fixed it for me.

    I wasn't getting the error from the lastfm plugin itself. It was in fact a modified verion - lastfm spotify for wordpress, which I think is based on the same plugin anyway. The developer of that modified plugin might not know about the problem yet.

    Still, thanks all, especially sbruner who fixed it for me!

34. sbruner
    Member
    Posted 2 years ago #

    matsillo: you're welcome! Glad it worked.

    Looks like this fix will appear in 2.8.2.

    Until then, my fix should work.

35. wildbug
    Member
    Posted 2 years ago #

    Thanks so much sbruner!!! It worked for me too. Not sure if I should upgrade to 2.8.1. Can someone tell me the pros and cons of doing so? I'd like to wait for 2.8.2 since the fix is there. Thanks!!

36. lorisir
    Member
    Posted 2 years ago #

    sbruner, this worked on a related issue I was having as well. Thanks!

    See related issue:

    "Javascript in Admin Tool Not Loading Properly"
    http://wordpress.org/support/topic/288907?replies=3

37. iblogie
    Member
    Posted 2 years ago #

    Unfortunately, the fix was not included in 2.8.2. :( After upgrading, I got the error again! Now I have to apply the fix once more...

38. oxnardmontalvo
    Member
    Posted 2 years ago #

    i only had this crop up following the 2.8.2 update. html file replacement doesn't fix it. and, it's intermittent. darn it all to heck

39. UserName9
    Member
    Posted 2 years ago #

    Ok, so i am running 2.8.2, what did you guys do to fix the errors?

    Thanks

40. sbruner
    Member
    Posted 2 years ago #

    Had to move fix. You can download here:
    http://www.slipfire.com/download/3/

    Change the name to http.php, and overwrite the current one in your wp-includes folder. You should only need this if you're running 2.8. I believe this fix will be included in 2.8.3.

41. Opethian
    Member
    Posted 2 years ago #

    Hello everyone!

    I too have the same problem and have tried all the fixes stated in this thread so far. I'm now running 2.8.4

    My hosting provider is Network Solutions, my family website is http://gurling.org and my blog is at http://gurling.org/alan/.

    The odd thing is, the error messages:

    Warning: gzinflate() [function.gzinflate]: data error in /data/11/0/155/153/807642/user/828456/htdocs/gurling/alan/wp-includes/http.php on line 1787
    
    Warning: gzuncompress() [function.gzuncompress]: data error in /data/11/0/155/153/807642/user/828456/htdocs/gurling/alan/wp-includes/http.php on line 1792

    I'm unsure on how to proceed here. This error message appears in the admin screen.

    If there's anyone who can help, I'd appreciate it!

    Kind regards,

    Alan

42. abelcreative
    Member
    Posted 2 years ago #

    Getting this problem too in a 2.8.4 site - loading the site will occasionally appear totally blank, than hitting refresh will show the site. Very weird, can't figure out what to do.

43. thpanagos
    Member
    Posted 2 years ago #

    Using 2.8.4, have the same.
    First, i see this on my admin page

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

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

    AND i have a http.php file starting with the /**/eval(base64_decode('aWYoZnVu...

44. Opethian
    Member
    Posted 2 years ago #

    It cleared out this past few days, now the the issue is there again. My host won't help me either. LOL Oh man.

45. lisaschon
    Member
    Posted 2 years ago #

    I suddenly got the same error messages. After much messing around I finally got it sorted - thanks to the help on this thread.

    What I did was go to the 'backup' options in my weird looking admin section. Backed up my database.

    Then upgraded automatically to 2.8.4 (which is what I was on anyway but the option was still there so I took it).

    Then I downloaded the link from sbrunner (5 messages above this one) and ftp'd it into my wp-includes to replace my http.php file.

    It worked for me.

    Hope this helped.

    Lisa

46. c-bass
    Member
    Posted 2 years ago #

    i had the same with 2.84 and got fixed it with sbrunners tool: http://www.slipfire.com/download/3/

    thanks

47. zzb
    Member
    Posted 2 years ago #

    Confirmed... follow lisachon and c-bass suggestions.

48. mwmalta
    Member
    Posted 2 years ago #

    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: http://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.Dž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: http://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.

49. voolword
    Member
    Posted 2 years ago #

    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.

50. cwesterman1
    Member
    Posted 2 years ago #

    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.

51. takien
    Member
    Posted 2 years ago #

    getting these error when upgrading to 2.8.5

52. epiyoo
    Member
    Posted 2 years ago #

    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.

53. mrgtb
    Member
    Posted 2 years ago #

    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.

54. morcom
    Member
    Posted 2 years ago #

    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

55. pjholden
    Member
    Posted 2 years ago #

    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

56. france1972
    Member
    Posted 2 years ago #

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

57. Smoke House Willie
    Member
    Posted 2 years ago #

    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

58. solutionsphp
    Member
    Posted 2 years ago #

    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.

Topic Closed

This topic has been closed to new replies.