[ic] Items Options update in Admin UI fails silently - new error message

[Gert van der Spoel]

>>>> Hillary Corney wrote:
>>>> Hi all, 
>>>> 
>>>> Debian Woody non-threaded perl 
>>>> 
>>>> When I upgraded from 4.8 to 5.2 I lost all the options in the  product  
>>>> Items list even the options column disappeared. 
>>>> 
>>>> Tying to recover the situation is proving very frustrating :-( 
>>>> 
>>>> I have searched the FAQ's and this list without finding any  useful  
>>>> info except that I was using the Admin UI as intended. 
>>>> 
>>>> The options TAB brings up a menu which has radio buttons for 
>>>> 
>>>> None
>>>> Matrix
>>>> old 4.8 options
>>>> simple 
>>>> 
>>>> Update 
>>>> 
>>>> selecting any of these buttons and clicking update has no effect  the  
>>>> form blinks and reappears with the same radio buttons with  "None"  
>>>> selected 
>>>> 
>>>> There are no errors in any of the the logs at all, 
>>>> 
>>>> The only thing that has happened is the options column has  appeared  
>>>> in the items list with every option for every item set  at none and  
>>>> clicking it brings you back to the failing options  update page. 
>>>> 
>>>> Can anyone suggest what I should look for as I cannot see where  the  
>>>> problem lies.

> On 2 Nov 2005, at 10:50 pm, Hillary Corney wrote: 
> 
>> Hi Nigel, 
>> 
>> Sorry you are having problems too. I have at least at last managed  to 
>> get an error message which might help point someone better at  SQL than 
>> me in the right direction: 
>> 
>> table options: set_slice error as called by Vend::Interpolate:  
>> DBD::mysql::st execute failed: You have an error in your SQL syntax  near 
>> 'WHERE code = '00025'' at line 1 at /usr/local/interchange/lib/ 
>> Vend/Table/DBI.pm line 1251. query was:update options SET WHERE  code = 
>> '00025' values were:'' 
>> 
>> This appeared in the browser when attempting to click the radio  button 
>> to insert an option into a new item on a new catalog.  Interestingly the 
>> option to use old 4.8 options did not appear in  the radio buttons list 
>> so something was detecting the fact that  this catalog was new. 
>> 
>> I am now looking at /usr/local/interchange/lib/Vend/Table/DBI.pm  line 
>> 1251 for clues as unfortunately options are an essential part  of this 
>> catalog as is a working Admin UI 
>> 
>> Cheers 
>> 
>> Hillary 
>> 
>> 
>> On 2 Nov 2005, at 9:06 pm, Nigel Titley wrote:
> 
> HI Again Nigel, 
> 
> I uncommented the debug comments either side of the block of perl in / 
> usr/local/interchange/lib/Vend/Table/DBI.pm around line 1251 and got  the 
> following error log entry can anyone help to decipher where the  problems 
> lie now? 
> 
> 
> > query was:update options SET  WHERE code = '00025'
> > values were:''
> 82.69.222.70 YLKTNCt6:82.69.222.70 - [02/November/2005:23:17:27  +0000] ng 
> /cgi-bin/ng/admin/item_option_old.html bad field o_modular  in record 
> update, value=1
> 82.69.222.70 YLKTNCt6:82.69.222.70 - [02/November/2005:23:17:27  +0000] ng 
> /cgi-bin/ng/admin/item_option_old.html bad field o_master  in record 
> update, value=1
> 82.69.222.70 YLKTNCt6:82.69.222.70 - [02/November/2005:23:17:27  +0000] ng 
> /cgi-bin/ng/admin/item_option_old.html bad field o_enable  in record 
> update, value=1
> 82.69.222.70 YLKTNCt6:82.69.222.70 - [02/November/2005:23:17:27  +0000] ng 
> /cgi-bin/ng/admin/item_option_old.html bad field o_matrix  in record 
> update, value=0
> 82.69.222.70 YLKTNCt6:82.69.222.70 - [02/November/2005:23:17:27  +0000] ng 
> /cgi-bin/ng/admin/item_option_old.html set_slice error as  called by 
> Vend::Interpolate: DBD::mysql::st execute failed: You have  an error in 
> your SQL syntax near 'WHERE code = '00025'' at line 1 at / 
> usr/local/interchange/lib/Vend/Table/DBI.pm line 1251.
> >

Hi Hillary, 

I don't have a setup atm where I can do some tests, but perhaps the 
following helps a bit: 

 - that old 4.8 options are not anymore showing is because you are not 
looking at  item_option.html   anymore in the admin, but you get 
item_option_old.html .  This has to do with the yes/no setting of 
OptionsEnable  (see top of item_option.html in lib/UI/pages/admin) 

 - perhaps the CVS log for item_option_old.html gives some away about the 
fields that are marked as 'bad' and something regarding variants: 

http://www.icdevgroup.org/cgi-bin/cvsweb/interchange/dist/lib/UI/pages/admin 
/item_option_old.html?r1=2.1#rev2.1 

Hope this helps a bit. Good luck! 

CU, 

Gert