ezsystems / legacy-bridge
eZ Platform bridge to eZ Publish Legacy
Installs: 116 173
Dependents: 8
Suggesters: 1
Security: 0
Stars: 17
Watchers: 33
Forks: 31
Type:ezplatform-bundle
Requires
- ezsystems/ezplatform-xmltext-fieldtype: ^1.8
- ezsystems/ezpublish-kernel: ^7.5.24
- ezsystems/ezpublish-legacy: ^2019.03
- ezsystems/ezpublish-legacy-installer: ^2.0.4
- sensio/distribution-bundle: ^5.0.24
- twig/twig: ^1.35 || ^2.5
Requires (Dev)
- dev-master / 2.1.x-dev
- v2.1.9
- v2.1.8
- v2.1.7
- v2.1.6
- v2.1.5
- v2.1.4
- v2.1.3
- v2.1.2
- v2.1.1
- v2.1.0
- v2.1.0-rc3
- v2.1.0-rc2
- v2.1.0-rc1
- v2.0.11
- v2.0.10
- v2.0.9
- v2.0.8
- v2.0.7
- v2.0.6
- v2.0.5
- v2.0.4
- v2.0.3
- v2.0.2
- v2.0.1
- v2.0.0
- 1.5.x-dev
- v1.5.0
- 1.4.x-dev
- v1.4.11
- v1.4.10
- v1.4.9
- v1.4.8
- v1.4.7
- v1.4.6
- v1.4.5
- v1.4.4
- v1.4.3
- v1.4.2
- v1.4.1
- v1.4.0.1
- v1.4.0
- v1.4.0-RC1
- v1.4.0-beta2
- v1.4.0-beta1
- 1.3.x-dev
- v1.3.1
- v1.3.0
- 1.2.x-dev
- v1.2.1
- v1.2.0
- 1.1.x-dev
- v1.1.2
- v1.1.1
- v1.1.0
- 1.0.x-dev
- v1.0.5
- v1.0.4
- v1.0.3
- v1.0.2
- v1.0.1
- v1.0.0
- v0.2.1
- v0.2.0
- v0.1.1
- v0.1.0
- dev-ezp_29144
- dev-distributionBundleCompatibility
- dev-community_behat_tests
- dev-bd_sensiolabs_insight
- dev-bdd_wizard_kickstart
This package is auto-updated.
Last update: 2024-10-26 18:22:39 UTC
README
This package integrates eZ Publish Legacy into eZ Platform. It is an enhanced version of LegacyBundle that were part of eZ Publish 5.x, providing even more features to simplify running Platform stack and legacy together.
It is meant to be installed as an addition to eZ Platform 1.13.x - 2.x installs when you need legacy for migration.
NOTE: Legacy bridge will not be supported on eZ Platform 3.x eZ Platform 3.x aims to finally start improving database schema again, which will break legacy comparability. Recommendation is to use eZ Platform / Platform Enterprise 2.5LTS to handle migration needs, and once done evaluate 3.x upgrade.
See INSTALL.md for the installation procedure.
Reporting issues
As Legacy Bridge is co-maintained by the community and eZ Engineering (as active community members), issues found can be reported directly here on Github. There is no SLA on fixes, this is all on voluntary basis, and we welcome you in contributing to issues in any form you you are capable of.
For Enterprise Customers
As of version 1.3.0 you can optionally report issues via normal support channels as well where you do have an SLA on response time. But as always if you know a possible fix, proposing a PR as well here can speed up the issue identification and fixing a lot so we encourage eZ Partners to actively participate whenever they can, as it benefits themselves as well as the customer.