Hi!

When I set the availability of a file to Internal or Public, anonymous users cant download the file. If I make DBFM available to anonymous user in the Access List configuration, then anonymous users can download any file, it seems, after a few quick tests.

If you want ACL support, then may I recommend a complete integration with Taxonomy ACL to make life easier?

When I upgraded from DBFM version 5.x-1.0-beta1 to 5.x-1.x-dev, DBFM kept showing a warning about missing "og" variables in the database; I installed the "Organic Groups" module, and the error didn't appear anymore. However, I find OG, even though I have spent only two hours with it, an incredible mess and unnecessarily complicated.

Correct me if I'm wrong, but perhaps integrating an ACL function with Taxonomy ACL in DBFM is easier than through OG?

The reason I would like to propose this, is because currently every File Manager using a flat file system don't protect the files themselves: an anonymous user could just enter the direct URI into the browser to gain access to the content. Through a database this problem could be solved, but only through ACL. And I think that Taxonomy ACL might prove to be a very interesting system, flexible yet simple enough to meet most people's demands.

Best regards

/Danai

Comments

rooey’s picture

rooey commented

Use the stable release - OG is supposed to be optional.

rooey’s picture

rooey commented
Assigned: Unassigned » rooey
cncoleman’s picture

cncoleman commented

I would like to second the request for taxonomy access control with DB file manager. Thank you.

rooey’s picture

rooey commented

Please provide some clear requirements of how you would expect this to work.

Danai-1’s picture

Danai-1 commented

When adding files to DBFM, you had to manually add files to the database (not sure if it still is the case; I suppose so).

You could add a part (below the description of the file) that shows a list of all the tags that are used in TAC. The user adds one or more tags, and DBFM would only allow the download if it is allowed by TAC.

Let me give you an example: suppose I have a vocabulary named "Public" (all, admins, members), and another one "Topic" (agenda, documentation, opinion, project). In TAC I grant access to everybody (authenticated, admins, others) WRT "all", "documentation" and "opinion".

I have a few files: some of them are for documentation, some belong to a non-public project. I just tag the file "documentation" or "project" and DBFM will grant access according to TAC rules. Same with tags from the "Public" vocabulary.

Or you might take another approach: just allow tags in general to the files. Then allow downloads only if TAC grants access, and if TAC is installed. Or make DBFM depend on TAC.

Best regards

/Danai

rooey’s picture

rooey commented

Err?

Not sure what you're talking about - try the 5.x.2.1 release - it's much prettier o.o

TAC?

Danai-1’s picture

Danai-1 commented

TAC stands for Taxonomy Access Control: http://drupal.org/project/taxonomy_access

Regards

rooey’s picture

rooey commented

Allrighty - that makes things a bit clearer.

It's unlikely at this stage that this will be added - as we've now met our requirements for ACL's. Right now the focus is on Replication, Search and Notification/Subscription.

Do take a look at 5.x.2.1 tho, we'd be interested to hear your thoughts.

rooey’s picture

rooey commented
Status: Active » Closed (works as designed)
geoff_eagles’s picture

geoff_eagles commented
Status: Closed (works as designed) » Closed (fixed)

Access control has been implemented using roles and organic groups. We will not be using TAC.