Upgrade 1.5 > 1.5.1

So far so good here!

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!

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

??

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

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

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.

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.

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: https://asymptomatic.net/wp-hacks
Description: This plugin calculates statistics for a WordPress weblog.
Author: Owen Winkler
Version: 1.0&beta; build 6
Author URI: https://asymptomatic.net
*/
?>

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

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.

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

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.

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!

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.

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.

miklb – sorry – I should have slung a few smilies in there ??
Hopefully people will at least skim the whole thread before upgrading if they are worried, and hopefully all upgrade issues are kept in this thread too so as to not lose other forum posts.

And thanks to everyone for adding all the useful information to the thread !