We use our own ImageProcessor
In the past we passed it as a config value to MPDF:
|
parent::__construct([ |
|
'mode' => $mode, |
|
'format' => $format, |
|
'default_font_size' => $fontsize, |
|
'ImageProcessorClass' => DokuImageProcessorDecorator::class, |
|
'tempDir' => _MPDF_TEMP_PATH, //$conf['tmpdir'] . '/tmp/dwpdf' |
|
'SHYlang' => $docLang, |
|
]); |
Unfortunately this seems no longer be supported in MPDF (I'm not sure if this was ever supported or if we monkey patched our MPDF version).
The proper way would be to pass a custom $container to the constructor which would then be used by the internal ServiceFactory to load our class.
Unfortunately it seems the ImageDecorator is not loaded through that Factory.
So going forward I see two options:
- Monkey patch our MPDF library in the vendor directory (probably using a simple setImageDecorator() method)
- Use reflection to set the private property in our sub class
The second method would probably more future proof as there would be no need to reapply the patch on updates.
Any opinions?
PS: I will also open an issue upstream.
We use our own ImageProcessor
In the past we passed it as a config value to MPDF:
dokuwiki-plugin-dw2pdf/DokuPDF.class.php
Lines 55 to 62 in 5da2fd3
Unfortunately this seems no longer be supported in MPDF (I'm not sure if this was ever supported or if we monkey patched our MPDF version).
The proper way would be to pass a custom $container to the constructor which would then be used by the internal ServiceFactory to load our class.
Unfortunately it seems the ImageDecorator is not loaded through that Factory.
So going forward I see two options:
The second method would probably more future proof as there would be no need to reapply the patch on updates.
Any opinions?
PS: I will also open an issue upstream.