se7enxweb / ezprestapiprovider
Deprecated compatibility shim: REST API v1 and v2 are served by se7enxweb/ezprestapi. Keeps the class names ezpRestApiProvider and ezpRestContentController of the old v1 content provider working.
Package info
github.com/se7enxweb/ezprestapiprovider
Type:ezpublish-legacy-extension
pkg:composer/se7enxweb/ezprestapiprovider
Fund package maintenance!
v6.0.4
2026-10-16 03:55 UTC
Requires
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-10-24 02:33:22 UTC
README
ezprestapiprovider (deprecated) =============================== REST API v1 and v2 are served by one extension, ezprestapi (https://github.com/se7enxweb/ezprestapi). Since 6.0.4 this extension is a compatibility shim and adds nothing of its own: - ezpRestApiProvider extends ezp7xRestApiProvider and ezpRestContentController extends ezp7xRestContentController, so a rest.ini or code that names the old classes keeps working; - its rest.ini maps the prefixes ezp and ezpl to ezp7xRestApiProvider, the same values ezprestapi sets, so activating both, in either order, gives the same API; - the classes it used to share with ezprestapi (ezpRestAtomController, ezpRestAtomView, ezpRestAtomDecorator, ezpRestContentModel, ezpRestApiViewController) are only in ezprestapi now. The v1 URLs (/api/ezp/v1/content/node/<id>/list/offset/0/limit/20?ResponseGroups=Fields and the rest) answer with the same bodies as before. Migrate by activating ezprestapi and removing ActiveExtensions[]=ezprestapiprovider, then clear the INI cache and regenerate the extension autoloads.