Upgrade, modules still show old version...

Just as the title states.

I'm working on an upgrade today, going from 7.0.8 to current at 7.1.5

The upgrade went well with one error, it was related to this topic.

http://www.boonex.com/forums/topic/upgrade-from-7-9-to-7-1-problem-help-please.htm

After correcting the database, and starting the Dolphin-Patch-v.7.1.0-Cumulative, again, all the updates went fine.

Clearing the caches each time then proceeding with the next update... I didn't see the need to check each version updated in the modules list.

The problems are strange to say the least and I need some suggestions.

A lot of the language files are missing; that is related to the modules still being at version "1.0.9" which is the last ones for 7.0.9.

Looking at the installed modules, they all showed versions 1.0.9 except for the ones I had to remove like the events module was 1.0.9, now 1.1.5; I could only get the modules to show and function in 7.1 by un installing them and re installing.

Example, the videos module would show the old version on the site side as well in the admin page.

I'm almost sure there in not much to do except redo the modules or start the update again from a backup.

Open for all suggestions.

I also just noticed I have two Members links in the admin!!!

WTF

[edit] OK, that was some extra links made before the upgrade.

As a reminder of those still upgrading sites, if you have added an extra link to a module in the navigation menu the update from 7.0.9 to 7.1 will fail.

I notice the b on the version numbers.  Did you apply the beta versions because they were not suppose to be applied.  Boonex should make that clear, I was told I could do it myself but this is the responsibility of Boonex.  The beta upgrades only need to be applied if one had started at a beta and needed to update from that beta.

So there is no fixing this one.

The the error caused many more hidden problems.

Why did it allow the ones after the initial error?

Oh well, work lost. Start again now knowing what to expect.

My apology, I did not see the image clearly; after looking closer that was "by" and the line was over the y.

However, if you did apply any beta updates then yes, they should not have been applied.  If you did not apply any beta updates, then something else is the reason.

Something went wrong with the update of the database for the version number.  In the upgrade folder there is a sql.sql for each of the modules.  That sql changes the version number dependent on the old version number.  For example, this is from the 7.1.4 to 7.1.5 upgrade.

-- update module version

UPDATE `sys_modules` SET `version` = '1.1.5' WHERE `uri` = 'blogs' AND `version` = '1.1.4';

So if at some point that failed, then all that follows would fail.  Say that at some point the 1.1.4 did not get changed in the database, then when that query runs, it will not find the version equals 1.1.4 and thus not update the module to version 1.1.5.  I am not saying that is what happen but just how it is suppose to work.

As you saw with the modules that you were required to remove, most likely the files were uploaded.  You can check the config.php file in the module's install directory and see what version is stated:

'version' => '1.1.5',

If it was just a version number error in the database, you could fix the reported version number by doing a query; however, I would start over if it was me because I would worry about what else failed in the upgrades.

If i was you, i would revert back to 7.0.8 from your back before you started. assuming you did make a back up...

i would then correct the database issue you had to begin with...

then start the upgrade process from again.

If not this person is going to have issues with there site from here on out.

Edit:  never mind i see your last post.

 That's where we are at right now...

Thanks everyone.