Not upgrading but Version changing

Hi there

I got this message when upgrading to 7.3.4 as well as 7.3.5, and did not have any scripts show on my screen or have any instructions I need to complete, however my version number has changed to 7.3.5 and before it changed to 7.3.4

Can this be right?

Check Dolphin version in inc/version.inc.php file and in dolphin database, `sys_options` table, check `VALUE` field for `Name` = 'sys_tmp_version' row. These values must match. If they aren't matching then it was a problem with some previous update.

I don't know the current policy but in the past the upgrades changed the version number in the database BEFORE the the upgrade was completed.  That resulted in a wrong version number being stored in the database.  So check the number in the inc/version.inc.php file.  That is probably the correct version instead of what is reported in the database.

If you backed up your database and site files before attempting the 7.3.4 upgrade, then you can restore and try again.  If you need help, send me a PM.

Hi everyone

Thanks for much for answering

I get this:

<?php

$site['ver'] = '7.3';
$site['build'] = '5';

So all seems good

Thank you!

One more thing to check is BoonEx modules versions, they should be all the same and 2nd and 3rd number is BoonEx module version must match Dolphin version.

Dolphin version number in the database changed only AFTER system files and DB upgrade is fully completed, but BEFORE applying modules updates. 

@collarme

<?php

$site['ver'] = '7.3';
$site['build'] = '5';

You didn't specify the version in the DB ?

The number in version.inc.php means nothing except that the last patch you copied over was patch 7.3.5.  Every patch has a version.inc.php file.  It does not mean that the upgrade actually was done properly.  

Checking the DB number will tell you if the upgrade made it to the point where it changes the DB number.

So Boonex doesn't consider the upgrade of the modules as part of the site upgrade?  Why?  I have had an upgrade fail in the module upgrade section.  However, as far as the upgrade was concerned, all had gone well.  Don't you think that the site version in the DB should be done at the very end; after all the modules have been upgraded as well? 

Modules upgrades can be checked separately, each module store the version number in the DB, module version number is changes AFTER module upgrade is completed. 

Let me say this; in the past I have had the module upgrades fail in the middle.  That meant going into the database, find the version number and change it back in order to continue with the upgrade after fixing why it failed in the middle of upgrading modules.  Upgrading modules is not a separate process from upgrading the site, it is all together.  So the upgrade should not change the site version in the database until the very end after all modules have also been successfully upgraded.

 You and Andrew may think differently and you and him are the ones in control.