Opening a remote file is blank

[SimCoxuK]

When opening a remote file from the FTP it shows the contents of this file to be completely blank, to view the contents of this file, I need to view it in local view and then edit from there, would be great if we could open the downloaded local file when trying to open a file from the server.

[grenierdev]

When opening a remote file, it should download it to local and then open the local file. Are you saying that it doesn't open it or that the local file is empty ?

[grenierdev]

not fixed

[SimCoxuK]

The local file isn't empty - when i browse to the downloaded local file and open it us - it works fine, but when i open the file from the remote connection - its blank - see attached screeen, pane on the left is from local, pane on the right is the same file but opened from the remote connection.

[SimCoxuK]

Is there anything i can do to help you replicate this issue? want me to create a video etc? Let me know as I'd love to see this package flourish as it's a great addition to atom

Brendan

[grenierdev]

Sorry I did not see that you had replied to the issue.

When downloading the file from remote, the package replace (or create) the local's content with the remote's. Then it call atom internal function to open file atom.workspace.open(...).

In your screenshot, can you verify that both file (panel) are leading to the same file? (you can do so by placing your cursor in each one and look at the status bar)

[SimCoxuK]

Hi just took the screenshots (see below) it looks like the remote accessed file's path has a '/' before it's location therefore not resolving to its local location - as with the local access file that has a full location.

[SimCoxuK]

Local file is on the right, remote on left, but yes they are both meant to be the same accesed file.

[grenierdev]

Can you update to v0.2.4 and try again?

[SimCoxuK]

Updated but still getting the same issue.

[SimCoxuK]

I might try repairing my disk permissions and see if that helps - although another colleague of mine in the office is using your package as well and is having the same issue. So i cant see it fixing (we are both running recent up to date installs of osx mavericks)

[grenierdev]

I'm gonna convince a colleague, who use OSX, to install Atom and the package so I can debug the problem. Will keep you posted.

[jerometan1]

Had this installed on Mac and Windows, Mac still have this problem but perfectly fine on Windows.

[jerometan1]

Hope this gets fixed... really like this plug-in very much

[grenierdev]

Could finaly test it out on a MAC. Seems like Atom open the file slightly before the download has finished. So a "blank" file is opened instead of the local computer.

[jerometan1]

Glad it will get fixed soon

[vincentducorps]

Same issue for me :)

OSX 10.10
Atom 0.139.0
Remote FTP 0.2.4

[jerometan1]

Still wishing this get fixed some day

[grenierdev]

Got busy for the past months, didn't get much time to work on this plugin. I started an other branch "rewrite" and will be testing out soon on a Mac.

[jerometan1]

Great! Looking forward to it

[grenierdev]

Fixed. Will commit the fix to the "rewrite" branch tonight (GMT -05). Will be releasing the official v0.3 in the next few days.

[lenguyenitc]

Hello mgrenier, This is really great package. Have you solve this problem. I'm using the latest version of package but still same issue?

[oscarhogervorst]

Old issue, but it can still occur. And I found a fix. It turns out that if you use the "remote" setting in your config file it's important to both start and end with a "/" character. In my case not doing this resulted in local creating a folder named "l" that did not match the remote structure.
Using this value worked
"remote": "/public_html/",