I understand the template author was trying to create a unique template. The buggy ie6 warning really should have been left out of the template or should have encouraged use of one of the plug-ins. Some of us are not coders and get really frustrated when things don’t work right. We are looking for design ideas in the templates, let us choose the other options without forcing them upon us. When you start stuffing in features that are available as optional plug-ins, you just add more ways for something to go wrong.
———
Removed from ja_kyanitelayoutsdefault.php
<?php if ($this->isIE6()) : ?>
<?php $this->loadBlock(‘ie6/ie6warning’) ?>
<?php endif; ?>
Removed “you are here” from ja_kyanitelayoutsblockstopsl.php
<strong><?php echo JText::_(‘You are here’)?></strong>
Changed ja_kyanite/css/ie.css – kept wrapper for future use
from
*html #ja-wrapper { margin-top: 205px; }
to
*html #ja-wrapper { margin-top: 0px; }
Removed from ja_kyanitelayoutsblockshead.php
<?php if ($this->isIE6()) : ?>
<link rel=”stylesheet” href=”<?php echo $this->templateurl(); ?>/css/ie6warning.css” type=”text/css” />
<?php endif; ?>
Removed now unused isIE6 function from ja_kyanitelibsja.template.helper.php
function isIE6 () { $msie=’/msies(5.[5-9]|[6].[0-9]*).*(win)/i’; return isset($_SERVER[‘HTTP_USER_AGENT’]) && preg_match($msie,$_SERVER[‘HTTP_USER_AGENT’]) && !preg_match(‘/opera/i’,$_SERVER[‘HTTP_USER_AGENT’]); }