Closed (fixed)
Project:
Content Profile
Version:
6.x-1.x-dev
Component:
User registration module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Nov 2008 at 18:20 UTC
Updated:
19 Mar 2009 at 09:10 UTC
all new content is named "ant"
Steps to reproduce:
- auto_nodetitle installed and configured for a profile content type
- go to user account -> edit, and create a profile using a subtab
- the new profile node is titled "ant"
It does work fine however if you use the "add coach profile" link on the pain profile page.
Comments
Comment #1
fagohm, indeed. Auto nodetitle works only on regular node forms. So best this is improved in ant.
Comment #2
fagohm, indeed. Auto nodetitle works only on regular node forms. So best this is improved in ant.
Comment #3
niklp commentedAnother reason why we should be using full node forms for content_profile_registration I think!
Comment #4
nadavoid commentedThis seems to be fixed by the 2008-Nov-24 dev release. Nodes get programmed titles. Could someone else confirm too please?
Comment #5
fagoAh, I see. I thought this is about the registration integration. Indeed the base module show now with the fix in place work fine. So I sort this issue into the registration integration queue now.
@NikLP: Unfortunately this won't help in this case. But this case can be easily fixed by letting ANT rely on nodeapi.
Comment #6
nadavoid commentedfago, actually, earlier, I think this was happening both when editing and when registering. Earlier, all nodes were titled "ant". Now they're not. This is definitely better! Thank you!! But after a little more testing (registering), it looks like it's naming the new nodes after the username.
I have a content type called "coachprofile" and a role called "Coach" . Here's the rule that I have set for coachprofile:
coach-[author-uid]-profileI register as a new user, using username "coach2".
The new user is created and a new coachprofile node is created, named "coach2" instead of "coach-11-profile".
Comment #7
fagoyep, currently it's hardcoded to the username during registration. Anyway ANT fails to apply its title during registration.
Comment #8
alanburke commentedMaybe I've slightly misunderstood this but...
As far as content_profile is concerned, this is an issue with ANT.
ANT isn't using the nodeAPI correctly and therefore any rules configured for a content type via ANT will be ignored on user registration.
Is that correct?
Comment #9
fagoI've just improved the ant module - please test again with its latest dev snapshot.
Comment #10
fagoI assume this is working now.
Comment #12
rizzo commentedSorry, was this bug supposed to be fixed in 6.x-1.1? I'm seeing similar behavior on my site. I created this issue: http://drupal.org/node/379666
I can only get ANT working when I do the batch updates, which isn't very friendly for the non-techie site authors.
Comment #13
asak commentedsubscribing.