Testing...

To test the modules I've written just follow the instructions of the nodeprofile README Please fill bug reports to the appropriate projects on drupal.org. Please also report which parts should be better documented. Thanks!

Demo!

I've just created a simple nodeprofile demo. Login and try :)

I've just committed a major update to the pageroute module. I've reorganized the page types and created a new one: the node management type. The node management page allows one to add/edit/delete nodes from a configurable content type. It shows a themeable list of already created nodes and allows editing and deleting if the user has access. The node management page type was the last important piece missing for nodeprofiles: A userfriendly way to create several nodes of the same type.

I've separated the modules into own projects, as they are not only for nodeprofiles useful. Now there are the following drupal projects: Node Profile Node Family Views Fusion Pageroute

I've just committed an inital version of the pageroute module. The module can be used to provide an userfriendly way for creating and optional editing several nodes.

I've started working on providing a userfriendly way for filling out the nodes of a profile in a through steps. I started with providing a unique url for each content-type which restricts its number of creatable nodes per user to 1 - as it happens for a nodeprofile content type.

I've created an updated version of the firefox search plugin. (there was already a plugin which still used drupaldocs.org and so was broken) additional to the updated HEAD plugin i added a plugin for 4.7.

By doing the nodefamily views integration I ended in writing the module views_fusion.

Views Fusion allows one to fuse multiple views into one. So you can build fusioned views that display information that is stored in multiple nodes - useful for tabular views. It uses node relations for joining the appropriate nodes together.

In the last days I was working on the views integration for the nodefamily module. Unfortunately it turned out to be more complex than I thought originally. What I wanted to do, was that views is able to automatically join the node tables of different nodes together, so that one is able to list information of both nodes. But I noticed that this approach has some downsides. They are:

I have done the views integration for the usernode module. With it's possible to create user listings using views. The next step I've planned is to add views integration to the nodefamily module in that way, that it would be possible to display profile fields like "Surname", "Address", .. in the userlist.

at http://drupal.org/node/73245#comment-115470 the suggestion came up to reuse the author field of the node table for linking users with usernodes.