Display Author's username to link to content profile

You can change it with theme_username but most people simply put the information from content profile on the user page rather than changing all the links to go to the node.

Michelle

Thanks for your feedback!

First - How do I use theme_username to change the links? I know just enough php to get me into trouble so explanations are appreciated.

Second - please explain what you mean by "it's just technically a node reference" and how I can use that to reroute people to the content profile.

Third - The suggestion of similar profile fields on content profile & user pages -- Tried that. It made my beta testers really unhappy. They got very lost and confused. There was no consistency.

Why? Well, having most of the member links on the site take the customer to a lovely content profile page (that looks similar to a myspace page, with a wall and personal photo albums) but then having the author links take the customer to a page that looks completely different, an unorganized user page that doesn't have the member's "wall," or other features that can't be shown on a user page (thus, the reason for using the content profile module), causes anxiety for customers.

Right now I have a button on the user page that they can click on to get to the content profile page. But that's ridiculous. Customers should only see one profile for each member and feel confident that they will get to that same profile any time they click on that member's name throughout the site. That's just good usability.

I know this isn't a TNT problem. This is a problem for anyone who uses content profiles. I've seen sites who are using content profile and their author links take them to the correct profile. So I know there is a solution out there somewhere. I'm just looking for any kind of help to fix it. I've seen posts from a lot of others with the same problem.

Thanks again for your help!
Tamela

I see what's happening. I bought a book online on creating a community. It had us create the profiles with Panels using the node/%node page. What I should have done (by what you are saying) was created it in the user/%user page.

I've started doing it and see why the book gave the other way - the node/%node is easier to set up. Building the Panel in node/%node allows access the node content, node comments etc. when bringing in the content from the content_profile. With user/%user, I'll need to make a view of the content_profile information. In fact I will need to use views to do a lot of things that I just brought in easily in the node/%node page. Arrggh!

But then the user links will work correctly all over the site.

Plus, like you mention, using the actual user profile page will have easier access to the other profile information.

Thanks for being patient with me. I hope this helps other who bought the same book.

Building it on the user page is no harder than the node page and is less messy. You just need to set a relationship and get the node context. You might want to try Advanced Profile Kit. Even if you don't end up using the module, you can get an idea of how to do this from that. Or just look at step #4 here: http://drupal.org/node/532558

Michelle