Re: X-Cart v4.5.0 released
 

I've uploaded updated UPS bugfix and the necessary instructions here -> http://forum.x-cart.com/showthread.php?p=338697

Re: X-Cart v4.5.0 released
 

Couple of things.

1. Checkout by Amazon no longer works. (omg I just fixed it as I was typing this: re-copied database files). Wow. Nevermind.

2. Evaluation notice. After testing 4.5 in a sub-directory I moved it live after updating config. I already manually deleted the home eval notice because it's annoying when trying to do page design. Anyway after going to my licenses here and updating version, I'm still getting the eval notice on admin page, and ... I KID YOU NOT this also was fixed as I typed. Of course the updating the license took care of it, just on a little time delay. I should get a lotto ticket.

3. Upgrade patch to Smarty3 absolutely doesn't work for me, no doubt because I have 3rd party mods and don't have a clue about Smarty. 4.5.0 still works with current Smarty2 though.

I'm live with 4.5. My last version 4.4.3 lost ability to process cc, so going with 4.5.0 was easy decision. Fresh install but copied database info from earlier version. Only thing that didn't copy at all is product images/thumbs/detailed images. Not an x-cart issue of course.

BIG Question: Since now all 4.5.0 stores are PCI compliant, we don't need our SSL certificates anymore, right? I mean the whole purpose of buying those certs was so our stores were kosher as we accepted customer cc info and passed onto our gateways. Now all that cc info is entered off-site at, in my case, AuthNet/Google/Amazon/PayPal. Those sites need SSL certs. Or is there another reason why I should renew my cert?

Re: X-Cart v4.5.0 released
 

Two questions.
1. We use Authorize.net SIM payment gateway which as I understand it should be PCI compliant without using x-payments. Do I understand this correctly?
2. In a prior post, it was stated that an upgrade patch was being created. Will this upgrade from 4.4.5 to 4.5x? We are using xcart pretty much off the shelf at the moment as the standard features meet our needs without a great deal of massaging. Would I be better served by doing a new install pointing to the current 4.4.5 db?

Re: X-Cart v4.5.0 released
 

WRONG. You absolutely need SSL. SSL is not to make you PCI compliant. SSL works in secure mode to encrypt information transmitted over Internet. This applies not only to financial info but personal info as well. Any site that deals with customer financial and/or personal info, any site that has login/register must have SSL installed and work in secure mode when dealing with this kind of info

Re: X-Cart v4.5.0 released
 

1. We use Authorize.net SIM payment gateway which as I understand it should be PCI compliant without using x-payments. Do I understand this correctly? YES
2. In a prior post, it was stated that an upgrade patch was being created. Will this upgrade from 4.4.5 to 4.5x? We are using xcart pretty much off the shelf at the moment as the standard features meet our needs without a great deal of massaging. Would I be better served by doing a new install pointing to the current 4.4.5 db? NO, You can't just point 4.4.5 db to 4.5.x install. DB has to be upgraded first. QT will soon release upgrade packs

Re: X-Cart v4.5.0 released
 

Authorize.net SIM is PCI compliant. It was the AIM module that wasn't, unless your site itself was compliant. But remember that customers are still looking for that lock icon during checkout, so they should be directed to https area of the cart/registration pages etc.

I went to your site and noticed that customers aren't directed to https on the cart page. Customers may still think their data isn't secure, even though it is when they are taken to AuthNet's payment page. You'll lose orders from people wanting to see a secure page when they click on their cart.

That's because customers have been trained (via industry education and browsers' detection of unsecure pages) to avoid websites that don't have the lock icon/blue-or-green url bar or whatever their browser does with secure pages.

Re: X-Cart v4.5.0 released
 

Is V4.5.0 stable now?

Re: X-Cart v4.5.0 released
 

As stable as it was before

Re: X-Cart v4.5.0 released
 

Is ok to use for a live store or am I better sticking with v4.4.5

Thanks

Re: X-Cart v4.5.0 released
 

See post #36 - QT thinks it is. I would wait though for 4.5.1 to get live with 4.5.x branch

Re: X-Cart v4.5.0 released
 

Thanks Steve will do just that :)

Re: X-Cart v4.5.0 released
 

Anyone having a problem with Google checkout?

I'm getting "Script called without authorization, or caller authorization failed.
Request URI: /payment/ps_gcheckout.php
Backtrace:
/home/kustomrides/www/www/modules/Google_Checkout/gcheckout_callback.php:70
/home/kustomrides/www/www/modules/Google_Checkout/checkout.php:556
/home/kustomrides/www/www/payment/ps_gcheckout.php:50"

Never saw that before installing 4.5.0, and my SSL is up to date and worked on 4.4.3

Re: X-Cart v4.5.0 released
 

kustom,

You need to secure the callback script with HTTP Basic Authentication.

http://help.x-cart.com/index.php?title=X-Cart:Google_Checkout
Scroll down to the section "HTTP Basic Authentication for payment/ps_gcheckout.php"

Re: X-Cart v4.5.0 released
 

To fix the google call back error place this

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
</IfModule>


in folder Payments -.htaccess file

Worked for me.

Re: X-Cart v4.5.0 released
 

Anonymous checkout bug - same as this one - http://forum.x-cart.com/showthread.php?t=56877 - post #21 for recent details

Re: X-Cart v4.5.0 released
 

While waiting for an official upgrade path I've been checking DB changes from 4.4.4 (our current version) to 4.5.0. I'd be glad to have others' eyes on these in case I've missed something important.

NB - Our DB tables all start 'xcart'. Yours may start with (for example) your directory name (for instance, 'shop')or something else you chose at installation.

-- BEGINS --

REQUIRED DATABASE CHANGES

A. Database COLLATION changed from 'latin1_swedish_ci'... to 'utf8_general_ci'


B. Changes to TABLE: 'xcart_products'

1. Four COLUMNS removed and placed instead in new TABLE: 'xcart_products_lng_en' [with index 'productid' at COLUMN 1, duplicated from 'xcart_products']

COL NAME
--- ----
3. 'product'
8. 'desc'
9. 'fulldesc'
29. 'keywords'
[reducing COLUMN count to 31]

2. Addition to 'xcart_products': new COLUMN

COL NAME
--- ----
32. 'taxcloud_tic'


C. Changes to TABLE: 'xcart_products_lng'

a. TABLE renamed to: 'xcart_products_lng_en'
b. COLUMN 'code' removed at position 1


D. New empty TABLES created, modelled on schema of 'xcart_products_lng_en'

a. 'xcart_products_lng_de'
b. 'xcart_products_lng_fr'
c. 'xcart_products_lng_sv'

E. Changes to TABLE: customers

Removal of six COLUMNS relating to retained credit card information:

COL NAME
--- ----
13. 'card_name'
14. 'card_type'
15. 'card_number'
16. 'card_expire'
17. 'card_cvv2'
18. 'card_valid_from'
19. 'card_issue_no'

-- ENDS --

Re: X-Cart v4.5.0 released
 

Re: X-Cart v4.5.0 released
 

Thank you. To be clear, we're not thinking of going into production with this until 4.5.1, following your earlier wise guidance on this topic. In the meantime, I want to be able to start customising the Ideal Comfort template on my dedicated test server, based on a clean 4.5.0 install - but I also want to populate it with a copy of our live shop data so the owner can see if it is going to fulfil her every dream ;)

I hope we might be ready to go live in a month or two - just trying to steal a march on the game. And I'm not recommending others try this either.

Did you spot any table changes I had missed? I know you've done something very like the above yourself.

Re: X-Cart v4.5.0 released
 

That's pretty much it. You can use some file-compare program like diffmerge and see all changes side by side

Re: X-Cart v4.5.0 released
 

That did the trick. Either something I did on my fresh install, or something x-cart did with 4.5.0. Thanks a lot, James!

Re: X-Cart v4.5.0 released
 

Some other changes too including:

All the tables and columns will need charset changed.

"sessionid" is renamed to "sessid" throughout database with a varchar of 32.

data_type column in xcart_import_cache has been changed.

product, descr, keywords and fulldescr removed from xcart_products, taxcloud_tic added

xcart_taxcloud_cache table added

Many language variables have been added and/or removed.

Many cc processors have been removed.

Of course the version config value is different.

Many config values removed/added/changed.

xcart_language_codes all changed to UTF-8

New taxcloud module in xcart_modules

Many xcart_payment_methods add/changed/removed.

Many xcart_shipping values added/removed/changed.

USPS values in xcart_shipping_options changed.

Re: X-Cart v4.5.0 released
 

With so many changes in DB structure is it a good idea to update from 4.x.x to 4.5.0?

Re: X-Cart v4.5.0 released
 

Re: X-Cart v4.5.0 released
 

Admin -> Settings -> General settings

Since all CC manual and onsite processing is taken out of 4.5.x section "Payment options" should not be there at all and any php code related to it should be stripped out BUT it is not

Re: X-Cart v4.5.0 released
 

Admin -> Maintenance

Section "Remove credit card information" should not be there at all and all coding related to it removed from the cart - XC does not store CC info anymore so this section is useless

Re: X-Cart v4.5.0 released
 

This bug - http://forum.x-cart.com/showpost.php?p=312994&postcount=202 - still exists on 4.5.0
#-o

Re: X-Cart v4.5.0 released
 

I don't understand why is this happening. Something reported as bug and fixed should not be again a problem in future versions. It is possible QT to have their own list of fixes, separated from Bugtracker. This is the only way I accept it seeing such situations. And it is not the only one, there are many of them.

Re: X-Cart v4.5.0 released
 

Thank you for your reports. I've forwarded them to our maintenance team.



This issue is under consideration of our maintenance engineers.

Re: X-Cart v4.5.0 released
 

I find it totally insane that a business releases a product that they assure people is totally ready for live production...

Then use this forum to feed them your free info on the bugs that it may or may not have. Yet if you ask them a simple question pertaining to this half done version they want me to pay them $99.00 .. How can you justify asking me for $99 for something that is so flawed that you have to come here to even find out what flaws you missed..


I give them credit for taking advantage of suckers like us...

Re: X-Cart v4.5.0 released
 

Whoa, no need to react that strongly. Here we have a team that releases updates for free.

There are other platforms out there that charge annually for updates, and their releases are hardly "bug-free". You show me a team that provides free lifetime upgrades, and completely bug free releases. That simply doesn't exist, with open-source or paid software. At least in my experience.

QT does an excellent job, even releasing patches and fixes for older versions of their cart. Thanks guys, keep it coming.

Re: X-Cart v4.5.0 released
 

Sorry, James, but I have to disagree with you on this point. Julia provided you with a detailed explanation, specified a possible origin of the problem, gave you a link to our online manual with a configuration guide, and as you probably mentioned this consultation was provided free of charge.

Moreover, we offered you our technical assistance with the Google Checkout configuration. Our support system is commercial-based, therefore you were offered to purchase our support services, it is fair I reckon.

Should you have any technical issue, questions or complaints please feel free to contact us via the message board.

Re: X-Cart v4.5.0 released
 

QT's response to this


This is understandable but... of course - since XC deletes card fields from customers table automatically when upgrade to 4.5.x is done why not do the same for the orders table. I am sure non of the XC admins who used to store CC info will go to maintenance and use this to clear the database of any CC info. They will just assume XC already did that. It seems logical to me the upgrade to take care of this behind the scene automatically and not to rely on the XC admin to do this manually.
Do I have a point? Isn't it this the goal of 4.5.x stripping out all the CC related info from the code so it doesn't allow storing or keeping CC info anymore?

Re: X-Cart v4.5.0 released
 

Rocky, When do you expect 4.5.1 to be released?

Re: X-Cart v4.5.0 released
 

The ETA is unknown yet. The approximate date is the first half of June.

Re: X-Cart v4.5.0 released - one page checkout
 

How is x-cart one page checkout for v.4.5.x? Good enough or I still need to get Altered one page checkout.

Re: X-Cart v4.5.0 released - one page checkout
 

There are many different opinions on this subject. I have recently launched several sites using the default OPC. With a little language modifications, and a few graphics explaining the process, it works quite well.

The only complaint I hear about X-cart's OPC, is the need to click the Apply button at the bottom of the left-hand column. Some customers might miss this, especially if they have a small screen and do not scroll down. A simple message at the top of the middle column seems to clear this up though.

Re: X-Cart v4.5.0 released
 

Gift wrapping bug (I assume it exists in all 4.4.x as well). When gift wrap option in admin is active the gift wrap message box shows even if it is not checked in admin. To fix open

/skin/common_files/modules/Gift_Registry/gift_wrapping_cart.tpl

and change this line

{if $config.General.enable_greeting_message}

to

{if $config.General.enable_greeting_message eq 'Y'}

Re: X-Cart v4.5.0 released
 

Anyone experienced this products map bug - https://bugtracker.qtmsoft.com/view.php?id=41595

Re: X-Cart v4.5.0 released
 

how come there are still bugs for v4.5?

Re: X-Cart v4.5.0 released
 

There is no bug-free software. You have to expect any new version to have them. The frustrating part is when you get same bugs as the previous version after they have been reported....