wanted to add blogs to the /project/project-name pages so that they would be listed also, since these are likely (hopefully) to be a good source of daily project progress.
the fix turned out to be easier when the problem was recognized. the project page script already gets all the nodes for a named project, it then sorts them by type. for user-defined types we need to trim down the node list to only those tagged with the specific user defined type. for a core type, like blog, we don't need the extra queries since the type is embedded right in the node table. we can go right to selecting the "blog" subset of project nodes. this was easy to do by just adding a new function to list base types.
bug with elevating core types to level of user-defined types
if blogs (and other core types) are now elevated to the level of user-defined types we now have the potential for object cross over. with user defined types, we restrict to just one type of post: news, todo, etc. but these can be built from a blog, story, page, or book. this leads to having a post show up as a news item and a blog item if it is a blog item tagged as news.