Disable HTML correction

I have a similar problem. I try to use Smarty template syntax in the code editor. Now it changes the HTML.

from:

{foreach from=$messages item=message name=messages}
<table border="0" cellpadding="0" cellspacing="0">
   {if $message.title}
        <thead>
      <tr>
         <td width="20">&nbsp;</td>
         <td align="left"><h2>{$message.title|escape}</h2></td>
         <td width="25">&nbsp;</td>
      </tr>
   </thead>
        {/if}
   <tbody>
      <tr>
         <td width="20">
            &nbsp;</td>
         <td align="left">
            {$message.text}</td>
         <td width="25">
            &nbsp;</td>
      </tr>
   </tbody>
</table>
{/foreach}

You can configure CKEditor to ignore your custom tags, see the config.protectedSource option. There are also plenty of posts on this issue on the forum and in the Internet, so just search for that.

See also the "Output" articles from CKEditor HOWTOs here: http://docs.cksource.com/CKEditor_3.x/Howto

As said before, however, CKEditor will *not* output invalid (X)HTML code (e.g. with block-level elements inside inline elements etc.).

The only solution I can find online or on the forums to this problem is to 'not use it'. Surely there has to be some way to make this great library not **** up one's code?

config.protectedSource is not a good enough solution here for smarty loops. The only way around it we have found to work is HTML comments. 

e.g. 

<table>
<!--{foreach}-->
<tr>..</tr>
<!--{/foreach}-->
</table>

Then on form submit 

str_replace(array('<!--{','}-->'),array('{','}'),$data)

I'm still seeking the "perfect" solution.

Infact maybe just having protected source on the foreach loop is good enough? The code below protects all smarty tags;

config.protectedSource.push( /\{[\s\S]*?\}/g );

I'll try and figure out how to make this {foreach} only

So this issue should only really happen with foreach loops. The following code works for me:

config.protectedSource.push(/\{foreach[\s\S]*?}|\{\/foreach}/g);

My regex skills are weak so I don't know if this can be improved on.

See http://dev.ckeditor.com/ticket/7961. This is a known issue and there's no easy workaround.