XYplorer Beta Club

I found a bug that's been in XY for some time.

Normally, you can select a folder in the list pane and hit enter to enter that folder.


However, one of the PC's I use is diskless and boots from a network image.

I discovered that with current versions of XY, if I go to "Documents\", this doesn't work. Simply, nothing happens. XY doesn't freeze or anything, it just never enters the folder. I can select the target folder in the Tree, and then it will work fine, but I can't enter it from the List pane by hitting Enter.

But if I go to:
\\internal.server.com\username\Documents\

...then it works properly.


I did some troubleshooting and found exactly when this happened.

This bug was introduced in XYplorer v23.90.0100.


Works:
XYplorer v23.90.0000 and before.


Does NOT work:
XYplorer v23.90.0100 and all versions since.

... if I go to "Documents\", ...

Not sure what that means exactly. Could you provide a screenshot of the moment when ENTER does not work?

I apologize if I was unclear. What I meant was that if I go into the "Documents" folder off the root of the tree, then I can't enter any subfolder in the List pane by hitting enter.

But if I go to the full path for the same folder (i.e. \\internal.server.com\username\Documents\), then it works properly.

Works fine here.

Can anybody reproduce this?

Right-click the icon of Documents in the address bar and see what you get for Copy Real Path.

The real path is:
\\internal.server.com\username\Documents\

That's the one where XY is working properly.

And as I mentioned earlier, whatever change caused this bug was introduced in v23.90.0100.

Is Documents the only problem folder?

admin wrote: ↑08 Apr 2025 12:35 Is Documents the only problem folder?

I also saw the same behavior with the Desktop and Downloads folder.

OK, I have a vague theory. Try the next beta (v27.00.0105).

I tried v27.00.0300 earlier today, and the problem is still there, I'm afraid.

Too bad. Currently I don't see a solution.

Given that I identified that whatever change caused this bug was introduced in v23.90.0100, does that not make it relatively easy to identify?

The change log for that version is minimal and there couldn't have been that many changes that had the ability to affect something like this, I would imagine.

You're right, and I saw that too. Still I could not see the cause of it. I'll revisit it later.

I'm looking back at my original post and saw that I determined that XYplorer v23.90.0000 and before work fine and XYplorer v23.90.0100 and all versions since do not.

But going through the release list, there were a few releases between v23.90.0000 and v23.90.0100, so I'll try to see if I can get more specific with the target.

Great.

In the meantime I'll add some debug info to the next beta.