I have tested the module on three different servers. What kind of differences may cause this problem:
I have two folders "test1" and "test2", test1 is empty, but in "test2" there are 50+ files.
I try to move the incoming files into test2 (which is not empty), but it moves just 1 file (or maybe more, but not all of them, it's absolutely randomized). On my server it works fine, and all of the incoming files moved to "test2", but on the others i ran into the problem mentioned above.
If the destination folder is empty (or subfolder, which has a not empty parent folder), there's no problem.

All of the servers use LINUX, APACHE, PHP5.2, json enabled.

Comments

artam’s picture

artam commented

Memory settings can cause this problem? The system administrator increased the memory_limit to 384M and the upload limit to 32M, but it still not working. What kind of settings need to modify on the server? I have no idea.

blainelang’s picture

blainelang commented
Assigned: Unassigned » blainelang

Will take a look and replicate your test as best I can. If the files were uploaded to the incoming queue then there are no server PHP related settings effecting the upload as the file is already uploaded to the server and it only needs to now be moved.

Only PHP server settings to be worried about are the ones any PHP application would need set if your uploading larger files such as post_max_size and max_execution_time

artam’s picture

artam commented

Files are pdf files (~2MB all of them). The post_max_size value is larger, and the max_execution_time value is longer on the "wrong" server.
Different Server API can cause problems?

blainelang’s picture

blainelang commented

I just tested 10 files and it moved them fine (local install running on Windows) but will update my Linux hosted test site and re-test.

I ran two tests of moving 10 files each time (uploaded via the desktop client) to new empty folders. The files were moved correctly - these were all small test files (.xls, .doc and .pdf) of less then 50kb each.

UPDATE: Tested moving a batch of 10 files (similar test files) on the UNIX hosted setup - no issues.

The files that are uploaded via the Desktop Client are saved in sites/default/files/filedepot/incoming with random php****.tmp file names. Clear out this directory before you do a test if you want to verify the files are being uploaded correctly. Once they are here, the module just needs to move them and update the database accordingly.

So to move forward, can you test with a batch of 10 files and report back. Test as well with smaller files to rule out any issues and confirm if the files are 1) making it to the incoming folder and 2) are they being moved to the secure folder.

Are you seeing any errors or just randomly not moving all the files -- it could be file specific so need to run more tests with different and smaller files for example.

Is the problem intermittent and is that why I don't see it?

artam’s picture

artam commented

Uploading files via the client working fine, files are saved in the incoming folder. Moving files to a new, empty folder also working fine.
The problem occurs when there are ~50 or more files in the secure folder, and I want to move incoming files to it.

I created an empty TEMP folder, I moved batch of ~40-50 incoming files to it correctly. After that I moved these files correctly to a folder wich contains more than 100 files. So the problem is probably somewhere in the moveIncomingFile() method when the destination folder contains files.

In the watchdog table there are these rows after moving incoming files:
for example.:
message: "FileField was trying to display the file %file, but it does not exist."
variables: "a:1:{s:5:"%file";s:48:"sites/default/files/filedepot/incoming/phpAFMIix";}"
location: "http://{site}/filedepot_ajax/movecheckedfiles

pbeakley’s picture

pbeakley commented

I got the same message when trying to move around about 100 files. I ended up just waiting -- the longer I waited the more files got from the "incoming" bin into the correct folder. Kind of weirdly slow for what I thought the process would involve.

ben_lynch’s picture

ben_lynch commented
Version: 6.x-1.0-rc3 » 6.x-1.2

We are having the same issue, running on Windows. The first file moved is successful, the others are not physically moved however the database updates as if they have.

Karin’s picture

Karin commented

I have a similar problem. Files are uploaded by the client correctly (my incoming files directory is outside web root), but when I try to move them only one file makes it. It doesn't matter whether the directory I move the files to is empty or not. The rest of the files is still sitting in the incoming files folder with the phpxxx names. Each time it seems only the last uploaded file is the one that works. Happens with pdf and doc files (havent tested anything else).

It's a big issue for me because I'm presenting filedepot as a document management solution to a client this afternoon and now I can't show him a proper functioning windows client which he may well have been willing to pay for.

Update: I seemed to be getting some mimetype exclusion errors after each move attempt when I reloaded the filedepot page. I have now set the mode to exclusion and removed all types so it includes all, and now it seems it's working normally. Not exactly the desired way to handle it but at least I can demo it to my client now. Hope to find a solution to this. I'm sure that the files aren't the problem, though I can do more extended testing later.

_timpatrick’s picture

_timpatrick commented
Status: Active » Closed (cannot reproduce)

Closing as no activity for a long time - you may reopen if you are still encountering this issue.