[ic] Problem with option and migration from old catalog (4.6.x) to 5.6.0
ic at 3edge.com
ic at 3edge.com
Wed Aug 6 09:02:17 UTC 2008
> -----Original Message-----
> From: interchange-users-bounces at icdevgroup.org [mailto:interchange-
> users-bounces at icdevgroup.org] On Behalf Of Alessandro Poletto
> Sent: woensdag 6 augustus 2008 11:49
> To: interchange-users at icdevgroup.org
> Subject: Re: [ic] Problem with option and migration from old catalog
> (4.6.x) to 5.6.0
> Many many many thanks for your help...
> but the problem persist...
> the problem is strange and no logging is made so, for me, is really
> difficult to understand what happen!
> Is really important that I found a solution!
If you have access to the Interchange Core code, add additional logDebug
lines (or removed the # from already existing logDebug lines) to the various
modules to create your own logging and see where things are going wrong.
Also make sure you have Debug switched on and are sure that you are writing
to the correct Debug log ... For example, set in your interchange.cfg:
- Variable DEBUG 1
- DebugFile /tmp/debug.log
In a default interchange.cfg you probably should be able to find these lines
to be existing. Restart interchange and see if anything gets written in your
As you are working with an existing heavily customized site, it is near to
impossible for anyone to come up with a working solution, unless they dive
into your system/code to find out what is going on....
> On Sun, Aug 3, 2008 at 6:21 AM, Peter <peter at pajamian.dhs.org> wrote:
> > On 07/31/2008 12:48 AM, Alessandro Poletto wrote:
> >> I've taken an old catalog developed on interchange 4.6.x (I am not
> >> sure because I've only a backup of datas).
> >> After some simple adjustment all works perfectly but a problem
> >> when in the administration I go to modify an option, the interface
> >> propose me to change the type of the option as "matrix option
> >> widgets" (that is correct), when I confirm it rollback to the same
> >> page.
> >> I've thinked that in 4.6 the product/option structure was based on
> two tables:
> >> products and options
> >> In the earlier release the structure of database is changed with
> three tables:
> >> products variant option
> >> obviously the structure of the backup have only two tables...
> >> what the best way to return to use the options?
> >> I have to insert the vaiant table and make a script to convert
> >> In this case I've to rewrite a lot of software because the previous
> >> developer have wrote a lot of custo code about option!
> >> Is possibile to use the old option database structure with 5.6?
> > Well, you may have to tweak your database a bit, but you can still
> > the options table to store the variants. Just have the following
> > in your catalog.cfg file:
> > Options Matrix variant_table options
> > ...and change the ProductFiles line to:
> > ProductFiles products options
> > ...that should do it.
> > Peter
> > _______________________________________________
> > interchange-users mailing list
> > interchange-users at icdevgroup.org
> > http://www.icdevgroup.org/mailman/listinfo/interchange-users
> interchange-users mailing list
> interchange-users at icdevgroup.org
More information about the interchange-users