Open jerome-toole opened 7 years ago
Thank you for posting this issue. I had no idea and i have been trying to figure out what was wrong for days.
Good thing I searched for it before rolling up my sleeves and try to figure it out where I went wrong... Thanks for posting this!
Also wasted days trying to get things working till I found this. Really needs to be at the top of the Readme
+1
I guess I haven't made a new VVV subsite in a long time. I think I have updated to VVV 2.0 which is might be the cause of my issue #359
It does state in the VVV Wiki https://github.com/Varying-Vagrant-Vagrants/VVV/wiki/Auto-site-Setup that VV isn't currently compatible with VVV 2.0.
There is a work around for this issue that i found here: https://wpbeaches.com/setting-up-a-wordpress-vvv-vagrant-workflow/ "Provisioning with Variable VVV is not quite compatible with VVV2 but there is a workaround which makes it happen. Basically you need to add in the vvv-custom.yml file the name of the site before you use Variable VVV and format should be like so under sites:"
test: hosts:
It work for me at least
It would be great if there was a warning for new users on the front page that VV is not yet compatible with VVV 2. It took me a while to figure this out and should save a lot of time for others.