Community Forums

by **Qphoria** » Sat Jul 23, 2011 8:10 pm

OpenCart v1.4.9.6 Has been released!

Changes:

== OpenCart v1.4.9.6 ==

FIXES:
- Fixed php error for deleted products due to bad check for admin catalog controllers (long time bug) with !empty.
- Removed secret key required field in moneybookers and added the uppercase validation
- Fixed missing classification field in ups.php
- Fixed Customer filter to be case-insensitive
- Fixed continuity with HTTPS vs HTTP in the cart, module, and checkout pages
- Added callback to nochex.php and updated it for token support
- Fixed Flat and Free modules overriding the main status
- Fixed orphaned Germany zone to geozone (for new installs)

ADDED:
- Added Patched CURL-Based payment extensions with better curl error handling.
- Changed Worldpay to use quicker form url
- Updated royal mail rates
- changed header.tpl to use variable for theme name
- Updated common_form.tpl
- Default dimensions for UPS if left empty

DELETED:
- Empty placeholder files

Delta:

Files Changed Since 1.4.9.5
==========================
upload/admin/controller/catalog/category.php
upload/admin/controller/catalog/information.php
upload/admin/controller/catalog/manufacturer.php
upload/admin/controller/catalog/product.php
upload/admin/controller/catalog/review.php
upload/admin/controller/payment/moneybookers.php
upload/admin/controller/shipping/ups.php
upload/admin/language/english/payment/alertpay.php
upload/admin/language/english/payment/moneybookers.php
upload/admin/language/english/shipping/ups.php
upload/admin/model/sale/customer.php
upload/admin/view/javascript/ckeditor/config.js
upload/admin/view/template/payment/moneybookers.tpl
upload/admin/view/template/shipping/ups.tpl
upload/admin/index.php
upload/catalog/controller/checkout/cart.php
upload/catalog/controller/checkout/guest_step_2.php
upload/catalog/controller/checkout/shipping.php
upload/catalog/controller/module/bestseller.php
upload/catalog/controller/module/featured.php
upload/catalog/controller/module/latest.php
upload/catalog/controller/module/special.php
upload/catalog/controller/payment/authorizenet_aim.php
upload/catalog/controller/payment/moneybookers.php
upload/catalog/controller/payment/nochex.php
upload/catalog/controller/payment/perpetual_payments.php
upload/catalog/controller/payment/pp_pro.php
upload/catalog/controller/payment/pp_pro_uk.php
upload/catalog/controller/payment/pp_standard.php
upload/catalog/controller/payment/sagepay.php
upload/catalog/controller/payment/sagepay_direct.php
upload/catalog/controller/payment/sagepay_us.php
upload/catalog/controller/payment/worldpay.php
upload/catalog/controller/product/category.php
upload/catalog/language/english/payment/nochex.php
upload/catalog/language/english/shipping/royal_mail.php
upload/catalog/model/shipping/flat.php
upload/catalog/model/shipping/free.php
upload/catalog/model/shipping/royal_mail.php
upload/catalog/model/shipping/ups.php
upload/catalog/model/shipping/usps.php
upload/catalog/model/shipping/weight.php
upload/catalog/view/theme/default/template/common/header.tpl
upload/catalog/view/theme/default/template/payment/nochex.tpl
upload/index.php

DOWNLOADS:
If you are upgrading, be sure to read the "upgrade.txt" file that comes with either download

Do NOT post bugs in this thread. Use the official Bug thread here:
OFFICIAL BUG THREAD:
viewtopic.php?f=161&t=36789

EXTENSION & THEME NOTES:
Most 1.4.9.x themes should work fine. There were only tiny changes to the tpl files and only the header.tpl is likely to be something you'd have different in a custom theme. Be sure your custom themes never have their own "payment" folder as that folder should always be left out so that the default is used so that any updates to payment modules are applied to your store

OTHER NOTES:

If you are using vQmod, you will need to rerun the vQmod installer after upgrade.
If you still see 1.4.9.5 in the footer, then you didn't upload all the files, namely the index.php files
Be sure to read the doc files:
-- install.txt for new installs
-- upgrade.txt for upgrades

by **rph** » Sat Jul 23, 2011 10:39 pm

Awesome work Q!

by **amdev** » Sun Jul 24, 2011 2:30 am

Thanks Q, i'm trying to upgrade.

by **i2Paq** » Sun Jul 24, 2011 9:41 am

Nice work Q, thanks!

Edit: Dutch Translation released in the Extensions.

by **mikej** » Mon Jul 25, 2011 6:22 am

Hello,

I am confused. Is this the new release or is 1.5.1.1 the new release? Or is this the new release for people who don't want to upgrade to Version 1.5.X.X and stick with 1.4.X.X?

by **Johnathan** » Mon Jul 25, 2011 6:51 am

mikej wrote:Or is this the new release for people who don't want to upgrade to Version 1.5.X.X and stick with 1.4.X.X?

Yes.

by **mikej** » Mon Jul 25, 2011 7:22 am

Thanks for the fast reply. Can you tell me what the pro's and cons are to which version? I am going to be doing a new install, and if I should stick with 1.4.XX I will. Does one have more themes/modules etc than another? Thanks for the help.

by **Xsecrets** » Mon Jul 25, 2011 8:27 am

mikej wrote:Thanks for the fast reply. Can you tell me what the pro's and cons are to which version? I am going to be doing a new install, and if I should stick with 1.4.XX I will. Does one have more themes/modules etc than another? Thanks for the help.

1.4.x has many more themes and modules at this point, but 1.5.x has more built in features. It depends on if you need those features or not. RMA, option types, reward points to name a few of the big new features in 1.5.x

by **TheSponge** » Mon Jul 25, 2011 11:24 am

Im also a little confused, Im using 1.5.1 as I prefer the layout, features etc,
why are the 2 versions being developed side by side? is it not better to have 1 version? Im not complaining Im genuinely curious. I use 1.5.1 on a live site (I KNOW I SHOULDNT BE) its a small demo site with not many products so Im not worried about making constant changes, can I assume, 1.4.9.6 is a stable version, and 1.5.1 is still a work in progress?

Thanks

by **Qphoria** » Mon Jul 25, 2011 11:30 am

Assuming little to no bugs in 1.4.9.6, it will be the last version of 1.4.x
It is simply meant to round out the previous version for those who
A) Have no reason to upgrade to 1.5.x as that is a major change and themes are completely different
B) Have product options and no way to upgrade to 1.5.x yet
C) Prefer 1.4.x as they are running a live store and 1.4.x has 99.9% stability after being tested and developed for the past year and some change.

Upgrading your existing 1.4.x store to 1.4.9.6 is a lot easier than going to 1.5.x and if you've kept up with the smaller "Patch only" releases, then it is an extremely minor update process for you, fixing only existing bugs.

by **clark5188** » Tue Jul 26, 2011 11:30 am

Thanks to the OC. TEAM. :joker:

You guys did great jobs.
I am expecting for more new functions. :drunk:

I prefer V1.49 series rather than V1.5.

by **tirakarn** » Tue Jul 26, 2011 8:19 pm

Thank you,
Still using 1.4.x

by **Qphoria** » Wed Jul 27, 2011 1:15 am

clark5188 wrote:Thanks to the OC. TEAM.
You guys did great jobs.
I am expecting for more new functions.

I won't likely be adding any new functions. I am just making it stable for those running live stores. But the features of the 1.4.x version have come to an end and 1.5.x is the future, for better or for worse.

by **Purebeads** » Sat Jul 30, 2011 9:45 am

I expect to upgrade to 1.4.9.6 from 1.4.8b. What is the best way to do this?

I have made lots and lots of changes to the code in 1.4.8b. Should I install 1.4.9.6 in a new directory and add all of my customizations -- and then, when it is looking and working the way I want, copy it over my 1.4.8b installation? (or perhaps just switch directory names?)

by **Qphoria** » Fri Aug 05, 2011 3:08 pm

hard to say.. if you have a lot of customizations.. you will need to make them to any of the new files that have been updated. I'd recommend making custom changes with vQmod so that you don't have to worry about them

by **Purebeads** » Fri Aug 05, 2011 3:56 pm

I don't have a clue what vQmod is, even after reading the thread about it. I had better stick with what I know, which is modifying files directly.

So my question remains: Can I install 1.4.9.6 in a new directory, work on it until it is behaving the way I want it to, and then "install" it by renaming directories. E.g., my current installation is in "catalogue", so I would rename that to "catalogue-old", and then rename the new installation to "catalogue". I understand, of course, that there is a configuration file in there that I have to modify so that the program knows which directory it is in.

I assume that 1.4.9.6 will work with the database in the same way that 1.4.8b does, so I don't have to worry about copying the database too.

by **Qphoria** » Sun Aug 07, 2011 7:51 pm

Purebeads wrote:I don't have a clue what vQmod is, even after reading the thread about it. I had better stick with what I know, which is modifying files directly.

I'd recommend learning it. It is actually a pretty simple concept and the benefits are great.

it couldn't get simpler and to not have to worry about losing the modification during upgrades seems more than enough reason to give it another shot.

How do you modify files?
1. You find the file you want to change
2. You find the line you want to change
3. You change it

Exactly what vQmod does. But instead of manual changes, it uses a script file to simulate those changes. And instead of changing the actual file, it makes a clone with the changes in it and loads that in the background. You only need to do what you normally do but in a separate xml file.

Installation of vQmod is supereasy as well:
1. You upload a single folder called vqmod to your opencart store root
2. You goto a url and type http://mysite.com/vqmod/install
3. You upload xml files to the vqmod/xml folder

Let me know if you need some assistance, I'd be happy to help!

by **Qphoria** » Mon Aug 08, 2011 1:13 pm

FYI there is a hotfix for paypoint in all versions here:
viewforum.php?f=133

by **Purebeads** » Mon Aug 08, 2011 1:37 pm

If vQmod replaces lines of code on the fly when OpenCart is loading, I can see it working as long as the same version of the program is used. But it's hard for me to imagine that it could take modifications from one version of the program and apply it to another version. I took a programming course once, and I've done plenty of macro programming, and I know that a program can crash if just one line of code is off. Also, if I never upgrade beyond 1.4.9.6, I'm not sure I'll need vQmod. Nonetheless, I'll consider it. In the mean time, I still want to know if the strategy I outlined in my previous post is the way to upgrade without vQmod.

Thank you, Daniel.

by **Qphoria** » Mon Aug 08, 2011 1:58 pm

"Crash" is a scarier word than it needs to be in the web world
First off, vQmod searches for a line first
if it finds it... it does the next step
if it doesn't find it... it reverts to the original file gracefully and logs the reason. The worst scenario would simply be that it doesn't load your change and it just loads the normal page until you fix it.

There is no threat. If a file doesn't work, you simply remove it from the xml folder and your store is back to normal.
You can add 20 xml files that make 50 changes and immediately remove 20 files and it will be like those changes were never there.

You are right that an upgrade could potentially cause the core line that worked in 1.4.9.3 to change in 1.4.9.6 which would then not match. But aside from being unlikely, it is a graceful fallback and simple error log to see the issue and fix the issue with a small line change.

But since 1.4.9.x has been small bug fixes. It is unlikely anything has changed. I think in all 50+ vQmod scripts I've made since 1.4.8.. none of them have needed to be updated for 1.4.9.x. I did have to update them for 1.5.x, but that would be the case for manual mods anyway. Still updating the xml file for 1.5.x support was a lot easier and less work going forward.