Requests for R4 or R5
Posted: Tue Dec 11, 2012 3:44 pm
I know that R3 was released on November 30. After working with AC Gold for a couple of months we have some request for R4 or R5 that would make our lives a little easier.
Our storefront is deployed on a load-balanced, two-server environment. Some hurdles we encountered with AbleCommerce Gold were related to hard coded directories. For those unfamiliar with this, specifically I'm referring to:
* App_Data\Indexes
* Assets\DigitalGoods
* Assets\ProductImages
We use a load-balanced, 2-server environment to host our sites. The problem we encountered with uploading files (digital goods and product images) was that the uploaded files would be saved on one server, but not on the other server. We had a similar problem with the indexes. If we logged into the administration panel and re-indexed the site, the re-indexing would only occur on the server that our browser was pointed to.
So for instance, lets say I logged into the admin panel and was directed to the site on Server #1. Then I added a digital good, uploaded a related product image, and then re-indexed the site. All of that would show up correctly for customers whose browsers were directed to that same instance of the site on Server #1. But visitors who were directed to Server #2 by the load balancing process would see a broken image for the product, and would not be able to download the digital file. And if the site required re-indexing, then features that fail when the index is bad would fail for that visitor on Server #2. Visitors directed to Server #1 would have a trouble-free experience, while visitors on Server #2 would report problems.
There are several ways to handle this, and our ultimate solution was to create Symbolic Links for the above directories. The symbolic links pointed to common directories on a file-sharing server. Now when we deploy the site, we will write a script to recreate the symbolic links, and also set the correct directory permissions. All of this could be made easier if...
Request #1: Please make the targeted directories configurable. Instead of embedding them into the code in a hard-coded manner, make them config entries. Or make them virtual directories where the code performs a map path to virtual directories.
Our second request relates to the payment providers. In our case, we used the Skipjack payment provider, which we also found had hard coded properties rather than utilizing configurable settings. And the AbleCommerce interface presented a limited subset of capabilities from the Skipjack API. In our case, we needed the advanced payment processor, and the Comment Line. And we needed to target an alternate Skipjack URL for that payment provider. One of our experts had to jump through hoops to get that working, and mentioned that it would have been very helpful if more of that would have been configurable.
Request #2: Please enhance the Skipjack payment provider to be more configurable. Present the Skipjack URL and the Comment Line on the administration screen. If the URL needs to have a default value, put it there, but at least provide the capability of configuring that easily from the administrative tool.
That being said, we do like this product. Customer support has been very good, both on this forum and via cases I have submitted. Given the extensive feature-set present in AbleCommerce Gold, it's remarkable to see how well this product works. In a single-server environment with a basic payment provider, AbleCommerce Gold would likely work seamlessly for most businesses. Additionally, when I've needed to make code changes, the code has been easy to follow. Thanks.
Our storefront is deployed on a load-balanced, two-server environment. Some hurdles we encountered with AbleCommerce Gold were related to hard coded directories. For those unfamiliar with this, specifically I'm referring to:
* App_Data\Indexes
* Assets\DigitalGoods
* Assets\ProductImages
We use a load-balanced, 2-server environment to host our sites. The problem we encountered with uploading files (digital goods and product images) was that the uploaded files would be saved on one server, but not on the other server. We had a similar problem with the indexes. If we logged into the administration panel and re-indexed the site, the re-indexing would only occur on the server that our browser was pointed to.
So for instance, lets say I logged into the admin panel and was directed to the site on Server #1. Then I added a digital good, uploaded a related product image, and then re-indexed the site. All of that would show up correctly for customers whose browsers were directed to that same instance of the site on Server #1. But visitors who were directed to Server #2 by the load balancing process would see a broken image for the product, and would not be able to download the digital file. And if the site required re-indexing, then features that fail when the index is bad would fail for that visitor on Server #2. Visitors directed to Server #1 would have a trouble-free experience, while visitors on Server #2 would report problems.
There are several ways to handle this, and our ultimate solution was to create Symbolic Links for the above directories. The symbolic links pointed to common directories on a file-sharing server. Now when we deploy the site, we will write a script to recreate the symbolic links, and also set the correct directory permissions. All of this could be made easier if...
Request #1: Please make the targeted directories configurable. Instead of embedding them into the code in a hard-coded manner, make them config entries. Or make them virtual directories where the code performs a map path to virtual directories.
Our second request relates to the payment providers. In our case, we used the Skipjack payment provider, which we also found had hard coded properties rather than utilizing configurable settings. And the AbleCommerce interface presented a limited subset of capabilities from the Skipjack API. In our case, we needed the advanced payment processor, and the Comment Line. And we needed to target an alternate Skipjack URL for that payment provider. One of our experts had to jump through hoops to get that working, and mentioned that it would have been very helpful if more of that would have been configurable.
Request #2: Please enhance the Skipjack payment provider to be more configurable. Present the Skipjack URL and the Comment Line on the administration screen. If the URL needs to have a default value, put it there, but at least provide the capability of configuring that easily from the administrative tool.
That being said, we do like this product. Customer support has been very good, both on this forum and via cases I have submitted. Given the extensive feature-set present in AbleCommerce Gold, it's remarkable to see how well this product works. In a single-server environment with a basic payment provider, AbleCommerce Gold would likely work seamlessly for most businesses. Additionally, when I've needed to make code changes, the code has been easy to follow. Thanks.