X-Cart forums

[ambal]

Hi Everyone,

Recently we released X-Cart 4.6.4 - see http://blog.x-cart.com/x-cart-464-released.html

I want to comment on this improvement a bit

Quote:
X-Payments connector has got lots of improvements for better usability.

This update addresses many X-Payments known issues and troubles with X-Cart 4.x like too many technical DB entries about started orders at X-Cart side, saving customer notes, cc_xpc_iframe.php called twice to display CC form, Product inventory levels are not getting decreased when a Pre-Authorized order is paid via X-Payments (lite interface) and others. I would say this is quite serious update of X-Cart 4 connector. Besides it comes with much improved and easier X-Payments connection procedure.

IMPORTANT NOTE: in order to enable all the usability improvements you need to
1) upgrade your X-Payments to 2.1.1 (users of X-Payments Hosted accounts just need to post us a request to make such upgrade for them for free)
2) re-deploy X-Payments configuration bundle (re-import of X-Payments payment methods will happen automatically) in X-Cart after upgrading X-Cart to 4.6.4 or installing new X-Payments connector module (see below about that).

Next step is to release adapted versions of 4.6.4 connector for old X-Cart 4.x versions and to implement iFrame and PCI compliant credit card saving support for all of them. ETA for this step is August-September, but first updates should come this week. I'll keep you posted.


UPDATE:

New connector modules for various X-Cart 4.x versions can be downloaded at
https://drive.google.com/a/x-cart.com/folderview?id=0B6p7sehSZL8_akhxR0VwQ0dta2M&usp=dri ve_web

[Online Michael]

We had our store upgraded from 4.6.3 to 4.6.4 and I have to say the new "improvements" are causing us major headaches. This is what we discovered this morning:

A customer wanted to buy two products. One of the products they had in their cart was the last one we had in stock so while they were at the checkout, X-Payments created a "Not Finished" order. Then it created another order and all of the sudden there were two. However, after a short while the second "Not Finished" order had its status changed to "Processed/Paid".

At this point we had a "Not Finished" order and a "Processed" order for the same customer and for exactly the same amount. Nothing strange so far, right? What happened next was very concerning.

The customer emailed us because they were confused as to how she ended up with just one product in her order but ended up paying for two? As it turns out, due to the stock adjustments being done in the background, the allocation of stock with the first "Not Finished" order meant there was no stock left for the second order, which explains why only one product appeared on the processed order!

Not only was the product missing from the processed/paid order, the amount charged was never adjusted to reflect the change. In other words, the customer ended up paying for the missing product as well. And if it wasn't for her email, our staff would have packed and despatched her order with just the one single product.

Later, several more "Not Finished" orders appeared and after checking actual stock levels in our store, we quickly discovered that they were all holding stock as well! Changing the status to"Failed" fixed the problem and stock was released back.

In my opinion, this should never be allowed to happen. Why? Because we just lost a $180 order directly as a result of the way the connector/x-payments process orders/payments. We believe that the customer had more than likely abandoned the cart because one of the items they were purchasing was no longer in their cart.

I'll take everything I said back if I am doing something wrong, but I don't believe I am. Personally, I think Qualiteam may have solved one problem, to only created another... And we're losing sales because of it. Not happy.

[ambal]

Hi Michael,

Let us follow up with you regarding this via your HelpDesk account. Some investigation is needed as new connector relies on using latest X-Payments v2.1.1

[cflsystems]

Hi Alex

Since I was the one to upgrade the cart and worked with Michael through this at night I guess I should say something. I don't think I saw anywhere what you have just mentioned (did I miss it?) - "new connector relies on using latest X-Payments v2.1.1". So their X-Payments installation is not yet upgraded (it will be though) but to release changes to the Connector like this that depend on another piece of software and not mention this anywhere is not good practice. What about all the carts now that may have already upgraded to 4.6.4 and using X-Payments 1.0? They are screwed big time right.

If this was known up front their X-Payments would have been the first to upgrade. This is critical to active shops. I am not happy about this, you can imagine how Michael feels....

This is all that shows on the upgrade screen in admin before launch, not a word about the X-Payments Connector

11. After the upgrade is completed, check the following features (Enable and configure the ones you will use and disable the ones you won't):
-Pay with Amazon/Checkout by Amazon modules settings
-XPayments_Connector module settings
-iDEAL - Rabobank Professional payment settings
-ePDQ - Essential payment settings
-CyberSource - Secure Acceptance Web/Mobile payment settings
12. After the upgrade your store will be able to generate anonymous profiles from orders placed by anonymous users. Since after the upgrade your store's database may already contain previously created anonymous orders, you should use a special utility to generate anonymous profiles from them. <br />To launch the utility, open the link
http://YOUR_XCART_STORE/admin/tools.php?start_generate_anonymous=Y in your web browser, or go to the Tools > Maintenance section of your store's Admin area (http://YOUR_XCART_STORE/admin/tools.php) and click the button "Generate anonymous customers from orders" (The button is not displayed if there are no anonymous orders that have not been converted to anonymous profiles.). This will start the generation of anonymous profiles. Please note that this operation may be time consuming.
https://blog.x-cart.com/sites/default/files/blog/anonymous%205.png
13. This upgrade pack does not include changes for vivid*/fashion* skins. If your store uses any of these skins, you will need to upgrade the skin separately using a helpfull patch upgrade/4.6.x-4.6.4/patch_to_check_fashion_mosaic_vivid_dreams_changes .4.6.3-4.6.4.diff and the diff files from the upgrade/4.6.x-4.6.4/skin/common_files directory.

(If all this is due to the XC/XP and not some 3rd party software).

[cflsystems]

After upgrading X-Payments to latest it seems to have resolved the multiple orders and the stock issues.
I had to also delete X-Payments payment methods in XC and re-deploy them in order to make this work.
It does seem though the configuration "key" for deploy hold http instead of https for X-Payments url which results in the automatic deployment to fail - had to do it manually, that's where I saw the url being http://

So for everyone upgrading to 4.6.4 and using X-Payments - you are forced to upgrade X-Payments to its latest version 2.1.1 otherwise the new Connector will just not work properly.

[ambal]

Hi Steve and Michael,

Indeed you need to upgrade to X-Payments 2.1.1 and re-deploy X-Payments configuration bundle (re-import of payment methods will happen automatically) when you upgrade an existing X-Cart installation connected to X-Payments to 4.6.4.

We will correct our posts to reflect that.

Also, the new connector works with older X-Payments versions, too, but many of the usability improvements will take place with X-Payments 2.1.1 because changes have been made on two sides - in X-Cart and in X-Payments. Since changes in X-Payments assume releasing new versions we released 2.1.1, but unlike for X-Cart we can't release "adapted" versions of changes for older X-Payments

For older X-Cart versions we are preparing updated X-Payments connector modules that supports everything we've implemented in 4.6.4 and they will support 2.1.1 fully, of course.

[cflsystems]

Alex also check on this

It does seem though the configuration "key" for automatic deployment holds http instead of https for X-Payments url which results in the automatic deployment to fail

[ambal]

> It does seem though the configuration "key" for automatic deployment holds http
> instead of https for X-Payments url which results in the automatic deployment to
> fail

This depends on what you have on X-Payments config file. If you put X-Payments URL there as http:// you may face to this trouble. Just correct URL in X-Payments config file to https://

[cflsystems]

Yes it was http:// in the config file.
Funny thing is this X-Payments was installed and connected to the XC store by QT

[timbrrr]

Originally Posted by cflsystems

Hi Alex

........... What about all the carts now that may have already upgraded to 4.6.4 and using X-Payments 1.0? They are screwed big time right.

If this was known up front their X-Payments would have been the first to upgrade. This is critical to active shops. I am not happy about this, you can imagine how Michael feels....

This is all that shows on the upgrade screen in admin before launch, not a word about the X-Payments Connector...............

.

Nice to find this AFTER upgrading to 4.6.4 and searching in the forum for an answer to why my shop is totally hosed right now. I can't even roll back, because the database backup is not restoring all the tables correctly.

The word LIVID doesn't even touch the surface of what I am feeling right now.
I hope this wasn't an attempt to sell more copies of Xpayments 2.xx

From what I'm reading of CFL's post, I'm totally dead in the water until an updated version of 1.x is released, or I shell out the cost of upgrading to XP 2.x ?? I see the last post was five days ago, and still no updates.