Hi all,
I recently made some changes to the styles of the shopping cart and added some menus to the top. However instead of applying those changes directly to the server or overwriting the files directly, I created an alternate directory in the same webserver and put the whole contents of the previous installation there. I just replaced there the files I modified. Whenever I switch the IIS to point to this new folder, I'm requested to add the license key again as a new installation. I add it and then almost everything is working fine. I'm able to see the shopping cart products, add those the basket and go to the checkout page.
Here comes the problem. I put the credit card information and hit "pay with card" and the "Processing" image shows for ever and I'm not able to complete the transaction. In the backend, I switched to Test Mode and it is still doing the same thing. So I decided to switch it back to the old installation and works fine.
Is there something that I may be missing in the new installation? I have the same config files in place (database, encryption and ablecommerce), but my guess is that, whenever I apply the new license it checks the new path installation and creates some conflict with the old path or something like that. I did not started a new database installation, since I'm using the same database. Also, I didn't deployed a new installation of AbleCommerce, I just copied the files and modified them.
Thank you in advance for you help!
Sergio A.
Payment not working after move of website
Re: Payment not working after move of website
Try to export the encryption keys
- Login to AbleCommerce admin control panel
- From the top menu go to: Configure -> Security -> Encryption Key
- Under Back-up Encryption Key section click on Get Backups
and then import the keys under the new virtual folder.
We use both SVN and Mercurial version control for development and each AbleCommerce project is always deployed on the server from version control branch. In this case
when we have to make new site changes we can always export previous version of the site from a version control branch to the same site root folder on the sever (no need to change
virtual folders in IIS). If you are the only one working on the site you can install SVN/Mercurial both server and client on the same development machine (no need to configure separate server).
- Login to AbleCommerce admin control panel
- From the top menu go to: Configure -> Security -> Encryption Key
- Under Back-up Encryption Key section click on Get Backups
and then import the keys under the new virtual folder.
We use both SVN and Mercurial version control for development and each AbleCommerce project is always deployed on the server from version control branch. In this case
when we have to make new site changes we can always export previous version of the site from a version control branch to the same site root folder on the sever (no need to change
virtual folders in IIS). If you are the only one working on the site you can install SVN/Mercurial both server and client on the same development machine (no need to configure separate server).
Mike Kolev
Re: Payment not working after move of website
Hi Mike, thanks for your comment.
Actually we are using Mercurial too, and we were trying to implement and strategy of deploying the changes to production through it. Your comment is very valuable to me because you have it working right now. I'm going to try to follow your steps mentioned here. By the way, we had to do a clean installation or the store and then move the configuration files. Before that I had saved the encryption keys, but never thought about those being the problem when moving the site. At least we have an alternate site working now, but for future improvements we'll be implementing something like that.
Sergio A.
Actually we are using Mercurial too, and we were trying to implement and strategy of deploying the changes to production through it. Your comment is very valuable to me because you have it working right now. I'm going to try to follow your steps mentioned here. By the way, we had to do a clean installation or the store and then move the configuration files. Before that I had saved the encryption keys, but never thought about those being the problem when moving the site. At least we have an alternate site working now, but for future improvements we'll be implementing something like that.
Sergio A.