Upgrading to Symfony 3!

Hey axa,

Actually, I think your idea is partially OK, but it depends, because if we talk about real project - you will have a lot of custom configuration and dependencies. For example, except src/ folder you may have your own dependencies in composer.json, a lot of custom configuration in app/config/*.yml files, etc, so just copying src/ folder does not enough. And probably the most important problem is that this way you lose all your Git history, i.e. you create a new project where you'll need to do "git init" which means you start with empty Git repo. Also, most probably cache and logs from the previous project won't work, so copying them is pointless.

And btw, do not forget to run your tests before pushing to production (you write tests, right?) :)

Anyway, your way looks more time consuming as for me.

Cheers!

Yes, you are right... Thanks for answer.

Hey claire

Can you post your services.yml file? Look like you/or something is injecting the container into the mailchimp service in a deprecated way

Cheers!

Hey,
It pretty big so here the snippets which are using mailchimp. But if it helps i can post the whole thing.

    line_fringe.mailchimp_manager:
        class: Line\FringeBundle\Email\MailchimpManager
        arguments: [ '@mailchimp', '@line_fringe.setting_manager' ]
        lazy: true

  line_fringe.user_manager:
        class: Line\FringeBundle\Entity\Manager\UserManager
        arguments: [ '@doctrine.orm.entity_manager', '@security.encoder_factory', '@line_via.line_via_api', '@line_fringe.mailchimp_manager', '@line_fringe.mailer', '@line_fringe.setting_manager']

Thank you for taking the time to help me MolloKhan :)

Yo claire!

Yes, so I do know this error. Let me explain it first (actually it looks like you found the [BC BREAK] item), and then we'll see if we can find the cause! Normally (as you do in your code) when you pass arguments to a service, it looks like this (your example above passes the arguments all on 1 line, but it's equivalent to this multi-line version)

    arguments:
        - foo
        - bar

But, in Symfony 2, it was legal to do this instead:

    arguments:
        something: foo
        somethingelse: bar

In this case, you're naming the keys to your arguments. This had absolutely no effect - the above to examples created identical services. In Symfony 3, we made using string keys like this illegal (we did this because we now allow named arguments https://knpuniversity.com/screencast/symfony-3.3/named-arguments).

So, somewhere in your code, someone is doing this - and using a "container" key. And the problem is indeed in the bundle: https://github.com/AlmogBaku/MailchimpBundle/blob/master/Resources/config/services.yml#L5

I think you need to find a new bundle :). A quick search reveals this one: https://github.com/AhmedSamy/HypeMailchimpBundle, though I have never used it. But honestly, the bundle you're using isn't giving you anything, besides that one service definition - https://github.com/AlmogBaku/MailchimpBundle/blob/master/Resources/config/services.yml#L5 and this one class: https://github.com/AlmogBaku/MailchimpBundle/blob/master/Mailchimp/Mailchimp.php. You could just copy those into your code very easily :).

I hope that helps!

Had a thought could it be to do with the 'godisco/mailchimp-bundle' , im on the latest version but it seems it not been updated in a while. Looking into this bundles dependency injection I see :

public function load(array $configs, ContainerBuilder $container)
{
$configuration = new Configuration();
$config = $this->processConfiguration($configuration, $configs);

$loader = new Loader\YamlFileLoader($container, new FileLocator(__DIR__.'/../Resources/config'));
$loader->load('services.yml');

$container->setParameter("mailchimp.api_key", $config['api_key']);
$container->setParameter("mailchimp.default_list", $config['default_list']);
}

Could this be the cause? If so , what would you recommend, maybe finding a replacement bundle?