Responsive Sheffield Blue v1.0

[picaflor-azul]

Hi
Hi

I have just changed the page width of our site by changing..

.onerow-fluid{width:/*980px*/950px;*zoom:1;/*background: #fff;*/margin:0 auto;}

I am just checking to see that, that is all that needs to be changed, or will this change upset the layout of the site somewhere else.

Many thanks for a great template.

Kind regards
Grandpaj

I can not tell you for certain that this is the only place that needs to be changed unless I make these changes on a test site somewhere. I would recommend testing everything out to see if this is the only change that needs to be made.

Thanks,

Anne

[rbarbour]

Hi
Hi

I have just changed the page width of our site by changing..

.onerow-fluid{width:/*980px*/950px;*zoom:1;/*background: #fff;*/margin:0 auto;}

I am just checking to see that, that is all that needs to be changed, or will this change upset the layout of the site somewhere else.

Many thanks for a great template.

Kind regards
Grandpaj

I can not tell you for certain that this is the only place that needs to be changed unless I make these changes on a test site somewhere. I would recommend testing everything out to see if this is the only change that needs to be made.

Thanks,

Anne

I am not sure for I haven't looked at the responsive.css file for this template so am unsure if Anne altered the px and % fluid calculations.

But in the original responsive.css file the px and % fluid calculation are precise to 75px (the code includes 12 div's at 75px to calculate total width) including margins and changing (1) to anything other than - or + 75px or its % equivalent will most definitely break at some point on some devise or screen size.

[RixStix]

Hi Anne,

I don't know if you've been following my other thread but you might want to take a look at the SQL patches syntax. It is not directly causing my issue but was identified as a side effect.

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 (configuration_id, configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, date_added, use_function, set_function) VALUES 
(NULL, '<font color="#0044ff">ACTIVATE Responsive Template by selecting Column Widths</font>', 'COLUMN_WIDTH', '2', ........

[picaflor-azul]

Hi Anne,

I don't know if you've been following my other thread but you might want to take a look at the SQL patches syntax. It is not directly causing my issue but was identified as a side effect.

rbarbour can you take a look at this? I have just added the patch from the DIY responsive template default.

Thanks,

Anne

[rbarbour]

rbarbour can you take a look at this? I have just added the patch from the DIY responsive template default.

Thanks,

Anne

Will Do.

[rbarbour]

rbarbour can you take a look at this? I have just added the patch from the DIY responsive template default.

Thanks,

Anne

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 (configuration_id,  configuration_title, configuration_key, configuration_value,  configuration_description, configuration_group_id, sort_order,  date_added, use_function, set_function) VALUES 
(NULL, '<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.

[RixStix]

I did not mean to imply that this was causing my problem or to stir a hornet's nest. I only wanted to relay what I had been told about the patch while trying to fix the other problem that just coincidentally appeared when installing the template.

[rbarbour]

I did not mean to imply that this was causing my problem or to stir a hornet's nest. I only wanted to relay what I had been told about the patch while trying to fix the other problem that just coincidentally appeared when installing the template.

By no means are you stirring a hornet's nest.

As you can see we have just started implementing this code into our templates and any and all findings are being handled promptly to ensure all bugs are fixed.

[rbarbour]

I did not mean to imply that this was causing my problem or to stir a hornet's nest. I only wanted to relay what I had been told about the patch while trying to fix the other problem that just coincidentally appeared when installing the template.

By any chance did you install another responsive template?

[picaflor-azul]

I am not sure for I haven't looked at the responsive.css file for this template so am unsure if Anne altered the px and % fluid calculations.

But in the original responsive.css file the px and % fluid calculation are precise to 75px (the code includes 12 div's at 75px to calculate total width) including margins and changing (1) to anything other than - or + 75px or its % equivalent will most definitely break at some point on some devise or screen size.

There are changes to these since I have made the left and right hand columns come out to 180px.

Thanks,

Anne