Allow node teasers in output, or views-based output of node list

crap i don't think this module does create a hotblock content type i just made that up. i think i created that content type a while back...

A simpler way to allow more customized output of nodes than trying to factor in views might be to simply create a theme function, which would allow an override of the node's output in template.php.

For example:

    //default to node view
    $oNode = node_load($oHotblocks_Item->nid);
    
    //we will respect node access unless the option is turned off, in which case a user needs standard node access or 'administer hotblocks' to see the node
    if(!hotblocks_access('view node',$oNode,$iDelta)) {
      return false;
    }
    
    $oHotblocks_Item->title = $oNode->title;
    $sRenderedView = node_view($oNode);  
  }
  
  $sControls = hotblocks_hotblocks_item_controls($oHotblocks_Item);
  $sFormat= '
    <div id="hotblocks_item-%d-%d" class="%s">
      %s
      %s
    </div>';
  if($sContext == 'reorder' && variable_get('hotblocks_reorder_titles',true)) { $sRenderedView = $oHotblocks_Item->title; }
  $sContent = sprintf($sFormat, $oHotblocks_Item->nid, $iDelta, $sClass, $sRenderedView, $sControls);
  return $sContent;

to

    //default to node view
    $oNode = node_load($oHotblocks_Item->nid);
    
    //we will respect node access unless the option is turned off, in which case a user needs standard node access or 'administer hotblocks' to see the node
    if(!hotblocks_access('view node',$oNode,$iDelta)) {
      return false;
    }
    
    $oHotblocks_Item->title = $oNode->title;
    $sRenderedView = node_view($oNode);  
  }
  
  $sControls = hotblocks_hotblocks_item_controls($oHotblocks_Item);
  return theme("hotblocks_node", $oNode, $sContext, $sControls );
}

function theme_hotblocks_node($oNode, $sContext, $sControls) {
  $sFormat= '
    <div id="hotblocks_item-%d-%d" class="%s">
      %s
      %s
    </div>';
  if($sContext == 'reorder' && variable_get('hotblocks_reorder_titles',true)) { $sRenderedView = $oHotblocks_Item->title; }
  $sContent = sprintf($sFormat, $oHotblocks_Item->nid, $iDelta, $sClass, $sRenderedView, $sControls);
  return $sContent;
}

that would then require a new form registration in hook_theme()

another idea might be to simply flag the node before passing it into node_view, so that way another module can hook into the nodeapi and recognize that the node is being rendered for the hotblock region:

    $oHotblocks_Item->title = $oNode->title;
    $oNode->hotblock_view = true;
    $sRenderedView = node_view($oNode);  

I might implement some of these ideas and put up a patch -- I'm trying to get this built to a set specification ASAP, so I might just work around this and do something else like a pointer content type with a nodereference field...

the more i look at this the less possible using a view seems to be...

I saw that in there, but the problem with that is there's no distinction to CCK that the $oNode->is_hotblocks_item means that the node is being loaded into a hotblock region. it's being flagged in nodeapi without checking to see who's calling on the node to load (which i don't think is even possible in hook_nodeapi() )

so.. that flag is put there regardless of who is calling node_load -- that's why i was thinking you could flag it before you call node_view in hotblocks_item_view(). I'm pretty sure if you did, then the flag would end up in the "view" op of the nodeapi function.

i'm not sure what you mean by cck build mode... sounds cool tho. do you mean like a mode you can configure "display fields" on the content type UI? that could be really handy, would that mode be usable in the theme level? like in the node-whatever.tpl.php or in the node_preprocess function for template.php ?

hey i'm sorry i think i might have to come back to this another time -- i went with the "pointer" method i briefly touched on before... i just created a "quicklink" content type and set it up with a node reference field so i can use that in sidebars to let client admins point to content independently from what exactly that content contains... not as cool as it could be but it gets the job done. i'll definitely use this in the near future, and will test/comment.

thanks!