Closed (works as designed)
Project:
Auto Assign Role
Version:
6.x-2.0-beta1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Dec 2010 at 03:52 UTC
Updated:
22 Oct 2014 at 17:05 UTC
Jump to comment: Most recent
Comments
Comment #1
nohup commentedOn the content type page in the "User Registration" fieldset check the box which says "Other form elements (except for required CCK fields)". Please refer to the
README.txtfor details.Comment #3
christowm commentedHi Nohup,
Thanks for the reply. I forgot to mention in my previous post that I did actually have the checkbox checked for 'Other form elements (except for required CCK fields)' under the 'Hide form fields:' section of the 'content profile' tab. Still no luck, the body element is still showing up.
Some additional information, I am using Pressflow 6.20 along with a bunch of modules, most notably CCK 6.X-2.8, Automatic Node Titles 6.x-1.2, and Auto Assign Role 6.x-2.0-beta1. Any additional thoughts on what the culprit might be?
Comment #4
christowm commentedbump
Comment #5
nohup commentedHi Mitch,
I created a setup with
Pressflow: 6.20.97
CCK: 6.x-2.8
Auto Node Titles: 6.x-1.2
Auto Assign Role: 6.x-2.0-beta1
Content Profile: 6.x.1.0
Created two profiles, developer and social. Used "submission form settings" to remove the body field from both the content types. Configured both to be used for registration (without autoassignrole), the body field did not appear. Configured autoassigrole for developer and social roles, assigned paths for each role and configured content profile to use these autoassignroles, still the body field did not appear.
Most likely there is some other module which is causing the body field to appear, disable all other modules except cck, autonodetitle and autoassignrole and see how it goes. If it fixes the problem, you can find the culprit by elimination.
Comment #6
christowm commentedHi Nohup,
Thank you very much for all the hard digging. I really appreciate your efforts. I will go through and disable the other modules and see what happens. If I find the culprit I will post it here on the thread. Thanks again for your help.
Comment #7
christowm commentedHi nohup,
Ok, I figured out the problem. I was using the beta version of the Auto Assign Role module (6.x-2.0-beta1). Every time I turned that module off, the body field was no longer showing. As soon as I enabled the auto assign module, the body field started reappearing. So I deleted that module and downloaded the 1.2 version (6.x-1.2) of the auto assign module. After I installed that version, things started to work as advertised. I will dig some more and see if I can figure out why the beta version is ignoring the directive not to show the body field. Thanks again for your help.
Comment #8
guntherdevisch commentedHi christown,
I'm experiencing the same problem. I have installed Auto Assign Role 6.x.-2.0-beta1 for the use of 'Use on Auto Assign Role paths' but when i enable this with a cck field, all the form fields are shown even when the option 'Hide form fields' is enabled. When install Auto Assign Role 6.x-1.2, the extra form fields (not required) are gone. But i need the 6.x.-2.0-beta1 version because i have different roles and i need to display a cck field for only one role.
Does someone know what's causing the problem?
Thanks!
Gunther
Comment #9
mlalu commentedSame problem here.
Comment #10
hubris commentedI was having a similar issue (body field / body label would not go away) on 6.x-1.2.
I discovered this:
At first I thought I had only created 2 Profile Content Types (A & B), and I had gone through and done all the appropriate checkboxes and left the body field blank - But the Body field was still showing up.
I realized that I had actually created 3 profile Content Types. In this third profile content type (C), the checkbox "Use on Auto Assign Role paths: " was set to make it active for the paths of both of the other two profile types that I had created.
I'm guessing that Auto Assign Role will AND the different profile content types together into a single form on the page for that particular registration form if the types are all Check for that path. So what I was seeing was the Title & Body from Profile Type C and the Company, Phone, etc Fields from Profile Type A appear on the path/page that I believed was only for Profile Type A. And on the path for Profile Type B I was seeing Title & Body from Profile Type C and the Company, Phone, etc Fields from Profile Type B.
Deleting Profile Type C solved my problem - I'm sure just unchecking "Use on Auto Assign Role paths: " for Profile Type C would have worked too.
-Chris
Comment #11
koldtoft commented@ hubris
#10 solved my problem. I boxing this issue for 3h straight. So simple :) Thank you. Just deleted the 3rd profile content type (the default one) and it solved the problem.
Thank you very much
Comment #12
mike.davis commentedSeems this issue was more about configuration. Closing this now.