[CMS] why does vbcms_article_populate_start (end) load on CMS section pages?

[tpearl5]

Why does vbcms_article_populate_start (end) load on CMS section pages? Am I missing something?

[Wayne Luke]

I only see those hook locations called from within article.php of the vbCMS package.

If I had to make an estimation, I would say it could be called in the section because the hooks are part of the article view and that could be called for previews as well.

[tpearl5]

ugg... I was afraid of that. Is there any hook that is unique to the article page only?

[Wayne Luke]

Maybe vbcms_article_defaultcontent_start and vbcms_article_defaultcontent_end.

Haven't really looked into them much. There might be more information on them at www.vbulletin.org.

[Dead Eddie]

ugg... I was afraid of that. Is there any hook that is unique to the article page only?

Use whichever of the vbcms_article_populate_* hooks make sense and wrap your code in

if(self::VIEW_PAGE == $viewtype) 
{ 
} 

That only fires if it's putting together a full page (likely it'll also fire if you've got an article displaying full content on a section page, though, which may or not be what you're looking for).

[tpearl5]

I'll give that a try, thanks!

[tpearl5]

btw, I figured out that this hook is called because the section pages call all hooks an templates used on article pages to display the article preview. IMO, this is a completely backwards way of doing the preview. Why not have a separate preview template?