PHPackages netgen/ezpublish-legacy-installer - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. netgen/ezpublish-legacy-installer ActiveComposer-plugin[Utility & Helpers](/categories/utility) netgen/ezpublish-legacy-installer ================================= Installer for eZ Publish legacy extensions and legacy kernel itself. 2.2.0(3y ago)035012GPL-2.0PHPPHP ^7.4 || ^8.1 Since Jun 8Pushed 3y ago5 watchersCompare [ Source](https://github.com/netgen/ezpublish-legacy-installer)[ Packagist](https://packagist.org/packages/netgen/ezpublish-legacy-installer)[ RSS](/packages/netgen-ezpublish-legacy-installer/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependencies (1)Versions (2)Used By (2) Composer installer for eZ Publish Legacy Stack ============================================== [](#composer-installer-for-ez-publish-legacy-stack) This installer lets you install extensions for eZ Publish legacy (4.x) with [Composer](http://getcomposer.org). It also helps you install eZ Publish legacy (4.x) itself, by not deleting your settings and custom code when you upgrade to a new release. Installable extensions ---------------------- [](#installable-extensions) To be able to install a legacy extension, it must be properly exposed to Composer with a valid composer.json file (check [Composer documentation](http://getcomposer.org/doc/) for more information), declaring an `ezpublish-legacy-extension` type. Example for SQLIImport: ``` { "name": "lolautruche/sqliimport", "type": "ezpublish-legacy-extension", "description": "Import extension for eZ Publish legacy.", "license": "GPL-2.0", "minimum-stability": "dev", "require": { "php": ">=5.3.3", "ezsystems/ezpublish-legacy-installer": "*" } } ``` ### Extension name vs package name [](#extension-name-vs-package-name) By default, the legacy extension gets installed in a directory named by your package pretty name. For example, package `lolautruche/sqliimport` gets installed in a directory named `sqliimport`. If you ever need to name your composer package differently from your extension name (for example, legacy extension ezfind comes in a `ezsystems/ezfind-ls` package), you may tell composer to use a specifica extension name rather than the package's pretty name. Just add an `ezpublish-legacy-extension-name` extra option in your composer.json file : ``` { "name": "ezsystems/ezfind-ls", "description": "eZ Find is a search extension for eZ Publish legacy, providing more functionality and better results than the default search in eZ Publish.", "type": "ezpublish-legacy-extension", "license": "GPL-2.0", "authors": [ { "name": "eZ Publish dev-team & eZ Community", "homepage": "https://github.com/ezsystems/ezfind/contributors" } ], "minimum-stability": "dev", "require": { "ezsystems/ezpublish-legacy-installer": "*" }, "extra": { "ezpublish-legacy-extension-name": "ezfind" } } ``` How to install in my project ---------------------------- [](#how-to-install-in-my-project) All you need to do is create a composer.json at the root of your project and require the extension (if the extension is not published on packagist, you also need to tell composer where to find it): ``` { "name": "myvendorname/myproject", "description": "My super cool eZ Publish project", "license": "GPL-2.0", "minimum-stability": "dev", "require": { "php": ">=5.3.3", "lolautruche/sqliimport": "~1.2" }, "repositories" : [ { "type": "vcs", "url": "https://github.com/lolautruche/sqliimport.git" } ] } ``` Then run `php composer.phar install` (assuming you have already properly installed Composer of course πŸ˜‰). ### eZ Publish 5 case [](#ez-publish-5-case) By default, the legacy extension installer assumes that eZ Publish legacy is installed in the current folder; in other words, it is configured for pure-eZ Publish 4 projects. If this is not the case (like in eZ Publish 5, where it resides in the `ezpublish_legacy/` folder), then you'll need to configure where it is: ``` { "name": "myvendorname/myproject", "description": "My super cool eZ Publish 5 project", "license": "GPL-2.0", "minimum-stability": "dev", "require": { "php": ">=5.3.3", "lolautruche/sqliimport": "~1.2" }, "repositories" : [ { "type": "vcs", "url": "https://github.com/lolautruche/sqliimport.git" } ], "extra": { "ezpublish-legacy-dir": "ezpublish_legacy" } } ``` ### Health Score 29 β€” LowBetter than 60% of packages Maintenance20 Infrequent updates β€” may be unmaintained Popularity14 Limited adoption so far Community20 Small or concentrated contributor base Maturity56 Maturing project, gaining track record Bus Factor1 Top contributor holds 57.5% of commits β€” single point of failure How is this calculated?**Maintenance (25%)** β€” Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** β€” Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** β€” Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** β€” Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 1435d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/362286?v=4)[Edi ModriΔ‡](/maintainers/emodric)[@emodric](https://github.com/emodric) --- Top Contributors [![lolautruche](https://avatars.githubusercontent.com/u/313528?v=4)](https://github.com/lolautruche "lolautruche (23 commits)")[![andrerom](https://avatars.githubusercontent.com/u/289757?v=4)](https://github.com/andrerom "andrerom (9 commits)")[![emodric](https://avatars.githubusercontent.com/u/362286?v=4)](https://github.com/emodric "emodric (3 commits)")[![bchoquet-heliopsis](https://avatars.githubusercontent.com/u/465757?v=4)](https://github.com/bchoquet-heliopsis "bchoquet-heliopsis (2 commits)")[![bdunogier](https://avatars.githubusercontent.com/u/235928?v=4)](https://github.com/bdunogier "bdunogier (1 commits)")[![gggeek](https://avatars.githubusercontent.com/u/308634?v=4)](https://github.com/gggeek "gggeek (1 commits)")[![pborreli](https://avatars.githubusercontent.com/u/77759?v=4)](https://github.com/pborreli "pborreli (1 commits)") ### Embed Badge ![Health badge](/badges/netgen-ezpublish-legacy-installer/health.svg) ``` [![Health](https://phpackages.com/badges/netgen-ezpublish-legacy-installer/health.svg)](https://phpackages.com/packages/netgen-ezpublish-legacy-installer) ``` ### Alternatives [vaimo/composer-patches Applies a patch from a local or remote file to any package that is part of a given composer project. Patches can be defined both on project and on package level. Optional support for patch versioning, sequencing, custom patch applier configuration and patch command for testing/troubleshooting added patches. 2994.3M16](/packages/vaimo-composer-patches)[mglaman/composer-drupal-lenient 1317.4M15](/packages/mglaman-composer-drupal-lenient)[drupal/core-composer-scaffold A flexible Composer project scaffold builder. 5341.9M446](/packages/drupal-core-composer-scaffold)[drupal/core-project-message Adds a message after Composer installation. 2122.6M172](/packages/drupal-core-project-message)[olvlvl/composer-attribute-collector A convenient and near zero-cost way to retrieve targets of PHP 8 attributes 184108.8k8](/packages/olvlvl-composer-attribute-collector)[lullabot/drainpipe An automated build tool to allow projects to have a set standardized operations scripts. 41716.4k2](/packages/lullabot-drainpipe) PHPackages Β© 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)