2.1 vs 2.2CVS

[snipre]

What are the advantages of using 2.1 vs 2.2CVS? Will 2.1 be safer to use or is there not much difference?

 

Thanks

:arrow: Aaron

[Aodhan]

What are the advantages of using 2.1 vs 2.2CVS? Will 2.1 be safer to use or is there not much difference?

 

Thanks

:arrow: Aaron

 

2.1 is a stable release, but it is missing a LOT of the functionality, and new stuff (like some checkout modules), etc. 2.2 is what most of the people are using, even on their live shops.

 

Oh, also a lot of the mods won't work with 2.1

 

Aodhan

[mattice]

I would advise 2.2 any day. It as proven itself on an incredible amount of live shops... compared to 2.1 it is so much better / faster / nicer.

 

But just install them both and decide for yourself.

 

Oh, also a lot of the mods won't work with 2.1

 

Small correction:

 

Oh, only a handfull of mods of the +500 mods on here are intented for 2.1

Development on 2.1 has stopped and not many people make backwards compatible mods...

 

;)

[Guest]

I'm considering upgrading to 2.2 from 2.1 also - are there any differences between the database structures in the two versions?

 

Many thanks.

[Jan0815]

2.2-CVS is the current development version. It has a lot of changes compared to 2.1. The databases might look similar but they are factually very different.

 

All development work is concentrated on 2.2-CVS. All new features are added in 2.2-CVS. It has been a long time since I have seen a contribution for 2.1. And as 2.1 is not maintained any more there is no garantuee it might work with newer version of PHP etc.

 

The drawback of using 2.2-CVS: It is under development. There is no automagic upgrade facility from one 2.2-CVS version to another.

 

Result: Take a look at the current 2.2-CVS and decide for yourself if it fits your needs. If it does - use it. There is no need to "live on the edge". We are working hard to get 2.2 out ASAP. Once 2.2 is released you will have a stable codebase with a defined upgrade path to newer versions.

 

But all of this boils down to: If 2.2-CVS does what you need - use it and start running your shop. No need to update each and every single change we make.

 

HTH

[Harald Ponce de Leon]

But all of this boils down to: If 2.2-CVS does what you need - use it and start running your shop. No need to update each and every single change we make.

 

Beautifully said :D

 

It is a good idea however to sign up to the tep-bugs and/or the tep-commits mailing list to be notified of code changes (very very little has been commited this month but will be picked up next month). This way you can add the changes to your store that may fix possible bugs.

 

If you have "thoughts" on using 2.2-CVS due to implementing code changes, I'd suggest to look at the mailing list archives to get a feeling of how it works. All I can say is "dig in!" and these "thoughts" will be answered either to your favour or not in your favour; the main thing is concluding these "thoughts" with a definite answer.

[ippo]

If 2.2-CVS does what you need - use it and start running your shop. No need to update each and every single change we make.

 

HTH

 

But how do can I update my shop when the final version is done?

I want to update it because I read something about the security issue of register_globals in the php-manual. I am now trying to customize 2.2-CVS to my needs but when there are some changes made which I could use, how do I update it? Just dl the package again and see what changes there are made and then copy and paste it to my customized version?

 

Many thanks,

Ippo