Access restricted to missing content types
pebosi - October 13, 2008 - 15:17
| Project: | View own |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Description
Hi,
i your access list you only show content type by module "node", but for all other types like "forum" or "webform" access is restricted by default too, and there is no option to get access back...
regards pebosi

#1
hi!
first of all, you can uninstall module, rebuild your permissions and all will be ok with your rights. There are no access management module, which influence can't be undone.
second
do you check "access content" permission?
can you provide screenshot with permissions for forum module and node module?
#2
Djuba,
I noticed in view_own.module, line 33, that permissions are only set for modules of type 'node'. This restriction keeps other modules, like webform and blog, from being displayed. By removing the restriction the module will work for all content types.
Unfortunately, I don't know how to make a patch, so I'll just show the changes I made here:
Original code:
function view_own_perm() {foreach (node_get_types() as $type) {
if ($type->module == 'node') {
$perms[] = 'view own '. $type->type .' content';
$perms[] = 'view any '. $type->type .' content';
}
}
return $perms;
}
Updated code:
function view_own_perm() {foreach (node_get_types() as $type) {
$perms[] = 'view own '. $type->type .' content';
$perms[] = 'view any '. $type->type .' content';
}
return $perms;
}
If there's a good reason to restrict this access to types of module "node" please let me know. Otherwise, please update the module so it will work with all content types.
Chuck
#3
I agree with #2. I don't understand why this module can't be used with nodes created by blog.module, image.module or others.
#4
Created a patch for that, only removes the if statement
regards
#5
Subscribing
Hope this gets implemented soon:)
#6
Committed.
#7
Automatically closed -- issue fixed for 2 weeks with no activity.
#8
Thank you(!) for fixing this. I just ran into the same bug.
I just have two questions:
1. The fix was committed on: May 27, 2009.
Therefore, it looked like the development snap shot: 6.x-1.x-dev 2009-May-30, has this committed fix. Correct?
2. The current released version is: 6.x-1.1 2008-Sep-04.
Do you know when the nest released version will be?
Thank you in advance.