The problem is incorrect node_view() usage in node.views.inc. This patch resolves the issue for me.

CommentFileSizeAuthor
node.views_.inc_.fixed-node_view.patch940 bytesJames Andres

Comments

merlinofchaos’s picture

merlinofchaos commented

$page must be false unless you happen to be showing that node and only that node. Views is designed to show a list of nodes; setting $page to TRUE is actually incorrect. So your base assumptions seem to be incorrect.

merlinofchaos’s picture

merlinofchaos commented
Status: Needs review » Closed (won't fix)

If $page is true you will get interesting side effects such as breadcrumb trails changed, titles changed and other things by various modules that utilize hook_nodeapi.

dawehner’s picture

dawehner
Primary language German
commented
Status: Closed (won't fix) » Needs review

I'm not really sure whether this is right. If you read the parameters

$teaser Whether to display the teaser only or the full form.
$page Whether the node is being displayed by itself as a page.

So we never display the node on the page, so it has to be always FALSE, or not?

James Andres’s picture

James Andres commented

Hmm, perhaps then instead of calling node_view(). The node_render(), theme('node') ..etc. should be called individually to ensure variables are set correctly at the theme layer.

Thoughts?

merlinofchaos’s picture

merlinofchaos commented
Status: Needs review » Closed (won't fix)

No, node_view is definitely the right way to do it. In general, if you want an actual node view page, you should use a method that isn't Views to get it. Panels + Page Manager excels at this, for example.