Okay.... I'm at my wits end here. I believe I updated this module from 2.15 to 2.16 back in November when the site gave me notice of it. Like a bonehead I didn't watch closely to see what was going on, not realizing what a major update this was. So now.... the product manuals and data sheets I was controlling via WebFM do not play right at all. if I got to the module settings page/node and make changes the changes don't take. I'm logged in as User 1..... I consistently see the error message of "Role Root Directory not set for Authenticated User role".
I've tried to set this.... but when I come back to the page the settings I entered are not there any long and I'm back to where I started. I'm thinking I need to try and take the module back to 2.15 but I don't know how many fields changed when I originally applied this update. I never remember having to tweak anything on .htaccess or settings.php to get this module to work correctly.... so as I said in the beginning... I'm just at a total loss here as to where to go to try and fix this issue. I'm running a 6.22 site..... Thanks for any help that can be offered.
Jeffrey
Comments
Comment #1
zap-admin CreditAttribution: zap-admin commentedI should also add.... I'm seeing this set of errors pop up when I do try to make changes in the settings....
Comment #2
zap-admin CreditAttribution: zap-admin commentedOkay... on the permissions page I check "Admin webFM" for Authenticated users and now they can download files again. This setting makes me very very nervous for obvious reasons. I unchecked "WebFM upload".... these are two settings i had checked for a secondary admin role on the site for use by our engineers.
Okay... I just shut this off.... checking this allows any authenticated user to have access to the settings page on this module. WAY BAD.
But how in the heck to I restore the ability for authenticated users to freaking download PDF data sheets and modules again? UGH.
Comment #4
zap-admin CreditAttribution: zap-admin commentedJe n'parle pas français
At least that's about as much as I remember.
Or via the help of a translator:
Je parle le français environ aussi bien que le poulet moyen.
(I speak french about as well as a chicken)
Comment #5
zap-admin CreditAttribution: zap-admin commentedOMG... I just used a translator..... Jerk is posting French Spam..... this is not what we need on this site.... how do we delete spam?
Comment #7
nhck CreditAttribution: nhck commentedzap-admin you haven't done anything wrong. I beliee its a duplicate of this bug: #1361200: Roles with permission "view webfm attachments" can view attached files, but no longer actually download them. I need someone to test the dev-release so we can push out a new version.
Comment #8
zap-admin CreditAttribution: zap-admin commentedif you want to email me at jharrison at chtech.com as to where I can download the module I'd be more than willing to install, test and report back as I obviously have no means of fixing this in it's present state. Thanks.... Jeffrey
Comment #9
nhck CreditAttribution: nhck commentedUhm, as mentioned in #1361200: Roles with permission "view webfm attachments" can view attached files, but no longer actually download them you can download the dev-release to test. It can be found here: https://drupal.org/node/821502
Comment #10
zap-admin CreditAttribution: zap-admin commentedThanks neck.... I did see that link.... and problem looks similar. Installing 2.16rc1 did fix the issue.... but I'll to and install the dev-release and give it a try. Thanks again.
Comment #11
t-readyroc CreditAttribution: t-readyroc commentedI just got the same behavior on both 2.18 and 2.x-dev. Visiting the permissions section by going to configuration > webfm > permissions gives the role root dir not set + group root dirs not set for each of my groups. Attempting to set these options results in the same errors being displayed along with the PHP settings upload size error reported by zap-admin above (exact same, 2097152 MB).
Environment:
The odd thing is that the directories specified are in fact created, in the tree where I specified. The actual server file system mirrors the setup that I specified. The user, however, sees nothing, but can still upload. The upload goes directly into the repository root.