Hola Symfony

Vincent S. you're welcome!

Yes, you're right. Windows WSL forces you to use localhost instead of 127.0.0.1.
Thanks for sharing it! Cheers!

Hey @Doston-A

That's kinda weird, in theory Symfony 6 is compatible with PHP 8.4. Try running composer upgrade "symfony/*"

Cheers!

The error message is :
PHP Deprecated: Constant E_STRICT is deprecated in /home/doston/Documents/VinilMix/vendor/symfony/error-handler/ErrorHandler.php on line 58
PHP Deprecated: Constant E_STRICT is deprecated in /home/doston/Documents/VinilMix/vendor/symfony/error-handler/ErrorHandler.php on line 76<br />

Hey Doston,

Where exactly do you see that? In the console output of the symfony serve command? Anyway, I see you're on the latest stable PHP 8.4, which is great. Those messages are not errors but just deprecation warnings. That means that the project application should still be functioning; you can ignore those messages for learning purposes and continue following this course locally, it should not be a blocker for you. In case you want to deploy your project to production and allow your users to access it - I would recommend you to upgrade the dependencies first, as Diego suggested.

Cheers!

Victor , Hi ,
You are right , thanks you guys a lot , yes i continued the course and the error message is showing in every where , every console command, every twig environment. really i am afraid of to upgrade component because , I had experience with incompatibility between the article and the current version of the project and I spent a lot of time on it.
i know it is a part of coding and you learn a lot of things by this way, but when you are working at other working (not coding) on day, in evening i have little time to learn new somethings.
I am only was interested maybe someone know how to fixe this deprecation warnings. Of course i googled about it but i did not find any useful things.

Best regards,
Doston Asadov

Hey Doston,

I understand! First of all, you don't have to upgrade deps to try to fix it, you can just continue ignoring it.. but yeah, I understand that it may annoy you. You can try to suppress those warnings in your php.ini config file with:

error_reporting = E_ALL & ~E_DEPRECATED & ~E_USER_DEPRECATED

Restart the server just in case and warnigns should gone. That's a temporary solution, but should help. Just don't forget to return warnings back for your other (real) projects to avoid missing something important in them.

Or you can even try to supress them in your public/index.php, add this in the beginning:

error_reporting(E_ALL & ~E_DEPRECATED & ~E_USER_DEPRECATED);

Cheers!

i think 2 solution is sounds good and for temporary solution is good too.
you are the best !

Hey Doston,

For our course projects that you run locally, it should be good enough indeed. Just keep it in mind in case you decide to deploy it to production, then I would recommend you to do a proper fix by upgrading the dependencies :)

Cheers!

hi, Viktor

error_reporting(E_ALL & ~E_DEPRECATED & ~E_USER_DEPRECATED);
is not helped me and in the end of course when i send get request for getting audio file , status code was 200 but body of response begings with PHP Deprecated: Constant E_STRICT is deprecated in /home/doston/Documents/VinilMix/vendor/symfony/error-handler/ErrorHandler.php on line 58<br />PHP Deprecated: Constant E_STRICT is deprecated in /home/doston/Documents/VinilMix/vendor/symfony/error-handler/ErrorHandler.php on line 76<br /> and songs data. So audio play is not worked, and I found solution.
I use Linux Ubuntu , i install other version of php, 7.2, 7.4, 8.0, 8.2, 8.3 and only with 8.3 the error was disappeared.

Cheers!

Hey Doston,

Ah really, that won't work indeed. Well, there's a dirty solution, you can open that file in vendors and add @ in front of all ini_set()/ini_get() function calls, e.g.: @ini_set(...) - this will suppress the errors. Though do any changes in the vendor/ is not recommended, that might be OK in your case if you use this project only for learning purposes locally. On real projects better never do this.

But your solution to switch to Ubuntu is even better and much robust.

Cheers!

Hey Jan,

Thank you for your suggestion! Yeah, I agree, for newbies it might be crucial indeed!

Unfortunately, that's not that easy to cover this in this course. First of all, this is a course about Symfony, so we already suppose you know some PHP basics and so you already have PHP installed on your machine - I think most of our users hit this case. If you're new to PHP and don't know it at all - we would recommend you to learn PHP first instead of jumping into Symfony. We have some courses about PHP here in a separate track: https://symfonycasts.com/tracks/php . The same about Composer, you either have it installed and you know about it... or if not - please, check a separate course about it first: https://symfonycasts.com/screencast/composer .

Also, there's another problem with different platforms: MacOS, Windows, Linux... even different Linux distributions have their own different package managers and different ways to install PHP. That all complicates things a lot. If we will cover how to install it Mac in the screencast - it will be useful for Mac users only, but completely pointless for people on other platforms. That's why we do not cover such low lever things in the course about a completely different topic: Symfony introduction in this case.

And finally, if you experience any troubles to follow our courses - please, feel free to leave a comment below the video and our support team will help you!

I hope this helps and thanks for your understanding!

Cheers!

Hey Tim,

You almost nailed it, but mess up your configuration slightly. Try this one:

doctrine:
    dbal:
        default_connection: default
        connections:
            default:
                url: '%env(resolve:DATABASE_URL)%'
            old_wtb:
                url: '%env(resolve:DATABASE_URL_OLD_WTB)%'

So as you see you have the wrong level for default_connection.

Cheers!

Victor,

Is there a way I can reverse engineer the old_wtb database to entities? I found an article thats says to use the composer require symfony/orm-maker but it isn't supported anymore.

Hey Tim,

I think it should be in the core now, take a look at doctrine:mapping:import command, it imports mapping information from an existing database. I suppose that's what you need.

Cheers!

I did try that with the following command: ./bin/console doctrine:mapping:import --em=old_wtb --path=src/Entity/OldWtb yaml
Now I get this error:
[critical] Error thrown while running command "doctrine:mapping:import --em=old_wtb --path='src/Entity/OldWtb' yaml". Message: "Property "jobofferalertuserqueue" in "ClassificationTag" was already declared, but it must be declared only once"

Meanwhile I also tried to connect to a third database. When I try the import command: ./bin/console doctrine:mapping:import --em=wp --path=src/Entity/Wp yaml
The following error shows:
"Unknown database type enum requested, Doctrine\DBAL\Platforms\MySQL57Platform may not support it."

This is my current config:
`doctrine:

dbal:
    default_connection: default
    connections:
        default:
            url: '%env(resolve:DATABASE_URL)%'
        old_wtb:
            url: '%env(resolve:DATABASE_URL_OLD_WTB)%'
        wp:
            url: '%env(resolve:DATABASE_URL_WP)%'
        profiling_collect_backtrace: '%kernel.debug%'

orm:
    default_entity_manager: default
    entity_managers:
        default:
            connection: default
            mappings:
                App:
                    is_bundle: false
                    dir: '%kernel.project_dir%/src/Entity'
                    prefix: 'App\Entity'
                    alias: App
        old_wtb:
            connection: old_wtb
            mappings:
                OldWtb:
                    is_bundle: false
                    dir: '%kernel.project_dir%/src/Entity/OldWtb'
                    prefix: 'App\Entity\OldWtb'
                    alias: OldWtb
        wp:
            connection: wp
            mappings:
                OldWtb:
                    is_bundle: false
                    dir: '%kernel.project_dir%/src/Entity/Wp'
                    prefix: 'App\Entity\Wp'
                    alias: Wp`

Hey Tim,

I bet you should run that command for a new entity to avoid conflicts... I would recommend you to create a completely new and empty entity file and import it there even if you have already imported some fields manually. Then later you will be able to merge the new autogenerated entity from that import with your existing entity. That's. the best strategy I think.

About the 2nd error - hm, not sure, probably try to check the version of the DB you're trying to connect, and make sure you set up the server version correctly in your Doctrine config file, or most probably in your DATABASE_URL value.

I hope that helps!

Cheers!

Hi Victor,

Thank you for your quick reply. How can I run the command for a new entity? "I bet you should run that command for a new entity " I thought this config should do that:
dir: '%kernel.project_dir%/src/Entity/OldWtb'
prefix: 'App\Entity\OldWtb'
About the other error I did check the settings. I got these off my old project. But I will double check and try to debug.

Hey Tim,

you can do it with some workarounds I believe, e.g. you can just temporarily delete that ClassificationTag in your project and run the command... Or if that command requires an entity - you can at least temporarily delete or comment out the problematic property there.

Cheers!

Hey Victor,

Thank you for your reply. Unfortuntaly the configuration above isn't working for me.

This is my full config at doctrine.yml:

doctrine:
    dbal:
        default_connection: default
        connections:
            default:
                url: '%env(resolve:DATABASE_URL)%'
            old_wtb:
                url: '%env(resolve:DATABASE_URL_OLD_WTB)%'

        # IMPORTANT: You MUST configure your server version,
        # either here or in the DATABASE_URL env var (see .env file)
        #server_version: '16'

        profiling_collect_backtrace: '%kernel.debug%'
    orm:
        auto_generate_proxy_classes: true
        enable_lazy_ghost_objects: true
        report_fields_where_declared: true
        validate_xml_mapping: true
        naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
        auto_mapping: true
        mappings:
            App:
                type: attribute
                is_bundle: false
                dir: '%kernel.project_dir%/src/Entity'
                prefix: 'App\Entity'
                alias: App

when@test:
    doctrine:
        dbal:
            # "TEST_TOKEN" is typically set by ParaTest
            dbname_suffix: '_test%env(default::TEST_TOKEN)%'

when@prod:
    doctrine:
        orm:
            auto_generate_proxy_classes: false
            proxy_dir: '%kernel.build_dir%/doctrine/orm/Proxies'
            query_cache_driver:
                type: pool
                pool: doctrine.system_cache_pool
            result_cache_driver:
                type: pool
                pool: doctrine.result_cache_pool

    framework:
        cache:
            pools:
                doctrine.result_cache_pool:
                    adapter: cache.app
                doctrine.system_cache_pool:
                    adapter: cache.system

And this is the error I get:

Unrecognized option "profiling_collect_backtrace" under "doctrine.dbal". Available options are "connections", "default_connection", "driver_schemes", "types".

Can you see what's wrong?

I think I found it. The profiling_collect_backtrace: '%kernel.debug%' should also be indented another level.

doctrine:
    dbal:
        default_connection: default
        connections:
            default:
                url: '%env(resolve:DATABASE_URL)%'
            old_wtb:
                url: '%env(resolve:DATABASE_URL_OLD_WTB)%'
            profiling_collect_backtrace: '%kernel.debug%'

It was like this in my previously config:

doctrine:
    dbal:
        default_connection: default
        connections:
            default:
                url: '%env(resolve:DATABASE_URL)%'
            old_wtb:
                url: '%env(resolve:DATABASE_URL_OLD_WTB)%'
        profiling_collect_backtrace: '%kernel.debug%'

Hey Tim,

Good catch! I'm glad you were able to find it yourself :)

Most problems with config are about the wrong indentation. You can always leverage bin/console config:dump doctrine command to double-check that every option is on the correct level.

Cheers!

Hi Victor,

I ran into a new issue. At my project I manually created a new entity to connect to my old_wtb. My doctrine.yaml is as following:

doctrine:
dbal:
    default_connection: default
    connections:
        default:
            url: '%env(resolve:DATABASE_URL)%'
        old_wtb:
            url: '%env(resolve:DATABASE_URL_OLD_WTB)%'
        wp:
            url: '%env(resolve:DATABASE_URL_WP)%'
        profiling_collect_backtrace: '%kernel.debug%'
orm:
    auto_generate_proxy_classes: true
    enable_lazy_ghost_objects: true

    default_entity_manager: default
    entity_managers:
        default:
            connection: default
            report_fields_where_declared: true
            validate_xml_mapping: true
            naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
            mappings:
                App:
                    is_bundle: false
                    dir: '%kernel.project_dir%/src/Entity'
                    prefix: 'App\Entity'
                    alias: App
        old_wtb:
            connection: old_wtb
            report_fields_where_declared: true
            validate_xml_mapping: true
            naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
            mappings:
                OldWtb:
                    is_bundle: false
                    dir: '%kernel.project_dir%/src/Entity/OldWtb'
                    prefix: 'App\Entity\OldWtb'
                    alias: OldWtb
        wp:
            connection: wp
            report_fields_where_declared: true
            validate_xml_mapping: true
            naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
            mappings:
                OldWtb:
                    is_bundle: false
                    dir: '%kernel.project_dir%/src/Entity/Wp'
                    prefix: 'App\Entity\Wp'
                    alias: Wp

Company Entity

namespace App\Entity\OldWtb;

use App\Repository\OldWtb\CompanyRepository;
use Doctrine\ORM\Mapping as ORM;

#[ORM\Entity(repositoryClass: CompanyRepository::class)]
class Company
{

#[ORM\Id]
#[ORM\GeneratedValue]
#[ORM\Column]
private ?int $id = null;

#[ORM\Column(length: 255)]
private ?string $companyName = null;

public function getId(): ?int
{
    return $this->id;
}

public function getCompanyName(): ?string
{
    return $this->companyName;
}

public function setCompanyName(string $companyName): static
{
    $this->companyName = $companyName;

    return $this;
}
}

Now at my controller I'm trying to dump the companies for the old_wtb and default Manager.

BaseController.php

namespace App\Controller;

use App\Entity\Company;
use App\Entity\OldWtb\Company as PreviousCompany;

class BaseController extends AbstractController
{ #[Route('/companies', name: 'get_company')]

public function getCompanies(Request $request, ManagerRegistry $managerRegistry)
{
              $defaultEntityManager = $managerRegistry->getManager('default');

    $currentCompanies = $defaultEntityManager->getRepository(Company::class)->findAll();
    dump($currentCompanies);

    $oldWtbEntityManager = $managerRegistry->getManager('old_wtb');

    $oldCompanies = $oldWtbEntityManager->getRepository(PreviousCompany::class)->findAll();
    dd($oldCompanies);
 }
}

But I only see the default Manager Companies twice instead of the old_wtb companies and default companies.

If I dump the $defaultEntityManager and the $oldWtbEntityManager I can see that they are indeed different.

What's wrong?

Hey Tim,

Unfortunately, we don't have bandwidth to answer personal project related questions, and this topic is advanced and not covered by this tutorial.

My guess is that the default entity manager should be pointed to the subdirectory as well because right now it's literally linked to the global src/Entity/ folder which includes both your subdirectories: OldWtb and Wp. I would recommend you to use 3 separate folders like it's mentioned in the official docs, i.e. try to change the default entity manager prefix to src/Entity/Defaul/ for example. This way you will have 3 separate subfolders and will not have any overlapping.

I hope this helps and thank you for understanding!

Cheers!

Hi Victor,

I understand you don't have the bandwith to deep dive in all the questions. I thought the question could be of value for everyone that wants to have multiple database connections.

I did try to change the default entity manager prefix but then I had to change my entire code. But I found a solution!

At my project I did change the directory structure of the external Entities. So now I have my project entity folder like this: project/src/Entity

My Entity folder for the external Entities is Like this:

• project/src/ExternalData/Entity/OldWtb
• project/src/ExternalData/Repository/OldWtb

and

• project/src/ExternalData/Entity/Wp
• project/src/ExternalData/Repository/Wp

My config at project/config/packages/doctrine.yaml is as following:

    orm:
        auto_generate_proxy_classes: true
        enable_lazy_ghost_objects: true

        default_entity_manager: default
        entity_managers:
            default:
                connection: default
                report_fields_where_declared: true
                validate_xml_mapping: true
                naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
                mappings:
                    App:
                        is_bundle: false
                        dir: '%kernel.project_dir%/src/Entity'
                        prefix: 'App\Entity'
                        alias: App
            old_wtb:
                connection: old_wtb
                report_fields_where_declared: true
                validate_xml_mapping: true
                naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
                mappings:
                    OldWtb:
                        is_bundle: false
                        dir: '%kernel.project_dir%/src/ExternalData/Entity/OldWtb'
                        prefix: 'App\ExternalData\Entity\OldWtb'
                        alias: OldWtb
            wp:
                connection: wp
                report_fields_where_declared: true
                validate_xml_mapping: true
                naming_strategy: doctrine.orm.naming_strategy.underscore_number_aware
                mappings:
                    Wp:
                        is_bundle: false
                        dir: '%kernel.project_dir%/src/ExternalData/Entity/Wp'
                        prefix: 'App\ExternalData\Entity\Wp'
                        alias: Wp

I hope this will help anyone in the future!

Hey Tim,

Yeah, your change makes sense too, as long as the paths are not overlapped - it should work well.

I'm glad to hear you found a working solution for you, and thanks for sharing it with others!

Cheers!

Hey Kamil,

If you want to start from scratch a new project - I would recommend to start with this Symfony 6 course. Btw, we're working on Symfony 7 intro course that will be started releasing soon, but you can definitely start with this one to not wait it. And yes, you can watch everything in this track, and fall back to the previous Symfony version to look for more content - it may have some differences, but usually we add video and script notes to mention it.

But in case you're planning to maintain a legacy Symfony version - thats probably a good idea to start with the version you will have to maintain for simplicity.

Cheers!

Hey Danny,

First of all, we do recommend you to download the course code for this course on any video page - see "Download" button - and start from the start/ directory there. You will also find a README.md file inside with the detailed instructions about what command you need to run to bootstrap the course project locally. This way you will have the exact same versions we use in this course.

But if you want to follow this course on a newer Symfony version - that's up to you! But keep in mind some changes, depends on the version difference. Also, make sure you allow Composer to execute some plugins - otherwise Symfony Flex will not able to execute some recipes of dependencies and you really may miss some files unless copy/paste them manually.

Cheers!

Cheers!

Hey Mahmut,

Are you talking about this Symfony CLI download link? https://symfony.com/download Or what PHP version requirement are you talking about? Could you explain more please?

Cheers!

Hi Dear Victor,

I am really happy to see your message. Such community is realy nice to imrove ourselves.
For this topic, yes I mentioned that link. Actually, when we follow videos, I am not ( since I am junior, newbie) able to create projects well. I read other documentations about symfony then I was successfull.
Maybe if there can be step by step installation and requirements , will be perfect. because when I follow this video, ı was not aware of php version . so for example, maybe we can mention how to run on apache web server under /var/www/html etc.
other problem for example that ı encounter, I was doing my project in centos and ı needed to create .htaccess file to run my route.
Because http://172.22.111.7/index.bgp/my_route was working but http://172.22.111.7/my_route did not work etc.

thank you regards,

Hey Mahmut,

Thank you for your feedback! Yes, we do not talk about running this website on a real web server like Apache etc. mostly because Symfony makes it much simpler with the built-in web server we show in this course. Topic about running Symfony websites on a real web server deserves a separate course. Mostly, it's about production because configuring it for using locally does not make much sense thanks to the Symfony built-in web server. If you're looking into deploying a Symfony app to production - we have a separate course about it, see it here: https://symfonycasts.com/screencast/ansistrano - but mostly we talk about Nginx there instead of Apache, that is more "mainstream" lately :) Also, you can read more about recommended web server config in the official Symfony docs: https://symfony.com/doc/current/setup/web_server_configuration.html

About PHP version - yeah, we might not mention it in the video probably.. but you can see the minimum required PHP version for this course code on the "Versions" tab below the video on every video page - there's an actual composer.json file with all the main dependencies versions including PHP.

So, this is an intro course about Symfony, so we definitely don't want to complicate things too much for people who just want to start getting acquainted with Symfony, that topic deserve a separate more specific course :)

Btw, every course project code you downloaded will have a README file with all the necessary instructions what you have to boot the course project locally. If you miss it - that makes sense it was hard to configure the project locally for you.

Anyway, good catch on official Symfony docs. That's also a good spot to know more about Symfony, and it covers much more things that were not mentioned in the course.

I hope this helps!

Cheers!

ok, I just tried localhost (instead of 127....) and it worked. that's weird.

Hey Cameron,

Happy to hear you were able to find a workaround yourself, great job!

Yeah, sometimes it might be important, especially when you use Docker, or Windows also can give you some issues like this. What OS are you on btw?

I suppose if localhost works for you - great, just use it further. Btw, when you start the Symfony web server, i.e. run symfony serve - it should output you the correct URL. I wonder, if that a localhost URL or https://127.0.0.1:8000 for you?

I'm on windows 11, using WSL ubuntu. yes, it shows 127.0.0.1:800 - weird? thanks for the help.

Hey Cameron,

Ah, Windows + WSL, that makes sense unfortunately, I heard that has some problems with 127.0.0.1 and you have to use localhost instead. I think nothing much you can do with it, just remember to use localhost instead :)

Cheers!

Hey Kevin,

I'm not sure it's possible, probably you need to set up a real web server for this, Symfony binary usually is used for local development. Though, I think you need to think about somehow to open that port to your VM so you could run the Sf binary there but connect to it from your local machine (outside of VM). I think it should be possible, maybe try to google some info on the internet.

Cheers!

You can install it manually by moving the binary to a program folder such as this:
C:\Users\%USERNAME%\AppData\Local\Programs

Then copy the path to the folder where the .exe is and add it to your PATH
Windows > Search "env" > Edit the system environment variables > Edit Variables > Select "Path" > Add New > Paste and Apply

Hey Robert J.

My first suggestion is to user Windows WSL 2. It's an embedded Linux environment which works pretty well (that's what I use actually)

If you don't want to change to WSL, I found this SO answer which may help you out: https://stackoverflow.com/a...

I hope it helps. Cheers!