I am building a website where an applicant registers for an account.
Upon registering for an account, using the "email registration" module, an account is created using what they input before the "@" in their email as their username.

I'm also using "Content Profile" to make the user's profile a content type. Then I enabled a Workflow with 3 actions to be show on this "Profile" content type.

I had it working so that when an administrator goes to edit the person's profile, there is a workflow box that has states such as "awaiting application" or "application received" or "application reviewed", etc ...

This is my second install where I see the Workflow box with the radio buttons disappear after enabling logintoboggan (I think that's what caused it).

I have used the Devel module to reinstall all the modules, and then unchecked the modules from the module list to try and get the workflow box to come back, to the point where "Content Profile" and "Workflow" were the only ones left, and I rebuilt the Workflow so that it had the 3 actions again... But no luck.

I read this thread, and it separates into 3 other threads with various solutions... all of which I tried (one of which says that the problem that creates this issue is fixed in 6-1.3 of the workflow module).

http://drupal.org/node/431904

Has anyone experienced anything? The first time around I was nearly done the project, and now it's dragged on because I have had to start over and can't figure out where the workflows are anymore.

Comments

Anonymous’s picture

Anonymous (not verified) commented

So after further investigation, I'm finding that if I create a user using the "add user" form through the administrator account, I can see the workflow box in the "Profile" content node that's created along-side the account.

If I attempt to create an account with the "Create New Account" form as an anonymous user, it won't inject the workflow box in the "Profile" content node that is created.

If I try to access the node while logged in as an administrator after it has been created by an anonymous user, the box is still not shown, so something likes in the "initiation" of the workflow being tagged to this content type when created by anyone but the admin.

I'm pretty sure all the permissions are the same too :-/

can anyone point in me in the proper direction?

Anonymous’s picture

Anonymous (not verified) commented

I've figured it out... but it's still something that we could probably look at collectively.

It seems as though the LoginToboggan setting for "set password" must be checked.

I think this has to do with the validation scheme for the node/user creation.

1) User's who register when "set password" is not enabled do not have the "workflow" box in their Content Profile that is generated alongside their user account.

2)When administrators register the user accounts individually, the "workflow" box is in the Content Profile because the account is pre-validated.

3) User's who register when "set password" is a requirement do indeed have the "workflow" box in the Content Profile because the "set password" feature is a sort of pre-validation.

So my question now is... could there be a way of applying workflows to a node before it's validated? That would make this both work easily and remove the need for a password selection on the registration form (a requirement by the client). I'm ready to make my point to the client that the password is needed, but they're not interested in hearing anything technical.

Thanks to anyone who viewed this and can help me have a form that functions as I require.

halmsx’s picture

halmsx commented
Version: 6.x-1.3 » 6.x-1.5
Component: User interface » Code

hi

i am also having the same problem. i just solved it by using the rules module. this can also easily be achieved with a simple hook_user module override.

johnv’s picture

johnv
Primary language Dutch
commented
Title: Workflow options dissappear from content type (edit page) » Workflow Form disappears from user edit page with Content Profile
Status: Active » Closed (won't fix)

Closing this issue. I hope you have found a solution. There is too much interaction with other modules to help in here. Also D6 is not maintained anymore and the module-world in D7 has been changed dramatically.