Comments on: Should I use the new v3 osCommerce? http://www.clubosc.com/should-i-use-the-new-v3-oscommerce.html Showcasing osCommerce...the good, the bad and the ugly! Fri, 30 Jul 2010 13:32:48 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: enigma1 http://www.clubosc.com/should-i-use-the-new-v3-oscommerce.html/comment-page-1#comment-2965 enigma1 Sat, 11 Apr 2009 11:32:02 +0000 http://www.clubosc.com/?p=339#comment-2965 I wanted to point out, the few contributions that were available for the MS3 A4 release, were deleted from the osC forum. That does not encourage community members to create new ones or port existing ones to the MS3 A5. I wanted to point out, the few contributions that were available for the MS3 A4 release, were deleted from the osC forum. That does not encourage community members to create new ones or port existing ones to the MS3 A5.

]]> By: Juan http://www.clubosc.com/should-i-use-the-new-v3-oscommerce.html/comment-page-1#comment-2895 Juan Mon, 16 Mar 2009 15:07:33 +0000 http://www.clubosc.com/?p=339#comment-2895 Yes. Magento is unusable, but has great features, I'm developing some of them in my site. i.e. Category Design: Theme, Descriptions & Images Yes. Magento is unusable, but has great features, I'm developing some of them in my site.

i.e. Category Design: Theme, Descriptions & Images

]]> By: Gary http://www.clubosc.com/should-i-use-the-new-v3-oscommerce.html/comment-page-1#comment-2894 Gary Mon, 16 Mar 2009 15:00:28 +0000 http://www.clubosc.com/?p=339#comment-2894 Jared - agreed. It's a little different for me as I charge for my "bigger" modifications, so it makes it a little easier to support my stuff personally. However, I won't be doing anything to all my contributions available for free as there's no way I want to spend my time on too much stuff. Juan - Magento is unusable in a production environment. I have no experience with Prestashop so cannot say if osc3 is better or worse. I've spent this morning playing with the new codebase - it's a lot more complicated to do simple things (eg add in a language "define")...but all in all, v3 is a HUGE step forward compared to 2.2. Still say "do not use in a real shop" though! Jared – agreed. It's a little different for me as I charge for my "bigger" modifications, so it makes it a little easier to support my stuff personally. However, I won't be doing anything to all my contributions available for free as there's no way I want to spend my time on too much stuff.

Juan – Magento is unusable in a production environment. I have no experience with Prestashop so cannot say if osc3 is better or worse.

I've spent this morning playing with the new codebase – it's a lot more complicated to do simple things (eg add in a language "define")…but all in all, v3 is a HUGE step forward compared to 2.2. Still say "do not use in a real shop" though!

]]> By: Juan http://www.clubosc.com/should-i-use-the-new-v3-oscommerce.html/comment-page-1#comment-2893 Juan Mon, 16 Mar 2009 13:03:19 +0000 http://www.clubosc.com/?p=339#comment-2893 A lot of new features and changes, but below Magento/Prestashop/Etc.... :( A lot of new features and changes, but below Magento/Prestashop/Etc…. :(

]]> By: jared http://www.clubosc.com/should-i-use-the-new-v3-oscommerce.html/comment-page-1#comment-2892 jared Mon, 16 Mar 2009 07:41:15 +0000 http://www.clubosc.com/?p=339#comment-2892 I agree. The release notes say that the internal structure is still undergoing changes, so anyone who implements a shop now will either have to go through the hassle to upgrade to the "full release" version at some point, or spend the time and money to do one-off installs of every add-on or contribution they want. I just can't see contribution developers spending much more effort on this release of v3 than they have on previous releases of v3. There are a lot of developers now to barely have enough time to keep up with support on their contribs that are released for v2.2. Why would these folks intentionally create a new version that they know will either get soon(ish) confused by another osC release with structural changes they'll have to account for? I agree. The release notes say that the internal structure is still undergoing changes, so anyone who implements a shop now will either have to go through the hassle to upgrade to the "full release" version at some point, or spend the time and money to do one-off installs of every add-on or contribution they want.

I just can't see contribution developers spending much more effort on this release of v3 than they have on previous releases of v3. There are a lot of developers now to barely have enough time to keep up with support on their contribs that are released for v2.2. Why would these folks intentionally create a new version that they know will either get soon(ish) confused by another osC release with structural changes they'll have to account for?

]]>