<commit_before>---
layout: page
title: Changelog
permalink: /docs/en-US/changelog/
---

## 3.2.0 ( 2019 )

### Enhancements

 - Improved output of `xdebug_on` and `xdebug_off`
 - Updated the default config to reference PHP 7.4 support
 - webgrind is now provisioned using composer
 - Added support for the vagrant-disksize plugin if available

### Bug Fixes

 - Fixed cloning site provisioners into empty directories
 - Enabled MailHog for all PHP versions
 - Removed trailing spaces from all provisioner files and configs
 - `my.cnf` is now readable by the vagrant user
 - Fixes to newline substitution in the splash screen and some rearrangement
 - MySQL binary logging is now disabled
 - Synced folder permission fixes for VMWare

## 3.1.1 ( 2019 August 6th )

This is a quick update that changes a default parameter when undefined. In VVV 2 the database was stored inside the VM, and in VVV 3 we put it in a shared folder. This didn't work for some people, so we added a config option to disable this. If this option wasn't set, VVV would use the shared folder.

In v3.1.1 if the option isn't set, it will instead store the database inside the VM. This makes it work out of the box for everybody. If you have a working VVV with the shared folder, you can restore this behaviour by setting `db_share_type: true` in `vvv-custom.yml` and reprovisioning, see `vvv-config.yml` for an example of where this setting goes

### Enhancements

 - Improved the default `vvv-config.yml` to show new site template parameters
 = VVV installs less out of the box with a simplified `vvv-config.yml`, uncomment utilities to add software back in

### Bug Fixes

 - Fixes the grunt installation
 - Fixes to file permissions in the `/vagrant` folder
 - Removed typos in the readme
 - Switched to a new box for VMWare
 - Shared folder warning fixes for VMWare
 - Trailing whitespace removed from the editorconfig file
 - Visiting the dashboard before it's provisioned now no longer gives a PHP error

## 3.1.0 ( 2019 July 4th )

This is primarily a reliability update. Note that updating to v3.1 requires a `vagrant destroy` and a `vagrant up --provision`. If you've turned off shared database folders, backup beforehand.

### Enhancements<commit_msg>documented the vmware and parallels fixes in the changelog<commit_after>---
layout: page
title: Changelog
permalink: /docs/en-US/changelog/
---

## 3.2.0 ( 2019 )

### Enhancements

 - Improved output of `xdebug_on` and `xdebug_off`
 - Updated the default config to reference PHP 7.4 support
 - webgrind is now provisioned using composer
 - Added support for the vagrant-disksize plugin if available

### Bug Fixes

 - Fixed cloning site provisioners into empty directories
 - Enabled MailHog for all PHP versions
 - Removed trailing spaces from all provisioner files and configs
 - `my.cnf` is now readable by the vagrant user
 - Fixes to newline substitution in the splash screen and some rearrangement
 - MySQL binary logging is now disabled
 - Synced folder permission fixes for VMWare
 - Shared DB mounts are now mounted on Parallels and VMWare
 - Fixed `/var/log` being mounted on Parallels and VMWare

## 3.1.1 ( 2019 August 6th )

This is a quick update that changes a default parameter when undefined. In VVV 2 the database was stored inside the VM, and in VVV 3 we put it in a shared folder. This didn't work for some people, so we added a config option to disable this. If this option wasn't set, VVV would use the shared folder.

In v3.1.1 if the option isn't set, it will instead store the database inside the VM. This makes it work out of the box for everybody. If you have a working VVV with the shared folder, you can restore this behaviour by setting `db_share_type: true` in `vvv-custom.yml` and reprovisioning, see `vvv-config.yml` for an example of where this setting goes

### Enhancements

 - Improved the default `vvv-config.yml` to show new site template parameters
 = VVV installs less out of the box with a simplified `vvv-config.yml`, uncomment utilities to add software back in

### Bug Fixes

 - Fixes the grunt installation
 - Fixes to file permissions in the `/vagrant` folder
 - Removed typos in the readme
 - Switched to a new box for VMWare
 - Shared folder warning fixes for VMWare
 - Trailing whitespace removed from the editorconfig file
 - Visiting the dashboard before it's provisioned now no longer gives a PHP error

## 3.1.0 ( 2019 July 4th )

This is primarily a reliability update. Note that updating to v3.1 requires a `vagrant destroy` and a `vagrant up --provision`. If you've turned off shared database folders, backup beforehand.

### Enhancements
{'fraction_non_alphanumeric': 0.05832793259883344, 'fraction_numerical': 0.013825880319723483, 'mean_word_length': 3.8279457768508864, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4347672', 'n_tokens_mistral': 1380, 'n_tokens_neox': 1250, 'n_words': 687}