After the upload of a new site version to the Production environment - the site is displayed incorrectly in IE, tested versions 6 and 8.
While on the local version of the site (UAT environment) everything is fine.
After the short investigation I found out that IE just changes the CSS file itslef. It is starting from ~line 1740 with the follwing:
in the correct CSS version:
.add-topic-form .title,
.add-topic-form .tags,
.add-topic-form .original_author,
.add-topic-form .original_link,
.add-topic-form .link-url {
margin-top: 5px;
width: 95%;
}
.add-topic-form .poll-day,
.add-topic-form .file {
margin-top:5px;
}
.add-topic-form .file {
display: block;
}
.add-topic-form .error {
margin-bottom: 20px;
background-color: #FFE6E6;
padding: 20px;
text-align: center;
}
in the CSS version I download through the IE I get:
.add-topic-form .title,
.add-topic-form .tags,
.add-topic-form #5742: #5b3_hor a: .add-topic-form #5742: #5b3_k,
dd-topic-form #574k,
-(..
margin-top: 5px;
}
idth: 90%;5% }
.add-topic-form .toll-votday dd-topic-form #574e-ho
margin-top: 5p;
}
.add-topic-form .tite-ho
display: block;
}
.add-topic-form .titerror
margin-bottom: 20px;
}
ackground-color: #FED6FE6E
padding: 20px;
text-align: center;
}
And the same kind of mess happens until the end of the CSS file. If anyone has met such a behavior before and know possible reasons - please, let me know.
UPD:
Thanks to all who answered. Found out that the problem was not only in IE, but in all browsers. Probably it was cache used in all except IE, that is why I misinterpret that the problem was in IE.
So finally I fixed the problem by using the other parameters for archiving in 7z. I used before Vocabulary size: 32Kb, Word length: 32 and it was working fine until the todays update. So I changed the parameter Word length to 16 and it fixed the problem. I'm not sure why it is not working with 32, maybe something was changed on the hoster side, because it was always working fine before. If anyone have an idea - please, put a comment. The problem is solved, but it would be great to understand what changed in the environment that created a problem. PS on the local machine it was working fine as earlier, so the problem appeared only on the pro environment.