Migration SF2.8 => SF3.4

Question

Migration SF2.8 => SF3.4

YaaSSDD opened this issue 5 years ago · 11 comments

Hello I have a problem that I can not solve in spite of the corrections to be applied following the resolved issues and the official doc my problem is to reveal following the migration of Symfony towards the 3.4 and the passage to the 1.3 of CMF core bundle my mistake is this :

Unrecognized option "use_sonata_admin" under "cmf_core.persistence.orm"

my cmf conf to config.yml :

cmf_core:
    persistence:
        orm:
            enabled: true
            manager_name: ~
            use_sonata_admin: auto

Debian PHP7.1 Symfony3.4

Answer 1 · 2019-04-30T11:47:07.000Z

when moving to the cmf 2.0 version, all sonata admin integration has been moved to the separate bundle CmfSonataAdminIntegrationBundle. if you use sonata admin, you need to add that bundle and check its configuration. if you do not use sonata admin, simply delete the line about use_sonata_admin.

Answer 2 · 2019-04-30T12:07:54.000Z

so I have to remove this line: use_sonata_admin and add the following bundle: symfony-cmf / sonata-phpcr-admin-integration-bundle?

Answer 3 · 2019-04-30T12:25:36.000Z

if you are using sonata admins then yes. and check the configuration options for the sonata admin integration bundle to see if you want to configure something.

Answer 4 · 2019-04-30T12:34:11.000Z

ok thank you very much, would you have a link for me please

Answer 5 · 2019-04-30T12:37:50.000Z

best install the bundle and then run php bin/console config:dump-reference CmfSonataAdminIntegrationBundle

Answer 6 · 2019-04-30T13:18:39.000Z

thank you :-) I'm going to try

Answer 7 · 2019-04-30T13:39:53.000Z

symfony-cmf/sonata-phpcr-admin-integration-bundle or symfony-cmf/sonata-admin-integration-bundle because symfony-cmf/sonata-admin-integration-bundle is not maintened

Answer 8 · 2019-04-30T13:47:13.000Z

hm... looking at your original comment, you have been using sonata orm admin. if you did, you need to write your own admin now i think. there is only sonata-phpcr-admin-integration-bundle.

Answer 9 · 2019-04-30T14:17:21.000Z

if i use phpcr i would not need to write my own admin? What do you recommend ?
thank you for your availability :)

Answer 10 · 2019-04-30T14:27:22.000Z

i am not sure if we even provided orm admin classes in any cmf bundles - due to the nature of orm, this would be quite tricky to do in a reusable way. are you currently using orm admins from the cmf at all? what happens if you simply remove the use_sonata_admin: auto and don't do anything else? does your admin backend still work as expected?

using phpcr is quite a different thing as the storage changes. i don't know what you do in your project but that probably would be a lot of hassle.

Answer 11 · 2019-04-30T14:42:06.000Z

yes I try to remove it but it gives me an error:

Notice: Undefined index: user

suddenly I think there is a lot of dependence, and actually make changes for phpcr looks very complicated because the project is more than a million line of codes