h3imdall / ftp-remote-edit

Edit files on ftp servers with Atom editor and without a workspace.
MIT License
178 stars 26 forks source link

Try to open ftp-remote-edit in Pulsar #449

Closed DarthDensus closed 1 year ago

DarthDensus commented 1 year ago

Expected behavoir: ftp-remote-edit should toggle an let me add server with sftp

Problem: ftp-remote-edit ends with an error after typing masterpassword

image

If i press of "View Issue" im landing on this case https://github.com/h3imdall/ftp-remote-edit/issues/44 but this is not resolving the issue.

Can someone pls fix the problem, since atom was sunsetting i cant run ftp-remote-edit and i love this package.

topa-LE commented 1 year ago

I also used the ftp-remote-edit package for many years. Since I also switched to Pulsar, I hoped it would work again. With Atom it didn't work anymore either.

Would be great if the developer could solve the above problem, think many want to use the package further.

Thanks for fixing the bug. img_151

nocturnalguru commented 1 year ago

Also receiving this error? Any update on this?

nocturnalguru commented 1 year ago

I tried to copy the files from ~/.atom to ~/.pulsar but got the same issue. got the same error. I then tried to set it up from scratch (setup a server) and got the following error

configArray is not defined

configArray is not defined Hide Stack Trace ReferenceError: configArray is not defined at Storage.load (storage.js:56:22) at ftp-remote-edit.js:488:23

topa-LE commented 1 year ago

There is no need to copy anything from ./atom to Pulsar. Reinstall Pulsar completely and install the ftp-remote-edit extension on this system.

Create a new server and you get the above error messages.

The problem was also like this in the last build of Atom, so you need to contact the developer of the package.

cschindl commented 1 year ago

I have made the adjustments, merged into the master and am now trying to release a new version. Unfortunately it is not as easy as it was under atom. (https://github.com/orgs/pulsar-edit/discussions/91)

I hope the problem can be fixed quickly, so that you can download/install the new version in Pulsar again without any problems.

cschindl commented 1 year ago

I was now able to successfully update the package on the pulsar package registry. The package can now be easily updated from within pulsar and should be fully functional from version v0.20.0.

topa-LE commented 1 year ago

Perfectly ;-) img_159

DarthDensus commented 1 year ago

@cschindl Thank you so much, nice work :)