Permissions and default view
gomjabbaar - April 13, 2008 - 14:27
| Project: | Fotonotes |
| Version: | 6.x-1.1-beta1 |
| Component: | User interface |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
First im quite new to Drupal so bear with me if i missed something obvious.
Here are my questions:
- when i try to access http://www.drupal.localhost/node/xxx/fotonotes while logged as anything but admin, i get a "permission denied" message. For testing purpose i allowed everyone on all the fotonotes access control options, but to no avail.
- second, id like to make fotonotes the default view for my gallery images (ie without the "edit fotonotes" tab). Is that possible? i saw Romka did it on his homepage (http://fotonotes-en.romka.eu/)
Tx in advance for the help :)
#1
та ж проблема)
#2
The permissions don't seem to work for anybody but user 1. The "edit all fotonotes" and "edit own fotonotes" permissions are also unused.
#3
Same here. The permissions don't work for users except user 1 or admin,
even when access permissions have been set correctly.
Any work around / quick fix please ?
#4
I have also noticed that the edit own fotonotes permission is ignored.
#5
Using a later version (since a lot of time has passed since the original req!) and answering the second part of the original post:
I use a View that combines my Image content type with some other data, and this is the preprocessor to show the non-edit mode/tab:
<?phpfunction themename_preprocess_views_view_fields__viewname(&$variables) {
if (isset($variables['fields']['type']) && $variables['fields']['type']->raw == 'image') {
if($node = node_load($variables['fields']['nid']->raw)) {
$variables['fields']['body']->content = view_fotonotes($node);
}
}
}
?>
Note that the image body content is set to 'view_fotonotes($node)' given a few conditions. Not the neatest thing in the world, but fairly elegant considering the module provides this method but no UI for it. You could probably do something similar in preprocessing the node in question... or contrib a more flexible "show XXX tab by default" feature to the module.