Whenever breaking changes are present in an upgrade path, we document them here.
Replace the following line
new EMS\ClientHelperBundle\EMSClientHelperBundle()
with the following separated bundles (feel free to omit unused parts of the bundle)
new EMS\ClientHelperBundle\EMSTwigListBundle\EMSTwigListBundle(),
new EMS\ClientHelperBundle\EMSBackendBridgeBundle\EMSBackendBridgeBundle()
Each subbundle now has it's own configuration tree. The original config: (limited to the first hierarchical levels)
php bin/console config:dump-reference EMSClientHelperBundle
# Default configuration for "EMSClientHelperBundle"
ems_client_helper:
request_environment:
elasticms:
twig_list:
templates:
app_enabled:
app_base_path:
Is now splitted per subbundle (find the full reference in README.md)
php bin/console config:dump-reference EMSTwigListBundle
ems_twig_list:
templates:
app_enabled:
app_base_path:
php bin/console config:dump-reference EMSBackendBridgeBundle
ems_backend_bridge:
request_environment:
elasticms:
If you decide to keep using the EMSTwigListBundle, you should modify the routing file. Otherwise you can simply remove the routing configuration:
_ems_client_helper:
resource: "@EMSClientHelperBundle/Resources/config/routing.yml"
prefix: /_helper
becomes
_ems_twig_list:
resource: "@EMSTwigListBundle/Resources/config/routing.yml"
prefix: /_helper
Your project is using the EMSClientHelperBundle classes. Therefore many classNotFound exceptions will now be thrown. Find here some exemple changes to get you along:
EMS\ClientHelperBundle\Elasticsearch\ClientRequest
-->
EMS\ClientHelperBundle\EMSBackendBridgeBundle\Elasticsearch\ClientRequest,
EMS\ClientHelperBundle\Storage\StorageService
-->
EMS\ClientHelperBundle\EMSBackendBridgeBundle\Storage\StorageService
The easiest strategy would be to find and replace
ClientHelperBundle
with ClientHelperBundle\EMSBackendBridgeBundle
in your project source.