On one Drupal 6 Intranet portal I enabled Content Profile, Token, Pathauto, Node Auto Title and Revisioning.
I log in as user 1 (Admin), and browse the user list. I click on a user that has no profile yet, and click on the "Create Profile" link. I see the new editable profile page which bears the name of the user I'm creating the profile for as non-editable title. So far this is what I expect.
When I'm done editing the user's profile, I hit "Save". Now I get status messages that tell me that some weird things happened while saving. Indeed, the page title is replaced with my name (the user who edited the profile), and the automatic URL aliases attempt at creating aliases for me instead of the user.
The replacement token pattern I use for Pathauto is: "who_is/[title-raw]"
The replacement token I use for automatic profile page title generation is: "[user-name]"
Clearly this Drupal setup is having problems in knowing which [user-name] to use: the account being edited or the user that edits a profile belonging to another account.
I am reporting this bug here, but it may be linked to recent upgrades of a couple modules:
- Automatic Nodetitles recently went from version 6-x-1.1 to 6-x-1.2
- Revisioning recently went from version 6.x-2.6 to 6.x-2.7
- Module Grants (on which Revisioning depends) recently went from version 6.x-2.5 to 6.x-2.6
Best regards,
Olivier
Comments
Comment #1
ShutterFreak commentedUpdate: this does only apply when someone creates a new profile for another user.
The module behaves as expected when editing someone else's existing profile.
Comment #2
ShutterFreak commentedIn debugging this issue I checked the entries in the 'node' table and in the 'node_revisions' table.
All node entries relating to the content type associated to the "content profile" module featured the following behavior:
To fix my setup I have to follow the following steps:
(replace NID with the a value returned by the previous query) (note: I did not try these queries so they may not work out of the box - but the idea is there)
Hope this helps in pinning down this bug.
Comment #3
fagoComment #4
locomo commentedsubscribe