Advertisements

WordPress 3.5 has just been released and more than one million people have already downloaded the new blogging software. A lot of people are complaining about the problems in WordPress 3.5. You can go through the list of problems and known issues in WordPress 3.5 troubleshooting master list here.

We updated our installation of Technize.net to WordPress 3.5 as soon as it was released. The upgrade process went smoothly and everything was working fine. I had read some issues about the new media uploader being ugly and not uploading files. But this was not the case at Technize.net. All the authors were able to use the media uploader as well as Windows Live Writer to upload images to the server.

But after logging off and logging on again, my Add Media button stopped working. I was confused for a moment and then decided to Google the problem for a possible solution. I found multiple issues that were causing this problem. The most helpful post was from Trionic labs.

The following script error was found during the debugging process:

http://www.technize.net/wp-admin/load-scripts.php?c=0&load[]=jquery,utils,plupload,plupload-html5,plupload-flash,plupload-silverlight,plupload-html4,plupload-handlers&ver=3.5

The error means that WordPress 3.5 combines all the scripts into one script loads them using load-scripts.php file instead of loading them separately. This certainly saves some loading time but causes multiple problems. Disabling this behavior will get rid of the error message. To load all the admin side scripts separately, just add the following code at the end of your wp-config.php file.

define(‘CONCATENATE_SCRIPTS’, false );

Further digging down revealed that it is the caching that is creating all sorts of issues for WordPress 3.5. If you are using a caching plugin, you can prevent your admin part /wp-admin/ not to be cached at all. This will also get rid of problems like Add Media button or any other part of WordPress not working.

This issue has come particularly to the users who are using Google PageSpeed as their Content Delivery Network (CDN). If you are using Google PageSpeed, go to PageSpeed console and follow the steps below.

  1. Click on PageSpeed Service group and go to Configure Rewriters.
  2. Add the following in the text box labeled “List of URLs served without any optimizations (blacklist): (eg. http://www.example.com/bad/*)

    http://www.technize.net/wp-admin/*

    Make sure you replace www.technize.net with your own domain name.

  3. Press the Apply to live button to apply changes immediately.
    Google PageSpeed Console

This will prevent PageSpeed from caching your admin resources and all the errors pertaining to combining scripts will be resolved.

Did you encounter any problems while upgrading to WordPress 3.5? Please share your experiences with us in the comments.

Advertisements