I downloaded the latest accidfree (4.7.0) module and filemanager (cvs as for Dec21) module. Installation went without a glitch. Filemanager private patch has been applied successfully. Acidree self check reported no problem:

Acidfree self-test checklist

   1. Filemanager module enabled
   2. Latest version of Filemanager module installed
   3. filemanager-private.patch applied
   4. Filemanager private path set and permissions OK
   5. Filemanager public path set and permissions OK
   6. Filemanager database table created
   7. Acidfree class definition files found for album, photo, video
   8. Drupal 'Temporary directory' path set and permissions OK
   9. Acidfree database tables created
  10. gd image toolkit installed and properly configured

No errors were detected. But this doesn't mean that Acidfree is guaranteed to work flawlessly.
It is a complex system and still under development. Please be patient while all the wrinkles are 
found and ironed out.
PHP configuration

    * Maximum file upload size is 16M (upload_max_filesize)
    * Maximum POST size is 11M (post_max_size)
    * Maximum execution time is 120 seconds (max_execution_time)
    * Maximum memory usage is (memory_limit)

My system paths and attributes are as follows: public_html/tmp (777), public_html/private (777), public_html/files (777)

But any time I try to upload a single image or use a mass upload I'm getting the same kind of error, like:
The selected file /tmp/phps3ChHn could not be uploaded, because the destination is not properly configured.

What's wrong here? Any sugessions?
Cheers!

Comments

vhmauery’s picture

vhmauery commented

can you upload files using the attachment module? If you can, this is probably an acidfree issue. If not, it is most likely a configuration error.

muchio’s picture

muchio commented

I uploaded some files using attachment mudule without any problems. But the only strange thing I've noticed is that they are accessible via mydomain.com/system/files?file=file.ext instead of mydomain.com/files?file=file.ext.
Does that supposed to work this way?

Sunain’s picture

Sunain commented

warning: shell_exec() has been disabled for security reasons in *** on line 1890.
Im getting this issue, anyone know how to fix this?

vhmauery’s picture

vhmauery commented

muchio:

The listing you are showing is output from the upload module, not the attachment module. See http://drupal.org/node/10245

Sunain:

shell_exec is used by the video class to create a thumbnail using mplayer. According to http://php.net/shell_exec this function is disabled in safe mode. So you either need to disable safe mode in your php.ini file or choose another video thumbnail option.

stmind’s picture

stmind commented

Just a "me too" post: I'm getting the same error when creating acidfree media: "Could not upload {foo}, the destination is not properly configured."

Drupal 4.7.0-b2, latest versions of acidfree and filemanager, patch applied to filemanager.module. I've checked the perms on the filemanager's files and private folders. It might be useful to note that a lockfile left over in the private directory, as well as an empty folder called "0". Clearing the lockfile does not change anything, the error reoccurs and the lockfile is left again.

Anything I can supply for troubleshooting?

TIA

stmind’s picture

stmind commented

The precise error is:

The selected file /var/tmp/php8nhU7f could not be uploaded, because the destination is not properly configured.

It's printed three times in succession before the preview of the new image object (sans any image).

hadishon’s picture

hadishon commented

I have the current cvs versions of drupal and acidfree (downloaded and installed today).

I uploaded about 50 images with no problem.

I then installed the module "node privacy byrole".

I then had the same error that those above were getting.

I disabled the module "node privacy byrole".

Acidfree worked great again.

The only problem is that I would like hide some nodes to certain roles... I'm open for suggestions.

vhmauery’s picture

vhmauery commented

hadishon:

your problem sounds like a configuration problem. If it worked before node_access modules were enabled, and works again after they are disabled, then you very well may configuration problems. Check to make sure that your filemanager private directory is a subdirectory of your drupal files directory.

Also, you might want to be sure that you have patched the filemanager. It will mostly work without patching, but the private stuff will silently fail unless patched. But if you are actually seeing error messages, it is probably misconfiguration.

metapunk’s picture

metapunk commented

What version of PHP are you running ?
I had the same problem with my server that was running 5.05 and I couldn't upload anything without getting similar errors, I couldn't even upload theme logos or anything so I think it's a big with upload.module
Check out http://drupal.org/node/42561 and http://drupal.org/node/42588

I installed the same thing on my PHP 4.4 server and I've been able to upload logos themes and images to acidfree.

muchio’s picture

muchio commented

Failed to upload on a local testserver (LAMP with php4.10) along with the actual hosting machine with php 4.4.1.

Damn, I start thinking I'll better use Gallery integration for media management if no working fix be available soon . :(

muchio’s picture

muchio commented

I've made some tests with various acidfree settings on/off and came to the solution, that if image streaming through drupal is set to off, all problems with image upload is gone. IMHO, the problem comes from filemanager module.

The next logical question - why not to use filehandling functions from filemanager module into aceidfree, so people stop complaining (like me) about acidfree not being able to handle images when actually it's a third party module's fault?

Cheers!

vhmauery’s picture

vhmauery commented

muchio:

I am not really clear what your last post means. Personally, I think that apache does a much better job at serving files than drupal ever could so I haven't messed with the 'image streaming through drupal setting'.

As for the filemanager, Acidfree does use the filemanager file handling functions. And if you like to have images streamed, you can do that with the filemanager as well. But it really doesn't matter as far as Acidfree is concerned.

Other people on this support request: does muchio's solution work for you?

peterjohnhartman’s picture

peterjohnhartman commented

Just a "me too" on the original problem and to report that muchio's Jan 12 solution of modifying the settings did NOT fix my problem.

peterjohnhartman’s picture

peterjohnhartman commented

I resolved my problem by removing a custom module which was altering the form via _form_alter. Bizarre, but it fixed the problem.

vhmauery’s picture

vhmauery commented
Status: Active » Closed (fixed)