[ic] Cannot add new simple option in 4.9.8-release

NOW Website Coordinator webperson at now.org
Mon Sep 22 22:29:27 EDT 2003

I downloaded the latest 4.9.8 version -- which I assumed would have the 
patch described below.  But I can't for the life of me get the new options 
to work, let alone the old ones.  Without OptionsEnable, the catalog works 
with the old options, but I can't edit any of them (the catalog dies with a 
resounding crash and sometimes a core dump and then needs to be restarted 
or it gives errors like these:

lj1002.inktomisearch.com - - [22/September/2003:20:21:59 -0400] store 
Died in server spawn: Can't call method "new" on an undefined value at 
/usr/local/interchange/lib/Vend/Data.pm line 751.).

In a test catalog, I added OptionsEnable option_type, added that field to 
products, but can't get anything to save.  As soon as I click on Options, I 
am given the Select Options Type dialog (even if I manually have added 
"Simple" in) but then Update does nothing.

One thing I noticed in the error log was the line:
2003:20:43:14 -0400] mycatalog 
/cgi-bin/mycatalog/admin/item_option_old.html Safe: DBD::mysql::st execute 
failed: Column 'sku' cannot be null at 
/usr/local/interchange/lib/Vend/Table/DBI.pm line 1380.

My options table does indeed have lots of blank sku fields because it still 
has the old style entries, which had two lines for every item:

code o_master sku o_group o_sort phantom o_enable o_matrix o_modular 
o_default o_label o_value o_widget o_footer o_header o_height o_width 
description price wholesale differential weight volume mv_shipmode 
o_exclude o_include
TS-NOW 1         1 0 0             NULL NULL
TS-NOW-size   TS-NOW size             size S,M,L,XL,XXL

My questions are:
1) Do CVS changes automatically get loaded into the "nightly build"?  Or at 
least should I assume that the one mentioned below from July would be there 
in September?
2) What should my options table look like?  I'll manually edit if I knew 
what it should look like.
3) Suggestions on how to convert from an old options table to a new one?


I'm currently running <http://www.icdevgroup.org/>Interchange 
4.9.8-200309210658 with mySQL in the test version and PostgreSQL in the 
production version.

>[ic] Cannot add new simple option in 4.9.8-release
>Mike Heins mike at perusion.com
>Wed Jul 30 19:15:27 EDT 2003
>Previous message: [ic] Cannot add new simple option in 4.9.8-release
>Next message: [ic] Cannot add new simple option in 4.9.8-release
>Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>Quoting Reid Sutherland (reid-ic at thirddimension.net):
> > This will patch the _new_ addition of a 'simple option' problem I've
> > explained in my original email (below).  This patch works for me, not
> > sure if it's the "right way" to fix it, but it works none the less.
> >
> > I'm also going to write a HOWTO to deal with the new 4.9.8 option system
> > (upgrading from 4.8, etc).  The current documentation is sparse, and
> > confusing at times.  But I've been able to get it working for myself, so
> > I'll put it in writing and submit it to the list in the hopes it helps
> > others.
> >
> > Patch for simple options follows:
> >
> > --snip--
> > --- lib/UI/pages/include/Options/Simple-orig  Fri Apr 11 19:30:38 2003
> > +++ lib/UI/pages/include/Options/Simple      Wed Jul 30 14:59:25 2003
> > @@ -25,7 +25,7 @@
> >  [/perl]
> >  [/if]
> >
> > -[if cgi opt_groups]
> > +[if cgi opt_group_]
> >      [perl tables="[scratch option_table]"]
> >          my $otab = $Scratch->{option_table};
> >          my $odb = $Db{$otab};
> > --snip--
> >
> > Take care everyone,
> >
>Thanks -- actually, I just added:
>[or cgi opt_group_]
>below the existing one. This should fix other people's problems
>with creating new options when no previous options exist.
>Fixed and credited in CVS -- thanks!

More information about the interchange-users mailing list