Local Community

Open Site Shell drops me into the wrong Windows folder

Hi,
Just installed v5.2.3 on a Windows 10 box. My local sites are configured to be housed on my D drive. C is the system drive.

After building site, all files are properly created in D:\local_sites_v5\newv5site. Site loads properly and admin is available.

Open Site Shell command drops me into C:\Users\Matt which is not the WordPress install. Any CLI commands offer me the dreaded:

C:\Users\Matt>wp plugin list
Error: This does not seem to be a WordPress installation.
Pass --path=path/to/wordpress or run wp core download.

I can switch to my D drive by entering the command d:

C:\Users\Matt>d:
D:\local_sites_v5\newv5site\app\public>

…and now I am in the WP intall and CLI works.

It would be REAL nice if I didn’t have to change drives when dropped into the shell. v3 handled this correctly.

Thanks,
Matt

1 Like

This happens to me as well, would be awesome if they can fix it.

Issue for me as well, running Local 5.5.3 on Windows 10 Pro.

I have my sites installed on drive D: (as well as Local itself), and Open Site Shell simply opens up the current user folder on C: i.e. C:\users\username.
Simply switching to D: makes it jump straight to the correct site folder and wp-cli works as intended.

A fairly minor issue for now, since simply D: + Enter takes you to the right place. Of course a fix would still be nice.

1 Like