Hello,

Sorry for my bad English ;-)

I can run quick premissions. but also access file browser, I have not Action Failure
"You are not authorized to perform this action" what can that be? can you help me? thank you

Comments

r_honey’s picture

Looks like a module permission issue. Try the following 2 things in order:

1) Try logging in with User Id 1, and then access this module. If you are able to do so, then its surely a permission issue.
2) If you have verified that its a permission problem as in 1) above, or otherwise you do not have access to User Id 1 account, then ask your installation administrators to assign "access take control" and "access file browser" permissions to one of the roles that your user accounts belongs to. Please note that "access file browser" permission would be available separately under the "file browser" module in the permissions section.

fugazi’s picture

StatusFileSize
new23.97 KB
new13.95 KB
new39.17 KB

ohh as quickly as I had not viewed, fine!!

I have done everything, pictures for my bad english here are a few. in the file browser, the user 99 appears. Is that correct?

r_honey’s picture

Component: Miscellaneous » User interface
Status: Closed (fixed) » Active

I will answer the "User 99" comment later (I think I need to better explain that part in the module's Readme file).

However, from the screenshots, nothing obvious appears to nail down the issue. Its pretty difficult to comment on this from the outside.

Just another ideas, make sure the your PHP account has read/execute permissions on your Drupal root folder, and other such common symptoms. You can see a working copy of the module here:
http://drupal.sandbox.rahulsingla.com/admin/build/take_control

This is with the default settings. So, I don't see any reason for the module to fail if PHP account has sufficient permissions.
Your issue has led me to incorporate a debug mode for the module. For the next release, I would add a debug mode for more meaningful error messages to the module.

fugazi’s picture

have now tried everything. even a new site built and tested there again, unsuccessfully. I go once assume it to my host "HostEurope" lies the possibility he does not allow.

Nevertheless, many thanks for the quick help.

r_honey’s picture

Component: User interface » Miscellaneous
Status: Active » Closed (fixed)
fugazi’s picture

I still have to ask you something. what they mean by "PHP account has read/execute permissions on your Drupal root folder". Have now searched all night and still nothing
found.

Thank you very much.

r_honey’s picture

For other people who land on this issue page while googling, fugazi allowed me to remotely access his installation, and I figured out a minor difference in his Apache environment causing the module to give that permission problem.

I have fixed the code to adapt to it, and committed it to the CVS. The next version of the module (6.x-2.1 probably) would incorporate this fix.

marvita’s picture

Version: 6.x-2.0 » 6.x-2.x-dev
Component: User interface » Miscellaneous
Status: Active » Closed (fixed)

Hi r_honey,

I'm having the same problem regarding permissions. Would you mind to specify what did you change in the Apache environment to make fugazi's take control module to work without throwing that access message?

thank you!

r_honey’s picture

StatusFileSize
new790 bytes

Hi marvita, well it required a minor fix to the get-files.php script in the sites/all/modules/take_control/fb folder.

I have already committed the fix to the CVS, but no new version of the module has been released since the fix. So, I have attached the patch with this comment. Please apply it to the above mentioned file.

marvita’s picture

Version: 6.x-2.x-dev » 6.x-2.0
Component: Miscellaneous » Code
Assigned: Unassigned » marvita
Status: Closed (fixed) » Reviewed & tested by the community

Hi r_honey,

I try the patch and it worked!!! thanks very much for this you are awesome!!!

Marvita :)

r_honey’s picture

Assigned: marvita » Unassigned
Status: Reviewed & tested by the community » Fixed

Hi marvits, thanks for the feedback. Please note that on Drupal issue queues, assigning an issue to yourself means you are working on the solution to the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.