CM1 creates a file called Perc_decoration.css as part of the process to build our website. The code in this file was not created by our team. In that file on line 23 there is some code that states the below. When that line is removed the responsiveness to the American Tower website returns. Is there any way to remove this line from the css in CM1 so that our website can be viewed correctly on a tablet?
#content { margin : 0 auto }
Hi Ryan,
I will have to verify this with one of our engineers and get back to you, but it is my understanding that that particular rule set was supposed to have been removed from our global perc_decoration.css file in a recent release. Upon looking into this closer, this doesn’t appear to be the case.
If this is a bug, it will be easy enough to correct in one of our upcoming releases. For now, you should be able to work around this issue by appending an !important declaration to your margin rules for your #content region, to override the rule coming from perc_decoration.css.
Alternately, you could find and comment out line 23 from the source perc_decoration.css file on your CM1 application server at {cm1_root}/web_resources/cm/css/perc_decoration.css. Any changes made to this file will be reflected in your published environment once you run a full site publish. However, if this rule set still is present in a later release of CM1 (again, I will confirm the case here with one of our engineers), when you upgrade CM1 your changes would get overwritten.
Ryan,
Just to give you an update, it appears that that rule set was left in the perc_decoration.css file because certain Base CM1 templates still reference that Div ID. That said, we do have plans to remove that rule (and another overly generic rule) completely in an upcoming release. Can you tell me if you’ve had any success using either the !important declarations or commenting out that rule in order to progress with developing your responsive theme?
Hey Nathaniel,
I commented out the rule on the server side and it took 24 hours to push to the software but it appears to have worked. Thanks for your help. If this fix is not in the next update I will just repeat the process when we update our software.
That sounds good. I don’t expect this fix to make it into our immediate upcoming release, so if you do take that update, please be aware that you likely will have to re-implement this fix for the time being. I will be sure to update this thread when we have isolated a release version that will contain this fix.