Hi,

For a project I'm working on I need to create some sort of image tank to which only certain roles have access.
Because files can be fairly large I was thinking of going the FTP route for upload at least, but possible aslo download.

Not sure exactly how to accomplish this but I was thinking I could FTP a load of files to a certain FTP account.
Then a module would create nodes out of the files stored on the FTP account. The nodes could ossibly later be edited to add descriptions.
Also the nodes could be protected from users that should not have access to the files via some sort of node access module.

Can this module help me in achieving this? Or am I going about this the wrong way?

Cheers,
Bartezz

Comments

jbrown’s picture

jbrown commented
Version: 6.x-4.x-dev » 6.x-1.x-dev
bartezz’s picture

bartezz commented

Thanx for changing the version... a small reply would have been nice tho!

Cheers

fox_01’s picture

fox_01 commented
Issue summary: View changes

What was your solution?

perignon’s picture

perignon commented
Status: Active » Closed (won't fix)

Permissions are handled via other methods (access to nodes is the easiest). Since Storage API creates a field, handling permissions is a piece of cake.

In addressing large file uploads. The only real way to do this is to go through the process of creating the fields with Storage API, then uploading small files through the UI - this creates the entries in the database. Then going in an manually uploading the large/huge files to the storage area.

I personally had this very problem with S3 storage because there is a strict 2GB limit to uploads unless you use the Multi-Part implementation of the API which is far too complicated to implement in Storage API. So I uploaded files via the UI to create all my database entries. Once that was done I used an S3 client that supported the multi-part upload that I needed and replaced the files uploaded from Drupal with the real files. Then I corrected the file size of the field object manually.

Yeah this is not an easy way to do it. Updating the file size requires advanced Drupal knowledge to update the field data via SQL (but for the user they don't see these file sizes so it may not be important).

Large files can never be supported via the Storage API because file uploads are limited by the server, not by Drupal. php_upload and php_post_size dictate what you can upload via the UI.

We could write some in-depth documentation to cover this, but that would be the only solution.