Ability to select trimmed version of the body in custom build modes

I actually tried to do this, but it turned out to be tricky. I will try it again, though! I think it's important to have access to the "snipped" body field of the node.

I'm not keen to replace a template preprocessor function from Views with the one from this module. Is there a way to do this without replacing template_preprocess_views_view_row_node()?

Given that we can have different template suggestions for each build mode, wouldn't it be better to store the teaser content in a different template variable and just print that out in the template instead of $content?

I will review this patch to determine if some of it can be used to accomplish at least this, but the rewriting of the theme registry this way isn't acceptable. The maintenance cost and risks are too high.

This doesn't exactly do what you are requesting, but it's what I've figured out so far.

node_view() unsets the teaser property on any node build that isn't a full normal build. This means there's no way to get the teaser later after running node_view without reloading the node. Fortunately, this is static cached, and we only need core node properties.

I wanted to get the filtered node body and teaser into my template, so I did this in the buildmodes_preprocess_node() function. It's generally a useful thing to do, but it doesn't affect the $content variable, and so you don't have fields and other node elements in there.

I think the right way to handle this problem is to implement hook_nodeapi for the 'alter' operation. This will allow you to re-set the body or teaser property and regenerate the content value for any node that's viewed... not just those viewed by buildmodes_node_view(). Then you can avoid altering the registry to replace the Views preprocessor function.

I just realized that you will need to add the "read more" link to the node links, because this is NOT added by core because it will believe the node is not a teaser.

I'm not going to commit a patch that replaces another contrib module's template_preprocess function with a different one. I'm not convinced this is necessary.

There are three other ways to attempt this:

1. Create a different node row style plugin for Views that is used instead of the one Views uses.
2. Attempt the hook_nodeapi($op = 'alter') method which would require no template changes at all.
3. Rewrite the output of the node template's $content variable when the node's build mode needs a teaser.