XYplorer Beta Club
Just to make sure I get this right: Your new tests were done with your old configuration?
Because:
- Fresh instance, full tree enabled
Typing the \\server\share into the address bar: It asks for username + password
Canceling this out
Switching to mini tree mode (toolbar button)
Typing the \\server\share into the address bar: It asks for username + password
So in a fresh instance there is no minitree issue. At least here...
network share credential not popping up in latest beta
Forum rules
When reporting a bug, please include the following information: your XYplorer version (e.g., v27.90.0047), your Windows version (e.g., Win 11), and your screen scaling percentage (e.g., 125%). We recommend adding your Windows version and screen scaling percentage to your profile or signature. This will make debugging much easier for us.
When reporting a bug, please include the following information: your XYplorer version (e.g., v27.90.0047), your Windows version (e.g., Win 11), and your screen scaling percentage (e.g., 125%). We recommend adding your Windows version and screen scaling percentage to your profile or signature. This will make debugging much easier for us.
Re: network share credential not popping up in latest beta
One of my scripts helped you out? Please donate via Paypal
-
VeeGee
Re: network share credential not popping up in latest beta
Yes, all new tests were done using my standard XY configuration. Once I confirmed that everything was working normally using a fresh install, I went back and focused on my configuration to see if I can narrow down a specific setting, etc. that would be causing the issue.
Fresh instance - no problems, everything works as expected.
My configuration (which has very little tweak-age done to it) - has the problem.
Later this afternoon, I could make a backup of my INI, remove it, allow XY to make a fresh one, apply my license and start adding back my settings (with a test in between each change). Maybe I'll be able to see if one particular one triggers the problem.
Fresh instance - no problems, everything works as expected.
My configuration (which has very little tweak-age done to it) - has the problem.
Later this afternoon, I could make a backup of my INI, remove it, allow XY to make a fresh one, apply my license and start adding back my settings (with a test in between each change). Maybe I'll be able to see if one particular one triggers the problem.