Why didn't this mistake break my update?

[budfox100]

Hi all.

I just made a silly mistake, and used a full package rather than an upgrade package to update from 2.5.16 to 2.5.22 - I'd have assumed that this would wipe a lot of main files and really mess up things, taking the site back to a pre-install status. However, it seems to have worked fine.

I don't like to just assume that everything is OK though, so could someone let me know why this worked, or if I should restore a backup and do the upgrade properly.

Thanks
Steve

[wwtn]

Steve,

As long as you did not have any Joomla core files edited or modified in your v2.5.16 installation, there shouldn't be any negative consequences installing the full v2.5.22 over it. Just copying the core files, whether or not you use the full or updated version, does not alter or edit the actual database tables. That's assuming that you did not actually perform an actual full on re-installation of the entire Joomla system.

But if you did have any files or scripts that you made changes to in the previous Joomla v2.5.16 installation then, yes... Not ideal that you applied the full version versus the update version of Joomla when you upgraded your website. Any core files that were previously edited or modified by you manually, have likely been overwritten by the newer version files.

I'm curious as to why you apparently didn't (or possibly couldn't) use the internal upgrade option available within the Joomla administrator back end interface. That's the easiest way to apply an upgrade to a newer version of either a Joomla v2.5 or v3.x installation.

Jim

[budfox100]

Hi Jim, and thanks for taking the time to reply.

I never modify core files, so no worries there. Here's the full story:

I'm looking after three sites, all similar but in three different languages. I used the standard method to update two of them, but they both seemed to stick at the stage after the upload where the files were being unpacked. (I waited a LONG time). Of course I was uploading the full package rather than the upgrade version.

I then logged out and in again to see that 2.5.16 was still being reported, so I assumed that things had failed. I then just did an FTP of the extracted package to the third site, over-writing what I thought would be just some of the files (the way I've upgraded a few times in the past). Once that was done I looked at admin and was greeted by the install screen. Not surprising really... after all, I had effectively wiped the original files.

So then I looked at the first two sites, and they were both reporting 2.5.22 (having closed the browser and restarted). This surprised me because having just wiped a site with the same files via FTP, I couldn't imagine that making the same mistake via the installer would be any less disastrous. However, they do seem fine.

I've always had mixed fortunes with the installer for Joomla updates, and I normally resort to FTP. My Joomla 3.x sites update without issue though.

So all in all a bit weird, but maybe you can explain things...

Thanks
Steve

[leolam]

When you have accidentally have overwritten the files with the full package the only thing you should need to do is remove the "installation-folder" and you are good to go.

So next time go to Joomlacode.org and download in this specific case "Joomla_2.5.22-Stable-Update_Package.zip" That file (is always the biggest one in the file system) is a full package without the "installation-Folder"

You can do this way easier btw and use the Joomla automated upgrade or use the "install from url" and paste the link (in this case http://joomlacode.org/gf/download/frsre ... ackage.zip) in the box and hit "install" Your Joomla installation will than download the package and install it

Leo

[budfox100]

Thanks for all the help. I shall remove that folder in a moment.

Kind regards
Steve

[wwtn]

Steve,

Leo is 100% correct. Since you FTP'd up the full installation, the "installation" dir would be put up as well. That's a "no-no" to leave online and during a normal fresh install of Joomla, you're alerted to that fact and asked to delete that dir.

As for problems related to installs or upgrades "stalling", that likely is related to memory and/or resource usage limits that are set too low or restrictive by the web host. It could also be related to the particular web browser you're using. Try a different browser and if you're still having incomplete install issues, inquire with your web host about raising memory and/or resource usage limits.

Just remember to use Joomla update/upgrade packages and not the full install package when upgrading your installations. Those update/upgrade zip files are much smaller and lighter filesize wise, so that may eliminate any "stalled" attempted upgrades when using the Joomla backend installer.

Jim

[budfox100]

Thanks Jim.

I did know about the installation directory, but my reaction to seeing the install screen was that I'd over-written all sorts of files. Of course, the config files don't get changed, and nor does the custom template, and nor does the database. If I'd thought a bit longer I'd have realised.

Won't make the same mistake again, and in fairness to me I've been updating sites since 2008 and this is the first time I've made such a schoolboy error.

Kind regards
Steve

[wwtn]

Steve,

No worries. No matter how "bright" we may think we are, all of us have moments when the "lights go out". Just glad your sites are fine, that's the main thing.

Jim