could not move to library
 

I tried to download a few files and it comes up as 100% completed, but for the Status, it shows "Could not move to library".

What does that mean?

Thanks

I get this message as well, but only for a very few files that I've tried to download.

I just assume it's from people who have files to share, but don't have any upload slots opened. (They have set the number to zero)

I don't really know, but I don't think it's because of the default folder.

I get this all the time too and I'm sure it knows where my save folder is, I'm not sure why it does it either.

This has happened to me a few times, and every time the attempted download has been a file which happened to have a forward slash (/) in its name, as in a directory. The download reaches 100% immediately, in other words without downloading anything at all, and then fails with the "could not move to library" message.

Well, what I should've mentioned is that I'm on Linux, which is why my directories have forward slashes in them (not backslashes). Now that I think about it, that's probably the problem right there: Linux users can create files with backslashes (\) in the name, which will cause problems for Windows users. And Windows users can create files with forward slashes (/) in the name, which will cause problems for Linux users.

I'm not sure about the Windows part though; could some Windows user please check if you can create a file with a forward slash (/) in the name? If not, maybe the problem is caused by Mac users, or maybe something else entirely.

I tried using foreward slashes in windows and its a no-go. I guess us windows users just cant download files with any slashes. Any other ideas?

Very good eyes whoever spotted the slash thing by-the-way!

has anyone reported this as a bug yet?

Same issue here
 

I am having the same problem...I tried to download winrar files and it did it to me...which blew the entire hope of downloading what I was trying to download...this must be a bug...its only done this once on me though

Hmm...

a possible reason is that the file is in use! Did you lunch the file whil d/l?

Only an idea!

Morgwen

This path separator issues are one of the classic problem areas for maintaining cross-platform compatibility. We are very careful about this in our code (we never hard code forward or backward slashes, for example, but always use the pre-defined values for them on the specific platform).

We have not fully considered the possibility brought up here, though, and we'll look into it further. It does not appear to be an endemic problem, but there may very well be some lingering issues. I've entered it into our database of outstanding problems.

Thanks guys!!