By kulvik on

Hi.

I'm completely stunned after trying to get the filemanager module working with acidfree (also tested with attachment module, with the same result).

I did this:
1. Installed filemanager, acidfree and attachment modules (setup database for every module).
2. Entered the correct settings for all the different modules.

When I try to upload a image (acidfree) I get the following error:

File copy failed: no directory configured, or it could not be accessed.
File copy failed: no directory configured, or it could not be accessed.
File copy failed: no directory configured, or it could not be accessed.
(yes, 3x times. only one time if using attachment module)

I figured that it had to be my paths in admin/settings/filemanager but all the paths are correct and the folders have the correct attributes (apache writable). Acidfree have actually created the working/0/ folder, but it cannot upload / save the actual images. I have tried both relative and absolute paths and have made sure that the public url is correct and working.

When I try to upload a image everything works, except that the image is not saved to disk. The image node is saved and working. Just the image missing.

The drupal log shows nothing except:
2005-11-18 22:35 acidfree: added Test

No error messages in the log.

I am using latest version of drupal (6.4.3) and the latest version of all the three modules.

I feel completely crippled and retarded on this one guys :P All suggestions are welcome!

- Thomas -

Comments

shouchen’s picture

shouchen commented

You should probably create an issue to make sure Acidfree's author sees that you have a problem.

EvilBill’s picture

EvilBill commented

I poked around for a while.

With Acidfree, it tries to make three copies of the image and when there is a problem, you see all three error messages. The error message is produced by file_copy in file.inc.

I'd expect something is not checking the return code and that is why Acidfree says it copied your image even when it did not.

The problem is when the "private" directory is outside of the "files" directory. The code in drupal 4.6.3 that checks to make sure someone is not making a funny path only allows things under your temp directory or your files directory (see file_check_location in file.inc).

The "fix" to this is to go into file manager and make your private directory a subdirectory of files, eg. enter "files/private". Note the warning about moving your private directory around.

This "bug" is only triggered when you select "Force all new images to be transferred by Drupal" in Acidfree.

Hope that helps.

kulvik’s picture

kulvik commented

Thanks for the reply Evilbill. This was interesting input, but unfortunately it didn't solve my problem. I tried to move the file paths inside the files/... folder without success. Is there any way to debug more detailed so I can actually find out what's happening?

:*(

- Thomas -

"If I do this, he might kick me back. That's not what I want. So I break his arm" - Bas Rutten

kulvik’s picture

kulvik commented

I finally found the problem.

I forgot that I was running a multi-site configuration on my drupal, so I can't use the folders under files/. I needed to use the .../drupal/www/sites/domain.com/public_files/ folder in filemanager to get it working.

Hope this can help someone else with a similar problem.

- Thomas -

"If I do this, he might kick me back. That's not what I want. So I break his arm" - Bas Rutten

remtheory’s picture

remtheory commented

Hey there! I'm new, so be gentle, please! :)

I've installed Acidfree and FileManager, and I'm getting the same error. I'm dealing with an ISP, and when I have just the 'private' folder under 'public_html', it wigs out. When I have the private folder under 'public_html/files', it seems happy, though I'm getting the same error that was reported here:
File copy failed: no directory configured, or it could not be accessed.
File copy failed: no directory configured, or it could not be accessed.
File copy failed: no directory configured, or it could not be accessed.

I don't know where else to put what, but the acidfree test is all good, so I'm at a loss. Everything is happily 777, too. Can anyone help pretty please?

Thanks so much!

kulvik’s picture

kulvik commented

Hi remtheory.

I'm not an expert either, but I would try pointing the filemanager module to the .../files directory that resides in your drupal/www/ folder.

Just set both public and private path to files/ and see what happens. I bet it'll work. That's what worked for me, except that my folders were organized a little different due to the fact that i'm running a multi-site installation of drupal.

good luck!

- Thomas -

"If I do this, he might kick me back. That's not what I want. So I break his arm" - Bas Rutten

remtheory’s picture

remtheory commented

OMG, thank you so much. I was really about to give up on drupal altogether. A media manager is critical to what we do.

Whew!

wahwah’s picture

wahwah commented

Hello

I was trying to do pretty much what everyone else here is doing: on drupal 4.6.x and have a problem smilar to remtheory above.

I tried various combinations for the "private" folder, such as

http://mysite.com/files
http://mysite.com/www/files
/www/files
/www/private

etc. etc.

In each case, I get a message saying :

the directory '/www/files' does not exist, or is not writable. although the premissions for the file are allowing everything to everyone

I have a single site running and wish to use acidfree on it.

thanks

Ninad

______________________________________________________
Learning Drupal, one node at a time

franc23’s picture

franc23 commented

wahwah, you need to put your private folder under your files folder. Set the base url in filemanager, this should normally point to the files directory. Then set the private file system path to files/private. This fixed it for me.

http://voice.livecricketgames.com

wahwah’s picture

wahwah commented

Thanks a lot franc32!

I now went ahead with acidfree, when acidfree.module is enabled, in the "Create new content" menu of Drupal, my theme is ruined so that the ontent creation box slides to the left, and I don't see the left navigation bar at all. This fixes itself when acidfree.module is disabled.

This is affecting my entire site and the whole theme sort of mutates in a way thats not really nice.

I use the Democratica Civicspace theme for Drupal 4.6.x

Any ideas how to fix this?

regards

ninad

______________________________________________________
Learning Drupal, one node at a time

wahwah’s picture

wahwah commented

Thanks a lot franc32!

I now went ahead with acidfree, when acidfree.module is enabled, in the "Create new content" menu of Drupal, my theme is ruined so that the ontent creation box slides to the left, and I don't see the left navigation bar at all. This fixes itself when acidfree.module is disabled.

This is affecting my entire site and the whole theme sort of mutates in a way thats not really nice.

I use the Democratica Civicspace theme for Drupal 4.6.x

Any ideas how to fix this?

regards

ninad

______________________________________________________
Learning Drupal, one node at a time

franc23’s picture

franc23 commented

Most themes that do not come with drupal core may cause such issues, you could try playing with the style.css file of the theme to fix this. Or maybe go in for some other photo management tool, but sooner than later, you will have to fix the style.css to suit your needs.
If you are not sure on how to change your css file, create a topic in the appropriate category and post your css code and a link to the issue of concern. Hopefully, someone would be able to assist you.

Dilip

http://www.dilipfrancis.com/

crispin’s picture

crispin commented

..is what it says in the Private file system path:

I was having the same issue when setting up filemanager.

If you put the private file under your files folder it will be accessible from http://www.yoursite/files/private. I created a new folder at the top of the file structure on my site (as in above the public_html or www folders) and set the read/write prmissions - ctrl click or right click > set permissions to read/write/execute for all. Then i set the private file system path relative to the instalation of drupal ../private.

This fixed it while keeping the folder inaccessible from a web browser.

NB - also in the help for Private file system path:

Changing this location after the site has been in use will cause problems so only change this setting on an existing site if you know what you are doing.

...so be warned that changing it now might result in a royal balls up.