WordPress 2.8.2 Upgrade Information

by Frank Jovine on 07/23/2009 in Software

It looks like another upgrade, but this one is a very small change. There has been many issues around 2.8 with admin consoles disappearing, memory over allocated, unable to use automatic installation, etc. If you have experienced any of these issues, don’t worry or at least not yet, more on this later.

I compared 2.8.2 to 2.8.1 and found that only (8) files were changed or updated. There’s no need to upload the entire package to upgrade to 2.8.2.

The (8) files that were changed are;

wordpress/readme.html
wordpress/wp-admin/comment.php
wordpress/wp-admin/edit-form-comment.php
wordpress/wp-admin /includes/comment.php
wordpress/wp-admin /includes/template.php
wordpress/wp-includes/comment-template.php
wordpress/wp-includes/default-widgets.php
wordpress/wp-includes/version.php

You only need to over write those files indicated above. There are no database changes in this release.

Are you having memory allocation issues?

Here are steps you can take to tackle these annoyances.

Note: Some hosting companies restrict you from increasing your allocated memory using the php.ini file. If you are hosting with BlueHost or Aplus.net you will be able to make these changes, however you will need to create a php.ini file.

How to resolve fatal error: Allowed memory size exhausted

  1. If you have access to your PHP.ini file, change the line in PHP.ini where it shows (memory_limit = 32M ; Maximum amount of memory a script may consume (32MB) and increase that to 64M.
  2. If you don’t have access to PHP.ini try adding this to the wp-includes/cache.php file (right after the ini_set(‘memory_limit’,’64M’); // set memory to prevent fatal errors.
  3. I added this line to the wp-includes/cache.php file (right after the ini_set(‘memory_limit’,’64M’); // set memory to prevent fatal errors.

The reason I increased it to 64MB is if you look at the error you will get a memory size in bytes. The 33554432 in the error indicates that 32MB was not enough so I increased it to 64 and my errors in the dashboard went away.

You could also add the following line to your wp-config.php

define(‘WP_MEMORY_LIMIT’, ’64M’);

Once this is in place, you won’t have to constantly make the fix again whenever you upgrade WordPress.

If these steps don’t work, please contact your hosting company for further support.

If you have any issues, please leave a comment here.

  • Share/Bookmark

26 Responses to “WordPress 2.8.2 Upgrade Information”

  1. BunnygotBlog

    Jul 23rd, 2009

    Hi Frank,

    We always wait a while before installing the wp update.Just in case it needs some tweaking.I guess it is safe to go ahead now.

    Thanks for the info.It is great hearing this.

    • Frank J

      Jul 23rd, 2009

      Thank you bunny and let me know how it works. I know you will have no issues.

  2. A. Zuck

    Jul 23rd, 2009

    It’s cool to have a resident expert who can decipher this for me. Sometimes I can’t figure out the rhyme and reason behind these updates.

    • Frank J

      Jul 23rd, 2009

      I hear you what your saying. I always search for information on any new releases to see what others are saying and than I put it all together and share it with everyone.

  3. HART (aka PetLvr)

    Jul 23rd, 2009

    There’s always some XSS vulnerability to fix!

    “The 2.8.2 release fixes a issue with comment author URLs;

    Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.

    Read more: http://weblogtoolscollection.com/archives/2009/07/20/wordpress-2-8-2-security-update/#ixzz0M6xdSATS

    ===============

    By the way – off topic – I just copy and pasted that blurb above from weblogtoolscollection and was going to quote the source – but, the copy/paste ALREADY included the URL… How did they do that? I need that on my blogs :)

    • Frank J

      Jul 23rd, 2009

      Hart,

      Thank you for sharing that info!

  4. Thanks Frank, I think I’ll just wait awhile on this upgrade. Appreciate the heads up!

    • Frank J

      Jul 23rd, 2009

      Jonathan,

      Just copy the files I indicate and you will be fine. I am running 2.8.2 and haven’t had any issues.

  5. CrimeCleaner

    Jul 24th, 2009

    Good stuff, thanks for the heads up. I have actually been having some problems, so I guess I’ll just wait and see…

  6. Kurt Avish

    Jul 24th, 2009

    Thumb up for the further details. I already upgraded on the released date and everything went fine this time. :-)

    • Frank J

      Jul 24th, 2009

      Kurt,

      Glad the upgrade went well. Did you use the auto update or manual?

  7. Joanie

    Jul 24th, 2009

    Thanks for the tips. I was just thinking of updating WordPress because my install is out of date. Now I’ll know what to look for when I do. Maybe this weekend?

    • Dan

      Jul 24th, 2009

      Thanks for the great post Frank.
      especially the memory error stuff…
      I spent a few days trying to figure that one out
      Just wondering if anyone can tell me If you use the Click to upgrade option in your WordPress admin ?
      Does it only replace these files? or the whole lot? or just core files?
      Likewise for using Simple Scripts when hosting with Bluehost?
      Cheers
      Dan

      • Frank J

        Jul 25th, 2009

        Dan,

        The auto upgrade overwrites all files. It’s best that you just overwrite the files I indicated.

  8. Hamming

    Jul 24th, 2009

    Thanks for summarizing useful info. I’m kinda exciting about new WordPress version. Yes, I really want to do the upgrade. However, I have decided to wait for a little longer coz I concern with compatibility with current plugins.

    • Frank J

      Jul 25th, 2009

      Hamming,

      If you just over-write the files I posted, you will have no issues.

      • Hamming

        Jul 26th, 2009

        Yippe. The upgrade went well. I did exactly what you posted. Now, my site is running WP 2.8.2.

        Thanks. ;)

        • Frank J

          Jul 27th, 2009

          Hamming,

          Good to hear your upgrade went well!

  9. TwitterMega

    Jul 25th, 2009

    We always update on one blog out of our big network of blogs and if the update looks allright on that one then we mass upgrade all using a smart script that we use to mass manage our network.

    http://www.semmy.com/wordpress-automation/

    Enjoy!

  10. jj-momscashblog

    Jul 26th, 2009

    I guess my biggest problem is I hate change!! I will go kicking into the night, but a good techi friend of mine convinced me to finally update WordPress 2.8 and I let him do it for me. At first when I looked at it I thought it was the worst thing that I could of done… how will I get use to this? I hadn’t posted in several month due to illness and then to have this change was like a nightmare. Now that I’m back blogging and using this new WP it’s not so bad but I don’t like it every time you turn around there’s a new plugin, but I know there’s a reason for it and techi people love it. Great info and very in depth. thanks so much jj

    • Frank J

      Jul 26th, 2009

      Change can sometimes be a good thing and in this case, it is.

  11. Andy

    Jul 31st, 2009

    Hi, just tried upgrading following your instructions and seem to have a few problems. Getting a lot of fatal errors and cannot access the plugins from the dashboard and other areas.

    Any assistance would be very useful!

    Fatal error: Call to undefined function esc_url() in/home/vaughand/public_html/blog/wp-includes/comment-template.php on line 197

    • Frank J

      Jul 31st, 2009

      Andy,

      From what version were you upgrading from? This article only applies to 2.8.1 to 2.8.2.

  12. bedava kontör

    Aug 2nd, 2009

    WordPress 2.8.2 Upgrade Information | TechJaws: Internet Security and SEO great article thank you.

  13. abdomeri

    Aug 3rd, 2009

    thank sir this great inf i can not say this anew world for website content or seo man going on

    • Frank J

      Aug 3rd, 2009

      Whoa – Not sure what your trying to say, but welcome!