WordPress.org

Ready to get started?Download WordPress

Forums

[closed] Troubleshooting WordPress 3.5 Master List (4 posts)

  1. Issues with Twenty Twelve and themes? Please Read

    Horray! Elvin is here! But OMGWTFBBQ!? WordPress 3.5 broke everything?

    Don't Panic!

    This thread contains the known issues with plugins and themes found in 3.5. Please read this WHOLE topic and come back and check it later, as it will be updated.

    Remember to be calm, be patient and be respectful. Volunteers are out here to TRY and help you, but we need your help too. ALL forum rules still apply. You are just as important as everyone else.

    If your post doesn't show up right away, please be patient. With the higher than normal post volume, more people get erroneously flagged as spam. We're working hard to keep the queue clear, but making multiple posts slows us down, as we have to go back and check if you already posted. Post one. If it shows up as 'Anonymous', we'll fix it for you. Just wait.

    • Do use proper capitalization (in titles or body). Punctuate your sentence properly and humanely, it helps us read.
    • Do use descriptive subject lines ("All permalinks broken since 3.3" instead of "Augh! Help ASAP! This version is terrible!")
    • Do be patient. We know it sucks to be down, but we delete bumps on site.
    • Do make your own topic unless your problem is 100% exactly the same as someone elses (it will be easier for us to help YOU that way)
    • Do mark your topic as resolved when it's fixed so we know not to come looking there anymore.
    • Do remember you're not alone.

    If you're upgrading from an older version of WordPress, you may want to read lists for 3.1, 3.2, 3.3, and 3.4. There are known issues with older themes and plugins, and they may not have been corrected.

    Also keep in mind that not liking the direction of WordPress's Admin Design does not a bug make. If you don't like a feature, please don't make a series of posts complaining about it. Look and see if someone already did, and post there, or consider joining the process earlier on (like in Beta or even test via SVN). What you're seeing today is the result of months of work and testing, and unless something is outright broken, it's highly unlikely to be changed.

    Again, BEFORE you post:

    Make sure you've read the entire Master List post - http://bit.ly/wp35ml - and the New Features in 3.5 Codex Article - http://codex.wordpress.org/Version_3.5

    Go to your own install's about page - http://domain.com/wp-admin/about.php - to see what's new.

    And then make sure you've tried...

    • flushing any caching plugins you might be running, as well as server and/or browser caches.
    • deactivating all plugins (yes, all) to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s). If you can't get into your admin dashboard, try resetting the plugins folder by FTP or PhpMyAdmin (read http://bit.ly/UhpkLl if you need help). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old (read http://bit.ly/WMrMM5 for more information on mu-plugins)
    • switching to the Twenty Eleven theme to rule out any theme-specific problems. If you can't log in to change themes, you can remove the theme folders via FTP so the only one is twentyeleven. That will force your site to use it.
    • manually upgrading. When all else fails, download a fresh copy of the latest.zip file of 3.5 (top right on this page) to your computer, and use that to copy up. You may need to delete the wp-admin and wp-includes folders on your server. Read the Manual Update directions first: http://bit.ly/RbU5qG
  2. CORE CHANGES

    Outside of the normal changes (buttons are now square, colors have been tweaked, code has been optimized), there's one major new feature that everyone will be talking about: Improved Media Uploader.

    The media uploader is improved, and the way you insert galleries into your posts is changed. Just like before, you can upload and insert media (images, audio, document files, etc.) by clicking the Add Media button. The drag-and-drop box (introduced in WordPress 3.3) now overlays the whole screen. There's no need to press 'save' to change your title, alt tags, or captions, as WordPress will save it for you on the fly. To create an image gallery, select the images to add and click on the "Create a new gallery" button. It's just that easy.

    Also included in 3.5 is the new default theme, Twenty Twelve - http://wordpress.org/extend/themes/twentytwelve - which is a responsive theme that looks good on mobile devices, without any extra work needed by you. Twenty Twelve is also the first WordPress default theme that was designed to work either as a traditional website or a blog.

    One other major change is the Link Manager. If you're using it, you'll want to install the Link Manager plugin - http://wordpress.org/extend/plugins/link-manager/ - because it's going away. Don't worry, if you're using it, it will still be there, but if you've never used it, it will become invisible.

    If you're a fan of the HTML (i.e. plain text) editor, that's been renamed to 'Text' to more accurately describe what it really is. There are also new oEmbeds (Slideshare, Instagram, and SoundCloud), and the oEmbed feature is now on for everyone.

  3. KNOWN ISSUES

    jquery

    Plugins and themes which use their own jQuery without properly compensating for WP's will break. This isn't new by any means. In fact, we've always said that replacing or overriding jQuery will bust things, and we don't let people do it anymore in plugins or themes hosted here. That doesn't stop people from doing it, though.

    We've come up with some awesome directions to help you debug your jQuery issues: http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    Don't worry, if that was greek to you, do the usual turning off plugins and switching themes to figure out which one it is, and then tell the dev 'Hey, you're doing_it_wrong() and breaking things!'

    In all cases, make sure you're using the latest version of themes and plugins. For example, TwentyTen and TwentyEleven themes got an upgrade. Also many plugins have updated and will now work with 3.5. Make sure you upgrade them first before coming for help.

    mod_pagespeed

    On some hosting environments, aggressive settings for the "mod_pagespeed" addon can break the javascript code and cause scripts to not be able to function. This can cause many problems, such as widgets not working, menus not being draggable, the customizer not working, or the media screens not being available.

    To fix the issue, you will need to disable mod_pagespeed, or adjust its settings to not take effect in the wp-admin directories. You may need to ask your hosting service for help on how to do this.

    PerishablePress "5G" blacklist

    If you've ever added the 5G blacklist to your .htaccess file, then it will break the Javascript on WordPress 3.5. Get the updated 5G blacklist here: http://perishablepress.com/5g-blacklist-2013/ that works with 3.5+

  4. General

    Error message: Warning: Missing argument 2 for wpdb::prepare(), called in ... (happens in themes and plugins)

    Fix: Your site is fine, but you may wish to turn off PHP's display errors setting. Contact your theme or plugin dev and point them to http://make.wordpress.org/core/2012/12/12/php-warning-missing-argument-2-for-wpdb-prepare/ so they can fix the underlying issue.

    Error message: Download failed. Destination directory for file streaming does not exist or is not writable.

    Fix: When WordPress downloads any sort of file, then it has to be able to write that file somewhere. To do this, it uses the "temp" directory. If WP detects that it cannot write files to this temp directory, then you get the error message you are now getting. WP tries to find a valid temp directory, but sometimes servers are configured poorly.

    WordPress 3.5 changed the temp directory order to prefer the system's pre-defined temp directory instead of attempting to write into wp-content. On some badly configured hosting systems, this temp directory may be defined, but not actually writable. This causes the error message.

    You can work around this by specifying a temp directory on your server with a place that you know WordPress is allowed to write files to. You can do this by adding this line of code into the wp-config.php file.
    define( 'WP_TEMP_DIR' , ABSPATH . 'wp-content/' );

    That will tell WP where to write the temporary files.

    Themes

    Plugins

Topic Closed

This topic has been closed to new replies.

About this Topic