Closed (duplicate)
Project:
CCK Field Permissions
Version:
5.x-1.9
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 Sep 2007 at 18:39 UTC
Updated:
18 Feb 2008 at 23:18 UTC
I don't know what the policy is on setting module weight by default, but I was just struggling forever to figure out why cck_field_perms was working in my dev install but not in my production install. As it turns out, since everything had a module weight of 0, cck_field_perms was getting called before CCK was, ergo $node->content[$disallowed_field] didn't exist by the time it came to edit ['#access']; changing my module weight to 30 in the system table fixed it. Should the cck_field_perms.install file set the module weight as part of its script?
Comments
Comment #1
thepanz commentedHi, I got the same issue!
I setted cck_field_perms weight to 6 and it's working fine. Notice that cck_field_perms must be called BEFORE cck_fieldgroup (with weight 9), if not the form build and passed to cck_field_perms will contain cck_fields inside fieldsets that breaks cck_field_perms.
Regards
I created an cck_field_perms.istall file with all the necessary functions, but seems that this module is not mantained anymore :|
Comment #2
Vidarls commentedDuplicate with code: http://drupal.org/node/191836