Be able to skip first connection setup

[daviddesmet]

I just installed Mingo v2, and I can't get past the setup screen because it is forcing me to create the first connection while I already have several ones in Mingo v1.

It would be nice to be able to skip that.

[tothradoslav]

V2 should have migrated your settings from v1 and should have not asked for setting up the first connection. If this is the case, there must have been a problem migrating the data. We will investigate.

[jjimenezFinsus]

@tothradoslav I just migrated to v2 and my settings from v1 have been lost.

[ericneubauerbumphealth]

I'm also having this same issue. Trying v2 and none of my data from v1 was migrated.

[tothradoslav]

I have managed to solve this issue, but i'm afraid your previous state is not accessible since you opened the new mingo with this bug. If you have previously exported your mingo state, you should be able to import it. (File -> Export Mingo State).

I'm really sorry about this :(

[ericneubauerbumphealth]

Exporting and importing appears to have worked for me in RC3. I had to re-enter connection passwords, but that's no trouble. Thanks!

[mattivilola]

Is it possible to import/export also passwords? I have tens of connections and it would be very time consuming to fetch all of them to gain access again.. I am actually preventing my upgrade as of now due to this? And yes, I know exporting passwords is not good practice but doing it locally yes, I know the consequences/take the risk.

[tothradoslav]

Well, since you are using the old version of Mingo, which does not have an "export passwords" function, there's no way for you to export them. The new version uses a completely different way to store the passwords (we had to make this change and we are sorry for the loss), thus there's no way to export / import them.

I was thinking of releasing a patch for the old 1.x version of Mingo, that would be able to export the passwords, too, but users would HAVE TO install this patch before moving on to v2.x. Otherwise, v2 rewrites these with the new approach.

It is possible to access the passwords in your OS (keychain), but it's quite complicated.

Since Mingo is now using a standard way to store the passwords, migrating to v2 is a one-time thing, maybe not worth the hassle.

Sorry about this :(

[mattivilola]

Thanks for the response. The pop-up dialog to update to v2.0.2 is still reminding me and same time annoying me on daily basis. It is just too much of work for me to upgrade now and start fetching/collecting the passwords as I am too busy building stuff..

Is there any way to install both Mingo versions same time and to just start gradually adding new stuff to v2 but keep v1.x with me for production critical debugging with current onchain passwords..?

So yes, I still upvote for the patch to v1.x as it would be super :)

[mattivilola]

So can I assume that this task was closed and Available in... label was removed so there won't be any help on this topic.

Not possible to export full data with passwords with old Mingo v1.x version?
Not possible to run new Mingo version in parallel in Mac OS X as new app (to make transition smoother)?

== Not possible to upgrade to new Mingo until I find time to collect all credentials of my numerious client projects. So basically like starting to use a completely new tool (except if it is new tool, I can do this in parallel and keep old Mingo running). Very sad :(