WordPress.org

Ready to get started?Download WordPress

Forums

Upgrade 1.5 > 1.5.1 (204 posts)

  1. cyberhomie
    Member
    Posted 9 years ago #

    How can I disable BAStats after I already upgraded, but I can get to any of the pages? Is there a way to manually disable it?

  2. userx
    Member
    Posted 9 years ago #

    I initially got a blank page too, until I ran upgrade.php and all is humming along quite nicely now. Thanks for the hard work all.

  3. cyberhomie
    Member
    Posted 9 years ago #

    everything is uploaded, cleared the cache - tried viewing from a diff machine also - nuttin

  4. Mark (podz)
    Support Maven
    Posted 9 years ago #

    cyberhomie: Try renaming the plugin file ? That should stop it loading

  5. NorthernPassages
    Member
    Posted 9 years ago #

    I think there might be a problem with Asymptomatic's latest release of Exhibit as well, but i can't be sure. Anyone else have any issues with it?

  6. Matt Mullenweg
    Troublemaker
    Posted 9 years ago #

    Go directly to your admin and try activating a different theme. To deactivate a plugin you can delete it or rename it.

  7. lbessant

    Posted 9 years ago #

    Mmmmmm :-). Seems to be working so far. Haven't played with all plugins, but my main functions are just fine, and both trackbacks and pingbacks are now working as advertised on Dreamhost - thanks to the devs for sorting that out, and of course to Podz for the test site[1].

    And a word of advice if I may - people, if you're going to edit core files, *keep a record* in a text file. Saves a lot of pain later.

    [1] And for everything else he does here :-)

  8. tbrams
    Member
    Posted 9 years ago #

    Sh*t!

    My website just doesn't work anymore after the upgrade. I cannot even login to the admin part. It looked so promising, but there must have been some compatability issue with wp_users_online that I used.

    That is probably the most disappointing upgrade I have ever made.

    The error message is:

    Fatal error: Call to undefined function: get_currentuserinfo() in /customers/brams.dk/brams.dk/httpd.www/wordpress/wp-blog-header.php on line 169

    Let me know if there is anything I can do to avoid starting from scratch again.

  9. cyberhomie
    Member
    Posted 9 years ago #

    I put a # before the BAStats folder (renamed it) in pluggins and that fixed it

    Thanx for the help guys

  10. ArmageddonDesign
    Member
    Posted 9 years ago #

    I used this guide (mostly, I got lazy and just used my ftp overwrite on the root files) and everything is running smoothly. *thumbs up*

    Also, like I said, I used overwrite on the root files and it worked for me, but it might not work for you. Follow the guide to the letter. :)

    Edit: btw... if you use dropdown_cats with the code edit to template-functions-category.php, the code to comment out is now on lines 196 and 215 (not 208 and 227 as it states in the codex).

  11. jpettit
    Member
    Posted 9 years ago #

    tbrams...just roll back to your v1.5 backup...

  12. dolmarit
    Member
    Posted 9 years ago #

    Change the width back from 99% to 95% in wp-admin.css
    then it is better viewable in IE explorer to.
    Search for the following line.

    #template textarea {
    font: small 'Courier New', Courier, monospace;
    width: 99%;
    }

  13. sbrumb
    Member
    Posted 9 years ago #

    I ran into the same error as you, tbrams. It turns out that I forgot to do step 7; after doing it, though, everything worked fine.

  14. schulte
    Member
    Posted 9 years ago #

    podz,

    Item #3. In my version of wp-images for WP 1.5, I was missing get-firefox.png -- it was coming up as a broken image after upgrading. Not sure if anyone else experienced the missing png file...

  15. tbrams
    Member
    Posted 9 years ago #

    I am confident that there is a severe compatibility problem with the wp_list_user plugin. I have rolled back to 1.5 to disable this and attempt to upgrade again.

    Sorry for the panic - it's not the kind of surprise I was expecting just before going to bed (It's 2 mins past midnight here in Denmark).

  16. bwahahax
    Member
    Posted 9 years ago #

    vkaryl: Yes, I cleared and refreshed the cache.
    podz: I don't use any of the themes. Back in the pre-theme day I wrote my own index page and haven't used the theme system at all.

    And I did run upgrade.php.

  17. chrisgeleven
    Member
    Posted 9 years ago #

    So far so good here!

  18. kinkistyle
    Member
    Posted 9 years ago #

    The Exhibit gallery is not working with 1.5.1. Apparently it is calling a function called get_currentuserinfo() that has been moved over to the new pluggable_functions.php file and is not finding it. Disable that plug-in before upgrading!

  19. tbrams
    Member
    Posted 9 years ago #

    After disabling the troublesome plugin that was calling get_currentuserinfo() the upgrade went just fine.

    Looks great - thanks for all the hard work and for making sure that you reminded all of us to back up the existing tables as step 1 in the upgrade guide

    :-)

  20. lbessant

    Posted 9 years ago #

    Which version of Exhibit are you using? Mine seems fine (I'm using Exhibit 1.5d)

  21. kjarrett
    Member
    Posted 9 years ago #

    >>>
    The risk is not yet public knowledge.
    <<<

    Well, ok then. Motivation enough for the upgrade. Just did three sites, instructions were flawless. Excellent work, ladies and gentlemen. Thank you!

    -kj-

  22. theglobalguy
    Member
    Posted 9 years ago #

    Here's another instance of Exhibit not working with the new version. I'm running the latest (asy) version from his website. I'm guessing that there is an easy fix to point it to the file that has the get_currentuserinfo() function, but I haven't had a chance to look too far into it.

  23. kinkistyle
    Member
    Posted 9 years ago #

    I fixed teh Exhibit bug by simply delving into the exhibit10.php plugin file and adding this line right before the get_currentuserinfo() call:


    $incfile = 'wp-includes/pluggable-functions.php';
    $c=0;
    while(!is_file($incfile))
    {
    $incfile = '../' . $incfile;
    $c++;
    if($c==30) {
    echo "Could not find pluggable-functions.php.";
    exit;
    }
    }
    require_once($incfile);

    So dirty. So hacky. Whatcha gonna do right?

    There is a similar piece of code directly above the get_currentuserinfo() call that does the same thing when looking for wp_config.php. Apparently the creator of Exhibit used a lot of dirty hacks too ;D

    I am only keeping Exhibit around for old "legacy" posts that used it as I call most of my new photos from Flickr Gallery now.

  24. If you forgot to disable a plugin that has ben mentioned to cause errors after the upgrade (IOW, you can't get to the plugin panel to disable it), download the plugin file, edit so that it only has the plugin header, and upload the edited file. You should be able to disable the plugin now.

    For example, BA Stats would be:
    <?php
    /*
    Plugin Name: BAStats
    Plugin URI: http://asymptomatic.net/wp-hacks
    Description: This plugin calculates statistics for a WordPress weblog.
    Author: Owen Winkler
    Version: 1.0&beta; build 6
    Author URI: http://asymptomatic.net
    */
    ?>

    And, Entity2NCR would be:
    <?php
    /*
    Plugin Name: Entity2NCR
    Plugin URI: http://guff.szub.net/entity2ncr
    Description: Converts &raquo; and the like to their numeric equivalents.
    Version: 0.1
    Author: Kaf Oseo
    Author URI: http://szub.net
    */
    ?>

  25. theglobalguy
    Member
    Posted 9 years ago #

    That works...I just fixed it another route by copying the function get_currentuserinfo() and get_userdatabylogin() from pluggable-functions.php to functions.php. I think kinki's is the more elegant approach though, especially as it seems that exhibit development has pretty much progressed as much as it's going to go.

  26. vkaryl
    Member
    Posted 9 years ago #

    Due to the remarkably clear instructions, I just upgraded my four installs with zero problems.

    Thanks podz. And thanks to the developers for getting this out.

    [[Guess I should have noted that of all the plugins I use, the only one I had a problem with was one for which I forgot NOT to delete a data file in the WP root folder. Had to reupload the file, all is fine.]]

  27. Michael Bishop

    Posted 9 years ago #

    Maybe it's just me, but perhaps you want to clarify steps 5 and 7. The way I read it the first time, the only files to change were the directories outlined in step 5. You skip to talking about themes in 6, and then mention "files" in 7. It may be easier to just say Delete and replace everything except the config file and the content directory, including all files within wp-admin and wp-includes.

    Could have just been me though.

  28. TigerTor
    Member
    Posted 9 years ago #

    Guys, one quick question about theme:

    If I'm using my own theme, when upgrading from 1.5 to 1.5.1, should I do any change on my theme files?

    I'm asking this because I've been told that you've done some changes on "Classic" and "Default" theme files.

    Thank you!

  29. Mark (podz)
    Support Maven
    Posted 9 years ago #

    TigerTor - No.
    If your theme works, do not feel that you must update the default and classic themes. It is entirely optional.

    Miklb - I'm aware I could have written it somewhat better.

  30. Michael Bishop

    Posted 9 years ago #

    podz, I was not trying to correct you, I was simply trying to convey a sense of confusion, as to perhaps prevent someone else's.

    Regardless, thanks for the thread.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags