I assume due to some bug in the parser,

{exp:navee:nav nav_title="header" selected_class="on"}


    <li class="yes"><a href="/foo">Foo</a></li>
    <li><a href="/bar">Bar</a></li>
    <li><a href="/baz">Baz</a></li>

While I am able to change the styles, it would be highly preferable to overcome this issue, as the navigation is being retrofitted.

Has anyone else hit a similar issue?

1 Answer 1


I've had a bit of a poke around in EE core, and found the likely culprit. (system/libraries/Template.php:1690, in fetch_param())

// Making yes/no tag parameters consistent.  No "y/n" or "on/off".
  case 'y'  :
  case 'on' :
    return 'yes';
  case 'n'  :
  case 'off'  :
    return 'no';
  default   :
    return $this->tagparams[$which];

It would seem that the system translates all instances of y, on, n, and off into different values with no option to disable this functionality for modules using the function.

Frankly, I'm disappointed.

For now, I'd presume this impossible to fix without modifying core files.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.