• Insure backups are completed before doing the upgrade
    1. See WordPress Backups

    Can’t login to deactivate all plugins
    1. Read How to deactivate all plugins when not able to access the administrative menus?

    Try these things to resolve problems with Visual Editor and editor tool bar
    1. Delete or refresh the browser cache

    2. If using Gears, disable it and re-enable it again

    3. Delete wp-admin and wp-includes directories and upload fresh copies from a new(important) install package or reinstall automatically

    4. Visit https://yoursite.com/wp-includes/js/tinymce/wp-tinymce.php and look for any PHP errors or warnings at the top. If there are any try contacting your hosting provider to resolve them or try the next step. Of course replace yoursite.com with your domain

    5. A number of plugins have been reported to present problems so deactivate all plugins and reactivate one-by-one to find culprit. Any plugin that uses its own javascripts might be a possible candidate.

    6. Add define( ‘CONCATENATE_SCRIPTS’, false ); near the top of wp-config.php. That would make WordPress admin run slower, so can try removing it in a few days and testing again (this would eliminate any stale network cache)

    7. Some people also reported success redoing the upgrade via Tools->Upgrade->Re-install automatically, then clearing the browser cache.

    8. Try another browser

    9. Confirm that Your Profile, “Disable the visual editor when writing”, is NOT checked.

    Try these things to resolve problems with Widgets such as not able to drag and drop
    1. A number of plugins have been reported to present problems so deactivate all plugins and reactivate one-by-one to find culprit

    2. In Appearance->Widgets under Screen options, try the Enable Accessibility Mode

    3. Delete or refresh the browser cache

    Fatal error: Allowed memory size of xxxxxxxx bytes exhausted
    If deactivating plugins doesn’t work try one of these methods for increasing the amount of memory a PHP script may consume

    1. If you have access to your PHP.ini file, change the line in PHP.ini
    If your line shows 32M try 64M:
    memory_limit = 64M ; Maximum amount of memory a script may consume (64MB)

    2. If you don’t have access to PHP.ini try adding this to an .htaccess file:
    php_value memory_limit 64M

    3. Try adding this line to your wp-config.php file:
    Increasing memory allocated to PHP
    define('WP_MEMORY_LIMIT', '64M');

    4. Talk to your host.

    Upgraded, can’t login and getting error message
    In a few cases, the error message reports what plugin file is causing the problem so rename or delete the plugin folder, then try login again.

    A post is repeatedly displayed on the blog’s main page
    Likely a problem caused by a plugin so deactivate all plugins and reactivate one-by-one to determine the culprit.

    Getting Warning: gzinflate() [function.gzinflate]: data error when doing the upgrade
    1. Try redoing the upgrade via Tools->Upgrade->Re-install automatically
    2. If that fails, disable all plugins and perform a manual upgrade (see Upgrading WordPress.

    Upgrade causing error 500s
    1. Deactivate all plugins and redo upgrade.
    2. If necessary, perform a manual upgrade (see Upgrading WordPress.

    Blank admin pages after login
    1. Deactivate all plugins. See How to deactivate all plugins when not able to access the administrative menus?
    2. If necessary, rename theme folder in wp-content/themes to cause WordPress Default theme to be place into service

    Blank site after upgrade
    1. Deactivate all plugins. See How to deactivate all plugins when not able to access the administrative menus?
    2. If necessary, rename your theme folder in wp-content/themes to cause WordPress Default theme to be place into service, then see if there’s an upgrade for your theme

    Getting Fatal error: Cannot use object of type WP_Error as array
    1. Problem has been reported with the Options and Structure theme so look for upgrades
    2. Change to the WordPress Default theme if necessary

    Tags are not saved
    1. If you using hyperdb, make sure to update it.

Viewing 15 replies - 76 through 90 (of 111 total)
  • yes I deactivated all pluggins before I tried to upgrade! Should I maybe reinstall the includes from the current version I am running before I upgrade? Where can I get current version wordpress 2.3.2? Any suggestions?

    Ok I reinstalled the includes from a new version of 2.3.2 WP. Now I am getting

    Fatal error: Class ‘Translations’ not found in /home5/theoldfo/public_html/bequiablog/wp-includes/l10n.php on line 408

    I am lost what to do and put back all the includes from my backup so that I could get the site back up.

    @qsch I think you should do a manual install of the latest version.

    FYI, I’m using the Thesis theme and was able to resolve my own drag-and-drop issue with widgets by upgrading to the latest version of Thesis. In my case the plugins were all just fine; the necessary change was to the theme I’m using.

    This isn’t showing up as sticky for some reason, and it took me 4 weeks to find it.

    This should be stickied under trouble shooting also.

    Any suggestion about unable to edit in quick edit fix. 2.8.1 version have same problem. I can’t use quick edit.

    Since this seems to be the 2.8 stickypost, I’ll add to this that the editing of comments in 2.8.2 will cause author urls to vanish. The bug has been patched and the fix will appear in 2.8.3 (or 2.9 whichever is first.)

    Meanwhile it may be safest to avoid editing comments.

    seems more or less, Oops more not less people are having problem with 2.8., believe wp.org should look into this before they release any upgrade in future. i am also going to downgrade to 2.7 series which i found more stable and reliable.

    cheers to all bloggers
    BRIAN

    Not sure where to post this, so I am putting it in couple of spots as the issues this post addresses are popping up all over the place.

    Firstly, for those that can’t drag and drop widgets, and can’t get the screen options menu to respond, you can turn on the accessibility mode manually by logging into the admin panel and entering (your equivalent of):

    https://myblog.com/wp-admin/widgets.php?widgets-access=on

    Secondly, I have been doing some debugging of WP2.8.3 because my fresh (non upgrade) out of the box install of WP 2.8.3 on W2003/IIS6/MySQL 5/PHP 5 with no plugins and default theme and Gears NOT installed in any browser, failed to display a fully functional admin panel for a number of screens. Somethings like Edit worked in FireFox, but not in IE 7 and IE 8. Worse, the screen options menu would not display on any screen, so the option of setting up widgets using the add link was not available.

    In IE7, if you deleted the browsing cache of all files (noting else), the post edit panel, for example, would display correctly (with all the tiny MCE buttons) but once you publish the post, the post content became white space and the MCE buttons would vanish. This then became a permananent problem for new posts and editted old posts. Delete the history again, and you get one ok post edit, then the problems returns after publishing/updating.

    Analysing what was happening showed that when the error occurred an object or function defined in a script referenced by the load-scripts.php call was seemingly not present.

    Various other behaviours on other screens showed similar causes…So I turned on the debuggers on the server and one of the PC’s on my network and loaded the pages through the debuggers and took snapshots of the browser cache in IE7 before and after various operations to see what was going on.

    In summary I ended up fixing everything (except the drag and drop widgets), including the non-displaying screen-options menus by changing the caching rule in the header of the page generated by load-scripts.php to “no-store”. As follows:

    1. Locate the file “\wordpress\wp-admin\load-scripts.php”
    2. Open it in a text editor visual studio or equivalent is preferred, but notepad will do. DO NOT USE MS_WORD or similar word processing tool.
    3. Locate the following line:
    header(“Cache-Control: public, max-age=$expires_offset”);
    4. Comment this line out so it looks like this:
    /* header(“Cache-Control: public, max-age=$expires_offset”);
    */
    5. Add in the following line
    header(“Cache-Control: public, no-store”);
    6. Double check that you have written the above line EXACTLY as shown.
    7. Save the file
    8. Now go to your browser and delete all browser file history (sorry, but this is essential or you won’t see the fix.). On IE 7 you do this by:
    a. From the menu bar: Tools/Internet Options
    b. Select the General tab
    c. Under browsing history choose “delete”
    d. On the window that opens, choose “Delete Files”
    e. Confirm and close windows
    f. Close ALL open browsers and restart the browser.

    So what is going on?

    Well first it seems to me that the load-scripts header is wrong anyway (but that should not be causing the problem). As far as I can see, the code that generates the load-scripts line always adds a random string so that in theory the file reference is unique each time. Hence there is no need to set the browser cache to store the scripts until sometime in 2010, as the scripts reference is different with every call. Having said that, the scripts are pretty small anyway, so compared to an image, the performance gain from caching them is pretty marginal.

    BUT given the reference is unique, it should not be causing the problem that the above solution fixes – but it is definately the case
    that the IE 7 and 8 are caching the script as instructed in original the header, but NOT getting new copies of the scripts when the same page is executed, even though the calling line is notionally different because of the random string added to the ver parameter. Directly instructing the browser NOT to store the scripts file under any circumstances solves the problem.

    Miraculously this fixes practically every display problem in the admin-panel (except for the dragging and dropping of the widgets) – but since the screen options menu is now available you can use the add link instead.

    I will post this in the dev blog as well so that someone who know what they are doing (ie. from the dev team), rather than me who is not really a PHP programmer can look into it.

    Regards
    Jonathan Bishop
    Bishop Bhillips Consulting

    I keep getting this warning when I try to upgrade wordpress, and some plugins don’t be activated like they used to like wp-navi

    Warning: copy(/home/artygirl/public_html/wp-content/upgrade/wordpress-mu-2.8.4a/wordpress/wp-admin/includes/update-core.php) [function.copy]: failed to open stream: No such file or directory in /home/artygirl/public_html/wp-admin/includes/class-wp-filesystem-direct.php on line 131

    Please help I really don’t want to reinstall wordpress, I’ve tried everything, but can’t figure out whats gone wrong? This a fresh install too!

    Thanks
    Judi

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2482873 bytes) in /home/artygirl/public_html/wp-includes/http.php on line 1327

    I am having an issue with the widgets, but it’s not the “drag and drop” issue. My text box widget is completely gone from my list of widgets in the dashboard. I think it disappeared when I upgraded from 2.7 to 2.8. But since then, i’ve upgraded to 2.8.4.

    Does anyone know how to get it back? I am running the Thesis theme. I went to default theme, no luck. Disabled all of my plugins, no luck. I have heard that it’s a database issue, and it’s being hidden, but I am not good with MYSQL and i wouldnt know the command to get it back. Any help would be really appreciated.

    My experience with upgrading WP 2.7.1 > 2.8.4
    As for a lot of people, Tags don’t work any more (there are not shown and it’s impossible to add one). The RSS from www.remarpro.com in the admin page do not work. This update was made with all plugin desactivated.

    If I try a fresh installation of 2.8.4, everything works good. So it’s the update that fails…

    Mi Widgets are all scrambled up, impossible to use: screen capture

    I have tried enabling accessibility mode in Screen options directly or by using https://www.myblog.com/wp-admin/widgets.php?widgets-access=on

    I have not solution and I am quite baffled. This also happened to me on another WP blog I updated.

    OK, I found why I had problems to update: a function in my function.php file was obsolete – trying to create a button in the edition interface. So you can try to active the default theme if you get the same problem as me to see if your theme is not guilty…

Viewing 15 replies - 76 through 90 (of 111 total)
  • The topic ‘2.8 Problems and Solutions (FAQ)’ is closed to new replies.