Well-Known Member
Jan 31, 2002
We want to create a slightly customized version of interchange and then install it manually into accounts that request a shopping cart (different graphics and addition of payment gateways).

1. Can I intall interchange into a test account thru cpanel, then disable it from WebHostManager (so other users can NOT install it), then edit this one store thru admin and/or custom coding, then copy the revised “catalog” folder and revised “cgi files” into each additional account manually?

2. Are there any other local files that are part of the functioning of the store (other than catalog folder and cgi-bin files?

3. Once interchange files are installed in a local account, are there any global files that are necessary for functioning of the cart?

4. Do both versions 4.8 and 4.9 reside on the server, and it’s just a matter of which one is enabled thru WebHostManager that determines which version installs into my test domain.

5. Interchange’s resource site adamently says that they will not support installations done thru cpanel, as they have unique problems. What are the known issues related to cpanel?

6. Are there any support documents for interchange used with cpanel?

7. None of the graphics/images show up in the store that I installed thru cpanel. I see the path for existing images is supposed to be “mydomain.com/~username/cart/images/anothersubdirectory/image.gif” – with multiple folders under “images” depending on what type of image it is. Why are the images missing, and where in my local account is this /cart/images folder?

8. How can I delete the interchange shopcart on my local account if I make a mistake and want to start over?

9. How would any upgrades be added into existing interchange stores, or will a store have to be rebuilt from scratch?


Well-Known Member
Jul 4, 2002
Atlanta, GA
You're barking up the wrong tree trying to accomplish this task with Interchange (IC). It is not a standard script-driven shopping cart solution like Agora or osCommerce. It actually runs as it's own process (much like Apache, MySQL, etc.) and is really more of an e-commerce framework than a catalog/shopping cart.

IC was not designed to be 'virtualized' . It was intended to be a stand-alone server servicing multiple catalogs for a single user, not individual catalogs for multiple users. It's implementation within CPanel is buggy at best and will only cause you headaches in the long run. It has proven to be quite unstable (both 4.8 and 4.9) under Cpanel when you start adding more than a dozen or so catalogs.

I'd recommend switching to Agora or osCommerce to accomplish what you need.