Why Switch? Compare v1.3.9 & below v1.5.

Here's the deal: I sell tshirts. I NEED Stock-by-attribute and other add-ons.

Please correct me if I'm wrong but a lot of add-ons like stock by attribute do not work properly with v1.5 at the moment, right? I can not run my store without these add-on, so why should I ever consider upgrading to v1.5?

I really can't find any solid documentation/comparison between v1.5 and v.1.3.9 & below. If I can't get v1.5 to meet my business needs I'm seriously considering switching everything back to v1.3.9 or below.

What MAJOR concerns should I really be concerned about switching back to a earlier version than v1.5? (I.e security, bugs, flaws, etc.)

Please do not get upset/angry/ or flame on me, just put yourself in my shoes and understand my business needs & frustrations n hurdles I've encountered with the newest version of zen cart.

Thank you in advance.

Reading between the lines here, are you saying that you have upgraded your live site and suddenly it's missing something important ... instead of testing it first to be sure everything's good before going live with the new version?

I've not started my live site yet.

I've been learning how to use Zen-Cart since 1.3.X on my test server and all of the plugins work well. I've been teaching myself how to use zen-cart so when it goes live, I'll be ready.

So I tried giving 1.5 a shot on my test server and its been a night mare. I've been trying to find reasons not to go back but it is not easy. Is there a reason why v1.5 doesn't have Stock by Attributes or something like it embed into the code already?

My main concerns are, "Is v1.3.9 as secure as v1.5?"

g00glethis1:

My main concerns are, "Is v1.3.9 as secure as v1.5?"

v1.3.9 is secure. v1.5 is even more secure. Ergo. No.

I've been learning how to use Zen-Cart since 1.3.X on my test server and all of the plugins work well.

As RodG said, 1.3.9h is secure. If your desired plugins don't work with 1.5.0, you should just stay with 1.3.9h until they do.

So I tried giving 1.5 a shot on my test server and its been a night mare.

I've installed 1.5.0 dozens of times and have never had a glitch, much less a nightmare. I assume you're talikng about getting 1.3.9 mods to work on 1.5.0 ?

Is there a reason why v1.5 doesn't have Stock by Attributes or something like it embed into the code already?

I can't speak for the developers, but it seems like the overall approach is to leave the core code as lean as possible and use the community-provided modules for features that not everyone needs, like the ones you mentioned. I agree with that approach.

I'm not a coder, so I don't understand the details, but what I've read suggests that the reason many mods that work in 1.3.9 don't work in 1.5.0 has to do with the way modules are 'registered' (don't even know what that means) in Zencart admin. If that's the case, I guess I don't understand why porting STA to the latest version has been such a problem.

stevesh:

I'm not a coder, so I don't understand the details, but what I've read suggests that the reason many mods that work in 1.3.9 don't work in 1.5.0 has to do with the way modules are 'registered' (don't even know what that means) in Zencart admin. If that's the case, I guess I don't understand why porting STA to the latest version has been such a problem.

This is not the issue with SBA. That's why it's such a problem. :)

SBA modifies a bunch of core files and these changes would need to be merged with their 1.5.0 counterparts. This hasn't been done yet.

My guess for Stock by Attributes would be that since it makes a lot of database changes, and accesses and edits db content during operation, it may need significant functional changes to be fully secure in the v1.5.0 environment of PCI compliance.

...Plus merging mod files with changed core files, of course:)

gjh42:

My guess for Stock by Attributes would be that since it makes a lot of database changes, and accesses and edits db content during operation, it may need significant functional changes to be fully secure in the v1.5.0 environment of PCI compliance.

...Plus merging mod files with changed core files, of course:)
The only "significant" DB change I am aware of is the addition of a table to store stock for the product variants.. I don't think SBA makes many other DB changes.. Of course I am going from memory and would have to look..:laugh:

If it is not a tough job, hopefully someone familiar with it will update it for v1.5.0 soon...

Oh yes, creinold did that: Stock by Attributes 5.0 Beta (for v1.5.0) Check there for more current info.

gjh42:

If it is not a tough job, hopefully someone familiar with it will update it for v1.5.0 soon...

Oh yes, creinold did that: Stock by Attributes 5.0 Beta (for v1.5.0) Check there for more current info.
SBA has bigger issues.. There are about 4 or 5 different variants built off Kuroi's last stable release (v4.7) floating around out there and each is problematic in different ways.. There is only one of these variants that someone has made an attempt to update for v1.5, but it is not without it's issues (I personally found it unusable for my clients). I ended up paying a developer to update SBA for my one client who needed it..

DivaVocals:

I ended up paying a developer to update SBA for my one client who needed it..

Who does that belong to ? There seems to be enough interest that you could sell it for a reasonable sum if it's yours.

stevesh:

Who does that belong to ? There seems to be enough interest that you could sell it for a reasonable sum if it's yours.Goodness I never thought about that.. I suppose I'd have to speak with my client about that before I'd consider it.. She is aware I could (and may) use this code for other clients, and she's not communicated that she'd impose any restriction on me in that regard.. This version does not attempt to be fancy like the many other variants (no sequenced attributes or none of that other fancy stuff that's been attempted).. It is a Zen Cart 1.5 compatible version that is an update of Kuroi's last stable version of SBA (which is what my client was using happily with the Grid Attribute add-on).. It simply allows you to track stock for product variants..

DivaVocals:

Goodness I never thought about that.. I suppose I'd have to speak with my client about that before I'd consider it.. She is aware I could (and may) use this code for other clients, and she's not communicated that she'd impose any restriction on me in that regard.. This version does not attempt to be fancy like the many other variants (no sequenced attributes or none of that other fancy stuff that's been attempted).. It is a Zen Cart 1.5 compatible version that is an update of Kuroi's last stable version of SBA (which is what my client was using happily with the Grid Attribute add-on).. It simply allows you to track stock for product variants..

If your client is ok with it, I will gladly pay for this variant. PM Me...

"Why switch?" I agree is a very important question to ask yourself.

After going through a miserable upgrade (hired professionals to do it, who disappeared when I asked them to switch me back to 1.38, leaving me stuck with a poorly functioning site, that has me focusing on fixing software problems instead of focusing on my business), I will think long and hard about any future ZC upgrades. There is probably a lot to like about 1.5, however all the functionality that I've lost, and battled to regain, has prevented me from seeing anything positive about my 1.50 experience.

I am now resigned to building a brand new site, which may be 1.50, but will probably be 1.39 or a non Zen Cart platform, and starting over. So many of the broken bits that have emerged, have only been discovered weeks or months after the upgrade, so I can't even be sure if they are a result of the upgrade, or a victim of one of the "fixes" to another problem. I would strongly encourage owners of complex sites that have evolved over time (which in many cases may mean lots of useless/non-functioning code) to consider carefully the concept of an "upgrade."

When you get to the point where you require the enhancements of another software package, perhaps it is smarter to create from scratch, and take the process as an opportunity to re-think, and re-evaluate the important functions of your site. A new platform could, and probably should, allow you to do things you couldn't do before, and perhaps there is a element of the "upgrade" mindset that predisposes you to think about the way things have been done in the past. I'm not saying that you should not move forward, I'm only suggesting that you think about the different paths you might take to get to your destination.

Feel free to disagree . . . just stating my point of view!

smcelligott:

"Why switch?" I agree is a very important question to ask yourself.

After going through a miserable upgrade (hired professionals to do it, who disappeared when I asked them to switch me back to 1.38, leaving me stuck with a poorly functioning site, that has me focusing on fixing software problems instead of focusing on my business), I will think long and hard about any future ZC upgrades. There is probably a lot to like about 1.5, however all the functionality that I've lost, and battled to regain, has prevented me from seeing anything positive about my 1.50 experience.

I am now resigned to building a brand new site, which may be 1.50, but will probably be 1.39 or a non Zen Cart platform, and starting over. So many of the broken bits that have emerged, have only been discovered weeks or months after the upgrade, so I can't even be sure if they are a result of the upgrade, or a victim of one of the "fixes" to another problem. I would strongly encourage owners of complex sites that have evolved over time (which in many cases may mean lots of useless/non-functioning code) to consider carefully the concept of an "upgrade."

When you get to the point where you require the enhancements of another software package, perhaps it is smarter to create from scratch, and take the process as an opportunity to re-think, and re-evaluate the important functions of your site. A new platform could, and probably should, allow you to do things you couldn't do before, and perhaps there is a element of the "upgrade" mindset that predisposes you to think about the way things have been done in the past. I'm not saying that you should not move forward, I'm only suggesting that you think about the different paths you might take to get to your destination.

Feel free to disagree . . . just stating my point of view!
Two points:

1. No one should be wanting to stay with v1.3.8.. Two of my clients who chose not to upgrade from 1.3.8 were hacked (BOTH had their PayPal payment module "hijacked" and payments were re-routed to some Chinese PayPal account) 1.3.8 is not secure and any store still running this version is just a sitting duck waiting to be hacked..
2. A Zen Cart upgrade should be considered a RE-BUILD of the store which includes an update of the database.. This is the approach one should take when upgrading,.. and based on reading DrByte's postings on upgrading, he has said as much.. This is how I have approached all my client upgrades..