• Skip to primary navigation
  • Skip to main content
  • Skip to footer
WPSecurityLock – Malware removal & WordPress security services

WPSecurityLock – Malware removal & WordPress security services

WordPress security, malware removal, repair, backups, ongoing maintenance, installation, site migration & support services – WP Security Lock.

  • Facebook
  • LinkedIn
  • Twitter
  • Home
  • About
    • About Us
    • Speaker Information
    • Contact Us by Phone, Email or Live Chat
    • Testimonials
  • Security Services
    • Malware / Virus Removal
    • WordPress Security and Installation Services
    • Monthly Security Packages
    • SSL Conversion Service (HTTP to HTTPS)
  • Blog
  • Resources
  • Contact
  • SafeWP

WordPress 3.2.1 Update — Maintenance Releases Fixes

July 14, 2011 By Regina Smola 31 Comments

WordPress 3.2.1 UpdateWordPress 3.2.1 was released to the public on July 12, 2011.

This is a maintenance release for WordPress 3.2 and all self-hosted WordPress users should update their blogs to this latest stable version as soon as possible.

According to Andrew Nacin, a core developer of WordPress, Version 3.2.1 fixes a JSON-related server incompatibility issue that affects some users.

“A fair number of servers and distributions are, by default, missing the JSON extension for PHP. The number is actually a bit surprising, and is enough that we need to go forth with restoring these.

While core does not heavily rely on JSON, a number of actions will fail without it, and a lot of plugins rely on it. Without a compat layer, we'll see fatal errors.

Plugins, coincidentally, have relied on the existence of Services_JSON in class-json.php for unknown reasons, given they should have been using json_encode() and json_decode() directly since 2.9. Restoring this file in place should fix some of those compatibility issues, though I'd like to still get all of those plugins to change their bad ways.”

Source ~ core.trac.wordpress.org/ticket/18015

As Andrew pointed out about wanting to get plugins to change their bad ways. I say AMEN! I can’t tell you how many times I’ve work on a WordPress site and a plugin causes a hair-pulling problem.

WordPress 3.2.1 also includes some other fixes to the new dashboard design and the Twenty Eleven theme (based on the popular Duster theme).

Email received from Matt Mullenweg:

Subject: WordPress 3.2, you know what to do
Dated: July 12, 2011

Last week we released WordPress 3.2, a version focused on making WP faster and lighter with a refreshed dashboard, new Twenty Eleven theme, a zen writing mode, and more:

http://wordpress.org/news/2011/07/gershwin/

We waited to email because there were some issues with the JSON module on some web hosts, which the just-released version 3.2.1 fixes. Download from WordPress.org or click the update button in your dashboard to get the latest.

Let's have a look at the significant changes that developers made in WordPress 3.2.1:

  • WordPress 3.2.1 fixes a server incompatibility issue related to JSON (JavaScript Objection Notation).
  • Some updates in the new dashboard design, including fixing collapse/expand issues in admin menus, errors in nav menu items, styling changes, etc.
  • Fixes in the new Twenty Eleven theme, including loop confusion on password protected posts, a stray character, search form width, editor styles, etc.

For a complete list of fixes view their changelog and tickets.

Files Revised in WordPress 3.2.1:

  • readme.html
  • wp-admin/css/dashboard.css
  • wp-admin/css/dashboard.dev.css
  • wp-admin/css/global.css
  • wp-admin/css/global.dev.css
  • wp-admin/css/global-rtl.css
  • wp-admin/css/global-rtl.dev.css
  • wp-admin/css/install.css
  • wp-admin/css/install.dev.css
  • wp-admin/css/login.css
  • wp-admin/css/login.dev.css
  • wp-admin/css/media.css
  • wp-admin/css/media.dev.css
  • wp-admin/css/press-this.css
  • wp-admin/css/press-this.dev.css
  • wp-admin/css/wp-admin.css
  • wp-admin/css/wp-admin.dev.css
  • wp-admin/css/wp-admin-rtl.css
  • wp-admin/css/wp-admin-rtl.dev.css
  • wp-admin/includes/nav-menu.php
  • wp-admin/includes/update-core.php
  • wp-admin/js/wp-fullscreen.dev.js
  • wp-admin/js/wp-fullscreen.js
  • wp-content/themes/twentyeleven/content.php
  • wp-content/themes/twentyeleven/content-aside.php
  • wp-content/themes/twentyeleven/content-image.php
  • wp-content/themes/twentyeleven/content-link.php
  • wp-content/themes/twentyeleven/content-quote.php
  • wp-content/themes/twentyeleven/content-status.php
  • wp-content/themes/twentyeleven/editor-style.css
  • wp-content/themes/twentyeleven/inc/theme-options.php
  • wp-content/themes/twentyeleven/screenshot.png
  • wp-content/themes/twentyeleven/style.css
  • wp-includes/class-json.php
  • wp-includes/compat.php
  • wp-includes/nav-menu.php
  • wp-includes/post-template.php
  • wp-includes/script-loader.php
  • wp-includes/version.php

WordPress & Security Resources:

  • WordPress News: 3.2.1 Maintenance Update
  • WordPress Codex: Version 3.2.1
  • WordPress Trac: 3.2.1 Change Log
  • Download WordPress 3.2.1
  • WordPress Codex – Updating WordPress
  • Upgrading WordPress Extended
  • WordPress Release Notification Email List (fill out the form on the right side of the page)

Important! Updating your WordPress is Essential!

There aren’t that many file changes to WordPress 3.2.1, but it was important enough for the WordPress developers to release this update to ensure your site runs smoothly. If you haven't gotten around to updating to WordPress 3.2.1, then this is as good a time as any. Go do it now! It will keep your WordPress blog faster, more secure and reliable.

We recommend updating your blog manually using the Upgrading WordPress Extended tutorial from WordPress.org. But you can also update from your Dashboard → Updates menu inside your sites’ wp-admin area.

Leave Your Feedback

Have you upgraded to WordPress 3.2.1? Did you upgrade WordPress automatically through the Dashboard or manually? Do you have any WordPress plugin issues with WP version 3.2.1? If you noticed any glitches in the upgrade or conflicts with any plugins be sure to let us know. Leave your comment below.

Securely yours,

Regina Smola
WordPress Security Expert
Follow me on Twitter
Follow WPSecurityLock on Twitter
Become a Facebook Fan

Filed Under: WordPress Security Tips Tagged With: update wordpress, wordpress 3.2.1, wordpress upgrade

Reader Interactions

Comments

  1. sandy says

    July 14, 2011 at 12:44 pm

    Regina – I love your updates about WordPress and I like you have had hair pulling problems !!

    “I can’t tell you how many times I’ve work on a WordPress site and a plugin causes a hair-pulling problem.”

    That’s why I wait a bit after an upgrade – and I know others who wait also to allow plugin developers to catch up. Some plugins are not really an option and I would seriously consider going back to web editors and HTML without them!

    As for updating wordpress manually, well the immortal words of Tennis legend John McEnroe come to mind – “You cannot be serious”

    And yes I know you are !

    🙂

    Reply
    • Regina Smola says

      July 16, 2011 at 8:24 am

      Hi Sandy,

      I agree with you. I too wait a bit after a new version of WordPress is released, unless it’s a major security fix. In that case, I jump right on it. For WordPress 3.2.1, this one I would not wait on because it’s a quick fix for 3.2 (if that’s what you’re running). However, those WP users that have a much older version will definently want to do a complete plugin audit to see if the plugins are compatible first (which will certainly help from getting bald patches!)

      I also like to do manual coding whenever possible, like adding my Google Analytics code to my theme so I can avoid one more gray hair causing plugin. Let’s just say that I need to buy stock in Clairol. I contribute 40% of my grays from my gene pool and 60% from bad plugins.

      Updating manually, OH YEAH! Think about it, you know exactly what files you’re uploading to your server and you can check to see which “stragglers” are still there from a previous date. Then you can ask yourself, “Hmmm, is that supposed to be there?” Getting rid of obsolete files keeps a tidy site.

      Reply
  2. atozer says

    July 15, 2011 at 11:41 am

    Regina, I had to reversed the upgrade after a few functions in my theme can not work properly.
    Especially on javascript / ajax function which jammed.
    I’m visiting your site for finding the solution. Waiting other people which expert in programming to fix it.

    Reply
    • Regina Smola says

      July 16, 2011 at 8:10 am

      Hi atozer,

      Sorry to hear you have to revert back to a previous version. Glad you had a backup to do so. Were you using 3.2 prior to the update? Was your theme working then?

      Reply
    • Pedro Magalhães says

      July 17, 2011 at 10:38 am

      I’ve also had js/ajax issues on my wordpress theme.
      It gives me some errors on /wp-admin/load-scripts.php and my jquery theme file.
      I automatically update my wordpress trough the admin panel…

      Reply
      • Regina Smola says

        July 17, 2011 at 12:56 pm

        Hi Pedro,

        Thanks for letting us know how your upgrade went. It looks like you’re going to have to upgrade your theme to remove the errors.

        Reply
        • Pedro Magalhães says

          July 18, 2011 at 5:26 pm

          I think i solved my problem commenting the include of 2 js files.
          My theme was using a custom admin panel with a jQuery v1.4.2 file, and i guess that was the cause. Neither it was really need, and now WordPress uses v1.6.1…. Could be a conflict maybe.
          I haven’t tested all yet, but the ajax functionalities that weren’t working, now are.

          Reply
          • Regina Smola says

            July 19, 2011 at 7:19 am

            Hi Pedro,

            Glad you got your website fixed and new which files to updated. 🙂

  3. Robert Nelson says

    July 16, 2011 at 11:38 am

    It would be nice if more testing was done before releasing a WP upgrade into the wild. Neither recent upgrades had any problems.

    Reply
    • Regina Smola says

      July 17, 2011 at 1:00 pm

      Hi Robert,

      I hear you on more testing. Although, I know they tested it for months, they must of missed those. Glad they got em’ fixed now though. You can also contribute to WordPress by being a beta tester and report issues on a non-production site to let them know of any issues 🙂

      Reply
  4. Joe says

    July 18, 2011 at 9:43 am

    So I have upgraded my WP I too have been affected by the WP 3.2.1 issue. In the meantime is there a message I need to send to my web host at all?

    Reply
    • Regina Smola says

      July 18, 2011 at 9:51 am

      Hi Joe,

      Thanks for your comment and question. What type of issue are you having after you upgraded to WordPress 3.2.1? Your host may or may not help with it.

      Reply
      • Joe says

        July 18, 2011 at 10:20 am

        I Regina,

        I found that the main Admin menu usually down the left hand side column is completely missing. That is I no longer have the Posts, Pages, Settings, Plugins etc menu is visible. I noticed this soon after I upgraded to WP 3.2.1..

        Reply
        • Regina Smola says

          July 19, 2011 at 7:25 am

          Hi Joe,

          Not sure if this will help, but check out http://wordpress.org/support/topic/troubleshooting-wordpress-32-master-list. It has a list of things you can try to get your admin menu back.

          Please let us know if you find what works. 🙂

          Reply
  5. Joe says

    July 18, 2011 at 9:59 am

    I just upgraded to WP 3.2.1 and the main Admin menu usually down the left hand side column is completely missing. That is I no longer have the Posts, Pages, Settings, Plugins etc menu is visible.

    Reply
  6. Dawn says

    July 18, 2011 at 3:32 pm

    I am having the same problem. Updated a site to the most recent version and NO menu in left sidebar. Sites are on Hostgator hosting account.

    Need some help please!

    Reply
    • Regina Smola says

      July 19, 2011 at 7:19 am

      Hi Dawn,

      Have you tried to put your widget back in? It could be that your theme needs to be updated to work with WordPress 3.2.1.

      Otherwise, please check this: “Troubleshooting WordPress 3.2 Master List.”

      Reply
  7. Ruan Cowley says

    July 19, 2011 at 7:00 am

    I have upgraded to 3.2.1. and now my portfolio pages no longer loads correctly. It only loads when I enable compatibility mode. So you guys have definitely broken something.

    Reply
    • Regina Smola says

      July 19, 2011 at 7:17 am

      Hi Ruan,

      Sounds like your theme may need to be updated if your portfolio pages are no longer loading. As far as us breaking something, we have not worked on your site. Just sounds like a compatibility issues with your theme and WordPress 3.2.1.

      Reply
  8. Jatin Soni says

    July 20, 2011 at 1:24 am

    Its nice but biggest problem now facing with custom post and page template.. Its not working at all.. Where its gone????

    Reply
    • Regina Smola says

      July 21, 2011 at 9:01 am

      Have you tried using a default theme of WordPress (Twenty Ten or Twenty Eleven) to see if they work? If they do, then the problem lies in your current theme.

      Reply
  9. Patti Thompson says

    July 22, 2011 at 12:26 pm

    Hi Regina,

    Thanks for the thoughtful and eloquent explanation of the newest update. I, alas, have had one huge problem. The site runs fine, except all my images have vanished out of their posts. The images are still on the server, but don’t show up. I’ve disabled all my plug-ins, but no dice. I’m really frustrated and can’t be sure what’s happening. I love how stable the upgrades usually are, but this one has knocked me for a loop.

    Reply
    • Regina Smola says

      July 22, 2011 at 1:07 pm

      Hi Patti,

      Thanks for the kudos and your comment. Sorry to hear your pics are misbehaving. Just for the heck of it, try opening your permalinks settings and just hit the save button and see if that wakes your images up. May sound silly, but it’s the magic trick on many glitches. Also, check your media/uploads settings too and make sure they’re right.

      Reply
      • Patti Thompson says

        July 22, 2011 at 1:45 pm

        Thanks, Regina. I tried both those things and can’t get it to work. The weirdest part of the whole thing is that the site is throwing a 404 error when trying to view the images, but I can see them right in the directory that is displayed in the URL path. I feel like I’m in the Twilight Zone or something. The images are there, but the system is saying that they aren’t even though the path is absolutely correct in the Address Bar. Have you heard of anything like this?

        Reply
        • Regina Smola says

          July 24, 2011 at 10:10 am

          Patti,

          Now you have really intrigued my curiosity. There’s something different now, but now sure what. Do you have Skype? If so, send me a message at WPSecurityLock so I can troubleshoot with you.

          Reply
          • Regina Smola says

            July 24, 2011 at 10:11 am

            Also, have you tried switching to the Twenty Eleven theme to see if they show up? If they do, there’s something in your theme that’s causing them not to display.

        • Regina Smola says

          August 4, 2011 at 10:15 am

          Very strange! Try putting your path in Settings > Media > “Full URL path to files” and see if that helps.

          Reply
  10. Matthew says

    August 3, 2011 at 7:57 am

    Are you encountering any loading time issues with the latest wordpress release? Some of my sites have slowed down…

    Reply
    • Regina Smola says

      August 4, 2011 at 10:10 am

      Thanks for your question, Matthew.

      My site was loading extremely slow and found out it was my Firefox (had to update that too) and I also added W3 Total Cache which helped. WordPress 3.2 is supposed to be much faster and it is on some other sites I’ve upgraded. I’m thinking it’s my plugins/scripts and need to re-evaluate those.

      Reply
  11. Matthew says

    August 5, 2011 at 1:13 am

    To be honest these sites have slowed down across all browsers. But I’ll try out W3 Total Cache as you suggested. I didn’t know about it before you mentioned it.

    Thanks

    Reply
  12. Yev says

    September 29, 2011 at 1:48 am

    Greetings you guys
    I had a question which only you guys can answer.

    What do you think, should the twenty ten theme be updated form 1.0 to 1.1 specifically regarding security.

    I was trying to figure out what they changed in the 1.0 to 1.1 and it just appears to be code clean up; but I thought that you guys would know best.

    Cheers.
    Yev

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Let’s work together:

Get in touch with us and send some basic info about your project. Don't be shy, we can help with just about anything.

Contact Us!

Footer

  • Facebook
  • LinkedIn
  • Twitter

Contact

Call 815-600-7270
Contact
Mo,Tu,We,Th,Fr 9:00 am – 5:00 pm

Get WordPress Help Now

Chat With Us!
Submit A Support Ticket

Copyright © 2025 | WP Security Lock, Inc