2.0.0

This new major release is for use with ez Platform 2.0, and legacy 2017.12.0 release.
Make sure to take a look at the upgrade documentation provided with the release before upgrading.

Changes

• Support for eZ kernel 7.0 (#122)
• Apply Symfony best practices (#126)
• Add Upgrade docs (#128, 5ce5b8d)
• Require eZ Platform XMLText field type (#129)
• Remove deprecated features (#127)
• Update install instructions (#130)

1.4.2

Changes

• legacy:assets_install should remove empty IO root before check empty var folder (#125)

1.4.1

Changs

• Add missing argument to ezpublish.http_cache.purger.instant for 1.12 compatability (#123)

1.4.0.1

Changes

• Fix HttpCachePass error after #120 (#121)

v1.4.0

Changes

• #107: [FEATURE] Add support for setting up symlinks for legacy settings & designs
  • CONTEXT: As you might know, it is not considered safe to manually place files inside ezpublish_legacy/ folder, as it is managed by composer, it should ideally not be versioned in GIT, and furthermore composer will sometimes remove it and reinstall the package if it detects conflicts or similar. These feature is part of a continued effort to make sure such issues are handled / avoided by default.
  • THIS FEATURE aims to simplify upcoming migration documentation from 4.x / 5.x to eZ Platform 1.11 and higher with legacy bridge, it adds ezpublish:legacy:symlinkcommand (& composer install/update usage) for handling convention for symlinking designs and settings, doc also suggests convention for handling storage folder now even if not handled by this feature (storage is typically not stored in GITm and depends on setup). NOTE: Extensions are not covered by this feature as they are already covered via composer usage or using LegacyBundle feature for bundles either in src/ or via composer.
• #112: ezpublishlegacy:assets_install should not delete non empty folders unless asked to
  • BC: To retain old behavior of this command when always hard copying files you'll need to use --force option to always overwrite folders, symlinks are not affected by this as they are considered safe to remove
• [Doc] Update cluster rewrite rules to use "app.php" (#113)
• Update ScriptHandler to support symfony-bin-dir (#117)
• Align CS with eZ kernel (#118)
• [EZP-28156] Use ezplatform-http-cache services when available (#120)

1.4.0-RC1

No changes besides doc since beta2.

1.4.0-beta2

Changes since beta1:

• [Doc] Update cluster rewrite rules to use "app.php" (#113)
• Update ScriptHandler to support symfony-bin-dir (#117)
• Align CS with eZ kernel (#118)

1.4.0-beta1

Changes since 1.3:

• #107: [FEATURE] Add support for setting up symlinks for legacy settings & designs
  • CONTEXT: As you might know, it is not considered safe to manually place files inside ezpublish_legacy/ folder, as it is managed by composer, it should ideally not be versioned in GIT, and furthermore composer will sometime remove it and reinstall the package if it detects conflicts or similar. These feature is part of a continued effort to make sure such issues are handled / avoided by default.
  • THIS FEATURE aims to simplify upcoming migration documentation from 4.x / 5.x to eZ Platform 1.11 and higher with legacy bridge, it adds ezpublish:legacy:symlinkcommand (& composer install/update usage) for handling convention for symlinking designs and settings, doc also suggests convention for handling storage folder now even if not handled by this feature (storage is typically not stored in GITm and depends on setup). NOTE: Extensions are not covered by this feature as they are already covered via composer usage or using LegacyBundle feature for bundles either in src/ or via composer.
• #112: ezpublishlegacy:assets_install should not delete non empty folders unless asked to
  • BC: To retain old behavior of this command when always hard copying files you'll need to use --force option to always overwrite folders, symlinks are not affected by this as they are considered safe to remove

v1.3.1

EZP-27795: Notice thrown when declaring empty HTTP headers in Legacy …

v1.3.0

Changes since 1.2:

• Support:
  • LegacyBridge 1.3 and higher officially supported for eZ Platform Enterprise users together with the corresponding eZ Publish Legacy 2017.08 release and higher.
• Breaking:
  • Simplify install instructions by requiring eZ Platform v1.11, eZ Publish Legacy 2017.08 & Legacy Installer v2.0.4 and higher (#98) This also implies we only support PHP 5.6+ as of this version, given the Platform requirement change. The reason for that Platform requirement change is to make sure no one ends up with a Platform version that has incompatible features with legacy version installed, 1.11 and 2017.08 have feature parity, see 2017.08 milestone for details.
• Doc:
  • Clarify that legacy routes should be added at the end of app/config/routing (#99, #100)
  • Clarify install of optional legacy extensions (#105)
• Tests:
  • Fix tests after ezsystems/ezpublish-kernel#1965 (#97)
  • Move bundle test to right dir so it's tested by test suite (#104)