I am using Acidfree (current dev version) with core Upload 5.1. Although I set a max resolution 640x480 in "File uploads" setting, users are merrily uploading very large pictures. Apparently the max resolution constraint is not enforced. I guess this is not an Acidfree issue, still Acidfree users may be able to help. Few questions:

1) any one else experiencing this problem?
2) can I blindly resize the (original) images in the file system or is Acidfree keeping track of sizes in the db?
3) any way of enforcing the limitation before my disk fills up?

thank you.

Comments

vhmauery’s picture

vhmauery commented

The Upload module has nothing to do with Acidfree. Acidfree does use Image module, which uses the {files} table, which Upload uses as well. I am not sure how you are using the Upload module. If you are only using it for images, disable it. Image module has limits for file size or resolution as well, which you can enforce. And this does work (or did last time I was hit by it).

Acidfree's mass import may or may allow oversized images, but you can easily take that privilege away from untrusted users.

Sure, you can blindly resize the images if you want. The sizes are stored in the {files} table, but that data is not really required to be accurate. If you wanted to be correct in your resizing, you could update the table with the new size if you wanted.

skizzo’s picture

skizzo commented

thank you. I had Upload enabled as a pre-requisite for Flashvideo module. When I installed Acidfree I could not see any image until I enabled "view uploaded files" in Access Control for Upload module. So I thought that Upload was involved with Acidfree... Now, if it has nothing to do with Acidfree, why would it prevent viewing albums? I do not see any original-image resolution control in Image configuration (I would really like to be able to control both min and max res), so I settled for a max filesize of 350K.

vhmauery’s picture

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

Well, what you are asking now is really an Image module question. But I just found that if you go to image settings and add a new image size called '_original', give it a size that is greater than or equal to the preview size and add this one line to the image_links function, it works like a champ.

--- image.module.orig   2007-06-15 15:13:05.000000000 -0700
+++ image.module        2007-06-15 15:13:11.000000000 -0700
@@ -235,6 +235,7 @@
   if ($type == 'node' && $node->type == 'image' && !$main) {
     $request = ($_GET['size']) ? $_GET['size'] : 'preview';
     foreach (_image_get_sizes() as $size) {
+      if ($size['label'] == IMAGE_ORIGINAL) continue;
       if ($node->images[$request] != $node->images[$size['label']]) {
         $links['image_size_'. $size['label']] = array('title' => t($size['label']), 'href' => 'node/' . $node->nid, 'query' => 'size=' . urlencode($size['label']));
       }

Now why you have to use 'view uploaded files' access to view albums? Probably because the upload module will enforce file access to the files table or something (which Image module uses). It is because Upload module assumes that because the node uses the files table that it was created as an 'uploaded file'. This is a poor assumption.

skizzo’s picture

skizzo commented
Status: Closed (won't fix) » Closed (fixed)

Simple and effective. Thanks for this
workaround (will help many if added
to readme file). Closed.