Static pages plugin uses entries.tpl? WTF?

[yellowled]

Okay, so in case you were wondering why I asked about all this {serendipity_hookPlugin hook="entries_footer"} stuff in the first place, here's the reason why.

I'm working on a new template for my blog. My entries.tpl uses the pagination code Jude and I developed some time ago. This is only used in the entries.tpl, yet I get an empty <div class="pagination"></div> on static pages!

How's that possible? And is there a way to get rid of it? (.pagination is styled in this template, so the empty div is not only unnecessary but also noticable on screen)

(Yes, I know how to suppress it using CSS/display: none; -- but I'd much rather weed it out completely.)

YL

[Don Chambers]

Instead of display:none, how about wrapping your entire entries.tpl in this:

Code: Select all

{if $staticpage_pagetitle ==''} {* proceed only if this is not a static page *}
    .....
{/if}

[yellowled]

Code: Select all

{if $staticpage_pagetitle ==''} {* proceed only if this is not a static page *}
    .....
{/if}

See, this is the kind of stuff I never stumble upon on my own. Kind of like I'm wearing blinders or something. Jeez.

Tested ... aaand it works. Thanks.

(I'd still like to know the why here, though.)

YL

[Don Chambers]

Yeah, I stumbled on this same issue with Kinetic... sometimes I think Garvin planted little bumps in the code here and there just to see if we could find them!

I too would like to know why entries.tpl is called at all for static pages, since it has its own smarty templates. Would not be surprised to learn that is some kind of leftover to when static pages were first developed.

[yellowled]

Yeah, I stumbled on this same issue with Kinetic... sometimes I think Garvin planted little bumps in the code here and there just to see if we could find them!

Not bumps. Hooks. At least that's what I'd put my money on.

YL