Thread

I am unable to update from 2.1.5 (+MSM) to 2.3.0. The update fails with a blank screen on mydomain/admin.php?C=wizard&M=do_update&language=english&ajax_progress=yes

As mentioned in a previous thread I also tried to update after removing the addons in the third party folder.
When I enable debugging ($debug = 1;) the following error is displayed:

A PHP Error was encountered

Severity: Notice

Message: Undefined variable: resnum_rows

Filename: updates/ud_009.php

Line Number: 160


Fatal error: Function name must be a string in mypath\system\installer\updates\ud_009.php on line 160

Any idea what’s going wrong here?

Hi StudoKong,

Which exact thread are you referring to?
have you also added new MSM files when updating?

Do you have this in your config file?

$config['protect_javascript'] = "n";

Hi John,

I was referring to http://ellislab.com/forums/viewthread/160956/.
The MSM files are updated too (the latest version of MSM that is available for download is 2.1.1 - Build: 20111011).

There’s no

$config['protect_javascript'] = "n";

in my config file.
Any idea what the php error is referring to?

Thanks for the assistance,

Koen

Hi John,

if ($resnum_rows() == 0)

if ($res->num_rows() == 0)

After changing this the update continues until I encounter another error:

Fatal error: Call to a member function result_array() on a non-object in mypath\installer\updates\ud_100.php on line 97

To be continued…

StudioKing, thanks for catching the ud_009 error- got it fixed up for the next release.  The ud_100 error is puzzling the heck out of me, though.  Can you copy paste the query that generates the results through say line 100?

And while I was in there looking- I spotted an error on line 107- should be:

$query = $this->EE->db->query("SELECT * FROM exp_weblog_data");

  foreach ($query->result_array() as $key => $val)

And yes- Pascal just pointed out you’re upgrading from 2.1.5 so those files shouldn’t be run at all.  Are you definitely on 2.1.5?  And if so- in system/expressionengine/config/config.php does your version show as 215?  It should, if that’s what you’re running.

$config['app_version'] = '215';

Running v2.1.5 - Build: 20110510. I have a custom config file, but app_version = 215:

$config['app_version'] = '215';

But, during the failing update process my config file gets overwritten and finally looks like this:

<?php if ( ! defined('BASEPATH')) exit('Invalid file request');

$config['allow_extensions'] = "y";
$config['app_version'] = "009";
$config['word_separator'] = "_";
$config['license_number'] = "";
$config['ud_next_step'] = "";
?>

OK- that explains the 100 error where I couldn’t see it.  Just to see what happens- go into system/installer/updates/ and delete all the update files up to ud_215- you’re on 215, no need for those files.

If that doesn’t do it, I think we’ll want to take a closer look at the config file.

Hi Robin,

The problem was caused by one line of EE1 config variable syntax that got lost in my EE2 config file ($conf[’‘] instead of $config[’‘]).
Deleting all the update files up to ud_215 made me able to update, but still my custom config file got completely overwritten by a default one during the update process. I also did a test with another version of the site without custom config file and here the update went smoothly. So I had a closer look at all the config variables and I finally found the sneaky bastard that caused all this trouble ...

Many thanks for your assistance and for pointing me in the right direction!

LOL- don’t you HATE those sneaky ones!  You can blow an entire day pouring over the file and just never spot it!

Glad you got it squared away.  And hey- I got two bug fixes in for ancient update files, so it’s a win all around.

Give us a yell if you run into anything else!