Flow.Launcher icon indicating copy to clipboard operation
Flow.Launcher copied to clipboard

BUG: Explorer Plugin Cannot Save Network Path Root to Quick Access Links

Open EnigmaSolved opened this issue 1 year ago • 8 comments

Checks

  • [X] I have checked that this issue has not already been reported.

  • [X] I am using the latest version of Flow Launcher.

Problem Description

When in the Explorer Plugin, and trying to add a directory to Quick Access Links (or also applies to "Index Search Excluded Paths"), if I browse to a local root drive directory (eg, F drive) I can add "F:", but if I try to add the root directory of a network path (eg, "\NAS_ROOT" I get the following error: You can't open this location using this program. Please try a different location.

It does work fine if the network drive is mapped to a drive letter, but I have need of being able to use the network path (and the error occurs both with HOSTNAME and IP Address).

To Reproduce

  1. Open Explorer Plugin
  2. Go to Quick Access Links (or Index Search Excluded Paths)
  3. Add
  4. Browse to a network path (eg, \NAS_ROOT)
  5. Select Folder
  6. Encounter error: You can't open this location using this program. Please try a different location.

Screenshots

2024-02-07 08_08_42-Start

Flow Launcher Version

1.17.1

Windows Build Number

10.0.19045.3930

Error Log

Log contains no errors anytime close to time period of above issue (ie, it does not appear to be logged in the log).


Replace this line with the important log contents.

EnigmaSolved avatar Feb 07 '24 16:02 EnigmaSolved

I have been able to successfully add my \NAS_ROOT path to the Settings.json file (a la "Path": "\\\\NAS_ROOT") and it does work correctly for then allowing me to call that path via Flow Launcher and launch it via Explorer. The only thing is that it does not get a proper icon: 2024-02-08 16_32_21-Start

Does anyone know where/how the icons originate that get displayed in Flow Launcher? In the near term I don't mind manually updating a reference of some kind so that proper icon shows up, but I am not sure where to look....

EnigmaSolved avatar Feb 08 '24 21:02 EnigmaSolved

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

github-actions[bot] avatar Apr 09 '24 01:04 github-actions[bot]

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

github-actions[bot] avatar Apr 17 '24 01:04 github-actions[bot]

Just bumping this to keep it open. Would still love to see this fixed eventually (including displaying a proper icon). :)

Edit: Looks like there's no way for me to reopen this?

EnigmaSolved avatar Apr 17 '24 10:04 EnigmaSolved

Clip_20240508_130441

I can see this icon of a share folder. Could you check your log again to see if if contains any info?

VictoriousRaptor avatar May 08 '24 05:05 VictoriousRaptor

Clip_20240508_130441

I can see this icon of a share folder. Could you check your log again to see if if contains any info?

Is that for \NAS_ROOT, though? I am able to add paths like \NAS_ROOT\SharedFolder and have the correct icon appear, but I get an error if I try to add \NAS_ROOT and so can only add it manually via the Settings file, and then I do not get the proper icon (which technically in Windows would not be a shared folder icon, but instead some kind of device icon). Does that clarify things? Thanks much for having a look into this (and for reopening it)!

EnigmaSolved avatar May 08 '24 10:05 EnigmaSolved

I can reproduce the issue by trying to add the network root path to Quick Access Links, but at a glance not sure where exactly is causing this error. I am guessing maybe it's the windows dialog window component we are using.

jjw24 avatar Jul 03 '24 11:07 jjw24

I can reproduce the issue by trying to add the network root path to Quick Access Links, but at a glance not sure where exactly is causing this error. I am guessing maybe it's the windows dialog window component we are using.

Thanks for checking and confirming!

EnigmaSolved avatar Jul 03 '24 14:07 EnigmaSolved