I see - this is different to my "normal template" results, as this is kinetic. You know I don't have the (closed) sources, so I can not tell you.
That is why I asked, how you managed to get entries.tpl processed in a staticpage. I just wanted to state by this, that the normal workflow does "not process" entries.tpl on staticpages at all, while set empty.
All the other plugin_contactform.tpl, plugin_guestbook.tpl and so on check correct for $staticpage_pagetitle, this is the same like in plugin_staticpage.tpl. Since this is the normal workflow state, this for sure points to a stricter set scoping usage, which is good in my eyes, since it is closer to the real workflow!
I know about this old YL thread. It is just about the total opposite, since it wants to get rid of an outer div for the empty set {$ENTRIES} - entries.tpl. That is why I already asked, if you mean that there is no empty $staticpage_pagetitle == '' var available any more? And suggested to use:
Code: Select all
{if !$staticpage_pagetitle or empty($staticpage_pagetitle)} {* proceed only if this is not a static page *} {/if}
instead. (If this may be one of the problems we should check and repair this in all templates)
To give a helping hand on this "scoping issue" in Kinetic, and we know Smarty3 is more straight than its predecessor, I definitely need to know in detail how this is done on your side, to reproduce this behaviour.