Skip to content

Releases: humanmade/altis-cms-installer

0.4.4

19 Apr 19:52
5186116
Compare
Choose a tag to compare

What's Changed

  • Fix deprecation warning on a dynamic property by @jerico in #38

New Contributors

Full Changelog: 0.4.3...0.4.4

0.4.3

29 Oct 10:14
d4a49f6
Compare
Choose a tag to compare
  • Add Composer v2 support #34

0.4.2

15 Apr 10:58
e9b6426
Compare
Choose a tag to compare
  • Use platform-independent directory separator #32

0.4.1

04 Feb 13:32
3347ad9
Compare
Choose a tag to compare
  • Fix incorrect module paths generated after calling composer require #31

0.4.0

27 Nov 19:57
e8e70d5
Compare
Choose a tag to compare
  • Install files have been moved to the CMS module #28

0.3.3

21 Nov 09:43
86b0087
Compare
Choose a tag to compare
  • Don't load WP in unit testing context #27

0.3.2

21 Oct 14:23
ffd5d11
Compare
Choose a tag to compare
  • Support for project level custom module loading #25

v0.3.1

01 Oct 16:10
3a2619e
Compare
Choose a tag to compare
  • Bug: Fix variable name used to write modules.php file.

v0.3.0

01 Oct 11:32
8dd9627
Compare
Choose a tag to compare

This release brings in a fundamental change to how Altis modules are bootstrapped. They no longer need to register their load.php files via composer's autoload property or use the function_exists( 'add_action' ) guard.

This means we can avoid loading files that have side effects via composer's autoload.php.

Modules should remove load.php from being autoloaded and add the following to their composer.json file:

{
  "extra": {
    "altis": {}
  }
}

The Altis property can remain empty for the time being.

v0.2.2

24 May 13:34
e31031f
Compare
Choose a tag to compare
  • Ignore /content/upload by default #19