Well, at first glance the source of trouble appears when a new clonable template gets opened in browser the very first time (to get registered in backend) - and cms:dump outputs
k_template_is_clonable: 0
I could say it is not meant to be so. One is not expected to refresh the template in browser again to get the system variable correctly read from db. Perhaps, @KK should review the Couch code? Hopefully he can recreate the issue and would thank you later

The rest is obvious - the first time an editable gets registered because cms:else is taking the execution, the next time it gets removed, because template is recognized as clonable and editable's definition is not appearing anymore (considered deleted by user).
When this is fixed, I suggest to rewrite your snippet anyways, beacuse it is better to place editables inside cms:template block. And it would look like this (with one-liner setting of meta_title) -
- Code: Select all
<cms:template title='News' clonable='1' >
<cms:if k_template_is_clonable='1' >
<cms:editable name="meta_title" order="1" group="meta" label="Titel" type="text" />
</cms:if >
</cms:template>
<cms:if k_is_page>
<cms:set meta_title="<cms:get 'meta_title' default=k_page_title />" />
<cms:else />
<cms:set meta_title=k_template_title />
</cms:if>
<title ><cms:show meta_title /></title >