I had a lot of trouble setting this up (as you might have guessed) because of the number of modules involved. I did get it to work, but I realized that the nodeprofile and nodefamily components were overkill for me. I have two membership types. One type creates a lonely node and goes to the account editscreen. The other goes right to acount edit. It seems that I can't disable the 2 modules in question because of the dependencies.

I guess I am asking how dependet is it? Is it just that you configured the .info file that way, assuming usage like your situation? Or is there really dependencies?

Comments

rconstantine’s picture

rconstantine commented
Status: Active » Fixed

There really are dependencies. I call functions from pageroute and nodeprofile modules.

In the future, the ideal solution to this problem would include the addition to core of what some have called the "supernode". A supernode would simply be like an empty shell that other modules could expand on. You would not be able to create supernodes themselves. For example, nodes as we now know them would descend from supernodes, but expand on them. Comments, profiles, and other things would also descend from supernodes and so all of these items could be worked on with the same code.

Right now, using nodes for profiles adds a lot of 'weight' to profiles that is not needed. Nodes come with the ability to have comments, which aren't needed. Other modules add capabilities to nodes which are also not needed for profiles. If profiles were descended from supernodes, however, CCK could be made to work with them without all of the other things that go along with nodes. In fact, if supernodes were done correctly, a new version of CCK could work with all kinds of supernodes. This would allow customization of comments, nodes, profiles, and more. If supernodes get implemented, and CCK is rewritten to handle them, then the nodeprofile and nodefamily modules would either go away altogether or be greatly reduced in size, by which I mean, only add those features not in core.

Sorry to ramble, but if you'd like to see this functionality in the future, find any threads talking about supernodes and add your support. Maybe it can be added to version 7 of Drupal if enough people want it.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.