Bernhard Rusch

I'm still facing issues: ``` Traceback (most recent call last): File "/opt/bin/pyze", line 8, in sys.exit(main()) File "/volume1/Share/Web/SmartHome/.local/lib/python3.8/site-packages/pyze/cli/__main__.py", line 69, in main parsed_args.func(parsed_args) File "/volume1/Share/Web/SmartHome/.local/lib/python3.8/site-packages/pyze/cli/status.py", line 35, in run v...

Thank you very much!

@aashan10 it's about fixing deprecations, right? What does Symfony suggests here?

Probably also related: https://github.com/pimcore/pimcore/blob/38419b06c61565e62122e32684e37c102cbe25d2/bundles/AdminBundle/src/EventListener/AdminSessionBagListener.php#L70 https://github.com/pimcore/pimcore/blob/70b1db360a2a4fa498c69f71a33aa1db5a3a42d1/bundles/CoreBundle/DependencyInjection/Configuration.php#L1126

@kingjia90 I'm not sure if we really need a migration for that ... it shouldn't hurt/break if the config is still there and as soon as you save it again,...

We should also change the docs accordingly, e.g. here https://pimcore.com/docs/pimcore/current/Development_Documentation/Installation_and_Upgrade/Updating_Pimcore/index.html

@aashan10 I think we can also remove `Pimcore\Composer::executeMigrationsUp()` as we don't need it anywhere else ...

@aashan10 note: we also need to remove that from skeleton and demos. E.g.: https://github.com/pimcore/skeleton/blob/11.x/composer.json#L34

@aashan10 you can straight create a PR as well, shouldn't be too much effort - think it's just a one-liner 😉

This is on the roadmap for v11.