picaflor-azul:
rbarbour can you take a look at this? I have just added the patch from the DIY responsive template default.
Thanks,
Anne
DrByte:
Syntactically the patch you've been given isn't properly designed to work in the SQL patch tool.
Try removing the first field from those INSERT statements, since it should never be supplied if it's just gonna be auto-incremented (null) anyway. I've highlighted them here, from your first code snippet:```
INSERT INTO configuration ([B]configuration_id,[/B] configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added, use_function, set_function) VALUES
([B]NULL,[/B] '<font color="#0044ff">ACTIVATE Responsive Template by selecting Column Widths</font>', 'COLUMN_WIDTH', '2', ........
I get the same result with configuration_id VALUE NULL as I do if I remove it from the SQL patch
Result = highest configuration_id +1
I will update my template packages at my earliest convenience, IMO this has nothing to do with the blank configuration key issue of @RixStix
However, DrByte is the man and if he says "remove it", remove it.
Maybe DrByte can weigh in on how to go about doing this.
I would suggest including a patch to delete current configuration_key
DELETE FROM configuration WHERE configuration_key = 'COLUMN_WIDTH';
But this will have no effect if the configuration_key is blank
Changing the sql_patch is easy enough
INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added, use_function, set_function) VALUES
('<font color="#0044ff">ACTIVATE Responsive Template by selecting Column Widths</font>', 'COLUMN_WIDTH', '2', 'Width of the Left and Right Columns<br />0 = Use Default Template Settings<br />1 = 75px<br />2 = 150px<br />3 = 225px',@configuration_group_id, NULL, NOW(), NULL, 'zen_cfg_select_option(array(\'0\', \'1\', \'2\', \'3\'),');
Even though the SQL patch tool recognizes configuration_id as an AUTO_INCREMENT value and ignores it using the original patch.
I will copy this in the other thread as well in hopes to get a response from the man himself.
