You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to end of life of php7.4 I attempted to upgrade eZ Platform 2.5 project to Ibexa 3.3, so we can operate on php8.
What I found:
remote-media-bundle:3.0.x-dev installs ok and follows Symfony5 BC changes but lacks any support for eZ FieldTypes resulting in
"Could not find 'eZ\Publish\SPI\Persistence\Content\FieldValue\Converter\*' with identifier 'ngremotemedia'"
I can install remote-media-bundle:2.0.x-dev but DependencyInjection/Configuration breaks due to changes in TreeBuilder and /Core/FieldType/RemoteMedia/* need adaptation to meet updates FieldType interfaces.
I managed to overcome those issues by exluding vendor classes from autoload and replacing with my overrides but then I got
Argument 3 passed to Netgen\Layouts\RemoteMedia\ContentBrowser\Backend\RemoteMediaBackend::__construct() must be an instance of Symfony\Component\Translation\TranslatorInterface, instance of Symfony\Component\Translation\DataCollectorTranslator given
which might require ticket in layouts remote media repository.
I assume completing FieldType bundle for v3 where lot of rework is happening might be a big project, but maybe you can consider introduction of some indirect version between 2.0 and 3.0 that will address minor BC changes to help running Ibexa 3 installations while waiting for major work on 3.0 to get finished.
The text was updated successfully, but these errors were encountered:
Due to end of life of php7.4 I attempted to upgrade eZ Platform 2.5 project to Ibexa 3.3, so we can operate on php8.
What I found:
I managed to overcome those issues by exluding vendor classes from autoload and replacing with my overrides but then I got
which might require ticket in layouts remote media repository.
I assume completing FieldType bundle for v3 where lot of rework is happening might be a big project, but maybe you can consider introduction of some indirect version between 2.0 and 3.0 that will address minor BC changes to help running Ibexa 3 installations while waiting for major work on 3.0 to get finished.
The text was updated successfully, but these errors were encountered: