For better integration between 5.2 (symfony based) kernel and legacy (4.x) kernel, injection is used to inject settings, session and current siteaccess from 5.2 into legacy using an event: kernel.event_subscriber
Several settings are injected to avoid having to duplicate settings across new and old kernel, this is done in eZ\Bundle\EzPublishLegacyBundle\LegacyMapper\Configuration.
For mappings below, yml settings prefixed with ezpublish are system settings, while the rest are settings you can define pr siteaccess.
The settings for "Server", "Port", "User", "Password", "Database" and "DatabaseImplementation" is set based on the current settings in your yml files, either from the explicit settings defined below, or the "dsn"
The settings for "VarDir" and "StorageDir" is set based on current settings in your yml files as shown below.
Some of the settings for image sub system is set based on your yml files as shown below.
Using ImageMagick filters
The following block shows a valid ImageMagick filters usage example for
Since ImageMagick filters usage changed from eZ Publish 4.x versions you can find the list of filters existing by default to use eZ Publish 5.2:
|ImageMagick filters list for yml|
For more details on setting ImageMagick filters on image.ini please refer to the [imagemagick] / filters documentation.
Extending injected settings
It's possible to add your own kernel event subscriber and also inject your own settings by following how it is done in LegacyMapper\Configuration, and then at the end merge it with existing injected settings like so:
In addition to injected settings, some injection of behavior is also performed.
eZFormToken (CSRF) integration
This feature is available since eZ Publish 5.1 (2013.01)
If your config.yml setting have framework.csrf_protection.enabled set to true, then both kernel.secret and framework.csrf_protection.field_name will be sent to ezxFormToken class so csrf protection in legacy uses the same token and form field name.
framework.csrf_protection.field_name shouldn't be changed as that would prevent eZFormToken from working with most AJAX custom code
ezpEvent (Cache clear) integration
A listener is setup for both content/cache and content/cache/all to make sure Symfony (Internal proxy or Varnish with custom vcl) HTTP cache is cleared when cache is cleared in eZ Publish admin interface.