FUnction lost due to upgrade
huayen - January 18, 2007 - 04:18
| Project: | CCK Field Permissions |
| Version: | 5.x-1.4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I upgraded from 5.x-1.2 to 5.x-1.3 smoothly, but all previous fields with permission set become public, even though I double-checked the permission set and access role permissions are still there for those fields.
WHy this happen?

#1
This is because the name of the permissions changed to better match the standard terminology that drupal uses. I will make a note about this in the release notes.
#2
Even though I did this, still the field with permission dows not hide for anonymous users.
#3
WHat I did are:
Step #1: Site configuration >> CCK field permission, to enable permission for a specific field of a content type.
Step #2: CHeck 'view the field with permission' for all roles of logged in, and uncheck for anonymous users.
Then, the field with permission will be hidden if the visitor is not in logged-in status. Am I right?
I did this ok in previous version, but always have problem in new version.
I am looking forward to solving this problem with your help.
#4
I guess your new module has bug, since I did a fresh install of drupal, still has same problem on the test site.
So, I guess your 5.x-1.3 does not work. I am still using 5.x-1.2 version.
Hope more people will test your latest module and give their result.
#5
I now understand the problem you're having. Please try the new 5.1.4 version which fixes this issue
#6
I've just downloaded and installed 5.x-1.4 and am having the same issues as huayen.
I set the permissions according to your instructions and even though I deny access to particular fields to anon users they can still view the fields.
#7
I apologise humbly. My error. 5.x-1.4 works. Confirmed.
this is a very usefule module. Thanks.
#8
Now 5.x-1.4 works perfectly for me. Thanks arthurf for your great modules and fast update.
#9
Great. I'll close this issue now.