impossible to 7.1.6 to upgrade my dolphin
7.1.6-7.2.0 | Update can not be applied |
impossible to 7.1.6 to upgrade my dolphin
http://mysite.com/upgrade : error
BoonEx Dolphin Upgrade Script
| ||||
Most likely this is due to a mismatch between the version in the header.inc.php file (version is in that file for 7.1.6 but changes to version.inc.php in 7.2) and the value stored in the database. Geeks, making the world a better place | ||||
http://mysite.com/upgrade : error
BoonEx Dolphin Upgrade Script
Connect administration database query error header.inc.php file : <?php $site['ver'] = '7.1';
$site['build'] = '6'; version.inc.php file : <?php $site['ver'] = '7.2';
$site['build'] = '0'; and site : upgrade to dolphin 7.2
| ||||
I am not sure what you are trying to say. Boonex moved site version information to a version.inc.php file to help solve some issues with people forgetting to manually edit the header.inc.php file after upgrading. What I was stating was to find out what is the version for your site stored in the database. Geeks, making the world a better place | ||||
I said that when I'm on the site , the site is dolphin upgrade to 7.2 but when I connect to the Administration I have an error "database query" and also when I am not connected in that I footer " Copyright © 2015 Your Company . " whereas when I connected I have this, " Copyright © 2015 MySite as I can see the dolphin version of the database? | ||||
OK, the different information in the footer is curious; first make sure that all browser caches have been cleared and also clear your site caches as well through the admin panel, Clear the /cache and /cache_public directories making sure to not delete the .htaccess files. Once all caches have been cleared, see if the footer discrepancies disappear. Geeks, making the world a better place | ||||
The site version in the database is/was located in sys_options Geeks, making the world a better place | ||||
I said that when I'm on the site , the site is dolphin upgrade to 7.2 but when I connect to the Administration I have an error "database query" and also when I am not connected in that I footer " Copyright © 2015 Your Company . " whereas when I connected I have this, " Copyright © 2015 MySite Looking back through the topic I don;t see where you stated that, you stated you got an error message that you could not upgrade Geeks, making the world a better place | ||||
yes when I want to upgrade the site I error, but when I log on to the site home page of the site or other site is at version 7.2 I cleaned "cache , cache_public , tmp" always the copyright issue `sys_options`
| ||||
OK, it seems then that a partial upgrade may have happened. The database is saying you are at version 7.1.4; that gets set during upgrades when you run the patch. This: header.inc.php file :
$site['ver'] = '7.1';
$site['build'] = '6'; is saying the site is at version 7.1.6. So my guess is that something did not go correctly in the upgrades to 7.1.6. First step is for you to backup all your site files and your database. That is important so you don't lose anything at this point. If you have modified core files, upgrading becomes more difficult; so that is important to know. Others may need to come in with their suggestions. My suggestion is to first backup the site files (all of them) and database. Then I would go back through the updates, starting with the 7.1.4 to 7.1.5; then the 7.1.5 to 7.1.6. Check the database version after each upgrade to make sure it is being written to the database. Geeks, making the world a better place | ||||
GG said earlier... Boonex moved site version information to a version.inc.php file to help solve some issues with people forgetting to manually edit the header.inc.php file after upgrading. Others may need to come in with their suggestions.
My suggestion is to first backup the site files (all of them) and database. Then I would go back through the updates, starting with the 7.1.4 to 7.1.5; then the 7.1.5 to 7.1.6. Check the database version after each upgrade to make sure it is being written to the database. the other day when I mentioned the site with the upgrade folders left; viewing the upgrade page gave the option to upgrade from 7.1.5 to 7.1.6 changing the header.inc.php of course after each time. Then was able to do all three upgrades from the same upgrade folder. Keeping all the data. Of course I made full backups of the server beforehand. Guys, before you do any type of test, please clone your site into a subfolder and do the changes GG posted about. GG, if you remember that post link to it please. I just read it yesterday.
There are many problems with the upgrade, like I ran into. Original site install process strictly suggests to change the permissions on the /inc folder, if you don't remember doing it your in trouble. Files will not be uploaded to that directory and will cause many problems. ManOfTeal.COM a Proud UNA site, six years running strong! | ||||
Then was able to do all three upgrades from the same upgrade folder.
That is interesting as some suggested that problems with upgrades often happened because the upgrade directory was not removed between uploading the different patches. Geeks, making the world a better place | ||||
Geeks, making the world a better place | ||||
That is interesting as some suggested that problems with upgrades often happened because the upgrade directory was not removed between uploading the different patches.
Yes it is, the site was at 7.1.4, had the three links. Upgrade .4 was enabled, then after it, .5 was enabled, and then on the .6. Then of course navigating to a different browser cured the UNI template problem to go to 7.2. I'm amazed that site has no errors. It was not a modified site like most. ManOfTeal.COM a Proud UNA site, six years running strong! | ||||
OK, it seems then that a partial upgrade may have happened. The database is saying you are at version 7.1.4; that gets set during upgrades when you run the patch. This: header.inc.php file :
$site['ver'] = '7.1';
$site['build'] = '6'; is saying the site is at version 7.1.6. So my guess is that something did not go correctly in the upgrades to 7.1.6. First step is for you to backup all your site files and your database. That is important so you don't lose anything at this point. If you have modified core files, upgrading becomes more difficult; so that is important to know. Others may need to come in with their suggestions. My suggestion is to first backup the site files (all of them) and database. Then I would go back through the updates, starting with the 7.1.4 to 7.1.5; then the 7.1.5 to 7.1.6. Check the database version after each upgrade to make sure it is being written to the database. merci geek_girl, en avec les update de 7.1.4 to 7.1.5 / 7.1.5 to 7.1.6 / 7.1.6 to 7.2 it works |