For better integration between 5.x (symfony based) kernel and le= gacy (4.x) kernel, injection is used to inject settings, session and current siteaccess from 5.x into legacy u= sing an event: kernel.event_subscriber
Several settings are injected to avoid having to duplicate settings acro=
ss new and old kernel, this is done in eZ\Bundle\EzPublishLegacyBundle=
\LegacyMapper\Configuration.
For mappings below, yml settings prefixed w=
ith ezpublish are system settings, while the rest are settings you can defi=
ne pr siteaccess.
The settings for "Server", "Port", "User", "Password", "Database" and "D= atabaseImplementation" is set based on the current settings in your yml fil= es, either from the explicit settings defined below, or the "dsn"
Mapping:
| yml | site.ini [DatabaseSettings] |
|---|---|
| server | Server |
| port | Port |
| user | User |
| password | Password |
| database_name | Database |
| type | DatabaseImplementation |
The settings for "VarDir" and "StorageDir" is set based on current setti= ngs in your yml files as shown below.
Mapping:
| yml | site.ini [FileSettings] |
|---|---|
| var_dir | VarDir |
| storage_dir | StorageDir |
Some of the settings for image sub system is set based on your yml files= as shown below.
Mapping:
| yml | image.ini |
|---|---|
| ezpublish.image.temporary_dir | [FileSettings]\TemporaryDir |
| ezpublish.image.published_images_dir | [FileSettings]\PublishedImages |
| ezpublish.image.versioned_images_d= ir | [FileSettings]\VersionedImag= es |
| image_variations | [FileSettings]\AliasList |
| ezpublish.image.imagemagick.enable= d | [ImageMagick]\IsEnabled |
| ezpublish.image.imagemagick.execut= able_path | [ImageMagick]\ExecutablePath= |
| ezpublish.image.imagemagick.execut= able | [ImageMagick]\Executable |
| imagemagick.pre_parameters | [ImageMagick]\PreParameters |
| imagemagick.post_parameters | [ImageMagick]\PostParameters |
| ezpublish.image.imagemagick.filter= s | [ImageMagick]\Filters |
The following block shows a valid ImageMagick filters usage example for =
ezpublish.yml:
ezpublish:
imagemagick:
filters:
geometry/scale: "-geometry {1}x{2}"=20
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.x:
| ImageMagick filters list for yml |
|---|
sharpen: "-sharpen 0.5" |
geometry/scale: "-geometry {1}x{2}"=
|
geometry/scalewidth: "-geometry {1}" |
geometry/scaleheight: "-geometry x{1}" |
geometry/scaledownonly: "-geometry {1}x{2}=
>" |
geometry/scalewidthdownonly: "-geometry {1=
}>" |
geometry/scaleheightdownonly: "-geometry x=
{1}>" |
geometry/scaleexact: "-geometry {1}x{2}!"<=
/code> |
geometry/scalepercent: "-geometry {1}x{2}"=
|
geometry/crop: "-crop {1}x{2}+{3}+{4}" |
filter/noise: "-noise {1}" |
filter/swirl: "-swirl {1}" |
colorspace/gray: "-colorspace GRAY"=
|
colorspace/transparent: "-colorspace Trans=
parent" |
colorspace: "-colorspace {1}" |
border: "-border {1}x{2}" |
border/color: "-bordercolor rgb({1},{2},{3=
})" |
border/width: "-borderwidth {1}"
|
flatten: "-flatten"
|
|
For more details on setting ImageMagick filters on image.ini please refe= r to the [imagemagick] / filters documentation.
It's possible to add your own kernel event subscriber and also inject yo= ur own settings by following how it is done in LegacyMapper\Configurat= ion, and then at the end merge it with existing injected settings like so:<= /p>
$event->getParameters()->set(
"injected-settings",
$settings + (array)$event->getParameters()->get( "injecte=
d-settings" )
);=20
In addition to injected settings, some injection of behavior i= s also performed.
This feature is only available as of eZ Publish 5.1 (2013.01)
If your config.yml setting have framework.csrf_protection.enabl= ed set to true, then both kernel.secret an= d framework.csrf_protection.field_name will be sent to ezxFor= mToken class so csrf protection in legacy uses the same token and form fiel= d name.
By making sure all your Symfony forms uses the provided csrf protection, forms with intention=3Dlegacy can b= e setup to send data to legacy kernel.
Please note that framework.csrf_protection.field_name shoul=
dn't be changed as that would prevent eZFormToken from working with most AJ=
AX custom code.
A listener is setup for both content/cache and content/cache/a= ll to make sure Symfony (Internal proxy or Varnish with custom vcl) HTTP ca= che is cleared when cache is cleared in eZ Publish admin interface.