inra311 Posted March 10, 2015 Posted March 10, 2015 Hello, is it possible to upgrade the full path from v2.2 RC2a to 2.3.4? (I already did the first "big" step and upgraded to 2.3.0, but I am stuck now a bit...) Background: Until recently I ran v2.2 RC2a (plus some security patches) but my provider disabled php 5.2 and updated me to 5.6. My shop did not run on 5.6 but I could switch back to 5.3 which made the shop work again for now. As sooner or later 5.3 will be discontinued, I started the upgrade path to be prepared. I use several contributions so I did not want to start with a new installation but upgrade step by step. I am at 2.3.0 now already and the shop works without any errors :) I wanted to continue and upgrade from 2.3.0 to 2.3.1 next. However, I realized that my upgraded shop is not 100% identical with the files that came with 2.3.0. For example, the upgrade guide to 2.3.1 starts with some modifications of product_reviews.php but my file is similar but not 100% identical to the file that comes with a "real" 2.3.0. So I am not sure if I should put in the new code lines, or will run into big trouble this way. So, what to do? Can I move on, or is 2.3.0 the end for me now? If so, how can I make my shop php 5.5/5.6-ready? Can I use the database.php's from 2.3.2 to use the mySQLi requests (first trials resulted in missing Euro character and login problems...)? Thanks for help!
MrPhil Posted March 10, 2015 Posted March 10, 2015 It's unfortunate that you got suckered in to "upgrading" to 2.3.0. I really wish they would remove that upgrade package, as it leaves you with a hybrid "Frankenstore" that is unmaintainable. Don't try mix and match on old and new files, or try to patch an old osC to be PHP 5.6 ready. It won't be worth the effort. All you can really do is install 2.3.4 (the current version), and consider upgrading that to 2.3.4BS (responsive). You will need to migrate your database level-by-level up to 2.3.4, and bring over your product images. Any add-ons and custom changes will then have to be considered.
bigsteve111 Posted April 8, 2015 Posted April 8, 2015 I have a somewhat similar problem. We are running v2.2 RC2a with a lot of customizations. However, we need to get a responsive design. Our programmer is indicating he can do responsive design on v2.2 with a few features missing but I wonder if 2.3.4BS has enough improvements to make it worth while. Any thoughts?
MrPhil Posted April 8, 2015 Posted April 8, 2015 I would abandon 2.2 and move your data over to 2.3.4 or 2.3.4bs. Some of the customizations or add-ons won't be needed anymore, being built in to 2.3.4. Some add-ons are available for 2.3.4. Some things are done with CSS now. The rest you'll have to decide if it's worth porting the changes over to 2.3.4. If you choose to stick with 2.2 and make it responsive, you're going to find it harder and harder to maintain over time. It will be hard to find help with problems, and the burden of maintenance is going to fall solely on your shoulders. If you've done a good job of security patches and PHP upgrade compatibility, you should at least be fairly safe, but still, is it worth it?
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.