Upgrading From OSCMax 2 RC3 And Question About 2.1 Features

**cabobrian** · 01-11-2011, 06:32 PM

I have a site for a client that is Version 2.0 RC 3, or so it says in the Admin screen. On the home screen of the OSCMax web site, Michael lists some new features in version 2.1. I have not had a need to upgrade and everything has worked great, that is why I'm behind on my versions. But now I need the "Must Accept Terms" option that is listed in 2.1. So I have two questions:

- I do not see a version 2.1 in the list of available versions to download. Do I need to wait until 2.5 comes out?
- I have created a test database to try out the upgrade path and am not having much success. I download 2.0.25 and am trying to run the first upgrade, RC3-to-stable. I get a lot of table does not exist and column does not exist errors. Is there a previous upgrade file I am missing?

Thanks!

Brian

EDIT: Ignore my second question about the RC3 database not upgrading. I figured out my problem. I was using the data from an old osCommerce database instead of my RC3 database.

**ridexbuilder** · 01-11-2011, 11:37 PM

Release Candidate (RC) software is not intended for permanent production use - that is obsolete and should've been upgraded to a public release as soon as available.
2.1 - now 2.5 hasn't even become RC and is still Beta. As such, you are not advised to use in a production environment.

2.0.25 is the current public release.

**ridexbuilder** · 01-11-2011, 11:39 PM

Originally Posted by cabobrian

Version 2.0 RC 3 ... everything has worked great...

You've been sitting on a time bomb!

**met00** · 01-12-2011, 06:24 PM

I'm shocked that it's a still working site as there is a known security problem and most s.0 have been upgraded with the patches or have been hacked.

**cabobrian** · 03-14-2011, 07:10 PM

Okay, I get it. RC3 was not a stable release. I got it upgraded to 2.0.25 without any issues. But what I really need to know is an estimated time when the next release is available. I need the "Must Accept Terms" functionality for one of my customer's websites. I need to decide if I'm going to have to customize the solution or wait until the next version comes out. I would really rather not customize anything because it makes it more difficult to track changes when upgrading to the next version. Any ideas???

Thanks!

**michael_s** · 03-14-2011, 07:38 PM

We are aiming for The first week in April for the release candidate which would be considered usable in production, but things are still fluid so that could change.