3.1.6

What's Changed

• CMS 4.13 compatibility by @michalkleiner in #37

Full Changelog: 3.1.5...3.1.6

4.0.0-alpha10

Adding a feature where taxonomy type can determine whether singular or plural display name will be used for its child terms when displaying on the front-end.
Each term can also override this and/or provide a custom display name.

4.0.0 alpha9

4.0.0-alpha9

Merge pull request #29 from chrometoasters/pulls/28-publish-on-unvers…

4.0.0 alpha8

4.0.0-alpha8

Merge pull request #27 from chrometoasters/pulls/26-fresh-install-mig…

4.0.0 alpha7

4.0.0-alpha7

Ensure the migration runs only once via BaseObject and not its subcla…

4.0.0 alpha6

4.0.0-alpha6

Skip migration when BaseObject or BaseTerm contain any data

4.0.0 alpha5

Get legacy TaxonomyTerm db fields from the db table

The ORM doesn't know about the legacy fields that moved to other tables
anymore.

4.0.0 alpha4

Enhancements to the migration script to excluded fields added to BaseObject and BaseTerm (e.g. through an extension) that are not present on TaxonomyTerm.

Skip the migration when all base tables have the same number of records to avoid running the migration for each class extending BaseObject due to requireDefaultRecords being called for each ancestor.

4.0.0 alpha3

4.0.0-alpha3

Fix migration task class name usage

4.0.0 alpha2

Main changes

• Adding automatic migration from 3.x to 4.x data model format.

Notes

• Automatic migration can be disabled by setting Chrometoaster\AdvancedTaxonomies\Dev\AT4xMigrationTask::enable_v4_migration to false via yaml config.