Migrating Services & Security

Don't know if I missed some forum rule or something, I tried twice with my question and it just gets removed, not sure whether that's automatic or intentionally done by someone. Too much code sample in the question?

Just posted this but it got marked as spam, so I'll try it again 😎

Moving from symfony 3 to 4 I started injecting the service according to this.

Most functions where I inject the "helper" service it works fine, but for some reason it fails on a few of them and I can't figure out what I've done differently... Here's the error:

Could not resolve argument $helper of
"App\Controller\Poslog\OperatorController::historyindividualaction()",
maybe you forgot to register the controller as a service or missed
tagging it with the "controller.service_arguments"?

I've omitted the contents if the functions completely as it doesn't matter what they contain, I can comment out the entire code inside the HistoryIndividualAction() and still get the exact same error message.

The OperatorController::newAction() below works perfectly fine (as well as a number of other functions within the same object), while the OperatorController::HistoryIndividualAction() fails.

    use App\Service\globalHelper as globalHelper;
    ...
    class OperatorController extends AbstractController
    {
    
      public function newAction(Request $request, ACRGroup $ACRGroup = null, globalHelper $helper)
      {
      ...
      }
    
      public function HistoryIndividualAction($operatorId, globalHelper $helper)
      {
      ...
      }
    }

The routing looks like this

    operator_new:
        path:     /new/{ACRGroup}
        defaults: { _controller: App\Controller\Poslog\OperatorController::newAction, ACRGroup: null }
        methods:  [GET, POST]
    
    operator_history_individual:
        path:     /history/individual/{operatorId}
        defaults: { _controller: App\Controller\Poslog\OperatorController::historyIndividualAction }
        methods:  GET

Services.yml

    # This file is the entry point to configure your own services.
    # Files in the packages/ subdirectory configure your dependencies.
    
    # Put parameters here that don't need to change on each machine where the app is deployed
    # https://symfony.com/doc/current/best_practices/configuration.html#application-related-configuration
    parameters:
        locale: en
    
    
    services:
        # default configuration for services in *this* file
        _defaults:
            autowire: true      # Automatically injects dependencies in your services.
            autoconfigure: true # Automatically registers your services as commands, event subscribers, etc.
    
        # makes classes in src/ available to be used as services
        # this creates a service per class whose id is the fully-qualified class name
        App\:
            resource: '../src/'
            exclude:
                - '../src/DependencyInjection/'
                - '../src/Entity/'
                - '../src/Kernel.php'
    
        # controllers are imported separately to make sure services can be injected
        # as action arguments even if you don't extend any base controller class
        App\Controller\:
            resource: '../src/Controller/'
            tags: ['controller.service_arguments']
    
    
        # add more service definitions when explicit configuration is needed
        # please note that last definitions always *replace* previous ones
    
        globalHelper:
            class: App\Service\globalHelper
            public: false
            arguments: ['@service_container', '@doctrine.orm.entity_manager']

GlobalHelper starts out like this:

    namespace App\Service;
    
    use Symfony\Component\DependencyInjection\ContainerInterface as Container;
    //use Doctrine\ORM\EntityManager as EntityManager; //gave deprecation notice, profiler suggested to change to below and the deprecation notice disappeared.
    use Doctrine\ORM\EntityManagerInterface as EntityManager;
    
    
    class globalHelper {
    
    	private $container;
    	private $em;
    
    	public function __construct(Container $container, EntityManager $em) {
    		$this->container = $container;
    		$this->em = $em;
    	}

Just posted a question (below). I went to format it a little nicer (adding the PRE tags to the code blocks) and then it got marked as SPAM for some reason...

Moving from symfony 3 to 4 I started injecting the service according to this.

Most functions where I inject the "helper" service it works fine, but for some reason it fails on a few of them and I can't figure out what I've done differently... Here's the error:

<blockquote>Could not resolve argument $helper of "App\Controller\Poslog\OperatorController::historyindividualaction()", maybe you forgot to register the controller as a service or missed tagging it with the "controller.service_arguments"?</blockquote>

I've omitted the contents if the functions completely as it doesn't matter what they contain, I can comment out the entire code inside the HistoryIndividualAction() and still get the exact same error message.

The OperatorController::newAction() below works perfectly fine (as well as a number of other functions within the same object), while the OperatorController::HistoryIndividualAction() fails.

use App\Service\globalHelper as globalHelper;
...
class OperatorController extends AbstractController
{

  public function newAction(Request $request, ACRGroup $ACRGroup = null, globalHelper $helper)
  {
  ...
  }

  public function HistoryIndividualAction($operatorId, globalHelper $helper)
  {
  ...
  }

The routing looks like this

operator_new:
    path:     /new/{ACRGroup}
    defaults: { _controller: App\Controller\Poslog\OperatorController::newAction, ACRGroup: null }
    methods:  [GET, POST]

operator_history_individual:
    path:     /history/individual/{operatorId}
    defaults: { _controller: App\Controller\Poslog\OperatorController::historyIndividualAction }
    methods:  GET```


Services.yml

# This file is the entry point to configure your own services.
# Files in the packages/ subdirectory configure your dependencies.

# Put parameters here that don't need to change on each machine where the app is deployed
# https://symfony.com/doc/current/best_practices/configuration.html#application-related-configuration
parameters:

locale: en

services:

# default configuration for services in *this* file
_defaults:
    autowire: true      # Automatically injects dependencies in your services.
    autoconfigure: true # Automatically registers your services as commands, event subscribers, etc.

# makes classes in src/ available to be used as services
# this creates a service per class whose id is the fully-qualified class name
App\:
    resource: '../src/'
    exclude:
        - '../src/DependencyInjection/'
        - '../src/Entity/'
        - '../src/Kernel.php'

# controllers are imported separately to make sure services can be injected
# as action arguments even if you don't extend any base controller class
App\Controller\:
    resource: '../src/Controller/'
    tags: ['controller.service_arguments']

# add more service definitions when explicit configuration is needed
# please note that last definitions always *replace* previous ones

globalHelper:
    class: App\Service\globalHelper
    public: false
    arguments: ['@service_container', '@doctrine.orm.entity_manager']```

GlobalHelper starts out like this:

namespace App\Service;

use Symfony\Component\DependencyInjection\ContainerInterface as Container;
//use Doctrine\ORM\EntityManager as EntityManager; //gave deprecation notice, profiler suggested to change to below and the deprecation notice disappeared.
use Doctrine\ORM\EntityManagerInterface as EntityManager;

class globalHelper {

    private $container;
    private $em;

    public function __construct(Container $container, EntityManager $em) {
        $this->container = $container;
        $this->em = $em;
    }```

Hi, the video only shows a bundle called AppBundle but I have several bundles. Do I have to create a mapping for each bundle?

In a Symfony 3.4 project, I have several bundles in the src directory. Each of these bundles has a services.yml file and an DependencyInjection/Extension class. Some also have a config.yml file and a DependencyInjection/Configuration class.

Now I'm trying to convert to Symfony 4.3.

• Where should these internal bundle service definitions go?

• And more importantly, how do I deal with bundle configuration of these internal bundles when internal bundles aren't supposed to exist anymore?

Hi,
I must have skipped one page, I don't have the config/packages/doctrine.yaml file. I tried "composer require doctrine/doctrine-bundle" which added "doctrine/doctrine-bundle": "^1.9" in my composer.json but nothing else happens. What am I missing here ? How can I install Doctrine in my project ?
Thanks.

Edit : I found that I should use "require symfony/orm-pack" but the console answers "nothing to install or update"
Edit 2 : I deleted the vendor directory then re-ran (?) the previous command. Suddenly 83 installs, including doctrine, and "doctrine.yaml" is now in the packages directory (with several others - previously missing too - like google_recaptcha.yaml). All right, then, I can continue the migration ! I'll be back for many other questions ;)

Hi !

I'm actually facing a really weird error, the problem is 99% due to me, but I'm stuck.

First my error is :

In FileLoader.php line 168:

Expected to find class "UTM\CoreBundle\Controller\CoreController" in file "C:\Users\legof\Documents\GitHub\utm-website\src\UTM/CoreBundle\Controller\CoreController.php" while importing services from resource "../src/UTM/*", but it was not found! Check the namespa
ce prefix used with the resource in C:\Users\legof\Documents\GitHub\utm-website\config/services.yaml (which is loaded in resource "C:\Users\legof\Documents\GitHub\utm-website\config/services.yaml").

But I checked it couple times, the file and the namespace are ok.

Here are my services.yaml and the CoreController.php file

locale: fr

services:
    _defaults:
        autowire: true      # Automatically injects dependencies in your services.
        autoconfigure: true # Automatically registers your services as commands, event subscribers, etc.
        public: false       # Allows optimizing the container by removing unused services; this also means
                            # fetching services directly from the container via $container->get() won't work.
                            # The best practice is to be explicit about your dependencies anyway.
    App\:
        resource: '../src/*'
        exclude: '../src/{Entity,Migrations,Tests,UTM}'

    App\Controller\:
        resource: '../src/Controller'
        tags: ['controller.service_arguments']

    # REMOVE when AppBundle is removed
    UTM\:
        resource: '../src/UTM/*'
        exclude: '../src/UTM/{Entity,Repository}'

    UTM\Controller\:
        resource: '../src/UTM/Controller'
        public: true
        tags: ['controller.service_arguments']
    # END REMOVE

    UTM\UserBundle\Security\LoginFormAuthenticator: ~

    UTM\UserBundle\Security\UserProvider: ~

    UTM\UserBundle\Mojang\MojangAPI: ~

    UTM\UserBundle\Mojang\Uuid: ~

    UTM\FactionBundle\Twig\Extension\FactionExtension: ~

namespace UTM\CoreBundle\Controller;

use Symfony\Bundle\FrameworkBundle\Controller\Controller;

class CoreController extends Controller
{
    public function indexAction()
    {
        return $this->render('UTMCoreBundle:Core:index.html.twig');
    }
}