Technical Help - Coexistance of CMS-Builder with X-Cart Shopping Cart software

4 posts by 2 authors in: Forums > CMS Builder
Last Post: December 3, 2009   (RSS)

By garyhoffmann - December 3, 2009

This is a bit of technical issue - hopefully someone can help.

Here it goes...

I have a site that needs to have both CMS Builder and X-Cart software on the same site and same pages.

I'm using CMS Builder to deal with navigation of the non-cart pages, all of the content of the non-cart pages, etc., but want to place portions of the e-commerce system on these pages (featured items for example).

I know that CMS Builder does a very nice job of containing it's functions pretty much into the header of the code when we go to get data.

Here's the tricky part - I need to save off the current connection information (connection to database server, "current" database, etc.) before the viewer functions are called and then restore this information upon coming back from the viewer functions.

I think that's all there would be to it, but don't know what I should all do here.

For example, is there a way to get the "current" database?

Can we have a connection to more than one db account within the same script, etc?

Guidance on this would be extremely helpful. While I'm very comfortable doing the programming, I have never had to deal with this type of issue before.

Thanks in advance.
Gary.

Re: [garyhoffmann] Technical Help - Coexistance of CMS-Builder with X-Cart Shopping Cart software

By Dave - December 3, 2009

Hi Gary,

Is there a specific order that X-Cart and CMSB need to be called in? If it's possible to just load the viewer_functions first and load all the records you need for CMSB, then load xcart and call it's function below that, then that would probably be the simplest.

Let me know if that would work for you.
Dave Edis - Senior Developer
interactivetools.com

Re: [Dave] Technical Help - Coexistance of CMS-Builder with X-Cart Shopping Cart software

By garyhoffmann - December 3, 2009

Thank you for the reply, but that would only work for a single page - as soon as the page changes, the database connections get mixed up.

As I'm using CMSB for nav, etc., that has to be available on all pages.

Gary.