// composer.json
{
"require": {
"php": "^7.1.3",
"composer/package-versions-deprecated": "^1.11", // 1.11.99
"doctrine/doctrine-bundle": "^1.6", // 1.8.1
"doctrine/doctrine-cache-bundle": "^1.2", // 1.3.2
"doctrine/doctrine-migrations-bundle": "^1.1", // v1.3.1
"doctrine/orm": "^2.5", // v2.7.2
"fzaninotto/faker": "^1.7", // v1.7.1
"knplabs/knp-markdown-bundle": "^1.4", // 1.6.0
"sensio/framework-extra-bundle": "^5.0", // v5.1.3
"stof/doctrine-extensions-bundle": "dev-master", // dev-master
"symfony/asset": "^4.0", // v4.0.1
"symfony/console": "^4.0", // v4.0.1
"symfony/flex": "^1.0", // v1.9.10
"symfony/form": "^4.0", // v4.0.1
"symfony/framework-bundle": "^4.0", // v4.0.1
"symfony/lts": "^4@dev", // dev-master
"symfony/maker-bundle": "^1.0", // v1.0.2
"symfony/monolog-bundle": "^3.1", // v3.1.2
"symfony/polyfill-apcu": "^1.0", // v1.6.0
"symfony/profiler-pack": "^1.0", // v1.0.3
"symfony/security-bundle": "^4.0", // v4.0.1
"symfony/security-csrf": "^4.0",
"symfony/swiftmailer-bundle": "^3.1", // v3.1.6
"symfony/translation": "^4.0", // v4.0.1
"symfony/twig-bundle": "^4.0", // v4.0.1
"symfony/validator": "^4.0", // v4.0.1
"symfony/web-server-bundle": "^4.0", // v4.0.1
"symfony/yaml": "^4.0" // v4.0.1
},
"require-dev": {
"symfony/dotenv": "^4.0", // v4.0.1
"symfony/phpunit-bridge": "^4.0", // v4.0.1
"doctrine/doctrine-fixtures-bundle": "^3.0" // 3.0.2
}
}
54 Comments
Hello, what is the most current version that I could bring PHP to so that the project works without problems?
Hey @Ansise-S!
Are you asking specifically what version of PHP you need to get the code from this tutorials running? If so, we advertise that it'll work with PHP >= 5.5.9, but I would not be surprised if PHP 7.0 had some issues (8 would almost definitely be too new).
Or do you want to know what version of PHP you could use on a Symfony 3.4 project? If so, it looks like PHP
>=7.0.8should work: https://github.com/symfony/skeleton/blob/3.4/composer.json#L7Cheers!
Thank you very much for the answer, my question is the following, the company's server wants to update to php 8, and the project we currently have is symfony3.4 and the server runs php 7.4, but the requirement is to upgrade php 8 and symfony to 4.4, as I have no experience in doing this update symfony that's why this tutorial, because it seemed quite detailed to me in terms of the steps to follow. So what I want to know is what version of php 8 I could work with so that the project when I upgrade to symfony4 works without problems. Greetings and thank you for any answer you can give me.
Hey Ansise,
First of all, you have an ancient version of Symfony, because Symfony 3.4 & 4.4 are not supported anymore, you can see more information on this official page: https://symfony.com/releases/4.4
This means that, ideally, you will need to update your project at least to 5.4. But to do it, you first need to upgrade to 4.4 and then to 5.4.
If we're talking about Symfony 4.4 specifically, it requires PHP 7.1.3 or higher. And in theory it should work on PHP 8 but because it's not supported anymore - it's hard to tell for sure. And if it will not work, no PHP 8 support will be added to it because as I mentioned it's unmaintained anymore. For simplicity I would recommend you to stay on 7.4 for the Sf 4.4 upgrade and switch to PHP 8 after you will upgrade the project to Sf 5.4.
However, if your app is well covered with tests - you may try to upgrade it to Sf 4.4 and run the tests on PHP 8. If tests will pass - probably nothing to worry about and it should work. But it depends on how your app is well covered with tests.
Another possible problem - your dependencies. It might be so that your dependencies does not support PHP 8 and to upgrade them you first need to upgrade Symfony. Something that should be double-checked, but it's easy to check locally if you have PHP 8 installed.
I hope this helps!
Cheers!
Thank you very much, I will take your recommendation into account, it helps me a lot.
Hey Ansise,
Awesome, glad to hear it was helpful to you, and good luck with the upgrade!
Cheers!
I have followed the step that you provided to migrate from 3.3 to 3.4 but after I updated I am facing and issue now with AuthorizationChecker which fails when its trying to do isGranted() and returns an error:
Uncaught PHP Exception Symfony\Component\Security\Core\Exception\AuthenticationCredentialsNotFoundException: "The token storage contains no authentication token. One possible reason may be that there is no firewall configured for this URL."but before the migration everything was working fine :(
any ideas why the checks failing only after migration.
Hey @Sara!
Sorry for the slow reply - this was a tough issue, so it was left for me to do my best!
Ok, so this is interesting. I would not have expected simply upgrading from 3.3 to 3.4 to cause this. The error, as it says, typically means that the URL you are going to is not "under" a firewall. But what I can't imagine is why this would have changed going from 3.3 to 3.4.
What does your firewalls config look like for your security?
Cheers!
Hi what do I do after receiving this error message when trying to do php bin/console doctrine:database:create?.
PHP Warning: require(/.../start/app/../vendor/autoload.php): Failed to open stream: No such file or directory in /.../start/app/autoload.php on line 11
PHP Fatal error: Uncaught Error: Failed opening required '/.../start/app/../vendor/autoload.php' (include_path='.:/usr/share/php') in /.../start/app/autoload.php:11
Stack trace:
#0 /.../start/bin/console(17): require()
#1 {main}
thrown in /.../start/app/autoload.php on line 11
thank you for your help
Hey @Leilani!
That's no fun! Sorry about the trouble :). But, I know this error! Make sure you first run:
I believe that's all you're missing: you need this to populate your vendor/ directory. It should be mentioned in the README.md file in the code download - but let me know if you didn't find it.
Cheers!
hello i really have a big problem with my application and i would love some help
Please halp!
Hey @oumaima
Can you provide more details? What problem? What application? We will be glad to help you!
Cheers!
HI
just a quick question: how do I update the new directory structure? I did not have a public folder with Symfony 3.4, it seems I need it with Symfony 4.0.
Thanks
mario
Hey mario
In symfony 4, the
webdirectory got renamed topublicbut everything else is almost the same (inside that directory)Cheers!
Hi,
thanks for your reply.
Sorry, I did not explain myself. My 3.4 directory is:
├── app
│ ├── AppCache.php
│ ├── AppKernel.php
│ ├── autoload.php
│ ├── config
│ │ ├── ...
│ └── Resources
│ ├── Public
│ └── views
├── bin
│ ├── console
│ ├── php_errors.log
│ └── symfony_requirements
├── composer.json
├── composer.lock
├──. ...
├── src
│ └── MyBundle
│ ├── BlogBundle (a custom bundle)
│ │ ├── Controller
│ │ ├── DependencyInjection
│ │ ├── Entity
│ │ ├── Form
│ │ ├── JusBlogBundle.php
│ │ ├── Repository
│ │ ├── Resources (most view and public stuff is within these directories, for each bundle)
│ │ └── Tests
│ ├── ... several more bundles
├── var
│ ├── ...
├── vendor
│ ├── ...
└── web
├── ...
├── bundles
│ ├── jusblog -> ../../src/Jus/BlogBundle/Resources/public/
│ ├── ... several more symlinks
├── config.php
I modify composer.json, and >composer update; seems to work fine. But my web app does not work any more, since the directory structure remains the old one. I am not sure what the guideline are to move things around as to define the new structure.
Thanks Cheers
mario
Yeah, the structure changed considerably in Symfony4 and it's a manual process. If you keep watching the tutorial you will learn how Ryan handled it (and, of course, you can keep asking us questions :)
Cheers!
It's probably worth noting that as of Twig 2.7 (roughly Mar 2019), users will get an additional deprecation warning after updating to Symfony 3.4:
Using the "Twig_Extension" class is deprecated since Twig version 2.7, use "Twig\Extension\AbstractExtension" insteadI don't think this affects anything else in the tutorial, however, since twig's deprecations (and development path) are independent of symfony's.
Hey John christensen
You are right, Twig deprecations are other thing to consider but it has nothing to do with Symfony. You could even start a new Symfony project without Twig :)
Cheers!
Hi
You mentioned in the video that version 3.4 and 4 are identical. https://symfony.com/doc/cur... on this page from the symfony docs it says that symfony 4.0 requires PHP version 7.1.3 or higher. So as I understand, symfony 3.4 also requires at minimum PHP 7.1.3, correct? I am asking because the hosting I eventually want to deploy to can only run PHP 7.1.1 at this moment and upgrading to a higher version will not be possible for some time, maybe 6 months to a year.
I intended to start developing on symfony 3.4 and eventually upgrade to 4, because this page from the docs states that 3.4 only requires PHP 5.5.9 to run: https://symfony.com/doc/3.4...
I am a bit confused I must say :(
Hey Tobias I.
In the video, Ryan was talking about Symfony's behavior but as you already investigated, Symfony4 requires PHP >=7.1.3 in order to work, so if you really can't upgrade to that version, then you should stick with Symfony 3.4 and eventually do the upgrade
Here you can see all the requirements of Symfony3.4 https://github.com/symfony/...
Cheers!
Thanks for clarifying.
Have an awesome day :)
Hi,
"But thanks to optimizations in PHP 7, it's not needed anymore. Less code, more speed, woo!"
Whats r the optimisations in php7 that dont require loadCacheClasses.
Thanks in advance
Hey!
Great question! And actually, I wasn't sure myself :). So, I did some digging. Here is the source: https://github.com/symfony/...
It appears that the optimizations were more related to the Composer optimized autoloader & OpCache. That issue doesn't mention the exact things in PHP 7 that really allowed this. So, unfortunately, I can't answer that question fully. A lot was optimized in PHP 7, so it could have been a number of things.
Cheers!
Cool, I see now. I should have check why $kernel->loadClassCache() exist in the 1st place.
If anyone is interested. In the docs https://symfony.com/blog/ne....
It says
"Symfony provides three autoloaders via the ClassLoader component: two of them load classes that follow PSR-0 and PSR-4 standards and the other one uses a static map of classes and files. In addition, Symfony provides special wrappers for those loaders to add caching and debugging features."
So i guess previous to symfony 4, it reorders ur code and stores it in var/cache, so that it loads properly, then bring it to opcache as precompiled script. In symfony 4 it goes straight to opcache. I think this is right?
thanks for taking the time
Besides upgrading to PHP 7, what would you recommend people who are stuck on PHP 5.5.9 do in regards to the ```Kernel::loadClassCache()``` call? For internal reasons we have several apps that are still on Ubuntu 14.04 LTS versions and the systems administrators prefer to install PHP via APT, so we are limited on upgrading. I see that it looks like in a new Symfony 3.4 install they wrap this in a ```if (PHP_VERSION_ID < 70000) {}``` block, but I still had errors when I tried to load with that. Any recommendations?
Hey J.R. Jenkins!
Ah, stuck on PHP 5 - I understand it, but bummer! So, if you're stuck on PHP 5, then you're also stuck in Symfony 3.4 for now. This basically means that, until you're ready to upgrade to Symfony 4, you should just ignore the loadClassCache() stuff (i.e. LEAVE them - don't remove them). You mentioned you're having "errors" - you should only have deprecation warnings. Are you getting actual errors with loadClassCache()?
Cheers!
weaverryan I did get an error, although I will have to look it up when I get back to work in the morning, that actually led me to this discussion in the Symfony issue queue, https://github.com/symfony/.... Basically I had started with a 3.4 install and was slowly developing things out, but when trying to access the site through app.php it would crash with what I believe was the "Cannot redeclare class Symfony\Bundle\FrameworkBundle\Controller\ControllerNameParser" error
Commenting out both the include for bootstrap.php and call to loadClassCache resolved the issue, but that didn't seem right. I was going to dig into when I saw you were releasing this course so I thought I would see what you all had to say :-)
So I am apparently crazy or had some other bug that I didn't realize, as I uncommented those lines, cleared my caches, and there is no error... sorry for the red herring.
Ah yes, you started a new project - I'm aware of that bug you linked to. But, I'm glad it's working now - I'm not sure if your code contains that fix or not - but I wouldn't worry about it unless it comes up again :).
Cheers!
Hi weaverryan,
I install the a fresh symfony 4 with composer create-project symfony/skeleton
Everything seems to be ok. So I want to install all components. The symfony site (https://symfony.com/doc/cur... says to composer require symfony/symfony
I get an error
Your requirements could not be resolved to an installable set of packages.
Problem 1
- symfony/symfony v4.0.0 conflicts with __root__[No version set (parsed as 1.0.0)].
- symfony/symfony v4.0.1 conflicts with __root__[No version set (parsed as 1.0.0)].
- symfony/symfony v4.0.2 conflicts with __root__[No version set (parsed as 1.0.0)].
- Installation request for __root__ No version set (parsed as 1.0.0) -> satisfiable by __root__[No version set (parsed as 1.0.0)].
- Installation request for symfony/symfony ^4.0 -> satisfiable by symfony/symfony[v4.0.0, v4.0.1, v4.0.2].
My composer is of the latest version 1.5.6
Am I doing something wrong?
Thxs.
Hey Shing,
Good catch! Actually, it's impossible to require symfony/symfony due to this line: https://github.com/symfony/... . As you can see, it forbids installation of symfony/symfony. I'm not sure about the reasons behind, but I think it's kind of bug in Symfony docs. I opened an issue about it here: https://github.com/symfony/...
So, the only way I see is to install all the deps manually obviously specifying them in composer.json. Actually, it's not a best practice to install all the Symfony components to your project when you don't use them *all*. And probably in most cases you won't use them all :)
Cheers!
Hi Victor, Glad I know I'm not mad. I'm rather new at this. I guess documentation might not always be accurate. Also the change from symfony 3 to 4 does not seem trival.
Thanks for help :)
Hey Shing,
I agree, it's not trivial, but that's the price to increase code quality and make development more smooth. However, Symfony devs made all their best to make this upgrading process very smooth, thanks to cool deprecation notices feature.
Cheers!
In the lastest version of symfony3, the config.yml is not generated by using 'composer create-project symfony/skeleton 3.4'. I tried to load the file "doctrine_cache.yaml", but failed. When I type 'php ./bin/console dubug:container markdown_cache', the command line says 'In ContainerDebugCommand.php line 211: No services found that match "markdown_cache". How can I create a custom server? Can you help me ?
Hey Nan,
You're right, there's no config.yml anymore, it was splitted to separate files, that's why you need to create it "doctrine_cache.yaml" file manually inside "config/packages/". Actually, this question is duplicated, so look at my original answer:
https://knpuniversity.com/s...
Cheers!
Hey guys,
I had a working site at version 3.3.16. When I upgraded to 3.4 by changing the version number in composer.json and executing composer update, I got the following cryptic error message: "Circular reference detected for service "routing.loader", path: "routing.loader".
How do I find and fix that problem?
Hey Dan,
Sometimes upgrading is a bit tricker than just Symfony constraint tweaking to 3.4. First of all, try to compare the original composer.json file for 3.4 branch and tweak other constraints of core deps as well according to it: https://github.com/symfony/...
Also, try to manually remove folders from var/cache/* like dev/, prod/, test/, etc.
Then run composer update again, probably it helps. If not, try to make the output more verbose with:
composer update -vvv
It should give you more context to find the root of the problem. If you still cannot handle it - show us the verbose output with "-vvv" option and we'll try to help you.
Cheers!
Victor,
I followed those steps to no avail. I even cleared my composer cache and made it download all the packages again. No joy there either.
I hope the following is enough information for you to see something I don't.
Here's an excerpt from my composer.json file:
When I do composer update -vvv, I get this response:
Thanks!
OK, I see toy have this error on clear cache step.
First of all, I let's bump "symfony/swiftmailer-bundle" constraint to "^2.6.4", I see you have lower one. Also, let's use "symfony/symfony": "3.4.*" to allow only patch updates and try again. If you see the same error, let's temporarily remove this line:
Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache
So, the idea is to achieve green composer update operation. Then you can probably debug it later why cache clear thrown an error.
Btw, do you have any custom route loaders?
Cheers!
Victor,
I found the problem!!!! I had two controllers responding to the same path (one in each of the two bundles I was developing). Evidently that creates a routing loop. For some reason, Symfony 3.3 was just fine with that, but Symfony 3.4 was throwing errors. It looked like a problem with the upgrade, but it was a problem in my code that I was not aware of.
So, life is good! Thanks for your help.
Hey Dan,
Ah, not an obvious problem :) Glad you found a problem!
Cheers!
Hello,
Going back to the REST tutorial, in case of JwtTokenAuthenticator what functionality would you put into supports supports() and how should getCredentials() be refactored?
Thank you!
Hey Vlad,
I think it may be refactored as:
Cheers!
Thanks, Victor!
There is only one minor detail. If you look at the PHPDoc for the getCredentials function in AuthenticatorInterface, it says the return value must be Any non-null value
What should it be, if the $token is null?
Hey Vlad,
Ah, then probably the best would be:
Actually, the same example you can see in docs: https://symfony.com/doc/current/security/guard_authentication.html#step-1-create-the-authenticator-class
Cheers!
Thank you!
How does one get the color green in the command prompt ??
All I get is Black & White and I'm a bit jealous. Do I need to buy a Mac?
Hey @kribo,
Haha, it depends :) Btw, what OS you are on? Somehow your terminal does not allow ansi output by default. Well, you can try to force ANSI output with --ansi flag, for example, Composer has this option, so try:
$ composer --ansi
Do you see color output now? The same for Symfony commands, i.e. bin/console, try to add --ansi flasg to force ANSI output. What terminal do you use? I think you can configure your terminal to always support ANSI output and you won't need to pass that flag.
Cheers!
Got it to work..
OS = Win10 pro => had to install ANSICON from
1- https://github.com/adoxa/an....
2- open cmd and navigate to the unzipped folder
3- Navigate to x64 (if you have a 64 bit machine) otherwise navigate to x86
4- Type ansicon.exe -h and you will get the following:
D:\Data\ansicon\x86>ansicon.exe -h
And bingo it works I've now also got a green bar when I run the server....lol
Great! Thanks for sharing it with others :)
Cheers!
"Houston: no signs of life"
Start the conversation!