Rutas, Controladores & Respuestas!

Hey Mohsem,

I'm not sure I understand your question... Usually you don't need to specify methods there, the first few lines should register all your classes in the resource: ../src/Controller/ dir, i.e. this way you should not write a specific controller there, only the dir to all your controllers, i.e.:

controllers:
    resource: ../src/Controller/
    type: annotation

And it will register all your controllers, i.e. it will read all your route configuration there.

if you want to specify exact controller - you should use the code from the tutorial: https://symfonycasts.com/screencast/symfony5/route-controller#codeblock-b54cc0bccb where you need to specify the exact method. But then you should remove those few lines that are responsible for registering all your controllers or change it to avoid conflicts.

Cheers!

Hey Marius S.

I'd recommend you to wait the next version of tutorial, but the best way for you is to download code from this tutorial and use it instead of one generated by symfony new command. Also as way may be installing symfony 5 instead of 6 you can do it with
symfony new <project_name> --version=5.0

Cheers

Hey Brady Cargle

Try to clear cache, better to remove it manually, delete everything inside var/cache/ folder and restart your server, and try again.

Cheers!

That did the job. Thanks Vladimir :)

Hey Evgeny T.

It depends on use-case and your site structure, but it's totally good approach if you have dynamic data which should be included in multiple places.

Cheers!

Thanks a lot. I just wanted to know if this is a general practice.

Hi @Andreas

Can you please share your controller code? It's pretty hard to say something without seeing real code =)

Cheers

Idk why it looks for me that only 1st code is posted, so here is 2nd file
`
namespace App\Controller;

use Symfony\Component\HttpFoundation\Response;

class QuestionController
{
public function homepage(){

return new Response('What a nice site. START WORKING');
}

}`

Hey Jakub

You can ignore that warning. It's just PHPStorm doesn't know that the homepage function is going to be called dynamically by Symfony. Perhaps if you install the Symfony plugin it may help to get the warning away

Cheers!

I have Symfony plugin. I checked it on site. It doesnt work. I have still Symfony homepage instead of my words

Oh, I just noticed that you forgot to add the Route annotations on top of your homepage() method. Give it a try

Hey Chamal P.

You can just remove action="{{ path('/admin/account/edit') }}" attribute from <form> tag and it will send all data to the same page where you are currrently =)

Cheers!

Hey sam meunier

It looks like Symfony can't find your controller. Can you double-check the namespace of it, and double-check your config/services.yaml file, it should be registering your controllers as services

Cheers!

i have copy the files in script so i'm sure of it.

but i d'ont see the controller in config/services.yaml

it's here :

`# 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.html#use-parameters-for-application-configuration
parameters:

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'
        - '../src/Tests/'

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

`

thanks

Seems like you missed some how this piece of config:

services:
    # 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']

i have copied it seems to work but he say this :

`Invalid "exclude"

pattern when importing classes for "App\Controller\": make sure your

"exclude" pattern (../src/Tests/) is a subset of the "resource" pattern

(../src/Controller/) in

/home/sam/cauldron_overflow/src/../config/services.yaml (which is being

imported from "/home/sam/cauldron_overflow/src/Kernel.php").
`

the src\Tests\ line must go above the App\Controller line or not ?

` # 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\Controller\:
    resource: '../src/Controller/'
    tags: ['controller.service_arguments']
    exclude:
        - '../src/DependencyInjection/'
        - '../src/Entity/'
        - '../src/Kernel.php'
        - '../src/Tests/'  <-

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

`

sorry i'm new to symfony

Hey,

Somehow you ended up mixing the configuration. This is how your services.yaml file should look like:

# 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:

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,Entity,Migrations,Tests,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

give it a try and let me know if it worked. Oh, and welcome to Symfony! :)

hey,

thank you
it write again :

The controller for URI
"/" is not callable: Controller "App\Controller\QuestionController" does
neither exist as service nor as class.

i think it's the install of Symfony that failed, could it be ?
i had difficult to use the composer and Symfony during the install.

git status :

<blockquote>On branch master
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)

    modified:   config/routes.yaml
    modified:   config/services.yaml

Untracked files:
(use "git add <file>..." to include in what will be committed)

    config/services.yaml~
    src/Controller/QuestionController

no changes added to commit (use "git add" and/or "git commit -a")
</blockquote>

composer.json :

{
    "type": "project",
    "license": "proprietary",
    "minimum-stability": "stable",
    "prefer-stable": true,
    "require": {
        "php": ">=7.2.5",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "symfony/console": "5.3.*",
        "symfony/dotenv": "5.3.*",
        "symfony/flex": "^1.3.1",
        "symfony/framework-bundle": "5.3.*",
        "symfony/runtime": "5.3.*",
        "symfony/yaml": "5.3.*"
    },
    "require-dev": {
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": {
            "*": "dist"
        },
        "sort-packages": true
    },
    "autoload": {
        "psr-4": {
            "App\\": "src/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "App\\Tests\\": "tests/"
        }
    },
    "replace": {
        "symfony/polyfill-ctype": "*",
        "symfony/polyfill-iconv": "*",
        "symfony/polyfill-php72": "*"
    },
    "scripts": {
        "auto-scripts": {
            "cache:clear": "symfony-cmd",
            "assets:install %PUBLIC_DIR%": "symfony-cmd"
        },
        "post-install-cmd": [
            "@auto-scripts"
        ],
        "post-update-cmd": [
            "@auto-scripts"
        ]
    },
    "conflict": {
        "symfony/symfony": "*"
    },
    "extra": {
        "symfony": {
            "allow-contrib": false,
            "require": "5.3.*"
        }
    }

It could be, I'd re-install the vendors directory, and double-check the file name and namespace of the QuestionController

i have done :
- rm -rf vendor/*
- composer clearcache : he say : Composer is operating significantly slower than normal because you do not have the PHP curl extension enabled
- composer update

the vendor directory was empty with the rm command and normal with the update command
he says again :

The controller for URI
"/" is not callable: Controller "App\Controller\QuestionController" does
neither exist as service nor as class.

maybe i should get a copy from someone cauldron_overflow map so i can see the difference with mine ?

The composer warning it's interesting. You should install PHP curl and try again. Another thing you could try is to download again the course project from this page

i have rename QuestionController with QuestionController.php and it's work but phpstorm says 2 problems :
- missing function's return type declaration :9
- unused element: 'homepage' 9

Hey sam meunier

Sorry for my late reply. I got bugged down by the SymfonyWorld conference. You can add the return type to your controller's actions if you want
and about the unused element. You can ignore that warning because PHPStorm does not know that that method it's going to be calle dynamically

Cheers!

Hey Leo,

this is probably too late, but I had the same error. What helped was changing the ".env" file (right below vendor). In there, choose the database you are using and fill it with the data needed. For my personal setup, I just use MySQL, uncomment that and comment the "postgresql"-line. Then fill it with data, for me it looked like this:

<br />###> doctrine/doctrine-bundle ###<br /># Format described at https://www.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/configuration.html#connecting-using-a-url<br /># IMPORTANT: You MUST configure your server version, either here or in config/packages/doctrine.yaml<br />#<br /># DATABASE_URL="sqlite:///%kernel.project_dir%/var/data.db"<br />DATABASE_URL="mysql://root:@127.0.0.1:3306/library_project?serverVersion=5.7"<br /># DATABASE_URL="postgresql://db_user:db_password@127.0.0.1:5432/db_name?serverVersion=13&charset=utf8"<br />###< doctrine/doctrine-bundle ###<br />

I hope this helps.

Happy Coding

Martin

Hi,

I had the same error so i tried Martin's solution, and then the error transformed into "An exception occurred in driver: SQLSTATE[HY000] [2002] connection refused by the computer".

So, i went into "vendor\doctrine\dbal\lib\Doctrine\DBAL\Driver\PDOConnection.php", and around line 36 on the __construct(), i changed the $password from null to 'root'.

Then restart your server, and dont forget to start your wamp, xamp or mamp, because in my case it wont work without it (idk if they told us to activate it).

And thanks to Martin !

Hey Vandilour

Thanks for sharing your solution. All of it depends on how you configured your database in your local machine, so someone will or will not have the same problems as you

Cheers!

Hey Leo,

It's difficult to say what's wrong from the error message you share with us. What driver exactly? Is it PDO driver to connect to MySQL database? In what file do you see that error? Could you give us a bit more context on this error please? Sharing stacktrace would help.

Cheers!

Hi Angelika R.!

I'm really happy you like the quiz feature :)

> but I think that the text of the full answer is misleading

Hmm, I think you're right! As you correctly said, that word controller can mean either the class or the method/function. In this case, we were a bit lazy with our words and could have been more clear. I'm going to update that now!

Thanks!

Hey Joan P.

Did you uncomment the lines inside of config/routes.yaml?

Hey Simon L.!

Hmm, not normal! But good job noticing that :).

One of those (app_homepage) is coming from the annotations routes in your controller and the other (index) is coming from your config/routes.yaml file (I know because I remember that the default route in that file is just called "index"). When we switch to annotation routes in chapter 4 - https://symfonycasts.com/sc... - make sure you comment-out the YAML routes to avoid the duplicate - https://symfonycasts.com/sc...

Let me know if that helps!

Cheers!

Hi !

Thanks ! Works perfectly now :)

Hey Iheb Z.!

Hmm. That seems super odd. There is no reason that Symfony\Component\HttpFoundation\Response should not be in your project. I would try 2 things:

1) Manually remove the vendor/ directory and re-run composer install. See if that helps
2) Invalidate the cache in PhpStorm - you can do that at File -> "Invalidate Caches / Restart"

Let me know if that helps!

Cheers!

Ty for your help but I have the same problem.
Here you can find my files. you can check them, maybe I did a mistake.
https://drive.google.com/dr...

Hey Iheb Z.

Make sure that you have the following PHPStorm plugins installed and up to date
- Symfony Support
- PHP Annotations
- PHP Toolbox

Cheers!

Hey @Diego Aguiar

Ty for your support
yes it's already installed i watched chapter 1&2 and i did everything!

To ignore that error and keep watching tutos i just selected the type1 in response suggestions and added the use ... code manually it worked .

Cheers!

Well, at least it's working ;)
I believe it's a problem with PHPStorm, if you could update it, it may help