Changed configuration key to ezpublish from ezplatform #119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Travis failure: https://travis-ci.org/ezsystems/ezplatform/jobs/626869956?utm_medium=notification&utm_source=slack
In 3.0 we've changed the main config key from
ezpublish
toezplatform
. This change can be forward-compatible (ezsystems/ezplatform-core#11), but it requires enabling EzPlatformCoreBundle in AppKernel (new EzSystems\EzPlatformCoreBundle\EzPlatformCoreBundle(),
).This bundle is not enabled by default (see: https://github.com/ezsystems/ezplatform/blob/2.5/app/AppKernel.php), meaning we cannot use that and have to use
ezpublish
key.Also changing how the examples are run (they should be run in standard mode, not parallel).