Details
-
Story
-
Resolution: Done
-
High
-
3.3.33
-
Candidates for next sprint
-
13
Description
We've prepended ezpublish configuration with the one taken from ezplatform via EZP-30636 to provide forward compatibility and make migration easier.
Now we need to get rid of that dependency by providing fully functional EzPlatformCoreBundle.
This Story will require several sub-tasks, as the process should be gradual.
The most difficult parts:
- hooking new bundle into the Repository services as API loader,
- providing BC so it's possible to use either EzPlatformCoreBundle or deprecated {{EzPublishCoreBundle (might not be possible at all).
Designs
Attachments
Issue Links
1.
|
Create proper Configuration for {{ezplatform}} extension | Closed | Unassigned | |
2.
|
Create policy provider similar to EzPublishCoreExtension::addPolicyProvider | Closed | Unassigned | |
3.
|
Create SA configuration parser similar to EzPublishCoreExtension::addConfigParser | Closed | Unassigned | |
4.
|
Create default settings provider similar to EzPublishCoreBundle::addDefaultSettings | Closed | Unassigned |