4 replies to this topic

[Dorado]

I have been trying to understand the best way to upgrade my site from 2.2rca2 to a newer version. I just read that 3.0 was released over a year ago. Some say it is not to be used as functionality is not all there, etc, etc.  

I use a Template (2.2 monster template) that has worked wonderfully for the price I paid. I have upgraded it with some add-ons, etc over the last two years. Originally, I just wanted to have social add-ons but did not want to use the radius solution.

I can do an SQL upgrade of the database no problem adding new tables and extending the variable length to 255, etc.

After trying to upgrade to 2.3.1 unsuccessfully I am now confused.

My issues:

1) I can install a clean copy of 2.3.1 but lose all my data, images, template, etc. Seems like I just have them in the wrong folders for access.

2) Some forum topics say it is NOT POSSIBLE to upgrade using templates from 2.2 to 2.3 - I question this

3) Then there is 3.0...it appears to have been released in Mar 2011. So why would I not want to upgrade to this?

Any input would be great. For now, I would just be happy linking to FB with customers able to have live FB input, liking, etc. The rest can wait unless it can be done simply.

Thoughts? Suggestions?

Thanks

[npn2531]

Are  you working through this list?
http://www.oscommerce.info/confluence/display/OSCOM23/v2.2+to+v2.3.0

If you do the items marked (SEC) you at least have the updated security features. Lots of the other stuff you don't need since  you are using a template.

[FWR Media]

The above sounds good, ignore 3.X given your question.

[MrPhil]

Dorado, on 14 July 2012 - 09:41 PM, said:

1) I can install a clean copy of 2.3.1 but lose all my data, images, template, etc. Seems like I just have them in the wrong folders for access.

Whatever you do, back up your files and database first, so that you can at least get back to where you are now. You can certainly install a clean copy of 2.3.1, modify a backup (.sql file) of your current site (where the database schema is a bit different), and import the data. Images can just be copied over to the right place. Template information is not going to come over to 2.3.1 -- you will probably lose it. The bottom line is that you can have a 2.3.1 store with your current data and products, but the amount of work involved may be more than you want to put in, particularly if your current template is heavily modified from stock osC 2.2.

You can always make a "/test" or "/dev" directory, install 2.3.1 with a new database, and import your old database and files and see how it looks. You will of course lose any template-specific features, but you can look around in the "add-ons" area to see if there's something useful there. Many templates simply package up add-ons from osC, so you may find a match. You can tweak the CSS for 2.3.1 to get it closer looking to your desired store (see "ThemeRoller"), but keep in mind that the display side of osC 2.3.1 is written quite a bit differently than in 2.2.

Quote

2) Some forum topics say it is NOT POSSIBLE to upgrade using templates from 2.2 to 2.3 - I question this

It's always possible to upgrade, but it may be more work than you're willing to put in (i.e., the automatic process may be able to do very little of it). Just try it, in a test environment separate from your current store (so there will be no interference). If it doesn't work out, you're only out some time.

Quote

3) Then there is 3.0...it appears to have been released in Mar 2011. So why would I not want to upgrade to this?

No, no, no, no, no. It is still only a developers' sandbox. It is nowhere near ready for production use, especially by non-experts. Pretend you never heard of it.

[multimixer]

Dorado, on 14 July 2012 - 09:41 PM, said:

2) Some forum topics say it is NOT POSSIBLE to upgrade using templates from 2.2 to 2.3 - I question this

You can follow of course the upgrade process and do the SEC items first or at least as @npn2531 said.

In any case, the result of the upgrade is not equal to a new, fresh 2.3.1 store. You'll have a "hybrid", something in between the versions. That's good enough I guess