After registration, profile node do not have "Read/Write" comments

Having the same issue, subscribing.

Well, nothing ?

I can confirm this.
I looked into content_profile_registration module and i suspect that the content_profile_registration_user_register_submit function is to blame for this. But at the moment I don't have a solution. I'll look into this later when i'll have some more time.

This is a really big issue, because this is the only way for me to automatically create a node for every registered user,
I am using advanced profile kit, and if a user don't have a node created, then the comment wall of the user's page is not created.
any fix for this anytime soon ?
Thanks.

same problem.... tried to go back a version, but beta2 doesn't have user registration module... subscribing.

same issue here.

i have the same problem. does anybody found a solution?

Subscribe. Is anyone taking a look at this problem? (I tried, but beyond my meager abilities...)

The problem is that when using the content_profile_user_registration it does not follow the comment/publishing/etc. settings defined for the content type. When you put the default to "not pulished" the node will be published after the user has created an account.

so whats the solution for this issue?

I really need a solution for this. subscribe

I am having the same issue. I have to manually enable comments every time somebody new registers.

I am using the latest dev version!

Where is the maintainer? Why he does not respond?

disabling content fields on registration seems to work for me.

After registration a user should create his profile. this seems to work.

subscribing

I need this too. Yes it does work with content fields on registration disabled but I need that. Hopefully there's a solution soon. This is much needed.

Thanks for the module though. It's quite helpful.

Phil

subscribing. this is urgently needed for our site.

Can we find another solution ? maybe we can do it using rules ?

This Module has a high responsibility. So where is the maintainer?

If you are tired of waiting for this issue to be solved just do it with rules !
works like a charm.

hi tsi,

can you give us a short instruction?

Sure,
first of all, you should have Rules and the latest Dev of Token.

then:
1. Create a new rule, I called it uprofile_creation
2. The event is when "user account has been created".
3. You need only one action - "Add new content"
4. Set author as "registered user"
5. I also set the title to [account:user] so the title is the user name but it can be anything you want
6. Then set the content type to be created, in my case 'uprofile'.

and thats it, if you are still having problems I can give you my exported rule, but this is really very very simple.
Good luck !

I follow this so far but I'm confused about the item at the bottom of action the variable XXX setting, with label and machine readable label. What are these for and what do they do?

The other thing I want to do is to force data collection from the new use so that has to be in the profile form. I then want to pull that into this uprofile to display it there. I think for that I need a view to grab the data then cck to pull the view in, unless there is a simpler way?

tsi! thats it!

tsi, when somebody changes the title of his content profile a new node will be build instead of repleace the old one. a user is able to create as many uprofile content he wants!

Not in my case...
you meen it creates a new blank node ?
Do you have "Use this content type as a content profile for users" checked at the bottom of /admin/content/node-type/uprofile ?
Did you set the author of the node as "registered user" (#4 in the list) ?

yep i did both :\

i am very stressed because the maintainer says nothing to this issue for weeks...

Confirmed this is an issue. It is caused by the nodeapi prepare hook not firing which is what comment.module uses to load the default from the content type settings. There are other settings besides just comments that need to be defaulted so I have use the node api the same as the the content create form does.

In content_profile_registration.module > content_profile_registration_user_register_validate() > approx. line 136 add these two lines:

  module_load_include('pages.inc', 'node');
  node_object_prepare($node);

Your resulting function should look like this:

/**
 * Validates the user registration form
 */
function content_profile_registration_user_register_validate($form, &$form_state) {
  foreach (content_profile_get_types('names', 'registration_use') as $type => $typename) {
    $node = new StdClass;
    $node->type = $type;
    module_load_include('pages.inc', 'node');
    node_object_prepare($node);

    foreach ($form['#field_info'] as $field_name => $label) {
      $node->$field_name = $form_state['values'][$field_name];
    }
    content_validate($node);
    $form_state['content_profile_registration'][$type]['node'] = $node;
  }
}

I'm not rolling a patch for this as it is simple and I don't feel like re-rolling it until it gets in.

Great OFF. Thanks for testing.

Please do not set issues to fixed though unless you started the issue or you are a maintainer of the project. The issue is not "fixed" until code is committed to the repository. If you would like to let it be known that the patch has been properly tested and reviewed you can set the status to "Reviewed and tested by the community". If your review is not a complete review with understanding of the code then just leave the status at "needs review" so that other may review it so that it will continue to get more people reviewing the code for accuracy.

Thank you for marking your feedback though so that we know it is working for people. Also report back if you find any issues related to this.

i will test it today and will inrorm you.

it seems to work! what a good message!

I've incorporated+committed the fix, please test.