EZP-30636: Enabled eZ Platform Bundle

[alongosz]

Question	Answer
JIRA issue	EZP-30636
Bug/Improvement	no
New feature	yes
Target version	eZ Platform v3.0
BC breaks	yes
Tests pass	TBD
Doc needed	yes

This PR enables eZ Platform Core Bundle and uses ezplatform extension instead of ezpublish.

TODO:

• Rebase after merging EZP-30636: Provided forward compatibility for eZ Platform Extension ezplatform-core#11 up to master and delete TMP commit.

[emodric]

@alongosz In my limited tests on eZ Platform v3, this breaks our bundles if we switch to ezplatform extension. We have some eZ related config under ezpublish key like image aliases, field template overrides and so on.

If we prepend the bundle config to ezplatform extension instead of ezpublish, some of the config breaks, most notably, field template overrides.

I didn't test this, but this could maybe happen if our bundle is activated after the EzPlatformCoreBundle, meaning our prepending would execute after EzPlatformCoreExtension is done, which means it wouldn't get prepended to ezpublish namespace.

[emodric]

I didn't test this, but this could maybe happen if our bundle is activated after the EzPlatformCoreBundle, meaning our prepending would execute after EzPlatformCoreExtension is done, which means it wouldn't get prepended to ezpublish namespace.

It seems that this is indeed the case. If I move our bundle before the EzPlatformCoreBundle bundle, then it works fine. This unfortunately is not the solution, since there might be other code that depends on having the 3rd party bundles after eZ core bundles.

[alongosz]

I didn't test this, but this could maybe happen if our bundle is activated after the EzPlatformCoreBundle, meaning our prepending would execute after EzPlatformCoreExtension is done, which means it wouldn't get prepended to ezpublish namespace.

It seems that this is indeed the case. If I move our bundle before the EzPlatformCoreBundle bundle, then it works fine. This unfortunately is not the solution, since there might be other code that depends on having the 3rd party bundles after eZ core bundles.

This is known issue being documented via https://github.com/ezsystems/developer-documentation/pull/786/files#diff-c117f5035fbf4b21031830a1fb9927baR108-R111. Unfortunately it's a technical limitation due to how Symfony prepends configuration. Once EZP-30990 is resolved properly, prepending should behave correctly.

[emodric]

Alright, good to know that.