This error drove me nuts for quite some time. Even your suggestion didn't fix the problem. Here is what I did to find the issue.

In the core CI code in system/libraries is a file called input.php I made a small modification to that file so that it would show the actual data in question.

Around line number 199

function _clean_input_keys($str)
{
if ( ! preg_match(“/^[a-z0-9:_/-]+$/i”, $str))
{
exit('Disallowed Key Characters: '.$str); // Added the variable to display.
}

return $str;
}

I certainly hope this helps others.

"Disallowed Key Character," however, IS the specific language CodeIgniter uses. That, in my opinion isn't as clear or familiar as the PHP error and can trip up users new to both. That's what this post is addressing.

"Disallowed Key Character," however, IS the specific language CodeIgniter uses. That, in my opinion isn't as clear or familiar as the PHP error and can trip up users new to both. That's what this post is addressing.

still, dropping the ?> is a good way to prevent the problem. thanks for reiterating the point.

@markus: in CI, each key name in the data array becomes a variable. $data['foo'] in your controller becomes $foo in your view. using a foreach loop seems unnecessary to me, unless you’re returning multiple database rows.

still, dropping the ?> is a good way to prevent the problem. thanks for reiterating the point.

@markus: in CI, each key name in the data array becomes a variable. $data['foo'] in your controller becomes $foo in your view. using a foreach loop seems unnecessary to me, unless you’re returning multiple database rows.

For this reason, it’s a good practice to leave out the trailing ?> closing tag when writing anything that’s not specifically a view/template.

You can get around this, though, by turning on output buffering.