Closed (fixed)
Project:
Conditional Fields
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Feb 2009 at 15:04 UTC
Updated:
22 Jun 2011 at 12:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
kenorb commentedIt can be related to this one: #357506: Compatibility with CCK 3x multigroup
Comment #2
kenorb commentedBut probably not.
On node/add/type it's working, but when I'm going to form what was created via autoassignrole+content_profile it doesn't work.
Comment #3
kenorb commentedHere is the difference:
This one is working fine:
This one not:
There is no display and no 'conditional-field-processed' option.
Comment #4
kenorb commentedComment #5
designerbrent commentedI just run the latest dev release with autoassignrole and content_profile and it seems to work fine both on the creation form and the profile edit form.
Comment #6
kenorb commentedTested with dev on fresh installation, still doesn't work.
Needed module: content_profile (and submodule content_profile_registration).
How to reproduce the problem:
1. Create new content type with select list (filled with some choices) and two text fields.
2. Set some field condition between them via conditional_fields
3. Make this content type as Content Profile.
4. Go to Content Profile tab, and select Use On Registration.
5. Now try to register new user, Go to: /user/register on Anonymous
Conditional Fields are not working.
Comment #7
julianob commentedI hade the same issue. I identified the problem as an issue the allowed values in CCK fields. For some reasons, allowed_values and allowed_vales_php were empty, even that the fields had the proper functions to generate them. I solved the issue with a small snippet in the conditional_fields_allowed_values function on conditional_fields.module (patch attached). Don't know if the solution is elegant nor its impact on scalability, but it worked for me.
Comment #8
kenorb commentedThanks for a patch, but in my case conditional_fields_allowed_values() function is even not executed;/
So it not solved the problem.
Comment #9
kenorb commentedProbably this patch from: #357558: Conditional fields in colappsed fieldsets are not hidden on edit page load.
caused the problem
I've reverted changes from:
to:
And now it's working fine.
Comment #10
kenorb commentedComment #11
kenorb commentedComment #12
kaay commentedThanks, for some reason patch isn't working but changing a line of code as you have mentioned its working perfect.
Comment #13
kenorb commentedComment #14
peterpoe commentedThe simplest way is to modify line 80 of conditional_fields.js to this:
Note the new #user-register selector.
I added this patch to dev.
Comment #15
kenorb commentedThanks.
Comment #16
peterpoe commentedMarking as fixed.
In a future release, we should use a dynamic variable set in form_alter as selector, so the script is always sure where to look for the fields.
Comment #18
ss54 commentedI am having the same problem of conditional fields not working in anonymous mode. Is there any solution for this as yet
Comment #19
rot3r1i installed ver 2.0beta and 2.0Dev but it's seem that problem not solved for anonymous users..
Comment #20
pierremarcel commentedThere is another post with the same issue, they have a work around for it. I applied it to 6.x.2.0-beta2 and it's working.
http://drupal.org/node/959728