Windows Issue: Must provide a path in /Users

[lkhedlund]

• Local Version: 3.0.1
• Windows Version: 10.0.17134 Build 17134
• WSL Installed: Yes

Related: #5

On Windows 10, when trying to use this as an add-on with Local 3.0.2, I get the error Sorry! You must provide a path in /Users. My local sites are all installed in C:\Users\name, etc.

Let me know if you need anything else to help resolve this.

[peekstudio]

Workaround: Remapping works without issue on the previous version of the volumes add-on. I rolled back to that for now.

[endurtech]

Sorry, new to Github. I submitted a pull request which resolves the issue. See it at: 4eada46

[etarhan]

I can confirm 4eada46 indeed solved the problem for me as well. Thanks! @endurtech

[oliver-graetz]

I have the same problem. Why isn't this released more than 7 weeks after the fix was submitted?

[oliver-graetz]

@peekstudio Where can i get a the previous version? The web site doesn't provide old versions, the program doesn't, and here on Github there are only source code ZIP archives.

[Dean-Wilson]

@oliver-graetz Apologies for late reply. Go to code -> branches -> tags. Then I think it is version 1.2.1. Direct link to that would be https://github.com/getflywheel/local-addon-volumes/tree/1.2.1. Download the ZIP and you can install add on from disk by using the button from add-ons -> installed or just unzip into the right folder which will be something like C:\Users\User\AppData\Roaming\Local by Flywheel\addons (but first uninstalling the current version if you still have that installed).

[slavetotheweb]

So I am mighty confused.
Firstly this is seems to remain an issue - not yet rolled into the release you get via Local.
Second - inside Local the addon is shown as v1.3.0 - but looking here on GitHub the latest is shown as v1.2.1
Third - even if this issue were fixed, why do I have to choose a folder within C:\Users ? I'm trying to mount the app folder from another drive (as the add-on description states as a potential use-case)

[oliver-graetz]

Version 1.3.0 is broken. It states that the path must be in "/Users", which cannot be satisfied on Windows (even "C:\Users" doesn't work). Version 1.2.1 works without problems. I don't know why this regression in 1.3.0 hasn't been addressed with a newer version after months.

[manzoorwanijk]

Version 1.3.0 is broken. It states that the path must be in "/Users", which cannot be satisfied on Windows (even "C:\Users" doesn't work). Version 1.2.1 works without problems. I don't know why this regression in 1.3.0 hasn't been addressed with a newer version after months.

I am also facing the same issue :(

[jameselks]

Still not fixed :_(

To revert to 1.2.1:

• Uninstall Volumes

• Close Local by Flywheel

• Download v1.2.1 ZIP file
  https://github.com/getflywheel/local-addon-volumes/archive/1.2.1.zip

• Go to Local by Flywheel folder (paste in File Explorer)
  %appdata%\Local by Flywheel\addons

• Extract ZIP file here

• Relaunch Local by Flywheel

• Go to Addons > Installed > and turn on Volumes

• Restart Local by Flywheel

You're good to go! Enjoy this ridiculous workaround.

[manzoorwanijk]

Still does not work. My Sites Path in NEW SITE DEFAULTS is set to D:\LocalSites but I can't REMAP VOLUMES :(

[oliver-graetz]

Did you install the old version?

[manzoorwanijk]

Did you install the old version?

Yes I did.

[oliver-graetz]

With the old version remapping in general works using Windows paths. But there is still a restriction regarding "Users" or "Volumes" as first segment of the path, and apparently it also need to be on the C: drive.

As a workaround you could create an NTFS junction or symlink from "D:\LocalSites" to "C:\Users\LocalSites". This way, you can enter a correctly formatted path into the Host Source field and still keep the actual data on your D: drive.

[manzoorwanijk]

As a workaround you could create an NTFS junction or symlink from "D:\LocalSites" to "C:\Users\LocalSites".

That's what I am trying to do now.