Closed (fixed)
Project:
Acidfree Albums
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Oct 2005 at 23:54 UTC
Updated:
8 Nov 2005 at 17:06 UTC
Hi, I like this module a lot, dumping other album modules cuz of it. And Im using the latest version. I have disabled the /administer nodes/ option for my authenticated user group. But 2 things happen:
1. there is no "acidfree media" menu item under "create content". actually only the first user of the whole database has that. no other user has that, no matter if it was granted full permission or not.
2. but the biggest problem is, even if i add "acidfree media" menu items manually, and click on it, it will give out "You are not authorized to view this page". and once i turn on /administer nodes/ for this user, i'll be able to create/browse acidfree media.
BTW, using drupal 4.6.3.
Comments
Comment #1
vhmauery commentedI cannot reproduce this problem. I have never allowed 'authenticated users' to have 'adminster nodes' access. Only user id 1 gets that role for my installations. You do need to check the 'acidfree mass import', 'create acidfree albums', 'create acidfree photos', 'create acidfree videos', 'edit own acidfree elements' checkboxes in the access control area for the users that you want to do those tasks. Other than that, access controls should be working just as designed. Let me know if that helps.
Since this is not really a bug, I am changing it to be a support request.
Comment #2
asansen commentedI'm having the same problem.
First, authenticated users couldn't post any media (mind: they could enter the 'add acidfree media' pages, because I gave them the correct permissions in access control). Well, they could post, but no picture was available and could not be found. And they got these error-messages:
1) warning: mkdir(/public_html/drupal/files/acidfree/tmp): Permission denied in /scoutnet.be/users/menapiers/public_html/drupal/modules/acidfree/acidfree.module on line 1537
2) warning: fopen(public_html/drupal/files/acidfree/tmp/dir.lock): failed to open stream: No such file or directory in public_html/drupal/modules/acidfree/acidfree.module on line 1507
3) warning: flock(): supplied argument is not a valid stream resource in public_html/drupal/modules/acidfree/acidfree.module on line 1508.
I found that this was because they could not select an album to post their photo's, and after a bit of fiddling I found that the dropdown for the album-selection only appeared when administer nodes/ was turned on for these users.
After that I installed the new update as of 22 octobre, but suddenly the 'post:>acidfree media' menuoption was only visible for me, the admin, and not for the other users (access control still setup as before). They could reach the 'add acidfree media' via other ways, but it doesn't show up in the navigation menu anymore.
When I look in administer/menus the option for acidfree media is set to visible (that's why the admin can see it). It's like that particular menu-item has been set to be invisible for anyone other than admin.
This is odd.
Comment #3
vhmauery commentedasansen, it sounds like you are having filesystem permissions problems. Please go to yoursite.dom/acidfree/test and check out what it tells you and follow the directions to fix problems.
As for the menu problems, can you try this: go to the admin/modules page and simply press 'Save'. This is the easiest way to flush the cached menus that I have seen.
As for users not being able to choose the parent album without having administer nodes rights, this should not be the case. Are you using a module that adds entries to the node_access table? I would imagine that if the user cannot view an album, he could not post an image into it...
Comment #4
xe commentedI thought maybe I did something wrong. So i actually created a brand new drupal under one of my subdomains, using a brand new mysql db. Using only the latest drupal, filemanager and acidfree. Enabled access to all acidfree components to all authenticated users in access control. Passed the acidfree test. But if I disable admin/access control/administer nodes/, no1 except the first user will be able to see or post acidfree contents.
All the other build in node types like book, story, poll and page do not have this kinda behaviour. So that leads me to blieve this is still a bug in acidfree.
Regards.
FYI:
MySQL Version 4.0.24-standard
PHP Version 4.3.11
Comment #5
asansen commentedI ran the test and the one error I got told me that 'the system directory isn't writable'. Hmmm. Does that mean my drupal-root-directory isn't writable or my modules/acidfree-dir? But can that possibly be the cause of the permission- and menu-problems I'm having?
I noticed another problem: Watchdog filled my 20Mb-limit database with 50Mb of data. Maybe that partly explains some of the trouble, although the menu-problem isn't solved. Installed poormanscron to watch over my database, or isn't that enough?
The module 'node_access_byrole' ins installed on my configuration of drupal, maybe that could be the one interfering? Simply disabling the module didn't solve it...
And the 'Save' flush-thing didn't work.
greetings
Comment #6
vhmauery commentedThe system directory set on the admin/settings page. It defaults to 'files' inside of the drupal root. If that directory is not writeable, Acidfree will not be able to create image/video nodes properly.
Node_access_byrole could certainly be interfering with the user permissions stuff. I can't even find it to download and test. Even after disabling the node_access_byrole module, you would have to reset the {node_access} table to it default (I think it is a grant all view entry -- see the drupal install databse for details). Make sure you back it up before you blow it away.
I am still not sure about the menu situation. I am half tempted to zip up my sandbox database and post it for you to test on your machine to see if it works for you.
Comment #7
mike stewart commentedasansen probably meant: http://drupal.org/project/node_privacy_byrole
Comment #8
vhmauery commentedI just made some changes to the permissions/menu stuff. It affects acidfree.module and all the class_*.inc files as well. So you can get them from the cvs repository or you can wait 12 hours to get the repackaged version from the modules page.
Note that after you do upgrade, you will likely have to reset the access control settings at admin/access. Disable them all for acidfree, save and then and reset the ones you want.
This should fix the menu problems AND the permissions problems. Let me know what you find out.
Comment #9
asansen commentedgreat, tomorrow I'll give it a try, no time now.
and: thanks for the help so far.
and yes, mdrmike, I was too lazy to look up the proper name, thanks.
*fingers crossed*
Comment #10
xe commentedthank u. i tried the latest code. this works!
although, is it by design that if "create album" is disabled for authenticated users, they wont be able to "create photos"?
thanx again!
Comment #11
xe commentedactually, i found out why that is the case.
"acidfree media" under "create content" is linked to creating acidfree albums(node/add/acidfree).
when "create acidfree album" is disallowed, u'll get an access denied msg. but if manully put in node/add/acidfree/photo, the create photos page would show up fine. a little usability bug.
Comment #12
vhmauery commentedI guess I should probably look into this usability problem. Thanks for pointing it out. When I fix it, I will point it out and close this bug.
Comment #13
inspiredbylife commentedWell, looks like the module is still not working correctly with 'node privacy byrole' module. The problem occurs when mass editing using the 'album contents' link. All the access control settings vanish once the page is submitted. Then I have to go and individually set the permissions. :(
Comment #14
vhmauery commentedinspiredbylife: I don't think you meant for your comment to be here -- this bug is not about that.
Xe: this is fixed in CVS 4.6 and HEAD. I am closing it.