I am willing to presume that this has something to do with some other module I have installed, enabled, disabled or otherwise encountered (I say this because otherwise I imagine many more users would have encountered this!)
I have enabled the core 'Profile' and 'Taxonomy' modules and created a vocabulary and a few fields in the Profile section of User Management, then I have enabled Profile Taxonomy, but I don't get the new form field either when creating a new 'list selection' field or editing an already created 'selection' field.
I had previously installed the Content Profile module, but changed my mind about the way I wanted to do things and that module is now disabled (although the files are still on the server)
Any help pointing me in the right direction very much appreciated :)
Comments
Comment #1
ITMonkey CreditAttribution: ITMonkey commentedIn case anyone else does get this error, it's possible to get around the problem by simply creating a selection list field and then manually adding the field name and vocabulary id into the profile_taxonomy table kindly provided by the module.
The rest of the module seems to be working correctly, users can happily select from the assigned taxonomy category list when creating accounts and it stores the values correctly, I just can't see the settings in admin/users/profile when I add or edit.
Comment #2
gnindl CreditAttribution: gnindl commentedIt seems like the profile_taxonomy_form_profile_field_form_alter(&$form, $form_state) is not called. Disabling and enabling the 1.0-rc2 release of the module worked out for me.
Comment #4
gregoiresan CreditAttribution: gregoiresan commentedThe new form field "Selection options from vocabulary (advanced)" does not appear
I've tried : "Disabling and enabling the 1.0-rc3 release of the module "
Still, it doesn't work...
Any Idea ?
Comment #5
halmsx CreditAttribution: halmsx commentedhaving same problem. anyone?
Comment #6
giggler CreditAttribution: giggler commentedusing 6.x-1.x-dev and I don't see "Selection options from vocabulary (advanced)" either.
Comment #7
gregoiresan CreditAttribution: gregoiresan commentedI guess there is no solution and the module isn't working properly. I'm using User Terms which does the job.
Comment #8
gnindl CreditAttribution: gnindl commentedCurrent dev uses hook_form_alter instead of hook_form_FORM_ID_alter. The issue http://drupal.org/node/300481 deals with the problem that the first hook may be overriden by the second one, e. g. when using the module content profile
Comment #10
zet CreditAttribution: zet commentedSame problem here, after >1 year, with latest "stable" versions of both drupal and profile taxonomy module. Just the core User Profile. No Content Profile module enabled/disabled.
2 weeks with no activity does not mean is fixed.
I don't get the new form field either when creating a new 'list selection' field or editing an already created 'selection' field.
I think I'll try the User Terms module and switch to it if is proving to be better, as gregoiresan suggested.
Comment #11
zet CreditAttribution: zet commentedSo, after trying User Terms, I should say for the others that might have this issue, the problem with that module is that it sets a new fieldset above the others, that I don't want it, named "User Terms", that limits his purpose for some use cases.
ITMonkey, your aproach from #1 comment does not work for me. Maybe beacuse I use Profile checkboxes module(that stores serialized arrays), and I set the select list to Multiple Selections?
gnindl, have you tried weighting your module ?
Comment #12
zet CreditAttribution: zet commentedOk, so in my case, the problem seems to be dissapeared and the "Advanced selection options referencing taxonomy terms" appeared back after I disabled the Profile pictures module( that was enabled after Profile Taxonomy)
I did this after trying with setting Profile taxonomy's weight in the system table as a higher value with no result.
Profile taxonomy default weight was 0, same as Profile pictures.
It will be a very good thing for the moment to specify on the module description from the project page that it conflicts with Profile Pictures module.(don't know who's fault)
Just for the reference, this is Profile pictures implementation of hook_form_alter
and this is the implementation of hook_form_alter in Profile Taxonomy module
Comment #13
gnindl CreditAttribution: gnindl commented@zet: The bug was initially caused by a different problem. Now it's an incompatibility with profile pictures module. I advise therefore to continue in this thread. Thanks a lot: http://drupal.org/node/1245262#comment-4948094
Comment #14
chinita7 CreditAttribution: chinita7 commentedI had the same problem but updated it to 6.x-1.3 and it's already fixed.Thanks.