Author Topic: Cloud Drives (Read 21390 times)

GrantSP · « **on:** October 13, 2013, 04:00:57 »

You have previously said the 1508 build of MC fixed the cloud drives not showing up however even with the last version I am only getting my SkyDrive to show up, both on the toolbar and the dropdown selection box on the explorer panel.

Google Drive, DropBox, Box Net and Amazon Cloud are all available on my Windows 7 explorer but don't show inside MC.

Mathias (Author) · « **Reply #1 on:** October 13, 2013, 12:21:04 »

Only Skydrive and Dropbox are shown.

GDrive is does not shown up because they do not provide a way get where the location is.
BoxNet and Amazon Cloud I do not support. Never heard of them.. But if anyway can tell me how to identify where the path to them is I can add them.

GrantSP · « **Reply #2 on:** October 14, 2013, 01:24:37 »

Ok. Fair enough about the cloud drives you have never heard about. It is not a big problem.

As for DropBox. Sorry but it is not showing up on my system.
The DropBox system tray icon functions normally and it opens a windows explorer as intended, but there is no icon or item in the dropdown menu within MC.

I'm not sure what info you would need to look into this.
If it is only an issue with my system, everyone else has this option available, then I am really not fussed with getting it working. I can easily go about my work without this.
So if it is more work than is needed just to bugfix this for one user, I understand.

Mathias (Author) · « **Reply #3 on:** October 14, 2013, 07:02:55 »

Dropbox work..

If you enable AppLog uner core settings and set loglevel to info
You will see in the log window what it goes wrong.

GrantSP · « **Reply #4 on:** October 14, 2013, 07:39:52 »

The log has this entry:
2013-10-14 16:36:38.668 Dropbox folder not found : "s" ( "C:\Users\Grant\Dropboxÿ" )

I have no idea where this is configured or when/how it was set.

Mathias (Author) · « **Reply #5 on:** October 14, 2013, 07:46:38 »

It gets some extra characters at the end. Maybe dropbox change there format of host.db

It comes from
C:\Users\<your account name>\AppData\Roaming\Dropbox\host.db

And the data in it is base64 decoded..

GrantSP · « **Reply #6 on:** October 14, 2013, 07:58:38 »

What information do you need from me? If anything.

Explorer has always been able to find my DropBox folder, why would there be difference with MC?

Mathias (Author) · « **Reply #7 on:** October 14, 2013, 08:06:01 »

Because explorer does not need to find it by it self. Dropbox register it self as a virtual folder for Explorer.
If you look in the host.db file you can decode it at http://www.base64decode.org/ and see what you get

GrantSP · « **Reply #8 on:** October 14, 2013, 08:12:41 »

The decoded hosts.db points to the correct location of "C:\Users\Grant\Dropbox"

Any idea where the extra "ÿ" comes from?

Mathias (Author) · « **Reply #9 on:** October 14, 2013, 08:34:32 »

That file might be corrupt or dropbox change maybe changed the format.

GrantSP · « **Reply #10 on:** October 14, 2013, 08:58:25 »

Which file?

The hosts.db is fine since it points to the correct place.
Where is it read in MC?

As with the other cloud drives, if there is no fix it really isn't a big deal for me.

Mathias (Author) · « **Reply #11 on:** October 14, 2013, 09:02:09 »

The hostd.db did not point to the correct place..

"C:\Users\Grant\Dropbox"
is not the same path as
"C:\Users\Grant\Dropbox"

Question is why that is some extra bytes at the ends. That is why MC can not find the path.

GrantSP · « **Reply #12 on:** October 14, 2013, 09:16:14 »

Hmm, this forum doesn't display the extra characters properly.

Looking at you last post shows those two lines as being the same. I was able to look more closely in my editor and the first line is the one with the extra character.
The second line without the extra character is the decoded Base64 line from the hosts.db and points to the correct place.
So how do I get MC to remove that from its settings and look for a new location?

If I manually go to the Dropbox in MC and copy to the clipboard the path it is the same as the hosts.db.

Where is the setting stored inside MC?

Mathias (Author) · « **Reply #13 on:** October 14, 2013, 09:31:48 »

Quote from: GrantSP on October 14, 2013, 09:16:14

Hmm, this forum doesn't display the extra characters properly.

Ok. But on the file path on disk do not have that extra character at the end ? I guess not.
So the path it gets from host.db with extra character at the end do not match the path on the disk.
So MC do not find the path.

Quote from: GrantSP on October 14, 2013, 09:16:14

So how do I get MC to remove that from its settings and look for a new location?

MC read the path from host.db, the path in host.db should not have extra characters in it

Quote from: GrantSP on October 14, 2013, 09:16:14

If I manually go to the Dropbox in MC and copy to the clipboard the path it is the same as the hosts.db.

Do not edit host.db manually. Maybe reinstall dropbox fixes the host.db
(What is the content of the host.db ? )

Quote from: GrantSP on October 14, 2013, 09:16:14

Where is the setting stored inside MC?

MC read the path from host.db it is not stored inside MC.

GrantSP · « **Reply #14 on:** October 15, 2013, 02:17:56 »

Ahh, I see what is going on here.

The decoded hosts.db gives me the same result for both the correct and incorrect data.

QzpcVXNlcnNcR3JhbnRcRHJvcGJveA== (incorrect)
QzpcVXNlcnNcR3JhbnRcRHJvcGJveA (correct)

Both these lines when pasted into Base64 Decode give me

C:\Users\Grant\Dropbox

So, yes, you are correct. The fault is with DropBox and not MC.
I should have realized this all along. Thank you.

I have submitted a bug report to DropBox.

Mathias (Author) · « **Reply #15 on:** October 15, 2013, 05:15:56 »

Well.. Im not sure that is incorrect..

GrantSP · « **Reply #16 on:** October 15, 2013, 05:59:37 »

Ok. that got me thinking. So I went the other way.

If I take the actual path and "encode" it, this is the result:

QzpcVXNlcnNcR3JhbnRcRHJvcGJveA==

Now if I take the path as decoded from the hosts.db and then encode it, this is the result:

QzpcVXNlcnNcR3JhbnRcRHJvcGJveA8=

Clearly they are not the same. As you say, there are extra bytes added somewhere/somehow.
Am the only user that has this problem with DropBox? Maybe no-one else uses it?

DropBox is not taking into account the special character. Unicode instead of ascii? Wrong, or missing, byte-order marker maybe?

I am going to update the report to DropBox at any rate as it appears to be a problem with them.

Mathias (Author) · « **Reply #17 on:** October 15, 2013, 07:12:35 »

I think it is very unlikely that DropBox is doing anything wrong.
The base64 text is correct. both of them..
And it is not an unicode issue then nothing would have worked.

Must be some decoding issue with the base64 decoding library I use. It is some third part code that I use, I have not written it my self. But it has not been change so strange that it worked before..

GrantSP · « **Reply #18 on:** October 15, 2013, 09:30:02 »

Very well, I trust your judgement.

I guess I must be the only one with a DropBox account!

Thank you.

Mathias (Author) · « **Reply #19 on:** October 15, 2013, 09:57:58 »

hehe no you are not..

But I looks like it is because of your name, the way the path is encoded (you name are in the path) make the decode mess up the last character and say that there are 1 character more then there is. So I think it is some decoder issue that only get trigger in some situations depending on the content it decodes.
So there is some problem with the decoder.

Mathias (Author) · « **Reply #20 on:** October 16, 2013, 06:56:35 »

I replaced the base64 library with anohter one so it should work in the next version

GrantSP · « **Reply #21 on:** October 16, 2013, 10:48:41 »

Ok, great to hear. Thanks.

Just out of curiosity I changed the settings to point to a number of different folders, just to see what would happen.

There were no special characters at the end of the paths on any of them but still it didn't show up.

Hopefully the new version will fix it. Although as I said earlier, it really isn't a big deal. Just nice to have it available.

Regardless, this is still the best filemanager around at the moment. Well done.

News:

Author Topic: Cloud Drives (Read 21390 times)