{"id":37013140,"url":"https://github.com/netgen/ezpublish-kernel","last_synced_at":"2026-01-14T01:17:04.576Z","repository":{"id":57025472,"uuid":"46927752","full_name":"netgen/ezpublish-kernel","owner":"netgen","description":"eZ Publish API and kernel. This is the heart of eZ Publish 5. This is a v2014.11 kernel, maintained for bugfixes by Netgen.","archived":true,"fork":false,"pushed_at":"2021-01-11T13:11:42.000Z","size":33160,"stargazers_count":8,"open_issues_count":2,"forks_count":17,"subscribers_count":15,"default_branch":"master","last_synced_at":"2025-10-24T22:38:56.721Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://netgen.io","language":"PHP","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/netgen.png","metadata":{"files":{"readme":"Readme.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2015-11-26T13:17:50.000Z","updated_at":"2023-01-28T11:08:44.000Z","dependencies_parsed_at":"2022-08-23T14:20:10.522Z","dependency_job_id":null,"html_url":"https://github.com/netgen/ezpublish-kernel","commit_stats":null,"previous_names":[],"tags_count":15,"template":false,"template_full_name":null,"purl":"pkg:github/netgen/ezpublish-kernel","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/netgen%2Fezpublish-kernel","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/netgen%2Fezpublish-kernel/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/netgen%2Fezpublish-kernel/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/netgen%2Fezpublish-kernel/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/netgen","download_url":"https://codeload.github.com/netgen/ezpublish-kernel/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/netgen%2Fezpublish-kernel/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28407666,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-14T00:40:43.272Z","status":"ssl_error","status_checked_at":"2026-01-14T00:40:42.636Z","response_time":56,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-01-14T01:17:03.668Z","updated_at":"2026-01-14T01:17:04.562Z","avatar_url":"https://github.com/netgen.png","language":"PHP","funding_links":[],"categories":[],"sub_categories":[],"readme":"# eZ Publish 5.x Kernel\n[![Build Status](https://travis-ci.org/netgen/ezpublish-kernel.png?branch=master)](https://travis-ci.org/netgen/ezpublish-kernel)\n\n[![SensioLabsInsight](https://insight.sensiolabs.com/projects/0885c0ce-4b9f-4b89-aa9c-e8f9f7a315e0/big.png)](https://insight.sensiolabs.com/projects/0885c0ce-4b9f-4b89-aa9c-e8f9f7a315e0)\n\nWelcome to the new eZ Publish 5.x Kernel, this code repository contains several layers of API's and implementation of them.\nHowever it does not contain all parts that make up the eZ Publish 5 install, for the full eZ Publish 5 package including\nbundles, Legacy Stack, install doc and more; please see our [ezpublish-community](https://github.com/ezsystems/ezpublish-community) repository.\n\n## Legacy Stack (LS)\n\nLegacy Stack: Legacy kernel (4.x) + extensions\n\neZ Publish 5.x is a bottom up rewrite of eZ Publish, so a conservative approach where taken on backwards compatibility\nby bundling both Legacy Stack (4.x) and 5.x Stack together in one integrated package (ref ezpublish-community repository above).\n\nIn addition to the BC reason, the second reason is that eZ Publish 5.x does not yet provide own UI's, editor and admin\ngui is for the time being still provided by Legacy Stack.\n\nThe legacy integrations are done in many parts of the systems, making it possible to use both kernels in the same request,\nhence being able to do a smooth transition from existing 4.x installation to 5.x installation going forward.\n\nHowever for performance reasons we recommend trying to use either legacy with \"legacy\\_mode\" turned on or pure 5.x Stack\non a siteaccess case by case basis. This will still make sure cache and other integrations work together (something that\nis not the case if you point Apache directly to eZ Publish Legacy), but will avoid duplicate lookups (\"fallbacks\").\n\n\n## 5.x Stack\n\n5.x Stack: 5.x kernel + Bundles (former extensions)\n\n### Bundles\nThe highest level in the eZ Publish 5 architecture are bundles that builds on top of everything bellow, this is where\nmost eZ Publish 5 Bundles  will be written. They will exist in separate git repositories, and optionally\ndefined as dependencies in your project composer.json file (see ezpublish-community repository).\n\n### 5.x Kernel\n\n#### Kernel Bundles: REST, Core \u0026 Legacy\nThese bundles are important parts of the eZ Publish 5.x kernel.\n\n* Core Bundle: Provide additional features to a standard Symfony2 distribution like multilingual UrlAlias routing,\n  siteaccess matching, permissions and helpers for Public API use.\n* Legacy Bundle: Integrations with Legacy kernel, like fallbacks and code reuse across 5.x/Legacy Stack.\n* REST Bundle: Integration of REST API to 5.x (Symfony) Stack\n\nYou can find these in [eZ/Bundle](eZ/Bundle/) and their lower level parts in:\n* [eZ/Publish/Core/REST](eZ/Publish/Core/REST/)  *The REST API implementation*\n* [eZ/Publish/Core/MVC](eZ/Publish/Core/MVC/)  *MVC implementation that integrate with Symfony and Legacy*\n\n\n#### Public API\nPublic API currently provides access to the Content Repository of eZ Publish, exposing Content, Locations\n(former Nodes), Sections, Content Types (former Content Classes), User Groups, Users and Roles.\nIt also provides a new clear interface for plugging in custom field types (former Datatypes).\n\nPublic API is built on top of a set of SPI's abstracting storage/file/\\* functionality.\nBy using Public API your code will be forward compatible to future releases based on enhanced, more scalable and more\nperformant storage engines. It is also fully backwards compatible by using the included \"Legacy\" storage engine, which\nstores data in the way legacy kernel is used to finding it.\n\nImportant parts of this layer is:\n* [eZ/Publish/API](eZ/Publish/API/)  *Public API Interfaces*\n* [eZ/Publish/Core/Repository](eZ/Publish/Core/Repository/)  *Public API Repository implementation*\n\n#### (Private) SPI(Service Provider Interface)\n\nService Provider Interfaces are interfaces that can contain one or several implementations, in some cases Public API\nwill only be able to use one at a time; Persistence (database), IO (file system). In other cases it expects several\nimplementations; FieldTypes (former DataTypes), Limitations (permissions system).\n\nSPI layer is currently considered \"private\" as it will still undergo changes, it will be made \"final\" by the time we\nhave a fully working NoSQL implementation of Persistence and scalable IO storage implementation like S3.\nMeaning you can make your own implementation if you want, but we don't guarantee that it will work across versions.\n\nCurrently SPI consists of:\n* [eZ/Publish/SPI](eZ/Publish/SPI/)  *Service provider interfaces*\n* [eZ/Publish/Core/Persistence/Legacy](eZ/Publish/Core/Persistence/Legacy/)  *Legacy Storage-Engine (Persistence-handler)*\n* [eZ/Publish/Core/IO](eZ/Publish/Core/IO/])  *IO (file) Handlers: flysystem (metadata + binarydata), legacy_dfs_cluster (metadata)*\n\n## How to run tests\n\n### Dependencies\n* **PHP 5 Modules**: php5\\_intl php5\\_xsl php5\\_gd php5\\_sqlite\n* **Database**: sqlite3\n\nYou can also run tests (slower) on mysql or postgres, see [.travis.yml](.travis.yml) for how.\n\n### Installation\n* Clone this repo `git clone https://github.com/netgen/ezpublish-kernel.git`\n* Enter directory `cd ezpublish-kernel`\n* Get [Composer](http://getcomposer.org/download/) using curl `curl -s http://getcomposer.org/installer | php`\n* Install dev dependencies: `php composer.phar install --prefer-dist --dev`\n* Copy config.php-DEVELOPMENT  `cp config.php-DEVELOPMENT config.php`\n* Execute `phpunit -vc phpunit*.xml` with one of:\n  * phpunit.xml  *unit test xml configuration*\n  * phpunit-integration-legacy.xml  *integration test xml configuration for running integration tests with Legacy Storage engine*\n\nThis should produce similar result as [travis](https://travis-ci.org/netgen/ezpublish-kernel).\nIf you don't double check [.travis.yml](.travis.yml) for up-to-date info on how travis is setup.\n\n## Issue tracker\nSubmitting bugs, improvements and stories is possible on https://jira.ez.no/browse/EZP\n\n## Contributing\neZ Publish 5.x is a fully open source, community-driven project, and code contributions are simply done via github pull requests.\n\nShort:\n* Remember to first create a issue in our issue tracker and refer to it in commits and pull requests headers, example:\n  \"Fix EZP-20104: ContentController should return error status when content is not found\"\n  or\n  \"Implement EZP-201xx: Add support for X in Y\"\n* If you want to contribute implementation specification proposals, place them in [doc/](doc/) folder.\n* Keep different changes in different commits in case cherry-pick is preferred instead of a merge later.\n  * A Pull Request should only cover one issue.\n  * A commit should not contain code changes at the same time as doing coding standards/whitespace/typo fixes.\n* TDD: Write/Change the test(s) for the change you do and commit it before you do the actual code change.\n  * If a bug affects Public API, write or enhance a integration test to make sure the bug is covered.\n  * Unit tests should only use mocks/stubs and never test the full stack like integrations tests does.\n* Please test/check your commits before pushing even if we have automated checks in place on pull requests:\n  * Run unit tests and integration test before commits\n  * Make sure you follow our [coding standards](https://github.com/ezsystems/ezcs)\n\nFor further information please have a look at the [related guidance page](http://share.ez.no/get-involved/develop). You will, amongst other, learn how to make pull-requests. More on this here : [\"How to contribute to eZ Publish using GIT\"](http://share.ez.no/learn/ez-publish/how-to-contribute-to-ez-publish-using-git).\n\n## Discussing/Exchanging\nA dedicated forum has been set-up to discuss all PHP API-related topics : http://share.ez.no/forums/new-php-api\n\n## Copyright \u0026 license\nCopyright eZ Systems AS, for copyright and license details see provided LICENSE file.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnetgen%2Fezpublish-kernel","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnetgen%2Fezpublish-kernel","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnetgen%2Fezpublish-kernel/lists"}