WordPress.org

Ready to get started?Download WordPress

Forums

[closed] Troubleshooting WordPress 3.3 - Master List (5 posts)

  1. Horray! Sonny is here! But OMGWTFBBQ!? WordPress 3.3 broke everything?

    Don't Panic!

    This thread contains the known issues with plugins (and, yes, in core) found in 3.3. 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.

    • Don't use excessive caps (in titles or body). Punctuate your sentence properly and humanely.
    • Do use descriptive subject lines ("All permalinks broken since 3.3" instead of "Augh! Help ASAP! This version is terrible!")
    • Don't bump your posts (they will be deleted on sight)
    • 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)
    • Don't post in topics marked "Resolved" (we don't look at them).

    If you're upgrading from an older version of WordPress, you may want to read Troubleshooting WordPress 3.1 - Master List and Troubleshooting WordPress 3.2 - Master List. 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 and the New Features in 3.3 Post.

    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. 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

    - 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.3 (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!

  2. QUICK FAQ!

    The following questions were culled from the alpha/beta forum as well as the wp-testers list.

    I can't install a Plugin/theme! WordPress says "The package is corrupt or not in the correct format."

    If you're getting this from the official WordPress.org repositories, please email plugins[at]wordpress.org or contact http://lists.wordpress.org/mailman/listinfo/theme-reviewers to let people know.

    If you're getting this from an external site, it means they didn't package the theme/plugin correctly. All themes and plugins should install into a folder (i.e. pluginname). Also all themes require a style.css. If you see this error, contact the site from which you got the installer and let them know.

    Admin menu doesn't expand/collapse

    Actually it does, but on a per-section basis. This is not a bug, this is by design and will not be changed any time soon. The menus are now 'flyout' when you hover over them and will expand completely if you click on them.

    If you're desperate to expand all menus, there is a plugin: http://wordpress.org/extend/plugins/expanded-admin-menus/

    I lost my media upload buttons!

    No, they were just consolidated into one. You can upload all media types via the one button.

    I can't turn off the Admin Bar

    You can disable it from showing on the front-end of your site, but not the admin area. This is by design, as the Admin Bar has replaced the admin page header from previous versions. Notice that your 'Site Name' no longer appears at the top of the page, and is now a part of the Admin Bar.

    My Admin bar is styled wrong/has no style/won't format!

    You were probably using something like this to disable it:

    wp_deregister_script('admin-bar');
    wp_deregister_style('admin-bar');

    Remove that from your theme and you're GTG!

    I'm getting weird java/js errors!

    jQuery was changed to version 1.7.1 in WordPress core, which may cause problems with plugins and themes.  Do the needful and turn off your plugins and try the default theme first.

    I'm on Chrome and my admin-side looks all wrong!

    The Chrome extension Send from Gmail (by Google) causes a javascript issue with makes the display on the admin-end look wrong. Turn it off and remove.

    I need to disable those cool feature pointers for my site!

    If you must... Add this to your functions.php:

    remove_action( 'admin_enqueue_scripts', array( 'WP_Internal_Pointers', 'enqueue_scripts' ) );
  3. PLUGINS WITH ISSUES

    In all cases, make sure you're using the latest version of the plugin. Many plugins have updated and will now work with 3.3, but upgrade the plugins first before reporting an issue. For people who reported a plugin to me before, I tested them all out on a clean install of WP with only that plugin installed. If it worked, I removed it from this list. Plugin conflicts aren't the same as plugins not working on 3.3

    * Plugin CSS bleeding into the admin

    Cause: The plugin is hooking into the wp_print_styles hook.

    Fix: Hook into the wp_enqueue_scripts hook (for scripts or styles).

    More: http://wpdevel.wordpress.com/2011/12/12/use-wp_enqueue_scripts-not-wp_print_styles-to-enqueue-scripts-and-styles-for-the-frontend/

    Gory details: http://core.trac.wordpress.org/ticket/19510

    * Reports on twitter that the Postie plugin breaks 3.3 admin.

    * Popup Domination (a plugin NOT available on the WordPress repository) is breaking 3.3. There is an update, but as this is a premium (i.e. you buy it) plugin, you're not going to get a lot of support here.

    * IntenseDebate is showing a miss-match of comments pending.

    * Count Per Day breaks the Media Uploader.

    * Advanced Access Manager causes a white screen of death.

    * TubePress interferes with drag'n'drop in the Admin area.

    * White Label CMS breaks image insertion.

    * All In One SEO reported to lose all custom menu label tags.
    http://wordpress.org/support/topic/menu-label-issue-in-wp33-upgrade

    * Improved Page Permalinks reported to cause newly published Pages to produce 404s.

    * Ad blocker plugins may conflict with the visual editor.

    * Viperbar may become de-enabled and lose all settings.
    http://wordpress.org/support/topic/plugin-viperbar-plug-in-deactivateds-itself-and-loses-data-on-upgrade-to-wp-33

    * Google XML Sitemaps 4.0Beta7 has blank line
    http://wordpress.org/support/topic/plugin-google-xml-sitemaps-beta-7-broken-on-wordpress-33?replies=1

    * WordPress MU Domain Mapping doesn't let you change settings. The dev version fixes this.

    * WordPress MU Sitewide Tags Plugin also has issues, please try the dev version of that plugin too.

  4. THEMES WITH ISSUES

    Background images not showing

    Open header.php and locate your <body> tag. Change this value to <body <?php body_class(''); ?>>

    WooThemes framework breaks the upload/insert media link. Per their site, refreshing your cache will fix this (props Drew!)

    Atuhualpa has some issues with plugins that use the updated jQuery (reported Dec 10th).

  5. Known issues, from Nacin:

    Letting you know about two potentially nasty issues with WordPress 3.3, and
    what you should be recommending in master lists and individual forum
    threads.

    ***

    1. JAVASCRIPT ISSUES. The first problem is again JSON-related. (Once
    bitten, twice WTF.)

    * The symptom: Barely any JavaScript works in the admin. Meta boxes cannot
    be collapsed. Clicking the Screen Options or Help tabs don't do anything.
    etc.

    * To confirm: Go to
    http://example.com/wp-admin/load-scripts.php?load=jquery. (This page is
    accessible logged out.) If it's blank, the bug is confirmed. Please reply
    to this thread with a link to wherever this is confirmed, as we're curious
    as to how common this is in the wild.

    * The bug: load-scripts.php may call json_encode() without us loading our
    compatibility layer. Whoops.

    * The fix: It'll be fixed in WordPress 3.3.1 (timeline still TBD), but for
    now, you can use Hotfix 0.8. Hotfix 0.8 will disable script concatenation
    and fix the problem.

    * The better fix: Tell these individuals to please figure out why PHP is
    compiled to explicitly exclude JSON. I can't even begin to explain how
    backwards that is.

    ***

    2. CSS ISSUES. The second problem is related to plugin styles (or theme
    styles) bleeding into the admin.

    - The symptom. Something doesn't look right in the admin, typically on the
    dashboard, comments screen, or post/page edit screen (post-new or post.php).

    - To confirm: Some CSS file from some plugin or theme is being enqueued
    when it shouldn't be. This is visible in the source in the admin.

    - The fix: It'll be fixed in WordPress 3.3.1 (timeline still TBD), but for
    now, you can use Hotfix 0.8. Hotfix 0.8 will remove all styles accidentally
    enqueued in the admin.

    - The better fix: One of their plugins is guilty of using the wrong hook.
    There's a bit of nuance here, but I've posted a summary at
    http://wpdevel.wordpress.com/2011/12/12/use-wp_enqueue_scripts-not-wp_print_styles-to-enqueue-scripts-and-styles-for-the-frontend/
    .

    ***

    More about Hotfix: Hotfix is a plugin maintained by lead developer Mark
    Jaquith and some other core developers including myself. Users should leave
    the plugin active (or at least installed) and always updated, in the case
    of quick patches for future releases. The current version is 0.7. Mark will
    release 0.8 in the morning. The development version is 0.8:
    http://wordpress.org/extend/plugins/hotfix/download/.

    ***

    The full list of known, reported, and confirmed issues is at
    http://core.trac.wordpress.org/report/4.

    Cheers,
    Nacin

    ETA (Dec 16th) - If you use Multisite and DO NOT have a DB prefix (i.e. wp_) on your database, there may be some problems. Strictly speaking, that's not supported as it does silly things with your settings if you later try to turn on multisite, but that being said, it looks like the core devs may have to reinstate things for 3.3.1. Keep tabs on http://core.trac.wordpress.org/ticket/19566 for more gory details. Oh and in the future, please use db prefixes. Every app, from WordPress to those professional ones people pay millions for suggests you use them.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.