[Bug] Folder unaccessable under connections list

[expired user #4720]'s profile image [expired user #4720] posted 12 years ago in Creating a connection Permalink
After I created folder to grouping several connections, it content has been unavailable on next application start. Heidy displays this folder as normal connection, but not as folder. And now I cannot access to several real DB connections which stored in this folder.
ansgar's profile image ansgar posted 12 years ago Permalink
Did you downgrade your HeidiSQL.exe to an earlier build? Or probably you have two different build revisions in use?
[expired user #4720]'s profile image [expired user #4720] posted 12 years ago Permalink
I'm using single Heidy build, which upgrades with replacement of .exe
First it was 4168 Heidy's build and there were no folders.
Than I upgraded Heidy up to 4172 and created 1 folder and dropped several existing connections to it.
After this, I checked new Heidy version and installed build 4174. When Heidy started, I saw that folder looks as connection. I downgrade Heidy down to 4172, but nothing happened.
ansgar's profile image ansgar posted 12 years ago Permalink
I'm sorry, this seems to be a bug in r4172. Please upgrade as soon as you find a newer build via updatecheck.

In the meantime, do the following:
- Exit all heidisql.exe instances
- Start regedit.exe
- Navigate to HKEY_CURRENT_USER\Software\HeidiSQL\Servers\[Your new folder]\
- Verify that there is a numeric value called "Folder" with a "1" in that folder. If not, create it via righclick > New > DWord, 32 Bit.
- start HeidiSQL and watch out for the folders in the session dialog
[expired user #4720]'s profile image [expired user #4720] posted 12 years ago Permalink
Yeah! I have restored folder via registry edit. Thank you very much!
ansgar's profile image ansgar posted 12 years ago Permalink
Nice, glad to hear that.

The question remains if there is a bug at all, or if that happened due to a downgrade to some pre-4172 build.
[expired user #6512]'s profile image [expired user #6512] posted 12 years ago Permalink
I've several folders and I could connect perfectly to my servers.

But after upgrading to r4174 I can't use the quick connect any more.
Before when I pressed the arrow I got:
Folder1\Server1
Folder1\Server2
Folder2\Server3
...

But now I'm getting:
Folder1
Folder2

The session manager still displays the folders and underlying servers correctly.
The Folder setting is set to 1 in Windows Registry.
[expired user #6512]'s profile image [expired user #6512] posted 12 years ago Permalink
Note that I was using r4170 befor the upgrade. Reading the changelog I guess it happend in r4171
ansgar's profile image ansgar posted 12 years ago Permalink
Confirmed... Will check that this evening. And yes, my guess is also r4171.
Code modification/commit from ansgar.becker, 12 years ago, revision 7.0.0.4175
TAppSettings.ValueExists respects SessionPath, which is not used in GetSessionNames, so prefer FRegistry.ValueExists here. See http://www.heidisql.com/forum.php?t=11020
ansgar's profile image ansgar posted 12 years ago Permalink
Fixed in r4175 . Please update immediately, as this was causing folders to be turned into sessions, so you could not access sub folders or sessions within that folder any longer.
[expired user #5221]'s profile image [expired user #5221] posted 12 years ago Permalink
Hello, I'm using portable version V.7.0.0.4208 and I had the same problem.

Adding the "Folder" key to the registry entry fixed the issue, however creating new folders still displays them as sessions.
[expired user #5221]'s profile image [expired user #5221] posted 12 years ago Permalink
Hello, I'm using portable version V.7.0.0.4208 and I had the same problem.

Adding the "Folder" key to the registry entry fixed the issue, however creating new folders still displays them as sessions until I manually edit them with regedit.
[expired user #5221]'s profile image [expired user #5221] posted 12 years ago Permalink
Whoops sorry for double posting, I just refreshed the window >_>
[expired user #6740]'s profile image [expired user #6740] posted 11 years ago Permalink
The question remains if there is a bug at all, or if that happened due to a downgrade to some pre-4172 build.

Please login to leave a reply, or register at first.