AND I QUOTE:
With an exception of .onerow-fluid (width) to px instead of %
I cannot say this enough -
I spent almost 4 months testing the px and % calculations for the responsive code, their is NO REASON to alter, add to, remove from this part of the responsive.css file.
If something isn't displaying correctly within the media queries provided, add a new media query but do not mess with the px or % of the responsive file.
@brian70809
I used the original responsive.css file (mine) and Anne's responsive file included in this template package and both resulted in a (disrupted) layout on your site.
You have 2 options and neither include altering the responsive.css file. LOL
1.) Back trace through all the files (you altered), mainly anywhere you added DIV's, viewing your HTML source, you have a few closing DIV's </div> showing. Also as stated before (THE FIRST REASON FOR THE RESPONSIVE CODE TO BREAK).
2.) Completely uninstall the template package, remove any other altered php files and start with a fresh copy of the template package
Without access to your files, I cannot trouble shoot or reproduce your results at all in any of my altered and highly customized templates.
Bookmarks