link author name to user page instead of author page

Interesting idea, but not easily achieved without some coding. I'll look into adding this option, so that if link between a biblio author and a drupal user has been established you will have the possibility to use /user/xx/biblio rather than biblio/author/xx.

Probably within the next few days.

This is has been checked in and will be in the latest -dev version when it is next built.

Ron

P.S. look in the links section of the biblio settings page for the new option.

G'Day Ron,

This thread is just what I'm looking for, but am having trouble seeing how Biblio is handling the path to the user's profile.

I use the content_profile module, and path alias, so my user's profile pages are a long way away from the Biblio path, eg:
http://www.site.org/user/21/publications/register

The page I acutally want them to show up on is:
http://www.site.org/people/profile/joe-surname

This is the node produced by the content_profile module, and it of course stores the user's UID as the AuthorID, so the UID value is available for use...but it's not in my URL.

I understand this whole issue is downstream of the check to see if an author has been linked to a Drupal user...we don't mind non-Drupal authors to go to the bilblio author page.

There is a lot of customised functionality already in place on our user's profile pages, and I was assuming there would be a headache-reduced method of routing the Biblio author links over to the profile pages (which feature the Biblio listings).

What are your feelings? Is this complex, or simple?

Should be simple. I presume you are building your own publications list on the profile pages and not depending on biblio to do this? (i.e. in the "Profile pages" section of the 'admin/settings/biblio' page, you have NOT checked "Show publications on users profile pages").

Basically I can just do an path alias look up for "user/x" and it should return "people/profile/joe-surname", probably should have been doing this all along anyway ;-)

I've pushed the path alias changes to the 6.x-2.x branch...

http://drupalcode.org/project/biblio.git/commit/85521f5

Ron.

G'Day Ron,

Amazing work, as always! But I'm not sure if it's quite working for us yet....

Downloaded and upgraded about 4 hrs ago and the links have indeed changed, but perhaps too soon.

If we type this (previous biblio link format) straight into the browser:
http://www.site.org/user/21

Drupal grabs it and routes us to:
http://www.site.org/users/joe-surname

In the updated version of biblio, the links rendered on the page (eg, though the Biblio View element: biblio_author) are already of the form:
http://www.site.org/users/joe-surname

Drupal happily renders this URL as-is, and takes us to the same default 'profile page' as before (ignoring the customised cck and panels-driven profile page.

In the PathAuto settings, there is a separate path provided for Users...this is supposed to be used for "account pages" which is different to a "profile" page.

Our User path settings were pointed at: users/[user-raw]. I changed them to: people/profiles/[user-raw] and then flushed caches.

The biblio nodes appear to still be pointing author links to the /users/joe-surname path, and Drupal is not re-routing to the desired /people/profile/joe-surname path.

Sorry if I'm missing something out of the Drupal Newbie 101 Orientation...I was out that day!

I suspect that your user aliases are still pointed to "users/[user-raw]". If they were generated before you changed the setting to "people/profiles/[user-raw]" you will have to go to the alias list page and delete all the user aliases and re-generate them. I just tested this on my machine and this does the trick.

Bingo! Thanks as always...

Well well...back again!

The user account/profile management space is mind-bending for me, and the earlier "solution" appearerd to work but has now fallen apart.

The problem is in the concept of routing to the Drupal-reserved notion of a "user page", which is normally found at /user/%user or %uid.

This default can be overwritten by pathauto to something nicer...but it's still pointed at a "special" page that behaves differently depending on if you *are* that user, if you are logged in or not, etc. It's basic stuff, but bears repeating because...

Enter the concept of the "profile node" as built by CCK and assigned by the Content Profile module.

Regardless of alternative strategies, in this particular site, what I'm actually looking for is to route any Biblio author link (where that biblio author is paired with a Drupal user ID) to the Drupal User's *profile page*, not their Drupal 'user' page.

So we were steaming along with the solution in #13 til things started going weird with duplicate path entries in the menurouter table...don't want to go there again....

Now, we have clearly pulled the path to the cck Profile page distinct from the Drupal user page:
/people/profile/[name-raw] << nice cck Profile page
/people/user/[name-raw] << Drupal 'user page'

And biblio (latest 6.x-2.x dev) is happily finding the Biblio-Drupal users, and is writing links out to the *Drupal user page*.

My (humble, apologetic) request...
Is it possible to point Biblio instead at the user's *Profile* page?

Thanks at least for the read of the issue!
Kind regards,
JB

Hey John,

I've added a new setting (actually a whole new sub-section called Author links) in the "links" section of the 'admin/settings/biblio' page. There is now a "Path to profile page" text field into which you can enter 'people/profile/[name-raw]' (no leading slash) also don't know where [name-raw] is coming from, so that may or may not work :(

http://drupalcode.org/project/biblio.git/commit/153a6ad

Enjoy,

Ron.

Hey Ron, thanks for that! We'll give it a roll asap.
The token/substitution would be coming from the same source as you get in PathAuto, I guess.
Since this is all about routing links to a Content Profile, I wonder if there's an elegant solution by trying to hook into that module's logic to avoid replication of code and confusion of admin?

I did take a quick look at the content profile module, and didn't see an obvious way to do that, but I'll take another look.

I looked at the content profile code again, and if you have a path like "/people/profile/[name-raw]" then I suspect it must be "path auto" that is creating that, not content profile. As far as I can tell, content profile creates a path... /user/[uid]/profile, or since the profiles are just regular nodes, they can also be accessed by their regular /node/123 path.