Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Unexpected issues 2.2MS2 to 2.3.4 - heavily modified cart


yomama360

Recommended Posts

Probably already been answered 100 different ways. I did all searching and reading I could think to do, so forgive me if this is a stupid question. If it's been answered, please point me to the answer.

 

What are some major issues we will encounter upgrading from 2.2MS2 to 2.3.4?

 

We are updating a heavily modified cart. Many of the mods are of our own making (or tweaking). We did a fresh install of 2.3.4 an are applying our mods on top of that. Now we are trying to smooth out the bugs. But easier said than done.

 

Recent example was the functions that call "mysql_" being changed to "mysqli_" across the whole application. It took us quite a bit of time to even realize that was what was messing us up on one bug.

 

Perhaps it's too broad of a question, but what other things like that should we be aware of?

 

By the way, would it be safe to just change everywhere it says "mysql_" in our mods to "msqli_" ?

"The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself.

Therefore, all progress depends upon the unreasonable man."

-- George Bernard Shaw

Link to comment
Share on other sites

 

By the way, would it be safe to just change everywhere it says "mysql_" in our mods to "msqli_" ?

 

Not quite, you will need to do some other changes too since mysql_ and mysqli_ differ abit in how connections are made.

 

The easiest way to make sure you mods work now as well as in the future is to use the oscommerce db functions, from includes/functions/database.php

Link to comment
Share on other sites

Your situation is a good reminder for why you need to keep careful track of which add-ons (and in which order) you add to a store, and why (what new feature you're getting). The same goes for any custom coding. The idea is that you can check your list against what's been added to the 2.3.4 base, avoid duplicating existing features, and properly select from available add-ons. Failure to keep track of what has been done to your osC code means overlooking features you want to add, and trying to add unnecessary (already built-in) features.

 

It's always risky trying to install add-ons intended for 2.2 to osC 2.3, as there are considerable differences in the base code. If you determine that you still need to add that feature, and there's not a 2.3 version available, you need to thoroughly understand how the add-on works and how it will likely interact with the 2.3 level base. The point is that you can't simply slap on a 2.2 add-on to 2.3, and expect to patch any minor incompatibilities (e.g., mysql_* to mysqli_*), and have it work fine. Considerable editing may be needed to bring the add-on up to date and make sure it doesn't have unexpected side effects.

 

By the way, I wouldn't say you're upgrading from 2.2MS2 to 2.3.4, so much as you're starting afresh with 2.3.4 and migrating your existing data and a number of modifications to the new code base. "Upgrading" implies step-by-step incremental code changes to bring the "base" code up to 2.3.4, which incidentally, will badly break going to 2.3.

 

Finally, it's a good idea to keep reasonably up to date, even if your store seems to be working fine. The further you fall behind in your base osC installation, the harder it will be to catch up when you finally have to upgrade. I would suggest not falling behind the current level by more than a couple minor upgrades, or a year or two, whichever comes first. It's more work for a working store, but in the end it will pay off by keeping your store up to date (security, PHP level) and much easier to upgrade in the future.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...